Uplink transmission sending method and apparatus

Abstract

Embodiments of the present application provide an uplink transmission sending method and apparatus. The method comprises: a terminal device receives a first media access control control element (MAC CE) which is sent by a first distributed unit (DU) and comprises candidate configuration information; the terminal device uses an available configured grant (CG) occasion or uses a dynamic grant (DG) to send uplink transmission to a cell associated with the candidate configuration information. According to the embodiments of the present application, a terminal device can use an appropriate uplink grant to send uplink transmission, thereby ensuring the successful completion of LTM cell handover, and improving the network performance.

Description

Uplink transmission sending method and device Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] The PUSCH (Physical Uplink Shared Channel) can be scheduled by the DCI (Downlink Control Information) on the PDCCH (Physical Downlink Control Channel). The network device uses the uplink grant on the DCI to schedule the initial transmission of each uplink transmission. Alternatively, the PUSCH can provide a configured grant (CG) via the RRC (Radio Resource Control) protocol. Currently, the following two operations are supported:

[0003] Type-2: The first PUSCH is triggered by DCI, and subsequent PUSCH transmissions follow the RRC configuration and the scheduling received from the DCI;

[0004] Type-1: PUSCH is triggered by the arrival of buffered data sent by the terminal device, and the transmission of this PUSCH follows the RRC configuration.

[0005] For shared spectrum channel access, the terminal device can retransmit on the CG. To handle possible LBT (listen before talk) failures on the CG, a CG retransmission timer can be configured to ensure autonomous retransmission. When the CG retransmission timer is configured, the terminal device will automatically select the HARQ (Hybrid Automatic Repeat-reQuest) process for each CG resource.

[0006] For cell-level scheduling, CS-RNTI (Configured Scheduling RNTI) is a unique terminal device identifier used for downlink SPS (Semi-Persistent Scheduling) and uplink CG.

[0007] For a BWP (Bandwidth Part) of a serving cell, a terminal device can be configured with up to 12 activated CGs. When multiple CGs are configured, the network side decides which (including all) CGs to activate at a time. For Type-2, each CG is activated separately using a DCI command, and one DCI can be used to deactivate one or more CGs.

[0008] When SUL (Supplementary Uplink) is configured, the network side needs to ensure that an activated CG on the SUL does not overlap in time with another activated CG on another UL configuration.

[0009] For dynamic grant (DG) and CG Type-2, the number of repetitions can also be dynamically indicated in L1 signaling. If the number of repetitions also exists in RRC, the dynamically indicated number of repetitions overrides the number of repetitions configured in RRC.

[0010] To improve NR (New Radio) uplink coverage, both dynamically granted and configured granted PUSCH transmissions support multi-slot aggregation enhancement with TB (Transport Block) repetition.

[0011] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0012] Summary of the Invention

[0013] The inventors discovered that during the Layer 1 / L2 Triggered Mobility (LTM) process, when a network device sends a MAC CE triggering a cell handover, the terminal device switches to the target cell based on the indicated candidate configuration index and applies the corresponding configuration. Furthermore, when the terminal device sends its first uplink transmission in the target cell, such as an RRC Reconfiguration Complete message, if no random access procedure has been performed, the LTM execution is considered complete when the terminal device determines that the network has successfully received its first uplink transmission.

[0014] According to the current discussion, either dynamic grant or configured grant can be used for the first uplink transmission of the terminal device in the target cell during the LTM process. In the case of dynamic grant, it is assumed that the source DU (Distributed Unit) informs the target DU of the selected beam so that the target DU can start dynamically scheduling UL grant; in the case of configured grant, the terminal device selects the configured grant opportunity associated with the beam indicated in the LTM MAC CE.

[0015] However, the configured grant includes one or more uplink grants, and the terminal device needs to confirm the uplink grant that can be used for the first uplink transmission of the terminal in the target cell during the LTM process. There is currently no solution to this problem.

[0016] In response to at least one of the above problems or other similar problems, an embodiment of the present application provides a method and apparatus for sending uplink transmission, so that a terminal device can use appropriate authorization for uplink transmission, thereby ensuring successful completion of LTM cell switching.

[0017] According to one aspect of an embodiment of the present application, a sending device for uplink transmission is configured in a terminal device, wherein the device includes:

[0018] a receiving unit configured to receive a MAC CE (Media Access Control Element) including candidate configuration information sent by a first DU (Distributed Unit);

[0019] A sending unit, which uses an available CG occasion (configured grant opportunity) or a DG (dynamic grant) to send uplink transmission to the cell associated with the candidate configuration information.

[0020] According to another aspect of an embodiment of the present application, there is provided an apparatus for receiving uplink transmission, configured in a network device, wherein the apparatus includes:

[0021] A sending unit, which sends a first MAC CE (Media Access Control Element) including candidate configuration information to a terminal device at a source DU;

[0022] A receiving unit, which uses an available CG occasion (configured grant opportunity) or a DG (dynamic grant) in a candidate or target DU to receive the uplink transmission sent by the terminal device to the cell associated with the candidate configuration information.

[0023] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, the terminal device can use appropriate uplink authorization to send uplink transmission, thereby ensuring the successful completion of LTM cell switching and improving network performance.

[0024] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0025] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0026] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0028] FIG1 is a schematic diagram of the LTM process;

[0029] FIG2 is a schematic diagram of an inter-cell mobility scenario based on L1 / L2;

[0030] FIG3 is a schematic diagram of the L1 / L2 triggered mobility procedure (LTM) within the gNB-DU;

[0031] FIG4 is a schematic diagram of the L1 / L2 triggered mobility procedure (LTM) between gNB and DU.

[0032] FIG5 is a schematic diagram of a method for sending uplink transmission according to an embodiment of the present application;

[0033] FIG6 is another schematic diagram of the uplink transmission sending method according to an embodiment of the present application;

[0034] FIG7 is a schematic diagram of a method for receiving uplink transmission according to an embodiment of the present application;

[0035] FIG8 is another diagram illustrating the L1 / L2 triggered mobility procedure (LTM) between gNB and DU.

[0036] FIG9 is another schematic diagram of the L1 / L2 triggered mobility procedure (LTM) between gNB and DU.

[0037] FIG10 is a schematic diagram of a transmitting device for uplink transmission according to an embodiment of the present application;

[0038] FIG11 is a schematic diagram of a receiving device for uplink transmission according to an embodiment of the present application;

[0039] FIG12 is a schematic diagram of a communication system according to an embodiment of the present application;

[0040] FIG13 is a schematic diagram of a network device according to an embodiment of the present application;

[0041] FIG14 is a schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0042] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0043] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0044] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0045] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0046] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and 5G, New Radio (NR), etc., and / or other communication protocols currently known or to be developed in the future.

[0047] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0048] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays or low-power nodes (e.g., femeto, pico, etc.), IAB (Integrated Access and Backhaul) nodes, IAB-DUs, or IAB-donors. The term "base station" may include some or all of these functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which it is used. The terms "cell" and "base station" are interchangeable to avoid confusion.

[0049] In the embodiments of the present application, the term "user equipment" (UE) or "terminal equipment" (TE) refers to, for example, a device that accesses a communication network through a network device and receives network services. A terminal device can be fixed or mobile and may also be referred to as a mobile station (MS), a terminal, a subscriber station (SS), an access terminal (AT), an IAB-MT (Mobile Terminal), a station, and so on.

[0050] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, etc.

[0051] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0052] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0053] FIG1 is a schematic diagram of the LTM process. As shown in FIG1 , the process includes the following steps:

[0054] 1. The UE sends a MeasurementReport message to the gNB, where the gNB-CU decides to use LTM and initiates candidate cell preparation.

[0055] 2. The gNB sends an RRCReconfiguration message to the UE, including the LTM candidate cell configuration of one or more candidate cells.

[0056] 3. The UE stores the LTM candidate cell configuration and sends an RRCReconfigurationComplete message to the gNB.

[0057] 4a / 4b. Before receiving the cell handover command, the UE may perform DL (Downlink, downlink, referred to as downlink) synchronization and TA (Timing Advance, timing advance) acquisition of the candidate cell;

[0058] 5. The UE performs L1 measurements on the configured candidate cells and sends a low-layer measurement report to the gNB.

[0059] Note: The order of DL / UL (Uplink) synchronization and L1 measurement is not yet defined and can be changed.

[0060] 6. The gNB decides to perform a cell handover to the target cell and sends a MAC CE (MAC Control Element) triggering a cell handover LTM command by including the candidate configuration index of the target cell. The UE switches to the configuration of the target cell.

[0061] 7. If the cell handover requires the execution of a random access procedure, the UE performs a random access procedure to the target cell;

[0062] 8. The UE indicates the completion of the cell handover to the target cell.

[0063] The UE may perform steps 4-8 multiple times based on the configuration provided in step 2 for subsequent LTM cell handovers.

[0064] FIG2 is a schematic diagram of an inter-cell mobility scenario based on L1 / L2 according to an embodiment of the present application.

[0065] As shown in Figure 2, in an embodiment of the present application, when a terminal moves from the coverage area of ​​one cell to the coverage area of ​​another cell, an L1 / L2-triggered serving cell change needs to be performed at some point. According to the discussion, the scenarios supported by L1 / L2-based inter-cell mobility include: Inter-DU scenario, Intra-DU scenario, handover scenario, Carry-over scenario, NR-DC scenario, inter-frequency scenario, etc.

[0066] In both Inter-DU and Intra-DU scenarios, the designs of intra-DU and inter-DU L1 / L2-based mobility should share as much commonality as possible under reasonable circumstances.

[0067] In handover scenarios, handover refers to the mobility / change of the PCell, which involves both non-CA (i.e., PCell only) and CA scenarios (i.e., PCell and SCell(s)). It includes:

[0068] The target PCell / target SCell(s) is not the current serving cell (i.e., CA→CA scenario with PCell change), such as the LTM from B to D in the scenario shown in Figure 2;

[0069] The target PCell is a current SCell, such as the LTM from B to C in the scenario shown in Figure 4; and

[0070] The target SCell is the current PCell, for example, the LTM from A to B in the scenario shown in FIG4 .

[0071] In the CA scenario, PCell changes without SCell changes and PCell changes with SCell changes are supported.

[0072] In the NR-DC scenario, PSCell changes that do not involve the MN (i.e., intra-SN) are supported.

[0073] In the inter-frequency scenario, which includes mobility to an inter-frequency cell other than the current serving cell, inter-frequency L1 measurement is supported if feasible.

[0074] In the above scenarios, the source cell and the target cell may be synchronous or asynchronous, and may operate in FR1 or FR2.

[0075] Figure 3 illustrates the intra-gNB-DU (intra-DU) L1 / L2-triggered mobility procedure (LTM), showing the scenario where a UE moves within the same gNB-CU and the same gNB-DU. As shown in Figure 3, when a UE moves within the same gNB-DU, the procedure includes:

[0076] 1. The UE sends a MeasurementReport message containing neighbor cell measurements to the gNB-DU. The gNB-DU sends an UL RRC MESSAGE TRANSFER message carrying the received MeasurementReport message to the gNB-CU.

[0077] 2. The gNB-CU decides on the configuration for initiating L1 / L2 triggered mobility.

[0078] 3. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the gNB-DU, including the target candidate cell.

[0079] 4. If the LTM configuration request is accepted, the gNB-DU responds to the gNB-CU with a UE CONTEXT MODIFICATION RESPONSE message including the generated lower layer RRC configuration of the accepted candidate cell.

[0080] 5. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the gNB-DU, including a generated RRCReconfiguration message carrying the L1 / L2 triggered mobility configuration. FFS: Whether it is a DL RRC MESSAGE TRANSFER message or a UE CONTEXT MODIFICATION REQUEST message.

[0081] 6. The gNB-DU passes the received RRCReconfiguration message to the UE.

[0082] 7. The UE responds to the gNB-DU with an RRCReconfigurationComplete message.

[0083] 8. The gNB-DU transmits the RRCReconfigurationComplete message to the gNB-CU via a UL RRC MESSAGE TRANSFER message. FFS: Whether this is a UL RRC MESSAGE TRANSFER message or a UE CONTEXT MODIFICATION RESPONSE message.

[0084] 9. The UE sends lower layer measurement results to the gNB-DU. The gNB-DU decides to perform L1 / L2 inter-cell mobility.

[0085] 10. The gNB-DU sends an LTM command to the UE.

[0086] 11. The gNB-DU sends a UE CONTEXT MODIFICATION REQUIRED message to the gNB-CU to indicate the initiation of an L1 / L2 triggered mobility command to the UE including the target cell ID.

[0087] 12. The gNB-CU responds to the gNB-DU with a UE CONTEXT MODIFICATION CONFIRM message.

[0088] 13.FFS: How does the target gNB-DU detect UE access?

[0089] 14. The gNB-DU sends an Access Success message to the gNB-CU, including the target cell ID.

[0090] 15. The gNB-CU may send a UE Context Modification REQUEST message to the gNB-DU to release the resources of the prepared cell.

[0091] 16. The gNB-DU responds with the UE CONTEXT MODIFICATION RESPONSE message.

[0092] Figure 4 illustrates the inter-gNB-DU (inter-DU) L1 / L2-triggered mobility procedure (LTM), showing the scenario where a UE moves between different gNB-DUs within a gNB-CU. As shown in Figure 4, when the UE moves from one gNB-DU to another within the same gNB-CU, the NR operation for L1 / L2-triggered mobility includes:

[0093] 1. The UE sends a MeasurementReport message containing neighbor cell measurements to the source gNB-DU. The source gNB-DU sends an UL RRC MESSAGE TRANSFER message carrying the received MeasurementReport message to the gNB-CU.

[0094] 2. The gNB-CU decides on the configuration for initiating L1 / L2 triggered mobility.

[0095] 3. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the candidate gNB-DU, including the target candidate cell.

[0096] 4. If the candidate gNB-DU accepts the request for LTM configuration, it responds to the gNB-CU with a UE CONTEXT SETUP RESPONSE message including the generated lower layer RRC configuration of the accepted target candidate cell.

[0097] 5. The gNB-CU sends a DL RRC MESSAGE TRANSFER (FFS or UE CONTEXT MODIFICATION REQUEST) message to the source gNB-DU, including the generated RRCReconfiguration message carrying the L1 / L2 triggered mobility configuration.

[0098] 6. The source gNB-DU passes the received RRCReconfiguration message to the UE.

[0099] 7. The UE responds to the source gNB-DU with an RRCReconfigurationComplete message.

[0100] 8. The source gNB-DU delivers the RRCReconfigurationComplete message to the gNB-CU via the UL RRC MESSAGE TRANSFER (FFS or UE CONTEXT MODIFICATION RESPONSE) message.

[0101] 9. The UE sends the low-layer measurement results to the source gNB-DU.

[0102] 10. The source gNB-DU decides to perform L1 / L2 triggered mobility towards a candidate target cell. The FFS also notifies other nodes of the LTM triggering decision.

[0103] 11. The source gNB-DU sends an LTM command to the UE (this LTM command is updated based on RAN2 discussions).

[0104] 12. The source gNB-DU sends a UE CONTEXT MODIFICATION REQUIRED message to the gNB-CU to indicate the initiation of an L1 / L2 triggered mobility command to the UE including the target cell ID.

[0105] 13. The gNB-CU responds with a UE CONTEXT MODIFICATION CONFIRM message to the source gNB-DU.

[0106] 14.FFS: How does the target gNB-DU detect UE access? Is there any impact on F1?

[0107] 15. The target gNB-DU sends an ACCESS SUCCESS message to the gNB-CU, including the target cell ID.

[0108] 16. The gNB-CU may send a UE CONTEXT RELEASE COMMAND message to the source gNB-DU to release the resources of the prepared cell.

[0109] 17. The source gNB-DU responds with the UE CONTEXT RELESE COMPLETE message.

[0110] In the embodiments of this application, unless otherwise specified, all functions defined for the gNB-DU are also applicable to the IAB-DU and IAB-donor-DU. All functions defined for the gNB-CU are also applicable to the IAB-donor-CU. All functions defined for the UE are also applicable to the IAB-MT. In addition, in the following description, "if," "in the case of," and "when" can be used interchangeably to avoid confusion.

[0111] The embodiments of the present application are described below with reference to the accompanying drawings and specific implementation methods.

[0112] Embodiments of the first aspect

[0113] An embodiment of the present application provides a method for sending uplink transmission, which is described from the side of a terminal device.

[0114] FIG5 is a schematic diagram of a method for sending uplink transmission according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0115] 501: The terminal device receives a first MAC CE (Media Access Control Element) including candidate configuration information sent by a first DU (Distributed Unit);

[0116] 502: The terminal device uses an available CG occasion (configured grant opportunity) or uses DG (dynamic grant) to send uplink transmission to the cell associated with the candidate configuration information.

[0117] It is worth noting that FIG5 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG5 above.

[0118] In the above embodiments, the "first DU" is, for example, the "gNB-DU" in the scenario shown in Figure 3 and / or the "source gNB-DU" in the scenario shown in Figure 4, used to send a cell handover command to the terminal device. This application is not limited thereto. After the terminal device switches to the target gNB-DU, the target gNB-DU also performs relevant configurations on the terminal device. In this case, the "first DU" may also be the "target gNB-DU" in the scenario shown in Figure 4. Similarly, when the first DU is the source gNB-DU, the second DU may be the target gNB-DU.

[0119] In the above embodiment, after receiving the first MACCE including candidate configuration information sent by the first DU, the terminal device can use the available CG opportunity or use the DG (for example, when the CG opportunity is not available or the DG is available) to send an uplink transmission to the cell associated with or corresponding to the candidate configuration information. This solves the problem of how the terminal device selects resources for uplink transmission when the configured authorization includes one or more groups. The method of the embodiment of the present application selects resources for uplink transmission, thereby improving network performance.

[0120] In the above embodiment, the above uplink transmission may be the first uplink transmission of the terminal device in the target cell during the LTM process, such as an RRC reconfiguration completion message, but the present application is not limited thereto.

[0121] In some embodiments, the available CG opportunity is associated with the beam information included in the first MAC CE, such as unified TCI (Transmission Configuration Indication) state information and / or TCI state information and / or uplink spatial filtering information.

[0122] The unified TCI state information is, for example, a joint TCI state ID, or an uplink TCI state ID (UL TCI state ID) and / or a downlink TCI state ID (DL TCI state ID) in a separate TCI state ID, and the like.

[0123] If the above-mentioned beam information is unified TCI state information, the terminal device can send the above-mentioned uplink transmission on the beam corresponding to the joint TCI state ID or UL TCI state ID; or, the terminal device can receive the information of successful reception of the above-mentioned uplink transmission on the beam corresponding to the joint TCI state ID or DL ​​TCI state ID.

[0124] If the above-mentioned beam information is, for example, TCI status information and / or uplink space filtering information, the terminal device can receive the information that the above-mentioned uplink transmission is successfully received on the beam, for example, receiving the information that the above-mentioned uplink transmission is successfully received on the beam corresponding to the TCI status information; or, the terminal device can send the above-mentioned uplink transmission on the beam associated with the above-mentioned uplink space filtering information.

[0125] In other embodiments, the available CG opportunity is associated with a specific RO (Random Access Opportunity), which is, for example, the RO used by the terminal device for random access to obtain early uplink synchronization, namely, TA (Timing Advance).

[0126] In the above embodiment, if the above first MAC CE does not include beam information, or the CG occasion associated with the beam information included in the above first MAC CE is not configured, or the CG occasion associated with the beam information included in the above first MAC CE is invalid, then the above available CG occasion is associated with the specific RO.

