Method for supporting deterministic networks in a wireless communication network - Patents.com

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 herein generally relates to the field of implementing support for Layer 3 deterministic networks in 5G systems. [Background technology]

[0002] 3GPP has specified support for deterministic networks since Release 17.

[0003] Release 17 will include support for Layer 2 deterministic networks (i.e., IEEE time-sensitive networking based on the IEEE 802.1q standard).

[0004] Thus, existing support for 3GPP systems to route deterministic network traffic is based on Ethernet / Layer 2 based interfaces, whereas IETF networks use IP connectivity / Layer 3 based interfaces. Summary of the Invention [Problem to be solved by the invention]

[0005] A problem with the suggested procedures for impacting 3GPP systems to set up connections with specific quality of service requirements is that they 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] Disclosed herein are procedures for supporting Layer 3 deterministic networks in 5G systems, which may be implemented by the apparatus and architecture described herein. [Means for solving the problem]

[0007] 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.

[0008]

[0013] There is also provided a method in a wireless communication device, the wireless communication device configured to communicate with a wireless communication network, the method comprising 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] An application function in a wireless communication network is further provided, the application function comprising a transceiver and a processor. The transceiver is configured to send a subscription request to a first network function of the wireless communication network, the subscription request requesting notification of a network address of the device when the device establishes a user plane connection to support deterministic network deterministic traffic, receive first information from the first network function, the first information identifying the first device and the first information identifying a second network function supporting deterministic network relay node functionality, and receive deterministic network flow requirements from a deterministic network controller in response to receiving the first information. The processor is configured to translate the deterministic network flow requirements into quality of service requirements for relaying the deterministic network traffic over the wireless communication network. The transceiver is further configured to send a second request to the second network function to establish a user plane session with the wireless communication network according to the quality of service requirements for relaying the deterministic network traffic over the wireless communication network.

[0010] A method in an application function 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, the subscription request requesting notification of a network address of the device when the device establishes a user plane connection for supporting deterministic network deterministic traffic, and receiving first information from the first network function, the first information identifying the first device and the first information identifying a second network function supporting 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 the deterministic network traffic over the wireless communication network. The method further comprises sending a second request to the second network function to establish a user plane session with the wireless communication network in accordance with the quality of service requirements for relaying the deterministic network traffic over the wireless communication network.

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

[0012] Further provided is a method in a first network function of a wireless communications network, the method comprising receiving a subscription request from an application function of the wireless communications network, the subscription request requesting notification of a network address of the device when the device establishes a user plane connection for supporting deterministic network deterministic traffic, the method further comprising sending first information to the application function, the first information identifying the first device, the first information identifying a second network function supporting the deterministic network relay node functionality.

[0013] A user plane function in a wireless communications network is further provided, the user plane function comprising a transceiver configured to receive a request from a session management function for establishing a user plane session with the wireless communications network according to at least one quality of service requirement for relaying deterministic network traffic over the wireless communications network, the transceiver further configured to transmit a response to the session management function indicative of first information including the deterministic network capabilities of the user plane function.

[0014] There is further provided a method in a user plane function of a wireless communications network, the method comprising receiving a request from a session management function to establish a user plane session with the wireless communications network according to at least one quality of service requirement for relaying deterministic network traffic over the wireless communications network, the method further comprising sending a response to the session management function indicating first information including the deterministic network capabilities of the user plane function.

[0015] To illustrate the manner in which the advantages and features of the present disclosure may be obtained, the description of the present disclosure will be expressed by reference to several apparatus and methods illustrated in the accompanying drawings. Each of these drawings illustrates only some aspects of the present disclosure and therefore should not be considered as limiting its scope. The drawings may be simplified for clarity and are not necessarily drawn to scale.

[0016] A method and apparatus for supporting a Layer 3 deterministic network in a 5G system will now be described, by way of example only, with reference to the accompanying drawings, in which: [Brief description of the drawings]

[0017] [Figure 1] FIG. 1 is a schematic diagram of a network architecture for supporting an IEEE time-sensitive networking system in a 5G system. [Diagram 2] FIG. 1 is a schematic diagram of a network architecture for supporting an IETF deterministic network. [Diagram 3] 1 is a schematic diagram of a further network architecture for supporting an IETF deterministic network. [Figure 4] 1 is a schematic diagram of a user equipment device that may be used to implement the methods described herein. [Diagram 5] FIG. 2 is a schematic diagram of a network node that may be used to implement the methods described herein. [Figure 6] FIG. 1 is a schematic diagram of yet a further network architecture for supporting IETF deterministic network relay nodes in a 5G system. [Figure 7] A schematic diagram of a procedure for establishing a PDU session for relaying a deterministic network flow. [Figure 8] FIG. 1 is a schematic diagram of a procedure for configuring a 5G system with suitable quality of service characteristics. [Figure 9]FIG. 13 is a schematic diagram of a further procedure for routing deterministic network flow packets through a Deterministic Network-aware 5G system. [Figure 10] FIG. 1 is a schematic diagram of yet a further network architecture for supporting deterministic network flows over a Deterministic Network-unaware 5G system. [Figure 11] 1 is a process flow diagram illustrating a method performed by a wireless communication device in a wireless communication network. [Figure 12] 11 is a process flow diagram illustrating a further method performed by an application function of a wireless communications network. [Figure 13] 11 is a process flow diagram illustrating a yet further method performed by a first network function of a wireless communications network. [Figure 14] 11 is a process flow diagram illustrating yet a further method performed by a user plane function of a wireless communications network. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

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

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

[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-transitory, and / or non-transmittable. The storage devices may not embody signals. In some configurations, the storage devices merely employ signals to access the code.

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

[0022] More detailed examples (non-exhaustive list) of storage devices would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory ("RAM"), a read-only memory ("ROM"), an erasable programmable read-only memory ("EPROM" or flash memory), a portable compact disc read-only memory ("CD-ROM"), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of this specification, a computer-readable storage medium may be any tangible medium that can store or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0023] References throughout this specification to an example of a particular method or apparatus, or similar language, mean that a 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 features of an example of a particular method or apparatus, or similar language, may, but do not necessarily, refer to the same example, but mean "one or more, but not all, examples" unless otherwise specified. The terms "including," "comprising," "having," and variations thereof mean "including, but not limited to," unless otherwise specified. Enumerated 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 refer to "one or more," unless otherwise specified.

