Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  18.4.0

Top   Top   Up   Prev   Next
1…   5…   6   7…   7.3.2   7.4…   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.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.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

9  Application of functional model to deploymentsp. 55

9.1  Generalp. 55

This clause describes the application of the functional model, described in clause 7, to on-network and off-network deployments. It also describes deployment scenarios that highlight some of the possible variations in the way that the functional model can be applied in different situations.

9.2  Architecture model and deployment scenarios for on-network operationsp. 55

9.2.1  On-network architectural modelp. 55

9.2.1.1  On-network architectural model diagramp. 55

Figure 9.2.1.1-1 below is the on-network architectural model for the MC system solution, where the MC system provides one or more MC services via a single PLMN.
Reproduction of 3GPP TS 23.280, Fig. 9.2.1.1-1: On-network architectural model
Up

9.2.1.2  Application services layerp. 56

9.2.1.2.1  Overviewp. 56
The application services layer includes application functions of one or more MC services and any required supporting functions grouped into common services core.
9.2.1.2.2  Common services corep. 56
Common services core is composed of the following functional entities:
Up
9.2.1.2.3  MC servicesp. 56
MC services are composed of the following functional entities:
  • an MC service server as described in subclause 7.4.2.3.2 with relevant application functions of the corresponding MC service defined in the corresponding MC service TS.

9.2.1.3  SIP corep. 57

The SIP core provides rendezvous (contact address binding and URI resolution) and service control (application service selection) functions. It is composed of the following functional entities:
Up

9.2.1.4  EPSp. 57

The EPS provides point-to-point and point-to-multipoint bearer services with QoS.

9.2.1.5  UE 1p. 57

UE 1 is:
  • an MC service UE in on-network mode supporting bearer services and application(s) related to one or more MC service;
  • an MC service UE that acts as ProSe UE-to-network relay; or
  • both of the above.
When acting as an MC service UE in on-network mode supporting bearer services and application(s) related to one or more MC services, UE 1 is composed of the same functional entities as for UE 2, as described in subclause 9.2.1.6, without the support of ProSe capabilities.
Up

9.2.1.6  UE 2p. 57

UE 2 is a device using ProSe UE-to-network relay, and supporting application(s) related to one or more MC services. It is composed of the following functional entities:
Up

Up   Top   ToC