Content for TS 23.558 Word version: 18.1.0
7 Identities and commonly used values p. 33
7.1 General p. 33
The following clauses list identities and commonly used values that are used in this technical specification.
7.2 Identities p. 33
7.2.1 General p. 33
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. 33
The EECID is a globally unique value that identifies an EEC.
7.2.3 Edge Enabler Server ID (EESID) p. 33
The EESID identifies an EES and each EESID is unique within PLMN domain.
7.2.4 Edge Application Server ID (EASID) p. 34
The EASID identifies a particular application for e.g. SA6Video, SA6Game etc. For example, all Edge SA6Video Servers will share the same EASID.
7.2.5 Application Client ID (ACID) p. 34
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 ID p. 34
The UE ID uniquely identifies a particular UE within a PLMN domain. Following identities are examples that can be used:
- GPSI, as defined in TS 23.501.
7.2.7 UE Group ID p. 34
The UE Group ID uniquely identifies a group of UE within a PLMN domain. Following identities are examples that can be used:
7.2.8 EEC Context ID p. 34
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.
7.3 Commonly used values p. 34
7.3.1 General p. 34
7.3.2 UE location p. 34
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:
- 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 areas p. 35
7.3.3.1 General p. 35
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.
7.3.3.2 Topological Service Area p. 35
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.
7.3.3.3 Geographical Service Area p. 35
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.
7.3.3.4 EDN service area p. 35
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.
7.3.3.5 EES Service Area p. 35
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 area p. 36
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.
