Systems, methods, and non-transitory computer readable media for virtual carrier-based wireless communication

By adopting a combination solution of multi-beam technology and virtual carriers in wireless communication systems, the problem of large propagation loss in high frequency bands is solved, the coverage range and access efficiency are improved, and a wider communication coverage is achieved.

CN118985157APending Publication Date: 2024-11-19ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280094028.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-08-01
Publication Date
2024-11-19

AI Technical Summary

Technical Problem

Traditional wireless communication systems lead to large propagation losses in high frequency bands, resulting in small cell coverage radius and unable to effectively match service needs in different frequency bands.

Method used

Using a combination of multi-beam technology and virtual carrier, a wider coverage area is achieved by allocating uplink and downlink resources in the time domain, and the efficiency of the initial access process is enhanced.

Benefits of technology

It improves the coverage range and access efficiency of wireless communication systems, solves the problem of large propagation losses in high frequency bands, and achieves wider communication coverage.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118985157A_ABST
    Figure CN118985157A_ABST
Patent Text Reader

Abstract

Deployment disclosed herein relates to data communication using virtual carriers, including a user equipment (UE) receiving first information for a first virtual carrier from a network. The UE determines second information for the second virtual carrier based on the first information. In some examples, the UE transmits an uplink access signal to the network on an uplink resource of a first virtual carrier or a second virtual carrier. In some examples, the UE receives downlink control information from the network on at least one of a first downlink resource in the first virtual carrier or a second downlink resource in the second virtual carrier based on the first information and the second information.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates generally to wireless communications, and more particularly, to systems, methods, and non-transitory computer-readable media for signal and channel transmission. Background Art

[0002] Even though wireless communication services cover more and more applications, traditional wireless communication services do not match each communication frequency band. For some systems, the frequency band is relatively high relative to the service, resulting in greater propagation loss. At the same power, the cell coverage radius is relatively small. Summary of the invention

[0003] The example embodiments disclosed herein are intended to solve problems related to one or more of the problems presented in the prior art, and to provide additional features, which will become apparent when combined with the following figures and by reference to the following detailed description. According to various embodiments, example systems, methods, devices, and computer program products are disclosed herein. However, it will be understood that these embodiments are presented only as examples and are not restrictive, and it will be apparent to those of ordinary skill in the art who have read this disclosure that various modifications can be made to the disclosed embodiments while remaining within the scope of this disclosure.

[0004] Some deployments of the present disclosure relate to systems, apparatuses, methods, and non-transitory computer-readable media for data communication, including: a user equipment (UE) receives first information for a first virtual carrier from a network (e.g., a base station (BS)). The UE determines second information for a second virtual carrier based on the first information. In some examples, the UE sends an uplink access signal to the network on an uplink resource of the first virtual carrier or the second virtual carrier. In some examples, the UE receives downlink control information from the network on at least one of a first downlink resource in the first virtual carrier or a second downlink resource in the second virtual carrier based on the first information and the second information.

[0005] Some deployments of the present disclosure relate to systems, apparatuses, methods, and non-transitory computer-readable media for data communication, including: sending first information for a first virtual carrier to a UE. Second information for a second virtual carrier may be determined by the UE based on the first information. In some examples, the network receives an uplink access signal from the UE on an uplink resource of the first virtual carrier or the second virtual carrier. In some examples, the network sends downlink control information to the UE on at least one of a first downlink resource in the first virtual carrier or a second downlink resource in the second virtual carrier based on the first information and the second information.

[0006] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] Various example implementations of the present solution are described in detail below with reference to the following figures or drawings. These drawings are provided for illustrative purposes only and depict only example implementations of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered as limiting the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.

[0008] Figure 1 An example cellular communication network is shown in accordance with some deployments.

[0009] Figure 2 Block diagrams of example base stations and example user equipment are shown in accordance with some deployments.

[0010] Figure 3 is a diagram showing an example mapping relationship between SSB and time slots.

[0011] Figure 4 It is a diagram showing that SSB cannot be transmitted in the time slot.

[0012] Figure 5 An example frame structure for transmitting SSB is shown.

[0013] Figure 6 is a diagram illustrating a frame structure for PRACH transmission according to various deployments.

[0014] Figure 7 is a diagram illustrating a frame structure of two virtual carriers according to various deployments.

[0015] Figure 8 is a diagram illustrating a frame structure of two virtual carriers according to various deployments.

[0016] Fig. 9 is a diagram illustrating a frame structure of two virtual carriers according to various deployments.

[0017] Fig.10 is a table showing example definitions of transmission power parameters according to some deployments.

[0018] Fig.11 is a table showing an example relationship between transmission attempts and transmission power for a preamble of a PRACH according to some deployments.

[0019] Fig.12 is a table showing an example relationship between transmission attempts and transmission power for a preamble of a PRACH according to some deployments.

[0020] Fig.13 is a diagram illustrating example frame structures of two virtual carriers according to various deployments.

[0021] Fig.14 is a table showing example associations between SSB and RO for transmissions according to some deployments.

[0022] Fig.15 is a diagram illustrating example frame structures of two virtual carriers according to various deployments.

[0023] Fig.16 is a table showing example associations between SSB and RO for transmissions according to some deployments.

[0024] Fig.17 is a table showing example associations between SSB and RO for transmissions according to some deployments.

[0025] Fig.18 is a flow chart illustrating an example method for data communication according to various deployments. DETAILED DESCRIPTION

[0026] Various example implementations of the present solution are described below with reference to the accompanying drawings to enable those of ordinary skill in the art to make and use the present solution. As will be apparent to those of ordinary skill in the art, after reading this disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example implementations and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be redeployed while remaining within the scope of the present solution. Therefore, those of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in an example order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.

[0027] Mobile communication systems can be systematically networked on carrier frequencies higher than those used in 2G, 3G, and 4G systems. Some systems utilize frequency bands such as 3 GHz to 6 GHz and 6 GHz to 100 GHz. In these systems, the frequency bands are relatively high relative to the service, resulting in greater propagation losses. At the same power, the cell coverage radius is relatively small. In order to achieve a wider range of communication systems (including but not limited to 2G, 3G, and 4G), some deployments in this article involve enhanced coverage and implementation of multiple beams for the initial access process.

[0028] Figure 1An example wireless communication network and / or system 100 is shown in which the techniques disclosed herein may be implemented in accordance with an embodiment of the present disclosure. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a NarrowBand Internet of Things (NB-IoT) network, and is referred to herein as network 100. Such an example network 100 includes a BS 102 and a UE 104 that may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. In Figure 1 1, BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one BS operating on its allocated bandwidth to provide adequate wireless coverage to its intended users.

[0029] For example, BS 102 may operate on an allocated channel transmission bandwidth to provide adequate coverage to UE 104. BS 102 and UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may also be divided into subframes 120 / 127, which may include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are described herein as "communication nodes" that may generally practice non-limiting examples of the methods disclosed herein. According to various embodiments of the present solution, such communication nodes may be capable of wireless and / or wired communications.

[0030] Figure 2 A block diagram of an example wireless communication system 200 for sending and receiving wireless communication signals (e.g., OFDM (Orthogonal Frequency Division Multiplexing) / OFDMA (Orthogonal Frequency Division Multiple Access) signals) according to some embodiments of the present solution is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, the system 200 may be used in a wireless communication environment (such as, for example, a wireless communication environment such as described above). Figure 1 Communicate (eg, send and receive) data symbols in a wireless communication environment 100).

[0031] The system 200 generally includes a BS 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). The BS 202 includes a base station (BS) transceiver module 210 (hereinafter also referred to as: BS transceiver 210, transceiver 210), a BS antenna 212 (hereinafter also referred to as: antenna 212 or downlink antenna 212), a BS processor module 214 (hereinafter also referred to as: processor module 214), a BS memory module 216 (hereinafter also referred to as: memory module 216) and a network communication module 218, each module is coupled and interconnected to each other via a data communication bus 220 as needed. UE 204 includes a UE (user equipment) transceiver module 230 (also referred to as UE transceiver 230, transceiver 230), a UE antenna 232 (hereinafter also referred to as: antenna 232 or uplink antenna 232), a UE memory module 234 (hereinafter also referred to as: memory module 234) and a UE processor module 236 (hereinafter also referred to as: processor module 236), each of which is coupled and interconnected to each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via a communication channel 250, which (hereinafter also referred to as: wireless transmission link 250, wireless data communication link 250) may be any wireless channel or other medium suitable for data transmission as described herein.

