Signaling for conditional primary / secondary cell addition / change configuration

Abstract

Aspects of the disclosure relate to wireless communications in which a master node (MN) or a secondary node (SN) can initiate a conditional addition of a primary secondary cell (PSCell) or a conditional change from one PSCell to another PSCell. Each candidate target PSCell can provide information used by the MN to generate a conditional PSCell addition (CPA) configuration or a conditional PSCell change (CPC) configuration sent to a user equipment (UE). The information can indicate an execution condition for each candidate target PSCell and / or a radio bearer supported or not supported by each candidate target PSCell. The MN can modify a master cell group (MCG) configuration of the PSCell based on information received from a target SN having a secondary cell group (SCG) configuration for the PSCell. The MN can send the CPA or CPC configuration including the modified MCG configuration and the SCG configuration to the UE.

Description

[0001] Cross-references to related applications

[0002] This patent application claims priority to Pending U.S. Nonprovisional Application No. 17 / 483,644, filed September 23, 2021, and U.S. Provisional Application No. 63 / 090,689, filed October 12, 2020, and assigns them to the assignee herein, which are hereby expressly incorporated by reference as if their entire contents were fully set forth below and used for all applicable purposes. Technical Field

[0003] The technologies discussed below generally relate to wireless communications, and more specifically to signaling associated with additions and / or changes in primary and secondary cell configurations. Background Technology

[0004] Next-generation wireless communication systems (e.g., 5GS) may include a 5G core network and a 5G radio access network (RAN), such as a new radio (NR)-RAN. NR-RAN supports communication via one or more cells. For example, wireless communication devices such as user equipment (UE) may access a first cell of a first base station (BS) (such as a gNB) and / or access a second cell of a second base station.

[0005] Different cells can serve the UE at different times. For example, initially, the UE can be served by a first group of cells. Subsequently, additional cells can be selected to serve the UE (e.g., to provide additional resources for serving the UE). Alternatively or additionally, the cell currently serving the UE can be changed (switched out), so that different cells will serve the UE. Summary of the Invention

[0006] The following provides an overview of one or more aspects of this disclosure to offer a basic understanding of these aspects. This overview is not a comprehensive summary of all intended features of this disclosure, and its purpose is neither to identify key or essential elements of all aspects of this disclosure, nor to describe the scope of any or all aspects of this disclosure. Its sole purpose is to present some concepts of one or more aspects of this disclosure in the form of a preface to a more detailed description that will follow.

[0007] In some examples, a method for wireless communication at a device is disclosed. The method may include obtaining from a target secondary node (SN) a set of secondary cell group (SCG) configurations and associated information for a target primary / secondary cell (PSCell) identified as a user equipment, modifying the primary cell group (MCG) configuration of the target PSCell based on the associated information set, and outputting a conditional PSCell Addition (CPA) configuration including the MCG and SCG configurations for the target PSCell, or a conditional PSCell Change (CPC) configuration including the MCG and SCG configurations for the target PSCell, for transmission to the user equipment.

[0008] In some examples, the apparatus for wireless communication may include an interface and a processing system coupled to the interface. The processing system may be configured to obtain, via the interface, a set of secondary cell group (SCG) configurations and associated information for a target primary / secondary cell (PSCell) identified for a user equipment from a target secondary node (SN), modify the primary cell group (MCG) configuration of the target PSCell based on the set of associated information, and output via the interface a conditional primary / secondary cell addition (CPA) configuration including the MCG and SCG configurations for the target PSCell or a conditional PSCell change (CPC) configuration including the MCG and SCG configurations for the target PSCell for transmission to the user equipment.

[0009] In some examples, an apparatus for wireless communication may include components for obtaining from a target secondary node (SN) a set of secondary cell group (SCG) configuration and associated information for a target primary / secondary cell (PSCell) identified for a user equipment, components for modifying the primary cell group (MCG) configuration of the target PSCell based on the associated information set, and components for outputting a conditional PSCell Addition (CPA) configuration including the MCG configuration and SCG configuration for the target PSCell or a conditional PSCell Change (CPC) configuration including the MCG configuration and SCG configuration for the target PSCell for transmission to the user equipment.

[0010] In some examples, an article of manufacture used by an apparatus for wireless communication includes a non-transitory computer-readable medium storing instructions executable by one or more processors of the apparatus to obtain from a target secondary node (SN) a set of secondary cell group (SCG) configurations and associated information for a target primary / secondary cell (PSCell) identified as a user equipment, modify the primary cell group (MCG) configuration of the target PSCell based on the set of associated information, and output a conditional primary / secondary cell (PSCell) add (CPA) configuration including the MCG configuration and SCG configuration for the target PSCell or a conditional PSCell change (CPC) configuration including the MCG configuration and SCG configuration for the target PSCell for transmission to the user equipment.

[0011] In some examples, a method for wireless communication at a device is disclosed. This method may include obtaining a secondary node (SN) add request confirmation message including an identifier of a target primary / secondary cell (PSCell), and outputting a conditional PSCell add (CPA) configuration generated based on that identifier for transmission to a user equipment.

[0012] In some examples, the apparatus for wireless communication may include an interface and a processing system coupled to the interface. The processing system may be configured to obtain a secondary node (SN) add request acknowledgment message including the identifier of the target primary / secondary cell (PSCell) via the interface, and to output a conditional PSCell add (CPA) configuration generated based on the identifier via the interface for transmission to the user equipment.

[0013] In some examples, an apparatus for wireless communication may include components for obtaining a secondary node (SN) add request confirmation message including an identifier of a target primary / secondary cell (PSCell), and components for outputting a conditional PSCell add (CPA) configuration generated based on the identifier for transmission to a user equipment.

[0014] In some examples, an article of manufacture used by a device for wireless communication includes a non-transitory computer-readable medium containing instructions executable by one or more processors of the device to obtain a secondary node (SN) add request confirmation message including an identifier of a target primary / secondary cell (PSCell), and outputs a conditional PSCell add (CPA) configuration generated based on the identifier for transmission to a user equipment.

[0015] These and other aspects of this disclosure will become more fully understood upon review of the following detailed description. Other aspects, features, and examples of this disclosure will become apparent to those skilled in the art from the following description of specific, exemplary aspects of this disclosure in conjunction with the accompanying drawings. While features of this disclosure may be discussed with respect to certain examples and figures below, all examples of this disclosure may include one or more advantageous features discussed herein. In other words, when one or more examples can be discussed as having certain advantageous features, one or more such features may also be used according to the various examples of this disclosure discussed herein. Similarly, while exemplary aspects may be discussed below as examples of devices, systems, or methods, it should be understood that such exemplary aspects can be implemented in various devices, systems, and methods. Attached Figure Description

[0016] Figure 1 It is a schematic diagram of a wireless communication system based on some aspects.

[0017] Figure 2 This is a conceptual diagram based on some aspects of a radio access network.

[0018] Figure 3 This is a schematic diagram illustrating an example of utilizing radio resources in an air interface of orthogonal frequency division multiplexing (OFDM) based on certain aspects.

[0019] Figure 4 This is a block diagram illustrating an example of a wireless communication system based on some aspects.

[0020] Figure 5 It is a conceptual diagram of wireless communication via multiple radio frequency (RF) carriers based on some aspects.

[0021] Figure 6 It is a conceptual diagram based on some aspects of primary cell group (MCG) and secondary cell group (SCG).

[0022] Figure 7 This is a signaling diagram illustrating an example of signaling added to a conditional primary / secondary cell (PSCell) initiated by a primary node (MN) based on certain aspects.

[0023] Figure 8 and Figure 9 This is a signaling diagram illustrating an example of signaling that changes the conditional PSCell initiated by a secondary node (SN) based on some aspects.

[0024] Figure 10 and Figure 11 This is a signaling diagram illustrating an example of signaling changes to the PSCell initiated by the MN based on certain aspects.

[0025] Figure 12 This is a signaling diagram illustrating an example of signaling where the SN-initiated condition PSCell changes based on some aspects of the MN-involved SN-initiated condition PSCell.

[0026] Figure 13 This is a block diagram illustrating an example of the hardware implementation of a base station using a processing system based on some aspects.

[0027] Figure 14 This is a flowchart illustrating an example method of modifying configurations based on several aspects.

[0028] Figure 15 This is a flowchart illustrating an example method for providing configuration based on some aspects.

[0029] Figure 16 This is a flowchart illustrating an example method that provides execution conditions based on some aspects.

[0030] Figure 17 This is a flowchart illustrating an example method for modifying a cell group based on several aspects.

[0031] Figure 18 This is a flowchart illustrating an example method for configuring primary and secondary cells based on several aspects.

[0032] Figure 19 This is a flowchart illustrating another example method for configuring primary and secondary cells based on several aspects. Detailed Implementation

[0033] The specific embodiments described below with reference to the accompanying drawings are intended as descriptions of various configurations and are not intended to represent the only configuration in which the concepts described herein can be practiced. Specific details are included to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0034] While aspects and examples are described herein by way of illustration of a few examples, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects and / or uses may be implemented via integrated chip examples and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a particular use case or application, broad applicability of the described innovations may be possible. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and may also include aggregated, distributed, or original equipment manufacturer (OEM) devices or systems that integrate one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features must also include additional components and features for implementing and practicing the claimed and described examples. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors(s), interleavers, adders / summers, etc.). The innovations described herein are expected to be implemented in devices, chip-level components, systems, distributed deployments, end-user equipment, etc., of various sizes, shapes, and constructions.

[0035] In a wireless communication system with a primary node (MN) and at least one secondary node (SN), the MN or SN can initiate conditional addition of a primary / secondary cell (PSCell) or conditional change from one PSCell to another. In some examples, the MN sends an SN add request message for conditional PSCell addition (CPA) to one or more candidate target SNs. In some examples, the MN sends an SN add request message for conditional PSCell change (CPC) to one or more candidate target SNs. In some examples, the source SN sends a CPC SN change request message to the MN, and in response, the MN sends an SN add request message to one or more candidate target SNs. In any of these cases, each candidate target PSCell can acknowledge the add request with information that will be used for CPA or CPC configuration. In some examples, this information may indicate the execution conditions for each candidate target PSCell and / or may indicate the radio bearers supported by each candidate target PSCell.

[0036] In some examples, the source SN sends a CPC SN modification request message to the MN. The SN modification request message may include information used for CPC configuration. Optionally, in response to the SN modification request message, the MN may send a corresponding SN modification request message to the source SN. In response, the source SN may acknowledge the modification request with information that will be used for CPC configuration. In some examples, this information may indicate the execution conditions of each candidate target PSCell and / or may indicate the radio bearers supported by each candidate target PSCell.

[0037] In any of the above scenarios, the MN can generate a CPA configuration or CPC configuration based on the received information and send the configuration to the user equipment (UE). In some examples, the configuration can identify at least one candidate target PSCell and the execution conditions for each candidate target PSCell.

[0038] When the UE receives a message indicating that the execution conditions (e.g., addition / change conditions) of a candidate target PSCell have been met, the MN can send an acknowledgment message associated with the addition / change of the condition PSCell to the selected candidate target PSCell or the source SN. After reconfiguring the network with the addition / change of the PSCell, the UE can perform a random access procedure for the selected PSCell to establish a connection with that PSCell.

[0039] In some examples, the MN receives the corresponding secondary cell group (SCG) configuration and relevant information for each target PSCell from the target SN. For each target PSCell, the MN can modify the corresponding primary cell group (MCG) configuration based on the associated information received from the target SN with the corresponding SCG configuration. The MN can then send CPA or CPC configuration to the UE. Here, the CPA or CPC configuration for a given target PSCell may include the modified MCG and SCG configurations for that target PSCell.

[0040] In some examples, the MN can receive an SN add request confirmation message that includes at least one identifier of the candidate PSCell. In this case, the MN can send a CPA configuration generated based on at least one identifier to the UE.

[0041] The various concepts presented throughout this disclosure can be implemented in a wide range of telecommunications systems, network architectures, and communication standards. Reference is now made to... Figure 1As an unrestricted illustrative example, reference is made to a wireless communication system 100 to illustrate various aspects of this disclosure. The wireless communication system 100 includes three interaction domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. With the aid of the wireless communication system 100, the UE 106 can communicate data with an external data network 110 (such as, but not limited to, the Internet).

[0042] RAN 104 can implement any suitable wireless communication technology or multiple technologies to provide radio access to UE 106. As an example, RAN 104 can operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specification (commonly referred to as 5G). As another example, RAN 104 can operate under a hybrid of 5G NR and the Evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, commonly referred to as Long Term Evolution (LTE). 3GPP refers to this hybrid RAN as Next Generation RAN or NG-RAN. Of course, many other examples can be used within the scope of this disclosure.

[0043] As shown in the figure, RAN 104 includes multiple base stations 108. Broadly speaking, a base station is a network element in a radio access network responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, those skilled in the art may refer to a base station as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), node B (NB), eNode B (eNB), gNode B (gNB), transmit and receive point (TRP), or some other suitable terminology. In some examples, a base station may include two or more TRPs that can be co-located or non-co-located. Each TRP can communicate on the same or different carrier frequencies within the same or different frequency bands. In an example where RAN 104 operates according to both LTE and 5G NR standards, one base station may be an LTE base station, while the other may be a 5G NR base station.

[0044] RAN 104 is also shown as supporting wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a User Equipment (UE), but those skilled in the art may also refer to it as a Mobile Station (MS), Subscriber Station, Mobile Unit, Subscriber Unit, Radio Unit, Remote Unit, Mobile Device, Radio Equipment, Wireless Communication Equipment, Remote Equipment, Mobile Subscriber Station, Access Terminal (AT), Mobile Terminal, Radio Terminal, Remote Terminal, Handheld Device, Terminal, User Agent, Mobile Client, Client, or some other suitable term. A UE can be a device (e.g., a mobile device) that provides users with access to network services.

[0045] In this disclosure, a “mobile” device need not be capable of movement and may be stationary. The term mobile device or mobile equipment broadly refers to a variety of devices and technologies. A UE may include multiple hardware structural components whose size, shape, and arrangement facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile devices, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal computers (PCs), notebook computers, netbooks, smartbooks, tablets, personal digital assistants (PDAs), and a wide array of embedded systems, such as those corresponding to the “Internet of Things” (IoT).

[0046] Mobile devices can also be automobiles or other transportation vehicles, remote sensors or actuators, robots or robotic equipment, satellite radios, Global Positioning System (GPS) devices, object tracking devices, drones, multirotors, quadcopters, remote control devices, consumer and / or wearable devices (such as glasses, wearable cameras, virtual reality devices, smartwatches, health or fitness trackers), digital audio players (e.g., MP3 players), cameras, game consoles, etc. Mobile devices can also be digital home or smart home devices such as home audio, video and / or multimedia equipment, appliances, vending machines, smart lighting, home security systems, smart meters, etc. Mobile devices can also be smart energy devices, security devices, solar panels or solar arrays, municipal infrastructure equipment controlling electricity (e.g., smart grids), lighting, water, etc., industrial automation and enterprise equipment, logistics controllers and / or agricultural equipment, etc. Furthermore, mobile devices can provide connected medical or telemedicine support, such as telemedicine services. Remote health devices may include remote health monitoring devices and remote health management devices, whose communications may be given priority processing or access relative to other types of information, such as priority access to the transmission of critical service data and / or QoS aspects related to the transmission of critical service data.

[0047] Wireless communication between RAN 104 and UE 106 can be described as utilizing an air interface. Transmissions via the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., similar to UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of this disclosure, the term downlink can refer to point-to-multipoint transmissions originating from a base station (e.g., base station 108). Another way to describe this scheme is to use the term broadcast channel multiplexing. Transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to further aspects of this disclosure, the term uplink can refer to point-to-point transmissions originating from a UE (e.g., UE 106).

[0048] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication between some or all devices and equipment within its service area or cell. In this disclosure, as further discussed below, the scheduling entity may be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more scheduling entities (e.g., UE 106). That is, for scheduled communication, multiple UEs 106 may utilize resources allocated by the scheduling entity 108.

[0049] Base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduling entities (e.g., one or more other UEs). For example, a UE can communicate directly with other UEs in a peer-to-peer or device-to-device manner and / or in a relay configuration.

[0050] like Figure 1 As shown, scheduling entity 108 can broadcast downlink service 112 to one or more scheduling entities (e.g., one or more UEs 106). Broadly speaking, scheduling entity 108 is a node or device responsible for scheduling services in a wireless communication network, including downlink service 112 and, in some examples, uplink service 116 from one or more scheduling entities (e.g., one or more UEs 106) to scheduling entity 108. On the other hand, a scheduled entity (e.g., UE 106) is a node or device that receives downlink control information 114 from another entity in the wireless communication network (such as scheduling entity 108). This downlink control information includes, but is not limited to, scheduling information (e.g., authorization), synchronization or timing information, or other control information. Scheduled entity 106 can also send uplink control information 118 to scheduling entity 108, including, but not limited to, scheduling requests or feedback information, or other control information.

[0051] Furthermore, uplink control information 118 and / or downlink control information 114 and / or downlink traffic 112 and / or uplink traffic 116 can be transmitted on a waveform that can be time-divided into frames, subframes, time slots, and / or symbols. As used herein, a symbol can refer to a time unit in an orthogonal frequency division multiplexing (OFDM) waveform where each subcarrier carries a resource element (RE). A time slot can carry 7 or 14 OFDM symbols. A subframe can refer to a duration of 1 millisecond (ms). Multiple subframes or time slots can be grouped together to form a single frame or radio frame. In this disclosure, a frame can refer to a predetermined duration (e.g., 10 milliseconds) for wireless transmission, where each frame consists of, for example, 10 subframes of 1 millisecond (ms). Of course, these definitions are not required, and any suitable scheme for organizing the waveform can be used, and various time divisions of the waveform can have any suitable duration.

[0052] Typically, base station 108 may include a backhaul interface for communicating with the backhaul section 120 of wireless communication system 100. Backhaul section 120 provides a link between base station 108 and core network 102. Furthermore, in some examples, the backhaul network may provide interconnection between the individual base stations 108. Various types of backhaul interfaces can be used, such as a direct physical connection using any suitable transport network, a virtual network, or the like.

[0053] Core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some examples, core network 102 may be configured according to 5G standards (e.g., 5GC). In other examples, core network 102 may be configured according to 4G Evolved Packet Core (EPC) or any other suitable standard or configuration.

[0054] Now for reference Figure 2 As an unrestricted illustrative example, a schematic diagram of a radio access network (RAN) 200 according to some aspects of this disclosure is provided. In some examples, the RAN 200 may be consistent with the one described above and Figure 1 The same as RAN 104 shown in the figure.

[0055] The geographic area covered by RAN 200 can be divided into multiple cellular areas (cells), which can be uniquely identified by user equipment (UE) based on an identifier broadcast in the geographic area from an access point or base station. Figure 2Units 202, 204, 206, and 208 are shown, each unit may include one or more sectors (not shown). A sector is a sub-region of a unit. All sectors within a cell are served by the same base station. Radio links within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by antenna groups, and each antenna is responsible for communicating with UEs in a portion of the cell.

[0056] Various base station deployment methods can be used. For example, in Figure 2 In the examples shown, two base stations, base station 210 and base station 212, are illustrated in cells 202 and 204. A third base station, base station 214, is shown as a remote radio head (RRH) 216 controlling cell 206. That is, the base station can have an integrated antenna, or it can be connected to an antenna or RRH 216 via a feeder cable. In the illustrated example, cells 202, 204, and 206 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Furthermore, base station 218 is shown in cell 208, which can overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell (e.g., microcell, picocell, femtocell, home base station, home node B, home eNodeB, etc.) because base station 218 supports cells with relatively small sizes. Cell size can be determined based on system design and component constraints.

[0057] It should be understood that RAN 200 can include any number of radio base stations and cells. Furthermore, relay nodes can be deployed to extend the size or coverage area of ​​a given cell. Base stations 210, 212, 214, and 218 provide radio access points to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 can be integrated with those described above and... Figure 1 The scheduling entity 108 shown is the same as or similar to that shown.

[0058] Figure 2 It also includes an unmanned aerial vehicle (UAV) 220, which can be a drone or a quadcopter. The UAV 220 can be configured to be used as a base station, or more specifically as a mobile base station. That is, in some examples, the cell may not have to be stationary, and the geographical area of ​​the cell may move depending on the location of the mobile base station, such as the UAV 220.

[0059] Within RAN 200, a cell may include UEs capable of communicating with one or more sectors of each cell. Furthermore, each base station 210, 212, 214, 218 and UAV 220 may be configured to provide access to the core network 102 (see [link to core network 102]) for all UEs within the respective cell. Figure 1Access points. For example, UEs 222 and 224 can communicate with base station 210; UEs 226 and 228 can communicate with base station 212; UEs 230 and 232 can communicate with base station 214 via RRH 216; UE 234 can communicate with base station 218; and UE 236 can communicate with mobile base stations, such as UAV 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240 and / or 242 can communicate with the access points described above and... Figure 1 The UE / scheduled entity 106 shown is the same or similar. In some examples, UAV 220 (e.g., a quadcopter) can be a mobile network node and can be configured to act as a UE. For example, UAV 220 can operate within cell 202 by communicating with base station 210.

[0060] In a further aspect of RAN 200, sidelink signals can be used between UEs without relying on scheduling or control information from the base station. For example, sidelink communication can be used in device-to-device (D2D) networks, peer-to-peer (P2P) networks, vehicle-to-vehicle (V2V) networks, vehicle-to-everything (V2X) networks, and / or other suitable sidelink networks. For instance, two or more UEs (e.g., UEs 238, 240, and 242) can communicate with each other using sidelink signal 237 without relaying the communication through the base station. In some examples, UEs 238, 240, and 242 can each act as a scheduling entity or transmitting sidelink device and / or a scheduled entity or receiving sidelink device to schedule resources and transmit sidelink signal 237 therebetween, without relying on scheduling or control information from the base station. In other examples, two or more UEs (e.g., UEs 226 and 228) within the coverage area of ​​a base station (e.g., base station 212) may also transmit sidelink signals 227 via a direct link (sidelink) without transmitting the communication through base station 212. In this example, base station 212 may allocate resources for sidelink communication to UEs 226 and 228.

[0061] In RAN 200, the ability of a UE to communicate while moving, independent of its location, is referred to as mobility. Various physical channels between the UE and RAN 200 are typically established, maintained, and released under the control of the Access and Mobility Management Function (AMF). In some scenarios, the AMF may include a Security Context Management Function (SCMF) and a Security Anchor Function (SEAF) that performs authentication. The SCMF can manage the security context of both control plane and user plane functions, either fully or partially.

[0062] In various aspects of this disclosure, RAN 200 can utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the UE's connection is transferred from one radio channel to another). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Based on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another, or if the signal quality from a neighboring cell exceeds that from the serving cell within a given time period, the UE can perform a handover or handover from the serving cell to a neighboring (target) cell. For example, UE 224 can move from a geographic area corresponding to its serving cell 202 to a geographic area corresponding to a neighboring cell 206. When the signal strength or quality from the neighboring cell 206 exceeds the signal strength and quality of its serving cell 202 within a given time period, UE 224 can send a report message indicating this situation to its serving base station 210. In response, UE 224 can receive a handover command and the UE can undergo a handover to cell 206.

[0063] In a network configured for UL-based mobility, the network can utilize UL reference signals from each UE to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 can broadcast uniform synchronization signals (e.g., a uniform primary synchronization signal (PSS), a uniform secondary synchronization signal (SSS), and a uniform physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 can receive the uniform synchronization signals, derive carrier frequencies and time slot timings from the synchronization signals, and transmit uplink pilots or reference signals in response to the derived timings. The uplink pilot signal transmitted by a UE (e.g., UE 224) can be simultaneously received by two or more cells within RAN 200 (e.g., base stations 210 and 214 / 216). Each cell can measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within the core network) can determine the serving cell for UE 224. When UE 224 moves through RAN 200, RAN 200 can continue to monitor the uplink pilot signals transmitted by UE 224. When the signal strength or quality of the pilot signals measured by the neighboring cell exceeds the signal strength and quality measured by the serving cell, RAN 200 can switch UE 224 from the serving cell to the neighboring cell with or without notifying UE 224.

[0064] Although the synchronization signals transmitted by base stations 210, 212, and 214 / 216 can be uniform, the synchronization signals do not need to identify a specific cell. Instead, they can identify an area of ​​multiple cells operating at the same frequency and / or with the same timing. The use of areas in 5G networks or other next-generation communication networks enables an uplink-based mobility framework and improves the efficiency of both the UE and the network because the number of mobility messages that need to be exchanged between the UE and the network can be reduced.

[0065] In various implementations, the air interface in the radio access network 200 can utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum typically provides exclusive rights to a portion of the spectrum through a license purchased by the mobile network operator from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. While certain technical rules are usually still required to access unlicensed spectrum, access is generally available to any operator or device. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum can still be shared by multiple operators and / or multiple RATs. For example, a licensee of a portion of a licensed spectrum can provide a Licensed Shared Access (LSA) to share the spectrum with other parties, for example, by obtaining access under conditions determined by the appropriate licensor.

[0066] Devices communicating in the radio access network 200 can utilize one or more multiplexing techniques and multiple access algorithms to achieve simultaneous communication between various devices. For example, the 5G NR specification provides multiple access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing for DL ​​transmissions from base station 210 to one or more UEs 222 and 224, utilizing Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP). Furthermore, for UL transmissions, the 5G NR specification provides support for Discrete Fourier Transform Extended OFDM (DFT-s-OFDM) with CP (also known as Single-Carrier FDMA (SC-FDMA)). However, within the scope of this disclosure, multiplexing and multiple access are not limited to the above schemes and can be provided using Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Sparse Code Multiple Access (SCMA), Resource Extended Multiple Access (RSMA), or other suitable multiple access schemes. In addition, time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM) or other suitable multiplexing schemes can be used to provide multiplexed DL transmission from base station 210 to UEs 222 and 224.

[0067] Devices in the radio access network 200 can also utilize one or more duplex algorithms. Duplex refers to a point-to-point communication link where two endpoints can communicate with each other in both directions. Full-duplex means that two endpoints can communicate with each other simultaneously. Half-duplex means that only one endpoint can send information to the other endpoint at a time. Half-duplex simulation is often used for wireless links using Time Division Duplex (TDD). In TDD, time division multiplexing is used to separate transmissions in different directions on a given channel from each other. That is, in some cases, the channel is dedicated to transmissions in one direction, and in other cases, the channel is dedicated to transmissions in the other direction, where the direction may change very rapidly, for example, several times per time slot. In wireless links, full-duplex channels typically rely on physical isolation between the transmitter and receiver, as well as appropriate interference cancellation techniques. Full-duplex simulation for wireless links is often implemented using Frequency Division Duplex (FDD) or Space Division Duplex (SDD). In FDD, transmissions in different directions can operate at different carrier frequencies (e.g., within paired spectrum). In SDD, space division multiplexing (SDM) is used to separate transmissions in different directions on a given channel from each other. In other examples, full-duplex communication can be implemented in unpaired spectrum (e.g., within a single carrier bandwidth), where transmissions in different directions occur within different subbands of the carrier bandwidth. This type of full-duplex communication may be referred to herein as Subband Full-Duplex (SBFD), also known as Flexible Duplex.

[0068] Reference Figure 3 The OFDM waveforms illustrated herein are used to describe aspects of this disclosure. Those skilled in the art will understand that aspects of this disclosure can be applied to SC-FDMA waveforms in substantially the same manner as described below. That is, while some examples of this disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to SC-FDMA waveforms.

[0069] Now for reference Figure 3 An extended view of exemplary subframe 302 is shown, illustrating the OFDM resource grid. However, as those skilled in the art will readily understand, the physical (PHY) layer transport architecture for any particular application can differ from the example described herein, depending on any number of factors. Here, time is in the horizontal direction in units of OFDM symbols; and frequency is in the vertical direction in units of subcarriers of a carrier.

[0070] Resource grid 304 can be used to schematically represent the time-frequency resources of a given antenna port. That is, in a multiple-input multiple-output (MIMO) implementation with multiple antenna ports available, a corresponding number of resource grids 304 can be used for communication. Resource grid 304 is divided into multiple resource elements (REs) 306. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part in the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation used in a particular implementation, each RE can represent one or more bits of information. In some examples, a block of REs may be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 308, which contains any suitable number of consecutive subcarriers in the frequency domain. In one example, an RB may include 12 subcarriers, a number independent of the parameter set used. In some examples, depending on the parameter set, an RB may include any suitable number of consecutive OFDM symbols in the time domain. In this disclosure, it is assumed that a single RB (such as RB 308) corresponds exactly to a single communication direction (transmission or reception for a given device).

[0071] A set of contiguous or non-contiguous resource blocks may be referred to herein as a resource block group (RBG), subband, or bandwidth portion (BWP). A set of subbands or BWPs may span the entire bandwidth. Scheduling a scheduled entity (e.g., a UE) for downlink, uplink, or sidelink transmission typically involves scheduling one or more resource elements 306 within one or more subbands or bandwidth portions (BWPs). Therefore, a UE typically utilizes only a subset of resource grid 304. In some examples, an RB may be the smallest resource unit that can be allocated to a UE. Therefore, the more RBs scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of the UE. RBs may be scheduled by the base station (e.g., gNB, eNB, etc.) or may be scheduled by the UE itself implementing D2D sidelink communication.

[0072] In this illustration, RB 308 is shown occupying less than the entire bandwidth of subframe 302, and some subcarriers are illustrated above and below RB 308. In a given implementation, subframe 302 can have a bandwidth corresponding to any number of one or more RB 308s. Furthermore, in this illustration, RB 308 is shown occupying less than the entire duration of subframe 302, although this is merely one possible example.

[0073] Each 1ms subframe 302 can consist of one or more adjacent time slots. Figure 3In the example shown, a subframe 302 includes four time slots 310, as an illustrative example. In some examples, time slots can be defined based on a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot may include 7 or 14 OFDM symbols with a nominal CP. Additional examples may include micro-time slots, sometimes referred to as shortened transmission time intervals (TTIs), with a shorter duration (e.g., one to three OFDM symbols). These micro-time slots or shortened transmission time intervals (TTIs) may be transmitted in some cases, occupying resources scheduled for ongoing time slot transmissions of the same or different UEs. Any number of resource blocks can be utilized within a subframe or time slot.

[0074] An enlarged view of one of the time slots 310 shows a time slot 310 including a control area 312 and a data area 314. Typically, the control area 312 can carry a control channel, while the data area 314 can carry a data channel. Of course, a time slot can contain all DLs, all ULs, or at least one DL portion and at least one UL portion. Figure 3 The structure shown is merely exemplary and different time slot structures can be used, and may include one or more of each of the control region(s) and data regions(s).

[0075] although Figure 3 Although not shown, the various REs 306 within RB 308 can be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 306 within RB 308 can also carry pilot or reference signals. These pilot or reference signals can be provided to the receiving equipment to perform channel estimation for the corresponding channel, which enables coherent demodulation / detection of the control and / or data channels within RB 308.

[0076] In some examples, time slot 310 can be used for broadcast, multicast, groupcast, or unicast communication. For example, broadcast, multicast, or groupcast communication can refer to point-to-multipoint transmission from one device (e.g., a base station, UE, or other similar device) to other devices. Here, broadcast communication is delivered to all devices, while multicast or groupcast communication is delivered to multiple intended receiving devices. Unicast communication can refer to point-to-point transmission from one device to a single other device.

[0077] In an example of cellular communication over a cellular carrier via the Uu interface, for DL ​​transmission, a scheduling entity (e.g., a base station) may allocate one or more REs 306 (e.g., within control area 312) to transmit DL control information, including one or more DL control channels (e.g., Physical Downlink Control Channel (PDCCH)), to one or more scheduling entities (e.g., UEs). The PDCCH carries downlink control information (DCI), including but not limited to power control commands (e.g., one or more open-loop power control parameters and / or one or more closed-loop power control parameters), scheduling information, grants, and / or assignments of REs for DL ​​and UL transmissions. The PDCCH may also carry Hybrid Automatic Repeat Request (HARQ) feedback transmissions, such as acknowledgment (ACK) or negative acknowledgment (NACK). HARQ is a technique well-known to those skilled in the art, where the integrity of packet transmissions can be checked at the receiving side to ensure accuracy, for example, using any suitable integrity checking mechanism, such as checksums or cyclic redundancy checks (CRC). If the integrity of the transmission is acknowledged, an ACK can be sent, and if it is not acknowledged, a NACK can be sent. In response to NACK, the transmitting device can send HARQ retransmissions, which can achieve chase merging, incremental redundancy, and other functions.

[0078] The base station can further allocate one or more REs 306 (e.g., in control area 312 or data area 314) to carry other DL signals, such as demodulation reference signals (DMRS); phase tracking reference signals (PT-RS); channel state information (CSI) reference signals (CSI-RS); and synchronization signal blocks (SSBs). SSBs can be broadcast at regular intervals based on periodicity (e.g., 5, 10, 20, 40, 80, or 160 ms). SSBs include the primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast control channel (PBCH). The UE can utilize the PSS and SSS to achieve radio frame, subframe, time slot, and symbol synchronization in the time domain, identify the channel (system) bandwidth center in the frequency domain, and identify the cell's physical cell identifier (PCI).

[0079] The PBCH in the SSB may also include a Master Information Block (MIB), which includes various system information and parameters for decoding the System Information Block (SIB). The SIB may be, for example, System Information Type 1 (SIB1) that may include various additional system information. Together, the MIB and SIB1 provide the minimum system information (SI) for initial access. Examples of system information transmitted in the MIB may include, but are not limited to, subcarrier spacing (e.g., default downlink parameter set), system frame number, configuration of the PDCCH control resource set (CORESET) (e.g., PDCCH CORESET0), cell prohibition indicator, cell reselection indicator, raster offset, and the search space of SIB1. Examples of residual minimum system information (RMSI) transmitted in SIB1 may include, but are not limited to, random access search space, paging search space, downlink configuration information, and uplink configuration information. The base station may also transmit other system information (OSI).

[0080] In UL transmissions, the scheduled entity (e.g., the UE) may utilize one or more RE 306s to carry UL control information (UCI), which includes one or more UL control channels to the scheduling entity, such as the Physical Uplink Control Channel (PUCCH). UCIs may include various packet types and categories, including pilots, reference signals, and information configured to enable or assist in decoding uplink data transmissions. Examples of uplink reference signals may include Sounding Reference Signals (SRS) and Uplink DMRS. In some examples, the UCI may include a scheduling request (SR), a request from the scheduling entity to schedule uplink transmissions. Here, in response to an SR transmitted on the UCI, the scheduling entity may transmit downlink control information (DCI) that can schedule resources for uplink packet transmissions. UCIs may also include HARQ feedback, Channel State Feedback (CSF) (such as CSI reports), or any other suitable UCI.

[0081] In addition to control information, one or more REs 306 can be allocated for data services (e.g., within data area 314). Such data services can be carried on one or more service channels, such as the Physical Downlink Shared Channel (PDSCH) for DL ​​transmissions, or the Physical Uplink Shared Channel (PUSCH) for UL transmissions. In some examples, one or more REs 306 within data area 314 can be configured to carry other signals, such as one or more SIBs and DMRS. In some examples, the PDSCH can carry multiple SIBs, not limited to SIB1 discussed above. For example, OSI can be provided in these SIBs, such as SIB2 and above.

[0082] In an example of sidechain communication via a sidechain carrier through a ProSe PC5 interface, the control area 312 of time slot 310 may include a Physical Sidechain Control Channel (PSCCH) containing sidechain control information (SCI) transmitted by an initiating (transmitting) sidechain device (e.g., a Tx V2X device or other Tx UE) to a group of one or more other receiving sidechain devices (e.g., a receiving (Rx) V2X device or other Rx UE). The data area 314 of time slot 310 may include a Physical Sidechain Shared Channel (PSSCH) containing sidechain data traffic transmitted by the initiating (transmitting) sidechain device within resources reserved on the sidechain carrier by the transmitting sidechain device via the SCI. Other information may also be transmitted via various REs 306 within time slot 310. For example, HARQ feedback information may be transmitted from the receiving sidechain device to the transmitting sidechain device in the Physical Sidechain Feedback Channel (PSFCH) within time slot 310. In addition, one or more reference signals, such as sidechain SSB, sidechain CSI-RS, sidechain SRS and / or sidechain positioning reference signal (PRS), may be transmitted in time slot 310.

[0083] These physical channels are typically multiplexed and mapped to transport channels for processing at the Media Access Control (MAC) layer. The transport channel carries blocks of information called transport blocks (TBs). The transport block size (TBS), which can correspond to the number of bits of information, can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of redundancies (RBs) in a given transmission.

[0084] Figure 3 The channels or carriers shown are not necessarily all the channels or carriers that can be used between devices, and those skilled in the art will recognize that other channels or carriers, such as other service, control, and feedback channels, may be used in addition to those shown.

[0085] Figure 4 An example of a 5G wireless communication system (5GS) 400 is shown. In some examples, the 5GS 400 can be the one described above and... Figure 1 The same wireless communication system 100 shown. 5GS 400 includes user equipment (UE) 402, next-generation radio access network (NG-RAN) 404, and 5G core network 406. UE 402 may correspond to... Figure 1 , 2 and any UE or scheduling entity shown in any of 3 to 12. NG-RAN 404 may correspond to Figure 1 , 2 And any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 5 to 13.

[0086] Core network 406 may include, for example, Access and Mobility Management Functions (AMF) 408, Session Management Functions (SMF) 410, and User Plane Functions (UPF) 412. AMF 408 and SMF 410 use control plane (e.g., Non-Access Stratum (NAS)) signaling to perform various functions related to mobility and session management of UE 402. For example, AMF 408 provides connectivity, mobility management, and authentication for UE 402, while SMF 410 provides session management for UE 402 (e.g., handling signaling related to Protocol Data Unit (PDU) sessions between UE 402 and external data network (DN) 414). UPF 412 provides user plane connectivity to route 5G (NR) data packets to / from UE 402 via NG-RAN 404.

[0087] The core network 406 may also include other functions such as the Policy Control Function (PCF) 416, the Authentication Server Function (AUSF) 418, the Unified Data Management (UDM) 420, the Network Slice Selection Function (NSSF) 422, and other functions (not shown for simplicity). PCF 416 provides policy information (e.g., rules) for control plane functions such as network slicing, roaming, and mobility management. Furthermore, PCF 416 supports 5G Quality of Service (QoS) policies, network slicing policies, and other types of policies. AUSF 418 performs authentication for UE 402. UDM 420 assists in generating Authentication and Key Agreement (AKA) credentials, performing user identification, and managing subscription information and UE context. In some examples, AMF 408 includes a Secure Anchor for Co-location (SEAF) function, which allows UE 402 to be re-authenticated when the UE moves between different NG-RAN 404s without having to perform the full authentication process with AUSF 418. NSSF 422 redirects traffic to network slices. For example, network slices can be defined for different categories of subscribers or use cases, such as smart homes, the Internet of Things (IoT), connected cars, and smart grids. Each use case can receive a unique set of optimized resources and network topology (e.g., network slices) to meet the connectivity, speed, power, and capacity requirements of the use case.

[0088] To establish an NR SA connection to the 5G core network 406 via NG-RAN 404, UE 402 can send a registration request and a PDU session establishment request to the 5G core network 406 via NG-RAN 404. AMF 408 and SMF 410 can process the registration request and PDU session establishment request, and establish a PDU session between UE 402 and external DN 414 via UPF 412. A PDU session can include one or more sessions (e.g., a data session or data stream) and can be serviced by multiple UPF 412s (only one is shown for convenience). Examples of data streams include, but are not limited to, Internet Protocol (IP) streams, Ethernet streams, and unstructured data streams.

[0089] 5G-NR networks can further support carrier aggregation (CA) of component carriers transmitted from different cells and / or different transmit and receive points (TRPs) in multi-cell transmission environments. Different TRPs can be associated with a single serving cell or multiple serving cells. In some respects, the term component carrier can refer to the carrier frequency (or band) used for intra-cell communication.

[0090] Figure 5 This is a conceptual diagram illustrating a wireless communication system of a base station (BS) and user equipment (UE) communicating via multiple carriers, according to some aspects of this disclosure. Specifically, Figure 5 An example of a wireless communication system 500 is shown, including a primary serving cell (PCell) 502 and one or more secondary serving cells (SCells) 506a, 506b, 506c, and 506d. PCell 502 may be referred to as the anchor cell providing radio resource control (RRC) connectivity to UE 510. In some examples, the PCell and SCell may co-locate (e.g., different TRPs at the same location). UE 510 may correspond to... Figure 1 , 2 Any UE or scheduling entity shown in any of 4 and 6 to 12.

[0091] One or more SCells 506a-506d can be activated or added to PCell 502 to form a serving cell serving UE 510. Each serving cell corresponds to a component carrier (CC). The CC of PCell 502 can be referred to as the primary CC, while the CCs of SCells 506a-506d can be referred to as secondary CCs. PCell 502 and one or more SCells 506 can be provided by corresponding base stations 504 and 508a-508c or similar. Figure 1 , 2 The scheduling entity shown in 4 and 6 through 13 will serve the service. Figure 5In the example shown, each SCell 506a-506c is served by a corresponding base station 508a-508c. SCell 506d is co-located with PCell 502. For example, base station 504 may include multiple TRPs, each supporting a different carrier. The coverage of PCell 502 and SCell 506d may differ because component carriers in different frequency bands may experience different path losses.

[0092] In some examples, PCell 502 can add or remove one or more of SCells 506a-506d to improve the reliability of the connection to UE 510 and / or increase the data rate. PCell 502 can be changed when switching to another PCell.

[0093] In some examples, the PCell 502 may utilize a first radio access technology (RAT) (such as LTE), while one or more of the SCell 506 may utilize a second RAT (such as 5G-NR). In this example, the multi-cell transmission environment can be referred to as a multi-RAT-dual connectivity (MR-DC) environment. An example of MR-DC is the Evolved Universal Terrestrial Radio Access Network (E-UTRAN)-New Radio (NR) Dual Connectivity (EN-DC) mode, which enables the UE to simultaneously connect to both LTE and NR base stations to receive and transmit data packets from both.

[0094] In some examples, PCell 502 can be a low-band cell, and SCell 506 can be a high-band cell. Low-band (LB) cells use CC in a frequency band lower than that of high-band cells. For example, a high-band cell can use millimeter-wave (mmW) CC, while a low-band cell can use CC in a frequency band below mmW (e.g., sub-6 GHz band). Typically, a cell using mmW CC can provide greater bandwidth than a cell using low-band CC. Furthermore, in some examples, beamforming can be used to transmit and receive signals when using frequency carriers above 6 GHz (e.g., mmW).

[0095] Figure 6This is a conceptual diagram of a wireless communication system where UE 602 can be served by a primary node (MN) 604 and one or more secondary nodes (e.g., a first secondary node (SN) 606 and / or a second SN 608). A primary cell group (MCG) is associated with MN 604 and, in this example, includes PCells and SCells. A first secondary cell group (SCG) is associated with a first SN 606 and, in this example, includes two SCells. A second SCG is associated with a second SN 608 and, in this example, includes two SCells. Different examples may include different numbers of SCells. UE 602 may correspond to... Figure 1 , 2 Any UE or scheduling entity shown in any of 4, 5, and 7 through 12. MN 604 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 4, 5, and 7 through 13. The first SN 606 and the second SN 608 may correspond to... Figure 1 , 2 Any BS (e.g., gNB, eNB, SN, etc.) or scheduling entity shown in any of 4, 5, and 7 through 13.

[0096] The MN 604 can configure the MR-DC by selecting either a first or second SCG. The MN 604 can then select one SCell of the selected SCG as the SCG's PSCell (e.g., as shown in the image). Figure 6 (As shown in the diagram). Therefore, for the PSCell selection process, one or more SCcells of the SCG can be considered as candidate PSCells.

[0097] The PSCell(s) used to serve UE 602 may change over time. For example, due to service conditions at MN 604 or some other factor, MN 604 may choose to add another PSCell to serve UE 602. As another example, due to signaling conditions between UE 602 and one or more current PSCells (e.g., determined based on signal measurements performed by UE 602), either MN 604 or one of the PSCells may choose to change one or more PSCells. For example, the current PSCell (which may be referred to as the source SN) may identify (e.g., based on signal measurements of UE 602) another PSCell (which may be referred to as the target SN or target PSCell) that will provide better service to UE 602.

[0098] This disclosure relates in some aspects to signaling and related procedures for adding and / or changing PSCell configurations. In some aspects, adding / changing PSCell configurations can be conditional, as the addition of a target PCcell or the change of a target PSCell can depend on signal measurements performed at the UE. Here, the UE can verify whether the signaling conditions between the UE and the target PCell are acceptable. If so (e.g., the Reference Received Power (RSRP) measured at the UE meets defined criteria), the addition or change can be made.

[0099] In wireless communication systems, dual connectivity (DC) aims to utilize radio resources across multiple carriers. DC can be used to increase throughput, provide mobility robustness, support load balancing between network nodes, and / or similar purposes. DC operation mode is a mode in which a UE (e.g., UE 602) is configured to utilize the radio resources of two different schedulers located in two network nodes (e.g., MN 604 and first SN 606). These network nodes are referred to as the primary node (MN) and the secondary node (SN). Therefore, DC enables the UE to simultaneously transmit and receive data from a cell group across multiple component carriers via the MN and SN. In the context of DC, the primary cell group (MCG) is the serving cell group associated with the MN and includes the primary cell (PCell) and optionally one or more secondary cells (SCells). Furthermore, the secondary cell group (SCG) is the serving cell group associated with the SN and includes the primary and secondary cells (PSCells) and optionally one or more SCcells.

[0100] As described above, an example of MR-DC is E-UTRAN NR-DC, which is referred to as EN-DC. EN-DC allows a UE to connect to both an LTE base station (e.g., acting as an MN) and an NR base station (e.g., acting as an SN). A UE with EN-DC enabled registers with the LTE core network (i.e., the LTE Evolution Packet Core (EPC)) and reports measurements on NR frequencies. If the UE's signal quality supports NR service, the LTE base station communicates with the NR base station to allocate resources for carrying. NR resource allocation is then signaled to the UE via an LTE Radio Resource Control (RRC) connection reconfiguration message. Once the RRC connection reconfiguration process is complete, the UE is connected to both the LTE and NR networks simultaneously. In EN-DC, secondary cell group addition is performed using RRC procedures. For example, the RRC connection reconfiguration process can be used to add, modify, or release secondary cell groups based on NR measurements performed by the UE.

[0101] In MR-DC operations, a conditional PSCell addition procedure can be performed to add a candidate target PSCell for a target SN associated with the serving UE. Here, conditional PSCell addition is performed based on the UE detecting that the conditions for conditional PSCell addition are met for the target candidate PSCell. Similarly, in MR-DC operations, a conditional PSCell change procedure can be performed to change a PSCell serving the UE from a source PSCell to a candidate target PSCell. The candidate target PSCell can be associated with a source SN (i.e., the conditional PSCell change may be within the SN) or with a target SN (i.e., the conditional PSCell change may be between SNs). Conditional PSCell change can be performed based on the UE detecting that the conditions for conditional PSCell change have been met for the target candidate PSCell. Conditional PSCell addition or conditional PSCell change can be initiated by the MN or by the SN.

[0102] This disclosure relates in some aspects to techniques and apparatus for signaling notification of conditional PSCell change procedures (e.g., in MR-DC) to ensure reliable performance of conditional PSCell changes. The signaling aspects of conditional PSCell change procedures in MR-DC are described below in the context of various types of conditional PSCell change procedures.

[0103] Figure 7 , 8 Figures 9, 10, 11, and 12 are diagrams illustrating examples of signaling aspects associated with a conditional PSCell change process in an MR-DC, according to various aspects of this disclosure. Figure 7 , 8 In 9, 10, 11 and 12, MR-DC UE (e.g., Figure 6 The UE 602 is connected to the MN (e.g., Figure 6 MN 604) and SN (e.g., Figure 6 The first SN (606), and the source PSCell of the serving UE is associated with the SN.

[0104] This disclosure relates in some aspects to a conditional PSCell addition (CPA) initiated by an MN, wherein the MN can modify the MCG configuration based on information from a target SN. For example, the MN can discard RBs from the MCG configuration based on RB groups that the target SN cannot allow the MN to terminate.

[0105] This disclosure relates in some aspects to a CPA initiated by an MN, wherein for each target PSCell, the target SN provides the target PSCell ID at the top level of the SN adding a request confirmation message for the MN to use in configuring the CPA execution conditions.

[0106] Figure 7 This is a diagram illustrating an example of a CPA procedure 700 initiated by MN in a wireless communication system including UE 701, MN 702, first target SN (T-SN1) 703, second target SN (T-SN2) 704, UPF 705, and AMF 706. UE 701 may correspond to... Figure 1 , 2 Any UE or scheduling entity shown in any of 4 to 6 and 8 to 12. MN 702 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 4 to 6 and 8 to 13. T-SN1703 and T-SN2704 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, SN, etc.) or scheduling entity shown in any of 4 to 6 and 8 to 13. UPF 705 may correspond to Figure 4 and 8 Any of the UPFs shown in any of the 12. AMF 706 may correspond to Figure 4 and 8 Any of the AMFs shown in any of the 12.

[0107] In the CPA procedure 700 initiated by the MN, candidate target PSCells are being added. Here, MN 702 determines the group of target SNs and the candidate target PSCells for each target SN. For each candidate target PSCell, MN 702 determines the CPA execution conditions. In some examples, the CPA execution conditions involve comparing the target cell signal strength measured by the UE 701 with a threshold, such as target cell >= threshold (event A4).

[0108] In the SN Add Request sent to each target SN, MN 702 includes the following information: (1) the target PSCell in the candidate cell information list in the CG Configuration-Info (CGConfig-Info) for the target SN to consider. (2) a set of MN RBs to be established (e.g., separate bearers for MN termination) and the required SCG resources.

[0109] Upon receiving an SN add request, the target SN determines the target PSCell group to be included in the CPA configuration and sends it to UE 701. In response to the SN add request, the target SN sends an SN add request confirmation.

[0110] In the SN addition request confirmation, the target SN may include the following information: (1) Target PSCell and SCG configuration, including the radio bearer (RB) configuration for each target PSCell. (2) For each target PSCell, the target SN indicates the set of RBs that it can and cannot allow.

[0111] MN 702 determines the CPA configuration to be provided to UE 701. MN 702 can modify the MCG configuration based on information from the target SN. For example, based on RB groups that the target SN cannot allow to be terminated by MN, MN 702 can discard these RBs from the MCG configuration. For each target PSCell, MN 702 then combines the MCG configuration with the SCG configuration provided from the target SN (which remains unchanged) and forwards it to UE 701 as part of the CPA configuration.

[0112] CPA configuration can also include CPA execution conditions for each target PSCell. For each target PSCell, the target SN provides the target PSCell ID at the top level of the SN Add Request Acknowledgment message for the MN 702 to use in configuring CPA execution conditions. In some examples, the top level of the SN Add Request Acknowledgment message corresponds to the top level of the corresponding information element (IE) structure visible to the MN 702.

[0113] refer to Figure 7 As shown in operation 710, UE 701 may provide a measurement report (e.g., an RRC measurement report) to MN 702. In some aspects, the measurement report may include measurement results associated with the source PSCell of UE 701 and / or measurement results associated with a set of candidate target PSCells.

[0114] As shown in operation 715, MN 702 can determine the Conditional PSCell Addition (CPA) procedure to be initiated based at least in part on the measurement report. For example, MN 702 can determine that an additional cell is needed to serve UE 701 and can determine to initiate a Conditional PSCell Addition procedure.

[0115] As shown in operations 720 and 725, MN 702 may send an SN add request message to each of the candidate target SNs (T-SN1 703 and T-SN2 704 in this example) based at least in part on a group of candidate target SN identifiers associated with the candidate target PSCell group of UE 701. As shown, in some aspects, the SN add request message may include a conditional PSCell add (CPA) indicator (e.g., an indication that the requested SN add is associated with the conditional PSCell add procedure).

[0116] As illustrated by operations 730 and 735, each candidate target SN can send an acknowledgment of the SN add request to MN 702 (e.g., an SN add request acknowledgment message). In some aspects, the acknowledgment provided by a given candidate target SN may include information associated with the candidate target PSCell group, the SCG configuration associated with the candidate target PSCell group, and the data forwarding address (if required) (e.g., for the bearer whose termination point will be moved).

[0117] As shown in operation 740, MN 702 may send a reconfiguration message (e.g., an RRC reconfiguration message) to UE 701. As illustrated, in some aspects, the reconfiguration message may include configuration information associated with conditional PSCell addition. The configuration information may include, for example, information associated with each of the candidate target PSCell groups. As further shown, the reconfiguration message may include information indicating the conditions for each candidate target PSCell, which, if met, will cause UE 701 to perform conditional PSCell addition.

[0118] As shown in operation 745, after UE 701 receives the reconfiguration message, UE 701 can provide MN 702 with a reconfiguration completion message (e.g., RRC reconfiguration completion information).

[0119] As shown in operation 750, UE 701 may determine that a candidate target PSCell (e.g., one of a group of candidate target PSCells) satisfies a condition added to the condition PSCell. For example, UE 701 may determine that the signal strength associated with the candidate target PSCell satisfies a threshold identified by the condition indicated for the candidate target PSCell, that the signal strength associated with the candidate target PSCell exceeds a threshold amount of the signal strength associated with the source PSCell, and / or similar.

[0120] As shown in operation 755, UE 701 may send a reconfiguration complete message (e.g., RRC reconfiguration complete information) to MN 702, indicating that UE 701 has determined that the candidate target PSCell meets the conditions added by the condition PSCell. In some aspects, the message includes information identifying the candidate target PSCell (T-PSCell1 in this example) to which UE 701 has determined to meet the conditions for the candidate target PSCell.

[0121] As shown in operation 760, MN 702 can send an acknowledgment message associated with the conditional PSCell addition to the selected SN (selected target PSCell). (For example, an SN reconfiguration complete message.)

[0122] As shown in operation 765, the selected SN can send an SN state transition message to MN 702, after which data forwarding can begin, as shown in operation 770. As shown in operation 775, UE 701 can perform a random access channel (RACH) procedure for the candidate target PSCell, and as shown in operation 780, it can perform a path update procedure.

[0123] exist Figure 7 In the CPA procedure 700 initiated by the MN, the RRC reconfiguration message (operation 740) may contain the following information: A set of candidate target PSCells; Execution conditions that need to be met to access the target PSCell (e.g., based on event and measurement thresholds); The configuration to be used by the UE after accessing the target PSCell.

[0124] The RRC reconfiguration completion (operation 755) includes the selected target PSCell, enabling MN 702 to forward the SN reconfiguration completion to the corresponding target SN (T-SN). In operations 730 and 735, each T-SN provides MN 702 with a data forwarding address (e.g., for the bearer whose termination point moves from MN 702 to the selected SN). MN 702 can then send an SN status transfer and begin data forwarding to the selected T-SN after sending the SN reconfiguration completion. Operation 775 can be performed in parallel with operations 755 through 770.

[0125] In another example, in some aspects, this disclosure relates to a conditional PSCell change (CPC) initiated by an SN, wherein the source SN may include CPC execution condition information in the SN change required message sent to the MN. For example, for each target SN in a cell group configuration (CG-configuration), the source SN may send CPC execution conditions for each candidate target PSCell. In some examples, the CPC execution conditions involve comparing the signal strength of the source cell and neighbor cells as measured by the UE (e.g., neighbor >= source + offset (event A3)).

[0126] In some aspects, this disclosure also relates to a conditional PSCell change (CPC) initiated by the SN, wherein the MN may include the CPC execution condition of the target PSCell in an SN add request sent to the target SN.

[0127] In some aspects, this disclosure also relates to a conditional PSCell change (CPC) initiated by an SN, wherein the target SN may include a CPC configuration in an SN add request confirmation, which includes the CPC execution conditions for each target PSCell.

[0128] In some aspects, this disclosure also relates to SN-initiated conditional PSCell change (CPC), where the MN modifies the MCG configuration based on information from the target SN. For example, the MN can discard RBs from the MCG configuration based on RB groups that the target SN cannot allow to be terminated. For each target PSCell, the MN can combine the MCG configuration with the SCG configuration and CPC execution conditions provided from the target SN and provide the resulting CPC configuration to the UE.

[0129] In some aspects, this disclosure also relates to a conditional PSCell change (CPC) initiated by the SN, wherein the MN does not include the CPC execution condition in the SN add request message. For this example, in the SN add request confirmation, the target SN does not include the execution condition for each target PSCell, but provides the target PSCell ID at the top level of the SN add request confirmation message.

[0130] Figure 8 and 9 This diagram illustrates an example of a conditional PSCell change process 800 initiated by a SN in a wireless communication system. The system includes a UE 801, MN 802, a source SN (S-SN) 803, a first target SN (T-SN1) 804, an Nth target SN (T-SNn) 805, a UPF 806, and an AMF 807. UE 801 may correspond to... Figure 1 , 2 Any UE or scheduling entity shown in any of 4 to 7 and 10 to 12. MN 802 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 4 to 7 and 10 to 13. S-SN 803, T-SN1 804, and T-SNn 805 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, SN, etc.) or scheduling entity shown in any of 4 to 7 and 10 to 13. UPF 806 may correspond to Figure 4 , 7 and any of the UPFs shown in any of 10 to 12. AMF 807 may correspond to Figure 4 , 7 And any of the AMFs shown in any of 10 to 12.

[0131] In the conditional PSCell modification process 800 initiated by the SN, the SN is the source SN, and the PSCell is modified to a candidate target PSCell associated with the target SN (e.g., the second SN 608). That is, in Figure 8 and 9In the example, the conditional PSCell change is the conditional PSCell change between SNs.

[0132] In the case of CPC configuration for SN-initiated inter-SN CPC, the source SN determines the target SN group and candidate target PSCell group for each target SN. The source SN may include the information that follows in the SN change required message sent to MN 802. (1) A list of target SNs (e.g., target SN IDs). (2) For each target SN, an indication of the candidate target PSCells in the candidate cell information list in the CG-configuration for the target SN to consider. (3) For each target SN, the CPC execution conditions for each candidate target PSCell in the CG-configuration (e.g., neighbor >= source + offset (event A3)). (4) The source SCG configuration and the RB group to be terminated by the SN.

[0133] In the SN add request sent to the target SN, MN 802 may include the following information: (1) MN 802 may forward the identifier of the candidate target PSCell, the CPC execution conditions of the target PSCell, the source SCG configuration, and the SN termination RB group to be established, including in the SN required changes. (2) The MN RB group to be configured for the target SN (e.g., the detached bearer of the MN termination) and the required SCG resources.

[0134] Each target SN determines the target PSCell group to be included in the CPC configuration. In the SN add request confirmation, the target SN may include the following CPC configuration information: (1) The target PSCell and SCG configuration (including RB configuration) for each target PSCell. (2) The CPC execution conditions for each target PSCell. (3) For each target PSCell, the target SN indicates the set of RBs that it can and cannot allow.

[0135] MN 802 can modify the MCG configuration based on information from the target SN. For example, if the information indicates that the target SN cannot allow MN termination of RB groups, then MN 802 discards these RBs from the MCG configuration. For each target PSCell, MN 802 then combines the MCG configuration with the SCG configuration and CPC execution conditions provided from the target SN, and provides the resulting CPC configuration to UE 801.

[0136] During the replacement process, MN 802 does not include CPC execution conditions in the SN Add Request message. In the SN Add Request Confirmation, the target SN does not include the execution conditions for each target PSCell, but provides the target PSCell ID at the top level of the SN Add Request Confirmation message. For each target PSCell, MN 802 then combines the MCG configuration and CPC execution conditions with the SCG configuration provided from the target SN and provides the resulting CPC configuration to UE 801.

[0137] First refer to Figure 8 As shown in operation 810, UE 801 may provide a measurement report (e.g., an RRC measurement report) to the source SN. In some aspects, the measurement report may include measurement results associated with the source PSCell of UE 801 and measurement results associated with a set of candidate target PSCells. Here, the candidate target PSCell set includes one or more candidate target PSCells configured on UE 801 (e.g., at an earlier time).

[0138] As shown in operation 815, the source SN can determine the conditional PSCell change (CPC) procedure to be initiated based at least in part on the measurement report. For example, the source SN can determine that the measurement result associated with the source PSCell failed to meet a threshold (e.g., the signal strength associated with the source PSCell is below a signal strength threshold), and can determine that a conditional PSCell change procedure will be initiated.

[0139] As shown in operation 820, the source SN can send a change-required message (e.g., an SN change-required message) to MN802, at least in part, based on the determination to initiate a conditional PSCell change procedure. In some aspects, the change-required message may include an indicator indicating that a conditional PSCell change procedure is being initiated. In some aspects, such as Figure 8 As shown, the change message may include a set of n (n≥1) candidate target SN identifiers (e.g., T-SN1 ID, T-SNn ID). Here, each candidate target SN identifier corresponds to the corresponding candidate target SN of UE 801 included in the candidate target SN group.

[0140] As shown in operations 825a and 825b, MN 802 can send an SN add request message to each of the candidate target SNs (T-SN1 804 and T-SNn 805 in this example) based at least in part on the candidate target SN identifier group. As shown, in some aspects, the SN add request message may include a conditional PSCell change (CPC) indicator (e.g., an indication that the requested SN add is associated with a conditional PSCell change procedure).

[0141] As illustrated by operations 830a and 830b, each candidate target SN can send an acknowledgment of the SN add request to MN 802 (e.g., an SN add request acknowledgment message). In some aspects, the acknowledgment provided by a given candidate target SN may include information associated with the candidate target PSCell group, the SCG configuration associated with the candidate target PSCell group, and the data forwarding address (if required) (e.g., for the bearer whose termination point will be moved).

[0142] As shown in operation 835, when an acknowledgment is received from the candidate target SN group, MN 802 may send a reconfiguration message (e.g., an RRC reconfiguration message) to UE 801. As illustrated, in some aspects, the reconfiguration message may include configuration information associated with a conditional PSCell change (e.g., CPC_configuration). The configuration information may include, for example, information associated with each of the candidate target PSCell groups. As further shown, the reconfiguration message may include information indicating the conditions for each candidate target PSCell (e.g., T-PSCell1_CPC_exec_thresh, T-PSCell2_CPC_exec_thresh, and / or similar), which, if met, will cause UE 801 to execute the conditional PSCell change.

[0143] As shown in operation 840, after UE 801 receives the reconfiguration message, UE 801 can provide MN 802 with a reconfiguration completion message (e.g., RRC reconfiguration completion information).

[0144] As shown in operation 845, UE 801 may determine that a candidate target PSCell (e.g., one of a group of candidate target PSCells) satisfies the condition for a change in the condition PSCell. For example, UE 801 may determine that the signal strength associated with the candidate target PSCell satisfies a threshold identified by the condition indicated for the candidate target PSCell, the signal strength associated with the candidate target PSCell exceeds a threshold amount identified by the condition indicated for the candidate target PSCell associated with the source PSCell, and / or similar.

[0145] like Figure 9 As shown in operation 850, UE 801 can send a reconfiguration complete message (e.g., RRC reconfiguration complete information) indicating that UE 801 has determined that the candidate target PSCell meets the conditions for the conditional PSCell change. In some aspects, the message includes information identifying the candidate target PSCell (T-PSCell1 in this example) to which UE 801 has determined to satisfy the conditions for the candidate target PSCell.

[0146] In some aspects, based at least in part on receiving a reconfiguration complete message, MN 802 may further send a request to one or more candidate target SNs to release reserved resources for candidate target PSCells associated with one or more other candidate target SNs. In some aspects, the request may include a list of candidate target PSCells for which reserved resources are to be released at one or more other target SNs. In some aspects, one or more candidate target SNs may release the reserved resources for candidate target PSCells at least in part based on this request.

[0147] As shown in operation 855, MN 802 may send an acknowledgment message (e.g., an SN change acknowledgment message) associated with the condition PSCell change to the source SN. In some aspects, as shown, the acknowledgment message includes the data forwarding address of the target SN associated with the candidate target PSCell (e.g., Fwd_Addr_T-SN1) (e.g., enabling the source SN to directly forward data to the target SN). In some aspects, the acknowledgment includes the data forwarding address of MN 802 (e.g., enabling the source SN to forward data to the target SN via MN 802). In some aspects, upon receiving the acknowledgment message, the source SN releases resources used by UE 801.

[0148] As shown in operation 860, MN 802 can send an SN reconfiguration complete message to the target SN associated with the candidate target PSCell.

[0149] As shown in operations 865a and 865b, MN 802 and the source SN can send the corresponding SN state transition message to the target SN, after which data forwarding can begin, as shown in operations 870a (indirect data forwarding) and 870b (direct data forwarding).

[0150] As shown in operation 875, UE 801 may perform a random access channel (RACH) procedure for a candidate target PSCell. In some aspects, UE 801 may perform the RACH procedure at any time after the conditions for determining the candidate target PSCell have been met (e.g., during the time when the operations associated with operations 850 to 870 are being performed).

[0151] As shown in operation 880, a path update procedure can be performed, and as shown in operation 885, MN 802 can send a context release associated with UE 801 to the source SN.

[0152] exist Figure 8 and 9In the SN-initiated conditional PSCell change process 800, the RRC reconfiguration message (operation 835) may include the following information: (1) a set of candidate target PSCells, and the execution conditions to be met for accessing each target PSCell. (2) the configuration to be used by UE 801 after accessing the target PSCell.

[0153] In operation 855, MN 802 sends the data forwarding address provided by T-SN1 (direct data forwarding) along with MN 802's own address (indirect data forwarding) to the S-SN. The source SN resources of UE 801 are released upon receiving an SN change confirmation. Operations 870a and 870b involve indirect and direct data forwarding via MN 802, respectively. Operation 875 can be performed in parallel with operations 870a to 870b.

[0154] In another example, for the CPC configuration in the case of an inter-SN CPC initiated by the MN, the MN first uses the SN modification procedure to obtain the current SCG configuration before initiating the procedure with the target SN. The inter-node signaling and procedures used to construct the CPC configuration can be similar to those in the case of a CPA procedure initiated by the MN.

[0155] Figure 10 and 11 This is a diagram illustrating an example 1000 of a conditional PSCell change process 1000 initiated by an MN in a wireless communication system. The system includes a UE 1001, an MN 1002, a source SN (S-SN) 1003, a first target SN (T-SN1) 1004, an Nth target SN (T-SNn) 1005, a UPF 1006, and an AMF 1007. The UE 1001 may correspond to... Figure 1 , 2 Any UE or scheduling entity shown in any of 4 to 9 and 12. MN 1002 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 4 to 9, 12, and 13. S-SN 1003, T-SN1 1004, and T-SNn 1005 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, SN, etc.) or scheduling entity shown in any of 4 to 9, 12, and 13. UPF 1006 can correspond to Figure 4 , 7 Any UPF shown in either 9 or 12. AMF 1007 can correspond to Figure 4 , 7 Any AMF shown in either 9 or 12.

[0156] In the conditional PSCell modification process 1000 initiated by MN, the PSCell is modified to a candidate target PSCell associated with the target SN. That is, the conditional PSCell modification process 1000 initiated by MN involves conditional PSCell modification between SNs.

