Method for supporting deterministic networks in wireless communication networks

Abstract

A wireless communication device is provided for communicating with a wireless communication network, the wireless communication device comprising a transceiver configured to send a request to the wireless communication network, the request comprising first information for setting up a user plane connection for deterministic network traffic.

Description

TECHNICAL FIELD

[0001] The subject matter disclosed in the present specification generally relates to the field of implementing support for layer 3 deterministic networks in 5G systems. BACKGROUND ART

[0002] 3GPP (registered trademark) has defined support for deterministic networks from Release 17.

[0003] Release 17 supports layer 2 deterministic networks (i.e., IEEE Time Sensitive Networking based on the IEEE 802.1q standard).

[0004] Accordingly, while the existing support for 3GPP systems to route deterministic network traffic is based on Ethernet / layer 2-based interfaces, IETF networks use IP connectivity / layer 3-based interfaces. SUMMARY OF THE INVENTION PROBLEMS TO BE SOLVED BY THE INVENTION

[0005] A problem with the suggested procedures for setting up connections with specific quality of service requirements affecting 3GPP systems is that such procedures do not provide functionality for a deterministic network controller to identify and / or discover suitable user equipment, and for the 3GPP network to be configured to support suitable connections for deterministic traffic.

[0006] Procedures for supporting layer 3 deterministic networks in 5G systems are disclosed herein. The procedures may be implemented by the apparatuses and architectures described in the present specification. MEANS FOR SOLVING THE PROBLEMS

[0007] A wireless communication device is provided for communicating with a wireless communication network, the wireless communication device comprising a transceiver configured to send requests to the wireless communication network, the requests comprising first information for setting up a user plane connection for deterministic network traffic.

[0008] A method is further provided for a wireless communication device, wherein the wireless communication device is configured to communicate with a wireless communication network, and the method comprises sending a request to the wireless communication network, the request comprising first information for setting up a user plane connection for deterministic network traffic.

[0009] Application functionality is further provided in the wireless communication network, and the application functionality comprises a transceiver and a processor. The transceiver is configured to send a subscription request to a first network function of the wireless communication network, which requests notification of the device's network address when the device establishes a user plane connection to support deterministic network traffic, and to receive first information from the first network function, which identifies a first device, which identifies a second network function that supports deterministic network relay node functionality, and to receive deterministic network flow requirements from a deterministic network controller in response to the receipt of the first information. The processor is configured to translate the deterministic network flow requirements into quality of service requirements for relaying deterministic network traffic over the wireless communication network. The transceiver is further configured to send a second request to a second network function to establish a user plane session with the wireless communication network in accordance with the quality of service requirements for relaying deterministic network traffic over the wireless communication network.

[0010] A method in the application functionality of a wireless communication network is further provided. The method comprises sending a subscription request to a first network function of the wireless communication network, wherein the subscription request requests notification of the device's network address when the device establishes a user plane connection to support deterministic network traffic, and receiving first information from the first network function, wherein the first information identifies a first device, and the first information identifies a second network function that supports deterministic network relay node functionality. The method further comprises receiving deterministic network flow requirements from a deterministic network controller in response to the first information, and translating the deterministic network flow requirements into quality of service requirements for relaying deterministic network traffic over the wireless communication network. The method further comprises sending a second request to a second network function to establish a user plane session with the wireless communication network in accordance with the quality of service requirements for relaying deterministic network traffic over the wireless communication network.

[0011] A first network function is further provided in the wireless communication network, the first network function comprising a transceiver. The transceiver is configured to receive a subscription request from an application function of the wireless communication network, the subscription request being a request for notification of the device's network address when the device establishes a user plane connection to support deterministic network deterministic traffic, and to send first information to the application function, the first information identifying a first device, and the first information identifying a second network function supporting deterministic network relay node functionality.

[0012] A method in a first network function of a wireless communication network is further provided. The method comprises receiving a subscription request from an application function of the wireless communication network, the subscription request requesting notification of the device's network address when the device establishes a user plane connection to support deterministic network deterministic traffic. The method further comprises sending first information to the application function, the first information identifying a first device, and the first information identifying a second network function supporting deterministic network relay node functionality.

[0013] User plane functionality is further provided in the wireless communication network, and the user plane functionality comprises a transceiver. The transceiver is configured to receive requests from a session management function to establish a user plane session with the wireless communication network in accordance with at least one quality of service requirement for relaying deterministic network traffic over the wireless communication network. The transceiver is further configured to send a response to the session management function indicating first information, including the deterministic network capability of the user plane functionality.

[0014] A method in the user plane functionality of a wireless communication network is further provided. The method comprises receiving a request from a session management function to establish a user plane session with the wireless communication network in accordance with at least one quality of service requirement for relaying deterministic network traffic over the wireless communication network. The method further comprises sending a response to the session management function indicating first information, including the deterministic network capability of the user plane functionality.

[0015] To illustrate how the advantages and features of this disclosure can be obtained, the description of this disclosure is expressed by reference to several apparatuses and methods shown in the accompanying drawings. Each of these drawings illustrates only a few aspects of this disclosure and should therefore not be considered limiting its scope. The drawings may be simplified for clarity and are not necessarily drawn to a constant scale.

[0016] Methods and apparatus for supporting Layer 3 deterministic networks in 5G systems are described below, merely as examples, with reference to the attached drawings. [Brief explanation of the drawing]

[0017] [Figure 1] This is a schematic diagram of the network architecture for supporting IEEE time-sensitive networking systems in 5G systems. [Figure 2] This is a schematic diagram of the network architecture to support the IETF deterministic network. [Figure 3] This is a schematic diagram of an additional network architecture to support the IETF deterministic network. [Figure 4] This is a schematic diagram of user equipment that may be used to carry out the method described herein. [Figure 5] This is a schematic diagram of network nodes that may be used to implement the methods described herein. [Figure 6] This is a schematic diagram of a further network architecture to support IETF deterministic network relay nodes in 5G systems. [Figure 7] This is a schematic diagram illustrating the procedure for establishing a PDU session to relay deterministic network flows. [Figure 8] This is a schematic diagram illustrating the procedure for configuring a 5G system with appropriate service quality characteristics. [Figure 9]It is a schematic diagram of a further procedure for routing deterministic network flow packets via a Deterministic Network-aware 5G system. [Figure 10] It is a schematic diagram of a still further network architecture for supporting deterministic network flows via a Deterministic Network-unaware 5G system. [Figure 11] It is a process flowchart illustrating a method performed by a wireless communication device in a wireless communication network. [Figure 12] It is a process flowchart illustrating a further method performed by an application function of a wireless communication network. [Figure 13] It is a process flowchart illustrating a still further method performed by a first network function of a wireless communication network. [Figure 14] It is a process flowchart illustrating a still further method performed by a user plane function of a wireless communication network. [Description of Embodiments]

[0018] As will be appreciated by those skilled in the art, aspects of the present disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, the configurations described herein may be implemented entirely in hardware form, entirely in software form (including firmware, resident software, microcode, and the like), or in a form combining software and hardware aspects.

[0019] For example, the disclosed methods and apparatus may be implemented as hardware circuits comprising custom very-large-scale integration (VLSI) circuits or off-the-shelf semiconductors such as gate arrays, logic chips, transistors, or other discrete components. The disclosed methods and apparatus may also be implemented within programmable hardware devices such as field-programmable gate arrays, programmable array logic, or programmable logic devices. As another example, the disclosed methods and apparatus may include one or more physical or logical blocks of executable code, which may be organized as objects, procedures, or functions, for example.

[0020] Furthermore, the methods and apparatus may take the form of a program product embodied in one or more computer-readable storage devices that store machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage devices may be tangible, non-temporary, and / or non-transmitting. The storage devices may not embody signals. In some configurations, the storage devices merely employ signals for accessing the code.

