Method for inter-rat spectrum sharing

Abstract

In the present disclosure, unified and specific schemes for inter-RAT spectrum utilization are described. By way of example only, the various RATs can include, but are not limited to, LTE, NR, 6G, and any current and future other mobile communication technologies. Such inter-RAT spectrum sharing can be implemented via dynamic resource provisioning, across RATs, across frequencies (e.g., carriers), and / or across cells, in the form of dual connectivity (DC) and / or carrier aggregation (CA), for specific wireless terminal devices or UEs.

Description

Technical Field

[0001] This disclosure relates generally to wireless communication networks, and more particularly to spectrum utilization between RATs (radio access technologies). Background Technology

[0002] In a wireless access network, various radio access technologies (RATs) can be used to achieve communication between wireless terminal devices and wireless access network nodes. The goal is to design a wireless access network that efficiently allocates wireless spectrum resources for this type of communication. Summary of the Invention

[0003] This disclosure relates generally to wireless communication networks, and more particularly to spectrum utilization between RATs (Radio Access Technologies).

[0004] In one example implementation, a method performed by a wireless terminal device is disclosed. The method may include: establishing a connection with at least one radio access network node on at least one radio spectrum resource via both a first radio access technology (RAT) and a second RAT, wherein the second RAT is different from the first RAT, and each of the at least one radio spectrum resource includes a pre-configured radio spectrum range; and using at least one radio spectrum resource for both the first and second RATs.

[0005] In the above example implementation, at least one wireless spectrum resource includes a pre-configured wireless spectrum range shared by the first RAT and the second RAT.

[0006] In any of the above example implementations, using a pre-configured radio spectrum range for the first RAT and the second RAT includes: using the pre-configured radio spectrum range to communicate with the first cell and the second cell, respectively, based on the first RAT and the second RAT, wherein the first cell and the second cell belong to different cell groups or are different but belong to the same cell group.

[0007] In any of the above example implementations, using a pre-configured radio spectrum range for the first RAT and the second RAT includes: using the pre-configured radio spectrum range to communicate with a single cell supporting both the first RAT and the second RAT.

[0008] In any of the above example implementations, using a pre-configured wireless spectrum range for the first RAT and the second RAT includes channel sharing between the first RAT and the second RAT.

[0009] In any of the above example implementations, using a pre-configured wireless spectrum range for the first RAT and the second RAT includes sharing at least one control channel between the first RAT and the second RAT.

[0010] In any of the above example implementations, the first RAT includes a 6G RAT, and the second RAT includes a 4G RAT or a 5G RAT; and at least one control channel shared between the first RAT and the second RAT includes a 6G control channel.

[0011] In any of the above example implementations, at least one control channel shared between the first RAT and the second RAT is configured to receive downlink control information (DCI) defined in both the first RAT and the second RAT.

[0012] In any of the above example implementations, the wireless terminal device’s ability to blindly detect DCI is counted to one of the first RAT and the second RAT or counted to both the first RAT and the second RAT by a scaling factor.

[0013] In any of the above example implementations, the control information carried in at least one control channel shared by the first RAT and the second RAT includes a RAT flag indicating which of the first RAT and the second RAT the control information is intended for.

[0014] In any of the above example implementations, the control message carried in at least one control channel shared by the first RAT and the second RAT is configured to be the size of a format adapted to both the first predefined control information size of the first RAT and the second predefined control information size of the second RAT, and when carrying a control message that includes the shorter of the first predefined control information size and the second predefined control information size, the control message is padded with zero bits.

[0015] In any of the above example implementations, using the pre-configured wireless spectrum range for the first RAT and the second RAT includes resource sharing between the first RAT and the second RAT.

[0016] In any of the above example implementations, the resources of the first RAT shared with the second RAT are indicated by the control channel of the first RAT.

[0017] In any of the above example implementations, the first RAT is a 6G RAT, and the second RAT is a 4G RAT or a 5G RAT.

[0018] In any of the above example implementations, at least one wireless spectrum resource includes a first pre-configured wireless spectrum range and a second pre-configured spectrum range used by the first RAT and the second RAT.

[0019] In any of the above example implementations, the downlink spectrum resources of the first pre-configured wireless spectrum range and / or the second pre-configured spectrum range are dynamically scheduled by a single DCI.

[0020] In any of the above example implementations, the RAT of a single DCI is determined by the wireless terminal device via blind detection or is pre-configured.

[0021] In any of the above example implementations, at least one RAT-specific field or RAT common field of the first RAT and the second RAT is included in a single DCI.

[0022] In any of the above example implementations, the hybrid automatic repeat request acknowledgement (HARQ-ACK) feedback associated with the first RAT and the second RAT is grouped in a codebook.

[0023] In another example implementation, a method performed by a radio access network node is disclosed. The method may include: establishing a connection with a wireless terminal device on at least one radio spectrum resource via both a first radio access technology (RAT) and a second RAT, wherein the second RAT is different from the first RAT, and each of the at least one radio spectrum resource includes a pre-configured radio spectrum range; and communicating with the wireless terminal device using the at least one radio spectrum resource for the first RAT and the second RAT.

[0024] The paper also discloses a wireless terminal device or wireless access network node that embodies any of the above methods. The wireless terminal device or wireless access network node may include a processor and a memory, wherein the processor is configured to read computer code from the memory, causing the wireless terminal device or wireless access network node to execute any of the above methods.

[0025] A non-transitory computer-readable program medium is also disclosed, on which computer code is stored. When executed by a processor of a wireless terminal device or wireless access network node according to any of the above methods, the computer code is configured to cause the processor to implement any of the above methods.

[0026] Other aspects and alternatives to the above embodiments and their implementation are described in more detail in the accompanying drawings, description and claims. Attached Figure Description

[0027] Figure 1 An example wireless communication network including a wireless access network, a core network, and a data network is shown.

[0028] Figure 2 An example radio access network is shown, comprising multiple mobile stations / terminals or user equipment (UEs) and radio access network nodes, which communicate with each other via an over-the-air wireless communication interface.

[0029] Figure 3 An example radio access network (RAN) architecture is shown.

[0030] Figure 4 An example communication protocol stack is shown in a wireless access network node or wireless terminal device that includes various network layers.

[0031] Figure 5 An example core network is shown.

[0032] Figure 6 An example implementation of spectrum utilization between RATs is shown.

[0033] Figure 7 Another example implementation for spectrum utilization between RATs is shown.

[0034] Figure 8 Another example implementation for spectrum utilization between RATs is shown.

[0035] Figure 9 An example scheme for sharing control channels between different RATs is shown.

[0036] Figure 10 An example cellless system is shown.

[0037] Figure 11 It shows in Figure 10 Example spectrum utilization schemes in cellless systems.

[0038] Figure 12 It shows in Figure 10 Another example of spectrum utilization scheme in a cellless system. Detailed Implementation

