WO2023275341A1 - Réduction d'interruption dans des scénarios de changement de groupe de cellules secondaires - Google Patents

Réduction d'interruption dans des scénarios de changement de groupe de cellules secondaires Download PDF

Info

Publication number
WO2023275341A1
WO2023275341A1 PCT/EP2022/068224 EP2022068224W WO2023275341A1 WO 2023275341 A1 WO2023275341 A1 WO 2023275341A1 EP 2022068224 W EP2022068224 W EP 2022068224W WO 2023275341 A1 WO2023275341 A1 WO 2023275341A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
change
configuration information
complete
path
Prior art date
Application number
PCT/EP2022/068224
Other languages
English (en)
Inventor
Amaanat ALI
Srinivasan Selvaganapathy
Henri Markus Koskinen
Tero Henttonen
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Publication of WO2023275341A1 publication Critical patent/WO2023275341A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0096—Indication of changes in allocation
    • H04L5/0098—Signalling of the activation or deactivation of component carriers, subcarriers or frequency bands
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0069—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink
    • H04W36/00695—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using split of the control plane or user plane
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections

Definitions

  • This description relates to wireless communications.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
  • LTE Long Term Evolution
  • eNBs enhanced Node AP
  • LTE mobile devices, or mobile stations are referred to as user equipments (UE).
  • UE user equipments
  • LTE has included a number of improvements or developments. Aspects of LTE are also continuing to improve.
  • 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G and 4G wireless networks.
  • 5G is also targeted at the new emerging use cases in addition to mobile broadband.
  • a goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security.
  • 5GNR may also scale to efficiently connect the massive Internet of Things (IoT) and may offer new types of mission-critical services. For example, ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency.
  • IoT massive Internet of Things
  • URLLC ultra-reliable and low-latency communications
  • a device, a system, a non-transitory computer-readable medium having stored thereon computer executable program code which can be executed on a computer system
  • a method can perform a process with a method including receiving, by a user equipment (UE) from a first node, configuration information for a reserve path, the configuration information indicating one of a secondary cell group (SCG) change or a secondary node change, in response to receiving the configuration information, at least one of receiving, by the UE from a first node, downlink (DL) transmissions via the reserve path and transmitting, by the UE to the first node, uplink (UL) transmissions via the reserve path, determining, by the UE, the SCG change is complete or the secondary node change is complete, and in response to determining the SCG change is complete or the secondary node change is complete receiving, by the UE from a second node, DL transmissions via a primary path and transmitting, by the UE to the second node
  • Implementations can include one or more of the following features.
  • the second node is a target node and the method can further include before transmitting UL transmissions via the reserve path, apply a target node security key to UL data.
  • the configuration information can include a list of radio bearers requiring an interruption time below an interruption time requirement.
  • the first node can include (or be) a master node (MN) and the second node can include (or be) a secondary node (SN).
  • MN master node
  • SN secondary node
  • the reserve path can be associated with a sub-set of radio bearers and the sub-set of radio bearers can be associated with a service with an interruption time requirement.
  • the interruption time requirement can be defined in a standard.
  • the primary path and the reserve path can each be a data radio bearer (DRB) for user plane data.
  • the method can further include after receiving the configuration information and before receiving DL transmissions and transmitting UL transmissions via the reserve path, applying, by the UE, a configuration for the reserve path based on the configuration information.
  • the method can further include in response to determining the SCG change is complete or the secondary node change is complete, switching, by the UE, DL transmissions and UL transmissions from the reserve path to the SCG.
  • a device, a system, a non-transitory computer-readable medium having stored thereon computer executable program code which can be executed on a computer system
  • a method can perform a process with a method including receiving, by a first node from a second node, configuration information for a reserve path, the configuration information indicating one of a secondary cell group (SCG) change or a secondary node change, transmitting, by the first node to a user equipment (UE), the configuration information, switching, by the first node, uplink (UL) transmissions to the second node from a primary path to the reserve path, determining, by the first node, the SCG change is complete or the secondary node change is complete, and in response to determining the SCG change is complete or the secondary node change is complete, switching, by the first node, UL transmissions to the second node from the reserve path to the primary path.
  • SCG secondary cell group
  • Implementations can include one or more of the following features.
  • the second node is a target node and the method can further include before transmitting the configuration information to the UE, receiving by the first node from the second node, a target node security key; and including, by the first node, the target node security key in the configuration information.
  • the SCG change or the secondary node change can trigger a communication of configuration information associated with the reserve path.
  • the configuration information can include a list of radio bearers requiring an interruption time below an interruption time requirement.
  • the first node can include (or be) a master node (MN) and the second node can include (or be) a secondary node (SN).
  • MN master node
  • SN secondary node
  • the reserve path can be associated with a sub-set of radio bearers and the sub-set of radio bearers can be associated with a service with an interruption time requirement.
  • the interruption time requirement can be defined in a standard.
  • the primary path and the reserve path can each be a data radio bearer (DRB) for user plane data.
  • the method can further include in response to determining the SCG change or the secondary node change is complete is complete, switching, by the first node, DL transmissions and UL transmissions from the reserve channel radio bearer to the SCG.
  • FIG. 1 is a block diagram of a wireless network according to an example embodiment.
  • FIG. 2 is a block diagram illustrating a signal flow in a network according to an example embodiment.
  • FIG. 3 is a block diagram illustrating a signal flow in a network according to an example embodiment.
  • FIG. 4 is a block diagram of a method of operating a user equipment according to an example implementation.
  • FIG. 5 is a block diagram of a method of operating a network device according to an example implementation.
  • FIG. 6 is a block diagram of a method of operating a user equipment according to an example implementation.
  • FIG. 7 is a block diagram of a method of operating a network device (e.g., node) according to an example implementation.
  • a network device e.g., node
  • FIG. 8 is a block diagram of a wireless station or wireless node (e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-CP, ... or other node) according to an example embodiment.
  • a wireless station or wireless node e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-CP, ... or other node
  • FIG. 1 is a block diagram of a wireless network 130 according to an example embodiment.
  • user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs) may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a BS, next generation Node B (gNB), a next generation enhanced Node B (ng-eNB), or a network node.
  • AP access point
  • eNB enhanced Node B
  • gNB next generation Node B
  • ng-eNB next generation enhanced Node B
  • ng-eNB next generation enhanced Node B
  • a BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as (e.g., such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS).
  • a BS e.g., access point (AP), base station (BS) or (e)Node B (eNB), BS, RAN node
  • AP access point
  • BS base station
  • eNB Node B
  • BS RAN node
  • RAN node may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head.
  • BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided.
  • BS 134 is also connected to a core network 150 via a SI interface or NG interface 151.
  • a base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network.
  • a BS (or a RAN node) may be or may include (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB), or other network node.
  • a BS may include: a distributed unit (DU) network entity, such as a gNB -distributed unit (gNB-DU), and a centralized unit (CU) that may control multiple DUs.
  • the centralized unit (CU) may be split or divided into: a control plane entity, such as a gNB- centralized (or central) unit-control plane (gNB-CU-CP), and an user plane entity, such as a gNB -centralized (or central) unit-user plane (gNB-CU-UP).
  • the CU sub entities may be provided as different logical entities or different software entities (e.g., as separate or distinct software entities, which communicate), which may be running or provided on the same hardware or server, in the cloud, etc., or may be provided on different hardware, systems or servers, e.g., physically separated or running on different systems, hardware or servers.
  • a distributed unit may provide or establish wireless communications with one or more UEs.
  • a DUs may provide one or more cells, and may allow UEs to communicate with and/or establish a connection to the DU in order to receive wireless services, such as allowing the UE to send or receive data.
  • a centralized (or central) unit may provide control functions and/or data-plane functions for one or more connected DUs, e.g., including control functions such as gNB control of transfer of user data, mobility control, radio access network sharing, positioning, session management etc., except those functions allocated exclusively to the DU.
  • CU may control the operation of DUs (e.g., a CU communicates with one or more DUs) over a front-haul (Fs) interface.
  • Fs front-haul
  • a BS node e.g., BS, eNB, gNB, CU/DU, ...) or a radio access network (RAN) may be part of a mobile telecommunication system.
  • a RAN radio access network
  • a RAN may include one or more BSs or RAN nodes that implement a radio access technology, e.g., to allow one or more UEs to have access to a network or core network.
  • the RAN (RAN nodes, such as BSs or gNBs) may reside between one or more user devices or UEs and a core network.
  • each RAN node e.g., BS, eNB, gNB, CU/DU, ...) or BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node.
  • Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and/or receiving data from one or more of the UEs.
  • a RAN node e.g., BS, eNB, gNB, CU/DU, (7) may forward data to the UE that is received from a network or the core network, and/or forward data received from the UE to the network or core network.
  • RAN nodes may perform a wide variety of other wireless functions or services, e.g., such as broadcasting control information (e.g., such as system information) to UEs, paging UEs when there is data to be delivered to the UE, assisting in handover of a UE between cells, scheduling of resources for uplink data transmission from the UE(s) and downlink data transmission to UE(s), sending control information to configure one or more UEs, and the like.
  • broadcasting control information e.g., such as system information
  • paging UEs when there is data to be delivered to the UE, assisting in handover of a UE between cells, scheduling of resources for uplink data transmission from the UE(s) and downlink data transmission to UE(s), sending control information to configure one or more UEs, and the like.
  • a base station may also be DU (Distributed Unit) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node).
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM) (which may be referred to as Universal SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, and a multimedia device, as examples, or any other wireless device.
  • SIM subscriber identification module
  • a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a user device may be also MT (Mobile Termination) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). MT facilitates the backhaul connection for an IAB node.
  • IAB Integrated Access and Backhaul
  • core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility /handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • 5G which may be referred to as New Radio (NR)
  • NR New Radio
  • 5GC New Radio
  • New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), massive MTC (mMTC), Internet of Things (IoT), and/or narrowband IoT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC).
  • MTC machine type communications
  • eMTC enhanced machine type communication
  • mMTC massive MTC
  • IoT Internet of Things
  • URLLC ultra-reliable and low-latency communications
  • Many of these new 5G (NR) - related applications may require generally higher performance than previous wireless networks.
  • IoT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • many sensor type applications or devices may monitor a physical condition or a status and may send a report to a server or other network device, e.g., when an event occurs.
  • Machine Type Communications MTC, or Machine to Machine communications
  • MTC Machine Type Communications
  • eMBB Enhanced mobile broadband
  • Ultra-reliable and low-latency communications is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems.
  • 3 GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10-5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example.
  • BLER block error rate
  • U-Plane user/data plane
  • URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability).
  • a URLLC UE or URLLC application on a UE
  • the various example embodiments may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE-A, 5G (New Radio (NR)), cmWave, and/or mmWave band networks, IoT, MTC, eMTC, mMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution
  • 5G New Radio (NR)
  • cmWave and/or mmWave band networks
  • IoT IoT
  • MTC Mobility Management Entity
  • eMTC massive machine type
  • eMBB massive machine type
  • URLLC etc.
  • Multi-radio dual connectivity is based on Intra-E-UTRA Dual Connectivity (DC), where a multiple Rx/Tx capable UE may be configured to utilize resources provided by two different nodes connected via non-ideal backhaul.
  • a first node can provide NR access and a second node can provide either E-UTRA or NR access.
  • the first node can act as a Master Node (MN) and the second node as a Secondary Node (SN).
  • MN and SN can be connected via a network interface and at least the MN can be connected to the core network.
  • the MN and/or the SN can be operated with shared spectrum channel access. Functions specified for a UE may be used for an IAB-MT.
  • the IAB-MT can access the network using either one network node or using two different nodes with EN-DC and NR-DC architectures.
  • EN-DC the backhauling traffic over the E-UTRA radio interface is not supported.
  • Example implementations relate to reducing, minimizing, and/or eliminating interruption time during Secondary Cell Group (SCG) modification and/or change in MR-DC.
  • SCG Secondary Cell Group
  • the MN can use the SN modification procedure to initiate configuration changes (e.g., SCG changes) within the same SN.
  • the MN can use the SN modification procedure for the addition, modification or release of SCG bearer(s) and the SCG RLC bearer of split bearer(s), and configuration changes for SN terminated MCG bearers.
  • Bearer termination point change can be realized by adding the new bearer configuration and releasing the old bearer configuration within a single MN initiated SN Modification procedure for the respective E-RAB.
  • the MN also uses the procedure to query the current SCG configuration (e.g., when delta configuration is applied in an MN initiated SN change).
  • the MN also uses the procedure to provide the S-RLF related information to the SN.
  • the MN initiated SN change procedure can be used to transfer a UE context from the source SN to a target SN and to change the SCG configuration in UE from one SN to another.
  • the Secondary Node Change procedure can involve signalling over MCG SRB towards the UE.
  • MR-DC a radio bearer with RLC bearers in MCG and SCG is sometimes called a split bearer.
  • a radio bearer for which PDCP is located in the SN is sometimes called a SN terminated bearer.
  • a radio bearer for which PDCP is located in the MN is sometimes called a MN terminated bearer.
  • MR-DC a radio bearer with an RLC bearer (or two RLC bearers, in case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in case of CA packet duplication in a NR cell group) only in the MCG is sometimes called a MCG bearer.
  • MR-DC a radio bearer with an RLC bearer (or two RLC bearers, in case of CA packet duplication in an E-UTRAN cell group, or up to four RLC bearers in case of CA packet duplication in a NR cell group) only in the SCG is sometimes called a SCG bearer.
  • SCG bearer only in the SCG is sometimes called a SCG bearer.
  • path is sometimes used.
  • a normal (or primary) path is used to transmit (or communicate) data when the SCG is available (e.g., there is no underlying SCG modification/change occurring).
  • the split bearer can include two paths, the normal (or primary) path and a reserve path.
  • the reserve path can be active for data transmission during the execution of the SCG modification/change procedure.
  • a path can also be referred to as a channel, a bearer, a radio bearer and/or any combination thereof.
  • a primary path can be referred to as a primary channel, a primary bearer, a primary radio bearer, and/or a primary channel radio bearer.
  • a reserve path can be referred to as a reserve channel, a reserve bearer, a reserve radio bearer, and/or a reserve channel radio bearer.
  • the SN can use the SN modification procedure to perform configuration changes (e.g., SCG changes) within the same SN.
  • the SN can use the SN modification procedure to trigger the release of SCG bearer(s) and the SCG RLC bearer of split bearer(s) (upon which the MN may release the bearer or maintain current bearer type or reconfigure it to an MCG bearer, either MN terminated or SN terminated), and to trigger PSCell change (e.g., when a new security key is required or when the MN needs to perform PDCP data recovery).
  • the SN initiated SN change procedure can be used to transfer a UE context from the source SN to a target SN and to change the SCG configuration in the UE from one SN to another.
  • the SCG modification procedure may be initiated either by the MN or by the SN and be used to modify, establish or release bearer contexts, to transfer bearer contexts to and from the SN or to modify other properties of the UE context within the same SN.
  • the SCG modification procedure may also be used to transfer a New Radio (NR) Radio Resource Control (RRC) message from the SN to the User Equipment (UE) via the MN and the response from the UE via MN to the SN (e.g., when SRB3 is not used).
  • NR New Radio
  • RRC Radio Resource Control
  • UE User Equipment
  • CPC Conditional PSCell Change
  • Example implementations relate to two SCG modification procedure scenarios.
  • the first scenario is a SN (or MN) initiated SN modification with MN involvement.
  • the second scenario is a MN (or SN) initiated SN change.
  • Both of these scenarios can have a user plane interruption due to the SCG modification/change.
  • the user plane interruption can be as long as 30 msec.
  • the first scenario or SCG/SN modification e.g., Primary SCG Cell (PSCell)/RRC reconfiguration
  • PSCell Primary SCG Cell
  • RRC reconfiguration can cause data interruption to SCG bearers.
  • MN terminated bearers using SCG resources can have a user plane interruption due to SCG change (e.g., PSCell/RRC reconfiguration) not involving the MN.
  • Example implementations provide techniques to reduce, minimize, and/or eliminate the interruption time for the first scenario and the second scenario during split bearer communication.
  • example implementations can include signalling changes required from the SN to the MN. The signalling can identify a scenario (e.g., the first scenario or the second scenario) and related standardization impacts for the network and the UE.
  • Example implementations can provide an indication from the MN to the UE indicating the explicit or implicit switching based on DL UP data or an explicit reception of RRC reconfiguration.
  • Example implementations can provide an indication from the MN to the UE indicating the earliest time when the UE can receive the first DL data re-routed due to SCG switching and/or modification.
  • example implementations can establish a reserve data path on the MCG, the SN can switch the DL path towards the MN in response to a SCG change, a MN to UE indication can be communicated to activate the interruption free data radio bearer (DRB) mechanism for a subset of the DRBs setup for the UE, the UE can switch DL and UL away from the SCG and continue data transmission. After the reconfiguration is complete the UE can switch back DL and UL towards the reconfigured (or new) SCG. As a result, time duration from receiving RRC reconfiguration to SCG RA access can be interruption free.
  • FIGS. 2-5 can be used to describe the aforementioned techniques in more detail.
  • FIG. 2 is a block diagram illustrating a signal flow in a network according to an example embodiment.
  • a network can include, at least, a UE 202, a MN 204, and a SN 206.
  • an SN terminated split bearer is established between MN 204 and SN 206.
  • the bearer path from the MN to the UE (MCG leg) can be reserved for use during the user plane interruption due to the SCG modification/change. This reserved bearer path may only require the configuration of the bearer path to be configured to the UE.
  • the underlying physical resources may be allocated at the initiation of the SCG modification/change procedure.
  • Split bearer (252) communications can be conducted between the UE 202, the MN 204, and the SN 206.
  • a reserved data path 210 between the MN 204 and SN 206 and a reserved data path 212 between the UE 202 and the MN 204 each can be configured and not used (at this time).
  • Reserved data path 210 and reserved data path 212 can be associated with the MCG.
  • UP data 214 can be communicated between the UE 202 and the SN 206.
  • UP data 214 communications can be associated with the SCG and the PSCell.
  • the SN 206 can trigger a PSCell change or modification (block 216).
  • the SN 206 can trigger PSCell change or modification (block 216) in order to initiate a procedure to perform configuration changes of the SCG within the same SN (e.g., to trigger the release of SCG bearer(s) and the SCG Radio Link Control (RLC) bearer of split bearer(s)) and/or to trigger a PSCell change (e.g., when a new security key is required or when the MN 204 needs to perform Packet Data Convergence Protocol (PDCP) data recovery).
  • PDCP Packet Data Convergence Protocol
  • the MN 204 may not reject the release request of the SCG bearer and the SCG RLC bearer of a split bearer.
  • the SN 206 can communicate an SN modification required message (218) to the MN 204.
  • the message (218) can include a NR RRC configuration message.
  • the NR RRC configuration message can include bearer context related information, other UE context related information and the new SCG radio resource configuration.
  • E-RAB E-UTRAN Radio Access Bearer
  • the PDCP Change Indication can indicate that a key (e.g., a secondary node key (S-KgNB)) update can be required.
  • S-KgNB secondary node key
  • the PDCP Change Indication can indicate that PDCP data recovery is required.
  • the SN 206 can decide whether a change of security key is required.
  • the MN 204 then applies the configuration for the reserve bearer (222).
  • the applying of the configuration for the reserve bearer (222) prepares the MN 204 to use the reserve path for UL and/or DL.
  • the MN 204 also communicates an RRC reconfiguration indication or message (224).
  • the message (224) can include a list of DRB(s) that may require interruption free behaviour.
  • the message (224) can also include user plane resource configuration related context, other UE context related information and the new radio resource configuration of SCG.
  • the MN 204 then switches UL UP (226) to the reserve bearer. In other words, the bearer associated with the MCG is switched to the reserve bearer as configured in block 222.
  • the UE 202 then applies the configuration for the reserve bearer (228).
  • the applying of the configuration for the reserve bearer (228) prepares the UE 202 to use the reserve path for UL and/or DL.
  • the UE 202 can then switch the DL UP (230) to the reserve bearer.
  • the MN 204 can then send DL UP data (or SCG DL data) (232) to the UE 202 using the reserve bearer.
  • the UE 202 switch the UL UP (234) to the reserve bearer and sends UL UP data (or SCG UL data) (236) to the MN 204 using the reserve bearer.
  • the MN 204 can forward the UL UP data (or SCG UL data) (238) to the SN 206 using the reserve bearer.
  • the UE 202 After the UE 202 switches the UL UP (234) to the reserve bearer, the UE 202 indicates the reconfiguration is complete (240) to the MN 204.
  • the indication that the reconfiguration is complete (240) (e.g., RRCConnectionReconfigurationComplete) can include a NR RRC response message, if needed.
  • the UE In case the UE is unable to comply with (or comply with part of) the configuration included in the indication that the reconfiguration is complete (240), the UE 202 can perform a reconfiguration failure procedure.
  • the UE 202 then switches (242) the bearer to the SCG. In other words, in response to the reconfiguration being complete, the UE 202 can switch UL to SCG away from the reserve bearer. In response to a successful completion of the reconfiguration, the success of the procedure is indicated in a message (244) (e.g., a SgNB Modification Confirm message) communicated by the MN 204 to the SN 206.
  • the message can include the encoded NR RRC response message, if received from the UE 202.
  • a random access procedure (246) is performed for communications between the UE 202 and the SN 206.
  • the UE 202 can perform synchronization towards the PSCell of the SN 206. Otherwise, the UE 202 may perform UL transmission after having applied the new configuration.
  • the SCG change or modification is complete. Therefore, UP data can be communicated (248) between the UE 202 and the SN 206 via the SCG and the DRB(s) can be switched back to reserved (250) i.e., they are no longer used as the SCG is available.
  • FIG. 3 is a block diagram illustrating a signal flow in a network according to an example embodiment.
  • FIG. 3 illustrates a scenario where the SN is switched from a source SN to a target SN. This is sometimes called a secondary node change procedure.
  • the Secondary Node Change procedure can be initiated either by MN or SN and used to transfer a UE context from a source SN to a target SN and to change the SCG configuration in UE from one SN to another.
  • the Secondary Node Change procedure can involve signalling over MCG SRB towards the UE.
  • a network can include, at least, the UE 202, the MN 204, a source SN 302 and a target SN 304.
  • Operations, communications and/or steps performed in the signal flow of FIG. 3 that are also performed in the signal flow of FIG. 2 are labelled the same in FIG. 3 as in FIG. 2.
  • an SN addition request message (306) is communicated from the MN 204 to the target SN 304.
  • the target SN 304 communicates an SN addition request acknowledge message (308).
  • the MN 204 can initiate the SN change by requesting the target SN 304 to allocate resources for the UE 202 by using a SgNB addition procedure.
  • the MN 204 may include measurement results related to the target SN 304. If forwarding is needed, the target SN 304 can provide forwarding addresses to the MN 204.
  • the target SN 304 can include an indication of the full or delta RRC configuration.
  • the MN 204 may trigger the MN-initiated SN Modification procedure (to the source SN 302) to retrieve the current SCG configuration before communicating the SN addition request message (306).
  • the MN 204 can begin communicating DL UP data (310) to the source SN 302 via the MCG.
  • the UE 202 switching the UL UP to the reserve bearer can include using a security key associated with the target SN 304 when transmitting UL data.
  • the MN 204 can forward the UL UP data (or SCG UL data) (312) to the target SN 304 using the reserve bearer.
  • the MN 204 can indicate the SN reconfiguration is complete in a message (314) to the target SN 304. For example, if the RRC connection reconfiguration procedure was successful, the MN 204 informs the target SN 304 via a SgNBReconfigurationComplete message with the encoded NR RRC response message for the target SN 304, if received from the UE 202. Then a random access procedure (318) is performed for communications between the UE 202 and the target SN 304.
  • a message (244) e.g., a SgNB Modification Confirm message
  • the MN 204 can indicate the SN reconfiguration is complete in a message (314) to the target SN 304. For example, if the RRC connection reconfiguration procedure was successful, the MN 204 informs the target SN 304 via a SgNBReconfigurationComplete message with the encoded NR RRC response message for the target SN 304, if received from the UE 202. Then a random access
  • the UE 202 can perform synchronization towards the PSCell of the target SN 304. Otherwise, the UE 202 may perform UL transmission after having applied the new configuration.
  • the SCG change or modification is complete. Therefore, UP data can be communicated (320) between the UE 202 and the target SN 304 via the SCG and the DRB(s) can be switched back to reserved (250) i.e., they are no longer used as the SCG is available.
  • FIG. 4 is a block diagram of a method of operating a user equipment according to an example implementation.
  • a configuration message (e.g., message 224) including an interruption free DRB list is received.
  • a UE e.g., UE 202
  • MN e.g., MN 204
  • the message can be an RRC reconfiguration indication or message.
  • the message can include a list of DRB(s) that may require interruption free behaviour.
  • the message can also include user plane resource configuration related context, other UE context related information and the new radio resource configuration of SCG.
  • step S410 a configuration for reserved bearer is applied.
  • the UE e.g., UE 202
  • the applying of the configuration for the reserve bearer can prepare the UE to use the reserve path for UL and/or DL.
  • step S415 DL UP is switched.
  • the UE e.g., UE 202
  • DL UP data is received.
  • DL UP data can be received from the MN (e.g., MN 204) via the reserve bearer.
  • step S425 UL UP is switched.
  • the UE e.g., UE 202
  • the UE can switch the UL UP to the reserve bearer and in step S430 the UE transmits UL UP data.
  • the UL UP data (or SCG UL data) can be transmitted from the UE to the MN (e.g., MN 204) using the reserve bearer.
  • step S435 bearer is switched to SCG.
  • the UE in response to the reconfiguration being complete, the UE can switch UL to SCG away from the reserve bearer.
  • step S440 the UE can communicate via reserved DRB.
  • a random access procedure can be performed for communications between the UE (e.g., UE 202) and the SN (e.g., SN 206).
  • the UE can perform synchronization towards the PSCell of the SN. Otherwise, the UE may perform UL transmission after having applied the new configuration until the SCG change or modification is complete and the DRB(s) can be switched to reserved.
  • step S505 is a block diagram of a method of operating a network device according to an example implementation.
  • a message indicating SN modification/change required is received.
  • an SN can trigger PSCell change or modification.
  • the SN e.g., SN 206
  • the MN e.g., MN 204
  • the MN can receive the SN modification required message.
  • step S510 DL UP data is started (optional step).
  • the SN can require a modification without a change in SN. Otherwise, the modification can include a change in SN from a source SN to a target SN. If there is no change in SN, step S510 may not be performed. If there is a change in SN, step S510 may be performed.
  • the MN e.g., MN 204
  • the source SN e.g., source SN 302
  • step S515 a configuration for reserve bearer is applied.
  • the MN can apply the configuration for the reserve bearer.
  • the applying of the configuration for the reserve bearer can prepares the MN to use the reserve path for UL and/or DL.
  • a configuration message including an interruption free DRB list is communicated.
  • the MN can communicate a configuration message to a UE (e.g., UE 202).
  • the message can be an RRC reconfiguration indication or message.
  • the message can include a list of DRB(s) that may require interruption free behaviour.
  • the message can also include user plane resource configuration related context, other UE context related information and the new radio resource configuration of SCG.
  • step S525 UL UP is switched.
  • the MN e.g., MN 204
  • the bearer associated with the MCG can be switched to the reserve bearer as configured in step S515.
  • step S530 a message indicating RRC reconfiguration complete is received.
  • the success of the procedure can be indicated in a message (e.g., a SgNB Modification Confirm message) communicated by the MN (e.g., MN 204) to the SN (e.g., SN 206 or target SN 304).
  • the message can include the encoded NR RRC response message, if received from the UE 202.
  • the MN can communicate via reserved DRB.
  • FIG. 6 is a block diagram of a method of operating a user equipment
  • Operation S605 includes receiving, by a user equipment (UE) from a first node, configuration information for a reserve path, the configuration information indicating one of a secondary cell group (SCG) change or a secondary node change.
  • Operation S610 includes in response to receiving the configuration information, at least one of receiving, by the UE from a first node, downlink (DL) transmissions via the reserve path and transmitting, by the UE to the first node, uplink (UL) transmissions via the reserve path.
  • Operation S615 includes determining, by the UE, the SCG change is complete or the secondary node change is complete.
  • Operation S620 includes in response to determining the SCG change is complete or the secondary node change is complete receiving, by the UE from a second node, DL transmissions via a primary path and transmitting, by the UE to the second node, UL transmissions via the primary path. Determining the SCG change is complete or the secondary node change is complete can be based on whether or not the RRC connection reconfiguration procedure was successful.
  • Example 2 The method of Example 1, wherein the second node is a target node and the method can further include before transmitting UL transmissions via the reserve path, apply a target node security key to UL data.
  • Example 3 The method of Example 1 or 2, wherein the configuration information can include a list of radio bearers requiring an interruption time below an interruption time requirement.
  • Example 4 The method of any of Examples 1 to 3, wherein the first node can include (or be) a master node (MN) and the second node can include (or be) a secondary node (SN).
  • MN master node
  • SN secondary node
  • Example 5 The method of any of Examples 1 to 4, wherein the reserve path can be associated with a sub-set of radio bearers and the sub-set of radio bearers can be associated with a service with an interruption time requirement.
  • Example 6 The method of Example 5, wherein the interruption time requirement can be defined in a standard.
  • Example 7 The method of any of Examples 1 to 6, wherein the primary path and the reserve path can each be a data radio bearer (DRB) for user plane data.
  • DRB data radio bearer
  • Example 8 The method of any of Examples 1 to 7 can further include after receiving the configuration information and before receiving DL transmissions and transmitting UL transmissions via the reserve path, applying, by the UE, a configuration for the reserve path based on the configuration information.
  • Example 9 The method of any of Examples 1 to 8 can further include in response to determining the SCG change is complete or the secondary node change is complete, switching, by the UE, DL transmissions and UL transmissions from the reserve path to the SCG.
  • FIG. 7 is a block diagram of a method of operating a network device or node.
  • Operation S705 includes receiving, by a first node from a second node, configuration information for a reserve path, the configuration information indicating one of a secondary cell group (SCG) change or a secondary node change.
  • Operation S710 includes transmitting, by the first node to a user equipment (UE), the configuration information.
  • Operation S715 includes switching, by the first node, uplink (UL) transmissions to the second node from a primary path to the reserve path.
  • Operation S720 includes determining, by the first node, the SCG change is complete or the secondary node change is complete.
  • Operation S725 includes in response to determining the SCG change is complete or the secondary node change is complete, switching, by the first node, UL transmissions to the second node from the reserve path to the primary path. Determining the SCG change is complete or the secondary node change is complete can be based on the UE transmitting to the MN a RRC reconfiguration complete message in response to the reconfiguration message from the MN.
  • Example 11 The method of Example 10, wherein the second node is a target node and the method can further include before transmitting the configuration information to the UE, receiving by the first node from the second node, a target node security key; and including, by the first node, the target node security key in the configuration information.
  • Example 12 The method of Example 10 or 11, wherein the SCG change or the secondary node change can trigger a communication of configuration information associated with the reserve path.
  • Example 13 The method of any of Examples 10 to 12, wherein the configuration information can include a list of radio bearers requiring an interruption time below an interruption time requirement.
  • Example 14 The method of any of Examples 10 to 13, wherein the first node can include (or be) a master node (MN) and the second node can include (or be) a secondary node (SN).
  • MN master node
  • SN secondary node
  • Example 15 The method of any of Examples 10 to 14, wherein the reserve path can be associated with a sub-set of radio bearers and the sub-set of radio bearers can be associated with a service with an interruption time requirement.
  • Example 16 The method of Example 15, wherein the interruption time requirement can be defined in a standard.
  • Example 17 The method of any of Examples 10 to 16, wherein the primary path and the reserve path can each be a data radio bearer (DRB) for user plane data.
  • DRB data radio bearer
  • Example 18 The method of any of Examples 10 to 17 can further include in response to determining the SCG change or the secondary node change is complete is complete, switching, by the first node, DL transmissions and UL transmissions from the reserve channel radio bearer to the SCG.
  • Example 19 A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of Examples 1-18.
  • Example 20 An apparatus comprising means for performing the method of any of Examples 1-18.
  • Example 21 An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of Examples 1-18.
  • FIG. 8 is a block diagram of a wireless station 800 or wireless node or network node 800 according to an example embodiment.
  • the wireless node or wireless station or network node 800 may include, e.g., one or more of an AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-UP, ... or other node) according to an example embodiment.
  • the wireless station 800 may include, for example, one or more (e.g., two as shown in FIG. 8) radio frequency (RF) or wireless transceivers 802A, 802B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 804 to execute instructions or software and control transmission and receptions of signals, and a memory 806 to store data and/or instructions.
  • Processor 804 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 804 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 802 (802 A or 802B).
  • Processor 804 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 802, for example).
  • Processor 804 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 804 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 804 and transceiver 802 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 808 may execute software and instructions, and may provide overall control for the station 800, and may provide control for other systems not shown in FIG. 8, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 800, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 804, or other controller or processor, performing one or more of the functions or tasks described above.
  • RF or wireless transceiver s) 802A/802B may receive signals or data and/or transmit or send signals or data.
  • Processor 804 (and possibly transceivers 802A/802B) may control the RF or wireless transceiver 802A or 802B to receive, send, broadcast or transmit signals or data.
  • the example embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems.
  • Another example of a suitable communications system is the 5G system. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced.
  • 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Example embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
  • Example embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
  • Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium.
  • Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and/or programs and/or software embodiments that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks.
  • embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • example embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS cyber-physical system
  • CPS may enable the embodiment and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, Certainly embedded in physical objects at different locations.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Example embodiments may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Landscapes

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

