Systems and methods associated with redundant boot mode and pause for traffic replication

Abstract

Systems, methods, and tools associated with service replication pause are disclosed herein. A wireless transmit / receive unit (WTRU) may receive configuration information about traffic replication pause from a first network node. The WTRU may also receive a request message from a second network node, wherein the request message may indicate a request to suspend traffic replication. The WTRU may determine to at least partially suspend replication traffic in a first access branch of the WTRU based on the configuration information received from the first network node, the request message received from the second network node, and a condition at the WTRU. The WTRU may send a response message to the second network node, where the response message may indicate that traffic replication (e.g., at least in part) is suspended in the first access branch.

Description

[0001] Cross-reference to related applications

[0002] This application claims priority to provisional U.S. patent application 63 / 457,667, filed April 6, 2023, the disclosure of which is incorporated herein by reference in its entirety. Background Technology

[0003] Mobile communications using wireless communication continue to evolve. The fifth-generation mobile radio access technology (RAT) can be referred to as 5G New Radio (NR). Previous (traditional) generations of mobile communication RATs could be, for example, fourth-generation (4G) Long Term Evolution (LTE). Summary of the Invention

[0004] This document discloses systems, methods, and tools associated with service replication suspension. The Wireless Transmit / Receive Unit (WTRU) described herein can receive configuration information regarding service replication suspension from a first network node. The WTRU can also receive a request message from a second network node, wherein the request message may indicate a request to suspend service replication. The WTRU can determine, based on the configuration information received from the first network node, the request message received from the second network node, and conditions at the WTRU, to at least partially suspend replication service in a first access tributary of the WTRU. The WTRU can send a response message to the second network node, wherein the response message may indicate that service replication (e.g., at least partially) is suspended in the first access tributary.

[0005] In the example, the conditions at the WTRU may be associated with at least one of the following: the WTRU's power consumption, the frequency used by the WTRU, the connection type associated with the first or second access tributary, and the performance metric associated with the first or second access tributary. In the example, the response message sent to the second network node may also indicate the duration or period of the service replication pause in the first access tributary. In the example, the response message sent to the second network node may also indicate that the WTRU can use the second access tributary to transmit or receive services (e.g., data and / or control information) while service replication in the first access tributary is paused.

[0006] In the example, the WTRU can enter a power-saving mode (e.g., for a suspended access tributary) in response to a request message received from a second network node. In the example, the request message received from the second network node can indicate the duration or period of the service replication pause, the access tributary to be used during the service replication pause, or the bootstrapping mode to be used during the service replication pause. In the example, the request message received from the second network node can indicate exemption from one or more Service Data Streams (SDFs) for service replication pause, in which case the WTRU can continue replicating the service associated with one or more exempted SDFs in the first access tributary.

[0007] In the example, the first access tributary described herein may be associated with either a cellular or non-cellular network, and when service replication is suspended in the first access tributary, the WTRU may perform the transmission or reception of services (e.g., data and / or control information) in a second access tributary, which may be associated with the other of the cellular or non-cellular networks. In the example, service replication suspension may be associated with a Multi-Access Protocol Data Unit (MIU) session. In the example, configuration information may be received as part of Access Service Bootstrapping, Handover, and Split (ATSSS) rules. Attached Figure Description

[0008] Figure 1A This is a system diagram illustrating an exemplary communication system that can implement one or more of the disclosed embodiments.

[0009] Figure 1B It is shown that, according to the embodiment, it is possible to Figure 1A A system diagram of an exemplary wireless transmit / receive unit (WTRU) used within the communication system shown.

[0010] Figure 1C It is shown that, according to the embodiment, it is possible to Figure 1A The diagram shows an exemplary radio access network (RAN) and an exemplary core network (CN) used within the communication system.

[0011] Figure 1D It is shown that, according to the embodiment, it is possible to Figure 1A The system diagram shows another exemplary RAN and another exemplary CN used within the communication system shown.

[0012] Figure 2 This is a system diagram showing WTRUs with 3GPP access and non-3GPP access.

[0013] Figure 3 This is another system diagram showing a WTRU with 3GPP access and non-3GPP access.

[0014] Figure 4 This is a system diagram associated with Redundant Boot Mode (RSM).

[0015] Figure 5A This is a diagram illustrating an exemplary process associated with suspending business replication.

[0016] Figure 5B This is a diagram illustrating another exemplary process associated with suspending service replication based on CDRX configuration information.

[0017] Figure 6 This is a diagram illustrating an example of the replication performance management function (PMF) signaling.

[0018] Figure 7 This is a diagram illustrating an example of an access tributary being activated due to an event at the WTRU (e.g., the WTRU losing connection).

[0019] Figure 8 This is a diagram illustrating an example process associated with a serving cell on a WTRU change suspension access tributary. Detailed Implementation

[0020] Figure 1A This diagram illustrates an example communication system 100 in which one or more of the disclosed embodiments may be implemented. The communication system 100 may be a multiple access system that provides content such as voice, data, video, messaging, and broadcasting to multiple wireless users. The communication system 100 enables multiple wireless users to access such content by sharing system resources, including wireless bandwidth. For example, the communication system 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 Extended OFDM (ZT-UW DTS-s OFDM), Unique Word OFDM (UW-OFDM), Resource Block Filtered OFDM, Filter Bank Multicarrier (FBMC), etc.

[0021] like Figure 1AAs shown, the communication system 100 may include wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, RAN 104 / 113, CN 106 / 115, Public Switched Telephone Network (PSTN) 108, Internet 110, and other networks 112. However, it should be understood that the disclosed embodiments contemplate any number of WTRUs, base stations, networks, and / or network elements. Any of the WTRUs 102a, 102b, 102c, and 102d may be any type of device configured to operate and / or communicate in a wireless environment. For example, WTRUs 102a, 102b, 102c, and 102d (any of which may be referred to as a “station” and / or “STA”) may be configured to transmit and / or receive wireless signals and may include user equipment (UE), mobile stations, fixed or mobile subscriber units, subscription-based units, pagers, cellular phones, personal digital assistants (PDAs), smartphones, laptops, netbooks, personal computers, wireless sensors, hotspots or MiFi devices, Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated processing chain environments), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. Any of the wireless transmission / reception units 102a, 102b, 102c, and 102d may be interchangeably referred to as UEs.

[0022] The communication system 100 may also include base station 114a and / or base station 114b. Each of base stations 114a and 114b can be any type of device configured to wirelessly connect to at least one of WTRUs 102a, 102b, 102c, and 102d to facilitate access to one or more communication networks, such as CN 106 / 115, Internet 110, and / or other networks 112. As an example, base stations 114a and 114b may be base transceiver stations (BTS), NodeBs, eNodeBs, home NodeBs, home eNodeBs, gNBs, NRNodeBs, site controllers, access points (APs), wireless routers, etc. Although base stations 114a and 114b are each depicted as a single element, it will be understood that base stations 114a and 114b may include any number of interconnected base stations and / or network elements.

[0023] Base station 114a may be part of RAN 104 / 113, and may also include other base stations and / or network elements (not shown), such as base station controllers (BSCs), radio network controllers (RNCs), relay nodes, etc. Base station 114a and / or base station 114b may be configured to transmit and / or receive radio signals on one or more carrier frequencies, which may be referred to as cells (not shown). These frequencies may be in licensed spectrum, unlicensed spectrum, or a combination of licensed and unlicensed spectrum. A cell may provide coverage of a specific geographic area, which may be relatively fixed or may change over time. A cell may be further divided into cell sectors. For example, the cell associated with base station 114a may be divided into three sectors. Thus, in one embodiment, base station 114a may include three transceivers, i.e., one transceiver per sector of the cell. In one embodiment, base station 114a may employ multiple-input multiple-output (MIMO) technology and may use multiple transceivers for each sector of the cell. For example, beamforming may be used to transmit and / or receive signals in a desired spatial direction.

[0024] Base stations 114a and 114b can communicate with one or more of WTRUs 102a, 102b, 102c, and 102d via air interface 116, which can be any suitable wireless communication link (e.g., radio frequency (RF), microwave, centimeter wave, micrometer wave, infrared (IR), ultraviolet (UV), visible light, etc.). Air interface 116 can be established using any suitable radio access technology (RAT).

[0025] More specifically, as described above, the communication system 100 can be a multiple access system and can employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations 114a and WTRUs 102a, 102b, and 102c in RAN 104 / 113 can implement radio technologies such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which can use Wideband CDMA (WCDMA) to establish air interfaces 115 / 116 / 117. WCDMA can include communication protocols such as High-Speed ​​Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA can include High-Speed ​​Downlink (DL) Packet Access (HSDPA) and / or High-Speed ​​UL Packet Access (HSUPA).

[0026] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which can use Long Term Evolution (LTE) and / or LTE-A Advanced (LTE-A) and / or LTE-A Pro Advanced (LTE-A Pro) to establish air interface 116.

[0027] In one embodiment, base station 114a and WTRUs 102a, 102b, 102c can implement radio technologies such as NR radio access, which can use New Radio (NR) to establish air interface 116.

[0028] In one embodiment, base station 114a and WTRUs 102a, 102b, and 102c can implement multiple radio access technologies. For example, base station 114a and WTRUs 102a, 102b, and 102c can, for instance, use a dual connectivity (DC) principle to implement both LTE and NR radio access together. Therefore, the air interface used by WTRUs 102a, 102b, and 102c can be characterized by multiple types of radio access technologies and / or transmissions sent to / from multiple types of base stations (e.g., eNBs and gNBs).

[0029] In other embodiments, base station 114a and wireless transmission / reception units 102a, 102b, 102c may implement wireless technologies such as IEEE 802.11 (i.e., Wi-Fi), IEEE 802.16 (i.e., Global Microwave Access Interoperability (WiMAX)), CDMA 2000, CDMA 2000 1X, CDMA 2000 EV-DO, Provisional Standard 2000 (IS-2000), Provisional Standard 95 (IS-95), Provisional Standard 856 (IS-856), Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE), GSM EDGE (GERAN), etc.

[0030] Figure 1ABase station 114b can be, for example, a wireless router, a home NodeB, a home eNodeB, or an access point, and can utilize any suitable RAT to facilitate wireless connectivity in a local area, such as a business premises, home, vehicle, campus, industrial facility, air corridor (e.g., for drone use), road, etc. In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.11 to establish a wireless local area network (WLAN). In one embodiment, base station 114b and WTRUs 102c, 102d can implement radio technologies such as IEEE 802.15 to establish a wireless personal area network (WPAN). In yet another embodiment, base station 114b and WTRUs 102c, 102d can utilize cellular-based RATs (e.g., WCDMA, CDMA 2000, GSM, LTE-A, LTE-A Pro, NR, etc.) to establish picocells or femtocells. Figure 1A As shown, base station 114b can have a direct connection to Internet 110. Therefore, base station 114b does not need to access Internet 110 via CN 106 / 115.

[0031] RAN 104 / 113 can communicate with CN 106 / 115, which can be any type of network configured to provide voice, data, application, and / or Voice over Internet Protocol (VoIP) services to one or more of WTRUs 102a, 102b, 102c, and 102d. Data may have varying Quality of Service (QoS) requirements, such as different throughput requirements, latency requirements, fault tolerance requirements, reliability requirements, data throughput requirements, mobility requirements, etc. CN 106 / 115 can provide call control, billing services, location-based services, prepaid calling, internet connectivity, video distribution, etc., and / or perform advanced security functions (such as user authentication). Although in Figure 1A Although not shown, it should be understood that RAN 104 / 113 and / or CN 106 / 115 can communicate directly or indirectly with other RANs that use the same RAT as or a different RAT than RAN 104 / 113. For example, in addition to being connected to RAN 104 / 113, which can utilize NR radio technology, CN106 / 115 can also communicate with another RAN (not shown) that uses GSM, UMTS, CDMA 2000, WiMAX, E-UTRA, or WiFi radio technology.