[0024] As used herein, a list with the conjunction "and / or" includes any single item in the list or a combination of items in the list. For example, a list of A, B, and / or C includes only A, only B, only C, 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 the list or a combination of items in the list. For example, one or more of A, B, and C includes only A, only B, only C, 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 item of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C" includes only members A, B, or C, and excludes the combination of A, B, and C. As used herein, "a member selected from the group consisting of A, B, and C, and combinations thereof" includes only A, only B, only C, the combination of A and B, the combination of B and C, the combination of A and C, or the combination of A, B, and C.

[0025] Furthermore, the described features, structures, or characteristics described herein may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, and the like, to provide a thorough understanding of the present disclosure. However, those skilled in the art will recognize that the disclosed methods and apparatuses can be practiced without one or more of the specific details or with other methods, components, materials, and the like. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the present disclosure.

[0026] Aspects of the disclosed methods and apparatus are described below with reference to schematic flow chart illustrations and / or schematic block diagrams of methods, apparatus, systems, and program products. It will be understood that each block of the schematic flow chart illustrations and / or schematic block diagrams, and combinations of blocks in the schematic flow chart illustrations and / or schematic block diagrams, may be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to generate a machine, such that the instructions, executing via the processor of the computer or other programmable data processing apparatus, create means for performing the functions / acts specified in the schematic flow chart illustrations and / or schematic block diagrams.

[0027] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture that includes instructions implementing the functions / acts specified in the schematic flow chart illustrations and / or schematic block diagrams.

[0028] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device for causing a series of operational steps to be performed on the computer, other programmable apparatus, or other device to generate a computer-implemented process, such that the code executing on the computer or other programmable apparatus provides a process for performing the functions / operations specified in the schematic flow chart illustrations and / or schematic block diagrams.

[0029] The schematic flow chart diagrams and / or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, systems, methods, and program products. In this regard, each block in the schematic flow chart diagrams and / or schematic block diagrams may represent a module, segment, or portion of code that includes one or more executable instructions of code for implementing a specified logical function(s).

[0030] It should also be noted that in some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially in parallel, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. Other steps and methods may be conceived whose function, logic, or effect is equivalent to one or more of the blocks, or portions thereof, of the illustrated figures.

[0031] The description of an element in each drawing may refer to the element in the preceding drawing, and like numbers refer to like elements in all drawings.

[0032] 3GPP specifies support for deterministic networks starting with Release 17. Release 17 supports support for 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 a network architecture 100 for supporting an IEEE TSN system 102 in a 5G system (5GS).

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

[98] ) via the 5GS bridge 104, the 5GS supports the following features: Configure bridge information in 5GS. After the establishment of a Protocol Data Unit (PDU) session 106, reporting bridge information of the 5GS bridge 104 to the TSN network 102. Receiving configuration information from the 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) assistance information) of QoS flows in 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 the User Plane Function (UPF) 114 and the user equipment (UE) 116 respectively, are responsible for calculating the propagation delay within 5GS, which is used to adjust the time synchronization clocks. As part of Release 18, new considerations were agreed to support Layer 3 deterministic networks within 5GS systems (in detail, the IETF DetNet standard was agreed as described in IETF RFC8938). A very basic diagram of IETF DetNet support is shown in Figure 2. 2, in particular, illustrates a deterministic network (DetNet) aware node, i.e., service sublayer 200, that receives application packets from a source 202 (that is DetNet unaware) and encapsulates the packets into DetNet flows 204 that have certain deterministic characteristics (e.g., certain QoS, delay tolerance, etc.). The DetNet aware node 200 encapsulates packets into DetNet flows 204 based on information (rules) provided by a DetNet controller (not shown in FIG. 2). The rules are in 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 can reuse existing headers in an application flow from the source 202 or can use other headers added at the service sublayer 200. The headers may include a DetNet flow ID and may be arranged as metadata or as a packet header.

[0037] The DetNet flows 204 are received by the forwarding sublayer 206 and forwarded to lower layers 208 before making the return journey through the forwarding sublayer 206 and the service sublayer 200 to the destination 210 .

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

[0039] The present 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 IP-type PDU sessions. (DetNet over Ethernet TSN can be supported based on existing 3GPP and IETF standards and is therefore not within the scope of this work.) The solution should reuse functionality of the TSC Framework defined in Release 17 where applicable. The solution supports requests from a DetNet controller entity, including DetNet configuration for flow path establishment. The time synchronization framework in Release 17 is not modified because the synchronization mechanisms that can be used are outside the scope of the IETF DetNet standard. For DetNet, existing 3GPP routing mechanisms can be reused and no new routing functions will be specified in the 3GPP system. · Existing filtering mechanisms can be reused in the UE 116 and in the UPF 114 to identify traffic for QoS differentiation.

[0040] Based on SID purposes, when the service nodes of a network are configured as relays 300 as shown in FIG. 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 thus the relay node 306 forwards the DetNet flow 204 in accordance with the DetNet flow deterministic properties, as configured by a DetNet controller (not shown in FIG. 3).

[0042] FIG. 4 illustrates a UE 400 that may be used to implement the methods described herein. The UE 400 is used to implement one or more of the solutions described herein. The UE 400 conforms to one or more of the UEs described in the embodiments herein. In particular, the UE 400 conforms to the UE 116, and therefore, the reference number 400 is used below to indicate a UE according to the UE 116. The UE 400 includes a processor 405, a memory 410, an input device 415, an output device 420, and a transceiver 425.

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

[0044] As shown, 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 an unlicensed spectrum. Moreover, the transceiver 425 may include multiple UE panels supporting one or more beams. Additionally, 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 appreciated by those skilled in the art.

[0045] The processor 405 may include any known controller capable of executing computer-readable instructions and / or performing 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 the memory 410 to perform the methods and routines described herein. The processor 405 is communicatively coupled to the memory 410, the input device 415, the output device 420, and the transceiver 425.

[0046] The processor 405 may control the UE 400 to implement the UE behavior described herein. The processor 405 may include an application processor (also referred to as a “main processor”) that manages application domains and operating system (OS) functions, as well as a baseband processor (also referred to as a “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, a flash memory, or any other suitable non-volatile computer storage device. Memory 410 may include both volatile and non-volatile computer storage media.

[0048] The memory 410 may store relevant data for implementing the traffic category field as described herein. The memory 410 may also store program code and associated data, such as an operating system or other controller algorithms running on the UE 400.

[0049] The input devices 415 may include any known computer input devices, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. The input devices 415 may be integrated with the output devices 420, for example, as a touch screen or similar touch-sensitive display. The input devices 415 may include a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. The input devices 415 may include two or more different devices, such as a keyboard and a touch panel.

[0050] Output device 420 may be designed to output visual, audio, and / or tactile signals. Output device 420 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, 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 similar display device capable of outputting images, text, and the like to a user. As another non-limiting example, output device 420 may include a wearable display that is separate from but communicatively coupled to the rest of user equipment device 400, such as a smart watch, smart glasses, a head-up display, and the like. Additionally, output device 420 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0051] The output device 420 may include one or more speakers for generating sound. For example, the output device 420 may generate an acoustic alert or notification (e.g., a beep or chime). The output device 420 may include one or more haptic devices for generating vibration, movement, or other haptic feedback. All or a portion 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 touch screen 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 a mobile communications 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, as well as to receive messages, data, and other signals. For example, the processor 405 may selectively activate the transceiver 425 (or portions thereof) at particular times to send and receive messages.

[0053] The transceiver 425 includes at least one transmitter 430 and at least one receiver 435. The one or more transmitters 430 may be used to provide uplink communication signals to a base unit of a wireless communication network. Similarly, the 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 suitable number of transmitters 430 and receivers 435. Furthermore, the transmitters 430 and receivers 435 may be any suitable 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 a licensed radio spectrum, and a second transmitter / receiver pair used to communicate with a mobile communications network over an unlicensed radio spectrum may be combined into a single transceiver unit, e.g., a single chip, that performs functions for use with both licensed and unlicensed radio spectrums. The first transmitter / receiver pair and the second transmitter / receiver pair may share one or more hardware components. For example, some transceivers 425, transmitters 430, and receivers 435 may be implemented as physically separate components that access shared hardware and / or software resources, such as, for example, a network interface 440.

[0055] The transmitter(s) 430 and / or the receiver(s) 435 may be implemented and / or integrated in a single hardware component, such as a multi-transceiver chip, a system-on-chip, an application-specific integrated circuit ("ASIC"), or other type of hardware component. The transmitter(s) 430 and / or the receiver(s) 435 may be implemented and / or integrated in a multi-chip module. Other components, such as a network interface 440 or other hardware components / circuits, may be integrated in a single chip with any number of the transmitters 430 and / or receivers 435. The transmitters 430 and receivers 435 may be logically configured as a transceiver 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] 5 illustrates further details of a network node 500 that may be used to implement the methods described herein. The network node 500 may be an implementation of an entity in a wireless communication network, e.g., in one or more of the wireless communication networks described herein. The network node 500 may be, for example, a network function (NF) or application function (AF) or another entity of the UE 400 described above, or one or more of the wireless communication networks of the embodiments described herein. The network node 500 includes a processor 505, a memory 510, an input device 515, an output device 520, and a transceiver 525.

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

[0058] As shown, 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. Additionally, 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. As will be appreciated by one skilled in the art, other network interfaces 540 may be supported.

[0059] The processor 505 may include any known controller capable of executing computer-readable instructions and / or performing 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 the memory 510 to perform the methods and routines described herein. The processor 505 is communicatively coupled to the memory 510, the input device 515, the output device 520, and the 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, a flash memory, or any other suitable non-volatile computer storage device. Memory 510 may include both volatile and non-volatile computer storage media.

[0061] The memory 510 may store data related to establishing multipath unicast links and / or mobile operations. For example, the memory 510 may store parameters, configurations, resource allocations, policies, etc., as described herein. The memory 510 may also store program code and associated data, such as an operating system or other controller algorithms running on the network node 500.

[0062] The input device 515 may include any known computer input device, including a touch panel, buttons, a keyboard, a stylus, a microphone, etc. The input device 515 may be integrated with the output device 520, for example, as a touch screen or similar touch-sensitive display. The input device 515 may include a touch screen such that text may be entered using a virtual keyboard displayed on the touch screen and / or by handwriting on the touch screen. The input device 515 may include two or more different devices, such as a keyboard and a touch panel.

[0063] The output device 520 may be designed to output visual, audio, 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, and the like to a user. As another non-limiting example, the output device 520 may include a wearable display that is separate from but communicatively coupled to the rest of the network node 500, such as a smart watch, smart glasses, a head-up display, and the like. Furthermore, the output device 520 may be a component of a smartphone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, and the like.

[0064] The output device 520 may include one or more speakers for generating sound. For example, the output device 520 may generate an acoustic alert or notification (e.g., a beep or chime). The output device 520 may include one or more haptic devices for generating vibration, movement, or other haptic feedback. All or a portion 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 touch screen 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. The one or more transmitters 530 may be used to communicate with the UE 400, as described herein. Similarly, the 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 suitable number of transmitters 530 and receivers 535. Furthermore, the transmitters 530 and receivers 535 may be any suitable type of transmitter and receiver.

[0066] A proposed architecture 600 for supporting IETF DetNet relay nodes 306 in 5GS as shown in FIG. 3 is shown in FIG. 6, which illustrates the use of relay nodes 306 to support IETF DetNet flows 204.

[0067] In this embodiment, each 3GPP node (e.g., UE 400, UPF 114, etc.) used to route user plane traffic may be configured to act as a DetNet relay node 306. The UPF 114 may include or be considered as a NW relay node 114 supporting NW relay node functionality 602, and the UE 400 may support UE relay node functionality 604 as shown in FIG.

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

