You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: code/API_definitions/Discovery/simple_edge_discovery.yaml
+44-26
Original file line number
Diff line number
Diff line change
@@ -12,23 +12,24 @@ info:
12
12
Cloud Zone to a particular user device.
13
13
14
14
# Purpose
15
-
Network operators may host multiple Multi-access Edge Cloud Zones in a given
16
-
territory. Connecting your application to a server on the closest Edge Cloud
17
-
Zone means packets travel the shortest distance between endpoints,
18
-
typically resulting in the lowest round-trip latency. Note, the physical
19
-
(GPS) location of a user device is not a reliable way to determine the
20
-
closest Edge Cloud Zone, due to the way operator networks are routed - so the
21
-
operator will calculate the Edge Cloud Zone with the _shortest network path_
22
-
to the network-attached device identified in the API request.
15
+
Network operators may host multiple Multi-access Edge Cloud Zones in a
16
+
given territory. Connecting your application to a server on the closest
17
+
Edge Cloud Zone means packets travel the shortest distance between
18
+
endpoints, typically resulting in the lowest round-trip latency. Note, the
19
+
physical (GPS) location of a user device is not a reliable way to determine
20
+
the closest Edge Cloud Zone, due to the way operator networks are routed -
21
+
so the operator will calculate the Edge Cloud Zone with the
22
+
_shortest network path_to the network-attached device identified in the API
23
+
request.
23
24
24
25
Once you have the name of the closest Edge Cloud Zone to the user device,
25
26
you may:
26
27
27
28
* connect the application client on the user device to your application
28
29
server instance on that Edge Cloud Zone. Note: the address of that server
29
30
instance is not part of the API response, but should be known in advance.
30
-
* or, if you have no instance on that Edge Cloud Zone, you may wish to deploy
31
-
one there.
31
+
* or, if you have no instance on that Edge Cloud Zone, you may wish to
32
+
deploy one there.
32
33
33
34
# Usage
34
35
@@ -91,8 +92,10 @@ info:
91
92
92
93
## Success
93
94
94
-
A JSON object is returned containing an array with a single member object. This contains identifiers for the closest Edge Cloud Zone. The HTTP
95
-
status code will be`200 OK`. An example response:
95
+
A JSON object is returned containing an array with a single member object.
96
+
This contains identifiers for the closest Edge Cloud Zone. The HTTP status
97
+
code will be`200 OK`. An example response:
98
+
96
99
```
97
100
[
98
101
{
@@ -145,7 +148,9 @@ info:
145
148
# Authorization and authentication
146
149
147
150
CAMARA guidelines defines a set of authorization flows which can grant API
148
-
clients access to the API functionality, as outlined in the document [CAMARA-API-access-and-user-consent.md](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-API-access-and-user-consent.md).
151
+
clients access to the API functionality, as outlined in the document
0 commit comments