Systems and methods for reference signaling design and configuration

By introducing D2D communication and TSN converters into 5G NR systems, the data transmission path is optimized, addressing the challenges of low latency, low jitter, and high reliability in 5G NR systems. This improves data transmission performance between devices and user experience, and supports high data rates and proximity services.

CN123077044APending Publication Date: 2026-11-10ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480090175.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-04-08
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing 5G NR systems face challenges in achieving low latency, low jitter, and high reliability data transmission, especially in device-to-device communication and proximity services. Traditional cellular networks have limited data rate capabilities and proximity service support, making it difficult to meet the demands for high data rates and user experience.

Method used

By introducing device-to-device (D2D) communication technology, utilizing time-sensitive network converters (TSN converters) on the core network entity and user equipment side, and combining 5G system bridging management and reference signaling design, data transmission paths are optimized to achieve low-latency, low-jitter, and high-reliability data services.

Benefits of technology

It improves data transmission performance between devices, reduces the burden on cellular networks, lowers battery power consumption of user devices, enhances user experience, and supports high data rates and proximity services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123077044A_ABST
    Figure CN123077044A_ABST
Patent Text Reader

Abstract

Systems and methods for designing and configuring reference signaling are described. A first wireless communication device (e.g., a first user equipment (UE)) can initiate the establishment of a first protocol data unit (PDU) session, the first PDU session including a candidate-side time-sensitive communications (TSC) user equipment (UE) identifier (ID). The first wireless communication device can be communicatively coupled to a first core network entity (e.g., a user plane function (UPF)) through the first PDU session.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, including but not limited to systems and methods for designing and configuring reference signaling. Background Technology

[0002] The standards organization Third Generation Partnership Project (3GPP) is currently specifying a new radio interface called 5G New Radio (5G NR) and a Next Generation Packet Core Network (NG-CN or NGC). 5G NR will have three main components: 5G Access Network (5G-AN), 5G Core Network (5GC), and User Equipment (UE). To facilitate the implementation of different data services and needs, the network elements (also known as network functions) of 5GC have been simplified, with some elements being software-based and others hardware-based, allowing for customization as needed. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues existing in the prior art, and to provide additional features that will become apparent upon reading the following detailed description in conjunction with the accompanying drawings. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not as limiting, and that various modifications can be made to the disclosed embodiments without departing from the scope of this disclosure, as will be apparent to those skilled in the art upon reading this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium that includes the following: A first wireless communication device (e.g., a first user equipment (UE) or UE1) among a plurality of wireless communication devices can initiate / start the establishment of a first Protocol Data Unit (PDU) session, the first PDU session including a candidate-side walkway Time Sensitive Communication (TSC) User Equipment (UE) identification (ID). The first wireless communication device can communicatively couple to a first core network entity (e.g., a user plane function (UPF)) through the first PDU session.

[0005] In some implementations, a second core network entity (e.g., a session management function (SMF)) may be configured to determine whether a first wireless communication device and a second wireless communication device (e.g., a second UE or UE2) among the plurality of wireless communication devices can discover each other, and to select a first core network entity for both the first and second wireless communication devices.

[0006] In some implementations, a second core network entity may be configured to determine whether a first wireless communication device and a second wireless communication device among the plurality of wireless communication devices can discover each other, the first and second wireless communication devices being communicatively coupled to the first core network entity. In some implementations, the first core network entity may have a network-side time-sensitive network (TSN) translator (NW-TT), and each of the first and second wireless communication devices may have a corresponding device-side time-sensitive network translator (DS-TT) Ethernet port.

[0007] In some implementations, the second core network entity may be configured to determine which two wireless communication devices can form a sidelink port pair. In some implementations, the second core network entity may be configured to report all TSC information about candidate time-sensitive communication (TSC) UEs to a third core network entity (e.g., an application function (AF) such as time-sensitive networking (TSN) or time synchronization function (TSF)) via a fourth core network entity (e.g., a policy control function (PCF)), enabling the third core network entity to determine which two of the plurality of wireless communication devices can form a sidelink port pair.

[0008] In some implementations, the third core network entity may be configured to determine whether a stream is a UE-UE TSC (UE-UE TSC) and to classify the stream into one or more sidelink streams. In some implementations, the third core network entity may be configured to identify the sending UE and / or receiving UE of at least one of the one or more sidelink streams.

[0009] In some implementations, a third core network entity may be configured to request the creation of a new AF session, the new AF session being associated with at least one of the following: a first Media Access Control (MAC) address of a first wireless communication device; and / or a second MAC address of a second wireless communication device among the plurality of wireless communication devices. In some implementations, a fourth core network entity may be configured to, in response to receiving a request to create a new AF session, send at least one of the following to at least one of the plurality of wireless communication devices: a flow description, a TSC Quality of Service (QoS) parameter, and / or a peer UE ID.

[0010] In some implementations, a third core network entity may be configured to identify device-to-device traffic and to divide that traffic into first traffic from a first wireless communication device to a second wireless communication device and / or second traffic from the second wireless communication device to the first wireless communication device. In some implementations, the third core network entity may be configured to send a message to a fourth core network entity, the message including at least one of the following for the first and second wireless communication devices: UE ID; flow description; one or more QoS parameters; and / or TSC QoS parameters. Attached Figure Description

[0011] Various exemplary embodiments of this solution will be described in detail below with reference to the accompanying drawings or illustrations. These drawings are for illustrative purposes only and depict only exemplary embodiments of the solution to aid the reader's understanding. Therefore, these drawings should not be considered as limitations on the breadth, scope, or applicability of the solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0012] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, in which the techniques disclosed herein can be implemented; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 A block diagram of example 5G system (5GS) bridging management according to some embodiments of the present disclosure is shown; Figure 4 A flowchart illustrating example TSC information reporting according to some embodiments of this disclosure is shown; Figure 5 A flowchart illustrating an example TSC configuration according to some embodiments of this disclosure is shown; and Figure 6 A flowchart illustrating an example method for designing and configuring reference signaling according to an embodiment of this disclosure is shown. Detailed Implementation

[0013] 1. Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 according to an embodiment of this disclosure is illustrated, in which the techniques disclosed herein can be implemented. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as "network 100". Such an example network 100 includes a base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and a user equipment 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device), which can communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a set of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0014] For example, BS 102 can operate on the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes," which generally practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes may be able to perform wireless and / or wired communication.

[0015] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., Orthogonal Frequency Division Multiplexing (OFDM) / Orthogonal Frequency Division Multiple Access (OFDMA) signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics, which need not be described in detail herein. In one illustrative embodiment, system 200 may be used in applications such as those described above. Figure 1In wireless communication environments such as 100, data symbols are transmitted (e.g., sent and received).

[0016] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a base station (BS) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a user equipment (UE) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for the data transmission described herein.

[0017] As those skilled in the art will understand, system 200 may also include, in addition to Figure 2 Any number of modules other than those shown. Those skilled in the art will understand that the various illustrative logic blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described in terms of their functionality. Whether such functionality is implemented in hardware, firmware, or software can depend on the specific application and design constraints imposed on the overall system. Those skilled in the art can implement such functionality appropriately for each specific application, but such implementation decisions should not be construed as limiting the scope of this disclosure.

[0018] According to some embodiments, UE transceiver 230 may be referred to herein as an "uplink" transceiver 230 including a radio frequency (RF) transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-division duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each RF transmitter and RF receiver including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time-division duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 so that transmissions on the radio transmission link 250 can be received while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be time-coordinated, such that the downlink receiver is coupled to the downlink antenna 212 so that the uplink transmitter is coupled to the uplink antenna 232 while receiving transmissions on the wireless transmission link 250. In some embodiments, there is tight time synchronization with a minimum guard time between changes in the duplex direction.

[0019] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna arrangements 212 / 232 in a suitable configuration capable of supporting specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to application to specific standards and associated protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0020] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be implemented in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using a general-purpose processor, content-addressable memory, digital signal processor, application-specific integrated circuit, field-programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, or a state machine, etc. The processor may also be implemented as a combination of multiple computing devices, such as a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a digital signal processor core, or any other combination of such configurations.

[0021] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any feasible combination thereof. Memory modules 216 and 234 can be implemented as random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disks, removable disks, compact optical disc read-only storage (CD-ROM), or any other form of storage medium known in the art. In this respect, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0022] Network communication module 218 broadly represents the hardware, software, firmware, processing logic, and / or other components that enable bidirectional communication between base station 202, base transceiver 210, and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or Global Microwave Access Interoperability (WiMAX) services. In a typical deployment, but without limitation, network communication module 218 provides an 802.3 Ethernet interface, enabling base transceiver 210 to communicate with conventional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and variations thereof, used herein with respect to a specified operation or function, refer to devices, components, circuits, structures, machines, signals, etc., which are physically constructed, programmed, formatted, and / or arranged to perform the specified operation or function.

