hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.1 M5S Application Server originating message send request
| The information flows from the Application Server to the MSGin5G Server for message delivery includes the IEs in table 8.3.2-1. Additionally, the following information in table 9.1.2.1-2 elements needs to be included:
Table 9.1.2.1-2: M5S Northbound Message Delivery Send request
Information element
Status
Descripti... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.2 M5S Application Server originating message delivery status report request
| The information flows from the Application Server to the MSGin5G Server for message delivery status report includes the IE in table 8.3.4-1, and the following information in table 9.1.2.2-1 elements needs to be included:
Table 9.1.2.2-1: M5S Northbound Message Delivery Send request
Information element
Status
Descri... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.3 M5S Application Server registration request
| The information flows from the Application Server to the MSGin5G Server for registration request includes the information elements in Table 9.1.2.3-1.
Table 9.1.2.3-1: Application Server Registration request
Information element
Status
Description
AS service ID
M
The MSGin5G identifier of the Application Server.
... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.4 M5S Application Server registration response
| The information flows from the MSGin5G Server to the Application Server for registration response includes the information elements in Table 9.1.2.4-1.
Table 9.1.2.4-1: Application Server registration response
Information element
Status
Description
AS service ID
M
The MSGin5G identifier of the Application Server... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.5 M5S Application Server de-registration request
| The information flows from the Application Server to the MSGin5G Server for de-registration request includes the information elements in Table 9.1.2.5-1.
Table 9.1.2.5-1: Application Server de-registration request
Information element
Status
Description
AS service ID
M
The MSGin5G identifier of the Application Se... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.6 M5S Application Server de-registration response
| The information flows from the MSGin5G Server to the Application Server for de-registration response includes the information elements in Table 9.1.2.6-1.
Table 9.1.2.6-1: Application Server de-registration response
Information element
Status
Description
AS service ID
M
The MSGin5G identifier of the Application ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.1.2.7 M5S Send_MSGin5G_Message response notification
| The information flows from the MSGin5G Server to the Application Server for message response notification includes the IEs in table 8.3.2-3. Additionally, the following information in table 9.1.2.7-1 elements needs to be included:
Table 9.1.2.7-1: M5S Message response notification
Information element
Status
Descrip... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2 APIs provided by Message Gateway
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1 Ml3g APIs
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1.1 L3G_Message_Delivery API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1.1.1 General
| API description: This API enables the MSGin5G Server to deliver MSGin5G message to the Legacy 3GPP Message Gateway.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1.1.2 Send_Message operation
| API operation name: Send_MSGin5G_Message
Description: Send an MSGin5G message to Legacy 3GPP Message Gateway.
Known Consumers: M5S.
Inputs: Refer subclause 8.3.3
Outputs: Refer subclause 8.3.3
See subclause 8.3.3 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1.2 L3G_Delivery_Status_Report API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1.2.1 General
| API description: This API enables the MSGin5G Server to deliver a Delivery Status Report to the Legacy 3GPP Message Gateway.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.1.2.2 Report_Message_Delivery_Status operation
| API operation name: Report_Message_Delivery_Status
Description: Send an MSGin5G message delivery status report to Legacy 3GPP Message Gateway.
Known Consumers: M5S.
Inputs: Refer subclause 8.3.5
Outputs: Refer subclause 8.3.5
See subclause 8.3.5 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2 Mn3g APIs
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2.1 N3G_Message_Delivery API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2.1.1 General
| API description: This API enables the MSGin5G Server to deliver MSGin5G message to the Non-3GPP Message Gateway.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2.1.2 Send_Message operation
| API operation name: Create_MSGin5G_Message
Description: Send an MSGin5G message to Non-3GPP Message Gateway.
Known Consumers: M5S.
Inputs: Refer subclause 8.3.3
Outputs: Refer subclause 8.3.3
See subclause 8.3.3 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2.2 N3G_Delivery_Status_Report API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2.2.1 General
| API description: This API enables the MSGin5G Server to deliver a Delivery Status Report to the Non-3GPP Message Gateway.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.2.2.2 Report_Message_Delivery_Status operation
| API operation name: Report_Message_Delivery_Status
Description: Send an MSGin5G message delivery status report to Non-3GPP Message Gateway.
Known Consumers: M5S.
Inputs: Refer subclause 8.3.5
Outputs: Refer subclause 8.3.5
See subclause 8.3.5 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.3 Mbg APIs
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.3.1 Nbg_Message_Delivery API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.3.1.1 General
| API description: This API enables the MSGin5G Server to deliver MSGin5G messages to the Broadcast Message Gateway.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.2.3.1.2 Send_Message operation
| API operation name: Create_MSGin5G_Message
Description: Send an MSGin5G message to Broadcast Message Gateway.
Known Consumers: M5S.
Inputs: Refer subclause 8.3.3
Outputs: Refer subclause 8.3.3
See subclause 8.3.3 for the details of usage of this API operation.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3 APIs provided by MSGin5G Client
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1 Mm5c APIs
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1 M5C_AC_Message_Delivery API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.1 General
| API description: This API enables the Application Client to send MSGin5G message, MSGin5G message response and message delivery status to the MSGin5G Client.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.2 Send_MSGin5G_Message operation
| API operation name: Send_MSGin5G_Message
Description: Send an MSGin5G message to MSGin5G Client.
Known Consumers: Application Client
Inputs: Refer Request to send MSGin5G message in clause 8.11.4
Outputs: Refer MSGin5G message request to the MSGin5G Server in subclause 8.3.2
See subclause 8.11.4 for the details of... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.3 Send_MSGin5G_Message_Response operation
| API operation name: Send_MSGin5G_Message_Response
Description: Send an MSGin5G message response notification to MSGin5G Client.
Known Consumers: Application Client
Inputs: Refer the MSGin5G_Message response in subclause 8.11.5
Outputs: Refer the MSGin5G_Message response in subclause 8.3.2
See subclause 8.11.5 fo... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.4 Send_MSGin5G_Message delivery status operation
| API operation name: Send_MSGin5G_Message_Delivery_Status
Description: Send an MSGin5G Message delivery status to MSGin5G Client.
Known Consumers: Application Client
Inputs: Refer the MSGin5G_Message delivery status in subclause 8.11.5
Outputs: Refer the MSGin5G message delivery status report into the MSGin5G Serve... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.5 Receive_MSGin5G_Message_Notification operation
| API operation name: Receive_MSGin5G_Message_Notification
Description: Send an MSGin5G message as a Message notification to Application Client.
Known Consumers: Application Client
Inputs: Refer MSGin5G message request from MSGin5G Server in clause 8.3.3
Outputs: Refer Message received request in clause 8.11.5
See s... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.6 Receive_MSGin5G_Message_Response_Notification operation
| API operation name: Receive_MSGin5G_Message_Response_Notification
Description: Send an MSGin5G message response as a Message response notification to Application Client.
Known Consumers: Application Client
Inputs: Refer Message response sent by MSGin5G Server in clause 8.3.2
Outputs: Refer the MSGin5G Message res... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.1.7 Receive_MSGin5G_Message_Delivery_Status_Notification operation
| API operation name: Receive_MSGin5G_Message_Delivery_Status_Notification
Description: Send an MSGin5G Message delivery status to MSGin5G Client.
Known Consumers: Application Client
Inputs: Refer Message delivery status sent by MSGin5G Server in clause 8.3.2
Outputs: Refer the MSGin5G_Message delivery status in sub... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.2 M5C_AC_Registration API
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.2.1 General
| API description: This API enables the Application Client to register to MSGin5G Client.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.2.2 Registration operation
| API operation name: Registration
Description: Do registration or update registration to an MSGin5G Client, by using this API, the Application Client provides/updates its information, including the notification address, e.g. callback url, used for the message delivery from MSGin5G Client to Application Client.
Known ... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 9.3.1.2.3 Deregistration operation
| API operation name: De-registration
Description: Do deregistration with an MSGin5G Client
Known Consumers: Application Client
Inputs: Refer clause 8.11.3
Outputs: Refer clause 8.11.3
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10 Information Elements
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10.1 Payload
| The Payload Information Element carries the application payload that is transferred by the MSGin5G Service, of which the content is transparent to the MSGin5G Service.
If the message originates from an MSGin5G UE, the Payload IE is a string of maximum length that can be transported without segmentation but not more t... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10.2 Application ID
| The Application ID Information Element identifies the Application Client on the UE or in the Application Server.
The Application ID is a string, which shall allow identifying 65535 different Application Clients. The Application ID is configured or provisioned in the Application Client or the Application Server.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10.3 Messaging Topic
| The Messaging Topic Information Element indicates the topic of the message, which an interested UE or Application Server can subscribe to.
The Messaging Topic IE is a string, which shall allow identiying 65535 different Messaging Topics. Allocating and populating the Messaging Topic IE is done by the Application Clien... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10.4 Broadcast Area ID
| The Broadcast Area ID Information Element identifies the service area where the Broadcast Message will be delivered.
The Broadcast Area ID IE is a string, which shall allow identiying 65535 different Broadcast Areas. The Broadcast Area ID is provisioned on the Application Client or the Application Server and is mapped... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10.5 Message ID
| The Message ID Information Element uniquely identifies a specific MSGin5G message in the MSGin5G Service. If message delivery status report is requested by an MSGin5G message, the Message ID IE in this MSGin5G message is used by the sender of the MSGin5G message to match the message delivery status report with the orig... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 10.6 Failure Cause
| The Failure Cause Information Element indicates the the failure reason of an MSGin5G message, if this MSGin5G message can not be delivered successfully.
The Failure Cause IE is a string, which shall allow identiying 65535 different failure reasons.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 11 Deployment models
| |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 11.1 General
| This clause describes deployments of the functional model specified in clause 5.
|
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 11.2 Deployment of MSGin5G server(s)
| The MSGin5G server(s) should be deployed in the PLMN operator domain. The VAL service using MSGin5G service for the message delivery acts as Application Server and interacts with MSGin5G Server via MSGin5G-3 reference point. The MSGin5G server(s) connects with the 3GPP network system in one or more PLMN operator domain... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 11.3 Deployment of Message Gateway(s)
| Figure 11.3-1 illustrates the deployment of Message Gateway in a single PLMN operator domain. If only one Message Gateway, i.e. Message Gateway 1 in Figure 11.3-1, is deployed, all MSGin5G Servers in this PLMN domain may connected to a single Message Gateway to provide the MSGin5G service for the Non-MSGin5G UEs. Multi... |
8663f49cd6a7fb8a0488b42c64247911 | 23.554 | 11.4 Deployment of MSGin5G Server(s) and SEAL server(s)
| If an MSGin5G Server interacts with SEAL Servers over the SEAL-S reference point specified for each SEAL service, i.e. the SEAL Server are not collocated in the MSGin5G Server, the application of functional model to deployments of SEAL servers specified in 3GPP TS 23.434 [5] applied. In the deployment, MSGin5G acts as ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 1 Scope
| The present document specifies the application layer architecture, procedures and information flows necessary for enabling edge applications over 3GPP networks. It includes architectural requirements for enabling edge applications, application layer architecture fulfilling the architecture requirements and procedures t... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 2 References
| The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
-... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 3 Definitions of terms, symbols and abbreviations
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 3.1 Terms
| For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Application Context: A set of data about the Application Client that resides in the Edge ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 3.2 Symbols
| None.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 3.3 Abbreviations
| For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AC Application Client
ACID Application Client Identification
A... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4 Overview
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.1 General
| For edge computing, it is essential that the ACs are able to locate and connect with the most suitable application server available in the EDN, depending on the needs of the application. The edge enabler layer exposes APIs to support such capabilities.
The edge computing capabilities supported by 3GPP are illustrated ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.2 Service provisioning
| Service provisioning procedures supply the information required by the UE to access the edge services. The procedure takes UE's location, service requirements, service preferences and connectivity information into account to provide the required configuration. Service provisioning procedures are specified in clause 8.3... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.3 Registration
| Registration procedures specified in clause 8.4, allow entities (e.g. UE and Application Server) in the edge enabler layer to provide information about itself to other entities of the edge enabler layer.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.4 EAS discovery
| EAS discovery procedures enable the UE to obtain information about suitable EASs of interest (specified as discovery filters) in the EDN. EAS discovery procedures are specified in clause 8.5.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.5 Capability exposure to EAS and EEC
| The edge enabler layer exposes services towards the EASs and EECs. The exposed capabilities include the services of the Edge Enabler Layer and the re-exposed and enhanced services of the 3GPP core network. The capabilities exposed by the edge enabler layer are specified in clause 8.6 and the 3GPP network capability exp... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.6 Support for service continuity
| When a UE moves to a new location, different EASs can be more suitable for serving the UE. When no suitable EAS can be found for serving the UE, the service session may transition to a CAS. Such transitions can result from a non-mobility event of UE also, requiring support from the edge enabler layer to maintain the co... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.7 Security
| The edge enabler layer supports secure communication amongst the enabler layer entities. The security aspects for the edge enabler layer are specified in 3GPP TS 33.558 [23]. Clause 8.11 provides details on EEC authentication and authorization.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.8 Dynamic EAS instantiation triggering
| The Edge Enabler Layer can interact with the ECSP management system to trigger instantiation of a suitable EAS as per application needs. Details of the EAS instantiation triggering are specified in clause 8.12.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.9 Charging
| The general architecture and principles applicable for charging of Edge enabling services provided by an ECSP to an ASP, is specified in 3GPP TS 32.240 [24].
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.10 Common EAS discovery
| For the purpose of Common EAS discovery, it is relevant whether the deployment is with or without ECS-ER.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.11 Bundle EAS
| The bundle EAS contains two scenarios: direct bundle, proxy bundle. Both type of bundles are provided by the ASP
Direct bundle EAS: the AC interact with multiple EASs, so that the AC can obtain services from multiple EAS, then AC can process the data from multiple EASs and calculate the result based on the data obtain... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.11.1 Direct bundle
| For the purpose of direct bundle EAS discovery, the AC profile is configured the bundle type (direct bundle), bundle ID, list of EAS IDs which belongs to the direct bundle. Accordingly, the EAS profile is configured with the bundle type (direct bundle), bundle ID. The ECS identifies the EES(s) which support all the dir... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.11.2 Proxy bundle
| For the purpose of proxy bundle EAS discovery, the AC profile is configured with the bundle type (proxy bundle), bundle ID, main EAS ID. Accordingly, the main EAS profile is configured with the bundle type (proxy bundle), bundle ID, and list of EASIDs which belongs to the proxy bundle. The ECS identifies the EES which ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.12 Federation and Roaming
| Federation and Roaming is a scenario that UE consumes edge service involving two or more ECSPs. For example, two ECSPs (ECSP#1, ECSP#2) has business relationship that is the ECSP#2 can provide edge service to subscriber of ECSP#1, as for subscriber of ECSP#1, the ECSP#2 can be seen as partner ECSP. When ECSP#1' subscri... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 4.13 EAS content synchronization and Application context
| When a group of UEs with a common Application Group ID requires application service, the group of UE in different EDNs may connect to multiple common EASs; in such case, EAS content synchronization is required between the common EASs in different EDNs for the UEs in the group.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5 Architectural requirements
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.1 General
| This clause specifies architectural requirements for enabling edge applications in different functional aspects.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2 Architectural requirements
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.1 General requirements
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.1.1 General
| This clause specifies general requirements for the architecture.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.1.2 Requirements
| [AR-5.2.1.2-a] The application layer architecture shall support deployment of EAS(s) and AC(s) with or without modifications compared to their existing deployments.
[AR-5.2.1.2-b] The application layer architecture shall support different deployment models in conjunction with an operator's 3GPP network.
[AR-5.2.1.2-c... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.2 Edge configuration data
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.2.1 General
| This clause specifies the requirements for edge configuration data.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.2.2 Requirements
| [AR-5.2.2.2-a] The application layer architecture shall provide mechanisms to provide configuration parameters to an authorized EEC to access the EES(s).
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.3 Registration
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.3.1 General
| This clause specifies the requirements for EEC, EAS and EES registration.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.3.2 EEC registration
| [AR-5.2.3.2-a] The application layer architecture shall provide mechanisms for an EEC to register onto the EES.
[AR-5.2.3.2-b] The application layer architecture shall provide mechanisms for an EEC to de-register from the EES.
[AR-5.2.3.2-c] The application layer architecture shall provide mechanisms for the EES to d... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.3.3 EAS registration
| [AR-5.2.3.3-a] The application layer architecture shall provide mechanisms for an EAS to register to the EES.
[AR-5.2.3.3-b] The application layer architecture shall support EAS exposing its availability, which varies with time, location, etc.
[AR-5.2.3.3-c] The application layer architecture shall provide mechanisms... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.3.4 EES registration
| [AR-5.2.3.4-a] The application layer architecture shall provide mechanisms for an EES to register onto the ECS.
[AR-5.2.3.4-b] The application layer architecture shall support EES to publish EAS information on the ECS.
[AR-5.2.3.4-c] The application layer architecture shall support EES to update the published EAS inf... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.4 EAS discovery
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.4.1 General
| This clause specifies the requirements for EAS discovery.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.4.2 Requirements
| [AR-5.2.4.2-a] The application layer architecture shall provide mechanisms for an EEC to discover available EASs.
[AR-5.2.4.2-b] The application layer architecture shall provide relevant configuration information of the EASs to the EEC, in order to enable communication between ACs and the EASs.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.5 Capability exposure to EASs
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.5.1 General
| This clause specifies the requirements for capability exposure to EAS.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.5.2 Requirements
| [AR-5.2.5.2-a] The application layer architecture shall support exposure of 3GPP network's capabilities to the EASs.
[AR-5.2.5.2-b] The application layer architecture shall support exposure of EES's capabilities to the EASs.
[AR-5.2.5.2-c] The application layer architecture shall support exposure of EAS's capabilitie... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.6 Security
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.6.1 General
| This clause specifies the security requirements.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.6.2 Requirements
| [AR-5.2.6.2-a] The application layer architecture shall provide mechanisms for the Edge Computing Service Provider to authorize the usage of Edge Computing services by the EEC.
[AR-5.2.6.2-b] The application layer architecture shall provide mechanisms for the Edge Computing Service Provider to authorize the usage of ... |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.7 Subscription service
| |
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.7.1 General
| This clause specifies the requirements for a subscription service.
|
9141d8823335b14b481449c07d4caae6 | 23.558 | 5.2.7.2 Requirements
| [AR-5.2.7.2-a] The application layer architecture shall provide subscription and notification mechanisms enabling an EEC to receive changes in dynamic information of EASs from an EES.
[AR-5.2.7.2-b] The application layer architecture shall provide subscription and notification mechanisms enabling an EEC to receive cha... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.