Method and apparatus for multicast communication

Abstract

Various embodiments of the present disclosure provide a method for multicast communication. The method, which can be implemented by a terminal device, comprises receiving, from a network node, a first downlink channel comprising a first downlink assignment index. The first downlink channel is associated with a first service of the terminal device. The method further comprises determining, according to an association between the first downlink channel and the first service, that the first downlink assignment index is for the first service. According to various embodiments of the present disclosure, hybrid automatic repeat request feedback can be efficiently and flexibly implemented for different services (e.g. multicast and unicast services).

Description

Technical Field

[0001] This disclosure generally relates to communication networks, and more specifically, to methods and apparatus for multicast communication. Background Technology

[0002] This section introduces various aspects that may help in a better understanding of this disclosure. Accordingly, the statements in this section are to be read in this manner and should not be construed as an admission of what is prior art or what is not prior art.

[0003] Communication service providers and network operators continuously face the challenge of delivering value and convenience to consumers, for example, by providing impressive network services and performance. With the rapid development of networking and communication technologies, wireless communication networks such as LTE / 4G or NR / 5G networks promise high service capacity and end-user data rates. To meet diverse service needs, wireless communication networks are expected to support various transmission technologies, including, but not limited to, unicast, multicast, and broadcast transmissions. For transmitters, feedback information from receivers may be desired, indicating whether the receiver has successfully received the service data transmitted by the transmitter. Given the diversity of transmission technologies and application scenarios, feedback transmission may become even more challenging. Summary of the Invention

[0004] This summary is provided to introduce the selected concepts in a simplified form, and the concepts will be described in further detail in the following Detailed Description section. This summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter.

[0005] Multicast / broadcast transmission can be extremely useful for certain applications, such as cybersecurity and public safety (NSPS), vehicle-to-everything (V2X), etc. These applications may have quality of service (QoS) requirements, for example, a packet error rate of less than 1% with a latency budget of a few milliseconds. Therefore, supporting Hybrid Automatic Repeat Request (HARQ) feedback for multicast services in wireless communication networks such as 5G / NR to improve spectral efficiency may be beneficial.

[0006] Various exemplary embodiments of this disclosure propose a solution for multicast communication that can support multicast HARQ feedback with dynamic codebooks, thereby enabling terminal devices (e.g., user equipment (UE)) to efficiently implement HARQ feedback according to different services (e.g., multicast and unicast services).

[0007] According to a first aspect of this disclosure, a method implemented by a terminal device (e.g., a UE) is provided. The method includes: receiving from a network node a first downlink channel (e.g., a physical downlink control channel (PDCCH), etc.) including a first downlink allocation index (DAI). The first downlink channel may be associated with a first service of the terminal device. According to an exemplary embodiment, the method further includes: determining that the first DAI is used for the first service based on the association between the first downlink channel and the first service.

[0008] According to an exemplary embodiment, the first downlink channel can be associated with the first service by scrambling the first downlink channel using a first radio network temporary identifier (RNTI) corresponding to the first service.

[0009] According to an exemplary embodiment, the first RNTI may be a first set of radio network temporary identifiers (G-RNTI) for receiving a first multicast group of a first multicast service.

[0010] According to an exemplary embodiment, the first service may be the first multicast service for the terminal device.

[0011] According to an exemplary embodiment, the first RNTI may be a Cell Radio Network Temporary Identifier (C-RNTI) for the terminal device.

[0012] According to an exemplary embodiment, the first service may be a unicast service for the terminal device.

[0013] According to an exemplary embodiment, the first DAI may include one or more fields for the first carrier.

[0014] According to an exemplary embodiment, the first DAI used for the first service may be separate from the second DAI used for the second service.

[0015] According to an exemplary embodiment, the method according to the first aspect of this disclosure may further include: receiving a second downlink channel including a second DAI from the network node. The second downlink channel may be associated with a second service of the terminal device.

[0016] According to an exemplary embodiment, the method according to the first aspect of this disclosure may further include: determining that the second DAI is used for the second service based on the association between the second downlink channel and the second service.

[0017] According to an exemplary embodiment, the second downlink channel can be associated with the second service by scrambling the second downlink channel using a second RNTI corresponding to the second service.

[0018] According to an exemplary embodiment, the second RNTI may be a second G-RNTI for receiving a second multicast group of a second multicast service.

[0019] According to an exemplary embodiment, the second service may be the second multicast service for the terminal device.

[0020] According to an exemplary embodiment, the second DAI may include one or more fields for the second carrier.

[0021] According to a second aspect of this disclosure, an apparatus that can be implemented as a terminal device is provided. The apparatus may include one or more processors and one or more memories storing computer program code. The one or more memories and the computer program code may be configured, together with the one or more processors, to cause the apparatus to perform at least any step of the method according to the first aspect of this disclosure.

[0022] According to a third aspect of this disclosure, a computer-readable medium is provided having computer program code thereon that, when executed on a computer, causes the computer to perform any step of the method according to a first aspect of this disclosure.

[0023] According to a fourth aspect of this disclosure, an apparatus that can be implemented as a terminal device is provided. The apparatus may include a receiving unit and a determining unit. According to some exemplary embodiments, the receiving unit is operable to perform at least the receiving step of the method according to a first aspect of this disclosure. The determining unit is operable to perform at least the determining step of the method according to the first aspect of this disclosure.

[0024] According to a fifth aspect of this disclosure, a method implemented by a network node (e.g., a base station) is provided. The method includes: determining a first Data Access Interface (DAI) for a first service of a terminal device. According to an exemplary embodiment, the method further includes: transmitting a first downlink channel including the first DAI to the terminal device. The first downlink channel may be associated with the first service.

[0025] According to an exemplary embodiment, the method according to the fifth aspect of this disclosure may further include: determining a second DAI for a second service of the terminal device.

[0026] According to an exemplary embodiment, the method according to the fifth aspect of this disclosure may further include: transmitting a second downlink channel including the second DAI to the terminal device. The second downlink channel may be associated with the second service.

[0027] According to some exemplary embodiments, a first downlink channel including a first DAI according to a fifth aspect of this disclosure may correspond to a first downlink channel including a first DAI according to a first aspect of this disclosure, and therefore may have the same or similar content and / or feature elements. Similarly, a second downlink channel including a second DAI according to a fifth aspect of this disclosure may correspond to a second downlink channel including a second DAI according to a first aspect of this disclosure, and therefore may have the same or similar content and / or feature elements.

[0028] According to a sixth aspect of this disclosure, an apparatus that can be implemented as a network node is provided. The apparatus includes one or more processors and one or more memories storing computer program code. The one or more memories and the computer program code can be configured, together with the one or more processors, to cause the apparatus to perform at least any step of the method according to a fifth aspect of this disclosure.

[0029] According to a seventh aspect of this disclosure, a computer-readable medium is provided having computer program code thereon that, when executed on a computer, causes the computer to perform any step of the method according to a fifth aspect of this disclosure.

[0030] According to an eighth aspect of this disclosure, an apparatus that can be implemented as a network node is provided. The apparatus may include a determining unit and a transmitting unit. According to some exemplary embodiments, the determining unit is operable to perform at least the determining step of the method according to a fifth aspect of this disclosure. The transmitting unit is operable to perform at least the transmitting step of the method according to a fifth aspect of this disclosure.

[0031] According to a ninth aspect of this disclosure, a method is provided for implementation in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include: providing user data at the host computer. Optionally, the method may include: initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including the base station, wherein the base station may implement any step of the method according to a fifth aspect of this disclosure.

[0032] According to a tenth aspect of this disclosure, a communication system including a host computer is provided. The host computer may include: processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The cellular network may include a base station having a radio interface and processing circuitry. The processing circuitry of the base station may be configured to implement any step of the method according to a fifth aspect of this disclosure.

[0033] According to the eleventh aspect of this disclosure, a method is provided implemented in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include: providing user data at the host computer. Optionally, the method may include: initiating, at the host computer, a transmission carrying the user data to the UE via a cellular network including the base station. The UE may implement any step of the method according to the first aspect of this disclosure.

[0034] According to a twelfth aspect of this disclosure, a communication system including a host computer is provided. The host computer may include: processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to implement any step of the method according to a first aspect of this disclosure.

[0035] According to a thirteenth aspect of this disclosure, a method is provided for implementation in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include, at the host computer, receiving user data transmitted from the UE to the base station, wherein the UE may implement any step of the method according to a first aspect of this disclosure.

[0036] According to a fourteenth aspect of this disclosure, a communication system including a host computer is provided. The host computer may include a communication interface configured to receive user data originating from transmissions from a UE to a base station. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to implement any step of the method according to a first aspect of this disclosure.

[0037] According to a fifteenth aspect of this disclosure, a method is provided implemented in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include, at the host computer, receiving from the base station user data transmitted from the UE. The base station may implement any step of the method according to a fifth aspect of this disclosure.

[0038] According to a sixteenth aspect of this disclosure, a communication system is provided, which may include a host computer. The host computer may include a communication interface configured to receive user data originating from transmissions from a UE to a base station. The base station may include a radio interface and processing circuitry. The processing circuitry of the base station may be configured to implement any step of the method according to a fifth aspect of this disclosure. Attached Figure Description

[0039] The present disclosure itself, preferred modes of use, and further objects can be best understood by referring to the following detailed description of embodiments when read in conjunction with the accompanying drawings, wherein:

[0040] Figure 1 This is a diagram illustrating an exemplary DAI setup in the PDCCH according to an embodiment of the present disclosure;

[0041] Figure 2A-2D This is a diagram illustrating an exemplary DAI setup based on RNTI according to some embodiments of the present disclosure;

[0042] Figure 3 This is a flowchart illustrating a method according to an embodiment of the present disclosure;

[0043] Figure 4 This is a flowchart illustrating another method according to an embodiment of the present disclosure;

[0044] Figure 5 This is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

[0045] Figures 6A-6B This is a block diagram illustrating an apparatus according to some embodiments of the present disclosure;

[0046] Figure 7 This is a block diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments of the present disclosure;

[0047] Figure 8 This is a block diagram illustrating a host computer communicating with a UE via a base station over a partially wireless connection according to some embodiments of the present disclosure;

[0048] Figure 9 This is a flowchart illustrating a method implemented in a communication system according to embodiments of the present disclosure;

[0049] Figure 10 This is a flowchart illustrating a method implemented in a communication system according to embodiments of the present disclosure;

[0050] Figure 11 This is a flowchart illustrating a method implemented in a communication system according to embodiments of the present disclosure; and

[0051] Figure 12 This is a flowchart illustrating a method implemented in a communication system according to an embodiment of the present disclosure. Detailed Implementation

[0052] Embodiments of this disclosure have been described in detail with reference to the accompanying drawings. It should be understood that these embodiments are discussed merely to enable those skilled in the art to better understand and implement this disclosure, and not to imply any limitation on the scope of this disclosure. References to features, advantages, or similar language throughout the specification do not imply that all features and advantages achievable according to this disclosure should be present in or in any single embodiment of this disclosure. Rather, language relating to said features and advantages is understood to mean that a particular feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of this disclosure. Furthermore, the features, advantages, and characteristics of this disclosure described may be combined in one or more embodiments in any suitable manner. Those skilled in the art will recognize that this disclosure can be practiced without one or more specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be found in some embodiments that may not appear in all embodiments of this disclosure.

[0053] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE Advanced, Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc. Furthermore, communication between terminal devices and network nodes in a communication network can be implemented according to any suitable bandgap communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), 4G, 4.5G, 5G communication protocols and / or any other currently known or future-developed protocols.

[0054] The term "network node" refers to a network device in a communication network through which terminal devices access the network and receive services. A network node can refer to a base station (BS), access point (AP), multi-cell / multicast coordination entity (MCE), controller, or any other suitable device in a wireless communication network. A BS can be, for example, a Node B (or NB), an evolved Node B (eNode B or eNB), a next-generation Node B (gNode B or gNB), a remote radio unit (RRU), a radio head (RH), a remote radio headend (RRH), a repeater, a low-power node such as a femtocell or picocell, and so on.

[0055] Further examples of network nodes include: MSR radio equipment such as a Multi-Standard Radio (MSR) BS, network controllers such as a Radio Network Controller (RNC) or Base Station Controller (BSC), Base Transceiver Stations (BTS), transmission points, transmission nodes, and / or location nodes, etc. However, more generally, a network node can refer to any suitable device (or group of devices) that is capable of, configured to, arranged to, and / or operable to enable and / or provide access to a wireless communication network for terminal devices or to provide some service to terminal devices already connected to the wireless communication network.

[0056] The term "terminal device" refers to any end device that can access a communication network and receive services from it. By way of example and not limitation, terminal device can refer to a mobile terminal, user equipment (UE), or other suitable device. A UE can be, for example, a subscriber station, portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices can include, but are not limited to: portable computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback devices, mobile phones, cellular phones, smartphones, tablet computers, wearable devices, personal digital assistants (PDAs), vehicles, etc.

[0057] As another specific example, in the Internet of Things (IoT) scenario, a terminal device can also be referred to as an IoT device, and it refers to a machine or other device that performs monitoring, sensing, and / or measurement, and transmits the results of such monitoring, sensing, and / or measurement to another terminal device and / or network device. In this case, the terminal device can be a machine-to-machine (M2M) device, which in the context of the 3rd Generation Partnership Project (3GPP) can be referred to as a machine-type communication (MTC) device.

[0058] As a specific example, a terminal device can be a UE that implements the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal devices such as refrigerators, televisions, personal wearables such as watches, and so on. In other scenarios, a terminal device can represent a vehicle or other equipment, such as a medical instrument capable of monitoring, sensing, and / or reporting its operational status or other functions related to its operation.

[0059] As used herein, the terms “first,” “second,” etc., refer to different elements. Unless the context clearly indicates otherwise, the singular forms “a” and “an” are intended to include the plural forms as well. The terms “comprising,” “including,” “having,” “containing,” “comprises,” and / or “comprising” as used herein indicate the presence of the described features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. The term “based on” will be interpreted as “at least partially based on.” The terms “one embodiment” and “embodiment” will be interpreted as “at least one embodiment.” The term “another embodiment” will be interpreted as “at least one other embodiment.” Other definitions may be explicitly or implicitly included below.

[0060] Widespread deployment of wireless communication networks to provide various telecommunications services, such as voice, video, data, messaging, and broadcasting. According to 3GPP Releases 15 and 16, only unicast transmission is supported in 5G / NR communication systems. Because multicast / broadcast transmission can be very useful for certain applications (such as NSPS, V2X, etc.), a new work item (WI) was agreed upon in 3GPP Release 17 for NR to investigate broadcast / multicast transmission.

[0061] In practice, multicast / broadcast can be supported in LTE networks. There are two different ways to support multicast / broadcast: Single-Cell Point-to-Multipoint (SC-PTM) or Multimedia Broadcast Multicast Service (MBMS). These methods do not support HARQ feedback from the UE to the network. The advantage of this implementation is its simplicity. The disadvantage is its very low spectral efficiency. This is because the network does not know whether the UE has received the packet. To ensure reliability, the network may have to use a very low coding rate and may also need to repeat packet transmissions multiple times.

[0062] To address this issue, it is recommended that HARQ feedback be enabled for multicast transmissions in NR. For unicast transmissions in NR, there are two different schemes for sending HARQ feedback information bits: a semi-static codebook and a dynamic codebook. However, for multicast transmissions, it may be necessary to consider how to use an appropriate scheme to support HARQ feedback.

[0063] In NR networks supporting dynamic HARQ codebooks, the Downlink Allocation Index (DAI) in the Physical Downlink Control Channel (PDCCH) can be used to indicate how many PDCCHs have been scheduled to the UE, allowing the network and UE to have a shared understanding of how many bits are needed in the HARQ codebook. In the case of carrier aggregation, the DAI can include two fields: a counter DAI (c_DAI) and a total DAI (t_DAI). It is understood that the term "DAI" as used herein can refer to a single DAI for non-carrier aggregation scenarios, or to a combination of c_DAI and t_DAI for carrier aggregation scenarios.

[0064] For multicast transmissions, a PDCCH can be targeted at a group of UEs, and is therefore referred to as a multicast PDCCH. The DAI in a multicast PDCCH may need to be tailored to that group of UEs. UEs receiving a multicast PDCCH can also receive PDCCHs used for unicast services (also referred to herein as "unicast PDCCH"). The number of PDCCHs scheduled for unicast services over a given time interval may vary from UE to UE because scheduling decisions may differ for different UEs. Based on the rules for counting DAIs in the current version of NR—that is, using DAIs to count the number of scheduled PDCCHs—it may be impossible to set DAIs in a multicast PDCCH in many cases.

[0065] Figure 1 This diagram illustrates an exemplary DAI setting in the PDCCH according to embodiments of this disclosure. As previously described, in an NR network where a dynamic HARQ codebook can be supported, the DAI in the PDCCH can be used to indicate to the UE how many PDCCHs are scheduled for the UE, thereby allowing the network and the UE to have the same understanding regarding how many bits are needed in the HARQ codebook. For multicast transmissions, setting the DAI in the PDCCH can be somewhat challenging when scheduling multicast traffic. Figure 1 As shown, UE1 and UE2 come from the same multicast group. UE1 is scheduled for its own unicast service in time slots K=4 (where DAI=0) and K=2 (where DAI=1), while UE2 is scheduled for its own unicast service in time slot K=3 (where DAI=0). At time slot K=1, multicast service is scheduled for both UE1 and UE2. Then, according to the current rules for counting DAI in the NR, the DAI in the PDCCH at time slot K=1 may not be determined, because for UE1, DAI is 2, but for UE2, DAI is 1.

[0066] Various exemplary embodiments of this disclosure propose a solution to support multicast HARQ feedback using dynamic codebooks in NR. According to some exemplary embodiments, unicast transmissions can be scheduled using, for example, a C-RNTI (which is a unique identifier for a UE at the cell level), while multicast transmissions for multiple UEs can be scheduled using different RNTIs called G-RNTIs (which are identifiers shared by multiple UEs receiving the same multicast transmission). It is understood that although the terms "C-RNTI" and "G-RNTI" are used to refer to unicast and multicast transmissions in various exemplary embodiments, the proposed solution is also applicable to situations where unicast and multicast services can be scheduled in other ways.

[0067] According to an exemplary embodiment, the DAI in the PDCCH can be counted separately based on the RNTI (or, generally, separately for unicast and multicast services). In an embodiment, the DAI in the PDCCH scrambled by the G-RNTI can be used only to count the number of PDCCHs scheduled for the multicast group corresponding to that G-RNTI. Optionally or additionally, the DAI in the PDCCH scrambled by the C-RNTI of a particular UE can be used only to count the number of PDCCHs scheduled for that particular UE. In this way, the UE can determine whether the DAI in the PDCCH is set for multicast services (e.g., scrambled using the G-RNTI) or unicast services (e.g., scrambled using the C-RNTI).

[0068] Figure 2A-2D This is a diagram illustrating exemplary DAI settings based on RNTI according to some embodiments of the present disclosure. In exemplary embodiments, a dynamic HARQ codebook can be supported for multicast services. Figure 2A As shown, UE1 and UE2 come from the same multicast group, which can be identified by the corresponding G-RNTI. Figure 1 Similarly, UE1 is scheduled for its own unicast service in time slots K=4 and K=2, while UE2 is scheduled for its own unicast service in time slot K=3. Multicast service is scheduled for both UE1 and UE2 at time slot K=1. According to an exemplary embodiment, since this is the first scheduled multicast service in the PDCCH scrambled with G-RNTI, the DAI in the PDCCH at time slot K=1 can be set to 0, which applies to both UE1 and UE2. This DAI setting rule can also be applied to cases where the UE can support simultaneous reception of multicast and unicast services, such as... Figure 2B As stated above.

[0069] like Figure 2B As shown, UE1 and UE2 come from the same multicast group, which can be identified by the corresponding G-RNTI. Figure 2A Similarly, UE1 is scheduled for its own unicast service at timeslots K=4 and K=2, while UE2 is scheduled for its own unicast service at timeslot K=2. At timeslot K=3, UE1 is scheduled for both unicast and multicast services. According to an exemplary embodiment, since this is a second unicast PDCCH allocation using C-RNTI scrambling for UE1, the DAI in this unicast PDCCH scrambled with C-RNTI can be set to 1. Additionally, since this is a first multicast PDCCH scrambled with G-RNTI, the DAI in this multicast PDCCH scrambled with G-RNTI can be set to 0. Similarly, at timeslot K=1, UE2 is scheduled for both unicast and multicast services. According to an exemplary embodiment, since this is a second unicast PDCCH allocation using C-RNTI scrambling for UE2, the DAI in this unicast PDCCH scrambled with C-RNTI can be set to 1. Additionally, since this is the second multicast PDCCH scrambled using G-RNTI, the DAI in this multicast PDCCH scrambled using G-RNTI can be set to 1.

[0070] According to some exemplary embodiments, the proposed solution can also be applied to cases where the UE is registered to more than one multicast group and different multicast groups are assigned different G-RNTIs. According to exemplary embodiments, the DAIs in multicast PDCCHs scrambled with different G-RNTIs can be counted separately, as per [examples of specific implementations]. Figure 2C As stated above.

[0071] like Figure 2C As shown, each of UE1 and UE2 can join two multicast groups, namely group 1 which is assigned G-RNTI1. Figure 2C Group 2 (represented by Mul-1) and group 2 (assigned with G-RNTI2) Figure 2B (represented by Mul-2). In this case, the DAI for each multicast group can be counted separately according to different G-RNTIs. For example, at time slots K=4 and K=1, group 1 is scheduled, and the DAI in the PDCCH scrambled with G-RNTI1 is set to 0 and 1 respectively. At time slots K=3 and K=2, group 2 is scheduled, and the DAI in the PDCCH scrambled with G-RNTI2 is set to 0 and 1 respectively.

[0072] Figure 2D This example illustrates how, when carrier aggregation is used, the c_DAI and t_DAI fields of the DAI in the PDCCH are counted separately for multicast and unicast services. In this example, each DAI can be represented by two numbers, where the first number represents c_DAI and the second number represents t_DAI. Figure 2DAs shown, UE1 is scheduled for its own unicast service on carrier C1 at timeslots K=4 and K=2, and for its own unicast service on carrier C2 at timeslots K=4 and K=1. Additionally, UE1 is also scheduled for multicast service on carrier C1 at timeslots K=3 and K=1, and for multicast service on carrier C2 at timeslot K=2. Similarly, UE2 is scheduled for its own unicast service on carrier C1 at timeslots K=4, K=2, and K=1, and for its own unicast service on carrier C2 at timeslots K=3 and K=1. Additionally, UE2 is scheduled for multicast service on carrier C1 at timeslots K=3 and K=1, and for multicast service on carrier C2 at timeslot K=2.

[0073] It should be noted that some embodiments of this disclosure are described primarily with reference to 4G / LTE or 5G / NR specifications, which are used as non-limiting examples of specific exemplary network configurations and system deployments. Thus, the description of the exemplary embodiments given herein specifically refers to terminology directly related to them. Such terminology is used only in the context of the presented non-limiting examples and embodiments and is not intended to limit this disclosure in any way. Rather, any other system configuration or radio technology may be used equivalently, provided that the exemplary embodiments described herein are applicable.

[0074] Figure 3 This is a flowchart illustrating a method 300 according to some embodiments of the present disclosure. Figure 3 The method 300 shown can be implemented by a terminal device or a means communicatively coupled to the terminal device. According to an exemplary embodiment, a terminal device such as a UE can be configured to obtain various services (e.g., unicast services, multicast services, etc.) from a network node such as a gNB, and send HARQ feedback for the services to the network node, for example, according to a dynamic codebook.

[0075] according to Figure 3 The exemplary method 300 shown allows a terminal device to receive a first downlink channel (e.g., PDCCH, etc.) including a first DAI from a network node, as shown in block 302. The first downlink channel may be associated with a first service of the terminal device. According to an exemplary embodiment, based on the association between the first downlink channel and the first service, the terminal device can determine that the first DAI is used for the first service, as shown in block 304.

[0076] According to an exemplary embodiment, the first downlink channel can be associated with the first service by scrambling the first downlink channel using a first RNTI corresponding to the first service. It is understood that the first downlink channel can also be associated with the first service in other suitable ways, for example, by explicitly or implicitly including an indicator of the first service in the first downlink channel or other suitable signaling / message.

[0077] According to an exemplary embodiment, the first RNTI may be a first multicast group for receiving the first multicast service (e.g., Figure 2C The first G-RNTI (e.g., Mul-1 or Mul-2) in Mul-1 or Mul-2 Figure 2C (G-RNTI1 or G-RNTI2 in the original text). In this case, the first service can be a first multicast service for the terminal device. According to another exemplary embodiment, the first RNTI can be a C-RNTI for the terminal device. In this case, the first service can be a unicast service for the terminal device.

[0078] According to an exemplary embodiment, the terminal device can support receiving two or more services from the network node simultaneously or not simultaneously. In this case, the network node can set up different DAIs for different services. Accordingly, the terminal device can process DAIs separately for different services. According to an exemplary embodiment, the first DAI for a first service can be separate from the second DAI for a second service.

[0079] According to an exemplary embodiment, the terminal device can receive a second downlink channel (e.g., PDCCH, etc.) including a second DAI from the network node. The second downlink channel can be associated with a second service of the terminal device. Based on the association between the second downlink channel and the second service, the terminal device can determine that the second DAI is used for the second service.

[0080] According to an exemplary embodiment, by scrambling the second downlink channel using a second RNTI corresponding to the second service, the second downlink channel can be associated with the second service. According to an exemplary embodiment, the second RNTI can be a second multicast group (e.g., for receiving the second multicast service) used for receiving the second multicast service. Figure 2C The second G-RNTI (e.g., Mul-2 or Mul-1) in Mul-2) Figure 2C (G-RNTI2 or G-RNTI1 in the example). In this case, the second service can be a second multicast service for the terminal device.

[0081] According to an exemplary embodiment, the first DAI may include one or more fields for the first carrier (e.g., Figure 2D(C1 or C2 in the original text). For example, the first DAI may include a single DAI for non-carrier aggregation cases (such as...). Figure 2A , Figure 2B and Figure 2C (as shown), or the case of carrier aggregation including a combination of c_DAI and t_DAI (as shown). Figure 2D (As shown). Similarly, the second DAI may include one or more fields for the second carrier (e.g. Figure 2D (C2 or C1 in the text).

[0082] Figure 4 This is a flowchart illustrating a method 400 according to some embodiments of the present disclosure. Figure 4 The method 400 shown can be implemented by a network node or a means communicatively coupled to a network node. According to an exemplary embodiment, the network node may include a base station such as a gNB. The network node may be configured to provide various services (e.g., unicast services, multicast services, etc.) to one or more terminal devices such as UEs.

[0083] according to Figure 4 The exemplary method 400 shown indicates that the network node can determine the purpose of the terminal device (e.g., regarding...). Figure 3 The first DAI of the first service of the terminal device is shown in block 402. According to an exemplary embodiment, the network node may send a first downlink channel including the first DAI to the terminal device, as shown in block 404. The first downlink channel may be associated with the first service, for example, by scrambling the first downlink channel using a first RNTI corresponding to the first service, or in any other suitable manner.

[0084] According to an exemplary embodiment, the network node can determine a second DAI for a second service of the terminal device and send a second downlink channel including the second DAI to the terminal device. The second downlink channel can be associated with the second service, for example, by scrambling the second downlink channel using a second RNTI corresponding to the second service, or in any other suitable manner.

[0085] Understandable. Figure 4 The steps, operations, and related configurations of method 400 shown can be compared with... Figure 3The steps, operations, and related configurations of method 300 shown correspond to each other. Therefore, the first downlink channel including the first DAI received by the terminal device according to method 300 can correspond to the first downlink channel including the first DAI transmitted by the network node according to method 400. Similarly, the second downlink channel including the second DAI received by the terminal device according to method 300 can correspond to the second downlink channel including the second DAI transmitted by the network node according to method 400.

[0086] It's understandable, regarding Figure 4 The first DAI and the second DAI can respectively correspond to the information regarding... Figure 3 The first DAI and the second DAI mentioned above. Similarly, regarding... Figure 4 The first RNTI and the second RNTI can respectively correspond to the information about Figure 3 The first RNTI and the second RNTI.

[0087] Various exemplary embodiments of this disclosure enable the DAI in the PDCCH to be set or counted separately for multicast and unicast services. According to exemplary embodiments, the DAI in the PDCCH can be counted or set based on a scrambled RNTI, which may correspond to a unique multicast group or unicast service of the UE. In embodiments used for carrier aggregation, different fields, such as c_DAI and t_DAI, can be set or counted separately for multicast and unicast services. The application of these exemplary embodiments can enhance network performance with flexible service scheduling and improved resource utilization, because both the network and the UE can have the same understanding of how many bits are needed in the HARQ codebook, while supporting dynamic HARQ codebooks for multicast services.

[0088] Figures 3 to 4 The various blocks shown can be considered as method steps, and / or operations generated by the operation of computer program code, and / or multiple coupled logic circuit elements constructed to perform related functions. The schematic flowcharts described above are generally presented as logic flowcharts. Thus, the depicted sequence and labeled steps indicate specific embodiments of the proposed method. Other steps and methods are contemplated that are functionally, logically, or effectively equivalent to one or more steps or portions thereof of the illustrated method. Furthermore, the order in which a particular method occurs may or may not strictly adhere to the order of the corresponding steps shown.

[0089] Figure 5 This is a block diagram illustrating an apparatus 500 according to various embodiments of the present disclosure. Figure 5As shown, device 500 may include one or more processors (e.g., processor 501) and one or more memories (e.g., memory 502 storing computer program code 503). Memory 502 may be a non-transient machine / processor / computer-readable storage medium. According to some exemplary embodiments, device 500 may be implemented as an integrated circuit chip or module that can be inserted into or mounted to, as per [the relevant specification] Figure 3 The described terminal device, or one that can be plugged into or installed as per the description of... Figure 4 The network node described. In this case, device 500 can be implemented as described regarding Figure 3 The described terminal device, or as about Figure 4 The network node described.

[0090] In some implementations, one or more memories 502 and computer program code 503 may be configured together with one or more processors 501 to cause the device 500 to at least implement the combination Figure 3 Any operation of the described method. In other implementations, one or more memories 502 and computer program code 503 may be configured together with one or more processors 501 to cause the device 500 to at least implement as described in the combination. Figure 4 Any operation of the described method. Optionally or additionally, one or more memories 502 and computer program code 503 may be configured, together with one or more processors 501, to cause the apparatus 500 to perform at least more or fewer operations to implement the method proposed according to exemplary embodiments of this disclosure.

[0091] Figure 6A This is a block diagram illustrating an apparatus 610 according to some embodiments of the present disclosure. (See diagram for example.) Figure 6A As shown, apparatus 610 may include a receiving unit 611 and a determining unit 612. In an exemplary embodiment, apparatus 610 may be implemented in a terminal device such as a UE. The receiving unit 611 is operable to perform the operations in block 302, and the determining unit 612 is operable to perform the operations in block 304. Optionally, the receiving unit 611 and / or the determining unit 612 may be operable to perform more or fewer operations to implement the method proposed according to an exemplary embodiment of this disclosure.

[0092] Figure 6B This is a block diagram illustrating an apparatus 620 according to some embodiments of the present disclosure. Figure 6BAs shown, apparatus 620 may include a determining unit 621 and a transmitting unit 622. In an exemplary embodiment, apparatus 620 may be implemented in a network node such as a base station. The determining unit 621 is operable to perform the operations in block 402, and the transmitting unit 622 is operable to perform the operations in block 404. Optionally, the determining unit 621 and / or the transmitting unit 622 may be operable to perform more or fewer operations to implement the method proposed according to an exemplary embodiment of this disclosure.

[0093] Figure 7 This is a block diagram illustrating a telecommunications network connected to a host computer via an intermediate network according to some embodiments of the present disclosure.

[0094] refer to Figure 7 According to an embodiment, the communication system includes a telecommunications network 710 (such as a 3GPP-type cellular network), which includes an access network 711 (such as a radio access network) and a core network 714. The access network 711 includes multiple base stations 712a, 712b, 712c, such as NBs, eNBs, gNBs, or other types of radio access points, each defining a corresponding coverage area 713a, 713b, 713c. Each base station 712a, 712b, 712c can be connected to the core network 714 via a wired or wireless connection 715. A first UE 791 located in coverage area 713c is configured to wirelessly connect to or be paged by the corresponding base station 712c. A second UE 792 in coverage area 713a can wirelessly connect to the corresponding base station 712a. Although multiple UEs 791, 792 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is in a coverage area or a single UE is connected to a corresponding base station 712.

[0095] Telecommunications network 710 is connected to host computer 730, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server cluster. Host computer 730 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. Connections 721 and 722 between telecommunications network 710 and host computer 730 may extend directly from core network 714 to host computer 730, or may traverse an optional intermediate network 720. Intermediate network 720 may be one or a combination of public networks, private networks, or hosted networks; intermediate network 720 (if any) may be a backbone network or the Internet; in particular, intermediate network 720 may include two or more subnetworks (not shown).

[0096] Figure 7The communication system generally implements the connection between the connected UEs 791 and 792 and the host computer 730. This connection can be described as an over-the-top (OTT) connection 750. The host computer 730 and the connected UEs 791 and 792 are configured to transmit data and / or signaling via the OTT connection 750 using access network 711, core network 714, any intermediate network 720, and possibly other infrastructure (not shown) as intermediaries. The OTT connection 750 can be transparent from the perspective that the participating communication devices are unaware of the routes of uplink and downlink communications. For example, the base station 712 may not be informed or need not be informed of the past routes of incoming downlink communications originating from the host computer 730 that are to be forwarded (e.g., switched) to the connected UE 791. Similarly, the base station 712 does not need to know the future routes of outgoing uplink communications originating from the UE 791 toward the host computer 730.

[0097] Figure 8 This is a block diagram illustrating a host computer communicating with a UE via a base station over a partially wireless connection according to some embodiments of the present disclosure.

[0098] Now refer to Figure 8 This section describes an example implementation of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments. In communication system 800, host computer 810 includes hardware 815, which includes a communication interface 816 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of communication system 800. Host computer 810 also includes processing circuitry 818, which may have storage and / or processing capabilities. In particular, processing circuitry 818 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such components (not shown) suitable for executing instructions. Host computer 810 also includes software 811, which is stored in or accessible by host computer 810 and executable by processing circuitry 818. Software 811 includes host application 812. Host application 812 is operable to provide services to remote users, such as UE 830 connected via an OTT connection 850 terminated between UE 830 and host computer 810. When providing services to remote users, host application 812 can provide user data transmitted using OTT connection 850.

[0099] The communication system 800 also includes a base station 820 provided in the telecommunications system. The base station 820 includes hardware 825 enabling it to communicate with the host computer 810 and the UE 830. Hardware 825 may include a communication interface 826 for establishing and maintaining wired or wireless connections to different communication devices of the communication system 800, and for establishing and maintaining connections with the coverage area served by the base station 820. Figure 8 The UE 830 (not shown) has at least a radio interface 827 for a wireless connection 870. A communication interface 826 can be configured to facilitate a connection 860 to a host computer 810. The connection 860 can be direct, or it can traverse the core network of a telecommunications system. Figure 8 (Not shown) and / or through one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 825 of the base station 820 also includes processing circuitry 828, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such components (not shown) adapted to execute instructions. The base station 820 also has software 821 stored internally or accessible via an external connection.

[0100] The communication system 800 also includes the already cited UE 830. Its hardware 835 may include a radio interface 837 configured to establish and maintain a radio connection 870 with a base station serving the coverage area currently occupied by the UE 830. The hardware 835 of the UE 830 also includes processing circuitry 838, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of these components (not shown) suitable for executing instructions. The UE 830 also includes software 831, which is stored in or accessible by the UE 830 and executable by the processing circuitry 838. The software 831 includes a client application 832. The client application 832 is operable to provide services to human or non-human users via the UE 830 with the support of the host computer 810. In the host computer 810, a executing host application 812 may communicate with the executing client application 832 via an OTT connection 850 terminated between the UE 830 and the host computer 810. When providing services to a user, client application 832 can receive request data from host application 812 and provide user data in response to the request data. OTT connection 850 can transmit both request data and user data. Client application 832 can interact with the user to generate the user data it provides.

[0101] It is important to note that Figure 8 The host computer 810, base station 820, and UE 830 shown can be respectively connected to... Figure 7The host computer 730, base stations 712a, 712b, and 712c, and UEs 791 and 792 are similar to or identical to each other. That is to say, the internal workings of these entities can be as follows: Figure 8 As shown, and independently, the surrounding network topology can be Figure 7 The network topology.

[0102] exist Figure 8 In this diagram, OTT connection 850 is abstractly depicted to illustrate communication between host computer 810 and UE 830 via base station 820, without explicitly involving any intermediate devices or the precise routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to hide the routing for UE 830 or the service provider operating host computer 810, or both. When OTT connection 850 is active, the network infrastructure can further make dynamic decisions to change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0103] The wireless connection 870 between UE 830 and base station 820 is based on the teachings of the embodiments described throughout this disclosure. One or more embodiments in various embodiments use OTT connection 850 to improve the performance of OTT services provided to UE 830, wherein wireless connection 870 forms the final segment. More specifically, the teachings of these embodiments can improve latency and power consumption, thereby providing benefits such as lower complexity, reduced time required to access the cell, better responsiveness, and extended battery life.

[0104] Measurement procedures can be provided to monitor data rates, latency, and other factors improved by one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection 850 between the host computer 810 and the UE 830 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 850 may be implemented in the software 811 and hardware 815 of the host computer 810, or in the software 831 and hardware 835 of the UE 830, or both. In embodiments, sensors (not shown) may be deployed in or associated with the communication equipment through which the OTT connection 850 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which the software 811, 831 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 850 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect the base station 820, and the base station 820 may be unaware of or unaware of the reconfiguration. These procedures and functions may be known and practiced in the art. In some embodiments, the measurement may involve proprietary UE signaling, which facilitates the host computer 810 in measuring throughput, propagation time, latency, etc. The measurement can be implemented such that software 811 and 831, while monitoring propagation time, errors, etc., use OTT connection 850 to transmit messages (particularly empty messages or "dummy" messages).

[0105] Figure 9 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 7 and Figure 8 Those described. To simplify this disclosure, only those described herein are included in this section. Figure 9 Referring to the accompanying drawings. In step 910, the host computer provides user data. In sub-step 911 of step 910 (which may be optional), the host computer provides user data by executing a host application. In step 920, the host computer initiates a transmission carrying user data to the UE. In step 930 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station transmits the user data carried in the transmission initiated by the host computer to the UE. In step 940 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0106] Figure 10 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 7 and Figure 8Those described. To simplify this disclosure, only those described herein are included in this section. Figure 10 Refer to the accompanying drawings. In step 1010 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides user data by executing a host application. In step 1020, the host computer initiates a transmission carrying user data to the UE. According to the teachings of the embodiments described throughout this disclosure, the transmission may pass through a base station. In step 1030 (which may be optional), the UE receives the user data carried in the transmission.

