Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.0.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…

 

6  Generic functional model for SEAL servicesWord‑p. 22

6.1  GeneralWord‑p. 22

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 vertical application layer:
  • Location management;
  • Group management;
  • Configuration management;
  • Identity management;
  • Key management; and
  • Network resource management.
The generic functional model for the SEAL is organized into generic functional entities to describe a functional architecture which addresses the application layer support aspects for vertical applications. The on-network and off-network functional model is specified in this clause.
Up

6.2  On-network functional model descriptionWord‑p. 22

Figure 6.2-1 illustrates the generic on-network functional model for SEAL.
Reproduction of 3GPP TS 23.434, Fig. 6.2-1: Generic on-network functional model
Up
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.
The SEAL functional entities on the UE and the server are grouped into SEAL client(s) and SEAL server(s) respectively. The SEAL consists of a common set of services (e.g. group management, location management) and reference points. The SEAL offers its services to the vertical application layer (VAL).
The SEAL client(s) communicates with the SEAL server(s) over the SEAL-UU reference points. SEAL-UU supports both unicast and multicast delivery modes. The SEAL client(s) provides the service enabler layer support functions to the VAL client(s) over SEAL-C reference points. The VAL server(s) communicate with the SEAL server(s) over the SEAL-S reference points. The SEAL server(s) may communicate with the underlying 3GPP network systems using the respective 3GPP interfaces specified by the 3GPP network system.
The specific SEAL client(s) and the SEAL server(s) along with their specific SEAL-UU reference points and the specific network interfaces of 3GPP network system used are described in the respective on-network functional model for each SEAL service.
Figure 6.2-2 illustrates the functional model for interconnection between SEAL servers.
Reproduction of 3GPP TS 23.434, Fig. 6.2-2: Interconnection between SEAL servers
Up
To support distributed SEAL server deployments, the SEAL server interacts with another SEAL server for the same SEAL service over SEAL-E reference point.
Figure 6.2-3 illustrates the functional model for inter-service communication between SEAL servers.
Reproduction of 3GPP TS 23.434, Fig. 6.2-3: Inter-service communication between SEAL servers
Up
The SEAL server interacts with another SEAL server for inter-service communication over SEAL-X reference point.
Figure 6.2-4 illustrates the functional model for communication between SEAL server and VAL user database.
Reproduction of 3GPP TS 23.434, Fig. 6.2-4: Communication between SEAL server and VAL user database
Up
The SEAL server interacts with the VAL user database for storing and retrieving user profile over VAL-UDB reference point.
Figure 6.2-5 shows the functional model for the signalling control plane.
Reproduction of 3GPP TS 23.434, Fig. 6.2-5: Functional model for signalling control plane
Up

6.3  Off-network functional model descriptionWord‑p. 25

Figure 6.3-1 illustrates the generic off-network functional model for SEAL.
Reproduction of 3GPP TS 23.434, Fig. 6.3-1: Generic off-network functional model
Up
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 of UE2 over SEAL-PC5 reference points. The UE1, if connected to the network via Uu reference point, can also act as a UE-to-network relay, to enable UE2 to access the VAL server(s) over the VAL-UU reference point.
The specific SEAL client(s) along with their specific SEAL-PC5 reference points are described in the respective off network functional model for each SEAL service.
Up

Up   Top   ToC