Data sending method, data receiving method and related equipment

Abstract

The present application discloses a data sending method, a data receiving method and related equipment, which belong to the field of communication technology. The data sending method of an embodiment of the present application includes: a terminal performs a first operation; when the terminal is in an idle state or an inactive state, the terminal sends target data on a first bandwidth part BWP based on the first operation; wherein the first BWP is an initial uplink BWP configured by a network-side device for a terminal with reduced capability, and the first operation includes at least one of the following: mapping a first synchronization signal block SSB with a configured authorized physical uplink shared channel; determining whether a timing advance used for the configured authorized physical uplink shared channel is valid based on a target object, the target object being a second SSB or a target tracking reference signal; determining a target control resource set for sending the target data, the target control resource set being a control resource set associated with a dedicated search space for monitoring a physical downlink control channel PDCCH.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a data sending method, a data receiving method and related equipment. Background Art

[0002] With the advancement of communication technologies, network-side devices in communication systems typically need to configure an initial uplink (UL) bandwidth part (BWP). Furthermore, network-side devices can also configure a separate initial UL BWP for reduced-capability terminals. To reduce signaling overhead, terminals typically transmit small data over the initial UL BWP. However, whether reduced-capability terminals can transmit small data over the separate initial UL BWP is still under discussion. Summary of the Invention

[0003] Embodiments of the present application provide a data sending method, a data receiving method, and related devices, which can enable a reduced-capability terminal to transmit small data on a separate initial UL BWP.

[0004] In a first aspect, a data transmission method is provided, comprising:

[0005] The terminal performs a first operation;

[0006] When the terminal is in an idle state or an inactive state, the terminal sends target data on a first bandwidth part BWP based on a first operation;

[0007] The first BWP is an initial uplink BWP configured by the network side device for the reduced-capability terminal, and the first operation includes at least one of the following:

[0008] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0009] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0010] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0011] In a second aspect, a data receiving method is provided, comprising:

[0012] The network side device performs a first operation;

[0013] The network side device receives target data from the terminal on the first bandwidth part BWP based on the first operation;

[0014] The terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by a network-side device for the terminal with reduced capability, and the first operation includes at least one of the following:

[0015] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0016] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0017] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0018] According to a third aspect, a data transmission device is provided, comprising:

[0019] A first execution module, configured to execute a first operation;

[0020] a sending module, configured to send target data on the first bandwidth part BWP based on the first operation when the terminal is in an idle state or an inactive state;

[0021] The first BWP is an initial uplink BWP configured by the network side device for the reduced-capability terminal, and the first operation includes at least one of the following:

[0022] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0023] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0024] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0025] In a fourth aspect, a data receiving device is provided, comprising:

[0026] A second execution module, configured to execute the first operation;

[0027] A receiving module, configured to receive target data from a terminal on a first bandwidth part BWP based on the first operation;

[0028] The terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by a network-side device for the terminal with reduced capability, and the first operation includes at least one of the following:

[0029] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0030] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0031] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0032] 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.

[0033] In a sixth aspect, a terminal is provided, comprising a processor and a communication interface, wherein the processor is used to perform a first operation; the communication interface is used to send target data on a first bandwidth part BWP based on the first operation when the terminal is in an idle state or an inactive state; wherein the first BWP is an initial uplink BWP configured by a network-side device for a terminal with reduced capability, and the first operation includes at least one of the following: mapping a first synchronization signal block SSB with a configured authorized physical uplink shared channel; determining whether a time advance used for a configured authorized physical uplink shared channel is valid based on a target object, the target object being a second SSB or a target tracking reference signal; determining a target control resource set for sending target data, the target control resource set being a control resource set associated with a dedicated search space for monitoring a physical downlink control channel PDCCH.

[0034] 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 second aspect are implemented.

[0035] In the eighth aspect, a network side device is provided, including a processor and a communication interface, wherein the processor is used to perform a first operation, and the communication interface is used to receive target data from a terminal on a first bandwidth part BWP based on the first operation; wherein the terminal is in an idle state or an inactive state, and the first BWP is the initial uplink BWP configured by the network side device for the reduced capability terminal, and the first operation includes at least one of the following: mapping based on the first synchronization signal block SSB and the configured authorized physical uplink shared channel; determining whether the time advance used for the configured authorized physical uplink shared channel is valid based on the target object, and the target object is a second SSB or a target tracking reference signal; determining a target control resource set for sending target data, and the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel PDCCH.

[0036] In the ninth aspect, a communication system is provided, comprising: a terminal and a network side device, wherein the terminal can be used to execute the steps of the data sending method as described in the first aspect, and the network side device can be used to execute the steps of the data receiving method as described in the second aspect.

[0037] In the tenth 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.

[0038] 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 steps of the method described in the first aspect, or to implement the steps of the method described in the second aspect.

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

[0040] In an embodiment of the present application, a terminal performs a first operation; when the terminal is in an idle state or an inactive state, the terminal transmits target data on a first bandwidth part BWP based on the first operation; wherein the first BWP is the initial uplink BWP configured by the network-side device for the reduced-capability terminal, and the first operation includes at least one of the following: mapping the first synchronization signal block SSB with the configured authorized physical uplink shared channel; determining whether the timing advance used for the configured authorized physical uplink shared channel is valid based on the target object, the target object being the second SSB or the target tracking reference signal; determining the target control resource set for target data transmission, the target control resource set being the control resource set associated with the dedicated search space for monitoring the physical downlink control channel PDCCH. In this way, the terminal can implement small data transmission based on CG scheduling in the RRC inactive or idle state, thereby reducing the power consumption of the terminal and saving signaling overhead. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 This is a schematic diagram of a network structure applicable to the embodiments of the present application;

[0042] Figure 2 Schematic diagram of the data transmission method according to the embodiment of the present invention;

[0043] Figure 3 Schematic diagram of the data receiving method provided in the embodiment of the present application;

[0044] Figure 4 is a structural diagram of a data sending device provided in an embodiment of the present application;

[0045] Figure 5 is a structural diagram of a data receiving device provided in an embodiment of the present application;

[0046] Figure 6 is a structural diagram of a communication device provided in an embodiment of the present application;

[0047] Figure 7 is a structural diagram of a terminal provided in an embodiment of the present application;

[0048] Figure 8 This is a structural diagram of the network side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0049] 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.

