Method and device for indicating unused transmission opportunity

Abstract

The embodiment of the invention provides a method and a device for indicating an unused transmission opportunity. The method comprises the following steps: a terminal device receives a configuration message sent by a network; and the MAC entity of the terminal equipment determines whether a configuration uplink grant in a multi-PUSCH CG (multi-PUSCH CG) of a multi-PUSCH is used or not according to the configuration message, and informs a lower layer of information about whether the configuration uplink grant is used or not. According to the embodiment of the invention, the problem of how to determine whether the TO in the multi-PUSCH CG is used or not by the terminal equipment is solved, so that a network side can effectively utilize scheduling resources. In addition, as no redundant signaling is introduced, the signaling overhead is reduced, the data burst characteristics of the XR service and the media service are supported, and the network capacity is improved.

Description

Method and device for indicating unused transmission opportunities Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] Support for Extended Reality (XR) services within 3GPP (3rd Generation Partnership Project) services and networks. XR services refer to all real-world and virtual environments and human-computer interactions enabled by computing technology and wearable devices. Application areas include, but are not limited to, entertainment, healthcare, and education. XR services can include virtual reality (VR), augmented reality (AR), and mixed reality (MR).

[0003] Virtual reality is a rendered version of a visual and audio scene that is presented to the viewer or user, designed to simulate the visual and auditory sensory stimulation of the real world as naturally as possible as the viewer or user moves within the limitations defined by the application. Augmented reality refers to the provision of additional information or artificially generated items or content overlaid on the user's current environment. Mixed reality is an advanced form of AR, in which some virtual elements are inserted into the physical scene to provide the illusion that these elements are part of the real scene.

[0004] A PDU Set consists of one or more Protocol Data Units (PDUs) that carry the payload of an information unit generated at the application layer, such as a frame or video slice for XR and media services. In some embodiments, the application layer requires all PDUs in a PDU Set to use the corresponding information unit. In other embodiments, when some PDUs are lost, the application layer can still recover all or part of the information unit.

[0005] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0006] Summary of the Invention

[0007] The inventors discovered that in order to use resources more rationally, the UE can report subsequent unused transmission occasions (UTOs) through UCI (uplink control information). This UCI indication is called UTO-UCI. Generally, the UE sends UTO-UCI information through the physical layer to inform the base station of the relevant information of the next unused TOs. However, the physical layer is unable to know which TOs will be used or unused next because the physical layer does not cache status information and thus cannot estimate the usage of TOs. Therefore, in uplink transmission, how to determine the usage of transmission occasions requires further standardization and technical implementation. Otherwise, UTO-UCI will not work correctly, resulting in possible waste of CG resources, thereby reducing transmission efficiency.

[0008] In response to at least one of the above problems or other similar problems, an embodiment of the present application provides a method and device for indicating unused transmission opportunities, which supports how to promptly notify the physical layer about UTO information by enhancing at least one of RRC-related configurations, MAC-related processes, and characteristics of data bursts based on XR services.

[0009] According to one aspect of an embodiment of the present application, there is provided an apparatus for indicating unused transmission opportunities, configured in a terminal device, the apparatus comprising:

[0010] a receiving unit configured to receive a configuration message from a network device;

[0011] A processing unit, which determines whether the configured uplink authorization in the CG of the multi-PUSCH (multi-PUSCH CG) is used according to the configuration message in the MAC entity of the terminal device, and notifies the lower layer of the information of whether the configured uplink authorization is used.

[0012] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, by performing uplink-related enhancements at the MAC layer, the terminal device determines the subsequent TO usage through the MAC entity to notify the lower layer (i.e., the physical layer), so that the physical layer can correctly generate and send UTO-UCI, so that the network side can perform further operations, such as allocating unused TO to other terminal devices, thereby improving network capacity. Thus, the problem of how the terminal device determines whether the TO in the multi-PUSCH CG is used is solved, so that the network side can effectively utilize scheduling resources. In addition, since no redundant signaling is introduced, the signaling overhead is reduced, the data burst characteristics of XR services and media services are supported, and network capacity is improved.

[0013] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0014] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0015] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0017] FIG1 is a schematic diagram of an example of UTO-UCI;

[0018] FIG2 is a schematic diagram of a method for indicating unused transmission opportunities according to an embodiment of the present application;

[0019] FIG3 is a schematic diagram of a CG period of multiple PUSCHs;

[0020] FIG4 is a schematic diagram of a device for indicating unused transmission opportunities according to an embodiment of the present application;

[0021] FIG5 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0022] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0023] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0024] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0025] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0026] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0027] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0028] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), IAB (Integrated Access and Backhaul) nodes, IAB-DUs, or IAB-donors. The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used. The terms "cell" and "base station" are interchangeable to avoid confusion.

[0029] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), an IAB-MT (Mobile Terminal), a station, and so on.

[0030] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, wearable devices, etc.

[0031] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measuring, such as but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0032] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station, one or more network devices as described above, or a device in the core network. The term "user side" or "terminal side" or "terminal device side" refers to the side of the user or terminal, which can be a UE, one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0033] Currently, 5G technology is researching key issues, solutions, and conclusions to support advanced media services, such as High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and tactile / multimodal communication services. The goals include:

[0034] 1. Enhancements to support multi-mode services, including:

