A communication method and apparatus

Abstract

This application provides a communication method and apparatus. The method may include: a network device sending configuration parameter information, which is used by a terminal device to configure listening to the PDCCH. The configuration parameter information includes a mapping relationship between DCI formats and BWP indexes. The configuration information also includes search space set configuration information, which is used by the terminal device to configure listening to all DCI formats corresponding to the BWPs. The network device sends a first DCI, which is the same DCI format configured by the terminal device to listen to on both the active BWP and the target BWP. The first DCI includes indication information and scheduling information, where the indication information indicates the target BWP index and the scheduling information schedules data transmission. The terminal device transmits data through the target bandwidth portion. This method reduces the latency of switching bandwidth portions and improves communication efficiency.

Description

Technical Field

[0001] This application relates to the field of communications. In particular, it relates to a communication method and apparatus. Background Technology

[0002] The bandwidth part (BWP) represents a set of contiguous resource blocks (RBs) for a given carrier and a given set of parameters. This constitutes the operating bandwidth of the user equipment (UE), and each BWP has an index. During operation, the UE needs to switch BWPs according to instructions from network devices, such as downlink control information (DCI), to meet service requirements. However, currently, for different DCI formats, the UE may be unable to listen to or parse the information in the DCI, resulting in significant BWP switching latency or the UE being unable to obtain the scheduling information for transmitted data, severely impacting the communication of the terminal equipment. Therefore, how to solve the problem of the UE being unable to listen to or parse DCI is a current challenge. Summary of the Invention

[0003] This application provides a communication method and apparatus that can solve the problem that the UE may be unable to listen to or parse DCI.

[0004] In a first aspect, a communication method is provided, which may include: a network device sending configuration parameter information, the configuration parameter information being used by a terminal device to configure listening to the Physical Downlink Control Channel (PDCCH), the configuration parameter information including a first mapping relationship and a second mapping relationship, the first mapping relationship being a mapping relationship between at least one bandwidth portion (BWP) index and a first format, the second mapping relationship being a mapping relationship between at least one BWP index and a second format, the first format and the second format being different formats of Downlink Control Information (DCI), at least one BWP index being the same in the first mapping relationship and the second mapping relationship, the configuration information also including search space set configuration information, the search space set configuration information being used by the terminal device to configure listening to all DCI formats corresponding to each BWP index in the first mapping relationship and the second mapping relationship; the network device sending a first DCI, the first DCI being in a third format, the third format being the same DCI format configured by the terminal device to listen to on the active BWP and the target BWP, the first DCI including indication information and scheduling information, the indication information being used to indicate the target BWP index, and the scheduling information being used to schedule data transmission.

[0005] This method, when configuring the format for listening to downlink control information for terminal devices via network devices, ensures that at least a DCI format is configured, along with a corresponding search space set. Furthermore, the downlink control information sent by the network device is one of the DCI formats configured within the search space set. This allows the terminal device to receive downlink control information on the active bandwidth, complete handover, and parse the downlink control information on the target bandwidth for normal data transmission, reducing handover latency and improving communication efficiency.

[0006] The above methods can also be predefined through protocols.

[0007] In conjunction with the first aspect, in some implementations of the first aspect, the first mapping relationship differs from the second mapping relationship in at least one BWP index.

[0008] In conjunction with the first aspect, in some implementations of the first aspect, the first mapping relationship is exactly the same as the BWP index in the second mapping relationship.

[0009] In conjunction with the first aspect, in some implementations of the first aspect, the first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1.

[0010] Secondly, a communication method is provided, which may include: a terminal device receiving configuration parameter information, the configuration parameter information being used by the terminal device to configure listening to the Physical Downlink Control Channel (PDCCH), the configuration parameter information including a first mapping relationship and a second mapping relationship, the first mapping relationship being a mapping relationship between at least one bandwidth portion BWP index and a first format, the second mapping relationship being a mapping relationship between at least one BWP index and a second format, the first format and the second format being different formats of Downlink Control Information (DCI), at least one BWP index being the same in the first mapping relationship and the second mapping relationship, the configuration information also including search space set configuration information, the search space set configuration information being used by the terminal device to configure listening to all DCI formats corresponding to each BWP index in the first mapping relationship and the second mapping relationship; the terminal device receiving a first DCI, the first DCI being in a third format, the third format being the same DCI format configured by the terminal device to listen to on the active BWP and the target BWP, the first DCI including indication information and scheduling information, the indication information being used to indicate the target BWP index, and the scheduling information being used to schedule data transmission. The terminal device switches to the target BWP based on the first DCI to perform data transmission.

[0011] In conjunction with the second aspect, in some implementations of the second aspect, the terminal device determines that the format of the first DCI is different from the DCI format configured for monitoring on the target BWP, and the terminal device determines that the DCI is an error message.

[0012] In conjunction with the second aspect, in some implementations of the second aspect, the first mapping relationship differs from the second mapping relationship in that at least one BWP index.

[0013] In conjunction with the second aspect, in some implementations of the second aspect, the first mapping relationship is exactly the same as the BWP index in the second mapping relationship.

[0014] In conjunction with the second aspect, in some implementations of the second aspect, the first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1.

[0015] Thirdly, a communication method is provided, which may include: a terminal device receiving second downlink control information (DCI) in an active bandwidth portion, the second DCI including indication information for indicating a target bandwidth portion (BWP); the terminal device determining that the format of the second DCI is different from the DCI format configured for listening on the target BWP; and the terminal device performing any of the following:

[0016] The terminal device determined that the second DCI was an error message.

[0017] or,

[0018] The terminal device switches from the active BWP to the target BWP based on the second DCI.

[0019] or,

[0020] The terminal device switches from the active BWP to the target BWP according to the instruction information, and the terminal device ignores the first scheduling information carried in the DCI, which is used to schedule data transmission.

[0021] This method addresses the issue of a terminal device receiving a DCI format different from the configured listening format for a given bandwidth segment. When this information is identified as an error, the device can either simply switch to a different format or resume normal data communication based on the new DCI format after the switch. This resolves the problem of the terminal device being unable to determine whether to switch when receiving an unconfigured DCI format, thus improving communication efficiency.

[0022] The above methods can also be predefined through protocols.

[0023] Specifically, the terminal device determines that the format of the second DCI is different from the DCI format that the terminal device is configured to monitor on the target BWP. This could mean that the format of the second DCI is different from all the DCI formats that the terminal device is configured to monitor on the target BWP.

[0024] In conjunction with the third aspect, in some implementations of the third aspect, the terminal device switches from the active BWP to the target BWP according to the first instruction information. The method further includes: the terminal device receiving a third DCI on the target BWP, the format of the third DCI being the same as the DCI format configured for monitoring on the target BWP by the terminal device, the third DCI including second scheduling information used for scheduling data transmission; and the terminal device transmitting data on the target BWP according to the third DCI.

[0025] In conjunction with the third aspect, in some implementations of the third aspect, before the terminal device activates the BWP to receive the second DCI, the method further includes: the terminal device receiving first configuration parameter information and second configuration parameter information; the terminal device listening to the physical downlink control channel (PDCCH) on the activated BWP according to the first configuration parameter; and listening to the PDCCH on the target BWP according to the second configuration parameter information.

