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

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

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

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.

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.

The UE Identifier (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.

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.

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.

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.

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.

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.

Void.

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.