WO2021234639A1

WO2021234639A1 - Dynamic tsc service provision

Info

Publication number: WO2021234639A1
Application number: PCT/IB2021/054396
Authority: WO
Inventors: Marilet DE ANDRADE JARDIM; Kun Wang; Kefeng ZHANG
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-05-20
Filing date: 2021-05-20
Publication date: 2021-11-25

Abstract

Systems and methods are disclosed for dynamic management of a Time Sensitive Communication (TSC) service(s) in a cellular communications system. In one embodiment, a Network Exposure Function (NEF) in a core network of a cellular communications system (e.g., a Fifth Generation System (5GS)) exposes a set of capabilities to manage (e.g., add, delete, and/or modify) TSC subscriber data and/or TSC member group information. Related embodiments of a NEF, Application Function (AF), Network Function (NF), Policy and Control Function (PCF), Unified Data Management (UDM), Unified Data Repository (UDR), and methods of operation thereof are disclosed.

Description

DYNAMIC TSC SERVICE PROVISION

Related Applications

[0001] This application claims the benefit of PCT patent application serial number PCT/CN2020/091223, filed May 20, 2020, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

[0002] The present disclosure relates to operation of a cellular communications system (e.g., a Fifth Generation System (5GS)) as a virtual Time-Sensitive Networking (TSN) bridge.

Background

[0003] The fifth generation of mobile technology (5G) is positioned to provide much wider range of services than the existing third generation (3G) / fourth generation (4G) technologies. It is expected to enable a fully connected society, in which a rich set of Use Cases - some of them are still not yet conceptualized - will be supported from Enhanced Mobile Broadband (eMBB) through media distribution and Massive Machine Type Communication (M-MTC) to the Mission Critical Services (Critical Machine Type Communication - C-MTC).

[0004] The C-MTC Use Case group covers a large set of applications, but most of them can be characterized by low latency and high reliability. The Time-Sensitive Networking (TSN) Task Group of Institute of Electrical and Electronics Engineers (IEEE) 802.1 provides a standardized solution for satisfying low latency and high reliability requirements in fixed Ethernet networks. The Third Generation Partnership Project (3GPP) has defined an integration mechanism into TSN networks so that 3GPP networks can also act as virtual TSN bridges. With respect to the 5G system (5GS), these virtual TSN bridges are also referred to herein as 5GS bridges. In the model, Device Side TSN Translator (DS-TT) ports correspond to logical ports of the 5GS bridge on the device side, and Network side TSN Translator (NW-TT) ports correspond to logical ports of the 5GS bridge on the network side. The Integration of 3GPP networks into TSN is described further in 3GPP Technical Specification (TS) 23.501 V16.4.0, sections 4.4.8, 5.27, and 5.28. [0005] During the onboarding stage of the device side, the connection of the DS-TT with the 5GS is established via the Protocol Data Unit (PDU) Session Establishment procedure initiated by the corresponding User Equipment (UE). As described in 3GPP TS 23.502 V16.4.0 section 4.3.2.2, the UE initiates the UE Requested PDU Session Establishment procedure by the transmission of a Non-Access Stratum (NAS) message containing a PDU Session Establishment Request within the N1 Session Management (SM) container, which includes Single Network Slice Selection Assistance Information(s) (S-NSSAI(s)), UE Requested Data Network Name (DNN), PDU Session Identity (ID),

Port Management Information Container, etc.

[0006] Different TSN streams are mapped into Traffic Classes to meet different traffic characteristics. These Traffic Classes or streams are mapped to different Quality of Service (QoS) flows in the PDU session of the 5GS.

[0007] The TSN related configuration information (e.g., DNN, S-NSSAI, Quality of Service (QoS) profiles) are statically configured in UE and Unified Data Management (UDM), as specified in 3GPP TS 23.502 section 5.2.3.3.

Summary

[0008] Systems and methods are disclosed herein for dynamic Time Sensitive Communication (TSC) service management for a TSC service for a cellular communications system. In one embodiment, a method for dynamic TSC service management of a TSC service for a cellular communications system comprises, at a network function (NF), sending a subscribe request to a Unified Data Management (UDM) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises, at the UDM, receiving the subscribe request from the NF for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises, at a Policy and Control Function (PCF), sending a subscribe request to a User Data Repository (UDR) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises, at the UDR, receiving the subscribe request from the PCF for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises, at an Application Function (AF), sending, to a Network Exposure Function (NEF), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The method further comprises, at the NEF, receiving, from the AF, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters and sending, to the UDM, a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters. The method further comprises, at the UDM, receiving, from the NEF, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters; creating, updating, or deleting, at the UDR, the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device; and notifying the NF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters. The method further comprises, at the UDR, notifying the PCF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0009] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) a data network name (DNN), (b) a Single Network Slice Selection Assistance Information (S-NSSAI), (c) a Protocol Data Unit (PDU) session type, (d) information related with secondary authentication or authorization, (e) a subscribed Quality of Service (QoS) profile, (f) one or more Virtual Local Area Network (VLAN) Identities (IDs), (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0010] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by Generic Public Subscription Identifier (GPSI)), or (c) both (a) and (b). [0011] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the AF to the NEF is an Nnef_ParameterProvision service request. In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the NEF to the UDM is an Nudm_ParameterProvision service request.

[0012] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the AF to the NEF is an Nnef_TSC_ServiceProvision request. In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the NEF to the UDM is an Nudm_TSC_ServiceProvision request.

[0013] Embodiments of a method performed by a NEF in relation to dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a method performed by a NEF in relation to dynamic TSC service management of a TSC service for a cellular communications system comprises receiving, from an AF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The method further comprises sending, to a UDM, a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters and receiving a response from the UDM.