[0032] CN 106 / 115 can also be used as a gateway for WTRU 102a, 102b, 102c, 102d to access PSTN 108, the Internet 110, and / or other networks 112. PSTN 108 may include a circuit-switched telephone network providing Common Old-Style Telephone Service (POTS). The Internet 110 may include a global system of interconnected computer networks and devices using common communication protocols, such as Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and / or Internet Protocol (IP) from the TCP / IP Internet Protocol suite. Network 112 may include wired and / or wireless communication networks owned and / or operated by other service providers. For example, network 112 may include another CN connected to one or more RANs, which may use the same RAT as RAN 104 / 113 or a different RAT.

[0033] Some or all of the WTRUs 102a, 102b, 102c, and 102d in the communication system 100 may include multi-mode capability (e.g., WTRUs 102a, 102b, 102c, and 102d may include multiple transceivers to communicate with different wireless networks via different wireless links). For example, Figure 1A The WTRU 102c shown can be configured to communicate with base station 114a, which can use cellular-based radio technology, and with base station 114b, which can use IEEE 802 radio technology.

[0034] Figure 1B This is a system diagram illustrating example WTRU 102. (See diagram below.) Figure 1B As shown, WTRU 102 may include a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keyboard 126, a display / touchpad 128, non-removable memory 130, removable memory 132, a power supply 134, a Global Positioning System (GPS) chipset 136, and / or other peripheral devices 138, etc. It is understood that WTRU 102 may include any sub-combination of the foregoing elements while remaining consistent with the embodiments.

[0035] Processor 118 may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), multiple microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. Processor 118 may perform signal decoding, data processing, power control, input / output processing, and / or any other functions that enable WTRU 102 to operate in a wireless environment. Processor 118 may be coupled to transceiver 120, and transceiver 120 may be coupled to transmitting / receiving element 122. Although Figure 1B While the processor 118 and transceiver 120 are depicted as separate components, it should be understood that the processor 118 and transceiver 120 may be integrated together in an electronic package or chip.

[0036] Transmitting / receiving element 122 can be configured to transmit signals to or receive signals from a base station (e.g., base station 114a) via air interface 116. For example, in one embodiment, transmitting / receiving element 122 can be an antenna configured to transmit and / or receive RF signals. In one embodiment, transmitting / receiving element 122 can be a transmitter / detector configured to transmit and / or receive, for example, IR, UV, or visible light signals. In yet another embodiment, transmitting / receiving element 122 can be configured to transmit and / or receive both RF and optical signals. It should be understood that transmitting / receiving element 122 can be configured to transmit and / or receive any combination of wireless signals.

[0037] Although the transmitting / receiving element 122 is in Figure 1B While described as a single element, WTRU 102 may include any number of transmitting / receiving elements 122. More specifically, WTRU 102 may use MIMO technology. Thus, in one embodiment, WTRU 102 may include two or more transmitting / receiving elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals via air interface 116.

[0038] Transceiver 120 can be configured to modulate signals transmitted by transmitting / receiving element 122 and demodulate signals received by transmitting / receiving element 122. As described above, WTRU 102 can have multimode capability. Therefore, transceiver 120 can include multiple transceivers to enable WTRU 102 to communicate via various RATs, such as NR and IEEE 802.11.

[0039] The processor 118 of WTRU 102 may be coupled to a speaker / microphone 124, a keyboard 126, and / or a display / touchpad 128 (e.g., a liquid crystal display (LCD) unit or an organic light-emitting diode (OLED) display unit) and may receive user input data therefrom. The processor 118 may also output user data to the speaker / microphone 124, keyboard 126, and / or display / touchpad 128. Additionally, the processor 118 may access information from any type of suitable memory and store data in said memory, such as non-removable memory 130 and / or removable memory 132. 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. Removable memory 132 may include a user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc. In other embodiments, the processor 118 may access information from memory that is not physically located on WTRU 102 and store data in said memory (e.g., located on a server or home computer (not shown)).

[0040] The processor 118 can receive power from the power supply 134 and can be configured to distribute and / or control power to other components in the WTRU 102. The power supply 134 can be any suitable device for powering the WTRU 102. For example, the power supply 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, etc.

[0041] 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) about the current location of the WTRU 102. In addition to, or alternatively to, the information from the GPS chipset 136, the WTRU 102 may receive location information from base stations (e.g., base stations 114a, 114b) via the air interface 116, and / or determine its location based on the timing of signals received from two or more neighboring base stations. It should be understood that the WTRU 102 may acquire location information using any suitable location determination method, while remaining consistent with the embodiments.

[0042] The processor 118 can also be coupled to other peripheral devices 138, which may include one or more software and / or hardware modules providing additional features, functions, and / or wired or wireless connectivity. For example, peripheral devices 138 may include accelerometers, electronic compasses, satellite transceivers, digital cameras (for photos and / or video), Universal Serial Bus (USB) ports, vibration devices, television transceivers, hands-free headsets, etc. Modules, FM radio units, digital music players, media players, video game player modules, internet browsers, virtual reality and / or augmented reality (VR / AR) devices, activity trackers, etc. Peripheral devices 138 may include one or more sensors, which may be one or more of the following: gyroscopes, accelerometers, Hall effect sensors, magnetometers, orientation sensors, proximity sensors, temperature sensors, time sensors; geolocation sensors; altimeters, light sensors, touch sensors, magnetometers, barometers, gesture sensors, biometric sensors, and / or humidity sensors.

[0043] WTRU 102 may include a full-duplex radio for which transmission and reception of some or all of the signals (e.g., signals associated with specific subframes for uplink (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 through hardware (e.g., chokes) or through signal processing by a processor (e.g., a separate processor (not shown) or processor 118). In one embodiment, WTRU 102 may include a half-duplex radio for which transmission and reception of some or all of the signals (e.g., signals associated with specific subframes for uplink (e.g., for transmission) or downlink (e.g., for reception)) may occur.

[0044] Figure 1C This is a system diagram illustrating RAN 104 and CN 106 according to an embodiment. As described above, RAN 104 may employ E-UTRA radio technology to communicate with WTRUs 102a, 102b, and 102c via air interface 116. RAN 104 may also communicate with CN 106.

[0045] RAN 104 may include eNode-Bs 160a, 160b, and 160c, but it should be understood that RAN 104 may include any number of eNode-Bs while remaining consistent with the embodiments. eNode-Bs 160a, 160b, and 160c may each include one or more transceivers to communicate with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Therefore, for example, eNode-B 160a may use multiple antennas to transmit and / or receive radio signals from WTRU 102a.

[0046] Each of the eNode-B 160a, 160b, and 160c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, etc. Figure 1C As shown, eNode-B 160a, 160b, and 160C can communicate with each other via the X2 interface.

[0047] Figure 1C The CN 106 shown 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 is depicted as part of the CN 106, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0048] The MME 162 can connect to each of the eNodes B160a, 160b, and 160c in RAN 104 via the S1 interface and can be used as a control node. For example, the MME 162 can be responsible for authenticating users of WTRUs 102a, 102b, and 102c, bearer activation / deactivation, selecting a specific serving gateway during the initial attachment of WTRUs 102a, 102b, and 102c, etc. The MME 162 can provide control plane functions for handover between RAN 104 and other RANs (not shown) employing other radio technologies (such as GSM and / or WCDMA).

[0049] The SGW 164 can connect to each of the eNode-Bs 160a, 160b, and 160c in RAN 104 via the S1 interface. The SGW 164 can typically route and forward user data packets to / from WTRUs 102a, 102b, and 102c. The SGW 164 can perform other functions, such as anchoring the user plane during handover between eNode Bs, triggering paging when DL data is available to WTRUs 102a, 102B, and 102c, managing and storing the context of WTRUs 102a, 102B, and 102c, etc.

[0050] The SGW 164 can connect to the PGW 166, which can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, 102c and IP-enabled devices.

[0051] CN 106 can facilitate communication with other networks. For example, CN 106 can provide WTRUs 102a, 102b, and 102c with access to a circuit-switched network (e.g., PSTN 108) to facilitate communication between WTRUs 102a, 102b, and 102c and traditional landline communication equipment. For example, CN 106 may include an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) or can communicate with an IP gateway that serves as an interface between CN 106 and PSTN 108. Furthermore, CN 106 can provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers.

[0052] Although WTRU is Figure 1A-1D While described as a wireless terminal, it is conceivable that in some representative embodiments, such a terminal may use a wired communication interface with a communication network (e.g., temporary or permanent).

[0053] In a representative embodiment, the other network 112 may be a WLAN.

[0054] A WLAN in Infrastructure Basic Services Set (BSS) mode can have an access point (AP) for the BSS and one or more stations (STAs) associated with the AP. The AP can have access or interfaces to a distributed system (DS) or another type of wired / wireless network carrying traffic entering and / or leaving the BSS. Traffic originating outside the BSS destined for a STA can be delivered to the STA via the AP. Traffic originating from a STA destined for a destination outside the BSS can be sent to the AP for delivery to the appropriate destination. Traffic between STAs within the BSS can be sent via the AP, for example, where a source STA can send traffic to the AP, and the AP can deliver the traffic to the destination STA. Traffic between STAs within the BSS can be considered and / or referred to as peer-to-peer traffic. This peer-to-peer traffic can be sent between the source and destination STAs (e.g., directly between the source and destination STAs) using a direct link setup (DLS). In some representative embodiments, the DLS can use 802.11e DLS or 802.11z Tunneled DLS (TDLS). WLANs using the Standalone BSS (IBSS) mode cannot have access points (APs), and STAs within the IBSS or using the IBSS (e.g., all STAs) can communicate directly with each other. The IBSS communication mode may sometimes be referred to as the "ad-hoc" communication mode in this document.

[0055] When using 802.11ac infrastructure operating mode or a similar operating mode, the AP can transmit beacons on a fixed channel, such as the primary channel. The primary channel can be of fixed width (e.g., a bandwidth of 20 MHz) or dynamically set via signaling. The primary channel can be the operating channel of the BSS and can be used by the STA to establish a connection with the AP. In some representative embodiments, such as in an 802.11 system, Carrier Sense Multiple Access (CSMA / CA) with collision avoidance can be implemented. For CSMA / CA, STAs including the AP (e.g., each STA) can listen on the primary channel. If the primary channel is listened to / detected and / or determined to be busy by a particular STA, that particular STA can back off. A single STA (e.g., only one station) can transmit at any given time within a given BSS.

[0056] High-throughput (HT) STAs can communicate using a 40MHz wide channel, for example, by combining a primary 20MHz channel with adjacent or non-adjacent 20MHz channels to form a 40MHz wide channel.

[0057] Very High Throughput (VHT) STAs can support channels with widths of 20MHz, 40MHz, 80MHz, and / or 160MHz. 40MHz and / or 80MHz channels can be formed by combining consecutive 20MHz channels. A 160MHz channel can be formed by combining eight consecutive 20MHz channels, or by combining two non-consecutive 80MHz channels; this can be referred to as an 80+80 configuration. For the 80+80 configuration, after channel coding, the data can pass through a segmented parser that divides the data into two streams. Each stream can be processed separately using Inverse Fast Fourier Transform (IFFT) and time-domain processing. The streams can be mapped onto the two 80MHz channels, and the data can be transmitted by the transmitting STA. At the receiver of the receiving STA, the operation of the 80+80 configuration can be reversed, and the combined data can be sent to the Media Access Control (MAC).

[0058] Operating modes below 1 GHz are supported by 802.11af and 802.11ah. The channel operating bandwidth and carrier in 802.11af and 802.11ah are reduced compared to those used in 802.11n and 802.11ac. 802.11af supports 5 MHz, 10 MHz, and 20 MHz bandwidths in the TV whitespace (TVWS) spectrum, while 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.11ah can support instrument-type control / machine-type communications, such as MTC devices in macro coverage areas. MTC devices may have certain capabilities, such as limited capabilities including support for certain and / or limited bandwidths (e.g., only support). MTC devices may include batteries with a battery life exceeding a threshold (e.g., to maintain a very long battery life).

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

[0060] In the United States, the available frequency bands for 802.11ah are from 902MHz to 928MHz. In South Korea, the available frequency bands are from 917.5MHz to 923.5MHz. In Japan, the available frequency bands are from 916.5MHz to 927.5MHz. The total bandwidth available for 802.11ah is 6MHz to 26MHz, depending on the country code.

