Method and apparatus for transmitting uplink data, method and apparatus for receiving uplink data, and communication system

Abstract

The present application provides a method and apparatus for transmitting uplink data, a method and apparatus for receiving uplink data, and a communication system. The method for transmitting uplink data comprises: for a configured uplink grant configured with information related to uplink control information (UCI) which provides first information, determining that the configured uplink grant is available for use or determining whether the configured uplink grant is to be used for physical uplink shared channel (PUSCH) transmission, the first information comprising information about unused configured grant (CG) physical uplink shared channel (PUSCH) transmission occasions (UTO); and using the configured uplink grant which is available for use to transmit uplink data to a network device.

Description

Uplink data sending method, receiving method, device and communication system Technical Field

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

[0002] Extended Reality (XR) services were introduced during the standardization process of the 5th Generation Mobile Communication Technology (5G) within the 3rd Generation Partnership Project (3GPP). XR services refer to human-computer interactions that combine real and virtual environments, computing technologies, and wearable devices. XR services can include virtual reality (VR), augmented reality (AR), and mixed reality (MR). Research on enhancements to XR services began in Release 18.

[0003] 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.

[0004] Summary of the Invention

[0005] The inventors discovered that a MAC entity of a terminal device determines whether a configured uplink grant is available for use, or whether a configured uplink grant will be used for transmission on a physical uplink shared channel (PUSCH). The MAC entity sends information related to the determination result to lower layers, which is used for the physical layer to report uplink control information (UCI) that provides information about unused CG PUSCH transmission occasions (UTO) for the physical uplink shared channel that does not use the configured grant. In 3GPP, this uplink control information is referred to as UTO-UCI.

[0006] However, even if the terminal device does not need to report UTO-UCI, or does not indicate to the lower layer whether a configured uplink grant is the transmission timing of an unused configured authorized physical uplink shared channel, or does not perform related services such as XR, or does not support UTO-UCI, the MAC entity of the terminal device will still determine whether a configured uplink grant is available or determine whether a configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission, which greatly increases the complexity and power consumption of the terminal device. If the terminal device does not support UTO-UCI, the uplink transmission will exceed the capabilities of the terminal device.

[0007] In order to solve at least one of the above problems or other similar problems, embodiments of the present application provide a method for sending, a method for receiving, an apparatus, and a communication system for uplink data.

[0008] According to one aspect of an embodiment of the present application, there is provided an apparatus for transmitting uplink data, configured in a terminal device, the apparatus comprising:

[0009] a first determining unit configured to determine, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission, wherein the first information includes information of unused CG PUSCH transmission occasions (UTO) of the configured grant;

[0010] A first sending unit is configured to send uplink data to a network device using the available configured uplink grant.

[0011] According to another aspect of an embodiment of the present application, a device for receiving uplink data is provided, which is configured in a network device, and the device includes:

[0012] A first receiving unit, configured to receive uplink data sent by a terminal device using a configured uplink grant;

[0013] The configured uplink grant is configured with information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or whether the configured uplink grant will be used for a configured uplink grant sent by a physical uplink shared channel (PUSCH); the first information includes information on unused CG PUSCH transmission occasions (UTO) of the configured uplink grant physical uplink shared channel.

[0014] According to another aspect of an embodiment of the present application, a method for transmitting uplink data is provided, which is applied to a terminal device, and the method includes:

[0015] determining, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission, wherein the first information includes information of unused CG PUSCH transmission occasions (UTOs) of the configured grant;

[0016] Uplink data is sent to the network device using the available configured uplink grant.

[0017] According to another aspect of an embodiment of the present application, a method for receiving uplink data is provided, which is applied to a network device, and the method includes:

[0018] Receiving uplink data sent by the terminal device using the configured uplink authorization;

[0019] The configured uplink grant is configured with information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or whether the configured uplink grant will be used for a configured uplink grant sent by a physical uplink shared channel (PUSCH); the first information includes information on unused CG PUSCH transmission occasions (UTO) of the configured uplink grant physical uplink shared channel.

[0020] According to another aspect of an embodiment of the present application, a terminal device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the above-mentioned method for sending uplink data on the terminal device side.

[0021] According to another aspect of an embodiment of the present application, a network device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the above-mentioned method for receiving uplink data on the network device side.

[0022] According to another aspect of an embodiment of the present application, a communication system is provided, including:

[0023] A terminal device that determines, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is available for use or whether the configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information on unused CG PUSCH transmission occasions (UTO); and uses the available configured uplink grant to send uplink data to a network device.

[0024] A network device receives the uplink data sent by the terminal device.

[0025] The beneficial effects of the embodiments of the present application include:

[0026] The terminal device determines whether the configured uplink authorization for the relevant information configured with UTO-UCI is available or will be used for physical uplink shared channel (PUSCH) transmission. Thus, it can prevent terminal devices that do not need to report UTO-UCI or do not perform XR-related services or do not support UTO-UCI reporting from making judgments on whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it can prevent uplink transmission from exceeding the capability of the terminal device.

[0027] With reference to the following description and 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 thereby. Within the scope of the terms of the appended claims, the embodiments of the present application include many variations, modifications, and equivalents.

[0028] 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.

[0029] 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

[0030] The elements and features described in one figure or one embodiment of the present application may 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.

[0031] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0032] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application;

[0033] FIG2 is a schematic diagram of a method for transmitting uplink data according to an embodiment of the present application;

[0034] FIG3 is a signaling diagram of interaction between a terminal device and a network device according to an embodiment of the present application;

[0035] FIG4 is a schematic diagram of a data processing method according to an embodiment of the present application;

[0036] FIG5 is a schematic diagram of a method for transmitting uplink data according to an embodiment of the present application;

[0037] FIG6 is a schematic diagram of a device for transmitting uplink data according to an embodiment of the present application;

[0038] FIG7 is a schematic diagram of a data processing device according to an embodiment of the present application;

[0039] FIG8 is a schematic diagram of a device for receiving uplink data according to an embodiment of the present application;

[0040] FIG9 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application;

[0041] FIG10 is a schematic diagram showing the structure of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

[0042] The foregoing and other features of the present application will become apparent from the following description with reference to the accompanying drawings. In the description and drawings, specific embodiments of the present application are disclosed, which illustrate some embodiments in which the principles of the present application can be employed. 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 falling within the scope of the appended claims. Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely illustrative and are not intended to limit the present application.

[0043] 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.

[0044] 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.

[0045] 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.

[0046] 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, 5G, New Radio (NR) and future 6G, etc., and / or other currently known or future developed communication protocols.

[0047] 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.

[0048] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), and 5G base stations (gNB), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their 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.

[0049] 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 user equipment may 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), a station, and so on.

[0050] Among them, user equipment or 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, laptops, cordless phones, smartphones, smart watches, digital cameras, XR devices, etc.

[0051] For another example, in scenarios such as the Internet of Things (IoT), user equipment can also be machines or devices for monitoring or measurement, such as but not limited to: machine type communication (MTC) terminals, vehicle-mounted communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, terminals that support sidelink communication, terminals that support XR services, and so on.

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

[0053] In this application, the MAC entity may also be expressed as the MAC layer, and the MAC entity may also be replaced by MAC bearer or MAC channel; the RRC entity may also be expressed as the RRC layer, and the RRC entity may also be replaced by RRC bearer or RRC channel. The lower layer is, for example, the physical layer.

[0054] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0055] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101, the first terminal device 102, and the second terminal 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low-latency communication (URLLC), XR communication, and related communications of terminal devices with reduced capabilities, etc.

[0056] It is worth noting that FIG1 shows that the first terminal device 102 and the second terminal device 103 are both within the coverage range of the network device 101, but the present application is not limited thereto. The first terminal device 102 and the second terminal device 103 may both be outside the coverage range of the network device 101, or one of the first terminal device 102 and the second terminal device 103 may be within the coverage range of the network device 101 while the other is outside the coverage range of the network device 101.

[0057] In an embodiment of the present application, a terminal device can send services to and from an opposite-end device. Taking the terminal device as the first terminal device 102 in FIG. 1 as an example, the opposite-end device of the present application can be the network device 101 and / or the second terminal device 103 in FIG. 1 . In actual applications, the opposite-end device can also be other network devices or terminal devices, and the embodiments of the present application are not limited thereto.

[0058] The 3GPP standard supports Configured Grant (CG) for uplink transmission. Using CG, network equipment can allocate uplink resources to terminal devices. Two types of CG are defined:

[0059] Type 1: RRC directly provides the configured uplink grant (including period).

[0060] Type 2: The RRC defines the period of the configured uplink grant, and the Physical Downlink Control Channel (PDCCH) addressed to the Configuration Scheduling Radio Network Temporary Identifier (CS-RNTI) can activate the configured uplink grant, or notify and activate the configured uplink grant; that is, the PDCCH addressed to the CS-RNTI indicates that the configured uplink grant can be implicitly reused according to the period defined by the RRC until it is deactivated.

[0061] CG is a good feature for periodic services and services with strict delay requirements. Most of the services generated by XR applications meet these two criteria. However, some XR services have more complex service patterns than CG designs. For example, video streaming services may include periodic protocol data unit block data (PDU burst) instead of a single PDU. This new service pattern requires enhancements to traditional CG configurations and procedures. Therefore, 3GPP agrees to support more than one configured uplink granted physical uplink shared channel transmission occasion (CG PUSCH transmission occasion, which can also be expressed or abbreviated as: multi-PUSCH configured grant, CG PTO, CG PUSCH TO, CG PUSCH occasion, CG PUSCH, CG occasion, CGO, etc.) in the period of a single CG PUSCH configuration, and the terminal device can use uplink control information to dynamically indicate to the network device the unused CG PUSCH transmission occasion (i.e., unused configured uplink grant).

[0062] The MAC entity of the terminal device determines whether a configured and activated uplink grant is available (available for use), and determines whether a configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission and sends an indication related to this decision to the lower layer (physical layer) when determining it. The physical layer is used to report uplink control information (UCI) related to "unused CG PUSCH transmission occasions (UTO) of unused configured grant physical uplink shared information". The uplink control information can also be abbreviated as UTO-UCI. The existing standard description is shown in Table 1 below:

[0063] Table 1: Some existing standards

[0064] However, in the prior art, the MAC entity always determines whether each configured and activated configured uplink grant is available and / or whether it will be used for physical uplink shared channel (PUSCH) transmission, even when there is no need to perform the above judgment, for example, when the terminal device does not need to report UTO-UCI, or the terminal device does not indicate to the lower layer whether a configured uplink grant is an unused CG PUSCH transmission occasion, or when the terminal device does not perform related services such as XR, or when the terminal device does not support UTO-UCI, etc. This greatly increases the complexity and power consumption of the terminal device, or exceeds the capabilities of the terminal device.

[0065] Therefore, how to reduce the complexity and power consumption of terminal devices and prevent uplink transmission from exceeding the capabilities of the terminal devices is one of the technical issues that need to be solved urgently.

[0066] In response to at least one of the above problems, embodiments of the present application provide a method for sending, a method for receiving, an apparatus, and a communication system for uplink data.

[0067] Embodiments of the first aspect

[0068] An embodiment of the present application provides a method for sending uplink data, which is described from the terminal device side.

[0069] FIG2 is a schematic diagram of a method for transmitting uplink data according to an embodiment of the present application. The method is applied to a terminal device. As shown in FIG2 , the method includes:

[0070] 201. For a configured uplink grant configured with information related to uplink control information (UCI) providing first information, a terminal device determines whether the configured uplink grant is available for use or whether the configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information about unused CG PUSCH transmission occasions (UTO) of the configured grant.

[0071] 202. The terminal device uses the available configured uplink grant to send uplink data to the network device.

[0072] According to the above embodiment, the terminal device determines whether the configured uplink authorization for the configured UTO-UCI related information is available or will be used for physical uplink shared channel (PUSCH) transmission. This can prevent terminal devices that do not need to report UTO-UCI, terminal devices that do not perform XR-related services, or terminal devices that do not support UTO-UCI reporting from making judgments on whether the configured uplink authorization is available or will be used for physical uplink shared channel (PUSCH) transmission, thereby reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it can prevent the terminal device's capabilities from being exceeded. It is worth noting that FIG2 above only schematically illustrates an embodiment of the present application, but the present application is not limited thereto. For example, the execution order between the various operations can be appropriately adjusted, and other operations can be added or some operations can be reduced. Those skilled in the art can make appropriate modifications based on the above content, and are not limited to the description of FIG2 above.

[0073] In some embodiments, in 201, uplink control information (UCI) of the first information is provided, that is, uplink control information of "unused CG PUSCH transmission occasions (UTO) of the configured uplink authorization" is provided, which can be represented by UTO-UCI, and the terminal device can report the UTO-UCI to the network device so that the network device knows the configured uplink authorization that is not used by the terminal device. Thus, the network device can reallocate the unused configured uplink authorization for other uplink transmissions of the terminal device, or for uplink transmissions of other terminal devices, thereby saving uplink resources. Among them, the physical uplink shared channel transmission occasions of the configured uplink authorization that is not used can also be understood as the configured uplink authorization that will not be used for physical uplink shared channel (PUSCH) transmission in the future.

[0074] In some embodiments, the configured uplink grant (configured uplink grant) in 201 is configured by the network device to the terminal device, for example, via an RRC message. The network device may configure one or more configured uplink grant configurations (configuredGrantConfig) to the terminal device, wherein each configured uplink grant configuration is respectively configured with information related to uplink control information (UTO-UCI) providing the first information, or wherein all configured uplink grants are not configured with information related to uplink control information (UTO-UCI) providing the first information.

[0075] For example, when the terminal device is configured with a configured uplink grant configuration, the configuration of the configured uplink grant is configured with information related to UTO-UCI, or the configured uplink grant is not configured with information related to UTO-UCI; for another example, when the terminal device is configured with more than one configured uplink grant configuration, some of the configured uplink grant configurations in the more than one configured uplink grant configurations are configured with information related to UTO-UCI, or all of the configured uplink grant configurations in the more than one configured uplink grant configurations are configured with information related to UTO-UCI, or all of the more than one configured uplink grant configurations are not configured with information related to UTO-UCI. When at least two configured uplink grants are configured with information related to the UTO-UCI, the information related to the UTO-UCI configured for all of the at least two configured uplink grants is the same, or the information related to the UTO-UCI configured for some of the at least two configured uplink grants is the same, or the information related to the UTO-UCI configured for all of the at least two configured uplink grants is different. This application is not limited to this.

[0076] In some embodiments, information related to the UTO-UCI is configured via RRC signaling. For example, a terminal device receives RRC signaling sent by a network device, where the RRC signaling includes information related to the UTO-UCI configured for the configured uplink grant. For example, the configuration is performed via the uto-UCI-Config parameter in the ConfiguredGrantConfig parameter in the RRC signaling, and the configuration format is shown in Table 2 below:

[0077] Table 2: Configuration format of information related to UTO-UCI

[0078] In some embodiments, the RRC layer of the terminal device configures information related to the UTO-UCI for at least one configured uplink grant to the MAC entity. For example, the RRC layer of the terminal device configures information related to the UTO-UCI for at least one configured uplink grant to the MAC entity according to RRC signaling of the network device.

[0079] In some embodiments, the information related to the UTO-UCI includes the configuration of the parameter uto-UCI-Config, where the parameter uto-UCI-Config includes the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI. Alternatively, the information related to the UTO-UCI includes the configuration of the parameter nrofBitsInUTO-UCI and the configuration of the parameter betaOffsetUTO-UCI. For the configuration of the parameter uto-UCI-Config, please refer to Table 2 above.

[0080] In some embodiments, in 201, for a configured uplink grant configured with information related to UTO-UCI, the MAC entity of the terminal device determines whether the configured uplink grant is available for use, or whether the configured uplink grant will be used for PUSCH transmission.

[0081] For example, for a configured uplink grant that is configured with information related to UTO-UCI, the MAC entity of the terminal device should perform the following operations: if the configured uplink grant is associated with a multi-PUSCH configured grant, and if the configured uplink grant has not been indicated to the lower layer as unused for PUSCH transmission, and the configured uplink grant meets the relevant validity conditions specified by the physical layer, then the configured uplink grant is considered available;

[0082] Otherwise, if the configured uplink grant is not associated with the configured grant of multiple physical uplink shared channels, and the configured uplink grant has not been indicated to the lower layer not to be used for physical uplink shared channel transmission, the configured uplink grant is considered available.

[0083] The multi-PUSCH configured grant refers to supporting more than one CG PUSCH transmission opportunity in a single CG PUSCH configured period. The relevant validity conditions specified by the physical layer include, for example, the validity conditions specified in clause 6.1 of TS 38.214[7].

[0084] In some embodiments, the MAC entity of the terminal device indicates to the lower layer whether a configured uplink grant is not used for physical uplink shared channel transmission, or whether a configured uplink grant will be used for PUSCH transmission. For example, the MAC entity of the terminal device determines whether a configured uplink grant is not used for PUSCH transmission or will be used for PUSCH transmission, for example, by considering the amount of buffered data that can be transmitted at the available opportunity of the associated configured grant and other available uplink (UL-SCH) resources to determine whether a configured uplink grant will be used for PUSCH transmission; after making this determination, the MAC entity sends an indication related to the determination result to the lower layer for use in the process of reporting UTO-UCI.

[0085] In some embodiments, a MAC entity of a terminal device determines whether a configured uplink grant configured with information related to uplink control information (UTO-UCI) providing first information will be used for PUSCH transmission, and indicates the determination result to the physical layer, and the determination result is used by the physical layer of the terminal device to report the uplink control information providing the first information. Thus, for an uplink grant configured with information related to providing UTO-UCI, the MAC entity of the terminal device determines whether the configured uplink grant is used for PUSCH transmission, and for an uplink grant not configured with information related to providing UTO-UCI, the MAC entity of the terminal device does not determine whether the configured uplink grant is used for PUSCH transmission, thereby reducing the complexity and power consumption of the terminal device without exceeding the capabilities of the terminal device.

[0086] In some embodiments, in 202 , the terminal device sends a new transmission and / or retransmission of uplink data to the network device using the configured uplink grant determined to be available in 201 and configured with information related to the UTO-UCI.

[0087] In some embodiments, the method further comprises:

[0088] The terminal device determines whether a configured uplink grant is configured with information related to uplink control information (UTO-UCI) providing first information.

[0089] For example, the RRC layer of the terminal device determines whether a configured uplink authorization is configured with information related to UTO-UCI. In order to determine the UTO-UCI reporting or to determine the configured uplink authorization that is not used for physical uplink shared channel transmission, the RRC layer of the terminal device configures the parameter uto-UCI-Config, or the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI for at least one configured uplink authorization, and indicates to the MAC entity that the at least one configured uplink authorization is configured with information related to UTO-UCI. For example, the RRC layer of the terminal device receives an RRC message from a network device, and the RRC message includes information related to UTO-UCI. The RRC layer of the terminal device configures information related to UTO-UCI for at least one configured uplink authorization according to the RRC message. Thus, the MAC entity can know that the configured uplink authorization is configured with information related to UTO-UCI. Therefore, for an uplink authorization configured with the parameter uto-UCI-Config, or an uplink authorization configured with the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI, the MAC entity determines whether the uplink authorization of the configuration is available. For the specific method of determination, please refer to the operations that the MAC entity should perform in the aforementioned related embodiments, which will not be repeated here.

[0090] For another example, the lower layer of the terminal device determines whether a configured uplink authorization is configured with information related to UTO-UCI. The physical layer of the terminal device identifies whether a configured uplink authorization is configured with the parameter uto-UCI-Config, or identifies whether a configured uplink authorization is configured with the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI. If so, the physical layer considers that the configured uplink authorization is configured with information related to UTO-UCI, and indicates the result to the MAC layer. Thus, the MAC entity is able to know that the configured uplink authorization is configured with information related to UTO-UCI. Therefore, for a configured uplink authorization configured with the parameter uto-UCI-Config, or a configured uplink authorization configured with the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI, the MAC entity determines whether the configured uplink authorization is available. For the specific method of determination, please refer to the operations that the MAC entity should perform in the aforementioned related embodiments, which will not be repeated here.

[0091] Examples of modifications to the standard are shown in Table 3 (optional methods are shown in brackets) or Table 4 below:

[0092] Table 3: Modifications to the Standard (Example 1)

[0093] Table 4: Modifications to the Standard (Example 2)

[0094] For another example, the MAC entity of the terminal device determines whether a configured uplink grant is configured with information related to the UTO-UCI. For a configured uplink grant, the MAC entity of the terminal device should perform the following operations:

[0095] If the parameter uto-UCI-Config is configured, or the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI are configured, and if the configured uplink grant is associated with a multi-PUSCH configured grant, the configured uplink grant has not been indicated to the lower layers as unused for PUSCH transmission, and the configured uplink grant meets the relevant validity conditions specified by the physical layer, then the configured uplink grant is considered available; and / or,

[0096] If the parameter uto-UCI-Config is configured, or the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI are configured, and if the uplink grant of this configuration is not associated with the configured grant of multiple physical uplink shared channels, and the uplink grant of this configuration has not been indicated to the lower layer not to be used for physical uplink shared channel transmission, then the uplink grant of this configuration is considered available.

[0097] In some embodiments, the MAC entity of the terminal device determines that the configured uplink authorization is not configured with information related to the uplink control information (UTO-UCI) providing the first information, and considers that the configured uplink authorization is available.

[0098] For example, for a configured uplink authorization, the MAC entity of the terminal device should perform the following operations:

[0099] If the parameter uto-UCI-Config is not configured, or the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI are not configured, the uplink grant of this configuration is considered available.

[0100] Examples of modifications to the standard are shown in Table 5 below (optional methods are shown in brackets):

[0101] Table 5: Modifications to the Standard (Example 3)

[0102] In some embodiments, the method further comprises:

[0103] For each service cell and each configured uplink authorization, when the configured uplink authorization is configured and activated, if the configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing first information and is available, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

[0104] The configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing the first information, including: the configured uplink authorization is configured with the parameter uto-UCI-Config, and / or the configured uplink authorization is configured with the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI.

[0105] In this embodiment, it is first determined whether the configured uplink authorization is configured and activated. If the configured uplink authorization is configured and activated, it is then determined whether the configured and activated uplink authorization is configured with information related to the UTO-UCI and is available.

[0106] Examples of modifications to the standard are shown in Table 6 below (optional methods are shown in brackets):

[0107] Table 6: Modifications to the Standard (Example 4)

[0108] In some embodiments, the method further comprises:

[0109] For each service cell and each configured uplink authorization, if the configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing first information, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization when the configured uplink authorization is configured, activated and available.

[0110] The configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing the first information, including: the configured uplink authorization is configured with the parameter uto-UCI-Config, and / or the configured uplink authorization is configured with the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI.

[0111] In this embodiment, it is first determined whether the configured uplink authorization is configured with information related to the UTO-UCI. If the configured uplink authorization is configured with information related to the UTO-UCI, it is then determined whether the configured uplink authorization is configured, activated, and available.

[0112] In some embodiments, the method further comprises:

[0113] For each service cell and each configured uplink authorization, if the configured uplink authorization is not configured with information related to the uplink control information (UTO-UCI) providing the first information, when the configured uplink authorization is configured and activated, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

[0114] The configured uplink authorization is not configured with information related to the uplink control information (UTO-UCI) providing the first information, including: the configured uplink authorization is not configured with the parameter uto-UCI-Config, and the configured uplink authorization is not configured with the parameter nrofBitsInUTO-UCI and the parameter betaOffsetUTO-UCI.

[0115] Examples of modifications to the standard are shown in Table 7 below (optional methods are shown in brackets):

[0116] Table 7: Modifications to the Standard (Example 5):

[0117] In some embodiments, the MAC entity of the terminal device generates an uplink transmission (PUSCH transmission) for the configured uplink grant, including:

[0118] Under specific conditions, the relevant HARQ information of the configured uplink authorization is set, such as the HARQ process identifier (HARQ Process ID), the configured uplink authorization and the relevant HARQ information are passed to the HARQ entity, and the MAC PDU to be sent in the configured uplink authorization is obtained. The MAC PDU, the configured uplink authorization and the relevant HARQ information are passed to the relevant HARQ process, and the HARQ process is instructed to trigger a new transmission or retransmission. After the HARQ process generates a new transmission or retransmission, the physical layer is instructed to generate an uplink transmission according to the configured uplink authorization, that is, a PUSCH transmission.

[0119] In some embodiments, the method further comprises:

[0120] The terminal device reports uplink control information providing the first information, namely, UTO-UCI information, to the network device.

[0121] For example, when a terminal device needs to report UTO-UCI, the MAC entity of the terminal device determines whether a configured uplink grant configured with information related to the UTO-UCI will be used for PUSCH transmission, and indicates the determination result to a lower layer (e.g., a physical layer); the lower layer reports the UTO-UCI based on the indication of the MAC entity, for example, the UTO-UCI includes information of a configured uplink grant that is not used for physical uplink shared channel transmission (unused for PUSCH transmission). For the specific content of the MAC entity determining whether the configured uplink grant is available, please refer to the description of the aforementioned related embodiments, which will not be repeated here.

[0122] Examples of modifications to the standard are shown in Table 8 (optional methods are shown in brackets) or Table 9 below:

[0123] Table 8: Modifications to the Standard (Example 6)

[0124] Table 9: Modifications to the Standard (Example 7)

[0125] In some embodiments, the method further comprises:

[0126] The terminal device reports to the network device indication information indicating whether UTO-UCI reporting is supported. For example, this indication information is included in the UE capability information reported by the terminal device to the network device. This UE capability information is sent to the network device, for example, during the process of the terminal device initiating random access. This allows the network device to configure the configured uplink authorization configuration to match the capabilities of the terminal device, preventing the UE capabilities from being exceeded.

[0127] In some embodiments, the indication information for indicating whether the terminal device supports UTO-UCI reporting may be the cg-PUSCH-UTO-UCI-Ind-r18 parameter. The cg-PUSCH-UTO-UCI-Ind-r18 parameter indicates whether the UE supports multiplexing of unused transmission opportunity UCI (UTO-UCI) on the CG-PUSCH. Indicating that the terminal device supports multiplexing should also indicate support for at least one of the following parameters: configuredUL-GrantType1, configuredUL-GrantType1-v1650, configuredUL-GrantType2, configuredUL-GrantType2-v1650.

[0128] In some embodiments, if the terminal device supports UTO-UCI reporting, for example, the cg-PUSCH-UTO-UCI-Ind-r18 parameter is included in the UE capability information, the terminal device determines whether the configured uplink grant is available or whether it will be used for PUSCH transmission. The method for determining whether the configured uplink grant is available or whether it will be used for PUSCH transmission can refer to the above embodiment. This embodiment can be used alone or in combination with one or more of the above embodiments.

[0129] In some embodiments, for a configured uplink authorization, if the terminal device supports UTO-UCI reporting, the MAC entity of the terminal device determines whether the configured uplink authorization is available. For the specific determination method, please refer to the operations that the MAC entity should perform in the aforementioned related embodiments, which will not be repeated here.

[0130] Examples of modifications to the standard are shown in Table 10 below:

[0131] Table 10: Modifications to the Standard (Example 8)

[0132] In some embodiments, for a configured uplink authorization, the MAC entity should determine whether the configured uplink authorization is available when the terminal device supports UTO-UCI reporting. For the specific determination method, please refer to the operations that the MAC entity should perform in the aforementioned related embodiments, which will not be repeated here.

[0133] In some embodiments, for a configured uplink grant, the MAC entity should consider the configured uplink grant to be available when the terminal device does not support UTO-UCI reporting.

[0134] Examples of modifications to the standard are shown in Table 11 below:

[0135] Table 11: Modifications to the Standard (Example 9)

[0136] In some embodiments, for each serving cell and each configured uplink authorization, when the uplink authorization of the configuration is configured and activated, if the terminal device supports UTO-UCI reporting and the uplink authorization of the configuration is available, the MAC entity of the terminal device generates an uplink transmission for the uplink authorization of the configuration.

[0137] In this embodiment, it is first determined whether the configured uplink authorization is configured and activated. If the configured uplink authorization is configured and activated, it is then determined whether the terminal device supports UTO-UCI reporting and whether the configured and activated uplink authorization is available.

[0138] Examples of modifications to the standard are shown in Table 12 below:

[0139] Table 12: Modifications to the Standard (Example 10)

[0140] In some embodiments, for each serving cell and each configured uplink authorization, if the terminal device does not support UTO-UCI reporting, when the uplink authorization of the configuration is configured and activated, the MAC entity of the terminal device generates an uplink transmission for the uplink authorization of the configuration.

[0141] In some embodiments, for each serving cell and each configured uplink authorization, if the terminal device supports UTO-UCI reporting, when the configured uplink authorization is configured, activated and available, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

[0142] In this embodiment, it is first determined whether the terminal device supports UTO-UCI reporting. If the terminal device supports UTO-UCI reporting, it is then determined whether the configured uplink authorization is configured, activated, and available.

[0143] Examples of modifications to the standard are shown in Table 13 below:

[0144] Table 13: Modifications to the Standard (Example 11)

[0145] In some embodiments, the method further comprises:

[0146] If the terminal device supports UTO-UCI reporting, the MAC entity of the terminal device determines whether the configured uplink grant will be used for PUSCH transmission and indicates the determination result to the lower layer (e.g., the physical layer); the lower layer reports the UTO-UCI based on the indication of the MAC entity, for example, the UTO-UCI includes information about the configured uplink grant that is not used for physical uplink shared channel transmission (unused for PUSCH transmission). For the specific content of the MAC entity determining whether the configured uplink grant is available, please refer to the description of the relevant embodiments above and will not be repeated here.

[0147] Examples of modifications to the standard are shown in Table 14 below:

[0148] Table 14: Modifications to the Standard (Example 12)

[0149] FIG3 is a signaling diagram of the interaction between the terminal device and the network device according to an embodiment of the present application. As shown in FIG3 , the interaction between the terminal device and the network device includes:

[0150] 301. The terminal device reports UE capability information to the network device, where the UE capability information includes indication information indicating whether UTO-UCI reporting is supported.

[0151] 302. The network device provides the terminal device with a configured uplink grant (including a period) through RRC signaling, corresponding to a Type 1 configuration grant; or the network device configures the period of the configured uplink grant through RRC signaling, corresponding to a Type 2 configuration grant;

[0152] 303. The network device activates the configured uplink grant by addressing the PDCCH of the CS-RNTI. Step 303 is executed when a Type 2 configuration grant is configured in step 302. When a Type 1 configuration grant is configured in step 302, step 303 is not executed. The dotted line in FIG3 indicates that step 303 is optionally executed.

[0153] 304. The terminal device determines, for the uplink grant configured with information related to the UTO-UCI, whether the configured uplink grant is available or will be used for PUSCH transmission. For details related to the implementation of step 304, please refer to the aforementioned related embodiments and will not be repeated here.

[0154] 305 The terminal device uses the available configured uplink grant to perform uplink transmission, that is, to send uplink data to the network device;

[0155] 306. The terminal device reports the UTO-UCI to the network device. For details related to step 306, please refer to the above-mentioned related embodiments and will not be repeated here.

[0156] The execution order of steps 305 and 306 can be adjusted appropriately. For example, step 306 can be executed first and then step 305, or steps 305 and 306 can be executed simultaneously, or the UTO-UCI in step 306 can be sent in the configured uplink grant of step 305. At least one of steps 301 to 306 can be omitted, or the interaction between the terminal device and the network device can include other steps different from steps 301 to 306. This application does not impose any restrictions on this.

[0157] Through the above embodiments, the terminal device determines whether the configured uplink authorization is available or will be used for PUSCH transmission for the configured uplink authorization of the relevant information configured with UTO-UCI. Thus, it is possible to prevent terminal devices that do not need to report UTO-UCI or terminal devices that do not perform XR-related services or terminal devices that do not support UTO-UCI reporting from making judgments on whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it is possible to prevent the terminal device's capabilities from being exceeded. The above embodiments are only illustrative of the embodiments of the present application, but the present application is not limited thereto, and appropriate modifications can be made on the basis of the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0158] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0159] 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.

[0160] Embodiments of the second aspect

[0161] An embodiment of the present application provides a data processing method, which is described from the perspective of a terminal device.

[0162] FIG4 is a schematic diagram of a method for receiving uplink data according to an embodiment of the present application. The method is applied to a terminal device. As shown in FIG4 , the method includes:

[0163] 401. For a configured uplink grant configured with information related to uplink control information (UCI) providing first information, the terminal device determines whether the configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information on unused CG PUSCH transmission occasions (UTO) of the configured grant.

[0164] According to the above embodiment, the terminal device determines whether the configured uplink authorization for the relevant information configured with UTO-UCI will be used for PUSCH transmission, thereby preventing the terminal device that does not need to report UTO-UCI or does not perform XR-related services or does not support UTO-UCI reporting from making the judgment on whether the configured uplink authorization will be used for PUSCH transmission, reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for the terminal device that does not support UTO-UCI reporting, it can prevent the terminal device from exceeding the capability.

[0165] It is worth noting that FIG4 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG4 above.

[0166] In some embodiments, a MAC entity of a terminal device determines whether a configured uplink grant configured with information related to uplink control information (UTO-UCI) providing first information will be used for PUSCH transmission, and indicates the determination result to the physical layer, and the determination result is used by the physical layer of the terminal device to report the uplink control information providing the first information. Thus, for an uplink grant configured with information related to providing UTO-UCI, the MAC entity of the terminal device determines whether the configured uplink grant is used for PUSCH transmission, and / or, for an uplink grant not configured with information related to providing UTO-UCI, the MAC entity of the terminal device does not determine whether the configured uplink grant is used for PUSCH transmission, thereby reducing the complexity and power consumption of the terminal device without exceeding the capabilities of the terminal device.

[0167] Examples of modifications to the standard are shown in Table 15, Table 16, or Table 17 below (optional methods are shown in brackets):

[0168] Table 15: Modifications to the Standard (Example 13)

[0169] Table 16: Modifications to the Standard (Example 14)

[0170] Table 17: Modifications to the Standard (Example 15)

[0171] In some embodiments, the terminal device supports UTO-UCI reporting, and the terminal device determines whether the configured uplink grant is to be used for PUSCH transmission.

[0172] In the above embodiment, as long as the terminal device supports UTO-UCI reporting, whether the configured uplink grant will be used for PUSCH transmission. For the determination of whether the terminal device supports UTO-UCI reporting, please refer to the relevant content of the embodiment of the first aspect of this application, which will not be repeated here.

[0173] Examples of modifications to the standard are shown in Table 18 below:

[0174] Table 18: Modifications to the Standard (Example 16)

[0175] The implementation and glossary of the embodiment of the second aspect are similar to the contents of the embodiment of the first aspect of this application. The above related contents are merged here and will not be repeated here.

[0176] 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.

[0177] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0178] 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.

[0179] Embodiments of the third aspect

[0180] An embodiment of the present application provides a method for receiving uplink data, which is described from the perspective of a network device.

[0181] FIG5 is a schematic diagram of a method for receiving uplink data according to an embodiment of the present application. The method is applied to a network device. As shown in FIG5 , the method includes:

[0182] 501. A network device receives uplink data sent by a terminal device using a configured uplink grant; wherein the configured uplink grant is configured with information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or to be used for a configured uplink grant sent by a physical uplink shared channel (PUSCH); the first information includes information on unused CG PUSCH transmission occasions (UTO).

[0183] According to the above embodiment, the network device receives uplink data sent by the terminal device using the configured uplink authorization, and the configured uplink authorization is an uplink authorization that the terminal device determines is available or will be used for PUSCH transmission when the configured uplink authorization is configured with information related to UTO-UCI. As a result, terminal devices that do not need to report UTO-UCI or terminal devices that do not perform XR-related services or terminal devices that do not support UTO-UCI reporting can be prevented from judging whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it can prevent the terminal device's capabilities from being exceeded.

[0184] It is worth noting that FIG5 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG5 above.

[0185] In some embodiments, the implementation and glossary of 501 of the embodiment of the second aspect are similar to the contents of 201 and 202 of the embodiment of the first aspect of this application. The above related contents are merged here and will not be repeated here.

[0186] In some embodiments, information related to uplink control information (UTO-UCI) providing the first information is configured by the network device through RRC signaling.

[0187] In some embodiments, the information related to uplink control information (UCI) providing the first information (UTO-UCI) includes:

[0188] The configuration of the parameter uto-UCI-Config; or

[0189] Configuration of the parameter nrofBitsInUTO-UCI and the configuration of the parameter betaOffsetUTO-UCI.

[0190] In some embodiments, each configured uplink grant configured by the terminal device is respectively configured or not configured with information related to uplink control information (UTO-UCI) providing the first information.

[0191] In some embodiments, whether the configured uplink authorization is available is determined by the terminal device. For the specific manner in which the terminal device determines that the configured uplink authorization is available, please refer to the embodiment of the first aspect and will not be repeated here.

[0192] In some embodiments, the method further comprises:

[0193] The network device receives the UTO-UCI reported by the terminal device.

[0194] For the content related to the terminal device reporting UTO-UCI, please refer to the embodiment of the first aspect and will not be repeated here.

[0195] In some embodiments, the method further comprises:

[0196] The network device receives UE capability information reported by the terminal device, where the UE capability information includes indication information for indicating whether UTO-UCI reporting is supported.

[0197] For the content related to the indication information used to indicate whether UTO-UCI reporting is supported, please refer to the embodiment of the first aspect and will not be repeated here.

[0198] It can be seen from the above embodiments that in the uplink data receiving method of the embodiment of the present application, the network device receives the uplink data sent by the terminal device using the configured uplink authorization. The configured uplink authorization is an uplink authorization that the terminal device determines is available or will be used for PUSCH sending when the configured uplink authorization is configured with information related to UTO-UCI. Thus, terminal devices that do not need to report UTO-UCI or terminal devices that do not perform XR-related services or terminal devices that do not support UTO-UCI reporting can be prevented from judging whether the configured uplink authorization is available or will be used for PUSCH sending, thereby reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it can prevent the terminal device's capabilities from being exceeded.

[0199] The implementation and glossary of the embodiment of the third aspect are similar to the contents of the embodiment of the first aspect of this application. The above related contents are merged here and will not be repeated here.

[0200] 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.

[0201] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0202] 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.

[0203] Embodiments of the fourth aspect

[0204] An embodiment of the present application provides an uplink data sending device, which is applied / configured in a terminal device. The uplink data sending device and the uplink data sending method in the embodiment of the first aspect provided by the present application are based on the same inventive concept and have similar principles for solving the problem. Therefore, for the implementation of the uplink data sending device, please refer to the implementation of the uplink data sending method in the embodiment of the first aspect provided by the present application, and the repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0205] FIG6 is a schematic diagram of a device for transmitting uplink data according to an embodiment of the present application. As shown in FIG6 , the device includes:

[0206] A first determining unit 601 is configured to determine, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission; the first information including information of unused CG PUSCH transmission occasions (UTO) of the configured grant;

[0207] The first sending unit 602 is configured to send uplink data to a network device using the available configured uplink grant.

[0208] According to the above embodiment, the terminal device determines whether the configured uplink authorization is available or will be used for PUSCH transmission for the configured uplink authorization of the relevant information configured with UTO-UCI. Therefore, it is possible to prevent terminal devices that do not need to report UTO-UCI or do not perform XR-related services or do not support UTO-UCI reporting from making judgments on whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it is possible to prevent the terminal device's capabilities from being exceeded.

[0209] In some embodiments, the information related to uplink control information (UTO-UCI) providing the first information is configured through RRC signaling.

[0210] In some embodiments, the information related to uplink control information (UCI) providing the first information (UTO-UCI) includes:

[0211] The configuration of the parameter uto-UCI-Config; or

[0212] Configuration of the parameter nrofBitsInUTO-UCI and the configuration of the parameter betaOffsetUTO-UCI.

[0213] In some embodiments, each configured uplink grant configured by the terminal device is respectively configured or not configured with information related to uplink control information (UTO-UCI) providing the first information.

[0214] In some embodiments, the first determining unit 601 is further configured to:

[0215] If the configured uplink grant is associated with a multi-PUSCH configured grant, the configured uplink grant has not been indicated to lower layers as unused for PUSCH transmission, and the configured uplink grant satisfies relevant validity conditions specified by the physical layer, the configured uplink grant is considered available; and / or

[0216] If the configured uplink grant is not associated with a multi-PUSCH configured grant and the configured uplink grant has not been indicated to lower layers as unused for PUSCH transmission, the configured uplink grant is considered available.

[0217] In some embodiments, the apparatus further comprises:

[0218] The second determining unit 603 (not shown) is configured to determine that the configured uplink grant is configured with information related to uplink control information (UTO-UCI) providing the first information.

[0219] In some embodiments, the configured uplink grant determined by a lower layer or an RRC layer is configured with information related to uplink control information (UTO-UCI) providing the first information.

[0220] In some embodiments, the configured uplink grant determined by the MAC entity is configured with information related to uplink control information (UTO-UCI) providing the first information.

[0221] In some embodiments, the apparatus further comprises:

[0222] The third determining unit 604 (not shown) is configured to determine that the configured uplink grant is not configured with information related to uplink control information (UTO-UCI) providing the first information.

[0223] In some embodiments, the first determining unit 601 is further configured to:

[0224] In a case where it is determined that the configured uplink grant is not configured with information related to uplink control information (UTO-UCI) providing the first information, it is considered that the configured uplink grant is available.

[0225] In some embodiments, for each service cell and each configured uplink authorization, when the configured uplink authorization is configured and activated, if the configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing first information and is available, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

[0226] In some embodiments, for each service cell and each configured uplink authorization, if the configured uplink authorization is not configured with information related to uplink control information (UTO-UCI) providing first information, when the configured uplink authorization is configured and activated, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

[0227] In some embodiments, for each service cell and each configured uplink authorization, if the configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing first information, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization when the configured uplink authorization is configured, activated and available.

[0228] In some embodiments, the MAC entity of the terminal device determines whether the configured uplink authorization that is configured with information related to uplink control information (UTO-UCI) providing first information will be used for uplink transmission, and indicates the determination result to the physical layer, and the determination result is used for the physical layer of the terminal device to report the uplink control information providing first information.

[0229] In some embodiments, the apparatus further comprises:

[0230] The second sending unit 605 (not shown) is configured to report the uplink control information providing the first information to the network device.

[0231] In some embodiments, the RRC layer of the terminal device configures the MAC entity with information related to uplink control information (UCI) of at least one configured uplink authorization providing the first information.

[0232] In some embodiments, the apparatus further comprises:

[0233] The third sending unit 606 (not shown) is configured to report UE capability information to the network device, where the UE capability information includes indication information indicating whether UTO-UCI reporting is supported.

[0234] In some embodiments, the indication information includes a cg-PUSCH-UTO-UCI-Ind-r18 parameter.

[0235] It can be seen from the above embodiments that the terminal device determines whether the configured uplink authorization is available or will be used for PUSCH transmission for the configured uplink authorization of the relevant information configured with UTO-UCI. Therefore, it is possible to prevent terminal devices that do not need to report UTO-UCI or terminal devices that do not perform XR-related services or terminal devices that do not support UTO-UCI reporting from making judgments on whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it is possible to prevent the terminal device from exceeding its capabilities.

[0236] The implementation and glossary of this embodiment are similar to those of the embodiment of the first aspect of this application. The above related contents are incorporated herein and will not be repeated here.

[0237] 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.

[0238] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0239] 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.

[0240] Embodiments of the fifth aspect

[0241] The embodiment of the present application provides a data processing device, which is applied / configured to a terminal device. The data processing device and the data processing method in the embodiment of the second aspect provided by the present application are based on the same inventive concept and have similar principles for solving the problem. Therefore, for the implementation of the data processing device, please refer to the implementation of the data processing method in the embodiment of the second aspect provided by the present application, and the repeated parts will not be repeated. As used below, the term "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceived.

[0242] FIG7 is a schematic diagram of a data processing device according to an embodiment of the present application. As shown in FIG7 , the device includes:

[0243] A data processing unit 701 determines, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information on unused CG PUSCH transmission occasions (UTO) of the configured grant.

[0244] According to the above embodiment, the terminal device determines whether the configured uplink authorization for the relevant information configured with UTO-UCI is available or will be used for PUSCH transmission. Therefore, it is possible to prevent terminal devices that do not need to report UTO-UCI or do not perform XR-related services or do not support UTO-UCI reporting from making a judgment on whether the configured uplink authorization will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving the power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it is possible to prevent the terminal device's capabilities from being exceeded.

[0245] It is worth noting that FIG7 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG7 above.

[0246] In some embodiments, a MAC entity of a terminal device determines whether a configured uplink grant configured with information related to uplink control information (UTO-UCI) providing first information will be used for PUSCH transmission, and indicates the determination result to the physical layer, and the determination result is used by the physical layer of the terminal device to report the uplink control information providing the first information. Thus, for an uplink grant configured with information related to providing UTO-UCI, the MAC entity of the terminal device determines whether the configured uplink grant is used for PUSCH transmission, and for an uplink grant not configured with information related to providing UTO-UCI, the MAC entity of the terminal device does not determine whether the configured uplink grant is used for PUSCH transmission, thereby reducing the complexity and power consumption of the terminal device without exceeding the capabilities of the terminal device.

[0247] In some embodiments, the terminal device supports UTO-UCI reporting, and the terminal device determines whether the configured uplink grant is to be used for PUSCH transmission.

[0248] In the above embodiment, as long as the terminal device supports UTO-UCI reporting, whether the configured uplink grant will be used for PUSCH transmission. For the determination of whether the terminal device supports UTO-UCI reporting, please refer to the relevant content of the embodiment of the first aspect of this application, which will not be repeated here.

[0249] The implementation and glossary of the embodiment of the fifth aspect are similar to the contents of the embodiment of the second aspect of this application. The above related contents are merged here and will not be repeated here.

[0250] 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.

[0251] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0252] 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.

[0253] Embodiments of the sixth aspect

[0254] An embodiment of the present application provides a device for receiving uplink data, which is applied / configured in a network device. The device for receiving uplink data and the method for receiving uplink data in the embodiment of the third aspect provided by the present application are based on the same inventive concept and have similar principles for solving the problem. Therefore, the implementation of the device for receiving uplink data refers to the implementation of the method for receiving uplink data in the embodiment of the second aspect provided by the present application, and the repeated parts will not be repeated. As used below, the terms "unit" or "module" can be a combination of software and / or hardware that implements a predetermined function. Although the system described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0255] FIG8 is a schematic diagram of a device for receiving uplink data according to an embodiment of the present application. As shown in FIG8 , the device includes:

[0256] A first receiving unit 801 is configured to receive uplink data sent by a terminal device using a configured uplink grant;

[0257] The configured uplink grant is configured with information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or whether the configured uplink grant will be used for a configured uplink grant sent by a physical uplink shared channel (PUSCH); the first information includes information on unused CG PUSCH transmission occasions (UTO) of the configured uplink grant physical uplink shared channel.

[0258] According to the above embodiment, the network device receives uplink data sent by the terminal device using the configured uplink authorization, and the configured uplink authorization is an uplink authorization that the terminal device determines is available or will be used for PUSCH transmission when the configured uplink authorization is configured with information related to UTO-UCI. Thus, terminal devices that do not need to report UTO-UCI or terminal devices that do not perform XR-related services or terminal devices that do not support UTO-UCI reporting can be prevented from judging whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it can prevent the terminal device's capabilities from being exceeded.

[0259] It is worth noting that FIG8 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG8 above.

[0260] In some embodiments, information related to uplink control information (UTO-UCI) providing the first information is configured by the network device through RRC signaling.

[0261] In some embodiments, the information related to uplink control information (UCI) providing the first information (UTO-UCI) includes:

[0262] The configuration of the parameter uto-UCI-Config; or

[0263] Configuration of the parameter nrofBitsInUTO-UCI and the configuration of the parameter betaOffsetUTO-UCI.

[0264] In some embodiments, each configured uplink grant configured by the terminal device is respectively configured or not configured with information related to uplink control information (UTO-UCI) providing the first information.

[0265] In some embodiments, whether the configured uplink authorization is available is determined by the terminal device. For the specific manner in which the terminal device determines that the configured uplink authorization is available, please refer to the embodiment of the first aspect and will not be repeated here.

[0266] In some embodiments, the apparatus further comprises:

[0267] The second receiving unit 802 (not shown) is configured to receive the UTO-UCI reported by the terminal device.

[0268] For the content related to the terminal device reporting UTO-UCI, please refer to the embodiment of the first aspect and will not be repeated here.

[0269] In some embodiments, the apparatus further comprises:

[0270] The third receiving unit 803 (not shown) is configured to receive UE capability information reported by the terminal device, where the UE capability information includes indication information indicating whether UTO-UCI reporting is supported.

[0271] For the content related to the indication information used to indicate whether UTO-UCI reporting is supported, please refer to the embodiment of the first aspect and will not be repeated here.

[0272] It can be seen from the above embodiments that the network device receives the uplink data sent by the terminal device using the configured uplink authorization. The configured uplink authorization is an uplink authorization that the terminal device determines is available or will be used for PUSCH transmission when the configured uplink authorization is configured with information related to UTO-UCI. Therefore, it is possible to prevent terminal devices that do not need to report UTO-UCI or terminal devices that do not perform XR-related services or terminal devices that do not support UTO-UCI reporting from judging whether the configured uplink authorization is available or will be used for PUSCH transmission, thereby reducing the complexity of the terminal device and saving power consumption of the terminal device. In addition, for terminal devices that do not support UTO-UCI reporting, it is possible to prevent the terminal device's capabilities from being exceeded.

[0273] The implementation and glossary of this embodiment are similar to the contents of the embodiment of the third aspect of this application. The above related contents are merged here and will not be repeated here.

[0274] The above embodiments are merely exemplary of the embodiments of the present application, but the present application is not limited thereto, and 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 or the embodiments of the first aspect of the present application may be combined.

[0275] It is worth noting that the above only describes the steps related to the present application, but the present application is not limited thereto. The data receiving method of the present application may also include other steps, and for the specific content of these steps, reference may be made to the relevant art.

[0276] Embodiments of the seventh aspect

[0277] An embodiment of the present application provides a communication system, which can be referred to in FIG1 . The communication system includes a network device 101 , a terminal device 102 , and a terminal device 103 .

[0278] In an embodiment of the present application, the terminal device 102 and / or the terminal device 103 is configured to execute the method for sending uplink data in the embodiment of the first aspect of the present application, the content of which is incorporated herein and will not be repeated here.

[0279] In an embodiment of the present application, the network device 101 is configured to execute the method for receiving uplink data in the embodiment of the second aspect of the present application, the content of which is incorporated herein and will not be repeated here.

[0280] Embodiments of the eighth aspect

[0281] An embodiment of the present application provides a terminal device.

[0282] Figure 9 is a schematic diagram of the structure of a terminal device according to an embodiment of the present application, which may be a remote terminal device. As shown in Figure 9, terminal device 900 may include a processor 901 and a memory 902. Memory 902 stores data and programs and is coupled to processor 901. 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.

[0283] For example, the processor 901 may be configured to execute a program to implement the method for sending uplink data as described in the embodiment of the first aspect. For example, the processor 901 may be configured to perform the following operations: for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, determining that the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information about unused CG PUSCH transmission occasions (UTO) of the physical uplink shared channel of the configured grant; and using the available configured uplink grant to send uplink data to a network device.

[0284] For another example, the processor 901 may be configured to execute a program to implement the data processing method as described in the embodiment of the second aspect. For example, the processor 901 may be configured to perform the following operations: for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, determine whether the configured uplink grant will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information about unused CG PUSCH transmission occasions (UTO) of the configured grant.

[0285] As shown in Figure 9 , the terminal device 900 may further include: a communication module 903, an input unit 904, a display 905, and a power supply 906. 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 900 does not necessarily include all of the components shown in Figure 9 , and these components are not essential. Furthermore, the terminal device 900 may also include components not shown in Figure 9 , for which reference may be made to related art.

[0286] An embodiment of the present application provides a network device, which may be, for example, a base station, but the present application is not limited thereto and may also be other network devices.

[0287] Figure 10 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 10 , network device 1000 may include a processor 1010 (e.g., a central processing unit (CPU)) and a memory 1020; memory 1020 is coupled to processor 1010. Memory 1020 may store various data and may also store an information processing program 1030, which is executed under the control of processor 1010.

[0288] For example, the processor 1010 may be configured to execute a program to implement the method for receiving uplink data as described in the embodiment of the second aspect. For example, the processor 1010 may be configured to perform the following control: receiving uplink data sent by a terminal device using a configured uplink grant; wherein the configured uplink grant is configured with information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or to be used for a configured uplink grant sent on a physical uplink shared channel (PUSCH); the first information includes information on unused CG PUSCH transmission occasions (UTO).

[0289] In addition, as shown in FIG10 , the network device 1000 may further include: a transceiver 1040 and an antenna 1050; wherein, the functions of the above components are similar to those in the prior art and are not described in detail here. It is worth noting that the network device 1000 does not necessarily include all the components shown in FIG10 ; in addition, the network device 1000 may also include components not shown in FIG10 , and reference may be made to the prior art for details.

[0290] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a terminal device, the program enables the computer to execute the uplink data sending method described in the embodiment of the first aspect of the present application and / or the data processing method described in the embodiment of the second aspect of the present application in the terminal device.

[0291] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the uplink data sending method described in the embodiment of the first aspect of the present application and / or the data processing method described in the embodiment of the second aspect of the present application in a terminal device.

[0292] An embodiment of the present application also provides a computer-readable program, wherein when the program is executed in a network device, the program enables a computer to execute the uplink data receiving method described in the embodiment of the second aspect of the present application in the network device.

[0293] An embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the uplink data receiving method described in the embodiment of the second aspect of the present application in a network device.

[0294] 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.

[0295] The method / apparatus 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 correspond to the various steps shown in the figure, respectively. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0296] 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.

[0297] One or more of the functional blocks described in the drawings and / or one or more combinations of functional blocks may be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described in the present application. One or more of the functional blocks described in the drawings and / or one or more combinations of functional blocks 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.

[0298] 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.

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

[0300] 1. A method for transmitting uplink data, applied to a terminal device, the method comprising:

[0301] determining, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission, wherein the first information includes information of unused CG PUSCH transmission occasions (UTOs) of the configured grant;

[0302] Uplink data is sent to the network device using the available configured uplink grant.

[0303] 2. The method according to Note 1, wherein sending uplink data to the network device using the available configured uplink grant comprises:

[0304] Use available configured uplink grants to send new transmissions and / or retransmissions of uplink data to the network device.

[0305] 3. The method according to Note 1, wherein the configuration authorization includes type 1 (Type 1) configuration authorization and / or type 2 (Type 2) configuration authorization.

[0306] 4. The method according to Supplement 1, wherein:

[0307] The terminal device supports UTO-UCI reporting, and the terminal device determines whether the configured uplink grant is available or will be used for PUSCH transmission.

[0308] 5. A method for receiving uplink data, applied to a network device, the method comprising:

[0309] Receiving uplink data sent by the terminal device using the configured uplink authorization;

[0310] The configured uplink grant configures information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or to be used for the configured uplink grant sent by the physical uplink shared channel (PUSCH); the first information includes information on unused CG PUSCH transmission occasions (UTO) of the configured uplink grant.

[0311] 6. A data processing method, applied to a terminal device, comprising:

[0312] determining, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is to be used for physical uplink shared channel (PUSCH) transmission, wherein the first information includes information of unused CG PUSCH transmission occasions (UTOs) of the configured grant;

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

[0314] The terminal device supports UTO-UCI reporting, and the terminal device determines whether the configured uplink grant will be used for PUSCH transmission.

[0315] 8. A data processing method, applied to a terminal device, comprising:

[0316] When the terminal device supports reporting of uplink control information (UCI) that provides first information, determine whether the configured uplink authorization is available for use or whether the configured uplink authorization will be used for physical uplink shared channel (PUSCH) transmission; the first information includes information on unused CG PUSCH transmission occasions (UTO) of the physical uplink shared channel of the configured authorization.

Claims

1. A device for transmitting uplink data, configured in a terminal device, comprising: a first determining unit configured to determine, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, whether the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission, wherein the first information includes information of unused CG PUSCH transmission occasions (UTO) of the configured grant; A first sending unit is configured to send uplink data to a network device using the available configured uplink grant.

2. The device according to claim 1, wherein The information related to the uplink control information (UTO-UCI) providing the first information is configured through RRC signaling.

3. The device according to claim 2, wherein The information (UTO-UCI) related to uplink control information (UCI) providing the first information includes: The configuration of the parameter uto-UCI-Config; or Configuration of the parameter nrofBitsInUTO-UCI and the configuration of the parameter betaOffsetUTO-UCI.

4. The device according to claim 1, wherein Each configured uplink grant configured for the terminal device is respectively configured or not configured with information related to uplink control information (UTO-UCI) providing the first information.

5. The device according to claim 1, wherein The first determining unit is further configured to: If the configured uplink grant is associated with a multi-PUSCH configured grant, the configured uplink grant has not been indicated to lower layers as unused for PUSCH transmission, and the configured uplink grant satisfies relevant validity conditions specified by the physical layer, the configured uplink grant is considered available; and / or If the configured uplink grant is not associated with a multi-PUSCH configured grant and the configured uplink grant has not been indicated to lower layers as unused for PUSCH transmission, the configured uplink grant is considered available.

6. The device according to claim 1, wherein The device further comprises: The second determining unit is configured to determine whether the configured uplink authorization is configured with the uplink authorization for providing the first information. Information related to control information (UTO-UCI).

7. The device according to claim 6, wherein The configured uplink grant determined by the lower layer or the RRC layer is configured with information related to uplink control information (UTO-UCI) providing the first information.

8. The device according to claim 6, wherein The configured uplink grant determined by the MAC entity is configured with information related to uplink control information (UTO-UCI) providing the first information.

9. The device according to claim 1, wherein The device further comprises: The third determining unit is configured to determine that the configured uplink grant is not configured with information related to uplink control information (UTO-UCI) providing the first information.

10. The device according to claim 9, wherein The first determining unit is further configured to: In a case where it is determined that the configured uplink grant is not configured with information related to uplink control information (UTO-UCI) providing the first information, it is considered that the configured uplink grant is available.

11. The device according to claim 1, wherein For each service cell and each configured uplink authorization, when the configured uplink authorization is configured and activated, if the configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing first information and is available, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

12. The device according to claim 1, wherein For each service cell and each configured uplink authorization, if the configured uplink authorization is not configured with information related to the uplink control information (UTO-UCI) providing the first information, when the configured uplink authorization is configured and activated, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization.

13. The device according to claim 1, wherein For each service cell and each configured uplink authorization, if the configured uplink authorization is configured with information related to uplink control information (UTO-UCI) providing first information, the MAC entity of the terminal device generates an uplink transmission for the configured uplink authorization when the configured uplink authorization is configured, activated and available.

14. The device according to claim 1, wherein The MAC entity of the terminal device determines whether the configured uplink authorization configured with information related to uplink control information (UTO-UCI) providing first information will be used for uplink transmission, and indicates the determination result to the physical layer, and the determination result is used for the physical layer of the terminal device to report the uplink control information providing first information.

15. The device according to claim 14, wherein The device further comprises: The second sending unit is configured to report the uplink control information providing the first information to the network device.

16. The device according to claim 1, wherein The RRC layer of the terminal device configures the MAC entity with information related to uplink control information (UCI) providing first information for at least one configured uplink authorization.

17. The device according to claim 1, wherein The device further comprises: The third sending unit is configured to report UE capability information to the network device, where the UE capability information includes indication information indicating whether UTO-UCI reporting is supported.

18. The device according to claim 17, wherein The indication information includes the cg-PUSCH-UTO-UCI-Ind-r18 parameter.

19. A device for receiving uplink data, configured in a network device, the device comprising: A first receiving unit, configured to receive uplink data sent by a terminal device using a configured uplink grant; The configured uplink grant is configured with information related to uplink control information (UCI) providing first information, and is determined by the terminal device to be available or whether the configured uplink grant will be used for a configured uplink grant sent by a physical uplink shared channel (PUSCH); the first information includes information on unused configured grant physical uplink shared channel transmission occasions (UTO).

20. A communication system, wherein: The communication system comprises: A terminal device, for a configured uplink grant configured with information related to uplink control information (UCI) providing first information, determining whether the configured uplink grant is available for use or will be used for physical uplink shared channel (PUSCH) transmission, wherein the first information includes information of unused CG PUSCH transmission occasions (UTO); and sending uplink data to a network device using the available configured uplink grant; A network device receives the uplink data sent by the terminal device.

Images