CN116671252A

CN116671252A - Traffic class handling

Info

Publication number: CN116671252A
Application number: CN202080104722.5A
Authority: CN
Inventors: 李振东
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2020-07-29
Filing date: 2020-07-29
Publication date: 2023-08-29
Also published as: WO2022021109A1

Abstract

The present invention relates to methods, systems, and devices related to digital wireless communications, and more particularly to techniques related to traffic class processing. In one exemplary aspect, a method of data communication is described. The method includes a first network function receiving a data configuration from a network node. The method also includes the first network function obtaining traffic class information based on the data configuration. The method also includes the first network function transmitting traffic class information to the second network function.

Description

Traffic class handling

Technical Field

The present invention relates generally to wireless communications.

Background

Mobile communication technology has pushed the world to an increasingly social and networked society. The rapid growth and technological advances in mobile communication technology have led to greater demands for capacity and connectivity. Other things, such as energy consumption, equipment cost, spectral efficiency, and latency are also important to meet the needs of various communication schemes. Various techniques are being discussed, including new ways of providing higher quality of service.

Disclosure of Invention

Methods, systems, and devices related to digital wireless communications, and more particularly, techniques related to traffic class processing, are disclosed.

In one exemplary aspect, a method for data communication is disclosed. The method includes receiving, by a first network function, a data configuration from a network node. The method also includes obtaining, by the first network function, traffic class information based on the data configuration. The method also includes transmitting, by the first network function, traffic class information to the second network function.

In another exemplary embodiment, a method for data communication is disclosed. The method comprises receiving, by the second network function, a first message from the first network function, the first message comprising traffic class information, wherein the first network function is configured to obtain the traffic class information based on configuration data received from the network node.

In another exemplary aspect, a wireless communication apparatus including a processor is disclosed. The processor is configured to implement the methods described herein.

In yet another exemplary aspect, various techniques described herein may be embodied as processor executable code and stored on a computer readable program medium.

The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the clauses.

Drawings

Fig. 1 is a block diagram of an example virtual TSN bridge.

Fig. 2 is a block diagram of an example full centralized mode TSN network model.

Fig. 3 is a block diagram of an example bridge ingress port and egress port. Ingress and egress ports of a bridge are logical concepts associated with each flow.

Fig. 4 is a block diagram of an example frame process in a bridge.

Figure 5 is a block diagram of an example 5GS supported TSN as a virtual TSN bridge.

Fig. 6 is a signaling procedure of an example procedure in which the TSN AF provides traffic categories to the UPF/NW-TT.

Fig. 7 is a signaling procedure of an example procedure in which the TSN AF provides traffic class to the UE/DS-TT.

Fig. 8 is a signaling procedure of an example procedure in which TSN AF provides traffic classes to SMF and UPF.

Fig. 9 is an example signaling procedure for TSN AF to provide traffic classes to SMF and UE.

FIG. 10 is a block diagram of an example method for traffic class processing.

Fig. 11 illustrates an example of a wireless communication system in which one or more embodiments in accordance with the present technology may be employed.

FIG. 12 is a block diagram representing a portion of a hardware platform.

Detailed Description

The development of new generation wireless communication 5G new wireless (NR) communication is part of the evolving mobile broadband evolution process to meet the increasing network demands. NR will provide a greater throughput to allow more users to connect simultaneously. Other things, such as energy consumption, equipment cost, spectral efficiency, and latency are also important to meet the needs of various communication schemes.

As throughput increases in 5G networks, more data traffic may be transmitted over the 5G network to execute various resource intensive applications (e.g., video game streams). Data traffic transmitted over such networks may be included in any of a number of traffic classes. The 5G network may transmit data according to traffic class to improve data communication efficiency and quality (e.g., improve quality of service (QoS)).

In many cases, 5G systems may support IEEE Time Sensitive Network (TSN) traffic. The 5GS may be enhanced as a TSN virtual bridge, i.e. from the perspective of the TSN network, the 5GS may appear as a TSN bridge entity.

Fig. 1 is a block diagram 100 of an example virtual TSN bridge. For a particular TSN network, a virtual TSN bridge may be per UPF granularity. This may mean that all PDU sessions targeting the TSN network consist of one virtual TSN bridge under the same UPF.

The CNC may configure the gating of each traffic class at the egress port of the bridge. For each traffic class, there may be one or more flows within one traffic class. There may be 8 traffic classes per port per bridge. There may be a queue in the egress port for a traffic class.

