Capability reporting method and apparatus

Abstract

The present disclosure provides a capability reporting method and apparatus. The method includes: a terminal device sending capability indication information to a network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT). Thus, it is possible to support the terminal device in reporting to the network-side device the capability of the terminal device to support beam reciprocity during the CG-SDT process.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular, to a method and apparatus for reporting capabilities. Background Art

[0002] In the related art, during the process of CG-SDT (Configured Grant Small Data Transmission), a terminal device in a non-connected state does not support beam reciprocity and does not support the terminal device reporting to the network-side device the capability of supporting beam reciprocity during the CG-SDT process, which is an urgent problem to be solved. Summary of the Invention

[0003] Embodiments of the present disclosure provide a method and apparatus for reporting capabilities. The terminal device sends capability indication information to the network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data transmission (CG-SDT). Thus, it is possible to support the terminal device reporting to the network-side device the capability of supporting beam reciprocity during the CG-SDT process.

[0004] In a first aspect, embodiments of the present disclosure provide a method for reporting capabilities. The method is executed by a terminal device and includes: sending capability indication information to a network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data transmission (CG-SDT).

[0005] In this technical solution, the terminal device sends capability indication information to the network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data transmission (CG-SDT). Thus, it is possible to support the terminal device reporting to the network-side device the capability of supporting beam reciprocity during the CG-SDT process.

[0006] In a second aspect, embodiments of the present disclosure provide another method for reporting capabilities. The method is executed by a network-side device and includes: receiving capability indication information sent by a terminal device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data transmission (CG-SDT).

[0007] In a third aspect, embodiments of the present disclosure provide a communication device, which has some or all of the functions of the terminal device in the method described in the first aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of any one of the embodiments in the present disclosure alone. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0008] In one implementation, the structure of the communication device may include a transceiver module and a processing module. The processing module is configured to support the communication device in executing the corresponding functions in the above method. The transceiver module is used to support the communication between the communication device and other devices. The communication device may further include a storage module, which is used to be coupled with the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0009] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory.

[0010] In one implementation, the communication device includes: a transceiver module, configured to send capability indication information to a network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT).

[0011] In a fourth aspect, embodiments of the present disclosure provide another communication device, which has some or all of the functions of the network-side device in the method described in the second aspect above. For example, the functions of the communication device may have some or all of the functions in the embodiments of the present disclosure, or may have the functions of any one of the embodiments in the present disclosure alone. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0012] In one implementation, the structure of the communication device may include a transceiver module and a processing module. The processing module is configured to support the communication device in executing the corresponding functions in the above method. The transceiver module is used to support the communication between the communication device and other devices. The communication device may further include a storage module, which is used to be coupled with the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0013] As an example, the processing module may be a processor, the transceiver module may be a transceiver or a communication interface, and the storage module may be a memory.

[0014] In one implementation, the communication device includes: a transceiver module configured to receive capability indication information sent by a terminal device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT).

[0015] In a fifth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor that, when calling a computer program in a memory, executes the method described in the first aspect above.

[0016] In a sixth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor that, when calling a computer program in a memory, executes the method described in the second aspect above.

[0017] In a seventh aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory so that the communication device executes the method described in the first aspect above.

[0018] In an eighth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and a memory, and a computer program is stored in the memory; the processor executes the computer program stored in the memory so that the communication device executes the method described in the second aspect above.

[0019] In a ninth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions so that the device executes the method described in the first aspect above.

[0020] In a tenth aspect, an embodiment of the present disclosure provides a communication device, which includes a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, and the processor is used to run the code instructions so that the device executes the method described in the second aspect above.

[0021] In an eleventh aspect, an embodiment of the present disclosure provides a random access system, which includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0022] In a twelfth aspect, an embodiment of the present invention provides a computer-readable storage medium for storing instructions used by the above terminal device. When the instructions are executed, the terminal device is caused to execute the method described in the first aspect above.

[0023] In a thirteenth aspect, an embodiment of the present invention provides a readable storage medium for storing instructions used by the above network-side device. When the instructions are executed, the network-side device is caused to execute the method described in the second aspect above.

[0024] In a fourteenth aspect, the present disclosure further provides a computer program product including a computer program. When it runs on a computer, the computer is caused to execute the method described in the first aspect above.

[0025] In a fifteenth aspect, the present disclosure further provides a computer program product including a computer program. When it runs on a computer, the computer is caused to execute the method described in the second aspect above.

[0026] In a sixteenth aspect, the present disclosure provides a chip system. The chip system includes at least one processor and an interface, and is used to support the terminal device to implement the functions involved in the first aspect. For example, to determine or process at least one of the data and information involved in the above method. In a possible design, the chip system further includes a memory for storing the necessary computer programs and data of the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0027] In a seventeenth aspect, the present disclosure provides a chip system. The chip system includes at least one processor and an interface, and is used to support the network-side device to implement the functions involved in the second aspect. For example, to determine or process at least one of the data and information involved in the above method. In a possible design, the chip system further includes a memory for storing the necessary computer programs and data of the network-side device. The chip system may be composed of chips or may include chips and other discrete devices.

[0028] In an eighteenth aspect, the present disclosure provides a computer program. When it runs on a computer, the computer is caused to execute the method described in the first aspect above.

[0029] In a nineteenth aspect, the present disclosure provides a computer program. When it runs on a computer, the computer is caused to execute the method described in the second aspect above. BRIEF DESCRIPTION OF THE DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background art, the following will describe the drawings required to be used in the embodiments of the present disclosure or the background art.

[0031] Figure 1 It is an example diagram of the SDT process;

[0032] Figure 2 It is an example diagram of the CG-SDT retransmission process;

[0033] Figure 3 It is an architecture diagram of a communication system provided by an embodiment of the present disclosure;

[0034] Figure 4 It is a flowchart of a capability reporting method provided by an embodiment of the present disclosure;

[0035] Figure 5 It is a flowchart of an information transmission method provided by an embodiment of the present disclosure;

[0036] Figure 6 It is a flowchart of another information transmission method provided by an embodiment of the present disclosure;

[0037] Figure 7 It is a flowchart of yet another information transmission method provided by an embodiment of the present disclosure;

[0038] Figure 8 It is a flowchart of yet another information transmission method provided by an embodiment of the present disclosure;

[0039] Figure 9 It is a flowchart of another capability reporting method provided by an embodiment of the present disclosure;

[0040] Figure 10 It is a flowchart of yet another information transmission method provided by an embodiment of the present disclosure;

[0041] Figure 11 It is a flowchart of yet another information transmission method provided by an embodiment of the present disclosure;

[0042] Figure 12 It is a flowchart of yet another information transmission method provided by an embodiment of the present disclosure;

[0043] Figure 13 It is a flowchart of yet another information transmission method provided by an embodiment of the present disclosure;

[0044] Figure 14 It is a structure diagram of a communication device provided by an embodiment of the present disclosure;

[0045] Figure 15 It is a structure diagram of another communication device provided by an embodiment of the present disclosure;

[0046] Figure 16 It is a schematic structural diagram of a chip provided by an embodiment of the present disclosure. Detailed implementation manners

[0047] Exemplary embodiments will be described in detail herein, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0048] It can be understood that "a plurality of" in the present disclosure means two or more, and other quantifiers are similar thereto. "And / or" describes the association relationship of associated objects and indicates that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally represents an "or" relationship between the associated objects before and after. The singular forms of "a", "the", and "said" are also intended to include the plural forms unless the context clearly indicates otherwise.

[0049] It can be further understood that although the operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood as requiring the operations to be performed in the specific order shown or in a serial order, or requiring all the operations shown to obtain the desired result. In a specific environment, multitasking and parallel processing may be advantageous.

[0050] To facilitate understanding of the technical solutions of the present disclosure, some terms related to the embodiments of the present disclosure are briefly introduced below.

[0051] 1. Beam

[0052] A beam can be a spatial domain filter, or a spatial filter or a spatial parameter. The beam used for transmitting a signal can be called a transmission beam (Tx beam), and can be called a spatial domain transmission filter or a spatial transmission parameter; the beam used for receiving a signal can be called a reception beam (Rx beam), and can be called a spatial domain receive filter or a spatial RX parameter.

[0053] A transmission beam may refer to the distribution of signal strength formed in different directions in space after a signal is transmitted by an antenna, and a reception beam may refer to the distribution of signal strength of a wireless signal received by an antenna in different directions in space.

[0054] In addition, a beam may be a wide beam, or a narrow beam, or other types of beams. The technology for forming a beam may be beamforming technology or other technologies. The beamforming technology may specifically be digital beamforming technology, analog beamforming technology, or hybrid digital / analog beamforming technology, etc.

[0055] Generally, a beam corresponds to a resource. For example, when performing beam measurement, a network-side device may use different beams to transmit signals on different resources, and a terminal device may use different beams to receive signals on different resources. Moreover, the terminal device may feedback the quality of the signals measured on different resources to the network-side device, so that the network-side device knows the quality of the corresponding beam. During data transmission, beam information is also indicated through its corresponding resource. For example, the network-side device indicates the beam information of the physical downlink shared channel (PDSCH) of the terminal device through the transmission configuration indicator (TCI) resource in the downlink control information (DCI).

[0056] Optionally, multiple beams with the same or similar communication characteristics may be regarded as one beam.

[0057] One beam corresponds to one or more antenna ports, which are used to transmit data channels, control channels, sounding signals, etc. The one or more antenna ports corresponding to one beam may also be regarded as an antenna port set.

[0058] In beam measurement, each beam of the network-side device corresponds to a resource. Therefore, the beam corresponding to the resource can be uniquely identified by the identifier (or index) of the resource.

[0059] 2. Beam Reciprocity (Beam correspondence)

[0060] The terminal device can determine its uplink transmission beam according to the downlink receiving beam or determine its downlink receiving beam according to the uplink transmission beam. Exemplarily, if receiving beam A is a better / best choice for receiving downlink signals, the terminal device infers from the downlink receiving beam A that its corresponding uplink transmission beam A' is also a better / best uplink transmission beam. If the network side device indicates a downlink reference signal X corresponding to a certain downlink transmission beam A, the terminal device can know its corresponding transmission beam A' according to the receiving beam A corresponding to the received signal X.

[0061] 3. Small Data Transmission (SDT)

[0062] Generally, when the terminal device is in the RRC connected state (CONNECTED), data can be transmitted between the terminal device and the network side device. However, in some scenarios, the data packets to be transmitted by the terminal device in the RRC idle state (IDLE) or RRC inactive state (INACTIVE) are very small, and such data packets can be called small data. Moreover, the signaling required for the terminal device to enter the RRC CONNECTED state from the RRC IDLE state or RRC INACTIVE state is even greater than the small data, resulting in unnecessary power consumption and signaling overhead of the terminal device. To avoid the above situation, the terminal device in the RRC IDLE state or RRC INACTIVE state can transmit small data during the random access (RA) process or on the resources configured by the network side device, without having to enter the RRC CONNECTED state to transmit small data.

[0063] The above transmission process can be called SDT (small data transmission), and the method by which the terminal device transmits small data on the resources configured by the network side device can be called CG-SDT (ConfigureGrant small data transmission).

[0064] According to the resources configured by the network side, when the terminal device is in the non-connected state, such as IDLE (idle state) or INACTIVE (inactive state), the terminal device can directly send data to the network side device by the following methods:

[0065] 1) Msg3 of the four-step random access process for initial access (or called 4-step RACH SDT);

[0066] 2) MsgA of the two-step random access procedure for initial access. (Or referred to as 2-step RACH SDT);

[0067] 3) Dedicated uplink PUSCH (Physical Uplink Shared Channel) resources configured by the network (i.e., CG (Configure Grant) or PUR (Preallocated Uplink Resource)); or referred to as CG SDT.

[0068] Such as Figure 1 shown, the SDT process may include an initial data transmission phase and a subsequent data transmission phase.

[0069] Among them, the initial data transmission phase: starting from triggering the initial data transmission of SDT until receiving the confirmation information of the network side for this initial data.

[0070] Among them, this confirmation information has the following three differences for different SDT processes:

[0071] (1) 4-step RACH SDT: The confirmation information is the contention resolution identifier for successfully receiving Msg4;

[0072] (2) 2-step RACH SDT: The confirmation information is the contention resolution identifier for successfully receiving MsgB;

[0073] (3) CG-SDT: The confirmation information is the data reception success indication sent by the network side device (e.g., the ACK (positive acknowledgment) information indicated by the physical layer DCI (Downlink Control Information)).

[0074] The subsequent data transmission phase: from receiving the confirmation information of the network side device for this initial data until receiving the connection release message sent by the network side device. In this phase, the terminal device can perform the transmission and reception of uplink and downlink data.

[0075] In the subsequent data transmission phase of CG-SDT, in this process, the terminal device will listen to the PDCCH (Physical downlink control channel) to receive the C-RNTI (Cell Radio Network Temporary Identifier) and send CG-PUSCH at a subsequent moment. Before receiving the connection release message sent by the network side device, the terminal device will continuously repeat listening to the PDCCH and then sending CG-PUSCH.

[0076] Among them, there is a correlation mapping relationship between the SSB (Synchronization Signal and PBCH block) beam and the CG-PUSCH.

[0077] As Figure 2 shown, Figure 2 It is an example diagram of the CG-SDT retransmission process. For the CG-SDT resources configured by the network-side device, after the terminal device sends data using this CG resource, it will start a feedback timer (such as, feedbackTimer) to listen for the feedback information from the network-side device. If the terminal device does not receive a successful reception confirmation from the network-side device during the operation of the feedback timer, the terminal device will retransmit the data on the subsequent CG resources for CG-SDT retransmission. For the uplink configured grant, each time the terminal device sends an uplink new data transmission on a HARQ process, the configured grant timer corresponding to this HARQ process will be started. During the operation of this timer, no other new transmissions can be scheduled on this HARQ process. The configured grant retransmission timer (CG-RetransmissionTimer) can be configured per ConfiguredGrant and is used for uplink automatic retransmission. Each time the terminal device sends an uplink new transmission or retransmission on a HARQ process, the CG-RetransmissionTimer corresponding to this HARQ process will be started. During the operation of this timer, uplink automatic retransmission is not performed. After this timer stops running, uplink automatic retransmission is started.

[0078] 4. QCL (Quasi-collocation)

[0079] Quasi-collocation (QCL) means that the large-scale parameters of the channel experienced by the symbols on a certain antenna port can be inferred from the channel experienced by the symbols on another antenna port. The large-scale parameters can include delay spread, average delay, Doppler spread, Doppler shift, average gain, and spatial reception parameters, etc.

[0080] The concept of QCL was introduced with the emergence of Coordinated Multiple Point (CoMP) transmission technology. The multiple stations involved in the CoMP transmission process may correspond to multiple stations with different geographical locations or multiple sectors with different antenna panel orientations. For example, when a terminal device receives data from different stations, the spatial differences among the stations will result in differences in the large-scale channel parameters of the receiving links from different stations, such as Doppler frequency offset, delay spread, etc. And the large-scale parameters of the channel will directly affect the adjustment and optimization of the filter coefficients during channel estimation. For signals sent from different stations, different channel estimation filter parameters should be used to adapt to the corresponding channel propagation characteristics.

[0081] Therefore, although the differences in the spatial position or angle of each station are transparent to the UE and the CoMP operation itself, the impact of the above spatial differences on the large-scale channel parameters is an important factor that needs to be considered during channel estimation and reception detection by the terminal device. The so-called QCL of two antenna ports in terms of certain large-scale parameters means that these large-scale parameters of the two ports are the same. Or rather, as long as the certain large-scale parameters of two ports are consistent, regardless of whether there are differences in their actual physical positions or the orientations of the corresponding antenna panels, the terminal device can consider that these two ports are from the same location (i.e., quasi-common site).

[0082] For some typical application scenarios, considering the possible QCL relationships among various reference signals, from the perspective of simplifying signaling, several large-scale channel parameters in NR are divided into the following 4 types to facilitate the system to configure / indicate according to different scenarios:

[0083] 1) QCL-TypeA: {Doppler frequency shift, Doppler spread, average delay, delay spread}

[0084] - Except for the spatial reception parameters, all other large-scale parameters are the same.

[0085] - For the frequency band below 6 GHz, spatial reception parameters may not be required.

[0086] 2) QCL-TypeB: {Doppler frequency shift, Doppler spread}

[0087] - Only for the following two cases in the frequency band below 6 GHz

[0088] 3) QCL-TypeC: {Doppler frequency shift, average delay}

[0089] 4) QCL-TypeD: {Spatial reception parameters}

[0090] As described above, since this parameter is mainly for the frequency band above 6 GHz, it is taken as a QCL type separately.

[0091] To better understand a method and apparatus for reporting capabilities disclosed in embodiments of the present disclosure, a communication system applicable to embodiments of the present disclosure will be described first below.

[0092] Please refer to Figure 3 , Figure 3 which is a schematic diagram of the architecture of a communication system provided in embodiments of the present disclosure. The communication system may include, but is not limited to, a network-side device and a terminal device. Figure 3 The number and form of the devices shown are only for illustration and do not constitute a limitation on embodiments of the present disclosure. In practical applications, there may be two or more network-side devices and two or more terminal devices. Figure 3 Taking the communication system 10 shown as an example, it may include a network-side device 101 and a terminal device 102.

[0093] It should be noted that the technical solutions in embodiments of the present disclosure can be applied to various communication systems. For example: Long Term Evolution (LTE) systems, 5th generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems, etc. It should also be noted that the sidelink in embodiments of the present disclosure can also be referred to as a sidelink or a direct link.

[0094] The network-side device 101 in embodiments of the present disclosure is an entity on the network side for transmitting or receiving signals. For example, the network-side device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a Wireless Fidelity (WiFi) system, etc. Embodiments of the present disclosure do not limit the specific technologies and specific device forms adopted by the base station. The base station provided in embodiments of the present disclosure may be composed of a central unit (CU) and a distributed unit (DU). Among them, the CU can also be called a control unit. Adopting the CU-DU structure can split the base station, for example, the protocol layer of the base station, and the functions of some protocol layers are centrally controlled by the CU, and the functions of the remaining part or all protocol layers are distributed in the DU, and the DU is centrally controlled by the CU.

[0095] The terminal device 102 in the embodiments of the present disclosure is an entity on the user side for receiving or transmitting signals, such as a mobile phone. The terminal device can also be referred to as a terminal, a user equipment (UE), a mobile station (MS), a mobile terminal (MT), etc. The terminal device can be an automobile with communication functions, a smart car, a mobile phone, a wearable device, a tablet computer (Pad), a computer with wireless transceiver functions, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and so on. The specific technologies and specific device forms adopted by the terminal device in the embodiments of the present disclosure are not limited.

[0096] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly explaining the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art know that with the evolution of the system architecture and the emergence of new service scenarios, the technical solutions provided by the embodiments of the present disclosure are equally applicable to similar technical problems.

[0097] In a communication system, the communication protocol stack between the terminal device and the network-side device may include an RRC (radio resource control) layer. Among them, the states of the terminal device may include a connected state (also referred to as the CONNCETED state or the RRC_CONNCETED state), an inactive state (also referred to as the inactive state or the RRC_INACTIVE state), and an idle state (also referred to as the idle state or the RRC_IDLE state).

[0098] It should be noted that throughout the description of the embodiments of the present disclosure, the terminal device is in a non-connected state, which can be that the terminal device is in an idle state, or the terminal device is in a deactivated state, or in a state other than other connected states; when the terminal device is in a non-connected state, it can be when the terminal device is in an idle state, or when the terminal device is in a deactivated state, or when the terminal device is in a state other than the connected state.

[0099] In the embodiments of the present disclosure, "for indicating" may include for directly indicating and for indirectly indicating. When it is described that a certain indication information is used to indicate A, it may include that the indication information directly indicates A or indirectly indicates A, and it does not mean that A must be included in the indication information.

[0100] The method and device for reporting capabilities provided by the present disclosure will be described in detail below with reference to the accompanying drawings.

[0101] Please refer to Figure 4 , Figure 4 which is a flowchart of a method for reporting capabilities provided by an embodiment of the present disclosure.

[0102] As Figure 4 shown, this method is executed by a terminal device, and this method may include but is not limited to the following steps:

[0103] S41: The terminal device sends capability indication information to the network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT).

[0104] Regarding the problem in the related art that the terminal device does not support reporting the capability of supporting beam reciprocity during the CG-SDT process.

[0105] In the embodiments of the present disclosure, the terminal device can send capability indication information to the network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the CG-SDT process. Thus, it is possible to support the terminal device to report to the network-side device the capability of the terminal device to support beam reciprocity during the CG-SDT process.

[0106] Among them, the terminal device can send the information element (IE) beamcorrespondence-cg-SDT-r18 ENUMERATED{supported} to the network-side device to send the capability indication information to report the capability of the terminal device to support beam reciprocity during the CG-SDT process.

[0107] In some embodiments, the terminal device supporting beam reciprocity means that the terminal device can determine the uplink transmission beam according to the downlink reception beam without performing uplink beam scanning.

[0108] It can be understood that when the terminal device does not support beam reciprocity, the terminal device needs to perform uplink beam scanning to determine a beam with better or optimal beam quality, which is determined as the uplink transmission beam, and then use the uplink transmission beam to perform CG-SDT and send small data packets to the network-side device.

[0109] In the embodiments of the present disclosure, during the CG-SDT process, the terminal device supports beam reciprocity. The terminal device can determine the uplink transmission beam according to the downlink reception beam configured by the network-side device for the exclusive PUSCH resource, and then use the determined uplink transmission beam on the exclusive PUSCH resource to send small data packets to the network-side device to perform CG-SDT and / or perform CG-SDT retransmission. Thus, the terminal device does not need to perform uplink beam scanning to determine the uplink beam, which can save the energy consumption of the terminal device. Moreover, since the terminal device does not need to perform beam scanning to determine the candidate uplink transmission beam, the delay can be reduced.

[0110] In some embodiments, the terminal device receives a radio resource control (RRC) release message sent by the network-side device in the connected state and switches to the non-connected state. The RRC release message is used to indicate the exclusive physical uplink shared channel (PUSCH) resource for performing CG-SDT. The terminal device in the non-connected state determines the candidate uplink transmission beam according to the candidate downlink reception beam for receiving the RRC release message. The terminal device in the non-connected state uses the candidate uplink transmission beam on the exclusive PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission.

[0111] In the embodiments of the present disclosure, the terminal device in the connected state receives the RRC connection release message sent by the network-side device and switches to the non-connected state. When the network-side device sends the RRC connection release message to the terminal device in the connected state, the QCL information can be released synchronously.

[0112] The RRC connection release message sent by the network-side device to the terminal device in the connected state is used to indicate the exclusive PUSCH resource for performing CG-SDT.

[0113] In the embodiments of the present disclosure, after the terminal device in the connected state receives the RRC connection release message sent by the network-side device, it switches from the connected state to the non-connected state. The terminal device in the non-connected state can determine the candidate downlink reception beam used for receiving the RRC release message. Furthermore, since the terminal device supports beam reciprocity during the CG-SDT process, the terminal device can determine the candidate uplink transmission beam according to the candidate downlink reception beam.

[0114] After that, the terminal device can use the candidate uplink transmission beam on the exclusive PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission and send small data packets.

[0115] Among them, the process of the terminal device performing CG-SDT and / or performing CG-SDT retransmission can refer to the above relevant description, and the same content will not be repeated here.

[0116] It can be understood that when the terminal device does not support beam reciprocity during the CG-SDT process, the terminal device needs to perform uplink beam scanning to determine a better or optimal candidate uplink transmission beam, and use the determined candidate uplink transmission beam to perform CG-SDT to send small data packets.

[0117] However, in the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process, and can determine the candidate uplink transmission beam according to the candidate downlink reception beam used by the network-side device to send the RRC release message, and then use the candidate uplink transmission beam to perform CG-SDT to send small data packets. Thus, the terminal device does not need to perform uplink beam scanning to determine the uplink beam, which can save the energy consumption of the terminal device, and moreover, the terminal device does not need to perform beam scanning to determine the candidate uplink transmission beam, which can reduce the delay.

[0118] In some embodiments, the terminal device receives a data reception success indication sent by the network-side device in the non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

[0119] In the embodiments of the present disclosure, the terminal device uses the candidate uplink transmission beam to perform CG-SDT and / or perform CG-SDT retransmission on the dedicated PUSCH resource to send data to the network-side device, that is, to send small data packets. After the network-side device receives the data sent by the terminal device, that is, receives the small data packets sent by the terminal device, it can send a data reception success indication to the terminal device to inform the terminal device that it has received the data sent by the terminal device during CG-SDT and / or during CG-SDT retransmission.

[0120] It can be understood that CG-SDT includes two stages: an initial data transmission stage and a subsequent data transmission stage.

[0121] Among them, in the initial data transmission stage, it includes: the terminal device in the non-connected state uses the candidate uplink transmission beam to perform CG-SDT and / or perform CG-SDT retransmission on the dedicated PUSCH resource to send data (small data packets) to the network-side device.

[0122] After the network-side device receives the data (small data packets) sent by the terminal device during CG-SDT and / or during CG-SDT retransmission, it can send a data reception success indication to the terminal device.

[0123] Among them, when the terminal device is in the connected state, the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process, and there is an association relationship between the SSB beam and the PUSCH resource. The network-side device can determine the downlink beam based on the association relationship between the SSB beam and the PUSCH, and the dedicated PUSCH resource used by the terminal device during CG-SDT and / or CG-SDT retransmission, and then send a data reception success indication to the terminal device on the downlink beam.

[0124] Among them, the subsequent data transmission phase can be after the terminal device receives the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device. During the subsequent data transmission phase, the terminal device continuously repeats listening to the PDCCH.

[0125] In some embodiments, there is a mapping relationship between the SSB beam and the PUSCH resource. After the terminal device receives the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device, it further includes: listening to the physical downlink control channel PDCCH and receiving the PDCCH carrying the C-RNTI on the candidate SSB beam, where the candidate SSB beam is determined by the network-side device based on the dedicated PUSCH resource and the mapping relationship in the case of determining that the terminal device supports beam reciprocity.

[0126] It can be understood that after the terminal device receives the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device, during the subsequent data transmission phase, the terminal device listens to the physical downlink control channel PDCCH and receives the PDCCH carrying the C-RNTI on the candidate SSB beam.

[0127] Among them, there is a mapping relationship between the SSB and the PUSCH resource, and when the terminal device is in the connected state, the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process. During the subsequent data transmission phase, the network-side device can determine the corresponding candidate SSB beam according to the dedicated PUSCH resource and the mapping relationship used by the terminal device during SDT and / or SDT retransmission, and send the PDCCH carrying the C-RNTI to the terminal device on the candidate SSB beam.

[0128] Based on this, the terminal device listens to the PDCCH and can receive the PDCCH carrying the C-RNTI on the candidate SSB beam to further send the PUSCH to the network-side device.

[0129] In some embodiments, the terminal device determines the uplink SSB beam according to the candidate SSB beam and sends the PUSCH to the network-side device on the uplink SSB beam.

[0130] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. The terminal device monitors the PDCCH and receives the PDCCH carrying the C-RNTI on the candidate SSB beam. The terminal device can determine the uplink SSB beam according to the candidate SSB beam. Further, the terminal device can send the PUSCH to the network device on the uplink SSB beam.

[0131] It can be understood that when the terminal device does not support beam reciprocity, the terminal device needs to perform uplink beam scanning to determine the beam with better or best beam quality, determine it as the uplink transmission beam, and then use the uplink transmission beam to send the PUSCH.

[0132] However, in the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. After the terminal device receives the PDCCH on the candidate SSB beam, the terminal device can directly determine the uplink SSB beam according to the candidate SSB beam. The terminal device does not need to perform uplink beam scanning and can directly determine the uplink SSB beam, which can save the energy consumption of the terminal device and reduce the latency.

[0133] Please refer to Figure 5 , Figure 5 which is a flowchart of an information transmission method provided by the embodiments of the present disclosure.

[0134] As Figure 5 shown, this method is executed by the terminal device, and this method may include but is not limited to the following steps:

[0135] S51: The terminal device receives the radio resource control (RRC) release message sent by the network device in the connected state and switches to the non-connected state, where the RRC release message is used to indicate the dedicated physical uplink shared channel (PUSCH) resource for CG-SDT.

[0136] S52: The terminal device determines the candidate uplink transmission beam according to the candidate downlink reception beam for receiving the RRC release message in the non-connected state, where the terminal device supports beam reciprocity during the CG-SDT process.

[0137] S53: The terminal device performs CG-SDT and / or CG-SDT retransmission using the candidate uplink transmission beam on the dedicated PUSCH resource in the non-connected state.

[0138] In the embodiments of the present disclosure, the terminal device in the connected state receives the RRC connection release message sent by the network device and switches to the non-connected state. Wherein, when the network device sends the RRC connection release message to the terminal device in the connected state, the QCL information can be synchronously released.

[0139] Among them, the RRC connection release message sent by the network-side device to the terminal device in the connected state is used to indicate the dedicated PUSCH resource for CG-SDT.

[0140] In the embodiments of the present disclosure, after the terminal device in the connected state receives the RRC connection release message sent by the network-side device, it switches from the connected state to the non-connected state. The terminal device in the non-connected state can determine the candidate downlink receiving beam used to receive the RRC release message. Furthermore, since the terminal device supports beam reciprocity during the CG-SDT process, the terminal device can determine the candidate uplink transmission beam based on the candidate downlink receiving beam.

[0141] After that, the terminal device can use the candidate uplink transmission beam on the dedicated PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission to send small data packets.

[0142] Among them, the process of the terminal device performing CG-SDT and / or performing CG-SDT retransmission can refer to the above related description, and the same content will not be repeated here.

[0143] It can be understood that in the case where the terminal device does not support beam reciprocity during the CG-SDT process, the terminal device needs to perform uplink beam scanning to determine the better or best candidate uplink transmission beam, and use the determined candidate uplink transmission beam to perform CG-SDT to send small data packets.

[0144] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process, can determine the candidate uplink transmission beam according to the candidate downlink receiving beam used by the network-side device to send the RRC release message, and then use the candidate uplink transmission beam to perform CG-SDT to send small data packets. Thus, the terminal device does not need to perform uplink beam scanning to determine the uplink beam, which can save the energy consumption of the terminal device. Moreover, the terminal device can determine the candidate uplink transmission beam without performing beam scanning, which can reduce the delay.

[0145] It should be noted that in the embodiments of the present disclosure, S51 to S53 can be implemented alone or in combination with any other step in the embodiments of the present disclosure. For example, it can be implemented in combination with S41 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard.

[0146] Please refer to Figure 6 , Figure 6 which is the flowchart of another information transmission method provided by the embodiments of the present disclosure.

[0147] As Figure 6 shown, this method is executed by the terminal device, and this method may include but is not limited to the following steps:

[0148] S61: The terminal device receives a Radio Resource Control (RRC) release message sent by the network-side device in the connected state and switches to the non-connected state. The RRC release message is used to indicate the Physical Uplink Shared Channel (PUSCH) resources dedicated to the Cell Global Identifier - Single Data Transmission (CG-SDT).

[0149] S62: The terminal device determines candidate uplink transmission beams based on the candidate downlink reception beams for receiving the RRC release message in the non-connected state. The terminal device supports beam reciprocity during the CG-SDT process.

[0150] S63: The terminal device performs CG-SDT and / or CG-SDT retransmission using the candidate uplink transmission beams on the dedicated PUSCH resources in the non-connected state.

[0151] For the relevant descriptions of S61 to S63, reference can be made to the relevant descriptions in the above embodiments, which will not be elaborated here.

[0152] S64: The terminal device receives a data reception success indication sent by the network-side device in the non-connected state. The data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

[0153] In the embodiments of the present disclosure, the terminal device uses the candidate uplink transmission beams on the dedicated PUSCH resources to perform CG-SDT and / or CG-SDT retransmission, and sends data to the network-side device, that is, sends small data packets. After the network-side device receives the data sent by the terminal device, that is, receives the small data packets sent by the terminal device, it can send a data reception success indication to the terminal device to inform the terminal device that it has received the data sent by the terminal device during CG-SDT and / or CG-SDT retransmission.

[0154] It should be noted that in the embodiments of the present disclosure, S61 to S64 can be implemented independently or in combination with any other step in the embodiments of the present disclosure. For example, it can be implemented in combination with S41 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard.

[0155] Please refer to Figure 7 , Figure 7 which is a flowchart of another information transmission method provided by the embodiments of the present disclosure.

[0156] As Figure 7 shown, this method is executed by the terminal device, and this method may include but is not limited to the following steps:

[0157] S71: After receiving the data reception success indication sent by the network side device and before receiving the connection release message sent by the network side device, listen to the physical downlink control channel PDCCH, and receive the PDCCH carrying the cell radio network temporary identity C-RNTI on the candidate SSB beam, where the candidate SSB beam is determined by the network side device according to the dedicated PUSCH resource and the mapping relationship when it determines that the terminal device supports beam reciprocity, and there is a mapping relationship between the synchronization signal block SSB beam and the PUSCH resource.

[0158] It can be understood that CG-SDT includes two stages: the initial data transmission stage and the subsequent data transmission stage.

[0159] Among them, the initial data transmission stage includes: the terminal device in the non-connected state uses the candidate uplink transmission beam on the dedicated PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission, and sends data (small data packets) to the network side device. After the network side device receives the data (small data packets) sent by the terminal device for CG-SDT and / or CG-SDT retransmission, it can send a data reception success indication to the terminal device.

[0160] Among them, when the terminal device is in the connected state, the network side device already knows that the terminal device supports beam reciprocity during CG-SDT, and there is an association relationship between the SSB beam and the PUSCH resource. The network side device can determine the downlink beam according to the association relationship between the SSB beam and the PUSCH, and the dedicated PUSCH resource used by the terminal device for CG-SDT and / or CG-SDT retransmission, and then send a data reception success indication to the terminal device on the downlink beam.

[0161] Among them, the subsequent data transmission stage can be after the terminal device receives the data reception success indication sent by the network side device and before receiving the connection release message sent by the network side device. In the subsequent data transmission stage, the terminal device continuously repeats listening to the PDCCH.

[0162] It can be understood that after the terminal device receives the data reception success indication sent by the network side device and before receiving the connection release message sent by the network side device, in the subsequent data transmission stage, the terminal device listens to the physical downlink control channel PDCCH and receives the PDCCH carrying C-RNTI on the candidate SSB beam.

[0163] Among them, the SSB and the PUSCH resources have a mapping relationship, and the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process when the terminal device is in the connected state. In the subsequent data transmission phase, the network-side device can determine the corresponding candidate SSB beams according to the dedicated PUSCH resources and the mapping relationship used by the terminal device for SDT and / or SDT retransmission, and send a PDCCH carrying the C-RNTI to the terminal device on the candidate SSB beams.

[0164] Based on this, the terminal device monitors the PDCCH and can receive the PDCCH carrying the C-RNTI on the candidate SSB beams to further send a PUSCH to the network-side device.

[0165] It should be noted that in the embodiments of the present disclosure, S71 can be implemented alone or in combination with any one of the other steps in the embodiments of the present disclosure. For example, it can be implemented in combination with S41 and / or S51 to S53 and / or S61 to S64 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard.

[0166] Please refer to Figure 8 , Figure 8 which is a flowchart of another information transmission method provided by the embodiments of the present disclosure.

[0167] As Figure 8 shown, this method is executed by the terminal device, and this method may include but is not limited to the following steps:

[0168] S81: After receiving the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device, monitor the physical downlink control channel PDCCH and receive the PDCCH carrying the cell radio network temporary identity C-RNTI on the candidate SSB beams, where the candidate SSB beams are determined by the network-side device according to the dedicated PUSCH resources and the mapping relationship in the case of determining that the terminal device supports beam reciprocity, and the synchronization signal block SSB beams and the PUSCH resources have a mapping relationship.

[0169] Among them, the relevant description of S81 can refer to the relevant description in the above embodiments and will not be elaborated here.

[0170] S82: Determine the uplink SSB beam according to the candidate SSB beam, where the terminal device supports beam reciprocity during the CG-SDT process.

[0171] S83: Send a PUSCH to the network-side device on the uplink SSB beam.

[0172] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. The terminal device monitors the PDCCH and receives the PDCCH carrying the C-RNTI on the candidate SSB beam. The terminal device can determine the uplink SSB beam according to the candidate SSB beam. Further, the terminal device can send the PUSCH to the network device on the uplink SSB beam.

[0173] Among them, the network device can determine one or more candidate SSB beams according to the dedicated PUSCH resource and the mapping relationship. The network device can send the PDCCH carrying the C-RNTI to the terminal device on multiple candidate SSB beams. The terminal device monitors the PDCCH and receives the PDCCH carrying the C-RNTI on the candidate SSB beam. Since the terminal device supports beam reciprocity, the terminal device can determine the uplink SSB beam according to the candidate SSB beam.

[0174] Among them, when there is one candidate SSB beam, the terminal device can determine one uplink SSB beam to send the PUSCH to the network device on the uplink SSB beam. When there are multiple candidate SSB beams, the terminal device can determine multiple uplink beams corresponding to the candidate SSB beams. The terminal device can randomly select one as the uplink SSB beam, or can also compare multiple uplink beams and select one as the uplink SSB beam from them. Among them, the terminal device can use the method in the related art to compare multiple uplink beams, and the embodiments of the present disclosure do not make specific limitations on this.

[0175] Of course, when there are multiple candidate SSB beams, the terminal device can also determine the uplink beams corresponding to the multiple candidate SSB beams as the uplink SSB beams. The terminal device can send the PUSCH to the terminal device on multiple uplink SSB beams. The embodiments of the present disclosure do not make specific limitations on this.

[0176] It can be understood that when the terminal device does not support beam reciprocity, the terminal device needs to perform uplink beam scanning to determine the beam with better or best beam quality, determine it as the uplink transmission beam, and then use the uplink transmission beam to send the PUSCH.

[0177] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. After the terminal device receives the PDCCH on the candidate SSB beam, the terminal device can directly determine the uplink SSB beam according to the candidate SSB beam. The terminal device does not need to perform uplink beam scanning and can directly determine the uplink SSB beam, which can save the energy consumption of the terminal device and reduce the latency.

[0178] It should be noted that in the embodiments of the present disclosure, S81 to S83 can be implemented independently, or can be implemented in combination with any other steps in the embodiments of the present disclosure. For example, it can be implemented in combination with S41 and / or S51 to S53 and / or S61 to S64 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard.

[0179] Please refer to Figure 9 , Figure 9 which is a flowchart of another method for reporting capabilities provided by the embodiments of the present disclosure.

[0180] As Figure 9 shown, this method is executed by a network-side device, and this method may include but is not limited to the following steps:

[0181] S91: Receive capability indication information sent by a terminal device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT).

[0182] Regarding the problem in the related art that the terminal device does not support reporting the capability of supporting beam reciprocity during the CG-SDT process.

[0183] In the embodiments of the present disclosure, a terminal device in a connected state can send capability indication information to a network-side device, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the CG-SDT process. Thus, it is possible to support the terminal device to report to the network-side device the capability of the terminal device to support beam reciprocity during the CG-SDT process.

[0184] Among them, the terminal device can send an information element (IE) beamcorrespondence-cg-SDT-r18 ENUMERATED{supported} to the network-side device to send the capability indication information to report the capability of the terminal device to support beam reciprocity during the CG-SDT process.

[0185] In some embodiments, the terminal device supporting beam reciprocity means that the terminal device can determine the uplink transmission beam according to the downlink reception beam without performing uplink beam scanning.

[0186] It can be understood that when the terminal device does not support beam reciprocity, the terminal device needs to perform uplink beam scanning to determine the beam with better or best beam quality, determine it as the uplink transmission beam, and then use the uplink transmission beam to perform CG-SDT to send small data packets to the network-side device.

[0187] In the embodiments of the present disclosure, during the CG-SDT process, the terminal device supports beam reciprocity. The terminal device can determine the uplink transmission beam according to the downlink reception beam used for configuring the dedicated PUSCH resource by the network-side device, and then use the determined uplink transmission beam on the dedicated PUSCH resource to send small data packets to the network-side device for CG-SDT and / or CG-SDT retransmission.

[0188] In some embodiments, the network-side device sends an RRC release message to the terminal device in the connected state and releases the QCL information, where the RRC release message is used to indicate the dedicated PUSCH resource for CG-SDT; the network-side device receives data sent by the terminal device in the non-connected state using a candidate uplink transmission beam for CG-SDT and / or CG-SDT retransmission on the dedicated PUSCH resource, where the candidate uplink transmission beam is determined by the terminal device according to the candidate downlink reception beam for receiving the RRC release message.

[0189] In the embodiments of the present disclosure, the terminal device in the connected state receives the RRC connection release message sent by the network-side device and switches to the non-connected state. When the network-side device sends the RRC connection release message to the terminal device in the connected state, the QCL information can be released synchronously.

[0190] The RRC connection release message sent by the network-side device to the terminal device in the connected state is used to indicate the dedicated PUSCH resource for CG-SDT.

[0191] In the embodiments of the present disclosure, after the terminal device in the connected state receives the RRC connection release message sent by the network-side device, it switches from the connected state to the non-connected state. The terminal device in the non-connected state can determine the candidate downlink reception beam used for receiving the RRC release message. Furthermore, since the terminal device supports beam reciprocity during the CG-SDT process, the terminal device can determine the candidate uplink transmission beam according to the candidate downlink reception beam.

[0192] After that, the terminal device can use the candidate uplink transmission beam on the dedicated PUSCH resource for CG-SDT and / or CG-SDT retransmission to send small data packets.

[0193] For the process of the terminal device performing CG-SDT and / or CG-SDT retransmission, reference can be made to the above related description, and the same content will not be elaborated here.

[0194] It can be understood that when the terminal device does not support beam reciprocity during the CG-SDT process, the terminal device needs to perform uplink beam scanning to determine a better or optimal candidate uplink transmission beam, and use the determined candidate uplink transmission beam to perform CG-SDT and send small data packets.

[0195] However, in the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process, and can determine a candidate uplink transmission beam according to the candidate downlink reception beam used by the network-side device to send the RRC release message, and then use the candidate uplink transmission beam for CG-SDT to send small data packets. Thus, the terminal device does not need to perform uplink beam scanning to determine the uplink beam, which can save the energy consumption of the terminal device. Moreover, since the terminal device can determine the candidate uplink transmission beam without performing beam scanning, the latency can be reduced.

[0196] In some embodiments, the network-side device sends a data reception success indication to a terminal device in a non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

[0197] In the embodiments of the present disclosure, the terminal device uses a candidate uplink transmission beam on the dedicated PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission, and sends data, that is, sends small data packets, to the network-side device. After the network-side device receives the data sent by the terminal device, that is, receives the small data packets sent by the terminal device, it can send a data reception success indication to the terminal device to inform the terminal device that it has received the data sent by the terminal device during CG-SDT and / or during CG-SDT retransmission.

[0198] It can be understood that CG-SDT includes two stages: an initial data transmission stage and a subsequent data transmission stage.

[0199] Among them, the initial data transmission stage includes: a terminal device in a non-connected state uses a candidate uplink transmission beam on the dedicated PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission, and sends data (small data packets) to the network-side device.

[0200] After the network-side device receives the data (small data packets) sent by the terminal device during CG-SDT and / or during CG-SDT retransmission, it can send a data reception success indication to the terminal device.

[0201] Among them, when the terminal device is in a connected state, the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process, and there is an association relationship between the SSB beam and the PUSCH resource. The network-side device can determine the downlink beam according to the association relationship between the SSB beam and the PUSCH, and the dedicated PUSCH resource used by the terminal device during CG-SDT and / or during CG-SDT retransmission, and then send a data reception success indication to the terminal device on the downlink beam.

[0202] Among them, in the subsequent data transmission phase, it can be after the terminal device successfully receives the data reception indication sent by the network-side device and before receiving the connection release message sent by the network-side device. In the subsequent data transmission phase, the terminal device continuously repeats listening to the PDCCH.

[0203] In some embodiments, there is a mapping relationship between the synchronization signal block SSB beam and the PUSCH resource. After sending the data reception success indication to the terminal device and before sending the connection release message to the terminal device, it further includes: determining candidate SSB beams according to the dedicated PUSCH resource and the mapping relationship; sending a PDCCH carrying the C-RNTI to the terminal device on the candidate SSB beams.

[0204] It can be understood that after the terminal device successfully receives the data reception indication sent by the network-side device and before receiving the connection release message sent by the network-side device, in the subsequent data transmission phase, the terminal device listens to the physical downlink control channel PDCCH and receives the PDCCH carrying the C-RNTI on the candidate SSB beams.

[0205] Among them, there is a mapping relationship between the SSB and the PUSCH resource, and when the terminal device is in the connected state, the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process. In the subsequent data transmission phase, the network-side device can determine the corresponding candidate SSB beams according to the dedicated PUSCH resource and the mapping relationship used by the terminal device for SDT and / or SDT retransmission, and send a PDCCH carrying the C-RNTI to the terminal device on the candidate SSB beams.

[0206] Based on this, the terminal device listens to the PDCCH, can receive the PDCCH carrying the C-RNTI on the candidate SSB beams, and further send a PUSCH to the network-side device.

[0207] In some embodiments, the network-side device receives the PUSCH sent by the terminal device in the non-connected state on the uplink SSB beam, where the uplink SSB beam is determined by the terminal device according to the candidate SSB beams.

[0208] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. The terminal device listens to the PDCCH, receives the PDCCH carrying the C-RNTI on the candidate SSB beams, can determine the uplink SSB beam according to the candidate SSB beams, and further can send a PUSCH to the network-side device on the uplink SSB beam.

[0209] It can be understood that when the terminal device does not support beam reciprocity, the terminal device needs to perform uplink beam scanning to determine a beam with better or optimal beam quality, which is determined as the uplink transmission beam, and then use the uplink transmission beam to transmit PUSCH.

[0210] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. After the terminal device receives the PDCCH on the candidate SSB beam, it can directly determine the uplink SSB beam according to the candidate SSB beam. The terminal device does not need to perform uplink beam scanning and can directly determine the uplink SSB beam, which can save the energy consumption of the terminal device and reduce the latency.

