Skip to content

QOD_0.8.0_Documentation#1

Open
ravindrapalaskar17 wants to merge 8 commits intomainfrom
ravindrapalaskar17_QOD_080_Documentation
Open

QOD_0.8.0_Documentation#1
ravindrapalaskar17 wants to merge 8 commits intomainfrom
ravindrapalaskar17_QOD_080_Documentation

Conversation

@ravindrapalaskar17
Copy link
Copy Markdown
Owner

Added New Image file in resource.

@ravindrapalaskar17 ravindrapalaskar17 changed the title Add files via upload QOD_0.8.0_Documentation Nov 11, 2022
Copy link
Copy Markdown

@akoshunyadi akoshunyadi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The correct branching for Camara contributions is described here: https://mywiki.confluence.telekom.de/pages/viewpage.action?pageId=1435539866


**App-Flow**
Describes the precise flow the developer wants to prioritize and have stable bandwidth/latency for. This flow is described using source and destination IP addresses, ports and protocols with flow direction.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not correct, the v0.8.0 uses ueId and asId and no protocol.

# Overview

<span class="colour" style="color:rgb(0, 0, 0)">The Quality-On-Demand (QoD 0.8.0) API provides programmable interface for developers and other users (capabilities consumers) to specify stable data-transfer throughput/latency managed by Telco networks, without necessity to have in-depth knowledge of the 4G/5G system complexity by abstracting the internal complexity of telecom systems [1].</span>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The API version shouldn't be contained in the text, maybe as a extra field.

| Snippet 1. Create QoS session |
|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| curl -X 'POST' `https://sample-base-url/qod/api/v0/sessions` <br> -H 'accept: application/json' <br> -H 'Content-Type: application/json'<br> -H "Authorization: Bearer eyJ0eXAiOiJKV1QiLCJhbG...."<br> -d '{<br> "duration": 3600,<br> "ueId": "10.0.0.1",<br> "asId": "54.204.25.0/28",<br> "asPorts": "33001",<br> "qos": "QOS\_L",<br> "notificationUri": `https://your-callback-server.com/notifications` ,<br> "notificationAuthToken": "c8974e592c2fa383d4a3960714"<br> }' |
<br>
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parameters are incorrect ueId, asId, asPorts

| 7 | Forbidden | 403 | "Forbidden to invoke operation" |
| 8 | Session with same parameters already exists | 409 | "Found session \<session> already active until \<expirationTime>" |
| 9 | Service unavailable | 503 | “Internal error due to requrired telco service unvailability" |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The table should have the columns: HTTP status code, error code, error message. Please check the implementation!


* QoS session with 1H duration and QoS-profile "L" mapping,
* App-Flow is specified for UDP protocol with UE-Terminal IP address (ueAddr=10.0.0.1), Application server network (asAddr=54.204.25.0/28) and Port number (asPorts=33001).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no ueAddr, asAddr, port spec is different, please check the spec.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants