Uplink data transmission method and apparatus, device, and storage medium

Abstract

The present application relates to the technical field of communications, and discloses an uplink data transmission method and apparatus, a device, and a storage medium. The uplink data transmission method of the embodiments of the present application comprises: a terminal acquires first information, the first information being related configuration information of uplink data transmission in a non-connected state, and the first information comprising at least one of the following: repeat transmission-related information, retransmission-related information, and TA information; and the terminal performs uplink data transmission on the basis of the first information.

Description

Uplink data transmission method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application number 202311711513.9 filed on December 12, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to an uplink data transmission method, apparatus, device and storage medium. Background Art

[0004] In a communication system, a terminal's air interface exists in three states: Radio Resource Control (RRC) idle state, RRC inactive state, and RRC connected state. A terminal in the RRC idle or inactive state is referred to as a terminal in a non-connected state. A terminal can access the network through a random access procedure to enter the RRC connected state.

[0005] When a terminal is in the RRC connected state, it can transmit data to and from network devices. Data transmission in the connectionless state is a special transmission mechanism that allows the terminal to send and receive dedicated data to and from the network without entering a connection state. However, there is currently no solution for implementing uplink data transmission in the connectionless state, and therefore the reliability of uplink data transmission in the connectionless state cannot be guaranteed. Summary of the Invention

[0006] The embodiments of the present application provide an uplink data transmission method, apparatus, device, and storage medium, which can solve the problem of how to implement uplink data transmission in a non-connected state to ensure the reliability of uplink data transmission.

[0007] In a first aspect, a method for uplink data transmission is provided, the method comprising: a terminal obtaining first information, the first information being relevant configuration information for uplink data transmission in a non-connected state, the first information comprising at least one of the following: repeated transmission related information, retransmission related information, and timing advance (TA) information; the terminal performing uplink data transmission according to the first information.

[0008] In a second aspect, an uplink data transmission method is provided, which includes: a network side device sends first information to a terminal, where the first information is relevant configuration information for uplink data transmission in a non-connected state, and the first information is used to perform uplink data transmission; wherein the first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

[0009] According to a third aspect, an uplink data transmission apparatus is provided, comprising: an acquisition module and a transmission module. The acquisition module is configured to acquire first information, wherein the first information is configuration information related to uplink data transmission in a non-connected state, and the first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information. The transmission module is configured to perform uplink data transmission based on the first information acquired by the acquisition module.

[0010] In a fourth aspect, an uplink data transmission apparatus is provided, comprising: a sending module. The sending module is configured to send first information to a terminal, the first information being configuration information related to uplink data transmission in a non-connected state, the first information being used to perform uplink data transmission; wherein the first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

[0011] In a fifth aspect, a terminal is provided, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the first aspect are implemented.

[0012] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is configured to obtain first information, the first information being configuration information related to uplink data transmission in a non-connected state, the first information including at least one of the following: repeated transmission related information, retransmission related information, and TA information. The communication interface is configured to perform uplink data transmission based on the first information.

[0013] In the seventh aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect are implemented.

[0014] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the communication interface is used to send first information to the terminal, the first information being relevant configuration information for uplink data transmission in a non-connected state, and the first information being used to perform uplink data transmission; wherein the first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

[0015] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented.

[0016] In the tenth aspect, a wireless communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the method described in the first aspect, and the network side device can be used to execute the steps of the method described in the second aspect.

[0017] In the eleventh aspect, a chip is provided, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or to implement the method as described in the second aspect.

[0018] In the twelfth aspect, a computer program / program product is provided, which is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the uplink data transmission method as described in the first aspect, or to implement the steps of the uplink data transmission method as described in the second aspect.

[0019] In an embodiment of the present application, a terminal may obtain relevant configuration information for uplink data transmission in a non-connected state, including at least one of the following: repeated transmission related information, retransmission related information, and TA information, and perform uplink data transmission according to the relevant configuration information. In this solution, for uplink data transmission of a terminal in a non-connected state, the terminal may perform repeated transmission of uplink data transmission in a non-connected state according to repeated transmission related information, or perform retransmission of uplink data transmission in a non-connected state according to retransmission related information, or perform uplink data transmission in a non-connected state according to TA information, thereby enabling the terminal to perform initial transmission, repeated transmission, or retransmission of data with the network side without entering a connected state, thereby improving the reliability of uplink data transmission in a non-connected state. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] FIG1 is a schematic diagram of the architecture of a wireless communication system provided in an embodiment of the present application;

[0021] FIG2 is a flowchart of an uplink data transmission method according to an embodiment of the present application;

[0022] FIG3 is a second flowchart of an uplink data transmission method provided in an embodiment of the present application;

[0023] FIG4 is a third flowchart of an uplink data transmission method provided in an embodiment of the present application;

[0024] FIG5 is a fourth flowchart of an uplink data transmission method provided in an embodiment of the present application;

[0025] FIG6 is a fifth flowchart of an uplink data transmission method provided in an embodiment of the present application;

[0026] FIG7 is a sixth flowchart of an uplink data transmission method provided in an embodiment of the present application;

[0027] FIG8 is a schematic diagram of a structure of an uplink data transmission device according to an embodiment of the present application;

[0028] FIG9 is a second structural diagram of an uplink data transmission device provided in an embodiment of the present application;

[0029] FIG10 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application;

[0030] FIG11 is a schematic diagram of the hardware structure of a terminal provided in an embodiment of the present application;

[0031] FIG12 is a schematic diagram of the hardware structure of a network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0033] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects, for example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0034] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0035] The terms "at least one" and "at least one of" in this application refer to any one, any two, or a combination of more than two of the objects included. For example, at least one of a, b, and c can be represented by: "a", "b", "c", "a and b", "a and c", "b and c", and "a, b, and c", where a, b, and c can be single or multiple. Similarly, "at least two" means two or more, and its meaning is similar to "at least one".

[0036] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0037] FIG1 is a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0038] The following explains some concepts and / or terms involved in an uplink data transmission method, apparatus, device, and storage medium provided in an embodiment of the present application.

[0039] 1. Paging

[0040] In NR, paging can be divided into the following types according to the source of the message:

[0041] Core network paging, which comes from the core network. In the RRC_IDLE state, when downlink data arrives for the RRC_IDLE state terminal, the core network notifies the terminal through a paging message;

[0042] RAN paging, which comes from the base station. When downlink data arrives for a terminal in the RRC_INACTIVE state, the base station notifies the terminal through a paging message.

[0043] The final paging message is sent by the base station to the terminal through the air interface.

[0044] The paging message is carried by the Paging Control Channel (PCCH), and the data block of the PCCH is carried by the Paging Channel (PCH), and the data block of the PCH is carried by the Physical Downlink Shared Channel (PDSCH). Since PDSCH is a downlink shared physical channel, it can carry not only PCH but also Downlink Shared Channel (DL-SCH). Therefore, before receiving a paging message (on PDSCH), the terminal needs to first monitor the Physical Downlink Control Channel (PDCCH), and then determine whether the network has sent a paging message to itself in this paging cycle based on whether the PDCCH carries the Paging Radio Network Temporary Identifier (P-RNTI).

[0045] In addition to sending a paging message, the downlink control information (DCI) for scheduling paging may also carry a short message and indicate whether there are available Tracking Reference Signal (TRS) resources.

[0046] A paging message carries a paging record list (PagingRecordList), which contains at least one and at most maxNrofPageRec paging records. Each paging record carries a paging identifier of the paged terminal. That is, a paging message can indicate that at most maxNrofPageRec terminals are paged.

[0047] There are two types of identification for the paged terminal: one for paging terminals in the idle state and the other for paging terminals in the inactive state. The terminal receiving the paging message is in the idle state or the inactive state.

[0048] 2. Paging Occasion (PO) and Paging Frame (PF)

[0049] A PF is a radio frame that may contain one or more POs. A PO is a subframe that may contain a paging message.

[0050] If the terminal knows the paging cycle, PF, and PO, it can know the exact time to receive the paging message. In order to reduce the power consumption of the terminal in the RRC_IDLE or RRC_INACTIVE state, the terminal uses discontinuous reception (DRX) to receive paging messages. There are several PFs in a DRX cycle, and one PF corresponds to several POs. The terminal only wakes up once in a DRX cycle to monitor one PO. The terminal monitors one PO in each DRX cycle. PO is a set of PDCCH monitoring opportunities and can include multiple time slots (such as subframes or symbols) in which paging DCI can be sent.

