hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.3.9 Trigger XR transmission request
| Table 9.12.3.9-1 describes the information flow from the SEALDD server to the SEALDD client to trigger XR transmission connection operation between two UEs.
Table 9.12.3.9-1: Trigger XR transmission request
Information element
Status
Description
Requestor ID
M
Identity of the requestor (i.e. SEALDD server).
VAL... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.3.10 Trigger XR transmission response
| Table 9.12.3.10-1 describes the information flow from the SEALDD client to the SEALDD server to acknowledge XR transmission connection operation between two UEs.
Table 9.12.3.10-1: Trigger XR transmission response
Information element
Status
Description
Result
M
Result of the operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4 APIs
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4.1 General
| Table 9.12.4.1-1 illustrates the APIs exposed by SEALDD server for XR transmission.
Table 9.12.4.1-1: List of SEALDD server APIs for XR transmission
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_multi-modalTransmission
Request
Request/Response
VAL server
Sdd_XRTransmissionConnnection
Establish
... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4.2 Sdd_multi-modalTransmission Request operation
| API operation name: Sdd_multi-modalTransmission Request
Description: The consumer requests for one time for multi-modal transmission service.
Inputs: See clause 9.12.3.1.
Outputs: See clause 9.12.3.2
See clause 9.12.2.1.2 and 9.12.2.2.2 for details of usage of this operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4.3 Sdd_XRTransmissionConnection_Establish operation
| API operation name: Sdd_XRTransmissionConnection_Establish
Description: The consumer requests for multi-modal transmission connection establishment.
Inputs: See clause 9.12.3.3.
Outputs: See clause 9.12.3.4.
See clause 9.12.2.1.2 and 9.12.2.2.2 for details of usage of this operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4.4 Sdd_SEALDD-UUcConnectionEstablish operation
| API operation name: Sdd_SEALDD-UUcConnectionEstablish
Description: The consumer requests for SEALDD-UUc connection establishment between the SEALDD client on 3GPP UE and tethered device.
Inputs: See clause 9.12.3.5.
Outputs: See clause 9.12.3.6.
See clause 9.12.2.3.4 for details of usage of this operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4.5 Sdd_XRTransmissionConnection_Trigger operation
| API operation name: Sdd_XRTransmissionConnection_Trigger
Description: The consumer requests to trigger direct multi-modal transmission connection establishment between two UEs.
Inputs: See clause 9.12.3.7.
Outputs: See clause 9.12.3.8.
See clause 9.12.2.4 for details of usage of this operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.12.4.6 Sdd_XRTransmissionConnection_Inform operation
| API operation name: Sdd_XRTransmissionConnection_Inform
Description: The consumer informs direct multi-modal transmission connection establishment between two UEs.
Inputs: See clause 9.12.3.9.
Outputs: See clause 9.12.3.10.
See clause 9.12.2.4 for details of usage of this operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13 SEALDD enabled adaptive data transmission
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.1 General
| The following clauses specify procedures, information flows and APIs about SEALDD enabled adaptive data transmission.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.2 SEALDD enabled adaptive data transmission
| Figure 9.13.2-1 illustrate the procedure for supporting adaptive data transmission. The SEALDD facilitates to transmit data between the VAL client and VAL server adaptively by using application enablement layer capabilities of the AIML Enablement server defined in 3GPP TS 23.482 [xx]. This procedure is used to support ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.3 Information flows
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.3.1 SEALDD adaptive data transmission request
| Table 9.13.3.1-1 describes the information flow from the consumer to the SEALDD server for requesting or updating request for an adaptive data transmission.
Table 9.13.3.1-1: SEALDD adaptive data transmission request
Information element
Status
Description
Requestor ID
M
(NOTE)
The identifier of the consumer (e.... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.3.2 SEALDD adaptive data transmission response
| Table 9.13.3.2-1 describes the information from the SEALDD server to the consumer for responding to the adaptive data transmission request.
Table 9.13.3.2-1: SEALDD adaptive data transmission response
Information element
Status
Description
Result
M
The result of the request (positive or negative acknowledgement)... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.4 APIs
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.4.1 General
| Table 9.13.4.1-1 illustrates the APIs exposed by SEALDD server for adaptive data transmission.
Table 9.13.4.1-1: List of SEALDD server APIs for adaptive data transmission
API Name
API Operations
Operation Semantics
Consumer(s)
Sdd_AdaptiveTransmission
Request
Request/Response
VAL server, SEALDD client
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 9.13.4.2 Sdd_AdaptiveTransmission Request operation
| API operation name: Sdd_AdaptiveTransmission Request
Description: The consumer requests for adaptive data transmission service.
Inputs: See clause 9.13.3.1.
Outputs: See clause 9.13.3.2.
See clause 9.13.2 for details of usage of this operation.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10 SEALDD services over Satellite Access
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.1 General
| This clause provides clarifications on the procedures and information flows for enabling SEALDD services using satellite access.
|
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2 SEALDD enabled transmission for S&F Satellite operation
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.1 General
| This clause provides the services to support the transmission for delivery of delay-tolerant/non-real-time satellite services (i.e. CIoT/MTC, SMS) based on SEALDD capabilities including adapt the DL data delivery according to the S&F events from the 3GPP core network.
NOTE: In Store and Forward Satellite operation, th... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.2 Procedures
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.2.1 SEALDD enabled data transmission for delay-tolerant satellite services
| Figure 10.2.2.1-1 illustrates the procedure for establishing S&F data transmission connection, and the SEALDD facilitates the delay-tolerant satellite services to transmit its data between the VAL client and VAL server.
Pre-condition:
- The VAL server discovers and selects the SEALDD server by CAPIF functions.
Fig... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.2.2 Client initiated data transmission for delay-tolerant satellite services
| Figure 10.2.2.2-1 illustrates the procedure for establishing S&F data transmission connection, and the SEALDD facilitates the delay-tolerant satellite services to transmit data initiated by the VAL client to VAL server.
Pre-condition:
- The VAL client is aware of the availability of delay-tolerant satellite services ... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.3 Information flows
| |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.3.1 SEALDD enabled DTwithS&F transmission request
| Table 10.2.3.1-1 describes the information flow from the VAL server to the SEALDD server for requesting the delay-tolerant with S&F application transmission service.
Table 10.2.3.1-1: SEALDD enabled DTwithS&F transmission request
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.3.2 SEALDD enabled DTwithS&F transmission response
| Table 10.2.3.2-1 describes the information flow from the SEALDD server to the VAL server for responding to the delay-tolerant with S&F application transmission.
Table 10.2.3.2-1: SEALDD enabled DTwithS&F transmission response
Information element
Status
Description
Result
M
Success or failure.
SEALDD-S informati... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.3.3 SEALDD DTwithS&F transmission notification
| Table 10.2.3.3-1 describes the information flow from the SEALDD server to the VAL server to notify S&F delivery related events.
Table 10.2.3.3-1: SEALDD DL delivery notification
Information element
Status
Description
Event ID
O
(see NOTE)
Identifies event SEALDD client connection status for DL data delivery e.g... |
7c353f7900c6911ed12bf8daab944b90 | 23.433 | 10.2.3.4 Sdd_S&FTransmission_notification
| Table 10.2.3.4-1 describes the information flow from the SEALDD server to the SEALDD Client to notify the DL estimated delivery time.
Table 10.2.3.4-1: Sdd_S&FTransmission_notification
Information element
Status
Description
VAL server ID
M
Identity of the VAL server
VAL service ID
O
Identity of the VAL servic... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 1 Scope
| The present document specifies the functional architecture for service enabler architecture layer (SEAL) and the procedures, information flows and APIs for each service within SEAL in order to support vertical applications over the 3GPP system. The present document is applicable to vertical applications using E-UTRAN o... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 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.
-... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 3 Definitions, symbols and abbreviations
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 3.1 Definitions
| For the purposes of the present document, the terms and definitions 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].
VAL user: An authorized user, who can use a VAL UE to participate in one ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 3.2 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].
5GS 5G System
5GVN 5G Virtual Network
ASCAI Application Satell... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4 Architectural requirements
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.1 General
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.1.1 Description
| This subclause specifies the general requirements for SEAL.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.1.2 Requirements
| [AR-4.1.2-a] The SEAL shall support applications from one or more verticals.
[AR-4.1.2-b] The SEAL shall support multiple applications from the same vertical.
[AR-4.1.2-c] The SEAL shall offer SEAL services as APIs to the vertical applications.
[AR-4.1.2-d] The SEAL shall support notification mechanism for SEAL serv... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.2 Deployment models
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.2.1 Description
| This subclause specifies the requirements for various deployment models.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.2.2 Requirements
| [AR-4.2.2-a] The SEAL shall support deployments in which SEAL services are deployed only within PLMN network.
[AR-4.2.2-b] The SEAL shall support deployments in which SEAL services are deployed only outside of PLMN network.
[AR-4.2.2-c] The SEAL shall support deployments in which SEAL services are deployed both withi... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.3 Location management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.3.1 Description
| This subclause specifies the requirements for location management service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.3.2 On-network functional model requirements
| [AR-4.3.2-a] The SEAL shall enable sharing location data between client and server for vertical applications usage.
[AR-4.3.2-b] The SEAL shall support different granularity of location data, as required by the vertical application.
[AR-4.3.2-c] The SEAL shall support requests for on-demand location reporting.
[AR-4... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.3.3 Off-network functional model requirements
| [AR-4.3.3-a] The SEAL shall support on-demand location reporting and event-triggered location reporting within PC5 communication.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.4 Group management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.4.1 Description
| This subclause specifies the requirements for group management service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.4.2 Requirements
| [AR-4.4.2-a] The SEAL shall enable group management operations (e.g. CRUDN) by the authorized users or VAL server.
[AR-4.4.2-b] The SEAL shall enable creation of group to be used by one or more vertical applications within the same VAL system.
[AR-4.4.2-c] The SEAL shall enable two or more groups to be merged (tempor... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.5 Configuration management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.5.1 Description
| This subclause specifies the requirements for configuration management service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.5.2 Requirements
| [AR-4.5.2-a] The SEAL shall enable configuring service specific configuration data applicable to vertical applications.
[AR-4.5.2-b] The SEAL shall support configuring data applicable to different vertical applications.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.6 Key management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.6.1 Description
| This subclause specifies the requirements for key management service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.6.2 Requirements
| [AR-4.6.2-a] The SEAL shall support secure distribution of security related information (e.g. encryption keys).
[AR-4.6.2-b] The SEAL shall support all communications in SEAL ecosystem to be secured.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.7 Identity management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.7.1 Description
| This subclause specifies the requirements for identity management service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.7.2 Requirements
| [AR-4.7.2-a] The SEAL shall enable the access to SEAL services from the vertical application layer entities to be authorized.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.8 Network resource management
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.8.1 Description
| This subclause specifies the requirements for network resource management service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 4.8.2 Requirements
| [AR-4.8.2-a] The SEAL shall enable support for unicast bearer establishment and modification to support service KPIs for VAL communications.
[AR-4.8.2-b] The SEAL shall enable support for multicast bearer establishment and modification to support service KPIs for VAL communications.
[AR-4.8.2-c] The SEAL shall suppor... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 5 Involved business relationships
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 5.1 Business relationships for VAL services
| Figure 5.1-1 shows the business relationships that exist and that are needed to support a single VAL user.
Figure 5.1-1: Business relationships for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL service provi... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 5.2 Business relationships for VAL services with satellite connectivity
| Figure 5.2-1 shows the business relationship for VAL services with satellite connectivity.
Figure 5.2-1: Business relationships for VAL services with satellite connectivity
The PLMN operator has satellite service agreement with the satellite service provider to offer his services e.g. to serve the unconnected areas... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 5.3 Business relationships for VAL services involving SEAL client provider
| VAL service provider may get SEAL services by the following service agreements:
- Establishing the service agreement with SEAL server service provider directly as figure 5.3-1 shows, or
- Indirectly based on the service agreement between VAL service provider and SEAL client service provider, and SEAL client service ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6 Generic functional model for SEAL services
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.1 General
| The functional model for SEAL is organized into generic SEAL service functional model and specific SEAL service functional models. The generic SEAL service functional model will be used as the reference model for the specific SEAL service functional models.
The following SEAL services are supported towards the vertica... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.2 On-network functional model description
| Figure 6.2-1 illustrates the generic on-network functional model for SEAL.
Figure 6.2-1: Generic on-network functional model
In the vertical application layer, the VAL client communicates with the VAL server over VAL-UU reference point. VAL-UU supports both unicast and multicast delivery modes.
NOTE 1: The VAL-UU ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.3 Off-network functional model description
| Figure 6.3-1 illustrates the generic off-network functional model for SEAL.
Figure 6.3-1: Generic off-network functional model
In the vertical application layer, the VAL client of UE1 communicates with VAL client of UE2 over VAL-PC5 reference point. A SEAL client of UE1 interacts with the corresponding SEAL client ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4 Functional entities description
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.1 General
| Each subclause is a description of a functional entity corresponding to SEAL and does not imply a physical entity.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2 Application plane
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2.1 General
| Entities within the application plane of a VAL system provide application control and media specific functions to support one or more VAL services.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2.2 VAL client
| The VAL client provides the client side functionalities corresponding to the vertical applications (e.g. V2X client). The VAL client supports interactions with the SEAL client(s).
NOTE: The details of the VAL client is specific to the vertical and out of scope of the present document.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2.3 VAL server
| The VAL server provides the server side functionalities corresponding to the vertical applications (e.g. V2X application servers). The VAL server acts as CAPIF's API invoker as specified in 3GPP TS 23.222 [8].
NOTE: The details of the VAL server is specific to the vertical and out of scope of the present document.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2.4 SEAL client
| The SEAL client provides the client side functionalities corresponding to the specific SEAL service. The SEAL client(s) supports interactions with the VAL client(s). The SEAL client also supports interactions with the corresponding SEAL client between the two UEs.
NOTE: It is up to each SEAL client to support the app... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2.5 SEAL server
| The SEAL server provides the server side functionalities corresponding to the specific SEAL service. The SEAL server supports interactions with the VAL server(s). The SEAL server acts as CAPIF's API exposing function as specified in 3GPP TS 23.222 [8]. The SEAL server also supports interactions with the corresponding S... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.2.6 VAL user database
| This functional entity contains information of the user profile associated with a VAL service that is served by the VAL service provider at the application plane.
Each VAL service may have a corresponding user database e.g. MCPTT user database as defined in 3GPP TS 23.379 [3], MCVideo user database as defined in 3GPP ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3 Signalling control plane
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1 SIP entities
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.1 Signalling user agent
| This functional entity acts as the SIP user agent (both client and server) for all SIP transactions.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.2 SIP AS
| The SIP AS functional entity supports the following functions on behalf of the VAL service:
- influencing and impacting the SIP session; and
- supporting event subscription and event notification.
NOTE: In the IM CN subsystem, this is provided by the Application Server as defined in 3GPP TS 23.002 [14].
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.3 SIP core
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.3.1 General
| The SIP core contains a number of sub-entities responsible for registration, service selection and routing in the signalling control plane.
The SIP core shall be either:
1. compliant with 3GPP TS 23.228 [15], i.e. the SIP core is a 3GPP IP multimedia core network subsystem; or
2. a SIP core, which internally need no... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.3.2 Local inbound / outbound proxy
| The local inbound / outbound proxy functional entity acts as both an inbound proxy and an outbound proxy for all SIP transactions. This functional entity can provide the following functions:
- NAT traversal;
- Resource control;
- Route/forward requests and responses to the user agents;
- SIP signalling security; an... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.3.3 Registrar finder
| The registrar finder functional entity is responsible for:
a) Identifying the serving registrar / application service selection functional entity. The serving registrar / application service selection functional entity is identified using information provided either by the PLMN operator's own SIP database or the VAL ... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.3.4 Registrar / application service selection
| The registrar / application service selection functional entity provides the following functions:
- Registrar function (with integral provision of a location server) and also acts as an inbound proxy (with access to the integral location server), and outbound proxy for all SIP transactions where application service se... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.1.4 Diameter proxy
| This functional entity acts as a proxy agent for Diameter messaging as specified in IETF RFC 6733 [24].
The Diameter proxy, when used on the AAA-2 interface, is collocated with the migration management server.
Other instances of the Diameter proxy may also be present in the SIP core / IMS.
NOTE: The number of instan... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.2 SIP database
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.2.1 General
| The SIP database contains information concerning the SIP subscriptions and corresponding identity and authentication information required by the SIP core, and such information as application service selection.
In deployment scenarios where the PLMN operator provides the SIP core, this database is provided by the HSS.... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.2.2 SIP database logical functions
| The SIP database provides the following logical functions:
a) mobility management;
- provides the UE mobility through the SIP core.
b) registrar assignment support;
- provides to the registrar finder the required capabilities for VAL services based on VAL service provider requirements on a per-user basis, (e.g. whe... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.3 HTTP entities
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.3.1 HTTP client
| This functional entity acts as the client for all hypertext transactions.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.3.2 HTTP proxy
| This functional entity acts as a proxy for hypertext transactions between the HTTP client and one or more HTTP servers. The HTTP proxy terminates a TLS session on HTTP-1 with the HTTP client of the VAL UE allowing the HTTP client to establish a single TLS session for hypertext transactions with multiple HTTP servers th... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.3.3 HTTP server
| This functional entity acts as the HTTP server for all hypertext transactions.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.4 LWP entities
| |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.4.1 LWP client
| This functional entity acts as the light-weight protocol client for all transactions of the SEAL client executing in a constrained UE. A SEAL client executing in an unconstrained UE may choose to use the LWP client if it is available.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.4.2 LWP proxy
| This functional entity acts as a proxy for transactions between the LWP client and one or more LWP servers. The LWP proxy typically terminates a secure transport protocol (e.g. DTLS, TLS or secure WebSocket) session on LWP-1 reference point with the LWP client of the VAL UE allowing the LWP client to establish a single... |
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.4.3 LWP server
| This functional entity acts as the LWP server for all LWP transactions of the SEAL server.
NOTE: A SEAL client can act as LWP server for certain transactions as required by the SEAL service.
|
56c06b1a1bfa4b9f9d78b7b8cc808ade | 23.434 | 6.4.3.5 LWP usage
| LWP is a generic representation of a light-weight protocol for use in constrained environments. Realizations of the light-weight protocol (LWP) functional entities and reference points to a particular protocol are defined in the annexes of this specification.
LWP is a representation of a protocol to be used by the SEA... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.