[0023] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communication used by systems (e.g., wireless communication devices, wireless communication nodes) for interconnecting and communicating with other systems. The model is divided into seven sub-components or layers, each representing a conceptual set of services provided to the layers above and below it. The OSI model also defines logical networks and efficiently describes computer packet transmission using different layer protocols. The OSI model may also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Medium Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is another layer.

[0024] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to make and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and shown herein. Furthermore, the specific order or hierarchy of the steps in the methods disclosed herein is merely an example. Based on design preferences, the specific order or hierarchy of the steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0025] 2. Systems and methods for designing and configuring reference signaling. In some systems, data transmission capabilities with predetermined performance limitations, requirements, and / or conditions (such as lower latency and higher reliability to meet the needs or standards of certain applications or platforms) can be provided, introduced, or supported. In some cases, latency, jitter, and / or reliability may depend on the implementation and deployment of the network (e.g., Network 100). However, because the engineering implementation of some systems (e.g., relying on UE or network implementations for latency, jitter, and / or reliability considerations) may be insufficient or uneconomical, allowing / achieving or achieving the desired performance of data transmission (e.g., latency less than a predefined threshold (e.g., 5 milliseconds (ms)) or reliability greater than or equal to a reliability threshold (e.g., 99.999%)) can be challenging.

[0026] In some configurations, certain networks may include mechanisms to help / assist in reducing end-to-end latency, such as Protocol Data Unit (PDU) session anchor (PSA) relocation for Session and Service Continuity (SSC) Mode 2 or Mode 3 sessions, and / or traffic routing impacting application functions. However, shortening / reducing data transmission paths may not be sufficient to guarantee performance (or guarantee performance improvements) in various scenarios. Other factors in some systems (including but not limited to UE mobility / movement) can cause latency, jitter, or other performance degradation, which may be considered in this document. Simultaneously, it may be desirable to support or provide higher reliability than certain telecommunications network functions and / or single-user-plane tunnels. In such cases, it may be desirable to enhance / improve the system and architecture to allow / achieve or reach the desired performance (e.g., performance meeting predefined requirements). The corresponding effects and mechanisms of the improved system and architecture can be identified.

[0027] With the emergence of wireless multimedia services, the demand for higher data rates and better user experience may increase, thus placing relatively higher standards / conditions / requirements or parameters on the system capacity, capabilities, or coverage of cellular networks. In some cases, considering at least one of public safety, social networks, short-range data sharing, local communication, etc., proximity services can continue to expand incrementally, allowing entities (e.g., users or clients) to send or receive information from users or devices within a certain proximity / distance, and to communicate with users or devices. Some network-centric cellular networks may have limited high data rate capabilities or support for proximity services. In this context, device-to-device (D2D) communication can be used to address / overcome the shortcomings of the network-centric model. The application of D2D technology can alleviate the burden on cellular networks, reduce UE 104 battery power consumption, improve data rates, and / or improve the robustness of network infrastructure, for example, to meet the aforementioned high data rate services and proximity services. D2D technology can be referred to as proximity services (ProSe), one-sided, sidelink, or sidelink (SL) communication, etc.

[0028] The systems and methods of this technical solution can provide one or more mechanisms or technologies in a wireless communication system (e.g., a 5G system) to allow / implement or provide data services with relatively low (or low) latency, low jitter, and / or high reliability between UE 104 and external entities (including but not limited to between UE 104 and a donor node, between UE 104 and BS 102, and / or between multiple UE 104). By utilizing implementations of the mechanisms discussed herein, the systems and methods of this technical solution can improve the performance of data transmission between network devices (e.g., wireless communication devices or nodes) and the user experience for users of the network devices.

[0029] TSC information may include, but is not limited to, at least one of the following: UE ID; UE 104 IP address; UE-DS-TT dwell time; DS-TT Ethernet port MAC address; port management information or capabilities; user management information; data network name (DNN); single network slice selection assistance information (S-NSSAI); bridge ID; user plane function (UPF) ID; user plane node ID; port number; indication of support for TSC on the side link, etc.

[0030] Indication of a sidelink TSC can indicate that a PDU session is established for a sidelink TSC. In some cases, the network (e.g., session management functions, policy control functions, etc.) can identify that a PDU session is established for a sidelink TSC via a DNN and / or S-NSSAI. Examples of UE IDs may include: gNB-CU UE F1 application protocol (F1AP) ID; gNB-DU UE F1AP ID; C-RNTI; 5G-temporary mobile subscriber identity (TMSI); UE MAC address; IPv4 address; IPv6 address, etc.

[0031] TSC information may include, but is not limited to, at least one of the following: UE dwell time to the device-side (DS) TSN translator (TT) (e.g., the time for transmitting packets between the UE and the DS-TT port) and / or the DS-TT MAC address of the PDU session; port management information or capabilities from the DS-TT and / or UE in the PDU session establishment request; and / or the port number of the assigned DS-TT Ethernet port, the port number of the NW-TT, the port management information or capabilities of the NW-TT, user plane management information and / or user plane node identifier / identifier (ID) (e.g., bridge ID) in the N4 (e.g., UPF-SMF) session establishment response message (e.g., sometimes generally referred to as a response or reply to a session establishment request); and / or the TSN domain number.

[0032] Port management information (e.g., included in the container) may include, but is not limited to, at least one of the following: port management capabilities; bridge latency-related information (e.g., txPropagationDelay or txPropagationDelayDeltaThreshold); traffic category table; gating information; NW-TT port neighbor discovery configuration; DS-TT port neighbor discovery configuration; neighbor discovery information for each discovered neighbor in NW-TT; neighbor discovery information for each discovered neighbor in DS-TT; flow parameters; per-stream filtering and policing information; time synchronization information; precision time protocol (PTP) instance specification; and / or predefined datasets.

[0033] Port management capabilities may include, but are not limited to, at least one of the following: support for TSN time domain numbers, txPropagationDelay and traffic category tables, support for neighbor discovery and / or TSN domain numbers.

[0034] User management information (e.g., included in a container) may include, but is not limited to, at least one of the following: information for the 5GS bridge or router (e.g., user plane node information, user plane node address, user plane node ID or NW-TT port number, IP address), traffic forwarding information, neighbor discovery configuration, DS-TT port neighbor discovery configuration for DS-TT ports, discovered neighbor information for DS-TT ports, discovered neighbor information for each DS-TT port, time synchronization information, predefined datasets, etc. User plane node information may include at least one port number (e.g., a port number assigned by a node for a given PDU session) and / or at least one user plane node ID (e.g., the bridge identifier of a 5GS TSN bridge and / or the user plane node ID), etc.

[0035] 5GS Bridge or TSC Information Management Figure 3 A block diagram 300 illustrating example 5G system (5GS) bridge or TSC information management is shown. In various implementations, 5GS can act as / perform as a Layer 2 Ethernet bridge and / or a Layer 3 (L3) IP router. When integrated with Time-Sensitive Networking (TSN), 5GS functionality can act as one or more TSN bridges in a TSN network. A 5GS bridge may include: a port on the side of a single User Plane Function (UPF) (e.g., a Protocol Data Unit (PDU) session anchor (PSA)); a user plane tunnel between UE1 (e.g., the first UE) and / or UE2 (e.g., the second UE) and the UPF; a user plane (e.g., a device-to-device interface) between UE1 and UE2; and ports on the device-side (DS) TSN converter (TT) (DS-TT)-1 and / or DS-TT-2 side. For each 5GS bridge in the TSN network, the port on the network-side TSN converter (NW-TT) can support the connection to the TSN network, and the port on the DS-TT-1 side can be associated with the PDU session that provides the connection to the TSN network or the device-to-device link of the peer DS-TT-2 of UE-2.

[0036] For each network instance, the granularity of a 5GS TSN bridge can be based on a UPF (per UPF). The bridge identifier (ID) of a 5GS TSN bridge can be bound to the UPF ID of the UPF. During 5GS TSN bridge information reporting, the Application Function (AF) can store the binding relationships between ports and PDU sessions on the UE and / or DS-TT side. For example, the AF can include or correspond to a TSN AF or a time-sensitive communication or time-synchronization function (TSC TSF). The AF can store information about ports on the UPF and / or NW-TT side. The UPF and / or NW-TT can forward / send / transmit traffic to the appropriate egress port based on or according to traffic forwarding information. From the AF's perspective, for example, a 5GS TSN bridge can have a single NW-TT entity within the UPF, and the NW-TT can have multiple ports for traffic forwarding.

[0037] To support TSN-scheduled traffic over the 5GS bridge (e.g., as described in the specification or depending on the configuration), 5GS may support, but is not limited to, the following functionalities: Configure bridge information in 5GS.