[0014] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) DNN, (b) a S-NSSAI, (c) a PDU session type, (d) information related with secondary authentication or authorization, (e) a subscribed QoS profile, (f) one or more VLAN IDs, (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0015] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by GPSI), or (c) both (a) and (b).

[0016] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the AF is an Nnef_ParameterProvision service request. In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the UDM is an Nudm_ParameterProvision service request.

[0017] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the AF is an Nnef_TSC_ServiceProvision request. In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the UDM is an Nudm_TSC_ServiceProvision request.

[0018] Corresponding embodiments of a NEF for dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a NEF for dynamic TSC service management of a TSC service for a cellular communications system is adapted to receive, from an AF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The NEF is further adapted to send, to a UDM, a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters and receive a response from the UDM.

[0019] In one embodiment, a network node for implementing a NEF for dynamic TSC service management of a TSC service for a cellular communications system comprises processing circuitry configured to cause the network node to receive, from an AF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The processing circuitry is further configured to cause the network node to send, to a UDM, a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters and receive a response from the UDM.

[0020] Embodiments of a method performed by a NF related to dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a method performed by a NF related to dynamic TSC service management of a TSC service for a cellular communications system comprises sending a subscribe request to a UDM for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises receiving, from the UDM, a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

[0021] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) DNN, (b) a S-NSSAI, (c) a PDU session type, (d) information related with secondary authentication or authorization, (e) a subscribed QoS profile, (f) one or more VLAN IDs, (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0022] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by GPSI), or (c) both (a) and (b).

[0023] Corresponding embodiments of a NF for dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a NF related to dynamic TSC service management of a TSC service for a cellular communications system is adapted to send a subscribe request to a UDM for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The NF is further adapted to receive, from the UDM, a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

[0024] In one embodiment, a network node for implementing a NF for dynamic TSC service management of a TSC service for a cellular communications system comprises processing circuitry configured to cause the network node to send a subscribe request to a UDM for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The processing circuitry is further configured to cause the network node to receive, from the UDM, a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters. [0025] Embodiments of a method performed by a UDM related to dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a method performed by a UDM related to dynamic TSC service management of a TSC service for a cellular communications system comprises receiving, from a NF, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises receiving, from an NEF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The method further comprises, responsive to receiving the request from the NEF, creating, updating, or deleting, at a UDR, the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112). The method further comprises notifying the NF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0026] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) DNN, (b) a S-NSSAI, (c) a PDU session type, (d) information related with secondary authentication or authorization, (e) a subscribed QoS profile, (f) one or more VLAN IDs, (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0027] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by GPSI), or (c) both (a) and (b).

[0028] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the NEF is an Nudm_ParameterProvision service request.

[0029] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the NEF is an Nudm_TSC_ServiceProvision request. [0030] Corresponding embodiments of a UDM for TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a UDM for TSC service management of a TSC service for a cellular communications system is adapted to receive, from a NF, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The UDM is further adapted to receive, from a NEF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The UDM is further adapted to, responsive to receiving the request from the NEF, create, update, or delete, at a UDR, the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device. The UDM is further adapted to notify the NF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0031] In one embodiment, a network node for implementing a UDM for TSC service management of a TSC service for a cellular communications system comprises processing circuitry configured to cause the network node to receive, from a NF, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The processing circuitry is further configured to cause the network node to receive, from a NEF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The processing circuitry is further configured to cause the network node to, responsive to receiving the request from the NEF, create, update, or delete, at a UDR, the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device. The processing circuitry is further configured to cause the network node to notify the NF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0032] Embodiments of a method performed by a PCF in relation to dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a method performed by a PCF in relation to dynamic TSC service management of a TSC service for a cellular communications system comprises sending a subscribe request to a UDR for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises receiving, from the UDR, a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

[0033] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) DNN, (b) a S-NSSAI, (c) a PDU session type, (d) information related with secondary authentication or authorization, (e) a subscribed QoS profile, (f) one or more VLAN IDs, (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0034] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by GPSI), or (c) both (a) and (b).

[0035] Corresponding embodiments of a PCF for dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a PCF for dynamic TSC service management of a TSC service for a cellular communications system is adapted to send, to a UDR, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The PCF is further adapted to receive, from the UDR, a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

[0036] In one embodiment, a network node for implementing a PCF for dynamic TSC service management of a TSC service for a cellular communications system comprises processing circuitry configured to cause the network node to send, to a UDR, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The processing circuitry is further configured to cause the network node to receive, from the UDR, a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

[0037] Embodiments of a method performed by a UDR in relation to dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a method performed by a UDR in relation to dynamic TSC service management of a TSC service for a cellular communications system comprises receiving, from a PCF, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The method further comprises communicating, with a UDM, to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device. The method further comprises notifying the PCF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0038] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) DNN, (b) a S-NSSAI, (c) a PDU session type, (d) information related with secondary authentication or authorization, (e) a subscribed QoS profile, (f) one or more VLAN IDs, (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0039] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by GPSI), or (c) both (a) and (b).

[0040] Corresponding embodiments of a UDR for dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, a UDR for dynamic TSC service management of a TSC service for a cellular communications system is adapted to receive, from a PCF, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The UDR is further adapted to communicate, with a UDM, to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device. The UDR is further adapted to notify the PCF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0041] In one embodiment, a network node for implementing a UDR for dynamic TSC service management of a TSC service for a cellular communications system comprises processing circuitry configured to cause the network node to receive, from a PCF, a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification. The processing circuitry is further configured to cause the network node to communicate, with a UDM, to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device. The processing circuitry is further configured to cause the network node to notify the PCF of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

