Guaranteed bit rate quality of service flows for access traffic steering, switching, and splitting

Abstract

Systems, methods, and instrumentalities are disclosed herein for access traffic steering, switching, and splitting for guaranteed bit rate (GBR) flows. An example network node may receive, from a device, a first message that indicates a transition of a redundant steering mode (RSM) from a first state to a second state and a duration of time that the RSM will remain in the second state. In the first state, the device may send transmissions via a first access node and a second access node. In the second state, the device may send transmissions via only the first access node. The network node may determine a change to a guaranteed bit rate condition of the second access node. In response to the first message, the network node may send, to the second access node, a second message that indicates the change to the guaranteed bit rate condition of the second access node.

Description

GUARANTEED BIT RATE QUALITY OF SERVICE FLOWS FOR ACCESS TRAFFIC STEERING, SWITCHING, AND SPLITTINGCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 531,878, filed August 10, 2023, the contents of which is incorporated by reference herein.BACKGROUND

[0002] Mobile communications using wireless communications continue to evolve. A fifth generation of mobile communication radio access technology (RAT) may be referred to as 5G new radio (NR). A previous (legacy) generation of mobile communication RAT may be, for example, fourth generation (4G) long term evolution (LTE).SUMMARY

[0003] Systems, methods, and instrumentalities are disclosed herein for access traffic steering, switching, and splitting for guaranteed bit rate (GBR) flows.

[0004] An example network node may receive a first message from a device. The first message may indicate a transition of a redundant steering mode (RSM) from a first state to a second state and a duration of time that the RSM will remain in the second state. In the first state, the device may send transmissions via a first access node and a second access node. In the second state, the device may send transmissions via only the first access node. The network node may determine a change to a guaranteed bit rate condition of the second access node. In response to the first message, the network node may send a second message to the second access node. The second message may indicate the change to the guaranteed bit rate condition of the second access node.

[0005] The duration of time may be a first duration of time. The change may be a first change. The network node may receive a third message from the device. The third message may indicate a transition of the RSM from the second state to the first state and a second duration of time that the RSM will remain in the first state. The network node may determine a second change to the guaranteed bit rate condition of the second access node. In response to the third message, the network node may send a fourth messageto the second access node. The fourth message may indicate at least one of the transition of the RSM from the second state to the first state, the second change to the guaranteed bit rate condition of the second access node, or the second duration of time.

[0006] While in the first state, the network node may receive, from the device, duplication information that indicates a percentage of total traffic that is duplicated over the first access node and the second access node.

[0007] The network node may determine the change to the guaranteed bit rate condition of the second access node by determining a guaranteed bit rate scaling factor based on the percentage and sending the guaranteed bit rate scaling factor to the second access node.

[0008] The network node may determine the change to the guaranteed bit rate condition of the second access node by determining a guaranteed bit rate scaling factor based on the transition from the first state to the second state, and scaling the guaranteed bit rate condition based on the guaranteed bit rate scaling factor.

[0009] The second message may indicate at least one of the transition of the RSM from the first state to the second state, or the duration of time.

[0010] The guaranteed bit rate condition may be associated with at least one of a duplication rate at the second access node, a duplication status at the second access node, or a bit rate measurement at the second access node.

[0011] The first access node may be a primary access node. The second access node may be a secondary access node. The network node may determine to change the second access node to the primary access node and the first access node to the secondary access node.

[0012] The network node may determine to change the second access node to the primary access node and the first access node to the secondary access node based on the first access node failing to satisfy a guaranteed bit rate threshold.

[0013] An example device may receive a multi-access protocol data unit (MA-PDU) session establishment request from a wireless transmit / receive unit (WTRU). The MA-PDU session establishment request may indicate that the WTRU supports guaranteed bit rate (GBR) assistance information. The device may select a static redundant steering mode with a primary access node for an MA-PDU session. The device may determine GBR handling information based on the static redundant steering mode and the indication that the WTRU supports GBR assistance information. The device may send a quality of service (QoS) profile to the primary access node and a secondary access node. The QoS profile may include the GBR handling information. The device may, based on a satisfaction of a condition, determine an updated GBR parameter (e.g., requirement) and updated GBR handling information for the secondary access node.The device may send to the secondary access node an updated QoS profile that indicates the updated GBR parameter (e.g., requirement) and the updated GBR handling information.

[0014] The GBR assistance information may include measurements for GBR optimization over the secondary access node. The GBR handling information may indicate one or more of: a primary or secondary status for the primary and secondary access nodes, a GBR scaling factor, or a user plane security policy. The condition may be associated with a duplication rate at the secondary access node, a duplication status at the secondary access node, or bit rate measurements at the secondary access node.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG. 1A is a system diagram illustrating an example communications system in which one or more disclosed embodiments may be implemented.

[0016] FIG. 1 B is a system diagram illustrating an example wireless transmit / receive unit (WTRU) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0017] FIG. 1 C is a system diagram illustrating an example radio access network (RAN) and an example core network (ON) that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0018] FIG. 1 D is a system diagram illustrating a further example RAN and a further example ON that may be used within the communications system illustrated in FIG. 1A according to an embodiment.

[0019] FIG. 2 shows an example WTRU with multiple simultaneous access types.

[0020] FIG. 3 shows an example WTRU with multiple simultaneous access types.

[0021] FIG. 4 shows an example of gaps in a transmission over a first access type.

[0022] FIG. 5 shows an example technique for setting up a multi-access protocol data unit (MA-PDU) session for a guaranteed bit rate (GBR) quality of service (QoS) flow.DETAILED DESCRIPTION

[0023] FIG. 1A is a diagram illustrating an example communications system 100 in which one or more disclosed embodiments may be implemented. The communications system 100 may be a multiple access system that provides content, such as voice, data, video, messaging, broadcast, etc., to multiple wireless users. The communications system 100 may enable multiple wireless users to access such content through the sharing of system resources, including wireless bandwidth. For example, the communicationssystems 100 may employ one or more channel access methods, such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), single-carrier FDMA (SC-FDMA), zero-tail unique-word DFT-Spread OFDM (ZT UW DTS-s OFDM), unique word OFDM (UW-OFDM), resource block-filtered OFDM, filter bank multicarrier (FBMC), and the like.

[0024] As shown in FIG. 1A, the communications system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, a RAN 104 / 113, a ON 106 / 115, a public switched telephone network (PSTN) 108, the Internet 110, and other networks 112, though it will be appreciated that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102a, 102b, 102c, 102d may be any type of device configured to operate and / or communicate in a wireless environment. By way of example, the WTRUs 102a, 102b, 102c, 102d, any of which may be referred to as a “station” and / or a “STA”, may be configured to transmit and / or receive wireless signals and may include a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a subscription-based unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a netbook, a personal computer, a wireless sensor, a hotspot or Mi-Fi device, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. Any of the WTRUs 102a, 102b, 102c and 102d may be interchangeably referred to as a UE.

[0025] The communications systems 100 may also include a base station 114a and / or a base station 114b. Each of the base stations 114a, 114b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, 102c, 102d to facilitate access to one or more communication networks, such as the CN 106 / 115, the Internet 110, and / or the other networks 112. By way of example, the base stations 114a, 114b may be a base transceiver station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a gNB, a NR NodeB, a site controller, an access point (AP), a wireless router, and the like. While the base stations 114a, 114b are each depicted as a single element, it will be appreciated that the base stations 114a, 114b may include any number of interconnected base stations and / or network elements.

[0026] The base station 114a may be part of the RAN 104 / 113, which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. The base station 114a and / or the base station 114b may be configured to transmit and / or receive wireless signals on one or more carrier frequencies, which may be referred to asa cell (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage for a wireless service to a specific geographical area that may be relatively fixed or that may change over time. The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, in one embodiment, the base station 114a may include three transceivers, i.e., one for each sector of the cell. In an embodiment, the base station 114a may employ multiple-input multiple output (MIMO) technology and may utilize multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in desired spatial directions.

[0027] The base stations 114a, 114b may communicate with one or more of the WTRUs 102a, 102b, 102c, 102d over an air interface 116, which may be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). The air interface 116 may be established using any suitable radio access technology (RAT).

[0028] More specifically, as noted above, the communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and the like. For example, the base station 114a in the RAN 104 / 1 13 and the WTRUs 102a, 102b, 102c may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 using wideband CDMA (WCDMA). WCDMA may include communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink (DL) Packet Access (HSDPA) and / or High-Speed UL Packet Access (HSUPA).

[0029] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 116 using Long Term Evolution (LTE) and / or LTE-Advanced (LTE-A) and / or LTE-Advanced Pro (LTE-A Pro).

[0030] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement a radio technology such as NR Radio Access, which may establish the air interface 116 using New Radio (NR).

[0031] In an embodiment, the base station 114a and the WTRUs 102a, 102b, 102c may implement multiple radio access technologies. For example, the base station 114a and the WTRUs 102a, 102b, 102c may implement LTE radio access and NR radio access together, for instance using dual connectivity (DC) principles. Thus, the air interface utilized by WTRUs 102a, 102b, 102c may be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., an eNB and a gNB).

[0032] In other embodiments, the base station 114a and the WTRUs 102a, 102b, 102c may implement radio technologies such as IEEE 802.11 (i.e., Wireless Fidelity (WiFi), IEEE 802.16 (i.e., Worldwide Interoperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for Mobile communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0033] The base station 114b in FIG. 1 A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a campus, an industrial facility, an air corridor (e.g., for use by drones), a roadway, and the like. In one embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station 114b and the WTRUs 102c, 102d may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, the base station 114b and the WTRUs 102c, 102d may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, LTE-A Pro, NR etc.) to establish a picocell or femtocell. As shown in FIG. 1A, the base station 114b may have a direct connection to the Internet 110. Thus, the base station 114b may not be required to access the Internet 110 via the CN 106 / 115.

[0034] The RAN 104 / 113 may be in communication with the CN 106 / 115, which may be any type of network configured to provide voice, data, applications, and / or voice over internet protocol (VoIP) services to one or more of the WTRUs 102a, 102b, 102c, 102d. The data may have varying quality of service (QoS) requirements, such as differing throughput requirements, latency requirements, error tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, and the like. The CN 106 / 115 may provide call control, billing services, mobile location-based services, pre-paid calling, Internet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication. Although not shown in FIG. 1A, it will be appreciated that the RAN 104 / 113 and / or the CN 106 / 115 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 104 / 113 or a different RAT. For example, in addition to being connected to the RAN 104 / 113, which may be utilizing a NR radio technology, the CN 106 / 115 may also be in communication with another RAN (not shown) employing a GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0035] The CN 106 / 115 may also serve as a gateway for the WTRUs 102a, 102b, 102c, 102d to access the PSTN 108, the Internet 110, and / or the other networks 112. The PSTN 108 may include circuit- switched telephone networks that provide plain old telephone service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices that use commoncommunication protocols, such as the transmission control protocol (TCP), user datagram protocol (UDP) and / or the internet protocol (IP) in the TCP / IP internet protocol suite. The networks 112 may include wired and / or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may include another CN connected to one or more RANs, which may employ the same RAT as the RAN 104 / 113 or a different RAT.

[0036] Some or all of the WTRUs 102a, 102b, 102c, 102d in the communications system 100 may include multi-mode capabilities (e.g., the WTRUs 102a, 102b, 102c, 102d may include multiple transceivers for communicating with different wireless networks over different wireless links). For example, the WTRU 102c shown in FIG. 1A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114b, which may employ an IEEE 802 radio technology.

[0037] FIG. 1 B is a system diagram illustrating an example WTRU 102. As shown in FIG. 1 B, the WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and / or other peripherals 138, among others. It will be appreciated that the WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with an embodiment.

[0038] The processor 118 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 1 B depicts the processor 118 and the transceiver 120 as separate components, it will be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0039] The transmit / receive element 122 may be configured to transmit signals to, or receive signals from, a base station (e.g., the base station 114a) over the air interface 116. For example, in one embodiment, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmit / receive element 122 may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In yet another embodiment, the transmit / receive element 122 may be configured to transmit and / or receive both RF and light signals. It willbe appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless signals.

[0040] Although the transmit / receive element 122 is depicted in FIG. 1 B as a single element, the WTRU 102 may include any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, in one embodiment, the WTRU 102 may include two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 116.

[0041] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may include multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, such as NR and IEEE 802.11, for example.

[0042] The processor 118 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit). The processor 118 may also output user data to the speaker / microphone 124, the keypad 126, and / or the display / touchpad 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory, such as the non-removable memory 130 and / or the removable memory 132. The non-removable memory 130 may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may include a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. In other embodiments, the processor 118 may access information from, and store data in, memory that is not physically located on the WTRU 102, such as on a server or a home computer (not shown).

[0043] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example, the power source 134 may include one or more dry cell batteries (e.g., nickel-cadmium (NiCd), nickel-zinc (NiZn), nickel metal hydride (NiMH), lithium-ion (Li-ion), etc.), solar cells, fuel cells, and the like.

[0044] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 116 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It willbe appreciated that the WTRU 102 may acquire location information by way of any suitable locationdetermination method while remaining consistent with an embodiment.

[0045] The processor 118 may further be coupled to other peripherals 138, which may include one or more software and / or hardware modules that provide additional features, functionality and / or wired or wireless connectivity. For example, the peripherals 138 may include an accelerometer, an e-compass, a satellite transceiver, a digital camera (for photographs and / or video), a universal serial bus (USB) port, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, a Virtual Reality and / or Augmented Reality (VR / AR) device, an activity tracker, and the like. The peripherals 138 may include one or more sensors, the sensors may be one or more of a gyroscope, an accelerometer, a hall effect sensor, a magnetometer, an orientation sensor, a proximity sensor, a temperature sensor, a time sensor; a geolocation sensor; an altimeter, a light sensor, a touch sensor, a magnetometer, a barometer, a gesture sensor, a biometric sensor, and / or a humidity sensor.

[0046] The WTRU 102 may include a full duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for both the UL (e.g., for transmission) and downlink (e.g., for reception) may be concurrent and / or simultaneous. The full duplex radio may include an interference management unit to reduce and or substantially eliminate self-interference via either hardware (e.g., a choke) or signal processing via a processor (e.g., a separate processor (not shown) or via processor 118). In an embodiment, the WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., associated with particular subframes for either the UL (e.g., for transmission) or the downlink (e.g., for reception)).

[0047] FIG. 1 C is a system diagram illustrating the RAN 104 and the CN 106 according to an embodiment. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 104 may also be in communication with the CN 106.

[0048] The RAN 104 may include eNode-Bs 160a, 160b, 160c, though it will be appreciated that the RAN 104 may include any number of eNode-Bs while remaining consistent with an embodiment. The eNode-Bs 160a, 160b, 160c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the eNode-Bs 160a, 160b, 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a.

[0049] Each of the eNode-Bs 160a, 160b, 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling ofusers in the UL and / or DL, and the like. As shown in FIG. 1 C, the eNode-Bs 160a, 160b, 160c may communicate with one another over an X2 interface.

[0050] The CN 106 shown in FIG. 1 C may include a mobility management entity (MME) 162, a serving gateway (SGW) 164, and a packet data network (PDN) gateway (or PGW) 166. While each of the foregoing elements are depicted as part of the CN 106, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0051] The MME 162 may be connected to each of the eNode-Bs 162a, 162b, 162c in the RAN 104 via an S1 interface and may serve as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, bearer activation / deactivation, selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, 102c, and the like. The MME 162 may provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM and / or WCDMA.

[0052] The SGW 164 may be connected to each of the eNode Bs 160a, 160b, 160c in the RAN 104 via the S1 interface. The SGW 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, 102c. The SGW 164 may perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when DL data is available for the WTRUs 102a, 102b, 102c, managing and storing contexts of the WTRUs 102a, 102b, 102c, and the like.

[0053] The SGW 164 may be connected to the PGW 166, which may provide the WTRUs 102a, 102b, 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b, 102c and IP-enabled devices.

[0054] The CN 106 may facilitate communications with other networks. For example, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, 102c and traditional land-line communications devices. For example, the CN 106 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 106 and the PSTN 108. In addition, the CN 106 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers.

[0055] Although the WTRU is described in FIGS. 1 A-1 D as a wireless terminal, it is contemplated that in certain representative embodiments that such a terminal may use (e.g., temporarily, or permanently) wired communication interfaces with the communication network.

[0056] In representative embodiments, the other network 112 may be a WLAN.