But within the 5GS virtual bridge the granularity may be Qos flows per PDU session per UE. There may be 10000 PDU sessions and for one bridge there may be one or more Qos flows in each PDU session. There may also be one or more flows in a Qos flow.

One problem may be how the 5GS maps flows/QoS flows inside the 5G to traffic classes in the 5GS TSN bridge egress ports. In many cases, only a fully centralized mode of TSN may be supported.

A fully centralized mode TSN network may be shown in fig. 2. In addition to the TSN end stations and TSN bridges, there may be CUCs (centralized user controllers) and CNCs (centralized network controllers). The CNC in the TSN network may control/configure all TSN entities within the TSN network. The CUC may communicate TSN application service information with the TSN end station and send stream configuration information to the CNC. All nodes in the TSN network (TSN terminals and TSN bridges) can report their capabilities and neighborhood topology to the CNC. After obtaining this information, the CNC can build the topology (topology discovery) and capabilities of the entire TSN network.

Fig. 2 is a block diagram 200 of an example full centralized mode TSN network model. Based on the flow configuration information from the CUC, the CNC may decide whether to establish a TSN flow. CNCs can calculate the end-to-end path of a flow from the flow sender (so-called Talker in the TSN), the flow receiver (so-called listener in the TSN), the TSN entity capabilities, the link capabilities, and the TSN network topology.

After calculating the path, the CNC may configure the TSN bridge with forwarding rules, flow information in the ingress ports (i.e., per flow forwarding and policing, PSFP), and scheduling patterns for each traffic class in the egress ports. When a data frame/packet arrives at the bridge, the bridge can know how to handle, i.e., when and at which port to forward the received frame.

Fig. 3 is a block diagram 300 of an example bridge ingress port and egress port. Ingress and egress ports of a bridge are logical concepts associated with each flow. One port may be an ingress port and an egress port of different streams.

For example, in FIG. 3, for flow-1, the ingress port is port-1 and the egress port is port-5; for flow-2, the ingress port is port-3 and the egress port is port-4; for flow-3, the ingress port is port-4 and the egress port is port-2.

A TSN bridge can support up to 8 traffic classes. Different processing priorities may exist for different traffic classes. Each stream is associated with a class. Before a packet of a flow is sent out of an egress port, the packet will be placed in a queue associated with the packet class in the egress port. The scheduling process may select packets from the queues and send out according to a scheduling scheme from the CNC.

Fig. 4 is a block diagram 400 of an example frame process in a bridge. Fig. 4 may show how frames of a flow are handled in a TSN bridge.

This may assume that the ingress and egress ports of a flow are port-1 and port-2. The traffic class of the flow may be 2. The CNC may provide the PSFP in the ingress port (i.e., port-1) and the forwarding rules and scheduling information in the egress port (i.e., port-2).

When a packet of a flow arrives at port-1, the bridge may perform related operations, such as policy, queuing, etc., and send the packet to the forwarding process. The forwarding process may send packets to the outgoing port's queue (i.e., the traffic class 2 queue) according to the forwarding rules and the traffic class of the packets.

The scheduling process may select packets from the queues and send out according to a scheduling scheme from the CNC. In some embodiments, the frame and packet are the same. The flow may be identified by a source address and a destination address.

For ethernet flows, each packet may be identified by a source and destination MAC address and optionally a VLAN ID. For IP flows, each packet may be identified by a source and destination IP address, a port number, and optionally a protocol type.

In many cases, 5G systems may simulate TSN bridge to TSN network, a so-called virtual/logical TSN bridge mode. Such a "logical" TSN bridge may include TSN converter (TT) functionality for interoperability between TSN systems and 5G systems in the U-plane. In the UPF, there is an NW-TT (network TT) connected to the TSN domain. In the UE, there may be a DS-TT (device TT) connected to the TSN domain. In the control plane, TSN AF (adaptive function) may be connected to TSN CNC.

To achieve this transparency to the TSN network, the 5GS may provide TSN ingress and egress ports via the TSN converter (device) functions on the UE side and the UPF side.

Fig. 5 is a block diagram 500 of an example 5GS supported TSN as a virtual TSN bridge. For a particular TSN network, a virtual TSN bridge may be per UPF granularity. This may indicate that all PDU sessions targeting that particular TSN network consist of one virtual TSN bridge under the same UPF.

The virtual TSN bridge design may hide certain processes, RANs, wireless communication links, etc. in the 5GC system in the TSN network. Inside 5GS, existing mechanisms may still be valid.