[0051] 3. Random access process

[0052] In the prior art, the random access procedure may be a contention-based random access procedure or a non-contention-based random access procedure. The random access procedure may be a four-step random access procedure (also called a Type-1 random access procedure) or a two-step random access procedure (also called a Type-2 random access procedure).

[0053] During the contention-based 4-step random access process, the terminal first sends Msg1, which contains a preamble, to the network. After the network detects the preamble, it sends Msg2 or a Random Access Reception (RAR) message, which contains the preamble number detected by the network and the uplink radio resources allocated to the terminal for sending Msg3. After receiving Msg2, the terminal confirms that at least one of the preamble numbers carried in Msg2 matches the number of the preamble it sent. Then, based on the resources indicated by the RAR, it sends Msg3 containing contention resolution information. After receiving Msg3, the network sends Msg4 containing contention resolution information. Upon receiving Msg4, the terminal confirms that the resolution information matches the one it sent in Msg3, completing the 4-step random access process.

[0054] The network includes uplink grant (UL grant) information in the RAR to indicate the scheduling information of the Msg3 Physical Uplink Shared Channel (PUSCH), and includes information such as the Random Access Channel Preamble ID (RAPID), the Temporary Cell-Radio Network Temporary Identifier (TC-RNTI), and the TA. If the network does not receive the Msg3PUSCH, it can schedule the retransmission of the Msg3PUSCH in the PDCCH scrambled by the TC-RNTI.

[0055] For the contention-based random access process, different terminals randomly select preambles for transmission. In this way, different terminals may select the same preamble to send on the same time-frequency radio resources (Random Access Channel Occasion (RO) resources). This situation can be understood as a preamble conflict of the terminal. In this case, different terminals will receive the same RAR. At this time, different terminals will transmit Msg3PUSCH according to the scheduling information in the RAR UL grant. Since the existing technology does not support repeated transmission of Msg3PUSCH, the network can only decode the PUSCH (including contention resolution information) sent by one terminal on one Msg3PUSCH scheduling resource. Therefore, the network will include the contention resolution information received in Msg3 in Msg4. If the contention resolution information in Msg4 received by the terminal matches the contention resolution information sent by the terminal in Msg3PUSCH, the terminal considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0056] If the contention resolution is unsuccessful, the terminal reselects a random access channel (RACH) transmission resource, performs physical random access channel (PRACH) transmission, and makes the next random access attempt.

[0057] In NR Rel-16, the two-step random access process 2-step RACH was introduced. The first step is that the terminal sends MsgA to the network side. After receiving MsgA, the network side sends MsgB to the terminal. If the terminal does not receive MsgB within a certain period of time, the terminal will increment the counter that counts the number of times MsgA is sent and resend MsgA. If the counter that counts the number of times MsgA is sent reaches a certain threshold, the terminal will switch from the 2-step random access process to the 4-step random access process. MsgA includes the MsgA preamble part and the MsgA PUSCH part. The preamble part is sent on the RO used for 2-step RACH, and the PUSCH part is sent on the MsgA PUSCH resources associated with the sending of the MsgA preamble and the RO. MsgA PUSCH resources are a set of PUSCH resources configured relative to each PRACH time slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

[0058] 4. Repeated transmission

[0059] Generally speaking, due to factors such as limited terminal power, uplink channel coverage is more likely to be limited, and repeated transmissions are needed to improve coverage or reliability. Taking the Physical Uplink Control Channel (PUCCH) repeated transmission as an example, there are two types of repeated transmissions: dedicated PUCCH repeated transmissions and common PUCCH repeated transmissions.

[0060] Prior to NR Rel-16, dedicated PUCCH repetitions were configured in conjunction with the PUCCH format, for example, via the nrofSlots parameter in PUCCH-FormatConfig. In NR Rel-17, dedicated PUCCH repetitions can be configured for each PUCCH resource in the PUCCH-config IE, using the parameter pucch-RepetitionNrofSlots-r17, thus indirectly enabling dynamic PUCCH repetitions.

[0061] The number of repetitions for common PUCCH retransmissions is {1, 2, 4, 8}. There are two main ways to indicate the configuration of PUCCH retransmissions: one is to configure a repetition number through the System Information Block (SIB), so that terminals with the transmission capability of common PUCCH retransmissions can transmit based on the configured repetition number; the other is to configure at least two repetition numbers through the SIB, so that terminals with the transmission capability of common PUCCH retransmissions can be dynamically scheduled by the base station for PUCCH retransmissions, and the indicated repetition number is one of the at least two repetition numbers.

[0062] 5. Hybrid Automatic Repeat reQuest (HARQ) retransmission

[0063] The HARQ scheme increases both system reliability and transmission efficiency. HARQ is a stop-and-wait protocol consisting of multiple processes. A stop-and-wait protocol means that the transmitter pauses after each data packet transmission, awaiting confirmation from the receiver. When a data packet arrives at the receiver, it undergoes error checking. If received correctly, an acknowledgment is returned; otherwise, a non-acknowledgment is returned. Upon receiving an acknowledgment, the transmitter sends new data; otherwise, the previously transmitted data packet is resent. Multiple processes mean that the transmitter runs multiple different stop-and-wait protocols concurrently on the channel, utilizing the gaps between channels to interleave data and signaling, thereby improving channel utilization. For uplink HARQ retransmissions, since NR requires a DCI indication for both retransmissions and new transmissions, if the base station fails to receive uplink data at the resource location indicated by the DCI or if the received uplink data contains errors, it sends a new DCI instructing the terminal to retransmit.

[0064] NR introduces autonomous retransmission for unlicensed band operation. Specifically, if the terminal device does not receive an acknowledgment or dynamic grant for the HARQ process before the timer expires, the terminal device interprets it as a non-acknowledgment of the configured grant transmission. The terminal device then performs a retransmission for the HARQ process in the configured grant resources. If there is a new packet to be sent, the retransmission should be given priority. Using the configured grant resources for autonomous retransmission as in unlicensed band operation will be detrimental to the deterministic transmission of time-sensitive communication services, because the configured grant resources are used to retransmit a previous packet of the time-sensitive communication service, and no resources can be used to send a new packet of the time-sensitive communication service. As a result, the subsequent transmission of the time-sensitive communication service will be delayed.

[0065] 6. TA

[0066] The TA is sent by the base station to the terminal, indicating the timing advance to be adjusted when sending uplink channels (such as PUSCH, PUCCH) and sounding reference signals (SRS). The timing advance command (TAC) is a command instructing the terminal to adjust the TA.

[0067] In NR, TA information is delivered to the terminal in two main ways: the initial timing advance command delivered in the RAR message and the timing advance command delivered in the Media Access Control-Control Element (MAC-CE) message. The initial timing advance command delivered in the RAR message: For the first uplink message after the PRACH, the terminal applies the timing advance value extracted from the RAR. The timing advance command delivered in the MAC-CE message: After the initial connection is completed, the terminal adjusts the uplink transmission based on the MAC-CE timing advance.

[0068] The initial TAC (transfer address) used by the RAR is approximately 12 bits long and has a value range of 0–3846, representing an absolute TA. The TAC (transfer address) used by the MAC-CE is approximately 6 bits long and has a value range of 0–63, representing a relative TA. The TA is controlled by the MAC layer and implemented by the physical layer. The TA value depends on the signal propagation delay from the base station to the terminal, meaning that different terminals in different locations will have different TA values. The goal of the TAC is to ensure consistent uplink transmissions from all terminals to the base station.

[0069] The following describes in detail the uplink data transmission method provided by the embodiment of the present application through some embodiments and their application scenarios in combination with the accompanying drawings.

[0070] The embodiment of the present application provides an uplink data transmission method, and Figure 2 shows a flow chart of the uplink data transmission method provided by the embodiment of the present application. As shown in Figure 2, the uplink data transmission method provided by the embodiment of the present application may include the following steps 201 and 202.

[0071] Step 201: The terminal obtains first information.

[0072] In the embodiment of the present application, the first information is configuration information related to uplink data transmission in a non-connected state, and the first information includes at least one of the following: repetition related information, retransmission related information, and TA information.

