Method related to inter-cell beam operation, user equipment and network equipment

Abstract

The invention provides a method related to inter-cell beam operation, user equipment and network equipment. The method includes receiving an RRC message from a serving cell, applying at least one of a TCI configuration, an RS configuration associated with the TCI configuration, and a first value of a CORESET pool index, and performing transmission or reception with another cell according to an applied configuration from the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index. The RRC message includes first information of at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index, and the first information is associated with the other cell having a second PCI different from a first PCI of the serving cell.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application Serial No. 63 / 336,944, filed on April 29, 2022, with attorney case number US87368, and entitled “METHOD AND APPARATUS FOR SYSTEMINFORMATION TRANSMISSION AND RECEPTION IN INTER-CELL BEAM MANAGEMENT,” the contents of which are hereby incorporated by reference into this disclosure in their entirety. Technical Field

[0002] The present disclosure relates generally to wireless communications, and more particularly to methods, user equipment, and network devices related to inter-cell beam operations. Background Art

[0003] With the huge growth in the number of connected devices and the rapid increase in the total amount of user / network traffic, various efforts have been made to improve different aspects of wireless communication in next generation wireless communication systems such as fifth generation (5G) New Radio (NR) by improving data rate, latency, reliability and mobility. The 5G NR system is designed to provide flexibility and configurability to optimize network services and types to accommodate various use cases such as enhanced mobile broadband (eMBB), massive machine type communication (mMTC) and ultra-reliable and low latency communication (URLLC).

[0004] Multiple Input Multiple Output (MIMO) is one of the key technologies for achieving high data rates and meeting the requirements of enhanced mobile broadband (eMBB) in 5G systems. In addition, MIMO technology is successful in commercial deployment. MIMO features are studied and specified for both FDD and TDD systems, the main part of which is used for downlink MIMO operation. In addition, enhancing uplink MIMO is important, while the necessary enhancements on downlink MIMO that promote the use of large antenna arrays (not only for FR1 but also for FR2) will still need to be introduced to meet the requirements for the evolution of NR deployment.

[0005] Multiple transmission and reception points (multiple TRPs, mTRPs) are introduced to enhance massive MIMO. In addition, the mTRP feature can improve reliability, coverage, and capability performance through flexible deployment scenarios. In mTRP operation, the base station can communicate with the UE through multiple TRPs. It should be noted that each TRP can be associated with a cell, a specific sounding reference signal (SRS) resource set, a specific radio resource control (RRC) parameter (i.e., CORESETPoolIndex), and / or a specific transmission configuration indication (TCI) state. It should be noted that the TCI state may include parameters for configuring a quasi-co-site (QCL) relationship between one or two downlink (DL) reference signals and a target reference signal set. For example, the target reference signal set can be a demodulation reference signal (DMRS) port of a PDSCH or a physical downlink control channel (PDCCH).

[0006] When multi-beam operation is involved, especially when targeting FR2, a unified TCI framework is introduced to facilitate pipelined multi-beam operation and reduce signaling overhead. The unified TCI framework is applied to the single TRP case, but it is envisioned that the unified TCI framework will be applied to the multi-TRP case.

[0007] With the evolution of MIMO technology, inter-cell mobility including inter-cell beam management has attracted attention. In order to reduce latency and signaling overhead while achieving high data rates, it is important and necessary to study inter-cell mobility, especially in mTRP operation. Summary of the invention

[0008] The present disclosure relates to methods, user equipment (UE) and network devices related to inter-cell beam operation.

[0009] According to one or more exemplary embodiments of the present disclosure, a method related to inter-cell beam operation applicable to a UE is provided. The method includes but is not limited to: receiving a radio resource control (RRC) message from a serving cell, applying at least one of a transmission configuration indicator (TCI) configuration, a reference signal (RS) configuration associated with the TCI configuration, and a first value of a control resource set (CORESET) pool index, and performing transmission or reception with another cell according to the applied configuration of at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index. The RRC message includes first information of at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index, and the first information is associated with the other cell having a second PCI different from the first physical cell identifier (PCI) of the serving cell.

[0010] According to one or more exemplary embodiments of the present disclosure, a UE is provided. The UE includes, but is not limited to: a transceiver; one or more non-transitory computer-readable media, on which the one or more non-transitory computer-readable media embody computer-executable instructions; and at least one processor, which is coupled to the transceiver and the one or more non-transitory computer-readable media. The processor is configured to execute the computer-executable instructions to: receive an RRC message from a serving cell through the transceiver, apply at least one of a TCI configuration, an RS configuration associated with the TCI configuration, and a first value of a CORESET pool index, and perform transmission or reception with another cell through the transceiver according to the applied configuration of at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index. The RRC message includes first information of at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index, and the first information is associated with the other cell having a second PCI different from the first PCI of the serving cell.

[0011] According to one or more exemplary embodiments of the present disclosure, a network device is provided. The network device includes, but is not limited to: a transceiver; one or more non-transitory computer-readable media, on which the one or more non-transitory computer-readable media embody computer-executable instructions; and at least one processor, the at least one processor being coupled to the transceiver and the one or more non-transitory computer-readable media. The processor is configured to execute the computer-executable instructions to: send an RRC message to a UE via a serving cell through the transceiver, and perform transmission or reception through the transceiver via another cell according to at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index. The RRC message includes first information of at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index, and the first information is associated with the other cell having a second PCI different from the first PCI of the serving cell. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] When with Figure 1 Various aspects of the exemplary disclosure are best understood from the following detailed description when read in conjunction with the various features that are not drawn to scale and the dimensions of the various features may be arbitrarily increased or reduced for clarity of discussion. Figure 1 is a schematic diagram illustrating a radio communication network architecture according to an exemplary embodiment of the present disclosure. Figure 2is a schematic diagram illustrating association in inter-cell beam management according to one of the exemplary embodiments of the present disclosure. Figure 3 is a flowchart of a method applicable to a UE according to an exemplary embodiment of the present disclosure. Figure 4 is a flow chart of a method related to capability inquiry according to an exemplary embodiment of the present disclosure. Figure 5 This is a schematic diagram illustrating that the same MAC entity of a UE according to one of the exemplary embodiments of the present disclosure processes messages / information / signals sent to or received from a TRP of a serving cell (or a TRP associated with the PCI of a serving cell) and a TRP associated with a PCI different from the PCI of the serving cell. Figure 6 This is a schematic diagram illustrating that different MAC entities of a UE according to one of the exemplary embodiments of the present disclosure process messages / information / signals sent to or received from a TRP of a serving cell (or a TRP associated with the PCI of a serving cell) and a TRP associated with a PCI different from the PCI of the serving cell. Figure 7 is a flowchart of a method applicable to a network device according to an exemplary embodiment of the present disclosure. Figure 8 is a block diagram illustrating a node for wireless communication according to one of the exemplary embodiments of the present disclosure. DETAILED DESCRIPTION

[0013] The acronyms used in this disclosure are defined below, and unless otherwise indicated, the acronyms have the following meanings: Full acronym 3GPP 3rd Generation Partnership Project 5GC 5G Core ACK ARQ Automatic Repeat Request BS Base Station BWP Bandwidth Part CA Carrier Aggregation CCS Public Search Space CMAS Commercial Mobile Alerting System CN Core Network CORESET Control Resource Set C-RNTI Cell-Radio Network Temporary Identifier DC Dual Connection DCI Downlink Control Information DL Downlink ETWS Earthquake and Tsunami Warning System HARQ Hybrid Automatic Repeat Request ICBM inter-cell beam management IE Information Elements MAC Media Access Control MCG Master Cell Group MIB Master Information Block MIMO Multiple Input Multiple Output MR Multi-Radio Access Technology NG-RAN Next Generation Radio Access Network NR New Radio NW Network PCell Primary Cell PCI Physical Cell Identifier PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDSCH Physical Downlink Shared Channel PDU Protocol Data Unit PHY Physical Layer PRACH Physical Random Access Channel PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RA Random Access RACH Random Access Channel RAN Radio Access Network Rel version RLC Radio Link Control RNTI Radio Network Temporary Identifier RRC Radio Resource Control RS reference signal SCell Secondary Cell SCG Secondary Cell Group SCS Subcarrier Spacing SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SI System Information SIB System Information Block SRB Signalling Radio Bearer SSB Synchronous Signal Block TS Technical Specifications TCI Transmission Configuration Indicator TRP Send and Receive Points UCI Uplink Control Information UE User Equipment UL Uplink

[0014] The following description contains specific information about example implementations in the present disclosure. The drawings in the present disclosure and the detailed descriptions attached thereto are only for example implementations. However, the present disclosure is not limited to these example implementations. Other variations and implementations of the present disclosure will occur to those skilled in the art. Unless otherwise specified, identical or corresponding elements in the drawings may be indicated by identical or corresponding reference numerals. In addition, the drawings and illustrations in the present disclosure are generally not to scale and are not intended to correspond to actual relative sizes.

[0015] For the purpose of consistency and ease of understanding, in the example drawings, similar features may be identified by the same numerals (although not shown in some examples). However, features in different implementations may differ in other aspects, and therefore should not be narrowly limited to what is shown in the drawings.

[0016] The description uses the phrases "in one specific implementation", or "in some specific implementations", which may each refer to one or more of the same or different embodiments. The term "coupled" is defined as connected, whether directly or indirectly through intermediate components, and is not necessarily limited to physical connections. When used, the term "comprising" means "including, but not necessarily limited to", which specifically indicates an open inclusion or member in the described combination, group, series, and equivalents. The expression "at least one of A, B, and C" or "at least one of the following: A, B, and C" means "only A, or only B, or only C, or any combination of A, B, and C".

[0017] Any statement, paragraph, (sub) item, point, action, behavior, term, alternative, aspect, example or claim described in this disclosure can be logically, reasonably and appropriately combined to form a specific method. Any statement, paragraph, (sub) item, point, action, behavior, term, alternative, aspect, example or claim described in this disclosure can be independently and separately implemented to form a specific method. The dependency in this disclosure (e.g., "based on", "more specifically", "in some specific implementations", "in an alternative", "in an example", "in an aspect", etc.) is only a possible example in which a specific method will not be limited. For example, one aspect of this disclosure can be used for communication, communication equipment (e.g., mobile phone devices, advertising base station devices, wireless LAN devices and / or sensor devices, etc.) and integrated circuits (e.g., communication chips) and / or programs, etc. According to any statement, paragraph, (sub) item, point, action, behavior, term, alternative, aspect, example, specific implementation or claim described in this disclosure, "X / Y" may include the meaning of "X or Y". According to any sentence, paragraph, (sub)item, point, action, behavior, term, alternative, aspect, example, specific implementation or claim described in this disclosure, "X / Y" may also include the meaning of "X and Y". According to any sentence, paragraph, (sub)item, point, action, behavior, term, alternative, aspect, example, specific implementation or claim described in this disclosure, "X / Y" may also include the meaning of "X and / or Y".

[0018] In addition, for the purpose of explanation rather than limitation, specific details such as functional entities, technologies, protocols, standards, etc. are set forth to provide an understanding of the described technology. In other examples, detailed descriptions of well-known methods, technologies, systems, architectures, etc. are omitted to avoid obscuring the description with unnecessary details.

[0019] Those skilled in the art will immediately recognize that any network function or algorithm described in this disclosure may be implemented by hardware, software, or a combination of software and hardware. The functions described may correspond to modules that may be software, hardware, firmware, or any combination thereof. Software implementations may include computer executable instructions stored on a computer-readable medium such as a memory or other type of storage device. For example, one or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and perform the described network functions or algorithms. A microprocessor or general-purpose computer may be formed by an application specific integrated circuit (ASIC), a programmable logic array, and / or formed using one or more digital signal processors (DSPs). Although some example implementations described in this specification are for software installed and executed on computer hardware, alternative example implementations implemented as firmware or hardware or a combination of hardware and software are also within the scope of this disclosure.

[0020] Computer readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disk read-only memory (CD-ROM), magnetic tape cassettes, magnetic tapes, magnetic disk storage devices, or any other equivalent medium capable of storing computer readable instructions.

[0021] Figure 1 is a schematic diagram illustrating a radio communication network architecture according to an exemplary embodiment of the present disclosure. Figure 1 , a radio communication network architecture (e.g., a long term evolution (LTE) system, an advanced LTE (LTE-A) system, an advanced LTE Pro system, or a 5G NR radio access network (RAN)) typically includes at least one base station 110, at least one UE 120, and one or more optional network elements that provide a connection toward the network. The UE 120 communicates with a network (e.g., a core network (CN), an evolved packet core (EPC) network, an evolved universal terrestrial radio access network (E-UTRAN), a 5G core (5GC), or the Internet) through a RAN established by one or more base stations.

[0022] It should be noted that in the present disclosure, UE 120 may include but is not limited to a mobile station, a mobile terminal or device, a user communication radio terminal. For example, UE 120 may be a portable radio equipment, which includes but is not limited to a mobile phone, a tablet computer, a wearable device, a sensor, a vehicle, or a personal digital assistant (PDA) with wireless communication capabilities. UE 120 is configured to receive and send signals over an air interface relative to one or more cells in a radio access network.

[0023] The base station 110 may be configured to provide communication services according to at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile Communications (GSM, commonly referred to as 2G), GSM Enhanced Data Rates for GSM Evolution (EDGE), Radio Access Network (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS, commonly referred to as 3G) based on basic Wideband Code Division Multiple Access (W-CDMA), High Speed ​​Packet Access (HSPA), LTE, LTE-A, eLTE (Evolved LTE, e.g., LTE connected to 5GC), NR (commonly referred to as 5G) and / or LTE-A Pro. However, the scope of the present disclosure should not be limited to the above-mentioned protocols.

[0024] The base station 110 may include, but is not limited to, a node B (NB) such as in UMTS, an evolved node B (eNB) such as in LTE or LTE-A, a radio network controller (RNC) such as in UMTS, a base station controller (BSC) such as in a GSM / GSM enhanced data rate for GSM evolution (EDGE) radio access network (GERAN), a next generation eNB (ng-eNB) in an evolved universal terrestrial radio access (E-UTRA) BS related to 5GC, a next generation node B (gNB) such as in a 5G access network (5G-AN), and any other device capable of controlling radio communications and managing radio resources within a cell. The BS 110 may be connected to a radio interface to a network to serve one or more UEs 120.

[0025] Base station 110 (or referred to as network equipment) is operable to provide radio coverage to a specific geographic area using multiple cells included in the RAN. BS110 can support the operation of cells. Each cell is operable to provide services to at least one UE within its radio coverage. Specifically, each cell (usually referred to as a serving cell) can provide services to serve one or more UEs 120 within its radio coverage (e.g., each cell schedules downlink (DL) and optional uplink (UL) resources to at least one UE 120 within its radio coverage for DL ​​and optional UL packet transmission). BS110 can communicate with one or more UEs 120 in a radio communication system through multiple cells.

[0026] The base station 110 may include a network node 111 and one or more TRPs 112 and 113.

[0027] The network node 111 may be, but is not limited to, a Node B (NB) as in LTE, an evolved Node B (eNB) as in LTE-A, a Radio Network Controller (RNC) as in UMTS, a Base Station Controller (BSC) as in GSM / GERAN, a New Radio Evolved Node B (NReNB) as in NR, a Next Generation Node B (gNB) as in NR, and any other device capable of controlling radio communications and managing radio resources within one or more cells.

