Method and apparatus for indicating semi-persistent scheduling (SPS) transmission for multicast scheduling (MBS)

Abstract

Embodiments of the present application disclose a method and device for indicating semi-persistent scheduling (SPS) transmission of multicast scheduling (MBS), which can be applied in long term evolution (LTE) system, 5th generation (5G) mobile communication system, 5G new radio (NR) system, etc. The method comprises: receiving, by a terminal device, SPS transmission indication signaling sent by a network side device; and obtaining, by the terminal device, a terminal device sub-group to which SPS transmission belongs and an SPS transmission state corresponding to the terminal device sub-group to which the SPS transmission belongs based on the SPS transmission indication signaling. According to the embodiments of the present application, the SPS transmission state corresponding to the sub-group to which the terminal device transmission belongs can be determined according to the SPS transmission instruction sent by the network side device, so that the differentiated SPS transmission requirement of the terminal device can be met, thereby improving the efficiency of SPS transmission in MBS service and saving resources.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a semi-persistent scheduling (SPS) transmission indication method and apparatus for multicast scheduling (MBS). Background Technology

[0002] In wireless communication, in order to perform multicast-broadcast service (MBS), the network-side equipment needs to configure semi-persistent scheduling (SPS) for the terminal devices. After the SPS configuration is activated, the terminal devices in the same subgroup use the SPS configuration to perform SPS transmission.

[0003] However, different terminal devices may have different specific service requirements and different channel conditions. Using the same SPS configuration for SPS transmission on terminal devices in the same subgroup will limit the flexibility of multicast broadcast services. Furthermore, regrouping terminal devices will introduce significant transmission latency. If only one SPS configuration is activated on the network side, the network cannot flexibly select the terminal device group to which the activated SPS is directed based on changes in service requirements. If multiple SPS configurations are activated on the network side, the differences in transmission requirements between terminal devices will exacerbate the mismatch between activation signaling and the audience. Summary of the Invention

[0004] This application provides a semi-persistent scheduling (SPS) transmission indication method and apparatus for multicast scheduling (MBS), applicable to evolved NodeBs (eNBs), transmission reception points (TRPs), next-generation NodeBs (gNBs) in NR systems, base stations in other future mobile communication systems, or access nodes in wireless fidelity (WiFi) systems. By determining the SPS transmission status of the subgroup to which the terminal device belongs through SPS transmission instructions sent by network-side equipment, the application avoids failing to meet the differentiated SPS transmission requirements of terminal devices, thereby improving the efficiency of SPS transmission in MBS services and saving resources.

[0005] In a first aspect, embodiments of this application provide a semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS), the method comprising:

[0006] Receive SPS transmission indication signaling sent by network-side equipment;

[0007] Based on the SPS transmission indication signaling, the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs are obtained.

[0008] By determining the SPS transmission status of the subgroup to which the terminal device belongs through the SPS transmission command sent by the network-side device, the differentiated SPS transmission requirements of the terminal device can be avoided, thereby improving the efficiency of SPS transmission in MBS services and saving resources.

[0009] Optionally, the SPS transmission indication signaling is an activation signaling, which includes at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0010] Optional, also includes:

[0011] When the terminal device belongs to the subgroup to which the SPS transmission belongs, the SPS Physical Downlink Shared Channel (PDSCH) is received according to the SPS transmission status corresponding to the subgroup to which the SPS transmission belongs.

[0012] Optional, also includes:

[0013] The network-side device receives an SPS configuration activation state list configured by Radio Resource Control (RRC) signaling, wherein the length of the SPS configuration activation state list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H, and the SPS transmission state of the terminal device is configured according to the SPS transmission indication signaling and the SPS configuration activation state list.

[0014] Optionally, if the network-side device activates multiple SPS transmissions simultaneously, and the Hybrid Automatic Repeat Request Process Numbers (HPNs) calculated by two or more PDSCHs corresponding to the multiple SPS transmissions are the same, then the HPNs corresponding to the two or more PDSCHs are determined according to the IDs of the terminal device subgroups corresponding to the two or more PDSCHs.

[0015] Optionally, the SPS transmission indication signaling is deactivation signaling, and the step of obtaining the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs based on the SPS transmission indication signaling includes:

[0016] Receive the SPS configuration deactivation status list configured by the network-side device via RRC signaling;

[0017] The terminal device subgroup corresponding to the indication information in the deactivation signaling is obtained according to the deactivation status list, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

[0018] Optional, also includes:

[0019] The deactivation terminal device subgroup is determined based on the deactivation signaling.

[0020] Optional, also includes:

[0021] The specific information field in the deactivation signaling indicates the terminal device subgroup corresponding to the deactivation entry.

[0022] Optional, also includes:

[0023] The specific information field in the deactivation signaling indicates the terminal device subgroup that is immune to the deactivation entry.

[0024] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is: the SPS transmission corresponding to the terminal device subgroup corresponding to the deactivation indication information is still in an active state.

[0025] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0026] Secondly, embodiments of this application provide another method for semi-persistent scheduling (SPS) transmission indication applied to multicast scheduling (MBS), the method comprising:

[0027] Send SPS transmission indication signaling to the terminal device, wherein the SPS transmission indication signaling is used to indicate the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs.

[0028] By determining the SPS transmission status of the subgroup to which the terminal device belongs through the SPS transmission command sent by the network-side device, the differentiated SPS transmission requirements of the terminal device can be avoided, thereby improving the efficiency of SPS transmission in MBS services and saving resources.

[0029] Optionally, the SPS transmission indication signaling is an activation signaling, and the indication information of the activation signaling includes: at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0030] Optional, also includes:

[0031] The SPS configuration activation status list is sent to the terminal device via RRC signaling, wherein the length of the SPS configuration activation status list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H.

[0032] Optionally, if the network-side device activates multiple SPS transmissions simultaneously, and the Hybrid Automatic Repeat Request Process Numbers (HPNs) calculated by two or more PDSCHs corresponding to the multiple SPS transmissions are the same, then the HPNs corresponding to the two or more PDSCHs are determined according to the subgroup IDs corresponding to the two or more PDSCHs.

[0033] Optional, also includes:

[0034] The SPS configuration deactivation status list is sent to the terminal device via RRC signaling.

[0035] Optionally, the indication information is used to deactivate SPS transmissions belonging to a specific subgroup of terminal devices.

[0036] Optionally, the indication information is: a specific information field in the deactivation signaling, wherein the specific information field is used to indicate the terminal device subgroup corresponding to the deactivation entry or the terminal device subgroup that is immune to the deactivation entry.

[0037] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0038] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is one whose SPS transmission is still active for the terminal device subgroup corresponding to the deactivation indication information.

[0039] Thirdly, embodiments of this application provide a communication device that implements some or all of the functions of the terminal device described in the first aspect above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0040] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module supports communication between the communication device and other devices. The communication device may also include a storage module, coupled to the transceiver module and the processing module, which stores necessary computer programs and data for the communication device.

[0041] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0042] In one implementation, the communication device includes:

[0043] The receiving module is used to receive SPS transmission indication signaling sent by network-side devices;

[0044] The acquisition module is used to acquire the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs, based on the SPS transmission indication signaling.

[0045] Optionally, the SPS transmission indication signaling is an activation signaling, which includes at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0046] Optional, also includes:

[0047] The first receiving submodule, when belonging to the terminal equipment subgroup to which the SPS transmission belongs, is used to receive the SPS Physical Downlink Shared Channel (PDSCH) according to the SPS transmission status corresponding to the terminal equipment subgroup to which the SPS transmission belongs.

[0048] Optional, also includes:

[0049] The second receiving submodule is used to receive the SPS configuration activation status list configured by the network-side device through Radio Resource Control (RRC) signaling, wherein the length of the SPS configuration activation status list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H, wherein the SPS transmission status of the terminal device is configured according to the SPS transmission indication signaling and the SPS configuration activation status list.