[0057] A WLAN in Infrastructure Basic Service Set (BSS) mode may have an Access Point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP may have an access or an interface to a Distribution System (DS) or another type of wired / wireless network that carries traffic in to and / or out of the BSS. Traffic to STAs that originates from outside the BSS may arrive through the AP and may be delivered to the STAs. Traffic originating from STAs to destinations outside the BSS may be sent to the AP to be delivered to respective destinations. Traffic between STAs within the BSS may be sent through the AP, for example, where the source STA may send traffic to the AP and the AP may deliver the traffic to the destination STA. The traffic between STAs within a BSS may be considered and / or referred to as peer-to- peer traffic. The peer-to-peer traffic may be sent between (e.g., directly between) the source and destination STAs with a direct link setup (DLS). In certain representative embodiments, the DLS may use an 802.11e DLS or an 802.11 z tunneled DLS (TDLS). A WLAN using an Independent BSS (IBSS) mode may not have an AP, and the STAs (e.g., all of the STAs) within or using the IBSS may communicate directly with each other. The IBSS mode of communication may sometimes be referred to herein as an “ad- hoc” mode of communication.

[0058] When using the 802.11 ac infrastructure mode of operation or a similar mode of operations, the AP may transmit a beacon on a fixed channel, such as a primary channel. The primary channel may be a fixed width (e.g., 20 MHz wide bandwidth) or a dynamically set width via signaling. The primary channel may be the operating channel of the BSS and may be used by the STAs to establish a connection with the AP. In certain representative embodiments, Carrier Sense Multiple Access with Collision Avoidance (CSMA / CA) may be implemented, for example in 802.11 systems. For CSMA / CA, the STAs (e.g., every STA), including the AP, may sense the primary channel. If the primary channel is sensed / detected and / or determined to be busy by a particular STA, the particular STA may back off. One STA (e.g., only one station) may transmit at any given time in a given BSS.

[0059] High Throughput (HT) STAs may use a 40 MHz wide channel for communication, for example, via a combination of the primary 20 MHz channel with an adjacent or nonadjacent 20 MHz channel to form a 40 MHz wide channel.

[0060] Very High Throughput (VHT) STAs may support 20MHz, 40 MHz, 80 MHz, and / or 160 MHz wide channels. The 40 MHz, and / or 80 MHz, channels may be formed by combining contiguous 20 MHz channels. A 160 MHz channel may be formed by combining 8 contiguous 20 MHz channels, or by combining two non-contiguous 80 MHz channels, which may be referred to as an 80+80 configuration. For the 80+80 configuration, the data, after channel encoding, may be passed through a segment parser that may divide the data into two streams. Inverse Fast Fourier Transform (IFFT) processing, and time domain processing, may be done on each stream separately. The streams may be mapped on to the two 80 MHzchannels, and the data may be transmitted by a transmitting STA. At the receiver of the receiving STA, the above-described operation for the 80+80 configuration may be reversed, and the combined data may be sent to the Medium Access Control (MAC).

[0061] Sub 1 GHz modes of operation are supported by 802.11 af and 802.11 ah. The channel operating bandwidths, and carriers, are reduced in 802.11 af and 802.11 ah relative to those used in 802.11 n, and802.11 ac. 802.11 af supports 5 MHz, 10 MHz and 20 MHz bandwidths in the TV White Space (TVWS) spectrum, and 802.11ah supports 1 MHz, 2 MHz, 4 MHz, 8 MHz, and 16 MHz bandwidths using non- TVWS spectrum. According to a representative embodiment, 802.11 ah may support Meter Type Control / Machine-Type Communications, such as MTC devices in a macro coverage area. MTC devices may have certain capabilities, for example, limited capabilities including support for (e.g., only support for) certain and / or limited bandwidths. The MTC devices may include a battery with a battery life above a threshold (e.g., to maintain a very long battery life).

[0062] WLAN systems, which may support multiple channels, and channel bandwidths, such as802.11 n, 802.11 ac, 802.11 af, and 802.11 ah, include a channel which may be designated as the primary channel. The primary channel may have a bandwidth equal to the largest common operating bandwidth supported by all STAs in the BSS. The bandwidth of the primary channel may be set and / or limited by a STA, from among all STAs operating in a BSS, which supports the smallest bandwidth operating mode. In the example of 802.11 ah, the primary channel may be 1 MHz wide for STAs (e.g., MTC type devices) that support (e.g., only support) a 1 MHz mode, even if the AP, and other STAs in the BSS support 2 MHz, 4 MHz, 8 MHz, 16 MHz, and / or other channel bandwidth operating modes. Carrier sensing and / or Network Allocation Vector (NAV) settings may depend on the status of the primary channel. If the primary channel is busy, for example, due to a STA (which supports only a 1 MHz operating mode), transmitting to the AP, the entire available frequency bands may be considered busy even though a majority of the frequency bands remains idle and may be available.

[0063] In the United States, the available frequency bands, which may be used by 802.11 ah, are from 902 MHz to 928 MHz. In Korea, the available frequency bands are from 917.5 MHz to 923.5 MHz. In Japan, the available frequency bands are from 916.5 MHz to 927.5 MHz. The total bandwidth available for802.11 ah is 6 MHz to 26 MHz depending on the country code.

[0064] FIG. 1 D is a system diagram illustrating the RAN 113 and the CN 115 according to an embodiment. As noted above, the RAN 113 may employ an NR radio technology to communicate with the WTRUs 102a, 102b, 102c over the air interface 116. The RAN 113 may also be in communication with the

[0065] The RAN 113 may include gNBs 180a, 180b, 180c, though it will be appreciated that the RAN 113 may include any number of gNBs while remaining consistent with an embodiment. The gNBs 180a, 180b, 180c may each include one or more transceivers for communicating with the WTRUs 102a, 102b, 102c over the air interface 116. In one embodiment, the gNBs 180a, 180b, 180c may implement MIMO technology. For example, gNBs 180a, 108b may utilize beamforming to transmit signals to and / or receive signals from the gNBs 180a, 180b, 180c. Thus, the gNB 180a, for example, may use multiple antennas to transmit wireless signals to, and / or receive wireless signals from, the WTRU 102a. In an embodiment, the gNBs 180a, 180b, 180c may implement carrier aggregation technology. For example, the gNB 180a may transmit multiple component carriers to the WTRU 102a (not shown). A subset of these component carriers may be on unlicensed spectrum while the remaining component carriers may be on licensed spectrum. In an embodiment, the gNBs 180a, 180b, 180c may implement Coordinated Multi-Point (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNB 180a and gNB 180b (and / or gNB 180c).

[0066] The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using transmissions associated with a scalable numerology. For example, the OFDM symbol spacing and / or OFDM subcarrier spacing may vary for different transmissions, different cells, and / or different portions of the wireless transmission spectrum. The WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using subframe or transmission time intervals (TTIs) of various or scalable lengths (e.g., containing varying number of OFDM symbols and / or lasting varying lengths of absolute time).

[0067] The gNBs 180a, 180b, 180c may be configured to communicate with the WTRUs 102a, 102b, 102c in a standalone configuration and / or a non-standalone configuration. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c without also accessing other RANs (e.g., such as eNode-Bs 160a, 160b, 160c). In the standalone configuration, WTRUs 102a, 102b, 102c may utilize one or more of gNBs 180a, 180b, 180c as a mobility anchor point. In the standalone configuration, WTRUs 102a, 102b, 102c may communicate with gNBs 180a, 180b, 180c using signals in an unlicensed band. In a non-standalone configuration WTRUs 102a, 102b, 102c may communicate with / connect to gNBs 180a, 180b, 180c while also communicating with / connecting to another RAN such as eNode-Bs 160a, 160b, 160c. For example, WTRUs 102a, 102b, 102c may implement DC principles to communicate with one or more gNBs 180a, 180b, 180c and one or more eNode-Bs 160a, 160b, 160c substantially simultaneously. In the non-standalone configuration, eNode-Bs 160a, 160b, 160c may serve as a mobility anchor for WTRUs 102a, 102b, 102c and gNBs 180a, 180b, 180c may provide additional coverage and / or throughput for servicing WTRUs 102a, 102b, 102c.

[0068] Each of the gNBs 180a, 180b, 180c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the UL and / or DL, support of network slicing, dual connectivity, interworking between NR and E- UTRA, routing of user plane data towards User Plane Function (UPF) 184a, 184b, routing of control plane information towards Access and Mobility Management Function (AMF) 182a, 182b and the like. As shown in FIG. 1 D, the gNBs 180a, 180b, 180c may communicate with one another over an Xn interface.

[0069] The CN 115 shown in FIG. 1 D may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and possibly a Data Network (DN) 185a, 185b. While each of the foregoing elements are depicted as part of the CN 115, it will be appreciated that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0070] The AMF 182a, 182b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N2 interface and may serve as a control node. For example, the AMF 182a, 182b may be responsible for authenticating users of the WTRUs 102a, 102b, 102c, support for network slicing (e.g., handling of different PDU sessions with different requirements), selecting a particular SMF 183a, 183b, management of the registration area, termination of NAS signaling, mobility management, and the like. Network slicing may be used by the AMF 182a, 182b in order to customize CN support for WTRUs 102a, 102b, 102c based on the types of services being utilized WTRUs 102a, 102b, 102c. For example, different network slices may be established for different use cases such as services relying on ultra-reliable low latency (URLLC) access, services relying on enhanced massive mobile broadband (eMBB) access, services for machine type communication (MTC) access, and / or the like. The AMF 162 may provide a control plane function for switching between the RAN 113 and other RANs (not shown) that employ other radio technologies, such as LTE, LTE-A, LTE-A Pro, and / or non-3GPP access technologies such as WiFi.

