Communication method and apparatus

Abstract

This application provides a communication method, which includes: a Controlled Flow Controller (CUC) determining the demand information of a TSN flow based on the characteristic information of multiple QoS flows; the CUC receiving the status information of a TSN flow from a Controlled Flow Controller (CNC); and the CUC sending configuration information to the sending and receiving ends of the multiple QoS flows based on the status information of the TSN flow from the CNC. The CUC treats multiple QoS flows as a single TSN flow, determines the demand information of that single TSN flow, and determines the same set of configuration information for the multiple QoS flows, meaning that the multiple QoS flows are configured to be transmitted on the same port. With a fixed number of ports at the sending and receiving ends, this method can increase the number of QoS flows transmitted. These multiple QoS flows are mapped from latency-sensitive service data, thereby improving the transmission efficiency of latency-sensitive service data.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a communication method and apparatus. Background Technology

[0002] To ensure end-to-end quality of service (QoS), 5G mobile communication systems employ a 5G QoS model based on quality of service flow (QoSflow). Terminal devices can establish one or more Protocol Data Unit (PDU) sessions with the 5G network, and each PDU session can establish one or more QoS flows.

[0003] To address the need for reliable latency transmission, the Institute of Electrical and Electronics Engineers (IEEE) defined the Time-Sensitive Network (TSN) standard. This standard can provide reliable latency transmission services, ensuring the reliability of latency-sensitive business data transmission and predictable end-to-end transmission latency.

[0004] In the system architecture of 3GPP and TSN interoperability, TSN flows are bound to QoS flows and transmitted through the 5G network. With the rapid growth of communication services, the amount of latency-sensitive service data is also increasing. How to improve the transmission efficiency of latency-sensitive service data in the 3GPP and TSN interoperability system architecture is an urgent problem to be solved. Summary of the Invention

[0005] This application provides a communication method and apparatus that improves the transmission efficiency of latency-sensitive service data under a 3GPP and TSN interoperability system architecture.

[0006] In a first aspect, a communication method is provided, comprising: a centralized user configuration function (PCF) network element determining demand information for a Time Sensitive Network (TSN) flow based on characteristic information of multiple Quality of Service (QoS) flows, wherein the TSN flow corresponds to the multiple QoS flows; the PCF network element sending the demand information for the TSN flow to a centralized network configuration function (NMC) network element; the PCF network element receiving status information of the TSN flow from the NMC network element, wherein the status information of the TSN flow is determined based on the demand information for the TSN flow; and the PCF network element sending information for configuring the sending end and receiving end corresponding to the multiple QoS flows to the sending end and receiving end corresponding to the multiple QoS flows based on the status information of the TSN flow.

[0007] It should be understood that the centralized user configuration function network element sends the same set of configuration information to the sender and receiver of the multiple QoS flows based on the status information of the TSN flow. That is, the configuration information received by the sender and receiver of the multiple QoS flows from the centralized user configuration function network element based on the status information of the TSN flow is the same set of configuration information, which is used to configure the sender and receiver corresponding to the multiple QoS flows.

[0008] It should also be understood that a TSN stream in this application is any TSN stream, not a specific TSN stream.

[0009] According to the method provided in this application, multiple QoS flows are treated as a single TSN flow, and configuration information is determined based on the demand information of this single TSN flow. This configuration information is used to configure the sending and receiving ends corresponding to the multiple QoS flows. The multiple QoS flows are transmitted on the same port of the sending and receiving ends corresponding to the multiple QoS flows according to the configuration information, thereby improving the transmission efficiency of the QoS flows. Furthermore, these multiple QoS flows are mapped from latency-sensitive service data in the communication system; in other words, the method provided in this application can improve the transmission efficiency of latency-sensitive service data in the communication system.

[0010] Furthermore, multiple QoS flows correspond to the same TSN flow, and these multiple QoS flows are configured with the same set of configuration information by the centralized user configuration function network element. When processing these multiple QoS flows, the sending and receiving ends do not need to process each QoS flow corresponding to the configuration information based on the configuration information for each QoS flow within the multiple QoS flows. Instead, the sending and receiving ends can process the multiple QoS flows based on the configuration information determined in this application. Simultaneously, the centralized user configuration function does not need to perform multiple configurations when determining the configuration information; that is, the centralized user configuration function sends the same set of configuration information to the sending and receiving ends of multiple QoS flows based on the TSN flow status information, thereby reducing signaling overhead.

[0011] In conjunction with the first aspect, in some possible implementations, the information used to configure the sender and receiver corresponding to the multiple QoS flows includes the identifier of the TSN flow, and the method further includes: the centralized user configuration function sending the correspondence between the TSN flow and the multiple QoS flows to the sender and receiver corresponding to the multiple QoS flows.

[0012] It should be understood that the centralized user configuration function sends the correspondence between the TSN flow and the multiple QoS flows to the sending and receiving ends corresponding to the multiple QoS flows. That is, after receiving the configuration information, the sending and receiving ends corresponding to the multiple QoS flows determine, based on the correspondence between the TSN flow and the multiple QoS flows, which specific QoS flow data frames should be adjusted (e.g., the sending time of the QoS flow data frames).

[0013] Based on the above technical solution, the centralized user configuration function sends information to the sender and receiver corresponding to the multiple QoS flows, including the identifier of the TSN flow. The sender and receiver of the multiple QoS flows determine the configuration information including the TSN flow identifier based on the correspondence between the TSN flow and the multiple QoS flows, and configure the data frames of the multiple QoS flows accordingly. This ensures that the sender and receiver of the multiple QoS flows use the required information of the TSN flow corresponding to the multiple QoS flows to configure the data frames of the multiple QoS flows, further guaranteeing the system's transmission performance.

[0014] In conjunction with the first aspect, in some possible implementations, the information used to configure the sending and receiving ends corresponding to the plurality of QoS flows includes the identifiers of the plurality of QoS flows.

[0015] Based on the above technical solution, the centralized user configuration function sends information to the sending and receiving ends corresponding to the multiple QoS flows, including the identifiers of the multiple QoS flows. The sending and receiving ends of these multiple QoS flows determine which QoS flows to schedule using the configuration information based on these identifiers. This ensures that the sending and receiving ends of the multiple QoS flows use the identifier information of the multiple QoS flows to determine which QoS flow data frames to schedule using the configuration information, further guaranteeing the system's transmission performance.

[0016] In conjunction with the first aspect, in some possible implementations, the sending end corresponding to the multiple QoS flows is the same, and the receiving end corresponding to the multiple QoS flows is the same.

[0017] In conjunction with the first aspect, in some possible implementations, the multiple QoS flows satisfy an aggregation condition, which includes one or more of the following:

[0018] The sessions to which these multiple QoS flows belong correspond to the same centralized user configuration function network element;

[0019] The transmission periods of these multiple QoS flows are the same or are multiples of each other;

[0020] The core network packet delay budget (CN PDB) corresponding to these multiple QoS flows is the same;

[0021] The multiple QoS flows arrive at their respective senders at the same time.

[0022] It should be understood that the aggregation condition may also include: the allocation and retention priority (ARP) values ​​of the multiple QoS flows are all within a preset range, such as ARP between 1 and 8; or, the ARP values ​​of the multiple QoS flows are all outside the preset range, such as ARP outside the range of 1 to 8. The range of ARP values ​​may be predefined by the protocol, or indicated by the system through indication information, and is not limited in this application. Furthermore, the specific range of ARP values ​​in this application is merely an example; the ARP values ​​may also be other ranges, and this application does not limit them.

[0023] It should also be understood that when the session management function (SMF) is used as a centralized user configuration function network element, the aggregation condition may also include: the SMF corresponding to the PDU sessions to which the multiple QoS flows belong is the same.

[0024] In conjunction with the first aspect, in some possible implementations, before the centralized user configuration function network element determines the demand information of a time-sensitive network (TSN) flow based on the characteristic information of multiple QoS flows, the method further includes: the centralized user configuration function network element receiving information from the sending end corresponding to the multiple QoS flows for indicating that the multiple QoS flows are mapped to a single TSN flow.

[0025] It should be understood that the centralized user configuration receives indication information from the senders corresponding to the multiple QoS flows, indicating that the multiple QoS flows should be treated as a single TSN flow. Specifically, the centralized user configuration sends the established multiple QoS flows to their corresponding senders. Based on the information of the multiple QoS flows, the senders assign the same aggregation identifier to the QoS flows within the same transmission time interval and send indication information to the centralized user configuration. This indication information is used to instruct the aggregation of the multiple QoS flows.

[0026] Based on the above technical solution, the centralized user configuration function network element receives information from the sending end corresponding to the multiple QoS flows, indicating that the multiple QoS flows are regarded as a single TSN flow. The centralized user configuration function network element treats the multiple QoS flows as a single TSN flow according to the indication information and determines the configuration information for configuring the multiple QoS flows based on the requirement information of the single TSN flow. The multiple QoS flows are transmitted on the same port of the sending and receiving ends corresponding to the multiple QoS flows according to the configuration information, improving the transmission efficiency of the QoS flows. Simultaneously, the multiple QoS flows are obtained by mapping time-sensitive service data in the communication system; in other words, the method provided in this application can improve the transmission efficiency of time-sensitive service data in the communication system.

[0027] In conjunction with the first aspect, in some possible implementations, the demand information for a TSN flow includes the maximum frame length. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0028] The centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst volume (MDBV) of multiple QoS flows, or the centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst lengths of the multiple QoS flows.

[0029] In conjunction with the first aspect, in some possible implementations, the demand information for a TSN flow includes the maximum number of frames per period. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0030] The centralized user configuration function network element determines the maximum number of frames per period based on the sum of the number of data frames transmitted by multiple QoS flows within an interval, where the interval is the least common multiple of the transmission periods of the multiple QoS flows.

[0031] In conjunction with the first aspect, in some possible implementations, the demand information for the TSN flow includes intervals. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0032] The centralized user configuration function network element determines the interval based on the least common multiple of the transmission cycles of multiple QoS flows.

[0033] In conjunction with the first aspect, in some possible implementations, the requirement information of the TSN flow includes the latest transmission offset, which represents the maximum value of the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows later than the start time of the interval, the interval being the least common multiple of the transmission periods of the multiple QoS flows, and the maximum frame length being the maximum length of the data frames of the multiple QoS flows.

[0034] In conjunction with the first aspect, in some possible implementations, the requirement information of the TSN flow includes the earliest transmission offset, which indicates that the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows is earlier than the maximum value of the start time of the interval;

[0035] This centralized user configuration function network element determines the demand information of a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0036] The centralized user configuration function network element determines the earliest transmission offset based on the earliest time that the multiple QoS flows arrive at the corresponding transmitters.

[0037] In conjunction with the first aspect, in some possible implementations, the TSN flow demand information includes the maximum allowed latency of the TSN flow. The centralized user configuration function network element determines the demand information of a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0038] The centralized user configuration function network element determines the maximum allowed latency of the TSN flow based on the maximum value among the maximum buffer durations of the multiple QoS flows. The maximum buffer duration is the maximum duration for which the sending end corresponding to the multiple QoS flows buffers the data frames of the multiple QoS flows.

[0039] It should be understood that the requirement information of the TSN flow includes the maximum allowed latency of the TSN flow, the maximum buffer duration of the multiple QoS flows being the same, and the maximum allowed latency of the TSN flow being determined based on the maximum buffer duration of any one of the multiple QoS flows at the sending end; or the maximum buffer duration of the multiple QoS flows being different, and the maximum allowed latency of the TSN flow being determined based on the maximum value among the maximum buffer durations of the multiple QoS flows; wherein, the maximum buffer duration is the maximum duration for which the sending end buffers the data frames of the multiple QoS flows.

[0040] In conjunction with the first aspect, in some possible implementations, the TSN flow requirement information includes the number of redundant paths. This number of redundant paths is determined based on whether the multiple QoS flows include data frames that need to be sent to multiple QoS receivers via multiple user plane paths. The centralized user configuration function network element determines the TSN flow requirement information based on the characteristic information of multiple QoS flows, including:

[0041] The centralized user configuration function network element determines the number of redundant paths based on whether the multiple QoS flows include QoS flows that require redundant transmission.

[0042] In conjunction with the first aspect, in some possible implementations, the information for configuring the sending and receiving ends corresponding to the plurality of QoS flows includes information for adjusting the transmission time of the data frames of the plurality of QoS flows.

[0043] Secondly, a communication method is provided, comprising: a centralized user configuration function network element determining demand information of a time-sensitive network (TSN) flow based on characteristic information of multiple QoS flows, wherein the TSN flow corresponds to the multiple QoS flows; the centralized user configuration function network element sending the demand information of the TSN flow to a centralized network configuration function network element; the centralized network configuration function network element receiving the demand information of the TSN flow from the centralized user configuration function network element, determining the status information of the TSN flow based on the demand information of the TSN flow, and sending the status information of the TSN flow to the centralized user configuration function network element; the centralized user configuration function network element receiving the status information of the TSN flow from the centralized network configuration function network element, and sending information for configuring the sending and receiving ends corresponding to the multiple QoS flows to the sending and receiving ends corresponding to the multiple QoS flows based on the status information of the TSN flow.