[0042] Embodiments of a method performed by an AF for dynamic TSC service management of a TSC service for a cellular communications system are also disclosed.

In one embodiment, a method performed by an AF for dynamic TSC service management of a TSC service for a cellular communications system comprises sending, to a NEF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The method further comprises receiving a response from the NEF.

[0043] In one embodiment, the one or more TSC group subscription data parameters comprise: (a) DNN, (b) a S-NSSAI, (c) a PDU session type, (d) information related with secondary authentication or authorization, (e) a subscribed QoS profile, (f) one or more VLAN IDs, (g) one or more time synchronization parameters, (h) device information, or (i) a combination of any two or more of (a) - (h).

[0044] In one embodiment, the one or more TSC member group information parameters comprise: (a) one or more TSC member group identifiers, (b) membership (e.g., identified by GPSI), or (c) both (a) and (b).

[0045] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the NEF is an Nnef_ParameterProvision service request.

[0046] In one embodiment, the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the NEF is an Nnef_TSC_ServiceProvision request. [0047] Corresponding embodiments of an AF for dynamic TSC service management of a TSC service for a cellular communications system are also disclosed. In one embodiment, an AF is adapted to send, to a NEF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The AF is further adapted to receive a response from the NEF.

[0048] In one embodiment, a network node for implementing an AF for dynamic TSC service management of a TSC service for a cellular communications system comprises processing circuitry configured to cause the network node to send, to a NEF, a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters. The processing circuitry is further configured to cause the network node to receive a response from the NEF.

Brief Description of the Drawings

[0049] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0050] Figure 1 illustrates one example of a cellular communications system according to some embodiments of the present disclosure;

[0051] Figures 2 and 3 illustrate example embodiments of the cellular commutations system of Figure 1 in which the cellular communications system is a 5GS;

[0052] Figure 4 illustrates one example embodiment of a 5GS virtual TSN bridge in which embodiments of the present disclosure may be implemented;

[0053] Figure 5 illustrates a Time Sensitive Communication (TSC) service provision procedure in accordance with one embodiment of the present disclosure;

[0054] Figure 6 illustrates a TSC service provision procedure in accordance with another embodiment of the present disclosure; [0055] Figure 7 is a schematic block diagram of a network node according to some embodiments of the present disclosure;

[0056] Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node of Figure 7 according to some embodiments of the present disclosure; and

[0057] Figure 9 is a schematic block diagram of the network node of Figure 7 according to some other embodiments of the present disclosure.

Detailed Description

[0058] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0059] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless communication device.

[0060] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node.

[0061] Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Flome Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing an Access and Mobility Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

[0062] Communication Device: As used herein, a "communication device" is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle- mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection.

[0063] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection.

[0064] Network Node: As used herein, a "network node" is any node that is either part of the RAN or the core network of a cellular communications network/system. [0065] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0066] Note that, in the description herein, reference may be made to the term "cell"; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0067] There currently exist certain challenge(s). In the 5GS, a Time Sensitive Communication (TSC) service, with Time Sensitive Networking (TSN) or without TSN, is usually dynamically configured by an Application Function (AF) for the supported Traffic Classes, Virtual Local Area Networks (VLANs), etc. For a 5GS virtual TSN bridge, the serving Data Network Name (DNN), Serving Network Slice Assistance Information (S- NSSAI), Protocol Data Unit (PDU) session type, Quality of Service (QoS) profiles, and time synchronization parameters are subject to change according to the TSN requirements and 5G system optimization.

[0068] The current TSC subscriber information (e.g., DNN, S-NSSAI, PDU session type, QoS profiles) in 5GS are statically configured in the UE and UDM, which cannot fulfill the requirement of quick deployment of a new TSC service (with or without TSN) and real time update of a TSC service. A mechanism is needed to expose the management capability of a TSC service (with or without TSN) and support the TSC service provisioning from an external AF.

[0069] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. In one embodiment, in order to support dynamic management of a TSC service(s), a Network Exposure Function (NEF) in the 5GS exposes a set of capabilities to manage (e.g., add, delete, and/or modify) TSC subscriber data (also referred to herein as, e.g., TSC group subscription data) and/or a TSC member group (also referred to herein as TSC member group information).

[0070] TSC subscriber data (e.g., serving S-NSSAI, connected DNN, PDU session type, Virtual Local Area Network (VLAN) Identity(ies) (ID(s)), QoS requirement(s), and/or time synchronization parameter(s)) and UE membership information (e.g., TSC member group identifiers and/or membership identified by Generic Public Subscription Identifier (GPSI)) is provided by an AF. A UDM updates the corresponding UE's subscription data in a User Data Repository (UDR). The UDR and/or UDM notifies the updated TSC subscriber data to one or more NFs (e.g., PCF, SMF, and/or AMF) and/or the UE(s).

[0071] Two alternative procedures are disclosed herein:

• Alternative 1: Reuse an existing service operation(s), (e.g., Nnef_ParameterProvision, Nudm_ParameterProvision), but carrying the newly defined TSC subscriber data.

• Alternative 2: Define a new service operation(s) (e.g., Nnef_TSC_ServiceProvision, Nudm_TSC_ Nudm_ServiceProvision) to carry the newly defined TSC subscriber data.