[0038] • Report bridge information of the 5GS bridge to the TSN network.

[0039] • For example, according to the specification, receive (e.g., predefined) configurations from the TSN network.

[0040] • The configuration information obtained from the TSN network is mapped to the 5GS QoS information (e.g., 5G QoS Flow Identifier (5QI), TSC auxiliary information) of the quality of service (QoS) flow in the corresponding PDU session, for example for efficient time-aware scheduling as described in the specification.

[0041] • The configuration information obtained from the TSN network is mapped to the 5GS device-to-device QoS information (e.g., physical layer quality indicator (PQI), device-to-device (D2D) TSC auxiliary information, etc.) of the D2D QoS flow in the corresponding D2D link for efficient time-aware scheduling.

[0042] In cases where UE1 is not connected to the network, for example, UE2 can help / assist UE1 in transmitting bridge information to the network and assist the network in transmitting bridge configuration to UE1. UE1's DS-TT bridge information can be transmitted / sent / provided to the network (e.g., AF) via UE2. UE1's DS-TT bridge configuration can be transmitted to UE1 (e.g., AF) via UE2.

[0043] 5GS bridge configuration SMF can report the MAC address of the DS-TT port to AF via Policy Control Function (PCF). The association between the DS-TT MAC address, 5GS bridge ID, and / or port number on the DS-TT can be maintained / stored at AF, and this association can be used to assist in binding TSN traffic to UE 104 PDU sessions and / or D2D links. Two (or more) of the following models can be supported to configure 5GS QoS for TSN traffic: • Model 1: Based on the assumption that per-stream filtering and policing parameters (PSFP) information is always provided by the central network controller (CNC). In this case, QoS flows can be established based on the PSFP information provided by the CNC.

[0044] If the AF has declared support for PSFP to the CNC, the CNC can provide PSFP information. If each DS-TT and NW-TT of the 5GS bridge has indicated support for PSFP, the AF can indicate support for PSFP to the CNC.

[0045] • Second Model: PSFP information is not required from the CNC. In this case, pre-configured QoS flows can be used and / or configured. For example, as defined in the specification, additional QoS flows can be established as needed based on the PSFP if it is available.

[0046] When PSFP information is available, AF can identify the ingress and / or egress ports of a TSN stream and determine one or more DS-TT port MAC addresses that identify the corresponding one or more PDU sessions and / or D2D links carrying the TSN stream. The flow direction of the TSN stream can be determined as, but is not limited to: if the ingress port is a DS-TT port or the egress port is an NW-TT port, the flow direction can be an uplink (UL); if one or more ingress ports are NW-TT ports, the flow direction can be a downlink (DL); and / or if the ingress port is DS-TT-1 and the egress port is DS-TT-2, the flow direction can be a D2D link (from TT-1 to TT-2). The flow direction can be part of TSC Auxiliary Information (TSCAI).

[0047] AF can use the flow filter instance in the PSFP information to derive the service dataflow of a TSN flow. AF can use the priority value (if available), 5GS bridge latency information, and scheduling traffic information in the flow filter instance in the PSFP information to derive TSNQoS information (e.g., priority and latency) for a given TSN flow and / or a flow that aggregates TSN flows.

[0048] TSCAI determination based on TSC auxiliary container for D2D link PCF can determine the TSCAI of a QoS flow based on the TSC auxiliary container bound to the policy and charging control (PCC) rules of the QoS flow. For example, this can be applied regardless of whether the TSC auxiliary container is determined by AF (e.g., including or corresponding to Time Sensitive Communication and Time Synchronization Function (TSC TSF)).

[0049] The burst arrival time and period components of the TSCAI sent by the PCF to the 5G-AN can be specified relative to the 5G clock. The PCF can be responsible for mapping the burst arrival time and period in the TSC auxiliary container from the external clock to the 5G clock based on the time offset and cumulative rate ratio between the external time and 5GS time (when available) measured and reported by the UPF. In some cases, the SMF and / or PCF can be responsible for mapping the burst arrival time and period in the TSC auxiliary container from the external clock to the 5G clock based on the time offset and cumulative rate ratio between the external time and 5GS time (when available) measured and reported by the UPF. After the mapping operation, the SMF can send / transmit / provide the mapped burst arrival time (BAT) and period in the TSC auxiliary container to the PCF. The PCF can correct the TSCAI based on the UPF report regarding the time offset and cumulative rate ratio between the external Precise Time Protocol (PTP) time and 5GS time (as measured and reported by the UPF).

[0050] The TSCAI parameter in PCF can be determined, for example, as follows: For downlink traffic, the PCF can correct the burst arrival time in the TSC auxiliary container based on the latest time offset measurement received from the UPF, and set / configure the TSCAI burst arrival time to the sum of the correction value and the core network (CN) packet delay budget (PDB) (as provided in the specification, for example), representing the latest possible time when the first packet of the data burst arrives in the access network (AN).

[0051] For uplink traffic, the PCF can correct the burst arrival time in the TSC auxiliary container based on the latest time offset measurement received from the UPF, and set the TSCAI burst arrival time as the sum of the correction value and the UE-DS-TT dwell time, representing the latest possible time when the first packet of the data burst arrives at the UE 104's egress. If the UE-DS-TT dwell time is not yet provided by the UE 104, the technique for correcting the burst arrival time by the PCF can be, for example, based on the PCF implementation or determined by the PCF implementation.

[0052] For D2D traffic, the PCF can correct the burst arrival time in the TSC auxiliary container based on or according to the latest time offset measurement received from the UPF, and set the TSCAI burst arrival time as the sum of the correction value and / or the UE-DS-TT dwell time, representing the latest possible time when the first packet of the data burst arrives at the UE 104's egress. If the UE-DS-TT dwell time is not yet provided by the UE 104, the technique for correcting the burst arrival time by the PCF can be, for example, based on the PCF implementation or determined by the PCF implementation.

[0053] If a cumulative rate ratio has been previously received from the UPF, the PCF can use that cumulative rate ratio to correct the period in the TSC auxiliary container and set the TSCAI period to the corrected value. Otherwise, the PCF can set / configure the received period in the TSCAI without any correction.

[0054] PCF can set the TSCAI flow direction to the flow direction in the TSC auxiliary container.

[0055] If the lifetime is provided in terms of maximum message count, the PCF can convert the maximum message count to a time unit by multiplying its value by the TSCAI period and set the TSCAI lifetime to a calculated / determined value. If the lifetime is provided in terms of time units, the PCF can use the cumulative rate ratio to correct the lifetime if a cumulative rate ratio has previously been received from the UPF and set the TSCAI lifetime to the corrected value. Otherwise, the PCF can set the TSCAI lifetime without correction.

[0056] • If the TSC auxiliary container contains a BAT window, the PCF can set and / or correct / update / modify the earliest possible arrival time and / or latest possible arrival time of the indicated first packet (in the same manner as described above for correction of burst arrival time).

[0057] • If the TSC auxiliary container includes / includes BAT adaptive capability, the PCF can set the BAT adaptive capability in the TSCAI. When the PCF determines that the TSCAI includes BAT adaptive capability without BAT, the PCF can enable / implement notification control for QoS flows to receive BAT offsets and notifications indicating that the guaranteed flow bit rate (GFBR) can no longer be guaranteed, which can be a predefined notification according to the specification.

[0058] • If the TSC auxiliary container contains a cycle range, the PCF can set and correct the cycle range (e.g., in a manner similar to that described above for cycle correction).

[0059] Depending on whether a time domain is provided in the TSC auxiliary container, the PCF can perform at least one of the following: • The PCF can regulate the SMF to report clock drift between the 5G clock configured for the (g)PTP time domain number of NW-TT and the external master clock (GM clock).

[0060] • The PCF can regulate the SMF to report clock drift between the 5G clock for a given time domain number and the external GM clock.

[0061] The PCF can regulate the SMF's reporting of clock drift using N4 association establishment or update procedures as described in the specification or predefined. If the PCF has clock drift information for a specific time domain, and if that time domain matches the time domain in the TSC auxiliary container (e.g., clock drift between the 5G timing determined based on the UPF report and the time domain provided by the AF), and / or no time domain information is provided in the TSC auxiliary container, the PCF can adjust the TSCAI information to reflect a predefined 5GS clock (e.g., as described in the specification). If the PCF does not have synchronization information for the requested time domain in the TSC auxiliary container, and / or the time domain in the TSC auxiliary container is set to a value equal to 5GS, the TSCAI information can be used without adjustment.

[0062] In cases of drift between the external GM clock and the 5G clock, the UPF can update the offset to the PCF using a predefined N4 reporting procedure. If the cumulative rate ratio is available, and if the cumulative rate ratio changes between the external PTP time and the 5G time, the UPF can update the cumulative rate ratio to the PCF using a predefined N4 reporting procedure. Subsequently, the PCF can trigger a PDU session modification, such as as provided in the specification, to update the TSCAI to the NG-RAN, for example, without requiring AN or N1-specific signaling exchange with UE 104. In some cases, to prevent frequent updates from the UPF, the UPF can send the offset or cumulative rate ratio when the difference between the current measurement and a previously reported measurement is higher than / greater than a predefined threshold.