[0050] Optional, also includes:

[0051] The first determining submodule is used to determine the HPN corresponding to the two or more PDSCHs based on the ID of the terminal device subgroup corresponding to the two or more PDSCHs if the network-side device activates multiple SPS transmissions at the same time, and the multiple SPS transmissions correspond to the same Hybrid Automatic Repeat Request Process Number (HPN) calculated by the two or more PDSCHs respectively.

[0052] Optionally, the SPS transmission indication signaling is deactivation signaling, and the acquisition module includes:

[0053] The third receiving submodule is used to receive the SPS configuration deactivation status list configured by the network-side device through RRC signaling;

[0054] The acquisition submodule is used to acquire the terminal device subgroup corresponding to the indication information in the deactivation signaling according to the deactivation status list, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

[0055] Optional, also includes:

[0056] The second determining submodule is used to determine the deactivation terminal device subgroup based on the deactivation signaling.

[0057] Optional, also includes:

[0058] The first instruction submodule is used to instruct the terminal device subgroup corresponding to the deactivation entry according to a specific information field in the deactivation signaling.

[0059] Optional, also includes:

[0060] The second instruction submodule is used to indicate the terminal device subgroup that is immune to the deactivation entry based on a specific information field in the deactivation signaling.

[0061] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is: the SPS transmission corresponding to the terminal device subgroup corresponding to the deactivation indication information is still in an active state.

[0062] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0063] Optionally, the specific information field is the information field in the deactivation DCI that is not used for deactivation verification.

[0064] Fourthly, embodiments of this application provide another communication device that implements some or all of the functions of the network device in the method example described in the second aspect above. For example, the communication device may have the functions of some or all of the embodiments in this application, or it may have the functions of any one embodiment in this application implemented individually. The functions may be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the above functions.

[0065] In one implementation, the communication device may include a transceiver module and a processing module, the processing module being configured to support the communication device in performing the corresponding functions described in the above method. The transceiver module is used to support communication between the communication device and other devices. The communication device may also include a storage module, which is coupled to the transceiver module and the processing module, and stores the necessary computer programs and data of the communication device.

[0066] As an example, the processing module can be a processor, the transceiver module can be a transceiver or a communication interface, and the storage module can be a memory.

[0067] In one implementation, the communication device includes:

[0068] The sending module is used to send SPS transmission indication signaling to the terminal device, wherein the SPS transmission indication signaling is used to indicate the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs.

[0069] Optionally, the SPS transmission indication signaling is an activation signaling, and the indication information of the activation signaling includes: at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0070] Optional, also includes:

[0071] The first sending submodule is used to send an SPS configuration activation status list to the terminal device via RRC signaling, wherein the length of the SPS configuration activation status list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H.

[0072] Optional, also includes:

[0073] The determination submodule is used to determine the HPN corresponding to the two or more PDSCHs based on the subgroup IDs corresponding to the two or more PDSCHs if the network-side device activates multiple SPS transmissions simultaneously and the Hybrid Automatic Repeat Request Process Numbers (HPNs) calculated by the two or more PDSCHs are the same.

[0074] Optional, also includes:

[0075] The second sending submodule is used to send the SPS configuration deactivation status list to the terminal device via RRC signaling.

[0076] Optionally, the indication information is used to deactivate SPS transmissions belonging to a specific subgroup of terminal devices.

[0077] Optionally, the indication information is: a specific information field in the deactivation signaling, wherein the specific information field is used to indicate the terminal device subgroup corresponding to the deactivation entry or the terminal device subgroup that is immune to the deactivation entry.

[0078] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0079] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is one whose SPS transmission is still active for the terminal device subgroup corresponding to the deactivation indication information.

[0080] Fifthly, embodiments of this application provide a communication device including a processor, which executes the method described in the first aspect when it calls a computer program in memory.

[0081] In a sixth aspect, embodiments of this application provide a communication device including a processor that, when the processor invokes a computer program in memory, executes the method described in the second aspect above.

[0082] In a seventh aspect, embodiments of this application provide a communication device, which includes a processor and a memory, wherein the memory stores a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the first aspect above.

[0083] Eighthly, embodiments of this application provide a communication device including a processor and a memory, the memory storing a computer program; the processor executes the computer program stored in the memory to cause the communication device to perform the method described in the second aspect above.

[0084] Ninthly, embodiments of this application provide a communication device, the device including a processor and an interface circuit, the interface circuit being used to receive code instructions and transmit them to the processor, the processor being used to execute the code instructions to cause the device to perform the method described in the first aspect above.

[0085] In a tenth aspect, embodiments of this application provide a communication device including a processor and an interface circuit. The interface circuit is used to receive code instructions and transmit them to the processor, which is used to execute the code instructions to cause the device to perform the method described in the second aspect above.

[0086] Eleventhly, embodiments of this application provide a semi-persistent scheduling (SPS) transmission indication system applied to multicast scheduling (MBS). The system includes the communication device described in the third aspect and the communication device described in the fourth aspect, or the system includes the communication device described in the fifth aspect and the communication device described in the sixth aspect, or the system includes the communication device described in the seventh aspect and the communication device described in the eighth aspect, or the system includes the communication device described in the ninth aspect and the communication device described in the tenth aspect.

[0087] In a twelfth aspect, embodiments of the present invention provide a computer-readable storage medium for storing instructions for use by the aforementioned terminal device, which, when executed, cause the terminal device to perform the method described in the first aspect.

[0088] In a thirteenth aspect, embodiments of the present invention provide a readable storage medium for storing instructions for use by the network device described above, which, when executed, cause the network device to perform the method described in the second aspect above.

[0089] In a fourteenth aspect, this application also provides a computer program product including a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0090] In a fifteenth aspect, this application also provides a computer program product including a computer program, which, when run on a computer, causes the computer to perform the method described in the second aspect above.

[0091] In a sixteenth aspect, this application provides a chip system including at least one processor and an interface for supporting a terminal device in implementing the functions involved in the first aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the terminal device. The chip system may be composed of chips or may include chips and other discrete devices.

[0092] In a seventeenth aspect, this application provides a chip system including at least one processor and an interface for supporting a network device in implementing the functions involved in the second aspect, such as determining or processing at least one of the data and information involved in the above methods. In one possible design, the chip system further includes a memory for storing computer programs and data necessary for the network device. The chip system may be composed of chips or may include chips and other discrete devices.

[0093] In an eighteenth aspect, this application provides a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect above.

[0094] In a nineteenth aspect, this application provides a computer program that, when run on a computer, causes the computer to perform the method described in the second aspect above. Attached Figure Description

[0095] To more clearly illustrate the technical solutions in the embodiments of this application or the background art, the accompanying drawings used in the embodiments of this application or the background art will be described below.

[0096] Figure 1 This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0097] Figure 2 This is a flowchart illustrating a semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS) according to an embodiment of this application.

[0098] Figure 3 This is a flowchart illustrating a semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS) according to an embodiment of this application.

[0099] Figure 4 This is a schematic diagram of a semi-persistent scheduling (SPS) transmission indication device applied to multicast scheduling (MBS) according to an embodiment of this application.

[0100] Figure 5 This is a schematic diagram of a semi-persistent scheduling (SPS) transmission indication device applied to multicast scheduling (MBS) according to an embodiment of this application.

[0101] Figure 6 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0102] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0103] Figure 8 This is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0104] To facilitate understanding, the terminology used in this application will be introduced first.

[0105] 1. Multicast-broadcast service (MBS)

[0106] Multicast Broadcast Service (MBS) is an important function of a wireless communication system defined by the IEEE 802.16e protocol. MBS can be divided into single-base station access and multi-base station access. Single-base station access refers to multicast broadcast services within a single base station, while multi-base station access refers to all terminals registered to multicast broadcast content at the network level being able to receive multicast broadcast services synchronously transmitted on the downlink connection by all base stations within the multicast broadcast service area.

[0107] 2. Downlink control information (DCI)

[0108] The Downlink Control Channel (DCI) is carried by the Physical Downlink Control Channel (PDCCH). The DCI can include uplink and downlink resource allocation, hybrid automatic repeat request (HARQ) information, power control, etc. The PDCCH is a physical channel used to carry downlink scheduling information.

[0109] To better understand the semi-persistent scheduling (SPS) transmission indication method for multicast scheduling (MBS) disclosed in this application, the communication system to which this application is applicable will be described first.

[0110] Please see Figure 1 , Figure 1 This application provides a schematic diagram of the architecture of a communication system according to an embodiment. The communication system may include, but is not limited to, a network device and a terminal device. Figure 1 The number and form of devices shown are for illustrative purposes only and do not constitute a limitation on the embodiments of this application. In actual applications, it may include two or more network devices and two or more terminal devices. Figure 1 The communication system shown is exemplified by a network device 101 and a terminal device 102.

[0111] 3. Scrambling

[0112] Scrambling is a digital signal processing method that uses a scrambling code to perform an XOR operation with the original signal to obtain a new signal. Typically, uplink physical channel scrambling distinguishes different terminal devices, while downlink scrambling distinguishes cells and channels. Scrambling codes can be used to scramble and descramble the original signal. For example, scrambling codes can scramble downlink control information (DCI), also known as PDCCH scrambling. Specifically, DCI scrambling refers to scrambling the cyclic redundancy check (CRC) field of the DCI. Correspondingly, the terminal device descrambles the received DCI, specifically by using an appropriate type of scrambling code to descramble the CRC field of the DCI to determine its format or type.

[0113] Scrambling codes may include, but are not limited to: cell radio network temporary identifier (C-RNTI), temporary cell radio network temporary identifier (TC-RNTI), groupscheduling radio network temporary identifier (GS-RNTI), and random access radio network temporary identifier (RA-RNTI).

[0114] It should be noted that the technical solutions of this application embodiment can be applied to various communication systems. For example, Long Term Evolution (LTE) systems, 5th Generation (5G) mobile communication systems, 5G New Radio (NR) systems, or other future new mobile communication systems. It should also be noted that the side link in this application embodiment can also be called a side link or a direct link.

[0115] The network device 101 in this embodiment is a network-side entity used for transmitting or receiving signals. For example, the network device 101 can be an evolved NodeB (eNB), a transmission reception point (TRP), a next-generation NodeB (gNB) in an NR system, a base station in other future mobile communication systems, or an access node in a wireless fidelity (WiFi) system. This application does not limit the specific technology or device form used in the network device. The network device provided in this embodiment can be composed of a central unit (CU) and a distributed unit (DU). The CU can also be called a control unit. Using a CU-DU structure allows the protocol layer of a network device, such as a base station, to be separated. Some protocol layer functions are centrally controlled by the CU, while the remaining or all protocol layer functions are distributed in the DU, which is centrally controlled by the CU.

[0116] In this application embodiment, the terminal device 102 is a user-side entity used to receive or transmit signals, such as a mobile phone. The terminal device can also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device can be a car with communication capabilities, a smart car, a mobile phone, a wearable device, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, etc. The embodiments of this application do not limit the specific technology or device form used in the terminal device.

[0117] In related technologies, for MBS SPS configuration, the network side can configure multiple SPS configurations for terminals. However, different terminals may have different specific service requirements and channel conditions. Under the current mechanism, once an SPS is activated, terminals within the group must use the same SPS configuration to receive data, thus limiting the flexibility of SPS scheduling. Regrouping terminal devices via Radio Resource Control (RRC) signaling would introduce significant transmission latency. If the network side activates only one SPS configuration, it cannot flexibly select the terminal groups targeted by the activated SPS based on service changes. If the network side activates multiple SPS configurations, the differences in transmission requirements between terminals will exacerbate the mismatch between activation signaling and the target audience.

[0118] In related technologies, the network side can configure one or more SPS configurations for a terminal. When activating a configured SPS, the network side can only activate one SPS configuration at a time. However, for MBS, a single activation can only activate the same SPS configuration for all terminals within a subgroup, resulting in insufficient scheduling flexibility.

[0119] In related technologies, joint deactivation of SPS by terminals is supported, meaning that multiple SPS configurations can be activated through a single deactivation DCI. However, this only supports deactivation of SPS for all terminals within a subgroup and cannot meet the differentiated needs of different terminals. If devices within a subgroup have different SPS configuration requirements, this approach will not be feasible.

[0120] It is understood that the communication system described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0121] The SPS transmission indication method and apparatus for MBS provided in this application will be described in detail below with reference to the accompanying drawings.

[0122] Please see Figure 2 , Figure 2 This is a flowchart illustrating a semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS) according to an embodiment of this application. The method is applied in a terminal device. Figure 2As shown, the method may include, but is not limited to, the following steps:

[0123] Step S201: Receive SPS transmission indication signaling sent by the network-side device;

[0124] In this embodiment, the network-side device configures one or more SPS configurations for the terminal device, and simultaneously configures one or more GS-RNTIs for the terminal device. The network side can configure one or more terminal device sub-group IDs for terminal devices configured with the same GS-RNTI, which are used to indicate the terminal device sub-group to which the terminal device belongs, and the terminal device sub-group belongs to the MBS group.

[0125] In one possible embodiment, the relationship between the terminal devices and the terminal device subgroups configured by the network-side devices is shown in Table 1:

[0126] UE ID Sub-group ID #1 {#1#2#3#4} #2 {#1#2#4} #3 {#1#2#3} #4 {#1}

[0127] Table 1

[0128] Wherein, UE ID is the ID of the terminal device, and Sub-group ID is the ID of the terminal device subgroup. UE#1 belongs to terminal device subgroups Sub-group#1, Sub-group#2, Sub-group#3, and Sub-group#4; UE#2 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#4; UE#3 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#3; and UE#4 belongs to terminal device subgroup#1. UE#1, UE#2, UE#3, and UE#4 belong to the same MBS group.

[0129] Step S202: Based on the SPS transmission indication signaling, obtain the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs.

[0130] In this embodiment of the application, after receiving the SPS transmission indication signaling sent by the network-side device, the terminal device determines the terminal device subgroup to which it belongs in the SPS transmission and the corresponding SPS transmission status of the terminal device subgroup based on the SPS transmission indication signaling. The SPS transmission status can be an active transmission status or a deactivated transmission status.

[0131] By implementing the embodiments of this application, the SPS transmission status corresponding to the subgroup to which the terminal device belongs can be determined by the SPS transmission command sent by the network-side device. This can avoid the inability to meet the differentiated SPS transmission requirements of the terminal device, thereby improving the efficiency of SPS transmission in MBS services and saving resources.

[0132] Optionally, the SPS transmission indication signaling is an activation signaling, which includes at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0133] In this embodiment of the application, the SPS transmission indication signaling is an activation signaling. The terminal device determines at least one activated SPS configuration index based on the activation signaling. Based on the activated SPS configuration index, the activated SPS configuration and its corresponding terminal device subgroup can be determined.

[0134] In one possible implementation, the network-side device is configured with at least one activated SPS configuration identifier. The activated SPS configuration identifier and the corresponding terminal device subgroup are indicated by the 4-bit Hybrid Automatic Repeat Request Process Number (HPN) field in the activation signaling. The correspondence is shown in Table 2.

[0135]

[0136]

[0137] Table 2

[0138] Table 2 shows the SPS activation state list. The activation information bit is the 4-bit HPN field in the activation signaling. Based on the activation information bit, a maximum of 2^4 = 16 different SPS activation states can be configured. The SPS configuration index is the SPS configuration identifier, and the Sub-group set is the terminal device subgroup corresponding to the SPS configuration identifier. As shown in Table 2, when the activation information bit is 0000, the SPS configuration with SPS configuration identifier #0 is activated and enters the activation state. The terminal devices contained in its corresponding Sub-group #1, Sub-group #2, Sub-group #3, and Sub-group #4 need to perform SPS transmission services according to the SPS configuration corresponding to SPS configuration index #0, that is, to detect and receive data in the PDSCH corresponding to the SPS based on SPS configuration #0.

[0139] Optionally, one activation information bit corresponds to multiple SPS configuration indices, meaning that one activation information bit can activate multiple SPS configurations to enter the active state.

[0140] Optional, also includes:

[0141] When the terminal device belongs to the subgroup to which the SPS transmission belongs, the SPS Physical Downlink Shared Channel (PDSCH) is received according to the SPS transmission status corresponding to the subgroup to which the SPS transmission belongs.

[0142] In this embodiment of the application, when the terminal device belongs to the terminal device subgroup to which the SPS transmission belongs, the terminal device can determine the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs, and receive the corresponding PDSCH of SPS according to the SPS transmission status.

[0143] As shown in Table 2, when the activation information bit is 0001, the SPS configuration with SPS configuration identifier #1 is activated and enters the active state. The terminal devices contained in Sub-group #1, Sub-group #2 and Sub-group #4 need to perform SPS transmission services according to the SPS configuration corresponding to SPS configuration index #1, that is, to detect and receive the data in the PDSCH corresponding to SPS according to SPS configuration #1.

[0144] Optional, also includes:

[0145] The network-side device receives an SPS configuration activation state list configured by Radio Resource Control (RRC) signaling, wherein the length of the SPS configuration activation state list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H, and the SPS transmission state of the terminal device is configured according to the SPS transmission indication signaling and the SPS configuration activation state list.

[0146] In this embodiment of the application, the network-side device configures the SPS configuration activation state list for the terminal device through Radio Resource Control (RRC) signaling. The SPS configuration activation state list is shown in Table 2. When the activation information bit is 0010, the SPS configuration with SPS configuration identifier #2 is activated and enters the activation state. The terminal devices contained in Sub-group #1, Sub-group #2 and Sub-group #3 corresponding to it need to perform SPS transmission services according to the SPS configuration corresponding to SPS configurationindex #2, that is, to detect and receive the data in the PDSCH corresponding to the SPS according to SPS configuration #2.

[0147] Optionally, if the network-side device activates multiple SPS transmissions simultaneously, and the Hybrid Automatic Repeat Request Process Numbers (HPNs) calculated by two or more PDSCHs corresponding to the multiple SPS transmissions are the same, then the HPNs corresponding to the two or more PDSCHs are determined according to the IDs of the terminal device subgroups corresponding to the two or more PDSCHs.

[0148] In this embodiment of the application, the network-side device activates multiple SPS transmissions simultaneously, and the Hybrid Automatic Repeat Request Process Number (HPN) calculated by two or more PDSCHs corresponding to the multiple SPS transmissions is the same, that is, the HPN number conflicts. In order to avoid the PDSCH merging error caused by HPN number conflicts, the HPN corresponding to the two or more PDSCHs is determined according to the ID of the terminal device subgroups corresponding to the two or more PDSCHs, so as to distinguish the HPN values.

[0149] Please see Figure 3 , Figure 3 This is a flowchart illustrating a semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS) according to an embodiment of this application. The method is applied in a terminal device. Figure 3 As shown, the method may include, but is not limited to, the following steps:

[0150] Step S301: Receive the SPS configuration deactivation status list configured by the network-side device through RRC signaling;

[0151] In this embodiment, the network-side device configures an SPS configuration deactivation list for the terminal device to indicate the SPS configuration in a deactivated state and the terminal device corresponding to the deactivated SPS configuration. Simultaneously, the network-side device configures one or more SPS configurations for the terminal device, and also configures one or more GS-RNTIs for the terminal device. The network side can configure one or more terminal device sub-group IDs for terminal devices configured with the same GS-RNTI, indicating the terminal device sub-group to which the terminal device belongs, and the terminal device sub-group belongs to the MBS group.

[0152] Step S302: Obtain the terminal device subgroup corresponding to the indication information in the deactivation signaling according to the deactivation status list, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

[0153] In this embodiment of the application, the terminal device subgroup corresponding to the indication information in the deactivation signaling is obtained according to the deactivation status list. The terminal device subgroup corresponding to the indication information in the deactivation signaling is the sub-group to which the SPS transmission belongs.

[0154] By implementing the embodiments of this application, the SPS transmission status corresponding to the subgroup to which the terminal device belongs can be determined by the SPS transmission command sent by the network-side device. This can avoid the inability to meet the differentiated SPS transmission requirements of the terminal device, thereby improving the efficiency of SPS transmission in MBS services and saving resources.

[0155] Optional, also includes:

[0156] The deactivation terminal device subgroup is determined based on the deactivation signaling.

[0157] In one possible embodiment, the relationship between the terminal devices and the terminal device subgroups configured by the network-side devices is shown in Table 3:

[0158] UE ID Sub-group ID #1 {#1#2#3#4} #2 {#1#2#4} #3 {#1#2#3} #4 {#1}

[0159] Table 3

[0160] Wherein, UE ID is the ID of the terminal device, and Sub-group ID is the ID of the terminal device subgroup. UE#1 belongs to terminal device subgroups Sub-group#1, Sub-group#2, Sub-group#3, and Sub-group#4; UE#2 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#4; UE#3 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#3; and UE#4 belongs to terminal device subgroup#1. UE#1, UE#2, UE#3, and UE#4 belong to the same MBS group.

[0161] Optional, also includes:

[0162] The specific information field in the deactivation signaling indicates the terminal device subgroup corresponding to the deactivation entry.

[0163] In one possible implementation, the network-side device is configured with at least one deactivated SPS configuration identifier. The deactivated SPS configuration identifier and the corresponding terminal device subgroup are indicated by a specific information field in the deactivation signaling, namely the 4-bit Hybrid Automatic Repeat Request Process Number (HARQ ProcessN) field. The correspondence is shown in Table 4.

[0164]

[0165]

[0166] Table 4

[0167] Table 4 shows the SPS deactivation state list. The deactivation information bit is the 4-bit HPN field in the aforementioned deactivation signaling. Based on the deactivation information bit, a maximum of 2^4 = 16 different SPS deactivation states can be configured. The SPS configuration index is the SPS configuration identifier, and the Sub-group set is the terminal device subgroup corresponding to the SPS configuration identifier. As shown in Table 4, when the deactivation information bit is 0000, the SPS configurations with SPS configuration identifiers #0, #1, #2, and #3 are deactivated and enter the deactivation state. The terminal devices contained in their corresponding Sub-groups #1, #2, #3, and #4 need to deactivate the SPS transmission services corresponding to SPS configuration indices #0, #1, #2, and #3.

[0168] In another possible embodiment, the SPS configurations with deactivation information bits of 0001 and SPS configuration identifiers of #0, #1, and #2 are deactivated and enter the deactivation state. The terminal devices contained in the corresponding Sub-group #1, Sub-group #2, and Sub-group #4 need to deactivate the SPS transmission services corresponding to SPS configuration indexes #0, #1, and #2.

[0169] Optionally, a de-activation information bit corresponds to a single SPS configuration index, meaning that a de-activation information bit can deactivate a single SPS configuration, putting it into a deactivated state.

[0170] Optional, also includes:

[0171] The specific information field in the deactivation signaling indicates the terminal device subgroup that is immune to the deactivation entry.

[0172] In this embodiment, the terminal determines the terminal device subgroup corresponding to the de-activation entry indicated by the de-activation signaling according to the specific information field. The specific information field is an information field in the de-activation DCI that is not used for de-activation verification validation.

