WO2023133902A1 - 一种无线通信方法及装置、终端设备、网络设备 - Google Patents

一种无线通信方法及装置、终端设备、网络设备 Download PDF

Info

Publication number
WO2023133902A1
WO2023133902A1 PCT/CN2022/072419 CN2022072419W WO2023133902A1 WO 2023133902 A1 WO2023133902 A1 WO 2023133902A1 CN 2022072419 W CN2022072419 W CN 2022072419W WO 2023133902 A1 WO2023133902 A1 WO 2023133902A1
Authority
WO
WIPO (PCT)
Prior art keywords
type
channel access
lbt
access type
terminal device
Prior art date
Application number
PCT/CN2022/072419
Other languages
English (en)
French (fr)
Inventor
赵楠德
马东俊
Original Assignee
Oppo广东移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to PCT/CN2022/072419 priority Critical patent/WO2023133902A1/zh
Priority to CN202280073861.5A priority patent/CN118202766A/zh
Publication of WO2023133902A1 publication Critical patent/WO2023133902A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access

Definitions

  • the embodiments of the present application relate to the field of mobile communication technologies, and in particular to a wireless communication method and device, terminal equipment, and network equipment.
  • unlicensed bands can be used as a supplement to licensed bands to help operators expand services.
  • the unlicensed frequency band can work in the 5GHz, 37GHz and 60GHz frequency bands.
  • the large bandwidth (80MHz or 100MHz) of the unlicensed frequency band can reduce the implementation complexity of the base station (gNB) and the terminal (User Equipment, UE). Sharing, such as Wi-Fi, radar, Long Term Evolution License Assisted Access (LTE-LAA), etc. Therefore, the use of unlicensed frequency bands must comply with certain rules to ensure that all devices can Use the resource fairly, such as Listen Before Talk (LBT), Maximum Channel Occupancy Time (MCOT) and other rules.
  • LBT Listen Before Talk
  • MCOT Maximum Channel Occupancy Time
  • the NRU system supports UE switching from Type 1 LBT to Type 2A LBT in the way of channel occupancy time (Channel Occupancy Time, COT) sharing, but the switching method of NRU is no longer suitable for high frequency, and needs to be redesigned Channel switching scheme.
  • channel occupancy time Channel Occupancy Time, COT
  • Embodiments of the present application provide a wireless communication method and device, a terminal device, and a network device.
  • the terminal device receives first information configured by the network device, the first information indicates at least one first channel access type in non-fallback downlink control information (Downlink Control Information, DCI), and the first information is used to determine the first channel access type A target channel access type, the first target channel access type is the case where the terminal device is instructed to execute type 1 listen-before-talk LBT, and the scheduled or configured first transmission is carried on the first resource
  • the channel access type switched from type 1 LBT the first resource is the resource corresponding to the first channel occupancy time COT, and the first COT is the COT initiated by the network device.
  • the network device sends first information to the terminal device, where the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, where the first information is used to determine a first target channel access type,
  • the first target channel access type is when the terminal device is instructed to perform type 1 listen before talk LBT, and the scheduled or configured first transmission is carried on the first resource, switch from type 1 LBT to channel access type, the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the first receiving module is configured to receive first information configured by the network device, the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, and the first information is used to determine the first A target channel access type, where the first target channel access type is the case where the terminal device is instructed to execute type 1 listen-before-talk LBT, and the scheduled or configured first transmission is carried on the first resource , the channel access type switched from type 1 LBT, the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the second sending module is configured to send first information to the terminal device, the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, and the first information is used to determine the first target A channel access type, where the first target channel access type is the case where the terminal device is instructed to execute type 1 listen-before-talk LBT, and the scheduled or configured first transmission is carried on the first resource,
  • the channel access type switched from type 1 LBT, the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the communication device provided in the embodiment of the present application may be the terminal device in the above solution or the network device in the above solution, and the communication device includes a processor and a memory.
  • the memory is used for storing computer programs
  • the processor is used for invoking and running the computer programs stored in the memory to execute the above wireless communication method.
  • the chip provided in the embodiment of the present application is used to implement the above wireless communication method.
  • the chip includes: a processor, configured to call and run a computer program from the memory, so that the device installed with the chip executes the above wireless communication method.
  • the computer-readable storage medium provided by the embodiment of the present application is used for storing a computer program, and the computer program causes a computer to execute the above wireless communication method.
  • the computer program product provided by the embodiments of the present application includes computer program instructions, where the computer program instructions cause a computer to execute the above wireless communication method.
  • the computer program provided by the embodiment of the present application when running on a computer, enables the computer to execute the above wireless communication method.
  • the first channel access type in the non-fallback DCI implicitly indicates the first target channel access type when the terminal device meets the channel access switching type, so that when the channel access switching condition is met, Channel access is performed based on the first target channel access type, so as to adapt to high-frequency COT sharing.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application
  • Fig. 2 is a schematic flowchart of an optional wireless communication method provided by an embodiment of the present application.
  • Fig. 3 is an optional schematic diagram of COT sharing provided by the embodiment of the present application.
  • Fig. 4 is an optional schematic diagram of COT sharing provided by the embodiment of the present application.
  • FIG. 5 is a schematic flowchart of an optional wireless communication method provided by an embodiment of the present application.
  • Fig. 6 is an optional schematic diagram of COT sharing provided by the embodiment of the present application.
  • FIG. 7 is an optional schematic diagram of COT sharing provided by the embodiment of the present application.
  • FIG. 8 is a schematic flowchart of an optional wireless communication method provided by an embodiment of the present application.
  • FIG. 9 is an optional schematic diagram of COT sharing provided by the embodiment of the present application.
  • FIG. 10 is an optional schematic structural diagram of a wireless communication device provided by an embodiment of the present application.
  • Fig. 11 is an optional schematic structural diagram of a wireless communication device provided by an embodiment of the present application.
  • Fig. 12 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • Fig. 14 is a schematic block diagram of a communication system provided by an embodiment of the present application.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • a communication system 100 may include a terminal device 110 and a network device 120 .
  • the network device 120 may communicate with the terminal device 110 through an air interface. Multi-service transmission is supported between the terminal device 110 and the network device 120 .
  • the embodiment of the present application is only described by using the communication system 100 as an example, but the embodiment of the present application is not limited thereto. That is to say, the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Long Term Evolution (Long Term Evolution, LTE) system, LTE Time Division Duplex (Time Division Duplex, TDD), Universal Mobile Communication System (Universal Mobile Telecommunication System, UMTS), Internet of Things (Internet of Things, IoT) system, Narrow Band Internet of Things (NB-IoT) system, enhanced Machine-Type Communications (eMTC) system, 5G communication system (also known as New Radio (NR) communication system), or future communication systems, etc.
  • LTE Long Term Evolution
  • LTE Time Division Duplex Time Division Duplex
  • TDD Time Division Duplex
  • Universal Mobile Telecommunication System Universal Mobile Telecommunication System
  • UMTS Universal Mobile Communication System
  • Internet of Things Internet of Things
  • NB-IoT Narrow Band Internet of Things
  • eMTC enhanced Machine-Type Communications
  • the network device 120 may be an access network device that communicates with the terminal device 110 .
  • the access network device can provide communication coverage for a specific geographical area, and can communicate with terminal devices 110 (such as UEs) located in the coverage area.
  • the network device 120 may be an evolved base station (Evolutional Node B, eNB or eNodeB) in a long-term evolution (Long Term Evolution, LTE) system, or a next-generation radio access network (Next Generation Radio Access Network, NG RAN) device, Either a base station (gNB) in the NR system, or a wireless controller in a cloud radio access network (Cloud Radio Access Network, CRAN), or the network device 120 can be a relay station, an access point, a vehicle-mounted device, a wearable Devices, hubs, switches, bridges, routers, or network devices in the future evolution of the Public Land Mobile Network (Public Land Mobile Network, PLMN), etc.
  • Evolutional Node B, eNB or eNodeB in a long-term evolution (Long Term Evolution, LTE) system
  • NG RAN next-generation radio access network
  • gNB base station
  • CRAN Cloud Radio Access Network
  • the network device 120 can be a relay station, an access point,
  • the terminal device 110 may be any terminal device, including but not limited to a terminal device connected to the network device 120 or other terminal devices by wire or wirelessly.
  • the terminal device 110 may refer to an access terminal, UE, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device .
  • Access terminals can be cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, IoT devices, satellite handheld terminals, Wireless Local Loop (WLL) stations, Personal Digital Assistant , PDA), handheld devices with wireless communication functions, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminal devices in 5G networks or terminal devices in future evolution networks, etc.
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • the wireless communication system 100 may also include a core network device 130 that communicates with the base station.
  • the core network device 130 may be a 5G core network (5G Core, 5GC) device, for example, Access and Mobility Management Function (Access and Mobility Management Function , AMF), and for example, authentication server function (Authentication Server Function, AUSF), and for example, user plane function (User Plane Function, UPF), and for example, session management function (Session Management Function, SMF).
  • the core network device 130 may also be a packet core evolution (Evolved Packet Core, EPC) device of the LTE network, for example, a data gateway (Session Management Function+Core Packet Gateway, SMF+PGW- C) equipment.
  • EPC packet core evolution
  • SMF+PGW-C can realize the functions of SMF and PGW-C at the same time.
  • the above-mentioned core network equipment may be called by other names, or a new network entity may be formed by dividing functions of the core network, which is not limited in this embodiment of the present application.
  • Various functional units in the communication system 100 may also establish a connection through a next generation network (next generation, NG) interface to implement communication.
  • NG next generation network
  • the terminal device establishes an air interface connection with the access network device through the Uu interface to transmit user plane data and control plane signaling; the terminal device can establish a control plane signaling connection with the AMF through the NG interface 1 (N1 for short);
  • the access Network equipment such as the next generation wireless access base station (gNB), can establish a user plane data connection with UPF through NG interface 3 (abbreviated as N3); access network equipment can establish control plane signaling with AMF through NG interface 2 (abbreviated as N2) connection;
  • UPF can establish a control plane signaling connection with SMF through NG interface 4 (abbreviated as N4);
  • UPF can exchange user plane data with the data network through NG interface 6 (abbreviated as N6);
  • AMF can communicate with SMF through NG interface 11 (abbreviated as N11)
  • the SMF establishes a control plane signaling connection; the SMF may establish a control plane signaling connection with the PCF through an NG interface 7 (N7 for short).
  • Figure 1 exemplarily shows a base station, a core network device, and two terminal devices.
  • the wireless communication system 100 may include multiple base station devices and each base station may include other numbers of terminals within the coverage area.
  • the device is not limited in the embodiment of this application.
  • FIG. 1 is only an illustration of a system applicable to this application, and of course, the method shown in the embodiment of this application may also be applicable to other systems.
  • system and “network” are often used interchangeably herein.
  • the term “and/or” in this article is just an association relationship describing associated objects, which means that there can be three relationships, for example, A and/or B can mean: A exists alone, A and B exist simultaneously, and there exists alone B these three situations.
  • the character "/" in this article generally indicates that the contextual objects are an "or” relationship.
  • the "indication” mentioned in the embodiments of the present application may be a direct indication, may also be an indirect indication, and may also mean that there is an association relationship.
  • A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also indicate that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also indicate that there is an association between A and B relation.
  • the "correspondence” mentioned in the embodiments of the present application may mean that there is a direct correspondence or an indirect correspondence between the two, or that there is an association between the two, or that it indicates and is indicated. , configuration and configured relationship.
  • the "predefined” or “predefined rules” mentioned in the embodiments of this application can be used by pre-saving corresponding codes, tables or other It is implemented by indicating related information, and this application does not limit the specific implementation.
  • pre-defined may refer to defined in the protocol.
  • the "protocol” may refer to a standard protocol in the communication field, for example, it may include the LTE protocol, the NR protocol, and related protocols applied to future communication systems, and this application does not limit this .
  • the transmission node can also be called an initiating device.
  • the transmission node can include a base station and a UE. After the transmission node obtains a channel, it can share the COT with the receiving node.
  • the receiving node can also be called a responding node.
  • a responding device the receiving node may also include UE and base station. That is, when the base station is an initiating device, the UE is a responding device; when the UE is an initiating device, the base station is a responding device.
  • the following process can be applied:
  • the UE can switch from Type 1 channel access to Type 2A channel access.
  • the base station/UE uses Type1 LBT to initiate COT on the channel
  • the COT can be shared with the UE/base station for UL/DL transmission after DL/UL transmission.
  • the responding device needs to follow the following procedures:
  • COT sharing scheme 1 Regardless of the size of the gap between the UL/DL transmission and the previous DL/UL transmission, there is no need to perform LBT (that is, Type3 LBT) before the UL/DL transmission, and directly perform UL/DL transmission;
  • LBT that is, Type3 LBT
  • Type 2 LBT If the gap between the UL/DL transmission and the previous DL/UL transmission exceeds the threshold determined by the base station (at least 8 microseconds ( ⁇ s)), execute Type 2 LBT before the UL/DL transmission starts , otherwise, Type 3 LBT is performed before the UL/DL transmission.
  • scheme 1 or scheme 2 depends on the selection of the base station, and at least the requirements of local regulations need to be considered.
  • DCI format 0_1 is a non-fallback uplink grant for scheduling physical uplink shared channel (Physical Uplink Share Channel, PUSCH) transmission.
  • Physical Uplink Share Channel Physical Uplink Share Channel, PUSCH
  • PUSCH Physical Uplink Share Channel
  • the bit width is log 2 I bits, where I is the index number configured by the high-level parameter ul-AccessConfigListDCI-0-1, that is, the number of index items.
  • the index allowed by DCI 0_1 in high frequency is configured by high layer parameters, as shown in Table 1.
  • DCI format 1_1 is a non-fallback uplink grant for scheduling physical downlink shared channel (Physical Downlink Share Channel, PDSCH) transmission.
  • PDSCH Physical Downlink Share Channel
  • the bit width is log 2 I bits, where I is the index number configured by the high layer parameter ul-AccessConfigListDCI-1-1.
  • the index allowed by DCI 1_1 in the high frequency is configured by the high layer, as shown in Table 2, and this channel access method is used to carry the physical uplink control channel of the hybrid automatic repeat request (Hybrid Automatic Repeat Request, HARQ)-acknowledgment (ACK) (Physical Uplink Control Channel, PUCCH) transmission.
  • Hybrid Automatic Repeat Request Hybrid Automatic Repeat Request, HARQ
  • ACK Physical Uplink Control Channel
  • the NRU system supports the UE to switch from Type1 LBT to Type2A LBT in the way of COT sharing, but since the high frequency supports two COT sharing methods, it is necessary to clarify which channel access type the UE switches from Type1LBT to, so as to ensure that the base station and UE There is a common understanding of the type of channel access after switching.
  • the wireless communication method provided in the embodiment of the present application is applied to a terminal device, as shown in FIG. 2 , including:
  • the terminal device receives first information configured by the network device, the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, and the first information is used to determine the first target channel access type input type.
  • the first target channel access type is when the terminal device is instructed to perform type 1 listen before talk LBT, and the scheduled or configured first transmission is carried on the first resource, switch from type 1 LBT to channel access type, the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the terminal equipment and network equipment support the high frequency of 52.6GHz-71GHz, and the terminal equipment and network equipment communicate based on the high frequency of 52.6GHz-71GHz.
  • the terminal equipment and network equipment work in frequency bands other than 52.6GHz-71GHz, such as FR1 and FR2.
  • the terminal device when the terminal device is instructed to perform type 1 LBT, and the first transmission scheduled or configured is carried on the first resource, the terminal device considers that the channel access type switching condition is currently satisfied, and can perform channel access Type switching. At this time, the terminal device switches the channel access type from type 1 LBT to the first target channel access type, and performs channel access based on the first target channel access type.
  • the first target channel access type is determined implicitly based on the first information, and the first information is used to indicate at least one first channel access type in the non-fallback DCI.
  • the first information is a high layer parameter sent by the network device indicating at least one first channel access type in the non-fallback DCI.
  • the non-fallback DCI allows multiple channel access types
  • the network device indicates through the first information that some or all of the multiple channel access types allowed by the non-fallback DCI are at least one of the non-fallback DCI A channel access type.
  • the channel access types allowed by the non-fallback DCI include: type 1 LBT, type 2 LBT, and type 3 LBT
  • the first information indicates that the channel access types in the non-fallback DCI include: type 1 LBT and type 2 LBT .
  • each channel access type allowed by the non-fallback DCI is configured with a different index item
  • the first information carries the index item
  • the terminal device determines the channel access type in the non-fallback DCI based on the index item carried in the first information .
  • the network device may configure the first information to the network device, and send the configured first information to the terminal device.
  • the terminal device determines the first target channel access type based on the first information when the handover indication condition is met.
  • the network device may instruct the terminal device to execute Type 1 LBT through the first DCI sent to the terminal device.
  • the COT that instructs the UE to perform Type 1 LBT is not the same COT as the COT that transmits the first transmission, that is, the first COT.
  • the first DCI may be sent in a COT preceding the first COT.
  • the first transmission is an uplink transmission scheduled by a network device or configured by a high layer.
  • the first transmission may be scheduled by the first DCI.
  • the network device sends the first DCI to the terminal device, and the terminal device receives the first DCI sent by the network device. Based on the first DCI, the terminal device can determine that the first transmission is scheduled and is instructed to perform Type 1 LBT.
  • the first transmission may be PUSCH.
  • the first transmission is configured by a higher layer, the first transmission is CG-PUSCH.
  • the network device may send the second DCI to the terminal device at the first COT, and the second DCI is used to indicate the information of the first COT.
  • the terminal device determines the first transmission scheduled by the first DCI or the first transmission configured by the high layer based on the second DCI.
  • a transmission is carried on the first resource corresponding to the first COT, and the terminal device determines to switch the channel access type.
  • the terminal device After determining the first target channel access type, the terminal device performs channel access based on the first target channel access type after the first resource arrives, and sends the first transmission after the channel access is successful.
  • the first target channel access type may be: type 1 LBT, type 2 LBT or type 3 LBT.
  • the terminal device When the first target channel access type is type 1LBT, the terminal device performs channel access type switching if the channel access type switching condition is met, and the switched channel access type is still type 1LBT. At this time, the terminal The device still performs Type 1 LBT for channel access.
  • the terminal device When the first target channel access type is type 2LBT or type 3LBT, then in the case that the terminal device satisfies the channel access type switching conditions, perform channel access type switching, switching from type 1 LBT to type 2LBT or type 3LBT, at this time , the terminal device executes type 2 LBT or type 3 LBT for channel access.
  • the network device sends DCI 1 to the terminal device on COT1, DCI 1 instructs the terminal device to execute type 1 LBT, when DCI 1 schedules or high-level
  • the configured first transmission is carried on the resources corresponding to COT2.
  • the terminal device executes type 2 LBT, and after the channel access is successful, sends the first transmission in COT2.
  • the network device sends DCI 1 to the terminal device on COT1, and DCI 1 instructs the terminal device to execute type 1 LBT, when DCI 1 schedules or high-level
  • the configured first transmission is borne on resources corresponding to COT2, and the terminal device performs type 3 LBT before transmitting the first transmission, and sends the first transmission in COT2 after channel access is successful.
  • the terminal device after the terminal device successfully accesses the channel, it may be considered that the terminal device shares the COT initiated by the network device, or it may be considered that the terminal device initiates a new COT.
  • the wireless communication method provided in the embodiment of the present application is applied to a network device, as shown in FIG. 5, including:
  • the network device sends first information to the terminal device, the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, and the first information is used to determine the first target channel access type.
  • the first target channel access type is the channel access type to switch from type 1 LBT when the terminal device is instructed to execute type 1 LBT, and the scheduled or configured first transmission is carried on the first resource , the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the terminal equipment and network equipment support the high frequency of 52.6GHz-71GHz, and the terminal equipment and network equipment communicate based on the high frequency of 52.6GHz-71GHz.
  • the terminal equipment and network equipment work in frequency bands other than 52.6GHz-71GHz, such as FR1 and FR2.
  • the terminal device when the terminal device is instructed to perform type 1 LBT, and the first transmission scheduled or configured is carried on the first resource, the terminal device considers that the channel access type switching condition is currently satisfied, and can perform channel access Type switching. At this time, the terminal device switches the channel access type from type 1 LBT to the first target channel access type, and performs channel access based on the first target channel access type.
  • the first target channel access type is determined implicitly based on the first information, and the first information is used to indicate at least one first channel access type in the non-fallback DCI.
  • the first information is a high layer parameter sent by the network device indicating at least one first channel access type in the non-fallback DCI.
  • the non-fallback DCI allows multiple channel access types
  • the network device indicates through the first information that some or all of the multiple channel access types allowed by the non-fallback DCI are at least one of the non-fallback DCI A channel access type.
  • the channel access types allowed by the non-fallback DCI include: type 1 LBT, type 2 LBT, and type 3 LBT
  • the first information indicates that the channel access types in the non-fallback DCI include: type 1 LBT and type 2 LBT .
  • each channel access type allowed by the non-fallback DCI is configured with a different index item
  • the first information carries the index item
  • the terminal device determines the channel access type in the non-fallback DCI based on the index item carried in the first information .
  • the network device may configure the first information to the network device, and send the configured first information to the terminal device.
  • the terminal device determines the first target channel access type based on the first information when the handover indication condition is met.
  • the network device may instruct the terminal device to execute Type 1 LBT through the first DCI sent to the terminal device.
  • the COT that instructs the UE to perform Type 1 LBT is not the same COT as the COT that transmits the first transmission, that is, the first COT.
  • the first DCI may be sent in a COT preceding the first COT.
  • the first transmission is an uplink transmission scheduled by a network device or configured by a high layer.
  • the first transmission may be scheduled by the first DCI.
  • the network device sends the first DCI to the terminal device, and the terminal device receives the first DCI sent by the network device. Based on the first DCI, the terminal device can determine that the first transmission is scheduled and is instructed to perform Type 1 LBT.
  • the first transmission may be PUSCH.
  • the first transmission is configured by a higher layer, the first transmission is CG-PUSCH.
  • the network device may send the second DCI to the terminal device at the first COT, and the second DCI is used to indicate the information of the first COT.
  • the terminal device determines the first transmission scheduled by the first DCI or the first transmission configured by the high layer based on the second DCI.
  • a transmission is carried on the first resource corresponding to the first COT, and the terminal device determines to switch the channel access type.
  • the terminal device After determining the first target channel access type, the terminal device performs channel access based on the first target channel access type after the first resource arrives, and sends the first transmission after the channel access is successful.
  • the first target channel access type may be: type 1 LBT, type 2 LBT or type 3 LBT.
  • the terminal device When the first target channel access type is type 1LBT, and the terminal device meets the channel access type switching conditions, the channel access type switching is performed, and the switched channel access type is still type 1LBT. At this time, the terminal device Still execute type 1 LBT for channel access.
  • the terminal device When the first target channel access type is type 2LBT or type 3LBT, then in the case that the terminal device satisfies the channel access type switching conditions, perform channel access type switching, switching from type 1 LBT to type 2LBT or type 3LBT, at this time , the terminal device executes type 2 LBT or type 3 LBT for channel access.
  • the network device sends DCI 1 to the terminal device on COT1, DCI 1 instructs the terminal device to execute type 1 LBT, when DCI 1 schedules or high-level The configured first transmission is carried on the resource corresponding to COT2.
  • the terminal device executes type 2 LBT, and sends the first transmission on COT2 after the channel access is successful.
  • the network device sends DCI 1 to the terminal device on COT1, and DCI 1 instructs the terminal device to execute type 1 LBT, when DCI 1 schedules or high-level
  • the configured first transmission is carried on the resource corresponding to COT2, and the terminal device performs type 3 LBT before transmitting the first transmission, and sends the first transmission on COT2 after the channel access is successful.
  • the terminal device after the terminal device successfully accesses the channel, it may be considered that the terminal device shares the COT initiated by the network device, or it may be considered that the terminal device initiates a new COT.
  • the first information includes at least one of the following:
  • the first configuration information indicates at least one second channel access type in the first non-fallback DCI, and the first non-fallback DCI is used to schedule the non-fallback uplink of the physical uplink shared channel PUSCH authorization;
  • the second configuration information indicates at least one second channel access type in the second non-fallback DCI, and the second non-fallback DCI is used to schedule the non-fallback downlink of the physical downlink shared channel PDSCH authorized.
  • the first information includes any one of the following three situations:
  • the first information includes first configuration information, and at this time, at least one first channel access type indicated by the first information includes at least one second channel access type in the first non-fallback DCI.
  • the first information includes the second configuration information, and in this case, the at least one first channel access type indicated by the first information includes at least one second channel access type in the second non-fallback DCI.
  • the first information includes the first configuration information and the second configuration information.
  • the first channel access type indicated by the first information includes at least one second channel access type and the second channel access type in the first non-fallback DCI. At least one second channel access type in the two non-fallback DCIs.
  • the first non-fallback DCI may be DCI 0_1 (DCI format 0_1), and the first configuration information is ul-AccessConfigListDCI-0-1.
  • the second non-fallback DCI may be DCI 1_1 (DCI format 1_1), and the second configuration information is ul-AccessConfigListDCI-1-1.
  • the first information includes first configuration information, and the first target channel access type is determined based on at least one second channel access type in the first non-fallback DCI The third channel access type.
  • the manner in which the first information is used to determine the first target channel includes:
  • Determining manner 1 Determine the first target channel access type based on at least one second channel access type on the first non-backoff indicated by the first configuration information.
  • the terminal device determines at least one second channel access type on the first non-fallback DCI based on the first configuration information, and determines the first target channel access type based on the at least one second channel access type on the first non-fallback DCI type.
  • the first information includes second configuration information, and the first target channel access type is determined based on at least one second channel access type in the second non-fallback DCI The third channel access type.
  • the manner in which the first information is used to determine the first target channel includes:
  • Determining manner 2 Determine the first target channel access type based on at least one second channel access type on the second non-backoff indicated by the second configuration information.
  • the terminal device determines at least one second channel access type on the second non-fallback DCI based on the second configuration information, and determines the first target channel access type based on the at least one second channel access type on the second non-fallback DCI type.
  • the first information includes first configuration information and second configuration information
  • the first target channel access type is selected from the fourth channel access type and the fifth channel access type
  • the fourth channel access type is a third channel access type determined based on at least one second channel access type in the first non-backoff DCI
  • the fifth channel access type is based on the first channel access type A third channel access type determined by at least one second channel access type in the two non-fallback DCIs.
  • the manner in which the first information is used to determine the first target channel includes:
  • Determination mode 3 Determine a fourth channel access type based on at least one second channel access type on the first non-fallback DCI indicated by the first configuration information, and determine a fourth channel access type based on the second non-fallback DCI indicated by the second configuration information. at least one second channel access type, determine a fifth channel access type, and select one of the fourth channel access type and the fifth channel access type as the first target channel access type.
  • the terminal device determines at least one second channel access type on the first non-fallback DCI based on the first configuration information, and determines the fourth channel based on at least one second channel access type on the first non-fallback DCI access type, the terminal device determines at least one second channel access type on the second non-fallback DCI based on the second configuration information, and determines the fifth channel access type based on the at least one second channel access type on the second non-fallback DCI
  • the terminal device determines the time-consuming channel access type among the fourth channel access type and the fifth channel access type as the first target channel access type.
  • the first target channel access type is the fourth channel access type.
  • the fourth channel access type is type 2 LBT
  • the fifth channel access type is type 2 LBT
  • the first target channel access type is type 2 LBT.
  • the first target channel access type is the fourth channel access type and the fifth channel access type.
  • the channel access type takes a long time.
  • the fourth channel access type is type 2 LBT
  • the fifth channel access type is type 3 LBT
  • the time consumption of type 2 LBT is greater than that of type 3 LBT
  • the first target channel access type is type 2 LBT.
  • the terminal device determines the first target channel access type according to at least one second channel access type in any one of the first non-fallback DCI and the second non-fallback DCI.
  • the situation of the third channel access type determined based on at least one second channel access type includes at least one of the following:
  • Channel access type case 1 In the case where the at least one second channel access type is type 1 LBT, the third channel access type is type 1 LBT;
  • Channel access type case 2 In the case where the at least one second channel access type includes type 1 LBT and type 2 LBT, the third channel access type is type 2 LBT;
  • Channel access type situation 3 In the case where the at least one second channel access type includes type 1 LBT and type 3 LBT, the third channel access type is type 3 LBT;
  • Channel access type case 4 In the case where the at least one second channel access type includes type 1 LBT, type 2 LBT and type 3 LBT, the third channel access type is type 2 LBT.
  • the first target channel access type when at least one second channel access type only includes type 1 LBT, the first target channel access type is still type 1 LBT. At this time, the terminal device meets the channel access type switching condition, Type 1 LBT still needs to be performed, that is, no channel access type switching is performed.
  • the first target channel access type is Type 2 LBT or Type 3LBT, at this time, the terminal device satisfies Channel access type switching condition, the channel access type is switched from type 1 LBT to type 2 LBT or type 3 LBT.
  • the first target channel access type is type 2 LBT
  • the terminal device satisfies the channel access type switching condition
  • the channel access type is switched from type 1 LBT to type 2 LBT
  • the first target channel access type is type 3 LBT
  • the terminal device meets the channel access type switching conditions, then the channel access type is switched from type 1 LBT to type 3 LBT
  • at least one second channel access type includes type 2 LBT and type 3 LBT in addition to type 1 LBT
  • the first target channel access type is Type 2 LBT and Type 3 LBT, which takes a long time. At this time, the terminal device meets the channel access type switching conditions, and the channel access type is switched from Type 1LBT to Type 1LBT.
  • Type 2 LBT the first target channel access type is Type 2 LBT and Type 3 LBT.
  • the first information is also used to indicate a COT sharing scenario of the terminal device.
  • the first information indicates the first target channel access type when the terminal device meets the channel access type switching condition, and is also used to indicate a COT sharing scenario.
  • the COT sharing scenario can be understood as when the terminal device performs channel access based on the second target channel access type or the third target channel access type when performing COT sharing, that is, before the terminal device shares the COT initiated by the network device for PUSCH transmission Perform channel access based on the second target channel access type indicated by the network device, or perform channel access based on the third target channel access type indicated by the network device before the terminal device shares the COT initiated by the network device for PUCCH transmission.
  • the terminal device shares COT601 for PUSCH transmission, and the DCI0_1 of the network device on COT601 indicates to the terminal device that the second target channel access type is type 2LBT, and the terminal device performs PUSCH transmission before COT601 , execute type 2 LBT to perform channel access, and perform PUSCH transmission in COT601 after successful channel access.
  • the terminal device shares COT701 for PUCCH transmission, and the DCI1_1 of the network device on COT701 indicates to the terminal device that the third channel access type is type 3 LBT.
  • the terminal device execute type 3 LBT to perform channel access, and perform PUCCH transmission on COT701 after successful channel access.
  • PUCCH transmission carries HARQ-ACK.
  • the first configuration information is used to determine a COT sharing scenario for PUSCH transmission.
  • at least one second channel access type in the first non-backoff DCI indicated by the first configuration information is used to determine a COT sharing scenario for PUSCH transmission.
  • the second configuration information is used to determine a COT sharing scenario for PUCCH transmission.
  • at least one second channel access type in the second non-fallback DCI indicated by the second configuration information is used to determine a COT sharing scenario for PUCCH transmission.
  • COT sharing scenarios include:
  • COT sharing scenario 1 The terminal device does not support COT sharing;
  • COT sharing scenario 2 Terminal devices need to implement Type1 LBT during COT sharing;
  • COT sharing scenario 3 Terminal devices execute Type2 LBT during COT sharing;
  • COT sharing scenario 4 Terminal devices execute Type3 LBT during COT sharing;
  • COT sharing scenario 5 the terminal device executes Type2 LBT or Type3 LBT, and the terminal device executes Type2 LBT or Type3 LBT based on the interval between the network device ending the transmission and the terminal device starting the transmission and the set interval.
  • the first information can determine the first target channel access type, it can also determine the COT sharing scenario, so as to realize the association between the first target channel access type and the COT sharing scenario.
  • the COT sharing scenario may be determined based on at least one second channel access type on the first non-fallback DCI or the second non-fallback DCI indicated by at least the first information.
  • the COT sharing scenario determined by the at least one second channel access type on the first non-fallback DCI is aimed at PUSCH transmission when the COT is shared, and the at least one second channel access type determination on the second non-fallback DCI
  • the COT sharing scenario is aimed at the PUCCH transmission carrying the HARQ-ACK when the COT is shared.
  • the COT sharing scenario determined based on at least one second channel access type includes one of the following:
  • the COT sharing scenario is that the terminal device does not support COT sharing or that the terminal device performs type 1 LBT during COT sharing 1 LBT;
  • the COT sharing scenario is that the terminal device executes type 2 LBT during COT sharing;
  • the COT sharing scenario is that the terminal device executes type 3 LBT during COT sharing;
  • the COT sharing scenario is that the terminal device performs Type 2 LBT or Type 2 LBT during COT sharing Type 3 LBT.
  • At least one second channel access type is Type 1 LBT, which means that the terminal device does not support COT sharing, or the terminal device needs to implement Type1 LBT during COT sharing. At this time, even if the terminal device meets the channel access type Switching conditions still need to execute Type1 LBT, that is, switching of the channel access type is not performed.
  • At least one second channel access type is type 1 LBT and type 2 LBT, and the terminal device needs to perform at least type 2 LBT when characterizing COT sharing. At this time, if the UE meets the channel access type switching conditions, then Can be switched from Type 1 LBT to Type 2 LBT.
  • At least one second channel access type is type 1 LBT and type 3 LBT, which means that the terminal device always executes type 3 LBT during COT sharing, which corresponds to COT sharing scheme 1. At this time, if the terminal device meets the channel Access type switching conditions, you can switch from type 1 LBT to type 3 LBT.
  • At least one second channel access type is type 1 LBT, type 2 LBT and type 3 LBT, indicating that the terminal device may implement type 2 LBT or type 3 LBT during COT sharing, which corresponds to COT sharing scheme 2.
  • the terminal device meets the channel access type switching conditions, it can switch from type 1 LBT to type 2 LBT.
  • the number of the second channel access types in the first non-fallback DCI is used to determine the size of the second information on the first non-fallback DCI, and the second information is used for Indicate the second target channel access type, where the second target channel access type is the channel access type used by the terminal device for PUSCH transmission during COT sharing; or,
  • the quantity of the second channel access type in the second non-fallback DCI is used to determine the size of third information on the second non-fallback DCI, and the third information is used to indicate that the third target channel access input type, the third target channel access type is the channel access type used by the terminal device for PUCCH transmission during COT sharing.
  • the second information is information indicating a second target channel access type in the first non-backoff DCI, and the second target channel access type is used for PUSCH transmission when the COT is shared.
  • the second information is ChannelAccess-CPext-CAPC in DCI format 0_1.
  • the size of the second information in the first non-fallback DCI is determined based on the quantity of the second channel access type in the first non-fallback DCI.
  • the size of the second information in the first non-fallback DCI is log 2 I 1 , where I 1 is the number of second channel access types in the first non-fallback DCI.
  • the second channel access type in the first non-fallback DCI includes: type 1LBT and type 2LBT, and I 1 is 2, then the size of the second information in the first non-fallback DCI is 1 bit, when If the value of the second information is 0, the terminal device performs channel access of type 1 LBT before the shared COT performs PUSCH transmission; when the value of the second information is 1, the terminal device performs PUSCH transmission on the shared COT , execute type 2 LBT for channel access.
  • the second channel access type in the first non-backoff DCI includes: type 1LBT, type 2LBT and type 3LBT, and I1 is 3, then the size of the second information in the first non-backoff DCI is 2 bits, when the value of the second information is 00, the terminal device executes type 1 LBT for channel access before performing PUSCH transmission on the shared COT; when the value of the second information is 01, the terminal device performs channel access on the shared COT Before performing PUSCH transmission, execute type 2 LBT for channel access, and when the value of the second information is 10, the terminal device executes type 3 LBT for channel access before performing PUSCH transmission on the shared COT.
  • the third information is information indicating a third target channel access type in the second non-fallback DCI, and the third target channel access type is used for PUCCH transmission when the COT is shared.
  • the third information is ChannelAccess-CPext-CAPC in DCI format 1_1.
  • the size of the third information in the second non-fallback DCI is determined based on the quantity of the second channel access type in the second non-fallback DCI.
  • the size of the third information in the second non-fallback DCI is log 2 I 2 , where I 2 is the number of second channel access types in the second non-fallback DCI.
  • the second channel access type in the second non-fallback DCI includes: type 1 LBT and type 2 LBT, and I 2 is 2, then the size of the third information in the second non-fallback DCI is 1 bit, when The value of the third information is 1, and the terminal device executes type 1 LBT for channel access before the shared COT transmits the PUCCH carrying HARQ-ACK.
  • the terminal device executes type 2 LBT for channel access.
  • the second channel access type in the first non-backoff DCI includes: type 1LBT, type 2LBT and type 3LBT, and I1 is 3, then the size of the third information in the first non-backoff DCI is 2 bits, when the value of the third information is 00, the terminal device performs type 1 LBT for channel access before the shared COT transmits the PUCCH carrying HARQ-ACK; when the value of the third information is 01, the terminal device The device executes type 2 LBT for channel access before the shared COT transmits the PUCCH carrying HARQ-ACK. When the value of the third information is 10, the terminal device performs the shared COT before the PUCCH carrying HARQ-ACK Perform type 3 LBT for channel access.
  • the terminal device also performs the following steps:
  • the terminal device sends first capability indication information to the network device, where the first capability indication information is used to indicate whether the terminal device supports Type 2 LBT.
  • the network device implements the following steps:
  • the network device receives first capability indication information sent by the terminal device, where the first capability indication information is used to indicate whether the terminal device supports Type 2 LBT.
  • the terminal device reports whether it supports Type 2 LBT to the network device through the first capability indication information.
  • the way in which the first capability indication information indicates whether the terminal device supports Type 2 LBT includes one of the following indication ways
  • Indication mode A indicating that the terminal device does not support type 2 LBT based on the sending of the first capability indication information
  • the first capability indication information indicates whether the terminal device supports or does not support Type 2 LBT based on different values.
  • the terminal device sends the first capability indication information to the network device, which indicates that the terminal device does not support type 2 LBT. At this time, when the terminal device does not send the first capability indication information to the network device, it indicates that the terminal device supports Type 2 LBT.
  • the first capability indication information whose value is the first value indicates that the terminal device supports Type 2 LBT
  • the first capability indication information whose value is the second value indicates that the terminal device does not support Type 2 LBT.
  • the terminal device Taking the first capability indication information to indicate whether the terminal device supports type 2 LBT as the indication mode B as an example, if the terminal device supports type 2LBT, then send the first capability indication information with a value of the first value to the network device, and the network The device determines that the terminal device supports type 2LBT based on the first capability indication information with the first value; if the terminal device does not support type 2LBT, it sends the first capability indication information with the second value to the network device, and the network device based on the The first capability indication information whose value is the second value determines that the terminal device does not support type 2 LBT.
  • the network device After receiving the first capability indication information, the network device configures first information for the terminal device based on the received first capability indication information.
  • the at least one first channel access type may include Type 2 LBT.
  • the network device determines that the terminal device supports Type 2LBT, and the at least one first channel access type indicated by the configured first information may or may not include Type 2 LBT 2 LBT.
  • the at least one first channel access type does not include Type 2 LBT.
  • the at least one first channel access type indicated by the first information configured by the network device does not include Type 2 LBT.
  • the wireless communication method provided in the embodiment of the present application is applied to a wireless communication system including a terminal device and a network device, as shown in FIG. 8 , including:
  • the network device sends first information to the terminal device.
  • the first information is used to determine a first target channel access type, and the first target channel access type is the first scheduled or configured first target channel access type that the terminal device is instructed to perform type 1 listen before talk LBT.
  • the transmission is carried on the first resource, switch from type 1 LBT to the channel access type, the first resource is the resource corresponding to the first channel occupancy time COT, and the first COT is the COT initiated by the network device.
  • the method for determining the first target channel access type by the first information may include:
  • the first information indicates at least one first channel access type in the non-fallback DCI, and at this time, based on the first information indicating at least one first channel access type in the non-fallback DCI implicit indicates the first target channel access type.
  • the first information explicitly indicates Type 2 LBT or Type 3 LBT, where different values of the first information indicate different channel access types.
  • the terminal device meets the channel access type switching condition, it switches from type 1 LBT to the first target channel access type indicated by the first information.
  • the first information indicates type 2 LBT
  • the first information indicates type 3 LBT
  • the network device may configure the first information based on a COT sharing scenario.
  • the first information indicates type 3 LBT; when the COT sharing scenario of the terminal device is COT sharing scheme 2, the first information indicates type 2 LBT.
  • the terminal device in the second indication manner, sends the first capability indication information to the network device, and at this time, the network device receives the first capability indication information sent by the terminal device.
  • the first capability indication information in the indication mode 2 is the same as the first capability indication information in the indication mode 1.
  • the description of the first capability indication information please refer to the description of the first capability indication information in the indication mode 1. repeat.
  • the embodiment of the present application provides a scheme for switching channel access types of a UE in a high-frequency unlicensed frequency band.
  • the NRU system supports the switching of UE channel access types. Specifically: if the UE is scheduled for uplink transmission by DCI1 or configured for CG-PUSCH transmission, and Type1 LBT needs to be performed before uplink transmission, but then the UE finds out through DCI2 (corresponding to DCI 2_0) If the previously scheduled or configured uplink transmission occurs within the COT initiated by the base station, the UE can switch from Type1 channel access to Type2A channel access in a COT sharing manner.
  • the base station schedules a PUSCH not in the COT on DCI1 of the previous COT, that is, COT901. Therefore, DCI1 needs to instruct the UE to perform Type1 LBT. Then the base station reacquires a new COT, namely COT902, and the UE finds that the previously scheduled PUSCH occurs in the time-frequency domain resources corresponding to COT902 through DCI 2 on COT902, then at COT902, the UE can switch from Type1 LBT in the way of COT sharing It is Type2A LBT.
  • the high frequency supports two COT sharing schemes:
  • COT sharing scheme 1 when the UE shares the COT initiated by the base station, it always executes Type3 LBT;
  • Type2 LBT/Type3 LBT is executed depending on whether the transmission gap is greater than the threshold value. Among them, when the transmission gap is not greater than the threshold value, Type3 LBT is executed; otherwise, Type2 LBT is executed .
  • the access type of the first target channel that the UE switches to is also different. That is, for COT sharing scheme 1, when the UE meets the channel access type switching conditions, the UE can switch from Type1 LBT to Type3 LBT; for sharing scheme 2, when the UE meets the channel access type switching conditions, the UE can switch from Type1 LBT Switch to Type2 LBT.
  • the UE can determine the first target channel access type to switch to by determining the current COT sharing scheme.
  • the way for the UE to determine the first target channel access type includes:
  • Mode 1 (corresponding to indication mode 1), implicitly determine the first target channel access type
  • Mode 2 (corresponding to indication mode 2), displaying and indicating the access type of the first target channel.
  • the wireless communication method provided by the embodiment of this application may be implemented as but not limited to the following embodiments.
  • the manner of determining the first target channel access type is manner 1, implicitly determining the first target channel access type.
  • the base station will configure the actual channel access type through the high-level parameter ul-AccessConfigListDCI-0-1 from all channel access types allowed by non-fallback DCI according to the current LBT application scenario.
  • the bit width indicating the channel access type in DCI 0_1 is Bit
  • the bit field is 0 corresponding to Type1 LBT
  • the bit field is 1 corresponding to Type3 LBT.
  • the UE can implicitly determine the current COT sharing scenario according to the channel access type configured by high-level parameters in the non-fallback DCI, thereby determining the first target channel access type when switching the channel access type.
  • the channel access type in the high layer parameter configuration non-fallback DCI is Type1 LBT, it means that the current scenario does not support COT sharing, or the UE needs to implement Type1 LBT during COT sharing. At this time, even if the UE meets the channel access type switching conditions, it still needs to perform Type1 LBT.
  • the channel access types in the non-fallback DCI are set to Type1 LBT and Type2 LBT in the high-level parameter configuration, it means that the UE needs to execute at least Type2 LBT when COT is shared. At this time, if the UE meets the channel access type switching conditions, it can switch from Type 1 LBT to Type 2 LBT.
  • the UE If the channel access types in the high-layer parameter configuration non-fallback DCI are Type1 LBT and Type3 LBT, it means that the UE always executes Type3 LBT during COT sharing, which corresponds to COT sharing scheme 1. At this time, if the UE meets the channel access type switching conditions, it can switch from Type1 LBT to Type3 LBT.
  • the channel access types in the high-layer parameter configuration non-fallback DCI are Type1 LBT, Type2 LBT and Type3 LBT, it means that during COT sharing, UE may implement Type2 LBT or Type3 LBT, which corresponds to COT sharing scheme 2.
  • the UE can switch from Type1 LBT to Type2 LBT.
  • the channel access type in non-fallback DCI is configured by high-level parameters
  • Type 1 LBT if Type 2 LBT is additionally configured, when the UE meets the channel access type switching conditions, it can switch from Type 1 LBT Switch to Type2 LBT; otherwise, if Type3 LBT is additionally configured, the UE can switch from Type1 LBT to Type3 LBT when the channel access type switching conditions are met.
  • the above-mentioned scheme for implicitly determining the access type of the first target channel may be based on non-fallback DCI 0_1, may also be based on non-fallback DCI 1_1, or may be jointly determined based on non-fallback DCI 0_1 and 1_1.
  • the LBT that takes longer time as the first target channel access type. For example, based on the channel access types in DCI 0_1 and DCI 1_1 configured by high-level parameters, it is determined that the first target channel access types to switch to are Type2 LBT and Type3 LBT, and when the UE meets the channel access type switching conditions, it can Switch from Type1 LBT to Type2 LBT.
  • the base station can configure the channel access type in the non-fallback DCI for the UE according to the UE capability, so as to ensure that the base station and the UE can access the first target channel after switching.
  • Types share a common understanding. For example, considering that Type2 LBT is a UE capability in high frequencies, if the UE does not support Type2 LBT, the base station will not configure Type2 LBT for the UE in non-fallback DCI; if the UE supports Type2 LBT, the base station will further share information based on the current COT The scenario determines whether to configure Type2 LBT for the UE. Regardless of whether the UE supports Type2 LBT or not, the implicitly determined scheme can ensure that the base station and the UE have a common understanding of the first target channel access type after handover.
  • the manner of determining the first target channel access type is manner 2, explicitly determining the first target channel access type.
  • the base station can also explicitly indicate the switched channel access type for the UE, that is, it can indicate the first target of the UE after switching through system information (further can be SIB1) indication or RRC parameter configuration (further can be cell-level RRC signaling).
  • the channel access type is Type2/Type3 LBT.
  • the base station may indicate/configure the switched channel access type for the UE according to the current COT sharing scheme. For example, if the COT sharing scheme 1 is currently applied, the base station can indicate/configure the switched channel access type for the UE as Type3 LBT; if the COT sharing scheme 2 is currently applied, the base station can indicate/configure the switched channel access type for the UE.
  • the input type is Type2 LBT.
  • Type 2 LBT is a UE capability in high frequency
  • the UE will not switch the channel access type even if it meets the switching conditions of the channel access type, that is, still Maintain Type1 LBT for channel access. In this way, it is ensured that the base station and the UE have a common understanding of the switched channel access type.
  • sequence numbers of the above-mentioned processes do not mean the order of execution, and the order of execution of the processes should be determined by their functions and internal logic, and should not be used in this application.
  • the implementation of the examples constitutes no limitation.
  • the terms “downlink”, “uplink” and “sidelink” are used to indicate the transmission direction of signals or data, wherein “downlink” is used to indicate that the transmission direction of signals or data is sent from the station The first direction to the user equipment in the cell, “uplink” is used to indicate that the signal or data transmission direction is the second direction sent from the user equipment in the cell to the station, and “side line” is used to indicate that the signal or data transmission direction is A third direction sent from UE1 to UE2.
  • “downlink signal” indicates that the transmission direction of the signal is the first direction.
  • the term “and/or” is only an association relationship describing associated objects, indicating that there may be three relationships. Specifically, A and/or B may mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this article generally indicates that the contextual objects are an "or” relationship.
  • Fig. 10 is a schematic diagram of the first structural composition of a wireless communication device provided by an embodiment of the present application, which is applied to a terminal device.
  • the wireless communication device 1000 includes:
  • the first receiving module 1001 is configured to receive first information configured by the network device, the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, and the first information is used to determine the first channel access type A target channel access type, where the first target channel access type is the case where the terminal device is instructed to execute type 1 LBT, and the scheduled or configured first transmission is carried on the first resource, from type 1 LBT
  • the channel access type to switch to, the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the first information includes at least one of the following:
  • the first configuration information indicates at least one second channel access type in the first non-fallback DCI, and the first non-fallback DCI is used to schedule the non-fallback uplink of the physical uplink shared channel PUSCH authorization;
  • the second configuration information indicates at least one second channel access type in the second non-fallback DCI, and the second non-fallback DCI is used to schedule the non-fallback downlink of the physical downlink shared channel PDSCH authorized.
  • the first target channel access type is based on at least one second channel access type in the first non-backoff DCI The determined third channel access type.
  • the first target channel access type is based on at least one second channel access in the second non-backoff DCI The type determines the third access type.
  • the first target channel access type is selected from the fourth channel access type and the fifth channel access type. Selected from the access type, the fourth channel access type is a third channel access type determined based on at least one second channel access type in the first non-backoff DCI, and the fifth channel access type The type is a third channel access type determined based on at least one second channel access type in the second non-fallback DCI.
  • the first target channel access type is the fourth channel access type
  • the first target channel access type is the fourth channel access type and the fifth channel access type takes a long time.
  • the third channel access type is type 1 LBT.
  • the third channel access type is Type 2 LBT.
  • the third channel access type is Type 3 LBT.
  • the third channel access type is type 2 LBT.
  • the first information is further used to indicate a COT sharing scenario of the terminal device.
  • the COT sharing scenario is that the terminal device does not support COT sharing or the terminal device performs COT sharing Type 1 LBT.
  • the COT sharing scenario is that the terminal device at least executes type 2 LBT during COT sharing.
  • the COT sharing scenario is that the terminal device performs type 3 LBT during COT sharing.
  • the COT sharing scenario is that the terminal device performs type 2 LBT during COT sharing Or Type 3 LBT.
  • device 1000 also includes:
  • the first sending module is configured to send first capability indication information to the network device, where the first capability indication information is used to indicate whether the terminal device supports Type 2 LBT.
  • the at least one first channel access type does not include Type 2 LBT.
  • Fig. 11 is a schematic diagram of the first structural composition of a wireless communication device provided by an embodiment of the present application, which is applied to a network device.
  • the wireless communication device 1100 includes:
  • the second sending module 1101 is configured to send first information to the terminal device, the first information indicates at least one first channel access type in the non-fallback downlink control information DCI, and the first information is used to determine the first A target channel access type, where the first target channel access type is the case where the terminal device is instructed to execute type 1 listen-before-talk LBT, and the scheduled or configured first transmission is carried on the first resource , the channel access type switched from type 1 LBT, the first resource is a resource corresponding to a first channel occupancy time COT, and the first COT is a COT initiated by a network device.
  • the first information includes at least one of the following:
  • the first configuration information indicates at least one second channel access type in the first non-fallback DCI, and the first non-fallback DCI is used to schedule the non-fallback uplink of the physical uplink shared channel PUSCH authorization;
  • the second configuration information indicates at least one second channel access type in the second non-fallback DCI, and the second non-fallback DCI is used to schedule the non-fallback downlink of the physical downlink shared channel PDSCH authorized.
  • the first target channel access type is based on at least one second channel access type in the first non-backoff DCI The determined third channel access type.
  • the first target channel access type is based on at least one second channel access in the second non-backoff DCI The third access type determined by the type.
  • the first target channel access type is selected from the fourth channel access type and the fifth channel access type. Selected from the access type, the fourth channel access type is a third channel access type determined based on at least one second channel access type in the first non-backoff DCI, and the fifth channel access type The type is a third channel access type determined based on at least one second channel access type in the second non-fallback DCI.
  • the first target channel access type is the fourth channel access type
  • the first target channel access type is the fourth channel access type and the fifth channel access type takes a long time.
  • the third channel access type is type 1 LBT.
  • the third channel access type is Type 2 LBT.
  • the third channel access type is Type 3 LBT.
  • the third channel access type is type 2 LBT.
  • the first information is further used to indicate a COT sharing scenario of the terminal device.
  • the COT sharing scenario is that the terminal device does not support COT sharing or the terminal device performs COT sharing Type 1 LBT.
  • the COT sharing scenario is that the terminal device at least executes type 2 LBT during COT sharing.
  • the COT sharing scenario is that the terminal device performs type 3 LBT during COT sharing.
  • the COT sharing scenario is that the terminal device performs type 2 LBT during COT sharing Or Type 3 LBT.
  • device 1100 also includes:
  • the second receiving module is configured to receive first capability indication information sent by the terminal device, where the first capability indication information is used to indicate whether the terminal device supports Type 2 LBT.
  • the at least one first channel access type does not include Type 2 LBT.
  • Fig. 12 is a schematic structural diagram of a communication device 1200 provided by an embodiment of the present application.
  • the communication device may be a terminal device or a network device.
  • the communication device 1200 shown in FIG. 12 includes a processor 1210, and the processor 1210 can invoke and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the communication device 1200 may further include a memory 1220 .
  • the processor 1210 can invoke and run a computer program from the memory 1220, so as to implement the method in the embodiment of the present application.
  • the memory 1220 may be an independent device independent of the processor 1210 , or may be integrated in the processor 1210 .
  • the communication device 1200 may further include a transceiver 1230, and the processor 1210 may control the transceiver 1230 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.
  • the processor 1210 may control the transceiver 1230 to communicate with other devices, specifically, to send information or data to other devices, or receive other Information or data sent by the device.
  • the transceiver 1230 may include a transmitter and a receiver.
  • the transceiver 1230 may further include antennas, and the number of antennas may be one or more.
  • the communication device 1200 may specifically be the network device of the embodiment of the present application, and the communication device 1200 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, details are not repeated here. .
  • the communication device 1200 may specifically be the mobile terminal/terminal device of the embodiment of the present application, and the communication device 1200 may implement the corresponding processes implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, for the sake of brevity , which will not be repeated here.
  • FIG. 13 is a schematic structural diagram of a chip according to an embodiment of the present application.
  • the chip 1300 shown in FIG. 13 includes a processor 1310, and the processor 1310 can call and run a computer program from a memory, so as to implement the method in the embodiment of the present application.
  • the chip 1300 may further include a memory 1320 .
  • the processor 1310 can invoke and run a computer program from the memory 1320, so as to implement the method in the embodiment of the present application.
  • the memory 1320 may be an independent device independent of the processor 1310 , or may be integrated in the processor 1310 .
  • the chip 1300 may also include an input interface 1330 .
  • the processor 1310 can control the input interface 1330 to communicate with other devices or chips, specifically, can obtain information or data sent by other devices or chips.
  • the chip 1300 may also include an output interface 1340 .
  • the processor 1310 can control the output interface 840 to communicate with other devices or chips, specifically, can output information or data to other devices or chips.
  • the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application.
  • the chip can implement the corresponding processes implemented by the network device in the methods of the embodiment of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
  • the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
  • the chip can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application.
  • the chip mentioned in the embodiment of the present application may also be called a system-on-chip, a system-on-chip, a system-on-a-chip, or a system-on-a-chip.
  • Fig. 14 is a schematic block diagram of a communication system 1400 provided by an embodiment of the present application. As shown in FIG. 14 , the communication system 1400 includes a terminal device 1410 and a network device 1420 .
  • the terminal device 1410 can be used to realize the corresponding functions realized by the terminal device in the above method
  • the network device 1420 can be used to realize the corresponding functions realized by the network device in the above method.
  • the processor in the embodiment of the present application may be an integrated circuit chip, which has a signal processing capability.
  • each step of the above-mentioned method embodiments may be completed by an integrated logic circuit of hardware in a processor or instructions in the form of software.
  • the above-mentioned processor can be a general-purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), an off-the-shelf programmable gate array (Field Programmable Gate Array, FPGA) or other available Program logic devices, discrete gate or transistor logic devices, discrete hardware components.
  • DSP Digital Signal Processor
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • a general-purpose processor may be a microprocessor, or the processor may be any conventional processor, or the like.
  • the steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field such as random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, register.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a nonvolatile memory, or may include both volatile and nonvolatile memories.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electronically programmable Erase Programmable Read-Only Memory (Electrically EPROM, EEPROM) or Flash.
  • the volatile memory can be Random Access Memory (RAM), which acts as external cache memory.
  • RAM Static Random Access Memory
  • SRAM Static Random Access Memory
  • DRAM Dynamic Random Access Memory
  • Synchronous Dynamic Random Access Memory Synchronous Dynamic Random Access Memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data Rate SDRAM, DDR SDRAM enhanced synchronous dynamic random access memory
  • Enhanced SDRAM, ESDRAM synchronous connection dynamic random access memory
  • Synchlink DRAM, SLDRAM Direct Memory Bus Random Access Memory
  • Direct Rambus RAM Direct Rambus RAM
  • the memory in the embodiment of the present application may also be a static random access memory (static RAM, SRAM), a dynamic random access memory (dynamic RAM, DRAM), Synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous connection Dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is, the memory in the embodiments of the present application is intended to include, but not be limited to, these and any other suitable types of memory.
  • the embodiment of the present application also provides a computer-readable storage medium for storing computer programs.
  • the computer-readable storage medium can be applied to the network device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application.
  • the computer program enables the computer to execute the corresponding processes implemented by the network device in the methods of the embodiments of the present application.
  • the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the various methods of the embodiments of the present application , for the sake of brevity, it is not repeated here.
  • the embodiment of the present application also provides a computer program product, including computer program instructions.
  • the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the Let me repeat for the sake of brevity, the Let me repeat.
  • the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods of the embodiments of the present application, For the sake of brevity, details are not repeated here.
  • the embodiment of the present application also provides a computer program.
  • the computer program can be applied to the network device in the embodiment of the present application.
  • the computer program executes the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program executes the corresponding process implemented by the network device in each method of the embodiment of the present application.
  • the computer program can be applied to the mobile terminal/terminal device in the embodiment of the present application.
  • the computer program executes each method in the embodiment of the present application to be implemented by the mobile terminal/terminal device
  • the corresponding process will not be repeated here.
  • the disclosed systems, devices and methods may be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of the units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components can be combined or May be integrated into another system, or some features may be ignored, or not implemented.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of devices or units may be in electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or may be distributed to multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, each unit may exist separately physically, or two or more units may be integrated into one unit.
  • the functions described above are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or the part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including Several instructions are used to make a computer device (which may be a personal computer, a server, or a network device, etc.) execute all or part of the steps of the methods described in the various embodiments of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (Read-Only Memory,) ROM, random access memory (Random Access Memory, RAM), magnetic disk or optical disc, etc., which can store program codes. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例提供一种无线通信方法及装置、终端设备、网络设备，该方法包括：终端设备接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。

Description

一种无线通信方法及装置、终端设备、网络设备 技术领域
本申请实施例涉及移动通信技术领域，具体涉及一种无线通信方法及装置、终端设备、网络设备。
背景技术
在移动通信系统中，非授权频段(unlicensed band)可以作为授权频段(licensed band)的补充，以帮助运营商对服务进行扩容。为了新空口(New Radio，NR)系统中的部署保持一致，并尽可能的最大化基于NR系统的非授权接入，非授权频段可以工作在5GHz、37GHz和60GHz频段。非授权频段的大带宽(80MHz或者100MHz)能够减小基站(gNB)和终端(User Equipment，UE)的实施复杂度，但是由于非授权频段由多种无线接入技术(Radio Access Technology，RAT)共用，例如无线保真WiFi、雷达、长期演进系统授权频谱辅助接入(Long Term Evolution License Assisted Access，LTE-LAA)等，因此，非授权频段在使用时必须符合某些规则以保证所有设备可以公平的使用该资源，例如先听后说(Listen Before Talk，LBT)，最大信道占用时间(Maximum Channel Occupancy Time，MCOT)等规则。
NRU系统中支持UE以信道占用时间(Channel Occupa ncy Time，COT)共享的方式从类型(Type)1 LBT切换为Type2A LBT，但NRU的切换方式对于高频不再适用，需要重新设计高频中信道切换方案。
发明内容
本申请实施例提供一种无线通信方法及装置、终端设备、网络设备。
本申请实施例提供的无线通信方法包括：
终端设备接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息(Downlink Control Information，DCI)中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
本申请实施例提供的无线通信方法包括：
网络设备向终端设备发送第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
本申请实施例提供的无线通信装置，包括：
第一接收模块，配置为接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
本申请实施例提供的无线通信装置，包括：
第二发送模块，配置为向终端设备发送第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
本申请实施例提供的通信设备，可以是上述方案中的终端设备或者是上述方案中的网络设备，该通信设备包括处理器和存储器。该存储器用于存储计算机程序，该处理器用于调用并运行该存储器中存储的计算机程序，执行上述的无线通信方法。
本申请实施例提供的芯片，用于实现上述的无线通信方法。
具体地，该芯片包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有该芯片的设备执行上述的无线通信方法。
本申请实施例提供的计算机可读存储介质，用于存储计算机程序，该计算机程序使得计算机执行上述的无线通信方法。
本申请实施例提供的计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行上述的无线通信方法。
本申请实施例提供的计算机程序，当其在计算机上运行时，使得计算机执行上述的无线通信方法。
通过上述技术方案，通过非回退DCI中的第一信道接入类型隐式地指示终端设备满足信道接入切换类型时的第一目标信道接入类型，以在满足信道接入切换条件时，基于第一目标信道接入类型进行信道接入，从而适应高频的COT共享。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1是本申请实施例的一个应用场景的示意图；
图2是本申请实施例提供的无线通信方法的可选地流程示意图；
图3是本申请实施例的提供的COT共享的可选地示意图；
图4是本申请实施例提供的COT共享的可选地示意图；
图5是本申请实施例提供的无线通信方法的可选地流程示意图；
图6是本申请实施例的提供的COT共享的可选地示意图；
图7是本申请实施例的提供的COT共享的可选地示意图；
图8是本申请实施例提供的无线通信方法的可选地流程示意图；
图9是本申请实施例提供的COT共享的可选地示意图；
图10是本申请实施例提供的一种无线通信装置的可选地示意性结构图；
图11是本申请实施例提供的一种无线通信装置的可选地示意性结构图；
图12是本申请实施例提供的一种通信设备示意性结构图；
图13是本申请实施例的芯片的示意性结构图；
图14是本申请实施例提供的一种通信系统的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
图1是本申请实施例的一个应用场景的示意图。
如图1所示，通信系统100可以包括终端设备110和网络设备120。网络设备120可以通过空口与终端设备110通信。终端设备110和网络设备120之间支持多业务传输。
应理解，本申请实施例仅以通信系统100进行示例性说明，但本申请实施例不限定于此。也就是说，本申请实施例的技术方案可以应用于各种通信系统，例如：长期演进(Long Term Evolution，LTE)系统、LTE时分双工(Time Division Duplex，TDD)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、物联网(Internet of Things，IoT)系统、窄带物联网(Narrow Band Internet of Things，NB-IoT)系统、增强的机器类型通信(enhanced Machine-Type Communications，eMTC)系统、5G通信系统(也称为新无线(New Radio，NR)通信系统)，或未来的通信系统等。
在图1所示的通信系统100中，网络设备120可以是与终端设备110通信的接入网设备。接入网设备可以为特定的地理区域提供通信覆盖，并且可以与位于该覆盖区域内的终端设备110(例如 UE)进行通信。
网络设备120可以是长期演进(Long Term Evolution，LTE)系统中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者是下一代无线接入网(Next Generation Radio Access Network，NG RAN)设备，或者是NR系统中的基站(gNB)，或者是云无线接入网络(Cloud Radio Access Network，CRAN)中的无线控制器，或者该网络设备120可以为中继站、接入点、车载设备、可穿戴设备、集线器、交换机、网桥、路由器，或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)中的网络设备等。
终端设备110可以是任意终端设备，其包括但不限于与网络设备120或其它终端设备采用有线或者无线连接的终端设备。
例如，所述终端设备110可以指接入终端、UE、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。接入终端可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、IoT设备、卫星手持终端、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备、5G网络中的终端设备或者未来演进网络中的终端设备等。
无线通信系统100还可以包括与基站进行通信的核心网设备130，该核心网设备130可以是5G核心网(5G Core，5GC)设备，例如，接入与移动性管理功能(Access and Mobility Management Function，AMF)，又例如，认证服务器功能(Authentication Server Function，AUSF)，又例如，用户面功能(User Plane Function，UPF)，又例如，会话管理功能(Session Management Function，SMF)。可选地，核心网络设备130也可以是LTE网络的分组核心演进(Evolved Packet Core，EPC)设备，例如，会话管理功能+核心网络的数据网关(Session Management Function+Core Packet Gateway，SMF+PGW-C)设备。应理解，SMF+PGW-C可以同时实现SMF和PGW-C所能实现的功能。在网络演进过程中，上述核心网设备也有可能叫其它名字，或者通过对核心网的功能进行划分形成新的网络实体，对此本申请实施例不做限制。
通信系统100中的各个功能单元之间还可以通过下一代网络(next generation，NG)接口建立连接实现通信。
例如，终端设备通过Uu接口与接入网设备建立空口连接，用于传输用户面数据和控制面信令；终端设备可以通过NG接口1(简称N1)与AMF建立控制面信令连接；接入网设备例如下一代无线接入基站(gNB)，可以通过NG接口3(简称N3)与UPF建立用户面数据连接；接入网设备可以通过NG接口2(简称N2)与AMF建立控制面信令连接；UPF可以通过NG接口4(简称N4)与SMF建立控制面信令连接；UPF可以通过NG接口6(简称N6)与数据网络交互用户面数据；AMF可以通过NG接口11(简称N11)与SMF建立控制面信令连接；SMF可以通过NG接口7(简称N7)与PCF建立控制面信令连接。
图1示例性地示出了一个基站、一个核心网设备和两个终端设备，可选地，该无线通信系统100可以包括多个基站设备并且每个基站的覆盖范围内可以包括其它数量的终端设备，本申请实施例对此不做限定。
需要说明的是，图1只是以示例的形式示意本申请所适用的系统，当然，本申请实施例所示的方法还可以适用于其它系统。此外，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。还应理解，在本申请的实施例中提到的“指示”可以是直接指示，也可以是间接指示，还可以是表示具有关联关系。举例说明，A指示B，可以表示A直接指示B，例如B可以通过A获取；也可以表示A间接指示B，例如A指示C，B可以通过C获取；还可以表示A和B之间具有关联关系。还应理解，在本申请的实施例中提到的“对应”可表示两者之间具有直接对应或间接对应的关系，也可以表示两者之间具有关联关系，也可以是指示与被指示、配置与被配置等关系。还应理解，在本申请的实施例中提到的“预定义”或“预定义规则”可以通过在设备(例如，包括终端设备和网络设备)中预先保存相应的代码、表格或其他可用于指示相关信息的方式来实现，本申请对于其具体的实现方式不做限定。比如预定义可以是指协议中定义的。还应理解，本申请实施例中，所述"协议"可以指通信领域的标准协议，例如可以包括LTE协议、NR协议以及应用于未来的通信系统中的相关协议，本申请对此不做限定。
为便于理解本申请实施例的技术方案，以下对本申请实施例的相关技术进行说明，以下相关技 术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。
对于传输节点，该传输节点也可以叫作发起设备(initiating device)，该传输节点可以包括基站和UE，当传输节点获得信道后，可以将COT共享给接收节点，该接收节点也可以称为响应设备(responding device)，该接收节点也可以包括UE和基站。即当基站为initiating device时，UE是responding device；当UE为initiating device时，基站是responding device。
信道接入类型切换
NRU系统中，如果UE通过DCI 2_0确定基站发起的COT的时间长度和频域位置，则可以应用如下流程：
－ 如果UE的上行传输发生在基站发起的COT对应的时频域资源内，则UE可以从Type 1信道接入切换为Type 2A信道接入。
高频系统中，如果基站/UE使用Type1 LBT在信道上发起COT，则可以在DL/UL传输后将COT共享给UE/基站进行UL/DL传输，此时，响应设备需要遵守以下流程：
COT共享方案1、无论UL/DL传输和之前的DL/UL传输之间的空隙大小，该UL/DL传输之前无需执行LBT(也即Type3 LBT)，直接进行UL/DL传输；
COT共享方案2、如果UL/DL传输和之前DL/UL传输之间的空隙超过由基站确定的门限值(至少8微秒(μs))，则在UL/DL传输开始前执行Type 2 LBT，否则，该UL/DL传输之前执行Type 3 LBT。
其中，方案1或方案2的使用取决于基站的选择，且至少需要考虑当地法规要求。
非回退(non-fallback)DCI
DCI格式0_1为调度物理上行共享信道(Physical Uplink Share Channel，PUSCH)传输的非回退上行授权。在共享频谱信道接入的小区中，携带0-6比特ChannelAccess-CPext-CAPC信息。且比特位宽为log 2I比特，其中，I为高层参数ul-AccessConfigListDCI-0-1配置的索引数即索引项的数量。高频中DCI 0_1允许的索引由高层参数配置，可如表1所示。
表1.高频中DCI格式0_1允许的索引
索引项 信道接入类型
0 Type1信道接入
1 Type2信道接入
2 Type3信道接入
DCI格式1_1为调度物理下行共享信道(Physical Downlink Share Channel，PDSCH)传输的非回退上行授权。在共享频谱信道接入的小区中，携带0-4比特ChannelAccess-CPext-CAPC信息。且比特位宽为log 2I比特，其中，I为高层参数ul-AccessConfigListDCI-1-1配置的索引数。高频中DCI 1_1允许的索引由高层配置，如表2所示，且该信道接入方式用于携带混合自动重传请求(Hybrid Automatic Repeat Request，HARQ)-确认(ACK)的物理上行控制信道(Physical Uplink Control Channel，PUCCH)传输。
表2.高频中DCI格式1_1允许的索引
索引项 信道接入类型
0 Type1信道接入
1 Type2信道接入
2 Type3信道接入
NRU系统支持UE以COT共享的方式从Type1 LBT切换为Type2A LBT，但由于高频支持两种COT共享方式，因此，需要明确UE从Type1LBT切换到哪种信道接入类型，从而保证基站和UE对于切换后的信道接入类型有着共同的理解。
为便于理解本申请实施例的技术方案，以下通过具体实施例详述本申请的技术方案。以上相关技术作为可选方案与本申请实施例的技术方案可以进行任意结合，其均属于本申请实施例的保护范围。本申请实施例包括以下内容中的至少部分内容。
本申请实施例提供的无线通信方法，应用于终端设备，如图2所示，包括：
S201、终端设备接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息DCI中 的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型。
所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
终端设备和网络设备支持52.6GHz-71GHz的高频，终端设备与网络设备基于52.6GHz-71GHz的高频进行通信。可选地，终端设备和网络设备工作在52.6GHz-71GHz以外的频段，比如：FR1、FR2。
本申请实施例中，当终端设备被指示执行类型1LBT，且被调度或被配置的第一传输承载在第一资源上，则终端设备认为当前满足信道接入类型切换条件，可以进行信道接入类型的切换。此时，终端设备将信道接入类型从类型1LBT切换为第一目标信道接入类型，基于第一目标信道接入类型进行信道接入。
本申请实施例中，第一目标信道接入类型基于第一信息隐式确定，第一信息用于指示非回退DCI中的至少一个第一信道接入类型。
可选地，第一信息为网络设备发送的指示非回退DCI中的至少一个第一信道接入类型的高层参数。
本申请实施例中，非回退DCI允许多个信道接入类型，网络设备通过第一信息指示非回退DCI允许的多个信道接入类型中的部分或全部为非回退DCI中的至少一个信道接入类型。
在一示例中，非回退DCI允许的信道接入类型包括：类型1 LBT、类型2LBT和类型3 LBT，第一信息指示非回退DCI中的信道接入类型包括：类型1 LBT和类型2LBT。
可选地，非回退DCI允许的各信道接入类型配置有不同的索引项，第一信息携带索引项，终端设备基于第一信息携带的索引项确定非回退DCI中的信道接入类型。
本申请实施例中，终端设备在初始接入后，网络设备可向网络设备配置第一信息，并将配置的第一信息发送至终端设备。终端设备在满足切换指示条件时，基于第一信息确定第一目标信道接入类型。
本申请实施例中，网络设备可通过向终端设备发送的第一DCI指示终端设备执行类型1 LBT。此时，指示UE执行类型1 LBT的COT与传输第一传输的COT即第一COT不是同一个COT。其中，第一DCI可在第一COT的前一个COT发送。
第一传输为由网络设备调度或由高层配置的上行传输。
在第一传输由网络设备调度的情况下，第一传输可由第一DCI调度。此时，网络设备向终端设备发送第一DCI，终端设备接收网络设备发送的第一DCI，终端设备基于第一DCI能够确定被调度第一传输，并确定被指示执行类型1 LBT。
本申请实施例中，第一传输可为PUSCH。当第一传输为高层配置的，第一传输为CG-PUSCH。
网络设备在第一COT可向终端设备发送第二DCI，第二DCI用于指示第一COT的信息，此时，终端设备基于第二DCI确定第一DCI调度的第一传输或高层配置的第一传输承载在第一COT对应的第一资源上，终端设备确定执行信道接入类型的切换。
终端设备确定第一目标信道接入类型后，在第一资源达到后，基于第一目标信道接入类型执行信道接入，并在信道接入成功后进行第一传输的发送。
本申请实施例中，第一目标信道接入类型可为：类型1LBT、类型2 LBT或类型3LBT。
当第一目标信道接入类型为类型1LBT，则终端设备满足信道接入类型切换条件的情况下，执行信道接入类型切换，且切换后的信道接入类型仍然为类型1LBT，此时，终端设备仍然执行类型1 LBT进行信道接入。
当第一目标信道接入类型为类型2LBT或类型3LBT，则终端设备满足信道接入类型切换条件的情况下，执行信道接入类型切换，从类型1 LBT切换为类型2LBT或类型3LBT，此时，终端设备执行类型2LBT或类型3LBT进行信道接入。
以第一目标信道接入类型为类型2 LBT为例，如图3所示，网络设备在COT1上向终端设备发送DCI 1，DCI 1指示终端设备执行类型1 LBT，当DCI 1调度的或高层配置的第一传输承载在COT2对应的资源上，终端设备在开始传输第一传输之前，执行类型2 LBT，并在信道接入成功后，在COT2进行第一传输的发送。
以第一目标信道接入类型为类型3 LBT为例，如图4所示，网络设备在COT1上向终端设备发送DCI 1，DCI 1指示终端设备执行类型1 LBT，当DCI 1调度的或高层配置的第一传输承载在COT2对应的资源上，终端设备在传输第一传输之前，执行类型3LBT，并在信道接入成功后，在COT2 进行第一传输的发送。
本申请实施例中，终端设备在信道接入成功后，可认为是终端设备共享网络设备发起的COT，也可认为是终端设备发起了新的COT。
本申请实施例提供的无线通信方法，应用于网络设备，如图5所示，包括：
S501、网络设备向终端设备发送第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型。
所述第一目标信道接入类型为所述终端设备被指示执行类型1LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
终端设备和网络设备支持52.6GHz-71GHz的高频，终端设备与网络设备基于52.6GHz-71GHz的高频进行通信。可选地，终端设备和网络设备工作在52.6GHz-71GHz以外的频段，比如：FR1、FR2。
本申请实施例中，当终端设备被指示执行类型1LBT，且被调度或被配置的第一传输承载在第一资源上，则终端设备认为当前满足信道接入类型切换条件，可以进行信道接入类型的切换。此时，终端设备将信道接入类型从类型1LBT切换为第一目标信道接入类型，基于第一目标信道接入类型进行信道接入。
本申请实施例中，第一目标信道接入类型基于第一信息隐式确定，第一信息用于指示非回退DCI中的至少一个第一信道接入类型。
可选地，第一信息为网络设备发送的指示非回退DCI中的至少一个第一信道接入类型的高层参数。
本申请实施例中，非回退DCI允许多个信道接入类型，网络设备通过第一信息指示非回退DCI允许的多个信道接入类型中的部分或全部为非回退DCI中的至少一个信道接入类型。
在一示例中，非回退DCI允许的信道接入类型包括：类型1 LBT、类型2LBT和类型3 LBT，第一信息指示非回退DCI中的信道接入类型包括：类型1 LBT和类型2LBT。
可选地，非回退DCI允许的各信道接入类型配置有不同的索引项，第一信息携带索引项，终端设备基于第一信息携带的索引项确定非回退DCI中的信道接入类型。
本申请实施例中，终端设备在初始接入后，网络设备可向网络设备配置第一信息，并将配置的第一信息发送至终端设备。终端设备在满足切换指示条件时，基于第一信息确定第一目标信道接入类型。
本申请实施例中，网络设备可通过向终端设备发送的第一DCI指示终端设备执行类型1 LBT。此时，指示UE执行类型1 LBT的COT与传输第一传输的COT即第一COT不是同一个COT。其中，第一DCI可在第一COT的前一个COT发送。
第一传输为由网络设备调度或由高层配置的上行传输。
在第一传输由网络设备调度的情况下，第一传输可由第一DCI调度。此时，网络设备向终端设备发送第一DCI，终端设备接收网络设备发送的第一DCI，终端设备基于第一DCI能够确定被调度第一传输，并确定被指示执行类型1 LBT。
本申请实施例中，第一传输可为PUSCH。当第一传输为高层配置的，第一传输为CG-PUSCH。
网络设备在第一COT可向终端设备发送第二DCI，第二DCI用于指示第一COT的信息，此时，终端设备基于第二DCI确定第一DCI调度的第一传输或高层配置的第一传输承载在第一COT对应的第一资源上，终端设备确定执行信道接入类型的切换。
终端设备确定第一目标信道接入类型后，在第一资源达到后，基于第一目标信道接入类型执行信道接入，并在信道接入成功后进行第一传输的发送。
本申请实施例中，第一目标信道接入类型可为：类型1LBT、类型2 LBT或类型3LBT。
当第一目标信道接入类型为类型1LBT，则终端设备满足信道接入类型切换条件的情况下，执行信道接入类型切换，切换后的信道接入类型仍然为类型1LBT，此时，终端设备仍然执行类型1 LBT进行信道接入。
当第一目标信道接入类型为类型2LBT或类型3LBT，则终端设备满足信道接入类型切换条件的情况下，执行信道接入类型切换，从类型1 LBT切换为类型2LBT或类型3LBT，此时，终端设备执行类型2LBT或类型3LBT进行信道接入。
以第一目标信道接入类型为类型2 LBT为例，如图3所示，网络设备在COT1上向终端设备发 送DCI 1，DCI 1指示终端设备执行类型1 LBT，当DCI 1调度的或高层配置的第一传输承载在COT2对应的资源上，终端设备在开始传输第一传输之前，执行类型2 LBT，并在信道接入成功后，在COT2上进行第一传输的发送。
以第一目标信道接入类型为类型3 LBT为例，如图4所示，网络设备在COT1上向终端设备发送DCI 1，DCI 1指示终端设备执行类型1 LBT，当DCI 1调度的或高层配置的第一传输承载在COT2对应的资源上，终端设备在传输第一传输之前，执行类型3LBT，并在信道接入成功后，在COT2上进行第一传输的发送。
本申请实施例中，终端设备在信道接入成功后，可认为是终端设备共享网络设备发起的COT，也可认为是终端设备发起了新的COT。
在一些实施例中，所述第一信息包括以下至少之一：
第一配置信息，所述第一配置信息指示第一非回退DCI中的至少一个第二信道接入类型，所述第一非回退DCI用于调度物理上行共享信道PUSCH的非回退上行授权；
第二配置信息，所述第二配置信息指示第二非回退DCI中的至少一个第二信道接入类型，所述第二非回退DCI用于调度物理下行共享信道PDSCH的非回退下行授权。
本申请实施例中，第一信息包括以下三种情况中的任一一种：
情况一、第一信息包括第一配置信息，此时，第一信息指示的至少一个第一信道接入类型包括第一非回退DCI中的至少一个第二信道接入类型。
情况二，第一信息包括第二配置信息，此时，第一信息指示的至少一个第一信道接入类型包括第二非回退DCI中的至少一个第二信道接入类型。
情况三，第一信息包括第一配置信息和第二配置信息，此时，第一信息指示的第一信道接入类型包括第一非回退DCI中的至少一个第二信道接入类型和第二非回退DCI中的至少一个第二信道接入类型。
可选地，第一非回退DCI可为DCI 0_1(DCI格式0_1)，第一配置信息为ul-AccessConfigListDCI-0-1。
可选地，第二非回退DCI可为DCI 1_1(DCI格式1_1)，第二配置信息为ul-AccessConfigListDCI-1-1。
以第一信息为情况一为例，第一信息包括第一配置信息，所述第一目标信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
此时，第一信息用于确定第一目标信道的方式包括：
确定方式一、基于第一配置信息指示的第一非回退上的至少一个第二信道接入类型，确定第一目标信道接入类型。
终端设备基于第一配置信息确定第一非回退DCI上的至少一个第二信道接入类型，并基于第一非回退DCI上的至少一个第二信道接入类型确定第一目标信道接入类型。
以第一信息为情况二为例，第一信息包括第二配置信息，所述第一目标信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
此时，第一信息用于确定第一目标信道的方式包括：
确定方式二、基于第二配置信息指示的第二非回退上的至少一个第二信道接入类型，确定第一目标信道接入类型。
终端设备基于第二配置信息确定第二非回退DCI上的至少一个第二信道接入类型，并基于第二非回退DCI上的至少一个第二信道接入类型确定第一目标信道接入类型。
以第一信息为情况三为例，第一信息包括第一配置信息和第二配置信息，所述第一目标信道接入类型从第四信道接入类型和第五信道接入类型中选择，所述第四信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型，所述第五信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
此时，第一信息用于确定第一目标信道的方式包括：
确定方式三、基于第一配置信息指示的第一非回退DCI上的至少一个第二信道接入类型，确定第四信道接入类型，基于第二配置信息指示的第二非回退DCI上的至少一个第二信道接入类型，确定第五信道接入类型，并从第四信道接入类型和第五信道接入类型中选择一个作为第一目标信道接入类型。
此时，终端设备基于第一配置信息确定第一非回退DCI上的至少一个第二信道接入类型，并基于第一非回退DCI上的至少一个第二信道接入类型确定第四信道接入类型，终端设备基于第二配置 信息确定第二非回退DCI上的至少一个第二信道接入类型，并基于第二非回退DCI上的至少一个第二信道接入类型确定第五信道接入类型，终端设备将第四信道接入类型和第五信道接入类型中耗时长的信道接入类型确定为第一目标信道接入类型。
可选地，在所述第四信道接入类型和所述第五信道接入类型相同的情况下，所述第一目标信道接入类型为所述第四信道接入类型。
在一示例中，第四信道接入类型为类型2LBT，第五信道接入类型为类型2LBT，则第一目标信道接入类型为类型2 LBT。
可选地，在所述第四信道接入类型和所述第五信道接入类型不同的情况下，所述第一目标信道接入类型为所述第四信道接入类型和所述第五信道接入类型中耗时较长的。
在一示例中，第四信道接入类型为类型2LBT，第五信道接入类型为类型3 LBT，且类型2LBT的耗时大于类型3 LBT，则第一目标信道接入类型为类型2 LBT。
在实际应用中，当第一配置信息指示的第一非回退DCI上的至少一个第二信道接入类型和第二配置信息指示的第二非回退DCI上的至少一个第二信道接入类型相同的情况下，终端设备通过第一非回退DCI和第二非回退DCI中任一上的至少一个第二信道接入类型确定第一目标信道接入类型。
在一些实施例中，在上述情况一至情况三中任一情况下，基于至少一个第二信道接入类型确定的第三信道接入类型的情况包括以下至少之一：
信道接入类型情况一、在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述第三信道接入类型为类型1 LBT；
信道接入类型情况二、在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述第三信道接入类型为类型2 LBT；
信道接入类型情况三、在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型3LBT；
信道接入类型情况四、在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型2LBT。
本申请实施例中，在至少一个第二信道接入类型仅包括类型1 LBT的情况下，第一目标信道接入类型仍然为类型1 LBT，此时，终端设备满足信道接入类型切换条件，仍需执行类型1 LBT，即不进行信道接入类型的切换。在至少一个第二信道接入类型除了类型1 LBT之外，还包括类型2LBT和/或类型3LBT的情况下，第一目标信道接入类型为类型2 LBT或类型3LBT，此时，终端设备满足信道接入类型切换条件，则信道接入类型从类型1LBT切换为类型2LBT或类型3LBT。其中，在至少一个第二信道接入类型除了类型1 LBT之外，还包括类型2LBT的情况下，第一目标信道接入类型为类型2 LBT，此时，终端设备满足信道接入类型切换条件，则信道接入类型从类型1LBT切换为类型2LBT；在至少一个第二信道接入类型除了类型1 LBT之外，还包括类型3LBT的情况下，第一目标信道接入类型为类型3 LBT，此时，终端设备满足信道接入类型切换条件，则信道接入类型从类型1LBT切换为类型3LBT；在至少一个第二信道接入类型除了类型1 LBT之外，还包括类型2 LBT和类型3LBT的情况下，第一目标信道接入类型为类型2LBT和类型3LBT中耗时较长的类型2 LBT，此时，终端设备满足信道接入类型切换条件，则信道接入类型从类型1LBT切换为类型2 LBT。
在一些实施例中，第一信息还用于指示所述终端设备的COT共享场景。
此时，第一信息指示终端设备满足信道接入类型切换条件时的第一目标信道接入类型，还用于指示COT共享场景。
这里，COT共享场景可以理解为终端设备在进行COT共享时，基于第二目标信道接入类型或第三目标信道接入类型进行信道接入，即终端设备共享网络设备发起的COT进行PUSCH传输之前，基于网络设备指示的第二目标信道接入类型进行信道接入，或终端设备共享网络设备发起的COT进行PUCCH传输之前，基于网络设备指示的第三目标信道接入类型进行信道接入。
在一示例中，如图6所示，终端设备共享COT601进行PUSCH传输，网络设备在COT601上的DCI0_1向终端设备指示的第二目标信道接入类型为类型2LBT，终端设备在COT601进行PUSCH传输之前，执行类型2LBT进行信道接入，并在信道接入成功后，在COT601进行PUSCH传输。
在一示例中，如图7所示，终端设备共享COT701进行PUCCH传输，网络设备在COT701上的DCI1_1向终端设备指示的第三信道接入类型为类型3LBT，终端设备在COT701进行PUCCH传输之前，执行类型3LBT进行信道接入，并在信道接入成功后，在COT701进行PUCCH传输。其中，PUCCH传输携带HARQ-ACK。
这里，第一配置信息用于确定PUSCH传输的COT共享场景。可选地，第一配置信息指示的第 一非回退DCI中的至少一个第二信道接入类型用于确定PUSCH传输的COT共享场景。
第二配置信息用于确定PUCCH传输的COT共享场景。可选地，第二配置信息指示的第二非回退DCI中的至少一个第二信道接入类型用于确定PUCCH传输的COT共享场景。
本申请实施例中，COT共享场景包括：
COT共享场景一、终端设备不支持COT共享；
COT共享场景二、COT共享时终端设备需要执行Type1 LBT；
COT共享场景三、COT共享时终端设备执行Type2 LBT；
COT共享场景四、COT共享时终端设备执行Type3 LBT；
COT共享场景五、COT共享时终端设备执行Type2 LBT或Type3 LBT，且终端设备执行Type2 LBT或Type3 LBT基于网络设备结束传输与终端设备开始传输之间的间隔与设定间隔之间的大小。
本申请实施例中，第一信息能够确定第一目标信道接入类型的同时，还能够确定COT共享场景，从而实现第一目标信道接入类型和COT共享场景的关联。
本申请实施例中，可基于至少第一信息指示的第一非回退DCI或第二非回退DCI上的至少一个第二信道接入类型确定COT共享场景。
其中，第一非回退DCI上的至少一个第二信道接入类型确定的COT共享场景针对的是共享COT时的PUSCH传输，第二非回退DCI上的至少一个第二信道接入类型确定的COT共享场景针对的是共享COT时携带HARQ-ACK的PUCCH传输。
可选地，基于至少一个第二信道接入类型确定的COT共享场景包括以下之一：
COT共享情况一、在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述COT共享场景为所述终端设备不支持COT共享或者，所述终端设备在COT共享时执行类型1 LBT；
COT共享情况二、在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2 LBT；
COT共享情况三、在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型3 LBT；
COT共享情况四、在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2LBT或者类型3 LBT。
在COT共享情况一中，至少一个第二信道接入类型为类型1 LBT，表征终端设备不支持COT共享，或者COT共享时终端设备需要执行Type1 LBT，此时，终端设备即使满足信道接入类型切换条件，仍需执行Type1 LBT，即不进行信道接入类型的切换。
在COT共享情况二中，至少一个第二信道接入类型为类型1 LBT和类型2 LBT，表征COT共享时终端设备至少需要执行类型2 LBT，此时UE若满足信道接入类型切换条件，则可以从类型1 LBT切换为类型2 LBT。
在COT共享情况三中，至少一个第二信道接入类型为类型1 LBT和类型3LBT，表征COT共享时终端设备始终执行类型3 LBT，即对应COT共享方案1，此时，终端设备若满足信道接入类型切换条件，则可以从类型1 LBT切换为类型3 LBT。
在COT共享情况四中，至少一个第二信道接入类型为类型1 LBT、类型2 LBT和类型3LBT，表征COT共享时终端设备可能执行类型2 LBT或类型3 LBT，即对应COT共享方案2。此时，终端设备若满足信道接入类型切换条件，则可以从类型1 LBT切换为类型2 LBT。
在一些实施例中，所述第一非回退DCI中的第二信道接入类型的数量用于确定所述第一非回退DCI上的第二信息的大小，所述第二信息用于指示第二目标信道接入类型，所述第二目标信道接入类型为所述终端设备在COT共享时用于PUSCH传输的信道接入类型；或者，
所述第二非回退DCI中的第二信道接入类型的数量用于确定所述第二非回退DCI上的第三信息的大小，所述第三信息用于指示第三目标信道接入类型，所述第三目标信道接入类型为所述终端设备在COT共享时用于PUCCH传输的信道接入类型。
第二信息为第一非回退DCI中指示第二目标信道接入类型的信息，第二目标信道接入类型用于共享COT时的PUSCH传输。可选地，第二信息为DCI格式0_1中的ChannelAccess-CPext-CAPC。
在第一非回退DCI中的第二信息的大小基于第一非回退DCI中第二信道接入类型的数量确定。
可选地，第一非回退DCI中第二信息的大小为log 2I 1，其中，I 1为第一非回退DCI中第二信道接入类型的数量。
在一示例中，第一非回退DCI中的第二信道接入类型包括：类型1LBT和类型2LBT，I 1为2， 则第一非回退DCI中第二信息的大小为1比特，当第二信息的取值为0，则终端设备在共享的COT进行PUSCH传输之前，执行类型1LBT进行信道接入，当第二信息的取值为1，则终端设备在共享的COT进行PUSCH传输之前，执行类型2 LBT进行信道接入。
在又一示例中，第一非回退DCI中的第二信道接入类型包括：类型1LBT、类型2LBT和类型3LBT，I 1为3，则第一非回退DCI中第二信息的大小为2比特，当第二信息的取值为00，则终端设备在共享的COT进行PUSCH传输之前，执行类型1LBT进行信道接入，当第二信息的取值为01，则终端设备在共享的COT进行PUSCH传输之前，执行类型2 LBT进行信道接入，当第二信息的取值10，则终端设备在共享的COT进行PUSCH传输之前，执行类型3 LBT进行信道接入。
第三信息为第二非回退DCI中指示第三目标信道接入类型的信息，第三目标信道接入类型用于共享COT时的PUCCH传输。可选地，第三信息为DCI格式1_1中的ChannelAccess-CPext-CAPC。
在第二非回退DCI中的第三信息的大小基于第二非回退DCI中第二信道接入类型的数量确定。
可选地，第二非回退DCI中第三信息的大小为log 2I 2，其中，I 2为第二非回退DCI中第二信道接入类型的数量。
在一示例中，第二非回退DCI中的第二信道接入类型包括：类型1LBT和类型2LBT，I 2为2，则第二非回退DCI中第三信息的大小为1比特，当第三信息的取值为1，则终端设备在共享的COT进行携带HARQ-ACK的PUCCH传输之前，执行类型1LBT进行信道接入，当第三信息的取值为0，则终端设备在共享的COT进行携带HARQ-ACK的PUCCH传输之前，执行类型2 LBT进行信道接入。
在又一示例中，第一非回退DCI中的第二信道接入类型包括：类型1LBT、类型2LBT和类型3LBT，I 1为3，则第一非回退DCI中第三信息的大小为2比特，当第三信息的取值为00，则终端设备在共享的COT进行携带HARQ-ACK的PUCCH传输之前，执行类型1LBT进行信道接入，当第三信息的取值为01，则终端设备在共享的COT进行携带HARQ-ACK的PUCCH传输之前，执行类型2 LBT进行信道接入，当第三信息的取值10，则终端设备在共享的COT进行携带HARQ-ACK的PUCCH传输之前，执行类型3 LBT进行信道接入。
在一些实施例中，终端设备还实施以下步骤：
所述终端设备向所述网络设备发送第一能力指示信息，所述第一能力指示信息用于指示所述终端设备是否支持类型2 LBT。
此时，网络设备实施以下步骤：
所述网络设备接收所述终端设备发送的第一能力指示信息，所述第一能力指示信息用于指示所述终端设备是否支持类型2 LBT。
这里，终端设备通过第一能力指示信息向网络设备上报自身是否支持类型2 LBT。
第一能力指示信息指示所述终端设备是否支持类型2 LBT的方式包括以下指示方式之一
指示方式A、基于第一能力指示信息的发送指示终端设备不支持类型2LBT；
指示方式B、第一能力指示信息基于不同的取值指示终端设备支持或不支持类型2LBT。
在指示方式A中，终端设备向网络设备发送第一能力指示信息，则指示终端设备不支持类型2LBT。此时，当终端设备未向网络设备发送第一能力指示信息，则指示终端设备支持类型2 LBT。
指示方式B中，取值为第一值的第一能力指示信息指示终端设备支持类型2LBT，取值为第二值的第一能力指示信息指示终端设备不支持类型2LBT。
以第一能力指示信息指示所述终端设备是否支持类型2 LBT的方式为指示方式B为例，终端设备支持类型2LBT，则向网络设备发送取值为第一值的第一能力指示信息，网络设备基于取值为第一值的第一能力指示信息确定终端设备支持类型2LBT；终端设备不支持类型2LBT，则向网络设备发送取值为第二值的第一能力指示信息，网络设备基于取值为第二值的第一能力指示信息确定终端设备不支持类型2LBT。
网络设备接收到第一能力指示信息后，基于接收的第一能力指示信息为终端设备配置第一信息。
可选地，在所述第一能力指示信息用于指示所述终端设备支持类型2 LBT的情况下，所述至少一个第一信道接入类型可包括类型2 LBT。
在第一能力指示信息指示终端设备支持类型2LBT的情况下，网络设备确定终端设备支持类型2LBT，配置的第一信息指示的至少一个第一信道接入类型中可包括类型2 LBT也可不包括类型2LBT。
可选地，在所述第一能力指示信息用于指示所述终端设备不支持类型2 LBT的情况下，所述至 少一个第一信道接入类型不包括类型2 LBT。
在第一能力指示信息指示终端设备不支持类型2LBT的情况下，网络设备配置的第一信息指示的至少一个第一信道接入类型中不包括类型2 LBT。
本申请实施例提供的无线通信方法，应用于包括终端设备和网络设备的无线通信系统，如图8所示，包括：
S801、网络设备向终端设备发送第一信息。
所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
本申请实施例中，第一信息确定第一目标信道接入类型的方式可包括：
指示方式一、隐式指示；
指示方式二、显式指示。
在隐式方式中，第一信息指示非回退DCI中的至少一个第一信道接入类型，此时，基于指示非回退DCI中的至少一个第一信道接入类型的第一信息隐式的指示第一目标信道接入类型。
基于第一信息隐式指示第一目标信道接入类型的描述可参见图2和图5所示的无线通信方法的描述，这里不再赘述。
在显式指示方式中，第一信息显式指示类型2LBT或类型3LBT，这里，第一信息的不同取值指示不同的信道接入类型。终端设备在满足信道接入类型切换条件时，从类型1LBT切换至第一信息指示的第一目标信道接入类型。
在一示例中，第一信息的取值为第三值，则第一信息指示类型2 LBT，第一信息的取值为第四值，则第一信息指示类型3LBT。
本申请实施例中，网络设备可基于COT共享场景配置第一信息。
可选地，当终端设备的COT共享场景为COT共享方案1，则第一信息指示类型3 LBT；当终端设备的COT共享场景为COT共享方案2，则第一信息指示类型2 LBT。
在一些实施例中，在指示方式二中，终端设备向网络设备发送第一能力指示信息，此时，网络设备接收终端设备发送的第一能力指示信息。
这里，指示方式二中的第一能力指示信息同指示方式一中的第一能力指示信息，关于第一能力指示信息的描述可参见指示方式一中关于第一能力指示信息的描述，这里不再赘述。
下面，对本申请实施例提供的无线通信方法进行进一步描述。
本申请实施例提供了高频非授权频段下UE信道接入类型的切换方案。
NRU系统支持UE信道接入类型的切换，具体的：如果UE被DCI1调度了上行传输或被配置CG-PUSCH传输，且上行传输前需要执行Type1 LBT，但随后UE通过DCI2(对应DCI 2_0)发现之前被调度或被配置的上行传输发生在基站发起的COT内，则UE可以以COT共享的方式从Type1信道接入切换为Type2A信道接入。
在一示例中，如图9所示，基站在前一个COT即COT901上的DCI1调度了不在该COT内的PUSCH，因此，需要在DCI1指示UE执行Type1 LBT。随后基站重新获得了新的COT即COT902，且UE通过COT902上的DCI 2发现之前调度的PUSCH发生在COT902对应的时频域资源内，则在COT902，UE可以以COT共享的方式从Type1 LBT切换为Type2A LBT。
而高频中支持两种COT共享方案：
COT共享方案1，UE共享基站发起的COT时，始终执行Type3 LBT；
COT共享方案2、UE共享基站发起的COT时，执行Type2 LBT/Type3 LBT取决于传输空隙是否大于门限值，其中，当传输空隙不大于门限值，则执行Type3 LBT，否则，执行Type2 LBT。
可见，高频中对于不同的COT共享方案，UE切换到的第一目标信道接入类型也是不同的。即，对于COT共享方案1，当UE满足信道接入类型切换条件时，UE可以从Type1 LBT切换为Type3 LBT；对于共享方案2，当UE满足信道接入类型切换条件时，UE可以从Type1 LBT切换为Type2 LBT。
因此，UE可以通过确定当前所处的COT共享方案，从而确定切换到的第一目标信道接入类型。其中，UE确定第一目标信道接入类型的方式包括：
方式一(对应指示方式一)、隐式确定第一目标信道接入类型；
方式二(对应指示方式二)、显示指示第一目标信道接入类型。
本申请实施例提供的无线通信方法可以实施为但不限于以下实施例。
实施例一、
在实施例一中，确定第一目标信道接入类型的方式为方式一、隐式确定第一目标信道接入类型。
对于non-fallback DCI：DCI 0_1和1_1，基站会根据当前LBT应用场景从non-fallback DCI允许的所有信道接入类型中通过高层参数ul-AccessConfigListDCI-0-1配置实际使用的信道接入类型。例如：表1中DCI 0_1允许的信道接入类型包括Type1/Type2/Type3 LBT，且基站通过高层参数ul-AccessConfigListDCI-0-1配置Type1和Type3 LBT，即配置的信道接入类型索引数I＝2。则此时DCI 0_1中指示信道接入类型的比特位宽为
Figure PCTCN2022072419-appb-000001
比特，且比特域为0对应Type1 LBT，比特域为1对应Type3 LBT。
因此，UE可以根据non-fallback DCI中高层参数配置的信道接入类型隐式确定当前COT共享场景，从而确定信道接入类型切换时的第一目标信道接入类型。其中，
●如果高层参数配置non-fallback DCI中的信道接入类型为Type1 LBT，说明当前场景不支持COT共享，或者COT共享时UE需要执行Type1 LBT。此时UE即使满足信道接入类型切换条件，仍需执行Type1 LBT。
●如果高层参数配置non-fallback DCI中的信道接入类型为Type1 LBT和Type2 LBT，说明COT共享时UE至少需要执行Type2 LBT。此时UE若满足信道接入类型切换条件，则可以从Typ1 LBT切换为Type 2 LBT。
●如果高层参数配置non-fallback DCI中的信道接入类型为Type1 LBT和Type3 LBT，说明COT共享时UE始终执行Type3 LBT，即对应COT共享方案1。此时UE若满足信道接入类型切换条件，则可以从Type1 LBT切换为Type3 LBT。
●如果高层参数配置non-fallback DCI中的信道接入类型为Type1 LBT、Type2 LBT和Type3 LBT，说明COT共享时，UE可能执行Type2 LBT或Type3 LBT，即对应COT共享方案2。
此时UE若满足信道接入类型切换条件，则可以从Type1 LBT切换为Type2 LBT。
综合上述，高层参数配置non-fallback DCI中信道接入类型的情况，在配置Type 1 LBT的条件下，如果额外配置了Type2 LBT，则UE满足信道接入类型切换条件时，可以从Type 1 LBT切换为Type2 LBT；否则，如果额外配置了Type3 LBT，则UE满足信道接入类型切换条件时，可以从Type1 LBT切换为Type3 LBT。
此外，上述隐式确定第一目标信道接入类型的方案可以基于non-fallback DCI 0_1，也可以基于non-fallback DCI 1_1，也可以基于non-fallback DCI 0_1和1_1联合确定。
对于联合确定的方案，如果基于DCI 0_1和DCI 1_1确定的信道接入类型不一致，则将所需时间更长的LBT确定为第一目标信道接入类型。例如，基于高层参数配置的DCI 0_1和DCI 1_1中的信道接入类型，分别确定切换到的第一目标信道接入类型为Type2 LBT和Type3 LBT，则UE满足信道接入类型切换条件时，可以从Type1 LBT切换为Type2 LBT。
另外，对于隐式确定第一目标信道接入类型的方案，基站可以根据UE能力为UE配置non-fallback DCI中的信道接入类型，从而保证基站和UE对于切换后的第一目标信道接入类型有着共同的理解。例如，考虑到高频中Type2 LBT为UE能力，如果UE不支持Type2 LBT，则基站不会在non-fallback DCI中为UE配置Type2 LBT；如果UE支持Type2 LBT，则基站将进一步基于当前COT共享场景决定是否为UE配置Type2 LBT。无论UE是否支持Type2 LBT，隐式确定的方案都能保证基站和UE对于切换后的第一目标信道接入类型有着共同的理解。
实施例二
在实施例二中，确定第一目标信道接入类型的方式为方式二、显式确定第一目标信道接入类型。
基站也可以显式为UE指示切换后的信道接入类型，即可以通过系统消息(进一步可以为SIB1)指示或者RRC参数配置(进一步可以为小区级RRC信令)指示UE切换后的第一目标信道接入类型为Type2/Type3 LBT。
此时基站可以根据当前COT共享方案为UE指示/配置切换后的信道接入类型。例如，如果当前应用COT共享方案1，则基站可以为UE指示/配置切换后的信道接入类型为Type3 LBT；如果当前应用COT共享方案2，则基站可以为UE指示/配置切换后的信道接入类型为Type2 LBT。
同样，考虑到高频中Type2 LBT为UE能力，则此时需要规定：如果UE不支持Type2 LBT，那么UE即使满足信道接入类型的切换条件，也不进行信道接入类型的切换，即仍维持Type1 LBT进行信道接入。从而保证基站和UE对于切换后的信道接入类型有着共同的理解。
以上结合附图详细描述了本申请的优选实施方式，但是，本申请并不限于上述实施方式中的具 体细节，在本申请的技术构思范围内，可以对本申请的技术方案进行多种简单变型，这些简单变型均属于本申请的保护范围。例如，在上述具体实施方式中所描述的各个具体技术特征，在不矛盾的情况下，可以通过任何合适的方式进行组合，为了避免不必要的重复，本申请对各种可能的组合方式不再另行说明。又例如，本申请的各种不同的实施方式之间也可以进行任意组合，只要其不违背本申请的思想，其同样应当视为本申请所公开的内容。又例如，在不冲突的前提下，本申请描述的各个实施例和/或各个实施例中的技术特征可以和现有技术任意的相互组合，组合之后得到的技术方案也应落入本申请的保护范围。
还应理解，在本申请的各种方法实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。此外，在本申请实施例中，术语“下行”、“上行”和“侧行”用于表示信号或数据的传输方向，其中，“下行”用于表示信号或数据的传输方向为从站点发送至小区的用户设备的第一方向，“上行”用于表示信号或数据的传输方向为从小区的用户设备发送至站点的第二方向，“侧行”用于表示信号或数据的传输方向为从用户设备1发送至用户设备2的第三方向。例如，“下行信号”表示该信号的传输方向为第一方向。另外，本申请实施例中，术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系。具体地，A和/或B可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图10是本申请实施例提供的无线通信装置的结构组成示意图一，应用于终端设备，如图10所示，无线通信装置1000包括：
第一接收模块1001，配置为接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
在一些实施例中，所述第一信息包括以下至少之一：
第一配置信息，所述第一配置信息指示第一非回退DCI中的至少一个第二信道接入类型，所述第一非回退DCI用于调度物理上行共享信道PUSCH的非回退上行授权；
第二配置信息，所述第二配置信息指示第二非回退DCI中的至少一个第二信道接入类型，所述第二非回退DCI用于调度物理下行共享信道PDSCH的非回退下行授权。
在一些实施例中，在所述第一信息包括第一配置信息的情况下，所述第一目标信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
在一些实施例中，在所述第一配置信息包括第二配置信息的情况下，所述第一目标信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三接入类型。
在一些实施例中，在所述第一信息包括所述第一配置信息和所述第二配置信息的情况下，所述第一目标信道接入类型从第四信道接入类型和第五信道接入类型中选择，所述第四信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型，所述第五信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
在一些实施例中，在所述第四信道接入类型和所述第五信道接入类型相同的情况下，所述第一目标信道接入类型为所述第四信道接入类型；或者，
在所述第四信道接入类型和所述第五信道接入类型不同的情况下，所述第一目标信道接入类型为所述第四信道接入类型和所述第五信道接入类型中耗时较长的。
在一些实施例中，在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述第三信道接入类型为类型1 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述第三信道接入类型为类型2 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型3LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型2LBT。
在一些实施例中，所述第一信息还用于指示所述终端设备的COT共享场景。
在一些实施例中，在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述COT共 享场景为所述终端设备不支持COT共享或者，所述终端设备在COT共享时执行类型1 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时至少执行类型2 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型3 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2LBT或者类型3 LBT。
在一些实施例中，装置1000还包括：
第一发送模块，配置为向所述网络设备发送第一能力指示信息，所述第一能力指示信息用于指示所述终端设备是否支持类型2 LBT。
在一些实施例中，在所述第一能力指示信息用于指示所述终端设备不支持类型2 LBT的情况下，所述至少一个第一信道接入类型不包括类型2 LBT。
图11是本申请实施例提供的无线通信装置的结构组成示意图一，应用于网络设备，如图11所示，无线通信装置1100包括：
第二发送模块1101，配置为向终端设备发送第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
在一些实施例中，所述第一信息包括以下至少之一：
第一配置信息，所述第一配置信息指示第一非回退DCI中的至少一个第二信道接入类型，所述第一非回退DCI用于调度物理上行共享信道PUSCH的非回退上行授权；
第二配置信息，所述第二配置信息指示第二非回退DCI中的至少一个第二信道接入类型，所述第二非回退DCI用于调度物理下行共享信道PDSCH的非回退下行授权。
在一些实施例中，在所述第一信息包括第一配置信息的情况下，所述第一目标信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
在一些实施例中，在所述第一配置信息包括第二配置信息的情况下，所述第一目标信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三接入类型。
在一些实施例中，在所述第一信息包括所述第一配置信息和所述第二配置信息的情况下，所述第一目标信道接入类型从第四信道接入类型和第五信道接入类型中选择，所述第四信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型，所述第五信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
在一些实施例中，在所述第四信道接入类型和所述第五信道接入类型相同的情况下，所述第一目标信道接入类型为所述第四信道接入类型；或者，
在所述第四信道接入类型和所述第五信道接入类型不同的情况下，所述第一目标信道接入类型为所述第四信道接入类型和所述第五信道接入类型中耗时较长的。
在一些实施例中，在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述第三信道接入类型为类型1 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述第三信道接入类型为类型2 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型3LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型2LBT。
在一些实施例中，所述第一信息还用于指示所述终端设备的COT共享场景。
在一些实施例中，在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述COT共享场景为所述终端设备不支持COT共享或者，所述终端设备在COT共享时执行类型1 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时至少执行类型2 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型3 LBT。
在一些实施例中，在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2LBT或者类型3 LBT。
在一些实施例中，装置1100还包括：
第二接收模块，配置为接收终端设备发送的第一能力指示信息，所述第一能力指示信息用于指示所述终端设备是否支持类型2 LBT。
在一些实施例中，在所述第一能力指示信息用于指示所述终端设备不支持类型2 LBT的情况下，所述至少一个第一信道接入类型不包括类型2 LBT。
本领域技术人员应当理解，本申请实施例的上述无线通信装置的相关描述可以参照本申请实施例的无线通信方法的相关描述进行理解。
图12是本申请实施例提供的一种通信设备1200示意性结构图。该通信设备可以终端设备，也可以是网络设备。图12所示的通信设备1200包括处理器1210，处理器1210可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图12所示，通信设备1200还可以包括存储器1220。其中，处理器1210可以从存储器1220中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1220可以是独立于处理器1210的一个单独的器件，也可以集成在处理器1210中。
可选地，如图12所示，通信设备1200还可以包括收发器1230，处理器1210可以控制该收发器1230与其他设备进行通信，具体地，可以向其他设备发送信息或数据，或接收其他设备发送的信息或数据。
其中，收发器1230可以包括发射机和接收机。收发器1230还可以进一步包括天线，天线的数量可以为一个或多个。
可选地，该通信设备1200具体可为本申请实施例的网络设备，并且该通信设备1200可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该通信设备1200具体可为本申请实施例的移动终端/终端设备，并且该通信设备1200可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
图13是本申请实施例的芯片的示意性结构图。图13所示的芯片1300包括处理器1310，处理器1310可以从存储器中调用并运行计算机程序，以实现本申请实施例中的方法。
可选地，如图13所示，芯片1300还可以包括存储器1320。其中，处理器1310可以从存储器1320中调用并运行计算机程序，以实现本申请实施例中的方法。
其中，存储器1320可以是独立于处理器1310的一个单独的器件，也可以集成在处理器1310中。
可选地，该芯片1300还可以包括输入接口1330。其中，处理器1310可以控制该输入接口1330与其他设备或芯片进行通信，具体地，可以获取其他设备或芯片发送的信息或数据。
可选地，该芯片1300还可以包括输出接口1340。其中，处理器1310可以控制该输出接口840与其他设备或芯片进行通信，具体地，可以向其他设备或芯片输出信息或数据。
可选地，该芯片可应用于本申请实施例中的网络设备，并且该芯片可以实现本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该芯片可应用于本申请实施例中的移动终端/终端设备，并且该芯片可以实现本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
图14是本申请实施例提供的一种通信系统1400的示意性框图。如图14所示，该通信系统1400包括终端设备1410和网络设备1420。
其中，该终端设备1410可以用于实现上述方法中由终端设备实现的相应的功能，以及该网络设备1420可以用于实现上述方法中由网络设备实现的相应的功能为了简洁，在此不再赘述。
应理解，本申请实施例的处理器可能是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array， FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
应理解，上述存储器为示例性但不是限制性说明，例如，本申请实施例中的存储器还可以是静态随机存取存储器(static RAM，SRAM)、动态随机存取存储器(dynamic RAM，DRAM)、同步动态随机存取存储器(synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(synch link DRAM，SLDRAM)以及直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)等等。也就是说，本申请实施例中的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提供了一种计算机可读存储介质，用于存储计算机程序。
可选的，该计算机可读存储介质可应用于本申请实施例中的网络设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机可读存储介质可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序产品，包括计算机程序指令。
可选的，该计算机程序产品可应用于本申请实施例中的网络设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序产品可应用于本申请实施例中的移动终端/终端设备，并且该计算机程序指令使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本申请实施例还提供了一种计算机程序。
可选的，该计算机程序可应用于本申请实施例中的网络设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由网络设备实现的相应流程，为了简洁，在此不再赘述。
可选地，该计算机程序可应用于本申请实施例中的移动终端/终端设备，当该计算机程序在计算机上运行时，使得计算机执行本申请实施例的各个方法中由移动终端/终端设备实现的相应流程，为了简洁，在此不再赘述。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种 逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，)ROM、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。