[0021] Any combination of one or more computer-readable media may be used. The computer-readable media may be computer-readable storage media. The computer-readable storage media may be a storage device that stores code. The storage device may be, for example, but not limited to, a system, apparatus, or device of electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor, or any suitable combination thereof.

[0022] More detailed examples (a non-exclusive list) of storage devices include, namely, electrical connections having one or more wires, portable computer diskettes, hard disks, random-access memory ("random-access memory: RAM"), read-only memory ("read-only memory: ROM"), erasable programmable read-only memory ("EPROM" or flash memory), portable compact disc read-only memory ("compact disc read-only memory: CD-ROM"), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the context of this specification, a computer-readable storage medium may be any tangible medium on which a program for use by or relating to an instruction execution system, apparatus, or device can be stored or stored.

[0023] Any reference throughout this specification to an example of a particular method or apparatus, or similar language, means that the particular feature, structure, or characteristic described with that example is included in at least one implementation of the methods and apparatus described herein. Thus, all references to an example of a particular method or apparatus, or similar language, may, but not necessarily, refer to the same example, meaning "one or more, but not all, examples" unless otherwise specified. The terms "including," "comprising," "having," and their variations mean "including, but not limited to," unless otherwise specified. Listings of items do not imply that any or all of the items are mutually exclusive unless otherwise specified. The terms "a," "an," and "the" also mean "one or more" unless otherwise specified.

[0024] As used herein, a list containing the conjunction "and / or" includes any single item in that list, or any combination of items in that list. For example, the list A, B, and / or C includes A only, B only, C only, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one or more of" includes any single item in that list, or any combination of items in that list. For example, one or more of A, B, and C includes A only, B only, C only, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C. As used herein, a list using the term "one of" includes only one of any single items in that list. For example, "one of A, B, and C" includes A only, B only, or C only, excluding the combination of A, B, and C. When used herein, “members selected from the group consisting of A, B, and C” includes a single member from A, B, or C, and excludes any combination of A, B, and C. When used herein, “members selected from the group consisting of A, B, and C, and any combination thereof” includes A only, B only, C only, a combination of A and B, a combination of B and C, a combination of A and C, or a combination of A, B, and C.

[0025] Furthermore, the features, structures, or properties described herein may be combined in any preferred manner. The following description provides numerous specific details, including examples of programming, software modules, user selection, network transactions, database queries, database structures, hardware modules, hardware circuits, and hardware chips, in order to provide a full understanding of the disclosure. However, those skilled in the art will recognize that the disclosed methods and apparatus may be practiced without one or more of these specific details, or using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not illustrated or described in detail to avoid obscuring aspects of the disclosure.

[0026] The methods and apparatuses disclosed are described below with reference to schematic flowcharts and / or schematic block diagrams of the methods, apparatuses, systems, and program products. It will be understood that each block in the schematic flowcharts and / or schematic block diagrams, as well as combinations of blocks within the schematic flowcharts and / or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general-purpose computer, a dedicated computer, or other programmable data processing device to generate a machine, and as a result, instructions executed via the computer or other programmable data processing device processor create means for performing the functions / operations specified in the schematic flowcharts and / or schematic block diagrams.

[0027] The code may also be stored in a memory device that can direct a computer, other programmable data processing device, or other device to function in a particular manner, resulting in the instructions stored in the memory device generating a product containing instructions that perform functions / operations specified in a schematic flowchart and / or schematic block diagram.

[0028] The code may also be loaded onto a computer, another programmable device, or another device to perform a series of operational steps on that computer, another programmable data processing device, or another device in order to generate a computer implementation process, and as a result, the code running on the computer or other programmable device provides a process for performing functions / operations specified in schematic flowcharts and / or schematic block diagrams.

[0029] The schematic flowcharts and / or schematic block diagrams in the drawings illustrate the architecture, functionality, and operation of possible implementations of the device, system, method, and program product. In this regard, each block in the schematic flowcharts and / or schematic block diagrams may represent a module, segment, or portion of code containing one or more executable instructions of code for performing a specified logical function.

[0030] It should also be noted that in some alternative implementations, the functions mentioned within a block may be performed in a different order than those mentioned in the diagram. For example, two blocks shown consecutively may actually be executed substantially in parallel, or blocks may sometimes be executed in reverse order depending on the functionality involved. Other steps and methods may be devised in which the function, logic, or effect is equivalent to one or more blocks or parts thereof in the illustrated diagram.

[0031] The descriptions of elements within each drawing may refer to elements in preceding drawings. Similar numbers refer to the same elements across all drawings.

[0032] 3GPP has specified support for deterministic networks since Release 17. Release 17 supports Layer 2 deterministic networks (i.e., IEEE time-sensitive networking based on the IEEE 802.1Q standard).

[0033] To support IEEE Time-Sensitive Networking (TSN), the 5GS system is configured as a Layer 2 bridge as shown in Figure 1. Figure 1 is identical to Figure 5.28.1-1 of 3GPP TS23.501 v17.4.0 and shows the network architecture 100 for supporting the IEEE TSN system 102 within the 5G system (5GS).

[0034] To support TSN scheduled traffic (section 8.6.8.4 in IEEE Std 802.1Q-2018

[98] ) via the 5GS bridge 104, the 5GS supports the following functions: • Configure the bridge information within the 5GS. After establishing Protocol Data Unit (PDU) session 106, report the bridge information of the 5GS bridge 104 to the TSN network 102. • Receive configuration information from TSN network 102. • Mapping configuration information obtained from the TSN network to 5GS Quality of Service (QoS) information (e.g., 5QI, Time-Sensitive Communication (TSC) support information) of the QoS flow within the corresponding PDU session 108 for efficient time-aware scheduling.

[0035] The Network Side TSN Translator (NW-TT) 110 and Device Side TSN Translator (DS-TT) 112 functions, located in User Plane Function (UPF) 114 and user equipment (UE) 116 respectively, are responsible for calculating propagation delay within 5GS, which is used to synchronize the time-synchronization clock. As part of Release 18, a new approach was agreed upon to support Layer 3 deterministic networks within 5GS systems (in detail, the IETF DetNet standard was agreed upon, as described in IETF RFC8938). A very basic diagram of IETF DetNet support is shown in Figure 2. Figure 2 shows, in detail, a deterministic network (DetNet) aware node, i.e., a service sublayer 200, which receives application packets from source 202 (which is DetNet non-aware) and encapsulates those packets into a DetNet flow 204 having specific deterministic characteristics (e.g., specific QoS, delay tolerance, etc.). The DetNet aware node 200 encapsulates the packets into a DetNet flow 204 based on information (rules) provided by the DetNet controller (not shown in Figure 2). These rules take the form of the DetNet Yang model, as described in draft-ietf-detnet-yang-16. This specification includes specifications for configuration and operational data for DetNet flows, such as DetNet flow 204.

[0036] A DetNet flow may reuse existing headers in the application flow from source 202, or it may use other headers added in the service sublayer 200. The headers may include a DetNet flow ID and may be arranged as metadata or as packet headers.

[0037] The DetNet flow 204 is received by the forwarding sublayer 206, forwarded to the lower layer 208, and then returns to destination 210 via the forwarding sublayer 206 and the service sublayer 200.

[0038] In the forwarding sublayer 206, resources for DetNet flows are allocated to explicit routes as per RFC8938.