[0071] The SMF 183a, 183b may be connected to an AMF 182a, 182b in the CN 115 via an N11 interface. The SMF 183a, 183b may also be connected to a UPF 184a, 184b in the CN 115 via an N4 interface. The SMF 183a, 183b may select and control the UPF 184a, 184b and configure the routing of traffic through the UPF 184a, 184b. The SMF 183a, 183b may perform other functions, such as managing and allocating UE IP address, managing PDU sessions, controlling policy enforcement and QoS, providing downlink data notifications, and the like. A PDU session type may be IP-based, non-IP based, Ethernetbased, and the like.

[0072] The UPF 184a, 184b may be connected to one or more of the gNBs 180a, 180b, 180c in the RAN 113 via an N3 interface, which may provide the WTRUs 102a, 102b, 102c with access to packet- switched networks, such as the Internet 110, to facilitate communications between the WTRUs 102a, 102b,102c and IP-enabled devices. The UPF 184, 184b may perform other functions, such as routing and forwarding packets, enforcing user plane policies, supporting multi-homed PDU sessions, handling user plane QoS, buffering downlink packets, providing mobility anchoring, and the like.

[0073] The CN 115 may facilitate communications with other networks. For example, the CN 115 may include, or may communicate with, an IP gateway (e.g., an IP multimedia subsystem (IMS) server) that serves as an interface between the CN 115 and the PSTN 108. In addition, the CN 115 may provide the WTRUs 102a, 102b, 102c with access to the other networks 112, which may include other wired and / or wireless networks that are owned and / or operated by other service providers. In one embodiment, the WTRUs 102a, 102b, 102c may be connected to a local Data Network (DN) 185a, 185b through the UPF 184a, 184b via the N3 interface to the UPF 184a, 184b and an N6 interface between the UPF 184a, 184b and the DN 185a, 185b.

[0074] In view of Figures 1A-1 D, and the corresponding description of Figures 1A-1 D, one or more, or all, of the functions described herein with regard to one or more of: WTRU 102a-d, Base Station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF 184a-b, SMF 183a-b, DN 185a-b, and / or any other device(s) described herein, may be performed by one or more emulation devices (not shown). The emulation devices may be one or more devices configured to emulate one or more, or all, of the functions described herein. For example, the emulation devices may be used to test other devices and / or to simulate network and / or WTRU functions.

[0075] The emulation devices may be designed to implement one or more tests of other devices in a lab environment and / or in an operator network environment. For example, the one or more emulation devices may perform the one or more, or all, functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network in order to test other devices within the communication network. The one or more emulation devices may perform the one or more, or all, functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. The emulation device may be directly coupled to another device for purposes of testing and / or may perform testing using over-the-air wireless communications.

[0076] The one or more emulation devices may perform the one or more, including all, functions while not being implemented / deployed as part of a wired and / or wireless communication network. For example, the emulation devices may be utilized in a testing scenario in a testing laboratory and / or a non-deployed (e.g., testing) wired and / or wireless communication network in order to implement testing of one or more components. The one or more emulation devices may be testing equipment. Direct RF coupling and / or wireless communications via RF circuitry (e.g., which may include one or more antennas) may be used by the emulation devices to transmit and / or receive data.

[0077] Reference to a timer herein may refer to a time, a time period, a tracking of time, a tracking of a period of time, a combination thereof, and / or the like. Reference to a timer expiration herein may refer to determining that the time has occurred or that the period of time has expired.

[0078] A guaranteed bit rate (GBR) parameter (e.g., specification or requirement) may be set up. The GBR parameter may be maintained.

[0079] A session management function (SMF) may support multi-access protocol data unit (MA-PDU) sessions.

[0080] The SMF may receive an MA-PDU session establishment request from a WTRU. The MA-PDU session establishment request may include an indication that the WTRU supports assistance information for GBR (e.g., GBR optimization).

[0081] The SMF may determine to use a static redundant steering mode (e.g., with a primary access) for the MA-PDU session.

[0082] The SMF may determine GBR handling (GBRH) information (e.g., based on the selected steering mode and the indication that the WTRU supports assistance information for GBR optimization).

[0083] The SMF may provide access traffic steering, switching, and splitting (ATSSS) rules to the WTRU. The SMF may provide N4 rules to a user plane function (UPF). The SMF may provide a QoS profile to radio access network (RAN) nodes. The QoS profile may include the GBRH information.

[0084] The SMF may determine a GBR parameter (e.g., a new GBR specification or requirement) for the secondary access RAN node. For example, the SMF may determine a GBR parameter (e.g., a new GBR specification or requirement) for the secondary access RAN node based on a change-in-GBR-parameter trigger. The SMF may provide an updated QoS profile to the RAN node.

[0085] The assistance information for GBR optimization may include measurements specific for GBR optimization (e.g., over a secondary access node).

[0086] GBRH information may include an indication of whether the RAN node is a secondary access node, a GBR scaling factor, a user plane (UP) security policy, and / or the like.

[0087] Change in GBR parameter (e.g., specification or requirement) triggers may include a monitored duplication rate at the secondary access node, a duplication status on the secondary access node, bit rate measurements in secondary access, and / or the like.

[0088] ATSSS may be used (e.g., in 3GPP).

[0089] WTRUs may be capable of one or more types of access (e.g., both 3GPP access and non-3GPP access). This capability may provide flexibility to network operators (e.g., in determining which access to use for a service data flow). In some examples (e.g., in Release 15), if a WTRU used more than one (e.g.,both) access types, the WTRU may (e.g., may be required to) establish independent single-access (SA) PDU sessions over each of the access types.

[0090] FIG. 2 illustrates an example WTRU with multiple access types (e.g., simultaneous 3GPP and non-3GPP access, in Release 15).

[0091] This architecture may not be flexible (e.g., it may not take full advantage of the flexibility). In some examples (e.g., in Release 16), an MA-PDU session may be used. The MA-PDU may allow uplink and downlink traffic of a service data flow to be more easily steered, switched, or split between access types (e.g., as illustrated in Fig. 3). An MA-PDU session may refer to a PDU session with traffic that can be sent over multiple access types (e.g., 3GPP access, non-3GPP access, or over both access types).

[0092] FIG. 3 illustrates an example WTRU with multiple access types (e.g., simultaneous 3GPP and non-3GPP access in Release 16).

[0093] The architecture (e.g., introduced in Release 16 and further enhanced in Release 17) is illustrated in Fig. 3. The architecture may allow the following ATSSS functionalities.

[0094] ATSSS functionalities may include access traffic steering. Access traffic steering may involve selecting an access network for a data flow (e.g., a new data flow). Access traffic steering may involve transferring the traffic of the data flow over the selected access network. Access traffic steering may be applicable between different access types (e.g., 3GPP and non-3GPP access types).

[0095] ATSSS functionalities may include access traffic switching. Access traffic switching may involve moving traffic (e.g., all traffic) of an ongoing data flow from an access type (e.g., one access network) to another access type (e.g., another access network). The data flow may be moved in a way that maintains the continuity of the data flow. Access traffic switching may be applicable between different access types (e.g., 3GPP and non-3GPP access types).

[0096] ATSSS functionalities may include access traffic splitting. Access traffic splitting may involve splitting the traffic of a data flow across multiple access networks. If traffic splitting is applied to a data flow, some traffic of the data flow may be transferred via an access type (e.g., one access type) and other traffic of the same data flow may be transferred via another access type. Access traffic splitting may be applicable between different access types (e.g., 3GPP and non-3GPP access types).