[0127] In some further embodiments, the available CG opportunity is associated with a specific RS, which is, for example, the RS associated with the beam information included in the above-mentioned first MAC CE, or the RS associated with the above-mentioned specific RO, or the SSB (Synchronization Signal / PBCH Block) receiving the SIB1 (first system information block), or the RS indicated in the SIB1 or MIB (Master Information Block), and so on.

[0128] In the above embodiment, the RS may be at least one of an SSB, a CSI-RS (Channel State Information-Reference Signal) and an SRS (Sounding Reference Signal), but the present application is not limited thereto.

[0129] The above embodiments are merely exemplary of available CG opportunities, but the present application is not limited thereto, and appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0130] In some embodiments, the terminal device considers that the above-mentioned CG opportunity is available or that there is the above-mentioned available CG opportunity when at least one of the following conditions is met.

[0131] RRC signaling configures the above CG occasion;

[0132] Receive the first MAC CE;

[0133] Receive specific DCI.

[0134] For example, when the terminal device configures the above-mentioned CG occasion through RRC signaling, it considers that the configured CG opportunity is available; for another example, when the terminal device receives the above-mentioned first MAC CE, it considers that the CG opportunity related to the candidate configuration information included in the first MAC CE is available; for another example, when the terminal device receives the above-mentioned specific DCI, it considers that the RRC pre-configured CG opportunity is available, and so on.

[0135] In some implementations, the specific DCI is used to schedule the PDSCH carrying the first MAC CE. That is, when the terminal device receives the DCI for scheduling the PDSCH carrying the first MAC CE, it considers that the RRC pre-configured CG opportunity is available.

[0136] In some implementations, the specific DCI and the first MAC CE are sent or received simultaneously. For example, the network sends the specific DCI and the first MAC CE simultaneously, or the terminal device receives the specific DCI and the first MAC CE simultaneously. Here, "sending or receiving simultaneously" means sending or receiving in the same time unit, such as the same time slot, symbol, or RB (Resource Block).

[0137] In the above embodiment, "available" can also be replaced by "activated", "valid", "initialized" and other similar terms. In the following description, if there is no special explanation, the above similar terms can be used to replace "available".

[0138] The above embodiments illustrate the circumstances under which a terminal device considers a CG opportunity to be available, but the present application is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0139] In some embodiments, the available CG opportunity is on an uplink carrier, where the uplink carrier is, for example, at least one of the following:

[0140] NUL (normal uplink) or SUL (Supplementary uplink) configured with CG;

[0141] NUL or SUL of the CG configured for the LTM process;

[0142] NUL or SUL of the available CG configured for LTM process;

[0143] The uplink carrier used by the terminal device for random access to obtain TA (timing advance);

[0144] the uplink carrier indicated by the first MAC CE;

[0145] The uplink carrier is selected based on the RSRP (Reference Signal Receiving Power / Reference Signal Received Power) of the downlink path loss reference signal.

[0146] For example, if an RSRP threshold is configured and if the RSRP of the downlink path loss reference signal is less than the RSRP threshold, the selected uplink carrier is SUL; otherwise, that is, the RSRP threshold is not configured, or the RSRP of the downlink path loss reference signal is greater than or equal to the RSRP threshold, the selected uplink carrier is NUL.

[0147] The above embodiments only provide exemplary illustrations of the uplink carriers where available CG opportunities are located, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0148] In some embodiments, the uplink transmission carries an RRC reconfiguration complete message, or carries a MAC CE for indicating LTM completion. This application does not limit the name of the MAC CE for indicating LTM completion, for example, it can be called "LTM completion MAC CE", etc.

[0149] In some embodiments, the uplink transmission may be at least one of an initial transmission, a repetition of the initial transmission, and a retransmission, and may be configured by RRC signaling and / or the first MAC CE and / or the DCI for scheduling the PDSCH carrying the first MAC CE.

[0150] In the above embodiment, if the above uplink transmission is a retransmission, the terminal device may introduce a retransmission timer, start the retransmission timer after the initial transmission is sent, and send the above retransmission when the retransmission timer expires.

[0151] In some embodiments, the terminal device may use a HARQ process to send the above-mentioned uplink transmission. The ID of the HARQ process may be determined using an existing calculation formula and parameters, or using a new calculation formula and parameters. For example, for CG type 1, the existing calculation formula and parameters may be reused, referred to as the first calculation formula and first parameters; for another example, for CG type 2, the existing calculation formula and new parameters may be used, referred to as the second calculation formula and second parameters.

[0152] In the above embodiment, the first calculation formula, the second calculation formula and the first parameter can refer to the relevant technology, and the description is omitted here. As for the second parameter, the difference from the existing first parameter is that the SFN in the second parameter is start time , slotstart time and symbolstart time may be respectively the SFN (System Frame Number), slot (time slot) and symbol (symbol) of the first transmission opportunity of the PUSCH when or after the above-mentioned CG occasion is available (including activation or validity or initialization, etc.).

[0153] In some embodiments, the terminal device may further determine whether to use a CG opportunity to send an uplink transmission. For example, if determined, the uplink transmission may be sent using the available CG opportunity. This application does not limit the determination method.

[0154] FIG6 is another schematic diagram of a method for sending uplink transmission according to an embodiment of the present application, and the contents identical to those in the embodiment of FIG5 are not repeated. As shown in FIG6 , the method includes:

[0155] 601: The terminal device receives a first MAC CE including candidate configuration information sent by a first DU;

[0156] 602: The terminal device determines whether to use the CG opportunity to send uplink transmission, and if so, performs operation 603; otherwise, performs operation 604;

[0157] 603: The terminal device uses an available CG occasion to send an uplink transmission to the cell associated with the candidate configuration information;

[0158] 604: The terminal device uses DG to send uplink transmission to the cell associated with the candidate configuration information.

[0159] It is worth noting that FIG6 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG6 above.

[0160] In some embodiments, if the conditions for using CG are met or the conditions for using DG are not met, the terminal device determines to use the CG opportunity to send uplink transmission; conversely, if the conditions for using DG are met or the conditions for using CG are not met, the terminal device determines to use DG to send uplink transmission.

[0161] In the above embodiment, the conditions for using CG include, for example, at least one of the following:

[0162] Configured CG;

[0163] The configured CG is valid or available (or activated or initialized, etc.);

[0164] The time interval related to the reception of the first MAC CE satisfies a first predetermined condition.

[0165] For example, if CG is configured, the terminal device determines to use the CG opportunity to send uplink transmission; for another example, if the configured CG is valid or available, the terminal device determines to use the CG opportunity to send uplink transmission; for another example, if the time interval related to the above-mentioned first MAC CE reception meets the first predetermined condition, the terminal device determines to use the CG opportunity to send uplink transmission.

[0166] In the above embodiment, the first predetermined condition is, for example, that the time interval between the reception of the above-mentioned first MAC CE and the next CGoccasion is less than the configured offset; another example is that after the above-mentioned first MAC CE is received, no PDCCH addressed by C-RNTI (Cell Radio Network Temporary Identifier) ​​is received; another example is that no PDCCH addressed by C-RNTI is received between the reception of the above-mentioned first MAC CE and the next CG occasion.

[0167] In the above embodiment, the conditions for using DG include, for example, at least one of the following:

[0168] The first DU is the DU associated with the candidate configuration information;

[0169] The first DU notifies the second DU terminal device to perform LTM;

[0170] The first DU notifies the second DU of the beam information included in the first MAC CE;

[0171] The time interval related to the reception of the first MAC CE satisfies the second predetermined condition.

[0172] For example, if the first DU is the DU associated with the candidate configuration information, the terminal device determines to use DG to send uplink transmission; for another example, if the first DU notifies the second DU terminal device to perform LTM, the terminal device determines to use DG to send uplink transmission; for another example, if the first DU notifies the second DU of the beam information included in the first MACCE, the terminal device determines to use DG to send uplink transmission; for another example, if the time interval associated with receiving the first MAC CE satisfies a second predetermined condition, the terminal device determines to use DG to send uplink transmission. If the above conditions are not met, the terminal device determines that the conditions for using DG are not met.

[0173] In the above embodiment, the second predetermined condition is, for example: the time interval between the reception of the above-mentioned first MAC CE and the reception of the next C-RNTI-addressed PDCCH is less than the configured offset; another example is: there is no available CG occasion after the reception of the above-mentioned first MAC CE; another example is: there is no available CG occasion between the reception of the above-mentioned first MAC CE and the reception of the next C-RNTI-addressed PDCCH.

[0174] The above embodiments merely illustrate the conditions for using CG and DG, but the present application is not limited thereto. Appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used individually, or one or more of the above embodiments can be combined.

[0175] In some embodiments, the terminal device also receives information indicating that the uplink transmission is successfully received. For example, after the terminal device sends the uplink transmission, the target cell feeds back information indicating that the uplink transmission is successfully received.

[0176] In the above embodiment, the above information may be the RLC ACK of the above uplink transmission, or a PDCCH addressed by a C-RNTI, or a UE contention resolution ID MAC CE, or a MAC CE indicating that the LTM cell handover is completed. This application does not impose any restrictions on this.

[0177] For example, if the CG is used for retransmission (implying that the initial transmission is also through the CG), the above information is the PDCCH addressed by the C-RNTI.

[0178] For another example, if the DG is used for initial transmission or retransmission, the above information is a PDCCH addressed by the C-RNTI, and the above PDCCH schedules a new transmission (for example, a new transmission of another transmission different from the above uplink transmission), or the above PDCCH schedules a new transmission on the above HARQ process ID. That is, if the DG is used for initial transmission or retransmission, and the PDCCH schedules a new transmission or schedules a new transmission on the above HARQ process ID, the above information is a PDCCH addressed by the C-RNTI.

[0179] In the above embodiment, the PDCCH may schedule one of the RLC ACK for the above uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover. In other words, when the above information is a C-RNTI addressed PDCCH, the PDCCH may schedule one of the RLC ACK for the above uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover.