Abstract

Diverses techniques sont proposées pour un procédé comprenant la réception (S605), par un équipement utilisateur (UE) depuis un premier nœud, d'informations de configuration pour un chemin de réserve, les informations de configuration indiquant l'un d'un changement de groupe cellulaire secondaire (SCG) ou d'un changement de nœud secondaire; en réponse à la réception (S610) des informations de configuration, la réception, par l'UE depuis un premier nœud, de transmissions de liaison descendante (DL) via le chemin de réserve et/ou l'émission, par l'UE vers le premier nœud, des transmissions de liaison montante (UL) via le chemin de réserve; la détermination (S615), par l'UE, que le changement de SCG est terminé ou que le changement de nœud secondaire est terminé; et en réponse à la détermination (S620) que le changement de SCG est terminé ou que le changement de nœud secondaire est terminé, la réception, par l'UE depuis un second nœud, des transmissions DL via un chemin primaire et la transmission, par l'UE vers le second nœud, des transmissions UL via le chemin primaire.
PCT/EP2022/068224 2021-07-02 2022-07-01 Réduction d'interruption dans des scénarios de changement de groupe de cellules secondaires WO2023275341A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN202141029852 2021-07-02
IN202141029852 2021-07-02

Publications (1)

Publication Number Publication Date
WO2023275341A1 true WO2023275341A1 (fr) 2023-01-05