[0069] The NW relay node 114 and the UE relay node may exist outside the UE 400 and the UPF 114, respectively, i.e. as separate functions 602, 604, or the relay nodes 114, 400 may be collocated. Additionally, it is possible for 5GS to 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 as much as possible the IEEE TSN functionality of the 5GS system, where the DetNet-aware AF 605 receives configuration information in the form of a DetNet Yang traffic profile from a DetNet controller 606 (located outside the 3GPP domain) and converts said configuration information into TSC assistance information including QoS information, which is sent to a Policy Control Function (PCF) 608 in the 3GPP system. The PCF 608 determines Policy and Charging Control (PCC) rules based on the QoS information and instructs a Session Management Function (SMF) 610 to configure the UE's PDU sessions to be used for the DetNet flows 204 to support the QoS characteristics of said DetNet flows 204.

[0071] Receipt of configuration information by the DetNet-aware AF 605 is indicated in FIG. 6 by a single arrow and reference numeral 607 .

[0072] In order to support the architecture proposed in FIG. 6, the following needs to be done: · Configuring the UE 400 to be used as a relay node 306 and to establish a PDU session 612 for a DetNet flow 204. One option is for the UE 400 to be pre-configured with a DetNet relay node configuration. · Reporting IETF DetNet relay node support (i.e., the IP address of the UE 400 to be used as a relay node 306) to the DetNet controller 606. Discovery of DetNet end systems 302 located behind relay nodes 306. (This may be optional for instance-specific DetNet end systems interfacing with a particular UE that supports DetNet relay nodes.) Determining the propagation delay within 5GS when transmitting a DetNet flow 204. Receipt of DetNet flow configurations by the DetNet-aware AF 605 from the DetNet controller 606. The DetNet controller 606 may take into account the propagation delay reported by the 5GS. Mapping of DetNet flow configuration information including application flows and traffic profiles obtained by the DetNet-aware AF 605 from the DetNet controller 606 to 5GS QoS information (e.g., 5QI, TSC assistance information) of QoS flows in a corresponding PDU session 612 for the DetNet flow 204. Two or more application flows may map to the same DetNet flow 204. The mapping of DetNet flow configuration information by the DetNet-aware AF 605 to 5GS QoS information of QoS flows is indicated in FIG. 6 by a single arrow and reference numeral 614. · Establishment by the UE 400 of a PDU session 612 for relaying the DetNet flow 204 as shown in FIG.

[0073] FIG. 7 shows a procedure 700 for establishing a PDU session 612 for relaying a DetNet flow 204.

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

[0075] Establishing a PDU session 612 by the UE 400 is indicated in FIG.

[0076] In this embodiment, the UE 400 includes the requested S-NSSAI, DNN, and optionally DetNet Capability Indication in a PDU session establishment to be sent via the Access and Mobility Management (AMF) 704 to the SMF 610. The S-NSSAI, DNN, and DetNet Capability may be included outside a Session Management (SM) container that includes the PDU session establishment request such that the AMF 704 can select the appropriate SMF 610 to support the DetNet flow. The UL Non-Access Stratum (NAS) transport (S-NSSAI / DNN, DetNet Capability Indication, SM container PDU session establishment (including DNN, S-NSSAI, and optionally DetNet Capability)) from the UE 400 to the AMF 704 is indicated in FIG. 7 by a single arrow and reference numeral 706.

[0077] The DetNet capability indication may include information indicating: Support for relay, edge and / or transit nodes. Support for protocols for receiving DetNet configuration (e.g. NETCONF RFC6241 / YANG RFC6020 or PRE-CC RFC8283). Residence time information (i.e. the time for the UE relay node 604 to process the DetNet flow 204). For this purpose, the Device Side TSN Translator (DS-TT) functionality as specified in 3GPP TS23.501 v17.4.0 may be reused.

[0078] In this embodiment, the AMF 704 receives the request and selects the TSC-aware SMF 610 based on the requested S-NSSAI / DNN and / or the DetNet capability indication, if received from the UE 400. The selection of the TSC-aware SMF 610 by the AMF 704 is indicated in Figure 7 by reference numeral 708.

[0079] In this embodiment, the AMF 704 sends a Create Session Establishment request including the SM container received at 706 to the SMF 610. The sending of the Create Session Establishment request by the AMF 704 to the SMF 610 is indicated in FIG.

[0080] In this embodiment, the SMF 610 selects a PCF 608 with which to establish an SM Policy Association, and establishes the Policy Association with that PCF 608. The establishment of the SM Policy Association with a PCF 608 by the SMF 610 is indicated in FIG. 7 using a double arrow and reference numeral 712.

[0081] In this embodiment, the SMF 610 selects a DetNet-capable UPF 114 (i.e., a UPF 114 that supports relaying DetNet flows) based on the S-NSSAI / DNN and / or DetNet capability indication. The SMF 610 may interface with a Network Repository Function (NRF) to discover a DetNet-capable UPF 114 based on the S-NSSAI / DNN and / or DetNet capability indication. If the UE 400 requests two PDU sessions for redundancy, the SMF 610 ensures that a separate N3 tunnel is established to the selected UPF 114. The selection of the DetNet-capable UPF 114 by the SMF 610 is indicated in FIG. 7 by reference numeral 714.

[0082] In this embodiment, the SMF 610 acknowledges the request to the AMF 704. The sending of the acknowledge response by the SMF 610 to the AMF 704 is indicated in FIG.

[0083] In this embodiment, the SMF 610 initiates the N4 session establishment, which includes the rules for establishing the PDU session 612. During this procedure, the UPF 714 may provide DetNet capability information, which includes the following information: Support for relay, edge and / or transit nodes. Support for protocols for receiving DetNet configuration (e.g. NETCONF RFC6241 / YANG RFC6020 or PRE-CC RFC8283). Residence time information (i.e. the time that a NW relay node processes a DetNet flow 204). For this purpose, the Network Side TSN Translator (NW-TT) functionality as specified in 3GPP TS23.501 v17.4.0 may be reused.

[0084] Initiation of N4 session establishment by SMF 610 is indicated in FIG.