[0211] Please refer to Figure 10 , Figure 10 which is a flowchart of another information transmission method provided by the embodiments of the present disclosure.

[0212] As Figure 10 shown, this method is executed by the network-side device, and this method may include but is not limited to the following steps:

[0213] S101: Send an RRC release message to the terminal device in the connected state and release the quasi-co-location (QCL) information, where the RRC release message is used to indicate the dedicated PUSCH resource for CG-SDT.

[0214] S102: Receive the data sent by the terminal device in the non-connected state on the dedicated PUSCH resource using the candidate uplink transmission beam during the CG-SDT process and / or during the CG-SDT retransmission process, where the candidate uplink transmission beam is determined by the terminal device according to the candidate downlink reception beam for receiving the RRC release message, and the terminal device supports beam reciprocity during the CG-SDT process.

[0215] In the embodiments of the present disclosure, the terminal device in the connected state receives the RRC connection release message sent by the network-side device and switches to the non-connected state. Among them, when the network-side device sends the RRC connection release message to the terminal device in the connected state, the QCL information can be released synchronously.

[0216] Among them, the RRC connection release message sent by the network-side device to the terminal device in the connected state is used to indicate the dedicated PUSCH resource for CG-SDT.

[0217] In an embodiment of the present disclosure, after a terminal device in the connected state receives an RRC connection release message sent by a network-side device, it switches from the connected state to the disconnected state. The terminal device in the disconnected state can determine candidate downlink receiving beams used to receive the RRC release message. Furthermore, since the terminal device supports beam reciprocity during the CG-SDT process, the terminal device can determine candidate uplink transmitting beams based on the candidate downlink receiving beams.

[0218] After that, the terminal device can use the candidate uplink transmitting beams on dedicated PUSCH resources to perform CG-SDT and / or perform CG-SDT retransmission to send small data packets.

[0219] Among them, the process of the terminal device performing CG-SDT and / or performing CG-SDT retransmission can refer to the above-related description, and the same content will not be repeated here.

[0220] It can be understood that in the case where the terminal device does not support beam reciprocity during the CG-SDT process, the terminal device needs to perform uplink beam scanning to determine better or optimal candidate uplink transmitting beams, and use the determined candidate uplink transmitting beams to perform CG-SDT to send small data packets.

[0221] In an embodiment of the present disclosure, since the terminal device supports beam reciprocity during the CG-SDT process, it can determine candidate uplink transmitting beams based on the candidate downlink receiving beams used by the network-side device to send the RRC release message, and then use the candidate uplink transmitting beams to perform CG-SDT to send small data packets. Thus, the terminal device does not need to perform uplink beam scanning to determine the uplink beam, which can save the energy consumption of the terminal device. Moreover, since the terminal device can determine candidate uplink transmitting beams without performing beam scanning, the delay can be reduced.

[0222] It should be noted that in an embodiment of the present disclosure, S101 and S102 can be implemented separately, or can be implemented together with any other step in an embodiment of the present disclosure. For example, they can be implemented together with S91 in an embodiment of the present disclosure. The embodiment of the present disclosure does not make any limitations in this regard.

[0223] Please refer to Figure 11 , Figure 11 which is a flowchart of another information transmission method provided by an embodiment of the present disclosure.

[0224] As Figure 11 shown, this method is executed by a network-side device, and this method may include but is not limited to the following steps:

[0225] S111: Send an RRC release message to a terminal device in the connected state and release quasi co-location (QCL) information, where the RRC release message is used to indicate dedicated PUSCH resources for performing CG-SDT.

[0226] S112: Receive data sent by a terminal device in a non-connected state on a dedicated PUSCH resource using a candidate uplink transmission beam during a CG-SDT process and / or during a CG-SDT retransmission process, where the candidate uplink transmission beam is determined by the terminal device based on a candidate downlink reception beam for receiving an RRC release message.

[0227] For the relevant descriptions of S111 and S112, reference can be made to the relevant descriptions in the foregoing embodiments, which will not be elaborated herein.

[0228] S113: Send a data reception success indication to the terminal device in the non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

[0229] In the embodiments of the present disclosure, the terminal device uses a candidate uplink transmission beam on a dedicated PUSCH resource to perform CG-SDT and / or perform a CG-SDT retransmission, and sends data to the network-side device, that is, sends a small data packet. After the network-side device receives the data sent by the terminal device, that is, receives the small data packet sent by the terminal device, it may send a data reception success indication to the terminal device to inform the terminal device that it has received the data sent by the terminal device during the CG-SDT and / or during the CG-SDT retransmission.

[0230] It should be noted that in the embodiments of the present disclosure, S111 to S113 may be implemented independently, or may be implemented together with any other step in the embodiments of the present disclosure, for example, implemented together with S91 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations thereto.

[0231] Please refer to Figure 12 , Figure 12 which is a flowchart of another information transmission method provided by the embodiments of the present disclosure.

[0232] As Figure 12 shown, this method is executed by the terminal device, and this method may include but is not limited to the following steps:

[0233] S121: After sending a data reception success indication to the terminal device and before sending a connection release message to the terminal device, when it is determined that the terminal device supports beam reciprocity, determine a candidate SSB beam according to a dedicated PUSCH resource and a mapping relationship; send a PDCCH carrying a C-RNTI to the terminal device on the candidate SSB beam, where a synchronization signal block SSB beam has a mapping relationship with the PUSCH resource.

[0234] It can be understood that CG-SDT includes two phases: an initial data transmission phase and a subsequent data transmission phase.

[0235] Among them, in the initial data transmission phase, the terminal device in the non-connected state uses the candidate uplink transmission beam on the dedicated PUSCH resource to perform CG-SDT and / or perform CG-SDT retransmission, and sends data (small data packets) to the network-side device. After the network-side device receives the data (small data packets) sent by the terminal device for CG-SDT and / or CG-SDT retransmission, it can send a data reception success indication to the terminal device.

[0236] Among them, when the terminal device is in the connected state, the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process, and there is an association relationship between the SSB beam and the PUSCH resource. The network-side device can determine the downlink beam according to the association relationship between the SSB beam and the PUSCH, and the dedicated PUSCH resource used by the terminal device for CG-SDT and / or CG-SDT retransmission, and then send a data reception success indication to the terminal device on the downlink beam.

[0237] Among them, the subsequent data transmission phase can be after the terminal device receives the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device. In the subsequent data transmission phase, the terminal device continuously repeats listening to the PDCCH.

[0238] It can be understood that after the terminal device receives the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device, in the subsequent data transmission phase, the terminal device listens to the physical downlink control channel PDCCH and receives the PDCCH carrying the C-RNTI on the candidate SSB beam.

[0239] Among them, there is a mapping relationship between the SSB and the PUSCH resource, and when the terminal device is in the connected state, the network-side device has learned that the terminal device supports beam reciprocity during the CG-SDT process. In the subsequent data transmission phase, the network-side device can determine the corresponding candidate SSB beam according to the dedicated PUSCH resource and the mapping relationship used by the terminal device for SDT and / or SDT retransmission, and send the PDCCH carrying the C-RNTI to the terminal device on the candidate SSB beam.

[0240] Based on this, the terminal device listens to the PDCCH and can receive the PDCCH carrying the C-RNTI on the candidate SSB beam to further send the PUSCH to the network-side device.

[0241] It should be noted that in the embodiments of the present disclosure, S121 can be implemented alone or in combination with any other step in the embodiments of the present disclosure. For example, it can be implemented in combination with S91 and / or S101 and S102 and / or S111 to S1134 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard.

[0242] Please refer to Figure 13 , Figure 13 which is a flowchart of another information transmission method provided by the embodiments of the present disclosure.

[0243] As Figure 13 shown, this method is executed by a terminal device, and this method may include but is not limited to the following steps:

[0244] S131: After sending a data reception success indication to the terminal device and before sending a connection release message to the terminal device, when it is determined that the terminal device supports beam reciprocity, determine candidate SSB beams according to dedicated PUSCH resources and mapping relationships; send a PDCCH carrying C-RNTI to the terminal device on the candidate SSB beams, where the synchronization signal block SSB beams and the PUSCH resources have a mapping relationship.

[0245] Among them, the relevant description of S131 can refer to the relevant description in the above embodiments and will not be elaborated here.

[0246] S132: Receive a PUSCH sent by a terminal device in a non-connected state on an uplink SSB beam, where the uplink SSB beam is determined by the terminal device according to the candidate SSB beams.

[0247] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. The terminal device listens to the PDCCH and receives the PDCCH carrying C-RNTI on the candidate SSB beams. It can determine the uplink SSB beam according to the candidate SSB beams. Further, it can send a PUSCH to the network-side device on the uplink SSB beam.

[0248] It can be understood that when the terminal device does not support beam reciprocity, the terminal device needs to perform uplink beam scanning to determine a beam with better or best beam quality, determine it as the uplink transmission beam, and then use the uplink transmission beam to send the PUSCH.

[0249] In the embodiments of the present disclosure, the terminal device supports beam reciprocity during the CG-SDT process. After the terminal device receives the PDCCH on the candidate SSB beams, it can directly determine the uplink SSB beam according to the candidate SSB beams. The terminal device does not need to perform uplink beam scanning and can directly determine the uplink SSB beam, which can save the energy consumption of the terminal device and reduce the delay.

