Movatterモバイル変換


[0]ホーム

URL:


CN112806053A - Communication method and terminal device - Google Patents

Communication method and terminal device
Download PDF

Info

Publication number
CN112806053A
CN112806053ACN201980065737.2ACN201980065737ACN112806053ACN 112806053 ACN112806053 ACN 112806053ACN 201980065737 ACN201980065737 ACN 201980065737ACN 112806053 ACN112806053 ACN 112806053A
Authority
CN
China
Prior art keywords
logical channel
report
mac pdu
mac
channel
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.)
Granted
Application number
CN201980065737.2A
Other languages
Chinese (zh)
Other versions
CN112806053B (en
Inventor
徐婧
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
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 Guangdong Oppo Mobile Telecommunications Corp LtdfiledCriticalGuangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN112806053ApublicationCriticalpatent/CN112806053A/en
Application grantedgrantedCritical
Publication of CN112806053BpublicationCriticalpatent/CN112806053B/en
Activelegal-statusCriticalCurrent
Anticipated expirationlegal-statusCritical

Links

Images

Classifications

Landscapes

Abstract

The embodiment of the application provides a communication method and terminal equipment, which can enable a triggered report to be reported to a network side in time, so that the communication performance is improved. The method comprises the following steps: and when the first MAC PDU is transmitted on the first uplink channel resource, canceling a first report, wherein the first report is used for generating a first MAC CE contained in the first MAC PDU.

Description

Communication method and terminal deviceTechnical Field
The embodiment of the application relates to the technical field of communication, in particular to a communication method and terminal equipment.
Background
In a wireless communication system, there may be resource conflicts among multiple grants (grants) for a terminal device, in which case the terminal device performs transmissions for one of the grants.
Media Access Control (MAC) Protocol Data Unit (PDU) transmitted on the grant may encapsulate a Report of a MAC layer, for example, a Buffer State Report (BSR), however, in the above-mentioned scenario of resource conflict, when the BSR is encapsulated into one of the authorized MAC PDUs, the BSR will be cancelled and will not be encapsulated into another authorized MAC PDU, if the other authorized MAC PDU is transmitted on the conflicting resource, because the MAC Control Element (CE) of the BSR is not encapsulated in the other authorized MAC PDU, the BSR is not reported to the network side in time, thereby affecting the communication performance between the terminal device and the network.
Disclosure of Invention
The embodiment of the application provides a communication method and terminal equipment, which can enable a triggered report to be reported to a network side in time, so that the communication performance is improved.
In a first aspect, a communication method is provided, including:
and when the first MAC PDU is transmitted on the first uplink channel resource, canceling a first report, wherein the first report is used for generating a first MAC CE contained in the first MAC PDU.
In a second aspect, a terminal device is provided for executing the method in the first aspect.
In particular, the terminal device comprises functional modules for performing the method in the first aspect described above.
In a third aspect, a terminal device is provided that includes a processor. The processor is configured to call and execute a computer program stored in the memory to perform the method of the first aspect.
In a fourth aspect, a chip is provided for implementing the method in the first aspect.
Specifically, the chip includes: a processor for calling and running the computer program from the memory so that the device in which the chip is installed performs the method as in the first aspect described above.
In a fifth aspect, a computer-readable storage medium is provided for storing a computer program for causing a computer to perform the method of the first aspect.
In a sixth aspect, there is provided a computer program product comprising computer program instructions for causing a computer to perform the method of the first aspect.
In a seventh aspect, there is provided a computer program which, when run on a computer, causes the computer to perform the method of the first aspect.
In the embodiment of the present application, when the first MAC PDU is transmitted, the first report used for generating the first MAC CE included in the first MAC PDU is cancelled, instead of when the MAC PDU is generated, the first report is cancelled, so that a problem that the first report cannot be reported to the network side due to the fact that the first MAC PDU is not transmitted can be avoided.
Drawings
Fig. 1 is a schematic diagram of a communication system architecture provided in an embodiment of the present application.
Fig. 2 is a schematic diagram of an authorization transmission provided in an embodiment of the present application.
Fig. 3 is a schematic flow chart of a communication method provided in an embodiment of the present application.
Fig. 4 is a schematic structural diagram of a MAC PDU provided in an embodiment of the present application.
Fig. 5 is a schematic structural diagram of a subheader of a MAC CE according to an embodiment of the present application.
Fig. 6 is a schematic structural diagram of a MAC CE according to an embodiment of the present application.
Fig. 7 is a schematic structural diagram of a MAC CE according to an embodiment of the present application.
Fig. 8 is a schematic structural diagram of a MAC CE according to an embodiment of the present application.
Fig. 9 is a schematic structural diagram of a MAC CE according to an embodiment of the present application.
Fig. 10 is a schematic structural diagram of a MAC CE according to an embodiment of the present application.
Fig. 11 is a schematic structural diagram of a MAC CE according to an embodiment of the present application.
Fig. 12 is a schematic diagram of an authorization transmission provided by an embodiment of the present application.
Fig. 13 is a schematic diagram of an authorization transmission provided by an embodiment of the present application.
Fig. 14 is a schematic block diagram of a terminal device according to an embodiment of the present application.
Fig. 15 is a schematic block diagram of a communication device according to an embodiment of the present application.
Fig. 16 is a schematic block diagram of a communication device according to an embodiment of the present application.
Detailed Description
Technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The technical scheme of the embodiment of the application can be applied to various communication systems, 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 LTE Frequency Division Duplex (FDD) System, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication System, or a 5G System.
Illustratively, acommunication system 100 applied in the embodiment of the present application is shown in fig. 1. Thecommunication system 100 may include anetwork device 110, and thenetwork device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal, a terminal).Network device 110 may provide communication coverage for a particular geographic area and may communicate with terminal devices located within that coverage area. Optionally, theNetwork device 110 may be a Base Transceiver Station (BTS) in a GSM system or a CDMA system, a Base Station (NodeB, NB) in a WCDMA system, an evolved Node B (eNB or eNodeB) in an LTE system, or a wireless controller in a Cloud Radio Access Network (CRAN), or may be a Network device in a Mobile switching center, a relay Station, an Access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a Network-side device in a 5G Network, or a Network device in a Public Land Mobile Network (PLMN) for future evolution, or the like.
Thecommunication system 100 further comprises at least oneterminal device 120 located within the coverage area of thenetwork device 110. As used herein, "terminal equipment" includes, but is not limited to, connections via wireline, such as Public Switched Telephone Network (PSTN), Digital Subscriber Line (DSL), Digital cable, direct cable connection; and/or another data connection/network; and/or via a Wireless interface, e.g., to a cellular Network, a Wireless Local Area Network (WLAN), a digital television Network such as a DVB-H Network, a satellite Network, an AM-FM broadcast transmitter; and/or means of another terminal device arranged to receive/transmit communication signals; and/or Internet of Things (IoT) devices. A terminal device arranged to communicate over a wireless interface may be referred to as a "wireless communication terminal", "wireless terminal", or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular telephones; personal Communications Systems (PCS) terminals that may combine cellular radiotelephones with data processing, facsimile, and data Communications capabilities; PDAs that may include radiotelephones, pagers, internet/intranet access, Web browsers, notepads, calendars, and/or Global Positioning System (GPS) receivers; and conventional laptop and/or palmtop receivers or other electronic devices that include a radiotelephone transceiver. Terminal Equipment may refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, remote terminal, mobile device, User terminal, wireless communication device, User agent, or User Equipment. An access terminal may be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device having Wireless communication capabilities, a computing device or other processing device connected to a Wireless modem, a vehicle mounted device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.
Optionally, a Device to Device (D2D) communication may be performed between theterminal devices 120.
Alternatively, the 5G system or the 5G network may also be referred to as a New Radio (NR) system or an NR network.
Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, thecommunication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device, which is not limited in this embodiment of the present application.
Optionally, thecommunication system 100 may further include other network entities such as a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that a device having a communication function in a network/system in the embodiments of the present application may be referred to as a communication device. Taking thecommunication system 100 shown in fig. 1 as an example, the communication device may include anetwork device 110 and aterminal device 120 having a communication function, and thenetwork device 110 and theterminal device 120 may be the specific devices described above and are not described herein again; the communication device may also include other devices in thecommunication system 100, such as other network entities, for example, a network controller, a mobility management entity, and the like, which is not limited in this embodiment.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
During the communication between the terminal device and the network device, the network device may assign an authorization to the terminal device, and the assigned authorization may include a configuration authorization (Configured Grant) and/or a dynamic authorization. The configuration authorization may be configured by the network device to the terminal device semi-statically, and the dynamic authorization may be dynamically scheduled by the network device to the terminal device, for example, may be scheduled to the terminal device through Downlink Control Information (DCI). Each grant may correspond to a resource for transmitting a MAC PDU. In the embodiments of the present application, authorization may also be understood as a resource.
On the terminal device side, there may be a case where multiple authorized resources conflict. The resource conflict of multiple grants may mean that resources occupied by multiple grants are completely the same, or that the resources occupied by multiple grants partially overlap.
In the case of resource conflicts with multiple grants of a terminal device, the terminal device will perform a transmission for one of the grants.
For example, as shown in fig. 2, DCI1 and DCI2 allocategrant 1 and grant 2 to the terminal device, respectively, wheregrant 1 and grant 2 have overlapping resources, where the time of the group packet of MAC PDU1 forgrant 1 is earlier than the time of the group packet of MAC PDU2 for grant 2 (at this time, the start position occupied bygrant 1 in the time domain may be earlier than the time domain position occupied by grant 2 in the time domain, and/or the time domain length ofgrant 1 may be longer than the time domain length of grant 2), if the priority of the traffic of grant 2 is higher than that of the traffic ofgrant 1, the MAC PDU2 will be transmitted on grant 2, and the MAC PDU1 will be dropped or wait for the subsequent grant to be transmitted.
On the terminal device side, when new uplink data arrives (i.e., new uplink data is generated), in the MAC layer, generating a BSR may be triggered, where the BSR may be used to generate a MAC CE, and the MAC CE may be encapsulated in a MAC PDU.
For example, as shown in fig. 2, before the MAC PDU1 is packed, BSR1 is triggered by the arrival of new uplink data, the MAC CE of BSR1 may be encapsulated in MAC PDU1, and when the MAC PDU1 is packed, the BSR1 may be cancelled.
And as shown in fig. 2, the MAC PDU2 can be encapsulated for grant 2, at which point the terminal device can transmit the MAC PDU2 on grant 2 and discard the MAC PDU1 or buffer the MAC PDU1 for subsequent transmission, since the priority of the traffic for grant 2 is higher compared to the priority of the traffic forgrant 1.
This implementation may ensure that the service with high priority can be transmitted in time, but if the MAC CE of the BSR is encapsulated into the MAC PDU of the service with low priority, such as the BSR is encapsulated into the MAC PDU1 described above, but not into the MAC PDU2, the BSR cannot be reported to the network side.
Based on this, the embodiments of the present application provide the following scheme, which can avoid the problem that a triggered report, for example, a BSR, cannot be reported to the network side, thereby improving communication performance.
Fig. 3 is a schematic flow chart diagram of acommunication method 200 according to an embodiment of the present application. Themethod 200 includes at least some of the following.
In 210, when transmitting a first MAC PDU on a first uplink channel resource, a terminal device cancels a first report, where the first report is used to generate a first MAC CE included in the first MAC PDU.
Specifically, the terminal device may generate a first MAC CE based on the first report, encapsulate the first MAC CE into a first MAC PDU, and transmit the first MAC PDU on the first uplink channel resource, and when transmitting the first MAC PDU on the first uplink channel resource, the terminal device may cancel the first report.
The timing of canceling the first report may be performed from a starting point of transmitting the first MAC PDU, or may be performed at an intermediate time point of transmitting the first MAC PDU, or may be performed at a time point of ending transmission of the first MAC PDU.
Optionally, the Uplink Channel resources (e.g., the first Uplink Channel resource and the second Uplink Channel resource) in the embodiment of the present application may be a Physical Uplink Shared Channel (PUSCH).
Alternatively, the report mentioned in the embodiment of the present application (which may be the first report mentioned above, the second report mentioned below, and the third report) may be a MAC layer triggered report. The Report in the embodiment of the present application may specifically be a BSR, a Power Headroom Report (PHR), or a configuration authorization confirmation.
Optionally, the BSR in the embodiment of the present application may be classified as a retransmission BSR, a periodic BSR, a padding BSR, (padding BSR), a long BSR, (long BSR), a short BSR, (short BSR), or a truncated BSR (truncated BSR). The Truncated BSR may be further divided into a short Truncated BSR (short Truncated BSR) or a long Truncated BSR (long Truncated BSR).
Optionally, the PHR in the embodiment of the present application may be a periodic PHR.
Optionally, the configuration authorization confirmation in this embodiment may be a report confirming that the network device confirms the configuration authorization, the activation authorization, or the deactivation authorization to the terminal device.
Optionally, the report in the embodiment of the present application may be a report triggered periodically or a report triggered by a special event.
Taking the report as a BSR as an example, the BSR may be a report triggered periodically, or may also be a report triggered by the arrival of uplink data.
The MAC PDU in the embodiment of the present application may include a plurality of MAC sub-PDUs, where the MAC sub-PDUs may include a Service Data Unit (SDU) and a sub-header thereof, or may include a MAC CE and a sub-header thereof, where the MAC CE may be a fixed-size MAC CE or a variable-length MAC CE, for example, as shown in fig. 4.
And as shown in fig. 5, the subheader of the MAC CE may include a Logical Channel Identity (LCID), where the LCID is used to distinguish what type of report the MAC CE corresponds to, for example, a long BSR, a short BSR, a PHR, or the like. Where R in fig. 5 represents a reserved bit, L represents a byte length occupied by the corresponding MAC CE, F represents a size of a length field (of the MAC CE),
as shown in fig. 6 and 7, the MAC CE may include a Logical Channel Group (LCG) identifier (Identity, ID) and a buffer size of the logical Channel Group, where fig. 6 shows a format of the MAC CE of the short BSR or the truncated BSR, that is, an identifier of a logical Channel Group and a buffer size thereof; fig. 7 shows the format of the MAC CE of the long BSR or the long truncated BSR, i.e. the identity of the group of multiple logical channels and their buffer size.
Optionally, the report in this embodiment may be a report triggered based on a Logical Channel (LC) or a logical Channel group, and may also be referred to as a report of a per logical Channel or a logical Channel group.
Optionally, in this embodiment of the present application, a logical channel or a logical channel group may correspond to a service, for example, one service may correspond to at least one logical channel or a logical channel group, and different services may correspond to logical channels or logical channel groups that are completely different.
In the embodiment of the present application, all logical channels in one logical channel group may correspond to the same service, or may correspond to different services.
The categories of the logical channels in the embodiment of the present application may be divided according to the corresponding services, for example, the logical channels corresponding to the same service (where the logical channels may be a logical channel group) may be the same type of logical channels, or the logical channel group including the same service may be the same type of logical channel group, or the categories of the logical channels may also be divided based on the logical channel group to which the logical channels belong, for example, the logical channels belonging to the same logical channel group may be the same type of logical channels.
Wherein, the report triggered based on the logical channel or the logical channel group can be understood as: the reporting is based on service triggered reporting, and the logical channel or logical channel group mentioned here is the logical channel or logical channel group corresponding to the service. Service-based triggering may also be referred to as reporting is per-service.
Optionally, the information carried in the report is information based on a service, where the service is a service of a certain logical channel or logical channel group, and the logical channel or logical channel to which the report belongs is the certain logical channel or logical channel group.
Optionally, in this embodiment of the present application, the reported MAC CE may carry an identifier (LCID) of the logical Channel on which the MAC CE is based.
For example, as shown in fig. 8 and 9, the MAC CE may carry an identifier of a logical channel to which the report belongs. Fig. 8 illustrates information of buffer sizes of one logical channel encapsulated in the MAC CE. Fig. 9 illustrates information of buffer sizes of a plurality of logical channels encapsulated in the MAC CE. The plurality of logical channels in fig. 9 may be a type of logical channel, and may correspond to the same service, for example.
Fig. 9 shows information of buffer sizes of 8 logical channels, and if the number of logical channels of a service is less than 8 or there are less than 8 logical channels with buffered data, the MAC CE may carry the identifier of the logical channel less than 8 and its buffer size. At this time, the size of the MAC CE may be variable.
For example, as shown in fig. 10, the identifiers of 5 logical channels and their buffer sizes may be carried, and the other bit positions may be reserved bits R.
Or, in this embodiment of the present application, when the report is based on the service trigger, and a service may correspond to at least one logical channel group, the identification information of the at least one logical channel group and the buffer size thereof may be carried in the MAC CE.
For example, as shown in fig. 11, the logical channel groups corresponding to the services may be 4, the identifiers of the 4 logical channel groups and the buffer sizes thereof may be carried in the MAC CE, and the other bits may be reserved bits.
Optionally, in this embodiment of the present application, the first report is a report of a first logical channel, and the first report is triggered when a condition for triggering the report of the first logical channel is satisfied.
Wherein the condition for triggering reporting of the first logical channel comprises at least one of:
1) the first logical channel or the logical channel group to which the first logical channel belongs has data to be transmitted.
2) The first logical channel has data to be transmitted, and the logical channels except the first logical channel in the logical channel group to which the first logical channel belongs have no data to be transmitted.
3) The first logic channel has data to be transmitted, and a fourth logic channel in a logic channel group to which the first logic channel belongs has data to be transmitted, and the priority of the fourth logic channel is lower than that of the first logic channel.
4) The first uplink channel resource is allocated for transmitting data of the first logical channel or a logical channel group to which the first logical channel belongs.
5) The number of bits remaining after data transmission in the first uplink resource channel resource is greater than or equal to a first value, where the first value is the number of bits occupied by the first MAC CE and the subheader of the first MAC CE.
6) The retransmission report timer of the first logical channel or the logical channel group to which the first logical channel belongs is expired.
7) The periodic report timer of the first logical channel or the logical channel group to which the first logical channel belongs is expired.
Optionally, in this embodiment of the present application, the logical channel of the first report and the logical channel to which the data of the first grant bearer belongs are the same logical channel or the same type of logical channel, or the first grant can satisfy a logical channel priority mapping limitation configured for the logical channel of the first report, where the first grant is a grant corresponding to the first MAC PDU.
Specifically, when a certain type of logical channel or a grant of a certain logical channel encapsulates a MAC PDU, a report of the logical channel of the certain type of logical channel may be encapsulated into the MAC PDU.
The logical channel priority mapping restriction of a logical channel or a logical channel group may indicate a requirement or restriction on an authorization when information in the logical channel or the logical channel group is transmitted by using the authorization, and data or information in the logical channel or the logical channel group may be transmitted on the authorization if the authorization meets the requirement or restriction.
Therefore, the reporting of the first report to the network side through the MAC PDU which has the same logical channel or the same kind of logical channel as the first report in the embodiment of the present application can be understood as: and reporting the first report to the network side through the MAC PDU with the same service as the first report.
The first grant mentioned in the embodiment of the present application can satisfy the logical channel priority mapping restriction configured for the logical channel or the logical channel group associated with the first report, that is, it can be understood as: the logical channel priority mapping restriction of the first reported logical channel or logical channel group matches the first grant (which may specifically be an attribute of the first grant).
Optionally, in this embodiment of the present application, when the first MAC PDU is transmitted on the first uplink channel resource or before the first MAC PDU is transmitted, the terminal device cancels a second report, where the second report is triggered between the grouping of the first MAC PDU and the transmission of the first MAC PDU on the first uplink channel resource.
Specifically, since the second report is triggered after the first MAC PDU group package and before the first MAC PDU is transmitted, compared with the first report, the second report may be some reports that are duplicated to the information content of the first report or reports that contain useless information, for example, the second report is a retransmission BSR, a periodic BSR, or a padding BSR, the second report may be cancelled, specifically, the second report may be cancelled when the first MAC PDU is transmitted on the first uplink channel resource, or, since the second report is a relatively useless report, the second report may be cancelled before the first MAC PDU is transmitted, of course, the second report may also be cancelled after the first MAC PDU is transmitted, which is not limited in the embodiment of the present application.
Wherein the second report is optionally a report satisfying the following condition: have the same kind of logical channel or the same logical channel as the first report. The first report and the second report have the same type of logical channel or the same logical channel may mean that the services to which the first report and the second report belong are the same, or may mean that the first report and the second report have the same type of logical channel or information in the same logical channel, or may mean that the first report and the second report have the same type of logical channel group or information in the same logical channel group.
Specifically, the first report and the second report have the same kind of logical channel or the same logical channel, and the second report usually contains some duplicated information with respect to the first report, and at this time, the first report may be cancelled.
Wherein, the first report and the second report have the same kind of logical channel or the same logical channel, it can be understood that the first report and the second report are reports of the same service respectively.
In the embodiment of the present application, the logical channel or the logical channel group that the first report has may be referred to as: the logical channel or logical channel group to which the first report belongs, the logical channel or logical channel group of the first report, or the logical channel or logical channel group with which the first report is associated.
Optionally, in this embodiment of the present application, the report is associated with a logical channel group, which may mean that the report includes information in the logical channel. And, reporting is associated with a logical channel group, which may refer to reporting information in logical channels that include all or part of the logical channel group.
Alternatively, in the embodiment of the present application, the report is associated with the logical channel group, and may refer to that the report includes information of a service corresponding to the logical channel. And, reporting is associated with a logical channel group, which may refer to reporting information including traffic corresponding to all or part of the logical channels in the logical channel group.
The service mentioned in the embodiment of the present application may be enhanced Mobile bandwidth (eMBB) service, massive Machine-Type Communications (mtc) service, ultra-Reliable Low latency Communications (urlclc) service, and Industrial Internet of Things (IIoT) service.
Optionally, in this embodiment of the present application, the terminal device may reserve a third report until a second MAC PDU is transmitted on a second uplink channel resource, where the second MAC PDU includes a second MAC CE generated based on the third report; the third report is triggered between packing the first MAC PDU with a packet and transmitting the first MAC PDU on the first uplink channel resource.
Specifically, a third report is triggered between the first MAC PDU grouping and the transmission of the first MAC PDU on the first uplink channel resource, and the third report may also be retained until the second MAC PDU encapsulating the MAC CE of the third report is transmitted on the second uplink channel resource.
Wherein the third report may not be cancelled when the third report is a report satisfying at least one of the following conditions:
triggered by the arrival of upstream data;
a second logical channel having a non-first logical channel, or a third logical channel that is not of the same class as the first logical channel, the first logical channel being a logical channel to which the first report belongs.
Specifically, if the third report is triggered by the arrival of uplink data, the information of the third report is relatively useful for the terminal device, and the terminal device can request the network device for authorization by reporting the BSR to the network device.
And if the first report and the third report have different logical channels or different classes of logical channels, the third report represents that the third report is a report triggered by other services, and the third report is not a repeat of the first report, so that the third report needs to be reported to the network side.
Optionally, in this embodiment of the present application, the first uplink channel resource is configured to transmit a MAC PDU of a first grant and a second grant; the first granted MAC PDU is the first MAC PDU; the second granted MAC PDU is a third MAC PDU, the third MAC PDU is packed before the first MAC PDU and is not transmitted on the first uplink channel resource, and the third MAC PDU includes the first MAC CE.
Specifically, as mentioned above, in the case that there is a resource conflict among multiple authorized resources, the terminal device may transmit one authorized first MAC PDU on the conflicted resource, even if a second authorized third MAC PDU exists before the first MAC PDU and encapsulates the first report, since the first report is not cancelled, the terminal device may generate a MAC CE based on the first report to encapsulate into the first MAC PDU, so that it may be realized that the first report may be reported to the network side through the first MAC PDU even if the previous third MAC PDU is not transmitted.
The grant mentioned in the embodiment of the present application may be a configured grant or a dynamic grant, where the configured grant may be configured semi-statically by the network device, for example, may be configured through RRC signaling, and the dynamic grant may be scheduled by the network device to the terminal device through DCI.
For example, to more clearly understand the present application, the first report is taken as a BSR as an example, and the embodiment of the present application is described below with reference to fig. 1.
As shown in fig. 2, DCI1 and DCI2 allocategrant 1 and grant 2 to a terminal device, respectively, and a resource ofgrant 1 and a resource of grant 2 may have overlapping resources, assuming that the priority of grant 2 is higher than the priority ofgrant 1.
When a certain condition is met, for example, when new uplink data arrives, BSR1 will be triggered, BSR MAC CE generated based on BSR1 will be encapsulated into MAC PDU1, and MAC PDU1 is a MAC PDU forgrant 1.
Assuming thatgrant 1 has a higher priority than grant 2, the terminal device may transmit MAC PDU1 containing BSR MAC CE ongrant 1 and may cancel the BSR when transmitting this MAC PDU1, wherein, since MAC PDU2 for grant 2 will not be transmitted, there may be no need to encapsulate the BSR MAC CE into MAC PDU2 or may not generate MAC PDU 2.
Assuming that grant 2 has a higher priority thangrant 1, since the BSR1 has not been cancelled, a MAC CE may be generated based on the BSR1 and encapsulated into a MAC PDU2, a MAC PDU2 including the MAC CE of BSR1 is transmitted on grant 2, and the BSR is cancelled when transmitting MAC PDU 2.
Assuming that a new BSR2 exists after the grouping ofMAC PDUs 1 and before the transmission of a MAC PDU (MAC PDU1 or MAC PDU2) ongrant 1, the new BSR may or may not be cancelled when transmitting data ongrant 1.
For example, if the BSR2 is a retransmitted BSR, a periodic BSR, or a padding BSR, the BSR2 may be cancelled.
For example, if the BSR2 is a BSR triggered by the arrival of new uplink data, the BSR2 is not cancelled, and when waiting for encapsulating the MAC PDU3 for the next grant, a MAC CE is generated based on the BSR2 and encapsulated in the MAC PDU 3.
It should be understood that, in the embodiment of the present application, when the BSR2 arrives due to new uplink data, if the BSR2 is triggered after the MAC PDU1 is packed and before the MAC PDU2 is packed, and the MAC PDU2 is transmitted on grant 2, the MAC CE of the BSR2 may be encapsulated into the MAC PDU2 together with the MAC CE of the BSR1, or at least one of the two may be encapsulated into the MAC PDU2, or the MAC CE of the BSR2 may be encapsulated into the MAC PDU 2.
If the remaining bits of the uplink data transmitted byresource 1 are not enough to encapsulate the MAC CE and its subheader of BSR1 and the MAC CE and its subheader of BSR2 at the same time, only the MAC CE and its subheader of BSR1, or only the MAC CE and its subheader of BSR2, specifically which BSR MAC CE and its subheader are encapsulated, may be determined according to the priority of the BSR, and the priority of the BSR may be determined based on the priority of the logical channel or logical channel group to which the BSR belongs. Alternatively, the MAC CE of the previous BSR may be encapsulated, i.e., the MAC CE encapsulating BSR1 is in MAC PDU 2. Alternatively, the MAC CE of the following BSR may be encapsulated, i.e., the MAC CE of the encapsulated BSR2 is in the MAC PDU 2. MAC CEs inBSRs 1 and 2 that are not encapsulated can be encapsulated into the next authorized MAC PDU 3.
The above description is given by taking an example of overlapping two authorized resources, but it should be understood that the embodiments of the present application are also applicable to a scenario where more than two authorized resources overlap.
The above describes a scheme of how to cancel the report when the granted resources overlap, and how to perform the cancellation of the report in the case where the granted resources do not overlap will be described below.
As shown in fig. 12, the network device allocatesgrant 1 and grant 2 to the terminal device through DCI1 and DCI2, respectively, andresource 1 ofgrant 1 and resource 2 of grant 2 are non-overlapping resources. Since there are no overlapping resources forgrant 1 and grant 2, the MAC PDU1 encapsulated forgrant 1 may be sent onresource 1 and the MAC PDU2 encapsulated for grant 2 may be sent on resource 2, respectively.
When a certain condition is met, for example, when new uplink data arrives, BSR1 will be triggered, the MAC CE generated based on BSR1 will be encapsulated into MAC PDU1, MAC PDU1 is transmitted onresource 1 ofgrant 1, and BSR1 is cancelled when MAC PDU1 is transmitted.
Assuming that there is no new BSR after the MAC PDU1 package and before the MAC PDU2 package, the MAC CE of the BSR may not be included in the MAC PDU 2.
Or even if there is a new BSR before the MAC PDU2 group package after the MAC PDU1 group package, if the new BSR is a periodic BSR, a retransmitted BSR or a padding BSR, the new BSR may not be encapsulated in the MAC PDU 2. Where these new BSRs may be cancelled when triggered, or may also be cancelled when MAC PDU1 is transmitted onresource 1.
If, as shown in fig. 13, the BSR2 is triggered after the MAC PDU1 is packed inpacket 1 and before the MAC PDU2 is packed, the BSR2 is triggered by the arrival of new uplink data, the MAC CE of the BSR2 may be encapsulated in the MAC PDU2, and the BSR2 is cancelled when the MAC PDU2 is transmitted on resource 2.
In the embodiment of the present application, it is mentioned that the report may be triggered based on a logical channel, that is, the report may be triggered based on a per logical channel or a per service, and the manner of canceling the reports may not be limited to canceling the above-mentioned cancellation when the MAC PDU of the MAC CE encapsulating the report is transmitted, for example, the cancellation may be cancelled when the MAC PDU is encapsulated, or may be cancelled after the MAC PDU is encapsulated and before the MAC PDU is transmitted.
In the embodiment of the present application, when the first MAC PDU is transmitted, the first report used for generating the first MAC CE included in the first MAC PDU is cancelled, instead of when the MAC PDU is generated, the first report is cancelled, so that a problem that the first report cannot be reported to the network side due to the fact that the first MAC PDU is not transmitted can be avoided.
Specifically, when the first report is the BSR, the transmission requirement of the terminal device may be reported to the network side in time, so that the network device side may schedule the terminal device in time, and particularly when the BSR is a BSR based on a specific service (e.g., URLLC service), the QoS of the service may be ensured.
It should be understood that themethod 200 described above is merely a specific implementation of the present application, and that embodiments of the present application may have other implementations.
For example, when the terminal device cancels the first report used for generating the first MAC CE included in the first MAC PDU when transmitting the first MAC PDU on the first uplink channel resource as mentioned above, in this embodiment of the present application, if the terminal device determines that no grant other than the grant of the first MAC PDU exists on the first uplink channel resource, the first report may be cancelled when determining that this fact is true, for example, when or before the terminal device encapsulates the first MAC PDU, the terminal device determines that no grant other than the grant of the first MAC PDU exists on the first uplink channel resource, the terminal device cancels the first report when encapsulating the first MAC PDU; for example, if the terminal device determines that no grant other than the grant of the first MAC PDU exists on the first uplink channel resource after encapsulating the first MAC PDU, the first report may be cancelled when it determines that no grant other than the grant of the first MAC PDU exists on the first uplink channel resource.
Or, in the embodiment of the present application, even if the first uplink channel is used for multiple grants including the grant of the first MAC PDU, if the terminal device determines that the priority of the grant of the first MAC PDU is highest, the terminal device may cancel the first report when determining that the priority of the grant of the first MAC PDU is highest; if the terminal device determines that the priority of the grant of the first MAC PDU is highest before performing encapsulation of the first MAC PDU, the first report may be cancelled when performing encapsulation of the first MAC PDU.
Fig. 14 is a schematic block diagram of a terminal device 400 according to an embodiment of the present application. The terminal device 400 comprises a cancellingunit 410 for:
when a first Media Access Control (MAC) Protocol Data Unit (PDU) is transmitted on a first uplink channel resource, a first report is cancelled, wherein the first report is used for generating a first MAC CE contained in the first MAC PDU.
Optionally, in this embodiment of the present application, the first report is a buffer status report BSR, a power headroom report PHR, or a configuration authorization confirmation.
Optionally, in this embodiment of the present application, the cancelingunit 410 is further configured to:
canceling a second report triggered between packing the first MAC PDU with the packet and transmitting the first MAC PDU on the first uplink channel resource at or before transmitting the first MAC PDU.
Optionally, in an embodiment of the present application, the second report is a report satisfying the following condition: belonging to the same class of logical channels or the same logical channel as the first report.
Optionally, in an embodiment of the present application, the second report includes at least one of: retransmission BSR, periodic BSR, padding BSR, periodic PHR.
Optionally, in this embodiment of the present application, as shown in fig. 14, the terminal device 400 further includes a reservingunit 420, configured to:
reserving a third report until a second MAC PDU is transmitted on a second uplink channel resource, wherein the second MAC PDU comprises a second MAC CE generated based on the third report;
the third report is triggered between packing the first MAC PDU with a packet and transmitting the first MAC PDU on the first uplink channel resource.
Optionally, in an embodiment of the present application, the third report satisfies at least one of the following conditions:
triggered by the arrival of upstream data;
a second logical channel that is not the first logical channel, or a third logical channel that is not of the same class as the first logical channel, the first logical channel being a logical channel to which the first report belongs.
Optionally, in this embodiment of the present application, the first uplink channel resource configuration is configured to transmit a first authorized MAC PDU and a second authorized MAC PDU;
the first granted MAC PDU is the first MAC PDU;
the second granted MAC PDU is a third MAC PDU, the third MAC PDU is packed before the first MAC PDU and is not transmitted on the first uplink channel resource, and the third MAC PDU includes the first MAC CE.
Optionally, in this embodiment of the present application, a logical channel to which the first report belongs and a logical channel to which data carried by a first grant belongs are the same logical channel or the same type of logical channel, or the first grant can satisfy a logical channel priority mapping restriction configured for a logical channel or a logical channel group associated with the first report, where the first grant is a grant corresponding to the first MAC PDU.
Optionally, in this embodiment of the present application, the first report is a report belonging to a first logical channel, and the first report is triggered when a condition for triggering the report of the first logical channel is satisfied.
Optionally, in this embodiment of the present application, the condition for triggering the report of the first logical channel includes at least one of the following:
the first logical channel or the logical channel group to which the first logical channel belongs has data to be transmitted;
the first logic channel has data to be transmitted, and the logic channels except the first logic channel in the logic channel group to which the first logic channel belongs have no data to be transmitted;
the first logic channel has data to be transmitted, and a fourth logic channel in a logic channel group to which the first logic channel belongs has data to be transmitted, wherein the priority of the fourth logic channel is lower than that of the first logic channel;
the first uplink channel resource is allocated for transmitting data of the first logical channel or a logical channel group to which the first logical channel belongs;
the number of remaining bits after data transmission in the first uplink resource channel resource is greater than or equal to a first numerical value, where the first numerical value is the number of bits occupied by the first MAC CE and the subheader of the first MAC CE;
a retransmission report timer of the first logical channel or a logical channel group to which the first logical channel belongs is expired;
the periodic report timer of the first logical channel or the logical channel group to which the first logical channel belongs is expired.
It should be understood that the terminal device 400 may be configured to implement the operations implemented by the terminal device in the foregoing method embodiments, and for brevity, no further description is provided here.
Fig. 15 is a schematic structural diagram of a communication apparatus 500 according to an embodiment of the present application. The communication apparatus 500 shown in fig. 15 includes a processor 510, and the processor 510 can call and run a computer program from a memory to implement the terminal device in the embodiment of the present application.
Optionally, as shown in fig. 15, the communication device 500 may further include a memory 520. From the memory 520, the processor 510 can call and run a computer program to implement the terminal device in the embodiment of the present application.
The memory 520 may be a separate device from the processor 510, or may be integrated into the processor 510.
Optionally, as shown in fig. 15, the communication apparatus 500 may further include a transceiver 530, and the processor 510 may control the transceiver 530 to communicate with other devices, and in particular, may transmit information or data to the other devices or receive information or data transmitted by the other devices.
The transceiver 530 may include a transmitter and a receiver, among others. The transceiver 530 may further include one or more antennas.
Optionally, the communication apparatus 500 may specifically be a network device in this embodiment, and the communication apparatus 500 may implement a corresponding process implemented by the network device in each terminal device in this embodiment, which is not described herein again for brevity.
Optionally, the communication apparatus 500 may specifically be a mobile terminal/terminal device in this embodiment, and the communication apparatus 500 may implement a corresponding process implemented by the mobile terminal/terminal device in each terminal device in this embodiment, which is not described herein again for brevity.
Fig. 16 is a schematic configuration diagram of a communication device 600 according to an embodiment of the present application. The communication device 600 shown in fig. 16 includes a processor 610, and the processor 610 can call and run a computer program from a memory to implement the method in the embodiment of the present application.
Optionally, as shown in fig. 16, the communication device 600 may further include a memory 620. From the memory 620, the processor 610 may call and run a computer program to implement the method in the embodiment of the present application.
The memory 620 may be a separate device from the processor 610, or may be integrated into the processor 610.
Optionally, the chip 600 may further include an input interface 630. The processor 610 may control the input interface 630 to communicate with other devices or chips, and in particular, may obtain information or data transmitted by other devices or chips.
Optionally, the communication device 600 may further include an output interface 640. The processor 610 may control the output interface 640 to communicate with other devices or chips, and in particular, may output information or data to the other devices or chips.
Optionally, the communication apparatus may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the communication apparatus may implement the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, and for brevity, no further description is given here.
It should be understood that the communication device mentioned in the embodiments of the present application may be a chip, which may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip.
It should be understood that the processor of the embodiments of the present application may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile 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, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double Data Rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that the above memories are exemplary but not limiting illustrations, for example, the memories in the embodiments of the present application may also be Static Random Access Memory (SRAM), dynamic random access memory (dynamic RAM, DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (enhanced SDRAM, ESDRAM), Synchronous Link DRAM (SLDRAM), Direct Rambus RAM (DR RAM), and the like. That is, the memory in the embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.
The embodiment of the application also provides a computer readable storage medium for storing the computer program.
Optionally, the computer-readable storage medium may be applied to the network device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, which is not described herein again for brevity.
Optionally, the computer-readable storage medium may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Embodiments of the present application also provide a computer program product comprising computer program instructions.
Optionally, the computer program product may be applied to the network device in the embodiment of the present application, and the computer program instructions enable the computer to execute corresponding processes implemented by the network device in the methods in the embodiment of the present application, which are not described herein again for brevity.
Optionally, the computer program product may be applied to the mobile terminal/terminal device in the embodiment of the present application, and the computer program instructions enable the computer to execute the corresponding processes implemented by the mobile terminal/terminal device in the methods in the embodiment of the present application, which are not described herein again for brevity.
The embodiment of the application also provides a computer program.
Optionally, the computer program may be applied to the network device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the network device in each method in the embodiment of the present application, and for brevity, details are not described here again.
Optionally, the computer program may be applied to the mobile terminal/terminal device in the embodiment of the present application, and when the computer program runs on a computer, the computer is enabled to execute the corresponding process implemented by the mobile terminal/terminal device in each method in the embodiment of the present application, which is not described herein again for brevity.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. 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.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, 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 through some interfaces, devices or units, and may be in an electrical, mechanical 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 functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including 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 method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (26)

CN201980065737.2A2019-03-292019-03-29Communication method and terminal deviceActiveCN112806053B (en)

Applications Claiming Priority (1)

Application NumberPriority DateFiling DateTitle
PCT/CN2019/080594WO2020199004A1 (en)2019-03-292019-03-29Communication method and terminal device

Publications (2)

Publication NumberPublication Date
CN112806053Atrue CN112806053A (en)2021-05-14
CN112806053B CN112806053B (en)2023-01-24

Family

ID=72664784

Family Applications (1)

Application NumberTitlePriority DateFiling Date
CN201980065737.2AActiveCN112806053B (en)2019-03-292019-03-29Communication method and terminal device

Country Status (2)

CountryLink
CN (1)CN112806053B (en)
WO (1)WO2020199004A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN116325994A (en)*2023-01-302023-06-23北京小米移动软件有限公司 GNSS validity period transmission method, device, equipment and storage medium

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
WO2022236681A1 (en)*2021-05-112022-11-17Oppo广东移动通信有限公司Communication method and apparatus

Citations (5)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN102264098A (en)*2010-05-312011-11-30中兴通讯股份有限公司 Method and device for buffer status report processing
EP2693821A1 (en)*2011-04-292014-02-05Huawei Technologies Co., Ltd.Data sending method, transmission resource allocation method and device
US20170019812A1 (en)*2014-03-192017-01-19Lg Electronics Inc.Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system
CN108810975A (en)*2017-05-052018-11-13华为技术有限公司The method and apparatus for being used for transmission buffer status report
CN109392147A (en)*2017-08-112019-02-26华为技术有限公司 Communication method and device

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
KR20170057227A (en)*2014-09-232017-05-24엘지전자 주식회사Method for priority handling for buffer status reporting in a d2d communication system and device therefor
CN108924877B (en)*2017-03-242022-02-11华为技术有限公司 Information processing methods and equipment
CN108809594B (en)*2017-05-052021-01-29华为技术有限公司 Method, terminal device and network device for transmitting data

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN102264098A (en)*2010-05-312011-11-30中兴通讯股份有限公司 Method and device for buffer status report processing
EP2693821A1 (en)*2011-04-292014-02-05Huawei Technologies Co., Ltd.Data sending method, transmission resource allocation method and device
US20170019812A1 (en)*2014-03-192017-01-19Lg Electronics Inc.Method and apparatus for configuring buffer status report for public safety transmission or vehicle-related transmission in wireless communication system
CN108810975A (en)*2017-05-052018-11-13华为技术有限公司The method and apparatus for being used for transmission buffer status report
CN109392147A (en)*2017-08-112019-02-26华为技术有限公司 Communication method and device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication numberPriority datePublication dateAssigneeTitle
CN116325994A (en)*2023-01-302023-06-23北京小米移动软件有限公司 GNSS validity period transmission method, device, equipment and storage medium

Also Published As

Publication numberPublication date
WO2020199004A1 (en)2020-10-08
CN112806053B (en)2023-01-24

Similar Documents

PublicationPublication DateTitle
CN113133123B (en) A method and device for processing scheduling requests, and a terminal
CN112740587B (en)Wireless communication method, terminal equipment and network equipment
WO2020062832A1 (en)Wireless communication method and communication device
AU2017391838B2 (en)Method and device for multiplexing uplink authorization resources
CN113595704B (en) An information processing method, network device, and terminal device
CN111886911B (en)Communication method, terminal equipment and network equipment
CN113133054A (en)Data transmission method and terminal equipment
CN112929975B (en)Resource determining and configuring method, device, terminal and network equipment
CN113517973B (en)Wireless communication method, terminal equipment and network equipment
EP3908053A1 (en)Communication method, terminal device, and network device
WO2021134619A1 (en)Method and apparatus for transmitting uplink control information, device, and storage medium
CN113557779B (en)Method and equipment for scheduling request transmission
CN113115467B (en)Data transmission method, terminal equipment and network equipment
CN112806053B (en)Communication method and terminal device
CN112534924A (en)Wireless communication method and communication equipment
JP7655868B2 (en) HARQ codebook determination method and device, terminal device, and network device
WO2020061773A1 (en)Feedback resource allocation method, terminal device, and network device
CN113455079B (en)Method and apparatus for wireless communication
CN111934831B (en)Communication method and terminal device
WO2021087925A1 (en)Method for configuring transmission resource cancellation indication information, network apparatus, and terminal apparatus
TW202037126A (en)Method and apparatus for determining number of uplink control information transmission resources, and program
WO2020107714A1 (en)Radio communication method and communication device
WO2022267022A1 (en)Wireless communication method, terminal device, and network device

Legal Events

DateCodeTitleDescription
PB01Publication
PB01Publication
SE01Entry into force of request for substantive examination
SE01Entry into force of request for substantive examination
GR01Patent grant
GR01Patent grant

[8]ページ先頭

©2009-2025 Movatter.jp