[0157] As shown in operation 1010, UE 1001 may provide a measurement report (e.g., an RRC measurement report) to source MN 1002. In some aspects, the measurement report may include measurement results associated with the source PSCell of UE 1001 and / or measurement results associated with a set of candidate target PSCells.

[0158] As shown in operation 1015, MN 1002 can determine the conditional PSCell change process to be initiated based at least in part on the measurement report. For example, MN 1002 can determine that the measurement result associated with the source PSCell fails to meet a threshold (e.g., the signal strength associated with the source PSCell is below a signal strength threshold), and can determine that a conditional PSCell change will be initiated.

[0159] As shown in operations 1020a and 1020b, MN 1002 may send an SN add request message to each of the candidate target SNs (T-SN1 1004 and T-SNn 1005 in this example) based at least in part on a group of candidate target SN identifiers associated with the candidate target PSCell group of UE 1001. As shown, in some aspects, the SN add request message may include a conditional PSCell change (CPC) indicator (e.g., an indication that the requested SN add is associated with a conditional PSCell change procedure).

[0160] As illustrated by operations 1025a and 1025b, each candidate target SN can send an acknowledgment of the SN add request to MN 1002 (e.g., an SN add request acknowledgment message). In some aspects, the acknowledgment provided by a given candidate target SN may include information associated with the candidate target PSCell group, the SCG configuration associated with the candidate target PSCell group, and the data forwarding address (if needed) (e.g., for the bearer whose termination point will be moved).

[0161] As shown in operation 1030, when an acknowledgment is received from the candidate target SN group, MN 1002 may send a reconfiguration message (e.g., an RRC reconfiguration message) to UE 1001. As illustrated, in some aspects, the reconfiguration message may include configuration information associated with a conditional PSCell change. The configuration information may include, for example, information associated with each of the candidate target PSCell groups (e.g., T-PSCell1 and T-PSCell2). As further shown, the reconfiguration message may include information indicating a condition for each candidate target PSCell, which, if met, will cause UE 1001 to perform a conditional PSCell change.

[0162] As shown in operation 1035, after UE 1001 receives the reconfiguration message, UE 1001 can provide MN 1002 with a reconfiguration completion message (e.g., RRC reconfiguration completion information).

[0163] As shown in operation 1040, UE 1001 may determine that a candidate target PSCell (e.g., one of a group of candidate target PSCells) satisfies the condition for a change in the condition PSCell. For example, UE 1001 may determine that the signal strength associated with the candidate target PSCell satisfies a threshold identified by the condition indicated for the candidate target PSCell, or that the signal strength associated with the candidate target PSCell exceeds a threshold amount identified by the condition indicated for the candidate target PSCell associated with the source PSCell, and / or similar.

[0164] like Figure 11 As shown in operation 1045, UE 1001 can send a reconfiguration complete message (e.g., RRC reconfiguration complete information) indicating that UE 1001 has determined that the candidate target PSCell meets the conditions for the conditional PSCell change. In some aspects, the message includes information identifying the candidate target PSCell (T-PSCell1 in this example) to which UE 1001 has determined to satisfy the conditions for the candidate target PSCell.

[0165] In some aspects, based at least in part on receiving a reconfiguration complete message, MN 1002 may further send a request to one or more candidate target SNs to release reserved resources for candidate target PSCells associated with one or more other candidate target SNs. In some aspects, the request may include a list of candidate target PSCells for which reserved resources are to be released at one or more other target SNs. In some aspects, one or more candidate target SNs may release the reserved resources for candidate target PSCells based at least in part on the request.

[0166] As shown in operation 1050, MN 1002 may send an acknowledgment message (e.g., an SN release request message) associated with the condition PSCell change to source SN 1003. In some aspects, the acknowledgment message includes the data forwarding address of the target SN associated with the candidate target PSCell (T-SN11004 in this example) (e.g., enabling source SN 1003 to forward data directly to the target SN). In some aspects, the acknowledgment includes the data forwarding address of MN 1002 (e.g., enabling source SN 1003 to forward data to the target SN via MN 1002).

[0167] In some aspects, upon receiving an acknowledgment message, source SN 1003 releases the resources used by UE 1001. As shown in operation 1055, source SN 1003 may send and MN 1002 may receive an acknowledgment of the release request (e.g., an SN release request acknowledgment message).

[0168] As shown in operation 1060, MN 1002 can send an SN reconfiguration complete message to the target SN associated with the candidate target PSCell.

[0169] As shown in operations 1065a and 1065b, MN 1002 and source SN 1003 (via MN 1002) can send the corresponding SN state transition message to the target SN, after which data forwarding can begin, as shown in operations 1070a (indirect data forwarding) and 1070b (direct data forwarding).

[0170] As shown in operation 1075, UE 1001 can perform a random access channel (RACH) procedure for a candidate target PSCell. In particular, in some aspects, UE 1001 can perform the RACH procedure at any time after the condition for determining the candidate target PSCell has been met (e.g., during the time when the operations associated with operations 1050 to 1070b are being performed).

[0171] As shown in operation 1080, a path update procedure can be performed, and as shown in operation 1085, MN 1002 can send a context release associated with UE 1001 to source SN 1003.

[0172] exist Figure 10 and Figure 11In the conditional PSCell change procedure 1000 initiated by MN, at operation 1050, MN 1002 sends the data forwarding address (for direct data forwarding) provided by T-SN1 1004 along with the address of MN 1002 (for indirect data forwarding) to the S-SN. The source SN resources of UE 1001 are released upon receiving the SN release request.

[0173] In another example, in some aspects, this disclosure relates to an SN-initiated intra-SN conditional PSCell change (CPC) with MN participation, wherein the SN includes the execution conditions of each target PSCell configured in the CPC request message. In some aspects, this disclosure also relates to an SN-initiated intra-SN conditional PSCell change with MN participation, wherein the MN includes settings for separate bearers terminated by the SN(multiple) SN(s) in the SN modification request for each target PSCell.

[0174] In some aspects, this disclosure also relates to SN-initiated conditional PSCell changes with the participation of the MN, wherein the MN modifies the MCG configuration upon receiving confirmation of the SN's modification request. For example, the MN may add an RB indicating to the SN that it can allow SN termination.

[0175] In some aspects, this disclosure also relates to SN-initiated intra-SN conditional PSCell changes with the participation of an MN, wherein for each target PSCell, the MN combines the MCG configuration with the provided SCG configuration and the CPC execution conditions sent by the SN. The MN then provides the obtained CPC configuration to the UE.

[0176] Figure 12 This is a diagram illustrating an example 1200 of an intra-SN condition PSCell change initiated by an SN in a wireless communication system including UE 1201, MN 1202, SN 1203, UPF 1204, and AMF 1205. UE 1201 may correspond to... Figure 1 , 2 and any UE or scheduling entity shown in any of 4 to 11. MN 1202 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 4 to 11 and 13. SN 1203 may correspond to Figure 1 , 2 Any BS (e.g., gNB, eNB, MN, etc.) or scheduling entity shown in any of 4 to 11 and 13. UPF 1204 may correspond to Figure 4 and 7Any UPF shown in any of 11. AMF 1205 may correspond to Figure 4 and 7 Any of the AMFs shown in any of 11.

[0177] In the SN-initiated intra-SN conditional PSCell change process 1200 with MN participation, the PSCell is changed to the candidate target PSCell associated with SN 1203. That is, in this example, the conditional PSCell change is an intra-SN conditional PSCell change.

[0178] As shown in operation 1210, UE 1201 may provide a measurement report (e.g., an RRC measurement report) to source SN 1203. In some aspects, the measurement report may include measurement results associated with the source PSCell of UE 1201 and / or measurement results associated with a set of candidate target PSCells.

[0179] As shown in operation 1215, SN 1203 can determine the conditional PSCell change procedure to be initiated based at least in part on the measurement report. For example, SN 1203 can determine that the measurement result associated with the source PSCell fails to meet a threshold (e.g., the signal strength associated with the source PSCell is below a signal strength threshold), and can determine to initiate a conditional PSCell change.

[0180] As shown in operation 1220, SN 1203 can send an SN modification required message to MN 1202. As shown, in some aspects, the SN modification required message may include a conditional PSCell change (CPC) indicator (e.g., an indication that the requested SN modification is associated with a conditional PSCell change procedure).

[0181] As shown in optional operations 1225 and 1230, in some aspects, MN 1202 may send an SN modification request to SN 1203, and SN 1203 may send an acknowledgment of the SN modification request to MN 1202 (e.g., an SN modification request acknowledgment message).

[0182] For CPC configurations where the condition PSCell changes within an SN initiated by an SN with MN participation, where no... Figure 12 In operations 1225 and 1230 of the call flow, SN 1203 provides the complete CPC configuration and includes it in the SN modification required message to MN 1202 at operation 1220. MN 1202 adds the MCG configuration before forwarding this information to UE 1201.

[0183] When using operations 1225 and 1230, SN 1203, in the SN modification required by operation 1220, includes the following information: (1) For each target PSCell, a request to release a set (or more) of SCG bearers and a request to release a set (or more) of MN-terminated detached bearers. (2) SN key update. (3) A set of target PSCells for CPC configuration. (4) Execution conditions for each target PSCell for CPC configuration. (5) SCG configuration for the target PSCells for CPC configuration.

[0184] If needed, the MN 1202 can include settings for separate bearers with SN termination for each target PSCell in the SN modification request. The MN 1202 can also include a new SN key in the SN modification request.

[0185] After receiving confirmation of the SN modification request, MN 1202 may need to modify the MCG configuration. For example, MN 1202 may add an RB indicating SN 1203 that it can allow SN termination.

[0186] The SN modification request confirmation may also include the SCG configuration for each target PSCell. For example, when configuring a separate bearer for SN termination, the SCG configuration may be included.

[0187] For each target PSCell, MN 1202 in Figure 12 In operation 1220 or operation 1230, the MCG configuration is combined with the provided SCG configuration and the CPC execution conditions sent by SN 1203 in operation 1220. MN 1202 then provides the obtained CPC configuration to UE 1201.

[0188] As shown in operation 1235, MN 1202 may send a reconfiguration message (e.g., an RRC reconfiguration message) to UE 1201. As illustrated, in some aspects, the reconfiguration message may include configuration information associated with a conditional PSCell change. The configuration information may include, for example, information associated with each of the candidate target PSCell groups (T-PSCell1 and T-PSCell2 in this example). As further shown, the reconfiguration message may include information indicating the conditions for each candidate target PSCell, which, if met, will cause UE 1201 to perform a conditional PSCell change.

[0189] As shown in operation 1240, after UE 1201 receives the reconfiguration message, UE 1201 can provide MN 1202 with a reconfiguration completion message (e.g., RRC reconfiguration completion information).

[0190] As shown in operation 1245, UE 1201 can determine that a candidate target PSCell (e.g., one of a group of candidate target PSCells) satisfies the condition for a conditional PSCell change. For example, UE 1201 can determine that the signal strength associated with the candidate target PSCell satisfies a threshold identified by the condition indicated for the candidate target PSCell, that the signal strength associated with the candidate target PSCell exceeds the signal strength threshold associated with the source PSCell by an amount and / or similar.

[0191] As shown in operation 1250, UE 1201 may send a reconfiguration complete message (e.g., RRC reconfiguration complete information) indicating that UE 1201 has determined that the candidate target PSCell meets the conditions for the conditional PSCell change. In some aspects, the message includes information identifying the candidate target PSCell (T-PSCell1 in this example) to which UE 1201 has determined to meet the conditions for that candidate target PSCell.

[0192] As shown in operation 1255, MN 1202 can send an acknowledgment message (e.g., SN reconfiguration complete message) to SN 1203 that is associated with the condition PSCell change.

[0193] As shown in operation 1260, SN 1203 can send an SN state transition message to MN 1202, and then data forwarding can begin, as shown in operation 1265. As shown in operation 1270, UE 1201 can perform a RACH procedure on the candidate target PSCell, and as shown in operation 1275, it can perform a path update procedure.

[0194] Figure 13 This is a block diagram conceptually illustrating an example hardware implementation of a BS 1300 employing a processing system 1314 according to some aspects of this disclosure. In some examples, the BS 1300 may correspond to... Figure 1 , 2 and any BS (e.g., gNB, eNB, MN, SN, etc.) or scheduling entity shown in any of 4 to 12.

[0195] According to various aspects of this disclosure, elements or any portion of elements or any combination of elements can be implemented using processing system 1314. Processing system 1314 may include one or more processors 1304. Examples of processors 1304 include microprocessors, microcontrollers, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuitry, and other suitable hardware configured to perform various functions throughout this disclosure. In various examples, BS 1300 may be configured to perform any one or more of the functions described herein. That is, as used in BS 1300, processor 1304 may be used to implement any one or more of the processes and procedures described below.

[0196] In this example, the processing system 1314 can be implemented using a bus architecture, typically represented by bus 1302. Bus 1302 may include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system 1314. Bus 1302 communicatively couples together various circuits including one or more processors (typically represented by processor 1304), memory 1305, and computer-readable media (typically represented by computer-readable media 1306). Bus 1302 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described further. Bus interface 1308 provides an interface between bus 1302 and transceiver 1310 and antenna array, as well as an interface between bus 1302 and interface 1330. Transceiver 1310 provides a communication interface or component for communicating with various other devices via a wireless transmission medium. In some examples, the wireless communication device may include two or more transceivers 1310, each configured to communicate with a corresponding network type. At least one interface 1330 (e.g., a network interface and / or a user interface) provides a communication interface or component for communicating with various other devices and equipment (e.g., other devices housed in the same device as BS 1300 or external devices) via an internal bus or external transmission medium such as an Ethernet cable.

[0197] Processor 1304 is responsible for managing bus 1302 and general processing, including the execution of software stored on computer-readable medium 1306. When executed by processor 1304, the software causes processing system 1314 to perform the various functions described below on any particular device. Computer-readable medium 1306 and memory 1305 may also be used to store data manipulated by processor 1304 during software execution. For example, memory 1305 may store PSCell information 1315 (e.g., identifiers, configuration, and associated information) used by processor 1304 in cooperation with transceiver 1310 for the communication operations described herein.

[0198] One or more processors 1304 in the processing system can execute software. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, application programs, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software may reside on computer-readable media 1306.

[0199] Computer-readable medium 1306 may be a non-transitory computer-readable medium. Non-transitory computer-readable media include, as examples, magnetic storage devices (e.g., hard disks, floppy disks, magnetic stripes), optical disks (e.g., compact discs (CDs) or digital multifunction discs (DVDs)), smart cards, flash memory devices (e.g., card, stick, or key drives), random access memory (RAM), read-only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing computer-accessible and readable software and / or instructions. Computer-readable medium 1306 may reside in processing system 1314, be external to processing system 1314, or be distributed across multiple entities including processing system 1314. Computer-readable medium 1306 may be embodied in a computer program product. As an example, a computer program product may include the computer-readable medium in packaging material. Those skilled in the art will recognize how best to implement the functionality described throughout this disclosure, depending on the specific application and the overall design constraints imposed on the system.

[0200] The BS 1300 can be configured to perform any one or more of the operations described herein (e.g., as combined with the above). Figures 1 to 12 The above and the following combined Figures 14 to 19 (As described above). In some aspects of this disclosure, such as that used in BS 1300, processor 1304 may include circuitry configured for various functions.

[0201] Processor 1304 can be configured to generate, schedule, and modify resource allocations or authorizations (e.g., groups of one or more resource elements) for time-frequency resources. For example, processor 1304 can schedule time-frequency resources within multiple time-division duplex (TDD) and / or frequency-division duplex (FDD) subframes, time slots, and / or hour slots to transmit user data services and / or control information to and / or from multiple UEs.

[0202] Processor 1304 may include communication and processing circuitry 1341 configured to communicate with one or more other communication devices (e.g., base stations, UEs, etc.). In some examples, communication and processing circuitry 1341 may include one or more hardware components providing physical structures for performing various processes related to the wireless communication described herein (e.g., signal reception and / or signal transmission). Communication and processing circuitry 1341 may also include one or more hardware components providing physical structures for performing various processes related to the signal processing described herein (e.g., processing received signals and / or processing signals for transmission). In some examples, communication and processing circuitry 1341 may include two or more transmit / receive chains. Communication and processing circuitry 1341 may also be configured to execute communication and processing software 1351 included on computer-readable medium 1306 to implement one or more functions described herein.

[0203] The communication and processing circuit 1341 can also be configured to send messages to and receive messages from the UE. For example, the messages sent may include MAC-CE, DCI, random access messages, or RRC messages carried in the PDSCH, PDCCH, or PDSCH. As another example, the messages received may include MAC-CE, UCI, random access messages, or RRC messages carried in the PUSCH, PUCCH, or PUSCH. The communication and processing circuit 1341 can also be configured to receive a scheduling request for uplink grants for the PUSCH from the UE (e.g., via UCI in the PUCCH) and send grants (e.g., via DCI in the PDCCH) in response to the request.