[0107] Figure 11 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 7 and Figure 8 Those described. To simplify this disclosure, only those described herein are included in this section. Figure 11 Referring to the accompanying drawings. In step 1110 (which may be optional), the UE receives input data provided by the host computer. Additionally or optionally, in step 1120, the UE provides user data. In sub-step 1121 of step 1120 (which may be optional), the UE provides user data by executing a client application. In sub-step 1111 of step 1110 (which may be optional), the UE executes a client application that provides user data in response to the received input data provided by the host computer. When providing user data, the executed client application may also consider user input received from the user. Regardless of the specific manner in which user data is provided, the UE initiates a transmission of user data to the host computer in sub-step 1130 (which may be optional). In step 1140 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0108] Figure 12 This is a flowchart illustrating a method implemented in a communication system according to an embodiment. The communication system includes a host computer, a base station, and a UE, which may be referenced... Figure 7 and Figure 8 Those described. To simplify this disclosure, only those described herein are included in this section. Figure 12 Refer to the accompanying drawings. In step 1210 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1220 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In step 1230 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0109] According to some exemplary embodiments, a method is provided implemented in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include: providing user data at the host computer. Optionally, the method may include: at the host computer, initiating a transmission carrying user data for the UE via a cellular network including a base station, the base station being capable of implementing [further details regarding the transmission method]. Figure 4 Any step of the exemplary method 400 described.