[0072] In one embodiment, a NEF exposes a set of services to an AF to manage (e.g., add, delete, and/or modify) TSC member groups information and TSC group subscription data. Upon receiving a creation (i.e., add) or updating (i.e., modify) TSC service request from the AF, the NEF provides TSC subscriber data, TSN membership information, and/or subscriber data of TSN members to a UDM. The UDM stores or updates the TSC member groups information and TSC group subscription in a UDR. The UDM creates, updates, or deletes the provisioned TSC subscriber data as part of the UE subscriber data of the TSN members. The updating of subscriber data is notified to one or more NFs (e.g., PCF, SMF, and/or AMF, etc.) and/or the UE(s).

[0073] Certain embodiments may provide one or more of the following technical advantage(s). For example, embodiments disclosed herein expose the management capability of a TSC service to an AF (e.g., an AF that is external to the 5GS). Embodiments disclosed herein enable quick provision of a TSC service. Embodiments disclosed herein support dynamic management of a TSC service from an authorized AF. [0074] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G System (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs) (i.e., LTE RAN nodes connected to the 5GC), , controlling corresponding (macro) cells 104-1 and 104- 2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 104- 1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108. The cellular communications system 100 also includes a core network 110, which in the 5GS is referred to as the 5G Core (5GC). The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110.

[0075] The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs and as such sometimes referred to herein as UEs 112, but the present disclosure is not limited thereto.

[0076] Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point-to-point reference point/interface.

Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1. [0077] Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 2 include a NSSF 202, an AUSF 204, a UDM 206, the AMF 200, a SMF 208, a PCF 210, and an Application Function (AF) 212.

[0078] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 200. The reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively. There is a reference point, Nil, between the AMF 200 and SMF 208, which implies that the SMF 208 is at least partly controlled by the AMF 200. N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208. N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 210 applies policy to the AMF 200 and SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208.

[0079] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 2, the UPF 214 is in the UP and all other NFs, i.e., the AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204, and UDM 206, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency.

[0080] The core 5G network architecture is composed of modularized functions. For example, the AMF 200 and SMF 208 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling. Other CP functions like the PCF 210 and AUSF 204 can be separated as shown in Figure 2. Modularized function design enables the 5GC network to support various services flexibly.

[0081] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs.

[0082] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2. Flowever, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter "N" followed by the name of the NF, e.g. Namf for the service based interface of the AMF 200 and Nsmf for the service based interface of the SMF 208, etc. The NEF 300 and the NRF 302 in Figure 3 are not shown in Figure 2 discussed above. Flowever, it should be clarified that all NFs depicted in Figure 2 can interact with the NEF 300 and the NRF 302 of Figure 3 as necessary, though not explicitly indicated in Figure 2.

[0083] Some properties of the NFs shown in Figures 2 and 3 may be described in the following manner. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 200 because the AMF 200 is independent of the access technologies. The SMF 208 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 214 for data transfer. If a UE 112 has multiple sessions, different SMFs 208 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 212 provides information on the packet flow to the PCF 210 responsible for policy control in order to support QoS. Based on the information, the PCF 210 determines policies about mobility and session management to make the AMF 200 and SMF 208 operate properly. The AUSF 204 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 206 stores subscription data of the UE 112. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar.

[0084] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure.

[0085] Figure 4 is an example illustration of the 5GS implementing a number of TSN bridges in accordance with embodiments of the present disclosure. In this example, as illustrated, the 5GS implements a first virtual TSN bridge 400-A (denoted in Figure 4 as "Bridge A") including a first UPF 214-A (denoted in Figure 4 as "UPF-A"), and a second virtual TSN bridge 400-B (denoted in Figure 4 as "Bridge B") including a second UPF 214-B (denoted in Figure 4 as "UPF-B"). As illustrated, a first port of a first TSN bridge or TSN end station 402-A is connected to a DS-TT 404 associated with a first UE 112-A (denoted in Figure 4 as "UE1"). The DS-side TT 404 together with the first UE 112-A, the first UPF 614-A, and a NW-TT 406 implement the first virtual TSN bridge 400-A. All PDU sessions for the particular TSN system shown (including a first PDU session from the first UE 112-A to the first UPF 614-A, which is denoted "PDU Session 1A") which connect to the first UPF 614-A are grouped into the first virtual TSN bridge 400-A. As illustrated, in this example, a second port of the first TSN bridge or end station 402-A is connected to a DS-TT 408 associated with the first UE 112-A. In addition, a port of a second TSN bridge or end station 402-B is connected to a DS-TT 410 associated with a second UE 112-B (denoted in Figure 4 as "UE2). The DS-side TTs 408 and 410 together with the UEs 112-A and 112-B, the second UPF 214-B, and a NW-TT 412 implement the second virtual TSN bridge 400-B. All PDU sessions for the particular TSN system shown (including a second PDU session from the first UE 112-A to the first UPF 214-A, which is denoted "PDU Session IB", and a PDU session from the second UE 112-B to the second UPF 214-B, which is denoted "PDU Session 2B") which connect to the second UPF 214-B are grouped into the second virtual TSN bridge 400-B.

[0086] In accordance with embodiments of the present disclosure, the 5GS supports dynamic management of a TSC service. In one embodiment, this dynamic management of a TSC service includes management of TSC group subscription data (e.g., serving S- NSSAI, connected DNN, PDU session type, VLAN ID(s), QoS requirement s), and/or time synchronization capabilities) and/or UE membership information (e.g., TSC member group identifiers and/or membership identified by, e.g., GPSI). Note that the UE membership information is also referred to herein as TSC member groups information. The TSC service management (e.g., add, delete, and/or modify) can be configured by a network administrator or can be managed dynamically by an AF.

[0087] The NEF 300 exposes a set of services to a TSC AF (e.g., AF 212 may be a TSC AF) to manage (e.g., add, delete, and/or modify) TSC groups subscription data and/or TSC member groups. In one embodiment, a procedure(s) is similar to the 5G Virtual Network (VN) group management depicted in 3GPP TS 23.501 clause 5.29.2 is used for TSC group subscription data and/or TSC member groups management.