[0044] According to the method provided in this application, the centralized user configuration function network element treats multiple QoS flows as a single TSN flow and determines configuration information based on the requirement information of this single TSN flow. This configuration information is used to configure the sending and receiving ends corresponding to the multiple QoS flows. The multiple QoS flows are transmitted on the same port of the sending and receiving ends corresponding to the multiple QoS flows according to the configuration information, thereby improving the transmission efficiency of QoS flows. Furthermore, these multiple QoS flows are mapped from latency-sensitive service data in the communication system; in other words, the method provided in this application can improve the transmission efficiency of latency-sensitive service data in the communication system.

[0045] In conjunction with the second aspect, in some possible implementations, the information used to configure the sender and receiver corresponding to the multiple QoS flows includes the identifier of the TSN flow. The method further includes: the centralized user configuration function network element sending the correspondence between the TSN flow and the multiple QoS flows to the sender and receiver corresponding to the multiple QoS flows.

[0046] Based on the above technical solution, the centralized user configuration function sends information to the sender and receiver corresponding to the multiple QoS flows, including the identifier of the TSN flow. The sender and receiver of the multiple QoS flows determine the configuration information including the TSN flow identifier based on the correspondence between the TSN flow and the multiple QoS flows, and configure the data frames of the multiple QoS flows accordingly. This ensures that the sender and receiver of the multiple QoS flows use the required information of the TSN flow corresponding to the multiple QoS flows to configure the data frames of the multiple QoS flows, further guaranteeing the system's transmission performance.

[0047] In conjunction with the second aspect, in some possible implementations, the information used to configure the sending and receiving ends corresponding to the plurality of QoS flows includes the identifiers of the plurality of QoS flows.

[0048] Based on the above technical solution, the centralized user configuration function sends information to the sending and receiving ends corresponding to the multiple QoS flows, including the identifiers of the multiple QoS flows. The sending and receiving ends of these multiple QoS flows determine which QoS flows to schedule using the configuration information based on these identifiers. This ensures that the sending and receiving ends of the multiple QoS flows use the identifier information of the multiple QoS flows to determine which QoS flow data frames to schedule using the configuration information, further guaranteeing the system's transmission performance.

[0049] In conjunction with the second aspect, in some possible implementations, the sending end corresponding to the multiple QoS flows is the same, and the receiving end corresponding to the multiple QoS flows is the same.

[0050] In conjunction with the second aspect, in some possible implementations, the multiple QoS flows satisfy an aggregation condition, which includes one or more of the following:

[0051] The multiple QoS flows belong to the same centralized user configuration function network element corresponding to the sessions they belong to;

[0052] The transmission periods of these multiple QoS flows are the same or are multiples of each other;

[0053] The CN PDBs corresponding to these multiple QoS flows are the same;

[0054] The multiple QoS flows arrive at their respective senders at the same time.

[0055] It should be understood that the aggregation condition may also include: the allocation and retention priority (ARP) values ​​of the multiple QoS flows are all within a preset range, for example, the ARP values ​​are all within the range of 1-8; or, the ARP values ​​of the multiple QoS flows are all outside the preset range, for example, the ARP values ​​are all outside the range of 1-8. The range of ARP values ​​may be predefined by the protocol, or it may be indicated by the system through indication information, and this application does not limit it. Furthermore, the specific range of ARP values ​​in this application is merely an example; the ARP values ​​may also be other ranges, and this application does not limit them.

[0056] It should also be understood that when the session management function (SMF) is used as a centralized user configuration function network element, the aggregation condition may also include: the SMF corresponding to the PDU sessions to which the multiple QoS flows belong is the same.

[0057] In conjunction with the second aspect, in some possible implementations, before the centralized user configuration function network element determines the demand information of a time-sensitive network (TSN) flow based on the characteristic information of multiple QoS flows, the method further includes: the centralized user configuration function network element receiving information from the sending end corresponding to the multiple QoS flows for indicating that the multiple QoS flows are mapped to a single TSN flow.

[0058] Based on the above technical solution, the centralized user configuration function network element receives information from the sending end corresponding to the multiple QoS flows, indicating that the multiple QoS flows are regarded as a single TSN flow. The centralized user configuration function network element treats the multiple QoS flows as a single TSN flow according to the indication information and determines the configuration information for configuring the multiple QoS flows based on the requirement information of the single TSN flow. The multiple QoS flows are transmitted on the same port of the sending and receiving ends corresponding to the multiple QoS flows according to the configuration information, improving the transmission efficiency of the QoS flows. Simultaneously, the multiple QoS flows are obtained by mapping time-sensitive service data in the communication system; in other words, the method provided in this application can improve the transmission efficiency of time-sensitive service data in the communication system.

[0059] In conjunction with the second aspect, in some possible implementations, the demand information for a TSN flow includes the maximum frame length. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0060] The centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst volume (MDBV) of multiple QoS flows, or the centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst lengths of the multiple QoS flows.

[0061] In conjunction with the second aspect, in some possible implementations, the demand information for a TSN flow includes the maximum number of frames per period. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0062] The centralized user configuration function network element determines the maximum number of frames per period based on the sum of the number of data frames transmitted by multiple QoS flows within an interval, where the interval is the least common multiple of the transmission periods of the multiple QoS flows.

[0063] In conjunction with the second aspect, in some possible implementations, the demand information for the TSN flow includes intervals. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0064] The centralized user configuration function network element determines the interval based on the least common multiple of the transmission periods of multiple QoS flows.

[0065] In conjunction with the second aspect, in some possible implementations, the requirement information of the TSN flow includes the latest transmission offset, which represents the maximum value of the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows later than the start time of the interval, the interval being the least common multiple of the transmission periods of the multiple QoS flows, and the maximum frame length being the maximum length of the data frames of the multiple QoS flows.

[0066] In conjunction with the second aspect, in some possible implementations, the demand information of the TSN flow includes the earliest transmission offset, which indicates that the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows is earlier than the maximum value of the start time of the interval;

[0067] This centralized user configuration function network element determines the demand information of a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0068] The centralized user configuration function network element determines the earliest transmission offset based on the earliest time that the multiple QoS flows arrive at the corresponding transmitters.

[0069] In conjunction with the second aspect, in some possible implementations, the TSN flow demand information includes the maximum allowed latency of the TSN flow. The centralized user configuration function network element determines the demand information of a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0070] The centralized user configuration function network element determines the maximum allowed latency of the TSN flow based on the maximum value among the maximum buffer durations of the multiple QoS flows. The maximum buffer duration is the maximum duration for which the sending end corresponding to the multiple QoS flows buffers the data frames of the multiple QoS flows.

[0071] It should be understood that the requirement information of the TSN flow includes the maximum allowed latency of the TSN flow, the maximum buffer duration of the multiple QoS flows being the same, and the maximum allowed latency of the TSN flow being determined based on the maximum buffer duration of any one of the multiple QoS flows at the sending end; or the maximum buffer duration of the multiple QoS flows being different, and the maximum allowed latency of the TSN flow being determined based on the maximum value among the maximum buffer durations of the multiple QoS flows; wherein, the maximum buffer duration is the maximum duration for which the sending end buffers the data frames of the multiple QoS flows.

[0072] In conjunction with the second aspect, in some possible implementations, the TSN flow requirement information includes the number of redundant paths. This number of redundant paths is determined based on whether the multiple QoS flows include data frames that need to be sent to multiple QoS receivers via multiple user plane paths. The centralized user configuration function network element determines the TSN flow requirement information based on the characteristic information of multiple QoS flows, including:

[0073] The centralized user configuration function network element determines the number of redundant paths based on whether the multiple QoS flows include QoS flows that require redundant transmission.

[0074] In conjunction with the second aspect, in some possible implementations, the information for configuring the sending and receiving ends corresponding to the plurality of QoS flows includes information for adjusting the transmission time of the data frames of the plurality of QoS flows.

[0075] Thirdly, a communication system is provided, including a centralized user configuration function network element and a centralized network configuration function network element, wherein:

[0076] The centralized user configuration function network element is used to: determine the demand information of a Time Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, wherein the TSN flow corresponds to the multiple QoS flows;

[0077] The centralized user configuration function network element is also used to: send the demand information of a TSN flow to the centralized network configuration function network element;

[0078] The centralized network configuration function network element is used to: receive the demand information of a TSN flow from the centralized user configuration function network element, determine the status information of the TSN flow based on the demand information of the TSN flow, and send the status information of the TSN flow to the centralized user configuration function network element.

[0079] The centralized user configuration function network element is also used to: receive the status information of a TSN flow from the centralized network configuration function network element, and send information for configuring the senders and receivers corresponding to the multiple QoS flows according to the status information of the TSN flow.

[0080] In conjunction with the third aspect, in some possible implementations, the information used to configure the sender and receiver corresponding to the multiple QoS flows includes the identifier of the TSN flow. The method further includes: the centralized user configuration function network element sending the correspondence between the TSN flow and the multiple QoS flows to the sender and receiver corresponding to the multiple QoS flows.

[0081] It should be understood that the centralized user configuration function network element sends the correspondence between the TSN flow and the multiple QoS flows to the corresponding sender and receiver. That is, after receiving the configuration information, the sender and receiver corresponding to the multiple QoS flows determine, based on the correspondence between the TSN flow and the multiple QoS flows, which specific QoS flows' data frames will have their transmission times adjusted.

[0082] In conjunction with the third aspect, in some possible implementations, the centralized user configuration function network element is also used to: send the correspondence between the TSN flow and the multiple QoS flows to the sending end and the receiving end corresponding to the multiple QoS flows when the information used to configure the sending end and the receiving end corresponding to the multiple QoS flows includes the identifier of the TSN flow.

[0083] In conjunction with the third aspect, in some possible implementations, the information used to configure the sending and receiving ends corresponding to the plurality of QoS flows includes the identifiers of the plurality of QoS flows.

[0084] In conjunction with the third aspect, in some possible implementations, the sending end corresponding to the multiple QoS flows is the same, and the receiving end corresponding to the multiple QoS flows is the same.

[0085] In conjunction with the third aspect, in some possible implementations, the multiple QoS flows satisfy an aggregation condition, which includes one or more of the following:

[0086] The multiple QoS flows belong to the same centralized user configuration function network element corresponding to the sessions they belong to;

[0087] The transmission periods of these multiple QoS flows are the same or are multiples of each other;

[0088] The CN PDBs corresponding to these multiple QoS flows are the same;

[0089] The multiple QoS flows arrive at their respective senders at the same time.

[0090] It should be understood that the centralized user configuration receives indication information from the senders corresponding to the multiple QoS flows, indicating that the multiple QoS flows should be treated as a single TSN flow. Specifically, the centralized user configuration sends the established multiple QoS flows to their corresponding senders. Based on the information of the multiple QoS flows, the senders assign the same aggregation identifier to the QoS flows within the same transmission time interval and send indication information to the centralized user configuration. This indication information is used to instruct the aggregation of the multiple QoS flows.

[0091] It should also be understood that the aggregation condition may also include: the allocation and retention priority (ARP) values ​​of the multiple QoS flows are all within the range of 1-8, or the ARP values ​​of the multiple QoS flows are all outside the range of 1-8.

[0092] It should also be understood that, assuming that the SMF is used as a centralized user configuration function network element, the fact that the SMF corresponding to the PDU sessions to which the multiple QoS flows belong is the same can be used as an aggregation condition.

[0093] In conjunction with the third aspect, in some possible implementations, before the centralized user configuration function network element determines the demand information of a time-sensitive network (TSN) flow based on the characteristic information of multiple QoS flows, the method further includes: the centralized user configuration function network element receiving information from the sending end corresponding to the multiple QoS flows for indicating that the multiple QoS flows are mapped to a single TSN flow.

[0094] In conjunction with the third aspect, in some possible implementations, the demand information for a TSN flow includes the maximum frame length. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0095] The centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst volume (MDBV) of multiple QoS flows, or the centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst lengths of the multiple QoS flows.

[0096] In conjunction with the third aspect, in some possible implementations, the demand information for a TSN flow includes the maximum number of frames per period. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0097] The centralized user configuration function network element determines the maximum number of frames per period based on the sum of the number of data frames transmitted by multiple QoS flows within an interval, where the interval is the least common multiple of the transmission periods of the multiple QoS flows.

[0098] In conjunction with the third aspect, in some possible implementations, the demand information for the TSN flow includes intervals. The centralized user configuration function network element determines the demand information for a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0099] The centralized user configuration function network element determines the interval based on the least common multiple of the transmission periods of multiple QoS flows.

