r2.2
Pre-release
Pre-release
Release Notes
This release candidate contains the definition and documentation of
- dedicated-network-accesses 0.2.0-rc.1
- dedicated-network-profiles 0.2.0-rc.1
- dedicated-network 0.2.0-rc.1
- dedicated-network-areas 0.1.0-rc.1
The API definition(s) are based on
- Commonalities r4.3 (0.8.0)
- Identity and Consent Management r4.2 (0.5.0)
dedicated-network-accesses 0.2.0-rc.1
dedicated-network-accesses 0.2.0-rc.1 is a release-candidate version of this API. A rc.2 release-candidate version will be available soon.
Changes documented below are compared to version 0.1.0.
- API definition with inline documentation:
Breaking changes
- Support operations to manage access to dedicated network for multiple devices at a time by @hubertp-ericsson in #98
- Update pagination realization to align with commonalities by @hubertp-ericsson in #122
- Completing pagination support for operations
retrieveNetworkServiceAreas,listNetworksandlistAccessesby @hubertp-ericsson in #149 Devices.itemsnarrowed fromDeviceto a newValidDevicerequiringphoneNumberby @hubertp-ericsson in #170
Added
- Introducing a 409 Error Code called INCOMPATIBLE_STATE, indicating that the dedicated network resource referenced in the POST request is in an incompatible state, e.g. in TERMINATED state by @hubertp-ericsson in #81
- Support for asynchronous events for device access creation and device access lifecycle by @hubertp-ericsson in #91
- Support operations to manage access to dedicated network for multiple devices at a time by @hubertp-ericsson in #98
- Update pagination realization to align with commonalities by @hubertp-ericsson in #122
- Completing pagination support for operations
retrieveNetworkServiceAreas,listNetworksandlistAccessesby @hubertp-ericsson in #149
Changed
- Adding a clear description of the
MaxNumberOfDevicesparameter and its relation to aggregated UL/DL throughput parameters by @tlohmar in #88 - Implementing range limits for integer, array and string datatypes, as needed by Commonalities r4.3 by @tlohmar in #95
- Updating existing API test definitions and adding a new test definition for the Areas API by @tlohmar in #102
- Adding the missing mandatory template elements into the info.description section by @tlohmar in #121
Fixed
- Sync common files from Commonalities r4.3 by @camara-release-automation[bot] in #115
- Fixing
Schema must declare a type or combiner(S-016),Write operation must be security-restricted(S-303) andOperation must document a 401 response(S-307) validation errors by @hubertp-ericsson in #118 - Replacing the CloudEvent object definition with a reference (fixing
CloudEvent should be $ref, not inline(P-020)). Correcting the CloudEvent type (fixingCloudEvent type format is wrong(P-015)) by @jimfengjinhua in #120 Replacing local common data type definitions with direct $ref to CAMARA_common.yaml. Remove all unused local definitions. In dedicated-network-areas.yaml, Circle.radius has been changed from type integer (with maximum as 200000) to type number (without max limitation) by @jimfengjinhua in #123 - Addressing the "missing description" warnings (S-009, S-011, S-014, S-031, S-215) and the "Component may be unused" hints by @hubertp-ericsson in #124
- Addressing critical Release Management review corrections (on three-legged access token) by @tlohmar in #136
- Remove the NOTE mentioning three-legged access token from the
createAccessoperation description, as this API uses two-legged access tokens per the device identification section ininfo.descriptionby @jimfengjinhua in #140 - Adding missing x-correlator request parameter and response header by @jimfengjinhua in #141
- Correcting
optionationIdwithin the test definitions to be aligned with the associated APIs by @jimfengjinhua in #148 - Clarifying the "Identifying the device from the access token" section on 2-legged access token usages by @jimfengjinhua in #146
- Correction inconsistencies and errors (Clarifying descriptions, improve error handling, schema corrections, usage of device object, etc) on the Accesses API by @hubertp-ericsson in #170
- Correcting multiple assertions that do not match the API definitions (Issue #166) by @jimfengjinhua in #171
- Fixes small corrections in the test definitions (Issue #167) identified during release review by @jimfengjinhua in #172
Removed
- N/A
dedicated-network-profiles 0.2.0-rc.1
dedicated-network-profiles 0.2.0-rc.1 is a release-candidate version of this API.
Changes documented below are compared to version 0.1.0.
- API definition with inline documentation:
Breaking changes
- Enhancement to use format UUID for the NetworkProfileId and to add a human readable name, consistent with other DN APIs by @hubertp-ericsson in #83
- Pagination support when reading network profiles by @hubertp-ericsson in #125
Added
- Pagination support when reading network profiles by @hubertp-ericsson in #125
- Adding error scenarios according to CAMARA testing guideline to networks, profiles and areas APIs by @jimfengjinhua in #177
- Adding additional sunny day test definitions for networks, areas and profiles APIs, testing additional query parameter combinations and pagination by @jimfengjinhua in #178
- Making test case scenario names unique and operation specific by @jimfengjinhua in #183
Changed
- Enhancement to use format UUID for the NetworkProfileId and to add a human readable name, consistent with other DN APIs by @hubertp-ericsson in #83
- Adding a clear description of the
MaxNumberOfDevicesparameter and its relation to aggregated UL/DL throughput parameters by @tlohmar in #88 - Implementing range limits for integer, array and string datatypes, as needed by Commonalities r4.3 by @tlohmar in #95
- Adding missing range restrictions for two query line parameters and removing API readiness checklist file by @tlohmar in #126
- Adding the missing mandatory template elements into the info.description section by @tlohmar in #121
BitRate.required: [value, unit]newly enforced by @hubertp-ericsson in #174
Fixed
- Sync common files from Commonalities r4.3 by @camara-release-automation[bot] in #115
- Correcting global tags for dedicted network areas and profiles by @jordijoangimenez in #117
- Replacing local common data type definitions with direct $ref to CAMARA_common.yaml. Remove all unused local definitions. In dedicated-network-areas.yaml, Circle.radius has been changed from type integer (with maximum as 200000) to type number (without max limitation) by @jimfengjinhua in #123
- Addressing the "missing description" warnings (S-009, S-011, S-014, S-031, S-215) and the "Component may be unused" hints by @hubertp-ericsson in #124
- Adding missing x-correlator request parameter and response header by @jimfengjinhua in #141
- Correction inconsistencies and errors (lifecycle, response codes, QoS Profile usage, etc) on the Networks and the Profiles API by @hubertp-ericsson in #174
- Fixes small corrections in the test definitions (Issue #167) identified during release review by @jimfengjinhua in #172
- Making test case scenario names unique and operation specific by @jimfengjinhua in #183
Removed
- N/A
dedicated-network 0.2.0-rc.1
dedicated-network 0.2.0-rc.1 is a release-candidate version of this API.
Changes documented below are compared to version 0.1.0.
- API definition with inline documentation:
Breaking changes
- A new API is added which provides information about the geographical areas where consistent service coverage according to one or more network profiles is supported by @hubertp-ericsson in #87
- Enhancement to use format UUID for the NetworkProfileId and to add a human readable name, consistent with other DN APIs by @hubertp-ericsson in #83
- Completing pagination support for operations
retrieveNetworkServiceAreas,listNetworksandlistAccessesby @hubertp-ericsson in #149
Added
- Allowing the API Consumer to assign an own
nameto a dedicated network resource, which is returned when the network is read or listed by @hubertp-ericsson in #97 - Completing pagination support for operations
retrieveNetworkServiceAreas,listNetworksandlistAccessesby @hubertp-ericsson in #149 createNetworkgains404/422responses and four newDEDICATED_NETWORK.*error codes by @hubertp-ericsson in #174- Adding error scenarios according to CAMARA testing guideline to networks, profiles and areas APIs by @jimfengjinhua in #177
- Adding additional sunny day test definitions for networks, areas and profiles APIs, testing additional query parameter combinations and pagination by @jimfengjinhua in #178
- Making test case scenario names unique and operation specific by @jimfengjinhua in #183
Changed
- Enhancement to use format UUID for the NetworkProfileId and to add a human readable name, consistent with other DN APIs by @hubertp-ericsson in #83
- A new API is added which provides information about the geographical areas where consistent service coverage according to one or more network profiles is supported by @hubertp-ericsson in #87
- Implementing range limits for integer, array and string datatypes, as needed by Commonalities r4.3 by @tlohmar in #95
- Updating API test definitions by @tlohmar in #102
- Adding missing range restriction for strings in query line by @tlohmar in #126
- Adding the missing mandatory template elements into the info.description section by @tlohmar in #121
- Documented
ACTIVATED→RESERVEDtransition removed from NetworkStatus by @hubertp-ericsson in #174
Fixed
- Sync common files from Commonalities r4.3 by @camara-release-automation[bot] in #115
- Fixing
Schema must declare a type or combiner(S-016),Write operation must be security-restricted(S-303) andOperation must document a 401 response(S-307) validation errors by @hubertp-ericsson in #118 - Replacing the CloudEvent object definition with a reference (fixing
CloudEvent should be $ref, not inline(P-020)). Correcting the CloudEvent type (fixingCloudEvent type format is wrong(P-015)) by @jimfengjinhua in #120 - Replacing local common data type definitions with direct $ref to CAMARA_common.yaml. Remove all unused local definitions. In dedicated-network-areas.yaml, Circle.radius has been changed from type integer (with maximum as 200000) to type number (without max limitation) by @jimfengjinhua in #123
- Addressing the "missing description" warnings (S-009, S-011, S-014, S-031, S-215) and the "Component may be unused" hints by @hubertp-ericsson in #124
- Adding missing x-correlator request parameter and response header by @jimfengjinhua in #141
- Correction inconsistencies and errors (lifecycle, response codes, QoS Profile usage, etc) on the Networks and the Profiles API by @hubertp-ericsson in #174
- Correcting multiple assertions that do not match the API definitions (Issue #166) by @jimfengjinhua in #171
- Fixes small corrections in the test definitions (Issue #167) identified during release review by @jimfengjinhua in #172
- Making test case scenario names unique and operation specific by @jimfengjinhua in #183
Removed
IDENTIFIER_NOT_FOUNDremoved from theGeneric404code enum by @hubertp-ericsson in #174
dedicated-network-areas 0.1.0-rc.1
dedicated-network-areas 0.1.0-rc.1 is the first release-candidate version of this API.
- API definition with inline documentation:
Breaking changes
- N/A
Added
- A new API is added which provides information about the geographical areas where consistent service coverage according to one or more network profiles is supported by @hubertp-ericsson in #87
- Updating existing API test definitions and adding a new test definition for the Areas API by @tlohmar in #102
- Completing pagination support for operations
retrieveNetworkServiceAreas,listNetworksandlistAccessesby @hubertp-ericsson in #149 - Implementing range limits for integer, array and string datatypes, as needed by Commonalities r4.3 by @tlohmar in #95
- Correcting URL in API test definition file by @tlohmar in #127
- Adding the missing mandatory template elements into the info.description section by @tlohmar in #121
- Sync common files from Commonalities r4.3 by @camara-release-automation[bot] in #115
- Fix global tags for dedicted network areas and profiles by @jordijoangimenez in #117
- Fixing
Schema must declare a type or combiner(S-016),Write operation must be security-restricted(S-303) andOperation must document a 401 response(S-307) validation errors by @hubertp-ericsson in #118 - Replacing local common data type definitions with direct $ref to CAMARA_common.yaml. Remove all unused local definitions. In dedicated-network-areas.yaml, Circle.radius has been changed from type integer (with maximum as 200000) to type number (without max limitation) by @jimfengjinhua in #123
- Addressing the "missing description" warnings (S-009, S-011, S-014, S-031, S-215) and the "Component may be unused" hints by @hubertp-ericsson in #124
- Adding missing x-correlator request parameter and response header by @jimfengjinhua in #141
- Correcting
optionationIdwithin the test definitions to be aligned with the associated APIs by @jimfengjinhua in #148 - Correcting inconsistencies and errors (like error responses, pagination responses, missing schema types), identified during review by @hubertp-ericsson in #173
- Correcting multiple assertions that do not match the API definitions (Issue #166) by @jimfengjinhua in #171
- Fixes small corrections in the test definitions (Issue #167) identified during release review by @jimfengjinhua in #172
- Adding error scenarios according to CAMARA testing guideline to networks, profiles and areas APIs by @jimfengjinhua in #177
- Adding additional sunny day test definitions for networks, areas and profiles APIs, testing additional query parameter combinations and pagination by @jimfengjinhua in #178
- Making test case scenario names unique and operation specific by @jimfengjinhua in #183
Changed
- N/A
Fixed
- N/A
Removed
- N/A
New Contributors
- @hubertp-ericsson made their first contribution in #83
- @jordijoangimenez made their first contribution in #117
- @jimfengjinhua made their first contribution in #120
Full Changelog: r1.2...r2.2