[0250] It should be noted that in the embodiments of the present disclosure, S131 and S132 can be implemented independently, or can be implemented together with any other step in the embodiments of the present disclosure. For example, they can be implemented together with S91 and / or S101 and S102 and / or S111 to S113 in the embodiments of the present disclosure. The embodiments of the present disclosure do not make any limitations in this regard.

[0251] In the above embodiments provided by the present disclosure, the methods provided by the embodiments of the present disclosure are introduced from the perspectives of the terminal device and the network-side device respectively. To implement each function in the methods provided by the above embodiments of the present disclosure, the terminal device and the network-side device may include a hardware structure and software modules, and implement the above functions in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module. A certain function among the above functions can be executed in the form of a hardware structure, a software module, or a combination of a hardware structure and a software module.

[0252] Please refer to Figure 14 , which is a schematic structural diagram of a communication device 1 provided by the embodiments of the present disclosure. Figure 14 The shown communication device 1 may include a transceiver module 11 and a processing module 12. The transceiver module 11 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 11 can implement the sending function and / or the receiving function.

[0253] The communication device 1 can be a terminal device, or a device in the terminal device, or a device that can be used in matching with the terminal device. Alternatively, the communication device 1 can be a network-side device, or a device in the network-side device, or a device that can be used in matching with the network-side device.

[0254] The communication device 1 is a terminal device:

[0255] The device includes: a transceiver module 11.

[0256] The transceiver module 11 is configured to send capability indication information to the network-side device in the connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT) process.

[0257] In some embodiments, the terminal device supporting beam reciprocity means that the terminal device can determine the uplink transmission beam according to the downlink reception beam without performing uplink beam scanning.

[0258] In some embodiments, the transceiver module 11 is further configured to receive a Radio Resource Control (RRC) release message sent by a network-side device in the connected state and switch to the non-connected state, where the RRC release message is used to indicate the Physical Uplink Shared Channel (PUSCH) resources for Cell-specific Grant-based Semi-persistent Downlink Transmission (CG-SDT).

[0259] The processing module 12 is configured to determine a candidate uplink transmission beam according to a candidate downlink reception beam for receiving the RRC release message in the non-connected state.

[0260] The transceiver module 11 is further configured to perform CG-SDT and / or perform CG-SDT retransmission on the dedicated PUSCH resources using the candidate uplink transmission beam in the non-connected state.

[0261] In some embodiments, the transceiver module 11 is further configured to receive a data reception success indication sent by a network-side device for a terminal device in the non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

[0262] In some embodiments, there is a mapping relationship between the Synchronization Signal Block (SSB) beam and the PUSCH resources. After receiving the data reception success indication sent by the network-side device and before receiving the connection release message sent by the network-side device,

[0263] The transceiver module 11 is further configured to monitor the Physical Downlink Control Channel (PDCCH) and receive the PDCCH carrying the Cell Radio Network Temporary Identity (C-RNTI) on the candidate SSB beam, where the candidate SSB beam is determined by the network-side device according to the dedicated PUSCH resources and the mapping relationship when it is determined that the terminal device supports beam reciprocity.

[0264] In some embodiments, the processing module 12 is further configured to determine an uplink SSB beam according to the candidate SSB beam.

[0265] The transceiver module 11 is further configured to send a PUSCH to the network-side device on the uplink SSB beam.

[0266] The communication device 1 is a network-side device:

[0267] The device includes: a transceiver module 11.

[0268] The transceiver module 11 is configured to receive capability indication information sent by a terminal device in the connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the Cell-specific Grant-based Semi-persistent Downlink Transmission (CG-SDT) process.

[0269] In some embodiments, the terminal device supports beam reciprocity, which means that the terminal device can determine the uplink transmission beam according to the downlink reception beam without performing uplink beam scanning.

[0270] In some embodiments, the transceiver module 11 is further configured to send an RRC release message to a terminal device in a connected state and release the quasi co-location (QCL) information, where the RRC release message is used to indicate the dedicated PUSCH resource for CG-SDT.

[0271] The transceiver module 11 is further configured to receive data sent by a terminal device in a non-connected state using a candidate uplink transmission beam for CG-SDT and / or for CG-SDT retransmission on the dedicated PUSCH resource, where the candidate uplink transmission beam is determined by the terminal device according to the candidate downlink reception beam for receiving the RRC release message.

[0272] In some embodiments, the transceiver module 11 is further configured to send a data reception success indication to a terminal device in a non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

[0273] In some embodiments, there is a mapping relationship between the synchronization signal block (SSB) beam and the PUSCH resource. After sending the data reception success indication to the terminal device and before sending the connection release message to the terminal device,

[0274] The processing module 12 is configured to determine that the terminal device supports beam reciprocity and determine a candidate SSB beam according to the dedicated PUSCH resource and the mapping relationship.

[0275] The transceiver module 11 is further configured to send a PDCCH carrying a C-RNTI to the terminal device on the candidate SSB beam.

[0276] In some embodiments, the transceiver module 11 is further configured to receive a PUSCH sent by a terminal device in a non-connected state on the uplink SSB beam, where the uplink SSB beam is determined by the terminal device according to the candidate SSB beam.

[0277] Regarding the device in the above embodiments, the specific manner in which each module performs operations has been described in detail in the embodiments related to the method, and will not be elaborated here.

[0278] The communication device 1 provided in the above embodiments of the present disclosure achieves the same or similar beneficial effects as the capability reporting method provided in some of the above embodiments, and will not be repeated here.

[0279] Please refer to Figure 15 , Figure 15It is a schematic structural diagram of another communication device 1000 provided by an embodiment of the present disclosure. The communication device 1000 may be a network-side device, a terminal device, a chip, a chip system, or a processor that supports the network-side device to implement the above method, or a chip, a chip system, or a processor that supports the terminal device to implement the above method. The communication device 1000 can be used to implement the method described in the above method embodiment. For details, please refer to the description in the above method embodiment.

[0280] The communication device 1000 may include one or more processors 1001. The processor 1001 may be a general-purpose processor or a dedicated processor, etc. For example, it may be a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a network-side device, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute computer programs, and process the data of the computer programs.

[0281] Optionally, the communication device 1000 may further include one or more memories 1002, on which a computer program 1004 may be stored. The memory 1002 executes the computer program 1004 to enable the communication device 1000 to execute the method described in the above method embodiment. Optionally, data may also be stored in the memory 1002. The communication device 1000 and the memory 1002 may be provided separately or integrated together.

[0282] Optionally, the communication device 1000 may further include a transceiver 1005 and an antenna 1006. The transceiver 1005 may be referred to as a transceiver unit, a transceiver, or a transceiver circuit, etc., for implementing the transceiver function. The transceiver 1005 may include a receiver and a transmitter. The receiver may be referred to as a receiver or a receiving circuit, etc., for implementing the receiving function; the transmitter may be referred to as a transmitter or a transmitting circuit, etc., for implementing the transmitting function.

[0283] Optionally, the communication device 1000 may further include one or more interface circuits 1007. The interface circuit 1007 is used to receive code instructions and transmit them to the processor 1001. The processor 1001 runs the code instructions to enable the communication device 1000 to execute the method described in the above method embodiment.

[0284] When the communication device 1000 is a terminal device: the transceiver 1005 is used to execute Figure 4 S41 in Figure 5 S51 and S53 in Figure 6 S61, S63 and S64 in Figure 7 S71 in Figure 8 S81 and S83 in The processor 1001 is used to executeFigure 5 S52 in; Figure 6 S62 in; Figure 8 S82 in.

[0285] The communication device 1000 is a network side device: the transceiver 1005 is used to perform Figure 9 S91 in; Figure 10 S101 and S102 in; Figure 11 S111 to S113; Figure 12 S121 in; Figure 13 S131 and S132 in.

[0286] In one implementation, the processor 1001 may include a transceiver for implementing receiving and sending functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing the receiving and sending functions may be separate or integrated. The above-mentioned transceiver circuit, interface, or interface circuit may be used for reading and writing code / data, or the above-mentioned transceiver circuit, interface, or interface circuit may be used for transmitting or delivering signals.

[0287] In one implementation, the processor 1001 may store a computer program 1003, which runs on the processor 1001 and enables the communication device 1000 to perform the method described in the above method embodiment. The computer program 1003 may be fixed in the processor 1001, in which case the processor 1001 may be implemented by hardware.

[0288] In one implementation, the communication device 1000 may include circuitry that can implement the functions of transmitting, receiving, or communicating in the foregoing method embodiments. The processor and transceiver described in this disclosure may be implemented on an integrated circuit (IC), analog IC, radio frequency integrated circuit (RFIC), mixed-signal IC, application specific integrated circuit (ASIC), printed circuit board (PCB), electronic device, etc. The processor and transceiver may also be fabricated using various IC process technologies, such as complementary metal oxide semiconductor (CMOS), N-type metal oxide semiconductor (NMOS), P-type metal oxide semiconductor (PMOS), bipolar junction transistor (BJT), BiCMOS, silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0289] The communication device described in the above embodiments may be a terminal device, but the scope of the communication device described in this disclosure is not limited thereto, and the structure of the communication device may not be restricted by Figure 15 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be:

[0290] (1) An independent integrated circuit (IC), or chip, or chip system or subsystem;

[0291] (2) A collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and computer programs;

[0292] (3) An ASIC, such as a modem;

[0293] (4) A module that can be embedded in other devices;

