Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.558  Word version:  19.1.0

Top   Top   Up   Prev   Next
0…   5…   6…   6.2a…   6.2b…   6.3…   6.4…   7…   8…   8.3…   8.3.3…   8.3.3.3…   8.4…   8.4.3…   8.4.4…   8.5…   8.6…   8.6.3…   8.6.4…   8.6.6…   8.7…   8.8…   8.8.2.5…   8.8.2A…   8.8.3…   8.8.4…   8.8.5…   8.9…   8.14…   8.14.3…   8.15…   8.17…   8.17.3…   8.17.4…   8.18…   8.19…   8.20…   9…   A…   A.4…   A.5…   B…   E…

 

7  Identities and commonly used valuesp. 47

7.1  Generalp. 47

The following clauses list identities and commonly used values that are used in this technical specification.

7.2  Identitiesp. 48

7.2.1  Generalp. 48

The following clauses specify a collection of identities that are associated with entities defined and being used in this specification.

7.2.2  Edge Enabler Client ID (EECID)p. 48

The EECID is a globally unique value that identifies an EEC.

7.2.3  Edge Enabler Server ID (EESID)p. 48

The EESID identifies an EES and each EES connected with the PLMN has a unique EESID within PLMN domain.

7.2.4  Edge Application Server ID (EASID)p. 48

The EASID is a globally unique identifier which identifies a particular application for e.g. SA6Video, SA6Game etc. All EAS instances (e.g. of SA6Video application) will share the same EASID.

7.2.5  Application Client ID (ACID)p. 48

The ACID identifies the client side of a particular application, for e.g. SA6Video viewer, SA6MsgClient etc. For example, all SA6MsgClient clients will share the same ACID.
In case that the UE is running mobile OS, the ACID is a pair of OSId and OSAppId.

7.2.6  UE IDp. 48

The UE ID uniquely identifies a particular UE within a PLMN domain. UE ID can be:
  1. a GPSI, as defined in TS 23.501.
  2. an EEL-generated Edge UE ID, as defined in clause 7.2.9
Up

7.2.7  UE Group IDp. 48

The UE Group ID uniquely identifies a group of UE within a PLMN domain. Following identities are examples that can be used:
  1. internal group ID, as defined in TS 23.501; and
  2. external group ID, as defined in TS 23.501.

7.2.8  EEC Context IDp. 48

The EEC Context ID is a globally unique value which identifies a set of parameters associated with the EEC (e.g., due to registration) and maintained in the Edge Enabler Layer by EESs.
If the EEC registration request does not include a previously assigned EEC Context ID value, the receiver EES assigns a new EEC Context ID and creates an EEC Context as described in the Table 8.2.8-1.
Providing a previously assigned EEC Context ID at registration allows maintaining the EEC Context in the Edge Enabler Layer beyond the lifetime of a registration, subject to policies. If the EEC registration request does include a previously assigned EEC Context ID value, after EEC Context relocation, the receiver EES may assign a new EEC Context ID, subject to implementation and local policies.
Up

7.2.9  Edge UE ID |R18|p. 49

The Edge UE ID is an identifier that is associated with the UE ID (GPSI as per clause 7.2.6) and managed by EES. The EES can generate Edge UE ID as needed (e.g. as per ECSP policy). Edge UE ID can be shared with the EAS directly (using UE Identifier API as per clause 8.6.5) and/or indirectly via AC (using UE ID request as per clause 8.14.2.6) in order for it to be used by the EAS over EDGE-3 interactions when it is not desired to share the UE ID (GPSI as per clause 7.2.6) with the EAS. The Edge UE ID can be temporary to limit the access of the EAS when needed.
Up

7.2.10  EAS bundle information |R18|p. 49

The EAS bundle information includes EAS bundle type, a list of EASIDs or a EAS bundle ID. The EAS bundle information may also include main EASID and EAS bundle requirements. EAS bundle ID establishes an association between the EASs. When included in the EAS profile, EAS bundle ID denotes the bundle to which the EAS belongs. When included in the AC profile EAS bundle ID is used to perform different Edge Enabler Layer operations, such as EAS discovery. Edge Enabler Layer handles the EASs belonging to the same bundle as required by related EAS bundle requirements as described in clause 8.2.10.
Up

7.2.11  Application Group ID |R18|p. 49

Application Group ID uniquely identifies a group of UEs using the same application. It is allocated (either dynamically or pre-configured in the AC) by the ASP and is unique within the application. ACs supporting the same application on different OS (e.g., iOS, Android), and therefore differing ACIDs (as specified in clause 7.2.5), can have the same Application Group ID.
Up

7.3  Commonly used valuesp. 50

7.3.1  Generalp. 50

Void.

7.3.2  UE locationp. 50

The UE location identifies where the UE is connected to the network or the position of the UE. It provides consistent definition of the UE's location across the UE and network entities. Following values are examples of UE locations that can be used:
  1. Cell Identity, Tracking Area Identity, GPS Coordinates or civic addresses as defined in clause 4.15.3 of TS 23.502.

7.3.3  Service areasp. 50

7.3.3.1  Generalp. 50

ECSPs and ASPs may allow access to Edge Computing service from specific areas i.e. allowing only the UEs within that area to access functional entities resident in the EDN. This area is called service area.
Some functional elements make decisions based on the topological location of the UE, (e.g. the cell it is connected to) while others make decisions based on the UE's geographical location (e.g. its geographical coordinates).
Functional elements that are aware of both topological and geographical information can translate one value to the other.
Up

7.3.3.2  Topological Service Areap. 50

A Topological Service Area is defined in relationship with a UE's point of connection to the network, such as: a collection of Cell IDs, Tracking Area Identities or the PLMN ID. Any UE that is attached to the Core Network from a cell whose ID is in this list, can be served by the functional entity in the EDN that is configured to serve that Topological Service Area.
Up

7.3.3.3  Geographical Service Areap. 50

A Geographical Service Area is an area that is specified by geographical units as defined in TS 23.032, such as: Geographical coordinates, an area that is defined as a circle whose centre is denoted by geographical coordinates, an area that is defined by a polygon whose corners are denoted by geographical coordinates. A Geographical Service Area can also be expressed in other ways such as: a well-known buildings, parks, arenas, civic addresses or ZIP code etc.
Applications can be configured to serve UEs that are in a specified geographical area and deny service from UEs that are not located in that area.
Up

7.3.3.4  EDN service areap. 50

A service area from which the access to the EDN is allowed. ECSPs can use LADNs, as described in Annex A.2.4 of this document, to deploy EDNs with access restricted from specific areas. When an EDN is deployed using LADN, the EDN service area is same as the LADN service area and rules specified for LADN apply to the UE, as specified in TS 23.501.
In a deployment using DNs other than LADNs, the EDN service area is the whole PLMN for non-roaming scenario.
The EDN service area may be expressed as a Topological Service Area.
Up

7.3.3.5  EES Service Areap. 51

A service area from which the access to the EES is allowed. This service area is equal to or a subset of the service area of the EDN in which the EES resides.
The EES service area may be expressed as a Topological Service Area, a Geographical Service Area or both.

7.3.3.6  EAS service areap. 51

A service area from which the access to the EAS is allowed. This service area is equal to or a subset of the service area of the EES which serves the EAS.
The EAS service area may be expressed as a Topological Service Area, a Geographical Service Area or both.

Up   Top   ToC