[0050] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that 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, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected are in an "or" relationship.

[0051] 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) and 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 applications other than NR system applications, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0052] Figure 1A block diagram of a wireless communication system applicable to the embodiments of the present application is shown. 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) or 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) / virtual reality (VR) device, a robot, a wearable device (Wearable Device), a vehicle-mounted device (VUE), a pedestrian terminal (PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM or a self-service machine, and 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. It should be noted that the specific type of the terminal 11 is not limited in the embodiments 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 12 may also be referred to as a radio access network device, a radio access network (RAN), a radio access network function, or a radio access network unit. The access network device 12 may include a base station, a WLAN access point, or a WiFi node, etc. The base station may be referred to as a node B, an evolved node B (eNB), an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an extended service set (ESS), a home B node, a home evolved B node, a transmitting and receiving point (TRP), or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to a 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.

[0053] For ease of understanding, some of the contents involved in the embodiments of this application are described below:

[0054] 1. Random Access Channel (RACH) Process

[0055] Generally, the random access procedure includes a contention-based random access procedure and a non-contention-based random access procedure.

[0056] In the contention-based 4-step random access process, the terminal first sends message 1 (msg1) to the network device. The msg1 contains a preamble. After the network device detects the preamble, it sends msg2, which can also be called a random access response (RAR) message. The msg2 contains the number of the preamble 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 is consistent with the number of the preamble it sent. Then, according to the resources indicated by the RAR, it sends msg3 containing contention resolution information. After receiving msg3, the network device sends msg4 containing contention resolution information. After receiving msg4, the UE confirms that the resolution information is consistent with the one it sent in msg3, thus completing the 4-step random access.

[0057] Optionally, the network-side device includes uplink grant (UL grant) information in the RAR to indicate msg3 physical uplink shared channel (PUSCH) scheduling information, random access preamble ID (RACH preamble ID, RAPID), temporary cell-radio network temporary identifier (TC-RNTI), and timing advance (TA). If the network-side device does not receive the msg3 PUSCH, it can schedule the retransmission of the msg3 PUSCH in the TC-RNTI-scrambled physical downlink control channel (PDCCH).

[0058] 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 wireless 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 msg3 PUSCH according to the scheduling information in the RAR UL grant. Since repeated transmission of msg3 PUSCH is not currently supported, the network-side device can only decode the PUSCH sent by one UE on one msg3 PUSCH scheduling resource. Therefore, the network-side device 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 msg3 PUSCH, the terminal considers that the contention resolution is successful. If they do not match, the contention resolution is considered unsuccessful.

[0059] Optionally, if the contention resolution is unsuccessful, the UE reselects RACH transmission resources, performs PRACH transmission, and makes the next random access attempt.

[0060] Optionally, the 2-step random access process is as follows: first, the terminal sends message A (MsgA) to the network-side device, and then the network-side device sends message B (MsgB) to the terminal after receiving MsgA. 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 has been sent and resend MsgA. If the counter that counts the number of times MsgA has been 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 random access opportunity (RACH Occasion, RO) used for 2-step RACH, and the PUSCH part is sent on the MsgA preamble and the MsgAPUSCH resources associated with the RO. MsgAPUSCH resources are a group of PUSCH resources configured relative to each Physical Random Access Channel (PRACH) slot, including time-frequency resources and demodulation reference signal (DMRS) resources.

[0061] 2. Small Data Transmission

[0062] Efficient small data transmission is characterized by avoiding excessive signaling overhead during Radio Resource Control (RRC) state transitions and RRC connection establishment for non-connected terminals, achieving small data transmission through a minimal signaling process. Non-connected terminals include those in idle and inactive states.

[0063] A key characteristic of small data transmission is that the terminal's current Data Radio Bearer (DRB) is suspended, not released. Therefore, the terminal can resume the DRB before sending a ResumeRequest message, then use RRC signaling to piggyback the small data. At this point, data can be transmitted on the DRB, just like a connected terminal. This avoids state transitions and achieves efficient small data transmission with minimal signaling overhead.

[0064] Because small data transmission uses DRB transmission and access stratum (AS) security is activated, small data transmission can provide necessary security protections, such as data encryption and integrity protection. From a security perspective, since the terminal may have moved to another base station while in the suspended state, the security key used by the terminal to resend packets needs to be updated. The update method is based on the parameters provided by the network device to the terminal when the terminal enters the suspended state. The parameters are used to calculate the next hop key.

[0065] Small data transmissions are carried on the Dedicated Traffic Channel (DTCH) and multiplexed with the uplink RRC Connection Resume Request message before transmission. Similarly, any downlink reply message can also be carried on the DTCH and multiplexed with the downlink RRC Connection Release message. Both uplink and downlink data are encrypted using the next key after the update.

[0066] It should be understood that the transmission of small data may include the following situations:

[0067] Transmitted on Msg3 PUSCH based on the 4-step RACH process;

[0068] Transmitted on MsgAPUSCH based on the 2-step RACH process;

[0069] Transmission is performed on PUSCH resources scheduled by a Configured Grant (CG) configured in the RRC inactive state.

[0070] Among them, the small data transmission in the 2-step RACH and 4-step RACH processes can be called RACH-based small data transmission, and the small data transmission based on the PUSCH scheduled by CG is called CG-based small data transmission.

[0071] Currently, small data transmission in the RRC inactive state is only supported on the initial UL BWP. When a cell configures a separate initial UL BWP for a reduced-capability terminal, whether small data transmission can be performed on this BWP has not yet been discussed. To this end, the data transmission method of the present application is proposed.

[0072] The data sending method provided in the embodiments of the present application is described in detail below through some embodiments and their application scenarios in conjunction with the accompanying drawings.

[0073] Reference Figure 2 , the embodiment of the present application provides a data sending method, such as Figure 2 As shown, the data sending method includes:

[0074] Step 201: The terminal performs a first operation;

[0075] Step 202: When the terminal is in an idle state or an inactive state, the terminal sends target data on a first bandwidth part BWP based on a first operation;

[0076] The first BWP is an initial uplink BWP configured by a network-side device for a reduced capability (RedCap) terminal, and the first operation includes at least one of the following:

[0077] Physical uplink shared channel mapping based on the first synchronization signal block (Synchronization Signal and PBCH block, SSB) and configuration authorization;

[0078] Determining whether a timing advance (TA) used to configure an authorized physical uplink shared channel is valid based on a target object, wherein the target object is a second SSB or a target tracking reference signal (TRS);

[0079] A target control resource set (CORESET) for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space (SS) for monitoring a physical downlink control channel (PDCCH).

[0080] In this embodiment of the present application, a reduced-capability terminal may be referred to as a RedCap UE. The aforementioned first BWP may also be understood as the initial UL BWP provided by the initialUplinkBWP in the UplinkConfigCommonRedCapSIB, or as a separate initial UL BWP. Furthermore, the initial downlink (DL) BWP provided by the initialDownlinkBWP in the DownlinkConfigCommonRedCapSIB may be referred to as a separate initial DL BWP.

[0081] It should be understood that when the network-side device additionally configures a separate initial UL BWP for the RedCap UE, a cell will simultaneously have two initial uplink BWPs, namely the initial UL BWP and the separate initial ULBWP. The RedCap UE clarifies the mapping of the SSB and the CG PUSCH through the first operation, determines the validity of the timing advance used by the CG PUSCH, and at least one item in the target control resource set used for target data transmission, thereby enabling the RedCap UE to support small data transmission based on CG scheduling in the RRC inactive or idle state, that is, to transmit small data on the separate initial UL BWP. This can reduce power consumption of the RedCap UE and save signaling overhead.

[0082] In an embodiment of the present application, a terminal performs a first operation; when the terminal is in an idle state or an inactive state, the terminal transmits target data on a first bandwidth part BWP based on the first operation; wherein the first BWP is the initial uplink BWP configured by the network-side device for the reduced-capability terminal, and the first operation includes at least one of the following: mapping the first synchronization signal block SSB with the configured authorized physical uplink shared channel; determining whether the timing advance used for the configured authorized physical uplink shared channel is valid based on the target object, the target object being the second SSB or the target tracking reference signal; determining the target control resource set for target data transmission, the target control resource set being the control resource set associated with the dedicated search space for monitoring the physical downlink control channel PDCCH. In this way, the terminal can implement small data transmission based on CG scheduling in the RRC inactive or idle state, thereby reducing the power consumption of the terminal and saving signaling overhead.

[0083] Optionally, in some embodiments, the first SSB satisfies at least one of the following:

[0084] The first SSB is a cell definition (Cell Defining, CD) SSB or a non-cell definition (Non Cell Definition, NCD) SSB;

[0085] The first SSB is determined based on a first preset rule.

[0086] In the embodiment of the present application, the cell-defined SSB may also be referred to as CD-SSB, and the non-cell-defined SSB may also be referred to as NCD-SSB. Among them, CD-SSB refers to the SSB used by the terminal to obtain System Information Block 1 (System Information Block 1, SIB1), or CD-SSB refers to the SSB that provides a control resource set for the PDCCH common search space (Common Search Space, CSS) of type 0 (Type 0). NCD-SSB refers to the SSB that the terminal does not use to obtain SIB1, or NCD-SSB refers to the SSB that does not provide a control resource set for the PDCCH CSS of type 0.

[0087] It should be understood that the first SSB being CD-SSB or NCD-SSB can be understood as: the first SSB defaults to CD-SSB, or the first SSB defaults to NCD-SSB.

[0088] It should be noted that when the first SSB is CD-SSB, RedCap UEs do not rely on NCD-SSB for small data transmission and are required to use CD-SSB. The mapping of the physical uplink shared channel based on the first synchronization signal block SSB and the configuration grant is similar to the mapping of CD-SSB to RO on the separate initial UL BWP.

[0089] Optionally, the first preset rule includes at least one of the following:

[0090] Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0091] Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB;