[0088] Parameters specified in TS 23.502 V16.4.0 clause 4.15.6.3c can be reused for the management of TSC member group.

[0089] In one example embodiment, the TSC group subscription data includes:

• DNN (e.g., as specified in TS 23.502 clause 4.15.6.3b),

• S-NSSAI (e.g., as specified in TS 23.502 clause 4.15.6.3b), • PDU Session Type (e.g., as specified in TS 23.502 clause 4.15.6.3b ),

• information related with secondary authentication / authorization (e.g., as specified in TS 23.502 clause 4.15.6.3b ),

• subscribed QoS profile (e.g., as specified in TS 23.502 clause 5.2.3.3.1),

• QoS requirements or/and QoS characteristics of non-3GPP devices that are connected to a UE subscriber (e.g., a number of end-stations or applications are connected to a UE), the information may be used by 5G system, or alternatively used by non-3GPP entities (expose such information to AF for non-3GPP entities, e.g. CUC)

• VLAN ID(s),

• time synchronization parameters (e.g., synchronicity (synchronization accuracy) requirement, clock accuracy related parameters (e.g., rateRatio), supported clock domains (e.g., list of domainNumbers that subscriber is using), tick-granularity if the UE or DS-TT has 802,lQbv/Qci gating functions, indication of synchronization directions or use-cases, e.g. o Casel: UE(DS-TT) to UE(DS-TT) synchronization. (GM at one UE, sync devices at the other UEs), o Case2: UE(DS-TT) to UPF(NW-TT) synchronization. (GM at UE side, sync devices at UPF side), or o Case3: UPF(NW-TT) to UE(DS-TT) synchronization. (GM at UPF side, sync devices at UE side), and/or

• device information (e.g., any devices that are associated with the subscriber, e.g., DS-TT). The device information may include, e.g., o number of connected devices, o device ID, and/or o device type.

[0090] In order to support dynamic management of a TSC service, the NEF 300 exposes a set of services to an AF to manage (e.g., add, delete, and/or modify) TSC member groups information and TSC group subscription data.

[0091] When configuration is provided by an AF, the procedures described in 3GPP TS 23.502 section 4.15.6.2 apply for storing the TSC member groups information and TSC group subscription data in the UDR, as follows: • The NEF 300 provides the TSC member groups information and TSC group subscription data to the UDM 206. The UDM 206 stores or updates the TSC member groups information and TSC group subscription data in the UDR.

[0092] If a UE 112 is member of a TSC member group, the UDM 206 retrieves UE subscription data for the UE 112 and corresponding TSC group subscription data from the UDR, and provides the AMF 200 and SMF 208 with the UE subscription data with the TSC group subscription data included.

[0093] The PCF 210 retrieves the TSC group subscription data from the UDR. The PCF(s) 210 that have subscribed to modifications of TSC group subscription data receive(s) a Nudr_DM_Notify notification of data change from the UDR, which is used for UE Route Selection Policy (URSP) generation for the UE 112 that belongs to the same TSC group.

[0094] An AF may update the TSC member groups information and TSC group subscription data at any time after the initial provisioning of the TSC service.

[0095] TSC service provision procedure, alternative 1:

[0096] The TSC service provision is invoked by the AF using the Nnef_ParameterProvision Service as described in 3GPP TS 23.502 clause 4.15.6.2. [0097] More specifically, alternative 1 of the TSC service provision procedure is illustrated in Figure 5. The steps of the TSC service provision procedure for alternative 1 are as follows:

• Step 506: An NF 500, which is in this example either an AMF 200 or an SMF 208, subscribes to UDM notifications of TSC member groups information and TSC group subscription data modification. In other words, the NF 500 sends a subscribe request to the UDM 206 for notifications of TSC member groups information and TSC group subscription data modification.

• Step 508: PCF 210 subscribes to UDR notification of TSC member groups information and TSC group subscription data modification. In other words, the PCF 210 sends a subscribe request to UDR 502 for notifications of TSC member groups information and TSC group subscription data modification.

• Step 510: An AF 504 provides one or more TSC member groups information and TSC group parameter(s) to be created or updated. More specifically, the AF 504 sends a parameter provision create/update/delete (i.e., create, update, or delete) request to the NEF 300, where this request includes one or more TSC member groups information and TSC group parameter(s) to be created or updated. The AF 504 is also referred to herein as a TSC AF. Further, the AF 504 may be external to the 5GC.

• Step 512: If the AF 504 is authorized by the NEF 300 to provision the parameters, the NEF 300 requests to create, update and store, or delete the provisioned parameters as part of the subscriber data. More specifically, the NEF 300 sends a parameter provision create/update/delete request to the UDM 206, where this request includes the parameters to be created or updated.

Additionally or alternatively, if a parameter(s) is(are) to be deleted, the request may include information that indicates the parameter(s) to be deleted.

• Step 514: (Optional) The UDM 206 may read from the UDR 502 corresponding subscription information in order to validate required data updates and authorize these changes for this subscriber or member group for the corresponding AF 504. This validates if the updates are coming from valid/authorized TSC member group. The example of update can be, e.g. a new non-3GPP device connected/removed to/from the existing UE.

• Step 516: If the AF 504 is authorized by the UDM 206 to provision the parameters for the respective TSC group, the UDM 206 creates, updates, or deletes the provisioned TSC group parameter(s) as part of the TSC member groups information and TSC group subscription data.

• Step 518: The UDM 206 responds to the request of step 512.

• Step 520: The NEF 300 responds to the request of step 510.

• Step 522: The UDM 206 notifies the subscribed NF 500 (e.g., AMF 200 or SMF 208) of the updated TSC member groups information and TSC group subscription data.

• Step 524: The UDR 502 notifies the 210 PCF of the updated TSC member groups information and TSC group subscription data.

[0098] TSC service provision procedure, alternative 2:

[0099] The TSC service provision is invoked by AF the newly defined NEF service Nnef_TSC_ServiceProvision_Request/Response and UDM service Nudm_TSC_ServiceProvision Request/Response. [0100] More specifically, alternative 2 of the TSC service provision procedure is illustrated in Figure 6. The steps of the TSC service provision procedure for alternative 2 are as follows:

• Step 600: An NF 500, which is in this example either an AMF 200 or an SMF 208, subscribes to UDM notifications of TSC member groups information and TSC group subscription data modification. In other words, the NF 500 sends a subscribe request to the UDM 206 for notifications of TSC member groups information and TSC group subscription data modification.

• Step 602: PCF 210 subscribes to UDR notification of TSC member groups information and TSC group subscription data modification. In other words, the PCF 210 sends a subscribe request to UDR 502 for notifications of TSC member groups information and TSC group subscription data modification.

• Step 604: An AF 504 provides one or more TSC member groups information and TSC group parameter(s) to be created or updated. More specifically, the AF 504 sends a TSC service provision create/update/delete request to the NEF 300, where this request includes one or more TSC member groups information and TSC group parameter(s) to be created or updated. The AF 504 is also referred to herein as a TSC AF. Further, the AF 504 may be external to the 5GC. Note that the name "Nnef_TSC_ServiceProvision" request is used herein as a placeholder, other names may be given to this request, e.g., in the 3GPP specifications. Thus, the term "Nnef_TSC_ServiceProvision" or the like, as used herein, is intended encompass a request of any name that is a new type of request used to request creation, updating, or deletion of one or more TSC member groups information parameters and/or one or more TSC group parameters.

• Step 606: If the AF 504 is authorized by the NEF 300 to provision the parameters, the NEF 300 requests to create, update and store, or delete the provisioned parameters as part of the subscriber data. More specifically, the NEF 300 sends a TSC service provision create/update/delete request to the UDM 206, where this request includes the parameters to be created or updated.

Additionally or alternatively, if a parameter(s) is(are) to be deleted, the request may include information that indicates the parameter(s) to be deleted. • Step 608: (Optional) The UDM 206 may read from the UDR 502 corresponding subscription information in order to validate required data updates and authorize these changes for this subscriber or member group for the corresponding AF 504.

• Step 610: If the AF 504 is authorized by the UDM 206 to provision the parameters for the TSC group, the UDM 206 creates, updates, or deletes the provisioned TSC group parameters as part of the TSC member groups information and TSC group subscription data.

• Step 612: The UDM 206 responds to the request of step 606.

• Step 614: The NEF 300 responds to the request of step 604.

• Step 616: The UDM 206 notifies the subscribed NF 500 (e.g., AMF 200 or SMF 208) of the updated TSC member groups information and TSC group subscription data.

• Step 618: The UDR 504 notifies the PCF 200 of the updated TSC member groups information and TSC group subscription data.

[0101] Figure 7 is a schematic block diagram of a network node 700 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 700 may be, for example, a network node that implements the AF 504, the NEF 300, the UDM 206, the UDR 502, the NF 500, or the PCF 510, as described herein. As illustrated, the network node 700 includes one or more processors 704 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 706, and a network interface 708. The one or more processors 704 are also referred to herein as processing circuitry. The one or more processors 704 operate to provide one or more functions of the network node 700 as described herein (e.g., one or more functions of the AF 504, the NEF 300, the UDM 206, the UDR 502, the NF 500, or the PCF 510, as described herein, e.g., with respect to Figure 5 or 6). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 706 and executed by the one or more processors 704.

[0102] Figure 8 is a schematic block diagram that illustrates a virtualized embodiment of the network node 700 according to some embodiments of the present disclosure. As used herein, a "virtualized" network node is an implementation of the network node 700 in which at least a portion of the functionality of the network node 700 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 700 includes one or more processing nodes 800 coupled to or included as part of a network(s) 802. Each processing node 800 includes one or more processors 804 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 806, and a network interface 808.

[0103] In this example, functions 810 of the network node 700 described herein (e.g., one or more functions of the AF 504, the NEF 300, the UDM 206, the UDR 502, the NF 500, or the PCF 510, as described herein, e.g., with respect to Figure 5 or 6) are implemented at the one or more processing nodes 800 or distributed across the two or more processing nodes 800 in any desired manner. In some particular embodiments, some or all of the functions 810 of the network node 700 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 800.

[0104] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 700 or a node (e.g., a processing node 800) implementing one or more of the functions 810 of the network node 700 in a virtual environment according to any of the embodiments described herein (e.g., one or more functions of the AF 504, the NEF 300, the UDM 206, the UDR 502, the NF 500, or the PCF 510, as described herein, e.g., with respect to Figure 5 or 6) is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

[0105] Figure 9 is a schematic block diagram of the network node 700 according to some other embodiments of the present disclosure. The network node 700 includes one or more modules 900, each of which is implemented in software. The module(s) 900 provide the functionality of the network node 700 described herein (e.g., one or more functions of the AF 504, the NEF 300, the UDM 206, the UDR 502, the NF 500, or the PCF 510, as described herein, e.g., with respect to Figure 5 or 6). This discussion is equally applicable to the processing node 800 of Figure 8 where the modules 900 may be implemented at one of the processing nodes 800 or distributed across multiple processing nodes 800. [0106] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0107] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

