Method and apparatus in communication node used for wireless communication

By receiving messages in the wireless communication system, configuring uplink grants and sending control information, indicating whether K2 uplink grants are not used, the problem of low efficiency and high complexity of control information indication is solved, and more efficient resource utilization and hardware cost are achieved. .

CN118945682APending Publication Date: 2024-11-12SHANGHAI LANGBO COMM TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310552491.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2023-05-16
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

In wireless communication systems, the indication of control information has problems of low efficiency and high complexity, especially in many application scenarios, it is difficult to meet the performance requirements of high speed and low latency.

Method used

By introducing a method in the NR system, receiving a message to configure uplink grants, and sending control information in the first uplink grants, indicating whether K2 uplink grants are not in use, and K2 uplink grants time domain locations that depend on the first message configuration are Or symbol set position, reducing the impact on symbol set and saving signaling overhead.

Benefits of technology

Improve the information effectiveness of control information indication, reduce hardware complexity and cost, reduce unnecessary indications and impact on existing protocols, and achieve more efficient resource utilization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118945682A_ABST
    Figure CN118945682A_ABST
Patent Text Reader

Abstract

The invention discloses a method and an apparatus in a communication node used for wireless communication. A communication node receives a first message, the first message configures uplink grants, and any two uplink grants configured by the first message are not overlapped in time; receiving a second message, the second message indicating the first symbol set; first control information is sent in a first uplink grant, the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; k2 is a positive integer. According to the scheme provided by the invention, the signaling overhead is saved, and the effectiveness of the information indicated by the first control information is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a control information indication method and device. Background Art

[0002] In the future, the application scenarios of wireless communication systems will become more and more diversified, and different application scenarios will put forward high-speed and low-latency performance requirements for the system. For example, in order to meet the different performance requirements of various application scenarios, such as capacity requirements, the WI (Work Item) of "XR (Extended Reality) Enhancements for NR (New Radio)" was passed at the 3GPP (3rd Generation Partner Project) RAN (Radio Access Network) #98 plenary meeting. Summary of the invention

[0003] The inventors have discovered through research that the indication of control information is a key issue.

[0004] In response to the above problems, the present application provides a solution for indicating control information. In the description of the above problems, the NR system is used as an example. The present application is also applicable to scenarios such as LTE (Long-Term Evolution) or LTE-A (Long-Term Evolution Advanced) systems, and achieves technical effects similar to those of the NR system; further, although the present application provides a specific implementation method for the uplink, the present application can also be used in scenarios such as the downlink to achieve technical effects similar to those of the uplink. Furthermore, adopting a unified design scheme for different scenarios also helps to reduce hardware complexity and cost. Furthermore, although the present application provides a specific implementation method for the XR scenario, the present application can also be used in scenarios of uplink enhancement to achieve technical effects similar to those of the XR system. Furthermore, although the present application provides a specific implementation method for PUSCH (Physical Uplink Shared CHannel), the present application can also be used in scenarios such as PRACH or PUCCH or PUSCH repetition to achieve technical effects similar to those of PUSCH. Further, although the original intention of this application is for the Uu air interface, this application can also be used for the PC5 port to achieve a technical effect similar to the Uu air interface. Further, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the V2X (Vehicle-to-Everything) scenario, the communication scenario between the terminal and the relay, and the relay and the base station, to achieve a technical effect similar to that in the terminal and base station scenario. Further, although the original intention of this application is for the terminal and base station scenario, this application is also applicable to the IAB (Integrated Access and Backhaul) communication scenario, to achieve a technical effect similar to that in the terminal and base station scenario. Further, although the original intention of this application is for the terrestrial network (TN) scenario, this application is also applicable to the non-terrestrial network (NTN) communication scenario, to achieve a technical effect similar to that in the TN scenario. In addition, the use of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

[0005] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the 3GPP specification protocol TS36 series.

[0006] As an example, the interpretation of the terms in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.

[0007] As an example, the interpretation of the terms in the present application refers to the definition of the TS37 series of specification protocols of 3GPP.

[0008] As an embodiment, the interpretation of the terms in this application refers to the definition of the standard protocol of IEEE (Institute of Electrical and Electronics Engineers).

[0009] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.

[0010] The present application discloses a method in a first node used for wireless communication, characterized by comprising:

[0011] receiving a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; receiving a second message, wherein the second message indicates a first symbol set;

[0012] Sending first control information in a first uplink grant, the first control information indicating whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants being configured by the first message, and the K2 uplink grants being after the first uplink grant;

[0013] Typically, the K2 uplink grants depend on the time domain position of the uplink grant configured by the first message; and K2 is a positive integer.

[0014] Typically, the K2 uplink grants depend on the time domain position of the uplink grant configured by the first message and the position of the first symbol set; and K2 is a positive integer.

[0015] As an embodiment, the problem to be solved by the present application includes: the first control information indicates which uplink grants are not used.

[0016] As an embodiment, the problem to be solved by the present application includes: the first control information indicates how much uplink grant is not used.

[0017] As an embodiment, the characteristics of the above method include: the positions of the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set.

[0018] As an embodiment, the characteristics of the above method include: K2 depends on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set.

[0019] As an embodiment, the benefits of the above method include: reducing the impact on the first symbol set.

[0020] As an embodiment, the benefits of the above method include: saving signaling overhead.

[0021] As an embodiment, the benefits of the above method include: improving the effectiveness of the information indicated by the first control information.

[0022] According to one aspect of the present application, it is characterized in that the K2 uplink grants depend on a first time interval; the starting time of the first time interval is related to the time domain position of the first uplink grant, and the length of the first time interval is configurable.

[0023] As an embodiment, the benefits of the above method include: reducing unnecessary instructions.

[0024] According to one aspect of the present application, it is characterized in that the first control information is a bit map, the number of bits occupied by the first control information is greater than K2, and at least one bit in the first control information is reserved.

[0025] As an embodiment, the benefits of the above method include: reducing unnecessary instructions.

[0026] As an embodiment, the benefits of the above method include: reducing the impact on existing protocols.

[0027] As an embodiment, the benefits of the above method include: reducing implementation complexity.

[0028] According to one aspect of the present application, it is characterized in that the K2 uplink grants depend on the number of bits occupied by the first control information; the first control information is a bit map.

[0029] According to one aspect of the present application, it is characterized in that the K2 uplink grants are valid uplink grants; the valid uplink grants satisfy at least one of not overlapping with the first symbol set or belonging to the first time interval or being later than the first uplink grant in the time domain.

[0030] As an embodiment, the benefits of the above method include: reducing the impact on existing protocols.

[0031] As an embodiment, the benefits of the above method include: reducing implementation complexity.

[0032] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0033] Sending a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; sending a second message, wherein the second message indicates a first symbol set;

[0034] receiving first control information, the first control information indicating whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants being configured by the first message, the K2 uplink grants being after the first uplink grant;

[0035] Among them, the recipient of the first message sends the first control information in a first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0036] According to one aspect of the present application, it is characterized in that the K2 uplink grants depend on a first time interval; the starting time of the first time interval is related to the time domain position of the first uplink grant, and the length of the first time interval is configurable.

[0037] According to one aspect of the present application, it is characterized in that the first control information is a bit map, the number of bits occupied by the first control information is greater than K2, and at least one bit in the first control information is reserved.

[0038] According to one aspect of the present application, it is characterized in that the K2 uplink grants depend on the number of bits occupied by the first control information; the first control information is a bit map.

[0039] According to one aspect of the present application, it is characterized in that the K2 uplink grants are valid uplink grants; the valid uplink grants satisfy at least one of not overlapping with the first symbol set or belonging to the first time interval or being later than the first uplink grant in the time domain.

[0040] The present application discloses a first node used for wireless communication, characterized in that it includes:

[0041] A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; and receives a second message, wherein the second message indicates a first symbol set;

[0042] A first transmitter sends first control information in a first uplink grant, wherein the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant;

[0043] The K2 uplink grants depend on at least the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0044] The present application discloses a second node used for wireless communication, characterized in that it includes:

[0045] A second transmitter sends a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; and sends a second message, wherein the second message indicates a first symbol set;

[0046] A second receiver receives first control information, wherein the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant;

[0047] Among them, the recipient of the first message sends the first control information in a first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0048] As an embodiment, compared with the traditional solution, the present application has at least one of the following advantages:

[0049] -. Reduced impact on the first symbol set;

[0050] -.Saves signaling overhead;

[0051] -. Improves the effectiveness of the information indicated by the first control information;

[0052] -.Reduce unnecessary instructions;

[0053] - Reduced impact on existing protocols;

[0054] -. Reduced implementation complexity. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:

[0056] Figure 1A flow chart showing transmission of a first message, a second message and first control information according to an embodiment of the present application is shown;

[0057] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;

[0058] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0059] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;

[0060] Figure 5 A wireless signal transmission flow chart according to an embodiment of the present application is shown;

[0061] Figure 6 A schematic diagram showing K2 uplink grants depending on a first time interval according to an embodiment of the present application is shown;

[0062] Figure 7 A schematic diagram showing that K2 uplink grants are valid uplink grants according to an embodiment of the present application;

[0063] Figure 8 A schematic diagram showing that at least one bit in the first control information is reserved according to an embodiment of the present application;