When the TSN AF receives the configuration from the CNC, it may trigger a PCC procedure to establish resources (e.g., qoS flows) that may carry the TSN flows and/or send PMIC (port management information container) or BMIC (bridge management information container) to the UPF/NW-TT and/or UE/DS-TT.

The PMIC and BMIC may be exchanged between TSN AF and UPF/NW-TT via PCF and SMF. PMIC and BMIC may be exchanged between TSN AF and UE/DS-TT via PCF, SMF, AMF and NG-RAN. The PMIC and BMIC may be transparent to the 5GS entity (i.e., PCF, SMF, AMF, NG-RAN).

In a 5GS TSN bridge, there may be thousands of PDU sessions above, and there may be one or more Qos flows carrying TSN flows in each PDU session. If NW-TT/UPF or DS-TT/UE implements traffic class based scheduling in the egress port of the 5GS TSN bridge, a solution to map Qos flows of PDU sessions to queues of the bridge egress port may be required.

Overview of the System

Some embodiments relate to traffic class processing performed by a wireless communication device or function. The UPF/NW-TT and/or the UE/DS-TT may receive information indicating traffic categories of QoS flows or service flows. One example case may be when the TSN AF receives a configuration from the CNC, the TSN AF may send traffic class information to the UPF/NW-TT and/or UE/DS-TT in the PMIC or BMIC. Traffic class information includes flows and related traffic classes. Alternatively, another example is when the TSN AF receives a configuration from the CNC, the TSN AF may send traffic class information to the SMF via the PCF. The SMF sends traffic class information to the UE/DS-TT and/or UPF/NW-TT. Traffic class information may include QoS flows and related traffic classes, or flows and related traffic classes.

Fig. 6 is a signaling procedure 600 of an example procedure for the TSN AF to provide traffic classes to the UPF/NW-TT. Fig. 6 may show that the TSN AF sends traffic class information to the UPF/NW-TT in the PMIC or BMIC.

In step 610, the CNC 608 may send the configuration to the TSN AF. The configuration may include forwarding rules, PSFP information, and scheduling modes.

In step 612, the TSN AF 606 may determine the traffic class of the flow according to the configuration received from the CNC.

In step 614, the TSN AF 606 may send traffic class information to the UPF/NW-TT 602 in the PMIC or BMIC via the PCF and SMF. Traffic class information may include flows and related traffic classes.

For UL flow traffic of a flow, the UPF/NW-TT may send packets to queues corresponding to the flow's traffic class.

Fig. 7 is a signaling procedure 700 of an example procedure for the TSN AF to provide traffic class to the UE/DS-TT. Fig. 7 shows that the TSN AF can send traffic information to the UE/DS-TT in the PMIC or BMIC.

In step 710, the CNC may send the configuration to the TSN AF. The configuration includes forwarding rules, PSFP information, and scheduling modes.

In step 712, the TSN AF may determine the traffic class of the flow from the configuration received from the CNC.

In step 714, the TSN AF may send traffic class information to the UE/DS-TT in the PMIC or BMIC via PCF, SMF, AMF and NG-RAN. Traffic class information includes flows and related traffic classes.

For DL flow traffic of a flow, the UE/DS-TT may send packets to a queue corresponding to the flow's traffic class.

Fig. 8 is a signaling process 800 of an example process for TSN AF to provide traffic classes to SMF and UPF. Fig. 8 may show that the TSN AF may send traffic information to the SMF, and that the SMF sends the UPF/NW-TT in an N4 request.

In step 812, the CNC 810 may send the configuration to the TSN AF 808. The configuration may include forwarding rules, PSFP information, and scheduling modes.

In step 814, the TSN AF may determine the traffic class of the flow according to the configuration received from the CNC.

In step 816, the TSN AF may provide/withdraw service information to the PCF by invoking an npcf_policyauthentication_create request or an npcf_policyauthentication_update request service operation. The request/service operation may carry traffic class information including flow information and related traffic classes.

In step 818, PCF 806 may initiate an SM policy association modification to SMF 804, which includes PCC rules. The message may also carry traffic class information.

In step 820, the SMF may apply the received PCC rule to an existing Qos flow or establish a new Qos flow. The SMF 804 may send an N4 request to the UPF/NW-TT 802 carrying traffic class information. Traffic class information includes QoS flows and related traffic classes, or flows and related traffic classes. For UL flow traffic of a flow, the UPF/NW-TT may send packets to queues corresponding to the flow's traffic class.

