WO2021031778A1 - Procédé de transmission, et procédé et dispositif de configuration de pucch - Google Patents

Procédé de transmission, et procédé et dispositif de configuration de pucch Download PDF

Info

Publication number
WO2021031778A1
WO2021031778A1 PCT/CN2020/103526 CN2020103526W WO2021031778A1 WO 2021031778 A1 WO2021031778 A1 WO 2021031778A1 CN 2020103526 W CN2020103526 W CN 2020103526W WO 2021031778 A1 WO2021031778 A1 WO 2021031778A1
Authority
WO
WIPO (PCT)
Prior art keywords
pucch
configuration information
version
priority
rel
Prior art date
Application number
PCT/CN2020/103526
Other languages
English (en)
Chinese (zh)
Inventor
鲁智
潘学明
李娜
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Publication of WO2021031778A1 publication Critical patent/WO2021031778A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H04W72/044—Wireless resource allocation based on the type of the allocated resource
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria

Definitions

  • the embodiments of the present disclosure relate to the field of communication technologies, and in particular to a transmission method, a method and a device for configuring a physical uplink control channel (PUCCH).
  • PUCCH physical uplink control channel
  • 5G fifth generation
  • the main scenarios of 5G include mobile broadband enhancement (Enhance Mobile Broadband, eMBB), Ultra-Reliable and Low Latency Communications (URLLC), and Massive Machine Type Communication (mMTC). These scenarios The system puts forward requirements for high reliability, low delay, large bandwidth, and wide coverage.
  • eMBB enhanced Mobile Broadband
  • URLLC Ultra-Reliable and Low Latency Communications
  • mMTC Massive Machine Type Communication
  • PDSCH Physical Downlink shared channel
  • PUSCH Physical uplink shared channel
  • PUCCH Physical Uplink Control Channel
  • embodiments of the present disclosure provide a transmission method applied to a terminal, including:
  • the information carried by the PUCCH is transmitted.
  • the embodiments of the present disclosure also provide a method for configuring PUCCH, which is applied to the network side, and includes:
  • Configure PUCCH configuration information where the configuration information indicates the priority of the PUCCH.
  • embodiments of the present disclosure also provide a terminal, including:
  • a determining module configured to determine the priority of the PUCCH according to the configuration information of the PUCCH
  • the transmission module is configured to transmit the information carried by the PUCCH according to the priority of the PUCCH.
  • the configuration module is used to configure PUCCH configuration information, where the configuration information indicates the priority of the PUCCH.
  • the embodiments of the present disclosure also provide a terminal, including: a processor, a memory, and a program stored on the memory and capable of running on the processor, which is implemented when the program is executed by the processor The steps of the transmission method as described above.
  • the embodiments of the present disclosure also provide a network device, including: a processor, a memory, and a program stored on the memory and capable of running on the processor.
  • a network device including: a processor, a memory, and a program stored on the memory and capable of running on the processor.
  • the program is executed by the processor, The steps of the method for configuring PUCCH as described above are implemented.
  • the embodiments of the present disclosure also provide a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, the method for configuring PUCCH as described above is implemented. Steps, or, the steps of the transmission method as described above.
  • the PUCCH configuration information can be used to determine the priority of the PUCCH, when multiple PUCCH time domain resources conflict, the high priority PUCCH can be used for transmission, which can solve the problem of PUCCH transmission of multiple services.
  • the problem of priority determination can meet the requirements of high-reliability service transmission.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to an embodiment of the disclosure
  • FIG. 2 is a flowchart of a method for configuring PUCCH in an embodiment of the disclosure
  • FIG. 3 is one of the flowcharts of the transmission method in the embodiment of the disclosure.
  • FIG. 4 is one of the schematic diagrams of the network device of the embodiment of the disclosure.
  • FIG. 5 is one of schematic diagrams of a terminal according to an embodiment of the disclosure.
  • FIG. 6 is a second schematic diagram of a network device according to an embodiment of the disclosure.
  • FIG. 7 is a second schematic diagram of a terminal according to an embodiment of the disclosure.
  • FIG. 8 is the second flowchart of the transmission method in the embodiment of the disclosure.
  • LTE Long Time Evolution
  • LTE-A Long Time Evolution
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single Carrier Frequency Division multiple access
  • the terms “system” and “network” are often used interchangeably.
  • the CDMA system can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA).
  • UTRA includes Wideband Code Division Multiple Access (WCDMA) and other CDMA variants.
  • the TDMA system can implement radio technologies such as the Global System for Mobile Communication (GSM).
  • OFDMA system can realize such as Ultra Mobile Broadband (UMB), Evolved UTRA (Evolution-UTRA, E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, etc. Radio technology.
  • UMB Ultra Mobile Broadband
  • Evolution-UTRA Evolved UTRA
  • E-UTRA IEEE 802.11
  • WiMAX IEEE 802.16
  • IEEE 802.20 Flash-OFDM
  • Flash-OFDM Flash-OFDM
  • FIG. 1 it is a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system may include: a network device 11 and a terminal 12.
  • the terminal 12 may be denoted as a UE 12, and the terminal 12 may communicate with the network device 11 (transmit signaling or data).
  • the connection between the above-mentioned various devices may be a wireless connection.
  • a solid line is shown in FIG. 1.
  • the network device 11 provided by the embodiment of the present disclosure may be a base station, which may be a commonly used base station, an evolved node base station (eNB), or a network device in a 5G system (for example, the following Equipment such as next generation node base station (gNB) or transmission and reception point (TRP)).
  • eNB evolved node base station
  • 5G system for example, the following Equipment such as next generation node base station (gNB) or transmission and reception point (TRP)).
  • gNB next generation node base station
  • TRP transmission and reception point
  • an embodiment of the present disclosure provides a method for configuring PUCCH.
  • the execution subject of the method may be a network device, such as a base station.
  • the method includes: step 201.
  • Step 201 Configure PUCCH configuration information, where the configuration information indicates (for example, implicitly indicates) the priority of the PUCCH.
  • the PUCCH configuration information is sent to the terminal through radio resource control (Radio Resource Control, RRC) signaling.
  • RRC Radio Resource Control
  • the configuration information includes one or more of the following: (1) configuration information of the first version; (2) configuration information of the second version; wherein the priority of the configuration information of the second version is higher than that of the first version
  • the priority of the information the priority of the PUCCH configured by the configuration information of the second version is higher than the priority of the PUCCH configured by the configuration information of the first version.
  • the version number of the second version is higher than the version number of the first version.
  • the above version can be understood as the version of the communication system, such as version 15 (Release 15, Rel-15), Rel-16, etc.
  • the configuration information of the first version includes: multi-CSI-PUCCH-ResourceList; the configuration information of the second version does not include: multi-CSI-PUCCH- ResourceList. That is, through the multi-CSI-PUCCH-ResourceList, it can be determined whether the version of the configuration information is the first version or the second version.
  • the configuration information of the first version and the configuration information of the second version further include: a scheduling request resource configuration (SchedulingRequestResourceConfig) parameter.
  • the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the second version is higher than the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the first version.
  • the maximum number of scheduling requests SR configured by the configuration information of the first version and/or the configuration information of the second version is configured.
  • the time slot granularity includes from the beginning of a time slot to the end of a time slot.
  • the configuration information is at least one of the following: PUCCH configuration information element (PUCCH-config IE); scheduling request resource configuration information element (SchedulingRequestResourceConfig IE).
  • SR configuration 1 belongs to the SchedulingRequestResourceConfig IE configuration of Rel-15 version
  • SR configuration 2 belongs to the SchedulingRequestResourceConfig IE configuration of Rel-16 version
  • the priority of SR configuration 1 is lower than the priority of SR configuration 2.
  • an embodiment of the present disclosure also provides a transmission method.
  • the execution subject of the method is a terminal.
  • the method may include: step 301 and step 302.
  • Step 301 Determine the priority of the PUCCH according to the configuration information of the PUCCH;
  • the method may further include: receiving the PUCCH configuration information configured by the network side.
  • the PUCCH configuration information is received through RRC signaling.
  • the configuration information of the first version is the configuration information of the Rel-15 version
  • the configuration information of the second version is the configuration information of the Rel-16 version.
  • the configuration information of the Rel-16 version has a higher priority than the Rel-15 version.
  • the priority of the configuration information in the Rel-16 version is higher than the priority of the PUCCH configured in the Rel-15 version.
  • Step 302 According to the priority of the PUCCH, transmit the information carried by the PUCCH.
  • the information carried by the PUCCH with high priority is transmitted, the information carried by the low priority PUCCH is discarded, or the information carried by the low priority PUCCH is multiplexed Transfer to the high priority PUCCH.
  • the configuration information of the first version includes: multi-CSI-PUCCH-ResourceList; the configuration information of the second version does not include: multi-CSI-PUCCH- ResourceList. That is, through the multi-CSI-PUCCH-ResourceList, it can be determined whether the version of the configuration information is the first version or the second version.
  • the configuration information of the first version and the configuration information of the second version further include: a scheduling request resource configuration (SchedulingRequestResourceConfig) parameter.
  • the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the second version is higher than the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the first version.
  • the maximum number of scheduling requests SR configured by the configuration information of the first version and/or the configuration information of the second version is configured by the network side or agreed upon by a protocol.
  • the configuration information is at least one of the following: PUCCH configuration information element (PUCCH-config IE); scheduling request resource configuration information element (SchedulingRequestResourceConfig IE).
  • the priority of the SR configuration 1 is lower than the priority of the SR configuration 2.
  • an embodiment of the present disclosure also provides a transmission method, and the specific steps are as follows:
  • Step 802 The terminal determines the priority of the PUCCH according to the configuration information of the PUCCH;
  • Example 1 the configuration methods of configuration information of different versions are introduced.
  • the sequence of the configuration information may also include: Rel-15 version of the scheduling request resource release list (schedulingRequestResourceToReleaseList), the sequence of this list can configure the resource size N of the Rel-15 version of the scheduling request resource configuration, and the specific size can be configured as 1 ⁇
  • the maximum number of scheduling request resources supported by Rel-15 (schedulingRequestResourceToAddModList-r15 SEQUENCE(SIZE(1..maxNrofSR-Resources-r15)) OF SchedulingRequestResourceConfig-r15 OPTIONAL,--Need N);
  • SchedulingRequestConfig-r15 represents the configuration information of the PUCCH version of Rel-15.
  • the sequence of the configuration information includes: the scheduling request add modification list of the Rel-15 version (schedulingRequestToAddModList), and the sequence of this list can configure the Rel-15 version of scheduling
  • the number of requests for each cell group configuration N the specific size can be configured from 1 to the maximum supported by Rel-15 version.
  • the number of scheduling requests per cell group configuration (schedulingRequestToAddModList-r15 SEQUENCE(SIZE(1..maxNrofSR-ConfigPerCellGroup-r15) )) OF SchedulingRequestToAddMod-r15 OPTIONAL,--Need N);
  • the sequence of the configuration information may also include: Rel-15 version of the scheduling request release list (schedulingRequestToReleaseList), the sequence of this list can configure the number N of each cell group configuration of the Rel-15 version of the scheduling request, and the specific size can be configured
  • the maximum number of scheduling requests per cell group configuration supported by version 1 to Rel-15 (schedulingRequestToReleaseList-r15 SEQUENCE(SIZE(1..maxNrofSR-ConfigPerCellGroup-r15)) OF SchedulingRequestId-r15 OPTIONAL--Need N);
  • the above-mentioned SchedulingRequestConfig-r15 represents the configuration information of the PUCCH version of Rel-15.
  • the sequence of the configuration information includes: Rel-15 version of the scheduling request resource identifier (schedulingRequestResourceId-r15), Rel-15 version of the scheduling request identifier (schedulingResourceId) -r15), the period and offset of Rel-15 (periodicityAndOffset-r15) and the resource of Rel-15 (resource-r15), where the resource of Rel-15 can be configured as the PUCCH resource identifier of Rel-15 ( PUCCH-ResourceId-r15).
  • SchedulingRequestId-r15:: INTEGER(0..7)
  • the value of the Rel-15 version of the scheduling request identifier can be configured as (0..7).
  • schedulingRequestResourceToAddModList-r16 SEQUENCE(SIZE(1..maxNrofSR-Resources-r16))OF
  • schedulingRequestResourceToReleaseList-r16 SEQUENCE(SIZE(1..maxNrofSR-Resources-r16))OF
  • the above PUCCH-Config-r16 represents the configuration information of the PUCCH version of Rel-16.
  • the sequence of the configuration information includes: Rel-16 version of the scheduling request resource addition modification list (schedulingRequestResourceToAddModList).
  • the sequence of this list can be configured with Rel-
  • the resource size N of the 16 version scheduling request resource configuration can be configured from 1 to the maximum number of scheduling request resources supported by the Rel-16 version (schedulingRequestResourceToAddModList-r16 SEQUENCE(SIZE(1..maxNrofSR-Resources-r16))OFSchedulingRequestResourceConfig- r16 OPTIONAL,--Need N);
  • the sequence of configuration information may also include: Rel-16 version of scheduling request resource release list (schedulingRequestResourceToReleaseList), the sequence of this list can configure the resource size N of Rel-16 version of scheduling request resource configuration, and the specific size can be configured as 1 ⁇
  • the maximum number of scheduling request resources supported by Rel-16 (schedulingRequestResourceToAddModList-r16SEQUENCE(SIZE(1..maxNrofSR-Resources-r15))OFSchedulingRequestResourceConfig-r16OPTIONAL,--NeedN).
  • SchedulingRequestConfig-r16 represents the configuration information of the Rel-16 version of PUCCH.
  • the sequence of the configuration information includes: the Rel-16 version of the scheduling request add modification list (schedulingRequestToAddModList).
  • the sequence of the list can be configured with the Rel-16 version
  • the number of scheduling requests per cell group configuration N, the specific size can be configured from 1 to the maximum number of scheduling requests per cell group configuration supported by Rel-16 (schedulingRequestToAddModList-r16 SEQUENCE(SIZE(1..maxNrofSR-ConfigPerCellGroup- r16)) OF SchedulingRequestToAddMod-r16 OPTIONAL,--Need N);
  • the sequence of the configuration information may also include: Rel-16 version of the scheduling request release list (schedulingRequestToReleaseList), the sequence of the list can configure the number of Rel-16 version of scheduling request per cell group configuration N, the specific size can be configured The maximum number of scheduling requests per cell group configuration supported by version 1 to Rel-16 (schedulingRequestToReleaseList-r16 SEQUENCE(SIZE(1..maxNrofSR-ConfigPerCellGroup-r16)) OF SchedulingRequestId-r16 OPTIONAL--Need N);
  • the sequence of the configuration information may also include: Rel-16 version of SchedulingRequestToAddMod (SchedulingRequestToAddMod), and the parameter sequence includes: Rel-16 version of scheduling request identifier (schedulingRequestId-r16), Rel-16 version The scheduling request timer (sr-ProhibitTimer-r16) and the Rel-16 version of the scheduling request maximum transmission number (sr-TransMax-r15), of which,
  • the duration of the scheduling request timer of the Rel-16 version can be configured as ⁇ 1 millisecond (ms), 2ms, 4ms, 8ms, 16ms, 32ms, 64ms, 128ms ⁇ ;
  • the maximum number of transmissions of scheduling requests in the Rel-16 version can be configured as ⁇ n4, n8, n16, n32, n64, spare3, spare2, spare1 ⁇ .
  • the above-mentioned SchedulingRequestResourceConfig-r16 represents the configuration information of the PUCCH version of Rel-16.
  • the sequence of the configuration information includes: the scheduling request resource identifier (schedulingRequestResourceId-r16) of the Rel-16 version and the scheduling request identifier (schedulingResourceId-r16) of the Rel-16 version. -r16), Rel-16 version period and offset (periodicityAndOffset-r16) and Rel-16 version resources (resource-r16), where Rel-16 version resources can be configured as Rel-16 version PUCCH resource identifier ( PUCCH-ResourceId-r16).
  • SchedulingRequestId-r16:: INTEGER(0..7)
  • the value of the Rel-16 version of the scheduling request identifier can be configured as (0..7)
  • the number of the largest configured SRs may be limited.
  • the maximum number of configured SRs is 8.
  • the maximum number of SRs configured by the configuration information of each version may be configured by the network side or agreed by a protocol, for example, pre-configured.
  • the total number of SRs configured for a terminal may be configured by the network side or agreed by a protocol.
  • the maximum number of SRs can be 8.
  • the maximum number of SRs that can be configured is 8.
  • the number of SRs configured for the configuration information of the Rel-15 version may be a
  • SchedulingRequestId–r15:: INTEGER(0..maxnumberofSR-R15)
  • SchedulingRequestId–r16:: INTEGER(maxnumberofSR-R15+1..maxnumberofSR-R16)
  • the SR resource ID is configured using a similar mechanism, as follows:
  • SchedulingRequestResourceId-15:: INTEGER(1..maxNrofSR-Resources-R15)
  • the granularity of the PUCCH resource configured by the PUCCH-config IE of the first version is a slot.
  • the granularity of the PUCCH resource configured by the PUCCH-config IE of the second version can be either a slot or a sub-slot.
  • PUCCH resources may be configured to the default slot granularity.
  • Slot granularity can be defined as its duration (duration) spanning multiple sub-slots.
  • the embodiment of the present disclosure also provides a network device. Since the principle of the network device to solve the problem is similar to that of configuring the PUCCH in the embodiment of the present disclosure, the implementation of the network device can refer to the implementation of the method, and the repetition will not be repeated.
  • an embodiment of the present disclosure provides a network device, and the network device 400 includes:
  • the configuration module 401 is configured to configure PUCCH configuration information, where the configuration information indicates the priority of the PUCCH.
  • the configuration information includes one or more of the following: (1) configuration information of the first version; (2) configuration information of the second version; wherein the priority of the configuration information of the second version is higher than that of the first version.
  • Priority of the configuration information of the first version the priority of the PUCCH configured by the configuration information of the second version is higher than the priority of the PUCCH configured by the configuration information of the first version.
  • the version number of the second version is higher than the version number of the first version.
  • the above version can be understood as the version of the communication system, such as Rel-1515, Rel-16, etc.
  • the configuration information of the first version is the configuration information of the Rel-15 version
  • the configuration information of the second version is the configuration information of the Rel-16 version.
  • the configuration information of the Rel-16 version has a higher priority than the Rel-15 version.
  • the priority of the configuration information in the Rel-16 version is higher than the priority of the PUCCH configured in the Rel-15 version.
  • configuration information of Rel-15 version can be used by terminals of Rel-16 version, while the configuration information of Rel-16 version cannot be used by terminals of Rel-15 version.
  • the configuration information of the first version includes: multi-CSI-PUCCH-ResourceList; the configuration information of the second version does not include: multi-CSI-PUCCH-ResourceList. That is, through the multi-CSI-PUCCH-ResourceList, it can be determined whether the version of the configuration information is the first version or the second version.
  • the configuration information of the first version and the configuration information of the second version further include: a SchedulingRequestResourceConfig parameter.
  • the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the second version is higher than the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the first version.
  • the maximum number of scheduling requests SR configured by the configuration information of the first version and/or the configuration information of the second version is configured by the network side or agreed upon by a protocol.
  • the granularity of the PUCCH resource configured by the configuration information of the first version is a time slot; and/or the granularity of the PUCCH resource configured by the configuration information of the second version includes a time slot and/or sub-time Gap.
  • the configuration information is at least one of the following: PUCCH-config IE; SchedulingRequestResourceConfig IE.
  • SR configuration 1 belongs to the SchedulingRequestResourceConfig IE configuration of Rel-15 version
  • SR configuration 2 belongs to the SchedulingRequestResourceConfig IE configuration of Rel-16 version
  • the priority of SR configuration 1 is lower than the priority of SR configuration 2.
  • the network device provided in the embodiment of the present disclosure can execute the embodiment shown in FIG. 2 above, and its implementation principles and technical effects are similar, and details are not described herein again in this embodiment.
  • the embodiment of the present disclosure also provides a terminal. Since the principle of the terminal to solve the problem is similar to the transmission method in the embodiment of the present disclosure, the implementation of the terminal can refer to the implementation of the method, and the repetition will not be repeated.
  • an embodiment of the present disclosure provides a terminal, and the terminal 500 includes:
  • the determining module 501 is configured to determine the priority of the PUCCH according to the configuration information of the PUCCH;
  • the transmission module 502 is configured to transmit the information carried by the PUCCH according to the priority of the PUCCH.
  • the transmission module 502 is further configured to: when multiple PUCCH time domain resources conflict, transmit the information carried by the PUCCH with high priority, discard the information carried by the low priority PUCCH, or set the low priority The information carried by the first-level PUCCH is multiplexed onto the high-priority PUCCH for transmission.
  • the terminal 500 further includes: a receiving module configured to receive the PUCCH configuration information configured on the network side.
  • the determining module 501 is further configured to determine the priority of the PUCCH according to the priority of the configuration information of the PUCCH.
  • the configuration information includes one or more of the following: (1) configuration information of the first version; (2) configuration information of the second version; wherein the priority of the configuration information of the second version is higher than that of the first version.
  • Priority of the configuration information of the first version the priority of the PUCCH configured by the configuration information of the second version is higher than the priority of the PUCCH configured by the configuration information of the first version.
  • the version number of the second version is higher than the version number of the first version.
  • the above version can be understood as the version of the communication system, such as Rel-15, Rel-16, etc.
  • the configuration information of the first version is the configuration information of the Rel-15 version
  • the configuration information of the second version is the configuration information of the Rel-16 version.
  • the configuration information of the Rel-16 version has a higher priority than the Rel-15 version.
  • the priority of the configuration information in the Rel-16 version is higher than the priority of the PUCCH configured in the Rel-15 version.
  • configuration information of Rel-15 version can be used by terminals of Rel-16 version, while the configuration information of Rel-16 version cannot be used by terminals of Rel-15 version.
  • the configuration information of the first version includes: multi-CSI-PUCCH-ResourceList; the configuration information of the second version does not include: multi-CSI-PUCCH-ResourceList. That is, through the multi-CSI-PUCCH-ResourceList, it can be determined whether the version of the configuration information is the first version or the second version.
  • the configuration information of the first version and the configuration information of the second version further include: a SchedulingRequestResourceConfig parameter.
  • the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the second version is higher than the priority of the SchedulingRequestResourceConfig parameter in the configuration information of the first version.
  • the maximum number of scheduling requests SR configured by the configuration information of the first version and/or the configuration information of the second version is configured by the network side or agreed through a protocol.
  • the granularity of the PUCCH resource configured by the configuration information of the first version is a time slot; and/or the granularity of the PUCCH resource configured by the configuration information of the second version includes a time slot and/or sub-time Gap.
  • the configuration information is at least one of the following: PUCCH-config IE; SchedulingRequestResourceConfig IE.
  • SR configuration 1 belongs to the SchedulingRequestResourceConfig IE configuration of Rel-15 version
  • SR configuration 2 belongs to the SchedulingRequestResourceConfig IE configuration of Rel-16 version
  • the priority of SR configuration 1 is lower than the priority of SR configuration 2.
  • the terminal provided by the embodiment of the present disclosure may execute the embodiment shown in FIG. 3 above, and its implementation principles and technical effects are similar, and details are not described herein again in this embodiment.
  • FIG. 6 is a structural diagram of a network device applied in an embodiment of the present disclosure.
  • the network device 600 includes a processor 601, a transceiver 602, a memory 603, and a bus interface.
  • the processor 601 Can be responsible for managing the bus architecture and general processing.
  • the memory 603 may store data used by the processor 601 when performing operations.
  • the network device 600 further includes: a computer program that is stored in the memory 603 and can run on the processor 601, and the computer program is executed by the processor 601 to implement the steps in the method shown in FIG. 2 above .
  • the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 601 and various circuits of the memory represented by the memory 603 are linked together.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein.
  • the bus interface provides the interface.
  • the transceiver 602 may be a plurality of elements, that is, including a transmitter and a receiver, and provide a unit for communicating with various other devices on the transmission medium.
  • the network device provided in the embodiment of the present disclosure can execute the method embodiment shown in FIG. 2 above, and its implementation principles and technical effects are similar, and details are not described in this embodiment here.
  • the terminal 700 shown in FIG. 7 includes: at least one processor 701, a memory 702, at least one network interface 704, and a user interface 703.
  • the various components in the terminal 700 are coupled together through the bus system 705.
  • the bus system 705 is used to implement connection and communication between these components.
  • the bus system 705 also includes a power bus, a control bus, and a status signal bus.
  • various buses are marked as the bus system 705 in FIG. 7.
  • the user interface 703 may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball (trackball), a touch panel, or a touch screen).
  • a pointing device for example, a mouse, a trackball (trackball), a touch panel, or a touch screen.
  • the memory 702 in the embodiment of the present disclosure may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), and electrically available Erase programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • the volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache.
  • RAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous dynamic random access memory
  • SDRAM double data rate synchronous dynamic random access memory
  • Double Data rate SDRAM DDRSDRAM
  • enhanced SDRAM ESDRAM
  • Synchlink DRAM SLDRAM
  • Direct Rambus RAM DRRAM
  • the memory 702 of the system and method described in the embodiments of the present disclosure is intended to include, but is not limited to, these and any other suitable types of memory.
  • the memory 702 stores the following elements, executable modules or data structures, or a subset of them, or an extended set of them: the operating system 7021 and the application 7022.
  • the operating system 7021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., for implementing various basic services and processing hardware-based tasks.
  • the application program 7022 includes various application programs, such as a media player (Media Player), a browser (Browser), etc., which are used to implement various application services.
  • a program that implements the method of the embodiments of the present disclosure may be included in the application program 7022.
  • the terminal provided in the embodiment of the present disclosure can execute the method embodiment shown in FIG. 3, and its implementation principles and technical effects are similar, and details are not described herein again in this embodiment.
  • the steps of the method or algorithm described in conjunction with the disclosure of the present disclosure may be implemented in a hardware manner, or may be implemented in a manner in which a processor executes software instructions.
  • the software instructions can be composed of corresponding software modules.
  • the software modules can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, mobile hard disks, read-only optical disks, or any other form of storage media known in the art.
  • An exemplary storage medium is coupled to the processor, so that the processor can read information from the storage medium and can write information to the storage medium.
  • the storage medium may also be an integral part of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the ASIC may be located in the core network interface device.
  • the processor and the storage medium may also exist as discrete components in the core network interface device.
  • Computer readable media include computer storage media and communication media, where communication media includes any media that facilitates the transfer of computer programs from one place to another.
  • the storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer.
  • the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present disclosure may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present disclosure may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable data processing equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including the instruction device.
  • the device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, so as to execute on the computer or other programmable equipment.
  • the instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé de transmission, ainsi qu'un procédé et un dispositif de configuration d'un PUCCH. Le procédé consiste : à déterminer la priorité d'un PUCCH selon des informations de configuration du PUCCH ; et à transmettre, selon la priorité du PUCCH, des informations transportées par le PUCCH.
PCT/CN2020/103526 2019-08-16 2020-07-22 Procédé de transmission, et procédé et dispositif de configuration de pucch WO2021031778A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910759503.X 2019-08-16
CN201910759503.XA CN111836381B (zh) 2019-08-16 2019-08-16 传输方法、配置pucch的方法和设备

Publications (1)

Publication Number Publication Date
WO2021031778A1 true WO2021031778A1 (fr) 2021-02-25

Family

ID=72912075

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/103526 WO2021031778A1 (fr) 2019-08-16 2020-07-22 Procédé de transmission, et procédé et dispositif de configuration de pucch

Country Status (2)

Country Link
CN (1) CN111836381B (fr)
WO (1) WO2021031778A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108401485A (zh) * 2017-09-29 2018-08-14 北京小米移动软件有限公司 信号传输方法及装置
US20180368173A1 (en) * 2017-06-15 2018-12-20 Sharp Laboratories Of America, Inc. Systems and methods for an enhanced scheduling request for 5g nr
CN109156028A (zh) * 2018-08-06 2019-01-04 北京小米移动软件有限公司 上行消息传输方法、装置及存储介质
CN110691412A (zh) * 2018-07-04 2020-01-14 维沃移动通信有限公司 Pucch冲突的处理方法和终端

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101778419B (zh) * 2009-01-09 2012-10-17 华为技术有限公司 Pucch资源的配置、发送方法及其装置
CN103095394B (zh) * 2011-11-02 2017-09-29 中兴通讯股份有限公司 信道状态信息、肯定确认/否定确认信息反馈方法及装置
CN108306673B (zh) * 2012-04-27 2021-09-24 北京三星通信技术研究有限公司 一种harq-ack信息传输方法
WO2013166670A1 (fr) * 2012-05-09 2013-11-14 华为技术有限公司 Procédé et dispositif pour configurer les ressources d'un canal montant
CN103686858B (zh) * 2012-08-31 2018-02-06 华为技术有限公司 上行控制信息的反馈方法、基站及用户设备
US9876620B2 (en) * 2013-01-10 2018-01-23 Samsung Electronics Co., Ltd. Uplink control information transmissions/receptions in wireless networks
JP6721506B2 (ja) * 2013-12-18 2020-07-15 アイディーエーシー ホールディングス インコーポレイテッド 全二重無線システムにおける干渉管理のための方法、装置、およびシステム
CN104936300A (zh) * 2014-03-20 2015-09-23 中兴通讯股份有限公司 上行信道处理方法、终端、基站和系统
CN104661316A (zh) * 2015-01-28 2015-05-27 中兴通讯股份有限公司 一种载波聚合下调度请求的发送方法、装置和终端
CN106257856B (zh) * 2015-06-19 2021-02-02 北京三星通信技术研究有限公司 一种传输上行控制信息的方法
CN108282278B (zh) * 2017-01-05 2021-02-05 华为技术有限公司 传输数据的方法、终端设备和网络设备
CN108811099A (zh) * 2017-05-03 2018-11-13 华为技术有限公司 上行传输资源的调度方法和设备
US20200163079A1 (en) * 2017-07-27 2020-05-21 Lg Electronics Inc. Method for transmitting signal according to resource allocation priority, and terminal therefor
CN109392169B (zh) * 2017-08-04 2021-05-07 维沃移动通信有限公司 一种数据传输方法、终端及基站
CN109392126A (zh) * 2017-08-10 2019-02-26 华为技术有限公司 上行传输方法、终端设备和网络设备
WO2019075762A1 (fr) * 2017-10-20 2019-04-25 Oppo广东移动通信有限公司 Procédé de transmission de demande de programmation et dispositif terminal

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20180368173A1 (en) * 2017-06-15 2018-12-20 Sharp Laboratories Of America, Inc. Systems and methods for an enhanced scheduling request for 5g nr
CN108401485A (zh) * 2017-09-29 2018-08-14 北京小米移动软件有限公司 信号传输方法及装置
CN110691412A (zh) * 2018-07-04 2020-01-14 维沃移动通信有限公司 Pucch冲突的处理方法和终端
CN109156028A (zh) * 2018-08-06 2019-01-04 北京小米移动软件有限公司 上行消息传输方法、装置及存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
OPPO: "Summary on UCI enhancements for URLLC", 3GPP DRAFT; R1-1907754, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. Reno, USA; 20190513 - 20190517, 16 May 2019 (2019-05-16), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France, XP051740029 *

Also Published As

Publication number Publication date
CN111836381A (zh) 2020-10-27
CN111836381B (zh) 2023-09-08

Similar Documents

Publication Publication Date Title
US11082963B2 (en) Method, terminal device and network device for transmitting uplink control information
US10952207B2 (en) Method for transmitting data, terminal device and network device
US11601958B2 (en) Data transmission method and apparatus
WO2019201023A1 (fr) Procédé et dispositif de transmission de données
US11595964B2 (en) Method and device for determining information domain value in DCI
EP3618513B1 (fr) Procédé, dispositif et système de transmission de service
CN109565676B (zh) 用于配置半持久调度的方法和设备
WO2018202178A1 (fr) Procédé et dispositif de récupération de faisceau
WO2021139832A1 (fr) Procédé d'envoi de signal de sondage de référence srs et dispositif associé
CN110602769B (zh) 数据处理方法、用户设备和网络侧设备
WO2019028771A1 (fr) Dispositif terminal et procédé d'émission de données
WO2019137502A1 (fr) Procédé et dispositif de transmission d'uci
WO2017193827A1 (fr) Procédé et dispositif de traitement d'envoi de srs, ainsi que procédé, dispositif et système d'envoi
WO2012034527A1 (fr) Procédé et dispositif adaptés pour transmettre des srs non périodiques dans un système tdd
WO2019024713A1 (fr) Procédé de transmission de données, terminal et station de base
US11228933B2 (en) Method for transmitting information and terminal device
CN111953458B (zh) 一种pucch资源确定方法和通信设备
CN114287156A (zh) 资源请求的方法和通信装置
WO2021031778A1 (fr) Procédé de transmission, et procédé et dispositif de configuration de pucch
WO2020228631A1 (fr) Procédé et dispositif de traitement pour planification inter-créneaux
US20240057071A1 (en) Panel selection for uplink transmission
CN115499101A (zh) 处理方法及设备
RU2815922C1 (ru) Способ и устройство для указания луча и устройство связи
EP3986058A1 (fr) Procédé et dispositif d'envoi de pucch et de configuration d'informations
WO2020019322A1 (fr) Procédé et appareil de transmission d'informations

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20855493

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20855493

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 20855493

Country of ref document: EP

Kind code of ref document: A1