Commit 5a07b995 authored by Yann Garcia's avatar Yann Garcia
Browse files

Bug fixed in fed-api.yaml; Change version to 1.11.0-beta FSCOM

parent 935aad6f

config/api/fed-api.yaml

+57 −4
Original line number Diff line number Diff line
@@ -12,7 +12,7 @@ externalDocs: 
  description: "ETSI GS MEC 040 Federation enablement API, v3.2.1"

  url: https://www.etsi.org/deliver/etsi_gs/MEC/001_099/040/03.02.01_60/gs_MEC040v030201p.pdf

servers:

- url: https://localhost/sandboxname/fed_enablement/v1

- url: https://localhost/sandboxname/sandboxname/sandboxname/sandboxname/fed_enablement/v1

tags:

- name: systemInfo

- name: subscription
@@ -710,7 +710,8 @@ paths: 
        x-exportParamName: Path.serviceId

      responses:

        "200":

          description: "Upon success, a response body containing data type describing the specific subscription data type is returned."

          description: "Upon success, a response body containing data type describing\

            \ the specific subscription data type is returned."

          content:

            application/json:

              schema:
@@ -949,8 +950,60 @@ components: 
        \ as a part of the \nUpdate of MEC system(s) to the federation.\n"

    EndPointInfo:

      title: EndPointInfo

      type: object

      properties:

        uris:

          type: array

          description: "Entry point information of the service as string, formatted\

            \ according to URI syntax (see IETF RFC 3986 [8]). Shall be used for REST\

            \ APIs. See note."

          items:

            type: string

      description: "Endpoint information (e.g. URI, FQDN, IP address) of MEC federator."

        fqdn:

          type: array

          description: Fully Qualified Domain Name of the service. See note.

          items:

            type: string

        addresses:

          type: array

          items:

            $ref: '#/components/schemas/Addresses'

        alternative:

          type: string

          description: "Entry point information of the service in a format defined\

            \ by an implementation, or in an external specification. See\_note."

      description: "NOTE: Exactly one of \"uris\", \"fqdn\", \"addresses\" or \"alternative\"\

        \ shall be present. \n"

      example:

        uris:

        - uris

        - uris

        addresses:

        - port: 0

          host: host

        - port: 0

          host: host

        fqdn:

        - fqdn

        - fqdn

        alternative: alternative

    Addresses:

      required:

      - host

      - port

      type: object

      properties:

        host:

          type: string

          description: Host portion of the address.

        port:

          type: integer

          description: Port portion of the address.

      description: Entry point information of the service as one or more pairs of

        IP address and port. See note.

      example:

        port: 0

        host: host

    SystemUpdateNotificationSubscription:

      title: SystemUpdateNotificationSubscription

      required:

js-apps/frontend/src/js/containers/home/home-page-container.js

+1 −1
Original line number Diff line number Diff line
@@ -71,7 +71,7 @@ class HomePageContainer extends Component { 
                (4G, 5G, Wi-Fi, MEC Federation) and terminal types. Combining these assets in a geolocated environment, a user can gain

                hands-on experience on the behaviour and capabilities of the Location (MEC013), Radio Network

                Information (MEC012), Traffic Management APIs (MEC015), Device application interface (MEC016), Application Mobility (MEC021), WLAN Information (MEC028),

                V2X Information API (MEC030) service API, MEC Federation Service API (MEC040) service APIs and Sensors-Sharing Services (MEC046).

                V2X Information API (MEC030) service API, MEV IoT API (MEC 033), MEC Federation Service API (MEC040) service APIs and Sensors-Sharing Services (MEC046).

                MEC Sandbox provides also a support for Edge Native Connector (3GPP TS 29.222: 3rd Generation Partnership Project; Technical Specification Group Core

                Network and Terminals; Common API Framework for 3GPP Northbound APIs).

              </p>