Family

ID=82693798

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/068224 WO2023275341A1 (fr) 2021-07-02 2022-07-01 Réduction d'interruption dans des scénarios de changement de groupe de cellules secondaires

Country Status (1)

Country Link
WO (1) WO2023275341A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180035485A1 (en) * 2014-08-07 2018-02-01 Lg Electronics Inc. Method for deactivating scells during scg change procedure and a device therefor
US20200214069A1 (en) * 2018-02-15 2020-07-02 Qualcomm Incorporated Secondary cell group failure handling

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180035485A1 (en) * 2014-08-07 2018-02-01 Lg Electronics Inc. Method for deactivating scells during scg change procedure and a device therefor
US20200214069A1 (en) * 2018-02-15 2020-07-02 Qualcomm Incorporated Secondary cell group failure handling

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Uplink switching", vol. RAN WG2, no. Qingdao, China; 20170627 - 20170629, 26 June 2017 (2017-06-26), XP051301297, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20170626] *
VIVO: "UE behavior when SCG is deactivated", vol. RAN WG2, no. electronic; 20210519 - 20210527, 11 May 2021 (2021-05-11), XP052007193, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_114-e/Docs/R2-2105628.zip R2-2105628_UE behavior when SCG is deactivated.docx> [retrieved on 20210511] *

