WO2024031383A1 - Gestion de réseau pour de multiples configurations conditionnelles conflictuelles - Google Patents

Gestion de réseau pour de multiples configurations conditionnelles conflictuelles Download PDF

Info

Publication number
WO2024031383A1
WO2024031383A1 PCT/CN2022/111273 CN2022111273W WO2024031383A1 WO 2024031383 A1 WO2024031383 A1 WO 2024031383A1 CN 2022111273 W CN2022111273 W CN 2022111273W WO 2024031383 A1 WO2024031383 A1 WO 2024031383A1
Authority
WO
WIPO (PCT)
Prior art keywords
cpc
configuration
indication
transceiver
processor
Prior art date
Application number
PCT/CN2022/111273
Other languages
English (en)
Inventor
Haijing Hu
Naveen Kumar R PALLE VENKATA
Yuqin Chen
Fangli Xu
Alexander Sirotkin
Ping-Heng Kuo
Peng Cheng
Ralf ROSSBACH
Zhibin Wu
Original Assignee
Apple Inc.
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 Apple Inc. filed Critical Apple Inc.
Priority to PCT/CN2022/111273 priority Critical patent/WO2024031383A1/fr
Publication of WO2024031383A1 publication Critical patent/WO2024031383A1/fr

Links

Images

Classifications

    • 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/00692—Transmission or use of information for re-establishing the radio link in case of dual connectivity, e.g. decoupled uplink/downlink using simultaneous multiple data streams, e.g. cooperative multipoint [CoMP], carrier aggregation [CA] or multiple input multiple output [MIMO]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/36—Reselection control by user or terminal equipment
    • H04W36/362—Conditional handover

Definitions

  • Embodiments of the present disclosure generally relate to the field of telecommunications, and in particular, to a solution for NW handling and optional UE assistance for conflicting multiple conditional configurations.
  • a user equipment may establish a connection to at least one of a plurality of different networks or types of networks, for example a 5G New Radio (NR) radio access technology (RAT) and a Long-Term Evolution (LTE) RAT.
  • the UE may support standalone (SA) carrier aggregation (CA) on LTE, SA CA on NR (NR-CA) , or a variety of non-standalone (NSA) and/or dual-connectivity (DC) functionalities in which a plurality of component carriers (CCs) are combined across LTE and/or NR.
  • SA carrier aggregation
  • NR-CA SA CA on NR
  • NSA non-standalone
  • DC dual-connectivity
  • NR-NR DC NR-DC
  • the UE is connected to two cells or cell groups (CG) wherein one gNB acts as master node (MN) , or primary cell (PCell) in a master CG (MCG) and another gNB acts as a secondary node (SN) (or primary secondary cell (PSCell) ) in a secondary CG (SCG) .
  • MN master node
  • PCell primary cell
  • SCG secondary CG
  • CPC Conditional PSCell Change
  • example embodiments of the present disclosure provide a solution for NW handling and optional UE assistance for conflicting multiple conditional configurations.
  • a processor of a user equipment communicatively coupled to a transceiver of the UE and configured to perform operations comprising: in accordance with a determination that a conditional primary secondary cell change (CPC) configuration from a secondary node (SN) is present at the UE, transmitting a first indication of existence of the CPC configuration to a master node (MN) using the transceiver; and in accordance with a determination that the CPC configuration is absent at the UE, transmitting a second indication of absence of the second CPC configuration to the MN using the transceiver.
  • CPC conditional primary secondary cell change
  • a processor of a base station communicatively coupled to a transceiver of the base station and configured to perform operations comprising: transmitting, using the transceiver to a user equipment (UE) , a first indication to inform the base station whether a conditional primary secondary cell change (CPC) configuration from a secondary node (SN) is present or absent at the UE, the base station being a master node (MN) of the UE; and receiving, using the transceiver from the UE, a second indication of existence or absence of the CPC configuration.
  • CPC conditional primary secondary cell change
  • a processor of a base station communicatively coupled to a transceiver of the base station and configured to perform operations comprising: in accordance with determining to transmit a first conditional primary secondary cell (PSCell) change (CPC) configuration to a user equipment (UE) , transmitting a first indication of existence of the first CPC configuration to a secondary node (SN) of the UE using the transceiver, the base station being a master node (MN) of the UE; and in accordance with a determination that the first CPC configuration is released, transmitting a second indication of absence of the first CPC configuration to the SN using the transceiver.
  • PSCell primary secondary cell
  • MN master node
  • a processor of a base station communicatively coupled to a transceiver of the base station and configured to perform operations comprising: in accordance with receiving a first indication of existence of a first conditional primary secondary cell (PSCell) change (CPC) configuration from a master node (MN) of a user equipment (UE) using the transceiver, avoiding transmitting a second CPC configuration to the UE, the base station being a secondary node (SN) of the UE; and in accordance with receiving a second indication of absence of the first CPC configuration from the MN using the transceiver, canceling avoidance of transmitting the second CPC configuration.
  • PSCell conditional primary secondary cell
  • CPC conditional primary secondary cell
  • MN master node
  • UE user equipment
  • SN secondary node
  • Fig. 1 shows an exemplary communication network in which example embodiments of the present disclosure can be implemented
  • Fig. 2A illustrates an exemplary Release 17 SN-initiated CPC with which example embodiments of the present disclosure can be implemented together;
  • Fig. 2B illustrates an exemplary Release 17 MN-initiated CPC with which example embodiments of the present disclosure can be implemented together;
  • Fig. 2C illustrates an exemplary Release 16 CPC with which example embodiments of the present disclosure can be implemented together;
  • Fig. 3 illustrates an exemplary process flow for NW handling of conflicting multiple conditional configurations according to some embodiments of the present disclosure
  • Fig. 4 illustrates an exemplary process flow for NW handling with no R16 CPC according to some embodiments of the present disclosure
  • Fig. 5 illustrates an exemplary process flow for NW handling with UE assistance according to some embodiments of the present disclosure
  • Fig. 6 illustrates another exemplary process flow for NW handling with UE assistance according to some embodiments of the present disclosure
  • Fig. 7A illustrates an exemplary information element for UE to inform MN about presence or absence of R16 CPC according to some embodiments of the present disclosure
  • Fig. 7B illustrates another exemplary information element for UE to inform MN about presence or absence of R16 CPC according to some embodiments of the present disclosure
  • Fig. 7C illustrates an exemplary information element for configuration from MN to UE according to some embodiments of the present disclosure
  • Fig. 8 illustrates another exemplary process flow for NW handling of conflicting multiple conditional configurations according to some embodiments of the present disclosure
  • Fig. 9 illustrates an exemplary process flow for MN handling with SN assistance according to some embodiments of the present disclosure
  • Fig. 10 illustrates an exemplary method implemented at a UE according to some embodiments of the present disclosure
  • Fig. 11 illustrates an exemplary method implemented at a MN according to some embodiments of the present disclosure
  • Fig. 12 illustrates another exemplary method implemented at a MN according to some embodiments of the present disclosure
  • Fig. 13 illustrates an exemplary method implemented at a SN according to some embodiments of the present disclosure.
  • Fig. 14 illustrates a simplified block diagram of a device that is suitable for implementing embodiments of the present disclosure.
  • first and second etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments.
  • the term “and/or” includes any and all combinations of one or more of the listed terms.
  • the term “communication network” refers to a network following any suitable communication standards, such as Long Term Evolution (LTE) , LTE-Advanced (LTE-A) , Wideband Code Division Multiple Access (WCDMA) , High-Speed Packet Access (HSPA) , Narrow Band Internet of Things (NB-IoT) and so on.
  • LTE Long Term Evolution
  • LTE-A LTE-Advanced
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • NB-IoT Narrow Band Internet of Things
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the fourth generation (4G) , 4.5G, the future fifth generation (5G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • 4G fourth generation
  • 4.5G the future fifth generation
  • 5G fifth generation
  • Embodiments of the present disclosure may be applied in various
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , a NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated and Access Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and
  • terminal device refers to any end device that may be capable of wireless communication.
  • a terminal device may also be referred to as a communication device, user equipment (UE) , a Subscriber Station (SS) , a Portable Subscriber Station, a Mobile Station (MS) , or an Access Terminal (AT) .
  • UE user equipment
  • SS Subscriber Station
  • MS Mobile Station
  • AT Access Terminal
  • the terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA) , portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE) , laptop-mounted equipment (LME) , USB dongles, smart devices, wireless customer-premises equipment (CPE) , an Internet of Things (IoT) device, a watch or other wearable, a head-mounted display (HMD) , a vehicle, a drone, a medical device and applications (for example, remote surgery) , an industrial device and applications (for example, a robot and/or other wireless devices operating in an industrial and/or an automated processing chain contexts) , a consumer electronics device, a device operating on commercial and/or industrial wireless networks
  • a UE may establish a connection to at least one of a plurality of different networks or types of networks, for example a 5G New Radio (NR) radio access technology (RAT) and a Long-Term Evolution (LTE) RAT.
  • the UE may support standalone (SA) carrier aggregation (CA) on LTE, SA CA on NR (NR-CA) , or a variety of non-standalone (NSA) and/or dual-connectivity (DC) functionalities in which a plurality of component carriers (CCs) are combined across LTE and/or NR.
  • SA carrier aggregation
  • NR-CA SA CA on NR
  • DC dual-connectivity
  • NR-NR DC NR-DC
  • the UE is connected to two cells or cell groups (CG) wherein one gNB acts as master node (MN) (or primary cell (PCell) ) in a master CG (MCG) and another gNB acts as a secondary node (SN) (or primary secondary cell (PSCell) ) in a secondary CG (SCG) .
  • MN master node
  • SN secondary node
  • PSCell primary secondary cell
  • SCG secondary CG
  • CPC Conditional PSCell Change
  • Embodiments of the present disclosure propose a solution for MN handling and optional UE assistance for conflicting multiple conditional configurations.
  • the NW deals with conflict of a first CPC configuration from the MN and a second CPC configuration from the SN.
  • CPC conditional primary secondary cell change
  • MN master node
  • the CPC configuration is absent at the UE
  • transmitting a second indication of absence of the second CPC configuration to the MN using the transceiver In accordance with a determination that the CPC configuration is absent at the UE, transmitting a second indication of absence of the second CPC configuration to the MN using the transceiver.
  • the NW can handle the conflict of CPC configuration from the MN and the SN, and avoid out of sync configuration between the UE and the network, such as the MN and the SN.
  • Principle and implementations of the present disclosure will be described in detail below with reference to Figs. 1-12.
  • Fig. 1 shows an exemplary communication network 100 in which example embodiments of the present disclosure can be implemented.
  • the network 100 includes a UE 101, a master node (MN) 103 and a R16 secondary node (SN) 105.
  • the MN 103 and SN 105 are both base stations.
  • the UE 101 is in dual connection (DC) with the MN 103 and the SN 105.
  • the wireless connection between the UE 101 and the MN 103 is 113, and the wireless connection between the UE 101 and the SN 105 is 109.
  • the connection between the MN 103 and the SN 105 is 111.
  • UE 101 can be in dual connection with MN103 and SN107.
  • the wireless connection between UE 101 and SN 107 is 117, and connection between MN 103 and SN 107 is 115.
  • one of the targets is to specify Conditional Hand Over (CHO) including target Master Cell Group (MCG) and target Secondary Cell Group (SCG) in Radio Access Network (RAN) 3 and RAN 2.
  • the target is also to specify CHO including target MCG and candidate SCGs for Conditional PSCell change (CPC) and Conditional PSCell Addition/Change (CPAC) in New Radio (NR) DC.
  • CPC Conditional PSCell change
  • CPAC Conditional PSCell Addition/Change
  • NR New Radio
  • the MN 103 can configure the UE 101 with CPC configuration.
  • the SN 105 can also configure the UE 101 with CPC configuration.
  • the CPC configuration is confined such that, the PSCell candidate is only limited to the current serving cells of the SCG. The primary intention is to avoid the MN 103 getting involved. So for R16 CPC, the MN 103 is not aware of this at all. In R17, both the MN 103 and the SN 105 can initiate CPC configuration, but the MN 103 is always in co-ordination.
  • the SN candidates are not limited to just serving cells of the current SCG.
  • the SN 105 informs the MN 103 about this, and provides the CPC configurations.
  • the MN 103 then provides these to the UE.
  • the MN 103 can also evaluate SN candidates without ever informing the current SN 105.
  • MN 103 directly configures the UE 101 with these candidates.
  • MI-CPC MN initiated CPC
  • MN 103 does inform the current SN 105 about the procedure, just does not need to get permissions/ACK from current SN 105.
  • Fig. 2A illustrates an exemplary Release 17 SN-initiated CPC with which example embodiments of the present disclosure can be implemented together.
  • the UE 101, MN 103 and R17 SN 107 are the same as in Fig. 1.
  • the UE 101 is in DC with the MN 103 and the SN 107.
  • the SN 107 coordinates R17 CPC candidates 203 for SI-CPC.
  • the SN 107 transmits (213) SgNB modification 215, or CG configuration to the MN 103, to trigger a SI-CPC.
  • the MN 103 transmits (218) a SgNB modification ACK 220 to the SN 107.
  • the SgNB modification ACK 220 the SN 107 gets positive feedback from the MN 103.
  • the MN 103 transmits (223) an RRCReconfig with SI-CPC configuration 225 to the UE 101.
  • the UE 101 After receiving (227) the RRCReconfig with SI-CPC configuration 225, the UE 101 transmits (228) a RRC Reconfiguration complete message 230 to the MN 103. The UE 101 make evaluation in 235, then transmits (238) RRC Reconfiguration complete message 240 to the MN 103. After receiving (242) the RRC Reconfiguration complete message 240, the MN 103 knows the SI-CPC successful in the UE 101, then transmits (243) RRC Reconfiguration complete message 245 to the new SN. After receiving (247) the RRC Reconfiguration complete message 245, a R17 SN candidate chosen by SN 105 becomes the new SN. This way, a R17 SI-CPC is completed.
  • Fig. 2B illustrates an exemplary Release 17 MN-initiated CPC with which example embodiments of the present disclosure can be implemented together.
  • the UE 101, MN 103, R17 SN 107, R17 SN candidate chosen by MN 201, R17 SN candidate chosen by SN 203, and block 205 are the same as in Fig. 2A.
  • the MN 103 coordinates R17 candidates for MI-CPC.
  • the MN 103 transmits (248) SgNB modification 250, or CG configuration to the SN 107, to trigger a MI-CPC.
  • the SN 107 transmits (253) a SgNB modification ACK 255 to the MN 103.
  • the MN 103 gets positive feedback from the SN 107.
  • the MN 103 transmits (223) an RRCReconfig with MI-CPC configuration 259 to the UE 101.
  • the UE 101 After receiving (227) the RRCReconfig with MI-CPC configuration 259, the UE 101 transmits (228) a RRC Reconfiguration complete message 230 to the MN 103. The UE 101 make evaluation in 235, then transmits (238) RRC Reconfiguration complete message 240 to the MN 103. After receiving (242) the RRC Reconfiguration complete message 240, the MN 103 knows the MI-CPC successful in the UE 101, then transmits (258) RRC Reconfiguration complete message 260 to the new SN. After receiving (262) the RRC Reconfiguration complete message 260, a R17 SN candidate chosen by MN 103 becomes the new SN. This way, a R17 MI-CPC is completed.
  • Fig. 2C illustrates an exemplary Release 16 CPC with which example embodiments of the present disclosure can be implemented together.
  • the UE 101, MN 103, SN 105, R17 SN candidate chosen by MN 201, and block 205 are the same as in Fig. 2A and 2B.
  • the SN 106 coordinates R16 CPC candidates.
  • the SN 103 transmits (273) R16 CPC configuration message 275 to the UE 101 directly, and the MN 103 does not aware of the R16 CPC configuration message 275.
  • the UE 101 evaluates and triggers a PSCell change at block 280.
  • the UE 101 transmits (283) R16 configuration complete message 285 to the SN 105 directly.
  • the MN 103 does not aware of the R16 configuration complete message 285.
  • the R16 CPC ends. So, in the whole R16 CPC process, the communication is between the SN 105 and the UE 101, the MN 103 does not aware of it.
  • the UE 101 considers conditional reconfigurations, which are received via the MCG, such as from the MN 013, for CHO and Rel-17 CPAC, and via the SCG, such as from the SN 105, or for Rel-16 CPC, as separate UE variables.
  • the MN 103 can choose whether to configure the UE 101 directly after receiving the response from the at least one target candidate SN, without first perform a second step of signaling towards the source SN so that it could update such as the measurement configuration.
  • the UE 101 can have a measurement configuration with at least one measID with reportType set to condTriggerConfig that are not linked to any conditional configuration.
  • the UE is not required to perform measurements on at least one measId with reportType set to condTriggerConfig that are not included in any conditional reconfigurations.
  • R16 SN CPC While MN 103 has already configured a R17 CHO or CPC, there are already some checks within network (NW) nodes to prevent CHO and R16 CPC in Release 16. For example, the MN 103 does not configure CHO if DC is configured to the UE 101. MI-CPC and SI-CPC both use MN 103 for configuration, while SN-CPC in Release 16 is via the SN 105. So the UE 101 has some level of distinction already. The UE 101 can know if the provided CPC is R16 CPC or R17 CPC.
  • the UE 101 since the UE 101 releases all conditional configurations whenever a condition is triggered, and the MN 103 is not aware of the R16 SN CPC, there are cases where UE 101 and the NW are out of sync in terms of what the UE 101 configuration is.
  • SN 105 transparently configures R16 CPC to the UE 101, while MN 103 has provided a MI-CPC or SI-CPC. If the UE 101 executes R16 CPC, the MI-CPC or SI-CPC is now released at the UE 101. MN 103 is not aware. If the UE 101 executes R17 CPC, then UE releases R16 CPC and SN is not aware. Such out of sync configurations need to be avoided. According to embodiments of the present disclosure, the previous out of sync configuration problem can be handled at the MN 103 and SN 105, with assistance of UE 101.
  • Fig. 3 illustrates an exemplary process flow for NW handling of conflicting multiple conditional configurations according to some embodiments of the present disclosure.
  • the UE 101 receives (312) an indication to inform the base station where a CPC configuration from a SN is present or absence 310 from the MN 103.
  • the UE 101 transmits (322) an indication of existence or absence of CPC configuration from the SN. This way, the conflict of CPC configuration can be avoided, and avoid out of sync between the UE 101 and the NW, such as MN 103 or SN 105.
  • the UE 101 in accordance with a determination that a CPC configuration from a SN is present at the UE, transmits a first indication of existence of the CPC configuration to the MN 103 using the transceiver; and in accordance with a determination that the CPC configuration is absent at the UE 101, the UE 101 transmits a second indication of absence of the second CPC configuration to the MN 103 using the transceiver.
  • the first indication or the second indication is transmitted via UE assistance information (UAI) .
  • UAI UE assistance information
  • RRC radio resource control
  • the UE 101 determines that the CPC configuration is present can be implemented in: in accordance with receiving the second CPC configuration from the SN using the transceiver, the UE 101 determines that the CPC configuration is present. This way, the UE101 can get accurate situation of the second CPC configuration from the SN 105, so it can inform the MN 103 about the accurate situation for the second CPC configuration from the SN 105.
  • the UE 101 determines that the CPC configuration is absent can be implemented in: in accordance with a determination that the second CPC configuration is completed at the UE 101, the UE 101 determines that the CPC configuration is present. This way, the second CPC configuration is processed by UE 101, so the UE 101 can inform the MN 103 that the second CPC configuration is absent. It can avoid out of sync between the UE 101, the MN 103 and the SN 105.
  • the UE 101 also receives a UE capability enquiry from the MN using the transceiver; and based on receiving the UE capability enquiry, transmits, using the transceiver to the MN, UE capability information indicating that the UE is configured to inform the MN whether the CPC configuration is present or absent at the UE.
  • the UE 101 also transmits UE capability information to the SN using the transceiver.
  • the UE 101 gets capability enquiry from the MN 103, then informs the MN 103 and SN 105 about the capability of informing the MN about the existence or absence of the second CPC configuration from the SN105. So it provides the capability to sync the status of the second CPC configuration from the SN 105, avoid out of sync between the UE 101 and the network nodes.
  • transmitting the first indication and the second indication comprises: in accordance with receiving, using the transceiver from the MN 103, a third indication that the UE 101 is configured to report presence or absence of the CPC configuration, the UE 101 transmits at least one of the first indication or the second indication to the MN using the transceiver.
  • the report of presence or absence of the second CPC configuration from the SN 105 is based on the indication from the MN103. It can make the UE 101 more efficient in assistance in dealing with conflict handling.
  • the UE 101 based on determining that the UE is configured with a configuration for persisting a conditional configuration after execution, the UE 101 releases the CPC configuration regardless of the configuration for persisting the conditional configuration. According to embodiments of the present disclosure, the UE 101 does not release the conditional configuration if the UE101 is a Release 18 UE and the NW intends the UE to perform back to back CHO or CPC without explicit RRC messages. In this case, special handling is needed by the Release 18, which preserves the conditional configuration.
  • the root cause of the problem is that MN 103 is not aware of configurations done by SN 105 with R16 CPC. With R18, there is persistence element.
  • the UE 101 configuration is always clearly aware at the NW, including MN 103 and via MN 103 to SN105. Based on this, it is proposed that if the Release 18 UE is configured with R16 CPC, once the condition is triggered, the R18 UE does not save this R16 CPC configuration.
  • the Release18 NW configuration asks UE to preserve the configuration, and does not apply to Rel-16 configuration.
  • the R16 CPC configuration is always released after execution, even in Release 18, while the other configurations are saved. This can make the proposal keep compatibility in the future.
  • the CPC configuration is a R16 or R17 CPC configuration. This way, it can keep compatibility in the future releases.
  • the MN 103 is a release 17 MN.
  • the SN 105 is a release 16 SN.
  • the CPC configuration is a release 16 CPC configuration. Additionally or alternatively, the CPC configuration is released after execution, even in release 18 or higher. This can avoid out of sync between UE 101 and NW, and make the proposal keep compatibility in the future.
  • the MN103 transmits (308) , using the transceiver to a user equipment (UE) , a first indication 310 to inform the base station whether a conditional primary secondary cell change (CPC) configuration from a secondary node (SN) is present or absent at the UE, the base station being a master node (MN) of the UE; and receives (324) , using the transceiver from the UE, a second indication 320 of existence or absence of the CPC configuration.
  • CPC conditional primary secondary cell change
  • the MN 103 based on receiving the indication of existence of the CPC configuration, the MN 103 also avoids transmitting a further CPC configuration to the UE.
  • the MN 301 avoids transmitting the further CPC configuration to the UE 101 can be implemented as: the MN 301 stops a CPC procedure initiated by the MN 301 or a release 17 SN. This way, CPC configuration conflict can be avoided in the UE, thus avoid out of sync between the UE and the NW.
  • the MN 103 also cancels avoidance of transmitting the further CPC configuration.
  • the MN 103 cancels avoidance of transmitting the further CPC configuration can be implemented as the MN 103 restarts a CPC procedure initiated by the MN or a release 17 SN. This way, the MN 103 can continue with the CPC configuration procedure, without conflict at UE101, and avoids out of sync between UE 101 and NW.
  • the first indication or the second indication is transmitted via UE assistance information. Additionally or alternatively, the first indication or the second indication is transmitted via a radio resource control (RRC) reconfiguration complete message.
  • RRC radio resource control
  • the MN 103 also transmits a UE capability enquiry to the UE 101 using the transceiver; and receives, using the transceiver from the UE 101, UE capability information indicating that the UE 101 is configured to inform the MN 103 whether the CPC configuration is present or absent at the UE.
  • the MN 103 can get UE capability information about the present or absence of the CPC configuration from the SN105, thus synchronizes situation between the UE 101 and the MN103, finally avoids out of sync between the UE 101 and the NW.
  • the MN 103 also transmits, using the transceiver to the UE, a third indication that the UE is configured to report presence or absence of the CPC configuration. This way, according to the third indication, the UE 101 can report back presence or absence of the CPC configuration, to avoid out of sync between the UE 101 and the NW.
  • the MN 103 based on determining that the UE is configured with a configuration for persisting a conditional configuration after execution, the MN 103 also releases the CPC configuration regardless of the configuration for persisting the conditional configuration, and persists the further CPC configuration.
  • the UE 101 does not release the conditional configuration if the UE101 is a Release 18 UE and the NW intends the UE to perform back-2-back CHO or CPC without explicit RRC messages. In this case, special handling is needed by the Release 18, which preserves the conditional configuration.
  • the root cause of the problem is that MN 103 is not aware of configurations done by SN 105 with R16 CPC. With R18, there is persistence element.
  • the UE 101 configuration is always clearly aware at the NW, including MN 103 and via MN 103 to SN105. Based on this, it is proposed that if the Release 18 UE is configured with R16 CPC, once the condition is triggered, the R18 UE does not save this R16 CPC configuration.
  • the Release18 NW configuration asks UE to preserve the configuration, and does not apply to Rel-16 configuration.
  • the R16 CPC configuration is always released after execution, even in Release 18, while the other configurations are saved. This can make the proposal keep compatibility in the future.
  • the MN is a release 17 MN.
  • the SN is a release 16 SN.
  • the CPC configuration is a release 16 CPC configuration.
  • the further CPC configuration is a release 17 CPC configuration initiated by the MN or a release 17 SN.
  • the CPC configuration and the further CPC configuration are released by the UE after execution. This can avoid out of sync between UE 101 and NW, and make the proposal keep compatibility in the future.
  • the UE 101 actually informs the MN 103 whenever the UE is configured with R16 CPC directly from SN 105.
  • This information to MN 103 can be provided in a UE Assistance Information or in a RRCREconfigComplete Message.
  • the MN 103 can prevent any MI-CPC or SI-CPC until the UE 101 informs MN 103 about the clearing of R16 CPC. This prevents the simultaneous configuration of R17 and R16 CPC. This whole operation at the UE can be protected by a UE capability.
  • the UE 101 informs to both MN 103 and SN 105 that it has implemented the feature where the UE 101 informs MN 103 whenever it is configured with a R16 CPC. And whenever the R16 CPC is cleared. As a variation, the UE 101 informs the R17 MN NW about the presence of R16 CPC configuration, only if the R17 MN NW has a field that allows the UE to report such R16 configuration of presence or absence. This way, the R17 NW which has not implemented this, would not be confused by the new indication from the UE 101. If the UE 101 informs the Release 17 MN 103 about the presence of R16 CPC configuration at the UE 101, the MN can stop any R17 CPC procedures and prevent such configuration to the UE. This includes rejecting any SN requests for SI-CPC while the R16 CPC is configured. This is resumed once the UE 101 informs that there is no R16 CPC configuration.
  • Fig. 4 illustrates an exemplary process flow 400 for NW handling with no R16 CPC according to some embodiments of the present disclosure.
  • UE 101 receives (412) UE capability enquiry 410 from the MN 103, and transmits (413) UE capability information 415 to MN103.
  • UE 101 also transmits (416) UE capability information 415 to MN103.
  • UE capability information 415 can be UE capability information indicating that the UE 101 is configured to inform the MN 103 whether the CPC configuration is present or absent at the UE.
  • UE 101 is in dual connection (DC) with MN103 and SN 105.
  • UE 101 receives (423) RRCReconfig with R17 MI-CPC 425 from MN103.
  • RRCReconfig with R17 MI-CPC 425 is a flag indicating UE to inform about status of R16 CPC.
  • RRCReconfig with R17 MI-CPC 425 from MN103 is the third indication that the UE 101 is configured to report presence or absence of the CPC configuration.
  • Information element for RRCReconfig with R17 MI-CPC 425 is in 761 in Fig. 7C.
  • UE 101 transmits (428) to the MN 103, RRCReconfigComple information 430 to the MN 103, about no information about R16 CPC.
  • RRCReconfigComple information 430 is the second indication of absence of the second CPC configuration to the MN.
  • the UE101 ignores R16 CPC from SN 105.
  • the UE 101 receives (457) from the SN 105 that R16 CPC configuration is released 455.
  • the MN 103 transmits (408) UE capability enquiry 410 to the UE 101, and receives (414) UE capability information 415 from UE 101.
  • MN 103 coordinates SN candidates for R17 MI-CPC.
  • MN 103 transmits (427) RRCReconfig with R17 MICPC message 425 to the UE 101, and receives (432) RRCReconfigComplete message 430 from UE 101.
  • the SN 105 receives (417) UE capability information 315 from UE 101.
  • the SN 105 transmits (453) to the UE 101 that that R16 CPC configuration is released 455.
  • Fig. 5 illustrates an exemplary process flow 500 for NW handling with UE assistance according to some embodiments of the present disclosure.
  • the UE 101, MN 103, SN 105, block 205, UE capability enquiry 410, UE capability information 415, RRCReconfig with R17 MI-CPC 425, block 420 are the same with in Fig. 4.
  • UE 101 transmits (512) RRCReconfigComplete message 510 to MN103, to inform about absence of the R16 CPC.
  • RRCReconfigComplete message 510 is a second indication of absence of the second CPC configuration to the MN.
  • UE101 receives (522) R16 CPC configuration 520 from SN 105.
  • R16 CPC configuration 520 is the second CPC configuration form SN105.
  • UE 101 transmits (523) RRCReconfigComplete or UEAssistanceInformation 525 to MN103, to inform MN about existing of R16 CPC.
  • the information element for RRCReconfigComplete is in 701 in Fig. 7A, for UE 101 to inform MN103 about existence or absence of R16 CPC configuration at UE 101.
  • RRCReconfigComplete or UEAssistanceInformation 525 is the first indication of existence of the CPC configuration to the MN.
  • UE 101 evaluates R16 CPC from SN 105.
  • UE101 transmits (537) RRCReconfigComplete message 540 to SN105, to inform that R16 CPC happened.
  • UE 101 transmits (543) RRCReconfigComplete or UEAssistanceInformation 545 to MN 103, to inform MN 103 about absence of R16 CPC.
  • MN103 receives (508) RRCReconfigComplete message 510 from UE 101, to inform about absence of the R16 CPC.
  • MN103 receives (527) RRCReconfigComplete or UEAssistanceInformation 525 from UE 101, to inform MN about existing of R16 CPC.
  • MN103 stops the MI or SI-CPC procedure.
  • MN 103 receives (547) RRCReconfigComplete or UEAssistanceInformation 545 from UE 101, to inform MN 103 about absence of R16 CPC.
  • MN103 restarts the MI or SI-CPC procedure.
  • UE105 coordinates R16 CPC candidates.
  • UE 105 transmits (518) R16 CPC configuration 520 to UE 101.
  • SN 105 receives (542) RRCReconfigComplete message 540 from UE 101, to inform that R16 CPC happened.
  • RRCReconfigComplete message 540 from UE 101, to inform that R16 CPC happened.
  • SN 105 can get CPC configuration situation from UE 101, and avoids out of sync from UE101.
  • Fig. 6 illustrates another exemplary process flow 600 for NW handling with UE assistance according to some embodiments of the present disclosure.
  • the difference from Fig. 6 and Fig. 5 is that there is no UE capability enquiry 410 or UE capability information 415 in Fig. 6.
  • the UE 101 informs the R17 MN NW 103 about the presence of R16 CPC configuration, only if the R17 MN 103 has a field that allows the UE 101 to report such R16 configuration of presence or absence. This way, the R17 MN 103 which has not implemented this, would not be confused by the new indication from the UE 101.
  • Fig. 8 illustrates another exemplary process flow 800 for NW handling of conflicting multiple conditional configurations according to some embodiments of the present disclosure.
  • MN103 transmits (808) first indication of existence of the first CPC configuration 810 to SN 105, and transmits (818) second indication of absence of the first CPC configuration 820 to SN 105.
  • the MN 103 in accordance with determining to transmit a first CPC configuration to the UE 101, transmits a first indication of existence of the first CPC configuration to the SN 105. In accordance with a determination that the first CPC configuration is released, the MN 103 transmits a second indication of absence of the first CPC configuration to the SN 103 using the transceiver.
  • the first indication is transmitted via a first SgNB modification request. Additionally or alternatively, the second indication is transmitted via a first SgNB modification request. This way, the situation can be synchronized between UE 101, MN 103 and SN 105, to avoid out of sync configuration, and keep flexibility.
  • the MN is a release 17 MN.
  • the SN is a release 16 MN.
  • the first CPC configuration is a release 17 CPC configuration initiated by the MN or a release 17 SN.
  • the second CPC configuration is a release 16 CPC configuration. This way, it can avoid out of sync configuration between UE 101 and NW.
  • SN 105 receives (812) first indication of existence of the first CPC configuration 810 from MN 103. At block 815, the SN 105 avoids transmitting a second CPC configuration to the UE 101. The SN 105 receives (822) the second indication of absence of the first CPC configuration from the MN103. At block 825, SN 105 cancels avoidance of transmitting the second CPC configuration. This way, the situation between UE 101, MN 103 and SN 105 can be synchronized, to avoid out of sync configuration.
  • SN 105 avoids transmitting the second CPC configuration can be implemented in the SN 105 stops coordinating CPC candidates for the second CPC configuration.
  • SN 105 cancels the avoidance of transmitting the second CPC configuration can be implemented in SN 105 resumes coordinating CPC candidates for the second CPC configuration. This way, the out of sync configuration between UE 101 and NW can be avoided.
  • the first indication is received via a first SgNB modification request. Additionally or alternatively, the second indication is received via a first SgNB modification request. This way, it provides flexibility in transmitting the first indication and the second indication.
  • the MN is a release 17 MN.
  • the SN is a release 16 MN.
  • the first CPC configuration is a release 17 CPC configuration initiated by the MN or a release 17 SN.
  • the second CPC configuration is a release 16 CPC configuration. This way, the out of sync issue can be avoided, and keep capability in the future releases.
  • the MN 103 can inform the SN 105 to release the R16 CPC configuration. This is using the SN modification request.
  • Fig. 9 illustrates an exemplary process flow 900 MN handling with SN assistance according to some embodiments of the present disclosure.
  • the UE 101, MN103, SN 105, block 205, block 420, and block 515 are all the same with Fig. 5.
  • the MN 103 transmits (908) SgNB modification request 910 to SN 107, to inform SN 107 about R17 CPC.
  • R17 MI-CPC is released at UE 101 N 103.
  • MN 103 transmits (923) SgNB modification request 925 to SN 105, to inform SN 105 about absence of R17 CPC.
  • the SN 105 stops coordinating R16 CPC candidates.
  • the SN 105 coordinates R16 CPC candidates.
  • Fig. 10 illustrates an exemplary method 1000 implemented at a UE according to some embodiments of the present disclosure.
  • UE 101 in accordance with a determination that a conditional primary secondary cell change (CPC) configuration from a secondary node (SN) is present at the UE, UE 101 transmits a first indication of existence of the CPC configuration to a master node (MN) using the transceiver.
  • MN master node
  • UE 101 transmits a second indication of absence of the second CPC configuration to the MN using the transceiver.
  • the UE 101 further receives, using the transceiver from the MN, an indication to inform the MN whether the CPC configuration is present or absent at the UE.
  • the second indication is transmitted via UE assistance information. Additionally or alternatively, the second indication is transmitted via a radio resource control (RRC) reconfiguration complete message.
  • RRC radio resource control
  • determining that the CPC configuration is present comprises: in accordance with receiving the second CPC configuration from the SN using the transceiver, determining that the CPC configuration is present.
  • the UE 101 determines that the CPC configuration is absent by: in accordance with a determination that the second CPC configuration is completed at the UE, determining that the CPC configuration is absent.
  • UE 101 further receives a UE capability enquiry from the MN using the transceiver; and based on receiving the UE capability enquiry, transmits, using the transceiver to the MN, UE capability information indicating that the UE is configured to inform the MN whether the CPC configuration is present or absent at the UE. According to embodiments of the present disclosure, UE 101 further transmits UE capability information to the SN using the transceiver.
  • UE 101 transmits the first indication and the second indication can be implemented in: in accordance with receiving, using the transceiver from the MN, a third indication that the UE is configured to report presence or absence of the CPC configuration, UE 101 transmits at least one of the first indication or the second indication to the MN using the transceiver.
  • UE 101 based on determining that the UE is configured with a configuration for persisting a conditional configuration after execution, UE 101 further releases the CPC configuration regardless of the configuration for persisting the conditional configuration.
  • the MN is a release 17 MN. Additionally or alternatively, the SN is a release 16 MN. Additionally or alternatively, the CPC configuration is a release 16 CPC configuration. Additionally or alternatively, the CPC configuration is released after execution.
  • Fig. 11 illustrates an exemplary method 1100 implemented at a MN according to some embodiments of the present disclosure.
  • MN 103 transmits, using the transceiver to a user equipment (UE) , a first indication to inform the base station whether a conditional primary secondary cell change (CPC) configuration from a secondary node (SN) is present or absent at the UE, the base station being a master node (MN) of the UE.
  • MN 103 receives, using the transceiver from the UE, a second indication of existence or absence of the CPC configuration.
  • CPC conditional primary secondary cell change
  • MN 103 based on receiving the indication of existence of the CPC configuration, MN 103 further avoids transmitting a further CPC configuration to the UE. According to embodiments of the present disclosure, MN 103 avoids transmitting the further CPC configuration by: stopping a CPC procedure initiated by the MN or a release 17 SN.
  • MN 103 based on receiving the indication of absence of the CPC configuration, MN 103 further cancels avoidance of transmitting the further CPC configuration.
  • MN 103 cancels avoidance of transmitting the further CPC configuration can be implemented in: MN 103 restarts a CPC procedure initiated by the MN or a release 17 SN.
  • at least one of the first indication or the second indication is transmitted via UE assistance information. Additionally or alternatively, at least one of the first indication or the second indication is transmitted via a radio resource control (RRC) reconfiguration complete message.
  • RRC radio resource control
  • MN103 further transmits a UE capability enquiry to the UE using the transceiver; and receives, using the transceiver from the UE, UE capability information indicating that the UE is configured to inform the MN whether the CPC configuration is present or absent at the UE.
  • MN103 further transmits, using the transceiver to the UE, a third indication that the UE is configured to report presence or absence of the CPC configuration.
  • MN 103 based on determining that the UE is configured with a configuration for persisting a conditional configuration after execution, MN 103 further releases the CPC configuration regardless of the configuration for persisting the conditional configuration, and persists the further CPC configuration.
  • the MN is a release 17 MN.
  • the SN is a release 16 SN.
  • the CPC configuration is a release 16 CPC configuration.
  • the further CPC configuration is a release 17 CPC configuration initiated by the MN or a release 17 SN. Additionally or alternatively, the CPC configuration and the further CPC configuration are released by the UE after execution.
  • Fig. 12 illustrates another exemplary method 1200 implemented at a MN according to some embodiments of the present disclosure.
  • MN 103 transmits a first indication of existence of the first CPC configuration to a secondary node (SN) of the UE using the transceiver, the base station being a master node (MN) of the UE.
  • MN 103 transmits a second indication of absence of the first CPC configuration to the SN using the transceiver.
  • the first indication is transmitted via a first SgNB modification request. Additionally or alternatively, the second indication is transmitted via a first SgNB modification request.
  • the MN is a release 17 MN. Additionally or alternatively, the SN is a release 16 MN. Additionally or alternatively, the first CPC configuration is a release 17 CPC configuration initiated by the MN or a release 17 SN. Additionally or alternatively, the second CPC configuration is a release 16 CPC configuration.
  • Fig. 13 illustrates an exemplary method 1300 implemented at a SN according to some embodiments of the present disclosure.
  • SN 105 in accordance with receiving a first indication of existence of a first conditional primary secondary cell (PSCell) change (CPC) configuration from a master node (MN) of a user equipment (UE) using the transceiver, SN 105 avoids transmitting a second CPC configuration to the UE, the base station being a secondary node (SN) of the UE.
  • SN 105 in accordance with receiving a second indication of absence of the first CPC configuration from the MN using the transceiver, SN 105 cancels avoidance of transmitting the second CPC configuration.
  • SN 105 avoids transmitting the second CPC configuration by: stopping coordinating CPC candidates for the second CPC configuration.
  • SN 105 cancels the avoidance of transmitting the second CPC configuration can be implemented in: SN 105 resumes coordinating CPC candidates for the second CPC configuration.
  • the first indication is received via a first SgNB modification request. Additionally or alternatively, the second indication is received via a first SgNB modification request.
  • the MN is a release 17 MN. Additionally or alternatively, the SN is a release 16 MN. Additionally or alternatively, the first CPC configuration is a release 17 CPC configuration initiated by the MN or a release 17 SN. Additionally or alternatively, the second CPC configuration is a release 16 CPC configuration.
  • Fig. 14 is a simplified block diagram of a device 1400 that is suitable for implementing embodiments of the present disclosure.
  • the UE 101, the MN 103 and the SN 105 can be implemented by the device 1400.
  • the device 1400 includes a processor 1410, a memory 1420 coupled to the processor 1410, and a transceiver 1240 coupled to the processor 1410.
  • the transceiver 1440 is for bidirectional communications.
  • the transceiver 1440 is coupled to at least one antenna to facilitate communication.
  • the transceiver 1440 can comprise a transmitter circuitry (e.g., associated with one or more transmit chains) and/or a receiver circuitry (e.g., associated with one or more receive chains) .
  • the transmitter circuitry and receiver circuitry can employ common circuit elements, distinct circuit elements, or a combination thereof.
  • the processor 1410 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples.
  • the device 1200 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.
  • the memory 1420 may include one or more non-volatile memories and one or more volatile memories.
  • the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1424, an electrically programmable read only memory (EPROM) , a flash memory, a hard disk, a compact disc (CD) , a digital video disk (DVD) , and other magnetic storage and/or optical storage.
  • the volatile memories include, but are not limited to, a random access memory (RAM) 1422 and other volatile memories that will not last in the power-down duration.
  • a computer program 1430 includes computer executable instructions that are executed by the associated processor 1410.
  • the program 1430 may be stored in the ROM 1424.
  • the processor 1410 may perform any suitable actions and processing by loading the program 1430 into the RAM 1422.
  • the embodiments of the present disclosure may be implemented by means of the program 1430 so that the device 1400 may perform any process of the disclosure as discussed with reference to Figs. 3-6 and 8-13.
  • the embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.
  • the present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium.
  • the computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target real or virtual processor, to carry out the method 1000 as described above with reference to Fig. 10 and/or the method 1100 as described above with reference to Fig. 11, and/or the method 1200 as described above with reference to Fig. 12, and/or the method 1300 as described above with reference to Fig. 13.