[0063] TSC Information Reporting refer to Figure 4 This document depicts a flowchart 400 for example TSC information reporting (e.g., steps / processes / operations for reporting TSC information). TSC information may include or correspond to bridge information at least. One or more operations of flowchart 400 may be performed using methods described herein. Figures 1 to 2 The flowchart 400 may be implemented by any components and devices described in detail. In some embodiments, one or more operations of the flowchart 400 may be performed by at least one wireless communication device (e.g., UE or terminal device), at least one wireless communication node (e.g., BS, gNB, radio access network (RAN), or access network device), at least one core network entity (e.g., session management function (SMF), policy control function (PCF), application function (AF), etc.), at least one satellite, etc. Depending on the embodiment, more, fewer, or different operations may be performed or included in the flowchart 400. For example, the operations of the flowchart 400 may include, but are not limited to, operations 402 through 416. One or more operations of the flowchart 400 may be performed or arranged in a different order or sequence, not limited to the order discussed herein. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0064] In operation 402, at least one UE 104 (e.g., a first wireless communication device (UE1) or one of the UEs 104) may initiate / start or execute / perform a discovery or connection process / operation / procedure. The at least one UE 104 performing the discovery may, for example, include: sending / transmitting / providing a discovery message, and / or receiving / obtaining / acquiring a discovery message to discover / identify / find and / or connect to other UEs supporting sidelink time-sensitive communication (TSC) (e.g., a second wireless communication device (UE2) or another UE 104 among the UEs 104). UEs supporting sidelink TSC may sometimes be broadly referred to as sidelink TSC UEs. During the discovery or connection establishment process, UE 104 (e.g., UE1) may indicate or provide TSC information associated with that UE 104 (e.g., UE1's TSC information, such as capabilities, support, or configuration) to other UEs 104 (e.g., UE2).

[0065] In operation 404, UE 104 (e.g., UE1 and UE2) may initiate a PDU session establishment or modification procedure, for example, to establish a new PDU session or modify a PDU session, switch between existing PDU sessions, and / or request a PDU session for one or more services. A request for a PDU session may be referred to as a PDU session establishment or modification request. In various aspects, UE 104 may initiate a PDU session establishment or modification procedure to establish or modify a PDU session for Time Sensitive Communications (TSC) services. For example, UE1 and UE2 may initiate a PDU session establishment to establish PDU sessions for TSC services, respectively. For example, during this procedure, one or more of UE 104 may send a PDU session establishment or modification request to the network (e.g., SMF, sometimes referred to as a second core network entity). The PDU session establishment or modification request may include TSC information from UE 104 or (e.g., received from a peer UE) TSC information from at least one peer UE. In some cases, a PDU session establishment request may include at least one candidate peer UE identifier (ID) and / or the peer UE's TSC information.

[0066] In some implementations, if the bridge ID included in the bridge information received from the peer UE is the same as the bridge ID of UE 104, UE 104 can report the received TSC information from the peer UE to the network (via PDU session establishment or modification). In some implementations, if the user plane node ID included in the bridge information received from the peer UE is the same as the user plane node ID of UE 104, UE 104 can report the received bridge information from the peer UE to the network (via PDU session establishment or modification). In some implementations, if the UPF ID included in the bridge information received from the peer UE is the same as the UPF ID of UE 104, UE 104 can report the received bridge information from the peer UE to the network (via PDU session establishment or modification).

[0067] In some implementations, the SMF (e.g., a second core network entity) can determine or identify whether two UEs 104 (e.g., UE1 and UE2) connected to the same SMF can discover / find each other. In response to determining, for example, that UE1 and UE2 can discover each other, the SMF can select / select the same User Plane Function (UPF) (e.g., sometimes referred to as the first core network entity) for both sidelink UEs 104 (UE1 and UE2). In this case, for example, the UPF can be selected for both UE1 and UE2.

[0068] During Operation 404, the Session Management Function (SMF) (e.g., a second core network entity) can initiate an SMF policy association with the PCF (e.g., a fourth core network entity) by sending an Npcf_SMPolicyControl_Create message to the PCF. Npcf_SMPolicyControl_Create may include TSC information received from at least one of the UEs 104 (e.g., UE1 and / or UE2). The PCF can, for example, detect whether the Npcf_SMPolicyControl_Create request involves a session management (SM) policy association that enables sidelink time-sensitive communication and / or time synchronization based on the TSC indication included in the received DNN and / or S-NSSAI or RSC or TSC information. The PCF can instruct the SMF (e.g., by sending an SmPolicyDecision to the SMF) to initiate / execute / trigger a PCF interaction (e.g., the SMF exchanging information with the PCF) when at least one trigger (e.g., a condition / criteria) is met. Triggers can be predetermined or configured according to specifications or other settings. As an example, triggers for SMF-initiated PCF interactions may include, but are not limited to, the availability of new TSC information. In some implementations, the PCF can identify or determine that a PDU session is established for a sidelink trunk TSC flow based on or based on data network name / single network slice selection auxiliary information (DNN / S-NASSI) or other types of information.

[0069] During SMF policy association, the SMF may send / transmit / provide information to the PCF, such as, but not limited to, at least one of the following: UE ID (e.g., destination (DST) layer 2 (L2) ID, 5G-TMSI and / or subscription permanent identifier (SUPI) etc.); UE's TSC information; peer UE ID; peer UE's TSC information; and / or measurements of the D2D link with the peer UE (e.g., reference signal received power (RSRP), reference signal received quality indicator (RSRI), channel state information (CSI) and / or constant bit rate (CBR) etc.).

[0070] The PCF can detect, based on the received DNN and S-NSSAI, whether the Npcf_SMPolicyControl_Create request involves or is associated with a Session Management (SM) policy that enables sidelink time-sensitive communication. The PCF can then provide an indication (e.g., a "TSN_BRIDGE_INFO" policy control request trigger within the "policyCtrlReqTriggers" attribute of the SmPolicyDecision data structure) to instruct the SMF to report bridge information when the trigger is satisfied (e.g., new TSC user plane node information becomes available).

[0071] In some implementations, the SMF can perform a UE-to-UE port pair selection process. In some implementations, the PCF can perform a UE-to-UE port pair selection process.

[0072] The port pair selection process may include or involve determining which two UEs can be associated with a port pair (e.g., D2D port pair information) based on at least one of the following: UE ID (e.g., DST L2 ID, 5G-TMSI, SUPI, etc.); TSC information of at least one of the two UEs; peer UE ID; peer UE's TSC information; and measurements of the D2D link with the peer UE (e.g., RSRP, RSRI, CSI, CBR, etc.).

[0073] In some configurations, the SMF can select a UPF for a PDU session. This UPF can support one or more functions, such as D2D TSN, 5G System (5GS) bridge management for Time-Sensitive Networking (TSN), TSC, sidelink relay TSC, and other specifications-compliant functions. The SMF can select other functions for the PDU session, not limited to those discussed herein. In some implementations, the SMF can determine whether two UEs 104 (e.g., UE1 and UE2) sharing a connection to the same UPF (e.g., a first core network entity) (e.g., communications coupled to that UPF) can discover each other.

[0074] In some implementations, the SMF can check, determine, or confirm the existence of two UEs that can discover each other. Subsequently, the SMF can select the same UPF for these two UEs.

[0075] The SMF can send one or more of the following information to the UPF (e.g., included in the PFCP session establishment request): UE ID (e.g., DST L2 ID, 5G-TMSI, SUPI); TSC information for one or more UEs; peer UE ID; peer UE's TSC information; and measurements of the D2D link with the peer UE (e.g., RSRP, RSRI, CSI, CBR, etc.). Within the PFCP session establishment request, bridge information for TSC is created, where the bridge information indication (BII) bit is set to "1". The UPF can assign port numbers to the UE's DSTT and / or the UE's peer DSTT and report these port numbers to the SMF along with at least one of the following: bridge ID; user plane node ID; and / or NW-TT port number. The identifiers of the 5GS bridge and / or user plane node, as well as the UPF and / or NW-TT port, can be pre-configured in the UPF. The UFP can perform the D2D port pair selection process.

[0076] In various implementations, during operation 404 of establishing a PDU session, the SMF (e.g., a second core network entity) may receive / obtain / acquire TSC information from the UE and / or UPF. The TSC information may include, but is not limited to, at least one of the following: UE-to-device-side (DS) TSN converter (TT) (DS-TT) (UE-DS-TT) dwell time (e.g., the time for transmitting packets between the UE and the DS-TT port) and / or the DS-TT MAC address of the PDU session; port management information or capabilities from the DS-TT and / or UE in the PDU session establishment request; and / or the port number of the DS-TT Ethernet port assigned to each sidelink UE (e.g., UE1 and / or UE2); and / or the user plane node identifier / identifier (ID) (e.g., bridge ID) in the N4 (e.g., UPF-SMF) session establishment response message (e.g., sometimes broadly referred to as a response or reply to the session establishment request). Each UE 104 (e.g., UE1 and / or UE2) may have a corresponding DS-TT Ethernet port.

[0077] SMF can send the following information to UE 104 (included in the PDU session establishment response or modification): the port number of the DS-TT Ethernet port assigned to each D2D UE; the user plane node ID; and / or the bridge ID, etc.

[0078] In operation 406, an Application Function (AF) (e.g., a third core network entity) may subscribe to one or more notifications regarding updated TSC user plane node information (e.g., TSC information) via or through the PCF. By subscribing to notifications, in response to updated TSC information including user plane node information, the AF may receive at least one notification (e.g., indication or signal) and / or information from one or more entities or functions via the PCF. For example, the SMF may send / transmit / provide information including the TSC information obtained in operation 404 to the AF via the PCF to establish / configure and / or modify / update / change / alter the 5GS bridge.

[0079] In some implementations, the SMF can determine that two sidelink UEs that can connect to each other can become (or form) a pair of ports. For example, the SMF can determine that UE1 and UE2 (e.g., a first wireless communication device and a second wireless communication device) can form a sidelink port pair. In this case, in response to determining that the two sidelink UEs can become a pair of ports, the SMF can, for example, report the sidelink port pair to at least one other core network entity (e.g., the PCF and / or AF). In some implementations, the SMF (e.g., a second core network entity) can report / indicate all candidate TSC UE information (e.g., information about at least one candidate TSC UE such as UE1 and / or UE2) to the AF (e.g., the TSC-AF or a third core network entity). The SMF can perform the reporting to the AF via / through the PCF (e.g., a fourth core network entity). In response to this report, the AF can determine or decide which two of the individual UEs 104 are bound to or can form a sidelink port pair.

[0080] When new TSC user plane node information becomes available, the SMF can request an update to the SM policy association and provide the PCF with information about the conditions that have been met. The policy control request trigger condition "TSN_BRIDGE_INFO" can be met in at least one of the following situations: the SMF detects new candidate peer UE information; the reported peer UE information is unavailable, as reported by UE 104; and / or the SMF detects a new port pair (to name a few).

[0081] The SMF can send at least one of the following information to the PCF (e.g., included in Npcf_SMPolicyControl_Update): TSC information; bridge ID; DSTT-MAC address; DSTT port number; DSTT dwell time; UE ID; TSC information of the peer UE, etc. In some implementations, if the peer UE 104 is associated with UE 104 (e.g., the peer UE and UE 104 can form a port pair), the SMF can include the TSC information of the peer UE.

[0082] The AF can store the binding relationship between the 5GS user plane node ID and the DS-TT Ethernet port MAC address or IP address of UE1 (e.g., the first wireless communication device), or the IP address of UE2 (e.g., the second wireless communication device). The binding relationship can refer to the association or information between the 5GS user plane node ID, IP address, or DS-TT Ethernet port MAC address in this context. The AF can update / modify the 5GS latency for various configurations (e.g., existing or new configurations).

[0083] The AF can store port pair information, such as UE ID and bridge information of the peer UE. The AF can perform D2D port pair selection procedures.

[0084] TSN-AF can calculate / compute D2D port pair latency based on or according to at least one of the following: DSTT dwell time or pre-configured dwell time of UE-1; DSTT dwell time or pre-configured dwell time of peer UE-2; and / or minimum and maximum latency per traffic class between UEs 104 (e.g., between UE1 and UE2).

[0085] The AF can use the Npcf_PolicyAuthorization_Create operation or command to request the creation of a new AF session associated with the MAC address of the DS-TT Ethernet port, the MAC address of any one of the two UE 104s (e.g., UE1 and / or UE2), and / or the MAC addresses of both UE 104s. The AF can use the Npcf_PolicyAuthorization_Subscribe operation or command to subscribe to or request updates about TSC events on the newly created AF session.

[0086] Using the 5GS user plane node ID (e.g., received in response to the delivery of an Npcf_PolicyAuthorization_Notify message), the AF can subscribe to the network-side TSN converter (NW-TT) to receive / receive changes to the user plane node management information of the 5GS bridge indicated by the 5GS user plane node ID (e.g., according to the specification). After / after receiving a user plane node management information container (UMIC) that includes / contains / contains one or more NW-TT port numbers, or in response to receiving a UMIC, the AF can subscribe to the NW-TT to receive changes to the NW-TT port management information of the NW-TT ports indicated by the respective NW-TT port numbers (e.g., according to the specification).

[0087] In various arrangements, the AF (e.g., TSN AF or TSC TSF) can use / utilize any PDU session (e.g., one or more PDU sessions) to subscribe to bridge notifications and / or port management information notifications to NW-TT. For example, depending on the subscription, the AF can receive notifications from other entities or functions (e.g., from the UPF) regarding bridge and / or port management information. This notification may include indications of at least one change / modification / update to: the bridge; and / or port management information; and / or other data related to the bridge and / or port management information. In some aspects, the UPF can use any PDU session to send / transmit bridge notifications and / or port management information notifications to other entities and / or functions (e.g., the AF). In some configurations, the UPF may have or subscribe to NW-TT.

[0088] In Operation 408, if the DS-TT has indicated / notified support for the TSN time domain number in its port management capabilities (or if support for the TSN time domain number is part of the port management capabilities), the AF can provide the TSN time domain number to the DS-TT. In some cases, the AF can provide the TSN time domain number to the NW-TT. For example, the AF can provide the TSN time domain number to both the DS-TT and the NW-TT. In another example, the AF can provide the time domain number to either the DS-TT or the NW-TT, such as providing the time domain number only to the DS-TT and not to the NW-TT.

[0089] In operation 410, if the time domain number is supported based on the port management capabilities received from DS-TT, the AF can retrieve / obtain, but is not limited to, at least one of the following from DS-TT: txPropagationDelay (e.g., a value corresponding to the amount of time from when the signal is sent to when it is received); and / or the traffic category table. In some cases, the AF can retrieve / obtain txPropagationDelay and / or the traffic category table from NW-TT. In some other cases, the AF can retrieve / obtain txPropagationDelay and / or the traffic category table from at least one other network device or multiple network devices (e.g., from both DS-TT and NW-TT).

[0090] In various configurations, for the TSN time domain, the distribution of the TSN master clock (grantmaster, GM) time to / to NW-TT and / or DS-TT can precede or precede the AF retrieval of the txPropagationDelay being activated / executed / initiated. In this case, by activating the distribution of the TSN GM time before the AF retrieves the txPropagationDelay, DS-TT and / or NW-TT can convert the txPropagationDelay from 5GS time to TSN time before reporting / notifying the AF of the txPropagationDelay.

[0091] In Operation 412, if DS-TT supports neighbor discovery based on the port management capabilities received from DS-TT, the AF can provide DS-TT with DS-TT port neighbor discovery configuration to configure and / or activate the link layer discovery protocol (LLDP) agent in DS-TT. In this case, the AF can subscribe to receive neighbor discovery information (e.g., including updates / changes to neighbor discovery information) for each discovered neighbor of DS-TT (e.g., according to the specification).

[0092] In some cases, DS-TT may not support neighbor discovery. In such cases, the AF can provide the NW-TT with the DS-TT port neighbor discovery configuration for configuration. In response to providing the DS-TT port neighbor discovery configuration, the AF can activate / initiate or command the LLDP agent in the NW-TT to perform neighbor discovery, for example, on behalf of or in place of the DS-TT. The AF can subscribe to receive neighbor discovery information for each discovered neighbor from the DS-TT (e.g., according to the specification). The neighbor discovery information for each discovered neighbor can be included in the TSC information to be reported to the AF.

[0093] In some cases, if DS-TT-1 does not support neighbor discovery, the AF can perform at least one of the following: • Provide DS-TT-1 port neighbor discovery configuration to DS-TT-2 connected to DS-TT-1, in order to configure and activate / initiate the LLDP agent in NW-TT to perform neighbor discovery on behalf of DS-TT-1.

[0094] • Subscribe to receive neighbor discovery information for each discovered neighbor from DS-TT-1 from DS-TT-2.

[0095] In some other cases, if DS-TT-1 does not support neighbor discovery, the AF may perform at least one of the following: • Provide the DS-TT-1 port neighbor discovery configuration to NW-TT to configure and activate the LLDP agent in NW-TT to perform neighbor discovery on behalf of (or on behalf of) DS-TT-1; • Subscribe to receive neighbor discovery information for each discovered neighbor from NW-TT to DS-TT-1.

[0096] If the LLDP message is received by DS-TT-1, then DS-TT-1 can transmit the LLDP message to DS-TT2. For example, DS-TT-2 can process the LLDP message based on DS-TT-2's capabilities or support (e.g., if DS-TT-2 is capable), or transmit the LLDP message along with DS-TT1's UE ID to NW-TT (e.g., if DS-TT-2 is not capable).

[0097] In various configurations, the AF can write to or provide NW-TT port neighbor discovery configurations for configuration. In response to writing NW-TT port neighbor discovery configurations, the AF can activate the LLDP agent in NW-TT. The AF can subscribe to receive neighbor discovery information for each discovered neighbor in NW-TT.

[0098] In operation 414, the AF may receive one or more notifications (e.g., included in TSC information) regarding discovered neighbors from DS-TT and / or NW-TT, such notifications originating from at least one of DS-TT (e.g., where DS-TT supports neighbor discovery) and / or NW-TT. Notifications from DS-TT and / or NW-TT may include neighbor discovery information, bridge management information, and / or port management information, or other types of information not limited to those discussed herein. In operation 416, in response to receiving a notification, the AF may construct, process, or form the received information from DS-TT and / or NW-TT into 5GS information or TSC information. The AF may send / forward / provide the constructed information to the Central Network Controller (CNC) (e.g., an external control plane node) to register a new TSN bridge or update an existing TSN bridge based on that information.

[0099] TSC Configuration refer to Figure 5 This document depicts a flowchart 500 illustrating an example TSC configuration (e.g., steps / procedures / operations for configuring a TSC). One or more operations of flowchart 500 can be used in conjunction with the methods described herein. Figures 1 to 2 It can be implemented using any one or more components and devices described in detail. For example, certain operations of flowchart 500 may incorporate or include information associated with one or more operations of flowchart 500, such as... Figure 5As described herein. In some embodiments, one or more operations of flowchart 500 may be performed by at least one wireless communication device (e.g., UE or terminal device), at least one wireless communication node (e.g., BS, gNB, RAN, or access network device), at least one core network entity (e.g., SMF, PCF, AF, etc.), at least one satellite, etc. Depending on the embodiment, flowchart 500 may perform or include more, fewer, or different operations. For example, the operations of flowchart 500 may include, but are not limited to, operations 502 through 518. One or more operations of flowchart 500 may be performed or arranged in a different order or sequence, not limited to the order discussed herein. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0100] For 5GS integrated with a (fully) centralized TSN network model, the Central Network Controller (CNC) (e.g., an external control node) can provide / transmit TSC configuration to the AF (e.g., a TSN AF or a third core network entity). For example, in Operation 502, as described in the specification or predefined in the configuration, the CNC can provide the AF with per-flow filtering and / or policing parameters / criteria / conditions. The CNC can provide the AF with other parameters, not limited to per-flow filtering and / or policing parameters. The AF can use these one or more parameters to derive or determine TSC Quality of Service (QoS) parameters and / or related flow information. For example, according to the specification, the CNC can provide the AF with at least one (e.g., predefined) forwarding rule. The AF can use the information derived from these one or more parameters to identify the DS-TTMAC address or IP address of at least one of the UEs (e.g., UE1 and / or UE2) for the corresponding PDU session.

