Simultaneous Connection Switching User Equipment Capability Reporting Method

Abstract

Various aspects of this invention propose a solution to the mobility interruption problem during handover between base stations by providing a mechanism for the UE to report its DAPS-HO (Dual-Active Protocol Stack Handover) capability. The UE reports its DAPS-HO capability to the network, and then the base station initiates a physical layer procedure to execute the DAPS-HO based on the reported DAPS-HO capability. Various aspects of this invention also provide examples of signaling that the UE can use to report its DAPS-HO capability to the network, and physical layer procedures that the UE can follow based on the configuration provided to it by the network, wherein such configuration should be consistent with the UE's capability.

Description

[0001] This application claims priority to U.S. Provisional Patent Application No. 62 / 910,176, filed October 3, 2019, entitled “METHODS FOR USER EQUIPMENT CAPABILITY REPORTING OF SIMULTANEOUS CONNECTIVITY HANDOVER”, and U.S. Patent Application No. 17 / 034,417, filed September 28, 2020, entitled “METHODS FOR USER EQUIPMENT CAPABILITY REPORTING OF SIMULTANEOUS CONNECTIVITY HANDOVER”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This invention generally relates to wireless communication, and in a particular embodiment, to the reporting of user equipment capabilities for simultaneous connection switching. Background Technology

[0003] In some wireless communication systems, user equipment (UE) communicates wirelessly with a base station to send data to and / or receive data from the base station. Wireless communication from the UE to the base station is called uplink (UL) communication. Wireless communication from the base station to the UE is called downlink (DL) communication.

[0004] Performing uplink, downlink, and sidelink communications requires resources. For example, a base station can wirelessly transmit data to a UE in a downlink transmission, such as a transport block (TB), at a specific frequency and for a specific duration. The frequency and duration used are examples of resources.

[0005] Base stations have specific coverage areas. The location of base stations allows coverage areas to overlap, thus covering a larger area. When a UE moves from a location served by a first base station to a second location served by a second base station, the UE needs to hand over from the first base station to the second base station. In traditional 3G and 4G networks, the UE may experience a mobility interruption during handover. When operating in these traditional networks, the UE releases the link with the source base station and then establishes a new link with the target base station.

[0006] These traditional networks support "build-before-disconnect" handover, which involves establishing a connection with the target cell and then releasing the source cell. However, in this scenario, the Mobile Broadband Handover (MBB-HO) scheme is left to the UE to implement.

[0007] Next-generation wireless networks such as 5G New Radio (NR) are expected to support UEs in simultaneously receiving transmissions from both the source and target cells during handover. This means that during handover, the UE is connected to both the source and target base stations at the same time.

[0008] Specifically, the next-generation network is expected to support independent UE capabilities for Dual Active Protocol Stack (DAPS-HO) handover and independent UE capabilities for NR Dual Connectivity / Carrier Aggregation (NR-DC / CA), as well as a scheme to reduce handover interruptions for Dual Active Protocol Stack (DAPS).

[0009] Therefore, improving the DAPS-HO mechanism will benefit communication systems. Summary of the Invention

[0010] According to one aspect of the present invention, a method is provided. The method includes: a UE selecting DAPS-HO UE capability information to be provided to a network, wherein the capability information indicates the functions supported by the UE during handover from a source cell to a target cell; the UE sending the selected DAPS-HO capability information to the network; and the UE receiving a DAPS-HO command from the network, wherein the DAPS-HO command is used to execute DAPS-HO.

[0011] In some embodiments, sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

[0012] In some embodiments, the selectable DAPS-HO UE capability information includes one or more of the following parameters: simultaneous reception of the Physical Downlink Control Channel (PDCCH) of the source cell and the target cell; simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) of the source cell and the target cell; multiplexing timing advance; band identifier (bandId); time division multiplexing (TDM) map of PDCCH; TDM map of PDSCH; TDM map of PUCCH; TDM map of PUSCH; maximum number of candidate target cells; or uplink power sharing between the source cell and the target cell.

[0013] In some embodiments, sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the frequency band combination list parameters.

[0014] In some embodiments, at least one of the one or more parameters includes additional parameters that further define how the at least one parameter is supported.

[0015] In some embodiments, sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the DAPS-HO list parameters.

[0016] In some embodiments, at least one of the one or more parameters includes additional parameters that further define how the at least one parameter is supported.

[0017] In some embodiments, sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the function set parameters.

[0018] In some embodiments, at least one of the one or more parameters includes additional parameters that further define how the at least one parameter is supported.

[0019] According to one aspect of the present invention, a method is provided. The method includes: a network receiving DAPS-HO UE capability information from a UE, wherein the capability information indicates the functions supported by the UE during handover from a source cell to a target cell; the network sending a DAPS-HO command to the UE, wherein the DAPS-HO command is used to perform DAPS-HO.

[0020] In some embodiments, receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

[0021] In some embodiments, the DAPS-HO UE capability information includes one or more of the following parameters: simultaneous reception of PDCCH of the source cell and the target cell; simultaneous reception of PDSCH of the source cell and the target cell; simultaneous transmission of Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; simultaneous transmission of Physical Uplink Shared Channel (PUSCH) of the source cell and the target cell; bandId; multiplexing timing advance frequency; TDM spectrum of PDCCH; TDM spectrum of PDSCH; TDM spectrum of PUCCH; TDM spectrum of PUSCH; maximum number of candidate target cells; or uplink power sharing between the source cell and the target cell.

[0022] In some embodiments, receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of frequency band combination list parameters.

[0023] In some embodiments, at least one of the one or more parameters includes additional parameters that further define how the at least one parameter is supported.

[0024] In some embodiments, receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the DAPS-HO list parameters.

[0025] In some embodiments, at least one of the one or more parameters includes additional parameters that further define how the at least one parameter is supported.

[0026] In some embodiments, receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the function set parameters.

[0027] In some embodiments, at least one of the one or more parameters includes additional parameters that further define how the at least one parameter is supported.

[0028] According to one aspect of the present invention, a method is provided. The method includes: a UE using a priority rule to determine when the UE can release a processing task related to a handover from a source cell to a target cell, wherein the priority rule is based on DAPS-HO UE capability information previously provided by the UE to the network; and the UE releasing the processing task when the processing task exceeds the UE's capability.

[0029] According to one aspect of the present invention, an apparatus is provided. The apparatus includes: a processor; and a computer-readable medium having processor-executable instructions stored in the computer-readable medium. When executed, the processor-executable instructions cause the apparatus to: select DAPS-HO device capability information to be provided to a network, wherein the capability information indicates functions supported by the device during handover from a source cell to a target cell; send the selected DAPS-HO capability information to the network; and receive a DAPS-HO command from the network, wherein the DAPS-HO command is used to perform DAPS-HO.

[0030] In some embodiments, when the processor-executable instruction that causes the device to send selected DAPS-HO capability information is executed, the device sends the selected DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

[0031] In some embodiments, the selectable DAPS-HO UE capability information includes one or more of the following parameters: simultaneous reception of the Physical Downlink Control Channel (PDCCH) of the source cell and the target cell; simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) of the source cell and the target cell; multiplexing timing advance; band identifier (bandId); time division multiplexing (TDM) map of PDCCH; TDM map of PDSCH; TDM map of PUCCH; TDM map of PUSCH; maximum number of candidate target cells; or uplink power sharing between the source cell and the target cell.

[0032] In some embodiments, when the processor-executable instruction that causes the device to send the selected DAPS-HO capability information is executed, the device sends the selected DAPS-HO capability information as a subset of the frequency band combination list parameters.

[0033] According to one aspect of the present invention, an apparatus is provided. The apparatus includes: a processor; and a computer-readable medium having processor-executable instructions stored in the computer-readable medium. When executed, the processor-executable instructions cause the apparatus to: receive Dual Activation Protocol Stack Handover (DAPS-HO) UE capability information from a UE, wherein the capability information indicates the functions supported by the UE during handover from a source cell to a target cell; and send a DAPS-HO command to the UE, wherein the DAPS-HO command is used to execute DAPS-HO.

[0034] In some embodiments, when the processor-executable instruction that causes the device to receive DAPS-HO capability information is executed, the device receives the DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

[0035] In some embodiments, the DAPS-HO UE capability information includes one or more of the following parameters: simultaneous reception of the Physical Downlink Control Channel (PDCCH) of the source cell and the target cell; simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) of the source cell and the target cell; multiplexing timing advance; band identifier (bandId); time division multiplexing (TDM) map of PDCCH; TDM map of PDSCH; TDM map of PUCCH; TDM map of PUSCH; maximum number of candidate target cells; or uplink power sharing between the source cell and the target cell.

[0036] In some embodiments, when the processor-executable instruction that causes the device to receive DAPS-HO capability information is executed, the device receives the DAPS-HO capability information as a subset of the frequency band combination list parameters. Attached Figure Description

[0037] To gain a more comprehensive understanding of the embodiments of the present invention and their advantages, the following description is provided with reference to examples and the accompanying drawings.

[0038] Figure 1 This is a schematic diagram of a communication system that can be implemented in an embodiment of the present invention.

[0039] Figure 2A and Figure 2B Block diagrams of an exemplary UE and a base station, respectively.

[0040] Figure 3A The diagram illustrates the hierarchical structure of information in a UE New Radio (NR) capability message, which is sent by the UE to the network to indicate the capabilities supported by the UE.

[0041] Figure 3B An example of a field that may be included in the RF parameters section of a UE NR capability message according to NR version 15 is shown.

[0042] Figure 4A The hierarchical structure of information in a UE NR capability message provided in the first embodiment of the present invention is shown. This capability message is sent by the UE to the network to indicate the capabilities supported by the UE.

[0043] Figure 4B An example of a field that may be included in the RF parameter section of a UE NR capability message, provided by a first embodiment of the present invention, is shown.

[0044] Figure 5A It shows Figure 4AThe illustration shows another detailed hierarchical structure of information in the UE NR capability message provided by the first embodiment of the present invention, which is sent by the UE to the network to indicate the capabilities supported by the UE.

[0045] Figure 5B An example of a field that may be included in a new section of the RF parameter section of a UE NR capability message, as provided in the first embodiment of the present invention, is shown.

[0046] Figure 5C An example is shown provided by the first embodiment of the present invention, which may include fields in the PDCCH field simultaneously received in the RF parameter portion of the UE NR capability message.

[0047] Figure 5D An example of a field in a time-division multiplexing graph that may be included in the PUCCH field of the RF parameter section of a UE NR capability message, as provided in the first embodiment of the present invention, is shown.

[0048] Figure 6A The hierarchical structure of information in a UE NR capability message provided by the second embodiment of the present invention is shown. This capability message is sent by the UE to the network to indicate the capabilities supported by the UE.

[0049] Figure 6B An example of a field that may be included in a new section of the RF parameter section of a UE NR capability message, as provided in a second embodiment of the present invention, is shown.

[0050] Figure 7A The hierarchical structure of information in a UE NR capability message provided in the third embodiment of the present invention is shown. This capability message is sent by the UE to the network to indicate the capabilities supported by the UE.

[0051] Figure 7B An example of a field that may be included in a new section of the RF parameter section of a UE NR capability message, as provided in a third embodiment of the present invention, is shown.

[0052] Figure 8 An example is shown of using a timer to determine the duration of monitoring the PDCCH or source and target cells.

[0053] Figure 9A The signal flow diagram is provided as a first example of simultaneous handover of a UE from a source cell to a target cell in an embodiment of the present invention.

[0054] Figure 9B This is a signal flow diagram of a second example of simultaneous handover involving timers for a UE from a source cell to a target cell, according to an embodiment of the present invention. Detailed Implementation

[0055] For illustrative purposes, specific exemplary embodiments are explained in more detail below with reference to the accompanying drawings.

[0056] The embodiments presented herein illustrate information sufficient to practice the claimed subject matter and describe methods for practicing such subject matter. Those skilled in the art will understand the concepts of the claimed subject matter after reading the following description with reference to the accompanying drawings, and will recognize that the application of these concepts is not specifically mentioned herein. It should be understood that these concepts and applications are within the scope of this invention and the appended claims.

[0057] Furthermore, it should be understood that any module, component, or device with executable instructions disclosed herein may include or otherwise access one or more non-transitory computer / processor-readable storage media for storing information, such as computer / processor-readable instructions, data structures, program modules, and / or other data. A non-exhaustive list of examples of non-transitory computer / processor-readable storage media includes magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices, read-only optical discs (CD-ROMs), digital video optical discs or digital versatile optical discs (i.e., DVDs), Blu-ray™ and other optical discs, or other optical storage devices; volatile and non-volatile, removable and non-removable media implemented in any method or technology; random access memory (RAM); read-only memory (ROM); electrically erasable programmable read-only memory (EEPROM); flash memory or other storage technologies. Any of these non-transitory computer / processor-readable storage media may be part of a device or may be accessed or connected to a device. Computer / processor-readable / executable instructions used to implement the applications or modules described herein may be stored or otherwise preserved by such non-transitory computer / processor-readable storage media.

[0058] Various aspects of this invention propose a solution to the mobility interruption problem during handover between base stations by providing a mechanism for the UE to report its DAPS-HO (Dual-Active Protocol Stack Handover) capability. The UE reports its DAPS-HO capability to the network, and then the base station initiates a physical layer procedure to execute the DAPS-HO based on the reported DAPS-HO capability. Various aspects of this invention provide examples of signaling that the UE can use to report its DAPS-HO capability to the network, as well as physical layer procedures that the UE can follow based on the configuration provided to it by the network, wherein such configuration should be consistent with the UE's capability.

[0059] The following Figure 1 , Figure 2A and Figure 2B A context is provided for networks and devices (which may be in a network and can implement various aspects of the invention).

[0060] Figure 1An exemplary communication system 100, in which embodiments of the present invention can be implemented, is illustrated. Generally, system 100 enables multiple wireless elements or multiple wired elements to transmit data and other content. The purpose of system 100 may be to provide content (voice, data, video, text) via broadcast, narrowcast, user equipment to user equipment, etc. System 100 can operate efficiently by sharing resources such as bandwidth.

[0061] In this example, the communication system 100 includes electronic devices (EDs) 110a to 110c, radio access networks (RANs) 120a and 120b, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. Although Figure 1 A certain number of these components or elements are shown, but system 100 may include any suitable number of these components or elements.

[0062] EDs 110a to 110c are used for operation and / or communication within system 100. For example, EDs 110a to 110c are used for transmitting and / or receiving via a wireless communication channel. EDs 110a to 110c represent any end-user equipment suitable for wireless operation and may include (or be referred to as) devices such as: user equipment (UE / user device), wireless transmit / receive unit (WTRU), mobile station, mobile subscriber unit, cellular telephone, site (STA), machine-type communication (MTC) equipment, personal digital assistant (PDA), smartphone, laptop computer, computer, touchpad, wireless sensor, or consumer electronic device.

[0063] Figure 1 An exemplary communication system 100, in which embodiments of the present invention can be implemented, is shown. Generally, the communication system 100 enables multiple wireless or wired components to transmit data and other content. The purpose of the communication system 100 may be to provide content (voice, data, video, text) via broadcast, multicast, unicast, user equipment to user equipment, etc. The communication system 100 can operate by sharing resources such as bandwidth.

[0064] In this example, the communication system 100 includes electronic devices (EDs) 110a to 110c, radio access networks (RANs) 120a and 120b, a core network 130, a public switched telephone network (PSTN) 140, the Internet 150, and other networks 160. Although Figure 1 A certain number of these components or elements are shown, but the communication system 100 may include any suitable number of these components or elements.

[0065] EDs 110a to 110c are used for operation and / or communication in communication system 100. For example, EDs 110a to 110c are used for transmitting and / or receiving via a wireless communication channel or a wired communication channel. EDs 110a to 110c represent any end-user equipment suitable for wireless operation and may include (or be referred to as) devices such as: user equipment (UE / userdevice), wireless transmit / receive unit (WTRU), mobile station, fixed or mobile subscriber unit, cellular telephone, station (STA), machine-type communication (MTC) equipment, personal digital assistant (PDA), smartphone, laptop computer, computer, tablet computer, wireless sensor, or consumer electronic device.

[0066] Figure 1 RAN 120a and 120b in the diagram include base stations 170a and 170b, respectively. Base stations 170a and 170b are used to establish wireless connections with one or more of EDs 110a to 110c to enable access to any other base stations 170a and 170b, core network 130, PSTN 140, Internet 150, and / or other networks 160. For example, base stations 170a and 170b may include (or may be) one or more of several well-known devices, such as base transceiver stations (BTS), Node-Bs (NodeBs), evolved NodeBs (eNodeBs), femtocells, gNodeBs, transmit / receive points (TRPs), site controllers, access points (APs), or wireless routers. Any ED 110a to 110c may optionally or additionally be used to connect to, access, or communicate with any other base stations 170a and 170b, Internet 150, core network 130, PSTN 140, other networks 160, or any combination thereof. The communication system 100 may include a RAN, such as RAN 120b, wherein the corresponding base station 170b is directly or as shown in the figure connected to the core network 130 via the Internet 150.

[0067] EDs 110a to 110c, as well as base stations 170a and 170b, are examples of communication devices that can be used to implement some or all of the functions and / or embodiments described herein. Figure 1In the illustrated embodiment, base station 170a is part of RAN 120a, which may include other base stations, one or more base station controllers (BSCs), one or more radio network controllers (RNCs), relay nodes, components, and / or devices. Any base station 170a and 170b may be a single component as shown, or multiple components distributed within the corresponding RAN, etc. Similarly, base station 170b is part of RAN 120b, which may include other base stations, components, and / or devices. Both base stations 170a and 170b transmit and / or receive radio signals within a geographic area (sometimes referred to as a "cell" or "coverage area"). A cell may be further divided into cell sectors, and base stations 170a and 170b may use multiple transceivers to provide services to multiple sectors, etc. In some embodiments, there may be established picocells or femtocells supported by radio access technologies. In some embodiments, multiple transceivers may use multiple-input multiple-output (MIMO) technology, etc., for each cell. The number of RANs 120a and 120b shown is merely exemplary. When designing a communication system 100, any number of RANs can be envisioned.

[0068] Base stations 170a and 170b use radio frequency (RF), microwave, infrared (IR), or other wireless communication links to communicate with one or more of ED 110a to 110c via one or more air interfaces 190. Air interface 190 can use any suitable wireless access technology. For example, communication system 100 can implement one or more orthogonal or non-orthogonal channel access methods in air interface 190, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Single Carrier FDMA (SC-FDMA).

[0069] In this invention, UL and DL transmissions between the UE and the base station can be "unlicensed" transmissions, or data transmission modes performed without dynamic scheduling communication. Unlicensed transmissions are sometimes referred to as "configured licensed" transmissions, "unlicensed" transmissions, "unscheduling-free" transmissions, or "unscheduling-free" transmissions. Unlicensed SL transmissions can also be referred to as SL "unlicensed transmissions," "no dynamic licensed transmissions," "no dynamic scheduling transmissions," or "configured licensed transmissions," and so on.

[0070] Base stations 170a and 170b can implement Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA) to establish an air interface 190 using Wideband CDMA (WCDMA). In this case, base stations 170a and 170b can implement protocols such as High-Speed ​​Packet Access (HSPA), Evolved HPSA (HSPA+), where HSPA+ optionally includes High-Speed ​​Downlink Packet Access (HSDPA) and / or High-Speed ​​Uplink Packet Access (HSUPA). Optionally, base stations 170a and 170b can use LTE, LTE-A, and / or LTE-B to establish an air interface 190 with Evolved UTTS Terrestrial Radio Access (E-UTRA). It is conceivable that communication system 100 can use multi-channel access capabilities, including those schemes described above. Other wireless technologies used for air interface implementation include IEEE 802.11, 802.15, 802.16, CDMA2000, CDMA2000 1X, CDMA2000 EV-DO, IS-2000, IS-95, IS-856, GSM, EDGE, and GERAN. Of course, other multiple access schemes and wireless protocols can also be used.

[0071] RANs 120a and 120b communicate with core network 130 to provide various services, such as voice, data, and other services, to EDs 110a through 110c. RANs 120a and 120b and / or core network 130 may communicate directly or indirectly with one or more other RANs (not shown), which may or may not be directly served by core network 130 and may or may not use the same radio access technology as RANs 120a and / or RAN 120b. Core network 130 may also serve as a gateway access between (i) RANs 120a and 120b and / or EDs 110a through 110c, and (ii) other networks (e.g., PSTN 140, Internet 150, and other networks 160).

[0072] EDs 110a to 110c communicate with each other via one or more sidelink (SL) air interfaces 180 using radio frequency (RF), microwave, infrared (IR), or other wireless communication links. The SL air interface 180 can use any suitable wireless access technology. The SL air interface 180 can be substantially similar to, or substantially different from, the air interface 190 through which EDs 110a to 110c communicate with one or more base stations 170a to 170b. For example, the communication system 100 can implement one or more channel access methods, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Single Carrier FDMA (SC-FDMA), in the SL air interface 180. In some embodiments, the SL air interface 180 can be implemented at least partially on unlicensed spectrum.

[0073] In this invention, SL transmission between cooperating UEs can be "unlicensed" transmission, or a mode of data transmission performed without dynamic scheduling communication. Unlicensed transmission is sometimes referred to as "configured licensed" transmission, "unlicensed" transmission, "unscheduling-free" transmission, or "no-scheduling" transmission. Unlicensed SL transmission can also be referred to as SL "unlicensed transmission," "no dynamic licensed transmission," "no dynamic scheduling transmission," or "configured licensed transmission," etc.

[0074] Additionally, some or all of EDs 110a to 110c may include the ability to communicate with different wireless networks via different wireless links using different wireless technologies and / or protocols. The ED may communicate with a service provider or exchange (not shown) via a wired communication channel and with the Internet 150, rather than wirelessly (or otherwise wirelessly). PSTN 140 may include a circuit-switched telephone network for providing traditional telephone service (POTS). The Internet 150 may include a computer network and / or subnet (internal network) and include protocols such as Internet Protocol (IP), Transmission Control Protocol (TCP), and User Datagram Protocol (UDP). EDs 110a to 110c may be multimode devices capable of operating according to multiple wireless access technologies and include multiple transceivers required to support multiple wireless access technologies.

[0075] Figure 2A and Figure 2B Exemplary devices are shown that can implement the various methods and teachings provided by this invention. Specifically, Figure 2A An example ED 110 is shown. Figure 2B An exemplary base station 170 is shown. These components can be used in system 100 or any other suitable system.

[0076] like Figure 2AAs shown, ED 110 includes at least one processing unit 200. The processing unit 200 implements various processing operations of ED 110. For example, the processing unit 200 may perform signal encoding, data processing, power control, input / output processing, or any other function that enables ED 110 to operate within communication system 100. The processing unit 200 may also be used to implement some or all of the functions and / or embodiments detailed herein. Each processing unit 200 includes any suitable processing or computing device for performing one or more operations. Each processing unit 200 may include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit, etc.

[0077] ED 110 also includes at least one transceiver 202. Transceiver 202 is used to modulate data or other content for transmission via at least one antenna or network interface controller (NIC) 204. Transceiver 202 is also used to demodulate data or other content received via at least one antenna 204. Each transceiver 202 includes any suitable structure for generating signals for wireless or wired transmission and / or for processing signals received wirelessly or wiredly. Each antenna 204 includes any suitable structure for transmitting and / or receiving wireless or wired signals. One or more transceivers 202 may be used in ED 110. One or more antennas 204 may be used in ED 110. Although transceiver 202 is shown as a separate functional unit, transceiver 202 may also be implemented using at least one transmitter and at least one separate receiver.

[0078] ED 110 also includes one or more input / output devices 206 or interfaces (e.g., wired interfaces connected to the Internet 150). Input / output devices 206 can interact with users or other devices on the network. Each input / output device 206 includes any suitable structure for providing or receiving information from a user, such as a speaker, microphone, keypad, keyboard, display, or touchscreen, including network interface communication.

[0079] Additionally, ED 110 includes at least one memory 208. Memory 208 stores instructions and data used, generated, or collected by ED 110. For example, memory 208 may store software instructions or modules for implementing some or all of the functions and / or embodiments described above and executed by one or more processing units 200. Each memory 208 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices. Any suitable type of memory can be used, such as random access memory (RAM), read-only memory (ROM), hard disk, optical disk, user identification module (SIM) card, memory stick, secure digital storage (SD) card, etc.

[0080] like Figure 2B As shown, base station 170 includes at least one processing unit 250, at least one transmitter 252, at least one receiver 254, one or more antennas 256, at least one memory 258, and one or more input / output devices or interfaces 266. Transmitters 252 and receivers 254 (not shown) may be used in place of transceivers. Scheduler 253 may be coupled to processing unit 250. Scheduler 253 may be included within base station 170 or may operate separately from base station 170. Processing unit 250 implements various processing operations of base station 170, such as signal encoding, data processing, power control, input / output processing, or any other functions. Processing unit 250 may also be used to implement some or all of the functions and / or embodiments detailed above. Each processing unit 250 includes any suitable processing or computing device for performing one or more operations. Each processing unit 250 may include a microprocessor, microcontroller, digital signal processor, field-programmable gate array, or application-specific integrated circuit, etc.

[0081] Each transmitter 252 includes any suitable structure for generating signals to be transmitted wirelessly or wired to one or more EDs or other devices. Each receiver 254 includes any suitable structure for processing signals received wirelessly or wired from one or more EDs or other devices. Although at least one transmitter 252 and at least one receiver 254 are shown as separate components, they can be combined into a transceiver. Each antenna 256 includes any suitable structure for transmitting and / or receiving wireless or wired signals. Although a shared antenna 256 is shown coupled to both transmitter 252 and receiver 254, one or more antennas 256 can be coupled to one or more transmitters 252, and one or more individual antennas 256 can be coupled to one or more receivers 254. Each memory 258 includes any suitable one or more volatile and / or non-volatile storage and retrieval devices, such as those described above in conjunction with ED 110. Memory 258 stores instructions and data used, generated, or collected by base station 170. For example, memory 258 may store software instructions or modules for implementing some or all of the functions and / or embodiments described above and executed by one or more processing units 250.

[0082] Each input / output device 266 can interact with users or other devices in the network. Each input / output device 266 includes any suitable structure for providing information to or receiving / providing information from users, including network interface communication.

[0083] Further details regarding UE 110 and base station 170 are known to those skilled in the art. Therefore, for clarity, these details are omitted herein.

[0084] In NR Release 15 (R15), the UE reports the capabilities it supports. Figure 3A The hierarchy 300 of the contents in the UE NR Capability message is shown. Figure 3A The hierarchical structure illustrated in the following figures using level 1, 2, 3, etc., is merely for ease of understanding of the information included in the capability message, and it should be understood that explicit level labels may not be included in this parameter information. Level 1 310 is the capability message that includes all capability information. Level 2 320 includes parameters for different layers, such as Media Access Control (MAC) parameters, Physical Layer (PHY) parameters, and Radio Frequency (RF) parameters. In some embodiments, the UE's DAPS-HO capability information is included in the RF parameter section of the UE NR capability message. Capability information can be transmitted from the UE to the network via the source cell using higher-layer signaling. An example of such higher-layer signaling could be Radio Resource Control (RRC) signaling.

[0085] Figure 3B An example of information 330 is shown. Information 330 can be included in various fields of a capability message sent from the UE to the network and is located in... Figure 3A In the RF parameter section of the hierarchical structure shown, the UE reports a list of supported carrier aggregation / dual carrier (CA / DC) bands. Specifically, the UE transmits information from the BandCombinationList 340 field and the corresponding BandCombinationList-v15xx 350 field. Figure 3B This includes the fields BandCombinationList-v1540, BandCombinationList-v1550, and BandCombinationList-v1560. Each band combination is associated with a set of DL / UL functions 360, which in turn is associated with FeatureSetCombinationId 370.

[0086] Figure 9AThis is an exemplary signaling flow diagram of signaling (part of DAPS-HO) occurring between UE 910 and source cell 904, and between UE 910 and target cell 907. Source cell 904 and target cell 907 are part of the network in which UE 910 communicates. Processes performed by the network (e.g., generating DAPS-HO commands based on UE capability information provided by UE 910) may be concentrated in or near target cell 907 or source cell 904, or elsewhere in the network. At some point before a possible handover from source cell 904 to target cell 907, UE 910 sends a higher-level signaling message 920 including UE-NR-Capability information. This information may include capability information about many capabilities supported by the UE, some of which are related to DAPS-HO capabilities, or the capability information sent to the network at a given time may only relate to the DAPS-HO capabilities supported by the UE. An example of higher-level signaling could be Radio Resource Control (RRC) signaling. At a certain point after the source cell 904 receives the UE capability information, the network generates a DAPS-HO command, and the source cell 904 sends the 930 DAPS-HO command to the UE 910. In step 940, the source cell 904 and the target cell 907 send PDDCH messages. In step 950, the UE 910 monitors the PDDCH messages sent by the source cell 904 and the target cell 907 in step 940. Once the network determines that the handover has been completed, the target cell 907 sends the 960 higher-layer signaling to the UE 910 to release the source cell 904. The higher-layer signaling can be RRC signaling.

[0087] The embodiments described below illustrate three different formats in which a UE can send capability information to the network and how the UE operates when it receives a DAPS-HO command from the network in response to the capability information.

[0088] In one embodiment, the UE sends capability information to the network in a format that includes all frequency band combinations supported by the UE; this capability information may also be referred to as a capability report. For each supported frequency band combination, the UE includes a DAPS-HO capability parameter. In this embodiment, for each CA / DC frequency band combination, the UE indicates the DAPS-HO capability in the "DAPSHandover" parameter of each frequency band combination entry.

[0089] Figure 4A The hierarchy of information in the UE NR Capability message (UE-NR-Capability) is shown 400. Descriptions of levels 1 and 2 are referenced. Figure 3ALevel 3 includes RF parameter information, indicating the frequency bands supported by the UE in the supportedBandListNR 405, the supported frequency band combinations in the supportedBandCombinationList 410, and the applied frequency band list filter 415. An additional frequency band combination list, identified as supportedBandCombinationLists-v16xx 420, exists, representing additional capability parameters that can be added, including the capability parameters described in this invention. However, it should be understood that this representation is merely for ease of understanding, and the parameter supportedBandCombinationLists-v16xx may not be specifically named. The parameter dapsHandover 425 in Level 4 is shown to be included in the parameter supportedBandCombinationLists-v16xx.

[0090] After the UE initially accesses the network, the UE sends a capability message to the network. Figure 4B An example of information 430 is shown. Information 430 can be included in the UE's capability message and is located in... Figure 4A The RF parameter section of the hierarchical structure shown.

[0091] Much of the content of Info 430 is similar to Figure 3A The content of information 330 is shown in the diagram. However, information 430 contains additional new content not present in information 330, which is unique to various aspects of this invention. The field BandCombinationLists-v16xx 435 is added after the field BandCombinationList-v1560. The parameter field dapsHandover 440 is shown at the end of the content of information 430. An example of the parameters in the parameter field dapsHandover 440 is described below.

[0092] Figure 5A This shows the hierarchical structure of the contents in the UE-NR-Capability message (UE-NR-Capability) 500. Descriptions of levels 1, 2, 3, and 4 are referenced. Figure 3A and Figure 4A Level 5 510 includes a parameter list 510, which can be included in the parameter field dapsHandover 440.

[0093] The parameter list 510 in the `intraFreqDapsHandover` parameter includes, but is not limited to, the following parameters: `simultaneousRxPDCCH`, `simultaneousRxPDSCH`, `simultaneousTxPUCCH`, `simultaneousTxPUSCH`, `maxNumCandidateTargetCells`, `multipleTimingAdvance`, `tdm-Pattern-PDCCH`, `tdm-Pattern-PDSCH`, `tdm-Pattern-PUCCH`, `tdm-Pattern-PUSCH`, `ulPowerSharing`, and `bandID`. All parameters or subsets of parameters shown may be indicated by a UE that supports in-frequency DAPS-HO at a given time. In-frequency DAPS-HO refers to the UE using in-frequency measurements to identify handover to the target cell. In-frequency measurements are defined as measurements where the SS / PBCH blocks of the source and target cells occupy the same center frequency and use the same subcarrier spacing. Correspondingly, inter-frequency DAPS-HO refers to the UE using inter-frequency measurements to identify handover to the target cell. Inter-frequency measurements are measurements other than in-frequency measurements. It is also assumed that when the source and target cells are both located in the same frequency band, a co-frequency DAPS-HO operation is performed. Other parameters not listed in this example may also exist and can be included (if they exist).

[0094] The parameter `simultaneousRxPDCCH` indicates whether the UE supports receiving PDCCH from both the source and target base stations during handover. The parameter `simultaneousRxPDSCH` indicates whether the UE supports receiving PDSCH from both the source and target base stations during handover. The parameter `simultaneousTxPUCCH` indicates whether the UE supports sending PUCCH to both the source and target base stations during handover. The parameter `simultaneousTxPUSCH` indicates whether the UE supports sending PUSCH to both the source and target base stations during handover. The parameter `maxNumCandidateTargetCells` indicates the number of candidate target cells the UE may involve when determining the final target cell (as part of DAPS-HO). The parameter `multipleTimingAdvance` indicates whether multiple timing advance is supported for both the source and target base stations during handover. The parameter `tdm-Pattern-PDCCH` indicates whether time division multiplexing (TDM) patterns of PDCCH are supported during handover. The parameter `tdm-Pattern-PDSCH` indicates whether TDM patterns of PDSCH are supported during handover. The parameter tdm-Pattern-PUCCH indicates whether TDM patterns for PUCCH are supported during handover. The parameter tdm-Pattern-PUSCH indicates whether TDM patterns for PUSCH are supported during handover. The parameter ulPowerSharing indicates whether dynamic and / or semi-static UL power sharing is supported during handover. The parameter bandID provides an identifier for one or more frequency bands involved in the handover.

[0095] Figure 5B An example of information 530 is shown. Information 530 may optionally be included in the UE's capability message and located in... Figure 5A The RF parameters section of the hierarchical structure is shown. Each listed parameter can be used to indicate whether a specific function is supported. Taking a single bit as an example, "1" indicates support, and "0" indicates no support.

[0096] After receiving the UE capability information sent by the UE, the network sends a same-frequency DAPS-HO command to the UE. The DAPS-HO command sent by the network provides the target cell configuration to the UE, enabling the UE to establish a connection with the target cell. The signaling information used to configure the connection with the target cell is based on one or more capability parameters reported by the UE to the network.

[0097] If the UE indicates support for simultaneousRxPDCCH, then upon receiving a co-frequency DAPS-HO command from the network, the UE monitors PDCCH candidates for both the target cell and the source cell within the same transport resource (e.g., within the same time slot). The PDCCH candidates monitored by the UE for the target cell reside on the control resource set (CORESET) and search space set indicated by the network in the DAPS-HO command. The CORESET is a set of physical resources and parameters used to carry the PDCCH, which may include downlink control information (DCI). The search space set provides an indication of the existence of search space regions within the downlink resources that can carry the PDCCH.

[0098] Figure 5C An example of information 540 is shown. Information 540 may optionally be included in the UE's capability message and as... Figure 5B The parameter field `simultanousRxPDCCH` is shown as a portion of the parameter field. The `simultanousRxPDCCH` parameter field includes the maximum number of CORESETs on the PDCCH (which can be 6, 9, or 12), the maximum number of PDCCH candidates monitored in the source and / or target cells (which can be 10, 11, 18, or 22), and the maximum number of overlapping control channel elements (CCEs) (which can be 16, 24, or 28). Various parameters are identified, showing that these parameters are optional. When using parameters, these parameters can be enumerated to represent appropriate values, such as the exemplary values ​​included above.

[0099] If the UE indicates support for simultaneous TxPUCCH, then upon receiving a co-frequency DAPS-HO command from the network, the UE transmits PUCCH to both the target cell and the source cell within the same transport resource (e.g., within the same time slot). PUCCH transmissions are performed on the PUCCH resource group based on the corresponding beam assumption indicated by the network in the co-frequency DAPS-HO command.

[0100] If the UE indicates support for multipleTimingAdvance, when receiving the same-frequency DAPS-HO command from the network, the UE sends a random access channel (RACH) preamble to the target cell, obtains the timing advance of the target cell, and simultaneously maintains the timing advance values ​​of multiple cells (i.e., the target cell and the source cell).

[0101] If the UE indicates support for tdm-Pattern-PDCCH, then when receiving the same-frequency DAPS-HO command from the network, the UE expects to configure the source cell and target cell configurations so that the DL / UL process is performed within orthogonal time slots. This means that the UE monitors a cell's PDCCH candidates within a certain time slot.

[0102] If the UE indicates support for tdm-pattern-PDSCH, then when receiving the same-frequency DAPS-HO command from the network, the UE expects to configure the source cell and target cell configurations so that the DL / UL process occurs within orthogonal time slots. This means that the UE receives PDSCH transmissions from one cell within a certain time slot.

[0103] If the UE indicates support for tdm-pattern-PUCCH, then when receiving the same-frequency DAPS-HO command from the network, the UE expects to configure the source cell and target cell configurations so that the DL / UL process is performed within orthogonal time slots. This means that the UE sends a PUCCH transmission carrying a hybrid automatic repeat request / channel state information / scheduling request (HARQ-ACK / CSI / SR) to a cell within a certain time slot.

[0104] If the UE indicates support for tdm-pattern-PUSCH, then when receiving the same-frequency DAPS-HO command from the network, the UE expects to configure the source cell and target cell configurations so that the DL / UL process occurs within orthogonal time slots. This means that the UE sends a PUSCH transmission to a cell within a certain time slot.

[0105] The TDM map in any of the above cases can be based on one or more attributes, such as UE identifier, time-domain time slot, quasi-co-address (QCL) assumption, frequency-domain resources, code sequence, and antenna port.

[0106] Figure 5D An example of information 550 is shown. Information 550 may optionally be included in the UE's capability message and serve as... Figure 5B The parameter field tdm-Pattern-PUCCH is shown as a portion of the parameter field. For the source cell and / or target cell, the parameter field tdm-Pattern-PUCCH includes an indication of supported PUCCH periodicity and whether PUCCH frequency hopping is supported. Various parameters are identified, and these parameters are shown as optional. When using parameters, these parameters can be listed to represent appropriate values ​​for PUCCH periodicity or simply to indicate whether the function is supported in the case of PUCCH frequency hopping.

[0107] If the UE indicates that it supports ulPowerSharing for a certain type of value (semi-static or dynamic), then when receiving the same-frequency DAPS-HO command from the network, the UE shares the UE uplink transmission power between the source cell and the target cell in a semi-static or dynamic manner (as indicated by the network), corresponding to the uplink transmission power indicated by the network in the same-frequency DAPS-HO command.

[0108] The following describes other examples of how the UE and network operate according to specific parameters indicated in the UE-NR-Capability message.

[0109] PDCCH receives simultaneously

[0110] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A If the reference numeral 425 in the attached figure is part of a frequency band with simultaneous RxPDCCH, then the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the target cell) in each time slot.

[0111] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability is identified as bandId (e.g., in... Figure 5A If a UE is selected from a portion of a frequency band (as indicated in parameter group 510), the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the target cell) in each time slot.

[0112] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability is part of a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the target cell) in each time slot.

[0113] The above embodiments can be used individually or in combination. For example, the UE indicates that the simultaneous RxPDCCH is part of a band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable when the source cell and the target cell are in the same downlink bandwidth portion (DL BWP) of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0114] PDSCH simultaneous reception

[0115] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4AIf the reference numeral 425 in the attached figure is a portion of a frequency band with simultaneous RxPDSCH, then the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled by the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0116] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability is identified as bandId (e.g., in... Figure 5A If a UE is assigned a portion of a frequency band (as indicated in parameter group 510), the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0117] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability is part of a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During the DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0118] The above embodiments can be used individually or in combination. For example, the UE indicates that simultaneousRxPDSCH is part of a band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0119] Simultaneous transmission of PUCCH

[0120] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A If the reference numeral 425 in the attached diagram is part of a frequency band with simultaneous TxPUCCH, then the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to report uplink control information (UCI) corresponding to the received PDSCH transmission scheduled through the corresponding PDCCH transmission with a certain serving cell.

[0121] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability is identified as bandId (e.g., in... Figure 5A If a UE is assigned a portion of a frequency band (as indicated in parameter group 510), the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to report the UCI corresponding to the received PDSCH transmission scheduled via the corresponding PDCCH transmission with a serving cell.

[0122] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability is part of a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During the DAPS-HO, the UE is expected to report the UCI corresponding to a received PDSCH transmission scheduled via the appropriate PDCCH transmission with a serving cell.

[0123] The above embodiments can be used individually or in combination. For example, the UE indicates that the simultaneous TxPUCCH is part of a band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0124] Simultaneous transmission of PUSCH

[0125] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A If a simultaneous TxPUSCH (as shown by reference numeral 425 in the attached diagram) has a certain frequency band, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions scheduled by the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0126] In another example, if the UE indicates the dapsHandover capability in UE-NR-Capability to the identifier marked with bandId (e.g., in... Figure 5A If a frequency band is specified in parameter group 510, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions scheduled by the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0127] In another example, if the UE indicates dapsHandover capability in UE-NR-Capability to a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0128] Number of candidate target cells for DAPS-HO

[0129] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A (As shown by reference numeral 425 in the attached figure) has maxNumCandidateTargetCells of a certain frequency band (e.g., in...) Figure 5A If the parameter group 510 indicates that the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE, then the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0130] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has a maximum of maxNumCandidateTargetCells for a certain frequency band, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0131] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells for a frequency band identified as bandId, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0132] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells for a certain frequency band identified by bandId, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0133] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells of a certain band combination identified as bandCombinationId, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0134] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells of a certain band combination identified as bandCombinationId, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0135] In the various examples above, the serving cell can be the primary cell in a cell group and can correspond to the source cell or the candidate target cell indicated in the DAPS-HO command.

[0136] PDCCH TDM spectrum

