Method for supporting deterministic networks in wireless communication network

Abstract

There is provided a wireless communication device for communicating with a wireless communication network, the wireless communication device comprising a transceiver arranged to issue a request to the wireless communication network, the request comprising first information for establishing a user plane connection for deterministic network traffic.

Description

Technical Field

[0001] The subject matter disclosed herein generally relates to the field of enabling support for layer 3 deterministic networking in 5G systems. Background Art

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

[0003] In Release 17, support for Layer 2 deterministic networking (ie, IEEE Time-Sensitive Networking based on the IEEE 802.1q standard) is supported.

[0004] Therefore, the existing support of 3GPP systems for routed deterministic network services is based on Ethernet / layer 2-based interfaces, while IETF networks use IP-connected / layer 3-based interfaces. Summary of the invention

[0005] The problem with the proposed procedures for influencing the 3GPP system to establish a connection with specific quality of service requirements is that they do not provide functionality for the deterministic network controller to identify and / or discover suitable user equipment, nor do they provide functionality for the 3GPP network to be configured to support a suitable connection for deterministic services.

[0006] Disclosed herein is a process for supporting layer 3 deterministic networking in a 5G system. The above process can be implemented by the apparatus and architecture described herein.

[0007] A wireless communication device for communicating with a wireless communication network is provided, the wireless communication device comprising a transceiver arranged to issue a request to the wireless communication network, the request comprising first information for establishing a user plane connection for deterministic network services.

[0008] There is also provided a method in a wireless communication device arranged to communicate with a wireless communication network, the method comprising issuing a request to the wireless communication network, the request comprising first information for establishing a user plane connection for a deterministic network service.

[0009] An application function in a wireless communication network is also provided, the application function comprising a transceiver and a processor. The transceiver is arranged to: issue 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 a deterministic network deterministic service; 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 a deterministic network relay node function; receive a deterministic network flow requirement from a deterministic network controller in response to receiving the first information. The processor is arranged to convert the deterministic network flow requirement into a quality of service requirement for relaying deterministic network services through the wireless communication network. The transceiver is also arranged to issue a second request to the second network function to establish a user plane session with the wireless communication network based on the quality of service requirement for relaying deterministic network services through the wireless communication network.

[0010] A method in an application function of a wireless communication network is also provided, the method comprising issuing 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 a deterministic network deterministic service; 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 a deterministic network relay node function. The method also includes receiving a deterministic network flow requirement from a deterministic network controller in response to the first information; and converting the deterministic network flow requirement into a quality of service requirement for relaying the deterministic network service through the wireless communication network. The method also includes issuing a second request to the second network function to establish a user plane session with the wireless communication network based on the quality of service requirement for relaying the deterministic network service through the wireless communication network.

[0011] A first network function in a wireless communication network is also provided, the first network function comprising a transceiver. The transceiver is arranged to: receive a subscription request from an application 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 a deterministic network deterministic service; and send first information to the application function, the first information identifying the first device, and the first information identifying a second network function supporting a deterministic network relay node function.

[0012] A method in a first network function of a wireless communication network is also provided. The method includes receiving a subscription request from an application 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 a deterministic network deterministic service. The method also includes sending first information to the application function, the first information identifying the first device, and the first information identifying a second network function supporting a deterministic network relay node function.

[0013] A user plane function in a wireless communication network is also provided, the user plane function comprising a transceiver. The transceiver is arranged to receive from a session management function a request to establish a user plane session with the wireless communication network according to at least one quality of service requirement for relaying deterministic network traffic through the wireless communication network. The transceiver is further arranged to send a response to the session management function, the response indicating first information including deterministic network capabilities of the user plane function.

[0014] A method in a user plane function of a wireless communication network is also provided. The method includes receiving from a session management function a request to establish a user plane session with the wireless communication network according to at least one quality of service requirement for relaying deterministic network traffic through the wireless communication network. The method also includes sending a response to the session management function, the response indicating first information including deterministic network capabilities of the user plane function. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to describe the manner in which the advantages and features of the present disclosure can be obtained, the present disclosure is described by reference to certain devices and methods shown in the accompanying drawings. Each of these drawings depicts only certain aspects of the present disclosure and should not be considered as limiting the scope thereof. For the sake of clarity, the drawings may have been simplified and are not necessarily drawn to scale.

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

[0017] Figure 1 is a schematic diagram of a network architecture for supporting an IEEE time-sensitive networking system in a 5G system;

[0018] Figure 2 It is a schematic diagram of a network architecture used to support IETF deterministic networking;

[0019] Figure 3 is a schematic diagram of another network architecture for supporting IETF deterministic networks;

[0020] Figure 4 is a schematic diagram of a user equipment device that may be used to implement the methods described herein;

[0021] Figure 5 is a schematic diagram of a network node that can be used to implement the methods described herein;

[0022] Figure 6 is a schematic diagram of another network architecture for supporting an IETF deterministic network relay node in a 5G system;

[0023] Figure 7is a schematic diagram of a process for establishing a PDU session to relay a deterministic network flow;

[0024] Figure 8 is a schematic diagram of a process for configuring a 5G system with appropriate quality of service characteristics;

[0025] Fig. 9 is a schematic diagram of another process for routing deterministic network flow packets via a deterministic network-aware 5G system;

[0026] Fig.10 is a schematic diagram of yet another network architecture for supporting deterministic network flows via a deterministic network-unaware 5G system;

[0027] Fig.11 is a process flow diagram depicting a method performed by a wireless communication device in a wireless communication network;

[0028] Fig.12 is a process flow diagram depicting another method performed by an application function of a wireless communication network;

[0029] Fig.13 is a process flow diagram depicting yet another method performed by a first network function of a wireless communication network; and

[0030] Fig.14 is a process flow diagram illustrating another method performed by a user plane function of a wireless communication network. DETAILED DESCRIPTION

[0031] Those skilled in the art will appreciate that aspects of the present disclosure may be embodied as systems, devices, methods or program products. Therefore, the arrangements described herein may be implemented in full hardware form, full software form (including firmware, resident software, microcode, etc.), or in a combination of software and hardware aspects.

[0032] For example, the disclosed methods and apparatus may be implemented as hardware circuits, including custom very large scale integrated (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.

[0033] In addition, the method and apparatus may take the form of a program product embodied in one or more computer-readable storage devices storing machine-readable code, computer-readable code, and / or program code, hereinafter referred to as code. The storage device may be tangible, non-transitory, and / or non-transmitting. The storage device may not embody a signal. In some arrangements, the storage device uses only a signal for accessing the code.

[0034] Any combination of one or more computer readable media may be used. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical or semiconductor system, device or apparatus, or any suitable combination of the above.

[0035] More specific examples of storage devices (a non-exhaustive list) include: an electrical connection with one or more wires, a portable computer disk, 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 disk 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 document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0036] Throughout this specification, references to examples or similar language of a particular method or device indicate that a particular feature, structure, or characteristic described in conjunction with the example is included in at least one implementation of the method and device described herein. Therefore, unless otherwise expressly provided, references to features of examples or similar language of a particular method or device may, but do not necessarily, all refer to the same example, but rather to "one or more but not all examples". Unless otherwise expressly provided, the terms "include", "comprise", "have" and their variations mean "including but not limited to". Unless otherwise expressly provided, a list of items listed does not mean that any or all items are mutually exclusive. Unless otherwise expressly provided, the terms "one", "an" and "claimed" also mean "one or more".