[0085] In this embodiment, the SMF 610 sends a PDU Session Accept message to the UE 400 via the AMF 704. The sending of the PDU Session Accept by the SMF 610 to the UE 400 is indicated in Figure 7 by a single arrow and respective reference numerals 720, 722.

[0086] In this embodiment, based on a subscription from the PCF 608 (via the AF 605), the SMF 610 provides the PCF 608 with the DetNet capabilities and IP addresses of the UE 400 and the UPF 114. The provision of the DetNet capabilities and IP addresses of the UE 400 and the UPF 114 to the PCF 608 is indicated in FIG. 7 by the double arrow and reference numeral 724.

[0087] In this embodiment, the PCF 608 forwards or reports the information to the DetNet-aware AF 605 by calling Npcf_PolicyAuthorization_Notify. The forwarding / reporting of information by the PCF 608 to the DetNet-aware AF 605 is indicated in FIG.

[0088] In this embodiment, the DetNet-aware AF 605 learns the IP addresses of the UE 400 and the UPF 114, as well as the potential latency of the DetNet flows 204 to traverse 5GS (i.e., between the UE 400 and the UPF 114). Learning the IP addresses of the UE 400 and the UPF 114, as well as the potential latency of the DetNet flows 204 by the DetNet-aware AF 605 is indicated in FIG. 7 by reference numeral 728.

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

[0090] In this embodiment, once the DetNet Controller 606 / DetNet-aware AF 605 knows the IP address of the UE 400, the DetNet Controller 606 / DetNet-aware AF 605 can use a neighbor discovery protocol as per IETF RFC4861 to discover the DetNet end systems 302 located behind the UE 400 and the UPF 114.

[0091] In this embodiment, the DetNet controller 606 or the DetNet-aware AF 605 can then determine the QoS characteristics for sending the DetNet flows 204 between the DetNet end systems 302. The DetNet controller 606 takes into account the latency in 5GS as reported by the UE 400 and the UPF 114.

[0092] Alternatively, the DetNet-aware AF 605 determines the DetNet-specific TSC assistance information taking into account the characteristics of the DetNet flows 204 according to information provided by the DetNet controller 606 in a DetNet Yang model configuration profile, as specified in draft-ietf-detnet-yang-16. In the Yang model, each DetNet flow 204 (associated with an ingress node and an egress node) 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 service. ·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 one-way latency and the maximum end-to-end one-way latency. · MaxLoss: This specifies the maximum packet loss ratio (PLR) parameter for the DetNet service between the ingress and egress of the DetNet domain. · MaxConsecutiveLossTolerance: This is the maximum consecutive loss tolerance parameter that represents the maximum number of consecutive packets that can be tolerated to be lost. · MaxMisordering: This represents the maximum allowable number of packets that can be received out of order. · Max-pkts-per-interval: This is the maximum number of packets that a source will send in one 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 a source will send in an interval.

[0093] In this embodiment, based on the traffic profile information, the DetNet-aware AF 605 determines the following TSC assistance information, as shown in the table below.

[0094] [Table 1]

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

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

[0097] The UE 400 establishes a PDU session 612 for the DetNet flow 204 as shown in Figure 6. The establishment of the PDU session 612 for the DetNet flow 204 by the UE 400 is indicated in Figure 8 by reference numeral 802.

[0098] In this embodiment, the DetNet controller 606 subscribes to be notified of DetNet nodes in the 3GPP system via the AF 605. In one embodiment, the AF 605 subscribes to PDU session status events and / or DetNet capabilities for a particular S-NSSAI / DNN (used for the DetNet flow 204). Subscribing to PDU session status events and / or DetNet capabilities by the AF 605 is indicated in FIG. 8 by reference numeral 804.

[0099] In an alternative embodiment, the AF 605 subscribes to the new event ID. The DetNet controller 606 discovers the IP addresses of the UEs 400 used as DetNet relay nodes 306 and the potential latency when the DetNet flows 204 are routed through the DetNet relay nodes 306 in the 5GS.

[0100] Returning to the embodiment of Figure 8, the DetNet controller 606 discovers the DetNet end systems 302 that interface with the UE 400 acting as a DetNet relay node 306 using procedures outside the scope of 3GPP. For example, the DetNet controller 606 may use a Neighbor Discovery protocol as per IETF RFC4861 to discover the DetNet end systems 302 located behind the UE 400 and the UPF 114. The discovery of the DetNet end systems 302 by the DetNet controller 606 is indicated in Figure 8 by reference numeral 806.

[0101] In this embodiment, the DetNet controller 606 provides configuration information for the DetNet flows 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 flows 204 by the DetNet controller 606 to the DetNet-aware AF 605 is indicated in FIG. 8 by a single arrow and reference numeral 808.

[0102] In this embodiment, the DetNet-aware AF 605 derives the DetNet-specific TSC assistance information, including QoS characteristics, from the DetNet configuration information provided by the DetNet controller 606 based on the IETF DetNet Yang profile. The derivation of the DetNet-specific TSC assistance information by the DetNet-aware AF 605 is indicated in FIG. 8 by reference numeral 810.

[0103] In this embodiment, the DetNet-aware AF 605 sends a request to the NEF 808 to establish an AF session with the required QoS, where the request includes the UE IP address and TSC support information along with DetNet-specific parameters and / or an indication to establish a QoS flow for the DetNet flow 204. The sending of the request by the DetNet-aware AF 605 to the NEF 808 to establish an AF session with the required QoS is indicated in FIG. 8 by a single arrow and reference numeral 812.

[0104] In this embodiment, the NEF 808 discovers the PCF 608 serving the UE 400 and sends an Npcf_PolicyAuthorizationRequest to the PCF 608. The Npcf_PolicyAuthorizationRequest may include the UE IP address and TSC assistance information. The sending of the Npcf_PolicyAuthorizationRequest by the NEF 808 to the PCF 608 serving the UE 400 is indicated in FIG. 8 by a single arrow and reference numeral 814.

[0105] If the AF 605 includes the respective QoS information, the NEF 808 interacts with a Time Sensitive Communication and Time Synchronization Function (TSCTSF) 816 to request the establishment of a corresponding session with the QoS requirements. The interaction with the TSCTSF 816 by the NEF 808 and the request for the establishment of the corresponding session are indicated in FIG. 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 TS 23.502 v17.4.0. The execution of these steps is indicated in Figure 8 by reference numeral 818.

