Communication method and device

Abstract

The invention relates to the field of communication, in particular to a communication method and equipment. Comprising the steps that the terminal equipment receives configuration information of a first part, and the configuration information of the first part is configured for at least one of a bandwidth part BWP, a cell and a carrier; wherein the first part is determined based on the configuration information of the first part, the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit. According to the embodiment of the invention, the configuration information of the first part is configured for the BWP, the cell or the carrier, and the first part can be flexibly configured.

Description

Communication method and device Technical Field

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

[0002] The 3rd Generation Partnership Project (3GPP) proposed X-Division Duplexing (XDD) technology. XDD can also be called time division duplexing or frequency division duplexing. Using XDD, data can be sent and received simultaneously on different subbands within the same subframe. However, XDD-based configurations may conflict with BWP configurations.

[0003] Summary of the Invention

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

[0005] The terminal device receives the configuration information of the first part, which is configured for at least one of the bandwidth part BWP, the cell and the carrier; wherein the first part is determined based on the configuration information of the first part, the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

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

[0007] The network device sends a first portion of configuration information, where the first portion of configuration information is configured for at least one of a BWP, a cell, and a carrier;

[0008] The first part is determined based on configuration information of the first part; a transmission direction of the first part can be different from a transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

[0009] An embodiment of the present application provides a terminal device, including:

[0010] A receiving unit, configured to receive a first portion of configuration information, where the first portion of configuration information is configured for at least one of a bandwidth part BWP, a cell, and a carrier;

[0011] a processing unit, configured to determine the first part based on the configuration information of the first part;

[0012] The transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

[0013] An embodiment of the present application provides a network device, including:

[0014] A sending unit, configured to send a first part of configuration information, where the first part of configuration information is configured for at least one of a BWP, a cell, and a carrier;

[0015] The first part is determined based on configuration information of the first part; a transmission direction of the first part can be different from a transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

[0016] An embodiment of the present application provides a terminal device, comprising a processor and a memory, 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, so that the terminal device executes the above-mentioned communication method.

[0017] An embodiment of the present application provides a network device, comprising a processor and a memory, 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, so that the network device executes the above-mentioned communication method.

[0018] An embodiment of the present application provides a chip for implementing the above-mentioned communication method.

[0019] Specifically, the chip includes: a processor, configured to call and run a computer program from a memory, so that a device equipped with the chip executes any of the above-mentioned communication methods.

[0020] An embodiment of the present application provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a device, the device executes any of the above-mentioned communication methods.

[0021] An embodiment of the present application provides a computer program product, including computer program instructions, which enable a computer to execute any of the above-mentioned communication methods.

[0022] An embodiment of the present application provides a computer program, which, when executed on a computer, enables the computer to execute any of the above-described communication methods.

[0023] In the embodiment of the present application, the configuration information of the first part is configured for at least one of the BWP, the cell, and the carrier, and the first part can be flexibly configured. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] FIG1 is a schematic diagram of an application scenario according to an embodiment of the present application.

[0025] FIG2 is a schematic diagram showing that a downlink symbol / downlink time slot includes an uplink subband according to an embodiment of the present application.

[0026] FIG3 a is a schematic flowchart of a communication method according to an embodiment of the present application.

[0027] FIG3 b is a schematic flowchart of a communication method according to another embodiment of the present application.

[0028] 4a and 4b are schematic diagrams of a guard band according to an embodiment of the present application.

[0029] FIG5 a is a schematic flowchart of a communication method according to another embodiment of the present application.

[0030] FIG5 b is a schematic flowchart of a communication method according to another embodiment of the present application.

[0031] FIG6 is a schematic diagram of an uplink part determination process according to an embodiment of the present application.

[0032] FIG7 is a schematic diagram of Example 1 of an uplink portion determination process according to an embodiment of the present application.

[0033] FIG8 is a schematic diagram of a TDD system configuration according to an embodiment of the present application.

[0034] FIG9 is a schematic diagram of Example 2 of an uplink part determination process according to an embodiment of the present application.

[0035] FIG10 is a schematic diagram of Example 3 of the uplink part determination process according to an embodiment of the present application.

[0036] FIG11 a is a schematic diagram of an example of uplink configuration.

[0037] FIG11 b is a schematic diagram of an example of uplink configuration for a cell or a carrier.

[0038] FIG11c is a schematic diagram of an example of BWP configuration for the uplink portion.

[0039] FIG12 is a schematic block diagram of a terminal device according to an embodiment of the present application.

[0040] FIG13 is a schematic block diagram of a network device according to an embodiment of the present application.

[0041] FIG14 is a schematic block diagram of a communication device according to an embodiment of the present application.

[0042] FIG15 is a schematic block diagram of a chip according to an embodiment of the present application.

[0043] FIG16 is a schematic block diagram of a communication system according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

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

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

[0051] 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.).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0065] 1. Uplink and Downlink Configuration

[0066] For the Time Division Duplexing (TDD) system, the uplink and downlink configuration is used to configure / indicate the transmission direction of each symbol. In the related art, one or more of the three methods of time division duplex uplink and downlink common configuration (TDD-UL-DL-ConfigCommon), time division duplex uplink and downlink exclusive configuration (TDD-UL-DL-ConfigDedicated) and slot format indication (SFI) are used to indicate the transmission direction of each symbol. The transmission direction can generally include uplink, downlink and flexible types. Among them, TDD-UL-DL-ConfigCommon and TDD-UL-DL-ConfigDedicated are high-layer signaling and are configured for the cell. The former is sent to all users in the cell through broadcast information, and the latter is sent independently to the required users through radio resource control (RRC) signaling. SFI indicates the transmission direction of each symbol of each carrier through the downlink control information (DCI) (also called group common DCI) of the user group.

[0067] An exemplary time division duplex uplink and downlink common configuration information element (TDD-UL-DL-ConfigCommon information element) is as follows:

[0068]

[0069] An exemplary time division duplex uplink and downlink dedicated configuration information element (TDD-UL-DL-ConfigDedicated information element) is as follows:

[0070]

[0071] 2. Bandwidth Part (BWP) Configuration

[0072] The BWP configuration is used to indicate information about transmission frequency domain resources, subcarrier spacing, and various channels. Examples of various channels include: Physical Downlink Shared Channel (PDSCH), Physical Downlink Control Channel (PDCCH), Physical Uplink Control Channel (PUCCH), Physical Uplink Shared Channel (PUSCH), Random Access Channel (RACH), channels related to Semi-Persistent Scheduling (SPS), etc. The BWP configuration can be a parameter in the cell configuration (or cell configuration information). For example, if a cell can be configured with up to 4 BWPs, the BWP to be used can be indicated to the terminal device in a semi-static or dynamic manner. Dynamic indication methods include timer-based switching and DCI indication.

[0073] 1. UL subband in DL symbol / slot

[0074] TDD is primarily used on the base station side. The terminal device side maintains its current state, supporting only sending or receiving data within a subframe. For example, as shown in Figure 2, in a full-duplex (non-overlapping) or subband non-overlapping full-duplex (SBFD) subframe, the middle subband of a downlink timeslot can be configured as an uplink subband.

[0075] However, the method for configuring the uplink portion is still unclear. Since both uplink and downlink configurations indicate the transmission direction, one approach is to configure the uplink portion in a similar manner to the uplink and downlink configurations, namely, to configure it for each cell as a parameter in the cell configuration. However, the parallel BWP configuration allows for flexible configuration of the bandwidth used for transmission within a cell. This can lead to conflicts between the frequency domain bandwidth of the BWP configuration and the frequency domain bandwidth of the uplink portion configuration, for example, the frequency domain bandwidth of the uplink portion configuration is larger than the frequency domain bandwidth of the BWP configuration, which complicates implementation.

[0076] The communication method proposed in the embodiment of the present application may include an uplink part configuration method to solve the problem of conflict between the uplink part configuration and the BWP configuration.

[0077] FIG3a is a schematic flow chart of a communication method 300 according to an embodiment of the present application. The method can optionally be applied to a terminal device in the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0078] S310. The terminal device receives a first portion of configuration information, where the first portion of configuration information is configured for at least one of a bandwidth part (BWP), a cell, and a carrier.

[0079] The first portion is determined based on configuration information of the first portion. The transmission direction of the first portion can be different from the transmission direction of the second portion, and the first portion and the second portion are different frequency domain portions of the same time unit. In other words, the transmission direction of the first portion can be different from the transmission direction of the second portion, or the transmission direction of the first portion can be the same as the transmission direction of the second portion. This can be specifically configured using signaling.