[0039] The structure of this disclosure is based on the following assumptions. Only IP-based DetNet is within the scope of this work; Multiprotocol Label Switching (MPLS)-based DetNet is outside its scope. • IP-based DetNet traffic is carried within an IP-type PDU session. (DetNet over Ethernet TSN is not within the scope of this work, as it may be supported based on existing 3GPP and IETF standards.) This solution should reuse the functionality of the TSC framework as defined in Release 17, where applicable. This solution supports requests from DetNet controller entities, including DetNet configuration for establishing flow paths. The time synchronization framework in Release 17 will not be modified because the synchronization mechanism that may be used is outside the scope of the IETF DetNet standard. • Existing 3GPP routing mechanisms can be reused for DetNet, and no new routing functions will be defined in the 3GPP system. Existing filtering mechanisms can be reused within UE116 and UPF114 to identify traffic for QoS differentiation.

[0040] Based on the SID objective, if the network service node is configured as a relay 300 as shown in Figure 3, the following IETF DetNet implementations are supported.

[0041] The IETF DetNet end system 302 may have already encapsulated one or more application flows into a DetNet flow 204, and therefore the relay node 306 forwards the DetNet flow 204 according to the deterministic characteristics of the DetNet flow, as configured with a DetNet controller (not shown in Figure 3).

[0042] Figure 4 shows a UE400 that may be used to carry out the method described herein. The UE400 is used to carry out one or more of the solutions described herein. The UE400 follows one or more of the UEs described in the embodiments herein. In detail, the UE400 follows the UE116, and therefore the reference number 400 is used below to refer to the UE according to the UE116. The UE400 includes a processor 405, memory 410, input device 415, output device 420, and transceiver 425.

[0043] The input device 415 and output device 420 may be combined into a single device such as a touchscreen. In some implementations, the UE400 does not include any input device 415 and / or output device 420. The UE400 may include one or more of the processor 405, memory 410, and transceiver 425, and may not include the input device 415 and / or output device 420.

[0044] As shown in the figure, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435. The transceiver 425 may communicate with one or more cells (i.e., wireless coverage areas) supported by one or more base units. The transceiver 425 may be capable of operating on unlicensed spectrum. Furthermore, the transceiver 425 may include multiple UE panels supporting one or more beams. In addition, the transceiver 425 may support at least one network interface 440 and / or application interface 445. The application interface 445 may support one or more APIs. The network interface 440 may support 3GPP reference points such as Uu, N1, PC5, etc. Other network interfaces 440 may be supported as will be understood by those skilled in the art.

[0045] The processor 405 may include any known controller capable of executing computer-readable instructions and / or logical operations. For example, the processor 405 may be a microcontroller, a microprocessor, a central processing unit ("CPU"), a graphics processing unit ("GPU"), an auxiliary processing unit, a field programmable gate array ("FPGA"), or a similar programmable controller. The processor 405 may execute instructions stored in memory 410 for performing the methods and routines described herein. The processor 405 is communicatively coupled to memory 410, an input device 415, an output device 420, and a transceiver 425.

[0046] Processor 405 may control UE400 to perform the UE behavior described herein. Processor 405 may include an application processor (also called the “main processor”) that manages application domain and operating system (“operating system:OS”) functions, and a baseband processor (also called the “baseband radio processor”) that manages radio functions.

[0047] Memory 410 may be a computer-readable storage medium. Memory 410 may include volatile computer storage media. For example, memory 410 may include RAM, including dynamic RAM ("dynamic RAM: DRAM"), synchronous dynamic RAM ("synchronous dynamic RAM: SDRAM"), and / or static RAM ("static RAM: SRAM"). Memory 410 may include non-volatile computer storage media. For example, memory 410 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 410 may include both volatile and non-volatile computer storage media.

[0048] Memory 410 may store relevant data for implementing traffic category fields as described herein. Memory 410 may also store program code and related data, such as the operating system or other controller algorithms running on the UE400.

[0049] The input device 415 may include any known computer input device, including touch panels, buttons, keyboards, styluses, microphones, etc. The input device 415 may be integrated with the output device 420, for example, as a touchscreen or similar touch-sensitive display. The input device 415 may include a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. The input device 415 may include two or more different devices, such as a keyboard and a touchscreen.

[0050] The output device 420 may be designed to output visual signals, acoustic signals, and / or tactile signals. The output device 420 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 420 may include, but is not limited to, a liquid crystal display ("LCD"), a light-emitting diode ("LED") display, an organic LED ("OLED") display, a projector, or a similar display device capable of outputting images, text, etc., to a user. As another non-limiting example, the output device 420 may include a wearable display, such as a smartwatch, smart glasses, or a head-up display, that is separate from but communicatively coupled to the rest of the user equipment device 400. Furthermore, the output device 420 may be a component of a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, vehicle dashboard, etc.

[0051] The output device 420 may include one or more speakers for generating sound. For example, the output device 420 may generate an audible alarm or notification (e.g., a beep or chime). The output device 420 may include one or more haptic devices for generating vibration, motion, or other haptic feedback. All or part of the output device 420 may be integrated with the input device 415. For example, the input device 415 and the output device 420 may form a touchscreen or similar touch-sensitive display. The output device 420 may be located near the input device 415.

[0052] The transceiver 425 communicates with one or more network functions of the mobile communication network via one or more access networks. The transceiver 425 operates under the control of the processor 405 to transmit messages, data, and other signals, and to receive messages, data, and other signals. For example, the processor 405 may selectively activate the transceiver 425 (or a portion thereof) at certain times to send and receive messages.

[0053] The transceiver 425 includes at least one transmitter 430 and at least one receiver 435. One or more transmitters 430 may be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, one or more receivers 435 may be used to receive downlink communication signals from the base unit. Although only one transmitter 430 and one receiver 435 are illustrated, the UE 400 may have any preferred number of transmitters 430 and receivers 435. Furthermore, the transmitters 430 and receivers 435 may be any preferred type of transmitter and receiver. The transceiver 425 may include a first transmitter / receiver pair used to communicate with a mobile communication network over a licensed radio spectrum, and a second transmitter / receiver pair used to communicate with a mobile communication network over an unlicensed radio spectrum.

[0054] A first transmitter / receiver pair may be used to communicate with a mobile communications network over licensed radio spectrum, and a second transmitter / receiver pair may be used to communicate with a mobile communications network over unlicensed radio spectrum. The second transmitter / receiver pair may be combined into a single transceiver unit, e.g., a single chip, that performs the functions for use with both licensed and unlicensed radio spectrum. The first and second transmitter / receiver pairs may share one or more hardware components. For example, several transceivers 425, transmitters 430, and receivers 435 may be implemented as physically separate components that access shared hardware and / or software resources, such as a network interface 440.

[0055] One or more transmitters 430 and / or one or more receivers 435 may be implemented and / or integrated into a single hardware component, such as a multi-transceiver chip, a system-on-a-chip, an application-specific integrated circuit ("ASIC"), or other types of hardware components. One or more transmitters 430 and / or one or more receivers 435 may be implemented and / or integrated into a multi-chip module. Other components, such as a network interface 440 or other hardware components / circuits, may be integrated into a single chip together with any number of transmitters 430 and / or receivers 435. Transmitters 430 and receivers 435 may be logically configured as transceivers 425 using another common control signal, or as modular transmitters 430 and receivers 435 implemented in the same hardware chip or in a multi-chip module.

[0056] Figure 5 shows further details of a network node 500 that may be used to implement the method described herein. The network node 500 may be an implementation of an entity in a wireless communication network, for example, in one or more of the wireless communication networks described herein. The network node 500 may be, for example, a network function (NF) or an application function (AF) or another entity in the UE400 described above, or in one or more of the wireless communication networks of the embodiments described herein. The network node 500 includes a processor 505, memory 510, input device 515, output device 520, and transceiver 525.

[0057] The input device 515 and output device 520 may be combined into a single device such as a touchscreen. In some implementations, the network node 500 does not include any input device 515 and / or output device 520. The network node 500 may include one or more of the processor 505, memory 510, and transceiver 525, and may not include the input device 515 and / or output device 520.