[0107] The TSCTSF then acknowledges the request made by the NEF 808 at 816. The acknowledgment by the TSCTSF of the request made by the NEF 808 is indicated in FIG.

[0108] In this embodiment, the PCF 608 determines the PCC rules based on the TSC assistance information. The determination of the PCC rules by the PCF 608 based on the TSC assistance information is indicated in FIG.

[0109] The PCF 608 then acknowledges the Npcf_PolicyAuthorization request received by the NEF 808 at 814. The acknowledgement of the Npcf_PolicyAuthorization request by the PCF 608 is indicated in FIG.

[0110] In this embodiment, the NEF 808 acknowledges the AF session with a QoS response to the AF 605. The NEF 808 may create an AF session with the QoS response to the AF 605. The acknowledgement or creation by the NEF 808 of an AF session with a QoS response is indicated in FIG. 8 using a single arrow and reference numeral 826.

[0111] In this embodiment, the PCF 608 incorporates the updated PCC rules, i.e., the SM policy association updates, into the SMF 610 for the PDU session used for the DetNet flow 204. The incorporation of the updated PCC rules into the SMF 610 by the PCF 608 is indicated in FIG. 8 by the double arrow and reference numeral 828.

[0112] In this embodiment, the SMF 610 incorporates the N4 rules into the UPF 114. The incorporation of the N4 rules into the UPF 114 by the SMF 610 is indicated in Figure 8 by the double arrow and reference numeral 830. Once the user plane path is properly configured, i.e., once the DetNet controller 606 / DetNet aware AF 605 receives the response / acknowledge response at 826, the DetNet flow packets traverse the 3GPP domain as shown in Figure 9.

[0113] FIG. 9 shows a procedure 900 for routing DetNet flow packets through a DetNet-aware 5GS.

[0114] In this embodiment, an application 902 sends application packets to the DetNet end system 302. The sending of application packets by the application 902 to the DetNet end system is indicated in FIG.

[0115] In this embodiment, the DetNet end system 302 encapsulates the application packets into the DetNet flows 204. The encapsulation of the application packets by the DetNet end system 302 into the DetNet flows 204 is indicated in FIG.

[0116] In this embodiment, the DetNet end system 302 sends DetNet flow packets, e.g., IP packets, to a NW DetNet relay node 908, e.g., to the NW relay node function 602, in a DetNet flow 204. The sending of DetNet flow packets by the DetNet end system 302 to the NW DetNet relay node 908 is indicated in FIG. 9 by a single arrow and reference numeral 910.

[0117] In this embodiment, the NW DetNet relay node 908 processes the DetNet flow packets according to the DetNet configuration information. The processing of the DetNet flow packets according to the DetNet configuration information by the NW DetNet relay node 908 is indicated in FIG.

[0118] In this embodiment, the NW DetNet relay node 908 routes the DetNet flow packets to the UPF 114 in the DetNet flow 204. The routing of the DetNet flow packets by the NW DetNet relay node 908 to the UPF 114 is indicated in FIG.

[0119] In this embodiment, the UPF 114 sends the DetNet flow packets over the 3GPP tunnel to the UE 400. The sending of the DetNet flow packets over the 3GPP tunnel by the UPF 114 to the UE 400 is indicated in FIG.

[0120] In this embodiment, the UE 400 sends the DetNet flow packets to a UE DetNet relay node 918, e.g., to the UE relay node function 604, in the DetNet flow 204. The sending of the DetNet flow packets by the UE 400 to the UE DetNet relay node 918 is indicated in FIG. 9 by a single arrow and reference numeral 920. In this embodiment, the UE DetNet relay node 918 processes the DetNet flow packets in accordance with the DetNet configuration information. The processing of the DetNet flow packets by the UE DetNet relay node 918 in accordance with the DetNet configuration information is indicated in FIG. 9 by reference numeral 922.

[0121] In this embodiment, the UE DetNet relay node 918 forwards the DetNet flow packets to the DetNet end system 302. The forwarding of the DetNet flow packets by the UE DetNet relay node 918 to the DetNet end system 302 is indicated in FIG.

[0122] FIG. 10 illustrates an alternative embodiment of an architecture 1000 in which DetNet flows 204 are supported over a DetNet-non-aware 3GPP system.

[0123] In this alternative embodiment, the UE 400 and UPF 114 are unaware of the DetNet flow 204, but the 3GPP system is configured to route packets that include additional DetNet flows with QoS requirements similar to those of the DetNet flow 204. The UE 400 and UPF 114 may be considered as DetNet non-aware relay nodes 1002.

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

[0125] To support architecture 1000, the following needs to be done: The UE establishes a PDU session 612 as per 3GPP TS 23.502 v17.4.0. The UE 400 may request to establish a further redundant PDU session. The DetNet aware AF 605 subscribes to be informed of the IP address of the UE 400 used for the DetNet flows 204. Discovery of DetNet end systems 302 located behind relay nodes 306, i.e. behind the UE 400 and the UPF 114. The DetNet aware AF 605 receives DetNet flow configuration information from the DetNet controller 606. Mapping of DetNet flow configuration information obtained from the DetNet controller 606 to 5GS QoS information (e.g., 5QI, TSC assistance information) of the QoS flows in the corresponding PDU session 612 for the DetNet flow 204. The mapping of DetNet flow configuration information to 5GS QoS information of the QoS flows by the DetNet-aware AF 605 is indicated in FIG. 10 by a single arrow and reference numeral 614 and follows the actions 614 described above.

[0126] It shall be understood that much of the architecture 1000 corresponds to the architecture 600 described above with reference to Figure 6. For example, receipt of configuration information by the DetNet-aware AF 605 is indicated in Figure 10 by a single arrow and reference number 607, and follows action 607 described above. Where architecture 1000 includes an entity or action that corresponds to one described in architecture 600, the like reference number shall be understood to confer the same or similar role as that entity or action, unless otherwise noted.