[0061] Figure 1DThis is a system diagram illustrating RAN 113 and CN 115 according to an embodiment. As described above, RAN 113 can communicate with WTRUs 102a, 102b, and 102c via air interface 116 using NR wireless technology. RAN 113 can also communicate with CN 115.

[0062] RAN 113 may include gNBs 180a, 180b, and 180c; however, it should be understood that RAN 113 may include any number of gNBs while remaining consistent with the embodiments. Each of gNBs 180a, 180b, and 180c includes one or more transceivers for communicating with WTRUs 102a, 102b, and 102c via air interface 116. In one embodiment, gNBs 180a, 180b, and 180c may implement MIMO technology. For example, gNBs 180a and 180b may utilize beamforming to transmit signals to and / or receive signals from gNBs 180a, 180b, and 180c. Therefore, gNB 180a may, for example, use multiple antennas to transmit radio signals to and / or receive radio signals from WTRU 102a. In one embodiment, gNBs 180a, 180b, and 180c may implement carrier aggregation technology. For example, gNB 180a can transmit multiple component carriers to 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 one embodiment, gNBs 180a, 180b, and 180c may implement Cooperative Multipoint (CoMP) technology. For example, WTRU 102a may receive coordinated transmissions from gNBs 180a and 180b (and / or gNB 180c).

[0063] WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using transmissions associated with Scalable Digital Numerology (SDN). For example, OFDM symbol spacing and / or OFDM subcarrier spacing can vary for different transmissions, different cells, and / or different portions of the radio transmission spectrum. WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using subframes or Transmission Time Intervals (TTIs) of varying lengths or scalable lengths (e.g., containing different numbers of OFDM symbols and / or continuously varying lengths of absolute time).

[0064] gNBs 180a, 180b, and 180c can be configured to communicate with WTRUs 102a, 102b, and 102c in standalone and / or non-standalone configurations. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c without needing to access other RANs (e.g., eNode-Bs 160a, 160b, and 160c). In standalone configuration, WTRUs 102a, 102b, and 102c can utilize one or more of gNBs 180a, 180b, and 180c as mobility anchors. In standalone configuration, WTRUs 102a, 102b, and 102c can communicate with gNBs 180a, 180b, and 180c using signals in unlicensed frequency bands. In a non-standalone configuration, WTRUs 102a, 102b, and 102c can communicate / connect with gNBs 180a, 180b, and 180c, and also with another RAN (such as eNode-Bs 160a, 160b, and 160c). For example, WTRUs 102a, 102b, and 102c can implement DC principles to communicate essentially simultaneously with one or more gNBs 180a, 180b, and 180c, as well as one or more eNode-Bs 160a, 160b, and 160c. In a non-standalone configuration, eNode-Bs 160a, 160b, and 160c can serve as mobility anchors for WTRUs 102a, 102b, and 102c, while gNBs 180a, 180b, and 180c can provide additional coverage and / or throughput for serving WTRUs 102a, 102b, and 102c.

[0065] Each of gNBs 180a, 180b, and 180c can be associated with a specific cell (not shown) and can be configured to handle radio resource management decisions, handover decisions, user scheduling in UL and / or DL, network fragmentation support, dual connectivity, interoperability between NR and E-UTRA, routing of user plane data to User Plane Functions (UPF) 184a and 184b, routing of control plane information to Access and Mobility Management Functions (AMF) 182a and 182b, etc. Figure 1D As shown, gNB 180a, 180b, and 180c can communicate with each other via the Xn interface.

[0066] Figure 1DThe CN 115 shown may include at least one AMF 182a, 182b, at least one UPF 184a, 184b, at least one Session Management Function (SMF) 183a, 183b, and may include data networks (DN) 185a, 185b. While each of the foregoing elements is depicted as part of the CN 115, it should be understood that any of these elements may be owned and / or operated by an entity other than the CN operator.

[0067] AMF 182a and 182b can connect to one or more of gNBs 180a, 180b, and 180c in RAN 113 via the N2 interface and can act as control nodes. For example, AMF 182a and 182b can be responsible for authenticating users of WTRU 102a, 102b, and 102c, supporting network slicing (e.g., handling different PDU sessions with different needs), selecting specific SMF 183a and 183b, managing registration areas, terminating NAS signaling, mobility management, and so on. AMF 182a and 182b can use network slicing to customize CN support for WTRU 102a, 102b, and 102c based on the type of service being used by WTRU 102a, 102b, and 102c. For example, different network slices can 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, and services for Machine Type Communication (MTC) access. AMF 162 can provide control plane functions for handover between RAN 113 and other RANs (not shown) employing other radio technologies (such as LTE, LTE-A, LTE-A Pro and / or non-3GPP access technologies (such as WiFi)).

[0068] SMFs 183a and 183b can connect to AMFs 182a and 182b in CN 115 via the N11 interface. SMFs 183a and 183b can also connect to UPFs 184a and 184b in CN 115 via the N4 interface. SMFs 183a and 183b can select and control UPFs 184a and 184b, and configure them to route traffic through UPFs 184a and 184b. SMFs 183a and 183b can perform other functions, such as managing and allocating UE IP addresses, managing PDU sessions, controlling policy enforcement and QoS, and providing downlink data notifications. PDU session types can be IP-based, non-IP-based, Ethernet-based, etc.

[0069] UPF 184a and 184b can connect to one or more of gNB 180a, 180b, and 180c in RAN 113 via the N3 interface. The N3 interface can provide WTRU 102a, 102b, and 102c with access to packet-switched networks (such as Internet 110) to facilitate communication between WTRU 102a, 102b, and 102c and IP-enabled devices. UPF 184 and 184b can 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, and providing mobility anchoring.

[0070] CN 115 can facilitate communication with other networks. For example, CN 115 may include, or communicate with, an IP gateway (e.g., an IP Multimedia Subsystem (IMS) server) serving as an interface between CN 115 and PSTN 108. Furthermore, CN 115 may provide WTRUs 102a, 102b, and 102c with access to other networks 112, which may include other wired and / or wireless networks owned and / or operated by other service providers. In one embodiment, WTRUs 102a, 102b, and 102c may be connected to DN 185a and 185b via UPF 184a and 184b through the N3 interface to UPF 184a and 184b and the N6 interface between UPF 184a and 184b and local data networks (DNs) 185a and 185b.

[0071] Given Figure 1A-1D and Figure 1A-1D As described herein, one or more of the functions described with respect to one or more of the following can be performed by one or more emulation devices (not shown): WTRU 102a-d, base station 114a-b, eNode-B 160a-c, MME 162, SGW 164, PGW 166, gNB 180a-c, AMF 182a-b, UPF184a-b, SMF 183a-b, DN 185a-b, and / or any other device described herein. An emulation device can be one or more devices configured to emulate one or more of the functions described herein. For example, an emulation device can be used to test other devices and / or simulate network and / or WTRU functions.

[0072] Simulation devices can be designed to perform one or more tests on other devices in laboratory and / or carrier network environments. For example, one or more simulation devices may perform one or more functions while being fully or partially implemented and / or deployed as part of a wired and / or wireless communication network to test other devices within the communication network. The one or more simulation devices may perform one or more or all functions while being temporarily implemented / deployed as part of a wired and / or wireless communication network. Simulation devices may be directly coupled to another device for testing purposes and / or may use over-the-air wireless communication to perform tests.

[0073] One or more simulation devices can perform one or more functions (including all functions) without being implemented / deployed as part of a wired and / or wireless communication network. For example, simulation devices can be used in test scenarios within a test laboratory and / or an undeployed (e.g., tested) wired and / or wireless communication network to perform testing of one or more components. One or more simulation devices can be test equipment. Simulation devices can transmit and / or receive data using direct RF coupling and / or wireless communication via RF circuitry (e.g., which may include one or more antennas).

[0074] In this article, the term "timer" can refer to time, time period, time tracking, time period tracking, or combinations thereof. The term "timer expiration" can refer to the determination that a specific time has occurred or that a specific time period has expired.

[0075] The following abbreviations and acronyms may be used in this article:

[0076] AN access node

[0077] AMF Access and Mobility Management Functions

[0078] ATSSS access service guidance, switching, and splitting

[0079] ATSSS-LL ATSSS Low Level

[0080] CDRX connection mode discontinuous reception

[0081] CE control elements

[0082] DCI Downlink Control Information

[0083] DL downlink

[0084] DN Data Network

[0085] EPTI Extended Procedure Transaction Identifier

[0086] GBR guarantees bit rate gNB Next Generation Node B

[0087] HPLMN belongs to PLMN

[0088] IP Internet Protocol

[0089] LTE Long Term Evolution

[0090] MAC Media Access Control

[0091] MA-PDU (Multi-access PDU) MP-DCCP Multipath Datagram Congestion Control Protocol

[0092] MPTCP Multipath TCP

[0093] MP-TCP Multipath Transmission Control Protocol

[0094] NAS Non-Access Layer

[0095] NR New Radio

[0096] PCC Policy and Billing Control

[0097] PCF policy control function

[0098] PDU Protocol Data Unit

[0099] PLMN Public Land Mobile Network

[0100] PLR packet loss rate

[0101] PMF performance management functions

[0102] PSA PDU Session Anchor

[0103] QoE (Quality of Experience)

[0104] QoS (Quality of Service)

[0105] RAN (Radio Access Network)

[0106] RAT Radio Access Technology

[0107] RI Request Identifier

[0108] RF (Radio Frequency)

[0109] RRC (Radio Resource Control)

[0110] RTT round trip delay

[0111] SDF Service Data Flow

[0112] SM Session Management

[0113] SMF Session Management Function

[0114] TCP Transmission Control Protocol

[0115] UDP User Datagram Protocol

[0116] UE User Equipment

[0117] UL uplink

[0118] UPF User Plane Functions

[0119] VPLMN visits public terrestrial mobile networks

[0120] A Wireless Transmit / Receive Unit (WTRU) may support Multiple Access Protocol Data Unit (MA PDU) sessions, MA PDU transports, and / or Redundancy Boot Mode (RSM). The WTRU may include a processor. The WTRU may receive a first message from a first network node (e.g., a RAN node or PCF), where the first message may include one or more ATSSS rules and / or configuration information. In the example, one or more ATSSS rules may be provided as part of the configuration information, or vice versa. The configuration information may indicate the access to be used (e.g., an access tributary) when service replication is suspended. The WTRU may receive request messages (e.g., Performance Management Function (PMF) request messages) from a second network node (e.g., a UPF). The request message may indicate a request to suspend service replication. The WTRU may determine the access tributary associated with the service replication suspension based on the first message received from the first network node, the request message received from the second network node, and / or conditions associated with the WTRU. The WTRU may send a response message (e.g., a PMF response message) to the second network node. The response message may indicate a request for the WTRU to enter a power-saving mode (e.g., for the determined access tributary).

[0121] When mentioned in this article, service replication suspension can be associated with a specific service data flow (SDF). For example, when two access tributaries or access networks are available for transmitting and / or receiving services and service replication is enabled, services associated with an SDF can be replicated between the two access tributaries. In such an example, service replication suspension could mean transmitting or receiving services associated with an SDF on one of the two access tributaries, while stopping the replication of services on the other access tributary.

[0122] When referred to herein, a PMF message can be a control plane message that can be transmitted or received on the user plane. PMF messages can be carried in data radio bearers to RAN nodes and / or in user plane tunnels between RAN nodes and network devices such as UPFs.

[0123] In the example, the configuration information may indicate instructions for operation when service replication is suspended (e.g., at least partially), the duration of the service replication suspension, and at least one of the SDF list exempting the service replication suspension. In one example, the second network node may provide User Plane Function (UPF). In the example, the request message may also indicate the second access (e.g., a second access tributary) to use when service replication is suspended (e.g., at least partially), the duration of the service replication suspension, the time indicating when service replication is suspended, the direction of the suspension (e.g., uplink or downlink), and at least one of the SDF list exempting the service replication suspension. In one example, the conditions used by the WTRU to make decisions associated with service replication suspension may include at least one of power level, operating frequency, and link performance.