[0028] The TRP (e.g., HF-TRP or LF-TRP) 112 or 113, which may also be considered as a remote radio head (RRH), may be a transceiver under the protocol of the 5G NR wireless communication system and / or the protocol of the 4G wireless communication system. The TRP 112 or 113 may be communicatively connected to the network node 111. The network node 111 may be connected to serve one or more UEs 120 through one or more TRPs 112 and 113 in the radio communication system.

[0029] The cell may allocate side link (SL) resources for supporting proximity services (ProSe) or vehicle to everything (V2X) services. Each cell may have a coverage area that overlaps with other cells. In the case of multi-RAT dual connectivity (MR-DC), the main cell of the main cell group (MCG) or the secondary cell group (SCG) may be referred to as a special cell (SpCell). The main cell (PCell) may refer to the SpCell of the MCG. The primary SCG cell (PSCell) may refer to the SpCell of the SCG. MCG may refer to a group of service cells associated with a master node (MN), including SpCell and optionally one or more secondary cells (SCell). SCG may refer to a group of service cells associated with a secondary node (SN), including SpCell and optionally one or more SCells.

[0030] As discussed above, the frame structure of NR will support flexible configuration to accommodate various next-generation (e.g., 5G) communication requirements, such as enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low latency communication (URLLC), while meeting high reliability, high data rate, and low latency requirements. The orthogonal frequency division multiplexing (OFDM) technology agreed upon in 3GPP can be used as a baseline for the NR waveform. Scalable OFDM parameter sets, such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP) can also be used. In addition, two decoding schemes are considered for NR: (1) low-density parity check (LDPC) code and (2) polar code. The decoding scheme adaptation can be configured based on channel conditions and / or service applications.

[0031] In addition, it is also considered that in the transmission time interval TX of a single NR frame, at least downlink (DL) transmission data, protection period and uplink (UL) transmission data should be included, wherein the corresponding parts of DL transmission data, protection period and UL transmission data should also be configurable, for example, based on the network dynamics of NR. In addition, sidelink resources can also be provided in the NR frame to support ProSe services, (E-UTRA / NR) sidelink services or (E-UTRA / NR) V2X services.

[0032] In addition, the terms "system", "network" and "network device" in this document are used interchangeably. The term "and / or" in this document is only used to describe the association relationship of associated objects, and indicates that three relationships may exist. For example, A and / or B may indicate: A exists alone, A and B exist at the same time, or B exists alone. In addition, the character " / " in this document generally indicates that the previous and next associated objects are in an "or" relationship.

[0033] As discussed above, it is envisioned that the next generation (e.g., 5G NR) wireless networks support more capacity, data, and services. A UE configured with multiple connections may be connected to a master node (MN) as an anchor and one or more secondary nodes (SN) for data delivery. Each of these nodes may be formed by a cell group including one or more cells. For example, a master cell group (MCG) may be formed by a MN, and a secondary cell group (SCG) may be formed by a SN. In other words, for a UE configured with dual connectivity (DC), an MCG is a set of one or more serving cells including a PCell and zero or more secondary cells. In contrast, an SCG is a set of one or more serving cells including a PSCell and zero or more secondary cells.

[0034] As also described above, the primary cell (PCell) may be an MCG cell operating on the primary frequency, in which the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. In MR-DC mode, the PCell may belong to the MN. The primary SCG cell (PSCell) may be an SCG cell in which the UE performs random access (for example, when reconfiguration is performed through a synchronization process). In MR-DC, the PSCell may belong to the SN. The special cell (SpCell) may refer to the PCell of the MCG or the PSCell of the SCG, depending on whether the MAC entity is associated with the MCG or the SCG. Otherwise, the term special cell may refer to the PCell. The special cell may support physical uplink control channel (PUCCH) transmission and contention-based random access (CBRA), and may always be activated. In addition, for a UE in the RRC_CONNECTED state that is not configured with CA / DC, it may communicate only with one serving cell (SCell), which may be the primary cell. In contrast, for a UE in RRC_CONNECTED state configured with CA / DC, a set of serving cells including the special cell and all secondary cells may communicate with the UE.

[0035] In the present disclosure, network (NW), network equipment, network node, cell, resident cell, serving cell, base station, gNB, eNB and ng-eNB may be used interchangeably. In some implementations, some of these items may refer to the same network entity.