[0032] As will be appreciated by those skilled in the art, the system 200 may also include Figure 2 . It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether this function is implemented as hardware, firmware, or software may depend on the specific application and the design constraints imposed on the entire system. Personnel familiar with the concept described herein can implement this function in an appropriate manner for each specific application, but this implementation decision should not be interpreted as limiting the scope of the present disclosure.

[0033] According to some embodiments, the UE transceiver 230 may be referred to herein as an uplink transceiver 230 including a Radio Frequency (RF) transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 232. A duplex switch (not shown) may alternately couple the uplink transmitter or receiver to the uplink antenna in a time duplex manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210 including an RF transmitter and an RF receiver, each of which includes a circuit coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time division duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time so that the uplink receiver circuit is coupled to the uplink antenna 232 so as to receive transmissions over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. In some embodiments, there is tight time synchronization with a minimum guard time between changes in both duplex directions.

[0034] The UE transceiver 230 and the BS transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna deployment 212 / 232 that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the BS transceiver 210 are configured to support industry standards, such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to application to specific standards and related protocols. Instead, the UE transceiver 230 and the BS transceiver 210 can be configured to support alternative or additional wireless data communication protocols (including future standards or variations thereof).

[0035] According to various embodiments, BS202 can be, for example, an evolved node B (eNB), a serving eNB, a target eNB, a femtocell or a microcell. In some embodiments, UE 204 can be various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, a wearable computing device, etc. Processor modules 214 and 236 can be implemented or realized using a general-purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof designed to perform the functions described herein. In this way, the processor can be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor can also be implemented as a combination of computing devices, for example, a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a digital signal processor core, or a combination of any other such configurations.

[0036] Further, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly in hardware, in firmware, in software modules executed by the processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, so that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into their respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by the processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.

[0037] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the BS 202, which implement bidirectional communication between the BS transceiver 210 and other network components and communication nodes configured to communicate with the BS 202. For example, the network communication module 218 can be configured to support the Internet or WiMAX (World Interoperability for Microwave Access) business. In a typical deployment, but without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the BS transceiver 210 can communicate with a traditional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms "configured to", "configured to" and various variations thereof used herein with respect to a specified operation or function refer to a device, component, circuit, structure, machine, signal, etc., which is physically constructed, programmed, formatted and / or deployed to perform a specified operation or function.

[0038] During the initial access process, the terminal (e.g., user equipment (UE)) attempts to detect a synchronization signal / physical broadcast channel (PBCH) block (SynchronizationSignal / PBCH Block, SSB) at a predefined frequency point. The frequency point, which may be referred to as a synchronization raster, can be used to detect the primary synchronization signal (PSS), the secondary synchronization signal (SSS) and receive the PBCH. In some embodiments, multiple SSBs in the time domain are defined within a transmission period. For example, for FR1 (frequency range 1), the maximum number of SSBs in a period is L max =4 or 8. In some examples, for FR2 (frequency range 2), the maximum number of SSBs in a period is L max=64. In some embodiments, each SSB occupies 4 OFDM symbols in the time domain and 240 subcarriers in the frequency domain. In some embodiments, one SSB includes PSS, SSS and PBCH. In some embodiments, the SSB index is indicated by the PBCH demodulation reference signal (DMRS) of FR1. In some embodiments, the SSB index is indicated by the PBCH DMRS and PBCH payload of FR2.

[0039] For different sub-carrier spacings (SCS), different mapping relationships from SSB to time slots may be defined. Figure 3 is a diagram showing an example mapping relationship 300 between SSBs and time slots according to some deployments. The vertical dimension corresponds to the frequency domain and the horizontal dimension corresponds to the time domain. The mapping relationship 300 corresponds to a 15kHz SCS SSB. For a frequency range of, for example, 0-3GHz, four time domain positions are defined. The time domain positions occupy the first two time slots of a half frame, which contains a total of 5 time slots. There are two SSBs in each time slot. The starting symbols of the two SSBs are symbol #2 and symbol #8, respectively. For a frequency range of, for example, 3-6GHz, eight time domain positions are defined. These time domain positions occupy the first four time slots of a half frame. There are two SSBs in each time slot. The starting symbols of the two SSBs are symbol #2 and symbol #8, respectively. In an example where a TDD (Time Division Duplexing) carrier is configured with a frame structure "DDSUU", since the fourth time slot is an uplink time slot, the SSB located in the fourth time slot cannot be transmitted to the UE. As used herein, "D" refers to a downlink time slot, "U" refers to an uplink time slot, and "S" refers to a flexible or special time slot. A flexible or special time slot can be further rewritten as a downlink resource or an uplink resource or a dynamic flexible resource through dynamic signaling. Whether an SSB located in the third special time slot can be transmitted depends on the symbol properties. In the example where the third time slot has a symbol configured as "DDDFFFF UUUUUUU", the second SSB cannot be transmitted either. Figure 4 As shown, Figure 4 is a diagram showing that SSB cannot be transmitted in a time slot, and only the first five SSBs can be transmitted under the frame structure configuration “DDSUU.” The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. Figure 4 Each unshaded block in corresponds to a time slot, and each shaded block corresponds to one or more symbols within the time slot for transmitting an SSB.

[0040] After successfully detecting the SSB, the UE receives System Information Block (SIB) 1 to further obtain the initial access configuration information carried in the SIB1 Physical Downlink Shared Channel (PDSCH). The SIB1 Physical Downlink Control Channel (PDCCH) (also referred to as Type 0 PDCCH) includes monitoring opportunity configuration information, such as the Control Resource Set (CORESET) and the Search Space Set (SS), which are indicated by the fields controlResourceSetZero and searchSpaceZero in the PBCH, respectively. In some examples, the SS of the Type 0 PDCCH is Search Space Zero (SS0), and the associated CORESET is CORESET#0. The field controlResourceSetZero is 4 bits, and the field controlResourceSetZero supports indicating up to 16 different CORESET configurations in one CORESET configuration set. Similarly, there are 4 bits for searchSpaceZero, which supports indicating up to 16 different SS configurations in one search space set configuration set. The CORESET / SS configuration in each configuration set can be predefined.

[0041] For SS0, each SSB corresponds to two consecutive time slots, and each time slot contains one monitoring opportunity. The BS can select either of the two consecutive time slots to transmit type 0 PDCCH. Figure 5 An example frame structure 500 is shown for mapping between time slots and SSBs for monitoring opportunities under SS0. The vertical dimension corresponds to the frequency domain and the horizontal dimension corresponds to the time domain. Frame structure 500 includes time slots configured as "DDSUU". Two uplink time slots correspond to SSB#4. The BS cannot allocate resources for transmission type 0 PDCCH. Therefore, SSB#4 cannot be used for initial access either.

[0042] Based on the initial access configuration information carried in the SIB1 PDSCH, the UE can send a physical random access channel (PRACH) (e.g., a preamble or msg1) in a PRACH transmission resource (e.g., a random access channel (RACH) opportunity (RO) associated with the selected SSB). The association between the SSB and the RO is made according to a predefined rule. Before the association, the UE first determines which ROs are valid ROs. The association between the actually transmitted SSB and the valid RO can be determined. In some examples, for a UE provided with tdd-UL-DL-ConfigurationCommon (time division duplex-uplink-downlink-common configuration), a PRACH opportunity in a PRACH slot is determined to be valid in response to determining the following items: 1) the PRACH opportunity is within a UL symbol, or 2) the PRACH opportunity is not earlier than the SSB in the PRACH slot and is at least N after the last downlink symbol. gap symbols and at least N after the last SSB symbol gap Symbols start, where N gap is predefined. The candidate SSB index of the SSB corresponds to the SSB index provided by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon. Therefore, the TDD frame structure affects whether the configured RO is a valid RO.

[0043] For TDD carriers, uplink and downlink transmissions are restricted by a specific frame structure. This restriction may cause additional delays in uplink and downlink transmissions or some transmission failures. Specifically, during the initial access process, SSB and SIB1 may not be able to send enough SSBs due to the frame structure. Because there are not enough uplink resources, PRACH transmission delays are increased. The deployment disclosed in this article alleviates the restrictions or impacts on uplink and downlink transmissions caused by the frame structure of the TDD carrier.

