A method and device for aligning downlink control information

Abstract

The embodiments of the present disclosure disclose a method and apparatus for aligning downlink control information, which can be applied to the field of communication technology, wherein the method performed by a network device includes: aligning the payload of the first downlink control information DCI with the payload of one of the second DCIs based on a statistical method of the size of the first DCI, wherein the first DCI is a DCI for scheduling multicast scheduling MBS specific services, and the second DCI is a DCI for scheduling other services. Thus, by aligning the payload of the first DCI for scheduling MBS services with the payload of one of the second DCIs for scheduling other services, the network device avoids the total number of DCIs of different sizes ultimately sent by the network device exceeding the capacity of the terminal device.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and device for aligning downlink control information. Background Art

[0002] In the multi-broadcast scheduling (MBS) service in a communication system, the frequency domain resources used for MBS service transmission differ from the bandwidth part (BWP) of the terminal device. Consequently, the information fields contained in the downlink control information (DCI) used to schedule the MBS service may differ from those contained in the DCI used to schedule other services. This may result in different payloads for the DCI used to schedule the MBS service and other services. Consequently, the number of DCIs of different sizes configured on the network device may exceed the capabilities of the terminal device. Summary of the Invention

[0003] The embodiments of the present disclosure provide a downlink control information alignment method and apparatus thereof, which can be applied in the field of communication technology.

[0004] In a first aspect, an embodiment of the present disclosure provides a method for aligning downlink control information, which is executed by a network device. The method includes: aligning the payload of the first downlink control information DCI with the payload of one of the second DCIs according to a statistical method of the size of the first downlink control information DCI, wherein the first DCI is a DCI for scheduling multicast scheduling MBS specific services, and the second DCI is a DCI for scheduling other services.

[0005] Optionally, the aligning the payload of the first DCI with the payload of one of the second DCIs according to the statistical method of the first DCI size includes:

[0006] When the statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, the payload of the first DCI is aligned with the payload of one of the second DCIs transmitted in the common search space CSS or the terminal device-specific search space USS.

[0007] Optionally, aligning the payload of the first DCI with a payload of a second DCI transmitted in a common search space CSS or a terminal device-specific search space USS includes:

[0008] Adding padding bits to the first DCI, or adding appended bits after all valid information fields of the first DCI, or truncating the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the CSS;

[0009] or,

[0010] Adding padding bits to the first DCI, or adding appended bits after all valid information fields of the first DCI, or truncating the first DCI, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the USS;

[0011] or,

[0012] Adding padding bits to the first DCI, or adding appended bits after all valid information fields of the first DCI, or truncating the first DCI, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_1 transmitted in the USS;

[0013] or,

[0014] Adding padding bits to the first DCI, or adding appended bits after all valid information fields of the first DCI, or truncating the first DCI, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_2 transmitted in the USS;

[0015] or,

[0016] Add padding bits to the second DCI in format 1_1 or format 1_2 transmitted in the USS, or add appended bits after all valid information fields of the second DCI, or truncate the second DCI so that the payload of the processed second DCI is consistent with the payload of the first DCI.

[0017] Optionally, the aligning the payload of the first DCI with the payload of one of the second DCIs according to the statistical method of the first DCI size includes:

[0018] In a case where a statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by other RNTIs for statistical purposes, the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs.

[0019] Optionally, aligning the payload of the first DCI with the payload of the second DCI scrambled by another RNTI includes:

[0020] Determine the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of resource blocks RB included in the control resource set CORESET#0, or the number of RBs included in the initial downlink DL bandwidth part BWP;

[0021] In a case where the payload of the first DCI is different from the payload of the second DCI scrambled by the other RNTI, the first DCI is aligned with the payload of the second DCI scrambled by the other RNTI.

[0022] Optionally, the aligning the first DCI with the payload of the second DCI scrambled by the other RNTI includes:

[0023] When the payload of the first DCI is smaller than the payload of the second DCI scrambled by the other RNTI, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI;

[0024] or,

[0025] When the payload of the first DCI is greater than the payload of the second DCI scrambled by the other RNTI, the first DCI is truncated.

[0026] Optionally, the truncating the first DCI includes:

[0027] The FDRA field in the first DCI is truncated.

[0028] Optionally, also include:

[0029] When the number of RBs included in the CORESET#0 is greater than the number of RBs included in the common frequency domain resources CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI;

[0030] or,

[0031] When the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI;

[0032] Wherein, N is a positive integer.

[0033] Optionally, also include:

[0034] When the number of RBs included in the CORESET#0 is less than the number of RBs included in the CFR, scaling the frequency domain scheduling granularity of the first DCI;

[0035] or,

[0036] When the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0037] Optionally, scaling the frequency domain scheduling granularity of the first DCI includes:

[0038] Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET#0;

[0039] or,

[0040] A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

[0041] Optionally, the aligning the payload of the first DCI with the payload of one of the second DCIs according to the statistical method of the first DCI size includes:

[0042] When the statistical method for the size of the first DCI is to classify the first DCI as C-RNTI-scrambled DCI for statistics and other second DCIs are not aligned, the payload of the first DCI is aligned with the payload of one of the second DCIs according to the format of the first DCI.

[0043] Optionally, aligning the payload of the first DCI with the payload of one of the second DCIs according to the format of the first DCI includes:

[0044] When the format of the first DCI is format1_0, determine the size of the FDRA field in the first DCI according to the number of RBs included in CORESET#0 or initialDL BWP;

[0045] When the payload of the first DCI is different from the payload of the second DCI encrypted by other RNTIs, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or part of the information fields are truncated, so that the payload of the first DCI is aligned with the payload of the second DCI encrypted by other RNTIs.

[0046] Optionally, also include:

[0047] When the number of RBs included in the CORESET#0 is greater than the number of RBs included in the CFR, or when the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI, where N is a positive integer;

[0048] or,

[0049] When the number of RBs included in the CORESET#0 is smaller than the number of RBs included in the CFR, or when the number of RBs included in the initialDL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0050] Optionally, scaling the frequency domain scheduling granularity of the first DCI includes:

[0051] Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET 0;

[0052] or,

[0053] A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

[0054] Optionally, aligning the payload of the first DCI with the payload of one of the second DCIs according to the format of the first DCI includes:

[0055] When the format of the first DCI is format1_1 or format1_2, determine the size of the FDRA field in the first DCI according to the number of RBs included in the CFR;

[0056] The payload of the first DCI is aligned with the payload of one of the second DCIs.

[0057] Optionally, aligning the payload of the first DCI with the payload of one of the second DCIs includes:

[0058] In a case where the current cell is configured with a second DCI format identical to the first DCI format, aligning the payload of the first DCI with the payload of the second DCI format identical to the first DCI format and scrambled by the C-RNTI;

[0059] or,

[0060] In a case where the current cell is not configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of a specified second DCI, wherein the specified second DCI is a DCI having a format of format1_1 or format1_2.

[0061] Optionally, aligning the payload of the first DCI with the payload of one of the second DCIs includes:

[0062] When the payload of the first DCI is smaller than the payload of one of the second DCIs, padding bits are added to the first DCI, or appended bits are added after the information field of the first DCI;

[0063] or,

[0064] In a case where the payload of the first DCI is greater than the payload of one of the second DCIs, the first DCI is truncated.

[0065] Optionally, the adding padding bits to the first DCI, or adding appended bits after the information field of the first DCI, includes:

[0066] Adding padding bits to the FDRA field of the first DCI;

[0067] Optionally, the truncating the first DCI includes:

[0068] The FDRA field in the first DCI is truncated.

[0069] In a second aspect, an embodiment of the present disclosure provides another method for aligning downlink control information, which is executed by a terminal device. The method includes: determining an alignment method of a payload of the first downlink control information DCI with a payload of one of the second DCIs based on a statistical method of the size of the first downlink control information DCI, wherein the first DCI is a DCI for scheduling multicast scheduling MBS specific services, and the second DCI is a DCI for scheduling other services.

[0070] Optionally, determining, based on a statistical method of the first DCI size, an alignment method of the payload of the first DCI and the payload of one of the second DCIs includes:

[0071] When the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI, aligning a payload of the first DCI with a payload of one of the second DCIs transmitted in the CSS;

[0072] or,

[0073] In a case where the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI, determining that a payload of the first DCI is aligned with a payload of one of the second DCIs transmitted in the USS;

[0074] or,

[0075] In a case where the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI, determining, according to a format of the first DCI, a second DCI aligned with the first DCI;

[0076] or,

[0077] In a case where a statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by other RNTIs for statistical purposes, it is determined that the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs.

[0078] Optionally, the determining, according to the format of the first DCI, a second DCI aligned with the first DCI includes:

[0079] When the format of the first DCI is format1_0, determine that the second DCI aligned with the payload of the first DCI is the second DCI scrambled by another RNTI;

[0080] or,

[0081] When the format of the first DCI is format1_1 or format1_2, and the current cell is configured with a second DCI having the same format as the first DCI, determining that the second DCI aligned with the payload of the first DCI is a C-RNTI-scrambled second DCI;

[0082] or,

[0083] When the format of the first DCI is format1_1 or format1_2, and the current cell is not configured with a second DCI with the same format as the first DCI, the second DCI aligned with the payload of the first DCI is determined to be a designated second DCI, wherein the designated second DCI is a DCI with a format of format1_1 or format1_2.

[0084] Optionally, also include:

[0085] When the number of RBs included in CORESET#0 is greater than the number of RBs included in CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI;

[0086] or,

[0087] When the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI;

[0088] Wherein, N is a positive integer.

[0089] Optionally, also include:

[0090] When the number of RBs included in the CORESET#0 is less than the number of RBs included in the CFR, scaling the frequency domain scheduling granularity of the first DCI;

[0091] or,

[0092] When the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0093] Optionally, scaling the frequency domain scheduling granularity of the first DCI includes:

[0094] Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET 0;

[0095] or,

[0096] A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the initial DL BWP.

[0097] In a third aspect, an embodiment of the present disclosure provides a communication device that implements some or all of the functions of the network device described in the method described in the first aspect above. For example, the functions of the communication device may include some or all of the functions in the embodiments of the present disclosure, or may include the functions of implementing any one of the embodiments of the present disclosure separately. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0098] In a fourth aspect, an embodiment of the present disclosure provides another communication device that has some or all of the functions of the terminal device in the method example described in the second aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of implementing any one of the embodiments of the present disclosure alone. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0099] In a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the first aspect is executed.

[0100] In a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor. When the processor calls a computer program in a memory, the method described in the second aspect is executed.

[0101] In a seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, wherein a computer program is stored in the memory; when the computer program is executed by the processor, the communication device executes the method described in the first aspect above.

[0102] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, wherein a computer program is stored in the memory; when the computer program is executed by the processor, the communication device executes the method described in the second aspect above.

[0103] In a ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the first aspect above.

[0104] In the tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit, wherein the interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions to enable the device to execute the method described in the second aspect above.

[0105] In the eleventh aspect, an embodiment of the present disclosure provides a communication system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0106] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above-mentioned network device, and when the instructions are executed, the method described in the above-mentioned first aspect is implemented.

[0107] In a thirteenth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions for the above-mentioned terminal device, and when the instructions are executed, the method described in the above-mentioned second aspect is implemented.

[0108] In a fourteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0109] In a fifteenth aspect, the present disclosure further provides a computer program product comprising a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0110] In a sixteenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a network device in implementing the functions described in the first aspect, such as determining or processing at least one of the data and information described in the aforementioned method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the network device. The chip system may consist of a single chip or may include a chip and other discrete components.

[0111] In a seventeenth aspect, the present disclosure provides a chip system comprising at least one processor and an interface for supporting a terminal device in implementing the functions described in the second aspect, such as determining or processing at least one of the data and information described in the aforementioned method. In one possible design, the chip system further comprises a memory for storing computer programs and data necessary for the terminal device. The chip system may consist of a chip alone or may include a chip and other discrete components.

[0112] In an eighteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the first aspect above.

[0113] In a nineteenth aspect, the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the method described in the second aspect above.

[0114] Based on the above embodiments, the network device aligns the payload of the first downlink control information DCI with the payload of one of the second DCIs according to the statistical method of the size of the first downlink control information DCI, wherein the first DCI is a DCI for scheduling multicast scheduling MBS specific services, and the second DCI is a DCI for scheduling other services. Therefore, by aligning the payload of the first DCI for scheduling MBS services with the payload of one of the second DCIs for scheduling other services, the network device avoids the total number of DCIs of different sizes ultimately sent by the network device exceeding the capacity of the terminal device. BRIEF DESCRIPTION OF THE DRAWINGS

[0115] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0116] Figure 1 is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0117] Figure 2 This is a flowchart of a method for aligning downlink control information provided by an embodiment of the present disclosure;

[0118] Figure 3 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0119] Figure 4 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0120] Figure 5 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0121] Figure 6 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0122] Figure 7 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0123] Figure 8 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0124] Figure 9 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0125] Figure 10 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0126] Figure 11 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0127] Figure 12 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0128] Figure 13 is a flowchart of a method for aligning downlink control information provided by another embodiment of the present disclosure;

[0129] Figure 14 is a structural diagram of a communication device according to an embodiment of the present disclosure;

[0130] Figure 15 is a structural diagram of a communication device according to another embodiment of the present disclosure;

[0131] Figure 16 It is a schematic structural diagram of a chip according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0132] In order to better understand a downlink control information alignment method disclosed in an embodiment of the present disclosure, a communication system to which the embodiment of the present disclosure is applicable is first described below.

[0133] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure. The communication system may include but is not limited to a network device, a terminal device, Figure 1 The number and form of devices shown are for example only and do not constitute a limitation on the embodiments of the present disclosure. In actual applications, two or more network devices and two or more terminal devices may be included. Figure 1 The communication system shown includes a network device 11 and a terminal device 12 as an example.

[0134] It should be noted that the technical solutions of the embodiments of the present disclosure can be applied to various communication systems, such as long-term evolution (LTE) systems, fifth-generation (5G) mobile communication systems, 5G new radio (NR) systems, or other future new mobile communication systems.

[0135] The network device 11 in the embodiment of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network device 11 can be an evolved NodeB (eNB), a transmission point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the network device. The network device provided in the embodiment of the present disclosure can be composed of a centralized unit (CU) and a distributed unit (DU), wherein the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the network device, such as the base station, and the functions of some protocol layers are placed in the CU for centralized control, and the functions of the remaining part or all of the protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0136] The terminal device 12 in the embodiment of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can also be called a terminal device (terminal), user equipment (UE), mobile station (MS), mobile terminal device (MT), etc. The terminal device can be a car with communication function, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation safety (transportation safety), a wireless terminal device in smart city (smart city), a wireless terminal device in smart home (smart home), etc. The embodiment of the present disclosure does not limit the specific technology and specific device form adopted by the terminal device.

[0137] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0138] The downlink control information alignment method and device provided by the present disclosure are described in detail below with reference to the accompanying drawings.

[0139] See Figure 2 , Figure 2 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 2 As shown, the method may include but is not limited to the following steps:

[0140] Step 21, according to the statistical method of the size of the first downlink control information DCI, align the payload of the first DCI with the payload of one of the second DCIs, wherein the first DCI is the DCI used to schedule multicast scheduling MBSspecific services, and the second DCI is the DCI used to schedule other services.

[0141] It should be noted that in scheduling MBS services, the frequency domain resource allocation (FDRA) field of the first DCI used to schedule MBS services is determined based on the common frequency domain resources (CFR) on the network device side, and the information field contained in the first DCI may be different from the information field in the second DCI. Therefore, the total number of DCI sizes configured by the network device may exceed the maximum capacity of 3+1 DCIs that the terminal device can blindly detect. At this time, it is necessary to align the payload of the first DCI with the payload of one of the second DCIs so that the number of DCIs that the terminal device needs to detect does not exceed the limit of the DCI budget 3+1.

[0142] In the present disclosure, the second DCI for scheduling other services may be aligned first according to the DCI alignment operation in Rel-15 / 16, and then the payload of the first DCI may be aligned with the payload of one of the second DCIs. Alternatively, the payload of the first DCI may be aligned with the payload of one of the second DCIs during the process of aligning the payload of the second DCI.

[0143] Optionally, when the payload of the first DCI and the payload of the second DCI are different, the network device may align the payload of the first DCI with the payload of one of the second DCIs according to a statistical method of the size of the first DCI.

[0144] Optionally, when the statistical method for the first DCI size is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier (Cell-Radio Network Temporary Identifier, C-RNTI) and other second DCIs have been aligned, the payload of the first DCI is aligned with the payload of one of the second DCIs transmitted in the common search space (Common Search Space, CSS) or the terminal device-specific search space (User Search Space, USS).

[0145] Optionally, when the statistical method of the first DCI size is to classify the first DCI as DCI scrambled by other RNTIs for statistics, the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs.

[0146] Optionally, when the statistical method for the first DCI size is to classify the first DCI as C-RNTI-scrambled DCI for statistics and other second DCIs are not aligned, the payload of the first DCI is aligned with the payload of one of the second DCIs according to the format of the first DCI.

[0147] By implementing the disclosed embodiments, a network device aligns the payload of a first downlink control information (DCI) with the payload of one of the second DCIs based on a statistical method for calculating the size of the first downlink control information (DCI), where the first DCI is used to schedule a multicast MBS-specific service, and the second DCI is used to schedule other services. Thus, by aligning the payload of the first DCI used to schedule the MBS service with the payload of one of the second DCIs used to schedule other services, the network device avoids ultimately sending a total of DCIs of different sizes that exceed the capabilities of the terminal device.

[0148] See Figure 3 , Figure 3 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 3 As shown, the method may include but is not limited to the following steps:

[0149] In step 31, when the statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or the first DCI is truncated, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the CSS.

[0150] In an embodiment of the present disclosure, the network device configures an MBS service for the terminal device and schedules it through DCI format 1_0 encrypted by G-RNTI. If the size statistics of DCI format 1_0 encrypted by G-RNTI are within 3 in DCI budget 3+1, the first DCI is classified as DCI encrypted by C-RNTI for size statistics.

[0151] When the first DCI is classified as C-RNTI-scrambled DCI and the size of the DCI is counted, the DCI alignment operation in Rel-16 can be first performed to align the second DCI format 0_0 and the second DCI format 1_0 transmitted in the CSS and USS, the second DCI format 0_1 ​​and the second DCI format 1_1 transmitted in the USS, and the second DCI format 0_2 and the second DCI format 1_2 transmitted in the USS to meet the 3+1 DCI budget requirement. Subsequently, if the number of different sizes of the second DCI scrambled by C-RNTI configured in the cell reaches 3, and the size of the first DCI is different from the size of any second DCI, the payload of the first DCI is aligned with the payload of the second DCI format 1_0 transmitted in the CSS.

[0152] Optionally, if the payload of the first DCI is smaller than the payload of the DCI in format 1_0 transmitted in the CSS, padding bits may be added to the first DCI, or appended bits may be added after all valid information fields of the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the CSS.