[0036] The RAT may be (but not limited to) NR, LTE, E-UTRA connected to 5GC, LTE connected to 5GC, E-UTRA connected to EPC, and LTE connected to EPC. The proposed mechanism may be applied to UEs in a public network or a private network (e.g., NPN (non-public network, SNPN (standalone NPN), PNI-NPN (public network integrated NPN)).

[0037] The proposed mechanism can be used for licensed frequencies and / or unlicensed frequencies.

[0038] System information (SI) may refer to MIB, SIB1 and other SI. Minimum SI may include MIB and SIB1. Other SI may refer to SIB3, SIB4, SIB5 and other SIBs.

[0039] Dedicated signaling may refer to (but is not limited to) RRC messages. For example, RRC (connection) establishment request message, RRC (connection) establishment message, RRC (connection) establishment complete message, RRC (connection) reconfiguration message, RRC connection reconfiguration message including mobility control information, RRC connection reconfiguration message without internal mobility control information, RRC reconfiguration message including configuration with synchronization, RRC reconfiguration message without internal configuration with synchronization, RRC (connection) reconfiguration complete message, RRC (connection) recovery request message, RRC (connection) recovery message, RRC (connection) recovery complete message, RRC (connection) reestablishment request message, RRC (connection) reestablishment message, RRC (connection) repair complete message, RRC (connection) rejection message, RRC (connection) release message, RRC system information request message, UE assistance information message, UE capability inquiry message and UE capability information message.

[0040] RRC_CONNECTED UE, RRC_INACTIVE UE and RRC_IDLE UE can apply the proposed implementation.

[0041] An RRC_CONNECTED UE may be configured with an active BWP with a common search space configured to monitor system information or paging. An RRC_CONNECTED UE configured with ICBM may be configured with an active BWP on the serving cell with a common search space configured to monitor system information or paging from the serving cell. An RRC_CONNECTED UE configured with ICBM may be configured with an active BWP on the target cell with a common search space configured to monitor system information or paging from the target cell.

[0042] The UE may be served by a cell (eg, a serving cell). The serving cell may serve (but is not limited to) an RRC_CONNECTED UE. The serving cell may be (but is not limited to) a suitable cell.

[0043] The UE may camp on a cell, such as a camped cell. The camped cell may be a suitable cell or an acceptable cell.

[0044] A suitable cell is a cell that the UE can camp on. The UE may consider a cell to be suitable if the following conditions are met: (1) the cell is part of the selected PLMN or the registered PLMN or a PLMN in the equivalent PLMN list, and (2) the cell criteria for the cell are met. In addition, according to the latest information provided by the NAS, the suitable cell is not prohibited. A suitable cell is part of at least one TA that is not part of the list of "prohibited tracking areas" and belongs to a PLMN that meets condition (1). The target cell may be a suitable cell.

[0045] An acceptable cell is a cell on which the UE can camp to obtain limited service (initiate emergency calls and receive ETWS and CMAS notifications). Such a cell may meet the following requirements, which are the minimum set of requirements for initiating emergency calls and receiving ETWS and CMAS notifications in an NR network: (1) the cell is not barred, and / or (2) the cell selection criteria are met.

[0046] DL BWP may refer to initial (DL) BWP, default BWP, active (DL) BWP.

[0047] PCell (primary cell): MCG cell, operating on the primary frequency, where the UE performs an initial connection establishment procedure or initiates a connection re-establishment procedure.

[0048] PSCell (Primary SCG Cell): For dual connectivity operation, the SCG cell in which the UE performs random access when reconfiguration is performed using a synchronization procedure.

[0049] Serving cell: For a UE in RRC_CONNECTED without CA / DC configured, there is only one serving cell consisting of the primary cell. For a UE in RRC_CONNECTED configured with CA / DC, the term "serving cell" is used to refer to the set of cells consisting of the special cell and all secondary cells.

[0050] Secondary cell: A cell that provides additional radio resources in addition to the special cell for UEs configured with CA.

[0051] Special cell: For dual connectivity operation, the term special cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term special cell refers to the PCell.

[0052] Primary cell group: In MR-DC, a group of service cells associated with the primary node, consisting of SpCell (PCell) and optionally one or more SCells.

[0053] Master Node: In MR-DC, the radio access node that provides the control plane connection to the core network. It can be a master eNB (in EN-DC), a master ng-eNB (in NGEN-DC), or a master gNB (in NR-DC and NE-DC).

[0054] Secondary cell group: In MR-DC, a group of serving cells associated with a secondary node, consisting of a SpCell (PSCell) and optionally one or more SCells.

[0055] Secondary Node: In MR-DC, a radio access node without a control plane connection to the core network, providing additional resources to the UE. It can be an en-gNB (in EN-DC), secondary ng-eNB (in NE-DC) or secondary gNB (in NR-DC and NGEN-DC).

[0056] The CSS may be a Type0-PDCCH CSS and / or a Type0A-PDCCH CSS.

[0057] The required SI of the UE may be interpreted as the required on-demand SI of the UE.

[0058] SI on demand may refer to system information (eg, other SI) that a UE requests from a network. SI on demand may include an SI message, a SIB, and / or a SIB segment.

[0059] In the present disclosure, the terms "serving cell", "TRP associated with the PCI of the serving cell" and "TRP associated with the serving cell" are used interchangeably.

[0060] In the present disclosure, the terms "target cell", "another cell", "TRP associated with a PCI different from the PCI of the serving cell", "TRP associated with the PCI of the target cell different from the PCI of the serving cell", "TRP associated with the PCI of another cell different from the PCI of the serving cell", "TRP associated with the PCI of the macro cell" and "TRP associated with the target cell" may be used interchangeably.

[0061] In a specific implementation, the serving cell may be a PCell, a SCell or a PSCell.

[0062] In a specific implementation, the target cell may be a PCell, a SCell or a PSCell.

[0063] The cell area relative to the serving cell of the UE may be a neighboring cell, a cell other than the serving cell, an additional cell, another cell, or a cell having a PCI different from that of the serving cell. Figure 1For example, TRP1 112 serves UE 120 within the coverage of serving cell 115, and TRP2 113 serves UE 120 within the coverage of another cell 116. Another cell 116 is an inter-cell with respect to serving cell 115 of UE 120. If the UE can perform inter-cell beam management, the UE can be in inter-cell coverage. TRP1 112 is associated with serving cell 115, and TRP2 113 is associated with another cell 116. TRP1 112 is associated with the PCI of serving cell 115, and TRP2 113 is associated with the PCI of another cell 116.

[0064] It should be noted that in some implementations, if the UE is configured with inter-cell beam management, the UE is not required to acquire SI from the serving cell while the UE is receiving (or may receive) DL-SCH from a TRP associated with a PCI different from the PCI of the serving cell. As presented in the implementation of the present disclosure, it is possible that the UE may acquire the SI of the serving cell from a TRP associated with a PCI different from the PCI of the serving cell.

[0065] It should be noted that in some specific implementations, when the UE does not receive (or does not receive) DL-SCH from a TRP associated with a PCI that is different from the PCI of the serving cell, the UE may request the required system information of the target cell by sending an RRC message.

[0066] The term "MAC layer" and the term "MAC entity" are used interchangeably.

[0067] It should be noted that the system information may be associated with a serving cell and / or the system information may be associated with a target cell.

[0068] It should be noted that when the UE is performing inter-cell beam management, it is basic but important for the UE to receive system information associated with the serving cell or associated with the inter-cell of the serving cell. However, it is not clear how to implement the sending and receiving of system information when the UE is configured with inter-cell beam management and / or when the UE is in mTRP operation. In the present disclosure, a mechanism for implementing the sending and receiving of system information is proposed, especially when the UE is configured with inter-cell beam management and / or when the UE is in mTRP operation, but not limited to this. The mechanism includes a method in which the UE is configured to receive and send in mTRP operation and / or a method in which the UE is configured to send and receive when the UE operates in inter-cell beam management. The energy-saving mechanism achieves a reduction in signaling overhead. The mechanism establishes the basis for inter-cell beam management and inter-cell mobility.

[0069] Several scenarios are possible.

[0070] mTRP Operation:

[0071] In one implementation, if multi-TRP (mTRP) operation is applied, the serving cell (or network node 111) may schedule traffic from two TRPs (eg, Figure 1 Multi-TRP operation is proposed and designed to provide wider coverage, enhance reliability, and improve the data rate of transmission / reception of downlink channels (e.g., PDSCH, PDCCH), downlink reference signals (e.g., channel state information-reference signal (CSI-RS), demodulation reference signal (DMRS), SSB, phase tracking reference signal (PT-RS), tracking reference signal (TRS)), uplink channels (e.g., physical uplink shared channel (PUSCH), physical uplink control channel (PUCCH)), and uplink reference signals (e.g., SRS).

[0072] In one specific implementation, if mTRP PUCCH repetition is applied, a UE in TRP operation may perform PUCCH transmission of the same content (or transport block (TB)) toward two TRPs with corresponding beam directions associated with different spatial relationship information. It should be noted that the spatial relationship information may include parameters for configuring the spatial relationship between a reference signal (e.g., SRS, CSI-RS, or SSB) and a target reference signal set. For example, the target reference signal set may be a DM-RS port of a PUSCH or a PUCCH. In addition, the spatial relationship information may also include parameters for configuring power control for the PUCCH or the PUSCH.

[0073] In the single-cell case, the two TRPs may be associated with the PCI (Physical Cell Identity (ID)) of the serving cell.

[0074] In the inter-cell case, the two TRPs can be associated with different PCIs. Figure 1 For example, one TRP1 112 may be associated with a PCI of a serving cell 115 , while another TRP2 113 may be associated with a PCI of another cell 116 that is different from the PCI of the serving cell 115 .

[0075] In one specific implementation, if mTRP PUSCH repetition is applied, then based on an indication in a single DCI received by the UE from a serving cell (or from a TRP associated with a serving cell) and / or an indication in a semi-statically configured grant provided on an RRC message received by the UE from the serving cell (or from a TRP associated with a serving cell), the UE may perform a set of PUSCH transmissions of the same content (or transport blocks) toward two TRPs with corresponding beam directions associated with different spatial relationship information in the time domain.

[0076] In the single-cell case, the two TRPs may be associated with the PCI of the serving cell. In the inter-cell case, the two TRPs may be associated with different PCIs. For example, one TRP may be associated with the PCI of the serving cell, while the other TRP may be associated with a PCI different from the PCI of the serving cell.

[0077] In one specific implementation, for the inter-cell case, it is possible that the UE may receive an indication from the serving cell (or from a TRP associated with the serving cell) or from a TRP associated with a PCI different from the PCI of the serving cell in a single DCI. In one specific implementation, for the inter-cell case, it is possible that the UE may receive an indication from the serving cell (or from a TRP associated with the serving cell) or from a TRP associated with a PCI different from the PCI of the serving cell in a semi-statically configured grant via an RRC message.

[0078] In one specific implementation, if mTRP PDCCH transmission is applied, a UE in mTRP operation may receive two PDCCH transmissions carrying the same DCI, one PDCCH transmission for each TRP. There are two modes for mTRP PDCCH transmission: PDCCH repetition mode and single frequency network (SFN) based PDCCH transmission mode. In PDCCH repetition mode, the UE may receive two PDCCH transmissions carrying the same DCI format from two linked search space sets within a time slot, where each search space set is associated with a corresponding CORESET. In SFN based PDCCH transmission mode, the UE may receive a PDCCH transmission carrying DCI in a given search space set from a CORESET with two TCI states. In one specific implementation, in SFN based PDCCH transmission mode, the UE may receive two PDCCH transmissions carrying the same DCI from a single search space / CORESET using different TCI states.

[0079] In one specific implementation, in the case of a single cell, for a PDCCH repetition mode or other transmission mode, two linked search spaces and associated different CORESETs (or CORESET pools indicated by the value of the CORESET pool index) are associated with a serving cell. In one specific implementation, in the case of an inter-cell, for a PDCCH repetition mode or other transmission mode, one of the two linked search spaces and the associated CORESET (or CORESET pool indicated by the value of the CORESET pool index) may be associated with a serving cell (or may belong to a serving cell), while the other of the two linked search spaces and the associated CORESET (or CORESET pool indicated by the value of the CORESET pool index) may be associated with a TRP associated with a PCI different from the PCI of the serving cell (or may belong to a TRP). In addition, the value of the CORESET pool index may also be the value of the parameter CORESETPoolIndex.

[0080] In one specific implementation, in a single-cell case, for an SFN-based PDCCH transmission mode, a single search space (or a single CORESET or CORESET pool or CORESETPoolIndex) and a corresponding TCI state may be associated with a serving cell (or may belong to a serving cell). In one specific implementation, in an inter-cell case, for an SFN-based PDCCH transmission mode, a single search space (or a single CORESET or CORESET pool or CORESETPoolIndex) and a corresponding TCI state may be associated with a TRP associated with a PCI different from the PCI of the serving cell (or may belong to the TRP). For example, in the presence of two corresponding TCI states, one of the corresponding TCI states may be associated with a TRP associated with a PCI different from the PCI of the serving cell (or may belong to the TRP), and the other of the corresponding TCI states may be associated with the serving cell (or may belong to the serving cell). In general, some of the corresponding TCI states may be associated with (or may belong to) a TRP associated with a PCI different from the PCI of the serving cell, and some of the corresponding TCI states may be associated with (or may belong to) the serving cell. It should be noted that the UE may receive configuration of the corresponding TCI state from the serving cell or from a TRP associated with a PCI different from the PCI of the serving cell.

[0081] In one specific implementation, if mTRP PDSCH transmission is applied, then the UE in mTRP operation may receive PDSCH transmissions from two TRPs. If the two TRPs are associated with the serving cell of the UE, then it is a case of single-cell mTRP PDSCH transmission. If the two TRPs are associated with different serving cells of the UE, then it is a case of inter-cell mTRP PDSCH transmission.

[0082] Single-cell mTRP PDSCH transmission:

[0083] In one specific implementation, the control of UL and DL is performed by the PHY layer and MAC entity (of the UE and / or serving cell) within the configuration provided by the RRC layer (of the UE and / or serving cell). For example, the UE may receive an RRC message including a configuration for single-cell mTRP PDSCH transmission from the serving cell, and then the UE may configure itself using the configuration for single-cell mTRP PDSCH transmission. The UE may also apply the configuration to single-cell mTRP PDSCH transmission. Thereafter, the UE may receive a MAC CE and / or DCI from the serving cell to activate / deactivate / apply a configuration for indicating TRP-related information for single-cell mTRP PDSCH transmission.

[0084] In one specific implementation, there are two different operating modes in the case of single-cell mTRP PDSCH transmission: single DCI mode and multi-DCI mode. For single DCI mode, the UE is scheduled by the same DCI for two TRPs, for example, to receive mTRP PDSCH transmissions from different TRPs. The content of the PDSCH transmissions from the two TRPs scheduled by the same DCI is the same. For multi-DCI mode, the UE is scheduled by independent DCI from different CORESET pools (for example, indicated by different values ​​of the CORESET pool index) for each corresponding TRP to receive mTRP PDSCH transmissions. For example, one DCI is associated with one CORESET pool index corresponding to one value of the CORESET pool index, and another DCI is associated with another CORESET pool index corresponding to another value of the CORESET pool index. The content of the PDSCH transmissions from each TRP scheduled by each corresponding separate DCI (for example, the TBs carried by the PDSCH) may be different.

[0085] Inter-cell mTRP PDSCH transmission:

[0086] In one specific implementation, for inter-cell mTRP PDSCH transmission, multi-DCI PDSCH transmission may be applied. One or more TCI states may be associated with an SSB having a PCI different from the PCI of the serving cell. However, an activated TCI state may be associated with at most one PCI different from the PCI of the serving cell at a time. That is, in SSBs associated with corresponding PCIs different from the PCI of the serving cell, one or more TCI states may be configured to be associated with these SSBs. However, those configured TCI states associated with SSBs may be activated at one time, where the SSB is associated with at most one PCI different from the PCI of the serving cell.

[0087] For example, Figure 2 is a schematic diagram illustrating association in inter-cell beam management according to one of the exemplary embodiments of the present disclosure. Figure 2 As shown in , cell #1 is the serving cell of the UE, while cell #2 and cell #3 are inter-cells relative to the UE. Each cell has a corresponding PCI, for example, the PCI of the serving cell (cell #1) is PCI #1, the PCI of cell #2 is PCI #2, and the PCI of cell #3 is PCI #3. Each cell may have several SSBs. For example, cell #2 has SSB #21 and SSB #22, but is not limited thereto; and cell #3 has SSB #31 and SSB #32, but is not limited thereto. It should be noted that Figure 2 The SSB box illustrated in (e.g., SSB#21) may include one or more SSBs, i.e., a set of SSBs. Each SSB box (e.g., SSB#21) may be configured with a set of TCI states by the NW via an RRC message to the UE. For example, SSB#21 may be configured to be associated with TCI state #211, TCI state #212, TCI state #213, TCI state #221, TCI state #222, TCI state #223, but not limited thereto. Similarly, the NW may send an RRC message including a TCI state configuration associated with a set of SSBs belonging to cell #3, for example, SSB#31 may be configured to be associated with TCI state #311, TCI state #312, TCI state #313, but not limited thereto. However, although the UE receives an RRC message including a TCI configuration associated with an SSB belonging to an inter-cell (or a neighboring cell or a cell other than the serving cell or an additional cell or another cell), the NW (or the UE) may activate a TCI state associated with at most one PCI different from the PCI of the serving cell at one time. For example, Figure 2 As shown, only the configured TCI state associated with the SSB belonging to the cell #2 having PCI #2 is activated, while the configured TCI state associated with the SSB belonging to the cell #3 having PCI #3 may not be activated.

[0088] Configuration in inter-cell mTRP operation:

[0089] Figure 3 is a flow chart of a method applicable to a UE according to an exemplary embodiment of the present disclosure. Figure 3 It should be noted that the order of the steps in the figure can be changed according to actual requirements.

[0090] Step S310: The UE receives a radio resource control (RRC) message from a serving cell. The RRC message includes first information of at least one of a transmission configuration indicator (TCI) configuration, a reference signal (RS) configuration associated with the TCI configuration, and a first value of a control resource set (CORESET) pool index, and the first information is associated with another cell having a second physical cell identifier (PCI) different from the first PCI of the serving cell.

[0091] Step S320: The UE applies at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

[0092] Step S330: The UE performs transmission or reception with another cell according to the applied configuration from at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

[0093] In one specific implementation, in addition to SSB, other reference signals such as CSI-RS, DMRS, tracking reference signal (TRS) and phase tracking reference signal (PT-RS) may be applied and configured for inter-cell beam management including inter-cell mTRP PDSCH transmission, inter-cell mTRP PDCCH transmission, inter-cell mTRP PUCCH transmission and inter-cell mTRP PUSCH transmission.

[0094] For example, the UE may receive an RRC message from a serving cell. The RRC message may include information about a TCI configuration, information about a spatial relationship configuration, information about a reference signal configuration associated with the TCI configuration, and / or information about a reference signal configuration associated with the spatial relationship configuration. The information about the TCI configuration, the information about the spatial relationship configuration, the information about the RS configuration associated with the TCI configuration, and / or the information about the RS configuration associated with the spatial relationship configuration may be associated with the serving cell. However, it is possible that the information about the TCI configuration, the information about the spatial relationship configuration, the information about the RS configuration associated with the TCI configuration, and / or the information about the RS configuration associated with the spatial relationship configuration may be associated with a TRP associated with a second PCI of another cell different from the first PCI of the serving cell.

[0095] In one specific implementation, the RRC message may also include second information of at least one of a second TCI configuration, a second RS configuration associated with the second TCI configuration, and a second value of the CORESET pool index, and the second information is associated with the serving cell.

[0096] In one specific implementation, the first value of the CORESET pool index in the first information is different from the second value of the CORESET pool index in the second information. The CORESET pool can be identified by the value of the CORESET pool index. The CORESET pool can include at least one CORESET.

[0097] In one implementation, a first value of the CORESET pool index is associated with a TCI configuration. In one implementation, a second value of the CORESET pool index is associated with a TCI configuration. For example, the first value of the CORESET pool index is associated with a first TCI configuration for an inter-cell (or an additional cell or a neighboring cell or another cell) other than the serving cell, and the second value of the CORESET pool index is associated with a second TCI configuration for the serving cell.

[0098] In one implementation, the TCI configuration may be a downlink TCI configuration (e.g., a list of TCI states configured for downlink reception), an uplink TCI configuration (e.g., a list of TCI states configured for uplink transmission), and / or a joint TCI configuration (e.g., a list of TCI states configured for both downlink reception and uplink transmission). In one implementation, downlink reception may include reception of a signal on a DL channel (e.g., PDSCH or PDCCH) and / or reception of a DL reference signal (e.g., DMRS, SSB). In one implementation, uplink transmission may include transmission of a signal on a UL channel (e.g., PUSCH or PUCCH) and / or transmission of a UL reference signal (e.g., SRS).

[0099] In a specific implementation, the information of the reference signal configured with the TCI configuration may be the information of the reference signal configured with the downlink TCI configuration, the uplink TCI configuration and / or the joint TCI configuration.

[0100] In one specific implementation, the UE may add a TCI configuration in response to receiving information of a TCI configuration including a TCI configuration to be added. In one specific implementation, the UE may modify the TCI configuration in response to receiving information of a TCI configuration including a TCI configuration to be modified. That is, if the information of the TCI configuration includes a TCI configuration to be added and / or modified, the UE may add and / or modify the indicated TCI configuration to the stored TCI configuration. In one specific implementation, the UE may store the TCI configuration in response to adding and / or modifying the TCI configuration. After adding and / or modifying, the UE may store the updated TCI configuration. In one specific implementation, the UE may release the TCI configuration in response to receiving information of a TCI configuration including a TCI configuration to be released. That is, if the information of the TCI configuration includes a TCI configuration to be released, the UE may release the indicated TCI configuration from the stored TCI configuration. In one specific implementation, in response to releasing the TCI configuration, the UE may store the remaining (or updated) TCI configuration. After releasing, the UE may store the updated TCI configuration.

[0101] In one example, the UE has stored TCI configurations according to a previous RRC message carrying information of TCI configurations (e.g., TCI states to be released, TCI states to be modified, and TCI states to be added). If the UE receives a new RRC message carrying TCI configuration information, the UE may release one or more stored TCI states according to the TCI states indicated by the new RRC message as being released, modify one or more stored TCI states according to the TCI states indicated by the new RRC message as being modified, and add one or more TCI states according to the TCI states indicated by the new RRC message as being added.

[0102] In a specific implementation, if the information of the spatial relationship configuration includes a spatial relationship configuration to be added and / or modified, the UE may add and / or modify the indicated spatial relationship configuration to the stored spatial relationship configuration. After adding and / or modifying, the UE may store the updated spatial relationship configuration. If the information of the spatial relationship configuration includes a spatial relationship configuration to be released, the UE may release the indicated spatial relationship configuration from the stored spatial relationship configuration. After releasing, the UE may store the updated spatial relationship configuration.

[0103] In one example, the UE has stored spatial relationship information according to a previous RRC message carrying information of spatial relationship settings (e.g., spatial relationship settings to be released, spatial relationship settings to be modified, and spatial relationship settings to be added). If the UE receives a new RRC message carrying information of the spatial relationship settings, the UE may release one or more stored spatial relationship information according to the spatial relationship settings indicated by the new RRC message as to be released, modify one or more stored spatial relationship information according to the spatial relationship settings indicated by the new RRC message as to be modified, and add one or more spatial relationship information according to the spatial relationship settings indicated by the new RRC message as to be added.

[0104] In a specific implementation, if the information of the RS configuration (e.g., the information of the RS configuration associated with the spatial relationship configuration, the information of the RS configuration associated with the TCI configuration) includes the RS configuration to be added and / or modified, the UE may add and / or modify the indicated RS configuration to the stored RS configuration. After adding and / or modifying, the UE may store the updated RS configuration. If the information of the RS configuration includes the RS configuration to be released, the UE may release the indicated RS configuration from the stored RS configuration. After releasing, the UE may store the updated RS configuration.

[0105] In one specific implementation, it is possible that the UE may maintain (eg, update, add, modify, and release) the RS configuration associated with the spatial relationship configuration and the RS configuration associated with the TCI configuration, respectively.

[0106] In one specific implementation, the UE may apply the updated TCI configuration and / or the associated updated RS configuration after adding, modifying and / or releasing. However, in one specific implementation, it is possible that the UE may only store the updated TCI configuration and / or the associated updated RS configuration after adding, modifying and / or releasing, but has not yet applied them. In this case, when the UE receives a DCI and / or MAC CE to activate the updated TCI configuration and / or the associated updated RS configuration, the UE may start applying the (stored) updated TCI configuration and / or the associated (stored) updated RS configuration. When the UE receives a DCI and / or MAC CE to deactivate the activated TCI configuration and / or the associated activated RS configuration, the UE may deactivate the TCI configuration and / or the associated RS configuration, where the TCI configuration and / or the associated RS configuration may be indicated in the DCI and / or MAC CE.

[0107] In one example, the TCI configuration and / or the associated RS configuration may be updated by an RRC message, for example, after the UE receives the RRC message, the UE may add, modify and / or release the stored TCI state on the UE side. And the updated TCI configuration and / or the associated RS configuration (i.e., the TCI configuration and / or the associated RS configuration updated by the RRC message) may be activated / deactivated by DCI and / or MAC CE. For example, the MAC CE may activate one or more TCI states included in the updated TCI configuration, and then the UE may apply the activated TCI state to downlink channel reception and / or uplink channel transmission. For another example, the MAC CE may activate one or more TCI states included in the updated TCI configuration, and the DCI may indicate which activated TCI states included in the MAC CE will be applied to downlink channel reception and / or uplink channel transmission. If (only) one TCI state is activated by the MAC CE (e.g., in the case of a single TRP), the UE may directly apply the TCI state to downlink channel reception and uplink channel transmission without the TCI state indication in the DCI. If (only) two TCI states are activated by the MAC CE (eg, in the case of mTRP or in the case of SFN), the UE may directly apply the two TCI states to downlink channel reception and uplink channel transmission without TCI state indication in the DCI.

[0108] In one specific implementation, the UE may apply the updated spatial relationship configuration and / or the associated updated RS configuration after adding, modifying and / or releasing. However, in one specific implementation, it is possible that the UE may only store the updated spatial relationship configuration and / or the associated updated RS configuration after adding, modifying and / or releasing, but has not yet applied them. In this case, when the UE receives a DCI and / or MAC CE to activate the updated spatial relationship configuration and / or the associated updated RS configuration, the UE may start applying the activated updated spatial relationship configuration and / or the associated updated RS configuration. When the UE receives a DCI and / or MAC CE to deactivate the activated spatial relationship configuration and / or the associated activated RS configuration, the UE may deactivate the spatial relationship configuration and / or the associated RS configuration, where the spatial relationship configuration and / or the associated RS configuration may be indicated in the DCI and / or MAC CE.

[0109] In one specific implementation, the reference signal configuration may include a configuration of at least one of a set of SSBs, a set of CSI-RSs, a set of DMRSs, a set of TRSs, and a set of PT-RSs. In one specific implementation, the reference signal configuration may include a list of SSBs to be added and / or modified, a list of CSI-RSs, a list of DMRSs, a list of TRSs, and a list of PT-RSs. In one specific implementation, the reference signal configuration may include a list of SSBs to be released, a list of CSI-RSs, a list of DMRSs, a list of TRSs, and a list of PT-RSs. SSBs may be identified by SSB indexes. CSI-RSs may be identified by CSI-RS indexes. DMRSs may be identified by DMRS indexes. TRSs may be identified by TRS indexes. PT-RSs may be identified by PT-RS indexes.

[0110] In one specific implementation, the TCI configuration may include a list of TCI states to be added and / or modified and a list of TCI states to be released. The TCI state may be identified by a TCI state index. It should be noted that the list of TCI states may be a list of DL TCI states, a UL TCI state, a list of joint TCI states, and / or a list of TCI states for indicating joint TCI states for different TRPs.

[0111] In one implementation, the spatial relationship configuration may include a list of spatial relationships to be added and / or modified and a list of spatial relationships to be released. The spatial relationships may be identified by an index of the spatial relationship and / or by an indicated joint TCI state or UL TCI state.

[0112] In one implementation, the UE may receive the RRC message when the UE is in the RRC_CONNECTED state. However, in one implementation, it is possible that the UE may receive the RRC message when the UE is in the RRC_INACTIVE state.

[0113] In one implementation, the UE may receive the RRC message from the serving cell. However, in one implementation, it is possible that the UE may receive the RRC message from a TRP associated with a PCI of another cell different from the PCI of the serving cell.

[0114] In one specific implementation, once the UE applies a TCI configuration, an RS configuration associated with the TCI configuration, a spatial relationship configuration, a value of a CORESET pool index, and / or an RS configuration associated with the spatial relationship configuration, wherein the TCI configuration, the RS configuration associated with the TCI configuration, the spatial relationship configuration, the value of the CORESET pool index, and / or the RS configuration associated with the spatial relationship configuration are associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell, the UE may perform inter-cell PDSCH reception to receive a PDSCH transmission from a TRP associated with a PCI of another cell different from the PCI of the serving cell, and perform inter-cell PDCCH reception to receive a PDSCH transmission from a TRP associated with a PCI of another cell different from the PCI of the serving cell. Receive PDCCH transmission to a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell downlink reference signal reception from a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell PUSCH transmission to send PUSCH to a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell PUCCH transmission to send PUCCH to a TRP associated with a PCI of another cell different from the PCI of the serving cell, and / or perform inter-cell uplink reference signal transmission to a TRP associated with a PCI of another cell different from the PCI of the serving cell. It should be noted that the TCI configuration can be a downlink TCI configuration (e.g., a list of TCI states configured for downlink channels), an uplink TCI configuration (e.g., a list of TCI states configured for uplink channels), and / or a joint TCI configuration (e.g., a list of TCI states configured for both downlink channels and uplink channels). Similarly, the information of the reference signal configured with the TCI configuration may be information of the reference signal configured with the downlink TCI configuration, the uplink TCI configuration and / or the joint TCI configuration. The downlink reference signal may include a demodulation reference signal (DMRS), a channel state information reference signal (CSI-RS), SSB, TRS and PT-RS. The uplink reference signal may include a sounding reference signal (SRS).

[0115] In one specific implementation, if the UE is enabled to perform inter-cell PDSCH reception, inter-cell PDCCH reception, inter-cell downlink reference signal reception, inter-cell PUSCH transmission, inter-cell uplink reference signal transmission and / or inter-cell PUCCH transmission, the UE may be considered to be configured with inter-cell beam management (ICBM), and / or the UE may perform inter-cell beam management.

[0116] In one example, an ICBM configuration associated with a TRP associated with a PCI of a serving cell and associated with a TRP having a PCI different from the PCI of the serving cell (e.g., RS for beam failure detection, beam indication) may be configured via an RRC message. Once the UE is enabled to perform inter-cell PDSCH reception, inter-cell PDCCH reception, downlink reference signal reception, uplink reference signal transmission, inter-cell PUSCH transmission, and / or inter-cell PUCCH transmission, the UE may apply ICBM according to the ICBM configuration configured by (or received in) the RRC message.

[0117] In one example, once the UE is configured to perform one of inter-cell PDSCH reception, inter-cell PDCCH reception, downlink reference signal reception, uplink reference signal transmission, inter-cell PUSCH transmission, and inter-cell PUCCH transmission, the UE is expected to apply ICBM to DL reference signals, DL channels, UL reference signals, and UL channels.

[0118] In one example, the UE may perform ICBM for DL ​​and single-cell beam management for UL. Conversely, the UE may perform ICBM for UL and single-cell beam management for DL.

[0119] Inter-cell beam management:

[0120] In one specific implementation, the UE may be configured with inter-cell beam management through the NW, pre-configuration, or UE capabilities.

[0121] For example, after receiving the configuration including the information related to the inter-cell beam management, the UE may determine that it is configured with the inter-cell beam management through the NW. The configuration including the information related to the inter-cell beam management may be included in the RRC message, the MAC CE and / or the DCI.

[0122] The configuration including information related to inter-cell beam management may be or may include (but is not limited to) information of a TCI configuration associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell, information of a spatial relationship configuration associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell, information of an RS configuration associated with a TCI configuration associated with a PCI of another cell different from the PCI of the serving cell, information of a CORESET pool index value associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell, and / or information of an RS configuration associated with a spatial relationship configuration associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell. It should be noted that the TCI configuration may be a downlink TCI configuration (e.g., a list of TCI states configured for a downlink channel), an uplink TCI configuration (e.g., a list of TCI states configured for an uplink channel), and / or a joint TCI configuration (e.g., a list of TCI states configured for both a downlink channel and an uplink channel). Similarly, the information of the reference signal configured with the TCI configuration may be the information of the reference signal configured with the downlink TCI configuration, the uplink TCI configuration and / or the joint TCI configuration.

[0123] In one specific implementation, the UE may be (pre)configured with the ability to perform transmission or reception according to an applied configuration from at least one of a TCI configuration, an RS configuration associated with the TCI configuration, and a first value of a CORESET pool index. The preconfiguration may be stored in the USIM based on the UE device itself and / or based on a version.

[0124] For example, the UE may be pre-configured with the ability to perform inter-cell beam management. The pre-configuration may be stored in the USIM based on the UE device itself and / or based on the version. A UE with an advanced version (e.g., Rel-17 and above) may be pre-configured with inter-cell beam management. The UE may determine whether it is configured with inter-cell beam management based on the pre-configured information.

[0125] Figure 4 is a flow chart of a method related to capability inquiry according to an exemplary embodiment of the present disclosure. Figure 4 In one specific implementation, the UE may receive a UE capability query message (step S410), and send a UE capability information message in response to receiving the UE capability query message (step S420). The UE capability information message may include a capability to perform transmission or reception according to an applied configuration from at least one of a TCI configuration, an RS configuration associated with the TCI configuration, and a first value of a CORESET pool index.

[0126] For example, after the UE receives the UE capability inquiry message from the serving cell, the UE may include information related to the capability of performing inter-cell beam management in the UE capability information message. Thereafter, the UE (e.g., in particular the RRC layer of the UE) may submit the UE capability information message to the lower layer (e.g., the PDCP layer of the UE, the RLC layer of the UE, the MAC layer of the UE, the PHY layer of the UE) for sending to the serving cell.

[0127] After receiving the UE capability inquiry message, the UE can determine whether at least one of information about support for inter-cell beam management, information about support for feMIMO, information about support for higher frequency bands (e.g., FR2), and information about support for NR is present in the UE capability inquiry message.

[0128] In one specific implementation, if at least one of information about support for inter-cell beam management, information about support for feMIMO, information about support for higher frequency bands (e.g., FR2), and information about support for NR is present in the UE capability inquiry message, the UE may further determine whether it supports inter-cell beam management and / or whether it is (pre-)configured with inter-cell beam management.

[0129] In one specific implementation, if information about support for inter-cell beam management, information about support for feMIMO, information about support for higher frequency bands (e.g., FR2), and information about support for NR are not present in the UE capability inquiry message, the UE cannot further determine whether it supports inter-cell beam management, nor can it determine whether it is (pre-)configured with inter-cell beam management.

[0130] In one specific implementation, after the UE determines that it supports inter-cell beam management and / or is (pre-)configured with inter-cell beam management, the UE may include information related to the capability to perform inter-cell beam management in the UE capability information message.

[0131] In one specific implementation, after the UE determines that it neither supports inter-cell beam management nor is (pre-)configured with inter-cell beam management, the UE may not include information related to the capability to perform inter-cell beam management in the UE capability information message.

[0132] In one example, the UE capability information message may include the number of cells supported for operating ICBM.

[0133] In one specific implementation, for inter-cell beam management (for example, if the UE is configured with inter-cell beam management), the UE may receive or send UE-dedicated channels / signals via a TRP associated with a PCI of another cell different from the PCI of the serving cell, while non-UE-dedicated channels / signals may only be received via a TRP associated with the PCI of the serving cell.

[0134] In some implementations, UE-specific channels / signals may include, but are not limited to, messages / signals / information via logical channels such as dedicated control channels (DCCH) and dedicated traffic channels (DTCH). In some implementations, UE-specific channels / signals may include, but are not limited to, signals / information via PDCCH and / or PUCCH.

[0135] DCCH: DCCH is a point-to-point bidirectional (including UL and DL) control channel that sends dedicated control (plane) information between the UE and the network. DCCH can be used by UEs with RRC connection.

[0136] DCCH-DL-SCH (logical channel DCCH can be mapped to transport channel DL-SCH): The MAC entity of the UE can receive DL control messages / information / signals on the transport channel DL-SCH. After processing in the MAC entity of the UE, the MAC entity of the UE can pass the processed DL control messages / information / signals to the upper layer (e.g., the PDCP layer of the UE, the RRC layer of the UE) via the logical channel DCCH. For example, the RRC layer of the UE can receive DL RRC messages such as RRC reconfiguration messages, RRC recovery messages, RRC reconstruction messages, RRC release messages, UE capability inquiry messages, UE information request messages, and logged measurement configuration messages from the lower layer of the UE via the logical channel DCCH mapped to the transport channel DL-SCH.

[0137] DCCH-UL-SCH (logical channel DCCH can be mapped to transport channel UL-SCH): The MAC entity of the UE can receive DL control messages / information / signals on the logical channel DCCH. After processing in the MAC entity of the UE, the MAC entity of the UE can pass the processed UL control message / information / signal to the lower layer (e.g., the PHY layer of the UE) via the transport channel UL-SCH. For example, the RRC layer of the UE can send UL RRC messages such as RRC reconfiguration complete message, RRC recovery complete message, RRC reconstruction complete message, RRC establishment complete message, measurement report message, UE capability information message, UE auxiliary information message and dedicated SIB request message to the lower layer of the UE via the logical channel DCCH mapped to the transport channel UL-SCH.

[0138] DTCH: DTCH is a point-to-point traffic channel dedicated to one UE and used to transfer user (plane) information. DTCH can exist in both uplink and downlink.

[0139] DTCH-DL-SCH (logical channel DTCH can be mapped to transport channel DL-SCH): The MAC entity of the UE can receive DL user information / signals on the transport channel DL-SCH. After processing in the MAC entity of the UE, the MAC entity of the UE can deliver the processed DL user information / signals to the upper layer (e.g., PDCP layer of the UE, RRC layer of the UE) via the logical channel DTCH.

[0140] DTCH-UL-SCH (logical channel DTCH can be mapped to transport channel UL-SCH): The MAC entity of the UE can receive DL user information / signals on the logical channel DTCH. After processing in the MAC entity of the UE, the MAC entity of the UE can pass the processed UL user information / signals to the lower layer (e.g., the PHY layer of the UE) via the transport channel UL-SCH.

[0141] In some implementations, non-UE-dedicated channels / signals may include, but are not limited to, messages / signals / information via logical channels such as a broadcast control channel (BCCH), a paging control channel (PCCH), and / or a common control channel (CCCH)).

[0142] BCCH: BCCH is a downlink channel used for broadcasting system control information.

[0143] BCCH-BCH (logical channel BCCH can be mapped to transport channel BCH): The MAC entity of the UE can receive DL control messages / information / signals on the transport channel BCH. After processing in the MAC entity of the UE, the MAC entity of the UE can deliver the processed DL control messages / information / signals to the upper layer (e.g., PDCP layer of the UE, RRC layer of the UE) via the logical channel BCCH. For example, the RRC layer of the UE can receive MIB messages from the lower layer of the UE via the logical channel BCCH mapped to the transport channel BCH.

[0144] BCCH-DL-SCH (logical channel BCCH can be mapped to transport channel DL-SCH): The MAC entity of the UE can receive DL control messages / information / signals on the transport channel DL-SCH. After processing in the MAC entity of the UE, the MAC entity of the UE can deliver the processed DL control messages / information / signals to the upper layer (e.g., the PDCP layer of the UE, the RRC layer of the UE) via the logical channel BCCH. For example, the RRC layer of the UE can receive SIB1 messages and system information messages from the lower layer of the UE via the logical channel BCCH mapped to the transport channel DL-SCH.

[0145] PCCH: PCCH is a downlink channel that carries paging messages.

[0146] PCCH-PCH (logical channel PCCH can be mapped to transport channel PCH): The MAC entity of the UE can receive DL control messages / information / signals on the transport channel PCH. After processing in the MAC entity of the UE, the MAC entity of the UE can deliver the processed DL control messages / information / signals to the upper layer (e.g., PDCP layer of the UE, RRC layer of the UE) via the logical channel PCCH. For example, the RRC layer of the UE can receive a paging message from the lower layer of the UE via the logical channel PCCH mapped to the transport channel PCH.

[0147] CCCH: CCCH is a channel used to send control information between UE and network. This channel is used for UE that does not have RRC connection with the network.

[0148] CCCH-DL-SCH (logical channel CCCH can be mapped to transport channel DL-SCH): The MAC entity of the UE can receive DL control messages / information / signals on the transport channel DL-SCH. After processing in the MAC entity of the UE, the MAC entity of the UE can deliver the processed DL control messages / information / signals to the upper layer (e.g., the PDCP layer of the UE, the RRC layer of the UE) via the logical channel CCCH. For example, the RRC layer of the UE can receive DL RRC messages (such as RRC setup messages and RRC rejection messages) from the lower layer of the UE via the logical channel CCCH mapped to the transport channel DL-SCH.

[0149] CCCH-UL-SCH (logical channel CCCH can be mapped to transport channel UL-SCH): The MAC entity of the UE can receive DL control messages / information / signals on the logical channel CCCH. After processing in the MAC entity of the UE, the MAC entity of the UE can pass the processed UL control message / information / signal to the lower layer (e.g., the PHY layer of the UE) via the transport channel UL-SCH. For example, the RRC layer of the UE can send UL RRC messages (such as RRC recovery request message, RRC reconstruction request message, RRC establishment request message and RRC system information request message) to the lower layer of the UE via the logical channel CCCH mapped to the transport channel UL-SCH.

[0150] In one specific implementation, if the UE is configured with inter-cell beam management or when the UE is performing an inter-cell beam management operation, the UE may send a message / information / signal to or receive a message / information / signal from a TRP associated with a PCI different from the PCI of the serving cell. The PCI associated with the TRP may belong to another cell, i.e., a cell having a TRP associated with a PCI different from the PCI of the serving cell. For ease of illustration, we may refer to such another cell as a "target cell".

[0151] Scenario 1: Intra-node (e.g. in case of carrier aggregation (CA)):

[0152] Figure 5 1 is a schematic diagram illustrating that the same MAC entity of a UE according to one of the exemplary embodiments of the present disclosure processes messages / information / signals sent to or received from a TRP of a serving cell (or a TRP associated with a PCI of a serving cell) and a TRP associated with a PCI different from a PCI of a serving cell. Figure 5 , the UE may apply the same MAC entity of the UE to the serving cell and the target cell. The serving cell and the target cell may be operated by the same network node (e.g., a master node), but is not limited thereto. From the perspective of the UE, when the UE is configured with inter-cell beam management or when the UE is performing inter-cell beam management, the UE may communicate with the serving cell (e.g., Figure 5 Receive non-UE dedicated channels / signals via a TRP associated with a PCI of a cell #1 in the serving cell, and send / receive UE dedicated channels / signals via a TRP associated with a PCI different from the PCI of the serving cell, such as Figure 5 In one specific implementation, it can be applied to single TRP operation and inter-cell beam management. In one specific implementation, the UE can communicate with the serving cell (e.g., Figure 5The invention relates to a method for transmitting / receiving non-UE dedicated channels / signals via a TRP associated with a PCI of a serving cell (cell #1) and a TRP associated with a PCI different from the serving cell and / or a TRP associated with the serving cell's PCI. The method can be applied to mTRP operation and inter-cell beam management.

[0153] In one implementation, it is possible that the serving cell and the target cell may operate on the same frequency band or different frequency bands. In one implementation, it is possible that the TRP of the serving cell and the TRP of the target cell may be spatially multiplexed. In one implementation, if the TRP of the serving cell and the TRP of the target cell operate on different component carriers, the UE may perform CA between the serving cell and the target cell, where the serving cell may be a primary cell and the target cell may be a secondary cell.

[0154] Scenario 2: Inter-node (e.g., in dual connectivity (DC) scenario):

[0155] Figure 6 1 is a schematic diagram illustrating that different MAC entities of a UE according to one of the exemplary embodiments of the present disclosure process messages / information / signals sent to or received from a TRP of a serving cell (or a TRP associated with a PCI of a serving cell) and a TRP associated with a PCI different from a PCI of a serving cell. Figure 6 In one specific implementation, the UE may apply one MAC entity of the UE to process messages / information / signals received from or sent to the serving cell, and apply another MAC entity of the UE to process messages / information / signals received from or sent to the target cell. In one specific implementation, it is possible that the serving cell and the target cell may be operated by different network nodes (for example, one is operated by a primary node and the other is operated by a secondary node), but is not limited thereto. From the perspective of the UE, when the UE is configured with inter-cell beam management or when the UE is performing inter-cell beam management, the UE may communicate with the serving cell (for example, Figure 6 Receive non-UE dedicated channels / signals via a TRP associated with a PCI of a cell #1 in the serving cell, and send / receive UE dedicated channels / signals via a TRP associated with a PCI different from the PCI of the serving cell, such as Figure 6 In one specific implementation, it can be applied to single TRP operation and inter-cell beam management. In one specific implementation, the UE can communicate with the serving cell (e.g., Figure 6The UE-specific channels / signals may be received via a TRP associated with a PCI different from the serving cell's PCI and / or a TRP associated with the serving cell's PCI. In a specific implementation, it may be applied to mTRP operation and inter-cell beam management. For example, cell #1 may be associated with two TRPs, while cell #2 may be associated with a single TRP.

[0156] In one implementation, it is possible that the serving cell and the target cell may operate on the same frequency band or different frequency bands. In one implementation, it is possible that the TRP of the serving cell and the TRP of the target cell may be spatially multiplexed. In one implementation, if the TRP of the serving cell and the TRP of the target cell operate on different frequency carriers, the UE may perform multi-connectivity (MC) or dual connectivity (DC) between the serving cell and the target cell, where the serving cell may be a primary cell and the target cell may be a primary secondary cell or a secondary cell.

[0157] PDCCH CSS for system information:

[0158] In one specific implementation, the set of PDCCH candidates to be monitored by the UE is defined according to a PDCCH search space set. The search space set may be a CSS set or a UE-specific search space (USS) set. The UE may monitor PDCCH candidates in one or more of the following search space sets:

[0159] (1) Type0-PDCCH CSS set, configured for a downlink control indicator (DCI) format with a cyclic redundancy check (CRC) scrambled by the system information radio network temporary identifier (SI-RNTI) on the primary cell of the primary cell group (MCG) through the pdcch-ConfigSIB1 IE in the MIB or through the searchSpaceSIB1 IE in the PDCCH-ConfigCommon IE or through the searchSpaceZero in the PDCCH-ConfigCommon IE. It should be noted that the SearchSpaceZero IE is only used for the initial BWP. It is assumed that the UE can (always) be configured with a Type-0-PDCCH CSS to receive SIB1.

[0160] In one specific implementation, for inter-cell beam management, a Type0-PDCCH CSS set may be configured to the UE per cell, per TRP and / or per BWP. For example, a Type0-PDCCH CSS set for a DCI format with a CRC scrambled by the SI-RNTI on the serving cell, a Type0-PDCCH CSS set for a DCI format with a CRC scrambled by the SI-RNTI on the target cell.

[0161] (2) Type0A-PDCCH CSS set, configured via searchSpaceOtherSystemInformation IE in PDCCH-ConfigCommon IE for DCI format with CRC scrambled by SI-RNTI on primary cell of MCG. It should be noted that searchSpaceOtherSystemInformation IE indicates the ID of the search space for other system information (i.e., SIB2 and above). If the field is not present, the UE may not receive other system information in this BWP. In one specific implementation, the UE may be configured with a common search space to receive other SI on the active DL BWP via RRC messages by the network. In one specific implementation, the UE may be configured with a common search space to receive other SI on the initial DLBWP via SIB1 and / or RRC messages by the network.

[0162] In one specific implementation, for inter-cell beam management, a Type0A-PDCCH CSS set may be configured to the UE per cell, per TRP and / or per BWP. For example, a Type0A-PDCCH CSS set for a DCI format with a CRC scrambled by the SI-RNTI on the serving cell, a Type0A-PDCCH CSS set for a DCI format with a CRC scrambled by the SI-RNTI on the target cell.

[0163] In one specific implementation, for a DL BWP, if the searchSpaceOtherSystemInformation IE for a Type0A-PDCCH CSS set is not provided to the UE, the UE may not monitor the PDCCH for the Type0A-PDCCH CSS set on the corresponding DL BWP. Therefore, the UE may not receive other SI on the DL BWP.

[0164] (3) TypeX-PDCCH CSS set can be configured to UEs supporting ICBM per cell, per TRP or / and per BWP. For example, the UE can receive other SI for multi-TRP scenarios (e.g., intra-cell scenario, inter-cell scenario, intra-node scenario, or / and inter-node scenario) by monitoring the DCI in the TypeX PDCCH CSS set.

[0165] System information sending and receiving:

[0166] The specific implementation for sending and receiving system information in the present disclosure is generally applied to the case when the UE is configured with inter-cell beam management, but is not limited thereto.

[0167] In one specific implementation, when a UE configured with inter-cell beam management is receiving DL-SCH from a TRP associated with a PCI that is different from the PCI of the serving cell, the UE may receive other SI on the transport channel DL-SCH via a UE-dedicated logical channel (e.g., DCCH).

[0168] Other SI covers all SIBs (eg, SIB2, SIB3, SIB4, slice-specific SIB, sidelink-specific SIB, NPN-specific SIB) that are not broadcast in the minimum SI (eg, MIB, SIB1).

[0169] Other SI may be sent by the network on the DL-SCH in a dedicated manner to the UE in RRC_CONNECTED.

[0170] Part 1 - System Information Reception:

[0171] In one specific implementation, without a prior request from the UE, the UE may receive other SI from a TRP associated with a PCI different from the PCI of the serving cell via a DCCH on the DL-SCH in dedicated signaling. The other SI may be included or encapsulated in the dedicated signaling. The dedicated signaling may be, but is not limited to, an RRC reconfiguration message, an RRC reconstruction message, an RRC release message, and a UE capability inquiry message. We demonstrate the design by adopting, for example, an RRC reconfiguration process. However, the design may not be limited to applying the RRC reconfiguration message, the RRC reconfiguration complete message, and other RRC messages mentioned in the example. Other RRC messages and RRC processes (e.g., an RRC reconstruction process, an RRC release process, a UE capability inquiry process) may be applied in the design.

[0172] By using an RRC procedure of an RRC reconfiguration procedure, for example:

[0173] The network may initiate an RRC reconfiguration procedure to a UE in RRC_CONNECTED via a TRP associated with a PCI different from the PCI of the serving cell. The purpose of the RRC reconfiguration procedure is to provide system information (e.g., other SI) to the UE when the UE is configured with inter-cell beam management and the UE is receiving DL-SCH from a TRP associated with a PCI different from the PCI of the serving cell.

[0174] The UE may receive an RRC reconfiguration message from the network via a TRP associated with a PCI that is different from the PCI of the serving cell.

[0175] In scenario 1: If the UE applies the same MAC entity of the UE to process messages / information / signals received from or sent to a TRP associated with a PCI of a serving cell and a TRP associated with a PCI different from the serving cell's PCI, the UE may receive an RRC reconfiguration message including system information (e.g., MIB, SIB1, other SI) and / or an indication for obtaining MIB and / or SIB1 and / or an indication for obtaining SIB1 and / or other SI from the TRP associated with a PCI different from the serving cell's PCI.

[0176] System information (e.g., MIB, SIB1, other SI) received via a TRP associated with a PCI different from the PCI of the serving cell may be synchronized or identical to system information received from a TRP associated with the PCI of the serving cell. That is, system information received via a TRP associated with a PCI different from the PCI of the serving cell may be associated with the serving cell.

[0177] When the UE is receiving an RRC reconfiguration including SI from a TRP associated with a PCI different from the PCI of the serving cell via DL-SCH, the UE may not be required to obtain system information from the serving cell. The UE may receive the RRC reconfiguration message via SRB1 or the new SRB. The new SRB may be a signaling radio bearer used to carry specific RRC messages between the UE and the target cell via a TRP associated with a PCI different from the PCI of the serving cell, for example, using a logical channel DCCH, using a transport channel DL-SCH for DL ​​RRC messages, and a transport channel UL-SCH for UL RRC messages.

[0178] In one specific implementation, when the UE receives an RRC reconfiguration message including system information via a TRP associated with a PCI different from the PCI of the serving cell (via SRB1 or a new SRB), the UE may perform actions upon receiving system information as specified in Section 5.2.2.4 of 3GPP TS 38.331. The UE may not be required to obtain system information from the serving cell. After receiving the RRC reconfiguration message or after performing actions (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with a PCI different from the PCI of the serving cell via SRB1 or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB.

[0179] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from the PCI of the serving cell, wherein the RRC reconfiguration message includes an indication for obtaining system information, the UE may obtain an SI message as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via the TRP associated with the PCI of the serving cell. The UE may still be required to obtain system information from the serving cell. This specific implementation may be applied when the target cell does not have the same system information as the serving cell, for example, in particular when the target cell and the serving cell are not synchronized or are not operated by the same network node. After receiving the RRC reconfiguration message or after (successfully) performing an action upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI different from the PCI of the serving cell via SRB1 or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB. Alternatively, after receiving the RRC reconfiguration message or after (successfully) performing an action upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI of the serving cell via SRB1.

[0180] It should be noted that the instruction to acquire the system information may also include information on the system information associated with the serving cell to be acquired and / or the system information associated with the target cell to be acquired.

[0181] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from the PCI of the serving cell, wherein the RRC reconfiguration message includes an indication for obtaining MIB and / or SIB1, the UE may obtain MIB and / or SIB1 as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via the TRP associated with the PCI of the serving cell. The UE may still be required to obtain MIB and / or SIB1 from the serving cell, while the UE may obtain other SI from the target cell. After receiving the RRC reconfiguration message or after (successfully) performing the action of obtaining MIB and / or SIB1, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI different from the PCI of the serving cell via SRB1 or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB. Alternatively, after receiving the RRC reconfiguration message or after (successfully) performing the action of acquiring MIB and / or SIB1, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI of the serving cell via SRB1.

[0182] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from the PCI of the serving cell, wherein the RRC reconfiguration message includes an indication for obtaining system information, the UE may obtain an SI message as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via the TRP associated with the PCI different from the PCI of the serving cell. The UE may not be required to obtain system information from the serving cell. The BWP operated by the target cell (e.g., initial BWP, active BWP) may be configured with a common search space (e.g., with a field searchSpaceOtherSystemInformaiton) so that the UE may receive system information on the BWP via a TRP associated with a PCI different from the PCI of the serving cell. After receiving the RRC reconfiguration message or after performing an action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI different from the PCI of the serving cell via SRB1 or a new SRB. If the UE receives the RRC reconfiguration message via SRB 1, the UE may send the RRC reconfiguration complete message via SRB 1. If the UE receives the RRC reconfiguration message via the new SRB, the UE may send the RRC reconfiguration complete message via the new SRB.

[0183] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from a PCI of a serving cell, wherein the RRC reconfiguration message includes an indication for obtaining SIB1 and / or other SI, the UE may obtain SIB1 and / or other SI as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via a TRP associated with a PCI different from a PCI of a serving cell. The UE may not be required to obtain SIB1 and / or other SI from the serving cell, but the UE is still required to obtain the MIB from the serving cell. The BWP operated by the target cell (e.g., an initial BWP, an active BWP) may be configured with a common search space (e.g., with a field searchSpaceOtherSystemInformaiton) so that the UE may receive SIB1 and / or other SI on the BWP via a TRP associated with a PCI different from a PCI of a serving cell. After receiving the RRC reconfiguration message or after performing the action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with a PCI different from the PCI of the serving cell via SRB1 or the new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send the RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via the new SRB, the UE may send the RRC reconfiguration complete message via the new SRB.

[0184] In scenario 2: If the UE applies one MAC entity of the UE to process messages / information / signals received from or sent to a TRP associated with a PCI of a serving cell, and applies another MAC entity of the UE to process messages / information / signals received from or sent to a TRP associated with a PCI different from the PCI of the serving cell, the UE may receive an RRC reconfiguration message including system information (e.g., MIB, SIB1, other SI) and / or an indication for obtaining MIB and / or SIB1 and / or an indication for obtaining SIB1 and / or other SI from the TRP associated with a PCI different from the PCI of the serving cell.

[0185] In one specific implementation, system information (e.g., MIB, SIB1, other SI) received via a TRP associated with a PCI different from the PCI of the serving cell may be synchronized or identical to system information received from a TRP associated with the PCI of the serving cell. That is, the system information may be associated with the serving cell. In one specific implementation, system information (e.g., MIB, SIB1, other SI) received via a TRP associated with a PCI different from the PCI of the serving cell may be associated with a target cell instead of a serving cell. That is, system information received via a TRP associated with a PCI different from the PCI of the serving cell may be asynchronous or different from system information received from a TRP associated with the PCI of the serving cell (or associated with the serving cell).

[0186] When the UE is receiving an RRC reconfiguration including SI from a TRP associated with a PCI different from the PCI of the serving cell via DL-SCH, the UE may not be required to obtain system information from the serving cell. The UE may receive the RRC reconfiguration message via SRB1, SRB3 or a new SRB. The new SRB may be a signaling radio bearer, which is used to carry specific RRC messages between the UE and the target cell via a TRP associated with a PCI different from the PCI of the serving cell, for example, using a logical channel DCCH, using a transport channel DL-SCH for DL ​​RRC messages and a transport channel UL-SCH for UL RRC messages. SRB3 may be a direct signaling radio bearer, which is used to carry specific RRC messages between the UE and the secondary node when the UE is in (NG) EN-DC or NR-DC, both using the logical channel DCCH.

[0187] In one specific implementation, when the UE receives an RRC reconfiguration message including system information via a TRP associated with a PCI different from the PCI of the serving cell (via SRB1, SRB3, or a new SRB), the UE may perform actions upon receiving the system information as specified in Section 5.2.2.4 of 3GPP TS 38.331. The UE may not be required to obtain system information from the serving cell. In one specific implementation, when the UE receives an RRC reconfiguration message including system information via a TRP associated with a PCI different from the PCI of the serving cell (via SRB1, SRB3, or a new SRB), the UE may perform actions upon receiving the system information as specified in Section 5.2.2.4 of 3GPP TS 38.331. If the system information is associated with the serving cell, the UE may not be required to obtain the system information from the serving cell. If the system information is associated with the target cell instead of the serving cell, the UE may still be required to obtain the system information associated with the serving cell from the serving cell, for example, via a non-UE dedicated channel / signal from the TRP associated with the PCI of the serving cell. If the system information is associated with the target cell rather than the serving cell, the UE may still be required to obtain the system information associated with the serving cell, for example via a UE dedicated channel / signal from a TRP associated with a PCI different from the PCI of the serving cell.

[0188] After receiving the RRC reconfiguration message or after performing the action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with a PCI different from the PCI of the serving cell via SRB1, SRB3, or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB. If the UE receives the RRC reconfiguration message via SRB3, the UE may send an RRC reconfiguration complete message via SRB3.

[0189] In one implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from the PCI of the serving cell, wherein the RRC reconfiguration message includes an indication for obtaining system information associated with the serving cell, the UE may obtain the SI message as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via the TRP associated with the PCI of the serving cell. The UE may still be required to obtain the system information from the serving cell. This implementation may be applied when the target cell does not have the same system information as the serving cell, for example, in particular when the target cell and the serving cell are not synchronized or are not operated by the same network node.

[0190] After receiving the RRC reconfiguration message or after performing an action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with a PCI different from the PCI of the serving cell via SRB1, SRB3, or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB. If the UE receives the RRC reconfiguration message via SRB3, the UE may send an RRC reconfiguration complete message via SRB3. Alternatively, after receiving the RRC reconfiguration message or after performing an action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI of the serving cell via SRB1.

[0191] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from the PCI of the serving cell, wherein the RRC reconfiguration message includes an indication for obtaining the MIB and / or SIB1 associated with the serving cell, the UE may obtain the MIB and / or SIB1 as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via the TRP associated with the PCI of the serving cell. The UE may still be required to obtain the MIB and / or SIB1 associated with the serving cell from the serving cell, while the UE may obtain other SI associated with the serving cell or associated with the target cell from the target cell. This specific implementation may be applied by the UE, particularly when the MIB and / or SIB1 associated with the serving cell is the same as the MIB and / or SIB1 associated with the target cell, but is not limited thereto. Therefore, the UE may receive the MIB and / or SIB1 from the serving cell via a non-UE dedicated channel / signal via the TRP associated with the PCI of the serving cell.

[0192] After receiving the RRC reconfiguration message or after (successfully) performing the action of obtaining the MIB and / or SIB1 associated with the serving cell, the UE may send an RRC reconfiguration complete message to the TRP associated with the PCI different from the PCI of the serving cell via SRB1, SRB3 or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send the RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via the new SRB, the UE may send the RRC reconfiguration complete message via the new SRB. If the UE receives the RRC reconfiguration message via SRB3, the UE may send the RRC reconfiguration complete message via SRB3. Alternatively, after receiving the RRC reconfiguration message or after (successfully) performing the action of obtaining the MIB and / or SIB1 associated with the serving cell, the UE may send the RRC reconfiguration complete message to the TRP associated with the PCI of the serving cell via SRB1.

[0193] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from a PCI of a serving cell, wherein the RRC reconfiguration message includes an indication for obtaining system information (e.g., MIB, SIB1, or other SI) associated with a target cell, the UE may obtain SI messages as defined in subclause 5.2.2.3 in 3GPP TS 38.331 via a TRP associated with a PCI different from a PCI of a serving cell. A BWP (e.g., an initial BWP, an active BWP) operated by the target cell may be configured with a common search space (e.g., with a field searchSpaceOtherSystemInformaiton) so that the UE may receive system information on the BWP via a TRP associated with a PCI different from a PCI of a serving cell.

[0194] After receiving the RRC reconfiguration message or after performing the action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with a PCI different from the PCI of the serving cell via SRB1, SRB3, or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB. If the UE receives the RRC reconfiguration message via SRB3, the UE may send an RRC reconfiguration complete message via SRB3.

[0195] In one specific implementation, when the UE receives an RRC reconfiguration message via a TRP associated with a PCI different from a PCI of a serving cell, wherein the RRC reconfiguration message includes an indication for obtaining SIB1 and / or other SI associated with a target cell, the UE may obtain SIB1 and / or other SI associated with the target cell as defined in subclause 5.2.2.3 in 3GPP TS38.331 via a TRP associated with a PCI different from a PCI of a serving cell. A BWP operated by the target cell (e.g., an initial BWP, an active BWP) may be configured with a common search space (e.g., with a field searchSpaceOtherSystemInformaiton) so that the UE may receive SIB1 and / or other SI on the BWP via a TRP associated with a PCI different from a PCI of a serving cell. If the SIB1 and / or other SI associated with the target cell are synchronized or identical with the SIB1 and / or other SI associated with the serving cell, the UE may not be required to obtain the SIB1 and / or other SI from the serving cell, but the UE may still be required to obtain the MIB associated with the serving cell from the serving cell.

[0196] After receiving the RRC reconfiguration message or after performing the action (successfully) upon receiving the SI, the UE may send an RRC reconfiguration complete message to the TRP associated with a PCI different from the PCI of the serving cell via SRB1, SRB3, or a new SRB. If the UE receives the RRC reconfiguration message via SRB1, the UE may send an RRC reconfiguration complete message via SRB1. If the UE receives the RRC reconfiguration message via a new SRB, the UE may send an RRC reconfiguration complete message via the new SRB. If the UE receives the RRC reconfiguration message via SRB3, the UE may send an RRC reconfiguration complete message via SRB3.

[0197] System Information Request:

[0198] In one implementation, with the UE's prior request, the UE may receive additional SI from a TRP associated with a PCI different from the PCI of the serving cell via a DCCH on the DL-SCH in dedicated signaling. Details of how the UE receives additional SI may refer to the implementations of the present disclosure, particularly in one or more implementations of Section 1 - System Information Reception as described in the previous paragraphs.

[0199] We further propose how the UE requests system information (e.g., MIB, SIB1, other SI) before the UE receives the system information. The details of how the UE receives the system information can refer to the specific implementations in this disclosure, especially in one or more specific implementations of Section 1 - System Information Reception as described in the previous paragraphs.

[0200] In one specific implementation, the UE may request system information without determining that a timer (e.g., a prohibit timer associated with requesting system information) is running or expired and / or without determining that any configuration associated with whether the UE is allowed to request system information is configured to the UE. In one specific implementation, the UE may request system information after the UE determines that a timer (e.g., a prohibit timer associated with requesting system information) expires or is not running. In one specific implementation, the UE may request system information after the UE determines that the UE is configured with a configuration associated with whether the UE is allowed to request system information. In one specific implementation, the UE may request system information after the UE determines that a timer (e.g., a prohibit timer associated with requesting system information) expires or is not running and the UE is configured with a configuration associated with whether the UE is allowed to request system information.

[0201] In one specific implementation, the configuration related to whether the UE is allowed to request system information may include a configuration related to whether the UE is allowed to request system information when the UE is configured with inter-cell beam management.

[0202] In one specific implementation, the configuration related to whether the UE is allowed to request system information may include information on whether the UE is allowed to request system information of a serving cell (e.g., via any TRP, such as a TRP associated with a PCI of the serving cell and a TRP associated with a PCI different from the serving cell), information on whether the UE is allowed to request system information of a target cell (e.g., via any TRP, such as a TRP associated with a PCI of the serving cell and a TRP associated with a PCI different from the serving cell), and / or information on whether the UE is allowed to request system information of a target cell from a TRP associated with a PCI different from the serving cell.

[0203] In one specific implementation, the UE may receive a configuration related to whether the UE is allowed to request system information in an RRC message (e.g., an RRC reconfiguration message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell). After receiving the configuration related to whether the UE is allowed to request system information, the UE may configure and / or apply the configuration.

[0204] In one specific implementation, the UE may receive an absence field for a configuration related to whether the UE is allowed to request system information in an RRC message (e.g., an RRC reconfiguration message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell). After receiving an absence field for a configuration related to whether the UE is allowed to request system information, the UE may release the configuration.

[0205] In one specific implementation, the UE may receive a configuration related to whether the UE is allowed to request system information in an RRC message (e.g., an RRC release message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell). After receiving the configuration related to whether the UE is allowed to request system information, the UE may release the configuration.

[0206] In one specific implementation, the UE may receive an indicator of a configuration related to whether the UE is allowed to request system information in an RRC message (e.g., an RRC release message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell). After receiving the indicator of the configuration related to whether the UE is allowed to request system information, the UE may release the configuration.

[0207] In one specific implementation, after the UE receives the requested system information, the UE may release the configuration related to whether the UE is allowed to request the system information.

[0208] In one specific implementation, the prohibition timer associated with requesting system information may be a timer associated with requesting system information when the UE is configured with inter-cell beam management. Once the UE requests system information, the UE may start the timer (i.e., the UE sets the timer value to the configured timer value). When the timer is running, the UE may be prohibited from requesting system information. Once the UE receives system information, the UE may stop the timer. Once the timer is not running (e.g., stopped or expired), the UE may be allowed to request system information.

[0209] In one specific implementation, the prohibition timer associated with requesting system information may be a timer associated with requesting system information associated with a serving cell, in particular when the UE is configured with inter-cell beam management, but not limited thereto. Another prohibition timer associated with requesting system information may be a timer associated with requesting system information associated with a target cell, in particular when the UE is configured with inter-cell beam management, but not limited thereto. The UE may operate these two prohibition timers independently. For example, even if the timer associated with requesting system information associated with a serving cell is running (and if the timer associated with requesting system information associated with a target cell is not running, expired, not configured and / or stopped), the UE may still be allowed to request system information associated with a target cell.

[0210] In one implementation, the UE may receive a configured timer value in an RRC message (e.g., an RRC reconfiguration message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell's PCI). In one implementation, the UE may receive a configured timer value for an inhibit timer associated with requesting system information associated with the serving cell in an RRC message received from the serving cell (e.g., from a TRP associated with a PCI of the serving cell). In one implementation, the UE may receive a configured timer value for an inhibit timer associated with requesting system information associated with the target cell in an RRC message received from the target cell (e.g., from a TRP associated with a PCI different from the serving cell's PCI). In one implementation, there is (only) one configured timer value for both the inhibit timer associated with requesting system information associated with the serving cell and the inhibit timer associated with requesting system information associated with the target cell. In one specific implementation, if the configured timer value of the inhibit timer associated with the request for system information associated with the target cell does not exist, the configured timer value of the inhibit timer associated with the request for system information associated with the serving cell may be applied to the inhibit timer associated with the request for system information associated with the target cell. In one specific implementation, if the configured timer value of the inhibit timer associated with the request for system information associated with the serving cell does not exist, the configured timer value of the inhibit timer associated with the request for system information associated with the target cell may be applied to the inhibit timer associated with the request for system information associated with the serving cell.

[0211] In one specific implementation, the configured timer value may be included in the configuration related to whether the UE is allowed to request system information.

[0212] In one specific implementation, the configured timer value may not be included in the configuration related to whether the UE is allowed to request system information. However, the configured timer value and the configuration related to whether the UE is allowed to request system information are included in the same RRC message.

[0213] In one specific implementation, the UE may receive a configured timer value in an RRC message (e.g., an RRC release message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell). After receiving the configured timer value, the UE may release the configured timer value.

[0214] In one specific implementation, the UE may receive an indicator of a configured timer value in an RRC message (e.g., an RRC release message) from a serving cell (e.g., from a TRP associated with a PCI of the serving cell) or from a target cell (e.g., from a TRP associated with a PCI different from the serving cell). After receiving the indicator of the configured timer value, the UE may release the configured timer value.

[0215] In one specific implementation, after the UE receives the requested system information, the UE may release the configured timer value.

[0216] In one specific implementation, the system information to be requested may be MIB associated with the serving cell, SIB1 associated with the serving cell, other SI associated with the serving cell, MIB associated with the target cell, SIB1 associated with the target cell, and other SI associated with the target cell.

[0217] In scenario 1 or when the serving cell and the target cell are associated with the same network node, the MIB associated with the serving cell may be the same as the MIB associated with the target cell, the SIB1 associated with the serving cell may be the same as the SIB1 associated with the target cell, and other SI associated with the serving cell may be the same as other SI associated with the target cell.

[0218] In scenario 2 or when the serving cell and the target cell are associated with different network nodes, the MIB associated with the serving cell may be different from the MIB associated with the target cell, the SIB1 associated with the serving cell may be different from the SIB1 associated with the target cell, and other SI associated with the serving cell may be different from other SI associated with the target cell.

[0219] In various specific implementations and conditions, the UE may receive the MIB associated with the serving cell from a TRP associated with the PCI of the serving cell via the BCCH on the BCH, receive the MIB associated with the serving cell from a TRP associated with the PCI of another cell different from the PCI of the serving cell via the BCCH on the BCH, receive the MIB associated with the serving cell from a TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH, and / or receive the MIB associated with the serving cell from a TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH.

[0220] It should be noted that the terms "TRP associated with a PCI of another cell different from the PCI of the serving cell" and "TRP associated with a PCI different from the PCI of the serving cell" are used interchangeably.

[0221] In various specific implementations and conditions, the UE may receive the MIB associated with the serving cell from the TRP associated with the PCI of the serving cell via the BCCH on the BCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the BCCH on the BCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH, and / or receive the MIB associated with the target cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH.

[0222] In various specific implementations and conditions, the UE may receive the MIB associated with the serving cell from the TRP associated with the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH, and / or receive SIB1 associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH.

[0223] In various specific implementations and conditions, the UE may receive the MIB associated with the serving cell from the TRP associated with the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH, and / or receive SIB1 associated with the target cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH.

[0224] In various specific implementations and conditions, the UE may receive the MIB associated with the serving cell from the TRP associated with the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH, and / or receive other SI associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH.

[0225] In various specific implementations and conditions, the UE may receive the MIB associated with the serving cell from the TRP associated with the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the BCCH on the DL-SCH, receive the MIB associated with the serving cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH, and / or receive other SI associated with the target cell from the TRP associated with the PCI of another cell different from the PCI of the serving cell via the DCCH on the DL-SCH.

[0226] In one specific implementation, if the signal strength of a reference signal associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ)) is less than or equal to a corresponding threshold, the UE may request system information by following the specific implementation in the present disclosure. The UE may be preconfigured with the corresponding threshold. Alternatively, the UE may receive an RRC message including the corresponding threshold. It should be noted that if the signal strength of a reference signal associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ)) is less than or equal to the corresponding threshold, the lower layer of the UE (e.g., PHY layer, MAC layer) may indicate to the upper layer of the UE (e.g., RRC layer). When receiving the indication from the lower layer of the UE, the upper layer of the UE may trigger a system information request process. It should be noted that the reference signal may be a synchronization signal block (SSB) or a CSI-RS.