[0058] As shown in the figure, the transceiver 525 includes at least one transmitter 530 and at least one receiver 535, where the transceiver 525 communicates with one or more remote units 400. In addition, the transceiver 525 may support at least one network interface 540 and / or application interface 545. The application interface 545 may support one or more APIs. The network interface 540 may support 3GPP reference points such as Uu, N1, N2, and N3. Other network interfaces 540 may be supported as will be understood by those skilled in the art.

[0059] The processor 505 may include any known controller capable of executing computer-readable instructions and / or logical operations. For example, the processor 505 may be a microcontroller, microprocessor, CPU, GPU, auxiliary processing unit, FPGA, or similar programmable controller. The processor 505 may execute instructions stored in memory 510 for performing the methods and routines described herein. The processor 505 is communicatively coupled to memory 510, input device 515, output device 520, and transceiver 525.

[0060] Memory 510 may be a computer-readable storage medium. Memory 510 may include volatile computer storage media. For example, memory 510 may include RAM, including dynamic RAM ("DRAM"), synchronous dynamic RAM ("SDRAM"), and / or static RAM ("SRAM"). Memory 510 may include non-volatile computer storage media. For example, memory 510 may include a hard disk drive, flash memory, or any other suitable non-volatile computer storage device. Memory 510 may include both volatile and non-volatile computer storage media.

[0061] Memory 510 may store data relating to establishing a multipath unicast link and / or mobile operation. For example, memory 510 may store parameters, configurations, resource allocations, policies, etc., as described herein. Memory 510 may also store program code and related data, such as operating systems or other controller algorithms running on network node 500.

[0062] The input device 515 may include any known computer input device, including touch panels, buttons, keyboards, styluses, microphones, etc. The input device 515 may be integrated with the output device 520, for example, as a touchscreen or similar touch-sensitive display. The input device 515 may include a touchscreen on which text can be entered using a virtual keyboard displayed on the touchscreen and / or by writing on the touchscreen. The input device 515 may include two or more different devices, such as a keyboard and a touchscreen.

[0063] The output device 520 may be designed to output visual signals, acoustic signals, and / or tactile signals. The output device 520 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, the output device 520 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or a similar display device capable of outputting images, text, etc., to a user. As another non-limiting example, the output device 520 may include a wearable display, such as a smartwatch, smart glasses, or a head-up display, that is separate from but communicatively coupled to the rest of the network node 500. Furthermore, the output device 520 may be a component of a smartphone, personal digital assistant, television, table computer, notebook (laptop) computer, personal computer, vehicle dashboard, etc.

[0064] The output device 520 may include one or more speakers for generating sound. For example, the output device 520 may generate an audible alarm or notification (e.g., a beep or chime). The output device 520 may include one or more haptic devices for generating vibration, motion, or other haptic feedback. All or part of the output device 520 may be integrated with the input device 515. For example, the input device 515 and the output device 520 may form a touchscreen or similar touch-sensitive display. The output device 520 may be located near the input device 515.

[0065] The transceiver 525 includes at least one transmitter 530 and at least one receiver 535. One or more transmitters 530 may be used to communicate with the UE400 as described herein. Similarly, one or more receivers 535 may be used to communicate with network functions in the PLMN and / or RAN as described herein. Although only one transmitter 530 and one receiver 535 are illustrated, the network node 500 may have any preferred number of transmitters 530 and receivers 535. Furthermore, the transmitters 530 and receivers 535 may be any preferred type of transmitter and receiver.

[0066] As shown in Figure 3, the proposed architecture 600 for supporting the IETF DetNet relay node 306 in 5GS is shown in Figure 6, and Figure 6 shows that the relay node 306 is used to support the IETF DetNet flow 204.

[0067] In this embodiment, each 3GPP node used to route user plane traffic (e.g., UE400, UPF114, etc.) may be configured to act as a DetNet relay node 306. UPF114 may include, or be considered as, a network relay node 114 that supports network relay node function 602, and UE400 may support UE relay node function 604 as shown in Figure 6.

[0068] The NW relay node function 602 and UE relay node function 604 are DetNet-aware and receive configuration (from the DetNet controller) regarding how to handle DetNet flow 204.

[0069] The NW relay node 114 and the UE relay node may exist outside of the UE 400 and UPF 114, respectively, i.e., as separate functions 602 and 604, or the relay nodes 114 and 400 may be placed together. In addition, 5GS may support only one relay node 306, i.e., only the UE relay node 400 or the NW relay node 114, depending on the implementation.

[0070] It is proposed to reuse the IEEE TSN functionality of the 5GS system as much as possible. DetNet-aware AF605 receives configuration information from DetNet controller 606 (located outside the 3GPP domain) in the form of a DetNet Yang traffic profile, converts the configuration information into TSC-supported information including QoS information, and sends the QoS information to Policy Control Function (PCF) 608 within the 3GPP system. PCF 608 determines Policy and Charging Control (PCC) rules based on the QoS information and instructs Session Management Function (SMF) 610 to configure the UE's PDU session to be used for the DetNet flow 204 to support the QoS characteristics of the DetNet flow 204.

[0071] The reception of configuration information by DetNet Aware AF605 is indicated in Figure 6 by a single arrow and reference number 607.

[0072] To support the architecture proposed in Figure 6, the following must be done: • Configuration of UE400 to be used as relay node 306 and to establish PDU session 612 for DetNet flow 204. One option is for UE400 to be pre-configured with a DetNet relay node configuration. • Report IETF DetNet relay node support (i.e., the IP address of the UE400 used as relay node 306) to the DetNet controller 606. • Discovery of DetNet end system 302 located behind relay node 306. (This may be optional for case-specific DetNet end systems that interface with a particular UE supporting a DetNet relay node.) Determining propagation delay within 5GS when sending a DetNet flow 204. • Reception of the DetNet flow configuration from the DetNet controller 606 by DetNet-aware AF605. The DetNet controller 606 may take into account the propagation delay reported by 5GS. Mapping of DetNet flow configuration information, including application flows and traffic profiles, obtained from the DetNet controller 606 by the DetNet-aware AF 605, to 5GS QoS information (e.g., 5QI, TSC support information) of the QoS flow in the corresponding PDU session 612 for the DetNet flow 204. Two or more application flows may be mapped to the same DetNet flow 204. The mapping of DetNet flow configuration information to 5GS QoS information of the QoS flow by the DetNet-aware AF 605 is shown in Figure 6 by a single arrow and reference number 614. As shown in Figure 7, UE400 establishes PDU session 612 to relay DetNet flow 204.

[0073] Figure 7 shows the procedure 700 for establishing a PDU session 612 to relay DetNet flow 204.

[0074] A DetNet-aware UE400 (i.e., acting as a relay node) is triggered (based on configuration information) to establish a PDU session 612 for relaying DetNet flow 204. The UE400 is pre-configured to act as a DetNet-aware node, i.e., a relay node 306. The UE400 may be configured to establish dual connectivity by setting up two redundant PDU sessions over the 5G network. The UE400 may use overlapping paths to support redundancy of DetNet flow 204 in accordance with DetNet flow requirements.

[0075] The establishment of PDU session 612 by UE400 is shown in Figure 7 by reference number 702.

[0076] In this embodiment, UE400 includes the requested S-NSSAI, DNN, and optionally DetNet capability indication within the PDU session establishment so that it is sent to SMF610 via Access and Mobility Management (AMF) 704. The S-NSSAI, DNN, and DetNet capability may be included outside the Session Management (SM) container, which includes a PDU session establishment request that allows AMF704 to select the appropriate SMF610 to support the DetNet flow. The UL Non-Access Stratum (NAS) transport from UE400 to AMF704 (S-NSSAI / DNN, DetNet capability indication, SM container PDU session establishment (including DNN, S-NSSAI, and optionally DetNet capability)) is shown in Figure 7 by a single arrow and reference number 706.