[0294] (5) A receiver, terminal device, smart terminal device, cellular phone, wireless device, handset, mobile unit, vehicle-mounted device, network device, cloud device, artificial intelligence device, etc.;

[0295] (6) Others, etc.

[0296] For the case where the communication device may be a chip or chip system, please refer toFigure 16 , which is a structural diagram of a chip provided in an embodiment of the present disclosure.

[0297] The chip 1100 includes a processor 1101 and an interface 1103. Among them, the number of processors 1101 can be one or more, and the number of interfaces 1103 can be multiple.

[0298] For the case where the chip is used to implement the functions of the network-side device in the embodiments of the present disclosure:

[0299] The interface 1103 is used to receive code instructions and transmit them to the processor.

[0300] The processor 1101 is used to run code instructions to execute the capability reporting method as described in some of the above embodiments.

[0301] For the case where the chip is used to implement the functions of the terminal device in the embodiments of the present disclosure:

[0302] The interface 1103 is used to receive code instructions and transmit them to the processor.

[0303] The processor 1101 is used to run code instructions to execute the capability reporting method as described in some of the above embodiments.

[0304] Optionally, the chip 1100 further includes a memory 1102, and the memory 1102 is used to store necessary computer programs and data.

[0305] Those skilled in the art can also understand that the various illustrative logical blocks and steps listed in the embodiments of the present disclosure can be implemented by electronic hardware, computer software, or a combination of both. Whether such a function is implemented by hardware or software depends on the specific application and the design requirements of the entire system. For each specific application, those skilled in the art can use various methods to implement the described function, but such implementation should not be construed as exceeding the scope of protection of the embodiments of the present disclosure.

[0306] The embodiments of the present disclosure further provide a capability reporting system, which includes the foregoing Figure 14 communication device as the terminal device and the communication device as the network-side device in the embodiments, or, the system includes the foregoing Figure 15 communication device as the terminal device and the communication device as the network-side device in the embodiments.

[0307] The present disclosure also provides a readable storage medium, on which instructions are stored, and when the instructions are executed by a computer, the functions of any of the foregoing method embodiments are implemented.

[0308] The present disclosure also provides a computer program product, which when executed by a computer implements the functions of any of the above method embodiments.

[0309] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, the processes or functions described in the embodiments of the present disclosure are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer program can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another. For example, the computer program can be transmitted from a website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (such as a floppy disk, hard disk, magnetic tape), an optical medium (such as a high-definition digital video disc (DVD)), or a semiconductor medium (such as a solid state disk (SSD)), etc.

[0310] Those of ordinary skill in the art can understand that the various numerical numbers such as the first and second involved in the present disclosure are only for the convenience of description and are not used to limit the scope of the embodiments of the present disclosure, nor do they represent the order of precedence.

[0311] At least one in the present disclosure can also be described as one or more. The plurality can be two, three, four, or more, and the present disclosure does not make any restrictions. In the embodiments of the present disclosure, for a technical feature, the technical features in this technical feature are distinguished by "first", "second", "third", "A", "B", "C", and "D", etc. There is no order of precedence or size order among the technical features described by the "first", "second", "third", "A", "B", "C", and "D".

[0312] The corresponding relationships shown in each table in this disclosure can be configured or predefined. The values of the information in each table are merely examples and can be configured as other values, which are not limited in this disclosure. When configuring the corresponding relationships between the configuration information and each parameter, it is not necessarily required to configure all the corresponding relationships shown in each table. For example, in the tables in this disclosure, the corresponding relationships shown in some rows can also not be configured. Another example is that appropriate deformation adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the titles of the above tables can also use other names that can be understood by the communication device, and the values or representation methods of the parameters can also use other values or representation methods that can be understood by the communication device. When implementing the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables or hash maps, etc.

[0313] The predefined in this disclosure can be understood as defining, predefining, storing, prestoring, pre-negotiating, preconfiguring, solidifying, or pre-burning.

[0314] Those of ordinary skill in the art can realize that the units and algorithm steps of each example described in combination with the embodiments disclosed in this article can be implemented by electronic hardware or a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this disclosure.

[0315] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be repeated here.

[0316] As described above, the above is only the specific implementation manner of this disclosure, but the protection scope of this disclosure is not limited thereto. Any person skilled in the art within the technical scope disclosed in this disclosure can easily think of changes or substitutions, which should all be covered by the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be subject to the protection scope of the claimed rights.

Claims

1. A method for reporting capabilities, characterized in that, The method is executed by a terminal device and includes: The terminal device sends capability indication information to a network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT). The terminal device that supports beam reciprocity during the CG-SDT process supports determining an uplink transmission beam based on a downlink reception beam and uses the determined uplink transmission beam to send small data packets to the network-side device.

2. The method according to claim 1, characterized in that, It further includes: The terminal device receives a radio resource control (RRC) release message sent by the network-side device in the connected state and switches to a non-connected state, where the RRC release message is used to indicate the dedicated physical uplink shared channel (PUSCH) resource for CG-SDT. The terminal device determines a candidate uplink transmission beam according to a candidate downlink reception beam for receiving the RRC release message in the non-connected state. The terminal device performs CG-SDT and / or CG-SDT retransmission on the dedicated PUSCH resource using the candidate uplink transmission beam in the non-connected state.

3. The method according to claim 2, characterized in that, It further includes: The terminal device receives a data reception success indication sent by the network-side device in the non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

4. The method according to claim 3, wherein There is a mapping relationship between the synchronization signal block (SSB) beam and the PUSCH resource. After receiving the data reception success indication sent by the network-side device and before receiving a connection release message sent by the network-side device, it further includes: Listening to the physical downlink control channel (PDCCH) and receiving the PDCCH carrying the cell radio network temporary identity (C-RNTI) on a candidate SSB beam, where the candidate SSB beam is determined by the network-side device according to the dedicated PUSCH resource and the mapping relationship when determining that the terminal device supports beam reciprocity.

5. The method according to claim 4, wherein It further includes: Determining an uplink SSB beam according to the candidate SSB beam. Sending a PUSCH to the network-side device on the uplink SSB beam.

6. A method for reporting capabilities, characterized in that, The method is executed by a network-side device and includes: Receiving capability indication information sent by a terminal device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the configured grant small data packet transmission (CG-SDT). The terminal device that supports beam reciprocity during the CG-SDT process supports determining an uplink transmission beam based on a downlink reception beam and uses the determined uplink transmission beam to send small data packets to the network-side device.

7. The method according to claim 6, wherein It further includes: Sending an RRC release message to the terminal device in the connected state and releasing the quasi-co-location (QCL) information, where the RRC release message is used to indicate the dedicated PUSCH resource for CG-SDT. Receiving data sent by the terminal device in a non-connected state on the dedicated PUSCH resource using a candidate uplink transmission beam for CG-SDT and / or for CG-SDT retransmission, where the candidate uplink transmission beam is determined by the terminal device according to the candidate downlink reception beam for receiving the RRC release message.

8. The method according to claim 7, wherein Further comprising: Sending a data reception success indication to the terminal device in a non-connected state, where the data reception success indication is used to indicate that the network-side device has received the data sent by the terminal device during the CG-SDT process and / or during the CG-SDT retransmission process.

9. The method according to claim 8, wherein There is a mapping relationship between the synchronization signal block SSB beam and the PUSCH resource. After sending the data reception success indication to the terminal device and before sending the connection release message to the terminal device, it further comprises: Determining that the terminal device supports beam reciprocity, and determining a candidate SSB beam according to the dedicated PUSCH resource and the mapping relationship; Sending a PDCCH carrying a C-RNTI to the terminal device on the candidate SSB beam.

10. The method according to claim 9, characterized in that, Further comprising: Receiving a PUSCH sent by the terminal device in a non-connected state on an uplink SSB beam, where the uplink SSB beam is determined by the terminal device according to the candidate SSB beam.

11. A communication device, characterized in that, The apparatus is disposed in a terminal device and includes: A transceiver module, configured to send capability indication information to a network-side device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the CG-SDT process of configured grant small packet transmission, and the terminal device that supports beam reciprocity during the CG-SDT process supports determining an uplink transmission beam according to a downlink reception beam and using the determined uplink transmission beam to send small packets to the network-side device.

12. A communication device, characterized in that, The apparatus is disposed in a network-side device and includes: A transceiver module, configured to receive capability indication information sent by a terminal device in a connected state, where the capability indication information is used to indicate that the terminal device supports beam reciprocity during the CG-SDT process of configured grant small packet transmission, and the terminal device that supports beam reciprocity during the CG-SDT process supports determining an uplink transmission beam according to a downlink reception beam and using the determined uplink transmission beam to send small packets to the network-side device.

13. A communication device, characterized in that, The apparatus includes a processor and a memory, and a computer program is stored in the memory. The processor executes the computer program stored in the memory to cause the apparatus to execute the method according to any one of claims 1 to 5, or the processor executes the computer program stored in the memory to cause the apparatus to execute the method according to any one of claims 6 to 10.

14. A communication device, characterized in that, Comprising: A processor and an interface circuit; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is used to run the code instructions to execute the method according to any one of claims 1 to 5, or is used to run the code instructions to execute the method according to any one of claims 6 to 10.

15. A computer-readable storage medium for storing instructions that, when executed, cause the method according to any one of claims 1 to 5 to be implemented, or that, when executed, cause the method according to any one of claims 6 to 10 to be implemented.

Images