[0173] If a de-activation DCI can only be used to deactivate an SPS transmission, then the relevant information fields not used for deactivation verification are one or more information fields other than the following bit fields: HARQ process number (HPN), Redundancy version (RV), Modulation and coding scheme (MACS), and Frequency domain resource allocation (RDRA).

[0174] If the aforementioned de-activation DCI is used to deactivate multiple SPS transmissions, then the relevant information fields not used for deactivation verification are one or more other information fields excluding the following bit fields: information field, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0175] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is: the SPS transmission corresponding to the terminal device subgroup corresponding to the deactivation indication information is still in an active state.

[0176] If a de-activation DCI can only be used to deactivate an SPS transmission, then the relevant information fields not used for deactivation verification are one or more information fields other than the following bit fields: HARQ process number, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0177] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0178] If the aforementioned de-activation DCI is used to deactivate multiple SPS transmissions, then the relevant information fields not used for deactivation verification are one or more other information fields excluding the following bit fields: information field, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0179] This application provides a flowchart illustrating a semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS). The method is applied in network-side devices. The method may include, but is not limited to, the following steps:

[0180] Send SPS transmission indication signaling to the terminal device, wherein the SPS transmission indication signaling is used to indicate the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs.

[0181] In this embodiment, the network-side device configures one or more SPS configurations for the terminal device via SPS transmission indication signaling, and simultaneously configures one or more GS-RNTIs for the terminal device. The network side can configure one or more terminal device subgroups for terminal devices configured with the same GS-RNTI, to indicate the terminal device subgroup to which the terminal device belongs, and the terminal device subgroup belongs to the MBS group.

[0182] In one possible embodiment, the relationship between the terminal devices and the terminal device subgroups configured by the network-side devices is shown in Table 5:

[0183] UE ID Sub-group ID #1 {#1#2#3#4} #2 {#1#2#4} #3 {#1#2#3} #4 {#1}

[0184] Table 5

[0185] Wherein, UE ID is the ID of the terminal device, and Sub-group ID is the ID of the terminal device subgroup. UE#1 belongs to terminal device subgroups Sub-group#1, Sub-group#2, Sub-group#3, and Sub-group#4; UE#2 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#4; UE#3 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#3; and UE#4 belongs to terminal device subgroup#1. UE#1, UE#2, UE#3, and UE#4 belong to the same MBS group.

[0186] By implementing the embodiments of this application, the SPS transmission status corresponding to the subgroup to which the terminal device belongs can be determined by the SPS transmission command sent by the network-side device. This can avoid the inability to meet the differentiated SPS transmission requirements of the terminal device, thereby improving the efficiency of SPS transmission in MBS services and saving resources.

[0187] Optionally, the SPS transmission indication signaling is an activation signaling, and the indication information of the activation signaling includes: at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0188] In this embodiment of the application, the SPS transmission indication signaling is an activation signaling. The terminal device determines at least one activated SPS configuration index based on the activation signaling. Based on the activated SPS configuration index, the activated SPS configuration and its corresponding terminal device subgroup can be determined.

[0189] In one possible implementation, the network-side device is configured with at least one activated SPS configuration identifier. The activated SPS configuration identifier and the corresponding terminal device subgroup are indicated by the 4-bit Hybrid Automatic Repeat Request Process Number (HPN) field in the activation signaling. The correspondence is shown in Table 6.

[0190]

[0191]

[0192] Table 6

[0193] Table 6 shows the SPS activation state list. The activation information bit is the 4-bit HPN field in the activation signaling. Based on the activation information bit, a maximum of 2^4 = 16 different SPS activation states can be configured. The SPS configuration index is the SPS configuration identifier, and the Sub-group set is the terminal device subgroup corresponding to the SPS configuration identifier. As shown in Table 6, when the activation information bit is 0000, the SPS configuration with SPS configuration identifier #0 is activated and enters the activation state. The terminal devices contained in its corresponding Sub-group #1, Sub-group #2, Sub-group #3, and Sub-group #4 need to perform SPS transmission services according to the SPS configuration corresponding to SPS configuration index #0, that is, to detect and receive data in the PDSCH corresponding to the SPS based on SPS configuration #0.

[0194] Optionally, one activation information bit corresponds to multiple SPS configuration indices, meaning that one activation information bit can activate multiple SPS configurations to enter the active state.

[0195] Optional, also includes:

[0196] The SPS configuration activation status list is sent to the terminal device via RRC signaling, wherein the length of the SPS configuration activation status list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H.

[0197] In this embodiment of the application, the network-side device configures the SPS configuration activation state list for the terminal device through Radio Resource Control (RRC) signaling. The SPS configuration activation state list is shown in Table 2. When the activation information bit is 0010, the SPS configuration with SPS configuration identifier #2 is activated and enters the activation state. The terminal devices contained in Sub-group #1, Sub-group #2 and Sub-group #3 corresponding to it need to perform SPS transmission services according to the SPS configuration corresponding to SPS configurationindex #2, that is, to detect and receive the data in the PDSCH corresponding to the SPS according to SPS configuration #2.

[0198] Optionally, if the network-side device activates multiple SPS transmissions simultaneously, and the Hybrid Automatic Repeat Request Process Numbers (HPNs) calculated by two or more PDSCHs corresponding to the multiple SPS transmissions are the same, then the HPNs corresponding to the two or more PDSCHs are determined according to the subgroup IDs corresponding to the two or more PDSCHs.

[0199] In this embodiment of the application, the network-side device activates multiple SPS transmissions simultaneously, and the Hybrid Automatic Repeat Request Process Number (HPN) calculated by two or more PDSCHs corresponding to the multiple SPS transmissions is the same, that is, the HPN number conflicts. In order to avoid the PDSCH merging error caused by HPN number conflicts, the HPN corresponding to the two or more PDSCHs is determined according to the ID of the terminal device subgroups corresponding to the two or more PDSCHs, so as to distinguish the HPN values.

[0200] Optional, also includes:

[0201] The SPS configuration deactivation status list is sent to the terminal device via RRC signaling.

[0202] In this embodiment, the network-side device configures an SPS configuration deactivation list for the terminal device via RRC signaling to indicate the SPS configurations in a deactivated state and the corresponding terminal devices. Simultaneously, the network-side device configures one or more SPS configurations for the terminal device, and also configures one or more GS-RNTIs for the terminal device. The network side can configure one or more terminal device sub-group IDs for terminal devices configured with the same GS-RNTI, indicating the terminal device sub-group to which the terminal device belongs; the terminal device sub-group belongs to the MBS group.

[0203] In one possible embodiment, the relationship between the terminal devices and the terminal device subgroups configured by the network-side devices is shown in Table 7:

[0204] UE ID Sub-group ID #1 {#1#2#3#4} #2 {#1#2#4} #3 {#1#2#3} #4 {#1}

[0205] Table 7

[0206] Wherein, UE ID is the ID of the terminal device, and Sub-group ID is the ID of the terminal device subgroup. UE#1 belongs to terminal device subgroups Sub-group#1, Sub-group#2, Sub-group#3, and Sub-group#4; UE#2 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#4; UE#3 belongs to terminal device subgroups Sub-group#1, Sub-group#2, and Sub-group#3; and UE#4 belongs to terminal device subgroup#1. UE#1, UE#2, UE#3, and UE#4 belong to the same MBS group.

[0207] In one possible implementation, the network-side device configures at least one deactivated SPS configuration identifier. The deactivated SPS configuration identifier and the corresponding terminal device subgroup are indicated by a specific information field in the deactivation signaling, namely the 4-bit Hybrid Automatic Repeat Request Process Number (HARQ ProcessN) field. The correspondence is shown in Table 8.

