CN117413547A

CN117413547A - Information indicating method, terminal device, network device, chip and storage medium

Info

Publication number: CN117413547A
Application number: CN202180098766.6A
Authority: CN
Inventors: 胡奕; 李海涛
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-08-16
Filing date: 2021-08-16
Publication date: 2024-01-16
Also published as: WO2023019409A1

Abstract

The present application relates to an information indicating method, a terminal device, a network device, a chip, a computer readable storage medium, a computer program product, a computer program and a communication system. The method comprises the following steps: the terminal device transmits information indicating whether the terminal device has a capability of ending repeated transmission of PUSCH in advance to the network device based on PUSCH. The embodiment of the application is beneficial to realizing the advanced ending of the repeated transmission of the PUSCH and saving uplink resources.

Description

Information indicating method, terminal device, network device, chip and storage medium

Technical Field

The present application relates to the field of communications, and more particularly, to an information indicating method, a terminal device, a network device, a chip, a computer-readable storage medium, a computer program product, a computer program, and a communication system.

Background

Communication coverage is one of the main network capabilities of a communication system. The fifth Generation communication (5G) system operates in a higher frequency band than the long term evolution (Long Term Evolution, LTE) system. The higher the operating frequency band, the greater the path loss experienced by the signal, resulting in reduced coverage. In addition, the transmission power of the network device is far greater than that of the terminal device, so that the uplink coverage faces the problem of more serious coverage limitation.

For a physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), uplink coverage may be enhanced by using a retransmission mechanism. However, repeating the transmission will increase the use of uplink resources.

Disclosure of Invention

In view of this, the embodiments of the present application provide an information indication method, a terminal device, a network device, a chip, and a storage medium, which can be used to optimize a PUSCH retransmission mechanism for a random access procedure.

The embodiment of the application provides an information indication method, which comprises the following steps:

the terminal device transmits information indicating whether the terminal device has a capability of ending repeated transmission of PUSCH in advance to the network device based on PUSCH.

the network device receives information sent by the terminal device based on the PUSCH and used for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance.

The embodiment of the application also provides a terminal device, which comprises:

and the first communication module is used for sending information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance to the network equipment based on the PUSCH.

The embodiment of the application also provides a network device, which comprises:

And the second communication module is used for receiving information which is sent by the terminal equipment based on the PUSCH and is used for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance.

The embodiment of the application also provides a terminal device, which comprises: the processor and the memory are used for storing the computer program, and the processor calls and runs the computer program stored in the memory to execute the information indication method provided by any embodiment of the application.

The embodiment of the application also provides a network device, which comprises: the processor and the memory are used for storing the computer program, and the processor calls and runs the computer program stored in the memory to execute the information indication method provided by any embodiment of the application.

The embodiment of the application also provides a chip, which comprises: and a processor for calling and running the computer program from the memory, so that the device with the chip is used for executing the information indication method provided by any embodiment of the application.

The embodiment of the application also provides a computer readable storage medium for storing a computer program, wherein the computer program causes a computer to execute the information indication method provided by any embodiment of the application.

Embodiments of the present application also provide a computer program product, including computer program instructions, where the computer program instructions cause a computer to perform the information indication method provided in any of the embodiments of the present application.

The embodiment of the application also provides a computer program, and the computer program enables the computer to execute the information indication method provided by any embodiment of the application.

The embodiment of the application also provides a communication system which comprises a terminal device and a network device for executing the information indication method provided by any embodiment of the application.

According to the technical scheme of the embodiment of the application, the terminal equipment sends the information based on the PUSCH to indicate whether the terminal equipment has the capability of finishing repeated transmission of the PUSCH in advance, so that the network equipment can respond to the PUSCH as early as possible according to the relevant capability of different terminals, thereby being beneficial to realizing the purpose of finishing repeated transmission of the PUSCH in advance and saving uplink resources.

Drawings

Fig. 1 is a schematic diagram of a communication system architecture according to an embodiment of the present application.

Fig. 2A is a schematic diagram of a contention-based random access scheme according to an embodiment of the present application.

Fig. 2B is a schematic diagram of a non-contention based random access scheme according to an embodiment of the present application.

Fig. 3A is a schematic diagram of a two-step random access procedure in a scenario according to an embodiment of the present application.

Fig. 3B is a schematic diagram of a two-step random access procedure in another scenario according to an embodiment of the present application.

Fig. 4 is a flow diagram of an information indication method according to an embodiment of the present application.

Fig. 5 is a flow chart of an information indication method according to another embodiment of the present application.

Fig. 6 is a schematic diagram of an application example one of the information indicating method according to the embodiment of the present application.

Fig. 7 is a schematic diagram of an application example two of the information indicating method according to the embodiment of the present application.

Fig. 8 is a schematic block diagram of a terminal device according to an embodiment of the present application.

Fig. 9 is a schematic block diagram of a terminal device according to another embodiment of the present application.

Fig. 10 is a schematic block diagram of a network device according to an embodiment of the present application.

Fig. 11 is a schematic block diagram of a network device according to another embodiment of the present application.

Fig. 12 is a schematic block diagram of a communication device of an embodiment of the present application.

Fig. 13 is a schematic block diagram of a chip of an embodiment of the present application.

Fig. 14 is a schematic block diagram of a communication system of an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.

The technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system over unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system over unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, with the development of communication technology, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., and the embodiments of the present application may also be applied to these communication systems.

Optionally, the communication system in the embodiment of the present application may be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, a dual connectivity (Dual Connectivity, DC) scenario, and a Stand Alone (SA) fabric scenario.

Embodiments of the present application describe various embodiments in connection with network devices and terminal devices, where a terminal device may also be referred to as a User Equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, user Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In embodiments of the present application, the terminal device may be deployed on land, including indoor or outdoor, hand-held, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present application, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present application, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

In this embodiment of the present application, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device (gNB) in NR network, or a network device in a PLMN network of future evolution, etc.

By way of example and not limitation, in embodiments of the present application, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In this embodiment of the present application, a network device may provide a service for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to a network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

Fig. 1 schematically shows a wireless communication system 1000 comprising one network device 1100 and two terminal devices 1200. Alternatively, the wireless communication system 1000 may include a plurality of network devices 1100, and the coverage area of each network device 1100 may include other numbers of terminal devices, which are not limited by the embodiments of the present application. Optionally, the wireless communication system 1000 shown in fig. 1 may further include other network entities such as a mobility management entity (Mobility Management Entity, MME), an access and mobility management function (Access and Mobility Management Function, AMF), and the embodiment of the present application is not limited thereto.

It should be understood that a device having a communication function in a network/system in an embodiment of the present application may be referred to as a communication device. Taking the communication system shown in fig. 1 as an example, the communication device may include a network device and a terminal device with a communication function, where the network device and the terminal device may be specific devices in the embodiments of the present application, and are not described herein again; the communication device may also include other devices in the communication system, such as a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" is used herein to describe association of associated objects, for example, to indicate that there may be three relationships between the associated objects, for example, a and/or B, may indicate: three cases of A alone, A and B together, and B alone exist. The character "/" herein generally indicates that the context associated object is an "or" relationship.

It should be understood that, in the embodiments of the present application, the "indication" may be a direct indication, an indirect indication, or an indication having an association relationship. For example, a indicates B, which may mean that a indicates B directly, e.g., B may be obtained by a; it may also indicate that a indicates B indirectly, e.g. a indicates C, B may be obtained by C; it may also be indicated that there is an association between a and B.

In the description of the embodiments of the present application, the term "corresponding" may indicate that there is a direct correspondence or an indirect correspondence between the two, or may indicate that there is an association between the two, or may indicate a relationship between the two and the indicated, configured, or the like.

In order to facilitate understanding of the technical solutions of the embodiments of the present application, the following description is given of related technologies of the embodiments of the present application, and the following related technologies may be optionally combined with the technical solutions of the embodiments of the present application as an alternative, which all belong to the protection scope of the embodiments of the present application.

(one) radio resource control (Radio Resource Control, RRC) state

Due to the pursuit of speed, delay, high-speed mobility, energy efficiency and the diversity and complexity of future life services, 5G has been widely used. The main application scenarios of 5G include enhanced mobile Ultra-wideband (Enhance Mobile Broadband, emmbb), low latency high reliability communications (Ultra-Reliable and Low Latency Communications, URLLC), large scale machine type communications (Massive Machine Type Communication, mctc), and the like.