[0077] DetNet capability representation may include information indicating the following: • Support for relay nodes, edge nodes, and / or transit nodes. • Support for protocols for receiving DetNet configurations (e.g., NETCONF RFC6241 / YANG RFC6020 or PRE-CC RFC8283). • Dwell time information (i.e., the time it takes for UE relay node 604 to process DetNet flow 204). For this purpose, device-side TSN translator (DS-TT) functionality, as defined in 3GPP TS23.501 v17.4.0, may be reused.

[0078] In this embodiment, the AMF704 receives a request and selects the TSC-Aware SMF610 based on the requested S-NSSAI / DNN and / or DetNet capability indication, if received from the UE400. The selection of the TSC-Aware SMF610 by the AMF704 is shown in Figure 7 by reference no. 708.

[0079] In this embodiment, AMF704 sends a session establishment request, including the SM container received in 706, to SMF610. The sending of the Create Session Establishment request by AMF704 to SMF610 is indicated in Figure 7 by a single arrow and reference number 710.

[0080] In this embodiment, SMF610 selects PCF608 to jointly establish an SM Policy Association and establishes the Policy Association with PCF608. The establishment of the SM policy association with PCF608 by SMF610 is shown in Figure 7 using double arrows and reference numeral 712.

[0081] In this embodiment, the SMF610 selects a DetNet-enabled UPF114 (i.e., a UPF114 that supports relaying DetNet flows) based on the S-NSSAI / DNN and / or DetNet capability indicator. The SMF610 may interface with a Network Repository Function (NRF) to discover a DetNet-enabled UPF114 based on the S-NSSAI / DNN and / or DetNet capability indicator. If the UE400 requests two PDU sessions for redundancy, the SMF610 ensures that separate N3 tunnels are established to the selected UPF114. The selection of a DetNet-enabled UPF114 by the SMF610 is shown in Figure 7 by reference no. 714.

[0082] In this embodiment, SMF610 recognizes and responds to the request with AMF704. The sending of a response of recognition by SMF610 to AMF704 is indicated in Figure 7 by a single arrow and reference numeral 716.

[0083] In this embodiment, SMF610 initiates N4 session establishment, which includes rules for establishing PDU session 612. During this procedure, UPF714 may provide DetNet capability information, which includes the following information: • Support for relay nodes, edge nodes, and / or transit nodes. • Support for protocols for receiving DetNet configurations (e.g., NETCONF RFC6241 / YANG RFC6020 or PRE-CC RFC8283). • Dwell time information (i.e., the time a network relay node takes to process DetNet flow 204). For this purpose, network-side TSN translator (NW-TT) functionality, as defined in 3GPP TS23.501 v17.4.0, may be reused.

[0084] The initiation of N4 session establishment by SMF610 is indicated in Figure 7 by a double-headed arrow and reference number 718.

[0085] In this embodiment, the SMF610 sends a PDU Session Accept message to the UE400 via the AMF704. The sending of the PDU Session Accept message to the UE400 by the SMF610 is indicated in Figure 7 by a single arrow and reference numerals 720 and 722, respectively.

[0086] In this embodiment, based on a subscription from PCF608 (via AF605), SMF610 provides PCF608 with DetNet capabilities and IP addresses for UE400 and UPF114. The provision of DetNet capabilities and IP addresses for UE400 and UPF114 to PCF608 is indicated in Figure 7 by double arrows and reference numeral 724.

[0087] In this embodiment, PCF608 forwards, or reports, information to DetNet-Aware AF605 by calling Npcf_PolicyAuthorization_Notify. The forwarding / reporting of information by PCF608 to DetNet-Aware AF605 is shown in Figure 7 by double arrows and reference number 726.

[0088] In this embodiment, the DetNet-aware AF605 learns the IP addresses of the UE400 and UPF114, as well as the potential latency of the DetNet flow 204 traversing 5GS (i.e., between the UE400 and UPF114). The learning of the IP addresses of the UE400 and UPF114, as well as the potential latency of the DetNet flow 204, by the DetNet-aware AF605 is shown in Figure 7 by reference no. 728.

[0089] In an alternative embodiment, the DetNet controller 606 recognizes the IP address of the UE400 used as the DetNet relay node 306 by subscribing to 5GS (from AF) via the Network Exposure Function (NEF) a PDU session status request that includes an S-NSSAI / DNN and / or DetNet capability indication (of the slice or DNN used for the DetNet flow) in the subscription request. This procedure is similar to that described in Figure 4.15.3.2.3-1 in 3GPP TS23.502 v17.4.0.

[0090] In this embodiment, once the DetNet controller 606 / DetNet-aware AF605 recognizes the IP address of the UE400, the DetNet controller 606 / DetNet-aware AF605 can use the Neighbor Discovery Protocol as described in IETF RFC4861 to discover the DetNet end system 302 located behind the UE400 and UPF114.

[0091] In this embodiment, the DetNet controller 606 or DetNet-aware AF605 can then determine the QoS characteristics for sending the DetNet flow 204 between the DetNet end systems 302. The DetNet controller 606 takes into account latency within 5GS, as reported by the UE400 and UPF114.

[0092] Alternatively, DetNet-aware AF605 determines DetNet-specific TSC support information, taking into account the characteristics of DetNet flow 204, according to the information provided by DetNet controller 606 in the DetNet Yang model configuration profile, as defined in draft-ietf-detnet-yang-16. In the Yang model, each DetNet flow 204 (related to ingress and egress nodes) is associated with a traffic profile that includes the following information: • Minimum bandwidth: This is the minimum bandwidth that must be guaranteed for the provision of DetNet services. • Maximum latency: This is the maximum latency in nanoseconds from the ingress node to the egress node. • Maximum latency variation: This is the difference in nanoseconds between the minimum end-to-end unidirectional latency and the maximum end-to-end unidirectional latency. • MaxLoss: This parameter specifies the maximum packet loss ratio (PLR) for DetNet services between ingress and egress in a DetNet domain. • MaxConsecutiveLossTolerance: This is the maximum consecutive loss tolerance parameter, which represents the maximum number of consecutive packets for which loss is acceptable. • MaxMisordering: This represents the maximum number of packets that can be received in a non-order manner. • Max-pkts-per-interval: This is the maximum number of packets that a source can send within a single interval. • Leaf max-payload-size: This is the maximum payload size that the source will send. • Min-payload-size: This is the minimum payload size that the source will send. • Leaf min-pkts-per-interval: This is the minimum number of packets that a source sends within a single interval.

[0093] In this embodiment, based on the traffic profile information, the DetNet Aware AF605 determines the following TSC support information, as shown in the table below.

[0094] [Table 1]

[0095] Alternatively, TSC support information includes all traffic profile parameters contained within the DetNet Yang model traffic profile.

[0096] Figure 8 shows the procedure 800 for configuring 5GS with appropriate QoS characteristics.

[0097] The UE400 establishes PDU session 612 for DetNet flow 204, as shown in Figure 6. The establishment of PDU session 612 for DetNet flow 204 by the UE400 is shown in Figure 8 by reference number 802.

[0098] In this embodiment, the DetNet controller 606 subscribes via AF605 so that DetNet nodes in the 3GPP system are notified. In one embodiment, AF605 subscribes to PDU session status events and / or DetNet capabilities for a specific S-NSSAI / DNN (used for DetNet flow 204). The subscription of PDU session status events and / or DetNet capabilities by AF605 is shown in Figure 8 by reference no. 804.

[0099] In an alternative embodiment, AF605 subscribes to the new event ID. The DetNet controller 606 discovers the IP address of the UE400 used as the DetNet relay node 306, and the potential latency when the DetNet flow 204 is routed through the DetNet relay node 306 in 5GS.