[0035] - Investigate whether and how to enable applications to provide relevant tactile and multimodal data to users at similar times (e.g., audio, video, and tactile data associated with a specific time), focusing on the need for enhanced policy control (e.g., QoS policy coordination).

[0036] 2. Enhanced network exposure to support interaction between 5GS (5G system) and applications, including:

[0037] - Study whether and how to perform application synchronization and QoS (Quality of Service) policy coordination between multiple UEs or multiple QoS flows per UE, and how to interact between AF and 5GS.

[0038] - Study the exposure of 5GS QoS information (e.g., QoS capabilities) and network conditions to applications to enable fast codec / rate adaptation that helps deliver the desired QoE (e.g., helping alleviate 5GS congestion).

[0039] 3. Study whether and how to implement the following QoS and policy enhancements for XR service and media service transport, including:

[0040] -Study the traffic characteristics of media services that can improve network resource utilization and QoE (Quality of Experience).

[0041] - Enhance the QoS framework to support PDU Set granularity (e.g. video / audio frame / tile, application data unit, control information), where a PDU Set consists of PDUs with the same QoS requirements.

[0042] - Considering the different importance of PDU Sets, it supports differentiated QoS processing. For example, packets belonging to less important PDU Sets can be legally discarded to reduce resource waste.

[0043] - Whether and how to support uplink-downlink transmission coordination to meet the RTT (Round Trip Time) delay requirement between the UE and the N6 termination point of the UPF (User Plane Function).

[0044] - Potential policy enhancements to minimize jitter, focusing on demand provisioning from AF (Application Function) and extensions of PCC (policy and charging control) rules.

[0045] To support the data burst characteristics of XR services and better pre-configure resources, enhancements have been made to the uplink scheduling method of configured grants (CG). A CG cycle can contain multiple (multi-)PUSCH (Physical Uplink Shared CHannel) transmission occasions (occasions), that is, the CG configuration contains multiple consecutive configured uplink grants (configured uplink grants) within a cycle. Configured uplink grants can also be called configured grant occasions (CGOs), transmission occasions (TOs), PUSCH (Physical Uplink Shared Channal) transmissions, PUSCH occasions, PUSCH transmission occasions, etc.

[0046] Since the CG of multiple PUSCHs is pre-configured, considering the characteristics of data bursts, more periodic uplink resources may be configured so that large data bursts can be scheduled in time when they arrive to reduce latency. However, this may sometimes cause a certain amount of resource waste. For example, some periodic data traffic is relatively small, resulting in pre-configured resources not being used. In order to use resources more reasonably, the UE can report subsequent unused transmission occasions (UTO) through UCI (uplink control information). This UCI indication is called UTO-UCI. Unused means that it will not be used, will not be used, or will not be used. Used means that it will be used, will be used, and will not be unused (not unused).

[0047] The UE can multiplex a UTO-UCI represented by an N-bit bitmap in each CG-PUSCH transmission. The N bits in the UTO-UCI map the subsequent N CG-PUSCH transmission opportunities in ascending order of start time one-to-one from low to high. A bit value of 0 indicates that the UE may transmit CG-PUSCH at the corresponding CG-PUSCH transmission opportunity, and a bit value of 1 indicates that the UE will not transmit CG-PUSCH at the corresponding CG-PUSCH transmission opportunity. Figure 1 shows an example of using a 3-bit UTO-UCI indication in each CG-PUSCH transmission. In Figure 1, 4 TOs are configured for each CG period. The TOs with background color in Figure 1 indicate used (also called not unused) TOs, and the TOs without background color indicate unused TOs. The UTO-UCI bitmap is customarily with the high bit on the left and the low bit on the right.

[0048] The inventors discovered that the UE sends UTO-UCI information through the physical layer to inform the base station of information about unused TOs. However, the physical layer is unable to know which TOs will be used or unused next because it does not cache status information, making it unable to estimate TO usage. Therefore, in uplink transmission, determining the usage of transmission opportunities requires further standardization and technical implementation. Otherwise, UTO-UCI will not function correctly, potentially wasting CG resources and reducing transmission efficiency.

[0049] To address at least one of the above-mentioned issues or other similar issues, embodiments of the present application provide a method and apparatus for indicating unused transmission opportunities. The embodiments of the present application are described below with reference to the accompanying drawings and specific implementations. In the following description, "if..." can be replaced with "under..." or "when..." to avoid confusion.

[0050] Embodiments of the first aspect

[0051] An embodiment of the present application provides a method for indicating unused transmission opportunities, which is described from the side of a terminal device.

[0052] FIG2 is a schematic diagram of a method for indicating unused transmission opportunities according to an embodiment of the present application. As shown in FIG2 , the method includes:

[0053] 210: The terminal device receives a configuration message from the network device;

[0054] 220: The MAC entity of the terminal device determines whether the configured uplink authorization in the multi-PUSCH CG (multi-PUSCH CG) is used according to the configuration message, and notifies the lower layer of the information of whether the configured uplink authorization is used.

[0055] It is worth noting that FIG2 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG2 above.

[0056] According to the above embodiment, the terminal device determines the subsequent TO usage through the MAC entity to notify the lower layer (i.e., the physical layer), so that the physical layer can correctly generate and send the UTO-UCI, so that the network side can perform further operations, such as allocating unused TO to other terminal devices, thereby improving network capacity.