[0092] Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP;

[0093] Determine the first SSB according to whether the network side device configures the first object on the first BWP;

[0094] Among them, the first object includes at least one of the following items: a common search space CSS of type 2, a CSS of type 2A, a CSS where the terminal monitors the PDCCH scrambled by the paging radio network temporary identity (Paging-Radio Network Temporary Identity, P-RNTI), and a CSS where the terminal monitors the PDCCH scrambled by the paging early indication radio network temporary identity (Paging Early Indication-Radio Network Temporary Identity, PEI-RNTI).

[0095] In an embodiment of the present application, when determining the first SSB based on whether the network-side device uses a cell-defined SSB, if the network-side device is configured to use a cell-defined SSB, the first SSB is determined to be a cell-defined SSB; otherwise, the first SSB is determined to be a non-cell-defined SSB. When determining the first SSB based on whether the network-side device uses a non-cell-defined SSB, if the network-side device is configured to use a non-cell-defined SSB, the first SSB is determined to be a non-cell-defined SSB; otherwise, the first SSB is determined to be a cell-defined SSB.

[0096] Optionally, when the first preset rule includes determining the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies:

[0097] In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0098] When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0099] In the embodiment of the present application, if the network side device configures the non-cell-defined SSB on the first BWP, it can be understood that the terminal is instructed to send the NCD-SSB by the separate initial DL BWP.

[0100] Optionally, when the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies:

[0101] When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0102] When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0103] In an embodiment of the present application, if the terminal is configured with Type 2 / Type 2ACSS in the separate initial DL BWP and / or the terminal monitors the common search space (CSS) where the PDCCH encrypted by P-RNTI and / or PEI-RNTI is located, the terminal uses NCD-SSB to select the CG PUSCH associated therewith; otherwise, the terminal uses CD-SSB to select the CGPUSCH associated therewith.

[0104] Optionally, in some embodiments, when the first SSB is the non-cell-defined SSB, the first SSB is the SSB defined on the first BWP. That is, in this embodiment of the present application, the non-CD SSB defined on the separate initial DLBWP is used for mapping with the CG PUSCH.

[0105] It should be noted that whether CD-SBB is configured on the first BWP can be understood or replaced by whether CD-SBB is included on the first BWP. Whether non-CD-SBB is configured on the first BWP can be understood or replaced by whether non-CD-SBB is included on the first BWP. The SSB defined on the first BWP can be understood or replaced by the SSB included on the first BWP.

[0106] Optionally, in some embodiments, the second SSB satisfies at least one of the following:

[0107] The second SSB is a cell-defined SSB or a non-cell-defined SSB;