Landscapes

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

Abstract

Des modes de réalisation de la présente divulgation concernent une gestion de réseau (NW) et une assistance d'UE pour de multiples configurations conditionnelles conflictuelles. Selon des modes de réalisation de la présente divulgation, en fonction d'une détermination selon laquelle une configuration de changement de cellule secondaire primaire conditionnelle (CPC) à partir d'un nœud secondaire (SN) est présente au niveau de l'UE, l'UE transmet une première indication de présence de la configuration de CPC à un nœud maître (MN) à l'aide de l'émetteur-récepteur; et en fonction d'une détermination selon laquelle la configuration de CPC est absente au niveau de l'UE, l'UE transmet une seconde indication d'absence de la seconde configuration de CPC au MN à l'aide de l'émetteur-récepteur. De cette manière, la configuration de désynchronisation peut être évitée.
PCT/CN2022/111273 2022-08-09 2022-08-09 Gestion de réseau pour de multiples configurations conditionnelles conflictuelles WO2024031383A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/111273 WO2024031383A1 (fr) 2022-08-09 2022-08-09 Gestion de réseau pour de multiples configurations conditionnelles conflictuelles

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/111273 WO2024031383A1 (fr) 2022-08-09 2022-08-09 Gestion de réseau pour de multiples configurations conditionnelles conflictuelles

