Communication methods, communication equipment, communication systems, storage media and software products

Abstract

This application discloses a communication method, communication device, communication system, storage medium, and program product. By receiving downlink control information (DCI) sent by a network device, the DCI includes a first information field indicating a first BWP. The first BWP is different from the terminal's currently active BWP, and a handover condition is determined. If the handover condition is met, the terminal switches to the first BWP. This allows the terminal to determine whether to perform a BWP handover based on additional verification conditions, effectively increasing information reliability, reducing the probability of erroneous handover, and improving the overall system efficiency.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology

[0002] New Radio (NR) systems support Bandwidth Part (BWP) operation, allowing a User Equipment (UE) to be configured with up to four BWPs within a serving cell. A UE has only one active BWP at any given time, and data transmission and reception are performed within the active BWP. The active BWP of a UE can be handed over; NR supports BWP handover mechanisms based on Radio Resource Control (RRC), timers, and Downlink Control Information (DCI). Summary of the Invention

[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0004] A first aspect of this disclosure provides a communication method, which is executed by a terminal, and the method includes:

[0005] The network device receives downlink control information (DCI), which includes a first information field that indicates a first bandwidth portion (BWP).

[0006] The first BWP is different from the currently active BWP of the terminal, and it is determined whether the switching conditions are met.

[0007] If the switching conditions are met, the system will switch to the first BWP.

[0008] A second aspect of this disclosure provides a communication method, which is executed by a network device, and the method includes:

[0009] Sending downlink control information (DCI) to the terminal, the DCI including a first information field, the first information field being used to indicate a first bandwidth portion (BWP);

[0010] The first BWP is different from the currently active BWP of the terminal, and the transmission of the DCI satisfies the switching conditions;

[0011] The DCI is used to instruct the terminal to switch to the first BWP.

[0012] A third aspect of this disclosure provides a terminal, comprising:

[0013] The transceiver module is used to receive downlink control information (DCI) sent by the network device. The DCI includes a first information field, which is used to indicate a first bandwidth portion (BWP).

[0014] The processing module is used to determine whether the switching conditions are met if the first BWP is different from the currently active BWP of the terminal.

[0015] The processing module is further configured to determine to switch to the first BWP if the switching conditions are met.

[0016] A fourth aspect of this disclosure provides a network device, comprising:

[0017] The transceiver module is used to send downlink control information (DCI) to the terminal. The DCI includes a first information field, which is used to indicate a first bandwidth portion (BWP).

[0018] The first BWP is different from the currently active BWP of the terminal, and the transmission of the DCI satisfies the switching conditions;

[0019] The DCI is used to instruct the terminal to switch to the first BWP.

[0020] The solution proposed in this embodiment receives downlink control information (DCI) sent by a network device. The DCI includes a first information field indicating a first BWP. The first BWP is different from the currently active BWP of the terminal, and it is determined whether the handover conditions are met. If the handover conditions are met, the terminal is determined to switch to the first BWP. This enables the terminal to determine whether to perform BWP handover based on additional verification conditions, effectively increasing the reliability of information, effectively reducing the probability of incorrect terminal handover, improving the overall efficiency of the system, and enhancing communication quality. Attached Figure Description

[0021] To more clearly illustrate the technical solutions in the embodiments or background art of this disclosure, the accompanying drawings used in the embodiments or background art of this disclosure will be described below.

[0022] Figure 1A This is a schematic diagram of the architecture of a communication system provided in an embodiment of this disclosure;

[0023] Figure 2A This is an interactive schematic diagram of a communication method provided in an embodiment of this disclosure;

[0024] Figure 3A This is an interactive schematic diagram of a communication method provided in an embodiment of this disclosure;

[0025] Figure 4AThis is a schematic diagram of the structure of a terminal provided in an embodiment of this disclosure;

[0026] Figure 4B This is a schematic diagram of the structure of a network device provided in an embodiment of this application;

[0027] Figure 5A This is a schematic diagram of the structure of a communication device provided in an embodiment of this disclosure;

[0028] Figure 5B This is a schematic diagram of the structure of a chip provided in an embodiment of this disclosure. Detailed Implementation

[0029] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.

[0030] In a first aspect, embodiments of this disclosure provide a communication method, the method comprising: receiving downlink control information (DCI) sent by a network device, the DCI including a first information field, the first information field being used to indicate a first bandwidth portion (BWP); the first BWP being different from the currently active BWP of the terminal, determining whether a handover condition is met; and if the handover condition is met, determining to switch to the first BWP.

[0031] In the above embodiments, the terminal is able to determine whether to perform BWP switching based on additional verification conditions, which effectively increases the reliability of information, effectively reduces the probability of terminal erroneous switching, improves the overall efficiency of the system, and enhances communication quality.

[0032] In conjunction with some embodiments of the first aspect, in some embodiments, the aforementioned DCI is used to indicate scheduling information corresponding to the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) within the first BWP; or, the aforementioned DCI is not used to indicate scheduling information corresponding to the PDSCH or PUSCH within the first BWP.

[0033] In the above embodiments, the DCI indicating BWP handover can be used or not used to indicate scheduling information within the BWP after handover, which can effectively balance the reliability verification of BWP handover with the flexibility of DCI scheduling, improve the overall efficiency of the system, and effectively improve communication quality.

[0034] In some embodiments of the first aspect, the above method further includes: if the above switching conditions are not met, determining to ignore the above DCI.

[0035] In the above embodiments, DCIs that do not meet the verification conditions can be ignored and BWP switching can be avoided, which can effectively reduce the probability of BWP erroneous switching caused by false DCI detection, ensure communication reliability, and improve communication quality and overall system efficiency.

[0036] In conjunction with some embodiments of the first aspect, in some embodiments, the switching condition includes at least one of the following: the DCI is received in the first search space; the DCI is received in the first control resource set (CORESET); the DCI is scrambled by the first radio network temporary identifier (RNTI); and the content of the DCI satisfies the first condition.

[0037] In conjunction with some embodiments of the first aspect, in some embodiments, the first condition includes at least one of the following: the second information field included in the DCI is used to indicate the current active BWP of the terminal; the value of the third information field included in the DCI is a first value; the scheduling information indicated by the DCI satisfies a preset condition; and the padding bits in the DCI are set to a preset sequence.