[0026] Fourthly, a communication device is provided, which may include a processing unit and a transceiver unit. The transceiver unit can be used to transmit configuration parameter information for a terminal device to configure listening to the Physical Downlink Control Channel (PDCCH). The configuration parameter information includes a first mapping relationship and a second mapping relationship. The first mapping relationship is a mapping relationship between at least one bandwidth portion (BWP) index and a first format. The second mapping relationship is a mapping relationship between at least one BWP index and a second format. The first format and the second format are different formats of downlink control information (DCI), respectively. At least one of the first mapping relationship and the second mapping relationship is present. The BWP indexes are the same. The configuration information also includes search space set configuration information. This search space set configuration information is used by the terminal device to configure listening to all DCI formats corresponding to each BWP index in the first mapping relationship and the second mapping relationship. The transceiver unit is also used to send a first DCI. The format of the first DCI is a third format. The third format is the same DCI format that the terminal device configures to listen to on the active BWP and the target BWP. The first DCI includes indication information and scheduling information. The indication information is used to indicate the target BWP index, and the scheduling information is used to schedule data transmission.

[0027] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first mapping relationship differs from the second mapping relationship in at least one BWP index.

[0028] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first mapping relationship is exactly the same as the BWP index in the second mapping relationship.

[0029] In conjunction with the fourth aspect, in some implementations of the fourth aspect, the first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1.

[0030] Fifthly, a communication apparatus is provided, which may include a processing unit and a transceiver unit. The transceiver unit is configured to receive configuration parameter information, and the processing unit is configured to configure a listening physical downlink control channel (PDCCH) according to the configuration parameter information. The configuration parameter information includes a first mapping relationship and a second mapping relationship. The first mapping relationship is a mapping relationship between at least one bandwidth portion (BWP) index and a first format, and the second mapping relationship is a mapping relationship between at least one BWP index and a second format. The first format and the second format are different formats of downlink control information (DCI), respectively. At least one BWP index is present in the first mapping relationship and the second mapping relationship. The configuration information, which includes search space set configuration information, includes the same WP index. The processing unit can also configure, based on the search space set configuration information, to monitor all DCI formats corresponding to each BWP index in the first and second mapping relationships. The transceiver unit can also receive a first DCI in a third format, which is the same DCI format configured to be monitored by the terminal device on both the active and target BWPs. This DCI includes indication information and scheduling information; the indication information indicates the target BWP index, and the scheduling information schedules data transmission. The terminal device switches to the target BWP based on the first DCI for data transmission.

[0031] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the terminal device determines that the format of the first DCI is different from the DCI format configured for monitoring on the target BWP, and the terminal device determines that the DCI is an error message.

[0032] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first mapping relationship differs from the second mapping relationship in at least one BWP index.

[0033] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first mapping relationship is exactly the same as the BWP index in the second mapping relationship.

[0034] In conjunction with the fifth aspect, in some implementations of the fifth aspect, the first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1.

[0035] A sixth aspect provides a communication apparatus, which may include a processing unit and a transceiver unit. The transceiver unit is configured to receive second downlink control information (DCI) in an active bandwidth portion, the second DCI including indication information for indicating a target bandwidth portion (BWP). The processing unit is configured to determine that the format of the second DCI differs from the DCI format configured for monitoring on the target BWP by the terminal device. The processing unit is also configured to perform any of the following:

[0036] The processing unit can also be used to determine that the second DCI is an error message.

[0037] or,

[0038] The processing unit can also be used to switch from the active BWP to the target BWP based on the second DCI.

[0039] or,

[0040] The processing unit can also be used to switch from the active BWP to the target BWP according to the indication information and ignore the first scheduling information carried in the DCI, which is used to schedule data transmission.

[0041] The processing unit is used to determine that the format of the second DCI is different from the DCI format that the terminal device is configured to monitor on the target BWP. This can be because the format of the second DCI is different from all the DCI formats that the terminal device is configured to monitor on the target BWP.

[0042] In conjunction with the sixth aspect, in some implementations of the sixth aspect, after the processing unit switches from the active BWP to the target BWP according to the first instruction information, the transceiver unit can also be used to receive a third DCI on the target BWP. The format of the third DCI is the same as the DCI format configured for monitoring on the target BWP by the terminal device. The third DCI includes second scheduling information, which is used to schedule data transmission. The transceiver unit can also be used to transmit data on the target BWP according to the third DCI.

[0043] In conjunction with the sixth aspect, in some implementations of the sixth aspect, before the transceiver unit is used to receive the second DCI on the activated BWP, the transceiver unit can also be used to receive first configuration parameter information and second configuration parameter information. The processing unit can be used to listen to the physical downlink control channel (PDCCH) on the activated BWP according to the first configuration parameter, and listen to the PDCCH on the target BWP according to the second configuration parameter information. The PDCCH is used to transmit the DCI.

[0044] It should be understood that the beneficial effects of the method also apply to the device, which will not be elaborated further.

[0045] A seventh aspect provides a computer-readable medium storing program code for execution by a communication device, the program code including instructions for a communication method in a method for executing the first, second, or third aspect, any possible implementation of the first, second, or third aspect, or all possible implementations of the first, second, or third aspect.

[0046] Eighthly, a computer program product containing instructions is provided, which, when run on a computer, causes the computer to perform the first, second, or third aspect described above, or any possible implementation of the first, second, or third aspect, or all possible implementations of the first, second, or third aspect.

[0047] Ninthly, a communication system is provided, the communication system including means having a method and various possible designs for implementing the first, second, or third aspects described above, or any possible implementation of the first, second, or third aspects, or all possible implementations of the first, second, or third aspects.

[0048] In a tenth aspect, a processor is provided for coupling with a memory for performing the methods of the first, second, or third aspect described above, or any possible implementation of the first, second, or third aspect, or all possible implementations of the first, second, or third aspect.

[0049] Eleventhly, a chip is provided, the chip including a processor and a communication interface for communicating with external or internal devices, the communication interface being used to implement the methods of the first, second, or third aspects described above, or any possible implementation of the first, second, or third aspects, or all possible implementations of the first, second, or third aspects.

[0050] Optionally, the chip may further include a memory storing instructions, which the processor executes either the instructions stored in the memory or instructions derived therefrom. When the instructions are executed, the processor implements the methods described in the first, second, or third aspects, or any possible implementation thereof.

[0051] Optionally, the chip can be integrated into the terminal. Attached Figure Description

[0052] Figure 1 This is a schematic diagram of a communication system applicable to an embodiment of this application.

[0053] Figure 2 This is a time slot diagram for switching BWPs.

[0054] Figure 3 This is a schematic diagram of a method for parsing the DCI indicator field.

[0055] Figure 4 This is a schematic diagram of another method for resolving the DCI indicator field.

[0056] Figure 5 This is a schematic diagram of a communication method proposed in an embodiment of this application.

[0057] Figure 6 This is a flowchart illustrating a communication method proposed in an embodiment of this application.

[0058] Figure 7 This is a flowchart illustrating another communication method proposed in an embodiment of this application.

[0059] Figure 8 This is a schematic diagram of another communication method proposed in an embodiment of this application.

[0060] Figure 9 This is a flowchart illustrating another communication method proposed in an embodiment of this application.

[0061] Figure 10 This is a flowchart illustrating another communication method proposed in an embodiment of this application.

[0062] Figure 11 This is a schematic block diagram of a communication device proposed in an embodiment of this application.

[0063] Figure 12 This is a schematic block diagram of another communication device proposed in the embodiments of this application. Detailed Implementation

[0064] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0065] Figure 1This is a schematic diagram of a communication system applicable to this application. The technical solutions of the embodiments of this application can be applied to various communication systems, such as 5G (5th generation, 5G or new radio, NR) systems, Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, etc. The technical solutions provided by this application can also be applied to future communication systems, such as sixth-generation mobile communication systems. The technical solutions provided by this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0066] In the embodiments of this application, the UE may be referred to as terminal equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device.

[0067] Terminal devices can be devices that provide voice / data to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0068] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0069] Furthermore, in this embodiment, the terminal device can also be a terminal device in an IoT system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0070] It should be understood that the network device in this wireless communication system can be a device capable of communicating with the terminal device. This network device can also be called an access network device or a radio access network device, such as a base station. In the embodiments of this application, the network device can refer to a radio access network (RAN) node (or device) that connects the terminal device to the wireless network. A base station can broadly encompass, or be replaced by, various names including: NodeB, evolved NodeB (eNB), next-generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master eNodeB (MeNB), secondary eNodeB (SeNB), multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, micro base station, relay node, donor node, or similar entities, or combinations thereof. A base station can also refer to a communication module, modem, or chip installed within the aforementioned equipment or apparatus. A base station can also be a mobile switching center, a device that performs base station functions in D2D, V2X, and M2M communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. A base station can support networks using the same or different access technologies. The embodiments of this application do not limit the specific technologies or device forms used in the network equipment.

[0071] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move depending on the location of the mobile base station. In other examples, a helicopter or drone can be configured as a device to communicate with another base station.

[0072] In some deployments, the network device in this application embodiment may refer to a CU or a DU, or the network device may include both a CU and a DU. The gNB may also include an active antenna unit (AAU).

[0073] Network devices and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; and they can also be deployed in the air on airplanes, balloons, and satellites. This application does not limit the scenario in which the network devices and terminal devices are located.

[0074] The technical solutions provided in this application can be applied to wireless communication between communication devices. Wireless communication between communication devices can include: wireless communication between network devices and terminals, wireless communication between network devices, and wireless communication between terminal devices. In this application, the term "wireless communication" can also be abbreviated as "communication," and the term "communication" can also be described as "data transmission," "information transmission," or "transmission."

[0075] To facilitate understanding of the solution in this application, the relevant concepts will be explained in advance:

[0076] 1. BWP: Represents a contiguous set of resource blocks (RBs) for a given carrier and a given set of parameters, which can be understood as the UE's operating bandwidth. Each BWP has an index for distinguishing it from others. When the UE is operating in a BWP, this BWP is called the active BWP. The base station can dynamically instruct the UE to switch to another BWP via downlink control information (DCI), which can be called the target BWP.

[0077] 2. DCI Format: In the current protocol, the DCI formats that support dynamic switching of BWP are DCI format 0_1, DCI format 1_1, DCI format 0_2, and DCI format 1_2. In DCI format x_2, 2 represents a type (e.g., '2' indicates bit compression), and x can be 0 (uplink) or 1 (downlink). DCI format 0_1 / 1_1 can be understood as DCI format x_1, where 1 represents a type (e.g., '1' indicates regular DCI), and x can be understood in the same way.

[0078] 3. Domain Information: The DCI contains domain information, which can be used to instruct the UE on scheduling data transmission or reception. For example, the frequency domain resource assignment (FDRA) field indicates the frequency domain resource location for the UE to transmit or receive data; the time domain resource assignment (TDRA) field indicates the time domain resource location for the UE to transmit or receive data; DCI format 1_1 or 1_2 includes the PDSCH-to-HARQ_feedback timing indicator field, which indicates the time slot offset between the PDSCH of the downlink data received by the UE and the HARQ-ACK information feedback of that data, and so on.

[0079] It should be understood that, for the sake of brevity, English abbreviations are used instead of full Chinese names in this application. For example, BWP represents the bandwidth portion. The terminology for the bandwidth portion is not limited to this, and related concepts may have other names in the future as technology develops, but they will still apply to this application and are within the scope of protection of this application.

[0080] The domain information in the DCI mentioned above can be determined based on the higher-layer parameters of the activated BWP (e.g., radio resource control (RRC) parameters) or other parameters (e.g., the frequency domain resource parameters of the activated BWP). The domain information on the DCI can indicate scheduling information, which can be used to schedule data transmission. The scheduling information can include relevant parameters and time-frequency resource information. For example, if the activated BWP is BWP#1, the FDRA domain is determined based on the number of resource blocks (RBs) contained in the frequency domain resources of BWP#1. The TDRA domain is determined based on the RRC parameter configuration of BWP#1. Assuming the time domain resource allocation list (pdsch-TimeDomainAllocationList) has 16 rows, the TDRA domain size is 4 bits; if the list has 2 rows, the TDRA domain size is 1 bit. Since the DCI formats that currently support BWP dynamic switching indication are DCI format 0_1, DCI format 1_1, DCI format 0_2 and DCI format 1_2, the bit size of each DCI format field information can be determined according to the corresponding RRC parameters. For example, the RRC parameters for determining the bit size of the TDRA field in DCI format 0_1 ​​are different from those for determining the bit size of the TDRA field in DCI format 0_2.

[0081] The UE can determine the BWP indicator field (Bandwidth part indicator) and its bit size within DCI format 0_1 / 1_1 or DCI format 0_2 / 1_2 using RRC parameters. When the UE detects a DCI format 0_1 / 1_1 or DCI format 0_2 / 1_2 containing a BWP indicator field, and the BWP index indicated by this field is different from the index of the active BWP, it means the UE has received a BWP handover indication, instructing the UE to switch to the BWP corresponding to that index for data transmission. For example, the network device configures four BWPs for the UE using higher-layer parameters, with BWP indices (BWPindex or BWP ID) of 1, 2, 3, and 4. The active BWP's index is 1. The UE listens for a DCI on BWP#1, and the BWP indicator field in this DCI indicates BWP#2. Since BWP#2's index is different from the index of the active BWP#1 currently occupied by the UE, this indicates that the network device is instructing the UE to switch from active BWP#1 to BWP#2 via this DCI. Once the UE switches to BWP#2, the activated BWP changes from BWP#1 to BWP#2, and the UE performs data reception or transmission on BWP#2.

[0082] The current protocol specifies that the DCI instructing BWP handover is scheduled during the first three symbols of a time slot. This is mainly because the UE needs to perform a series of operations to activate BWP handover, and these operations require a certain amount of time, which can be called the BWP handover activation processing time (T). BWPswitchDelay The handover process is scheduled on the first three symbols of a time slot, allowing the UE to detect the DCI as early as possible for subsequent processing. The BWP handover process generally includes the following steps: the UE detects the handover indication DCI, parses the DCI, identifies the BWP index, modifies the bandwidth of the RF front-end, reconfigures the parameters of the target BWP, and performs a series of complex processes such as system timed handover.

[0083] The handover time of a BWP (Browser-to-WP) depends on the UE's capabilities and the subcarrier spacing of the BWP. Currently, the protocol specifies that a BWP handover with a subcarrier spacing of 15kHz requires one time slot (1ms); a BWP handover with a subcarrier spacing of 30kHz requires two time slots (1ms); a BWP handover with a subcarrier spacing of 60kHz requires three time slots (0.75ms); and a BWP handover with a subcarrier spacing of 120kHz requires six time slots (0.75ms). Figure 2 As shown, the activation BWP switching time is calculated from the start of the OFDM symbol in the time slot where the DCI format indicating BWP switching is detected.

[0084] In BWP handover scenarios, because the RRC parameters are configured differently on different BWPs, the bit size of a certain field information in the DCI format corresponding to different BWPs may differ. For example, when switching from BWP#1 to BWP#2, the number of RBs in BWP#1 is different from that in BWP#2. This might result in the FDRA field bit size of DCI format 1_1 for BWP#1 being 18 bits, while the FDRA field bit size of DCI format 1_1 for BWP#2 is 16 bits. When the UE detects a DCI format 1_1 indication for handover to BWP#2 on BWP#1, since the UE is listening for this DCI format 1_1 on BWP#1, the bit size of DCI format 1_1 is determined based on the active BWP#1. However, data scheduling is implemented on the target BWP#2. Therefore, parsing this DCI format 1_1 requires parsing along with the RRC parameter configuration and / or other parameters of BWP#2.

[0085] like Figure 3 As shown, MSB represents the most significant bit (MSB), and LSB represents the least significant bit (LSB). When the UE detects a DCI indication on BWP#1 that the UE is switching from BWP#1 to BWP#2, the FDRA field is calculated to be 18 bits based on the number of RBs contained in the frequency domain of BWP#1, and 16 bits based on the number of RBs contained in the frequency domain of BWP#2. According to the protocol, when the bit width of the indication field determined by the active BWP is greater than the bit width of the indication field determined by the target BWP, the resolution is performed starting from the least significant bit using bits equal to the bit size of the indication field determined by the target BWP.

[0086] like Figure 4 As shown, when the UE detects a DCI indication on BWP#1 that the UE is switching from BWP#1 to BWP#2, the FDRA field is calculated to be 16 bits based on the number of RBs contained in the frequency domain of BWP#1, and the FDRA field is calculated to be 18 bits based on the number of RBs contained in the frequency domain of BWP#2. According to the protocol, when the bit width of the indication field determined by the active BWP is less than the bit width of the indication field determined by the target BWP, the shorter indication field is padded with zeros until the length is equal to the bit width of the indication field determined by the target BWP, and then parsing is performed based on the length after zero padding.

[0087] However, the current protocol does not consider the following scenario: When the active BWP is configured to listen for DCI format 0_2 / 1_2, and the UE detects or receives a DCI format 0_2 / 1_2 on the active BWP, indicating that the BWP needs to switch, but the target BWP is not configured to listen for DCI format 0_2 / 1_2, or does not have the relevant higher-layer parameters configured. In this case, the UE cannot determine whether it needs to dynamically switch the BWP based on the detected or received DCI. The same problem also occurs when the active BWP is configured to listen for DCI format 0_1 / 1_1, but the target BWP does not have a search space set for listening to DCI format 0_1 / 1_1 and / or does not have the relevant higher-layer parameters configured.

[0088] Generally, if a BWP is not configured to listen to a DCI format, such as DCI format 0_2 / 1_2, it means the base station will not use this DCI format for UE scheduling. Therefore, no higher-layer parameters related to this DCI format will be configured, saving signaling transmission overhead. Higher-layer parameters related to the DCI format are mainly used to determine the bit width of the indication fields contained in this DCI format, which can also be understood as the set of candidate values ​​that the corresponding indication field can indicate. If no relevant higher-layer parameters are configured, it means that the field information of this DCI format does not exist on the target BWP, and the UE cannot send or receive data based on non-existent field information.

[0089] For example, a UE receives a DCI format 1_2 on active BWP#1. The BWP indicator field in this DCI indicates BWP#2, meaning the UE is switching from active BWP#1 to the target BWP#2. If the target BWP#2 does not have the RRC parameter dl-DataToUL-ACK-DCI-1-2-r16 (used to indicate K1) configured, then the target BWP#2 cannot know the value of K1. Since there is no default definition in the protocol, the UE cannot determine at what time and frequency position to send the hybrid automatic repeat request (HARQ) feedback information on the target BWP#2, and therefore cannot perform normal scheduling. Here, K1 is the time slot offset value, which is the time slot offset between scheduling the physical downlink shared channel (PDSCH) and sending back the HARQ-ACK information.

[0090] It should be understood that there are multiple formats for DCI. When one or more formats are used as examples in this application to describe the scheme, it is not intended to limit the DCI format applicable to this application.

[0091] To address the above problems, this application proposes a communication method, such as... Figure 5 As shown, the method may include the following steps:

[0092] Step 501: The network device sends configuration parameter information to the terminal device, and the terminal device receives the configuration parameter information accordingly.

[0093] The configuration parameter information can be used by the terminal device to configure listening to the Physical Downlink Control Channel (PDCCH). This configuration parameter information can include a first mapping relationship and a second mapping relationship. The first mapping relationship is a mapping between at least one bandwidth portion BWP index and a first format, and the second mapping relationship is a mapping between at least one BWP index and a second format. The first format and the second format are different formats of the Downlink Control Information (DCI), and at least one BWP index is the same in both the first and second mapping relationships. That is, the first mapping relationship can include a set of BWP indices and the correspondence between that set and the first format, and the second mapping relationship can include a set of BWP indices and the correspondence between that set and the second format; the two sets of BWP indices have an intersection.

[0094] The first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1. It should be understood that the above formats are only examples and not limitations.

[0095] It should also be understood that the first mapping relationship and the second mapping relationship can have at least one different BWP index, and the first mapping relationship and the second mapping relationship can also have the same BWP index.

[0096] The configuration parameter information may also include search space set configuration information. For example, the starting OFDM symbol of the PDCCH, the listening period, and the associated control resource set (CORESET) can be encapsulated in the search space set configuration information and sent to the terminal device. This search space set configuration information can be used by the terminal device to configure the listening of all downlink control information (DCI) formats corresponding to each BWP index in the first and second mapping relationships. In other words, for any BWP in the mapping relationship of the configuration parameter information, it is necessary to configure the listening of all DCI formats corresponding to that BWP.

[0097] The DCI format for BWP configuration monitoring described above can also be carried in the search space collection configuration information.

[0098] The active bandwidth portion can be configured to listen to downlink control information in at least one format, and the target bandwidth portion can also be configured to listen to downlink control information in at least one format. The number of control information formats that the active bandwidth portion is configured to listen to can be the same as the number of control information formats that the target bandwidth portion is configured to listen to. For example, the active bandwidth portion can be configured to listen to downlink control information in formats 1_2 and 0_1, and the target bandwidth portion can be configured to listen to downlink control information in formats 1_2 and 0_2, meaning there are two formats in each case. Alternatively, the number of control information formats that the active bandwidth portion is configured to listen to can be different from the number of control information formats that the target bandwidth portion is configured to listen to. For example, the active bandwidth portion can be configured to listen to downlink control information in formats 1_2 and 0_1 (two formats), and the target bandwidth portion can be configured to listen to downlink control information in formats 1_2, 1_1, and 0_2 (three formats).

[0099] For example, if the first mapping relationship includes BWP indices BWP#1, BWP#2, and BWP#3 corresponding to format 0_2, then the configuration information should also include search space set configuration information on the BWPs corresponding to BWP#1, BWP#2, and BWP#3, used to configure the search space set to monitor the DCI of format 0_2. Similarly, if the second mapping relationship includes BWP indices BWP#1, BWP#2, and BWP#4 corresponding to format 0_1, then the configuration information should also include search space set configuration information on the BWPs corresponding to BWP#1, BWP#2, and BWP#4, used to configure the search space set to monitor the DCI of format 0_1. Thus, monitoring the DCI of both format 0_1 ​​and format 0_2 is configured on the BWPs corresponding to BWP#1 and BWP#2.

[0100] One possible approach is to configure the active bandwidth portion to listen to downlink control information in at least two formats, wherein at least one of the downlink control information formats is the same as the format of the downlink control information that the target bandwidth portion is configured to listen to.

[0101] Another possible approach is that the target bandwidth portion is configured to listen to downlink control information in at least two formats, at least one of which has the same format as the downlink control information that the target bandwidth portion is configured to listen to.

[0102] In other words, at least one of the following formats must be the same: the format of the downlink control information being monitored in the active bandwidth portion and the format of the downlink control information being monitored in the target bandwidth portion. For example, the active bandwidth portion can be configured to monitor downlink control information in formats 1_2 and 0_1, which have two possible formats. The target bandwidth portion can be configured to monitor downlink control information in formats 1_2, 1_1, and 0_2, where format 1_2 is the same.

[0103] Step 502: The network device sends the first DCI, and correspondingly, the terminal device receives the first DCI.

[0104] The terminal device can receive the first DCI on the active bandwidth portion based on the configuration parameter information.

[0105] The downlink control information may include indication information and scheduling information. The indication information may be used to indicate the target bandwidth portion index, and the scheduling information may be used to indicate the data transmission of the terminal device.

[0106] It should be understood that the target bandwidth index can also be called the indicated bandwidth index (indicated BWP). This application only uses the target bandwidth index as an example of the name of the index and does not limit it.

[0107] Step 503: The terminal device transmits data through the target BWP.

[0108] The terminal device can switch to the target BWP based on the first DCI.

[0109] The terminal device can receive data from the network device through the target BWP, or it can send data to the network device through the target BWP.

[0110] Understandably, although predefined rules are established for network devices in terms of protocols, inconsistencies between the network device and the protocol during communication cannot be ruled out. For example, the format of the DCI sent by the network device may not be the format configured for listening on the target BWP by the terminal device. In view of this, the terminal device may also perform the following steps:

[0111] Step 504: The terminal device determines that the format of the first DCI is different from the DCI format configured for monitoring on the target BWP, and the terminal device determines that the DCI is an error message.

[0112] This method, when configuring the format for listening to downlink control information for terminal devices via network devices, ensures that at least a DCI format is configured, along with a corresponding search space set. Furthermore, the downlink control information sent by the network device is one of the DCI formats configured within the search space set. This allows the terminal device to receive downlink control information on the active bandwidth, complete handover, and parse the downlink control information on the target bandwidth for normal data transmission, reducing handover latency and improving communication efficiency.

[0113] The above methods can also be predefined through protocols.

[0114] It should be understood that the step numbers in this application are merely for clarity and brevity and do not imply any limitation on the order of execution. The device may perform the above steps separately or simultaneously; this application does not impose any limitation on this.

[0115] exist Figure 5 Based on the method shown, this application proposes a communication method, such as... Figure 6 As shown, in this method, Figure 5 In the method shown, the first configuration parameter can be PDCCH listening configuration information. Figure 5 The downlink control information in the method shown can be DCI#A, and the method can include the following steps:

[0116] Step 601: The terminal device reports the DCI format that it supports to be monitored to the network device.

[0117] For example, a terminal device can report to the network device that the DCI format supported for listening on BWP1 is 1_2 or 1_1, and the format supported for listening on BWP2 is 1_2. Here, BWP1 can be... Figure 5 In the method shown, the activation bandwidth portion, BWP2 can be... Figure 5 The target bandwidth portion of the method shown.

[0118] Step 602: The network device sends PDCCH listening configuration information to the terminal device, and the terminal device receives the PDCCH listening configuration information accordingly.

[0119] The PDCCH monitoring configuration information can be found at [reference]. Figure 5 The description of step 501 will not be repeated here.

[0120] The PDCCH monitoring configuration information may also include the DCI format that the network device configures for the terminal device to monitor on a specific BWP. For example, corresponding to the format reported by the terminal device in step 601, the network device can configure the terminal device to monitor DCI formats 1_2 and 1_1 on BWP1, and to monitor format 1_2 on BWP2. In other words, when configuring the monitoring DCI format for a BWP, the network device must configure the BWP to monitor the DCI formats supported by that BWP.

[0121] It should also be understood that the number of DCI format types configured for monitoring on BWP1 can be the same as or different from the number of DCI format types configured for monitoring on BWP2.

[0122] Step 603: The network device sends DCI#A to the terminal device, and the terminal device receives DCI#A on BWP1.

[0123] The BWP indicator field in DCI#A indicates that the BWP index is BWP2. In other words, DCI#A instructs the terminal device to switch from the active bandwidth portion BWP1 to the target bandwidth portion BWP2.

[0124] The network device can send DCIs in the same format as those configured to be listened to on BWP1 and BWP2. For example, if the terminal device is configured to listen to DCIs of format 1_2 and 1_1 on BWP1, and is configured to listen to DCIs of format 1_2 on BWP2, then the network device will send DCI#A in the format 1_2.

[0125] Step 604: The terminal device parses DCI#A to obtain scheduling information.

[0126] This scheduling information may include modulation and coding scheme (MCS) information, redundancy version (RV), HARQ process, K1, and other relevant parameters. It may also include time-frequency resource information, which can be indicated by field information in DCI#A.

[0127] Step 605: The terminal device transmits data to the network device.

[0128] It should be understood that terminal devices transmit data to network devices via BWP2.

[0129] This method improves communication efficiency by requiring network devices to configure the BWP to listen to DCI formats supported by the BWP when configuring the DCI format for the BWP. This solves the problem that terminal devices may receive DCI formats that are different from the format configured to be listened to by the BWP, making it impossible to determine whether to switch and causing communication failure.

[0130] The above methods can also be predefined through protocols.

[0131] exist Figure 5 Based on the method shown, this application also proposes a communication method, such as... Figure 7 As shown, the method may include the following steps:

[0132] Step 701: The terminal device reports the DCI format that it supports to be monitored to the network device.

[0133] This step can be referenced. Figure 6 The description of step 601 will not be repeated here.

[0134] Step 702: The network device sends PDCCH listening configuration information to the terminal device, and the terminal device receives the PDCCH listening configuration information accordingly.

[0135] The PDCCH monitoring configuration information can be found at [reference]. Figure 5 The description of step 501 will not be repeated here.

[0136] Step 703: The network device sends DCI to the terminal device according to the preset rules.

[0137] The rule could be: when the DCI instructs the terminal device to switch BWP, the network device is not allowed to send DCIs in a format where the target bandwidth portion is not configured to be monitored to the terminal device.

[0138] For example, the terminal device is configured to listen for DCI formats 1_2 and 1_1 on BWP1, and the terminal device is configured to listen for DCI format 1_2 on BWP2. The format of DCI#A sent by the network device cannot be 1_1. That is, the format of DCI#A sent by the network device must be 1_2.

[0139] Step 704: The terminal device parses the DCI and obtains scheduling information.

[0140] The scheduling information can be found in the description of step 604, and will not be repeated here.

[0141] Step 705: The terminal device transmits data to the network device.

[0142] It should be understood that terminal devices transmit data to network devices via BWP2.

[0143] It should also be understood that terminal devices can also receive data from network devices via BWP2.

[0144] This method improves communication efficiency by preventing network devices from sending DCIs in formats that BWP is not configured to listen to, thus addressing the problem that terminal devices may receive DCIs in formats different from those configured to be listened to by BWP and be unable to determine whether to switch or communicate normally.

[0145] The above methods can also be predefined through protocols.

[0146] This application proposes yet another communication method, which can be as follows: Figure 8 As shown, the method may include the following steps:

[0147] Step 801: The network device sends the second DCI to the terminal device, and the terminal device receives the second DCI.

[0148] The terminal device can receive the second DCI in the active bandwidth portion.

[0149] Step 802: The terminal device determines that the format of the second DCI is different from the DCI format configured for monitoring on the target BWP. The terminal device determines that the second DCI is an error message. Alternatively, the terminal device switches from the active BWP to the target BWP based on the second DCI. Or, the terminal device switches from the active BWP to the target BWP based on the indication information and ignores the first scheduling information carried in the DCI. The first scheduling information is used to schedule data transmission.

[0150] It should be understood that before the terminal device activates the BWP to receive the second DCI, the network device may send first configuration parameter information and second configuration parameter information to the terminal device. Correspondingly, the terminal device receives the first configuration parameter information and the second configuration parameter information. The terminal device listens to the Physical Downlink Control Channel (PDCCH) on the activated BWP according to the first configuration parameter, and listens to the PDCCH on the target BWP according to the second configuration parameter information. The PDCCH is used to transmit DCI. The first and second configuration parameter information can be found in [reference needed]. Figure 5 The description of the configuration parameters is omitted here.

[0151] When the terminal device determines that the format of the DCI is different from the DCI format that the target BWP is configured to listen to, the terminal device determines that the DCI is an error message and can ignore the message, not process it, discard the message, or skip decoding.

[0152] When the terminal device determines that the format of the DCI is different from the DCI format configured to be listened to by the target BWP, the terminal device specifically switches from the active BWP to the target BWP according to the indication information, and the terminal device ignores the first scheduling information carried in the DCI. It should be understood that this method can be applied to case 1: when the format of the DCI sent by the network device is different from the DCI format configured to be listened to by the terminal device on the target bandwidth portion, the network device does not configure domain information in the DCI, or the configured scheduling information is incomplete; for example, the scheduling information may only include some static physical parameters, such as the number of RBs.

[0153] When the terminal device determines that the format of the second DCI differs from the DCI format configured to be listened to on the target BWP, the terminal device can switch from the active bandwidth portion to the target bandwidth portion based on the second DCI. In other words, it only switches based on the second DCI without any other processing. After the switch is complete, the terminal device can receive a third DCI on the target BWP. The format of this third DCI is the same as the DCI format configured to be listened to on the target BWP. This third DCI includes second scheduling information used to schedule data transmission. The terminal device transmits data on the target BWP based on this third DCI. In other words, after the switch is complete, normal communication can proceed according to the configuration on the BWP.

[0154] This method addresses the issue where, when a terminal device receives a DCI format on a bandwidth segment that differs from the configured listening format for that bandwidth segment, it can either classify the information as an error, perform a simple switch, or resume normal data communication based on the new DCI format after the switch. This resolves the problem of the terminal device being unable to determine whether to switch when receiving an unconfigured DCI format, thus improving communication efficiency.

[0155] The above methods can also be predefined through protocols.

[0156] exist Figure 8 Based on the method shown, this application proposes a communication method, such as... Figure 9 As shown, in this method, Figure 8 In the method shown, the second configuration parameter can be PDCCH monitoring configuration information. Figure 8 The downlink control information in the method shown can be DCI#B, and the method may include the following steps:

[0157] Step 901: The terminal device reports the DCI format that it supports to be monitored to the network device.

[0158] This step can be referenced. Figure 6 The description of step 601 will not be repeated here.

[0159] Step 902: The network device sends PDCCH listening configuration information to the terminal device, and the terminal device receives the PDCCH listening configuration information accordingly.

[0160] The PDCCH monitoring configuration information can be found at [reference]. Figure 5 The description of step 501 will not be repeated here.

[0161] Step 903: The network device sends DCI#B to the terminal device, and the terminal device receives DCI#B on BWP1.

[0162] The BWP indicator field in DCI#B indicates that the BWP index is BWP2. In other words, DCI#B indicates that the terminal device switches from the active bandwidth portion BWP1 to the target bandwidth portion BWP2.

[0163] When a network device sends a DCI, it may only refer to the DCI format that BWP1 is configured to listen to. For example, if the terminal device is configured to listen to DCI formats 1_2 and 1_1 on BWP1, and the terminal device is configured to listen to DCI format 1_2 on BWP2, then the DCI#B sent by the network device will be in format 1_1.

[0164] Step 904: The terminal device determines that the format of DCI#B is different from the DCI format that BWP2 is configured to listen to, and the terminal device determines that DCI#B is an error message.

[0165] The terminal device can ignore the DCI#B, or not process it, or discard the information, or skip the decoding process.

[0166] As an alternative to step 904, the terminal device may also perform the following steps:

[0167] Step 905: The terminal device switches from BWP1 to BWP2 according to DCI#B.

[0168] After a successful handover, the network device can send DCI messages according to the DCI format that the terminal device is configured to listen to on BWP2 and the relevant parameters of BWP2, so that the network device and the terminal device can communicate normally on BWP2.

[0169] This application also proposes a communication method, which can be as follows: Figure 10 As shown, the following steps may be included:

[0170] Step 1001: The terminal device reports the DCI format that it supports to be monitored to the network device.

[0171] This step can be referenced. Figure 6 The description of step 601 will not be repeated here.

[0172] Step 1002: The network device sends PDCCH listening configuration information to the terminal device, and sends RRC parameters and / or predefined default values ​​according to the protocol predefined. Correspondingly, the terminal device receives the PDCCH listening configuration information and RRC parameters or predefined default values.

[0173] The PDCCH monitoring configuration information can be found at [reference]. Figure 5 The description of step 501 will not be repeated here.

[0174] For example, when BWP1 is configured to listen to DCI format 0_2 / 1_2, and BWP2 is not configured to listen to DCI format 0_2 / 1_2, the protocol predefines the RRC parameters related to DCI format 0_2 / 1_2 in the network device configuration and / or the protocol predefines the default values ​​related to DCI format 0_2 / 1_2. The RRC parameters related to DCI format 0_2 / 1_2 can be scheduling-related RRC parameters. For example, the RRC parameter can be a time domain resource allocation list (pdsch-TimeDomainAllocationList), which can be used to schedule the time domain resources of BWP2 using DCI format 0_1 / 1_1.

[0175] Step 1003: The network device sends DCI#C to the terminal device, and the terminal device receives DCI#C on BWP1.

[0176] The BWP indicator field in DCI#C indicates that the BWP index is BWP2. In other words, this DCI#C instructs the terminal device to switch from the active bandwidth portion BWP1 to the target bandwidth portion BWP2.

[0177] Step 1004: The terminal device switches from BWP1 to BWP2 according to DCI#C.

[0178] Step 1005: The terminal device parses DCI#C based on the RRC parameters and / or predefined default values.

[0179] For example, if the base station does not configure the time domain resource indication list defined by pdsch-TimeDomainAllocationList, the terminal device can use the default list "default A" according to the protocol predefined values. Default values ​​related to DCI format 0_2 / 1_2 can be used when the terminal device does not know which parameters to use for normal data transmission if the RRC parameters related to DCI format 0_2 / 1_2 are not configured. In this case, it can handle the situation according to the protocol predefined default values. For example, if the RRC parameter dl-DataToUL-ACK-DCI-1-2-r16 does not exist, the terminal device can use the protocol predefined default values, such as K1=1, allowing data transmission even with the RRC parameters defaulted.

[0180] For example, if the base station does not configure the RRC parameter numberOfBitsForRV-DCI-1-2 to define the bit size of the Redundancy Version Indicator (RV) field in DCI format 1_2, the protocol needs to predefine the RV field size to 0 bits, 2 bits, or any other number of bits in the scenario where this RRC parameter is not configured. When the protocol predefines the RV field size to 0 bits in the scenario where this RRC parameter is not configured, the default RV used can be predefined as RV 0, or another RV number, such as RV 3, etc. In this way, data transmission can be performed even with the RRC parameter numberOfBitsForRV-DCI-1-2 defaulting. The same applies to the RRC parameter numberOfBitsForRV-DCI-0-2.

[0181] For example, if the base station does not configure the RRC parameter harq-ProcessNumberSizeDCI-1-2-r16 to define the bit size of the HARQ number process field in DCI format 1_2, then the protocol needs to predefine the bit size of the HARQ number process field to 0 bits, or it can be predefine to 2 bits, or it can be predefine to other bit numbers, in the scenario where this RRC parameter is not configured. When the protocol predefines the bit size of the HARQ process number field to be 0 bits in the scenario where this RRC parameter is not configured, the default HARQ process number can be predefine as process 0, or a process with other numbers, such as process 1, etc. In this way, data transmission can be performed even with the RRC parameter harq-ProcessNumberSizeDCI-1-2-r16 at its default value.

[0182] For example, if the base station does not configure the RRC parameter numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2 to define the bit size of the Physical Uplink Control Channel (PUCCH) resource indicator field in DCI format 1_2, then the protocol needs to predefine the bit size of the PUCCH resource indicator field to 0 bits, or it can be predefine to 2 bits, or it can be predefine to other bit numbers, in the scenario where this RRC parameter is not configured. When the protocol predefines the bit size of the PUCCH resource indicator field to be 0 bits in the scenario where this RRC parameter is not configured, the default PUCCH resource can be predefine as the first PUCCH resource in the configured PUCCH resource set. In this way, data transmission can be performed even with the RRC parameter numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2 at its default value.

[0183] Step 1006: The terminal device transmits data to the network device.

[0184] It should be understood that terminal devices transmit data to network devices via BWP2.

[0185] This method involves pre-configuring RRC parameters or default values ​​related to the DCI format that is configured to be monitored in the target bandwidth portion of the network device. This allows the terminal device to still parse the DCI when it receives a DCI with a different format than the DCI format configured to be monitored in the target bandwidth portion, and to transmit data through the time domain resources on the target bandwidth portion, thereby improving communication efficiency.

[0186] The above methods can also be predefined through protocols.

[0187] The various embodiments described herein can be independent solutions or combinations thereof based on their inherent logic, and all such solutions fall within the protection scope of this application.

[0188] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspective of interaction between various devices. To implement the functions of the methods provided in the embodiments of this application, network devices or terminal devices may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0189] The module division in this embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used. Furthermore, the functional modules in the various embodiments of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0190] The following, combined with Figures 11 to 12 This application provides a detailed description of the communication device provided in its embodiments. It should be understood that the descriptions of the device embodiments correspond to the descriptions of the method embodiments; therefore, any content not described in detail here will be referred to the method embodiments above, and for the sake of brevity, will not be repeated here.

[0191] Similar to the above concept, such as Figure 11 As shown, this application embodiment also provides an apparatus 1100 for implementing the function of the session management network element in the above method. For example, the apparatus can be a software module or a chip system. In this application embodiment, the chip system can be composed of chips or may include chips and other discrete devices. The apparatus 1100 may include: a processing unit 1110 and a communication unit 1120.

[0192] In this embodiment of the application, the communication unit may also be called a transceiver unit, which may include a sending unit and / or a receiving unit, respectively used to perform the steps of sending and receiving the session management function network element in the above method embodiment.

[0193] A communication unit can also be called a transceiver, transceiver device, or transceiver unit. A processing unit can also be called a processor, processing board, processing module, or processing device. Optionally, the device in communication unit 1120 used to implement the receiving function can be considered a receiving unit, and the device in communication unit 1120 used to implement the transmitting function can be considered a transmitting unit; that is, communication unit 1120 includes a receiving unit and a transmitting unit. A communication unit can sometimes also be called a transceiver, transceiver unit, or interface circuit. A receiving unit can sometimes be called a receiver, receiver circuit, or receiving unit. A transmitting unit can sometimes be called a transmitter, transmitter, or transmitting circuit.

[0194] Communication device 1100 performs the above embodiment Figures 5 to 10 When the network device functions in any of the processes shown in the diagram:

[0195] The communication unit is used for sending and receiving information.

[0196] Communication device 1100 performs the functions described in embodiments 5 to 6 above. Figure 10 When the function of the second device in any of the processes shown is:

[0197] The processing unit can be used to parse DCI.

[0198] The communication unit is used for sending and receiving information.

[0199] The above is just an example. Processing unit 1110 and communication unit 1120 can also perform other functions. For a more detailed description, please refer to [link / reference needed]. Figure 3 The relevant descriptions in the method embodiments shown in or 4, or other method embodiments, will not be repeated here.

[0200] like Figure 12 The image shown is of the device 1200 provided in an embodiment of this application. Figure 12 The device shown can be Figure 11 The illustrated device represents one hardware circuit implementation. This communication device can be applied to the flowchart shown above to perform the functions of the terminal device or network device in the method embodiments described. For ease of explanation, Figure 12 Only the main components of the communication device are shown.

[0201] like Figure 12 As shown, the communication device 1200 includes a processor 1210 and an interface circuit 1220. The processor 1210 and the interface circuit 1220 are coupled to each other. It is understood that the interface circuit 1220 can be a transceiver or an input / output interface. Optionally, the communication device 1200 may also include a memory 1230 for storing instructions executed by the processor 1210, or storing input data required by the processor 1210 to execute instructions, or storing data generated after the processor 1210 executes instructions.

[0202] When the communication device 1200 is used to implement Figure 3 or Figure 4 In the method shown, processor 1210 is used to implement the functions of the processing unit 1110, and interface circuit 1220 is used to implement the functions of the communication unit 1120.

[0203] When the aforementioned communication device is a chip applied to a terminal device, the terminal device chip implements the functions of the terminal device in the above method embodiments. The terminal device chip receives information from other modules (such as an RF module or antenna) in the terminal device, the information being sent to the terminal device by the network device; or, the terminal device chip sends information to other modules (such as an RF module or antenna) in the terminal device, the information being sent to the network device by the terminal device.

[0204] When the aforementioned communication device is a chip applied to a network device, the network device chip implements the functions of the network device in the above method embodiments. The network device chip receives information from other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the terminal device to the network device; or, the network device chip sends information to other modules (such as radio frequency modules or antennas) in the network device, which is information sent from the network device to the terminal device.

[0205] It is understood that the processor in the embodiments of this application may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor may be a microprocessor or any conventional processor.

[0206] In embodiments of this application, the processor may be a random access memory (RAM), flash memory, read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), register, hard disk, portable hard disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and storage medium may reside in an ASIC. Additionally, the ASIC may reside in a network device or terminal device. Alternatively, the processor and storage medium may exist as discrete components in the network device or terminal device.

[0207] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, etc.) containing computer-usable program code.

[0208] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0209] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0210] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

[0211] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, include: The network device sends configuration parameter information, which is used by the terminal device to configure listening to the Physical Downlink Control Channel (PDCCH). The configuration parameter information includes a first mapping relationship and a second mapping relationship. The first mapping relationship is a mapping between at least one Bandwidth Part (BWP) index and a first format. The second mapping relationship is a mapping between at least one BWP index and a second format. The first and second formats are different formats of Downlink Control Information (DCI), and at least one BWP index is the same in both the first and second mapping relationships. The configuration parameter information also includes search space set configuration information, which is used by the terminal device to configure the monitoring of all DCI formats corresponding to each BWP index in the first mapping relationship and the second mapping relationship. The network device sends a second DCI, the format of which is different from the DCI format configured for monitoring on the target BWP. The format of the second DCI is one of all the DCI formats. The second DCI includes indication information, which is used to indicate the index of the target BWP. The network device sends a third DCI on the target BWP. The format of the third DCI is the same as the DCI format configured for monitoring on the target BWP by the terminal device. The format of the third DCI is one of all the DCI formats. The third DCI includes second scheduling information, which is used to schedule data transmission.

2. The method according to claim 1, characterized in that, The first mapping relationship and the second mapping relationship have at least one different BWP index.

3. The method according to claim 1, characterized in that, The first mapping relationship is exactly the same as the BWP index in the second mapping relationship.

4. The method according to any one of claims 1 to 3, characterized in that, The first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1.

5. A communication method, characterized in that, include: The terminal device receives configuration parameter information, which is used by the terminal device to configure listening to the Physical Downlink Control Channel (PDCCH). The configuration parameter information includes a first mapping relationship and a second mapping relationship. The first mapping relationship is a mapping relationship between at least one bandwidth portion (BWP) index and a first format. The second mapping relationship is a mapping relationship between at least one BWP index and a second format. The first format and the second format are different formats of Downlink Control Information (DCI). At least one BWP index is the same in the first mapping relationship and the second mapping relationship. The configuration parameter information also includes search space set configuration information, which is used by the terminal device to configure listening to all DCI formats corresponding to each BWP index in the first mapping relationship and the second mapping relationship. The terminal device receives a second DCI, the format of which is different from the DCI format configured for monitoring on the target BWP. The format of the second DCI is one of all the DCI formats. The second DCI includes indication information, which is used to indicate the index of the target BWP. The terminal device switches to the target BWP according to the second DCI; The terminal device receives a third DCI on the target BWP. The format of the third DCI is the same as the DCI format configured for monitoring on the target BWP by the terminal device. The format of the third DCI is one of all the DCI formats. The third DCI includes second scheduling information, which is used to schedule data transmission. The terminal device transmits data on the target BWP according to the third DCI.

6. The method according to claim 5, characterized in that, The method further includes: The terminal device determines that the format of the second DCI is different from the DCI format configured for monitoring on the target BWP, and the terminal device determines that the DCI is an error message.

7. The method according to claim 5, characterized in that, The first mapping relationship and the second mapping relationship have at least one different BWP index.

8. The method according to any one of claims 5 to 7, characterized in that, The first mapping relationship is exactly the same as the BWP index in the second mapping relationship.

9. The method according to any one of claims 5 to 8, characterized in that, The first format can be 0_2 or 1_2, and the second format can be 0_1 or 1_1.

10. A communication method, characterized in that, include: The terminal device receives a second downlink control information (DCI) in the active bandwidth portion, the second DCI including indication information, the indication information being used to indicate the target bandwidth portion (BWP); If the terminal device determines that the format of the second DCI is different from the DCI format configured for monitoring on the target BWP, the terminal device performs any of the following: The second DCI was determined to be an error message. or, Switching from the active BWP to the target BWP based on the second DCI. or, According to the indication information, the terminal device switches from the active BWP to the target BWP, and ignores the first scheduling information carried in the second DCI. The first scheduling information is used to schedule data transmission. The terminal device receives a third DCI from the target BWP, the format of which is the same as the DCI format configured for monitoring on the target BWP by the terminal device. The third DCI includes second scheduling information, which is used to schedule data transmission. The terminal device transmits data on the target BWP according to the third DCI.

11. The method according to claim 10, characterized in that, Before the terminal device activates BWP to receive the second DCI, the method further includes: The terminal device receives the first configuration parameter information and the second configuration parameter information. The terminal device listens to the Physical Downlink Control Channel (PDCCH) on the active BWP according to the first configuration parameter, and listens to the PDCCH on the target BWP according to the second configuration parameter information.

12. A communication device, characterized in that, The communication device includes a processing unit and a transceiver unit, and is used to perform the method as described in any one of claims 1 to 4, or to perform the method as described in claim 10 or 11.

13. A communication device, characterized in that, The communication device includes a processing unit and a transceiver unit, and is used to perform the method as described in any one of claims 5 to 9.

14. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program that, when run on a computer, causes the computer to perform the method as claimed in any one of claims 1 to 4, or to perform the method as claimed in claim 10 or 11, or causes the computer to perform the method as claimed in any one of claims 5 to 9.

15. A chip, characterized in that, Includes a processor and a communication interface, the processor being configured to read instructions to execute the method as described in any one of claims 1 to 4, or to execute the method as described in claim 10 or 11, or to cause the processor to execute the method as described in any one of claims 5 to 9.

16. A communication system, characterized in that, The communication system includes the communication device as described in claim 12, and / or, as described in claim 13.

Images