hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.8 Traffic management
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.8.1 General
| This clause specifies the requirements for traffic management.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.8.2 Requirements
| [AR-5.2.8.2-a] The application layer architecture shall support AF influence on traffic routing over N6 interface.
[AR-5.2.8.2-b] The application layer architecture should be able to monitor the network status (e.g. traffic volume, throughput, network load, etc.) that may impact the application KPIs.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.9 Lifecycle management
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.9.1 General
| This clause specifies the requirements for lifecycle management.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.9.2 Requirements
| [A.5.2.9.2-a] The application layer architecture shall support interactions with a lifecycle management system.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.10 Edge application KPIs
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.10.1 General
| This clause specifies the requirements for edge application KPIs.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.10.2 Requirements
| [AR-5.2.10.2-a] The application layer architecture shall provide mechanisms for the EAS to publish its KPIs or application level requirements when available (e.g. upon new application on-boarding).
[AR-5.2.10.2-b] The application layer architecture shall provide mechanisms for the EAS to update its KPIs or application... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.11 Service continuity
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.11.1 General
| This clause specifies the requirements for service continuity.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.11.2 Requirements
| [AR-5.2.11.2-a] The application layer architecture shall provide mechanisms to support service continuity such that the Application Context with a S-EAS is transferred to a T-EAS.
[AR-5.2.11.2-b] The application layer architecture shall provide mechanisms to support service continuity such that the Application Context... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6 Application layer architecture
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.1 General
| This clause provides the overall architecture description:
- Clause 6.2 describes the functional architecture and corresponding considerations to support roaming and federation scenarios as well as interactions with cloud services;
- Clause 6.3 describes the functional entities;
- Clause 6.4 describes the service-ba... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.2 Architecture
| This clause describes the architecture for enabling edge applications in the following representations:
- A service-based representation, where the Edge Enabler Layer functions (e.g. ECS) enable other authorized Edge Enabler Layer functions (e.g. EES) to access their services. This representation also includes point-t... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3 Functional entities
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.1 General
| This clause describes the functional entities of the architecture for enabling edge applications.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.2 Edge Enabler Server (EES)
| EES provides supporting functions needed for EASs and EEC.
Functionalities of EES are:
a) provisioning of configuration information to EEC, enabling exchange of application data traffic with the EAS;
b) providing API invoker and API exposing functions as specified in 3GPP TS 23.222 [6]. To support deployments specif... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.3 Edge Enabler Client (EEC)
| EEC provides supporting functions needed for AC(s).
Functionalities of EEC are:
a) retrieval of configuration information to enable the exchange of Application Data Traffic with the EAS;
b) discovery of EASs available in the EDN;
c) detecting UE mobility events;
d) exposure of events of interest to AC;
e) retriev... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.4 Edge Configuration Server (ECS)
| ECS provides supporting functions needed for the EEC to connect with an EES.
Functionalities of ECS are:
a) provisioning of Edge configuration information to the EEC. The Edge configuration information includes the following:
1) the information for the EEC to distinguish amongst the EESs (e.g. EDN service area); and... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.5 Application Client (AC)
| AC is the application resident in the UE performing the client function. Depending on how ACR is implemented, the AC might be required to decide whether to initiate ACR. Other details of the AC are out of scope of this specification.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.6 Edge Application Server (EAS)
| EAS is the application server resident in the EDN, performing the server functions. The AC connects to the EAS in order to avail the services of the application with the benefits of Edge Computing.
It is possible that the server functions of an application are available only as an EAS.
However, it is also possible t... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.7 Notification management client
| Notification management client is as specified in 3GPP TS 23.434 [13].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.8 Notification management server
| Notification management server is as specified in 3GPP TS 23.434 [13].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.9 Cloud Enabler Server (CES)
| CES provides supporting functions needed for CASs. The CES is part of the EEL and it does not have service area restriction. CES facilitates service continuity between EAS and CAS. The CES re-uses most of the EES services.
Functionalities of the CES are:
a) providing access to network capability information (e.g. loc... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.3.10 Cloud application server (CAS)
| CAS is the application server resident in the cloud, performing the server functions. The AC connects to the CAS in order to avail the services of the application.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.4 Service-based interfaces
| The architecture for enabling edge applications contains the following service-based interfaces:
Eecs: Service-based interface exhibited by ECS.
Eees: Service-based interface exhibited by EES.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5 Reference Points
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.1 General
| This clause describes the reference points of the architecture for enabling edge applications.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.2 EDGE-1
| EDGE-1 reference point enables interactions between the EES and the EEC. It supports:
a) registration and de-registration of the EEC to the EES;
b) retrieval and provisioning of EAS configuration information;
c) discovery of EASs available in the EDN; and
d) service continuity procedures (e.g. ACR initiation).
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.3 EDGE-2
| EDGE-2 reference point enables interactions between the EES and the 3GPP Core Network functions and APIs for retrieval of network capability information. It supports:
- access via SCEF and NEF APIs as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], 3GPP TS 29.522 [4], 3GPP TS 23.682 [17], 3GPP TS 29.122 [5]; or
- ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.4 EDGE-3
| EDGE-3 reference point enables interactions between the EES and the EASs. It supports:
a) registration of EASs with availability information (e.g. time constraints, location constraints);
b) de-registration of EASs from the EES;
c) discovery of T-EAS information to support ACT;
d) providing access to network capabi... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.5 EDGE-4
| EDGE-4 reference point enables interactions between the ECS and the EEC. It supports:
a) provisioning of Edge configuration information to the EEC.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.6 EDGE-5
| EDGE-5 reference point enables interactions between AC(s) and the EEC. It supports:
a) registration, registration update and de-registration of AC to the EEC;
b) EAS discovery by the AC;
c) ACR triggering by the AC;
d) EEC services subscription; and
e) UE ID request.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.7 EDGE-6
| EDGE-6 reference point enables interactions between the ECS and the EES. It supports:
a) registration of EES information to the ECS;
b) de-registration of EES information from the ECS; and
c) retrieval of the T-EES information from the ECS; and
d) subscription and notification for service continuity related events... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.8 EDGE-7
| EDGE-7 reference point enables interactions between the EAS and the 3GPP Core Network functions and APIs for retrieval of network capability information. It supports:
- access via SCEF and NEF APIs as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], 3GPP TS 29.522 [4], 3GPP TS 23.682 [17], 3GPP TS 29.122 [5]; or
-... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.9 EDGE-8
| EDGE-8 reference point enables interactions between the ECS and the 3GPP Core Network functions and APIs for retrieval of network capability information. It supports:
- access via SCEF and NEF APIs as defined in 3GPP TS 23.501 [2], 3GPP TS 23.502 [3], 3GPP TS 29.522 [4], 3GPP TS 23.682 [17], 3GPP TS 29.122 [5]; or
-... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.10 EDGE-9
| EDGE-9 reference point enables interactions between two EESs. EDGE-9 reference point may be provided between EES within different EDN (Figure 6.5.10-1) and within the same EDN (Figure 6.5.10-2).
Figure 6.5.10-1: Inter-EDN EDGE-9
Figure 6.5.10-2: Intra-EDN EDGE-9
EDGE-9 supports:
a) discovery of T-EAS informatio... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.11 NM-UU
| NM-UU reference point is as specified in 3GPP TS 23.434 [13].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.12 NM-S
| NM-S reference point is as specified in 3GPP TS 23.434 [13], where EES or ECS acts VAL server.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.13 NM-C
| NM-C reference point is as specified in 3GPP TS 23.434 [13], where EEC acts as VAL client.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.14 ECI-1
| ECI-1 enables interaction between CAS and EES. ECI-1 supports:
a) notifying the CAS about selection of an EES to provide edge enabler services;
b) discovery of T-EAS to support ACT from CAS to T-EAS; and
c) selected T-EAS declaration where CAS acts as S-EAS.
ECI-1 supports:
a) ACR status update between EES and CA... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.15 ECI-2
| ECI-2 enables interaction between CAS and ECS.
NOTE: ECI-2 functionalities are not specified in the current release.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.16 ECI-3
| ECI-3 enables interaction between CES and ECS.
ECI-3 supports:
a) T-EES retrieval procedure.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.17 ECI-4
| ECI-4 enables interaction between CES and EES.
ECI-4 supports:
a) EEC context relocation procedure; and
b) ACR parameter information procedure.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.18 CLOUD-1
| CLOUD-1 enables interaction between CAS and CES.
CLOUD-1 supports:
a) providing access to network capability information (e.g. location information);
b) requesting the setup of a data session between AC and CAS with a specific QoS and receiving QoS related information; and
c) service continuity procedures (e.g. ACR... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.19 CLOUD-2
| CLOUD-2 enables interaction between CES and CES.
NOTE: CLOUD-2 functionalities are not specified in the current release.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.20 CLOUD-3
| CLOUD-3 enables interaction between CAS and the 3GPP core network.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.21 CLOUD-4
| CLOUD-4 enables interaction between CES and the 3GPP core network.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.5.22 EDGE-10
| EDGE-10 reference point enables interactions between the ECS and another ECS. It supports:
a) service provisioning information retrieval.
b) registration and de-registration of the ECS to the ECS acting as edge repository; and
c) retrieval or discovery of information about other ECS(s) of the federation.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6 Cardinality rules
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.1 General
| The cardinality rules are applied to the architecture specified in clause 6.2. The cardinality rules are classified as functional entity cardinality and reference point cardinality. The functional entity cardinality specifies the multiplicity of the functional entity that can exist as per the architecture. The referenc... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2 Functional Entity Cardinality
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.1 General
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.2 AC
| The following cardinality rules apply for ACs:
a) one or more ACs may be located in a UE.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.3 EEC
| The following cardinality rules apply for EECs:
a) One or more EEC(s) may be located in a UE.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.4 ECS
| The following cardinality rules apply for ECSs:
a) One or more ECS(s) may be deployed to support one EDN;
b) One ECS may be deployed to support one or more EDN(s);
c) One or more ECS(s) may be deployed by a PLMN operator; and
d) One or more ECS(s) may be deployed by an ECSP.
Following cardinality rule apply to the... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.5 EES
| The following cardinality rules apply for EES:
a) One or more EES(s) may be located in an EDN; and
b) One or more EES(s) may be located in an EDN per ECSP.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.6 EAS
| The following cardinality rules apply for EASs:
a) One or more EAS(s) may be located in an EDN.
NOTE: EAS(s) belonging to the same EASID can be deployed with EES(s) of multiple ECSP(s) in an EDN.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.7 CES
| The following cardinality rules apply for CES:
a) One CES may be located in a cloud DN per ECSP.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.2.8 CAS
| The following cardinality rules apply for CASs:
a) One or more CAS(s) may be located in a cloud DN.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3 Reference Point Cardinality
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.1 General
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.2 EDGE-1 (Between EEC and EES)
| The following cardinality rules apply for EDGE-1:
a) One EEC may communicate with one or more EES(s) for one or more AC concurrently; and
b) One EES may communicate with one or more EEC(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.3 EDGE-3 (Between EAS and EES)
| The following cardinality rules apply for EDGE-3:
a) One EAS may communicate with only one EES within the same EDN; and
b) One EES may communicate with one or more EAS(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.4 EDGE-4 (Between EEC and ECS)
| The following cardinality rules apply for EDGE-4:
a) One EEC may communicate with one or more ECS(s) concurrently; and
b) One ECS may communicate with one or more EEC(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.5 EDGE-5 (Between AC and EEC)
| The following cardinality rules apply for EDGE-5:
a) One AC may communicate with only one EEC; and
b) One EEC may communicate with one or more AC(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.6 EDGE-6 (Between EES and ECS)
| The following cardinality rules apply for EDGE-6:
a) One EES may communicate with one or more ECS(s) concurrently; and
b) One ECS may communicate with one or more EES(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.7 EDGE-9 (Between EES and EES)
| The following cardinality rules apply for EDGE-9:
a) One EES may communicate with one or more EES(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.8 EDGE-10 (Between ECS and ECS)
| Following cardinality rules apply for EDGE-10:
a) One ECS may communicate with one or more ECS(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.9 ECI-1 (Between CAS and EES)
| The following cardinality rules apply for ECI-1:
a) One CAS may communicate with one or more EES(s) concurrently; and
b) One EES may communicate with one or more CAS(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.10 ECI-2 (Between CAS and ECS)
| The following cardinality rules apply for ECI-2:
a) One CAS may communicate with one or more ECS(s) concurrently; and
b) One ECS may communicate with one or more CAS(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.11 ECI-3 (Between CES and ECS)
| The following cardinality rules apply for ECI-3:
a) One CES may communicate with one or more ECS(s) concurrently; and
b) One ECS may communicate with one or more CES(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.12 ECI-4 (Between CES and EES)
| The following cardinality rules apply for ECI-4:
a) One CES may communicate with one or more EES(s) concurrently; and
b) One EES may communicate with one or more CES(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.13 CLOUD-1 (Between CAS and CES)
| The following cardinality rules apply for CLOUD-1:
a) One CAS may communicate with only one CES within the same cloud DN; and
b) One CES may communicate with one or more CAS(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.6.3.14 CLOUD-2 (Between CES and CES)
| The following cardinality rules apply for CLOUD-2:
a) One CES may communicate with one or more CES(s) concurrently.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.7 Capability exposure for enabling edge applications
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.7.1 General
| The Figure 6.7.1-1 shows the capability exposure for enabling edge applications.
Figure 6.7.1-1: Capability exposure for enabling edge applications
Capability exposure includes the 3GPP core network (i.e. 5GC, EPC), ECS and the EES capability exposure, to fulfil the needs of the edge service operations. The capabil... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.7.2 APIs provided by the Edge Enabler Layer
| Table 6.7.2-1 summarizes the APIs exposed by the ECS.
Table 6.7.2-1: APIs provided by the ECS
API Name
Known Consumers
References
Eecs_ServiceProvisioning
EEC
8.3
Eecs_EESRegistration
EES
8.4.4
Eecs_TargetEESDiscovery
EES, CES
8.8.3.3
Eecs_ECSRegistration
ECS
8.17.2.2
Eecs_ECSDiscovery
ECS
8.17.2.3
... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.8 Capability exposure for enabling cloud applications with edge applications, with CES support
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.8.1 General
| The Figure 6.8.1-1 shows the capability exposure for enabling cloud applications with edge applications, when CES is used.
Figure 6.8.1-1: Capability exposure for enabling cloud applications with edge applications with CES
To enable the interworking with Cloud Application Server (CAS) and Cloud Enabler Server (CES)... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.9 Capability exposure for enabling cloud applications with edge applications
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 6.9.1 General
| The Figure 6.9.1-1 shows the capability exposure for enabling cloud applications with edge applications.
Figure 6.9.1-1: Capability exposure for enabling cloud applications with edge applications
The Cloud Application Server residing in the cloud DN, outside the EDN, may need to interact with the EEL entities for e... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7 Identities and commonly used values
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.1 General
| The following clauses list identities and commonly used values that are used in this technical specification.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2 Identities
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.1 General
| The following clauses specify a collection of identities that are associated with entities defined and being used in this specification.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.2 Edge Enabler Client ID (EECID)
| The EECID is a globally unique value that identifies an EEC.
NOTE: Security and privacy aspects related to EECID are specified in 3GPP TS 33.558 [23].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.3 Edge Enabler Server ID (EESID)
| The EESID identifies an EES and each EES connected with the PLMN has a unique EESID within PLMN domain.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.4 Edge Application Server ID (EASID)
| 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.
NOTE: The definition of the EASID is in 3GPP TS 24.558 [29] and 3GPP TS 29.558 [30].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.5 Application Client ID (ACID)
| 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.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.6 UE ID
| The UE Identifier (UE ID) uniquely identifies a particular UE within a PLMN domain. UE ID can be:
a) a GPSI, as defined in 3GPP TS 23.501 [2].
NOTE 1: For user's privacy reasons, GPSI in the form of MSISDN can be used only after obtaining user's consent.
NOTE 2: To protect user's privacy, if MSISDN cannot be used th... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.7 UE Group ID
| The UE Group ID uniquely identifies a group of UE within a PLMN domain. Following identities are examples that can be used:
a) internal group ID, as defined in 3GPP TS 23.501 [2]; and
b) external group ID, as defined in 3GPP TS 23.501 [2].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.8 EEC Context ID
| 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 Conte... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.9 Edge UE ID
| 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... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.10 EAS bundle information
| 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 bel... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.2.11 Application Group ID
| 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 c... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.3 Commonly used values
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.3.1 General
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 7.3.2 UE location
| 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:
a) Cell Identity, Tracking Area Identity, GPS Coordinates or civic ad... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.