[0100] Returning to the embodiment in Figure 8, the DetNet controller 606 discovers a DetNet end system 302 that interfaces with the UE400, which acts as a DetNet relay node 306 using procedures outside the scope of 3GPP. For example, the DetNet controller 606 can use the Neighbor Discovery Protocol as per IETF RFC4861 to discover the DetNet end system 302 located behind the UE400 and UPF114. The discovery of the DetNet end system 302 by the DetNet controller 606 is shown in Figure 8 by reference no. 806.

[0101] In this embodiment, the DetNet controller 606 provides configuration information for the DetNet flow 204 to the DetNet-aware AF 605 by providing rules in the form of the DetNet Yang model, as described in draft-ietf-detnet-yang-16. This procedure is outside the scope of 3GPP. The provision of configuration information for the DetNet flow 204 to the DetNet-aware AF 605 by the DetNet controller 606 is indicated in Figure 8 by a single arrow and reference number 808.

[0102] In this embodiment, the DetNet-aware AF605 derives DetNet-specific TSC support information, including QoS characteristics, from DetNet configuration information provided by the DetNet controller 606 based on the IETF DetNet Yang profile. The deriving of DetNet-specific TSC support information by the DetNet-aware AF605 is shown in Figure 8 by reference no. 810.

[0103] In this embodiment, DetNet-aware AF605 sends a request to NEF808 to establish an AF session with the required QoS, the request including the UE IP address and TSC support information, along with DetNet-specific parameters and / or indications for establishing a QoS flow for DetNet flow 204. The sending of a request by DetNet-aware AF605 to NEF808 to establish an AF session with the required QoS is shown in Figure 8 by a single arrow and reference number 812.

[0104] In this embodiment, NEF808 discovers the PCF608 serving the UE400 and sends an Npcf_PolicyAuthorizationRequest to the PCF608. The Npcf_PolicyAuthorizationRequest may include the UE IP address and TSC support information. The sending of the Npcf_PolicyAuthorizationRequest by NEF808 to the PCF608 serving the UE400 is indicated in Figure 8 by a single arrow and reference number 814.

[0105] If AF605 contains individual QoS information, NEF808 interacts with the Time Sensitive Communication and Time Synchronization Function (TSCTSF) 816 to request the establishment of a corresponding session with QoS requirements. The interaction between NEF808 and TSCTSF816, and the request for the establishment of a corresponding session, is indicated in Figure 8 by a single arrow and reference number 816.

[0106] In this case, steps 3b to 4a are performed as described in Figure 4.15.6.6-1 in 3GPP TS23.502 v17.4.0. The execution of these steps is shown in Figure 8 by reference number 818.

[0107] TSCTSF then acknowledges and responds to the request made by NEF808 at 816. The recognition and response of the request made by NEF808 by TSCTSF is shown in Figure 8 by a single arrow and reference number 820.

[0108] In this embodiment, PCF608 determines the PCC rules based on TSC support information. The determination of PCC rules by PCF608 based on TSC support information is shown in Figure 8 by reference no. 822.

[0109] PCF608 then acknowledges and responds to the Npcf_PolicyAuthorization request received by NEF808 at 814. The recognition and response of the Npcf_PolicyAuthorization request by PCF608 is indicated in Figure 8 by a single arrow and reference number 824.

[0110] In this embodiment, NEF808 recognizes and responds to AF605 with a QoS response to establish an AF session. NEF808 may create an AF session using a QoS response to AF605. Recognition or creation of an AF session by NEF808 using a QoS response is shown in Figure 8 with a single arrow and reference numeral 826.

[0111] In this embodiment, PCF608 incorporates the updated PCC rules, i.e., SM policy association updates, into SMF610 for the PDU session used for DetNet flow 204. The incorporation of the updated PCC rules into SMF610 by PCF608 is shown in Figure 8 by double arrows and reference number 828.

[0112] In this embodiment, SMF610 incorporates the N4 rule into UPF114. The incorporation of the N4 rule into UPF114 by SMF610 is shown in Figure 8 by double arrows and reference number 830. If the user plane path is properly configured, i.e., when the DetNet controller 606 / DetNet aware AF605 receives a response / recognition response at 826, the DetNet flow packets traverse the 3GPP domain as shown in Figure 9.

[0113] Figure 9 shows procedure 900 for routing DetNet flow packets via DetNet Aware 5GS.

[0114] In this embodiment, application 902 sends application packets to the DetNet end system 302. The sending of application packets by application 902 to the DetNet end system is indicated in Figure 9 by a single arrow and reference numeral 904.

[0115] In this embodiment, the DetNet end system 302 encapsulates the application packets into a DetNet flow 204. The encapsulation of application packets into a DetNet flow 204 by the DetNet end system 302 is shown in Figure 9 by reference no. 906.

[0116] In this embodiment, the DetNet end system 302 sends DetNet flow packets, such as IP packets, within the DetNet flow 204 to the NW DetNet relay node 908, for example, to the NW relay node function 602. The sending of DetNet flow packets by the DetNet end system 302 to the NW DetNet relay node 908 is indicated in Figure 9 by a single arrow and reference number 910.

[0117] In this embodiment, the NW DetNet relay node 908 processes DetNet flow packets according to the DetNet configuration information. The processing of DetNet flow packets by the NW DetNet relay node 908 according to the DetNet configuration information is shown in Figure 9 by reference no. 912.

[0118] In this embodiment, the NW DetNet relay node 908 sends the DetNet flow packet to the UPF 114 within the DetNet flow 204. The sending of the DetNet flow packet to the UPF 114 by the NW DetNet relay node 908 is indicated in Figure 9 by a single arrow and reference number 914.

[0119] In this embodiment, UPF114 sends DetNet flow packets to UE400 via a 3GPP tunnel. The sending of DetNet flow packets to UE400 via a 3GPP tunnel by UPF114 is shown in Figure 9 by reference no. 916.

[0120] In this embodiment, UE400 sends DetNet flow packets to UE DetNet relay node 918, for example, to UE relay node function 604, within DetNet flow 204. The sending of DetNet flow packets by UE400 to UE DetNet relay node 918 is indicated in Figure 9 by a single arrow and reference number 920. In this embodiment, UE DetNet relay node 918 processes DetNet flow packets according to DetNet configuration information. The processing of DetNet flow packets by UE DetNet relay node 918 according to DetNet configuration information is indicated in Figure 9 by reference number 922.

[0121] In this embodiment, the UE DetNet relay node 918 sends DetNet flow packets to the DetNet end system 302. The sending of DetNet flow packets to the DetNet end system 302 by the UE DetNet relay node 918 is shown in Figure 9 by reference no. 924.

[0122] Figure 10 shows an alternative embodiment of architecture 1000 in which DetNet flow 204 is supported via a DetNet non-aware 3GPP system.

[0123] In this alternative embodiment, UE400 and UPF114 are unaware of DetNet flow 204, but the 3GPP system is configured to route packets containing further DetNet flows with QoS requirements similar to those of DetNet flow 204. UE400 and UPF114 may be considered DetNet non-aware relay nodes 1002.

[0124] In Architecture 1000, the entire 5GS network is configured as a DetNet relay node 306.

[0125] To support Architecture 1000, the following needs to be done: The UE establishes PDU session 612 as per 3GPP TS23.502 v17.4.0. UE400 may request the establishment of additional redundant PDU sessions. • DetNet Aware AF605 subscribes to be notified of the IP address of the UE400 used for DetNet Flow 204. • Discovery of DetNet end system 302 located behind relay node 306, i.e., behind UE400 and UPF114. The DetNet-aware AF605 receives DetNet flow configuration information from the DetNet controller 606. Mapping of DetNet flow configuration information obtained from DetNet controller 606 to 5GS QoS information (e.g., 5QI, TSC support information) of the QoS flow in the corresponding PDU session 612 for DetNet flow 204. The mapping of DetNet flow configuration information to 5GS QoS information of the QoS flow by DetNet-aware AF 605 is shown in Figure 10 by a single arrow and reference number 614, following action 614 described above.

