Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.1.0

Top   Top   Up   Prev   Next
0…   4…   6…   6.4…   6.5…   7…   8…   8.2.2…   9…   9.3…   9.3.6…   9.4…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.4…   11…   11.3…   12…   13…   14…   14.3…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6…   14.4…   15…   A…

 

4  Architectural requirementsp. 18

4.1  Generalp. 18

4.1.1  Descriptionp. 18

This subclause specifies the general requirements for SEAL.

4.1.2  Requirementsp. 18

[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 service events.
[AR-4.1.2-e]
The API interactions between the vertical application server(s) and SEAL server(s) shall conform to CAPIF as specified in TS 23.222.
[AR-4.1.2-f]
The SEAL server(s) shall provide a service API compliant with CAPIF as specified in TS 23.222.

4.2  Deployment modelsp. 18

4.2.1  Descriptionp. 18

This subclause specifies the requirements for various deployment models.

4.2.2  Requirementsp. 18

[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 within and outside the PLMN domain at the same time.
[AR-4.2.2-d]
The SEAL shall support SEAL capabilities for centralized deployment of vertical applications.
[AR-4.2.2-e]
The SEAL shall support SEAL capabilities for distributed deployment of vertical applications.
Up

4.3  Location managementp. 19

4.3.1  Descriptionp. 19

This subclause specifies the requirements for location management service.

4.3.2  Requirementsp. 19

[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.3.2-d]
The SEAL shall support client location reporting based on triggers.
[AR-4.3.2-e]
The SEAL shall enable vertical applications to receive updates to the location information.
[AR-4.3.2-f]
The SEAL shall enable sharing the network location information obtained from the 3GPP network systems to the vertical applications.
[AR-4.3.2-g]
The SEAL shall provide a mechanism to enable vertical applications to obtain a list of UE(s), and the location information of each UE, in the proximity to a designated/requested location.
Up

4.4  Group managementp. 19

4.4.1  Descriptionp. 19

This subclause specifies the requirements for group management service.

4.4.2  Requirementsp. 19

[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 (temporarily or permanently) into a single group by the authorized users or VAL server wherein all the group members of the constituent groups are designated as members of the merged group.

4.5  Configuration managementp. 19

4.5.1  Descriptionp. 19

This subclause specifies the requirements for configuration management service.

4.5.2  Requirementsp. 20

[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.

4.6  Key managementp. 20

4.6.1  Descriptionp. 20

This subclause specifies the requirements for key management service.

4.6.2  Requirementsp. 20

[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.

4.7  Identity managementp. 20

4.7.1  Descriptionp. 20

This subclause specifies the requirements for identity management service.

4.7.2  Requirementsp. 20

[AR-4.7.2-a]
The SEAL shall enable the access to SEAL services from the vertical application layer entities to be authorized.

4.8  Network resource managementp. 20

4.8.1  Descriptionp. 20

This subclause specifies the requirements for network resource management service.

4.8.2  Requirementsp. 20

[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 support announcement of multicast bearers to the UEs.
[AR-4.8.2-d]
The SEAL shall support switching of bearers between unicast and multicast.
[AR-4.8.2-e]
The SEAL shall support multicast bearer quality detection.

5  Involved business relationshipsp. 20

Figure 5-1 shows the business relationships that exist and that are needed to support a single VAL user.
Reproduction of 3GPP TS 23.434, Fig. 5-1: Business relationships for VAL services
Up
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 provider can have VAL service agreements with several VAL users. The VAL user can have VAL service agreements with several VAL service providers.
The VAL service provider and the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The VAL service provider can have SEAL provider arrangements with multiple SEAL providers and the SEAL provider can have PLMN operator service arrangements with multiple home PLMN operators. The SEAL provider and the VAL service provider or the home PLMN operator can be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The home PLMN operator can have PLMN operator service arrangements with multiple VAL service providers and the VAL service provider can have PLMN operator service arrangements with multiple home PLMN operators. As part of the PLMN operator service arrangement between the VAL service provider and the home PLMN operator, PLMN subscription arrangements can be provided which allows the VAL UEs to register with home PLMN operator network.
The home PLMN operator can have PLMN roaming agreements with multiple visited PLMN operators and the visited PLMN operator can have PLMN roaming agreements with multiple home PLMN operators.
Up

Up   Top   ToC