Wireless communication methods, terminal devices, and network devices
Through the introduction of the first displacement in the non -ground communication network system, the physical downside -sharing channel receiving hybrid automatic transmission request feedback of the physical downward channels of multi -broadcasting services is determined to solve the time order of the delay, improve the business, and improve the business. 传输的可靠性。
Patent Information
- Application Number
- PCT/CN2023/108837
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-07-24
- Publication Date
- 2025-01-30
AI Technical Summary
In non-terrestrial communication network systems, there is a large delay, which makes it difficult to effectively enhance the timing of feedback of hybrid automatic retransmission requests received by physical downlink shared channels of multicast broadcast services, affecting the reliability of service transmission.
Introduce the first displacement to determine the time domain resources corresponding to the hybrid automatic transmission request feedback information received for the physical downside sharing channel for multiple broadcasting services. The exclusive offset of the group or the public offset of the community.
Through the introduction of the first displacement volume, it can effectively enhance the sequence of the hybrid automatic transmission request feedback that is accepted by the physical downside sharing channels for multiple broadcasting services, and improves the reliability of business transmission.
Smart Images

Figure CN2023108837_30012025_PF_FP_ABST
Abstract
Description
Wireless communication method, terminal device and network device Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art
[0002] Some communication systems (such as non-terrestrial network (NTN) systems) may have large delays. Therefore, such communication systems usually introduce offset values (such as K offset ) to enhance the timing relationship in the communication system.
[0003] To achieve network resource sharing and improve resource utilization, communication systems may introduce multicast broadcast services (MBS). For MBS physical downlink shared channel (PDSCH) reception, if the network side is configured with hybrid automatic repeat request (HARQ) feedback, how to enhance the timing of HARQ feedback for MBS PDSCH reception becomes a challenge.
[0004] Summary of the Invention
[0005] The present application provides a wireless communication method, terminal device, and network device. The following introduces various aspects of the present application.
[0006] In a first aspect, a method for wireless communication is provided, including: a first terminal device receives a first PDSCH for MBS; the first terminal device determines, based on a first offset, a time domain resource corresponding to a first PUCCH, and the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; wherein the first offset is determined based on one or more of the following: an offset exclusive to the first terminal device; an offset exclusive to the first terminal device group to which the first terminal device belongs; and a cell-common offset.
[0007] According to a second aspect, a method for wireless communication is provided, including: a network device sends a first PDSCH for MBS to a first terminal device; the network device determines the time domain resources corresponding to a first PUCCH based on a first offset, and the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; wherein the first offset is determined based on one or more of the following: an offset exclusive to the first terminal device; an offset exclusive to the first terminal device group to which the first terminal device belongs; and a cell-common offset.
[0008] According to a third aspect, a terminal device is provided, which is a first terminal device, and includes: a receiving module for receiving a first PDSCH for MBS; a determination module for determining, based on a first offset, a time domain resource corresponding to a first PUCCH, and the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; wherein the first offset is determined based on one or more of the following: an offset exclusive to the first terminal device; an offset exclusive to the first terminal device group to which the first terminal device belongs; and a cell-common offset.
[0009] In a fourth aspect, a network device is provided, including: a sending module for sending a first PDSCH for MBS to a first terminal device; a determination module for determining the time domain resources corresponding to a first PUCCH based on a first offset, and the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; wherein the first offset is determined based on one or more of the following: an offset exclusive to the first terminal device; an offset exclusive to the first terminal device group to which the first terminal device is located; and a cell-common offset.
[0010] In a fifth aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.
[0011] In the sixth aspect, a network device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the second aspect.
[0012] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided in the embodiment of the present application.
[0013] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a computer to execute part or all of the steps in the methods of the above aspects.
[0014] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a computer to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.
[0015] In a tenth aspect, an embodiment of the present application provides a computer program, which can be operated to enable a computer to execute part or all of the steps in the methods of the above aspects.
[0016] In the eleventh aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.
[0017] In this embodiment of the present application, a first offset is introduced to enhance the timing of HARQ feedback for PDSCH reception of MBS. The determination of the first offset is related to one or more of the following: a terminal device-specific offset, a terminal device group-specific offset, and a cell-common offset. The introduction of the first offset helps ensure that HARQ feedback for PDSCH reception of MBS can be smoothly transmitted, thereby improving the reliability of MBS service transmission. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG1A is an exemplary diagram of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.
[0019] FIG1B is another exemplary diagram of a system architecture of a wireless communication system to which embodiments of the present application may be applied.
[0020] FIG1C is another example diagram of the system architecture of a wireless communication system to which the embodiments of the present application may be applied.
[0021] FIG2 is an example diagram of a transparent forwarding NTN network architecture.
[0022] FIG3 is a diagram showing an example of a regeneration and forwarding NTN network architecture.
[0023] FIG4A is an example diagram of the time delay of an uplink signal reaching a network device when there is no TA.
[0024] FIG4B is an example diagram of the time delay of an uplink signal reaching a network device when TA exists.
[0025] FIG5 is a diagram showing an example of the timing relationship of the NTN system.
[0026] FIG6 is another example diagram of the timing relationship of the NTN system.
[0027] FIG. 7 is a diagram illustrating an example of a PTP transmission mode of an MBS.
[0028] FIG8 is a diagram illustrating an example of a PTM transmission mode of an MBS.
[0029] FIG9 is a flow chart of a wireless communication method provided in an embodiment of the present application.
[0030] FIG10 is an example diagram of a possible implementation method for determining the first offset provided in an embodiment of the present application.
[0031] FIG11 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.
[0032] FIG12 is a schematic diagram of the structure of the network device provided in an embodiment of the present application.
[0033] FIG13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0034] Communication system architecture
[0035] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, advanced long term evolution (LTE-A) system, new radio (NR) system, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system on unlicensed spectrum, NR-based access to unlicensed spectrum (NR-U) system on unlicensed spectrum, NTN system, universal mobile telecommunication system (UMTS), wireless local area networks (WLAN), wireless fidelity (WLAN), etc. fidelity, WiFi), fifth-generation communication (5G) systems or other communication systems, such as future communication systems, such as sixth-generation mobile communication systems, and satellite communication systems.
[0036] Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communications, but will also support, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication, etc. The embodiments of the present application can also be applied to these communication systems.
[0037] The communication system in the embodiment of the present application can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, and a standalone (SA) networking scenario.
[0038] The communication system in the embodiment of the present application can be applied to an unlicensed spectrum, where the unlicensed spectrum can also be considered as a shared spectrum; or, the communication system in the embodiment of the present application can also be applied to an authorized spectrum, where the authorized spectrum can also be considered as a dedicated spectrum.
[0039] The embodiments of the present application can be applied to NTN systems as well as terrestrial network (TN) systems. As an example and not a limitation, NTN systems include NR-based NTN systems and IoT-based NTN systems.
[0040] The embodiments of the present application describe various embodiments in conjunction with network devices and terminal devices, where the terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.
[0041] In an embodiment of the present application, the terminal device may be a station (STATION, ST) in a WLAN, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a next-generation communication system such as a terminal device in an NR network, or a terminal device in a future-evolved public land mobile network (PLMN) network, etc.
[0042] In the embodiments of the present application, a terminal device may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.
[0043] Alternatively, a UE can function as a base station. For example, a UE can act as a dispatching entity, providing sidelink signals between UEs in V2X or D2D applications. For example, a cell phone and a car can communicate with each other using sidelink signals. A cell phone and a smart home device can also communicate without relaying the communication signal through a base station.
[0044] As an example and not a limitation, in an embodiment of the present application, the terminal device may be a wearable device. Wearable devices may also be referred to as wearable smart devices, which are a general term for wearable devices that are intelligently designed and developed using wearable technology for daily wear, such as glasses, gloves, watches, clothing, and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothes or accessories. Wearable devices are not only hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are fully functional, large in size, and can achieve complete or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.
[0045] In the embodiments of the present application, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable, or vehicle-mounted; it can also be deployed on the water (such as a ship, etc.); it can also be deployed in the air (such as on an airplane, balloon, and satellite, etc.). In the embodiments of the present application, the terminal device can be fixed or mobile.
[0046] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station may broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmitting and receiving point (TRP), transmitting point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station may be a macro base station, a micro base station, a relay node, a donor node, or the like, or a combination thereof. The base station may also refer to a communication module, modem or chip provided in the aforementioned device or apparatus. The base station may also be a mobile switching center and a device-to-device D2D, vehicle-to-everything (V2X), machine-to-machine (M2M) communication device that performs the base station function, a network side device in a 6G network, a device that performs the base station function in a future communication system, etc. The base station may support networks with the same or different access technologies. The embodiments of the present application do not limit the specific technology and specific device form adopted by the network equipment.
[0047] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.
[0048] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.
[0049] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.
[0050] As an example and not a limitation, in an embodiment of the present application, the network device may have a mobile feature, for example, the network device may be a mobile device. In some embodiments of the present application, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. In some embodiments of the present application, the network device may also be a base station set up in a location such as land or water.
[0051] In an embodiment of the present application, a network device may provide services for a cell, and a terminal device may communicate with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell may be a cell corresponding to a network device (e.g., a base station). The cell may belong to a macro base station or a base station corresponding to a small cell. The small cells here may include: metro cells, micro cells, pico cells, femto cells, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
[0052] For example, Figure 1A is a schematic diagram of the architecture of a communication system provided in an embodiment of the present application. As shown in Figure 1A, the communication system 100 may include a network device 110, which may be a device that communicates with a terminal device 120 (or also referred to as a communication terminal or terminal). The network device 110 may provide communication coverage for a specific geographic area and may communicate with terminal devices located within the coverage area.
[0053] Figure 1A exemplarily shows a network device and two terminal devices. In some embodiments of the present application, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.
[0054] For example, FIG1B is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG1B , a terminal device 1101 and a satellite 1102 are included, and wireless communication can be performed between the terminal device 1101 and the satellite 1102. The network formed between the terminal device 1101 and the satellite 1102 can also be referred to as an NTN. In the architecture of the communication system shown in FIG1B , the satellite 1102 can have the function of a base station, and the terminal device 1101 and the satellite 1102 can communicate directly. In the system architecture, the satellite 1102 can be referred to as a network device. In some embodiments of the present application, a plurality of network devices 1102 may be included in the communication system, and each network device 1102 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.
[0055] For example, FIG1C is a schematic diagram of the architecture of another communication system provided in an embodiment of the present application. Referring to FIG1C , it includes a terminal device 1201, a satellite 1202, and a base station 1203. Wireless communication can be performed between the terminal device 1201 and the satellite 1202, and communication can be performed between the satellite 1202 and the base station 1203. The network formed between the terminal device 1201, the satellite 1202, and the base station 1203 can also be referred to as an NTN. In the architecture of the communication system shown in FIG1C , the satellite 1202 may not have the function of a base station, and the communication between the terminal device 1201 and the base station 1203 needs to be transferred through the satellite 1202. In this system architecture, the base station 1203 can be referred to as a network device. In some embodiments of the present application, a plurality of network devices 1203 may be included in the communication system, and each network device 1203 may include other number of terminal devices within its coverage area, which is not limited in the embodiments of the present application.
[0056] It should be noted that Figures 1A-1C are only examples of the system to which the present application is applicable. Of course, the method shown in the embodiment of the present application can also be applied to other systems, such as 5G communication systems, LTE communication systems, etc., and the embodiment of the present application does not make specific limitations on this.
[0057] In some embodiments of the present application, the wireless communication system shown in Figures 1A-1C may also include other network entities such as a mobility management entity (MME) and an access and mobility management function (AMF), but the embodiments of the present application are not limited to this.
[0058] It should be understood that in the embodiments of the present application, a device having a communication function in a network / system may be referred to as a communication device. Taking the communication system 100 shown in FIG1A as an example, the communication device may include a network device 110 and a terminal device 120 having a communication function. The network device 110 and the terminal device 120 may be the specific devices described above and will not be described in detail here. The communication device may also include other devices in the communication system 100, such as a network controller, a mobility management entity, and other network entities, which are not limited in the embodiments of the present application.
[0059] 5G application scenarios
[0060] With the increasing demand for speed, latency, high-speed mobility, and energy efficiency, coupled with the increasing diversity and complexity of future services, the 3rd Generation Partnership Project (3GPP), an international standards organization, has begun developing 5G. The main application scenarios for 5G are enhanced mobile broadband (eMBB), ultra-reliable low latency communications (URLLC), and massive machine-type communications (mMTC).
[0061] On the one hand, eMBB still aims to provide users with multimedia content, services, and data, and demand for this is growing rapidly. On the other hand, since eMBB can be deployed in different scenarios, such as indoors, in urban areas, and in rural areas, its capabilities and requirements vary greatly. Therefore, it cannot be generalized and requires detailed analysis based on specific deployment scenarios.
[0062] A key feature of URLLC is low latency. In this scenario, connection latency can be as short as 1 millisecond or less. It also supports high-reliability connections at high speeds. For example, at speeds of 500 km / h, reliability can reach 99.999%. Typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), and traffic safety.
[0063] Typical characteristics of mMTC include high connection density, small data volumes, latency-insensitive services, low module costs, and long service life. Based on this, mMTC can include one or more of the following communications: industrial wireless sensor networks, video surveillance scenarios, and wearable devices.
[0064] Radio resource control (RRC) status
[0065] Currently, the protocol defines three RRC states of terminal devices: RRC connected (RRC_CONNECTED) state, RRC idle (RRC_IDLE) state and RRC inactive (RRC_INACTIVE) state.
[0066] The RRC connection state may refer to the state in which the terminal device is in when the RRC release is not performed after the random access process is completed. An RRC connection exists between the terminal device and the network device, and a terminal device access stratum (AS) context exists between the network device and the terminal device. In the RRC connection state, the terminal device can perform data transmission with the network device, such as downlink data transmission and / or uplink data transmission. Alternatively, the terminal device can also perform terminal device-specific data channel and / or control channel transmission with the network device to transmit specific information or unicast information of the terminal device.
[0067] In the RRC connected state, the network device can determine the cell-level location information of the terminal device, that is, the network device can determine the cell to which the terminal device belongs. In addition, the mobility management of the terminal device in the RRC connected state can be controlled by the network device, that is, the mobility of the terminal device in the RRC connected state is the mobility controlled by the network device.
[0068] The RRC idle state refers to the state of a terminal device when it is resident in a cell but not performing random access. A terminal device typically enters the RRC idle state after being powered on or after RRC release. In the RRC idle state, there is no RRC connection between the terminal device and the network device, the network device does not store the AS context of the terminal device, and no connection is established between the network device and the core network for the terminal device. If the terminal device needs to enter the RRC connected state from the RRC idle state, it needs to initiate the RRC connection establishment process.
[0069] In the RRC Idle state, the core network (CN) can send a paging message to the terminal device. In other words, the paging process can be triggered by the CN. Optionally, the paging area can also be configured by the CN. The mobility management of the terminal device in the RRC Idle state includes cell selection / cell reselection based on the terminal device.
[0070] The RRC inactive state is a new RRC state defined to reduce air interface signaling, quickly restore wireless connections, and quickly restore data services. The RRC inactive state is a state between the RRC connected state and the RRC idle state (that is, the RRC inactive state is different from the RRC connected state and the RRC idle state). The terminal device has previously entered the RRC connected state and then released the RRC connection with the network device, but the network device saves the AS context of the terminal device. In addition, the connection established between the network device and the core network for the terminal device has not been released, that is, the user plane bearer and control plane bearer between the RAN and the CN are still maintained, that is, there is a connection between CN-NR.
[0071] In the RRC inactive state, the RAN can send paging messages to the terminal device, meaning that the paging process can be triggered by the RAN. RAN-based paging areas are managed by the RAN, and network equipment can determine the terminal device's location based on the RAN's paging area level. Mobility management for terminal devices in the RRC inactive state includes terminal-based cell selection and reselection.
[0072] NTN
[0073] The Third Generation Partnership Project (3GPP) is currently researching NTN technology. NTN typically uses satellite communications to provide communication services to terrestrial users. Compared to terrestrial communication networks (e.g., terrestrial cellular networks), satellite communications offer many unique advantages.
[0074] First, satellite communications are not restricted by user geography. For example, conventional terrestrial communication networks cannot cover areas where network equipment cannot be deployed, such as oceans, mountains, and deserts. Alternatively, terrestrial communication networks cannot cover certain areas due to sparse populations. However, satellite communications, because a single satellite can cover a large ground area and orbits the Earth, theoretically, every corner of the Earth can be covered by a satellite communication network.
[0075] Secondly, satellite communications have significant social value. They can provide low-cost coverage to remote, mountainous areas and impoverished countries and regions, enabling people in these areas to enjoy advanced voice communications and mobile internet technologies. From this perspective, satellite communications help narrow the digital divide with developed regions and promote their development.
[0076] Again, satellite communication has a long distance, and the communication cost does not increase significantly with the increase of communication distance.
[0077] Finally, satellite communications are highly stable and not affected by natural disasters.
[0078] Communication satellites can be divided into LEO satellites, MEO satellites, GEO satellites, HEO satellites, etc. according to the different orbital altitudes. At the current stage, the main research is on LEO satellites and GEO satellites.
[0079] LEO satellites typically operate at altitudes between 500 and 1500 km. Accordingly, their orbital period is approximately 1.5 to 2 hours. For LEO satellites, the signal propagation delay for single-hop communication between users is typically less than 20 milliseconds. The maximum satellite visibility time for LEO satellites is approximately 20 minutes. LEO satellites offer advantages such as short signal propagation distances, low link loss, and low transmit power requirements for terminal devices.
[0080] GEO satellites orbit at an altitude of approximately 35,786 km. They orbit the Earth every 24 hours. For GEO satellites, the signal propagation delay for single-hop communication between users is typically about 250 milliseconds.
[0081] To ensure satellite coverage and increase the capacity of the entire satellite communication system, satellites typically use multiple beams to cover the ground. Therefore, a single satellite can form dozens or even hundreds of beams to cover the ground. A single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.
[0082] Currently, NTN systems can include NR NTN systems and IoT NTN systems.
[0083] NTN Network Architecture
[0084] The NTN network architecture may include the following network elements: gateway, feeder link, service link and satellite.
[0085] The NTN network architecture may include one or more gateways, which may be used to connect satellites and terrestrial public networks.
[0086] A feeder link may refer to a link for communication between a gateway and a satellite.
[0087] The service link may refer to a link for communication between a terminal device and a satellite.
[0088] In terms of the functions provided by satellites, they can be categorized as those with transparent payloads or those with regenerative payloads. Transparent payload satellites provide only radio frequency filtering, frequency conversion, and amplification. In other words, transparent payload satellites transparently forward signals without altering the waveform of the transmitted signal. Regenerative payload satellites, in addition to providing radio frequency filtering, frequency conversion, and amplification, can also provide one or more of the following functions: demodulation, decoding, routing, conversion, encoding, and modulation. Regenerative payload satellites can have some or all of the functions of a base station. Depending on the functions provided by satellites in an NTN network, NTN network architectures can be categorized as either transparent or regenerative. Figures 2 and 3 provide example diagrams of transparent and regenerative payload NTN architectures, respectively.
[0089] In some embodiments, the NTN network architecture may further include inter-satellite links (ISLs). For example, ISLs may exist in a regenerative forwarding NTN network architecture.
[0090] Timing Advance (TA)
[0091] A key feature of uplink transmission is orthogonal multiple access (MA) across different devices in time and frequency. This means that uplink transmissions from different devices in the same cell do not interfere with each other. To ensure orthogonality in uplink transmissions and avoid intra-cell interference, network equipment requires that signals from different devices at the same time but using different frequency resources arrive at the network equipment at essentially aligned times. To ensure time synchronization on the network equipment side, communication systems (e.g., LTE / NR) can support an uplink TA mechanism.
[0092] In a communication system that supports uplink TA, the uplink and downlink clocks on the network device are identical, while those on the terminal device are offset, and different terminal devices have different uplink TA values. By appropriately controlling the offset for each terminal device, the network device can control the time it takes for uplink signals from different terminal devices to reach the network device. Terminal devices farther from the network device experience greater transmission delays and therefore need to send uplink data earlier than closer terminal devices.
[0093] Figures 4A and 4B respectively show the time delay of the uplink signal reaching the network device in the absence of TA and the time delay of the uplink signal reaching the network device in the presence of TA. As shown in Figure 4A, in the absence of TA, the time at which the uplink signals sent by different terminal devices (for example, terminal devices at different distances from the network device) arrive at the network device is inconsistent, which may cause interference within the cell. After the introduction of TA, see Figure 4B, different terminal devices are configured with different uplink TAs, so that the uplink signals sent by different terminal devices arrive at the network device at the same time, which is conducive to avoiding interference within the cell.
[0094] The network device can determine the TA value of each terminal device by measuring the uplink transmission of the terminal device. The network device can send a TA command to the terminal device to notify the terminal device of its corresponding TA value. For example, the network device can send a TA command to the terminal device in two ways, as follows:
[0095] Method 1: Acquisition of initial TA: During the random access process, the network device can determine the TA value by measuring the received preamble and send it to the terminal device through the Timing Advance Command field of the random access response (RAR) message.
[0096] Method 2: Adjustment of TA in RRC connection state: Although the terminal device and the network device have achieved uplink synchronization during the random access process, the timing of the uplink signal reaching the network device may change over time. Therefore, the terminal device needs to continuously update its uplink TA amount to maintain uplink synchronization. If the TA of a terminal device needs to be corrected, the network device can send a TA command (Timing Advance Command) to the terminal device, requesting it to adjust the uplink timing. In some implementations, the TA command is sent by the network device to the terminal device through a media access control control element (MAC CE). This MAC CE can also be called a TA command MAC CE (i.e., a MAC CE carrying a TA command).
[0097] In a CA scenario, a terminal device may need to use different TAs for different uplink carriers. Therefore, the standard introduces timing advance groups (TAGs). Network equipment can configure up to four TAGs for each cell group of a terminal device, and a TAG associated with that serving group for each serving cell. In some implementations, the terminal device can maintain a separate TA for each TAG.
[0098] Timing relationships in NTN systems
[0099] In TN systems, signal propagation delay is typically less than 1ms. In NTN systems, due to the long distance between terminal devices and satellites (or network equipment), signal propagation delay can be significantly longer, ranging from tens to hundreds of milliseconds, depending on the satellite's orbital altitude and the type of satellite communication service. Therefore, to handle this significant propagation delay, the timing relationship in NTN systems needs to be enhanced compared to NR systems.
[0100] As with NR systems, in NTN systems, terminal devices must consider the impact of time delay (TA) during uplink transmission. In an NTN system, when a terminal device is scheduled for uplink transmission in time slot n, it considers the round-trip propagation delay and transmits the uplink signal in advance, ensuring that the uplink signal reaches the network device in time slot n. Due to the significant propagation delay in NTN systems, the range of TA values is also relatively large. Specifically, the timing relationship in an NTN system may include two scenarios, as shown in Figures 5 and 6.
[0101] Case 1: As shown in Figure 5, the downlink time slot and uplink time slot on the network device side are aligned. Accordingly, in order to align the uplink transmission of the terminal device with the uplink time slot on the network device side, the terminal device needs to use a larger TA value. Therefore, when performing uplink transmission, a larger offset value (or offset, offset parameter, etc.) needs to be introduced into the system. This offset value can be, for example, K offset express.
[0102] Case 2: As shown in Figure 6, there is an offset between the downlink and uplink timeslots on the network device side. In this case, to align the terminal device's uplink transmission with the network device's uplink timeslot, the terminal device only needs a smaller TA value. However, in Case 2, the network device may require additional scheduling to handle the corresponding scheduling timing, which is more complex.
[0103] Timing relationship of NR system
[0104] In the NR system, there are many communication processes with timing relationships. The following examples introduce the timing relationships of several communication processes in the NR system.
[0105] PDSCH reception timing: When the terminal device is scheduled (such as scheduled by downlink control information (DCI)) to receive PDSCH, the scheduling information (such as DCI) includes the indication information of K0, and K0 is used to determine the time domain unit (such as time slot) for transmitting the PDSCH. The following is an introduction using the time domain unit as the time slot as an example, but the time domain unit can also be other time domain units other than the time slot, such as subframes, symbols, etc. For example, if the terminal device receives the scheduling information on time slot n, then the time slot allocated to the terminal device for PDSCH transmission is time slot Among them, K0 is determined according to the subcarrier spacing of PDSCH, μ PDSCH and μ PDCCH Used to determine the subcarrier spacing configured for PDSCH and PDCCH respectively. The value range of K0 is 0 to 32.
[0106] DCI-scheduled physical uplink shared channel (PUSCH) transmission timing: When a terminal device is scheduled by DCI to transmit PUSCH, the DCI includes K2 indication information, which is used to determine the time slot for transmitting the PUSCH. For example, if the terminal device receives the scheduled DCI on time slot n, the time slot allocated to the terminal device for PUSCH transmission is time slot n. Among them, K2 is determined according to the subcarrier spacing of PUSCH, μ PDSCH and μ PDCCH Used to determine the subcarrier spacing configured for PUSCH and PDCCH respectively. The value range of K2 is 0 to 32.
[0107] Transmission timing of PUSCH scheduled by random access response (RAR) grant: For the time slot scheduled for PUSCH transmission by RAR grant, if the terminal device initiates physical random access channel (PRACH) transmission, and the end position of the PDSCH including the RAR grant message received by the terminal device is in time slot n, then the terminal device can transmit the PUSCH scheduled by RAR grant in time slot n+K2+Δ, where K2 and Δ are agreed upon by the protocol.
[0108] Transmission timing of HARQ feedback information on the physical uplink control channel (PUCCH): For the time slot of PUCCH transmission, if the end position of a PDSCH reception is in time slot n or the end position of a PDCCH reception indicating a semi-persistent scheduling (SPS) PDSCH release is in time slot n, then the terminal device should transmit the corresponding HARQ feedback information (such as HARQ-ACK information) on the PUCCH resource in time slot n+K1, where K1 is the number of time slots. As an implementation method, K1 can be indicated by the PDSCH-to-HARQ-timing-indicator information field in the DCI format, or can be provided by the dl-DataToUL-ACK parameter. It should be noted that when K1=0, the last time slot of PUCCH transmission overlaps with the time slot of PDSCH reception or PDCCH reception indicating SPS PDSCH release.
[0109] Activation timing of medium access control element (MAC CE): When the HARQ feedback information corresponding to the PDSCH including the MAC CE command is transmitted on time slot n, the corresponding behavior indicated by the MAC CE command and the downlink configuration assumed by the terminal device should be activated from time slot n. The first time slot after Indicates the number of time slots in each subframe when the subcarrier spacing is configured as μ.
[0110] Channel state information (CSI) transmission timing on PUSCH: The CSI transmission timing on PUSCH is the same as the transmission timing of DCI-scheduled PUSCH transmission in general.
[0111] CSI reference resource timing: The CSI reference resource for reporting CSI in uplink time slot n′ is based on the timing of a single downlink time slot nn. CSI_ref Certain. Among them, μ DL and μ UL The subcarrier spacing configurations for downlink and uplink respectively. CSI_ref The value of depends on the type of CSI reporting.
[0112] Aperiodic sounding reference signal (SRS) transmission timing: If a terminal device receives a DCI-triggered aperiodic SRS in time slot n, the terminal device can transmit the SRS in time slot The aperiodic SRS in each triggered SRS resource set is transmitted on the tx_ssrv_tx ... SRS and μ PDCCH They are respectively the subcarrier spacing configuration of the triggered SRS transmission and the PDCCH carrying the triggering command.
[0113] Timing enhancement of NTN systems
[0114] The PDSCH reception timing in the NTN system is only affected by the timing of the downlink receiving side and is not affected by the large transmission round-trip delay in the NTN system. Therefore, the timing relationship of PDSCH reception in the NR system can be reused in the NTN system.
[0115] For other timings affected by the interaction between downlink reception and uplink transmission, in order to work properly in the NTN system, or in other words, to overcome the large transmission delay in the NTN system, the timing relationship in the NTN system needs to be enhanced. A simple solution is to introduce an offset value in the system. The offset value can be expressed as K offset This offset value can then be applied to the relevant timing relationships.
[0116] In some embodiments, the offset value may be a cell-common offset value broadcast by the network device. In some embodiments, the network device may also configure a terminal device-specific offset value for the terminal device. In some embodiments, if the network device does not configure a terminal device-specific offset value for the terminal device, the terminal device may use the cell-common offset value.
[0117] In some embodiments, the network device may refer to the TA when configuring the offset value. For example, the cell-common offset value broadcast by the network device may be configured based on the maximum TA supported in the cell. Alternatively, the terminal device-specific offset value may be configured based on the TA of the terminal device.
[0118] Like NR systems, NTN systems also have many communication processes with timing relationships. The following examples illustrate the timing relationships of several communication processes in NTN systems.
[0119] The transmission timing of the DCI-scheduled PUSCH (including the CSI transmitted on the PUSCH): If the terminal device receives the scheduled DCI on time slot n, the time slot allocated to the terminal device for PUSCH transmission is time slot
[0120] RAR grant-scheduled PUSCH transmission timing: For the time slot scheduled by RAR grant for PUSCH transmission, the terminal device can transmit in time slot n+K2+Δ+K offset The PUSCH is transmitted on the
[0121] Transmission timing of HARQ feedback information on PUCCH: For the time slot of PUCCH transmission, the terminal device can transmit HARQ feedback information in time slot n+K1+K offset The corresponding HARQ feedback information is transmitted on the PUCCH resources within the HARQ channel.
[0122] MAC CE activation timing: When the HARQ feedback information corresponding to the PDSCH including the MAC CE command is transmitted on time slot n, the corresponding behavior indicated by the MAC CE command and the downlink configuration assumed by the terminal device can be obtained from time slot n. It takes effect in the first time slot after the 1st time slot, where X may be determined by the terminal equipment capability in the NTN and may not be 3.
[0123] CSI reference resource timing: The CSI reference resource for reporting CSI in uplink time slot n′ can be based on a single downlink time slot. Sure.
[0124] Aperiodic SRS transmission timing: If the terminal device receives the DCI-triggered aperiodic SRS in time slot n, the terminal device can transmit the SRS in time slot The aperiodic SRS in each triggered SRS resource set is transmitted.
[0125] MBS
[0126] Traditional video software transmits data content via unicast. Therefore, when there are too many users, the network becomes overwhelmed and congested. In other words, if multiple users are simultaneously viewing video content within a wireless cell, the wireless downlink rate may become a bottleneck. As a possible implementation, if multiple users are simultaneously viewing video content within a wireless cell, broadcasting within the cell can ensure smooth viewing.
[0127] Therefore, to achieve network resource sharing and improve resource utilization, some communication systems (such as NR systems) have introduced MBS. MBS is a service for multiple terminal devices, such as television broadcasting, live broadcasting, public safety services, and batch software updates. The introduction (or development) of MBS enables multimedia content to be delivered to terminal devices via broadcast or multicast, allowing users to watch television broadcasts or receive data push services anytime and anywhere.
[0128] MBS is called slightly differently depending on the connection state (RRC state) of the terminal device receiving the MBS. For example, the physical layer design of Rel-17NR MBS also uses slightly different names for MBS.
[0129] In some implementations, multicast refers to the network sending MBS services to a group of connected terminal devices. Accordingly, the network device can send a group-common PDCCH to schedule a group-common PDSCH. In multicast services, the group-common PDCCH may refer to the PDCCH being scrambled using the group radio network temporary identifier (G-RNTI) or the group-configured scheduling RNTI (G-CS-RNTI), or in other words, the CRC in the PDCCH is scrambled using the G-RNTI or G-CS-RNTI.
[0130] In some implementations, broadcast means that the network sends MBS services to terminal devices within the coverage. The terminal devices within the network coverage can be terminal devices in a connected state or terminal devices in a non-connected state (such as RRC idle state or RRC inactive state). Accordingly, the network device can send a group-common PDCCH to schedule a group-common PDSCH. In the broadcast service, the group-common PDCCH may mean that the PDCCH is scrambled using the multicast control channel RNTI (multicast control channel RNTI, MCCH-RNTI) or G-RNTI, or that the CRC in the PDCCH is scrambled using the MCCH-RNTI or G-RNTI.
[0131] For connected terminal devices, MBS multicast scheduling (MBS PDSCH scheduling) can support different transmission modes (or transmission modes), or in other words, MBS can support different transmission modes. Taking the NR system as an example, MBS multicast scheduling can support point-to-point (PTP) transmission mode and point-to-multipoint (PTM) transmission mode. The following describes the MBS transmission modes in conjunction with Figures 7 and 8.
[0132] Figure 7 shows an example diagram of the PTP transmission mode of MBS. As shown in Figure 7, for a terminal device in a connected state (such as terminal device A), the network device can send a dedicated PDCCH to this terminal device, and the dedicated PDCCH is used to indicate the dedicated PDSCH of the terminal device. In some implementations, the dedicated PDCCH of the terminal device may refer to the PDCCH (or the CRC of the PDCCH) being scrambled with the dedicated RNTI (for example, C-RNTI) of the terminal device. In addition, the PDSCH indicated by the dedicated PDCCH can be scrambled with the dedicated RNTI of the same terminal device. In some embodiments, the PTP transmission mode can only be used as a transmission mode for retransmission in MBS.
[0133] Figure 8 shows an example diagram of the PTM transmission mode for MBS. As shown in Figure 8, for a group of connected terminal devices (such as terminal device A, terminal device B, and terminal device C), the network device can send a group-common PDCCH to this group of terminal devices. This group-common PDCCH is used to schedule the group PDSCH. In some embodiments, the group-common PDCCH may refer to a PDCCH (or a CRC of the PDCCH) that is scrambled using a group-common RNTI. In addition, the PDSCH scheduled by the group-common PDCCH is scrambled using the same group-common RNTI.
[0134] During MBS retransmission, the network device can configure different HARQ feedback modes for the terminal device. For example, the network device can configure two HARQ feedback modes for the connected terminal device, namely the first HARQ feedback mode (ACK / NACK mode) and the second HARQ feedback mode (NACK-only mode).
[0135] As an implementation method, when a network device configures a terminal device with the first HARQ feedback mode, the network device can schedule the initial transmission of a transport block (TB) for a group of terminal devices using the PTM transmission mode. Subsequently, the network device can schedule the retransmission of this TB using the PTM transmission mode or the PTP transmission mode based on the feedback status of each terminal device in the group (including feedback ACK, feedback NACK, or no feedback).
[0136] As another implementation, when the network device configures the second HARQ feedback mode for the terminal device, the network device can schedule the initial transmission of a TB for a group of terminal devices using the PTM transmission mode. Subsequently, if at least one terminal device in the group feedbacks a NACK, the network device can schedule the retransmission of the TB using the PTM transmission mode.
[0137] As mentioned above, some communication systems (such as NTN systems) may have large delays. In order to adapt to the large delay of terminal equipment, such communication systems usually introduce offset values (such as K offset ) to enhance the timing relationship affected by the interaction between downlink reception and uplink transmission. As a possible implementation method, some communication systems with large latency (such as NTN systems) may support MBS. In this case, for MBS PDSCH reception, if HARQ feedback is configured on the network side, the timing of HARQ feedback for MBS PDSCH reception also needs to be enhanced. Therefore, how to enhance the timing of HARQ feedback for MBS PDSCH reception is a problem that needs to be solved.
[0138] To address the above issues, embodiments of the present application provide a wireless communication method, terminal device, and network device that can help the terminal device and network device determine an offset value corresponding to HARQ feedback for PDSCH reception of an MBS service. This helps ensure that HARQ feedback for PDSCH reception of the MBS service can be smoothly transmitted, thereby improving the reliability of MBS service transmission. The following describes embodiments of the method of the present application in conjunction with the accompanying drawings.
[0139] The technical solutions provided by the embodiments of the present application can be applied to scenarios or communication systems with large delays. For example, the embodiments of the present application can be applied to NTN systems, but the embodiments of the present application are not limited thereto. The embodiments of the present application can also be applied to TN systems, such as certain scenarios with large delays in TN systems.
[0140] FIG9 is a flow chart of a wireless communication method provided by an embodiment of the present application. The method shown in FIG9 is described from the perspective of the interaction between a first terminal device and a network device. The first terminal device may be, for example, terminal device 120, terminal device 1101, or terminal device 1201 shown in FIG1A-FIG1C. The network device may be, for example, network device 110, satellite 1102, or network device 1203 shown in FIG1A-FIG1C. The method shown in FIG9 may include steps S910 and S920, which are described below.
[0141] In step S910 , the network device sends a first PDSCH for an MBS to a first terminal device.
[0142] In some embodiments, the first PDSCH for MBS can be understood as the first PDSCH being used to transmit MBS, or the first PDSCH carrying MBS-related information. For example, the first PDSCH can be used to transmit MBS data, or the first PDSCH carries MBS data.
[0143] In some embodiments, the network device may configure the first terminal device to feed back HARQ feedback information for the first PDSCH of the MBS. That is, after receiving the first PDSCH, the first terminal device may send the HARQ feedback information corresponding to the first PDSCH to the network device.
[0144] In some embodiments, the HARQ feedback information corresponding to the first PDSCH may be carried on the first PUCCH. In other words, the first PUCCH may be used to carry the HARQ feedback information corresponding to the first PDSCH. However, the present application is not limited thereto. As a possible implementation, the HARQ feedback information corresponding to the first PDSCH may be carried on the PUSCH. In other words, certain PUSCHs may also be used to carry the HARQ feedback information corresponding to the first PDSCH.
[0145] The embodiment of the present application does not limit the HARQ feedback mode corresponding to the first terminal device, or in other words, the embodiment of the present application does not limit the HARQ feedback mode configured by the network device for the first terminal device. Exemplarily, the HARQ feedback mode corresponding to the first terminal device can be the first HARQ feedback mode (ACK / NACK mode), or the HARQ feedback mode corresponding to the first terminal device can be the second HARQ feedback mode (NACK-only mode).
[0146] In some embodiments, the HARQ feedback mode corresponding to the first terminal device can be understood as the HARQ feedback mode corresponding to the first PDSCH, or the HARQ feedback mode corresponding to the first terminal device can be understood as the HARQ feedback mode configured by the network device for the first PDSCH of the first terminal device.
[0147] In some embodiments, if the HARQ feedback mode corresponding to the first PDSCH is the first HARQ feedback mode, the subsequent network device can use the PTM transmission mode or the PTP transmission mode to schedule the retransmission of the TB where the first PDSCH is located according to the feedback situation of the first terminal device (for example, feedback ACK, feedback NACK, or no feedback of any information).
[0148] In some embodiments, if the HARQ feedback mode corresponding to the first PDSCH is the second HARQ feedback mode, if the network device subsequently receives NACK information fed back by the first terminal device, the PTM transmission mode can be used to schedule the retransmission of the TB where the first PDSCH is located.
[0149] The HARQ feedback information corresponding to the first PDSCH in the embodiment of the present application is not specifically limited. For example, the HARQ feedback information corresponding to the first PDSCH may include HARQ-ACK information and / or HARQ-NACK information. Taking the HARQ feedback information corresponding to the first PDSCH carried on the first PUCCH as an example, the first PUCCH can carry HARQ-ACK information or HARQ-NACK information.
[0150] In step S920, the first terminal device determines the time domain resources corresponding to the first PUCCH based on the first offset.
[0151] In some embodiments, the first terminal device determines the time domain resources corresponding to the first PUCCH based on the first offset, which can be understood as the first terminal device determining the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH based on the first offset. In other words, the first terminal device determines the time domain resources corresponding to the first PUCCH based on the first offset, which can be understood as the first offset is used to determine the time domain resource position of the first terminal device transmitting the HARQ feedback information corresponding to the first PDSCH.
[0152] The embodiments of the present application do not limit the granularity (unit) of the time domain resources. The time domain resources mentioned in the embodiments of the present application may refer to one of a frame, a subframe, a time slot, and a symbol, for example. Of course, the time domain resources mentioned in the embodiments of the present application may also be time domain resources in a future communication system. Taking the time domain resource as a time slot as an example, the first terminal device can determine the time slot for transmitting the HARQ feedback information corresponding to the first PDSCH based on the first offset, or the first terminal device can determine the time slot for transmitting the first PUCCH based on the first offset.
[0153] As described above, in some embodiments, the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH. The following description will be based on the example of the HARQ feedback information corresponding to the first PDSCH being carried on the first PUCCH. However, the present application is not limited to this. For example, if the HARQ feedback information corresponding to the first PDSCH is carried on the PUSCH, the first terminal device can determine the time domain resource corresponding to the PUSCH based on the first offset.
[0154] In some embodiments, the network device also needs to determine the time domain resource that carries the HARQ feedback information corresponding to the first PDSCH, so as to receive the HARQ feedback information sent by the first terminal device on the corresponding time domain resource. In other words, the network device also needs to determine the time domain resource corresponding to the first PUCCH, so as to receive the first PUCCH sent by the first terminal device on the time domain resource corresponding to the first PUCCH.
[0155] That is to say, in an embodiment of the present application, the network device may also determine the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH according to the first offset, or determine the time domain resources corresponding to the first PUCCH according to the first offset.
[0156] In some embodiments, the first offset can be determined based on one or more of the following, or in other words, the determination of the first offset can be related to one or more of the following: an offset exclusive to the first terminal device, an offset exclusive to the first terminal device group to which the first terminal device belongs, and a cell common offset.
[0157] That is, the embodiments of the present application can determine the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH based on one or more of the following factors: a terminal device-specific offset, a terminal device group-specific offset, and a cell-common offset. Thus, the introduction of the first offset in the embodiments of the present application can enhance the timing of HARQ feedback received for the MBS PDSCH, which is beneficial for ensuring that the HARQ feedback received for the MBS PDSCH can be smoothly transmitted, thereby improving the reliability of MBS service transmission.
[0158] In some embodiments, the first offset may be determined based on one of the above factors, for example, the first offset is determined based on an offset specific to the first terminal device group, or the first offset is determined based on a cell-common offset.
[0159] In some embodiments, the first offset may be determined based on multiple (two or more) of the above factors. For example, the first offset may be determined based on an offset specific to the first terminal device group and an offset specific to the first terminal device, or the first offset may be determined based on an offset specific to the first terminal device group and a cell-common offset, etc.
[0160] In some embodiments, the first offset may be one or more of the following: an offset specific to the first terminal device, an offset specific to the first terminal device group, and a cell-common offset. That is, in some embodiments, the first offset is determined based on the offset specific to the first terminal device, which can be understood as the first offset being the offset specific to the first terminal device. In some embodiments, the first offset is determined based on the offset specific to the first terminal device group, which can be understood as the first offset being the offset specific to the first terminal device group. In some embodiments, the first offset is determined based on the cell-common offset, which can be understood as the first offset being the cell-common offset.
[0161] In some embodiments, determination of the first offset is related to a transmission mode corresponding to a first PDSCH for an MBS, or in other words, determination of the first offset is related to a transmission mode of the MBS.
[0162] In some embodiments, if the first PDSCH is a PDSCH corresponding to the PTM transmission mode, the first offset may be determined based on an offset specific to the first terminal device group.
[0163] In some embodiments, the first PDSCH being a PDSCH corresponding to the PTM transmission mode can be understood as the first PDSCH being scrambled using the G-RNTI or G-CS-RNTI. However, the present application is not limited thereto. For example, the first PDSCH can also be scrambled using the MCCH-RNTI.
[0164] In some embodiments, if the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset may be determined based on an offset specific to the first terminal device group.
[0165] In some embodiments, if the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset can be determined based on an offset specific to the first terminal device.
[0166] In some embodiments, the first PDSCH is a PDSCH corresponding to the PTP transmission mode, which can be understood as the first PDSCH being scrambled using the C-RNTI or CS-RNTI.
[0167] In some embodiments, in the scenario of HARQ retransmission corresponding to MBS, the first PDSCH may be a PDSCH corresponding to PTP transmission mode. In other words, in the scenario of HARQ retransmission corresponding to MBS, the network device may use PTP transmission mode to send the first PDSCH to the first terminal device.
[0168] In some embodiments, the determination of the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH may be related to other information in addition to the first offset. For example, the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH may be determined based on the first offset and a first parameter, and the first parameter may be used to determine the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH.
[0169] In some embodiments, the first parameter can be used to indicate an offset of the time domain resource so that the first terminal device determines the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH according to the end position of the first PDSCH reception and the first parameter. For example, the HARQ feedback information corresponding to the first PDSCH can be K+K after the end position of the first PDSCH reception. offset The transmission starts from the time domain resource, where K is the value of the first parameter, K offset For the first offset. Taking the time domain resource as a time slot as an example, the first parameter can be used to indicate the time slot offset. The value of the first parameter is K, and the value of the first offset is K offset , the end position of the first PDSCH reception is time slot n, then the HARQ feedback information corresponding to the first PDSCH can be in time slot n+K+K offset The transmission starts with the uplink resources (such as PUCCH resources).
[0170] In some embodiments, the first parameter is the K1 value corresponding to the transmission timing of the HARQ feedback information transmitted on the PUCCH mentioned above.
[0171] In some embodiments, the first parameter may be carried in a PDCCH. For example, the first parameter may be carried in a first PDCCH associated with a first PDSCH.
[0172] In some embodiments, the first parameter carried in the PDCCH may refer to the first parameter being carried in the DCI. As an implementation, the first parameter may be indicated by the PDSCH-to-HARQ-timing-indicator information field in the DCI format. As another implementation, the first parameter may be provided by the dl-DataToUL-ACK parameter.
[0173] In some embodiments, the offset specific to the first terminal device may be configured by the network device. As an implementation, the offset specific to the first terminal device may be indicated by the network device via a MAC CE.
[0174] In some embodiments, the cell common offset may be configured by a network device. As an implementation, the cell common offset may be indicated by the network device via broadcast.
[0175] In some embodiments, the offset specific to the first terminal device group may be configured by the network device. As one implementation, the offset specific to the first terminal device group may be configured by the network device based on dedicated signaling for the first terminal device group. As another implementation, the offset specific to the first terminal device group may be configured by the network device based on dedicated signaling for the first terminal device group.
[0176] In some embodiments, the first offset may be configured by a network device. For example, the network device may configure the first offset for the first terminal device (e.g., when the first terminal device is in a connected state). Taking the first offset as an offset exclusive to the first terminal device group as an example, the first offset may be configured by the network device through exclusive signaling of the first terminal device group or exclusive signaling of the first terminal device. However, the embodiments of the present application are not limited thereto. In some embodiments, the first offset may also be preconfigured or predefined by a protocol.
[0177] As mentioned above, the first offset can be determined based on one or more of an offset exclusive to the first terminal device group, an offset exclusive to the first terminal device, and a cell common offset. The following, in combination with Example 1 and Example 2, a detailed introduction is given to the determination of the first offset based on the offset exclusive to the first terminal device group and the determination of the first offset based on the cell common offset.
[0178] Embodiment 1: The first offset is determined based on the offset specific to the first terminal device group
[0179] In the first embodiment, the first offset may be, for example, an offset specific to the first terminal device group.
[0180] In the embodiment of the present application, different terminal device groups may be associated with or correspond to different group identifiers. In other words, the embodiment of the present application can identify which terminal device group the terminal device belongs to by the group identifier corresponding to the terminal device.
[0181] In some embodiments, the first terminal device group may be associated with or correspond to a first group identifier. In other words, the first terminal device group may be indicated (or identified) using the first group identifier. In some embodiments, each terminal device in the first terminal device group is associated with or corresponds to the first group identifier.
[0182] In some embodiments, the first group identifier may be used to scramble a first PDSCH sent by each terminal device in the first terminal device group.
[0183] In some embodiments, the first group identifier may include a G-RNTI or a G-CS-RNTI. However, the present application is not limited thereto, as long as the first group identifier can be used to perform RNTI scrambling on a group of terminal devices. For example, in some embodiments, the first group identifier may include an MCCH-RNTI, etc.
[0184] The embodiment of the present application does not limit the configuration granularity of the first offset. The first offset may be configured for a group of terminal devices, or the first offset may be configured for multiple groups of terminal devices.
[0185] In some embodiments, the first offset may correspond to the first group identifier. That is, embodiments of the present application may configure terminal device group-specific offsets for different terminal device groups. Alternatively, the terminal device group-specific offsets may correspond one-to-one with the group identifier, i.e., a terminal device group-specific offset may be configured for each group identifier. For example, the first offset corresponding to the first terminal device group may correspond to the first group identifier, and the second offset corresponding to the second terminal device group may correspond to the second group identifier.
[0186] In some embodiments, the first offset may correspond to multiple group identifiers. For example, the first offset may correspond to multiple group identifiers including the first group identifier. That is, the embodiment of the present application may configure the same first offset (i.e., the offset exclusive to the terminal device group) for multiple terminal device groups, that is, the same first offset may be configured for multiple group identifiers. In other words, the offset exclusive to the terminal device group may have a one-to-many correspondence with the group identifier. For example, the first offset may correspond to both the first group identifier and the second group identifier, wherein the first group identifier is the group identifier corresponding to the first terminal device group, and the second group identifier is the group identifier corresponding to the second terminal device group. In other words, the offset exclusive to the terminal device group corresponding to the first terminal device group and the second terminal device group may be the same.
[0187] In some embodiments, if the first offset corresponds to multiple group identifiers, the network device may simultaneously indicate the multiple group identifiers corresponding to the first offset.
[0188] In some embodiments, when the first terminal device is not configured with the first offset, the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH (such as the time domain resources corresponding to the first PUCCH) can be determined based on the cell common offset. In other words, in some embodiments, for a certain terminal device group or for a group identifier corresponding to a certain terminal device group, if the terminal device group or the group identifier corresponding to the terminal device group is not configured with an offset exclusive to the terminal device group corresponding thereto, the first offset can be determined based on the cell common offset (for example, using the cell common offset as the first offset).
[0189] In some embodiments, whether to configure the first offset is determined based on a condition, which may be related to HARQ feedback corresponding to the first PDSCH.
[0190] For example, whether to configure the first offset can be determined based on a first condition, which can be associated with whether HARQ feedback is enabled (or enabled) for the first group identifier, or in other words, the first condition can be associated with whether HARQ feedback is enabled for the first terminal device group.
[0191] In some embodiments, if HARQ feedback is enabled for the first group identifier (or for the first terminal device group), a first offset may be configured, i.e., the first offset may be configured for the first terminal device or the first terminal device group. In other words, the first offset may be configured for the first group identifier (or the first terminal device group) configured to enable HARQ feedback.
[0192] In some embodiments, the first offset can be configured only when HARQ feedback is enabled for the first group identifier (or for the first terminal device group). In other words, the first offset can be configured only for the first group identifier (or first terminal device group) configured to enable HARQ feedback.
[0193] In some embodiments, if HARQ feedback is not enabled for the first group identifier (or for the first terminal device group), the first offset may not be configured, that is, the first offset may not be configured for the first terminal device or the first terminal device group. In other words, the first offset cannot be configured for the first group identifier (or the first terminal device group) configured to disable HARQ feedback.
[0194] As mentioned above, the first offset can be configured by the network device. The embodiment of the present application does not limit the manner in which the network device configures the first offset. The following examples illustrate several manners for configuring the first offset.
[0195] As an implementation manner, the first offset may be configured based on a first signaling, which may be dedicated signaling for the first terminal device.
[0196] The embodiment of the present application does not limit the dedicated signaling of the first terminal device. Exemplarily, the dedicated signaling of the first terminal device may be, for example, RRC signaling (RRC dedicated signaling), MAC CE, PDCCH, etc., which are dedicated to the first terminal device.
[0197] The embodiments of the present application do not limit the scrambling method or carrying method of the dedicated signaling of the first terminal device. In some embodiments, the first signaling may be the dedicated RRC signaling of the terminal device, and the RRC signaling may be carried in the PDSCH scrambled by C-RNTI or CS-RNTI. In some embodiments, the first signaling may be the dedicated MAC CE of the terminal device, and the MAC CE may be carried in the PDSCH scrambled by C-RNTI or CS-RNTI. In some embodiments, the first signaling may be the dedicated PDCCH of the first terminal device, and the PDCCH may be scrambled based on C-RNTI or CS-RNTI.
[0198] As another implementation, the first offset may be configured based on a first signaling, which may be dedicated signaling for the first terminal device group.
[0199] The embodiment of the present application does not limit the dedicated signaling of the first terminal device group. Exemplarily, the dedicated signaling of the first terminal device group may be, for example, RRC signaling (RRC dedicated signaling), MAC CE, PDCCH, etc., which are dedicated to the first terminal device group.
[0200] The embodiments of the present application do not limit the scrambling method or carrying method of the exclusive signaling of the first terminal device group. In some embodiments, the first signaling may be the exclusive RRC signaling of the terminal device group, and the RRC signaling may be carried in the PDSCH scrambled by GC-RNTI or G-CS-RNTI. In some embodiments, the first signaling may be the exclusive MAC CE of the terminal device group, and the MAC CE may be carried in the PDSCH scrambled by GC-RNTI or G-CS-RNTI. In some embodiments, the first signaling may be the exclusive PDCCH of the first terminal device group, and the PDCCH may be scrambled based on GC-RNTI or G-CS-RNTI.
[0201] In some embodiments, the dedicated signaling of the first terminal device group may be scrambled in other ways. For example, the dedicated RRC signaling, MAC CE or PDCCH of the terminal device group may be scrambled using MCCH-RNTI.
[0202] The embodiment of the present application does not limit the indication method of the first offset, or in other words, the embodiment of the present application does not limit the signaling content of the signaling for configuring the first offset. The following takes the configuration of the first offset through the first signaling as an example to introduce the signaling content of the first signaling.
[0203] In some embodiments, the first signaling may be dedicated signaling for the first terminal device, or dedicated signaling for the first terminal device group.
[0204] In some embodiments, the first signaling may be used to determine the value of the first offset. In some embodiments, the value of the first offset configured by the first signaling may be an absolute value or a relative value, which is not limited in this embodiment of the present application.
[0205] In some embodiments, if the value of the first offset configured by the first signaling is a relative value, the embodiment of the present application does not limit the reference object corresponding to the first offset. For example, the first offset can be a relative value relative to the offset exclusive to the first terminal device, or a relative value relative to the common offset of the cell, etc.
[0206] Exemplarily, the first signaling can be used to configure one or more of the following: the value of the first offset, the absolute value of the first offset, the difference between the first offset and the cell-common offset, the increment of the first offset relative to the cell-common offset, the difference between the first offset and the offset specific to the first terminal device, and the increment of the first offset relative to the offset specific to the first terminal device.
[0207] In some embodiments, the difference between the first offset and the reference object (such as the cell common offset, the offset specific to the first terminal device) can be a positive number or a non-negative number. In some embodiments, the increment of the first offset relative to the reference object can be a positive number or a non-negative number. This embodiment of the present application is not limited to this.
[0208] As an example, the first signaling may be used to configure the absolute value of the first offset. For example, if the first signaling is dedicated to the first terminal device, the first signaling may be used to configure the absolute value of the first offset. Alternatively, if the first signaling is dedicated to the first terminal device group, the first signaling may be used to configure the absolute value of the first offset.
[0209] As another example, the first signaling can be used to configure the difference between the first offset and the cell-common offset or can be used to configure the increment of the first offset relative to the cell-common offset. In this case, the first terminal device can determine the first offset (i.e., the offset exclusive to the first terminal device group) based on the difference value (incremental value) carried in the first signaling and the cell-common offset.
[0210] Taking the difference value (incremental value) carried in the first signaling as the first incremental value as an example, as an implementation method, the first terminal device can determine the first offset according to the following formula: first offset = cell common offset + first incremental value; as another implementation method, the first terminal device can determine the first offset according to the following formula: first offset = cell common offset - first incremental value. In the embodiment of the present application, the first incremental value can be a positive number or a non-negative number.
[0211] In some embodiments, when the first signaling is dedicated signaling for the first terminal device, the first signaling may be used to configure the difference between the first offset and the cell-common offset or may be used to configure the increment of the first offset relative to the cell-common offset. In some embodiments, when the first signaling is dedicated signaling for the first terminal device group, the first signaling may be used to configure the difference between the first offset and the cell-common offset or may be used to configure the increment of the first offset relative to the cell-common offset.
[0212] As another example, the first signaling may be used to configure a difference between the first offset and an offset specific to the first terminal device, or may be used to configure an increment of the first offset relative to an offset specific to the first terminal device. In this case, the first terminal device may determine the first offset (i.e., the offset specific to the first terminal device group) based on the difference value (incremental value) carried in the first signaling and the offset specific to the first terminal device.
[0213] Taking the difference value (incremental value) carried in the first signaling as the second incremental value as an example, as one implementation method, the first terminal device can determine the first offset according to the following formula: first offset = first terminal device-specific offset + second incremental value; as another implementation method, the first terminal device can determine the first offset according to the following formula: first offset = first terminal device-specific offset - second incremental value. In this embodiment of the present application, the second incremental value can be a positive number or a non-negative number.
[0214] In some embodiments, when the first signaling is exclusive signaling for the first terminal device, the first signaling can be used to configure the difference between the first offset and the offset exclusive to the first terminal device or can be used to configure the increment of the first offset relative to the offset exclusive to the first terminal device.
[0215] For ease of understanding, a possible implementation method for determining the first offset is provided below in conjunction with FIG10. It should be understood that the example of FIG10 is not intended to limit the solution of the embodiment of the present application. For example, in the example of FIG10, the reference object corresponding to the first offset is the cell common offset, but the reference object corresponding to the first offset may also be other, such as an offset specific to the first terminal device.
[0216] As shown in Figure 10, when the network device does not configure the first offset for the first terminal device (i.e., the offset exclusive to the first terminal device group), the first terminal device can use the cell common offset to determine the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH. For example, the first terminal device can use the cell common offset to determine the time domain resources corresponding to the first PUCCH.
[0217] If the network device configures an incremental value of the first offset relative to the reference object for the first terminal device through the first signaling, the first terminal device can use the value of the reference object and the incremental value carried in the first signaling to determine the first offset, and determine the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH based on the first offset. Referring to Figure 10, at time T1, the network device configures an incremental value of 1 for the first terminal device, the first terminal device can determine the first offset based on the incremental value 1 and the cell-common offset (such as offset 1 shown in Figure 10), and determine the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH based on offset 1. At time T2, the network device configures an incremental value of 2 for the first terminal device, the first terminal device can determine the first offset based on the incremental value 2 and the cell-common offset (such as offset 2 shown in Figure 10), and determine the time domain resources carrying the HARQ feedback information corresponding to the first PDSCH based on offset 2.
[0218] In some embodiments, the first terminal device may determine the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH based on the first offset (i.e., the offset specific to the first terminal device group) and the first parameter. For an introduction to the first parameter, please refer to the previous text and will not be repeated here for the sake of brevity.
[0219] As an example, if the first PDSCH is the PDSCH corresponding to the PTM transmission mode, that is, the first PDSCH scrambled by G-RNTI or G-CS-RNTI, the first terminal device can use the offset specific to the terminal device group corresponding to the G-RNTI or G-CS-RNTI, and the first parameter to determine the time domain resources carrying the HARQ feedback information of the first PDSCH.
[0220] As another example, if the first PDSCH is the PDSCH corresponding to the PTP transmission mode, that is, the first PDSCH scrambled by C-RNTI or CS-RNTI, the terminal device can use the offset and first parameter exclusive to the first terminal device group to determine the time domain resources carrying the HARQ feedback information of the first PDSCH.
[0221] As another example, if the first PDSCH is the PDSCH corresponding to the PTP transmission mode, that is, the first PDSCH scrambled by C-RNTI or CS-RNTI, the terminal device can use the offset and first parameter exclusive to the first terminal device to determine the time domain resources carrying the HARQ feedback information of the first PDSCH.
[0222] Embodiment 2: The first offset is determined based on the cell common offset
[0223] In the second embodiment, the first offset may be, for example, a cell common offset.
[0224] In some embodiments, the network device may configure a cell-common offset and / or an offset specific to the first terminal device for the first terminal device.
[0225] In some embodiments, the network device may indicate the cell common offset to the first terminal device by broadcasting.
[0226] In some embodiments, the network device may indicate an offset specific to the first terminal device to the first terminal device via a MAC CE.
[0227] In some embodiments, even if the network device configures a first terminal device-specific offset for the first terminal device, the first terminal device-specific offset may be applicable to unicast transmission of the first terminal device but not to HARQ feedback for MBS.
[0228] In some embodiments, the first terminal device may determine the time domain resource carrying the HARQ feedback information corresponding to the first PDSCH based on the first offset (i.e., the cell-common offset) and the first parameter. For an introduction to the first parameter, please refer to the previous text and will not be repeated here for the sake of brevity.
[0229] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 10. The device embodiment of the present application is described in detail below in conjunction with Figures 11 to 13. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.
[0230] FIG11 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application. The terminal device 1100 shown in FIG11 may include a receiving module 1110 and a determining module 1120.
[0231] The receiving module 1110 may be configured to receive a first PDSCH for an MBS.
[0232] The determination module 1120 can be used to determine the time domain resources corresponding to the first PUCCH based on the first offset, and the first PUCCH is used to carry the HARQ feedback information corresponding to the first PDSCH; wherein the first offset is determined based on one or more of the following: an offset exclusive to the first terminal device; an offset exclusive to the first terminal device group to which the first terminal device is located; and a cell-common offset.
[0233] Optionally, the first offset is determined based on an offset specific to the first terminal device group.
[0234] Optionally, the first offset corresponds to a first group identifier; or the first offset corresponds to multiple group identifiers including the first group identifier; wherein the first group identifier is associated with the first terminal device group.
[0235] Optionally, when the first terminal device is not configured with the first offset, the time domain resources corresponding to the first PUCCH are determined based on the cell common offset.
[0236] Optionally, whether to configure the first offset is determined based on a first condition, where the first condition is associated with whether HARQ feedback is enabled for a first group identifier; wherein the first group identifier is associated with the first terminal device group.
[0237] Optionally, if HARQ feedback is enabled for the first group identifier, the first offset is configured; and / or if HARQ feedback is not enabled for the first group identifier, the first offset is not configured.
[0238] Optionally, the first offset is configured based on a first signaling, and the first signaling is dedicated signaling for the first terminal device; or, the first signaling is dedicated signaling for the first terminal device group.
[0239] Optionally, the first signaling is dedicated signaling for the first terminal device, including: the first signaling is RRC signaling, and the RRC signaling is carried in the PDSCH encrypted by C-RNTI or CS-RNTI; or, the first signaling is MAC CE, and the MAC CE is carried in the PDSCH encrypted by C-RNTI or CS-RNTI; or, the first signaling is PDCCH, and the PDCCH is encrypted based on C-RNTI or CS-RNTI.
[0240] Optionally, the first signaling is exclusive signaling for the first terminal device group, including: the first signaling is RRC signaling, and the RRC signaling is carried in the PDSCH encrypted by G-RNTI or G-CS-RNTI; or, the first signaling is MAC CE, and the MAC CE is carried in the PDSCH encrypted by G-RNTI or G-CS-RNTI; or, the first signaling is PDCCH, and the PDCCH is encrypted based on G-RNTI or G-CS-RNTI.
[0241] Optionally, the first signaling is used to configure one or more of the following: the value of the first offset; the absolute value of the first offset; the difference between the first offset and the cell-common offset; the increment of the first offset relative to the cell-common offset; the difference between the first offset and the offset specific to the first terminal device; and the increment of the first offset relative to the offset specific to the first terminal device.
[0242] Optionally, if the first PDSCH is the PDSCH corresponding to the PTM transmission mode, the first offset is an offset exclusive to the first terminal device group; or, if the first PDSCH is the PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device group; or, if the first PDSCH is the PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device.
[0243] Optionally, the first PDSCH is associated with a first PDCCH, the first PDCCH includes a first parameter, the first parameter is used to determine the time domain resources corresponding to the first PUCCH, and the time domain resources corresponding to the first PUCCH are determined based on the first offset and the first parameter.
[0244] Optionally, the first group identifier is G-RNTI or G-CS-RNTI.
[0245] Optionally, the receiving module 1110 may be a transceiver 1330, and the determining module 1120 may be a processor 1310. The terminal device 1100 may further include a memory 1320, as specifically shown in FIG13 .
[0246] FIG12 is a schematic diagram of the structure of a network device according to an embodiment of the present application. The network device shown in FIG12 may include a sending module 1210 and a determining module 1220.
[0247] The sending module 1210 can be used to send a first PDSCH for the MBS to the first terminal device.
[0248] The determination module 1220 can be used to determine the time domain resources corresponding to the first PUCCH based on the first offset, and the first PUCCH is used to carry the HARQ feedback information corresponding to the first PDSCH; wherein the first offset is determined based on one or more of the following: an offset exclusive to the first terminal device; an offset exclusive to the first terminal device group to which the first terminal device is located; and a cell-common offset.
[0249] Optionally, the first offset is determined based on an offset specific to the first terminal device group.
[0250] Optionally, the first offset corresponds to a first group identifier; or the first offset corresponds to multiple group identifiers including the first group identifier; wherein the first group identifier is associated with the first terminal device group.
[0251] Optionally, when the first terminal device is not configured with the first offset, the time domain resources corresponding to the first PUCCH are determined based on the cell common offset.
[0252] Optionally, whether to configure the first offset is determined based on a first condition, where the first condition is associated with whether HARQ feedback is enabled for a first group identifier; wherein the first group identifier is associated with the first terminal device group.
[0253] Optionally, if HARQ feedback is enabled for the first group identifier, the first offset is configured; and / or if HARQ feedback is not enabled for the first group identifier, the first offset is not configured.
[0254] Optionally, the first offset is configured based on a first signaling, and the first signaling is dedicated signaling for the first terminal device; or, the first signaling is dedicated signaling for the first terminal device group.
[0255] Optionally, the first signaling is dedicated signaling for the first terminal device, including: the first signaling is RRC signaling, and the RRC signaling is carried in the PDSCH encrypted by C-RNTI or CS-RNTI; or, the first signaling is MAC CE, and the MAC CE is carried in the PDSCH encrypted by C-RNTI or CS-RNTI; or, the first signaling is PDCCH, and the PDCCH is encrypted based on C-RNTI or CS-RNTI.
[0256] Optionally, the first signaling is exclusive signaling for the first terminal device group, including: the first signaling is RRC signaling, and the RRC signaling is carried in the PDSCH encrypted by G-RNTI or G-CS-RNTI; or, the first signaling is MAC CE, and the MAC CE is carried in the PDSCH encrypted by G-RNTI or G-CS-RNTI; or, the first signaling is PDCCH, and the PDCCH is encrypted based on G-RNTI or G-CS-RNTI.
[0257] Optionally, the first signaling is used to configure one or more of the following: the value of the first offset; the absolute value of the first offset; the difference between the first offset and the cell-common offset; the increment of the first offset relative to the cell-common offset; the difference between the first offset and the offset specific to the first terminal device; and the increment of the first offset relative to the offset specific to the first terminal device.
[0258] Optionally, if the first PDSCH is the PDSCH corresponding to the PTM transmission mode, the first offset is an offset exclusive to the first terminal device group; or, if the first PDSCH is the PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device group; or, if the first PDSCH is the PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device.
[0259] Optionally, the first PDSCH is associated with a first PDCCH, the first PDCCH includes a first parameter, the first parameter is used to determine the time domain resources corresponding to the first PUCCH, and the time domain resources corresponding to the first PUCCH are determined based on the first offset and the first parameter.
[0260] Optionally, the first group identifier is G-RNTI or G-CS-RNTI.
[0261] Optionally, the sending module 1210 may be a transceiver 1330, and the determining module 1220 may be a processor 1310. The network device 1200 may further include a memory 1320, as specifically shown in FIG13 .
[0262] Figure 13 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 13 indicate that the unit or module is optional. Apparatus 1300 may be used to implement the method described in the above method embodiment. Apparatus 1300 may be a chip, a terminal device, or a network device.
[0263] The device 1300 may include one or more processors 1310. The processor 1310 may support the device 1300 to implement the method described in the above method embodiment. The processor 1310 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another 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, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0264] The apparatus 1300 may further include one or more memories 1320. The memories 1320 store programs that can be executed by the processor 1310, causing the processor 1310 to perform the methods described in the above method embodiments. The memories 1320 may be independent of the processor 1310 or integrated into the processor 1310.
[0265] The apparatus 1300 may further include a transceiver 1330. The processor 1310 may communicate with other devices or chips via the transceiver 1330. For example, the processor 1310 may transmit and receive data with other devices or chips via the transceiver 1330.
[0266] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.
[0267] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal device or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.
[0268] The present application also provides a computer program that can be applied to a terminal device or network device provided in the present application, and enables a computer to execute the method performed by the terminal device or network device in each embodiment of the present application.
[0269] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.
[0270] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.
[0271] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.
[0272] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.
[0273] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."
[0274] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.
[0275] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.
[0276] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0277] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0278] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0279] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0280] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
[0281] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).
[0282] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.
Claims
1. A wireless communication method, characterized in that: include: The first terminal device receives a first PDSCH for the MBS; The first terminal device determines, according to the first offset, a time domain resource corresponding to a first PUCCH, where the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; The first offset is determined based on one or more of the following: An offset specific to the first terminal device; An offset specific to the first terminal device group to which the first terminal device belongs; and The common offset of the cell.
2. The method according to claim 1, characterized in that The first offset is determined based on an offset specific to the first terminal device group.
3. The method according to claim 2, characterized in that: The first offset corresponds to the first group identifier; or The first offset corresponds to a plurality of group identifiers including the first group identifier; The first group identifier is associated with the first terminal device group.
4. The method according to claim 2 or 3, characterized in that: When the first terminal device is not configured with the first offset, the time domain resources corresponding to the first PUCCH are determined based on the cell common offset.
5. The method according to any one of claims 2 to 4, characterized in that Whether to configure the first offset is determined based on a first condition, where the first condition is associated with whether HARQ feedback is enabled for a first group identifier; wherein the first group identifier is associated with the first terminal device group.
6. The method according to claim 5, characterized in that: If HARQ feedback is enabled for the first group identifier, configuring the first offset; and / or If HARQ feedback is not enabled for the first group identifier, the first offset is not configured.
7. The method according to any one of claims 2 to 6, characterized in that The first offset is configured based on a first signaling, where the first signaling is dedicated signaling for the first terminal device; or, the first signaling is dedicated signaling for the first terminal device group.
8. The method according to claim 7, characterized in that The first signaling is a dedicated signaling of the first terminal device, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a C-RNTI or a CS-RNTI.
9. The method according to claim 7, characterized in that: The first signaling is a dedicated signaling of the first terminal device group, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a G-RNTI or a G-CS-RNTI.
10. The method according to any one of claims 7 to 9, characterized in that The first signaling is used to configure one or more of the following: The value of the first offset; the absolute value of the first offset; a difference between the first offset and the cell common offset; An increment of the first offset relative to the cell common offset; a difference between the first offset and an offset specific to the first terminal device; and The first offset is an increment of an offset specific to the first terminal device.
11. The method according to claim 1, characterized in that: If the first PDSCH is a PDSCH corresponding to the PTM transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device.
12. The method according to any one of claims 1 to 11, characterized in that The first PDSCH is associated with a first PDCCH, the first PDCCH includes a first parameter, the first parameter is used to determine a time domain resource corresponding to the first PUCCH, and the time domain resource corresponding to the first PUCCH is determined based on the first offset and the first parameter.
13. The method according to claim 3, 5 or 6, characterized in that The first group identifier is a G-RNTI or a G-CS-RNTI.
14. A wireless communication method, characterized in that: include: The network device sends a first PDSCH for the MBS to the first terminal device; The network device determines, according to the first offset, a time domain resource corresponding to a first PUCCH, where the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; The first offset is determined based on one or more of the following: An offset specific to the first terminal device; An offset specific to the first terminal device group to which the first terminal device belongs; and The common offset of the cell.
15. The method according to claim 14, characterized in that The first offset is determined based on an offset specific to the first terminal device group.
16. The method according to claim 15, characterized in that: The first offset corresponds to the first group identifier; or The first offset corresponds to a plurality of group identifiers including the first group identifier; The first group identifier is associated with the first terminal device group.
17. The method according to claim 15 or 16, characterized in that When the first terminal device is not configured with the first offset, the time domain resources corresponding to the first PUCCH are determined based on the cell common offset.
18. The method according to any one of claims 15 to 17, characterized in that Whether to configure the first offset is determined based on a first condition, where the first condition is associated with whether HARQ feedback is enabled for a first group identifier; wherein the first group identifier is associated with the first terminal device group.
19. The method according to claim 18, characterized in that: If HARQ feedback is enabled for the first group identifier, configuring the first offset; and / or If HARQ feedback is not enabled for the first group identifier, the first offset is not configured.
20. The method according to any one of claims 15 to 19, characterized in that The first offset is configured based on a first signaling, where the first signaling is dedicated signaling for the first terminal device; or, the first signaling is dedicated signaling for the first terminal device group.
21. The method according to claim 20, characterized in that The first signaling is a dedicated signaling of the first terminal device, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a C-RNTI or a CS-RNTI.
22. The method according to claim 20, characterized in that The first signaling is a dedicated signaling of the first terminal device group, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a G-RNTI or a G-CS-RNTI.
23. The method according to any one of claims 20 to 22, characterized in that The first signaling is used to configure one or more of the following: The value of the first offset; the absolute value of the first offset; a difference between the first offset and the cell common offset; An increment of the first offset relative to the cell common offset; a difference between the first offset and an offset specific to the first terminal device; and The first offset is an increment of an offset specific to the first terminal device.
24. The method according to claim 14, characterized in that: If the first PDSCH is a PDSCH corresponding to the PTM transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is the first terminal device group A dedicated offset; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device.
25. The method according to any one of claims 14 to 24, characterized in that The first PDSCH is associated with a first PDCCH, the first PDCCH includes a first parameter, the first parameter is used to determine a time domain resource corresponding to the first PUCCH, and the time domain resource corresponding to the first PUCCH is determined based on the first offset and the first parameter.
26. The method according to claim 16, 18 or 19, characterized in that The first group identifier is a G-RNTI or a G-CS-RNTI.
27. A terminal device, characterized in that: The terminal device is a first terminal device, and the terminal device includes: A receiving module, configured to receive a first PDSCH for the MBS; A determination module, configured to determine, according to a first offset, a time domain resource corresponding to a first PUCCH, where the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; The first offset is determined based on one or more of the following: An offset specific to the first terminal device; An offset specific to the first terminal device group to which the first terminal device belongs; and The common offset of the cell.
28. The terminal device according to claim 27, characterized in that: The first offset is determined based on an offset specific to the first terminal device group.
29. The terminal device according to claim 28, characterized in that: The first offset corresponds to the first group identifier; or The first offset corresponds to a plurality of group identifiers including the first group identifier; The first group identifier is associated with the first terminal device group.
30. The terminal device according to claim 28 or 29, characterized in that: When the first terminal device is not configured with the first offset, the time domain resources corresponding to the first PUCCH are determined based on the cell common offset.
31. The terminal device according to any one of claims 28 to 30, characterized in that: Whether to configure the first offset is determined based on a first condition, where the first condition is associated with whether HARQ feedback is enabled for a first group identifier; wherein the first group identifier is associated with the first terminal device group.
32. The terminal device according to claim 31, characterized in that: If HARQ feedback is enabled for the first group identifier, configuring the first offset; and / or If HARQ feedback is not enabled for the first group identifier, the first offset is not configured.
33. The terminal device according to any one of claims 28 to 32, characterized in that: The first offset is configured based on a first signaling, where the first signaling is dedicated signaling for the first terminal device; or, the first signaling is dedicated signaling for the first terminal device group.
34. The terminal device according to claim 33, characterized in that: The first signaling is a dedicated signaling of the first terminal device, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a C-RNTI or a CS-RNTI.
35. The terminal device according to claim 33, characterized in that: The first signaling is a dedicated signaling of the first terminal device group, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a G-RNTI or a G-CS-RNTI.
36. The terminal device according to any one of claims 33 to 35, characterized in that: The first signaling is used to configure one or more of the following: The value of the first offset; the absolute value of the first offset; a difference between the first offset and the cell common offset; An increment of the first offset relative to the cell common offset; a difference between the first offset and an offset specific to the first terminal device; and The first offset is an increment of an offset specific to the first terminal device.
37. The terminal device according to claim 27, characterized in that: If the first PDSCH is a PDSCH corresponding to the PTM transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device.
38. The terminal device according to any one of claims 27 to 37, characterized in that: The first PDSCH is associated with a first PDCCH, the first PDCCH includes a first parameter, the first parameter is used to determine a time domain resource corresponding to the first PUCCH, and the time domain resource corresponding to the first PUCCH is determined based on the first offset and the first parameter.
39. The terminal device according to claim 29, 31 or 32, characterized in that: The first group identifier is a G-RNTI or a G-CS-RNTI.
40. A network device, characterized in that: include: A sending module, used for sending a first PDSCH for the MBS to a first terminal device; A determination module, configured to determine, according to a first offset, a time domain resource corresponding to a first PUCCH, where the first PUCCH is used to carry HARQ feedback information corresponding to the first PDSCH; The first offset is determined based on one or more of the following: An offset specific to the first terminal device; An offset specific to the first terminal device group to which the first terminal device belongs; and The common offset of the cell.
41. The network device according to claim 40, characterized in that The first offset is determined based on an offset specific to the first terminal device group.
42. The network device according to claim 41, characterized in that: The first offset corresponds to the first group identifier; or The first offset corresponds to a plurality of group identifiers including the first group identifier; The first group identifier is associated with the first terminal device group.
43. The network device according to claim 41 or 42, characterized in that: When the first terminal device is not configured with the first offset, the time domain resources corresponding to the first PUCCH are determined based on the cell common offset.
44. The network device according to any one of claims 41 to 43, characterized in that: Whether to configure the first offset is determined based on a first condition, where the first condition is associated with whether HARQ feedback is enabled for a first group identifier; wherein the first group identifier is associated with the first terminal device group.
45. The network device according to claim 44, characterized in that: If HARQ feedback is enabled for the first group identifier, configuring the first offset; and / or If HARQ feedback is not enabled for the first group identifier, the first offset is not configured.
46. The network device according to any one of claims 41 to 45, characterized in that: The first offset is configured based on a first signaling, where the first signaling is dedicated signaling for the first terminal device; or, the first signaling is dedicated signaling for the first terminal device group.
47. The network device according to claim 46, characterized in that The first signaling is a dedicated signaling of the first terminal device, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a C-RNTI or a CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a C-RNTI or a CS-RNTI.
48. The network device according to claim 46, characterized in that The first signaling is a dedicated signaling of the first terminal device group, including: The first signaling is RRC signaling, and the RRC signaling is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a MAC CE, and the MAC CE is carried in a PDSCH scrambled by a G-RNTI or a G-CS-RNTI; or, The first signaling is a PDCCH, and the PDCCH is scrambled based on a G-RNTI or a G-CS-RNTI.
49. The network device according to any one of claims 46 to 48, characterized in that: The first signaling is used to configure one or more of the following: The value of the first offset; the absolute value of the first offset; a difference between the first offset and the cell common offset; An increment of the first offset relative to the cell common offset; a difference between the first offset and an offset specific to the first terminal device; and The first offset is an increment of an offset specific to the first terminal device.
50. The network device according to claim 40, characterized in that: If the first PDSCH is a PDSCH corresponding to the PTM transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset specific to the first terminal device group; or, If the first PDSCH is a PDSCH corresponding to the PTP transmission mode, the first offset is an offset exclusive to the first terminal device.
51. The network device according to any one of claims 40 to 50, characterized in that: The first PDSCH is associated with a first PDCCH, the first PDCCH includes a first parameter, the first parameter is used to determine a time domain resource corresponding to the first PUCCH, and the time domain resource corresponding to the first PUCCH is determined based on the first offset and the first parameter.
52. The network device according to claim 42, 44 or 45, characterized in that: The first group identifier is a G-RNTI or a G-CS-RNTI.
53. A terminal device, characterized in that: The device comprises a memory, a processor and a transceiver, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the terminal device executes the method as claimed in any one of claims 1 to 13.
54. A network device, characterized in that: The device comprises a memory, a processor and a transceiver, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the network device executes the method according to any one of claims 14 to 26.
55. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 26.
56. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 26.
57. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 26.
58. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 26.
59. A computer program, characterized in that The computer program enables a computer to execute the method according to any one of claims 1 to 26.
Citation Information
Patent Citations
Method and apparatus for transmitting a high priority uplink transmission
CN113287359A
System and method for supporting multicast broadcast service (MBS) service in non-terrestrial network (NTN)
CN116171544A
Method and device for receiving MBS data
US20220417906A1
Method and apparatus for supporting more users in a multicast group
WO2022083290A1
Method and device for transmitting and receiving pucch in wireless communication system
WO2023014151A1