embbs still target users to obtain multimedia content, services, and data, and their demand is growing very rapidly. On the other hand, since the eMBB may be deployed in different scenarios, such as indoor, urban, rural, etc., the capability and demand of the eMBB are also relatively different, so that detailed analysis must be performed in connection with a specific deployment scenario. Typical applications of URLLC include: industrial automation, electric power automation, remote medical operation (surgery), traffic safety guarantee and the like. Typical characteristics of mctc include: high connection density, small data volume, low cost and long service life of the module, etc. are suitable for delay insensitive services.

NR can also be deployed independently. In a 5G network environment, in order to reduce air interface signaling and quickly restore a radio connection to quickly restore data traffic, a new RRC state, namely, an INACTIVE state (rrc_inactive), is defined. Rrc_inactive is different from an IDLE state (rrc_idle) and a CONNECTED state (rrc_connected). The characteristics of these states are as follows:

Rrc_idle: mobility is UE-based cell selection reselection, paging is initiated by a Core Network (CN), and the paging area is configured by the CN. The base station side does not have a UE Access Stratum (AS) context. There is no RRC connection.

Rrc_connected: there is an RRC connection and the base station and UE have a UE AS context. The network device knows that the location of the UE is cell specific. Mobility is mobility controlled by the network device. Unicast data may be transmitted between the UE and the base station.

Rrc_inactive: mobility is a UE-based cell selection reselection, there is a connection between CN-NRs, the UE AS context is present on a certain base station, paging is triggered by the radio access network (Radio Access Network, RAN), and the RAN-based paging area is managed by the RAN. The network device knows that the location of the UE is based on the paging area level of the RAN.

(two) NR random Access procedure

The random access procedure is mainly triggered by the following events:

-an RRC connection re-establishment procedure for the UE to re-establish the radio connection after a radio link failure;

-a handover for the UE to establish uplink synchronization with a new cell;

in the rrc_connected state, DL (Downlink) data arrives, when UL is in an out-of-sync state;

-in rrc_connected state, UL (Uplink) data arrives, when UL is in out-of-sync state or there is no physical Uplink control channel (Physical Uplink Control Channel, PUCCH) resource for sending a scheduling request (Scheduling Request, SR);

-SR failure;

-a synchronous reconfiguration request from RRC;

-the UE transitions from the rrc_inactive state to the rrc_connected state;

-establishing a time alignment during Secondary Cell (Scell) addition;

-request other system messages (System Information, SI);

beam failure recovery.

In the NR Rel-15 version, two random access modes are mainly supported: the contention-based random access scheme and the non-contention-based random access scheme, fig. 2A illustrates the contention-based random access scheme. Fig. 2B illustrates a non-contention based random access scheme.

As shown in fig. 2A, the contention-based random access procedure includes 4 steps. As shown in fig. 2B, the non-contention based random access procedure includes 2 steps. The detailed steps are as follows:

step 1: terminal sends Msg1 (Message 1) to the network

The terminal selects a physical random access channel (Physical Random Access Channel, PRACH) and transmits a selected preamble (preamble) on the selected PRACH. As shown in fig. 2B, if non-contention based random access, PRACH resources and preambles may be specified by a network (base station).

The network may estimate the grant size (grant) required for the terminal to transmit Msg3 (Message 3) based on the preamble.

Step 2: the network sends a random access response (Random Access Response, RAR) to the terminal

After the terminal transmits Msg1, a random access response time window (RA-ResponseWindow) is opened, and a physical downlink control channel (Physical Downlink Control Channel, PDCCH) scrambled by an RA-radio network temporary identifier (RA-Radio Network Temporary Identifier, RA-RNTI) is monitored within the window. The RA-RNTI relates to the PRACH time-frequency resources used by the terminal to transmit Msg 1.

After the terminal successfully receives the RA-RNTI scrambled PDCCH, it can acquire the physical downlink shared channel (Physical Downlink Shared Channel, PDSCH) scheduled by the PDCCH. The PDSCH includes an RAR (also referred to as Msg 2), which includes the following information:

a Back Indicator (BI) included in the subheader of the RAR, for indicating a Back-off time of retransmission Msg 1;

RA preamble identifier (Random Access Preamble Identifier, RAPID) in RAR: an index (preamble index) of its received preamble of the network response;

a set of timing advances (Timing Advance Group, TAG) contained in the payload (payload) of the RAR for adjusting the uplink timing;

Uplink grant information (UL grant): uplink resource indication for scheduling Msg 3;

temporary (Cell-Radio Network Temporary Identifier, C-RNTI): PDCCH (initial access) for scrambling Msg4.

If the terminal receives the PDCCH scrambled by the RAR-RNTI and the RAR contains the preamble index sent by the terminal, the terminal considers that the random access response is successfully received.

As shown in fig. 2B, for non-contention based random access, after the terminal successfully receives Msg2, the random access procedure ends. As shown in fig. 2A, for contention-based random access, after the terminal successfully receives the Msg2, it is further required to continue transmitting the Msg3 and receiving the Msg4, which specifically includes the following steps:

step 3: terminal transmitting Msg3 on network scheduling resource

Msg3 is mainly used to inform the network what event the random access channel (Random Access Channel, RACH) procedure is triggered by. For example, if it is an initial access random procedure, the UE ID and establishment cause will be carried in Msg3 (establishment cause); in the case of RRC reestablishment, the UE identity in connected state and establishment cause are carried. The terminal starts a random access contention resolution timer (RA-contentionresolution timer) after transmitting Msg3, and listens to the PDCCH during operation of the timer to receive Msg4.

Step 4: the network sends Msg4 (Message 4) to the terminal

Msg4 has mainly two roles, one for contention conflict resolution and the other for the network to transmit RRC configuration messages to the terminal. The contention resolution is achieved in two ways: one is PDCCH scheduling with C-RNTI scrambling by Msg4 if the UE carries the C-RNTI in Msg 3. Another is that if the UE does not carry a C-RNTI in the Msg3, such as initial access, then the Msg4 is scheduled with a PDCCH scrambled with a Temporary Cell radio network Temporary identity (TC-RNTI), then the solution of the collision is that the UE receives PDSCH of the Msg4 by matching the common control channel (Common Control Channel, CCCH) service data units (Service Data Unit, SDU) in the PDSCH.

From the above random access procedure, it can be seen that the main purpose of random access is for the terminal to acquire uplink synchronization with the cell. In the random access process, the network can know the time when the terminal sends the preamble according to the RACH time-frequency resource used by the preamble received from the terminal, so as to determine the initial Timing Advance (TA) of the terminal according to the sending time and the receiving time of the preamble, and inform the terminal through the RAR.

The time delay cost of the four-step random access is relatively large, and the method is unsuitable for a low-time delay high-reliability scene in 5G. In the NR standardization process, considering the characteristics of low-delay high-reliability related services, in the Rel-16 version, two-step random access is introduced, and the introduction of the two-step random access can reduce delay and simultaneously reduce signaling. Fig. 3A and 3B illustrate a two-step random access procedure in two scenarios. As shown in fig. 3A and 3B, the two-step random access mainly includes a terminal to network transmission MsgA (Message A) and a network to terminal transmission MsgB (Message B).

The MsgA in the two-step random access includes a Preamble transmitted on PRACH and load information transmitted on PUSCH. After the MsgA transmission, the terminal starts a response window (MsgB-ResponseWindow) of the MsgB, and listens for the response of the network side within the MsgB-ResponseWindow. As shown in fig. 3A, if an indication of success of contention conflict resolution issued by the network is received, the terminal ends the random access procedure. As shown in fig. 3B, if a back-off indication is received in the MsgB, the terminal performs transmission of Msg3 and listens for a contention conflict resolution result. If the contention resolution is unsuccessful after the Msg3 transmission, the terminal continues to transmit MsgA.

(III) NR uplink coverage enhancement

Coverage has always been one of the main network capabilities. Compared to LTE, 5G operates in a higher frequency band. For example: for FR1, the operating band is 3.5GHz (gigahertz); for the FR2 band, the operating band may be as high as 28GHz or 39GHz. The higher the operating frequency band, the greater the path loss experienced by the signal, resulting in reduced coverage. The transmission power of the network is usually much larger than that of the terminal, so that the uplink coverage suffers from more serious coverage limitation. In order to solve the above-described problems, coverage enhancement projects are the main research projects in the field of communication, and the main objective thereof is to study uplink coverage enhancement techniques applicable to FR1 and FR2 under time division duplex (Time Division Duplex, TDD)/frequency division duplex (Frequency Division Duplex, FDD), including coverage enhancement for PUSCH and coverage enhancement for PUCCH.

For PUSCH, uplink coverage may be improved by using a retransmission mechanism.

For example, the UE may determine whether PUSCH retransmission for Msg3 needs to be requested based on a measurement result of reference signal received power (Reference Signal Received Power, RSRP). I.e. when the RSRP measurement is less than an RSRP threshold, the UE may request PUSCH retransmission for Msg 3.

For example, the UE requests PUSCH retransmission of Msg3, and may configure different PRACH resources/preambles for the UE requesting PUSCH retransmission of Msg3 and the UE not requesting PUSCH retransmission of Msg3, so that the network may learn whether the UE requests PUSCH retransmission of Msg3 according to the PRACH resources/preambles used by the UE.

The inventor of the application has intensively studied and found that taking PUSCH transmission in a four-step random access process as an example, the monitoring of Msg4 is controlled by ra-contentioresolutiontimer. In the current NR system, ra-ContentionResolTimer is started after Msg3 transmission. After PUSCH retransmission with Msg3 is introduced, how to start ra-contentioresolutiontimer is a problem to be solved. If started after the completion of the retransmission of all Msg3, the terminal expects the network to respond to Msg4 after receiving all Msg3 retransmission. This is suitable for half duplex capable terminals, such as low capability (Reduced Capability, redCap) terminals, because such terminals can only start listening to the downlink after PUSCH transmission is complete anyway. However, for terminals with full duplex capability, both transmit and receive may be used. If the network only receives Msg3 successfully through partial Msg3 repeated transmission, the Msg4 can be responded as early as possible, so that if the terminal still receives Msg4 when transmitting the rest Msg3 repeated transmission, the terminal can terminate the rest Msg3 repeated transmission, thereby achieving the purpose of saving electricity, saving uplink resources and reducing uplink interference. Terminals of different capabilities can affect the implementation of the base station, and how to distinguish these terminals is a problem to be solved.

The solution provided by the embodiments of the present application is mainly used for solving at least one of the above problems.

For a more complete understanding of the nature and the technical content of the embodiments of the present invention, reference should be made to the following detailed description of embodiments of the invention, taken in conjunction with the accompanying drawings, which are meant to be illustrative only and not limiting of the embodiments of the invention.

Fig. 4 is a schematic flow chart of an information indication method according to an embodiment of the present application. The method may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method includes at least some of the following.

S41: the terminal device transmits information indicating whether the terminal device has a capability of ending repeated transmission of PUSCH in advance to the network device based on PUSCH.

The capability of ending the repeated transmission PUSCH in advance may also be referred to as an advanced PUSCH ending capability (early PUSCH termination capability).

Illustratively, the terminal device sends a capability indication message to the network device, where the capability indication message includes the above information for indicating whether the terminal device has the capability of ending the repeated PUSCH transmission in advance.

Illustratively, the capability indication information may include a medium access Control layer Control Element (MAC CE), RRC signaling, and the like.

Optionally, the capability of ending the repeated PUSCH transmission in advance includes a full duplex capability. In other words, if the terminal device is a half duplex capable terminal, the terminal device does not have the capability to end the repeated transmission of PUSCH in advance. If the terminal equipment is a full duplex capable terminal, the terminal has the capability of ending the repeated transmission of the PUSCH in advance. Terminal apparatuses having the capability of ending the repeated transmission PUSCH in advance include full duplex terminals, and terminal apparatuses not having the capability of ending the repeated transmission PUSCH in advance include half duplex terminals.

Optionally, the PUSCH includes:

PUSCH in message Msg3 of the four-step random access procedure, and/or,

PUSCH in message MsgA of two-step random access procedure.

That is, in the four-step random access procedure, the terminal device may instruct the terminal device whether to have the capability of ending the repeated transmission of PUSCH in advance based on the PUSCH in Msg 3. Or, in the two-step random access procedure, the terminal device may instruct the terminal device whether to have the capability of ending the repeated transmission of PUSCH in advance based on the PUSCH in the MsgA. In this way, the network device can determine whether to respond to PUSCH in advance according to whether the terminal device has the capability.

In practical applications, the information for indicating the above-mentioned capability may be transmitted based on PUSCH in a case where the terminal device does not indicate the above-mentioned capability based on other information.

An optional implementation manner is that the terminal device sends information for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance to the network device based on the PUSCH, including:

in the case that the first message in the random access process does not indicate whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance, the terminal equipment sends information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance to the network equipment based on the PUSCH; wherein the first message is used for transmitting a preamble in a random access procedure.

Illustratively, the first message includes Msg1 in a four-step random access procedure. In the four-step random procedure, the terminal device may select whether the terminal device has the above-described capability indicated in Msg1 or Msg3, and if the terminal device does not indicate whether the terminal device has the above-described capability in Msg1, the terminal device may transmit information for indicating whether the terminal device has the above-described capability based on PUSCH in Msg 3.

Another optional implementation manner is that the terminal device sends, to the network device, information for indicating whether the terminal device has a capability of ending the repeated PUSCH in advance, based on the PUSCH, including:

in the absence of a random access opportunity (RACH occision) or a preamble based on a second message in the random access procedure indicating whether the terminal device has the capability of ending the repeated transmission of PUSCH in advance, the terminal device transmits information for indicating whether the terminal device has the capability of ending the repeated transmission of PUSCH in advance to the network device based on PUSCH; wherein the second message is used for transmitting PUSCH and preamble.

Illustratively, the second message includes MsgA in a two-step random access procedure. In the two-step random access procedure, the terminal device may select a preamble based on the RO of MsgA or PUSCH of MsgA to indicate whether the terminal device has the above capability, and if the terminal device does not indicate whether the terminal device has the above capability based on the preamble of MsgA or RO of MsgA, the terminal device may transmit information indicating whether the terminal device has the above capability based on PUSCH of Msg 3.

In practical applications, whether the terminal device indicates the capability based on other information or not, the terminal device indicates whether the capability is available or not to the network device based on PUSCH.

Alternatively, the terminal device may determine through which information the above-described capabilities are indicated based on the indication of the network device. Specifically, the above information indication method may further include:

the terminal device determines, based on the received first indication information from the network device, information for indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance based on PUSCH transmission.

Optionally, the first indication information informs the terminal device in a broadcast mode, a multicast mode or a unicast mode.

Optionally, in the case that the first indication information is sent through unicast, the first indication information is sent through a dedicated signaling bearer.

And the network equipment receives the information sent by the terminal equipment based on the PUSCH according to the steps executed by the terminal equipment. Specifically, referring to fig. 5, the embodiment of the present application further provides an information indication method, including:

s51: the network device receives information sent by the terminal device based on the PUSCH and used for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance.

Optionally, the information indication method may further include:

the network equipment sends first indication information to the terminal equipment;

the first indication information is used for indicating the terminal equipment to send information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance or not based on the PUSCH.

In practical applications, there are various ways in which the terminal device sends the indication information based on PUSCH, and correspondingly, there are various ways in which the network device determines whether the terminal has the capability based on the received information. Various specific examples are provided below.

Example one:

the terminal device sends information for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance to the network device based on the PUSCH, and the information comprises: the terminal device transmits a MAC CE to the network device, wherein the MAC CE includes information for indicating whether the terminal device has a capability of ending the repeated transmission of PUSCH in advance.

Accordingly, the network device receives information sent by the terminal device based on the PUSCH and used for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance, and the information comprises: the network device receives a MAC CE including information for indicating whether the terminal device has a capability to end the repeated transmission PUSCH in advance.

For example, in case the terminal device has the capability to end the repeated transmission of PUSCH in advance, the MAC CE transmitted by the terminal device includes a first MAC CE corresponding to the first logical channel identification (Logical Channel Identifier, LCID). That is, if the MAC CE transmitted by the terminal device includes a MAC CE corresponding to a specific LCID, the terminal device is instructed to have the capability of ending the repeated PUSCH transmission in advance.