[0227] In one specific implementation, if the signal strength of a reference signal associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ)) is greater than or equal to a corresponding threshold, the UE may request system information by following the specific implementation in the present disclosure. It should be noted that if the signal strength of a reference signal associated with a TRP associated with a PCI of another cell different from the PCI of the serving cell (e.g., reference signal received power (RSRP), reference signal received quality (RSRQ)) is greater than or equal to a corresponding threshold, the lower layer of the UE (e.g., PHY layer, MAC layer) may indicate to the upper layer of the UE (e.g., RRC layer). When receiving the indication from the lower layer of the UE, the upper layer of the UE may trigger a system information request process. It should be noted that the reference signal may be an SSB or a CSI-RS.

[0228] In some cases, the UE may request system information and then receive the requested system information (i.e., the mechanism proposed in this disclosure). Cases include but are not limited to: (1) When the UE is in RRC_CONNECTED, and / or (2) When the UE is configured with inter-cell beam management, and / or (3) When the UE operates on an active BWP that is not configured with a common search space (CSS) with the field searchSpaceOtherSystemInformation, (4) When the UE operates on an active BWP (or initial BWP) that is not configured with a CSS with the field searchSpaceSIB1, and / or (5) When the UE does not yet store a valid version of one or more of the required SIBs, and / or (6) When the UE is requested by an upper layer (e.g., the NAS layer of the UE). It should be noted that in case (3), an active BWP that is not configured with a CSS with the field searchSpaceOtherSystemInformation may be associated with a serving cell or a target cell.