[0208] de-Activation information bit SPS configuration index Sub-group set 0000 #0#1#2#3 {#1#2#3#4} 0001 #0#1#2 {#1#2#4} 0010 #0#1#3 {#1#2#3} 0011 #0#2#3 {#1} 0100 #0#1 {#1#2#3#4} 0101 #0#2 {#1#2#4} 0110 #0#3 {#1#2#3} 0111 #1#2#3 {#1} 1000 #1#2 {#1#2#3#4} 1001 #1#3 {#1#2#4} 1010 #2#3 {#1#2#3} 1011 #0 {#1#2} 1100 #0 {#1#2#3#4} 1101 #1 {#1#2#4} 1110 #2 {#1#2#3} 1111 #3 {#1}

[0209] Table 8

[0210] Table 8 shows the SPS deactivation state list. The deactivation information bit is the 4-bit HPN field in the aforementioned deactivation signaling. Based on this information bit, a maximum of 2^4 = 16 different SPS deactivation states can be configured. The SPS configuration index is the SPS configuration identifier, and the Sub-group set is the terminal device subgroup corresponding to the SPS configuration identifier. As shown in Table 8, when the deactivation information bit is 0000, the SPS configurations with SPS configuration identifiers #0, #1, #2, and #3 are deactivated and enter the deactivation state. The terminal devices contained in their corresponding Sub-groups #1, #2, #3, and #4 need to deactivate the SPS transmission services corresponding to SPS configuration indices #0, #1, #2, and #3.

[0211] Optionally, the indication information is used to deactivate SPS transmissions belonging to a specific subgroup of terminal devices.

[0212] In another possible embodiment, the SPS configurations with deactivation information bits of 0001 and SPS configuration identifiers of #0, #1, and #2 are deactivated and enter the deactivation state. The terminal devices contained in the corresponding Sub-group #1, Sub-group #2, and Sub-group #4 need to deactivate the SPS transmission services corresponding to SPS configuration indexes #0, #1, and #2.

[0213] Optionally, one de-activation information bit corresponds to a single SPS configuration index, meaning that one de-activation information bit can deactivate a single SPS configuration, putting it into a deactivated state.

[0214] Optionally, the indication information is: a specific information field in the deactivation signaling, wherein the specific information field is used to indicate the terminal device subgroup corresponding to the deactivation entry or the terminal device subgroup that is immune to the deactivation entry.

[0215] In this embodiment, the terminal determines the terminal device subgroup corresponding to the de-activation entry indicated by the de-activation signaling according to the specific information field. The specific information field is an information field in the de-activation DCI that is not used for de-activation verification validation.

[0216] If a de-activation DCI can only be used to deactivate an SPS transmission, then the relevant information fields not used for deactivation verification are one or more information fields other than the following bit fields: HARQ process number, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0217] If the aforementioned de-activation DCI is used to deactivate multiple SPS transmissions, then the relevant information fields not used for deactivation verification are one or more other information fields excluding the following bit fields: information field, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0218] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0219] If the aforementioned de-activation DCI is used to deactivate multiple SPS transmissions, then the relevant information fields not used for deactivation verification are one or more other information fields excluding the following bit fields: information field, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0220] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is one whose SPS transmission is still active for the terminal device subgroup corresponding to the deactivation indication information.

[0221] If a de-activation DCI can only be used to deactivate an SPS transmission, then the relevant information fields not used for deactivation verification are one or more information fields other than the following bit fields: HARQ process number, Redundancy version, Modulation and coding scheme, and Frequency domain resource assignment.

[0222] In the embodiments provided above, the methods provided by the embodiments of this application have been described from the perspectives of network devices and terminal devices, respectively. To implement the functions of the methods provided in the embodiments of this application, the network device and the terminal device may include hardware structures and software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. One of the above functions can be executed in the form of hardware structures, software modules, or a combination of hardware structures and software modules.

[0223] Please see Figure 6 This is a schematic diagram of the structure of a communication device 60 provided in an embodiment of this application. Figure 6 The communication device 60 shown may include a transceiver module 601 and a processing module 602. The transceiver module 601 may include a sending module and / or a receiving module. The sending module is used to implement the sending function, and the receiving module is used to implement the receiving function. The transceiver module 601 can implement both sending and / or receiving functions.

[0224] The communication device 60 may be a terminal device (such as the terminal device in the aforementioned method embodiments), a device within a terminal device, or a device compatible with a terminal device. Alternatively, the communication device 60 may be a network device, a device within a network device, or a device compatible with a network device.

[0225] Communication device 60 is a terminal device, such as Figure 4 As shown, Figure 4 This is a schematic diagram of a semi-persistent scheduling (SPS) transmission indication device applied to multicast scheduling (MBS) according to an embodiment of this application. The terminal device includes:

[0226] The receiving module 410 is used to receive SPS transmission indication signaling sent by the network-side device;

[0227] The acquisition module 420 is used to acquire the terminal equipment subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal equipment subgroup to which the SPS transmission belongs, based on the SPS transmission indication signaling.

[0228] Optionally, the SPS transmission indication signaling is an activation signaling, which includes at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0229] Optional, also includes:

[0230] The first receiving submodule, when belonging to the terminal equipment subgroup to which the SPS transmission belongs, is used to receive the SPS Physical Downlink Shared Channel (PDSCH) according to the SPS transmission status corresponding to the terminal equipment subgroup to which the SPS transmission belongs.

[0231] Optional, also includes:

[0232] The second receiving submodule is used to receive the SPS configuration activation status list configured by the network-side device through Radio Resource Control (RRC) signaling, wherein the length of the SPS configuration activation status list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H, wherein the SPS transmission status of the terminal device is configured according to the SPS transmission indication signaling and the SPS configuration activation status list.

[0233] Optional, also includes:

[0234] The first determining submodule is used to determine the HPN corresponding to the two or more PDSCHs based on the ID of the terminal device subgroup corresponding to the two or more PDSCHs if the network-side device activates multiple SPS transmissions at the same time, and the multiple SPS transmissions correspond to the same Hybrid Automatic Repeat Request Process Number (HPN) calculated by the two or more PDSCHs respectively.

[0235] Optionally, the SPS transmission indication signaling is deactivation signaling, and the acquisition module includes:

[0236] The third receiving submodule is used to receive the SPS configuration deactivation status list configured by the network-side device through RRC signaling;

[0237] The acquisition submodule is used to acquire the terminal device subgroup corresponding to the indication information in the deactivation signaling according to the deactivation status list, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

[0238] Optional, also includes:

[0239] The second determining submodule is used to determine the deactivation terminal device subgroup based on the deactivation signaling.

[0240] Optional, also includes:

[0241] The first instruction submodule is used to instruct the terminal device subgroup corresponding to the deactivation entry according to a specific information field in the deactivation signaling.

[0242] Optional, also includes:

[0243] The second instruction submodule is used to indicate the terminal device subgroup that is immune to the deactivation entry based on a specific information field in the deactivation signaling.

[0244] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is: the SPS transmission corresponding to the terminal device subgroup corresponding to the deactivation indication information is still in an active state.

[0245] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0246] Optionally, the specific information field is the information field in the deactivation DCI that is not used for deactivation verification.

[0247] Communication device 60 is a network device, such as Figure 5 As shown, Figure 5This is a schematic diagram of a semi-persistent scheduling (SPS) transmission indication device applied to multicast scheduling (MBS) according to an embodiment of this application. The network device includes:

[0248] The sending module 50 is used to send SPS transmission indication signaling to the terminal device, wherein the SPS transmission indication signaling is used to indicate the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs.

[0249] Optionally, the SPS transmission indication signaling is an activation signaling, and the indication information of the activation signaling includes: at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup.

[0250] Optional, also includes:

[0251] The first sending submodule is used to send an SPS configuration activation status list to the terminal device via RRC signaling, wherein the length of the SPS configuration activation status list is L, the length of the indication field included in the DCI is H, and ceil(log2L)≤H.

[0252] Optional, also includes:

[0253] The determination submodule is used to determine the HPN corresponding to the two or more PDSCHs based on the subgroup IDs corresponding to the two or more PDSCHs if the network-side device activates multiple SPS transmissions simultaneously and the Hybrid Automatic Repeat Request Process Numbers (HPNs) calculated by the two or more PDSCHs are the same.