[0039] The techniques described in this disclosure can be used to implement spectrum sharing between RATs in a wireless access system. In this disclosure, the term "over-the-air interface" is used interchangeably with "air interface" or "wireless interface." The term "exemplary" is used to mean "an example of" and, unless otherwise stated, does not imply an ideal or preferred example, implementation, or embodiment. Section headings in this disclosure are used to facilitate understanding of the disclosed implementations and are not intended to limit the techniques disclosed in a section to the corresponding section. The disclosed implementations may be further embodied in various different forms, and therefore, the scope of this disclosure or the claimed subject matter is intended to be construed as not being limited to any embodiment set forth below. Various implementations may be embodied as methods, apparatus, components, systems, or non-transitory computer-readable media. Accordingly, embodiments of this disclosure may take the form of hardware, software, firmware, or any combination thereof.

[0040] This disclosure describes uniform and specific schemes for inter-RAT spectrum utilization. By way of example only, various RATs may include, but are not limited to, LTE, NR, 6G, and any other current and future mobile communication technologies. Such inter-RAT spectrum sharing can be implemented for a specific radio terminal equipment or UE in the form of dual connectivity (DC) and / or carrier aggregation (CA) via dynamic resource provisioning across RATs, across frequencies (e.g., carriers), and / or across cells.

[0041] Wireless communication network Figure 1The example wireless communication network shown as 100 may include wireless terminal devices or user equipment (UEs) 110, 111, and 112, a carrier network 102, various service applications 140, and other data networks 150. The wireless terminal devices or UEs may alternatively be referred to as wireless terminals. The carrier network 102 may include, for example, access network nodes 120 and 121, and a core network 130. The carrier network 110 may be configured to transmit voice, data, and other information (collectively referred to as data services) between UEs 110, 111, and 112, between a UE and a service application 140, or between a UE and other data networks 150. Access network nodes 120 and 121 may be configured as various wireless access network nodes (WANNs, alternatively referred to as base stations) to interact with the UE on one side of a communication session and the core network 130 on the other side. The term "access network" can be more broadly used to refer to the combination of wireless terminal devices 110, 111, and 112 and access network nodes 120 and 121. The radio access network can also be referred to as the radio access network (RAN). The core network 130 may include various network nodes configured to control communication sessions and perform network access management and service routing. Service applications 140 may be hosted by various application servers deployed outside the core network 130 but connected to it. Similarly, other data networks 150 may also be connected to the core network 130.

[0042] exist Figure 1 In the example wireless communication network 100, each UE can communicate with each other via a radio access network. For example, UEs 110 and 112 can connect to the same access network node 120 and communicate through that same access network 120. UEs can communicate with each other via the access network and the core network. For example, UE 110 can connect to access network node 120, while UE 111 can connect to access network node 121, and thus, UEs 110 and UE 111 can communicate with each other through access network nodes 120 and 121 and the core network 130. UEs can also communicate with the serving application 140 and the data network 150 via the core network 130. Furthermore, as shown in 113, each UE can communicate directly with each other via sidelink communication.

[0043] Figure 2An example system diagram of a radio access network 120 including a WANN 202 serving UEs 110 and 112 via air interface 204 is also shown. Radio transmission resources for air interface 204 include a combination of frequency resources, time resources, and / or spatial resources. Each of UEs 110 and 112 can be a mobile or fixed terminal device equipped with a mobile access unit (such as a SIM / USIM (Subscriber Identity Module / Universal Subscriber Identity Module) module) for accessing the wireless communication network 100. Each of UEs 110 and 112 can be implemented as a terminal device including, but not limited to, mobile phones, smartphones, tablets, laptops, in-vehicle communication devices, roadside communication devices, sensor devices, smart appliances (such as televisions, refrigerators, and ovens), or other devices capable of wireless communication over a network. Figure 2 As shown, each of the plurality of UEs (such as UE 112) may include transceiver circuitry 206 coupled to one or more antennas 208 to enable wireless communication with WANN 120 or with another UE (such as UE 110). Transceiver circuitry 206 may also be coupled to processor 210, which may also be coupled to memory 212 or other storage devices. Memory 212 may be transient or non-transient and may store computer instructions or code therein that, when read and executed by processor 210, cause processor 210 to implement the various methods described herein.

[0044] Similarly, WANN 120 may include a wireless base station or other wireless network access point capable of wirelessly communicating with one or more UEs and the core network 130 via air interface 204. For example, WANN 120 may be implemented as, but is not limited to, a 2G base station, a 3G NodeB, an LTE eNB, a 4G LTE base station, a 5G gNB, a 5G NR base station, a 5G centralized unit base station, or a 5G distributed unit base station. Each type of WANN can be configured to perform a corresponding set of wireless network functions. WANN 202 may include transceiver circuitry 214 coupled to one or more antennas 216 (antennas 216 may include various forms of antenna towers 218) to enable wireless communication with UEs 110 and 112. Transceiver circuitry 214 may also be coupled to one or more processors 220, which may also be coupled to memory 222 or other storage devices. The memory 222 may be transient or non-transient and may store instructions or code therein that, when read and executed by one or more processors 220, cause one or more processors 220 to perform the various functions of the WANN 120 described herein.

[0045] Such as Figure 2 In the example wireless access network described, data packets can be transmitted as protocol data units (PDUs). Data can be packaged into PDUs using nested and / or layered protocol headers at various network layers. Once a connection is established between the transmitting and receiving ends (e.g., a radio link control (RRC) connection), PDUs can be transmitted between the transmitting device or receiving end (these terms are used interchangeably) and the receiving device or receiving end (also the terms are used interchangeably). Either the transmitting or receiving device can be a wireless terminal device, such as... Figure 2 Devices 110 and 120; or wireless access network nodes, such as Figure 2 Node 202. Each device can be a transmitting device and a receiving device for bidirectional communication.

[0046] Figure 1 The core network 130 may include various network nodes or functions that are geographically distributed and interconnected to provide network coverage for the service area of ​​the carrier network 102. These network nodes may be implemented as dedicated hardware network nodes. Alternatively, these network nodes may be virtualized and implemented as virtual machines or software entities. Each of these network nodes may be configured with one or more types of network functions that collectively provide configuration and routing capabilities for the core network 130.

[0047] Returning to the Radio Access Network (RAN). Figure 3 An example RAN 340 communicating with core network 310 and radio terminals UE1 through UE7 is shown. RAN 340 may include one or more types of radio base stations or WANNs 320 and 321, which may include, but are not limited to, gNBs, eNodeBs, NodeBs, or other types of base stations (for simplicity, ...). Figure 3 (Only gNB is shown in the image). RAN340 can backhaul to core network 310 via, for example, an NG interface.

[0048] Figure 3 The WANN can be configured to communicate with each other via inter-node interfaces. For example, gNBs can communicate with each other via an Xn interface. As another example, a 5G base station gNB can communicate with an LTE base station (such as a NodeB or eNodeB) via an X2 interface. In some example implementations, for example, WANN 320 may further include multiple individual access network nodes in the form of a Central Unit (CU) 322 and one or more Distributed Units (DUs) 324 and 326. In some embodiments, the CU can be a gNB Central Unit (gNB-CU), and the DU can be a gNB Distributed Unit (gNB-DU). CU 322 can be connected to DU1 324 and DU2 326 via various inter-node interfaces (e.g., F1 interfaces). Each of the various inter-node interfaces can be further divided into a control plane interface and a user plane interface. As a specific example, the F1 interface between the CU and DU may further include an F1-C interface and an F1-U interface, which can be used to carry control plane information and user plane data, respectively. Similarly, the Xn interface or X2 interface may include an Xn-C interface and an Xn-U interface or an X2-C interface and an X2-U interface. For the purposes of this disclosure and its claims, each CU and DU is considered a separate access network node. Therefore, the F1 interface falls within the definition of an inter-node communication interface. Furthermore, although the various embodiments described below are provided in the context of 5G cellular wireless networks, the basic principles described herein are applicable to other types of wireless access networks, including but not limited to other generations of cellular networks, as well as Wi-Fi, Bluetooth, ZigBee, and WiMax networks.

[0049] The UE can connect to the network via the WANN 320 through the air interface. The UE can be served by at least one cell. Each cell is associated with a coverage area. These cells can be alternatively referred to as serving cells. The coverage areas between cells may partially overlap. Each UE can actively communicate with at least one cell and may connect to or be able to connect to more than one cell. Figure 1 In the example, UE 1, UE 2, and UE 3 may be served by cell 1 330 of DU1, while UE 4 and UE 5 may be served by cell 2 332 of DU1, and UE 6 and UE 7 may be served by cell 3 associated with DU2. In some implementations, a UE may be served by two or more cells simultaneously. Each UE may be mobile, and the signal strength and quality at the UE from the various cells may depend on the UE's location and mobility.

[0050] In some example implementations, Figure 3 The cells shown can be alternatively referred to as serving cells. Serving cells can be grouped into serving cell groups (CGs). A serving cell group can be a master CG (MCG) or a secondary CG (SCG). Within each type of cell group, there can be one master cell and one or more secondary cells. For example, the master cell in an MSG can be called a PCell, while the master cell in an SCG can be called a PScell. Secondary cells in either an MCG or an SCG can be called SCells. Master cells including both PCells and PScells can be collectively referred to as spCells (special cells). All of these cells can be called serving cells or cells. The terms "cell" and "serving cell" are generally used interchangeably unless specifically distinguished. The term "serving cell" can refer to a cell that is currently serving, will serve, or may serve a UE. In other words, a "serving cell" may not currently be serving a UE. Although the various embodiments described below may sometimes refer to one type of serving cell described above, the basic principles apply to all types of serving cells in both types of serving cell groups.

[0051] Figure 4 Further demonstrated in Figures 1 to 3 A simplified diagram illustrating the various network layers involved in transmitting a user plane PDU from a transmitting device 402 to a receiving device 404 in an example wireless access network. Figure 4 It is not intended to include all the necessary equipment components or network layers for handling PDU transmissions. Figure 4This illustrates that data encapsulated at the upper network layer 420 of the transmitting device 402 can be transmitted to the corresponding upper layer 430 (such as the Radio Resource Control or RRC layer) at the receiving device 304. This transmission is via the Packet Data Convergence Protocol (PDCP) layer of the transmitting device, not in... Figure 4 The layers 422 and 434 are shown in the diagram, including the Radio Link Control (RLC) layer, the Physical (PHY) layer of the transmitting and receiving devices, the radio interface (as shown in 406), and the Media Access Control (MAC) layer and RLC layer of the receiving device. Various network entities in each of these layers can be configured to handle the transmission and retransmission of PDUs.

[0052] exist Figure 4 In the middle, the upper layer 420 can be called layer-3 or L3, while the intermediate layers (such as RLC layers and / or MAC layers and / or PDCP layers, not in the middle) Figure 4 (As shown in the diagram) can be collectively referred to as Layer-2 or L2, and the term Layer-1 is used to refer to layers (such as the physical layer and the layers associated with the radio interface). In some instances, the term "lower layer" can be used to refer to the set of L1 and L2, while the term "higher layer" can be used to refer to Layer-3. In some cases, the term "lower layer" can be used to refer to a layer below the current reference layer in L1, L2, and L3. Control signaling can be initiated and triggered within each of L1 through L3 and within the various network layers therein. These signaling messages can be encapsulated and concatenated into lower-layer packets and transmitted via allocated air radio resources and control or data over the interface. The term "layer" typically includes its various corresponding entities. For example, the MAC layer includes corresponding MAC entities that may be created. For example, Layer-1 includes the PHY entity. As another example, Layer-2 includes the MAC layer / entity, RLC layer / entity, Service Data Adaptation Protocol (SDAP) layer, and / or PDCP layer / entity.

[0053] Figure 5 An example partitioning of network node functions in core network 130 is shown. Although Figure 5 Only a single instance of a network node with some functionalities is shown, but those skilled in the art will understand that each of these network nodes can be instantiated as multiple instances, distributed throughout the core network 130. For example... Figure 5As shown, the core network 130 may include, but is not limited to, access management network function (AMF) node 530, session management function (SMF) node 540, user plane function (UPF) node 550, policy control function (PCF) node 520, and application data management function (AF) node 510.

[0054] AMF node 530 can communicate with access network 120, SMF node 540, and PCF node 520 via communication interfaces 522, 532, and 524, respectively, and can be responsible for providing UE registration, authentication, and access to core network 130, as well as allocating SMF node 540 to support specific UE communication sessions. The SMF node 540 allocated by AMF node 530 can then be responsible for allocating UPF node 550 to support specific UE communication sessions, and controlling these allocated UPF nodes 550 via communication interface 546. Alternatively, or further, in some embodiments, UPF node 550 can be directly allocated by AMF node 530 via interface 534 and controlled by SMF node 540 via communication interface 546. Access policies and session routing policies applicable to the UE can be managed by PCF node 520, which transmits these policies to AMF node 530 and SMF node 540 via communication interfaces 524 and 523, respectively. PCF node 520 can further be responsible for managing user subscriptions 512 to service application 140 via AF node 510. Figure 5 The signaling and data exchange between various types of network nodes indicated by various connection lines through various communication interfaces can be carried by signaling or data messages that follow a predetermined format or protocol.

[0055] To support a specific end-to-end communication task requested by the UE, a communication session can be established to support the data service pipeline used to transmit that specific end-to-end data communication service. For example... Figure 5The carrier network portion of the data service pipeline shown in 570 may involve one or more network nodes in access network 120 and a set of UPF nodes 552, 554, and 556 in core network 130, such as a set of SMF nodes 542 and 544 selected and controlled by AMF node 530 responsible for establishing and managing communication sessions. Data services are routed between a UE at one end of the data service pipeline, the carrier network portion of the data service pipeline (including a set of network nodes in access network 120 and selected UPF nodes 552, 554, and 556 in core network 130), and the other end of the data service pipeline (e.g., including another UE, a service application or application server 140, or a data network 150).