[0229] Embodiment 1: UE requests other SI associated with the serving cell.

[0230] After the UE determines that the UE falls into a situation where the UE can be triggered to request system information and then receives the requested system information (for example, in particular when the UE has not yet stored a valid version of an SIB in one or several required SIBs associated with the serving cell), the UE may request the required other SI associated with the serving cell by sending an RRC ICBM SI request message via the UL-SCH to (or via) a TRP associated with a PCI different from the PCI of the serving cell.

[0231] According to the system information of the information in the stored SIB of the scheduling UE (e.g., si-SchedulingInfo IE), for the SI message including at least one of the required SIBs of the UE associated with the serving cell, the UE (e.g., the RRC layer of the UE) may include an indication of the required SI message including at least one of the required SIBs of the UE and / or include an indication of the required SIBs of the UE in the RRC ICBM SI request message. The UE (e.g., the RRC layer of the UE) may then submit the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission.

[0232] It should be noted that the indication of the required SI messages including at least one of the required SIBs for the UE may be in the form of a list, where the entries of the list may represent the required SI messages.

[0233] It should be noted that the indication of the required SIBs to the UE may be in the form of a list, where the entries of the list may represent the required SIBs.

[0234] It should be noted that, particularly in scenario 1, the RRC layer of the UE and the MAC layer of the UE may handle the process for sending a TRP associated with the PCI of the serving cell and the process for sending a TRP associated with a PCI different from the PCI of the serving cell.