[0126] It is understood that much of Architecture 1000 corresponds to Architecture 600 as described above with reference to Figure 6. For example, the reception of configuration information by DetNet Aware AF605 is shown in Figure 10 by a single arrow and reference number 607, and follows action 607 as described above. If Architecture 1000 includes entities or actions that correspond to those described in Architecture 600, similar reference numbers are understood to assign the same or similar roles to those entities or actions unless otherwise stated.

[0127] When UE400 establishes PDU session 612, the difference in this embodiment from procedure 700 described in Figure 7 is that UE400 does not report any DetNet capability, and SMF610 reports the IP address of UE400 to DetNet-aware AF605 (corresponding to action 728 in Figure 7). In the corresponding procedure in this embodiment, if UE400 and UPF114 support DS-TT and NW-TT functionality, respectively, UE400 and UPF114 may still report dwell time, in which case the dwell time is forwarded to DetNet-aware AF605. This can be used by the DetNet controller 606 to determine packet latency as the packet traverses 5GS and to determine appropriate QoS for DetNet flow 204 to traverse 5GS.

[0128] The procedure for the DetNet controller 606 to configure DetNet-aware AF605 with QoS requirements is as described in the description of procedure 800, with reference to Figure 8. In action 810 shown in Figure 8, DetNet-aware AF605 determines the IP address of UE400 in order to initiate an AF session request with specific QoS requirements in action 812.

[0129] In one embodiment, a wireless communication device is provided for communicating with a wireless communication network. In this embodiment, the wireless communication device is a UE400 configured to perform the procedure described in the above embodiment and to participate in the architecture.

[0130] The transceiver of the wireless communication device, i.e., the transceiver 425 of the UE400, is configured to send a request to the wireless communication network, the request comprising first information for setting up a user plane connection for DetNet traffic, i.e., a DetNet flow 204. In this embodiment, the first information includes configuration information received by the DetNet controller 606 as described in the above embodiment.

[0131] The request may request the establishment of a user plane connection, for example, the PDU session 612 established in the above embodiment. In this embodiment, the request for the establishment of a user plane connection is made in accordance with actions 702, 802 described in the above embodiment. By sending a request comprising first information for setting up a user plane connection for deterministic network traffic, the wireless communication device is configured to carry deterministic network traffic over the wireless communication network. The first information may comprise at least one requirement.

[0132] In this embodiment, the first information may comprise at least one of DNN, S-NSSAI, or both.

[0133] In this embodiment, the first information may include the DetNet capability of the wireless communication device, i.e., the DetNet capability of the UE400, as provided to the PCF608 in step 700 in action 724.

[0134] In this embodiment, the DetNet capability of a wireless communication device may define the ability of the wireless communication device to act as at least one of a relay node, edge node, transit node, or a combination thereof.

[0135] In this embodiment, the DetNet capability of the wireless communication device may include the ability of the wireless communication device to support the Neighbor Discovery Protocol and / or the DetNet Configuration Protocol.

[0136] In this embodiment, the DetNet capability of the wireless communication device may include the capability to calculate dwell time.

[0137] The DetNet may be an IETF DetNet according to the embodiment described above.

[0138] In one embodiment, a method 1100 is provided which is performed by the wireless communication device of the above embodiment. Figure 11 is a process flowchart illustrating method 1100, which in step s1102 includes sending a request to a wireless communication network by the transceiver of the wireless communication device, i.e., the transceiver 425 of UE400, the request comprising first information for setting up a user plane connection for DetNet traffic, i.e., a DetNet flow 204.

[0139] In one embodiment, an AF in a wireless communication network is provided. In this embodiment, the AF follows the DetNet Aware AF 605 described in the above embodiment and the network node 500 described above.

[0140] The AF comprises a transceiver with transceiver 525 configured to send subscription requests to a first NF of the wireless communication network, which requests notification of the device's network address when a device (e.g., UE400) establishes a user plane connection to support DetNet deterministic traffic. The first NF follows the network node 500 described above.

[0141] The transceiver is further configured to receive first information from the first NF, the first information identifying the first device, and the first information identifying that the second NF supports DetNet relay node functionality, i.e., that the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF follows network node 500.

[0142] The transceiver is further configured to receive from the DetNet controller by the DetNet controller 606 described in the above embodiment in response to the reception of first information, namely DetNet flow requirements.

[0143] In this embodiment, the AF further comprises a processor by processor 505 configured to convert DetNet flow requirements into QoS requirements for relaying DetNet traffic over the wireless communication network. Converting DetNet flow requirements into QoS requirements is performed in this embodiment according to the mapping 614 of DetNet flow configuration information obtained from the DetNet controller 606 to 5GS QoS information, as described in the above embodiment.

[0144] The transceiver is further configured to send a second request to a second NF to establish a user plane session with the wireless communication network in accordance with QoS requirements for relaying DetNet traffic over the wireless communication network.

[0145] Therefore, the AF in this embodiment is configured to carry DetNet traffic over a wireless communication network and to implement DetNet flow requirements for DetNet traffic (for example, the DetNet configuration information described in the above embodiment).

[0146] DetNet flow requirements may be QoS requirements originating from the DetNet. QoS requirements for relaying DetNet traffic over a wireless communication network may be 3GPP QoS requirements.

[0147] The processor may be configured to translate DetNet flow requirements into QoS requirements for relaying DetNet traffic over a wireless communication network, which depend on information provided by a first device and / or a second NF. This information may include, for example, dwell time.

[0148] The first NF may be an NEF, for example, the NEF808 described above with reference to Figure 8.

[0149] The second NF may be a UPF, for example, UPF114 as described in the above embodiment.

[0150] The DetNet may be an IETF DetNet according to the embodiment described above.

[0151] In one embodiment, a method 1200 is provided which is performed by the AF of the above embodiment. Figure 12 is a process flowchart illustrating method 1200. The method includes, in step s1202, sending a subscription request to a first NF of a wireless communication network, the subscription request requesting notification of the device's network address when the device has established a user plane connection to support DetNet deterministic traffic.

[0152] The method includes, in step s1204, receiving first information from the first NF, the first information identifying the first device, and the first information identifying that the second NF supports DetNet relay node functionality, i.e., that the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF follows network node 500.

[0153] The method includes, in step s1206, receiving a DetNet flow requirement from the DetNet controller via the DetNet controller 606 described in the above embodiment in response to the receipt of the first information.

[0154] The method includes, in step s1208, converting the DetNet flow requirements into QoS requirements for relaying DetNet traffic over the wireless communication network. Converting the DetNet flow requirements into QoS requirements is performed in this embodiment according to the mapping 614 of DetNet flow configuration information obtained from the DetNet controller 606 to 5GS QoS information, as described in the above embodiment.

[0155] The method includes, in step s1210, sending a second request to a second NF to establish a user plane session with the wireless communication network in accordance with QoS requirements for relaying DetNet traffic over the wireless communication network.

[0156] Therefore, Method 1200 is provided for configuring AF to carry DetNet traffic over a wireless communication network and to implement DetNet flow requirements for DetNet traffic (e.g., DetNet configuration information described in the embodiments above).

[0157] In one embodiment, a first NF is provided in a wireless communication network, the first NF comprising a transceiver, i.e., transceiver 525, configured to receive subscription requests from the AF of the wireless communication network, the subscription requests request notification of the device's network address when the device establishes a user plane connection to support DetNet deterministic traffic. The first NF follows the network node 500 described above.