Claims (46)

  1. 一种无线通信方法，所述方法包括：
    终端设备接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
  2. 根据权利要求1所述的方法，其中，所述第一信息包括以下至少之一：
    第一配置信息，所述第一配置信息指示第一非回退DCI中的至少一个第二信道接入类型，所述第一非回退DCI用于调度物理上行共享信道PUSCH的非回退上行授权；
    第二配置信息，所述第二配置信息指示第二非回退DCI中的至少一个第二信道接入类型，所述第二非回退DCI用于调度物理下行共享信道PDSCH的非回退下行授权。
  3. 根据权利要求2所述的方法，其中，在所述第一信息包括第一配置信息的情况下，所述第一目标信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
  4. 根据权利要求2所述的方法，其中，在所述第一配置信息包括第二配置信息的情况下，所述第一目标信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三接入类型。
  5. 根据权利要求2所述的方法，其中，在所述第一信息包括所述第一配置信息和所述第二配置信息的情况下，所述第一目标信道接入类型从第四信道接入类型和第五信道接入类型中选择，所述第四信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型，所述第五信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
  6. 根据权利要求5所述的方法，其中，
    在所述第四信道接入类型和所述第五信道接入类型相同的情况下，所述第一目标信道接入类型为所述第四信道接入类型；或者，
    在所述第四信道接入类型和所述第五信道接入类型不同的情况下，所述第一目标信道接入类型为所述第四信道接入类型和所述第五信道接入类型中耗时较长的。
  7. 根据权利要求3至6中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述第三信道接入类型为类型1LBT。
  8. 根据权利要求3至6中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述第三信道接入类型为类型2 LBT。
  9. 根据权利要求3至6中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型3LBT。
  10. 根据权利要求3至6中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型2LBT。
  11. 根据权利要求2至10中任一项所述的方法，其中，所述第一信息还用于指示所述终端设备的COT共享场景。
  12. 根据权利要求11所述的方法，其中，在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述COT共享场景为所述终端设备不支持COT共享或者，所述终端设备在COT共享时执行类型1 LBT。
  13. 根据权利要求11所述的方法，其中，在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时至少执行类型2 LBT。
  14. 根据权利要求11所述的方法，其中，在所述至少一个第二信道接入类型包括类型1 LBT 和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型3 LBT。
  15. 根据权利要求11所述的方法，其中，在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2LBT或者类型3 LBT。
  16. 根据权利要求1至15中任一项所述的方法，其中，所述方法还包括：
    所述终端设备向所述网络设备发送第一能力指示信息，所述第一能力指示信息用于指示所述终端设备是否支持类型2 LBT。
  17. 根据权利要求16所述的方法，其中，在所述第一能力指示信息用于指示所述终端设备不支持类型2 LBT的情况下，所述至少一个第一信道接入类型不包括类型2 LBT。
  18. 一种无线通信方法，所述方法包括：
    网络设备向终端设备发送第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
  19. 根据权利要求18所述的方法，其中，所述第一信息包括以下至少之一：
    第一配置信息，所述第一配置信息指示第一非回退DCI中的至少一个第二信道接入类型，所述第一非回退DCI用于调度物理上行共享信道PUSCH的非回退上行授权；
    第二配置信息，所述第二配置信息指示第二非回退DCI中的至少一个第二信道接入类型，所述第二非回退DCI用于调度物理下行共享信道PDSCH的非回退下行授权。
  20. 根据权利要求19所述的方法，其中，在所述第一信息包括第一配置信息的情况下，所述第一目标信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
  21. 根据权利要求19所述的方法，其中，在所述第一配置信息包括第二配置信息的情况下，所述第一目标信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三接入类型。
  22. 根据权利要求19所述的方法，其中，在所述第一信息包括所述第一配置信息和所述第二配置信息的情况下，所述第一目标信道接入类型从第四信道接入类型和第五信道接入类型中选择，所述第四信道接入类型为基于所述第一非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型，所述第五信道接入类型为基于所述第二非回退DCI中的至少一个第二信道接入类型确定的第三信道接入类型。
  23. 根据权利要求22所述的方法，其中，
    在所述第四信道接入类型和所述第五信道接入类型相同的情况下，所述第一目标信道接入类型为所述第四信道接入类型；或者，
    在所述第四信道接入类型和所述第五信道接入类型不同的情况下，所述第一目标信道接入类型为所述第四信道接入类型和所述第五信道接入类型中耗时较长的。
  24. 根据权利要求20至23中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型为类型1 LBT的情况下，所述第三信道接入类型为类型1LBT。
  25. 根据权利要求20至23中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述第三信道接入类型为类型2 LBT。
  26. 根据权利要求20至23中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型3LBT。
  27. 根据权利要求20至23中任一项所述的方法，其中，
    在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述第三信道接入类型为类型2LBT。
  28. 根据权利要求19至27中任一项所述的方法，其中，所述第一信息还用于指示所述终端设备的COT共享场景。
  29. 根据权利要求28所述的方法，其中，在所述至少一个第二信道接入类型为类型1 LBT 的情况下，所述COT共享场景为所述终端设备不支持COT共享或者，所述终端设备在COT共享时执行类型1 LBT。
  30. 根据权利要求28所述的方法，其中，在所述至少一个第二信道接入类型包括类型1 LBT和类型2 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2 LBT。
  31. 根据权利要求28所述的方法，其中，在所述至少一个第二信道接入类型包括类型1 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型3 LBT。
  32. 根据权利要求30所述的方法，其中，在所述至少一个第二信道接入类型包括类型1 LBT、类型2 LBT和类型3 LBT的情况下，所述COT共享场景为所述终端设备在COT共享时执行类型2LBT或者类型3 LBT。
  33. 根据权利要求18至32中任一项所述的方法，其中，所述方法还包括：
    所述网络设备接收所述终端设备发送的第一能力指示信息，所述第一能力指示信息用于指示所述终端设备是否支持类型2 LBT。
  34. 根据权利要求33所述的方法，其中，在所述第一能力指示信息用于指示所述终端设备不支持类型2 LBT的情况下，所述至少一个第一信道接入类型不包括类型2 LBT。
  35. 一种无线通信装置，包括：
    第一接收模块，配置为接收网络设备配置的第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
  36. 一种无线通信装置，包括：
    第二发送模块，配置为向终端设备发送第一信息，所述第一信息指示非回退下行控制信息DCI中的至少一个第一信道接入类型，所述第一信息用于确定第一目标信道接入类型，所述第一目标信道接入类型为所述终端设备被指示执行类型1先听后说LBT，且被调度或被配置的第一传输承载在第一资源上的情况下，从类型1LBT切换到的信道接入类型，所述第一资源为第一信道占用时间COT对应的资源，所述第一COT为网络设备发起的COT。
  37. 一种终端设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求1至17中任一项所述的方法。
  38. 一种网络设备，包括：处理器和存储器，该存储器用于存储计算机程序，所述处理器用于调用并运行所述存储器中存储的计算机程序，执行如权利要求18至34中任一项所述的方法。
  39. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求1至17中任一项所述的方法。
  40. 一种芯片，包括：处理器，用于从存储器中调用并运行计算机程序，使得安装有所述芯片的设备执行如权利要求18至34中任一项所述的方法。
  41. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求1至17中任一项所述的方法。
  42. 一种计算机可读存储介质，用于存储计算机程序，所述计算机程序使得计算机执行如权利要求18至34中任一项所述的方法。
  43. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求1至17中任一项所述的方法。
  44. 一种计算机程序产品，包括计算机程序指令，该计算机程序指令使得计算机执行如权利要求18至34中任一项所述的方法。
  45. 一种计算机程序，所述计算机程序使得计算机执行如权利要求1至17中任一项所述的方法。
  46. 一种计算机程序，所述计算机程序使得计算机执行如权利要求18至34中任一项所述的方法。