[0110] According to some exemplary embodiments, a communication system including a host computer is provided. The host computer may include: processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The cellular network may include a base station having a radio interface and processing circuitry. The processing circuitry of the base station may be configured to implement as described above. Figure 4 Any step of the exemplary method 400 described.

[0111] According to some exemplary embodiments, a method is provided implemented in a communication system, which may include a host computer, a base station, and a UE. The method may include: providing user data at the host computer. Optionally, the method may include: initiating, at the host computer, a transmission carrying user data for the UE via a cellular network including the base station. The UE may implement as described above. Figure 3 Any step of the exemplary method 300 described.

[0112] According to some exemplary embodiments, a communication system including a host computer is provided. The host computer may include: processing circuitry configured to provide user data, and a communication interface configured to forward the user data to a cellular network for transmission to a UE. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to implement as described above. Figure 3 Any step of the exemplary method 300 described.

[0113] According to some exemplary embodiments, a method is provided implemented in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include: at the host computer, receiving user data transmitted from the UE to the base station, the UE being able to implement as described above. Figure 3 Any step of the exemplary method 300 described.

[0114] According to some exemplary embodiments, a communication system including a host computer is provided. The host computer may include a communication interface configured to receive user data originating from transmissions from a UE to a base station. The UE may include a radio interface and processing circuitry. The processing circuitry of the UE may be configured to implement, as per [example of exemplary embodiments], [further details about the UE]. Figure 3 Any step of the exemplary method 300 described.

[0115] According to some exemplary embodiments, a method is provided implemented in a communication system, which may include a host computer, a base station, and a user equipment (UE). The method may include, at the host computer, receiving from the base station user data transmitted to the UE. The base station may be implemented as described above. Figure 4 Any step of the exemplary method 400 described.

[0116] According to some exemplary embodiments, a communication system including a host computer is provided. The host computer may include a communication interface configured to receive user data originating from transmissions from a UE to a base station. The base station may include a radio interface and processing circuitry. The processing circuitry of the base station may be configured to implement, as per [specific example description needed] Figure 4 Any step of the exemplary method 400 described.

[0117] Generally, various exemplary embodiments can be implemented using hardware or dedicated chips, circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software executable by a controller, microprocessor, or other computing device, although this disclosure is not limited thereto. While various aspects of exemplary embodiments of this disclosure may be illustrated and described as block diagrams, flowcharts, or other graphical representations, it is understood that such blocks, apparatuses, systems, techniques, or methods described herein may be implemented as non-limiting examples in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controllers, or other computing devices, or combinations thereof.

[0118] Thus, it should be recognized that at least some aspects of the exemplary embodiments of this disclosure can be practiced in various components such as integrated circuit chips and modules. Therefore, it should be understood that exemplary embodiments of this disclosure can be implemented in devices embodied as integrated circuits, wherein the integrated circuits may include at least circuitry (and possible firmware) embodying one or more of a data processor, digital signal processor, baseband circuitry, and radio frequency circuitry that can be configured to operate according to exemplary embodiments of this disclosure.

[0119] It should be understood that at least some aspects of the exemplary embodiments of this disclosure may be embodied in computer-executable instructions, such as those in one or more program modules, which are executed by one or more computers or other devices. Typically, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type when executed by a processor in a computer or other device. The computer-executable instructions may be stored on a computer-readable medium such as a hard disk, optical disk, removable storage medium, solid-state memory, random access memory (RAM), etc. As those skilled in the art will understand, the functionality of program modules may be combined or distributed as needed in various embodiments. Furthermore, the functionality may be wholly or partially embodied in firmware or hardware equivalents (such as integrated circuits, field-programmable gate arrays (FPGAs), etc.).

[0120] This disclosure includes any novel features or combinations of features expressly disclosed herein or arbitrarily generalized herein. In view of the foregoing description, various modifications and adaptations to the foregoing exemplary embodiments of this disclosure will become apparent to those skilled in the art when read in conjunction with the accompanying drawings. However, any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure.

Claims

1. A method (300) implemented by a terminal device, comprising: Receive (302) from network node a first downlink channel including a first downlink allocation index (DAI), wherein the first downlink channel is associated with a first service of the terminal device; and Based on the association between the first downlink channel and the first service, determine (304) that the first downlink allocation index is used for the first service; Wherein, the first downlink channel is scrambled using a first radio network temporary identifier (RNTI) corresponding to the first service, and the first downlink channel is associated with the first service; the first radio network temporary identifier is a first group of radio network temporary identifiers (G-RNTI) for receiving a first multicast group of a first multicast service; the first service is the first multicast service used by the terminal device. Receive from the network node a second downlink channel including a second downlink allocation index, wherein the second downlink channel is associated with a second service of the terminal device; and Based on the association between the second downlink channel and the second service, the second downlink allocation index is determined for the second service; Wherein, the second downlink channel is scrambled using a second radio network temporary identifier corresponding to the second service, and the second downlink channel is associated with the second service; the second radio network temporary identifier is a second set of radio network temporary identifiers for a second multicast group used to receive the second multicast service; the second service is the second multicast service used by the terminal device; The first downlink allocation index used for the first service and the second downlink allocation index used for the second service are counted separately.

2. The method according to claim 1, wherein, The first downlink allocation index includes one or more fields for the first carrier.

3. The method according to claim 1 or 2, wherein, The second downlink allocation index includes one or more fields for the second carrier.