[0137] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A (As shown by reference numeral 425 in the attached figure) has a tdm-pattern-PDCCH with a certain frequency band (e.g., in Figure 5AIf the parameter group 510 indicates that the network can send a DAPS-HO command to the UE, then the network can send the command. During the DAPS-HO period, the UE is expected to monitor the PDCCH candidates of a serving cell (i.e., the source cell or the target cell) in each time unit.

[0138] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PDCCH for a specific frequency band identified as bandId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of a serving cell (i.e., the source cell or the target cell) in each time unit.

[0139] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PDCCH for a certain band combination identified as bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of a serving cell (i.e., the source cell or the target cell) in each time unit.

[0140] When the UE is used to perform DAPS-HO operations (i.e., when the UE receives the DAPS-HO command from the network), and when the UE reports the tdm-Pattern-PDCCH in UE-NR-Capability, it is not expected that the UE will be used to monitor multiple serving cell PDCCH candidates in each time unit.

[0141] PDSCH TDM spectra

[0142] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A (As shown by reference numeral 425 in the attached figure) has a tdm-pattern-PDSCH with a certain frequency band (e.g., in Figure 5A If the parameter group 510 indicates that the network can send a DAPS-HO command to the UE, then the network can send a DAPS-HO command to the UE. During the DAPS-HO period, the UE is expected to receive PDSCH transmissions scheduled by the corresponding PDCCH from a serving cell (i.e., the source cell or the target cell) in each time unit.

[0143] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PDSCH for a specific frequency band identified as bandId, the network can send a DAPS-HO command to the UE. During the DAPS-HO period, the UE is expected to receive PDSCH transmissions from a serving cell (i.e., the source cell or the target cell) scheduled via the corresponding PDCCH in each time unit.

[0144] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PDSCH for a frequency band combination identified as bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions from a serving cell (i.e., the source cell or the target cell) scheduled via the corresponding PDCCH in each time unit.

[0145] When the UE is used to perform DAPS-HO operations (i.e., when the UE receives the DAPS-HO command from the network), and when the UE reports the tdm-Pattern-PDSCH in UE-NR-Capability, it is not expected that the UE will be used to receive PDSCH transmissions of multiple serving cells in each time unit.

[0146] PUCCH's TDM spectrum

[0147] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A (As shown by reference numeral 425 in the attached figure) has a tdm-pattern-PUCCH with a certain frequency band (e.g., in Figure 5A If the parameter group 510 indicates that the network can send a DAPS-HO command to the UE, then the network can send a DAPS-HO command to the UE. During the DAPS-HO period, the UE is expected to send a PUCCH carrying the UCI of the corresponding PDSCH scheduled by the serving cell (source cell or target cell) through the PDCCH in each time unit.

[0148] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PUCCH for a certain frequency band identified as bandId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send a PUCCH carrying the UCI of the corresponding PDSCH scheduled by the serving cell (source cell or target cell) via PDCCH in each time unit.

[0149] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PUCCH with a frequency band combination identified as bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send a PUCCH carrying the UCI of the corresponding PDSCH scheduled by the serving cell (source cell or target cell) via PDCCH in each time unit.

[0150] When the UE is used to perform DAPS-HO operations (i.e., when the UE receives the DAPS-HO command from the network), and when the UE reports the tdm-Pattern-PUCCH in UE-NR-Capability, it is not expected that the UE will use to send multiple PUCCHs carrying the UCI of the corresponding PDSCH scheduled by the serving cell (source cell or target cell) through the PDCCH in each time unit.

[0151] PUSCH's TDM map

[0152] If the UE indicates dapsHandover capability in UE-NR-Capability (e.g., by...) Figure 4A (As shown by reference numeral 425 in the attached figure) has a tdm-pattern-PUSCH with a certain frequency band (e.g., in Figure 5A If the parameter group 510 indicates that the network can send a DAPS-HO command to the UE, then the network can send a DAPS-HO command to the UE. During the DAPS-HO period, the UE is expected to send a PUSCH transmission scheduled by the corresponding PDCCH for a certain serving cell (i.e., the source cell or the target cell) in each time unit.

[0153] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PUSCH for a specific frequency band identified as bandId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions for a serving cell (i.e., the source cell or the target cell) scheduled via the corresponding PDCCH in each time unit.

[0154] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has a tdm-pattern-PUSCH for a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send a PUSCH transmission for a serving cell (i.e., the source cell or the target cell) scheduled via the corresponding PDCCH in each time unit.

[0155] In the examples above, the serving cell can be the primary cell in a cell group and can correspond to the source cell or the candidate target cell indicated in the DAPS-HO command. The time unit can be any of an OFDM symbol, OFDM symbol group, mini-slot, time slot, or time slot group.

[0156] When the UE is used to perform DAPS-HO operations (i.e., when the UE receives the DAPS-HO command from the network), and when the UE reports tdm-Pattern-PUSCH in UE-NR-Capability, it is not expected that the UE will be used to send PUSCH transmissions to multiple serving cells in each time unit.

[0157] In another embodiment, the UE sends capability information or a capability report to the network in a format that includes DAPS-HO capability parameters. The DAPS-HO capability parameters include the DAPS-HO band combinations supported by the UE. In this embodiment, the DAPS-HO capability is indicated in each corresponding CA / DC band combination entry in the parameter BandCombinationList.

[0158] Figure 6A The hierarchy of information in the UE-NR-Capability message (UE-NR-Capability) is shown 600. Descriptions of levels 1 and 2 are referenced. Figure 3ALevel 3 includes RF parameter information, indicating the frequency bands supported by the UE in the supported BandList NR 610, the supported band combinations in the supported BandCombinationList 620, and the applied band list filter 630. Several parameters included in Level 4 are related to the supported BandCombinationList 620. The band combination identifier parameter 621 can be added to Level 4 as a new parameter along with the bandList 622 and featureSetCombination 623 parameters associated with the band combination list 620. An additional DAPS handover list 640 exists in Level 3, which includes the DAPS handover-specific parameter set 641 from Level 4.

[0159] Examples of DAPS switching specific parameter 641 in Level 4 include, but are not limited to: bandCombinationId, simultaneousRxPDCCH, simultaneousRxPDSCH, simultaneousTxPUCCH, simultaneousTxPUSCH, maxNumCanadidateTargetCells, multipleTimingAdvance, bandID, tdm-Pattern-PDCCH, tdm-Pattern-PDSCH, tdm-Pattern-PUCCH, tdm-Pattern-PUSCH, and ulPowerSharing.

[0160] The parameter bandCombinationId indicates the identifier of a specific frequency band combination. The remaining parameters are the same as those described in the above embodiments, but can be implemented in different ways.

[0161] Figure 6B An example of information 650 is shown. Information 650 may optionally be included in the UE's capability message and located in... Figure 6A The RF parameter section of the hierarchy is shown. Each listed parameter can be used to represent a specific parameter name, possible values ​​for the parameter, or whether a specific feature is supported. An example of a value indicating whether a feature is supported might be a single bit, such as "1" for supported and "0" for unsupported.

[0162] Most of the content in Information 650 is similar to Figure 3AThe information in information 330 is as described above. However, information 650 contains additional new content not found in information 330, which is unique to various aspects of this invention. A field DAPSHandoverList 660 is added after the field BandCombinationList-v1560. A DAPSHandover section 680 is added to the end of information 650, which includes multiple DAPS switching-specific parameters.

[0163] After receiving the UE capability information sent by the UE, the network sends a DAPS-HO command to the UE. The DAPS-HO command sent by the network provides the target cell configuration to the UE, enabling the UE to establish a connection with the target cell. The signaling information used to configure the connection with the target cell is based on one or more capability parameters reported by the UE to the network.

[0164] If the UE indicates support for simultaneousRxPDCCH, then upon receiving the DAPS-HO command from the network, the UE monitors the PDCCH candidates of the target cell and the source cell in the same transport resource (e.g., within the same time slot). The PDCCH candidates monitored by the UE for the target cell are located on the CORESET and search space set indicated by the network in the DAPS-HO command.

[0165] If the UE indicates support for simultaneous TxPUCCH, then upon receiving the DAPS-HO command from the network, the UE transmits PUCCH to both the target cell and the source cell within the same transport resource (e.g., within the same time slot). The PUCCH transmission is carried out on the PUCCH resource group based on the corresponding beam assumption indicated by the network in the DAPS-HO command.

[0166] If the UE indicates support for multipleTimingAdvance, when receiving the DAPS-HO command from the network, the UE sends a RACH preamble to the target cell, obtains the timing advance of the target cell, and simultaneously maintains the timing advance values ​​of multiple cells (i.e., the target cell and the source cell).

[0167] If the UE indicates support for tdm-Pattern-PDCCH, it is not expected that the UE will use it to monitor multiple serving cell PDCCH candidates in each time unit when receiving the DAPS-HO command from the network.

[0168] If the UE indicates support for tdm-Pattern-PDSCH, then when receiving the DAPS-HO command from the network, it is not expected that the UE will receive PDSCH transmissions scheduled by the corresponding PDCCH transmission from multiple serving cells in each time unit.

[0169] If the UE indicates support for tdm-Pattern-PUCCH, then when receiving the DAPS-HO command from the network, it is not expected that the UE will use it to send multiple PUCCHs carrying the UCI of the corresponding PDSCH scheduled by the serving cell (source cell or target cell) through the PDCCH in each time unit.

[0170] If the UE indicates support for tdm-Pattern-PUSCH, then when receiving the DAPS-HO command from the network, it is not expected that the UE will send multiple serving cells' scheduled PUSCH transmissions via the corresponding PDCCH in each time unit.

[0171] The TDM map in any of the above cases can be based on one or more attributes, such as UE identifier, time-domain slots, QCL assumptions, frequency-domain resources, code sequences, and antenna ports.

[0172] If the UE indicates that it supports uplinkPowerSharing for a certain type of value (semi-static or dynamic), then when receiving the DAPS-HO command from the network, the UE shares the UE uplink transmission power between the source cell and the target cell in a semi-static or dynamic manner (as indicated by the network), corresponding to the uplink transmission power indicated by the network in the DAPS-HO command.

[0173] The following describes other examples of how the UE and network operate according to specific parameters indicated in the UE-NR-Capability message.

[0174] PDCCH receives simultaneously

[0175] If the UE indicates in UE-NR-Capability that the dapsHandover capability has a simultaneous RxPDCCH in a certain frequency band (e.g., in...), Figure 6A If the parameter group 641 indicates that the network can send a DAPS-HO command to the UE, then the network can send the command. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the target cell) in each time slot.

[0176] In another example, if the UE indicates the dapsHandover capability in UE-NR-Capability to the identifier marked with bandId (e.g., in... Figure 6A If a frequency band is specified in parameter group 641, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the target cell) in each time slot.

[0177] In another example, if the UE indicates the dapsHandover capability in UE-NR-Capability to an identifier identified as bandCombinationId (e.g., in... Figure 6A If a certain frequency band combination (indicated in parameter group 641) is selected, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the target cell) in each time slot.

[0178] The above embodiments can be used individually or in combination. For example, the UE may indicate the simultaneous RxPDCCH to a band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0179] PDSCH simultaneous reception

[0180] If the UE indicates in its UE-NR-Capability that the dapsHandover capability has simultaneous RxPDSCH in a certain frequency band, the network can send a DAPS-HO command to the UE. During the DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled by the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0181] In another example, if the UE indicates dapsHandover capability to a frequency band identified as bandId in UE-NR-Capability, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0182] In another example, if the UE indicates dapsHandover capability in UE-NR-Capability to a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0183] The above embodiments can be used individually or in combination. For example, the UE indicates that simultaneousRxPDSCH is part of a band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0184] Simultaneous transmission of PUCCH

[0185] If the UE indicates in its UE-NR-Capability that the dapsHandover capability has a simultaneous TxPUCCH in a certain frequency band, the network can send a DAPS-HO command to the UE. During the DAPS-HO, the UE is expected to report the UCI corresponding to the received PDSCH transmission scheduled through the corresponding PDCCH transmission with a certain serving cell.

[0186] In another example, if the UE indicates dapsHandover capability to a frequency band identified as bandId in UE-NR-Capability, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to report the UCI corresponding to the received PDSCH transmission scheduled via the corresponding PDCCH transmission with a serving cell.

[0187] In another example, if the UE indicates dapsHandover capability in UE-NR-Capability to a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to report the UCI corresponding to the received PDSCH transmission scheduled via the corresponding PDCCH transmission with a serving cell.

[0188] The above embodiments can be used individually or in combination. For example, the UE may indicate a simultaneous TxPUCCH to a frequency band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0189] Simultaneous transmission of PUSCH

[0190] If the UE indicates in its UE-NR-Capability that the dapsHandover capability has simultaneous TxPUSCH in a certain frequency band, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions for each serving cell (i.e., the source cell and the target cell) via the corresponding PDCCH.

[0191] In another example, if the UE indicates dapsHandover capability to a frequency band identified as bandId in UE-NR-Capability, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0192] In another example, if the UE indicates dapsHandover capability in UE-NR-Capability to a frequency band combination identified by bandCombinationId, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0193] The above embodiments can be used individually or in combination. For example, the UE may indicate simultaneousTxPUSCH to a band combination identified as bandCombinationId. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0194] Number of candidate target cells for DAPS-HO

[0195] If the UE indicates in UE-NR-Capability that the dapsHandover capability has a maximum number of maxNumCandidateTargetCells for a certain frequency band (e.g., in...), Figure 6A If the parameter group 641 indicates that the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE, then the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0196] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has a maximum of maxNumCandidateTargetCells for a certain frequency band, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0197] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells for a frequency band identified as bandId, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0198] In another example, if the UE indicates in its UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells for a certain frequency band identified by bandId, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0199] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells of a certain band combination identified as bandCombinationId, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0200] In another example, if the UE indicates in UE-NR-Capability that the dapsHandover capability has maxNumCandidateTargetCells of a certain band combination identified as bandCombinationId, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0201] In the various examples above, the serving cell can be the primary cell in a cell group and can correspond to the source cell or the candidate target cell indicated in the DAPS-HO command.

[0202] In another embodiment, the UE sends capability information or a capability report to the network in a format that includes DAPS-HO capability parameters. The DAPS-HO capability parameters include the DAPS-HO band combinations supported by the UE. In this embodiment, the DAPS-HO capability is indicated in the DL / UL function set of each reported CA / DC combination.