Publications (1)

Publication Number Publication Date
WO2024031383A1 true WO2024031383A1 (fr) 2024-02-15

Family

ID=89850044

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/111273 WO2024031383A1 (fr) 2022-08-09 2022-08-09 Gestion de réseau pour de multiples configurations conditionnelles conflictuelles

Country Status (1)

Country Link
WO (1) WO2024031383A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210099926A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Method and apparatus for conditional pscell change
WO2021162507A1 (fr) * 2020-02-13 2021-08-19 Lg Electronics Inc. Procédé et appareil pour transmettre un message de réponse dans un système de communication sans fil
US20210321310A1 (en) * 2020-04-09 2021-10-14 Samsung Electronics Co., Ltd. Method for handling conditional configuration stored in ue
US20210337449A1 (en) * 2020-04-27 2021-10-28 Qualcomm Incorporated Avoiding simultaneous conditional handover and conditional primary scg cell change

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210099926A1 (en) * 2019-09-26 2021-04-01 FG Innovation Company Limited Method and apparatus for conditional pscell change
WO2021162507A1 (fr) * 2020-02-13 2021-08-19 Lg Electronics Inc. Procédé et appareil pour transmettre un message de réponse dans un système de communication sans fil
US20210321310A1 (en) * 2020-04-09 2021-10-14 Samsung Electronics Co., Ltd. Method for handling conditional configuration stored in ue
US20210337449A1 (en) * 2020-04-27 2021-10-28 Qualcomm Incorporated Avoiding simultaneous conditional handover and conditional primary scg cell change

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Discussion on support of conditional PSCell change/addition", 3GPP DRAFT; R2-2010125, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. Online; 20201102 - 20201113, 22 October 2020 (2020-10-22), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051941553 *