[0064] Fig. 9 A schematic diagram showing an uplink grant and a first symbol set of a first message configuration according to an embodiment of the present application is shown;

[0065] Fig.10 A schematic diagram showing a time domain position of an uplink grant configured by K2 depending on a first message according to an embodiment of the present application;

[0066] Fig.11 A schematic diagram showing the time domain position of the uplink grants configured by the first message according to an embodiment of the present application in which K2 uplink grants are dependent;

[0067] Fig.12 A structural block diagram of a processing device used in a first node according to an embodiment of the present application is shown;

[0068] Fig.13 A structural block diagram of a processing device used in a second node according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0069] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.

[0070] Example 1

[0071] Embodiment 1 illustrates a flow chart of the transmission of a first message, a second message and a first control information according to an embodiment of the present application, as shown in the attached figure. Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.

[0072] In Example 1, the first node in the present application receives a first message in step 101, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; in step 102, a second message is received, and the second message indicates a first symbol set; in step 103, a first control information is sent in the first uplink grant, and the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; wherein the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0073] As an embodiment, the first message is UE-specific signaling.

[0074] As an embodiment, the first message is cell common signaling.

[0075] As an embodiment, the first message is used to configure CG (Configured Grant).

[0076] As an embodiment, the first message is used for semi-persistently configuration.

[0077] As an embodiment, the first message is layer 1 signaling (L1 signalling).

[0078] As an embodiment, the first message is transmitted via PDCCH (Physical downlink control channel).

[0079] As an embodiment, the first message is a DCI (Downlink control information).

[0080] As an embodiment, the DCI format of the first message is DCI format 0_0.

[0081] As an embodiment, the DCI format of the first message is DCI format 0_1.

[0082] As an embodiment, the DCI format of the first message is DCI format 0_2.

[0083] As an embodiment, the DCI format of the first message is a new DCI format.

[0084] As an embodiment, the first message includes at least one field in a DCI format.

[0085] As an embodiment, the first message is a DCI in which a CRC (Cyclic redundancy check) is scrambled by a CS (Configured Scheduling)-RNTI (Radio Network Temporary Identity).

[0086] As an embodiment, the first message is an RRC (Radio Resource Control) message.

[0087] As an embodiment, the first message is an RRCReconfiguration message.

[0088] As an embodiment, the first message is a CellGroupConfig IE.

[0089] As an embodiment, the first message includes an IE whose name includes ConfiguredGrantConfig.

[0090] As an embodiment, the first message is a ConfiguredGrantConfig IE.

[0091] As an embodiment, the first message includes a field, and the field indicates a first index.

[0092] As a sub-embodiment of this embodiment, the name of the domain includes configuredGrantConfigIndex.

[0093] As a sub-embodiment of this embodiment, the one domain is a configuredGrantConfigIndex domain.

[0094] As a sub-embodiment of this embodiment, the name of the domain includes configuredGrantConfigIndexMAC.

[0095] As a sub-embodiment of this embodiment, the one domain is a configuredGrantConfigIndex domain.

[0096] As a sub-embodiment of this embodiment, the first index is used to indicate a CG configuration.

[0097] As a sub-embodiment of this embodiment, the first index is used to indicate the CG configuration to which the uplink grant configured by the first message belongs.

[0098] As a sub-embodiment of this embodiment, the first index is associated with the CG configuration to which the uplink grant of the first message configuration belongs.

[0099] As an embodiment, the first message includes a field, and the field indicates an offset.

[0100] As a sub-embodiment of this embodiment, the offset is used to determine the time interval in the time domain between any two adjacent uplink grants configured by the first message.

[0101] As a sub-embodiment of this embodiment, the offset is the time interval between a deadline of an uplink grant configured by the first message and a start time of another uplink grant immediately following the uplink grant configured by the first message.

[0102] As a sub-embodiment of this embodiment, the offset is used to determine the time interval between time slots occupied by any two adjacent uplink grants configured by the first message.

[0103] As a sub-embodiment of this embodiment, the offset is the time interval between the last time slot occupied by an uplink grant configured by the first message and the first time slot occupied by another uplink grant configured by the first message immediately following the uplink grant.

[0104] As a sub-embodiment of this embodiment, the offset is a non-negative number.

[0105] As a sub-embodiment of this embodiment, the offset is a positive number.

[0106] As a sub-embodiment of this embodiment, the offset is a non-negative integer.

[0107] As a sub-embodiment of this embodiment, the offset is a positive integer.

[0108] As a sub-embodiment of this embodiment, the unit of the offset is a time slot.

[0109] As a sub-embodiment of this embodiment, the unit of the offset is millisecond (ms).

[0110] As a sub-embodiment of this embodiment, the unit of the offset is 0.5 time slots.

[0111] As a sub-embodiment of this embodiment, the unit of the offset is 0.5 milliseconds.

[0112] As an embodiment, the first message configures uplink grant in a configuration cycle.

[0113] As an embodiment, the first message configures uplink grant in multiple consecutive configuration cycles.

[0114] As an embodiment, the first message configures uplink grant in at least one consecutive configuration period.

[0115] As an embodiment, the uplink grant configured in the first message is related.

[0116] As an embodiment, at least two uplink grants in the uplink grants configured by the first message are unrelated.

[0117] As an embodiment, the uplink grant configured in the first message is for the same MAC (Medium Access Control) entity.

[0118] As an embodiment, the uplink grant configured in the first message is for the same UL BWP (Bandwidth Part).

[0119] As an embodiment, the uplink grant configured by the first message occupies PUSCH resources.

[0120] As an embodiment, the type of uplink grant configured in the first message is configured grantType 1.

[0121] As an embodiment, the type of uplink grant configured in the first message is configured grantType 2.

[0122] As an embodiment, the uplink grant configured by the first message is used for UL-SCH (Uplink Shared Channel) data transmission.

[0123] As an embodiment, the uplink grant configured in the first message belongs to the same CG configuration.

[0124] As an embodiment, the uplink grant configured by the first message belongs to the same configuration period.

[0125] As an embodiment, the first message is used to determine the start time of each configuration cycle.

[0126] As an embodiment, the first message is used to determine the duration of each configuration period.

[0127] As an embodiment, the first message is used to determine the number of transmission opportunities in each configuration period.

[0128] As an embodiment, the first message is used to determine the time interval between adjacent transmission opportunities in each configuration period.

[0129] As an embodiment, the first message configures at least one configuration period, and each configuration period in the at least one configuration period includes at least one uplink grant.

[0130] As an embodiment, the first message configures at least one configuration period, and each configuration period in the at least one configuration period includes at least one uplink grant.

[0131] As an embodiment, the first message is used to determine a CG configuration, the one CG configuration includes at least one configuration cycle, and each configuration cycle in the at least one configuration cycle includes at least one uplink grant.

[0132] As an embodiment, the number of uplink grants included in a configuration period is configurable.

[0133] As an embodiment, the number of uplink grants included in a configuration period is predefined.

[0134] As an embodiment, the number of uplink grants included in one configuration period is fixed.

[0135] As an embodiment, the number of uplink grants included in a configuration period is explicitly indicated by an RRC message.

[0136] As an embodiment, the number of uplink grants included in a configuration period is implicitly indicated by an RRC message.

[0137] As an embodiment, a configuration cycle is a configuration cycle of a CG.

[0138] As an embodiment, a configuration cycle is a configuration cycle in a CG configuration.

[0139] As an embodiment, uplink grants in a configuration period have the same MCS or at least one of frequency domain resources or PUSCH duration.

[0140] As an embodiment, the uplink grant configured by the first message is a plurality of consecutive PUSCH resources in a plurality of configuration periods.

[0141] As an embodiment, the uplink grant configured by the first message is a plurality of discontinuous PUSCH resources in a plurality of configuration periods.

[0142] As an embodiment, the uplink grant configured by the first message belongs to multiple configuration periods.

[0143] As an embodiment, the uplink grant configured by the first message belongs to a continuous configuration period.

[0144] As an embodiment, the uplink grant configured by the first message belongs to a maximum of M1 configuration periods; M1 is a positive integer.

[0145] As an embodiment, the K2 uplink grants belong to uplink grants in the same configuration period of the first message configuration.

[0146] As an embodiment, the K2 uplink grants belong to uplink grants in multiple configuration periods configured by the first message.

[0147] As an embodiment, the K2 uplink grants belong to uplink grants in at least one configuration period of the first message configuration.

[0148] As an embodiment, the K2 uplink grants belong to a maximum of M1 configuration periods; and M1 is a positive integer.

[0149] As an embodiment, the K2 uplink grants belong to M1 configuration periods; and M1 is a positive integer.

[0150] As an embodiment, the M1 is predefined.

[0151] As an embodiment, the M1 is configurable.

[0152] As an embodiment, M1 is fixed.

[0153] As an embodiment, M1 is 2.

[0154] As an embodiment, M1 is 1.

[0155] As an embodiment, the M1 configuration cycles are adjacent.

[0156] As an embodiment, each uplink grant configured by the first message is an uplink grant (ULgrant).

[0157] As an embodiment, each uplink grant configured by the first message is part of a UL grant.

[0158] As an embodiment, each uplink grant configured in the first message is a transmission opportunity (Transmission Occasion, TO).

[0159] As an embodiment, each uplink grant configured by the first message is a sending opportunity in a configuration period.