[0101] In various configurations, the AF can determine whether a flow is a UE-UE TSC. Based on the determination of whether a flow is a UE-UE TSC (e.g., whether the flow is UE-UE TSC), the AF can segment / separate or filter the flow into UL flows and / or DL ​​flows and / or D2D flows for one or more PDU sessions (e.g., existing or established PDU sessions) (e.g., in the case of a UE-UE TSC flow), and / or one or more sidelink (SL) flows corresponding to one or more ingress DS-TT Ethernet ports and / or one or more egress DS-TT ports. Subsequently, the AF can trigger or perform (e.g., trigger separately or individually) one or more of the following operations (e.g., one or more of operations 504 to 518) for the UL flow, DL flow, and / or SL flow.

[0102] In Operation 504, for an SL flow, the AF can identify the sending UE (Tx UE) and / or receiving UE (Rx UE) of at least one of one or more SL flows. The AF can determine the MAC address or IP address of at least one PDU session based on or according to previously stored associations. In response to determining the MAC address or IP address, the AF can trigger an AF request procedure, for example, by sending an AF request to the PCF. The AF request may include the DS-TT MAC address or IP address of the PDU session. The AF request can be used to create a new AF session. For example, the AF can request the creation of a new AF session associated with at least one of the first MAC address of UE1 and / or the second MAC address of UE2.