PCT/CN2022/072419 2022-01-17 2022-01-17 一种无线通信方法及装置、终端设备、网络设备 WO2023133902A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2022/072419 WO2023133902A1 (zh) 2022-01-17 2022-01-17 一种无线通信方法及装置、终端设备、网络设备
CN202280073861.5A CN118202766A (zh) 2022-01-17 2022-01-17 一种无线通信方法及装置、终端设备、网络设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2022/072419 WO2023133902A1 (zh) 2022-01-17 2022-01-17 一种无线通信方法及装置、终端设备、网络设备

Publications (1)

Publication Number Publication Date
WO2023133902A1 true WO2023133902A1 (zh) 2023-07-20

Family

ID=87279954

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/072419 WO2023133902A1 (zh) 2022-01-17 2022-01-17 一种无线通信方法及装置、终端设备、网络设备

Country Status (2)

Country Link
CN (1) CN118202766A (zh)
WO (1) WO2023133902A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110602785A (zh) * 2018-06-12 2019-12-20 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
CN111742601A (zh) * 2019-01-24 2020-10-02 联发科技股份有限公司 上行链路传输的信道接入过程
US20200413414A1 (en) * 2018-12-24 2020-12-31 Shanghai Langbo Communication Technology Company Limited Method and device in ue and base station used for wireless communication
CN112534943A (zh) * 2018-08-09 2021-03-19 Lg 电子株式会社 用于在无线通信系统中发送和接收无线信号的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110602785A (zh) * 2018-06-12 2019-12-20 上海朗帛通信技术有限公司 一种被用于无线通信的用户设备、基站中的方法和装置
CN112534943A (zh) * 2018-08-09 2021-03-19 Lg 电子株式会社 用于在无线通信系统中发送和接收无线信号的方法和装置
US20200413414A1 (en) * 2018-12-24 2020-12-31 Shanghai Langbo Communication Technology Company Limited Method and device in ue and base station used for wireless communication
CN111742601A (zh) * 2019-01-24 2020-10-02 联发科技股份有限公司 上行链路传输的信道接入过程