[0160] As an embodiment, each uplink grant configured by the first message is an uplink resource block.

[0161] As an embodiment, each uplink grant configured by the first message is a PUSCH (Physical uplink shared channel) resource.

[0162] As an embodiment, each uplink grant configured by the first message occupies one PUSCH resource.

[0163] As an embodiment, each uplink grant configured by the first message occupies a PUSCH opportunity.

[0164] As an embodiment, each uplink grant configured by the first message corresponds to a PUSCH duration.

[0165] As an embodiment, each uplink grant configured by the first message corresponds to a PUSCH transmission.

[0166] As an embodiment, each uplink grant configured by the first message is configured with an index.

[0167] As a sub-embodiment of this embodiment, the one index is unique within a configuration cycle.

[0168] As a sub-embodiment of this embodiment, the index is used to identify an uplink grant within a configuration period.

[0169] As an embodiment, at least one symbol is included between any two adjacent configuration periods.

[0170] As an embodiment, any two adjacent configuration periods do not include any symbol.

[0171] As an embodiment, any two uplink grants configured in the first message do not include the same time domain resources.

[0172] As an embodiment, any two uplink grants configured by the first message are not allocated the same time domain resources.

[0173] As an embodiment, any two uplink grants configured in the first message do not include the same symbol.

[0174] As an embodiment, any symbol does not belong to any two uplink grants configured in the first message at the same time.

[0175] As an embodiment, for two adjacent uplink grants configured by the first message, the expiration time of an earlier uplink grant in the time domain is earlier than the start time of a later uplink grant in the time domain.

[0176] As an embodiment, for two adjacent uplink grants configured in the first message, at least one symbol is included between the expiration time of an earlier uplink grant in the time domain and the start time of a later uplink grant in the time domain.

[0177] As an embodiment, for two adjacent uplink grants configured by the first message, no symbol is included between the end time of an earlier uplink grant in the time domain and the start time of a later uplink grant in the time domain.

[0178] As an embodiment, any two uplink grants configured by the first message do not overlap in time, which means that the PUSCH durations (durations) of any two uplink grants configured by the first message do not overlap in time.

[0179] As an embodiment, the first symbol set is at least one symbol.

[0180] As an embodiment, the first symbol set is at least one symbol that is continuous in the time domain.

[0181] As an embodiment, the first symbol set is a plurality of symbols that are continuous in the time domain.

[0182] As an embodiment, the first symbol set is all symbols in a time slot.

[0183] As an embodiment, the first symbol set is a portion of symbols in a time slot.

[0184] As an embodiment, the first symbol set belongs to the same time slot.

[0185] As an embodiment, the first symbol set belongs to at least one time slot.

[0186] As an embodiment, the first symbol set belongs to multiple time slots.

[0187] As an embodiment, the first set of symbols is not continuous in the time domain.

[0188] As an embodiment, whether the first set of symbols is continuous in the time domain is configurable.

[0189] As an embodiment, the first symbol set is a time domain resource configured by the second message.

[0190] As an embodiment, the first symbol set is a time domain resource determined by the second message.

[0191] As an embodiment, the first symbol set is a time domain resource activated by the second message.

[0192] As an embodiment, the first symbol set is a time domain resource configured and activated by the second message.

[0193] As an embodiment, the first symbol set is a time domain resource corresponding to a time-frequency resource allocated to the secondary link.

[0194] As an embodiment, the above method reduces the impact on secondary link communication.

[0195] As an embodiment, the first symbol set is used for network energy saving.

[0196] As an embodiment, the first symbol set is the inactive time of cell DRX (Discontinuous Reception) / DTX (Discontinuous Transmission).

[0197] As an embodiment, the first symbol set is the time at which a timer is running.

[0198] As an embodiment, the first symbol set is the time when a ra-ResponseWindow is running.

[0199] As an embodiment, the first symbol set is the time when a msgB-ResponseWindow is running.

[0200] As an embodiment, the first symbol set is the time at which a ra-ContentionResolutionTimer is running.

[0201] As an embodiment, the second message is an RRC message.

[0202] As an embodiment, the second message includes at least one RRC message.

[0203] As an embodiment, the second message includes at least one RRC IE.

[0204] As an embodiment, the second message includes at least one RRC domain.

[0205] As an embodiment, the second message includes signaling of at least one protocol layer below the RRC protocol layer.

[0206] As an embodiment, the second message is signaling of at least one protocol layer below the RRC protocol layer.

[0207] As an embodiment, the second message configures the first set of symbols.

[0208] As an embodiment, the second message is used to determine the first set of symbols.

[0209] As an embodiment, the second message configures and activates the first set of symbols.

[0210] As an embodiment, the second message includes at least one RRC message, and the at least one RRC message is used to configure the first symbol set; the second message includes signaling of at least one protocol layer below the RRC protocol layer, and the signaling of the at least one protocol layer below the RRC protocol layer is used to activate the first symbol set.

[0211] As an embodiment, the second message indicates the first set of symbols in time domain resources for downlink transmission.

[0212] As a sub-embodiment of this embodiment, the time domain resource for downlink transmission is a downlink time slot.

[0213] As a sub-embodiment of this embodiment, the time domain resource for downlink transmission is a flexible time slot.

[0214] As a sub-embodiment of this embodiment, the time domain resource for downlink transmission is a downlink time slot or a flexible time slot.

[0215] As a sub-embodiment of this embodiment, each symbol in the first symbol set is configured for subband non-overlapping full duplex (SBFD).

[0216] As a sub-embodiment of this embodiment, a SIB1 (System Information Block 1) is used to configure the time domain resources for downlink transmission.

[0217] As a sub-embodiment of this embodiment, a ServingCellConfigCommon IE is used to configure the time domain resources for downlink transmission.

[0218] As a sub-embodiment of this embodiment, a ServingCellConfigCommonSIB IE is used to configure the time domain resources for downlink transmission.

[0219] As a sub-embodiment of this embodiment, a BWP-Uplink IE is used to configure the time domain resources for downlink transmission.

[0220] As a sub-embodiment of this embodiment, a BWP-UplinkCommon IE is used to configure the time domain resources for downlink transmission.

[0221] As a sub-embodiment of this embodiment, a tdd-UL-DL-ConfigurationCommon field is used to configure the time domain resources for downlink transmission.

[0222] As a sub-embodiment of this embodiment, an RRC domain whose name includes tdd-UL-DL-ConfigurationCommon is used to configure the time domain resources for downlink transmission.

[0223] As a sub-embodiment of this embodiment, a TDD-UL-DL-ConfigCommon IE is used to configure the time domain resources for downlink transmission.

[0224] As a sub-embodiment of this embodiment, a TDD-UL-DL-Pattern IE is used to configure the time domain resources for downlink transmission.

[0225] As a sub-embodiment of this embodiment, a TDD-UL-DL-ConfigDedicated IE is used to configure the time domain resources for downlink transmission.

[0226] As an embodiment, the first symbol set is an activated measurement gap.

[0227] As a sub-embodiment of this embodiment, the above method reduces the impact on the activated measurement interval.

[0228] As a sub-embodiment of this embodiment, the first symbol set is the duration of an activated measurement interval.

[0229] As a sub-embodiment of this embodiment, the first symbol set is a time domain resource occupied by an activated measurement interval.

[0230] As a sub-embodiment of this embodiment, the first symbol set is configured for the time of an activated measurement interval.

[0231] As a sub-embodiment of this embodiment, the one activated measurement interval is used to perform measurement.

[0232] As a sub-embodiment of this embodiment, the one activated measurement interval is an FR1 (Frequency range 1) measurement interval.

[0233] As a sub-embodiment of this embodiment, the activated measurement interval is a FR2 (Frequency range 2) measurement interval.

[0234] As a sub-embodiment of this embodiment, the frequency domain resources corresponding to the activated measurement interval overlap with the frequency domain resources granted by the uplink configured by the first message.

[0235] As a sub-embodiment of this embodiment, the frequency domain resources corresponding to the one activated measurement interval belong to the frequency domain resources granted by the uplink configured by the first message.

[0236] As a sub-embodiment of this embodiment, the frequency domain resources granted in the uplink configured by the first message belong to the frequency domain resources corresponding to the one activated measurement interval.

[0237] As a sub-embodiment of this embodiment, the frequency domain resources corresponding to the one activated measurement interval and the frequency domain resources granted by the uplink configured by the first message do not overlap.

[0238] As an embodiment, the first symbol set is a time domain resource allocated to a candidate uplink grant.

[0239] As a sub-embodiment of this embodiment, the first symbol set is a PUSCH duration allocated to a candidate uplink grant.

[0240] As a sub-embodiment of this embodiment, the candidate uplink grant is addressed to the Temporary C-RNTI.

[0241] As a sub-embodiment of this embodiment, the above method reduces the impact on random access.

[0242] As a sub-embodiment of this embodiment, the candidate uplink grant is dynamically received on the PDCCH.

[0243] As a sub-embodiment of this embodiment, the candidate uplink grant is received in a random access response (Random Access Response, RAR).

[0244] As a sub-embodiment of this embodiment, the above method reduces the impact on random access.

[0245] As a sub-embodiment of this embodiment, the candidate uplink grant is configured semi-persistently by RRC.

[0246] As a sub-embodiment of this embodiment, the candidate uplink grant is determined according to the PUSCH resource associated with MSGA (Message A).