[0180] The above embodiments only illustrate information on successful uplink transmission reception, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0181] The above embodiments are merely exemplary of the methods of the present application, but the present application is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used individually, or one or more of the above embodiments may be combined.

[0182] According to the method of the embodiment of the present application, the problem of how the terminal device selects resources for uplink transmission when the configured authorization includes one group and multiple groups is solved. According to the method of the embodiment of the present application, the resources for uplink transmission are selected, which ensures the successful completion of LTM cell switching and improves network performance.

[0183] Embodiments of the second aspect

[0184] An embodiment of the present application provides a method for receiving uplink transmissions, described from the perspective of a network device. The network device is, for example, the gNB in ​​the scenario shown in FIG3 , including a gNB-DU and a gNB-CU, wherein the gNB-DU implements the function of the first DU in the embodiment of the first aspect. Another example is the gNB shown in FIG4 , including a source gNB-DU, a candidate or target gNB-DU, and a gNB-CU, wherein the source gNB-DU implements the function of the first DU in the embodiment of the first aspect. In the embodiment of the first aspect, the cell associated with the candidate configuration information is located in the candidate or target gNB-DU. The same contents as those in the embodiment of the first aspect are not repeated here.

[0185] FIG7 is a schematic diagram of a method for receiving uplink transmission according to an embodiment of the present application. As shown in FIG7 , the method includes:

[0186] 701: The network device sends a first MAC CE (Media Access Control Element) including candidate configuration information to the terminal device at the source DU;

[0187] 702: The network device uses an available CG occasion (configured grant opportunity) or a DG (dynamic grant) in the candidate or target DU to receive the uplink transmission sent by the terminal device to the cell associated with the candidate configuration information.

[0188] It is worth noting that FIG7 above only schematically illustrates the embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG7 above.

[0189] In some embodiments, the available CG occasion is associated with at least one of the following:

[0190] The beam information included in the first MAC CE;

[0191] The above terminal device is used to obtain the RO used by the TA for random access;

[0192] the RS of the beam information included in the first MAC CE;

[0193] RS of the above RO;

[0194] Specific RS.

[0195] In the above embodiment, the above beam information may include Unified TCI state information and / or TCI state information and / or uplink spatial filtering information.

[0196] The unified TCI state information includes the joint TCI state ID, or the UL TCI state ID and / or DL ​​TCI state ID in the separate TCI state ID.

[0197] When the beam information includes Unified TCI state information, the candidate or target DU of the network device can receive the uplink transmission sent by the terminal device on the beam corresponding to the above-mentioned joint TCI state ID or the above-mentioned UL TCI state ID; and / or, the candidate or target DU of the network device sends the information of successful reception of the above-mentioned uplink transmission to the terminal device on the beam corresponding to the above-mentioned joint TCI state ID or the above-mentioned DL TCI state ID.

[0198] In the case where the beam information includes TCI state information and / or uplink space filtering information, the candidate or target DU of the network device can receive the above-mentioned uplink transmission sent by the terminal device on the beam associated with the above-mentioned uplink space filtering information; and / or, the candidate or target DU of the network device can send information on the successful reception of the above-mentioned uplink transmission to the terminal device on the beam corresponding to the above-mentioned TCI state information.

[0199] In the above embodiment, the available CG occasion associated terminal device for obtaining the RO used for random access performed by the TA includes:

[0200] If the first MAC CE does not include beam information, or the CG occasion associated with the beam information included in the first MAC CE is not configured, or the CG occasion associated with the beam information included in the first MAC CE is invalid, then the available CG occasion is associated with the RO.

[0201] In the above embodiment, the above specific RS may be an SSB for receiving SIB1.

[0202] In the above embodiment, the above specific RS may be an RS indicated in SIB1 or MIB.

[0203] In the above embodiment, the RS includes at least one of the following: SSB, CSI-RS, SRS.

[0204] In some embodiments, when at least one of the following conditions is met, the terminal device considers that the CG occasion is available or there is the available CG occasion:

[0205] RRC signaling configures the CG occasion;

[0206] receiving the first MAC CE;

[0207] Receive specific DCI.

[0208] In some implementations, the specific DCI is used to schedule the PDSCH carrying the first MAC CE.

[0209] In some other implementations, the specific DCI and the first MAC CE are sent or received simultaneously, and sending or receiving simultaneously means sending or receiving in the same time slot, symbol, or RB.

[0210] In some embodiments, the available CG occasion is on an uplink carrier, and the uplink carrier is at least one of the following:

[0211] NUL (Normal Uplink) or SUL (Supplementary Uplink) configured with CG;

[0212] NUL or SUL of the CG configured for the LTM process;

[0213] NUL or SUL of the available CG configured for LTM process;

[0214] An uplink carrier used by the terminal device for random access to obtain TA (timing advance);

[0215] the uplink carrier indicated by the first MAC CE;

[0216] The uplink carrier is selected based on the RSRP of the downlink path loss reference signal.

[0217] For example, if an RSRP threshold is configured, and if the RSRP of the downlink path loss reference signal is less than the RSRP threshold, the selected uplink carrier is SUL; otherwise, the selected uplink carrier is NUL.

[0218] In some embodiments, the uplink transmission carries an RRC reconfiguration completion message, or carries a MAC CE indicating LTM completion.

[0219] In some embodiments, the uplink transmission is at least one of an initial transmission, a repetition of an initial transmission, and a retransmission, and is configured by RRC signaling and / or the first MAC CE and / or DCI.

[0220] In some embodiments, the candidate or target DU of the network device uses a HARQ process to receive the above-mentioned uplink transmission sent by the terminal device; wherein, for CG type 1, the process ID of the HARQ process is calculated using a first calculation formula and a first parameter; for CG type 2, the process ID of the HARQ process is calculated using the second calculation formula and the second parameter; wherein the SFNstart time, slotstart time and symbolstart time in the second parameter are respectively the SFN, slot and symbol of the first transmission opportunity of the PUSCH when or after the CG occasion is available.

[0221] In some embodiments, the information regarding successful uplink transmission reception may be one of the following:

[0222] RLC ACK of the uplink transmission;

[0223] PDCCH addressed by C-RNTI;

[0224] UE contention resolution ID MAC CE;

[0225] MAC CE indicating that the LTM cell handover is completed.

[0226] For example, if the above-mentioned CG is used for retransmission, the above-mentioned information is a PDCCH addressed by C-RNTI.

[0227] For another example, if the DG is used for initial transmission or retransmission, the information is a PDCCH addressed by the C-RNTI, and the PDCCH schedules the new transmission, or the PDCCH schedules the new transmission on the HARQ process ID.

[0228] In the above embodiment, the PDCCH can be used to schedule the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and one of the MAC CEs indicating the completion of the LTM cell handover; or, when the information is a PDCCH addressed by C-RNTI, the PDCCH can be used to schedule the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and one of the MAC CEs indicating the completion of the LTM cell handover.

[0229] In some embodiments, the source DU of the network device may also send a target cell identifier and beam information to the CU of the network device; the CU of the network device sends the above target cell identifier and beam information to the candidate or target DU of the network device.

[0230] For example, when the CG configuration configured for the terminal device does not include the configuration of the cell associated with the candidate configuration information included in the above-mentioned first MAC CE, the source DU of the network device sends the above-mentioned target cell identifier and beam information to the CU of the network device, and the CU of the network device sends the target cell identifier and beam information to the candidate or target DU of the network device.

[0231] In the above embodiment, the target cell identifier and beam information sent by the source DU of the network device may be included in a UE CONTEXT MODIFICATION REQUIRED message, or included in an F1 message (referred to as a first F1 message). The first F1 message may be, for example, a UE CONTEXT SETUP REQUIRED message, but the present application is not limited thereto.

[0232] In the above embodiment, the target cell identifier and beam information sent by the CU of the network device may be included in an F1 message (referred to as a second F1 message). The second F1 message may be, for example, a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message, but the present application is not limited thereto.

[0233] In the above embodiment, the beam information may include at least one of the following:

[0234] Unified TCI status information;

[0235] TCI status information;

[0236] Uplink space filtering information.

[0237] For details, please refer to the embodiment of the first aspect, and the description is omitted here.

[0238] In the above embodiment, the target cell identifier may include candidate configuration information, or include candidate configuration information and a cell index under the candidate configuration.

[0239] Figure 8 is another diagram of the inter-gNB-DU L1 / L2 triggered mobility procedure (LTM), illustrating the scenario where the source DU notifies the target DU of the target cell ID and beam information via the CU. As shown in Figure 8, unlike the process shown in Figure 4, in step 12, the UE CONTEXT MODIFICATION REQUIRED message includes beam information in addition to the target cell ID. Furthermore, a new step, S1, is added between steps 12 and 14. In step S1, the gNB-CU sends an F1 message, such as a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message, to the candidate or target gNB-DU. This message includes the target cell ID and beam information received in step 12.

[0240] In the above example, there is no limitation on the position of step S1 , for example, it can be before step 13 or after step 13 , and so on.

[0241] Figure 9 is another diagram of the inter-gNB-DU L1 / L2 triggered mobility procedure (LTM), illustrating the scenario where the source DU notifies the target DU of the target cell identifier and beam information via the CU. Unlike the example shown in Figure 8, in the example of Figure 9, step 12 is not modified. Instead, two new steps, numbered S2 and S3, are added between steps 10 and 13. Step S2 involves the source gNB-DU sending an F1 message, such as a UE CONTEXT SETUP REQUIRED message, to the gNB-CU. This message includes the target cell identifier and beam information, or may only include the beam information. Step S3 involves the gNB-CU sending an F1 message, such as a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message, to the candidate or target gNB-DU. This message includes the target cell identifier and beam information received in step S2.

[0242] In the above example, there is no limitation on the positions of steps S2 and S3. For example, they can be placed before or after step 11, or before or after step 12, and so on.

