WO2024088593A1 - Prise en charge de l'orientation de trafic multi-accès dans un système de communication sans fil - Google Patents

Prise en charge de l'orientation de trafic multi-accès dans un système de communication sans fil Download PDF

Info

Publication number
WO2024088593A1
WO2024088593A1 PCT/EP2023/062179 EP2023062179W WO2024088593A1 WO 2024088593 A1 WO2024088593 A1 WO 2024088593A1 EP 2023062179 W EP2023062179 W EP 2023062179W WO 2024088593 A1 WO2024088593 A1 WO 2024088593A1
Authority
WO
WIPO (PCT)
Prior art keywords
traffic
user equipment
processor
steering
data flow
Prior art date
Application number
PCT/EP2023/062179
Other languages
English (en)
Inventor
Apostolis Salkintzis
Original Assignee
Lenovo (Singapore) Pte. Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo (Singapore) Pte. Ltd filed Critical Lenovo (Singapore) Pte. Ltd
Publication of WO2024088593A1 publication Critical patent/WO2024088593A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/12—Communication route or path selection, e.g. power-based or shortest path routing based on transmission quality or channel quality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals

Definitions

  • the subject matter disclosed herein relates generally to the field of implementing supporting multiaccess traffic steering in a wireless communication system.
  • This document defines a user equipment apparatus, a first apparatus in a wireless communication network, a second apparatus in a wireless communication network, a third apparatus in a wireless communication network, and methods in a user equipment, first apparatus, second apparatus and third apparatus.
  • Multiaccess (MA) data connections between a 5G capable user equipment (UE) and a 5G core (5GC) network are referred to in the third generation partnership project (3GPP) specifications as MA protocol data unit (PDU) sessions.
  • 3GPP third generation partnership project
  • Steering rules created by the 5GC network, specify how uplink (UL) and downlink (DL) traffic should be routed across multiple accesses of the MA PDU session.
  • the steering rules comprise access traffic steering, switching, splitting (ATSSS) rules, which specify how UL traffic should be routed by a UE.
  • the steering rules further comprise multiaccess rules (MAR), provisioned to a user plane function (UPF), which specify how DL traffic should be routed.
  • MAR multiaccess rules
  • UPF user plane function
  • the UL and DL traffic respectively is routed across the multiple accesses of the MA PDU session.
  • IP multimedia subsystem (IMS) voice and video traffic comprises voice, video telephony and multimedia communications over IP networks.
  • Internet traffic comprises Internet data traffic with wide availability but no critical requirements on latency or data rates.
  • On demand downlink streaming traffic comprises traffic characterized by downlink high data rates and low latency, delivered and consumed in a continuous manner from a source, with little or no intermediate storage in network elements.
  • Uplink streaming traffic comprises traffic characterized by uplink high data rates and low latency, sent in a continuous manner from a source, with little or no intermediate storage in network elements.
  • Vehicular communications traffic comprises traffic characterized by low latency, high reliability and high availability.
  • Real time interactive traffic comprises traffic characterized by bidirectional variable data rates as well as low latency requirements, for example gaming, augmented reality (AR) /virtual reality (VR).
  • AR augmented reality
  • VR virtual reality
  • Unified communications traffic comprises communications through a single service, for instance instant messaging, voice over IP (VoIP) and video collaboration through the same user interface.
  • VoIP voice over IP
  • Background traffic comprises traffic running in the background e.g., firmware/ software updates over the air, with no critical requirements from a latency or data rate perspective.
  • Location-based traffic comprises traffic requiring highly reliable user and control plane signaling.
  • Critical Communications traffic comprises traffic with low to very low latency requirements, variable data rates and high availability and prioritization.
  • the issue addressed in this disclosure is that a UE cannot consider the traffic category when deciding how to route IP flows across the multiple accesses of a MA PDU Session. This is because the specified ATSSS rules do not support a traffic category.
  • ATSSS rules that specify how to route data traffic depending on the traffic category of the data traffic.
  • ATSSS rules that route the data traffic belonging to a first traffic category differently from the data traffic belonging to a second traffic category.
  • PMF Performance Measurement Function
  • a user equipment apparatus for wireless communication comprising a processor; and a memory coupled with the processor, the processor configured to cause the user equipment apparatus to: receive a data flow for transmission over a multiaccess protocol data unit (MA PDU) session; determine at least a first traffic category of the data flow; determine at least a first steering rule that matches the at least a first traffic category; and determine, based on the at least a first steering rule, how uplink traffic of the data flow is to be routed over one or more accesses of the MA PDU session.
  • MA PDU multiaccess protocol data unit
  • a first apparatus in a wireless communication network comprising a processor and a memory coupled with the processor, the processor configured to cause the first apparatus to: generate a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session; and transmit, to a session management function (SMF) of the wireless communication network, the steering policy.
  • SMF session management function
  • a second apparatus in a wireless communication network comprising a processor and a memory coupled with the processor, the processor configured to cause the second apparatus to: receive a data flow for transmission over one or more accesses of a MA PDU session; determine at least a first traffic category of the data flow; determine at least a first steering rule that matches the at least a first traffic category; and determine, based on the at least a first steering rule, how downlink traffic of the data flow is to be routed over the one or more accesses of the MA PDU session.
  • a third apparatus in a wireless communication network comprising a processor and a memory coupled with the processor, the processor configured to cause the third apparatus to: receive, from a policy control function TCF’ of the wireless communication network, a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session; generate, based on the steering policy, at least a first ATSSS rule for a user equipment apparatus, and at least a first MAR rule for a UPF of the wireless communication network, the at least a first ATSSS rule and at least a first MAR rule indicating, respectively, how uplink and downlink traffic are to be routed over one or more accesses of the MA PDU session.
  • TCF policy control function
  • a method in a user equipment apparatus comprising: receiving a data flow for transmission over a MA PDU session; determining at least a first traffic category of the data flow; determining at least a first steering rule that matches the at least a first traffic category; and determining, based on the at least a first steering rule, how uplink traffic of the data flow is to be routed over one or more accesses of the MA PDU session.
  • a method in a first apparatus in a wireless communication network comprising: generating a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session; and transmitting, to a SMF of the wireless communication network, the steering policy.
  • a method in a second apparatus in a wireless communication network comprising: receiving a data flow for transmission over one or more accesses of a MA PDU session; determining at least a first traffic category of the data flow; determining at least a first steering rule that matches the at least a first traffic category; and determining, based on the at least a first steering rule, how downlink traffic of the data flow is to be routed over the one or more accesses of the MA PDU session.
  • a method in a third apparatus in a wireless communication network comprising: receiving, from a PCF of the wireless communication network, a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session; generating, based on the steering policy, at least a first ATSSS rule for a user equipment apparatus, and at least a first MAR rule for a UPF of the wireless communication network, the at least a first ATSSS rule and the at least a first MAR rule indicating, respectively, how uplink and downlink traffic are to be routed over one or more accesses of the MA PDU session.
  • Figure 1 illustrates an embodiment of a wireless communication system
  • Figure 2 illustrates an embodiment of a user equipment
  • Figure 3 illustrates an embodiment of a network node
  • Figure 4 illustrates an example scenario wherein a MA data connection is being established between a UE and a 5GC;
  • Figure 5 illustrates an embodiment of an architecture for establishing a MA data connection between a UE and a 5GC
  • Figure 6 illustrates an embodiment of a method in a user equipment apparatus
  • Figure 7 illustrates an embodiment of a method in a first apparatus
  • Figure 8 illustrates an embodiment of a method in a second apparatus
  • Figure 9 illustrates an embodiment of a method in a third apparatus.
  • Figure 10 illustrates an embodiment of a procedure for establishing an MA PDU session between a UE and a 5GC that supports traffic steering using traffic categories.
  • aspects of this disclosure may be embodied as a system, apparatus, method, or program product. Accordingly, arrangements described herein may be implemented in an entirely hardware form, an entirely software form (including firmware, resident software, micro-code, etc.) or a form combining software and hardware aspects.
  • the disclosed methods and apparatus may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components.
  • VLSI very-large-scale integration
  • 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, or the like.
  • the disclosed methods and apparatus may include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function.
  • the methods 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, referred hereafter as code.
  • the storage devices may be tangible, non-transitory, and/or non-transmission.
  • the storage devices may not embody signals. In certain arrangements, the storage devices only employ signals for accessing code.
  • the computer readable medium may be a computer readable storage medium.
  • the computer readable storage medium may be a storage device storing the code.
  • the storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
  • a storage device More specific examples (a non-exhaustive list) of the storage device 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 foregoing.
  • 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.
  • references throughout this specification to an example of a particular method or apparatus, or similar language means that a particular feature, structure, or characteristic described in connection with that example is included in at least one implementation of the method and apparatus described herein.
  • reference to features of an example of a particular method or apparatus, or similar language may, but do not necessarily, all refer to the same example, but mean “one or more but not all examples” unless expressly specified otherwise.
  • the terms “a”, “an”, and “the” also refer to “one or more”, unless expressly specified otherwise.
  • a list with a conjunction of “and/ or” includes any single item in the list or a combination of items in the list.
  • 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.
  • a list using the terminology “one or more of’ includes any single item in the list or a combination of items in the list.
  • 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.
  • a list using the terminology “one of’ includes one, and only one, of any single item in the list.
  • “one of A, B and C” includes only A, only B or only C and excludes combinations of A, B and C.
  • a member selected from the group consisting of A, B, and C includes one and only one of A, B, or C, and excludes combinations of A, B, and C.”
  • “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.
  • the code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/ act specified in the schematic flowchart diagrams and/or schematic block diagrams.
  • the code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other devices to produce a computer implemented process such that the code which executes on the computer or other programmable apparatus provides processes for implementing the functions /acts specified in the schematic flowchart diagrams and/or schematic block diagram.
  • each block in the schematic flowchart diagrams and/ or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).
  • the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.
  • FIG. 1 depicts an embodiment of a wireless communication system 100 for supporting multiaccess traffic steering in a wireless communication system.
  • the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.
  • the wireless communication system may comprise a wireless communication network and at least one wireless communication device.
  • the wireless communication device is typically a 3GPP User Equipment (UE).
  • the wireless communication network may comprise at least one network node.
  • the network node may be a network unit.
  • the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle onboard computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like.
  • the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like.
  • the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art.
  • the remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.
  • the network units 104 may be distributed over a geographic region.
  • a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an Access and Mobility Management Function (“AMF”), a Unified Data Management Function (“UDM”), a Unified Data Repository (“UDR”), a UDM/UDR, a Policy Control Function (“PCF”), a Radio Access Network (“RAN”), an Network Slice Selection Function (“NSSF”), an operations, administration, and management (“OAM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non-3GPP gateway function (“TNGF”), an
  • AMF Access and
  • the network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104.
  • the radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.
  • the wireless communication system 100 is compliant with New Radio (NR) protocols standardized in 3GPP, wherein the network unit 104 transmits using an Orthogonal Frequency Division Multiplexing (“OFDM”) modulation scheme on the downlink (DL) and the remote units 102 transmit on the uplink (UL) using a Single Carrier Frequency Division Multiple Access (“SC-FDMA”) scheme or an OFDM scheme.
  • OFDM Orthogonal Frequency Division Multiplexing
  • SC-FDMA Single Carrier Frequency Division Multiple Access
  • the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, LTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfox, LoraWAN among other protocols.
  • WiMAX WiMAX
  • IEEE 802.11 variants GSM
  • GPRS Global System for Mobile communications
  • UMTS Long Term Evolution
  • LTE Long Term Evolution
  • CDMA2000 Code Division Multiple Access 2000
  • the network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link.
  • the network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/ or spatial domain.
  • Figure 2 depicts a user equipment apparatus 200 that may be used for implementing the methods described herein.
  • the user equipment apparatus 200 is used to implement one or more of the solutions described herein.
  • the user equipment apparatus 200 is in accordance with one or more of the user equipment apparatuses described in embodiments herein.
  • the user equipment apparatus 200 may comprise the remote unit 505 of Figure 5, or a UE performing the method of Figure 6, or a UE 1020 of Figure 10.
  • the user equipment apparatus 200 includes a processor 205, a memory 210, an input device 215, an output device 220, and a transceiver 225.
  • the input device 215 and the output device 220 may be combined into a single device, such as a touchscreen.
  • the user equipment apparatus 200 does not include any input device 215 and/ or output device 220.
  • the user equipment apparatus 200 may include one or more of: the processor 205, the memory 210, and the transceiver 225, and may not include the input device 215 and/ or the output device 220.
  • the transceiver 225 includes at least one transmitter 230 and at least one receiver 235.
  • the transceiver 225 may communicate with one or more cells (or wireless coverage areas) supported by one or more base units.
  • the transceiver 225 may be operable on unlicensed spectrum.
  • the transceiver 225 may include multiple UE panels supporting one or more beams.
  • the transceiver 225 may support at least one network interface 240 and/ or application interface 245.
  • the application interface(s) 245 may support one or more APIs.
  • the network interface(s) 240 may support 3GPP reference points, such as Uu, Nl, PC5, etc. Other network interfaces 240 may be supported, as understood by one of ordinary skill in the art.
  • the processor 205 may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 205 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 similar programmable controller.
  • the processor 205 may execute instructions stored in the memory 210 to perform the methods and routines described herein.
  • the processor 205 is communicatively coupled to the memory 210, the input device 215, the output device 220, and the transceiver 225.
  • the processor 205 may control the user equipment apparatus 200 to implement the user equipment apparatus behaviors described herein.
  • the processor 205 may include an application processor (also known as “main processor”) which manages application-domain and operating system (“OS”) functions and a baseband processor (also known as “baseband radio processor”) which manages radio functions.
  • the memory 210 may be a computer readable storage medium.
  • the memory 210 may include volatile computer storage media.
  • the memory 210 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”).
  • the memory 210 may include non-volatile computer storage media.
  • the memory 210 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 210 may include both volatile and non-volatile computer storage media.
  • the memory 210 may store data related to implement a traffic category field as described herein.
  • the memory 210 may also store program code and related data, such as an operating system or other controller algorithms operating on the apparatus 200.
  • the input device 215 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 215 may be integrated with the output device 220, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 215 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen.
  • the input device 215 may include two or more different devices, such as a keyboard and a touch panel.
  • the output device 220 may be designed to output visual, audible, and/ or haptic signals.
  • the output device 220 may include an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 220 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, or the like to a user.
  • LCD Liquid Crystal Display
  • LED Light- Emitting Diode
  • OLED Organic LED
  • the output device 220 may include a wearable display separate from, but communicatively coupled to, the rest of the user equipment apparatus 200, such as a smartwatch, smart glasses, a heads-up display, or the like. Further, the output device 220 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 220 may include one or more speakers for producing sound.
  • the output device 220 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 220 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 220 may be integrated with the input device 215.
  • the input device 215 and output device 220 may form a touchscreen or similar touch-sensitive display.
  • the output device 220 may be located near the input device 215.
  • the transceiver 225 communicates with one or more network functions of a mobile communication network via one or more access networks.
  • the transceiver 225 operates under the control of the processor 205 to transmit messages, data, and other signals and also to receive messages, data, and other signals.
  • the processor 205 may selectively activate the transceiver 225 (or portions thereof) at particular times in order to send and receive messages.
  • the transceiver 225 includes at least one transmitter 230 and at least one receiver 235.
  • the one or more transmitters 230 may be used to provide uplink communication signals to a base unit of a wireless communication network.
  • the one or more receivers 235 may be used to receive downlink communication signals from the base unit.
  • the user equipment apparatus 200 may have any suitable number of transmitters 230 and receivers 235.
  • the transmitter(s) 230 and the receiver(s) 235 may be any suitable type of transmitters and receivers.
  • the transceiver 225 may include a first transmitter/receiver pair used to communicate with a mobile communication network over licensed radio spectrum and a second transmitter/ receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum.
  • the first transmitter/ receiver pair may be used to communicate with a mobile communication network over licensed radio spectrum and the second transmitter/receiver pair used to communicate with a mobile communication network over unlicensed radio spectrum may be combined into a single transceiver unit, for example a single chip performing functions for use with both licensed and unlicensed radio spectrum.
  • the first transmitter/receiver pair and the second transmitter/receiver pair may share one or more hardware components.
  • certain transceivers 225, transmitters 230, and receivers 235 may be implemented as physically separate components that access a shared hardware resource and/or software resource, such as for example, the network interface 240.
  • One or more transmitters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a single hardware component, such as a multitransceiver chip, a system-on-a-chip, an Application-Specific Integrated Circuit (“ASIC”), or other type of hardware component.
  • One or more transmitters 230 and/ or one or more receivers 235 may be implemented and/ or integrated into a multi-chip module.
  • Other components such as the network interface 240 or other hardware components/ circuits may be integrated with any number of transmitters 230 and/ or receivers 235 into a single chip.
  • the transmitters 230 and receivers 235 may be logically configured as a transceiver 225 that uses one more common control signals or as modular transmitters 230 and receivers 235 implemented in the same hardware chip or in a multi-chip module.
  • FIG. 3 depicts further details of the network node 300 that may be used for implementing the methods described herein.
  • the network node 300 may be one implementation of an entity in the wireless communication network, e.g. in one or more of the wireless communication networks described herein.
  • the network node 300 may comprise a UPF 541, SMF 545, or PCF 547 of Figure 5, or a network node/ entity performing the methods of either of Figure 7, Figure 8 or Figure 9, or may comprise a SMF 1050, a PCF 1060 or a UPF 1070 of Figure 10.
  • the network node 300 includes a processor 305, a memory 310, an input device 315, an output device 320, and a transceiver 325.
  • the input device 315 and the output device 320 may be combined into a single device, such as a touchscreen.
  • the network node 300 does not include any input device 315 and/ or output device 320.
  • the network node 300 may include one or more of: the processor 305, the memory 310, and the transceiver 325, and may not include the input device 315 and/ or the output device 320.
  • the transceiver 325 includes at least one transmitter 330 and at least one receiver 335.
  • the transceiver 325 communicates with one or more remote units 200.
  • the transceiver 325 may support at least one network interface 340 and/or application interface 345.
  • the application interface(s) 345 may support one or more APIs.
  • the network interface(s) 340 may support 3GPP reference points, such as Uu, Nl, N2 and N3. Other network interfaces 340 may be supported, as understood by one of ordinary skill in the art.
  • the processor 305 may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations.
  • the processor 305 may be a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or similar programmable controller.
  • the processor 305 may execute instructions stored in the memory 310 to perform the methods and routines described herein.
  • the processor 305 is communicatively coupled to the memory 310, the input device 315, the output device 320, and the transceiver 325.
  • the memory 310 may be a computer readable storage medium.
  • the memory 310 may include volatile computer storage media.
  • the memory 310 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/ or static RAM (“SRAM”).
  • the memory 310 may include non-volatile computer storage media.
  • the memory 310 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device.
  • the memory 310 may include both volatile and non-volatile computer storage media.
  • the memory 310 may store data related to establishing a multipath unicast link and/ or mobile operation.
  • the memory 310 may store parameters, configurations, resource assignments, policies, and the like, as described herein.
  • the memory 310 may also store program code and related data, such as an operating system or other controller algorithms operating on the network node 300.
  • the input device 315 may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like.
  • the input device 315 may be integrated with the output device 320, for example, as a touchscreen or similar touch-sensitive display.
  • the input device 315 may include a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/ or by handwriting on the touchscreen.
  • the input device 315 may include two or more different devices, such as a keyboard and a touch panel.
  • the output device 320 may be designed to output visual, audible, and/ or haptic signals.
  • the output device 320 may include an electronically controllable display or display device capable of outputting visual data to a user.
  • the output device 320 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user.
  • the output device 320 may include a wearable display separate from, but communicatively coupled to, the rest of the network node 300, such as a smart watch, smart glasses, a heads-up display, or the like.
  • the output device 320 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.
  • the output device 320 may include one or more speakers for producing sound.
  • the output device 320 may produce an audible alert or notification (e.g., a beep or chime).
  • the output device 320 may include one or more haptic devices for producing vibrations, motion, or other haptic feedback. All, or portions, of the output device 320 may be integrated with the input device 315.
  • the input device 315 and output device 320 may form a touchscreen or similar touch-sensitive display.
  • the output device 320 may be located near the input device 315.
  • the transceiver 325 includes at least one transmitter 330 and at least one receiver 335.
  • the one or more transmitters 330 may be used to communicate with the UE, as described herein.
  • the one or more receivers 335 may be used to communicate with network functions in the PLMN and/ or RAN, as described herein.
  • the network node 300 may have any suitable number of transmitters 330 and receivers 335.
  • the transmitter(s) 330 and the receiver(s) 335 may be any suitable type of transmitters and receivers.
  • FIG. 4 illustrates an example scenario 400 wherein a MA data connection is being established between a UE and a 5GC.
  • the scenario 400 shows a UE 410, a 5G- RAN 420 and a 5GC 430 and the various steps 401-406 of the MA data connection establishment procedure.
  • a first step 401 the UE 410 decides to request a MA PDU session using multiple accesses.
  • the UE 410 sends a MA PDU Session Establishment Request message to 5GC 430 via 5G-RAN 420.
  • This is illustrated as, 2VL4 PDU Session Est. Request, PDU Session ID, [S -NS SAI], [DNN], [PDU type], [SSC mode], 5 GSM capability (ATSSS capabilities) ’.
  • the 5GC 430 processes the message and creates steering rules that specify how the UL and DL traffic should be routed across the multiple accesses of the MA PDU Session. This is illustrated as, ‘Create steering rules (ATSSS rules, MAR rules) that determine how UE/ DE data traffic should be routed across the multiple accesses. Steering rules are created based on network poliyt and UE subscription information ’.
  • a MA PDU Session Establishment Accept message is sent by 5GC 430 to UE 410 via 5G-RAN 420.
  • This message includes ATSSS rules, which specify how the UL traffic should be routed across the multiple accesses. This is illustrated as, ‘NLA PDU Session Est. Accept, PDU Session ID, PDU type, SSC Mode, ATSSS container (ATSSS rules, etc)’.
  • Similar MAR rules are provided to a UPF in 5GC 430, which specify how the DL traffic should be routed across the multiple accesses.
  • step 405a the UE 410 routes UL data traffic across the multiple accesses based on the created ATSSS rules.
  • step 405b the 5GC 430 routes DL data traffic across the multiple accesses based on the created MAR rules.
  • the ATSSS rules in the UE 410 and the MAR rules in the UPF of 5GC 530 the UL and the DL traffic respectively is routed across the multiple accesses of the MA PDU Session.
  • the procedure illustrated in Figure 4 has a first issue.
  • the created ATSSS and MAR rules cannot indicate how the traffic belonging to a specific traffic category should be routed across the multiple accesses.
  • Such an issue manifests itself further in step 406, wherein UE 410 receives an IP flow to be transmitted over the MA PDU session, wherein the IP flow belongs to a first traffic category.
  • a traffic category may be any of the traffic categories mentioned hereinbefore.
  • the UE 410 cannot, in the scenario 400 of Figure 4, take into account the first traffic category when deciding how to route the IP flow across the multiple accesses.
  • FIG. 5 illustrates an embodiment 500 of an architecture for establishing a MA data connection between a UE and a 5GC.
  • the figure illustrates a remote unit 505 (UE) connected to a 5G core (5GC) network 540 via two types of access networks: (a) a 3GPP access network 520 and (b) a non-3GPP access network 530.
  • the first type of access 520 uses a 3GPP-defmed type of wireless communication (e.g., NG-RAN), while the second type of access 530 uses a non-3GPP-defmed type of wireless communication (e.g., WEAN/WiFi).
  • the 5G-RAN illustrated as 515 refers to any type of 5G access network that can provide access to 5GC 540, including the 3GPP access network 520 and the non-3GPP access network 530.
  • the 3GPP access network 520 is illustrated as comprising a cellular base unit 521.
  • the non-3GPP access network 530 is illustrated as comprising an access point 531.
  • the remote unit 505 can establish a multiaccess data connection 548 with a UPF 541 in 5GC 540, which can support data communication using multiple access types, such as the first access type 520 (e.g., NG-RAN) and the second access type 530 (e.g., WiFi access).
  • the multiaccess data connection 548 is also known as multiaccess PDU Session and supports two user-plane connections: one user-plane connection using communication over 3GPP access 525 and another user-plane connection using communication over non-3GPP access 535.
  • the user-plane connection using communication over non-3GPP access 535 utilises an interworking function 536.
  • a MA PDU Session may have two or more user-plane connections, each one using communication over a different type of access network.
  • the 5GC network 540 further comprises an AMF 543, an SMF 545, a PCF 547 and a UDM 549.
  • the PCF 547 creates session management policy rules (or PCC rules) for the MA PDU session, which are delivered to the SMF 545 that creates steering rules 508 for the Uplink (UL) traffic and steering rules 509 for the Downlink (DL) traffic, which are forwarded to the remote unit 505 and to UPF 541, respectively.
  • the steering rules 508 for the Uplink (UL) traffic are called ATSSS rules, and the steering rules 509 for the Downlink (DL) traffic are called multiaccess rules (MAR).
  • MAR multiaccess rules
  • the steering rules 508, 509 specify how the UL traffic and how the DL traffic of the MA PDU Session is to be routed across the two user-plane connections, or across the two types of accesses.
  • the remote unit 505 may use the MA PDU Session 548 to communicate with a Remote Host 555, connectable via a Data Network 550.
  • the disclosure herein provides a user equipment apparatus for wireless communication, comprising a processor; and a memory coupled with the processor, the processor configured to cause the user equipment apparatus to: receive a data flow for transmission over a MA PDU session; determine at least a first traffic category of the data flow; determine at least a first steering rule that matches the at least a first traffic category; and determine, based on the at least a first steering rule, how uplink traffic of the data flow is to be routed over one or more accesses of the MA PDU session.
  • the user equipment apparatus may receive a request to establish a data connection, and, based on provisioned URSP rules, determine to establish the MA PDU session.
  • the one or more accesses comprises 3GPP and non- 3GPP accesses.
  • the at least a first steering rule comprises at least a first access traffic steering switching and splitting ‘ATSSS’ rule.
  • the at least a first traffic category is provided in at least a first traffic descriptor of the at least a first ATSSS rule.
  • an ATSSS rule may indicate that all traffic belonging to the “real time interactive” traffic category should be routed with an active standby steering mode, where the active access is a 3GPP access.
  • an ATSSS rule may match all traffic generated by a UE application which belongs to “background” traffic category.
  • the processor is further configured to cause the user equipment apparatus to: transmit, to a core network of a wireless communication network, a MA PDU session establishment request, wherein the MA PDU session establishment request comprises one or more ATSSS capabilities of the user equipment apparatus, the one or more ATSSS capabilities indicating that the user equipment apparatus can support traffic steering based on traffic categories.
  • the core network is a 5G core network.
  • the processor is configured to transmit the MA PDU session establishment request to a session management function ‘SMF’, via an access management function ‘AMF’.
  • the establishment request may be received by AMF, forwarded to SMF, which then forwards the ATSSS capabilities to a PCF in a SM policy control create message.
  • the processor is further configured to cause the user equipment apparatus to: receive, from the core network, a MA PDU session establishment accept response, wherein the MA PDU session establishment accept response comprises the at least a first ATSSS rule.
  • the processor is further configured to cause the user equipment apparatus to: transmit assistance information to a user plane function ‘UPF’ of the core network, wherein the assistance information comprises one or more parameters for determining (i.e. assisting the UPF to determine) a routing of downlink traffic of the data flow that is in accordance with the routing of the uplink traffic of the data flow.
  • the assistance information comprises one or more parameters for determining (i.e. assisting the UPF to determine) a routing of downlink traffic of the data flow that is in accordance with the routing of the uplink traffic of the data flow.
  • the processor is configured to cause the user equipment apparatus to transmit the assistance information to the UPF within a performance measurement function ‘PMF’ message.
  • MAR rules may not themselves contain traffic categories of data/IP flows transmitted in the DL direction.
  • the UE may send the information to UPF to assist. This may be sent as a first performance measurement function message, after the UE determines how to route UL traffic.
  • the UPF uses this information to determine how to route DL traffic of the IP flow.
  • the data flow is an internet protocol ‘IP’ data flow.
  • IP internet protocol
  • the IP flow may be received from an application internal to the UE.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IP multimedia subsystem voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on-demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • Figure 6 illustrates an embodiment of a method 600 in a user equipment apparatus.
  • a first step 610 comprises receiving a data flow for transmission over a multiaccess protocol data unit ‘MA PDU’ session.
  • a further step 620 comprises determining at least a first traffic category of the data flow.
  • a further step 630 comprises determining at least a first steering rule that matches the at least a first traffic category.
  • a further step 640 comprises determining, based on the at least a first steering rule, how uplink traffic of the data flow is to be routed over one or more accesses of the MA PDU session.
  • the method 600 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the at least a first steering rule comprises at least a first access traffic steering switching and splitting ‘ATSSS’ rule.
  • the at least a first traffic category is provided in at least a first traffic descriptor of the at least a first ATSSS rule.
  • Some embodiments further comprise: transmitting, to a core network of a wireless communication network, a MA PDU session establishment request, wherein the MA PDU session establishment request comprises one or more ATSSS capabilities of the user equipment apparatus, the one or more ATSSS capabilities indicating that the user equipment apparatus can support traffic steering based on traffic categories.
  • the transmitting comprises transmitting the MA PDU session establishment request to a session management function ‘SMF’, via an access management function.
  • SMF session management function
  • Some embodiments further comprise receiving, from the core network, a MA PDU session establishment accept response, wherein the MA PDU session establishment accept response comprises the at least a first ATSSS rule.
  • Some embodiments further comprise transmitting assistance information to a user plane function ‘UPF’ of the core network, wherein the assistance information comprises one or more parameters for determining (i.e. assisting the UPF to determine) a routing of downlink traffic of the data flow that is in accordance with the routing of the uplink traffic of the data flow.
  • the assistance information comprises one or more parameters for determining (i.e. assisting the UPF to determine) a routing of downlink traffic of the data flow that is in accordance with the routing of the uplink traffic of the data flow.
  • the data flow is an internet protocol ‘IP’ data flow.
  • IP internet protocol
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IP multimedia subsystem voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on-demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • the disclosure herein further provides a first apparatus in a wireless communication network, comprising a processor and a memory coupled with the processor, the processor configured to cause the first apparatus to: generate a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session; and transmit, to a SMF of the wireless communication network, the steering policy.
  • the steering policy is contained in the multiaccess component of PCC policy.
  • a PCC policy rules containing a multiaccess component is called ‘multiaccess PCC rule’.
  • the multiaccess PCC policy may indicate that all traffic belonging to a first traffic category should be routed over the access that has smallest delay.
  • the policy may indicate that traffic belonging to a second category should be routed over WiFi access only.
  • the processor is further configured to cause the first apparatus to: receive, from the SMF, one or more ATSSS capabilities of a user equipment apparatus, the one or more ATSSS capabilities indicating the user equipment apparatus can support traffic steering based on traffic categories; and generate the steering policy, based at least partly on the one or more ATSSS capabilities.
  • the first apparatus comprises a PCF.
  • the steering policy may be sent in a PCC response message to the SMF.
  • the data flow is an internet protocol ‘IP’ data flow.
  • IP internet protocol
  • the data/IP flow is received from an application internal to a UE.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IMS voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on- demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • Figure 7 illustrates an embodiment of a method 700 in a first apparatus.
  • a first step 710 comprises generating a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session.
  • a further step 720 comprises transmitting, to a SMF of the wireless communication network, the steering policy.
  • the method 700 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • Some embodiments further comprise: receiving, from the SMF, one or more ATSSS capabilities of a user equipment apparatus, the one or more ATSSS capabilities indicating the user equipment apparatus can support traffic steering based on traffic categories; and generating the steering policy, based at least partly on the one or more ATSSS capabilities.
  • the method is performed by a PCF.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IMS voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on- demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • the disclosure herein further provides a second apparatus in a wireless communication network, comprising a processor and a memory coupled with the processor, the processor configured to cause the second apparatus to: receive a data flow for transmission over one or more accesses of a MA PDU session; determine at least a first traffic category of the data flow; determine at least a first steering rule that matches the at least a first traffic category; and determine, based on the at least a first steering rule, how downlink traffic of the data flow is to be routed over the one or more accesses of the MA PDU session.
  • the at least a first steering rule comprises at least a first multiaccess rule MAR’.
  • the processor is further configured to cause the second apparatus to: receive assistance information from a user equipment apparatus, wherein the assistance information comprises one or more parameters for determining (i.e. assisting the second apparatus to determine) the routing of downlink traffic of the data flow in accordance with a routing of uplink traffic of the data flow.
  • the processor is further configured to receive the assistance information in a PMF message.
  • the second apparatus comprises a user plane function ‘UPF’.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IMS voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on- demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • Figure 8 illustrates an embodiment of an method 800 in a second apparatus.
  • a first step 810 comprises, receiving a data flow for transmission over one or more accesses of a MA PDU session.
  • a second step 820 comprises, determining at least a first traffic category of the data flow.
  • a third step 830 comprises, determining at least a first steering rule that matches the at least a first traffic category.
  • a fourth step 840 comprises, determining, based on the at least a first steering rule, how downlink traffic of the data flow is to be routed over the one or more accesses of the MA PDU session.
  • the method 800 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • the at least a first steering rule comprises at least a first multiaccess rule ‘MAR’.
  • Some embodiments further comprise: receiving assistance information from a user equipment apparatus, wherein the assistance information comprises one or more parameters for determining (i.e. assisting the determining) of the routing of downlink traffic of the data flow in accordance with a routing of uplink traffic of the data flow.
  • Some embodiments comprise receiving the assistance information in a PMF message.
  • the method is performed by a user plane function ‘UPF’.
  • the data flow is an internet protocol ‘IP’ data flow.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IMS voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on- demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • the disclosure herein further provides a third apparatus in a wireless communication network, comprising a processor and a memory coupled with the processor, the processor configured to cause the third apparatus to: receive, from a PCF of the wireless communication network, a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session; and generate, based on the steering policy, at least a first ATSSS rule for a user equipment apparatus, and at least a first MAR rule for a UPF of the wireless communication network, the at least a first ATSSS rule and at least a first MAR rule indicating, respectively, how uplink and downlink traffic are to be routed over one or more accesses of the MA PDU session.
  • the processor is further configured to cause the third apparatus to transmit, to the user equipment apparatus and UPF, the respective at least a first ATSSS rule and at least a first MAR rule.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IMS voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on- demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • the third apparatus is a SMF.
  • Figure 9 illustrates an embodiment of a method 900 in a third apparatus.
  • a first step 910 comprises, receiving, from a PCF of the wireless communication network, a steering policy for a data flow of a MA PDU session, wherein the steering policy determines how uplink traffic and downlink traffic of the data flow, belonging to at least a first traffic category, should be routed across one or more accesses of the MA PDU session.
  • a further step 920 comprises, generating, based on the steering policy, at least a first ATSSS rule for a user equipment apparatus, and at least a first MAR rule for a UPF of the wireless communication network, the at least a first ATSSS rule and MAR rule indicating, respectively, how uplink and downlink traffic are to be routed over one or more accesses of the MA PDU session.
  • the method 900 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.
  • Some embodiments further comprise, transmitting, to the user equipment apparatus and UPF, the respective at least a first ATSSS rule and at least a first MAR rule.
  • the at least a first traffic category comprises one or more traffic categories selected from the list of traffic categories consisting of: IMS voice and video traffic; internet traffic; internet of things and/ or machine to machine traffic; on- demand downlink streaming traffic; on-demand uplink streaming traffic; vehicular communications traffic; real-time interactive traffic; unified communications traffic; background traffic; location-based traffic; and critical communications traffic.
  • the third apparatus is a SMF.
  • FIG. 10 illustrates an embodiment of a procedure 1000 for establishing an MA PDU session between a UE and a 5GC that supports traffic steering using traffic categories.
  • the figure shows a UE 1020, a 5G-RAN 1030, an application management function (AMF) 1040, a session management function (SMF) 1050, a policy control function (PCF) 1060 and a user plane function (UPF) 1070.
  • AMF application management function
  • SMF session management function
  • PCF policy control function
  • UPF user plane function
  • a first step 1001 the UE 1020 decides to establish a MA PDU Session. This decision is based on known procedures executed in the UE 1020. For example, the UE 1020 may receive (from an internal application or other component) a request to establish a data connection and, based on the provisioned UE route selection policy (URSP) rules, the UE 1020 decides to establish a MA PDU Session. This is illustrated as, ‘Decide to request a MA PDU session using multiple accesses’.
  • URSP UE route selection policy
  • the UE 1020 sends a MA PDU Session Establishment Request message, which contains the ATSSS Capabilities of the UE 1020 and other parameters known in the prior art (see e.g., 3GPP technical specifications TS 23.502 and TS 24.502).
  • the ATSSS Capabilities of the UE 1020 indicate also that the UE 1020 can support traffic steering (or ATSSS procedures) based on Traffic Categories.
  • the ATSSS Capabilities indicate that the UE 1020 is capable of routing data traffic across the multiple accesses of the MA PDU Session based on the Traffic Category of the data traffic.
  • data traffic belonging to a fist traffic category could be routed over a 3GPP access, whereas data traffic belonging to a second traffic category could be routed over a non-3GPP access or over both accesses.
  • This is illustrated as, ‘MA PDU Session Est. Request, PDU Session ID, [S-NSSAI], [DNN], [PDU type], [S SC Mode], 5 GSM capability (ATSSS capabilities)’.
  • the MA PDU Session Establishment Request message which contains the extended ATSSS Capabilities, is received via 5G-RAN 1030 by an AMF 1040 in 5GC and is forwarded to an SMF 1050 (as already specified).
  • the SMF 1050 forwards the ATSSS Capabilities to a PCF 1060 within a SM Policy Control Create Request message.
  • the PCF 1060 creates the session management policy rules (or PCC rules) for the MA PDU Session, which contain also multiaccess steering policy (or multiaccess PCC policy) indicating how the traffic over the MA PDU Session should be routed across the multiple accesses of the MA PDU Session. If the received ATSSS capabilities indicate that the UE 1020 can support traffic steering based on Traffic Categories, the PCF 1060 may create a multiaccess PCC policy that determines how data traffic belonging to different traffic categories should be routed across the multiple accesses. This is illustrated as, fUE capable of supporting traffic steering based on traffic categories, create multiaccess PCC policy that determines how data traffic belonging to different traffic categories should be routed across the multiple accesses’.
  • the multiaccess PCC policy created by PCF 1060 may indicate that all traffic belonging to a first traffic category (e.g., all real time interactive traffic), should be routed over the access that has the smallest delay. Furthermore, the multiaccess PCC policy may indicate that all traffic belonging to a second traffic category (e.g., all background traffic), should be routed over WiFi access only.
  • a first traffic category e.g., all real time interactive traffic
  • a second traffic category e.g., all background traffic
  • the PCF 1060 sends a SM Policy Control Create Response message to SMF 1050, which includes the created PCC policy, including the multiaccess PCC policy.
  • the SMF 1050 receives the multiaccess PCC policy and in a further step 1006 uses this policy to create (a) ATSSS rules for the UE 1020 and (b) Multi Access Routing (MAR) rules for the UPF 1070, which indicate how the uplink and the downlink traffic, respectively, is to be routed over the multiple accesses of the MA PDU Session.
  • This is illustrated as, ‘Use the multiaccess PCC policy to create steering rules for the UE (ATSSS rules) and steering rules for the UPF (MAR rules)
  • the SMF 1050 selects a UPF 1070 and establishes an N4 session (aka PFCP session) with the selected UPF 1070. During the establishment of this session, the SMF 1050 provides the created MAR rules to the selected UPF 1070. This is illustrated as, Nd Session E st. Reguest’ nd, Nd Session Est.Reponse’.
  • the SMF 1050 sends a MA PDU Session Establishment Accept message to UE 1020, which includes the created ATSSS rules. This is illustrated as, A PDU Session Est.Accept, PDU Session ID, PDU type, SSC mode, ATSSS container (ATSSS rules, etc)’. This concludes the establishment of the MA PDU Session.
  • the ATSSS rules are therefore enhanced to contain also a traffic category element in the traffic descriptor component.
  • an ATSSS rule comprising a traffic category is shown below, which indicates that all traffic that belongs to the “real time interactive” traffic category should be routed with an Active-Standby steering mode, where the active access is the 3GPP access. Also, the ATSSS-LL steering functionality should be applied for this traffic:
  • Traffic Category Teal time interactive traffic
  • Steering Mode Active-Standby; Motive access— 3 GPP Steering Tunctionality — /ITSSS-1.1..
  • the above ATSSS rule matches all traffic generated by the UE 1020, which belongs to the “real time interactive” traffic category.
  • the UE 1020 can determine the traffic category associated with some data traffic (e.g., with an IP flow) based on implementation means. In some cases, the application which creates the data traffic can also indicate traffic category of this traffic.
  • the traffic descriptor of the ATSSS rule may also include other components such as an Application Identity (Id), as shown below.
  • Id Application Identity
  • An ATSSS rule having this traffic descriptor matches all traffic generated by the UE 1020 application “com.example.app”, which belongs to the “background” traffic category.
  • Application Id com.example.app Traffic Category — background traffic.
  • Traffic Descriptor The new component in the Traffic Descriptor specified above is named “Traffic Category”. Alternatively, however, it could be named “Connection Capability”.
  • step 1010a the UE 1020 routes UL data traffic across the multiple accesses of the MA PDU Session based on the received ATSSS rules. Furthermore, in step lOlObthe UPF 1070 routes DL data traffic across the multiple accesses of the MA PDU Session based on the received MAR rules.
  • a further step 1011 when the UE 1020 receives an IP flow (e.g., from an internal application) to be transmitted over the MA PDU Session and the UE 1020 determines that this IP flow belongs to a first traffic category (using implementation means), the UE 1020 attempts to find an ATSSS rule that matches the first traffic category. If a matching ATSSS rule is found, then the UE 1020 applies this rule to determine how to route the uplink traffic of the IP flow across the multiple accesses of the MA PDU Session.
  • an IP flow e.g., from an internal application
  • An IP flow as used herein can be defined as a sequence of data packets having the same characteristics, e.g., packets that should be delivered to the same destination IP address, and/ or to the same destination port, and/ or using the same transport protocol (e.g., UDP or TCP).
  • the UE 1020 may send information to UPF 1070 in order to assist the UPF 1070 routing the downlink traffic of the IP flow in alignment with the routing of the uplink traffic.
  • the MAR rules receives by UPF 1070 may not contain traffic categories (as the ATSSS rules) because it is difficult for the UPF 1070 to identify the traffic category of the IP flows transmitted in the downlink direction. This is why the UE 1020 may send information to UPF 1070 to assist the UPF 1070 deciding how to route the downlink traffic of the IP flow, which the UE 1020 has determined that it belongs to a certain traffic category.
  • This assistance information the UE 1020 provides to the UPF 1070 is illustrated in step 1012, wherein the UE 1020 may send a first Performance Measurement Function (PMF) message to UPF 1070, after determining how to route the uplink traffic of an IP flow that belongs to a first traffic category.
  • PMF Performance Measurement Function
  • This PMF message can be used by UPF 1070 to determine how to route the downlink traffic of this IP flow in order to align with the routing of the uplink traffic of this IP flow.
  • the UPF 1070 considers the assistance information in the first PMF message to determine how to route the downlink traffic of IP flow across the multiple accesses of the MA PDU session.
  • This disclosure proposes novel enhancements to the ATSSS feature, which enable the 5GC network to create ATSSS rules for a MA PDU Session that specify how data traffic belonging to a first traffic category should be routed across the multiple accesses of the MA PDU Session.
  • the disclosure proposes (a) extensions to the ATSSS rules, (b) extensions to the MA PDU Session procedure and (c) extensions that specify an IP flow can be routed across the multiple accesses of the MA PDU Session based on the traffic category of the IP flow.
  • the disclosure herein provides, from the perspective of a UE in, for instance Figure 10, a method comprising: receiving an IP flow to be transmitted over the MA PDU Session, wherein the IP flow belongs to a first Traffic Category; finding an ATSSS rule matching the first Traffic Category; and applying the matching ATSSS rule to determine how to route the uplink traffic of IP flow across the multiple accesses of the MA PDU Session.
  • the method further comprises sending an MA PDU Session Establishment Request message containing the ATSSS capabilities of the UE, which indicate whether the UE can support traffic steering based on traffic categories.
  • the method further comprises receiving an MA PDU Session Establishment Accept message containing at least one ATSSS rule, wherein the at least one ATSSS rule specifies how data traffic is to be routed across the multiple accesses of the MA PDU Session based on the traffic category for the data traffic.
  • the disclosure herein further provides methods from the perspective of a PCF and a UPF, such as the PCF and UPF of Figure 10.
  • the method may also be embodied in a set of instructions, stored on a computer readable medium, which when loaded into a computer processor, Digital Signal Processor (DSP) or similar, causes the processor to carry out the hereinbefore described methods.
  • DSP Digital Signal Processor
  • 3GPP third generation partnership project
  • 5GC 5G core
  • AMF access management function
  • AR augmented reality
  • ATSSS access traffic steering, switching, splitting
  • DL downlink
  • GSMA global system for mobile communications association
  • IMS IP multimedia subsystem
  • loT Internet of Things
  • IP internet protocol
  • MA PDU multiaccess protocol data unit
  • MA multiaccess
  • MAR multiaccess rule
  • NG-RAN new generation radio access network
  • PCC policy control and charging
  • PCF policy control function
  • SMF session management function
  • UDM unified data manager/ management
  • UDM unified data manager/ management
  • UE user equipment
  • UL uplink
  • UPF user plane function
  • VR virtual reality
  • WLAN wireless local area network

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un appareil d'équipement utilisateur pour communication sans fil, comprenant : un processeur ; et une mémoire couplée au processeur, le processeur étant configuré pour amener l'appareil d'équipement utilisateur à : recevoir un flux de données aux fins de transmission au cours d'une session d'unité de données de protocole multi-accès 'PDU MA' ; déterminer au moins une première catégorie de trafic du flux de données ; déterminer au moins une première règle d'orientation qui correspond à ladite au moins une première catégorie de trafic ; et déterminer, sur la base de ladite au moins une première règle d'orientation, la manière dont le trafic montant du flux de données doit être acheminé par un ou plusieurs accès de la session de PDU MA.
PCT/EP2023/062179 2023-03-24 2023-05-09 Prise en charge de l'orientation de trafic multi-accès dans un système de communication sans fil WO2024088593A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
GR20230100252 2023-03-24
GR20230100252 2023-03-24