[0204] In some implementations of communication involving the reception of information, communication and processing circuitry 1341 may obtain information from components of BS 1300 (e.g., from transceiver 1310 that receives information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium) and output processed information. For example, communication and processing circuitry 1341 may output information to another component of processor 1304, memory 1305, or bus interface 1308. In some examples, communication and processing circuitry 1341 may receive one or more of signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1341 may receive information via one or more channels. In some examples, communication and processing circuitry 1341 may include the functionality of components for receiving information.

[0205] In some implementations where communication involves sending (e.g., transmitting) information, communication and processing circuitry 1341 may obtain information (e.g., from another component of processor 1304, memory 1305, or bus interface 1308), process (e.g., encode) the information, and output the processed information. For example, communication and processing circuitry 1341 may output information to transceiver 1310 (e.g., by transmitting information via radio frequency signaling or some other type of signaling suitable for the applicable communication medium). In some examples, communication and processing circuitry 1341 may transmit signals, messages, other information, or any combination thereof. In some examples, communication and processing circuitry 1341 may transmit information via one or more channels. In some examples, communication and processing circuitry 1341 may include the functionality of components for transmission (e.g., components for transmitting).

[0206] The communication and processing circuitry 1341 may include the functionality of components for acquiring (and / or receiving) a set of associated information about the SCG configuration and the target PSCell. For example, the communication and processing circuitry 1341 may be configured to receive one or more messages (e.g., SN add request acknowledgment messages, SN modify request acknowledgment messages, SN modify required messages, or other suitable messages) from one or more SNs (e.g., via an x2 interface, an Xn interface, or some other suitable interface).

[0207] The communication and processing circuitry 1341 may include functionality for acquiring (and / or receiving) a message that includes an identifier of the target PSCell (e.g., an SN add request acknowledgment message). For example, the communication and processing circuitry 1341 may be configured to receive messages from one or more SNs (e.g., via an x2 interface, an Xn interface, or some other suitable interface).

[0208] Processor 1304 may include PSCell configuration processing circuitry 1342, which is configured to perform PSCell configuration processing related operations as discussed herein. PSCell configuration processing circuitry 1342 may be configured to execute PSCell configuration processing software 1352 included on computer-readable medium 1306 to implement one or more of the functions described herein.

[0209] The PSCell configuration processing circuit 1342 may include functionality for modifying configuration components. For example, the PSCell configuration processing circuit 1342 may be configured to receive information (e.g., measurement reports) and determine, based on the received information, whether to initiate a CPC or CPA process (e.g., as described above). Figures 7 to 12 (As discussed).

[0210] The PSCell configuration processing circuit 1342 may include functionality for generating an MCG configuration. For example, the PSCell configuration processing circuit 1342 may be configured to receive information about at least one candidate target PSCell (e.g., at least one identifier, etc.) and generate an MCG configuration based on the received information (e.g., as described above). Figures 7 to 12 (As discussed). The PSCell configuration processing circuit 1342 may include functionality for modifying the MCG configuration. For example, the PSCell configuration processing circuit 1342 may be configured to receive information (e.g., identifier, indication of supported / unsupported radio bearers, execution conditions, etc.) from a candidate target PSCell (e.g., from the SN), and modify the MCG configuration based on the received information (e.g., as described above). Figures 7 to 12 (As discussed). The PSCell configuration processing circuitry 1342 may include functionality for including MCG and SCG configurations in the CPA configuration. For example, the PSCell configuration processing circuitry 1342 may be configured to define the CPA configuration based on the modified MCG configuration and the received SCG configuration (e.g., as described above). Figures 7 to 12 (As discussed). The PSCell configuration processing circuit 1342 may include the functionality of components for removing a set of radio bearers from the MCG configuration that the target PSCell cannot allow for master node termination. For example, the PSCell configuration processing circuit 1342 may be configured to receive an indication (e.g., from the SN) of at least one unsupported radio bearer for a candidate target PSCell and remove at least one unsupported radio bearer from the MCG configuration (e.g., as combined above). Figures 7 to 12(As discussed). The PSCell configuration processing circuitry 1342 may include the functionality of components for adding a set of radio bearers that the target PSCell can terminate as secondary nodes to the MCG configuration. For example, the PSCell configuration processing circuitry 1342 may be configured to receive an indication (e.g., from the SN) of at least one supported radio bearer of a candidate target PSCell and add at least one supported radio bearer to the MCG configuration (e.g., as described above). Figures 7 to 12 (As discussed).

[0211] The PSCell configuration processing circuit 1342 may include functionality for identifying radio bearers that the PSCell does not permit. For example, the PSCell configuration processing circuit 1342 may be configured to receive (e.g., from the SN) information identifying radio bearers that a target SN does not permit (e.g., as described above). Figures 7 to 12 (As discussed).

[0212] The PSCell configuration processing circuit 1342 may include functionality for identifying radio bearers that the PSCell can permit. For example, the PSCell configuration processing circuit 1342 may be configured to receive (e.g., from the SN) information identifying radio bearers that a target SN can permit (e.g., as described above). Figures 7 to 12 (As discussed).

[0213] Processor 1304 may include PSCell configuration control circuitry 1343, which is configured to perform PSCell configuration control related operations as discussed herein. PSCell configuration control circuitry 1343 may be configured to execute PSCell configuration control software 1353 included on computer-readable medium 1306 to implement one or more of the functions described herein.

[0214] The PSCell configuration control circuit 1343 may include functions for outputting a CPA configuration or CPC configuration to the UE for transmission (and / or for transmitting components). For example, the PSCell configuration control circuit 1343 may be configured to generate a CPA configuration or CPC configuration, including a modified MCG configuration and a received SCG configuration, and send the CPA configuration or CPC configuration to the UE via allocated resources (e.g., an RRC message on the PDSCH) (e.g., as described above). Figures 7 to 12 (As discussed).

[0215] The PSCell configuration control circuit 1343 may include functionality for determining execution conditions. For example, the PSCell configuration control circuit 1343 may be configured to select CPC execution conditions and / or CPA execution conditions based on the identifier of the target PSCell. As another example, the PSCell configuration control circuit 1343 may be configured to receive CPC execution conditions and / or CPA execution conditions (e.g., from the SN), which instruct the UE to change at least one condition of the PSCell and / or add a PSCell (e.g., as combined above). Figures 7 to 12 (As discussed). The PSCell configuration control circuit 1343 may include functionality for obtaining (and / or receiving) execution conditions. For example, the PSCell configuration control circuit 1343 may be configured to (e.g., from SN) receive CPC execution conditions and / or CPA execution conditions, as described above. Figures 7 to 12 The PSCell configuration control circuit 1343, as discussed above, may include functionality for generating a message that excludes execution conditions for candidate target PSCells. For example, the PSCell configuration control circuit 1343 may be configured to generate an SN add request message that does not include execution conditions for candidate target PSCells (e.g., as described above). Figures 7 to 12 (As discussed). The PSCell configuration control circuit 1343 may include functionality for outputting a message for sending execution conditions that exclude the target PSCell (and / or for sending the message). For example, the PSCell configuration control circuit 1343 may be configured to cooperate with the communication and processing circuit 1341 (e.g., indication) to send an SN add request message that does not include the execution conditions of the candidate target PSCell (e.g., as discussed above). Figures 7 to 12 (As discussed above). The PSCell configuration control circuit 1343 may include functionality for configuring CPC execution conditions. For example, the PSCell configuration control circuit 1343 may be configured to define CPC execution conditions using the identifier of the target PSCell (e.g., as described above). Figures 7 to 12 (As discussed).

[0216] The PSCell configuration control circuit 1343 may include functionality for generating CPA configurations. For example, the PSCell configuration control circuit 1343 may be configured to generate CPA configurations based on the identifier of the target PSCell (e.g., as described above). Figures 7 to 12 (As discussed). The PSCell configuration control circuit 1343 may include functionality for including CPA execution conditions in the CPA configuration. For example, the PSCell configuration control circuit 1343 may be configured to generate a CPA configuration that includes CPA execution conditions, or to modify a CPA configuration to include CPA execution conditions (e.g., as described above). Figures 7 to 12 (As discussed). The PSCell configuration control circuit 1343 may include functionality for including CPC execution conditions in the CPC configuration. For example, the PSCell configuration control circuit 1343 may be configured to generate a CPC configuration that includes CPC execution conditions, or to modify a CPC configuration to include CPC execution conditions (e.g., as described above). Figures 7 to 12 (As discussed).

[0217] Figure 14 This is a flowchart illustrating an example method 1400 for wireless communication according to some aspects of this disclosure. As described herein, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be required for all example implementations. In some examples, method 1400 may be... Figure 13 The method 1400 shown is executed as described in the diagram. In some examples, the method 1400 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0218] At box 1402, the base station (e.g., the primary node) can obtain from the target secondary node (SN) the secondary cell group (SCG) configuration and associated information set of the target primary / secondary cell (PSCell) identified for the user equipment. For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuitry 1343, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide a set of secondary cell group (SCG) configuration and associated information for the target primary / secondary cell (PSCell) identified by the user equipment, obtained from the target secondary node (SN). In some examples, the base station is the MN of a multiple radio access technology (multiple RAT)-dual connectivity (MR-DC) system serving user equipment.

[0219] In some examples, the target PSCell may initially be one of a group of candidate PSCells identified for the UE. This specific PSCell can then be selected by the UE for PSCell addition or modification.

[0220] In some examples, the associated information set may include an indication of whether the candidate target PSCell can support at least one radio bearer specified for adding or changing a conditional PSCell. In some examples, the base station may receive an SN add request confirmation message including SCG configuration and the associated information set. In some examples, the base station may receive an SN modify request confirmation message including SCG configuration and the associated information set. In some examples, the base station may receive an SN modify request message including SCG configuration and the associated information set.

[0221] At box 1404, the base station can modify the primary cell group (MCG) configuration of the target PSCell based on the associated information set. For example, as described above... Figure 13 The PSCell configuration control circuit 1343 shown and described can provide a component for modifying the primary cell group (MCG) configuration of a target PSCell based on an associated set of information.

[0222] In some examples, the associated information set specifies the set of radio bearers that the target PSCell cannot allow the master node to terminate. In some examples, the base station can remove the set of radio bearers that the target PSCell cannot allow the master node to terminate from the MCG configuration. In some examples, the base station can receive an SN add request confirmation message from the target SN, which includes the SCG configuration and the associated information set.

[0223] In some examples, the associated information set specifies a set of radio bearers that the target PSCell can allow to be terminated by secondary nodes (SNs). In some examples, the base station can add the set of radio bearers that the target PSCell can allow to be terminated by SNs to the MCG configuration. In some examples, the base station can receive a secondary node (SN) modification request confirmation message from the target SN, which includes the SCG configuration and the associated information set.

[0224] At box 1406, the base station can output a Conditional Primary / Secondary Cell (PSCell) Addition (CPA) configuration including MCG and SCG configurations for the target PSCell, or a Conditional PSCell Change (CPC) configuration including MCG and SCG configurations for the target PSCell, for transmission to the user equipment. For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can provide outputs including a Conditional PSCell Add (CPA) configuration of the target PSCell's MCG and SCG configurations, or a Conditional PSCell Change (CPC) configuration of the target PSCell's MCG and SCG configurations, for transmission to a user equipment.

[0225] In some examples, the base station can receive a secondary node (SN) add request confirmation message that includes an identifier of the target PSCell, and generate a CPA configuration based on that identifier. In some examples, the SN add request confirmation message includes at least one other identifier of at least another target PSCell, and the base station can generate a CPA configuration based on that other identifier. In some examples, the base station can receive a secondary node (SN) add request confirmation message that includes at least one identifier of a candidate target PSCell, and generate a CPA configuration based on at least one identifier.

[0226] In some examples, the base station may receive a secondary node (SN) add request acknowledgment message including the identifier of the target PSCell, receive CPA execution conditions using the identifier of the target PSCell, and include the CPA execution conditions in the CPA configuration. In some examples, the SN add request acknowledgment message includes at least another identifier of at least another target PSCell, and the base station may use at least another identifier of at least another target PSCell to receive at least another CPA execution condition, and include that at least another CPA execution condition in the CPA configuration. In some examples, the base station may receive a secondary node (SN) add request acknowledgment message including at least one identifier of a candidate target PSCell, and use at least one identifier of the candidate target PSCell to receive CPA execution conditions.

[0227] In some examples, the base station may receive a Conditional PSCell Change (CPC) execution condition for the target PSCell. In some examples, the base station may include the CPC execution condition in the CPC configuration. In some examples, the base station may receive a Secondary Node (SN) Add Request Acknowledgment message including the SCG configuration and associated information set for the target PSCell. In some examples, the base station may receive a Secondary Node (SN) Modification Request Acknowledgment message including the SCG configuration and associated information set for the target PSCell. In some examples, the base station may receive a Secondary Node (SN) Modification Requirement message including the SCG configuration and associated information set for the target PSCell.

[0228] In some examples, the base station can generate a secondary node (SN) add request message that excludes the execution conditions of candidate target PSCells and send the SN add request message to the target SN. In some examples, the base station can receive an SN add request acknowledgment message from the target SN after sending the SN add request message, which includes at least one identifier of the candidate target PSCell, configure CPC execution conditions using the at least one identifier of the candidate target PSCell, and include the CPC execution conditions in the CPC configuration. In some examples, the base station can receive an SN add request acknowledgment message from the target SN after sending the secondary node (SN) add request message, which includes the identifier of the target PSCell, configure CPC execution conditions using the identifier of the target PSCell, and include the CPC execution conditions in the CPC configuration.

[0229] In some examples, the base station can receive from the target secondary node at least another SCG configuration and at least another set of associated information for at least another target PSCell identified for the user equipment, and modify at least another MCG configuration for at least another target PSCell based on the at least another set of associated information. Furthermore, the base station can send to the user equipment at least another CPA configuration including at least another MCG configuration and at least another SCG configuration for at least another target PSCell, or at least another CPC configuration including at least another MCG configuration and at least another SCG configuration for at least another target PSCell.

[0230] In some examples, the base station may receive at least another CPA execution condition or at least another CPC execution condition for at least another target PSCell. Furthermore, the base station may include at least another CPA execution condition in at least another CPA configuration or at least another CPC execution condition in at least another CPC configuration.

[0231] Figure 15 This is a flowchart illustrating an example method 1500 for wireless communication according to some aspects of this disclosure. As described herein, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be required for all example implementations. In some examples, method 1500 may be... Figure 13 The BS 1300 shown is executed. In some examples, method 1500 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0232] At box 1502, the base station (e.g., the primary node) can receive a request confirmation message from the secondary node (SN) including the identifier of the target primary / secondary cell (PSCell). For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuitry 1343, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide components for a secondary node (SN) to add a request confirmation message, which includes at least one identifier of the candidate primary / secondary cell (PSCell). In some examples, the BS is the MN for a multiple radio access technology (multiple RAT)-dual connectivity (MR-DC) system serving user equipment.

[0233] At box 1504, the base station can output a Conditional PSCell Addition (CPA) configuration generated based on this identifier for transmission to the user equipment. For example, as described above... Figure 13As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can provide components for outputting identifier-based conditional PSCell Addition (CPA) configurations for transmission to user equipment.

[0234] In some examples, the base station can use the identifier of the target PSCell to determine the CPA execution conditions and include the CPA execution conditions in the CPA configuration. In some examples, the base station can generate a secondary node (SN) add request message that includes at least one identifier and send an SN add request message to the target SN. In some examples, the SN add request acknowledgment message includes at least another identifier of at least another target PSCell, and the base station can generate the CPA configuration based on at least another identifier.

[0235] In some examples, the base station can generate a secondary node (SN) add request message that excludes the execution conditions of the target PSCell and send the SN add request message to the target SN. In some examples, the base station can receive an SN add request acknowledgment message from the target SN after sending the SN add request message, which includes the identifier of the target PSCell.

[0236] In some examples, the base station can receive a secondary cell group (SCG) configuration and associated information set from the target secondary node (SN), modify the primary cell group (MCG) configuration based on the associated information set, and include the MCG configuration and SCG configuration in the CPA configuration. In some examples, the associated information set specifies the set of radio bearers that the target PSCell cannot allow the primary node to terminate. In some examples, the base station can remove the set of radio bearers that the target PSCell cannot allow the primary node to terminate from the MCG configuration. In some examples, the associated information set specifies a set of radio bearers that the candidate target PSCell can allow to terminate from secondary nodes (SNs). In some examples, the base station can add a set of radio bearers that the candidate target PSCell can allow the SN to terminate to the MCG configuration.

[0237] Figure 16 This is a flowchart illustrating an example method 1600 for wireless communication according to some aspects of this disclosure. As described herein, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be required for all example implementations. In some examples, method 1600 may be... Figure 13 The method 1600 shown is executed by BS 1300. In some examples, method 1600 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0238] At box 1602, the base station (e.g., a source-secondary node) can determine the corresponding conditional primary-secondary cell (PSCell) change (CPC) execution conditions for at least one candidate target PSCell. In some examples, the BS is the source SN for the MR-DC system serving the user equipment. For example, as combined with the above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can be provided as components.

[0239] At box 1604, the base station can determine the corresponding CPC execution conditions for each candidate target PSCell. For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can be provided as components.