[0108] The second SSB is determined based on a second preset rule.

[0109] Optionally, the second preset rule includes at least one of the following:

[0110] Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0111] Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB;

[0112] Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP;

[0113] Determine the second SSB according to whether the network side device configures the second object on the first BWP;

[0114] Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0115] Optionally, when the second preset rule includes determining the second SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies:

[0116] In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0117] When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0118] In an embodiment of the present application, when it is determined that the second SSB is NCD-SSB, the terminal uses NCD-SSB to determine whether the TA is valid; when it is determined that the second SSB is CD-SSB, the terminal uses CD-SSB to determine whether the TA is valid.

[0119] Optionally, when the second preset rule includes determining the second SSB according to whether the network-side device configures a second object on the first BWP, the second SSB satisfies:

[0120] In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0121] When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0122] In an embodiment of the present application, if the terminal is configured with Type 2 / Type 2ACSS in the separate initial DL BWP and / or the terminal monitors the common search space (CSS) where the PDCCH encrypted by P-RNTI and / or PEI-RNTI is located, the terminal uses NCD-SSB for TA validity verification; otherwise, the terminal uses CD-SSB for TA validity verification.

[0123] Optionally, when the second SSB is the SSB defined by the non-cell, the second SSB is the SSB defined on the first BWP.

[0124] Optionally, in some embodiments, the target tracking reference signal is a tracking reference signal configured by the network side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network side device.

[0125] In the embodiment of the present application, a non-capability-reduced terminal can be understood as a normal terminal. It should be noted that the second BWP can be called an initial UL BWP. When the network-side device does not configure a separate initial UL BWP, the initial UL BWP can also be used by a RedCap terminal.

[0126] Optionally, in some embodiments, the target control resource set satisfies at least one of the following:

[0127] The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal;

[0128] The target control resource set is determined based on a target BWP, where the target BWP is the BWP of the terminal before radio resource control (RRC release) is released;

[0129] When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

[0130] Optionally, the target CORESET is a CORESET defined on the target BWP. For example, if the UE is in an initial DL BWP before RRC release, the target CORESET is the CORESET defined in the initial BWP; if the UE is in a separate initial DL BWP before RRC release, the target CORESET is the CORESET defined in the separate initial BWP.

[0131] It should be understood that when there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set can be the control resource set defined on the BWP indicated by the network side device, or the BWP can be the initial DL BWP or the separate initial DL BWP.

[0132] Optionally, when the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following:

[0133] In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP;

[0134] In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

[0135] In the embodiment of the present application, for non-RedCap UE, the target CORESET must be the CORESET defined on the initial DL BWP. For RedCap UE, the target CORESET can be the CORESET defined on the initial DL BWP or separate initial DL BWP.

[0136] Optionally, in some embodiments, when the type of the terminal is a reduced-capability terminal and the network-side device configures the first BWP for the terminal, the target control resource set is a control resource set defined on the first BWP.

[0137] In the embodiment of the present application, if the network side device is configured with a separate initial DL BWP, the target CORESET must be the CORESET defined on the separate initial DL BWP.

[0138] Optionally, in some embodiments, when the terminal is a reduced-capability terminal and the cell where the terminal is located is time division duplex, the data transmission by the terminal satisfies any one of the following conditions:

[0139] During data transmission, the terminal does not expect radio frequency retuning;

[0140] During data transmission, the terminal does not expect the central frequencies of uplink transmission and downlink reception to be inconsistent;

[0141] During data transmission, the terminal expects that the center frequencies of uplink transmission and downlink reception are consistent.

[0142] Reference Figure 3 , an embodiment of the present application further provides a data receiving method, comprising:

[0143] Step 301: The network-side device performs a first operation;

[0144] Step 302: The network-side device receives target data from the terminal on the first bandwidth part BWP based on the first operation;

[0145] The terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by a network-side device for the terminal with reduced capability, and the first operation includes at least one of the following:

[0146] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0147] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0148] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0149] Optionally, the first SSB satisfies at least one of the following:

[0150] The first SSB is a cell-defined SSB or a non-cell-defined SSB;

[0151] The first SSB is determined based on a first preset rule.

[0152] Optionally, the first preset rule includes at least one of the following:

[0153] Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0154] Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB;

[0155] Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP;

[0156] Determine the first SSB according to whether the network side device configures the first object on the first BWP;

[0157] Among them, the first object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0158] Optionally, when the first preset rule includes determining the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies:

[0159] In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0160] When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0161] Optionally, when the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies:

[0162] When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0163] When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0164] Optionally, when the first SSB is the SSB defined for the non-cell, the first SSB is the SSB defined on the first BWP.

[0165] Optionally, the second SSB satisfies at least one of the following:

[0166] The second SSB is a cell-defined SSB or a non-cell-defined SSB;

[0167] The second SSB is determined based on a second preset rule.

[0168] Optionally, the second preset rule includes at least one of the following:

[0169] Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0170] Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB;

[0171] Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP;

[0172] Determine the second SSB according to whether the network side device configures the second object on the first BWP;

[0173] Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0174] Optionally, when the second preset rule includes determining the second SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies:

[0175] In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0176] When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0177] Optionally, when the second preset rule includes determining the second SSB according to whether the network-side device configures a second object on the first BWP, the second SSB satisfies:

[0178] In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0179] When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0180] Optionally, when the second SSB is the SSB defined by the non-cell, the second SSB is the SSB defined on the first BWP.

[0181] Optionally, the second SSB and the first SSB are both cell-defined SSBs or non-cell-defined SSBs.

[0182] Optionally, the target tracking reference signal is a tracking reference signal configured by the network side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network side device.

[0183] Optionally, the target tracking reference signal is a tracking reference signal configured by a network-side device on the first BWP or the second BWP for an idle or inactive terminal.

[0184] Optionally, the target control resource set satisfies at least one of the following:

[0185] The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal;

[0186] The target control resource set is determined based on a target BWP, where the target BWP is the BWP where the terminal is located before radio resource control is released;

[0187] When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

[0188] Optionally, when the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following:

[0189] In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP;

[0190] In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

[0191] Optionally, when the type of the terminal is a reduced-capability terminal and the network-side device configures the first BWP for the terminal, the target control resource set is a control resource set defined on the first BWP.

[0192] Optionally, the target control resource set is a control resource set defined on the target BWP.