Similar Documents

Publication Publication Date Title
AU2018379536B2 (en) Link monitoring with self-backhauling for wireless networks
EP3520481B1 (fr) Gestion de tampon pour réseaux sans fil durant un transfert
EP3861792A1 (fr) Avance temporelle pour transfert de liaison terrestre sans rach
US11218925B2 (en) Data forwarding for inter-radio access technology wireless networks
EP3824671B1 (fr) Réduction d&#39;interruption de transfert avec deux émetteurs et récepteurs
US20240023186A1 (en) Network method for small data transmission termination and signaling
WO2022084110A1 (fr) Rapport de faisceau basé sur un groupe
EP4055881B1 (fr) Transfert intercellulaire conditionnel pour des réseaux sans fil
US11044640B2 (en) Uplink bearer binding in handover
WO2023275341A1 (fr) Réduction d&#39;interruption dans des scénarios de changement de groupe de cellules secondaires
EP4366380A1 (fr) Utilisation d&#39;informations relatives à la probabilité d&#39;arrivée estimée pour sélectionner des noeuds secondaires cibles pour un transfert de données précoce pour des communications sans fil à double connectivité
US20230224252A1 (en) Downlink data stall optimization by addressing an out-of-order packet sequence
US20230239753A1 (en) Reconfiguration failure handling for cpac
AU2022323667A1 (en) Measurement configuration update during conditional reconfiguration for pscell for wireless networks
EP4381794A1 (fr) Mise à jour de configuration de mesure pendant une reconfiguration conditionnelle destinée à une pscell pour réseaux sans fil
US20230232292A1 (en) Lossless data forwarding in telecommunication systems
JP2024501028A (ja) 第１装置、第２装置、及び通信方法
WO2023006514A1 (fr) Configuration de repli conditionnel pour mcg-rlf
WO2024027971A1 (fr) Procédé et appareil de récupération de transfert conditionnel à double connectivité
WO2024022655A1 (fr) Procédé et appareil de transfert conditionnel à double connectivité avec transfert des données en temps voulu
WO2023066807A1 (fr) Procédure de signalisation améliorée pour mobilité de scg dans un état désactivé par configuration conditionnelle
WO2023036407A1 (fr) Transfert efficient pour communication point à multipoint
CN112868253A (zh) 条件触发的配置方法及相关产品

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22746965

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE