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

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.17…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C… 
9.3 Architecture model for off-network operations  9.3.1 Off-network architectural model diagram  9.3.2 UE 3  9.3.3 UE 4  9.3.4 Offline common services server  9.4 Architecture model for roaming 
...

 

9.3  Architecture model for off-network operations  p. 67

9.3.1  Off-network architectural model diagram  p. 67

Figure 9.3.1-1 shows the off-network architectural model for the MC system solution for inter-UE communication, where no relay function is used.
Reproduction of 3GPP TS 23.280, Fig. 9.3.1-1: Off-network architectural model for inter-UE communication where no relay function is used
Figure 9.3.1-1: Off-network architectural model for inter-UE communication where no relay function is used
Up
Figure 9.3.1-2 shows the off-network architectural model for the MC system solution for configuration management and group management.
Reproduction of 3GPP TS 23.280, Fig. 9.3.1-2: Off-network architectural model for configuration management and group management
Figure 9.3.1-2: Off-network architectural model for configuration management and group management
Up
The offline common services server could be the same entity (or set of entities) as the common services core. In this case the configuration management server shall not configure to the same user on the same UE, with parameters provisioned by offline and online configuration simultaneously. The configuration management server shall not configure to the same user on the same UE for the same parameters by using CSC-11 and CSC-4 reference points simultaneously.
The entities within this model are described in the following subclauses and a full functional model is given in subclause 7.3.2.
Up

9.3.2  UE 3  p. 67

The UE 3 is a UE using ProSe and supporting application(s) related to off-network MC service, and is composed of the following functional entities:
  • for MC services, MC service clients as described in subclause 7.4.2.3.1 with relevant application functions of the specific MC service defined in the corresponding MC service TS;
  • for signalling control, a signalling user agent as described in subclause 7.4.3.1.1;
  • for configuration management, a configuration management client as described in subclause 7.4.2.2.1; and
  • for group management, a group management client as described in subclause 7.4.2.2.3.
Up

9.3.3  UE 4  p. 68

The UE 4 represents one or more UEs with the same functionality as UE 3.

9.3.4  Offline common services server  p. 68

The offline common services server supports configuration applications related to MC service, and is composed of the following functional entities:

9.4  Architecture model for roaming  p. 68

Roaming is achieved using either:

Up   Top   ToC