[0243] The above embodiments illustrate the methods of the present invention, but the present invention is not limited thereto. Appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0244] According to the method of the embodiment of the present application, the problem of how the terminal device selects resources for uplink transmission when the configured authorization includes one group and multiple groups is solved, ensuring the successful completion of LTM cell switching and improving network performance.

[0245] Embodiments of the third aspect

[0246] The embodiments of the present application provide an uplink transmission device, which may be, for example, a terminal device, or one or more components or assemblies configured on the terminal device. Because the principle of solving the problem of this device is the same as the method of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method of the embodiment of the first aspect, and the same content will not be repeated here.

[0247] FIG10 is a schematic diagram of a sending device for uplink transmission according to an embodiment of the present application. As shown in FIG10 , the device 1000 includes:

[0248] A receiving unit 1001 receives a first MAC CE (Media Access Control Element) including candidate configuration information sent by a first DU (Distributed Unit);

[0249] The sending unit 1002 uses an available CG occasion (configured grant opportunity) or a DG (dynamic grant) to send uplink transmission to the cell associated with the candidate configuration information.

[0250] In some embodiments, the available CG occasion is associated with at least one of the following:

[0251] beam information included in the first MAC CE;

[0252] The terminal device is used to obtain the RO used for random access performed by the TA;

[0253] RS of beam information included in the first MAC CE;

[0254] RS of the RO;

[0255] Specific RS.

[0256] In the above embodiment, the beam information may include unified TCI state information, and the unified TCI state information may include a joint TCI state ID, or a UL TCI state ID and / or a DL TCI state ID in a separate TCI state ID. The terminal device may send the uplink transmission on the beam corresponding to the joint TCI state ID or the UL TCI state ID; and / or, the terminal device may receive information indicating that the uplink transmission is successfully received on the beam corresponding to the joint TCI state ID or the DL TCI state ID.

[0257] In the above embodiment, the beam information may include TCI state information and / or uplink spatial filtering information. The terminal device may receive information indicating successful reception of the uplink transmission on the beam corresponding to the TCI state information; and / or the terminal device may send the uplink transmission on the beam associated with the uplink spatial filtering information.

[0258] In the above embodiment, associating the available CG occasion with the RO used by the terminal device for random access to obtain the TA may include:

[0259] If the first MAC CE does not include beam information, or the CG occasion associated with the beam information included in the first MAC CE is not configured, or the CG occasion associated with the beam information included in the first MAC CE is invalid, the available CG occasion is associated with the RO.

[0260] In the above embodiment, the specific RS may be the SSB for receiving SIB1.

[0261] In the above embodiment, the specific RS may be an RS indicated in SIB1 or MIB.

[0262] In the above embodiment, the RS may include at least one of the following: SSB, CSI-RS, SRS.

[0263] In some embodiments, when at least one of the following conditions is met, the terminal device considers that the CG occasion is available or there is the available CG occasion:

[0264] RRC signaling configures the CG occasion;

[0265] receiving the first MAC CE;

[0266] Receive specific DCI.

[0267] In some implementations, the specific DCI is used to schedule the PDSCH carrying the first MAC CE.

[0268] In some implementations, the specific DCI and the first MAC CE are sent or received simultaneously, and sending or receiving simultaneously means sending or receiving in the same time slot, symbol, or RB.

[0269] In some embodiments, the available CG occasion is on an uplink carrier, which is at least one of the following:

[0270] NUL (Normal Uplink) or SUL (Supplementary Uplink) configured with CG;

[0271] NUL or SUL of the CG configured for the LTM process;

[0272] NUL or SUL of the available CG configured for LTM process;

[0273] An uplink carrier used by the terminal device for random access to obtain TA (timing advance);

[0274] the uplink carrier indicated by the first MAC CE;

[0275] The uplink carrier is selected based on the RSRP of the downlink path loss reference signal.

[0276] In the above embodiment, if an RSRP threshold is configured and if the RSRP of the downlink path loss reference signal is less than the RSRP threshold, the selected uplink carrier is SUL; otherwise, the selected uplink carrier is NUL.

[0277] In some embodiments, the uplink transmission carries an RRC reconfiguration completion message, or carries a MAC CE indicating LTM completion.

[0278] In some embodiments, the uplink transmission is at least one of an initial transmission, a repetition of an initial transmission, and a retransmission, and is configured by RRC signaling and / or the first MAC CE and / or DCI.

[0279] In the above embodiment, if the uplink transmission includes retransmission, the sending unit 1002 may further start a retransmission timer after the initial transmission is sent, and send the retransmission when the retransmission timer expires.

[0280] In some embodiments, the terminal device sends the uplink transmission using a HARQ process;

[0281] Among them, for CG type 1, the first calculation formula and the first parameter are used to calculate the process ID of the HARQ process; for CG type 2, the second calculation formula and the second parameter are used to calculate the process ID of the HARQ process; wherein, the SFNstart time, slotstart time and symbolstart time in the second parameter are respectively the SFN, slot and symbol of the first transmission opportunity of the PUSCH when or after the CG occasion is available.

[0282] In some embodiments, the sending unit 1002 determines whether to use the above-mentioned CG occasion to send the uplink transmission.

[0283] In some embodiments, if the conditions for using CG are met or the conditions for using DG are not met, the sending unit 1002 determines to use the CG occasion to send the uplink transmission; if the conditions for using DG are met or the conditions for using CG are not met, the sending unit 1002 uses the DG to send the uplink transmission.

[0284] In the above embodiment, the conditions for using CG may include at least one of the following:

[0285] Configured CG;

[0286] The configured CG is valid or available;

[0287] A time interval associated with receiving the first MAC CE satisfies a first predetermined condition.

[0288] In the above embodiment, the first predetermined condition may include at least one of the following:

[0289] The time interval between the reception of the first MAC CE and the next CG occasion is less than the configured offset;

[0290] After receiving the first MAC CE, no PDCCH addressed by the C-RNTI is received;

[0291] No PDCCH addressed by the C-RNTI is received between the first MAC CE reception and the next CG occasion.

[0292] In the above embodiment, the conditions for using DG may include at least one of the following:

[0293] The first DU is a DU associated with the candidate configuration information;

[0294] The first DU notifies the second DU that the terminal device performs LTM;

[0295] The first DU notifies the second DU of the beam information included in the first MAC CE;

[0296] A time interval associated with receiving the first MAC CE satisfies a second predetermined condition.

[0297] In the above embodiment, the second predetermined condition may include at least one of the following:

[0298] The time interval between the reception of the first MAC CE and the next C-RNTI-addressed PDCCH is less than the configured offset;

[0299] There is no available CG occasion after the first MAC CE is received;

[0300] There is no available CG occasion between the first MAC CE reception and the next C-RNTI addressed PDCCH reception.

[0301] In some embodiments, the receiving unit 1001 receives the information indicating that the uplink transmission is successfully received.

[0302] In the above embodiment, the above information may be one of the following:

[0303] RLC ACK of the uplink transmission;

[0304] PDCCH addressed by C-RNTI;

[0305] UE contention resolution ID MAC CE;

[0306] MAC CE indicating that the LTM cell handover is completed.

[0307] For example, if the above-mentioned CG is used for retransmission, the above-mentioned information may be a PDCCH addressed by C-RNTI.

[0308] For another example, if the DG is used for initial transmission or retransmission, the information is a PDCCH addressed by the C-RNTI, and the PDCCH schedules a new transmission, or the PDCCH schedules a new transmission on a HARQ process ID.

[0309] In the above embodiment, the PDCCH may be used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover. For example, when the information is a C-RNTI-addressed PDCCH, the PDCCH is used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover.

[0310] The present application also provides an uplink transmission receiving device, which can be a network device or one or more components or assemblies configured on the network device. Since the principle of solving the problem of this device is the same as the method of the embodiment of the second aspect, its specific implementation can refer to the implementation of the method of the embodiment of the second aspect, and the same content will not be repeated here.

[0311] FIG11 is a schematic diagram of an uplink transmission receiving device according to an embodiment of the present application. As shown in FIG11 , the device 1100 includes:

[0312] A sending unit 1101, which sends a first MAC CE (Media Access Control Element) including candidate configuration information to a terminal device at a source DU;

[0313] The receiving unit 1102 receives the uplink transmission sent by the terminal device to the cell associated with the candidate configuration information using an available CG occasion (configured grant opportunity) or a DG (dynamic grant) in the candidate or target DU.

[0314] In some embodiments, the available CG occasion is associated with at least one of the following:

[0315] beam information included in the first MAC CE;

[0316] The terminal device is used to obtain the RO used for random access performed by the TA;

[0317] RS of beam information included in the first MAC CE;

[0318] RS of the RO;

[0319] Specific RS.

[0320] In the above embodiment, the beam information may include Unified TCI state information, and the Unified TCI state information may include a joint TCI state ID, or a UL TCI state ID and / or a DL TCI state ID in a separate TCI state ID. The receiving unit 1102 may receive the uplink transmission sent by the terminal device on the beam corresponding to the joint TCI state ID or the UL TCI state ID; and / or the sending unit 1101 may send information indicating successful reception of the uplink transmission to the terminal device on the beam corresponding to the joint TCI state ID or the DL TCI state ID.

[0321] In the above embodiment, the beam information may include TCI state information and / or uplink spatial filtering information. The sending unit 1101 may send information indicating successful reception of the uplink transmission to the terminal device on the beam corresponding to the TCI state information; and / or the receiving unit 1102 may receive the uplink transmission sent by the terminal device on the beam associated with the uplink spatial filtering information.

[0322] In the above embodiment, the available CG occasion associated with the RO used by the terminal device for random access to obtain the TA may include:

[0323] If the first MAC CE does not include beam information, or the CG occasion associated with the beam information included in the first MAC CE is not configured, or the CG occasion associated with the beam information included in the first MAC CE is invalid, the available CG occasion is associated with the RO.

[0324] In the above embodiment, the specific RS may be an SSB for receiving SIB1.