[0124] In one example, a first network node (e.g., a UPF) may support MA PDU sessions or transport and / or redundant bootstrapping mode (RSM). The first network node may include a processor. The first network node may receive a first message from a second network node (e.g., a PCF), where the first message may include one or more N4 rules and / or configuration information regarding service replication suspension. For example, the configuration information may indicate the access (e.g., an access tributary) to be used when service replication is suspended. The first network device (e.g., the UPF) may receive an indication to suspend service replication from a third network node (e.g., a RAN node and PDU session anchor UPF (PSF-UPF), an SMF, or an intermediate UPF between RAN nodes (I-UPF)). The second network node may determine that service replication is suspended based on the received indication. The second network node may send a request message (e.g., a PMF request message) to the WTRU. The request message may indicate a request to suspend service replication and may indicate the access (e.g., an access tributary) to be used when service replication is suspended. The second network node may receive a response message (e.g., a PMF response message) from the WTRU. The response message may indicate the WTRU's request to enter power-saving mode based on the access tributary.

[0125] The configuration information described in the above examples may also indicate instructions for operation when service replication is suspended (e.g., at least partially), the duration of the service replication suspension, and at least one of the SDF exemption list. The request message (e.g., PMF request message) described in the above examples may also indicate instructions for operation when service replication is suspended, the duration of the service replication suspension, and at least one of the SDF exemption list. The second network node (e.g., UPF) described in the above examples may determine to suspend downlink replication on the access tributary based on a received response message (e.g., PMF response message). The second network node may send a message to a fourth network node (e.g., RAN node) to indicate that the access tributary has been suspended.

[0126] In one example, the WTRU may support an MA PDU session or transport. The WTRU may include a processor. The WTRU may receive configuration information for PMF signaling (e.g., via one or more ATSSS rules). The WTRU may generate a PMF message and send it to a network node (e.g., a UPF). The PMF message may include an indication (e.g., bit fields) that the PMF message is the first (e.g., initial) PMF message transmission. The WTRU may determine the access tributary for sending the PMF message and may use that access tributary to send the PMF message to the network node.

[0127] In the above example, the configuration information may indicate at least one of PMF transmission information for sending PMF messages and PMF retransmission information for sending retransmissions of PMF messages. The access tributary in the above example may be determined based on a bootstrapping mode (e.g., bootstrapping mode rules). The WTRU may also determine that a PMF message should be retransmitted and may modify the PMF message to indicate that the PMF message is being retransmitted. In some cases, the WTRU may use a first access tributary for the first (e.g., initial) PMF message transmission and a second access tributary for the retransmission of PMF messages. The second access tributary may be determined based on a bootstrapping mode (e.g., bootstrapping mode rules). In some cases, the WTRU may send a message to a network node (e.g., an SMF) that may include notification that the PMF message has been retransmitted a maximum of times.

[0128] In the example, the WTRU may support MA PDU sessions or transports, and / or Redundant Bootstrapping Mode (RSM). The WTRU may include a processor. The WTRU may establish an MA PDU session with a network node (e.g., a UPF). The MA PDU session may be an MA PDU session with Redundant Bootstrapping Mode. The WTRU may receive request messages (e.g., PMF request messages) from the network node. A PMF request message may indicate a request to suspend service replication, based on which the WTRU may suspend data transmission or data reception on a first access tributary. The WTRU may then determine to resume service replication (e.g., so that the WTRU can use the suspended access tributary to send uplink transports). The WTRU may send a recovery request message (e.g., a PMF recovery request message) to the network node. The recovery request message may indicate the reason for the request. The WTRU may receive recovery response messages (e.g., PMF recovery response messages) from the network node.

[0129] In the above example, the determination to resume service replication (e.g., sending uplink transmissions using the suspended access tributary) can be based on at least one of the following: loss of connectivity to the active access tributary (e.g., a second access tributary used by the WTRU for data transmission or data reception when service replication is suspended), performance measurements or metrics based on the active access tributary, and / or the start of the Service Data Stream (SDF). In the above example, the recovery request message can also indicate the time for resuming service replication (e.g., the time for performing transmissions using the suspended access tributary). In the above example, the recovery response message can indicate at least one of the following: an instruction to use the active access tributary (e.g., the second access tributary), an instruction to use the suspended access tributary (e.g., the first access tributary), and an instruction to use both the active and suspended access tributaries. In response to receiving the recovery response message, the WTRU can use the active access tributary, the suspended access tributary, or both the active and suspended access tributaries to perform uplink transmissions.

[0130] In one example, the WTRU may support MA PDU sessions or transports, and / or Redundant Bootstrap Mode (RSM). The WTRU may include a processor. An MA PDU session can be established with the RSM. The WTRU may receive request messages (e.g., PMF request messages) from network nodes (e.g., UPFs). These request messages may indicate a request to suspend service replication, and the WTRU may suspend data transmission or reception on the access tributary based on this request message. The WTRU may then determine that an event may have occurred associated with the suspended access tributary (e.g., the event may be associated with a change in serving cell or termination of the SDF). The WTRU may send an Access Assistance Request message to the network node based on this event (e.g., via PMF signaling). The Access Assistance Request message may indicate the reason associated with the event.

[0131] One or more examples described herein may be associated with an MA PDU session. One or more of the examples described herein may use PMF signaling, PMF pause, or PMF resume. The term “access” may be used interchangeably with the term “access tributary”, wherein an access tributary may be associated with a cellular communication network (e.g., a 3GPP network) or a non-cellular communication network (e.g., a non-3GPP network).

[0132] The embodiments disclosed herein can be used to enhance Redundancy Boot Mode (RSM). In one example, a WTRU procedure for suspending service replication can be provided. In one example, a WTRU procedure for handling WTRU mobility on an active access tributary can be provided. In one example, a WTRU procedure for handling WTRU mobility on a suspended access tributary can be provided. In one example, PMF signaling on an MA PDU session can be provided. In one example, a UPF procedure for suspending service replication can be provided.

[0133] The embodiments disclosed herein can provide WTRUs and / or network devices (e.g., UPFs) with the ability to effectively suspend service replication and / or handle potential mobility issues when service replication is suspended for an MA PDU session. The embodiments can allow WTRUs and / or network devices (e.g., UPFs) to use service replication to send PMF messages.

[0134] A WTRU and / or network device (e.g., UPF) procedure can be provided to suspend service replication. For example, a WTRU procedure can be provided. The WTRU can support MA PDU transport and Redundancy Guided Mode (RSM). The WTRU can receive ATSSS rules and / or configuration information regarding service replication suspension and / or Redundancy Guided Mode. The configuration information can indicate how to operate when service replication is (at least partially) suspended, such as which access tributary(s)(s) to use when service replication is suspended, the duration of the suspension, and / or a list of SDFs exempt from suspension.

[0135] The WTRU can receive request messages (e.g., PMF request messages) from network devices (e.g., UPF). Request messages can indicate the suspension of service replication. They can specify which access tributary(s) to use when (at least partially) suspending service replication, when to suspend replication, the direction of suspension (e.g., UL and / or DL), and / or the list of SDFs exempt from suspension. The WTRU can determine which access tributary(s) to suspend based on the request message, configuration information (e.g., including ATSSS rules), and conditions at the WTRU (e.g., power, operating frequency, link performance, etc.). The WTRU can send response messages (e.g., PMF response messages) to the network device (e.g., UPF). Response messages can include requests to put the WTRU into power-saving mode (e.g., on the suspended access tributary).

[0136] Network device procedures associated with service replication suspension can be provided. Network devices such as I-UPFs may support MA PDU transmission and / or redundant boot mode. The network device may receive one or more N4 rules. N4 rules may include configuration information regarding redundant boot mode and / or how to operate when service replication is suspended. The configuration information may indicate, for example, which access tributary to use when service replication is suspended (at least partially), the duration of the suspension, exemption from SDF, and / or how to send pause / resume messages (e.g., via PMF signaling). The network device may receive an indication to suspend traffic replication from another network device or node (e.g., such as an I-UPF, SMF, RAN node, etc.). The network device can determine to suspend traffic replication based on the received indication.

[0137] Network devices can send request messages (such as PMF request messages) to the WTRU to suspend service replication. The request message can indicate which access tributary to use when service replication is suspended, when service replication is suspended, the direction of suspension (such as UL and / or DL), and / or a list of exempted SDFs.

[0138] Network devices can receive response messages (e.g., PMF response messages) from the WTRU. These response messages may include an indication to put the WTRU into a power-saving mode (e.g., on a suspended access tributary). Based on the received response message, the network device can determine whether service replication (e.g., in the downlink) should be suspended (e.g., on a suspended access tributary reported by the WTRU). The network device can send a message to another network device or node (e.g., a RAN node, such as a base station) indicating that the access tributary has been suspended.

[0139] A WTRU procedure can be provided for handling WTRU mobility on active access tributaries. The WTRU can support MA PDU transmission and / or redundant boot mode. The WTRU can establish an MA PDU session using redundant boot mode. The WTRU can receive request messages (e.g., PMF request messages) from network devices (e.g., UPF). Request messages can indicate a pause in service replication.

[0140] The WTRU can determine when to stop service replication pauses (e.g., to resume uplink transmissions on a paused access tributary). This determination can be based on the loss of connectivity to the active access tributary (e.g., the access tributary used during the service replication pause), performance metrics or measurements on the active access tributary, the start of SDF, etc.

[0141] The WTRU can send a recovery request message (e.g., via PMF signaling) to network devices (e.g., UPF). The recovery request message may include the reason for the request and / or the time when service replication (e.g., data transmission or reception) should be restored on the suspended access tributary.

[0142] The WTRU can receive a recovery response message (e.g., via PMF signaling) from a network device (e.g., a UPF). The response message can instruct the WTRU whether it should continue data transmission or reception on the active access tributary (e.g., only on the active access tributary), whether it should restart data transmission or reception on the suspended access tributary, or whether it should replicate data transmission or reception on both access tributaries.

[0143] In response to receiving an instruction in a recovery response message, the WTRU may continue (e.g., use only) the active access tributary, stop using the active access tributary and start using the suspended access tributary, or start using both access tributaries.

[0144] A WTRU procedure can be provided for handling WTRU mobility on suspended access tributaries. The WTRU can support MA PDU transmission and / or redundant boot mode. The WTRU can establish an MA PDU session in redundant boot mode. The WTRU can receive request messages (e.g., PMF request messages) from network devices (e.g., UPF) to suspend service replication.

[0145] The WTRU can determine whether to notify network devices (e.g., UPFs) about events detected on suspended access tributaries, such as changes in serving cells or termination of the SDF. The WTRU can send an Access Assistance Request message (e.g., via PMF signaling) to the network device (e.g., the UPF). The Access Assistance Request message can indicate the reason for the request.

[0146] PMF signaling can be executed through an MA PDU session. The WTRU can support MA PDU transmissions. The WTRU can receive configuration information about the PMF signaling (e.g., via ATSSS rules for the WTRU, via N4 rules for the UPF). The configuration information can indicate how to send the first (e.g., initial) PMF message and / or how to retransmit the PMF message. The WTRU can determine whether to send a PMF message to a network device (e.g., the UPF). The PMF message may include an indication (e.g., bit fields) that the message is a first (e.g., initial) PMF message transmission. The WTRU can determine the access tributary guidance for the first (e.g., initial) PMF message transmission (e.g., based on the guidance mode and / or related rules).

[0147] The WTRU can determine when a PMF message needs to be retransmitted. The WTRU can include an indication that the message is being retransmitted (e.g., by modifying bit fields in the PMF message). The WTRU can determine the access tributary for the PMF message retransmission (e.g., based on bootstrapping patterns and / or relevant rules). If the PMF message has been retransmitted the maximum number of times, the WTRU can send a notification to the network device (e.g., the SMF).

[0148] One or more WTRU operations described in this article can be performed by network devices such as UPF.