[0057] In some embodiments, the above-mentioned configuration message is a first configuration message, such as an RRCReconfiguration message, including a first information unit, such as a ConfiguredGrantConfig IE, and the first information unit includes a first field, such as numberOfPUSCH-PerPeriod, or nrofSlots_InCGperiod, cg-nrofSlotsPerPeriod, cg-nrofPUSCH-PerPeriod, etc. The first field provides the number of consecutive time slots allocated in a CG period of multiple PUSCHs.

[0058] In the above embodiment, by enhancing the ConfiguredGrantConfig IE in the RRCReconfiguration message and adding the above first field to provide the number of consecutive time slots allocated in a multi-PUSCH CG period, the relevant configuration of the UTO-UCI of the multi-PUSCH CG can be supported.

[0059] In the above embodiment, the first field may be of integer type, and its value range may be from 2 to 16 or from 2 to 32, but the present application is not limited thereto.

[0060] In some embodiments, if the above-mentioned first field is configured, the terminal device ignores the cg-nrofSlot and cg-nrofPUSCH-InSlot configurations. Since cg-nrofSlot is the number of time slots allocated in the CG period, and cg-nrofPUSCH-InSlot is the number of consecutive PUSCHs in a time slot in the CG, these parameters are applicable to traditional CGs and not to CGs with multiple PUSCHs. Therefore, when the first field is configured, the terminal device ignores the above two parameters, ensuring the correctness of the configuration and preventing conflicts with existing configuration parameters.

[0061] In some embodiments, if the first field is configured, the fields in the sub-information element rrc-ConfiguredUplinkGrant in the first information element, such as timeDomainAllocation, timeDomainOffset, timeReferenceSFN, etc., are used to determine the time-frequency resource configuration of the first configured uplink grant in the CG period of the multi-PUSCH. This allows the reuse of existing configurations and saves signaling overhead.

[0062] In the above embodiment, the time domain position (symbol) of the subsequent i-th configured uplink grant in the CG period of the above multi-PUSCH is i time slots larger than the time domain position of the above first configured uplink grant. As a result, only one configured uplink grant needs to be configured, and the UE can calculate the time domain resource scheduling information of the other configured uplink grants by itself, thereby reducing signaling overhead.

[0063] In the above embodiment, the first information unit may further include a second field, for example, called nrof_UTO_UCI, which is used to indicate the number of bits of UTO-UCI reported for the subsequent CG-PUSCH TO (that is, the TO of PUSCH in the CG, referred to as TO for short), corresponding to the N introduced above.

[0064] In the above embodiment, the second field may be an integer, and its value range may be from 3 to 8, but the present application is not limited thereto.

[0065] In the previous embodiment, the first field and the second field are located in the ConfiguredGrantConfig IE as an example, but the present application is not limited to this. The first field and the second field may also be located in a newly added IE of the RRCReconfiguration message, such as an IE specifically defined for the CG of multiple PUSCHs, etc., or located in an existing or newly added IE of other configuration messages, but the present application is not limited to this.

[0066] In some embodiments, since the physical layer needs to multiplex the UTO-UCI in each transmitted CG-PUSCH, the MAC entity of the terminal device can determine the relevant information of whether the subsequent TO of the configured uplink authorization is used before the start time of a current configured uplink authorization, for example, before the first symbol time of the configured uplink authorization, and notify the lower layer of the relevant information of whether the subsequent TO is used.

[0067] In the above embodiment, the MAC entity of the terminal device can make the above notification when instructing the physical layer to generate a transmission based on the stored uplink authorization, or make the above notification when obtaining the MAC PDU from the multiplexing and assembly entity to send, or make the above notification when delivering the configured uplink authorization and associated HARQ message to the HARQ entity, or make the above notification after the logical channel priority process is completed, etc.

[0068] In the above embodiment, when the MAC entity notifies the lower layer of relevant information on whether the subsequent TO is used, the MAC entity can also notify the lower layer of time reference information, which indicates the starting time of the relevant information on whether the subsequent TO is used, that is, the time reference information indicates the starting time of the notified information on whether the subsequent TO is used or not.

[0069] In the above embodiment, the time reference information may be a specific time, for example, represented by a frame number, a subframe number, a time slot, a symbol, etc. The present application is not limited thereto. The time reference information may also be the number of TOs starting from in the CG period of the current multi-PUSCH, or the number of configured uplink authorizations after the current configured uplink authorization, and so on.

[0070] In the above embodiment, the following methods can be used to determine whether the TO subsequently authorized by the configuration is used (ie, the subsequent use or status of the TO), which are described below.

[0071] In some implementations, the MAC entity of the terminal device determines the usage of the next N TOs based on the current cache status and notifies the lower layer of the usage of the N TOs. Here, N refers to the value of the second field.

[0072] For example, the terminal device calculates the number of TOs required to complete the data transmission in the cache based on the cache status of one or more logical channels that can be mapped to the CG of multiple PUSCHs and the transport block size (TBS) corresponding to the TO in the CG of multiple PUSCHs, that is, how many TOs will be needed in the future to complete the data transmission in the cache; then, based on the calculated number, the usage status of the above-mentioned N TOs is determined and the usage of the N TOs is notified to the lower layer.

[0073] In the above example, the multi-PUSCH CG is the multi-PUSCH CG that includes the currently configured uplink grant; the above buffer status refers to the sum of the buffer sizes of the above one or more logical channels. The buffer size of each logical channel is equal to the sum of the corresponding PDCP layer data volume and the RLC layer data volume.

[0074] In the above example, the MAC entity of the terminal device can determine the usage of the future N TOs and inform the lower layer each time it generates a MAC PDU.

[0075] In the above example, one or more logical channels that can be mapped to the CG of multiple PUSCHs meet the following conditions:

[0076] If the CG of the multi-PUSCH is configured as type 1, the logical channel needs to be configured as configuredGrandType1Allowed;

[0077] If a logical channel is configured with allowedCG-List, the allowedCG-List needs to include the ConfiguredGrantConfigIndexMAC value configured by the CG of the multiple PUSCHs.

[0078] In this way, the amount of cached data of the logical channel belonging to the CG can be correctly calculated, thereby correctly predicting the usage of subsequent TO.

[0079] In the above example, when the MAC entity of the terminal device notifies the lower layer of relevant information on whether the subsequent TO is used, it can also follow the following principle, namely: if a TO (that is, a CG PUSCH opportunity) is indicated as "unused" in the previous notification, then it cannot be indicated as "used" in the subsequent notification.

[0080] That is, for the same TO, if it is previously predicted that it will not be used, even if it is later predicted that the TO can be used due to the arrival of new data, the lower layer can only be notified that the TO is not used, that is, the terminal device can only give up using the TO. Unless otherwise specified, the above principles apply to other methods in the embodiments of this application.

[0081] According to the above implementation, it can be considered that the MAC entity of the terminal device generates the UTO bitmap and notifies the physical layer, and the physical layer generates the UTO-UCI completely according to the instructions of the MAC layer. This application does not limit the specific content of the MAC entity's notification to the lower layer. It can be a bitmap, or it can also be a notification of which TOs are unused, or which TOs are used, etc.

[0082] In other embodiments, the MAC entity of the terminal device determines the usage of all TOs of the CG cycle of the multi-PUSCH before the first used TO of the CG cycle of the multi-PUSCH, for example, before the start of the CG cycle of the multi-PUSCH, that is, before the start time of the first TO of the CG cycle of the multi-PUSCH, and notifies the lower layer of the usage.

[0083] For example, the MAC entity of the terminal device calculates the number of TOs required to complete the data transmission in the cache based on the current cache status; then, based on the calculated number, it determines the usage of all TOs of the CG period of the multi-PUSCH and notifies the lower layer of the usage.

[0084] FIG3 is a schematic diagram of a multi-PUSCH CG period. As shown in FIG3 , the multi-PUSCH CG period (also referred to as the CG period) is typically configured as a period for data bursts. Uplink data bursts often arrive at the user equipment cache at the same time or at a similar time. For example, at the beginning of the CG period, the data burst has already arrived at the Layer 2 cache. Therefore, the MAC entity of the terminal device can calculate the number of TOs required for the data in this CG period based on the cache status at this time. The calculation method refers to the aforementioned embodiment.

[0085] In the above embodiment, the usage of all TOs in the CG cycle may be the number of TOs that still need to be used, but the present application is not limited thereto.

[0086] In the above embodiment, the MAC entity of the terminal device can inform the lower layer of the usage when generating the first transmission data configured with uplink authorization, for example, informing the lower layer of the number of TOs required for the data burst. The present application is not limited to this, and the MAC entity of the terminal device can also inform the lower layer of the usage at other times.

[0087] In the above implementation, the physical layer of the terminal device can generate the corresponding UTO-UCI for each PUSCH transmission based on the indication received once per multi-PUSCH CG period and send it to the network side. This allows the network side to perform further operations, such as allocating unused TO to other terminal devices, thereby improving network capacity.

[0088] In some further embodiments, the MAC entity of the terminal device notifies the lower layer of an unused TO before the start time of an unused TO of the CG of multiple PUSCHs.

[0089] In the above implementation, since the status of unused TOs cannot be changed, notification to lower layers is done as late as possible. However, the physical layer needs to send the UTO-UCI information to the network in advance to allow the network sufficient processing time to schedule the TO for other terminal devices. Therefore, in this implementation, a time threshold T can also be set, which can be in milliseconds, number of time slots, number of TOs, etc.

[0090] In the above embodiment, before the time threshold T before the start time of the unused TO, if the MAC entity of the terminal device predicts that the TO is unused, it notifies the lower layer that the TO will not be used.

[0091] For example, assuming the time threshold is T milliseconds, if the MAC entity predicts that a TO is unused T milliseconds before the start time of a TO, it notifies the lower layer that the TO will not be used. This notification method is similar to a sliding window, always notifying the TO usage status at time t+T at time t.

[0092] In the above embodiment, the time threshold T may be configured by RRC signaling, indicating that the MAC layer needs to notify the physical layer of the minimum time advance of unused TO, or may be specified by the protocol, such as T=4 milliseconds.

[0093] In the above embodiment, the physical layer of the terminal device considers a TO to be used before receiving an indication from the MAC entity that the TO is not used. That is, if the physical layer does not receive an indication from the MAC entity about the UTO, it assumes that the next N TOs are all used.

[0094] In the above implementation, the physical layer may generate the UTO-UCI according to the default situation and the instruction of the MAC layer.

[0095] In some further embodiments, when a data burst ends in a certain logical channel, the MAC entity of the terminal device determines relevant information of unused TOs and notifies the lower layer of relevant information of the unused TOs.

[0096] In the above embodiment, when the end of the data burst (EoDB, i.e., the last PDU in the data burst) arrives at the cache queue of the above logical channel, and the CG of the multi-PUSCH only contains the above logical channel, the MAC entity of the terminal device believes that the current data burst has arrived at the cache, and it determines the usage of subsequent TO in the CG period of the current multi-PUSCH according to the current cache status. For example, the usage of subsequent TO in the CG period of the current multi-PUSCH can be determined according to the method of the above embodiment, which is omitted here.

[0097] In some further embodiments, when the cache of one or more logical channels of the CG that can be mapped to multiple PUSCHs is cleared, the MAC entity of the terminal device determines the relevant information of the unused TO and notifies the lower layer of the relevant information of the unused TO.

[0098] For example, after the cache of one or more logical channels is cleared or after waiting for a period of time after the cache is cleared, when the MAC entity of the terminal device confirms that there is no data to be sent in the CG period of the current multi-PUSCH, it notifies the lower layer that all subsequent TOs in the CG period of the current multi-PUSCH are unused TOs.

[0099] In some further embodiments, the MAC entity of the terminal device determines the usage of TO within the CG of multiple PUSCHs based on traffic patterns and / or historical information and / or statistical information, and notifies the lower layers of the usage. That is, the usage of TO within the CG of multiple PUSCHs is determined based on the implementation of the terminal device.

[0100] In the above implementation, similar to the information generation method when the terminal device reports UE assistance information (UE Assistance Information) about XR uplink traffic, the UE can predict future traffic based on traffic patterns, historical information, measurement information, statistical information, etc., thereby obtaining the TO situation to be used and notifying the lower layer.

[0101] In the above embodiment, the physical layer of the terminal device can generate the UTO-UCI based on the relevant information received from the upper layer on whether the TO is used, and send it to the network device together with the next PUSCH transmission.

[0102] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0103] In this embodiment of the present application, to maintain the integrity of a PDU Set, the UE may discard data based on the PDU Set. When the UE discards a PDU Set, the PDCP layer discards all PDUs in the PDU Set. This significantly changes the UE's Layer 2 buffer, potentially affecting the use of the TO, such as causing subsequent TOs to become unused.

[0104] In response to the above problems, the embodiments of the present application further provide solutions.

[0105] In some embodiments, when the PDCP entity of the terminal device discards a PDU set, it triggers the MAC entity to determine unused TOs, that is, to update the usage of TOs and notify the lower layer of relevant information of the unused TOs, thereby solving the above problem.

[0106] In the above embodiment, when the PDCP entity of the terminal device discards a PDU set, it can also notify the MAC entity of the amount of discarded data; thus, the MAC entity can determine the unused TO based on the amount of discarded data, that is, predict the UTO information.

[0107] In the embodiment of the present application, in the process of transmitting and receiving data without dynamic scheduling, the uplink configuration can be further enhanced, for example, when the MAC entity configures the uplink.

[0108] In some embodiments, for a configuration uplink grant in a multi-PUSCH CG, if the TO corresponding to the configuration uplink grant is indicated to the lower layer as unused TO, the MAC entity of the terminal device releases or skips the configuration uplink grant. In this way, the terminal device maintains the consistency of information indication and transmission behavior, ensuring the correctness of the uplink configuration grant.

[0109] In some other embodiments, for TDD (non-paired spectrum operation), the MAC entity of the terminal device does not indicate to the lower layer the information related to the invalid unused TO configured for uplink authorization.

[0110] In the above embodiment, an invalid configured uplink grant means that the timeslot in which the configured uplink grant is located is a downlink timeslot, so the corresponding TO is invalid for uplink scheduling. Therefore, in the various methods for determining whether the TO subsequent to the configured uplink grant is used, the invalid TO is directly skipped when indicating the subsequent TO. For example, if the MAC entity determines that two subsequent TOs are unused, and the second subsequent TO is an invalid TO, it indicates that the first and third subsequent TOs are unused.

[0111] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0112] The method according to the embodiment of the present application solves the problem of how the UE determines whether the TO in the multi-PUSCH CG is used, allowing the network side to effectively utilize scheduling resources. No redundant signaling is introduced, signaling overhead is reduced, the data burst characteristics of XR services and media services are supported, and network capacity is improved.

[0113] Embodiments of the second aspect

[0114] An embodiment of the present application provides a device for indicating unused transmission opportunities. The device may be, for example, a terminal device, or one or more components or assemblies configured on the terminal device. The device of the embodiment of the present application corresponds to the method of the embodiment of the first aspect, and the contents that are the same as those of the embodiment of the first aspect are not repeated here.

[0115] FIG4 is a schematic diagram of an unused transmission opportunity indication device according to an embodiment of the present application. As shown in FIG4 , the unused transmission opportunity indication device 400 according to the embodiment of the present application includes:

[0116] A receiving unit 410, which receives a configuration message from a network device;

[0117] The processing unit 420 determines whether the configured uplink authorization in the multi-PUSCH CG (multi-PUSCH CG) is used according to the configuration message through the MAC entity of the terminal device, and notifies the lower layer of the information of whether the configured uplink authorization is used.

[0118] In some embodiments, the configuration message is a first configuration message comprising a first information unit comprising a first field providing the number of consecutive time slots allocated within a CG period of a multi-PUSCH.

[0119] In the above embodiment, the first configuration message may be an RRCReconfiguration message.

[0120] In the above embodiment, the first information unit may be a ConfiguredGrantConfig IE.

[0121] In the above embodiment, if the first field is configured, the terminal device can ignore the cg-nrofSlot and cg-nrofPUSCH-InSlot configurations.

[0122] In the above embodiment, if the first field is configured, the fields in the sub-information unit rrc-ConfiguredUplinkGrant in the first information unit are all used to determine the time-frequency resource configuration of the first configured uplink grant in the CG period of multiple PUSCHs.

[0123] In the above embodiment, the time domain position of the subsequent i-th configuration of uplink authorization in the CG period of multiple PUSCHs can add i time slots to the time domain position of the first configuration of uplink authorization.

[0124] In the above embodiment, the first information unit may further include a second field, where the second field is used to indicate the number of bits used to report the UTO-UCI for the subsequent CG-PUSCH TO.

[0125] In some embodiments, the processing unit 420 determines the relevant information of whether the subsequent TO of the configured uplink authorization is used before the start time of the current configured uplink authorization through the MAC entity of the terminal device, and notifies the lower layer of the relevant information of whether the subsequent TO is used.

[0126] In the above embodiment, the processing unit 420 may also notify the lower layer of time reference information through the MAC entity of the terminal device, where the time reference information indicates the starting time of the relevant information on whether the subsequent TO is used.

[0127] In the above embodiment, the processing unit 420 may determine the usage of the subsequent N TOs according to the current cache status through the MAC entity of the terminal device and notify the lower layer of the usage of the N TOs.

[0128] For example, the processing unit 420 calculates the number of TOs required to complete the data transmission in the cache based on the cache status of one or more logical channels that can be mapped to the CG of the multi-PUSCH and the transmission block size corresponding to the TO in the CG of the multi-PUSCH; determines the usage of the N TOs based on the calculated number of TOs and notifies the lower layer of the usage of the N TOs.

[0129] In the above example, one or more logical channels that can be mapped to the CG of the multiple PUSCHs meet the following conditions:

[0130] If the CG of multiple PUSCHs is configured as type 1, the logical channel is configured as configuredGrandType1Allowed;

[0131] If a logical channel is configured with allowedCG-List, the allowedCG-List contains the ConfiguredGrantConfigIndexMAC value configured by the CG of multiple PUSCHs.

[0132] In the above example and other examples, if a TO is indicated as "unused" in a previous notification, it cannot be indicated as "used" in a subsequent notification.

[0133] In the above embodiment, the processing unit 420 may also determine the usage of all TOs of a multi-PUSCH CG period before the first used TO of a multi-PUSCH CG period through the MAC entity of the terminal device, and notify the lower layer of the usage.

[0134] For example, the processing unit 420 calculates the number of TOs required to complete the data transmission in the cache based on the current cache status; determines the usage of all TOs of the CG period of the above-mentioned multi-PUSCH based on the calculated number of TOs, and notifies the lower layer of the usage.

[0135] In the above example, the processing unit 420 can generate a corresponding UTO-UCI each time a PUSCH is transmitted based on an indication received once in each CG period of multiple PUSCHs through the physical layer of the terminal device.

[0136] In the above embodiment, the processing unit 420 may also notify the lower layer of the unused TO before the start time of a certain unused TO of the CG of the multiple PUSCHs through the MAC entity of the terminal device.

[0137] For example, before a time threshold T before the start time of an unused TO, if the MAC entity predicts that the TO is unused, it notifies the lower layer that the TO will not be used.

[0138] In the above example, the time threshold T may be configured by RRC signaling, and the time threshold T indicates the minimum timing advance that the MAC layer needs to notify the physical layer of unused TO.

[0139] In the above example, the processing unit 420 may consider a TO to be used before receiving an indication from the MAC entity that the TO is not used through the physical layer of the terminal device.

[0140] In the above embodiment, when a data burst ends in a certain logical channel, the processing unit 420 may also determine the relevant information of the unused TO through the MAC entity of the terminal device, and notify the lower layer of the relevant information of the unused TO.

[0141] For example, when the data burst ends and arrives at the cache of the above-mentioned logical channel, and the CG of the multi-PUSCH only contains this logical channel, the processing unit 420 determines the usage of subsequent TO in a multi-PUSCH CG period based on the current cache status through the MAC entity of the terminal device.

[0142] In the above embodiment, when the cache of one or more logical channels of the CG that can be mapped to the multiple PUSCHs is cleared, the processing unit 420 can also determine the relevant information of the unused TO through the MAC entity of the terminal device and notify the lower layer of the relevant information of the unused TO.

[0143] In the above example, when the MAC entity confirms that there is no data to be sent in the CG period of the current multi-PUSCH, the processing unit 420 notifies the lower layer that all subsequent TOs in the CG period of the current multi-PUSCH are unused TOs.

[0144] In the above embodiment, the processing unit 420 can also determine the usage of TO within the CG of multiple PUSCHs based on the traffic pattern and / or historical information and / or statistical information through the MAC entity of the terminal device, and notify the lower layer of the usage of the TO.

[0145] In the above example, the processing unit 420 can generate UTO-UCI through the physical layer of the terminal device based on the relevant information received from the upper layer on whether TO is used, and send it to the network device together with the next PUSCH transmission.