[0080] In an embodiment of the present application, a terminal device may receive the first portion of configuration information from a network device or other terminal device. For example, if the first portion of configuration information is for BWP configuration, the first portion of configuration information may be included in the BWP configuration information. For another example, if the first portion of configuration information is for cell or carrier configuration, the first portion of configuration information may be included in the uplink and downlink configuration information.

[0081] In one embodiment, the first part may be an uplink part. For example, if the transmission direction of the second part is a downlink direction, the transmission direction of the first part may be an uplink direction.

[0082] In one embodiment, the first part may be a downlink part. For example, if the transmission direction of the second part is an uplink direction, the transmission direction of the first part may be a downlink direction.

[0083] In an embodiment of the present application, the same time unit in which the first part and the second part are located can be the same time slot, the same symbol, the same subframe, the same sub-time slot, etc.

[0084] In the embodiments of the present application, the first part is mainly introduced and illustrated as an uplink part. For the case where the first part is a downlink part, reference can be made to the relevant description of the uplink part.

[0085] In one implementation, the first portion of configuration information includes the first portion of frequency domain configuration information and / or the first portion of time domain configuration information.

[0086] In one embodiment, the first part of the frequency domain configuration information is for BWP configuration, and the first part of the frequency domain configuration information is configured in the BWP configuration information; and / or

[0087] The first part of the time domain configuration information is for BWP configuration, and the first part of the time domain configuration information is configured in the BWP configuration information.

[0088] In one case, the frequency domain configuration information in the first part is for BWP configuration, and the time domain configuration information in the first part is for cell or carrier configuration. In another case, both the frequency domain configuration information and the time domain configuration information in the first part are for BWP configuration. In another case, both the frequency domain configuration information and the time domain configuration information in the first part are for cell or carrier configuration.

[0089] In some embodiments, the terminal device may receive BWP configuration information carrying the first part of frequency domain configuration information from a network device or other terminal device, and the terminal device may also receive uplink and downlink configuration information carrying the first part of time domain configuration information from a network device or other terminal device.

[0090] In other embodiments, the terminal device may receive BWP configuration information carrying the first part of frequency domain configuration information and time domain configuration information from a network device or other terminal devices.

[0091] In some further embodiments, the terminal device may receive uplink and downlink configuration information carrying the first part of frequency domain configuration information and time domain configuration information from a network device or other terminal devices.

[0092] In one implementation, the BWP configuration information includes uplink BWP configuration information and / or downlink BWP configuration information, and the first part of the configuration information is configured in the uplink BWP configuration information and / or the downlink BWP configuration information.

[0093] In one embodiment, the first portion of configuration information is configured in BWP public configuration information or BWP user-specific configuration information.

[0094] In an embodiment of the present application, the uplink BWP configuration information may include BWP uplink common configuration information, such as the BWP-UplinkCommon information element, and may also include BWP uplink dedicated configuration information, such as the BWP-UplinkDedicated information element. The downlink BWP configuration information may include BWP uplink common configuration information, such as the BWP-UplinkCommon information element, and may also include BWP uplink dedicated configuration information, such as the BWP-UplinkDedicated information element. In the BWP uplink common configuration information, the BWP uplink dedicated configuration information, the BWP downlink common configuration information, or the BWP downlink dedicated configuration information, the frequency domain configuration information of the uplink part may include the uplink subband, and the time domain configuration information of the uplink part may include the time slot where the uplink subband is located. Similarly, in these information, the frequency domain configuration information of the downlink part may include the downlink subband, and the time domain configuration information of the downlink part may include the time slot downlink subband.

[0095] In one embodiment, the subcarrier spacing used in the first part is determined by or based on the uplink BWP configuration information or the downlink BWP configuration information. For example, the subcarrier spacing used in the first part can be directly determined by the subcarrier spacing in the uplink BWP configuration information or the downlink BWP configuration information. For another example, the subcarrier spacing used in the first part can also be indirectly determined by the uplink BWP configuration information or the downlink BWP configuration information. This can prevent inter-subcarrier interference.

[0096] In one embodiment, the cyclic prefix used in the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information. For example, the cyclic prefix used in the first part can be directly determined by the cyclic prefix in the uplink BWP configuration information or the downlink BWP configuration information. For another example, the cyclic prefix used in the first part can be indirectly determined by the uplink BWP configuration information or the downlink BWP configuration information. This can prevent inter-symbol interference.

[0097] In one embodiment, the subcarrier spacing in the uplink BWP configuration information is the same as the subcarrier spacing in the downlink BWP configuration information; and / or the cyclic prefix in the uplink BWP configuration information is the same as the cyclic prefix in the downlink BWP configuration information.

[0098] In some embodiments, if the uplink configuration information is configured in the BWP uplink public configuration information, the subcarrier spacing used by the uplink portion is determined by the subcarrier spacing in the BWP uplink public configuration information, and the cyclic prefix used by the uplink portion is determined by the cyclic prefix in the BWP uplink public configuration information. In this case, the subcarrier spacing in the BWP uplink public configuration information can be the same as the subcarrier spacing in the BWP downlink public configuration information, and the cyclic prefix in the BWP uplink public configuration information can be the same as the cyclic prefix in the BWP downlink public configuration information. In this way, inter-subcarrier interference and / or inter-symbol interference can be avoided.

[0099] In other embodiments, if the configuration information of the uplink part is configured in the BWP downlink public configuration information, the subcarrier spacing used by the uplink part is determined by the subcarrier spacing in the BWP downlink public configuration information, and the cyclic prefix used by the uplink part is determined by the cyclic prefix in the BWP downlink public configuration information.

[0100] In some further embodiments, if the configuration information of the downlink part is configured in the BWP uplink public configuration information, the subcarrier spacing used by the downlink part is determined by the subcarrier spacing in the BWP uplink public configuration information, and the cyclic prefix used by the downlink part is determined by the cyclic prefix in the BWP uplink public configuration information.

[0101] In yet other embodiments, if the configuration information for the downlink portion is configured in the BWP downlink common configuration information, the subcarrier spacing used in the downlink portion is determined by the subcarrier spacing in the BWP downlink common configuration information, and the cyclic prefix used in the downlink portion is determined by the cyclic prefix in the BWP downlink common configuration information. In this case, the subcarrier spacing in the BWP downlink common configuration information can be the same as the subcarrier spacing in the BWP uplink common configuration information, and the cyclic prefix in the BWP downlink common configuration information can be the same as the cyclic prefix in the uplink BWP configuration information. In this way, inter-subcarrier interference and / or inter-symbol interference can be avoided.

[0102] The BWP uplink common configuration information in the above examples can be replaced with BWP downlink common configuration information, BWP uplink dedicated configuration information, or BWP downlink dedicated configuration information. Correspondingly, the BWP downlink common configuration information can be replaced with BWP uplink common configuration information, BWP downlink dedicated configuration information, or BWP uplink dedicated configuration information. Therefore, the examples are not repeated.

[0103] In one implementation, the indication manner of the first part of the frequency domain configuration information includes a resource indication value (RIV), a bitmap, or a count.

[0104] For example, the frequency domain configuration information of the uplink part may indicate a continuous RB resource in the RIV manner, wherein the RIV indication value may be obtained from the indicated starting RB and the number of RBs.

[0105] In one embodiment, the bandwidth of the first portion is within the bandwidth of the BWP. Alternatively, the bandwidth of the first portion does not exceed the bandwidth of the BWP. Alternatively, the bandwidth of the first portion is less than or equal to the bandwidth of the BWP. For example, the bandwidth of the uplink portion indicated by the RIV is less than or equal to the bandwidth of the BWP.

[0106] In one embodiment, as shown in FIG3b , the method 300 further includes:

[0107] S320. The terminal device receives protection sideband configuration information; wherein the position of the protection sideband is determined based on the protection sideband configuration information, and the protection sideband is located on one side or both sides of the first part.

[0108] In the embodiment of the present application, the protection sideband may also be referred to as protection bandwidth, protection frequency band, protection frequency band, etc. The terminal device may receive protection sideband configuration information from the network device, and the protection sideband configuration information may be carried by the same information as the configuration information of the first part, or may be carried by different information. Among them, if the protection sideband configuration information and the configuration information of the first part are received respectively by different information, the receiving timing is not restricted. The position of the protection sideband is related to the position of the first part, and may be located on one side or both sides of the first part. For example, as shown in FIG4a , if the first part is the uplink part, the protection sideband may be located on both sides of the uplink part, i.e., the uplink sub-band. For another example, as shown in FIG4b , if the first part is the uplink part, the protection sideband may be located on one side of the uplink part, i.e., the uplink sub-band.

[0109] In one embodiment, when the guard band is located on both sides of the first portion, the bandwidths of the guard bands on both sides of the first portion are the same or different. For example, if the first portion is an uplink portion, the number of RBs of the guard bands on both sides of the uplink portion can be the same or different.

[0110] In one embodiment, when there are downlink transmission resources, such as downlink frequency domain resources, on both sides of the first part within a carrier, the protection sideband is located between the first part and the downlink transmission resources, and the number of resource blocks RB of the protection sideband on both sides of the first part is the same.

[0111] In the case where the uplink subband configured by the frequency domain configuration information of the first part is located in the middle of a carrier, downlink transmission resources may exist on both sides of the first part within a carrier. For example, referring to Figure 4a, the first part is an uplink subband, which is located between two downlink transmission resources (labeled as DL), and has a guard sideband on each side of the uplink subband. The number of RBs in these two guard sidebands can be the same.

[0112] In one embodiment, when downlink transmission resources exist only on one side of the first portion within a carrier, the guard sideband is located between the first portion and the downlink transmission resources. For example, referring to FIG4b , when downlink transmission resources (DL) exist on one side of an uplink subband within a carrier and not on the other side, the guard sideband is located between the uplink subband and the downlink transmission resources (DL).

[0113] In one embodiment, the first part of the frequency domain configuration information is applicable to at least one of the following:

[0114] All first time slots;

[0115] All the first symbols;

[0116] The first time slot containing the first part as agreed upon in the protocol;

[0117] The first symbol of the first part as agreed in the agreement;

[0118] a first time slot of the configuration comprising the first portion;

[0119] The configuration includes a first symbol of a first portion.

[0120] In one embodiment, the above-mentioned time slots or symbols may also be replaced by subframes, sub-time slots, half-time slots, etc.

[0121] In one embodiment, if the first part is an uplink part, the first time slot and / or the first symbol is determined based on at least one of the following:

[0122] An uplink subband (UL subband) indicated by the frequency domain configuration information of the uplink part;

[0123] The time domain configuration information of the uplink part indicates the time slot (SlotULsubband) where the uplink subband is located.

[0124] In one embodiment, if the first part is a downlink part, the first time slot and / or the first symbol is determined based on at least one of the following:

[0125] A downlink subband indicated by the frequency domain configuration information of the downlink part;

[0126] The time domain configuration information of the downlink part indicates the time slot where the downlink subband is located.

[0127] In one embodiment, the first time slot includes a downlink time slot or a flexible time slot, and the first symbol includes a downlink symbol or a flexible symbol.

[0128] In one implementation, the first part of the frequency domain configuration information is configured for a cell or a carrier; and / or the first part of the time domain configuration information is configured for a cell or a carrier.

[0129] For example, the frequency domain configuration information and time domain configuration information of the uplink part are both configured for a cell or a carrier.

[0130] For another example, the frequency domain configuration information of the uplink part is configured for the BWP, and the time domain configuration information of the uplink part is configured for the cell or carrier.

[0131] In one embodiment, the subcarrier spacing used in the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information. For example, the subcarrier spacing used in the first part is directly determined by the subcarrier spacing in the activated uplink BWP configuration information or the downlink BWP configuration information. For another example, the subcarrier spacing used in the first part is indirectly determined by the activated uplink BWP configuration information or the downlink BWP configuration information.

[0132] In one embodiment, the cyclic prefix used in the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information. For example, the cyclic prefix used in the first part is directly determined by the cyclic prefix in the activated uplink BWP configuration information or the downlink BWP configuration information. For another example, the cyclic prefix used in the first part is indirectly determined by the activated uplink BWP configuration information or the downlink BWP configuration information.

[0133] For example, the first part is uplink, when the other parts except the first part are downlink, the subcarrier spacing / cyclic prefix is ​​determined by the activation downlink BWP configuration information; when the other parts except the first part are uplink, the subcarrier spacing / cyclic prefix is ​​determined by the activation uplink BWP configuration information; when the other parts except the first part are flexible, the subcarrier spacing / cyclic prefix is ​​determined by the activation downlink BWP configuration information.

[0134] For example, when the first part is downlink and the other parts other than the first part are uplink, the subcarrier spacing / cyclic prefix is ​​determined by the activated uplink BWP configuration information; when the other parts other than the first part are downlink, the subcarrier spacing / cyclic prefix is ​​determined by the activated downlink BWP configuration information; when the other parts other than the first part are flexible, the subcarrier spacing / cyclic prefix is ​​determined by the activated uplink BWP configuration information.

[0135] In one embodiment, the frequency domain position of the first portion is obtained based on at least one of the following:

[0136] The frequency domain configuration information of the first part in the BWP configuration information;

[0137] The frequency domain configuration information in the BWP configuration information and the frequency domain configuration information in the first part.

[0138] For example, if the frequency domain configuration information of the uplink part is included in the BWP configuration information, the frequency domain configuration information of the uplink part in the BWP configuration information can be used to determine the frequency domain position of the uplink part. This can reduce the conflict between the frequency domain position of the uplink part determined by using the BWP configuration information and the frequency domain configuration information of other methods.

[0139] For another example, if the frequency domain configuration information of the uplink part is not in the BWP configuration information, the frequency domain configuration information in the BWP configuration information and the frequency domain configuration information of the uplink part can be compared to determine which uplink part frequency domain configuration information is ultimately used to determine the frequency domain position of the uplink part. This can reduce the conflict between the frequency domain position of the uplink part determined by using the BWP configuration information and the frequency domain configuration information of other methods.

[0140] In one embodiment, when the terminal device is configured with the first part, the configuration of the BWP needs to meet at least one of the following:

[0141] BWP only supports semi-static configuration. The bandwidth of this BWP includes the bandwidth of the first part.

[0142] The bandwidth of all BWPs includes the bandwidth of the first part.

[0143] In some embodiments, the BWP bandwidth can be obtained based on the BWP configuration information. If the BWP only supports semi-static configuration rather than dynamic configuration, bandwidth changes in the BWP configuration information can be reduced. Configuring the BWP bandwidth to include the first portion of bandwidth can reduce conflicts between the BWP configuration information and the bandwidths in the uplink and downlink configuration information, simplifying implementation. The BWP bandwidth can also be referred to as the BWP's frequency-domain configured bandwidth. The first portion of bandwidth can also be referred to as the first portion of the frequency-domain configured bandwidth.

[0144] In other embodiments, if the bandwidth of the BWP configured in the BWP configuration information is greater than or equal to the bandwidth of the first part configured in the uplink and downlink information, or the bandwidth of the first part is within the bandwidth range of the BWP, the conflict between the BWP configuration information and the bandwidth in the uplink and downlink configuration information can also be reduced, which is simple to implement.

[0145] FIG5a is a schematic flow chart of a communication method 500 according to an embodiment of the present application. The method can optionally be applied to the network device in the system shown in FIG1 , but is not limited thereto. The method includes at least part of the following contents.

[0146] S510. The network device sends a first portion of configuration information, where the first portion of configuration information is configured for at least one of a BWP, a cell, and a carrier.

[0147] The first part is determined based on configuration information of the first part; a transmission direction of the first part can be different from a transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

[0148] In one embodiment, the method may further include: the network device determining the configuration information of the first part.

[0149] In one implementation, the first portion of configuration information includes the first portion of frequency domain configuration information and / or the first portion of time domain configuration information.

[0150] In one embodiment, the frequency domain configuration information of the first part is configured for BWP, and the frequency domain configuration information of the first part is configured in the BWP configuration information; and / or, the time domain configuration information of the first part is configured for BWP, and the time domain configuration information of the first part is configured in the BWP configuration information.

[0151] In one implementation, the BWP configuration information includes uplink BWP configuration information and / or downlink BWP configuration information, and the first part of the configuration information is configured in the uplink BWP configuration information and / or the downlink BWP configuration information.

[0152] In one embodiment, the first portion of configuration information is configured in BWP public configuration information or BWP user-specific configuration information.

[0153] In one embodiment, the subcarrier spacing used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information; and / or, the cyclic prefix used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information.

[0154] In one embodiment, the subcarrier spacing in the uplink BWP configuration information is the same as the subcarrier spacing in the downlink BWP configuration information; and / or the cyclic prefix in the uplink BWP configuration information is the same as the cyclic prefix in the downlink BWP configuration information.

[0155] In one implementation, the indication manner of the first part of the frequency domain configuration information includes a resource indication value RIV, a bitmap, or a count.

[0156] In one embodiment, the bandwidth of the first portion is within the bandwidth of the BWP.

[0157] In one embodiment, as shown in FIG5b , the communication method 500 further includes:

[0158] S520: The network device sends guard band configuration information; wherein the position of the guard band is determined based on the guard band configuration information, and the guard band is located on one side or both sides of the first portion. S510 and S520 may not have a timing restriction.

[0159] In one embodiment, when the guard band is located on both sides of the first portion, the bandwidths of the guard bands on both sides of the first portion are the same or different.

[0160] In one embodiment, when there are downlink transmission resources on both sides of the first part within a carrier, the protection sideband is located between the first part and the downlink transmission resources, and the number of resource blocks RB of the protection sideband on both sides of the first part is the same.

[0161] In one embodiment, when downlink transmission resources exist only on one side of the first part within a carrier, the guard sideband is located between the first part and the downlink transmission resources.

[0162] In one embodiment, the first part of the frequency domain configuration information is applicable to at least one of the following:

[0163] All first time slots;

[0164] All the first symbols;

[0165] The first time slot containing the first part as agreed upon in the protocol;

[0166] The first symbol of the first part as agreed in the agreement;

[0167] a first time slot of the configuration comprising the first portion;

[0168] The configuration includes a first symbol of a first portion.

[0169] In one embodiment, the first time slot includes a downlink time slot or a flexible time slot, and the first symbol includes a downlink symbol or a flexible symbol.

[0170] In one implementation, the first part of the frequency domain configuration information is configured for a cell or a carrier; and / or the first part of the time domain configuration information is configured for a cell or a carrier.

[0171] In one embodiment, the subcarrier spacing used by the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information; and / or, the cyclic prefix used by the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information.

[0172] In one embodiment, the frequency domain position of the first portion is obtained based on at least one of the following:

[0173] The frequency domain configuration information of the first part in the BWP configuration information;

[0174] The frequency domain configuration information in the BWP configuration information and the frequency domain configuration information in the first part.

[0175] In one embodiment, when the first part is configured, the configuration of the BWP needs to meet at least one of the following:

[0176] BWP only supports semi-static configuration. The bandwidth of this BWP includes the bandwidth of the first part.

[0177] The bandwidth of all BWPs includes the bandwidth of the first part.

[0178] In one embodiment, the first portion includes an uplink portion or a downlink portion.

[0179] In a specific application scenario, as shown in FIG6 , the uplink portion determination process may include the following steps:

[0180] S610: The terminal device receives a frequency domain configuration of an uplink portion. The frequency domain configuration of the uplink portion is configured for a bandwidth portion. Specifically, the terminal device may receive the frequency domain configuration of the uplink portion from a network device.

[0181] Furthermore, the uplink frequency domain configuration is a parameter of the bandwidth. Changing the bandwidth also changes the uplink frequency domain configuration. Furthermore, the uplink frequency domain configuration can be configured only in the downlink bandwidth configuration, only in the uplink bandwidth configuration, or in both the downlink and uplink bandwidth configurations.

[0182] Furthermore, the bandwidth of the uplink portion is less than or equal to the bandwidth of the corresponding bandwidth portion.

[0183] Furthermore, the bandwidth portion includes one or more uplink frequency domain configurations. When the bandwidth portion includes only one uplink frequency domain configuration, the uplink frequency domain configuration is always valid for the bandwidth portion. When the bandwidth portion includes multiple uplink configurations, the MAC layer-based control element (MAC CE) or DCI indicates one of the multiple uplink frequency domain configurations.

[0184] Furthermore, the terminal device receives a guard band configuration. The guard band is located on one side or both sides of the uplink portion. If the guard band is located on both sides of the uplink portion, the bandwidth of the guard bands on both sides can be the same or different.

[0185] S620. The terminal device determines the uplink part based on the frequency domain configuration of the uplink part.

[0186] In this example, if the frequency domain configuration of the uplink part is for BWP configuration and the time domain configuration of the uplink part is for cell configuration, the uplink part can adapt to dynamic BWP bandwidth changes and adapt to cell-level uplink and downlink configurations.

[0187] The communication method of the embodiment of the present application is applicable to any link from a base station to a terminal device, from a terminal device to a base station, and between terminal devices.

[0188] Example 1: Semi-statically configure the uplink bandwidth, see Figure 7.

[0189] S710. The terminal device receives a frequency domain configuration for the uplink portion. The frequency domain configuration for the uplink portion is configured for the bandwidth portion. The time domain configuration for the uplink portion is configured for the cell or carrier. Specifically, the terminal device may receive a configuration for the BWP including the frequency domain configuration for the uplink portion from the network device.

[0190] Furthermore, the uplink frequency domain configuration is a parameter of the bandwidth. For example, the uplink frequency domain configuration, such as an uplink subband (UL subband), can use a resource indicator value (RIV) to indicate a continuous range of resource blocks (RBs). The RIV indicator value is derived from the indicated starting RB and the number of RBs. Alternatively, a bitmap can be used to indicate the uplink subband.

[0191] Furthermore, the UL subband indicated by the RIV is within the bandwidth part, that is, the bandwidth of the UL subband is less than or equal to the bandwidth of the bandwidth part.

[0192] Furthermore, the frequency domain configuration of the uplink part is a common configuration parameter for the cell. For example, the frequency domain configuration of the uplink part, such as UL subband, can be a parameter in the bandwidth part uplink common parameter (BWP-UplinkCommon), or the frequency domain configuration of the uplink part can be a parameter in the bandwidth part downlink common parameter (BWP-DownlinkCommon), or a parameter in BWP.

[0193] The following are some examples of uplink subband (i.e., UL subband-r18) in BWP basic parameters, BWP downlink common parameters, and BWP uplink common parameters:

[0194]

[0195] Since the seamless bidirectional forwarding detection (SBFD) operation is performed on the base station side, the division of the uplink and downlink parts is usually directly related to the radio frequency implementation of the base station. Using a unified configuration for the entire cell can reduce the complexity of the base station implementation.

[0196] (a) When the UL subband is configured in BWP-UplinkCommon, the subcarrier spacing (subcarrierSpacing) and / or cyclic prefix (cyclicPrefix) used in the uplink portion can be determined by the subcarrierSpacing and / or cyclicPrefix in BWP-UplinkCommon, respectively. Furthermore, the subcarrier spacing (subcarrierSpacing) and / or cyclic prefix (cyclicPrefix) used in the uplink portion are the same as the subcarrierSpacing and / or cyclicPrefix in BWP-DownlinkCommon, respectively, to ensure time-frequency synchronization when uplink and downlink occur in the same symbol. Alternatively, the subcarrierSpacing and / or cyclic prefix used in the uplink portion can be configured based on the UL subband-specific subcarrierSpacing and / or cyclicPrefix.

[0197] (b) When the UL subband is configured in BWP-DownlinkCommon, the subcarrierSpacing and / or cyclicPrefix used in the uplink part are determined by the subcarrierSpacing and / or cyclicPrefix in BWP-DownlinkCommon respectively.

[0198] Of course, to adapt to the bandwidth capabilities and service requirements of different terminal devices, the uplink part can also be a user-specific configuration parameter. For example, the uplink part configuration, such as UL subband, can be a parameter in the bandwidth part uplink dedicated parameters (BWP-UplinkDedicated), or the uplink part configuration can be a parameter in the bandwidth part uplink dedicated parameters (BWP-DownlinkDedicated).

[0199]

[0200] When the bandwidth part configuration changes, the uplink part configuration also changes accordingly. And the effective time of the uplink part configuration is consistent with the effective time of the bandwidth part configuration. For example, the terminal device receives two BWP configurations, such as the first BWP-UplinkDedicated and the second BWP-UplinkDedicated, and each BWP-UplinkDedicated contains a UL subband. If the terminal device indicates the first BWP-UplinkDedicated, the terminal device determines the uplink part based on the UL subband in the first BWP-UplinkDedicated. If the terminal device indicates the second BWP-UplinkDedicated, the terminal device determines the uplink part based on the UL subband in the second BWP-UplinkDedicatedn.

[0201] Furthermore, the terminal device receives a guard band configuration, such as a guard bandwidth (Guard Band). The guard band is located on one or both sides of the uplink part. If the guard band is located on both sides of the uplink part, the guard band bandwidths on both sides may be the same or different. Guard Band may be only the number of RBs, or the starting RB and the number of RBs. When the Guard band only contains the number of RBs, the Guard band is close to the UL subband by default. When the UL subband is located in the middle of the carrier, the Guard band acts on both sides of the UL subband, and the number of RBs of the Guard bands on both sides is the same. When the UL subband is located on one side of the carrier, the Guard band acts on the side of the UL subband close to the center frequency. Alternatively, two guard bands may be configured to act on both sides of the UL subband respectively.

[0202] S720. The terminal device determines the uplink part based on the frequency domain configuration of the uplink part.

[0203] (a) If the UL subband is configured only in BWP-UplinkCommon, the uplink portion of the downlink timeslot / symbol and / or flexible timeslot / symbol is determined based on the UL subband configuration in BWP-UplinkCommon;

[0204] (b) If the UL subband is configured only in BWP-DownlinkCommon, the uplink portion of the downlink slots / symbols and / or flexible slots / symbols is determined based on the UL subband configuration in BWP-DownlinkCommon;

[0205] (c) If the UL subband is configured in BWP-DownlinkCommon and BWP-UplinkCommon, the uplink part of the downlink time slot / symbol is determined according to the UL subband configuration in BWP-DownlinkCommon; the uplink part of the flexible time slot / symbol is determined according to the UL subband configuration in BWP-UplinkCommon.

[0206] Furthermore, BWP-UplinkCommon and BWP-DownlinkCommon can be replaced with BWP-UplinkDedicated and BWP-DownlinkDedicated.

[0207] Furthermore, the frequency domain configuration of the uplink part is applicable to all downlink and / or flexible time slots / symbols, or available downlink and / or flexible time slots / symbols agreed upon by the protocol, or configured downlink and / or flexible time slots / symbols.

[0208] The configured downlink time slot / symbol is the time slot / symbol containing the uplink portion configured for the cell. For example, the time slot / symbol information containing the uplink portion is configured in the serving cell common configuration (ServingCellConfigCommon) and / or the serving cell configuration (ServingCellConfig), such as the time slot where the uplink subband is located (SlotULSubband). Furthermore, SlotULSubband is configured in TDD-UL-DL-ConfigCommon and / or TDD-UL-DL-ConfigDedicated. For example, the "nrofSBFDSymbols" parameter in the following parameters is the SlotULSubband configuration.

[0209]

[0210]

[0211] In one embodiment, the terminal device receives BWP-UplinkCommon and TDD-UL-DL-ConfigCommon.

[0212] Among them, BWP-UplinkCommon includes UL subband-r18. In the following configuration, UL subband-r18=501 and the BWP bandwidth is 50. It can be seen that the starting RB of the uplink part is 1 and the number of RBs is 11.

[0213]

[0214] Based on BWP-UplinkCommon and TDD-UL-DL-ConfigCommon, the terminal device can obtain the uplink and downlink transmission directions as shown in Figure 8, that is, there are 2 downlink time slots and 2 uplink time slots in a radio frame, and time slots 1-8 include the uplink part.

[0215] Example 2: semi-statically configure the time-frequency domain information of the uplink part, see Figure 9.

[0216] S910. The terminal device receives the frequency domain configuration and time domain configuration of the uplink part. The frequency domain configuration and time domain configuration of the uplink part are configured for the bandwidth part. Specifically, the terminal device can receive the configuration for the BWP including the frequency domain configuration and time domain configuration of the uplink part from the network device.

[0217] Furthermore, the uplink frequency domain configuration is a parameter of the bandwidth component. For example, the uplink frequency domain configuration, such as the UL subband, uses the RIV method to indicate a continuous range of RB resources. The RIV indicator value is derived from the indicated starting RB and the number of RBs. Furthermore, if the UL subband indicated by the RIV is within the bandwidth component, the bandwidth of the UL subband is less than or equal to the bandwidth of the bandwidth component.

[0218] Furthermore, the uplink frequency domain configuration is a common configuration parameter for the cell. For example, the uplink frequency domain configuration, such as the UL subband, is a parameter in BWP-UplinkCommon, or the uplink frequency domain configuration is a parameter in BWP-DownlinkCommon. Because SBFD operation is performed on the base station side, the division between the uplink and downlink parts is often directly related to the base station's RF implementation. Using a unified configuration across the entire cell can reduce the complexity of base station-side implementation.

[0219] (a) When the UL subband is configured in BWP-UplinkCommon, the subcarrier spacing (subcarrierSpacing) and / or cyclic prefix (cyclicPrefix) used in the uplink are determined by the subcarrierSpacing and / or cyclicPrefix in BWP-UplinkCommon, respectively. Furthermore, the subcarrierSpacing and / or cyclicPrefix in the uplink are identical to those in BWP-DownlinkCommon, respectively, to ensure time-frequency synchronization when uplink and downlink occur in the same symbol. Alternatively, the subcarrierSpacing and / or cyclicPrefix configured specifically for the UL subband can be used.

[0220] (b) When the UL subband is configured in BWP-DownlinkCommon, the subcarrierSpacing and / or cyclicPrefix used in the uplink part are determined by the subcarrierSpacing and / or cyclicPrefix in BWP-DownlinkCommon respectively.

[0221] Of course, to adapt to the bandwidth capabilities and service requirements of different terminal devices, the uplink part can also be a user-specific configuration parameter. For example, the uplink part configuration, such as UL subband, is a parameter in BWP-UplinkDedicated, or the uplink part configuration is a parameter in BWP-DownlinkDedicated.

[0222] Furthermore, the uplink time domain configuration is a parameter of the bandwidth. For example, the uplink time domain configuration includes the timeslot (SlotULSubband) where the uplink subband resides. The uplink time domain configuration can use a bitmap to indicate the SlotULSubband within a period, for example, 1 indicates an SBFD timeslot / symbol, and 0 indicates a non-SBFD timeslot / symbol. The uplink time domain can also directly indicate the number of SBFD timeslots / symbols, for example, nrofSBFD. The uplink symbols are immediately adjacent to the uplink symbols.

[0223] Furthermore, the time domain configuration of the uplink part is a common configuration parameter for the cell. For example, the time domain configuration of the uplink part, such as SlotULSubband, is a parameter in BWP-UplinkCommon, or the frequency domain configuration of the uplink part is a parameter in BWP-DownlinkCommon. Since the SBFD operation is on the base station side, the division of the uplink and downlink parts is usually directly related to the radio frequency implementation of the base station. The use of a unified configuration for the entire cell can reduce the complexity of the implementation on the base station side. Of course, in order to adapt to the bandwidth capabilities and service requirements of different terminal devices, the uplink part can also be a user-specific configuration parameter. For example, the time domain configuration of the uplink part, such as SlotULSubband, is a parameter in BWP-UplinkDedicated, or the uplink part configuration is a parameter in BWP-DownlinkDedicated.

[0224] When the bandwidth part configuration changes, the uplink part configuration also changes accordingly. And the effective time of the uplink part configuration is consistent with the effective time of the bandwidth part configuration. For example, the terminal device receives 2 BWP configurations, such as the first BWP-UplinkCommon and the second BWP-UplinkCommon, each BWP-UplinkCommon contains UL subband and SlotULSubband. When the terminal device indicates the first BWP-UplinkCommon, the terminal device determines the uplink part according to the UL subband and SlotULSubband in the first BWP-UplinkCommon. When the terminal device indicates the second BWP-UplinkCommon, the terminal device determines the uplink part according to the UL subband and SlotULSubband in the second BWP-UplinkCommon.

[0225] Furthermore, the terminal device receives a protection band configuration, such as a Guard Band. The protection band is located on one or both sides of the uplink part. If the protection band is located on both sides of the uplink part, the protection band bandwidths on both sides may be the same or different. The Guard Band may be only the number of RBs, or the starting RB and the number of RBs. When the Guard band only contains the number of RBs, the Guard band is close to the UL subband by default. When the UL subband is located in the middle of the carrier, the Guard band acts on both sides of the UL band, and the number of RBs of the Guard bands on both sides is the same. When the UL subband is located on one side of the carrier, the Guard band acts on the side of the UL subband close to the center frequency. Alternatively, two guard bands may be configured, one on each side of the UL subband.

[0226] S920. The terminal device determines the uplink part based on the frequency domain configuration of the uplink part.

[0227] (a) If the UL subband and / or SlotULSubband are configured only in BWP-UplinkCommon, then at least one of the downlink timeslot, downlink symbol, flexible timeslot, and flexible symbol configured in step S810 is determined as the uplink portion according to the UL subband and / or SlotULSubband configuration in BWP-UplinkCommon;

[0228] (b) If UL subband and / or SlotULSubband are configured only in BWP-DownlinkCommon, then at least one of the downlink timeslot, downlink symbol, flexible timeslot, and flexible symbol configured in step S810 is determined as the uplink portion according to the UL subband and / or SlotULSubband configuration in BWP-DownlinkCommon;

[0229] (c) If the UL subband and / or SlotULSubband are configured in BWP-DownlinkCommon and BWP-UplinkCommon, the downlink time slot and / or downlink symbol configured in step S810 determines the uplink part according to the UL subband and / or SlotULSubband configuration in BWP-DownlinkCommon; the flexible time slot and / or flexible symbol configured in step 1 determines the uplink part according to the UL subband and / or SlotULSubband configuration in BWP-UplinkCommon.

[0230] Furthermore, BWP-UplinkCommon and BWP-DownlinkCommon can be replaced by BWP-UplinkDedicated and BWP-DownlinkDedicated in the above examples.

[0231] Example 3: The frequency domain configuration of the uplink part adopts cell-level configuration, see Figure 10.

[0232] S1010. The terminal device receives a frequency domain configuration for the uplink portion. The frequency domain configuration for the uplink portion is cell-specific. The time domain portion of the uplink portion may also be cell-specific. Specifically, the terminal device may receive a cell-specific configuration including the frequency domain configuration and the time domain configuration for the uplink portion from the network device.

[0233] For example, the uplink frequency domain configuration is indicated by the ServingCellConfigCommon System Information Block (ServingCellConfigCommonSIB) or the ServingCellConfigCommon information. Typically, the frequency domain configuration uses the RIV method to indicate a continuous range of RB resources. The RIV indication value is derived from the indicated starting RB and the number of RBs. As shown in Figure 11a, the uplink frequency domain configuration is for RBs 6-10.

[0234] S1020. The terminal device determines the uplink part based on the time domain configuration and frequency domain configuration of the uplink part.

[0235] For example, the terminal device determines whether to include the uplink part and / or the frequency domain position of the uplink part based on the frequency domain configuration of the uplink part configured in ServingCellConfigCommonSIB or ServingCellConfigCommon and the current BWP configuration.

[0236] As shown in Figure 11a, for BWP1, its frequency domain range RB{1,2,3} does not include the uplink portion RB{6,7,8,...10}. Therefore, BWP1 in this time slot / symbol does not include the uplink portion, and the transmission direction of this time slot / symbol is determined based on the uplink and downlink configuration and / or scheduling. For BWP2, its frequency domain range RB{10,11,12} includes the uplink portion, and the uplink portion is the first RB of BWP2, corresponding to RB10 in Figure 11a.

[0237] For example, as shown in Figure 11b, the BWP bandwidth is RB{6,7,8,...12}. The uplink portion is configured for a cell or carrier, and is configured as RB{6,7,8,9}. Based on the BWP bandwidth and uplink portion configuration, the frequency domain location of the uplink portion within the current BWP is RB{1,2,3,4}. That is, if the uplink portion is configured as RB{6,7,8,9} and the BWP bandwidth is RB{6,7,8,...12}, the uplink portion corresponds to RB{1,2,3,4} within the BWP.

[0238] For another example, as shown in Figure 11c, if the uplink part is configured for BWP, then the uplink part is configured as {RB1,2,3,4}. That is, when the uplink part is configured as RB{1,2,3,4}, then the uplink part corresponds to RB{1,2,3,4} in the BWP.

[0239] FIG12 is a schematic block diagram of a terminal device 1200 according to an embodiment of the present application. The terminal device 1200 may include:

[0240] The receiving unit 1210 is used to receive configuration information of the first part, where the configuration information of the first part is configured for at least one of the bandwidth part BWP, the cell and the carrier; wherein the first part is determined based on the configuration information of the first part, the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

[0241] In one embodiment, the terminal device 1200 may further include a processing unit 1220 configured to determine the first part based on the configuration information of the first part.

[0242] In one implementation, the first portion of configuration information includes the first portion of frequency domain configuration information and / or the first portion of time domain configuration information.

[0243] In one embodiment, the frequency domain configuration information of the first part is configured for BWP, and the frequency domain configuration information of the first part is configured in the BWP configuration information; and / or, the time domain configuration information of the first part is configured for BWP, and the time domain configuration information of the first part is configured in the BWP configuration information.

[0244] In one implementation, the BWP configuration information includes uplink BWP configuration information and / or downlink BWP configuration information, and the first part of the configuration information is configured in the uplink BWP configuration information and / or the downlink BWP configuration information.

[0245] In one embodiment, the first portion of configuration information is configured in BWP public configuration information or BWP user-specific configuration information.

[0246] In one embodiment, the subcarrier spacing used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information; and / or, the cyclic prefix used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information.

[0247] In one embodiment, the subcarrier spacing in the uplink BWP configuration information is the same as the subcarrier spacing in the downlink BWP configuration information; and / or the cyclic prefix in the uplink BWP configuration information is the same as the cyclic prefix in the downlink BWP configuration information.

[0248] In one implementation, the indication manner of the first part of the frequency domain configuration information includes a resource indication value RIV, a bitmap, or a count.

[0249] In one embodiment, the bandwidth of the first portion is within the bandwidth of the BWP.

[0250] In one embodiment, the receiving unit 1210 is further configured to receive guard band configuration information, and the processing unit 1220 is further configured to determine a position of the guard band based on the guard band configuration information. The guard band is located on one side or both sides of the first portion.

[0251] In one embodiment, when the guard band is located on both sides of the first portion, the bandwidths of the guard bands on both sides of the first portion are the same or different.

[0252] In one embodiment, when there are downlink transmission resources on both sides of the first part within a carrier, the protection sideband is located between the first part and the downlink transmission resources, and the number of resource blocks RB of the protection sideband on both sides of the first part is the same.

[0253] In one embodiment, when downlink transmission resources exist only on one side of the first part within a carrier, the guard sideband is located between the first part and the downlink transmission resources.

[0254] In one embodiment, the first part of the frequency domain configuration information is applicable to at least one of the following:

[0255] All first time slots;

[0256] All the first symbols;

[0257] The first time slot containing the first part as agreed upon in the protocol;

[0258] The first symbol of the first part as agreed in the agreement;

[0259] a first time slot of the configuration comprising the first portion;

[0260] The configuration includes a first symbol of a first portion.

[0261] In one embodiment, the first time slot includes a downlink time slot or a flexible time slot, and the first symbol includes a downlink symbol or a flexible symbol.

[0262] In one implementation, the first part of the frequency domain configuration information is configured for a cell or a carrier; and / or the first part of the time domain configuration information is configured for a cell or a carrier.

[0263] In one embodiment, the subcarrier spacing used by the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information; and / or, the cyclic prefix used by the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information.

[0264] In one embodiment, the frequency domain position of the first portion is obtained based on at least one of the following:

[0265] The frequency domain configuration information of the first part in the BWP configuration information;

[0266] The frequency domain configuration information in the BWP configuration information and the frequency domain configuration information in the first part.

[0267] In one embodiment, when the first part is configured, the configuration of the BWP needs to meet at least one of the following:

[0268] BWP only supports semi-static configuration. The bandwidth of this BWP includes the bandwidth of the first part.

[0269] The bandwidth of all BWPs includes the bandwidth of the first part.

[0270] In one embodiment, the first portion includes an uplink portion or a downlink portion.

[0271] The terminal device 1200 of the embodiment of the present application can implement the corresponding functions of the terminal device in the embodiment of the aforementioned method 300. The processes, functions, implementation methods and beneficial effects corresponding to the various modules (sub-modules, units or components, etc.) in the terminal device 1200 can be found in the corresponding descriptions in the above-mentioned method embodiments, and will not be repeated here. It should be noted that the functions described in the various modules (sub-modules, units or components, etc.) in the terminal device 1200 of the embodiment of the application can be implemented by different modules (sub-modules, units or components, etc.) or by the same module (sub-module, unit or component, etc.).

[0272] FIG13 is a schematic block diagram of a network device 1300 according to an embodiment of the present application. The network device 1300 may include:

[0273] The sending unit 1310 is configured to send a first part of configuration information, where the first part of configuration information is configured for at least one of a BWP, a cell, and a carrier;

[0274] The first part is determined based on configuration information of the first part; a transmission direction of the first part can be different from a transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

[0275] In one implementation, the network device 1300 may further include a determining unit (not shown in the figure) configured to determine the configuration information of the first part.

[0276] In one implementation, the first portion of configuration information includes the first portion of frequency domain configuration information and / or the first portion of time domain configuration information.

[0277] In one embodiment, the frequency domain configuration information of the first part is configured for BWP, and the frequency domain configuration information of the first part is configured in the BWP configuration information; and / or, the time domain configuration information of the first part is configured for BWP, and the time domain configuration information of the first part is configured in the BWP configuration information.

[0278] In one implementation, the BWP configuration information includes uplink BWP configuration information and / or downlink BWP configuration information, and the first part of the configuration information is configured in the uplink BWP configuration information and / or the downlink BWP configuration information.

[0279] In one embodiment, the first portion of configuration information is configured in BWP public configuration information or BWP user-specific configuration information.

[0280] In one embodiment, the subcarrier spacing used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information; and / or, the cyclic prefix used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information.

[0281] In one embodiment, the subcarrier spacing in the uplink BWP configuration information is the same as the subcarrier spacing in the downlink BWP configuration information; and / or the cyclic prefix in the uplink BWP configuration information is the same as the cyclic prefix in the downlink BWP configuration information.

[0282] In one implementation, the indication manner of the first part of the frequency domain configuration information includes a resource indication value RIV, a bitmap, or a count.

[0283] In one embodiment, the bandwidth of the first portion is within the bandwidth of the BWP.

[0284] In one embodiment, the sending unit 1310 is further configured to send guard band configuration information, wherein the position of the guard band is determined based on the guard band configuration information, and the guard band is located on one side or both sides of the first portion.

[0285] In one embodiment, when the guard band is located on both sides of the first portion, the bandwidths of the guard bands on both sides of the first portion are the same or different.

[0286] In one embodiment, when there are downlink transmission resources on both sides of the first part within a carrier, the protection sideband is located between the first part and the downlink transmission resources, and the number of resource blocks RB of the protection sideband on both sides of the first part is the same.

[0287] In one embodiment, when downlink transmission resources exist only on one side of the first part within a carrier, the guard sideband is located between the first part and the downlink transmission resources.

[0288] In one embodiment, the first part of the frequency domain configuration information is applicable to at least one of the following:

[0289] All first time slots;

[0290] All the first symbols;

[0291] The first time slot containing the first part as agreed upon in the protocol;

[0292] The first symbol of the first part as agreed in the agreement;

[0293] a first time slot of the configuration comprising the first portion;

[0294] The configuration includes a first symbol of a first portion.

[0295] In one embodiment, the first time slot includes a downlink time slot or a flexible time slot, and the first symbol includes a downlink symbol or a flexible symbol.

[0296] In one implementation, the first part of the frequency domain configuration information is configured for a cell or a carrier; and / or the first part of the time domain configuration information is configured for a cell or a carrier.

[0297] In one embodiment, the subcarrier spacing used by the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information; and / or, the cyclic prefix used by the first part is determined by the activated uplink BWP configuration information or the downlink BWP configuration information.

[0298] In one embodiment, the frequency domain position of the first portion is obtained based on at least one of the following:

[0299] The frequency domain configuration information of the first part in the BWP configuration information;

[0300] The frequency domain configuration information in the BWP configuration information and the frequency domain configuration information in the first part.

[0301] In one embodiment, when the first part is configured, the configuration of the BWP needs to meet at least one of the following:

[0302] BWP only supports semi-static configuration. The bandwidth of this BWP includes the bandwidth of the first part.

[0303] The bandwidth of all BWPs includes the bandwidth of the first part.

[0304] In one embodiment, the first portion includes an uplink portion or a downlink portion.

[0305] The network device 1300 of the embodiment of the present application can implement the corresponding functions of the terminal device in the embodiment of the aforementioned method 500. The processes, functions, implementation methods and beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the network device 1300 can be found in the corresponding description in the above-mentioned method embodiment, and will not be repeated here. It should be noted that the functions described in the various modules (sub-module, unit or component, etc.) in the network device 1300 of the embodiment of the application can be implemented by different modules (sub-module, unit or component, etc.) or by the same module (sub-module, unit or component, etc.).

[0306] Figure 14 is a schematic structural diagram of a communication device 1400 according to an embodiment of the present application. The communication device 1400 includes a processor 1410, which can call and execute a computer program from a memory to enable the communication device 1400 to implement the method in the embodiment of the present application. For example, in a terminal device, the processor 1410 may include the processing unit 1220 of the terminal device or be capable of implementing the functions and steps implemented by the processing unit 1220. For another example, in a network device, the processor 1410 may include a determination unit of the network device or be capable of implementing the functions and steps implemented by the processing unit 1220.

[0307] In one embodiment, the communication device 1400 may further include a memory 1420. The processor 1410 may call and execute a computer program from the memory 1420 to enable the communication device 1400 to implement the method in the embodiment of the present application.

[0308] The memory 1420 may be a separate device independent of the processor 1410 , or may be integrated into the processor 1410 .

[0309] In one embodiment, the communication device 1400 may further include a transceiver 1430. The processor 1410 may control the transceiver 1430 to communicate with other devices. Specifically, the transceiver 1430 may send information or data to other devices, or receive information or data sent by other devices. For example, in a terminal device, the transceiver 1430 may include the receiving unit 1210 of the terminal device or may be capable of implementing the functions and steps implemented by the receiving unit 1210. For another example, in a network device, the transceiver 1430 may include the sending unit 1310 of the network device or may be capable of implementing the functions and steps implemented by the sending unit 1310.

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

[0311] In one embodiment, the communication device 1400 may be a network device of an embodiment of the present application, and the communication device 1400 may implement the corresponding processes implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0312] In one embodiment, the communication device 1400 may be a terminal device of an embodiment of the present application, and the communication device 1400 may implement the corresponding processes implemented by the terminal device in each method of the embodiment of the present application. For the sake of brevity, they will not be repeated here.

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

[0314] In one embodiment, the chip 1500 may further include a memory 1520. The processor 1510 may call and execute a computer program from the memory 1520 to implement the method executed by the terminal device or the network device in the embodiment of the present application.

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

[0316] In one embodiment, the chip 1500 may further include an input interface 1530. The processor 1510 may control the input interface 1530 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0317] In one embodiment, the chip 1500 may further include an output interface 1540. The processor 1510 may control the output interface 1540 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0318] In one embodiment, the chip can be applied to the network device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the network device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0319] In one embodiment, the chip can be applied to the terminal device in the embodiments of the present application, and the chip can implement the corresponding processes implemented by the terminal device in each method of the embodiments of the present application. For the sake of brevity, they will not be repeated here.

[0320] The chips used in the network device and the terminal device may be the same chip or different chips.

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

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

[0323] 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).

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

[0325] FIG16 is a schematic block diagram of a communication system 1600 according to an embodiment of the present application. The communication system 1600 includes a terminal device 1610 and a network device 1620 .

[0326] The network device 1620 is configured to send a first portion of configuration information, where the first portion of configuration information is configured for at least one of a bandwidth part BWP, a cell, and a carrier.

[0327] Terminal device 1610 is configured to receive a first portion of configuration information, wherein the first portion is determined based on the configuration information of the first portion, a transmission direction of the first portion can be different from a transmission direction of the second portion, and the first portion and the second portion are different frequency domain portions of the same time unit;

[0328] The terminal device 1610 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1620 can be used to implement the corresponding functions implemented by the network device in the above method. For the sake of brevity, they are not described here in detail.

[0329] 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 instructions are loaded and executed on a computer, the process or function in accordance with 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 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 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)).

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

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

[0332] 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 terminal device receives the first part of the configuration information, where the first part of the configuration information is configured for at least one of the bandwidth part BWP, the cell, and the carrier; The first part is determined based on the configuration information of the first part, the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

2. The method according to claim 1, wherein The first part of the configuration information includes the first part of the frequency domain configuration information and / or the first part of the time domain configuration information.

3. The method according to claim 1 or 2, wherein: The first part of the frequency domain configuration information is configured for the BWP, and the first part of the frequency domain configuration information is configured in the BWP configuration information; and / or The first part of the time domain configuration information is configured for BWP, and the first part of the time domain configuration information is configured in the BWP configuration information.

4. The method according to claim 3, wherein: The BWP configuration information includes uplink BWP configuration information and / or downlink BWP configuration information, and the first part of the configuration information is configured in the uplink BWP configuration information and / or the downlink BWP configuration information.

5. The method according to any one of claims 1 to 4, wherein The configuration information of the first part is configured in BWP public configuration information or BWP user-specific configuration information.

6. The method according to claim 4 or 5, wherein: The subcarrier spacing used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information; and / or, The cyclic prefix used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information.

7. The method according to claim 6, wherein: The subcarrier spacing in the uplink BWP configuration information is the same as the subcarrier spacing in the downlink BWP configuration information; and / or the cyclic prefix in the uplink BWP configuration information is the same as the cyclic prefix in the downlink BWP configuration information.

8. The method according to any one of claims 1 to 7, wherein The indication manner of the frequency domain configuration information of the first part includes a resource indication value RIV, a bitmap or a count.

9. The method according to any one of claims 1 to 8, wherein The bandwidth of the first part is within the bandwidth of the BWP.

10. The method according to any one of claims 1 to 9, wherein The method further comprises: The terminal device receives protection sideband configuration information; wherein, the position of the protection sideband is determined based on the protection sideband configuration information, and the protection sideband is located on one side or both sides of the first part.

11. The method according to claim 10, wherein: In a case where the guard bands are located at both sides of the first portion, the bandwidths of the guard bands at both sides of the first portion are the same or different.

12. The method according to claim 11, wherein When there are downlink transmission resources on both sides of the first part in a carrier, the protection sideband is located between the first part and the downlink transmission resources, and the number of resource blocks RB of the protection sideband on both sides of the first part is the same.

13. The method according to any one of claims 10 to 12, wherein In a case where downlink transmission resources exist only on one side of the first part within a carrier, the guard sideband is located between the first part and the downlink transmission resources.

14. The method according to claim 12 or 13, wherein: The first part of the frequency domain configuration information is applicable to at least one of the following: All first time slots; All the first symbols; The first time slot containing the first part as agreed upon in the protocol; The first symbol of the first part as agreed in the agreement; a first time slot of the configuration comprising the first portion; The configuration includes a first symbol of a first portion.

15. The method according to claim 14, wherein The first time slot includes a downlink time slot or a flexible time slot, and the first symbol includes a downlink symbol or a flexible symbol.

16. The method according to any one of claims 1 to 15, wherein The first part of the frequency domain configuration information is configured for a cell or a carrier; and / or The first part of the time domain configuration information is configured for a cell or a carrier.

17. The method according to claim 16, wherein The subcarrier spacing used in the first part is determined by the activated uplink BWP configuration information or downlink BWP configuration information; and / or, The cyclic prefix used by the first part is determined by activated uplink BWP configuration information or downlink BWP configuration information.

18. The method according to any one of claims 1 to 17, wherein The frequency domain position of the first part is obtained based on at least one of the following: The frequency domain configuration information of the first part in the BWP configuration information; The frequency domain configuration information in the BWP configuration information and the frequency domain configuration information of the first part.

19. The method according to any one of claims 1 to 18, wherein When the first part is configured, the BWP configuration must meet at least one of the following requirements: BWP only supports semi-static configuration, and the bandwidth of the BWP includes the bandwidth of the first part; The bandwidth of all BWPs includes the bandwidth of the first part.

20. The method according to any one of claims 1 to 19, wherein The first portion includes an uplink portion or a downlink portion.

21. A communication method, comprising: The network device sends a first part of configuration information, where the first part of configuration information is configured for at least one of a BWP, a cell, and a carrier; The first part is determined based on the configuration information of the first part; the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

22. The method according to claim 21, wherein The first part of the configuration information includes the first part of the frequency domain configuration information and / or the first part of the time domain configuration information.

23. The method according to claim 21 or 22, wherein: The first part of the frequency domain configuration information is configured for the BWP, and the first part of the frequency domain configuration information is configured in the BWP configuration information; and / or The first part of the time domain configuration information is configured for BWP, and the first part of the time domain configuration information is configured in the BWP configuration information.

24. The method according to claim 23, wherein The BWP configuration information includes uplink BWP configuration information and / or downlink BWP configuration information, and the first part of the configuration information is configured in the uplink BWP configuration information and / or the downlink BWP configuration information.

25. The method according to any one of claims 21 to 24, wherein The configuration information of the first part is configured in BWP public configuration information or BWP user-specific configuration information.

26. The method according to claim 24 or 25, wherein The subcarrier spacing used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information; and / or, The cyclic prefix used by the first part is determined by the uplink BWP configuration information or the downlink BWP configuration information.

27. The method according to claim 26, wherein The subcarrier spacing in the uplink BWP configuration information is the same as the subcarrier spacing in the downlink BWP configuration information; and / or the cyclic prefix in the uplink BWP configuration information is the same as the cyclic prefix in the downlink BWP configuration information.

28. The method according to any one of claims 21 to 27, wherein The indication manner of the frequency domain configuration information of the first part includes a resource indication value RIV, a bitmap or a count.

29. The method according to any one of claims 21 to 28, wherein The bandwidth of the first part is within the bandwidth of the BWP.

30. The method according to any one of claims 21 to 29, wherein The method further comprises: The network device sends protection sideband configuration information; wherein the position of the protection sideband is determined based on the protection sideband configuration information, and the protection sideband is located on one side or both sides of the first part.

31. The method according to claim 30, wherein In a case where the guard bands are located at both sides of the first portion, the bandwidths of the guard bands at both sides of the first portion are the same or different.

32. The method according to claim 31, wherein When there are downlink transmission resources on both sides of the first part in a carrier, the protection sideband is located between the first part and the downlink transmission resources, and the number of resource blocks RB of the protection sideband on both sides of the first part is the same.

33. The method according to any one of claims 30 to 32, wherein In a case where downlink transmission resources exist only on one side of the first part within a carrier, the guard sideband is located between the first part and the downlink transmission resources.

34. The method according to claim 32 or 33, wherein The first part of the frequency domain configuration information is applicable to at least one of the following: All first time slots; All the first symbols; The first time slot containing the first part as agreed upon in the protocol; The first symbol of the first part as agreed in the agreement; a first time slot of the configuration comprising the first portion; The configuration includes a first symbol of a first portion.

35. The method according to claim 34, wherein The first time slot includes a downlink time slot or a flexible time slot, and the first symbol includes a downlink symbol or a flexible symbol.

36. The method according to any one of claims 21 to 35, wherein The first part of the frequency domain configuration information is configured for a cell or a carrier; and / or The first part of the time domain configuration information is configured for a cell or a carrier.

37. The method according to claim 36, wherein The subcarrier spacing used in the first part is determined by the activated uplink BWP configuration information or downlink BWP configuration information; and / or, The cyclic prefix used by the first part is determined by activated uplink BWP configuration information or downlink BWP configuration information.

38. The method according to any one of claims 21 to 37, wherein The frequency domain position of the first part is obtained based on at least one of the following: The frequency domain configuration information of the first part in the BWP configuration information; The frequency domain configuration information in the BWP configuration information and the frequency domain configuration information of the first part.

39. The method according to any one of claims 21 to 38, wherein When the first part is configured, the BWP configuration must meet at least one of the following requirements: BWP only supports semi-static configuration, and the bandwidth of the BWP includes the bandwidth of the first part; The bandwidth of all BWPs includes the bandwidth of the first part.

40. The method according to any one of claims 21 to 39, wherein The first portion includes an uplink portion or a downlink portion.

41. A terminal device comprising: A receiving unit, configured to receive a first part of configuration information, where the first part of configuration information is configured for at least one of a BWP, a cell, and a carrier; The first part is determined based on the configuration information of the first part, the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

42. A network device comprising: a sending unit, configured to send a first part of configuration information, where the first part of configuration information is configured for at least one of a BWP, a cell, and a carrier; The first part is determined based on the configuration information of the first part; the transmission direction of the first part can be different from the transmission direction of the second part, and the first part and the second part are different frequency domain parts of the same time unit.

43. A terminal device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so that the terminal device executes the method according to any one of claims 1 to 20 or 21 to 40.

44. A network device comprising: A processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory so as to enable the network device to perform the method according to any one of claims 1 to 20 or 21 to 40.

45. 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 the method according to any one of claims 1 to 20 or 21 to 40.

46. ​​A computer-readable storage medium for storing a computer program, which, when executed by a device, causes the device to perform the method according to any one of claims 1 to 20 or 21 to 40.

47. A computer program product comprising computer program instructions for causing a computer to perform the method of any one of claims 1 to 20 or 21 to 40.

48. A computer program causing a computer to perform the method of any one of claims 1 to 20 or 21 to 40.

Images