Communication method and device

Abstract

The embodiment of the invention provides a communication method and equipment, and the communication method comprises the steps that a first terminal receives first COT request information of a second terminal; the first terminal sends first response information to the second terminal, wherein the first response information comprises first confirmation information and / or second confirmation information; wherein the first confirmation information is used for indicating or confirming that the first terminal will initiate the first COT; the second confirmation information is used for indicating or confirming that the first terminal does not initiate the first COT. According to the embodiment of the invention, the power consumption in a channel access process can be reduced.

Description

Communication method and device Technical Field

[0001] The present invention relates to the field of communications, and more particularly, to a communication method and device. Background Art

[0002] In the prior art, when a terminal operates on a sidelink in an unlicensed frequency band, the terminal needs to perform different types of Listen before Talk (LBT) before sending sidelink data. Only when the LBT is successful can it successfully access the channel for sidelink transmission. When there is no channel occupancy time (COT), the terminal needs to perform the first type of LBT (Type 1 LBT). Only after success can it initiate a COT. Other terminals that meet the conditions can also share the resources in this COT and adopt the second type of LBT (Type 2 LBT). In the prior art, whether a terminal initiates a COT is determined by whether it has data to send and whether the Type 1 LBT is successful. It does not support scenarios where a terminal requests another terminal to initiate a COT for its own use.

[0003] SideLink Unlicensed (SL-U) technology can be deployed in commercial scenarios such as wearable smart devices, smart homes, and the Industrial Internet. Because terminal device cost and power consumption are crucial metrics for commercial deployment, the question of how to achieve energy conservation in SL-U Reduced Capability (RedCap) terminals is a topic requiring research.

[0004] When SL-U terminals operate in unlicensed frequency bands, they must first perform LBT before transmitting data. RedCap terminals must continuously perform long-duration channel sensing operations to access the channel, which results in high power consumption. Therefore, how to save energy during the channel access process is a research issue.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide a communication method and device that can reduce power consumption during channel access.

[0007] An embodiment of the present application provides a communication method, including:

[0008] The first terminal receives first channel occupancy time (COT) request information from the second terminal;

[0009] The first terminal sends a first response message to the second terminal, where the first response message includes a first confirmation message and / or a second confirmation message; wherein,

[0010] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0011] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0012] The present application also provides a communication method, including:

[0013] The second terminal sends a first COT request message to the first terminal;

[0014] The second terminal receives first response information from the first terminal, where the first response information includes first confirmation information and / or second confirmation information; wherein,

[0015] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0016] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0017] The embodiment of the present application further provides a first terminal, including:

[0018] A first receiving module, configured to receive first COT request information from a second terminal;

[0019] The first sending module is configured to send a first response message to the second terminal, where the first response message includes a first confirmation message and / or a second confirmation message; wherein,

[0020] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0021] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0022] The embodiment of the present application further provides a second terminal, including:

[0023] A second sending module, configured to send first COT request information to the first terminal;

[0024] The second receiving module is configured to receive first response information from the first terminal, where the first response information includes first confirmation information and / or second confirmation information; wherein,

[0025] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0026] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0027] The present application also provides a communication device including a processor, a memory, and a transceiver. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory and control the transceiver so that the device executes the above method.

[0028] The embodiment of the present application also provides a chip for implementing the above method.

[0029] Specifically, the chip includes: a processor, which is used to call and run a computer program from a memory, so that a device equipped with the chip executes the above method.

[0030] An embodiment of the present application further provides a computer-readable storage medium for storing a computer program, which enables a device to execute the above method when the computer program is executed by the device.

[0031] An embodiment of the present application also provides a computer program product, including computer program instructions, which enable a computer to execute the above method.

[0032] An embodiment of the present application also provides a computer program, which, when executed on a computer, enables the computer to execute the above method.

[0033] In an embodiment of the present application, after receiving the first COT request information from the second terminal, the first terminal may initiate a COT, which may be used by at least other terminals including the second terminal, thereby reducing the power consumption generated by other terminals during channel access. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] FIG1 is a schematic diagram of an application scenario of an embodiment of the present application.

[0035] FIG. 2A is a schematic diagram of network coverage inner row communication.

[0036] FIG2B is a schematic diagram of sideline communication with partial network coverage.

[0037] FIG2C is a schematic diagram of network coverage outer-side communication.

[0038] FIG. 2D is a schematic diagram of sideline communication with a central control node.

[0039] FIG3A is a schematic diagram of unicast transmission in NR-V2X.

[0040] FIG3B is a schematic diagram of multicast transmission in NR-V2X.

[0041] FIG3C is a schematic diagram of a broadcast transmission in NR-V2X.

[0042] FIG4 is a schematic diagram of a channel occupancy time obtained by a communication device after successful LBT on a channel of an unlicensed spectrum, and signal transmission using resources within the channel occupancy time.

[0043] FIG5 is a schematic flowchart of a communication method 500 according to an embodiment of the present application.

[0044] FIG6 is a schematic diagram of Example 1 of the present application.

[0045] 7A-7E are schematic diagrams of the second embodiment of the present application.

[0046] FIG8A is a schematic diagram 1 of the third embodiment of the present application.

[0047] FIG8B is a second schematic diagram of the third embodiment of the present application.

[0048] FIG9A is a first schematic diagram of the fourth embodiment of the present application.

[0049] FIG9B is a second schematic diagram of the fourth embodiment of the present application.

[0050] FIG10 is a schematic flowchart of a communication method 1000 according to an embodiment of the present application.

[0051] FIG11 is a schematic structural diagram of a first terminal 1100 according to an embodiment of the present application.

[0052] FIG12 is a schematic structural diagram of a first terminal 1200 according to an embodiment of the present application.

[0053] FIG13 is a schematic structural diagram of a second terminal 1300 according to an embodiment of the present application.

[0054] FIG14 is a schematic structural diagram of a second terminal 1400 according to an embodiment of the present application.

[0055] FIG15 is a schematic structural diagram of a communication device 1500 according to an embodiment of the present application.

[0056] FIG16 is a schematic structural diagram of a chip 1600 according to an embodiment of the present application. DETAILED DESCRIPTION

[0057] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

[0058] It should be noted that the terms "first," "second," and the like in the description and claims of the embodiments of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. The objects described by the terms "first" and "second" may be the same or different.

[0059] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, NR system evolution system, LTE on unlicensed spectrum (LTE-U) system, NR on unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity) system. Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

[0060] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.

[0061] In one embodiment, the communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.

[0062] In one embodiment, the communication system in the embodiment of the present application can be applied to an unlicensed spectrum, wherein the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, wherein the authorized spectrum can also be considered as an unshared spectrum.

[0063] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, wherein the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0064] The terminal device can be a station (STAION, ST) in a WLAN, a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a next-generation communication system such as an NR network, or a terminal device in a future evolved Public Land Mobile Network (PLMN) network, etc.

[0065] In an embodiment of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water surface (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).

[0066] In an embodiment of the present application, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0067] As an example and not a limitation, in the embodiment of the present application, the terminal device may also be a wearable device. Wearable devices may also be called wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0068] In an embodiment of the present application, the network device may be a device for communicating with a mobile device. The network device may be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (eNB or eNodeB) in LTE, or a relay station or access point, or a vehicle-mounted device, a wearable device, and a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or a network device in an NTN network, etc.

[0069] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. Alternatively, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station set up in a location such as land or water.

[0070] In an embodiment of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resources used by the cell (for example, frequency domain resources, or spectrum resources). The cell can be a cell corresponding to the network device (for example, a base station). The cell can belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

[0071] FIG1 exemplarily illustrates a communication system 100. The communication system includes a network device 110 and two terminal devices 120. In one embodiment, the communication system 100 may include multiple network devices 110, and each network device 110 may include a different number of terminal devices 120 within its coverage area, which is not limited in this embodiment of the present application.

[0072] In one embodiment, the communication system 100 may further include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which is not limited in this embodiment of the present application.

[0073] Among them, the network equipment may include access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks for communicating with the access network equipment. The access network equipment can be an evolutionary base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, micro base station (also called "small base station"), pico base station, access point (AP), transmission point (TP) or new generation base station (new generation Node B, gNodeB), etc. in a long-term evolution (LTE) system, a next-generation (mobile communication system) (next radio, NR) system or an authorized auxiliary access long-term evolution (LAA-LTE) system.

[0074] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system shown in Figure 1 as an example, the communication device may include a network device and a terminal device having a communication function. The network device and the terminal device may be specific devices in the embodiments of the present application and will not be described in detail here. The communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.

[0075] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" is simply a description of an association between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " generally indicates that the related objects are in an "or" relationship.

[0076] It should be understood that the "indication" mentioned in the embodiments of this application can be a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B.

[0077] In the description of the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and being indicated, configuration and being configured, etc.

[0078] To facilitate understanding of the technical solutions of the embodiments of the present application, the relevant technologies of the embodiments of the present application are described below. The following relevant technologies can be arbitrarily combined with the technical solutions of the embodiments of the present application as optional solutions, and they all fall within the protection scope of the embodiments of the present application.

[0079] 1. Sideline communication technology:

[0080] In sideline communication technology, according to the network coverage of the communicating terminals, it can be divided into sideline communication within network coverage, sideline communication with partial network coverage, sideline communication outside network coverage and sideline communication with a central control node, as shown in Figures 2A-2D respectively.

[0081] As shown in FIG2A , in sideline communication within network coverage, all terminals performing sideline communication are within the coverage of the same base station. Thus, the above terminals can perform sideline communication based on the same sideline configuration by receiving configuration signaling from the base station.

[0082] As shown in Figure 2B, in the case of partial network coverage for sidelink communication, some terminals performing sidelink communication are within the coverage of the base station. These terminals can receive configuration signaling from the base station and perform sidelink communication according to the base station's configuration. However, terminals outside the network coverage cannot receive configuration signaling from the base station. In this case, terminals outside the network coverage will determine the sidelink configuration based on pre-configuration information and information carried in the Physical Sidelink Broadcast Channel (PSBCH) sent by terminals within the network coverage, and perform sidelink communication.

[0083] As shown in FIG2C , for sideline communication outside the network coverage, all terminals performing sideline communication are located outside the network coverage, and all terminals determine the sideline configuration according to the pre-configured information to perform sideline communication.

[0084] As shown in Figure 2D, for side communication with a central control node, multiple terminals form a communication group. The communication group has a central control node, which can also become the cluster head terminal (Cluster Header, CH). The central control node has one of the following functions: responsible for establishing the communication group; joining and leaving the group members; coordinating resources, allocating side transmission resources to other terminals, receiving side feedback information from other terminals; coordinating resources with other communication groups, etc.

[0085] 2. Device to Device (D2D) / Vehicle to Everything (V2X)

[0086] Device-to-device communication is a sidelink (SL) transmission technology based on D2D. Unlike traditional cellular systems, where data is received or sent via base stations, this technology offers higher spectrum efficiency and lower transmission latency. The IoV system utilizes direct end-to-end communication and currently defines two transmission modes: Mode 1 and Mode 2.

[0087] Mode 1: The terminal's transmission resources are allocated by the base station, and the terminal transmits data on the sidelink based on the allocated resources. The base station can allocate resources for either single transmissions or semi-static transmissions. As shown in Figure 2A, the terminal is within network coverage, and the network allocates transmission resources for sidelink transmissions.

[0088] Mode 2: The terminal selects a resource from the resource pool for data transmission. For example, in Figure 2C, if the terminal is outside the cell coverage area, the terminal autonomously selects a transmission resource from the pre-configured resource pool for sideline transmission. Alternatively, as in Figure 2A, the terminal autonomously selects a transmission resource from the network-configured resource pool for sideline transmission.

[0089] NR-V2X

[0090] In NR-V2X, autonomous driving needs to be supported, which places higher requirements on data interaction between vehicles, such as higher throughput, lower latency, higher reliability, larger coverage, and more flexible resource allocation.

[0091] In LTE-V2X, broadcast transmission is supported, while in NR-V2X, unicast and multicast transmission are introduced. For unicast transmission, there is only one receiving terminal. Figure 3A is a schematic diagram of unicast transmission in NR-V2X. In Figure 3A, unicast transmission is performed between UE1 and UE2. For multicast transmission, the receiving terminals are all terminals in a communication group, or all terminals within a certain transmission distance. Figure 3B is a schematic diagram of multicast transmission in NR-V2X. As shown in Figure 3B, UE1, UE2, UE3, and UE4 constitute a communication group, in which UE1 sends data, and the other terminal devices in the group are all receiving terminals. For broadcast transmission, the receiving terminal is any terminal around the sending terminal. Figure 3C is a schematic diagram of broadcast transmission in NR-V2X. In Figure 3C, UE1 is the sending terminal, and the other terminals around it, UE2-UE6, are all receiving terminals.

[0092] 4. 5G Unlicensed (Unlicensed) Spectrum Communications NR-U

[0093] NR systems enable seamless cellular network coverage, high spectral efficiency, high peak rates, and high reliability. In Long Term Evolution (LTE) systems, unlicensed spectrum (or unlicensed spectrum) has been used as a supplementary frequency band to the licensed spectrum for cellular networks. Similarly, NR systems can also use unlicensed spectrum as part of 5G cellular network technology to provide services to users. The relevant standards discuss NR systems used in unlicensed spectrum, referred to as NR-unlicensed (NR-U).

[0094] The NR-U system supports two networking modes: licensed spectrum-assisted access and unlicensed spectrum-independent access. The former requires the use of licensed spectrum to access the network, with the unlicensed spectrum used as a secondary carrier. The latter allows independent networking through unlicensed spectrum, allowing UEs to access the network directly through the unlicensed spectrum.

[0095] Unlicensed spectrum is a spectrum that can be used for radio equipment communications, which is divided by countries and regions. This spectrum is generally considered to be a shared spectrum, that is, as long as the communication equipment meets the regulatory requirements set by the country or region on the spectrum, it can use the spectrum without applying for exclusive spectrum authorization from the country or region's exclusive spectrum management agency. Since the use of unlicensed spectrum needs to meet the specific regulatory requirements of each country and region, such as communication equipment using unlicensed spectrum in accordance with the "listen-before-talk, LBT" principle. Therefore, NR technology needs to be enhanced accordingly to adapt to the regulatory requirements of unlicensed frequency bands, while efficiently utilizing unlicensed spectrum to provide services. In the relevant standards, the standardization of NR-U technology in aspects such as channel monitoring process, initial access process, control channel design, HARQ and scheduling, and scheduling-free authorization transmission has been completed.