[0158] In this embodiment, the transceiver is configured to send first information to the AF, the first information identifying the first device, and the first information identifying that the second NF supports DetNet relay node functionality, i.e., that the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF follows the network node 500.

[0159] The first NF may be an NEF, for example, the NEF808 described above with reference to Figure 8.

[0160] The DetNet may be an IETF DetNet according to the embodiment described above.

[0161] In one embodiment, a method 1300 is provided which is performed by the first NF of the above embodiment. Figure 13 is a process flowchart illustrating method 1300. The method includes, in step s1302, receiving a subscription request from an AF of a wireless communication network, the subscription request requesting notification of the device's network address when the device establishes a user plane connection to support DetNet deterministic traffic. The first NF follows the network node 500 described above.

[0162] The method includes, in step s1304, sending first information to the AF, the first information identifying the first device, and the first information identifying that the second NF supports DetNet relay node functionality, i.e., that the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF follows network node 500.

[0163] In one embodiment, a UPF is provided in a wireless communication network, the UPF following the UPF 114 described in the above embodiment and following a network node 500. The UPF includes a transceiver, i.e., a transceiver 525, configured to receive requests from the SMF by the SMF 610 described in the above embodiment for establishing a user plane session with the wireless communication network in accordance with at least one QoS requirement for relaying DetNet traffic over the wireless communication network.

[0164] In this embodiment, the transceiver is further configured to send a response to the SMF indicating first information, including the DetNet capability of the UPF. The first information may be transmitted within a container.

[0165] In one embodiment, a method 1400 is provided which is performed by the UPF of the above embodiment. Figure 14 is a process flowchart illustrating method 1400. The method includes, in step s1402, receiving from the SMF by the SMF610 described in the above embodiment a request to establish a user plane session with the wireless communication network in accordance with at least one QoS requirement for relaying DetNet traffic over the wireless communication network.

[0166] Method 1400 includes, in step s1404, sending a response to the SMF indicating first information, including the DetNet capability of the UPF. The first information may be sent within a container.

[0167] Therefore, Method 1400 is provided for configuring the UPF to carry DetNet traffic over a wireless communication network (i.e., to act as a DetNet relay node) and to implement DetNet flow requirements for DetNet traffic (e.g., DetNet configuration information described in the embodiments above).

[0168] Advantageously, the methods and apparatus described herein help integrate DetNet support using the IETF DetNet standard via 5GS. This solution helps enable a DetNet controller within a DetNet-aware 3GPP system to discover nodes and to enable the controller to introduce requirements that allow the 3GPP network to establish user-plane connectivity with QoS requirements that meet the QoS standards for DetNet flows.

[0169] Advantageously, the methods and apparatus described herein overcome existing problems regarding how to identify and discover UEs that support the establishment of user plane connections for DetNet traffic, and how to configure 3GPP systems, such as existing 3GPP systems, to support user plane connections for DetNet traffic.

[0170] In some embodiments described above, the 3GPP system is configured to support DetNet traffic that is DetNet-aware (using DetNet-aware nodes acting as relay nodes, e.g., UE and UPF), while in other configurations, the 3GPP system is DetNet-non-aware and, more advantageously, can support DetNet flows. Specifically, in a DetNet-non-aware 3GPP system, the network may be set up to route DetNet flows with specific QoS requirements, thereby fulfilling the IETF QoS requirements for DetNet flows.

[0171] It should be noted that the methods and apparatus described above are illustrative rather than limiting of the present invention, and that many alternative configurations can be designed by those skilled in the art without departing from the scope of the appended claims. The term “comprising” does not exclude the existence of elements or steps other than those enumerated in the claims, and “a” or “an” does not exclude the plural, and a single processor or other unit may perform the functions of several units described in the claims. No reference numerals in the claims shall be construed as limiting their scope.

[0172] Furthermore, although examples are given in the context of specific communication standards, these examples are not intended to limit the communication standards to which the disclosed methods and apparatus may be applied. For example, although specific examples are given in the context of 3GPP, the principles disclosed herein may also be applied to other wireless communication systems, and certainly to any communication system that uses routing rules.

[0173] This method may also be embodied in a set of instructions stored on a computer-readable medium that, when loaded into a computer processor, a digital signal processor (DSP), or similar device, causes the processor to execute the method described above.

[0174] The methods and apparatus described may be practiced in other specific forms. The methods and apparatus described should be considered illustrative and not restrictive in all respects. Therefore, the scope of the invention is indicated not by the above description but by the appended claims. All modifications that fall within the equivalent meaning and scope of the claims should be included within those scopes. [Explanation of Symbols]

[0175] 100 Network Architectures 102 IEEE TSN system, TSN network 104 5GS Bridge 106 Protocol Data Unit (PDU) Session 108 Protocol Data Unit (PDU) Sessions 110 Network-side TSN translator (NW-TT) 112 Device-side TSN translator (DS-TT) 114 User Plane Function (UPF) 116 User Equipment (UE) 200 service sublayers, DetNet-aware nodes 202 Source 204 DetNet Flow 206 Transfer Sublayer 208 Lower Layers 210 Recipient 300 relays 302 IETF DetNet End Systems 306 relay nodes 400 User Equipment (UE) 405 Processor 410 memory 415 Input Devices 420 Output Devices 425 Transceiver 430 Transmitter 435 Receiver 440 Network Interfaces 445 Application Interfaces 500 network nodes 505 Processor 510 memory 515 Input Devices 520 Output Devices 525 Transceiver 530 Transmitter 535 Receiver 540 Network Interfaces 545 Application Interfaces 600 Architecture 602 Network relay node function 604 UE relay node function 605 DetNet Aware AF 606 DetNet Controller 608 Policy Control Function (PCF) 610 Session Management Function (SMF) 704 Access and Mobility Management (AMF) 808 NEF 816 Time-sensitive communication and time synchronization function (TSCTSF) 902 Application 908 NW DetNet relay node 918 UE DetNet relay node 1000 Architectures 1002 DetNet Non-Aware Relay Node

Claims

1. User equipment (UE) for wireless communication, At least one memory, The UE comprises at least one processor coupled to the at least one memory, and the at least one processor provides the UE with The transmission of a request to a wireless communication network, wherein the request comprises first information for setting up a user plane connection for deterministic network (DetNet) data traffic, is configured to cause such transmission to occur. The first information includes the DetNet capability of the UE, The DetNet capability of the aforementioned UE includes the capability to support one or more of the Neighbor Discovery Protocol or DetNet Configuration Protocol. UE.

2. The first information includes at least one of the following: a data network name or single network slice selection support information. The UE according to claim 1.

3. The DetNet capability of the aforementioned UE stipulates that the UE behaves as at least one of a relay node, edge node, or transit node. The UE according to claim 1.

4. The DetNet capability of the aforementioned UE includes the capability to calculate the dwell time, The aforementioned dwell time is the time required for the UE to process the DetNet flow. The UE according to claim 1.

5. A processor for wireless communication, It comprises at least one controller coupled to at least one memory, and the at least one controller provides the processor with The transmission of a request to a wireless communication network, wherein the request comprises first information for setting up a user plane connection for deterministic network (DetNet) data traffic, is configured to cause such transmission to occur. The first information includes the DetNet capability of the UE, The DetNet capability of the aforementioned UE includes the capability to support one or more of the Neighbor Discovery Protocol or DetNet Configuration Protocol. Processor.

6. The first information includes at least one of the following: a data network name or single network slice selection support information. The processor according to claim 5.

7. The DetNet capability of the aforementioned UE stipulates that the UE behaves as at least one of a relay node, edge node, or transit node. The processor according to claim 5.

Images