WO2022078321A1 - 上行信息发送方法及相关产品 - Google Patents

上行信息发送方法及相关产品 Download PDF

Info

Publication number
WO2022078321A1
WO2022078321A1 PCT/CN2021/123243 CN2021123243W WO2022078321A1 WO 2022078321 A1 WO2022078321 A1 WO 2022078321A1 CN 2021123243 W CN2021123243 W CN 2021123243W WO 2022078321 A1 WO2022078321 A1 WO 2022078321A1
Authority
WO
WIPO (PCT)
Prior art keywords
pusch
user equipment
pucch
memory
processor
Prior art date
Application number
PCT/CN2021/123243
Other languages
English (en)
French (fr)
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 WO2022078321A1 publication Critical patent/WO2022078321A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Definitions

  • the present application relates to the technical field of communication processing, and in particular, to a method for sending uplink information and related products.
  • the embodiments of the present application disclose an uplink information sending method and related products.
  • the PUSCH and the SR conflict the PUSCH is sent preferentially, thereby realizing the repeated sending of the PUSCH, improving the network performance and improving the user experience.
  • a first aspect provides a method for sending uplink information, the method is applied to MTC for machine type communication, and the method includes the following steps:
  • the user equipment UE preferentially transmits the PUSCH repeatedly.
  • a user equipment in a second aspect, includes:
  • the processing unit is used for the physical uplink control channel PUCCH of the resource scheduling request SR to collide with the physical uplink shared channel PUSCH, and the communication unit is preferentially controlled to repeatedly transmit the PUSCH.
  • a third aspect provides a terminal comprising a processor, a memory, a communication interface, and one or more programs, the one or more programs being stored in the memory and configured to be executed by the processor,
  • the program includes instructions for performing the steps in the method of the first aspect.
  • a computer-readable storage medium storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method of the first aspect.
  • a computer program product in a fifth aspect, includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute the first aspect of the embodiments of the present application. some or all of the steps described in .
  • the computer program product may be a software installation package.
  • a chip system in a sixth aspect, includes at least one processor, a memory and an interface circuit, the memory, the transceiver and the at least one processor are interconnected through a line, and the at least one memory stores There is a computer program; the computer program when executed by the processor implements the method of the first aspect.
  • the technical solution provided by the present application preferentially transmits the PUSCH when the PUCCH of the SR collides with the PUSCH, thereby ensuring the transmission of the PUSCH and improving the reliability of the network and the user experience.
  • the transmission of PUSCH is preferentially sent, so that the base station cannot decode the PUSCH due to the high SR priority and puncturing the PUSCH, thereby improving the stability and reliability of the network.
  • FIG. 1 is a system architecture diagram of an exemplary communication system provided by an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a method for sending uplink information provided by an embodiment of the present application
  • FIG. 3 is a schematic diagram of a resource timing relationship provided in Embodiment 1 of the present application.
  • FIG. 4 is a schematic diagram of another timing relationship of resources provided in Embodiment 1 of the present application.
  • FIG. 5 is a schematic structural diagram of a terminal provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an electronic device provided by an embodiment of the present application.
  • connection in the embodiments of the present application refers to various connection modes such as direct connection or indirect connection, so as to realize communication between devices, which is not limited in the embodiments of the present application.
  • the example communication system 100 may be, for example, a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system ) system, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) system, Advanced Long Term Evolution (Advanced long term evolution, LTE-A) system, New Radio (New Radio, NR) ) system, evolution system of NR system, LTE system on unlicensed spectrum (LTE-based access to unlicensed spectrum, LTE-U), NR system on unlicensed spectrum (NR-based access to unlicensed spectrum, NR-U), Universal Mobile Telecommunication System (UMTS), next-generation communication system or other communication systems, etc.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • LTE-A
  • the communication system in this embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, or a standalone (Standalone, SA) distribution. web scene.
  • Carrier Aggregation, CA Carrier Aggregation, CA
  • DC Dual Connectivity
  • SA standalone
  • the terminal 110 in this embodiment of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user device.
  • the terminal may also be a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a wireless communication function handheld devices, computing devices or other processing devices connected to wireless modems, relay devices, in-vehicle devices, wearable devices, terminals in future 5G networks or future evolution of public land mobile networks (PLMN)
  • SIP session initiation protocol
  • WLL wireless local loop
  • PDA personal digital assistant
  • PLMN public land mobile networks
  • the network device 120 in this embodiment of the present application may be a device for communicating with a terminal, and the network device may be an evolved base station (evoled NodeB, eNB or eNodeB) in an LTE system, or a cloud radio access network (cloud radio access network).
  • evoled NodeB evoled NodeB, eNB or eNodeB
  • cloud radio access network cloud radio access network
  • the network device can be a relay device, an access point, an in-vehicle device, a wearable device, and a network device in a future 5G network or a network in a future evolved PLMN network Equipment, one or a group (including multiple antenna panels) antenna panels of the base station in the 5G system, or, it can also be a network node that constitutes a gNB or a transmission point, such as a baseband unit (baseband unit, BBU), or, distributed A unit (distributed unit, DU), etc., is not limited in this embodiment of the present application.
  • a baseband unit baseband unit
  • BBU baseband unit
  • DU distributed A unit
  • a gNB may include a centralized unit (CU) and a DU.
  • the gNB may also include an active antenna unit (AAU).
  • the CU implements some functions of the gNB, and the DU implements some functions of the gNB.
  • the CU is responsible for processing non-real-time protocols and services, and implementing functions of radio resource control (RRC) and packet data convergence protocol (PDCP) layers.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the DU is responsible for processing physical layer protocols and real-time services, and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer.
  • RLC radio link control
  • MAC media access control
  • PHY physical
  • the transmission of the PUSCH will be interrupted, resulting in abnormal reception by the base station.
  • the SR is normally sent, if PUSCH is sent at this time, the PUSCH will be punctured due to the higher priority of the PUCCH.
  • FIG. 2 provides a method for sending uplink information.
  • the method is executed in the communication system as shown in FIG. 1, and the method is applied to MTC.
  • the method may include the following steps:
  • Step S200 if the PUCCH of the SR collides with the physical uplink shared channel PUSCH, the user equipment UE sends the PUSCH repeatedly in priority.
  • the PUSCH when the PUCCH of the SR collides with the PUSCH, the PUSCH is preferentially transmitted, thereby ensuring the transmission of the PUSCH, and improving the reliability of the network and the user experience.
  • the transmission of PUSCH is preferentially sent, so that the base station cannot decode the PUSCH due to the high SR priority and puncturing the PUSCH, thereby improving the stability and reliability of the network.
  • the method further includes:
  • the delay triggers the sending of the SR.
  • delayed triggering of SR transmission can trigger the transmission of SR in the time slot after the repeated transmission of PUSCH is completed, so that the repeated transmission of PUSCH will not fail due to SR transmission, and the stability of the network is improved.
  • the SR sending count is not increased, that is, the SR count is temporarily stopped, which can avoid the problem of SR reconstruction caused by too many SR counts.
  • FIG. 3 A schematic diagram of the resources after delayed sending is shown in FIG. 3 .
  • the method before the delay triggering the sending of the SR, the method further includes:
  • the PUSCH will continue to be sent preferentially.
  • PUSCH needs to be sent first, because if the PUSCH is not decoded correctly, even if the SR is sent successfully, the network performance of the base station will be affected, that is, the resource cannot be scheduled according to the SR, so the MTC needs to give priority to the PUSCH transmission.
  • the method further includes:
  • the delay time for delaying the triggering of the SR is determined according to the information of the PUCCH.
  • the PUCCH information includes one or any combination of the following: PUSCH repetition process and repetition times; SR repetition process and repetition times.
  • the delay triggering the sending of the SR specifically includes:
  • the first frame of the SR is the xth frame after the completion frame of the PUSCH, where x ⁇ 1 and x is an integer.
  • X is preferentially set to 1. This setting enables the SR to be sent directly after the PUSCH is sent, thereby reducing the advantage of network delay.
  • the method for determining the collision between the PUCCH of the SR and the PUSCH specifically includes:
  • the PUCCH and the PUSCH shown in FIG. 4 collide in some frames.
  • Embodiment 1 of the present application provides a method for sending uplink information.
  • the method is executed in the communication system shown in FIG. 1 .
  • the transmission of SR and PUSCH in this method is shown in FIG. 4 .
  • the method may include the following: if the SR The PUCCH collides with the PUSCH, and the user equipment UE preferentially transmits the PUSCH repeatedly, that is, delays the transmission of the SR. As shown in FIG. 3 , the SR may be delayed until the data frame transmission after the completion frame of the PUSCH.
  • FIG. 5 provides a user equipment UE.
  • the user equipment UE may include:
  • the processing unit is used for the physical uplink control channel PUCCH of the resource scheduling request SR to collide with the physical uplink shared channel PUSCH, and the communication unit is preferentially controlled to repeatedly transmit the PUSCH.
  • the PUSCH when the PUCCH of the SR collides with the PUSCH, the PUSCH is sent preferentially, thereby ensuring the sending of the PUSCH, and improving the reliability of the network and the user experience.
  • the transmission of PUSCH is preferentially sent, so that the base station cannot decode the PUSCH due to the high SR priority and puncturing the PUSCH, thereby improving the stability and reliability of the network.
  • the processing unit is further configured to delay the sending of the triggering SR.
  • delayed triggering of SR transmission can trigger the transmission of SR in the time slot after the repeated transmission of PUSCH is completed, so that the repeated transmission of PUSCH will not fail due to SR transmission, and the stability of the network is improved.
  • the SR sending count is not increased, that is, the SR count is temporarily stopped, which can avoid the problem of SR reconstruction caused by too many SR counts.
  • FIG. 3 A schematic diagram of the resources after delayed sending is shown in FIG. 3 .
  • the processing unit is further configured to continue to preferentially send the PUSCH if the PUSCH has not been sent yet.
  • PUSCH needs to be sent first, because if the PUSCH is not decoded correctly, even if the SR is sent successfully, the network performance of the base station will be affected, that is, the resource cannot be scheduled according to the SR, so the MTC needs to give priority to the PUSCH transmission.
  • the processing unit is further configured to determine the delay time for delaying the triggering of the SR according to the information of the PUCCH.
  • the PUCCH information includes one or any combination of the following: PUSCH repetition process and repetition times; SR repetition process and repetition times.
  • the processing unit is further configured to determine that the first frame of the SR is the xth frame after the completion frame of the PUSCH, where x ⁇ 1 and x is an integer.
  • X is preferentially set to 1. This setting enables the SR to be sent directly after the PUSCH is sent, thereby reducing the advantage of network delay.
  • the method for determining the collision between the PUCCH of the SR and the PUSCH specifically includes:
  • the user equipment includes corresponding hardware and/or software modules for executing each function.
  • the present application can be implemented in hardware or in the form of a combination of hardware and computer software in conjunction with the algorithm steps of each example described in conjunction with the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functionality for each particular application in conjunction with the embodiments, but such implementations should not be considered beyond the scope of this application.
  • the electronic device can be divided into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above-mentioned integrated modules can be implemented in the form of hardware. It should be noted that, the division of modules in this embodiment is schematic, and is only a logical function division, and there may be other division manners in actual implementation.
  • the user equipment may include a processing module, a storage module and a communication module.
  • the processing module may be used to control and manage the actions of the user equipment, for example, may be used to support the electronic equipment to perform the steps performed by the communication unit and the processing unit.
  • the storage module may be used to support the electronic device to execute stored program codes and data, and the like.
  • the communication module can be used to support the communication between the electronic device and other devices.
  • the processing module may be a processor or a controller. It may implement or execute the various exemplary logical blocks, modules and circuits described in connection with this disclosure.
  • the processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of digital signal processing (DSP) and a microprocessor, and the like.
  • the storage module may be a memory.
  • the communication module may specifically be a device that interacts with other electronic devices, such as a radio frequency circuit, a Bluetooth chip, and a Wi-Fi chip.
  • the interface connection relationship between the modules illustrated in the embodiments of the present application is only a schematic illustration, and does not constitute a structural limitation of the user equipment.
  • the user equipment may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.
  • FIG. 6 is an electronic device 60 provided by an embodiment of the present application.
  • the electronic device may be a terminal, and includes a processor 601, a memory 602, and a communication interface 603.
  • the processor 601, the memory 602, and the communication interface 603 are connected to each other through a bus.
  • the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM for short), programmable read-only memory (PROM for short), erasable programmable read-only memory (EPROM for short) , Electrically Erasable Programmable Read-Only Memory (electrically EPROM, EEPROM for short) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache.
  • RAM random access memory
  • SRAM static random access memory
  • DRAM dynamic random access memory
  • DRAM synchronous Dynamic random access memory
  • SDRAM synchronous Dynamic random access memory
  • DDR SDRAM double data rate synchronous dynamic random access memory
  • ESDRAM enhanced synchronous dynamic random access memory
  • SLDRAM Synchronous connection dynamic random access memory
  • DR RAM direct memory bus random access memory
  • the processor 601 may be one or more central processing units (central processing units, CPUs).
  • CPUs central processing units
  • the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 601 may include one or more processing units, for example, the processing unit may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor ( image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (neural-network processing unit, NPU), etc.
  • the processing unit may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor ( image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (neural-network processing unit, NPU), etc.
  • different processing units can be independent components, or can be integrated in one or more processors.
  • the user equipment may also include one or more processing units.
  • the controller can generate an operation control signal according to the instruction operation code and the timing signal
  • memory may also be provided in the processing unit for storing instructions and data.
  • the memory in the processing unit may be a cache memory. This memory can hold instructions or data that have just been used or recycled by the processing unit. If the processing unit needs to use the instruction or data again, it can be called directly from the memory. In this way, repeated access is avoided, and the waiting time of the processing unit is reduced, thereby improving the efficiency of the user equipment in processing data or executing instructions.
  • processor 601 may include one or more interfaces.
  • the interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transceiver (universal) asynchronous receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input/output (GPIO) interface, SIM card interface and/or USB interface, etc.
  • the USB interface is an interface that conforms to the USB standard specification, and can specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, and the like.
  • the USB interface can be used to connect a charger to charge the user equipment, and can also be used to transfer data between the user equipment and peripheral devices.
  • the USB port can also be used to connect headphones and play audio through the headphones.
  • the processor 601 in the electronic device 60 is configured to read the computer program code stored in the memory 602, and perform the following operations:
  • the PUSCH is preferentially transmitted repeatedly.
  • An embodiment of the present application further provides a chip system, the chip system includes at least one processor, a memory, and an interface circuit, the memory, the transceiver, and the at least one processor are interconnected by lines, and the at least one memory
  • a computer program is stored in the computer; when the computer program is executed by the processor, the method flow shown in FIG. 2 is realized.
  • Embodiments of the present application also provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when it runs on a network device, the method flow shown in FIG. 2 is implemented.
  • the embodiment of the present application further provides a computer program product, when the computer program product runs on the terminal, the method flow shown in FIG. 2 is realized.
  • Embodiments of the present application further provide a terminal, including a processor, a memory, a communication interface, and one or more programs, where the one or more programs are stored in the memory and configured to be executed by the processor , the program includes instructions for performing the steps in the method of the embodiment shown in FIG. 2 .
  • the electronic device includes corresponding hardware structures and/or software templates for executing each function.
  • the present application can be implemented in hardware or in the form of a combination of hardware and computer software, in combination with the units and algorithm steps of each example described in the embodiments provided herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of this application.
  • the electronic device may be divided into functional units according to the foregoing method examples.
  • each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units. It should be noted that the division of units in the embodiments of the present application is illustrative, and is only a logical function division, and other division methods may be used in actual implementation.
  • the disclosed apparatus may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the above-mentioned units is only a logical function division.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical or other forms.
  • the units described above as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.
  • the above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.
  • the above-mentioned integrated units if implemented in the form of software functional units and sold or used as independent products, may be stored in a computer-readable memory.
  • the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art, or all or part of the technical solution, and the computer software product is stored in a memory.
  • a computer device which may be a personal computer, a server, or a network device, etc.
  • the aforementioned memory includes: U disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), mobile hard disk, magnetic disk or optical disk and other media that can store program codes.

Landscapes

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

Abstract

本申请实施例提供一种上行信息发送方法及相关产品，所述方法应用于机器类通信MTC，所述方法包括如下步骤：若资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，用户设备UE优先对该PUSCH重复发送。本申请提供的技术方案具有网络性能好的优点。

Description

上行信息发送方法及相关产品 技术领域
本申请涉及通信处理技术领域，尤其涉及一种上行信息发送方法及相关产品。
背景技术
在MTC(Machine-Type Communication，机器类型通信)通信系统中，对于广覆盖、弱覆盖、快衰落等信道条件下，当终端规划PUSCH(physical uplink shared channel，物理上行共享信道)重复发送，又识别到存在新的数据触发SR(Resource scheduling request，资源调度请求)发送时，UE(User Equipment，用户设备)无法实现对PUSCH的重复发送，影响了网络性能。
发明内容
本申请实施例公开了一种上行信息发送方法及相关产品，其在PUSCH与SR发生冲突时，优先发送PUSCH，进而实现了对PUSCH的重复发送，提高了网络性能，提高了用户体验度。
第一方面，提供一种上行信息发送方法，所述方法应用于机器类通信MTC，所述方法包括如下步骤：
若资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，用户设备UE优先对该PUSCH重复发送。
第二方面，提供一种用户设备，所述UE包括：
处理单元，用于资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，优先控制通信单元对该PUSCH重复发送。
第三方面，提供一种终端，包括处理器、存储器、通信接口，以及一个或多个程序，所述一个或多个程序被存储在所述存储器中，并且被配置由所述处理器执行，所述程序包括用于执行第一方面所述的方法中的步骤的指令。
第四方面，提供了一种计算机可读存储介质，存储用于电子数据交换的计算机程序，其中，所述计算机程序使得计算机执行第一方面所述的方法。
第五方面，提供了一种计算机程序产品，其中，上述计算机程序产品包括 存储了计算机程序的非瞬时性计算机可读存储介质，上述计算机程序可操作来使计算机执行如本申请实施例第一方面中所描述的部分或全部步骤。该计算机程序产品可以为一个软件安装包。
第六方面，提供了芯片系统，所述芯片系统包括至少一个处理器，存储器和接口电路，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有计算机程序；所述计算机程序被所述处理器执行时实现第一方面所述的方法。
通过实施本申请实施例，本申请提供的技术方案在SR的PUCCH与PUSCH产生碰撞时，优先发送PUSCH，进而保证了PUSCH的发送，提高了网络的可靠性以及用户体验度。此方案在SR与PUSCH产生碰撞时，优先发送PUSCH的发送，这样不会因为SR优先级高而对PUSCH打孔导致基站无法解码PUSCH，进而提高网络的稳定性和可靠性。
附图说明
以下对本申请实施例用到的附图进行介绍。
图1是本申请实施例提供的一种示例通信系统的系统架构图；
图2是本申请实施例提供的一种上行信息发送方法流程示意图；
图3是本申请实施例一提供的资源时序关系示意图；
图4是本申请实施例一提供的资源另一时序关系示意图；
图5是本申请实施例提供的一种终端的结构示意图；
图6是本申请实施例提供的一种电子设备的结构示意图。
具体实施方式
下面结合本申请实施例中的附图对本申请实施例进行描述。
本申请中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，表示前后关联对象是一种“或”的关系。
本申请实施例中出现的“多个”是指两个或两个以上。本申请实施例中出 现的第一、第二等描述，仅作示意与区分描述对象之用，没有次序之分，也不表示本申请实施例中对设备个数的特别限定，不能构成对本申请实施例的任何限制。本申请实施例中出现的“连接”是指直接连接或者间接连接等各种连接方式，以实现设备间的通信，本申请实施例对此不做任何限定。
本申请实施例的技术方案可以应用于如图1所示的示例通信系统100，该示例通信系统100包括终端110和网络设备120，终端110与网络设备120通信连接。
该示例通信系统100例如可以是：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution，LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、免授权频谱上的LTE系统(LTE-based access to unlicensed spectrum，LTE-U)、免授权频谱上的NR系统(NR-based access tounlicensed spectrum，NR-U)、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，以及车辆间(Vehicle to Vehicle，V2V)通信等，本申请实施例也可以应用于这些通信系统。可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
本申请实施例中的终端110可以指用户设备、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置。终端还可以是蜂窝电话、无绳电话、会话启动协议(session initiation protocol，SIP)电话、无线本地环路(wireless local  loop，WLL)站、个人数字助理(personal digital assistant，PDA)、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、中继设备、车载设备、可穿戴设备，未来5G网络中的终端或者未来演进的公用陆地移动通信网络(public land mobile network，PLMN)中的终端等，本申请实施例对此并不限定。
本申请实施例中的网络设备120可以是用于与终端通信的设备，该网络设备可以是LTE系统中的演进型基站(evoled NodeB，eNB或eNodeB)，还可以是云无线接入网络(cloud radio access network，CRAN)场景下的无线控制器，或者该网络设备可以为中继设备、接入点、车载设备、可穿戴设备以及未来5G网络中的网络设备或者未来演进的PLMN网络中的网络设备，5G系统中的基站的一个或一组(包括多个天线面板)天线面板，或者，还可以为构成gNB或传输点的网络节点，如基带单元(baseband unit，BBU)，或，分布式单元(distributed unit，DU)等，本申请实施例并不限定。
在一些部署中，gNB可以包括集中式单元(centralized unit，CU)和DU。gNB还可以包括有源天线单元(active antenna unit，AAU)。CU实现gNB的部分功能，DU实现gNB的部分功能。比如，CU负责处理非实时协议和服务，实现无线资源控制(radio resource control，RRC)，分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能。DU负责处理物理层协议和实时服务，实现无线链路控制(radio link control，RLC)层、媒体接入控制(media access control，MAC)层和物理(physical，PHY)层的功能。
在MTC系统中，若PUSCH和SR冲突(即产生碰撞)时，会造成PUSCH发送中断，造成基站接收异常。正常发送SR时，此时如有PUSCH发送，因PUCCH优先级较高，会对PUSCH造成打孔。
参阅图2，图2提供了一种上行信息发送方法，该方法由如图1所示的通信系统内执行，该方法应用于MTC，该方法如图2所示，可以包括如下步骤：
步骤S200、若SR的PUCCH与物理上行共享信道PUSCH产生碰撞，用户设备UE优先对该PUSCH重复发送。
本申请提供的技术方案在SR的PUCCH与PUSCH产生碰撞时，优先发送PUSCH，进而保证了PUSCH的发送，提高了网络的可靠性以及用户体验 度。此方案在SR与PUSCH产生碰撞时，优先发送PUSCH的发送，这样不会因为SR优先级高而对PUSCH打孔导致基站无法解码PUSCH，进而提高网络的稳定性和可靠性。
在一种可选的方案中，所述方法还包括：
延时触发SR的发送。在此方案中，延迟触发SR发送可以在PUSCH重复发送完毕之后的时隙内触发SR的发送，这样不会因为SR发送导致PUSCH重复发送失败，提高了网络的稳定性。另外，该延时触发SR的发送时不增加SR发送计数，即将SR计数器暂时停止，这样能够避免了因为SR计数过多导致的SR重建的问题。延时发送后的资源示意如图3所示。
在一种可选的方案中，所述方法在延时触发SR的发送之前还包括：
若该PUSCH未完成发送，则继续优先发送该PUSCH。该方案对于PUSCH需要优先发送，因为若PUSCH未正确解码，即使SR发送成功，也会影响基站的网络性能，即无法依据SR进行资源的调度，因此对于MTC需要优先PUSCH的传输。
在一种可选的方案中，所述方法还包括：
依据PUCCH的信息确定延时触发SR的延时时间。
在一种可选的方案中，所述PUCCH的信息包括以下的一种或任意组合：PUSCH的重复过程、重复次数；SR重复过程、重复次数。
在一种可选的方案中，所述延时触发SR的发送具体包括：
确定SR的首发帧在该PUSCH的完成帧之后的第x帧，x≥1且x为整数。其中X优先取1，此种设置能够让PUSCH发送完毕后直接发送SR，进而减少网络延时的优点。
在一种可选的方案中，SR的PUCCH与PUSCH产生碰撞的确定方法具体包括：
若同一帧内存在SR和PUSCH发送时，确定SR的PUCCH与PUSCH产生碰撞。
如图4所示，如图4所示的PUCCH与PUSCH在部分帧即发生碰撞。
实施例一
本申请实施例一提供一种上行信息发送方法，该方法在如图1所示的通信 系统内执行，该方法的SR以及PUSCH的发送如图4所示，该方法可以包括如下：若SR的PUCCH与PUSCH产生碰撞，用户设备UE优先对该PUSCH重复发送，即将SR延时发送，如图3所示，该SR可以延时到PUSCH的完毕帧之后的数据帧发送。
参阅图5，图5提供了一种用户设备UE，如图5所示，该用户设备UE可以包括：
处理单元，用于资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，优先控制通信单元对该PUSCH重复发送。
本申请提供的技术方案在SR的PUCCH与PUSCH产生碰撞时，优先发送PUSCH，进而保证了PUSCH的发送，提高了网络的可靠性以及用户体验度。此方案在SR与PUSCH产生碰撞时，优先发送PUSCH的发送，这样不会因为SR优先级高而对PUSCH打孔导致基站无法解码PUSCH，进而提高网络的稳定性和可靠性。
在一种可选的方案中，处理单元，还用于延时触发SR的发送。
在此方案中，延迟触发SR发送可以在PUSCH重复发送完毕之后的时隙内触发SR的发送，这样不会因为SR发送导致PUSCH重复发送失败，提高了网络的稳定性。另外，该延时触发SR的发送时不增加SR发送计数，即将SR计数器暂时停止，这样能够避免了因为SR计数过多导致的SR重建的问题。延时发送后的资源示意如图3所示。
在一种可选的方案中，在一种可选的方案中，处理单元，还用于若该PUSCH未完成发送，则继续优先发送该PUSCH。
该方案对于PUSCH需要优先发送，因为若PUSCH未正确解码，即使SR发送成功，也会影响基站的网络性能，即无法依据SR进行资源的调度，因此对于MTC需要优先PUSCH的传输。
在一种可选的方案中，处理单元，还用于依据PUCCH的信息确定延时触发SR的延时时间。
在一种可选的方案中，所述PUCCH的信息包括以下的一种或任意组合：PUSCH的重复过程、重复次数；SR重复过程、重复次数。
在一种可选的方案中，在一种可选的方案中，处理单元，还用于确定SR 的首发帧在该PUSCH的完成帧之后的第x帧，x≥1且x为整数。其中X优先取1，此种设置能够让PUSCH发送完毕后直接发送SR，进而减少网络延时的优点。
在一种可选的方案中，SR的PUCCH与PUSCH产生碰撞的确定方法具体包括：
若同一帧内存在SR和PUSCH发送时，确定SR的PUCCH与PUSCH产生碰撞。
可以理解的是，用户设备为了实现上述功能，其包含了执行各个功能相应的硬件和/或软件模块。结合本文中所公开的实施例描述的各示例的算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。本领域技术人员可以结合实施例对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本实施例可以根据上述方法示例对电子设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块可以采用硬件的形式实现。需要说明的是，本实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
在采用集成的单元的情况下，用户设备可以包括处理模块、存储模块和通信模块。其中，处理模块可以用于对用户设备的动作进行控制管理，例如，可以用于支持电子设备执行上述通信单元和处理单元执行的步骤。存储模块可以用于支持电子设备执行存储程序代码和数据等。通信模块，可以用于支持电子设备与其他设备的通信。
其中，处理模块可以是处理器或控制器。其可以实现或执行结合本申请公开内容所描述的各种示例性的逻辑方框，模块和电路。处理器也可以是实现计算功能的组合，例如包含一个或多个微处理器组合，数字信号处理(digital signal processing，DSP)和微处理器的组合等等。存储模块可以是存储器。通信模块具体可以为射频电路、蓝牙芯片、Wi-Fi芯片等与其他电子设备交互的设备。
可以理解的是，本申请实施例示意的各模块间的接口连接关系，只是示意性说明，并不构成对用户设备的结构限定。在本申请另一些实施例中，用户设备也可以采用上述实施例中不同的接口连接方式，或多种接口连接方式的组合。
请参见图6，图6是本申请实施例提供的一种电子设备60，该电子设备可以为终端，包括处理器601、存储器602和通信接口603，所述处理器601、存储器602和通信接口603通过总线相互连接。
本申请实施例中的存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(read-only memory，简称ROM)、可编程只读存储器(programmable ROM，简称PROM)、可擦除可编程只读存储器(erasable PROM，简称EPROM)、电可擦除可编程只读存储器(electrically EPROM，简称EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory，简称RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的随机存取存储器(random access memory，简称RAM)可用，例如静态随机存取存储器(static RAM，简称SRAM)、动态随机存取存储器(DRAM)、同步动态随机存取存储器(synchronous DRAM，简称SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM，简称DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM，简称ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM，简称SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM，简称DR RAM)。
处理器601可以是一个或多个中央处理器(central processing unit，CPU)，在处理器601是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
处理器601可以包括一个或多个处理单元，例如：处理单元可以包括应用处理器(application processor，AP)，调制解调处理器，图形处理器(graphics processing unit，GPU)，图像信号处理器(image signal processor，ISP)，控制器，视频编解码器，数字信号处理器(digital signal processor，DSP)，基带处理器，和/或神经网络处理器(neural-network processing unit，NPU)等。其 中，不同的处理单元可以是独立的部件，也可以集成在一个或多个处理器中。在一些实施例中，用户设备也可以包括一个或多个处理单元。其中，控制器可以根据指令操作码和时序信号，产生操作控制信号，完成取指令和执行指令的控制。在其他一些实施例中，处理单元中还可以设置存储器，用于存储指令和数据。示例性地，处理单元中的存储器可以为高速缓冲存储器。该存储器可以保存处理单元刚用过或循环使用的指令或数据。如果处理单元需要再次使用该指令或数据，可从所述存储器中直接调用。这样就避免了重复存取，减少了处理单元的等待时间，因而提高了用户设备处理数据或执行指令的效率。
在一些实施例中，处理器601可以包括一个或多个接口。接口可以包括集成电路间(inter-integrated circuit，I2C)接口、集成电路间音频(inter-integrated circuit sound，I2S)接口、脉冲编码调制(pulse code modulation，PCM)接口、通用异步收发传输器(universal asynchronous receiver/transmitter，UART)接口、移动产业处理器接口(mobile industry processor interface，MIPI)、用输入输出(general-purpose input/output，GPIO)接口、SIM卡接口和/或USB接口等。其中，USB接口是符合USB标准规范的接口，具体可以是Mini USB接口、Micro USB接口、USB Type C接口等。USB接口可以用于连接充电器为用户设备充电，也可以用于用户设备与外围设备之间传输数据。该USB接口也可以用于连接耳机，通过耳机播放音频。
该电子设备60中的处理器601用于读取所述存储器602中存储的计算机程序代码，执行以下操作：
若资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，优先对该PUSCH重复发送。
其中，上述方法实施例涉及的各场景的所有相关内容均可以援引到对应功能模块的功能描述，在此不再赘述。
本申请实施例还提供一种芯片系统，所述芯片系统包括至少一个处理器，存储器和接口电路，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有计算机程序；所述计算机程序被所述处理器执行时，图2所示的方法流程得以实现。
本申请实施例还提供一种计算机可读存储介质，所述计算机可读存储介质 中存储有计算机程序，当其在网络设备上运行时，图2所示的方法流程得以实现。
本申请实施例还提供一种计算机程序产品，当所述计算机程序产品在终端上运行时，图2所示的方法流程得以实现。
本申请实施例还提供一种终端，包括处理器、存储器、通信接口，以及一个或多个程序，所述一个或多个程序被存储在所述存储器中，并且被配置由所述处理器执行，所述程序包括用于执行图2所示实施例的方法中的步骤的指令。
上述主要从方法侧执行过程的角度对本申请实施例的方案进行了介绍。可以理解的是，电子设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模板。本领域技术人员应该很容易意识到，结合本文中所提供的实施例描述的各示例的单元及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对电子设备进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个处理单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。需要说明的是，本申请实施例中对单元的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
需要说明的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模板并不一定是本申请所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详述的部分，可以参见其他实施例的相关描述。
在本申请所提供的几个实施例中，应该理解到，所揭露的装置，可通过其 它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如上述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性或其它的形式。
上述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
上述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储器中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储器中，包括若干指令用以使得一台计算机设备(可为个人计算机、服务器或者网络设备等)执行本申请各个实施例上述方法的全部或部分步骤。而前述的存储器包括：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储器中，存储器可以包括：闪存盘、只读存储器(英文：Read-Only Memory，简称：ROM)、随机存取器(英文：Random Access Memory，简称：RAM)、磁盘或光盘等。

Claims (19)

  1. 一种上行信息发送方法，其特征在于，所述方法应用于机器类通信MTC，所述方法包括如下步骤：
    若资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，用户设备UE优先对该PUSCH重复发送。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    延时触发SR的发送。
  3. 根据权利要求2所述的方法，其特征在于，所述方法在延时触发SR的发送之前还包括：
    若该PUSCH未完成发送，则继续优先发送该PUSCH。
  4. 根据权利要求2所述的方法，其特征在于，所述方法还包括：
    依据PUCCH的信息确定延时触发SR的延时时间。
  5. 根据权利要求4所述的方法，其特征在于，所述PUCCH的信息包括：
    PUSCH的重复过程、重复次数；SR重复过程、重复次数。
  6. 根据权利要求2所述的方法，其特征在于，所述延时触发SR的发送具体包括：
    确定SR的首发帧在该PUSCH的完成帧之后的第x帧，x≥1且x为整数。
  7. 根据权利要求1所述的方法，其特征在于，SR的PUCCH与PUSCH产生碰撞的确定方法具体包括：
    若同一帧内存在SR和PUSCH发送时，确定SR的PUCCH与PUSCH产生碰撞。
  8. 一种用户设备UE，其特征在于，所述UE包括：
    处理单元，用于资源调度请求SR的物理上行链路控制信道PUCCH与物理上行共享信道PUSCH产生碰撞，优先控制通信单元对该PUSCH重复发送。
  9. 根据权利要求8所述的用户设备，其特征在于，
    处理单元，还用于延时触发SR的发送。
  10. 根据权利要求9所述的用户设备，其特征在于，
    处理单元，还用于若该PUSCH未完成发送，则继续优先发送该PUSCH。
  11. 根据权利要求9所述的用户设备，其特征在于，
    处理单元，还用于依据PUCCH的信息确定延时触发SR的延时时间。
  12. 根据权利要求11所述的用户设备，其特征在于，所述PUCCH的信息包括：PUSCH的重复过程、重复次数；SR重复过程、重复次数。
  13. 根据权利要求9所述的用户设备，其特征在于，
    处理单元，具体用于确定SR的首发帧在该PUSCH的完成帧之后的第x帧，x≥1且x为整数。
  14. 根据权利要求8所述的用户设备，其特征在于，
    处理单元，具体用于若同一帧内存在SR和PUSCH发送时，确定SR的PUCCH与PUSCH产生碰撞。
  15. 一种终端，包括处理器、存储器、通信接口，以及一个或多个程序，所述一个或多个程序被存储在所述存储器中，并且被配置由所述处理器执行，所述程序包括用于执行如权利要求1-7任意一项所述的方法中的步骤的指令。
  16. 一种芯片系统，所述芯片系统包括至少一个处理器，存储器和接口电 路，所述存储器、所述收发器和所述至少一个处理器通过线路互联，所述至少一个存储器中存储有计算机程序；所述计算机程序被所述处理器执行时实现如权利要求1-7任意一项所述的方法。
  17. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，当其在用户设备上运行时，执行如权利要求1-7任意一项所述的方法。
  18. 一种计算机程序产品，其特征在于，所述计算机程序产品包括存储了计算机程序的非瞬时性计算机可读存储介质，所述计算机程序可操作来使计算机执行如权利要求1-7任一项所述的方法。
  19. 一种网络设备，其特征在于，所述网络设备用于支持用户设备执行如权利要求1-7任一项所述的方法。
PCT/CN2021/123243 2020-10-16 2021-10-12 上行信息发送方法及相关产品 WO2022078321A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011122872.7 2020-10-16
CN202011122872.7A CN112311517A (zh) 2020-10-16 2020-10-16 上行信息发送方法及相关产品

Publications (1)

Publication Number Publication Date
WO2022078321A1 true WO2022078321A1 (zh) 2022-04-21

Family

ID=74328647

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/123243 WO2022078321A1 (zh) 2020-10-16 2021-10-12 上行信息发送方法及相关产品

Country Status (2)

Country Link
CN (1) CN112311517A (zh)
WO (1) WO2022078321A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115333910A (zh) * 2022-08-10 2022-11-11 广东电网有限责任公司江门供电局 电力线网络随机接入的帧间干扰连续消除方法及相关装置

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112311517A (zh) * 2020-10-16 2021-02-02 紫光展锐(重庆)科技有限公司 上行信息发送方法及相关产品

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108702768A (zh) * 2018-04-24 2018-10-23 北京小米移动软件有限公司 调度请求传输方法及装置和资源分配方法及装置
CN111586759A (zh) * 2019-02-15 2020-08-25 电信科学技术研究院有限公司 一种传输方法和设备
CN111585722A (zh) * 2019-02-15 2020-08-25 电信科学技术研究院有限公司 物理上行共享信道的传输方法、终端及网络设备
WO2020196546A1 (en) * 2019-03-25 2020-10-01 Sharp Kabushiki Kaisha COLLISION HANDLING and UCI MULTIPLEXING for URLLC PUCCH and eMBB PUSCH
US20200329486A1 (en) * 2019-04-09 2020-10-15 Qualcomm Incorporated Handling collisions between uplink data repetitions and an uplink control transmission
CN112020149A (zh) * 2019-05-29 2020-12-01 成都鼎桥通信技术有限公司 一种避免pusch和pucch冲突的方法和设备
CN112311517A (zh) * 2020-10-16 2021-02-02 紫光展锐(重庆)科技有限公司 上行信息发送方法及相关产品

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10841934B2 (en) * 2017-11-27 2020-11-17 Qualcomm Incorporated Priority rule for signal repetition collisions
WO2019157684A1 (zh) * 2018-02-13 2019-08-22 华为技术有限公司 一种通信方法及装置
CN110351757B (zh) * 2018-04-04 2020-12-04 电信科学技术研究院有限公司 一种调度请求传输方法、终端及网络侧设备
CN111294936B (zh) * 2018-12-06 2023-04-14 大唐移动通信设备有限公司 一种传输方法及终端
CN111586854B (zh) * 2019-02-15 2024-03-08 大唐移动通信设备有限公司 物理上行共享信道的传输方法、终端及网络设备
CN111757496B (zh) * 2019-03-29 2023-07-11 华为技术有限公司 一种通信方法及装置
CN111615184B (zh) * 2019-04-22 2023-12-22 维沃移动通信有限公司 处理方法及终端

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108702768A (zh) * 2018-04-24 2018-10-23 北京小米移动软件有限公司 调度请求传输方法及装置和资源分配方法及装置
CN111586759A (zh) * 2019-02-15 2020-08-25 电信科学技术研究院有限公司 一种传输方法和设备
CN111585722A (zh) * 2019-02-15 2020-08-25 电信科学技术研究院有限公司 物理上行共享信道的传输方法、终端及网络设备
WO2020196546A1 (en) * 2019-03-25 2020-10-01 Sharp Kabushiki Kaisha COLLISION HANDLING and UCI MULTIPLEXING for URLLC PUCCH and eMBB PUSCH
US20200329486A1 (en) * 2019-04-09 2020-10-15 Qualcomm Incorporated Handling collisions between uplink data repetitions and an uplink control transmission
CN112020149A (zh) * 2019-05-29 2020-12-01 成都鼎桥通信技术有限公司 一种避免pusch和pucch冲突的方法和设备
CN112311517A (zh) * 2020-10-16 2021-02-02 紫光展锐(重庆)科技有限公司 上行信息发送方法及相关产品

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CATT: "Prioritization rule for SR-PUSCH collision", 3GPP DRAFT; R2-1903144-PRIORITIZATION RULE FOR SR-PUSCH COLLISION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Xi’an, China; 20190408 - 20190412, 6 April 2019 (2019-04-06), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051700498 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115333910A (zh) * 2022-08-10 2022-11-11 广东电网有限责任公司江门供电局 电力线网络随机接入的帧间干扰连续消除方法及相关装置
CN115333910B (zh) * 2022-08-10 2024-01-23 广东电网有限责任公司江门供电局 电力线网络随机接入的帧间干扰连续消除方法及相关装置

Also Published As

Publication number Publication date
CN112311517A (zh) 2021-02-02

Similar Documents

Publication Publication Date Title
WO2020216341A1 (zh) 随机接入方法和通信装置
WO2022078321A1 (zh) 上行信息发送方法及相关产品
WO2020156521A1 (zh) 一种无线资源控制rrc消息发送方法及装置
US20230156830A1 (en) Communication method and related device
US10819397B2 (en) Information transmission method and related device
WO2022152329A1 (zh) 辅链路的psfch传输方法、装置及存储介质
JP2022516899A (ja) 無線通信方法及び装置
WO2021056583A1 (zh) 一种上行传输方法及装置
WO2022063186A1 (zh) 传输链路的切换方法及相关产品
WO2018126410A1 (zh) 数据传输方法及终端与网络设备
WO2022120516A1 (zh) 通信方法、设备和系统
WO2022068666A1 (zh) 基于业务的中继选择方法及相关产品
WO2022068701A1 (zh) 中继的bsr触发方法及相关产品
WO2022062855A1 (zh) 多播业务的反馈方法及相关产品
WO2021169840A1 (zh) 使用预配置资源传输的方法及相关装置
WO2021168801A1 (zh) 中继通信QoS保证的方法及相关装置
WO2022068667A1 (zh) 物理下行数据信道pdsch资源确定方法及相关产品
WO2021196147A1 (zh) 信息传输的方法、终端设备和网络设备
WO2022218416A1 (zh) 一种反馈方法、装置及设备
US20230328825A1 (en) Configuration reset method and apparatus, and terminal device
WO2023131319A1 (zh) 定时提前确定方法及相关装置
AU2020428979B2 (en) Method for determining transport block size and communication apparatus
WO2022213779A1 (zh) 参数配置方法、终端设备和网络设备
WO2023131220A1 (zh) 一种通信方法、装置及系统
WO2022021032A1 (zh) 信息处理方法、终端设备和网络设备

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: 21879365

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: 21879365

Country of ref document: EP

Kind code of ref document: A1