[0044] Figure 66 is a diagram showing a frame structure 600 for PRACH transmission according to various deployments. The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. The frame structure 600 includes two virtual carriers, virtual carrier 610 and virtual carrier 620, having different frame structures. The frame structure of each of the carriers 610 or 620 may be configured by the BS for the UE. The half frame of the frame structure of the virtual carrier 610 is shown to include 5 time slots, configured as "UUSDD". The half frame of the frame structure of the virtual carrier 620 is shown to include 5 time slots, configured as "DDSUU". The virtual carriers 610 and 620 complement each other, thereby more completely showing the uplink and downlink resources in the time domain. As shown, at any given time slot in the time domain, there are uplink resources and downlink resources between the virtual carriers 610 and 620. In some cases, the two virtual carriers may be configured to be fully complementary, i.e., the uplink of one virtual carrier is configured to align or correspond in the time domain with the downlink of another virtual carrier. Therefore, uplink and downlink resources always exist between two virtual carriers at the same time. Uplink and downlink signals and channels can be transmitted on at least one of the two virtual carriers. The two virtual carriers can have the same or different bandwidths and the same or different parameter sets (numerology). Similar concepts can be extended to multiple (e.g., three or more) virtual carriers, so that at any given time slot in the time domain, there are at least uplink time slots and downlink time slots between multiple virtual carriers. In some deployments, multiple virtual carriers can be partially complementary. For example, when the second virtual carrier includes downlink resources, the first virtual carrier may include uplink resources. In some examples, when the second virtual carrier includes uplink resources, the first virtual carrier includes downlink resources.

[0045] In some deployments, two virtual carriers 610 and 620 are aggregated to implement transmission together. An example of transmission may be a transmission during an initial access process, such as a PRACH transmission. Two virtual carriers may be provided within a physical carrier or cell, and each of the two virtual carriers is referred to as a set of continuous resource blocks, or subbands, or bandwidth parts (Bandwidth Part, BWP). In some examples, two different physical carriers or cells may be used to provide two virtual carriers. In other words, each virtual carrier involves frequency domain resources that may be provided by the same physical carrier / cell or different physical carriers / cells.

[0046] In some examples, the virtual carriers do not overlap with each other and may be adjacent to each other or occupy non-contiguous frequency domain resources (e.g., do not overlap in the frequency domain). In other examples, two virtual carriers may overlap on at least one frequency domain resource (e.g., at least partially overlap in the frequency domain). In some examples, more than two virtual carriers may be aggregated with each other. Although two aggregated virtual carriers are used as examples throughout this disclosure, similar concepts may be extended to aggregating multiple (e.g., three or more) virtual carriers so that uplink transmissions may be transmitted in uplink time slots on any one of the multiple virtual carriers. Downlink transmissions may be transmitted in downlink time slots on any one of the multiple virtual carriers.

[0047] In some deployments, a network (eg, a BS) transmits type 0 PDCCHs to a UE on multiple virtual carriers (eg, virtual carriers 610 and 620).

[0048] Figure 7 is a diagram showing a frame structure 700 of two virtual carriers according to various deployments. The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. Uplink resources 730 are shown as pure white blocks, while downlink resources 740 are shown as shaded blocks. The frame structure 700 includes two virtual carriers 710 and 720, and the combined frequency range of the virtual carriers 710 and 720 covers the initial downlink / uplink BWP 702 (e.g., the initial downlink BWP or the initial uplink BWP). The BS can transmit SSB in any one of the virtual carriers (e.g., virtual carrier 710). In some examples, the first information includes at least the time domain resources, bandwidth, and frequency position of the first downlink resource (e.g., virtual carrier 710). The second information includes at least the time domain resources, bandwidth, and position of the second downlink resource (e.g., virtual carrier 720). As Figure 7 As shown, in some examples, the bandwidth of the first downlink resource (e.g., the downlink resource of the virtual carrier 710) is the same as the bandwidth of the first virtual carrier (e.g., the virtual carrier 710). The bandwidth of the second downlink resource (e.g., the downlink resource of the virtual carrier 720) is the same as the bandwidth of the second virtual carrier (e.g., the virtual carrier 720).