[0193] The data sending method provided in the embodiment of the present application can be executed by a data sending device. In the embodiment of the present application, the data sending device provided in the embodiment of the present application is described by taking the data sending method executed by the data sending device as an example.

[0194] like Figure 4As shown, the data sending device 400 provided in this embodiment of the present application includes:

[0195] A first execution module 401 is configured to execute a first operation;

[0196] The sending module 402 is configured to send target data on the first bandwidth part BWP based on the first operation when the terminal is in an idle state or an inactive state;

[0197] The first BWP is an initial uplink BWP configured by the network side device for the reduced-capability terminal, and the first operation includes at least one of the following:

[0198] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0199] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0200] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0201] Optionally, the first SSB satisfies at least one of the following:

[0202] The first SSB is a cell-defined SSB or a non-cell-defined SSB;

[0203] The first SSB is determined based on a first preset rule.

[0204] Optionally, the first preset rule includes at least one of the following:

[0205] Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0206] Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB;

[0207] Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP;

[0208] Determine the first SSB according to whether the network side device configures the first object on the first BWP;

[0209] Among them, the first object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0210] Optionally, when the first preset rule includes determining the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies:

[0211] In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0212] When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0213] Optionally, when the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies:

[0214] When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0215] When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0216] Optionally, when the first SSB is the SSB defined for the non-cell, the first SSB is the SSB defined on the first BWP.

[0217] Optionally, the second SSB satisfies at least one of the following:

[0218] The second SSB is a cell-defined SSB or a non-cell-defined SSB;

[0219] The second SSB is determined based on a second preset rule.

[0220] Optionally, the second preset rule includes at least one of the following:

[0221] Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0222] Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB;

[0223] Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP;

[0224] Determine the second SSB according to whether the network side device configures the second object on the first BWP;

[0225] Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0226] Optionally, when the second preset rule includes determining the second SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies:

[0227] In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0228] When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0229] Optionally, when the second preset rule includes determining the second SSB according to whether the network-side device configures a second object on the first BWP, the second SSB satisfies:

[0230] In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0231] When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0232] Optionally, when the second SSB is the SSB defined by the non-cell, the second SSB is the SSB defined on the first BWP.

[0233] Optionally, the second SSB and the first SSB are both cell-defined SSBs or non-cell-defined SSBs.

[0234] Optionally, the target tracking reference signal is a tracking reference signal configured by the network side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network side device.

[0235] Optionally, the target tracking reference signal is a tracking reference signal configured by a network-side device on the first BWP or the second BWP for an idle or inactive terminal.

[0236] Optionally, the target control resource set satisfies at least one of the following:

[0237] The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal;

[0238] The target control resource set is determined based on a target BWP, where the target BWP is the BWP where the terminal is located before radio resource control is released;

[0239] When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

[0240] Optionally, when the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following:

[0241] In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP;

[0242] In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

[0243] Optionally, when the type of the terminal is a reduced-capability terminal and the network-side device configures the first BWP for the terminal, the target control resource set is a control resource set defined on the first BWP.

[0244] Optionally, the target control resource set is a control resource set defined on the target BWP.

[0245] Optionally, when the terminal is a reduced-capability terminal and the cell where the terminal is located is time division duplex, the terminal performs data transmission satisfying any one of the following:

[0246] During data transmission, the terminal does not expect radio frequency retuning;

[0247] During data transmission, the terminal does not expect the central frequencies of uplink transmission and downlink reception to be inconsistent;

[0248] During data transmission, the terminal expects that the center frequencies of uplink transmission and downlink reception are consistent.

[0249] The data receiving method provided in the embodiment of the present application can be executed by a data receiving device. In the embodiment of the present application, the data receiving device provided in the embodiment of the present application is described by taking the data receiving device executing the data receiving method as an example.

[0250] like Figure 5 As shown, the data receiving device 500 provided in this embodiment of the application includes:

[0251] A second execution module 501 is configured to execute a first operation;

[0252] A receiving module 502 is configured to receive target data from a terminal on a first bandwidth part BWP based on the first operation;

[0253] The terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by a network-side device for the terminal with reduced capability, and the first operation includes at least one of the following:

[0254] Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization;

[0255] Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal;

[0256] A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

[0257] Optionally, the first SSB satisfies at least one of the following:

[0258] The first SSB is a cell-defined SSB or a non-cell-defined SSB;

[0259] The first SSB is determined based on a first preset rule.

[0260] Optionally, the first preset rule includes at least one of the following:

[0261] Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0262] Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB;

[0263] Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP;

[0264] Determine the first SSB according to whether the network side device configures the first object on the first BWP;

[0265] Among them, the first object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0266] Optionally, when the first preset rule includes determining the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies:

[0267] In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0268] When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0269] Optionally, when the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies:

[0270] When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0271] When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0272] Optionally, when the first SSB is the SSB defined for the non-cell, the first SSB is the SSB defined on the first BWP.

[0273] Optionally, the second SSB satisfies at least one of the following:

[0274] The second SSB is a cell-defined SSB or a non-cell-defined SSB;

[0275] The second SSB is determined based on a second preset rule.

[0276] Optionally, the second preset rule includes at least one of the following:

[0277] Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0278] Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB;

[0279] Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP;

[0280] Determine the second SSB according to whether the network side device configures the second object on the first BWP;

[0281] Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0282] Optionally, when the second preset rule includes determining the second SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies:

[0283] In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0284] When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0285] Optionally, when the second preset rule includes determining the second SSB according to whether the network-side device configures a second object on the first BWP, the second SSB satisfies:

[0286] In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0287] When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0288] Optionally, when the second SSB is the SSB defined by the non-cell, the second SSB is the SSB defined on the first BWP.

[0289] Optionally, the second SSB and the first SSB are both cell-defined SSBs or non-cell-defined SSBs.

[0290] Optionally, the target tracking reference signal is a tracking reference signal configured by the network side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network side device.

[0291] Optionally, the target tracking reference signal is a tracking reference signal configured by a network-side device on the first BWP or the second BWP for an idle or inactive terminal.

[0292] Optionally, the target control resource set satisfies at least one of the following:

[0293] The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal;

[0294] The target control resource set is determined based on a target BWP, where the target BWP is the BWP where the terminal is located before radio resource control is released;

[0295] When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