[0037] 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 one and only one of any single item in the list. For example, "one of A, B, and C" includes only A, only B, or only C, and does not include a combination of A, B, and C. As used herein, "a member selected from A, B, and C" includes one and only one of A, B, or C, and does not include a 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, 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.

[0038] In addition, the features, structures or characteristics described herein may be combined in any suitable manner. In the following description, many 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, etc., to provide a comprehensive understanding of the present disclosure. However, those skilled in the relevant art will recognize that the disclosed methods and apparatus may be practiced without one or more of the specific details, or may be practiced using other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid confusing aspects of the present disclosure.

[0039] The following is a description of various aspects of the disclosed method and apparatus with reference to schematic flow charts and / or schematic block diagrams of methods, apparatuses, systems, and program products. It will be understood that each block of the schematic flow charts and / or schematic block diagrams and the combination of blocks in the schematic flow charts and / or schematic block diagrams can be implemented by code. The code can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that instructions executed by a processor of a computer or other programmable data processing device can create a component for implementing the function / action specified in the schematic flow charts and / or schematic block diagrams.

[0040] The code may also be stored in a storage device that can instruct a computer, other programmable data processing apparatus, or other device to work in a specific manner so that the instructions stored in the storage device produce an article of manufacture that includes instructions for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0041] The code may also be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operating steps are executed on the computer, other programmable apparatus, or other device, thereby producing a computer-implemented process, so that the code executed on the computer or other programmable apparatus provides a process for implementing the functions / actions specified in the schematic flowchart and / or schematic block diagram.

[0042] The schematic flow charts and / or schematic block diagrams in the figure illustrate the possible implementation architectures, functions and operations of the device, system, method and program product. In this regard, each block in the schematic flow chart and / or schematic block diagram can represent a code module, segment or portion, which includes one or more executable instructions for implementing the code of (multiple) specified logical functions.

[0043] It should also be noted that in some alternative implementations, the functions shown in the blocks may not appear in the order shown in the figures. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order, depending on the functions involved. Other steps and methods are contemplated that are equivalent in function, logic or effect to one or more blocks or portions thereof of the illustrated figures.

[0044] The description of the elements in each figure can refer to the elements in the subsequent figures. The same numbers represent the same elements in all figures.

[0045] 3GPP has defined support for deterministic networks since Release 17. In Release 17, support for Layer 2 deterministic networks (i.e., IEEE Time Sensitive Networking based on the IEEE 802.1Q standard) is supported.

[0046] To support IEEE Time-Sensitive Networking (TSN), the 5GS system is configured as a Layer 2 bridge, such as Figure 1 shown. Figure 1 and 3 GPP TS23.501v17.4.0 Figure 5 .28.1-1 is the same as, and depicts a network architecture 100 for supporting an IEEE TSN system 102 in a 5G system (5GS).

[0047] To support TSN scheduling services (IEEE Std802.1Q-2018

[98] Section 8.6.8.4) via the 5GS bridge 104, the 5GS supports the following functions:

[0048] Configure bridge information in 5GS.

[0049] After the establishment of the protocol data unit (PDU) session 106 , the bridge information of the 5GS bridge 104 is reported to the TSN network 102 .

[0050] Receive configuration information from the TSN network 102.

[0051] Mapping the configuration information obtained from the TSN network to the 5GS Quality of Service (QoS) information (e.g., 5QI, Time Sensitive Communication (TSC) assistance information) of the QoS flow in the corresponding PDU session 108 to achieve efficient time-aware scheduling.

[0052] The network-side TSN translator (NW-TT) 110 and device-side TSN translator (DS-TT) 112 functions located at the user plane function (UPF) 114 and the user equipment device (UE) 116, respectively, are responsible for calculating the propagation delay within the 5GS, which is used to adjust the time synchronization clock.