Also Published As

Publication number Publication date
CN118202766A (zh) 2024-06-14

Similar Documents

Publication Publication Date Title
WO2020147115A1 (zh) 用于非授权频谱的无线通信方法和设备
WO2020143057A1 (zh) 信道接入方案的确定方法及装置、终端设备、网络设备
EP3863357B1 (en) Data transmission method and terminal device
US11283552B2 (en) Feedback information transmission method and apparatus and communications device
WO2020140289A1 (zh) 资源分配的方法、终端设备和网络设备
WO2020087524A1 (zh) 非授权频段上ssb的传输方法和设备
WO2020062084A1 (zh) 无线通信方法和通信设备
WO2020029256A1 (zh) 一种数据传输方法、终端设备及网络设备
WO2020164154A1 (zh) 传输信号的方法及设备
WO2020073623A1 (zh) 一种资源配置方法及装置、通信设备
WO2020051919A1 (zh) 一种资源确定及配置方法、装置、终端、网络设备
WO2020037655A1 (zh) 一种反馈信息长度的确定方法及装置、通信设备
WO2020087424A1 (zh) 一种数据传输方法、终端设备及存储介质
WO2020034203A1 (zh) 传输信号的方法、终端设备和网络设备
TW202014015A (zh) 傳輸訊息的方法和終端設備
WO2020087545A1 (zh) 一种上行控制信息确定方法和通信设备
EP3958629A1 (en) Method for configuring transmission resource cancellation indication information, network apparatus, and terminal apparatus
WO2020061773A1 (zh) 一种反馈资源分配方法、终端设备及网络设备
US11800546B2 (en) Method and apparatus for determining number of uplink control information transmission resources, and program
WO2023133902A1 (zh) 一种无线通信方法及装置、终端设备、网络设备
WO2020107692A1 (zh) 一种无线通信方法和通信设备
WO2020093403A1 (zh) 一种随机接入方法及装置、终端、基站
WO2020107714A1 (zh) 一种无线通信方法和通信设备
WO2020056556A1 (zh) 用于非授权频谱的通信方法、终端设备和网络设备
WO2023130393A1 (zh) 一种无线通信方法及装置、终端设备、网络设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22919548

Country of ref document: EP

Kind code of ref document: A1