Find Optimal 5G Edge Platforms

Find the 5G Mobile Edge Computing (MEC) node that is optimal to use for your application.

 

Get MEC Platforms

Returns the optimal 5G Edge platforms for deployment based on a region, service profile of the service that you want to deploy or user equipment. The ern of each platform in the response contains the name of the matching AWS Wavelength zone that can be used when deploying.

Note: Send a GET /regions request first to identify the region that you want to query in a GET /mecplatforms request.

Note: For the initial release of the Edge Discovery Service API, maxLatencyMs is the only service profile property that is compared with 5G Edge platform capabilities.

HTTP Request

 

GET https://5gedge.verizon.com/api/mec/eds/mecplatforms

 

See also:

HEADER PARAMETERS: application/json

The request header must contain a current ThingSpace authorization bearer token and must set the content-type to JSON. For more information about tokens, see Getting Started

 

QUERY PARAMETERS: application/json

Note: Sending a request with all of the parameters will fail with a "400" error code. 

Use one of the following combinations:

  • region + service profile ID + subscriber density (density is optional but recommended)
  • region + UEIdentity (Including UEIdentity Type)
  • service profile ID + UEIdentity (Including UEIdentity Type)
  • region
    string

    The Region name of a Multi-access Edge Compute (MEC) region. Current valid regions are US_WEST_2 and US_EAST_1.

    Note: using US_WEST_1 or US_EAST_2 will cause a 500 error.

  • serviceProfileId
    string

    An individual service profile ID

  • subscriberDensity
    integer

    The minimum number of subscribers in the region

  • UEIdentityType
    string

    The type of User Equipment identifier used for the query

    Note: Only the identifier of IPAddress is currently available

  • UEIdentity
    string

    The User Equipment identifier. This can be in IPv4 or IPv6 format for IP Address

PATH PARAMETERS: application/json

None

 

REQUEST BODY: application/json

None

 

Responses

Note: For cases where user input exceeds the boundary values an additional "data" key will be returned with a relevant description. The error response returns an additional data key value beyond the error values listed here. 

 

RESPONSE BODY SCHEMA: application/json

  • Success response
    schema
    {
       "MECPlatforms": [
           {
             "ern": "string",
             "zone": null,
             "region": "string",
             "status": "unknown",
             "properties": [
                {
                   "type": "string",
                   "data": {}
                 }
              ]
          }
       ]
    }
    
Response Parameters
Parameter Description
ern An Edge Resource Name. This is the identifier for an Edge Resource to use as a connection.
zone A zone is a sub-set of a region, like a neighborhood within a city or a municipality within a county. This is future functionality, so the response will be "null".
region A region is a defined area of coverage.
status Current status, or "Health", of a MEC platform. Values are: active, inactive and unknown.
properties Additional service support information for the MEC platform.

RESPONSE BODY SCHEMA: application/json

  • status
    string

    HTTP status code

  • message
    string

    Error details

RESPONSE BODY SCHEMA: application/json

  • status
    string

    HTTP status code

  • message
    string

    Error details

RESPONSE BODY SCHEMA: application/json

  • status
    string

    HTTP status code

  • message
    string

    Error details