[0103] Based on information received from the CNC (e.g., 5GS bridge delay information (e.g., per-port-pair delay) and / or UE-DS-TT dwell time, the AF can determine the TSC QoS parameters and / or TSC auxiliary containers for one or more TSC flows. The AF can then send the TSC configuration to the PCF. The AF can, for example, provide the PCF with at least one service flow filter, which includes / contains / contains flow descriptions and / or at least one of Ethernet packet filters or IP packet filters.

[0104] TSC configuration may include at least one of the following: UE ID; peer UE ID; TSC QoS parameters; or data flow filters (e.g., Ethernet packet filters, IP packet filters, etc.); TSCAI and / or TSC auxiliary containers; QoS flow ID; TSC QoS parameters, etc.

[0105] In operation 506, when the PCF receives an AF request (e.g., from the AF), the PCF can identify / find or search for the SMF (e.g., the correct or expected SMF) based on the DS-TT MAC address or IP address of the PDU session. In response to identifying the SMF, the PCF can notify the SMF of the TSC configuration via an Npcf_SMPolicyControl_UpdateNotify message / signaling or other types of signaling. In some implementations, in response to receiving QoS information from the AF, the PCF can, for example, map received TSC QoS parameters from one or more TSC flows to 5GS QoS parameters or profiles (e.g., PQI).

[0106] In Operation 506, when the PCF receives an AF request, the PCF can identify / find or search for the UE (e.g., the correct or expected SMF) based on the DS-TT MAC address or IP address of the PDU session. In response to identifying the SMF, the PCF can notify the UE of the TSC configuration via a UE policy container message / signaling or other type of signal. The TSC configuration can include at least a UE policy. UE policies can include, but are not limited to, at least one of TSCAI, TSC Auxiliary Container (TSCAC), time-domain and / or data packet filters. In response to the peer UE not having a network connection, the UE can transmit the TSC configuration to that peer UE.

[0107] TSC QoS parameters may include, but are not limited to, at least one of the following: maximum burst size of TSC traffic; TSC traffic latency; and / or priority of TSC traffic relative to other TSC and / or non-TSC traffic. 5GS QoS parameters or profiles may include, but are not limited to, at least one of the following: 5G QoS flow identifier (5QI); PC5 5QI (PQI); allocation and retention priority (ARP), etc.

[0108] A TSC assistance container (TSCAC) may include, but is not limited to, at least one of the following: flow direction (e.g., the direction of the TSC flow, such as uplink (UL), downlink (DL), D2D link, and / or sidelink); period (e.g., sometimes referring to the time interval between the start of two data bursts); burst arrival time (e.g., the time when the first packet of a data burst arrives at a 5GS ingress port for a given flow direction, such as DS-TT for uplink (e.g., ingress DS-TT) and NW-TT for downlink (e.g., ingress DS-TT)); lifetime (e.g., sometimes referring to the time interval during which an application can survive without any data bursts); time domain (e.g., the generalized precision time protocol of the TSC flow). Protocol (gPTP) domain); Burst arrival time window (e.g., sometimes called BAT time window, which can indicate the earliest and / or latest arrival time acceptable for the first packet of a data burst to arrive at a 5GS ingress port for a given flow direction, such as DS-TT for uplink or NW-TT for downlink); BAT adaptation capability (e.g., indicating that the AF will adjust the burst transmission time according to the burst arrival time offset provided by the network); period range (e.g., indicating that the AF will adjust the period and provide an acceptable range, such as a lower and upper limit of the period); and / or one or more acceptable period values ​​(e.g., represented as a list of period values).

[0109] TSC assistance information (TSCAI) may include at least one of the following: flow direction; cycle time; burst arrival time; survival time; burst arrival time (BAT) window; BAT adaptation capability; N6 jitter information; cycle range, etc.

[0110] After mapping the received TSC QoS parameters of the TSC flow to 5GS QoS, the PCF can trigger an Npcf_SMPolicyControl_UpdateNotify message to update or configure Policy and Charging Control (PCC) rules to the SMF. PCC rules may include at least the following items for implementing / allowing detection of policy control or appropriate charging for service-facing data flows: one or more packet filters; a 5GS QoS profile; a TSC auxiliary container; or other information.