[0203] Figure 7A The hierarchy of information in the UE-NR-Capability message (UE-NR-Capability) is shown 700. Descriptions of levels 1 and 2 are referenced. Figure 3A However, there is a new additional Level 2 parameter identified as featureSets 720. The existing Level 3 parameters in this Level 2 parameter set include featureSetsDownlink, featureSetsDownlinkPerCC, featureSetsUplink, and featureSetsUplinkPerCC. These parameters can include additional information about specific features supported by the UE. The new Level 3 parameters in the featureSets 720 section include featureSetsDownlink-v16xx740 and featureSetsUplinkparameter-v16xx 745. featureSetsDownlink-v16xx 740 and featureSetsUplinkparameter-v16xx 745 represent additional capability parameters. However, it should be understood that this representation is merely for ease of understanding, and featureSetsDownlink-v16xx and featureSetsUplinkparameter-v16xx may not be specifically named.

[0204] The parameter `featureSetsDownlink-v16xx 740` can include additional parameters such as `simultaneousRxPDCCH` and `simultaneousRxPDSCH`. The parameter `featureSetsUplink-v16xx 745` can include additional parameters such as `simultaneousTxPUCCH`, `simultaneousTxPUSCH`, and `multipleTimingAdvance`. These parameters can include those described above. Figure 4B , Figure 5B , Figure 6B Similar information described and Figure 5C and Figure 5D A detailed description of the example in the document.

[0205] Figure 7B An example of information 750 is shown, which may optionally include the UE's capability message and is located in Figure 7A The hierarchy is shown in the featureSetsDownlink-v16xx 740 section. Each listed parameter can be used to represent a specific parameter name, possible values ​​for the parameter, or whether a specific feature is supported. An example of a value indicating whether a feature is supported might be a single bit, such as "1" for supported and "0" for not supported.

[0206] Examples of parameters in featureSetsDownlink-v16xx 740 include, but are not limited to: simultaneousRxPDCCH, simultaneousRxPDSCH, simultaneousTxPUCCH, simultaneousTxPUSCH, multipleTimingAdvance, tdm-Pattern-PDCCH, and tdm-Pattern-PDSCH.

[0207] These parameters have the same meaning as those described in Embodiments 1 and 2 above, but can be implemented in different ways.

[0208] After receiving the UE capability information sent by the UE, the network sends a DAPS-HO command to the UE. The DAPS-HO command sent by the network provides the target cell configuration to the UE, enabling the UE to establish a connection with the target cell. The signaling information used to configure the connection with the target cell is based on one or more capability parameters reported by the UE to the network.

[0209] If the UE indicates support for simultaneousRxPDCCH, then upon receiving the DAPS-HO command from the network, the UE monitors the PDCCH candidates of the target cell and the source cell in the same transport resource (e.g., within the same time slot). The PDCCH candidates monitored by the UE for the target cell are located on the CORESET and search space set indicated by the network in the DAPS-HO command.

[0210] If the UE indicates support for simultaneous TxPUCCH, then upon receiving the DAPS-HO command from the network, the UE transmits PUCCH to both the target cell and the source cell within the same transport resource (e.g., within the same time slot). The PUCCH transmission is carried out on the PUCCH resource group based on the corresponding beam assumption indicated by the network in the DAPS-HO command.

[0211] If the UE indicates support for multipleTimingAdvance, when receiving the DAPS-HO command from the network, the UE sends a random access channel (RACH) preamble to the target cell, obtains the timing advance of the target cell, and maintains the timing advance values ​​of multiple cells simultaneously.

[0212] PDCCH receives simultaneously

[0213] If the UE indicates featureSetsDownlink capability in UE-NR-Capability (e.g., by...) Figure 7A If the attached figure (reference numeral 740 indicates a simultaneous RxPDCCH in a certain frequency band), the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the target cell) in each time slot.

[0214] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsDownlink capability has a simultaneous RxPDCCH for a certain frequency band combination, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the target cell) in each time slot.

[0215] PDSCH simultaneous reception

[0216] If the UE indicates in its UE-NR-Capability that the featureSetsDownlink capability has simultaneous RxPDSCH in a certain frequency band, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled through the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0217] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsDownlink capability has a simultaneous RxPDSCH for a certain frequency band combination, the network can send a DAPS-HO command to the UE. During the DAPS-HO, the UE is expected to receive PDSCH transmissions scheduled via the corresponding PDCCH for each serving cell (i.e., the source cell and the target cell).

[0218] Simultaneous transmission of PUCCH

[0219] If the UE indicates featureSetsUplink capability in UE-NR-Capability (e.g., by...) Figure 7A If a simultaneous TxPUCCH (as shown by reference numeral 745 in the attached diagram) has a certain frequency band, the network can send a DAPS-HO command to the UE. During the DAPS-HO period, the UE is expected to report the UCI corresponding to the received PDSCH transmission scheduled through the corresponding PDCCH transmission with a certain serving cell.

[0220] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsUplink capability has a simultaneous TxPUCCH for a certain frequency band combination, the network can send a DAPS-HO command to the UE. During the DAPS-HO, the UE is expected to report the UCI corresponding to the received PDSCH transmission scheduled via the corresponding PDCCH transmission with a serving cell.

[0221] Simultaneous transmission of PUSCH

[0222] If the UE indicates in its UE-NR-Capability that the featureSetsUplink capability has simultaneous TxPUSCH in a certain frequency band, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions for each serving cell (i.e., the source cell and the target cell) via the corresponding PDCCH.

[0223] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsUplink capability has a simultaneous TxPUSCH for a certain frequency band combination, the network can send a DAPS-HO command to the UE. During DAPS-HO, the UE is expected to send PUSCH transmissions for each serving cell (i.e., the source cell and the target cell) via the corresponding PDCCH.

[0224] Number of candidate target cells for DAPS-HO

[0225] If the UE indicates in UE-NR-Capability that the featureSetsDownlink capability has a maxNumCandidateTargetCells for a certain frequency band (e.g., by...), Figure 7A As shown by reference numeral 740 in the attached figure, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period of a target cell, the UE is expected to monitor the PDCCH candidates of each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0226] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsDownlink capability has maxNumCandidateTargetCells for a certain frequency band, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0227] In another example, if the UE indicates in UE-NR-Capability that the featureSetsDownlink capability has maxNumCandidateTargetCells for a frequency band identified as bandId, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0228] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsDownlink capability has maxNumCandidateTargetCells for a frequency band identified by bandId, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0229] In another example, if the UE indicates in UE-NR-Capability that the featureSetsDownlink capability has maxNumCandidateTargetCells of a certain band combination identified as bandCombinationId, the network can send a maximum of maxNumCandidateTargetCells DAPS-HO commands to the UE. During each DAPS-HO period for a target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0230] In another example, if the UE indicates in its UE-NR-Capability that the featureSetsDownlink capability has maxNumCandidateTargetCells for a certain band combination identified by bandCombinationId, the network can send the UE a DAPS-HO command carrying up to maxNumCandidateTargetCells of target cell configurations. During each DAPS-HO period for a given target cell, the UE is expected to monitor the PDCCH candidates for each serving cell (i.e., the source cell and the given target cell) in each time slot.

[0231] The following includes several other examples of UE behavior under simultaneous connection handover related to UE capabilities, which apply to any of Embodiments 1, 2 and 3.

[0232] The following embodiments provide examples of UE behavior, wherein the UE indicates a capability C that may not be included in dapsHandover or a specific frequency band or combination of frequency bands. However, this capability C still affects the UE's behavior during DAPS-HO when the UE is used to perform DAPS-HO operations.

[0233] PDCCH receives simultaneously

[0234] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum number of CORESETs for the source and target cells via the parameter maxNumCORESETs. If the UE reports the maxNumCORESETs of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to configure a number of CORESETs greater than maxNumCORESETs in a cell. The UE monitors a maximum of multiple PDCCH candidates within a single cell (i.e., the source or target cell) at a time slot, up to maxNumCORESETs of CORESETs.

[0235] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of search space sets for the source and target cells via the parameter maxNumSearchSpaceSets. If the UE reports the maxNumSearchSpaceSets of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to configure a search space set larger than maxNumSearchSpaceSets in any given cell. The UE monitors a maximum of multiple PDCCH candidates within a single cell's (i.e., the source or target cell) search space sets in each time slot.

[0236] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of PDCCH candidates for the source and target cells via the parameter maxNumPDCCHCandidates. If the UE reports maxNumPDCCHCandidates for a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to monitor more than maxNumPDCCHCandidates of PDCCH candidates in a cell within each time slot. The UE monitors a maximum of maxNumPDCCHCandidates of PDCCH candidates within a certain number of CORESETs and the search space set of a cell (i.e., the source or target cell) in each time slot.

[0237] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum number of non-overlapping CCEs for the PDCCH candidates in the source and target cells via the parameter maxNumNonOverlappedCCEs. If the UE reports maxNumNonOverlappedCCEs for a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to provide multiple non-overlapping CCEs to monitor a number of corresponding PDCCH candidates in a cell that exceeds maxNumNonOverlappedCCEs. The UE monitors a maximum of multiple PDCCH candidates within the maxNumNonOverlappedCCEs CCEs of a cell (i.e., the source or target cell) per time slot.

[0238] The above embodiments can be used individually or in combination. For example, the UE indicates the maximum number of CORESET and PDCCH candidates. The above embodiments for the UE to indicate DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0239] The above embodiments also apply to the maximum values ​​provided for all serving cells (i.e., source cells and candidate target cells). For example, the UE can indicate in UE-NR-Capability the maxNumCORESETs that can be used in combination across source and target cells.

[0240] The above embodiments can be described as supporting UE capabilities for various purposes, not just DAPS-HO, such as multiple transport receiver point (TRP) transmission, ultra-reliable low-latency communication (URLLC), multiple-input multiple-output (MIMO), vehicle-to-everything (V2X), new radio unlicensed spectrum (NR-U), new radio dual connectivity (NR-DC), and new radio carrier aggregation (NR-CA). In some embodiments, to achieve the other purposes described above, these capabilities can be communicated to the network in a similar manner to that used in implementing DAPS-HO.

[0241] Simultaneous transmission of PDSCH

[0242] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of codewords for the source and target cells via the `maxNumCodewords` parameter. If the UE reports the `maxNumCodewords` of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords that are scheduled in a cell greater than `maxNumCodewords`. The UE can receive a maximum of `maxNumCodewords` codewords from a single cell (i.e., the source or target cell) in each time slot.

[0243] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of layers for the source and target cells via the `maxNumLayers` parameter. If the UE reports the `maxNumLayers` of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords scheduled on layers with a number greater than `maxNumLayers` in a given cell. The UE can receive a maximum of `maxNumLayers` codewords from a single cell in each time slot.

[0244] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of layers in each codeword of the source and target cells via the parameter maxNumLayersPerCodeword. If the UE reports the maxNumLayersPerCodeword of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords in a cell that use more layers than maxNumLayersPerCodeword in a given codeword. The UE can receive at most maxNumLayersPerCodeword layers in each codeword of a cell (i.e., the source or target cell) in each time slot.