[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the aforementioned third information field includes at least one of the following: Redundancy Version (RV) information field; New Data Indicator (NDI) information field; Hybrid Automatic Repeat Request (HARQ) process number information field; Modulation and Coding Strategy (MCS) information field; Frequency Domain Resource Allocation (FDRA) information field.

[0039] In conjunction with some embodiments of the first aspect, in some embodiments, the aforementioned third information field is an MCS information field or an FDRA information field; for different first BWPs, the first value corresponding to the aforementioned third information field is different.

[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the value of the third information field is a first value, including at least one of the following: the RV information field is all 0s; the NDI information field is all 0s or all 1s, or the NDI information field is used to indicate that the currently scheduled transport block TB is new data; the HARQ process number information field is all 0s or all 1s; the MCS information field is any one of the following: all 0s, all 1s, or the value configured by the network device; the FDRA information field is any one of the following: all 0s, all 1s, or the value configured by the network device.

[0041] In the above embodiments, by restricting the values ​​of the information fields in DCI, the probability of BWP erroneous handover caused by false DCI detection can be effectively reduced, ensuring communication reliability and improving communication quality and overall system efficiency.

[0042] In conjunction with some embodiments of the first aspect, in some embodiments, the scheduling information indicated by the DCI satisfies preset conditions, including at least one of the following: the length of the frequency domain resource indicated by the DCI does not exceed a first threshold; the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is greater than a first duration, or the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is not less than the first duration; the index of the MCS indicated by the DCI is less than a second threshold, or the index of the MCS indicated by the DCI is not greater than a second threshold; the modulation order indicated by the DCI is a first modulation order; the modulation order indicated by the DCI is lower than a second modulation order, or the modulation order indicated by the DCI is not higher than a second modulation order.

[0043] In the above embodiments, by restricting the scheduling information indicated by DCI, a reasonable range of restrictions can be set, which can effectively balance the reliability verification of BWP handover with the flexibility of DCI scheduling, improve the overall efficiency of the system, and effectively improve the communication quality.

[0044] Secondly, embodiments of this disclosure provide a communication method, the method comprising: sending downlink control information (DCI) to a terminal, the DCI including a first information field, the first information field being used to indicate a first bandwidth portion (BWP); the first BWP being different from the terminal's currently active BWP, and the transmission of the DCI satisfying a handover condition; wherein the DCI is used to instruct the terminal to switch to the first BWP.

[0045] In the above embodiments, the terminal is able to determine whether to perform BWP switching based on additional verification conditions, which effectively increases the reliability of information, effectively reduces the probability of terminal erroneous switching, improves the overall efficiency of the system, and enhances communication quality.

[0046] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned DCI is used to indicate the scheduling information corresponding to the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) within the first BWP; or, the aforementioned DCI is not used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP.

[0047] In conjunction with some embodiments of the second aspect, in some embodiments, the switching conditions include at least one of the following: the DCI is transmitted in the first search space; the DCI is transmitted in the first control resource set (CORESET); the DCI is scrambled by the first radio network temporary identifier (RNTI); and the content of the DCI satisfies the first condition.

[0048] In conjunction with some embodiments of the second aspect, in some embodiments, the first condition mentioned above includes at least one of the following: the second information field included in the DCI is used to indicate the current active BWP of the terminal; the value of the third information field included in the DCI is a first value; the scheduling information indicated by the DCI satisfies a preset condition; and the padding bits in the DCI are set to a preset sequence.

[0049] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned third information field includes at least one of the following: Redundancy Version (RV) information field; New Data Indicator (NDI) information field; Hybrid Automatic Repeat Request (HARQ) process number information field; Modulation and Coding Strategy (MCS) information field; Frequency Domain Resource Allocation (FDRA) information field.

[0050] In conjunction with some embodiments of the second aspect, in some embodiments, the aforementioned third information field is an MCS information field or an FDRA information field; for different first BWPs, the first value corresponding to the aforementioned third information field is different.

[0051] In conjunction with some embodiments of the second aspect, in some embodiments, the value of the third information field is a first value, including at least one of the following: the RV information field is all 0s; the NDI information field is all 0s or all 1s, or the NDI information field is used to indicate that the currently scheduled transport block TB is new data; the HARQ process number information field is all 0s or all 1s; the MCS information field is any one of the following: all 0s, all 1s, or the value configured by the network device; the FDRA information field is any one of the following: all 0s, all 1s, or the value configured by the network device.

[0052] In conjunction with some embodiments of the second aspect, in some embodiments, the scheduling information indicated by the DCI satisfies preset conditions, including at least one of the following: the length of the frequency domain resource indicated by the DCI does not exceed a first threshold; the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is greater than a first duration, or the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is not less than the first duration; the index of the MCS indicated by the DCI is less than a second threshold, or the index of the MCS indicated by the DCI is not greater than a second threshold; the modulation order indicated by the DCI is a first modulation order; the modulation order indicated by the DCI is lower than a second modulation order, or the modulation order indicated by the DCI is not higher than a second modulation order.

[0053] Thirdly, embodiments of this application propose a communication method for a communication system, the communication system including a terminal and a network device. The method includes: the network device sending downlink control information (DCI), the DCI including a first information field, the first information field being used to indicate a first bandwidth portion (BWP); the first BWP being different from the terminal's currently active BWP, the terminal determining whether a handover condition is met; if the handover condition is met, the terminal determining to switch to the first BWP.

[0054] Fourthly, embodiments of this application propose a terminal, which includes a transceiver module and a processing module; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0055] Fifthly, embodiments of this application propose a network device, which includes a transceiver module; wherein the network device is used to execute the second aspect and the optional implementation of the second aspect.

[0056] In a sixth aspect, embodiments of this application provide a terminal, which includes one or more processors; wherein the terminal is used to execute the first aspect and optional implementations of the first aspect.

[0057] In a seventh aspect, embodiments of this application provide a network device, wherein the terminal includes one or more processors; wherein the network device is used to execute the second aspect and optional implementations of the second aspect.

[0058] Eighthly, embodiments of this application provide a communication device for executing the first aspect and optional implementations of the first aspect, as well as the second aspect and optional implementations of the second aspect.

[0059] Ninthly, embodiments of this application propose a communication system, which includes: a terminal and a network device; wherein the terminal is configured to perform the method described in the first aspect and the optional implementation of the first aspect, and the network device is configured to perform the method described in the second aspect and the optional implementation of the second aspect.

[0060] In a tenth aspect, embodiments of this application provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0061] In the eleventh aspect, embodiments of this application provide a program product that, when executed by a communication device, causes the communication device to perform the method described in the first aspect and its optional implementation, as well as the second aspect and its optional implementation.

[0062] In a twelfth aspect, embodiments of this application provide a computer program that, when run on a computer, causes the computer to perform the methods described in the first aspect and its optional implementations, the second aspect and its optional implementations.

[0063] In a thirteenth aspect, embodiments of this application provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described according to the first aspect and its optional implementations, the second aspect, and its optional implementations.

[0064] It is understood that the aforementioned terminals, network devices, access network devices, core network devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0065] This disclosure provides a communication method, a communication device, a communication system, a storage medium, and a program product. In some embodiments, terms such as communication method and information processing method may be used interchangeably.

[0066] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0067] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0068] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0069] In the embodiments disclosed herein, "multiple" refers to two or more.

[0070] In some embodiments, the terms "at least one of A or B, at least one of A and B", "one or more", "a plurality of", "multiple" and the like can be used interchangeably.

[0071] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.

[0072] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, and C.

[0073] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0074] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0075] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.

[0076] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.

[0077] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.

[0078] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.

[0079] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).

[0080] In some embodiments, the terms "access network device (AN device)," "radio access network device (RAN device)," "base station (BS)," "radio base station," "fixed station," "node," "access point," "transmission point (TP)," "reception point (RP)," "transmission / reception point (TRP)," "panel," "antenna panel," "antenna array," "cell," "macro cell," "small cell," "femto cell," "pico cell," "sector," "cell group," "serving cell," "carrier," "component carrier," and "bandwidth part (BWP)" can be used interchangeably.

[0081] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriberstation, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0082] In some embodiments, access network devices, core network devices, or network devices can be replaced by terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced by communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0083] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

[0084] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0085] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0086] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0087] Figure 1A This is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0088] like Figure 1A As shown, the communication system 100 includes a terminal 101 and a network device 102.

[0089] In some embodiments, terminal 101 includes, for example, at least one of the following: mobile phone, wearable device, Internet of Things (IoT) device, narrowband Internet of Things (NB-IoT) device, satellite communication device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, and red-capped terminal, but is not limited thereto.

[0090] In some embodiments, network device 102 may be a node or device that connects a terminal to a wireless network. The network device may include, but is not limited to, nodes such as satellites or drones in non-terrestrial communication networks, evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), next-generation RAN node (NG-RAN node), node B (NB), home node B (HNB), home evolved node B (HeNB), wireless backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in Wi-Fi system.

[0091] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.

[0092] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0093] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.

[0094] The following embodiments of this disclosure can be applied to Figure 1A The communication system 100 shown, or a part thereof, but not limited to it. Figure 1A The entities shown are illustrative; a communication system may include... Figure 1A All or part of the main body, or may include Figure 1A Other entities besides the main body, the number and form of each entity are arbitrary, each entity can be physical or virtual, the connection relationship between the entities is illustrative, the entities can be unconnected or connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0095] The embodiments disclosed herein can be applied to Non-terrestrial Networks (NTN), Internet of Things (IoT) systems, Narrow Band-IoT (NB-IoT) systems, Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), 5G-Advanced (5G-A), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), and IEEE IEEE 802.11 (Wi-Fi, registered trademark), IEEE 802.16 (WiMAX, registered trademark), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (Bluetooth, registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0096] In some embodiments of a mobile communication system, service data is typically carried by a shared channel. For example, downlink service data can be carried by the Physical Downlink Shared Channel (PDSCH), and uplink service data can be carried by the Physical Uplink Shared Channel (PUSCH). PDSCH / PUSCH scheduling is carried by the Physical Downlink Control Channel (PDCCH). The PDCCH carries downlink control information (DCI), which contains many information fields. These fields include the allocation of time and frequency resources for scheduled PDSCH / PUSCH transmissions, the modulation and coding scheme (MCS), and the configuration of Hybrid Automatic Repeat Request (HARQ) feedback information for PDSCH.

[0097] In some embodiments, 5G NR supports BWP operation, and a UE can be configured with up to four BWPs within a serving cell. A UE has only one active BWP at any given time, and data transmission and reception are performed within the active BWP. The UE's active BWP can be handed over; NR supports BWP handover mechanisms based on RRC, timers, and DCI.

[0098] In some embodiments, the DCI-based BWP handover mechanism is implemented through a DCI containing a bandwidth part indicator information field. This DCI is used for uplink and downlink data scheduling (e.g., the aforementioned PDSCH / PUSCH). The DCI indicates a BWP through the bandwidth part indicator field, specifying the BWP containing the data channel (e.g., the aforementioned PDSCH / PUSCH) scheduled by the DCI. The DCI can also indicate other scheduling information, such as time-frequency resource allocation and MCS. If the BWP indicated by the DCI differs from the BWP currently activated by the UE, the UE needs to perform a BWP handover, switching to the target BWP indicated by the DCI. Within the target BWP, data reception or transmission is performed according to the scheduling information indicated by the scheduling DCI.

[0099] In some embodiments, the DCI-based BWP handover mechanism suffers from erroneous BWP handover due to false DCI detection. False DCI detection refers to the UE incorrectly detecting a DCI from a noisy signal; that is, the base station did not actually send the DCI to the UE, but the UE detected it. In this case, the Bandwidth part indicator field in the detected DCI may indicate a target BWP different from the UE's currently active BWP, causing the UE to incorrectly perform a BWP handover. Since the base station did not send the DCI to the UE, it does not expect the UE to perform a BWP handover and will continue scheduling and data transmission within the previously active BWP. However, the UE performs a BWP handover, receiving scheduling information and transmitting and receiving data within the incorrectly detected target BWP. This inconsistency in the base station and UE's understanding of the active BWP can lead to prolonged communication breakdowns between the base station and the terminal, potentially causing RRC connection failures and reconstruction processes, severely impacting user communication quality and user experience.

[0100] Therefore, BWP handover based on DCI relies solely on the Bandwidth part indicator field in the scheduling DCI for indication, resulting in low reliability. A more reliable BWP handover method needs to be considered.

[0101] The communication method and apparatus provided in this disclosure will now be described in detail with reference to the accompanying drawings.

[0102] Figure 2A This is an interactive schematic diagram illustrating a communication method according to an embodiment of this disclosure. For example... Figure 2A As shown, the embodiments of this disclosure relate to a communication method, which includes:

[0103] Step S2101, network device 102 sends DCI.

[0104] In some embodiments, terminal 101 receives DCI sent by network device 102.

[0105] In some embodiments, the DCI described above may be carried by a PDCCH.

[0106] In some embodiments, the DCI includes a first information field, which is used to indicate a first BWP.

[0107] Optionally, the first information field mentioned above can be, for example, a "bandwidth part indicator information field".

[0108] In some embodiments, the first BWP described above is different from the currently active BWP of terminal 101.

[0109] Furthermore, terminal 101 can switch BWPs based on the aforementioned DCI, that is, terminal 101 can switch from the currently active BWP to the aforementioned first BWP based on the instruction of the aforementioned DCI.

[0110] Furthermore, in some embodiments, the terminal 101 can determine whether the handover conditions are met before performing a BWP handover.

[0111] Optionally, if the switching conditions are met, terminal 101 performs a BWP switch, switching from the currently active BWP to the aforementioned first BWP.

[0112] Optionally, if the handover conditions are not met, terminal 101 will not perform BWP handover, and terminal 101 may ignore the received (or detected) DCI.

[0113] In some embodiments, it can be understood that when network device 102 instructs terminal 101 to perform BWP handover via DCI, the DCI sent should meet the handover conditions, that is, network device 102 should send DCI based on the handover conditions.

[0114] In some embodiments, the aforementioned DCI is used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP, or in other words, the aforementioned DCI is used to schedule the PDSCH or PUSCH within the first BWP. That is, the terminal 101 can receive the PDSCH or transmit the PUSCH within the first BWP based on the information included in the aforementioned DCI (e.g., allocated resources, modulation scheme, encoding scheme, etc.).

[0115] In some embodiments, the aforementioned DCI is not used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP, or in other words, the aforementioned DCI is not used to schedule the PDSCH or PUSCH within the first BWP. That is, the terminal 101 will not receive the PDSCH or transmit the PUSCH within the first BWP based on the information included in the aforementioned DCI (e.g., allocated resources, modulation scheme, encoding scheme, etc.).

[0116] In some embodiments, the aforementioned DCI may be used only as control information to instruct terminal 101 to perform BWP handover, and may not be used to schedule the reception or transmission of data channels of terminal 101 in the target BWP after handover.

[0117] In some embodiments, the control signaling includes a cyclic redundancy check (CRC) scrambled with a Radio Network Temporary Identity (RNTI). Terminal 101 can use the corresponding RNTI to descramble the control signaling, thereby decoding the received control signaling and parsing the information fields included in the control signaling.

[0118] Understandably, terminal 101 parses the received control signaling, including parsing each information field included in the control signaling, so as to obtain the information indicated or carried by each information field.

[0119] In some embodiments, the control signaling described above may include multiple information fields, such as: information fields related to resource allocation, information fields related to frequency domain resource allocation, information fields related to time domain resource allocation, information fields related to modulation and coding, information fields related to demodulation reference signal (DMRS), information fields related to HARQ feedback, information fields indicating redundancy version (RV), information fields related to power control, information fields related to PDSCH transmission implementation, etc., which are not limited here.

[0120] In step S2102, terminal 101 determines whether the handover conditions are met.

[0121] In some embodiments, terminal 101 parses the received DCI, determines that it includes a first information field, and is able to determine that the first BWP indicated by the first information field is different from the currently active BWP of terminal 101. Further, terminal 101 can determine whether the handover conditions are met.

[0122] Optionally, if terminal 101 determines that the handover conditions are met, it executes steps S2103a and S2104; if terminal 101 determines that the handover conditions are not met, it executes step S2103b.

[0123] In some embodiments, the switching conditions described above include at least one of the following:

[0124] The aforementioned DCI was received in the first search space;

[0125] The aforementioned DCI is received in the first Control Resource Set (CORESET);

[0126] The aforementioned DCI is scrambled using the first Radio Network Temporary Identity (RNTI);

[0127] The content of the aforementioned DCI (or the information included in the aforementioned DCI) satisfies the first condition.

[0128] The first search space is either pre-configured by network device 102 or a pre-defined search space by the protocol. Similarly, the first CORESET is either pre-configured by network device 102 or a pre-defined set of control resources by the protocol. The first RNTI is either pre-configured by network device 102 or a pre-defined RNTI by the protocol.

[0129] It is understandable that terminal 101 can determine whether the above-mentioned handover conditions are met during the process of detecting and parsing the above-mentioned DCI. For example, in the case of determining whether the above-mentioned DCI is scrambled by the first RNTI, if terminal 101 receives the above-mentioned DCI and can successfully descramble the above-mentioned DCI using the first RNTI, then terminal 101 can determine that the handover conditions are met.

[0130] In some embodiments, the first condition satisfied by the content of the aforementioned DCI may include at least one of the following:

[0131] The second information field included in the aforementioned DCI is used to indicate the currently active BWP of terminal 101;

[0132] The third information field included in the above DCI takes the first value;

[0133] The scheduling information indicated by the above DCI meets the preset conditions;

[0134] The padding bits in the aforementioned DCI are set to a preset sequence.

[0135] In some embodiments, the terminal 101 parses and determines that the second information field included in the DCI is used to indicate the current active BWP of the terminal 101. The terminal 101 may consider that the switching conditions are met, and may further switch from the current active BWP to the first BWP.

[0136] In some embodiments, if the terminal 101 parses and determines that the padding bits included in the DCI are set to a preset sequence, the terminal 101 may consider that the switching conditions are met, and may further switch from the current active BWP to the first BWP.

[0137] It should be noted that padding bits are bits added to make the DCI reach a certain bit length, and do not actually carry downlink control information.

[0138] Optionally, the aforementioned preset sequence may be pre-configured by the network device 102 or pre-defined by the protocol. For example, it may be a sequence of all 1s, a sequence of all 0s, a sequence of 0s and 1s (e.g., 0101…, 1010…), or a bit sequence generated based on other rules, etc.

[0139] In some embodiments, if the terminal 101 parses and determines that the value of the third information field included in the DCI is a first value, the terminal 101 may consider that the switching conditions are met, and may further switch from the currently active BWP to the first BWP.

[0140] Optionally, the aforementioned third information field may include at least one of the following: Redundancy Version (RV) information field; New Data Indicator (NDI) information field; Hybrid Automatic Repeat Request (HARQ) process number information field; Modulation and Coding Strategy (MCS) information field; Frequency Domain Resource Allocation (FDRA) information field.

[0141] Optionally, the corresponding first value can be different for different third information domains.

[0142] Optionally, the first value mentioned above may be pre-configured by the network device 102 or pre-defined by the protocol.

[0143] As an example, the value of the third information field is the first value, which can be, for example, the RV information field included in the above DCI being all 0.

[0144] As an example, the value of the third information field is the first value, which can be, for example, all 0s or all 1s of the NDI information field included in the DCI mentioned above.

[0145] As an example, the value of the third information field is the first value, which can be, for example, the NDI information field included in the DCI mentioned above, used to indicate that the currently scheduled Transport Block (TB) is new data (that is, not retransmitted data).

[0146] As an example, the value of the third information field is the first value, which can be, for example, the HARQ process number information field included in the DCI mentioned above being all 0s or all 1s.

[0147] As an example, the value of the third information field is the first value, which can be, for example, all 0s or all 1s of the MCS information field included in the DCI, or a value pre-configured by the network device 102 or pre-defined by the protocol.

[0148] Optionally, network device 102 can independently configure the value corresponding to the MCS information field for each BWP (different BWPs can correspond to different preset values), that is, the value configured per BWP. Alternatively, network device 102 can also configure a value for an MCS information field to be applied to all BWPs.

[0149] As an example, the value of the third information field is the first value, which can be, for example, all 0s or all 1s of the FDRA information field included in the DCI mentioned above, or a value pre-configured by the network device 102 or pre-defined by the protocol.

[0150] Optionally, network device 102 can independently configure the value corresponding to the FDRA information field for each BWP (different BWPs can correspond to different preset values), that is, the value configured per BWP. Alternatively, network device 102 can also configure a value for the FDRA information field to be applied to all BWPs.

[0151] In the examples above, it can be understood that an information field consisting entirely of zeros means that all bits in the field are 0. For example, if the field size is two bits, the value is 00. Similarly, an information field consisting entirely of one bits means that all bits in the field are 1. For example, if the field size is two bits, the value is 11. A value pre-configured by the network device 102 or pre-defined by the protocol can be, for example, a bit sequence (e.g., 01, 11, 1011, etc.) or the corresponding bit value (e.g., 1, 3, 11, etc.).

[0152] In some embodiments, the scheduling information indicated by the DCI above satisfies preset conditions, which may include at least one of the following:

[0153] The length of the frequency domain resources indicated by the aforementioned DCI does not exceed the first threshold;

[0154] The time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is greater than the first duration, or the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is not less than the first duration.

[0155] The index of the MCS indicated by the above DCI is less than the second threshold, or the index of the MCS indicated by the above DCI is not greater than the second threshold;

[0156] The modulation order indicated by the DCI above is the first modulation order;

[0157] The modulation order indicated by the above DCI is lower than the second modulation order, or the modulation order indicated by the above DCI is not higher than the second modulation order.

[0158] Optionally, the first threshold is pre-configured by the network device 102 or pre-defined by the protocol. The unit of the first threshold can be, for example, a resource block (RB), a resource element (RE), or other frequency domain resource units. For example, the first threshold can be N resource blocks (RB), where N is a positive integer.

[0159] Optionally, the aforementioned first duration is pre-configured by network device 102 or pre-defined by the protocol. The unit of the first duration can be, for example, a slot, a sub-frame, a time-domain symbol, a second (s), a millisecond (ms), or other time-domain resource units. For example, the aforementioned first duration can be S1 symbols, or S2 slots, or time T.

[0160] Optionally, the second threshold mentioned above is pre-configured by network device 102 or pre-defined by the protocol. The second threshold is a number (or index) of the MCS.

[0161] Optionally, the first modulation order and the second modulation order mentioned above are also pre-configured by the network device 102 or pre-defined by the protocol. For example, they are 2, 4, 6, 8, etc.

[0162] Optionally, the first modulation order and the second modulation order can be the same or different.

[0163] It is understood that the switching conditions described in the embodiments of this application can serve as additional verification conditions, thereby enabling terminal 101 to effectively reduce erroneous BWP switching caused by false DCI detection when determining whether to perform BWP switching based on DCI. For example, taking setting the RV version in DCI to all zeros as an example, assuming the RV version is 2 bits, the probability of each of the four states is 1 / 4. Since the RV version of the DCI required for BWP switching must be all zeros, considering the probability of all zeros in DCI false detection is 1 / 4, the probability of erroneous BWP switching can be further reduced by 3 / 4 = 75%. The remaining switching conditions are similar to this example; due to the additional restrictions, erroneous BWP switching caused by false DCI detection can be effectively reduced.

[0164] Step S2103a: The switching conditions are met, and terminal 101 determines to switch to the first BWP.

[0165] In some embodiments, terminal 101 determines that the first BWP indicated in the DCI is different from the current active BWP of terminal 101, and determines in step S2102 that the switching conditions are met, and terminal 101 can switch from the current active BWP to the first BWP.

[0166] In step S2104, terminal 101 performs PUDCH / PUSCH transmission within the first BWP.

[0167] In some embodiments, terminal 101 may receive PDSCH or send PUSCH within the first BWP.

[0168] Correspondingly, in some embodiments, network device 102 can transmit PDSCH or receive PUSCH within the first BWP.

[0169] In some embodiments, terminal 101 may receive PDSCH or transmit PUSCH within the first BWP based on the instruction of the received DCI. Correspondingly, network device 102 may transmit PDSCH or receive PUSCH within the first BWP based on the instruction of the received DCI.

[0170] In other words, in some embodiments, the aforementioned DCI is used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP, or in other words, the aforementioned DCI is used to schedule the PDSCH or PUSCH within the first BWP. That is, the terminal 101 can receive PDSCH or transmit PUSCH within the first BWP based on the information included in the aforementioned DCI (e.g., allocated resources, modulation scheme, coding scheme, etc., wherein the information included in the DCI can be information set to satisfy the aforementioned handover conditions). In other words, the aforementioned DCI can serve both as control information instructing the terminal 101 to perform BWP handover and as control information scheduling the reception or transmission of data channels in the target BWP after handover.

[0171] In some embodiments, terminal 101 may receive PDSCH or transmit PUSCH within the first BWP based on instructions from other DCIs sent by network device 102. Correspondingly, network device 102 may transmit PDSCH or receive PUSCH within the first BWP based on instructions from other DCIs sent by network device 102.

[0172] In other words, in some embodiments, the aforementioned DCI is not used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP, or in other words, the aforementioned DCI is not used to schedule the PDSCH or PUSCH within the first BWP. That is, the terminal 101 will not receive the PDSCH or transmit the PUSCH within the first BWP based on the information included in the aforementioned DCI (e.g., allocated resources, modulation scheme, coding scheme, etc.). In other words, the aforementioned DCI can only serve as control information instructing the terminal 101 to perform BWP handover, and may not be used to schedule the reception or transmission of data channels by the terminal 101 in the target BWP after the handover.

[0173] In step S2103b, the handover conditions are not met, and terminal 101 ignores the aforementioned DCI.

[0174] In some embodiments, terminal 101 determines that the first BWP indicated in the above DCI is different from the currently active BWP of terminal 101, and determines in step S2102 that the switching conditions are not met, and terminal 101 may ignore the above DCI.

[0175] In some embodiments, ignoring the DCI means ignoring all the information included in the DCI, that is, the terminal 101 will not switch the BWP or perform any other scheduling and operation based on the received DCI.

[0176] In some embodiments, the terms “eNB”, “gNB”, “base station”, and “NG-RAN node” can be used interchangeably.

[0177] In some embodiments, the terms "carrier," "band," and "frequency" can be used interchangeably.

[0178] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0179] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".

[0180] In some embodiments, the terms "repeating pattern", "repeating design", "pattern", "repeating design" and other similar terms may be used interchangeably.

[0181] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.

[0182] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".

[0183] In some embodiments, the terms "time domain unit", "time unit", "transmission unit", "Iridium unit", "Iridium system unit", "Iridium system transmission unit", and "time slot" can be used interchangeably.

[0184] In some embodiments, the terms "radio", "wireless", "radioaccess network (RAN)", "access network (AN)", and "RAN-based" can be used interchangeably. In some embodiments, the terms "moment", "point in time", "time", and "time location" can be used interchangeably, as can the terms "duration", "segment", "time window", "window", and "time".

[0185] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0186] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.

[0187] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.

[0188] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.

[0189] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0190] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0191] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.

[0192] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2103. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2103 may be implemented as an independent embodiment, step S2101+S2102 may be implemented as an independent embodiment, step S2102+S2103 may be implemented as an independent embodiment, step S2101+S2103 may be implemented as an independent embodiment, step S2101+S2102+S2103 may be implemented as an independent embodiment, etc., but not limited thereto.

[0193] In some embodiments, see Figure 2A Other optional implementation methods described before or after the corresponding instruction manual.

[0194] Figure 3A This is an interactive schematic diagram illustrating a communication method according to an embodiment of this application. For example... Figure 3AAs shown, the embodiments of this application relate to a communication method, which includes:

[0195] In step S3101, network device 102 sends DCI, which includes a first information field used to indicate the first BWP.

[0196] In step S3102, since the first BWP is different from the currently active BWP of terminal 101, terminal 101 determines whether the handover conditions are met.

[0197] In step S3103, the handover conditions are met, and terminal 101 determines to switch to the first BWP mentioned above.

[0198] In some embodiments, if the above switching conditions are not met, terminal 101 determines to ignore the above DCI.

[0199] In some embodiments, the DCI is used to indicate the scheduling information corresponding to the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) within the first BWP.

[0200] In some embodiments, the DCI is not used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP.

[0201] In some embodiments, the switching conditions described above include at least one of the following:

[0202] The aforementioned DCI was received in the first search space;

[0203] The aforementioned DCI was received in the first control resource set CORESET;

[0204] The aforementioned DCI is scrambled by the first wireless network temporary identifier RNTI;

[0205] The content of the above DCI satisfies the first condition.

[0206] In some embodiments, the first condition above includes at least one of the following:

[0207] The second information field included in the aforementioned DCI is used to indicate the currently active BWP of terminal 101;

[0208] The third information field included in the above DCI takes the first value;

[0209] The scheduling information indicated by the above DCI meets the preset conditions;

[0210] The padding bits in the aforementioned DCI are set to a preset sequence.

[0211] In some embodiments, the third information field includes at least one of the following:

[0212] Redundant version RV information field;

[0213] New data indicates the NDI information field;

[0214] Hybrid Automatic Repeat Request (HARQ) process number information field;

[0215] Modulation and coding scheme (MCS) information field;

[0216] Frequency domain resource allocation FDRA information domain.

[0217] In some embodiments, the third information field is an MCS information field or an FDRA information field; for different first BWPs, the first value corresponding to the third information field is different.

[0218] In some embodiments, the value of the third information field is a first value, including at least one of the following:

[0219] The above RV information field is all 0;

[0220] The above NDI information field is all 0 or all 1, or the above NDI information field is used to indicate that the currently scheduled transport block TB is new data;

[0221] The HARQ process number information field mentioned above is either all 0s or all 1s;

[0222] The above MCS information field can be any of the following: all 0s, all 1s, or the value configured for network device 102;

[0223] The above FDRA information field can be any of the following: all 0s, all 1s, or the value configured by network device 102.

[0224] In some embodiments, the scheduling information indicated by the DCI above satisfies preset conditions, including at least one of the following:

[0225] The length of the frequency domain resources indicated by the aforementioned DCI does not exceed the first threshold;

[0226] The time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is greater than the first duration, or the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is not less than the first duration.

[0227] The index of the MCS indicated by the above DCI is less than the second threshold, or the index of the MCS indicated by the above DCI is not greater than the second threshold;

[0228] The modulation order indicated by the DCI above is the first modulation order;

[0229] The modulation order indicated by the above DCI is lower than the second modulation order, or the modulation order indicated by the above DCI is not higher than the second modulation order.

[0230] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0231] The following is an exemplary description of the methods described in the above embodiments.

[0232] In some embodiments, DCI-based BWP handover relies solely on the bandwidth partindicator field in the scheduling DCI for indication, resulting in low reliability.

[0233] To address the aforementioned issues, this application proposes adding additional verification conditions to the DCI for BWP handover, thereby increasing reliability and reducing the probability of erroneous BWP handover. Specifically, this includes limiting the CORESET / search space to which the BWP handover DCI belongs, setting a specific RNTI, and setting the value of a specific DCI field to a preset value or a preset range. The specific method can be as follows:

[0234] Terminal side:

[0235] The terminal receives downlink control information (DCI), which indicates a first BWP (target BWP). If the first BWP is different from the UE's currently active BWP and meets preset conditions, the terminal switches to the first BWP.

[0236] Optionally, the preset conditions are one or more of the following:

[0237] DCI is detected in a predefined or preconfigured search space;

[0238] DCI is detected in a predefined or preconfigured set of control resources, CORESET;

[0239] DCI is scrambled by a predefined or preconfigured RNTI;

[0240] The DCI information meets the preset conditions.

[0241] Optionally, the preset conditions that the DCI information meets are one or more of the following conditions:

[0242] The redundant version's RV field is all zeros;

[0243] The new data indicator field is a preset value (for example, the new data indicator field is 0 or 1, or the new data indicator field indicates that new data is being transmitted).

[0244] The HARQ process number field is a preset value (for example, the protocol predefines the HARQ process number field to be all 0s or all 1s);

[0245] The modulation and coding scheme (MCS) field has a preset value (e.g., all 0s, all 1s, or a network-preconfigured value); optionally, the network side can configure the MCS field value independently for each BWP, or the network side can configure one MCS field value to be applied to all BWPs.

[0246] The frequency domain resource allocation field is a preset value (e.g., all 0s, all 1s, or a network-preconfigured value); optionally, the network side configures a frequency domain resource allocation field value independently for each BWP, or the network side configures a frequency domain resource allocation field value to be applied to all BWPs;

[0247] The second BWP field indicates the UE's currently active BWP; the DCI in the NR has only one BWP indication field, but in this embodiment, the DCI has two BWP indication fields, one of which indicates the target BWP (first BWP) and the other indicates the currently active BWP (second BWP).

[0248] The number of resource blocks (RBs) indicated by DCI does not exceed N, where N is predefined by the protocol or preconfigured by the network.

[0249] The time interval between the data channel indicated by DCI and DCI is greater than or not less than a preset value (e.g., the preset value is S1 symbols, or S2 time slots, or time T), where the preset value is predefined or pre-configured by the network;

[0250] The value of the Modulation and Coding System (MCS) field is less than or no greater than a preset value, wherein the preset value is predefined or pre-configured by the network; optionally, the preset value is an MCS number.

[0251] The modulation order indicated by DCI is a preset modulation order, which is either predefined by the protocol or preconfigured by the network.

[0252] The modulation order indicated by DCI is lower than or not higher than the preset modulation order, wherein the modulation order is predefined by the protocol or preconfigured by the network;

[0253] The padding bits in DCI are set to preset values. Padding bits are bits added to make the number of DCI information bits reach a specific length and do not actually carry downlink control information. Optionally, the preset values ​​are predefined or configured values ​​or bit sequences, such as all 1s, 0101, ..., 1010, ...

[0254] Optionally, the terminal receives downlink data or sends uplink data within the first BWP according to the scheduling information indicated by the DCI.

[0255] This step is optional. This application's embodiments consider the following two cases:

[0256] 1) The DCI that indicates the BWP handover also indicates the scheduling information of the data channel within the target BWP;

[0257] 2) The DCI that instructs BWP handover does not schedule the data channel.

[0258] In some embodiments, if the first BWP is different from the UE's currently active BWP but does not meet the preset conditions, the UE ignores all information of the DCI.

[0259] Base station side:

[0260] The base station sends downlink control information (DCI), which indicates a first BWP (target BWP); if the first BWP is different from the UE's currently active BWP, the DCI transmission meets preset conditions.

[0261] Optionally, the preset conditions are one or more of the following:

[0262] DCI sends within a predefined or preconfigured search space.

[0263] DCI is sent within a predefined or preconfigured set of control resources (CORESET).

[0264] DCI is scrambled by a predefined or preconfigured RNTI.

[0265] The DCI information meets the preset conditions.

[0266] Optionally, the preset conditions that the DCI information meets are one or more of the following conditions:

[0267] The redundant version's RV field is all zeros;

[0268] The new data indicator field is a preset value (for example, the new data indicator field is 0 or 1, or the new data indicator field indicates that new data is being transmitted).

[0269] The HARQ process number field is a preset value (for example, the protocol predefines the HARQ process number field to be all 0s or all 1s);

[0270] The modulation and coding scheme (MCS) field has a preset value (e.g., all 0s, all 1s, or a network-preconfigured value); optionally, the network side can configure the MCS field value independently for each BWP, or the network side can configure one MCS field value to be applied to all BWPs.

[0271] The frequency domain resource allocation field is a preset value (e.g., all 0s, all 1s, or a network-preconfigured value); optionally, the network side configures a frequency domain resource allocation field value independently for each BWP, or the network side configures a frequency domain resource allocation field value to be applied to all BWPs;

[0272] The second BWP field indicates the UE's currently active BWP; the DCI in the NR has only one BWP indication field, but in this embodiment, the DCI has two BWP indication fields, one of which indicates the target BWP (first BWP) and the other indicates the currently active BWP (second BWP).

[0273] The number of resource blocks (RBs) indicated by DCI does not exceed N, where N is predefined by the protocol or preconfigured by the network.

[0274] The time interval between the data channel indicated by DCI and DCI is greater than or not less than a preset value (e.g., the preset value is S1 symbols, or S2 time slots, or time T), where the preset value is predefined or pre-configured by the network;

[0275] The value of the Modulation and Coding System (MCS) field is less than or no greater than a preset value, wherein the preset value is predefined or pre-configured by the network; optionally, the preset value is an MCS number.

[0276] The modulation order indicated by DCI is a preset modulation order, which is either predefined by the protocol or preconfigured by the network.

[0277] The modulation order indicated by DCI is lower than or not higher than the preset modulation order, wherein the modulation order is predefined by the protocol or preconfigured by the network;

[0278] The padding bits in DCI are set to preset values. Padding bits are bits added to make the number of DCI information bits reach a specific length and do not actually carry downlink control information. Optionally, the preset values ​​are predefined or configured values ​​or bit sequences, such as all 1s, 0101, ..., 1010, ...

[0279] Optionally, the base station receives uplink data or transmits downlink data according to the scheduling information indicated by the DCI within the first BWP.

[0280] This step is optional. This application's embodiments consider the following two cases:

[0281] 1) The DCI that indicates the BWP handover also indicates the scheduling information of the data channel within the target BWP;

[0282] 2) The DCI that instructs BWP handover does not schedule the data channel.

[0283] In some embodiments, unless contradictory, the optional implementations in this embodiment can be implemented as independent embodiments, and the optional implementations in this embodiment can also be combined arbitrarily. The technical features of different feasible implementations in this embodiment can be combined to form new optional implementations based on their inherent logical relationships.

[0284] It is understood that the embodiments of this application determine BWP switching based on DCI by adding additional verification conditions, thereby reducing erroneous BWP switching caused by false DCI detection. Taking setting the RV version in DCI to all zeros as an example, assuming the RV version is 2 bits, the probability of each of the four states is 1 / 4. Since the RV version of the DCI required for BWP switching must be all zeros, considering that the probability of the RV version being all zeros is 1 / 4 in the case of false DCI detection, the probability of erroneous BWP switching can be further reduced by 3 / 4 = 75%.

[0285] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.

[0286] This application also proposes an apparatus (also referred to as a communication device, etc.) for implementing any of the above methods. For example, an apparatus is proposed, which includes units or modules for implementing the steps performed by the terminal in any of the above methods. Furthermore, another apparatus is proposed, which includes units or modules for implementing the steps performed by a network device (e.g., an access network device, a core network functional node, a core network device, etc.) in any of the above methods.

[0287] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0288] In this application embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).

[0289] Figure 4A This is a schematic diagram of the structure of a terminal according to an embodiment of this application. Terminal 4100 is used to execute any of the above methods. In some embodiments, such as... Figure 4AAs shown, terminal 4100 may include at least one of a transceiver module 4101, a processing module 4102, etc. In some embodiments, the transceiver module 4101 is configured to receive downlink control information (DCI) sent by a network device, the DCI including a first information field, the first information field being used to indicate a first bandwidth portion (BWP); the processing module 4102 is configured to determine whether a handover condition is met if the first BWP is different from the terminal's currently active BWP; the processing module 4102 is further configured to determine to switch to the first BWP if the handover condition is met. Optionally, the transceiver module is configured to perform at least one of the communication steps (e.g., steps S2101, S2104, S3101, but not limited thereto) performed by terminal 101 in any of the above methods, which will not be elaborated here. Optionally, the above processing module is used to execute at least one of the other steps executed by the terminal 101 in any of the above methods (e.g., steps S2102, S2103a, S2103b, S3102, S3103, but not limited thereto), which will not be elaborated here.

[0290] Figure 4B This is a schematic diagram of the network device proposed in an embodiment of this application. Network device 4200 is used to perform any of the above methods. In some embodiments, such as... Figure 4B As shown, network device 4200 may include at least one of a transceiver module 4201, a processing module 4202, etc. In some embodiments, the transceiver module 4201 is used to send downlink control information (DCI) to a terminal. The DCI includes a first information field, which indicates a first bandwidth portion (BWP). The first BWP is different from the terminal's currently active BWP, and the transmission of the DCI satisfies a handover condition. The DCI is used to instruct the terminal to switch to the first BWP. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2104, S3101, but not limited thereto) performed by network device 102 in any of the above methods, which will not be elaborated here. Optionally, the processing module is used to perform at least one of the other steps performed by network device 102 in any of the above methods, which will not be elaborated here.

[0291] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.

[0292] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module.

[0293] In some embodiments, the processing module can be interchanged with the processor, and the transceiver module can be interchanged with the transceiver.

[0294] Figure 5A This is a schematic diagram of the structure of the communication device 5100 proposed in an embodiment of this application. The communication device 5100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 5100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0295] like Figure 5A As shown, the communication device 5100 is used to execute any of the above methods. In some embodiments, the communication device 5100 includes one or more processors 5101. The processor 5101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 5100 is used to execute any of the above methods. Optionally, one or more processors 5101 are used to invoke instructions to cause the communication device 5100 to execute any of the above methods.

[0296] In some embodiments, the communication device 5100 further includes one or more transceivers 5102. When the communication device 5100 includes one or more transceivers 5102, the transceiver 5102 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2104, S3101, but not limited thereto), and the processor 5101 performs at least one of other steps (e.g., steps S2102, S2103a, S2103b, S3102, S3103, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated together. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.

[0297] In some embodiments, the communication device 5100 further includes one or more memories 5103 for storing data and / or instructions. Optionally, one or more processors 5101 are used to invoke instructions stored in the memory 5103 to cause the communication device 5100 to perform any of the above methods. Optionally, all or part of the memory 5103 may also be located outside the communication device 5100. In an optional embodiment, the communication device 5100 may include one or more interface circuits 5104. Optionally, the interface circuit 5104 is connected to the memory 5102 and can be used to receive data and / or instructions from the memory 5102 or other devices, and can be used to send data and / or instructions to the memory 5102 or other devices. For example, the interface circuit 5104 can read data and / or instructions stored in the memory 5102 and send the data and / or instructions to the processor 5101.

[0298] The communication device 5100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 5100 described in this application is not limited thereto, and the structure of the communication device 5100 may vary. Figure 5A The limitations. The communication device may be a standalone device or part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally including storage components for storing data, programs and / or instructions; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.

[0299] Figure 5B This is a schematic diagram of the structure of chip 5200 according to an embodiment of this application. For cases where the communication device 5100 can be a chip or a chip system, please refer to... Figure 5B The diagram shown is a schematic representation of the structure of chip 5200, but it is not limited to this.

[0300] Chip 5200 includes one or more processors 5201. Chip 5200 is used to perform any of the methods described above.

[0301] In some embodiments, chip 5200 further includes one or more interface circuits 5202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 5200 further includes one or more memories 5203 for storing data and / or instructions. Optionally, all or part of the memories 5203 may be located outside of chip 5200. Optionally, the interface circuit 5202 is connected to the memories 5203, and the interface circuit 5202 can be used to receive data and / or instructions from the memories 5203 or other devices, and the interface circuit 5202 can be used to send data and / or instructions to the memories 5203 or other devices. For example, the interface circuit 5202 can read data and / or instructions stored in the memories 5203 and send the data and / or instructions to the processor 5201.

[0302] In some embodiments, the interface circuit 5202 performs at least one of the communication steps such as sending and / or receiving in the above-described method (e.g., steps S2101, S2104, and S3101, but not limited thereto). The interface circuit 5202 performing the communication steps such as sending and / or receiving in the above-described method refers, for example, to the interface circuit 5202 performing data and / or instruction interaction between the processor 5201, the chip 5200, the memory 5203, or the transceiver device. In some embodiments, the processor 5201 performs at least one of other steps (e.g., steps S2102, S2103a, S2103b, S3102, and S3103, but not limited thereto).

[0303] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.

[0304] This application also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.

[0305] This application also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.

[0306] This application also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.

Claims

1. A communication method, characterized in that, The method is executed by a terminal, and the method includes: The network device receives downlink control information (DCI), which includes a first information field that indicates a first bandwidth portion (BWP). The first BWP is different from the currently active BWP of the terminal, and it is determined whether the switching conditions are met. If the switching conditions are met, the system will switch to the first BWP.

2. The method according to claim 1, characterized in that, The DCI is used to indicate the scheduling information corresponding to the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) within the first BWP; or... The DCI is not used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP.

3. The method according to claim 1, characterized in that, The method further includes: If the switching conditions are not met, the DCI is determined to be ignored.

4. The method according to any one of claims 1-3, characterized in that, The switching conditions include at least one of the following: The DCI is received in the first search space; The DCI is received in the first control resource set CORESET; The DCI is scrambled by the first wireless network temporary identifier RNTI; The content of the DCI satisfies the first condition.

5. The method according to claim 4, characterized in that, The first condition includes at least one of the following: The second information field included in the DCI is used to indicate the current active BWP of the terminal; The third information field included in the DCI takes the first value; The scheduling information indicated by the DCI meets preset conditions; The padding bits in the DCI are set to a preset sequence.

6. The method according to claim 5, characterized in that, The third information field includes at least one of the following: Redundant version RV information field; New data indicates the NDI information field; Hybrid Automatic Repeat Request (HARQ) process number information field; Modulation and coding scheme (MCS) information field; Frequency domain resource allocation FDRA information domain.

7. The method according to claim 6, characterized in that, The third information field is either the MCS information field or the FDRA information field; for different first BWPs, the first value corresponding to the third information field is different.

8. The method according to claim 6, characterized in that, The value of the third information field is a first value, including at least one of the following: The RV information field is all zeros; The NDI information field is either all 0s or all 1s, or the NDI information field is used to indicate that the currently scheduled transport block TB is new data; The HARQ process number information field is either all 0s or all 1s; The MCS information field can be any of the following: all 0s, all 1s, or the value configured by the network device. The FDRA information field can be any of the following: all 0s, all 1s, or the value configured by the network device.

9. The method according to claim 5, characterized in that, The scheduling information indicated by the DCI meets preset conditions, including at least one of the following: The length of the frequency domain resource indicated by the DCI does not exceed a first threshold. The time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is greater than a first duration, or the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is not less than a first duration. The index of the MCS indicated by the DCI is less than the second threshold, or the index of the MCS indicated by the DCI is not greater than the second threshold. The modulation order indicated by the DCI is the first modulation order; The modulation order indicated by the DCI is lower than the second modulation order, or the modulation order indicated by the DCI is not higher than the second modulation order.

10. A communication method, characterized in that, The method is performed by a network device, and the method includes: Sending downlink control information (DCI) to the terminal, the DCI including a first information field, the first information field being used to indicate a first bandwidth portion (BWP); The first BWP is different from the currently active BWP of the terminal, and the transmission of the DCI satisfies the switching conditions; The DCI is used to instruct the terminal to switch to the first BWP.

11. The method according to claim 10, characterized in that, The DCI is used to indicate the scheduling information corresponding to the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) within the first BWP; or... The DCI is not used to indicate the scheduling information corresponding to the PDSCH or PUSCH within the first BWP.

12. The method according to any one of claims 10-11, characterized in that, The switching conditions include at least one of the following: The DCI is sent within the first search space; The DCI is sent in the first control resource set CORESET; The DCI is scrambled by the first wireless network temporary identifier RNTI; The content of the DCI satisfies the first condition.

13. The method according to claim 12, characterized in that, The first condition includes at least one of the following: The second information field included in the DCI is used to indicate the current active BWP of the terminal; The third information field included in the DCI takes the first value; The scheduling information indicated by the DCI meets preset conditions; The padding bits in the DCI are set to a preset sequence.

14. The method according to claim 13, characterized in that, The third information field includes at least one of the following: Redundant version RV information field; New data indicates the NDI information field; Hybrid Automatic Repeat Request (HARQ) process number information field; Modulation and coding scheme (MCS) information field; Frequency domain resource allocation FDRA information domain.

15. The method according to claim 14, characterized in that, The third information field is either the MCS information field or the FDRA information field; for different first BWPs, the first value corresponding to the third information field is different.

16. The method according to claim 14, characterized in that, The value of the third information field is a first value, including at least one of the following: The RV information field is all zeros; The NDI information field is either all 0s or all 1s, or the NDI information field is used to indicate that the currently scheduled transport block TB is new data; The HARQ process number information field is either all 0s or all 1s; The MCS information field can be any of the following: all 0s, all 1s, or the value configured by the network device. The FDRA information field can be any of the following: all 0s, all 1s, or the value configured by the network device.

17. The method according to claim 13, characterized in that, The scheduling information indicated by the DCI meets preset conditions, including at least one of the following: The length of the frequency domain resource indicated by the DCI does not exceed a first threshold. The time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is greater than a first duration, or the time interval between the PDSCH or PUSCH indicated by the DCI and the DCI is not less than a first duration. The index of the MCS indicated by the DCI is less than the second threshold, or the index of the MCS indicated by the DCI is not greater than the second threshold. The modulation order indicated by the DCI is the first modulation order; The modulation order indicated by the DCI is lower than the second modulation order, or the modulation order indicated by the DCI is not higher than the second modulation order.

18. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-9 and 10-17.

19. A communication system, characterized in that, The device includes a terminal and a network device, wherein the terminal is configured to implement the communication method of any one of claims 1-9, and the network device is configured to implement the communication method of any one of claims 10-17.

20. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-9 and 10-17.

21. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the communication method according to any one of claims 1-9 and 10-17.

Images