Publications (1)

Publication Number Publication Date
WO2024088593A1 true WO2024088593A1 (fr) 2024-05-02

Family

ID=86558791

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2023/062179 WO2024088593A1 (fr) 2023-03-24 2023-05-09 Prise en charge de l'orientation de trafic multi-accès dans un système de communication sans fil

Country Status (1)

Country Link
WO (1) WO2024088593A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220116327A1 (en) * 2020-02-28 2022-04-14 Apostolis Salkintzis Access traffic steering using a plurality of steering connections over different access networks
US20220264370A1 (en) * 2019-08-22 2022-08-18 Ofinno, Llc Policy Control for Multiple Accesses

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220264370A1 (en) * 2019-08-22 2022-08-18 Ofinno, Llc Policy Control for Multiple Accesses
US20220116327A1 (en) * 2020-02-28 2022-04-14 Apostolis Salkintzis Access traffic steering using a plurality of steering connections over different access networks

Similar Documents

Publication Publication Date Title
US20230247704A1 (en) Multi-access data connection in a mobile network
US10904942B2 (en) Network slice selection in a mobile communication network
US11979813B2 (en) Data packet routing in a remote unit
US20220116327A1 (en) Access traffic steering using a plurality of steering connections over different access networks
US20210329541A1 (en) Determining a type of network connection from an os-specific connection capability
EP4183147A1 (fr) Nouveau mappage d'un profil de réseau
WO2024088593A1 (fr) Prise en charge de l'orientation de trafic multi-accès dans un système de communication sans fil
WO2024088592A1 (fr) Établissement d'une connexion de données à accès multiples dans un système de communication sans fil
WO2024088570A1 (fr) Appareil et procédé pour prendre en charge la réalité étendue et le trafic multimédia dans un réseau de communication sans fil
WO2024027942A1 (fr) Contrôle de qualité de service dans un réseau de communication sans fil
WO2024088598A1 (fr) Mappage réseau de sections de règles dans un réseau de communication sans fil
US20230300729A1 (en) User equipment radio capabilities
WO2024061475A1 (fr) Qualité de service de supports de réalité étendue sur un réseau de communication sans fil
US20240114335A1 (en) Network security based on routing information
WO2024051960A1 (fr) Synchronisation d'horloges entre des dispositifs via une liaison latérale dans un réseau de communications sans fil
WO2024032915A1 (fr) Connexion à un réseau d'accès wlan à l'aide d'une authentification basée sur 3gpp
WO2024068025A1 (fr) Communication de flux de réseau sensible au temps dans un réseau de communication sans fil
WO2024068026A1 (fr) Protection de règle de politique de sélection d'itinéraires d'ue pendant l'itinérance
WO2024037727A1 (fr) Procédés et appareils permettant de fournir des informations de consentement d'utilisateur pour des services de collecte de données dans un réseau de communication sans fil
WO2024022594A1 (fr) Association de dispositifs virtuels dans des environnements virtuels à des abonnements d'utilisateur dans un réseau de communication sans fil
WO2024008320A1 (fr) Découverte de dispositifs dans un service d'expérience virtuelle dans un réseau de communication sans fil
WO2024088552A1 (fr) Amélioration des performances de fonction de plan utilisateur dans un réseau de communication sans fil
WO2023057078A1 (fr) Coordination de l'enregistrement double
WO2024022596A1 (fr) Procédés et appareils de fourniture de services de périphérie lors de déploiements fédérés de réseaux de communication sans fil
WO2023001394A1 (fr) Mappage de ports pour une connexion de données à accès multiple