[0100] In conjunction with the third aspect, in some possible implementations, the requirement information of the TSN flow includes the latest transmission offset, which represents the maximum value of the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows later than the start time of the interval, the interval being the least common multiple of the transmission periods of the multiple QoS flows, and the maximum frame length being the maximum length of the data frames of the multiple QoS flows.

[0101] In conjunction with the third aspect, in some possible implementations, the requirement information of the TSN flow includes the earliest transmission offset, which indicates that the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows is earlier than the maximum value of the start time of the interval.

[0102] This centralized user configuration function network element determines the demand information of a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0103] The centralized user configuration function network element determines the earliest transmission offset based on the earliest time that the multiple QoS flows arrive at the corresponding transmitters.

[0104] In conjunction with the third aspect, in some possible implementations, the TSN flow demand information includes the maximum allowed latency of the TSN flow. The centralized user configuration function network element determines the demand information of a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including:

[0105] The centralized user configuration function network element determines the maximum allowed latency of the TSN flow based on the maximum value among the maximum buffer durations of the multiple QoS flows. The maximum buffer duration is the maximum duration for which the sending end corresponding to the multiple QoS flows buffers the data frames of the multiple QoS flows.

[0106] It should be understood that the requirement information of the TSN flow includes the maximum allowed latency of the TSN flow, the maximum buffer duration of the multiple QoS flows being the same, and the maximum allowed latency of the TSN flow being determined based on the maximum buffer duration of any one of the multiple QoS flows at the sending end; or the maximum buffer duration of the multiple QoS flows being different, and the maximum allowed latency of the TSN flow being determined based on the maximum value among the maximum buffer durations of the multiple QoS flows; wherein, the maximum buffer duration is the maximum duration for which the sending end corresponding to the multiple QoS flows buffers the data frames of the multiple QoS flows.

[0107] In conjunction with the third aspect, in some possible implementations, the TSN flow requirement information includes the number of redundant paths. This number of redundant paths is determined based on whether the multiple QoS flows include data frames that need to be sent to multiple QoS receivers via multiple user plane paths. The centralized user configuration function network element determines the TSN flow requirement information based on the characteristic information of multiple QoS flows, including:

[0108] The centralized user configuration function network element determines the number of redundant paths based on whether the multiple QoS flows include QoS flows that require redundant transmission.

[0109] In conjunction with the third aspect, in some possible implementations, the information for configuring the sending and receiving ends corresponding to the plurality of QoS flows includes information for adjusting the transmission time of the data frames of the plurality of QoS flows.

[0110] Fourthly, a communication device is provided, comprising a processing module and a transceiver module, wherein,

[0111] This processing module is used to: determine the demand information of Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, wherein the TSN flow corresponds to the multiple QoS flows and the multiple QoS flows satisfy the aggregation conditions;

[0112] This transceiver module is used to: send the TSN flow request information to the centralized network configuration function network element;

[0113] The transceiver module is also used to: receive the status information of the TSN flow from the centralized network configuration function network element, wherein the status information of the TSN flow is determined based on the demand information of the TSN flow;

[0114] The processing module is also used to: based on the status information of the TSN flow, send information for configuring the sender and receiver to the sender and receiver corresponding to the multiple QoS flows through the transceiver module.

[0115] In conjunction with the fourth aspect, in some possible implementations, the processing module is further configured to: when the information used to configure the sending end corresponding to the plurality of QoS flows and the receiving end corresponding to the plurality of QoS flows includes the identifier of the TSN flow, transmit the correspondence between the TSN flow and the plurality of QoS flows to the sending end corresponding to the plurality of QoS flows and the receiving end corresponding to the plurality of QoS flows through the transceiver module.

[0116] In conjunction with the fourth aspect, in some possible implementations, the transceiver module is further configured to: send the correspondence between the TSN flow and the multiple QoS flows to the sending end and the receiving end corresponding to the multiple QoS flows when the information used to configure the sending end and the receiving end corresponding to the multiple QoS flows includes the identifier of the TSN flow.

[0117] In conjunction with the fourth aspect, in some possible implementations, the aggregation condition includes one or more of the following:

[0118] The Session Management Function (SMF) corresponding to the Protocol Data Unit (PDU) sessions to which these multiple QoS flows belong is the same;

[0119] The transmission periods of these multiple QoS flows are the same or are multiples of each other;

[0120] The core network packet delay budget (CN PDB) corresponding to these multiple QoS flows is the same;

[0121] The multiple QoS flows arrive at the corresponding senders at the same time.

[0122] The centralized user configuration receives information from the sender corresponding to the multiple QoS flows, indicating that the multiple QoS flows are mapped to a single TSN flow.

[0123] It should be understood that the centralized user configuration receives indication information from the senders corresponding to the multiple QoS flows, indicating that the multiple QoS flows should be treated as a single TSN flow. Specifically, the centralized user configuration sends the established multiple QoS flows to their corresponding senders. Based on the information of the multiple QoS flows, the senders corresponding to these multiple QoS flows assign the same aggregation identifier to the QoS flows within the same transmission time interval and send indication information to the centralized user configuration. This indication information is used to instruct the aggregation of the multiple QoS flows.

[0124] It should also be understood that the aggregation conditions may include: the ARP values ​​of the multiple QoS flows are all within a preset range, such as the ARP values ​​being between 1 and 8; or the ARP values ​​of the multiple QoS flows are all outside the preset range, such as the ARP values ​​being outside the range of 1 and 8.

[0125] In conjunction with the fourth aspect, in some possible implementations, the requirement information of the TSN flow includes a maximum frame length, which is determined based on the sum of the maximum data burst values ​​(MDBV) of the multiple QoS flows, or the maximum frame length is determined based on the sum of the maximum data burst lengths of the multiple QoS flows.

[0126] In conjunction with the fourth aspect, in some possible implementations, the requirement information of the TSN flow includes the maximum number of frames per period, which is the sum of the number of data frames transmitted by the multiple QoS flows within an interval, which is the least common multiple of the transmission periods of the multiple QoS flows.

[0127] In conjunction with the fourth aspect, in some possible implementations, the requirement information of the TSN flow includes the latest transmission offset, which is determined based on the interval and the maximum frame length. The latest transmission offset indicates the maximum value of the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows later than the start time of the interval, which is the least common multiple of the transmission periods of the multiple QoS flows, and the maximum frame length is the maximum length of the data frames of the multiple QoS flows sent by the sender corresponding to the multiple QoS flows.

[0128] In conjunction with the fourth aspect, in some possible implementations, the requirement information of the TSN flow includes the earliest transmission offset, which indicates that the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows is earlier than the maximum value of the start time of the interval.

[0129] The multiple QoS flows arrive at the corresponding sender at the same time, and the earliest transmission offset is determined based on the arrival time of any one of the multiple QoS flows at the sender.

[0130] or,

[0131] The multiple QoS flows arrive at their respective senders at different times, and the earliest transmission offset is determined based on the earliest time that the multiple QoS flows arrive at the sender.

[0132] In conjunction with the fourth aspect, in some possible implementations, the demand information for the TSN stream includes the maximum allowable latency for the TSN stream.

[0133] The maximum buffer duration of these multiple QoS flows is the same, and the maximum allowed latency of this TSN flow is determined based on the maximum buffer duration of any one of the multiple QoS flows at the sending end corresponding to the multiple QoS flows.

[0134] The maximum buffer durations of these multiple QoS flows are different, and the maximum allowed latency of this TSN flow is determined based on the maximum value among the maximum buffer durations of these multiple QoS flows;

[0135] The maximum buffer duration is the maximum duration for which the sending end of the multiple QoS flows buffers the data frames of those multiple QoS flows.

[0136] In conjunction with the fourth aspect, in some possible implementations, the requirement information of the TSN flow includes the number of redundant paths, which is determined based on whether the multiple QoS flows include QoS flows that require redundant transmission. The number of redundant paths indicates whether the network device needs to provide redundant paths.

[0137] In conjunction with the fourth aspect, in some possible implementations, the configuration information includes the interface configuration information, which is used by the sending end corresponding to the multiple QoS flows to adjust the transmission time of the data frames of the multiple QoS flows.

[0138] In conjunction with the fourth aspect, in some possible implementations, the information used to configure the sending end and the receiving end corresponding to the multiple QoS flows includes the identifiers of the multiple QoS flows.

[0139] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the methods of the first aspect and any possible implementation thereof.

[0140] Optionally, the communication device may also include a memory.

[0141] Optionally, the communication device may also include a communication interface, to which the processor is coupled.

[0142] In one implementation, the communication device configures network elements for centralized users. When the communication device configures network elements for centralized users, the communication interface can be a transceiver or an input / output interface.

[0143] In another implementation, the communication device is a chip configured in a centralized user configuration function network element. When the communication device is a chip configured in a centralized user configuration function network element, the communication interface can be an input / output interface.

[0144] Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0145] In a sixth aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any possible implementation of the first aspect.

[0146] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0147] In a seventh aspect, a processing apparatus is provided, including a processor and a memory. The processor is configured to read instructions stored in the memory and to receive signals via a receiver and transmit signals via a transmitter to execute the method in any possible implementation of the first aspect.

[0148] Optionally, the processor may be one or more, and the memory may be one or more.

[0149] Optionally, the memory can be integrated with the processor, or the memory can be set separately from the processor.

[0150] In the specific implementation process, the memory can be a non-transitory memory, such as a read-only memory, which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0151] It should be understood that related data interaction processes, such as sending configuration information, can be the process of outputting configuration information from the processor, and receiving configuration information can be the process of the processor receiving input configuration information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the receiver. The transmitter and receiver can be collectively referred to as a transceiver.

[0152] The processing device mentioned in the seventh aspect above can be one or more chips. The processor in the processing device can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0153] Eighthly, a computer program product is provided, comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform a method in any possible implementation of the first aspect, or causes a computer to perform a method in any possible implementation of the second aspect, or causes a computer to perform a method in any possible implementation of the third aspect.

[0154] Ninthly, a computer-readable storage medium is provided that stores a computer program (also referred to as code or instructions) that, when run on a computer, causes the method in any of the possible implementations of the first aspect to be executed, or causes the method in any of the possible implementations of the second aspect to be executed, or causes the method in any of the possible implementations of the third aspect to be executed. Attached Figure Description

[0155] Figure 1 This is a schematic diagram of a network architecture applicable to an embodiment of this application.

[0156] Figure 2 This is a schematic diagram of a QoS model.

[0157] Figure 3 This is a schematic diagram of the TSN configuration model.

[0158] Figure 4 This is a schematic diagram of a system architecture for 3GPP and TSN interoperability.

[0159] Figure 5 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0160] Figure 6 This is a schematic diagram illustrating the latency of a TSN stream in a 5G system.

[0161] Figure 7 This is a schematic diagram illustrating the latency of another type of TSN stream in a 5G system.

[0162] Figure 8 This is a schematic flowchart illustrating another communication method provided in an embodiment of this application.

[0163] Figure 9 This is a schematic block diagram of a communication device provided in an embodiment of this application.

[0164] Figure 10 This is a schematic block diagram of the device 1000 provided in the embodiments of this application.

[0165] Figure 11 This is a schematic block diagram of the device 1100 provided in the embodiments of this application.

[0166] Figure 12 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0167] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0168] The technical solutions of this application can be applied to various communication systems, such as Long Term Evolution (LTE) systems, Frequency Division Duplex (FDD) systems, Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or New Radio (NR) systems, 6th Generation (6G) systems or future communication systems, etc.

[0169] The 5G mobile communication system described in this application includes non-standalone (NSA) 5G mobile communication systems or standalone (SA) 5G mobile communication systems. The communication system can also be a public land mobile network (PLMN), a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT) communication system, a vehicle-to-everything (V2X) communication system, an unmanned aerial vehicle (UAV) communication system, or other communication systems.

[0170] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplarily" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0171] Furthermore, the network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0172] Figure 1 This application illustrates a network architecture to which embodiments of the present application are applicable, the network architecture including user equipment, access network, core network and data network.

[0173] 1. User Equipment (UE): This can be referred to as terminal equipment, terminal, access terminal, user unit, user station, mobile station, mobile station (MS), remote station, remote terminal, mobile device, mobile terminal (MT), user terminal, wireless communication equipment, user agent, or user device. Terminal equipment can also be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), computing device or other processing device connected to a wireless modem, in-vehicle equipment, drone, wearable device, terminal equipment in a 5G network, or terminal equipment in an evolved PLMN, etc., and this application embodiment is not limited thereto. Terminal equipment may also include handheld devices, in-vehicle equipment, wearable devices, or computing devices with wireless communication capabilities. For example, a UE can be a mobile phone, tablet computer, or computer with wireless transceiver capabilities. Terminal devices can also be virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, wireless terminals in autonomous driving, wireless terminals in telemedicine, wireless terminals in smart grids, wireless terminals in smart cities, wireless terminals in smart homes, and so on. Terminals can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminals can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc.

