CN112311517A - Uplink information sending method and related product - Google Patents
Uplink information sending method and related product Download PDFInfo
- Publication number
- CN112311517A CN112311517A CN202011122872.7A CN202011122872A CN112311517A CN 112311517 A CN112311517 A CN 112311517A CN 202011122872 A CN202011122872 A CN 202011122872A CN 112311517 A CN112311517 A CN 112311517A
- Authority
- CN
- China
- Prior art keywords
- pusch
- memory
- pucch
- processor
- physical uplink
- Prior art date
- Legal status (The legal status 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 status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 52
- 238000004891 communication Methods 0.000 claims abstract description 40
- 230000015654 memory Effects 0.000 claims description 42
- 230000005540 biological transmission Effects 0.000 claims description 32
- 238000012545 processing Methods 0.000 claims description 31
- 238000004590 computer program Methods 0.000 claims description 18
- 230000008569 process Effects 0.000 claims description 8
- 230000003111 delayed effect Effects 0.000 claims description 7
- 230000001960 triggered effect Effects 0.000 claims description 2
- 230000006870 function Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 5
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000007774 longterm Effects 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000010295 mobile communication Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000013528 artificial neural network Methods 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000001934 delay Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 238000005562 fading Methods 0.000 description 1
- 230000000977 initiatory effect Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
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]
Abstract
The embodiment of the application provides an uplink information sending method and a related product, wherein the method is applied to Machine Type Communication (MTC), and comprises the following steps: if a Physical Uplink Control Channel (PUCCH) of the resource scheduling request SR collides with a Physical Uplink Shared Channel (PUSCH), the User Equipment (UE) preferentially and repeatedly sends the PUSCH. The technical scheme provided by the application has the advantage of good network performance.
Description
Technical Field
The present application relates to the field of communication processing technologies, and in particular, to an uplink information sending method and a related product.
Background
In an MTC (Machine-Type Communication) Communication system, under channel conditions of wide coverage, weak coverage, fast fading, and the like, when a terminal plans a PUSCH (physical uplink shared channel) for repeated transmission and recognizes that a new data trigger SR (Resource scheduling request) is present for transmission, a UE (User Equipment) cannot achieve repeated transmission of the PUSCH, which affects network performance.
Disclosure of Invention
The embodiment of the application discloses an uplink information sending method and a related product, wherein when a PUSCH conflicts with an SR, the PUSCH is sent preferentially, so that repeated sending of the PUSCH is realized, the network performance is improved, and the user experience is improved.
In a first aspect, an uplink information sending method is provided, where the method is applied to machine type communication MTC, and the method includes the following steps:
if a Physical Uplink Control Channel (PUCCH) of the resource scheduling request SR collides with a Physical Uplink Shared Channel (PUSCH), the User Equipment (UE) preferentially and repeatedly sends the PUSCH.
In a second aspect, a user equipment is provided, the UE comprising:
and the processing unit is used for colliding a Physical Uplink Control Channel (PUCCH) of the resource Scheduling Request (SR) with a Physical Uplink Shared Channel (PUSCH), and controlling the communication unit to repeatedly transmit the PUSCH according to priority.
In a third aspect, there is provided a terminal comprising a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing the steps of the method of the first aspect.
In a fourth aspect, a computer-readable storage medium is provided, storing a computer program for electronic data exchange, wherein the computer program causes a computer to perform the method of the first aspect.
In a fifth aspect, there is provided a computer program product, wherein the computer program product comprises a non-transitory computer readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps as described in the first aspect of an embodiment of the present application. The computer program product may be a software installation package.
In a sixth aspect, a chip system is provided, the chip system comprising at least one processor, a memory and an interface circuit, the memory, the transceiver and the at least one processor being interconnected by wires, the at least one memory having a computer program stored therein; the computer program, when executed by the processor, implements the method of the first aspect.
By implementing the embodiment of the application, when the PUCCH of the SR collides with the PUSCH, the PUSCH is preferentially sent, so that the sending of the PUSCH is ensured, and the reliability of a network and the user experience are improved. According to the scheme, when the SR collides with the PUSCH, the PUSCH is sent preferentially, so that the situation that the PUSCH cannot be decoded by the base station due to the fact that the PUSCH is punched because of high SR priority is avoided, and the stability and the reliability of a network are improved.
Drawings
The drawings used in the embodiments of the present application are described below.
Fig. 1 is a system architecture diagram of an example communication system provided by an embodiment of the present application;
fig. 2 is a flowchart illustrating an uplink information sending method according to an embodiment of the present application;
FIG. 3 is a schematic diagram of a resource timing relationship according to an embodiment of the present application;
FIG. 4 is a schematic diagram of another timing relationship of resources provided in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The embodiments of the present application will be described below with reference to the drawings.
The term "and/or" in this application is only one kind of association relationship describing the associated object, and means that there may be three kinds of relationships, for example, a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" in this document indicates that the former and latter related objects are in an "or" relationship.
The "plurality" appearing in the embodiments of the present application means two or more. The descriptions of the first, second, etc. appearing in the embodiments of the present application are only for illustrating and differentiating the objects, and do not represent the order or the particular limitation of the number of the devices in the embodiments of the present application, and do not constitute any limitation to the embodiments of the present application. The term "connect" in the embodiments of the present application refers to various connection manners, such as direct connection or indirect connection, to implement communication between devices, which is not limited in this embodiment of the present application.
The technical solution of the embodiment of the present application may be applied to the example communication system 100 shown in fig. 1, where the example communication system 100 includes a terminal 110 and a network device 120, and the terminal 110 is communicatively connected to the network device 120.
The example communication system 100 may be, for example: a Global System for Mobile communications (GSM) System, a Code Division Multiple Access (CDMA) System, a Wideband Code Division Multiple Access (WCDMA) System, a General Packet Radio Service (GPRS), a Long Term Evolution (Long Term Evolution, LTE) System, an Advanced Long Term Evolution (LTE-a) System, a New Radio (NR) System, an Evolution System of an NR System, an LTE-over-unlicensed spectrum (LTE-U) System, an NR-over-unlicensed spectrum (NR-over-licensed spectrum) System, a Universal Mobile Telecommunications System (UMTS) System, or other next generation communication systems.
Generally, conventional Communication systems support a limited number of connections and are easy to implement, however, with the development of Communication technology, mobile Communication systems will support not only conventional Communication, but also, for example, Device-to-Device (D2D) Communication, Machine-to-Machine (M2M) Communication, Machine Type Communication (MTC), and Vehicle-to-Vehicle (V2V) Communication, and the embodiments of the present application can also be applied to these Communication systems. Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.
A terminal 110 in the embodiments of the present application may refer to a user equipment, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user 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 handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a relay device, a vehicle-mounted device, a wearable device, a terminal in a future 5G network or a terminal in a future evolved Public Land Mobile Network (PLMN), and the like, which are not limited in this embodiment.
The network device 120 in this embodiment may be a device for communicating with a terminal, where the network device may be an evolved NodeB (eNB or eNodeB) in an LTE system, and may also be a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or the network device may be a relay device, an access point, a vehicle-mounted device, a wearable device, and a network device in a future 5G network or a network device in a future evolved PLMN network, one or a group (including multiple antenna panels) of base stations in a 5G system, or may also be a network node forming a gNB or a transmission point, such as a baseband unit (BBU) or a Distributed Unit (DU), and the present embodiment is not limited.
In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include an Active Antenna Unit (AAU). The CU implements part of the function of the gNB and the DU implements part of the function of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing functions of a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer.
In the MTC system, if the PUSCH and the SR collide (i.e., a collision occurs), the PUSCH transmission is interrupted, and the base station reception is abnormal. When the SR is normally transmitted, if the PUSCH is transmitted at the moment, the PUSCH is punctured due to the fact that the priority of the PUCCH is high.
Referring to fig. 2, fig. 2 provides an uplink information sending method, which is performed in the communication system shown in fig. 1, and is applied to MTC, and the method shown in fig. 2 may include the following steps:
and step S200, if the PUCCH of the SR collides with a Physical Uplink Shared Channel (PUSCH), the User Equipment (UE) preferentially and repeatedly sends the PUSCH.
According to the technical scheme, when the PUCCH and the PUSCH of the SR collide, the PUSCH is preferentially sent, so that the sending of the PUSCH is ensured, and the reliability of the network and the user experience are improved. According to the scheme, when the SR collides with the PUSCH, the PUSCH is sent preferentially, so that the situation that the PUSCH cannot be decoded by the base station due to the fact that the PUSCH is punched because of high SR priority is avoided, and the stability and the reliability of a network are improved.
In an optional aspect, the method further comprises:
and triggering the SR to send in a delayed way. In the scheme, the delayed trigger SR transmission can trigger the SR transmission in the time slot after the PUSCH repeated transmission is finished, so that the repeated PUSCH transmission failure caused by the SR transmission is avoided, and the stability of the network is improved. In addition, when the time delay triggers the SR to transmit, the SR transmission count is not increased, namely, the SR counter is stopped temporarily, so that the problem of SR reestablishment caused by excessive SR count can be avoided. The resource after delayed transmission is schematically shown in fig. 3.
In an optional scheme, before the delaying the transmission of the trigger SR, the method further includes:
and if the PUSCH is not transmitted, continuing to preferentially transmit the PUSCH. This scheme requires preferential transmission for PUSCH, because if PUSCH is not decoded correctly, even if SR transmission is successful, network performance of the base station is affected, that is, scheduling of resources according to SR is not possible, and thus transmission of PUSCH is required preferentially for MTC.
In an optional aspect, the method further comprises:
and determining the delay time for delaying and triggering the SR according to the information of the PUCCH.
In an optional scheme, the information of the PUCCH includes one or any combination of the following: the repeated process and repeated times of the PUSCH; SR repetition process, repetition number.
In an optional scheme, the sending of the delay triggered SR specifically includes:
and determining the xth frame of the initial frame of the SR after the completion frame of the PUSCH, wherein x is not less than 1 and is an integer. Wherein X takes 1 first, and the setting can enable PUSCH to directly send SR after sending is finished, thereby reducing the network delay.
In an optional scheme, the method for determining that the PUCCH of the SR collides with the PUSCH specifically includes:
and if the SR and the PUSCH exist in the same frame for transmission, determining that the PUCCH of the SR collides with the PUSCH.
As shown in fig. 4, the PUCCH and PUSCH shown in fig. 4 collide in a partial frame.
Example one
An uplink information sending method according to an embodiment of the present application is implemented in the communication system shown in fig. 1, where SR and PUSCH of the method are shown in fig. 4, and the method may include the following steps: if the PUCCH of SR collides with PUSCH, the user equipment UE preferentially repeats transmission of the PUSCH, that is, delays transmission of SR, and as shown in fig. 3, the SR may be delayed to transmit a data frame after the end frame of PUSCH.
Referring to fig. 5, fig. 5 provides a user equipment UE, and as shown in fig. 5, the user equipment UE may include:
and the processing unit is used for colliding a Physical Uplink Control Channel (PUCCH) of the resource Scheduling Request (SR) with a Physical Uplink Shared Channel (PUSCH), and controlling the communication unit to repeatedly transmit the PUSCH according to priority.
According to the technical scheme, when the PUCCH and the PUSCH of the SR collide, the PUSCH is preferentially sent, so that the sending of the PUSCH is ensured, and the reliability of the network and the user experience are improved. According to the scheme, when the SR collides with the PUSCH, the PUSCH is sent preferentially, so that the situation that the PUSCH cannot be decoded by the base station due to the fact that the PUSCH is punched because of high SR priority is avoided, and the stability and the reliability of a network are improved.
In an optional scheme, the processing unit is further configured to delay triggering of the SR.
In the scheme, the delayed trigger SR transmission can trigger the SR transmission in the time slot after the PUSCH repeated transmission is finished, so that the repeated PUSCH transmission failure caused by the SR transmission is avoided, and the stability of the network is improved. In addition, when the time delay triggers the SR to transmit, the SR transmission count is not increased, namely, the SR counter is stopped temporarily, so that the problem of SR reestablishment caused by excessive SR count can be avoided. The resource after delayed transmission is schematically shown in fig. 3.
In an optional scheme, the processing unit is further configured to continue to preferentially transmit the PUSCH if the PUSCH is not finished being transmitted.
This scheme requires preferential transmission for PUSCH, because if PUSCH is not decoded correctly, even if SR transmission is successful, network performance of the base station is affected, that is, scheduling of resources according to SR is not possible, and thus transmission of PUSCH is required preferentially for MTC.
In an optional scheme, the processing unit is further configured to determine a delay time for delaying the trigger SR according to information of the PUCCH.
In an optional scheme, the information of the PUCCH includes one or any combination of the following: the repeated process and repeated times of the PUSCH; SR repetition process, repetition number.
In an optional scheme, the processing unit is further configured to determine an xth frame of the SR frame after the completion frame of the PUSCH, where x ≧ 1 and x is an integer. Wherein X takes 1 first, and the setting can enable PUSCH to directly send SR after sending is finished, thereby reducing the network delay.
In an optional scheme, the method for determining that the PUCCH of the SR collides with the PUSCH specifically includes:
and if the SR and the PUSCH exist in the same frame for transmission, determining that the PUCCH of the SR collides with the PUSCH.
It will be appreciated that the user equipment, in order to carry out the above-described functions, comprises corresponding hardware and/or software modules for performing the respective functions. The present application is capable of being implemented in hardware or a combination of hardware and computer software in conjunction with the exemplary algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, with the embodiment described in connection with the particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In this embodiment, the electronic device may be divided into functional modules according to the above method example, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module may be implemented in the form of hardware. It should be noted that the division of the modules in this embodiment is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
In case of an integrated unit, the user equipment may comprise a processing module, a storage module and a communication module. The processing module may be configured to control and manage actions of the user equipment, and for example, may be configured to support the electronic equipment to perform steps performed by the communication unit and the processing unit. The memory module may be used to support the electronic device in executing stored program codes and data, etc. The communication module can be used for supporting the communication between the electronic equipment and other equipment.
The processing module may be a processor or a controller. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., a combination of one or more microprocessors, a Digital Signal Processing (DSP) and a microprocessor, or the like. The storage module may be a memory. The communication module may specifically be a radio frequency circuit, a bluetooth chip, a Wi-Fi chip, or other devices that interact with other electronic devices.
It should be understood that the interface connection relationship between the modules illustrated in the embodiments of the present application is only an exemplary illustration, and does not form a structural limitation on the user equipment. In other embodiments of the present application, the user equipment may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.
Referring to fig. 6, fig. 6 is an electronic device 60, which may be a terminal and includes a processor 601, a memory 602, and a communication interface 603, where 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 either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example and not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM), SDRAM (SLDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).
The processor 601 may be one or more Central Processing Units (CPUs), and in the case that the processor 601 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.
Processor 601 may include one or more processing units, such as: the processing unit may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. Wherein the different processing units may be separate components or may be integrated in one or more processors. In some embodiments, 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 time sequence signal to complete the control of instruction fetching and instruction execution. In other embodiments, a memory may also be provided in the processing unit for storing instructions and data. Illustratively, the memory in the processing unit may be a cache memory. The memory may hold instructions or data that have just been used or recycled by the processing unit. If the processing unit needs to reuse the instruction or data, it can be called directly from the memory. This avoids repeated accesses and reduces the latency of the processing unit, thereby improving the efficiency with which the user equipment processes data or executes instructions.
In some embodiments, processor 601 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a SIM card interface, a USB interface, and/or the like. The USB interface is an interface conforming to the USB standard specification, and may specifically be a Mini USB interface, a Micro USB interface, a USB Type C interface, or the like. The USB interface can be used for connecting a charger to charge the user equipment, and can also be used for transmitting data between the user equipment and peripheral equipment. The USB interface can also be used for connecting an earphone and playing audio through the earphone.
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:
if collision occurs between a Physical Uplink Control Channel (PUCCH) of a resource Scheduling Request (SR) and a Physical Uplink Shared Channel (PUSCH), the PUSCH is preferentially and repeatedly transmitted.
All relevant contents of each scene related to the method embodiment may be referred to the functional description of the corresponding functional module, and are not described herein again.
The embodiment of the present application further provides a chip system, where the chip system includes at least one processor, a memory and an interface circuit, where the memory, the transceiver and the at least one processor are interconnected by a line, and the at least one memory stores a computer program; the method flow shown in fig. 2 is implemented when the computer program is executed by the processor.
An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, and when the computer program runs on a network device, the method flow shown in fig. 2 is implemented.
An embodiment of the present application further provides a computer program product, and when the computer program product runs on a terminal, the method flow shown in fig. 2 is implemented.
Embodiments of the present application also provide a terminal including a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs including instructions for performing the steps in the method of the embodiment shown in fig. 2.
The above description has introduced the solution of the embodiment of the present application mainly from the perspective of the method-side implementation process. It will be appreciated that the electronic device, in order to carry out the functions described above, may comprise corresponding hardware structures and/or software templates for performing the respective functions. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative elements and algorithm steps described in connection with the embodiments provided herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit. It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation.
It should be noted that, for simplicity of description, the above-mentioned method embodiments are described as a series of acts or combination of acts, but those skilled in the art will recognize that the present application is not limited by the order of acts described, as some steps may occur in other orders or concurrently depending on the application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are presently preferred and that no acts or templates referred to are necessarily required by the application.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus may be implemented in other manners. For example, the above-described embodiments of the apparatus are merely illustrative, and for example, the above-described division of the units is only one type of division of logical functions, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection of some interfaces, devices or units, and may be an electric or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit may be stored in a computer readable memory if it is implemented in the form of a software functional unit and sold or used as a stand-alone product. Based on such understanding, the technical solution of the present application may be substantially implemented or a part of or all or part of the technical solution contributing to the prior art may be embodied in the form of a software product stored in a memory, and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the above-mentioned method of the embodiments of the present application. And the aforementioned memory comprises: a U-disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic or optical disk, and other various media capable of storing program codes.
Those skilled in the art will appreciate that all or part of the steps in the methods of the above embodiments may be implemented by associated hardware instructed by a program, which may be stored in a computer-readable memory, which may include: flash Memory disks, Read-Only memories (ROMs), Random Access Memories (RAMs), magnetic or optical disks, and the like.
Claims (11)
1. An uplink information sending method is applied to Machine Type Communication (MTC), and comprises the following steps:
if a Physical Uplink Control Channel (PUCCH) of the resource scheduling request SR collides with a Physical Uplink Shared Channel (PUSCH), the User Equipment (UE) preferentially and repeatedly sends the PUSCH.
2. The method of claim 1, further comprising:
and triggering the SR to send in a delayed way.
3. The method of claim 2, further comprising, prior to the delaying the transmission of the trigger SR:
and if the PUSCH is not transmitted, continuing to preferentially transmit the PUSCH.
4. The method of claim 2, further comprising:
and determining the delay time for delaying and triggering the SR according to the information of the PUCCH.
5. The method of claim 4, wherein the information of the PUCCH comprises:
the repeated process and repeated times of the PUSCH; SR repetition process, repetition number.
6. The method according to claim 2, wherein the sending of the delay triggered SR specifically comprises:
and determining the xth frame of the initial frame of the SR after the completion frame of the PUSCH, wherein x is not less than 1 and is an integer.
7. The method according to claim 1, wherein the method for determining collision of the SR PUCCH and PUSCH specifically comprises:
and if the SR and the PUSCH exist in the same frame for transmission, determining that the PUCCH of the SR collides with the PUSCH.
8. A User Equipment (UE), the UE comprising:
and the processing unit is used for colliding a Physical Uplink Control Channel (PUCCH) of the resource Scheduling Request (SR) with a Physical Uplink Shared Channel (PUSCH), and controlling the communication unit to repeatedly transmit the PUSCH according to priority.
9. A terminal comprising a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing the steps of the method of any of claims 1-7.
10. A chip system, the chip system comprising at least one processor, a memory and an interface circuit, the memory, the transceiver and the at least one processor being interconnected by a line, the at least one memory having a computer program stored therein; the computer program, when executed by the processor, implements the method of any one of claims 1-7.
11. A computer-readable storage medium, in which a computer program is stored which, when run on a user equipment, performs the method of any one of claims 1-7.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011122872.7A CN112311517A (en) | 2020-10-16 | 2020-10-16 | Uplink information sending method and related product |
| PCT/CN2021/123243 WO2022078321A1 (en) | 2020-10-16 | 2021-10-12 | Uplink information sending method and related product |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011122872.7A CN112311517A (en) | 2020-10-16 | 2020-10-16 | Uplink information sending method and related product |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112311517A true CN112311517A (en) | 2021-02-02 |
Family
ID=74328647
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011122872.7A Pending CN112311517A (en) | 2020-10-16 | 2020-10-16 | Uplink information sending method and related product |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN112311517A (en) |
| WO (1) | WO2022078321A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022078321A1 (en) * | 2020-10-16 | 2022-04-21 | 紫光展锐(重庆)科技有限公司 | Uplink information sending method and related product |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115333910B (en) * | 2022-08-10 | 2024-01-23 | 广东电网有限责任公司江门供电局 | Inter-frame interference continuous elimination method and related device for power line network random access |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110351757A (en) * | 2018-04-04 | 2019-10-18 | 电信科学技术研究院有限公司 | A kind of scheduling request transmission method, terminal and network side equipment |
| CN111294936A (en) * | 2018-12-06 | 2020-06-16 | 电信科学技术研究院有限公司 | Transmission method and terminal |
| CN111373823A (en) * | 2017-11-27 | 2020-07-03 | 高通股份有限公司 | Priority rules for signal repetition collisions |
| CN111586854A (en) * | 2019-02-15 | 2020-08-25 | 电信科学技术研究院有限公司 | Transmission method, terminal and network equipment of physical uplink shared channel |
| CN111615184A (en) * | 2019-04-22 | 2020-09-01 | 维沃移动通信有限公司 | Processing method and terminal |
| CN111713152A (en) * | 2018-02-13 | 2020-09-25 | 华为技术有限公司 | Communication method and device |
| CN111757496A (en) * | 2019-03-29 | 2020-10-09 | 华为技术有限公司 | Communication method and device |
| CN112020149A (en) * | 2019-05-29 | 2020-12-01 | 成都鼎桥通信技术有限公司 | Method and equipment for avoiding PUSCH (physical uplink shared channel) and PUCCH (physical uplink control channel) collision |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108702768B (en) * | 2018-04-24 | 2023-03-31 | 北京小米移动软件有限公司 | Scheduling request transmission method and device and resource allocation method and device |
| CN111585722B (en) * | 2019-02-15 | 2022-05-24 | 大唐移动通信设备有限公司 | Transmission method, terminal and network equipment of physical uplink shared channel |
| CN111586759B (en) * | 2019-02-15 | 2022-10-18 | 大唐移动通信设备有限公司 | Transmission method and equipment |
| WO2020196546A1 (en) * | 2019-03-25 | 2020-10-01 | Sharp Kabushiki Kaisha | COLLISION HANDLING and UCI MULTIPLEXING for URLLC PUCCH and eMBB PUSCH |
| US11589372B2 (en) * | 2019-04-09 | 2023-02-21 | Qualcomm Incorporated | Handling collisions between uplink data repetitions and an uplink control transmission |
| CN112311517A (en) * | 2020-10-16 | 2021-02-02 | 紫光展锐(重庆)科技有限公司 | Uplink information sending method and related product |
-
2020
- 2020-10-16 CN CN202011122872.7A patent/CN112311517A/en active Pending
-
2021
- 2021-10-12 WO PCT/CN2021/123243 patent/WO2022078321A1/en active Application Filing
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111373823A (en) * | 2017-11-27 | 2020-07-03 | 高通股份有限公司 | Priority rules for signal repetition collisions |
| CN111713152A (en) * | 2018-02-13 | 2020-09-25 | 华为技术有限公司 | Communication method and device |
| CN110351757A (en) * | 2018-04-04 | 2019-10-18 | 电信科学技术研究院有限公司 | A kind of scheduling request transmission method, terminal and network side equipment |
| CN111294936A (en) * | 2018-12-06 | 2020-06-16 | 电信科学技术研究院有限公司 | Transmission method and terminal |
| CN111586854A (en) * | 2019-02-15 | 2020-08-25 | 电信科学技术研究院有限公司 | Transmission method, terminal and network equipment of physical uplink shared channel |
| CN111757496A (en) * | 2019-03-29 | 2020-10-09 | 华为技术有限公司 | Communication method and device |
| CN111615184A (en) * | 2019-04-22 | 2020-09-01 | 维沃移动通信有限公司 | Processing method and terminal |
| CN112020149A (en) * | 2019-05-29 | 2020-12-01 | 成都鼎桥通信技术有限公司 | Method and equipment for avoiding PUSCH (physical uplink shared channel) and PUCCH (physical uplink control channel) collision |
Non-Patent Citations (4)
| Title |
|---|
| ""R1-161249 Collision Handling Summary"", 《3GPP TSG_RAN\WG1_RL1》 * |
| ""R1-1808754 PUCCH"", 《3GPP TSG_RAN\WG1_RL1》 * |
| ERICSSON: "R1-156413 "PUSCH definition for MTC"", 《3GPP TSG_RAN\WG1_RL1》 * |
| HUAWEI等: "R1-151267 "PUCCH and UCI for MTC and coverage enhancement"", 《3GPP TSG_RAN\WG1_RL1》 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2022078321A1 (en) * | 2020-10-16 | 2022-04-21 | 紫光展锐(重庆)科技有限公司 | Uplink information sending method and related product |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2022078321A1 (en) | 2022-04-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2020248259A1 (en) | Random access method, terminal device and network device | |
| CA3137983A1 (en) | Random access method and communications apparatus | |
| WO2022078321A1 (en) | Uplink information sending method and related product | |
| WO2020215262A1 (en) | Power allocation method and terminal device | |
| WO2020191679A1 (en) | Random access method, terminal device, and network device | |
| JP2019531009A (en) | Data transmission method, terminal device and network side device | |
| WO2021087929A1 (en) | Random access method and apparatus | |
| US20230026332A1 (en) | Wireless communication method and communication apparatus | |
| US20230013617A1 (en) | Method for sending media access control control element and terminal device | |
| CN114286397A (en) | Transmission link switching method and related product | |
| WO2021062869A1 (en) | Radio communication method and terminal device | |
| WO2020206658A1 (en) | Wireless communication method, terminal apparatus, and network apparatus | |
| US20220231824A1 (en) | Data transmission method, apparatus, and device, and storage medium | |
| EP4224920A1 (en) | Bsr triggering method for relay, and related product | |
| WO2021169840A1 (en) | Transmission method using preconfigured resource, and related apparatus | |
| CN114765506B (en) | PSFCH transmission method and device for auxiliary link and computer readable storage medium | |
| AU2020428979B2 (en) | Method for determining transport block size and communication apparatus | |
| CN113965955A (en) | Selection method of communication resource conflict and related product | |
| WO2022152329A1 (en) | Psfch transmission method and device for sidelink, and storage medium | |
| WO2022110178A1 (en) | Transmission method and terminal device | |
| WO2021196147A1 (en) | Information transmission method, terminal device and network device | |
| WO2022068416A1 (en) | Feedback information transmission method and communication device | |
| CN114337961A (en) | Method for transmitting resource by uplink channel and related product | |
| CN114339934A (en) | Relay selection method based on service and related product | |
| CN114257345A (en) | Method for confirming HARQ-ACK feedback time and related product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210202 |
|
| RJ01 | Rejection of invention patent application after publication |