[0325] In the above embodiment, the specific RS may be an RS indicated in SIB1 or MIB.

[0326] In the above embodiment, the RS may include at least one of the following: SSB, CSI-RS, SRS.

[0327] In some embodiments, when at least one of the following conditions is met, the terminal device considers that the CG occasion is available or there is the available CG occasion:

[0328] RRC signaling configures the CG occasion;

[0329] receiving the first MAC CE;

[0330] Receive specific DCI.

[0331] In some implementations, the specific DCI is used to schedule the PDSCH carrying the first MAC CE.

[0332] In some implementations, the specific DCI and the first MAC CE are sent or received simultaneously, and sending or receiving simultaneously means sending or receiving in the same time slot, symbol, or RB.

[0333] In some embodiments, the available CG occasion is on an uplink carrier, and the uplink carrier is at least one of the following:

[0334] NUL (Normal Uplink) or SUL (Supplementary Uplink) configured with CG;

[0335] NUL or SUL of the CG configured for the LTM process;

[0336] NUL or SUL of the available CG configured for LTM process;

[0337] An uplink carrier used by the terminal device for random access to obtain TA (timing advance);

[0338] the uplink carrier indicated by the first MAC CE;

[0339] The uplink carrier is selected based on the RSRP of the downlink path loss reference signal.

[0340] In the above embodiment, if an RSRP threshold is configured and if the RSRP of the downlink path loss reference signal is less than the RSRP threshold, the selected uplink carrier is SUL; otherwise, the selected uplink carrier is NUL.

[0341] In some embodiments, the uplink transmission carries an RRC reconfiguration completion message, or carries a MAC CE for indicating LTM completion.

[0342] In some embodiments, the uplink transmission is at least one of an initial transmission, a repetition of an initial transmission, and a retransmission, and is configured by RRC signaling and / or the first MAC CE and / or DCI.

[0343] In some embodiments, the receiving unit 1102 receives the uplink transmission sent by the terminal device using the HARQ process; wherein, for CG type 1, the process ID of the HARQ process is calculated using a first calculation formula and a first parameter; and for CG type 2, the process ID of the HARQ process is calculated using the second calculation formula and the second parameter; wherein the SFNstart time, slotstart time and symbolstart time in the second parameter are respectively the SFN, slot and symbol of the first transmission opportunity of the PUSCH when or after the CG occasion is available.

[0344] In some embodiments, the sending unit 1101 sends information indicating successful reception of the uplink transmission to the terminal device.

[0345] In the above embodiment, the information may be one of the following:

[0346] RLC ACK of the uplink transmission;

[0347] PDCCH addressed by C-RNTI;

[0348] UE contention resolution ID MAC CE;

[0349] MAC CE indicating that the LTM cell handover is completed.

[0350] For example, if the CG is used for retransmission, the information is a C-RNTI addressed PDCCH.

[0351] For another example, if the DG is used for initial transmission or retransmission, the information is a PDCCH addressed by a C-RNTI, and the PDCCH schedules a new transmission, or the PDCCH schedules a new transmission on a HARQ process ID.

[0352] In the above embodiment, the PDCCH may be used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover. For example, when the information is a C-RNTI addressed PDCCH, the PDCCH is used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover.

[0353] In some embodiments, the sending unit 1101 sends the target cell identifier and beam information to the CU at the source DU; the CU sends the above target cell identifier and beam information to the candidate or target DU.

[0354] In the above embodiment, when the CG configuration configured for the terminal device does not include the configuration of the cell associated with the candidate configuration information included in the above first MAC CE, the sending unit 1101 performs the above processing.

[0355] In the above embodiment, the target cell identifier and beam information sent by the sending unit 1101 in the source DU are included in a UE CONTEXT MODIFICATION REQUIRED message, or included in a first F1 message, such as a UE CONTEXT SETUP REQUIRED message.

[0356] In the above embodiment, the target cell identifier and beam information sent by the sending unit 1101 in the CU are included in the second F1 message. The second F1 message is, for example, a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0357] In the aforementioned embodiment, the beam information may include at least one of the following:

[0358] Unified TCI status information;

[0359] TCI status information;

[0360] Uplink space filtering information.

[0361] In the aforementioned embodiment, the target cell identifier may include candidate configuration information, or include candidate configuration information and a cell index under the candidate configuration.

[0362] The above embodiments of the present application are illustrative, but the present application is not limited thereto, and appropriate modifications can be made based on the above embodiments. For example, the above embodiments can be used alone, or one or more of the above embodiments can be combined.

[0363] It is worth noting that the above description only describes the components or modules related to this application, but this application is not limited thereto. The above-mentioned device may also include other components or modules. For the specific content of these components or modules, please refer to the relevant art. In addition, the above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; the implementation of this application is not limited to this.

[0364] According to the device of the embodiment of the present application, the successful completion of LTM cell switching is ensured, and network performance is improved.

[0365] Embodiments of the fourth aspect

[0366] An embodiment of the present application also provides a communication system, including a network device and a terminal device.

[0367] FIG12 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG12 , a communication system 1200 may include a network device 1201 and terminal devices 1202 and 1203. For simplicity, FIG12 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0368] In the embodiment of the present application, existing services or future services can be transmitted between the network device 1201 and the terminal devices 1202 and 1203. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0369] It is worth noting that Figure 12 shows that both terminal devices 1202 and 1203 are within the coverage range of network device 1201, but the present application is not limited thereto. Both terminal devices 1202 and 1203 may not be within the coverage range of network device 1201, or one terminal device 1202 may be within the coverage range of network device 1201 while the other terminal device 1203 is outside the coverage range of network device 1201.

[0370] In some embodiments, the network device includes the apparatus 1100 described in the embodiment of the third aspect, configured to execute the method described in the embodiment of the second aspect. Since the method has been described in detail in the embodiment of the second aspect, its content is incorporated herein and will not be repeated.

[0371] The above-mentioned network device can be an intra-DU mobility scenario, including a gNB-DU and a gNB-CU, or a gNB in ​​an inter-DU mobility scenario, including a source gNB-DU, a candidate or target gNB-DU, and a gNB-CU, and performs the method described in the embodiment of the second aspect.

[0372] In some embodiments, the terminal device includes the apparatus 1000 described in the embodiment of the third aspect, and is configured to perform the method described in the embodiment of the first aspect. Since the method has been described in detail in the embodiment of the first aspect, its content is incorporated herein and will not be repeated.

[0373] The above-mentioned terminal device can be a UE in an intra-DU mobility scenario or an inter-DU mobility scenario, and executes the method described in the embodiment of the first aspect.

[0374] An embodiment of the present application also provides a network device, which may be, for example, a base station, such as a gNB in ​​an intra-DU mobility scenario or an inter-DU mobility scenario, but the present application is not limited thereto and may also be other network devices.

[0375] Figure 13 is a schematic diagram illustrating the structure of a network device according to an embodiment of the present application. As shown in Figure 13 , network device 1300 may include a processor 1301 and a memory 1302 ; the memory 1302 is coupled to the processor 1301 . The memory 1302 may store various data and information processing programs, which are executed under the control of the processor 1301 .

[0376] In some embodiments, the functions of the device 1100 of the embodiment of the third aspect can be integrated into the processor 1301, wherein the processor 1301 can be configured to execute a program to implement the method described in the embodiment of the second aspect, the content of which is incorporated herein and will not be repeated here.

[0377] In other embodiments, the apparatus 1100 of the embodiment of the third aspect may be configured separately from the processor 1301. For example, the apparatus 1100 of the embodiment of the third aspect may be configured as a chip connected to the processor 1301, and the functions of the apparatus 1100 of the embodiment of the third aspect may be implemented through the control of the processor 1301.

[0378] Furthermore, as shown in FIG13 , network device 1300 may further include transceivers 1303 and 1304. The functions of these components are similar to those in the prior art and are not further described here. It is worth noting that network device 1300 does not necessarily include all of the components shown in FIG13 ; furthermore, network device 1300 may also include components not shown in FIG13 , for which reference may be made to the prior art.

[0379] An embodiment of the present application also provides a terminal device, which may be, for example, a UE, such as a UE in an intra-DU mobility scenario or an inter-DU mobility scenario, but the present application is not limited thereto and may also be other terminal devices.

[0380] Figure 14 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 14 , terminal device 1400 may include a processor 1401 and a memory 1402. Memory 1402 stores data and programs and is coupled to processor 1401. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0381] In some embodiments, the functions of the device 1000 of the embodiment of the third aspect can be integrated into the processor 1401, wherein the processor 1401 can be configured to execute a program to implement the method described in the embodiment of the first aspect, the content of which is incorporated herein and will not be repeated here.

[0382] In other embodiments, the apparatus 1000 of the embodiment of the third aspect may be configured separately from the processor 1401. For example, the apparatus 1000 of the embodiment of the third aspect may be configured as a chip connected to the processor 1401, and the functions of the apparatus 1000 of the embodiment of the third aspect may be implemented through the control of the processor 1401.

[0383] As shown in Figure 14 , the terminal device 1400 may further include: a communication module 1403, an input unit 1404, a display 1405, and a power supply 1406. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 1400 does not necessarily include all of the components shown in Figure 14 , and these components are not essential. Furthermore, the terminal device 1400 may also include components not shown in Figure 14 , for which reference may be made to related art.

[0384] An embodiment of the present application further provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.

[0385] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.

[0386] An embodiment of the present application further provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0387] An embodiment of the present application further provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0388] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0389] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0390] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0391] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0392] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0393] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0394] 1. A method for sending an uplink transmission, wherein the method comprises:

[0395] The terminal device receives a first MAC CE (Media Access Control Element) including candidate configuration information sent by a first DU (Distributed Unit);

[0396] The terminal device uses an available CG occasion (configured grant opportunity) or uses DG (dynamic grant) to send uplink transmission to the cell associated with the candidate configuration information.

[0397] 2. The method according to Supplementary Note 1, wherein the available CG occasion is associated with at least one of the following:

[0398] beam information included in the first MAC CE;

[0399] The terminal device is used to obtain the RO used for random access performed by the TA;

[0400] RS of beam information included in the first MAC CE;

[0401] RS of the RO;

[0402] Specific RS.

[0403] 3. The method according to Supplementary Note 2, wherein:

[0404] The beam information includes Unified TCI state information.

[0405] 3a. The method according to Note 3, wherein:

[0406] The unified TCI state information includes a joint TCI state ID, or a UL TCI state ID and / or a DL TCI state ID in a separate TCI state ID.

[0407] 4. The method according to Supplement 3a, wherein:

[0408] The terminal device sends the uplink transmission on the beam corresponding to the joint TCI state ID or the UL TCI state ID; and / or,

[0409] The terminal device receives the information that the uplink transmission is successfully received on the beam corresponding to the joint TCI state ID or the DL TCI state ID.

[0410] 5. The method according to Supplementary Note 2, wherein:

[0411] The beam information includes TCI state information and / or uplink spatial filtering information.

[0412] 6. The method according to Supplement 5, wherein:

[0413] The terminal device receives the information that the uplink transmission is successfully received on the beam corresponding to the TCI state information; and / or,

[0414] The terminal device sends the uplink transmission on the beam associated with the uplink spatial filtering information.

[0415] 7. The method according to Note 2, wherein the available CG occasion is associated with the RO used by the terminal device to obtain the TA for random access, comprising:

[0416] If the first MAC CE does not include beam information, or the CG occasion associated with the beam information included in the first MAC CE is not configured, or the CG occasion associated with the beam information included in the first MAC CE is invalid, the available CG occasion is associated with the RO.

[0417] 8. The method according to Supplementary Note 2, wherein:

[0418] The specific RS is the SSB for receiving SIB1.

[0419] 9. The method according to Supplement 2, wherein:

[0420] The specific RS is the RS indicated in SIB1 or MIB.

[0421] 10. The method according to Supplement 2 or Supplement 9, wherein:

[0422] The RS includes at least one of the following: SSB, CSI-RS, SRS.

[0423] 11. The method according to Supplementary Note 1, wherein the terminal device considers that the CG occasion is available or that there is the available CG occasion when at least one of the following conditions is satisfied:

[0424] RRC signaling configures the CG occasion;

[0425] receiving the first MAC CE;

[0426] Receive specific DCI.

[0427] 12. The method according to Supplement 11, wherein:

[0428] The specific DCI is used to schedule the PDSCH carrying the first MAC CE; and / or,

[0429] The specific DCI is sent or received simultaneously with the first MAC CE. Sending or receiving simultaneously means sending or receiving in the same time slot, symbol or RB.

[0430] 13. The method according to any one of Notes 1 to 12, wherein the available CG occasion is on an uplink carrier, and the uplink carrier is at least one of the following:

[0431] NUL (Normal Uplink) or SUL (Supplementary Uplink) configured with CG;

[0432] NUL or SUL of the CG configured for the LTM process;

[0433] NUL or SUL of the available CG configured for LTM process;

[0434] An uplink carrier used by the terminal device for random access to obtain TA (timing advance);

[0435] the uplink carrier indicated by the first MAC CE;

[0436] The uplink carrier is selected based on the RSRP of the downlink path loss reference signal.

[0437] 14. The method according to Supplement 13, wherein:

[0438] If an RSRP threshold is configured, and if the RSRP of the downlink path loss reference signal is less than the RSRP threshold, the selected uplink carrier is the SUL;

[0439] Otherwise, the selected uplink carrier is NUL.

[0440] 15. The method according to any one of Notes 1 to 14, wherein:

[0441] The uplink transmission carries an RRC reconfiguration completion message, or carries a MAC CE for indicating LTM completion.

[0442] 16. The method according to any one of Notes 1 to 15, wherein:

[0443] The uplink transmission is at least one of an initial transmission, a repetition of an initial transmission, and a retransmission.

[0444] 16a. The method according to Note 16, wherein:

[0445] At least one of the initial transmission, the repetition of the initial transmission and the retransmission is configured by RRC signaling and / or the first MAC CE and / or DCI.

[0446] 17. The method according to Note 16, wherein if the uplink transmission includes retransmission, the method further comprises:

[0447] The terminal device starts a retransmission timer after the initial transmission is sent, and sends the retransmission when the retransmission timer expires.

[0448] 18. The method according to any one of Notes 1 to 17, wherein:

[0449] The terminal device sends the uplink transmission using a HARQ process;

[0450] For CG type 1, the process ID of the HARQ process is calculated using the first calculation formula and the first parameter; for CG type 2, the process ID of the HARQ process is calculated using the second calculation formula and the second parameter;

[0451] Among them, the SFNstart time, slotstart time and symbolstart time in the second parameter are respectively the SFN, slot and symbol of the first transmission opportunity of the PUSCH when or after the CG occasion is available.

[0452] 19. The method according to any one of Notes 1 to 18, wherein the method further comprises:

[0453] The terminal device determines whether to use the CG occasion to send the uplink transmission.

[0454] 20. The method according to any one of Notes 1 to 19, wherein:

[0455] If the condition for using the CG is met or the condition for using the DG is not met, the terminal device determines to use the CG occasion to send the uplink transmission;

[0456] If the conditions for using DG are met or the conditions for using CG are not met, the terminal device uses the DG to send the uplink transmission.

[0457] 21. The method according to Supplementary Note 20, wherein the conditions for using CG include at least one of the following:

[0458] Configured CG;

[0459] The configured CG is valid or available;

[0460] A time interval associated with receiving the first MAC CE satisfies a first predetermined condition.

[0461] 22. The method according to Supplementary Note 21, wherein the first predetermined condition includes at least one of the following:

[0462] The time interval between the reception of the first MAC CE and the next CG occasion is less than the configured offset;

[0463] After receiving the first MAC CE, no PDCCH addressed by the C-RNTI is received;

[0464] No PDCCH addressed by the C-RNTI is received between the first MAC CE reception and the next CG occasion.

[0465] 23. The method according to Supplementary Note 20, wherein the conditions for using DG include at least one of the following:

[0466] The first DU is a DU associated with the candidate configuration information;

[0467] The first DU notifies the second DU that the terminal device performs LTM;

[0468] The first DU notifies the second DU of the beam information included in the first MAC CE;

[0469] A time interval associated with receiving the first MAC CE satisfies a second predetermined condition.

[0470] 24. The method according to Supplementary Note 23, wherein the second predetermined condition includes at least one of the following:

[0471] The time interval between the reception of the first MAC CE and the next C-RNTI-addressed PDCCH is less than the configured offset;

[0472] There is no available CG occasion after the first MAC CE is received;

[0473] There is no available CG occasion between the first MAC CE reception and the next C-RNTI addressed PDCCH reception.

[0474] 25. The method according to any one of Notes 1 to 24, wherein the method further comprises:

[0475] The terminal device receives information that the uplink transmission is successfully received.

[0476] 26. The method according to Supplementary Note 25, wherein the information is one of the following:

[0477] RLC ACK of the uplink transmission;

[0478] PDCCH addressed by C-RNTI;

[0479] UE contention resolution ID MAC CE;

[0480] MAC CE indicating that the LTM cell handover is completed.

[0481] 27. The method according to Supplementary Note 26, wherein:

[0482] When the information is a PDCCH addressed by a C-RNTI, the PDCCH is used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating completion of the LTM cell handover.

[0483] 28. The method according to Supplementary Note 26, wherein:

[0484] If the CG is used for retransmission, the information is a PDCCH addressed by C-RNTI.

[0485] 29. The method according to Supplementary Note 26, wherein:

[0486] If the DG is used for initial transmission or retransmission, the information is a PDCCH addressed by a C-RNTI, and the PDCCH schedules a new transmission, or the PDCCH schedules a new transmission on a HARQ process ID.

[0487] 30. A method for receiving uplink transmission, wherein the method comprises:

[0488] The source DU of the network device sends a first MAC CE (Media Access Control Element) including candidate configuration information to the terminal device;

[0489] The candidate or target DU of the network device uses an available CG occasion (configured grant opportunity) or uses DG (dynamic grant) to receive the uplink transmission sent by the terminal device to the cell associated with the candidate configuration information.

[0490] 31. The method according to Supplement 30, wherein the available CG occasion is associated with at least one of the following:

[0491] beam information included in the first MAC CE;

[0492] The terminal device is used to obtain the RO used for random access performed by the TA;

[0493] RS of beam information included in the first MAC CE;

[0494] RS of the RO;

[0495] Specific RS.

[0496] 32. The method according to Note 31, wherein:

[0497] The beam information includes Unified TCI state information.

[0498] 32a. The method according to Note 32, wherein:

[0499] The unified TCI state information includes a joint TCI state ID, or a UL TCI state ID and / or a DL TCI state ID in a separate TCI state ID.

[0500] 33. The method according to Note 32a, wherein:

[0501] The candidate or target DU of the network device receives the uplink transmission sent by the terminal device on the beam corresponding to the joint TCI state ID or the UL TCI state ID; and / or,

[0502] The candidate or target DU of the network device sends the information of successful reception of the uplink transmission to the terminal device on the beam corresponding to the joint TCI state ID or the DL TCI state ID.

[0503] 34. The method according to Note 31, wherein:

[0504] The beam information includes TCI state information and / or uplink spatial filtering information.

[0505] 35. The method according to Note 34, wherein:

[0506] The candidate or target DU of the network device receives the uplink transmission sent by the terminal device on the beam associated with the uplink spatial filtering information; and / or,

[0507] The candidate or target DU of the network device sends the information that the uplink transmission is successfully received to the terminal device on the beam corresponding to the TCI state information.

[0508] 36. The method according to note 31, wherein the available CG occasion is associated with the RO used by the terminal device for random access to obtain the TA, comprising:

[0509] If the first MAC CE does not include beam information, or the CG occasion associated with the beam information included in the first MAC CE is not configured, or the CG occasion associated with the beam information included in the first MAC CE is invalid, the available CG occasion is associated with the RO.

[0510] 37. The method according to Note 31, wherein:

[0511] The specific RS is the SSB for receiving SIB1.

[0512] 38. The method according to Note 31, wherein:

[0513] The specific RS is the RS indicated in SIB1 or MIB.

[0514] 39. The method according to Supplement 31 or Supplement 38, wherein:

[0515] The RS includes at least one of the following: SSB, CSI-RS, SRS.

[0516] 40. The method according to Supplementary Note 30, wherein the terminal device considers that the CG occasion is available or that there is the available CG occasion when at least one of the following conditions is satisfied:

[0517] RRC signaling configures the CG occasion;

[0518] receiving the first MAC CE;

[0519] Receive specific DCI.

[0520] 41. The method according to Note 40, wherein:

[0521] The specific DCI is used to schedule the PDSCH carrying the first MAC CE; and / or,

[0522] The specific DCI is sent or received simultaneously with the first MAC CE. Sending or receiving simultaneously means sending or receiving in the same time slot, symbol or RB.

[0523] 42. The method according to any one of Notes 30 to 41, wherein the available CG occasion is on an uplink carrier, and the uplink carrier is at least one of the following:

[0524] NUL (Normal Uplink) or SUL (Supplementary Uplink) configured with CG;

[0525] NUL or SUL of the CG configured for the LTM process;

[0526] NUL or SUL of the available CG configured for LTM process;

[0527] An uplink carrier used by the terminal device for random access to obtain TA (timing advance);

[0528] the uplink carrier indicated by the first MAC CE;

[0529] The uplink carrier is selected based on the RSRP of the downlink path loss reference signal.

[0530] 43. The method according to Note 42, wherein:

[0531] If an RSRP threshold is configured, and if the RSRP of the downlink path loss reference signal is less than the RSRP threshold, the selected uplink carrier is the SUL;

[0532] Otherwise, the selected uplink carrier is NUL.

[0533] 44. The method according to any one of Notes 30 to 43, wherein:

[0534] The uplink transmission carries an RRC reconfiguration completion message, or carries a MAC CE for indicating LTM completion.

[0535] 45. The method according to any one of Notes 30 to 43, wherein:

[0536] The uplink transmission is at least one of an initial transmission, a repetition of an initial transmission, and a retransmission, which is configured by RRC signaling and / or the first MAC CE and / or DCI.

[0537] 46. ​​The method according to any one of Notes 30 to 45, wherein:

[0538] The candidate or target DU of the network device receives the uplink transmission sent by the terminal device using the HARQ process;

[0539] For CG type 1, the process ID of the HARQ process is calculated using the first calculation formula and the first parameter; for CG type 2, the process ID of the HARQ process is calculated using the second calculation formula and the second parameter;

[0540] Among them, the SFNstart time, slotstart time and symbolstart time in the second parameter are respectively the SFN, slot and symbol of the first transmission opportunity of the PUSCH when or after the CG occasion is available.

[0541] 47. The method according to Note 33 or 35, wherein:

[0542] The information of successful uplink transmission reception is one of the following:

[0543] RLC ACK of the uplink transmission;

[0544] PDCCH addressed by C-RNTI;

[0545] UE contention resolution ID MAC CE;

[0546] MAC CE indicating that the LTM cell handover is completed.

[0547] 48. The method according to Note 47, wherein:

[0548] When the information is a PDCCH addressed by a C-RNTI, the PDCCH is used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating completion of the LTM cell handover.

[0549] 49. The method according to Supplement 47, wherein:

[0550] If the CG is used for retransmission, the information is a PDCCH addressed by C-RNTI.

[0551] 50. The method according to Note 47, wherein:

[0552] If the DG is used for initial transmission or retransmission, the information is a PDCCH addressed by a C-RNTI, and the PDCCH schedules a new transmission, or the PDCCH schedules a new transmission on a HARQ process ID.

[0553] 51. The method according to any one of Notes 30 to 50, further comprising:

[0554] The source DU of the network device sends a target cell identifier and beam information to the CU of the network device;

[0555] The CU of the network device sends the target cell identifier and the beam information to the candidate or target DU of the network device.

[0556] 51a. The method according to Note 51, wherein:

[0557] The CG configuration configured for the terminal device does not include the configuration of the cell associated with the candidate configuration information included in the first MAC CE.

[0558] 52. The method according to Note 51, wherein:

[0559] The target cell identifier and beam information sent by the source DU of the network device are included in a UE CONTEXT MODIFICATION REQUIRED message, or included in a first F1 message.

[0560] 53. The method according to Note 52, wherein:

[0561] The first F1 message is a UE CONTEXT SETUP REQUIRED message.

[0562] 54. The method according to Note 51, wherein:

[0563] The target cell identifier and beam information sent by the CU of the network device are included in the second F1 message.

[0564] 55. The method according to Note 54, wherein:

[0565] The second F1 message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

[0566] 56. The method according to any one of Notes 51 to 55, wherein:

[0567] The beam information includes at least one of the following:

[0568] Unified TCI status information;

[0569] TCI status information;

[0570] Uplink space filtering information.

[0571] 57. The method according to any one of Notes 51 to 55, wherein:

[0572] The target cell identifier includes candidate configuration information, or includes candidate configuration information and a cell index under the candidate configuration.

[0573] 58. A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 29.

[0574] 59. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 30 to 57.

[0575] 60. A communication system comprising the network device described in Note 59 and / or the terminal device described in Note 58.

Claims

1. A sending device for uplink transmission, configured in a terminal device, wherein: The device comprises: a receiving unit, configured to receive a first MAC CE (Media Access Control Element) including candidate configuration information sent by a first DU (Distributed Unit); A sending unit, which uses an available CG occasion (configured grant opportunity) or a DG (dynamic grant) to send uplink transmission to the cell associated with the candidate configuration information.

2. The device according to claim 1, wherein: The available CG occasion is associated with at least one of the following: beam information included in the first MAC CE; The terminal device is used to obtain the RO used for random access performed by the TA; The RS of the beam information included in the first MAC CE; The RS of the RO; Specific RS.

3. The device according to claim 2, wherein: The specific RS is the SSB for receiving SIB1.

4. The device according to claim 1, wherein: When at least one of the following conditions is met, the terminal device considers that the CG occasion is available or there is the available CG occasion: RRC signaling configures the CG occasion; receiving the first MAC CE; A specific DCI is received.

5. The device according to claim 4, wherein: The specific DCI is used to schedule the PDSCH carrying the first MAC CE; and / or, The specific DCI is sent or received simultaneously with the first MAC CE. Sending or receiving simultaneously means sending or receiving in the same time slot, symbol or RB.

6. The device according to claim 1, wherein: The available CG occasion is on an uplink carrier, and the uplink carrier refers to at least one of the following: NUL (Normal Uplink) or SUL (Supplementary Uplink) configured with CG; NUL or SUL of the CG configured for the LTM process; NUL or SUL of the available CG configured for LTM process; An uplink carrier used by the terminal device for random access to obtain TA (timing advance); an uplink carrier indicated by the first MAC CE; The uplink carrier is selected based on the RSRP of the downlink path loss reference signal.

7. The device according to claim 1, wherein: The uplink transmission is at least one of an initial transmission, a repetition of an initial transmission, and a retransmission.

8. The device according to claim 7, wherein: If the uplink transmission includes retransmission, the sending unit starts a retransmission timer after the initial transmission is sent, and sends the retransmission when the retransmission timer expires.

9. The device according to claim 1, wherein: The sending unit determines whether to use the CG occasion to send the uplink transmission.

10. The device according to claim 1, wherein: The receiving unit receives information indicating that the uplink transmission is successfully received.

11. The device according to claim 10, wherein: The information is one of the following: RLC ACK of the uplink transmission; PDCCH addressed by C-RNTI; UE contention resolution ID MAC CE; MAC CE indicating the completion of LTM cell handover.

12. The device according to claim 11, wherein: When the information is a PDCCH addressed by the C-RNTI, the PDCCH is used to schedule one of the RLC ACK for the uplink transmission, the UE contention resolution ID MAC CE, and the MAC CE indicating the completion of the LTM cell handover.

13. The device according to claim 11, wherein: If the DG is used for initial transmission or retransmission, the information is a PDCCH addressed by a C-RNTI, and the PDCCH schedules a new transmission, or the PDCCH schedules a new transmission on a HARQ process ID.

14. A receiving device for uplink transmission, configured in a network device, comprising a source DU, a candidate or target DU and a CU, wherein: The device comprises: A sending unit, which sends a first MAC CE (Media Access Control Element) including candidate configuration information to a terminal device at a source DU; A receiving unit, which uses an available CG occasion (configured grant opportunity) or a DG (dynamic grant) in a candidate or target DU to receive an uplink transmission sent by the terminal device to the cell associated with the candidate configuration information.

15. The device according to claim 14, wherein: The sending unit sends the target cell identifier and beam information to the CU of the network device at the source DU; The sending unit sends the target cell identifier and the beam information to the candidate or target DU in the CU.

16. The device according to claim 15, wherein: The target cell identifier and beam information sent by the sending unit in the source DU are included in a UE CONTEXT MODIFICATION REQUIRED message, or are included in a first F1 message.

17. The device according to claim 16, wherein: The first F1 message is a UE CONTEXT SETUP REQUIRED message.

18. The device according to claim 15, wherein: The target cell identifier and beam information sent by the sending unit in the CU are included in the second F1 message.

19. The device according to claim 18, wherein: The second F1 message is a UE CONTEXT SETUP REQUEST message or a UE CONTEXT MODIFICATION REQUEST message.

20. The device according to claim 15, wherein: The target cell identifier includes candidate configuration information, or includes candidate configuration information and a cell index under the candidate configuration.

Images