[0296] Optionally, when the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following:

[0297] In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP;

[0298] In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

[0299] Optionally, when the type of the terminal is a reduced-capability terminal and the network-side device configures the first BWP for the terminal, the target control resource set is a control resource set defined on the first BWP.

[0300] Optionally, the target control resource set is a control resource set defined on the target BWP.

[0301] The data sending device and the data receiving device in the embodiments of the present application can be electronic devices, such as electronic devices with an operating system, or components in electronic devices, such as integrated circuits or chips. The electronic device can be a terminal or other devices 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 be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0302] The data sending device and data receiving device provided in the embodiments of the present application can achieve Figures 2 to 3 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0303] Optional, such as Figure 6As shown, an embodiment of the present application further provides a communication device 600, including a processor 601 and a memory 602, wherein the memory 602 stores a program or instruction that can be run on the processor 601. For example, when the communication device 600 is a terminal, the program or instruction, when executed by the processor 601, implements the various steps of the above-mentioned data sending method embodiment and can achieve the same technical effect. When the communication device 600 is a network-side device, the program or instruction, when executed by the processor 601, implements the various steps of the above-mentioned data receiving method embodiment and can achieve the same technical effect. To avoid repetition, they are not described here.

[0304] An embodiment of the present application also provides a terminal, including a processor and a communication interface, the processor is used to perform a first operation; the communication interface is used to send target data on a first bandwidth part BWP based on the first operation when the terminal is in an idle state or an inactive state; wherein the first BWP is the initial uplink BWP configured by the network side device for the reduced capability terminal, and the first operation includes at least one of the following: based on the first synchronization signal block SSB and the configuration authorization physical uplink shared channel mapping; based on the target object, determining whether the time advance used for the configuration authorization physical uplink shared channel is valid, the target object is the second SSB or the target tracking reference signal; determining the target control resource set for sending the target data, the target control resource set is the control resource set associated with the dedicated search space for monitoring the physical downlink control channel PDCCH. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Figure 7 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0305] The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709 and at least some of the components of the processor 710.

[0306] Those skilled in the art will understand that the terminal 700 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 710 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 7 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be repeated here.

[0307] It should be understood that in an embodiment of the present application, the input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042, and the graphics processor 7041 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 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 707 includes a touch panel 7071 and at least one of other input devices 7072. The touch panel 7071 is also called a touch screen. The touch panel 7071 may include two parts: a touch detection device and a touch controller. Other input devices 7072 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.

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

[0309] The memory 709 can be used to store software programs or instructions and various data. The memory 709 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 709 may include a volatile memory or a non-volatile memory, or the memory 709 may include both volatile and non-volatile memories. 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 RAM bus random access memory (DRRAM). The memory 709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0310] Processor 710 may include one or more processing units. Optionally, processor 710 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 processor 710.

[0311] The processor 710 is configured to perform a first operation;

[0312] The radio frequency unit 701 is configured to send target data on the first bandwidth part BWP based on the first operation when the terminal is in an idle state or an inactive state;

[0313] Among them, the first BWP is the initial uplink BWP configured by the network side device for the reduced capability terminal, and the first operation includes at least one of the following: mapping the first synchronization signal block SSB with the configured authorized physical uplink shared channel; determining whether the time advance used for the configured authorized physical uplink shared channel is valid based on the target object, and the target object is the second SSB or the target tracking reference signal; determining the target control resource set for sending target data, and the target control resource set is the control resource set associated with the dedicated search space for monitoring the physical downlink control channel PDCCH.

[0314] The embodiment of the present application performs a first operation; when the terminal is in an idle state or an inactive state, target data is sent on the first bandwidth part BWP based on the first operation; wherein the first BWP is the initial uplink BWP configured by the network side device for the reduced capability terminal, and the first operation includes at least one of the following: mapping the first synchronization signal block SSB with the configured authorized physical uplink shared channel; determining whether the timing advance used for the configured authorized physical uplink shared channel is valid based on the target object, the target object being the second SSB or the target tracking reference signal; determining the target control resource set for target data transmission, the target control resource set being the control resource set associated with the dedicated search space for monitoring the physical downlink control channel PDCCH. In this way, the terminal can implement small data transmission based on CG scheduling in the RRC inactive or idle state, thereby reducing the power consumption of the terminal and saving signaling overhead.

[0315] Optionally, the first SSB satisfies at least one of the following:

[0316] The first SSB is a cell-defined SSB or a non-cell-defined SSB;

[0317] The first SSB is determined based on a first preset rule.

[0318] Optionally, the first preset rule includes at least one of the following:

[0319] Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0320] Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB;

[0321] Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP;

[0322] Determine the first SSB according to whether the network side device configures the first object on the first BWP;

[0323] Among them, the first object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0324] Optionally, when the first preset rule includes determining the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies:

[0325] In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0326] When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0327] Optionally, when the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies:

[0328] When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB;

[0329] When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

[0330] Optionally, when the first SSB is the SSB defined for the non-cell, the first SSB is the SSB defined on the first BWP.

[0331] Optionally, the second SSB satisfies at least one of the following:

[0332] The second SSB is a cell-defined SSB or a non-cell-defined SSB;

[0333] The second SSB is determined based on a second preset rule.

[0334] Optionally, the second preset rule includes at least one of the following:

[0335] Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB;

[0336] Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB;

[0337] Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP;

[0338] Determine the second SSB according to whether the network side device configures the second object on the first BWP;

[0339] Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

[0340] Optionally, when the second preset rule includes determining the second SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies:

[0341] In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0342] When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0343] Optionally, when the second preset rule includes determining the second SSB according to whether the network-side device configures a second object on the first BWP, the second SSB satisfies:

[0344] In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB;

[0345] When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

[0346] Optionally, when the second SSB is the SSB defined by the non-cell, the second SSB is the SSB defined on the first BWP.

[0347] Optionally, the second SSB and the first SSB are both cell-defined SSBs or non-cell-defined SSBs.

[0348] Optionally, the target tracking reference signal is a tracking reference signal configured by the network side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network side device.

[0349] Optionally, the target tracking reference signal is a tracking reference signal configured by a network-side device on the first BWP or the second BWP for an idle or inactive terminal.

[0350] Optionally, the target control resource set satisfies at least one of the following:

[0351] The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal;