[0254] Optional, also includes:

[0255] The second sending submodule is used to send the SPS configuration deactivation status list to the terminal device via RRC signaling.

[0256] Optionally, the indication information is used to deactivate SPS transmissions belonging to a specific subgroup of terminal devices.

[0257] Optionally, the indication information is: a specific information field in the deactivation signaling, wherein the specific information field is used to indicate the terminal device subgroup corresponding to the deactivation entry or the terminal device subgroup that is immune to the deactivation entry.

[0258] Optionally, the specific information field is an information field in the deactivation signaling that is not used for deactivation verification.

[0259] Optionally, the terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is one whose SPS transmission is still active for the terminal device subgroup corresponding to the deactivation indication information.

[0260] Please see Figure 7 , Figure 7 This is a schematic diagram of another communication device 70 provided in an embodiment of this application. The communication device 70 can be a network device, a terminal device (such as the terminal device in the foregoing method embodiments), a chip, chip system, or processor that supports the network device in implementing the above methods, or a chip, chip system, or processor that supports the terminal device in implementing the above methods. This device can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0261] The communication device 70 may include one or more processors 701. The processor 701 may be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control the communication device (e.g., base station, baseband chip, terminal equipment, terminal equipment chip, DU or CU, etc.), execute computer programs, and process data from the computer programs.

[0262] Optionally, the communication device 70 may further include one or more memories 702, on which a computer program 703 may be stored. The processor 701 executes the computer program 703 to cause the communication device 70 to perform the methods described in the above method embodiments. Optionally, the memory 702 may also store data. The communication device 70 and the memory 702 may be provided separately or integrated together.

[0263] Optionally, the communication device 70 may further include a transceiver 704 and an antenna 705. The transceiver 704 may be referred to as a transceiver unit, transceiver, or transceiver circuit, etc., and is used to implement the transmission and reception functions. The transceiver 704 may include a receiver and a transmitter. The receiver may be referred to as a receiver or receiving circuit, etc., and is used to implement the receiving function; the transmitter may be referred to as a transmitter or transmitting circuit, etc., and is used to implement the transmitting function.

[0264] Optionally, the communication device 70 may further include one or more interface circuits 706. The interface circuits 706 are used to receive code instructions and transmit them to the processor 701. The processor 701 executes the code instructions to cause the communication device 70 to perform the methods described in the above method embodiments.

[0265] Communication device 70 is a terminal device: processor 701 is used to execute Figure 2 Step S202; Execute Figure 3Steps S302 and S302 in the process. Transceiver 704 is used to perform... Figure 2 Step S201 in the process.

[0266] In one implementation, the processor 701 may include a transceiver for implementing receiving and transmitting functions. For example, the transceiver may be a transceiver circuit, an interface, or an interface circuit. The transceiver circuit, interface, or interface circuit for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, or interface circuit can be used for reading and writing code / data, or it can be used for transmitting or relaying signals.

[0267] In one implementation, processor 701 may store computer program 703, which runs on processor 701 and causes communication device 70 to perform the methods described in the above method embodiments. Computer program 703 may be embedded in processor 701; in this case, processor 701 may be implemented in hardware.

[0268] In one implementation, the communication device 70 may include circuitry capable of performing the functions of transmitting, receiving, or communicating as described in the aforementioned method embodiments. The processor and transceiver described in this application can be implemented on integrated circuits (ICs), analog ICs, radio frequency integrated circuits (RFICs), mixed-signal ICs, application-specific integrated circuits (ASICs), printed circuit boards (PCBs), electronic devices, etc. The processor and transceiver can also be manufactured using various IC process technologies, such as complementary metal oxide semiconductors (CMOS), n-metal-oxide-semiconductor (NMOS), positive-channel metal oxide semiconductors (PMOS), bipolar junction transistors (BJTs), bipolar CMOS (BiCMOS), silicon germanium (SiGe), gallium arsenide (GaAs), etc.

[0269] The communication device described in the above embodiments may be a network device or a terminal device (such as the terminal device in the foregoing method embodiments), but the scope of the communication device described in this application is not limited thereto, and the structure of the communication device may vary. Figure 7The communication device may be a standalone device or part of a larger device. For example, the communication device may be:

[0270] (1) Independent integrated circuit IC, or chip, or chip system or subsystem;

[0271] (2) A collection of one or more ICs, optionally including storage components for storing data and computer programs;

[0272] (3) ASIC, such as modem;

[0273] (4) Modules that can be embedded in other devices;

[0274] (5) Receivers, terminal equipment, smart terminal equipment, cellular phones, wireless equipment, handheld devices, mobile units, vehicle-mounted equipment, network equipment, cloud equipment, artificial intelligence equipment, etc.

[0275] (6) Others, etc.

[0276] For cases where the communication device can be a chip or a chip system, please refer to [link / reference]. Figure 8 The diagram shows the structure of the chip. Figure 8 The chip shown includes a processor 801 and an interface 802. There can be one or more processors 801, and multiple interfaces 802.

[0277] Optionally, the chip also includes a memory 803, which is used to store necessary computer programs and data.

[0278] Those skilled in the art will also understand that the various illustrative logical blocks and steps listed in the embodiments of this application can be implemented by electronic hardware, computer software, or a combination of both. Whether such functionality is implemented through hardware or software depends on the specific application and the overall system design requirements. Those skilled in the art can implement the described functionality using various methods for each specific application, but such implementation should not be construed as exceeding the scope of protection of the embodiments of this application.

[0279] This application also provides a semi-persistent scheduling (SPS) transmission indication system applied to multicast scheduling (MBS), the system including the aforementioned Figure 6 The embodiments include a communication device as a terminal device (such as the terminal device in the aforementioned method embodiments) and a communication device as a network device; or, the system includes the aforementioned... Figure 7 The embodiments include a communication device as a terminal device (such as the terminal device in the aforementioned method embodiments) and a communication device as a network device.

[0280] This application also provides a readable storage medium having instructions stored thereon that, when executed by a computer, implement the functions of any of the above method embodiments.

[0281] This application also provides a computer program product that, when executed by a computer, implements the functions of any of the above method embodiments.

[0282] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program can be transferred from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., high-density digital video discs (DVDs)), or semiconductor media (e.g., solid-state disks (SSDs)).

[0283] Those skilled in the art will understand that the various numerical designations such as "first," "second," etc., involved in this application are merely for the convenience of description and are not intended to limit the scope of the embodiments of this application, nor do they indicate the order of sequence.

[0284] At least one in this application can also be described as one or more, and multiple can be two, three, four or more, and this application does not impose any limitation. In the embodiments of this application, for a technical feature, the technical features in that technical feature are distinguished by "first", "second", "third", "A", "B", "C" and "D", and there is no order or size among the technical features described by "first", "second", "third", "A", "B", "C" and "D".

[0285] The correspondences shown in the tables of this application can be configured or predefined. The values ​​of the information in each table are merely examples and can be configured to other values; this application is not limited to these values. When configuring the correspondences between information and parameters, it is not necessarily required to configure all the correspondences shown in each table. For example, the correspondences shown in some rows of the tables in this application may not be configured. Furthermore, appropriate modifications and adjustments can be made based on the above tables, such as splitting, merging, etc. The names of the parameters shown in the headings of the above tables can also use other names that the communication device can understand, and the values ​​or representations of the parameters can also be other values ​​or representations that the communication device can understand. In the implementation of the above tables, other data structures can also be used, such as arrays, queues, containers, stacks, linear lists, pointers, linked lists, trees, graphs, structures, classes, heaps, hash tables, or hash tables, etc.

[0286] The term "predefined" in this application can be understood as definition, pre-defined, stored, pre-stored, pre-negotiated, pre-configured, solidified, or pre-burned.