[0056] Wireless Network Generation, Wireless Spectrum Sharing and Cross-Carrier Scheduling The allocation and use of radio spectrum has always been essential for the development and advancement of each generation of cellular and cellless radio access systems. The more recent 5th Generation (5G) mobile communication technology, or the future 6th Generation (6G) mobile communication technology, is facing high demand. Based on current developments, 5G systems are also beginning to support additional enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC). As new access features and technologies are developed and adopted in each generation of radio systems, or between new generations of radio systems, it becomes necessary to reuse radio spectrum resources used by previous generations through new resource allocation and scheduling schemes, enabling the sharing of radio spectrum resources between generations of radio technologies to improve the efficiency of radio spectrum utilization.

[0057] For example, in 5G mobile communication technology, alternatively referred to as New Radio (NR), dynamic spectrum sharing (DSS) with the Long-Term Evolution (LTE) of 4G has been developed and adopted. In some example implementations of LTE-NR spectrum sharing, a portion of LTE spectrum resources may be allocated for NR communications. However, the NR Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH) may not be permitted to be transmitted on LTE PDCCH and Cell-Specific Reference Signal (CRS) resources to avoid unintentional impacts on the LTE system.

[0058] In some implementations, the radio spectrum can be used for communication between wireless terminal equipment and access network nodes on a carrier or subcarrier basis. When multiple carriers or subcarriers are used to support the communication of a single mobile terminal equipment, inter-carrier resource scheduling can be implemented to reduce scheduling overhead and thus improve resource utilization efficiency. For example, PCell and SCell in NR can utilize different radio carriers. When supporting UE communication, NR PDCCH enhancements for cross-carrier scheduling within the RAT can be introduced, including scheduling PDSCH or PUSCH on PCell via PDCCH of SCell to offload PCell PDCCH.

[0059] In the following further disclosure, uniform and specific schemes for inter-RAT spectrum utilization or sharing are described. By way of example only, various RATs may include, but are not limited to, LTE (4G), NR (5G), 6G, and any other current and future mobile communication technologies. Such inter-RAT spectrum utilization or sharing can be implemented for a specific radio terminal equipment or UE in the form of dual connectivity (DC) and / or carrier aggregation (CA) via semi-static and / or dynamic resource provisioning across RATs, across frequencies (e.g., carriers), and / or across cells.

[0060] In the following disclosure, the term "spectrum resource" may be used to refer to a range of radio spectrum predefined, preconfigured, or otherwise allocated in the air interface. As an example, a spectrum resource may include one or more predetermined, preconfigured, or allocated radio carriers or subcarriers. As another example, a spectrum resource may, for example, refer to one of frequency range 1 (FR1) and frequency range 2 (FR2), as well as other wireless communication frequency bands and / or combinations thereof. Spectrum resources may be licensed or unlicensed. A cell may utilize a single carrier or a combination of carriers. The term "spectrum resource" may be used interchangeably with "spectral resource," "frequency range," etc. Sharing spectrum resources by different cells or different RATs may include sharing at various granular levels on one or both of frequency and / or time (e.g., resource blocks, channels, subcarriers, carriers, or other levels in the frequency domain, or frames, subframes, time slots, and symbols in the time domain).

[0061] In the following further disclosures, the term "dynamic" (such as in "dynamic scheduling," "dynamic spectrum sharing," etc.) may be used to refer to resource provisioning that occurs within a communication session, such as downlink resource scheduling via downlink control information. For example, resource allocation by radio resource control (RRC) information elements may be considered static rather than dynamically provisioned.

[0062] Dynamic RAT Inter-Spectrum Sharing When applying Dynamic Spectrum Sharing (DSS), it is possible to re-farm spectrum allocated to a first RAT technology (e.g., 6G technology, referred to as the current technology) for use by a second RAT technology (e.g., 4G / 5G technology, referred to as the legacy technology). In other words, spectrum sharing between radios of the first RAT can be dynamically shared with the second RAT.

[0063] In some example implementations, referred to below as Option 1, the same spectrum resource can be used or shared by different RATs for the same UE. Such spectrum resource sharing can be provided semi-statically or dynamically. As a specific example, such as... Figure 6As shown, the same frequency resource (e.g., a carrier on the frequency band) at f1 can be configured to be shared by a first cell 602 of a first RAT (e.g., a 6G RAT) and a second cell 604 of a second RAT (e.g., a 4G / 5G RAT) for a specific radio terminal device 606 (e.g., UE 1). Dynamic resource sharing can be provided by a radio access network node 610, which can be configured to support both the first and second RATs.

[0064] In some other alternative implementations, referred to below as Option 2, the same spectrum resource can be used and shared by different RATs to serve different UEs, such that the same UE does not communicate with more than one RAT on the same spectrum resource. However, the same UE can use two or more different RATs on different spectrum resources in a multi-connectivity (e.g., dual-connectivity or DC) configuration to enhance overall communication bandwidth. In other words, the same UE may not access the same spectrum resource from different RATs, but the same spectrum resource can be dynamically shared by different RATs communicating with different UEs.

[0065] like Figure 7 As shown in the example for option 2, the same frequency resource at f1 can be configured for a first UE 706 (UE 1) using a first cell 702 of a first RAT (e.g., a 6G RAT) and for a second UE 708 (UE 2) using a second cell 704 of a second RAT (e.g., a 4G / 5G RAT) (in other words, different UEs share the same spectrum resource using different RATs). Dynamic resource sharing can be provided by a radio access network node 710, which can be a single radio access network node (e.g., a 6G / 5G / 4G NodeB) configured to support both the first and second RATs, or a separate radio network node (e.g., a 6G NodeB and a 4G / 5G NodeB) configured to support both the first and second RATs.

[0066] As mentioned above Figure 7 As further illustrated in option 2, the same UE1 can communicate on different frequency resources in a first RAT (e.g., a 6G RAT) and another RAT (e.g., a 4G / 5G RAT). These different frequency resources can be considered together as shared by the first RAT and other RATs. Again, such sharing can be provided dynamically. Specifically, as... Figure 7As shown, different frequency resources f1 and f2 can be associated with a first cell 702 of a first RAT (e.g., a 6G RAT) and another cell 705 of another RAT (e.g., a 4G / 5G RAT), and used respectively to communicate with the same UE 706 (UE 1). The first cell 702 and the other cell 705 can be provided by one or more radio access network nodes 710 and 712, respectively, and in this way, the same UE 706 (UE 1) can use frequency resources f1 and f2 to connect to the first cell 702 and the other cell 705 via a DC (dual connectivity) mechanism.

[0067] like Figure 8 As further shown, when the same radio access network node 810 uses different frequency resources at f1 and f2 for the first cell 802 and other cells 805 respectively, the utilization of f1 and f2 can be configured to provide communication to the same UE 806 via RAT inter-carrier aggregation (CA).

