Communication method and communication device

Abstract

The invention provides a communication method and a communication device. The method comprises the following steps: a network device configures a first bandwidth part or a first resource pool for a sidelink for a first terminal device; and the network device configures the first bandwidth part and / or the second bandwidth part or the first resource pool and / or the second resource pool for a sidelink for a second terminal device, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the first terminal device. According to the method provided by the embodiment of the invention, the sharing of the bandwidth part and / or the resource pool between the terminal devices with different capabilities and different versions is facilitated.

Description

Communication method and communication device Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a communication method and a communication device. Background Art

[0002] With the development of communication technology, the types of terminal devices are increasing. However, it is still unclear how terminal devices with different capabilities and versions can share bandwidth and / or resource pools on the sidelink.

[0003] Summary of the Invention

[0004] The embodiments of the present application provide a communication method and a communication device. The following describes various aspects of the embodiments of the present application.

[0005] In a first aspect, a communication method is provided, comprising: a network device configures a first bandwidth portion or a first resource pool for a side link for a first terminal device; the network device configures the first bandwidth portion and / or the second bandwidth portion, or the first resource pool and / or the second resource pool for a side link for a second terminal device, the bandwidth supported by the second terminal device being different from the bandwidth supported by the first terminal device.

[0006] According to a second aspect, a communication method is provided, comprising: a first terminal device and a second terminal device perform sidelink transmission via a first bandwidth portion or a first resource pool, wherein the first terminal device is configured with the first bandwidth portion or the first resource pool for the sidelink, the second terminal device is configured with the first bandwidth portion and / or the second bandwidth portion, or the first resource pool and / or the second resource pool for the sidelink, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the first terminal device.

[0007] According to a third aspect, a communication device is provided, comprising: a configuration unit for configuring a first bandwidth part or a first resource pool for a side link for a first terminal device; the configuration unit is for configuring the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for a side link for a second terminal device, the bandwidth supported by the second terminal device being different from the bandwidth supported by the first terminal device.

[0008] In a fourth aspect, a communication device is provided, comprising: a transmission unit for performing sidelink transmission with a second terminal device through a first bandwidth part or a first resource pool, wherein the device is configured with the first bandwidth part or the first resource pool for the sidelink, the second terminal device is configured with the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for the sidelink, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the device.

[0009] In a fifth aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in the first aspect.

[0010] In the sixth aspect, a communication device is provided, comprising a memory, a transceiver and a processor, wherein the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method described in the second aspect.

[0011] In a seventh aspect, a communication device is provided, comprising a processor configured to call a program from a memory so that the communication device executes the method described in the first aspect.

[0012] In an eighth aspect, a communication device is provided, comprising a processor for calling a program from a memory, so that the communication device executes the method described in the second aspect.

[0013] In a ninth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the first aspect.

[0014] In a tenth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in the second aspect.

[0015] In an eleventh aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the first aspect.

[0016] In a twelfth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in the second aspect.

[0017] In a thirteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the first aspect.

[0018] In a fourteenth aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method described in the second aspect.

[0019] In a fifteenth aspect, a computer program is provided, which enables a computer to execute the method described in the first aspect.

[0020] In a sixteenth aspect, a computer program is provided, which enables a computer to execute the method described in the second aspect.

[0021] In an embodiment of the present application, the network device configures the first bandwidth part or the first resource pool for the side link for the first terminal device, and the network device configures the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for the side link for the second terminal device, which facilitates sharing of bandwidth parts and / or resource pools between terminal devices of different capabilities and different versions. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] FIG1 is an exemplary diagram of a wireless communication system according to an embodiment of the present application.

[0023] FIG2 is an exemplary diagram of a wireless communication system according to another embodiment of the present application.

[0024] FIG3 is an exemplary diagram of a wireless communication system applied in yet another embodiment of the present application.

[0025] FIG4 is an exemplary diagram of a wireless communication system applied in yet another embodiment of the present application.

[0026] FIG5 is an example diagram of unicast transmission in an embodiment of the present application.

[0027] FIG6 is an example diagram of multicast transmission in an embodiment of the present application.

[0028] FIG7 is an example diagram of broadcast transmission in an embodiment of the present application.

[0029] FIG8 is an example diagram of a time slot structure in V2X in an embodiment of the present application.

[0030] FIG9 is a schematic diagram of PSFCH resources and the corresponding number of OFDM symbols in a time slot.

[0031] FIG10 is a schematic diagram of a second-order SCI mapping method.

[0032] FIG11 is a schematic diagram of the time-frequency domain position of DMRS in PSCCH.

[0033] FIG12 is a schematic diagram of the time domain positions of 4 DMRS symbols when the number of PSSCH symbols is 13.

[0034] FIG13 is a schematic diagram of single-symbol DMRS frequency domain type 1.

[0035] FIG14 is a schematic diagram of the time-frequency position of the SL CSI-RS.

[0036] FIG15 is a schematic diagram of channel occupancy time and channel occupancy.

[0037] FIG16 is a schematic flowchart of a communication method provided in accordance with an embodiment of the present application.

[0038] FIG17 is a schematic flowchart of a communication method provided in another embodiment of the present application.

[0039] FIG18 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0040] FIG19 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0041] FIG20 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0042] FIG21 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0043] FIG22 is a schematic flowchart of a communication method provided in yet another embodiment of the present application.

[0044] FIG23 is a schematic structural diagram of a communication device provided in one embodiment of the present application.

[0045] FIG24 is a schematic structural diagram of a communication device provided in another embodiment of the present application.

[0046] FIG25 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The technical solution in this application will be described below with reference to the accompanying drawings.

[0048] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided by the present application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0049] In the embodiments of the present application, user equipment (UE) may also be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. The UE in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device or vehicle-mounted device with wireless connection capabilities. The UE in the embodiments of the present application can be a mobile phone, a tablet, a laptop, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle to everything (V2X) or device to device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through a base station.

[0050] The network device in the embodiments of the present application may be a device for communicating with a UE, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a UE to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof.

[0051] It should be understood that all or part of the functions of the network device and UE in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0052] The technical solutions in the embodiments of the present application can be applied to sideline communications (i.e., sidelink communications), and the sideline communications will be first introduced in detail below.

[0053] In sideline communication, according to the network coverage of the communicating terminal equipment, it can be divided into sideline communication within the network coverage, sideline communication with partial network coverage, and sideline communication outside the network coverage, as shown in Figures 1, 2, 3 and 4 respectively.

[0054] In sideline communications within network coverage, all terminal devices performing sideline communications are within the coverage of the same base station. As shown in Figure 1, terminal devices 120 and 130 are both within the network coverage of network device 110, can receive the sideline configuration sent by network device 110, and perform sideline communications based on the sideline configuration.

[0055] In the case of partial network coverage for sidelink communication, some terminal devices performing sidelink communication are located within the coverage of the network device. As shown in FIG2 , terminal device 220 is able to receive the sidelink configuration of network device 210 and perform sidelink communication based on the sidelink configuration, while terminal device 230 located outside the network coverage cannot receive the sidelink configuration of network device 210. In this case, terminal device 230 outside the network coverage can determine the sidelink configuration based on pre-configuration information and information carried in the physical sidelink broadcast channel (PSBCH) sent by terminal device 220, and perform sidelink communication based on the sidelink configuration.

[0056] For sideline communications outside network coverage, all terminal devices performing sideline communications are located outside network coverage. As shown in Figure 3, terminal devices 310 and 320 are both located outside network coverage. In this case, terminal devices 310 and 320 can each determine a sideline configuration based on pre-configured information and perform sideline communications based on the sideline configuration.

[0057] In sideline communication, multiple terminal devices can also form a communication group. This communication group has a central control node, which can also serve as the cluster header (CH). This central control node has one of the following functions: responsible for establishing the communication group; controlling the joining and leaving of group members; coordinating resources, allocating sideline transmission resources to other terminal devices in the communication group, receiving sideline feedback information from other terminal devices; and coordinating resources with other communication groups. As shown in Figure 4, terminal devices 410, 420, and 430 form a communication group. Terminal device 410 is the central control node of the communication group, and terminal devices 420 and 430 are group members. Terminal device 410 can allocate sideline transmission resources to terminal devices 420 and 430.

[0058] Device-to-device communication (D2D) is a sidelink (SL) transmission technology based on D2D. Unlike traditional cellular systems, where communication data is sent or received by network devices, D2D communication offers higher spectrum efficiency and lower transmission latency. For example, connected vehicle systems can use D2D communication. Currently, the 3rd Generation Partnership Project (3GPP) defines two transmission modes for D2D communication: Mode 1 and Mode 2.

[0059] Mode 1: The network device allocates transmission resources to the terminal device, and the terminal device transmits data on the sidelink based on the allocated resources. The network device can allocate resources for single transmissions or semi-static transmissions. For example, as shown in Figure 1, the terminal device is within the network coverage area, and the network device allocates transmission resources for sidelink transmissions.

[0060] Second mode: The terminal device selects a resource from the resource pool for data transmission. For example, as shown in Figure 3, if the terminal device is outside the network coverage area, the terminal device can autonomously select a transmission resource from the pre-configured resource pool for sideways transmission. Alternatively, as shown in Figure 1, the terminal device can autonomously select a transmission resource from the network-configured resource pool for sideways transmission.

[0061] New Radio Vehicle to Everything (NR-V2X) is a sidelink transmission technology used for vehicular wireless communications. NR-V2X supports unicast, multicast, and broadcast transmission modes. For unicast transmission, there is only one receiving terminal. As shown in Figure 5, unicast transmission is performed between terminal device 510 and terminal device 520. For multicast transmission, the receiving terminals are all terminal devices in a communication group, or all terminal devices within a certain transmission distance. As shown in Figure 6, terminal devices 610, 620, 630, and 640 form a communication group, where terminal device 610 transmits data, and the other terminal devices in the communication group are all receiving terminal devices. For broadcast transmission, the receiving terminal is any terminal around the transmitting terminal device. As shown in Figure 7, terminal device 710 is the transmitting terminal device, and terminal devices 720-760 are all receiving terminal devices around terminal device 710. Terminal device 710 can send data to terminal devices 720-760.

[0062] The time slot structure in NR-V2X can be shown in Figure 8. Part (a) of Figure 8 shows the time slot structure without the physical sidelink feedback channel (PSFCH) in the time slot; Part (b) of Figure 8 shows the time slot structure including the PSFCH.

[0063] As shown in Figure 8, the physical sidelink control channel (PSCCH) in NR-V2X starts from the second sidelink symbol of the time slot in the time domain, occupies 2 or 3 orthogonal frequency division multiplexing (OFDM) symbols, and can occupy {10, 12 15, 20, 25} physical resource blocks (PRBs) in the frequency domain. In order to reduce the complexity of UE's blind detection of PSCCH, only one number of PSCCH symbols and PRBs can be configured in a resource pool. In addition, because the subchannel is the minimum granularity of physical sidelink shared channel (PSSCH) resource allocation in NR-V2X, the number of PRBs occupied by PSCCH can be less than or equal to the number of PRBs contained in a subchannel in the resource pool, so as to avoid additional restrictions on PSSCH resource selection or allocation. As shown in part (a) of Figure 8, the PSSCH also begins in the time domain with the second sidelink symbol of the timeslot. The last time-domain symbol in the timeslot is the guard period (GP) symbol, and the remaining symbols are mapped to the PSSCH. The first sidelink symbol in the timeslot is a repetition of the second sidelink symbol. The receiving terminal typically uses the first sidelink symbol as an automatic gain control (AGC) symbol; the data on this symbol is not typically used for data demodulation. The PSSCH can occupy K subchannels in the frequency domain, each of which can include M consecutive PRBs, where K and M are integers.

[0064] As shown in part (b) of FIG8 , when a time slot contains a PSFCH channel, the second to last and third to last symbols in the time slot are used for PSFCH channel transmission, and a time domain symbol before the PSFCH channel is used as a GP symbol.

[0065] In NR-V2X, the PSSCH is used to carry second-order sidelink control information (SCI) (such as SCI 2-A or SCI 2-B, see the subsequent description for details) and data information. The second-order SCI uses Polar coding and fixed quadrature phase shift keying (QPSK) modulation. The data portion of the PSSCH uses low-density parity check (LDPC) code, and the highest modulation order supported is 256 quadrature amplitude modulation (QAM).

[0066] In NR-V2X, PSSCH supports up to two stream transmissions and uses a unit precoding matrix to map data on two layers to two antenna ports. At most, only one transport block (TB) can be sent in a PSSCH. However, unlike the transmission method of the PSSCH data portion, when PSSCH adopts a dual-stream transmission method, the modulation symbols sent by the second-order SCI on both streams are exactly the same. This design can ensure the reception performance of the second-order SCI in highly correlated channels.

[0067] Since the maximum number of retransmissions of a PSSCH in NR-V2X is 32, if there are PSFCH resources in the resource pool and the configuration period of PSFCH resources is 2 or 4, the OFDM symbols available in the time slot where different transmissions of a PSSCH are located may change, as shown in Figure 9. If calculated based on the actual number of OFDM symbols in a time slot ( The reference value of the number of symbols occupied by PSSCH) may be different due to the number of symbols available for PSSCH transmission in a time slot. SCI2 Different, and Q′ SCI2 The change of will lead to the change of the size of the TB carried by PSSCH, as described below. In order to ensure that the transmission block size (TBS) remains unchanged during multiple transmissions of PSSCH, The actual number of PSFCH symbols is not used. The number of resource elements (REs) occupied by the PSSCH demodulation reference signal (DMRS) and the number of REs occupied by the phase tracking reference signal (PT-RS), which may change during retransmission, are not taken into account. In Figure 9, n and l are integers.

[0068] The code rate of the second-order SCI can be dynamically adjusted within a certain range. The specific code rate used is indicated by the first-order SCI, so the receiver does not need to perform blind detection of the second-order SCI even after the code rate changes. The modulation symbols of the second-order SCI are mapped in the frequency domain first and then in the time domain, starting from the symbol containing the first PSSCH DMRS. In the OFDM symbol containing the DMRS, the second-order SCI is mapped to the REs not occupied by the DMRS, as shown in Figure 10.

[0069] The data portion of the PSSCH within a resource pool can use multiple different modulation and coding scheme (MCS) tables, including the conventional 64QAM MCS table, the 256QAM MCS table, and the low-spectrum-efficiency 64QAM MCS table. The specific MCS table used in a transmission is indicated by the "MCS table indicator" field in the first-order SCI. To control the peak-to-average power ratio (PAPR), the PSSCH must be transmitted using contiguous PRBs. Since the subchannel is the minimum frequency-domain resource granularity of the PSSCH, this requires that the PSSCH must occupy contiguous subchannels.

[0070] PSSCH follows the NR PDSCH and PUSCH transport block size (TBS) determination mechanism, that is, the TBS is determined based on the reference value of the number of REs used for PSSCH in the time slot where PSSCH is located, so that the actual code rate is as close to the target code rate as possible. The purpose of using the reference value of the number of REs instead of the actual number of REs here is to ensure that the number of REs used to determine the TBS remains unchanged during the PSSCH retransmission process, so that the determined TBS size is the same. To achieve this goal, the reference value N of the number of REs occupied by PSSCH in the TBS determination process is used. RE Determine according to the following formula (1):

[0071]

[0072] Among them, n PRB is the number of PRBs occupied by PSSCH, is the number of REs occupied by the first-order SCI (including the REs occupied by the DMRS of the PSCCH), is the number of REs occupied by the second-order SCI, N′ RE Indicates the number of reference REs that can be used for PSSCH in a PRB. N' RE It can be determined by the following formula (2):

[0073]

[0074] in: Indicates the number of subcarriers in a PRB; Indicates the number of symbols available for sidelink in a time slot, excluding the last GP symbol and the first symbol used for AGC; or 3, the specific value is indicated by the "PSFCH symbol number" field in the first-order SCI, which is the reference value of the number of symbols occupied by PSFCH; The value of is configured by the RRC layer parameters and is used to indicate the reference value of the number of REs occupied by PT-RS and channel state information reference signal (CSI-RS); It represents the average number of DMRS REs in a time slot and is related to the DMRS pattern allowed in the resource pool. The corresponding relationship can be shown in the following Table 1.

[0075] Table 1 DMRS patterns allowed in the resource pool and The corresponding relationship

[0076]

[0077] In NR-V2X, the DMRS pattern of the PSCCH is the same as that of the NR physical downlink control channel (PDCCH). That is, the DMRS is present in each OFDM symbol of the PSCCH and is located in the frequency domain at {#1, #5, #9} REs of a PRB, as shown in Figure 11. The DMRS sequence of the PSCCH is generated by the following formula (3):

[0078]

[0079] Among them, the pseudo-random sequence c(m) is given by Initialize, where l is the index of the OFDM symbol where the DMRS is located in the time slot, is the index of the time slot where the DMRS is located in the system frame, Indicates the number of OFDM symbols in a time slot, NID ∈{0,1,…,65535}, in a resource pool N ID The specific value is configured or pre-configured by the network.

[0080] NR-V2X draws on the design of the NR Uu interface and adopts multiple time-domain PSSCH DMRS patterns. Within a resource pool, the number of available DMRS patterns is related to the number of PSSCH symbols in the resource pool. For a specific number of PSSCH symbols (including the first AGC symbol) and PSCCH symbols, the available DMRS patterns and the position of each DMRS symbol within the pattern are shown in Table 2 below. Figure 12 shows a schematic diagram of the time-domain position of four DMRS symbols when the PSSCH has 13 symbols.

[0081] Table 2 Number and position of DMRS symbols under different PSSCH and PSCCH symbol numbers

[0082]

[0083] If multiple time-domain DMRS patterns are configured within the resource pool, the transmitting UE selects the specific time-domain DMRS pattern to use and indicates this in the first-order SCI. This design allows high-speed UEs to select a high-density DMRS pattern, thereby ensuring accurate channel estimation, while low-speed UEs can use a low-density DMRS pattern, thereby improving spectrum efficiency.

[0084] The generation method of the PSSCH DMRS sequence is almost identical to that of the PSCCH DMRS sequence. The only difference is the initialization formula c(m) of the pseudo-random sequence. init middle, p i The i-th CRC bit of the PSCCH that schedules the PSSCH, where L=24 is the number of bits of the PSCCH CRC.

[0085] NR PDSCH and PUSCH support two frequency domain DMRS patterns, namely DMRS frequency domain type 1 and DMRS frequency domain type 2. For each frequency domain type, there are two different types: single DMRS symbol and double DMRS symbol. Single symbol DMRS frequency domain type 1 supports 4 DMRS ports, single symbol DMRS frequency domain type 2 can support 6 DMRS ports, and in the case of double DMRS symbols, the number of supported ports is doubled. However, in NR-V2X, since PSSCH only needs to support a maximum of two DMRS ports, only single symbol DMRS frequency domain type 1 is supported, as shown in Figure 13.

[0086] To better support unicast communication, NR-V2X supports SL CSI-RS. SL CSI-RS is only sent when the following three conditions are met:

[0087] (1) The UE sends the corresponding PSSCH, that is, the UE cannot only send SL CSI-RS;

[0088] (2) Sidelink CSI reporting is activated by higher-layer signaling;

[0089] (3) When sidelink CSI reporting is activated by higher layer signaling, the corresponding bit in the second-order SCI sent by the UE triggers sidelink CSI reporting.

[0090] The maximum number of ports supported by SL CSI-RS is two. For two ports, SL CSI-RSs from different ports are code-division multiplexed across two adjacent REs in the same OFDM symbol. Within a PRB, the number of SL CSI-RSs per port is one, meaning the density is one. Therefore, within a PRB, SL CSI-RSs appear in at most one OFDM symbol. The specific location of this OFDM symbol is determined by the transmitting terminal. To avoid impacting the resource mapping of the PSCCH and second-order SCI, SL CSI-RSs cannot be located in the same OFDM symbol as the PSCCH and second-order SCIs. Because the channel estimation accuracy of the OFDM symbol where the PSSCH DMRS resides is higher, and the SL CSI-RSs for two ports occupy two consecutive REs in the frequency domain, SL CSI-RSs cannot be transmitted in the same OFDM symbol as the PSSCH DMRS. The OFDM symbol location of the SL CSI-RS is indicated by the sl-CSI-RS-FirstSymbol parameter in the PC5RRC protocol.

[0091] The position of the first RE occupied by the SL CSI-RS in a PRB is indicated by the sl-CSI-RS-FreqAllocation parameter in PC5RRC. If the SL CSI-RS is a single port, this parameter is a bitmap of length 12, corresponding to the 12 REs in a PRB. If the SL CSI-RS is a dual port, this parameter is a bitmap of length 6. In this case, the SL CSI-RS occupies two REs, 2f(1) and 2f(1)+1, where f(1) represents the index of the bit with a value of 1 in the bitmap. The frequency domain position of the SL CSI-RS is also determined by the transmitting terminal, but the determined frequency domain position of the SL CSI-RS cannot conflict with the PT-RS. FIG14 shows a schematic diagram of the time-frequency position of the SL CSI-RS. In FIG14 , the number of SL CSI-RS ports is 2, the sl-CSI-RS-FirstSymbol is 8, and the sl-CSI-RS-FreqAllocation is [b5, b4, b3, b2, b1, b0] = [0, 0, 0, 1, 0, 0].

[0092] The NR system, introduced in 3GPP Release 15 (R15), is a communications technology designed for use in existing and newly licensed spectrum. The NR system enables seamless cellular network coverage, high spectral efficiency, high peak rates, and high reliability. In LTE, unlicensed spectrum (or unlicensed spectrum) has been implemented as a supplementary frequency band to the licensed spectrum for cellular networks.

[0093] Similarly, NR systems can also use unlicensed spectrum as part of 5G cellular network technology to provide services to users. In the 3GPP R16 standard, the NR system for unlicensed spectrum was discussed, called 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, and the unlicensed spectrum is used as a secondary carrier; the latter can independently network through the unlicensed spectrum, and the UE can directly access the network through the unlicensed spectrum. The range of unlicensed spectrum used by the NR-U system introduced in 3GPP R16 is concentrated in the 5GHz and 6GHz frequency bands, for example, 5925–7125MHz in the United States, or 5925–6425MHz in Europe. In the R16 standard, band 46 (5150MHz-5925MHz) is also newly defined for use as an unlicensed spectrum.

[0095] Unlicensed spectrum is spectrum designated by countries and regions for use by radio equipment. This spectrum is generally considered shared spectrum, meaning that as long as communications devices meet national or regional regulatory requirements for that spectrum, they can use it without having to apply for exclusive spectrum authorization from the national or regional spectrum management agency. Because the use of unlicensed spectrum must comply with specific national and regional regulations, such as the "listen before talk" (LBT) principle, NR technology requires corresponding enhancements to meet regulatory requirements for unlicensed frequency bands and efficiently utilize unlicensed spectrum to provide services. The 3GPP Release 16 standard primarily standardizes NR-U technology in the following areas: channel sensing; initial access; control channel design; HARQ and scheduling; and scheduling-free grant transmission. This chapter provides a detailed introduction to these technologies.

[0096] 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 (Type1) channel access method and type 2 (Type2) channel access method. The Type1 channel access method is a multi-slot channel detection with random backoff based on the adjustment of the contention window size, 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. The Type2 channel access method is a channel access method based on a fixed-length monitoring time slot, wherein the Type2 channel access method includes Type2A channel access, Type2B channel access and Type2C channel access. The Type1 channel access method is mainly used for communication equipment to initiate channel occupancy, and the Type2 channel access method is mainly used for communication equipment to share channel occupancy.

[0097] A special case that needs to be explained is that when the base station initiates channel occupancy for the transmission of the SS / PBCH block in the discovery reference symbol (DRS) and the DRS window does not include unicast data transmission of the UE, if the length of the DRS window does not exceed 1ms and the duty cycle of the DRS window transmission does not exceed 1 / 20, then the base station can use Type2A channel access to initiate channel occupancy.

[0098] FIG15 shows an example 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.

[0099] The default channel access mode on the base station side is Type 1 channel access. 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 3 below. 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 for the base station to use the channel for transmission cannot exceed T mcot,p .

[0100] Table 3 Channel access parameters corresponding to different channel priorities

[0101]

[0102] Among them, in the above Table 1, m p Indicates the number of fallback slots corresponding to the channel access priority, CW p Indicates the size of the contention window corresponding to the channel access priority, CW min,p Indicates the CW corresponding to the channel access priority p Minimum value, CW max,p Indicates the CW corresponding to the channel access priority p The maximum value, T mcot,p Indicates the maximum channel occupancy time corresponding to the channel access priority.

[0103] When the base station initiates the channel occupying time (COT), in addition to using the resources in the COT for downlink transmission, the resources in the COT can also be shared with the UE for uplink transmission. When the resources in the COT are shared with the UE for uplink transmission, the channel access method that the UE can use is Type 2A channel access, Type 2B channel access or Type 2C channel access, among which 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. Type 2 channel access is channel detection based on fixed-length channel monitoring time slots. Type 2 channel access can include the following:

[0104] Type 2A channel access: The terminal device uses a 25μs single-slot channel detection method. Specifically, in Type 2A channel access, the terminal device can monitor the channel for 25μs before starting transmission and transmit data after the channel detection is successful.

[0105] Type 2B channel access: The terminal device uses a 16μs single-slot channel detection method. Specifically, in Type 2B channel access, the terminal device can monitor the channel for 16μs before starting transmission and transmit after the channel is successfully detected. The interval between the start position of each transmission and the end position of the previous transmission is 16μs.

[0106] Type 2C channel access: The terminal device transmits after the gap ends without performing channel detection. Specifically, under Type 2C channel access, the terminal device can directly transmit, where the gap between the start position of the transmission and the end position of the previous transmission is less than or equal to 16μs. The transmission length does not exceed 584μs.

[0107] The existing side communication technology does not consider / support the sharing of bandwidth part (BWP) or resource pool between UEs of different capabilities and versions. In future versions of the (communication protocol), whether it is a licensed frequency band, a dedicated frequency band (such as an intelligent traffic system (ITS)), or unlicensed frequency band resources, if there are UEs of different versions and different capabilities, these UEs can support different bandwidths. If they share the same BWP or resource pool for communication, it may cause performance impact on terminals with weak capabilities. The system cannot guarantee that UEs of new and old versions have the same communication capabilities. Therefore, when configuring BWP and / or resource pools, it is necessary to divide the BWP / resource pools according to different versions and capabilities, which is more conducive to improving resource utilization efficiency.

[0108] In order to solve one or more of the above technical problems, the present application proposes a communication method and a communication device. For example, when there are UEs of different versions or UEs of different capabilities in the system, the network can configure a first BWP for the old version UE (or UE with weak capabilities), and the network can also configure a first BWP for the new version UE; optionally, a second BWP can be configured for the new version UE (or UE with strong capabilities), so that the resource pools belonging to different BWPs can avoid overlapping of frequency domain resources, wherein the old version UE (or UE with weak capabilities) can refer to the UE corresponding to the earlier version of the communication protocol, and the new version UE (or UE with strong capabilities) can refer to the UE corresponding to the newer version of the communication protocol. For another example, there can be a corresponding relationship between the resource pool and the frequency domain bandwidth size. The network can configure a resource pool corresponding to a larger frequency domain bandwidth for a UE with strong capabilities, and the network can configure a resource pool corresponding to a smaller frequency domain bandwidth for a UE with weak capabilities; optionally, the network can configure a resource pool corresponding to any or all adaptive frequency domain bandwidths within the capability range of the UE with strong capabilities.

[0109] The embodiments of the present application are described in detail below with reference to Figures 16 to 22.

[0110] Figure 16 is a schematic flow chart of a communication method according to an embodiment of the present application. The method 1600 shown in Figure 16 may include steps S1610 and S1620, as follows:

[0111] S1610: The network device configures a first bandwidth portion or a first resource pool for a side link for a first terminal device.

[0112] The first bandwidth portion may include one or more bandwidth portions. Each bandwidth portion (of the one or more bandwidth portions) may include one or more resource pools.

[0113] The first resource pool may include one or more resource pools. Optionally, the first resource pool may be a default resource pool.

[0114] It should be understood that the network device configuring the first bandwidth portion for the first terminal device also includes configuring the resource pool included in the first bandwidth portion for the first terminal device. Similarly, the first terminal device using the first bandwidth portion also includes the first terminal device using the resource pool included in the first bandwidth portion.

[0115] The first bandwidth part or the first resource pool may include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

[0116] The first terminal device can use the first bandwidth part or the first resource pool to send or receive sidelink information.

[0117] S1620: The network device configures the first bandwidth portion and / or the second bandwidth portion, or the first resource pool and / or the second resource pool for the side link for the second terminal device.

[0118] The second bandwidth portion may include one or more bandwidth portions. Each bandwidth portion (of the one or more bandwidth portions) may include one or more resource pools.

[0119] The second resource pool may include one or more resource pools.

[0120] It should be understood that the network device configuring the second bandwidth portion for the second terminal device also includes configuring the resource pool included in the second bandwidth portion for the second terminal device. Similarly, the second terminal device using the second bandwidth portion also includes the second terminal device using the resource pool included in the second bandwidth portion.

[0121] The second bandwidth part or the second resource pool may include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

[0122] The bandwidth supported by the second terminal device may be different from the bandwidth supported by the first terminal device. For example, the bandwidth supported by the first terminal device may be smaller, and the bandwidth supported by the second terminal device may be larger.

[0123] Optionally, compared to the second terminal device, the first terminal device may refer to a UE of an older version or with weaker capabilities; compared to the first terminal device, the second terminal device may refer to a UE of a newer version or with stronger capabilities. For example, the first terminal device may be at least one of the following: a UE supporting the sidelink feature of communication protocol version 18 (Rel-18) (e.g., the Rel-18 sidelink feature may include features for communicating on licensed frequency bands and / or communicating on unlicensed frequency bands), a UE supporting the Rel-17 sidelink feature, and a UE supporting the Rel-16 sidelink feature; the second terminal device may be at least one of the following: a UE supporting the Rel-19 sidelink feature, and a UE supporting the Rel-20 and / or Rel-20 or higher sidelink feature.

[0124] The second terminal device can use the first bandwidth portion and / or the second bandwidth portion, or the first resource pool and / or the second resource pool to send or receive sideline information. For example, the second terminal device can use the first bandwidth portion or the first resource pool to perform sideline transmission with the first terminal device.

[0125] In the embodiments of the present application, when configuring bandwidth portions and / or resource pools, the bandwidth portions and / or resource pools are divided according to different UE versions and / or capabilities. This not only improves resource utilization efficiency but also enables the system to simultaneously support communication between UEs of different versions and capabilities on the sidelink. Furthermore, the compatibility of the sidelink system can be improved, thereby supporting more types of products in future commercial applications.

[0126] The relationships between bandwidth parts and resource pools are described in detail below with reference to the accompanying drawings. For ease of description, in the following drawings, BWP_1 represents the first bandwidth part and BWP_2 represents the second bandwidth part.

[0127] In some embodiments, the first bandwidth portion and the second bandwidth portion may not overlap in the frequency domain. Alternatively, any resource pool in the first bandwidth portion may not overlap in the frequency domain with any resource pool in the second bandwidth portion. For example, as shown in Figure 17 , BWP_1 and BWP_2 do not overlap in frequency domain resources. BWP_1 is configured with resource pools 1 and 2, and BWP_2 is configured with resource pools 3, 4, and 5. Resource pools 1 and 2 do not overlap with resource pools 3, 4, and 5.

[0128] Optionally, the second bandwidth portion may contain the first bandwidth portion.

[0129] In some embodiments, any resource pool in the first bandwidth portion may not overlap with any resource pool in the second bandwidth portion in the frequency domain. For example, as shown in FIG18 , BWP_2 includes BWP_1, but the resource pools configured in BWP_1 do not overlap with the resource pools configured in BWP_2 in the frequency domain.

[0130] In some embodiments, the second bandwidth portion may partially overlap with the first bandwidth portion in the frequency domain.

[0131] Optionally, any resource pool in the first bandwidth part may not overlap with any resource pool in the second bandwidth part in the frequency domain. For example, as shown in Figure 19, BWP_1 and BWP_2 overlap in frequency domain resources, but the resource pools configured in BWP_1 do not overlap with the resource pools configured in BWP_2 in the frequency domain.

[0132] Optionally, some resources in at least one resource pool in the first bandwidth portion may be resources that overlap in the frequency domain between the second bandwidth portion and the first bandwidth portion. For example, as shown in Figure 20 , BWP_1 and BWP_2 overlap in frequency domain resources, and the resource pools configured within BWP_1 and the resource pools configured within BWP_2 do not overlap in frequency domain resources. However, resource pool 2 within BWP_1 includes a portion of the frequency domain resource overlap between BWP_1 and BWP_2, and resource pool 3 within BWP_1 also includes a portion of the frequency domain resource overlap between BWP_1 and BWP_2.

[0133] Optionally, all resources in at least one resource pool in the first bandwidth portion may be resources that overlap in the frequency domain between the second bandwidth portion and the first bandwidth portion. For example, as shown in Figure 21 , BWP_1 and BWP_2 overlap in frequency domain resources, the resource pools configured in BWP_1 do not overlap in frequency domain resources with the resource pools configured in BWP_2, and both BWP_1 and BWP_2 contain resource pool 3.

[0134] In some embodiments, the frequency domain bandwidth of the second resource pool may be greater than the frequency domain bandwidth of the first resource pool. For example, as shown in Figure 22, the frequency domain bandwidth of resource pool 2 may be greater than the frequency domain bandwidth of resource pool 1. Resource pool 1 in Figure 22 may be the default resource pool.

[0135] In some embodiments, the network device may further configure a third resource pool for the second terminal device. The second terminal device may use the third resource pool to send or receive sidelink information. The third resource pool may include one or more resource pools.

[0136] Optionally, the frequency domain bandwidth of the third resource pool may be smaller than the frequency domain bandwidth of the first resource pool. For example, as shown in FIG22 , the frequency domain bandwidth of resource pool 3 may be smaller than the frequency domain bandwidth of resource pool 1.

[0137] In some embodiments, the resource pools may be associated with frequency domain bandwidths. Alternatively, different resource pools may be associated with or correspond to different frequency domain bandwidths.

[0138] Optionally, each frequency domain bandwidth may be associated with one or more resource pools. For example, a resource pool may correspond one-to-one with a frequency domain bandwidth, or multiple resource pools may correspond to one frequency domain bandwidth.

[0139] For example, the first resource pool RP_1 may correspond to bandwidth BW_1, and the second resource pool RP_2 may correspond to bandwidth BW_2; or, multiple resource pools (eg, the third resource pool RP_3 and the fourth resource pool RP_4) may correspond to bandwidth BW_3.

[0140] Optionally, if the terminal device supports a certain bandwidth, the network device may configure resources corresponding to the bandwidth for the terminal device. For example, assuming that the first resource pool RP_1 corresponds to bandwidth BW_1, when a UE can support bandwidth BW_1, the network device configures resource pool RP_1 for the UE.

[0141] In some embodiments, an association relationship (or correspondence relationship) between a resource pool and a frequency domain bandwidth may be configured in the network device.

[0142] In some embodiments, the network device may configure a first resource pool for the first terminal device based on the association relationship and the maximum bandwidth capability of the first terminal device. Optionally, the frequency domain bandwidth associated with the first resource pool may be less than or equal to the maximum bandwidth capability of the first terminal device.

[0143] In an embodiment of the present application, the network device configures the first bandwidth part or the first resource pool for the side link for the first terminal device, and the network device configures the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for the side link for the second terminal device, which facilitates sharing of bandwidth parts and / or resource pools between terminal devices of different capabilities and different versions.

[0144] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 22. The device embodiment of the present application is described in detail below in conjunction with Figures 23 to 25. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0145] FIG23 is a schematic structural diagram of a communication device provided in an embodiment of the present application. As shown in FIG23 , the device 2300 includes a configuration unit 2310, which is as follows:

[0146] The configuration unit 2310 is configured to configure a first bandwidth portion or a first resource pool for a sidelink for a first terminal device;

[0147] The configuration unit 2310 is used to configure the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for the side link for the second terminal device, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the first terminal device.

[0148] Optionally, the first bandwidth part and the second bandwidth part do not overlap in the frequency domain.

[0149] Optionally, the second bandwidth portion includes the first bandwidth portion.

[0150] Optionally, the second bandwidth part partially overlaps with the first bandwidth part in the frequency domain.

[0151] Optionally, part of the resources in at least one resource pool in the first bandwidth part are resources that overlap with the first bandwidth part in the frequency domain.

[0152] Optionally, all resources in at least one resource pool in the first bandwidth part are resources that overlap with the first bandwidth part in the frequency domain.

[0153] Optionally, any resource pool in the first bandwidth part and any resource pool in the second bandwidth part do not overlap in the frequency domain.

[0154] Optionally, the first bandwidth part and the second bandwidth part include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

[0155] Optionally, the frequency domain bandwidth of the second resource pool is greater than the frequency domain bandwidth of the first resource pool.

[0156] Optionally, the configuration unit 2310 is further used to: configure a third resource pool for the second terminal device, where the frequency domain bandwidth of the third resource pool is smaller than the frequency domain bandwidth of the first resource pool.

[0157] Optionally, the device is configured with an association relationship between the resource pool and the frequency domain bandwidth; wherein, the configuration unit 2310 is specifically used to: configure the first resource pool for the first terminal device based on the association relationship and the maximum bandwidth capability of the first terminal device, and the frequency domain bandwidth associated with the first resource pool is less than or equal to the maximum bandwidth capability of the first terminal device.

[0158] Optionally, each frequency domain bandwidth in the device is associated with one or more resource pools.

[0159] Optionally, the first resource pool and the second resource pool contain resources in a licensed frequency band, resources in an exclusive frequency band, or resources in an unlicensed frequency band.

[0160] Figure 24 is a schematic structural diagram of a communication device provided in an embodiment of the present application. The communication device 2400 in Figure 24 includes a transmission unit 2410, which is specifically as follows:

[0161] The transmission unit 2410 is used for sidelink transmission with a second terminal device through a first bandwidth part or a first resource pool, wherein the device is configured with the first bandwidth part or the first resource pool for the side link, the second terminal device is configured with the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for the side link, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the device.

[0162] Optionally, the first bandwidth part and the second bandwidth part do not overlap in the frequency domain.

[0163] Optionally, the second bandwidth portion includes the first bandwidth portion.

[0164] Optionally, the second bandwidth part partially overlaps with the first bandwidth part in the frequency domain.

[0165] Optionally, part of the resources in at least one resource pool in the first bandwidth part are resources that overlap with the first bandwidth part in the frequency domain.

[0166] Optionally, all resources in at least one resource pool in the first bandwidth part are resources that overlap with the first bandwidth part in the frequency domain.

[0167] Optionally, any resource pool in the first bandwidth part and any resource pool in the second bandwidth part do not overlap in the frequency domain.

[0168] Optionally, the first bandwidth part and the second bandwidth part include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

[0169] Optionally, the frequency domain bandwidth of the second resource pool is greater than the frequency domain bandwidth of the first resource pool.

[0170] Optionally, the second terminal device is configured with a third resource pool, and the frequency domain bandwidth of the third resource pool is smaller than the frequency domain bandwidth of the first resource pool.

[0171] Optionally, the frequency domain bandwidth associated with the first resource pool is less than or equal to the maximum bandwidth capability of the device.

[0172] Optionally, each frequency domain bandwidth in the network device is associated with one or more resource pools.

[0173] Optionally, the first resource pool and the second resource pool contain resources in a licensed frequency band, resources in an exclusive frequency band, or resources in an unlicensed frequency band.

[0174] Figure 25 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dashed lines in Figure 25 indicate that the unit or module is optional. Apparatus 2500 may be used to implement the method described in the above method embodiment. Apparatus 2500 may be a chip or a communication device.

[0175] The device 2500 may include one or more processors 2510. The processor 2510 may support the device 2500 to implement the method described in the method embodiment above. The processor 2510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0176] The apparatus 2500 may further include one or more memories 2520. The memories 2520 store programs that can be executed by the processor 2510, causing the processor 2510 to perform the methods described in the above method embodiments. The memories 2520 may be independent of the processor 2510 or integrated into the processor 2510.

[0177] The apparatus 2500 may further include a transceiver 2530. The processor 2510 may communicate with other devices or chips via the transceiver 2530. For example, the processor 2510 may transmit and receive data with other devices or chips via the transceiver 2530.

[0178] The present invention also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the communication device provided in the present invention, and the program enables a computer to execute the method performed by the communication device in each embodiment of the present invention.

[0179] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the communication device provided in the present application, and the program causes a computer to execute the method performed by the communication device in each embodiment of the present application.

[0180] The embodiments of the present application also provide a computer program. The computer program can be applied to the communication device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the communication device in each embodiment of the present application.

[0181] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0182] It should be understood that the term "and / or" in this document simply describes a relationship 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 " / " in this document generally indicates that the related objects are in an "or" relationship.

[0183] 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.

[0184] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0185] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0186] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0187] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, 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 instructions are 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 device. The computer instructions 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 instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0188] 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 changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A communication method, characterized in that: include: The network device configures a first bandwidth portion or a first resource pool for a sidelink for the first terminal device; The network device configures the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for a side link for a second terminal device, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the first terminal device.

2. The method according to claim 1, characterized in that The first bandwidth part and the second bandwidth part do not overlap in the frequency domain.

3. The method according to claim 1, characterized in that The second bandwidth portion includes the first bandwidth portion.

4. The method according to claim 1, characterized in that: The second bandwidth portion partially overlaps with the first bandwidth portion in the frequency domain.

5. The method according to claim 4, characterized in that Part of the resources in at least one resource pool in the first bandwidth part are resources overlapping the second bandwidth part and the first bandwidth part in the frequency domain.

6. The method according to claim 4 or 5, characterized in that: All resources in at least one resource pool in the first bandwidth part are resources that overlap the second bandwidth part and the first bandwidth part in the frequency domain.

7. The method according to any one of claims 2 to 6, characterized in that Any resource pool in the first bandwidth part does not overlap with any resource pool in the second bandwidth part in the frequency domain.

8. The method according to any one of claims 1 to 7, characterized in that The first bandwidth part and the second bandwidth part include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

9. The method according to claim 1, characterized in that: The frequency domain bandwidth of the second resource pool is greater than the frequency domain bandwidth of the first resource pool.

10. The method according to claim 9, characterized in that The method further comprises: The network device configures a third resource pool for the second terminal device, and a frequency domain bandwidth of the third resource pool is smaller than a frequency domain bandwidth of the first resource pool.

11. The method according to claim 9 or 10, characterized in that: The network device is configured with an association relationship between a resource pool and a frequency domain bandwidth; The network device configuring the first frequency domain resource for the first terminal device includes: The network device configures the first resource pool for the first terminal device based on the association relationship and the maximum bandwidth capability of the first terminal device, and the frequency domain bandwidth associated with the first resource pool is less than or equal to the maximum bandwidth capability of the first terminal device.

12. The method according to claim 11, characterized in that Each frequency domain bandwidth in the network device is associated with one or more resource pools.

13. The method according to any one of claims 1 to 12, characterized in that The first resource pool and the second resource pool contain resources in a licensed frequency band, resources in an exclusive frequency band, or resources in an unlicensed frequency band.

14. A communication method, characterized in that: include: A first terminal device performs sidelink transmission with a second terminal device via a first bandwidth portion or a first resource pool, wherein the first terminal device is configured with the first bandwidth portion or the first resource pool for the sidelink, the second terminal device is configured with the first bandwidth portion and / or the second bandwidth portion, or the first resource pool and / or the second resource pool for the sidelink, and a bandwidth supported by the second terminal device is different from a bandwidth supported by the first terminal device.

15. The method according to claim 14, characterized in that The first bandwidth part and the second bandwidth part do not overlap in the frequency domain.

16. The method according to claim 14, characterized in that The second bandwidth portion includes the first bandwidth portion.

17. The method according to claim 14, characterized in that The second bandwidth portion partially overlaps with the first bandwidth portion in the frequency domain.

18. The method according to claim 17, characterized in that Part of the resources in at least one resource pool in the first bandwidth part are resources overlapping the second bandwidth part and the first bandwidth part in the frequency domain.

19. The method according to claim 17 or 18, characterized in that All resources in at least one resource pool in the first bandwidth part are resources that overlap the second bandwidth part and the first bandwidth part in the frequency domain.

20. The method according to any one of claims 15 to 19, characterized in that Any resource pool in the first bandwidth part does not overlap with any resource pool in the second bandwidth part in the frequency domain.

21. The method according to any one of claims 14 to 20, characterized in that The first bandwidth part and the second bandwidth part include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

22. The method according to claim 14, characterized in that The frequency domain bandwidth of the second resource pool is greater than the frequency domain bandwidth of the first resource pool.

23. The method according to claim 22, characterized in that The second terminal device is configured with a third resource pool, and the frequency domain bandwidth of the third resource pool is smaller than the frequency domain bandwidth of the first resource pool.

24. The method according to claim 22 or 23, characterized in that The frequency domain bandwidth associated with the first resource pool is less than or equal to the maximum bandwidth capability of the first terminal device.

25. The method according to claim 24, characterized in that Each frequency domain bandwidth in the network device is associated with one or more resource pools.

26. The method according to any one of claims 14 to 25, characterized in that The first resource pool and the second resource pool contain resources in a licensed frequency band, resources in an exclusive frequency band, or resources in an unlicensed frequency band.

27. A communication device, characterized in that: include: A configuration unit, configured to configure a first bandwidth portion or a first resource pool for a sidelink for a first terminal device; The configuration unit is used to configure the first bandwidth part and / or the second bandwidth part, or the first resource pool and / or the second resource pool for the side link for a second terminal device, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the first terminal device.

28. The device according to claim 27, characterized in that The first bandwidth part and the second bandwidth part do not overlap in the frequency domain.

29. The device according to claim 27, characterized in that The second bandwidth portion includes the first bandwidth portion.

30. The device according to claim 27, characterized in that The second bandwidth portion partially overlaps with the first bandwidth portion in the frequency domain.

31. The device according to claim 30, characterized in that Part of the resources in at least one resource pool in the first bandwidth part are resources overlapping the second bandwidth part and the first bandwidth part in the frequency domain.

32. The device according to claim 30 or 31, characterized in that All resources in at least one resource pool in the first bandwidth part are resources that overlap the second bandwidth part and the first bandwidth part in the frequency domain.

33. The device according to any one of claims 28 to 32, characterized in that Any resource pool in the first bandwidth part does not overlap with any resource pool in the second bandwidth part in the frequency domain.

34. The device according to any one of claims 27 to 33, characterized in that The first bandwidth part and the second bandwidth part include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

35. The device according to claim 27, characterized in that The frequency domain bandwidth of the second resource pool is greater than the frequency domain bandwidth of the first resource pool.

36. The device according to claim 35, characterized in that The configuration unit is further used to configure a third resource pool for the second terminal device, wherein a frequency domain bandwidth of the third resource pool is smaller than a frequency domain bandwidth of the first resource pool.

37. The device according to claim 35 or 36, characterized in that The device is configured with an association relationship between the resource pool and the frequency domain bandwidth; wherein the configuration unit is specifically used to: configure the first resource pool for the first terminal device based on the association relationship and the maximum bandwidth capability of the first terminal device, and the frequency domain bandwidth associated with the first resource pool is less than or equal to the maximum bandwidth capability of the first terminal device.

38. The device according to claim 37, characterized in that Each frequency domain bandwidth in the device is associated with one or more resource pools.

39. The device according to any one of claims 27 to 38, characterized in that The first resource pool and the second resource pool contain resources in a licensed frequency band, resources in an exclusive frequency band, or resources in an unlicensed frequency band.

40. A communication device, characterized in that: include: A transmission unit, used for performing sidelink transmission with a second terminal device via a first bandwidth portion or a first resource pool, wherein the device is configured with the first bandwidth portion or the first resource pool for the sidelink, the second terminal device is configured with the first bandwidth portion and / or the second bandwidth portion, or the first resource pool and / or the second resource pool for the sidelink, and the bandwidth supported by the second terminal device is different from the bandwidth supported by the device.

41. The device according to claim 40, characterized in that The first bandwidth part and the second bandwidth part do not overlap in the frequency domain.

42. The device according to claim 40, characterized in that The second bandwidth portion includes the first bandwidth portion.

43. The device according to claim 40, characterized in that The second bandwidth portion partially overlaps with the first bandwidth portion in the frequency domain.

44. The device according to claim 43, characterized in that Part of the resources in at least one resource pool in the first bandwidth part are resources overlapping the second bandwidth part and the first bandwidth part in the frequency domain.

45. The device according to claim 43 or 44, characterized in that All resources in at least one resource pool in the first bandwidth part are resources that overlap the second bandwidth part and the first bandwidth part in the frequency domain.

46. ​​The device according to any one of claims 41 to 45, characterized in that Any resource pool in the first bandwidth part does not overlap with any resource pool in the second bandwidth part in the frequency domain.

47. The device according to any one of claims 40 to 46, characterized in that The first bandwidth part and the second bandwidth part include resources of a licensed frequency band, resources of an exclusive frequency band, or resources of an unlicensed frequency band.

48. The device according to claim 40, characterized in that The frequency domain bandwidth of the second resource pool is greater than the frequency domain bandwidth of the first resource pool.

49. The device according to claim 48, characterized in that The second terminal device is configured with a third resource pool, and the frequency domain bandwidth of the third resource pool is smaller than the frequency domain bandwidth of the first resource pool.

50. The device according to claim 48 or 49, characterized in that The frequency domain bandwidth associated with the first resource pool is less than or equal to the maximum bandwidth capability of the device.

51. The device according to claim 50, characterized in that Each frequency domain bandwidth in the network device is associated with one or more resource pools.

52. The device according to any one of claims 40 to 51, characterized in that The first resource pool and the second resource pool contain resources in a licensed frequency band, resources in an exclusive frequency band, or resources in an unlicensed frequency band.

53. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 1 to 13.

54. A communication device, characterized in that: It includes a memory, a transceiver and a processor, the memory is used to store programs, the processor sends and receives data through the transceiver, and the processor is used to call the program in the memory so that the communication device executes the method as described in any one of claims 14 to 26.

55. A communication device, characterized in that: The device comprises a processor, configured to call a program from a memory so as to enable the communication device to execute the method according to any one of claims 1 to 13.

56. A communication device, characterized in that: The device comprises a processor, configured to call a program from a memory so as to enable the communication device to execute the method according to any one of claims 14 to 26.

57. A chip, characterized in that: The device comprises a processor, which is used to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 13.

58. A chip, characterized in that: The device comprises a processor, configured to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 14 to 26.

59. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 13.

60. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 14 to 26.

61. A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 13.

62. A computer program product, characterized in that A program is included, which causes a computer to execute the method as claimed in any one of claims 14 to 26.

63. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 13.

64. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 14 to 26.

Images