Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.280  Word version:  19.0.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.16.3…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C… 
7 Functional model  7.1 General  7.2 Description of the planes  7.3 Functional model description  7.3.1 On-network functional model 
...

 

7  Functional model  p. 33

7.1  General  p. 33

The functional model for the MC services architecture is defined as a series of planes to allow for the breakdown of the architectural description.
Further, each plane is expected to operate in an independent manner, providing services to the connected planes as and when requested by the connected plane, and requesting services from other planes as required.
As a consequence of this each plane should manage on its own behalf:
  1. use of identities. Each plane is therefore responsible for the privacy of that plane's own identities; and
  2. security for that plane. This does not preclude a plane requesting security services from another plane, but that is a decision made within the plane, as to whether to use offered security services or mechanisms within the plane itself.
Up

7.2  Description of the planes  p. 33

The following planes are identified:
  1. application plane: The application plane provides all of the services (e.g. call control, floor control, video control, data control) required by the user together with the necessary functions to support MC service. It uses the services of the signalling control plane to support those requirements. For example, within the MCPTT service, the application plane also provides for the conferencing of media, and provision of tones and announcements; and
  2. signalling control plane: The signalling control plane provides the necessary signalling support to establish the association of users involved in an MC service, such as an MCPTT call or other type of MC services. The signalling control plane also offers access to and control of services across MC services. The signalling control plane uses the services of the bearer plane.
Bearers supporting these planes are defined for LTE within TS 23.401. The resource control that is needed to support these planes is defined within TS 23.203. The application plane also relies on the use of multicast bearers established via procedures defined in TS 23.468 and TS 23.246.
Up

7.3  Functional model description  p. 33

7.3.1  On-network functional model  p. 33

Each MC service can be represented by an application plane functional model. The functional model across MC services may be similar but is described by the individual functional entities and reference points that belong to that MC service. Within the application plane for an MC service there is a common set of functions and reference points. The common set is shared across services. This common set of functions and reference points is known as the common services core.
Figure 7.3.1-1 shows the functional model for the application plane for an MC system.
Reproduction of 3GPP TS 23.280, Fig. 7.3.1-1: Functional model for application plane for an MC system
Figure 7.3.1-1: Functional model for application plane for an MC system
Up
The common services core functions and reference points shown in Figure 7.3.1-1 are shared across each MC service. The description of the functions and reference points specific to an MC service is contained in the corresponding MC service TS.
In the model shown in Figure 7.3.1-1, the following apply:
  • A specific MC service server is an instantiation of a GCS AS in accordance with TS 23.468.
  • The functional alias management client is an integrated functional entity of the configuration management client. The functional alias management client is described in subclause 7.4.2.2.12.
  • The functional alias management server is an integrated functional entity of the configuration management server. The functional alias management server is described in subclause 7.4.2.2.13.
Figure 7.3.1-2 shows the functional model for the signalling control plane.
Reproduction of 3GPP TS 23.280, Fig. 7.3.1-2: Functional model for signalling control plane
Figure 7.3.1-2: Functional model for signalling control plane
Up
Figure 7.3.1-3 shows the relationships between the reference points of the application plane of an MC service server and the signalling plane.
Reproduction of 3GPP TS 23.280, Fig. 7.3.1-3: Relationships between reference points of MC service application plane and signalling control planes
Figure 7.3.1-3: Relationships between reference points of MC service application plane and signalling control planes
Up
Up

Up   Top   ToC