[0245] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum number of active transmission configuration indicator (TCI) states in the PDSCH transmissions of the source and target cells via the parameter maxNumActiveTCIStates. If the UE reports the maxNumActiveTCIStates of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI formats that use more than maxNumActiveTCIStates of active TCI state scheduling codewords in a cell. The UE receives at most maxNumActiveTCIStates of active TCI states in each PDSCH transmission of a cell (i.e., the source or target cell) per time slot.

[0246] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of PRBs for the active DL BWP in the source and target cells via the parameter maxNumPRBs. If the UE reports the maxNumPRBs of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords using a number of PRBs greater than maxNumPRBs in a given cell. The UE receives multiple codewords in each time slot, up to maxNumPRBs of PRBs for a given cell (i.e., the source or target cell).

[0247] The above embodiments can be used individually or in combination. For example, the UE indicates the maximum value of the codeword and layer. The above embodiments for the UE to indicate DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0248] The above embodiments also apply to the maximum values ​​provided for all serving cells (i.e., source cells and candidate target cells). For example, the UE can indicate in UE-NR-Capability the maxNumCodewords that can be used in combination across source and target cells.

[0249] The above embodiments can utilize UE capabilities for a variety of purposes, not just DAPS-HO.

[0250] Simultaneous transmission of PUCCH

[0251] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of PUCCH resource sets for the source and target cells via the parameter maxNumPUCCHResourceSets. If the UE reports the maxNumPUCCHResourceSets of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to configure a PUCCH resource set in a cell with a number greater than maxNumPUCCHResourceSets.

[0252] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum value of the number of PUCCH spatial relationships between the source and target cells using the parameter maxNumPUCCHSpatialRelations. If the UE reports the maxNumPUCCHSpatialRelations of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to configure a number of PUCCH spatial relationships in a cell that are greater than maxNumPUCCHSpatialRelations.

[0253] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum value of the UCI payload for the source and target cells using the parameter maxUCIPayloadSize. If the UE reports the maxUCIPayloadSize of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE sends a PUCCH carrying the UCI with a payload up to maxUCIPayloadSize.

[0254] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum number of PDSCH transmissions that the UE can use to combine to generate a UCI carrying the HARQ-ACK bits of the corresponding PDSCH transmissions for the source and target cells via the parameter maxNumPDSCHstoCombine. If the UE reports maxNumPDSCHstoCombine for a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not need to combine HARQ-ACK bits used for more than maxNumPDSCHstoCombine PDSCH transmissions in a UCI within a cell.

[0255] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate a value in the {dynamic; semiStatic} field to support uplinkPowerSharing for both the source and target cells. If the UE reports uplinkPowerSharing in UE-NR-Capability, the UE sends PUCCHs carrying UCIs to both the source and target cells based on the value reported in uplinkPowerSharing.

[0256] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate a value in the {supported} field to support multipleTimingAdvance for both the source and target cells. If the UE reports multipleTimingAdvance in UE-NR-Capability, the UE sends a PUCCH carrying the UCI to both the source and target cells using the corresponding timing advance value.

[0257] The above embodiments can be used individually or in combination. For example, the UE indicates the maximum value of the PUCCH resource set and the maximum value of the UCI payload. The above embodiments of the UE indicating DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0258] The above embodiments also apply to the maximum values ​​provided for all serving cells (i.e., source cells and candidate target cells). For example, the UE can indicate in UE-NR-Capability that maxNumPUCCHResourceSets can be used in combination across source and target cells.

[0259] The above embodiments can utilize UE capabilities for a variety of purposes, not just DAPS-HO.

[0260] Simultaneous transmission of PUSCH

[0261] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of codewords for the source and target cells via the `maxNumCodewords` parameter. If the UE reports the `maxNumCodewords` of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords that are scheduled in a cell greater than `maxNumCodewords`. The UE can receive a maximum of `maxNumCodewords` codewords from a single cell (i.e., the source or target cell) in each time slot.

[0262] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of layers for the source and target cells via the `maxNumLayers` parameter. If the UE reports the `maxNumLayers` of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords scheduled on layers with a number greater than `maxNumLayers` in a given cell. The UE can receive a maximum of `maxNumLayers` codewords from a single cell in each time slot.

[0263] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of layers in each codeword of the source and target cells via the parameter maxNumLayersPerCodeword. If the UE reports the maxNumLayersPerCodeword of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords in a cell that use more layers than maxNumLayersPerCodeword in a given codeword. The UE can receive at most maxNumLayersPerCodeword layers in each codeword of a cell (i.e., the source or target cell) in each time slot.

[0264] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of active TCI states in the PDSCH transmissions of the source and target cells via the parameter maxNumActiveTCIStates. If the UE reports the maxNumActiveTCIStates of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI formats that use more than maxNumActiveTCIStates of active TCI state scheduling codewords in a cell. The UE receives at most maxNumActiveTCIStates of active TCI states in each PDSCH transmission of a cell (i.e., the source or target cell) in each time slot.

[0265] When a UE performs a DAPS-HO operation (i.e., when the UE receives a DAPS-HO command from the network), the UE can indicate the maximum corresponding number of PRBs for the active DL BWP in the source and target cells via the parameter maxNumPRBs. If the UE reports the maxNumPRBs of a cell (i.e., the source or target cell) in UE-NR-Capability, the UE does not expect to receive DCI format codewords using a number of PRBs greater than maxNumPRBs in a given cell. The UE receives multiple codewords in each time slot, up to maxNumPRBs of PRBs for a given cell (i.e., the source or target cell).

[0266] The above embodiments can be used individually or in combination. For example, the UE indicates the maximum value of the codeword and layer. The above embodiments for the UE to indicate DAPS-HO capability in a certain frequency band are applicable to the following situations: the source cell and the target cell are in the same DL BWP of a certain carrier, in different DL BWPs of a certain carrier, or in different carriers of a certain frequency band.

[0267] The above embodiments also apply to the maximum values ​​provided for all serving cells (i.e., source cells and candidate target cells). For example, the UE can indicate in UE-NR-Capability the maxNumCodewords that can be used in combination across source and target cells.

[0268] The above embodiments can utilize UE capabilities for a variety of purposes, not just DAPS-HO.

[0269] The following section describes the network-side procedures after the network receives DAPS-HO capability information from the UE.

[0270] In some embodiments, the network sends a DAPS-HO command to the UE and provides the target cell configuration to the UE, enabling the UE to establish a connection with the target cell. To handle situations that may exceed the UE's capabilities, priority rules can be defined to help the UE determine which processing tasks should be executed first within a given time period.

[0271] If some physical channels overlap in specific domains (e.g., time domain, frequency domain, spatial domain, code domain, etc.), the UE can release one of the PUCCH transmissions based on the following criteria: service type (Mobile Broadband (MBB) and Ultra-Reliable Low-Latency Communication (URLLC)), uplink control information (UCI) payload size, and cell type (source cell and target cell). In a specific example, if the PUCCHs of the source cell and the target cell overlap on some resources, the UE can release the PUCCH with the smaller UCI payload, or transmit the UCI of the first PUCCH in the next PUCCH transmission opportunity.

[0272] If the network configures parameters to the UE that would cause the UE to exceed its capabilities in certain aspects (e.g., PDCCH candidate monitoring, PUCCH transmission, UL power control), the UE may not process tasks that exceed the capabilities previously reported to the network by the UE.

[0273] For example, if a UE reports its ability to perform N blind PDCCH detections in each transmission resource (e.g., time slot) in each serving cell, where N is an integer, and the network configures the CORESET and search space set to the serving cell (e.g., source cell or target cell), such that the UE may need to perform N' (>N) blind PDCCH detections in each time slot to find the PDCCH message, then it is not expected that the UE will perform more than N blind PDCCH detections in the corresponding cell.

[0274] For example, if the UE reports its ability to control uplink power dynamically or semi-statically, and the network configuration exceeds the maximum transmit power that the UE can transmit, then the UE is not expected to transmit at a power higher than its maximum transmit power.

[0275] In some embodiments, the UE can report the ability to configure the network to perform mobility procedures that reduce and eliminate service interruptions. This is because the network can configure two serving cells for the UE, allowing the UE to receive transmissions from both the source and target cells simultaneously.

[0276] In addition, the network can configure two serving cells to the UE, enabling simultaneous transmission to the source cell and the target cell, or transmission to the source cell and the target cell in an orthogonal manner (e.g., in the time domain, frequency domain, code domain, spatial domain, etc.).

[0277] Based on the UE capability report, the network can configure the UE to perform handovers that reduce or eliminate service interruptions.

[0278] When the UE is located at the edge of a serving cell adjacent to the target cell, the network can instruct the UE to monitor the PDCCH candidates of the source and target cells during handover. Similarly, the network can instruct the UE to send the PUCCH corresponding to the PDSCH transmission to the source and target cells during handover.

[0279] In some embodiments, priority-based rules may be based on timers. Figure 8 The diagram illustrates the possible handover duration of 800 seconds. In the accompanying figure, the UE monitors both the source and target cells only for the maximum finite duration of the timer. Once the timer expires, the UE monitors only the target cell. In a specific example, for the duration 810 before the handover occurs, the UE monitors only the source cell's PDCCH. When the handover is about to occur, the timer can start at 815. While the timer is running at 820, the UE monitors the PDCCHs of both the source and target cells. The timer expires at 825, after which the UE monitors only the target cell's PDCCH at 830. In this example, the UE can switch to monitoring only the target cell's PDCCH before the timer expires, but will not monitor either the source or target cell's PDCCH after the timer expires.

[0280] Figure 9BThis is an exemplary signal flow diagram of the signaling occurring between UE 910 and source cell 904, and between UE 910 and target cell 907 when using timers. Source cell 904 and target cell 907 are part of the network in which UE 910 communicates. Processes performed by the network (e.g., generating DAPS-HO commands based on UE capability information provided by UE 910) may be concentrated in or near target cell 907 or source cell 904, or elsewhere in the network. At some point before a possible handover from source cell 904 to target cell 907, UE 910 sends a higher-level signaling message 920 including UE-NR-Capability information. This information may include capability information about many capabilities supported by UE 910, some of which are related to DAPS-HO capabilities, or the capability information sent to the network at a certain time may only be related to the DAPS-HO capabilities supported by UE 910. The higher-level signaling may be RRC signaling. At a certain point after the source cell 904 receives the UE capability information, the network generates a DAPS-HO command, and the source cell 904 sends the DAPS-HO command (930) to the UE 910. At a certain point after receiving the DAPS-HO command, the UE 910 starts a timer (935). If the UE 910 has not switched to the target cell 907 by the timer expires, the UE 910 releases the source cell 904. In step 940, the source cell 904 and the target cell 907 send a PDDCH message. In step 950, the UE 910 monitors the PDDCH messages sent by the source cell 904 and the target cell 907 in step 940. As described above, if the UE 910 has not released the source cell 904 by the timer expires, the UE 910 continues to release the source cell 904 (965).

[0281] In this embodiment of the invention, if the source cell and the target cell use the exact same BWP bandwidth, which is consistent with the assumption in multiple TRP, where the TRP uses the same DL BWP (i.e. the same DL BWP bandwidth), then the functions supported by the multiple TRP framework are generally applicable to the same-frequency DAPS-HO case.

[0282] In some embodiments, during DAPS-HO, the UE monitors PDCCH candidates belonging to the search space sets of the source cell and the target cell within the same time slot. A search space set is configured for the primary cells in a Primary Cell Group (MCG). A primary cell in a given MCG is either the source cell or the target cell.