[0149] WTRUs can have both 3GPP and non-3GPP access capabilities. These capabilities provide network operators with flexibility in determining which access to use for servicing data flows. WTRUs using both access methods can be requested to establish independent single-access PDU sessions on each access (e.g., on each access).

[0150] Figure 2 This is a system diagram illustrating an example of a WTRU with both 3GPP and non-3GPP access. Multi-access PDU (MA PDU) sessions can be established to allow for the routing, handover, and / or splitting of uplink and downlink traffic of service data streams between access points (e.g., such as...). Figure 3 (As shown). Services associated with an MA PDU session can be transmitted via 3GPP access, non-3GPP access, or both.

[0151] Figure 3 This is a system diagram illustrating another example of a WTRU with both 3GPP and non-3GPP access. Figure 3The example shown may allow bootstrapping functionality, which can include access service bootstrapping applicable between 3GPP and non-3GPP access networks. Bootstrapping functionality may include access service handover, which may include moving all or part of an ongoing data flow from one access network to another in a manner that maintains data flow continuity. Access service handover can be applied between 3GPP and non-3GPP access networks.

[0152] The guiding function can include access service splitting, which can split the traffic of a data stream across multiple access networks. When service splitting is applied to a data stream, one access network can be used to transmit some traffic of the data stream, and another access network can be used to transmit another part of the same data stream. Access service splitting can occur between 3GPP access networks and non-3GPP access networks.

[0153] The bootstrapping function in a WTRU with ATSSS capability can bootstrap, switch, and / or split services associated with MA PDU sessions across 3GPP access and non-3GPP access. One or more of the following bootstrapping functions can be provided. The first function can be a higher-level bootstrapping function (e.g., operating above the IP layer). The higher-level bootstrapping function can be applied to the MPTCP protocol (e.g., IETF RFC 8684) and can be referred to as an "MPTCP function." This function may be applicable to (e.g., only to) TCP services. The second function can be a lower-level bootstrapping function (e.g., operating below the IP layer). A lower-level bootstrapping function can be referred to as an "ATSSS lower-level function" or an ATSSS-LL function. The ATSSS-LL function can be applied to Ethernet and IP (e.g., TCP and UDP). The bootstrapping function can be a function present in the WTRU and network devices, such as UPFs (e.g., endpoints of PDU sessions).

[0154] The bootstrapping feature enables multiple bootstrapping modes. These modes determine how services matching service data flows can be distributed across multiple access points (e.g., 3GPP and non-3GPP accesses). Bootstrapping modes can include an active standby mode. This mode can be used to bootstrap services to an access point (e.g., the active access) when the access point is available, and / or to switch services to another access point (e.g., a standby access) when a previously used access point becomes unavailable.

[0155] The bootstrapping mode can include a minimum latency mode. The minimum latency mode can be used to bootstrap traffic to an access point that can be determined to have the minimum round-trip time (RTT). WTRUs and / or network devices (such as UPFs) can measure the RTT to determine which access point has the lowest RTT. This mode can be used with non-GBR SDFs.

[0156] The bootstrapping mode may include a load balancing mode. A load balancing mode can be used to split traffic across multiple (e.g., two) access tributaries based on the percentage of traffic that can be transmitted on each access tributary (e.g., a 3GPP access tributary or a non-3GPP access tributary). This mode can be used for non-GBR SDFs.

[0157] The bootstrapping mode can include a priority-based mode. A priority-based mode can be used to bootstrap services (e.g., all services) to a high-priority access point by matching policy and charging control (PCC) rules until that access point is determined to be congested. In this case, services (e.g., a portion of a service) can be sent to a low-priority access point (e.g., services can be split across high-priority and low-priority access points). This mode can be used (e.g., only for) non-GBR SDFs.

[0158] One or more of the bootstrapping modes described above can be enhanced. For load balancing modes, bootstrapping mode indicators can be used, which can indicate to the WTRU that it can change the default bootstrapping parameters provided in the bootstrapping mode component and can adjust service bootstrapping based on its own decisions. Bootstrapping mode indicators can be autonomous load balancing indicators. When such an indicator is provided, the WTRU can ignore the percentage in the bootstrapping mode component (e.g., the default percentage provided by the network) and autonomously determine its own percentage for service offloading in a way that maximizes aggregated bandwidth in the uplink direction. Steering mode indicators can be WTRU auxiliary indicators. When provided by the network, the indicator can indicate to the WTRU that it can decide how to distribute services (e.g., UL services) matching the SDF based on the WTRU's internal state (e.g., when the WTRU is in a special internal state, such as at a low battery level). In the example, the WTRU auxiliary indicator can indicate that the WTRU should inform the network (e.g., the UPF) how it allocates UL services matching the SDF. In the example, even if the WTRU auxiliary indicator is provided, the WTRU can still distribute services (e.g., UL services) as instructed by the network.

[0159] A threshold can be provided and used in load balancing bootstrapping mode. The threshold can be a value associated with RTT or packet loss rate. The threshold can apply to multiple (e.g., two) access points (e.g., access tributaries) and can be applied by WTRUs and / or network devices (e.g., UPFs). If a measured parameter (e.g., RTT or packet loss rate) for an access point exceeds the threshold, the WTRU and / or network devices can either stop transmitting traffic on that access point, or they can continue transmitting traffic on that access point but can reduce the amount of traffic transmitted on that access point by a certain amount (e.g., this can be implementation-specific and / or configurable). The WTRU and / or network devices can then transmit the reduced traffic on another access point. When one or more measured access parameters (e.g., RTT and / or packet loss rate) do not exceed the threshold, the WTRU and / or network devices apply a fixed percentage split to the access point.

[0160] A threshold can be provided for priority-based bootstrapping. The threshold can be a value associated with RTT or packet loss rate. This threshold can apply to multiple (e.g., two) accesses and can be applied by the WTRU and / or network devices (e.g., UPF). The WTRU and network devices can consider this threshold to determine when an access becomes congested. For example, if a measurement parameter (e.g., RTT or packet loss rate) for an access exceeds the threshold, the WTRU and / or network devices can consider the access congested and can send traffic (e.g., a portion of the traffic) to a lower-priority access.

[0161] To implement the bootstrap mode, the WTRU and / or network devices (such as the UPF) can use rules. These rules can be generated by a network device such as the SMF based on information known to another network device such as the PCF. Rules can be sent to the WTRU (e.g., as ATSSS rules) to determine the handover function and / or handover mode for UL services. Rules can be sent to network devices such as the UPF (e.g., as N4 rules) to determine the handover function and / or handover mode for DL ​​services.

[0162] To support certain boot modes, WTRUs and network devices (such as UPFs) can use the Performance Management Function (PMF) protocol to make / report the measurements necessary for switching modes (such as round-trip time measurements, access availability / unavailability reports, and / or packet loss rate).

[0163] Figure 4 This is a system diagram illustrating an example of providing Redundant Boot Mode (RSM). RSM can be considered a boot mode that allows WTRUs and / or network devices (such as UPFs) to replicate services on multiple (e.g., two) access tributaries of an MA-PDU session. Figure 4Some functions associated with RSM are illustrated. WTRUs can be configured with ATSSS rules associated with RSMs. Network devices such as UPFs can be configured with N4 rules associated with RSMs. These rules can inform WTRUs and / or network devices about which services can be replicated. Multiple (e.g., three) RSM modes can be provided.

[0164] In the first mode (which may be referred to herein as "static and with WTRU / UPF configured with primary access"), the WTRU and / or UPF can transmit services on the primary access (e.g., a primary access tributary), and when needed, the WTRU and / or UPF can replicate services through secondary access (e.g., a secondary access tributary). The primary access can be provided to the WTRU via one or more ATSSS rules and to the UPF via one or more N4 rules. The services to be replicated can be configurable and / or left to the WTRU / UPF to implement.

[0165] In the second mode (which may be referred to herein as "static and WTRU / UPF not configured for primary access"), the decision to replicate services can be static. WTRU and / or UPF can (e.g., always) replicate services on both primary and secondary access.

[0166] In the third mode (referred to herein as the "requirement-driven dynamic mode"), the decision to replicate services can be dynamic. The WTRU / UPF can replicate services based on primary access, configured requirements, requirements related to packet loss rate (PLR) or round-trip time (RTT), and / or performance measured on the primary and / or secondary access. The primary access can be configured to the WTRU via one or more ATSSS rules and to the UPF via one or more N4 rules. If no such rules are configured, the WTRU and / or UPF can determine the primary access based on their own implementation.

[0167] WTRU and / or network devices (e.g., UPF) can use multiple rules to determine whether service replication can be used for packets. In one example, if performance measured on the first access tributary does not meet requirements, but performance measured on the second access tributary does, the WTRU and / or network device may decide to transmit the service on the second access tributary. In another example, if requirements (e.g., performance requirements) are met on both accesses, the WTRU and / or network device may decide to transmit the service on the primary access (e.g., only on the primary access). In another example, if PLR measurements do not meet requirements regarding both the primary and secondary accesses, the WTRU and / or network device may replicate the service on both accesses. In yet another example, if RTT measurements do not meet requirements regarding both the primary and secondary accesses, the replication decision may be left to the WTRU and / or network device. For example, if the WTRU determines that service replication can help meet the RTT requirements, the WTRU may decide to replicate the service. On the other hand, if the WTRU determines that replication may not help meet the RTT requirements, the WTRU may decide not to replicate the service.