[0108] At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

3GPP Third Generation Partnership Project

5G Fifth Generation

5GC Fifth Generation Core

5GS Fifth Generation System

AF Application Function

AMF Access and Mobility Function

AN Access Network

AP Access Point

ASIC Application Specific Integrated Circuit • AUSF Authentication Server Function

• CPU Central Processing Unit

• DN Data Network

• DSP Digital Signal Processor

• FPGA Field Programmable Gate Array

• gNB New Radio Base Station

• FISS Flome Subscriber Server

• MTC Machine Type Communication

• NEF Network Exposure Function

• NF Network Function

• NR New Radio

• NRF Network Function Repository Function

• NSSF Network Slice Selection Function

• PCF Policy Control Function

• RAM Random Access Memory

• RAN Radio Access Network

• ROM Read Only Memory

• SCEF Service Capability Exposure Function

• SMF Session Management Function

• UDM Unified Data Management

• UE User Equipment

• UPF User Plane Function

[0109] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

What is claimed is:

1. A method for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising:

• at a network function, NF, (500): o sending (506; 600) a subscribe request to a Unified Data Management, UDM, (206) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification;

• at the UDM (206): o receiving (506; 600) the subscribe request from the NF (500) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification;

• at a Policy and Control Function, PCF, (210): o sending (508; 602) a subscribe request to a User Data Repository, UDR, (502) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification;