[0174] 2. Access Network (AN): Provides network access functionality for authorized user equipment in a specific area and can use transmission tunnels of different quality depending on the user equipment's level and service requirements. Access networks can employ different access technologies. Current access network technologies include: radio access network technologies used in 3G systems, radio access network technologies used in 4G systems, or next-generation radio access network (NG-RAN) technologies (such as those used in 5G systems).

[0175] An access network that implements access network functions based on wireless communication technology can be called a radio access network (RAN). A RAN manages radio resources, provides access services to terminals, and facilitates the forwarding of control signals and user data between terminals and the core network.

[0176] Wireless access network equipment can be, for example, a base station (NodeB), an evolved NodeB (eNB or eNodeB), a next-generation node base station (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access point (AP) in a Wi-Fi hotspot system. It can also be a wireless controller in a cloud radio access network (CRAN) scenario, or it can be a relay station, access point, vehicle-mounted equipment, drone, wearable device, or network equipment in a 5G network or an evolved PLMN. This application does not limit the specific technology or equipment form used in the wireless access network equipment.

[0177] 3. Core Network: This includes one or more of the following network elements: access management network elements, session management network elements, user plane network elements, policy control network elements, data management network elements, network open function network elements, etc. A brief introduction to the network elements in the core network is given below.

[0178] (1) Access Management Network Element: Primarily used for mobility management and access management, responsible for transmitting user policies between user equipment and policy control function (PCF) network elements, etc. It can be used to implement other functions in the mobility management entity (MME) function besides session management. For example, access authorization (authentication) function.

[0179] In 5G communication systems, the access management network element can be an access and mobility management function (AMF) network element. In future communication systems, the access management network element can still be an AMF network element, or it can have other names; this application does not limit this.

[0180] (2) Session management network element: mainly used for session management, allocation and management of Internet protocol (IP) addresses of user equipment, selection of endpoints for manageable user plane functions, policy control and charging function interfaces, and downlink data communication.

[0181] In 5G communication systems, the session management network element can be a session management function (SMF) network element. In future communication systems, the session management network element can still be an SMF network element, or it can have other names; this application does not limit this.

[0182] (3) User plane network elements: used for packet routing and forwarding, quality of service (QoS) processing of user plane data, completion of user plane data forwarding, session / flow-based billing statistics, bandwidth limiting functions, etc.

[0183] In 5G communication systems, user plane network elements can be user plane function (UPF) network elements. In future communication systems, user plane network elements can still be UPF network elements, or they can have other names; this application does not limit this.

[0184] (4) Policy control network element: a unified policy framework used to guide network behavior, providing policy rule information for control plane functional network elements (such as AMF, SMF, etc.).

[0185] In 4G communication systems, this policy control network element can be a policy and charging rules function (PCRF) network element. In 5G communication systems, this policy control network element can be a policy control function (PCF) network element. In future communication systems, this policy control network element can still be a PCF network element, or it can have other names; this application does not limit its scope.

[0186] (5) Data management network element: used to handle user equipment identification, access authentication, registration and mobility management, etc.

[0187] In 5G communication systems, this data management network element can be a unified data management (UDM) network element; in 4G communication systems, this data management network element can be a home subscriber server (HSS) network element. In future communication systems, the data management network element can still be a UDM network element, or it can have other names; this application does not limit this.

[0188] (6) Network Exposure Function (NEF) element: used to securely expose services and capabilities provided by the 3rd Generation Partnership Project (3GPP) network functions to the outside world.

[0189] 4. Various services can be deployed on the data network to provide data and / or voice services to user equipment, such as operator services, Internet access, and third-party services.

[0190] Figure 1The network architecture shown can also include application function (AF) network elements. AF network elements can provide certain application-layer services to user equipment. When providing services to user equipment, AF network elements have requirements for QoS and charging policies and need to notify the network. Simultaneously, AF network elements also need to obtain application-related information from the core network. An AF can possess all the functions of an AF network element as defined in the technical specification (TS) 23.501R-15, as well as related functions for application services. That is, in the user plane architecture, the application server and user equipment communicate via the UE-RAN-UPF-AF path. AF network elements can also communicate with other network elements in the core network in the control plane architecture through NEF network elements. For example, communicating with PCF network elements via NEF network elements. If the AF network element is deployed by the core network operator, then the AF network element can also communicate directly with other network elements in the core network in the control plane architecture, i.e., within the trusted domain, without going through NEF network elements, such as directly communicating with PCF network elements.

[0191] In addition to the network elements mentioned above, the network architecture may also include network slice selection function (NSSF) network elements, network repository function (NRF) network elements, authentication server function (AUSF) network elements, and other network elements. For the meanings of the above-mentioned NSSF network elements, NRF network elements, and AUSF network elements, please refer to relevant technologies.

[0192] It should be understood that the network architecture described above for the embodiments of this application is merely an example, and the network architecture applicable to the embodiments of this application is not limited thereto. Any network architecture capable of realizing the functions of the above-described network elements is applicable to the embodiments of this application.

[0193] It should also be understood that Figure 1 The AMF, SMF, UPF, NEF, PCF, UDM, etc. shown can be understood as network elements in the core network used to implement different functions, such as network slices that can be combined as needed. These core network elements can be independent devices or integrated into the same device to implement different functions. This application does not limit the specific form of the above network elements.

[0194] It should also be understood that the above naming is defined solely for the purpose of distinguishing different functions and should not constitute any limitation on this application. This application does not preclude the possibility of using other naming conventions in 5G networks and other future networks. For example, in 6G networks, some or all of the aforementioned network terminology may be retained from 5G, or other names may be used. Figure 1 The interface names between the various network elements are merely examples; in actual implementations, the interface names may differ, and this application does not impose any specific limitations on them. Furthermore, the names of the messages (or signaling) transmitted between the aforementioned network elements are also merely examples and do not constitute any limitation on the function of the messages themselves.

[0195] To ensure end-to-end service quality, 5G systems (e.g.) Figure 1 The system shown adopts a 5G QoS model based on QoS flow, such as... Figure 2 As shown, a terminal device can establish one or more PDU sessions with a 5G network, and each PDU session can establish one or more QoS flows.

[0196] Currently, in the forwarding process of traditional Ethernet networks, when a large number of data packets arrive at the forwarding port in an instant, it can cause significant packet forwarding delays or packet loss. Therefore, traditional Ethernet cannot provide highly reliable services with guaranteed transmission latency, failing to meet the needs of fields such as automotive control and the Industrial Internet. Against this backdrop, the Institute of Electrical and Electronics Engineers (IEEE) defined the Time-Sensitive Network (TSN) standard. This standard, based on Layer 2 switching, provides reliable latency-sensitive transmission services, ensuring the reliability of latency-sensitive business data transmission and predictable end-to-end transmission latency.

[0197] Figure 3 A fully centralized configuration model for a TSN is illustrated, comprising: a centralized user configuration (CUC) network element, a centralized network configuration (CNC) network element, and one or more TSN terminals (e.g., Figure 3 (the receiving end and the sending end in the middle), and one or more switching nodes (e.g., Figure 3 The network bridges (bridges) in this configuration model are as follows. The CUC and CNC network elements serve as the management plane of the TSN, while the TSN terminals and various switching nodes serve as the user plane. A brief introduction to the network elements and devices in this configuration model is provided below.

[0198] (1) CUC network element: used to manage TSN terminals and services. For example, the CUC network element can be used to discover and manage TSN terminals, obtain the capabilities of TSN terminals, send TSN stream requests to the CNC network element, and configure TSN terminals according to the instructions of the CNC network element.

[0199] TSN flows are service flows within a TSN network, and they can be identified by flow identifiers (e.g., stream identifiers, or stream IDs). For details on TSN flow requirements, or TSN flow requirement information, please refer to the following description.

[0200] (2) CNC network element: It can be used to manage the topology of TSN user plane and the capability information of each switching node, calculate and generate end-to-end (E2E) forwarding path of TSN flow according to the requirements of TSN flow, and send scheduling parameters to each switching node.

[0201] (3) Switching Node: This node can be used to report its capability and topology information to the CNC network element and to schedule and forward TSN flows based on rules issued by the CNC network element. This application does not limit the specific type of switching node; for example, a switching node can be a bridge, a switch, or a router. The following explanation will use a bridge as an example of a switching node.

[0202] (4) Sender: This is the data sender. In this configuration model, there can be one or more senders. The sender can also be called the initiator, stream service provider, or talker, etc., and will be referred to as the sender in the following text.

[0203] (5) Receiver: This is the data receiver. In this configuration model, there can be one or more receivers. The receiver can also be called a listener, stream service receiver, or listener, etc., and will be referred to as the receiver in the following text.

[0204] It should be noted that the sending end and receiving end here can refer to communication devices.

[0205] The aforementioned CUC network elements, CNC network elements, switching nodes, and TSN terminals can exchange information. For example, CUC network elements and CNC network elements can exchange TSN flow configuration information, such as user configuration information and / or network configuration information. This TSN flow user configuration information and / or network configuration information can include multiple group information, such as talker group information, listener group information, and status group information. The talker group information can include information received by the CUC network element from the talker. The listener group information can include information received by the CUC network element from the listener. In this embodiment, both the talker group information and the listener group information can be referred to as TSN flow requirement information. The status group information can be referred to as TSN flow status information, and the status group information can include information sent by the CNC network element to the CUC network element, used by the CUC network element to determine the configuration status of the TSN flow sent to the talker / listener.

[0206] The TSN flow requirements include one or more of the following: flow identifier (e.g., stream ID), flow class (e.g., StreamRank), end station interface (e.g., EndStationInterfaces), data frame definition (e.g., DataFrameSpecification), traffic description (e.g., TrafficSpecification), user network requirements (e.g., UserToNetworkRequirements), interface capabilities, etc. Traffic descriptions include one or more of the following: interval (e.g., Interval), maximum number of frames per interval (e.g., MaxFramesPerInterval), maximum frame size (e.g., MaxFrameSize), transmission selection (e.g., TransmissionSelection), earliest transmission offset (e.g., EarliestTransmitOffset), latest transmission offset (e.g., LatestTransmitOffset), and jitter (e.g., Jitter). User network requirements include one or more of the following: number of redundant paths (e.g., NumSeamlessTrees) and maximum latency (e.g., Maxlatency).

[0207] The status information of a TSN stream includes one or more of the following: stream identifier (e.g., Stream ID), status information (e.g., StatusInfo), accumulated latency (e.g., AccumulatedLatency), interface configuration (e.g., InterfaceConfiguration), failed interfaces (e.g., FailedInterfaces), etc.

[0208] Figure 4 A schematic diagram of a system architecture for 3GPP and TSN interoperability is shown. Figure 4 In the system architecture shown, the 3GPP 5G system and the TSN (time-sensitive network translator, TT) can be integrated as a logical TSN bridge (e.g., Figure 3 The bridge shown allows the 5G system to exchange information with other nodes in the TSN network via TSN TT, such as 5G system Bridge capability information, TSN configuration information, TSN input / output port time scheduling information, time synchronization information, etc. TSN TT includes device-side TT (DS-TT) and network-side TT (NW-TT). DS-TT can be considered as the UE-side TT, which can be located inside or outside the UE; NW-TT can be considered as the UPF-side TT, which can be located inside the UPF. It should be understood that... Figure 4 The 3GPP 5G system architecture shown is merely an example; other architecture models are also possible for the 3GPP 5G system, which will not be described in detail in this application.

[0209] like Figure 4As shown, the TSN system can interact with the TSN AF in the 5G system via control plane signaling. The TSN system can also transmit data packets (or messages, data frames) in the TSN stream through the user plane of the 5G system. For example, when the RAN and UPF network elements support TSN end station capabilities, the RAN and UPF network elements can act as the sender and receiver of the TSN stream, respectively; that is, the RAN acts as the access network talker / listener (AN-TL), and the UPF acts as the core network talker / listener (CN-TL). For instance, in the uplink direction, the RAN acts as the sender of the TSN stream, and the UPF network element acts as the receiver of the TSN stream; in the downlink direction, the UPF network element acts as the sender of the TSN stream, and the RAN acts as the receiver of the TSN stream. Control plane network elements in the 5G system (e.g., SMF network elements) can act as CUC network elements in the TSN network. In this application, an SMF network element configured as a CUC network element in the TSN network can be represented as SMF / CUC.

[0210] For example, assuming the SMF network element acts as the CNC network element in the TSN, the RAN acts as the transmitter, and the UPF network element acts as the receiver, the SMF network element can receive transmitter group information and receiver group information (referred to as TSN flow requirement information in this application) from the RAN and UPF network elements respectively. It then sends the TSN flow requirement information to the CNC network element through the user network interface (UNI). The CNC network element uses the TSN flow requirement information to configure the bridge and sends the status group information to the SMF network element. The SMF network element can configure the transmitter and receiver according to the status group information, that is, the SMF network element configures the RAN and UPF network elements according to the status group information.

[0211] With the rapid growth in demand for communication services, the amount of latency-sensitive service data is also increasing. Improving the transmission efficiency of latency-sensitive service data within a 3GPP and TSN interoperability system architecture has become a hot research topic for those skilled in the art.

[0212] This application provides a communication method that can improve the transmission efficiency of latency-sensitive service data in a system architecture that interoperates with 3GPP and TSN.

[0213] The following is combined Figures 5 to 8 The present application provides an exemplary embodiment of the communication method.

[0214] It should be noted that the time-sensitive network involved in this application is not limited to a TSN network, but can also be a non-TSN TSC service, and the method of this application is equally applicable. The time-sensitive network in the embodiments of this application takes a TSN network as an example to describe the communication method provided in this application in detail, and does not have any limiting effect on the method provided in the embodiments of this application.

[0215] It should also be noted that, Figure 5 or Figure 8 RAN in the text can be Figure 1 The example of the access network device, UPF, can be... Figure 1 The example of the user plane network element described herein, PCF can be Figure 1 Examples of the policy control network elements described herein. Furthermore, it is understood that the methods described in this application are not only applicable to 5G communication systems, but can also be used in other types of communication systems; however, these methods will not be elaborated further in the embodiments of this application.

[0216] Figure 5 This is a schematic flowchart of a communication method provided in an embodiment of this application.

[0217] 501. CUC determines the demand information of a TSN flow based on the characteristic information of multiple QoS flows.

[0218] For example, CUC treats the multiple QoS flows as a single TSN flow and determines the demand information of that single TSN flow based on the characteristic information of the multiple QoS flows. Here, the single TSN flow corresponds to the multiple QoS flows.

[0219] Before the CUC determines the demand information of a TSN flow based on the characteristic information of multiple QoS flows, the communication method also includes: the CUC acquiring the characteristic information of the multiple QoS flows. For example, the CUC can acquire the characteristic information of the multiple QoS flows in one of the following ways.

[0220] Method 1: In scenarios where the SMF network element is configured as a CUC, the SMF can establish multiple QoS flows based on the session establishment request of the terminal device. When establishing these multiple QoS flows, the SMF determines the characteristic information of these multiple QoS flows based on relevant parameters (e.g., the session establishment request information of the terminal device, the policy and charging control (PCC) rules of the PCF). The characteristic information of these multiple QoS flows includes parameters such as the transmission period of these multiple QoS flows.

[0221] Method 2: Before step 501, the CUC receives the feature information of the multiple QoS flows sent from the RAN and UPF. The feature information of the multiple QoS flows includes parameters such as the transmission period of the multiple QoS flows.

[0222] In one possible implementation, the multiple QoS flows satisfy the aggregation condition, and CUC treats these multiple QoS flows as a single TSN flow.

[0223] The aggregation conditions include one or more of the following:

[0224] (1) The sessions to which these multiple QoS flows belong correspond to the same CUC;

[0225] As an example, in a scenario where the SMF network element is configured as a CUC, the sessions to which these multiple QoS flows belong correspond to the same CUC; in other words, the sessions to which these multiple QoS flows belong correspond to the same SMF network element. The SMF network element establishes and manages the sessions to which these multiple QoS flows belong. These multiple QoS flows can belong to the same session or different sessions; this application does not impose any restrictions on this.

[0226] (2) The transmission periods of these multiple QoS flows are the same or are multiples of each other;

[0227] (3) The CN PDBs corresponding to these multiple QoS flows are the same;

[0228] (4) The multiple QoS flows arrive at the sending end corresponding to the multiple QoS flows at the same time;

[0229] As an example, if it is an uplink QoS flow, that is, TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB are the same; if it is a downlink QoS flow, that is, TSCAC BAT in DL direction are the same.

[0230] As another example, the RAN can adjust the TSCAI BAT corresponding to each of the multiple QoS flows to ensure that the arrival times of the multiple QoS flows at their respective transmitters are the same. For example, the TSCAC received by the CUC also includes a TSCAC BAT window, which represents the earliest and latest times when the first data packet in a data burst arrives at the 5G system ingress in a given traffic direction. Specifically, when the traffic direction is uplink, the 5G system ingress is DS-TT; when the traffic direction is downlink, the 5G system ingress is NW-TT. The CUC network element determines the TSCAI BAT window based on the TSCAC BAT window and sends the TSCAI BAT window, carried in the TSCAI, to the RAN. After receiving the TSCAI, the RAN determines the TSCAI BAT offset based on the TSCAI BAT window and feeds this offset back to the CUC. For example, when the TSCAI received by the RAN includes capability information indicating that the QoS flow corresponding to the TSCAI supports adjusting the BAT, the RAN can also determine the offset of the TSCAI BAT based on the capability information and feed the offset back to the CUC.

[0231] The CUC then instructs the application (e.g., AF) to adjust the packet transmission time based on the offset fed back by the RAN, thereby ensuring that the multiple QoS flows arrive at the transmitter at the same time. The specific value of this BAT offset can be positive or negative.

[0232] It should also be understood that the UPF can also adjust the BAT in the same way as the RAN to make the multiple QoS Flows arrive at the sending end at the same time. The specific implementation method will not be elaborated here.

[0233] (5) The ARP values ​​of the multiple QoS flows are all within the preset range, for example, the ARP values ​​are in the range of 1-8, or the ARP values ​​of the multiple QoS flows are all outside the preset range, for example, the ARP values ​​are outside the range of 1-8.

[0234] It should be understood that CUC can map multiple QoS flows that meet the above aggregation conditions to a single TSN flow based on the above aggregation conditions, and determine the demand information of the single TSN flow based on the characteristic information of the multiple QoS flows.

[0235] In another possible implementation, the CUC can also determine the demand information of a single TSN flow based on the received information indicating that the multiple QoS flows are regarded as the same TSN flow, and then determine the demand information of the single TSN flow based on the characteristic information of the multiple QoS flows.

[0236] For example, before the CUC determines the demand information of the TSN flow based on the characteristic information of multiple QoS flows, the CUC receives indication information from the sender corresponding to the multiple QoS flows. This indication information is used to instruct the CUC to regard the multiple QoS flows as the same TSN flow.

[0237] For example, if the senders corresponding to the multiple QoS flows are the same sender, and this sender determines that the multiple QoS flows are considered as a single TSN flow, then the senders corresponding to the multiple QoS flows send indication information to the CUC. This indication information indicates that the multiple QoS flows are associated with a single TSN flow. Accordingly, the CUC receives the indication information from the senders corresponding to the multiple QoS flows and determines the demand information for a single TSN flow based on the characteristic information of the multiple QoS flows.

[0238] Optionally, the sending end corresponding to the multiple QoS flows can determine the multiple QoS flows that arrive at the sending end corresponding to the multiple QoS flows within the same transmission time interval (TTI) as the same TSN flow for processing. In other words, the indication information is used to indicate the multiple QoS flows that arrive at the sending end of the multiple QoS flows within the same TTI.

[0239] In another possible implementation, the CUC can also map multiple QoS flows carrying the same aggregation ID to a single TSN flow, and determine the demand information of a TSN flow based on the characteristic information of the multiple QoS flows. For example, before the CUC determines the demand information of a TSN flow based on the characteristic information of the multiple QoS flows, the CUC receives the aggregation ID corresponding to each of the multiple QoS flows, and then maps the multiple QoS flows carrying the same aggregation ID to a single TSN flow.

[0240] For example, the senders corresponding to the multiple QoS flows determine that these multiple QoS flows are considered as the same TSN flow and assign the same aggregation identifier to these multiple QoS flows. Then, the senders send the aggregation identifiers corresponding to the multiple QoS flows to the CUC. For example, the senders send the correspondence between the identifiers (QoS flowidentifiers, QFIs) of the multiple QoS flows and the aggregation identifiers to the CUC. Alternatively, when sending the feature information of a QoS flow to the CUC, the senders send the aggregation identifier of the QoS flow to the CUC; optionally, the feature information of the QoS flow includes the aggregation identifier of the QoS flow. Optionally, the senders corresponding to the multiple QoS flows may carry the aggregation identifier with the QoS flows arriving at the senders corresponding to the multiple QoS flows within the same TTI. In other words, the multiple QoS flows carrying the aggregation identifier are the QoS flows arriving at the senders of the multiple QoS flows within the same TTI.

[0241] It should also be understood that CUC determines the demand information of a TSN flow based on the characteristic information of multiple QoS flows. The demand information of a TSN flow may include one or more of the following parameters: TSN flow identifier (e.g., TSN Stream ID), interval (e.g., Interval), latest transmission offset (e.g., LatestTransmitOffset), earliest transmission offset (e.g., EarliestTransmitOffset), maximum frame length (e.g., MaxFrameSize), maximum number of frames per interval (e.g., MaxFramesPerInterval), maximum allowed latency for the TSN flow (e.g., MaxLatency), and number of redundant paths (e.g., NumSeamlessTrees). The following is an illustrative description of these parameters:

[0242] 1) TSN Stream Identifier: For example, the stream identifier may include two fields: a medium access control (MAC) address (MACAddress) and a unique identifier (UniqueID). The MAC address is the MAC address of the sender of the TSN stream, and the unique identifier is used to distinguish different streams sent by the same sender.

[0243] As an example, CUC assigns the same TSN flow identifier to multiple QoS flows.

[0244] 2) Interval: Used to indicate the period of the TSN stream, also known as the time interval. The interval can be a rational number of seconds, defined by an unsigned 32-bit integer numerator and an unsigned 32-bit integer denominator, i.e., it can be less than a second.

[0245] As an example, the interval is the least common multiple of the transmission periods of the multiple QoS flows.

[0246] For example, suppose that the unit of periodicity is seconds (s), the unit of interval is also seconds (s), the multiple QoS flows include QoS flow#1, QoS flow#2 and QoS flow#3, the periodicity corresponding to QoS flow#1 is 1s, the periodicity corresponding to QoS flow#2 is 3s, the periodicity corresponding to QoS flow#3 is 5s, and the interval in the TSN flow demand information is taken as the least common multiple of {1s, 3s, 5s}, which is 15s.

[0247] It should be understood that the interval in this application is exemplarily given in units of s, and the interval may take other values ​​or other units, which are not limited in this application.

[0248] As an example, when multiple QoS flows have the same periodicity, the interval can be set to the periodicity of any one of the QoS flows. For instance, if the multiple QoS flows include QoS flow#1, QoS flow#2, and QoS flow#3, the periodicity of all three is 1 second. The interval in the TSN flow's demand information can be any value of 1 second from {1 second, 1 second, 1 second}.

[0249] As another example, when the periods corresponding to multiple QoS flows are multiples of each other, the interval can also be set to the maximum value of the periods corresponding to the multiple QoS flows. For example, the multiple QoS flows include QoS flow#1, QoS flow#2, and QoS flow#3. The period corresponding to QoS flow#1 is 1s, the period corresponding to QoS flow#2 is 2s, and the period corresponding to QoS flow#3 is 4s. The interval in the TSN flow demand information is the maximum value of 4s among {1s, 2s, 4s}.

[0250] 3) Maximum frame length: The maximum length of a data frame in a TSN stream.

[0251] As an example, the maximum frame length is determined based on the sum of the maximum data burst sizes of the plurality of QoS flows, or the maximum frame length is determined based on the sum of the maximum data burst lengths of the plurality of QoS flows.

[0252] The maximum data burst size represents the maximum amount of data transmitted within the AN PDB. The AN PDB (or 5G-AN PDB) defines the upper limit of the possible delay of data packets between the UE and the RAN.

[0253] For example, suppose the multiple QoS flows include QoS flow#1, QoS flow#2, and QoS flow#3. The MDBV value corresponding to QoS flow#1 is x1, the MDBV value corresponding to QoS flow#2 is x2, and the MDBV value corresponding to QoS flow#3 is x3. Then the maximum frame length is x1 + x2 + x3.

[0254] For example, suppose the multiple QoS flows include QoS flow#1, QoS flow#2, and QoS flow#3. The maximum data burst length corresponding to QoS flow#1 is y1, the maximum data burst length corresponding to QoS flow#2 is y2, and the maximum data burst length corresponding to QoS flow#3 is y3. Then the maximum frame length is y1 + y2 + y3.

[0255] Optionally, the maximum frame length can also be determined based on the number of framing bits not used for transmission. These framing bits may include cyclic redundancy check (CRC) bits and General Packet Radio Service Tunneling Protocol (GTP-U) tunnel headers, etc. For example, it can be the sum of the maximum data burst sizes of the multiple QoS flows minus the number of framing bits not used for transmission in the multiple QoS flows, or the sum of the maximum data burst lengths of the multiple QoS flows minus the number of framing bits not used for transmission in the multiple QoS flows.

[0256] 4) Maximum number of frames per period, or maximum number of frames per interval (e.g., MaxFramesPerInterval): This indicates the maximum number of data frames that the sender of the TSN stream can send within an interval.