[0352] The target control resource set is determined based on a target BWP, where the target BWP is the BWP where the terminal is located before radio resource control is released;

[0353] When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

[0354] Optionally, when the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following:

[0355] In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP;

[0356] In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

[0357] Optionally, when the type of the terminal is a reduced-capability terminal and the network-side device configures the first BWP for the terminal, the target control resource set is a control resource set defined on the first BWP.

[0358] Optionally, the target control resource set is a control resource set defined on the target BWP.

[0359] Optionally, when the terminal is a reduced-capability terminal and the cell where the terminal is located is time division duplex, the terminal performs data transmission satisfying any one of the following:

[0360] During data transmission, the terminal does not expect radio frequency retuning;

[0361] During data transmission, the terminal does not expect the central frequencies of uplink transmission and downlink reception to be inconsistent;

[0362] During data transmission, the terminal expects that the center frequencies of uplink transmission and downlink reception are consistent.

[0363] An embodiment of the present application also provides a network-side device, including a processor and a communication interface, the processor being configured to execute a first operation, and the communication interface being configured to receive target data from a terminal on a first bandwidth part BWP based on the first operation; wherein the terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by the network-side device for the reduced-capability terminal, and the first operation includes at least one of the following: mapping the first synchronization signal block SSB with the configured authorized physical uplink shared channel; determining whether the timing advance used for the configured authorized physical uplink shared channel is valid based on the target object, the target object being a second SSB or a target tracking reference signal; determining a target control resource set for sending target data, the target control resource set being a control resource set associated with a dedicated search space for monitoring a physical downlink control channel PDCCH. 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 effect.

[0364] Specifically, the embodiment of the present application also provides a network side device. Figure 8 As shown, network-side device 800 includes an antenna 801, a radio frequency device 802, a baseband device 803, a processor 804, and a memory 805. Antenna 801 is connected to radio frequency device 802. In the uplink direction, radio frequency device 802 receives information via antenna 801 and sends the received information to baseband device 803 for processing. In the downlink direction, baseband device 803 processes the information to be transmitted and sends it to radio frequency device 802. Radio frequency device 802 processes the received information and then sends it through antenna 801.

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

[0366] The baseband device 803 may include, for example, at least one baseband board, on which a plurality of chips are arranged, such as Figure 8 As shown, one of the chips is, for example, a baseband processor, which is connected to the memory 805 via a bus interface to call the program in the memory 805 to execute the network device operations shown in the above method embodiment.

[0367] The network side device may further include a network interface 806, which is, for example, a common public radio interface (CPRI).

[0368] Specifically, the network side device 800 of the embodiment of the present invention further includes: instructions or programs stored in the memory 805 and executable on the processor 804, and the processor 804 calls the instructions or programs in the memory 805 to execute. Figure 5 The methods executed by the modules shown achieve the same technical effects, so they will not be described here to avoid repetition.

[0369] 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 data sending method or data receiving method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0370] 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.

[0371] 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 data sending method or data receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0372] 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.

[0373] 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 data sending method or data receiving method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0374] An embodiment of the present application further provides a communication system, including: a terminal and a network-side device, wherein the terminal can be used to execute the steps of the data sending method described above, and the network-side device can be used to execute the steps of the data receiving method described above.

[0375] 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 statement "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 noted 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.

[0376] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in each embodiment of the present application.

[0377] 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 without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this application.

Claims

1. A data transmission method, characterized in that: include: The terminal performs a first operation; When the terminal is in an idle state or an inactive state, the terminal sends target data on a first bandwidth part BWP based on a first operation; The first BWP is an initial uplink BWP configured by the network side device for the reduced-capability terminal, and the first operation includes at least one of the following: Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization; Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal; A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

2. The method according to claim 1, characterized in that The first SSB satisfies at least one of the following: The first SSB is a cell-defined SSB or a non-cell-defined SSB; The first SSB is determined based on a first preset rule.

3. The method according to claim 2, wherein the first preset rule comprises at least one of the following: Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB; Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB; Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP; Determine the first SSB according to whether the network side device configures the first object on the first BWP; Among them, the first object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

4. The method according to claim 3, characterized in that In a case where the first preset rule includes determining the first SSB based on whether the network-side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies: In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB; When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

5. The method according to claim 3, characterized in that In the case where the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies: When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB; When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

6. The method according to claim 2, characterized in that In the case where the first SSB is the non-cell-defined SSB, the first SSB is the SSB defined on the first BWP.

7. The method according to claim 1, characterized in that The second SSB satisfies at least one of the following: The second SSB is a cell-defined SSB or a non-cell-defined SSB; The second SSB is determined based on a second preset rule.

8. The method according to claim 7, characterized in that The second preset rule includes at least one of the following: Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB; Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB; Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP; Determine the second SSB according to whether the network side device configures the second object on the first BWP; Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

9. The method according to claim 8, characterized in that In the case where the second preset rule includes determining the second SSB based on whether the network-side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies: In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB; When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

10. The method according to claim 8, characterized in that In the case where the second preset rule includes determining the second SSB according to whether the network-side device configures the second object on the first BWP, the second SSB satisfies: In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB; When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

11. The method according to claim 7, characterized in that In the case where the second SSB is the non-cell-defined SSB, the second SSB is the SSB defined on the first BWP.

12. The method according to claim 1, characterized in that The second SSB and the first SSB are both cell-defined SSBs or non-cell-defined SSBs.

13. The method according to claim 1, wherein The target tracking reference signal is a tracking reference signal configured by a network-side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network-side device.

14. The method according to claim 13, wherein: The target tracking reference signal is a tracking reference signal configured by a network-side device for an idle or inactive terminal on the first BWP or the second BWP.

15. The method according to claim 1, wherein The target control resource set satisfies at least one of the following: The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal; The target control resource set is determined based on a target BWP, where the target BWP is the BWP where the terminal is located before radio resource control is released; When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

16. The method according to claim 15, characterized in that In a case where the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following: In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP; In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

17. The method according to claim 16, characterized in that In a case where the type of the terminal is a reduced-capability terminal and the network-side device configures the first BWP for the terminal, the target control resource set is a control resource set defined on the first BWP.

18. The method according to claim 15, characterized in that The target control resource set is a control resource set defined on the target BWP.

19. The method according to claim 1, wherein When the terminal is a reduced-capability terminal and the cell where the terminal is located uses time division duplex, the terminal performs data transmission satisfying any of the following conditions: During data transmission, the terminal does not expect radio frequency retuning; During data transmission, the terminal does not expect the central frequencies of uplink transmission and downlink reception to be inconsistent; During data transmission, the terminal expects that the center frequencies of uplink transmission and downlink reception are consistent.

20. A data receiving method, characterized in that: include: The network side device performs a first operation; The network side device receives target data from the terminal on the first bandwidth part BWP based on the first operation; The terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by a network-side device for the terminal with reduced capability, and the first operation includes at least one of the following: Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization; Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal; A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

21. The method according to claim 20, characterized in that The first SSB satisfies at least one of the following: The first SSB is a cell-defined SSB or a non-cell-defined SSB; The first SSB is determined based on a first preset rule.

22. The method according to claim 21, wherein the first preset rule comprises at least one of the following: Determine the first SSB based on whether the network-side device configuration uses the cell-defined SSB; Determine the first SSB based on whether the network side device configuration uses a non-cell defined SSB; Determine the first SSB according to whether the network side device configures a non-cell-defined SSB on the first BWP; Determine the first SSB according to whether the network side device configures the first object on the first BWP; Among them, the first object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

23. The method according to claim 22, characterized in that In a case where the first preset rule includes determining the first SSB based on whether the network-side device configures a non-cell-defined SSB on the first BWP, the first SSB satisfies: In a case where a non-cell-defined SSB is configured on the first BWP, the first SSB is a non-cell-defined SSB; When a non-cell-defined SSB is not configured on the first BWP, the first SSB is a cell-defined SSB.

24. The method according to claim 22, characterized in that In the case where the first preset rule includes determining the first SSB based on whether the network-side device configures the first object on the first BWP, the first SSB satisfies: When the first object is configured on the first BWP, the first SSB is a non-cell-defined SSB; When the first object is not configured on the first BWP, the first SSB is a cell-defined SSB.

25. The method according to claim 20, wherein The second SSB satisfies at least one of the following: The second SSB is a cell-defined SSB or a non-cell-defined SSB; The second SSB is determined based on a second preset rule.

26. The method according to claim 25, characterized in that The second preset rule includes at least one of the following: Determine the second SSB based on whether the network-side device configuration uses the cell-defined SSB; Determine the second SSB based on whether the network-side device configuration uses a non-cell-defined SSB; Determine the second SSB based on whether the network side device configures a non-cell-defined SSB on the first BWP; Determine the second SSB according to whether the network side device configures the second object on the first BWP; Among them, the second object includes at least one of the following: common search space CSS of type 2, CSS of type 2A, CSS where the terminal monitors the PDCCH scrambled by the paging wireless network temporary identifier, and CSS where the terminal monitors the PDCCH scrambled by the paging early indication wireless network temporary identifier.

27. The method according to claim 26, characterized in that In the case where the second preset rule includes determining the second SSB based on whether the network-side device configures a non-cell-defined SSB on the first BWP, the second SSB satisfies: In a case where a non-cell-defined SSB is configured on the first BWP, the second SSB is a non-cell-defined SSB; When a non-cell-defined SSB is not configured on the first BWP, the second SSB is a cell-defined SSB.

28. The method according to claim 26, characterized in that In the case where the second preset rule includes determining the second SSB according to whether the network-side device configures the second object on the first BWP, the second SSB satisfies: In a case where the second object is configured on the first BWP, the second SSB is a non-cell-defined SSB; When the second object is not configured on the first BWP, the second SSB is a cell-defined SSB.

29. The method according to claim 20, characterized in that The target tracking reference signal is a tracking reference signal configured by a network-side device on the first BWP or the second BWP, and the second BWP is an initial uplink BWP configured by the network-side device.

30. The method according to claim 29, wherein The target tracking reference signal is a tracking reference signal configured by a network-side device for an idle or inactive terminal on the first BWP or the second BWP.

31. The method according to claim 20, wherein The target control resource set satisfies at least one of the following: The target control resource set is determined based on the type of the terminal, where the type of the terminal includes a non-reduced capability terminal and a reduced capability terminal; The target control resource set is determined based on a target BWP, where the target BWP is the BWP where the terminal is located before radio resource control is released; When there is no overlap between the index of the control resource set defined on the first BWP and the index of the control resource set defined on the second BWP, the target control resource set is indicated by the network side device, and the second BWP is the initial uplink BWP configured by the network side device.

32. The method according to claim 31, wherein In a case where the target control resource set is determined based on the type of the terminal, the target control resource set satisfies at least one of the following: In a case where the type of the terminal is a non-reduced capability terminal, the target control resource set is a control resource set defined on the second BWP; In a case where the type of the terminal is a reduced-capability terminal, the target control resource set is a control resource set defined on the second BWP or a control resource set defined on the first BWP.

33. A data sending device, characterized in that: include: A first execution module, configured to execute a first operation; a sending module, configured to send target data on the first bandwidth part BWP based on the first operation when the terminal is in an idle state or an inactive state; The first BWP is an initial uplink BWP configured by the network side device for the reduced-capability terminal, and the first operation includes at least one of the following: Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization; Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal; A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

34. A data receiving device, characterized in that: include: A second execution module, configured to execute the first operation; A receiving module, configured to receive target data from a terminal on a first bandwidth part BWP based on the first operation; The terminal is in an idle state or an inactive state, the first BWP is an initial uplink BWP configured by a network-side device for the terminal with reduced capability, and the first operation includes at least one of the following: Physical uplink shared channel mapping based on the first synchronization signal block SSB and the configuration authorization; Determining whether a timing advance used to configure an authorized physical uplink shared channel is valid based on a target object, where the target object is a second SSB or a target tracking reference signal; A target control resource set for sending target data is determined, where the target control resource set is a control resource set associated with a dedicated search space for monitoring a physical downlink control channel (PDCCH).

35. A terminal, characterized in that: The method comprises 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 data sending method according to any one of claims 1 to 19 are implemented.

36. A network side device, characterized in that: The method comprises 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 data receiving method according to any one of claims 20 to 32 are implemented.

37. A readable storage medium, characterized in that The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the data sending method according to any one of claims 1 to 19, or implements the steps of the data receiving method according to any one of claims 20 to 32.

Images