The SMF may provide traffic class information to the UE/DS-TT.

Fig. 9 is an example signaling procedure 900 for TSN AF to provide traffic classes to SMFs and UEs. Fig. 9 may show that the TSN AF transmits traffic information to the SMF, and the SMF transmits the UE/DS-TT in PDU session modification.

In step 916, the CNC 914 may send the configuration to the TSN AF 912. The configuration may include forwarding rules, PSFP information, and scheduling modes.

In step 918, TSN AF 914 may determine the traffic class of the flow from the configuration received from the CNC.

In step 920, the TSN AF 912 may provide/withdraw service information to the PCF by invoking an npcf_policyauthentication_create request or an npcf_policyauthentication_update request service operation. The request/service operation may carry traffic class information including flow information and related traffic classes.

In step 922, PCF 910 may send to SMF 908 an SM policy association modification comprising PCC rules. The message may also carry traffic class information.

In step 924, the SMF 908 may apply the received PCC rules to an existing Qos flow or establish a new Qos flow. The SMF may initiate PDU session modification to the UE/DS-TT 902 via the AMF 906 and NG-RAN 904. The SMF may call namf_communication_n1n2 messaging to the AMF, which includes N2 SM information, N1 SM container. The message may include traffic class information. Traffic class information may be included in the N1 SM container. Traffic class information may include QoS flows and related traffic classes, or flows and related traffic classes.

In step 926, the AMF 906 may send an NG-RAN N2 message that may carry traffic class information.

In step 928, the NG-RAN may send an N1 SM message carrying traffic class information to the UE/DS-TT in RAN-specific signaling.

The UPF/NW-TT and/or the UE/DS-TT may receive information indicating traffic categories of QoS flows or service flows. In some embodiments, when the TSN AF receives a configuration from the CNC, the TSN AF may send traffic class information to the UPF/NW-TT and/or the UE/DS-TT in the PMIC or BMIC. Traffic class information may include flows and related traffic classes.

In some embodiments, the TSN AF receives the configuration from the CNC, and in response, the TSN AF may send traffic class information to the SMF via the PCF. The SMF may send traffic class information to the UE/DS-TT and/or UPF/NW-TT. Traffic class information may include QoS flows and related traffic classes, or flows and related traffic classes.

Fig. 10 is a block diagram 1000 of an example method for traffic class processing. The method may include receiving, by a first network function, a data configuration from a network node (block 1002). The method may also include obtaining, by the first network function, traffic class information based on the data configuration (block 1004). The method may also include transmitting traffic class information by the first network function to the second network function (block 1006).

In some embodiments, the first network function is a Time Sensitive Network (TSN) application or an Adaptation Function (AF).

In some embodiments, the data configuration includes any one of forwarding rules, per-flow filtering and policing (PSFP) information, and scheduling mode information.

In some embodiments, the second network function is a user plane function/network side TSN converter (UPF/NW-TT).

In some embodiments, the second network function is user equipment/terminal side TSN converter/(UE/DS-TT).

In some embodiments, the traffic class information is sent to the second network function via a Port Management Information Container (PMIC).

In some embodiments, the traffic class information is sent to the second network function via a Bridge Management Information Container (BMIC).

In some embodiments, the network node comprises a Centralized Network Controller (CNC).

In some embodiments, the second network function is a Policy Control Function (PCF), wherein the PCF is configured to forward the acquired traffic class information to a Session Management Function (SMF).

In some embodiments, the second network function is a PCF, wherein the PCF is configured to forward the acquired traffic class information to an SMF, wherein the SMF is configured to send the traffic class information to the user equipment/terminal side TSN converter/(UE/DS-TT) via an access and mobility management function (AMF) and a next generation radio access network (NG-RAN) node.

In some embodiments, the second network function is a PCF, wherein the PCF is configured to forward the obtained traffic class information to an SMF, wherein the SMF is configured to send the traffic class information to a user plane function/network side TSN converter (UPF/NW-TT).

In some embodiments, the traffic class information includes information related to the data flow and related traffic classes for the data flow.

In some embodiments, the traffic class information includes quality of service (QoS) flows and related traffic classes for QoS flows.

In another embodiment, a method for data communication includes receiving, by a second network function, a first message from a first network function, the first message including traffic class information, wherein the first network function is configured to obtain the traffic class information based on configuration data received from a network node.

In some embodiments, the first message includes any one of forwarding rules, per-flow filtering and policing (PSFP) information, and scheduling mode information.