[0283] In some embodiments, for UEs that cannot transmit simultaneously, for co-frequency DAPS-HO, the UE sends separate PUCCH transmissions to the source cell and the target cell according to the protocols in the multi-TRP framework. For other cases of DAPS-HO, the UE sends PUCCH carrying HARQ-ACK according to the existing Rel.15 specification. For UEs that can transmit simultaneously, they send PUCCH transmissions carrying HARQ-ACK to the source cell and the target cell within the same time slot.

[0284] In some embodiments, if the source and target cells are in the same frequency range and use the same DL and UL BWP, the UE can determine the downlink path loss estimate for each cell based on the reference signal (RS) transmitted by each cell. However, UL power control can ultimately be jointly performed through semi-static power sharing. During DAPS-HO, the PUCCH uplink power control of UEs indicating DAPS-HO with simultaneous transmission capability assumes power sharing. The power sharing mechanism under the frequency range 1 (FR1) and FR1 band combination supported in Rel.16NR-New Radio Dual Connectivity (NR DC) is applicable to power sharing during DAPS-HO.

[0285] In some embodiments, simultaneous connectivity depends on the granularity level, such as time slots. If the granularity defined by the TDM map is smaller than the time slot, it is still possible to configure the UE to simultaneously receive PDCCH and transmit PUCCH in FR2. For UEs in FR2, receiving PDCCH / PDSCH from the source gNB and the target gNB according to TDM during DAPS-HO is supported. For UEs in FR2, transmitting PUCCH / PUSCH to the source gNB and the target gNB according to TDM during DAPS-HO is supported.

[0286] In some embodiments, when DAPS-HO occurs, it is not expected that the UE will be in discontinuous reception (DRX) operation mode, nor is it expected that the UE will be configured with the same DRX periodicity during DAPS-HO operation. For each frequency band or combination of frequency bands that the UE supports for DAPS-HO, the UE may further indicate the functions that the UE supports to implement DAPS-HO, such as simultaneous reception, simultaneous transmission, etc. DAPS-HO capability is reported in each frequency band and / or each combination of frequency bands.

[0287] In some embodiments, for each supported frequency band or combination of frequency bands, the UE reports a set of supported functions, such as simultaneous PDCCH reception, PDSCH with full / partial / non-overlapping signals, multiple timing advance, dynamic or semi-static UL power control, etc.

[0288] It should be understood that one or more steps in the methods of the embodiments provided herein can be performed by corresponding units or modules. For example, a signal can be transmitted by a transmitting unit or transmitting module. A signal can be received by a receiving unit or receiving module. A signal can be processed by a processing unit or processing module. The corresponding units / modules can be hardware, software, or a combination thereof. For example, one or more of the above units / modules can be integrated circuits, such as field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs). It should be understood that if these modules are software, then these modules can be retrieved by a processor, in whole or in part, individually or collectively, for processing as needed, or in one or more instances as needed, and these modules themselves can include instructions for further deployment and instantiation.

[0289] While combinations of features are shown in the illustrated embodiments, not all features need to be combined to achieve the advantages of the various embodiments of the invention. In other words, a system or method designed according to one embodiment of the invention does not necessarily include all features or portions shown schematically in any of the figures. Furthermore, selected features of one exemplary embodiment may be combined with selected features of other exemplary embodiments.

[0290] Although the invention has been described with reference to illustrative embodiments, this specification is not intended to be limiting. Various modifications and combinations of the illustrative embodiments, as well as other embodiments of the invention, will be apparent to those skilled in the art upon reference to this specification. Therefore, the appended claims are intended to cover any such modifications or embodiments.

Claims

1. A communication method, characterized in that, The method includes: The user equipment (UE) selects the dual-active protocol stack handover (DAPS-HO) UE capability information to be provided to the network, wherein the capability information indicates the functions supported by the UE during the handover from the source cell to the target cell, and the DAPS-HO UE capability information is also used to indicate whether the UE supports uplink transmission in both the source cell and the target cell during the DAPS-HO process; The UE sends the selected DAPS-HO capability information to the network; The UE receives a DAPS-HO command generated from the network based on the DAPS-HO capability information, wherein the DAPS-HO command is used to execute DAPS-HO.

2. The method according to claim 1, characterized in that, Sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

3. The method according to claim 1 or 2, characterized in that, The DAPS-HO UE capability information includes one or more of the following parameters: Simultaneous reception of the physical downlink control channel (PDCCH) of both the source cell and the target cell; Simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) between the source cell and the target cell; Multi-path timing lead; Band identifier (bandId); Time Division Multiplexing (TDM) pattern of PDCCH; TDM spectra of PDSCH; PUCCH's TDM spectrum; PUSCH's TDM spectrum; The maximum number of candidate target cells; or Uplink power sharing between the source cell and the target cell.

4. The method according to claim 1, characterized in that, Sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the frequency band combination list parameters.

5. The method according to claim 4, characterized in that, The DAPS-HO UE capability information includes one or more parameters, at least one of which includes additional parameters that further define how to support the at least one parameter.

6. The method according to claim 1, characterized in that, Sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the DAPS-HO list parameters.

7. The method according to claim 6, characterized in that, The DAPS-HO UE capability information includes one or more parameters, at least one of which includes additional parameters that further define how to support the at least one parameter.

8. The method according to claim 1, characterized in that, Sending the selected DAPS-HO capability information to the network includes sending the selected DAPS-HO capability information as a subset of the function set parameters.

9. The method according to claim 8, characterized in that, The DAPS-HO UE capability information includes one or more parameters, at least one of which includes additional parameters that further define how to support the at least one parameter.

10. A communication method, characterized in that, The method includes: The network receives Dual Activated Protocol Stack Handover (DAPS-HO) UE capability information from the UE, wherein the capability information indicates the functions supported by the UE during handover from the source cell to the target cell, and the DAPS-HO UE capability information is also used to indicate whether the UE supports uplink transmission in both the source cell and the target cell during the DAPS-HO process; The network sends a DAPS-HO command generated based on the DAPS-HO capability information to the UE, wherein the DAPS-HO command is used to execute DAPS-HO.

11. The method according to claim 10, characterized in that, Receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

12. The method according to claim 10 or 11, characterized in that, The DAPS-HO UE capability information includes one or more of the following parameters: Simultaneous reception of the physical downlink control channel (PDCCH) of both the source cell and the target cell; Simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) between the source cell and the target cell; Multi-path timing lead; Band identifier (bandId); Time Division Multiplexing (TDM) pattern of PDCCH; TDM spectra of PDSCH; PUCCH's TDM spectrum; PUSCH's TDM spectrum; The maximum number of candidate target cells; or Uplink power sharing between the source cell and the target cell.

13. The method according to claim 10, characterized in that, Receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the frequency band combination list parameters.

14. The method according to claim 13, characterized in that, The DAPS-HO UE capability information includes one or more parameters, at least one of which includes additional parameters that further define how to support the at least one parameter.

15. The method according to claim 10, characterized in that, Receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the DAPS-HO list parameters.

16. The method according to claim 15, characterized in that, The DAPS-HO UE capability information includes one or more parameters, at least one of which includes additional parameters that further define how to support the at least one parameter.

17. The method according to claim 10, characterized in that, Receiving DAPS-HO capability information includes receiving the DAPS-HO capability information as a subset of the function set parameters.

18. The method according to claim 17, characterized in that, The DAPS-HO UE capability information includes one or more parameters, at least one of which includes additional parameters that further define how to support the at least one parameter.

19. A device, characterized in that, The device includes: processor; A computer-readable medium having processor-executable instructions stored therein, wherein, when executed, the processor-executable instructions cause the device to: Select the dual-active protocol stack handover (DAPS-HO) device capability information to be provided to the network, wherein the capability information indicates the functions supported by the device during handover from the source cell to the target cell, and the DAPS-HO UE capability information is also used to indicate whether the UE supports uplink transmission in both the source cell and the target cell during the DAPS-HO process; Send the selected DAPS-HO capability information to the network; Receive from the network a DAPS-HO command generated based on the DAPS-HO capability information, wherein the DAPS-HO command is used to execute DAPS-HO.

20. The device according to claim 19, characterized in that, When the processor-executable instruction that causes the device to send the selected DAPS-HO capability information is executed, the device sends the selected DAPS-HO capability information as a subset of the radio frequency (RF) parameters held by the device.

21. The device according to claim 19 or 20, characterized in that, The selectable DAPS-HO UE capability information includes one or more of the following parameters: Simultaneous reception of the physical downlink control channel (PDCCH) of both the source cell and the target cell; Simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) between the source cell and the target cell; Multi-path timing lead; Band identifier (bandId); Time Division Multiplexing (TDM) pattern of PDCCH; TDM spectra of PDSCH; PUCCH's TDM spectrum; PUSCH's TDM spectrum; The maximum number of candidate target cells; or Uplink power sharing between the source cell and the target cell.

22. The device according to claim 19, characterized in that, When the processor-executable instruction that causes the device to send the selected DAPS-HO capability information is executed, the device sends the selected DAPS-HO capability information as a subset of the frequency band combination list parameters.

23. A device, characterized in that, The device includes: processor; A computer-readable medium having processor-executable instructions stored therein, wherein, when executed, the processor-executable instructions cause the device to: The UE receives Dual Activated Protocol Stack Handover (DAPS-HO) UE capability information, wherein the capability information indicates the functions supported by the UE during handover from the source cell to the target cell, and the DAPS-HO UE capability information is also used to indicate whether the UE supports uplink transmission in both the source cell and the target cell during the DAPS-HO process; Send a DAPS-HO command generated based on the DAPS-HO capability information to the UE, wherein the DAPS-HO command is used to execute DAPS-HO.

24. The device according to claim 23, characterized in that, When the processor-executable instruction that causes the device to receive DAPS-HO capability information is executed, the device receives the DAPS-HO capability information as a subset of the radio frequency (RF) parameters supported by the UE.

25. The device according to claim 23 or 24, characterized in that, The DAPS-HO UE capability information includes one or more of the following parameters: Simultaneous reception of the physical downlink control channel (PDCCH) of both the source cell and the target cell; Simultaneous reception of the Physical Downlink Shared Channel (PDSCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Control Channel (PUCCH) of the source cell and the target cell; Simultaneous transmission of the Physical Uplink Shared Channel (PUSCH) between the source cell and the target cell; Multi-path timing lead; Band identifier (bandId); Time Division Multiplexing (TDM) pattern of PDCCH; TDM spectra of PDSCH; PUCCH's TDM spectrum; PUSCH's TDM spectrum; The maximum number of candidate target cells; or Uplink power sharing between the source cell and the target cell.

26. The device according to claim 23, characterized in that, When the processor-executable instruction that causes the device to receive DAPS-HO capability information is executed, the device receives the DAPS-HO capability information as a subset of the frequency band combination list parameters.

27. A device, characterized in that, The device includes: processor; A computer-readable medium having processor-executable instructions stored therein, wherein, when executed, the processor-executable instructions cause the device to: Select the dual-active protocol stack handover (DAPS-HO) device capability information to be provided to the network, wherein the capability information indicates the functions supported by the device during handover from the source cell to the target cell, and the DAPS-HO UE capability information is also used to indicate whether the UE supports uplink transmission in both the source cell and the target cell during the DAPS-HO process; Send the selected DAPS-HO capability information to the network; Receive a DAPS-HO command from the network, wherein the DAPS-HO command is used to execute DAPS-HO.

Images