[0240] In some examples, a conditional PSCell change (CPC) procedure identifies at least one target SN and an associated candidate target PSCell. In some examples, for an inter-SN conditional PSCell change (CPC) procedure initiated by an SN, at least one target SN and an associated candidate target PSCell are identified. In some examples, the method may further include receiving a second message that includes configuration information for the group of radio bearers (RBs) whose CPC procedure for the candidate target PSCell is terminated by the SN.

[0241] In some examples, the method may also include identifying at least one SN-terminated RB in a group of SN-terminated RBs that the candidate target PSCell can support, and sending a third message including an indication of at least one SN-terminated RB.

[0242] Figure 17 This is a flowchart illustrating an example method 1700 for wireless communication according to some aspects of this disclosure. As described herein, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be required for all example implementations. In some examples, method 1700 may be... Figure 13 The BS 1300 shown is executed. In some examples, method 1700 can be executed by any suitable means or component for performing the functions or algorithms described below.

[0243] At box 1702, the base station (e.g., the master node) may receive a message including an indication of whether a candidate primary / secondary cell (PSCell) can support adding or changing at least one radio bearer (RB) specified for a conditional PSCell. For example, as combined above. Figure 13As shown and described, the PSCell configuration control circuitry 1343, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide components that receive messages including an indication of whether a candidate primary / secondary cell (PSCell) can support adding or changing at least one radio bearer (RB) specified for a conditional PSCell. In some examples, the BS is the MN for a Multiple Radio Access Technology (Multiple RAT) - Dual Connectivity (MR-DC) system serving user equipment.

[0244] At box 1704, the base station can modify the Primary Cell Group (MCG) configuration based on this instruction. For example, in conjunction with the above... Figure 13 The PSCell configuration control circuit 1343 shown and described can provide a component for modifying the primary cell group (MCG) configuration based on the instruction.

[0245] At box 1706, the base station can send MCG configuration to the user equipment. For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can provide components for sending MCG configurations to user equipment.

[0246] In some examples, the instruction specifies a set of MN-terminated RBs that the candidate target PSCell cannot allow. In some examples, modifying the MCG configuration may include removing the MN-terminated RB group that the candidate target PSCell cannot allow from the MCG configuration. In some examples, receiving messages may include receiving an SN add request acknowledgment message from the target secondary node (SN). In some examples, sending the MCG configuration may include sending a Conditional PSCell Add (CPA) configuration including the MCG configuration, or sending a Conditional PSCell Change (CPC) configuration including the MCF configuration.

[0247] In some examples, the instruction specifies a set of secondary node (SN) terminated RBs that the candidate target PSCell can use. For example, the instruction could specify a set of secondary node (SN) terminated RBs that the candidate target PSCell is allowed to use. In some examples, modifying the MCG configuration could include adding a set of MN terminated RBs that the candidate target PSCell is allowed to use to the MCG configuration. In some examples, receiving messages could include receiving an SN modification request acknowledgment message from a secondary node (SN). In some examples, sending the MCG configuration could include sending a conditional PSCell change (CPC) configuration that includes the MCG configuration.

[0248] In some examples, the method may also include receiving a secondary node (SN) add request confirmation message including an identifier of a candidate target PSCell, determining (e.g., configuring) condition PSCell add (CPA) execution conditions using the identifier of the candidate target PSCell, and sending a CPA configuration including the CPA execution conditions to the user equipment.

[0249] In some examples, the method may also include generating a secondary node (SN) add request message that includes the execution conditions of the candidate target PSCell, and sending the SN add request message to the target SN.

[0250] In some examples, the method may further include receiving configuration information from a target secondary node (SN), wherein the configuration information may include at least one of the following: a secondary cell group (SCG) configuration of the candidate target PSCell, a conditional PSCell change (CPC) execution condition of the candidate target PSCell, or a combination thereof. In some examples, the method may further include generating a CPC configuration based on the configuration information and sending the CPC configuration to the user equipment. In some examples, receiving the configuration information may include receiving an SN add request confirmation message including the configuration information, or receiving an SN modify request confirmation message including the configuration information, or receiving an SN modify requirement message including the configuration information.

[0251] In some examples, the method may further include generating a secondary node (SN) add request message for excluding candidate target PSCells from the execution conditions, and sending the SN add request message to the target SN. In some examples, the method may further include receiving an SN add request confirmation message including the identifier of the candidate target PSCell from the target SN after sending the SN add request message, determining (e.g., configuring) the conditional PSCell add (CPC) execution conditions using the identifier of the candidate target PSCell, and sending a CPC configuration including the CPC execution conditions to the user equipment.

[0252] In some examples, the method may also include generating a secondary node (SN) modification request message that includes configuration information of the detached bearer for SN termination of the candidate target PSCell, and sending the SN modification request message to the SN.

[0253] Figure 18 This is a flowchart illustrating an example method 1800 for wireless communication according to some aspects of this disclosure. As described herein, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be required for all example implementations. In some examples, method 1800 may be... Figure 13The BS 1300 shown is executed. In some examples, method 1800 may be executed by any suitable means or component for performing the functions or algorithms described below.

[0254] At box 1802, the base station (e.g., the target secondary node) may receive a first message including an indication of a set of radio bearers (RBs) to be configured for a Conditional PSCell Add (CPA) procedure or a Conditional PSCell Change (CPC) procedure. For example, as combined above... Figure 13 As shown and described, the PSCell configuration control circuitry 1343, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide components for receiving a first message including an indication of a set of radio bearers (RBs) to be configured for a Conditional PSCell Add (CPA) or Conditional PSCell Change (CPC) procedure. In some examples, the BS is a target SN for an MR-DC system serving user equipment.

[0255] At box 1804, the base station can identify at least one RB from an RB group that is not supported by the candidate target primary / secondary cell (PSCell). For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuit 1343 can provide a component that identifies at least one RB in a group of RBs that are not supported by the candidate target primary / secondary cell (PSCell).

[0256] At box 1806, the base station may send a second message including an indication of at least one RB. For example, as combined with the above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can provide components for transmitting a second message including an indication of at least one RB.

[0257] In some examples, the group of RBs may include a group of RBs terminated by a primary node (MN). In some examples, the group of RBs may include a group of RBs terminated by secondary nodes (SN).

[0258] In some examples, the first message is a secondary node (SN) add request message. In other examples, the second message is a secondary node (SN) add request confirmation message.

[0259] In some examples, the first message may also include indications of multiple candidate target PSCells. In some examples, the second message may also include identifiers of multiple candidate target PSCells.

[0260] In some examples, the second message may also include instructions for multiple candidate target PSCells, and the corresponding CPC execution conditions for each of the multiple candidate target PSCells.

[0261] In some examples, the first message does not indicate the CPC execution conditions for the candidate target PSCell, and the second message includes the identifier of the candidate target PSCell. In some examples, the identifier of the candidate target PSCell is sent at the top level of the Information Element (IE) structure visible to the master node (MN).

[0262] Figure 19 This is a flowchart illustrating an example method 1900 for wireless communication according to some aspects of this disclosure. As described herein, some or all of the illustrated features may be omitted in certain implementations within the scope of this disclosure, and some illustrated features may not be required for all example implementations. In some examples, method 1900 may be... Figure 13 The BS 1300 shown is executed. In some examples, method 1900 can be executed by any suitable means or component for performing the functions or algorithms described below.

[0263] At box 1902, the base station (e.g., a source secondary node) can identify at least one target secondary node (SN) and an associated candidate target primary / secondary cell (PSCell). For example, as combined above... Figure 13 As shown and described, the PSCell configuration control circuitry 1343, together with the communication and processing circuitry 1341 and the transceiver 1310, can provide components for identifying at least one target secondary node (SN) and associated candidate primary / secondary cells (PSCells). In some examples, the BS is the source SN for a MR-DC system serving user equipment.

[0264] At box 1904, the base station can determine the corresponding CPC execution conditions for each candidate target PSCell. For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can provide components for determining the corresponding CPC execution conditions for each of the candidate target PSCells.

[0265] At box 1906, the base station can send a first message specifying the CPC execution condition for each candidate target PSCell in the candidate target PSCell list. For example, as described above... Figure 13 As shown and described, the PSCell configuration control circuit 1343, together with the communication and processing circuit 1341 and the transceiver 1310, can provide components for sending a first message that specifies the corresponding CPC execution conditions for each of the candidate target PSCells.

[0266] In some examples, the first message may be a message indicating that the SN needs to change. In some examples, the first message may be a message indicating that the SN needs to modify. In some examples, the second message may be a message indicating that the SN needs to modify.

[0267] In some examples, the Conditional PSCell Change (CPC) process identifies at least one target SN and an associated candidate target PSCell.

[0268] In some examples, for an inter-SN Conditional PSCell Change (CPC) procedure initiated by an SN, at least one target SN and an associated candidate target PSCell are identified. In some examples, the method may also include receiving a second message that includes settings information for the group of radio bearers (RBs) whose CPC procedure for the candidate target PSCell is terminated by the SN.

[0269] In some examples, the method may also include identifying at least one SN-terminated RB in a group of SN-terminated RBs that the candidate target PSCell can support, and sending a third message including an indication of at least one SN-terminated RB.

[0270] In some examples, a method for wireless communication at a master node (MN) may include receiving a message that includes an indication of whether a candidate primary and secondary cell (PSCell) can support adding or changing at least one radio bearer (RB) for a conditional PSCell, modifying the primary cell group (MCG) configuration based on the indication, and sending the MCG configuration to the user equipment.

[0271] In some examples, the master node (MN) may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to receive, via the transceiver, a message indicating whether a candidate primary / secondary cell (PSCell) can support adding or changing at least one radio bearer (RB) specified for a conditional PSCell, modify the primary cell group (MCG) configuration based on the indication, and transmit the MCG configuration to the user equipment via the transceiver.

[0272] In some examples, the master node (MN) may include components for receiving messages including an indication of whether a candidate primary / secondary cell (PSCell) can support adding or changing at least one radio bearer (RB) specified for a conditional PSCell, components for modifying the primary cell group (MCG) configuration based on the indication, and components for sending the MCG configuration to the user equipment.

[0273] In some examples, a manufactured item for use by a master node (MN) includes a computer-readable medium containing instructions that can be executed by one or more processors of the MN to receive messages including whether a candidate primary / secondary cell (PSCell) can support adding or changing at least one radio bearer (RB) for a conditional PSCell, modifying the primary cell group (MCG) configuration based on the instructions, and sending the MCG configuration to the user equipment.

[0274] In some examples, a method for wireless communication at a target secondary node may include receiving a first message including an indication of a set of radio bearers (RBs) to be configured for a Conditional PSCell Add (CPA) procedure or a Conditional PSCell Change (CPC) procedure, identifying at least one RB in a group of RBs not supported by the candidate target primary / secondary cell (PSCell), and sending a second message including the indication of the at least one RB.

[0275] In some examples, the target secondary node may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to receive a first message via the transceiver, the message including an indication of a set of radio bearers (RBs) to be configured for a Conditional PSCell Add (CPA) procedure or a Conditional PSCell Change (CPC) procedure, identifying at least one RB in a group of RBs not supported by the candidate target primary / secondary cell (PSCell), and to transmit a second message via the transceiver including the indication of the at least one RB.

[0276] In some examples, the target secondary node may include components for receiving a first message including an indication of a set of radio bearers (RBs) to be configured for a Conditional PSCell Add (CPA) procedure or a Conditional PSCell Change (CPC) procedure, components for identifying at least one RB in a group of RBs not supported by the candidate target primary / secondary cell (PSCell), and components for sending a second message including the indication of the at least one RB.

[0277] In some examples, a manufactured article for use by a target secondary node includes a computer-readable medium storing instructions executable by one or more processors of the target secondary node to receive a first message including an indication of a set of radio bearers (RBs) to be configured for a Conditional PSCell Add (CPA) or Conditional PSCell Change (CPC) procedure, identifying at least one RB in a group of RBs not supported by the candidate target primary / secondary cell (PSCell), and sending a second message including the indication of the at least one RB.

[0278] In some examples, a method for wireless communication at a source secondary node may include identifying at least one target secondary node (SN) and associated candidate target primary and secondary cells (PSCells), determining the corresponding conditional PSCell change (CPC) execution condition for each of the candidate target PSCells, and sending a first message specifying the corresponding CPC execution condition for each of the candidate target PSCells.

[0279] In some examples, the source secondary node may include a transceiver, a memory, and a processor communicatively coupled to the transceiver and the memory. The processor and memory may be configured to identify at least one target secondary node (SN) and associated candidate target primary / secondary cells (PSCells), determine the corresponding conditional PSCell change (CPC) execution condition for each of the candidate target PSCells, and transmit a first message specifying the corresponding CPC execution condition for each of the candidate target PSCells via the transceiver.

[0280] In some examples, the source secondary node may include components for identifying at least one target secondary node (SN) and associated candidate target primary and secondary cells (PSCells), components for determining the corresponding conditional PSCell change (CPC) execution condition for each of the candidate target PSCells, and components for sending a first message specifying the corresponding CPC execution condition for each of the candidate target PSCells.

[0281] In some examples, the manufactured article used by the source secondary node includes a computer-readable medium storing instructions executable by one or more processors of the target secondary node to identify at least one target secondary node (SN) and associated candidate target primary / secondary cells (PSCells), determine corresponding conditional PSCell change (CPC) execution conditions for each of the candidate target PSCells, and send a first message specifying the corresponding CPC execution conditions for each of the candidate target PSCells.

[0282] In one configuration, base station 1300 includes components for receiving from a target secondary node (SN) a set of secondary cell group (SCG) configuration and associated information for a target primary / secondary cell (PSCell) identified as a user equipment, components for modifying the primary cell group (MCG) configuration of the target PSCell based on the associated information set, and components for sending to the user equipment a conditional PSCell Add (CPA) configuration including the MCG and SCG configurations for the target PSCell, or a conditional PSCell Change (CPC) configuration including the MCG and SCG configurations for the target PSCell. In one configuration, base station 1300 includes components for receiving a secondary node (SN) add request confirmation message including an identifier of the target primary / secondary cell (PSCell), and components for sending to the user equipment a conditional PSCell Add (CPA) configuration generated based on the identifier. In one aspect, the aforementioned components may be… Figure 13 The processor 1304 shown is configured to perform the functions described in the foregoing components (e.g., as discussed above). In another aspect, the foregoing components may be circuitry or any device configured to perform the functions described in the foregoing components.

[0283] Of course, in the above example, the circuitry included in processor 1304 is provided merely as an example, and other means for performing the functions described herein may include, but are not limited to, instructions stored in computer-readable medium 1306, or Figure 1 , 2 and any other suitable means or apparatus described in any one or more of 4 to 13, and utilizing, for example, those described herein. Figures 14 to 19 The method and / or algorithm described.

[0284] Figures 14 to 19 The methods illustrated may include additional aspects, such as any single aspect or any combination of aspects described below, and / or aspects related to one or more other processes described elsewhere herein. An overview of several aspects of this disclosure is provided below. In some examples, the means of performing one or more aspects described herein may be a chipset (e.g., at least one integrated circuit). In some examples, the means of performing one or more aspects described herein may be a master node (e.g., which includes a chipset and a transceiver).

[0285] Aspect 1: A method for wireless communication at a device (e.g., a master node), the method comprising: obtaining from a target secondary node (SN) a set of secondary cell group (SCG) configurations and associated information for a target primary / secondary cell (PSCell) identified as a user equipment; modifying the primary cell group (MCG) of the target PSCell based on the set of associated information; and outputting a conditional PSCell Addition (CPA) configuration including the MCG configuration and SCG configuration for the target PSCell or a conditional PSCell Change (CPC) configuration including the MCG configuration and SCG configuration for the target PSCell for transmission to the user equipment.

[0286] Aspect 2: According to the method of Aspect 1, the associated information set specifies the set of radio bearers that the target PSCell cannot allow the master node to terminate.

[0287] Aspect 3: According to the method of aspect 2, wherein modifying the MCG configuration includes removing from the MCG configuration the set of radio bearers that the target PSCell cannot allow the master node to terminate.

[0288] Aspect 4: According to the method of aspect 1, wherein the associated information set specifies the set of radio bearers that the target PSCell can allow the secondary node (SN) to terminate.

[0289] Aspect 5: According to the method of aspect 4, modifying the MCG configuration includes adding to the MCG configuration a set of radio bearers that the target PSCell can allow for SN termination.

[0290] Aspect 6: The method according to any one of Aspects 1 to 5 further includes: obtaining a secondary node (SN) that includes an identifier of the target PSCell and adding a request confirmation message; and generating a CPA configuration based on the identifier.

[0291] Aspect 7: According to the method of aspect 6, wherein: the SN adds a request confirmation message including at least another identifier of at least another target PSCell; and the method further includes generating a CPA configuration based on at least another identifier.

[0292] Aspect 8: The method according to any one of Aspects 1 to 7 further includes: obtaining a secondary node (SN) that includes the identifier of the target PSCell to add a request confirmation message; obtaining the CPA execution condition using the identifier of the target PSCell; and including the CPA execution condition in the CPA configuration.