[0257] As an example, the maximum number of frames per period is the sum of the number of data frames transmitted by the multiple QoS flows within an interval, which is the least common multiple of the transmission periods of the multiple QoS flows.

[0258] The method for determining the intervals corresponding to these multiple QoS flows is as shown in 2) above, and will not be repeated here.

[0259] For example, these multiple QoS flows include QoS flow#1, QoS flow#2, and QoS flow#3, and the interval in the demand information of a single TSN flow corresponding to these multiple QoS flows is 1 second. The number of data frames transmitted by QoS flow#1 within this 1-second interval is D1, the number of data frames transmitted by QoS flow#2 within this interval is D2, and the number of data frames transmitted by QoS flow#3 within this interval is D3. Therefore, the maximum number of frames per period = D1 + D2 + D3. Where D1, D2, and D3 are all positive integers.

[0260] 5) Earliest Transmission Offset: This indicates the maximum value of the time when the sender corresponding to the multiple QoS flows began transmitting the data frames for those multiple QoS flows earlier than the start time of the interval. The earliest transmission offset is a signed integer, and the unit can be ns.

[0261] As an example, the multiple QoS flows arrive at the sender at the same time, and the earliest transmission offset is determined based on the arrival time of any one of the multiple QoS flows at the sender.

[0262] As another example, multiple QoS flows arrive at the sender at different times, and the earliest transmission offset is determined based on the earliest time of arrival of these multiple QoS flows at the sender.