[0247] As a sub-embodiment of this embodiment, the above method reduces the impact on random access.

[0248] As a sub-embodiment of this embodiment, the candidate uplink grant is a DG (Dynamic Grant).

[0249] As a sub-embodiment of this embodiment, the above method reduces the impact on uplink grants of dynamic scheduling.

[0250] As a sub-embodiment of this embodiment, the candidate uplink grant is a CG; the one CG is not an uplink grant in the uplink grant configured by the first message.

[0251] As a sub-embodiment of this embodiment, the priority of the candidate uplink grant is higher than the target uplink grant.

[0252] As a sub-embodiment of this embodiment, the above method reduces the impact on uplink grants with higher priorities.

[0253] As a sub-embodiment of this embodiment, the MAC entity of the first node is configured with lch-based Prioritization.

[0254] As a sub-embodiment of this embodiment, the MAC entity of the first node is not configured with lch-based Prioritization.

[0255] As a sub-embodiment of this embodiment, the MAC entity of the first node is configured with lch-basedPrioritization; the candidate uplink grant is addressed to Temporary C-RNTI, or the candidate uplink grant is received in a random access response, or the candidate uplink grant is associated with an MSGA payload.

[0256] As a sub-embodiment of this embodiment, the MAC entity of the first node is not configured with lch-basedPrioritization; the candidate uplink grant is dynamically received on the PDCCH, or the candidate uplink grant is received in a random access response, or the candidate uplink grant is associated with the MSGA payload.

[0257] As an embodiment, the position of the first control information on the PUSCH corresponding to the first uplink grant is predefined.

[0258] As an embodiment, the position of the first control information on the PUSCH corresponding to the first uplink grant is RRC configured.

[0259] As an embodiment, the position of the first control information on the PUSCH corresponding to the first uplink grant is calculated.

[0260] As an embodiment, the first control information is transmitted on a physical layer channel.

[0261] As an embodiment, the first control information is multiplexed on a physical layer channel.

[0262] As an embodiment, the first control information is transmitted on PUSCH.

[0263] As an embodiment, the first control information occupies PUSCH resources.

[0264] As an embodiment, the first control information occupies the PUSCH resources granted by the first uplink.

[0265] As an embodiment, the first control information is a partial bit in a PUSCH transmission.

[0266] As an embodiment, the first control information is a UCI (Uplink Control Information, uplink control information).

[0267] As an embodiment, the first control information is a CG-UCI.

[0268] As an embodiment, the first control information is a UTO (Unused Transmission Occasion, unused transmission opportunity) - UCI.

[0269] As an embodiment, the number of bits occupied by the first control information is fixed.

[0270] As an embodiment, the number of bits occupied by the first control information is configurable.

[0271] As an embodiment, the number of bits occupied by the first control information is predefined.

[0272] As an embodiment, the number of bits occupied by the first control information is a default number.

[0273] As an embodiment, the first control information includes a bit map.

[0274] As an embodiment, the first control information includes a bit map, and any bit in the bit map corresponds to an uplink grant.

[0275] As a sub-embodiment of this embodiment, if one bit in the bit map in the first control information is set to 1, the first control information indicates that the uplink grant corresponding to the one bit is not used; if one bit in the bit map in the first control information is set to 0, the first control information indicates that the uplink grant corresponding to the one bit is not unused.

[0276] As a sub-embodiment of this embodiment, if one bit in the bit map in the first control information is set to 0, the first control information indicates that the uplink grant corresponding to the one bit is not used; if one bit in the bit map in the first control information is set to 1, the first control information indicates that the uplink grant corresponding to the one bit is not unused.

[0277] As an embodiment, the first control information is a bit map.

[0278] As an embodiment, the first control information is a bit map, and any bit in the first control information corresponds to an uplink grant configured by the first message.

[0279] As an embodiment, the first control information is a bit map, and any bit in the first control information is not reserved.

[0280] As an embodiment, the above method improves resource scheduling flexibility.

[0281] As an embodiment, the first control information is a bit map, and at least one bit in the first control information is reserved.

[0282] As an embodiment, the above method avoids prematurely indicating whether an uplink grant is not used.

[0283] As an embodiment, the above method reduces the monitoring complexity.

[0284] As an embodiment, the above method reduces the probability of erroneous decoding.

[0285] As an embodiment, the candidate for indicating each uplink grant in the K2 uplink grants by the first control information includes one of not using or not not using.

[0286] As an embodiment, the first control information indicates that at least one of the K2 uplink grants is not used.

[0287] As an embodiment, the first control information indicates that any uplink grant among the K2 uplink grants is unused or not unused.

[0288] As an embodiment, non-use / non-non-use means: non-use / use.

[0289] As an embodiment, not using / not not using means: will not use / will use.

[0290] As an embodiment, not using / not not using means: not needing to be retained / needing to be retained.

[0291] As an embodiment, not using / not not using means: not needed / needed.

[0292] As an embodiment, unused / not unused refers to: unused / not unused.

[0293] As an embodiment, unused / non-unused refers to: unused / used.

[0294] As an embodiment, K2 is variable.

[0295] As a sub-embodiment of this embodiment, K2 is configurable.

[0296] As a sub-embodiment of this embodiment, the above method saves signaling overhead.

[0297] As a sub-embodiment of this embodiment, the above method improves resource utilization.

[0298] As a sub-embodiment of this embodiment, the K2 is configured by RRC signaling.

[0299] As an embodiment, K2 is fixed.

[0300] As a sub-embodiment of this embodiment, the K2 is predefined.

[0301] As a sub-embodiment of this embodiment, K2 is the default.

[0302] As a sub-embodiment of this embodiment, the K2 does not change with the configuration of the RRC signaling.

[0303] As a sub-embodiment of this embodiment, the above method reduces the complexity of blind detection.

[0304] As a sub-embodiment of this embodiment, the above method reduces erroneous transmission caused by missed detection.

[0305] As a sub-embodiment of this embodiment, the above method reduces the impact on the protocol.

[0306] As an embodiment, K2 is not greater than the number of uplink grants in a configuration cycle.

[0307] As an embodiment, K2 is smaller than the number of uplink grants in a configuration cycle.

[0308] As an embodiment, K2 is greater than the number of uplink grants in a configuration cycle.

[0309] As an embodiment, whether K2 is greater than the number of uplink grants in a configuration period is configured by the base station.

[0310] As an embodiment, K2 is the size of the first bit map in the first control information.

[0311] As an embodiment, K2 is the number of bits occupied by the first bit map in the first control information.

[0312] As an embodiment, the maximum value of K2 is the number of uplink grants configured by the first message in a configuration cycle.

[0313] As an embodiment, the maximum value of K2 is the number of uplink grants configured by the first message in multiple configuration cycles.

[0314] As an embodiment, K2 is the number of uplink grants configured by the first message in a configuration cycle.

[0315] As an embodiment, K2 is the number of uplink grants configured by the first message in multiple configuration cycles.

[0316] As an embodiment, K2 is not greater than the number of bits occupied by the first control information; the first control information is a bit map.

[0317] As an embodiment, the number of bits occupied by K2 and the first control information is equal; the first control information is a bit map.

[0318] As an embodiment, the more uplink grants that overlap with the first symbol set in the uplink grants configured by the first message in one configuration period, the smaller the K2 is; the uplink grants configured by the first message in the one configuration period include at least part of the K2 uplink grants.

[0319] As an embodiment, the smaller the number of uplink grants configured by the first message in a configuration cycle that are later than the first uplink grant, the smaller the K2; the uplink grant configured by the first message in the one configuration cycle includes at least part of the K2 uplink grants.

[0320] As an embodiment, the first uplink grant is one of the uplink grants configured by the first message, and each of the K2 uplink grants is one of the uplink grants configured by the first message.

[0321] As an embodiment, the time domain resources allocated to the K2 uplink grants are later than the time domain resources allocated to the first uplink grant.

[0322] As an embodiment, the K2 uplink grants are later than the first uplink grant in the time domain.

[0323] As an embodiment, the time domain position of any uplink grant among the K2 uplink grants is later than the time domain position of the first uplink grant.

[0324] As an embodiment, the time domain position of any uplink grant among the K2 uplink grants does not overlap with the first uplink grant.

[0325] As an embodiment, the K2 uplink grants are K2 consecutive uplink grants among the uplink grants configured by the first message.

[0326] As an embodiment, the K2 uplink grants are K2 consecutive uplink grants immediately following the first uplink grant in the uplink grant configured by the first message.

[0327] As an embodiment, the K2 uplink grants are K2 uplink grants that are non-overlapping with the first set of symbols and follow the first uplink grant in the uplink grant configured by the first message.

[0328] As an embodiment, the K2 uplink grants are continuous uplink grants configured by the first message.

[0329] As an embodiment, the K2 uplink grants are discontinuous uplink grants configured by the first message.

[0330] As an embodiment, the K2 uplink grants and the first uplink grant belong to the same configuration period.

[0331] As an embodiment, at least one uplink grant among the K2 uplink grants and the first uplink grant do not belong to the same configuration period.

[0332] As an embodiment, the time domain positions of the K2 uplink grants depend on the time domain positions of the uplink grants configured in the first message.

[0333] As an embodiment, the K2 uplink grants are K2 consecutive uplink grants after the first uplink grant configured by the first message.

[0334] As an embodiment, the K2 uplink grants are K2 valid uplink grants after the first uplink grant configured by the first message.

[0335] As an embodiment, the K2 uplink grants are K2 uplink grants after the first uplink grant configured by the first message.

[0336] As an embodiment, the K2 uplink grants depend on the time domain position of the uplink grant configured by the first message and the number of bits occupied by the first control information.

[0337] As an embodiment, the K2 uplink grants are K2 consecutive uplink grants after the first uplink grant configured by the first message.

[0338] As an embodiment, the K2 uplink grants are K2 valid uplink grants after the first uplink grant configured by the first message.

[0339] As an embodiment, the time domain positions of the K2 uplink grants depend on the time domain positions of the uplink grants configured by the first message and the position of the first symbol set.

[0340] As an embodiment, K2 depends on the time domain position of the uplink grant configured by the first message.

[0341] As an embodiment, the K2 depends on the time domain position of the first uplink grant in the uplink grant configured by the first message.

[0342] As an embodiment, the K2 relies on the number of uplink grants whose time domain position in the uplink grant configured by the first message is later than that of the first uplink grant.

[0343] As an embodiment, the K2 and the first message configure uplink grants whose time domain positions in the uplink grant are later than the first uplink grant by an equal number.

[0344] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant.

[0345] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message, the time domain position of which is later than that of the first uplink grant and belongs to the same configuration period as the first uplink grant.

[0346] As an embodiment, the time domain position in the uplink grant configured by K2 and the first message is later than that of the first uplink grant and is equal to the number of uplink grants that belong to the same configuration period as the first uplink grant.

[0347] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message, which are later in time domain than the first uplink grant and belong to the same configuration period as the first uplink grant.

[0348] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message, the time domain position of which is later than the first uplink grant and belongs to the first time interval.

[0349] As an embodiment, the time domain position of the uplink grant configured by K2 and the first message is later than that of the first uplink grant and the number of uplink grants belonging to the first time interval is equal.

[0350] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message, which are later in time domain than the first uplink grant and belong to the first time interval.

[0351] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant and no earlier than the first moment.

[0352] As an embodiment, the number of uplink grants in the uplink grant configured by K2 and the first message whose time domain positions are later than the first uplink grant and no earlier than the first moment is equal.

[0353] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant and not earlier than the first moment.

[0354] As an embodiment, if the time domain position of one uplink grant in the uplink grant configured by the first message is earlier than the first uplink grant, the first control information does not indicate the one uplink grant.

[0355] As an embodiment, the first control information may indicate an uplink grant only if the time domain position of one uplink grant in the uplink grant configured by the first message is later than the first uplink grant.

[0356] As an embodiment, K2 depends on the time domain position of the uplink grant configured by the first message and the position of the first symbol set.

[0357] As an embodiment, the K2 depends on the time domain position of the first uplink grant in the uplink grant configured by the first message and the position of the first symbol set.

[0358] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant and does not overlap with the first set of symbols.

[0359] As an embodiment, the K2 and the first message configure an uplink grant whose time domain position in the uplink grant is later than the first uplink grant and the number of uplink grants that do not overlap with the first symbol set is equal.

[0360] As an embodiment, the K2 is no greater than the number of uplink grants in the uplink grant configured by the first message that are later in time domain than the first uplink grant and do not overlap with the first set of symbols.

[0361] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message, whose time domain position is later than the first uplink grant, which belongs to the same configuration period as the first uplink grant and does not overlap with the first symbol set.

[0362] As an embodiment, the time domain position in the uplink grant configured by K2 and the first message is later than that of the first uplink grant and is equal to the number of uplink grants that belong to the same configuration period as the first uplink grant and do not overlap with the first symbol set.

[0363] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message, which are later than the first uplink grant in time domain position, belong to the same configuration period as the first uplink grant, and do not overlap with the first symbol set.

[0364] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message, which have a time domain position later than the first uplink grant, belong to the first time interval, and do not overlap with the first symbol set.

[0365] As an embodiment, the K2 and the first message configure an uplink grant whose time domain position in the uplink grant is later than the first uplink grant, which belongs to the first time interval and does not overlap with the first symbol set, and are equal in number.

[0366] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message, which have a time domain position later than the first uplink grant, belong to the first time interval, and do not overlap with the first symbol set.

[0367] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant and not earlier than the first moment and does not overlap with the first symbol set.

[0368] As an embodiment, the K2 and the first message configure an uplink grant whose time domain position in the uplink grant is later than the first uplink grant and not earlier than the first moment and does not overlap with the first symbol set, and the number of uplink grants is equal.

[0369] As an embodiment, the K2 is not greater than the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant and not earlier than the first moment and does not overlap with the first symbol set.

[0370] As an embodiment, if an uplink grant whose time domain position in the uplink grant configured by the first message is later than that of the first uplink grant overlaps with the first set of symbols, the first control information does not indicate the uplink grant.

[0371] As an embodiment, the first control information may indicate an uplink grant only if an uplink grant whose time domain position in the uplink grant configured by the first message is later than that of the first uplink grant and does not overlap with the first symbol set.

[0372] As an embodiment, the symbol is a single carrier symbol.

[0373] As an embodiment, the symbol is a multi-carrier symbol.

[0374] As an embodiment, the symbol is an OFDM (Orthogonal Frequency Division Multiplexing) symbol.

[0375] As an embodiment, the symbol is an SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbol.

[0376] As an embodiment, the symbol is a DFT-S-OFDM (Discrete Fourier Transform Spread OFDM) symbol.

[0377] As an embodiment, the symbol is a FBMC (Filter Bank Multi Carrier) symbol.

[0378] As an embodiment, the overlap refers to overlap.

[0379] As an embodiment, the overlap refers to a complete overlap.

[0380] As an embodiment, the overlap refers to a partial overlap.

[0381] As an embodiment, the overlapping refers to at least partial overlapping.

[0382] As an embodiment, the overlap refers to non-orthogonality.

[0383] As an embodiment, the overlap refers to including the same time domain resources.

[0384] As an embodiment, the non-overlapping refers to orthogonality.

[0385] As an embodiment, the non-overlapping means not including the same time domain resources.

[0386] Example 2

[0387] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2The network architecture 200 of the 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system is illustrated. The 5G NR / LTE / LTE-A network architecture 200 may be referred to as 5GS (5G System) / EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS / EPS 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, an HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and an Internet service 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet switching services, but it will be readily understood by those skilled in the art that the various concepts presented throughout this application can be extended to networks or other cellular networks that provide circuit switching services. RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol terminations toward UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a TRP (transmitting receiving node) or some other suitable terminology. Node 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable term.Node 203 is connected to 5GC / EPC210 via an S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is a control node that handles signaling between UE201 and 5GC / EPC210. ​​In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocal) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet service 230. Internet service 230 includes operator-corresponding Internet protocol services, which may specifically include Internet, Intranet, IMS (IP Multimedia Subsystem) and packet-switched streaming services.

[0388] As an embodiment, the UE201 corresponds to the first node in the present application.

[0389] As an embodiment, the UE 201 is a user equipment (User Equipment, UE).

[0390] As an embodiment, the node 203 corresponds to the second node in the present application.

[0391] As an embodiment, the node 203 is a base station (BS).

[0392] As an embodiment, the node 203 is a base transceiver station (Base Transceiver Station, BTS).

[0393] As an embodiment, the node 203 is a Node B (NB).

[0394] As an embodiment, the node 203 is a gNB.

[0395] As an embodiment, the node 203 is an eNB.

[0396] As an embodiment, the node 203 is an ng-eNB.

[0397] As an embodiment, the node 203 is an en-gNB.

[0398] As an embodiment, the node 203 is a CU (Centralized Unit).

[0399] As an embodiment, the node 203 is a DU (Distributed Unit).

[0400] As an embodiment, the node 203 is a user equipment.

[0401] As an embodiment, the node 203 is a relay.

[0402] As an embodiment, the node 203 is a gateway.

[0403] As an embodiment, the user equipment supports transmission of a terrestrial network (Non-Terrestrial Network, NTN).

[0404] As an embodiment, the user equipment supports transmission of a non-terrestrial network (Terrestrial Network).

[0405] As an embodiment, the user equipment supports transmission in a network with a large delay difference.

[0406] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0407] As an embodiment, the user equipment includes an aircraft.

[0408] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0409] As an embodiment, the user equipment includes a vessel.

[0410] As an embodiment, the user equipment includes an Internet of Things terminal.

[0411] As an embodiment, the user equipment includes a terminal of the industrial Internet of Things.

[0412] As an embodiment, the user equipment includes a device supporting low-latency and high-reliability transmission.

[0413] As an embodiment, the user equipment includes a test device.

[0414] As an embodiment, the user equipment includes a signaling tester.

[0415] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0416] As an embodiment, the base station device supports transmission in a network with a large delay difference.

[0417] As an embodiment, the base station device supports transmission of a terrestrial network.

[0418] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.

[0419] As an embodiment, the base station device includes a micro cell base station.

[0420] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0421] As an embodiment, the base station device includes a home base station (Femtocell).

[0422] As an embodiment, the base station device includes a base station device that supports a large delay difference.

[0423] As an embodiment, the base station device includes a flying platform device.

[0424] As an embodiment, the base station device includes a satellite device.

[0425] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

[0426] As an embodiment, the base station device includes a CU.

[0427] As an embodiment, the base station device includes a DU.

[0428] As an embodiment, the base station device includes a testing device.

[0429] As an embodiment, the base station equipment includes a signaling tester.

[0430] As an embodiment, the base station equipment includes an IAB (Integrated Access and Backhaul)-node.

[0431] As an embodiment, the base station device includes an IAB-donor.

[0432] As an embodiment, the base station device includes an IAB-donor-CU.

[0433] As an embodiment, the base station device includes an IAB-donor-DU.

[0434] As an embodiment, the base station device includes an IAB-DU.

[0435] As an embodiment, the base station device includes IAB-MT.

[0436] As an embodiment, the relay includes a relay.

[0437] As an embodiment, the relay includes an L3 relay.

[0438] As an embodiment, the relay includes an L2 relay.

[0439] As an embodiment, the relay includes a router.

[0440] As an embodiment, the relay includes a switch.

[0441] As an embodiment, the relay includes a user equipment.

[0442] As an embodiment, the relay includes a base station device.

[0443] Example 3

[0444] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture for the control plane 300 is shown in three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to as PHY 301 in this article. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by encrypting data packets, and provides inter-zone mobility support. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data packets to compensate for out-of-order reception due to HARQ (Hybrid Automatic Repeat Request). The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and using RRC signaling to configure the lower layers. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). In the user plane 350, the radio protocol architecture is substantially the same as the corresponding layers and sublayers in the control plane 300 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity.

[0445] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.

[0446] As an example, Figure 3The wireless protocol architecture in is applicable to the second node in this application.

[0447] As an embodiment, the first message in the present application is generated in the RRC306.

[0448] As an embodiment, the first message in the present application is generated by the MAC302 or MAC352.

[0449] As an embodiment, the first message in the present application is generated by the PHY301 or PHY351.

[0450] As an embodiment, the second message in the present application is generated in the RRC306.

[0451] As an embodiment, the second message in the present application is generated by the MAC302 or MAC352.

[0452] As an embodiment, the second message in the present application is generated by the PHY301 or PHY351.

[0453] As an embodiment, the first control information in the present application is generated in the RRC306.

[0454] As an embodiment, the first control information in the present application is generated by the MAC302 or MAC352.

[0455] As an embodiment, the first control information in the present application is generated in the PHY301 or PHY351.

[0456] Example 4

[0457] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in the attached figure. Figure 4 shown. Figure 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

[0458] The first communication device 450 includes a controller / processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter / receiver 454 and an antenna 452.

[0459] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 and an antenna 420 .

[0460] In transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller / processor 475. The controller / processor 475 implements the functionality of the L2 layer. In transmission from the second communication device 410 to the first communication device 450, the controller / processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communication device 450 based on various priority metrics. The controller / processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate forward error correction (FEC) at the second communication device 410, as well as mapping of signal constellations based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation on the time-domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream, and then provides it to a different antenna 420.

[0461] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the controller / processor 459. The controller / processor 459 implements the functions of the L2 layer. The controller / processor 459 may be associated with a memory 460 that stores program codes and data. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

[0462] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream, and then provides it to the antenna 452.

[0463] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly implement the functions of the L1 layer. The controller / processor 475 implements the L2 layer functions. The controller / processor 475 can be associated with a memory 476 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0464] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: receives a first message, the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; receives a second message, the second message indicates a first symbol set; sends first control information in the first uplink grant, the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; wherein the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; K2 is a positive integer.

[0465] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: receiving a first message, the first message configuring an uplink grant, any two uplink grants configured by the first message do not overlap in time; receiving a second message, the second message indicating a first symbol set; sending first control information in the first uplink grant, the first control information indicating whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; wherein the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0466] As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor. The second communication device 410 at least: sends a first message, the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; sends a second message, the second message indicates a first symbol set; receives first control information, the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; wherein the receiver of the first message sends the first control information in the first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; K2 is a positive integer.

[0467] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: sending a first message, the first message configuring an uplink grant, any two uplink grants configured by the first message do not overlap in time; sending a second message, the second message indicating a first symbol set; receiving first control information, the first control information indicating whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; wherein the recipient of the first message sends the first control information in the first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0468] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a first message.

[0469] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first message.

[0470] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a second message.

[0471] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a second message.

[0472] As an embodiment, at least one of the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 is used to send first control information.

[0473] As an embodiment, at least one of the antenna 420, the receiver 418, the receiving processor 470, and the controller / processor 475 is used to receive first control information.

[0474] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0475] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0476] As an embodiment, the first communication device 450 is a user equipment.

[0477] As an embodiment, the first communication device 450 is a base station device.

[0478] As an embodiment, the first communication device 450 is a relay device.

[0479] As an embodiment, the second communication device 410 is a user equipment.

[0480] As an embodiment, the second communication device 410 is a base station device.

[0481] As an embodiment, the second communication device 410 is a relay device.

[0482] Example 5

[0483] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0484] for First node U01In step S5101, a first message is received, the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; in step S5102, a second message is received, the second message indicates a first symbol set; in step S5103, first control information is sent in the first uplink grant, the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant.

[0485] for Second node N02 In step S5201, the first message is sent; in step S5202, the second message is sent; in step S5203, the first control information is received.

[0486] In Embodiment 5, the K2 uplink grants depend on at least the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0487] As an embodiment, the first node U01 is a user equipment.

[0488] As an embodiment, the first node U01 is a base station device.

[0489] As an embodiment, the first node U01 is a relay device.

[0490] As an embodiment, the second node N02 is a base station device.

[0491] As an embodiment, the second node N02 is a user equipment.

[0492] As an embodiment, the second node N02 is a relay device.

[0493] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a base station device.

[0494] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0495] As an embodiment, the first node U01 is a base station device, and the second node N02 is a base station device.

[0496] As an embodiment, the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set.

[0497] As an embodiment, the K2 uplink grants depend on the first time interval.

[0498] As an embodiment, the K2 uplink grants depend on the number of bits occupied by the first control information; the first control information is a bit map.

[0499] As an embodiment, the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set or the first time interval or the number of bits occupied by the first control information.

[0500] As an embodiment, the K2 uplink grants are uplink grants whose time domain positions in the uplink grants configured by the first message are later than the first uplink grant and belong to the first time interval.

[0501] As an embodiment, the K2 uplink grants are uplink grants whose time domain positions in the uplink grants configured by the first message are later than the first uplink grant, belong to the first time interval, and do not overlap with the first symbol set.

[0502] Example 6

[0503] Embodiment 6 illustrates a schematic diagram of K2 uplink grants depending on the first time interval according to an embodiment of the present application, as shown in the attached figure. Figure 6 shown.

[0504] In Embodiment 6, the K2 uplink grants depend on a first time interval; the start time of the first time interval is related to the time domain position of the first uplink grant, and the length of the first time interval is configurable.

[0505] As an embodiment, the K2 uplink grants are K2 uplink grants that follow the first uplink grant in the uplink grant configured by the first message and that do not overlap with the first symbol set and belong to the first time interval.

[0506] As an embodiment, the K2 uplink grants are K2 consecutive uplink grants belonging to the first time interval among the uplink grants configured by the first message.

[0507] As an embodiment, the time domain position of any uplink grant among the K2 uplink grants belongs to the first time interval.

[0508] As an embodiment, the longer the first time interval is, the larger the K2 is; the uplink grant configured by the first message in the one configuration period includes at least part of the K2 uplink grants.

[0509] As an embodiment, the first time interval is configured by an RRC message.

[0510] As an embodiment, the first time interval is related to the time interval between two adjacent uplink grants configured by the first message.

[0511] As an embodiment, the first time interval is a time interval between two adjacent uplink grants configured by a positive integer number of the first messages.

[0512] As an embodiment, the starting moment of the first time interval is the starting moment of the time domain position of the first uplink grant.

[0513] As an embodiment, the starting time of the first time interval is the ending time of the time domain position of the first uplink grant.

[0514] As an embodiment, the starting time of the first time interval is a time point X1 symbols after the end time of the time domain position of the first uplink grant; and X1 is predefined.

[0515] As an embodiment, the starting time of the first time interval is related to the starting time of the time domain position of the first uplink grant.

[0516] As an embodiment, the starting time of the first time interval is related to the ending time of the time domain position of the first uplink grant.

[0517] Example 7

[0518] Embodiment 7 illustrates a schematic diagram of K2 uplink grants being valid uplink grants according to an embodiment of the present application, as shown in the attached figure. Figure 7 shown.

[0519] In Embodiment 7, the K2 uplink grants are valid uplink grants; the valid uplink grants satisfy at least one of not overlapping with the first symbol set, belonging to the first time interval, or being later than the first uplink grant in the time domain.

[0520] As an embodiment, any uplink grant among the K2 uplink grants is a valid uplink grant.

[0521] As an embodiment, the valid uplink grant is an uplink grant that does not overlap with the first set of symbols.

[0522] As an embodiment, the valid uplink grant is an uplink grant belonging to the first time interval.

[0523] As an embodiment, the valid uplink grant is an uplink grant that is later than the first uplink grant in the time domain.

[0524] As an embodiment, the valid uplink grant is an uplink grant that belongs to the first time interval and does not overlap with the first set of symbols.

[0525] As an embodiment, the valid uplink grant is an uplink grant that is later than the first uplink grant in the time domain, belongs to the first time interval, and does not overlap with the first set of symbols.

[0526] As an embodiment, the valid uplink grant is an uplink grant that is later than the first uplink grant in the time domain and does not overlap with the first set of symbols.

[0527] As an embodiment, the first control information indicates K2 valid uplink grants; the number of bits occupied by the first control information is K2.

[0528] As an embodiment, the number of bits occupied by the first control information varies with the number of valid uplink grants.

[0529] As an embodiment, the first control information indicates K2 valid uplink grants; the K2 is not greater than the number of bits occupied by the first control information.

[0530] As an embodiment, if K2 is smaller than the number of bits occupied by the first control information, at least one bit in the first control information is reserved.

[0531] Example 8

[0532] Embodiment 8 illustrates a schematic diagram of at least one bit in the first control information being reserved according to an embodiment of the present application, as shown in the attached figure. Figure 8 shown.

[0533] In Embodiment 8, the first control information is a bit map, the number of bits occupied by the first control information is greater than K2, and at least one bit in the first control information is reserved.

[0534] As an embodiment, the number of bits occupied by the first control information is fixed.

[0535] As an embodiment, the number of bits occupied by the first control information is predefined.

[0536] As an embodiment, the number of bits occupied by the first control information does not change dynamically.

[0537] As an embodiment, the reserved bits in the first control information are mapped to an uplink grant.

[0538] As an embodiment, the reserved bit in the first control information does not indicate whether the corresponding uplink grant is not used.

[0539] As an embodiment, the reserved bits in the first control information are not interpreted by the second node.

[0540] As an embodiment, the value of the reserved bit in the first control information is not used to indicate unused or non-unused.

[0541] As an embodiment, whether the reserved bit in the first control information is set to 0 or 1 is determined by the UE implementation.

[0542] As an embodiment, whether the reserved bit in the first control information is set to 0 or 1 is predefined.

[0543] As an embodiment, the reserved bits in the first control information are set to 0.

[0544] As an embodiment, the reserved bit in the first control information is set to 1.

[0545] As an embodiment, the overlap between the time domain position of an uplink grant configured in the first message and the position of the first symbol set is used to determine that a bit corresponding to the uplink grant in the first control information is reserved.

[0546] As an embodiment, the number of uplink grants in the first time interval is less than the number of bits occupied by the first control information, which is used to determine that the bit corresponding to the one uplink grant in the first control information is reserved.

[0547] Example 9

[0548] Embodiment 9 illustrates a schematic diagram of an uplink grant and a first symbol set of a first message configuration according to an embodiment of the present application, as shown in the attached figure. Fig. 9 As shown in the attached Fig. 9 In the figure, the horizontal axis represents time and the vertical axis represents frequency; each box filled with horizontal lines represents an uplink grant configured by the first message; the boxes filled with horizontal lines represent the first symbol set; the dotted boxes represent the first control information; uplink grant i, uplink grant i+1, uplink grant i+2, uplink grant i+3, uplink grant i+4 and uplink grant i+5 are 6 adjacent uplink grants; the first uplink grant is uplink grant i; uplink grant i+3 overlaps with the first symbol set.

[0549] In Embodiment 9, whether an uplink grant configured by the first message is one of the K2 uplink grants depends on whether the time domain position of the uplink grant configured by the first message overlaps with the position of the first symbol set.

[0550] As an embodiment, when the time domain position of an uplink grant among the K2 uplink grants and the position of the first symbol set do not overlap, the one uplink grant is an uplink grant among the K2 uplink grants; when the time domain position of an uplink grant among the K2 uplink grants and the position of the first symbol set overlap, the one uplink grant is not an uplink grant among the K2 uplink grants.

[0551] As an embodiment, if an uplink grant configured by the first message is one of the K2 uplink grants, the first control information indicates whether the uplink grant is not used; if an uplink grant configured by the first message is not one of the K2 uplink grants, the first control information does not indicate whether the uplink grant is not used.

[0552] As an embodiment, if the first control information indicates whether an uplink grant is not used, a bit in the bit map in the first control information corresponds to the uplink grant; if the first control information does not indicate whether an uplink grant is not used, any bit in the bit map in the first control information does not correspond to the uplink grant.

[0553] As an embodiment, the first bit in the first control information corresponds to the uplink grant i+1, the second bit corresponds to the uplink grant i+2, the third bit corresponds to the uplink grant i+4, the second bit corresponds to the uplink grant i+5, and so on; any bit in the first control information does not correspond to the uplink grant i+3.

[0554] As an embodiment, this embodiment does not limit the implementation method of the first control information.

[0555] As an embodiment, this embodiment does not limit the number of bits occupied by the first control information.

[0556] As an embodiment, this embodiment does not limit the number of bits occupied by the bit map in the first control information.

[0557] As an embodiment, this embodiment does not limit the time-frequency position of the first control information in the first uplink grant.

[0558] As an embodiment, this embodiment does not limit whether the frequency domain resources occupied by the uplink grant configured by the first message are the same.

[0559] As an embodiment, this embodiment does not limit whether the lengths of the time domain resources occupied by the uplink grant configured by the first message are the same.

[0560] As an embodiment, this embodiment does not limit whether the time domain lengths between adjacent uplink grants configured by the first message are the same.

[0561] As an embodiment, this embodiment does not limit whether the 6 uplink grants belong to the same configuration period.

[0562] As an embodiment, this embodiment does not limit the number of uplink grants in each configuration period configured by the first message.

[0563] Example 10

[0564] Embodiment 10 illustrates a schematic diagram of the time domain position of the uplink grant configured by K2 depending on the first message according to an embodiment of the present application, as shown in the attached Fig.10 As shown in the attached Fig.10 In the figure, the horizontal axis represents time and the vertical axis represents frequency; each box filled with horizontal lines represents an uplink grant configured by the first message; uplink grant i, uplink grant i+1, uplink grant i+2, uplink grant i+3 and uplink grant i+4 are 5 adjacent uplink grants.

[0565] In embodiment 10, the K2 depends on the time domain position of the uplink grant configured by the first message; the number of bits occupied by the K2 and the first control information is equal; and the first control information is a bit map.

[0566] As an embodiment, K2 is the number of bits occupied by the first control information.

[0567] As an embodiment, the number of bits occupied by the first control information is variable.

[0568] As an embodiment, the number of bits occupied by the first control information changes dynamically.

[0569] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message, the time domain position of which is later than that of the first uplink grant and belongs to the same configuration period as the first uplink grant.

[0570] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message, the time domain position of which is later than the first uplink grant and belongs to the first time interval.

[0571] As an embodiment, K2 depends on the number of uplink grants in the uplink grant configured by the first message whose time domain position is later than the first uplink grant and no earlier than the first moment.

[0572] As an embodiment, the first uplink grant is uplink grant i, the dotted box F10.1 represents the first control information, the bits in the first control information correspond to uplink grant i+1, uplink grant i+2, uplink grant i+3 and uplink grant i+4 respectively, and K2 is equal to 4.

[0573] As an embodiment, the first uplink grant is uplink grant i+1, the dotted box F10.2 represents the first control information, the bits in the first control information correspond to uplink grant i+2, uplink grant i+3 and uplink grant i+4 respectively, and K2 is equal to 4.

[0574] As an embodiment, K2 depends on whether uplink grant i, uplink grant i+1, uplink grant i+2, uplink grant i+3 and uplink grant i+4 overlap with the first set of symbols; uplink grant i, uplink grant i+1, uplink grant i+2, uplink grant i+3 and uplink grant i+4 do not overlap with the first set of symbols.

[0575] As a sub-embodiment of this embodiment, if the uplink grant i+2 overlaps with the first symbol set, the first uplink grant is the uplink grant i, the dotted box F10.1 represents the first control information, the bits in the first control information correspond to the uplink grant i+1, the uplink grant i+3 and the uplink grant i+4 respectively, and the K2 is equal to 3.

[0576] As an embodiment, K2 does not depend on whether uplink grant i, uplink grant i+1, uplink grant i+2, uplink grant i+3 and uplink grant i+4 overlap with the first set of symbols.

[0577] As a sub-embodiment of this embodiment, if the uplink grant i+2 overlaps with the first symbol set, the first uplink grant is the uplink grant i, the dotted box F10.1 represents the first control information, the bits in the first control information correspond to the uplink grant i+1, the uplink grant i+2, the uplink grant i+3 and the uplink grant i+4 respectively, the K2 is equal to 4, and the bits corresponding to the uplink grant i+2 are reserved.

[0578] As a sub-embodiment of this embodiment, if the uplink grant i+2 overlaps with the first symbol set, the first uplink grant is the uplink grant i, the dotted box F10.1 represents the first control information, the bits in the first control information correspond to the uplink grant i+1, the uplink grant i+3, the uplink grant i+4 and the uplink grant i+5 respectively, and the K2 is equal to 4.

[0579] As an embodiment, this embodiment does not limit the implementation method of the first control information.

[0580] As an embodiment, this embodiment does not limit the number of bits occupied by the first control information.

[0581] As an embodiment, this embodiment does not limit the number of bits occupied by the bit map in the first control information.