[0168] Network devices such as UPFs can suspend and resume service replication. This can be achieved by sending a message (e.g., a PMF message) to the WTRU. The network device can determine to suspend traffic replication in an implementation-specific manner. For example, a suspension can be initiated by the network device upon detecting congestion locally (e.g., at the network device's location). Suspending uplink service replication allows the network device to stop receiving replicated services via multiple access points (e.g., simultaneously via 3GPP and non-3GPP access points). In the message sent to the WTRU, the network device can provide one or more of the following indications: suspend service replication for GBR services, suspend service replication for non-GBR services, and suspend service replication for all uplink services. The network device can send the message via (e.g., any) available access channel.

[0169] Service replication can be paused and / or resumed. The Redundancy Boot Mode (RSM) described herein allows WTRUs and / or network devices (e.g., UPFs) to replicate services across multiple (e.g., two) access tributaries in an MA-PDU session. Replication can be configured to be static or dynamic. In the example, network devices can be allowed to pause replication via PMF signaling and later resume service replication via PMF signaling.

[0170] Several issues can be resolved to enable the suspension or resumption of service replication. The first issue might be that the WTRU and / or network devices (such as UPF) may lack configuration information regarding how the WTRU should operate when service replication is suspended. Without such configuration information, the WTRU may default to using either the active or standby access when service replication is suspended, which may not be optimal in some cases. The second issue might be that the WTRU may not be configured with logic to determine what to do when service replication is suspended.

[0171] A mechanism for pausing and resuming service replication can address several inefficiencies. The first inefficiency might involve triggering service replication pauses or resumptions based on a UPF (User-Defined Function) and not providing network devices with the ability to signal these pauses or resumptions to the UPF. The second inefficiency might relate to access network (AN) nodes being unaware (e.g., not knowing) of service replication pauses or resumptions and therefore unable to optimize resource allocation.

[0172] In some RSM implementations, PMF signaling can be executed between the WTRU and UPF on the user plane, while RSM can be used (e.g., only for) service data flows. Therefore, in these implementations, the WTRU (or UPF) may not replicate PMF signaling across multiple (e.g., two) access tributaries. Leaving the choice of which access tributary to use for executing PMF signaling to the WTRU (or UPF) can be inefficient. The embodiments described herein can allow PMF signaling to use service replication.

[0173] The behavior of the MA-PDU session can be configured (e.g., defined) when service replication is suspended and / or when the WTRU changes serving cell. When service replication is suspended, the service being replicated can be transmitted on the active access tributary, and another access tributary can be designated as the dormant access tributary (e.g., during the service replication suspension, the dormant access tributary may not carry the service whose replication has been suspended). In some examples, if the WTRU loses connectivity on the active access tributary or if the WTRU changes the AN node on the dormant access tributary (e.g., due to cell reselection or handover), the WTRU may not know what to do. The embodiments described herein can allow the WTRU to know what to do if the WTRU loses connectivity on the active access tributary or if the WTRU changes the AN node on the dormant access tributary (e.g., due to cell reselection or handover).

[0174] In the examples provided in this article, the term "access" can be used to refer to the access mechanism between the WTRU and the network. The network can be a cellular (e.g., 3GPP) network or a non-cellular (e.g., non-3GPP) network. For example, a non-3GPP network could be a WiFi network.

[0175] In the examples provided herein, the terms “access,” “access tributary,” and “access path” are used interchangeably and can refer to a combination of access and N3 interfaces between the WTRU and network equipment (e.g., UPF). In the examples provided here, multiple (e.g., two) access tributaries can be used for ATSSS, including, for example, 3GPP access tributaries and non-3GPP access tributaries.

[0176] In the examples provided herein, the term "replication" may refer to the Redundant Boot Mode feature, which allows services to be replicated across multiple (e.g., two) access tributaries. In the examples provided herein, the terms "pause" and "pause replication" are used interchangeably and may refer to a situation where the WTRU and / or network device (e.g., UPF) is using Redundant Boot Mode and the WTRU and / or network device has determined to pause service replication.

[0177] In the examples provided here, the term "active access tributary" can refer to an access tributary on which service transmission or reception is not suspended (e.g., in an MA-PDU session). (For example, an active access tributary is an access tributary on which services are transmitted or received during a service replication suspension.)

[0178] In the examples provided here, the term “suspended access tributary” may refer to (e.g., an MA-PDU session) an access tributary on which the transmission or reception of services (e.g., data and / or control information) associated with a particular service data stream is suspended (e.g., during a service replication suspension, services from the service data stream may not be transmitted on the suspended access tributary).

[0179] In the examples provided in this document, the term "bootstrapping mode" can refer to how a service can be split, bootstrap, switch over, or replicated across multiple access tributaries (e.g., two access tributaries). For ATSSS, one or more of the following bootstrap modes can be provided: active-standby, load balancing, priority, minimum latency, and redundant bootstrap modes. It should be noted that "bootstrap mode" is not limited to ATSSS bootstrap modes and may include other bootstrap modes.

[0180] WTRUs and network devices (such as UPFs) can use the PMF protocol to exchange information (e.g., information related to performance management and / or control signaling). WTRUs and network devices can also use other performance management protocols. When ATSSS is based on one or more of those higher-level boot functions, the performance management protocol can be implemented over MP-QUIC, MP-TCP, or MP-DCCP. For example, measurement and control messages can be sent via one or more MP-QUIC frames.

[0181] The embodiments described herein can provide enhancements to the redundancy boot mode. A procedure for suspending service replication can be provided. A procedure at the WTRU and / or network device (e.g., UPF) to allow PMF signaling to be replicated can be provided. A procedure at the WTRU and / or network device (e.g., UPF) for MA-PDU sessions can be provided, for example, when service replication is suspended and / or when the serving cell is changed.

[0182] The embodiments described herein enable WTRUs and / or network devices (e.g., UPFs) to effectively suspend service replication in order to handle potential mobility issues, etc., when service replication is suspended for an MA-PDU session. The embodiments may allow WTRUs and / or network devices to utilize service replication to send PMF messages.

[0183] Figure 5A This is a diagram illustrating an example of pausing business replication. For ease of description, Figure 5A The example assumes that the WTRU and / or network device (e.g., UPF) has requested to establish an MA-PDU session.

[0184] exist Figure 5A At point 1, the WTRU may receive one or more rules (e.g., ATSSS rules) via a PMF message from the PCF, which may include configuration information about the WTRU's behavior during service replication pauses and / or resumes. The configuration information may, for example, indicate the access to be used when service replication is paused. The configuration information may be used for uplink transmission, downlink reception, or both.

[0185] Configuration information can indicate the bootstrapping mode to use when service replication is paused. Bootstrapping modes can be, for example, active-standby, minimum latency, priority, load balancing, etc. Configuration information can include configuration parameters associated with the bootstrapping mode.

[0186] Configuration information can indicate the duration of a replication pause, which can be the duration for which service replication can be suspended. This duration can be related to the time when the PMF message is received. For example, a duration of K milliseconds could imply that the pause should last from the time (T1) when the PMF message indicating the pause was received until T1+K milliseconds. As another example, the duration can be specified via a start time and an end time.

[0187] Configuration information can indicate replication cycles or periods, which can be cycles or periods that the WTRU can alternate between periods when it does not replicate services and periods when it replicates services. Replication cycles or periods can be indicated by the length of the cycle or period, as well as the start / end times for pausing replication and the start / end times for activating replication within the cycle or period.

[0188] Configuration information can indicate whether an SDF can be exempted from service replication interruption. For example, some SDFs may carry high-priority services for which the network may not want to interrupt service replication. Therefore, even if service replication may be interrupted, the WTRU can continue to replicate the services of these SDFs.

[0189] exist Figure 5A At point 1, a network device (e.g., a UPF) may receive one or more N4 rules (e.g., via a PMF message from a PCF), which may include configuration information about the network device's behavior during service replication pauses and / or resumes. The configuration information may indicate the access to be used when service replication is paused. This may be provided for downlink transmission, for uplink reception, or for both downlink transmission and uplink reception.

[0190] Configuration information can indicate the bootstrap mode to use when service replication is paused. This bootstrap mode can be, for example, active-standby, minimum latency, priority, load balancing, etc. Configuration information can include configuration parameters associated with these bootstrap modes.

[0191] Configuration information can indicate the duration of the replication pause, which can be a period of time during which service replication can be suspended. This duration can be specified relative to the time when the PMF message is transmitted. The duration can be specified by a start time and an end time.

[0192] Configuration information can indicate a replication cycle or period, which can be a cycle or period in which a network device (e.g., a UPF) alternates between periods when it does not replicate services and periods when it replicates services.

[0193] Configuration information can indicate whether an SDF can be exempted from service replication pauses. For example, some SDFs may carry high-priority services for which the network may not want to pause service replication, and even if service replication is paused, network devices (e.g., UPFs) can continue to replicate the services of these SDFs.

[0194] Configuration information can indicate the method used to transmit PMF messages, which can be used to signal a pause in service replication. A network device (e.g., a UPF) can be configured to transmit PMF messages on one or more (e.g., two) access tributaries. A network device (e.g., a UPF) can be configured to retransmit the PMF message a certain number of times if it is not acknowledged by the WTRU. A network device (e.g., a UPF) can be configured to retransmit the PMF message (different from the first transmission) on different access tributaries. In some cases, the PMF message may be retransmitted on multiple (e.g., two) access tributaries (using replication).

[0195] exist Figure 5A At point 2, a network device (e.g., a UPF) can be triggered to suspend service replication. The trigger may be based on one or more conditions at the network device (e.g., internally) (e.g., load on the N3 interface). The trigger may also be based on signaling from other network nodes. This trigger may be referred to herein as a replication pause trigger and may be based on one or more of the following.

[0196] Replication pauses can be triggered based on indications from intermediate UPFs. For example, an intermediate UPF might determine it has storage or load issues and send an indication of the problem to the PDU Session Anchor (PSA) UPF. In response, the PSA UPF can decide to pause replication in an attempt to mitigate the problem at the intermediate UPF.

[0197] Replication pause triggering can be based on an instruction from the SMF. For example, the SMF can prepare to change the PDU session anchor and can send an instruction about the change to the UPF. The UPF can then decide to pause service replication while the anchor is being changed. As another example, the SMF can prepare to change the intermediate UPF and can send an instruction about the change to the PSA UPF. The PSA UPF can then decide to pause service replication while the intermediate UPF is being changed.

[0198] The replication pause trigger can be based on an instruction from the WTRU. For example, the WTRU may be experiencing power issues and may not want to use two access branches. To save power, the WTRU can send an instruction to the UPF, and the UPF can decide to pause service replication to help the WTRU save power.

[0199] Replication pause triggering can be based on an indication from the AN node. For example, the NG RAN node can determine that the WTRU can perform a handover to the cell. The NG RAN node can send an indication regarding the handover to the UPF, and the UPF can decide to pause service replication for that WTRU to reduce service forwarding between NG RAN nodes and / or minimize service interruption during the handover process.

[0200] exist Figure 5A At point 3, a network device (e.g., a UPF) can request the WTRU to suspend service replication. The network device can send this request via a request message (e.g., using PMF signaling). The network device can indicate in the request message the type of traffic (GBR and / or non-GBR) that should be suspended from replication. The network device can include one or more of the following information in the request message.

[0201] exist Figure 5AExamples of the three pieces of information sent could be a period of time during which replication can be paused. A network device (e.g., a UPF) can pause service replication during the indicated time period, or until a resume message is sent / received. For example, a network device can signal in a request message (e.g., a PMF message) that the pause can last for K milliseconds. The network device can also indicate the duration by specifying the start and stop times of the pause.

[0202] exist Figure 5A Examples of the information sent in the three places could be a paused cycle or period, for example, if the network device decides to pause replication after a specific cycle or period.

[0203] exist Figure 5A Examples of the three points of information sent could be the direction of pausing replication. For example, a network device could instruct to pause replication for (e.g., only for) UL transmissions from the WTRU, for (e.g., only for) downlink transmissions to the WTRU, or for both uplink and downlink transmissions.

[0204] exist Figure 5A An example of the information sent in the three locations could be the boot mode used during a service replication pause. For instance, a network device could determine that when replication is paused, the WTRU can use another boot mode (such as the active standby mode).

[0205] exist Figure 5A Examples of information sent in the three locations could be the access route used during a service replication pause. For instance, a network device could determine the access tributary to use when replication is paused. As another example, a network device could indicate to the WTRU that the decision can be left to the WTRU or that the WTRU can use the primary access route configured in the ATSSS rules.

[0206] exist Figure 5A The three instances of information sent could be a list of SDFs for which service replication suspension may not be applied. This could be because some SDFs may have requirements for PLR and / or RTT, and suspending replication for those SDFs could prevent the network from meeting those requirements.

[0207] exist Figure 5A In one or more examples of the information sent in the three locations, if the request message (e.g., sent via PMF signaling) lacks that information, the WTRU may have a default behavior. For example, if the network device does not provide the access to be used, the default behavior of the WTRU may be that the WTRU can decide which access to use, or the WTRU can use the primary access configured in the ATSSS rules.

[0208] exist Figure 5AAt four points, the WTRU can determine which access tributary to suspend based on one or more of the following criteria. Under the example criterion, the WTRU can determine the access tributary to suspend based on information carried in a suspension request message (e.g., received from the UPF). Under the example criterion, the WTRU can determine the access tributary to suspend based on implicit indications received from the network device. For example, the WTRU can receive a suspension request message on access tributary 1 and use it as an indication to suspend service replication on access tributary 1. As another example, the WTRU can receive a suspension request message on access tributary 1 and use it as an indication to suspend service replication on access tributary 2.

[0209] Under the example standard, the WTRU can determine which access tributaries to suspend based on its power consumption. For example, the WTRU can determine that the first access tributary uses more power than the second access tributary and decide to suspend service replication on the first access tributary.

[0210] Under the example standard, the WTRU can determine which access tributaries to suspend based on the operating frequency or band used by the WTRU. For example, the WTRU can prefer a frequency or band relative to another frequency or band (e.g., prefer to use unlicensed spectrum when available, or prefer not to use the FR2 band), and can determine which access tributaries are to be suspended for frequencies or bands that are not preferred.

[0211] Under the example standard, the WTRU can determine which access tributaries to suspend based on connectivity to network devices (e.g., access network nodes). For example, the WTRU may prefer a WLAN connection over a cellular connection and may determine to suspend access tributaries associated with cellular connections. As another example, the WTRU may prefer not to use satellite-based cellular connections or indirect cellular connections (e.g., those involving one or more relays) and determine to suspend access tributaries associated with such non-preferred connections. As yet another example, the WTRU may prefer not to use untrusted WLAN connections and may suspend access tributaries associated with untrusted WLAN connections.

[0212] Under the example standard, the WTRU can determine which access tributaries to suspend based on performance metrics such as packet loss rate (PLR) and / or round-trip time (RTT). For example, the WTRU may preferentially use access tributaries that better meet PLR and / or RTT requirements.

[0213] It should be noted that even if the WTRU disagrees with a recommendation / request from a network device (e.g., from a UPF), the WTRU can still use the criteria described in this document to determine which access tributaries to use or suspend.

[0214] exist Figure 5AAt point 5, the WTRU can confirm that it has received a pause request from the network device (e.g., UPF). The WTRU can send an acknowledgment to the network device via a response message (e.g., a PMF response message). The WTRU can provide additional information in the response message, including one or more of the following: The WTRU can indicate the duration of the pause in the response message (e.g., how long the WTRU can pause service replication). The WTRU can indicate the pause cycle or period in the response message (e.g., if the WTRU decides to pause service replication after a certain cycle or period). The WTRU can indicate the access tributary to be used when service replication is paused in the response message. For example, if the WTRU determines the access tributary to be used during replication pause, the WTRU can provide this information to the network device. The WTRU can indicate a request in the response message to put the WTRU into power-saving mode on the paused access tributary.

[0215] exist Figure 5A At point 6, a network device (e.g., a UPF) can perform an action upon receiving an acknowledgment from the WTRU. In an exemplary action (e.g., where the WTRU acknowledges it can suspend uplink service replication), the network device can decide whether to also suspend downlink service replication. In an example action, if the network device determines that service replication can be suspended in both the uplink and downlink directions of the access tributary, the network device can notify the AN node associated with the access tributary of the suspension, and the AN node can use this information to decide whether to put the WTRU into a power-saving state. In an example action, if the WTRU acknowledges a request including putting the WTRU into a power-saving state on the access tributary, the network device can notify the AN node of the access tributary of the request, and the AN node can use this information to decide whether to put the WTRU into a power-saving state.

[0216] exist Figure 5A In the example shown, the WTRU can determine to suspend service replication based on a power-saving message received from the access node. In this example, the WTRU and network devices (such as UPF) can establish an MA PDU session and can be configured to use redundant boot mode for one or more SDFs.

[0217] Figure 5B This is a diagram illustrating an example of CDRX configuration information for suspending service-based replication. (See diagram for example.) Figure 5BAs shown, at point 1, the UPF can be triggered to pause replication. The trigger can be based on conditions within the UPF (e.g., load on the N3 interface). The trigger can also be based on a periodic pause-resume cycle, with the pause determined by the UPF based on redundancy bootstrapping configurations (e.g., replication percentage). The trigger can also be based on signaling from other network nodes, such as replication pause triggers from the SMF, access network nodes, or intermediate UPFs. For example, the UPF can determine to pause replication on access tributary 1.

[0218] exist Figure 5B At point 2, the UPF can send a message to the Radio Access Network (RAN) node of the access tributary (e.g., access tributary 1) to notify the RAN node of the suspension of service replication on access tributary 1. The notification message may include a pause / resume cycle or period configuration (e.g., including time periods within the cycle and / or pause and resume intervals). The notification message may include an indication to suspend service replication. The notification message may include a WTRU identifier. The notification message may include a list of SDFs that can suspend service replication. The notification message may include a PDU session ID, which may identify the MA-PDU session associated with the service replication suspension.

[0219] exist Figure 5B At point 3 (e.g., access tributary 1), the RAN node can send a power-saving message to the WTRU based on the content of a pause notification message (e.g., from the UPF) via RRC signaling. The RAN node may determine to send the power-saving message based on the determination that there may be no traffic queuing to the WTRU on any PDU session and / or that no traffic can be sent to the WTRU within the time period corresponding to the pause / resumption cycle or period from the notification message (e.g., the RAN node can make this determination based on the notification message from the UPF). The power-saving message may indicate a Connectivity Mode Discontinuous Receive (CDRX) configuration. The CDRX configuration may match the pause / resumption cycle or period received from the UPF. In one example, the power-saving message may include a "GoToSleep" indication for the WTRU. The power-saving message may be sent via RRC signaling (e.g., using an RRCReconfiguration message), via MAC layer signaling (e.g., via MAC CE), and / or via physical layer signaling (e.g., via DCI). The reason this message may include the power-saving message is an indication of a service replication pause requested by the UPF.

[0220] exist Figure 5BAt point 4, the WTRU can receive power-saving messages and limit uplink transmissions based on these messages. If the message indicates "GoToSleep," the WTRU can stop transmitting services on the corresponding access tributary (e.g., stop replication on that access tributary). In one example, if the WTRU receives a CDRX configuration, it can stop uplink transmissions on the access tributary during the CDRX shutdown period (e.g., the WTRU can stop replicating services on that access tributary).

[0221] In the example, UPF can determine (e.g., after pausing business replication) to resume business replication, such as... Figure 5B As shown in point 5. Therefore, UPF can (for example, in Figure 5B The RAN node (at one of the five points) sends a recovery indication to the RAN node (e.g., at access tributary 1). In response, the RAN node can (e.g., at...) Figure 5B The WTRU can send a power-saving message to the WTRU at six points (e.g., via RRC signaling). This message may include CDRX configuration (e.g., a new CDRX configuration) or a "wake-up" signal. Based on the power-saving message, the WTRU can (e.g., in...) Figure 5B (7 locations) take action based on the content of the message (e.g., WTRU can restore the service replicated on access tributary 1).

[0222] WTRUs and / or network devices (such as UPFs) can implement procedures to enable the replication of PMF signaling. PMF signaling can occur between a transmitting entity and a receiving entity, where the transmitting entity can be either a WTRU or a UPF, and the receiving entity can be either a UPF or a WTRU. WTRUs and UPFs can be configured to allow PMF messages (e.g., across multiple access tributaries) to be replicated. In this case, the ATSSS rules for the WTRU and the N4 rules for the UPF can include rules (e.g., dedicated rules) for PMF signal replication. For example, a rule can include a service descriptor component (e.g., “PMF signaling”) that indicates whether the rule is applicable to PMF signaling. As another example, the ATSSS rules for the WTRU and the N4 rules for the UPF can include indications of whether a rule is applicable to PMF signaling. For example, the service descriptor component of a rule may have one or more of the following: an "Application Descriptor" field, an "IP Descriptor" field, a "Non-IP Descriptor" field, and / or an "Also Applicable to PMF Signaling" field, which can indicate to the WTRU or UPF that the rule can be applied to an SDF that matches the service descriptor and the PMF signaling. The WTRU and UPF may rely on existing service descriptors and treat the PMF as another application. The N4 rule and ATSSS rule may include rules for "PMF application". The PMF may have a reserved application identifier known to both the WTRU and UPF (e.g., it may include a reserved OSId and / or OSAppId); in one example, the WTRU and / or UPF may rely on existing service descriptors and treat the PMF as another application with a specific IP descriptor; for example, a 5-tuple may have a source IP address set to the PMF IP address and a source port set to a PMF UDP port associated with a non-3GPP access or a PMF UDP port associated with a 3GPP access. The rule may include a field (e.g., a new field) for identifying whether the rule applies to a first (e.g., initial) PMF transmission or a PMF retransmission.

[0223] Figure 6 Example actions at the transmitting and receiving entities are shown for a scenario where PMF signaling can be executed in a redundant boot mode (e.g., to allow duplication of PMF signaling). It should be understood that PMF signaling can use any boot mode (e.g., not just redundant boot mode). For ease of description, in Figure 6In the example, it can be assumed that an MA-PDU session has been established, and that the ATSSS and N4 rules allow PMF signaling to be replicated on multiple (e.g., two) access tributaries. The ATSSS / N4 rules may include rules that can be applied to the first (e.g., initial) PMF message transmission (referred to herein as the “Initial PMF Transmission Rules”) and / or rules that can be applied to the retransmission of PMF messages (referred to herein as the “PMF Retransmission Rules”).

[0224] exist Figure 6 At point 1, the transmitting entity can be triggered to send a PMF message. If replication is enabled for the PMF message, the transmitting entity can determine which access tributary to use to send the PMF message. This decision can be based on one or more of the following initial PMF transmission rules. In the example initial PMF transmission rule, the transmitting entity can replicate the PMF message through two access tributaries (e.g., always replicate). In the example initial PMF transmission rule, the transmitting entity can select the optimal access tributary based on measured performance. For example, this could be based on RTT or PLR measurements. In the example initial PMF transmission rule, the transmitting entity can select the access tributary based on the type of the PMF message. If the PMF message is a performance-based PMF message, the transmitting entity can send the PMF message on an access tributary where performance is measurable. If the PMF message involves pausing service replication, the transmitting entity can send the PMF message on an access tributary where pausing is not allowed.

[0225] In the example initial PMF transport rule, the transmitting entity can respond to or acknowledge a PMF request message from the receiving entity. In this case, the transmitting entity can select the same access tributary as the one used for the PMF request message. In one example, the PMF request message may indicate how to send a PMF response / acknowledgment. In another example, the PMF request message may indicate that a response message can be copied.

[0226] If the receiving entity does not respond to or acknowledge the PMF request message, the transmitting entity may retransmit some PMF request messages. These messages may include PMF messages used to signal access availability / unavailability, PMF messages used to send WTRU auxiliary data to the UPF, and / or PMF messages related to suspending service replication. When a PMF request message is triggered or transmitted, the transmitting entity may start a timer. If no response or acknowledgment is received before the timer expires, the transmitting entity may decide to retransmit the PMF message. Figure 6 As shown in Figure 2, PMF request message 1 can be retransmitted. Since PMF messages can be copied, if the transmitting entity determines that it needs to retransmit a PMF message, it can follow one or more of the following PMF retransmission rules.

[0227] In the example PMF retransmission rule, if the transmitting entity initially sends the PMF message on an access tributary, the transmitting entity may decide to retransmit the PMF message on another (e.g., a different) access tributary. This rule can be applied to (e.g., any) bootstrap mode, and also to situations where replication may not be enabled or permitted.

[0228] In the example PMF retransmission rule, if the transmitting entity initially sends the PMF message on an access tributary, the WTRU may decide to retransmit the PMF message across multiple (e.g., two) access tributaries that include the original access tributary.

[0229] The transmitting entity can send the original PMF message on one access tributary and decide to retransmit the PMF message on an access tributary with better measured performance (e.g., in terms of PLR and / or RTT). This rule can be applied to any bootstrap mode and also to situations where replication is not enabled or permitted.

[0230] The transmitting entity can include an indication (e.g., a bit field) in a PMF message (e.g., a PMF packet) to indicate that the message may be a retransmission of the original PMF message. The ATSSS layer can use this indication to identify the retransmitted PMF message.

[0231] If replication is enabled for PMF messages, the receiving entity can receive multiple copies of the PMF message (e.g., in...). Figure 6 (3 instances). The receiving entity can rely on the Extended Procedure Transaction Identifier (EPTI) to help identify and discard duplicate PMF message transmissions. In the example (e.g., for PMF ECHO REQUEST signaling), multiple messages can share the same EPTI. For these messages, if the PMF message has the same EPTI and the same request identifier (RI) as a previous PMF message, the receiving entity can determine that the PMF message may be a duplicate.

[0232] Additional functionality can be provided for PMF messages related to paused service replication. For example, if the maximum number of PMF message transmissions has been attempted, the first network device (e.g., UPF) can notify another network device (e.g., SMF) of the number of transmissions, so that the SMF can send a control plane message (e.g., in the WTRU) to the WTRU. Figure 6 (4 locations), this control plane message indicates that the PFM transmission has failed. In one example, if the UPF has requested to pause replication and the UPF has observed traffic from the WTRU on the paused access, the UPF can trigger a retransmission of the PMF pause message without waiting for the retransmission timer described herein to expire.

[0233] If service replication is suspended and a mobility event (e.g., WTRU changes serving cell) occurs at the WTRU, the WTRU and / or network equipment (e.g., UPF) can perform procedures related to the MA-PDU session. As described herein, service replication suspension can be a network (e.g., UPF) decision and can be based on or not based on WTRU mobility. When service replication is suspended, the WTRU may not transmit uplink traffic for the serving data stream on the suspended access tributary and may transmit uplink traffic associated with the serving data stream (e.g., all uplink traffic) on another access tributary, which may be referred to as the active access tributary. Due to WTRU mobility, the WTRU may change its serving cell on the suspended access tributary, the active access tributary, or, in some cases, both the suspended and active access tributaries. The WTRU and / or network equipment (e.g., UPF) may perform certain operations to facilitate WTRU mobility events (e.g., changes in serving cell).

[0234] In one example, due to WTRU mobility (e.g., when the WTRU moves out of coverage), the WTRU may lose connectivity on the active access tributary. Figure 7 An example is shown of handling WTRU mobility when service replication is suspended (e.g., where the WTRU may have lost connectivity to the access tributary). For ease of description, this example assumes that the WTRU has already established an MA-PDU session using redundant bootstrapping mode. Furthermore, in Figure 7 In the diagram, transmissions on 3GPP access tributaries are shown as solid lines, while transmissions on non-3GPP access tributaries are shown as dashed lines.

[0235] exist Figure 7 At point 1, the WTRU can send replicated transmissions on multiple (e.g., two) access tributaries. Figure 7 At two points, the network device (e.g., UPF) can determine that service replication on the 3GPP access tributary can be suspended, and the network device can send a suspension request message to the WTRU. Figure 7 At point 3, the WTRU can perform uplink transmissions (e.g., all uplink transmissions) on non-3GPP access tributaries in response to a request message received from a network device.

[0236] exist Figure 7At four locations, events at the WTRU can trigger the WTRU to decide to resume service replication. Triggering events can be associated with one or more of the following: Triggering events can be associated with the WTRU losing connectivity to an access network node in a non-3GPP access tributary. Triggering events can be associated with the quality of the non-3GPP access tributary degrading below a threshold or rapidly degrading. Triggering events can be associated with PLR and / or RTT requirements no longer being met in the non-3GPP access tributary. Triggering events can be associated with the WTRU beginning to use the replicated SDF. Triggering events can be associated with the WTRU changing its serving cell in a non-3GPP access tributary (e.g., changing the serving access network node) (e.g., changing the WiFi access point). Triggering events can be associated with a user requesting service replication through the user interface. Figure 7 In the example, it can be assumed that the WTRU has lost its connection to the non-3GPP access tributary.

[0237] exist Figure 7 At point 5, the WTRU can initiate a replication recovery process. The WTRU can send a recovery request message (e.g., a PMF recovery request message) to a network device (e.g., a UPF). This message can be sent on a 3GPP access tributary and includes one or more of the following information elements and / or parameters: The recovery request message may include a cause value, which can indicate why the message was sent. The cause value may be an indication of a triggering event. The recovery request message may include an indication of the time at which uplink transmissions on the suspended access tributary can be resumed. For example, the WTRU may request that replication be resumed within K milliseconds. The recovery request message may include an indication of the serving cell on the suspended access tributary (e.g., a 3GPP tributary). When a 3GPP access tributary is suspended, the WTRU may have changed its serving cell (e.g., due to cell reselection or handover), and the network device (e.g., the UPF) can use the aforementioned indication to reactivate the suspended access tributary.

[0238] exist Figure 7 At point 6, the network can decide to keep the 3GPP access tributary suspended, resume (e.g., on both 3GPP and non-3GPP access tributaries) replication, or move traffic (e.g., all uplink traffic) to a previously suspended access tributary (e.g., move traffic from a non-3GPP access tributary to a 3GPP access tributary). The network device can make this decision based on a reason value included in the recovery request message. The network device can respond with a recovery response message (e.g., a PMF recovery response message). The recovery response message can include one or more of the following information elements and / or parameters. The recovery response message can include an indication of whether the recovery request was rejected or accepted. If the request is accepted, the recovery response message can also indicate whether service replication is resumed or whether uplink traffic is allowed only on the previously suspended access tributary.

[0239] exist Figure 7 In the example, the WTRU can be instructed to resume uplink transmissions on a previously suspended 3GPP access tributary. In response, the WTRU can... Figure 7 The 7 locations perform uplink transmissions on the 3GPP tributaries as indicated by the recovery response message.

[0240] In one example, if in Figure 7 If, after the triggering event at point 4, a non-3GPP access tributary remains available, the WTRU can send a recovery request message on that non-3GPP access tributary. In one example, if the WTRU lacks connectivity on a non-3GPP access tributary, it can send a PDU session establishment request or PDU session modification request to the network (e.g., instead of a recovery request). This message may have a request type field set to "MA PDU request" and a PDU session ID field set to the suspended MA-PDU session.

[0241] Figure 8 This diagram illustrates an example of how the WTRU notifies the network if it changes the serving cell on a suspended access tributary. Due to WTRU mobility, the WTRU can change the serving cell on a suspended access tributary, for example, when the WTRU undergoes cell reselection or cell handover on a 3GPP access tributary. Figure 8 In the example, the WTRU may have already established an MA-PDU session in redundant boot mode. Furthermore, in Figure 8 In the diagram, transmissions on 3GPP access tributaries are shown as solid lines, while transmissions on non-3GPP access tributaries are shown as dashed lines.

[0242] exist Figure 8 At point 1, the WTRU can send duplicate transmissions across multiple (e.g., two) access tributaries. Figure 8 At point 2, network equipment (e.g., UPF) can determine to suspend service replication on the 3GPP access tributary and can send a pause request message to the WTRU. Figure 8 At point 3, the WTRU can perform uplink transmissions (e.g., all uplink transmissions) on non-3GPP access tributaries in response to receiving a request message.

[0243] exist Figure 8At four points, a triggering event can occur at the WTRU, prompting the WTRU to notify network equipment (e.g., UPF) of the event and / or take one or more actions. A triggering event can be associated with one or more of the following: A triggering event can be associated with the WTRU losing connectivity to the 3GPP access tributary (e.g., to an access network node of the 3GPP access tributary). A triggering event can be associated with the WTRU changing its serving cell to another cell (e.g., due to cell reselection or cell handover). A triggering event can be associated with the 3GPP access tributary quality rising above a threshold. A triggering event can be associated with the WTRU terminating the SDF and no longer wishing to use service replication. A triggering event can be associated with a user requesting termination of replication via the user interface.

[0244] exist Figure 8 In the example, the WTRU may have changed its serving cell and can initiate an assistance procedure at point 5 (e.g., using PMF signaling). The WTRU can send an Access Assistance Request message (e.g., a PMF Access Assistance Request message) to a network device (e.g., a UPF). This message can be sent on a non-3GPP access tributary. The message may include a reason value, which can indicate why the message was sent (e.g., the reason value can indicate a triggering event).

[0245] exist Figure 8 At point 6, network devices (e.g., UPFs) can use auxiliary information provided by the WTRU to establish an N3 interface between the network device and the serving cell (e.g., a new serving cell). The network device can respond to the WTRU using an access assistance response message (e.g., a PMF access assistance response message). This message may include an indication that an N3 interface has been established to the new serving cell.

[0246] Although the features and elements described above are given in specific combinations, each feature or element may be used alone without the other features and elements of the preferred embodiment, or in various combinations with or without the other features and elements. While the implementations described herein may be considered for 3GPP-specific protocols, it should be understood that the implementations described herein are not limited 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 should be understood that the solutions described herein are not limited to this scenario and may also be applied to other wireless systems.

[0247] The above processes can be implemented in computer programs, software, and / or firmware, which are incorporated into computer-readable media for execution by a computer and / or processor. Examples of computer-readable media include, but are not limited to, electronic signals (transmitted via wired and / or wireless connections) and / or computer-readable storage media. Examples of computer-readable storage media include, but are not limited to, read-only memory (ROM), random access memory (RAM), registers, 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 CD-ROMs and / or DVDs. The processor associated with the software can be used to implement a radio frequency transceiver used in WTRUs, terminals, base stations, RNCs, and / or any host computer.

Claims

1. A wireless transmit / receive unit (WTRU), comprising: The processor is configured as follows: Receive configuration information about pausing service replication from the first network node; Receive a request message from the second network node, wherein the request message indicates a request to suspend service replication; Based on the configuration information received from the first network node, the request message received from the second network node, and the conditions at the WTRU, it is determined that the replication service should be at least partially suspended in the first access tributary of the WTRU. as well as A response message is sent to the second network node, wherein the response message indicates that service replication is suspended in the first access tributary.

2. The WTRU of claim 1, wherein the condition at the WTRU is associated with at least one of the following: the power consumption of the WTRU, the frequency used by the WTRU, the connection type associated with the first access tributary or the second access tributary, and a performance metric associated with the first access tributary or the second access tributary.

3. The WTRU of claim 1, wherein the response message sent to the second network node further indicates the duration or period of the service replication suspension in the first access tributary.

4. The WTRU of claim 1, wherein the response message sent to the second network node further indicates that the WTRU will use the second access tributary to transmit or receive services when service replication in the first access tributary is suspended.

5. The WTRU of claim 1, wherein the processor is further configured to enter a power-saving mode in response to receiving the request message from the second network node.

6. The WTRU of claim 1, wherein the request message received from the second network node indicates the duration or period of the service replication pause, the access tributary to be used during the service replication pause, or the bootstrapping mode to be used during the service replication pause.

7. The WTRU of claim 1, wherein the request message received from the second network node indicates exemption from one or more Service Data Streams (SDFs) of the service replication suspension, and wherein the processor is further configured to continue replicating the services associated with the one or more SDF exemptions in the first access tributary based on the indication.

8. The WTRU of claim 1, wherein the first access tributary is associated with either a cellular communication network or a non-cellular communication network, and wherein, During the service replication pause, the processor is also configured to perform service transmission or reception in a second access tributary associated with the other of the cellular communication network or the non-cellular communication network.

9. The WTRU of claim 1, wherein the service replication pause is associated with a multi-access protocol data unit session.

10. The WTRU of claim 1, wherein the configuration information is received as part of an Access Service Bootstrapping, Switching, and Splitting (ATSSS) rule.

11. A method implemented by a wireless transmit / receive unit (WTRU), the method comprising: Receive configuration information about pausing service replication from the first network node; Receive a request message from the second network node, wherein the request message indicates a request to suspend service replication; Based on the configuration information received from the first network node, the request message received from the second network node, and the conditions at the WTRU, it is determined that the replication service should be at least partially suspended in the first access tributary of the WTRU. as well as A response message is sent to the second network node, wherein the response message indicates that service replication is suspended in the first access tributary.

12. The method of claim 11, wherein the condition at the WTRU is associated with at least one of the following: the power consumption of the WTRU, the frequency used by the WTRU, the connection type associated with the first access tributary or the second access tributary, and a performance metric associated with the first access tributary or the second access tributary.

13. The method of claim 11, wherein the response message sent to the second network node further indicates the duration or period of the service replication suspension in the first access tributary.

14. The method of claim 11, wherein the response message further indicates a second access tributary to be used by the WTRU for transmitting or receiving services when service replication in the first access tributary is suspended.

15. The method of claim 11, further comprising entering a power-saving mode in response to receiving the request message from the second network node.

16. The method of claim 11, wherein the request message received from the second network node indicates the duration or period of the service replication pause, the access tributary to be used during the service replication pause, or the bootstrapping mode to be used during the service replication pause.

17. The method of claim 11, wherein the request message received from the second network node indicates exemption from one or more SDFs of the service replication suspension, and wherein the method further includes continuing to replicate the service associated with the one or more exempted SDFs in the first access tributary based on the indication.

18. The method of claim 11, wherein the first access tributary is associated with one of a cellular communication network or a non-cellular communication network, and wherein the method further comprises, during the service replication pause in the first access tributary, performing the transmission or reception of a service in a second access tributary associated with the other of the cellular communication network or the non-cellular communication network.

19. The method of claim 11, wherein the service replication pause is associated with a multi-access protocol data unit session.

20. The method of claim 11, wherein the configuration information is received as part of an Access Service Bootstrapping, Switching, and Splitting (ATSSS) rule.

Images