[0146] In some embodiments, the processing unit 420 triggers the MAC entity to determine unused TOs when the PDCP entity of the terminal device discards the PDU set, and notifies the lower layer of relevant information of the unused TOs.

[0147] In the above embodiment, the processing unit 420 may notify the MAC entity of the amount of discarded data when discarding a PDU set through the PDCP entity of the terminal device; the MAC entity determines the unused TO based on the amount of discarded data.

[0148] In some embodiments, for a configured uplink grant in a multi-PUSCH CG, if the TO corresponding to the configured uplink grant is indicated to the lower layer as an unused TO, the processing unit 420 releases or skips the configured uplink grant through the MAC entity of the terminal device.

[0149] In the above embodiment, for TDD, the processing unit 420 does not indicate to the lower layer, through the MAC entity of the terminal device, the relevant information of the invalid unused TO configured for uplink authorization.

[0150] It is worth noting that the above description only describes the components or modules related to the present application, but the present application is not limited thereto. The apparatus 400 of the embodiment of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art. In addition, the above components or modules may be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of the present application is not limited thereto.

[0151] The apparatus according to the embodiments of the present application solves the problem of how the UE determines whether the TO in the multi-PUSCH CG is used, allowing the network side to effectively utilize scheduling resources. No redundant signaling is introduced, signaling overhead is reduced, the data burst characteristics of XR services and media services are supported, and network capacity is improved.

[0152] Embodiments of the third aspect

[0153] An embodiment of the present application also provides a communication system, including a network device and a terminal device.

[0154] In an embodiment of the present application, a terminal device includes the apparatus described in the embodiment of the second aspect, and is configured to execute the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.

[0155] In the embodiments of the present application, the network device sends a configuration message to the terminal device, such as the first configuration message described above. Furthermore, the network device may also receive information from the terminal device, such as the aforementioned UCI, PUSCH, and so on. Since the behavior of the network device has been described in the previous embodiments, its content is incorporated here and is omitted here.

[0156] In the above embodiments, the network device can also perform conventional operations of the network device, and the network device can also perform operations corresponding to the operations of the terminal device, such as the network device receiving information / signals from the terminal device, and / or the network device sending information / signals to the terminal device, which are omitted here.

[0157] An embodiment of the present application further provides a terminal device, which may be, for example, a UE, but the present application is not limited thereto and may also be other terminal devices.

[0158] Figure 5 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 5 , terminal device 500 may include a processor 501 and a memory 502. Memory 502 stores data and programs and is coupled to processor 501. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0159] In some embodiments, the functions of the device 400 of the embodiment of the second aspect can be integrated into the processor 501, wherein the processor 501 can be configured to execute a program to implement the method described in the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0160] In other embodiments, the device 400 of the embodiment of the second aspect can be configured separately from the processor 501. For example, the device 400 of the embodiment of the second aspect can be configured as a chip connected to the processor 501, and the functions of the device 400 of the embodiment of the second aspect can be realized through the control of the processor 501.

[0161] As shown in Figure 5 , the terminal device 500 may further include: a communication module 503, an input unit 504, a display 505, and a power supply 506. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 500 does not necessarily include all of the components shown in Figure 5 , and these components are not essential. Furthermore, the terminal device 500 may also include components not shown in Figure 5 , for which reference may be made to related art.

[0162] An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0163] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0164] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0165] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0166] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0167] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0168] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0169] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0170] 1. A method for indicating unused transmission opportunities, wherein the method comprises:

[0171] The terminal device receives the configuration message from the network device;

[0172] The MAC entity of the terminal device determines whether the configured uplink authorization in the multi-PUSCH CG (multi-PUSCH CG) is used according to the configuration message, and notifies the lower layer of information on whether the configured uplink authorization is used.

[0173] 2. The method according to Supplement 1, wherein:

[0174] The MAC entity of the terminal device determines relevant information on whether a subsequent TO of the configured uplink authorization is used before a current start time of the configured uplink authorization, and notifies the lower layer of relevant information on whether the subsequent TO is used.

[0175] 3. The method according to Supplementary Note 2, wherein:

[0176] The MAC entity of the terminal device also notifies the lower layer of time reference information, where the time reference information indicates the starting time of the relevant information of whether the subsequent TO is used.

[0177] 4. The method according to Supplementary Note 2, wherein:

[0178] The MAC entity of the terminal device calculates the number of TOs required to complete the data transmission in the cache according to the current cache status;

[0179] The terminal device determines the usage of all TOs of the CG period of the multi-PUSCH based on the calculated number of TOs, and notifies the lower layer of the usage.

[0180] 5. The method according to Supplementary Note 2, wherein:

[0181] The physical layer of the terminal device generates a corresponding UTO-UCI each time a PUSCH is transmitted based on an indication received once in the CG period of each of the multiple PUSCHs.

[0182] 6. The method according to Supplement 2, wherein:

[0183] Before a time threshold T before the start time of the unused TO, if the MAC entity predicts that the TO is unused, it notifies the lower layer that the TO will not be used.

[0184] 7. The method according to Supplementary Note 6, wherein:

[0185] The time threshold T is configured by RRC signaling, and the time threshold T indicates the minimum time advance that the MAC layer needs to notify the physical layer of unused TO.