[0049] In some deployments, the bandwidth and frequency position of the virtual carrier (e.g., virtual carrier 710) used to transmit the SSB is indicated in the PBCH of the SSB. More specifically, controlResourceSetZero in the PBCH is used to indicate the CORESET configuration (e.g., CORESET#0 750) for type 0 PDCCH transmission. The frequency position includes at least one of a starting frequency, an ending frequency, or an intermediate frequency. The virtual carrier 710 can then be defined as CORESET#0 750 or corresponds to CORESET#0750. The configuration of CORESET#0 750 also includes the CORESET duration (e.g., the number of symbols of CORESET#0).

[0050] In some deployments, the UE may determine the bandwidth and frequency location of the initial downlink / uplink BWP 702 based on CORESET#0 750. For example, the bandwidth of the initial downlink / uplink BWP 702 may be a multiple of the bandwidth of CORESET#0 750, such as twice. Figure 7 In some examples shown, the lowest RB (Resource block) of the initial downlink / uplink BWP 702 (e.g., the initial downlink BWP or the initial uplink BWP) is the lowest RB of CORESET#0. In other examples, the highest RB of the initial downlink / uplink BWP 702 (e.g., the initial downlink BWP or the initial uplink BWP) is the highest RB of CORESET#0. In some examples, the UE determines third information of the initial BWP (e.g., the initial downlink / uplink BWP 702) based on the first information. The third information includes at least the bandwidth or frequency position of the initial BWP. In some examples, determining the third information based on the first information includes at least one of the following items: determining that the bandwidth of the initial BWP is a multiple of the bandwidth of the first downlink resource, determining that the lower boundary of the bandwidth of the initial BWP (e.g., the lowest RB) is the same as the lower boundary of the first downlink resource, or determining that the upper boundary of the bandwidth of the initial BWP (e.g., the highest RB) is the same as the upper boundary of the first downlink resource.

[0051] Then, another CORESET (e.g., CORESET#1 760) in another virtual carrier (e.g., virtual carrier 720 or a second virtual carrier) is determined according to a predefined rule. In some examples, CORESET#1 760 has the same bandwidth as CORESET#0750. In some examples, the lowest RB of CORESET#1 760 is the lowest RB of the initial downlink / uplink BWP702. In some examples, the highest RB of CORESET#1 760 is the highest RB of the initial downlink / uplink BWP 702. CORESET#1 760 has the same number of symbols as CORESET#0. In some examples, determining the second information of the second virtual carrier 720 based on the first information includes one of the following items: determining the lower boundary of the first downlink resource as the upper boundary of the second downlink resource, or determining the upper boundary of the first downlink resource as the lower boundary of the second downlink resource, and the number of time domain resources of the first downlink resource is the same as the number of time domain resources of the second downlink resource.

[0052] Both CORESET#0 750 and CORESET#1 760 are associated with the same SS (e.g., SS#0), through which the time domain positions of CORESET#0 750 and CORESET#1 760 can be configured. Then, CORESET#0 750 and CORESET#1 760 exist in the same time domain resources, and CORESET#0 750 and CORESET#1 760 are frequency-domain multiplexed (FDMed) with each other. The UE monitors the type 0-PDCCH in both CORESET#0 750 and CORESET#1 760 according to the SS configuration. In some examples, the first information and the second information include the same SS, and the time domain positions of the first downlink resource and the second downlink resource are configured by the SS. The time domain resources of the first downlink resource are the same as the time domain resources of the second downlink resource.

[0053] As an example, CORESET#0 750 is configured with 24 RBs in the frequency domain and 2 symbols in the time domain. The initial downlink / uplink BWP 702 contains 48 RBs, which is twice the bandwidth of the 24 RBs of CORESET#0 750. The lowest RB of the initial downlink / uplink BWP 702 is the lowest RB of CORESET#0 750. Another 24 RBs in the higher frequency range within the initial downlink / uplink BWP 702 are determined as CORESET#1 760. CORESET#1 760 also has 2 symbols. The BS also configures SS for the UE through searchSpaceZero in the PBCH. As shown in the frame structure 700, the time domain positions of both CORESET 750 and 760 can be determined. Specifically, CORESET 750 and 760 use the same time domain resources. Then, the UE monitors Type 0-PDCCH in both CORESET#0 and CORESET#1.

[0054] In some deployments, the bandwidth and frequency position of the initial downlink / uplink BWP 702 (e.g., initial DL BWP or initial ULBWP) are indicated in the PBCH of the SSB (e.g., by controlResourceSetZero). In some examples, the UE determines (e.g., receives in the PBCH of the SSB) the first information and the second information based on the third information of the initial BWP (e.g., initial downlink / uplink BWP). The first information includes at least the time domain resources, bandwidth, and frequency position of the first downlink resource. The second information includes at least the time domain resources, bandwidth, and position of the second downlink resource. The third information includes at least the bandwidth or frequency position of the initial BWP. The initial downlink / uplink BWP 702 can be divided into a plurality of parts, each corresponding to a virtual carrier. For example, the initial downlink / uplink BWP 702 is divided into two parts, each of which corresponds to a virtual carrier 710 or 720, respectively. The division is performed by the UE based on a predefined rule. For example, by taking an average of the frequency range of the downlink / uplink BWP 702, the initial downlink / uplink BWP 702 is divided into multiple (e.g., two) equal parts in the frequency domain. In some examples, the initial downlink / uplink BWP 702 is divided into multiple (e.g., two) parts according to a specific ratio (e.g., a percentage or proportion of the frequency range of the initial downlink / uplink BWP 702 is allocated to each virtual carrier). Then, the bandwidth and location of the two CORESETs (e.g., CORESET#0 and CORESET#1) can be determined accordingly. The two CORESETs are located in the two virtual carriers 710 and 720 and have the same bandwidth as their respective virtual carriers, such as Figure 7 In some examples, the UE determines the first information and the second information based on the third information, including: the UE divides the bandwidth of the initial BWP into a first part corresponding to the bandwidth of the first downlink resource and a second part corresponding to the bandwidth of the second downlink resource.

[0055] Both CORESET#0 750 and CORESET#1 760 are associated with the same SS (e.g., SS#0), by which the time domain locations of CORESET#0 750 and CORESET#1 760 can be configured. Then, CORESET#0 750 and CORESET#1 760 exist in the same time domain resources and are FDMed to each other. The UE monitors the Type 0-PDCCH in both CORESET#0 750 and CORESET#1 760 according to the SS configuration.

[0056] As an example, the initial downlink / uplink BWP 702 is configured with 48 RBs. Then, the initial downlink / uplink BWP 702 is divided into two equal parts by averaging the bandwidth of the initial downlink / uplink BWP 702 over the two virtual carriers. Then, two CORESETs 750 and 760 can be determined respectively, each CORESET containing 24 RBs.

[0057] In some deployments, the BS sends two CORESET configuration sets for CORESET 750 and 760 to the UE (eg, using PBCH). Each of the two CORESET configuration sets corresponds to one virtual carrier. The UE monitors Type 0-PDCCH in both CORESET#0 750 and CORESET#1 760.

[0058] Regarding the mapping of the DMRS of type 0-PDCCH in CORESET#0 to the corresponding PDSCH, the frequency domain reference point is subcarrier 0 of the lowest numbered RB in the initial DL BWP or subcarrier 0 of the lowest numbered RB in CORESET#0. Regarding the mapping of the DMRS of type 0-PDCCH in CORESET#1 to the corresponding PDSCH, the frequency domain reference point is subcarrier 0 of the lowest numbered RB in the initial DL BWP or subcarrier 0 of the lowest numbered RB in CORESET#1. In some examples, the UE determines the mapping of the DMRS of the downlink control information to the downlink channel (e.g., PDSCH) of the first downlink resource based on a first frequency domain reference point, and the first frequency domain reference point is determined based on the lowest frequency resource (e.g., the lowest numbered RB) of the initial downlink BWP or the lowest frequency resource of the first downlink resource. The UE determines the mapping of the DMRS of the downlink control information to the downlink channel of the second downlink resource based on a second frequency domain reference point. The second frequency domain reference point is determined based on the lowest frequency resource of the initial downlink BWP or the lowest frequency resource of the second downlink resource.

[0059] As shown in the figure, some CORESETs (e.g., CORESET#1 in slot indexes 0, 1, 2, 5, 6, 7 in virtual carrier 720, and CORESET#0 in slot indexes 3, 4, 8, 9 in virtual carrier 710) are located in uplink resources 730. The BS cannot transmit PDCCH to the UE in such CORESETs in uplink resources 730. That is, the remaining CORESETs in downlink resources 740 (e.g., CORESET#1 in slot indexes 3, 4, 8, and 9 in virtual carrier 720, and CORESET#0 in slot indexes 0, 1, 2, 5, 6, and 7 in virtual carrier 710) can be used by the BS to transmit type 0-PDCCH. Compared with type 0-PDCCH transmission using a single TDD carrier, this will provide more time domain opportunities for transmitting type 0-PDCCH and corresponding PDSCH (i.e., SIB1 PDSCH).

[0060] In some deployments, PRACH may be transmitted on multiple virtual carriers. Figure 8 800 is a diagram showing a frame structure 800 of two virtual carriers according to various deployments. The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. Uplink resources 830 are shown as pure white blocks, while downlink resources 840 are shown as shaded blocks. Frame structure 800 includes two virtual carriers 810 and 820, and the combined frequency range of virtual carriers 810 and 820 covers the initial downlink / uplink BWP 802 (e.g., initial downlink BWP or initial uplink BWP). The BS can transmit SSB in any one of the virtual carriers (e.g., virtual carrier 810). RO 850 can be configured in both virtual carriers 810 and 820.

[0061] Fig. 9 900 is a diagram showing a frame structure of two virtual carriers according to various deployments. The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. Uplink resources 930 are shown as pure white blocks, while downlink resources 940 are shown as shaded blocks. Frame structure 900 includes two virtual carriers 910 and 920, and the combined frequency range of virtual carriers 910 and 920 covers the initial downlink / uplink BWP 902 (e.g., initial downlink BWP or initial uplink BWP). The BS can transmit SSB in any one of the virtual carriers (e.g., virtual carrier 910). RO 950 can be configured in both virtual carriers 910 and 920.

[0062] In some deployments, the BS may configure the frequency starting point of the RO 850 and 950 for the UE via RRC (Radio Resource Control) signaling (e.g., via message msg1-FrequencyStart). The BS may configure the number of FDMed ROs 850 and 950 for the UE via RRC signaling (e.g., via message msg1-FDM (Frequency-division multiplexing). For example, the number of FDMed ROs 850 and 950 may be a value selected from 1, 2, 4, and 8. Figure 8 and Fig. 9 As shown, the number of FDMed RO 850 is 2 and the number of FDMed RO 950 is 4.

[0063] In some deployments, the frequency position of the RO in each virtual carrier will be determined separately within each virtual carrier. In some examples, the uplink resource includes the RO. The RO includes a first RO in the first virtual carrier and a second RO in the second virtual carrier. The UE receives configuration information (e.g., first configuration information) for both the first RO and the second RO. The UE determines the frequency position of the first RO based on the RB of the first virtual carrier and the configuration information. The UE determines the frequency position of the second RO based on the RB of the second virtual carrier and the configuration information.

[0064] More specifically, if Figure 8 As shown, there are two FDMed ROs 850 configured by RRC signaling (eg, msg1-FDM) within each virtual carrier 810 or 820. For the virtual carrier 810, the frequency resources (eg, vertical dimension) are numbered and range from RB 0,vc1 To RB max,vc1 The lowest RB of the lowest frequency RO within the virtual carrier 810 may be determined by the UE according to msg1-FrequencyStart, for example, the value corresponding to the lowest RB of the lowest frequency RO is set to n. Then, RB n,vc1 The lowest RB of the lowest frequency RO within the virtual carrier 810 may be determined. For the virtual carrier 820, the frequency resources are from RB 0,vc2 Numbered to RB max,vc2 The lowest RB of the lowest frequency RO within the virtual carrier 820 may be determined by the UE according to msg1-FrequencyStart, for example, the value corresponding to the lowest RB of the lowest frequency RO is set to n. Then, RB n,vc2 This will be the lowest RB of the lowest frequency RO within the virtual carrier 820. Different virtual carriers may share other configurations for PRACH transmission (eg, time domain resources, PRACH format, etc.).

[0065] In some deployments, the BS may configure the frequency starting point of RO 850 and 950 for the UE via RRC signaling (e.g., via message msg1-FrequencyStart). The BS may configure the number of FDMed RO 850 and 950 for the UE via RRC signaling (e.g., via message msg1-FDM). For example, the number of FDMed RO 950 may be a value selected from 1, 2, 4, and 8. Fig. 9 As shown, the number of FDMed ROs 950 is 4. The BS configures the frequency starting point of the RO and the number of FDMed ROs based on the bandwidth of the initial downlink / uplink BWP 902. In some examples, the uplink resources include ROs. The ROs include a first RO in a first virtual carrier and a second RO in a second virtual carrier. The UE receives configuration information (e.g., second configuration information) for both the first RO and the second RO. The UE determines the frequency position of the lowest RB of the lowest frequency RO within the initial BWP 902 based on the bandwidth of the initial BWP and the configuration information. Then, some ROs are located within the virtual carrier 910, while other ROs are located within the virtual carrier 920.

[0066] like Fig. 9 As shown, there are four FDMed ROs 950 in the initial BWP 902. The frequency resources of the initial BWP 902 are divided into RB 0,BWP Numbered to RB max,BWP The lowest RB of the lowest frequency RO within the initial BWP 902 is determined according to msg1-FrequencyStart, for example, the value corresponding to the lowest RB of the lowest frequency RO is set to n. Then, RB n,BWP The lowest RB determined by the UE as the lowest frequency RO.

[0067] According to such a configuration, some ROs may be located in virtual carrier 910, while other ROs may be located in virtual carrier 920. ROs located within downlink resources 940 will be considered invalid ROs (e.g., ROs in slot indexes 1, 2, 5, 6 and virtual carrier 920, and ROs in slot indexes 3, 4 and virtual carrier 910). In some examples, the UE determines that the RO is invalid in response to determining that the RO is located in the downlink resources of the first virtual carrier's identifier or the downlink resources of the second virtual carrier's identifier.

[0068] In some deployments, the UE may determine that a particular RO may be considered a valid RO in response to determining that: 1) the RO is in an uplink resource, or 2) the RO is not earlier than an SSB in a PRACH slot and the RO is at least N times after the last downlink symbol. gapsymbols and at least N after the last SSB symbol gap Symbols start, where N gap In other words, in some examples, the UE determines that the RO is valid in response to determining at least one of the following: the RO is located in the uplink resources of the first virtual carrier or the uplink resources of the second virtual carrier; or the RO is not earlier than the SSB in the PRACH slot, and the RO starts at least a predetermined time period after the last downlink symbol and at least a predetermined time period after the last SSB symbol.

[0069] Different virtual carriers may share other configurations for PRACH transmission (eg, time domain resources, PRACH format, etc.).

[0070] In some deployments, the BS may configure two frequency resource configuration sets for ROs in different virtual carriers for the UE, respectively. In some examples, the uplink resource includes the RO. The RO includes a first RO and a second RO. The UE receives a first configuration of the number and frequency position of FDMed ROs for the first RO in the first virtual carrier and a second configuration of the number and frequency position of FDMed ROs for the second RO in the second virtual carrier. For example, the BS sends a first configuration parameter set msg1-FrequencyStart and msg1-FDM, which are used to indicate the frequency starting point and the number of FDMed ROs for the RO of the virtual carrier 810 / 910, respectively. Similarly, for virtual carrier 2, the BS sends a second configuration parameter set msg1-FrequencyStart and msg1-FDM, which are used to indicate the frequency starting point and the number of FDMed ROs for the RO of the virtual carrier 820 / 920, respectively. PRACH transmission in multiple virtual carriers can be implemented accordingly, thereby increasing the number of valid ROs, and in this way, it is expected to improve the efficiency of access to the network.

[0071] Some deployments involve determining the PRACH transmission power on multiple virtual carriers. In response to determining that the access procedure initiated by the PRACH transmission has failed, the UE sends the PRACH again to trigger a new access procedure. This process is called a PRACH retry. For a PRACH retry, the UE increases the PRACH transmission power according to a specific configuration. When multiple virtual carriers are used for PRACH transmission, there is a method for determining the PRACH transmission power. The configuration parameters related to power determination include at least one of the following items: the PRACH target received power at the gNB (preambleReceivedTargetPower), the maximum number of transmissions of the PRACH (preambleTransMax), and the power ramping step (PowerRampingStep). The PRACH target received power at the gNB is used to determine the initial power of the PRACH transmission. The maximum number of transmissions of the PRACH represents the maximum number of transmissions of the PRACH (themaximum transmission number of PRACH). The power ramping step represents the power increment for each retry. The BS can configure such parameters for the UE. Fig.10 1 is a table 1000 showing example definitions of transmission power parameters according to some deployments. As shown, in some examples, the PRACH target received power can be an integer from -202 to -60. In some examples, the maximum number of transmissions of the PRACH can be a number selected from the set n3, n4, n5, n6, n7, n8, n10, n20, n50, n100 and n200 (e.g., 3 times, 4 times, 5 times, 6 times, 7 times, 8 times, 10 times, 20 times, 50 times, 100 times and 200 times). In some examples, the power increase step size can be a number selected from dB0, dB2, dB4 and dB6.

[0072] In some deployments, the UE may implement one or more power increase counters for recording the number of power increases (N). The transmission power for the PRACH retry may then be determined based on the power increase. Fig.11 1 is a table 1100 showing an example relationship between transmission attempts and transmission power for a preamble of a PRACH according to some deployments. In the example shown in table 1100, P0 is the power for an initial transmission of the PRACH, which is determined according to the PRACH target received power and path loss of the PRACH, and Δ is the power increase step size, which is determined according to the power increase step size. For any retry of the preamble, the power can be determined by adding P0 and the product of N and Δ.

[0073] In some deployments, the UE receives a power parameter for each virtual carrier from the BS, each virtual carrier being independently configured with a power parameter. Different virtual carriers may share the same power increase counter. Then, for PRACH transmissions (including initial transmissions and retries), the power is determined according to the parameters configured for the virtual carrier transmitting the PRACH and the value of the power increase counter. In some examples, the UE receives at least one first power parameter for a first virtual carrier and at least one second power parameter for a second virtual carrier from the network. At least one first power parameter and at least one second power parameter are independently configured for the first virtual carrier and the second virtual carrier. The UE determines a first power for sending an uplink access signal on an uplink resource of the first virtual carrier based on the at least one first power parameter and the power increase counter. The UE determines a second power for sending another uplink access signal on another uplink resource of the second virtual carrier based on at least one second power parameter and a power increase counter (e.g., the same power increase counter).

[0074] Fig.12 1 is a table 1200 showing an example relationship between transmission attempts and transmission power for a preamble of a PRACH according to some deployments. 0,vc(1) is the power used for the initial transmission on the first virtual carrier (vc1), P 0,vc(2) is the power used for the initial transmission on the second virtual carrier (vc2), Δ vc(1) is the power increase step size for PRACH retries on vc1, and Δ vc(2) is the power increase step size for PRACH retry on vc2. Then, for the Nth PRACH retry, the UE can determine the power to be P 0,vc(x) +N×Δ vc(x) , where x represents the virtual carrier index on which the Nth PRACH retry is transmitted.

[0075] In some deployments, different virtual carriers share the same set of power parameters, and each virtual carrier has its own power increase counter. For PRACH transmissions (including initial transmissions and retries), the power is determined based on the configured parameters and the value of the power increase counter of the virtual carrier on which the PRACH is transmitted. For example, assume that P0 is the power for the initial transmission on the first virtual carrier, and Δ is the power increase step size for the PRACH retry. Then, for the Nth PRACH retry on the first virtual carrier, the power can be calculated using P0+N×Δ. In some examples, the UE receives at least one power parameter for the first virtual carrier and for the second virtual carrier from the network. The UE determines a first power for sending an uplink access signal on an uplink resource of the first virtual carrier based on at least one power parameter and a first power increase counter. The UE determines a second power for sending another uplink access signal on another uplink resource of the second virtual carrier based on at least one power parameter and a second power increase counter. The first power increase counter and the second power increase counter are implemented separately and may be different.

[0076] In some deployments, PRACH may be transmitted on multiple virtual carriers. Different methods may be implemented to determine the mapping between SSBs and ROs in multiple virtual carriers. In addition, depending on the RRC configuration, two or more SSBs may be associated with one RO, and different PRACH indexes may be associated with different SSBs associated with one RO. Depending on the RRC configuration, one SSB may also be associated with one or more ROs. Therefore, in some examples, the UE determines at least one valid RO in both the first carrier and the second carrier. The UE sorts the at least one valid RO and associates each of the at least one SSB with one of the at least one valid ROs.

[0077] In some deployments, valid ROs in multiple virtual carriers may be sorted or ranked according to predefined rules. Fig.13 1300 is a diagram showing an example frame structure 1300 of two virtual carriers according to various deployments. The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. Uplink resources 1330 are shown as pure white blocks, while downlink resources 1340 are shown as shaded blocks. The frame structure 1300 includes two virtual carriers 1310 and 1320, and the combined frequency range of the virtual carriers 1310 and 1320 covers the initial downlink / uplink BWP 1302 (e.g., the initial downlink BWP or the initial uplink BWP). The RO 1350 can be configured in both the two virtual carriers 1310 and 1320.

[0078] like Fig.13As shown, a total of 4 valid ROs 1350 (e.g., RO1 to RO4) are shown. These ROs will be arranged according to the following rules: first, in the ascending order of the frequency resource index of the frequency-reused PRACH opportunity; second, in the ascending order of the time resource index of the time-reused PRACH opportunity within the PRACH time slot; and third, in the ascending order of the index of the PRACH time slot. According to these three rules, the valid ROs are arranged in order as RO1, RO2, RO3, and RO4. In this example, one SSB is associated with one RO. In this example, three SSBs (e.g., SSB#0, SSB#1, and SSB#3) are actually transmitted. Fig.14 1400 is a table showing example associations between SSBs and ROs for transmission according to some deployments. As shown, SSB#0 is associated with RO1, SSB#1 is associated with RO2, and SSB#3 is associated with RO3. As shown, the SSBs are mapped to the arranged ROs based on the increasing order of the SSB index and the order of the arranged ROs. After one round of association, each actually transmitted SSB becomes associated with a RO in a one-to-one mapping. There are ROs (e.g., RO4) that are not associated with any SSB. The RO that ranks lowest in the arranged RO sequence will not be used to transmit PRACH.

[0079] In some deployments, valid ROs are determined, ranked / ordered, and associated with SSBs during an association period.More than one association period may be implemented such that the same mechanism may be implemented for any association period.

[0080] In some deployments, valid ROs in multiple virtual carriers may be ranked or ordered according to predefined rules. Fig.15 1500 is a diagram showing an example frame structure 1500 of two virtual carriers according to various deployments. The vertical dimension corresponds to the frequency domain, and the horizontal dimension corresponds to the time domain. Uplink resources 1530 are shown as pure white blocks, while downlink resources 1540 are shown as shaded blocks. The frame structure 1500 includes two virtual carriers 1510 and 1520, and the combined frequency range of the virtual carriers 1510 and 1520 covers the initial downlink / uplink BWP 1502 (e.g., the initial downlink BWP or the initial uplink BWP). The RO 1550 can be configured in both the two virtual carriers 1510 and 1520.

[0081] The valid ROs in the multiple virtual carriers 1510 and 1520 are arranged according to predefined rules. Fig.15As shown, a total of 8 valid ROs 1550 (e.g., RO1 to RO8) are shown. These ROs will be arranged according to the following rules: First, the ROs are arranged from the virtual carrier dimension, for example, starting from the virtual carrier with the lowest frequency or the lowest index. Then, the ROs can be arranged relative to each virtual carrier using the Fig.13 and Fig.14 Similar rules disclosed in the disclosure. For example, second, in the ascending order of frequency resource index of frequency-reused PRACH opportunities; third, in the ascending order of time resource index of time-reused PRACH opportunities within PRACH time slots; and fourth, in the ascending order of index of PRACH time slots. According to these four rules, valid ROs are arranged in this order as RO1 to RO8. These ROs will then be associated with SSBs.

[0082] In some examples, SSB-RO associations will be made within each virtual carrier separately. Assume that the SSBs actually transmitted are SSB#0, SSB#1, and SSB#3. Fig.16 1600 is a table showing example associations between SSBs and ROs for transmission according to some deployments. As shown, SSB#0 is associated with RO1 and RO5, SSB#1 is associated with RO2 and RO6, and SSB#3 is associated with RO3 and RO7. As shown, the SSBs are mapped to the arranged ROs based on the increasing order of the SSB index and the order of the arranged ROs. For the virtual carrier 1510, after one round of association, each actually transmitted SSB becomes associated with a RO in a one-to-one mapping. There is a RO (e.g., RO4) that is not associated with any SSB, and the RO is used to transmit the PRACH. Similarly, for the virtual carrier 1520, after one round of association, each actually transmitted SSB becomes associated with a RO in a one-to-one mapping. There is a RO (e.g., RO8) that is not associated with any SSB, and the RO is used to transmit the PRACH.

[0083] In some examples, SSB-RO associations may be performed cyclically across multiple virtual carriers. Fig.171700 is a table showing example associations between SSBs and ROs transmitted according to some deployments. In one example, relative to the frame structure 1500, the SSBs actually transmitted are SSB#0, SSB#1, and SSB#3. As shown, SSB#0 is associated with RO1 and RO4, SSB#1 is associated with RO2 and RO5, and SSB#3 is associated with RO3 and RO6. Mapping can be performed based on the index of the RO and the increasing order of the index of the SSB. In the first round of association, each SSB is associated with the RO in ascending order of the index of the RO, so that SSB#0 is associated with RO1, SSB#1 is associated with RO2, and SSB#3 is associated with RO3. In the second round of association, each SSB is associated with the RO in ascending order of the index of the RO continuing after the first round of association, so that SSB#0 is additionally associated with RO4, SSB#1 is additionally associated with RO5, and SSB#3 is additionally associated with RO6. Therefore, after two rounds of association, each actually transmitted SSB becomes associated with two ROs, which may cover different virtual carriers based on the number of valid ROs in each virtual carrier. Specifically, for the second round of association, there are ROs located in different virtual carriers, for example, RO4 is located in virtual carrier 1520, while other ROs are located in virtual carrier 1510. There are two ROs (e.g., RO7 and RO8) that are not associated with any SSB and are not used to transmit PRACH.

[0084] In some examples, at least one valid RO is sorted according to at least one of: a frequency resource index of at least one valid RO, a time resource index of at least one valid RO, and an index of a time slot; a first carrier and a second carrier; or the index of at least one valid RO is incremented across the first carrier and the second carrier.

[0085] Therefore, different mechanisms for mapping SSBs and ROs in multiple virtual carriers are defined, thereby increasing the number of valid ROs, in which way it is expected to achieve improved efficiency in access to the network.

[0086] In some deployments, other data may be transmitted on multiple virtual carriers. As described herein, two or more virtual carriers may exist in one initial DL / UL BWP or physical carrier. Then, some information other than type 0-PDCCH and RO may also be received or sent by the UE via multiple virtual carriers in one BWP or one physical carrier.

[0087] In some deployments, each SSB associated with a cell may be sent in a different virtual carrier. Each SSB may indicate the same or different CORESET#0 and search space#0 for type 0-PDCCH monitoring. The type 0-PDCCH and the corresponding PDSCH may then be received by the UE in the virtual carrier or in different virtual carriers.

[0088] In some deployments, the UE may select a virtual carrier for PRACH transmission based on measurements or configuration in SIB 1. Then, at least one of msg.2 and msg.4 may be transmitted by the BS and received by the UE in the same virtual carrier of the PRACH transmission.

[0089] In some deployments, system information other than MIB (Master Information Block) / SIB1 may be referred to as Other System Information (OSI). The UE may request OSI transmission from the BS by transmitting msg.1 or msg.3 by the UE. Then, the virtual carrier used for OSI transmitted by the BS and received by the UE is the same as the virtual carrier used for transmitting msg.1 or msg.3 for OSI request. In some deployments, OSI is transmitted by the BS and received by the UE in a predefined virtual carrier.

[0090] In some deployments, the page may be transmitted by the BS and received by the UE in a predefined virtual carrier, or transmitted in both virtual carriers.

[0091] Therefore, the deployment disclosed herein involves configuring transmission resources for signals and channels (including, for example, type 0PDCCH, RO, SSB / SIB1, OSI, msg.2 / msg.4, paging, etc.) during the initial access process on multiple virtual carriers. Providing multiple virtual carriers allows the number of effective resources to be increased in time, by which more efficient access to the network can be expected.

[0092] Fig.18 is a flow chart illustrating an example method 1800 for data communication according to various deployments. Figures 1 to 18 , the method 1800 may be performed by a UE (eg, UE 104 / 204) and a network including at least one BS (eg, BS 102 / 202). As used herein, a network refers to a network entity other than a UE.

[0093] At 1810, a network (eg, a BS) sends first information for a first virtual carrier to a UE. At 1820, the UE receives the first information for the first virtual carrier. In some examples, the first information includes configuration information of the first virtual carrier, such as CORESET#0, and SS#0.

[0094] At 1830, the UE determines second information for the second virtual carrier based on the first information. In some examples, the second information includes configuration information of the second virtual carrier, such as CORESET#1 and SS#0.

[0095] At 1840, in some examples, based on the first information and the second information, the UE sends an uplink access signal to the network on an uplink resource of the first virtual carrier or the second virtual carrier. An example of a network uplink access signal is a preamble for an initial access procedure. An example of an uplink resource is an RO. In some examples, the UE receives downlink control information from the network on at least one of a first downlink resource in the first virtual carrier or a second downlink resource in the second virtual carrier based on the first information and the second information. An example of the downlink control information is a type 0 PDCCH.

[0096] At 1850, in some examples, based on the first information and the second information, the network receives an uplink access signal from the UE on an uplink resource of the first virtual carrier or the second virtual carrier. In some examples, the network sends downlink control information to the UE on at least one of a first downlink resource in the first virtual carrier or a second downlink resource in the second virtual carrier based on the first information and the second information.

[0097] In some examples, the first information includes at least a frequency location, bandwidth, and time domain resource of the first downlink resource. The second information includes at least a location, bandwidth, and time domain resource of the second downlink resource. In some examples, the bandwidth of the first downlink resource is the same as the bandwidth of the first virtual carrier. The bandwidth of the second downlink resource is the same as the bandwidth of the second virtual carrier.

[0098] In some examples, the UE determines third information of an initial BWP (e.g., an initial downlink / uplink BWP) based on the first information. The third information includes at least a bandwidth or a frequency position of the initial BWP. In some examples, determining the third information based on the first information includes at least one of the following items: determining that the bandwidth of the initial BWP is a multiple of the bandwidth of the first downlink resource, determining that the lower boundary of the bandwidth of the initial BWP (e.g., the lowest RB) is the same as the lower boundary of the first downlink resource, or determining that the upper boundary of the bandwidth of the initial BWP (e.g., the highest RB) is the same as the upper boundary of the first downlink resource.

[0099] In some examples, determining the second information based on the first information includes one of the following items: determining the lower boundary of the first downlink resource as the upper boundary of the second downlink resource, determining the upper boundary of the first downlink resource as the lower boundary of the second downlink resource, and the number of time domain resources of the first downlink resource is the same as the number of time domain resources of the second downlink resource.

[0100] In some examples, the first information and the second information include the same SS, and the time domain location of the first downlink resource and the second downlink resource is configured by the SS. The time domain resource of the first downlink resource is the same as the time domain resource of the second downlink resource.

[0101] In some examples, the UE determines (e.g., receives in the PBCH of the SSB) the first information and the second information based on the third information of the initial BWP (e.g., the initial downlink / uplink BWP). The first information includes at least the time domain resources, bandwidth, and frequency position of the first downlink resource. The second information includes at least the time domain resources, bandwidth, and position of the second downlink resource. The third information includes at least the bandwidth or frequency position of the initial BWP.

[0102] In some examples, the UE determines the first information and the second information based on the third information including: the UE divides the bandwidth of the initial BWP into a first part corresponding to the bandwidth of the first downlink resource and a second part corresponding to the bandwidth of the second downlink resource.

[0103] In some examples, the UE determines mapping of the DMRS of the downlink control information to the downlink channel (e.g., PDSCH) of the first downlink resource based on a first frequency domain reference point, and the first frequency domain reference point is determined based on the lowest frequency resource (e.g., the lowest numbered RB) of the initial downlink BWP or the lowest frequency resource of the first downlink resource. The UE determines mapping of the DMRS of the downlink control information to the downlink channel of the second downlink resource based on a second frequency domain reference point. The second frequency domain reference point is determined based on the lowest frequency resource of the initial downlink BWP or the lowest frequency resource of the second downlink resource.

[0104] In some examples, the uplink resource includes an RO. The RO includes a first RO in the first virtual carrier and a second RO in the second virtual carrier. The UE receives configuration information (e.g., first configuration information) for both the first RO and the second RO. The UE determines the frequency position of the first RO based on the RB of the first virtual carrier and the configuration information. The UE determines the frequency position of the second RO based on the RB of the second virtual carrier and the configuration information.

[0105] In some examples, the uplink resource includes an RO. The RO includes a first RO in the first virtual carrier and a second RO in the second virtual carrier. The UE receives configuration information (e.g., second configuration information) for both the first RO and the second RO. The UE determines a frequency position of the first RO and a frequency position of the second RO based on the bandwidth of the initial BWP and the configuration information. The first configuration information and the second configuration information are different. In some examples, the UE determines that the RO is invalid in response to determining that the RO is located in a downlink resource identified by the first virtual carrier or a downlink resource identified by the second virtual carrier.

[0106] In some examples, the UE determines that the RO is valid in response to determining at least one of the following items: the RO is located in an uplink resource identified by the first virtual carrier or an uplink resource identified by the second virtual carrier; or the RO is not earlier than the SSB in the PRACH time slot, and the RO starts at least a predetermined time period after the last downlink symbol and at least a predetermined time period after the last SSB symbol.

[0107] In some examples, the uplink resources include ROs. The ROs include a first RO and a second RO. The UE receives a first configuration of the number and frequency positions of FDMed ROs for the first RO in the first virtual carrier and a second configuration of the number and frequency positions of FDMed ROs for the second RO in the second virtual carrier.

[0108] In some examples, the UE receives at least one first power parameter for a first virtual carrier and at least one second power parameter for a second virtual carrier from the network. The at least one first power parameter and the at least one second power parameter are independently configured for the first virtual carrier and the second virtual carrier. The UE determines a first power for sending an uplink access signal on an uplink resource of the first virtual carrier based on the at least one first power parameter and a power increase counter. The UE determines a second power for sending another uplink access signal on another uplink resource of the second virtual carrier based on the at least one second power parameter and a power increase counter (e.g., the same power increase counter).

[0109] In some examples, the UE receives at least one power parameter for a first virtual carrier and for a second virtual carrier from the network. The UE determines a first power for sending an uplink access signal on an uplink resource of the first virtual carrier based on the at least one power parameter and a first power increase counter. The UE determines a second power for sending another uplink access signal on another uplink resource of the second virtual carrier based on the at least one power parameter and the second power increase counter. The first power increase counter and the second power increase counter are implemented separately and may be different.

[0110] In some examples, the UE determines at least one valid RO in both the first carrier and the second carrier. The UE sorts the at least one valid RO and associates each of the at least one SSB with one of the at least one valid RO.

[0111] In some examples, at least one valid RO is sorted according to at least one of: a frequency resource index of at least one valid RO, a time resource index of at least one valid RO, and an index of a time slot; a first carrier and a second carrier; or the index of at least one valid RO is incremented across the first carrier and the second carrier.

[0112] Although various embodiments of the present solution have been described above, it should be understood that these embodiments are presented only as examples and not as limitations. Similarly, various diagrams may depict example architectures or configurations, which are provided to enable those of ordinary skill in the art to understand the example features and functions of the present solution. However, those of ordinary skill in the art will understand that the solution is not limited to the example architectures or configurations shown, but may be implemented using various alternative architectures and configurations. In addition, as those of ordinary skill in the art will understand, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited by any of the above-described illustrative embodiments.

[0113] It should also be understood that any reference to elements using names such as "first", "second", etc. in this article does not generally limit the number or order of these elements. Instead, these names can be used as a convenient means of distinguishing between two or more elements or instances of elements in this article. Therefore, the reference to the first and second elements does not mean that only two elements can be used or that the first element must precede the second element in some way.

[0114] In addition, those skilled in the art will appreciate that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, and symbols such as may be referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0115] Those of ordinary skill in the art will further understand that any of the various illustrative logic blocks, modules, processors, means, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of the two), firmware, various forms of programs or design codes in conjunction with instructions (which, for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.

[0116] Further, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components and circuits described herein may be implemented in or performed by an integrated circuit (IC), which may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device or any combination thereof. The logic blocks, modules and circuits may also include antennas and / or transceivers to communicate with various components within a network or within a device. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller or state machine. The processor may also be implemented as a combination of computing devices, for example, a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or a combination of any other suitable configurations that perform the functions described herein.

[0117] If these functions are implemented in software, they can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, and communication media include any medium that can enable a computer program or code to be transferred from one location to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or can be used to store the required program code in the form of instructions or data structures and any other medium that can be accessed by a computer.

[0118] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various modules are described as separate modules; however, as is clear to one of ordinary skill in the art, two or more modules may be combined to form a single module that performs associated functions according to an embodiment of the present solution.

[0119] In addition, memory or other storage devices and communication components can be used in the implementation of the present solution. It should be understood that, for the purpose of clarity, the above description describes the implementation of the present solution with reference to different functional units and processors. However, it will be apparent that any suitable distribution of functions between different functional units, processing logic elements or domains can be used without detracting from the present solution. For example, functions shown as being performed by separate processing logic elements or controllers can be performed by the same processing logic element or controller. Therefore, references to specific functional units are only references to suitable means for providing the described functions, rather than indicating a strict logical or physical structure or organization.

[0120] Various modifications to the embodiments described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the widest scope consistent with the new features and principles disclosed herein as described in the following claims.

Claims

1. A wireless communication method, comprising: The wireless communication device receives first information for a first virtual carrier from a network; as well as The wireless communication device determines second information for a second virtual carrier based on the first information; as well as At least one of the following: The wireless communication device sends an uplink access signal to the network on an uplink resource of the first virtual carrier or the second virtual carrier; or The wireless communication device receives downlink control information from the network on at least one of first downlink resources in the first virtual carrier or second downlink resources in the second virtual carrier based on the first information and the second information.

2. The method according to claim 1, further comprising: The first information includes at least the frequency position, bandwidth and time domain resource of the first downlink resource; The second information includes at least the location, bandwidth and time domain resources of the second downlink resource.

3. The method according to claim 2, further comprising: The bandwidth of the first downlink resource is the same as the bandwidth of the first virtual carrier; A bandwidth of the second downlink resource is the same as a bandwidth of the second virtual carrier.

4. The method according to claim 2, further comprising: The wireless communication device determines third information of an initial bandwidth part (BWP) based on the first information, wherein the third information includes at least a frequency position or a bandwidth of the initial BWP.

5. The method according to claim 4, wherein: Determining the third information based on the first information includes at least one of the following items: Determining a bandwidth of the initial BWP as a multiple of a bandwidth of the first downlink resource; Determine that a lower boundary of the bandwidth of the initial BWP is the same as a lower boundary of the first downlink resource; or An upper boundary of the bandwidth of the initial BWP is determined to be the same as an upper boundary of the first downlink resource.

6. The method according to claim 1, wherein: Determining, based on the first information, that the second information includes one of the following items: determining a lower boundary of the first downlink resource as an upper boundary of the second downlink resource; determining an upper boundary of the first downlink resource as a lower boundary of the second downlink resource; The number of time domain resources of the first downlink resources is the same as the number of time domain resources of the second downlink resources.

7. The method according to claim 2, wherein: The first information and the second information include the same search space set (SS), and the time domain positions of the first downlink resource and the second downlink resource are configured by the SS; and The time domain resources of the first downlink resources are the same as the time domain resources of the second downlink resources.

8. The method according to claim 1, further comprising: The wireless communication device determines first information and second information based on third information of an initial bandwidth part (BWP), wherein the first information includes at least a frequency position, bandwidth, and time domain resources of the first downlink resource, the second information includes at least a position, bandwidth, and time domain resources of the second downlink resource, and the third information includes at least a frequency position or bandwidth of the initial BWP.

9. The method according to claim 8, wherein: Determining the first information and the second information based on the third information includes: The wireless communication device divides a bandwidth of the initial BWP into a first portion corresponding to a bandwidth of the first downlink resource and a second portion corresponding to a bandwidth of the second downlink resource.

10. The method according to claim 1, further comprising: The wireless communication device determines mapping of a demodulation reference signal (DMRS) of the downlink control information to a downlink channel of the first downlink resource based on a first frequency domain reference point, wherein the first frequency domain reference point is determined based on a lowest frequency resource of an initial downlink bandwidth part (BWP) or a lowest frequency resource of the first downlink resource; and The wireless communication device determines the mapping of the DMRS of the downlink control information to the downlink channel of the second downlink resource based on a second frequency domain reference point, and the second frequency domain reference point is determined based on the lowest frequency resource of the initial downlink BWP or the lowest frequency resource of the second downlink resource.

11. The method according to claim 1, wherein: The uplink resources include random access channel (RACH) opportunities (ROs), the ROs including a first RO in the first virtual carrier and a second RO in the second virtual carrier; The method further comprises: The wireless communication device receives configuration information for both the first RO and the second RO; The wireless communication device determines a frequency position of the first RO based on a resource block (RB) of the first virtual carrier and the configuration information; and The wireless communication device determines a frequency position of the second RO based on the RBs of the second virtual carrier and the configuration information.

12. The method according to claim 1, wherein: The uplink resources include random access channel (RACH) opportunities (ROs), the ROs including a first RO in the first virtual carrier and a second RO in the second virtual carrier; The method further comprises: The wireless communication device receives configuration information for both the first RO and the second RO; and the wireless communication device determines a frequency position of the first RO and a frequency position of the second RO based on a bandwidth of an initial bandwidth part (BWP) and the configuration information.

13. The method according to claim 12, further comprising: The wireless communication device determines that the RO is invalid in response to determining that the RO is located in the identified downlink resources of the first virtual carrier or the identified downlink resources of the second virtual carrier.

14. The method according to claim 12, further comprising: The wireless communication device determines that the RO is valid in response to determining at least one of the following: The RO is located in the identified uplink resource of the first virtual carrier or the identified uplink resource of the second virtual carrier; or The RO is no earlier than a synchronization signal / physical broadcast channel (PBCH) block (SSB) in a physical random access channel (PRACH) slot, and the RO starts at least a predetermined time period after a last downlink symbol and at least a predetermined time period after a last SSB symbol.

15. The method according to claim 1, wherein: The uplink resource includes a random access channel (RACH) opportunity (RO), and the RO includes a first RO and a second RO; The method also includes receiving, by the wireless communication device, a first configuration of the number and frequency location of frequency domain multiplexed (FDMed) ROs for the first RO in the first virtual carrier and a second configuration of the number and frequency location of FDMed ROs for the second RO in the second virtual carrier.

16. The method according to claim 1, further comprising: The wireless communication device receives at least one first power parameter for the first virtual carrier and at least one second power parameter for the second virtual carrier from the network, wherein the at least one first power parameter and the at least one second power parameter are independently configured for the first virtual carrier and the second virtual carrier; and The wireless communication device determines, based on the at least one first power parameter and a power increase counter, a first power for transmitting the uplink access signal on the uplink resource of the first virtual carrier; and The wireless communication device determines a second power for sending another uplink access signal on another uplink resource of the second virtual carrier based on the at least one second power parameter and the power increase counter.

17. The method according to claim 1, further comprising: The wireless communication device receives at least one power parameter for the first virtual carrier and for the second virtual carrier from the network; as well as The wireless communication device determines, based on the at least one power parameter and a first power increase counter, a first power for transmitting the uplink access signal on the uplink resource of the first virtual carrier; as well as The wireless communication device determines a second power for sending another uplink access signal on another uplink resource of the second virtual carrier based on the at least one power parameter and a second power increase counter.

18. The method of claim 1, further comprising: The wireless communication device determines at least one valid random access channel (RACH) opportunity (RO) in both the first carrier and the second carrier; The wireless communication device sorts the at least one valid RO; as well as The wireless communication device associates each of at least one synchronization signal / physical broadcast channel (PBCH) block (SSB) with one of the at least one valid ROs.

19. The method according to claim 18, wherein: The at least one valid RO is sorted according to at least one of the following items: a frequency resource index of the at least one valid RO, a time resource index of the at least one valid RO, and an index of a time slot; the first carrier and the second carrier; or An index of the at least one valid RO is incremented across the first carrier and the second carrier.

20. A wireless communication device comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 1.

21. A computer program product comprising a computer readable program medium on which codes are stored, which when executed by at least one processor cause the at least one processor to implement the method according to claim 1.

22. A wireless communication method, comprising: The network sends first information for a first virtual carrier to the wireless communication device, wherein second information for a second virtual carrier is determined by the wireless communication device based on the first information; and At least one of the following: The network receives an uplink access signal from the wireless communication device on an uplink resource of the first virtual carrier or the second virtual carrier; or The network sends downlink control information to the wireless communication device on at least one of first downlink resources in the first virtual carrier or second downlink resources in the second virtual carrier based on the first information and the second information.

23. A wireless communication device, comprising at least one processor and a memory, wherein: The at least one processor is configured to read code from the memory and implement the method according to claim 22.

24. A computer program product comprising a computer readable program medium on which codes are stored, which when executed by at least one processor cause the at least one processor to implement the method according to claim 22.