[0111] In some implementations, in response to receiving an AF request for creating a new AF session, the PCF may send flow descriptions / information (e.g., IP information, etc.), TSC (or TSCAI), peer UE ID, or other information to at least one of the UEs 104 (e.g., a sidelink UE). Upon receiving CNC configuration, the AF may, for example, identify or determine traffic between UEs 104 (e.g., traffic from UE1 to UE2 and / or traffic from UE2 to UE1) as a type of UE-to-UE (e.g., U2U) TSN traffic identifier. For example, the AF (e.g., a third core network entity) may identify device-to-device traffic, such as traffic between UE1 and UE2. Based on the device-to-device traffic, the AF may divide / separate the traffic into a first flow from UE1 to UE2 and a second flow from UE2 to UE1.

[0112] The AF can provide / send messages to the PCF. These messages may include at least one of the following for UE1 and / or UE2: UE ID (e.g., DSTT-MAC address); flow description (e.g., direction may be for the sidelink and / or peer UE ID and / or port ID); one or more QoS parameters; and one or more TSC QoS parameters (e.g., TSCAI or TSC container SL). Direction may refer to data transmission direction, such as at least one of uplink (e.g., UE 104 to the network), downlink (e.g., network to UE 104), and / or sidelink (e.g., one UE to another). In this scenario, the AF can interact with the PCF by configuring the sidelink UE. For example, configuration information can be sent to the network exposure function (NEF). Subsequently, the NEF can forward the configuration information to the PCF, and the PCF can forward the configuration information to UE 104 (e.g., UE1 and / or UE2). In this scenario, the PCF can use the DSTT-MAC address to identify the sidelink UE. The information exchanged between AF and NEF or between NEF and PCF includes at least one of the following: TSC configuration.

[0113] During Operation 508, the SMF can trigger a PDU session modification procedure to establish / modify a QoS flow for transmitting a TSC flow. During Operation 508, the SMF can, for example, provide the UPF with information from the received PCC rules via the N4 session modification procedure.

[0114] In some implementations, when the SMF (e.g., a second core network entity) receives a TSC auxiliary container, the SMF can determine the TSCAI of a QoS flow (e.g., a D2D QoS flow). In response to determining the TSCAI of the QoS flow, the SMF can send / transmit / provide the TSCAI and QoS profile to the BS 102 (e.g., a gNB, a wireless communication node, or a next-generation (NG) RAN).

[0115] In some configurations, BS 102 can be configured to send TSCAI to UE 104. TSCAI can be associated with at least a QoS flow, a data radio bearer (DRB), a radio link control (RLC) channel, and / or a configured grant (CG). For example, UE 104 can be configured with a radio bearer configuration including TSCAI, an RLC channel configuration including TSCAI, a configured grant configuration including TSCAI, QoS parameters for a QoS flow including TSCAI, etc. SMF can be configured to map at least one of the following from an external clock (e.g., when available): a burst arrival time (BAT) window, period and / or period range, or other information, based on (e.g., as measured and / or reported by UPF) the time offset between the external clock time and the 5GS time and / or the cumulative rate ratio (e.g., when available). In various implementations, SMF can determine or be configured to determine TSCAI according to a specification. In some implementations, the SMF can be configured to send the TSCAI associated with the QoS flow to the UE 104 (e.g., instead of the BS102) after the SMF sends the TSCAI and QoS profile to the BS 102.

[0116] In Operation 510, in some configurations, the CNC can provide additional information to the AF. This additional information may include, but is not limited to, a gating list. The gating list can be predetermined or predefined according to the specification.

[0117] In Operation 512, the AF can determine the MAC address or IP address of the PDU session for the configured port based on previously / historically stored associations. The determined MAC address or IP address of the PDU session can be used to: pass / transmit / convey port management information via the PCF to the expected SMF managing the port (e.g., corresponding to the MAC address). The AF can trigger an AF request procedure. The AF request may include a DS-TT MAC address or IP address (e.g., the MAC address or IP address of the PDU session), one or more TSN QoS parameters, a port management information container, and / or the relevant port number as indicated in the specification. The port number can be used by the SMF to determine whether the configured port is in DS-TT and / or NW-TT or whether it is used for DS-TT and / or NW-TT.

[0118] In various respects, when the AF is configured to communicate 5GS bridge-specific information and / or NW-TT port-specific information to the NW-TT and / or UPF, the AF can select / choose at least one AF session (e.g., any or random AF session) associated with the corresponding 5GS bridge. After selection, the AF can send the 5GS bridge-specific information via the User Plane Node Management Information Container (UMIC) and / or the NW-TT Port Management Information Container (NW-TT PMIC).

[0119] In operation 514, the PCF can determine the SMF based on a MAC address or IP address received via an AF request (e.g., at least from operation 512). The PCF can map TSN QoS information provided by the AF to one or more PCC rules. The PCF can receive or store the obtained TSC auxiliary container and one or more PCC rules from the AF. The PCF can forward the TSC auxiliary container (e.g., along with one or more PCC rules) to the SMF. The PCF can transparently transmit / forward the received port management information container and / or associated port number to the SMF via an Npcf_SMPolicyControl_UpdateNotify message or other types of signaling / messages. In some implementations, if sidelink data is received, the PCF can directly send configuration information to the sidelink UE. In this case, under the sidelink architecture, the configuration information may not go through the SMF. This document can provide non-limiting examples of TSC management information containers.

[0120]

[0121] Example TSC information container In operation 516, in some implementations, if the SMF determines that the port is on the DS-TT based on the received port number, the SMF may send / forward / transmit the received port management information container to UE 104 and / or DS-TT in a PDU session modification request message. The port management information container (PMIC) may be a predefined container that includes port management information, such as as described in the specification.

[0122] In Operation 518, if the SMF determines / determines that the port is on the NW-TT based on the received port number, the SMF may transmit the received port management information container to the UPF and / or NW-TT via / through an N4 Session Modification Request Message / signaling or other type of signaling, or within an N4 Session Modification Request Message / signaling or other type of signaling. In some cases, the SMF may provide one or more Ethernet packet filters to the UPF and / or NW-TT as part of the N4 packet detection rules.

[0123] In some implementations, if the UPF sends a clock drift report to the SMF, the SMF can update / modify / change / adjust the burst arrival time, period, and / or lifetime (e.g., if present or available) from the TSN master clock to the 5G clock. In response to this adjustment, the SMF can send an updated TSCAI to BS 102 (e.g., NG RAN). In some arrangements, for, but not limited to, for at least one of operations 516 and / or 506, upon receiving a TSC auxiliary container, the SMF can determine the TSCAI of the QoS flow and send the TSCAI along with the QoS profile to BS 102.

[0124] In some configurations, NG RAN and / or radio bearer (RB) configurations (e.g., survivalTimeStateSupport = true, EthernetHeaderCompression, etc.) can be provided to UE 104 based on TSCAI (e.g., periodicity, burst arrival time, survival time, etc.) and / or QoS profiles (e.g., 5QI, packet delay budget (PDB), etc.). BS 102 (e.g., NG RAN or RB) can provide configurations to UE 104 and other UE 104 devices. For example, BS 102 can provide configuration grants (CG) to UE 104.

[0125] In some implementations, after receiving sidelink flow information / description, TSCAI, and / or peer UE ID, the sidelink UE can establish a unicast link with the indicated peer UE. The sidelink UE can establish a QoS flow based on the sidelink flow information. The sidelink UE can bind the TSCAI to the established QoS flow. The sidelink UE can send / transmit at least one sidelink UE information (SUI) message to the network, which includes, but is not limited to, the TSCAI associated with the QoS flow.

[0126] Figure 6 A flowchart of an example method 600 for reference signaling design and configuration is shown. Method 600 can be used in conjunction with the methods described herein. Figures 1 to 4 The method is implemented by any one or more components and devices described in detail. In brief, in some embodiments, method 600 may be performed by at least one wireless communication device (e.g., UE or terminal device), at least one wireless communication node (e.g., BS, gNB, NG RAN, or access network device), at least one core network entity (e.g., PCF, SMF, AF, etc.), at least one satellite, etc. Depending on the embodiment, more, fewer, or different operations may be performed in method 600. At least one aspect of these operations relates to a system, method, apparatus, or computer-readable medium.

[0127] In operation 602, a first wireless communication device (e.g., the first wireless communication device or UE1) among a plurality of wireless communication devices may, for example, initiate / start / execute a procedure or process to establish a first Protocol Data Unit (PDU) session, which includes candidate-side transit time-sensitive communication (TSC) user equipment (UE) information (e.g., TSC UE identifier (ID)). The TSC UE information may include other non-limiting information, such as at least one of the following: UE ID (e.g., DST L2ID, Temporary Mobile Subscriber Identifier (TMSI), Subscription Permanent Identifier (SUPI), DS-TT MAC address, etc.); bridge ID; UPF ID; user plane node ID; number of DS-TTs; number of ports; port number; support for the counterpart transit TSN; DS-TT MAC address; UE-DS-TT dwell time; port management capabilities; whether at least one wireless communication device (e.g., UE) is capable of performing neighbor discovery on behalf of at least one peer wireless communication device, etc.