[0097] The steering functionality in an ATSSS-capable WTRU may steer, switch, and / or split the MA- PDU session traffic across multiple access types (e.g., 3GPP access and non-3GPP access). One or more (e.g., two) steering functionalities may be used (e.g., as standardized in release 17). A first example steering functionality may be a high-layer steering functionality. The high-layer steering functionality may operate above the Internet Protocol (IP) layer. The steering functionality may be based on a multi-path transmission control protocol (MPTCP) (e.g., sometimes referred to as “MPTCP functionality”). MPTCPfunctionality may be applicable (e.g., only applicable) to TCP traffic. A second example of steering functionality may be a low-layer steering functionality, which operates below the IP layer. A (e.g., only one) type of low-layer steering functionality may be used (e.g., In Release 17). The low-layer functionality may be referred to as “ATSSS Low-Layer functionality” (ATSSS-LL functionality). The ATSSS-LL functionality may be applicable to Ethernet and / or IP (e.g., TCP and UDP). The steering functionality may be a functionality that exists in more than one device (e.g., the endpoints of a PDU session, for example, both the WTRU and the UPF).

[0098] One or more steering modes may be allowed (e.g., with the above steering functionality). The steering mode may determine how the traffic of the matching service data flow may be distributed (e.g., across different access types, for example, 3GPP and non-3GPP access types). The steering modes supported (e.g., as of Release 16) may include one or more of the following.

[0099] The steering modes may be based on an active standby mode. The active standby mode may be used to steer traffic on an access type (e.g., the active access), for example, if this access is available. The active standby mode may be used to switch the traffic to another access type (e.g., the standby access), for example, if the active access becomes unavailable.

[0100] The steering modes may be based on a delay (e.g., the smallest delay). The delay may be used to steer traffic to the access that has (e.g., is determined to have) the smallest round-trip time (RTT). The WTRU and UPF may measure the RTT (e.g., to determine which access has the lowest RTT). The access may be used (e.g., may only be used) for a non-GBR service data flow (SDF).

[0101] The steering modes may be based on load balancing. Load balancing may be used to split traffic across access types (e.g., both access types). For example, load balancing may be used to split traffic across access types according to a percentage of traffic that may be sent over a first access type (e.g., 3GPP access) and a percentage of traffic that may be sent over a second access type (e.g., non-3GPP access). Load balancing may be applicable (e.g., only applicable) to non-GBR SDF.

[0102] The steering mode may be priority-based. In this case, the steering mode may steer traffic (e.g., all traffic) matching a policy, charging, and control (PCC) parameter (e.g., specification, requirement, a PCC rule, etc.) to a high priority access type (e.g., until the high priority access is determined to be congested). If the high priority access type may be congested, the traffic may be sent to a low priority access type (e.g., the traffic may be split over the two access types). A priority-based steering mode may be used (e.g., only used) for non-GBR SDF.

[0103] The steering modes may be enhanced (e.g., in Release 17). For the load balancing steering mode, a steering mode indicator may be added (e.g., in 3GPP). The steering mode indicator may indicate that the WTRU is capable of changing the default steering parameters (e.g., provided in the steering modecomponent) and / or may adjust the traffic steering (e.g., based on the WTRU’s own decisions). A steering mode indicator (e.g., only one of the following steering mode indicators) may be provided.

[0104] The steering mode indicator may include an autonomous load-balance indicator. If the autonomous load-balance indicator is provided, the WTRU may ignore the percentage(s) in the steering mode component (e.g., the default percentages provided by the network). In this case, the WTRU may determine (e.g., autonomously determine) percentages for traffic splitting (e.g., in a way that maximizes the aggregated bandwidth, for example, in the uplink direction).

[0105] The steering mode indicator may include a WTRU-assistance indicator. If the WTRU-assistance indicator is provided (e.g., by the network), the WTRU may decide how to distribute traffic (e.g., uplink traffic of the matching SDF). For example, the WTRU may decide how to distribute the traffic based on an internal state of the WTRU. For example, the WTRU may decide how to distribute the traffic if the WTRU is in a special internal state (e.g., a lower battery level). The WTRU may indicate (e.g., to the UPF) how the WTRU decided to distribute the uplink traffic of the matching SDF. In some cases (e.g., even if the WTRU- assistance indicator is provided), the WTRU may (e.g., still) distribute the uplink traffic as indicated by the network.

[0106] For the load balancing steering mode, a threshold value may be provided (e.g., according to 3GPP). The threshold value may be a value for RTT and / or a value for packet loss rate (PLR). The threshold value(s) may be applicable to more than one access type (e.g., both access types). The threshold value(s) may be applied by the WTRU and / or the UPF. If a measured parameter (e.g., at least one measured parameter, for example, RTT and / or PLR) on an access type (e.g., one access) exceeds the provided threshold value, the WTRU and / or UPF may stop sending traffic on that access type. If a measured parameter (e.g., at least one measured parameter, for example, RTT or PLR) on an access type (e.g., one access) exceeds the provided threshold value, the WTRU and / or UPF may continue sending traffic on that access type and may reduce the traffic on the access type (e.g., by an implementationspecific amount). The WTRU and / or UPF may send the amount of reduced traffic (e.g., the remaining traffic after reducing traffic on the determined access type) to another access type. If measured parameters (e.g., all measured parameters, for example, RTT and / or PLR) for more than one (e.g., both) access types do not exceed the provided threshold value(s), the WTRU and / or UPF may apply the fixed split percentage(s).

[0107] For the priority-based steering mode, a threshold value may be provided (e.g., according to 3GPP). The threshold value may be a value for RTT and / or a value for PLR. The threshold value(s) may be applicable to more than one access type (e.g., both access types). The threshold value(s) may be applied by the WTRU and / or UPF. The threshold value(s) may be considered by the WTRU and / or UPF to determine if an access has become congested. For example, if a measured parameter (e.g., RTT or PLR)on an access type (e.g., one access) exceeds the provided threshold value(s), the WTRU and / or UPF may consider the access type as congested. In this case, the WTRU and / or UPF may send traffic (e.g., leftover traffic) to the low priority access type.

[0108] Rules (e.g., ATSSS rules) may be (pre)configured at the WTRU and / or the UPF (e.g., to enable the steering modes for the steering functionalities). The rules may be generated by a session management function (SMF) (e.g., based on information known to a policy control function (PCF)). The rules may be sent to the WTRU. The WTRU may use the rules to determine switching functionality and / or a switching mode to use for traffic (e.g., uplink traffic). The rules (e.g., N4 rules) may be sent to the UPF. The UPF may use the rules to determine switching functionality and / or a switching mode to use for traffic (e.g., downlink traffic).

[0109] A performance measurement function (PMF) protocol may be used (e.g., at the WTRU and / or UPF). For example, the PMF protocol may be used to support one or more steering modes. The PMF protocol may indicate for the WTRU and / or UPF to take measurements to be used for the switching mode decisions. The measurements may include an RTT measurement, an access availability / unavailability report, and / or PLR.

[0110] In some examples (e.g., in Release 18), a redundant steering mode may be used. In the redundant steering mode, the traffic may be duplicated over more than one access type (e.g., over both access types). The traffic may be duplicated over more than one access type to better meet the parameter (e.g., specification or requirement) of SDFs. One or more (e.g., two) types of redundant steering mode may be used. The types of redundant steering modes may provide dynamicity of the duplication. For example, the types of redundant steering mode may be categorized as described herein.

[0111] The redundant steering mode may be static. In this case, the network may configure the WTRU and / or UPF with information regarding which access type is the primary access type (e.g., over which all packets are transmitted). The network may configure the WTRU and / or UPF with information regarding which access type is the secondary access type. If no primary access type is configured, the UPF and / or WTRU may duplicate packets over the different access types (e.g., both access types all the time, for example, 100% duplication). If the network configures a primary access type, the UPF and / or WTRU may send traffic (e.g., all traffic) over the primary access. The UPF and / or WTRU may decide (e.g., using a nonstandardized algorithm) whether to duplicate over the secondary access type.

[0112] The redundant steering mode may be dynamic. In this case, the duplication decision may be made per packet (e.g., for each packet of a flow). The decision may be based on measurements and / or parameters (e.g., specification, requirement, criteria, etc.). The dynamic redundant steering mode may be used (e.g., only used) for non-GBR SDF.

[0113] In some examples (e.g., Release 18), the UPF may be allowed to suspend and / or resume traffic duplication (e.g., based on the load at the UPF). The UPF may decide and inform the WTRU (e.g., via a PMF exchange).

[0114] The dynamic redundant steering mode may be used for (e.g., may only target) non-GBR traffic. The other steering modes (e.g., smallest delay, load-balancing, and / or priority-based steering modes) may be used (e.g., may only target) non-GBR traffic. Two (e.g., only two) steering modes may target GBR and non-GBR traffic (e.g., the static redundant steering mode and the active-standby steering mode). In these steering modes, the traffic may switch from an access type (e.g., one access) to another access type (e.g., based on an underlying condition). Fig. 4 illustrates an example of the redundant steering mode with dynamic duplication. The PDUs of the SDF are numbered in FIG. 4. As illustrated in FIG. 4, there may be a gap in the transmission over a first access type (e.g., the 3GPP access). In this case, PDUs 7, 8, and 9 of the SDF may not be transmitted over the first access type (e.g., the 3GPP access). The gap in transmission may be long and / or may impact one or more PDUs (e.g., many PDUs).