[0073] It should be noted that the non-connected state in the embodiment of the present application may be an RRC-idle state, an RRC-inactive state, or a standby state or an inactive state introduced in a 6G or future mobile communication system, or a state after RRC release and before random access, or other non-connected states before random access.

[0074] In the embodiments of the present application, uplink data transmission refers to the transmission of uplink data information for a terminal in a non-connected state, where the uplink data information includes small data (i.e., data with a size less than a preset bit) and normal data. Exemplarily, the uplink data information may include data information in a non-connected state before the terminal performs random access, such as but not limited to at least one of the following: early data transmission directly scheduled or carried by a paging PDCCH or a paging PDSCH.

[0075] Optionally, in the embodiment of the present application, the above-mentioned paging includes at least one of the following: a short message, a paging message.

[0076] Optionally, in an embodiment of the present application, the above-mentioned first information may be configured by the network or predefined by the protocol (for example, for repeated transmission in a non-connected state, N repeated transmissions are supported by default).

[0077] In one case, for uplink data transmission in a non-connected state, the reliability of uplink data transmission can be ensured by repeated transmission. Specifically, the terminal can be configured with repeated transmission related information to support repeated transmission of uplink data in a non-connected state.

[0078] Optionally, in the embodiment of the present application, the repeated transmission related information includes at least one of the following:

[0079] an indication of whether duplicate transmissions are allowed;

[0080] Number of repeated transmissions;

[0081] Repeated transmission resource information, used to represent the resources for repeated transmission;

[0082] Repeated transmission beam information, used to characterize the repeatedly transmitted beam, beam index, or relationship between beams;

[0083] The frequency hopping information is used to indicate that different times of repeated transmission have different frequency domain resources.

[0084] Optionally, in an embodiment of the present application, the repeatedly transmitted resource includes any one of the following:

[0085] Continuous physical time domain resources, the physical time domain resources including at least one of the following: a symbol, a time slot, a subframe, a frame, or other time units specified by a network configuration or protocol;

[0086] Continuous effective time domain resources.

[0087] Optionally, in an embodiment of the present application, the above-mentioned continuous physical time domain resources are used for repeated transmission, and these continuous physical time domain resources are counted in the configured number of repeated transmissions.

[0088] In the embodiment of the present application, the above-mentioned continuous valid time domain resources (also referred to as available time domain resources) are used for repeated transmission, and these valid time domain resources are counted in the configured number of repeated transmissions.

[0089] Optionally, in an embodiment of the present application, the above-mentioned effective time domain resources are time domain resources determined based on third information, and the third information includes at least one of the following: an uplink time slot or a non-downlink subband in an uplink time slot, a flexible time slot, and an uplink subband in a downlink time slot.

[0090] For example, the network configures 4 repeated transmissions, and in 4 consecutive uplink time slots, a downlink subband is configured in the second time slot, and the downlink subband overlaps with or is relatively close to the scheduled repeated transmission frequency domain resources (for example, not exceeding a certain frequency domain interval threshold). At this time, the second time slot can be considered invalid, that is, an unavailable time slot, and it is necessary to continue to find a time slot that can completely send 4 repeated transmissions.

[0091] Optionally, in an embodiment of the present application, the above-mentioned effective time domain resources are time domain resources that meet a first condition, and the first condition includes at least one of the following: not sending the first signal, not overlapping with the first signal in the time domain, not overlapping with the first signal in the frequency domain, and the time domain interval with the first signal is greater than or equal to a first threshold.

[0092] Optionally, in an embodiment of the present application, the above-mentioned first signal includes at least one of the following: terminal-specific PUCCH, terminal-specific PUSCH, PRACH, MsgA, MsgA PRACH, MagA PUSCH, Msg3PUSCH, PUCCH for Msg4 or MsgB HARQ feedback, Msg5PUSCH, synchronization signal block (Synchronization Signal Block, SSB), channel state information reference signal (Channel State Information-Reference Signal, CSI-RS).

[0093] Optionally, in an embodiment of the present application, the first signal may be a signal before RRC release or a signal in a non-connected state. For example, the signal before RRC release may include a terminal-specific PUCCH, a terminal-specific PUSCH, etc. The signal in the non-connected state may include PRACH, MsgA, MsgA PRACH, MagA PUSCH, Msg3PUSCH, PUCCH for Msg4 or MsgB HARQ feedback, Msg5PUSCH, etc.

[0094] Optionally, in an embodiment of the present application, the above-mentioned number of repeated transmissions is associated with second information, and the second information includes at least one of the following: scheduling information of initial transmission of uplink data in a non-connected state, the above-mentioned repeated transmission resource information, and the above-mentioned repeated transmission beam information.

[0095] It can be understood that the terminal can obtain the above-mentioned number of repeated transmissions from the association between the number of repeated transmissions and the second information, that is, the number of repeated transmissions is not directly indicated, and the terminal can implicitly determine it according to the second information.

[0096] Optionally, in an embodiment of the present application, the scheduling information may include at least one of the following: time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA).

[0097] Exemplarily, the network configures a TDRA for repeated transmission, and the TDRA is associated with a number of repeated transmissions, that is, the number of repeated transmissions is implicitly indicated by the TDRA.

[0098] For example, the network configures four consecutive time slots for repeated transmission, which implicitly indicates that the number of repeated transmissions is four, that is, four repeated transmissions are performed using four consecutive time slots. Alternatively, the network configures four different beams for repeated transmission, which implicitly indicates that the number of repeated transmissions is four, that is, four different beams are used for repeated transmission.

[0099] Optionally, in an embodiment of the present application, the above-mentioned number of repeated transmissions is the same as the number of repeated transmissions of the first signal.

[0100] Optionally, in an embodiment of the present application, the above-mentioned number of repeated transmissions is a common number of repeated transmissions, and the common number of repeated transmissions is a common number of repeated transmissions in a non-connected state predefined by the network configuration or protocol.

[0101] Optionally, in an embodiment of the present application, the number of repetitions and the first signal use the same set of repetitions. That is, the number of repetitions and the first signal use the same set of repetitions, and the number of repetitions and the first signal may be the same or different.

[0102] Exemplarily, SIB1 may configure one or more repetition times (a set of repetition times) for the repetition of the above uplink data transmission, and is also used to determine the repetition times of Msg1, Msg3 or MsgA.

[0103] For example, SIB1 configures a TDRA list, associates one or more repetition transmission times with a TDRA, and when the TDRA is determined, the repetition transmission times are also determined. The TDRA list can be used for the repetition transmission of at least one of the above-mentioned uplink data transmission, Msg1, Msg3, and MsgA.

[0104] Optionally, in an embodiment of the present application, the repeatedly transmitted resources may have the same or different FDRAs at different times, i.e., they may support frequency hopping or not. Specifically, for the frequency hopping information, frequency domain hopping is supported between different times of repeated transmission, thereby improving the reliability of uplink data transmission.

[0105] Optionally, in the embodiment of the present application, in combination with FIG. 2 , as shown in FIG. 3 , the above step 201 may be specifically implemented through the following step 201 a.

[0106] Step 201a: The terminal obtains first information from the first message.

[0107] The first information includes the repeated transmission related information.

[0108] In the embodiment of the present application, the first message is any one of the following:

[0109] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0110] Channels for downlink data transmission in the non-connected state (e.g., the newly introduced PDSCH for downlink data transmission in the non-connected state);

[0111] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located (e.g., the newly introduced DCI or PDCCH for scheduling downlink data transmission in the non-connected state);

[0112] Paging DCI or paging PDSCH;

[0113] paging messages;

[0114] System messages (such as SSB or SIB);

[0115] RRC release message.

[0116] Optionally, in an embodiment of the present application, the relationship between the beams of the repeated transmissions includes: the beams used for all the repeated transmissions are the same; or, the beams used for at least some of the repeated transmissions are different.

[0117] It can be understood that the beams used for all the above-mentioned repeated transmissions are the same; or, the beams used for all the repeated transmissions are different; or, the beams used for some of the repeated transmissions are the same, and the beams used for another part of the repeated transmissions are different.

[0118] Optionally, in an embodiment of the present application, the beam used for the above-mentioned repeated transmission is determined based on at least one of the number of terminals and the number of repeated transmissions in the first paging message, and the first paging message includes a paging message associated with the scheduling information for scheduling the above-mentioned uplink data transmission.