Accordingly, in case that the received MAC CE includes the first MAC CE corresponding to the first LCID, the network device determines that the terminal device has a capability to end the repeated transmission PUSCH in advance.

Optionally, the first MAC CE does not include a payload.

For another example, in the case where the terminal device does not have the capability of ending the repeated transmission of PUSCH in advance, the MAC CE transmitted by the terminal device does not include the first MAC CE corresponding to the first LCID. That is, if the transmitted MAC CE does not include a MAC CE corresponding to a specific LCID, the terminal device is instructed not to have the capability of ending the repeated PUSCH transmission in advance. I.e. the terminal device indicates to the terminal device whether the terminal device has or does not have the above-mentioned capability by transmitting or not transmitting a certain specific MAC CE.

Accordingly, in the case that the MAC CE does not include the first MAC CE corresponding to the first LCID, the network device determines that the terminal device does not have the capability to end the repeated transmission PUSCH in advance.

For another example, in a case where the terminal device does not have the capability of ending the repeated transmission of PUSCH in advance, the MAC CE transmitted by the terminal device includes a second MAC CE corresponding to the second LCID. That is, if the transmitted MAC CE includes a MAC CE corresponding to another specific LCID, the terminal device is instructed not to have the capability of ending the repeated transmission PUSCH in advance. I.e. the terminal device indicates whether the terminal device has the above-mentioned capability or not by means of the LCID corresponding to the specific MAC CE transmitted.

Accordingly, in the case where the MAC CE includes a second MAC CE corresponding to the second LCID, the network device determines that the terminal device does not have a capability to end the repeated transmission PUSCH in advance.

Optionally, the second MAC CE does not include a payload.

For another example, the PUSCH includes a third MAC CE, and a bit field in the payload of the third MAC CE is used to indicate whether the terminal device has the capability to end the repeated transmission of the PUSCH in advance.

Illustratively, the bit field includes one bit. The terminal device indicates whether the terminal device has the above-described capability based on one bit in a payload (payload) of a certain MAC CE. For example, a value of 1 for this bit indicates that the terminal device has the above-mentioned capability, and a value of 0 indicates that the terminal device does not have the above-mentioned capability.

Accordingly, the network device determines whether the terminal device has the capability to end the repeated transmission of PUSCH in advance based on the bit field in the payload of the third MAC CE.

Example two:

the terminal device sends information for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance to the network device based on the PUSCH, and the information comprises: the terminal device sends an RRC signaling to the network device, wherein the RRC signaling includes information indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance.

Accordingly, the network device receives information sent by the terminal device based on the PUSCH and used for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance, and the information comprises: the network device receives RRC signaling including information indicating whether the terminal device has the capability to end the repeated transmission of PUSCH in advance.

For example, the RRC signaling includes an information field for indicating whether the terminal device has the capability to end the repeated transmission of PUSCH in advance. That is, the RRC signaling may explicitly indicate whether the terminal device has the above-described capabilities.

Illustratively, the information field includes one bit. The terminal device indicates whether the terminal device has the above-described capability based on one bit of a certain RRC signaling. For example, a value of 1 for this bit indicates that the terminal device has the above-mentioned capability, and a value of 0 indicates that the terminal device does not have the above-mentioned capability.

Accordingly, the network device determines whether the terminal device has the capability of ending the repeated transmission of PUSCH in advance based on the information field in the RRC signaling.

For another example, the common control channel CCCH corresponding to RRC signaling is used to indicate whether the terminal device has the capability to end the repeated PUSCH transmission in advance. That is, RRC signaling may implicitly indicate whether or not the terminal device has the above-described capabilities. Specifically, a new CCCH may be introduced for RRC signaling sent by the half-duplex terminal device; the original CCCH is used for RRC signaling sent by the full duplex terminal device.

Illustratively, the RRC signaling corresponds to the first CCCH in case the terminal device has the capability to end the repeated transmission of PUSCH in advance.

For example, in case the terminal device does not have the capability to end the repeated transmission of PUSCH in advance, the RRC signaling corresponds to the second CCCH.

Accordingly, the network device determines whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance based on the CCCH corresponding to the RRC signaling.

Optionally, in a case where the RRC signaling corresponds to the first CCCH, the network device determines that the terminal device has a capability to end the repeated transmission of PUSCH in advance.

Optionally, in the case that the RRC signaling corresponds to the second CCCH, the network device determines that the terminal device does not have the capability to end the repeated transmission of PUSCH in advance.

Optionally, the embodiment of the present application further provides an implementation manner that the terminal device starts the random access contention resolution timer under different conditions.

Case one: information indicating that the terminal device has the capability of ending the repeated transmission PUSCH in advance has been transmitted;

if information indicating that the terminal device has the capability of ending the repeated transmission of the PUSCH in advance has been transmitted, the terminal device starts a random access contention resolution timer after the completion of the first repeated transmission of the PUSCH.

And a second case: no information is transmitted indicating that the terminal device has the capability to end the repeated transmission of PUSCH in advance;

alternatively, case two includes the terminal device having the capability of ending the repeated transmission PUSCH in advance but not transmitting information indicating that it has the capability to the terminal device, and the terminal device not having the capability of ending the repeated transmission PUSCH in advance. Alternatively, it may also include that the terminal device does not transmit information indicating that it has the capability, and that the terminal device transmits information indicating that it does not have the capability.

If no information indicating that the terminal device has the capability of ending the repeated transmission of PUSCH in advance is transmitted, the terminal device starts a random access contention resolution timer after the last repeated transmission of PUSCH is completed.

Illustratively, the random access contention resolution timer includes a random access contention resolution timer (RA-contentionresolution timer) in a four-step random access procedure or a response window (MsgB-ResponseWindow) of MsgB in a two-step random access procedure.

For the network device, if it determines that the terminal device has the above capability, it may choose to send a corresponding message for PUSCH, such as the above Msg4 or MsgB, to the terminal device before or after all repeated transmissions of PUSCH are completed.

That is, if the terminal device has the capability of ending the repeated transmission of PUSCH in advance and the network device completes the reception of PUSCH based on the partial repeated transmission of PUSCH, the network device can transmit a response message for PUSCH to the terminal device before the complete repeated transmission of PUSCH.

If the terminal device does not have the capability of ending the repeated transmission of PUSCH in advance, the network device may send a response message for PUSCH to the terminal device after all repeated transmissions of PUSCH are completed.

Therefore, according to the method of the embodiment of the application, the repeated transmission of the PUSCH in the random access process can be selected to be stopped in advance or not in advance according to the type of the terminal, so that the purpose of saving electricity is achieved, uplink resources are saved, uplink interference is reduced, and meanwhile, the terminal can be prevented from missing the receiving of response information.

Two complete examples of applications are provided below to further illustrate the above-described effects of embodiments of the present application.

Application example one

In a four-step random access procedure, for a UE using Msg3 retransmission, the UE indicates to the network via Msg3 whether it has the capability to end the retransmission PUSCH (early PUSCH termination) in advance. The specific implementation process is shown in fig. 6.

A first aspect of the present application example is that the condition that the UE indicates to the network whether it is early PUSCH termination capable or not through PUSCH of Msg3 may include:

a. if the UE does not indicate to the network whether it is early PUSCH termination capable by Msg1 (e.g., by using separate RO resources or preambles, etc.), the UE indicates to the network whether it is early PUSCH termination capable by PUSCH of Msg 3.

b. Whether or not the UE indicates to the network via Msg1 whether or not it is early PUSCH termination capable, the UE indicates to the network via PUSCH of Msg3 whether or not it is early PUSCH termination capable.

A second aspect of the present application example is that a specific implementation manner of the UE indicating to the network whether it has early PUSCH termination capability through PUSCH of Msg3 may include:

mode 1: whether the UE is early PUSCH termination capable is indicated by the MAC CE.

For example, 1 bit (bit) in the payload of the third MAC CE is used to indicate whether the UE is early PUSCH termination capable, e.g., a bit set to 1 indicates that the UE is early PUSCH termination capable; setting this bit to 0 indicates that the UE is not early PUSCH termination capable.

