Figure 14.2.2.1-1 illustrates the generic on-network functional model for network resource management.
The network resource management client communicates with the network resource management server over the NRM-UU reference point. The network resource management client provides the support for network resource management functions to the VAL client(s) over NRM-C reference point. The VAL server(s) communicate with the network resource management server over the NRM-S reference point.
The network resource management server obtains and controls the multicast/broadcast resource from the underlaying 3GPP network system by communicating with the BM-SC via MB2-C and xMB-C reference points towards LTE eMBMS and with the 5G MBS control plane functions via Nmb13, Nmb10 or N33 towards the 5GS. The network resource management server communicates with the PCRF via Rx reference point or communicates with the PCF via N5 reference point to control the unicast resources from the underlying 3GPP network system. The network resource management server communicates with the SCEF via T8 reference point or communicates with the NEF via N33 reference point to perform event monitoring procedures from the underlying 3GPP network system. The network resource management server interacts with NEF via N33 to obtain QoS monitoring information from the 5GS.
Figure 14.2.2.1-2 exhibits the service-based interfaces for providing and consuming group management services. The network resource management server could provide service to VAL server and network resource management client through interface Snrm.
Figure 14.2.2.1-3 illustrates the service-based representation for utilization of the 5GS network services based on the 5GS SBA specified in
TS 23.501.
Figure 14.2.2.1-4 illustrates the service-based representation for utilization of the Core Network northbound APIs via CAPIF.
The Network resource management server and VAL server act as authorized API invoker to consume services from the Core Network northbound API entities like NEF which act as API Exposing Function as specified in
TS 23.222.
The architecture for integration of the 5G with
TSN [36] is depicted in
Figure 14.2.2.2-1. The SEAL Network Resource Management (NRM) server acts as a TSN AF (defined in
clause 5.28.1 of TS 23.501). TSN CNC (defined in
[35]) via the NRM-S reference point configures the TSN flows in the 5GS. In this case the NRM-S supports the IEEE 802.1Qcc management protocol. As a TSN AF the SEAL NRM server interacts with the 5GS PCF over the N5 reference point to configure the 5G QoS and TSCAI parameters in the 5GS.
Acting as the TSN AF the NRM server collects 5GS TSN Bridge information by interaction with the 5GS via the N5 reference point, as described in in
TS 23.502 Annex F.1.
NRM server triggers via N5 the AF request procedure as described in
TS 23.502 Annex F.2.
5G TSC refers to time sensitive communication service offered within the 5G system (i.e. without integration with a TSN system) by the 5GS for the UEs connected to the 5GS. The architecture for the 5G TSC is depicted in
Figure 14.2.2.3-1. The SEAL NRM server acts as an AF towards the 5G Core Network and performs coordination of QoS flows to fulfill the end-to-end QoS requirements for the UEs involved in the TSC communication. It combines the roles of TSCTSF and TSC CNC (similar to the TSN CNC in the TSN integration case), which means that it controls the allocation of resources of TSC communication within the boundaries of the 5G domain.
Upon request from a VAL server via the NRM-S reference point it configures the TSC end-to-end QoS flows in the 5GS. In line with other SEAL service enablers the SEAL NRM server provides a RESTful interface on the NRM-S reference point. As a TSCTSF the SEAL NRM server interacts with the 5GS PCF over the N84 reference point to configure the 5G QoS and TSCAI parameters in the 5GS.