In some embodiments, the acquired traffic class information is received by the second network function via a Port Management Information Container (PMIC).

In some embodiments, the acquired traffic class information is received by a second network function via a Bridge Management Information Container (BMIC).

In some embodiments, the third network function is configured to receive the first message and send it to the second network function.

In some embodiments, the third network function is a Session Management Function (SMF) configured to receive the first message from the first network function via the PCF.

In some embodiments, the third network is configured to send traffic class information to a user plane function/network side TSN converter (UPF/NW-TT).

In some embodiments, the third network is configured to send traffic class information to the user equipment/terminal side TSN converter/(UE/DS-TT) via an access and mobility management function (AMF) and a next generation radio access network (NG-RAN) node.

In some embodiments, the acquired traffic class information includes quality of service (QoS) flows for traffic classes, or data flows and related traffic classes for the data flows.

Example Wireless System

Fig. 11 illustrates an example of a wireless communication system in which one or more embodiments in accordance with the present technology may be employed. The wireless communication system 1100 may include one or more Base Stations (BSs) 1105a, 1105b, one or more wireless devices or terminals 1110a, 1110b, 1110c, 1110d, and a core network 1125. Base stations 1105a, 1105b may provide access services to wireless devices 1110a, 1110b, 1110c, and 1110d in one or more wireless sectors. In some implementations, the base stations 1105a, 1105b include directional antennas that generate two or more directional beams to provide wireless coverage for different sectors. The base station may implement the functionality of scheduling cells or candidate cells as described in the present invention.

The core network 1125 may communicate with one or more base stations 1105a, 1105 b. The core network 1125 provides connectivity to other wireless communication systems and to wired communication systems. The core network may include one or more service subscription databases to store information related to subscribed wireless devices 1110a, 1110b, 1110c, and 1110 d. The first base station 1105a may provide wireless service based on a first radio access technology, and the second base station 1105b may provide wireless service based on a second radio access technology. The base stations 1105a and 1105b may be co-located or installed separately on site depending on the deployment scenario. Wireless devices 1110a, 1110b, 1110c, and 1110d can support a plurality of different wireless access technologies.

In some implementations, a wireless communication system may include multiple networks using different wireless technologies. Dual-mode or multi-mode wireless devices include two or more wireless technologies that may be used to connect to different wireless networks.

FIG. 12 is a block diagram representing a portion of a hardware platform. A hardware platform 1205, such as a network function or a base station or a terminal or wireless device (or UE), may include a processor circuit 1210, such as a microprocessor, that applies one or more of the techniques presented herein. Hardware platform 1205 may include transceiver circuitry 1215 to send and/or receive wired or wireless signals over one or more communication interfaces, such as antenna 1220 or a wired interface (not explicitly shown). Hardware platform 1205 may implement other communication interfaces having defined protocols for sending and receiving data. Hardware platform 1205 may include one or more memories (not explicitly shown) configured to store information, such as data and/or instructions. In some applications, processor circuit 1210 may include at least a portion of transceiver circuit 1215. In some embodiments, at least some of the techniques, modules, or functions of the present invention are implemented using hardware platform 1205.

Conclusion(s)

Other embodiments, modules, and functional operations of the present disclosure and described herein may be applied to digital electronic circuitry, or computer software, firmware, or hardware, including the architectures disclosed herein and their equivalent architectures, or combinations of one or more of them. Other embodiments disclosed and described may be implemented as one or more computer program products, such as one or more modules of computer program instructions encoded on a computer-readable medium, for execution by, or to control the operation of, data processing apparatus. The computer readable medium can be a machine readable storage device, a machine readable storage substrate, a memory device, a composition of matter effecting a machine readable transmission signal, or a combination of one or more thereof. The term "data processing apparatus" encompasses all apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus may comprise, in addition to hardware, code for creating an execution environment for the computer program in question, e.g., code, comprising processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A transmitted signal is a manually generated signal, such as a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiving devices.

A computer program (also known as a program, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computer environment. The computer program does not necessarily correspond to a file in the file system. A program can be stored in a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language publication), in a single file dedicated to the program in question, or in multiple coordinated files (e.g., files that store one or more modules, sub-programs, or portions of code). A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

The processes and logic flows described in this invention can be performed by one or more programmable processors executing one or more programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Processors suitable for the execution of a computer program include, by way of example, both general and special purpose functional processors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operable to receive, or transmit, data to, or from, one or more mass storage devices for storing data, e.g., a magnetic, magneto-optical disk, or optical disk. However, the computer need not have such devices. Computer readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disk; and CD ROM and DVD-ROM discs. The processor and the memory may be supplemented by, or incorporated in special purpose logic circuitry.