Similar Documents

Publication Publication Date Title
US20240022375A1 (en) Coordinated positioning via sidelink resource
US10945176B2 (en) Method, device and computer program for primary cell change
US20230232494A1 (en) Methods of communication, terminal devices, network devices and computer readable media
WO2022178837A1 (fr) Fourniture de données d'aide au positionnement pour le positionnement d'un ue dans un état inactif de commande de ressources radioélectriques
US20230370910A1 (en) Serving cell change procedure utilizing multiple candidate target cells
WO2024031383A1 (fr) Gestion de réseau pour de multiples configurations conditionnelles conflictuelles
WO2023272744A1 (fr) Procédés, dispositifs et support de communication
US20240323797A1 (en) Conditional handover
US20240129987A1 (en) Methods, devices, and medium for communication
WO2022178853A1 (fr) Procédé, dispositif et support d'enregistrement informatique de communication
WO2024031363A1 (fr) Gestion d'ue de configurations conditionnelles multiples conflictuelles
WO2024148545A1 (fr) Rapport de mesure pour activation de cellule
WO2024168896A1 (fr) Gestion de support de transmission de petites données à terminaison mobile
WO2024093115A1 (fr) Dispositifs et procédés de communication
WO2022227039A1 (fr) Amélioration d'intervalle de mesure
US12127051B2 (en) Device, method, apparatus and computer readable medium for inter-master node handover
WO2023115424A1 (fr) Activation et désactivation de cellules secondaires
US20240259891A1 (en) Interruption time reduction
US20240357632A1 (en) Method, device and computer storage medium of communication
WO2024207248A1 (fr) Transmission de données de liaison descendante dans un état inactif
WO2024212064A1 (fr) Rapport de csi pour activation de cellule
WO2024093154A1 (fr) Dispositifs et procédés de communication
WO2024216457A1 (fr) Dispositifs, procédés, appareils et support lisible par ordinateur pour communication
US20240107390A1 (en) Configuration of successful primary secondary cell change report
WO2024065322A1 (fr) Positionnement

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: 22954359

Country of ref document: EP

Kind code of ref document: A1