[0582] As an embodiment, this embodiment does not limit the time-frequency position of the first control information in the first uplink grant.

[0583] As an embodiment, this embodiment does not limit whether the frequency domain resources occupied by the uplink grant configured by the first message are the same.

[0584] As an embodiment, this embodiment does not limit whether the lengths of the time domain resources occupied by the uplink grant configured by the first message are the same.

[0585] As an embodiment, this embodiment does not limit whether the time domain lengths between adjacent uplink grants configured by the first message are the same.

[0586] As an embodiment, this embodiment does not limit whether the five uplink grants belong to the same configuration period.

[0587] As an embodiment, this embodiment does not limit the number of uplink grants in each configuration period configured by the first message.

[0588] Embodiment 11

[0589] Embodiment 11 illustrates a schematic diagram of the time domain position of the uplink grants configured by the first message according to an embodiment of the present application, as shown in the attached figure. Fig.11 As shown in the attached Fig.11 In the figure, the horizontal axis represents time and the vertical axis represents frequency; each box filled with horizontal lines represents an uplink grant configured by the first message; uplink grant i, uplink grant i+1, uplink grant i+2, uplink grant i+3, uplink grant i+4, uplink grant i+5 and uplink grant i+6 are 7 adjacent uplink grants.

[0590] In embodiment 11, the K2 uplink grants depend on the time domain position of the uplink grant configured by the first message; the first control information is a bit map.

[0591] As an embodiment, the number of bits occupied by the first control information is fixed.

[0592] As an embodiment, the number of bits occupied by the first control information is statically configured.

[0593] As an embodiment, the number of bits occupied by the first control information is semi-statically configured.

[0594] As an embodiment, the dotted box F11.1 represents the first control information, and the bits in the first control information correspond to uplink grant i+1, uplink grant i+2, uplink grant i+5 and uplink grant i+6 respectively, and any bit in the first control information does not correspond to uplink grant i+3 and uplink grant i+4.

[0595] As an embodiment, the dotted box F11.2 represents the first control information, and the bits in the first control information correspond to uplink grant i+1, uplink grant i+2, uplink grant i+4 and uplink grant i+5 respectively, and any bit in the first control information does not correspond to uplink grant i+3.

[0596] As an embodiment, this embodiment does not limit the implementation method of the first control information.

[0597] As an embodiment, this embodiment does not limit the number of bits occupied by the first control information.

[0598] As an embodiment, this embodiment does not limit the number of bits occupied by the bit map in the first control information.

[0599] As an embodiment, this embodiment does not limit the time-frequency position of the first control information in the first uplink grant.

[0600] As an embodiment, this embodiment does not limit whether the frequency domain resources occupied by the uplink grant configured by the first message are the same.

[0601] As an embodiment, this embodiment does not limit whether the lengths of the time domain resources occupied by the uplink grant configured by the first message are the same.

[0602] As an embodiment, this embodiment does not limit whether the time domain lengths between adjacent uplink grants configured by the first message are the same.

[0603] As an embodiment, this embodiment does not limit whether the 7 uplink grants belong to the same configuration period.

[0604] As an embodiment, this embodiment does not limit the number of uplink grants in each configuration period configured by the first message.

[0605] Example 12

[0606] Embodiment 12 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig.12 As shown in the attached Fig.12 In the embodiment, the processing device 1200 in the first node includes a first receiver 1201 and a first transmitter 1202.

[0607] A first receiver 1201 receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; and receives a second message, wherein the second message indicates a first symbol set;

[0608] The first transmitter 1202 sends first control information in a first uplink grant, where the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant;

[0609] In Embodiment 12, the K2 uplink grants depend on at least the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0610] As an embodiment, the K2 uplink grants depend on a first time interval; the starting time of the first time interval is related to the time domain position of the first uplink grant, and the length of the first time interval is configurable.

[0611] As an embodiment, the first control information is a bit map, the number of bits occupied by the first control information is greater than K2, and at least one bit in the first control information is reserved.

[0612] As an embodiment, the K2 uplink grants depend on the number of bits occupied by the first control information; the first control information is a bit map.

[0613] As an embodiment, the K2 uplink grants are valid uplink grants; the valid uplink grants satisfy at least one of not overlapping with the first symbol set or belonging to the first time interval or being later than the first uplink grant in the time domain.

[0614] As an embodiment, the first receiver 1201 includes the attached Figure 4 Antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460 and data source 467.

[0615] As an embodiment, the first receiver 1201 includes the attached Figure 4Antenna 452, receiver 454, multi-antenna receive processor 458, and receive processor 456.

[0616] As an embodiment, the first receiver 1201 includes the attached Figure 4 Antenna 452, receiver 454, and receive processor 456.

[0617] As an embodiment, the first transmitter 1202 includes the attached Figure 4 Antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.

[0618] As an embodiment, the first transmitter 1202 includes the attached Figure 4 Antenna 452, transmitter 454, multi-antenna transmit processor 457, and transmit processor 468.

[0619] As an embodiment, the first transmitter 1202 includes the attached Figure 4 Antenna 452, transmitter 454, and transmit processor 468.

[0620] Example 13

[0621] Embodiment 13 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.13 As shown in the attached Fig.13 In the embodiment, the processing device 1300 in the second node includes a second transmitter 1301 and a second receiver 1302.

[0622] The second transmitter 1301 sends a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; and sends a second message, wherein the second message indicates a first symbol set;

[0623] The second receiver 1302 receives first control information, where the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant;

[0624] In Example 13, the recipient of the first message sends the first control information in a first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

[0625] As an embodiment, the K2 uplink grants depend on a first time interval; the starting time of the first time interval is related to the time domain position of the first uplink grant, and the length of the first time interval is configurable.

[0626] As an embodiment, the first control information is a bit map, the number of bits occupied by the first control information is greater than K2, and at least one bit in the first control information is reserved.

[0627] As an embodiment, the K2 uplink grants depend on the number of bits occupied by the first control information; the first control information is a bit map.

[0628] As an embodiment, the K2 uplink grants are valid uplink grants; the valid uplink grants satisfy at least one of not overlapping with the first symbol set or belonging to the first time interval or being later than the first uplink grant in the time domain.

[0629] As an embodiment, the second transmitter 1301 includes the attached Figure 4 Antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475, and memory 476.

[0630] As an embodiment, the second transmitter 1301 includes the attached Figure 4 Antenna 420, transmitter 418, multi-antenna transmit processor 471, and transmit processor 416.

[0631] As an embodiment, the second transmitter 1301 includes the attached Figure 4 Antenna 420, transmitter 418, and transmit processor 416.

[0632] As an embodiment, the second receiver 1302 includes the attached Figure 4 Antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476.

[0633] As an embodiment, the second receiver 1302 includes the attached Figure 4 Antenna 420, receiver 418, multi-antenna receive processor 472, receive processor 470.

[0634] As an embodiment, the second receiver 1302 includes the attached Figure 4 Antenna 420, receiver 418, and receive processor 470.

[0635] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point) and other wireless communication devices.

[0636] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; receiving a second message, the second message indicating a first set of symbols; A first transmitter sends first control information in a first uplink grant, wherein the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; The K2 uplink grants depend on at least the time domain position of the uplink grant configured by the first message or the position of the first symbol set; The K2 is a positive integer.

2. The first node according to claim 1, characterized in that: The K2 uplink grants depend on a first time interval; a starting moment of the first time interval is related to a time domain position of the first uplink grant, and a length of the first time interval is configurable.

3. The first node according to claim 1 or 2, characterized in that: The first control information is a bit map, the number of bits occupied by the first control information is greater than K2, and at least one bit in the first control information is reserved.

4. The first node according to any one of claims 1 to 3, characterized in that: The K2 uplink grants depend on the number of bits occupied by the first control information; the first control information is a bit map.

5. The first node according to any one of claims 1 to 4, characterized in that: The K2 uplink grants are valid uplink grants; the valid uplink grants satisfy at least one of not overlapping with the first symbol set, belonging to the first time interval, or being later than the first uplink grant in the time domain.

6. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; sending a second message, the second message indicating the first set of symbols; A second receiver receives first control information, wherein the first control information indicates whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants are configured by the first message, and the K2 uplink grants are after the first uplink grant; Among them, the recipient of the first message sends the first control information in a first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.

7. A method in a first node for wireless communication, characterized in that: include: receiving a first message, wherein the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; receiving a second message, the second message indicating a first set of symbols; Sending first control information in a first uplink grant, the first control information indicating whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants being configured by the first message, and the K2 uplink grants being after the first uplink grant; The K2 uplink grants depend on at least the time domain position of the uplink grant configured by the first message or the position of the first symbol set; The K2 is a positive integer.

8. A method in a second node for wireless communication, characterized in that: include: Sending a first message, where the first message configures an uplink grant, and any two uplink grants configured by the first message do not overlap in time; sending a second message, the second message indicating the first set of symbols; receiving first control information, the first control information indicating whether K2 uplink grants are not used, the first uplink grant and the K2 uplink grants being configured by the first message, the K2 uplink grants being after the first uplink grant; Among them, the recipient of the first message sends the first control information in a first uplink grant; the K2 uplink grants depend on at least the former of the time domain position of the uplink grant configured by the first message or the position of the first symbol set; and K2 is a positive integer.