As another example, the UE is indicated early PUSCH termination capable by the first MAC CE. The second MAC CE corresponds to one LCID and the payload size is 0. If the UE is early PUSCH termination capable, the UE transmits a first MAC CE in Msg 3; otherwise, the UE does not transmit the first MAC CE in Msg 3.

As another example, whether the UE is early PUSCH termination capable is indicated by the first MAC CE and the second MAC CE. The first MAC CE and the second MAC CE each correspond to one LCID, and their payload sizes are all 0. If the UE is early PUSCH termination capable, the UE transmits a first MAC CE in Msg 3; otherwise, the UE transmits a second MAC CE in Msg 3.

Mode 2: whether the UE is early PUSCH termination capable is indicated by RRC signaling.

For example, the bit field reserved in RRC signaling corresponding to Msg3 is used for indication.

Mode 3: the CCCH1 is introduced, and the CCCH1 corresponds to a new LCID (different from the LCID corresponding to the original CCCH), and is used for half-duplex UE to send RRC message of Msg 3. The original CCCH is used for full duplex UEs to send RRC messages for Msg 3.

A third aspect of the present application example is that the UE may decide a point in time to start ra-contentioresolutiontimer according to whether it has early PUSCH termination capability or not.

a. If the UE sends early PUSCH termination capable indication information to the network, the UE starts ra-ContentionResolTimer after the first retransmission of Msg3 is completed.

b. If the UE does not send early PUSCH termination capable indication information to the network (including both cases where the UE is not early PUSCH termination capable and where the UE is early PUSCH termination capable but does not send early PUSCH termination capable indication information), the UE starts ra-contentioresolute after the last retransmission of Msg3 is completed.

A fourth aspect of the present application example is that the network side schedules Msg4 for the UE:

a. as shown in fig. 6, if the network receives early PUSCH termination-capable indication information from the UE and the network successfully receives Msg3 only by partial Msg3 retransmission, the network may choose to send an Msg4 response to the UE before all Msg3 retransmissions are received.

b. If the network side does not receive the early PUSCH termination capable indication information from the UE, the network can only send an Msg4 response to the UE after receiving all Msg3 retransmissions.

Application example two

In the two-step random access procedure, a UE that repeatedly transmits is used for PUSCH of MsgA, and indicates to the network whether it is early PUSCH termination-capable or not through PUSCH of MsgA. The specific implementation process is shown in fig. 7.

A first aspect of the present application example is that the condition that the UE indicates to the network whether it is early PUSCH termination capable through PUSCH of MsgA may include:

a. if the UE does not indicate to the network whether it is early PUSCH termination capable by way of RO resources or preambles of the MsgA, etc., the UE indicates to the network whether it is early PUSCH termination capable by way of PUSCH of the MsgA.

b. Whether the UE indicates to the network whether it is early PUSCH termination capable or not through RO resources or preambles of the MsgA or the like, the UE indicates to the network whether it is early PUSCH termination capable or not through PUSCH of the MsgA.

A second aspect of the present application example is that a specific manner in which the UE indicates to the network whether it is early PUSCH termination capable through PUSCH of MsgA may include:

For example, using 1bit in the payload of the third MAC CE to indicate whether the UE is early PUSCH termination capable, setting to 1 as this bit indicates that the UE is early PUSCH termination capable; setting this bit to 0 indicates that the UE is not early PUSCH termination capable.

As another example, the UE is indicated early PUSCH termination capable by the first MAC CE. The first MAC CE corresponds to one LCID and the payload size is 0. If the UE is early PUSCH termination capable, the UE transmits a first MAC CE in the MsgA; otherwise, the UE does not transmit the first MAC CE in MsgA.

As another example, whether the UE is early PUSCH termination capable is indicated by the first MAC CE and the second MAC CE. The first MAC CE and the second MAC CE each correspond to one LCID, and their payload sizes are all 0. If the UE is early PUSCH termination capable, the UE transmits a first MAC CE in the MsgA; otherwise, the UE transmits a second MAC CE in MsgA.

For example, the bit field reserved in the RRC signaling corresponding to the MsgA message is used for indicating.

Method 3: the CCCH1 is introduced, and the CCCH1 corresponds to a new LCID (different from the LCID corresponding to the original CCCH), and is used for the half-duplex UE to send the RRC message of MsgA. The original CCCH is used for full duplex UEs to send RRC messages for MsgA.

A third aspect of the present application example is that the UE decides the point in time to start the msgB-response window according to whether it has early PUSCH termination capability or not.

a. If the UE sends early PUSCH termination-capable indication information to the network, the UE starts the msgB-ResponseWindow after the completion of the first retransmission of the MsgA's PUSCH.

b. If the UE does not send early PUSCH termination capable indication information to the network (including both cases where the UE is not early PUSCH termination capable and where the UE is early PUSCH termination capable but does not send early PUSCH termination capable indication information), the UE starts the msgB-response window after the last repeated transmission of PUSCH for MsgA is completed.

A fourth aspect of the present application example is that the network side schedules the MsgB policy for the UE:

a. As shown in fig. 7, if the network receives the indication information with early PUSCH termination capability from the UE and the network successfully receives the MsgA only through PUSCH retransmission of a portion of the MsgA, the network may choose to send an MsgB response to the UE before PUSCH retransmission of all MsgA is received.

b. If the network side does not receive the early PUSCH termination-capable indication information from the UE, the network can only send the MsgB response to the UE after receiving PUSCH repeated transmissions of all MsgA.

The specific arrangements and implementations of the embodiments of the present application have been described above from a variety of angles by way of various embodiments. By utilizing the at least one embodiment, in the random access process, the terminal equipment indicates whether the terminal equipment has the capability of finishing the repeated transmission of the PUSCH in advance through the PUSCH, so that the network equipment can respond to the PUSCH as early as possible according to the relevant capability of different terminals, thereby being beneficial to realizing the repeated transmission of the PUSCH in advance and saving uplink resources.

Corresponding to the processing method of at least one embodiment described above, the embodiment of the present application further provides a terminal device 100, referring to fig. 8, which includes:

the first communication module 110 is configured to send, to the network device, information indicating whether the terminal device has a capability of ending the repeated PUSCH transmission in advance, based on the physical uplink shared channel PUSCH.

Optionally, the PUSCH includes:

PUSCH in message Msg3 of the four-step random access procedure, and/or,

PUSCH in message MsgA of two-step random access procedure.

Optionally, as shown in fig. 9, the first communication module 110 includes:

a MAC CE transmitting unit 111 configured to transmit a MAC CE to a network device, where the MAC CE includes information for indicating whether the terminal device has a capability of ending the repeated transmission of PUSCH in advance.

Alternatively, in the case where the terminal apparatus 100 has the capability of ending the repeated transmission PUSCH in advance, the MAC CE includes a first MAC CE corresponding to the first LCID.

Optionally, the first MAC CE does not include a payload.

Alternatively, in the case where the terminal apparatus 100 does not have the capability of ending the repeated transmission PUSCH in advance, the MAC CE does not include the first MAC CE corresponding to the first LCID.

Alternatively, in the case where the terminal device 100 does not have the capability of ending the repeated transmission PUSCH in advance, the MAC CE includes a second MAC CE corresponding to the second LCID.

Optionally, the second MAC CE does not include a payload.

Optionally, the PUSCH includes a third MAC CE, and a bit field in a payload of the third MAC CE is used to indicate whether the terminal device 100 has a capability to end the repeated PUSCH transmission in advance.

Alternatively, as shown in fig. 9, the first communication module 110 includes:

an RRC signaling sending unit 112, configured to send RRC signaling to the network device, where the RRC signaling includes information indicating whether the terminal device has a capability to end the repeated PUSCH transmission in advance.

Optionally, the RRC signaling includes an information field for indicating whether the terminal device has the capability to end the repeated PUSCH transmission in advance.

Optionally, the CCCH corresponding to the RRC signaling is used to indicate whether the terminal device has the capability of ending the repeated PUSCH transmission in advance.

Alternatively, in case the terminal device 100 has the capability to end the repeated transmission of PUSCH in advance, the RRC signaling corresponds to the first CCCH.

Alternatively, in the case where the terminal device 100 does not have the capability to end the repeated transmission of PUSCH in advance, the RRC signaling corresponds to the second CCCH.

Optionally, as shown in fig. 9, the terminal device 100 further includes:

a first starting module 120, configured to start a random access contention resolution timer after completing the first repeated transmission of the PUSCH if information indicating that the terminal device has the capability of ending the repeated transmission of the PUSCH has been transmitted.

Optionally, the terminal device 100 further includes:

the second starting module 130 is configured to start the random access contention resolution timer after the last repeated transmission of the PUSCH is completed if no information indicating that the terminal device has the capability of ending the repeated transmission of the PUSCH is transmitted.

Optionally, the first communication module 110 is specifically configured to:

in the case that the first message in the random access process does not indicate whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance, transmitting information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance to the network equipment based on the PUSCH; wherein the first message is used for transmitting a preamble in a random access procedure.

Optionally, the first message comprises a message Msg1 in a four-step random access procedure.

Optionally, the first communication module 110 is specifically configured to:

in the case that the terminal device 100 does not have the capability of ending the repeated transmission PUSCH in advance based on the random access opportunity RO resource or the preamble of the second message in the random access procedure, the terminal device 100 has the capability of ending the repeated transmission PUSCH in advance based on the PUSCH; wherein the second message is used for transmitting PUSCH and preamble.

Optionally, the second message comprises a message MsgA in a two-step random access procedure.

Optionally, the terminal device 100 further includes:

a first determining module 140, configured to determine, based on the received first indication information from the network device, whether to send, based on the PUSCH, information for indicating whether the terminal device has a capability to end the repeated PUSCH in advance.

The terminal device 100 in this embodiment of the present application may implement the corresponding functions of the terminal device in the foregoing method embodiment, and the flow, the functions, the implementation manner and the beneficial effects corresponding to each module (sub-module, unit or component, etc.) in the terminal device 100 may refer to the corresponding descriptions in the foregoing method embodiment, which are not repeated herein. It should be noted that, regarding the functions described in each module (sub-module, unit, or component, etc.) in the terminal device 100 of the embodiment of the present application, the functions may be implemented by different modules (sub-module, unit, or component, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.), for example, the MAC CE sending unit and the RRC signaling sending unit may be different units, or may be the same unit, and all the functions thereof in the embodiment of the present application may be implemented by the same unit. In addition, the communication module in the embodiment of the application may be implemented by a transceiver of the device, and part or all of the remaining modules may be implemented by a processor of the device.

Fig. 10 is a schematic block diagram of a network device 200 according to an embodiment of the present application. The network device 200 may include:

The second communication module 210 is configured to receive information sent by the terminal device based on the PUSCH and used for indicating whether the terminal device has a capability of ending the repeated PUSCH transmission in advance.

Optionally, the second communication module 210 is further configured to:

if the terminal device has the capability of ending the repeated transmission of the PUSCH in advance and the reception of the PUSCH is completed based on the partial repeated transmission of the PUSCH, a response message for the PUSCH can be sent to the terminal device before the complete repeated transmission of the PUSCH is completed.

Optionally, the second communication module 210 is further configured to:

if the terminal device does not have the capability of ending the repeated transmission of the PUSCH in advance, a response message for the PUSCH is sent to the terminal device after all the repeated transmission of the PUSCH is completed.

Optionally, as shown in fig. 11, the second communication module 210 includes:

a MAC CE receiving unit 211, configured to receive a MAC CE, where the MAC CE includes information for indicating whether the terminal device has a capability of ending the repeated PUSCH in advance.

Optionally, as shown in fig. 11, the network device 200 further includes:

the second determining module 220 is configured to determine that the terminal device has a capability of ending the repeated PUSCH in advance, in a case where the MAC CE includes a first MAC CE corresponding to the first LCID.

Optionally, the second determining module 220 is configured to:

in the case that the MAC CE does not include the first MAC CE corresponding to the first LCID, it is determined that the terminal device does not have a capability to end the repeated transmission PUSCH in advance.

Optionally, the second determining module 220 is configured to:

in the case that the MAC CE includes a second MAC CE corresponding to the second LCID, it is determined that the terminal device does not have a capability to end the repeated transmission PUSCH in advance.

Optionally, the PUSCH includes a third MAC CE, and the second determining module 220 is configured to:

based on the bit field in the payload of the third MAC CE, it is determined whether the terminal device has the capability to end the repeated transmission PUSCH in advance.

Optionally, the second communication module 210 includes:

the RRC signaling receiving unit 212 is configured to receive RRC signaling, where the RRC signaling includes information indicating whether the terminal device has a capability of repeatedly transmitting PUSCH in advance.

Optionally, the second determining module 220 is configured to:

based on the information field in the RRC signaling, it is determined whether the terminal device has the capability to end the repeated transmission of PUSCH in advance.

Optionally, the second determining module 220 is configured to:

and determining whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance based on the CCCH corresponding to the RRC signaling.

Optionally, the second determining module 220 is configured to:

in case the RRC signaling corresponds to the first CCCH, it is determined that the terminal device has the capability to end the repeated transmission of PUSCH in advance.

Optionally, the second determining module 220 is configured to:

in case the RRC signaling corresponds to the second CCCH, it is determined that the terminal device does not have the capability to end the repeated transmission of PUSCH in advance.

Optionally, the second communication module 210 is further configured to:

sending first indication information to terminal equipment;

The network device 200 of the embodiment of the present application can implement the corresponding functions of the network device in the foregoing method embodiment. The flow, function, implementation and beneficial effects corresponding to each module (sub-module, unit or assembly, etc.) in the network device 200 can be referred to the corresponding description in the above method embodiments, which are not repeated here. It should be noted that, regarding the functions described in each module (sub-module, unit, or component, etc.) in the network device 200 of the application embodiment, the functions may be implemented by different modules (sub-module, unit, or component, etc.), or may be implemented by the same module (sub-module, unit, or component, etc.), for example, the first sending module and the second sending module may be different modules, or may be the same module, and all the functions thereof in the embodiments of the application may be implemented. In addition, the communication module in the embodiment of the application may be implemented by a transceiver of the device, and part or all of the remaining modules may be implemented by a processor of the device.

Fig. 12 is a schematic block diagram of a communication device 600 according to an embodiment of the present application, wherein the communication device 600 includes a processor 610, and the processor 610 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, the communication device 600 may further comprise a memory 620. Wherein the processor 610 may call and run a computer program from the memory 620 to implement the methods in embodiments of the present application.

The memory 620 may be a separate device from the processor 610 or may be integrated into the processor 610.

Optionally, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, and in particular, may send information or data to other devices, or receive information or data sent by other devices.

The transceiver 630 may include a transmitter and a receiver, among others. Transceiver 630 may further include antennas, the number of which may be one or more.

Optionally, the communication device 600 may be a network device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the communication device 600 may be a terminal device in the embodiment of the present application, and the communication device 600 may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

Fig. 13 is a schematic block diagram of a chip 700 according to an embodiment of the present application, wherein the chip 700 includes a processor 710, and the processor 710 may call and run a computer program from a memory to implement the method in the embodiment of the present application.

Optionally, chip 700 may also include memory 720. Wherein the processor 710 may call and run a computer program from the memory 720 to implement the methods in embodiments of the present application.

Wherein the memory 720 may be a separate device from the processor 710 or may be integrated into the processor 710.

Optionally, the chip 700 may also include an input interface 730. The processor 710 may control the input interface 730 to communicate with other devices or chips, and in particular, may obtain information or data sent by other devices or chips.

Optionally, the chip 700 may further include an output interface 740. The processor 710 may control the output interface 740 to communicate with other devices or chips, and in particular, may output information or data to other devices or chips.

Optionally, the chip may be applied to a network device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the network device in each method in the embodiment of the present application, which is not described herein for brevity.

Optionally, the chip may be applied to a terminal device in the embodiment of the present application, and the chip may implement a corresponding flow implemented by the terminal device in each method in the embodiment of the present application, which is not described herein for brevity.

It should be understood that the chips referred to in the embodiments of the present application may also be referred to as system-on-chip chips, or the like.

The processors mentioned above may be general purpose processors, digital signal processors (digital signal processor, DSP), off-the-shelf programmable gate arrays (field programmable gate array, FPGA), application specific integrated circuits (application specific integrated circuit, ASIC) or other programmable logic devices, transistor logic devices, discrete hardware components, etc. The general-purpose processor mentioned above may be a microprocessor or any conventional processor.

The memory mentioned above may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM).