[0096] 5. Channel Monitoring

[0097] In order to allow various communication systems that use unlicensed spectrum for wireless communication to coexist in a friendly manner on the spectrum, some countries or regions have stipulated regulatory requirements that must be met when using unlicensed spectrum. For example, according to the regulations of some regions, when using unlicensed spectrum for communication, communication equipment follows the "Listen Before Talk (LBT)" principle, that is, before using the channel on the unlicensed spectrum to send a signal, the communication equipment needs to perform LBT (Listen Before Talk, or listen before use), or channel monitoring. Only when the channel monitoring result is that the channel is idle or LBT is successful, can the communication device send a signal through the channel; if the channel monitoring result of the communication device on the channel is that the channel is busy or LBT fails, then the communication device cannot send a signal through the channel. In addition, in order to ensure the fairness of the use of spectrum resources of the shared spectrum, if the communication device succeeds in LBT on the channel of the unlicensed spectrum, the time that the communication device can use the channel for communication transmission cannot exceed a certain time. This mechanism limits the maximum duration of communication after a successful LBT, allowing different communication devices to have the opportunity to access the shared channel, thereby enabling different communication systems to coexist in a friendly manner on the shared spectrum.

[0098] Because channel monitoring can bring interference avoidance and friendly coexistence benefits to communication transmissions between communication systems on shared spectrum, channel monitoring is a feature that must be supported by communication equipment in the unlicensed spectrum during the design process. From the perspective of system networking, channel monitoring includes two mechanisms: load-based equipment (LBE) LBT, also known as dynamic channel monitoring or dynamic channel occupancy, and frame-based equipment (FBE) LBT, also known as semi-static channel monitoring or semi-static channel occupancy.

[0099] 6. Dynamic Channel Monitoring

[0100] Dynamic channel monitoring can also be considered as an LBT method based on LBE, and its channel monitoring principle is that the communication equipment performs LBT on the carrier of the unlicensed spectrum after the service arrives, and starts sending signals on the carrier after the LBT is successful. The LBT method of dynamic channel monitoring includes type 1 (Type 1) channel access method and type 2 (Type 2) channel access method. Type 1 channel access method (also known as the first type of LBT) is a multi-slot channel detection with random backoff based on contention window size adjustment, wherein the corresponding channel access priority (Channel access priority class, CAPC) p can be selected according to the priority of the service to be transmitted. Type 2 channel access method (also known as the second type of LBT) is a channel access method based on a fixed-length monitoring time slot, wherein the Type 2 channel access method includes Type 2A channel access, Type 2B channel access and Type 2C channel access. Type 1 channel access method is mainly used for communication equipment to initiate channel occupancy, and Type 2 channel access method is mainly used for communication equipment to share channel occupancy.

[0101] FIG4 is a schematic diagram of a channel occupancy time obtained by a communication device after successful LBT on a channel of an unlicensed spectrum, and signal transmission using resources within the channel occupancy time.

[0102] 6. Default channel access mode on the base station side: Type 1 channel access

[0103] Taking the base station as an example, the channel access parameters corresponding to the channel access priority p on the base station side are shown in Table 1. In Table 1, mp refers to the number of backoff slots corresponding to the channel access priority p, CWp refers to the contention window (CW) size corresponding to the channel access priority p, CWmin,p refers to the minimum value of CWp corresponding to the channel access priority p, CWmax,p refers to the maximum value of CWp corresponding to the channel access priority p, and Tmcot,p refers to the channel occupancy time (COT) length corresponding to the channel access priority p.

[0104] If the channel access process is completed, the base station can use the channel to transmit the service to be transmitted. The maximum time length that the base station can use the channel for transmission cannot exceed Tmcot,p.

[0105] Table 1 - Channel access parameters corresponding to different channel access priorities p

[0106] 7. Channel Occupancy Time Sharing on the Base Station Side

[0107] After the base station initiates a COT, in addition to using the resources within the COT for downlink transmission, the resources within the COT can also be shared with the UE for uplink transmission. When the resources within the COT are shared with the UE for uplink transmission, the channel access method that the UE can use is the Type 2 channel access method, including Type 2A channel access, Type 2B channel access, or Type 2C channel access. Among them, Type 2A channel access, Type 2B channel access, and Type 2C channel access are all channel access methods based on fixed-length monitoring time slots.

[0108] In the existing technology, when a terminal operates on a sidelink in an unlicensed frequency band, it needs to perform different types of LBT before sending sidelink data. Only when the LBT is successful can it successfully access the channel for sidelink transmission. When there is no COT, the terminal needs to perform Type 1 LBT, and only after it succeeds can it initiate a COT. Other terminals that meet the conditions can also share the resources within this COT and use Type 2 LBT. In the existing technology, whether a terminal initiates a COT is determined by whether it has data to send and whether the Type 1 LBT is successful. It does not support scenarios where one terminal requests another terminal to initiate a COT for its own use.

[0109] Currently, standardization work is underway to deploy SL technology in unlicensed frequency bands, namely SL-U technology. SL-U technology can be deployed in commercial scenarios such as wearable smart devices, smart homes, and the industrial internet. In the Rel-18 SL-U discussion, all terminals had the same capabilities, and low-capability terminals were not considered. However, the cost and power consumption of terminal equipment are very important metrics for commercial deployment. The low cost and low power consumption brought by low-capability terminals or weak-capability terminals (RedCap UE, Reduced Capability UE) can provide a convenient channel for the commercialization of SL-U technology. From the perspective of low power consumption, how to save energy in SL-U RedCap terminals is an issue that needs to be studied.

[0110] When an SL-U terminal operates in an unlicensed frequency band, it must first perform LBT before transmitting data. When performing Type 1 channel access, the terminal must first determine the size of the random backoff counter N, which is a random value within the CWp. For example, when the CAPC is 4 and the CWp is 1023, assuming N is 1000, the terminal will require at least Td + N * Tsl = Tf + mp * Tsl + N * Tsl = 16 + 7 * 9 + 1000 * 9 = 9079 microseconds to perform Type 1 channel access. This means that a RedCap terminal must continuously perform channel sensing for at least 9 milliseconds to access the channel, resulting in significant power consumption. Therefore, energy conservation during the channel access process is a topic that requires research.

[0111] The present application provides a communication method. FIG5 is a schematic flow chart of a communication method 500 according to the present application embodiment. The method can be applied to the systems shown in FIG1-4, but is not limited thereto. The method includes at least part of the following contents.

[0112] S510: The first terminal receives first COT request information from the second terminal;

[0113] S520: The first terminal sends a first response message to the second terminal, where the first response message includes a first confirmation message and / or a second confirmation message;

[0114] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT (or will initiate a first COT);

[0115] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0116] In some implementations, the second terminal may be a RedCap UE.

[0117] In some embodiments, the first terminal may be a normal capability terminal or a non-RedCap UE. The first terminal may satisfy a first condition, which includes at least one of the following:

[0118] The first terminal is a target receiving terminal of the sidelink information sent by the second terminal;

[0119] The first terminal is a normal capability terminal or a non-RedCap UE;

[0120] The first terminal has a Type 1 LBT capability;

[0121] The first terminal has a sidelink sensing capability.

[0122] In one example, the sidelink information sent by the second terminal may include at least one of a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink feedback channel (PSFCH), and a sidelink synchronization signal block (S-SSB); wherein the S-SSB may include at least one of a sidelink primary synchronization signal (S-PSS), a sidelink secondary synchronization signal (S-SSS), and a physical sidelink broadcast channel (PSBCH). That is, the first terminal may be a target receiving terminal for information such as PSCCH, PSSCH, PSFCH, and S-SSB (including S-PSS, S-SSS, and PSBCH) sent by the second terminal.

[0123] In one example, the first terminal sends the first response information within a first time range. For example, if the second terminal sends the first COT request information at time T1, the first terminal sends the first response information within the time range [T1+t1, T1+t2]. Alternatively, if the first terminal receives the first COT request information at time T2, the first terminal sends the first response information within the time range [T2+t3, T2+t4], where t1, t2, t3, and t4 are preset values. The first terminal sends the first response information within the first time range to facilitate receipt of the first response information by the second terminal.

[0124] Through the above method, after the first terminal receives the first COT request information from the second terminal (such as the RedCap terminal), the first terminal can initiate a COT (such as the above-mentioned first COT) for use by other terminals including at least the second terminal, thereby realizing a terminal requesting another terminal to initiate a COT for its own use. In the method proposed in the embodiment of the present application, since the normal-capability terminal initiates a COT for use by other terminals including the weak-capability terminal based on the request of the weak-capability terminal, the weak-capability terminal does not need to initiate Type 1 LBT, thereby avoiding the large amount of power consumption generated by the weak-capability terminal due to Type 1 LBT.

[0125] In some implementations, the first COT to be initiated by the first terminal may satisfy a second condition, which mainly includes restrictions on the time domain resources and frequency domain resources occupied by the first COT, the time domain start time, the CAPC priority, etc. For example, the second condition includes at least one of the following:

[0126] The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal;

[0127] The first COT includes a resource block (RB set) to which the frequency domain resources occupied by the first COT request information belong;

[0128] The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal;

[0129] The first COT includes a resource block to which the first frequency domain resource belongs or a resource block (RB set) to which the first frequency domain resource set belongs;

[0130] The time domain start time of the first COT is no later than the first moment;

[0131] The time domain start time of the first COT is not later than the second time, where the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal;

[0132] The CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

[0133] In one example, the one or more time domain resources indicated or reserved by the second terminal include a sidelink time slot.

[0134] In one example, the one or more time domain resources indicated or reserved by the second terminal are indicated or reserved by at least one of the following:

[0135] First COT requests information;

[0136] First side information.

[0137] In an example, the first frequency domain resource or the first frequency domain resource set indicated or reserved by the second terminal may be indicated or reserved by at least one of the following:

[0138] the first COT request information;

[0139] First side information.

[0140] The one or more time domain resources indicated or reserved by the second terminal, and the first frequency domain resource or first frequency domain resource set indicated or reserved by the second terminal can be occupied when the second terminal sends sidelink information.

[0141] In one example, the first time may be indicated or scheduled by at least one of the following:

[0142] the first COT request information;

[0143] First side information.

[0144] In the above content, the first sidelink information may include at least one of PSCCH, PSSCH, PSFCH and a media access layer control element (MAC Control Element, MAC CE).

[0145] In some implementations, after the first terminal sends the first response information, it may perform a first type LBT (Type 1 LBT). In one example, the first terminal determines a third time; the first terminal starts performing Type 1 LBT at the third time.

[0146] The first terminal may determine the time (ie, the third time) at which the Type 1 LBT starts to be executed by itself through implementation.

[0147] Alternatively, the moment when Type1 LBT starts to be executed (ie, the third moment mentioned above) may be earlier than the time domain start time of the first COT.

[0148] In the above example, the frequency domain resources may include unlicensed frequency domain resources.

[0149] In some embodiments, after the first terminal sends the first response information to the second terminal, the first terminal may also initiate a first COT. The first COT may be used by the second terminal and / or other terminals. In one example, when the first terminal initiates the first COT, COT indication information may be included. The COT indication information includes at least one of the following:

[0150] First, the time domain resources of COT;

[0151] The frequency domain resource set of the first COT;

[0152] The time domain start time of the first COT;

[0153] The CAPC rating of the first COT.

[0154] According to the COT indication information, the second terminal (such as a weak capability terminal) and / or other terminals can use the first COT, so the weak capability terminal does not need to initiate Type 1 LBT, thereby avoiding the large amount of power consumption generated by the weak capability terminal due to Type 1 LBT.

[0155] The following describes the embodiments of the present application in detail with reference to the accompanying drawings.

[0156] Example 1:

[0157] Figure 6 is a schematic diagram of Example 1 of the present application. As shown in Figure 6, after receiving the first COT request information from the second terminal, the first terminal sends a first response information within a first time range. The first response information includes a first confirmation information or a second confirmation information. Among them, the first confirmation information can be used to indicate / confirm that the first terminal will initiate the first COT (or will initiate the first COT); the second confirmation information can be used to indicate / confirm that the first terminal will not initiate the first COT.

[0158] For example, if the time when the second terminal sends the first COT request message is recorded as T1, the first terminal can send the first response message within the time range of [T1+t1, T1+t2]. Alternatively, if the time when the first terminal receives the first COT request message is recorded as T2, the first terminal can send the first response message within the time range of [T2+t3, T2+t4]. t1, t2, t3, and t4 are preset values. The first terminal sends the first response message within the first time range, which can facilitate the second terminal to receive the first response message.

[0159] After sending the first confirmation information (ie, indicating / confirming that the first terminal will initiate the first COT), the first terminal can initiate the first COT. In Figure 6, the first COT initiated by the first terminal includes the sidelink resources indicated / reserved by the second terminal in the time domain.

[0160] In addition, the first COT initiated by the first terminal may include, in the frequency domain, the RB set to which the frequency domain resources occupied by the first COT request information belong, or the first frequency domain resources / first frequency domain resource set indicated / reserved by the second terminal, or the RB set to which the first frequency domain resources belong or the RB set to which the first frequency domain resource set belongs. The frequency domain resources occupied by the first COT will be described in detail in subsequent embodiments in conjunction with the accompanying drawings.

[0161] Example 2:

[0162] This embodiment mainly describes the starting position and duration of the first COT in the time domain. The duration of the first COT initiated by the first terminal may include at least one of the sidelink resources reserved by the second terminal. The sidelink resource may include a time slot in the sidelink time domain resource.

[0163] Figures 7A-7E are schematic diagrams of Example 2 of the present application. As shown in Figures 7A-7E, the first COT initiated by the first terminal includes one or more of the sideline resources reserved by the second terminal. In Figures 7A-7E, for convenience of display, the first response information sent by the first terminal after receiving the first COT request information is not shown. In fact, in this embodiment, after receiving the first COT request information, the first terminal can send a first response information, and when the first response information is a first confirmation information (i.e., indicating / confirming that the first terminal will initiate the first COT), the first terminal initiates the first COT, and the first COT includes at least one of the sideline resources reserved / indicated by the second terminal.

[0164] The sidelink resources reserved / indicated by the second terminal may be indicated by the first COT request information or by sidelink information, for example, by at least one of PSCCH, PSSCH, PSFCH, and MAC CE.

[0165] In addition, when the first terminal initiates the first COT, the CAPC level of the first COT may not be higher than the CAPC level indicated in the first COT request information. In other words, the CAPC level of the first COT is equal to or lower than the CAPC level of the data to be sent by the second terminal, so that the second terminal can use the first COT to send data.

[0166] In one example, when a first terminal initiates a first COT, it may include COT indication information to facilitate use of the first COT by a second terminal and / or other terminals. The COT indication information may include at least one of the time domain resources of the first COT, the frequency domain resource set of the first COT, the time domain start time of the first COT, and the CAPC level of the first COT. Based on the COT indication information, the second terminal and / or other terminals can understand the time and frequency domain locations of the first COT and the corresponding CAPC level, thereby enabling use of the first COT.

[0167] For example, when a terminal uses the first COT, it determines whether the CAPC level of its own service is higher than or equal to the CAPC level of the first COT. If it is higher than or equal to the CAPC level of the first COT, the terminal can use the first COT. For example, the CAPC levels include 0, 1, 2, 3, 4, and 5, with smaller values ​​indicating higher levels. If the CAPC level of the first COT is 2 and the CAPC level of the data that terminal A needs to send is 1, terminal A can use the first COT to send data. For another example, if the CAPC level of the first COT is 2 and the CAPC level of the data that terminal B needs to send is 5, terminal B cannot use the first COT to send data.

[0168] Example 3:

[0169] This embodiment mainly introduces the position of the first COT in the frequency domain.

[0170] Figure 8A is a schematic diagram of Embodiment 3 of the present application. In the example shown in Figure 8A , the first COT includes, in the frequency domain, the sidelink resources occupied by the second terminal when sending the first COT request information. As shown in Figure 8A , when the second terminal sends the first COT request information, the occupied sidelink resources belong to RB set 1. Therefore, the first COT initiated by the first terminal must include at least RB set 1.

[0171] Figure 8B is the second schematic diagram of the third embodiment of the present application. In the example shown in Figure 8B , the first COT includes, in the frequency domain, the sidelink resources reserved / indicated by the second terminal, or includes the RB set occupied by the sidelink resources reserved / indicated by the second terminal. As shown in Figure 8B , the second terminal sends a first COT request message on RB set 1. The sidelink resources reserved / indicated by the first COT request message occupy part or all of the sidelink resources in RB set 1 and RB set 2. Therefore, when the first terminal initiates the first COT, the first COT may include RB set 1 and / or RB set 2.

[0172] In the example shown in FIG8B , the sideline resource reserved / indicated by the second terminal is indicated by the first COT request information. In other examples, the second terminal may also indicate / reserve the sideline resource through sideline information, for example, through at least one of PSCCH, PSSCH, PSFCH, and MAC CE.

[0173] In addition, when the first terminal initiates the first COT, the CAPC level of the first COT may not be higher than the CAPC level indicated in the first COT request information. In other words, the CAPC level of the first COT is equal to or lower than the CAPC level of the data to be sent by the second terminal, so that the second terminal can use the first COT to send data.

[0174] In one example, when a first terminal initiates a first COT, it may carry COT indication information to facilitate use of the first COT by a second terminal and / or other terminals. The COT indication information may include at least one of the time domain resources of the first COT, the frequency domain resource set of the first COT, the time domain start time of the first COT, and the CAPC level of the first COT.

[0175] Example 4:

[0176] This embodiment mainly introduces the starting position of the first COT in the time domain, that is, the time domain starting time of the first COT.

[0177] In one example, the second terminal can indicate or reserve a time; then, the first terminal must initiate the first COT no later than that time. As shown in Figure 9A , in this example, the first COT request message sent by the second terminal indicates time n. Therefore, the time domain start time of the first COT initiated by the first terminal cannot be later than time n. Alternatively, the second terminal can indicate time n via sidelink information, for example, via at least one of the PSCCH, PSSCH, PSFCH, and MAC CE. In this example, the second terminal indicates / reserves time n by displaying an indication.

[0178] In one example, the second terminal may indicate or reserve time n by implicit indication. For example, the second terminal indicates / reserves one or more time domain resources through the first COT request information or sideline information. The time domain start time of the one or more time domain resources may be considered as the time n. Then, the time domain start time of the first COT initiated by the first terminal cannot be later than the time domain start time of the one or more time domain resources. As shown in Figure 9B, in this example, the first COT request information sent by the second terminal reserves the sideline resource. Then, the time domain start time of the first COT initiated by the first terminal cannot be later than the time domain start time of the sideline resource reserved by the second terminal.

[0179] In addition, when the first terminal initiates the first COT, the CAPC level of the first COT may not be higher than the CAPC level indicated in the first COT request information. In other words, the CAPC level of the first COT is equal to or lower than the CAPC level of the data to be sent by the second terminal, so that the second terminal can use the first COT to send data.

[0180] In one example, when a first terminal initiates a first COT, it may carry COT indication information to facilitate use of the first COT by a second terminal and / or other terminals. The COT indication information may include at least one of the time domain resources of the first COT, the frequency domain resource set of the first COT, the time domain start time of the first COT, and the CAPC level of the first COT.

[0181] In the above embodiments, the first terminal may include a normal capability terminal or a non-RedCap UE, and the second terminal may include a RedCap UE. The first COT initiated by the first terminal may be used by the second terminal and / or other terminals.

[0182] The above embodiments are not independent of each other. The contents of different embodiments can be combined with each other. The specific combination method will not be repeated here.

[0183] In the method for a sidelink terminal to initiate a COT proposed in an embodiment of the present application, after the first terminal receives the first COT request information initiated by the second terminal, the first terminal can initiate a COT for use by other terminals including at least the second terminal (Redcap weak-capability terminal). The COT initiated by the first terminal meets certain conditions in terms of occupied time domain resources, frequency domain resources, time domain start time, and CAPC level. In addition, when initiating the first COT, the first terminal can carry COT indication information, which can facilitate the use of the COT by the second terminal and / or other terminals. Therefore, the weak-capability terminal does not need to initiate Type 1 LBT, thereby avoiding the large amount of power consumption generated by the weak-capability terminal due to Type 1 LBT.

[0184] The present application also provides a communication method. FIG10 is a schematic flow chart of a communication method 1000 according to an embodiment of the present application. The method can be applied to the systems shown in FIG1-4, but is not limited thereto. The method includes at least part of the following contents.

[0185] S1010: The second terminal sends a first COT request message to the first terminal;

[0186] S1020: The second terminal receives a first response message from the first terminal, where the first response message includes a first confirmation message and / or a second confirmation message;

[0187] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0188] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0189] In some implementations, the second terminal includes a low-capability terminal.

[0190] In some embodiments, the first terminal satisfies a first condition, and the first condition includes at least one of the following:

[0191] The first terminal is a target receiving terminal of the sidelink information sent by the second terminal;

[0192] The first terminal is a normal-capability terminal or a non-weak-capability terminal;

[0193] The first terminal has a first type LBT capability;

[0194] The first terminal has a sidelink perception capability.

[0195] In this way, a weak-capability terminal can request a normal-capability terminal or a non-weak-capability terminal to initiate a COT for use by the weak-capability terminal or other terminals. Therefore, the weak-capability terminal does not need to initiate Type 1 LBT, thereby avoiding the large amount of power consumption generated by the weak-capability terminal due to Type 1 LBT.

[0196] In some embodiments, the sidelink information sent by the second terminal includes at least one of PSCCH, PSSCH, PSFCH and S-SSB.

[0197] In some embodiments, the S-SSB includes at least one of an S-PSS, an S-SSS, and a PSBCH.

[0198] In some embodiments, the first COT satisfies a second condition, which includes at least one of the following:

[0199] The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal;

[0200] The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong;

[0201] The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal;

[0202] The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs;

[0203] The time domain start time of the first COT is no later than the first moment;

[0204] The time domain start time of the first COT is not later than the second time, and the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal;

[0205] The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

[0206] The first COT initiated by the first terminal may meet certain conditions in terms of occupied time domain resources, frequency domain resources, time domain start time, and CAPC level, so that the second terminal and / or other terminals can use the first COT.

[0207] In some embodiments, the one or more time domain resources include a sidetrack time slot.

[0208] In some embodiments, the one or more time domain resources are indicated or reserved by at least one of the following:

[0209] First COT requests information;

[0210] First side information.

[0211] In some implementations, the first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following:

[0212] First COT requests information;

[0213] First side information.

[0214] In some embodiments, the first time is indicated or scheduled by at least one of the following:

[0215] First COT requests information;

[0216] First side information.

[0217] In some implementations, the first sidelink information includes at least one of: PSCCH, PSSCH, PSFCH, and MAC CE.

[0218] In some embodiments, the second terminal further includes performing LBT on the first COT.

[0219] In some embodiments, the first COT is used by the second terminal and / or other terminals.

[0220] The present embodiment further provides a first terminal. FIG11 is a schematic structural diagram of the first terminal 1100 according to the embodiment of the present application, including:

[0221] The first receiving module 1110 is configured to receive first COT request information from a second terminal;

[0222] The first sending module 1120 is configured to send a first response message to the second terminal, where the first response message includes a first confirmation message and / or a second confirmation message; wherein,

[0223] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0224] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0225] In some embodiments, the first terminal satisfies a first condition, where the first condition includes at least one of the following:

[0226] The first terminal is a target receiving terminal of the sidelink information sent by the second terminal;

[0227] The first terminal is a normal-capability terminal or a non-weak-capability terminal;

[0228] The first terminal has a first type of listen-before-talk (LBT) capability;

[0229] The first terminal has a sidelink perception capability.

[0230] In some embodiments, the sidelink information sent by the second terminal includes at least one of PSCCH, PSSCH, PSFCH and S-SSB.

[0231] In some embodiments, the S-SSB includes at least one of an S-PSS, an S-SSS, and a PSBCH.

[0232] In some embodiments, the first COT satisfies a second condition, and the second condition includes at least one of the following:

[0233] The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal;

[0234] The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong;

[0235] The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal;

[0236] The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs;

[0237] The time domain start time of the first COT is no later than the first moment;

[0238] The time domain start time of the first COT is not later than the second time, and the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal;

[0239] The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

[0240] In some embodiments, the one or more time domain resources include a sidetrack time slot.

[0241] In some embodiments, the one or more time domain resources are indicated or reserved by at least one of the following:

[0242] First COT requests information;

[0243] First side information.

[0244] In some implementations, the first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following:

[0245] First COT requests information;

[0246] First side information.

[0247] In some embodiments, the first time is indicated or scheduled by at least one of the following:

[0248] First COT requests information;

[0249] First side information.

[0250] In some implementations, the first sidelink information includes at least one of: PSCCH, PSSCH, PSFCH, and MAC CE.

[0251] Figure 12 is a schematic diagram of the structure of a first terminal 1200 according to an embodiment of the present application. The first terminal 1200 includes one or more features of the above-mentioned first terminal 1200 embodiment. In one possible implementation, in the embodiment of the present application, it further includes:

[0252] The first execution module 1230 is used to execute the first type LBT.

[0253] In some implementations, the first execution module 1230 is configured to:

[0254] Determine the third moment;

[0255] The first type LBT starts to be executed at the third time.

[0256] In some implementations, the third time instant is earlier than the time domain start time of the first COT.

[0257] In some implementations, the method further includes an initiating module 1240 configured to initiate a first COT.

[0258] In some embodiments, the initiating module 1240 is configured to carry COT indication information when initiating the first COT, where the COT indication information includes at least one of the following:

[0259] First, the time domain resources of COT;

[0260] The frequency domain resource set of the first COT;

[0261] The time domain start time of the first COT;

[0262] The CAPC rating of the first COT.

[0263] In some embodiments, the first COT is used by the second terminal and / or other terminals.

[0264] In some embodiments, the second terminal comprises a low-capability terminal.

[0265] It should be understood that the above and other operations and / or functions of the modules in the first terminal according to the embodiment of the present application are respectively for implementing the corresponding processes of the first terminal in the method 500 of Figure 5, and are not repeated here for the sake of brevity.

[0266] The present embodiment further provides a second terminal. FIG13 is a schematic structural diagram of a second terminal 1300 according to the present embodiment, including:

[0267] The second sending module 1310 is configured to send first COT request information to the first terminal;

[0268] The second receiving module 1320 is configured to receive first response information from the first terminal, where the first response information includes first confirmation information and / or second confirmation information; wherein,

[0269] First confirmation information, used to indicate or confirm that the first terminal will initiate a first COT;

[0270] The second confirmation information is used to indicate or confirm that the first terminal will not initiate the first COT.

[0271] In some embodiments, the second terminal comprises a low-capability terminal.

[0272] In some embodiments, the first terminal satisfies a first condition, where the first condition includes at least one of the following:

[0273] The first terminal is a target receiving terminal of the sidelink information sent by the second terminal;

[0274] The first terminal is a normal-capability terminal or a non-weak-capability terminal;

[0275] The first terminal has a first type LBT capability;

[0276] The first terminal has a sidelink perception capability.

[0277] In some embodiments, the sidelink information sent by the second terminal includes at least one of PSCCH, PSSCH, PSFCH and S-SSB.

[0278] In some embodiments, the S-SSB includes at least one of an S-PSS, an S-SSS, and a PSBCH.

[0279] In some embodiments, the first COT satisfies a second condition, and the second condition includes at least one of the following:

[0280] The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal;

[0281] The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong;

[0282] The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal;

[0283] The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs;

[0284] The time domain start time of the first COT is no later than the first moment;

[0285] The time domain start time of the first COT is not later than the second time, and the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal;

[0286] The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

[0287] In some embodiments, the one or more time domain resources include a sidetrack time slot.

[0288] In some embodiments, the one or more time domain resources are indicated or reserved by at least one of the following:

[0289] First COT requests information;

[0290] First side information.

[0291] In some implementations, the first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following:

[0292] First COT requests information;

[0293] First side information.

[0294] In some embodiments, the first time is indicated or scheduled by at least one of the following:

[0295] First COT requests information;

[0296] First side information.

[0297] In some implementations, the first sidelink information includes at least one of: PSCCH, PSSCH, PSFCH, and MAC CE.

[0298] Figure 14 is a schematic diagram of the structure of a second terminal 1400 according to an embodiment of the present application. The second terminal 1400 includes one or more features of the above-mentioned second terminal 1300 embodiment. In one possible implementation, in the embodiment of the present application, it further includes:

[0299] The second execution module 1430 is configured to execute LBT on the first COT.

[0300] In some embodiments, the first COT is used by the second terminal and / or other terminals.

[0301] It should be understood that the above and other operations and / or functions of the modules in the communication device according to the embodiment of the present application are respectively for implementing the corresponding processes of the second terminal in method 1000 of Figure 10. For the sake of brevity, they are not repeated here.

[0302] It should be noted that the functions described in the various modules (submodules, units, or components, etc.) in the communication device of the embodiment of the present application can be implemented by different modules (submodules, units, or components, etc.) or by the same module (submodule, unit, or component, etc.). For example, the first receiving module and the second receiving module can be different modules or the same module, and both can implement their corresponding functions in the embodiment of the present application. In addition, the sending module and the receiving module in the embodiment of the present application can be implemented by the transceiver of the device, and some or all of the other modules can be implemented by the processor of the device.

[0303] Figure 15 is a schematic structural diagram of a communication device 1500 according to an embodiment of the present application. The communication device 1500 shown in Figure 15 includes a processor 1510, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0304] In some implementations, as shown in FIG15 , the communication device 1500 may further include a memory 1520. The processor 1510 may call and execute a computer program from the memory 1520 to implement the communication device in the embodiment of the present application.

[0305] The memory 1520 may be a separate device independent of the processor 1510 , or may be integrated into the processor 1510 .

[0306] In some embodiments, as shown in FIG. 15 , the communication device 1500 may further include a transceiver 1530 , and the processor 1510 may control the transceiver 1530 to communicate with other devices. Specifically, the transceiver 1530 may send information or data to other devices, or receive information or data sent by other devices.

[0307] The transceiver 1530 may include a transmitter and a receiver. The transceiver 1530 may further include an antenna, and the number of antennas may be one or more.

[0308] In some embodiments, the communication device 1500 may be the communication device of an embodiment of the present application, and the communication device 1500 may implement the corresponding processes implemented by the communication device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0309] Figure 16 is a schematic structural diagram of a chip 1600 according to an embodiment of the present application. The chip 1600 shown in Figure 16 includes a processor 1610, which can call and execute a computer program from a memory to implement the method in the embodiment of the present application.

[0310] In some embodiments, as shown in FIG16 , the chip 1600 may further include a memory 1620 , wherein the processor 1610 may call and execute a computer program from the memory 1620 to implement the method in the embodiment of the present application.

[0311] The memory 1620 may be a separate device independent of the processor 1610 , or may be integrated into the processor 1610 .

[0312] In some embodiments, the chip 1600 may further include an input interface 1630. The processor 1610 may control the input interface 1630 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0313] In some embodiments, the chip 1600 may further include an output interface 1640. The processor 1610 may control the output interface 1640 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0314] In some embodiments, the chip can be applied to the communication equipment in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network equipment in the various methods of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0315] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0316] The processor mentioned above may be a general-purpose processor, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor, etc.

[0317] The memory mentioned above may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM).

[0318] It should be understood that the above-mentioned memories are exemplary but not restrictive. For example, the memories in the embodiments of the present application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM RAM (DR RAM), etc. In other words, the memories in the embodiments of the present application are intended to include, but are not limited to, these and any other suitable types of memories.

[0319] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable devices. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instruction can be transmitted from a website, computer, server or data center by wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) mode to another website, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state disk (SSD)).

[0320] It should be understood that in the various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0321] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0322] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present application should be included within the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A communication method, comprising: The first terminal receives first channel occupation time COT request information from the second terminal; The first terminal sends a first response message to the second terminal, wherein the first response message includes a first confirmation message and / or a second confirmation message; wherein, The first confirmation information is used to indicate or confirm that the first terminal will initiate a first COT; The second confirmation information is used to indicate or confirm that the first terminal will not initiate a first COT.

2. The method according to claim 1, wherein: The first terminal satisfies a first condition, wherein the first condition includes at least one of the following: The first terminal is a target receiving terminal of the sidelink information sent by the second terminal; The first terminal is a normal-capability terminal or a non-weak-capability terminal; The first terminal has a first type of listen-before-talk (LBT) capability; The first terminal has a sidelink perception capability.

3. The method according to claim 2, wherein: The sidelink information sent by the second terminal includes at least one of a physical sidelink control channel PSCCH, a physical sidelink shared channel PSSCH, a physical sidelink feedback channel PSFCH and a sidelink synchronization signal block S-SSB.

4. The method according to claim 3, wherein: The S-SSB includes at least one of a sideline primary synchronization signal S-PSS, a sideline secondary synchronization signal S-SSS and a physical sideline broadcast channel PSBCH.

5. The method according to any one of claims 1 to 4, wherein: The first COT satisfies a second condition, wherein the second condition includes at least one of the following: The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal; The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong; The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal; The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs; The time domain start time of the first COT is no later than the first moment; The time domain start time of the first COT is not later than a second time, where the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal; The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

6. The method according to claim 5, wherein: The one or more time domain resources include a sideline time slot.

7. The method according to claim 5, wherein: The one or more time domain resources are indicated or reserved by at least one of the following: the first COT requests information; First side information.

8. The method according to claim 5, wherein: The first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following: the first COT requests information; First side information.

9. The method according to claim 5, wherein: The first time is indicated or scheduled by at least one of the following: the first COT requests information; First side information.

10. The method according to any one of claims 7 to 9, wherein: The first sidelink information includes: at least one of: PSCCH, PSSCH, PSFCH and media access layer control element MAC CE.

11. The method according to any one of claims 1-10 further includes, the first terminal performing a first type of LBT.

12. The method according to claim 11, wherein: The first terminal performing the first type of LBT includes: The first terminal determines a third time; The first terminal starts to perform the first type LBT at the third time.

13. The method according to claim 12, wherein: The third moment is earlier than the time domain start time of the first COT.

14. The method according to any one of claims 11 to 13, further comprising: the first terminal initiating the first COT.

15. The method according to claim 14, further comprising, when the first terminal initiates the first COT, carrying COT indication information, wherein the COT indication information includes at least one of the following: The time domain resources of the first COT; A frequency domain resource set of the first COT; The time domain start time of the first COT; The CAPC rating of the first COT.

16. The method according to any one of claims 1 to 15, wherein: The first COT is used by the second terminal and / or other terminals.

17. The method according to any one of claims 1 to 16, wherein: The second terminal includes a weak capability terminal.

18. A communication method, comprising: The second terminal sends a first COT request message to the first terminal; The second terminal receives first response information from the first terminal, where the first response information includes first confirmation information and / or second confirmation information; wherein, The first confirmation information is used to indicate or confirm that the first terminal will initiate a first COT; The second confirmation information is used to indicate or confirm that the first terminal will not initiate a first COT.

19. The method according to claim 18, wherein: The second terminal includes a weak capability terminal.

20. The method according to claim 18 or 19, wherein: The first terminal satisfies a first condition, wherein the first condition includes at least one of the following: The first terminal is a target receiving terminal of the sidelink information sent by the second terminal; The first terminal is a normal-capability terminal or a non-weak-capability terminal; The first terminal has a first type of LBT capability; The first terminal has a sidelink perception capability.

21. The method according to claim 20, wherein: The side link information sent by the second terminal includes at least one of PSCCH, PSSCH, PSFCH and S-SSB.

22. The method according to claim 21, wherein: The S-SSB includes at least one of S-PSS, S-SSS and PSBCH.

23. The method according to any one of claims 18 to 22, wherein: The first COT satisfies a second condition, wherein the second condition includes at least one of the following: The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal; The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong; The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal; The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs; The time domain start time of the first COT is no later than the first moment; The time domain start time of the first COT is not later than a second time, where the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal; The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

24. The method according to claim 23, wherein: The one or more time domain resources include a sideline time slot.

25. The method according to claim 23, wherein: The one or more time domain resources are indicated or reserved by at least one of the following: the first COT requests information; First side information.

26. The method of claim 23, wherein: The first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following: the first COT requests information; First side information.

27. The method according to claim 23, wherein: The first time is indicated or scheduled by at least one of the following: the first COT requests information; First side information.

28. The method according to any one of claims 25 to 27, wherein: The first sideline information includes: at least one of: PSCCH, PSSCH, PSFCH and MAC CE.

29. The method according to any one of claims 18 to 28, further comprising the second terminal performing LBT on the first COT.

30. The method according to any one of claims 18 to 29, wherein: The first COT is used by the second terminal and / or other terminals.

31. A first terminal, comprising: A first receiving module, configured to receive first COT request information from a second terminal; The first sending module is used to send first response information to the second terminal, where the first response information includes first confirmation information and / or second confirmation information; wherein, The first confirmation information is used to indicate or confirm that the first terminal will initiate a first COT; The second confirmation information is used to indicate or confirm that the first terminal will not initiate a first COT.

32. The first terminal according to claim 31, wherein: The first terminal satisfies a first condition, wherein the first condition includes at least one of the following: The first terminal is a target receiving terminal of the sidelink information sent by the second terminal; The first terminal is a normal-capability terminal or a non-weak-capability terminal; The first terminal has a first type of listen-before-talk (LBT) capability; The first terminal has a sidelink perception capability.

33. The first terminal according to claim 32, wherein: The side link information sent by the second terminal includes at least one of PSCCH, PSSCH, PSFCH and S-SSB.

34. The first terminal according to claim 33, wherein: The S-SSB includes at least one of S-PSS, S-SSS and PSBCH.

35. The first terminal according to any one of claims 31 to 34, wherein: The first COT satisfies a second condition, wherein the second condition includes at least one of the following: The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal; The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong; The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal; The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs; The time domain start time of the first COT is no later than the first moment; The time domain start time of the first COT is not later than a second time, where the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal; The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

36. The first terminal according to claim 35, wherein: The one or more time domain resources include a sideline time slot.

37. The first terminal according to claim 35, wherein: The one or more time domain resources are indicated or reserved by at least one of the following: the first COT requests information; First side information.

38. The first terminal according to claim 35, wherein: The first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following: the first COT requests information; First side information.

39. The first terminal according to claim 35, wherein: The first time is indicated or scheduled by at least one of the following: the first COT requests information; First side information.

40. The first terminal according to any one of claims 37 to 39, wherein: The first sideline information includes: at least one of: PSCCH, PSSCH, PSFCH and MAC CE.

41. The first terminal according to any one of claims 31-40, further comprising a first execution module, configured to execute a first type of LBT.

42. The first terminal according to claim 41, wherein: The first execution module is used to: Determine the third moment; The first type LBT starts to be executed at the third time.

43. The first terminal according to claim 42, wherein: The third moment is earlier than the time domain start time of the first COT.

44. The first terminal according to any one of claims 41 to 43, further comprising an initiating module, configured to initiate the first COT.

45. The first terminal according to claim 44, wherein: The initiating module is used to carry COT indication information when initiating the first COT, and the COT indication information includes at least one of the following: The time domain resources of the first COT; A frequency domain resource set of the first COT; The time domain start time of the first COT; The CAPC rating of the first COT.

46. ​​The first terminal according to any one of claims 31 to 45, wherein: The first COT is used by the second terminal and / or other terminals.

47. The first terminal according to any one of claims 31 to 46, wherein: The second terminal includes a weak capability terminal.

48. A second terminal, comprising: A second sending module, configured to send first COT request information to the first terminal; The second receiving module is used to receive first response information from the first terminal, where the first response information includes first confirmation information and / or or second confirmation information; wherein, The first confirmation information is used to indicate or confirm that the first terminal will initiate a first COT; The second confirmation information is used to indicate or confirm that the first terminal will not initiate a first COT.

49. The second terminal according to claim 48, wherein: The second terminal includes a weak capability terminal.

50. The second terminal according to claim 48 or 49, wherein: The first terminal satisfies a first condition, wherein the first condition includes at least one of the following: The first terminal is a target receiving terminal of the sidelink information sent by the second terminal; The first terminal is a normal-capability terminal or a non-weak-capability terminal; The first terminal has a first type of LBT capability; The first terminal has a sidelink perception capability.

51. The second terminal according to claim 50, wherein: The side link information sent by the second terminal includes at least one of PSCCH, PSSCH, PSFCH and S-SSB.

52. The second terminal according to claim 51, wherein: The S-SSB includes at least one of S-PSS, S-SSS and PSBCH.

53. The second terminal according to any one of claims 48 to 52, wherein: The first COT satisfies a second condition, wherein the second condition includes at least one of the following: The first COT includes at least one time domain resource among the one or more time domain resources indicated or reserved by the second terminal; The first COT includes a resource block to which the frequency domain resources occupied by the first COT request information belong; The first COT includes a first frequency domain resource or a first frequency domain resource set indicated or reserved by the second terminal; The first COT includes a resource block to which the first frequency domain resource belongs or a resource block to which the first frequency domain resource set belongs; The time domain start time of the first COT is no later than the first moment; The time domain start time of the first COT is not later than a second time, where the second time includes the time domain start time of one or more time domain resources indicated or reserved by the second terminal; The channel access priority CAPC level of the first COT is not higher than the CAPC level indicated in the first COT request information.

54. The second terminal according to claim 53, wherein: The one or more time domain resources include a sideline time slot.

55. The second terminal according to claim 53, wherein: The one or more time domain resources are indicated or reserved by at least one of the following: the first COT requests information; First side information.

56. The second terminal according to claim 53, wherein: The first frequency domain resource or the first frequency domain resource set is indicated or reserved by at least one of the following: the first COT requests information; First side information.

57. The second terminal according to claim 53, wherein: The first time is indicated or scheduled by at least one of the following: the first COT requests information; First side information.

58. The second terminal according to any one of claims 55-57, wherein: The first sideline information includes: at least one of: PSCCH, PSSCH, PSFCH and MAC CE.

59. The second terminal according to any one of claims 48-58, further comprising a second execution module, configured to execute LBT on the first COT.

60. The second terminal according to any one of claims 48 to 59, wherein: The first COT is used by the second terminal and / or other terminals.

61. A communication device comprising: A processor, a memory and a transceiver, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory and control the transceiver to execute the method as described in any one of claims 1 to 17 or 18 to 30.

62. A chip, comprising: A processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 17 or 18 to 30.

63. A computer-readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the method according to any one of claims 1 to 17 or 18 to 30.

64. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 17 or 18 to 30.

65. A computer program causing a computer to execute the method of any one of claims 1 to 17 or 18 to 30.

Images