[0153] Optionally, if the payload of the first DCI is larger than the payload of the DCI in format1_0 transmitted in the CSS, the first DCI may be truncated so that the payload of the processed first DCI is consistent with the payload of the DCI in format1_0 transmitted in the CSS.

[0154] Optionally, if the payload of the first DCI is larger than the payload of the DCI in format 1_0 transmitted in the CSS, it may be preferred to truncate the FDRA field of the first DCI.

[0155] For example, if the payload of the first DCI is N bits larger than the DCI formatted in format1_0 transmitted in the CSS, the network device will preferentially delete the highest N bits of the FDRA field in the first DCI when sending the first DCI to the terminal device, thereby completing the truncation of the FDRA field in the first DCI and the entire DCI format.

[0156] Optionally, when determining the length of the FDRA field of the first DCI, the bit width may be determined based on the number of resource blocks (RBs) included in the CFR. Alternatively, the bit width may be determined based on the number of resource blocks (RBs) included in the control resource set (CORESET#0). Alternatively, the bit width may be determined based on the number of RBs included in the initial downlink bandwidth part (BWP).

[0157] Optionally, after the FDRA field of the first DCI is truncated, the frequency domain scheduling strength can be scaled. For example, after the FDRA field of the first DCI is truncated by N bits, the frequency domain resource scheduling granularity can be changed from the original M consecutive RBs to 2 N ×M consecutive RBs.

[0158] By implementing the embodiments of the present disclosure, when the network device counts the size of the first DCI by classifying the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, the network device adds padding bits to the first DCI, or adds appended bits after all valid information fields of the first DCI, or truncates the first DCI, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the CSS. Therefore, by aligning the payload of the first DCI used to schedule the MBS service with the payload of the DCI in format 1_0 transmitted in the CSS, the total number of DCIs of different sizes ultimately sent by the network device is prevented from exceeding the capacity of the terminal device.

[0159] See Figure 4 , Figure 4 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 4 As shown, the method may include but is not limited to the following steps:

[0160] In step 41, when the statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or the first DCI is truncated, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the USS.

[0161] In an embodiment of the present disclosure, the network device configures an MBS service for the terminal device and schedules it through DCI format 1_0 encrypted by G-RNTI. If the size statistics of DCI format 1_0 encrypted by G-RNTI are within 3 in DCI budget 3+1, the first DCI is classified as DCI encrypted by C-RNTI for size statistics.

[0162] When the first DCI is classified as C-RNTI-scrambled DCI and the size of the DCI is counted, the DCI alignment operation in Rel-16 can be first performed to align the second DCI format 0_0 and the second DCI format 1_0 transmitted in the CSS and USS, the second DCI format 0_1 ​​and the second DCI format 1_1 transmitted in the USS, and the second DCI format 0_2 and the second DCI format 1_2 transmitted in the USS to meet the 3+1 DCI budget requirement. Subsequently, if the number of different sizes of the second DCI scrambled by C-RNTI configured in the cell has reached 3, and the size of the first DCI is different from the size of any of the second DCIs, the payload of the first DCI is aligned with the payload of the second DCI format 1_0 transmitted in the USS.

[0163] Optionally, if the payload of the first DCI is smaller than the payload of the DCI in format 1_0 transmitted in the USS, padding bits may be added to the first DCI, or appended bits may be added after all valid information fields of the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the USS.

[0164] Optionally, if the payload of the first DCI is larger than the payload of the DCI in format 1_0 transmitted in the USS, the first DCI may be truncated so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the USS.

[0165] Optionally, if the payload of the first DCI is larger than the payload of the DCI in the format 1_0 transmitted in the USS, it may be preferred to truncate the FDRA field of the first DCI.

[0166] For example, if the payload of the first DCI is larger than the DCI format 1_0 transmitted in the USS by N bits, the network device will preferentially delete the highest N bits of the FDRA field in the first DCI when sending the first DCI to the terminal device, thereby completing the truncation of the FDRA field in the first DCI and the entire DCI format.

[0167] Optionally, when determining the length of the FDRA field of the first DCI, the bit width may be determined based on the number of resource blocks (RBs) included in the CFR. Alternatively, the bit width may be determined based on the number of resource blocks (RBs) included in the control resource set (CORESET#0). Alternatively, the bit width may be determined based on the number of RBs included in the initial downlink bandwidth part (BWP).

[0168] Optionally, after the FDRA field of the first DCI is truncated, the frequency domain scheduling strength can be scaled. For example, after the FDRA field of the first DCI is truncated by N bits, the frequency domain resource scheduling granularity can be changed from the original M consecutive RBs to 2 N ×M consecutive RBs.

[0169] By implementing the embodiment of the present disclosure, when the network device counts the size of the first DCI by classifying the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or the first DCI is truncated, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the USS. Therefore, by aligning the payload of the first DCI used to schedule the MBS service with the payload of the DCI in format 1_0 transmitted in the USS, the total number of DCIs of different sizes ultimately sent by the network device is prevented from exceeding the capacity of the terminal device.

[0170] See Figure 5 , Figure 5 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 5 As shown, the method may include but is not limited to the following steps:

[0171] In step 51, when the statistical method of the first DCI size is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or the first DCI is truncated so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_1 transmitted in the USS.

[0172] In an embodiment of the present disclosure, the network device configures an MBS service for the terminal device and schedules it through DCI format 1_1 encrypted by G-RNTI. If the size statistics of DCI format 1_1 encrypted by G-RNTI are within 3 in DCI budget 3+1, the first DCI is classified as DCI encrypted by C-RNTI for size statistics.

[0173] When the first DCI is classified as C-RNTI-scrambled DCI and the size of the DCI is counted, the DCI alignment operation in Rel-16 can be first performed to align the second DCI format 0_0 and the second DCI format 1_0 transmitted in the CSS and USS, the second DCI format 0_1 ​​and the second DCI format 1_1 transmitted in the USS, and the second DCI format 0_2 and the second DCI format 1_2 transmitted in the USS to meet the 3+1 DCI budget requirement. Subsequently, if the number of different sizes of the second DCI scrambled by C-RNTI configured in the cell reaches 3, and the size of the first DCI is different from the size of any of the second DCIs, the payload of the first DCI is aligned with the payload of the second DCI format 1_1 transmitted in the USS.

[0174] Optionally, if the payload of the first DCI is smaller than the payload of the DCI in format 1_1 transmitted in the USS, padding bits may be added to the first DCI, or appended bits may be added after all valid information fields of the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_1 transmitted in the USS.

[0175] Optionally, if the payload of the first DCI is larger than the payload of the DCI in format1_1 transmitted in the USS, the first DCI may be truncated so that the payload of the processed first DCI is consistent with the payload of the DCI in format1_1 transmitted in the USS.

[0176] Optionally, if the payload of the first DCI is larger than the payload of the DCI in the format 1_1 transmitted in the USS, it may be preferred to truncate the FDRA field of the first DCI.

[0177] For example, if the payload of the first DCI is N bits larger than the DCI formatted in format1_1 transmitted in the USS, the network device will preferentially delete the highest N bits of the FDRA field in the first DCI when sending the first DCI to the terminal device, thereby completing the truncation of the FDRA field in the first DCI and the entire DCI format.

[0178] Optionally, when determining the length of the FDRA field of the first DCI, the bit width may be determined based on the number of resource blocks (RBs) included in the CFR. Alternatively, the bit width may be determined based on the number of resource blocks (RBs) included in the control resource set (CORESET#0). Alternatively, the bit width may be determined based on the number of RBs included in the initial downlink bandwidth part (BWP).

[0179] Optionally, after the FDRA field of the first DCI is truncated, the frequency domain scheduling strength can be scaled. For example, after the FDRA field of the first DCI is truncated by N bits, the frequency domain resource scheduling granularity can be changed from the original M consecutive RBs to 2 N ×M consecutive RBs.

[0180] By implementing the embodiments of the present disclosure, when the network device counts the size of the first DCI by classifying the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or the first DCI is truncated, so that the payload of the processed first DCI is consistent with the payload of the DCI in the format 1_1 transmitted in the USS. Therefore, by aligning the payload of the first DCI used to schedule the MBS service with the payload of the DCI in the format 1_1 transmitted in the USS, the total number of DCIs of different sizes ultimately sent by the network device is prevented from exceeding the capacity of the terminal device.

[0181] See Figure 6 , Figure 6 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 6 As shown, the method may include but is not limited to the following steps:

[0182] Step 61, when the statistical method of the first DCI size is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_2 transmitted in the USS.

[0183] In an embodiment of the present disclosure, the network device configures the MBS service for the terminal device and schedules it through the DCI format 1_2 encrypted by G-RNTI. If the size statistics of the DCI format 1_2 encrypted by G-RNTI are within 3 in the DCI budget 3+1, the first DCI is classified as the DCI encrypted by C-RNTI for size statistics.

[0184] When the first DCI is classified as C-RNTI-scrambled DCI and the size of the DCI is counted, the DCI alignment operation in Rel-16 can be first performed to align the second DCI format 0_0 and the second DCI format 1_0 transmitted in the CSS and USS, the second DCI format 0_1 ​​and the second DCI format 1_1 transmitted in the USS, and the second DCI format 0_2 and the second DCI format 1_2 transmitted in the USS to meet the 3+1 DCI budget requirement. Subsequently, if the number of different sizes of the second DCI scrambled by C-RNTI configured in the cell reaches 3, and the size of the first DCI is different from the size of any second DCI, the payload of the first DCI is aligned with the payload of the second DCI format 1_2 transmitted in the USS.

[0185] Optionally, if the payload of the first DCI is smaller than the payload of the DCI in format 1_2 transmitted in the USS, padding bits may be added to the first DCI, or bits may be added after all valid information fields of the first DCI to increase appended bits, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_2 transmitted in the USS.

[0186] Optionally, if the payload of the first DCI is larger than the payload of the DCI in format 1_2 transmitted in the USS, the first DCI may be truncated so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_2 transmitted in the USS.

[0187] Optionally, if the payload of the first DCI is larger than the payload of the DCI in the format 1_2 transmitted in the USS, it may be preferred to truncate the FDRA field of the first DCI.

[0188] For example, if the payload of the first DCI is larger than the DCI format 1_2 transmitted in the USS by N bits, the network device will preferentially delete the highest N bits of the FDRA field in the first DCI when sending the first DCI to the terminal device, thereby completing the truncation of the FDRA field in the first DCI and the entire DCI format.

[0189] Optionally, when determining the length of the FDRA field of the first DCI, the bit width may be determined based on the number of resource blocks (RBs) included in the CFR. Alternatively, the bit width may be determined based on the number of resource blocks (RBs) included in the control resource set (CORESET#0). Alternatively, the bit width may be determined based on the number of RBs included in the initial downlink bandwidth part (BWP).

[0190] Optionally, after the FDRA field of the first DCI is truncated, the frequency domain scheduling strength can be scaled. For example, after the FDRA field of the first DCI is truncated by N bits, the frequency domain resource scheduling granularity can be changed from the original M consecutive RBs to 2 N ×M consecutive RBs.

[0191] By implementing the embodiments of the present disclosure, when the network device counts the size of the first DCI by classifying the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or the first DCI is truncated, so that the payload of the processed first DCI is consistent with the payload of the DCI in the format 1_2 transmitted in the USS. Therefore, by aligning the payload of the first DCI used to schedule the MBS service with the payload of the DCI in the format 1_2 transmitted in the USS, the total number of DCIs of different sizes ultimately sent by the network device is prevented from exceeding the capacity of the terminal device.

[0192] See Figure 7 , Figure 7 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 7 As shown, the method may include but is not limited to the following steps:

[0193] In step 71, when the statistical method for the first DCI size is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, padding bits are added to the second DCI in the format 1_1 or format 1_2 transmitted in the USS, or appended bits are added after all valid information fields of the above-mentioned second DCI, or the above-mentioned second DCI is truncated, so that the payload of the processed second DCI is consistent with the payload of the first DCI.

[0194] In an embodiment of the present disclosure, the network device configures an MBS service for the terminal device and schedules it through DCI format 1_1 or DCI format 1_2 encrypted by G-RNTI. If the size statistics of DCI format 1_1 or DCI format 1_2 encrypted by G-RNTI are within 3 in DCI budget 3+1, the first DCI is classified as DCI encrypted by C-RNTI for size statistics.

[0195] When the first DCI is classified as C-RNTI-scrambled DCI and the size of the DCI is counted, the DCI alignment operation in Rel-16 can be first performed to align the second DCI format 0_0 and the second DCI format 1_0 transmitted in the CSS and USS, the second DCI format 0_1 ​​and the second DCI format 1_1 transmitted in the USS, and the second DCI format 0_2 and the second DCI format 1_2 transmitted in the USS to meet the 3+1 DCI budget requirement. Subsequently, if the number of different sizes of the second DCI scrambled by C-RNTI configured in the cell reaches three, and the size of the first DCI is different from the size of any of the second DCIs, the payload of the first DCI is aligned with the payload of the second DCI format 1_1 or 1_2 transmitted in the USS.

[0196] Optionally, if the payload of the first DCI is smaller than the payload of the second DCI in format 1_1 or format 1_2 transmitted in the USS, padding bits may be added to the second DCI in format 1_1 or format 1_2, or appended bits may be added after all valid information fields of the second DCI in format 1_1 or format 1_2 so that the payload of the processed second DCI is consistent with the payload of the first DCI.

[0197] Optionally, if the payload of the first DCI is larger than the payload of the DCI in format1_2 transmitted in the USS, the second DCI in format1_1 or format1_2 transmitted in the USS may be truncated so that the payload of the processed second DCI is consistent with the payload of the first DCI.

[0198] Optionally, when determining the length of the FDRA field of the first DCI, the bit width may be determined based on the number of resource blocks (RBs) included in the CFR. Alternatively, the bit width may be determined based on the number of resource blocks (RBs) included in the control resource set (CORESET#0). Alternatively, the bit width may be determined based on the number of RBs included in the initial downlink bandwidth part (BWP).

[0199] By implementing the embodiment of the present disclosure, when the network device classifies the first DCI as a DCI scrambled by the cell radio network temporary identifier C-RNTI and performs statistics, and other second DCIs have been aligned, padding bits are added to the second DCI in the format 1_1 or format 1_2 transmitted in the USS, or appended bits are added after all valid information fields of the above-mentioned second DCI, or the above-mentioned second DCI is shortened, so that the payload of the processed second DCI is consistent with the payload of the first DCI. Thus, by aligning the payload of the DCI in the format 1_1 or format 1_2 transmitted in the USS with the payload of the first DCI used to schedule MBS services, the network device avoids the total number of DCIs of different sizes ultimately sent by the network device exceeding the capacity of the terminal device.

[0200] See Figure 8 , Figure 8 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 8 As shown, the method may include but is not limited to the following steps:

[0201] Step 81, when the statistical method of the first DCI size is to classify the first DCI as DCI scrambled by other RNTIs for statistics, determine the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of resource blocks RB included in the control resource set CORESET#0, or the number of RBs included in the initial downlink DL bandwidth part BWP.

[0202] In an embodiment of the present disclosure, the network device configures an MBS service for the terminal device and schedules it through DCI format 1_0 scrambled by G-RNTI. If the size statistics of DCI format 1_1 or DCI format 1_2 scrambled by G-RNTI are within 1 in DCI budget 3+1, the first DCI is classified as DCI scrambled by other RNTIs for size statistics.

[0203] Optionally, determining the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of resource blocks RBs included in the control resource set CORESET#0 may include:

[0204] When the number of RBs included in CORESET#0 is greater than the number of RBs included in the common frequency domain resources CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI, where N is a positive number.

[0205] Alternatively, when the number of RBs included in CORESET#0 is smaller than the number of RBs included in CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0206] Optionally, the scaling factor for scaling the frequency domain scheduling granularity of the first DCI may be determined according to the ratio of the number of RBs included in the CFR to the number of RBs included in CORESET#0.

[0207] Optionally, determining the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of RBs included in the initial downlink DL bandwidth part BWP may include:

[0208] When the number of RBs included in the initialDL BWP is greater than the number of RBs included in the CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI.

[0209] Alternatively, when the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0210] Optionally, the scaling factor may be determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

[0211] Step 82: When the payload of the first DCI is different from the payload of the second DCI scrambled by the other RNTI, align the payload of the first DCI with the payload of the second DCI scrambled by the other RNTI.

[0212] It should be noted that if, after determining the size of the FDRA field of the first DCI, the payload of the first DCI is still different from the payload of the second DCI encrypted with other RNTIs, padding bits can be added to the first DCI, or appended bits can be added after all valid information fields of the first DCI, or the first DCI can be truncated to align the payload of the processed first DCI with the payload of the second DCI encrypted with other RNTIs.

[0213] Optionally, when the payload of the first DCI is smaller than the payload of the second DCI scrambled by other RNTIs, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI.

[0214] Alternatively, when the payload of the first DCI is greater than the payload of the second DCI scrambled by other RNTIs, the first DCI is truncated.

[0215] Optionally, when the payload of the first DCI is greater than the payload of the second DCI scrambled by other RNTIs, the FDRA field in the first DCI may be preferentially truncated.

[0216] By implementing the embodiments of the present disclosure, when the statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by other RNTIs, the network device determines the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of resource blocks RB included in the control resource set CORESET#0, or the number of RBs included in the initial downlink DL bandwidth part BWP, and then aligns the payload of the first DCI with the payload of the second DCI scrambled by other RNTIs when the payload of the first DCI is different from the payload of the second DCI scrambled by other RNTIs. Thus, by aligning the payload of the first DCI used for scheduling MBS services with the payload of the second DCI scrambled by other RNTIs, the network device avoids the total number of DCIs of different sizes ultimately sent by the network device exceeding the capabilities of the terminal device.

[0217] See Figure 9 , Figure 9 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 9 As shown, the method may include but is not limited to the following steps:

[0218] Step 91: When the statistical method for the first DCI size is to classify the first DCI as C-RNTI-scrambled DCI for statistics, the format of the first DCI is format1_0, and other second DCIs are not aligned, determine the size of the FDRA field in the first DCI according to the number of RBs included in CORESET#0 or initialDL BWP.

[0219] In an embodiment of the present disclosure, the network device configures the MBS service for the terminal device and schedules it through the DCI format encrypted by G-RNTI. If the size statistics of the DCI format encrypted by G-RNTI are within 3 in the DCI budget3+1, the first DCI is classified as the DCI encrypted by C-RNTI for size statistics.

[0220] In an embodiment of the present disclosure, while performing alignment operations between the second DCI format0_0 and the second DCIformat1_0 transmitted in the CSS and USS, the second DCI format 0_1 ​​and the second DCI format 1_1 transmitted in the USS, and the second DCI format 0_2 and the second DCI format1_2 transmitted in the USS, the first DCI used to schedule the MBS service is aligned with the payload of the second DCI scrambled by other RNTIs, so that the DCI configured by the network device for the terminal device meets the 3+1 DCI budget requirement.

[0221] Optionally, when the number of RBs included in CORESET#0 is greater than the number of RBs included in CFR, or when the number of RBs included in initialDL BWP is greater than the number of RBs included in CFR, the frequency domain resource allocation information is determined based on the N highest bits or the N lowest bits in the first DCI, where N is a positive integer.

[0222] Alternatively, when the number of RBs included in CORESET#0 is smaller than the number of RBs included in CFR, or when the number of RBs included in the initial DL BWP is smaller than the number of RBs included in CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0223] Optionally, the scaling factor is determined based on the ratio of the number of RBs included in the CFR to the number of RBs included in CORESET 0. Alternatively, the scaling factor is determined based on the ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

[0224] Step 92, when the payload of the first DCI is different from the payload of the second DCI encrypted by other RNTIs, add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate part of the information fields, so that the payload of the first DCI is aligned with the payload of the second DCI encrypted by other RNTIs.

[0225] By implementing the embodiments of the present disclosure, the network device determines the size of the FDRA field in the first DCI according to the number of RBs included in CORESET#0 or initialDL BWP when the statistical method for the size of the first DCI is to classify the first DCI as a C-RNTI-scrambled DCI for statistics, the format of the first DCI is format1_0, and the alignment of other second DCIs is not completed. Then, when the payload of the first DCI is different from the payload of the second DCI scrambled by other RNTIs, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or part of the information field is truncated, so that the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs. Thus, the network device avoids the total DCI size ultimately sent by the network device from exceeding the capacity of the terminal device by aligning the payload of the first DCI used to schedule MBS services with the payload of the second DCI scrambled by other RNTIs.

[0226] See Figure 10 , Figure 10 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 10 As shown, the method may include but is not limited to the following steps:

[0227] Step 101, when the statistical method for the first DCI size is to classify the first DCI as C-RNTI-scrambled DCI for statistics, the format of the first DCI is format1_1, and other second DCIs are not aligned, determine the size of the FDRA field in the first DCI according to the number of RBs included in the CFR.

[0228] Step 102: Align the payload of the first DCI with the payload of one of the second DCIs.

[0229] Optionally, when the current cell is configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of the second DCI having the same format and being C-RNTI-scrambled.

[0230] Alternatively, when the current cell is not configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of the designated second DCI, where the designated second DCI is a DCI having a format of format1_1.

[0231] Optionally, when the payload of the first DCI is smaller than the payload of the second DCI in format1_1, padding bits are added to the first DCI, or appended bits are added after the information field of the first DCI to align the payload of the first DCI with the payload of the second DCI in format1_1.

[0232] Alternatively, when the payload of the first DCI is greater than the payload of the second DCI in the format 1_1, the first DCI is truncated so that the payload of the first DCI is aligned with the payload of the second DCI in the format 1_1.

[0233] Optionally, when the payload of the first DCI is smaller than the payload of the second DCI in format1_1, padding bits may be preferentially added to the FDRA field of the first DCI.

[0234] Optionally, when the payload of the first DCI is greater than the payload of the second DCI in format 1_1, the FDRA field in the first DCI may be preferentially truncated.

[0235] By implementing the embodiments of the present disclosure, when the network device classifies the first DCI as C-RNTI-scrambled DCI for statistics, the format of the first DCI is format1_1, and other second DCIs are not aligned, the network device determines the size of the FDRA field in the first DCI based on the number of RBs included in the CFR, and then aligns the payload of the first DCI with the payload of one of the second DCIs. As a result, when the network device does not complete the alignment of other second DCIs, the payload of the first DCI used to schedule the MBS service is aligned with the payload of one of the second DCIs, thereby avoiding the total number of DCIs of different sizes ultimately sent by the network device exceeding the capabilities of the terminal device.

[0236] See Figure 11 , Figure 11 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a network device. Figure 11 As shown, the method may include but is not limited to the following steps:

[0237] Step 111, when the statistical method for the first DCI size is to classify the first DCI as C-RNTI-scrambled DCI for statistics, the format of the first DCI is format1_2, and other second DCIs are not aligned, determine the size of the FDRA field in the first DCI according to the number of RBs included in the CFR.

[0238] Step 112: Align the payload of the first DCI with the payload of one of the second DCIs.

[0239] Optionally, when the current cell is configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of the second DCI having the same format and being C-RNTI-scrambled.

[0240] Alternatively, when the current cell is not configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of the designated second DCI, where the designated second DCI is a DCI having a format of format1_2.

[0241] Optionally, when the payload of the first DCI is smaller than the payload of the second DCI in format1_2, padding bits are added to the first DCI, or appended bits are added after the information field of the first DCI to align the payload of the first DCI with the payload of the second DCI in format1_2.

[0242] Alternatively, when the payload of the first DCI is greater than the payload of the second DCI in the format 1_2, the first DCI is truncated so that the payload of the first DCI is aligned with the payload of the second DCI in the format 1_1.

[0243] Optionally, when the payload of the first DCI is smaller than the payload of the second DCI in format1_2, padding bits may be preferentially added to the FDRA field of the first DCI.

[0244] Optionally, when the payload of the first DCI is greater than the payload of the second DCI in format1_2, the FDRA field in the first DCI may be preferentially truncated.

[0245] By implementing the embodiment of the present disclosure, when the network device classifies the first DCI as a C-RNTI-scrambled DCI for statistics, the format of the first DCI is format1_2, and other second DCIs are not aligned, the network device determines the size of the FDRA field in the first DCI based on the number of RBs included in the CFR, and then aligns the payload of the first DCI with the payload of one of the second DCIs. As a result, when the network device does not complete the alignment of other second DCIs, the payload of the first DCI used to schedule the MBS service is aligned with the payload of the second DCI with the same format, thereby avoiding the total number of DCIs of different sizes ultimately sent by the network device exceeding the capacity of the terminal device.

[0246] See Figure 12 , Figure 12 This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a terminal device. Figure 12 As shown, the method may include but is not limited to the following steps:

[0247] Step 121, based on the statistical method of the size of the first downlink control information DCI, determine the alignment method of the payload of the first DCI and the payload of one of the second DCIs, wherein the first DCI is the DCI used to schedule multicast scheduling MBSspecific services, and the second DCI is the DCI used to schedule other services.

[0248] Optionally, the terminal device may determine a statistical method for calculating the first DCI size according to an instruction from the network device or a protocol agreement, which is not limited in the present disclosure.

[0249] Optionally, when the statistical method of the first DCI size is to classify the first DCI as C-RNTI-scrambled DCI for statistics, it is determined that the payload of the first DCI is aligned with the payload of one of the second DCIs transmitted in the CSS.

[0250] Alternatively, when the statistical method for the first DCI size is to classify the first DCI as C-RNTI scrambled DCI for statistical purposes, it is determined that the payload of the first DCI is aligned with the payload of one of the second DCIs transmitted in the USS.

[0251] Alternatively, when the statistical method for the size of the first DCI is to classify the first DCI as C-RNTI-scrambled DCI for statistical purposes, a second DCI aligned with the first DCI is determined according to the format of the first DCI.

[0252] Alternatively, when the statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by other RNTIs for statistical purposes, it is determined that the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs.

[0253] Optionally, when the statistical method of the first DCI size is to classify the first DCI as C-RNTI scrambled DCI for statistics, determining the second DCI aligned with the first DCI according to the format of the first DCI may include:

[0254] In a case where the format of the first DCI is format1_0, it is determined that the second DCI aligned with the payload of the first DCI is the second DCI scrambled by another RNTI.

[0255] Alternatively, when the format of the first DCI is format1_1 or format1_2, and the current cell is configured with a second DCI having the same format as the first DCI, it is determined that the second DCI aligned with the payload of the first DCI is the C-RNTI-scrambled second DCI.

[0256] Alternatively, when the format of the first DCI is format1_1 or format1_2, and the current cell is not configured with a second DCI with the same format as the first DCI, the second DCI aligned with the payload of the first DCI is determined to be the designated second DCI, wherein the designated second DCI is a DCI with the format of format1_1 or format1_2.

[0257] By implementing the embodiments of the present disclosure, a terminal device determines the alignment of the payload of a first DCI with the payload of one of the second DCIs based on a statistical method for measuring the size of the first downlink control information (DCI), where the first DCI is a DCI for scheduling a multicast MBS-specific service, and the second DCI is a DCI for scheduling other services. Thus, by determining the alignment of the payload of the first DCI with the payload of one of the second DCIs based on a statistical method for measuring the size of the first DCI, the terminal device can determine the service type indicated by the DCI.

[0258] See Figure 13 , Figure 13This is a flow chart of a method for aligning downlink control information provided by an embodiment of the present disclosure, which is executed by a terminal device. Figure 13 As shown, the method may include but is not limited to the following steps:

[0259] Step 131, based on the statistical method of the size of the first downlink control information DCI, determine the alignment method of the payload of the first DCI and the payload of one of the second DCIs, wherein the first DCI is the DCI used to schedule multicast scheduling MBSspecific services, and the second DCI is the DCI used to schedule other services.

[0260] The specific implementation of step 131 can refer to the detailed descriptions in other embodiments of the present disclosure and will not be described in detail here.

[0261] Step 132: Determine frequency domain resource allocation information according to the number of resource blocks (RBs) included in the control resource set (CORESET#0) or the number of RBs included in the initial downlink bandwidth part (BWP).

[0262] Optionally, when the number of RBs included in CORESET#0 is greater than the number of RBs included in CFR, the frequency domain resource allocation information is determined according to the N highest bits or the N lowest bits in the first DCI.

[0263] Alternatively, when the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI.

[0264] Wherein, N is a positive integer.

[0265] Optionally, when the number of RBs included in CORESET#0 is smaller than the number of RBs included in CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0266] Alternatively, when the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0267] Optionally, the scaling factor may be determined according to a ratio of the number of RBs included in CFR to the number of RBs included in CORESET 0.

[0268] Alternatively, the scaling factor may be determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the initial DL BWP.

[0269] By implementing the embodiment of the present disclosure, the terminal device determines the alignment of the payload of the first DCI with the payload of one of the second DCIs based on the statistical method of the size of the first downlink control information DCI, wherein the first DCI is a DCI for scheduling multicast scheduling MBS specific services, and the second DCI is a DCI for scheduling other services. Then, the frequency domain resource allocation information is determined based on the number of resource blocks RB included in the control resource set CORESET#0, or the number of RBs included in the initial downlink DL bandwidth part BWP. Therefore, the terminal device determines the alignment of the payload of the first DCI with the payload of one of the second DCIs through the statistical method of the first DCI size, so as to determine the service type indicated by the DCI and then allocate frequency domain resources to the service.

[0270] In the embodiments provided above, the methods provided in the embodiments of the present disclosure are described from the perspectives of network devices and terminal devices, respectively. To implement the various functions provided in the methods provided in the embodiments of the present disclosure, the network devices and terminal devices may include hardware structures and software modules, and the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures and software modules. Certain of the aforementioned functions may be implemented in the form of hardware structures, software modules, or hardware structures and software modules.

[0271] See Figure 14 , which is a structural diagram of a communication device 140 provided in an embodiment of the present disclosure. Figure 14 The communication device 140 shown may include a processing module 1401 and a transceiver module 1402 .

[0272] The transceiver module 1402 may include a sending module and / or a receiving module. The sending module is used to implement a sending function, and the receiving module is used to implement a receiving function. The transceiver module 1402 may implement a sending function and / or a receiving function.

[0273] It is understandable that the communication device 140 may be a network device, a device in a network device, or a device that can be used in conjunction with a network device.

[0274] The communication device 140, on the network device side, includes:

[0275] The processing module 1401 is configured to align a payload of a first downlink control information (DCI) with a payload of one of the second DCIs according to a statistical method of a size of the first downlink control information (DCI), wherein the first DCI is a DCI for scheduling a multicast MBS specific service, and the second DCI is a DCI for scheduling other services.

[0276] Optionally, the processing module 1401 is specifically configured to:

[0277] When the statistical method of the first DCI size is to classify the first DCI as DCI scrambled by the cell radio network temporary identifier C-RNTI and other second DCIs have been aligned, the payload of the first DCI is aligned with the payload of one of the second DCIs transmitted in the common search space CSS or the terminal device-specific search space USS.

[0278] Optionally, the processing module 1401 is specifically configured to:

[0279] Add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the CSS;

[0280] or,

[0281] Add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate the first DCI so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_0 transmitted in the USS;

[0282] or,

[0283] Add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate the first DCI, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_1 transmitted in the USS;

[0284] or,

[0285] Add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate the first DCI, so that the payload of the processed first DCI is consistent with the payload of the DCI in format 1_2 transmitted in the USS;

[0286] or,

[0287] Add padding bits to the second DCI in format 1_1 or format 1_2 transmitted in the USS, or add appended bits after all valid information fields of the second DCI, or truncate the second DCI so that the payload of the processed second DCI is consistent with the payload of the first DCI.

[0288] Optionally, the processing module 1401 is specifically configured to:

[0289] In a case where the statistical method for the size of the first DCI is to classify the first DCI as DCI scrambled by other RNTIs for statistical purposes, the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs.

[0290] Optionally, the processing module 1401 is specifically configured to:

[0291] Determine the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of resource blocks RB included in the control resource set CORESET#0, or the number of RBs included in the initial downlink DL bandwidth part BWP;

[0292] In a case where the payload of the first DCI is different from the payload of the second DCI scrambled by the other RNTI, the payload of the first DCI is aligned with the payload of the second DCI scrambled by the other RNTI.

[0293] Optionally, the processing module 1401 is specifically configured to:

[0294] In the case where the payload of the first DCI is smaller than the payload of the second DCI scrambled by other RNTIs, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI;

[0295] or,

[0296] In the case where the payload of the first DCI is larger than the payload of the second DCI scrambled by other RNTIs, the first DCI is truncated.

[0297] Optionally, the processing module 1401 is specifically configured to:

[0298] The FDRA field in the first DCI is truncated.

[0299] Optionally, the processing module 1401 is further configured to:

[0300] When the number of RBs included in CORESET#0 is greater than the number of RBs included in the common frequency domain resources CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI;

[0301] or,

[0302] When the number of RBs included in the initialDL BWP is greater than the number of RBs included in the CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI;

[0303] Wherein, N is a positive integer.

[0304] Optionally, the processing module 1401 is further configured to:

[0305] When the number of RBs included in CORESET#0 is less than the number of RBs included in CFR, the frequency domain scheduling granularity of the first DCI is scaled;

[0306] or,

[0307] When the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0308] Optionally, the processing module 1401 is specifically configured to:

[0309] The scaling factor is determined based on the ratio of the number of RBs included in CFR to the number of RBs included in CORESET#0.

[0310] or,

[0311] The scaling factor is determined according to the ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

[0312] Optionally, the processing module 1401 is specifically configured to:

[0313] When the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI and other second DCIs are not aligned, the payload of the first DCI is aligned with the payload of one of the second DCIs according to the format of the first DCI.

[0314] Optionally, the processing module 1401 is specifically configured to:

[0315] When the format of the first DCI is format1_0, the size of the FDRA field in the first DCI is determined according to the number of RBs included in CORESET#0 or initialDL BWP;

[0316] When the payload of the first DCI is different from the payload of the second DCI encrypted by other RNTIs, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or part of the information fields are truncated, so that the payload of the first DCI is aligned with the payload of the second DCI encrypted by other RNTIs.

[0317] Optionally, the processing module 1401 is further configured to:

[0318] When the number of RBs included in CORESET#0 is greater than the number of RBs included in CFR, or when the number of RBs included in initialDL BWP is greater than the number of RBs included in CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI, where N is a positive integer;

[0319] or,

[0320] When the number of RBs included in CORESET#0 is smaller than the number of RBs included in CFR, or when the number of RBs included in the initial DL BWP is smaller than the number of RBs included in CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0321] Optionally, the processing module 1401 is specifically configured to:

[0322] The scaling factor is determined based on the ratio of the number of RBs included in CFR to the number of RBs included in CORESET 0.

[0323] or,

[0324] The scaling factor is determined according to the ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

[0325] Optionally, the processing module 1401 is specifically configured to:

[0326] When the format of the first DCI is format1_1 or format1_2, the size of the FDRA field in the first DCI is determined according to the number of RBs included in the CFR;

[0327] The payload of the first DCI is aligned with the payload of one of the second DCIs.

[0328] Optionally, the processing module 1401 is specifically configured to:

[0329] If the current cell is configured with a second DCI format identical to the first DCI format, align the payload of the first DCI with the payload of the second DCI format identical to the first DCI format and scrambled by the C-RNTI.

[0330] or,

[0331] In the case that the current cell is not configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of the designated second DCI, where the designated second DCI is a DCI having a format of format1_1 or format1_2.

[0332] Optionally, the processing module 1401 is specifically configured to:

[0333] In the case where the payload of the first DCI is smaller than the payload of one of the second DCIs, padding bits are added to the first DCI, or appended bits are added after the information field of the first DCI;

[0334] or,

[0335] In the case where the payload of the first DCI is greater than the payload of one of the second DCIs, the first DCI is truncated.

[0336] Optionally, the processing module 1401 is specifically configured to:

[0337] Add padding bits to the FDRA field of the first DCI;

[0338] Optionally, the processing module 1401 is specifically configured to:

[0339] The FDRA field in the first DCI is truncated.

[0340] In the communication device provided herein, a network device aligns the payload of a first downlink control information (DCI) with the payload of one of the second DCIs based on a statistical method for calculating the size of the first downlink control information (DCI). The first DCI is a DCI for scheduling a multicast MBS-specific service, and the second DCI is a DCI for scheduling other services. Thus, by aligning the payload of the first DCI for scheduling the MBS service with the payload of one of the second DCIs for scheduling other services, the total number of DCIs of different sizes configured by the network device is prevented from exceeding the capabilities of the terminal device.

[0341] It is understandable that the communication device 140 may be a terminal device, a device in the terminal device, or a device that can be used in conjunction with the terminal device.

[0342] The communication device 140, on the terminal device side, includes:

[0343] The processing module 1401 determines, based on a statistical method for calculating a size of first downlink control information (DCI), an alignment method for a payload of a first DCI with a payload of one of the second DCIs, wherein the first DCI is a DCI for scheduling a multicast MBS specific service, and the second DCI is a DCI for scheduling other services.

[0344] Optionally, the processing module 1401 is specifically configured to:

[0345] In a case where the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI, aligning a payload of the first DCI with a payload of one of the second DCIs transmitted in the CSS;

[0346] or,

[0347] In a case where the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI, determining that a payload of the first DCI is aligned with a payload of one of the second DCIs transmitted in the USS;

[0348] or,

[0349] In a case where the first DCI size is counted by classifying the first DCI as C-RNTI-scrambled DCI, determining, according to the format of the first DCI, a second DCI aligned with the first DCI;

[0350] or,

[0351] In a case where the first DCI size is counted in a manner of classifying the first DCI as DCI scrambled by other RNTIs for counting, it is determined that the payload of the first DCI is aligned with the payload of the second DCI scrambled by other RNTIs.

[0352] Optionally, the processing module 1401 is specifically configured to:

[0353] When the format of the first DCI is format1_0, determining that the second DCI aligned with the payload of the first DCI is the second DCI scrambled by another RNTI;

[0354] or,

[0355] When the format of the first DCI is format1_1 or format1_2, and the current cell is configured with a second DCI having the same format as the first DCI, determining that the second DCI aligned with the payload of the first DCI is a C-RNTI-scrambled second DCI;

[0356] or,

[0357] When the format of the first DCI is format1_1 or format1_2, and the current cell is not configured with a second DCI with the same format as the first DCI, the second DCI aligned with the payload of the first DCI is determined to be the designated second DCI, wherein the designated second DCI is a DCI with the format of format1_1 or format1_2.

[0358] Optionally, the processing module 1401 is further configured to:

[0359] When the number of RBs included in CORESET#0 is greater than the number of RBs included in CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI;

[0360] or,

[0361] When the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, the frequency domain resource allocation information is determined according to the N most significant bits or the N least significant bits in the first DCI;

[0362] Wherein, N is a positive integer.

[0363] Optionally, the processing module 1401 is further configured to:

[0364] When the number of RBs included in CORESET#0 is less than the number of RBs included in CFR, the frequency domain scheduling granularity of the first DCI is scaled;

[0365] or,

[0366] When the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

[0367] Optionally, the processing module 1401 is further configured to:

[0368] The scaling factor is determined based on the ratio of the number of RBs included in CFR to the number of RBs included in CORESET 0.

[0369] or,

[0370] The scaling factor is determined according to the ratio of the number of RBs included in the CFR to the number of RBs included in the initial DL BWP.

[0371] In the communication device provided by the present disclosure, a terminal device determines the alignment of a payload of a first downlink control information (DCI) with the payload of one of the second DCIs based on a statistical method for calculating the size of the first downlink control information (DCI), wherein the first DCI is a DCI for scheduling a multicast MBS-specific service, and the second DCI is a DCI for scheduling other services. Thus, by determining the alignment of the payload of the first DCI with the payload of one of the second DCIs based on a statistical method for calculating the size of the first DCI, the terminal device can determine the service type indicated by the DCI.

[0372] See Figure 15 , Figure 15 1 is a schematic diagram of the structure of another communication device 150 provided in an embodiment of the present disclosure. Communication device 150 can be a network device or a terminal device, or a chip, chip system, or processor that supports a network device in implementing the above-mentioned method. It can also be a chip, chip system, or processor that supports a terminal device in implementing the above-mentioned method. This device can be used to implement the method described in the above-mentioned method embodiment. For details, please refer to the description of the above-mentioned method embodiment.

[0373] The communication device 150 may include one or more processors 1501. The processor 1501 may be a general-purpose processor or a dedicated processor. For example, it may be 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 the communication device (e.g., a base station, a baseband chip, a terminal device, a terminal device chip, a DU or CU, etc.), execute computer programs, and process computer program data.

[0374] Optionally, the communication device 150 may further include one or more memories 1502, on which a computer program 1504 may be stored. The processor 1501 executes the computer program 1504 to cause the communication device 150 to perform the method described in the above method embodiment. Optionally, the memory 1502 may also store data. The communication device 150 and the memory 1502 may be provided separately or integrated together.

[0375] Optionally, the communication device 150 may further include a transceiver 1505 and an antenna 1506. The transceiver 1505 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., and is configured to implement transceiver functions. The transceiver 1505 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., and is configured to implement a receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., and is configured to implement a transmitting function.

[0376] Optionally, the communication device 150 may further include one or more interface circuits 1507. The interface circuit 1507 is configured to receive code instructions and transmit the code instructions to the processor 1501. The processor 1501 executes the code instructions to enable the communication device 150 to execute the method described in the above method embodiment.

[0377] The communication device 150 is a network device: the processor 1501 is used to execute Figure 2 Step 21 of ; or Figure 3 step 31 in ; or Figure 4 step 41 in ; or Figure 5 step 51 in; or Figure 6 step 61 in step 61; or Figure 7 Step 71 in , etc.

[0378] The communication device 150 is a terminal device: the processor 1501 is used to execute Figure 12 step 121 in step 121; or Figure 13 Step 131, step 132, etc.

[0379] In one implementation, processor 1501 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and transmitting functions may be separate or integrated. The transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or may be used for transmitting or delivering signals.

[0380] In one implementation, processor 1501 may store a computer program 1503. Computer program 1503, when executed on processor 1501, enables communication device 150 to perform the method described in the above method embodiment. Computer program 1503 may be embedded in processor 1501, in which case processor 1501 may be implemented by hardware.

[0381] In one implementation, the communication device 150 may include a circuit that can implement the functions of sending, receiving, or communicating in the aforementioned method embodiments. The processor and transceiver described in the present disclosure can be implemented on an integrated circuit (IC), an analog IC, a radio frequency integrated circuit RFIC, a mixed signal IC, an application specific integrated circuit (ASIC), a printed circuit board (PCB), an electronic device, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (nMetal-oxide-semiconductor, NMOS), P-type metal oxide semiconductor (positive channel metal oxide semiconductor, PMOS), bipolar junction transistor (bipolar junction transistor, BJT), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0382] The communication device described in the above embodiments may be a network device or a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be limited thereto. Figure 14 The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0383] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0384] (2) a collection of one or more ICs, optionally including a storage component for storing data and computer programs;

[0385] (3) ASIC, such as modem;

[0386] (4) Modules that can be embedded in other devices;

[0387] (5) Receivers, terminal devices, intelligent terminal devices, cellular phones, wireless devices, handheld devices, mobile units, vehicle-mounted devices, network devices, cloud devices, artificial intelligence devices, etc.;

[0388] (6)Others, etc.

[0389] For the case where the communication device may be a chip or a chip system, see Figure 16 Schematic diagram of the chip structure shown. Figure 16 The chip shown includes a processor 1601 and an interface 1602. There may be one or more processors 1601 and there may be more than one interface 1602.

[0390] For the case where the chip is used to implement the functions of the network device in the embodiments of the present disclosure:

[0391] Processor 1601 is used to execute Figure 2 Step 21 of ; or Figure 3 step 31 in ; or Figure 4 step 41 in ; or Figure 5 step 51 in; or Figure 6 step 61 in step 61; or Figure 7 Step 71 in , etc.

[0392] For the case where the chip is used to implement the functions of the terminal device in the embodiments of the present disclosure:

[0393] Processor 1601 is used to execute Figure 12 step 121 in step 121; or Figure 13 Step 131, step 132, etc.

[0394] Optionally, the chip further includes a memory 1603, which is used to store necessary computer programs and data.

[0395] Those skilled in the art will also appreciate that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure may be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented by hardware or software depends on the specific application and the design requirements of the entire system. Those skilled in the art may use various methods to implement the described functionality for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0396] The present disclosure also provides a communication system comprising the aforementioned Figure 14 In the embodiment, the communication device as the terminal device and the communication device as the network device, or the system includes the aforementioned Figure 15 The communication device in the embodiment serves as a terminal device and the communication device serves as a network device.

[0397] The present disclosure also provides a computer-readable storage medium having instructions stored thereon, which implement the functions of any of the above method embodiments when executed by a computer.

[0398] The present disclosure also provides a computer program product, which implements the functions of any of the above method embodiments when executed by a computer.

[0399] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0400] Those skilled in the art will understand that the various numerical numbers such as first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, and also indicate the order of precedence.

[0401] The at least one in the present disclosure can also be described as one or more, and the multiple can be two, three, four or more, which is not limited in the present disclosure. In the embodiments of the present disclosure, for a technical feature, the technical features in the technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order of precedence or size between the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0402] The correspondences shown in the tables of the present disclosure can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values, which are not limited by the present disclosure. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, in the tables of the present disclosure, the correspondences shown in certain rows may not be configured. For another example, appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables may also adopt other names that can be understood by the communication device, and the values ​​or representations of the parameters may also adopt other values ​​or representations that can be understood by the communication device. When implementing the above tables, other data structures may also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash tables, etc.

[0403] The predefined in the present disclosure may be understood as defined, predefined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0404] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

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

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

Claims

1. A method for aligning downlink control information, characterized in that: The method is performed by a network device, and includes: When the first downlink control information (DCI) size is counted by classifying the first DCI as DCI scrambled by a cell radio network temporary identifier (C-RNTI) and alignment of other second DCIs is not completed, aligning the payload of the first DCI with the payload of one of the second DCIs according to the format of the first DCI; The aligning, according to the format of the first DCI, the payload of the first DCI with the payload of one of the second DCIs includes: When the format of the first DCI is format1_0, determine the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of resource blocks (RBs) included in the control resource set CORESET#0 or the initial DL BWP; When the payload of the first DCI is different from the payload of the second DCI scrambled by the other RNTI, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or part of the information fields are truncated, so that the payload of the first DCI is aligned with the payload of the second DCI scrambled by the other RNTI; The first DCI is a DCI used for scheduling multicast scheduling MBS specific services, and the second DCI is a DCI used for scheduling other services.

2. The method according to claim 1, wherein Also includes: When the number of RBs included in the CORESET #0 is greater than the number of RBs included in the common frequency domain resources CFR, or when the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining the frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI, where N is a positive integer; or, When the number of RBs included in the CORESET#0 is smaller than the number of RBs included in the CFR, or when the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

3. The method according to claim 2, wherein The scaling of the frequency domain scheduling granularity of the first DCI includes: Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET#0; or, A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

4. The method according to claim 1, wherein The aligning, according to the format of the first DCI, the payload of the first DCI with the payload of one of the second DCIs includes: When the format of the first DCI is format1_1 or format1_2, the size of the FDRA field in the first DCI is determined according to the number of RBs included in the CFR; The payload of the first DCI is aligned with the payload of one of the second DCIs.

5. The method according to claim 4, wherein The aligning the payload of the first DCI with the payload of one of the second DCIs includes: In a case where the current cell is configured with a second DCI format identical to the first DCI format, aligning the payload of the first DCI with the payload of the second DCI format identical to the first DCI format and scrambled by the C-RNTI; or, In a case where the current cell is not configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of a specified second DCI, wherein the specified second DCI is a DCI having a format of format1_1 or format1_2.

6. The method according to any one of claims 1 to 5, characterized in that: The aligning the payload of the first DCI with the payload of one of the second DCIs includes: In the case where the payload of the first DCI is smaller than the payload of one of the second DCIs, padding bits are added to the first DCI, or appended bits are added after the information field of the first DCI; or, In a case where the payload of the first DCI is greater than the payload of one of the second DCIs, the first DCI is truncated.

7. The method according to claim 6, wherein The adding padding bits to the first DCI, or adding appended bits after the information field of the first DCI, includes: Add padding bits to the FDRA field of the first DCI.

8. The method according to claim 6, wherein The truncating the first DCI includes: The FDRA field in the first DCI is truncated.

9. A method for aligning downlink control information, characterized in that: The method is executed by a terminal device, and includes: In a case where the statistical method for the size of the first downlink control information DCI is to classify the first DCI as DCI scrambled by a cell radio network temporary identifier C-RNTI for statistical purposes, determining, according to the format of the first DCI, a second DCI aligned with the first DCI; The determining, according to the format of the first DCI, a second DCI aligned with the first DCI includes: When the format of the first DCI is format1_0, determine that the second DCI aligned with the payload of the first DCI is the second DCI scrambled by another RNTI; The first DCI is a DCI for scheduling a multicast scheduling MBS specific service, and the second DCI is a DCI for scheduling other services; The alignment method of the first DCI and the second DCI includes: Add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate part of the information fields, so that the payload of the first DCI is aligned with the payload of the second DCI scrambled by the other RNTI.

10. The method according to claim 9, wherein The determining, according to the format of the first DCI, a second DCI aligned with the first DCI includes: When the format of the first DCI is format1_1 or format1_2, and the current cell is configured with a second DCI having the same format as the first DCI, determining that the second DCI aligned with the payload of the first DCI is a C-RNTI-scrambled second DCI; or, When the format of the first DCI is format1_1 or format1_2, and the current cell is not configured with a second DCI with the same format as the first DCI, the second DCI aligned with the payload of the first DCI is determined to be a designated second DCI, wherein the designated second DCI is a DCI with a format of format1_1 or format1_2.

11. The method according to claim 9, wherein Also includes: When the number of RBs included in CORESET#0 is greater than the number of RBs included in the common frequency domain resources CFR, determining the frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI; or, When the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI; Wherein, N is a positive integer.

12. The method according to claim 11, wherein Also includes: When the number of RBs included in the CORESET#0 is less than the number of RBs included in the CFR, scaling the frequency domain scheduling granularity of the first DCI; or, When the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

13. The method according to claim 12, wherein: The scaling of the frequency domain scheduling granularity of the first DCI includes: Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET 0; or, A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the initial DL BWP.

14. A device for aligning downlink control information, characterized in that: The device is on the network device side, and the device includes: a processing module, configured to, when the statistical method for the size of the first downlink control information DCI is to classify the first DCI as DCI scrambled by a cell radio network temporary identifier C-RNTI for statistics, and when other second DCIs are not aligned, align the payload of the first DCI with the payload of one of the second DCIs according to the format of the first DCI; The processing module is specifically used to: When the format of the first DCI is format1_0, determine the size of the frequency domain resource allocation FDRA field in the first DCI according to the number of RBs included in the control resource set CORESET#0 or the initial DL BWP; When the payload of the first DCI is different from the payload of the second DCI encrypted by other RNTIs, padding bits are added to the first DCI, or appended bits are added after all valid information fields of the first DCI, or part of the information fields are truncated, so that the payload of the first DCI is aligned with the payload of the second DCI encrypted by other RNTIs.

15. The device according to claim 14, wherein The processing module is further specifically configured to: When the number of RBs included in the CORESET #0 is greater than the number of RBs included in the common frequency domain resources CFR, or when the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining the frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI, where N is a positive integer; or, When the number of RBs included in the CORESET#0 is smaller than the number of RBs included in the CFR, or when the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

16. The device according to claim 15, characterized in that The processing module is specifically used to: Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET#0; or, A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the DL BWP.

17. The device according to claim 14, wherein The processing module is specifically used to: When the format of the first DCI is format1_1 or format1_2, the size of the FDRA field in the first DCI is determined according to the number of RBs included in the CFR; The payload of the first DCI is aligned with the payload of one of the second DCIs.

18. The device according to claim 17, wherein The processing module is specifically used to: In a case where the current cell is configured with a second DCI format identical to the first DCI format, aligning the payload of the first DCI with the payload of the second DCI format identical to the first DCI format and scrambled by the C-RNTI; or, In a case where the current cell is not configured with a second DCI having the same format as the first DCI, the payload of the first DCI is aligned with the payload of a specified second DCI, wherein the specified second DCI is a DCI having a format of format1_1 or format1_2.

19. The device according to any one of claims 14 to 18, characterized in that: The processing module is specifically used to: In the case where the payload of the first DCI is smaller than the payload of one of the second DCIs, padding bits are added to the first DCI, or appended bits are added after the information field of the first DCI; or, In a case where the payload of the first DCI is greater than the payload of one of the second DCIs, the first DCI is truncated.

20. The device according to claim 19, wherein The processing module is specifically used to: Add padding bits to the FDRA field of the first DCI.

21. The device according to claim 19, wherein The processing module is specifically used to: The FDRA field in the first DCI is truncated.

22. A downlink control information alignment device, characterized in that: The apparatus is executed by a terminal device, and includes: a processing module, configured to determine, according to a format of the first DCI, a second DCI aligned with the first DCI, when the statistical method for counting the size of the first downlink control information DCI is to classify the first DCI as DCI scrambled by a cell radio network temporary identifier C-RNTI for statistical purposes; The processing module is specifically used to: When the statistical method for calculating the size of the first DCI is that the format of the first DCI is format1_0, determining that the second DCI aligned with the payload of the first DCI is the second DCI scrambled by another RNTI; The first DCI is a DCI for scheduling a multicast scheduling MBS specific service, and the second DCI is a DCI for scheduling other services; The alignment method of the first DCI and the second DCI includes: Add padding bits to the first DCI, or add appended bits after all valid information fields of the first DCI, or truncate part of the information fields, so that the payload of the first DCI is aligned with the payload of the second DCI scrambled by the other RNTI.

23. The device according to claim 22, wherein The processing module is specifically used to: When the statistical method for the size of the first DCI is that the format of the first DCI is format1_1 or format1_2, and when the current cell is configured with a second DCI having the same format as the first DCI, determining that the second DCI aligned with the payload of the first DCI is a C-RNTI-scrambled second DCI; or, When the statistical method of the first DCI size is that the format of the first DCI is format1_1 or format1_2, and when the current cell is not configured with a second DCI with the same format as the first DCI, the second DCI aligned with the payload of the first DCI is determined to be the designated second DCI, wherein the designated second DCI is a DCI with the format of format1_1 or format1_2.

24. The device according to claim 22, wherein The processing module is further specifically configured to: When the number of RBs included in CORESET#0 is greater than the number of RBs included in the common frequency domain resources CFR, determining the frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI; or, When the number of RBs included in the initial DL BWP is greater than the number of RBs included in the CFR, determining frequency domain resource allocation information according to the N most significant bits or the N least significant bits in the first DCI; Wherein, N is a positive integer.

25. The device according to claim 24, wherein The processing module is further specifically configured to: When the number of RBs included in the CORESET#0 is less than the number of RBs included in the CFR, scaling the frequency domain scheduling granularity of the first DCI; or, When the number of RBs included in the initial DL BWP is smaller than the number of RBs included in the CFR, the frequency domain scheduling granularity of the first DCI is scaled.

26. The device according to claim 25, characterized in that The processing module is further specifically configured to: Determining a scaling factor according to a ratio of the number of RBs included in the CFR to the number of RBs included in the CORESET 0; or, A scaling factor is determined according to a ratio of the number of RBs included in the CFR to the number of RBs included in the initial DL BWP.

27. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory, so that the device performs the method according to any one of claims 1 to 8.

28. A communication device, characterized in that: The device includes a processor and a memory, wherein a computer program is stored in the memory, and the processor executes the computer program stored in the memory to enable the device to perform the method according to any one of claims 9 to 13.

29. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method according to any one of claims 1 to 8.

30. A communication device, characterized in that: include: processor and interface circuits; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method according to any one of claims 9 to 13.

31. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 1 to 8 to be implemented.

32. A computer-readable storage medium storing instructions, which, when executed, enable the method according to any one of claims 9 to 13 to be implemented.

Images