4. A terminal device (500), comprising: One or more processors (501); as well as One or more memories (502) including computer program code (503), The one or more memories (502) and the computer program code (503) are configured, together with the one or more processors (501), to cause the terminal device (500) to at least: Receives from a network node a first downlink channel including a first downlink allocation index (DAI), wherein the first downlink channel is associated with a first service of the terminal device; and Based on the association between the first downlink channel and the first service, the first downlink allocation index is determined to be used for the first service; Wherein, the first downlink channel is scrambled using a first radio network temporary identifier (RNTI) corresponding to the first service, and the first downlink channel is associated with the first service; the first radio network temporary identifier is a first group of radio network temporary identifiers (G-RNTI) for receiving a first multicast group of a first multicast service; the first service is the first multicast service used by the terminal device. Receive from the network node a second downlink channel including a second downlink allocation index, wherein the second downlink channel is associated with a second service of the terminal device; and Based on the association between the second downlink channel and the second service, the second downlink allocation index is determined for the second service; Wherein, the second downlink channel is scrambled using a second radio network temporary identifier corresponding to the second service, and the second downlink channel is associated with the second service; the second radio network temporary identifier is a second set of radio network temporary identifiers for a second multicast group used to receive the second multicast service; the second service is the second multicast service used by the terminal device; The first downlink allocation index used for the first service and the second downlink allocation index used for the second service are counted separately.

5. The terminal device according to claim 4, wherein, The one or more memories and the computer program code are configured, together with the one or more processors, to cause the terminal device to implement the method according to any one of claims 2-3.

6. A computer-readable medium having thereon computer program code (503) that, when executed on a computer, causes the computer to perform any step of the method according to any one of claims 1-3.

7. A method (400) implemented by a network node, comprising: Determine (402) the first downlink allocation index (DAI) for the first service of the terminal equipment; as well as Send (404) a first downlink channel including the first downlink allocation index to the terminal device, wherein the first downlink channel is associated with the first service; Wherein, the first downlink channel is scrambled using a first radio network temporary identifier (RNTI) corresponding to the first service to associate the first downlink channel with the first service; the first radio network temporary identifier is a first group of radio network temporary identifiers (G-RNTI) for the terminal device to receive the first multicast service; the first service is the first multicast service for the terminal device. Determine the second downlink allocation index for the second service of the terminal device; and Send a second downlink channel, including the second downlink allocation index, to the terminal device, wherein the second downlink channel is associated with the second service; The second downlink channel is scrambled using a second radio network temporary identifier corresponding to the second service to associate the second downlink channel with the second service; the second radio network temporary identifier is a second set of radio network temporary identifiers for the second multicast group used by the terminal device to receive the second multicast service; the second service is the second multicast service used by the terminal device. The first downlink allocation index used for the first service and the second downlink allocation index used for the second service are counted separately.

8. The method according to claim 7, wherein, The first downlink allocation index includes one or more fields for the first carrier.

9. The method according to claim 7 or 8, wherein, The second downlink allocation index includes one or more fields for the second carrier.

10. A network node (500), comprising: One or more processors (501); as well as One or more memories (502) including computer program code (503), The one or more memories (502) and the computer program code (503) are configured, together with the one or more processors (501), to cause the network node (500) to at least: Determine the first downlink allocation index for the first service used by the terminal device; as well as Send a first downlink channel including the first downlink allocation index to the terminal device, wherein the first downlink channel is associated with the first service; Wherein, the first downlink channel is scrambled using a first radio network temporary identifier (RNTI) corresponding to the first service to associate the first downlink channel with the first service; the first radio network temporary identifier is a first group of radio network temporary identifiers (G-RNTI) for the terminal device to receive the first multicast service; the first service is the first multicast service for the terminal device. Determine the second downlink allocation index for the second service of the terminal device; and Send a second downlink channel, including the second downlink allocation index, to the terminal device, wherein the second downlink channel is associated with the second service; The second downlink channel is scrambled using a second radio network temporary identifier corresponding to the second service to associate the second downlink channel with the second service; the second radio network temporary identifier is a second set of radio network temporary identifiers for the second multicast group used by the terminal device to receive the second multicast service; the second service is the second multicast service used by the terminal device. The first downlink allocation index used for the first service and the second downlink allocation index used for the second service are counted separately.

11. The network node according to claim 10, wherein, The one or more memories and the computer program code are configured, together with the one or more processors, to cause the network node to implement the method according to any one of claims 8-9.

12. A computer-readable medium having thereon computer program code (503) that, when executed on a computer, causes the computer to perform any step of the method according to any one of claims 7-9.

13. A communication system including a host computer, the host computer comprising: Processing circuitry, configured to provide user data; as well as A communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The UE includes a radio interface and processing circuitry, wherein the processing circuitry of the UE is configured to implement the method according to any one of claims 1-3.

14. The communication system according to claim 13, further comprising the UE.

15. The communication system according to claim 14, wherein, The cellular network also includes base stations configured to communicate with the UE.

16. The communication system according to claim 14 or 15, wherein: The processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and The UE's processing circuitry is configured to execute a client application associated with the host application.

17. A communication system including a host computer, the host computer comprising: Processing circuitry, configured to provide user data; as well as A communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE). The cellular network includes a base station having a radio interface and processing circuitry, the processing circuitry of which is configured to implement the method according to any one of claims 7-9.

18. The communication system according to claim 17, further comprising the base station.

19. The communication system according to claim 18, further comprising the UE, wherein, The UE is configured to communicate with the base station.

20. The communication system according to claim 18 or 19, wherein: The processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and The UE includes processing circuitry configured to execute client applications associated with the host application.

21. A communication system including a host computer, the host computer comprising: The communication interface is configured to receive user data transmitted from the user equipment (UE) to the base station. The UE includes a radio interface and processing circuitry, wherein the processing circuitry of the UE is configured to implement the method according to any one of claims 1-3.

22. The communication system according to claim 21, further comprising the UE.

23. The communication system according to claim 22, further comprising the base station, wherein, The base station includes a radio interface and a communication interface. The radio interface is configured to communicate with the UE, and the communication interface is configured to forward the user data carried by the transmission from the UE to the base station to the host computer.

24. The communication system according to claim 22 or 23, wherein: The processing circuitry of the host computer is configured to execute host applications; and The UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

25. A communication system including a host computer, the host computer comprising: The communication interface is configured to receive user data transmitted from the user equipment (UE) to the base station. The base station includes a radio interface and processing circuitry, wherein the processing circuitry is configured to implement the method according to any one of claims 7-9.

26. The communication system according to claim 25, further comprising the base station.

27. The communication system according to claim 26, further comprising the UE, wherein, The UE is configured to communicate with the base station.

28. The communication system according to claim 26 or 27, wherein: The processing circuitry of the host computer is configured to execute host applications; The UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

Images