[0128] In operation 604, the first wireless communication device may be communicatively coupled to a first core network entity (e.g., UPF) among multiple core network entities. For example, the first wireless communication device may be coupled to the first core network entity via / through a first PDU session after a first session is established.

[0129] In some implementations, a second core network entity (e.g., SMF) can determine whether a first wireless communication device (e.g., UE1) and a second wireless communication device (e.g., UE2, sometimes referred to as the second wireless communication device) among the plurality of wireless communication devices can discover / detect each other. In response to determining that the first wireless communication device and the second wireless communication device (e.g., connected to the first core network entity) can discover each other, the second core network entity can select the first core network entity for both the first wireless communication device and the second wireless communication device.

[0130] In some implementations, a second core network entity (e.g., SMF) can determine whether a first wireless communication device and a second wireless communication device among the plurality of wireless communication devices can discover each other, the first and second wireless communication devices being communicatively coupled to the first core network entity. In some implementations, the first core network entity may have a network-side TSN converter (NW-TT), and each of the first and second wireless communication devices has a corresponding DS-TT Ethernet port. In this case, the DS-TT may be located within or on the UE side (e.g., the first and second wireless communication devices), and the NW-TT may be located on the UPF side (e.g., the first core network may have a corresponding NW-TT device).

[0131] In some implementations, the second core network entity can determine which two wireless communication devices are capable of forming a sidelink port pair. In some implementations, the first core network entity can report all time-sensitive communication (TSC) information about the candidate TSC UE to a third core network entity (e.g., AF or TSN-AF) via a fourth core network entity (e.g., PCF), enabling the third core network entity to determine which two of the plurality of wireless communication devices are capable of forming a sidelink port pair.

[0132] In some implementations, the third core network entity can determine whether a flow is a UE-UE TSC and classify the flow into one or more side-link flows. In some implementations, the third core network entity can identify the transmitting UE (Tx UE) and / or receiving UE (Rx UE) of at least one of the one or more side-link flows.

[0133] In some implementations, a third core network entity may request (e.g., an AF request) to create a new AF session, which is associated with at least one of the following: a first MAC address of a first wireless communication device; and / or a second MAC address of a second wireless communication device among the plurality of wireless communication devices. In some implementations, a fourth core network entity (e.g., a PCF) may, in response to receiving a request to create a new AF session, send / provide / provide at least one of the following to at least one of the plurality of wireless communication devices: a transport flow description, TSC QoS parameters, and / or the peer UE ID.

[0134] In some implementations, the third core network entity can identify device-to-device (e.g., UE-to-UE) traffic and classify that traffic into first traffic from a first wireless communication device to a second wireless communication device and / or second traffic from the second wireless communication device to the first wireless communication device. In some implementations, the third core network entity can send a message to a fourth core network entity, the message including at least one of the following for the first and second wireless communication devices, respectively: UE ID; flow description; one or more QoS parameters; and / or TSC QoS parameters.

[0135] While various embodiments of the solution have been described above, it should be understood that these embodiments are presented by way of example only and not as limitations. Similarly, various accompanying drawings may depict exemplary architectures or configurations, provided to enable those skilled in the art to understand exemplary features and functionality of the solution. However, those skilled in the art will understand that the solution is not limited to the exemplary architectures or configurations shown, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited to any of the illustrative embodiments described above.

[0136] It should also be understood that any references to elements using identifiers (such as "first" and "second") in this document generally do not restrict the number or order of these elements. Rather, these identifiers are used herein as a convenient means of distinguishing two or more elements or instances of elements. Therefore, a reference to the first element and the second element does not imply that only two elements can be used, or that the first element must precede the second element in some way.

[0137] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0138] Those skilled in the art will also recognize that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in connection with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code in conjunction with instructions (which may be referred to herein as "software" or "software module"), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, these components, blocks, modules, circuits, and steps have been generally described above in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not lead to a departure from the scope of this disclosure.

[0139] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or executed by an integrated circuit (IC), which may include: 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, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communication with various components within a network or device. A general-purpose processor may be a microprocessor, but alternatively, it may be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of multiple computing devices, such as a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a DSP core, or any other suitable configuration that performs the functions described herein.

[0140] If these functions are implemented in software, they can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. A computer-readable medium can include computer storage media and communication media, with communication media including any medium capable of transferring computer programs or code from one location to another. A storage medium can be any available medium accessible to a computer. For example, but not limited to, such a computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage devices, disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.

[0141] In this document, as used herein, the term "module" refers to software, firmware, hardware, and any combination of these elements used to perform the associated functions described herein. Furthermore, for purposes of discussion, various modules are described as discrete modules; however, as will be apparent to those skilled in the art, two or more modules may be combined to form a single module that performs the functions associated with embodiments of this solution.

[0142] Additionally, embodiments of this solution may employ memory or other storage devices, as well as communication components. It will be understood that, for clarity, the above description has referenced various functional units and processors in its depiction of embodiments of this solution. However, it will be apparent that any suitable functional distribution can be used across different functional units, processing logic elements, or domains without diminishing the effectiveness of this solution. For example, functions shown to be performed by separate processing logic elements or controllers may be performed by the same processing logic element or controller. Therefore, references to specific functional units are merely references to appropriate means of providing the described functions and do not indicate a strict logical or physical structure or organization.

[0143] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein can be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is intended to be accorded the broadest scope consistent with the inventive features and principles disclosed herein as set forth in the following claims.

Claims

1. A wireless communication method, comprising: A first wireless communication device among multiple wireless communication devices initiates the establishment of a first protocol data unit (PDU) session, the first PDU session including the candidate-side time-sensitive communication (TSC) user equipment (UE) identifier (ID); The first wireless communication device is coupled to the first core network entity through the first PDU session communication.

2. The wireless communication method according to claim 1, wherein, The second core network entity is configured to determine whether the first wireless communication device and the second wireless communication device among the plurality of wireless communication devices can discover each other, and to select the first core network entity for both the first wireless communication device and the second wireless communication device.

3. The wireless communication method according to claim 1, wherein, The second core network entity is configured to determine whether the first wireless communication device and the second wireless communication device among the plurality of wireless communication devices can discover each other, wherein the first wireless communication device and the second wireless communication device are communicatively coupled to the first core network entity.

4. The wireless communication method according to any one of claims 2 or 3, wherein, The first core network entity has a network-side TSN converter (NW-TT), and each of the first wireless communication device and the second wireless communication device has a corresponding DS-TT Ethernet port.

5. The wireless communication method according to claim 2 or 3, wherein, The second core network entity is configured to determine that the first wireless communication device and the second wireless communication device can form a sidelink port pair.

6. The wireless communication method according to claim 1, wherein, The second core network entity is configured to report all TSC information about candidate Time Sensitive Communication (TSC) UEs to the third core network entity via the fourth core network entity, such that the third core network entity determines which two of the plurality of wireless communication devices can form a sidelink port pair.

7. The wireless communication method according to claim 6, wherein, The third core network entity is configured to determine whether a flow is a UE-to-UE TSC and to divide the flow into one or more sidelink flows.

8. The wireless communication method according to claim 7, wherein, The third core network entity is configured to identify the transmitting UE and receiving UE of at least one of the one or more sidelink flows.

9. The wireless communication method according to claim 6, wherein, The third core network entity is configured to request the creation of a new AF session, the new AF session being associated with at least one of the following: the first MAC address of the first wireless communication device; or the second MAC address of the second wireless communication device among the plurality of wireless communication devices.

10. The wireless communication method according to claim 9, wherein, The fourth core network entity is configured to, in response to receiving a request to create the new AF session, send at least one of the following to at least one of the plurality of wireless communication devices: a flow description, a TSC QoS parameter, or a peer UE ID.

11. The wireless communication method according to claim 9, wherein, The third core network entity is configured to identify device-to-device traffic and to divide the traffic into a first flow from the first wireless communication device to the second wireless communication device and a second flow from the second wireless communication device to the first wireless communication device.

12. The wireless communication method according to claim 11, wherein, The third core network entity is configured to send a message to the fourth core network entity, the message including at least one of the following for the first wireless communication device and the second wireless communication device respectively: UE ID; flow description; one or more QoS parameters; or TSC QoS parameters.

13. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 12.

14. A computer program product comprising computer-readable program medium code stored thereon, the computer-readable program medium code, when executed by a processor, causing the processor to implement the method according to any one of claims 1 to 12.