[0263] For example, if the multiple QoS flows arrive at the transmitter at the same time: if the QoS flow is an uplink QoS flow (i.e., TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB are the same); or if the QoS flow is a downlink QoS flow (i.e., TSCAC BAT in DL direction are the same), the CUC determines the earliest transmission offset based on the arrival time of any one of these multiple QoS flows.

[0264] Wherein, the earliest transmission offset = TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB - M * interval. M is an integer, and it is guaranteed that TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB > -M * interval. TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB represents the TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB corresponding to any one of the multiple QoS flows.

[0265] For example, if the multiple QoS flows arrive at the sender at different times: The CUC selects the earliest arrival time among these multiple QoS flows to determine the earliest transmission offset. If the QoS flow is an uplink QoS flow, the earliest arrival time at the sender is determined by the minimum value of the TSCAC BAT in the UL direction + UE-DS-TT Residence Time + 5G-AN PDB corresponding to these multiple QoS flows. If the QoS flow is a downlink QoS flow, the earliest arrival time at the sender is determined by the minimum value of the TSCAC BAT in the DL direction corresponding to these multiple QoS flows.

[0266] The earliest transmission offset is defined as (TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB)min - M * interval. M is an integer, and it is guaranteed that (TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB)min > 5G-AN PDB - M * interval. (TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB)min represents the minimum value of TSCAC BAT in UL direction + UE-DS-TT Residence Time + 5G-AN PDB corresponding to these multiple QoS flows.

[0267] Wherein, TSCAC BAT in UL direction represents the uplink burst arrival time (BAT) of the time-sensitive communication assistance container (TSCAC), used to indicate the time when the TSN stream arrives at the 5G system entry point, that is, the time when the TSN stream arrives at the NW-TT entry point in the downlink direction, such as... Figure 6 The downlink burst time (e.g., DL burst arrival time) is shown; the time when the uplink TSN flow arrives at the DS-TT inlet is shown. Figure 7 The uplink burst arrival time (e.g., UL burst arrival time) is considered. For example, the SMF / CUC obtains the TSCAC from the TSN AF network element through the PCF network element, which includes the TSCAC BAT in the UL direction. This TSCAC can also be sent from the AF or the time-sensitive communication and time synchronization function (TSCTSF) network element to the SMF network element through the PCF network element; this application does not specifically limit this.

[0268] The UE-DS-TT residence time indicates the time difference between the time the DS-TT receives the data frame and the time the UE sends the data frame in the uplink direction. The AN PDB (or 5G-AN PDB) defines the upper limit of the possible delay of data packets between the UE and the RAN.

[0269] 6) Latest Transmission Offset: The latest transmission offset represents the maximum value of the interval's start time after which the sender corresponding to the multiple QoS flows begins transmitting the data frames for those multiple QoS flows. The latest transmission offset is a signed integer, and the unit can be ns.

[0270] As an example, the latest transmission offset is determined based on the interval and the maximum frame length.

[0271] For example, the latest transmission offset = the earliest transmission offset + the interval - (jitter + maximum frame length). The method for determining the earliest transmission offset can be found in section 5) above, the method for determining the interval can be found in section 2) above, and the method for determining the maximum frame length can be found in section 3) above.

[0272] 7) Maximum allowed latency for TSN streams: The maximum latency for data frames of the multiple QoS flows from the sending end corresponding to the multiple QoS flows to the receiving end corresponding to the multiple QoS flows. The maximum allowed latency for TSN streams is a signed integer, and the unit can be ns.

[0273] As an example, if the maximum buffer duration of these multiple QoS flows is the same, the maximum allowed latency of the TSN flow is determined based on the maximum buffer duration of any one of these QoS flows at the sending end. That is, the maximum buffer duration.

[0274] =LatestTransmitOffset - EarliestTransmitOffset, where LatestTransmitOffset and EarliestTransmitOffset are obtained using the methods described in 6) and 5) above.

[0275] As another example, the maximum buffer durations of these multiple QoS flows differ, and the maximum allowed latency for a TSN flow is determined based on the maximum value among the maximum buffer durations of these multiple QoS flows. The maximum buffer duration is the maximum duration for which the sender buffers data frames from multiple QoS flows.

[0276] For example, assuming that the multiple QoS flows have the same CN PDB, when determining the maximum latency of the TSN flow, the CN PDB of any one of the multiple QoS flows is selected, minus the maximum buffer duration for which the sender may buffer data frames of multiple QoS flows.

[0277] 8) Redundant path count: Indicates whether the sender of multiple QoS flows needs to send the data frames of the multiple QoS flows to the receiver of the multiple QoS flows through multiple user plane paths.

[0278] As an example, the number of redundant paths is determined based on whether multiple QoS flows include QoS flows that require redundant transmission.

[0279] The number of redundant paths can be used to indicate whether the network device needs to provide redundant paths for the multiple QoS flows; or, the number of redundant paths can also be used to indicate whether the sender corresponding to the multiple QoS flows needs to send the data frames of the multiple QoS flows to the receiver of the multiple QoS flows through multiple user plane paths.

[0280] For example, if each of the multiple QoS flows does not require redundant transmission, the number of redundant paths takes the first value, such as 1; if one or more of the multiple QoS flows require redundant transmission, the number of redundant paths takes the second value or any value other than the first value, such as 2, 3, 4, etc.

[0281] When one or more QoS flows among the multiple QoS flows require redundant transmission, the number of redundant paths can also be used to indicate the number of redundant paths. For example, if none of the multiple QoS flows require redundant transmission, the number of redundant paths takes the first value, such as 1; if one of the multiple QoS flows requires redundant transmission, the number of redundant paths takes the third value, such as 2; if two of the multiple QoS flows require redundant transmission, the number of redundant paths takes the fourth value, such as 3, and so on.

[0282] 9) Flow Class: Indicates the class of these QoS flows relative to other QoS flows in the network. This flow class is used to determine the priority of resource allocation for these QoS flows.

[0283] As an example, if the ARP values ​​of multiple QoS flows are all within a preset range, such as ARP values ​​being between 1 and 8, then the flow level is set to the fifth value, such as 0; if the ARP values ​​of multiple QoS flows are not within the preset range, such as ARP values ​​not being between 1 and 8, then the flow level is set to the sixth value, such as 1.

[0284] It should be understood that 1) to 9) above exemplarily describe how to determine the specific parameters in the requirement information of a single TSN flow when multiple QoS flows are considered as a single TSN flow. The requirement information of a TSN flow may also include other parameters, such as data frame definitions (e.g., DataFrameSpecification), interface capabilities (e.g., InterfaceCapabilities), jitter, etc. Those skilled in the art can determine other parameters in the requirement information of other TSN flows based on the method provided in this application and in conjunction with existing technology; these will not be listed individually in this application.

[0285] Optionally, prior to step 501 above, the method may further include:

[0286] The terminal device triggers the session establishment process, and the CUC receives PCC rules from the PCF network element. The CUC establishes multiple QoS flows based on the PCC rules and sends the corresponding information for these QoS flows (e.g., QoS flow parameters such as QFI, ARP, etc.) to the RAN and UPF. See below for details. Figure 8 Detailed introduction in the text.

[0287] Optionally, prior to step 501 above, the method may further include:

[0288] The CUC receives group information from the RAN and UPF.

[0289] It should be understood that when the RAN acts as the transmitter and the UPF as the receiver, the group information sent by the RAN to the CUC can be called transmitter group information, and the group information sent by the UPF to the CUC can be called receiver group information. Similarly, when the RAN acts as the receiver and the UPF acts as the transmitter, the group information sent by the RAN to the CUC can be called receiver group information, and the group information sent by the UPF to the CUC can be called transmitter group information. Both receiver group information and transmitter group information can be referred to as TSN flow demand information. For details on TSN flow demand information, please refer to the above. Figure 3 Detailed introduction in the text.

[0290] It should also be understood that the CUC can determine, based on the group information of the RAN and UPF, that multiple QoS flows corresponding to the group information of the RAN and UPF are considered as the same TSN flow. For example, if the multiple QoS flows corresponding to the group information sent by the RAN and UPF to the CUC satisfy the above aggregation conditions, that is, the CUC can consider the multiple QoS flows as a single TSN flow and determine the demand information of the TSN flow based on the characteristic information of the multiple QoS flows.

[0291] 502, CUC sends TSN stream request information to CNC.

[0292] For example, the CUC determines the demand information of a TSN flow based on the characteristic information of the multiple QoS flows, and sends the demand information of a TSN flow corresponding to the multiple QoS flows to the CNC.

[0293] Accordingly, the CNC receives demand information from the TSN stream of the CUC.

[0294] 503, CNC sends TSN stream status information to CUC.

[0295] For example, after receiving the demand information of a TSN stream, the CNC determines the status information of the TSN stream based on the demand information and sends the status information of the TSN stream to the CUC.

[0296] Accordingly, the CUC receives status information from the TSN stream of the CNC.

[0297] It should be understood that the status information of a TSN flow may include information sent by the CNC to the CUC, which is used by the CUC to determine the configuration status of the TSN flow sent to the sender and receiver of the multiple QoS Flows.

[0298] The status information of a TSN stream, or the status group information, may include one or more of the following parameters: stream identifier, status information (e.g., StatusInfo), accumulated latency (e.g., AccumulatedLatency), interface configuration (e.g., InterfaceConfiguration), or failed interfaces (e.g., FailedInterfaces).

[0299] The interface configuration may include a time-aware offset (e.g., TimeAwareOffset). For example, the status information of the TSN stream sent by the CNC to the CUC includes interface configuration information, which includes the time-aware offset. Further, the CUC sends this time-aware offset received from the CNC to the AN-TL port (for TSN streams in the UL direction) or the CN-TL port (for TSN streams in the DL direction). The AN-TL or CN-TL buffers the transmitted TSN stream data at the time indicated by the time-aware offset and then transmits it.

[0300] 504, CUC sends information to the senders and receivers corresponding to the multiple QoS flows to configure them. This information can be referred to as configuration information.

[0301] Accordingly, the sending and receiving ends corresponding to these multiple QoS flows receive the configuration information from CUC.

[0302] For example, the CUC receives status information from the TSN stream from the CNC, and the CUC determines the configuration information based on the status information of the TSN stream.

[0303] It should be understood that this configuration information includes information and port identifiers for configuring the sender and receiver corresponding to multiple QoS flows. The port identifier is used to identify the port number on which the sender and receiver corresponding to the multiple QoS flows transmit the single TSN flow, or it can be used to identify the port numbers of the sender and receiver corresponding to the multiple QoS flows corresponding to the single TSN flow. In other words, the sender and receiver corresponding to the multiple QoS flows transmit the multiple QoS flows corresponding to the single TSN flow on the same port.

[0304] Optionally, the configuration information may also include information for the sending end corresponding to the multiple QoS flows to adjust the transmission time of the data frames of the multiple QoS flows.

[0305] The sending and receiving ends corresponding to multiple QoS flows are adjusted according to the transmission time of the data frames of these multiple QoS flows in the configuration information, thereby further ensuring the transmission performance of the system.

[0306] Optionally, the configuration information may also include the identifiers of the multiple QoS flows.