[0119] For example, when paging four terminals, all four terminals are scheduled for uplink data transmission and instructed to transmit four repetitions. In this case, each terminal can use four different beams to transmit four uplink data transmissions. The beams can be determined by SRS training in the non-connected state or by CSI-RS measurement.

[0120] Optionally, in an embodiment of the present application, the beam used for the above-mentioned repeated transmission is associated with the beam of a second signal, and the second signal includes at least one of the following: paging PDCCH, paging PDSCH, one or more downlink transmission signals of repeated paging PDCCH transmission, one or more downlink transmission signals of repeated paging PDSCH transmission, CSI-RS, synchronization signal, broadcast signal, positioning reference signal (PRS), and SRS.

[0121] Exemplarily, the beam for uplink data transmission and the downlink beam for scheduling the paging PDCCH or the paging PDSCH for uplink data transmission are considered to have an uplink-downlink correspondence relationship.

[0122] As another example, the beam for uplink data transmission and the downlink beam for repeated transmission of the best paging PDCCH or paging PDSCH for scheduling uplink data transmission are considered to have an uplink and downlink correspondence relationship.

[0123] As another example, the beam for uplink data transmission and the downlink beam for CSI-RS transmission with the best early measurement result are considered to have an uplink and downlink correspondence relationship.

[0124] Optionally, in an embodiment of the present application, the above-mentioned synchronization signal may include at least one of the following: SSB, primary synchronization signal (Primary Synchronization Signal, PSS), secondary synchronization signal (Secondary Synchronization Signal, SSS), PRACH, Msg2, Msg 4, MsgB, SIB1, and other signals used for downlink synchronization (such as the downlink synchronization signal or channel defined in 6G).

[0125] Optionally, in an embodiment of the present application, the above-mentioned broadcast signal may include at least one of the following: SSB, Physical Broadcast Channel (PBCH), and public PDCCH.

[0126] In another case, for uplink data transmission in a non-connected state, the reliability of uplink data transmission can be ensured through retransmission. Specifically, retransmission related information can be configured for the terminal to support retransmission of uplink data in a non-connected state.

[0127] Optionally, in this embodiment of the present application, the retransmission-related information includes at least one of the following:

[0128] An indication of whether retransmission is allowed;

[0129] Retransmission resource information, used to represent the retransmission resources;

[0130] Retransmission beam information is used to identify the retransmission beam or beam index.

[0131] Optionally, in the embodiment of the present application, the retransmitted resource includes any one of the following:

[0132] The first PUSCH resource after the initial uplink data transmission in the non-connected state;

[0133] PUSCH resources after the first duration of initial uplink data transmission in the non-connected state;

[0134] The first semi-static or periodic uplink resource after the initial transmission of uplink data in the non-connected state;

[0135] Resources obtained based on scheduling information for uplink data retransmission in a non-connected state (e.g., resources determined based on relevant fields or bits (such as FDRA or TDRA) in the scheduling information);

[0136] Resources determined based on resources used for initial transmission of uplink data in the non-connected state (i.e., retransmission resources are associated with the resources used for initial transmission of the uplink data. For example, the retransmission resources are located at a time offset from the resources used for initial transmission of the uplink data, such as resources that are two time slots apart in time domain and share the same frequency domain);

[0137] A public transmission resource, which is a public resource for transmission in a non-connected state predefined by the network configuration or protocol;

[0138] The transmission resources configured by the network after entering the connected state.

[0139] Optionally, in the embodiment of the present application, in combination with FIG. 2 , as shown in FIG. 4 , the above step 201 may be specifically implemented through the following step 201 b.

[0140] Step 201b: The terminal obtains the first information from the second message.

[0141] The first information includes the retransmission related information.

[0142] In this embodiment of the present application, the second message is any one of the following:

[0143] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0144] Channels for downlink data transmission in the non-connected state (e.g., the newly introduced PDSCH for downlink data transmission in the non-connected state);

[0145] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located (e.g., the newly introduced DCI or PDCCH for scheduling downlink data transmission in the non-connected state);

[0146] Paging DCI or paging PDSCH;

[0147] paging messages;

[0148] System messages (such as SSB or SIB);

[0149] RRC release message;

[0150] The first PDCCH after the initial uplink data transmission in the non-connected state;

[0151] PDCCH after a preset time period for the initial transmission of uplink data in the non-connected state.

[0152] In another case, for uplink data transmission in a non-connected state, TA information may be configured for the terminal to support uplink data transmission in a non-connected state, thereby ensuring reliability of the uplink data transmission.

[0153] Optionally, in an embodiment of the present application, the first information includes the TA information; the TA information is any one of the following:

[0154] Default TA value (for example, TA value is 0);

[0155] a TA value determined by the terminal according to fourth information, where the fourth information includes at least one of the following: location information of the terminal, tracking area information (e.g., tracking area identifier) ​​of the terminal, and a TA offset;

[0156] TA value indicated by the network;

[0157] TA value used by the terminal in the last uplink transmission.

[0158] Optionally, in an embodiment of the present application, the TA value indicated by the network is determined based on at least one of the following (may be determined by the network based on at least one of the following): first location information, first tracking area information, and TA offset;

[0159] Among them, the above-mentioned first location information includes any one of the following items: the location information of the terminal most recently measured by the access network, the location information of the terminal stored by the access network or the core network; the above-mentioned first tracking area information includes the tracking area information of the terminal stored by the access network or the core network.

[0160] Optionally, in an embodiment of the present application, the network indicates multiple TA values, each used for uplink data transmission of multiple paged terminals. Alternatively, the network indicates a single TA value, used for uplink data transmission of all paged terminals. Alternatively, the network indicates a single TA value, used for uplink data transmission of the terminal corresponding to the first paging record in the paging message, and configures a TA offset relative to the TA value for each of the other paged terminals.

[0161] Optionally, in an embodiment of the present application, the TA offset is indicated by the network. The TA value indicated by the network or the indication method of the TA offset indicated by the network includes any of the following:

[0162] Indicated in paging PDCCH, paging PDSCH or other physical signals;

[0163] Indicated in the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0164] Indicated in the DCI or PDCCH for scheduling uplink data retransmission in the non-connected state;

[0165] Indicated in the channel for downlink data transmission in the non-connected state (for example, the newly introduced PDSCH for downlink data transmission);

[0166] The scheduling information of downlink data transmission in the non-connected state is indicated in the downlink channel (for example, the newly introduced DCI or PDCCH for scheduling the downlink data transmission);

[0167] It is indicated together with the scheduling information of uplink data transmission in the non-connected state (for example, the network indicates the scheduling information of uplink data transmission of the corresponding terminal and the TAC in each paging record, and the TAC is used to indicate the TA value of uplink data transmission).

[0168] Optionally, in the embodiment of the present application, the value of the TA offset is determined according to at least one of the following:

[0169] Duplex configuration information;

[0170] Whether it is a terrestrial network or a non-terrestrial network;

[0171] Whether the network coverage size is greater than a second threshold.

[0172] Optionally, in an embodiment of the present application, the TA value indicated by the above network is an absolute TA value (that is, the absolute TA value is an absolute indication of the TA value, that is, the TAC from the network used for uplink data transmission is an absolute TAC), which can be directly used by the terminal to adjust the uplink transmission time.

[0173] Optionally, in an embodiment of the present application, the above-mentioned absolute TA value can be carried in a MAC-CE message.

[0174] Optionally, in the embodiment of the present application, the TA value used for the initial transmission of uplink data in the non-connected state is a default TA value.

[0175] Optionally, in an embodiment of the present application, the TA value used for retransmission of uplink data in the non-connected state is a TA value indicated by the network.

[0176] Exemplarily, the network determines the first TA value of the terminal based on the initial transmission of uplink data in the non-connected state; the network indicates the first TA value to the terminal, for example, the first TA value can be carried in the DCI or PDCCH for scheduling the retransmission of uplink data in the non-connected state; the terminal performs the above-mentioned uplink data retransmission based on the first TA value.

[0177] Step 202: The terminal performs uplink data transmission according to the first information.

[0178] In the embodiment of the present application, the terminal may send uplink feedback information or data information (information of the terminal before random access) in a non-connected state according to the first information.