[0127] The difference in this embodiment from the procedure 700 described in FIG. 7 when the UE 400 establishes the PDU session 612 is that the UE 400 does not report any DetNet capabilities and the SMF 610 reports the IP address of the UE 400 to the DetNet-aware AF 605 (corresponding to action 728 in FIG. 7). In the corresponding procedure in this embodiment, if the UE 400 and the UPF 114 support DS-TT and NW-TT functionality, respectively, the UE 400 and the UPF 114 may still report the residence time, in which case the residence time is forwarded to the DetNet-aware AF 605. This may be used by the DetNet controller 606 to determine the latency of the packets as they traverse the 5GS and to determine the appropriate QoS for the DetNet flow 204 to traverse the 5GS.

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

[0129] In one embodiment, there is provided a wireless communication device for communicating with a wireless communication network, the wireless communication device being a UE 400 configured to perform the procedures and participate in the architecture as described in the above embodiments.

[0130] A transceiver of the wireless communication device, i.e., the transceiver 425 of the UE 400, 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 be for the establishment of a user plane connection, for example the PDU session 612 established in the above embodiment. The request for the establishment of the user plane connection is made in this embodiment according to 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 the 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 a DNN, an S-NSSAI, or both.

[0133] In this embodiment, the first information may include the DetNet capabilities of the wireless communication device, i.e., the DetNet capabilities of the UE 400 as provided to the PCF 608 in the procedure 700 at 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, an edge node, a transit node, or a combination thereof.

[0135] In this embodiment, the DetNet capabilities of the wireless communication device may include the capability of the wireless communication device to support a neighbor discovery protocol and / or a DetNet configuration protocol.

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

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

[0138] In one embodiment, there is provided a method 1100 performed by the wireless communication device of the above embodiment. Figure 11 is a process flow diagram illustrating the method 1100, which includes sending a request by a transceiver of the wireless communication device, i.e., the transceiver 425 of the UE 400, to a wireless communication network, 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 complies with the DetNet-aware AF 605 described in the above embodiment and the network node 500 described above.

[0140] The AF comprises a transceiver, via transceiver 525, configured to send a subscription request to a first NF of the wireless communication network, the subscription request requesting notification of a network address of a device (e.g., UE 400) when the device establishes a user plane connection for supporting DetNet deterministic traffic. The first NF conforms to 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., the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF conforms to network node 500.

[0142] The transceiver is further configured to receive, in response to receiving the first information, i.e., the DetNet flow requirement, from the DetNet controller by the DetNet controller 606 described in the above embodiment.

[0143] In this embodiment, the AF further comprises a processor configured to convert the DetNet flow requirements into QoS requirements for relaying the DetNet traffic over the wireless communication network by the processor 505. The conversion of 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 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] Thus, the AF of this embodiment is configured to carry DetNet traffic over a wireless communication network and enforces DetNet flow requirements for the DetNet traffic (eg, the DetNet configuration information described in the above embodiments).

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

[0147] The processor may be configured to translate the DetNet flow requirements into QoS requirements for relaying the DetNet traffic over the wireless communications network that depend on information provided by the first device and / or the second NF. The information may comprise, for example, a residence time.

[0148] The first NF may be a NEF, for example, NEF 808 described above with reference to FIG.

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

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

[0151] In one embodiment, a method 1200 is provided that is performed by the AF of the above embodiment. Figure 12 is a process flow diagram illustrating the method 1200. The method includes, in step s1202, sending a subscription request to a first NF of the wireless communication network, where the subscription request requests notification of a network address of the device when the device establishes 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., the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF complies with network node 500.

[0153] The method includes, in step s1206, receiving DetNet flow requirements from the DetNet controller by the DetNet controller 606 described in the above embodiments in response to receiving the first information.

[0154] The method includes, in step s1208, translating the DetNet flow requirements into QoS requirements for relaying DetNet traffic over the wireless communication network. The translation of 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 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 communications network in accordance with QoS requirements for relaying DetNet traffic through the wireless communications network.

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

[0157] In one embodiment, a first NF in a wireless communication network is provided, the first NF comprising a transceiver configured to receive a subscription request from an AF of the wireless communication network, the subscription request requesting notification of a network address of a device when the device establishes a user plane connection for supporting DetNet deterministic traffic. The first NF conforms to the network node 500 described above.

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

[0159] The first NF may be a NEF, for example, NEF 808 described above with reference to FIG.

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

[0161] In one embodiment, a method 1300 is provided that is performed by a first NF of the above embodiment. Figure 13 is a process flow diagram illustrating the method 1300. The method includes, in step s1302, receiving a subscription request from an AF of the wireless communication network, the subscription request requesting notification of a network address of the device when the device establishes a user plane connection to support DetNet deterministic traffic. The first NF conforms to 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, the first information identifying that the second NF supports DetNet relay node functionality, i.e., the second NF is configured to function as a DetNet relay node 306 as described in the above embodiment. The second NF complies with network node 500.

[0163] In one embodiment, a UPF in a wireless communication network is provided, where the UPF is in accordance with the UPF 114 described in the above embodiment and in accordance with a network node 500. The UPF comprises a transceiver, i.e., transceiver 525, configured to receive a request from an SMF by an 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 the first information including the DetNet capabilities of the UPF. The first information may be sent in a container.

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

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

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

[0168] Advantageously, the methods and apparatus described herein help integrate support for DetNet using the IETF DetNet standard over 5GS. The solution helps enable a DetNet controller to discover nodes in a 3GPP system that are DetNet aware, and enables the controller to provide requirements such that the 3GPP network may establish user plane connections with QoS requirements that meet the QoS criteria of the DetNet flows.

[0169] Advantageously, the methods and apparatus described herein overcome existing problems of how to identify and discover UEs that support establishment of a user plane connection for DetNet traffic, and how to configure a 3GPP system, e.g., an existing 3GPP system, to support a user plane connection for DetNet traffic.

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

[0171] It should be noted that the above-described methods and apparatus illustrate rather than limit the invention, and that those skilled in the art can design many alternative configurations without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of elements or steps other than those listed in a claim, and "a" or "an" does not exclude a plural form, and a single processor or other unit may fulfill the functions of several units recited in a claim. Any reference signs in the claims shall not be construed as limiting their scope.