[0115] FIG. 4 illustrates gaps in transmission over a first access type (e.g., the 3GPP access).

[0116] The gaps in transmission may not be a problem for non-GBR traffic. For GBR traffic, the gaps in transmission may lead to inefficient scheduling at the RAN node.

[0117] Of the steering modes supported for GBR traffic, static redundant steering mode (e.g., only static redundant steering mode) may lead to cases in which there are gaps in the transmission over an access. The RAN node may try to maintain the configured GBR parameter (e.g., specification or requirement) over the access. In the active-standby mode, if the access type is the active access and there is a gap in the transmission over the active access, the network may determine (e.g., use this as an indication) to move (e.g., try to move) the GBR parameter (e.g., specification or requirement) to another access. The network may not intend to maintain the GBR parameter (e.g., specification or requirement) during the gaps in the transmissions.

[0118] Gaps in a transmission for a first access path may occur for one or more reasons. For example, a gap may occur if the UPF decides to suspend duplication, and the primary access type is configured as the second access path.

[0119] A gap may occur if the WTRU and / or UPF have a primary access type configured as the second access path. In this case, the WTRU and / or UPF may send data packets (e.g., all data packets of the SDF) on the second access. The WTRU and / or UPF may duplicate data packets of the SDF on the first access path.

[0120] The gaps on the access paths (e.g., 3GPP paths) may lead to inefficient scheduling at the network node (e.g., the 3GPP RAN node).

[0121] If the RAN node gets the QoS profile and knows that the traffic is GBR traffic for a QoS flow, theRAN node may perform one or more actions (e.g., based on the knowledge that the traffic is GBR traffic). For example, the RAN node may determine whether to accept the QoS flow and / or whether to accept future QoS flows.

[0122] The RAN node may determine whether a target cell may accept a QoS flow during a handover.

[0123] The RAN node may set up configured grant(s) for uplink transmission(s). The grants may be reserved for uplink transmission. The grants may be based on the uplink GBR.

[0124] Setting a GBR that is too high may result in rejecting QoS flows, increased handover rejections, and / or wasted (e.g., unused) configured grants. Setting a GBR that is too low may result in not meeting the minimum parameter (e.g., specification or requirement) for the application.

[0125] One or more techniques described herein may be used to resolve the gaps in transmission (e.g., gaps in transmission over the 3GPP access).

[0126] The WTRU and / or network may manage an access type (e.g., 3GPP access) if that access type is defined as secondary access and no traffic is sent over that access type (e.g., to avoid wasting 3GPP resources that are not used / needed and may be needed in the future). The RAN node may be configured to handle traffic with a certain GBR. Some traffic of this flow may not be transmitted by the RAN node.

[0127] The network may determine a GBR parameter (e.g., specification or requirement) for the secondary access RAN node (e.g., in the case where the static redundant mode is configured with primary access).

[0128] One or more conditions may trigger the network to change (e.g., dynamically change) the GBR parameter (e.g., specification or requirement) for the secondary access RAN node.

[0129] The network performs one or more operations if a GBR QoS flow, using static redundant steering mode, may have a primary access RAN node that is not able to meet the configured GBR parameter (e.g., specification or requirement), for example, as a result of higher priority GBR QoS flows.

[0130] As used herein, the term "gaps in transmission" may refer to the period of time during which PDUs of an SDF are not transmitted over an access (e.g., due to a steering mode decision). The PDUs may be transmitted over another access type.

[0131] As used herein, the term “assistance information for GBR optimization” may refer to measurements that are specific for GBR optimization over a secondary access node.

[0132] As used herein, the term “GBRH information” may refer to information (e.g., that may be provided by the SMF to the RAN node) that allows the RAN node to manage (e.g., more efficiently manage) GBRtraffic over a secondary access. For example, GBRH information may include an indication of whether a RAN node is a secondary access node, a GBR scaling factor, an uplink security policy, and / or the like.

[0133] As used herein, the term “change in GBR requirement trigger” (which may be referred to as a change in GBR parameter trigger) may refer to triggers (e.g., to the SMF) that may lead to a change in GBR parameter (e.g., specification or requirement) for a secondary node. For example, a trigger (e.g., GBR condition) may be a monitored duplication rate at secondary access, a duplication status on the secondary access, bit rate measurements in secondary access, and / or the like.

[0134] Feature(s) described herein may enable support (e.g., efficient support) of GBR QoS flows with static redundant steering modes. For example, feature(s) associated with setting up an MA-PDU session for a GBR QoS flow using static redundant steering mode are provided herein.

[0135] For example, feature(s) associated with changing (e.g., dynamically changing) the GBR parameter (e.g., specification or requirement) of a secondary leg (e.g., for an MA-PDU session using static redundant steering mode). The GBR parameter (e.g., specification requirement) may be changed based on monitored performance at the WTRU and / or UPF.

[0136] For example, the primary and secondary access types may be swapped for a GBR QoS flow (e.g., for an MA-PDU session using static redundant steering mode).

[0137] Feature(s) described herein may allow the network to avoid overprovisioning the GBR parameter (e.g., specification or requirement) for the secondary access. This may allow the RAN node to schedule (e.g., properly schedule) configured grants for the WTRU, serve more QoS, and / or avoid unnecessary handover rejections.

[0138] An MA-PDU session may be set up for a GBR QoS flow.

[0139] FIG. 5 illustrates an example technique for setting up an MA-PDU session with GBR traffic (e.g., an MA-PDU session for a GBR QoS flow). The steering mode selected for the MA-PDU session may be (e.g., may be assumed to be) a static redundant steering mode. The SMF may have (e.g., may be assumed to have) configured a primary access RAN node for the MA-PDU session.

[0140] At 1 , a WTRU application may initiate (e.g., decide to initiate) communication with an application server (AS). The WTRU may determine to use an MA-PDU session.

[0141] At 2, the WTRU may send a PDU session establishment / modification request. The request may include an indication that the WTRU supports assistance information for GBR optimization over the secondary access.

[0142] At 3, the SMF may determine to use a static redundant steering mode for the MA-PDU session (e.g., based on configuration or PCC rules). The SMF may determine one or more ATSSS rules for theWTRU and / or N4 rules for the UPF. The SMF may determine to bind the service data flow to a QoS flow with an uplink and / or downlink GBR. The SMF may determine GBRH information (e.g., based on the WTRU support of assistance information for GBR optimization). Based on the GBRH information, the SMF may determine a UP security policy for the MA-PDU session.

[0143] At 4, the SMF may send to the UPF an N4 session establishment / modification request (e.g., including one or more N4 rules). The UPF may configure the ATSSS layer. The UPF may allocate the tunnels for the MA-PDU session.

[0144] At 5, the SMF may send a message to the RAN node over which the PDU session establishment / modification request was received. The message may include a PDU session establishment / modification accept message to be forwarded to the WTRU. The message may include N2 SM information. The N2 SM information may include the QoS profile for the GBR QoS flow.

[0145] The SMF may provide GBRH information. The GBRH information may include an indication of whether the RAN node is a primary access RAN node or a secondary access RAN node. The GBRH information may include an indication of an initial scaling factor (e.g., alpha). The RAN node may use alpha to scale the GBR specification (e.g., requirement). For example, if alpha is 0.5, the RAN node may determine that half (e.g., only half) of the GBR parameter (e.g., specification or requirement) has to be met. The GBRH information may include an updated UP security policy (e.g., integrity / confidentiality required, preferred, or not required). The updated UP security policy may be based on the SMF determination(s) at 3.

[0146] The SMF may decide to use different GBR parameters (e.g., specifications or requirements) for the primary access RAN node and / or the secondary access RAN node (e.g., that use access node specific GBR specifications). For example, if the QoS flow has a GBR of K bits per second (bps), the SMF may configure a GBR parameter (e.g., specification or requirement) of K bps for the primary access RAN node and a percentage (e.g., a fixed percentage) of K bps for the secondary access RAN node. The SMF may determine the percentage based on a (pre)configuration. The SMF may monitor prior QoS flows and determine the percentage (e.g., an acceptable percentage based on prior QoS flows).

[0147] At 6, the RAN node may forward the PDU session establishment / modification accept message to the WTRU. The PDU session establishment / modification accept message may carry the ATSSS rules for static redundant steering mode. The ATSSS rules may provide an indication of the primary access for the static redundant steering mode. The ATSSS rules may provide measurement configuration information in support of GBR optimization over the secondary access.