[0293] Aspect 9: According to the method of aspect 8, wherein: the SN adds a request confirmation message including at least another identifier of at least another target PSCell; the method further includes using at least another identifier of at least another target PSCell to obtain at least another CPA execution condition; and the method further includes including at least another CPA execution condition in the CPA configuration.

[0294] Aspect 10: The method according to any one of aspects 1 to 9 further includes: obtaining the conditional PSCell change (CPC) execution condition of the target PSCell.

[0295] Aspect 11: According to the method of aspect 10, it also includes: including CPC execution conditions in the CPC configuration.

[0296] Aspect 12: The method according to any one of Aspects 1 to 11 further includes: obtaining a secondary node (SN) add request confirmation message including the SCG configuration for the target PSCell and a set of associated information.

[0297] Aspect 13: The method according to any one of Aspects 1 to 11 further includes: obtaining a secondary node (SN) modification request confirmation message that includes the SCG configuration and associated information set for the target PSCell.

[0298] Aspect 14: The method according to any one of Aspects 1 to 11 further includes: obtaining the message required for modification of the secondary node (SN), which includes the SCG configuration and associated information set for the target PSCell.

[0299] Aspect 15: The method according to any one of aspects 1 to 14 further includes: generating a secondary node (SN) add request message to exclude the execution conditions for the candidate target PSCell; and outputting an SN add request message for transmission to the target SN.

[0300] Aspect 16: The method according to aspect 15 further includes: after outputting the SN add request message, obtaining from the target SN a secondary node (SN) add request confirmation message including the identifier of the target PSCell; configuring CPC execution conditions using the identifier of the target PSCell; and including the CPC execution conditions in the CPC configuration.

[0301] Aspect 17. The method of any one of Aspects 1 to 16, wherein the associated information set includes an indication of whether the candidate target PSCell is capable of supporting the addition or modification of at least one radio bearer specified for the conditional PSCell.

[0302] Aspect 18: The method according to any one of Aspects 1 to 17 further includes: obtaining from the target secondary node at least another SCG configuration and at least another set of associated information for at least another target PSCell identified by the user equipment; modifying at least another MCG configuration for at least another target PSCell based on the at least another set of associated information; and outputting at least another CPA configuration including at least another MCG configuration and at least another SCG configuration for at least another target PSCell or at least another CPC configuration including at least another MCG configuration and at least another SCG configuration for at least another target PSCell for transmission to the user equipment.

[0303] Aspect 19: The method according to any one of Aspects 1 to 18 further includes: obtaining at least another CPA execution condition or at least another CPC execution condition of at least another target PSCell; including at least another CPA execution condition in at least another CPA configuration or including at least another CPC execution condition in at least another CPC configuration.

[0304] Aspect 20: The method of any one of Aspects 1 to 19, wherein the master node is part of a multi-radio access technology (multi-RAT)-dual connectivity (MR-DC) system for serving user equipment.

[0305] Aspect 21: The method according to any one of Aspects 1 to 20 further includes: receiving from the target SN an SCG configuration and associated information set for the target PSCell; and sending to the user equipment a CPA configuration including an MCG configuration and an SCG configuration for the target PSCell or a CPC configuration including an MCG configuration and an SCG configuration for the target PSCell.

[0306] Aspect 22: A method for wireless communication at a device (e.g., a master node), the method comprising: obtaining a secondary node (SN) add request confirmation message including an identifier of a target primary secondary cell (PSCell); and outputting a conditional PSCell add (CPA) configuration generated based on the identifier for transmission to a user equipment.

[0307] Aspect 23: According to the method of aspect 22, it further includes: determining the CPA execution conditions using the identifier of the target PSCell; and including the CPA execution conditions in the CPA configuration.

[0308] Aspect 24: The method according to any one of Aspects 22 to 23, wherein: the SN adds a request confirmation message including at least another identifier of at least another target PSCell; and the process further includes generating a CPA configuration based on at least another identifier.

[0309] Aspect 25: The method according to any one of aspects 22 to 24 further includes: generating a secondary node (SN) add request message for excluding the execution conditions of the target PSCell; and outputting an SN add request message for transmission to the target SN.

[0310] Aspect 26: According to the method of aspect 25, it further includes: after outputting the SN add request message, obtaining the SN add request confirmation message from the target SN.

[0311] Aspect 27: The method according to any one of Aspects 22 to 26 further includes: obtaining a secondary cell group (SCG) configuration and a set of associated information from a target secondary node (SN); modifying the primary cell group (MCG) configuration based on the set of associated information; and including the MCG configuration and the SCG configuration in the CPA configuration.

[0312] Aspect 28: According to the method of aspect 27, wherein: the associated information set specifies the set of radio bearers that the target PSCell cannot allow the master node to terminate; wherein modifying the MCG configuration includes removing the set of radio bearers that the target PSCell cannot allow the master node to terminate from the MCG configuration.

[0313] Aspect 29: According to the method of aspect 27, wherein: the associated information set specifies a set of radio bearers terminated by secondary nodes (SNs) that the target PSCell can allow; wherein modifying the MCG configuration includes adding to the MCG configuration a set of radio bearers terminated by SNs that the target PSCell can allow.

[0314] Aspect 30: The method according to any one of aspects 22 to 29 further includes: receiving the SN add request confirmation message; and sending CPA configuration to the user equipment.

[0315] Aspect 31: An apparatus configured for wireless communication, comprising an interface and a processing system coupled to the interface, wherein the processing system is configured to perform any one of aspects 1 to 21.

[0316] Aspect 32: An apparatus configured for wireless communication, comprising at least one component for performing any one of aspects 1 to 21.

[0317] Aspect 33: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to perform any one of aspects 1 to 21.

[0318] Aspect 34: An apparatus configured for wireless communication, comprising an interface and a processing system coupled to the interface, wherein the processing system is configured to perform any one of aspects 22 to 30.

[0319] Aspect 35: An apparatus configured for wireless communication, comprising at least one component for performing any one of aspects 22 to 30.

[0320] Aspect 36: A non-transitory computer-readable medium storing computer-executable code, including code for causing a device to perform any one of aspects 22 to 30.

[0321] Several aspects of wireless communication networks have been presented with reference to example implementations. As will be readily understood by those skilled in the art, the various aspects described herein can be extended to other telecommunications systems, network architectures, and communication standards.

[0322] As examples, various aspects can be implemented within other systems defined by 3GPP, such as LTE, Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). These aspects can also be extended to systems defined by 3GPP2, such as CDMA2000 and / or Evolved Data Optimization (EV-DO). Other examples can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architecture, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0323] In this disclosure, the term “exemplary” is used to mean “serving as an example, instance, or illustration.” Any implementation or aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects of this disclosure. Similarly, the term “aspect” does not require that all aspects of this disclosure include the features, advantages, or modes of operation discussed. The term “coupled” is used herein to refer to direct or indirect coupling between two objects. For example, if object A is physically in contact with object B, and object B is in contact with object C, then objects A and C can be considered coupled to each other even if they are not in direct physical contact. For example, a first object can be coupled to a second object even if the first object never has direct physical contact with the second object. The terms “circuit” and “circuitry” are used broadly and are intended to include, but are not limited to, hardware implementations of electrical devices and conductors that, when connected and configured, are capable of performing the functions described in this disclosure, as well as software implementations of information and instructions that, when executed by a processor, perform the functions described in this disclosure. As used herein, the term “determine” can include a wide variety of actions. For example, "determine" can include calculation, computation, processing, derivation, investigation, search (e.g., searching in a table, database, or other data structure), determination, parsing, selection, selection, creation, receiving (e.g., receiving information), access (e.g., accessing data in memory), and the like.

[0324] Figures 1 to 19 One or more components, steps, features, and / or functions shown may be rearranged and / or combined into a single component, step, feature, or function, or embodied in several components, steps, and functions. Additional elements, components, steps, and / or functions may be added without departing from the novel features disclosed herein. Figure 1 , 2 Any of the apparatuses, devices, and / or components shown in any of 4 to 13 may be configured to perform one or more methods, features, or steps described herein. The novel algorithms described herein may also be efficiently implemented in software and / or hardware.

[0325] It should be understood that the specific order or hierarchy of steps in the disclosed method is an illustration of an exemplary process. Based on design preferences, it should be understood that the specific order or hierarchy of steps in the method may be rearranged. The fact that the appended claims present the elements of various steps in a sample order does not imply limitation to the specific order or hierarchy presented, unless specifically stated therein.

[0326] The above description is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects shown herein, but are given the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, reference to an element in the singular does not mean "one and only one," but rather "one or more." Unless otherwise specifically stated, the term "some" means one or more. The phrase "at least one" in the list of items refers to any combination of these items, including a single member. For example, "at least one of a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents of the elements of the various aspects described in this disclosure that are known or subsequently known to those skilled in the art are expressly incorporated herein by reference and are intended to be included in the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is expressly enumerated in the claims.

Claims

1. An apparatus for wireless communication, comprising: At least one transceiver; interface; as well as The processing system coupled to the interface is configured to: The system receives a secondary node (SN) add request confirmation message via at least one transceiver and via the interface. The SN add request confirmation message includes the secondary cell group (SCG) configuration and associated information set of the target cell associated with the user equipment. Modify the primary cell group (MCG) configuration of the target cell based on the associated information set; and The conditional cell addition configuration, which includes the modified MCG configuration and the SCG configuration for the target cell, or the conditional cell change configuration, which includes the modified MCG configuration and the SCG configuration for the target cell, is sent to the user equipment via at least one transceiver and via the interface.

2. The apparatus of claim 1, wherein the associated information set specifies a set of radio bearers that the target cell cannot allow the master node to terminate.

3. The apparatus of claim 2, wherein, in order to modify the MCG configuration, the processing system is further configured to: Remove the set of radio bearers that the target cell cannot allow the master node to terminate from the MCG configuration.

4. The apparatus of claim 1, wherein the associated information set specifies the set of radio bearers that the target cell can allow to be terminated by secondary node SNs.

5. The apparatus of claim 4, wherein, in order to modify the MCG configuration, the processing system is further configured to: Add to the MCG configuration a set of radio bearers that the target cell can allow to be terminated by the SN.

6. The apparatus of claim 1, wherein the processing system is further configured to: Receive, via at least one transceiver and via the interface, the SN add request confirmation message including the identifier of the target cell; and The condition cell configuration is added based on the identifier.

7. The apparatus according to claim 6, wherein: The SN add request confirmation message includes at least one other identifier of at least another target cell; and The processing system is also configured to generate the conditional cell addition configuration based on the at least one other identifier.

8. The apparatus of claim 1, wherein the processing system is further configured to: Receive a secondary node SN add request confirmation message including the identifier of the target cell via at least one transceiver and via the interface; The condition cell is received via at least one transceiver and via the interface using the identifier of the target cell to add execution conditions; and The condition cell addition configuration includes the condition cell addition execution conditions.

9. The apparatus according to claim 8, wherein: The SN add request confirmation message includes at least one other identifier of at least another target cell; The processing system is also configured to use the at least one other identifier of the at least one other target cell to receive at least one other condition cell via at least one transceiver and via the interface to add execution conditions; and The processing system is also configured to include the at least one other condition cell addition execution condition in the condition cell addition configuration.

10. The apparatus of claim 1, wherein the processing system is further configured to: The target cell condition change execution condition is received via at least one transceiver and via the interface.

11. The apparatus of claim 10, wherein the processing system is further configured to: Generate the conditional cell change configuration, which includes the conditions for executing the conditional cell change.

12. The apparatus of claim 1, wherein, in order to receive the SCG configuration and the associated information set for the target cell, the processing system is further configured to: The secondary node SN add request confirmation message, which includes the SCG configuration for the target cell and the associated information set, is received via at least one transceiver and via the interface.

13. The apparatus of claim 1, wherein, in order to receive the SCG configuration and the associated information set for the target cell, the processing system is further configured to: The secondary node SN modification request confirmation message, which includes the SCG configuration for the target cell and the associated information set, is received via at least one transceiver and via the interface.

14. The apparatus of claim 1, wherein, in order to receive the SCG configuration and the associated information set for the target cell, the processing system is further configured to: The secondary node SN modification message, including the SCG configuration for the target cell and the associated information set, is received via at least one transceiver and via the interface.

15. The apparatus of claim 1, wherein the processing system is further configured to: Generate a request message to add the secondary node SN to exclude the execution conditions used for candidate target cells; and The SN add request message is sent to the target SN via at least one transceiver and via the interface.

16. The apparatus of claim 15, wherein the processing system is further configured to: After sending the SN add request message, a secondary node SN add request confirmation message including the identifier of the target cell is received from the target SN via at least one transceiver and via the interface; The identifier of the target cell is used to configure the condition cell to change the execution conditions; and The conditional cell change configuration includes the conditional cell change execution conditions.

17. The apparatus of claim 1, wherein the associated information set includes an indication of whether the candidate target cell can support at least one radio bearer specified for adding or changing the condition cell.

18. The apparatus of claim 1, wherein the processing system is further configured to: Receive from the target secondary node via at least one transceiver and via the interface at least one other target cell configuration and at least one other set of associated information associated with the user equipment; Modify at least one more MCG configuration of the at least one more target cell based on the at least one other set of associated information; and Sending at least one condition cell add configuration, including at least one modified MCG configuration and at least one SCG configuration for the at least one target cell, or at least one condition cell change configuration, including at least one modified MCG configuration and at least one SCG configuration for the at least one target cell, to the user equipment via at least one transceiver and via the interface.

19. The apparatus of claim 18, wherein the processing system is further configured to: The execution conditions are added to or changed by at least one condition cell of the at least other target cell, received via at least one transceiver and via the interface; and The configuration for adding at least one condition cell includes the execution condition for adding at least one condition cell, or the configuration for changing at least one condition cell includes the execution condition for changing at least one condition cell.

20. A method for wireless communication by a device, the method comprising: Receive a secondary node SN addition request confirmation message, wherein the SN addition request confirmation message includes the secondary cell group (SCG) configuration and associated information set of the target cell associated with the user equipment; Modify the primary cell group (MCG) configuration of the target cell based on the associated information set; and Send to the user equipment a conditional cell addition configuration including the modified MCG configuration and the SCG configuration for the target cell, or a conditional cell change configuration including the modified MCG configuration and the SCG configuration for the target cell.

21. An apparatus for wireless communication, comprising: At least one transceiver; interface; as well as The processing system coupled to the interface is configured to: Receive a secondary node SN add request confirmation message including the identifier of the target cell via at least one transceiver and via the interface; Receive a set of secondary cell group (SCG) configuration and associated information from the target secondary node (SN) via at least one transceiver and via the interface; Modify the primary cell group (MCG) configuration based on the aforementioned set of related information; and A conditional cell addition configuration based on the identifier is sent to the user equipment via at least one transceiver and via the interface, wherein the modified MCG configuration and the SCG configuration are included in the conditional cell addition configuration.

22. The apparatus of claim 21, wherein the processing system is further configured to: The identifier of the target cell is used to determine the condition cell for adding execution conditions; and The condition cell addition configuration includes the condition cell addition execution conditions.

23. The apparatus according to claim 21, wherein: The SN add request confirmation message includes at least one other identifier of at least another target cell; and The processing system is also configured to generate the conditional cell addition configuration based on the at least one other identifier.

24. The apparatus of claim 21, wherein the processing system is further configured to: Generate an SN add request message that excludes the execution conditions of the target cell; and The SN add request message is sent to the target SN via at least one transceiver and via the interface.

25. The apparatus of claim 24, wherein the processing system is further configured to: After sending the SN add request message, the SN add request confirmation message is received from the target SN via at least one transceiver and via the interface.

26. The apparatus according to claim 21, wherein: The associated information set specifies the set of radio bearers that the target cell cannot allow the master node to terminate; and In order to modify the MCG configuration, the processing system is also configured to remove from the MCG configuration a set of radio bearers whose termination by the master node is not permitted by the target cell.

27. The apparatus according to claim 21, wherein: The associated information set specifies the set of radio bearers that the target cell can allow to be terminated by secondary node SNs; and In order to modify the MCG configuration, the processing system is also configured to add to the MCG configuration a set of radio bearers whose SN termination is permitted by the target cell.

28. A method for wireless communication by a device, the method comprising: Receive the secondary node SN add request confirmation message, which includes the identifier of the target cell; Receive the secondary cell group (SCG) configuration and associated information set from the target secondary node (SN); Modify the primary cell group (MCG) configuration based on the aforementioned set of related information; as well as Send a conditional cell addition configuration generated based on the identifier to the user equipment, wherein the modified MCG configuration and the SCG configuration are included in the conditional cell addition configuration.

29. An apparatus for wireless communication, comprising: Components for performing the method according to claim 20 or 28.

30. A computer-readable medium having program code recorded thereon, wherein, The program code may be executed by one or more processors to cause the one or more processors to perform the method according to claim 20 or 28.

31. A computer program product comprising computer-readable instructions, wherein, When the computer-readable instructions are executed by at least one processor of the device, the computer-readable instructions cause the device to perform the method according to claim 20 or 28.

Images