Since the present invention includes many details, it should not be construed as limiting the scope of any invention or of the claims, but rather as describing the particular features of particular embodiments of particular inventions. Suitable features described in the context of different embodiments of the invention may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple discrete embodiments or in any suitable subcombination. Furthermore, although features may be described above as applied in appropriate combinations and as initially claimed, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, operations are depicted in the drawings in a particular order, which should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Furthermore, the separation of various system components in the embodiments described herein should not be understood as requiring such separation in all embodiments.

Only a few applications and examples have been described, while other applications, enhancements and variations may be made based on the description and illustration of the present invention.

Claims

1. A method for data communication, comprising:

the first network function receives a data configuration from a network node;

the first network function obtains flow category information based on the data configuration; and

the first network function transmits the traffic class information to a second network function.

2. The method of claim 1, wherein the first network function is a time sensitive network, TSN, application or an adaptation function, AF.

3. The method of claim 1, wherein the data configuration includes any one of forwarding rules, per-flow filtering and policing PSFP information, and scheduling mode information.

4. The method of claim 1, wherein the second network function is a user plane function/network side TSN converter UPF/NW-TT.

5. The method of claim 1, wherein the second network function is a user equipment/terminal side TSN converter UE/DS-TT.

6. The method of claim 1, wherein the traffic class information is sent to the second network function via a port management information container PMIC.

7. The method of claim 1, wherein the traffic class information is sent to the second network function via a bridge management information container BMIC.

8. The method of claim 1, wherein the network node comprises a centralized network controller, CNC.

9. The method of claim 1, wherein the second network function is a policy control function, PCF, wherein the PCF is configured to forward the obtained traffic class information to a session management function, SMF.

10. The method of claim 1, wherein the second network function is a PCF, wherein the PCF is configured to forward the acquired traffic class information to an SMF, wherein the SMF is configured to send the traffic class information to a user equipment/terminal side TSN converter UE/DS-TT via an access and mobility management function AMF and a next generation radio access network NG-RAN node.

11. The method of claim 1, wherein the second network function is a PCF, wherein the PCF is configured to forward the obtained traffic class information to an SMF, wherein the SMF is configured to send the traffic class information to a user plane function/network side TSN converter UPF/NW-TT.

12. The method of claim 1, wherein the traffic class information comprises data flow related information and related traffic classes of the data flow.

13. The method of any of claims 1, 2, 9 and 10, wherein the traffic class information comprises quality of service, qoS, flows and related traffic classes of the QoS flows.

14. A method for data communication, comprising:

the second network function receives a first message from a first network function, the first message comprising traffic class information, wherein the first network function is configured to obtain the traffic class information based on configuration data received from a network node.

15. The method of claim 14, wherein the first network function is a time sensitive network, TSN, application or an adaptation function, AF.

16. The method of claim 14, wherein the configuration data includes any one of forwarding rules, per-flow filtering and policing PSFP information, and scheduling mode information.

17. The method of claim 14, wherein the second network function is a user plane function/network side TSN converter UPF/NW-TT.

18. The method of claim 14, wherein the second network function is a user equipment/terminal side TSN converter UE/DS-TT.

19. The method of claim 14, wherein the traffic class information is received by the second network function via a port management information container PMIC.

20. The method of claim 14, wherein the traffic class information is received by the second network function via a bridge management information container BMIC.

21. The method of claims 14, 17 and 18, wherein a third network function is configured to receive the first message and send it to the second network function.

22. The method of claim 21, wherein the third network function is a session management function, SMF, configured to receive the first message from a first network function via a PCF.

23. The method of claim 22, wherein the third network is configured to send traffic class information to a user plane function/network side TSN converter UPF/NW-TT.

24. The method of claim 22, wherein the third network is configured to send traffic class information to a user equipment/terminal side TSN converter UE/DS-TT via an access and mobility management function AMF and a next generation radio access network NG-RAN node.

25. The method of any of claims 14, 15, 19 and 20, wherein the obtained traffic class information comprises a quality of service, qoS, flow of a traffic class or a traffic class related to a data flow.

26. A wireless communication device comprising a processor configured to perform the method of any one of claims 1 to 25.

27. A non-transitory computer readable medium having stored thereon code, which when executed by a processor, causes the processor to implement the method of any of claims 1 to 25.