[0148] At 7, if the SMF is aware that the WTRU is registered (e.g., already registered) over the second access, the SMF may send the N2 SM information to the second access. The N2 SM information may include the QoS profile for the GBR QoS flow. The SMF may provide GBRH information.

[0149] The RAN nodes may use (e.g., subsequently use) the provided QoS profiles (e.g., in scheduling the traffic to / from the WTRU, in making handover decisions for future QoS flows, in making admission control decisions for future QoS flows, and / or the like). If a RAN node determines that it acts as a secondary access node, the RAN node may scale the GBR specification (e.g., requirement). For example, the RAN node may scale the GBR parameter (e.g., specification or requirement) based on the provided scaling factor in the QoS profile.

[0150] Application traffic (e.g., all downlink and uplink application traffic) may be sent over the MA-PDU session between the WTRU and UPF.

[0151] The GBR parameter (e.g., specification or requirement) for the secondary access RAN node may be changed (e.g., dynamically changed).

[0152] If downlink and uplink traffic is using the configured MA-PDU session, the GBR specification (e.g., requirement) may change (e.g., dynamically change) for the secondary access node (e.g., using one of the following changes in GBR parameter (e.g., requirement) triggers).

[0153] The WTRU may operate in a first state in which transmissions are sent via a first access node and a second access node. The WTRU may operate in the second state in which transmissions are sent via only the first access node. In an example, the WTRU (and / or UPF) may monitor the amount of transmissions (e.g., traffic) that is duplicated over the secondary access node (e.g., sent via the first access node and the second access node). The amount of traffic may be a percentage (e.g., 40% of traffic for the QoS flow is duplicated over the secondary access node).

[0154] The duplication monitoring information (e.g., duplication percentage) may be reported to the SMF. The information may be monitored by the PMF at the WTRU and / or by the PMF at the UPF. The UPF may provide the information over an N4 session level report. The WTRU may send the information to the UPF in a PMF measurement. The UPF may (e.g., subsequently) forward the information to the SMF (e.g., in an N4 session level report). The WTRU may provide the measurement information to the UPF via an NAS SM message. The information may be provided periodically. The information may be provided when the percentage of duplication changes by a certain threshold. The information may be provided when the percentage of duplication crosses a threshold.

[0155] The SMF may determine a GBR scaling factor (e.g., alpha) for the secondary access node (e.g., based on the percentage of total traffic that is duplicated over the first access node and the second access node).

[0156] The SMF may scale the guaranteed bit rate condition based on the guaranteed bit rate scaling factor. The SMF may send / provide the GBR scaling factor to the secondary access RAN node. The secondary access RAN node may scale the GBR parameter (e.g., specification or requirement) for the QoS flow (e.g., reduce according to the scaling factor). The SMF may inform the primary access RAN node that the GBR over the secondary access may be scaled. This information may be provided as part of a modified QoS profile (e.g., included in N2 SM information). This information may be included in time sensitive communications assistance information (TSCAI) (e.g., and forwarded to the RAN node).

[0157] In an example, the WTRU (and / or UPF) may monitor if traffic is duplicated over the secondary access node. The WTRU (and / or UPF) may send an indication to the SMF if traffic duplication changes from active to inactive, and / or vice versa. For example, the WTRU may send a message (e.g., to a network node, for example, the SMF) that indicates a transition of RSM from the first state (e.g., transmissions are sent via a first access node and a second access node) to the second state (e.g., transmissions are sent via only the first access node). Similarly, the WTRU may send a message that indicates a transition of the RSM from the second state to the first state.