[0307] Specifically, the sending and receiving ends corresponding to multiple QoS flows determine which QoS flows to schedule using the configuration information based on the identifiers of these multiple QoS flows in the configuration information. This ensures that the sending and receiving ends of these multiple QoS flows use the configuration information corresponding to the identifiers of these multiple QoS flows to schedule the data frames of the specific QoS flows, thereby improving transmission performance.

[0308] Optionally, the configuration information includes the identification information of the TSN flow. Before or during step 504, the CUC also sends the correspondence between the TSN flow and the multiple QoS flows to the sending and receiving ends corresponding to the multiple QoS flows.

[0309] After receiving the CUC configuration information, the sending and receiving ends corresponding to the multiple QoS flows determine which QoS flows correspond to the same TSN flow based on the correspondence between a TSN flow and multiple QoS flows in the configuration information, as well as the identification information of the TSN flow. The sending and receiving ends corresponding to the multiple QoS flows then schedule the multiple QoS flows corresponding to that TSN flow according to the configuration information. Specifically, the sending and receiving ends corresponding to the multiple QoS flows can schedule the transmission time of the data frames corresponding to the multiple QoS flows, as well as other relevant information (e.g., the port numbers of the sending and receiving ends corresponding to the multiple QoS flows), based on the configuration information. Finally, the multiple QoS flows are transmitted on the same port of the sending and receiving ends corresponding to the multiple QoS flows.

[0310] according to Figure 5 The method shown treats multiple QoS flows as a single TSN flow and determines the requirement information of this single TSN flow based on the characteristic information of the multiple QoS flows. The CNC then determines the status information of this single TSN flow based on its requirement information. The CNC determines configuration information based on the status information of this single TSN flow. This configuration information is used to configure the ports used by the sending and receiving ends corresponding to the multiple QoS flows to transmit this single TSN flow. By using the same port to transmit the multiple QoS flows corresponding to this single TSN flow, the number of QoS flows that can be transmitted can be increased when the number of sending and receiving ends corresponding to the multiple QoS flows is limited. That is, one port can transmit multiple QoS flows, improving the transmission efficiency of latency-sensitive service data. Furthermore, when the number of transmitted QoS flows is limited, the number of ports required by network devices can be reduced. By treating multiple QoS flows as a single TSN flow, meaning that multiple QoS flows can be transmitted on the same port, the number of ports required by network devices can be significantly reduced.

[0311] The following will combine Figure 8 Taking SMF as the CUC as an example, the following is a detailed explanation. Figure 5 The detailed configuration process is shown below. Figure 8 This is a schematic flowchart of another communication method provided in this application.

[0312] 801, The terminal device triggers the PDU session establishment process.

[0313] The PDU session establishment process can be referred to in section 4.3.2 of 3GPP TS23.502. For the sake of brevity, this embodiment will not be described in detail.

[0314] If the RAN supports TL functionality, during the PDU session establishment process, the RAN can send (e.g., report via a transparent container) its interface capabilities to the SMF. RAN support for TL functionality indicates that the RAN can act as a sender or receiver of TSN flows, i.e., AN-TL.

[0315] If the UPF supports TL functionality, then during the PDU session establishment process, the UPF can send (e.g., report via a transparent container) its interface capabilities to the SMF. UPF support for TL functionality indicates that the UPF can act as a sender or receiver of TSN streams, i.e., CN-TL.

[0316] Specifically, the RAN and UPF report their interface capabilities to the SMF, and these interface capabilities are related to the above. Figure 3 The interface capabilities described herein are similar. These capabilities may also include: Virtual LAN tagging capabilities (e.g., VLANTagCapable), supported flow identifier types (e.g., StreamIdenTypeList), and supported sequence encoding and decoding types (e.g., SequenceEncode / DecodeTypeList). The Virtual LAN tagging capability defines whether the sender supports adding or deleting VLAN tags. Supported flow identifier types define the flow identifier types supported by the sender. Supported sequence encoding and decoding types define the frame duplication and deduplication sequence encoding and decoding types supported by the sender.

[0317] 802, SMF receives PCC rules from PCF network elements.

[0318] Accordingly, the PCF network element sends PCC rules to the SMF network element.

[0319] It should be understood that when a terminal device triggers the establishment of a PDU session, the SMF establishes multiple QoS flows. The SMF can establish multiple QoS flows based on the PCC rules from the PCF. The following explanation uses the establishment of X QoS flows as an example, where X is an integer greater than 1. The PCC rules include TSCAC, which can include one or more of the following parameters: the direction of the TSN flow, the burst size of the TSN flow, the period of the TSN flow, the amount of data within the period, the time information of the data frame arriving at the 5G system, etc. Please refer to the above for details. Figure 5 Detailed introduction of step 501.

[0320] The SMF establishes the multiple QoS flows. The SMF can establish the multiple QoS flows during the PDU session establishment process, or the SMF can establish the multiple QoS flows during the PDU session modification process. This application does not make specific limitations on this.

[0321] It should also be understood that the SMF establishes X QoS flows based on the PCC rules sent by the PCF network element, and sends the information corresponding to these X QoS flows to the RAN and UPF.

[0322] 803, SMF executes parameter mapping to obtain the TSN stream requirement information.

[0323] SMF parameter mapping refers to the following: the SMF determines the TSN flow requirement information based on the information reported by the sending end and the receiving end; or, the SMF establishes multiple QoS flows according to step 802 and determines the characteristic information of these multiple QoS flows, and the SMF determines the TSN flow requirement information through the characteristic information of these multiple QoS flows. The TSN flow requirement information can also be referred to as merged stream requirements.

[0324] It should be understood that the demand information for TSN flows is determined based on the group information of the sending end (e.g., group information received by the SMF from the RAN / UPF) and the group information of the receiving end (e.g., group information received by the SMF from the UPF / RAN). The group information of the sending end and the receiving end can be determined based on the characteristic information of the X QoS flows. For example, the group information of the sending end and the group information of the receiving end can be the characteristic information of the X QoS flows.

[0325] It should also be understood that SMF treats these X QoS flows as a single TSN flow and determines the demand information for that TSN flow. For example... Figure 8 The TSN flow in the method shown refers to the same TSN flow. Specifically, the X QoS flows correspond to the same sender and the same receiver. It can be understood that the demand information for the TSN flow corresponding to these X QoS flows is the same.

[0326] In one possible implementation, the X QoS flows satisfy the aggregation condition, as described above. Figure 5In step 501, under any of the aggregation conditions 1) to 5), the SMF considers the X QoS flows that satisfy the aggregation conditions as the same TSN flow and determines the demand information of the TSN flow based on the characteristic information of the X QoS flows; or, before the SMF determines the demand information of the TSN flow, the CUC receives indication information from the sender (e.g., RAN or UPF) corresponding to the multiple QoS flows. This indication information is used to indicate that the X QoS flows are considered as the same TSN flow, and the SMF determines the demand information of the TSN flow based on the characteristic information of the X QoS flows according to the indication information; or, the sender (e.g., RAN or UPF) corresponding to the multiple QoS flows sends an aggregation identifier to the SMF. Based on the aggregation identifier, the SMF considers the QoS flows carrying the aggregation identifier (e.g., X QoS flows) among the multiple QoS flows as the same TSN flow, and the SMF determines the demand information of the TSN flow based on the characteristic information of the X QoS flows carrying the aggregation identifier.

[0327] It should be understood that the demand information for the TSN flow determined by CUC includes one or more parameters that are consistent with the above. Figure 5 The method for determining the specific parameters in the TSN flow demand information shown in step 501 is similar; please refer to the above. Figure 5 Detailed introduction in the text.

[0328] 804, SMF sends the TSN stream requirement information to CNC.

[0329] Accordingly, the CNC receives the demand information for the TSN stream from the SMF.

[0330] As an example, the CNC can also be a transport network CNC (TN CNC).

[0331] It should be understood that the demand information of this TSN stream is used by the CNC to determine the status information of the TSN stream. For details on the specific operations by which the CNC determines the status information of the TSN stream based on the demand information, please refer to the above. Figure 5 See step 502 for a detailed explanation.

[0332] 805, the CNC sends the status information of the TSN stream (also known as the merged endstation communication-configuration) to the SMF.

[0333] Accordingly, the SMF receives the status information of the TSN stream from the CNC.

[0334] It should be understood that the status information of the TSN stream is determined by the CNC based on the requirement information of the TSN stream.

[0335] It should also be understood that the status information of this TSN stream is used by the SMF to determine configuration information.

[0336] This step 805 is related to the above. Figure 5 Similar to 503 shown above, please refer to the above for details. Figure 5 See the detailed explanation in the document.

[0337] 806. The SMF sends configuration information to the RAN and UPF based on the status information of the TSN stream.

[0338] Accordingly, the RAN and UPF receive configuration information from the SMF. This configuration information is used by the transmitting end to adjust the transmission time of the data frames corresponding to the X QoS flows.

[0339] Optionally, the configuration information may include settings for adjusting the transmission time of data frames for the X QoS flows at the corresponding transmitters. For example, if the transmission direction of the data frames for the X QoS flows is uplink, with the RAN acting as the transmitter, the RAN adjusts the transmission time of the data frames according to the configuration information; or if the transmission direction of the data frames for the X QoS flows is downlink, with the UPF acting as the transmitter, the UPF adjusts the transmission time of the data frames according to the configuration information.

[0340] The SMF can send time-aware offsets (e.g., TimeAwareOffset) to the RAN and UPF within a transparent container. These time-aware offsets can be carried in the interface configuration within the configuration information to adjust the transmission time of data frames for the X QoS flows.

[0341] Optionally, the configuration information may include the identifiers of the X QoS flows.

[0342] Optionally, in step 803, the demand information of the TSN flow corresponds to X QoS flows. That is, before step 806, or during step 806, the CUC sends the correspondence between the TSN flow and the X QoS flows to the RAN and UPF. This configuration information includes the identifier of the TSN flow. After receiving the configuration information, the RAN and UPF, based on the identifier of the TSN flow and the correspondence between the TSN flow and the X QoS flows, determine how to schedule the data frames corresponding to the X QoS flows using the configuration information.

[0343] As an example, after receiving the CUC configuration information, the RAN and UPF determine the identifier of the same TSN flow corresponding to the X QoS flows based on the identifier of the TSN flow and the correspondence between the TSN flow and the X QoS flows. The RAN and UPF will then use the configuration information, including the identifier of the same TSN flow, to schedule the transmission time of the data frames corresponding to the X QoS flows, as well as other relevant information corresponding to the X QoS flows. For example, the port numbers used by the RAN and UPF to transmit the X QoS flows. Specifically, the RAN uses port #1 to transmit the X QoS flows, meaning the RAN transmits the X QoS flows through port #1, and the UPF uses port #2 to transmit the X QoS flows, meaning the UPF transmits the X QoS flows through port #2.

[0344] It should be understood that port #1 can be a port of the RAN, meaning that the X QoS flows are transmitted through the same port of the RAN; port #2 can be a port of the UPF, meaning that the X QoS flows are transmitted through the same port of the UPF.

[0345] It should also be understood that since this TSN flow corresponds to X QoS flows, the interface configuration in the configuration information is transmitted at the granularity of X QoS flows. Based on the TSN flow identifier and interface configuration, the RAN and UPF can treat these X QoS flows as a single TSN flow, eliminating the need to determine a specific TSN flow for each QoS flow. This avoids determining configuration information for the X TSN flows corresponding to these X QoS flows, thereby reducing the number of times the CUC configures the sending and receiving ends corresponding to the X QoS flows.

[0346] According to the above Figure 8In the method shown, during step 803 of this application, when the CUC performs parameter mapping, it treats X QoS flows as the same TSN flow and determines the demand information of this TSN flow. The CUC sends the demand information of this TSN flow to the CNC, the CNC determines the status information of this TSN flow based on the demand information, the CUC determines the configuration information based on the status information of this TSN flow, and sends the configuration information to the sending end and receiving end (e.g., RAN and UPF) corresponding to the X QoS flows. Since the TSN flow corresponds to the X QoS flows, the receiving configuration in the configuration information is transmitted at the granularity of the TSN flow. That is, the sending end can schedule the transmission time of the data frames corresponding to the X QoS flows according to the interface configuration in the configuration information based on the relationship between the TSN flow and the X QoS flows. At the same time, since the X QoS flows correspond to the same TSN flow, the port in the configuration information is the port corresponding to the TSN flow, that is, the X QoS flows are transmitted on the same port. With a limited number of sending and receiving ports corresponding to the X QoS flows, the number of QoS flows that can be transmitted can be increased, meaning that one port can transmit multiple QoS flows, thus improving transmission efficiency. Furthermore, with a limited number of QoS flows to be transmitted, the number of ports required by network devices can be reduced. By treating multiple QoS flows as a single TSN flow, meaning that multiple QoS flows can be transmitted on the same port, the number of ports required by network devices can be significantly reduced.