[0235] It should be noted that, particularly in scenario 2, the RRC layer of the UE and the MAC layer of the UE may handle the process for sending a TRP associated with a PCI different from the PCI of the serving cell, even if the requested other SI is associated with the serving cell.

[0236] It should be noted that, particularly in scenario 2, the RRC layer of the UE may handle the process for sending a TRP associated with the PCI of the serving cell and the process for sending a TRP associated with a PCI different from the PCI of the serving cell, while the MAC layer of the UE may handle the process for sending a TRP associated with a PCI different from the PCI of the serving cell.

[0237] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may start a prohibition timer associated with requesting system information. If the timer is running, the UE cannot send another RRC ICBM SI request message. If the timer is running, the UE cannot request system information, for example, according to embodiments 1, 2, 3, and 4, but not limited thereto. If the UE receives the requested other SI associated with the serving cell, the UE may stop the timer. If the timer expires and the UE does not receive the requested other SI associated with the serving cell, the UE may send the RRC ICBM SI request message again.

[0238] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may not start the prohibition timer associated with the request for system information. If the UE triggers the request for system information (not limited to being associated with the serving cell or the target cell), the UE triggers the request for system information. For example, the UE may send another RRC ICBM SI request message including the requested system information, such as according to embodiments 1, 2, 3, and 4, but not limited thereto.