[0158] The WTRU and / or UPF may provide an indication of a duration of time that the RSM will remain in the first or second state (e.g., how long the current condition, for example, only sending transmissions via the first access node, may persist). For example, a UPF may decide to suspend duplication for K seconds. The duration (K) may be provided to the SMF (e.g., so that it may be forwarded to the secondary access RAN node). The UPF may provide the information over an N4 session level report. The WTRU may send this information to the UPF in a PMF measurement. The UPF may (e.g., subsequently) forward the information to the SMF (e.g., in an N4 session level report. The WTRU may provide the measurement information to the UPF via a NAS SM message.

[0159] The network node (e.g., SMF) may determine a change to a guaranteed bit rate condition of the second access node. For example, the SMF may use the indication (e.g., message from the WTRU indicating the state transition) to determine a GBR scaling factor for the secondary access node. The SMF may use the indication to determine a new GBR parameter (e.g., specification or requirement) for the secondary access. The SMF may use the indication to indicate to the secondary access RAN node that traffic duplication is transitioning to active or transitioning to inactive on a QoS flow. The SMF may provide an indication of a duration of time that the RSM will remain in the first or second state (e.g., how long the transition is expected to last, for example, K seconds). This information may be provided as part of a modified QoS profile (e.g., included in N2 SM information). The information may be included in the TSCAI (e.g., and forwarded to the RAN node).

[0160] The RAN node may use the provided information. For example, the RAN node may decide whether to enforce GBR parameter (e.g., specification or requirement) for a QoS flow over the secondary access RAN node.

[0161] The guaranteed bit rate condition may be associated with at least one of a duplication rate at the second access node, a duplication status at the second access node, or a bit rate measurement at the second access node. In an example, the WTRU (and / or UPF) may monitor the bit rate over an access (e.g., each access). If the average bit rate over the primary access is less than the GBR, the network may take this as an indication that the GBR parameter (e.g., specification or requirement) over the primary access is over-provisioned (e.g., and / or that the GBR parameter, for example, specification or requirement, over the secondary access may be reduced).

[0162] The SMF may use this indication to determine a GBR scaling factor for the secondary access. The SMF may use the indication to determine a new GBR specification (e.g., requirement) for the secondary access. The SMF may provide this information to the RAN node. For example, the SMF may provide the information as part of a modified QoS profile (e.g., included in N2 SM information). The SMF may provide a value for the GBR parameter (e.g., specification or requirement) over the secondary access RAN node.

[0163] The secondary access RAN node may use the provided information. For example, the secondary access node may scale the GBR parameter (e.g., specification or requirement) for the QoS flow (e.g., reducing the GBR specification according to the scaling factor).

[0164] The duplication information may be sent to the SMF. The SMF may forward the information to the RAN node. The information may be provided (e.g., directly) from the WTRU and / or UPF to the RAN node. The WTRU may use an RRC measurement report. The UPF may provide the information in a GTP-U header of DL PDUs or in a GTP control plane PDU.

[0165] The primary access may be changed. For example, if the first access node is a primary access node, and the second access node is a secondary access node, the network node (e.g., SMF) may determine to change the second access node to the primary access node and the first access node to the secondary access node.

[0166] The RAN node may determine that the GBR parameter (e.g., specification or requirement) is not being met. For example, the SMF may enable QoS notification control (QNC) for a GBR QoS flow (e.g., based on the PCC rule from the SMF). QNC operation may allow a RAN node to send an asynchronous QoS Notificationcontrol — an unfulfilled event to the access and mobility management function (AMF) (e.g., if the RAN node can no longer guarantee the QoS parameters or specifications of a GBR QoS flow). The network node may determine to change the second access node to the primary access node and thefirst access node to the secondary access node based on the first access node failing to satisfy a guaranteed bit rate threshold. For example, the first node (e.g., RAN node) may not be able to guarantee the QoS parameters (e.g., specifications or requirements) because of resource capacity demanded by other higher priority GBR QoS flows. The AMF may inform the SMF that the QoS parameters (e.g., specifications or requirements) are not being met. The QNC may be used to swap the primary access and secondary access.

[0167] The SMF may enable QNC for a GBR QoS flow. The QNC may be enabled for the access RAN node, the secondary access RAN node, or both primary and secondary access nodes.

[0168] If requested (e.g., by the SMF), the RAN node may monitor whether the GBR parameter (e.g., specification or requirement) may be met. If the parameter (e.g., requirement or specification) cannot be met, the RAN node may notify the SMF.

[0169] The SMF may use the QNC information from the primary access and / or secondary access to swap the primary access and secondary access. For example, the SMF may swap the accesses if the primary access RAN node cannot meet the GBR parameter (e.g., specification or requirement) of the QoS flow. The SMF may swap the accesses if the secondary access RAN node may meet the GBR parameters (e.g., specification or requirement) of the QoS flow. The SMF may swap the accesses if the primary access may not meet the GBR parameter (e.g., specification or requirement) of the QoS flow and the secondary access RAN node may meet the GBR parameter (e.g., specification or requirement) of the QoS flow.

[0170] If an SMF determines to swap the primary access and secondary access, the SMF may send updated ATSSS rules to the WTRU and / or updated N4 rules to the UPF. The SMF may send modified QoS profiles to the primary and secondary access RAN nodes.

[0171] Although features and elements described above are described in particular combinations, each feature or element may be used alone without the other features and elements of the preferred embodiments, or in various combinations with or without other features and elements.

[0172] Although the implementations described herein may consider 3GPP specific protocols, it is understood that the implementations described herein are not restricted to this scenario and may be applicable to other wireless systems. For example, although the solutions described herein consider LTE, LTE-A, New Radio (NR) or 5G specific protocols, it is understood that the solutions described herein are not restricted to this scenario and are applicable to other wireless systems as well.

[0173] The processes described above may be implemented in a computer program, software, and / or firmware incorporated in a computer-readable medium for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted over wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, a read only memory (ROM), a random access memory (RAM), a register, cache memory, semiconductor memory devices, magnetic media such as, but not limited to, internal hard disks and removable disks, magneto-optical media, and / or optical media such as compact disc (CD)-ROM disks, and / or digital versatile disks (DVDs). A processor in association with software may be used to implement a radio frequency transceiver for use in a WTRU, terminal, base station, RNC, and / or any host computer.

[0174] It is understood that the entities performing the processes described herein may be logical entities that may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of, and executing on a processor of, a mobile device, network node or computer system. That is, the processes may be implemented in the form of software (e.g., computer-executable instructions) stored in a memory of a mobile device and / or network node, such as the node or computer system, which computer executable instructions, when executed by a processor of the node, perform the processes discussed. It is also understood that any transmitting and receiving processes illustrated in figures may be performed by communication circuitry of the node under control of the processor of the node and the computer-executable instructions (e.g., software) that it executes.

[0175] The various techniques described herein may be implemented in connection with hardware or software or, where appropriate, with a combination of both. Thus, the implementations and apparatus of the subject matter described herein, or certain aspects or portions thereof, may take the form of program code (e.g., instructions) embodied in tangible media including any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the subject matter described herein. In the case where program code is stored on media, it may be the case that the program code in question is stored on one or more media that collectively perform the actions in question, which is to say that the one or more media taken together contain code to perform the actions, but that - in the case where there is more than one single medium - there is no requirement that any particular part of the code be stored on any particular medium. In the case of program code execution on programmable devices, the computing device generally includes a processor, a storage medium readable by the processor (including volatile and non-volatile memory and / or storage elements), at least one input device, and at least one output device. One or more programs that may implement or utilize the processes described in connection with the subject matter described herein, e.g., through the use of an API, reusable controls, or the like. Such programs are preferably implemented in a high-level procedural or object-oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly ormachine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

[0176] Although example embodiments may refer to utilizing aspects of the subject matter described herein in the context of one or more stand-alone computing systems, the subject matter described herein is not so limited, but rather may be implemented in connection with any computing environment, such as a network or distributed computing environment. Still further, aspects of the subject matter described herein may be implemented in or across a plurality of processing chips or devices, and storage may similarly be affected across a plurality of devices. Such devices might include personal computers, network servers, handheld devices, supercomputers, or computers integrated into other systems such as automobiles and airplanes.

[0177] In describing preferred embodiments of the subject matter of the present disclosure, as illustrated in the Figures, specific terminology is employed for the sake of clarity. The claimed subject matter, however, is not intended to be limited to the specific terminology so selected, and it is to be understood that each specific element includes all technical equivalents that operate in a similar manner to accomplish a similar purpose.

Claims

CLAIMSWhat is Claimed:1 . A network node comprising: a processor, wherein the processor is configured to: receive a first message from a device, wherein the first message indicates a transition of a redundant steering mode (RSM) from a first state to a second state and a duration of time that the RSM will remain in the second state, wherein, in the first state, the device sends transmissions via a first access node and a second access node, and in the second state, the device sends transmissions via only the first access node; determine a change to a guaranteed bit rate condition of the second access node; and in response to the first message, send a second message to the second access node, wherein the second message indicates the change to the guaranteed bit rate condition of the second access node.

2. The network node of claim 1 , wherein the duration of time is a first duration of time, the change is a first change, and the processor is further configured to: receive a third message from the device, wherein the third message indicates a transition of the RSM from the second state to the first state and a second duration of time that the RSM will remain in the first state; determine a second change to the guaranteed bit rate condition of the second access node; and in response to the third message, send a fourth message to the second access node, wherein the fourth message indicates at least one of the transition of the RSM from the second state to the first state, the second change to the guaranteed bit rate condition of the second access node, or the second duration of time.

3. The network node of claim 1 , wherein the processor is further configured to: while in the first state, receive, from the device, duplication information that indicates a percentage of total traffic that is duplicated over the first access node and the second access node.

4. The network node of claim 3, wherein the processor being configured to determine the change to the guaranteed bit rate condition of the second access node comprises the processor being configured to determine a guaranteed bit rate scaling factor based on the percentage, and the processor is further configured to send the guaranteed bit rate scaling factor to the second access node.

5. The network node of claim 1 , wherein the processor being configured to determine the change to the guaranteed bit rate condition of the second access node comprises the processor being configured to: determine a guaranteed bit rate scaling factor based on the transition from the first state to the second state; and scale the guaranteed bit rate condition based on the guaranteed bit rate scaling factor.

6. The network node of claim 1 , wherein the second message further indicates at least one of the transition of the RSM from the first state to the second state, or the duration of time.

7. The network node of claim 1 , wherein the guaranteed bit rate condition is associated with at least one of a duplication rate at the second access node, a duplication status at the second access node, or a bit rate measurement at the second access node.

8. The network node of claim 1 , wherein the first access node is a primary access node, the second access node is a secondary access node, and the processor is further configured to determine to change the second access node to the primary access node and the first access node to the secondary access node.

9. The network node of claim 8, wherein the processor being configured to determine to change the second access node to the primary access node and the first access node to the secondary access node comprises the processor being configured to determine to change the second access node to the primary access node and the first access node to the secondary access node based on the first access node failing to satisfy a guaranteed bit rate threshold.

10. A method, performed by a network node, the method comprising: receiving a first message from a device, wherein the first message indicates a transition of a redundant steering mode (RSM) from a first state to a second state and a duration of timethat the RSM will remain in the second state, wherein, in the first state, the device sends transmissions via a first access node and a second access node, and in the second state, the device sends transmissions via only the first access node; determining a change to a guaranteed bit rate condition of the second access node; and in response to the first message, sending a second message to the second access node, wherein the second message indicates the change to the guaranteed bit rate condition of the second access node.11 . The method of claim 10, wherein the duration of time is a first duration of time, the change is a first change, and the method further comprises: receiving a third message from the device, wherein the third message indicates a transition of the RSM from the second state to the first state and a second duration of time that the RSM will remain in the first state; determining a second change to the guaranteed bit rate condition of the second access node; and in response to the third message, sending a fourth message to the second access node, wherein the fourth message indicates at least one of the transition of the RSM from the second state to the first state, the second change to the guaranteed bit rate condition of the second access node, or the second duration of time.

12. The method of claim 10, wherein the method further comprise: while in the first state, receiving, from the device, duplication information that indicates a percentage of total traffic that is duplicated over the first access node and the second access node.

13. The method of claim 12, wherein determining the change to the guaranteed bit rate condition of the second access node comprises determining a guaranteed bit rate scaling factor based on the percentage, and the method further comprises sending the guaranteed bit rate scaling factor to the second access node.

14. The method of claim 10, wherein determining the change to the guaranteed bit rate condition of the second access node comprises: determining a guaranteed bit rate scaling factor based on the transition from the first state to the second state; and scaling the guaranteed bit rate condition based on the guaranteed bit rate scaling factor.

15. The method of claim 10, wherein the second message further indicates at least one of the transition of the RSM from the first state to the second state, or the duration of time.

16. The method of claim 10, wherein the guaranteed bit rate condition is associated with at least one of a duplication rate at the second access node, a duplication status at the second access node, or a bit rate measurement at the second access node.

17. The method of claim 10, wherein the first access node is a primary access node, the second access node is a secondary access node, and the method further comprises determining to change the second access node to the primary access node and the first access node to the secondary access node.

18. The method of claim 17, wherein determining to change the second access node to the primary access node and the first access node to the secondary access node comprises determining to change the second access node to the primary access node and the first access node to the secondary access node based on the first access node failing to satisfy a guaranteed bit rate threshold.

Images