.
+
+# FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at .
+
+© ITU 2018
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|----------------------------------------------------------------------------------------|------|
+| 1 Scope..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 1 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 2 |
+| 6 Introduction..... | 2 |
+| 7 Cloud-based network management functional architecture ..... | 3 |
+| 7.1 Basic concept..... | 3 |
+| 7.2 Detailed structure of cloud-based network management functional architecture ..... | 4 |
+| 7.3 The functions of each part in the architecture ..... | 5 |
+| 7.4 The relationship between the components in the architecture..... | 6 |
+
+
+
+## Recommendation ITU-T M.3071
+
+## Cloud-based network management functional architecture
+
+# 1 Scope
+
+This Recommendation provides details on the concept of cloud-based network management functional architecture and its fundamental components. It describes the composition of a cloud-based network management functional architecture, explains the functions of each component in the architecture, and also introduces the relationship between these components.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*.
+
+[ITU-T Y.3521] Recommendation ITU-T Y.3521/M.3070 (2016), *Overview of end-to-end cloud computing management*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 management service** [ITU-T M.3010]: A management service is an offering fulfilling specific telecommunications management needs.
+
+**3.1.2 network element** [ITU-T M.3010]: An architectural concept that represents telecommunication equipment (or groups/parts of telecommunication equipment) and supports equipment or any item or groups of items considered belonging to the telecommunications environment that performs network element functions (NEFs).
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 cloud-based network management**: Cloud-based network management is to perform network management functions using cloud-computing technology, and it can also be used to manage both traditional telecommunication networks and/or cloud computing infrastructures.
+
+**3.2.2 management service analysis function:** The management service analysis function provides the ability to analyse each management service in the network management. Each management service is registered in this analyser function, and all related information about this service is analysed and stored for future use.
+
+**3.2.3 management service composing function:** The management service composing function provides the ability of composing several small management functions into a new complex management service, so that a new type of management functionality can be easily provided without having to change the implementation of the component management functions.
+
+**3.2.4 management service deployment function:** The management service deployment function provides the ability of deploying required services for a management task. Each management task may need the support of multiple management services, and for those services which are not ready for use, they will appropriately be deployed into some virtualized resources on the cloud infrastructure.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|-----|--------------------------|
+| FS | Function Set |
+| IT | Internet Technology |
+| NE | Network Element |
+| NEF | Network Element Function |
+| P&C | Perception and Control |
+| VM | Virtual Machine |
+
+# 5 Conventions
+
+None.
+
+# 6 Introduction
+
+Current network management and technologies have the weak point that when new management requirements are proposed, it is difficult to provide a new management service based on the existing services using traditional management technology. It is also hard to compose a small system with simplified management functions on demand.
+
+Cloud computing has become one of the mainstream technologies used in telecommunication networks, as well as Internet services. Cloud-computing technology has the following benefits: high usage rate of physical resources, reliable service provision, high extensibility, cost efficient and service on demand, etc. When introducing cloud computing technology into the network management domain, it is easy to solve the above problems, and it will be very flexible to provide new management services.
+
+When introducing the cloud into network management, it means that different management function blocks can be placed into virtual resources, and the virtualized resources can be grouped together to form a composed management service that is more powerful to provide complex management functions. It is also capable of dealing with a large amount of management data, as distributed computing can be carried out on cheap servers.
+
+The term management services used in this Recommendation is not the cloud service provided by a network operator or a cloud operator. Management services are provided by a management system, regardless of whether it is based on the cloud or not. A cloud service is provided by a cloud-service provider to end users for resource virtualization, which provides end users with the cloud-computing and/or cloud-storing capabilities.
+
+A cloud-aware management system described in [ITU-T Y.3521] is a management system which can be used to manage both traditional telecommunication networks and cloud-computing infrastructures. A cloud-based management system in this Recommendation is a management system which is built using cloud-computing technology, and it can also be used to manage both traditional telecommunication networks and/or cloud-computing infrastructures. A cloud-based management system can be a cloud-aware management system, but it is not necessary to manage cloud infrastructures using a cloud-based management system.
+
+# 7 Cloud-based network management functional architecture
+
+## 7.1 Basic concept
+
+Cloud computing is a technology from the IT domain, with the aim for a supplier to share computing and storage capabilities in the cloud to multiple customers. A system can be built using the traditional means, or using cloud-computing technology to provide services to customer and using the cloud as its infrastructure, as far as the services can be provided. A network management system is a software system which provides network management services to operators or telecommunication service providers. Thus using cloud technology in network management systems will also bring the benefits of the cloud into the network management field.
+
+Cloud-based network management systems may include two main parts, one is the cloud-based network management platform, and the other is management applications for various network technologies which are built over the management platform.
+
+Figure 1 shows the basic concept of the cloud-based network management platform and the management applications.
+
+
+
+The diagram illustrates the basic concept of the cloud-based network management platform and applications. It consists of three ovals, each labeled "Management application", arranged horizontally at the top. Below these ovals is a single rectangle labeled "Cloud-based network management platform". Three vertical arrows point from each of the three ovals down to the rectangle, indicating that the applications run on or are supported by the platform. Below the rectangle, the text "M.3071(18)\_F01" is displayed.
+
+Diagram showing three 'Management application' ovals above a 'Cloud-based network management platform' rectangle, with arrows pointing from each application to the platform.
+
+**Figure 1 – Cloud-based network management platform and applications**
+
+The cloud-based network management platform is described in detail in clause 7.2. Management application functions can be the applications that provide functions dedicated to the management of a specific network technology (e.g., mobile core network, transport network), and they provide their own functionality for its dedicated network, and share the lower layer functions of the cloud-based network management platform, e.g., cloud infrastructure management, or common management services.
+
+## 7.2 Detailed structure of cloud-based network management functional architecture
+
+### 7.2.1 High-level layering of cloud-based network management functional architecture
+
+
+
+```
+
+graph TD
+ subgraph Management_service_layer [Management service layer]
+ direction LR
+ MSF1[Management service function]
+ MSF2[Management service function]
+ MSF3[Management service function]
+ MSF4[Management service function]
+ end
+
+ subgraph Perception_and_control_layer [Perception and control layer]
+ PCMF[P&C management function]
+ PCAF1[P&C application function]
+ PCAF2[P&C application function]
+ PCAF3[P&C application function]
+ PCMF --> PCAF1
+ PCMF --> PCAF2
+ PCMF --> PCAF3
+ end
+
+ subgraph Managed_network_layer [Managed network layer]
+ direction LR
+ NEF1((NEF))
+ NEF2((NEF))
+ NEF3((NEF))
+ NEF4((NEF))
+ end
+
+ MSF1 --> PCMF
+ MSF2 --> PCMF
+ MSF3 --> PCMF
+ MSF4 --> PCMF
+
+ PCAF1 --> NEF1
+ PCAF2 --> NEF2
+ PCAF3 --> NEF3
+ PCAF3 --> NEF4
+
+```
+
+M.3071(18)\_F02
+
+Diagram of the high-level layering of cloud-based network management functional architecture showing three layers: Management service layer, Perception and control layer, and Managed network layer.
+
+**Figure 2 – High-level layering of cloud-based network management functional architecture**
+
+Figure 2 shows the high-level layering of cloud-based network management functional architecture, which includes the following three layers:
+
+- **Managed network layer:** This layer indicates the layer containing all the network element functions (NEFs) that are to be managed. The NEs providing the NEFs can be the traditional telecommunication network elements, or elements in a cloud infrastructure.
+- **Perception and control layer (P&C layer):** This layer indicates the perception function blocks and the NE controlling function blocks. Perception function blocks have the capability to collect the configuration information, running status, or the performance data from the NEFs, and the NE controlling function blocks are able to make necessary reconfigurations or modifications to NE parameters, through interactions with the specified NEFs.
+- **Management service layer:** This layer mainly contains the network management function blocks, which provide management services to network operators.
+
+### 7.2.2 Detailed composition of cloud-based network management functional architecture
+
+
+
+The diagram illustrates the detailed composition of the management service layer, organized into two primary functional sets:
+
+- Network management application function set:** This set is further divided into two functional sets:
+ - Management service FS:** Contains four identical "Management service function" blocks.
+ - Management controller FS:** Contains four distinct functions: "VM monitor function", "Management service analysis function", "Management service deployment function", and "Management service composing function".
+- Cloud infrastructure function set:** This set is divided into:
+ - Cloud hypervisor function:** A single function block.
+ - Cloud physical element functions:** A single function block.
+
+M.3071(18)\_F03
+
+Figure 3: Detailed composition of the management service layer. The diagram shows two main functional sets: Network management application function set and Cloud infrastructure function set. The Network management application function set is divided into Management service FS (containing four Management service functions) and Management controller FS (containing VM monitor, Management service analysis, Management service deployment, and Management service composing functions). The Cloud infrastructure function set is divided into Cloud hypervisor function and Cloud physical element functions.
+
+**Figure 3 – Detailed composition of the management service layer**
+
+Figure 3 shows the detailed composition of cloud-based network management functional architecture, which is a "refinery" of the components in the management service layer as shown in Figure 2.
+
+The cloud-based network management functional architecture is composed of the following two main parts: cloud infrastructure function set and network management application function set.
+
+The cloud infrastructure function set includes cloud physical element functions and a cloud hypervisor function above them. Cloud physical element functions provide the basic functions of computing and storage. The cloud hypervisor function provides the functionality to manage cloud physical elements, and provide virtualization functions above them.
+
+The network management application function set may be further divided into two parts: management controller function set and management service function set. The management controller function set includes the basic supporting functions of the management platform, and also provides common functions to support management applications. The management service function set provides management functions, which are divided into several aspects of network management, and usually they are application specific.
+
+## 7.3 The functions of each part in the architecture
+
+In Figure 3, the functions of each component are further explained in this clause.
+
+- 1) **Cloud physical element function:** This is the lowest level of cloud infrastructure and is usually composed of the functions provided by physical servers, computers, disks, network connectors, and all other elements that form a physical cloud computing environment. It provides the basic computing and storage resources from the physical layer.
+- 2) **Cloud hypervisor function:** This is a management layer over cloud physical element functions. The cloud hypervisor function provides the management ability of virtualized resources, for example, creating/deleting a new virtual machine (VM), start/suspend a VM,
+
+and query/change a configuration of a VM, etc. It also provides users with virtualized resources using a unified interface. From the users' perspective the cloud hypervisor function can provide computing and storage capabilities dynamically, based on users' requirements.
+
+- 3) Management controller function set: This contains multiple controlling functions that support the running of the cloud-based network management platform, and each function can be implemented by a small function block. Some basic function blocks in the controllers are listed below.
+ - VM monitoring function: This function provides the ability to monitor the performance of VMs. It monitors the dynamic information of the running status of VMs. When performance degradation is detected, the monitor informs the controller to handle the resource reassignment or service transportation.
+ - Management service analysis function: This function provides the ability of analysing each management service in the network management. Each management service is registered in this analyser, and all the related information about this service is analysed and storage for future use.
+ - Management service deployment function: This function provides the ability of deploying required services for a management task. Each management task may need the support of multiple management services, and for those services which are not ready for use they will appropriately be deployed into some virtualized resources on the cloud infrastructure.
+ - Management service composing function: This function provides the ability of composing several small management functions into a new complex management service, so that they can easily provide a new type of management functionality without having to change the implementation of the component management functions.
+ - More function blocks can be extended to support the running of the cloud-based network management architecture.
+- 4) Management service function set: This provides management functions to network operators, and is composed of all kinds of small management functions. Each network management function is performed by a service application, and those management functions can form composed services that provide more complex network management functions. Most management service applications are application-specific to a network technology, but there are still some applications which are more general to be used across different network technologies. In such cases, the common service application will be reused.
+
+## **7.4 The relationship between the components in the architecture**
+
+This clause will introduce the relationship between the components in the architecture.
+
+
+
+The diagram illustrates the cloud-based network management functional architecture, organized into three main layers within a dashed boundary, with an external component on the right.
+
+- Top Layer (Management service FS):** Contains three boxes labeled "Management service function". They are connected horizontally by reference points **r4**. The rightmost box connects to an external box labeled "NEFs of the network to be managed" via reference point **r5**.
+- Middle Layer (Management controller FS):** Contains four boxes: "VM monitor function", "Management service analysis function", "Management service deployment function", and "Management service composing function". This layer is connected to the top layer via reference point **r3**.
+- Bottom Layer (Cloud infrastructure function sets):**
+ - Contains a box labeled "Cloud hypervisor function" at the top.
+ - Below it, three boxes labeled "Element function" are shown, collectively labeled "Cloud physical equipment functions".
+ - The "Cloud hypervisor function" box is connected to the "Element function" boxes via reference point **r1**.
+ - The entire bottom layer is connected to the middle layer via reference point **r2**.
+
+Labels on the left side of the diagram identify the top two layers as the "Network management application function set" and the bottom layer as "Cloud infrastructure function sets". A label **M.3071(18)\_F04** is located in the bottom right corner.
+
+Diagram of cloud-based network management functional architecture showing layers for management services, management controller, cloud hypervisor, and physical equipment functions, with reference points r1 through r5.
+
+**Figure 4 – Reference point between the components in the cloud-based network management functional architecture**
+
+Figure 4 shows the reference point between the components in the cloud-based network management functional architecture. All the reference points in Figure 4 are defined in [ITU-T M.3010]. In order to distinguish these references points in this Recommendation, which can show the relationship among functional components, they are numbered as r1, r2, r3, r4 and r5 respectively, as explained in Table 1.
+
+**Table 1 – Reference points in cloud-based network management functional architecture**
+
+| Name | Position | Definition |
+|-------------|------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| r1 | Between cloud hypervisor function and cloud physical element function. | Through reference point r1 a hypervisor function can connect to cloud physical element functions to perform the virtualized resource management functions (for example, VM management, including but not limited to, creation, deletion, query and modification of virtualized resources.) In this Recommendation the virtualized resource will be assigned to building the management system itself. |
+| r2 | Between management controller function set and cloud hypervisor function. | Through reference point r2 the management controller function set can interact with the cloud hypervisor function. The management controller function set sometimes may ask the cloud infrastructure function set to assign new virtual resources in order to meet new management requirements. Through this reference point there is no need for management controller FS to know any details about the physical layer resources, and it only sends the command including the requirement for the virtualized resources, and then the cloud hypervisor function will handle the rest. |
+| r3 | Between management service function set and management controller function set. | Reference point r3 is provided from the management controller function set to the management service function set. Through this reference point applications can use the common functions provided by the management controller FS. For example, one service application can search for another service application which may be able to meet its requirements. Management controller FS can also use this reference point to perform the management service analysis and composition, etc. |
+| r4 | Between management service applications. | Reference point r4 is between the management service functions at the application level. Usually, there are cases when one management service function needs the support of another management service function, then it just invokes the function provided by that management service function. Reference point r4 is used in this situation. |
+| r5 | Between management service function set and the NEFs of the network to be managed. | The network to be managed is the target for network management. Through reference point r5 management service functions can interact with the NEFs in the network to be managed, and perform the actual network management functions. |
+
+
+
+# SERIES OF ITU-T RECOMMENDATIONS
+
+| | |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Series A | Organization of the work of ITU-T |
+| Series D | Tariff and accounting principles and international telecommunication/ICT economic and policy issues |
+| Series E | Overall network operation, telephone service, service operation and human factors |
+| Series F | Non-telephone telecommunication services |
+| Series G | Transmission systems and media, digital systems and networks |
+| Series H | Audiovisual and multimedia systems |
+| Series I | Integrated services digital network |
+| Series J | Cable networks and transmission of television, sound programme and other multimedia signals |
+| Series K | Protection against interference |
+| Series L | Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant |
+| Series M | Telecommunication management, including TMN and network maintenance |
+| Series N | Maintenance: international sound programme and television transmission circuits |
+| Series O | Specifications of measuring equipment |
+| Series P | Telephone transmission quality, telephone installations, local line networks |
+| Series Q | Switching and signalling, and associated measurements and tests |
+| Series R | Telegraph transmission |
+| Series S | Telegraph services terminal equipment |
+| Series T | Terminals for telematic services |
+| Series U | Telegraph switching |
+| Series V | Data communication over the telephone network |
+| Series X | Data networks, open system communications and security |
+| Series Y | Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities |
+| Series Z | Languages and general software aspects for telecommunication systems |
\ No newline at end of file
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..db3a38c033347284e438d3c46e2d6076a9731f6e
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/08a978a124d3ed6cf1a3d0cfd89418d0_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b99872ab48d68a8ad37d9d342b3b1a072c965da954770493c2ff5545913f5f75
+size 165640
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/0f2a1e4a7b12fe5b8749882ecd636f5c_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/0f2a1e4a7b12fe5b8749882ecd636f5c_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..bc0b7d230aa814ba7ff9ac76ad42df85d1a5e392
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/0f2a1e4a7b12fe5b8749882ecd636f5c_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:b0c7abe2c31f090e1c85560f9d1d8a3f7be583ad8383d32f010ee596b2f00001
+size 5264
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed476c5649e9eff05f321dedca1c27fd9d06292e
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/14a22f23ced8ba1d63ece69861dbaacc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c5d6ca7c564f9ab460a2e13cdcf1238a34c895bc9de4cd17bdb8b7379ec4b288
+size 5530
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..51e404213a852c62852a622b8323af431aa89060
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/5445597cceefaca1ac89e710fe339325_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:da3a8eb5a8ecdc6aad8366379c639207b2a0ff533e31cdd358a81eecac82f8f0
+size 166423
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ab436a3a95630a6d01951b6ad4a063fe884b7874
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/8fa679f79a1bb1f527cba9f29e784e89_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e32c36d24563c259c2bc035cdf58d261c73e6f36ea9e000162c56375c0b4df8c
+size 3110
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..d10e210fc9681951b00a7be5d996ed8b71ff48ab
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/9c6461e1e94afae4dec455e69a2ce152_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:6ea1eff168abaa18ee3e807d158ec9f3e65fe7aec8baddea323140a33197802b
+size 165051
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6e8963c5aa28ec3ba478d5cbad525ffe2b820c31
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/b0d4609bc46c2d88a8318706bb5321f7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7930c93851400e06322e92a6cbb3cfeabf048c7f4689df22eb0e5f8aeabe9d88
+size 20426
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..456a7824257a4f4bb120213fd94030a74b10afe7
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa343546063e2cb39bdc4ce620e72a0246d28b0cc597ffcbcc28ec6a3f43ae02
+size 161088
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b0b1e6b203489d5805750da6f0697b7fecf0dc0c
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/d26959f4514c26ca19c3d6f00da85956_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8dc554f50d327f5fbdb235dde887700d91aae7663aa5fd3e8a3c502d3a09ed20
+size 49469
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..32ffd4d8d8033ee7dab5adfc41585e7c0997a259
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/d4af765160d04ecef538e5066006dc77_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:45e1a68822ed0fa0c28a8a33951f67f7e04444a3a494786a86a113252b52ce9c
+size 201254
diff --git a/marked/M/T-REC-M.3080-202102-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg b/marked/M/T-REC-M.3080-202102-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ed21fe65ace00bbe913373659ca833f5d5766b43
--- /dev/null
+++ b/marked/M/T-REC-M.3080-202102-I_PDF-E/ff7ce44f3fdd51bae7b231f34df07c6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:02bf87cc334cc0ebe54f371c4ecf5955b05b9b2394b7ba684c201abcb9be6d0a
+size 100816
diff --git a/marked/M/T-REC-M.3101-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3101-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..07882e53216010a60e9a65c2269a1383f90fa8f5
--- /dev/null
+++ b/marked/M/T-REC-M.3101-199507-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8d55bc1404a00110e016e59b37c568857c51417048eaede96b71d932cccb62e1
+size 8202
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..50ce836e01a3c0ed06644e7e92f99c9015c3952e
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2b60ebe01f77d22e53da1fbe73083b01_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:1dc3a6dc9e552fc36ac9e91ae7dfe357683e40cd847c97ee41ce3566fff1151a
+size 92910
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0660fa30e9d6f1ad534b453f29e2fc622b3bb938
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2dfa6ac3edfe874f68aa0cbccaa42322_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:e2e3ca2fcbd91ed5602bb990c4cb2a138b0afa2c969f04ebabfd3ff0c5ab1bf9
+size 8209
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7a921feacf2f611e6a965e988b0acd4a15fa69f1
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/2f587210e4f97c32758c5972e2e83d20_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a463e04430965f707b115ee601f4750e864ce43bd7dd32010424abcdb5628cec
+size 85643
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b847031edac4ec46c3fd266f2acfc895585d000d
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/3198cdf0dbe501c46fe0e4073c7d8451_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fda82fa139def1ce33154a37c6f4ce99478665a3daf633135baa03fec0605024
+size 17583
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..96bec7a9b09f511a57049c6b8eb89c36ce619d05
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/364054adcd1b427fa259450e006c6b38_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:8b67b549276b1faef9b7a7a7281920ab561b3e44b54731d98f52d879a6d8ee18
+size 51681
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a6b9d0afa052282eb9cc55f347046f5e043b8b68
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/42f0611a8a2766c986ff45551918ca5d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:34923dfe73207c600215363c98c8b153bf62425c126ce6d41d3f4fdf12925deb
+size 37343
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..49a9c92c2f31b12c610022cf9dfdba2a3e159f7b
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5cc4a2ef554f31ea0577731931007fff_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:4aaa80da370dcafa628800a813a65ddddd9982e5bfa96fd43ac485ca4803e4d1
+size 105937
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..08f6ce9754fd131441b1806577c2f8754080f268
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/5e05915b2a93a3b404422e0966a7c924_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:a8a45275dda135228f4aeacb07f6137e63d85bb46459a985989f5eda0a69bbc0
+size 104294
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..66960163ddd69685525088d448ba53bbf33f94f7
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/76b0cd79baaedd942af4dc42f2e764b8_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be41dd293f59149c05260c189483aff306ff5a8490d4246b287022290cff115f
+size 86786
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..74af7694a11487098ea5e346120e1a36021a0737
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7d3ac32a2b29fb51bebe46677e839d82f5e5e3fd76f93bbff9c5e9ad5b91b653
+size 136210
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e8ab78bc244d66438a3bcfb8d97a9a2d877dcc68
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/c6212a3b14736d6a8c81ace75ae94ccf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d635cb8d02b8fe0452e59771e762553aa108f7daedd95ea7eb4d54961c59a42b
+size 59473
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..26abdca8a68250c2346fc3579041fa8407090cac
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/caeb1637753f79f4cd005eda3768d1d5_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:be4b05e49710a1d241f0efd3817a3153bafcd9cdcd290f668e6d521cdd5ee831
+size 170133
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..5916e73ba7e6ee539cde8c831ce6e0f4001de203
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/cdc21bbfcba380e98ece42e5b8da50bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ae56dd975c72eec94637739d3de1f660819d0a0a6c1fd35d64ce3f648d718757
+size 44395
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..53d590f38cf50cfe454e83430c71cda346ee1d04
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d31b402b650e68c7d6b55d3cf8fda086_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:bfea0b0b7113ad3bce3fd6a5a8ed22916bcd5d8880cbc038b7f7b8dcbde78b82
+size 26462
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..427e8a77c76fa047f0f76a123863cb622e051361
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/d546a282ce562b4930a36fcf2ec3e7b3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f33ecfea31c54e43ec44541e2e9fa53b1818a5536e649c1995a6dc6ad34416c0
+size 119640
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..f674f71d7581e7e841e202251c5bac1fe72af2da
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/dbd4bab54b57e8d1abf80e3de6471130_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c9ae24c0642f98508b7a32fb9a0c63f02fa17327448d2b3989f61324100e4bdc
+size 71249
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..47c98873329e3f6eb11ea04fc894bd6070739f81
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e404de9a69c05473fbd6af28ee32311b_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:cd0c370b88b51feb446caf32a0cd7cc432316aa13ab6c7685401d9060f2c5545
+size 18750
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..8e3d0b52e8b5fb8bdba16f6369c68215c842ae16
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/e5ded42f8e352da02ee86cb55550c45d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5000953ea30efbd99cc4f96fa75495394907fd8a7154d7a10cdd07edcc14d541
+size 43836
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..763641d0988d547169a8f91a0b5eefcb8b4b77ba
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f78d2e126f00fcc5d8d9797ca410cc09_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9db3266039ab4a128387f4e2db0d61c97c566d8041652f5d6534980911b1a02b
+size 23365
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7ab46520c9d0fe27294a8582deaff7fd422806a4
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/f97535cdaa4fe017f4659512f4f78028_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:9a86edd392c0f7b23e7ce794cee43ce7130a20d924f7cae2ce1b84fb848d2ab7
+size 26758
diff --git a/marked/M/T-REC-M.3108.1-199903-I_PDF-E/raw.md b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..36332413b9a630bb1916734f282a71ad86b37940
--- /dev/null
+++ b/marked/M/T-REC-M.3108.1-199903-I_PDF-E/raw.md
@@ -0,0 +1,4095 @@
+
+
+
+
+ITU logo: A globe with the letters ITU and a lightning bolt.
+
+INTERNATIONAL TELECOMMUNICATION UNION
+
+**ITU-T**
+
+**M.3108.1**
+
+TELECOMMUNICATION
+STANDARDIZATION SECTOR
+OF ITU
+
+(03/99)
+
+SERIES M: TMN AND NETWORK MAINTENANCE:
+INTERNATIONAL TRANSMISSION SYSTEMS,
+TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE
+AND LEASED CIRCUITS
+
+Telecommunications management network
+
+---
+
+**Information model for management of leased
+circuit and reconfigurable services**
+
+ITU-T Recommendation M.3108.1
+
+(Previously CCITT Recommendation)
+
+---
+
+# ITU-T M-SERIES RECOMMENDATIONS
+
+# **TMN AND NETWORK MAINTENANCE: INTERNATIONAL TRANSMISSION SYSTEMS, TELEPHONE CIRCUITS, TELEGRAPHY, FACSIMILE AND LEASED CIRCUITS**
+
+| | |
+|---------------------------------------------------------------------------------|----------------------|
+| Introduction and general principles of maintenance and maintenance organization | M.10–M.299 |
+| International transmission systems | M.300–M.559 |
+| International telephone circuits | M.560–M.759 |
+| Common channel signalling systems | M.760–M.799 |
+| International telegraph systems and phototelegraph transmission | M.800–M.899 |
+| International leased group and supergroup links | M.900–M.999 |
+| International leased circuits | M.1000–M.1099 |
+| Mobile telecommunication systems and services | M.1100–M.1199 |
+| International public telephone network | M.1200–M.1299 |
+| International data transmission systems | M.1300–M.1399 |
+| Designations and information exchange | M.1400–M.1999 |
+| International transport network | M.2000–M.2999 |
+| Telecommunications management network | M.3000–M.3599 |
+| Integrated services digital networks | M.3600–M.3999 |
+| Common channel signalling systems | M.4000–M.4999 |
+
+*For further details, please refer to ITU-T List of Recommendations.*
+
+# **INFORMATION MODEL FOR MANAGEMENT OF LEASED CIRCUIT AND RECONFIGURABLE SERVICES**
+
+## **Summary**
+
+This Recommendation provides a GDMO-based information model to support the management of the leased circuit service as outlined in Recommendation M.3208.1. Appendix I provides a protocol-independent version of this information model in "structured" English. Appendix II provides a mapping from the management functions in Recommendation M.3208.1 to the Managed Objects defined in this Recommendation. Appendix III provides a Unified Modelling Language (UML) view of the same information model.
+
+###### **Source**
+
+ITU-T Recommendation M.3108.1 was prepared by ITU-T Study Group 4 (1997-2000) and was approved under the WTSC Resolution No. 1 procedure on the 26th of March 1999.
+
+## FOREWORD
+
+ITU (International Telecommunication Union) is the United Nations Specialized Agency in the field of telecommunications. The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of the ITU. The ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Conference (WTSC), which meets every four years, establishes the topics for study by the ITU-T Study Groups which, in their turn, produce Recommendations on these topics.
+
+The approval of Recommendations by the Members of the ITU-T is covered by the procedure laid down in WTSC Resolution No. 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+### NOTE
+
+In this Recommendation the term *recognized operating agency (ROA)* includes any individual, company, corporation or governmental organization that operates a public correspondence service. The terms *Administration*, *ROA* and *public correspondence* are defined in the *Constitution of the ITU (Geneva, 1992)*.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+The ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. The ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, the ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database.
+
+© ITU 1999
+
+All rights reserved. No part of this publication may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from the ITU.
+
+## CONTENTS
+
+###### Page
+
+| | | |
+|-------|-------------------------------------------------------------------|----|
+| 1 | Scope, purpose and application..... | 1 |
+| 1.1 | Scope..... | 1 |
+| 1.2 | Purpose..... | 1 |
+| 1.3 | Application..... | 1 |
+| 2 | References..... | 1 |
+| 3 | Definitions ..... | 2 |
+| 4 | Abbreviations..... | 2 |
+| 5 | Overview..... | 3 |
+| 5.1 | Generic service request fragment..... | 5 |
+| 5.2 | LCS service request fragment..... | 5 |
+| 5.3 | Link connection service request fragment ..... | 5 |
+| 5.4 | Transport service fragment ..... | 6 |
+| 5.5 | Resource fragment ..... | 6 |
+| 6 | Information model ..... | 8 |
+| 6.1 | Managed objects for generic service request fragment..... | 8 |
+| 6.1.1 | currentServiceRequest ..... | 8 |
+| 6.1.2 | serviceRequestHistoryRecord..... | 10 |
+| 6.1.3 | serviceModifyRequest ..... | 10 |
+| 6.2 | Managed objects for LCS request fragment..... | 11 |
+| 6.2.1 | currentLcsRequest ..... | 11 |
+| 6.2.2 | lcsRequestHistoryRecord ..... | 11 |
+| 6.2.3 | lcsModifyRequest..... | 12 |
+| 6.3 | Managed objects for link connection service request fragment..... | 12 |
+| 6.3.1 | currentLinkConnectionServiceRequest ..... | 12 |
+| 6.3.2 | linkConnectionServiceRequestHistoryRecord ..... | 13 |
+| 6.3.3 | linkConnectionServiceModifyRequest..... | 13 |
+| 6.4 | Managed objects for service fragment ..... | 13 |
+| 6.4.1 | Transport service ..... | 13 |
+| 6.4.2 | lcs..... | 14 |
+| 6.4.3 | linkConnectionService..... | 15 |
+| 6.4.4 | Service Access Domain ..... | 15 |
+| 6.4.5 | Service Access Group..... | 16 |
+| 6.5 | Managed objects for resource fragment..... | 16 |
+| 6.5.1 | Service Access Equipment ..... | 16 |
+
+| | Page |
+|----------------------------------------------------------|-------------|
+| 6.6 Packages..... | 17 |
+| 6.6.1 aliasNameInfoPackage..... | 17 |
+| 6.6.2 aliasNamePackage..... | 17 |
+| 6.6.3 bandwidthInfoPackage..... | 17 |
+| 6.6.4 bandwidthPackage..... | 17 |
+| 6.6.5 customerRequestNumberPackage..... | 17 |
+| 6.6.6 dateOfInstallationPackage..... | 17 |
+| 6.6.7 dailySchedulingInfoPackage..... | 18 |
+| 6.6.8 dailySchedulingCurrentPackage..... | 18 |
+| 6.6.9 diversityInfoPackage..... | 18 |
+| 6.6.10 diversityPackage..... | 18 |
+| 6.6.11 equipmentManufacturerPackage..... | 18 |
+| 6.6.12 equipmentTypePackage..... | 18 |
+| 6.6.13 expectedDateOfInstallationInfoPackage..... | 18 |
+| 6.6.14 expectedDateOfInstallationPackage..... | 19 |
+| 6.6.15 externalSchedulerCurrentPackage..... | 19 |
+| 6.6.16 externalSchedulerInfoPackage..... | 19 |
+| 6.6.17 initialServiceAdministrativeStateInfoPackage..... | 19 |
+| 6.6.18 initialServiceAdministrativeStatePackage..... | 19 |
+| 6.6.19 modelTypePackage..... | 19 |
+| 6.6.20 originatingLocationCPEInfoPackage..... | 19 |
+| 6.6.21 originatingLocationCPEModifyPackage..... | 19 |
+| 6.6.22 originatingLocationCPEPackage..... | 20 |
+| 6.6.23 originatingLocationCPInfoPackage..... | 20 |
+| 6.6.24 originatingLocationInfoPackage..... | 20 |
+| 6.6.25 originatingLocationSapInfoPackage..... | 20 |
+| 6.6.26 originatingLocationSapPackage..... | 20 |
+| 6.6.27 procedurePackage..... | 20 |
+| 6.6.28 quantityInfoPackage..... | 20 |
+| 6.6.29 quantityPackage..... | 20 |
+| 6.6.30 reflectiveOperationalStatePackage..... | 21 |
+| 6.6.31 reflectiveAdministrativeStatePackage..... | 21 |
+| 6.6.32 routeInfoPackage..... | 21 |
+| 6.6.33 routePackage..... | 21 |
+| 6.6.34 serviceAdministrativeStatePackage..... | 21 |
+| 6.6.35 serviceAvailabilityDateInfoPackage..... | 21 |
+| 6.6.36 serviceAvailabilityDatePackage..... | 21 |
+| 6.6.37 serviceCustomerContactPackage..... | 22 |
+| 6.6.38 serviceDescriptionInfoPackage..... | 22 |
+
+| | Page |
+|---------------------------------------------------------|-------------|
+| 6.6.39 serviceDescriptionPackage ..... | 22 |
+| 6.6.40 serviceProviderContactPackage ..... | 22 |
+| 6.6.41 serviceTerminationDateInfoPackage ..... | 22 |
+| 6.6.42 serviceTerminationDatePackage ..... | 22 |
+| 6.6.43 serviceTypeInfoPackage ..... | 22 |
+| 6.6.44 terminatingLocationCPEInfoPackage..... | 23 |
+| 6.6.45 terminatingLocationCPEModifyPackage ..... | 23 |
+| 6.6.46 terminatingLocationCPEPackage ..... | 23 |
+| 6.6.47 terminatingLocationCPInfoPackage ..... | 23 |
+| 6.6.48 terminatingLocationInfoPackage ..... | 23 |
+| 6.6.49 terminatingLocationSapInfoPackage ..... | 23 |
+| 6.6.50 terminatingLocationSapPackage ..... | 23 |
+| 6.6.51 weeklySchedulingInfoPackage ..... | 23 |
+| 6.6.52 weeklySchedulingCurrentPackage ..... | 24 |
+| 6.7 Attributes ..... | 24 |
+| 6.7.1 aliasName ..... | 24 |
+| 6.7.2 bandwidth ..... | 24 |
+| 6.7.3 cp ..... | 24 |
+| 6.7.4 customerRequestNumber..... | 24 |
+| 6.7.5 dateOfInstallation ..... | 25 |
+| 6.7.6 diversity ..... | 25 |
+| 6.7.7 equipmentManufacturer..... | 25 |
+| 6.7.8 equipmentType ..... | 25 |
+| 6.7.9 expectedDateOfInstallation ..... | 25 |
+| 6.7.10 listOfSags..... | 25 |
+| 6.7.11 listOfSaps..... | 26 |
+| 6.7.12 modelType ..... | 26 |
+| 6.7.13 numberOfUnspecifiedSaps ..... | 26 |
+| 6.7.14 originatingLocation..... | 26 |
+| 6.7.15 originatingLocationCP ..... | 26 |
+| 6.7.16 originatingLocationCPE ..... | 26 |
+| 6.7.17 originatingLocationSap..... | 27 |
+| 6.7.18 procedure ..... | 27 |
+| 6.7.19 providerRequestNumber..... | 27 |
+| 6.7.20 quantity ..... | 27 |
+| 6.7.21 requestedInitialServiceAdministrativeState ..... | 27 |
+| 6.7.22 requestReceptionTime ..... | 28 |
+| 6.7.23 requestSequenceNumber ..... | 28 |
+| 6.7.24 route ..... | 28 |
+
+| | Page |
+|--------------------------------------------------------|-------------|
+| 6.7.25 sadId..... | 28 |
+| 6.7.26 sagId..... | 28 |
+| 6.7.27 sagLocation..... | 29 |
+| 6.7.28 serviceAvailabilityDate ..... | 29 |
+| 6.7.29 serviceCustomerContact..... | 29 |
+| 6.7.30 serviceInstance..... | 29 |
+| 6.7.31 serviceProviderContact..... | 29 |
+| 6.7.32 serviceRequestState ..... | 29 |
+| 6.7.33 serviceTerminationDate..... | 30 |
+| 6.7.34 terminatingLocation..... | 30 |
+| 6.7.35 terminatingLocationCP ..... | 30 |
+| 6.7.36 terminatingLocationCPE ..... | 30 |
+| 6.7.37 terminatingLocationSap..... | 30 |
+| 6.8 Error messages ..... | 31 |
+| 6.8.1 addToSagError..... | 31 |
+| 6.8.2 bandwidthUnavailable ..... | 31 |
+| 6.8.3 CreateLCSError ..... | 31 |
+| 6.8.4 createLinkConnectionError ..... | 31 |
+| 6.8.5 createSadError ..... | 31 |
+| 6.8.6 createSagError ..... | 31 |
+| 6.8.7 deleteLCSError ..... | 32 |
+| 6.8.8 deleteLinkConnectionError ..... | 32 |
+| 6.8.9 deleteSadError ..... | 32 |
+| 6.8.10 deleteSagError ..... | 32 |
+| 6.8.11 modifyLCSError ..... | 32 |
+| 6.8.12 removeFromSagError ..... | 32 |
+| 6.8.13 resourcesUnavailable..... | 33 |
+| 6.9 Notifications..... | 33 |
+| 6.9.1 lcsModifyProgressProblemReport..... | 33 |
+| 6.9.2 lcsRequestProgressProblemReport..... | 33 |
+| 6.9.3 linkConnectionModifyProgressProblemReport ..... | 33 |
+| 6.9.4 linkConnectionRequestProgressProblemReport ..... | 33 |
+| 6.10 Actions ..... | 34 |
+| 6.10.1 updateServiceRequest..... | 34 |
+| 6.10.2 AddSapsToSag ..... | 34 |
+| 6.11 Name bindings ..... | 34 |
+| 6.11.1 currentLcsRequest-account..... | 34 |
+| 6.11.2 lcsRequestHistoryRecord-currentLCSRequest..... | 34 |
+
+| | Page |
+|------------------------------------------------------------------------------------------------|-------------|
+| 6.11.3 lcsModifyRequest-lcs ..... | 35 |
+| 6.11.4 currentLinkConnectionServiceRequest-account ..... | 35 |
+| 6.11.5 linkConnectionServiceRequestHistoryRecord-
currentLinkConnectionServiceRequest ..... | 35 |
+| 6.11.6 linkConnectionServiceModifyRequest-linkConnectionService ..... | 35 |
+| 6.11.7 serviceAccessEquipmentView-account ..... | 35 |
+| 6.11.8 linkConnectionService-account ..... | 36 |
+| 6.11.9 lcs-account ..... | 36 |
+| 6.11.10 serviceAccessDomain-account ..... | 36 |
+| 6.11.11 serviceAccessGroup-serviceAccessDomain ..... | 36 |
+| 6.12 ASN.1 syntax ..... | 37 |
+| 6.12.1 Rules of extensibility ..... | 37 |
+| 6.12.2 ASN.1 module ..... | 37 |
+| 7 Functional units ..... | 44 |
+| 7.1 Basic transport service functional unit ..... | 45 |
+| 7.2 Transport service order functional unit ..... | 45 |
+| 7.3 Transport service order history functional unit ..... | 45 |
+| 7.4 Transport service modify functional unit ..... | 45 |
+| 7.5 Transport resource visibility functional unit ..... | 45 |
+| 7.6 Negotiation of functional units ..... | 45 |
+| 8 Conformance ..... | 46 |
+| 8.1 Static conformance ..... | 46 |
+| 8.2 Dynamic conformance ..... | 46 |
+| 8.3 Conformance to managed object definitions ..... | 46 |
+| Appendix I – Protocol-independent object description ..... | 47 |
+| I.1 Generic service request fragment ..... | 48 |
+| I.1.1 currentServiceRequest ..... | 48 |
+| I.1.2 serviceRequestHistoryRecord ..... | 50 |
+| I.1.3 serviceModifyRequest ..... | 52 |
+| I.2 LCS request fragment ..... | 53 |
+| I.2.1 currentLcsRequest ..... | 53 |
+| I.2.2 lcsRequestHistoryRecord ..... | 55 |
+| I.2.3 lcsModifyRequestRecord ..... | 55 |
+
+| | Page | |
+|--------------|---------------------------------------------------------------------|----|
+| I.3 | Link connection service request fragment ..... | 56 |
+| I.3.1 | currentLinkConnectionServiceRequest ..... | 56 |
+| I.3.2 | linkConnectionServiceRequestHistoryRecord ..... | 58 |
+| I.3.3 | linkConnectionServiceModifyRequest..... | 58 |
+| I.4 | Service fragment ..... | 59 |
+| I.4.1 | transportService ..... | 59 |
+| I.4.2 | lcs..... | 60 |
+| I.4.3 | linkConnectionService..... | 61 |
+| I.5 | Reconfigurable service fragment ..... | 62 |
+| I.5.1 | serviceAccessDomain..... | 62 |
+| I.5.2 | serviceAccessGroup ..... | 63 |
+| I.6 | Resource fragment ..... | 64 |
+| I.6.1 | serviceAccessEquipment ..... | 64 |
+| Appendix II | – Mapping of M.3208.1 functions into M.3108.1 MOs ..... | 65 |
+| Appendix III | – UML diagrams for leased circuit service object model ..... | 68 |
+| III.1 | Introduction..... | 68 |
+| III.2 | UML class diagrams for inheritance of M.3208.1 object classes ..... | 68 |
+| III.3 | UML class diagrams for modelling relationships ..... | 70 |
+| III.4 | UML class diagrams for modelling agent functionality..... | 72 |
+| III.5 | UML sequence diagrams to illustrate scenarios of object usage ..... | 73 |
+
+###### Recommendation M.3108.1
+
+# INFORMATION MODEL FOR MANAGEMENT OF LEASED CIRCUIT AND RECONFIGURABLE SERVICES
+
+(Geneva, 1999)
+
+# 1 Scope, purpose and application
+
+## 1.1 Scope
+
+This Recommendation provides a GDMO-based information model to support the management of the leased circuit service as outlined in Recommendation M.3208.1. Appendix I provides a protocol-independent version of this information model in "structured" English. Appendix II provides a mapping from the management functions in Recommendation M.3208.1 to the managed objects defined in this Recommendation. Appendix III provides a Unified Modelling Language (UML) view of the same information model.
+
+## 1.2 Purpose
+
+The purpose of this Recommendation is to support standard interfaces, across the X interface, among service customers, service providers and network providers for the purposes of managing leased circuit services in the service management layer of the TMN. It specifically intended to support the requirements provided in Recommendation M.3208.1.
+
+## 1.3 Application
+
+This Recommendation is applicable to interfaces between systems that participate in the ordering and management of leased circuit services.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; all users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published.
+
+- ITU-T Recommendation G.805 (1995), *Generic functional architecture of transport networks*.
+- ITU-T Recommendation M.3010 (1996), *Principles for a telecommunications management network*.
+- ITU-T Recommendation M.3100 (1995), *Generic network information model*.
+- ITU-T Recommendation M.3200 (1997), *TMN management services and telecommunications managed areas: Overview*.
+- ITU-T Recommendation M.3208.1 (1997), *TMN management services for dedicated and reconfigurable circuits network: Leased circuit services*.
+- ITU-T Recommendation M.3400 (1997), *TMN management functions*.
+
+- ITU-T Recommendation Q.821 (1993), *Stage 2 and stage 3 description for the Q3 interface – Alarm surveillance.*
+- CCITT Recommendation X.721 (1992) | ISO/IEC 10165-2:1992, *Information technology – Open Systems Interconnection – Structure of management information: Definition of management information.*
+- CCITT Recommendation X.734 (1992) | ISO/IEC 10164-5:1993, *Information technology – Open Systems Interconnection – Systems management: Event report management function.*
+- CCITT Recommendation X.735 (1992) | ISO/IEC 10164-6:1993, *Information technology – Open Systems Interconnection – Systems management: Log control function.*
+- ITU-T Recommendation X.746 (1995) | ISO/IEC 10164-15:1995, *Information technology – Open Systems Interconnection – Systems management: Scheduling function.*
+- ITU-T Recommendation X.790 (1995), *Trouble management function for ITU-T applications.*
+
+# 3 Definitions
+
+This Recommendation uses the definitions provided in Recommendation M.3208.1.
+
+# 4 Abbreviations
+
+This Recommendation uses the following abbreviations:
+
+| | |
+|------|----------------------------------------------------------|
+| AP | Access Point |
+| ATM | Asynchronous Transfer Mode |
+| CP | Connection Point |
+| CPE | Customer Premises Equipment |
+| GDMS | Guidelines for the Definition of TMN Management Services |
+| LC | Link Connection |
+| LCS | Leased Circuit Service |
+| MS | Management Services |
+| NML | Network level Management Layer |
+| PDH | Plesiochronous Digital Hierarchy |
+| SAD | Service Access Domain |
+| SAG | Service Access Group |
+| SC | Service Customer |
+| SDH | Synchronous Digital Hierarchy |
+| SML | Service level Management Layer |
+| SN | Service Node |
+| SNC | Sub-Network Connection |
+| SP | Service Provider |
+| TCP | Termination Connection Point |
+
+TMN Telecommunications Management Network
+
+UML Unified Modelling Language
+
+# 5 Overview
+
+This clause provides an overview of the information model and its use in the management of LCS. Clause 6 provides the formal definition of the GDMO-based information model.
+
+The information model consists of five fragments:
+
+- Generic service request – contains generic MOs to be used for subclassing MOs in support of specific services.
+- LCS service request – supports the service request process for LCS.
+- Link connection service request – supports the service request process for link connection service.
+- Transport service – represents transport services, supports SC's management of provisioned services.
+- Resources – represents resources used for the provisioning of LCS and link connection service.
+
+The first four are defined in this Recommendation. The fifth also includes information elements defined in other Recommendations, such as Recommendations M.3100 and G.855.1.
+
+The management of a LCS or a link connection service starts when a Service Customer (SC) requests the service. This can be achieved by the SC creating an instance of a subclass of transportService MO, or the SC creates an instance of a subclass of currentServiceRequest MO. More specifically, the created object is an instance of one of the following MO classes:
+
+- lcs;
+- linkConnectionService;
+- currentLcsRequest;
+- currentLinkConnectionService.
+
+The first two bullets above correspond to instant service provisioning, without going through the service request process. The last two bullets above correspond to the case where the SC's request goes through the service request process.
+
+The request must satisfy the terms of the Service Level Agreement (SLA) between the SC and the SP.
+
+The following scenario applies when the request proceeds through the service request process. The Service Provider (SP), assuming the Agent role, creates an instance of a (subclass of) currentServiceRequest MO. Upon creation of this MO instance the SP fills in the values of some of the attributes, as specified in Recommendation M.3208.1 (e.g. the actual due date for the service). The SP then sends a create reply regarding that creation to the SC, assuming the Manager role. The create reply includes the values of the attributes that must be communicated by the SP to the SC in response to the service request, as per Recommendation M.3208.1. If the SC has created an instance of a (subclass of) currentServiceRequest MO, then the SC can update the request through the updateServiceRequest action, e.g. the SC may request a change to the date when the service is desired, or a different route. The SC may also cancel the initial request by deleting the currentServiceRequest. The (subclasses of) currentServiceRequest represent the current view of the service request. In order to keep track of the modifications issued by the SC, the SP may create (subject to SLA) instances of (a subclass of) serviceRequestHistoryRecord that represent the values
+
+of the attributes requested to be modified by specific updateServiceRequest action. The first instance of serviceRequestHistoryRecord created for a specific service request represents the values of the attributes of the initial service request. The values of the currentServiceRequest may be different from the values requested by the SC due to changes made by the SP (and reported to the SC).
+
+After the requested LCS or link connection service has been implemented by the SP, the SP instantiates an instance of the lcs or linkConnectionService MO. Both are subclasses of the transportService MO. More specifically, the SP creates an instance of one of the following MO classes:
+
+- linkConnectionService;
+- lcs.
+
+The SP then informs the SC of the availability of the requested service through a notification of the creation of an instance of a MO representing that service.
+
+In some cases the SP may provide the requested service instantaneously, even though formally it goes through the service request process. In this case the SP will send the SC three consecutive notifications: for the creation of a service create request record, for the deletion of the just created service create request record, and for the creation of the requested service. In this case the service create request record is purely transient and the SC does not interact with it. This scenario applies when the SC initiates the request through the service request process. If the SP represents to provide requested LCS or link connection service instantaneously, then another scenario is also possible: the SC skips the service request process and requests the service by issuing a "create an instance of" (a subclass of) transportService.
+
+After the SC has been notified about the creation of that MO (a subclass of transportService), the SC can modify the service through management operations for some attributes. For other attributes the modification is done by creating an instance of the modifyRequestRecord MO class, referring to the lcs or linkConnectionService MO instance. The SP may choose to require that an instance of serviceModifyRequest MO be created every time the SC wishes to make changes to any attributes of the service.
+
+An instance of a (subclass of) transportService MO class may refer to instances of serviceAccessEquipmentView MO classes (representing CPE) and/or instances of MO classes corresponding to topological elements such as link, connection point and subnetwork.
+
+An instance of the networkR1 MO is used for naming. All entries in that MO instance can be changed only by the SP, though the SC can read (GET) such information.
+
+An instance of the account MO class (imported from Recommendation X.790) contains information regarding the SC, such as the SC's contact information. In general, only the SC can set information in the account MO. The account MO is contained in the network MO (imported from Recommendation M.3100).
+
+The SC can create an instance of a serviceAccessDomain MO class. A serviceAccessDomain contains zero or more serviceAccessGroups, though a serviceAccessDomain containing less than two serviceAccessGroups is not very useful. The SC can create instances of serviceAccessGroup MO class. A serviceAccessGroup MO contains zero or more SAPs. A serviceAccessGroup is created without any SAPs. After creation of a serviceAccessGroup, the SC can add or remove SAPs from the serviceAccessGroup. The SC can identify some or all of the SAPs desired in a serviceAccessGroup. If the SC adds to a serviceAccessGroup more SAPs than are explicitly identified, then the SP assigns additional SAPs, from the same service location to the serviceAccessGroup, and informs the SC about the identity of those SAPs. The SC can add or remove SAPs from a serviceAccessGroup through management operations. If the two SAPs corresponding to a LCS belong to
+
+serviceAccessGroups that are members of the same serviceAccessDomain, then the LCS is a reconfigurable LCS. This is usually also reflected in the service name and service type of the LCS.
+
+## 5.1 Generic service request fragment
+
+The (generic) service request MOs are not instantiable. They are used as superclasses for service-specific, instantiable MOs. As such the generic MOs can be reused to define instantiable MOs for other services. The LCS and link connection service requests instantiable MOs are derived from the generic ones.
+
+The generic service request fragment consists of MOs that support the request of a service as well as updates to service requests and modifications to existing services. It defines three generic, non-instantiable, classes:
+
+- currentServiceRequest;
+- serviceRequestHistoryRecord;
+- serviceModifyRequest.
+
+The currentServiceRequest represents the up-to-date values of the attributes describing the requested service. Those values may be different from those in the initial service request due to subsequent changes requested by the SC or introduced by the SP. Indeed, the SP may replace the values of some attributes (e.g. if the available bandwidth does not match the bandwidth requested by the SC). The SLA may specify that the service request history is kept through (subclasses of) serviceRequestHistoryRecord. Several instances of serviceRequestHistoryRecord may be created. The first instance of serviceRequestHistoryRecord represents the SC initial request for service. Subsequently created instances represent changes to the request submitted by the SC.
+
+If there is a large number of updates, it may not be clear what the SC really wants. To this end the SP may create an instance of a currentServiceRequest MO class. This is a generic, non-instantiable class that represents the current information about what the SC wants. It is derived from serviceCreateRequestRecord, though the values of its attributes are updated (by the SP) whenever a new serviceUpdateRequestRecord is received. When this happens it sends an attribute value change notification to the SC, thus keeping the SC updated. The SC can inquire about the current information in the request by retrieving values of attributes of the currentServiceRequest.
+
+After the requested service has been created, the SC can modify that service through management operations or by creating instances of (a subclass of) serviceModifyRequest MO class. As in the case of service request, the SC may issue management operations against the MO representing the service instead of creating new instances of serviceModifyRequest. In that case the SP may keep a log of the management operations issued by the SC to update attributes in the MO representing the service. (The mechanism for such storage is outside the scope of this Recommendation.)
+
+Instantiable, service-specific MO classes are derived from the MOs in this fragment.
+
+## 5.2 LCS service request fragment
+
+The MO classes in this fragment consist of LCS-specific subclasses of the MO classes in the generic service request fragment.
+
+## 5.3 Link connection service request fragment
+
+The MO classes in this fragment consist of link connection service-specific subclasses of the MO classes in the generic service request fragment.
+
+## 5.4 Transport service fragment
+
+The transport service fragment contains a generic, non-instantiable MO transportService from which two instantiable MOs are derived: lcs and linkConnectionService.
+
+This fragment further contains two objects representing serviceAccessGroup and serviceAccessDomain. Those instantiable objects allow the SC to manage the existing services through management operations directed at the corresponding objects. This is a plausible alternative to the management of existing services through the creation of serviceModifyRequestRecord MOs.
+
+## 5.5 Resource fragment
+
+The resource fragment contains two MOs that represent physical resources and which are needed in some aspects of LCS management: network, as defined in Recommendation M.3100, and serviceAccessEquipment, which is defined in this Recommendation. It further includes MOs that would be defined in support of elements in Recommendation G.805 corresponding to topological entities (link, connectionPoint, subNetwork). Those MOs allow the SP to offer the SC a more detailed view of how the service is provisioned.
+
+Figures 5-1 and 5-2 represent the inheritance and containment relationships of the MOs respectively. Inheritance and containment are not shown for all the MOs that are imported from other Recommendations. Figure 5-2 does not show the containment of the M.3100 network MO in directory objects as specified in Recommendation M.3100.
+
+This Recommendation defines six Functional Units (FUs):
+
+- Service order;
+- Service modify;
+- Leased circuit service;
+- Link connection service;
+- Reconfigurable circuit service;
+- Resource visibility.
+
+These FUs cover the management functions defined in Recommendation M.3208.1. This Recommendation provides a mapping of the M.3208.1 functions into the FUs and specifies the MOs required for each of the FUs.
+
+
+
+```
+
+classDiagram
+ class top_X721_top [top (X.721)]
+ class Generic_service_request_fragment [Generic service request fragment]
+ class Account_X790 [Account (X.790)]
+ class currentServiceRequest
+ class serviceRequestHistoryRecord
+ class serviceModifyRequest
+ class Link_connection_service_request_fragment [Link connection service request fragment]
+ class currentLinkConnectionServiceRequest
+ class linkConnectionServiceRequestHistoryRecord
+ class linkConnectionServiceModifyRequest
+ class LCS_service_request_fragment [LCS service request fragment]
+ class currentLcsRequest
+ class lcsRequestHistoryRecord
+ class lcsModifyRequest
+ class transport_service_request_fragment [transport service request fragment]
+ class serviceAccessGroup
+ class serviceAccessDomain
+ class transportService
+ class lcs
+ class linkConnectionService
+ class resource_fragment [resource fragment]
+ class serviceAccessEquipment
+ class networkR1_M3100 [networkR1 (M.3100)]
+
+ top_X721_top --- Generic_service_request_fragment
+ top_X721_top --- Account_X790
+ top_X721_top --- Link_connection_service_request_fragment
+ top_X721_top --- LCS_service_request_fragment
+ top_X721_top --- transport_service_request_fragment
+ top_X721_top --- resource_fragment
+
+ Generic_service_request_fragment --- currentServiceRequest
+ Generic_service_request_fragment --- serviceRequestHistoryRecord
+ Generic_service_request_fragment --- serviceModifyRequest
+
+ Link_connection_service_request_fragment --- currentLinkConnectionServiceRequest
+ Link_connection_service_request_fragment --- linkConnectionServiceRequestHistoryRecord
+ Link_connection_service_request_fragment --- linkConnectionServiceModifyRequest
+
+ LCS_service_request_fragment --- currentLcsRequest
+ LCS_service_request_fragment --- lcsRequestHistoryRecord
+ LCS_service_request_fragment --- lcsModifyRequest
+
+ transport_service_request_fragment --- serviceAccessGroup
+ transport_service_request_fragment --- serviceAccessDomain
+ transport_service_request_fragment --- transportService
+ transport_service_request_fragment --- lcs
+ transport_service_request_fragment --- linkConnectionService
+
+ resource_fragment --- serviceAccessEquipment
+ resource_fragment --- networkR1_M3100
+
+```
+
+UML class diagram showing inheritance relationships between service request fragments and resource fragments. The diagram is structured into three main horizontal sections. The top section, labeled 'top (X.721)', contains three gray boxes: 'Generic service request fragment' (with sub-classes 'currentServiceRequest', 'serviceRequestHistoryRecord', and 'serviceModifyRequest'), 'Link connection service request fragment' (with sub-classes 'currentLinkConnectionServiceRequest', 'linkConnectionServiceRequestHistoryRecord', and 'linkConnectionServiceModifyRequest'), and 'LCS service request fragment' (with sub-classes 'currentLcsRequest', 'lcsRequestHistoryRecord', and 'lcsModifyRequest'). A separate box labeled 'Account (X.790)' is also in this section. The bottom section contains two gray boxes: 'transport service request fragment' (with sub-classes 'serviceAccessGroup', 'serviceAccessDomain', 'transportService', 'lcs', and 'linkConnectionService') and 'resource fragment' (with sub-classes 'serviceAccessEquipment' and 'networkR1 (M.3100)'). Lines connect the sub-classes to their parent fragments and to the 'top (X.721)' box.
+
+T0410050-98
+
+**Figure 5-1/M.3108.1 – Inheritance**
+
+
+
+```
+
+graph TD
+ networkR1["networkR1 (M.3100)"]
+ account["account (X.790)"]
+ currentLCSRequest["currentLCSRequest"]
+ currentLinkConnectionServiceRequest["currentLinkConnectionService Request"]
+ serviceAccessEquipment["serviceAccess Equipment"]
+ linkConnectionService["LinkConnection Service"]
+ lcs["lcs"]
+ lcsRequestHistoryRecord["lcsRequestHistory Record"]
+ linkConnectionServiceRequestHistoryRecord["LinkConnectionService RequestHistoryRecord"]
+ linkConnectionServiceModifyRequest["LinkConnectionService ModifyRequest"]
+ serviceAccessDomain["serviceAccessDomain"]
+ lcsModifyRequest["lcsModifyRequest"]
+ serviceAccessGroup["serviceAccessGroup"]
+ otherMOs["other MOs describing resources and defined elsewhere"]
+
+ networkR1 --> account
+ account --> currentLCSRequest
+ account --> currentLinkConnectionServiceRequest
+ account --> serviceAccessEquipment
+ account --> linkConnectionService
+ account --> lcs
+ currentLCSRequest --> lcsRequestHistoryRecord
+ currentLinkConnectionServiceRequest --> linkConnectionServiceRequestHistoryRecord
+ linkConnectionService --> linkConnectionServiceModifyRequest
+ lcs --> lcsModifyRequest
+ serviceAccessGroup --> serviceAccessDomain
+ serviceAccessDomain --> account
+ otherMOs -.-> networkR1
+ otherMOs -.-> account
+
+```
+
+T0410060-98
+
+Containment diagram for networkR1 (M.3100) and account (X.790) showing various managed objects and their relationships.
+
+**Figure 5-2/M.3108.1 – Containment**
+
+# 6 Information model
+
+This clause provides the information model for the management of LCS using GDMO.
+
+The objects are grouped by fragment.
+
+## 6.1 Managed objects for generic service request fragment
+
+### 6.1.1 currentServiceRequest
+
+```
+
+currentServiceRequest MANAGED OBJECT CLASS
+ DERIVED FROM "Rec. X.721|ISO/IEC 10165-2:1992":top;
+ CHARACTERIZED BY
+ serviceRequestPackage PACKAGE
+ BEHAVIOUR
+ currentServiceRequestBehaviour BEHAVIOUR
+ DEFINED AS
+
+```
+
+"The currentServiceRequest MO class represents information elements that are common to all service requests and captures the current value of a service request. It is a superclass from which service-specific subclasses can be defined.
+
+This MO represents the current view of the values of the service request that the SP will process on behalf of the SC. They may be different from the values requested by the SC due to the availability or lack thereof of SP's resources.
+
+The updateServiceRequest action can be used by the service customer to modify the service request following creation of this object class (or subclasses). The following attributes specified in this object class can be modified by the updateServiceRequest action:
+
+- serviceCustomer contact;
+- serviceAvailabilityDate;
+- serviceTerminationDate;
+- initialServiceAdministrativeState;
+- aliasName;
+- intervalsOfDay;
+- weekMask.
+
+Subclasses of this object class can specify additional attributes that can be modified by the updateServiceRequest action.
+
+It is the responsibility of the SC to check the values of the attributes in the create notification and attribute value change notification emitted by this MO. If the values of any attributes in the notifications are different from those supplied by the SC, and if they are unacceptable to the SC, then the SC may cancel the service request by deleting this object.
+
+If the history of the requested values is to be kept by the SP, then a serviceRequestHistoryRecord is created when the service customer issues an updateServiceRequest action towards a currentServiceRequest (and subclasses); the serviceRequestHistoryRecord contains a record of the attribute values specified in the request. The SP also creates a serviceRequestHistoryRecord of the initial service request values (when the SC creates the currentServiceRequest).";;
+
+#### ATTRIBUTES
+
+| | | |
+|--------------------------|--------------------|------------------------------------|
+| providerRequestNumber | GET, | -- used as naming attribute |
+| requestSequenceNumber | GET, | |
+| requestReceptionTime | GET, | |
+| "Rec. X.790":serviceType | GET SET-BY-CREATE, | |
+| serviceProviderContact | GET, | |
+| serviceCustomerContact | GET SET-BY-CREATE, | |
+| serviceAvailabilityDate | GET SET-BY-CREATE, | |
+| serviceTerminationDate | GET SET-BY-CREATE, | |
+| serviceRequestState | GET; | |
+
+*-- this attribute represents the service request state*
+
+*-- defined in Rec. M.3208.1 and behaves according to the*
+
+*-- state model*
+
+##### ACTIONS
+
+updateServiceRequest;
+
+#### NOTIFICATIONS
+
+"Rec.X.721 | ISO/IEC 10165-2:1992": attributeValueChange,
+
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion;;;
+
+#### CONDITIONAL PACKAGES
+
+| | |
+|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------|
+| initialServiceAdministrativeStatePackage | PRESENT IF "SLA supports it", |
+| serviceDescriptionPackage | PRESENT IF "SLA supports it", |
+| -- represents the service class in Rec. M.3208.1 | |
+| customerRequestNumberPackage | PRESENT IF "SC provides it", |
+| aliasNamePackage | PRESENT IF "SLA supports it", |
+| "Rec. X.721":availabilityStatus | PRESENT IF "Any scheduling (daily, weekly, external) is present", |
+| dailySchedulingCurrentPackage | |
+| PRESENT IF "both the weekly scheduling current package and external scheduler current packages are not present and daily scheduling is supported for the requested service", | |
+| weeklySchedulingCurrentPackage | |
+| PRESENT IF "both the daily scheduling current package and external scheduler current packages are not present and weekly scheduling is supported for the requested service", | |
+| externalSchedulerCurrentPackage | |
+| PRESENT IF "both the daily scheduling current package and weekly scheduling current packages are not present and external scheduling is supported for the requested service"; | |
+
+REGISTERED AS {m3108Part1ObjectClass 1};
+
+### 6.1.2 serviceRequestHistoryRecord
+
+serviceRequestHistoryRecord MANAGED OBJECT CLASS
+DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top;
+CHARACTERIZED BY
+serviceRequestHistoryRecordPackage PACKAGE
+BEHAVIOUR
+serviceRequestRecordBehaviour BEHAVIOUR
+DEFINED AS
+"This MO represents a history record of the content of a service (update) request by the SC to a service request. The serviceRequestHistoryRecord is created when the service customer issues an updateServiceRequest action towards a currentServiceRequest (and subclasses) and contains a record of the attribute values specified in the request. The service provider also creates a serviceRequestHistoryRecord of the initial service request values (when the SC creates the currentServiceRequest).";;
+ATTRIBUTES
+requestSequenceNumber GET, -- used as naming attribute
+requestReceptionTime GET;
+NOTIFICATIONS
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectCreation,
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion;;;
+CONDITIONAL PACKAGES
+aliasNameInfoPackage PRESENT IF "part of the service (update) request",
+dailySchedulingInfoPackage PRESENT IF "part of the service (update) request",
+externalSchedulerInfoPackage PRESENT IF "part of the service (update) request",
+initialServiceAdministrativeStateInfoPackage
+PRESENT IF "part of the service (update) request",
+serviceAvailabilityDateInfoPackage PRESENT IF "part of the service (update) request",
+serviceCustomerContactPackage PRESENT IF "part of the service (update) request",
+serviceDescriptionInfoPackage PRESENT IF "part of the service (update) request",
+serviceTypeInfoPackage PRESENT IF "part of the service (update) request",
+serviceTerminationDateInfoPackage PRESENT IF "part of the service (update) request",
+weeklySchedulingInfoPackage PRESENT IF "part of the service (update) request";;
+REGISTERED AS {m3108Part1ObjectClass 2};
+
+### 6.1.3 serviceModifyRequest
+
+serviceModifyRequest MANAGED OBJECT CLASS
+DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top;
+CHARACTERIZED BY
+serviceModifyRequestPackage PACKAGE
+BEHAVIOUR
+serviceModifyRequestBehaviour BEHAVIOUR
+DEFINED AS "This MO represents SC's request to modify an existing service. It is a superclass from which service-specific subclasses are derived. When changes to the service occur as a result of such a modification request, or for any other reason, the MO representing the affected service (e.g. lcs or link connection service) will issue the appropriate attribute value change notifications. After all the modifications requested by the SC through this MO have been resolved, this MO instance will be deleted and a notification of its deletion shall be sent to the SC.";;
+ATTRIBUTES
+providerRequestNumber GET, -- used as naming attribute
+serviceRequestState GET,
+serviceInstance GET SET-BY-CREATE,
+requestReceptionTime GET;
+NOTIFICATIONS
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion,
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectCreation;;;
+CONDITIONAL PACKAGES
+aliasNamePackage
+PRESENT IF "SLA supports it",
+
+```
+
+"Rec. X.721":availabilityStatus PRESENT IF "Any scheduling (daily, weekly, external) is
+ present",
+dailySchedulingCurrentPackage
+ PRESENT IF "both the weekly scheduling current package and external scheduler current packages are not
+ present and daily scheduling is supported for the requested service",
+externalSchedulerCurrentPackage
+ PRESENT IF "both the daily scheduling current package and weekly scheduling current packages are not
+ present and external scheduling is supported for the requested service",
+serviceCustomerContactPackage
+ PRESENT IF "SLA supports it",
+weeklySchedulingCurrentPackage
+ PRESENT IF "both the daily scheduling current package and external scheduler current packages are not
+ present and weekly scheduling is supported for the requested service";
+REGISTERED AS {m3108Part1ObjectClass 3};
+
+```
+
+## 6.2 Managed objects for LCS request fragment
+
+### 6.2.1 currentLcsRequest
+
+```
+
+currentLcsRequest MANAGED OBJECT CLASS
+DERIVED FROM currentServiceRequest;
+CHARACTERIZED BY
+ currentLcsRequestPackage PACKAGE
+ BEHAVIOUR
+ currentLcsRequestBehaviour BEHAVIOUR
+ DEFINED AS "This MO represents the LCS the SC currently wants, as per the SC's create service request
+ and subsequent updates related to that create service request.";;
+ ATTRIBUTES
+ originatingLocation GET SET-BY-CREATE,
+ terminatingLocation GET SET-BY-CREATE;
+ ACTIONS
+ updateServiceRequest
+ bandwidthUnavailable
+ modifyLCSError
+ resourcesUnavailable;
+ NOTIFICATIONS
+ lcsRequestProgressProblemReport;;
+ -- used to report problems in progressing the request.
+ -- changes in the value of the serviceRequestState are
+ -- reported using the attribute value change notification.
+ CONDITIONAL PACKAGES
+ quantityPackage PRESENT IF "SLA supports it",
+ bandwidthPackage PRESENT IF "SLA supports it",
+ diversityPackage PRESENT IF "SLA supports it",
+ routePackage PRESENT IF "SLA supports it",
+ originatingLocationCPEPackage PRESENT IF "SLA supports it",
+ terminatingLocationCPEPackage PRESENT IF "SLA supports it",
+ originatingLocationSapPackage PRESENT IF "SLA supports it",
+ terminatingLocationSapPackage PRESENT IF "SLA supports it";
+REGISTERED AS {m3108Part1ObjectClass 4};
+
+```
+
+### 6.2.2 lcsRequestHistoryRecord
+
+```
+
+lcsRequestHistoryRecord MANAGED OBJECT CLASS
+DERIVED FROM serviceRequestHistoryRecord;
+CHARACTERIZED BY
+ lcsRequestHistoryRecordPackage PACKAGE
+ BEHAVIOUR
+ lcsRequestHistoryRecordBehaviour BEHAVIOUR
+
+```
+
+DEFINED AS "This MO represents a record of the attributes of a create or update request of a LCS.";;;
+
+#### **CONDITIONAL PACKAGES**
+
+| | |
+|-----------------------------------|----------------------------------------------------|
+| originatingLocationInfoPackage | PRESENT IF "part of the service (update) request", |
+| terminatingLocationInfoPackage | PRESENT IF "part of the service (update) request", |
+| quantityInfoPackage | PRESENT IF "part of the service (update) request", |
+| bandwidthInfoPackage | PRESENT IF "part of the service (update) request", |
+| diversityInfoPackage | PRESENT IF "part of the service (update) request", |
+| routeInfoPackage | PRESENT IF "part of the service (update) request", |
+| originatingLocationCPEInfoPackage | PRESENT IF "part of the service (update) request", |
+| terminatingLocationCPEInfoPackage | PRESENT IF "part of the service (update) request", |
+| originatingLocationSapInfoPackage | PRESENT IF "part of the service (update) request", |
+| terminatingLocationSapInfoPackage | PRESENT IF "part of the service (update) request"; |
+
+REGISTERED AS {m3108Part1ObjectClass 5};
+
+### 6.2.3 lcsModifyRequest
+
+lcsModifyRequest MANAGED OBJECT CLASS
+
+DERIVED FROM serviceModifyRequest;
+
+CHARACTERIZED BY
+
+lcsModifyRequestPackage PACKAGE
+
+BEHAVIOUR
+
+lcsModifyRequestBehaviour BEHAVIOUR
+
+DEFINED AS "This MO represents a request to modify an existing LCS service or a previous modify against an LCS.";;
+
+NOTIFICATIONS
+
+lcsModifyProgressProblemReport;;
+
+-- used to report problems in progressing the request.
+
+-- changes in the value of the serviceRequestState are
+
+-- reported using the attribute value change notification.
+
+#### **CONDITIONAL PACKAGES**
+
+| | |
+|-------------------------------|-------------------------------|
+| bandwidthPackage | PRESENT IF "SLA supports it", |
+| diversityPackage | PRESENT IF "SLA supports it", |
+| routePackage | PRESENT IF "SLA supports it", |
+| originatingLocationCPEPackage | PRESENT IF "SLA supports it", |
+| terminatingLocationCPEPackage | PRESENT IF "SLA supports it"; |
+
+REGISTERED AS {m3108Part1ObjectClass 6};
+
+## 6.3 Managed objects for link connection service request fragment
+
+### 6.3.1 currentLinkConnectionServiceRequest
+
+currentLinkConnectionServiceRequest MANAGED OBJECT CLASS
+
+DERIVED FROM currentServiceRequest;
+
+CHARACTERIZED BY
+
+currentLinkConnectionServiceRequestPackage PACKAGE
+
+BEHAVIOUR
+
+currentLinkConnectionServiceRequestBehaviour BEHAVIOUR
+
+DEFINED AS "This instantiable MO represents a SC's request for a link connection service.
+
+The following attributes specified by this object class (in addition to those inherited from currentServiceRequest) can be modified by the service customer using the updateServiceRequest action:
+
+- bandwidth
+- originatingLocationCP
+- terminationLocationCP
+
+The SC must provide either the Originating or Terminating Location Connection Point or both. If one of the points is at the customer premises, that point must be provided by the SC. If one of the points is in a network of a service provider other than the one receiving create request, it must be provided by the SC.";;
+
+#### ATTRIBUTES
+
+originatingLocationCP GET SET-BY-CREATE,
+terminatingLocationCP GET SET-BY-CREATE;
+
+##### ACTIONS
+
+updateServiceRequest
+ bandwidthUnavailable -- *specific action reply parameter values*
+ resourcesUnavailable;
+
+#### NOTIFICATIONS
+
+linkConnectionRequestProgressProblemReport;;;
+ -- *used to report problems in progressing the request.*
+ -- *changes in the value of the serviceRequestState are*
+ -- *reported using the attribute value change notification.*
+
+#### CONDITIONAL PACKAGES
+
+bandwidthPackage PRESENT IF "SLA supports it";
+REGISTERED AS {m3108Part1ObjectClass 7};
+
+### 6.3.2 linkConnectionServiceRequestHistoryRecord
+
+linkConnectionServiceRequestHistoryRecord MANAGED OBJECT CLASS
+
+DERIVED FROM serviceRequestHistoryRecord;
+
+#### CHARACTERIZED BY
+
+linkConnectionServiceRequestHistoryRecordPackage PACKAGE
+
+#### BEHAVIOUR
+
+linkConnectionServiceRequestHistoryRecordBehaviour
+
+BEHAVIOUR DEFINED AS "This MO represents a request to update either a previously issued request to create a link connection service, or a previous update against that link connection service request.";;;
+
+#### CONDITIONAL PACKAGES
+
+bandwidthInfoPackage PRESENT IF "part of the service (update) request",
+originatingLocationCPInfoPackage PRESENT IF "part of the service (update) request",
+terminatingLocationCPInfoPackage PRESENT IF "part of the service (update) request";
+
+REGISTERED AS {m3108Part1ObjectClass 8};
+
+### 6.3.3 linkConnectionServiceModifyRequest
+
+linkConnectionServiceModifyRequest MANAGED OBJECT CLASS
+
+DERIVED FROM serviceModifyRequest;
+
+#### CHARACTERIZED BY
+
+linkConnectionServiceModifyRequestPackage PACKAGE
+
+#### BEHAVIOUR
+
+linkConnectionServiceModifyRequestBehaviour BEHAVIOUR
+
+DEFINED AS "This MO represents a request to modify an existing link connection service or a previous modify against a link.";;;
+
+#### NOTIFICATIONS
+
+linkConnectionModifyProgressProblemReport;;;
+
+#### CONDITIONAL PACKAGES
+
+bandwidthPackage PRESENT IF "SLA supports it";
+
+REGISTERED AS {m3108Part1ObjectClass 9};
+
+## 6.4 Managed objects for service fragment
+
+### 6.4.1 Transport service
+
+transportService MANAGED OBJECT CLASS
+
+DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top;
+
+#### CHARACTERIZED BY
+
+"Rec. M.3100:1995":administrativeOperationalStatesPackage,
+"Rec. M.3100:1995":stateChangeNotificationPackage,
+"Rec. M.3100:1995":createDeleteNotificationsPackage,
+"Rec. M.3100:1995":attributeValueChangeNotificationPackage,
+
+```
+
+transportServicePackage PACKAGE
+ BEHAVIOUR
+ transportServiceBehaviour BEHAVIOUR
+ DEFINED AS "This MO represents a transport service. This MO class cannot be instantiated; service-
+ specific subclasses of this class can be instantiated. Values of attributes of subclasses of this MO class
+ can be set through management operations or through the creation of an instance of a service-specific
+ subclass of the serviceModifyRequest MO class. If an attribute is supported by the SLA, and it can be
+ set by the SC, and the SC has not specified its value in the service request, then it shall have its default
+ value when this MO is instantiated.";;
+ ATTRIBUTES
+ "Rec. X.790":serviceID GET SET-BY-CREATE,
+ -- represents the circuit ID or link connection ID specified in Rec. M.3208.1
+ -- the serviceID is used for naming
+ serviceTerminationDate GET-REPLACE,
+ bandwidth GET-REPLACE,
+ serviceProviderContact GET,
+ -- the value of this attribute is set at creation by the SP
+ -- this attribute points to an instance of X.790 contact MO
+ -- or it contains X.790 PersonReach information.
+ serviceCustomerContact GET-REPLACE;
+ -- this attribute points to an instance of X.790 contact MO
+ -- or it contains X.790 PersonReach information.
+ NOTIFICATIONS
+ "Rec. X.721 | ISO/IEC 10165-2": qualityOfServiceAlarm;;
+ CONDITIONAL PACKAGES
+ aliasNamePackage PRESENT IF "SLA supports it",
+ serviceDescriptionPackage PRESENT IF "present in the service request",
+ -- represents the service class in Rec. M.3208.1
+ "Rec. X.721":availabilityStatus PRESENT IF "Any scheduling (daily, weekly, external) is
+ present",
+ "Rec. X.721 | ISO/IEC 10165-2":dailyScheduling
+ PRESENT IF "present in the service request.",
+ "Rec. X.721 | ISO/IEC 10165-2":weeklyScheduling
+ PRESENT IF " present in the service request ",
+ "Rec. X.721 | ISO/IEC 10165-2":externalScheduler
+ PRESENT IF " present in the service request ";
+ REGISTERED AS {m3108Part1ObjectClass 10};
+
+```
+
+### 6.4.2 lcs
+
+```
+
+lcs MANAGED OBJECT CLASS
+ DERIVED FROM transportService;
+ CHARACTERIZED BY
+ lcsPackage PACKAGE
+ BEHAVIOUR
+ lcsBehaviour BEHAVIOUR
+ DEFINED AS "This instantiable MO represents a LCS. If the SLA allows the SC to specify the route
+ and the SC did not specify the route in the service request, then the route attribute shall be present as
+ an empty SEQUENCE. The route cannot be changed through a management operation on this MO.
+ The route can be changed by the SC by creating an instance of the lcsModifyRequest MO class.";;
+ ATTRIBUTES
+ originatingLocationSap GET SET-BY-CREATE,
+ "Rec. X.790":serviceType GET SET-BY-CREATE,
+ -- represents the service name in Rec. M.3208.1
+ "Rec. X.790":serviceLocationList GET SET-BY-CREATE,
+ -- represents the originating and terminating
+ -- locations in Rec. M.3208.1
+ serviceAvailabilityDate GET SET-BY-CREATE,
+ terminatingLocationSap GET SET-BY-CREATE;;
+
+```
+
+#### CONDITIONAL PACKAGES
+
+| | |
+|-------------------------------------|-------------------------------------------------------------------------|
+| diversityPackage | PRESENT IF "present in the service request", |
+| routePackage | PRESENT IF "route was present in the service request", |
+| originatingLocationCPEModifyPackage | PRESENT IF "originatingLocationCPE was present in the service request", |
+| terminatingLocationCPEModifyPackage | PRESENT IF "terminatingLocationCPE was present in the service request"; |
+
+REGISTERED AS {m3108Part1ObjectClass 11};
+
+### 6.4.3 linkConnectionService
+
+linkConnectionService MANAGED OBJECT CLASS
+
+DERIVED FROM transportService;
+
+CHARACTERIZED BY
+
+linkConnectionServicePackage PACKAGE
+
+BEHAVIOUR
+
+linkConnectionServiceBehaviour BEHAVIOUR
+
+DEFINED AS "This instantiable MO represents a link connection service.";;
+
+ATTRIBUTES
+
+| | |
+|--------------------------------------------------------|----------------------|
+| originatingLocationCP | GET SET-BY-CREATE, |
+| "Rec. X.790":serviceType | GET SET-BY-CREATE, |
+| -- represents the service name in Rec. M.3208.1 | |
+| "Rec. X.790":serviceLocationList | GET SET-BY-CREATE, |
+| -- represents the originating and terminating | |
+| -- locations in Rec. M.3208.1 | |
+| serviceAvailabilityDate | GET SET-BY-CREATE, |
+| terminatingLocationCP | GET SET-BY-CREATE;;; |
+
+REGISTERED AS {m3108Part1ObjectClass 12};
+
+### 6.4.4 Service Access Domain
+
+serviceAccessDomain MANAGED OBJECT CLASS
+
+DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top;
+
+CHARACTERIZED BY
+
+serviceAccessDomainPackage PACKAGE
+
+BEHAVIOUR
+
+serviceAccessDomainBehaviour BEHAVIOUR
+
+DEFINED AS "This MO represents a Service Access Domain consisting of Service Access Groups having similar characteristics (e.g. supporting the same bandwidths). Although Rec. M.3208.1 specifies that a provider request number be provided by the SP, it is not included in this MO since this MO is created directly by the SC.";;
+
+ATTRIBUTES
+
+| | |
+|------------------------|--------------------|
+| providerRequestNumber | GET, |
+| serviceCustomerContact | GET-REPLACE, |
+| sadId | GET SET-BY-CREATE, |
+
+*-- sadId can be provided by the SC, otherwise it is set by the SP; used as naming attribute*
+
+| | |
+|--------------------------|-------------------------|
+| listOfSags | GET-REPLACE ADD-REMOVE, |
+| "Rec. X.790":serviceType | GET SET-BY-CREATE, |
+| serviceProviderContact | GET; |
+
+NOTIFICATIONS
+
+| | |
+|------------------------------------------------------|--|
+| "Rec.X.721 ISO/IEC 10165-2:1992":objectDeletion, | |
+| "Rec.X.721 ISO/IEC 10165-2:1992":objectCreation;;; | |
+
+CONDITIONAL PACKAGES
+
+| | |
+|---------------------------|---------------------------------------------------------------------|
+| aliasNamePackage | PRESENT IF "aliasName was present in the service request", |
+| serviceDescriptionPackage | PRESENT IF "serviceDescription was present in the service request"; |
+
+REGISTERED AS {m3108Part1ObjectClass 13};
+
+### 6.4.5 Service Access Group
+
+serviceAccessGroup MANAGED OBJECT CLASS
+DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top;
+CHARACTERIZED BY
+serviceAccessGroupPackage PACKAGE
+BEHAVIOUR
+serviceAccessGroupBehaviour BEHAVIOUR
+DEFINED AS "This MO represents a Service Access Group consisting of Service Access Points having similar characteristics (e.g. supporting the same bandwidths). If the administrative state is locked, then all the SAPs in the SAG are locked";;
+ATTRIBUTES
+sagId GET SET-BY-CREATE,
+listOfSaps GET-REPLACE ADD-REMOVE
+addToSagError
+removeFromSagError,
+sagLocation GET SET-BY-CREATE;
+ACTIONS
+addSapsToSag;
+NOTIFICATIONS
+"Rec.X.721 | ISO/IEC 10165-2:1992":objectDeletion,
+"Rec.X.721 | ISO/IEC 10165-2:1992":objectCreation;;;
+CONDITIONAL PACKAGES
+aliasNamePackage PRESENT IF "aliasName was present in the service request",
+"Rec. X.721 | ISO/IEC 10165-2:1992":administrativeStatePackage
+PRESENT IF "SLA supports it",
+REGISTERED AS {m3108Part1ObjectClass 14};
+
+## 6.5 Managed objects for resource fragment
+
+### 6.5.1 Service Access Equipment
+
+serviceAccessEquipmentView MANAGED OBJECT CLASS
+DERIVED FROM "Rec. X.721 | ISO/IEC 10165-2:1992":top;
+CHARACTERIZED BY
+serviceAccessEquipmentViewPackage PACKAGE
+BEHAVIOUR
+serviceAccessEquipmentViewBehaviour BEHAVIOUR
+DEFINED AS "The serviceAccessEquipment MO class represents customer-owned equipment that terminates LCS(s). The SC updates information in this MO to correctly reflect the actual state of the service access equipment in the SC's premises.";;
+ATTRIBUTES
+"Rec. M3100:1995": equipmentId GET SET-BY-CREATE,
+listOfSaps GET-REPLACE ADD-REMOVE,
+"Rec. X.790:1995": locationAddress GET SET-BY-CREATE;
+NOTIFICATIONS
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectDeletion,
+"Rec.X.721 | ISO/IEC 10165-2:1992": objectCreation;;;
+CONDITIONAL PACKAGES
+reflectiveAdministrativeStatePackage
+PRESENT IF "SLA supports it",
+reflectiveOperationalStatePackage
+PRESENT IF "SLA supports it",
+equipmentTypePackage
+PRESENT IF "SLA supports it",
+equipmentManufacturerPackage
+PRESENT IF "SLA supports it",
+modelTypePackage
+PRESENT IF "SLA supports it",
+
+```
+
+dateOfInstallationPackage
+ PRESENT IF "SLA supports it",
+expectedDateOfInstallationPackage
+ PRESENT IF "SLA supports it",
+procedurePackage
+ PRESENT IF "SLA supports it";
+REGISTERED AS {m3108Part1ObjectClass 15};
+
+```
+
+## 6.6 Packages
+
+### 6.6.1 aliasNameInfoPackage
+
+```
+
+aliasNameInfoPackage PACKAGE
+ ATTRIBUTES
+ aliasName GET;
+REGISTERED AS {m3108Part1Package 1};
+
+```
+
+### 6.6.2 aliasNamePackage
+
+```
+
+aliasNamePackage PACKAGE
+ ATTRIBUTES
+ aliasName GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 2};
+
+```
+
+### 6.6.3 bandwidthInfoPackage
+
+```
+
+bandwidthInfoPackage PACKAGE
+ ATTRIBUTES
+ bandwidth GET;
+REGISTERED AS {m3108Part1Package 3};
+
+```
+
+### 6.6.4 bandwidthPackage
+
+```
+
+bandwidthPackage PACKAGE
+ BEHAVIOUR
+ bandwidthPackageBehaviour BEHAVIOUR
+ DEFINED AS "If the requested bandwidth cannot be provided by the SP, the SP shall return the value together
+ with a reason code indicating that the bandwidth is not available.";;
+ ATTRIBUTES
+ bandwidth GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 4};
+
+```
+
+### 6.6.5 customerRequestNumberPackage
+
+```
+
+customerRequestNumberPackage PACKAGE
+ ATTRIBUTES
+ customerRequestNumber GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 7};
+
+```
+
+### 6.6.6 dateOfInstallationPackage
+
+```
+
+dateOfInstallationPackage PACKAGE
+ ATTRIBUTES
+ dateOfInstallation GET;
+REGISTERED AS {m3108Part1Package 8};
+
+```
+
+### **6.6.7 dailySchedulingInfoPackage**
+
+dailySchedulingInfoPackage PACKAGE
+ATTRIBUTES
+"Rec. X.721 | ISO/IEC 10165-2":intervalsOfDay GET;
+REGISTERED AS {m3108Part1Package 9};
+
+### **6.6.8 dailySchedulingCurrentPackage**
+
+dailySchedulingCurrentPackage PACKAGE
+BEHAVIOUR
+dailySchedulingCurrentPackageBehaviour BEHAVIOUR
+DEFINED AS "If the SC specifies a value and the SP is not able to accommodate the requested schedule, the SP must return an error with a reason code indicating that the schedule can not be met.";;
+ATTRIBUTES
+"Rec. X.721 | ISO/IEC 10165-2":intervalsOfDay
+GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 10};
+
+#### **6.6.9 diversityInfoPackage**
+
+diversityInfoPackage PACKAGE
+ATTRIBUTES
+diversity GET;
+REGISTERED AS {m3108Part1Package 11};
+
+### **6.6.10 diversityPackage**
+
+diversityPackage PACKAGE
+BEHAVIOUR
+diversityPackageBehaviour BEHAVIOUR
+DEFINED AS "In the case of partial success, the SP may indicate the common (i.e. non-diverse) components of the circuits (new and/or old) as a set of topological entities.";;
+ATTRIBUTES
+diversity GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 12};
+
+### **6.6.11 equipmentManufacturerPackage**
+
+equipmentManufacturerPackage PACKAGE
+ATTRIBUTES
+equipmentManufacturer GET-REPLACE;
+REGISTERED AS {m3108Part1Package 14};
+
+### **6.6.12 equipmentTypePackage**
+
+equipmentTypePackage PACKAGE
+ATTRIBUTES
+equipmentType GET-REPLACE;
+REGISTERED AS {m3108Part1Package 16};
+
+### **6.6.13 expectedDateOfInstallationInfoPackage**
+
+expectedDateOfInstallationInfoPackage PACKAGE
+ATTRIBUTES
+expectedDateOfInstallation GET;
+REGISTERED AS {m3108Part1Package 17};
+
+### **6.6.14 expectedDateOfInstallationPackage**
+
+expectedDateOfInstallationPackage PACKAGE
+ATTRIBUTES
+ expectedDateOfInstallation GET-REPLACE;
+REGISTERED AS {m3108Part1Package 18};
+
+#### **6.6.15 externalSchedulerCurrentPackage**
+
+externalSchedulerCurrentPackage PACKAGE
+ATTRIBUTES
+ "Rec. X.721 | ISO/IEC 10165-2":schedulerName GET-REPLACE;
+REGISTERED AS {m3108Part1Package 19};
+
+### **6.6.16 externalSchedulerInfoPackage**
+
+externalSchedulerInfoPackage PACKAGE
+ATTRIBUTES
+ "Rec. X.721 | ISO/IEC 10165-2":schedulerName GET;
+REGISTERED AS {m3108Part1Package 20};
+
+### **6.6.17 initialServiceAdministrativeStateInfoPackage**
+
+initialServiceAdministrativeStateInfoPackage PACKAGE
+ATTRIBUTES
+ requestedInitialServiceAdministrativeState GET;
+REGISTERED AS {m3108Part1Package 21};
+
+### **6.6.18 initialServiceAdministrativeStatePackage**
+
+initialServiceAdministrativeStatePackage PACKAGE
+BEHAVIOUR
+ initialServiceAdministrativeStateBehaviour BEHAVIOUR
+ DEFINED AS "If this package is not present then the value of the service, when created, is subject to the SLA.";;
+ATTRIBUTES
+ requestedInitialServiceAdministrativeState
+ GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 22};
+
+#### **6.6.19 modelTypePackage**
+
+modelTypePackage PACKAGE
+ATTRIBUTES
+ modelType GET-REPLACE;
+REGISTERED AS {m3108Part1Package 23};
+
+#### **6.6.20 originatingLocationCPEInfoPackage**
+
+originatingLocationCPEInfoPackage PACKAGE
+ATTRIBUTES
+ originatingLocationCPE GET;
+REGISTERED AS {m3108Part1Package 25};
+
+#### **6.6.21 originatingLocationCPEModifyPackage**
+
+originatingLocationCPEModifyPackage PACKAGE
+ATTRIBUTES
+ originatingLocationCPE GET-REPLACE;
+REGISTERED AS {m3108Part1Package 26};
+
+#### **6.6.22 originatingLocationCPEPackage**
+
+originatingLocationCPEPackage PACKAGE
+ATTRIBUTES
+ originatingLocationCPE GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 27};
+
+#### **6.6.23 originatingLocationCPInfoPackage**
+
+originatingLocationCPInfoPackage PACKAGE
+ATTRIBUTES
+ originatingLocationCP GET;
+REGISTERED AS {m3108Part1Package 28};
+
+#### **6.6.24 originatingLocationInfoPackage**
+
+originatingLocationInfoPackage PACKAGE
+ATTRIBUTES
+ originatingLocation GET;
+REGISTERED AS {m3108Part1Package 30};
+
+#### **6.6.25 originatingLocationSapInfoPackage**
+
+originatingLocationSapInfoPackage PACKAGE
+ATTRIBUTES
+ originatingLocationSap GET;
+REGISTERED AS {m3108Part1Package 31};
+
+#### **6.6.26 originatingLocationSapPackage**
+
+originatingLocationSapPackage PACKAGE
+ATTRIBUTES
+ originatingLocationSap GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 32};
+
+#### **6.6.27 procedurePackage**
+
+procedurePackage PACKAGE
+ATTRIBUTES
+ procedure GET-REPLACE;
+REGISTERED AS {m3108Part1Package 33};
+
+#### **6.6.28 quantityInfoPackage**
+
+quantityInfoPackage PACKAGE
+ATTRIBUTES
+ quantity GET;
+REGISTERED AS {m3108Part1Package 35};
+
+#### **6.6.29 quantityPackage**
+
+quantityPackage PACKAGE
+ATTRIBUTES
+ quantity GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 36};
+
+#### **6.6.30 reflectiveOperationalStatePackage**
+
+reflectiveOperationalStatePackage PACKAGE
+ATTRIBUTES
+"Rec.X.721 | ISO/IEC 10165-2:1992":operationalState GET-REPLACE;
+REGISTERED AS { m3108Part1Package 37};
+
+#### **6.6.31 reflectiveAdministrativeStatePackage**
+
+reflectiveAdministrativeStatePackage PACKAGE
+ATTRIBUTES
+"Rec.X.721 | ISO/IEC 10165-2:1992":administrativeState GET-REPLACE;
+REGISTERED AS { m3108Part1Package 38};
+
+#### **6.6.32 routeInfoPackage**
+
+routeInfoPackage PACKAGE
+ATTRIBUTES
+route GET;
+REGISTERED AS {m3108Part1Package 39};
+
+### **6.6.33 routePackage**
+
+routePackage PACKAGE
+BEHAVIOUR
+routePackageBehaviour BEHAVIOUR
+DEFINED AS "The SP may reject the requested route with returning the reason code or may return alternate route when the requested route is not available."::
+ATTRIBUTES
+route GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 40};
+
+#### **6.6.34 serviceAdministrativeStatePackage**
+
+serviceAdministrativeStatePackage PACKAGE
+ATTRIBUTES
+"Rec.X.721 | ISO/IEC 10164-2":administrativeState GET-REPLACE;
+REGISTERED AS {m3108Part1Package 41};
+
+#### **6.6.35 serviceAvailabilityDateInfoPackage**
+
+serviceAvailabilityDateInfoPackage PACKAGE
+ATTRIBUTES
+serviceAvailabilityDate GET;
+REGISTERED AS {m3108Part1Package 42};
+
+#### **6.6.36 serviceAvailabilityDatePackage**
+
+serviceAvailabilityDatePackage PACKAGE
+BEHAVIOUR
+serviceAvailabilityDatePackageBehaviour BEHAVIOUR
+DEFINED AS "The Service Availability Date can be modified only if the service has not been established."::
+ATTRIBUTES
+serviceAvailabilityDate GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 43};
+
+#### **6.6.37 serviceCustomerContactPackage**
+
+serviceCustomerContactPackage PACKAGE
+ATTRIBUTES
+ serviceCustomerContact GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 45};
+
+#### **6.6.38 serviceDescriptionInfoPackage**
+
+serviceDescriptionInfoPackage PACKAGE
+ATTRIBUTES
+ "Rec. X.790":serviceDescription GET;
+REGISTERED AS {m3108Part1Package 46};
+
+#### **6.6.39 serviceDescriptionPackage**
+
+serviceDescriptionPackage PACKAGE
+BEHAVIOUR
+ serviceDescriptionPackageBehaviour BEHAVIOUR
+ DEFINED AS "If the requested service class is not equal to the class of service provided by the SP, then the SP
+ must supply the value, else it is optional.";;
+ATTRIBUTES
+ "Rec. X.790":serviceDescription GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 47};
+
+#### **6.6.40 serviceProviderContactPackage**
+
+serviceProviderContactPackage PACKAGE
+ATTRIBUTES
+ serviceProviderContact GET;
+REGISTERED AS {m3108Part1Package 48};
+
+#### **6.6.41 serviceTerminationDateInfoPackage**
+
+serviceTerminationDateInfoPackage PACKAGE
+ATTRIBUTES
+ serviceTerminationDate GET;
+REGISTERED AS {m3108Part1Package 49};
+
+#### **6.6.42 serviceTerminationDatePackage**
+
+serviceTerminationDatePackage PACKAGE
+BEHAVIOUR
+ serviceTerminationDatePackageBehaviour BEHAVIOUR
+ DEFINED AS "If the SP cannot accept the date, an alternate date is provided.";;
+ATTRIBUTES
+ serviceTerminationDate GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 50};
+
+#### **6.6.43 serviceTypeInfoPackage**
+
+serviceTypeInfoPackage PACKAGE
+ATTRIBUTES
+ "Rec. X.790":serviceType GET;
+REGISTERED AS {m3108Part1Package 51};
+
+#### **6.6.44 terminatingLocationCPEInfoPackage**
+
+terminatingLocationCPEInfoPackage PACKAGE
+ATTRIBUTES
+terminatingLocationCPE GET;
+REGISTERED AS {m3108Part1Package 52};
+
+#### **6.6.45 terminatingLocationCPEModifyPackage**
+
+terminatingLocationCPEModifyPackage PACKAGE
+ATTRIBUTES
+terminatingLocationCPE GET-REPLACE;
+REGISTERED AS {m3108Part1Package 53};
+
+#### **6.6.46 terminatingLocationCPEPackage**
+
+terminatingLocationCPEPackage PACKAGE
+ATTRIBUTES
+terminatingLocationCPE GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 54};
+
+#### **6.6.47 terminatingLocationCPInfoPackage**
+
+terminatingLocationCPInfoPackage PACKAGE
+ATTRIBUTES
+terminatingLocationCP GET;
+REGISTERED AS {m3108Part1Package 55};
+
+### **6.6.48 terminatingLocationInfoPackage**
+
+terminatingLocationInfoPackage PACKAGE
+ATTRIBUTES
+terminatingLocation GET;
+REGISTERED AS {m3108Part1Package 57};
+
+### **6.6.49 terminatingLocationSapInfoPackage**
+
+terminatingLocationSapInfoPackage PACKAGE
+ATTRIBUTES
+terminatingLocationSap GET;
+REGISTERED AS {m3108Part1Package 58};
+
+#### **6.6.50 terminatingLocationSapPackage**
+
+terminatingLocationSapPackage PACKAGE
+ATTRIBUTES
+terminatingLocationSap GET-REPLACE;
+REGISTERED AS {m3108Part1Package 59};
+
+#### **6.6.51 weeklySchedulingInfoPackage**
+
+weeklySchedulingInfoPackage PACKAGE
+ATTRIBUTES
+"Rec. X.721 | ISO/IEC 10165-2": weekMask GET;
+REGISTERED AS {m3108Part1Package 60};
+
+### 6.6.52 weeklySchedulingCurrentPackage
+
+weeklySchedulingCurrentPackage PACKAGE
+BEHAVIOUR
+ weeklySchedulingCurrentPackageBehaviour BEHAVIOUR
+ DEFINED AS "If the SC specifies a value and the SP is not able to accommodate the requested schedule, the SP must return an error with a reason code indicating that the schedule can not be met.";;
+ ATTRIBUTES
+ "Rec. X.721 | ISO/IEC 10165-2":weekMask
+ GET SET-BY-CREATE;
+REGISTERED AS {m3108Part1Package 61};
+
+## 6.7 Attributes
+
+### 6.7.1 aliasName
+
+aliasName ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.AliasName;
+ MATCHES FOR EQUALITY, SUBSTRINGS;
+REGISTERED AS {m3108Part1Attribute 1};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2],
+-- [3.3.3.2.6.2], [3.3.3.2.9.2], [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2], [3.3.3.4.3.2], [3.3.3.4.4.2],
+-- [3.3.3.4.6.2], [3.3.3.4.9.2], [3.3.3.7.1.2], [3.3.3.7.2.2]
+
+### 6.7.2 bandwidth
+
+bandwidth ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Bandwidth;
+ MATCHES FOR EQUALITY, ORDERING;
+REGISTERED AS {m3108Part1Attribute 2};
+-- represents Bandwidth, Link Connection Bandwidth information in the M.3208.1 "Information flow"
+-- [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2],
+-- [3.3.3.3.1.2], [3.3.3.4.1.2], [3.3.3.3.3.2], [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]
+
+### 6.7.3 cp
+
+cp ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cp;
+ MATCHES FOR EQUALITY, SUBSTRINGS;
+BEHAVIOUR
+ cpBehaviour BEHAVIOUR
+ DEFINED AS "This attribute identifies the connection point or the service node specified in Rec. M.3208.1";;
+REGISTERED AS {m3108Part1Attribute 3};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2],
+-- [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]
+
+### 6.7.4 customerRequestNumber
+
+customerRequestNumber ATTRIBUTE
+ WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestNumber;
+ MATCHES FOR EQUALITY, ORDERING;
+REGISTERED AS {m3108Part1Attribute 4};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]
+
+### 6.7.5 **dateOfInstallation**
+
+dateOfInstallation ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering;
+REGISTERED AS {m3108Part1Attribute 5};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]*
+
+### 6.7.6 **diversity**
+
+diversity ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Diversity;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+diversityBehaviour BEHAVIOUR
+DEFINED AS "This attribute identifies the topological entities from which the circuit should be diverse, or the other circuits from which the circuit should be diverse, or the number of the circuits in the diverse group and the topological entities from which the circuits in the group should be diverse.";;
+REGISTERED AS {m3108Part1Attribute 6};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.2.1.2], [3.3.3.2.4.2]*
+
+### 6.7.7 **equipmentManufacturer**
+
+equipmentManufacturer ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.EquipmentManufacturer;
+MATCHES FOR EQUALITY, SUBSTRINGS;
+REGISTERED AS {m3108Part1Attribute 7};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]*
+
+### 6.7.8 **equipmentType**
+
+equipmentType ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.EquipmentType;
+MATCHES FOR EQUALITY, SUBSTRINGS;
+REGISTERED AS {m3108Part1Attribute 8};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]*
+
+#### 6.7.9 **expectedDateOfInstallation**
+
+expectedDateOfInstallation ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time;
+MATCHES FOR EQUALITY, ORDERING;
+REGISTERED AS {m3108Part1Attribute 9};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]*
+
+#### 6.7.10 **listOfSags**
+
+listOfSags ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ListOfSags;
+MATCHES FOR EQUALITY, SET-INTERSECTION, SET-COMPARISON;
+REGISTERED AS {m3108Part1Attribute 10};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.7.1.2]*
+
+#### 6.7.11 listOfSaps
+
+listOfSaps ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ListOfSaps;
+MATCHES FOR EQUALITY, SET-INTERSECTION, SET-COMPARISON;
+REGISTERED AS {m3108Part1Attribute 11};
+*-- represents Service Access Point Ids, Service Access Point*
+*-- information in the M.3208.1 "Information flow" [3.3.3.7.4.2], [3.3.3.7.5.2], [3.3.3.9.1.2], [3.3.3.9.2.2]*
+
+#### 6.7.12 modelType
+
+modelType ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ModelType;
+MATCHES FOR EQUALITY, SUBSTRINGS;
+REGISTERED AS {m3108Part1Attribute 12};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.9.1.2], [3.3.3.9.2.2]*
+
+#### 6.7.13 numberOfUnspecifiedSaps
+
+numberOfUnspecifiedSaps ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.NumberOfUnspecifiedSaps;
+MATCHES FOR EQUALITY, ORDERING;
+REGISTERED AS {m3108Part1Attribute 13};
+*-- represents information in the M.3208.1 "Information flow" [ 3.3.3.7.4.2]*
+
+#### 6.7.14 originatingLocation
+
+originatingLocation ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.OriginatingLocation;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 14};
+*-- represents information in the M.3208.1 "Information flow" [ 3.3.3.1.1.2], [3.3.3.2.1.2]*
+
+#### 6.7.15 originatingLocationCP
+
+originatingLocationCP ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cp;
+MATCHES FOR EQUALITY, SUBSTRINGS;
+REGISTERED AS {m3108Part1Attribute 15};
+*-- represents information in the M.3208.1 "Information flow" [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2],*
+*-- [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]*
+
+#### 6.7.16 originatingLocationCPE
+
+originatingLocationCPE ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cpe;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+originatingLocationCPEBehaviour BEHAVIOUR
+DEFINED AS "This attribute describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit.";
+REGISTERED AS {m3108Part1Attribute 16};
+*-- represents Originating Location CPE Type information in the M.3208.1 "Information flow"*
+*-- [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.2.9.2]*
+
+#### 6.7.17 originatingLocationSap
+
+originatingLocationSap ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Sap;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+originatingLocationSAPBehaviour BEHAVIOUR
+DEFINED AS "This attribute identifies access point where the Leased Circuit Service originates.";;
+REGISTERED AS {m3108Part1Attribute 17};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2],
+-- [3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2]
+
+#### 6.7.18 procedure
+
+procedure ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Procedure;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+procedureBehaviour BEHAVIOUR
+DEFINED AS "This attribute describes the changes of the (test) procedure.";;
+REGISTERED AS {m3108Part1Attribute 18};
+-- represents Changes In Procedure information in the M.3208.1 "Information flow" [3.3.3.9.2.2]
+
+#### 6.7.19 providerRequestNumber
+
+providerRequestNumber ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestNumber;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR
+providerRequestNumberBehaviour BEHAVIOUR
+DEFINED AS "This attribute is a unique identifier provided by the SP to identify the request. The providerRequestNumber attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the current service request and service modify request object class";;
+REGISTERED AS {m3108Part1Attribute 19};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2],
+-- [3.3.3.1.4.2], [3.3.3.2.1.2], [3.3.3.2.4.2], [3.3.3.2.7.2], [3.3.3.2.8.2], [3.3.3.2.9.2], [3.3.3.3.1.2],
+-- [3.3.3.3.2.2], [3.3.3.3.3.2], [3.3.3.3.4.2], [3.3.3.4.1.2], [3.3.3.4.4.2], [3.3.3.4.7.2], [3.3.3.4.8.2],
+-- [3.3.3.4.9.2], [3.3.3.7.1.2]
+
+#### 6.7.20 quantity
+
+quantity ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Number;
+MATCHES FOR EQUALITY, ORDERING;
+REGISTERED AS {m3108Part1Attribute 21};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.2.1.2], [3.3.3.2.4.2]
+
+#### 6.7.21 requestedInitialServiceAdministrativeState
+
+requestedInitialServiceAdministrativeState ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestedInitialServiceAdministrativeState;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 22};
+-- represents Service Administrative State, Link Connection Service Administrative State
+-- information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.3.1.2]
+
+#### 6.7.22 requestReceptionTime
+
+requestReceptionTime ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering;
+REGISTERED AS {m3108Part1Attribute 23};
+
+#### 6.7.23 requestSequenceNumber
+
+requestSequenceNumber ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.RequestNumber;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+requestSequenceNumberBehaviour BEHAVIOUR
+DEFINED AS "The requestSequenceNumber attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service request history record object class";;
+REGISTERED AS {m3108Part1Attribute 24};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.3.2], [3.3.3.1.4.2], [3.3.3.2.4.2],
+-- [3.3.3.3.3.2], [3.3.3.3.4.2]
+
+#### 6.7.24 route
+
+route ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Route;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 25};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2],
+-- [3.3.3.2.3.2], [3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2]
+
+#### 6.7.25 sadId
+
+sadId ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.SadId;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+sadIDBehaviour BEHAVIOUR
+DEFINED AS "The sadID attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service access domain object class";;
+REGISTERED AS {m3108Part1Attribute 26};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.7.1.2], [3.3.3.7.2.2], [3.3.3.7.3.2]
+
+#### 6.7.26 sagId
+
+sagId ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.SagId;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+sagIDBehaviour BEHAVIOUR
+DEFINED AS "The sagID attribute is an attribute type whose distinguished value can be used as a RDN when naming an instance of the service access group object class";;
+REGISTERED AS {m3108Part1Attribute 27};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.7.2.2], [3.3.3.7.3.2], [3.3.3.7.4.2], [3.3.3.7.5.2]
+
+#### 6.7.27 sagLocation
+
+sagLocation ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.SagLocation;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 28};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.7.2.2]
+
+#### 6.7.28 serviceAvailabilityDate
+
+serviceAvailabilityDate ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Time;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering;
+REGISTERED AS {m3108Part1Attribute 29};
+-- represents Service Availability Date, Link Connection Availability Date information in the
+-- M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.4.2], [3.3.3.2.6.2],
+-- [3.3.3.2.9.2], [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2], [3.3.3.4.6.2], [3.3.3.4.9.2]
+
+#### 6.7.29 serviceCustomerContact
+
+serviceCustomerContact ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Contact;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 30};
+-- represents Customer Contact information in the M.3208.1 "Information flow" [3.3.3.1.1.2],
+-- [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.2.9.2], [3.3.3.3.1.2], [3.3.3.3.3.2],
+-- [3.3.3.4.6.2], [3.3.3.4.9.2], [3.3.3.7.1.2]
+
+#### 6.7.30 serviceInstance
+
+serviceInstance ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ObjectInstance;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 31};
+-- represents Circuit Number, Link Connection Identifier information in the M.3208.1 "Information
+-- flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.2.2], [3.3.3.2.3.2], [3.3.3.2.4.2],
+-- [3.3.3.2.5.2], [3.3.3.2.6.2], [3.3.3.3.1.2], [3.3.3.3.2.2], [3.3.3.3.3.2], [3.3.3.4.1.2], [3.3.3.4.2.2],
+-- [3.3.3.4.3.2], [3.3.3.4.5.2], [3.3.3.4.6.2], [3.3.3.4.9.2]
+
+#### 6.7.31 serviceProviderContact
+
+serviceProviderContact ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Contact;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 32};
+-- represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.2.1.2],
+-- [3.3.3.2.2.2], [3.3.3.2.4.2], [3.3.3.3.1.2], [3.3.3.3.2.2], [3.3.3.4.1.2], [3.3.3.4.2.2], [3.3.3.4.3.2],
+-- [3.3.3.4.4.2], [3.3.3.7.1.2]
+
+#### 6.7.32 serviceRequestState
+
+serviceRequestState ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.ServiceRequestState;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+serviceRequestStateBehaviour BEHAVIOUR
+DEFINED AS "This attribute represents the service request state specified in Rec. M.3208.1.";
+
+REGISTERED AS {m3108Part1Attribute 33};
+-- *represents Service Request State, Link Connection Request State information in the M.3208.1*
+-- *"Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2], [3.3.3.2.7.2], [3.3.3.2.8.2], [3.3.3.3.1.2],*
+-- *[3.3.3.3.3.2], [3.3.3.4.7.2], [3.3.3.4.8.2], [3.3.3.4.9.2]*
+
+#### 6.7.33 serviceTerminationDate
+
+serviceTerminationDate ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module. ServiceTerminationDate;
+MATCHES FOR EQUALITY, ORDERING;
+BEHAVIOUR "Rec. X.721 | ISO/IEC 10165-2:1992":timeOrdering;
+REGISTERED AS {m3108Part1Attribute 34};
+-- *represents Service Termination Date, Link Connection Termination Date, Link Termination Date*
+-- *information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.2.2], [3.3.3.1.3.2],*
+-- *[3.3.3.2.1.2], [3.3.3.2.2.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.3.1.2], [3.3.3.3.2.2], [3.3.3.3.3.2],*
+-- *[3.3.3.4.1.2], [3.3.3.4.2.2], [3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]*
+
+#### 6.7.34 terminatingLocation
+
+terminatingLocation ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.TerminatingLocation;
+MATCHES FOR EQUALITY;
+REGISTERED AS {m3108Part1Attribute 36};
+-- *represents information in the M.3208.1 "Information flow" [ 3.3.3.1.1.2], [3.3.3.2.1.2]*
+
+### 6.7.35 terminatingLocationCP
+
+terminatingLocationCP ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cp;
+MATCHES FOR EQUALITY, SUBSTRINGS;
+REGISTERED AS {m3108Part1Attribute 37};
+-- *represents information in the M.3208.1 "Information flow" [3.3.3.3.1.2], [3.3.3.3.3.2], [3.3.3.4.1.2],*
+-- *[3.3.3.4.3.2], [3.3.3.4.4.2], [3.3.3.4.6.2], [3.3.3.4.9.2]*
+
+#### 6.7.36 terminatingLocationCPE
+
+terminatingLocationCPE ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Cpe;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+terminatingLocationCPEBehaviour BEHAVIOUR
+DEFINED AS "This attribute describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit.";;
+REGISTERED AS {m3108Part1Attribute 38};
+-- *represents Originating Location CPE Type information in the M.3208.1 "Information flow"*
+-- *[3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2], [3.3.3.2.3.2], [3.3.3.2.6.2], [3.3.3.2.9.2]*
+
+#### 6.7.37 terminatingLocationSap
+
+terminatingLocationSap ATTRIBUTE
+WITH ATTRIBUTE SYNTAX M3108Part1ASN1Module.Sap;
+MATCHES FOR EQUALITY;
+BEHAVIOUR
+terminatingLocationSAPBehaviour BEHAVIOUR
+DEFINED AS "This attribute identifies access point where the Leased Circuit Service terminates.";;
+REGISTERED AS {m3108Part1Attribute 39};
+-- *represents information in the M.3208.1 "Information flow" [3.3.3.1.1.2], [3.3.3.1.3.2], [3.3.3.2.1.2],*
+-- *[3.3.3.2.4.2], [3.3.3.2.6.2], [3.3.3.2.9.2]*
+
+## 6.8 Error messages
+
+#### 6.8.1 addToSagError
+
+addToSagError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.AddToSagError;
+BEHAVIOUR addToSagErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request add a SAP to a SAG is invalid or if the SP cannot comply with the request.";;
+REGISTERED AS {m3108Part1Parameter 1};
+
+### 6.8.2 bandwidthUnavailable
+
+bandwidthUnavailable PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.Null;
+BEHAVIOUR bandwidthUnavailableBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the SP does not have the bandwidth to comply with the request.";;
+REGISTERED AS {m3108Part1Parameter 2};
+
+### 6.8.3 CreateLCSError
+
+createLCSError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.CreateLCSError;
+BEHAVIOUR createLCSErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request for LCS is invalid or if the SP cannot provide the requested service.";;
+REGISTERED AS {m3108Part1Parameter 3};
+
+### 6.8.4 createLinkConnectionError
+
+createLinkConnectionError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.CreateLinkConnectionError;
+BEHAVIOUR createLinkConnectionErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request for link connection service is invalid or if the SP cannot provide the requested service.";;
+REGISTERED AS {m3108Part1Parameter 4};
+
+### 6.8.5 createSadError
+
+createSadError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.CreateSadError;
+BEHAVIOUR createSadErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request for a SAD is invalid or if the SP cannot provide the requested SAD.";;
+REGISTERED AS {m3108Part1Parameter 5};
+
+### 6.8.6 createSagError
+
+createSagError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.CreateSagError;
+BEHAVIOUR createSagErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request for a SAG is invalid or if the SP cannot provide the requested SAG.";;
+REGISTERED AS {m3108Part1Parameter 6};
+
+### **6.8.7 deleteLCSError**
+
+deleteLCSError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.DeleteLCSError;
+BEHAVIOUR deleteLCSErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request to delete a LCS is incorrect.";;
+REGISTERED AS {m3108Part1Parameter 7};
+
+#### **6.8.8 deleteLinkConnectionError**
+
+deleteLinkConnectionError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.DeleteLinkConnectionError;
+BEHAVIOUR deleteLinkConnectionErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request to delete a link connection service is incorrect.";;
+REGISTERED AS {m3108Part1Parameter 8};
+
+### **6.8.9 deleteSadError**
+
+deleteSadError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.DeleteSadError;
+BEHAVIOUR deleteSadErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request to delete a SAD is incorrect, in particular, if the SAD contains
+SAG(s).";;
+REGISTERED AS {m3108Part1Parameter 9};
+
+### **6.8.10 deleteSagError**
+
+deleteSagError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.DeleteSagError;
+BEHAVIOUR deleteSagErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request to delete a SAG is incorrect.";;
+REGISTERED AS {m3108Part1Parameter 10};
+
+### **6.8.11 modifyLCSError**
+
+modifyLCSError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.ModifyLCSError;
+BEHAVIOUR modifyLcsErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the SP cannot comply with the request.";;
+REGISTERED AS {m3108Part1Parameter 11};
+
+### **6.8.12 removeFromSagError**
+
+removeFromSagError PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.RemoveFromSagError;
+BEHAVIOUR removeFromSagErrorBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the request remove a SAP from a SAG is invalid or if the SP cannot
+comply with the request.";;
+REGISTERED AS {m3108Part1Parameter 12};
+
+### **6.8.13 resourcesUnavailable**
+
+resourcesUnavailable PARAMETER
+CONTEXT SPECIFIC-ERROR;
+WITH SYNTAX M3108Part1ASN1Module.Null;
+BEHAVIOUR resourcesUnavailableBehaviour BEHAVIOUR
+DEFINED AS "This error is issued if the SP does not have the resources to comply with the request.";;
+REGISTERED AS {m3108Part1Parameter 13};
+
+## **6.9 Notifications**
+
+### **6.9.1 lcsModifyProgressProblemReport**
+
+lcsModifyProgressProblemReport NOTIFICATION
+BEHAVIOUR lcsModifyProgressProblemReportBehaviour;
+WITH INFORMATION SYNTAX M3108Part1ASN1Module.LcsModifyProgressProblemReport;
+REGISTERED AS {m3108Part1Notification 1};
+
+lcsModifyProgressProblemReportBehaviour
+BEHAVIOUR
+DEFINED AS "This notification is used to report problems with a LCS modification request.";
+
+### **6.9.2 lcsRequestProgressProblemReport**
+
+lcsRequestProgressProblemReport NOTIFICATION
+BEHAVIOUR lcsRequestProgressProblemReportBehaviour;
+WITH INFORMATION SYNTAX M3108Part1ASN1Module.LcsRequestProgressProblemReport;
+REGISTERED AS {m3108Part1Notification 2};
+
+lcsRequestProgressProblemReportBehaviour
+BEHAVIOUR
+DEFINED AS " This notification is used to report problems with a LCS request.";
+
+### **6.9.3 linkConnectionModifyProgressProblemReport**
+
+linkConnectionModifyProgressProblemReport NOTIFICATION
+BEHAVIOUR linkConnectionModifyProgressProblemReportBehaviour;
+WITH INFORMATION SYNTAX M3108Part1ASN1Module.LinkConnectionModifyProgressProblemReport;
+REGISTERED AS {m3108Part1Notification 3};
+
+linkConnectionModifyProgressProblemReportBehaviour
+BEHAVIOUR
+DEFINED AS "This notification is used to report problems with a link connection service modification request.";
+
+### **6.9.4 linkConnectionRequestProgressProblemReport**
+
+linkConnectionRequestProgressProblemReport NOTIFICATION
+BEHAVIOUR linkConnectionRequestProgressProblemReportBehaviour;
+WITH INFORMATION SYNTAX M3108Part1ASN1Module.LinkConnectionRequestProgressProblemReport;
+REGISTERED AS {m3108Part1Notification 4};
+
+linkConnectionRequestProgressProblemReportBehaviour
+BEHAVIOUR
+DEFINED AS "This notification is used to report problems with a link connection service request.";
+
+## 6.10 Actions
+
+### 6.10.1 updateServiceRequest
+
+updateServiceRequest ACTION
+BEHAVIOUR updateServiceRequestBehaviour;
+WITH INFORMATION SYNTAX M3108Part1ASN1Module.UpdateServiceRequest;
+WITH REPLY SYNTAX M3108Part1ASN1Module.UpdateServiceReply;
+REGISTERED AS {m3108Part1Action 1};
+
+updateServiceRequestBehaviour BEHAVIOUR
+DEFINED AS "The updateServiceRequest action is used by the service customer to modify a non-completed service request. The attributes that can be modified are identified by the service request object class. If the values provided by the SP are different from the values requested by the SC, then the values of those attributes must be returned by the SP to the SC. If as result of the action some other attributes have changed (e.g. the SC requests a different bandwidth, the request is implemented, but the route has changed, then the values of those changed attributes must be included in the response from the SP to the SC.";
+
+### 6.10.2 AddSapsToSag
+
+AddSapsToSag ACTION
+BEHAVIOUR AddSapsToSagBehaviour;
+WITH INFORMATION SYNTAX M3108Part1ASN1Module.AddSapsToSagInformation;
+WITH REPLY SYNTAX M3108Part1ASN1Module.AddSapsToSagResult;
+REGISTERED AS {m3108Part1Action 2};
+
+AddSapsToSagBehaviour BEHAVIOUR
+DEFINED AS "This action is used to arrange service access points into SAGs. Contained service access points IDs are added; if the service access points IDs are empty and the number of access service access points is provided, the SP adds as many SAPs as specified in the number of SAPs; the SP further provides their IDs. If the number of SAPs is not provided and no SAP IDs are specified, then the SP adds a single SAP to the SAG and provides its Id. If both the number of SAPs and SAP IDs are present, then the SP adds the identified SAPs to the SAG, the SP further adds as many SAPs as specified by the number of SAPs and provides their IDs. The SAP IDs must be present in case of an error or if the SAP IDs are provided by the SP to the SC in the reply value.";
+
+## 6.11 Name bindings
+
+### 6.11.1 currentLcsRequest-account
+
+currentLcsRequest-account NAME BINDING
+SUBORDINATE OBJECT CLASS currentLcsRequest AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES;
+WITH ATTRIBUTE providerRequestNumber;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING
+createLCSError;
+DELETE DELETES-CONTAINED-OBJECTS
+deleteLCSError;
+REGISTERED AS {m3108Part1NameBinding 1};
+
+### 6.11.2 lcsRequestHistoryRecord-currentLCSRequest
+
+lcsRequestHistoryRecord-currentLCSRequest NAME BINDING
+SUBORDINATE OBJECT CLASS lcsRequestHistoryRecord;
+NAMED BY SUPERIOR OBJECT CLASS currentLcsRequest AND SUBCLASSES;
+WITH ATTRIBUTE requestSequenceNumber;
+REGISTERED AS {m3108Part1NameBinding 2};
+
+### 6.11.3 lcsModifyRequest-lcs
+
+lcsModifyRequest-lcs NAME BINDING
+SUBORDINATE OBJECT CLASS lcsModifyRequest AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS lcs AND SUBCLASSES;
+WITH ATTRIBUTE providerRequestNumber;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING;
+DELETE;
+REGISTERED AS {m3108Part1NameBinding 3};
+
+### 6.11.4 currentLinkConnectionServiceRequest-account
+
+currentLinkConnectionServiceRequest-account NAME BINDING
+SUBORDINATE OBJECT CLASS currentLinkConnectionServiceRequest
+AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES;
+WITH ATTRIBUTE providerRequestNumber;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING
+createLinkConnectionError;
+DELETE DELETES-CONTAINED-OBJECTS
+deleteLinkConnectionError;
+REGISTERED AS {m3108Part1NameBinding 4};
+
+### 6.11.5 linkConnectionServiceRequestHistoryRecord-currentLinkConnectionServiceRequest
+
+linkConnectionServiceRequestHistoryRecord-currentLinkConnectionServiceRequest NAME BINDING
+SUBORDINATE OBJECT CLASS linkConnectionServiceRequestHistoryRecord;
+NAMED BY SUPERIOR OBJECT CLASS currentLinkConnectionServiceRequest
+AND SUBCLASSES;
+WITH ATTRIBUTE requestSequenceNumber;
+BEHAVIOUR
+historyBindingBehaviour BEHAVIOUR
+DEFINED AS "The service provider creates a serviceRequestHistoryRecord of the initial service
+request (currentServiceRequest) values. The serviceRequestHistoryRecord is also created when the
+service customer issues an updateServiceRequest action towards a currentServiceRequest (and
+subclasses) and contains a record of the attribute values specified in the request.";;
+REGISTERED AS {m3108Part1NameBinding 5};
+
+### 6.11.6 linkConnectionServiceModifyRequest-linkConnectionService
+
+linkConnectionServiceModifyRequest-linkConnectionService NAME BINDING
+SUBORDINATE OBJECT CLASS linkConnectionServiceModifyRequest;
+NAMED BY SUPERIOR OBJECT CLASS linkConnectionService
+AND SUBCLASSES;
+WITH ATTRIBUTE providerRequestNumber;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING;
+DELETE;
+REGISTERED AS {m3108Part1NameBinding 6};
+
+### 6.11.7 serviceAccessEquipmentView-account
+
+serviceAccessEquipmentView-account NAME BINDING
+SUBORDINATE OBJECT CLASS serviceAccessEquipmentView AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES;
+WITH ATTRIBUTE "Rec. M3100:1995":equipmentId;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING;
+
+DELETE;
+REGISTERED AS {m3108Part1NameBinding 7};
+
+### 6.11.8 linkConnectionService-account
+
+linkConnectionService-account NAME BINDING
+SUBORDINATE OBJECT CLASS linkConnectionService AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES;
+WITH ATTRIBUTE "Rec. X.790:1995": serviceID;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING;
+DELETE DELETES-CONTAINED-OBJECTS;
+REGISTERED AS {m3108Part1NameBinding 8};
+
+### 6.11.9 lcs-account
+
+lcs-account NAME BINDING
+SUBORDINATE OBJECT CLASS lcs AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES;
+WITH ATTRIBUTE "Rec. X.790:1995": serviceID;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING;
+DELETE DELETES-CONTAINED-OBJECTS;
+REGISTERED AS {m3108Part1NameBinding 9};
+
+### 6.11.10 serviceAccessDomain-account
+
+serviceAccessDomain-account NAME BINDING
+SUBORDINATE OBJECT CLASS serviceAccessDomain AND SUBCLASSES;
+NAMED BY SUPERIOR OBJECT CLASS "Rec. X.790":account AND SUBCLASSES;
+WITH ATTRIBUTE sadId;
+BEHAVIOUR
+serviceAccessDomainBindingBehaviour BEHAVIOUR
+DEFINED AS "An instance of this MO class can be created by the SC. An instance of this MO class
+can be deleted by the SC.";;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING
+createSadError;
+DELETE
+deleteSadError;
+REGISTERED AS {m3108Part1NameBinding 10};
+
+### 6.11.11 serviceAccessGroup-serviceAccessDomain
+
+serviceAccessGroup-serviceAccessDomain NAME BINDING
+SUBORDINATE OBJECT CLASS serviceAccessGroup;
+NAMED BY SUPERIOR OBJECT CLASS serviceAccessDomain AND SUBCLASSES;
+WITH ATTRIBUTE sagId;
+BEHAVIOUR
+serviceAccessGroupBindingBehaviour BEHAVIOUR
+DEFINED AS "An instance of this MO class can be created by the SC. An instance of this MO class
+can be deleted by the SC.";;
+CREATE
+WITH-AUTOMATIC-INSTANCE-NAMING
+createSagError;
+DELETE
+deleteSagError;
+REGISTERED AS {m3108Part1NameBinding 11};
+
+## 6.12 ASN.1 syntax
+
+### 6.12.1 Rules of extensibility
+
+The following types will be indicated as being extensible:
+
+- ENUMERATED;
+- named INTEGER;
+- named BIT STRING;
+- tagged SET;
+- tagged SEQUENCE;
+- tagged CHOICE.
+
+Under the rules of extensibility new enumerations (for ENUMERATED types), new bit name assignments (for named BIT STRING types), new named numbers (for named INTEGER types), and new tagged elements (for tagged SET, SEQUENCE, and CHOICE types) may be added in future versions of this Recommendation.
+
+When processing information in a System Management Application Protocol (SMAP) PDU, the accepting SMAP-machine shall ignore:
+
+- enumerations not recognized;
+- unrecognized named numbers;
+- unrecognized named bits;
+- unrecognized tagged elements of sets, sequences, and choices.
+
+### 6.12.2 ASN.1 module
+
+M3108Part1ASN1Module {ccitt recommendation m lcs(3108) serviceManagement(1) informationModel(0) asnlModules(2) asnlDefinedTypesModule(0)}
+
+DEFINITIONS IMPLICIT TAGS ::=
+
+BEGIN
+
+-- EXPORTS *everything*
+
+IMPORTS
+
+NameType
+
+FROM ASN1DefinedTypesModule {ccitt recommendation m gnm(100) informationModel(0)
+
+asnlModules(2) asnlDefinedTypesModule(0)}
+
+AdditionalInformation, AdditionalText, AdministrativeState, AttributeList, AvailabilityStatus, NotificationIdentifier, SourceIndicator
+
+FROM Attribute-ASN1Module {joint-iso-ccitt ms(9) smi(3) part2(2) asnlModule (2) 1}
+
+ObjectInstance
+
+FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)}
+
+LocationAddress, PersonReach
+
+FROM X790ASN1Module {itu-t(0) recommendation(0) x(24) x790(790) informationModel(0)
+
+asnlmodule(2)}
+
+;
+
+m3108Part1InformationModel OBJECT IDENTIFIER ::= {ccitt recommendation m lcs(3108) serviceManagement(1) informationModel(0) }
+
+m3108Part1ObjectClass OBJECT IDENTIFIER ::= {m3108Part1InformationModel managedObjectClass(1)}
+
+m3108Part1Package OBJECT IDENTIFIER ::= {m3108Part1InformationModel package(2)}
+
+m3108Part1Attribute OBJECT IDENTIFIER ::= {m3108Part1InformationModel attribute(3)}
+
+m3108Part1NameBinding OBJECT IDENTIFIER ::= {m3108Part1InformationModel nameBinding(4)}
+
+m3108Part1Notification OBJECT IDENTIFIER ::= {m3108Part1InformationModel notification(5)}
+
+m3108Part1Parameter OBJECT IDENTIFIER ::= {m3108Part1InformationModel parameter(6)}
+
+m3108Part1Action OBJECT IDENTIFIER ::= {m3108Part1InformationModel action(7)}
+
+```
+
+AddSapsToSagInformation ::= SEQUENCE {
+ listOfSaps ListOfSaps OPTIONAL,
+ numberOfServiceAccessPoints INTEGER OPTIONAL
+}
+
+AddSapsToSagResult ::= CHOICE {
+ listOfSaps ListOfSaps,
+ addToSagError AddToSagError
+}
+
+AddToSagError ::= ENUMERATED {
+ invalidSapId (0),
+ invalidSagId (1),
+ sapNotInAppropriateUsageState (2),
+ resourcesNotAvailable (3),
+ ...
+}
+
+AliasName ::= PrintableString
+
+Bandwidth ::= CHOICE {
+ bitsPerSecond [0] Number,
+ kiloBitsPerSecond [1] Number,
+ megaBitsPerSecond [2] Number,
+ gigaBitsPerSecond [3] Number,
+ teraBitsPerSecond [4] Number
+ -- , ...
+}
+
+CircuitId ::= NameType
+
+CircuitNumber ::= Number
+
+Contact ::= CHOICE {
+ person PersonReach,
+ contactObject ObjectInstance
+ -- the ObjectInstance points to an instance of a X.790 Contact object.
+}
+
+Cp ::= TopologicalEntity
+
+Cpe ::= CHOICE { name PrintableString,
+ object ObjectInstance
+ }
+
+CreateSadError ::= ENUMERATED {
+ invalidLocation (0),
+ invalidServiceType (1),
+ invalidServiceDescription (2),
+ ...
+}
+
+CreateSagError ::= ENUMERATED {
+ invalidLocation (0),
+ invalidSagId (1),
+ invalidSadId (2),
+ ...
+}
+
+```
+
+```
+
+CreateLCSError ::= ENUMERATED {
+ unknownServiceDescription (0),
+ unknownServiceType (1),
+ resourcesUnavailable (2),
+ requestedBandwidthNotAvailable (3),
+ quantitySpecifiedOutOfRange (4),
+ contractViolation (5),
+ invalidValue (6),
+ requiredParameterNotAvailable (7),
+ serviceCannotBeCompleted (8),
+ invalidServiceTerminationDate (9),
+ invalidSchedule (10),
+ invalidServiceAvailabilityDate (11),
+ requestAlreadyClosed (12),
+ invalidAddress (13),
+ nonExistentSAP (14),
+ ...
+}
+
+CreateLinkConnectionError ::= ENUMERATED {
+ unknownServiceDescription (0),
+ unknownServiceType (1),
+ resourcesUnavailable (2),
+ requestedLinkConnectionBandwidthNotAvailable (3),
+ contractViolation (4),
+ invalidValue (5),
+ requiredParameterNotAvailable (6),
+ linkConnectionRequestCannotBeCompleted (7),
+ invalidLinkConnectionTerminationDate (8),
+ invalidLinkConnectionAvailabilityDate (9),
+ nonExistentLinkConnectionPoint (10),
+ ...
+}
+
+DeleteLCSError ::= ENUMERATED {
+ alreadyDeleted (0),
+ invalidCircuitNumber (1),
+ invalidServiceTerminationDate (2),
+ notBeingInAppropriateServiceAdministrativeState (3),
+ contractViolation (4),
+ ...
+}
+
+DeleteLinkConnectionError ::= ENUMERATED {
+ alreadyDeleted (0),
+ invalidLinkConnectionIdentifier (1),
+ invalidLinkConnectionTerminationDate (2),
+ notBeingInAppropriateLinkConnectionAdministrativeState (3),
+ contractViolation (4),
+ ...
+}
+
+DeleteSadError ::= ENUMERATED {
+ invalidSadId (0),
+ sadContainsSags (1),
+ ...
+}
+
+```
+
+```
+
+DeleteSagError ::= ENUMERATED {
+ invalidSagId (0),
+ invalidSadId (1),
+ ...
+}
+
+Diversity ::= CHOICE {
+ topologicalElements [1] SET OF TopologicalEntity,
+ -- the topological entities from which the circuit should be diverse --
+ otherCircuits [2] SET OF CircuitId,
+ -- other circuits from which the circuit should be diverse --
+ severalGroups [3] SET OF SEQUENCE {
+ numberOfCircuits INTEGER,
+ -- the number of circuits in the diverse group --
+ topologicalElements SET OF TopologicalEntity
+ -- the topological entities from which the circuits in the group should be diverse --
+ }
+}
+
+EquipmentManufacturer ::= PrintableString
+
+EquipmentType ::= PrintableString
+
+LcsModifyProgressProblemReport ::= SEQUENCE {
+ sourceIndicator [1] SourceIndicator OPTIONAL,
+ lcsModifyProgressProblemReportInfo [2] LcsModifyProgressProblemReportInfo,
+ notificationIdentifier [3] NotificationIdentifier OPTIONAL,
+ additionalText [4] AdditionalText OPTIONAL,
+ additionalInformation [5] AdditionalInformation OPTIONAL
+}
+
+LcsModifyProgressProblemReportInfo ::= ENUMERATED {
+ resourcesUnavailable (0),
+ requestedBandwidthNotAvailable (1),
+ ...
+}
+
+LcsRequestProgressProblemReport ::= SEQUENCE {
+ sourceIndicator [1] SourceIndicator OPTIONAL,
+ lcsRequestProgressProblemReportInfo [2] LcsRequestProgressProblemReportInfo,
+ notificationIdentifier [3] NotificationIdentifier OPTIONAL,
+ additionalText [4] AdditionalText OPTIONAL,
+ additionalInformation [5] AdditionalInformation OPTIONAL
+}
+
+LcsRequestProgressProblemReportInfo ::= ENUMERATED {
+ resourcesUnavailable (0),
+ requestedBandwidthNotAvailable (1),
+ serviceCannotBeCompleted (2),
+ invalidServiceAvailabilityDate (3),
+ invalidAddress (4),
+ nonExistentSap (5),
+ ...
+}
+
+```
+
+```
+
+LinkConnectionModifyProgressProblemReport ::= SEQUENCE {
+ sourceIndicator [1] SourceIndicator OPTIONAL,
+ linkConnectionModifyProgressProblemReportInfo [2]
+LinkConnectionModifyProgressProblemReportInfo,
+ notificationIdentifier [3] NotificationIdentifier OPTIONAL,
+ additionalText [4] AdditionalText OPTIONAL,
+ additionalInformation [5] AdditionalInformation OPTIONAL
+}
+
+LinkConnectionModifyProgressProblemReportInfo ::= ENUMERATED {
+ resourcesUnavailable (0),
+ requestedBandwidthNotAvailable (1),
+ ...
+}
+
+LinkConnectionRequestProgressProblemReport ::= SEQUENCE {
+ sourceIndicator [1] SourceIndicator OPTIONAL,
+ linkConnectionRequestProgressProblemReportInfo [2]
+LinkConnectionRequestProgressProblemReportInfo,
+ notificationIdentifier [3] NotificationIdentifier OPTIONAL,
+ additionalText [4] AdditionalText OPTIONAL,
+ additionalInformation [5] AdditionalInformation OPTIONAL
+}
+
+LinkConnectionRequestProgressProblemReportInfo ::= ENUMERATED {
+ resourcesUnavailable (0),
+ requestedLinkConnectionBandwidthNotAvailable (1),
+ linkConnectionRequestCannotBeCompleted (2),
+ nonExistentLinkConnectionPoint (3),
+ ...
+}
+
+ListOfSags ::= SET OF SagId
+
+ListOfSaps ::= SET OF Sap
+
+M3108FunctionalUnits ::= BIT STRING {
+ basicTransportService (0),
+ transportServiceOrder (1),
+ transportServiceOrderHistory (2),
+ transportServiceModify (3),
+ transportResourceVisibility (4)
+}
+
+ModelType ::= PrintableString
+
+ModifyLCSError ::= UpdateLCSError
+
+ModifyLinkConnectionError ::= ENUMERATED {
+ requiredBandwidthNotAvailable (0),
+ resourcesUnavailable (1),
+ unknownRoute (2),
+ serviceAdministrativeStateUnlocked (3),
+ ...
+}
+
+NumberOfUnspecifiedSaps ::= INTEGER (1..MAX)
+
+```
+
+```
+
+Name ::= PrintableString
+
+Number ::= INTEGER (0..MAX)
+
+Null ::= NULL
+
+OriginatingLocation ::= LocationAddress
+
+Procedure ::= CHOICE {
+ name PrintableString,
+ number INTEGER
+ }
+
+RemoveFromSagError ::= SEQUENCE {
+ sourceIndicator [1] SourceIndicator OPTIONAL,
+ removeFromSagErrorInfo [2] RemoveFromSagErrorInfo,
+ notificationIdentifier [3] NotificationIdentifier OPTIONAL,
+ additionalText [4] AdditionalText OPTIONAL,
+ additionalInformation [5] AdditionalInformation OPTIONAL
+}
+
+RemoveFromSagErrorInfo ::= ENUMERATED {
+ invalidSapId (0),
+ invalidSagId (1),
+ sapNotInAppropriateUsageState (2),
+ ...
+ }
+
+RequestedInitialServiceAdministrativeState ::= AdministrativeState
+
+RequestNumber ::= INTEGER (0..MAX)
+
+Route ::= SEQUENCE OF TopologicalEntity
+
+SadId ::= NameType
+
+SagId ::= NameType
+
+SagLocation ::= LocationAddress
+
+Sap ::= PrintableString
+
+ServiceRequestState ::= ENUMERATED {
+ pre-processing (0),
+ open-active (1),
+ pending (2),
+ closed (3)
+ }
+
+ServiceTerminationDate ::= CHOICE { time Time,
+ continous NULL}
+-- continous means that no termination date has been specified, this is the default value
+-- for ServiceTerminationDate
+
+Time ::= GeneralizedTime
+-- without fractions of seconds, with time zone indication. --
+
+TerminatingLocation ::= LocationAddress
+
+```
+
+```
+
+TopologicalEntity ::= CHOICE { name PrintableString,
+ object ObjectInstance
+ }
+
+UpdateLCSError ::= ENUMERATED {
+ invalidCpeType (0),
+ invalidSAP (1),
+ resourcesUnavailable (2),
+ requiredBandwidthNotAvailable (3),
+ unknownRoute (4),
+ contractViolation (5),
+ serviceAdministrativeStateUnlocked (6),
+ invalidCircuitNumber (7),
+ invalidServiceTerminationDate (8),
+ invalidSchedule (9),
+ invalidServiceAvailableState (10),
+ invalidProviderRequestNumber (11),
+ invalidAliasName (12),
+ ...
+ }
+
+UpdateLinkConnectionError ::= ENUMERATED {
+ invalidLinkConnectionPoint (0),
+ resourcesUnavailable (1),
+ requiredBandwidthNotAvailable (2),
+ contractViolation (3),
+ linkConnectionAdministrativeStateUnlocked (4),
+ invalidLinkConnectionIdentifier (5),
+ invalidLinkConnectionTerminationState (6),
+ invalidLinkConnectionAvailableState (7),
+ invalidProviderRequestNumber (8),
+ invalidLinkConnectionAliasName (9),
+ invalidSchedule (10),
+ ...
+ }
+
+UpdateServiceRequest ::= AttributeList
+
+UpdateServiceReply ::= SEQUENCE {
+ requestIdentifier SEQUENCE {
+ initialRequest RequestNumber OPTIONAL,
+ newRequest RequestNumber
+ } OPTIONAL,
+ alternateValues AttributeList OPTIONAL
+ }
+
+OriginatingLocationCP ::= TopologicalEntity
+
+OriginatingLocationSap ::= TopologicalEntity
+
+TerminatingLocationCP ::= TopologicalEntity
+
+TerminatingLocationSap ::= TopologicalEntity
+
+END
+
+```
+
+## 7 Functional units
+
+The services defined to support the functions specified in Recommendation M.3208.1 have been grouped into several functional units to allow negotiation of their use on an association (during association establishment), and to allow referencing by other Recommendations. Functional unit negotiation shall be performed as described in Recommendation X.701. The bit string defined in 6.12.2 shall be used to represent functional units. No TMN-specific user information is supplied during association release or aborts. Table 7-1 lists these functional units and their corresponding managed object classes and functions from Recommendation M.3208.1.
+
+**Table 7-1/M.3108.1 – Functional units, object classes, and functions**
+
+| Functional unit | Object class(es) | Function(s) (M.3208.1) |
+|-------------------------|-----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Basic transport service | networkR1 account (subclass of) transportService, lcs, linkConnectionService, serviceAccessGroup, serviceAccessDomain | Create LCS (3.3.3.1.1)
Delete LCS (3.3.3.1.2)
Report creation of LCS (3.3.3.2.1)
Report deletion of LCS (3.3.3.2.2)
Report LCS configuration change (3.3.3.2.3)
Control LCS administrative state (3.3.3.2.5)
Link connection configuration (3.3.3.3)
Create link connection service (3.3.3.3.1)
Delete link connection service (3.3.3.3.2)
Report creation of link connection service (3.3.3.4.1)
Report deletion of link connection service (3.3.3.4.2)
Report link connection service configuration change (3.3.3.4.3)
Control link connection service administrative state (3.3.3.4.5)
Reconfigurable leased circuit service configuration (3.3.3.5, 3.3.3.6)
Service access domain configuration set (3.3.3.7)
Create SAD (3.3.3.7.1)
Create SAG (3.3.3.7.2)
Delete SAG (3.3.3.7.3)
Add SAPs to SAG (3.3.3.7.4)
Remove SAPs from SAG (3.3.3.7.5) |
+| Transport service order | networkR1 account (subclass of) currentServiceRequest | Create service request (3.3.3.1.1, 3.3.3.3.1)
Cancel service request (3.3.3.1.4, 3.3.3.3.4)
Report change of service request parameters (3.3.3.2.4, 3.3.3.4.4)
Monitor progress of service request (3.3.3.2.7)
Report progress of service request (3.3.3.2.8)
Retrieve service request parameters (3.3.3.2.9, 3.3.3.4.9) |
+
+**Table 7-1/M.3108.1 – Functional units, object classes, and functions (concluded)**
+
+| Functional unit | Object class(es) | Function(s) (M.3208.1) |
+|---------------------------------|--------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------|
+| Transport service order history | networkR1 account (subclass of) serviceRequestHistoryRecord linkConnectionServiceRequestHistoryRecord, lcsRequestHistoryRecord | Modify service request (3.3.3.1.3) |
+| Transport service modify | networkR1 account (subclass of) serviceModifyRecord, linkConnectionServiceModifyRequest, lcsModifyRequest | Modify LCS (3.3.3.1.3)
Modify link connection service (3.3.3.3.3) |
+| Transport resource visibility | networkR1 account serviceAccessEquipmentView (additional resource subject to SLA) | Access equipment status (3.3.3.9)
Access equipment status update (3.3.3.9.1)
Access equipment status inquiry (3.3.3.9.2) |
+
+### 7.1 Basic transport service functional unit
+
+The basic transport service functional unit supports services (subject to service level agreement) on provisioned transport services with the exception of modification of the service characteristics. The service customer can modify parameters that are not affecting service, e.g. service customer contact.
+
+### 7.2 Transport service order functional unit
+
+The transport service order functional unit permits the service customer to issue requests for transport services and it makes visible the service order process. The service customer can provide missing parameters or change previously supplied parameters while the service order is in the pending or open/active states, i.e. not yet completed.
+
+### 7.3 Transport service order history functional unit
+
+The transport service order history functional unit allows the service provider to keep a history of all requests for modifications of the service order as issued by the service customer.
+
+### 7.4 Transport service modify functional unit
+
+The transport service modify functional unit allows the service customer to modify parameters of existing transport services.
+
+### 7.5 Transport resource visibility functional unit
+
+The transport service visibility functional unit provides visibility of transport resources. The set of transport resources made visible to the customer is not specified in this Recommendation and is in general subject to SLA.
+
+### 7.6 Negotiation of functional units
+
+This Recommendation assigns the following object identifier values:
+
+{itu-t (0) recommendation(0) m(31) m3108(3108) part1(1) protocolSupport(1) functionalUnitPackage(1)}
+
+as a value of the ASN.1 type FunctionalUnitPackageId defined in Recommendation X.701 to use for negotiating the following functional units:
+
+- 0 basic transport service
+- 1 transport service order
+- 2 transport service order history
+- 3 transport service modify
+- 4 transport resource visibility
+
+where the number identifies the bit positions in the BIT STRING assigned to the functional units, and the names referencing the functional units as defined in clause 7.
+
+Within the systems management application context, the mechanism for negotiating the functional units is described in Recommendation X.701.
+
+NOTE – The requirement to negotiate functional units is specified by the application context.
+
+## **8 Conformance**
+
+### **8.1 Static conformance**
+
+A system claiming conformance to this Recommendation shall:
+
+- a) support the role of manager or agent or both, with respect to the FUs defined or referenced in this Recommendation;
+- b) support the transfer syntax derived from the encoding rules specified in Recommendation X.209 and named {joint-iso-ccitt asn(1) basicEncoding(1)}, for the purpose of generating and/or interpreting the MAPDUs defined by the abstract data types defined in this Recommendation for the role supported in a) above;
+- c) support at least one of the FUs defined in Table 7-1;
+- d) support the conformance requirements specified in Q.812 CMIP profile.
+
+### **8.2 Dynamic conformance**
+
+The system shall, for the role for which conformance is claimed, support the elements of procedure defined in:
+
+- Recommendation X.730 for the PT-GET, PT-CREATE, PT-DELETE, PT-SET services;
+- Recommendation X.730 for the object creation reporting and object deletion reporting, if the create delete notifications are specified in the objects supported;
+- Recommendation X.730 for the attribute value change reporting if the attribute value change notification is specified in the objects supported;
+- Recommendation X.731 for the state change reporting service if the state change reporting notification is specified in the objects supported.
+
+### **8.3 Conformance to managed object definitions**
+
+The managed objects supported by the open system for service provisioning shall comply with the syntax and semantics of the information model specified for the FUs to which conformance is claimed.
+
+## APPENDIX I
+
+### Protocol-independent object description
+
+This appendix provides a protocol-independent description of the objects in the information model.
+
+The protocol-independent description of the objects is based on the following template:
+
+- 1) **Unique name** (within a uniquely identified module).
+- 2) **Description**: general description of the object.
+- 3) **Business purpose description**: provides traceability to specific business needs in Recommendation M.3208.1; traceability is provided through the title of the appropriate clause in Recommendation M.3208.1 and/or the number of the appropriate clause in Recommendation M.3208.1 enclosed in square brackets. In general, different combinations of MOs can support the same generic business need. The selection of the specific MOs in support of a management function is a local matter that may depend on local business practices. Therefore, the traceability provided here is not complete; it points only to one or two functions in Recommendation M.3208.1 that may be supported by the MO. Appendix II provides a more complete listing of the MOs that may support each of the management functions in Recommendation M.3208.1.
+- 4) **Primary identifier**: the primary IDs for the modelling object.
+- 5) **Attributes**
+
+Attribute name: for ease of reading, the attribute name is given in plain English, e.g. Alias name rather than aliasName; if the object definition includes any packages that consist only of attributes and/or behaviours, such packages are listed as entries under this appendix, and the attributes within the package are listed in parenthesis after the **package name**.
+
+Access modes (R = read; W = write, update; S = set to default)
+
+Optional or Mandatory
+
+Description of the attribute.
+
+- 6) **Behaviour description**
+
+**Creation** When is the object created.
+
+**Read** When is the object read.
+
+**Update** When is the object updated.
+
+**Action** What actions are allowed on the object and when.
+
+**Deletion** When is the object deleted.
+
+**Notifications** Notifications emitted from the object.
+
+- 7) **Notes/Comment**
+
+For an object class that is a subclass of another object class, the inherited properties are not repeated. Only differences from the superclass are shown in the descriptions below.
+
+## I.1 Generic service request fragment
+
+### I.1.1 currentServiceRequest
+
+- 1) **Unique name:** currentServiceRequest.
+- 2) **Description:** Represents information elements that are common to all service requests and updates to service requests. It is used as a superclass for defining service-specific, instantiable managed objects representing requests for specific services.
+- 3) **Business purpose description:** Every information element (attribute, notification) in this object is listed in the "Create dedicated leased circuit service function" [3.3.3.1.1] in Recommendation M.3208.1; in particular, the attributes are listed under "Information Flow" [3.3.3.1.1.2]. However, since the currentServiceRequest object is designed a super class for service-specific objects, it does not contain all the information exchange listed in Recommendation M.3208.1 for "Create dedicated leased circuit service function".
+- 4) **Primary identifier:** providerRequestNumber.
+- 5) **Attributes**
+
+| Attribute name | Access mode | Optional/Mandatory | Description |
+|--------------------------------------|-------------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Provider request number | R | M | Unique identifier provided by the SP to identify the request. |
+| Request reception time | R | M | The time when the service request was received by the service provider. Used to establish an order among requests, and changes to requests. Such ordering may be needed since, in case of conflicting changes to a request, the most recent change request is effective. |
+| Initial service administrative state | R, W | O | The SC may specify the service administrative state when the service is created. Valid values are:
Unlocked – Indicating that the LCS is available for use (provides service) by the SC.
Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s).
See Figure 5/M.3208.1 for an explanation of the Service Administrative State Model.
|
+| Customer request number | R | O | Unique identifier provided by the SC to identify the request. |
+| Service termination date | R, W | O | The date at which the LCS will be made inactive.
If the SC provides a termination date and the SP does not return a date, the requested date is accepted. In case the SP cannot accept the date, an alternate date is provided.
|
+| Alias name | R, W | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. |
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|-------------------------------------|---------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Daily scheduling (intervals of day) | R, W | O | Allows the customer to specify during which periods of the day the service shall be available. |
+| Weekly scheduling (week mask) | R, W | O | Allows the customer to specify during which days of the week the service shall be available. |
+| External scheduler (schedule name) | R, W | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. |
+| Service availability status | R | O | |
+| Request sequence number | R | M | Allows the SP to "staple" together several changes to the same service request. |
+| Service type | R, W
(at create) | M | The type of leased circuit service offered by the SP. Service names are not subject to standardization and are defined by the contract between the SC and the SP. |
+| Service provider contact | R | M | The provider contact information for use by the SC in resolving questions or problems with the service. |
+| Service customer contact | R, W | M | The customer contact information for use by the SP in resolving questions or problems with the service. |
+| Service availability date | R, W | M | Date the service is due to be provisioned and placed in the requested Service Administrative State, as requested by the SC. |
+| Service request state | R | M | This parameter indicates that the request is in progress.
Valid values are:
pre-processing – Indicates that the service request is currently being checked for validity of request parameters.
open/active – Indicates that the service request is open and is being actively processed.
Pending – Indicating that the service request is deactivated for reasons such as waiting for additional information, completion of other supporting tasks. Activation from this pending state is required before processing can be continued.
Closed – Indicates the service request is closed either as a result of successful completion or error or because the request was cancelled.
See Figure 4/M.3208.1 for allowed state transitions. |
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|---------------------|-------------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service description | R, W
at create | O | The name of a profile of service characteristics (associated with the service type) defined and supported by the SP. Examples of the service characteristics that may be included in the profile are directionality, channelization, signalling options, protection, quality of service objectives, application, etc. Service values of this attribute are not subject to standardization and are defined by the contract.
If the requested service is not equal to the service provided by the SP, then the SP must supply the value; else, it is optional.
|
+
+6) **Behaviour description**
+
+- Creation** When the customer requests a service or changes the request.
+- Read** When the customer wants to know what is being requested, after any number of changes by the customer.
+- Update** When the customer decides to change (parts of) the request or as the processing of the request by the service provider proceeds and the status of the request evolves.
+- Action** An action allows the SC to update some of the attributes. If the updates are not feasible, the SP returns error messages. If agreed upon in the SLA, the action causes the SP to create an instance of a history record in order to log the action.
+- Deletion** When the service is made available to the customer, when the customer has requested cancellation of the service request and the request has been cancelled, when the service provider has determined that the service cannot be provided and has notified the customer thereof.
+- Notifications** Object creation, object deletion.
+
+7) **Notes/Comment**
+
+I.1.2 **serviceRequestHistoryRecord**
+
+- 1) **Unique name:** serviceRequestHistoryRecord.
+- 2) **Description:** This MO represents historical record of SC initiated change to a pending service request. Values of attributes of this MO are set by the SP at the time of creation, based on an action issued by the SC against a pending request. Values of attributes in this MO cannot be changed.
+- 3) **Business purpose:** This MO supports recording of generic information exchanged for the "Modify dedicated leased circuit service function" [3.3.3.1.3], in particular, the attributes in this MO correspond to information items listed in the "Information Flow" table [3.3.3.1.3.2].
+- 4) **Primary identifier:** requestSequenceNumber.
+
+## 5) Attributes
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|--------------------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Provider request number | R | M | Unique identifier provided by the SP to identify the request. |
+| Request reception time | R | M | The time when the service request was received by the service provider. Used to establish an order among requests, and changes to requests. Such ordering may be needed since in case of conflicting changes to a request the most recent change request is effective. |
+| Initial service administrative state | R | O | The SC may specify the service administrative state when the service is created. Valid values are:
Unlocked – Indicating that the LCS is available for use (provides service) by the SC.
Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s).
See Figure 5/M.3208.1 for an explanation of the Service Administrative State Model. |
+| Service termination date | R | O | The date at which the LCS will be made inactive. If the SC provides a termination date and the SP does not return a date, the requested date is accepted. In case the SP cannot accept the date, an alternate date is provided. |
+| Alias name | R | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. |
+| Daily scheduling (intervals of day) | R | O | Allows the customer to specify during which periods of the day the service shall be available. |
+| Weekly scheduling (week mask) | R | O | Allows the customer to specify during which days of the week the service shall be available. |
+| External scheduler (schedule name) | R | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. |
+| Service customer contact | R | O | The customer contact information for use by the SP in resolving questions or problems with the service. |
+| Service availability date | R | O | Date the service is due to be provisioned and placed in the requested Service Administrative State. |
+| Service description | R | O | |
+| Service type | R | O | |
+
+6) **Behaviour description**
+
+**Creation** By SP when SC wants to modify a request for service.
+
+**Read** When the SC wants to verify what changes in the service request were requested.
+
+**Update**
+
+**Action**
+
+**Deletion** When the service is provided or when the SP notifies the SC that the requested service cannot be provided.
+
+**Notifications** Object creation and object deletion.
+
+7) **Notes/Comment**
+
+**I.1.3 serviceModifyRequest**
+
+1) **Unique name:** serviceModifyRequest.
+
+2) **Description:** This MO represents SC's request to modify an existing service. It is a superclass from which service-specific subclasses are derived. When changes to the service occur as a result of such a modification request, or for any other reason, the MO representing the affected service (e.g. lcs or link connection service) will issue the appropriate attribute value change notifications. After all the modifications requested by the SC through this MO have been resolved, this MO instance will be deleted and a notification of its deletion shall be sent to the SC.
+
+3) **Business purpose:** This MO represents generic information exchanged for the purpose of modifying an existing service, as described in "Modify dedicated leased circuit service function" [3.3.3.1.3], in particular, attributes in this MO correspond to generic information items in "Information Flow" [3.3.3.1.3.2].
+
+4) **Primary identifier:** provider request number.
+
+5) **Attributes**
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|-------------------------|------------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Provider request number | R | M | Unique identifier provided by the SP to identify the request. |
+| Request reception time | R | M | The time when the service request was received by the service provider. Used to establish an order among requests, and changes to requests. Such ordering may be needed since in case of conflicting changes to a request the most recent change request is effective. |
+| Service request state | R | M | |
+| Service instance | R | M | |
+| Alias name | R, W
(at object creation) | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. |
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|----------------------------------------|------------------------------|------------------------|------------------------------------------------------------------------------------------------------------|
+| Daily scheduling
(intervals of day) | R, W
(at object creation) | O | Allows the customer to specify during which periods of the day the service shall be available. |
+| Weekly scheduling
(week mask) | R, W
(at object creation) | O | Allows the customer to specify during which days of the week the service shall be available. |
+| External scheduler
(schedule name) | R, W
(at object creation) | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. |
+| Service customer contact | R, W
(at object creation) | O | The customer contact information for use by the SP in resolving questions or problems with the service. |
+| Availability status | R, W
(at object creation) | O | |
+
+## 6) Behaviour description
+
+**Creation** When a change to an existing service is requested.
+
+**Read** When the SC wishes to verify what changes were requested or what is the status of the request.
+
+### Update
+
+### Action
+
+**Deletion** When the requested changes have been performed by the SP or when the SP reports to the SC that the requested changes cannot be performed.
+
+**Notifications** Object creation and object deletion.
+
+## 7) Notes/Comment
+
+## I.2 LCS request fragment
+
+### I.2.1 currentLcsRequest
+
+1) **Unique name:** currentLcsRequest.
+
+2) **Description:** This instantiable MO represents an SC request for LCS.
+
+3) **Business purpose:** Every information element (attribute, notification) in this object is listed in the "Create dedicated leased circuit service function" [3.3.3.1.1] in Recommendation M.3208.1, in particular, the attributes are listed under "Information Flow" [3.3.3.1.1.2].
+
+4) **Primary identifier:** See currentServiceRequest.
+
+5) **Attributes:** See currentServiceRequest, plus:
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|--------------------------|--------------------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Originating location | R, W
(at create only) | M | Physical location (e.g. street address) where the LCS originates. |
+| Terminating location | R, W
(at create only) | M | Physical location (e.g. street address) where the LCS terminates. |
+| Quantity | R, W | O | The number of LCSs to be generated by the SP. |
+| Bandwidth | R, W | O | The bandwidth to be provided by the SP. |
+| Diversity | R, W | O | Diversity may be specified with respect to existing leased circuit(s) by identification of leased circuit(s) from which this (these) new leased circuit(s) shall be diverse, or by identification of the set of topological entities from which this (these) new leased circuit(s) shall be diverse.
When more than one leased circuit is requested, diversity may be specified within the request. In this case, the SC specifies the number of diverse groups and the number of circuits within each group, and/or a set of topological entities. |
+| Route | R, W | O | A sequence of topological entities over which LCS is provided (i.e. connection points, links, subnetworks). The SP may associate user-friendly names (i.e. city names) with such topological entities. |
+| Originating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit. |
+| Terminating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit. |
+| Originating location SAP | R, W | O | Access point where the leased circuit service originates. |
+| Terminating location SAP | R, W | O | Access point where the leased circuit service terminates. |
+
+6) **Behaviour description**
+
+**Creation** When the SC requests an LCS.
+
+**Read** When the SC wants to verify the LCS request.
+
+**Update** When the SC wants to change information in the LCS request or when the SP wants to update information in the LCS request.
+
+**Action** When the SC wants to change information in the LCS.
+
+**Deletion** When the SP provides the requested LCS to the SC or when the SP reports to the SC that the requested LCS cannot be provided.
+
+**Notifications** Object creation, object deletion, attribute value change, report problems in progressing the LCS request.
+
+- 7) **Notes/Comment**
+
+#### **I.2.2 lcsRequestHistoryRecord**
+
+- 1) **Unique name:** lcsRequestHistoryRecord.
+- 2) **Description:** This MO provides a historical record of changes to a pending LCS request by the SC.
+- 3) **Business purpose:** This MO supports the "Report change of leased circuit service request parameter function" [3.3.3.2.4], in particular, information items in "Information Flow" [3.3.3.2.4.2] and "Retrieve leased circuit service request parameters function [3.3.3.2.9], in particular, information in "Information Flow" [3.3.3.2.9.2].
+- 4) **Primary identifier:** See currentLcsRequest.
+- 5) **Attributes:** See currentLcsRequest, but the attribute values cannot change.
+- 6) **Behaviour description**
+
+| | |
+|----------------------|------------------------------------------------------------------------------------------------------------|
+| Creation | When the SC requests LCS or makes changes to a pending LCS request changes to an LCS request. |
+| Read | When the SC wishes to know the current information in the LCS request. |
+| Update | |
+| Action | |
+| Deletion | When the service is provided or when the SP notifies the SC that the requested service cannot be provided. |
+| Notifications | Object creation and object deletion. |
+- 7) **Notes/Comment**
+
+#### **I.2.3 lcsModifyRequestRecord**
+
+- 1) **Unique name:** lcsModifyRequestRecord.
+- 2) **Description:** This MO represents a request to modify an existing LCS.
+- 3) **Business purpose:** This MO represents information exchanged for the purpose of modifying an existing LCS, as described in "Modify dedicated leased circuit service function" [3.3.3.1.3], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.1.3.2].
+- 4) **Primary identifier:** request sequence number.
+
+5) **Attributes:** See serviceModifyRequestRecord, plus:
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|--------------------------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Bandwidth | R, W | O | The bandwidth to be provided by the SP. |
+| Diversity | R, W | O | Diversity may be specified with respect to existing leased circuit(s) by identification of leased circuit(s) from which this (these) new leased circuit(s) shall be diverse, or by identification of the set of topological entities from which this (these) new leased circuit(s) shall be diverse.
When more than one leased circuit is requested, diversity may be specified within the request. In this case, the SC specifies the number of diverse groups and the number of circuits within each group, and/or a set of topological entities. |
+| Route | R, W | O | A sequence of topological entities over which LCS is provided (i.e. connection points, links, subnetworks). The SP may associate user-friendly names (i.e. city names) with such topological entities. |
+| Originating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit. |
+| Terminating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit. |
+
+6) **Behaviour description**
+
+**Creation** When the SC wants to change an existing LCS.
+
+**Read** When the SC wants to verify information in a request to change an existing LCS.
+
+**Update**
+
+**Action**
+
+**Deletion** When the requested changes have been made by the SP or when the SP reports to the SC that the requested changes cannot be performed.
+
+**Notifications** Object creation, object deletion, progress problem report.
+
+7) **Notes/Comment**
+
+### I.3 Link connection service request fragment
+
+#### I.3.1 currentLinkConnectionServiceRequest
+
+1) **Unique name:** currentLinkConnectionServiceRequest.
+
+2) **Description:** This instantiable MO represents an SC request for a link connection.
+
+3) **Business purpose:** This MO represents information specified in "Create link connection function" [3.3.3.3.1], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.3.1.2].
+
+4) **Primary identifier:** provider request number.
+
+5) **Attributes:** See currentServiceRequest, plus:
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|-------------------------|-------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Bandwidth | R, W | O | The bandwidth to be provided by the SP. |
+| Originating location CP | R, W | M | CP or SN, where the Link Connection originates. Must exist prior to provisioning. The SC may not know the name at the time of the request. SP must provide the name of the CP to the SC.
SP cannot provision the service unless the CP is known.
The SC must provide either the originating or terminating location connection point or both.
If one of the points is at the customer premises, that point must be provided by the SC.
If one of the points is in a network of a service provider other than the one receiving this request, it must be provided by the SC.
If the link connection point name is not provided by the SC in the request and the response indicates the completion of the LC and the SC did not provide it in the request, then the value of this parameter must be provided by the SP in the response.
|
+| Terminating location CP | R, W | M | CP or SN, where the link connection terminates. Must exist prior to provisioning. The SC may not know the name at the time of the request. SP must provide the name of the CP to the SC.
SP cannot provision the service unless the CP is known.
If the link connection point name is not provided by the SC in the request and the response indicates the completion of the LC and the SC did not provide it in the request, then the value of this parameter must be provided by the SP in the response.
|
+
+6) **Behaviour description**
+
+**Creation** When the SC requests a link connection.
+
+**Read** When the SC wants to verify a link connection request.
+
+**Update** When the SC wants to change a link connection request or when the SP has additional information for the link connection request.
+
+**Action** When the SC wants to change a link connection request.
+
+**Deletion** When the requested link connection has been provided by the SP or when the SP reports to the SC that the requested link connection cannot be provided.
+
+**Notifications** Object creation, object deletion, attribute value change.
+
+7) **Notes/Comment**
+
+### I.3.2 linkConnectionServiceRequestHistoryRecord
+
+- 1) **Unique name:** linkConnectionServiceRequestHistoryRecord.
+- 2) **Description:** This MO represents a request to update either a previously issued request to create a link connection service, or a previous update against that link connection service request.
+- 3) **Business purpose:** This MO supports information exchange specified in "Modify link connection function" [3.3.3.3.3], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.3.2].
+- 4) **Primary identifier:** See serviceUpdateRequestRecord.
+- 5) **Attributes:** See serviceRequestHistoryRecord, plus the additional attributes for currentLinkConnectionServiceRequest.
+- 6) **Behaviour description**
+ - Creation** When the SC wants to change an existing link connection request.
+ - Read** When the SC wants to verify changes request to an existing link connection request.
+ - Update**
+ - Action**
+ - Deletion** When the requested link connection has been provided by the SP or when the SP reports to the SC that the requested link connection cannot be provided.
+ - Notifications** Object creation, object deletion.
+- 7) **Notes/Comment**
+
+### I.3.3 linkConnectionServiceModifyRequest
+
+- 1) **Unique name:** linkConnectionServiceModifyRequest.
+- 2) **Description:** This MO represents a request to modify an existing link connection.
+- 3) **Business purpose:** This MO supports information exchange specified in "Modify link connection function" [3.3.3.3.3], in particular, attributes in this MO correspond to information items in "Information Flow" [3.3.3.3.2].
+- 4) **Primary identifier:** See serviceModifyRequest.
+- 5) **Attributes:** See serviceModifyRequest plus:
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|----------------|-------------|------------------------|-----------------------------------------|
+| Bandwidth | R, W | O | The bandwidth to be provided by the SP. |
+
+- 6) **Behaviour description**
+ - Creation** When the SC wants to change an existing link connection.
+ - Read** When the SC wants to verify a request for changing an existing link connection.
+ - Update**
+ - Action**
+
+**Deletion** When the requested changes have been implemented by the SP or when the SP reports to the SC that the requested changes cannot be made.
+
+**Notifications** Object creation, object deletion, link connection modify progress problem report.
+
+7) **Notes/Comment**
+
+**I.4 Service fragment**
+
+**I.4.1 transportService**
+
+- 1) **Unique name:** transportService.
+- 2) **Description:** This MO represents a transport service. This MO class cannot be instantiated; service-specific subclasses of this class can be instantiated. Values of attributes of subclasses of this MO class can be set through management operations or through the creation of an instance of a service-specific subclass of the serviceModifyRequestRecord MO class. It is expected that only one of those two methods for changing values of attributes of subclasses of this MO class will be supported on any specific interface.
+- 3) **Business purpose:** This MO supports information exchange specified for "Retrieve link connection parameters by the service customer function" [3.3.3.4.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.4.6.2]. It further supports information exchange specified for "Retrieve leased circuit service parameters by the service customer function" [3.3.3.2.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.2.6.2].
+- 4) **Primary identifier:** service ID.
+- 5) **Attributes**
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|--------------------------|-------------|------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service ID | R | M | Circuit number or link connection identifier. |
+| Administrative state | R, W | M | Valid values are:
Unlocked – Indicating that the LCS is available for use (provides service) by the SC.
Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s).
See Figure 5/M.3208.1 for an explanation of the Service Administrative State Model. |
+| Operational state | R | M | Indicates if the service is operational. Default value if parameter is absent is enabled. |
+| Service type | R | M | Corresponds to service name in Recommendation M.3208.1. |
+| Service location list | R | M | Represents the originating and terminating locations in Recommendation M.3208.1. |
+| Bandwidth | R, W | M | |
+| Service provider contact | R | M | The provider contact information for use by the SC in resolving questions or problems with the service. |
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|-------------------------------------|---------------------------|------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Service customer contact | R, W | M | The customer contact information for use by the SP in resolving questions or problems with the service. |
+| Service availability date | R, W (at object creation) | M | Customer's requested start date, can be changed by the SP to the actual start date which may be different, depending on availability of SP's resources. |
+| Service termination date | R, W | M | Date at which the SC wishes to terminate the service. |
+| Alias name | R | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. |
+| Service description | R | O | Corresponds to service class in Recommendation M.3208.1. |
+| Availability status | R, W | O | |
+| Daily scheduling (intervals of day) | R, W | O | Allows the customer to specify during which periods of the day the service shall be available. |
+| Weekly scheduling (week mask) | R, W | O | Allows the customer to specify during which days of the week the service shall be available. |
+| External scheduler (schedule name) | R, W | O | Allows the customer to point to an external scheduler which specifies when the service shall be available. |
+
+## 6) Behaviour description
+
+**Creation** When a requested service is made available by the SP to the SC.
+
+**Read** When the SC wants to verify the service parameters.
+
+**Update** When the parameters of the service change as result of a SC request or SP initiative.
+
+### Action
+
+**Deletion** When the service is terminated.
+
+**Notifications** Object creation, object deletion, state change notification, attribute value change, quality of service alarm.
+
+## 7) Notes/Comment
+
+### I.4.2 lcs
+
+1) **Unique name:** lcs.
+
+2) **Description:** This instantiable MO represents an LCS.
+
+3) **Business purpose:** This MO supports information exchange specified for "Retrieve leased circuit service parameters by the service customer function" [3.3.3.2.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.2.6.2].
+
+4) **Primary identifier:** Service ID.
+
+5) **Attributes:** See transportService, plus the following attributes:
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|--------------------------|-------------|------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Diversity | R, W | O | Diversity may be specified with respect to existing leased circuit(s) by identification of leased circuit(s) from which this (these) new leased circuit(s) shall be diverse, or by identification of the set of topological entities from which this (these) new leased circuit(s) shall be diverse.
When more than one leased circuit is requested, diversity may be specified within the request. In this case, the SC specifies the number of diverse groups and the number of circuits within each group, and/or a set of topological entities. |
+| Route | R, W | O | A sequence of topological entities over which LCS is provided (i.e. connection points, links, subnetworks). The SP may associate user-friendly names (i.e. city names) with such topological entities. |
+| Originating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the originating point of the circuit. |
+| Terminating location CPE | R, W | O | Describes the type and make of the CPE that the LCS is connected to at the terminating point of the circuit. |
+| Originating location SAP | R, W | M | Access point where the leased circuit service originates. |
+| Terminating location SAP | R, W | M | Access point where the leased circuit service terminates. |
+
+6) **Behaviour description**
+
+**Creation** When a requested LCS is provided.
+
+**Read** When a SC wants to verify the parameters of an LCS.
+
+**Update** When a SC wants to change some characteristics of an LCS.
+
+**Action**
+
+**Deletion** When the LCS is terminated.
+
+**Notifications** See transportService.
+
+7) **Notes/Comment**
+
+#### I.4.3 linkConnectionService
+
+1) **Unique name:** linkConnectionService.
+
+2) **Description:** This instantiable MO represents a link connection service.
+
+3) **Business purpose:** This MO supports information exchange specified for "Retrieve link connection parameters by the service customer function" [3.3.3.4.6]; in particular, attributes in this MO correspond to some of the information items in "Information Flow" [3.3.3.4.6.2].
+
+4) **Primary identifier:** service ID.
+
+5) **Attributes:** See transportService, plus the following attributes:
+
+| Attribute name | Access mode | Optional/mandatory | Description |
+|-------------------------|-------------|--------------------|-------------------------------------------------|
+| Originating location CP | R, W | M | CP or SN, where the link connection originates. |
+| Terminating location CP | R, W | M | CP or SN, where the link connection terminates. |
+
+6) **Behaviour description**
+
+**Creation** When a requested link connection is made available by the SP to the SC.
+
+**Read** When the SC wants to verify the parameters of a link connection.
+
+**Update** When the SC wants to change a link connection or when the SP changes a link connection in response to the SC's request or due to other circumstances.
+
+**Action**
+
+**Deletion** When the link connection is terminated.
+
+**Notifications** See transportService.
+
+7) **Notes/Comment**
+
+**I.5 Reconfigurable service fragment**
+
+**I.5.1 serviceAccessDomain**
+
+1) **Unique name:** serviceAccessDomain.
+
+2) **Description:** This MO represents a Service Access Domain consisting of Service Access Groups having similar characteristics (e.g. supporting the same bandwidths).
+
+3) **Business purpose:** This MO represents information exchanged in "Create service access domain function" [3.3.3.7.1], in particular, its attributes correspond to information items in "Information Flow" [3.3.3.7.1.2].
+
+4) **Primary identifier:** provider request number (for SAD creation request) or sadId (for existing SAD).
+
+5) **Attributes**
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|--------------------------|-------------|------------------------|-------------------------------------------------------------------------------------------------------------------------------|
+| Provider request number | R | M | SP-specific identifier for a SAD create request. |
+| SAD identifier | R | M | Uniquely identifies the SAD. |
+| Service type | R | M | Corresponds to service name in Recommendation M.3208.1. |
+| Service provider contact | R | M | The provider contact information for use by the SC in resolving questions or problems with the service. |
+| Service customer contact | R, W | M | The customer contact information for use by the SP in resolving questions or problems with the service. |
+| Alias name | R | O | Allows the customer to assign a "user-friendly" name to the service; this information has no meaning to the service provider. |
+| Service description | R | O | Corresponds to service class in Recommendation M.3208.1. |
+| List of SAGs | R, W | M | List of the SAGs making up the SAD. |
+
+#### 6) Behaviour description
+
+**Creation** When a SAD is created.
+
+**Read** When the SC wants to verify the SAD's parameters.
+
+**Update** When SAGs are added/removed from the SAD.
+
+##### Action
+
+**Deletion** When a SAD is deleted.
+
+**Notifications** Notifications emitted from the object.
+
+#### 7) Notes/Comment
+
+### I.5.2 serviceAccessGroup
+
+1) **Unique name:** serviceAccessGroup.
+
+2) **Description:** This MO represents a Service Access Group consisting of Service Access Points having similar characteristics (e.g. supporting the same bandwidths).
+
+3) **Business purpose:** This MO represents information exchanged in "Create service access group function" [3.3.3.7.2]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.7.2.2]; it further represents information exchanged in "Add service access points to service access group function" [3.3.3.7.4]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.7.4.2].
+
+4) **Primary identifier:** SAG ID.
+
+5) **Attributes**
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|----------------------------|-------------|------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| SAG ID | R | M | Uniquely identifies the SAG. |
+| List of SAPs | R, W | M | Lists the SAPs that make up the SAG. |
+| SAG location | R | M | Physical location (e.g. street address) of the SAG. |
+| Alias name | R, W | O | User-friendly name for the SAG. |
+| Number of unspecified SAPs | R, W | O | Number of SAPs in the SAG that are not individually identified in the list of SAPs. |
+| Administrative state | R, W | O | Valid values are:
Unlocked – Indicating that the LCS is available for use (provides service) by the SC.
Locked – Indicating that the LCS is currently not providing service. The SC may use this value for pre-provisioning LCS(s). |
+
+#### 6) Behaviour description
+
+**Creation** When a SAG is created.
+
+**Read** When the SC wants to verify the parameters of the SAG.
+
+**Update** When SAPs are added/removed from the SAG or when other parameters are updated.
+
+##### Action
+
+**Deletion** When the SAG is terminated.
+
+##### Notifications
+
+#### 7) Notes/Comment
+
+### I.6 Resource fragment
+
+#### I.6.1 serviceAccessEquipment
+
+1) **Unique name:** serviceAccessEquipment.
+
+2) **Description:** The serviceAccessEquipment MO class represents customer-owned equipment that terminates the LCS.
+
+3) **Business purpose:** This MO represents information exchanged in "Access equipment status update function" [3.3.3.9.1]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.9.1.2]; it further represents information exchanged in "Access equipment status inquiry function" [3.3.3.9.2]; in particular, its attributes correspond to information items in "Information Flow" [3.3.3.9.2.2].
+
+4) **Primary identifier:** equipment ID.
+
+##### 5) Attributes
+
+| Attribute name | Access mode | Optional/
Mandatory | Description |
+|-------------------------------|-------------|------------------------|--------------------------------------------|
+| Equipment ID | R, W | M | SC-provided unique identifier for the CPE. |
+| SAP | R, W | M | SAP connected to the equipment. |
+| Location address | R, W | M | Physical location of the CPE. |
+| Administrative state | R, W | O | |
+| Operational state | R, W | O | |
+| Equipment type | R, W | O | |
+| Equipment manufacturer | R, W | O | |
+| Model type | R, W | O | |
+| Date of installation | R, W | O | |
+| Expected date of installation | R, W | O | |
+| Procedure | R, W | O | |
+
+#### 6) Behaviour description
+
+**Creation** When the CPE is connected to a LCS or to a link connection.
+
+**Read** When the SP wants to verify CPE parameters.
+
+**Update** When the SC changes the CPE.
+
+**Action**
+
+**Deletion** When the CPE is not connected to any service provided by the SP.
+
+**Notifications** Object creation, object deletion.
+
+#### 7) Notes/Comment
+
+### APPENDIX II
+
+#### Mapping of M.3208.1 functions into M.3108.1 MOs
+
+The mapping provided here refers to each function in Recommendation M.3208.1 by its clause number and title. Functions are grouped under the corresponding M.3208.1 function sets. For each M.3208.1 function, this mapping indicates one or more M.3108.1 MOs that may be used to support that function. In general, if more than one MO is indicated, then the decision on which MO(s) to select for that function is a local matter based on local business practices.
+
+NOTE – Recommendation M.3208.1 does not include an explicit function specifying that the SP needs to keep a log of the SC's changes to a pending service request. However, this functionality is implicit in the request sequence number that the SP issues for every SC's modification of a pending service request. This is reflected by the inclusion of the history records in the modify services in the following:
+
+| M.3208.1
subclause | M.3208.1
Functions | M.3108.1
Managed objects |
+|-------------------------------|-----------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------|
+| 3.3.3.1 | Dedicated leased circuit service configuration function set | |
+| 3.3.3.1.1 | Create dedicated leased circuit service function | currentLcsRequest |
+| 3.3.3.1.2 | Delete dedicated leased circuit service function | lcs |
+| 3.3.3.1.3 | Modify dedicated leased circuit service function | lcs
lcsModifyRequestRecord
currentLcsRequest
lcsRequestHistoryRecord |
+| 3.3.3.1.4 | Cancel dedicated leased circuit service request function | currentLcsRequest |
+| 3.3.3.2 | Dedicated leased circuit service status administration function set | |
+| 3.3.3.2.1 | Report creation of leased circuit service to service customer function | lcs |
+| 3.3.3.2.2 | Report deletion of leased circuit service to service customer function | lcs |
+| 3.3.3.2.3 | Report configuration change of leased circuit service parameters to service customer function | lcs |
+| 3.3.3.2.4 | Report change of leased circuit service request parameters function | currentLcsRequest |
+| 3.3.3.2.5 | Control leased circuit service administrative state by the service customer function | lcs |
+| 3.3.3.2.6 | Retrieve leased circuit service parameters by the service customer function | lcs |
+| 3.3.3.2.7 | Monitor progress of the leased circuit service request function | currentLcsRequest |
+| 3.3.3.2.8 | Report progress of the leased circuit service request function | currentLcsRequest |
+| 3.3.3.2.9 | Retrieve leased circuit service request parameters function | currentLcsRequest |
+| 3.3.3.3 | Link connection configuration service function set | currentLinkConnectionServiceRequest |
+| 3.3.3.3.1 | Create link connection function | linkConnectionService |
+| 3.3.3.3.2 | Delete link connection function | linkConnectionService |
+| 3.3.3.3.3 | Modify link connection function | linkConnectionServiceModifyRequestRecord
currentLinkConnectionServiceRequest
linkConnectionServiceRequestHistoryRecord
linkConnectionService |
+| 3.3.3.3.4 | Cancel link connection request function | currentLinkConnectionServiceRequest |
+
+| M.3208.1
subclause | M.3208.1
Functions | M.3108.1
Managed objects |
+|-------------------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
+| 3.3.3.4 | Link connection status administration function set | |
+| 3.3.3.4.1 | Report creation of link connection to service customer function | linkConnectionService |
+| 3.3.3.4.2 | Report deletion of link connection to service customer function | linkConnectionService |
+| 3.3.3.4.3 | Report configuration change of link connection parameters to service customer function | linkConnectionService |
+| 3.3.3.4.4 | Report change of link connection request parameters function | currentLinkConnectionServiceRequest
linkConnectionServiceModifyRequestRecord |
+| 3.3.3.4.5 | Control link connection administrative state by the service customer function | linkConnectionService |
+| 3.3.3.4.6 | Retrieve link connection parameters by the service customer function | linkConnectionService |
+| 3.3.3.4.7 | Monitor progress of the link connection request function | currentLinkConnectionServiceRequest |
+| 3.3.3.4.8 | Report progress of the link connection request function | currentLinkConnectionServiceRequest |
+| 3.3.3.4.9 | Retrieve link connection request parameters function | currentLinkConnectionServiceRequest |
+| 3.3.3.5 | Reconfigurable leased circuit service configuration function set | serviceAccessDomain
serviceAccessGroup |
+| 3.3.3.6 | Reconfigurable leased circuit service function set | serviceAccessDomain
serviceAccessGroup |
+| 3.3.3.7 | Service access domain configuration function set | serviceAccessDomain |
+| 3.3.3.7.1 | Create service access domain function | serviceAccessDomain |
+| 3.3.3.7.2 | Create service access group function | serviceAccessGroup |
+| 3.3.3.7.3 | Delete service access group function | serviceAccessGroup |
+| 3.3.3.7.4 | Add service access points to service access group function | serviceAccessGroup |
+| 3.3.3.7.5 | Remove service access points from service access group function | serviceAccessGroup |
+| 3.3.3.8 | Reconfigurable leased circuit service administration function set | see 3.3.3.2/M.3208.1 for all functions in this set |
+| 3.3.3.9 | Access equipment status administration function set | |
+| 3.3.3.9.1 | Access equipment status update function | serviceAccessEquipment |
+| 3.3.3.9.2 | Access equipment status inquiry function | serviceAccessEquipment |
+
+## APPENDIX III
+
+### UML diagrams for leased circuit service object model
+
+#### III.1 Introduction
+
+This appendix provides UML (Unified Modelling Language) diagrams to assist in explanation of the M.3208.1 leased circuit service object model.
+
+#### III.2 UML class diagrams for inheritance of M.3208.1 object classes
+
+In these diagrams (Figures III.1 to III.5), classes are shown as boxes with three sections, including: object class name in the top section; the attribute names in the second section (not filled in for these figures for readability); and access operations in the bottom section.
+
+The operation "get( )" is used in the class diagrams to denote that the class attributes are readable after an instance of that class is created.
+
+The operation "set( )" is used to denote that some (at least one) of the class attributes may be modified after an instance of that class is created.
+
+UML class diagrams use large open-headed arrows to indicate inheritance relationships. When a class is related to another by inheritance, the operations from the superclass (the one which has the large arrowhead touching it) are also supported for the inherited class, but are not repeated in the operation section of the class box.
+
+
+
+```
+classDiagram
+ class top
+ class serviceModifyRequest {
+ get()
+ delete()
+ }
+ class serviceRequestHistoryRecord {
+ get()
+ }
+ class currentServiceRequest {
+ get()
+ updateServiceRequest()
+ delete()
+ }
+ top <|-- serviceModifyRequest
+ top <|-- serviceRequestHistoryRecord
+ top <|-- currentServiceRequest
+```
+
+UML class diagram showing inheritance relationships for generic service request fragment. A 'top' class is at the top, with three classes below it: 'serviceModifyRequest', 'serviceRequestHistoryRecord', and 'currentServiceRequest'. Arrows point from each of these three classes up to the 'top' class. The 'serviceModifyRequest' class has 'get()' and 'delete()' operations. The 'serviceRequestHistoryRecord' class has 'get()' operation. The 'currentServiceRequest' class has 'get()', 'updateServiceRequest()', and 'delete()' operations. The 'top' class has three empty sections. A label 'T0410070-98' is at the bottom right.
+
+Figure III.1/M.3108.1 – Inheritance relationships for generic service request fragment
+
+
+
+```
+classDiagram
+ class currentServiceRequest {
+ get()
+ updateServiceRequest()
+ delete()
+ }
+ class serviceRequestHistoryRecord {
+ get()
+ }
+ class serviceModifyRequest {
+ get()
+ delete()
+ }
+ class currentLcsRequest
+ class lcsRequestHistoryRecord
+ class lcsModifyRequest
+ currentLcsRequest <|-- currentServiceRequest
+ lcsRequestHistoryRecord <|-- serviceRequestHistoryRecord
+ lcsModifyRequest <|-- serviceModifyRequest
+```
+
+UML class diagram showing inheritance relationships for LCS request fragment. Three classes are at the top: 'currentServiceRequest', 'serviceRequestHistoryRecord', and 'serviceModifyRequest'. Below each of these classes is another class: 'currentLcsRequest', 'lcsRequestHistoryRecord', and 'lcsModifyRequest'. Arrows point from each of these three bottom classes up to the corresponding top class. The 'currentServiceRequest' class has 'get()', 'updateServiceRequest()', and 'delete()' operations. The 'serviceRequestHistoryRecord' class has 'get()' operation. The 'serviceModifyRequest' class has 'get()' and 'delete()' operations. The bottom classes are empty. A label 'T0410080-98' is at the bottom right.
+
+Figure III.2/M.3108.1 – Inheritance relationships for LCS request fragment
+
+
+
+```
+
+classDiagram
+ class currentServiceRequest {
+ get()
+ updateServiceRequest()
+ delete()
+ }
+ class serviceRequestHistoryRecord {
+ get()
+ }
+ class serviceModifyRequest {
+ get()
+ delete()
+ }
+ class currentLinkConnectionServiceRequest
+ class linkConnectionServiceModifyRequest
+ class linkConnectionServiceRequestHistoryRecord
+
+ currentLinkConnectionServiceRequest --|> currentServiceRequest
+ linkConnectionServiceRequestHistoryRecord --|> serviceRequestHistoryRecord
+ linkConnectionServiceModifyRequest --|> serviceModifyRequest
+
+```
+
+T0410090-98
+
+UML class diagram showing inheritance relationships for link connection service request fragment. It includes classes: currentServiceRequest, serviceRequestHistoryRecord, serviceModifyRequest, currentLinkConnectionServiceRequest, and linkConnectionServiceModifyRequest. Operations include get(), updateServiceRequest(), and delete().
+
+**Figure III.3/M.3108.1 – Inheritance relationships for link connection service request fragment**
+
+
+
+```
+
+classDiagram
+ class top
+ class ServiceAccessDomain {
+ get()
+ set()
+ delete()
+ }
+ class ServiceAccessGroup {
+ get()
+ set()
+ delete()
+ }
+ ServiceAccessDomain --|> top
+ ServiceAccessGroup --|> top
+
+```
+
+Reconfigurable service fragment
+
+UML class diagram showing inheritance relationships for reconfigurable service fragment. It includes classes: top, ServiceAccessDomain, and ServiceAccessGroup. Operations include get(), set(), and delete().
+
+
+
+```
+
+classDiagram
+ class top
+ class ServiceAccessEquipmentView {
+ get()
+ set()
+ delete()
+ }
+ ServiceAccessEquipmentView --|> top
+
+```
+
+T0410100-98
+
+Resource fragment
+
+UML class diagram showing inheritance relationships for resource fragment. It includes classes: top and ServiceAccessEquipmentView. Operations include get(), set(), and delete().
+
+**Figure III.4/M.3108.1 – Inheritance relationships for resource fragment and reconfigurable service fragment**
+
+
+
+```
+
+classDiagram
+ top <|-- transportService
+ lcs <|-- transportService
+ linkConnectionService <|-- transportService
+ class top
+ class transportService {
+ get()
+ set()
+ delete()
+ }
+ class lcs
+ class linkConnectionService
+
+```
+
+T0410110-98
+
+UML class diagram showing inheritance relationships. A 'top' class is at the top. Below it is a 'transportService' class with methods get(), set(), and delete(). At the bottom are two classes, 'lcs' and 'linkConnectionService', which inherit from 'transportService'. A small code 'T0410110-98' is at the bottom right.
+
+**Figure III.5/M.3108.1 – Inheritance relationships for service fragment**
+
+### III.3 UML class diagrams for modelling relationships
+
+The possible relationships between instances are shown in UML class diagrams with associations (Figures III.6 and III.7). Containment relationships are denoted by a diamond headed line touching the parent (UML aggregation). Simple associations are shown with lines with roles indicates on the line ends. Relationship cardinalities are indicated by "0..\*" or "1..\*" tags on the end of the line representing a relationship.
+
+
+
+```
+
+classDiagram
+ account "0..*" <|-- currentLinkConnectionServiceRequest
+ currentLinkConnectionServiceRequest "1..*" <|-- linkConnectionServiceRequestHistoryRecord
+ class account {
+ get()
+ }
+ class currentLinkConnectionServiceRequest
+ class linkConnectionServiceRequestHistoryRecord
+
+```
+
+T0410120-98
+
+UML class diagram showing containment relationships. An 'account' class is at the top with a 'get()' method. Below it is a 'currentLinkConnectionServiceRequest' class. At the bottom is a 'linkConnectionServiceRequestHistoryRecord' class. Arrows with cardinalities point from the bottom class to the middle, and from the middle class to the top. A small code 'T0410120-98' is at the bottom right.
+
+**Figure III.6/M.3108.1 – Containment relationships for link connection service request with history records**
+
+
+
+```
+
+classDiagram
+ account <|-- currentLcsRequest : 0..*
+ currentLcsRequest <|-- lcsRequestHistoryRecord : 1..*
+ class account {
+ get()
+ }
+ class currentLcsRequest
+ class lcsRequestHistoryRecord
+
+```
+
+UML class diagram showing containment relationships for LCS request with history records. The diagram includes three classes: 'account', 'currentLcsRequest', and 'lcsRequestHistoryRecord'. 'account' has a method 'get()'. 'currentLcsRequest' has a 0..\* association with 'account'. 'lcsRequestHistoryRecord' has a 1..\* association with 'currentLcsRequest'. The identifier 'T0410130-98' is at the bottom right.
+
+**Figure III.7/M.3108.1 – Containment relationships for LCS request with history records**
+
+In Figure III.8, associations from account to service customer and service provider are shown, even though the classes "service customer" and "service provider" are not exposed as managed objects.
+
+
+
+```
+
+classDiagram
+ account "0..*" -- "0..*" serviceProvider : +accountProvider
+ account "0..*" -- "0..*" serviceCustomer : +accountCustomer
+ account "0..*" -- "0..*" ServiceAccessEquipmentView
+ account "0..*" -- "0..*" linkConnectionService
+ account "0..*" -- "0..*" lcs
+ account "0..*" -- "0..*" ServiceAccessDomain
+ account "0..*" -- "0..*" ServiceAccessGroup
+ ServiceAccessEquipmentView --> account
+ linkConnectionService --> account
+ lcs --> account
+ ServiceAccessDomain --> account
+ ServiceAccessGroup --> account
+ linkConnectionServiceModifyRequest --> linkConnectionService : 0..*
+ lcsModifyRequest --> lcs : 0..*
+ note for serviceProvider "These are not exposed as managed objects"
+ class account {
+ get()
+ }
+ class serviceProvider
+ class serviceCustomer
+ class ServiceAccessEquipmentView {
+ get()
+ set()
+ delete()
+ }
+ class linkConnectionService
+ class lcs
+ class ServiceAccessDomain {
+ get()
+ set()
+ delete()
+ }
+ class ServiceAccessGroup {
+ get()
+ set()
+ delete()
+ }
+ class linkConnectionServiceModifyRequest
+ class lcsModifyRequest
+
+```
+
+UML class diagram showing relationships beyond service creation and update. The diagram includes classes: 'serviceProvider', 'serviceCustomer', 'account', 'ServiceAccessEquipmentView', 'linkConnectionService', 'lcs', 'ServiceAccessDomain', 'ServiceAccessGroup', 'linkConnectionServiceModifyRequest', and 'lcsModifyRequest'. 'account' is central, with associations to 'serviceProvider' (+accountProvider), 'serviceCustomer' (+accountCustomer), 'ServiceAccessEquipmentView', 'linkConnectionService', 'lcs', 'ServiceAccessDomain', and 'ServiceAccessGroup'. 'ServiceAccessEquipmentView', 'ServiceAccessDomain', and 'ServiceAccessGroup' have methods 'get()', 'set()', and 'delete()'. 'linkConnectionServiceModifyRequest' and 'lcsModifyRequest' have associations with 'linkConnectionService' and 'lcs' respectively. A note indicates 'serviceProvider' and 'serviceCustomer' are not exposed as managed objects. The identifier 'T0410140-98' is at the bottom right.
+
+**Figure III.8/M.3108.1 – UML model for relationships beyond service creation and update**
+
+### III.4 UML class diagrams for modelling agent functionality
+
+Some UML classes are introduced (factories and notification dispatcher) to model the actions for creating objects and distributing notifications from objects (Figure III.9). Instances of these agent functionality classes appear in the sequence diagrams. When a notification operation invocation is made onto a notification dispatch object, all destinations which have registered interest will receive a copy of that notification. These final delivery flows are not shown in the sequence diagrams in III.5, since many object may be interested in receiving them.
+
+
+
+```
+classDiagram
+ class objectFactory {
+ ◆ create_currentLcsServiceRequest()
+ ◆ create_currentLinkConnectionServiceRequest()
+ ◆ create_lcsModifyRequest()
+ ◆ create_linkConnectionServiceModifyRequest()
+ ◆ create_lcs()
+ ◆ create_linkConnectionService()
+ ◆ create_serviceAccessDomain()
+ ◆ create_serviceAccessGroup()
+ ◆ create_serviceAccessEquipmentView()
+ }
+ note right of objectFactory: For OSI Systems Management, these capabilities are provided by the Agent.
+```
+
+UML class diagram for objectFactory class. The class box contains the name 'objectFactory' and a list of 10 operations, each preceded by a diamond symbol. A dashed line connects the class to a note box on the right containing text about OSI Systems Management.
+
+Factory with operations for customer to create service and request objects
+
+
+
+```
+classDiagram
+ class notificationDispatcher {
+ ◆ objectCreation()
+ ◆ attributeValueChange()
+ ◆ objectDeletion()
+ ◆ lcsModifyProgressProblemReport()
+ ◆ lcsRequestProgressProblemReport()
+ ◆ linkConnectionModifyProgressProblemReport()
+ ◆ linkConnectionRequestProgressProblemReport()
+ }
+ note right of notificationDispatcher: For OSI Systems Management, these capabilities are provided by Event Forwarding.
+```
+
+UML class diagram for notificationDispatcher class. The class box contains the name 'notificationDispatcher' and a list of 7 operations, each preceded by a diamond symbol. A dashed line connects the class to a note box on the right containing text about OSI Systems Management and Event Forwarding.
+
+Notification Dispatcher to receive and distribute notifications
+
+T0410150-98
+
+**Figure III.9/M.3108.1 – UML model for agent functions (creating objects and disseminating notifications)**
+
+### III.5 UML sequence diagrams to illustrate scenarios of object usage
+
+The sequence diagrams (Figures III.10 to III.15) in this subclause illustrate various scenarios discussed in the overview in clause 5.
+
+The message flows from the notification dispatcher to the ultimate registered destinations are not shown in these diagrams. It would be normal for the customer (as well as other objects) to be a registered recipient for the notifications shown in these sequence diagrams).
+
+
+
+```
+sequenceDiagram
+ participant customer
+ participant notification Dispatcher
+ participant objectFactory
+ participant lcs
+
+ Note right of lcs: Successful creation of LCS
+ customer->>objectFactory: 1: create_lcs()
+ objectFactory-->>customer: 2: createResponse
+ objectFactory->>lcs: 3: objectCreation()
+ Note right of lcs: Customer reads attribute values
+ customer->>lcs: 4: get()
+ lcs-->>customer: 5: getResponse
+ customer->>lcs: 6: set()
+ Note right of lcs: Customer sets service termination date
+ lcs-->>customer: 7: setResponse
+ Note right of lcs: Provider terminates lcs at termination date
+ lcs->>objectFactory: 8: objectDeletion()
+```
+
+T0410160-98
+
+UML sequence diagram for explicit LCS create and automatic termination. Lifelines: customer, notification Dispatcher, objectFactory, lcs. The diagram shows 8 messages: 1. create\_lcs(), 2. createResponse, 3. objectCreation(), 4. get(), 5. getResponse, 6. set(), 7. setResponse, 8. objectDeletion(). Annotations explain each step: Successful creation of LCS, Customer reads attribute values, Customer sets service termination date, Provider terminates lcs at termination date.
+
+**Figure III.10/M.3108.1 – Sequence diagram for explicit LCS create and automatic termination**
+
+
+
+```
+
+sequenceDiagram
+ participant customer
+ participant notificationDispatcher
+ participant objectFactory
+ participant currentLcsRequest
+ participant lcs
+
+ Note right of lcs: Successful request creation
+ customer->>objectFactory: 1: create_currentLcsServiceRequest()
+ objectFactory->>notificationDispatcher: 2: createResponse
+ Note right of lcs: Customer reads current request
+ customer->>currentLcsRequest: 3: get()
+ currentLcsRequest->>notificationDispatcher: 4: getResponse
+ Note right of lcs: Provider changes request values
+ lcs->>notificationDispatcher: 5: attributeValueChange()
+ Note right of lcs: Provider instantiates lcs and destroys
+ objectFactory->>notificationDispatcher: 6: objectCreation()
+ notificationDispatcher->>currentLcsRequest: 7: objectDeletion()
+ Note right of lcs: Customer reads lcs attribute
+ customer->>currentLcsRequest: 8: get()
+ currentLcsRequest->>customer: 9: getResponse
+ Note right of lcs: customer terminates lcs
+ customer->>currentLcsRequest: 10: delete()
+ currentLcsRequest->>customer: 11: deleteResponse
+ lcs->>notificationDispatcher: 12: objectDeletion()
+
+```
+
+The sequence diagram illustrates the interaction for instantiating an LCS. It begins with the customer sending a `create_currentLcsServiceRequest()` message to the objectFactory, which responds with `createResponse` to the notificationDispatcher. A note indicates this is a 'Successful request creation'. Next, the customer sends a `get()` message to the currentLcsRequest, which responds with `getResponse` to the notificationDispatcher; a note indicates the 'Customer reads current request'. The lcs lifeline then sends an `attributeValueChange()` message to the notificationDispatcher, with a note that the 'Provider changes request values'. This is followed by `objectCreation()` from objectFactory to notificationDispatcher and `objectDeletion()` from notificationDispatcher to currentLcsRequest, with a note that the 'Provider instantiates lcs and destroys'. The customer then sends another `get()` message to currentLcsRequest, which responds with `getResponse` directly to the customer; a note indicates the 'Customer reads lcs attribute'. Finally, the customer sends a `delete()` message to currentLcsRequest, which responds with `deleteResponse` to the customer; a note indicates the 'customer terminates lcs'. The lcs lifeline sends a final `objectDeletion()` message to the notificationDispatcher.
+
+UML Sequence diagram for instantiation of LCS using request and explicit deletion. Lifelines: customer, notificationDispatcher, objectFactory, currentLcsRequest, lcs. The diagram shows 12 messages with associated notes explaining each step.
+
+T0410170-98
+
+**Figure III.11/M.3108.1 – Sequence diagram for instantiation of LCS using request and explicit deletion**
+
+
+
+```
+
+sequenceDiagram
+ participant customer
+ participant notification Dispatcher
+ participant object Factory
+ participant currentLcs Request
+ participant lcsRequest HistoryRec1
+ participant lcsRequest HistoryRec2
+ participant lcs
+
+ Note right of lcs: Successful creation of LCS request and history record 1
+ customer->>object Factory: 1: create_currentLcsServiceRequest()
+ object Factory-->>notification Dispatcher: 2: createResponse
+ notification Dispatcher-->>customer:
+ object Factory->>lcsRequest HistoryRec1: 3: objectCreation()
+ customer->>currentLcs Request: 4: get()
+ currentLcs Request-->>notification Dispatcher: 5: getResponse
+ notification Dispatcher-->>customer:
+ currentLcs Request->>notification Dispatcher: 6: attributeValueChange()
+ Note right of lcs: Customer reads request
+ customer->>lcsRequest HistoryRec1: 7: get()
+ lcsRequest HistoryRec1-->>notification Dispatcher: 8: getResponse
+ notification Dispatcher-->>customer:
+ Note right of lcs: Provider changes a requested value
+ customer->>currentLcs Request: 9: updateServiceRequest()
+ currentLcs Request-->>notification Dispatcher: 10: updateResponse
+ notification Dispatcher-->>customer:
+ Note right of lcs: Customer reads original request
+ currentLcs Request->>notification Dispatcher: 11: attributeValueChange()
+ Note right of lcs: Customer updates request causing history record 2
+ currentLcs Request->>lcsRequest HistoryRec2: 12: objectCreation()
+ currentLcs Request->>notification Dispatcher: 13: objectCreation()
+ currentLcs Request->>notification Dispatcher: 14: objectDeletion()
+ currentLcs Request->>lcsRequest HistoryRec1: 15: objectDeletion()
+ currentLcs Request->>notification Dispatcher: 16: objectDeletion()
+ Note right of lcs: Provider instantiates lcs then destroys request and history records
+ customer->>lcs: 17: get()
+ lcs-->>notification Dispatcher: 18: getResponse
+ notification Dispatcher-->>customer:
+ Note right of lcs: Customer reads lcs attributes
+
+```
+
+Sequence diagram for instantiation of LCS using request and history records. Lifelines: customer, notification Dispatcher, object Factory, currentLcs Request, lcsRequest HistoryRec1, lcsRequest HistoryRec2, lcs. The diagram shows 18 messages with associated callouts explaining the steps.
+
+T0410180-98
+
+Figure III.12/M.3108.1 – Sequence diagram for instantiation of LCS using request and history records
+
+
+
+```
+
+sequenceDiagram
+ participant customer
+ participant notification Dispatcher
+ participant object Factory
+ participant lcs
+ participant lcsModify Request
+
+ Note right of lcsModify Request: Customer reads lcs attribute values
+ customer->>lcs: 1: get()
+ lcs-->>customer: 2: getResponse
+ Note right of lcsModify Request: Customer changes settable lcs attributes, subject to SLA provisions
+ customer->>lcs: 3: set()
+ lcs-->>customer: 4: setResponse
+ lcs->>notification Dispatcher: 5: attributeValueChange()
+ Note right of lcsModify Request: Customer creates request to change lcs attributes subject to SLA provisions
+ customer->>object Factory: 6: create_lcsModifyRequest()
+ object Factory-->>customer: 7: createResponse
+ lcs->>lcsModify Request: 8: objectCreation()
+ Note right of lcsModify Request: Customer reads modify request
+ customer->>lcsModify Request: 9: get()
+ lcsModify Request-->>customer: 10: getResponse
+ Note right of lcsModify Request: Provider changes lcs attributes and destroys request
+ lcs->>notification Dispatcher: 11: attributeValueChange()
+ lcs->>notification Dispatcher: 12: objectDeletion()
+
+```
+
+T0410190-98
+
+Sequence diagram for modification of existing LCS. Lifelines: customer, notification Dispatcher, object Factory, lcs, lcsModify Request. The sequence shows the customer interacting with the lcs object to get and set attributes, then creating a lcsModifyRequest to change attributes, and finally getting the response and destroying the request.
+
+**Figure III.13/M.3108.1 – Sequence diagram for modification of existing LCS**
+
+
+
+```
+
+sequenceDiagram
+ participant customer
+ participant notification Dispatcher
+ participant objectFactory
+ participant currentLcs Request
+
+ Note right of currentLcs Request: Customer creates request
+ customer->>objectFactory: 1: create_currentLcsServiceRequest()
+ objectFactory-->>customer: 2: createResponse
+ Note right of currentLcs Request: Customer reads current request
+ customer->>currentLcs Request: 3: get()
+ currentLcs Request-->>customer: 4: getResponse
+ Note right of currentLcs Request: Progress problem notification
+ currentLcs Request->>notification Dispatcher: 5: lcsRequestProgressProblemReport()
+ Note right of currentLcs Request: Customer updates request
+ customer->>currentLcs Request: 6: updateServiceRequest()
+ currentLcs Request-->>customer: 7: updateResponse
+ Note right of currentLcs Request: Progress problem notification
+ currentLcs Request->>notification Dispatcher: 8: lcsRequestProgressProblemReport()
+ Note right of currentLcs Request: Customer cancels request
+ customer->>currentLcs Request: 9: delete()
+ currentLcs Request-->>customer: 10: deleteResponse
+ currentLcs Request->>notification Dispatcher: 11: objectDeletion()
+
+```
+
+T0410200-98
+
+Sequence diagram for unsuccessful LCS instantiation using request without history. Lifelines: customer, notification Dispatcher, objectFactory, currentLcs Request. The sequence shows the customer creating a currentLcsServiceRequest, getting a response, then interacting with the currentLcs Request object to get, update, and delete it, with progress notifications being sent.
+
+**Figure III.14/M.3108.1 – Sequence diagram for unsuccessful LCS instantiation using request without history**
+
+
+
+```
+
+sequenceDiagram
+ participant customer
+ participant notification Dispatcher
+ participant object Factory
+ participant lcs
+ participant lcsModify Request
+
+ Note right of lcsModify Request: Customer reads lcs attribute values
+ customer->>lcs: 1: get()
+ lcs-->>customer: 2: getResponse
+
+ Note right of lcsModify Request: Customer tries to set lcs attributes, without success
+ customer->>lcs: 3: set()
+ lcs-->>customer: 4: setErrorResponse
+
+ Note right of lcsModify Request: Customer creates request to change lcs attributes, subject to SLA provisions
+ customer->>object Factory: 5: create_lcsModifyRequest()
+ object Factory-->>customer: 6: createResponse
+
+ Note right of lcsModify Request: Notification of modify problem
+ object Factory->>notification Dispatcher: 7: objectCreation()
+ notification Dispatcher->>lcsModify Request: 8: lcsModifyProgressProblemReport()
+
+ Note right of lcsModify Request: Customer cancels modification request
+ customer->>lcsModify Request: 9: delete()
+ lcsModify Request-->>customer: 10: deleteResponse
+
+ Note right of lcsModify Request: Customer terminates lcs by explicit deletion
+ object Factory->>notification Dispatcher: 11: objectDeletion()
+ customer->>lcs: 12: delete()
+ lcs-->>customer: 13: deleteResponse
+ notification Dispatcher->>object Factory: 14: objectDeletion()
+
+```
+
+Sequence diagram for unsuccessful LCS modification followed by LCS deletion. Lifelines: customer, notification Dispatcher, object Factory, lcs, lcsModify Request. The diagram shows 14 messages. The modification attempt (set()) fails, returning an error response. The customer then creates a modification request, which results in notifications. Finally, the customer cancels the request and explicitly deletes the lcs object.
+
+T0410210-98
+
+**Figure III.15/M.3108.1 – Sequence diagram for unsuccessful LCS modification followed by LCS deletion**
+
+
+
+## ITU-T RECOMMENDATIONS SERIES
+
+- Series A Organization of the work of the ITU-T
+- Series B Means of expression: definitions, symbols, classification
+- Series C General telecommunication statistics
+- Series D General tariff principles
+- Series E Overall network operation, telephone service, service operation and human factors
+- Series F Non-telephone telecommunication services
+- Series G Transmission systems and media, digital systems and networks
+- Series H Audiovisual and multimedia systems
+- Series I Integrated services digital network
+- Series J Transmission of television, sound programme and other multimedia signals
+- Series K Protection against interference
+- Series L Construction, installation and protection of cables and other elements of outside plant
+- Series M TMN and network maintenance: international transmission systems, telephone circuits, telegraphy, facsimile and leased circuits**
+- Series N Maintenance: international sound programme and television transmission circuits
+- Series O Specifications of measuring equipment
+- Series P Telephone transmission quality, telephone installations, local line networks
+- Series Q Switching and signalling
+- Series R Telegraph transmission
+- Series S Telegraph services terminal equipment
+- Series T Terminals for telematic services
+- Series U Telegraph switching
+- Series V Data communication over the telephone network
+- Series X Data networks and open system communications
+- Series Y Global information infrastructure and Internet protocol aspects
+- Series Z Languages and general software aspects for telecommunication systems
\ No newline at end of file
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a326625a941cf3a036d72948beb7cd51403c1001
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/16152cf1d84aea10848758f51a91ff6a_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:d266933815a98f42e23eabda16e19bc77d87099be085f7de832227463e7d2854
+size 36601
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9652f7910b30c15c3b4fd1433cd478eb5ce0e82c
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/43837b056625d3d6ce615e4c02f163bb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:19c2a6bdd92debd8cac66775ce47d3858a43d5ee8d5cb98778d3af441599bea1
+size 54887
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ac295b1b0c7f14b1c5a33ef6682b1b017c812477
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/84a1d09fb489061482111515543b60dc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:37aed4fc114a39843438175326e0b7e1d09a9d6075723d82fea32040fd560ee4
+size 7192
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ec81cfa3d93578d493ad714ad530ace3a4a440bb
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/8fbdfc3d17fb1dae7b2d8f5a287fa9fc_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:869d120e0e46e4e642a8fb21b99554d600df93b0b56b04aa52ded258c76cf9ee
+size 33057
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e6054e6cdf2e7e208966c5d6d271a9301a8bfe87
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b28af4985cdef1e519e3aaf26561dcb3_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:48bcee396c2c295727dee1752d3222ac47f5f8223f245ca704846ea1374567d9
+size 12438
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..049c43b73ac5f6e5649e4be5e6476e807e102be1
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/b90144cfbb81a2d610d920240fda689d_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:c0d3154bb6b3a15c5d7e776b4adbdc02fde5fd39384def7a08ce2a1552fa21a4
+size 44018
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..9123bfc685c832a507fa99d3d65afac8abdcdaea
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/cfef993dcc8fb513de79eb1f93cf26ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:f97a3359b9f0e0a90f441af53d6d1bd5a4749845a611f9ef036e48d2a3c045d7
+size 49858
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dffc744f5569f61dbb1ad4d1cee1ebcc3f979bcd
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/df82d77a0d2637cbf2da9ea920a554fa_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:15474232a616738c1fed769a7b20e89e716dd76ddec67381d000c3f9e01085cc
+size 46616
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..060ca282e786a6ab22d478a434c9780b589fc262
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/f4fdd410cdb84df81274da55721e56fb_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:ec6f7f4d5a83e94cc843dc9c3fd8826a7df1e9dc161082ff77849b7d76de235c
+size 44540
diff --git a/marked/M/T-REC-M.3110.1-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..aa252597bd53cd14ee87ad961428d438d20c7204
--- /dev/null
+++ b/marked/M/T-REC-M.3110.1-202503-I_PDF-E/fa859e4e468bfb2710a94527f2c504af_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fe9b4140bcbbba3480ae9618fcb2cf9fa7e8cc0336f885391557124b09344f81
+size 52477
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..c1629394c02f697f60ae954ad36bf274fa8082cb
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/0538daaa5583c23e17db3a12f2281a55_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:3763acd7a0ed56aa30f3f90468c1fb0cb54573eb9045bca3eddf8976b4f0f41d
+size 7219
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..fc35582281fc82f90ce4dba35cb8b9afd5594e4e
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/33ed1f9b27c7c21c797aa928b0f06851_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:44c78e9969761482c0a76a91ddb7629a8ac0b7fc559eac0693b1fa15d2dfe7c9
+size 42217
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..ae13d19a0c1fa5b2baf187d798eb1ab591c2fffc
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4801720824e4b5e2361a5564f91cfb70_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:85dd23a875ddb80652f4d4e3020637fb3da41047f6399ac6707db540705a1ef0
+size 39365
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..e79f451b79a2d2a77db7a08ec76901d472c3409b
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/4ee27dbf5ef12e7b58b0ef0937bc5a5e_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:070ad550fc0ca388dd40b622c21d6c67b492adaa6c8320107517c582f678006a
+size 24362
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..7fcf69bb869388c8c887989ae7cc0db9ae66df22
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/99bae07626f60f9ede10e2e387ef7051_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:fd8b4c97eb9078df182a714da0bdbd6c0d690d71696eea386bb555b879a89652
+size 9742
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..02e8b83783d5bdf2effe93fb869bb7dd688c8102
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/9f9386d5b3d6cbeb1ed104a799320ebf_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:58ac276e50f5ef9bafb24890d7cbc88d2284fc8b3eb04bbde64276e0d90d7c33
+size 35729
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..6fd8ba6edd98fa5eb76828ecf32555f34a68878a
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/af7916c89a458fdab6c3f443217388ae_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:db2927fc5aa26429fd6e2255601e33ee3094b35f77ee4d3829bc055b7eff6435
+size 48322
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..dbef8003ff5a11e2acd84ca290e2a55422608d64
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/bd671b21db63e6fdb2196e9b18502aac_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:7072718d1d89281029e8afda7a95614f954a19d124e43bea1187a8542babe14f
+size 25293
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..0adba9e482e187b2b720c5ff69dd9c80a4353baf
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/cab0834804fb031b43865554cc8d06ab_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:0d6f900200b6051c08d3abc97280269f58851f18624f64d21cd89937c21436fa
+size 47050
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..b62bed9fce23c3e7173f8237f9ae15897c7bd651
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/eefe19c5e14dc4d6c316b7f7fbb7d7d7_img.jpg
@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:41168dbf54b626044740ec7a5c5d03a0282abff135b8d5711a27843726d9c469
+size 34176
diff --git a/marked/M/T-REC-M.3111.1-202503-I_PDF-E/raw.md b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/raw.md
new file mode 100644
index 0000000000000000000000000000000000000000..85e92775a747ff15d0d24aa3494fa78177028245
--- /dev/null
+++ b/marked/M/T-REC-M.3111.1-202503-I_PDF-E/raw.md
@@ -0,0 +1,1015 @@
+
+
+# Recommendation**ITU-T M.3111.1 (03/2025)**
+
+SERIES M: Telecommunication management, including
+TMN and network maintenance
+
+Telecommunications management network
+
+---
+
+### **X-interface between telecom operation system and Internet e-commerce platform – Protocol neutral requirements**
+
+
+
+The logo of the International Telecommunication Union (ITU) is located in the bottom right corner. It features a blue globe with white lines representing latitude and longitude, and the letters 'ITU' in a bold, blue, sans-serif font superimposed on the globe.
+
+ITU logo
+
+## ITU-T M-SERIES RECOMMENDATIONS
+
+## Telecommunication management, including TMN and network maintenance
+
+| | |
+|---------------------------------------------------------------------------------|----------------------|
+| Introduction and general principles of maintenance and maintenance organization | M.10-M.299 |
+| International transmission systems | M.300-M.559 |
+| International telephone circuits | M.560-M.759 |
+| Common channel signalling systems | M.760-M.799 |
+| International telegraph systems and phototelegraph transmission | M.800-M.899 |
+| International leased group and supergroup links | M.900-M.999 |
+| International leased circuits | M.1000-M.1099 |
+| Mobile telecommunication systems and services | M.1100-M.1199 |
+| International public telephone network | M.1200-M.1299 |
+| International data transmission systems | M.1300-M.1399 |
+| Designations and information exchange | M.1400-M.1999 |
+| International transport network | M.2000-M.2999 |
+| Telecommunications management network | M.3000-M.3599 |
+| Integrated services digital networks | M.3600-M.3999 |
+| Common channel signalling systems | M.4000-M.4999 |
+
+For further details, please refer to the list of ITU-T Recommendations.
+
+# Recommendation ITU-T M.3111.1
+
+## X-interface between telecom operation system and Internet e-commerce platform – Protocol neutral requirements
+
+## Summary
+
+With the current trend of digital transformation, information and communications service providers (ICSPs) need to expand their e-commerce ecology to improve customer experience and increase opportunities for ICSPs to provide services to customers. Recommendation ITU-T M.3111.1 provides the protocol neutral requirements for the X-interface between the telecom operation system (TOS) and the Internet e-commerce platform (IEP), following the interface specification methodology presented in Recommendation ITU-T M.3020.
+
+## History \*
+
+| Edition | Recommendation | Approval | Study Group | Unique ID |
+|---------|----------------|------------|-------------|--------------------|
+| 1.0 | ITU-T M.3111.1 | 2025-03-29 | 2 | 11.1002/1000/16279 |
+
+## Keywords
+
+Internet e-commerce platform, management interface, protocol neutral, requirements, telecom operation system.
+
+---
+
+\* To access the Recommendation, type the URL in the address field of your web browser, followed by the Recommendation's unique ID.
+
+## FOREWORD
+
+The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, and information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis.
+
+The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics.
+
+The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1.
+
+In some areas of information technology which fall within ITU-T's purview, the necessary standards are prepared on a collaborative basis with ISO and IEC.
+
+## NOTE
+
+In this Recommendation, the expression "Administration" is used for conciseness to indicate both a telecommunication administration and a recognized operating agency.
+
+Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure, e.g., interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words "shall" or some other obligatory language such as "must" and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party.
+
+## INTELLECTUAL PROPERTY RIGHTS
+
+ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process.
+
+As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents/software copyrights, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the appropriate ITU-T databases available via the ITU-T website at .
+
+© ITU 2025
+
+All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU.
+
+## Table of Contents
+
+| | Page |
+|----------------------------------------------------------------------|------|
+| 1 Scope ..... | 1 |
+| 2 References..... | 1 |
+| 3 Definitions ..... | 1 |
+| 3.1 Terms defined elsewhere ..... | 1 |
+| 3.2 Terms defined in this Recommendation..... | 2 |
+| 4 Abbreviations and acronyms ..... | 2 |
+| 5 Conventions ..... | 3 |
+| 6 Concepts and background..... | 3 |
+| 7 Requirements for the X-interface between the TOS and the IEP ..... | 4 |
+| 7.1 Business level requirements ..... | 4 |
+| 7.2 Specification level requirements ..... | 9 |
+| Appendix I – Example of product classification catalogue ..... | 26 |
+| Bibliography..... | 28 |
+
+
+
+# Recommendation ITU-T M.3111.1
+
+## X-interface between telecom operation system and Internet e-commerce platform – Protocol neutral requirements
+
+# 1 Scope
+
+This Recommendation specifies the requirements for the X-interface between the telecom operation system (TOS) and the Internet e-commerce platform (IEP). In general, the interactions of the TOS and the IEP include product support and readiness, customer management, order handling, order bill invoice, product renewal and customer service. During these interactions, the exchange of information between the TOS and the IEP is required. This Recommendation focuses on the requirements of this interface which cover all of these interactions. The requirements are provided using the management interface specification methodology described in [ITU-T M.3020], in a protocol neutral manner.
+
+# 2 References
+
+The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation.
+
+[ITU-T M.3010] Recommendation ITU-T M.3010 (2000), *Principles for a telecommunications management network*.
+
+[ITU-T M.3020] Recommendation ITU-T M.3020 (2023), *Management interface specification methodology*.
+
+# 3 Definitions
+
+## 3.1 Terms defined elsewhere
+
+This Recommendation uses the following terms defined elsewhere:
+
+**3.1.1 customer** [b-ITU-T M.3050.1]: The customer buys products and services from the enterprise or receives free offers or services. A customer may be a person or a business.
+
+**3.1.2 e-commerce** [b-ITU-T M.3050.1]: e-commerce is Internet presence and business buying and selling transactions over digital media.
+
+**3.1.3 information and communications service provider (ICSP)** [b-ITU-T M.3050.1]: A service provider enterprise that sells information and/or communications services to other parties.
+
+**3.1.4 operation system** [ITU-T M.3010]: A physical block which performs operations systems functions (OSFs).
+
+**3.1.5 operation systems function (OSF)** [ITU-T M.3010]: A function block that processes information related to the telecommunications management for the purpose of monitoring/coordinating and/or controlling telecommunication functions including management functions (i.e., the TMN itself).
+
+**3.1.6 partner** [b-ITU-T M.3050.1]: A partner has a stronger profit and risk-sharing component in their business agreement with the enterprise than a supplier would have. A partner generally is more
+
+visible to the enterprise's customer than a supplier would be. A partner might be part of an alliance, a joint service offering, etc.
+
+**3.1.7 platform** [b-ITU-T X.1149]: A hardware or software system that serves as a foundation or base for realizing a certain functionality.
+
+**3.1.8 product** [b-ITU-T M.3050.1]: Product is what an entity (supplier) offers or provides to another entity (customer). Product may include service, processed material, software or hardware, or any combination thereof. A product may be tangible (e.g., goods) or intangible (e.g., concepts) or a combination thereof. However, a product ALWAYS includes a service component.
+
+**3.1.9 service provider** [b-ITU-T M.3050.1]: See under information and communications service provider (ICSP). Throughout this Recommendation, the terms "service provider" and "ICSP" are synonymous.
+
+**3.1.10 telecommunication service** [b-ITU-T M.60]: That which is offered by an Administration to its customers in order to satisfy a specific telecommunication requirement.
+
+**3.1.11 X interface** [ITU-T M.3010]: An interface applied at x reference points.
+
+**3.1.12 x reference points** [ITU-T M.3010]: A reference point located between OSF function blocks in different TMNs.
+
+## 3.2 Terms defined in this Recommendation
+
+This Recommendation defines the following terms:
+
+**3.2.1 stock keeping unit (SKU)**: The unit of measure in which the stocks of a material are managed, which is a distinct type of item for sale, purchase, or tracking in inventory (such as a product or service).
+
+NOTE – An example of SKU is an annual 300 Mbit/s home broadband package.
+
+**3.2.2 standard product unit (SPU)**: The unit of product aggregation, which is a set of reusable and easily retrievable standardized information that describes the characteristics of a class of products.
+
+NOTE 1 – An example of SPU is home broadband. The attribute of this SPU may include bandwidth: 300 Mbit/s / 1 000 Mbit/s, charging period: monthly / annual.
+
+NOTE 2 – One SPU may include multiple SKUs. In the above SPU example, there can be four SKUs. The first SKU is a 300 Mbit/s monthly home broadband package. The second SKU is a 300 Mbit/s annual home broadband package. The third SKU is a 1 000 Mbit/s monthly home broadband package. The fourth SKU is a 1 000 Mbit/s annual home broadband package.
+
+# 4 Abbreviations and acronyms
+
+This Recommendation uses the following abbreviations and acronyms:
+
+| | |
+|--------|-------------------------------------------------|
+| CM | Customer Management |
+| CS | Customer Service |
+| FS | Function Set |
+| ICSP | Information and Communications Service Provider |
+| IEP | Internet e-commerce Platform |
+| Mbit/s | Mega bits per second |
+| OBI | Order Bill Invoice |
+| OH | Order Handling |
+| OS | Operations System |
+
+| | |
+|-----|---------------------------------------|
+| OSF | Operations Systems Function |
+| PR | Product Renewal |
+| PSR | Product Support and Readiness |
+| SKU | Stock Keeping Unit |
+| SPU | Standard Product Unit |
+| TMN | Telecommunications Management Network |
+| TOS | Telecom Operation System |
+| URL | Uniform Resource Locator |
+
+# 5 Conventions
+
+In this Recommendation:
+
+The keywords "is required to" indicate a requirement which must be strictly followed and from which no deviation is permitted, if conformance to this Recommendation is to be claimed.
+
+The keywords "is recommended" indicate a requirement which is recommended but which is not absolutely required. Thus, this requirement need not be present to claim conformance.
+
+For the qualifiers of a use case in the specification-level requirements, "M" standards for "Mandatory" and "O" stands for "Optional".
+
+# 6 Concepts and background
+
+With the current trend of digital transformation, information and communications service providers (ICSPs) need to respond to customers' increased demands for superior customer services. They have therefore been expanding their ecological cooperation, especially with Internet companies, to broaden their e-business. An ICSP needs to launch product onto external Internet companies for new customer development and for customers to order product more conveniently.
+
+According to the market sales demand, the ICSP decides what products need to be published to an Internet e-commerce platform (IEP) for sale and what product related information needs to be sent across the interface between the telecom operation system (TOS) and the IEP. When the products in the IEP are ready for sale, customers can browse the product information, order the product in the IEP, request for billing invoices from the IEP and submit complaint problems to the IEP. Related information needs to be exchanged across the interface between the TOS and the IEP.
+
+As described in [ITU-T M.3010], the X-interface is used to interconnect two telecommunications management networks (TMNs) or to interconnect a TMN with other systems which accommodate a TMN-like interface. The interface between the TOS and the IEP specified in this Recommendation is an X-interface, as shown in Figure 1.
+
+
+
+```
+
+graph LR
+ TOS((TOS)) --- X((X-interface)) --- IEP((IEP))
+ M3111_1_25[M.3111.1(25)] --- IEP
+
+```
+
+Diagram showing the X-interface between the TOS and the IEP. Two circles labeled 'TOS' and 'IEP' are connected by a horizontal line. A small black dot on the line represents the interface, labeled 'X-interface' above it. Below the IEP circle is the text 'M.3111.1(25)'.
+
+**Figure 1 – Position of the X-interface between the TOS and the IEP**
+
+This Recommendation contains requirements for the X-interface between the TOS and the IEP. In general, the information that needs to be exchanged across this interface between the TOS and the IEP includes the following function set (FS): product support and readiness, customer management, order handling, order bill invoice (OBI), product renewal and customer service:
+
+- Product support and readiness FS ensures that the product from the ICSP is available and ready to support Internet presence and business for buying and selling transactions over the IEP.
+- Customer management FS ensures that customers from the IEP can complete the authentication and credit worthiness in the TOS.
+- Order handling FS ensures that order actions initiated by customers in the IEP, such as order submission, order status inquiry and order cancellation, can be issued to the TOS for handling, and that the TOS can respond to the order handling result.
+- Order bill invoice FS ensures that customers in the IEP can inquire and obtain bill invoices from the TOS.
+- Product renewal FS ensures that customers in the IEP can continue to order the product which is used previously by the customers.
+- Customer service FS ensures that customers in the IEP can initiate product consultation or complaints to the TOS.
+
+This interface can provide the means for creating common practices for ICSPs to launch products onto external e-commerce platforms and for customers to be able to order product of ICSPs from the IEP.
+
+# 7 Requirements for the X-interface between the TOS and the IEP
+
+## 7.1 Business level requirements
+
+### 7.1.1 Requirements
+
+The general requirements include:
+
+- product support and readiness (clause 7.1.1.1)
+- customer management (clause 7.1.1.2)
+- order handling (clause 7.1.1.3)
+- order bill invoice (clause 7.1.1.4)
+- product renewal (clause 7.1.1.5)
+- customer service (clause 7.1.1.6)
+
+#### 7.1.1.1 Product support and readiness FS
+
+| | |
+|-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| REQ-PSR-FUN-101 | The TOS is required to send the product classification catalogue to the IEP, so that the customer-oriented product catalogue in the IEP can be established more easily according to this product classification catalogue. An example of the catalogue is shown in Appendix I. |
+| REQ-PSR-FUN-102 | The TOS is required to send the product standard product unit (SPU) information to the IEP, so that the product SPU can be correlated to the appropriate catalogue item and then the product SKU can be correlated to the specific SPU in the IEP. |
+| REQ-PSR-FUN-103 | The TOS is required to send the product SKU information to the IEP, so that the SKU can be correlated to a specific SPU in the IEP. |
+
+#### 7.1.1.2 Customer management FS
+
+| | |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| REQ-CM-FUN-201 | The IEP is required to send the information of the newly created customer, who has ordered product in the IEP, to the TOS, so that the TOS can determine if this customer is new in its own system and needs to initiate real name authentication according to this information. |
+| REQ-CM-FUN-202 | The TOS is required to provide a real name authentication failure result back to the IEP, so that the IEP can require the customer to modify the customer newly created information. |
+| REQ-CM-FUN-203 | The TOS is required to provide the customer newly created success response to the IEP.
See Notes 1 and 2 for more details. |
+| REQ-CM-FUN-204 | The IEP is required to send the credit worthiness verification request of the customer, who has ordered product in the IEP, to the TOS, so that the TOS can verify the customer's credit worthiness. |
+
+NOTE 1 – a) Authentication should be performed. If the real name authentication succeeds, the new customer ID of the TOS will be created and sent back to the IEP for recording through this interface.
+
+b) The customer already existed in the TOS. In such cases, the customer may have already ordered some products in the telecommunication service hall offline. Then the TOS sends the existing customer ID of the TOS back to the IEP for recording through this interface. When this customer wants to order the TOS products in the future, he/she does not need to provide newly created information again.
+
+NOTE 2 – The IEP and the TOS have two different sets of customer IDs, which need to establish a mapping relationship of the two sets of customer IDs in both the IEP and the TOS, because the TOS does not use the IEP customer ID set for its own order process and other operation and management activities. When a customer orders a product in the IEP, the IEP will first decide whether the customer needs to provide newly created information to the TOS based on the customer ID of the TOS. If the customer ID of the TOS already existed in the IEP, the IEP will associate this customer's order to his/her customer ID of the TOS, and will send this customer's order information along with his/her customer ID of the TOS.
+
+##### 7.1.1.3 Order handling FS
+
+| | |
+|----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| REQ-OH-FUN-301 | The IEP is required to send the order information to the TOS, which has been submitted by the customer in the IEP. |
+| REQ-OH-FUN-302 | The TOS is required to send the order fulfilment result to the IEP, so that the customer will be informed whether the order fulfilment is successful or has failed. |
+| REQ-OH-FUN-303 | The IEP is required to send the order status inquiry to the TOS, so that the customer can track the process of the order handling. |
+| REQ-OH-FUN-304 | The IEP is required to send the cancel products in the order request to the TOS, so that the customer can cancel all the products in the order or part of the products in order before the order fulfilment is completed. |
+
+##### 7.1.1.4 Order bill invoice FS
+
+| | |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------|
+| REQ-OBI-FUN-401 | The IEP is recommended to send a bill invoice request to the TOS, so that the customer can inquire after the bill invoice in the IEP. |
+| REQ-OBI-FUN-402 | The TOS is recommended to provide a bill invoice response to the IEP. |
+
+##### 7.1.1.5 Product renewal FS
+
+| | |
+|----------------|--------------------------------------------------------------------------------------------------------------------------|
+| REQ-PR-FUN-501 | The IEP is required to send the product renewal order to the TOS, so that the customer can renew the product in the IEP. |
+| REQ-PR-FUN-502 | The TOS is required to provide the product renewal result to the IEP. |
+
+##### 7.1.1.6 Customer service FS
+
+| | |
+|----------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| REQ-CS-FUN-601 | The IEP is required to send service consulting initiated by the customer to the TOS, so that the customer's service consulting, which cannot be processed in the IEP, can be resolved in the TOS. |
+| REQ-CS-FUN-602 | The TOS is required to provide the response of the customer's service consulting to the IEP, so that the customer's service consulting can be resolved. |
+| REQ-CS-FUN-603 | The IEP is required to send the customer's problems and complaints to the TOS, which are categorized for the TOS to resolve, so that the TOS can perform root cause analysis and recover the problem. |
+| REQ-CS-FUN-604 | The TOS is required to provide the response of the customer's problems and complaints to the IEP, so that the resolution result of the problems and complaints can be conveyed to the customer. |
+
+#### 7.1.2 Actor roles
+
+Telecom operation system (TOS): The entity performing the service provider role.
+
+Internet e-commerce platform (IEP): The entity performing the partner role.
+
+#### 7.1.3 Telecommunication resources
+
+The managed network resources are viewed as relevant telecommunication resources in this Recommendation.
+
+### 7.1.4 High level use case diagrams
+
+The function sets of the X-interface between the TOS and the IEP contain: product support and readiness function set, customer management function set, order handling function set, order bill invoice function set, product renewal function set and customer service function set.
+
+Figure 2 shows the top-level use case.
+
+Figure 3 shows the high-level use cases for the product support and readiness function set.
+
+Figure 4 shows the high-level use cases for the customer management function set.
+
+Figure 5 shows the high-level use cases for the order handling function set.
+
+Figure 6 shows the high-level use cases for the order bill invoice function set.
+
+Figure 7 shows the high-level use cases for the product renewal function set.
+
+Figure 8 shows the high-level use cases for the customer service function set.
+
+
+
+Interfaces for TOS and IEP
+
+TOS
+
+IEP
+
+<>
+
+Product Support and Readiness\_FS
+
+<>
+
+Customer\_Management\_FS
+
+<>
+
+Order\_Handling\_FS
+
+<>
+
+Order\_Bill\_Invoice\_FS
+
+<>
+
+Product\_Renewal\_FS
+
+<>
+
+Customer\_Service\_FS
+
+M.3111.1(25)
+
+Diagram of Interface function sets for the TOS and the IEP overview. It shows a central interface node connected to TOS and IEP actors, with six included function sets: Product Support and Readiness\_FS, Customer\_Management\_FS, Order\_Handling\_FS, Order\_Bill\_Invoice\_FS, Product\_Renewal\_FS, and Customer\_Service\_FS.
+
+**Figure 2 – Interface function sets for the TOS and the IEP overview**
+
+
+
+Product Support and Readiness\_FS
+
+TOS
+
+IEP
+
+<>
+
+TOS sends product classification catalogue to IEP
+
+<>
+
+TOS sends product SPU information to IEP
+
+<>
+
+TOS sends product SKU information to IEP
+
+M.3111.1(25)
+
+Diagram of Product support and readiness FS. It shows a central interface node connected to TOS and IEP actors, with three included function sets: TOS sends product classification catalogue to IEP, TOS sends product SPU information to IEP, and TOS sends product SKU information to IEP.
+
+**Figure 3 – Product support and readiness FS**
+
+
+
+Customer\_Management\_FS
+
+TOS
+
+IEP
+
+<>
+
+IEP sends information of newly created customer to TOS
+
+<>
+
+TOS provides real name authentication failure result to IEP
+
+<>
+
+TOS provides customer newly created success response to IEP
+
+<>
+
+IEP sends customer's credit worthiness verification request to TOS
+
+M.3111.1(25)
+
+Diagram of Customer management FS. It shows a central interface node connected to TOS and IEP actors, with four included function sets: IEP sends information of newly created customer to TOS, TOS provides real name authentication failure result to IEP, TOS provides customer newly created success response to IEP, and IEP sends customer's credit worthiness verification request to TOS.
+
+**Figure 4 – Customer management FS**
+
+
+
+```
+
+usecaseDiagram
+ actor TOS
+ actor IEP
+ usecase Order_Handling_FS
+ TOS --> Order_Handling_FS
+ IEP --> Order_Handling_FS
+ Order_Handling_FS -.-> IEP_sends_the_information_of_order_to_TOS : <>
+ Order_Handling_FS -.-> TOS_sends_order_fulfilment_result_to_IEP : <>
+ Order_Handling_FS -.-> IEP_requests_the_order_status_from_TOS : <>
+ Order_Handling_FS -.-> IEP_cancelled_products_in_the_order_from_TOS : <>
+
+```
+
+M.3111.1(25)
+
+UML Use Case Diagram for Order Handling FS. Actors: TOS, IEP. Use Case: Order\_Handling\_FS. Includes: IEP sends the information\_of order\_to\_TOS, TOS sends order\_fulfilment\_result\_to\_IEP, IEP requests the\_order\_status\_from\_TOS, IEP cancels products in the\_order\_from\_TOS. Reference: M.3111.1(25)
+
+**Figure 5 – Order handling FS**
+
+
+
+```
+
+usecaseDiagram
+ actor TOS
+ actor IEP
+ usecase Order_Bill_Invoice_FS
+ TOS --> Order_Bill_Invoice_FS
+ IEP --> Order_Bill_Invoice_FS
+ Order_Bill_Invoice_FS -.-> IEP_requests_bill_invoice_from_TOS : <>
+ Order_Bill_Invoice_FS -.-> TOS_provides_bill_invoice_response_to_IEP : <>
+
+```
+
+M.3111.1(25)
+
+UML Use Case Diagram for Order Bill Invoice FS. Actors: TOS, IEP. Use Case: Order\_Bill\_Invoice\_FS. Includes: IEP requests bill\_invoice\_from\_TOS, TOS provides bill\_invoice\_response\_to\_IEP. Reference: M.3111.1(25)
+
+**Figure 6 – Order bill invoice FS**
+
+
+
+```
+
+usecaseDiagram
+ actor TOS
+ actor IEP
+ usecase Product_Renewal_FS
+ TOS --> Product_Renewal_FS
+ IEP --> Product_Renewal_FS
+ Product_Renewal_FS -.-> IEP_sends_product_renewal_order_to_TOS : <>
+ Product_Renewal_FS -.-> TOS_sends_renewal_order_fulfilment_result_to_IEP : <>
+
+```
+
+M.3111.1(25)
+
+UML Use Case Diagram for Product Renewal FS. Actors: TOS, IEP. Use Case: Product\_Renewal\_FS. Includes: IEP sends product\_renewal\_order\_to\_TOS, TOS sends renewal\_order\_fulfilment\_result\_to\_IEP. Reference: M.3111.1(25)
+
+**Figure 7 – Product renewal FS**
+
+
+
+Figure 8 – Customer service FS. A functional specification diagram showing interactions between TOS and IEP actors through a central 'Customer\_Service\_FS' function. The diagram includes five use cases connected via '<>' relationships: 'IEP sends service consulting to TOS', 'TOS sends response of customer's problems and complaints to IEP', 'TOS sends service consulting response to IEP', and 'IEP sends customer's problems and complaints to TOS'. A reference code 'M.3111.1(25)' is present at the bottom right.
+
+**Figure 8 – Customer service FS**
+
+## **7.2 Specification level requirements**
+
+The general exceptions (e.g., communication error, processing error) related to all functions are not described in clause 7 and will only be handled in the design phase.
+
+The exception "Invalid input parameter" in the following clauses indicates that there is some syntactic error(s) in the input parameters, which does not involve semantic issues.
+
+The exception "Specified catalogue ID does not exist" (for example) indicates that the ID of the catalogue in the input parameter is syntactically correct, but it cannot be found in the IEP, which is considered as a semantic error.
+
+### **7.2.1 Requirements**
+
+There are no specification level requirements.
+
+### **7.2.2 Actor roles**
+
+See clause 7.1.2.
+
+### **7.2.3 Telecommunication resources**
+
+See clause 7.1.3.
+
+### **7.2.4 Use cases**
+
+##### **7.2.4.1 Product support and readiness use cases**
+
+Figure 3 shows the high-level use cases for the product support and readiness function set and these use cases are presented in clauses 7.2.4.1.1 to 7.2.4.1.3.
+
+###### **7.2.4.1.1 The TOS sends a product classification catalogue to the IEP (M)**
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS sends the product classification catalogue to the IEP, so that the customer-oriented product catalogue in the IEP can be established more easily according to this product classification catalogue. | |
+| Actors and roles | The IEP is the consumer of the product classification catalogue information sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The product classification catalogue information has existed in the TOS. | |
+| Begins when | The TOS sends the product classification catalogue to the IEP. | |
+| Step 1 | The TOS sends the product classification catalogue information to the IEP, which includes a list of items, and each item includes the following: - – item ID,
- – item name,
- – action type,
- – item number,
- – parent ID.
(An example of product classification catalogue is shown in Appendix I, with action types also illustrated.) | |
+| Step 2.1 | If the product classification catalogue is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | |
+| Step 2.2 | If the product classification catalogue cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | |
+| Ends when | The IEP has received the product classification catalogue information. | |
+| Exceptions | - – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The IEP receives the product classification catalogue information. | |
+| Traceability | REQ-PSR-FUN-101 | |
+
+###### 7.2.4.1.2 The TOS sends product SPU information to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS sends the product SPU information to the IEP, so that the product SPU can be correlated to the appropriate catalogue item and then the product SKU can be correlated to the specific SPU in the IEP. | |
+| Actors and roles | The IEP is the consumer of the product SPU information sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The related product classification catalogue has already been sent from the TOS to the IEP. | Use case 7.2.4.1.1 |
+| Begins when | The TOS sends the product SPU information to the IEP. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Step 1 | The TOS sends the product SPU information to the IEP, which includes: - – SPU ID,
- – SPU name,
- – catalogue ID it belongs to,
- – action type,
- – List of product SPU attributes, and each attribute may include:
- SPU attribute ID,
- SPU attribute name (optional, when action type is DEL),
- SPU attribute value (optional, when action type is DEL).
| |
+| Step 2.1 | If the product SPU information is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | |
+| Step 2.2 | If the product SPU information cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | |
+| Ends when | The IEP has received the product SPU information. | |
+| Exceptions | 1) General exceptions: - – Specified catalogue ID does not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
2) If the action type is ADD, exceptions may include: - – SPU ID has already existed,
- – SPU name has already existed.
3) If the action type is MOD, exceptions may include: - – Specified SPU ID does not exist,
- – SPU attribute ID does not exist.
4) If the action type is DEL, exceptions may include: - – Specified SPU ID does not exist.
| |
+| Post-conditions | The IEP receives the product SPU information. | |
+| Traceability | REQ-PSR-FUN-102 | |
+
+###### 7.2.4.1.3 The TOS sends product SKU information to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS sends the product SKU information to the IEP, so that the SKU can be correlated to a specific SPU in the IEP, and the products displayed for customers can be created. | |
+| Actors and roles | The IEP is the consumer of the product SKU information sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Pre-conditions | The related product SPU information has already been sent from the TOS to the IEP. | Use case 7.2.4.1.2 |
+| Begins when | The TOS sends the product SKU information to the IEP. | |
+| Step 1 | The TOS sends the product SKU information to the IEP, which includes: - – SKU ID,
- – SKU name,
- – SPU ID it belongs to,
- – SKU availability time,
- – SKU expiration time,
- – action type,
- – list of product SKU attributes, and each attribute may include:
- SKU attribute ID,
- SKU attribute name (optional, when action type is DEL),
- SKU attribute value (optional, when action type is DEL),
- – product description detail.
| |
+| Step 2.1 | If the product SKU information is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | |
+| Step 2.2 | If the product SKU information cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | |
+| Ends when | The IEP has received the product SKU information. | |
+| Exceptions | 1) General exceptions: - – Specified SPU ID does not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
2) If the action type is ADD, exceptions may include: - – SKU ID has already existed,
- – SKU name has already existed,
- – SKU expiration time is earlier that the current time,
- – SKU expiration time is earlier that SKU availability time.
3) If the action type is MOD, exceptions may include: - – Specified SKU ID does not exist,
- – Specified SKU attribute ID does not exist,
- – SKU expiration time is earlier that the current time,
- – SKU expiration time is earlier that SKU availability time.
4) If the action type is DEL, exceptions may include: - – Specified SKU ID does not exist.
| |
+| Post-conditions | The IEP receives the product SKU information. | |
+| Traceability | REQ-PSR-FUN-103 | |
+
+##### 7.2.4.2 Customer management use cases
+
+Figure 4 shows the high-level use cases for the customer management function set and these use cases are presented in clauses 7.2.4.2.1 to 7.2.4.2.4.
+
+###### 7.2.4.2.1 The IEP sends information of newly created customer to the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends the information of a newly created customer to the TOS. So that the TOS can determine whether this customer is new in its own system and initiate real name authentication according to this information. | |
+| Actors and roles | The TOS is the consumer of the newly created customer information sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer submitting an order in the IEP is new for the IEP.
The customer creation information has been completed in the IEP. | |
+| Begins when | The IEP sends the information of the newly created customer to the TOS. | |
+| Step 1 | The IEP sends the information of the newly created customer to the TOS, which includes: - – customer ID of the IEP (Note),
- – customer name,
- – customer ID card number,
- – front and back photos of the ID card,
- – contact phone number,
- – contact address,
- – payment account.
NOTE – When a customer is newly created in the IEP, a customer ID of the IEP will be created. The customer ID of the IEP is different from the customer ID of the TOS. The mapping relationship of these two customer IDs will be stored in both the IEP and the TOS. | |
+| Step 2.1 | If the information of the newly created customer is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | |
+| Step 2.2 | If the information of newly created customer cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | |
+| Ends when | The TOS has received the newly created customer information. | |
+| Exceptions | - – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The TOS receives the newly created customer information.
If this customer does not exist in the TOS, the TOS will start the real name authentication. | Use case 7.2.4.2.2 |
+| Traceability | REQ-CM-FUN-201 | |
+
+###### 7.2.4.2.2 The TOS provides real name authentication failure result to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | If the real name authentication fails in the TOS, the TOS provides the real name authentication failure result back to the IEP. So that the IEP can ask the customer to modify the newly created customer information. | |
+| Actors and roles | The IEP is the consumer of the real name authentication failure result sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The IEP has sent the information of the newly created customer to the TOS.
This customer does not exist in the TOS.
The customer real name authentication fails in the TOS. | Use case 7.2.4.2.1 |
+| Begins when | The TOS sends the real name authentication failure result to the IEP. | |
+| Step 1 | The TOS provides the real name authentication failure result back to the IEP, which includes: - – customer ID of the IEP,
- – the reason of the authentication failure (such as the information missing, or the information does not meet the authentication requirement).
| |
+| Step 2.1 | If the real name authentication failure result is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | |
+| Step 2.2 | If the real name authentication failure result cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | |
+| Ends when | The IEP has received the real name authentication failure result. | |
+| Exceptions | - – Specified customer ID of the IEP does not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The IEP receives the real name authentication failure result. | |
+| Traceability | REQ-CM-FUN-202 | |
+
+###### 7.2.4.2.3 The TOS provides customer newly created success response to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|------------------|--------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | If the real name authentication is successful in the TOS, the TOS provides customer newly created success response to the IEP. | |
+| Actors and roles | The IEP is the consumer of the customer newly created success response sent from the TOS. The TOS is the supplier. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| | The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The IEP has sent the information of the newly created customer to the TOS.
This customer's name and ID number have already existed in the TOS, or the real name authentication is successful in the TOS. | Use case 7.2.4.2.1 |
+| Begins when | The TOS sends a customer newly created success response to the IEP. | |
+| Step 1 | The TOS provides customer newly created success response to the IEP, which includes:
– customer ID of the IEP,
– customer ID of the TOS. | |
+| Step 2.1 | If the customer newly created success response is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | |
+| Step 2.2 | If the customer newly created success response cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | |
+| Ends when | The IEP has received the customer newly created success response. | |
+| Exceptions | – Specified customer ID of the IEP does not exist,
– Invalid parameter,
– Operation failed due to internal problem. | |
+| Post-conditions | The IEP receives the customer newly created success response. | |
+| Traceability | REQ-CM-FUN-203 | |
+
+###### 7.2.4.2.4 The IEP sends customer's credit worthiness verification request to the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends a customer's credit worthiness verification request to the TOS, who has ordered product in the IEP, so that the TOS can verify this customer's credit worthiness. | |
+| Actors and roles | The TOS is the consumer of the customer verification request sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has submitted an order in the IEP.
The real name authentication for the customer is successful in the TOS. | Use case 7.2.4.2.3 |
+| Begins when | The IEP sends the customer's credit worthiness verification request to the TOS. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Step 1 | The IEP sends a customer's credit worthiness verification request to the TOS, which includes:
– customer ID of the TOS. | |
+| Step 2.1 | If the customer's credit worthiness verification request is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | |
+| Step 2.2 | If the customer's credit worthiness verification request cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | |
+| Ends when | The TOS has received the customer's credit worthiness verification request. | |
+| Exceptions | – Specified customer ID of the TOS does not exist,
– Invalid parameter,
– Operation failed due to internal problem. | |
+| Post-conditions | The TOS receives the customer's credit worthiness verification request. | |
+| Traceability | REQ-CM-FUN-204 | |
+
+##### 7.2.4.3 Order handling use cases
+
+Figure 5 shows the high-level use cases for the order handling function set and these use cases are presented in clauses 7.2.4.3.1 to 7.2.4.3.4.
+
+###### 7.2.4.3.1 The IEP sends the order information to the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends the order information to the TOS, which has been submitted by the customer in the IEP. | |
+| Actors and roles | The TOS is the consumer of the order information sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation on the TOS. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has submitted an order in the IEP. | |
+| Begins when | The IEP sends the order information to the TOS. | |
+| Step 1 | The IEP sends the order information to the TOS, which includes:
– customer ID of the TOS,
– order IDNOTE,
– SKU ID in the order,
– order payment status.
NOTE – Order ID in this Recommendation refers to the order ID of the IEP. The TOS has its own order ID set which is different from the order ID set of the IEP. Their mapping relationship is stored in the TOS, which the IEP does not need to know. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Step 2.1 | If the order information is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | |
+| Step 2.2 | If the order information cannot be successfully processed by the TOS, including order feasibility verification failure, the TOS will inform the IEP with a failure response. | |
+| Ends when | The TOS has received the order information. | |
+| Exceptions | - – Order ID has already existed,
- – Specified customer ID of the TOS does not exist,
- – Specified SKU ID does not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The TOS receives the order information. | |
+| Traceability | REQ-PSR-FUN-301 | |
+
+###### 7.2.4.3.2 The TOS sends order fulfilment result to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS sends the order fulfilment result to the IEP after the TOS has completed the implementation of the order. | |
+| Actors and roles | The IEP is the consumer of the order fulfilment result sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The TOS has completed the implementation of the order. | Use case 7.2.4.3.1 |
+| Begins when | The TOS sends the order fulfilment result to the IEP. | |
+| Step 1 | The TOS sends the order fulfilment result to the IEP, which includes: - – order ID,
- – order fulfilment result (successful or failed),
- – fail reason (optional, only when the result is failed).
| |
+| Step 2.1 | If the order fulfilment result is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | |
+| Step 2.2 | If the order fulfilment result cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | |
+| Ends when | The IEP has received the order fulfilment result. | |
+| Exceptions | - – Specified order ID does not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The IEP receives the order fulfilment result. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|----------------|-------------------------|---------------------------------|
+| Traceability | REQ-PSR-FUN-302 | |
+
+###### 7.2.4.3.3 The IEP requests the order status from the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends the order status inquiry to the TOS. So that the customer can track the process of the order handling. | |
+| Actors and roles | The TOS is the consumer of the order status inquiry sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation on the TOS. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has submitted an order status inquiry in the IEP. | Use case 7.2.4.3.2 |
+| Begins when | The IEP sends the order status inquiry to the TOS. | |
+| Step 1 | The IEP sends the order status inquiry to the TOS, which includes:
– order ID. | |
+| Step 2.1 | If the order status inquiry is successfully received by the TOS without any problems, the TOS will inform the IEP with the order status inquiry result response, which includes:
– order ID,
– list of order SKU status, and each order SKU status includes:
SKU ID,
the SKU fulfilment status of the SKU ID in this order. | |
+| Step 2.2 | If the order status inquiry cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | |
+| Ends when | The IEP has received the order status result or an exception. | |
+| Exceptions | – Specified order ID does not exist,
– Specified SKU IDs do not exist,
– Invalid parameter,
– Operation failed due to internal problem. | |
+| Post-conditions | The IEP receives the order status result or an exception. | |
+| Traceability | REQ-PSR-FUN-303 | |
+
+###### 7.2.4.3.4 The IEP cancels products in the order from the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|----------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends the cancel products in the order request to the TOS, to cancel all the products in the order or part of products in the order. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Actors and roles | The TOS is the consumer of the cancel products in the order request sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has submitted an order cancellation in the IEP. | Use case 7.2.4.3.2 |
+| Begins when | The IEP sends the cancel products in the order request to the TOS. | |
+| Step 1 | The IEP sends the cancel products in the order request to the TOS, which includes:
– order ID,
– list of SKU IDs of products to be cancelled. | |
+| Step 2.1 | If the order cancellation is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response including:
– refund amount. | |
+| Step 2.2 | If the order cancellation cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response including:
– failure reason. | |
+| Ends when | The IEP receives the cancellation response from the TOS. | |
+| Exceptions | – Specified order ID does not exist,
– Specified SKU IDs do not exist,
– Invalid parameter,
– Operation failed due to internal problem. | |
+| Post-conditions | The IEP receives the product cancellation response.
The specified products of the SKU IDs are cancelled, if the operation is successful. | |
+| Traceability | REQ-PSR-FUN-304 | |
+
+##### 7.2.4.4 Order bill invoice use cases
+
+Figure 6 shows the high-level use cases for the order bill invoice function set and these use cases are presented in clauses 7.2.4.4.1 and 7.2.4.4.2.
+
+###### 7.2.4.4.1 The IEP requests bill invoice from the TOS (O)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|------------------|----------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP requests bill invoice from the TOS. So that the customer can inquire bill invoice in the IEP. | |
+| Actors and roles | The TOS is the consumer of the bill invoice inquiry sent from the IEP. The IEP is the supplier.
The IEP invokes the operation on the TOS. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has submitted a bill invoice inquiry in the IEP. | |
+| Begins when | The IEP sends the bill invoice request to the TOS. | |
+| Step 1 | The IEP sends the bill invoice inquiry request to the TOS, which includes: - – order ID,
- – list of SKU IDs,
- – invoice header type (individual or enterprise),
- – invoice header,
- – tax identification number (optional, if the invoice header type is enterprise).
| |
+| Step 2.1 | If the bill invoice inquiry is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | |
+| Step 2.2 | If the bill invoice inquiry cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | |
+| Ends when | The TOS has received the bill invoice inquiry. | |
+| Exceptions | - – Specified order ID does not exist,
- – Specified SKU IDs do not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The TOS receives the bill invoice inquiry. | |
+| Traceability | REQ-PSR-FUN-401 | |
+
+###### 7.2.4.4.2 The TOS provides bill invoice response to the IEP (O)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS provides bill invoice response to the IEP. | |
+| Actors and roles | The IEP is the consumer of the bill invoice response sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The TOS has already issued the invoice that is inquired by the customer in the IEP. | Use case 7.2.4.4.1 |
+| Begins when | The TOS provides the bill invoice response to the IEP. | |
+| Step 1 | The TOS provides the bill invoice response to the IEP, which includes: - – order ID,
- – list of SKU IDs,
- – URL for the bill invoice.
| |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Step 2.1 | If the bill invoice response is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful response. | |
+| Step 2.2 | If the bill invoice response cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure response. | |
+| Ends when | The IEP has received the bill invoice response. | |
+| Exceptions | - – Specified order ID does not exist,
- – Specified SKU IDs do not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The IEP receives the bill invoice response. | |
+| Traceability | REQ-PSR-FUN-402 | |
+
+##### 7.2.4.5 Product renewal use cases
+
+Figure 7 shows the high-level use cases for the product renewal function set and these use cases are presented in clauses 7.2.4.5.1 and 7.2.4.5.2.
+
+###### 7.2.4.5.1 The IEP sends product renewal order to the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends the product renewal order to the TOS, which has been submitted by the customer in the IEP. So that the customer can renew the product in the IEP. | |
+| Actors and roles | The TOS is the consumer of the order information sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation on the TOS.
| |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The original order has been successfully fulfilled in the TOS.
The customer has submitted the product renewal order in the IEP.
| Use case 7.2.4.3.2 |
+| Begins when | The IEP sends the product renewal order to the TOS. | |
+| Step 1 | The IEP sends the information of the product renewal order to the TOS, which includes:
- – renewal order ID,
- – original order ID,
- – list of SKU IDs to be renewed,
- – renewal order payment status.
| |
+| Step 2.1 | If the renewal order information is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | |
+| Step 2.2 | If the renewal order information cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | |
+| Ends when | The TOS has received the renewal order information. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Exceptions | - – Renewal order ID has already existed,
- – Specified original order ID does not exist,
- – Specified SKU ID(s) do not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The TOS receives the information of the product renewal order. | |
+| Traceability | REQ-PSR-FUN-501 | |
+
+###### 7.2.4.5.2 The TOS sends renewal order fulfilment result to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS sends the renewal order fulfilment result to the IEP. | |
+| Actors and roles | The IEP is the consumer of the renewal order fulfilment result sent from the TOS. The TOS is the supplier.
The TOS invokes the operation on the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has submitted a product renewal order in the IEP. | Use case 7.2.4.5.1 |
+| Begins when | The TOS sends the renewal order fulfilment result to the IEP. | |
+| Step 1 | The TOS sends the renewal order fulfilment result to the IEP, which includes: - – renewal order ID,
- – order fulfilment result (successful or failed),
- – fail reason (optional, only when the result is failed, such as customer in arrears).
| |
+| Step 2.1 | If the renewal order fulfilment result is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | |
+| Step 2.2 | If the renewal order fulfilment result cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | |
+| Ends when | The IEP has received the renewal order fulfilment result. | |
+| Exceptions | - – Specified renewal order ID does not exist,
- – Invalid parameter,
- – Operation failed due to internal problem.
| |
+| Post-conditions | The IEP receives the order fulfilment result. | |
+| Traceability | REQ-PSR-FUN-502 | |
+
+##### 7.2.4.6 Customer service use cases
+
+Figure 8 shows the high-level use cases for the customer service function set and these use cases are presented in clauses 7.2.4.6.1 to 7.2.4.6.4.
+
+###### 7.2.4.6.1 The IEP sends service consulting request to the TOS (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The IEP sends a service consulting request to the TOS, which has been initiated by the customer in the IEP and cannot be processed in the IEP. | |
+| Actors and roles | The TOS is the consumer of the service consulting sent from the IEP.
The IEP is the supplier.
The IEP invokes the operation in the TOS. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The customer has initiated service consulting in the IEP. The IEP cannot resolve it and needs to send this service consulting to the TOS for further processing. | |
+| Begins when | The IEP sends a service consulting request to the TOS. | |
+| Step 1 | The IEP sends a service consulting request to the TOS, which includes:
– work order ID,
– service consulting description. | |
+| Step 2.1 | If the service consulting is successfully received by the TOS without any problems, the TOS will inform the IEP with a successful response. | |
+| Step 2.2 | If the service consulting cannot be successfully processed by the TOS, the TOS will inform the IEP with a failure response. | |
+| Ends when | The TOS has received the service consulting request. | |
+| Exceptions | – Invalid parameter,
– Operation failed due to internal problem. | |
+| Post-conditions | The TOS receives the service consulting. | |
+| Traceability | REQ-PSR-FUN-601 | |
+
+###### 7.2.4.6.2 The TOS sends service consulting response to the IEP (M)
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Goal | The TOS sends service consulting response to the IEP. | |
+| Actors and roles | The IEP is the consumer of the service consulting response sent from the TOS. The TOS is the supplier.
The TOS invokes the operation in the IEP. | |
+| Telecom resources | See clause 7.2.3. | |
+| Assumptions | The communication between the TOS and the IEP is available. | |
+| Pre-conditions | The IEP has sent service consulting to the TOS. The TOS has prepared the response to the service consulting. | Use case 7.2.4.6.1 |
+| Begins when | The TOS sends the service consulting response to the IEP. | |
+
+| Use case stage | Evolution/Specification | <>
Related use case(s) |
+|-----------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------|
+| Step 1 | The TOS sends the service consulting response to the IEP, which includes:
– work order ID,
– service consulting reply. | |
+| Step 2.1 | If the service consulting response is successfully received by the IEP without any problems, the IEP will inform the TOS with a successful instruction. | |
+| Step 2.2 | If the service consulting response cannot be successfully processed by the IEP, the IEP will inform the TOS with a failure instruction. | |
+| Ends when | The IEP has received the service consulting response. | |
+| Exceptions | – Specified work order ID does not exist,
– Invalid parameter,
– Operation failed due to internal problem. | |
+| Post-conditions | The IEP receives the service consulting response. | |
+| Traceability | REQ-PSR-FUN-602 | |
+
+###### 7.2.4.6.3 The IEP sends customer's problems and complaints to the TOS (M)
+
+| Use case stage | Evolution/Specification | <>