[0172] Additionally, while examples are given in the context of particular communication standards, these examples are not intended to be a limitation of the communication standards to which the disclosed methods and apparatus may be applied. For example, although particular 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] The method may also be embodied in a set of instructions stored on a computer-readable medium which, when loaded into a computer processor, a Digital Signal Processor (DSP), or the like, causes the processor to execute the method described above.

[0174] The described method and apparatus may be embodied in other specific forms. The described method and apparatus should be considered in all respects only as illustrative and not restrictive. The scope of the invention is therefore indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalency of the claims are to be embraced within their scope. [Explanation of symbols]

[0175] 100 Network Architecture 102 IEEE TSN Systems, TSN Networks 104 5GS Bridge 106 Protocol Data Unit (PDU) Sessions 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 Sublayer, DetNet-aware nodes 202 Source 204 DetNet Flows 206 Forwarding Sublayer 208 Lower Layer 210 Destination 300 Relay 302 IETF DetNet End Systems 306 Relay Node 400 User Equipment (UE) 405 Processor 410 Memory 415 Input Devices 420 output device 425 Transceiver 430 Transmitter 435 Receiver 440 Network Interface 445 Application Interface 500 network nodes 505 Processor 510 Memory 515 Input Devices 520 Output Device 525 Transceiver 530 Transmitter 535 Receiver 540 Network Interface 545 Application Interface 600 Architecture 602 NW relay node function 604 UE Relay Node Function 605 DetNet Aware AF 606 DetNet Controller 608 Policy Control Function (PCF) 610 Session Management Facility (SMF) 704 Access and Mobility Management (AMF) 808 NEF 816 Time-Sensitive Communications and Time Synchronization Functions (TSCTSF) 902 Application 908 NW DetNet relay node 918 UE DetNet Relay Node 1000 Architecture 1002 DetNet unaware relay nodes

Claims

1. A user equipment (UE) for wireless communication, comprising: at least one memory; at least one processor coupled to the at least one memory, the at least one processor causing the UE to: send a request to a wireless communication network, the request comprising first information for setting up a user plane connection for Deterministic Network (DetNet) data traffic; UE.

2. The UE according to claim 1, wherein the first information comprises at least one of a data network name or single network slice selection assistance information. The UE according to claim 1.

3. The UE according to claim 1, wherein one of the following holds: the first information corresponds to DetNet, or the first information includes the DetNet capability of the UE. The UE according to claim 1.

4. The UE according to claim 3, wherein the DetNet capability of the UE is defined such that the UE acts as at least one of a relay node, an edge node, or a transit node. The UE according to claim 3.

5. The UE according to claim 3, wherein the DetNet capability of the UE includes the ability to support one or more of a neighbor discovery protocol or a DetNet configuration protocol. The UE according to claim 3.

6. The UE according to claim 3, wherein the DetNet capability of the UE includes the ability to calculate a dwell time. The UE according to claim 3.

7. A network node that implements an application function in a wireless communication network, comprising: at least one memory; at least one processor coupled to the at least one memory, the at least one processor causing the network node to: send a subscription request to a first network function of the wireless communication network, the subscription request requesting notification of a network address of a user equipment (UE) that establishes a user plane connection for supporting Deterministic Network (DetNet) deterministic data traffic; 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 DetNet relay node functionality; Receiving, in response to the receiving of the first information, DetNet flow requirements from a DetNet controller, wherein the application function is configured to convert the DetNet flow requirements into quality of service (QoS) requirements for relaying the DetNet deterministic data traffic via the wireless communication network; Causing the second network function to transmit a second request to establish a user plane session with the wireless communication network according to the QoS requirements for relaying the DetNet deterministic data traffic via the wireless communication network; Network node. Claim 8 The at least one processor is configured to cause the application function to convert the DetNet flow requirements into the QoS requirements for relaying the DetNet deterministic data traffic via the wireless communication network depending on second information provided by one or more of the first device or the second network function; The network node according to claim 7. Claim 9 The first network function is a network exposure function The network node according to claim 7. Claim 10 The second network function is a user plane function The network node according to claim 7. Claim 11 The DetNet is IETF DetNet The network node according to claim 7. Claim 12 A method performed by a network implementing an application function of a wireless communication network, comprising: Sending a subscription request to a first network function of the wireless communication network, wherein the subscription request requests notification of a network address of a user equipment (UE) for establishing a user plane connection to support Deterministic Network (DetNet) deterministic data traffic; 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 DetNet relay node functionality; Receiving DetNet flow requirements from a DetNet controller in response to the first information; Converting the DetNet flow requirements into quality of service (QoS) requirements for relaying the DetNet deterministic data traffic via the wireless communication network; Sending a second request to the second network function to establish a user plane session with the wireless communication network according to the QoS requirements for relaying the DetNet deterministic data traffic via the wireless communication network; A method comprising the steps of. The method according to claim 13, further comprising the step of converting the DetNet flow requirements into the QoS requirements for relaying the DetNet deterministic data traffic via the wireless communication network depending on second information provided by one or more of the first device or the second network function. The method according to claim 12. The method according to claim 12, wherein the first network function is a network exposure function. The method according to claim 12. The method according to claim 12, wherein the second network function is a user plane function. The method according to claim 12. A processor for wireless communication, comprising: At least one controller coupled to at least one memory, the at least one controller causing the processor to: To send a request to a wireless communication network, the request being configured to cause transmission of the request comprising first information for setting up a user plane connection for Deterministic Network (DetNet) traffic A processor.

17. The first information comprises at least one of a data network name or single network slice selection assistance information The processor according to claim 16.

18. The first information either corresponds to DetNet or the first information includes the DetNet capability of a user equipment (UE) The processor according to claim 16.

19. The DetNet capability of the UE is defined such that the UE acts as at least one of a relay node, an edge node, or a transit node The processor according to claim 18.

20. The DetNet capability of the UE includes the capability to support one or more of a neighbor discovery protocol or a DetNet configuration protocol The processor according to claim 18.

Images