It should be understood that the above memory is exemplary but not limiting, and for example, the memory in the embodiments of the present application may be Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), direct RAM (DR RAM), and the like. That is, the memory in embodiments of the present application is intended to comprise, without being limited to, these and any other suitable types of memory.

Fig. 14 is a schematic block diagram of a communication system 800 according to an embodiment of the present application, the communication system 800 comprising a terminal device 810 and a network device 820.

Wherein the terminal device 810 may be used to implement the corresponding functions implemented by the terminal device in the methods of the various embodiments of the present application, and the network device 820 may be used to implement the corresponding functions implemented by the network device in the methods of the various embodiments of the present application. For brevity, the description is omitted here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working processes of the above-described systems, apparatuses and units may refer to corresponding processes in the foregoing method embodiments, which are not described herein again.

The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes or substitutions are covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

An information indication method, comprising:

the terminal device sends information for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance to the network device based on the physical uplink shared channel PUSCH.
The method of claim 1, wherein the PUSCH comprises:

PUSCH in message Msg3 of four step random access procedure; and/or the number of the groups of groups,

PUSCH in message MsgA of two-step random access procedure.
The method according to claim 1 or 2, wherein the terminal device transmitting information indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance to the network device based on the physical uplink shared channel PUSCH, comprises:

the terminal device sends a media access control layer control unit (MAC CE) to the network device, wherein the MAC CE comprises information for indicating whether the terminal device has the capability of finishing repeated transmission of the PUSCH in advance.
The method of claim 3, wherein the MAC CE comprises a first MAC CE corresponding to a first logical channel identification LCID in case the terminal device has a capability to end a repeated transmission PUSCH in advance.
The method of claim 4, wherein the first MAC CE does not include a payload.
The method according to any of claims 3-5, wherein the MAC CE does not include a first MAC CE corresponding to a first LCID in case the terminal device does not have the capability to end the repeated transmission PUSCH in advance.
The method according to any of claims 3-5, wherein the MAC CE comprises a second MAC CE corresponding to a second LCID, in case the terminal device does not have the capability to end the repeated transmission PUSCH in advance.
The method of claim 7, wherein the second MAC CE does not include a payload.
The method of claim 3, wherein the MAC CE comprises a third MAC CE, a bit field in a payload of the third MAC CE to indicate whether the terminal device has a capability to end a retransmission PUSCH in advance.
The method according to claim 1 or 2, wherein the terminal device transmitting information indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance to the network device based on the physical uplink shared channel PUSCH, comprises:

the terminal device sends radio resource control, RRC, signaling to the network device, wherein the RRC signaling includes information indicating whether the terminal device has the capability to end repeat transmission, PUSCH, in advance.
The method of claim 10, wherein the RRC signaling includes an information field indicating whether the terminal device has a capability to end a repeated transmission of PUSCH in advance.
The method of claim 10, wherein a common control channel CCCH corresponding to the RRC signaling is used to indicate whether the terminal device has a capability to end a repeated PUSCH in advance.
The method of claim 12, wherein the RRC signaling corresponds to a first CCCH if the terminal device has a capability to end a repeated transmission of PUSCH in advance.
The method according to claim 12 or 13, wherein the RRC signaling corresponds to a second CCCH in case the terminal device does not have the capability to end the repeated transmission of PUSCH in advance.
The method of any one of claims 1-14, wherein the method further comprises:

if information indicating that the terminal device has the capability of ending the repeated transmission of the PUSCH in advance has been transmitted, the terminal device starts a random access contention resolution timer after completing the first repeated transmission of the PUSCH.
The method of any one of claims 1-15, wherein the method further comprises:

if no information indicating that the terminal device has the capability of ending the repeated transmission of PUSCH in advance is transmitted, the terminal device starts a random access contention resolution timer after the last repeated transmission of PUSCH is completed.
The method according to any one of claims 1-16, wherein the terminal device sending, to a network device, information indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance based on a physical uplink shared channel, comprises:

in the case that the first message in the random access process does not indicate whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance, the terminal equipment sends information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance to the network equipment based on the PUSCH; wherein the first message is used for transmitting a preamble in the random access procedure.
The method of claim 17, wherein the first message comprises a message Msg1 in a four-step random access procedure.
The method according to any one of claims 1-16, wherein the terminal device sending, to a network device, information indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance based on a physical uplink shared channel, comprises:

in the case that the random access opportunity RO resource or the preamble based on the second message in the random access procedure does not indicate whether the terminal device has the capability of ending the repeated transmission PUSCH in advance, the terminal device sends information for indicating whether the terminal device has the capability of ending the repeated transmission PUSCH in advance to the network device based on the PUSCH; wherein the second message is used for transmitting the PUSCH and the preamble.
The method of claim 19, wherein the second message comprises a message MsgA in a two-step random access procedure.
The method of any one of claims 1-20, wherein the method further comprises:

the terminal device determines, based on the received first indication information from the network device, information for indicating whether the terminal device has a capability of ending repeated transmission of PUSCH in advance based on the PUSCH transmission.
The method of claim 21, wherein the first indication information informs the terminal device in a broadcast manner, a multicast manner, or a unicast manner.
An information indication method, comprising:

the network device receives information sent by the terminal device based on the PUSCH and used for indicating whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance.
The method of claim 23, wherein the method further comprises:

if the terminal device has the capability of ending the repeated transmission of the PUSCH in advance and the network device completes the reception of the PUSCH based on the partial repeated transmission of the PUSCH, the network device can send a response message for the PUSCH to the terminal device before all the repeated transmission of the PUSCH is completed.
The method of claim 23 or 24, wherein the method further comprises:

and if the terminal equipment does not have the capability of ending the repeated transmission of the PUSCH in advance, the network equipment sends a response message for the PUSCH to the terminal equipment after all the repeated transmission of the PUSCH is completed.
The method according to any of claims 23-25, wherein the network device receiving, by the terminal device, information sent based on the PUSCH for indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance, comprises:

the network device receives a MAC CE including information for indicating whether the terminal device has a capability to end a repeated transmission PUSCH in advance.
The method of claim 26, wherein the method further comprises:

in the case that the MAC CE includes a first MAC CE corresponding to a first LCID, the network device determines that the terminal device has a capability to end a repeated transmission PUSCH in advance.
The method of claim 26 or 27, wherein the method further comprises:

in the case that the MAC CE does not include the first MAC CE corresponding to the first LCID, the network device determines that the terminal device does not have a capability to end the repeated transmission PUSCH in advance.
The method of claim 26 or 27, wherein the method further comprises:

in the case that the MAC CE includes a second MAC CE corresponding to a second LCID, the network device determines that the terminal device does not have a capability to end the repeated transmission PUSCH in advance.
The method of claim 26, wherein the MAC CE comprises a third MAC CE, the method further comprising:

the network device determines, based on a bit field in a payload of the third MAC CE, whether the terminal device has a capability to end the repeated transmission PUSCH in advance.
The method according to any of claims 23-25, wherein the network device receiving, by the terminal device, information sent based on the PUSCH for indicating whether the terminal device has a capability to end the repeated transmission of PUSCH in advance, comprises:

the network device receives RRC signaling including information indicating whether the terminal device has the capability to end repeatedly transmitting PUSCH in advance.
The method of claim 31, wherein the method further comprises:

the network device determines whether the terminal device has the capability of ending the repeated transmission of the PUSCH in advance based on the information field in the RRC signaling.
The method of claim 31, wherein the method further comprises:

and the network equipment determines whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance based on the CCCH corresponding to the RRC signaling.
The method of claim 33, wherein the method further comprises:

in case the RRC signaling corresponds to the first CCCH, the network device determines that the terminal device has a capability to end the repeated transmission of PUSCH in advance.
The method of claim 33 or 34, wherein the method further comprises:

in case the RRC signaling corresponds to the second CCCH, the network device determines that the terminal device does not have the capability to end the repeated transmission of PUSCH in advance.
The method of any of claims 23-35, wherein the method further comprises:

the network equipment sends first indication information to the terminal equipment;

the first indication information is used for indicating the terminal equipment to send information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance or not based on the PUSCH.
The method of claim 36, wherein the first indication information informs the terminal device in a broadcast manner, a multicast manner, or a unicast manner.
A terminal device, comprising:

and the first communication module is used for sending information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance or not to the network equipment based on the Physical Uplink Shared Channel (PUSCH).
The terminal device of claim 38, wherein the PUSCH comprises:

PUSCH in message Msg3 of the four-step random access procedure, and/or,

PUSCH in message MsgA of two-step random access procedure.
The terminal device of claim 38 or 39, wherein the first communication module comprises:

and the MAC CE sending unit is used for sending the MAC CE to the network equipment, wherein the MAC CE comprises information for indicating whether the terminal equipment has the capability of finishing the repeated transmission of the PUSCH in advance.
The terminal device of claim 40, wherein the MAC CE comprises a first MAC CE corresponding to a first logical channel identification LCID in case the terminal device has a capability to end repeated transmission of PUSCH in advance.
The terminal device of claim 41, wherein the first MAC CE does not include a payload.
The terminal device of any of claims 40-42, wherein the MAC CE does not include a first MAC CE corresponding to a first LCID in the event that the terminal device does not have the capability to end repeat transmissions of PUSCH in advance.
The terminal device of any of claims 40-42, wherein the MAC CE includes a second MAC CE corresponding to a second LCID in case the terminal device does not have the capability to end repeat transmissions of PUSCH in advance.
The terminal device of claim 44, wherein the second MAC CE does not include a payload.
The terminal device of claim 40, wherein the MAC CE comprises a third MAC CE, a bit field in a payload of the third MAC CE being used to indicate whether the terminal device has a capability to end repeat transmission PUSCH in advance.
The terminal device of claim 38 or 39, wherein the first communication module comprises:

and an RRC signaling transmitting unit configured to transmit radio resource control RRC signaling to the network device, where the RRC signaling includes information for indicating whether the terminal device has a capability of ending the repeated PUSCH in advance.
The terminal device of claim 47, wherein the RRC signaling includes an information field to indicate whether the terminal device has a capability to end repeat transmission of PUSCH in advance.
The terminal device of claim 47, wherein a common control channel CCCH corresponding to the RRC signaling is used to indicate whether the terminal device has a capability to end repeat a PUSCH in advance.
The terminal device of claim 49, wherein the RRC signaling corresponds to a first CCCH in case the terminal device has a capability to end repeated PUSCH transmissions in advance.
The terminal device of claim 49 or 50, wherein the RRC signaling corresponds to a second CCCH in case the terminal device does not have the capability to end the repeated PUSCH in advance.
The terminal device of any of claims 38-41, wherein the terminal device further comprises:

a first starting module, configured to start a random access contention resolution timer after completing a first repeated transmission of a PUSCH if information indicating that the terminal device has a capability of ending the repeated transmission of the PUSCH in advance has been sent.
The terminal device of any of claims 38-52, wherein the terminal device further comprises:

and a second starting module, configured to start a random access contention resolution timer after finishing the last repeated transmission of the PUSCH if no information indicating that the terminal device has the capability of ending the repeated transmission of the PUSCH is transmitted.
The terminal device of any of claims 38-53, wherein the first communication module is specifically configured to:

In the case that the first message in the random access process does not indicate whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance, transmitting information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance to the network equipment based on the PUSCH; wherein the first message is used for transmitting a preamble in the random access procedure.
The terminal device of claim 54, wherein the first message comprises message Msg1 in a four-step random access procedure.
The terminal device of any of claims 38-53, wherein the first communication module is specifically configured to:

transmitting information for indicating whether the terminal device has the capability of ending the repeated transmission of PUSCH in advance to the network device based on the PUSCH, in case that the terminal device does not have the capability of ending the repeated transmission of PUSCH in advance based on a random access opportunity RO resource or a preamble of the second message in the random access procedure; wherein the second message is used for transmitting the PUSCH and the preamble.
A terminal device according to claim 56 wherein the second message comprises a message MsgA in a two-step random access procedure.
The terminal device of any of claims 38-57, wherein the terminal device further comprises:

a first determining module, configured to determine, based on the received first indication information from the network device, information for indicating whether the terminal device has a capability of ending repeated PUSCH in advance based on the PUSCH transmission.
The terminal device of claim 58, wherein the first indication information informs the terminal device by broadcast, multicast or unicast.
A network device, comprising:

and the second communication module is used for receiving information which is sent by the terminal equipment based on the PUSCH and is used for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance.
The network device of claim 60, wherein the second communication module is further configured to:

if the terminal device has the capability of ending the repeated transmission of the PUSCH in advance and completes the reception of the PUSCH based on the partial repeated transmission of the PUSCH, a response message for the PUSCH can be sent to the terminal device before all the repeated transmission of the PUSCH is completed.
The network device of claim 60 or 61, wherein the second communication module is further configured to:

And if the terminal equipment does not have the capability of ending the repeated transmission of the PUSCH in advance, after all the repeated transmission of the PUSCH is completed, sending a response message for the PUSCH to the terminal equipment.
The network device of any of claims 60-62, wherein the second communication module comprises:

a MAC CE receiving unit, configured to receive a MAC CE, where the MAC CE includes information for indicating whether the terminal device has a capability of ending the repeated PUSCH in advance.
The network device of claim 63, wherein the network device further comprises:

and the second determining module is used for determining that the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance when the MAC CE comprises the first MAC CE corresponding to the first LCID.
The network device of claim 63 or 64, wherein a second determination module in the network device is configured to:

and if the MAC CE does not comprise the first MAC CE corresponding to the first LCID, determining that the terminal equipment does not have the capability of ending the repeated transmission of the PUSCH in advance.
The network device of claim 63 or 64, wherein a second determination module in the network device is configured to:

And if the MAC CE comprises a second MAC CE corresponding to the second LCID, determining that the terminal equipment does not have the capability of ending the repeated transmission of the PUSCH in advance.
The network device of claim 63, wherein the MAC CE comprises a third MAC CE, and the second determining module in the network device is configured to:

based on the bit field in the payload of the third MAC CE, it is determined whether the terminal device has a capability to end the repeated transmission PUSCH in advance.
The network device of any of claims 60-62, wherein the second communication module comprises:

and the RRC signaling receiving unit is used for receiving RRC signaling, and the RRC signaling comprises information for indicating whether the terminal equipment has the capability of finishing the repeated transmission of the PUSCH in advance.
The network device of claim 68, wherein the second determination module in the network device is configured to:

based on the information field in the RRC signaling, it is determined whether the terminal device has a capability to end the repeated PUSCH transmission in advance.
The network device of claim 68, wherein the second determination module in the network device is configured to:

and determining whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance or not based on the CCCH corresponding to the RRC signaling.
The network device of claim 70, wherein the second determining module is specifically configured to:

and in the case that the RRC signaling corresponds to the first CCCH, determining that the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance.
The network device of claim 70 or 71, wherein the second determining unit is specifically configured to:

and in case that the RRC signaling corresponds to the second CCCH, determining that the terminal equipment does not have the capability of ending the repeated transmission of the PUSCH in advance.
The network device of any one of claims 60-72, wherein the second communication module is further configured to send first indication information to the terminal device;

the first indication information is used for indicating the terminal equipment to send information for indicating whether the terminal equipment has the capability of ending the repeated transmission of the PUSCH in advance or not based on the PUSCH.
The network device of claim 73, wherein the first indication information informs the terminal device by broadcast, multicast, or unicast.
A terminal device, comprising: a processor and a memory for storing a computer program, the processor invoking and running the computer program stored in the memory, performing the steps of the method of any of claims 1 to 22.
A network device, comprising: a processor and a memory for storing a computer program, the processor invoking and running the computer program stored in the memory to perform the steps of the method of any of claims 23 to 37.
A chip, comprising:

a processor for calling and running a computer program from a memory, causing a device on which the chip is mounted to perform the steps of the method according to any one of claims 1 to 37.
A computer readable storage medium storing a computer program, wherein,

the computer program causes a computer to perform the steps of the method of any one of claims 1 to 37.
A computer program product comprising computer program instructions, wherein,

the computer program instructions cause a computer to perform the steps of the method of any one of claims 1 to 37.
A computer program which causes a computer to perform the steps of the method of any one of claims 1 to 37.
A communication system, comprising:

terminal device for performing the method of any of claims 1 to 22;

Network device for performing the method of any of claims 23 to 37.