[0053] As part of Release 18, a new study was agreed to support layer 3 deterministic networking in 5GS systems (specifically the IETF DetNet standard described in IETF RFC 8938). A very basic description of IETF DetNet support is as follows Figure 2 shown. Figure 2 In particular, a deterministic network (DetNet)-aware node, i.e., a service sublayer 200, is depicted, which receives application packets from a source 202 (which is DetNet-unaware) and encapsulates the packets into a DetNet flow 204 having certain deterministic characteristics (e.g., certain QoS, delay tolerance, etc.). The DetNet-aware node 200 is based on a DetNet controller ( Figure 2 The information (rules) provided by the DetNet flow (not shown) encapsulates the packets into the DetNet flow 204. These rules take the form of the DetNet Yang model, as described in draft-ietf-detnet-yang-16. This document contains the configuration and operational data specifications of a DetNet flow (such as DetNet flow 204).

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

[0055] DetNet flow 204 is received by forwarding sublayer 206 and forwarded to lower layer 208 before being returned to destination 210 via forwarding sublayer 206 and serving sublayer 200 .

[0056] At the forwarding sublayer 106, resources for DetNet flows are allocated to explicit routes according to RFC8938.

[0057] The currently disclosed arrangement involves the following assumptions:

[0058] Only IP-based DetNet is in scope; Multiprotocol Label Switching (MPLS)-based DetNet is not in scope.

[0059] IP-based DetNet services are carried in IP-type PDU sessions. (DetNet over Ethernet TSN is not in the scope of this work because it can be supported based on existing 3GPP and IETF standards.)

[0060] The solution should reuse functionality of the TSC framework defined in version 17 where applicable.

[0061] These solutions support requests from the DetNet controller entity, including DetNet configuration for flow path establishment.

[0062] The time synchronization framework has not been modified in Release 17, as the synchronization mechanisms that can be used are outside the scope of the IETF DetNet specification.

[0063] Existing 3GPP routing mechanisms can be reused for DetNet; no new routing functions will be defined in the 3GPP system.

[0064] • Existing filtering mechanisms can be reused in UE 116 and UPF 114 to identify traffic for QoS differentiation.

[0065] Based on the SID target, the following IETF DetNet implementation is supported, where the service node of the network is configured as a relay 300, such as Figure 3 shown.

[0066] The IETF DetNet terminal system 302 may have encapsulated one or more application flows into the DetNet flow 204, and thus the relay node 304 forwards the DetNet flow 204 according to the DetNet flow deterministic characteristics, such as from the DetNet controller ( Figure 3 (not shown) configuration.

[0067] Figure 4 A UE 400 that can be used to implement the methods described herein is depicted. The UE 400 is used to implement one or more of the solutions described herein. The UE 400 is consistent with one or more of the UEs described in the embodiments herein. Specifically, the UE 400 is consistent with the UE 116, and therefore the reference numeral 400 is used hereinafter to indicate a UE consistent with 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.

[0068] The input device 415 and the output device 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 415 and / or output device 420. The UE 400 may include one or more of a processor 405, a memory 410, and a transceiver 425, and may not include an input device 415 and / or an output device 420.

[0069] As shown, the transceiver 425 includes at least one transmitter 430 and at least one receiver 435. The transceiver 425 can communicate with one or more cells (or wireless coverage areas) supported by one or more base units. The transceiver 425 can be operable on an unlicensed spectrum. In addition, the transceiver 425 can include multiple UE panels supporting one or more beams. In addition, the transceiver 425 can support at least one network interface 440 and / or application interface 445. (Multiple) application interface 445 can support one or more APIs. (Multiple) network interface 440 can support 3GPP reference points, such as Uu, N1, PC5, etc. As understood by those of ordinary skill in the art, other network interfaces 440 can be supported.

[0070] Processor 405 may include any known controller capable of executing computer-readable instructions and / or capable of performing logical operations. For example, 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. Processor 405 may execute instructions stored in memory 410 to perform the methods and routines described herein. Processor 405 is communicatively coupled to memory 410, input device 415, output device 420, and transceiver 425.

[0071] Processor 405 may control UE 400 to implement UE behaviors described herein. Processor 405 may include an application processor (also referred to as a main processor) that manages application domain and operating system (OS) functions and a baseband processor (also referred to as a baseband radio processor) that manages radio functions.

[0072] 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 (DRAM), synchronous dynamic RAM (SDRAM) and / or static RAM (SRAM). Memory 410 may include non-volatile computer storage media. For example, memory 410 may include a hard drive, flash memory, or any other suitable non-volatile computer storage device. Memory 410 may include both volatile and non-volatile computer storage media.

[0073] Memory 410 may store data related to implementing the traffic class field as described herein.Memory 410 may also store program code and related data, such as an operating system or other controller algorithms operating on UE 400.

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

[0075] Output device 420 may be designed to output visual, auditory 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 a similar display device capable of outputting images, text, etc. 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 device apparatus 400, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 420 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0076] Output device 420 may include one or more speakers for producing sound. For example, output device 420 may produce an audible alarm or notification (e.g., a beep or buzzer). Output device 420 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 420 may be integrated with input device 415. For example, input device 415 and output device 420 may form a touch screen or similar touch-sensitive display. Output device 420 may be located near input device 415.

[0077] 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 send messages, data and other signals, and also receives messages, data and other signals. For example, the processor 405 can selectively activate the transceiver 425 (or part thereof) at a specific time to send and receive messages.

[0078] The transceiver 425 includes at least one transmitter 430 and at least one receiver 435. One or more transmitters 430 can be used to provide uplink communication signals to the base unit of the wireless communication network. Similarly, one or more receivers 435 can be used to receive downlink communication signals from the base unit. Although only one transmitter 430 and one receiver 435 are shown, the UE 400 can have any suitable number of transmitters 430 and receivers 435. In addition, (multiple) transmitters 430 and (multiple) receivers 435 can be any suitable type of transmitter and receiver. The transceiver 425 may include a first transmitter / receiver pair for communicating with a mobile communication network through a licensed radio spectrum, and a second transmitter / receiver pair for communicating with a mobile communication network through an unlicensed radio spectrum.

[0079] A first transmitter / receiver pair that can be used to communicate with a mobile communication network via a licensed radio spectrum and a second transmitter / receiver pair that can be used to communicate with a mobile communication network via an unlicensed radio spectrum can be combined into a single transceiver unit, such as 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 can share one or more hardware components. For example, some transceivers 425, transmitters 430, and receivers 435 can be implemented as physically independent components that access shared hardware resources and / or software resources, such as a network interface 440.

[0080] 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 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 with any number of transmitters 430 and / or receivers 435. Transmitters 430 and receivers 435 may be logically arranged as transceivers 425 using one or more common control signals, or may be arranged as modular transmitters 430 and receivers 435 implemented in the same hardware chip or multi-chip module.

[0081] Figure 5 Depicted are further details of a network node 500 that can be used to implement the methods described herein. The network node 300 can be an implementation of an entity in a wireless communication network, such as in one or more of the wireless communication networks described herein. The network node 500 can be, for example, the above-mentioned UE 400, or a network function (NF) or application function (AF) or another entity of one or more wireless communication networks in 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.

[0082] The input device 515 and the output device 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 device 515 and / or output device 520. The network node 500 may include one or more of a processor 505, a memory 510, and a transceiver 525, and may not include an input device 515 and / or an output device 520.

[0083] As shown, the transceiver 525 includes at least one transmitter 530 and at least one receiver 535. Here, the transceiver 525 communicates with one or more remote units 400. In addition, the transceiver 525 can support at least one network interface 540 and / or application interface 545. (Multiple) application interface 545 can support one or more APIs. (Multiple) network interface 540 can support 3GPP reference points such as Uu, N1, N2 and N3. As understood by those of ordinary skill in the art, other network interfaces 540 can be supported.

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

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

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

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

[0088] Output device 520 can be designed to output visual, auditory and / or tactile signals. Output device 520 may include an electronically controllable display or display device capable of outputting visual data to a user. For example, 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, output device 520 may include a wearable display that is separate from the rest of network node 500 but communicatively coupled, such as a smart watch, smart glasses, a head-up display, etc. In addition, output device 520 may be a component of a smart phone, a personal digital assistant, a television, a desktop computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, etc.

[0089] Output device 520 may include one or more speakers for producing sound. For example, output device 520 may produce an audible alarm or notification (e.g., a beep or buzzer). Output device 520 may include one or more tactile devices for producing vibration, motion, or other tactile feedback. All or part of output device 520 may be integrated with input device 515. For example, input device 515 and output device 520 may form a touch screen or similar touch-sensitive display. Output device 520 may be located near input device 515.

[0090] 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 335 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. In addition, the (multiple) transmitters 530 and (multiple) receivers 535 may be any suitable type of transmitter and receiver.

[0091] Figure 6 In the figure, it is shown that the Figure 3 The architecture 600 proposed for the IETF DetNet relay node 306 in the 5GS is shown in FIG. Figure 6 The use of relay nodes 306 to support IETF DetNet flows 204 is depicted.

[0092] In this embodiment, each 3GPP node for routing user plane traffic (e.g., UE 400, UPF 114, etc.) may be configured to act as a DetNet relay node 306. UPF 114 may include or be considered as a NW relay node 114 supporting NW relay node functionality 602, and UE 400 may support UE relay node functionality 604, such as Figure 6 shown.

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

[0094] The NW relay node 114 and the UE relay node can be located outside the UE 400 and the UPF 114, respectively, i.e., as separate functions 602, 604, or the above relay nodes 114, 400 can be collocated. In addition, depending on the implementation, the 5GS can support only one relay node 306, i.e., only support the UE relay node 400 or the NW relay node 114 relay node.

[0095] It is recommended to reuse the IEEE TSN functions of the 5GS system as much as possible, where the DetNet-aware AF 605 receives configuration information from the DetNet controller 606 (located outside the 3GPP domain) in the form of a DetNetYang service profile, and converts the above configuration information into TSC auxiliary information containing QoS information, which is sent to the Policy Control Function (PCF) 608 within the 3GPP system. The PCF 608 determines the policy and charging control (PCC) rules based on the QoS information, and instructs the Session Management Function (SMF) 610 to configure the UE's PDU session for the DetNet flow 204, thereby supporting the QoS characteristics of the above DetNet flow 204.

[0096] DetNet senses the AF 605 receiving the configuration information Figure 6 Indicated by a single arrow and reference numeral 607 .

[0097] To support Figure 6 The architecture proposed in , requires the following measures:

[0098] • The UE 400 is configured to act as a relay node 306 and a PDU session 612 is established for the DetNet flow 204. One option is that the UE 400 is pre-configured with a DetNet relay node configuration.

[0099] Report IETF DetNet relay node support to DetNet controller 606 (i.e.

[0100] The IP address of the UE 400 acting as the relay node 306).

[0101] • Discover the DetNet Terminal System 302 located behind the Relay Node 306. (This may be optional in the case of a specific DetNet Terminal System interfacing with a specific UE supporting DetNet Relay Nodes).

[0102] Determine the propagation delay within 5GS when sending the DetNet stream 204.

[0103] The DetNet-aware AF 605 receives the DetNet flow configuration from the DetNet controller 606 .

[0104] The DetNet controller 606 may take into account the propagation delay reported by the 5GS.

[0105] · Map the DetNet flow configuration information (including application flow and service profile) obtained by the DetNet-aware AF 605 from the DetNet controller 606 to the 5GS QoS information (e.g., 5QI, TSC auxiliary information) of the QoS flow in the corresponding PDU session 612 of the DetNet flow 204. More than one application flow can be mapped to the same DetNet flow 204. The DetNet-aware AF 605 maps the DetNet flow configuration information to the 5GS QoS information of the QoS flow in Figure 6 Indicated by a single arrow and reference numeral 614 .

[0106] UE 400 establishes a PDU session 612 to relay the DetNet flow 204, such as Figure 7 shown.

[0107] Figure 7 A process 700 for establishing a PDU session 612 to relay a DetNet flow 204 is depicted.

[0108] The UE 400 that is DetNet-aware (i.e., operating as a relay node) is triggered (based on the configuration information) to establish a PDU session 612 for relaying the DetNet flow 204. The UE 400 is preconfigured to act as a DetNet-aware node, i.e., a relay node 306. The UE 400 can be configured to establish dual connectivity by establishing two redundant PDU sessions on the 5G network. The UE 400 can use duplicate paths to support redundancy of the DetNet flow 204 according to the DetNet flow requirements.

[0109] The PDU session 612 is established by the UE 400 at Figure 7 Indicated by reference numeral 702.

[0110] In this embodiment, the UE 400 includes the requested S-NSSAI, DNN, and optional DetNet capability indication in the PDU session establishment to be issued to the SMF 610 via the access and mobility management (AMF) 704. The S-NSSAI, DNN, and DetNet capability may be included outside the session management (SM) container including the PDU session establishment request so that the AMF 704 can select the appropriate SMF 610 to support the DetNet flow. UL Non-Access Stratum (NAS) Transport from UE 400 to AMF 704 (S-NSSAI / DNN, DetNet Capability Indication, SM Container PDU Session Establishment (Including DNN, S-NSSAI and Optional DetNet Capability) Figure 7 Indicated by a single-headed arrow and reference numeral 706 .

[0111] The DetNet capability indication may include information indicating the following:

[0112] Support relay nodes, edge nodes and / or transport nodes;

[0113] Support for the protocol used to receive DetNet configuration (e.g., NETCONF RFC6241 / YANG RFC6020 or PRE-CC RFC 8283);

[0114] • Dwell time information (ie, the time for the UE relay node 604 to process the DetNet flow 204). The Device Side TSN Translator (DS TT) functionality defined in 3GPP TS 23.501 v17.4.0 may be reused for this purpose.

[0115] 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 received from the UE 400. The selection of the TSC-aware SMF 610 by the AMF 704 is as follows: Figure 7 Indicated by reference numeral 708.

[0116] In this embodiment, AMF 704 issues a create session establishment request to SMF 610, the request including the SM container received at 706. AMF 704 issues a create session establishment request to SMF 610 at Figure 7 Indicated by a single arrow and reference numeral 710 .

[0117] In this embodiment, the SMF 610 selects the PCF 608 with which the SM policy association is to be established, and establishes the above SM policy association with the PCF 608. The SMF 610 establishes the SM policy association with the PCF 608. Figure 7Indicated by a double-headed arrow and reference numeral 712.

[0118] In this embodiment, the SMF 610 selects a UPF 114 with DetNet capability (i.e., a UPF 114 that supports relaying of 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 UPF 114 with DetNet capability 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 for the selected UPF 114. The selection of the UPF 114 with DetNet capability by the SMF 610 is performed in accordance with the S-NSSAI / DNN and / or DetNet capability indication. Figure 7 Indicated by reference numeral 714.

[0119] In this embodiment, SMF 610 confirms the request to AMF 704. SMF 610 sends a confirmation response to AMF 704. Figure 7 Indicated by a single arrow and reference numeral 716.

[0120] In this embodiment, SMF 610 initiates N4 session establishment, which includes rules for establishing PDU session 612. In this process, UPF 714 can provide DetNet capability information, which includes the following information.

[0121] Support relay nodes, edge nodes and / or transport nodes;

[0122] Support for the protocol used to receive DetNet configuration (e.g., NETCONF RFC6241 / YANG RFC6020 or PRE-CC RFC 8283);

[0123] • Dwell time information (ie, the time the NW relay node processes the DetNet flow 204).

[0124] Network-side TSN Translator (NW TT) defined in 3GPP TS23.501v17.4.0

[0125] Functions can be reused for this purpose.

[0126] SMF 610 initiates N4 session establishment Figure 7 Indicated by a double-headed arrow and reference numeral 718.

[0127] In this embodiment, SMF 610 sends a PDU session accept message to UE 400 via AMF 704. SMF 610 sends a PDU session accept message to UE 400. Figure 7 Indicated by a single-headed arrow and corresponding reference numerals 720, 722.

[0128] In this embodiment, based on the subscription from PCF 608 (via AF 605), SMF 610 provides the DetNet capabilities and IP addresses of UE 400 and UPF 114 to PCF 608. Figure 7 Indicated by a double-headed arrow and reference numeral 724.

[0129] In this embodiment, the PCF 608 forwards (ie, reports) this information to the DetNet-aware AF 605 by calling Npcf_PolicyAuthorization_Notify. The PCF 608 forwards / reports this information to the DetNet-aware AF 605 in Figure 7 Indicated by a double-headed arrow and reference numeral 726.

[0130] In this embodiment, the DetNet-aware AF 605 learns the IP addresses of the UE 400 and the UPF 114 and the potential delay of the DetNet flow 204 to traverse the 5GS (i.e., between the UE 400 and the UPF 114). The DetNet-aware AF 605 learns the IP addresses of the UE 400 and the UPF 114 and the potential delay of the DetNet flow 204. Figure 7 Indicated by reference numeral 728 in the figure.

[0131] In an alternative embodiment, the DetNet controller 606 learns the IP address of the UE 400 used as the DetNet relay node 306 by subscribing to the 5GS PDU session status request via the network open function (NEF) (from the AF) to include the S-NSSAI / DNN and / or DetNet capability indication (for the slice or DNN of the DetNet flow) in the subscription request. This process is as described in 3GPP TS 23.502 v17.4.0 Figure 4 .As described in 15.3.2.3-1.

[0132] In this embodiment, after the DetNet controller 606 / DetNet-aware AF 605 perceives the IP address of the UE 400 , the DetNet controller 606 / DetNet-aware AF 605 may discover the DetNet terminal system 302 located behind the UE 400 and the UPF 114 using a neighbor discovery protocol according to IETF RFC 4861.

[0133] In this embodiment, the DetNet controller 606 or the DetNet-aware AF 605 may then determine QoS characteristics for issuing the DetNet flow 204 between the DetNet end systems 302. The DetNet controller 606 takes into account the delay within the 5GS reported by the UE 400 and the UPF 114.

[0134] Alternatively, the DetNet-aware AF 605 determines the DetNet-specific TSC auxiliary information based on the information provided by the DetNet controller 606 in the DetNet Yang model configuration profile, taking into account the characteristics of the DetNet flow 204, as defined in draft-ietf-detnet-yang-16. In the Yang model, each DetNet flow 204 (associated with ingress and egress nodes) is associated with a traffic profile containing the following information:

[0135] Minimum bandwidth: This is the minimum bandwidth that must be guaranteed for the provision of DetNet services.

[0136] Maximum Delay: This is the maximum delay from the ingress to the egress node in nanoseconds.

[0137] Maximum delay variation: This is the difference between the minimum and maximum end-to-end one-way delay,

[0138] The unit is nanoseconds.

[0139] MaxLoss: This defines the maximum packet loss rate (PLR) parameter of the DetNet service between the ingress(s) and egress(s) of the DetNet domain.

[0140] MaxConsecutiveLossTolerance: This is the maximum consecutive loss tolerance parameter,

[0141] It describes the maximum number of consecutive packets whose loss can be tolerated.

[0142] MaxMisordering: This describes the maximum tolerable number of packets that can be received out of order.

[0143] Max-pkts-per-interval: This is the maximum number of packets that the source will send in one interval.

[0144] Leaf max-payload-size: This is the maximum payload size that the source will send.

[0145] Min-payload-size: This is the minimum payload size that the source will send.

[0146] Leaf min-pkts-per-interval: This is the minimum number of packets that the source will send in one interval.

[0147] In this embodiment, based on the service profile information, the DetNet-aware AF 605 determines the following TSC auxiliary information, as shown in the following table.

[0148]

[0149] Table 1: TSC auxiliary information of DetNet stream.

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

[0151] Figure 8 Depicted is a process 800 for configuring a 5GS with appropriate QoS characteristics.

[0152] UE 400 establishes a PDU session 612 for DetNet flow 204, such as Figure 6 UE 400 establishes a PDU session 612 for DetNet flow 204. Figure 8 Indicated by reference numeral 802.

[0153] In this embodiment, the DetNet controller 606 subscribes to be notified of DetNet nodes in the 3GPP system via the AF 605. In an embodiment, the AF 605 subscribes to PDU session status events for specific S-NSSAI / DNN (for DetNet flow 204) and / or DetNet capabilities. The subscription of the AF 605 to PDU session status events and / or DetNet capabilities is Figure 8 Indicated by reference numeral 804.

[0154] In an alternative embodiment, the AF 605 subscribes to a new event ID. When the DetNet flow 204 is routed via the DetNet relay node 306 in the 5GS, the DetNet controller 606 discovers the IP address and potential delay of the UE 400 acting as the DetNet relay node 306.

[0155] Return to Figure 8In an embodiment, the DetNet controller 606 uses a process outside the scope of 3GPP to discover the DetNet terminal system 302 connected to the interface of the UE 400 acting as the DetNet relay node 306. For example, the DetNet controller 606 can use the neighbor discovery protocol according to IETF RFC 4861 to discover the DetNet terminal system 302 located behind the UE 400 and the UPF 114. The discovery of the DetNet terminal system 302 by the DetNet controller 606 is as follows: Figure 8 Indicated by reference numeral 806.

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

[0157] In this embodiment, based on the IETF DetNet Yang profile, 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. The DetNet-specific TSC assistance information derived by the DetNet-aware AF 605 is Figure 8 Indicated by reference numeral 810.

[0158] In this embodiment, the DetNet-aware AF 605 sends a request to the NEF 808 to establish an AF session with the required QoS, the request including the UE IP address and TSC assistance information, as well as DetNet-specific parameters and / or an indication to establish a QoS flow for the DetNet flow 204. The DetNet-aware AF 605 sends a request to the NEF 808 to establish an AF session with the required QoS. Figure 8 Indicated by a single arrow and reference numeral 812.

[0159] In this embodiment, NEF 808 finds that PCF 608 serves UE 400 and issues Npcf_PolicyAuthorizationRequest to PCF 608. Npcf_PolicyAuthorizationRequest may include UE IP address and TSC assistance information. NEF 808 issues Npcf_PolicyAuthorizationRequest to PCF 608 serving UE 400. Figure 8 Indicated by a single arrow and reference numeral 814 .

[0160] If the AF 605 includes individual QoS information, the NEF 808 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 the NEF 808 and the TSCTSF 816 and the establishment request of the corresponding session are described in detail in the following sections. Figure 8 Indicated by a single arrow and reference numeral 816.

[0161] In this case, the 3GPP TS23.502v17.4.0 Figure 4 .15.6.6-1 as described in steps 3b to 4a. These steps are performed in Figure 8 Indicated by reference numeral 818 in the figure.

[0162] The TSCTSF then acknowledges the request made by the NEF 808 at 816. The TSCTSF acknowledges the request made by the NEF 808 at 816. Figure 8 Indicated by a single arrow and reference numeral 820 .

[0163] In this embodiment, the PCF 608 determines the PCC rules based on the TSC assistance information. Figure 8 Indicated by reference numeral 822 in the figure.

[0164] 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 at 814. Figure 8 Indicated by a single-headed arrow and reference numeral 824 .

[0165] In this embodiment, the NEF 808 confirms the AF session by a QoS response to the AF 605. The NEF 808 may create an AF session with a QoS response to the AF 605. The NEF 808 confirms or creates an AF session with a QoS response. Figure 8Indicated by a single arrow and reference numeral 826.

[0166] In this embodiment, PCF 608 installs updated PCC rules, i.e., SM policy association updates, to SMF 610 for the PDU session for (multiple) DetNet flows 204. PCF 608 installs updated PCC rules to SMF 610 at Figure 8 Indicated by a double-headed arrow and reference numeral 828.

[0167] In this embodiment, SMF 610 installs N4 rules to UPF 114. SMF 610 installs N4 rules to UPF 114 Figure 8 Indicated by the bidirectional arrow and reference numeral 830. ##After the user plane path is appropriately configured, i.e. after the DetNet controller 606 / DetNet aware AF 605 receives the response / confirmation at 826, the DetNet flow packets traverse the 3GPP domain, as shown in FIG. Fig. 9 shown.

[0168] Fig. 9 Depicted is a process 900 for routing DetNet flow packets via a DetNet-aware 5GS.

[0169] In this embodiment, the application 902 sends an application packet to the DetNet terminal system 302. The application 902 sends an application packet to the DetNet terminal system. Fig. 9 Indicated by a single arrow and reference numeral 904 .

[0170] In this embodiment, the DetNet terminal system 302 encapsulates the application packet into the DetNet stream 204. The DetNet terminal system 302 encapsulates the application packet into the DetNet stream 204. Fig. 9 Indicated by reference numeral 906 in the figure.

[0171] In this embodiment, the DetNet terminal system 302 sends a DetNet flow packet, such as an IP packet, to the NW DetNet relay node 908 (e.g., to the NW relay node function 602) in the DetNet flow 204. The DetNet terminal system 302 sends a DetNet flow packet to the NW DetNet relay node 908. Fig. 9 Indicated by a single arrow and reference numeral 910 .

[0172] In this embodiment, the NW DetNet relay node 908 processes the DetNet flow packets according to the DetNet configuration information. Fig. 9 Indicated by reference numeral 912.

[0173] In this embodiment, the NW DetNet relay node 908 sends the DetNet flow packets to the UPF 114 in the DetNet flow 204. The NW DetNet relay node 908 sends the DetNet flow packets to the UPF 114 in Fig. 9 Indicated by a single-headed arrow and reference numeral 914 .

[0174] In this embodiment, UPF 114 sends DetNet flow packets to UE 400 via a 3GPP tunnel. UPF 114 sends DetNet flow packets to UE 400 via a 3GPP tunnel. Fig. 9 Indicated by reference numeral 916 in the figure.

[0175] In this embodiment, the UE 400 sends a DetNet flow packet to the UE DetNet relay node 918 (eg, to the UE relay node function 604) in the DetNet flow 204. The UE 400 sends a DetNet flow packet to the UE DetNet relay node 918 in the DetNet flow 204. Fig. 9 Indicated by a single arrow and reference numeral 920 .

[0176] In this embodiment, the UE DetNet relay node 918 processes the DetNet flow packets according to the DetNet configuration information. Fig. 9 Indicated by reference numeral 922 in the figure.

[0177] In this embodiment, the UE DetNet relay node 918 sends a DetNet flow packet to the DetNet terminal system 302. The UE DetNet relay node 918 sends a DetNet flow packet to the DetNet terminal system 302. Fig. 9 Indicated by reference numeral 924 in the figure.

[0178] Fig.10 Another embodiment of an architecture 1000 is depicted in which DetNet flows 204 are supported via a DetNet-unaware 3GPP system.

[0179] In this alternative embodiment, UE 400 and UPF 114 are unaware of DetNet flow 204, but the 3GPP system is configured to route packets including another DetNet flow having QoS requirements similar to those of DetNet flow 204. UE 400 and UPF 114 may be considered as DetNet unaware relay nodes 1002.

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

[0181] To support architecture 1000, the following operations are required:

[0182] • The UE establishes a PDU session 612 according to 3GPP TS 23.502 v17.4.0. The UE 400 may request to establish another redundant PDU session.

[0183] The DetNet-aware AF 605 subscribes to be informed of the IP address of the UE 400 for the DetNet flow 204 .

[0184] • Discover the DetNet End System 302 located behind the Relay Node 306 (ie, behind the UE 400 and the UPF 114).

[0185] The DetNet-aware AF 605 receives the DetNet flow configuration information from the DetNet controller 606 .

[0186] · Map the DetNet flow configuration information obtained from the DetNet controller 606 to the 5GS QoS information (e.g., 5QI, TSC auxiliary information) of the QoS flow in the corresponding PDU session 612 of the DetNet flow 204. The DetNet-aware AF 605 maps the DetNet flow configuration information to the 5GS QoS information of the QoS flow in Fig.10 Indicated by a single arrow and reference numeral 614, and consistent with action 614 described above.

[0187] It should be understood that much of architecture 1000 corresponds to the above referenced Figure 6 For example, the DetNet-aware AF 605 receives configuration information in Fig.10 607, and is consistent with the above-described action 607. Where architecture 1000 includes entities or actions corresponding to entities or actions described in architecture 600, the same reference numerals should be understood to give the entities or actions the same or similar roles, unless otherwise specified.

[0188] When UE 400 establishes PDU session 612, this embodiment is similar to Figure 7 The difference between the process 700 described in FIG. 7 is that the UE 400 does not report any DetNet capabilities, and the SMF 610 reports the IP address of the UE 400 (corresponding to the IP address of the UE 400) to the DetNet-aware AF 605. Figure 7In the corresponding process of this embodiment, if the UE 400 and UPF 114 support DS-TT and NW-TT functions respectively, the UE 400 and UPE 114 can still report the residence time, in which case the residence time is forwarded to the DetNet-aware AF 605. This can be used by the DetNet controller 606 to determine the delay of the packet when traversing the 5GS and determine the appropriate QoS for the DetNet flow 204 traversing the 5GS.

[0189] The process of DetNet controller 606 configuring DetNet-aware AF 605 with QoS requirements is as shown in FIG. Figure 8 The process 800 is described in detail. Figure 8 As shown at action 810 , the DetNet-aware AF 605 determines the IP address of the UE 400 to initiate an AF session request with specific QoS requirements at action 812 .

[0190] In an embodiment, a wireless communication device for communicating with a wireless communication network is provided. In this embodiment, the wireless communication device is a UE 400, which is configured to perform the process described in the above embodiment and participate in the architecture described in the above embodiment.

[0191] The 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 including first information for establishing a user plane connection for the DetNet service (i.e., the DetNet flow 204). In this embodiment, the first information includes configuration information received by the DetNet controller 606, as described in the above embodiment.

[0192] The request may be used for establishing a user plane connection, such as the PDU session 612 established in the above embodiment. In this embodiment, the request to establish a user plane connection is completed according to actions 702 and 802 described in the above embodiment. By sending a request including first information for establishing a user plane connection for a deterministic network service, the wireless communication device is arranged to enable the deterministic network service to be carried on the wireless communication network. The first information may include at least one requirement.

[0193] In this embodiment, the first information may include DNN, S-NSSAI, or at least one of the two.

[0194] In this embodiment, the first information may include the DetNet capability of the wireless communication device, ie, the DetNet capability of the UE 400 provided to the PCF 608 in the process 700 at action 724 .

[0195] In this embodiment, the DetNet capability of the 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 transport node, or a combination thereof.

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

[0197] In this embodiment, the DetNet capability of the wireless communication device may include the capability of calculating the dwell time.

[0198] According to the above embodiment, the DetNet may be an IETF DetNet.

[0199] In an embodiment, a method 1100 performed by the wireless communication device of the above embodiment is provided. Fig.11 is a process flow diagram depicting method 1100, which includes, at step s1102, a transceiver of a wireless communication device (i.e., transceiver 425 of UE 400) issuing a request to a wireless communication network, the request including first information for establishing a user plane connection for a DetNet service (i.e., DetNet flow 204).

[0200] In an embodiment, an AF in a wireless communication network is provided. In this embodiment, the AF is consistent with the DetNet-aware AF 605 described in the above embodiment and is consistent with the above network node 500.

[0201] The AF includes a transceiver consistent with the transceiver 525, which is arranged to issue a subscription request to a first NF of the wireless communication network, the subscription request requesting notification of the network address of the device when the device (e.g., UE 400) establishes a user plane connection to support DetNet deterministic services. The first NF is consistent with the above-mentioned network node 500.

[0202] The transceiver is further arranged to receive first information from the first NF, the first information identifying the first device, and the first information identifying the second NF supporting the DetNet relay node function, ie the second NF is configured to execute as the DetNet relay node 306 described in the above embodiment.

[0203] The second NF corresponds to the network node 500 .

[0204] The transceiver is further arranged to receive a DetNet flow requirement from a DetNet controller consistent with the DetNet controller 606 described according to the above embodiments in response to receiving the first information.

[0205] In this embodiment, the AF further comprises a processor consistent with the processor 505, which is arranged to convert the DetNet flow requirements into QoS requirements for associating DetNet services through the wireless communication network. In this embodiment, the conversion of the DetNet flow requirements into QoS requirements is performed according to the mapping 614 of the DetNet flow configuration information obtained from the DetNet controller 606 to the 5GS QoS information as described in the above embodiment.

[0206] The transceiver is further arranged to issue a second request to the second NF to establish a user plane session with the wireless communication network according to the QoS requirements for associating the DetNet traffic over the wireless communication network.

[0207] Therefore, the AF of this embodiment is arranged to carry the DetNet service through the wireless communication network to implement the DetNet flow requirements for the DetNet service (for example, the DetNet configuration information described in the above embodiments).

[0208] The DetNet flow requirements may be QoS requirements from the DetNet. The QoS requirements for relaying DetNet services through the wireless communication network may be 3GPP QoS requirements.

[0209] The processor may be arranged to convert the DetNet flow requirements into QoS requirements for relaying the DetNet service over the wireless communication network based on information provided by the first device and / or the second NF. The information may include, for example, a dwell time.

[0210] The first NF may be a NEF, such as the one referenced above. Figure 8 NEF 808.

[0211] The second NF may be a UPF, such as the UPF 114 described in the above embodiment.

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

[0213] In an embodiment, a method 1200 performed by the AF of the above embodiment is provided. Fig.12 is a process flow diagram depicting method 1200. The method includes, at step s1202, issuing a subscription request to a first NF of a wireless communication network, the subscription request requesting notification of a network address of a device when the device establishes a user plane connection to support a DetNet deterministic service.

[0214] The method includes receiving first information from the first NF at step s1204, the first information identifying the first device, and the first information identifying the second NF supporting the DetNet relay node function, that is, the second NF is configured to execute the DetNet relay node 306 as described in the above embodiment. The second NF is consistent with the network node 500.

[0215] The method comprises, at step s1206 , receiving a DetNet flow requirement from a DetNet controller consistent with the DetNet controller 606 described in the above embodiment in response to receiving the first information.

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

[0217] The method includes, at step s1210, issuing to the second NF a second request to establish a user plane session with the wireless communication network according to the QoS requirement for relaying the DetNet service through the wireless communication network.

[0218] Therefore, a method 1200 is provided, which is used to arrange the AF to carry the DetNet service on the wireless communication network to achieve the DetNet flow requirements for the DetNet service (for example, the DetNet configuration information described in the above embodiments).

[0219] In an embodiment, a first NF in a wireless communication network is provided, the first NF comprising a transceiver, namely a transceiver 525, the transceiver 525 being arranged 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 to support a DetNet deterministic service. The first NF is consistent with the above-mentioned network node 500.

[0220] In this embodiment, the transceiver is arranged to send a first message to the AF, the first message identifies the first device, and the first message identifies a second NF supporting the DetNet relay node function, i.e., the second NF is configured to execute as the DetNet relay node 306 described in the above embodiment. The second NF is consistent with the network node 500.

[0221] The first NF may be a NEF, such as the one referenced above. Figure 8 NEF 808.

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

[0223] In an embodiment, a method 1300 performed by the first NF of the above embodiment is provided. Fig.13 is a process flow diagram depicting method 1300. The method comprises, at step s1302, receiving a subscription request from an AF of a wireless communication network, the subscription request requesting notification of a network address of a device when the device establishes a user plane connection to support a DetNet deterministic service. The first NF is consistent with the network node 500 described above.

[0224] The method includes sending first information to the AF at step s1304, the first information identifying the first device, and the first information identifying the second NF supporting the DetNet relay node function, that is, the second NF is configured to be executed by the DetNet relay node 306 as described in the above embodiment. The second NF is consistent with the network node 500.

[0225] In an embodiment, a UPF in a wireless communication network is provided, which is consistent with the UPF 114 described in the above embodiment and consistent with the network node 500. The UPF includes a transceiver, namely a transceiver 525, which is arranged to receive a request to establish a user plane session with the wireless communication network according to at least one QoS requirement for relaying DetNet services through the wireless communication network from an SMF consistent with the SMF 610 described in the above embodiment.

[0226] In this embodiment, the transceiver is further arranged to send a response to the SMF, the response indicating first information including the DetNet capability of the UPF. The first information may be sent in a container.

[0227] In an embodiment, a method 1400 performed by the UPF of the above embodiment is provided. Fig.14 is a process flow diagram depicting method 1400. The method comprises, at step s1402, receiving from an SMF consistent with SMF 610 described in the above embodiments a request to establish a user plane session with a wireless communication network in accordance with at least one QoS requirement for relaying DetNet traffic through the wireless communication network.

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

[0229] Therefore, a method 1400 is provided for arranging a UPF to carry DetNet services on a wireless communication network (ie, act as a DetNet relay node) to implement DetNet flow requirements of the DetNet services (eg, the DetNet configuration information described in the above embodiments).

[0230] Advantageously, the methods and apparatus described herein tend to integrate support for DetNet via 5GS using the IETF DetNet specification. The solution tends to allow a DetNet controller to discover nodes within a 3GPP system that are DetNet aware, and allows the controller to provide requirements so that the 3GPP network can establish a user plane connection with QoS requirements that meet the QoS standards of the DetNet flow.

[0231] Advantageously, the methods and apparatus described herein overcome existing problems such as how to identify and discover UEs that support establishing user plane connections for DetNet services and how to configure a 3GPP system (eg, an existing 3GPP system) to support user plane connections for DetNet services.

[0232] Although in some of the above embodiments, the 3GPP system is configured to support DetNet services is DetNet-aware (where DetNet-aware nodes (e.g., UE and UPF) act as relay nodes), in other arrangements, the 3GPP system is DetNet-unaware, but can advantageously support DetNet flows. In particular, in a DetNet-unaware 3GPP system, the network can advantageously be set up to route DetNet flows with specific QoS requirements, thereby meeting the IETF QoS requirements for DetNet flows.

[0233] It should be noted that the above methods and apparatus illustrate rather than limit the present invention, and that those skilled in the art will be able to design many alternative arrangements without departing from the scope of the appended claims. The word "comprising" does not exclude the presence of other elements or steps than those listed in the claims, "a" or "an" does not exclude a plurality, and a single processor or other unit may perform the functions of several units listed in the claims. Any reference signs in the claims should not be construed as limiting the scope thereof.

[0234] Furthermore, although examples have been 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 have been given in the context of 3GPP, the principles disclosed herein may also be applied to another wireless communication system, and indeed to any communication system that uses routing rules.

[0235] 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 similar device causes the processor to perform the above method.

[0236] The described methods and apparatus may be practiced in other specific forms. The described methods and apparatus are considered in all respects to be illustrative only and not restrictive. Therefore, the scope of the present invention is indicated by the appended claims rather than by the foregoing description. All changes within the meaning and equivalent range of the claims should be included within their scope.

Claims

1. A wireless communication device for communicating with a wireless communication network, the wireless communication device comprising: A transceiver is arranged to issue a request to the wireless communication network, the request comprising: first information for establishing a user plane connection for a deterministic network service.

2. The wireless communication device according to claim 1, wherein the first information comprises: Data network name, single network slice selection auxiliary information, or at least one of the two. 3 . The wireless communication device according to claim 1 , wherein the first information corresponds to a deterministic network (DetNet).

4. The wireless communication device according to claim 1, 2 or 3, wherein the first information comprises: The deterministic network capabilities of the wireless communication device.

5. The wireless communication device of claim 4, wherein the deterministic network capabilities of the wireless communication device define an ability of the wireless communication device to act as at least one of a relay node, an edge node, a transport node, or a combination thereof.

6. The wireless communication device of claim 4, wherein the deterministic network capabilities of the wireless communication device include: The wireless communication device supports the capabilities of a proximity discovery protocol and / or a deterministic network configuration protocol.

7. The wireless communication device of claim 4, wherein the deterministic network capabilities of the wireless communication device include: Ability to calculate dwell time.

8. The wireless communication device of any preceding claim, wherein the deterministic network is IETF DetNet.

9. A method in a wireless communication device, the wireless communication device being arranged to communicate with a wireless communication network, the method comprising: A request is sent to the wireless communication network, the request comprising: first information for establishing a user plane connection for a deterministic network service.

10. An application function in a wireless communication network, the application function comprising: A transceiver, the transceiver being arranged to: issuing a subscription request to a first network function of the wireless communication network, the subscription request requesting notification of the network address of the device when the device establishes a user plane connection to support a deterministic network deterministic service; receiving first information from the first network function, the first information identifying a first device, and the first information identifying a second network function supporting a deterministic network relay node function; receiving a deterministic network flow requirement from a deterministic network controller in response to receiving the first information; The application function further comprises a processor arranged to: convert a deterministic network flow requirement into a quality of service requirement for relaying deterministic network traffic over the wireless communication network; The transceiver is further arranged to issue 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 requirement for relaying deterministic network traffic over the wireless communication network.

11. An application function according to claim 10, wherein the processor is arranged to: convert the deterministic network flow requirement into a quality of service requirement for relaying deterministic network services through the wireless communication network based on information provided by the first device and / or the second network function.

12. The application function according to claim 10 or 11, wherein the first network function is a network opening function.

13. An application function according to claim 10, 11 or 12, wherein the second network function is a user plane function.

14. The application function according to any one of claims 10 to 13, wherein the deterministic network is IETFDetNet.

15. A method in an application function of a wireless communication network, the method comprising: issuing a subscription request to a first network function of the wireless communication network, the subscription request requesting notification of the network address of the device when the device establishes a user plane connection to support a deterministic network deterministic service; receiving first information from the first network function, the first information identifying a first device, and the first information identifying a second network function supporting a deterministic network relay node function; receiving a deterministic network flow requirement from a deterministic network controller in response to the first information; converting deterministic network flow requirements into quality of service requirements for relaying the deterministic network traffic over the wireless communication network; A second request is issued to the second network function to establish a user plane session with the wireless communication network in accordance with the quality of service requirement for relaying deterministic network traffic through the wireless communication network.

16. A first network function in a wireless communication network, the first network function comprising: A transceiver, the transceiver being arranged to: receiving a subscription request from an application function of the wireless communication network, the subscription request requesting notification of the network address of the device when the device establishes a user plane connection to support a deterministic network deterministic service; First information is sent to the application function, the first information identifying a first device, and the first information identifying a second network function supporting a deterministic network relay node function. The first network function according to claim 16 , wherein the first network function is a network open function.

18. The first network function according to claim 16 or 17, wherein the deterministic network is IETF DetNet.

19. A method in a first network function of a wireless communication network, the method comprising: receiving a subscription request from an application function of the wireless communication network, the subscription request requesting notification of the network address of the device when the device establishes a user plane connection to support a deterministic network deterministic service; First information is sent to the application function, the first information identifying a first device, and the first information identifying a second network function supporting a deterministic network relay node function.

20. A user plane function in a wireless communication network, the user plane function comprising: a transceiver arranged to: receive from a session management function a request 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 through the wireless communication network; The transceiver is further arranged to send a response to the session management function, the response indication comprising first information of the deterministic network capability of the user plane function.

21. A method in a user plane function of a wireless communication network, the method comprising: receiving, from a session management function, a request 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 through the wireless communication network; A response is sent to the session management function, the response indicating first information including the deterministic network capabilities of the user plane function.

Images