[0186] 8. The method according to Supplementary Note 2, wherein:

[0187] The physical layer of the terminal device considers a TO to be used before receiving an indication from the MAC entity that the TO is not used.

[0188] 9. The method according to Supplement 2, wherein:

[0189] When a data burst ends in a certain logical channel, the MAC entity of the terminal device determines relevant information of unused TOs and notifies the lower layer of relevant information of the unused TOs.

[0190] 10. The method according to Supplementary Note 2, wherein:

[0191] When the cache of one or more logical channels that can be mapped to the CG of the multiple PUSCHs is cleared, the MAC entity of the terminal device determines the relevant information of the unused TOs and notifies the lower layer of the relevant information of the unused TOs.

Claims

1. A device for indicating unused transmission opportunities, configured in a terminal device, wherein: The device comprises: A receiving unit, which receives a configuration message from a network device; A processing unit, which determines whether the configured uplink authorization in the CG of multiple PUSCHs is used according to the configuration message through the MAC entity of the terminal device, and notifies the lower layer of the information of whether the configured uplink authorization is used.

2. The device according to claim 1, wherein: The configuration message is a first configuration message, including a first information unit, the first information unit including a first field, and the first field provides the number of consecutive time slots allocated in a CG period of multiple PUSCHs.

3. The device according to claim 2, wherein: The first information unit is ConfiguredGrantConfig IE.

4. The device according to claim 2, wherein: If the first field is configured, the processing unit ignores the cg-nrofSlot and cg-nrofPUSCH-InSlot configurations.

5. The device according to claim 2, wherein: If the first field is configured, the fields in the sub-information unit rrc-ConfiguredUplinkGrant in the first information unit are used to determine the time-frequency resource configuration of the first configured uplink grant in the CG period of multiple PUSCHs.

6. The device according to claim 5, wherein: The time domain position of the subsequent i-th configured uplink authorization in the CG period of the multiple PUSCHs is increased by i time slots on the time domain position of the first configured uplink authorization.

7. The device according to claim 2, wherein: The first information unit includes a second field, and the second field is used to indicate the number of bits of UTO-UCI reported for the subsequent CG-PUSCH TO.

8. The device according to claim 1, wherein: The processing unit determines, through the MAC entity of the terminal device, relevant information on whether a subsequent TO of the configured uplink authorization is used before a current start time of the configured uplink authorization, and notifies a lower layer of relevant information on whether the subsequent TO is used.

9. The device according to claim 8, wherein: The processing unit determines the usage of subsequent N TOs according to the current cache status through the MAC entity of the terminal device and notifies the usage of the N TOs to the lower layer.

10. The device according to claim 9, wherein: The processing unit calculates the number of TOs required to complete data transmission in the cache according to the cache status of one or more logical channels that can be mapped to the CG of the multiple PUSCHs and the transport block size corresponding to the TO in the CG of the multiple PUSCHs; The processing unit determines the usage of the N TOs according to the calculated number of the TOs and notifies the lower layer of the usage of the N TOs.

11. The device according to claim 10, wherein: One or more logical channels that can be mapped to the CG of the multiple PUSCHs meet the following conditions: If the CG of the multiple PUSCHs is configured as type 1, the logical channel is configured as configuredGrandType1Allowed; If a logical channel is configured with allowedCG-List, the allowedCG-List contains the ConfiguredGrantConfigIndexMAC value configured by the CG of the multiple PUSCHs.

12. The device according to claim 9, wherein: If a TO is indicated as "unused" in a previous notification, it cannot be indicated as "used" in a subsequent notification.

13. The device according to claim 8, wherein: The processing unit determines the usage of all TOs of a CG period of multiple PUSCHs before the first used TO of a CG period of multiple PUSCHs through the MAC entity of the terminal device, and notifies the lower layer of the usage.

14. The device according to claim 8, wherein: The processing unit notifies the lower layer of the unused TO through the MAC entity of the terminal device before a certain unused TO start time of the CG of the multiple PUSCHs.

15. The device according to claim 8, wherein: The processing unit generates UTO-UCI through the physical layer of the terminal device according to the relevant information received from the upper layer on whether the TO is used, and sends it to the network device together with the next transmission of PUSCH.

16. The device according to claim 1, wherein The device also includes: The processing unit triggers the MAC entity to determine the unused TOs when the PDCP entity of the terminal device discards the PDU set, and notifies the lower layer of the relevant information of the unused TOs.

17. The device according to claim 1, wherein: For a configured uplink grant in a CG of multiple PUSCHs, if the TO corresponding to the configured uplink grant is indicated to the lower layer as an unused TO, the processing unit releases or skips the configured uplink grant through the MAC entity of the terminal device.

18. The device according to claim 1, wherein: For TDD, the processing unit does not indicate to the lower layer, through the MAC entity of the terminal device, relevant information of the unused TO of the invalid configuration uplink authorization.

19. A terminal device, characterized in that: The terminal device includes a memory and a processor, the memory stores a computer program, and the processor is configured to execute the computer program to implement the following method: Receive configuration messages from network devices; The MAC entity determines whether the configured uplink authorization in the CG of multiple PUSCHs is used based on the configuration message, and notifies the lower layer of information on whether the configured uplink authorization is used.

20. A communication system, characterized in that: The communication system includes a network device and the terminal device described in claim 19.

Images