[0179] It is understood that the terminal may perform repeated transmission of uplink data transmission in the non-connection state based on the repeated transmission related information. Alternatively, the terminal may perform retransmission of uplink data transmission in the non-connection state based on the retransmission related information. Alternatively, the terminal may perform initial transmission or retransmission of uplink data transmission in the non-connection state based on the TA information.

[0180] Optionally, in the embodiment of the present application, the first information includes the retransmission related information. The step 202 can be implemented by the following step 202a or step 202b.

[0181] Step 202a: The terminal performs automatic retransmission or HARQ retransmission of uplink data transmission in a non-connected state according to the first information.

[0182] Step 202b: The terminal performs automatic retransmission or HARQ retransmission of uplink data transmission after entering the connected state according to the first information.

[0183] Optionally, in the embodiment of the present application, the retransmission of the uplink data transmission is the automatic retransmission. The “terminal performing automatic retransmission of uplink data transmission” can be implemented by any of the following:

[0184] The terminal automatically retransmits at least once within the first time window;

[0185] The terminal automatically retransmits at least once after the first time window;

[0186] The terminal automatically retransmits at least once within the start of the first timer;

[0187] The terminal automatically retransmits at least once after the first timer expires;

[0188] The terminal performs at least one automatic retransmission after a first moment, where the first moment is the sum of a moment of initial transmission of uplink data in a non-connected state and a time domain offset.

[0189] Optionally, in an embodiment of the present application, the first time window is determined by a start point and an end point or a start point and a duration predefined by a network configuration or a protocol.

[0190] Optionally, in an embodiment of the present application, the first timer may be triggered based on a condition predefined by a network configuration or protocol.

[0191] Optionally, in an embodiment of the present application, the first timer starts timing at a time slot next to the time slot in which the uplink data is initially transmitted in a non-connected state. Alternatively, the first timer starts timing at an uplink time slot next to the time slot in which the uplink data is initially transmitted in a non-connected state.

[0192] Optionally, in an embodiment of the present application, after receiving K (eg, a predefined number) retransmissions within the first timer, the first timer is stopped.

[0193] Optionally, in an embodiment of the present application, for retransmission of uplink data transmission in a non-connected state, the terminal performs retransmission after entering a connected state.

[0194] Optionally, in an embodiment of the present application, for retransmission of uplink data transmission in a non-connected state, the terminal performs retransmission after receiving retransmission scheduling information (such as the above-mentioned retransmission related information) from the network.

[0195] An embodiment of the present application provides an uplink data transmission method, in which a terminal can obtain relevant configuration information of uplink data transmission in a non-connected state, including at least one of the following: repeated transmission related information, retransmission related information, and TA information, and perform uplink data transmission according to the relevant configuration information. In this solution, for uplink data transmission of a terminal in a non-connected state, the terminal can perform repeated transmission of uplink data transmission in a non-connected state according to repeated transmission related information, or perform retransmission of uplink data transmission in a non-connected state according to retransmission related information, or perform uplink data transmission in a non-connected state according to TA information, so that the terminal can perform initial transmission, repeated transmission, or retransmission of data with the network side without entering a connected state, thereby improving the reliability of uplink data transmission in a non-connected state.

[0196] The embodiment of the present application provides an uplink data transmission method, and Figure 5 shows a flowchart of the uplink data transmission method provided by the embodiment of the present application. As shown in Figure 5, the uplink data transmission method provided by the embodiment of the present application may include the following steps 301 to 303.

[0197] Step 301: The network-side device sends first information to the terminal.

[0198] In the embodiment of the present application, the first information is configuration information related to uplink data transmission in a non-connected state, and the first information is used to perform uplink data transmission. The first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

[0199] Step 302: The terminal receives first information from a network-side device.

[0200] Step 303: The terminal performs uplink data transmission according to the first information.

[0201] Optionally, in an embodiment of the present application, in combination with FIG5 , as shown in FIG6 , the above step 301 may be specifically implemented through the following step 301a , and the above step 302 may be specifically implemented through the following step 302a .

[0202] Step 301a: The network-side device sends a first message to the terminal.

[0203] Step 302a: The terminal receives a first message from the network-side device.

[0204] In the embodiment of the present application, the first message includes first information. The first information includes repeated transmission related information. The first message is any one of the following:

[0205] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0206] A channel for downlink data transmission in a non-connected state;

[0207] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located;

[0208] Paging DCI or paging PDSCH;

[0209] paging messages;

[0210] System messages;

[0211] RRC release message.

[0212] Optionally, in an embodiment of the present application, in combination with FIG. 5 , as shown in FIG. 7 , the above step 301 may be specifically implemented through the following step 301 b , and the above step 302 may be specifically implemented through the following step 302 b .

[0213] Step 301b: The network-side device sends a second message to the terminal.

[0214] Step 302b: The terminal receives a second message from the network-side device.

[0215] In the embodiment of the present application, the second message includes the first information. The first information includes retransmission related information. The second message is any one of the following:

[0216] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0217] A channel for downlink data transmission in a non-connected state;

[0218] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located;

[0219] Paging DCI or paging PDSCH;

[0220] paging messages;

[0221] System messages;

[0222] RRC release message;

[0223] The first PDCCH after the initial uplink data transmission in the non-connected state;

[0224] PDCCH after a preset time period for the initial transmission of uplink data in the non-connected state.

[0225] It should be noted that, for repeated transmission related information, retransmission related information, TA information and related solutions, please refer to the description in the above embodiments, which will not be repeated here.

[0226] An embodiment of the present application provides an uplink data transmission method, in which a network-side device can send relevant configuration information of uplink data transmission in a non-connected state to a terminal, including at least one of the following: repeated transmission related information, retransmission related information, and TA information, so that the terminal performs uplink data transmission according to the relevant configuration information. In this solution, for uplink data transmission of a terminal in a non-connected state, the network-side device can configure relevant configuration information of uplink data transmission in a non-connected state to the terminal, so that the terminal can perform repeated transmission of uplink data transmission in a non-connected state according to repeated transmission related information, or perform retransmission of uplink data transmission in a non-connected state according to retransmission related information, or perform uplink data transmission in a non-connected state according to TA information, so that the terminal can perform initial transmission, repeated transmission, or retransmission of data with the network side without entering a connected state, thereby improving the reliability of uplink data transmission in a non-connected state.

[0227] Each of the above-mentioned method embodiments, or various possible implementation methods in each method embodiment, can be executed separately, or any two or more of them can be executed in combination with each other. The specific implementation can be determined according to actual usage requirements, and the embodiments of this application do not limit this.

[0228] The uplink data transmission method provided in the embodiment of the present application may be executed by an uplink data transmission device. In the embodiment of the present application, the uplink data transmission device provided in the embodiment of the present application is described by taking the uplink data transmission method performed by the uplink data transmission device as an example.

[0229] FIG8 shows a possible structural diagram of an uplink data transmission device involved in an embodiment of the present application. As shown in FIG8 , the uplink data transmission device 40 may include: an acquisition module 41 and a transmission module 42 .

[0230] The acquisition module 41 is configured to acquire first information, which is configuration information related to uplink data transmission in a non-connected state. The first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information. The transmission module 42 is configured to perform uplink data transmission based on the first information acquired by the acquisition module 41.

[0231] In one possible implementation, the repeated transmission related information includes at least one of the following:

[0232] an indication of whether duplicate transmissions are allowed;

[0233] Number of repeated transmissions;

[0234] Repeated transmission resource information, used to represent the resources for repeated transmission;

[0235] Repeated transmission beam information, used to characterize the repeatedly transmitted beam, beam index, or relationship between beams;

[0236] The frequency hopping information is used to indicate that different times of repeated transmission have different frequency domain resources.

[0237] In one possible implementation, the number of repeated transmissions is associated with second information, where the second information includes at least one of the following: scheduling information for initial transmission of uplink data in a non-connected state, repeated transmission resource information, and repeated transmission beam information;

[0238] Alternatively, the number of repeated transmissions is the same as the number of repeated transmissions of the first signal;

[0239] Alternatively, the number of repeated transmissions is a common number of repeated transmissions, which is a common number of repeated transmissions for transmission in a non-connected state predefined by a network configuration or a protocol;

[0240] Alternatively, the above-mentioned repetition transmission times and the first signal use the same repetition transmission times set.

[0241] In a possible implementation, the repeatedly transmitted resource includes any one of the following:

[0242] Continuous physical time domain resources, the physical time domain resources including at least one of the following: a symbol, a time slot, a subframe, a frame, or other time units specified by a network configuration or protocol;

[0243] Continuous effective time domain resources.

[0244] In one possible implementation, the above-mentioned effective time domain resources are time domain resources determined based on third information, and the third information includes at least one of the following: an uplink time slot or a non-downlink subband in an uplink time slot, a flexible time slot, and an uplink subband in a downlink time slot; or, the above-mentioned effective time domain resources are time domain resources that meet the first condition, and the first condition includes at least one of the following: not sending the first signal, not overlapping with the first signal in the time domain, not overlapping with the first signal in the frequency domain, and the time domain interval with the first signal is greater than or equal to the first threshold.

[0245] In one possible implementation, the first signal includes at least one of the following: terminal-specific PUCCH, terminal-specific PUSCH, PRACH, MsgA, MsgA PRACH, MagA PUSCH, Msg3 PUSCH, PUCCH for Msg4 or MsgB HARQ feedback, Msg5 PUSCH, SSB, and CSI-RS.

[0246] In a possible implementation, the first information includes repeated transmission related information; the acquisition module 41 is specifically configured to acquire the first information from the first message; wherein the first message is any one of the following:

[0247] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0248] A channel for downlink data transmission in a non-connected state;

[0249] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located;

[0250] Paging DCI or paging PDSCH;

[0251] paging messages;

[0252] System messages;

[0253] RRC release message.

[0254] In a possible implementation, the relationship between the beams of the repeated transmissions includes: the beams used for all the repeated transmissions are the same; or the beams used for at least some of the repeated transmissions are different.

[0255] In one possible implementation, the beam used for the above-mentioned repeated transmission is determined based on at least one of the number of terminals and the number of repeated transmissions in a first paging message, and the first paging message includes a paging message associated with the scheduling information for scheduling the above-mentioned uplink data transmission; or, the beam used for the above-mentioned repeated transmission is associated with the beam of a second signal, and the second signal includes at least one of the following: paging PDCCH, paging PDSCH, one or more downlink transmission signals of repeated paging PDCCH transmission, one or more downlink transmission signals of repeated paging PDSCH transmission, CSI-RS, synchronization signal, broadcast signal, PRS, SRS.

[0256] In one possible implementation, the retransmission-related information includes at least one of the following:

[0257] An indication of whether retransmission is allowed;

[0258] Retransmission resource information, used to represent the retransmission resources;

[0259] Retransmission beam information is used to identify the retransmission beam or beam index.

[0260] In a possible implementation, the retransmitted resource includes any one of the following:

[0261] The first PUSCH resource after the initial uplink data transmission in the non-connected state;

[0262] PUSCH resources after the first duration of initial uplink data transmission in the non-connected state;

[0263] The first semi-static or periodic uplink resource after the initial transmission of uplink data in the non-connected state;

[0264] Resources obtained based on scheduling information for uplink data retransmission in a non-connected state;

[0265] Resources determined based on resources for initial uplink data transmission in a non-connected state;

[0266] A public transmission resource, which is a public resource for transmission in a non-connected state predefined by the network configuration or protocol;

[0267] The transmission resources configured by the network after entering the connected state.

[0268] In a possible implementation, the first information includes retransmission related information; and the obtaining module 41 is specifically configured to obtain the first information from a second message, where the second message is any one of the following:

[0269] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0270] A channel for downlink data transmission in a non-connected state;

[0271] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located;

[0272] Paging DCI or paging PDSCH;

[0273] paging messages;

[0274] System messages;

[0275] RRC release message;

[0276] The first PDCCH after the initial uplink data transmission in the non-connected state;

[0277] PDCCH after a preset time period for the initial transmission of uplink data in the non-connected state.

[0278] In one possible implementation, the first information includes retransmission-related information; the transmission module 42 is specifically used to perform automatic retransmission or HARQ retransmission of uplink data transmission in a non-connected state according to the first information; or, according to the first information, perform automatic retransmission or HARQ retransmission of uplink data transmission after entering a connected state.

[0279] In a possible implementation, the retransmission of the uplink data transmission is automatic retransmission; and the transmission module 42 is specifically configured to perform any of the following:

[0280] Perform at least one automatic retransmission within the first time window;

[0281] Perform at least one automatic retransmission after the first time window;

[0282] Perform at least one automatic retransmission within the first timer start time;

[0283] Perform at least one automatic retransmission after a first timer expires;

[0284] At least one automatic retransmission is performed after a first moment, where the first moment is the sum of a moment of initial transmission of uplink data in a non-connected state and a time domain offset.

[0285] In one possible implementation, the first information includes TA information; the TA information is any one of the following:

[0286] Default TA value;

[0287] a TA value determined by the terminal according to fourth information, where the fourth information includes at least one of the following: location information of the terminal, tracking area information of the terminal, and a TA offset;

[0288] TA value indicated by the network;

[0289] TA value used by the terminal in the last uplink transmission.

[0290] In one possible implementation, the TA value indicated by the above network is determined based on at least one of the following: first location information, first tracking area information, and TA offset; wherein the first location information includes any one of the following: the location information of the terminal most recently measured by the access network, the location information of the terminal stored by the access network or the core network; the first tracking area information includes the tracking area information of the terminal stored by the access network or the core network.

[0291] In a possible implementation, the TA offset is indicated by a network; the TA value indicated by the network or the manner in which the TA offset indicated by the network is indicated includes any one of the following:

[0292] Indicated in paging PDCCH, paging PDSCH or other physical signals;

[0293] Indicated in the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0294] Indicated in the DCI or PDCCH for scheduling uplink data retransmission in the non-connected state;

[0295] In-channel indication of downlink data transmission in non-connected state;

[0296] Indicated in the downlink channel where the scheduling information for downlink data transmission in the non-connected state is located;

[0297] It is indicated together with the scheduling information of uplink data transmission in the non-connected state.

[0298] In one possible implementation, the value of the TA offset is determined according to at least one of the following:

[0299] Duplex configuration information;

[0300] Whether it is a terrestrial network or a non-terrestrial network;

[0301] Whether the network coverage size is greater than a second threshold.

[0302] In a possible implementation, the TA value indicated by the network is an absolute TA value;

[0303] The TA value used for initial uplink data transmission in the non-connected state is the default TA value;

[0304] The TA value used for uplink data retransmission in the non-connected state is the TA value indicated by the network.

[0305] An embodiment of the present application provides an uplink data transmission device. For uplink data transmission in a non-connected state, the uplink data transmission device can perform repeated transmission of uplink data transmission in the non-connected state based on repeated transmission related information, or perform retransmission of uplink data transmission in the non-connected state based on retransmission related information, or perform uplink data transmission in the non-connected state based on TA information, so as to achieve initial transmission, repeated transmission or retransmission of data with the network side without entering a connected state, thereby improving the reliability of uplink data transmission in the non-connected state.

[0306] The uplink data transmission device in the embodiments of the present application can be an electronic device, such as an electronic device with an operating system, or a component of an electronic device, such as an integrated circuit or chip. The electronic device can be a terminal or other device other than a terminal. For example, the terminal can include but is not limited to the types of terminal 11 listed above, and other devices can include servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0307] The uplink data transmission device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned uplink data transmission method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0308] FIG9 shows a possible structural diagram of an uplink data transmission device involved in an embodiment of the present application. As shown in FIG9 , the uplink data transmission device 50 may include: a sending module 51 .

[0309] Among them, the sending module 51 is used to send the first information to the terminal, which is the relevant configuration information of uplink data transmission in the non-connected state, and the first information is used to perform uplink data transmission; wherein, the first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

[0310] In one possible implementation, the repeated transmission related information includes at least one of the following:

[0311] an indication of whether duplicate transmissions are allowed;

[0312] Number of repeated transmissions;

[0313] Repeated transmission resource information, used to represent the resources for repeated transmission;

[0314] Repeated transmission beam information, used to characterize the repeatedly transmitted beam, beam index, or relationship between beams;

[0315] The frequency hopping information is used to indicate that different times of repeated transmission have different frequency domain resources.

[0316] In a possible implementation, the first information includes repeated transmission related information; the sending module 51 is specifically configured to send a first message to the terminal, where the first message includes the first information;

[0317] The first message is any of the following:

[0318] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0319] A channel for downlink data transmission in a non-connected state;

[0320] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located;

[0321] Paging DCI or paging PDSCH;

[0322] paging messages;

[0323] System messages;

[0324] RRC release message.

[0325] In one possible implementation, the retransmission-related information includes at least one of the following:

[0326] An indication of whether retransmission is allowed;

[0327] Retransmission resource information, used to represent the retransmission resources;

[0328] Retransmission beam information is used to identify the retransmission beam or beam index.

[0329] In a possible implementation, the first information includes retransmission related information; the sending module 51 is specifically configured to send a second message to the terminal, where the second message includes the first information;

[0330] The second message is any one of the following:

[0331] Schedule the DCI or PDCCH for the initial uplink data transmission in the non-connected state;

[0332] A channel for downlink data transmission in a non-connected state;

[0333] The downlink channel where scheduling information for downlink data transmission in the non-connected state is located;

[0334] Paging DCI or paging PDSCH;

[0335] paging messages;

[0336] System messages;

[0337] RRC release message;

[0338] The first PDCCH after the initial uplink data transmission in the non-connected state;

[0339] PDCCH after a preset time period for the initial transmission of uplink data in the non-connected state.

[0340] In one possible implementation, the first information includes TA information; the TA information is any one of the following:

[0341] Default TA value;

[0342] a TA value determined by the terminal according to fourth information, where the fourth information includes at least one of the following: location information of the terminal, tracking area information of the terminal, and a TA offset;

[0343] TA value indicated by the network;

[0344] TA value used by the terminal in the last uplink transmission.

[0345] An embodiment of the present application provides an uplink data transmission device. For uplink data transmission in a non-connected state, the uplink data transmission device can configure relevant configuration information of the uplink data transmission in the non-connected state to the terminal, so that the terminal can perform repeated transmission of uplink data transmission in the non-connected state according to the repeated transmission related information, or perform retransmission of uplink data transmission in the non-connected state according to the retransmission related information, or perform uplink data transmission in the non-connected state according to the TA information, so that the terminal can perform initial transmission, repeated transmission or retransmission of data with the network side without entering the connected state, thereby improving the reliability of uplink data transmission in the non-connected state.

[0346] The uplink data transmission device provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned uplink data transmission method embodiment and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0347] As shown in Figure 10, an embodiment of the present application further provides a communication device 5000, including a processor 5001 and a memory 5002, wherein the memory 5002 stores a program or instruction that can be run on the processor 5001. For example, when the communication device 5000 is a terminal, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned terminal-side method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here. When the communication device 5000 is a network-side device, the program or instruction is executed by the processor 5001 to implement the various steps of the above-mentioned network-side device method embodiment, and can achieve the same technical effect. To avoid repetition, it is not repeated here.

[0348] The present application also provides a terminal including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the above-described uplink data transmission method embodiment. This terminal embodiment corresponds to the above-described terminal-side method embodiment, and each implementation process and implementation method of the above-described method embodiment is applicable to this terminal embodiment and can achieve the same technical effects. Specifically, Figure 11 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0349] The terminal 7000 includes but is not limited to: a radio frequency unit 7001, a network module 7002, an audio output unit 7003, an input unit 7004, a sensor 7005, a display unit 7006, a user input unit 7007, an interface unit 7008, a memory 7009 and at least some of the components of the processor 7010.

[0350] Those skilled in the art will appreciate that the terminal 7000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 7010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG11 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0351] It should be understood that in an embodiment of the present application, the input unit 7004 may include a graphics processing unit (GPU) 70041 and a microphone 70042, and the graphics processor 70041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 7006 may include a display panel 70061, and the display panel 70061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 7007 includes a touch panel 70071 and at least one of other input devices 70072. The touch panel 70071 is also called a touch screen. The touch panel 70071 may include two parts: a touch detection device and a touch controller. Other input devices 70072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0352] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 7001 may transmit the data to the processor 7010 for processing. Furthermore, the RF unit 7001 may send uplink data to the network-side device. Typically, the RF unit 7001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0353] The memory 7009 can be used to store software programs or instructions and various data. The memory 7009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 7009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 7009 in the embodiment of the present application includes, but is not limited to, these and any other suitable types of memory.

[0354] The processor 7010 may include one or more processing units. Optionally, the processor 7010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into the processor 7010.

[0355] The terminal provided in the embodiment of the present application can implement the various processes implemented in the above-mentioned method embodiment and achieve the same technical effect. The implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned uplink data transmission method embodiment. To avoid repetition, it will not be repeated here.

[0356] The present application also provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the above-mentioned uplink data transmission method embodiment. This network-side device embodiment corresponds to the above-mentioned network-side device method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment are applicable to this network-side device embodiment and can achieve the same technical effects.

[0357] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 12, the network-side device 600 includes an antenna 61, a radio frequency device 62, a baseband device 63, a processor 64, and a memory 65. Antenna 61 is connected to radio frequency device 62. In the uplink direction, radio frequency device 62 receives information via antenna 61 and sends the received information to baseband device 63 for processing. In the downlink direction, baseband device 63 processes the information to be transmitted and sends it to radio frequency device 62. Radio frequency device 62 processes the received information and then sends it through antenna 61.

[0358] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 63 , which includes a baseband processor.

[0359] The baseband device 63 may include, for example, at least one baseband board, on which multiple chips are arranged, as shown in Figure 12, one of which is, for example, a baseband processor, which is connected to the memory 65 through a bus interface to call the program in the memory 65 and execute the network device operations shown in the above method embodiment.

[0360] The network side device may further include a network interface 66, which is, for example, a Common Public Radio Interface (CPRI).

[0361] Specifically, the network side device 600 of the embodiment of the present application also includes: instructions or programs stored in the memory 65 and executable on the processor 64. The processor 64 calls the instructions or programs in the memory 65 to execute the methods executed by the modules shown in the above-mentioned uplink data transmission device and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0362] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned uplink data transmission method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0363] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0364] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned uplink data transmission method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0365] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0366] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned uplink data transmission method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0367] An embodiment of the present application further provides a wireless communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the above-mentioned uplink data transmission method, and the network-side device can be used to execute the steps of the above-mentioned uplink data transmission method.

[0368] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0369] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a necessary general-purpose hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0370] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. A method for uplink data transmission, comprising: The terminal obtains first information, where the first information is configuration information related to uplink data transmission in a non-connected state, and the first information includes at least one of the following: repeated transmission related information, retransmission related information, and timing advance TA information; The terminal performs the uplink data transmission according to the first information.

2. The method according to claim 1, wherein: The repeated transmission related information includes at least one of the following: an indication of whether duplicate transmissions are allowed; Number of retransmissions; Repeated transmission resource information, used to characterize the resources for repeated transmission; Repeated transmission beam information, used to characterize the repeatedly transmitted beam, beam index or the relationship between beams; The frequency hopping information is used to indicate that different times of repeated transmission have different frequency domain resources.

3. The method according to claim 2, wherein: The number of repeated transmissions is associated with second information, and the second information includes at least one of the following: scheduling information of initial transmission of uplink data in a non-connected state, the repeated transmission resource information, and the repeated transmission beam information; Alternatively, the number of repeated transmissions is the same as the number of repeated transmissions of the first signal; Alternatively, the number of repeated transmissions is a common number of repeated transmissions, and the common number of repeated transmissions is a common number of repeated transmissions in a non-connected state predefined by a network configuration or a protocol; Alternatively, the repetition transmission times and the first signal use the same repetition transmission times set.

4. The method according to claim 2, wherein: The repeatedly transmitted resource includes any one of the following: Continuous physical time domain resources, the physical time domain resources including at least one of the following: a symbol, a time slot, a subframe, a frame, or other time units specified by a network configuration or protocol; Continuous effective time domain resources; The effective time domain resource is a time domain resource determined based on third information, and the third information includes at least one of the following: an uplink time slot or a non-downlink subband in an uplink time slot, a flexible time slot, and an uplink subband in a downlink time slot; or, The effective time domain resources are time domain resources that meet the first condition, and the first condition includes at least one of the following: not sending the first signal, not overlapping with the first signal in the time domain, not overlapping with the first signal in the frequency domain, and the time domain interval with the first signal is greater than or equal to a first threshold.

5. The method according to claim 3 or 4, wherein: The first signal includes at least one of the following: terminal-specific physical uplink control channel PUCCH, terminal-specific physical uplink shared channel PUSCH, physical random access channel PRACH, MsgA, MsgA PRACH, MagA PUSCH, Msg3 PUSCH, PUCCH for Msg4 or MsgB hybrid automatic repeat request HARQ feedback, Msg5 PUSCH, synchronization signal block SSB, and channel state information reference signal CSI-RS.

6. The method according to any one of claims 1 to 5, wherein: The first information includes the repeated transmission related information; the terminal acquires the first information, including: The terminal obtains the first information from the first message; The first message is any one of the following: Downlink control information DCI or physical downlink control channel PDCCH for scheduling initial transmission of uplink data in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging physical downlink shared channel PDSCH; Paging messages; System messages; Radio Resource Control RRC Release message.

7. The method according to claim 2, wherein: The relationship between the beams of the repeated transmission includes: The beam used for all the repeated transmissions is the same; Alternatively, the beams used for at least some of the repeated transmissions are different.

8. The method according to claim 2 or 7, wherein: The beam used for the repeated transmission is determined according to at least one of the number of terminals and the number of repeated transmissions in a first paging message, wherein the first paging message includes a paging message associated with scheduling information for scheduling the uplink data transmission; or, The beam used for the repeated transmission is associated with the beam of the second signal, and the second signal includes at least one of the following: paging PDCCH, paging PDSCH, one or more downlink transmission signals of paging PDCCH repeated transmission, one or more downlink transmission signals of paging PDSCH repeated transmission, CSI-RS, synchronization signal, broadcast signal, positioning reference signal PRS, and sounding reference signal SRS.

9. The method according to claim 1, wherein: The retransmission related information includes at least one of the following: An indication of whether retransmission is allowed; Retransmission resource information, used to represent the retransmission resources; Retransmission beam information is used to indicate the retransmission beam or beam index.

10. The method according to claim 9, wherein: The retransmission resource includes any one of the following: The first PUSCH resource after the initial transmission of uplink data in the non-connected state; PUSCH resources after the first duration of initial uplink data transmission in a non-connected state; The first semi-static or periodic uplink resource after the initial transmission of uplink data in a non-connected state; Resources obtained based on scheduling information for uplink data retransmission in a non-connected state; Resources determined based on resources for initial transmission of uplink data in a non-connected state; A public transmission resource, wherein the public transmission resource is a public resource for transmission in a non-connected state predefined by a network configuration or a protocol; The transmission resources configured by the network after entering the connected state.

11. The method according to claim 1, 9 or 10, wherein: The first information includes the retransmission related information; and the terminal acquires the first information, including: The terminal obtains the first information from a second message, where the second message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message; The first PDCCH after the initial transmission of uplink data in the non-connected state; PDCCH after a preset time period for initial transmission of uplink data in a non-connected state.

12. The method of claim 1, 9, 10 or 11, wherein: The first information includes the retransmission related information; The terminal performing the uplink data transmission according to the first information includes: The terminal performs automatic retransmission or HARQ retransmission of the uplink data transmission in a non-connected state according to the first information; or, The terminal performs automatic retransmission or HARQ retransmission of the uplink data transmission after entering the connected state according to the first information.

13. The method according to claim 12, wherein: The retransmission of the uplink data transmission is the automatic retransmission; The terminal performs automatic retransmission of the uplink data transmission, including any of the following: The terminal performs at least one automatic retransmission within the first time window; The terminal automatically retransmits at least once after the first time window; The terminal automatically retransmits at least once within the start of the first timer; The terminal automatically retransmits at least once after the first timer times out; The terminal performs at least one automatic retransmission after a first moment, where the first moment is the sum of a moment of initial transmission of uplink data in a non-connected state and a time domain offset.

14. The method according to claim 1, wherein: The first information includes the TA information; The TA information is any of the following: Default TA value; The TA value determined by the terminal according to fourth information, where the fourth information includes at least one of the following: location information of the terminal, tracking area information of the terminal, and a TA offset; TA value indicated by the network; The TA value used by the terminal in the last uplink transmission.

15. The method according to claim 14, wherein: The TA value indicated by the network is determined based on at least one of the following: the first location information, the first tracking area information, and the TA offset; Among them, the first location information includes any one of the following items: the location information of the terminal most recently measured by the access network, the location information of the terminal stored by the access network or the core network; the first tracking area information includes the tracking area information of the terminal stored by the access network or the core network.

16. The method according to claim 14, wherein: The TA offset is indicated by the network; The indication method of the TA value indicated by the network or the TA offset indicated by the network includes any of the following: Indicated in paging PDCCH, paging PDSCH or other physical signals; Indicated in the DCI or PDCCH for the initial transmission of uplink data in the non-connected state; Indicated in the DCI or PDCCH for scheduling uplink data retransmission in the non-connected state; Indication in the channel of downlink data transmission in a non-connected state; Indicated in the downlink channel where the scheduling information of downlink data transmission in the non-connected state is located; It is indicated together with the scheduling information of uplink data transmission in the non-connected state.

17. The method according to claim 14, wherein: The value of the TA offset is determined according to at least one of the following: Duplex configuration information; Whether it is a terrestrial network or a non-terrestrial network; Whether the network coverage size is greater than a second threshold.

18. The method according to any one of claims 14 to 17, wherein: The TA value used for initial uplink data transmission in a non-connected state is the default TA value; The TA value used for uplink data retransmission in the non-connected state is the TA value indicated by the network.

19. An uplink data transmission method, comprising: The network side device sends first information to the terminal, where the first information is configuration information related to uplink data transmission in a non-connected state, and the first information is used to perform the uplink data transmission; The first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

20. The method according to claim 19, wherein: The first information includes the repeated transmission related information; the network side device sends the first information to the terminal, including: The network side device sends a first message to the terminal, where the first message includes the first information; The first message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message.

21. The method according to claim 19, wherein: The first information includes the retransmission related information; The network side device sends first information to the terminal, including: The network side device sends a second message to the terminal, where the second message includes the first information; The second message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message; The first PDCCH after the initial transmission of uplink data in the non-connected state; PDCCH after a preset time period for initial transmission of uplink data in a non-connected state.

22. An uplink data transmission device, comprising: Acquisition module and transmission module; The acquisition module is used to acquire first information, where the first information is configuration information related to uplink data transmission in a non-connected state, and the first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information; The transmission module is used to perform the uplink data transmission according to the first information acquired by the acquisition module.

23. The device according to claim 22, wherein: The first information includes the repeated transmission related information; the acquisition module is specifically used to acquire the first information from the first message; The first message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message.

24. The device according to claim 22, wherein: The first information includes the retransmission related information; the acquisition module is specifically used to acquire the first information from a second message, and the second message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message; The first PDCCH after the initial transmission of uplink data in the non-connected state; PDCCH after a preset time period for initial transmission of uplink data in a non-connected state.

25. An uplink data transmission device, comprising: Send module; The sending module is used to send first information to the terminal, where the first information is related configuration information of uplink data transmission in a non-connected state, and the first information is used to perform the uplink data transmission; The first information includes at least one of the following: repeated transmission related information, retransmission related information, and TA information.

26. The device according to claim 25, wherein The first information includes the repeated transmission related information; the sending module is specifically used to send a first message to the terminal, and the first message includes the first information; The first message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message.

27. The device according to claim 25, wherein: The first information includes the retransmission related information; The sending module is specifically configured to send a second message to the terminal, where the second message includes the first information; The second message is any one of the following: DCI or PDCCH for scheduling initial uplink data transmission in a non-connected state; A channel for downlink data transmission in a non-connected state; A downlink channel where scheduling information for downlink data transmission in a non-connected state is located; Paging DCI or paging PDSCH; Paging messages; System messages; RRC release message; The first PDCCH after the initial transmission of uplink data in the non-connected state; PDCCH after a preset time period for initial transmission of uplink data in a non-connected state.

28. A terminal, comprising a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the uplink data transmission method according to any one of claims 1 to 18 are implemented.

29. A network side device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the uplink data transmission method as described in any one of claims 19 to 21 are implemented.

30. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the uplink data transmission method according to any one of claims 1 to 18, or implements the steps of the uplink data transmission method according to any one of claims 19 to 21.

Images