• at the UDR (502): o receiving (508; 602) the subscribe request from the PCF (210) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification;

• at an Application Function, AF, (504): o sending (510; 604), to a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters;

• at the NEF (300): o receiving (510; 604), from the AF (504), the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters; o sending (512; 606), to the UDM (206), a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters;

• at the UDM (206): o receiving (512; 606), from the NEF (300), the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters; o creating, updating, or deleting (516; 610), at the UDR (502), the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and o notifying (522; 616) the NF (500) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters; and

• at the UDR (502): o notifying (524; 618) the PCF (210) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

2. The method of claim 1 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identities, IDs; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

3. The method of claim 1 or 2 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

4. The method of any one of claims 1 to 3 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the AF (504) to the NEF (300) is an Nnef_ParameterProvision service request.

5. The method of claim 4 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the NEF (300) to the UDM (206) is an Nudm_ParameterProvision service request.

6. The method of any one of claims 1 to 3 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the AF (504) to the NEF (300) is an Nnef_TSC_ServiceProvision request.

7. The method of claim 6 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent from the NEF (300) to the UDM (206) is an Nudm_TSC_ServiceProvision request.

8. A method performed by a Network Exposure Function, NEF, (300) in relation to dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising: receiving (510; 604), from an Application Function, AF, (504), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; sending (512; 606), to a Unified Data Management, UDM, (206), a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters; and receiving (518; 612) a response from the UDM (206).

9. The method of claim 8 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identity, ID; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

10. The method of claim 8 or 9 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

11. The method of any one of claims 8 to 10 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the AF (504) is an Nnef_ParameterProvision service request.

12. The method of claim 11 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the UDM (206) is an Nudm_ParameterProvision service request.

13. The method of any one of claims 8 to 10 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the AF (504) is an Nnef_TSC_ServiceProvision request.

14. The method of claim 13 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the UDM (206) is an Nudm_TSC_ServiceProvision request.

15. A Network Exposure Function, NEF, (300) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the NEF (300) adapted to: receive (510; 604), from an Application Function, AF, (504), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; send (512; 606), to a Unified Data Management, UDM, (206), a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters; and receive (518; 612) a response from the UDM (206).

16. The NEF (300) of claim 15 wherein the NEF (300) is further adapted to perform the method of any of claims 9 to 14.

17. A network node (700) for implementing a Network Exposure Function, NEF,

(300) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: receive (510; 604), from an Application Function, AF, (504), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; send (512; 606), to a Unified Data Management, UDM, (206), a request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters; and receive (518; 612) a response from the UDM (206).

18. The network node (700) of claim 17 wherein the processing circuitry (704; 804) is further configured to cause the network node (700) to perform the method of any of claims 9 to 14.

19. A method performed by a Network Function, NF, (500) related to dynamic Time- Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising: sending (506; 600) a subscribe request to a Unified Data Management, UDM, (206) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; and receiving (522; 616), from the UDM (206), a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

20. The method of claim 19 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identity, ID; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

21. The method of claim 19 or 20 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

22. A Network Function, NF, (500) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the NF (500) adapted to: send (506; 600) a subscribe request to a Unified Data Management, UDM, (206) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; and receive (522; 616), from the UDM (206), a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

23. The NF (500) of claim 22 wherein the NF (500) is further adapted to perform the method of claim 20 or 21.

24. A network node (700) for implementing a Network Function, NF, (500) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: send (506; 600) a subscribe request to a Unified Data Management, UDM, (206) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; and receive (522; 616), from the UDM (206), a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

25. The network node (700) of claim 24 wherein the processing circuitry (704; 804) is further configured to cause the network node (700) to perform the method of claim 20 or 21.

26. A method performed by a Unified Data Management, UDM, (206) related to dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising: receiving (506; 600), from a Network Function, NF, (500), a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; receiving (512; 606), from a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; responsive to receiving (512; 606) the request, creating, updating, or deleting (516; 610), at a User Data Repository, UDR, (502), the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and notifying (522; 616) the NF (500) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

27. The method of claim 26 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identity, ID; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

28. The method of claim 26 or 27 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

29. The method of any one of claims 26 to 28 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the NEF (300) is an Nudm_ParameterProvision service request.

