3 title: TS 28.532 Performance data file reporting Service
6 OAS 3.0.1 specification of the Performance data file reporting Management Service © 2020,
7 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). All
10 description: 3GPP TS 28.532 V16.4.0; Generic management services
11 url: 'http://www.3gpp.org/ftp/Specs/archive/28_series/28.532/'
13 - url: '{MnSRoot}/PerfDataFileReportMnS/v1640'
16 description: See subclause 4.4 of TS 32.158
17 default: http://example.com/3GPPManagement
21 summary: Read resources of information of available files
22 description: 'With HTTP GET, resources of information of available files are read. The resources to be read are identified with the path component (base resource) and the query component (managementDataType, beginTime and endTime) of the URI. The fields query component allows to select the resource properties to be returned.'
24 - name: managementDataType
26 description: This parameter identifies the type of management data that the file contains to select the resources from the collection resources identified with the path component of the URI.
28 $ref: '#/components/schemas/managementDataType-Type'
31 description: This parameter identifies the time stamp no later than which the file became available to select the resources from the collection resources identified with the path component of the URI.
33 $ref: '#/components/schemas/dateTime-Type'
36 description: This parameter identifies the time stamp no earlier than which the file became available to select the resources from the collection resources identified with the path component of the URI.
38 $ref: '#/components/schemas/dateTime-Type'
41 description: 'Success case ("200 OK"). The resources identified in the request for retrieval are returned in the response message body. In case the fields query parameter is used, the selected resources are returned.'
45 $ref: '#/components/schemas/fileInfoRetrieval-ResponseType'
47 description: Error case.
51 $ref: '#/components/schemas/error-ResponseType'
54 summary: Create a subscription
55 description: To create a subscription the representation of the subscription is POSTed on the /subscriptions collection resource.
61 $ref: '#/components/schemas/subscription-RequestType'
64 description: Success case ("201 Created"). The representation of the newly created subscription resource shall be returned.
68 $ref: '#/components/schemas/subscription-ResponseType'
70 description: Error case.
74 $ref: '#/components/schemas/error-ResponseType'
77 '{request.body#/consumerReference}':
84 $ref: '#/components/schemas/notifyFileReady-NotifType'
87 description: Success case ("204 No Content"). The notification is successfully delivered. The response message body is absent.
89 description: Error case.
93 $ref: '#/components/schemas/error-ResponseType'
94 notifyFilePreparationError:
95 '{request.body#/consumerReference}':
102 $ref: '#/components/schemas/notifyFilePreparationError-NotifType'
105 description: Success case ("204 No Content"). The notification is successfully delivered. The response message body is absent.
107 description: Error case.
111 $ref: '#/components/schemas/error-ResponseType'
113 summary: Delete all subscriptions made with a specific consumerReferenceId
114 description: The subscriptions are deleted by deleting the corresponding subscription resources. The resources to be deleted are identified with the path component of the URI pointing to the /subscription collection resource and filtering on the consumerReferenceId provided in the query part.
116 - name: consumerReferenceId
118 description: Identifies the subscriptions to be deleted.
121 $ref: '#/components/schemas/consumerReferenceId-QueryType'
124 description: Success case ("204 No Content"). The subscription resources have been deleted. The response message body is absent.
126 description: Error case.
130 $ref: '#/components/schemas/error-ResponseType'
131 '/subscriptions/{subscriptionId}':
133 summary: Delete a single subscription
134 description: The subscription is deleted by deleting the corresponding subscription resource. The resource to be deleted is identified with the path component of the URI.
136 - name: subscriptionId
138 description: Identifies the subscription to be deleted.
141 $ref: '#/components/schemas/subscriptionId-PathType'
144 description: Success case ("204 No Content"). The subscription resource has been deleted. The response message body is absent.
146 description: Error case.
150 $ref: '#/components/schemas/error-ResponseType'
165 fileInfoRetrieval-ResponseType:
171 $ref: '#/components/schemas/fileInfo-Type'
176 $ref: '#/components/schemas/uri-Type'
178 $ref: '#/components/schemas/long-Type'
180 $ref: '#/components/schemas/dateTime-Type'
182 $ref: '#/components/schemas/dateTime-Type'
195 managementDataType-Type:
200 description: Header used in notifications as notification header
204 $ref: '#/components/schemas/uri-Type'
206 $ref: '#/components/schemas/notificationId-Type'
208 $ref: '#/components/schemas/notificationType-Type'
210 $ref: '#/components/schemas/dateTime-Type'
211 subscriptionId-PathType:
216 $ref: '#/components/schemas/long-Type'
217 notificationType-Type:
221 - notifyFilePreparationError
222 subscription-ResourceType:
226 $ref: '#/components/schemas/uri-Type'
228 $ref: '#/components/schemas/long-Type'
230 $ref: '#/components/schemas/filter-Type'
231 subscription-RequestType:
235 $ref: '#/components/schemas/subscription-ResourceType'
236 subscription-ResponseType:
240 $ref: '#/components/schemas/subscription-ResourceType'
241 consumerReferenceId-QueryType:
242 $ref: '#/components/schemas/uri-Type'
243 notifyFileReady-NotifType:
247 $ref: '#/components/schemas/header-Type'
254 $ref: '#/components/schemas/fileInfo-Type'
256 $ref: '#/components/schemas/additionalText-Type'
257 notifyFilePreparationError-NotifType:
261 $ref: '#/components/schemas/header-Type'
268 $ref: '#/components/schemas/fileInfo-Type'
270 $ref: '#/components/schemas/reason-Type'
272 $ref: '#/components/schemas/additionalText-Type'