[0068] In some example implementations of Option 1, the same spectrum resource can be used for different cells corresponding to different RATs of the same UE, and different cells can be associated with different cell groups. For example, the same frequency resource f1 can be configured with a cell number (or cell ID, e.g., cell #n) belonging to cell group #1 associated with a first RAT (e.g., 6G RAT), while the same frequency resource f1 can also be configured with a cell number (e.g., cell #m) belonging to cell group #2, which is different from cell group #1 and associated with a second RAT (e.g., 4G / 5G RAT). In such a configuration, DSS can be implemented via DC. In other words, the same UE can simultaneously use the same frequency resource dynamically shared between different RATs via DSS, connecting to different cells in different cell groups via different RATs.

[0069] In some alternative implementations of Option 1, the same spectrum resource can be used for different cells corresponding to different RATs of the same UE, and the different cells can be associated with the same cell group but have different cell numbers or cell IDs. For example, the same frequency resource f1 can be configured to belong to cell #n of cell group #1 associated with a first RAT (e.g., 6G RAT), while the same frequency resource f1 can also be configured to belong to cell group #1 but to cell #m (m≠n) associated with a second RAT (e.g., 4G / 5G RAT). In this way, the same frequency resource can be dynamically shared between different cells of different RATs via a carrier aggregation mechanism through a DSS in the same cell group, wherein the shared frequency resource can be regarded as an aggregated carrier.

[0070] In some alternative implementations of Option 1 above, the same spectrum resource can be used for the same cell corresponding to and supporting multiple different RATs for the same UE. For example, the same frequency resource f1 can be configured to be associated with and support both a first RAT (e.g., 6G RAT) and a second RAT (e.g., 4G / 5G RAT). In some implementations, the same frequency resource f1 can be provided semi-statically or dynamically between the first RAT (e.g., 6G RAT) and the second RAT (e.g., 4G / 5G RAT). For example, the same frequency resource f1 can be used for both the first RAT (e.g., 6G RAT) and the second RAT (e.g., 4G / 5G RAT), where different subband resources are semi-statically configured in the frequency resource f1, and these subband resources may overlap or not. As another example, the same frequency resource f1 can be dynamically scheduled for both the first RAT (e.g., 6G RAT) and the second RAT (e.g., 4G / 5G RAT). Specifically, by dynamically or semi-statically switching or using a target RAT applied to the same frequency resource or the same cell, the same frequency resource f1 can be used for the first RAT (e.g., 6G RAT) and the second RAT (e.g., 4G / 5G RAT).

[0071] In various example implementations of Option 1 above, the same frequency resource can be applied and shared by different RATs for the same UE. Therefore, services from different RATs can be transmitted simultaneously for the same UE on the same frequency resource, beneficially achieving higher efficiency in radio spectrum utilization. Cross-RAT scheduling for the same frequency resource can also be implemented to provide enhanced resource scheduling flexibility from the network side.

[0072] The following further describes an example of how the same spectrum resource can be shared by different RATs for the same UE (Option 1 above). In some example spectrum resource sharing implementations of Option 1, sharing of the same spectrum resource between RATs for the same UE can be achieved through channel or resource sharing. For channel or resource sharing, at least one of the following alternatives can be implemented.

[0073] In a first example alternative implementation of channel / resource sharing for Option 1, control channels within the same spectrum resource can be shared between different RATs. Such control channels can be used to schedule resources within the same spectrum resource. Therefore, spectrum resources can be scheduled between different RATs using control information transmitted in a shared control channel within the same spectrum resource. For example, as... Figure 9As shown, control channels (one or more) shared / used by different RATs can be located before the time slot, and the scheduling of resources for data services of different RATs (e.g., the first RAT, e.g., the 6G RAT) in the later part of the time slot can be based on the scheduling of shared control channels. Figure 9 In this context, the horizontal and vertical directions are associated with time and frequency, respectively.

[0074] For example, the shared control channel described above could be a control channel associated with one of the first RAT and the second RAT. For instance, for spectrum sharing between a 6G RAT and a 4G / 5G RAT, the shared control channel could be associated with the 6G RAT. Control channels, such as downlink control channels, can be used to transmit DCI defined for all RATs (e.g., 6G RAT and 4G / 5G RAT) based on the shared spectrum resources. In some example implementations, the blind decoding capability of the shared control channel may be counted only in one RAT (e.g., the 6G RAT) among multiple RATs. Alternatively, the blind decoding capability of the shared control channel can be counted in different RATs using a corresponding scaling factor.

[0075] In some example implementations of control channel sharing, the multiple RATs sharing spectrum resources include: 5GRATs, and the shared control channel can be one or more NR PDCCHs, which can be used to transmit DCIs defined according to the multiple RATs. For example, some or all of the NR PDCCHs used for control channel sharing can be located in a partial control resource set and search space.

[0076] In some example implementations of control channel sharing, the multiple RATs sharing spectrum resources include LTE, and the shared control channel can be one or more LTE PDCCHs, which can be used to transmit DCI defined according to the multiple RATs. For example, some or all of the LTE PDCCHs used for control channel sharing may reside in a partial search space. In some implementations, the network can be updated to support the use of legacy RAT channels to transmit control information associated with different subsequent RATs.

[0077] In some example implementations, various aspects or constraints regarding the application of the shared control channel may be employed. These aspects or constraints may include one or more of the following non-limiting items: ● Control information in the shared control channel may include RAT flags that can be used to determine the interpretation of other fields in the DCI. For example, such RAT flags can indicate which RAT a particular control message applies to.

[0078] ● The size of the shared DCI format used for transmission in the shared control channel can be determined by the maximum size of the DCI format of various RATs, and when transmitting DCI for a RAT with a shorter format, the extra bits in the shared DCI format can be zero-padded.

[0079] ● Partially shared control channels can be used for different RATs, where some parameters / resources of the control channel shared for, for example, NR PDCCH can be transmitted by using different MIMO (Multiple Input Multiple Output) layers or different control channel resources compared to the underlying control channel used for transmission (e.g., 6G control channel).

[0080] ● Control information in the shared control channel can schedule multiple service channels of multiple RATs, wherein the multiple service channels of multiple RATs can be distinguished by at least one of time domain / frequency domain / code domain resources.

[0081] In a second example alternative implementation of channel / resource sharing for Option 1, other resources may be shared between different RATs. Such shared resources can be broadly categorized, including but not limited to frequency, time, and other network resources across various network layers. For example, shared resources may include portions of resources allocated to a first RAT (e.g., a 6G RAT) that can be used to transmit channels / signals (e.g., control channels) for a second RAT (e.g., a 4G / 5G RAT). In some implementations, the shared resources of the first RAT for transmitting / receiving various signals / channels of the second RAT may be indicated by the control channel of the first RAT. In some implementations, such portions of resources for sharing may be determined based on network configuration or based on indications of signals / channels from the first RAT. For example, a UE may receive signals / channels of the second RAT (e.g., a 6G RAT) based on such network configuration or based on such indications in the signals / channels of the first RAT (e.g., a 6G RAT). In some example implementations, such configuration or indication may include information related to when / where / how the signal / channel of the second RAT is received. For example, such configuration or indication may instruct the UE to receive the PDCCH of the second RAT (e.g., NR or 4G / 5G RAT) within the configured / indicated resources in each time slot.

[0082] In a third example alternative implementation of channel / resource sharing for Option 1 above, synchronization / broadcast channel sharing between different RATs can be employed. For example, during the initial access of the UE to the network, only a single RAT may be accessed, or alternatively, multiple RATs may be accessed through synchronization / broadcast channel sharing. In the case of accessing multiple RATs, information of one of the multiple RATs may be carried on one or more synchronization or broadcast channels, which are used to indicate the use of a channel of one RAT for access. In some example implementations, the same spectrum resource may be used for the same cell corresponding to different RATs for the same UE. In some example implementations, one of the multiple RATs may be configured on the same spectrum resource.

[0083] In a fourth example alternative implementation of channel / resource sharing for Option 1, service channel sharing among various RATs can be employed. For example, dynamic scheduling can be implemented to indicate that the service of one of the plurality of RATs can be transmitted on one or more shared service channels. In the case of configured licensed or unlicensed transmission on one or more shared service channels, the service of one of the plurality of RATs to be transmitted can be determined by priority rules or reference signals. For example, the priority of a second RAT (e.g., a legacy 4G / 5G RAT) may be higher or lower than the priority of a first RAT (e.g., a current / new 6G RAT). As another example, the network or UE can detect or distinguish reference signals for different RATs.

[0084] In some other example implementations of spectrum resource sharing in Option 1 above, the same spectrum resource is shared by different RATs for the same UE, and the different RATs may be associated with the same hybrid automatic repeat request (HARQ) entity or different HARQ entities.

[0085] For example, the same spectrum resource used for different RATs may be associated with different cells. In some implementations, each HARQ entity may be associated with one cell, and different HARQ entities may be associated with different RATs. Alternatively, the same HARQ entity may be used for different RATs, and different HARQ entities for different RATs may not be supported. In some implementations, the HARQ process number pool may be shared or partitioned for different RATs. In some implementations, different HARQ entities for different RATs can be supported when using the same channel coding and modulation scheme.

[0086] For example, the same spectrum resource used for different RATs may be associated with the same cell. In some implementations, a HARQ entity may be associated with a cell, and that HARQ entity may further be associated with different RATs. In some other implementations, different HARQ entities may be used for different RATs for the same cell.

[0087] In some further example implementations of Option 1 above, where the same spectrum resource is shared for different RATs of the same UE, the inter-RAT sharing of this spectrum resource may involve uplink sharing. Several example alternative implementations for uplink sharing are provided below.

[0088] In a first example alternative implementation for uplink sharing, where the same spectrum resource shared by different RATs is associated with different cells, messages 1 and / or 3 of the random access procedure may be accessed by only one RAT or one cell, wherein the RAT or cell may be predefined or determined by configuration or dynamic selection. In some example implementations, the physical uplink control channel (PUCCH) may be RAT-specific, or the PUCCH of the first RAT (e.g., a 6G RAT) may be compatible with the PUCCH of the second RAT (e.g., a 4G / 5G RAT), which may be shared and used, for example, for the transmission of HARQ-ACK feedback of the second RAT (e.g., a 4G / 5G RAT).

[0089] In a second example alternative implementation for uplink sharing, where the same spectrum resource shared by different RATs is associated with the same cell, UL signals / channels may be associated with different RATs. In some implementations, different UL signals / channels can be used for different RATs. In some implementations, the UL signals / channels of a first RAT (e.g., a 6G RAT) can be compatible with the same type of signals / channels of a second RAT (e.g., a 4G / 5G RAT).

[0090] In various example implementations of Option 1 above, the same frequency resource can be applied and shared by different RATs for the same UE. Therefore, services from different RATs can be transmitted simultaneously for the same UE on the same frequency resource, beneficially achieving higher efficiency in radio spectrum utilization. Cross-RAT scheduling for the same frequency resource can also be implemented to provide enhanced resource scheduling flexibility from the network side.

[0091] The various implementations described above for inter-RAT spectrum resource sharing under Option 1 are not limited to Option 1. For example, these various example implementations can be applied to Option 2 for inter-RAT spectrum resource sharing, which is further described above and below.

[0092] Example of sharing the same spectrum resources between different RATs used by different UEs (Option 2) Figure 7 The left branch), that is, different spectrum resources are used for different RATs of the same UE (Option 2, Figure 7 The upper branch (of the UE) may include detailed implementations of different spectrum resources for scheduling different RATs for the UE.

[0093] In some example implementations of Option 2 for spectrum resource sharing, different spectrum resources for different RATs for the same UE can be scheduled independently by each RAT.

[0094] In other alternative implementations, different spectrum resources for different RATs of the same UE can be jointly scheduled by a single DCI. Such joint scheduling can be achieved through several different alternatives described below.

[0095] In the first alternative example of joint scheduling via a single DCI, the target RAT of the single DCI can be determined by the UE through blind detection, or it can be predefined or determined by configuration. For example, if the UE does not know the target RAT of the single DCI, the UE can perform blind detection of the potential RAT based on parameters configured for different RATs in predefined / configured shared / independent resources. As another example, if the UE knows the RAT of the single DCI, the UE can perform blind detection of the potential DCI based on parameters configured for the known RAT (e.g., a 6G RAT as a new RAT, as opposed to a traditional RAT, such as a 4G / 5G RAT) in predefined / configured resources.

[0096] In a second alternative example of joint scheduling via a single DCI, the single DCI may include at least one RAT-specific field or a common field. For example, the at least one RAT common field may include a field of a type applicable to all RATs in a RAT group. For example, the at least one RAT common field may include a DL or UL flag indication. As another example, the at least one RAT common field may include fields corresponding to different field types applicable to all RATs with multiple groups; for example, for one field, one group may be used for different cells of one type (4G / 5G), and other groups may be used for different cells of another type (6G). For example, the frequency domain resource allocation field for group #1 may be associated with cells #1 and #2 for 4G / 5G and may be a type 2 field, which may be a non-shared indication; the frequency domain resource allocation field for group #2 may be associated with cells #3 and #4 for 6G and may be a type 1A field, which may be a shared indication. As another example, the RAT-specific field may include a field of a type applicable to RATs in a group. For example, a field defined in 6G might only apply to a group of cells with 6G, and not to another group of cells with 4G / 5G.

[0097] In a third alternative example where joint scheduling is performed by a single DCI, HARQ-ACK feedback for different RATs may be grouped into a single codebook. For example, PUCCH cells or PUCCH cell groups can be defined independently for each RAT, and cross-PUCCH group HARQ-ACK feedback can be supported. In cases where multiple cell scheduling is used for scheduling across multiple RATs, cross-PUCCH group HARQ-ACK feedback can be supported, and the scheduling can also indicate whether feedback occurs in another PUCCH group. For example, PUCCH group #1 may correspond to cells #1 and #2 for 4G / 5G, PUCCH group #2 may correspond to cells #3 and #4 for 6G, and HARQ-ACK feedback for different RATs may be grouped into a single codebook and carried on cell #1, which is configured with PUCCH resources.

[0098] In various implementations of Option 2 above, different frequency resources can be shared between different RATs, thereby providing higher spectrum utilization efficiency. Different spectrum resources of different RATs for the same UE can be jointly scheduled through a single DCI, thereby enhancing scheduling or transmission flexibility. Furthermore, services from different RATs can be transmitted simultaneously on different frequency resources for the same UE, enhancing effective transmission bandwidth.

[0099] When the various implementation methods described above are described in the context of Option 2, they can also be applied to the implementation methods of Option 1.

[0100] The above implementation refers to the first RAT and the second RAT. However, these RAT implementations are applicable to situations involving two or more RATs utilizing a single or multiple spectrum resources.

[0101] Spectrum resource sharing or independent utilization in a cell-free system In some example implementations, the spectrum resources used in a cellless system can be shared among radio access network nodes (referred to as access points in a cellless context) or used independently by the radio access network nodes.

[0102] The term "cellless" refers to a network schema that lacks a clearly defined cell. However, in a cellless system, cells can be defined from the UE's schema, where UEs are concentrated in their own cells and can connect to more than one access point (AP) around them. Cellless implementations can be a potential solution for achieving distributed cell deployments. For example... Figure 10 As shown, UE 1002 (UE 1) can connect to a set of APs including AP #2 / 4 / 5, and from the UE's diagram, cell 1004 (cell #1) can be supported by these three APs. These specific APs together form a distributed antenna array as a massive MIMO configuration for UE 1002, where the transmission beam for UE 1002's location is dynamically managed by a central processing unit (CPU). In a cellless network, each mobile UE can be associated with a mobile cell, and the selection of APs providing the UE-centric cell changes over time. Cells of various UEs may overlap. In other words, the same AP can be part of multiple UE-centric cells for different UEs. The aforementioned cellless network can also be alternatively referred to as a "cellless" or "de-cellular" network. With such UE-centric cells, the UE can receive service from multiple APs and can reduce interference from neighboring APs that may occur in traditional wireless communication systems. Such cellless schemes further provide UEs with enhanced flexibility to select their serving APs with greater autonomy.

[0103] In a cell-free system, access points (APs) may consist of a single or a small number of antennas, while a large number of APs can be deployed within an area. In some example implementations, traffic from multiple APs can be forwarded to the CPU, and the same frequency resources can be used for different UEs in different locations. In such cell-free systems, multiple frequencies or carriers can be used by individual APs in the various example configurations described below.

[0104] In some example implementations, a set of carriers in an AP set can be determined for the UE, and different carrier subsets from that set can be applied to (or used by) different APs in the AP set. For example, the AP set for the UE can be determined by the network, and alternatively, the carrier set for the AP set can also be determined by the network (e.g., by the CPU) in conjunction with a UE capability report. Alternatively, the AP set for the UE can be determined by the UE, and alternatively, the carrier set can also be determined by the UE, for example, based on the UE capability limited by the maximum number of carriers in each AP set, and the carrier subset for each AP in the AP set can be determined by combining the UE capability with, for example, the coverage of each AP. Figure 11 As shown, the AP set may include AP #2 / 4 / 5 for UE1, the carrier set may include carriers f1, f2, and f3, and carrier aggregation can be performed by aggregating carrier f1 with AP2, carrier f3 with AP4, and carrier f2 with AP5. In some example implementations, the UE-centric cell may be a single cell associated with multiple carriers, which correspond to multiple APs. For example, in Figure 12 In this context, UE1 can be associated with service type 1 and AP set {2, 4, 5}, while UE2 (not shown) can be associated with service type 2 and AP set {2, 4}. For example, in initial access and / or RRC connection states, the AP set can be determined by conventional reference signal measurements, such as comparisons with one or more RSRP (reference signal receive power) thresholds, and the number of APs in the AP set can be selected based on one or more thresholds. In other words, the CA (carrier set) can be configured by the network, while the AP set can be determined by each UE.

[0105] In some other example implementations, the carrier set can be determined based on a reference AP in the AP set, and a carrier subset can be applied to different APs in the AP set. For example, the reference AP in the AP set could be the AP with the maximum number of antennas in the AP set, or the AP whose location is closest to the UE associated with the AP set. In some example implementations, the carrier set can be determined by the network (e.g., by the CPU) in combination with UE capability reports. In some example implementations, the carrier(s)(one or more) of each AP in the AP set for the UE can be based on the transmission capacity of each AP. The AP set for the UE can be determined by the UE, with the option that the carrier set can also be determined by the UE, for example, based on the UE capability limited by the maximum number of carriers per AP, and the carrier subset of each AP in the AP set can be determined by combining, for example, the UE capability of the coverage of each AP. Figure 12 As shown, the example AP set for UE1 includes AP2, AP4 and AP5, the example carrier set includes f1, f2 and f3, and carrier aggregation can be performed by aggregation (aggregating f1, f2 and f3 with AP4, aggregating f1 with AP2, and aggregating f1 and f2 with AP5).

[0106] The above-described example implementation of spectrum resource usage in a cellless system where different APs use the same UE can advantageously provide higher spectrum utilization efficiency. The same or different spectrum resources used by different APs for the same UE can be distributed or localized among the APs to enable flexible scheduling or transmission.

[0107] Finally, as described in the various schemes above, spectrum resources can be shared among different RATs or APs within the AP set used for the UE in a cellless system. Specifically, sharing the same spectrum resources for the same UE by different RATs (Option 1 above) can be achieved by one of the following: (1) using the same spectrum resources for the same UE in different cells corresponding to different RATs, wherein the different cells are associated with different cell groups; (2) using the same spectrum resources for the same UE in different cells corresponding to different RATs, wherein the different cells are associated with the same cell group; (3) using the same spectrum resources for the same UE in the same cell corresponding to different RATs.

[0108] Furthermore, sharing of the same spectrum resources for the same UE by different RATs (Option 1 above) can be achieved through channel or resource sharing. For example, such sharing can include control channel sharing. A shared control channel can be a control channel of one of multiple RATs (e.g., a 6G RAT). A shared control channel can be used to transmit DCIs defined in more than one RAT. For example, the capability of blind DCI decoding can be counted only in one of multiple RATs, or it can be counted in different RATs with corresponding scaling factors. For example, limitations on the application of a shared control channel can include one of the following: (1) the control information in the shared control channel can include RAT flag indications; (2) the control information in the shared control channel can be zero-padded for different RATs. Alternatively, such channel or resource sharing can include resource sharing. For example, shared resources for signals / channels for one RAT can be indicated by the control channel of another RAT.

[0109] Furthermore, different RATs sharing different spectrum resources for the same UE (Option 2 above) can be jointly scheduled by a single DCI. For example, the RAT used to transmit this single DCI can be determined by blind detection, or it can be predefined or determined by configuration. Another example is that the single DCI may include at least one RAT-specific field or common field. Yet another example is that HARQ-ACK feedback for different RATs can be grouped in a codebook.

[0110] For spectrum resource utilization in a cellless system, multiple carriers used in a cellless implementation can be determined as a carrier set of an AP set associated with the UE. Different carrier subsets in this carrier set can be applied to different APs in that AP set. Alternatively, multiple carriers used in a cellless implementation can be determined as a carrier set based on a reference AP in the AP set for the UE, and carrier subsets in this carrier set can be applied to different APs in that AP set.

[0111] The above description and accompanying drawings provide specific example embodiments and implementations. However, the described subject matter can be implemented in a variety of different forms, and therefore, the covered or claimed subject matter is intended to be construed as not being limited to any of the example embodiments set forth herein. A reasonably broad scope is intended for the claimed or covered subject matter. In particular, for example, the subject matter can be embodied as a method, apparatus, component, system, or non-transitory computer-readable medium for storing computer code. Thus, embodiments can take the form of, for example, hardware, software, firmware, storage medium, or any combination thereof. For example, the above-described method embodiments can be implemented by a component, apparatus, or system including a memory and a processor by executing computer code stored in the memory.

[0112] Throughout the specification and claims, terms may have suggestive or implied meanings beyond their explicitly stated meanings in the context. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to different embodiments. For example, the claimed subject matter is intended to include, in whole or in part, combinations of exemplary embodiments.

[0113] Generally, terms can be understood at least in part based on their usage in the context. For example, terms used herein (such as “and,” “or,” or “and / or”) can include a variety of meanings (which can depend at least in part on the context in which these terms are used). Typically, “or,” if used to associate a list such as A, B, or C, is intended to mean A, B, and C (used herein in an inclusive sense) and A, B, or C (used herein in an exclusive sense). Furthermore, depending at least in part on the context, the term “one or more,” as used herein, can be used to describe any feature, structure, or characteristic in a singular sense, or can be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, depending at least in part on the context, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage. Moreover, the term “based on,” depending at least in part on the context, can be understood to not necessarily convey an exclusive set of factors, but rather to allow for the presence of additional factors that are not necessarily explicitly described.

[0114] References to features, advantages, or similar language throughout this specification do not imply that all features and advantages achievable using this solution should be, or be included, in any single implementation thereof. Rather, references to such features and advantages are to be understood as indicating that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this solution. Therefore, throughout this specification, discussions of features and advantages and similar language may, but do not necessarily, refer to the same embodiment.

[0115] Furthermore, the features, advantages, or characteristics described in this solution can be combined in one or more embodiments in any suitable manner. Based on the description herein, those skilled in the art will recognize that this solution can be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of this solution.

Claims

1. A method performed by a wireless terminal device, comprising: A connection is established with at least one radio access network node on at least one radio spectrum resource via both a first radio access technology (RAT) and a second RAT, wherein the second RAT is different from the first RAT, and each of the at least one radio spectrum resource includes a pre-configured radio spectrum range; and Use the at least one wireless spectrum resource used for the first RAT and the second RAT.

2. The method according to claim 1, wherein, The at least one wireless spectrum resource includes a pre-configured wireless spectrum range shared by the first RAT and the second RAT.

3. The method according to claim 2, wherein, Using the pre-configured radio spectrum range for the first RAT and the second RAT includes: communicating with a first cell and a second cell respectively using the pre-configured radio spectrum range based on the first RAT and the second RAT, wherein the first cell and the second cell belong to different cell groups or are different but belong to the same cell group.

4. The method according to claim 2, wherein, Using the pre-configured radio spectrum range for the first RAT and the second RAT includes: using the pre-configured radio spectrum range to communicate with a single cell that supports both the first RAT and the second RAT.

5. The method according to claim 2, wherein, Using the pre-configured wireless spectrum range for the first RAT and the second RAT includes: channel sharing between the first RAT and the second RAT.

6. The method according to claim 5, wherein, The use of the pre-configured wireless spectrum range for the first RAT and the second RAT includes sharing at least one control channel between the first RAT and the second RAT.

7. The method of claim 6, wherein: The first RAT includes a 6G RAT, and the second RAT includes a 4G RAT or a 5G RAT; and The at least one control channel shared between the first RAT and the second RAT includes a 6G control channel.

8. The method according to claim 6, wherein, The at least one control channel shared between the first RAT and the second RAT is configured to receive downlink control information (DCI) defined in both the first RAT and the second RAT.

9. The method according to claim 8, wherein, The wireless terminal device's ability to blindly detect the DCI is counted in one of the first RAT and the second RAT, or counted in both the first RAT and the second RAT by a scaling factor.

10. The method according to claim 6, wherein, The control information carried in the at least one control channel shared by the first RAT and the second RAT includes a RAT flag indicating which of the first RAT and the second RAT the control information is for.

11. The method according to claim 6, wherein, The control messages carried in the at least one control channel shared by the first RAT and the second RAT are configured to fit the format of both the first predefined control information size of the first RAT and the second predefined control information size of the second RAT, and when carrying a control message that includes the shorter of the first predefined control information size and the second predefined control information size, the control message is padded with zero bits.

12. The method according to claim 2, wherein, Using the pre-configured wireless spectrum range for the first RAT and the second RAT includes: resource sharing between the first RAT and the second RAT.

13. The method according to claim 12, wherein, The resources of the first RAT shared with the second RAT are indicated by the control channel of the first RAT.

14. The method of claim 13, wherein, The first RAT is a 6G RAT, and the second RAT is a 4G RAT or a 5G RAT.

15. The method according to claim 1, wherein, The at least one wireless spectrum resource includes a first pre-configured wireless spectrum range and a second pre-configured spectrum range used by the first RAT and the second RAT.

16. The method according to claim 15, wherein, The downlink spectrum resources of the first pre-configured wireless spectrum range and / or the second pre-configured spectrum range are dynamically scheduled by a single DCI.

17. The method according to claim 16, wherein, The RAT of a single DCI is determined by the wireless terminal device via blind detection or is pre-configured.

18. The method according to claim 16, wherein, At least one RAT-specific field or RAT-common field of the first RAT and the second RAT is included in the single DCI.

19. The method of claim 16, wherein, The Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback associated with the first RAT and the second RAT is grouped in a codebook.

20. A method performed by a wireless access network node, comprising: A connection is established with a wireless terminal device on at least one radio spectrum resource via a first radio access technology (RAT) and a second RAT, wherein the second RAT is different from the first RAT, and each of the at least one radio spectrum resource includes a pre-configured radio spectrum range; and The wireless terminal device communicates using at least one wireless spectrum resource for the first RAT and the second RAT.

21. The wireless terminal device according to any one of claims 1 to 19, wherein the wireless terminal device comprises a processor and a memory, wherein, The processor is configured to read computer code from the memory to cause the wireless terminal device to perform the method according to any one of claims 1 to 19.

22. A computer program product comprising a non-transitory computer-readable program medium, wherein computer code is stored on the non-transitory computer-readable program medium, the computer code, when executed by a processor of a wireless terminal device according to any one of claims 1 to 19, causes the processor to implement the method according to any one of claims 1 to 19.

23. The wireless access network node according to claim 20, wherein the wireless access network node comprises a processor and a memory, wherein, The processor is configured to read computer code from the memory to cause the wireless access network node to execute the method according to claim 20.

24. A computer program product comprising a non-transitory computer-readable program medium, wherein computer code is stored on the non-transitory computer-readable program medium, the computer code, when executed by a processor of a wireless access network node according to claim 20, causes the processor to implement the method according to claim 20.

Images