30. The method of any one of claims 26 to 28 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters received from the NEF (300) is an Nudm_TSC_ServiceProvision request.

31. A Unified Data Management, UDM, (206) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the UDM (206) adapted to: receive (506; 600), from a Network Function, NF, (500), a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; receive (512; 606), from a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; responsive to receiving (512; 606) the request, create, update, or delete (516; 610), at a User Data Repository, UDR, (502), the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and notify (522; 616) the NF (500) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

32. The UDM (206) of claim 31 wherein the UDM (206) is further adapted to perform the method of any of claims 27 to 30.

33. A network node (700) for implementing a Unified Data Management, UDM, (206) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: receive (506; 600), from a Network Function, NF, (500), a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; receive (512; 606), from a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; responsive to receiving (512; 606) the request, create, update, or delete (516; 610), at a User Data Repository, UDR, (502), the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and notify (522; 616) the NF (500) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

34. The network node (700) of claim 33 wherein the processing circuitry (704; 804) is further configured to cause the network node (700) to perform the method of claims 27 to 30.

35. A method performed by a Policy and Control Function, PCF, (210) in relation to dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising: sending (508; 602) a subscribe request to a User Data Repository, UDR, (502) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; and receiving (524; 618), from the UDR (502), a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

36. The method of claim 35 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identity, ID; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

37. The method of claim 35 or 36 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

38. A Policy and Control Function, PCF, (210) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the PCF (210) adapted to: send (508; 602) a subscribe request to a User Data Repository, UDR, (502) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; and receive (524; 618), from the UDR (502), a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

39. The PCF (210) of claim 38 wherein the PCF (210) is further adapted to perform the method of claim 36 or 37.

40. A network node (700) for implementing a Policy and Control Function, PCF, (210) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: send (508; 602) a subscribe request to a User Data Repository, UDR, (502) for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; and receive (524; 618), from the UDR (502), a notification of one or more created, updated, or deleted TSC member group information parameters and/or one or more created, updated, or deleted TSC group subscription data parameters.

41. The network node (700) of claim 40 wherein the processing circuitry (704; 804) is further configured to cause the network node (700) to perform the method of claim 36 or 37.

42. A method performed by a User Data Repository, UDR, (502) in relation to dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising: receiving (508; 602), from a Policy and Control Function, PCF, (210), a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; communicating (516; 610), with a Unified Data Management, UDM, (206), to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and notifying (524; 618) the PCF (210) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

43. The method of claim 42 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identity, ID; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

44. The method of claim 42 or 43 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

45. A User Data Repository, UDR, (502) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the UDR (502) adapted to: receive (508; 602), from a Policy and Control Function, PCF, (210), a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; communicate (516; 610), with a Unified Data Management, UDM, (206), to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and notify (524; 618) the PCF (210) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

46. The UDR (502) of claim 45 wherein the UDR (502) is further adapted to perform the method of claim 43 or 44.

47. A network node (700) for implementing a User Data Repository, UDR, (502) for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: receive (508; 602), from a Policy and Control Function, PCF, (210), a subscribe request for notifications of TSC member groups information, TSC group subscription data modification, or both TSC member groups information and TSC group subscription data modification; communicate (516; 610), with a Unified Data Management, UDM, (206), to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters stored in subscription data of a corresponding wireless communication device (112); and notify (524; 618) the PCF (210) of the one or more created, updated, or deleted TSC member group information parameters and/or the one or more created, updated, or deleted TSC group subscription data parameters.

48. The network node (700) of claim 47 wherein the processing circuitry (704; 804) is further configured to cause the network node (700) to perform the method of claim 43 or 44.

49. A method performed by an Application Function, AF, for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the method comprising: sending (510; 604), to a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; and receiving (520) a response from the NEF (300).

50. The method of claim 49 wherein the one or more TSC group subscription data parameters comprise: a. a data network name, DNN; b. a Single Network Slice Selection Assistance Information, S-NSSAI; c. a Protocol Data Unit, PDU, session type; d. information related with secondary authentication or authorization; e. a subscribed Quality of Service, QoS, profile; f. one or more Virtual Local Area Network, VLAN, Identity, ID; g. one or more time synchronization parameters; h. device information; or i. a combination of any two or more of (a) - (h).

51. The method of claim 49 or 50 wherein the one or more TSC member group information parameters comprise: a. one or more TSC member group identifiers; b. membership (e.g., identified by GPSI); or c. both (a) and (b).

52. The method of any one of claims 49 to 51 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the NEF (300) is an Nnef_ParameterProvision service request.

53. The method of any one of claims 49 to 51 wherein the request to create, update, or delete the one or more TSC member group information parameters and/or the one or more TSC group subscription data parameters sent to the NEF (300) is an Nnef_TSC_ServiceProvision request.

54. An Application Function, AF, for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the AF adapted to: send (510; 604), to a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; and receive (520) a response from the NEF (300).

55. The AF of claim 54 wherein the AF is further adapted to perform the method of any of claims 50 to 53.

56. A network node (700) for implementing an Application Function, AF, for dynamic Time-Sensitive Communication, TSC, service management of a TSC service for a cellular communications system (100), the network node (700) comprising processing circuitry (704; 804) configured to cause the network node (700) to: send (510; 604), to a Network Exposure Function, NEF, (300), a request to create, update, or delete one or more TSC member group information parameters and/or one or more TSC group subscription data parameters; and receive (520) a response from the NEF (300).

57. The network node (700) of claim 56 wherein the processing circuitry (704; 804) is further configured to cause the network node (700) to perform the method of any of claims 50 to 53.