[0239] For example, in Example 1 and considering the specific implementation for system information reception in the present disclosure, the UE may request other SI associated with the serving cell by sending an RRC ICBM SI request message to the TRP associated with the target cell on SRB3 via the DCCH in the UL-SCH on the PUSCH, and obtain the requested other SI associated with the serving cell by receiving an RRC message from the TRP associated with the target cell on SRB3 via the DCCH in the DL-SCH on the PDSCH.

[0240] Embodiment 2: The UE requests the MIB and / or SIB1 associated with the serving cell.

[0241] After the UE determines that the UE falls into a situation where the UE can be triggered to request system information and then receives the requested system information, the UE can request the required MIB and / or SIB1 associated with the serving cell by sending an RRC ICBMSI request message via UL-SCH to a TRP associated with a PCI that is different from the PCI of the serving cell.

[0242] The UE (e.g., the RRC layer of the UE) may include in the RRC_ICBM SI request message an indication of the required MIB associated with the serving cell and / or include an indication of the required SIB1 associated with the serving cell. The UE (e.g., the RRC layer of the UE) may then submit the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission.

[0243] It should be noted that, particularly in scenario 1, the RRC layer of the UE and the MAC layer of the UE may handle the process for sending a TRP associated with the PCI of the serving cell and the process for sending a TRP associated with a PCI different from the PCI of the serving cell.

[0244] It should be noted that, particularly in scenario 2, the RRC layer of the UE and the MAC layer of the UE may handle the process for sending (and / or receiving) a TRP associated with a PCI that is different from the PCI of the serving cell, even if the requested other SI is associated with the serving cell.

[0245] It should be noted that, particularly in scenario 2, the RRC layer of the UE may handle the processes for sending (and / or receiving) a TRP associated with the PCI of the serving cell and for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell, while the MAC layer of the UE may handle the processes for sending a TRP associated with a PCI different from the PCI of the serving cell.

[0246] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may start a prohibition timer associated with requesting system information. If the timer is running, the UE cannot send another RRC ICBM SI request message. If the timer is running, the UE cannot request system information, for example, according to embodiments 1, 2, 3, and 4, but not limited thereto. If the UE receives the requested MIB and / or SIB1 associated with the serving cell, the UE may stop the timer. If the timer expires and the UE does not receive the requested MIB and / or SIB1 associated with the serving cell, the UE may send the RRC ICBM SI request message again.

[0247] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may not start the prohibition timer associated with the request for system information. If the UE triggers the request for system information (not limited to being associated with the serving cell or the target cell), the UE triggers the request for system information. For example, the UE may send another RRC ICBM SI request message including the requested system information, such as according to embodiments 1, 2, 3, and 4, but not limited thereto.

[0248] For example, in Example 2 and considering the specific implementation for system information reception in the present disclosure, the UE may request the MIB and / or SIB1 associated with the serving cell by sending an RRC ICBM SI request message to the TRP associated with the target cell on SRB3 via the DCCH in the UL-SCH on the PUSCH, and obtain the requested MIB and / or SIB1 associated with the serving cell by receiving an RRC message from the TRP associated with the target cell on SRB3 via the DCCH in the DL-SCH on the PDSCH.

[0249] Embodiment 3: UE requests other SI associated with the target cell.

[0250] After the UE determines that the UE falls into a situation where the UE can be triggered to request system information and then receive the requested system information (for example, in particular when the UE has not yet stored a valid version of the SIB in one or several required SIBs associated with the target cell), the UE may request the required other SI associated with the target cell by sending an RRCICBM SI request message via UL-SCH to a TRP associated with a PCI different from the PCI of the serving cell.

[0251] According to the system information of the information in the stored SIB of the scheduling UE (e.g., si-SchedulingInfo IE), for the SI message including at least one of the required SIBs of the UE associated with the target cell, the UE (e.g., the RRC layer of the UE) may include an indication of the required SI message including at least one of the required SIBs of the UE and / or include an indication of the required SIBs of the UE in the RRC ICBM SI request message. The UE (e.g., the RRC layer of the UE) may then submit the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission.

[0252] It should be noted that the indication of the required SI messages including at least one of the required SIBs for the UE may be in the form of a list, where the entries of the list may represent the required SI messages.

[0253] It should be noted that the indication of the required SIBs to the UE may be in the form of a list, where the entries of the list may represent the required SIBs.

[0254] It should be noted that, particularly in scenario 1, the RRC layer of the UE and the MAC layer of the UE may handle processes for sending (and / or receiving) a TRP associated with a PCI of a serving cell and for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell.

[0255] It should be noted that, particularly in scenario 2, the RRC layer of the UE and the MAC layer of the UE may handle the process for sending (and / or receiving) a TRP associated with a PCI that is different from the PCI of the serving cell, even if the requested other SI is associated with the serving cell.

[0256] It should be noted that, particularly in scenario 2, the RRC layer of the UE may handle the processes for sending (and / or receiving) a TRP associated with the PCI of the serving cell and for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell, while the MAC layer of the UE may handle the processes for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell.

[0257] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may start a prohibition timer associated with requesting system information. If the timer is running, the UE cannot send another RRC ICBM SI request message. If the timer is running, the UE cannot request system information, for example, according to embodiments 1, 2, 3, and 4, but not limited thereto. If the UE receives the requested other SI associated with the target cell, the UE may stop the timer. If the timer expires and the UE does not receive the requested other SI associated with the target cell, the UE may send the RRC ICBM SI request message again.

[0258] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may not start the prohibition timer associated with the request for system information. If the UE triggers the request for system information (not limited to being associated with the serving cell or the target cell), the UE triggers the request for system information. For example, the UE may send another RRC ICBM SI request message including the requested system information, such as according to embodiments 1, 2, 3, and 4, but not limited thereto.

[0259] For example, in Example 3 and considering the specific implementation for system information reception in the present disclosure, the UE may request other SI associated with the target cell by sending an RRC ICBM SI request message to the TRP associated with the target cell on SRB3 via the DCCH in the UL-SCH on the PUSCH, and obtain the requested other SI associated with the target cell by receiving an RRC message from the TRP associated with the target cell on SRB3 via the DCCH in the DL-SCH on the PDSCH.

[0260] Embodiment 4: The UE requests the MIB and / or SIB1 associated with the target cell.

[0261] After the UE determines that the UE falls into a situation where the UE can be triggered to request system information and then receives the requested system information, the UE can request the required MIB and / or SIB1 associated with the target cell by sending an RRC ICBMSI request message via UL-SCH to a TRP associated with a PCI that is different from the PCI of the serving cell.

[0262] The UE (e.g., the RRC layer of the UE) may include an indication of the required MIB associated with the target cell and / or include an indication of the required SIB1 associated with the target cell in the RRC_ICBM SI request message. The UE (e.g., the RRC layer of the UE) may then submit the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission.

[0263] It should be noted that, particularly in scenario 1, the RRC layer of the UE and the MAC layer of the UE may handle processes for sending (and / or receiving) a TRP associated with a PCI of a serving cell and for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell.

[0264] It should be noted that, particularly in scenario 2, the RRC layer of the UE and the MAC layer of the UE may handle the process for sending (and / or receiving) a TRP associated with a PCI that is different from the PCI of the serving cell, even if the requested other SI is associated with the serving cell.

[0265] It should be noted that, particularly in scenario 2, the RRC layer of the UE may handle the processes for sending (and / or receiving) a TRP associated with the PCI of the serving cell and for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell, while the MAC layer of the UE may handle the processes for sending (and / or receiving) a TRP associated with a PCI different from the PCI of the serving cell.

[0266] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may start a prohibition timer associated with requesting system information. If the timer is running, the UE cannot send another RRC ICBM SI request message. If the timer is running, the UE cannot request system information, for example, according to embodiments 1, 2, 3, and 4, but not limited thereto. If the UE receives the requested MIB and / or SIB1 associated with the target cell, the UE may stop the timer. If the timer expires and the UE does not receive the requested MIB and / or SIB1 associated with the target cell, the UE may send the RRC ICBM SI request message again.

[0267] In one specific implementation, after the UE (e.g., the RRC layer of the UE) submits the RRC ICBM SI request message to the lower layer (e.g., the MAC layer of the UE) for transmission, the UE may not start the prohibition timer associated with the request for system information. If the UE triggers the request for system information (not limited to being associated with the serving cell or the target cell), the UE triggers the request for system information. For example, the UE may send another RRC ICBM SI request message including the requested system information, such as according to embodiments 1, 2, 3, and 4, but not limited thereto.