[0347] Furthermore, compared to CUC, which sends TSN flow demand information to CNC for each QoS flow (i.e., multiple QoS flows correspond one-to-one with multiple TSN flows, with each QoS flow corresponding to the demand information of one TSN flow), the sending and receiving ends need different scheduling queues (or queues) for each of these multiple QoS flows. Since the sending and receiving ends corresponding to these multiple QoS flows may not be able to support too many queues, the number of QoS flows supported by the sending and receiving ends corresponding to these multiple QoS flows is limited. For example, if the sending and receiving ends corresponding to these multiple QoS flows determine one TSN flow (i.e., per UE per QoS flow) for each QoS flow and process it, the number of QoS flows supported by the sending and receiving ends corresponding to these multiple QoS flows will be insufficient. The above-mentioned method provided in this application... Figures 5 to 8The method shown treats multiple QoS flows as a single TSN flow for processing, which can significantly reduce the number of TSN flow queues that the sending and receiving ends corresponding to these multiple QoS flows need to process, thereby improving transmission efficiency while reducing the complexity of the sending and receiving ends corresponding to these multiple QoS flows.

[0348] The above combination Figures 5 to 8 The methods provided in the embodiments of this application are described in detail below. Figures 9 to 12 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail here will be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0349] Figure 9 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 9 As shown, the device may include an acquisition unit 910 and a transceiver unit 920.

[0350] In one possible design, the communication device 900 can be a centralized user configuration function network element in the above method embodiments, or it can be a component (such as a chip or circuit) that implements the function of the centralized user configuration function network element in the above method embodiments.

[0351] It should be understood that the communication device 900 may correspond to this application. Figure 5 , Figure 8 The method CUC in the communication device 900 is a unit that executes the method. Furthermore, each unit in the communication device 900 and the other operations and / or functions described above are respectively for implementing... Figure 5 The methods in Figure 8 The corresponding process of the method described above. It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0352] It should also be understood that, in some possible implementations, the transceiver unit 920 in the communication device 900 may correspond to Figure 11 The transceiver 1120 in the communication device 1100 shown in the figure, and the acquisition unit 910 in the communication device 900 can correspond to Figure 11 The processor 1110 in the communication device 1100 shown in the figure.

[0353] It should also be understood that when the communication device 900 is a chip, the chip includes a transceiver unit. Optionally, the chip may also include a processing unit. The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip.

[0354] Optionally, the communication device 900 further includes a storage unit 930 for storing instructions.

[0355] Figure 10 This is a schematic block diagram of a communication device provided in an embodiment of this application. Figure 10 As shown, the device 1000 may include a transceiver unit 1010 and a processing unit 1020.

[0356] In one possible design, the communication device 1000 can be a centralized user configuration function network element in the above method embodiments, or it can be a component (such as a chip or circuit) that implements the centralized user configuration function network element in the above method embodiments.

[0357] It should be understood that the specific process of each unit performing the above-mentioned corresponding steps has been described in detail in the above method embodiments, and will not be repeated here for the sake of brevity.

[0358] It should also be understood that, in some possible implementations, the transceiver unit 1010 in the communication device 1000 may correspond to Figure 11 The transceiver 1120 in the communication device 1100 shown in the figure, and the processing unit 1020 in the communication device 1000 can correspond to Figure 11 The processor 1110 in the communication device 1100 shown in the figure.

[0359] It should also be understood that when the communication device 1000 is a chip, the chip includes a transceiver unit. Optionally, the chip may also include a processing unit. The transceiver unit may be an input / output circuit or a communication interface; the processing unit may be a processor, microprocessor, or integrated circuit integrated on the chip.

[0360] Optionally, the communication device 1000 may also include a storage unit.

[0361] Figure 11 This is a schematic block diagram of the device 1100 provided in an embodiment of this application. Figure 11 As shown, the device 1100 includes at least one processor 1110. The processor 1110 is coupled to a memory and is used to execute instructions stored in the memory to perform... Figure 5 , Figure 8 The method described herein. Optionally, the device 1100 further includes a transceiver 1120, the processor 1110 being coupled to a memory for executing instructions stored in the memory to control the transceiver 1120 to transmit and / or receive signals. For example, the processor 1110 may control the transceiver 1120 to transmit first information. Optionally, the device 1100 also includes a memory 1130 for storing instructions.

[0362] It should be understood that the processor 1120 and memory 1130 can be combined into a single processing device, with the processor 1120 executing the program code stored in the memory 1130 to achieve the aforementioned functions. In specific implementations, the memory 1130 can also be integrated into the processor 1110 or be independent of the processor 1110.

[0363] It should also be understood that transceiver 1120 may include a receiver (or receiver unit) and a transmitter (or transmitter unit). Transceiver 1120 may further include an antenna, and the number of antennas may be one or more. Transceiver 1120 may also be a communication interface or interface circuit.

[0364] When the device 1100 is a chip, the chip includes a transceiver unit and a processing unit. The transceiver unit can be an input / output circuit or a communication interface; the processing unit can be a processor, microprocessor, or integrated circuit integrated on the chip.

[0365] Figure 12 This is a schematic diagram of a chip system according to an embodiment of this application. The chip system here can also be a system composed of circuits. Figure 12 The illustrated chip system 1200 includes: logic circuitry 1210 and an input / output interface 1220. The logic circuitry is coupled to the input interface to transmit data (e.g., configuration information) for execution. Figure 5 or Figure 8 The method described.

[0366] This application also provides a processing apparatus, including a processor and an interface. The processor can be used to execute the methods described in the above method embodiments.

[0367] It should be understood that the aforementioned processing device can be a chip. For example, the processing device can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0368] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or by a combination of hardware and software modules within the processor. The software modules can reside in mature storage media in the art, such as random access registers, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are omitted here.

[0369] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0370] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache.

[0371] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute... Figure 5 or Figure 8 The method in the illustrated embodiment.

[0372] According to the method provided in the embodiments of this application, this application also provides a computer-readable medium storing program code, which, when run on a computer, causes the computer to perform... Figure 5 or Figure 8 The method in the illustrated embodiment.

[0373] According to the method provided in the embodiments of this application, this application also provides a system, which includes the aforementioned centralized user configuration function and centralized network configuration function.

[0374] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable information medium to another computer-readable storage medium. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., high-density digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0375] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0376] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method characterized by comprising: include: The centralized user configuration function network element determines the demand information of a Time Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, wherein the TSN flow corresponds to the multiple QoS flows. The centralized user configuration function network element sends the demand information of the TSN flow to the centralized network configuration function network element; The centralized network configuration function network element receives the demand information of a TSN flow from the centralized user configuration function network element, determines the status information of the TSN flow based on the demand information of the TSN flow, and sends the status information of the TSN flow to the centralized user configuration function network element. The centralized user configuration function network element receives the status information of a TSN flow from the centralized network configuration function network element, and sends information for configuring the sending and receiving ends corresponding to the multiple QoS flows according to the status information of the TSN flow.

2. A communication method characterized by comprising: include: The centralized user configuration function network element determines the demand information of a Time Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, wherein the TSN flow corresponds to the multiple QoS flows. The centralized user configuration function network element sends the demand information of the TSN flow to the centralized network configuration function network element; The centralized user configuration function network element receives the status information of a TSN flow from the centralized network configuration function network element. The status information of a TSN flow is determined based on the demand information of the TSN flow. The centralized user configuration function network element sends information for configuring the senders and receivers corresponding to the multiple QoS flows to the senders and receivers corresponding to the multiple QoS flows based on the status information of the one TSN flow.

3. The method according to claim 1 or 2, characterized in that, The information used to configure the sender and receiver corresponding to the multiple QoS flows includes the identifier of the TSN flow, and the method further includes: The centralized user configuration function network element sends the correspondence between the one TSN flow and the multiple QoS flows to the sending and receiving ends corresponding to the multiple QoS flows.

4. The method according to claim 1 or 2, characterized in that, The information used to configure the sending and receiving ends corresponding to the multiple QoS flows includes the identifiers of the multiple QoS flows.

5. The method according to claim 1 or 2, characterized in that, The sending end corresponding to the multiple QoS flows is the same, and the receiving end corresponding to the multiple QoS flows is the same.

6. The method according to claim 5, characterized in that, The multiple QoS flows satisfy the aggregation conditions, which include one or more of the following: The sessions to which the multiple QoS flows belong correspond to the same centralized user configuration function network element; The transmission periods of the multiple QoS flows are the same or are multiples of each other; The core network data packet delay budgets corresponding to the multiple QoS flows are the same; The multiple QoS flows arrive at their corresponding senders at the same time.

7. The method according to claim 5, characterized in that, Before the centralized user configuration function network element determines the demand information of a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, the method further includes: The centralized user configuration function network element receives information from the sending end corresponding to the multiple QoS flows, indicating that the multiple QoS flows are mapped to a single TSN flow.

8. The method according to claim 1 or 2, characterized in that, The requirement information for a TSN flow includes the maximum frame length. The centralized user configuration function network element determines the requirement information for a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data bursts of the multiple QoS flows; or, The centralized user configuration function network element determines the maximum frame length based on the sum of the maximum data burst lengths of the multiple QoS flows.

9. The method according to claim 1 or 2, characterized in that, The requirement information for a TSN flow includes the maximum number of frames per period. The centralized user configuration function network element determines the requirement information for a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the maximum number of frames per period based on the sum of the number of data frames transmitted by the multiple QoS flows within an interval, wherein the interval is the least common multiple of the transmission periods of the multiple QoS flows.

10. The method according to claim 1 or 2, characterized in that, The demand information for a TSN flow includes intervals. The centralized user configuration function network element determines the demand information for a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the interval based on the least common multiple of the transmission cycles of the multiple QoS flows.

11. The method according to claim 1 or 2, characterized in that, The demand information for a TSN flow includes the latest transmission offset. The centralized user configuration function network element determines the demand information for a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the latest transmission offset based on the interval and the maximum frame length. The latest time offset represents the maximum value of the time when the sending end corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows later than the start time of the interval. The interval is the least common multiple of the transmission periods of the multiple QoS flows, and the maximum frame length is the maximum length of the data frames of the multiple QoS flows.

12. The method according to claim 1 or 2, characterized in that, The requirement information for a TSN flow includes the earliest transmission offset, which indicates that the time when the sender corresponding to the multiple QoS flows starts sending the data frames of the multiple QoS flows is earlier than the maximum value of the start time of the interval; The centralized user configuration function network element determines the demand information of a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the earliest transmission offset based on the earliest time that the multiple QoS flows arrive at the corresponding sending end of the multiple QoS flows.

13. The method according to claim 1 or 2, characterized in that, The TSN flow demand information includes the maximum allowed latency of the TSN flow. The centralized user configuration function network element determines the demand information of a time-sensitive network TSN flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the maximum allowed latency of the TSN flow based on the maximum value among the maximum buffer durations of the multiple QoS flows. The maximum buffer duration is the maximum duration for which the sending end corresponding to the multiple QoS flows buffers the data frames of the multiple QoS flows.

14. The method according to claim 1 or 2, characterized in that, The requirement information of the TSN stream includes the number of redundant paths, which indicates whether the sender of the multiple QoS streams needs to send the data frames of the multiple QoS streams to the receiver of the multiple QoS streams through multiple user plane paths; The centralized user configuration function network element determines the demand information of a Time-Sensitive Network (TSN) flow based on the characteristic information of multiple Quality of Service (QoS) flows, including: The centralized user configuration function network element determines the number of redundant paths based on whether the multiple QoS flows include QoS flows that require redundant transmission.

15. The method according to claim 1 or 2, characterized in that, The information used to configure the sending and receiving ends corresponding to the multiple QoS flows includes information for adjusting the transmission time of data frames for the multiple QoS flows.

16. A communication device, characterized in that, It includes at least one processor, the at least one processor being coupled to a memory, reading and executing instructions in the memory to implement the method as described in any one of claims 2 to 15.

17. The communication device according to claim 16, characterized in that, It also includes the memory.

18. A communication device, characterized in that, Includes modules for implementing the method as described in any one of claims 2 to 15.

19. A communication system, characterized in that, This includes centralized user configuration function network elements and centralized network configuration function network elements, among which: The centralized user configuration function network element is used to implement the method as described in any one of claims 2 to 15; The centralized network configuration function network element is used to: receive the demand information of a TSN flow from the centralized user configuration function network element, determine the status information of the TSN flow based on the demand information of the TSN flow, and send the status information of the TSN flow to the centralized user configuration function network element.

20. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, causes the method as described in any one of claims 2 to 15 to be performed.

21. A computer program product containing instructions, characterized in that, When the instructions are executed on a computer, the computer performs the method as described in any one of claims 2 to 15.

22. A chip, characterized in that, The chip includes a processor and a data interface, wherein the processor reads instructions stored in the memory through the data interface to execute the method as described in any one of claims 2 to 15.

Images