[0287] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0288] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0289] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A semi-persistent scheduling (SPS) transmission indication method applied to multicast scheduling (MBS), characterized in that, Applied to a terminal device, the method includes: Receive SPS transmission indication signaling sent by network-side equipment; Based on the SPS transmission indication signaling, the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs are obtained. Wherein, the SPS transmission indication signaling is deactivation signaling, and the specific information field in the deactivation signaling is used to indicate the terminal device subgroup that is immune to the deactivation entry indicated by the deactivation signaling, wherein the specific information field is the information field in the deactivation signaling that is not used for deactivation verification. Wherein, the SPS transmission indication signaling is deactivation signaling, and the step of obtaining the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs based on the SPS transmission indication signaling includes: The network-side device receives an SPS configuration deactivation status list configured via RRC signaling. The SPS configuration deactivation status list includes the correspondence between indication information and the deactivated SPS configuration identifier and the terminal device subgroup. The terminal device subgroup corresponding to the indication information in the deactivation signaling is obtained according to the deactivation status list, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

2. The method according to claim 1, characterized in that, The SPS transmission indication signaling is an activation signaling, which indicates, through a Hybrid Automatic Repeat Request process number (HPN): at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup; One of the terminal devices belongs to at least one terminal device subgroup.

3. The method according to claim 2, characterized in that, Also includes: When the terminal device belongs to the subgroup to which the SPS transmission belongs, the SPS Physical Downlink Shared Channel (PDSCH) is received according to the SPS transmission status corresponding to the subgroup to which the SPS transmission belongs.

4. The method according to claim 2, characterized in that, Also includes: The network-side device receives an SPS configuration activation state list configured via Radio Resource Control (RRC) signaling, wherein the length of the SPS configuration activation state list is L, the length of the indicator field included in the DCI is H, and ceil ( )≤H, wherein the SPS transmission status of the terminal device is configured according to the SPS transmission indication signaling and the SPS configuration activation status list; The SPS configuration activation status list includes the correspondence between HPN and SPS configuration identifier, and between terminal device subgroups.

5. The method according to claim 2, characterized in that, If the network-side device activates multiple SPS transmissions simultaneously, and the HPN calculated by two or more PDSCHs corresponding to the multiple SPS transmissions is the same, then the HPN corresponding to the two or more PDSCHs is determined according to the ID of the terminal device subgroups corresponding to the two or more PDSCHs.

6. The method according to claim 1, characterized in that, Also includes: The deactivation terminal device subgroup is determined based on the deactivation signaling.

7. The method according to claim 1, characterized in that, Also includes: The specific information field in the deactivation signaling indicates the terminal device subgroup corresponding to the deactivation entry.

8. The method according to claim 1, characterized in that, The terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is: the SPS transmission corresponding to the terminal device subgroup corresponding to the deactivation indication information is still in an active state.

9. An SPS transmission indication method applied to MBS, characterized in that, Applied to network-side devices, the method includes: Send SPS transmission indication signaling to terminal devices, wherein the SPS transmission indication signaling is used to indicate the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs; Wherein, the SPS transmission indication signaling is deactivation signaling, and the specific information field in the deactivation signaling is used to indicate the terminal device subgroup that is immune to the deactivation entry indicated by the deactivation signaling, wherein the specific information field is the information field in the deactivation signaling that is not used for deactivation verification. The method further includes: The SPS configuration deactivation status list is sent to the terminal device via RRC signaling. The SPS configuration deactivation status list includes the correspondence between indication information and the deactivated SPS configuration identifier and the terminal device subgroup. The deactivation status list is used to obtain the terminal device subgroup corresponding to the indication information in the deactivation signaling, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

10. The method according to claim 9, characterized in that, The SPS transmission indication signaling is an activation signaling, which indicates, through a Hybrid Automatic Repeat Request process number (HPN): at least one activated SPS configuration identifier, wherein each SPS configuration identifier corresponds to a terminal device subgroup; One of the terminal devices belongs to at least one terminal device subgroup.

11. The method according to claim 10, characterized in that, Also includes: The SPS configuration activation status list is sent to the terminal device via RRC signaling, wherein the length of the SPS configuration activation status list is L, the length of the indicator field included in the DCI is H, and ceil ( )≤H; The SPS configuration activation status list includes the correspondence between HPN and SPS configuration identifier, and between terminal device subgroups.

12. The method according to claim 10, characterized in that, If the network-side device activates multiple SPS transmissions simultaneously, and the HPN calculated by two or more PDSCHs corresponding to the multiple SPS transmissions is the same, then the HPN corresponding to the two or more PDSCHs is determined according to the subgroup IDs corresponding to the two or more PDSCHs respectively.

13. The method according to claim 9, characterized in that, The deactivation signaling instruction is used to deactivate SPS transmissions belonging to a specific subgroup of terminal devices.

14. The method according to claim 9, characterized in that, The specific information field is used to indicate the terminal device subgroup corresponding to the deactivation entry.

15. The method according to claim 9, characterized in that, The terminal device subgroup immune to the deactivation entry indicated by the deactivation signaling is: the SPS transmission corresponding to the terminal device subgroup corresponding to the deactivation indication information is still in an active state.

16. A semi-persistent scheduling (SPS) transmission indication device applied to multicast scheduling (MBS), characterized in that, Applied to a terminal device, the device includes: The receiving module is used to receive SPS transmission indication signaling sent by network-side devices; The acquisition module is used to acquire the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs, based on the SPS transmission indication signaling. Wherein, the SPS transmission indication signaling is deactivation signaling, and the specific information field in the deactivation signaling is used to indicate the terminal device subgroup that is immune to the deactivation entry indicated by the deactivation signaling, wherein the specific information field is the information field in the deactivation signaling that is not used for deactivation verification. Wherein, the SPS transmission indication signaling is deactivation signaling, and the step of obtaining the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs based on the SPS transmission indication signaling includes: The network-side device receives an SPS configuration deactivation status list configured via RRC signaling. The SPS configuration deactivation status list includes the correspondence between indication information and the deactivated SPS configuration identifier and the terminal device subgroup. The terminal device subgroup corresponding to the indication information in the deactivation signaling is obtained according to the deactivation status list, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

17. An SPS transmission indication device applied to MBS, characterized in that, Applied to network-side devices, the device includes: The sending module is used to send SPS transmission indication signaling to the terminal device, wherein the SPS transmission indication signaling is used to indicate the terminal device subgroup to which the SPS transmission belongs and the SPS transmission status corresponding to the terminal device subgroup to which the SPS transmission belongs. Wherein, the SPS transmission indication signaling is deactivation signaling, and the specific information field in the deactivation signaling is used to indicate the terminal device subgroup that is immune to the deactivation entry indicated by the deactivation signaling, wherein the specific information field is the information field in the deactivation signaling that is not used for deactivation verification. The device is also used for: The SPS configuration deactivation status list is sent to the terminal device via RRC signaling. The SPS configuration deactivation status list includes the correspondence between indication information and the deactivated SPS configuration identifier and the terminal device subgroup. The deactivation status list is used to obtain the terminal device subgroup corresponding to the indication information in the deactivation signaling, wherein the terminal device subgroup corresponding to the indication information in the deactivation signaling is the subgroup to which the SPS transmission belongs.

18. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 1 to 8.

19. A communication device, characterized in that, The device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program stored in the memory to cause the device to perform the method as described in any one of claims 9 to 15.

20. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 1 to 8.

21. A communication device, characterized in that, include: Processor and interface circuitry; The interface circuit is used to receive code instructions and transmit them to the processor; The processor is configured to run the code instructions to perform the method as described in any one of claims 9 to 15.

22. A computer-readable storage medium for storing instructions that, when executed, cause the method as described in any one of claims 1 to 8 to be implemented.

23. A computer-readable storage medium for storing instructions that, when executed, cause the method of any one of claims 9 to 15 to be implemented.

Images