[0268] For example, in Example 4 and considering the specific implementation for system information reception in the present disclosure, the UE may request the MIB and / or SIB1 associated with the target cell by sending an RRC ICBM SI request message to the TRP associated with the target cell on SRB3 via the DCCH in the UL-SCH on the PUSCH, and obtain the requested MIB and / or SIB1 associated with the target cell by receiving an RRC message from the TRP associated with the target cell on SRB3 via the DCCH in the DL-SCH on the PDSCH.

[0269] Figure 7 is a flow chart of a method applicable to a network device according to an exemplary embodiment of the present disclosure. Figure 7 It should be noted that the order of the steps in the figure can be changed according to actual requirements.

[0270] Step S710: The network device sends a radio resource control (RRC) message to the UE via the serving cell. The RRC message includes first information of at least one of a transmission configuration indicator (TCI) configuration, a reference signal (RS) configuration associated with the TCI configuration, and a first value of a control resource set (CORESET) pool index, and the first information is associated with another cell having a second physical cell identifier (PCI) different from the first PCI of the serving cell.

[0271] Step S720: The network device performs transmission or reception via another cell according to at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

[0272] In one specific implementation, the RRC message may also include second information of at least one of a second TCI configuration, a second RS configuration associated with the second TCI configuration, and a second value of the CORESET pool index, and the second information is associated with the serving cell.

[0273] In one specific implementation, a first value of the CORESET pool index in the first information is different from a second value of the CORESET pool index in the second information.

[0274] In one specific implementation, the first value of the CORESET pool index is associated with the TCI configuration.

[0275] In one specific implementation, the TCI configuration is at least one of: a downlink TCI configuration associated with a list of TCI states configured for downlink reception, an uplink TCI configuration associated with a list of TCI states configured for uplink transmission, and a joint configuration associated with a list of TCI states configured for downlink reception and uplink transmission.

[0276] In one specific implementation, the network device may perform inter-cell physical downlink shared channel (PDSCH) transmission to transmit the PDSCH via a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell physical downlink control channel (PDCCH) transmission to transmit the PDCCH via a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell downlink reference signal transmission via a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell physical uplink shared channel (PUSCH) reception to receive the PUSCH via a TRP associated with a PCI of another cell different from the PCI of the serving cell, perform inter-cell physical uplink control channel (PUCCH) reception to receive the PUCCH via a TRP associated with a PCI of another cell different from the PCI of the serving cell, or perform inter-cell uplink reference signal transmission via a TRP associated with a PCI of another cell different from the PCI of the serving cell. The downlink reference signal includes a demodulation reference signal (DMRS) and a channel state information reference signal (CSI-RS). The uplink reference signal includes a sounding reference signal (SRS).

[0277] In one specific implementation, the network device may send a UE capability query message, and receive a UE capability information message in response to sending the UE capability query message. The UE capability information message includes a capability to perform transmission or reception according to an applied configuration from at least one of a TCI configuration, an RS configuration associated with the TCI configuration, and a first value of a CORESET pool index.

[0278] In one specific implementation, the network device may receive or send a UE-dedicated channel or a UE-dedicated signal via a TRP associated with a PCI of another cell different from the PCI of the serving cell, and receive or send a non-UE-dedicated channel or a non-UE-dedicated signal via the serving cell. The UE-dedicated channel or the UE-dedicated signal is a message, signal or information via a logical channel, which is one of a dedicated control channel (DCCH) and a dedicated traffic channel (DTCH), the UE-dedicated channel or the UE-dedicated signal is a message, signal or information via one of a PDCCH and a PUCCH, and / or the non-UE-dedicated channel or the non-UE-dedicated signal is a message, signal or information via a logical channel, which is one of a broadcast control channel (BCCH), a paging control channel (PCCH) and a common control channel (CCCH).

[0279] Figure 8 A block diagram of a node for wireless communication according to various aspects of the present application is illustrated. Figure 8 As shown, the node 800 may include a transceiver 820, a processor 828, a memory 834, one or more presentation components 838, and at least one antenna 836. The node 800 may also include an RF spectrum band module, a base station communication module, a network communication module, and a system communication management module, an input / output (I / O) port, an I / O component, and a power supply ( Figure 8 Each of these components may communicate with each other directly or indirectly via one or more buses 840. In one specific implementation, the node 800 may be a processor that performs the operations described herein, for example, with reference to Figures 1 to 7 A UE or base station with various functions described.

[0280] A transceiver 820 having a transmitter 822 (e.g., a transmitting circuit) and a receiver 824 (e.g., a receiving circuit) may be configured to transmit and / or receive time and / or frequency resource partitioning information. In some implementations, the transceiver 820 may be configured to transmit in different types of subframes and time slots, including but not limited to available, unavailable, and flexibly usable subframe and time slot formats. The transceiver 820 may be configured to receive data and control channels.

[0281] Node 800 may include various computer-readable media. Computer-readable media may be any available media accessible by node 800, and include volatile and non-volatile media, removable and non-removable media. As an example and not limitation, computer-readable media may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented in any method or technology for storing information such as computer readable.

[0282] Computer storage media include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, cassettes, magnetic tape, magnetic disk storage, or other magnetic storage devices. Computer storage media do not include propagated data signals. Communication media typically embody computer-readable instructions, data structures, program modules or other data in the form of modulated data signals (such as carrier waves or other transmission mechanisms), and include any information delivery media. The term "modulated data signal" refers to a signal that sets or changes one or more of its characteristics in a manner that encodes information in the signal. By way of example and not limitation, communication media include wired media (such as a wired network or a direct wired connection) and wireless media (such as acoustic, RF, infrared and other wireless media). Combinations of any of the above should also be included within the scope of computer-readable media.

[0283] The memory 834 may include computer storage media in the form of volatile and / or non-volatile memory. The memory 834 may be removable, non-removable, or a combination thereof. Exemplary memories include solid-state memory, hard drives, optical drives, etc. Figure 8 As illustrated in FIG. 1 , the memory 834 may store computer-readable, computer-executable instructions 832 (e.g., software code) that, when executed, are configured to cause the processor 828 to perform the operations described herein, such as those described in the accompanying drawings. Figures 1 to 7 Alternatively, the instructions 832 may not be directly executable by the processor 828, but rather (eg, when compiled and executed) may be configured to cause the node 800 to perform the various functions described herein.

[0284] The processor 828 (e.g., having a processing circuit) may include an intelligent hardware device, such as a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 828 may include a memory. The processor 828 may process data 830 and instructions 832 received from the memory 834, as well as information passed through the transceiver 820, the baseband communication module, and / or the network communication module. The processor 828 may also process information to be transmitted to the transceiver 820 for transmission to the network communication module via the antenna 836 for transmission to the core network.

[0285] One or more presentation components 838 present the data indication to a person or other device. Exemplary presentation components 838 include a display device, a speaker, a printing component, a vibration component, etc.

[0286] From the above description, it is apparent that various techniques may be used to implement these concepts without departing from the scope of the concepts described in this disclosure. In addition, although these concepts have been described with specific reference to certain implementations, those of ordinary skill in the art will recognize that changes may be made in form and detail without departing from the scope of these concepts. Therefore, the implementations described are considered to be illustrative and non-restrictive in all respects. It should also be understood that the present disclosure is not limited to the specific implementations described above, but many rearrangements, modifications, and substitutions are possible without departing from the scope of the present disclosure.

Claims

1. A method for user equipment (UE) related to inter-cell beam operation, the method comprising: receiving a radio resource control (RRC) message from a serving cell, wherein the RRC message includes first information of at least one of a transmission configuration indicator (TCI) configuration, a reference signal (RS) configuration associated with the TCI configuration, and a first value of a control resource set (CORESET) pool index, and the first information is associated with another cell having a second physical cell identity (PCI) different from a first PCI of the serving cell; applying at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index; as well as Transmission or reception with the other cell is performed according to an applied configuration from the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

2. The method according to claim 1, wherein the RRC message further includes second information of at least one of a second TCI configuration, a second RS configuration associated with the second TCI configuration, and a second value of the CORESET pool index, and the second information is associated with the serving cell.

3. The method of claim 2, wherein the first value of the CORESET pool index in the first information is different from the second value of the CORESET pool index in the second information.

4. The method of claim 1, wherein the first value of the CORESET pool index is associated with the TCI configuration.

5. The method of claim 1, wherein the TCI configuration is at least one of the following: a downlink TCI configuration associated with a list of TCI states configured for downlink reception, an uplink TCI configuration associated with a list of TCI states configured for uplink transmissions, and A joint TCI configuration associated with a list of TCI states configured for the downlink reception and the uplink transmission.

6. The method of claim 1, wherein applying the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index comprises: adding the TCI configuration in response to receiving the information of the TCI configuration including the TCI configuration to be added; or modifying the TCI configuration in response to receiving the information of the TCI configuration including the TCI configuration to be modified; or storing the TCI configuration in response to adding and modifying the TCI configuration; or The TCI configuration is released in response to receiving the information of the TCI configuration including the TCI configuration to be released.

7. The method of claim 1, wherein performing the transmission or the reception with the another cell comprises: performing inter-cell physical downlink shared channel (PDSCH) reception to receive the PDSCH from the another cell; or performing inter-cell physical downlink control channel (PDCCH) reception to receive the PDCCH from the another cell; or performing inter-cell downlink reference signal reception from the other cell; or performing inter-cell physical uplink shared channel (PUSCH) transmission to transmit the PUSCH to the another cell; or performing inter-cell physical uplink control channel (PUCCH) transmission to transmit the PUCCH to the another cell; or performing an inter-cell uplink reference signal transmission to the another cell; wherein: The downlink reference signal includes a demodulation reference signal (DMRS) and a channel state information reference signal (CSI-RS); and The uplink reference signal includes a sounding reference signal (SRS).

8. The method according to claim 1, further comprising: Receive UE capability inquiry message; as well as A UE capability information message is sent in response to receiving the UE capability inquiry message, wherein the UE capability information message includes the ability to perform the sending or the receiving according to the applied configuration from at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

9. The method according to claim 1, further comprising: is preconfigured with the capability to perform the sending or the receiving according to the applied configuration from the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

10. The method of claim 1, wherein performing the transmitting or the receiving with the another cell comprises: receiving or sending a UE dedicated channel or a UE dedicated signal via the other cell; as well as receiving or sending a non-UE dedicated channel or a non-UE dedicated signal via the serving cell, wherein The UE-specific channel or the UE-specific signal is a message, a signal or information via a logical channel, and the logical channel is one of a dedicated control channel (DCCH) and a dedicated traffic channel (DTCH); or The UE-specific channel or the UE-specific signal is a message, a signal or information via one of a PDCCH and a PUCCH; or The non-UE-dedicated channel or the non-UE-dedicated signal is a message, a signal or information via a logical channel, and the logical channel is one of a broadcast control channel (BCCH), a paging control channel (PCCH) and a common control channel (CCCH).

11. A user equipment (UE), the UE comprising: Transceiver; one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and at least one processor coupled to the transceiver and to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to: receiving, by the transceiver, a radio resource control (RRC) message from a serving cell, wherein the RRC message includes first information of at least one of a transmission configuration indicator (TCI) configuration, a reference signal (RS) configuration associated with the TCI configuration, and a first value of a control resource set (CORESET) pool index, and the first information is associated with another cell having a second physical cell identity (PCI) different from a first PCI of the serving cell; applying at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index; as well as Transmission or reception with the other cell is performed by the transceiver according to the applied configuration of the at least one from among the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

12. The UE according to claim 11, wherein the RRC message further includes second information of at least one of a second TCI configuration, a second RS configuration associated with the second TCI configuration, and a second value of the CORESET pool index, the second information being associated with the serving cell.

13. The UE of claim 12, wherein the first value of the CORESET pool index in the first information is different from the second value of the CORESET pool index in the second information.

14. The UE of claim 11, wherein the first value of the CORESET pool index is associated with the TCI configuration.

15. The UE according to claim 11, wherein the TCI configuration is at least one of the following: a downlink TCI configuration associated with a list of TCI states configured for downlink reception, an uplink TCI configuration associated with a list of TCI states configured for uplink transmissions, and A joint TCI configuration associated with a list of TCI states configured for the downlink reception and the uplink transmission.

16. The UE of claim 11, wherein the at least one processor is further configured to: adding the TCI configuration in response to receiving the information of the TCI configuration including the TCI configuration to be added; or modifying the TCI configuration in response to receiving the information of the TCI configuration including the TCI configuration to be modified; or storing the TCI configuration in response to adding and modifying the TCI configuration; or The TCI configuration is released in response to receiving the information of the TCI configuration including the TCI configuration to be released.

17. The UE of claim 11, wherein the at least one processor is further configured to: performing inter-cell physical downlink shared channel (PDSCH) reception to receive the PDSCH from the another cell; or performing inter-cell physical downlink control channel (PDCCH) reception to receive the PDCCH from the another cell; or performing inter-cell downlink reference signal reception from the other cell; or performing inter-cell physical uplink shared channel (PUSCH) transmission to transmit the PUSCH to the another cell; or performing inter-cell physical uplink control channel (PUCCH) transmission to transmit the PUCCH to the another cell; or performing an inter-cell uplink reference signal transmission to the another cell; wherein: The downlink reference signal includes a demodulation reference signal (DMRS) and a channel state information reference signal (CSI-RS); and The uplink reference signal includes a sounding reference signal (SRS).

18. The UE of claim 11, wherein the at least one processor is further configured to: receiving, by the transceiver, a UE capability inquiry message; and sending, by the transceiver, a UE capability information message in response to receiving the UE capability inquiry message, wherein the UE capability information message includes a capability to perform the sending or the receiving according to the applied configuration from the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index; or The at least one processor is further configured to: is preconfigured with the capability to perform the sending or the receiving according to the applied configuration from the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

19. The UE of claim 11, wherein the at least one processor is further configured to: receiving or sending, by the transceiver, a UE-dedicated channel or a UE-dedicated signal via the other cell; and receiving or sending a non-UE dedicated channel or a non-UE dedicated signal by the transceiver via the other cell, wherein: The UE-specific channel or the UE-specific signal is a message, a signal or information via a logical channel, the logical channel being one of a dedicated control channel (DCCH) and a dedicated traffic channel (DTCH), or The UE-specific channel or the UE-specific signal is a message, a signal or information via one of a PDCCH and a PUCCH; or The non-UE-dedicated channel or the non-UE-dedicated signal is a message, a signal or information via a logical channel, and the logical channel is one of a broadcast control channel (BCCH), a paging control channel (PCCH) and a common control channel (CCCH).

20. A network device comprising: at least one transceiver; one or more non-transitory computer-readable media having computer-executable instructions embodied thereon; and at least one processor coupled to the transceiver and to the one or more non-transitory computer-readable media and configured to execute the computer-executable instructions to: transmitting, by the transceiver, a radio resource control (RRC) message to a user equipment (UE) via a serving cell, wherein the RRC message includes first information of at least one of a transmission configuration indicator (TCI) configuration, a reference signal (RS) configuration associated with the TCI configuration, and a first value of a control resource set (CORESET) pool index, and the first information is associated with another cell having a second physical cell identity (PCI) different from a first PCI of the serving cell; as well as Transmitting or receiving is performed, by the transceiver, via the other cell according to the at least one of the TCI configuration, the RS configuration associated with the TCI configuration, and the first value of the CORESET pool index.

Images