3 description: "Request the instantiation of a service\n\nA Service Order is a type\
4 \ of order which can be used to describe a group of operations on service – one\
5 \ service order item per service. An action at the level of the service order\
6 \ item describe the operation to be done on a service (add, terminate for example).\
7 \ The service order is triggered from the BSS system in charge of the product\
8 \ order management to ONAP that will manage the service fulfillment.\n\nList of\
9 \ available subscription for serviceOrdering notifications, see /hub resources\
10 \ for more information:\n\n- ServiceOrderCreationNotification\n- ServiceOrderStateChangeNotification\n\
11 - ServiceOrderItemStateChangeNotification\n\n"
12 version: "4.0.0_inProgress"
13 title: "API ServiceOrder"
15 url: "/redoc/logo.png"
16 backgroundColor: "#FFFFFF"
17 host: "localhost:8080"
18 basePath: "/nbi/api/v4"
22 - "application/json;charset=utf-8"
24 - name: "ServiceOrder"
25 description: "provided by NBI"
26 - name: "Notification"
27 description: "provided by subscribers, which MUST registered by creating a hub resource"
34 - "application/json;charset=utf-8"
36 - "application/json;charset=utf-8"
37 operationId: "serviceOrderCreate"
38 summary: "Create a service order"
39 description: "This operation creates a service order entity.\nThe TMF Open API\
40 \ specification document provides the list of mandatory and non mandatory\
41 \ attributes when creating a ServiceOrder, including any possible rule conditions\
42 \ and applicable default values.\nPOST should be used without specifying the\
43 \ id and the href, the Service Order Management system is in charge of generating\
44 \ the id + href for the ServiceOrder.\n\nIn Beijing Release, NBI will use\
45 \ only POST {{url}}/ecomp/mso/infra/serviceInstances/v4 SO API. This mean\
46 \ that only the 'service-instance' level will be created in AAI. Additional\
47 \ resource like VNF and/OR VF are not created.\n\nIn Casablanca release, NBI\
48 \ has been improved to also be able to use POST {{url}}/e2eServiceInstances/v3\
49 \ SO API. This API is able to instantiate in ONAP E2E service; This is useful\
50 \ for CCVPN and VoLTE UC.\nDepending on the service category defined in SDC,\
51 \ NBI will use one or the other SO API. If category starts with e2e, NBI will\
52 \ use {url}}/e2eServiceInstances/v3 SO API - else it will use {{url}}/ecomp/mso/infra/serviceInstances/v4\
56 - name: "serviceOrder"
61 $ref: "#/definitions/CreateServiceOrder"
64 description: "Created"
66 $ref: "#/definitions/ServiceOrder"
71 - "application/json;charset=utf-8"
72 operationId: "serviceOrderFind"
73 summary: "List service orders"
74 description: "Retrieve and list service order entities according to given criteria.\n\
75 Only a predefined set of attribute is proposed.\nAttribute selection could\
76 \ be described in the fields attribute."
87 description: "state of the order(s) to be retrieved"
94 - name: "orderDate.gt"
97 description: "order date greather than"
99 - name: "orderDate.lt"
102 description: "order date lower than"
107 description: "this attribute could be used to filter retrieved attribute(s)\
113 description: "The index of the first element to retrieve. Zero is the first\
114 \ element of the collection."
120 description: "The maximum number of elements to retrieve (it can be greater\
121 \ than the actual available number of items)."
130 $ref: "#/definitions/ServiceOrder"
145 - "application/json;charset=utf-8"
146 operationId: "serviceOrderGet"
147 summary: "Retrieve a service order"
148 description: "This operation retrieves a service order entity. \nAttribute selection\
149 \ is enabled for all first level attributes."
159 description: "Attribute selection"
165 $ref: "#/definitions/ServiceOrder"
171 - "application/json;charset=utf-8"
173 - "application/json;charset=utf-8"
174 operationId: "notificationCreate"
175 summary: "NBI will send notification to this operation provided by subscribers"
176 description: "Notification structure depends of the eventType:\n\n- ServiceOrderCreationNotification\n\
177 - ServiceOrderStateChangeNotification\n\n```\n{\n \"eventId\": \"string\"\
178 ,\n \"eventDate\": \"2019-03-12T16:21:27.530Z\",\n \"eventType\": \"string\"\
179 ,\n \"event\": {\n \"id\": \"string\",\n \"href\": \"string\",\n \
180 \ \"externalId\": \"string\",\n \"state\": \"acknowledged\",\n \"orderDate\"\
181 : \"2019-03-12T16:21:27.530Z\",\n \"completionDateTime\": \"2019-03-12T16:21:27.530Z\"\
182 \n }\n}\n```\n\n- ServiceOrderItemStateChangeNotification\n\n```\n{\n \"\
183 eventId\": \"string\",\n \"eventDate\": \"2019-03-12T16:21:44.066Z\",\n \
184 \ \"eventType\": \"string\",\n \"event\": {\n \"id\": \"string\",\n \
185 \ \"href\": \"string\",\n \"externalId\": \"string\",\n \"state\":\
186 \ \"acknowledged\",\n \"orderDate\": \"2019-03-12T16:21:44.066Z\",\n \
187 \ \"completionDateTime\": \"2019-03-12T16:21:44.066Z\",\n \"orderItem\"\
188 : [\n {\n \"id\": \"string\",\n \"action\": \"add\",\n\
189 \ \"state\": \"acknowledged\",\n \"service\": {\n \"\
190 id\": \"string\",\n \"href\": \"string\",\n \"name\": \"\
191 string\",\n \"serviceState\": \"string\",\n \"serviceCharacteristic\"\
192 : [\n {\n \"name\": \"string\",\n \"\
193 valueType\": \"string\",\n \"value\": {\n \"serviceCharacteristicValue\"\
194 : \"string\"\n }\n }\n ],\n \"serviceRelationship\"\
195 : [\n {\n \"type\": \"reliesOn\"\n }\n\
196 \ ],\n \"relatedParty\": [\n {\n \
197 \ \"id\": \"string\",\n \"href\": \"string\",\n \
198 \ \"role\": \"string\",\n \"name\": \"string\",\n \
199 \ \"@referredType\": \"string\"\n }\n ],\n \
200 \ \"serviceSpecification\": {\n \"id\": \"string\",\n \
201 \ \"href\": \"string\",\n \"name\": \"string\",\n \
202 \ \"version\": \"string\",\n }\n }\n }\n ]\n }\n\
206 - name: "Notification"
211 $ref: "#/definitions/Notification"
214 description: "Created"
216 $ref: "#/definitions/Notification"
219 description: "Action type to be describer on the order item.\nmodify is not managed\
220 \ in Beijing release"
228 description: "List of possible state for the order and the orderItem."
241 description: "Relationship type;\nOnly reliesOn is managed in Beijing release."
249 - "ServiceOrderCreationNotification"
250 - "ServiceOrderStateChangeNotification"
251 - "ServiceOrderItemStateChangeNotification"
266 description: "Application related code (as defined in the API or from a common\
271 description: "Text that explains the reason for error. This can be shown to\
275 description: "Text that provide more details and corrective actions related\
276 \ to the error. This can be shown to a client user"
279 description: "http error code extension like 400-2"
282 description: "url pointing to documentation describing the error"
285 description: "Linked Services to the one instantiate\nnbi component used this\
286 \ relationship to sort request to ONAP."
293 $ref: "#/definitions/RelationshipType"
295 $ref: "#/definitions/Service"
297 description: "Service references"
303 description: "Unique identifier of the service"
306 description: "Reference of the service"
308 ServiceCharacteristic:
309 description: "ServiceCharacteristic"
315 description: "Name of characteristic"
321 $ref: "#/definitions/Value"
323 description: "A related party defines party which are involved in this order and\
324 \ the role they are playing.\nfor Beijing release:\nWith the current version\
325 \ of APIs used from SO and AAI we need to manage a ‘customer’. This customer\
326 \ concept is confusing with Customer BSS concept. We took the following rules\
327 \ to manage the ‘customer’ information:\no\tIt could be provided through a serviceOrder\
328 \ in the service Order a relatedParty with role ‘ONAPcustomer’ should be provided\
329 \ in the serviceOrder header (we will not consider in this release the party\
330 \ at item level); External API component will check if this customer exists\
331 \ and create it in AAI if not.\no\tIf no relatedParty are provided the service\
332 \ will be affected to ‘generic’ customer (dummy customer) – we assume this ‘\
333 generic’ customer always exists."
340 description: "Unique identifier of a related party"
343 description: "An hyperlink to the party - not used in Beijnig release"
346 description: "The role of the related party (e.g. Owner, requester, fullfiller\
347 \ etc).\nONLY 'ONAPcustomer' is considered"
350 description: "Name of the related party"
355 ServiceSpecificationRef:
356 description: "The service specification (these attributes are fetched from the\
363 description: "Unique identifier of the service specification\nThis information\
364 \ will be used to retrieve SDC information + mapped to SO ModelNameVersionIdin\
368 description: "Reference of the service specification\nNot used in Beijing\
372 description: "Name of the service specification\nNot used in Beijing release"
375 description: "Version of the service Specification\nNot used in Beijing release"
378 $ref: "#/definitions/TargetServiceSchema"
380 description: "Not used in Beijing release"
383 description: "Not used in Beijing release"
386 description: "Not used in Beijing release"
389 description: "Service (to be added, modified, deleted) description"
395 description: "Identifier of a service instance.\nIt must be valued if orderItem\
396 \ action is 'delete' and corresponds to a AAI service.id"
399 description: "Reference to the Service (useful for delete or modify command).\n\
400 Not managed in Beijing release."
403 description: "Name of the service - When orderItem action is 'add' this name\
404 \ will be used in ONAP/SO request as InstaceName."
407 description: "The lifecycle state of the service requested;\nNot managed in\
411 description: "To define the service type\nNot managed in Beijing Release"
414 description: "The URL to get the resource schema.\nNot managed in Beijing\
417 serviceCharacteristic:
420 $ref: "#/definitions/ServiceCharacteristic"
424 $ref: "#/definitions/ServiceRelationship"
428 $ref: "#/definitions/RelatedParty"
429 serviceSpecification:
430 $ref: "#/definitions/ServiceSpecificationRef"
431 OrderItemRelationship:
432 description: "Linked order item to the one containing this attribute.\nnbi component\
433 \ used this relationship to sort request to ONAP."
440 $ref: "#/definitions/RelationshipType"
442 description: "Unique identifier of an order item"
445 description: "An identified part of the order. A service order is decomposed into\
446 \ one or more order items."
453 description: "Identifier of the line item (generally it is a sequence number\
457 $ref: "#/definitions/ActionType"
459 $ref: "#/definitions/StateType"
461 description: "Progress of the delivery in percentage."
464 description: "Used to extend the order item.\nnot used in Beijing relase"
467 description: "not used in Beijing relase"
470 description: "not used in Beijing relase"
472 orderItemRelationship:
475 $ref: "#/definitions/OrderItemRelationship"
477 $ref: "#/definitions/Service"
481 $ref: "#/definitions/OrderMessage"
483 description: "A Service Order is a type of order which can be used to place an\
484 \ order between a customer and a service provider or between a service provider\
485 \ and a partner and vice versa"
491 description: "ID created on repository side"
494 description: "Hyperlink to access the order"
497 description: "ID given by the consumer and only understandable by him (to\
498 \ facilitate his searches)"
501 description: "A way that can be used by consumers to prioritize orders in\
502 \ Service Order Management system (from 0 to 4 : 0 is the highest priority,\
506 description: "A free-text description of the service order"
509 description: "Used to categorize the order that can be useful for the OM system\
510 \ (e.g. “broadband”, “TVOption”, ...)"
513 $ref: "#/definitions/StateType"
519 description: "Date when the order was completed"
523 description: "Order start date wished by the requestor"
526 requestedCompletionDate:
527 description: "Requested delivery date from the requestor perspective"
530 expectedCompletionDate:
535 description: "Date when the order was started for processing"
550 $ref: "#/definitions/RelatedParty"
554 $ref: "#/definitions/OrderRelationship"
558 $ref: "#/definitions/ServiceOrderItem"
562 $ref: "#/definitions/OrderMessage"
564 description: "Linked order to the one containing this attribute.\nThis relationship\
565 \ is not used to sort ONAP request."
571 description: "The type of related order, can be : “dependency” if the order\
572 \ needs to be “not started” until another order item is complete (a service\
573 \ order in this case) or “cross-ref” to keep track of the source order (a\
577 description: "The id of the related order"
580 description: "A hyperlink to the related order"
583 description: "Type of the referred order."
586 description: "Target to the schema describing the service spec resource"
593 description: "Indicates the (class) type of resource."
596 description: "This field provided a link to the schema describing this REST\
600 description: "Value is a descriptive structure for service characteristic"
603 serviceCharacteristicValue:
604 description: "Value of the characteristic."
606 CreateServiceOrderItem:
607 description: "This structure is used in the operation POST for a serviceOrder\
608 \ request to describe an item.\nAttribute description is not accurate and should\
609 \ be find in the serviceOrderItem class."
616 description: "Identifier of the line item (generally it is a sequence number\
620 $ref: "#/definitions/ActionType"
621 orderItemRelationship:
624 $ref: "#/definitions/OrderItemRelationship"
626 $ref: "#/definitions/Service"
628 description: "This structure is used in the operation POST for a serviceOrder\
629 \ request.\nAttribute description is not accurate and should be find in the\
630 \ serviceOrder class."
634 description: "ID given by the consumer and only understandable by him (to\
635 \ facilitate his searches)"
638 description: "A way that can be used by consumers to prioritize orders in\
639 \ Service Order Management system (from 0 to 4 : 0 is the highest priority,\
643 description: "A free-text description of the service order"
646 description: "Used to categorize the order that can be useful for the OM system\
647 \ (e.g. “broadband”, “TVOption”, ...)"
650 description: "Order start date wished by the requestor"
653 requestedCompletionDate:
654 description: "Requested delivery date from the requestor perspective"
660 $ref: "#/definitions/RelatedParty"
664 $ref: "#/definitions/OrderRelationship"
668 $ref: "#/definitions/CreateServiceOrderItem"
670 description: "This structure is used to provide a subset of serviceOrder attributes\
671 \ to be provided in particular for notification messages"
677 description: "ID created on repository side"
680 description: "Hyperlink to access the order"
683 description: "ID given by the consumer and only understandable by him (to\
684 \ facilitate his searches)"
687 $ref: "#/definitions/StateType"
693 description: "Date when the order was completed"
697 description: "Notification structure for a serviceOrdering notification"
713 $ref: "#/definitions/EventType"
715 $ref: "#/definitions/ServiceOrderSummaryWithItem"
716 ServiceOrderItemSummary:
717 description: "Service Order item summary to be used for notification"
724 description: "Identifier of the line item (generally it is a sequence number\
728 $ref: "#/definitions/ActionType"
730 $ref: "#/definitions/StateType"
732 $ref: "#/definitions/Service"
733 ServiceOrderSummaryWithItem:
734 description: "Service order item summary with item description"
740 description: "ID created on repository side"
743 description: "Hyperlink to access the order"
746 description: "ID given by the consumer and only understandable by him (to\
747 \ facilitate his searches)"
750 $ref: "#/definitions/StateType"
756 description: "Date when the order was completed"
762 $ref: "#/definitions/ServiceOrderItemSummary"
764 description: "An optional array of messages associated with the Order"
767 - "correctionRequired"
771 description: "A code associated to this message"
774 description: "Service Order attribute related to this error message"
777 description: "Message related to this order"
780 $ref: "#/definitions/SeverityMessage"
782 description: "Indicator that an action is required to allow service order\
783 \ fullfilment to follow up"