Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
documentation
Manage
Activity
Members
Labels
Plan
Issues
5
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
3
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package Registry
Container Registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
OCF
documentation
Commits
3ca8cd5b
Commit
3ca8cd5b
authored
1 month ago
by
Jorge Moratinos
Browse files
Options
Downloads
Patches
Plain Diff
Copied information for ppt presented on TECH meeting
parent
e2d29213
1 merge request
!29
Resolve "Vendor extensibility Documentation"
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/vendor-ext/vendor-ext.md
+60
-1
60 additions, 1 deletion
doc/vendor-ext/vendor-ext.md
with
60 additions
and
1 deletion
doc/vendor-ext/vendor-ext.md
+
60
−
1
View file @
3ca8cd5b
# Vendor Extensibility
This is a mechanism for the APIs to re-use, extend their functionalities and data models and engage with third-party API frameworks.
DOC:Work in Progress
Is defined on 3GPP TS 29.122 and 29.500 and is tightly connected with “supported-features” and feature negotiation
## Supported Features in Publish API:

## Types of vendor extensions
**Data models**
*
Extend the information element with vendor specific fields
### Fields have specific naming schemes:
*
Using the 6-digit IANA-assigned enterprise code:
```
"vendorSpecific-010415": {
...
}
```
*
Using domain name:
```
"vendorSpecific-3gpp.org": {
...
}
```
*
Using URN:
```
"vendorSpecific-urn:3gpp:example": {
...
}
```
## Discover Query Parameters
*
Provisioning of vendor-specific query parameters to support additional vendor-specific filtering criteria
### A vendor-specific query parameter shall be encoded as follows:
*
query parameter name:
```
"vend-spec-<query parameter name>”
```
*
query parameter value encoded as JSON object:
*
"target"
*
"value"
**Example:**
```
GET {apiRoot}/3gpp-monitoring-event/v1/{scsAsId}/subscriptions?vend-spec-max-reports={"target": "/maximumNumberOfReports", value: "6"}
```
[
OCF Web
]:
https://ocf.etsi.org/
"OCF Web"
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment