HARQ feedback codebook for multicast and unicast

Abstract

A wireless device (110) obtains a codebook based on a first set of downlink data to uplink feedback timing for feedback associated with multicast downlink data (30) and a second set of downlink data to uplink feedback timing for feedback associated with unicast downlink data (31). A number of downlink slots associated with the codebook is determined based on a union of the first set and the second set. The wireless device transmits feedback to a network node (160) based on the codebook. A number of feedback bits in the codebook for downlink slots associated with the codebook is determined based on a union of a first time domain resource allocation (TDRA) list and a second TDRA list (32). The first list indicates possible allocations of symbols to a downlink shared channel for multicast. The second list indicates possible allocations of symbols to a downlink shared channel for unicast.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more specifically to systems and methods for designing hybrid automatic repeat request (HARQ) feedback codebooks for use by multicast and unicast services, for example, in new radios (NR). Background Technology

[0002] The fifth-generation mobile wireless communication system (5G), or New Radio (NR), has already been specified in the 3rd Generation Partnership Project (3GPP). To date, it includes two versions: Version 15 (R-15) and Version 16 (R-16). Only unicast transmission is supported. Because multicast / broadcast transmission is very useful for some applications (such as NSPS (Network Security and Public Safety), V2X (Vehicle-to-Everything), etc.), it has been agreed that broadcast / multicast transmission in NR Version 17 (R-17) should be studied.

[0003] In fact, multicast / broadcast is already supported in LTE. There are two different ways to support multicast / broadcast: Single-Cell Point-to-Multipoint (SC-PTM) or Multimedia Broadcast Multicast Service (MBMS). Regardless of the method used, there is no feedback from the User Equipment (UE) to the network. The advantage of this method is its simplicity. The disadvantage is its low spectral efficiency. This is because the network does not know whether the UE has received the packet. To ensure reliability, it must use a very low coding rate and may also need to repeat the transmission several times.

[0004] To address this issue, it has been proposed to enable Hybrid Automatic Repeat Request (HARQ) feedback for multicast transmissions in NR. One question regarding HARQ feedback for multicast is how to send it, particularly when HARQ feedback for unicast exists and they need to be sent within the same uplink (UL) time slot.

[0005] In NR, an adaptive retransmission scheme known as Hybrid Automatic Repeat Request (HARQ) is widely used. According to this scheme, the receiver of a packet sends an ACK or NACK response to the sender, depending on whether the receiver has successfully or unsuccessfully decoded the transport block. If it is an ACK, the sender will send a new transport block; if it is a NACK, the sender will retransmit the same or a different version of the initial transport block. Multiple retransmission attempts can occur for a single data transport block. As used herein, the term multicast refers to a transmission in the downlink from a network node (such as a gNB) to a group of radio devices (such as a UE). In this document, the terms multicast and point-to-multipoint (PTM) are used interchangeably.

[0006] The Physical Downlink Shared Channel (PDSCH) can be scheduled across a different number of Orthogonal Frequency Division Multiplexing (OFDM) symbols in a time slot, occupying consecutive symbols. The PDSCH configuration includes a so-called Time Domain Resource Allocation (TDRA) list. Figure 1 An example of a TDRA list is shown. Specifically, Figure 1 Different entries in the PDSCHTDRA list with corresponding assignments for symbols used in PDSCH are shown. As an example, TDRA entry 1 corresponds to the PDSCH assignments for symbols from 3 to 8, and entry 2 corresponds to the PDSCH assignments for symbols from 5 to 10, and so on.

[0007] The TDRA list is sometimes also referred to as a set. Each entry in the TDRA list defines a sequence of consecutive symbols that the gNodeB (gNB) can select. The gNB maps the PDSCH to the selected symbol sequence. The gNB has selected which entry for a specific time slot by signaling it to the UE in the Physical Downlink Control Channel (PDCCH).

[0008] The UE may miss the PDCCH in a time slot and therefore may not know that the gNB is scheduling the PDSCH in a time slot where it has been scheduled. However, the UE knows which time slots the gNB can schedule the PDSCH in. Therefore, if the UE does not receive the PDCCH in such a time slot, the UE should send as many HARQNACK signals as there are entries in the TDRA list containing non-overlapping (intersecting) symbol sequences. NACK is signaled as a 1-bit value in the so-called HARQ codebook. Here, we consider a Type 1 codebook or a semi-static codebook. For example, the Type 1 HARQ-ACK codebook construction is specified in 3GPP TS 38.213 Technical Specification Group Radio Access Networks; NR; Multiplexing and Channel Coding; v16.5.0.

[0009] There are some issues. For example, one problem might be that there is no clear method for designing the HARQ codebook when multicast needs to send its HARQ feedback along with unicast services. Summary of the Invention

[0010] Certain aspects of this disclosure and its embodiments may provide solutions to these or other challenges.

[0011] The first aspect provides an embodiment of a method performed by a wireless device. The method includes obtaining a codebook based on a first downlink data-to-uplink feedback timing set for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set for feedback associated with unicast downlink data. The number of downlink slots associated with the codebook is determined based on the union of the first downlink data-to-uplink feedback timing set and the second downlink data-to-uplink feedback timing set. The method includes sending feedback to a network node based on the codebook. The number of feedback bits in the codebook for the downlink slots associated with the codebook is determined based on the union of a first Time Domain Resource Allocation (TDRA) list and a second TDRA list. The first TDRA list indicates possible allocations of symbols for a downlink shared channel used for multicast downlink data. The second TDRA list indicates possible allocations of symbols for a downlink shared channel used for unicast downlink data.

[0012] The second aspect provides an embodiment of a wireless device including processing circuitry. The processing circuitry is configured to obtain a codebook based on a first downlink data-to-uplink feedback timing set for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set for feedback associated with unicast downlink data. The number of downlink slots associated with the codebook is determined based on the union of the first downlink data-to-uplink feedback timing set and the second downlink data-to-uplink feedback timing set. The processing circuitry is configured to send feedback to network nodes based on the codebook. The number of feedback bits in the codebook for the downlink slots associated with the codebook is determined based on the union of a first TDRA list and a second TDRA list. The first TDRA list indicates possible allocations of symbols for the downlink shared channel used for multicast downlink data. The second TDRA list indicates possible allocations of symbols for the downlink shared channel used for unicast downlink data.

[0013] The third aspect provides an embodiment of a method performed by a network node. The method includes obtaining a codebook based on a first downlink data-to-uplink feedback timing set for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set for feedback associated with unicast downlink data. The number of downlink slots associated with the codebook is determined based on the union of the first downlink data-to-uplink feedback timing set and the second downlink data-to-uplink feedback timing set. The method includes receiving feedback from a wireless device based on the codebook. The number of feedback bits in the codebook for the downlink slots associated with the codebook is determined based on the union of a first TDRA list and a second TDRA list. The first TDRA list indicates possible allocations of symbols for a downlink shared channel used for multicast downlink data. The second TDRA list indicates possible allocations of symbols for a downlink shared channel used for unicast downlink data.

[0014] The fourth aspect provides an embodiment of a network node including processing circuitry. This processing circuitry is configured to obtain a codebook based on a first downlink data-to-uplink feedback timing set for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set for feedback associated with unicast downlink data. The number of downlink slots associated with the codebook is determined based on the union of the first downlink data-to-uplink feedback timing set and the second downlink data-to-uplink feedback timing set. The processing circuitry is configured to receive feedback from a wireless device based on the codebook. The number of feedback bits in the codebook for the downlink slots associated with the codebook is determined based on the union of a first TDRA list and a second TDRA list. The first TDRA list indicates possible allocations of symbols for the downlink shared channel used for multicast downlink data. The second TDRA list indicates possible allocations of symbols for the downlink shared channel used for unicast downlink data.

[0015] For example, according to some embodiments, methods and systems for constructing HARQ-ACK codebooks are provided.

[0016] According to some embodiments, for example, the construction of the HARQ-ACK codebook for combining multicast and unicast services is based on the union of the downlink data to UL feedback timing sets of both multicast and unicast services. According to some embodiments, when using fallback DCI, this downlink data to UL feedback timing set can be a predefined {1, 2, 3, 4, 5, 6, 7, 8}, or when using non-fallback DCI, this downlink data to UL feedback timing set can be configured in dl-DataToUL-ACK.

[0017] In a particular embodiment, the values ​​in the union of the sets of downlink data to UL feedback times determine the number of downlink (DL) slots associated with the codebook, while the values ​​in the intersection of these sets affect the number of HARQ feedback bits for each DL slot.

[0018] Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that certain embodiments provide a combined HARQ codebook for unicast and multicast. Using a combined codebook can be more efficient. For example, compared to systems and techniques that use separate codebooks for unicast and multicast, using a combined codebook can reduce overall signaling overhead.

[0019] Other advantages may be apparent to those skilled in the art. Some embodiments may lack the advantages described, or may have some or all of the advantages described. Attached Figure Description

[0020] To gain a more complete understanding of the disclosed embodiments, their features and advantages, the following description is now taken in conjunction with the accompanying drawings, in which:

[0021] Figure 1 A list of example TDRAs is shown;

[0022] Figure 2 The construction of a type 1HARQ-ACK codebook is illustrated according to certain embodiments when there is no overlap between the configured dl-DataToUL-ACK sets for unicast and multicast;

[0023] Figure 3 The construction of a type 1HARQ-ACK codebook is illustrated according to certain embodiments when there is overlap between the configured dl-DataToUL-ACK sets for unicast and multicast;

[0024] Figure 4 An example wireless network according to certain embodiments is shown;

[0025] Figure 5 An example network node according to some embodiments is shown;

[0026] Figure 6 An example wireless device according to certain embodiments is shown;

[0027] Figure 7 An example user device according to certain embodiments is shown;

[0028] Figure 8 A virtualized environment is shown, according to some embodiments, in which functionality implemented by some embodiments can be virtualized;

[0029] Figure 9A telecommunications network connected to a host computer via an intermediate network, according to certain embodiments, is shown;

[0030] Figure 10 A general block diagram of a host computer communicating with a user equipment via a base station through a partially wireless connection, according to some embodiments, is shown.

[0031] Figures 11 to 14 The following are methods implemented in a communication system according to some embodiments;

[0032] Figure 15 Example methods performed by a wireless device according to certain embodiments are shown;

[0033] Figure 16 An example virtual device according to certain embodiments is shown;

[0034] Figure 17 Example methods performed by network nodes according to certain embodiments are shown; and

[0035] Figure 18 Another example virtual device according to certain embodiments is shown. Detailed Implementation

[0036] Some embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to the embodiments set forth herein; rather, these embodiments are provided by way of example only to convey the scope of the subject matter to those skilled in the art.

[0037] Generally, unless explicitly stated and / or implied from the context, all terms used herein shall be interpreted according to their common meaning in the relevant art. Unless otherwise expressly stated, all references to “an element, device, component, apparatus, step, etc.” shall be openly interpreted as referring to at least one instance of an element, device, component, apparatus, step, etc. Unless it must be explicitly described that a step is after or before another step and / or implicitly implied that a step must be after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0038] In some embodiments, the more general term "network node" may be used and may correspond to any type of radio network node or any network node that communicates with the UE (directly or via another node) and / or with another network node. Examples of network nodes are NodeB, MeNB, ENB, network nodes belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio nodes such as MSR BS, eNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node control relay, base transceiver station (BTS), access point (AP), transmission point, transmission node, RRU, RRH, nodes in distributed antenna system (DAS), core network nodes (e.g., MSC, MME, etc.), O&M, OSS, SON, location nodes (e.g., E-SMLC), MDT, test equipment (physical node or software), etc.

[0039] In some embodiments, the non-limiting terms User Equipment (UE) or Wireless Device may be used, and may refer to any type of wireless device that communicates with a network node in a cellular or mobile communication system and / or with another UE. Examples of UEs are target devices, device-to-device (D2D) UEs, machine-type UEs or UEs capable of machine-to-machine (M2M) communication, PDAs, PADs, tablets, mobile terminals, smartphones, LEEs (Laptop embedded devices), LMEs (Laptop installed devices), USB adapters, UE class M1, UE class M2, ProSe UEs, V2V UEs, V2X UEs, etc.

[0040] Furthermore, terms such as base station / gNodeB and UE should be considered non-restrictive and do not specifically imply any hierarchical relationship between them; generally, "gNodeB" can be considered device 1, and "UE" can be considered device 2, and the two devices communicate with each other through a radio channel. And in the following text, the sender or receiver can be either a gNB or a UE.

[0041] As mentioned above, multicast / broadcast transmission can be useful for some applications (such as NSPS, V2X, etc.). For these applications, there are QoS (Quality of Service) requirements. For example, a requirement might be a packet error rate of less than 1% with a latency budget of X ms. Therefore, NR needs to support HARQ feedback for multicast services. Otherwise, the spectral efficiency of supporting multicast services may be very low.

[0042] As mentioned above, it has been proposed to enable Hybrid Automatic Repeat Request (HARQ) feedback for multicast transmissions for NR. One issue with HARQ feedback for multicast is how to send it, particularly when HARQ feedback for unicast exists and they need to be sent within the same uplink (UL) slot.

[0043] Further suggestions have been proposed for constructing a Type 1 HARQ codebook. However, these suggestions assume that only one PUCCH configuration exists for unicast services. It has also been agreed that multicast services can have their own PUCCH configurations, including a list of TDRAs that can differ from the unicast PUCCH configuration. Therefore, it is necessary to consider methods for constructing a HARQ codebook for this more general case.

[0044] According to some embodiments, since multicast services can have their own PUCCH configuration and are configured with downlink data to UL ACK timing, the HARQ-ACK codebook should be determined by the downlink (DL) data to UL feedback timing in the multicast PUCCH configuration and the downlink data to UL feedback timing in the unicast PUCCH configuration. As an example, for DCI format 1_1 (for a description of this DCI format, see, for example, 3GPP TS 38.212 Technical Specification Group Radio Access Networks; NR; Multiplexing and Channel Coding; v16.5.0), the downlink data to UL feedback timing is dl-DataToUL-ACK in the PUCCH configuration. As another example, for DCI format 1_0, the downlink data to UL feedback timing is fixed at {1, 2, 3, 4, 5, 6, 7, 8}.

[0045] Some of the embodiments discussed in this article consider three scenarios.

[0046] First scenario

[0047] According to the first case (Case 1), there is no overlap between the downlink data in the multicast PUCCH and unicast PUCCH and the timing of the UL feedback. Figure 2 The construction of a type 1 HARQ-ACK codebook is illustrated according to certain embodiments when there is no overlap between the configured dl-DataToUL-ACK sets for unicast and multicast. Specifically, Figure 2 Use DCI format 1_1 as an example.

[0048] In this case, the codebook needs to transmit HARQ feedback for slots {n-5, n-4, n-3, n-2, n-1}. That is, the DL slots that require UL HARQ feedback are the union of the DL slots from both the unicast PUCCH configuration and the multicast PUCCH configuration.

[0049] Since there is no overlap between dl-DataToUL-ACK configurations, meaning that only unicast or multicast services exist at each DL slot, the number of HARQ feedback bits for each DL slot is determined by the corresponding TDRA set of the unicast or multicast configuration.

[0050] The second scenario

[0051] According to the second case (case 2), there is an overlap between the dl-DataToUL-ACK configurations in the multicast PUCCH and unicast PUCCH. Figure 3 The construction of a Type 1 HARQ-ACK codebook is illustrated according to certain embodiments when there is an overlap 33 between the unicast configured dl-DataToUL-ACK set 31 and the multicast configured dl-DataToUL-ACK set 30. Specifically, Figure 3 Using DCI format 11 as an example.

[0052] In this scenario, the DL slots requiring UL HARQ feedback are still the union of the DL slots from both unicast PUCCH configuration 31 and multicast PUCCH configuration 30. Because there is an overlap 33 between the dl-DataToUL-ACK configurations, both multicast and unicast require HARQ feedback at slot N-3. At this DL slot, the number of HARQ feedback bits 32 is determined by the union of the TDRA sets for unicast and multicast. Figure 3 As can be seen, unicast PUCCH configuration 31 includes value 35, which is not included in multicast PUCCH configuration 30. Similarly, multicast PUCCH configuration 30 includes value 34, which is not included in unicast PUCCH configuration 31.

[0053] The third scenario

[0054] According to the third case (Case 3), the dl-DataToUL-ACK configurations in the multicast PUCCH and unicast PUCCH are the same. In this case, the DL slots requiring UL HARQ feedback are still the union of the DL slots from both the unicast and multicast PUCCH configurations, and the number of HARQ feedback bits for each DL slot is determined by the union of the TDRA sets for unicast and multicast.

[0055] In summary, when multicast and unicast services are scheduled together in a cell and their HARQ feedbacks can be combined into a single codebook, the solution is as follows: the construction of the HARQ-ACK codebook for combined multicast and unicast services is determined by the union of two downlink data to UL ACK timing sets from the multicast configuration and unicast configuration / settings. The values ​​in the union of the downlink data to UL feedback times determine the number of DL slots associated with this codebook, while the redundancy values ​​in the intersection of these sets affect the number of HARQ feedback bits for each DL slot.

[0056] Figure 4 Wireless networks according to some embodiments are illustrated. Although the subject matter described herein can be implemented in any suitable system using any appropriate components, the embodiments disclosed herein pertain to wireless networks (e.g., Figure 4 The example wireless network shown is described. For simplicity, Figure 4 The wireless network depicted only includes network 106, network nodes 160 and 160b, and wireless devices 110, 110b, and 110c. In practice, the wireless network may also include any additional elements suitable for supporting communication between wireless devices or between a wireless device and another communication device (e.g., a landline telephone, a service provider, or any other network node or terminal device). Among the components shown, network node 160 and wireless device 110 are depicted with additional details. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate access to and / or use of services provided by or via the wireless network.

[0057] Wireless networks can include any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems, and / or interface with any type of communications, telecommunications, data, cellular and / or radio networks or other similar systems. In some embodiments, a wireless network can be configured to operate according to a specific standard or other type of predefined rules or procedures. Thus, specific embodiments of a wireless network can implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standards; Wireless Local Area Network (WLAN) standards (e.g., the IEEE 802.11 standard); and / or any other suitable wireless communication standards such as Global Microwave Access Interoperability (WiMax), Bluetooth, Z-Wave, and / or ZigBee standards.

[0058] Network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local area networks (WLAN), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[0059] Network node 160 and wireless device 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, the wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components that can facilitate or participate in communication of data and / or signals (whether via wired or wireless connections).

[0060] Figure 5An example network node 160 according to certain embodiments is shown. As used herein, a network node refers to a device capable of, configured, arranged, and / or operable to communicate directly or indirectly with wireless devices and / or with other network nodes or devices in a wireless network to implement and / or provide radio access to wireless devices and / or perform other functions (e.g., management) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points) and base stations (BSs) (e.g., radio base stations, NodeBs, evolved NodeBs (eNBs), and NR NodeBs (gNBs)). Base stations can be classified based on the coverage they provide (or in other words, based on their transmit power levels), and thus they can also be referred to as femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio headend (RRH). These remote radio units may be integrated with an antenna to form an antenna-integrated radio, or they may be independent of an antenna to form an antenna-integrated radio. A portion of a distributed radio base station may also be referred to as a node in a distributed antenna system (DAS). Other examples of network nodes include multi-standard radio (MSR) equipment (e.g., MSR BS), network controllers (e.g., Radio Network Controller (RNC) or Base Station Controller (BSC)), base transceiver stations (BTS), transmitting points, transmitting nodes, multi-cell / multicast coordination entities (MCE), core network nodes (e.g., MSC, MME), O&M nodes, OSS nodes, SON nodes, location nodes (e.g., E-SMLC), and / or MDTs. As another example, a network node may be a virtual network node, as described in more detail below. However, more generally, a network node can represent any suitable device (or group of devices) capable of, configured, arranged, and / or operable to enable and / or provide access to a wireless communication network for wireless devices, or to provide some service to wireless devices already connected to the wireless network.

[0061] exist Figure 5 In this network node 160, processing circuitry 170, device-readable medium 180, interface 190, auxiliary equipment 184, power supply 186, power supply circuitry 187, and antenna 162 are included. Although Figure 5The network node 160 shown in the example wireless network may represent a device including a combination of the hardware components shown, but other embodiments may include network nodes with different combinations of components. It should be understood that a network node includes any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. Furthermore, while the components of network node 160 are depicted as a single box within a larger box, or nested within multiple boxes, in practice, a network node may include multiple different physical components constituting a single illustrated component (e.g., device-readable medium 180 may include multiple separate hard disk drives and multiple RAM modules).

[0062] Similarly, network node 160 may consist of multiple physically separate components (e.g., Node B components and RNC components, BTS components and BSC components, etc.), each with its own respective components. In some scenarios where network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of these separate components may be shared among multiple network nodes. For example, a single RNC may control multiple NodeBs. In such scenarios, each unique NodeB and RNC pair may be considered a single, separate network node in some cases. In some embodiments, network node 160 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs), and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of various illustrated components for different wireless technologies (e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies) integrated into network node 160. These wireless technologies can be integrated into the same or different chips or chipsets and other components within network node 160.

[0063] Processing circuitry 170 is configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by processing circuitry 170 may include information obtained by processing circuitry 170 through processes such as: converting the obtained information into other information, comparing the obtained or converted information with information stored in the network node, and / or performing one or more operations based on the obtained or converted information, and making a determination based on the result of said processing.

[0064] Processor circuitry 170 may include a combination of one or more of the following: a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide network node 160 functionality, either alone or together with other network node 160 components (e.g., device-readable medium 180). For example, processing circuitry 170 may execute instructions stored in device-readable medium 180 or in memory within processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 may include a system-on-a-chip (SoC).

[0065] In some embodiments, processing circuitry 170 may include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, RF transceiver circuitry 172 and baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of RF transceiver circuitry 172 and baseband processing circuitry 174 may be on the same chip or chipset, board, or unit group.

[0066] In some embodiments, some or all of the functions described herein as being provided by a network node, base station, eNB, or other such network device may be performed by processing circuitry 170, which executes instructions stored on memory within device-readable medium 180 or processing circuitry 670. In alternative embodiments, some or all of the functions may be provided by processing circuitry 170, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable media. In any of these embodiments, processing circuitry 170 may be configured to perform the described functions regardless of whether instructions stored on device-readable storage media are executed. The benefits provided by such functions are not limited to processing circuitry 170 or other components of network node 160, but are enjoyed as a whole by network node 160 and / or generally by end users and wireless networks.

[0067] Device-readable medium 180 may include any form of volatile or non-volatile computer-readable memory, including but not limited to permanent storage devices, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drives, optical discs (CDs), or digital video discs (DVDs)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that can be used by processing circuitry 170. Device-readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions that can be executed by processing circuitry 170 and used by network node 160. Device-readable medium 180 may be used to store any calculations performed by processing circuitry 170 and / or any data received via interface 190. In some embodiments, processing circuitry 170 and device-readable medium 180 may be considered integrated.

[0068] Interface 190 is used for wired or wireless communication of signaling and / or data between network node 160, network 106, and / or wireless device 110. As shown, interface 190 includes a port / terminal 194 for sending and receiving data to and from network 106, for example, via a wired connection. Interface 190 also includes radio front-end circuitry 192, which may be coupled to antenna 162, or in some embodiments, is part of antenna 162. Radio front-end circuitry 192 includes a filter 198 and an amplifier 196. Radio front-end circuitry 192 may be connected to antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may be configured to modulate the signal communicating between antenna 162 and processing circuitry 170. Radio front-end circuitry 192 may receive digital data that will be transmitted to other network nodes or wireless devices via a wireless connection. Radio front-end circuitry 192 may use a combination of filter 198 and / or amplifier 196 to convert the digital data into a radio signal with suitable channel and bandwidth parameters. The radio signal can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 can collect radio signals, which are then converted into digital data by radio front-end circuitry 192. The digital data can then be passed to processing circuitry 170. In other embodiments, the interface may include different components and / or different combinations of components.

[0069] In some alternative embodiments, network node 160 may not include a separate radio front-end circuitry 192. Instead, processing circuitry 170 may include radio front-end circuitry and may be connected to antenna 162 without requiring a separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered part of interface 190. In other embodiments, interface 190 may include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not shown).

[0070] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector, or planar antennas operable to transmit / receive radio signals in, for example, between 2 GHz and 66 GHz. Omnidirectional antennas can be used to transmit / receive radio signals in any direction, sector antennas can be used to transmit / receive radio signals relative to a device within a specific area, and planar antennas can be line-of-sight antennas used to transmit / receive radio signals in a relatively straight line. In some cases, the use of more than one antenna may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and may be connected to network node 160 via an interface or port.

[0071] Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receive operation and / or certain acquire operation described herein as being performed by a network node. Any information, data, and / or signals can be received from a wireless device, another network node, and / or any other network device. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to a wireless device, another network node, and / or any other network device.

[0072] Power supply circuit 187 may include or be coupled to power management circuitry and is configured to provide power to the components of network node 160 for performing the functions described herein. Power supply circuit 187 may receive power from power source 186. Power source 186 and / or power supply circuit 187 may be configured to provide power to various components of network node 160 in a manner suitable for the individual components (e.g., at the voltage and current levels required by each respective component). Power source 186 may be included in or external to power supply circuit 187 and / or network node 160. For example, network node 160 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a cable, wherein the external power source supplies power to power supply circuit 187. As another example, power source 186 may include a power source in the form of a battery or battery pack, which is connected to or integrated into power supply circuit 187. The battery can provide backup power if the external power source fails. Other types of power sources, such as photovoltaic devices, may also be used.

[0073] Alternative embodiments of network node 160 may include more than Figure 5 Additional components of the illustrated components may be responsible for providing certain aspects of the functionality of the network node (including any of the functionalities described herein and / or any functionality required to support the subject matter described herein). For example, network node 160 may include a user interface device to allow information to be input into and output from network node 160. This can allow users to perform diagnostic, maintenance, repair, and other management functions on network node 160.

[0074] Figure 6Example wireless device 110 is shown. According to certain embodiments. As used herein, a wireless device means a device capable of, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Unless otherwise shown, the term wireless device may be used interchangeably with user equipment (UE) herein. Wireless communication may include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information through the air. In some embodiments, a wireless device may be configured to transmit and / or receive information without direct human interaction. For example, a wireless device may be designed to transmit information to the network according to a predetermined schedule, when triggered by internal or external events, or in response to a request from the network. Examples of wireless devices include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptop computers, laptop embedded devices (LEEs), laptop-mounted devices (LMEs), smart devices, wireless client devices (CPEs), and in-vehicle wireless terminal devices. Wireless devices can, for example, support device-to-device (D2D) communication, vehicle-to-vehicle (V2V) communication, vehicle-to-infrastructure (V2I) communication, and vehicle-to-anything (V2X) communication by implementing 3GPP standards for sidelink communication, and in this case, can be referred to as D2D communication devices. As yet another specific example, in the Internet of Things (IoT) scenario, a wireless device can refer to a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another wireless device and / or network node. In this context, the wireless device can be a machine-to-machine (M2M) device, which can be referred to as an MTC device in the 3GPP context. As a specific example, the wireless device can be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Specific examples of such machines or devices are sensors, metering devices (e.g., power meters), industrial machines, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearable devices (e.g., watches, fitness trackers, etc.). In other scenarios, the wireless device can represent a vehicle or other device capable of monitoring and / or reporting its operational status or other functions associated with its operation. The wireless device described above can represent an endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, the wireless device described above can be mobile, in which case it can also be referred to as a mobile device or mobile terminal.

[0075] As shown in the figure, wireless device 110 includes an antenna 111, an interface 114, processing circuitry 120, a device-readable medium 130, a user interface device 132, auxiliary devices 134, a power supply 136, and a power circuit 137. Wireless device 110 may include one or more of the components shown for various wireless technologies supported by wireless device 110 (e.g., GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, to name just a few). These wireless technologies may be integrated into a chip or chipset that is the same as or different from other components within wireless device 110.

[0076] Antenna 111 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals and connected to interface 114. In some alternative embodiments, antenna 111 may be separate from wireless device 110 and may be connected to wireless device 110 via an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receive or transmit operations described herein as performed by a wireless device. Any information, data, and / or signals may be received from a network node and / or another wireless device. In some embodiments, radio front-end circuitry and / or antenna 111 may be considered as an interface.

[0077] As shown, interface 114 includes radio front-end circuitry 112 and antenna 111. Radio front-end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front-end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to modulate the signal communicating between antenna 111 and processing circuitry 120. Radio front-end circuitry 112 may be coupled to antenna 111 or a portion thereof. In some embodiments, wireless device 110 may not include a separate radio front-end circuitry 112; instead, processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 may be considered part of interface 114. Radio front-end circuitry 112 can receive digital data that will be transmitted wirelessly to other network nodes or wireless devices. Radio front-end circuitry 112 may use a combination of filters 118 and / or amplifiers 116 to convert the digital data into radio signals with suitable channel and bandwidth parameters. The radio signals can then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 can collect radio signals, which are then converted into digital data by radio front-end circuitry 112. The digital data can then be passed to processing circuitry 120. In other embodiments, the interface may include different components and / or different combinations of components.

[0078] Processor circuitry 120 may include a combination of one or more of the following: a microprocessor, controller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coding logic, operable to provide wireless device 110 functionality, either alone or together with other wireless device 110 components (e.g., device-readable medium 130). Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored in device-readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

[0079] As shown in the figure, the processing circuit 120 includes one or more of an RF transceiver circuit 122, a baseband processing circuit 124, and an application processing circuit 126. In other embodiments, the processing circuit may include different components and / or different combinations of components. In some embodiments, the processing circuit 120 of the wireless device 110 may include a System-on-a-Chip (SOC). In some embodiments, the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be on a separate chip or chipset. In an alternative embodiment, some or all of the baseband processing circuit 124 and the application processing circuit 126 may be combined into a single chip or chipset, and the RF transceiver circuit 122 may be on a separate chip or chipset. In another alternative embodiment, some or all of the RF transceiver circuit 122 and the baseband processing circuit 124 may be on the same chip or chipset, and the application processing circuit 126 may be on a separate chip or chipset. In yet another alternative embodiment, some or all of the RF transceiver circuit 122, the baseband processing circuit 124, and the application processing circuit 126 may be combined in the same chip or chipset. In some embodiments, the RF transceiver circuit 122 may be part of the interface 114. The RF transceiver circuit 122 may regulate the RF signals used for processing circuit 120.

[0080] In some embodiments, some or all of the functions described herein as being performed by a wireless device may be provided by processing circuitry 120 that executes instructions stored on a device-readable medium 130, which may be a computer-readable storage medium. In alternative embodiments, some or all of the functions may be provided by processing circuitry 120, for example, in a hard-wired manner, without executing instructions stored on separate or discrete device-readable storage media. In any of these particular embodiments, processing circuitry 120 may be configured to perform the described functions regardless of whether instructions stored on a device-readable storage medium are executed. The benefits provided by such functions are not limited to processing circuitry 120 or other components of wireless device 110, but are enjoyed as a whole by wireless device 110 and / or generally by end users and wireless networks.

[0081] Processing circuitry 120 may be configured to perform any determination, calculation, or similar operation (e.g., certain acquisition operations) described herein as being performed by a wireless device. These operations performed by processing circuitry 120 may include information acquired by processing circuitry 120 through processes such as: converting the acquired information into other information, comparing the acquired or converted information with information stored by wireless device 110, and / or performing one or more operations based on the acquired or converted information, and making a determination based on the result of said processing.

[0082] Device-readable medium 130 is operable to store computer programs, software, applications including one or more of logic, rules, code, tables, etc., and / or other instructions executable by processing circuitry 120. Device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., CD or DVD), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions usable by processing circuitry 120. In some embodiments, processing circuitry 120 and device-readable medium 130 may be considered integrated.

[0083] User interface device 132 can provide components that allow a human user to interact with wireless device 110. This interaction can take many forms, such as visual, auditory, tactile, etc. User interface device 132 is operatively capable of producing output to the user and allowing the user to provide input to wireless device 110. The type of interaction can vary depending on the type of user interface device 132 installed in wireless device 110. For example, if wireless device 110 is a smartphone, interaction can be performed via a touchscreen; if wireless device 110 is a smart meter, interaction can be performed via a screen providing a purpose (e.g., the number of gallons used) or a speaker providing an audible alarm (e.g., if smoke is detected). User interface device 132 can include input interfaces, devices, and circuitry, as well as output interfaces, devices, and circuitry. User interface device 132 is configured to allow information to be input into wireless device 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface device 132 can include, for example, a microphone, proximity or other sensors, buttons / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface device 132 is also configured to allow information output from wireless device 110 and to allow processing circuitry 120 to output information from wireless device 110. User interface device 132 may include, for example, a speaker, display, vibration circuitry, USB port, headphone jack, or other output circuitry. By using one or more input and output interfaces, devices, and circuitry of user interface device 132, wireless device 110 can communicate with end users and / or wireless networks and allow them to benefit from the functionality described herein.

[0084] The auxiliary device 134 is operable to provide more specific functions that may not typically be performed by a wireless device. This may include dedicated sensors for measuring for various purposes, interfaces for additional types of communication such as wired communication, etc. The components and types included in the auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0085] In some embodiments, power source 136 may be in the form of a battery or battery pack. Other types of power sources may also be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery cell. Wireless device 110 may also include power circuitry 137 for supplying power from power source 136 to various parts of wireless device 110 that require power from power source 136 to perform any functions described or indicated herein. In some embodiments, power circuitry 137 may include power management circuitry. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; in this case, wireless device 110 may be connected to an external power source (e.g., a power outlet) via input circuitry or an interface such as a power cable. In some embodiments, power circuitry 137 may also be operable to supply power from an external power source to power source 136. For example, this may be used for charging power source 136. Power circuitry 137 may perform any formatting, conversion, or other modifications on the power from power source 136 to suit the power for the various components of wireless device 110 to which it powers.

[0086] Figure 7 An embodiment of a UE according to the various aspects described herein is illustrated. As used herein, a “User Equipment” or “UE” need not necessarily be a “user” in the sense of a human user who owns and / or operates the associated equipment. Alternatively, a UE may refer to a device intended to be sold to or operated by a human user but which may not or initially may not be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, a UE may refer to a device not intended to be sold to or operated by an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 200 can be any UE identified by the 3rd Generation Partnership Project (3GPP), including NB-IoT UEs, Machine Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs. Figure 7 As shown, UE 200 is an example of a radio device configured for communication according to one or more communication standards (e.g., 3GPP's GSM, UMTS, LTE, and / or 5G standards) published by the 3rd Generation Partnership Project (3GPP). As previously stated, the terms radio device and UE are used interchangeably. Therefore, although... Figure 7 This is for UEs, but the components discussed in this article also apply to wireless devices, and vice versa.

[0087] exist Figure 7In this embodiment, UE 200 includes processing circuitry 201 operatively coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network interface 211, a memory 215 including random access memory (RAM) 217, read-only memory (ROM) 219, and storage medium 221, a communication subsystem 231, a power supply 213, and / or any other component, or any combination thereof. Storage medium 221 includes an operating system 223, applications 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may use... Figure 7 All components may be shown, or only a subset of components may be used. The level of integration between components can vary from one UE to another. Furthermore, some UEs may contain multiple instances of components, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0088] exist Figure 7 In this embodiment, processing circuitry 201 can be configured to process computer instructions and data. Processor 201 can be configured to execute any sequential state machine containing machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic and suitable firmware; one or more stored programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and suitable software; or any combination thereof. For example, processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[0089] In the depicted embodiments, the input / output interface 205 can be configured to provide a communication interface to an input device, an output device, or both input and output devices. The UE 200 can be configured to use an output device via the input / output interface 205. The output device can use an interface port of the same type as the input device. For example, a USB port can be used to provide input to and output from the UE 200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smart card, another output device, or any combination thereof. The UE 200 can be configured to use an input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital camcorder, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional keyboard, a touchpad, a scroll wheel, a smart card, etc. A presence-sensitive display can include a capacitive or resistive touch sensor to sense input from the user. Sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, other types of sensors, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and optical sensors.

[0090] exist Figure 7 In this configuration, RF interface 209 can be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network interface 211 can be configured to provide a communication interface to network 243a. Network 243a may include wired and / or wireless networks, such as local area networks (LANs), wide area networks (WANs), computer networks, wireless networks, telecommunications networks, another similar network, or any combination thereof. For example, network 243a may include a Wi-Fi network. Network interface 211 can be configured to include receiver and transmitter interfaces for communicating with one or more other devices over the communication network according to one or more communication protocols (e.g., Ethernet, TCP / IP, SONET, ATM, etc.). Network interface 211 can implement receiver and transmitter functions suitable for the communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components or software, or alternatively, may be implemented separately.

[0091] RAM 217 can be configured to interface with processing circuitry 201 via bus 202 to provide storage or cache of data or computer instructions during the execution of software programs such as operating systems, applications, and device drivers. ROM 219 can be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O), startup, or reception of keystrokes from a keyboard, stored in non-volatile memory. Storage medium 221 can be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), disk, optical disk, floppy disk, hard disk, removable magnetic tape, or flash drive. In this example, storage medium 221 can be configured to include operating system 223, application 225 such as a web browser application, widget or utility engine or another application, and data file 227. Storage medium 221 can store any one or a combination of various operating systems for use by UE 200.

[0092] Storage medium 221 can be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile optical disc (HD-DVD) drive, an internal hard disk drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM / MSDRAM, smart card memory such as a user identification module or a removable user identifier (SIM / RUIM) module, other memory, or any combination thereof. Storage medium 221 can allow UE 200 to access computer-executable instructions, applications, etc., stored on a transient or non-transient storage medium to offload or upload data. Articles such as those utilizing a communication system can be tangibly embodied in storage medium 221, which can include a device-readable medium.

[0093] exist Figure 7In this configuration, processing circuitry 201 can be configured to communicate with network 243b using communication subsystem 231. Networks 243a and 243b can be one or more of the same networks or one or more different networks. Communication subsystem 231 can be configured to include one or more transceivers for communicating with network 243b. For example, communication subsystem 231 can be configured to include one or more remote transceivers for communicating with another device (e.g., another wireless device, UE) or a base station of a radio access network (RAN) capable of wireless communication according to one or more communication protocols (e.g., IEEE 802.QQ2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc.). Each transceiver can include transmitter 233 and / or receiver 235 to implement transmitter or receiver functions suitable for the RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 233 and receiver 235 of each transceiver can share circuit components, software, or firmware, or they can be implemented separately.

[0094] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication (such as the use of a Global Positioning System (GPS) for determining location), another type of communication function, or any combination thereof. For example, the communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. The network 243b may include wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0095] The features, benefits, and / or functions described herein may be implemented in one of the components of UE 200 or divided among multiple components of UE 200. Furthermore, the features, benefits, and / or functions described herein may be implemented in any combination of hardware, software, or firmware. In one example, communication subsystem 231 may be configured to include any of the components described herein. Additionally, processing circuitry 201 may be configured to communicate with any such component via bus 202. In another example, any such component may be represented by program instructions stored in memory, which, when executed by processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any such component may be divided between processing circuitry 201 and communication subsystem 231. In yet another example, the non-computationally intensive functions of any such component may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0096] Figure 8 This is a schematic block diagram illustrating a virtualized environment 300, in which functionality implemented by some embodiments can be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device that may include a virtualized hardware platform, storage devices, and network resources. As used herein, virtualization can be applied to nodes (e.g., virtualized base stations or virtualized radio access nodes) or devices (e.g., UEs, wireless devices, or any other type of communication device) or components thereof, and relates to an implementation in which at least a portion of functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0097] In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted on one or more hardware nodes 330. Furthermore, in embodiments where the virtual node is not a radio access node or does not require a radio connection (e.g., a core network node), the network node may then be fully virtualized.

[0098] These functionalities can be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual devices, network functions, virtual nodes, virtual network functions, etc.), which are operable to implement some of the features, functions, and / or benefits of some embodiments disclosed herein. Applications 320 run in a virtualization environment 300, which provides hardware 330 including processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by the processing circuitry 360, thereby enabling application 320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0099] The virtualization environment 300 includes general-purpose or special-purpose network hardware devices 330, which include one or more processors or processing circuitry 360, which may be commercial off-the-shelf (COTS) processors, application-specific integrated circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special-purpose processors. Each hardware device may include memory 390-1, which may be non-permanent memory for temporarily storing instructions 395 or software executed by the processing circuitry 360. Each hardware device may include one or more network interface controllers (NICs) 370 (also referred to as network interface cards), which include physical network interfaces 380. Each hardware device may also include a non-transitory, permanent machine-readable storage medium 390-2 in which the software 395 and / or instructions executable by the processing circuitry 360 are stored. The software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software for executing virtual machines 340, and software that allows them to perform the functions, features, and / or benefits described in relation to some embodiments described herein.

[0100] Virtual machine 340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of instances of virtual device 320 can be implemented on one or more of virtual machines 340, and this implementation can be done in different ways.

[0101] During operation, the processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 350 can present a virtual operating platform that appears as networked hardware of the virtual machine 340.

[0102] like Figure 8 As shown, hardware 330 can be a standalone network node with general or specific components. Hardware 330 may include antenna 3225 and may implement some functions via virtualization. Alternatively, hardware 330 may be part of a larger hardware cluster (e.g., in a data center or customer premises equipment (CPE)) where many hardware nodes work together and are managed by management and coordination (MANO) 3100, which in particular oversees the lifecycle management of application 320.

[0103] In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to unify numerous network device types onto industry-standard high-capacity server hardware, physical switches, and physical storage that can reside in data centers and customer premises equipment (CPE).

[0104] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine, and its running programs are executed as if they were on a physical, non-virtualized machine. Each of virtual machines 340 and the portion of hardware 330 that executes that virtual machine (whether it is hardware dedicated to that virtual machine and / or hardware shared by that virtual machine and other virtual machines in virtual machine 340) form a separate virtual network element (VNE).

[0105] Still within the context of NFV, Virtual Network Functions (VNFs) are responsible for handling one or more virtual machines 340 running on top of the hardware network infrastructure 330 and corresponding to... Figure 8 The application 320 has specific network functions.

[0106] In some embodiments, each of the one or more radio units 3200, including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio unit 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and may be used in conjunction with virtual components to provide radio capabilities to the virtual node, such as a radio access node or base station.

[0107] In some embodiments, the control system 3230 may be used to implement some signaling, and the control system 3230 may alternatively be used for communication between the hardware node 330 and the radio unit 3200.

[0108] Figure 9 A telecommunications network connected to a host computer via an intermediate network is shown according to some embodiments.

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

[0110] Telecommunications network 410 is connected to host computer 430, 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 430 may be owned by or under the control of a service provider, or may be operated by or on behalf of a service provider. Connections 421 and 422 between telecommunications network 410 and host computer 430 may extend directly from core network 414 to host computer 430, or may pass through optional intermediate network 420. Intermediate network 420 may be one or more of public, private, or hosted networks; intermediate network 420 (if any) may be a backbone network or the Internet; specifically, intermediate network 420 may include two or more subnetworks (not shown).

[0111] Figure 9 The communication system as a whole enables connectivity between connected UEs 491 and 492 and host computer 430. This connection can be described as an over-the-top (OTT) connection 450. Host computer 430 and connected UEs 491 and 492 are configured to transmit data and / or signaling via OTT connection 450 using access network 411, core network 414, any intermediate network 420, and possibly other intermediate infrastructure (not shown). The participating communication devices through which OTT connection 450 passes are unaware of the routes of uplink and downlink communications; in this sense, OTT connection 450 can be transparent. For example, base station 412 may not be informed or need not be informed of the past routes of incoming downlink communications containing data originating from host computer 430 and to be forwarded (e.g., handed over) to connected UE 491. Similarly, base station 412 does not need to know the future routes of uplink communications originating from UE 491 and outputting toward host computer 430.

[0112] Figure 10 A host computer is shown that communicates with a user equipment via a base station through a partially wireless connection, according to some embodiments.

[0113] Now refer to Figure 10The preceding paragraphs describe example implementations of the UE, base station, and host computer according to embodiments discussed in the preceding paragraphs. In the communication system 500, the host computer 510 includes hardware 515 including a communication interface 516 configured to establish and maintain wired or wireless connections with interfaces of different communication devices of the communication system 500. The host computer 510 also includes processing circuitry 518, which may have storage and / or processing capabilities. Specifically, the processing circuitry 518 may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) suitable for executing instructions. The host computer 510 also includes software 511 stored in or accessible by the host computer 510 and executable by the processing circuitry 518. The software 511 includes a host application 512. The host application 512 can be operated to provide services to a remote user, such as a UE 530 connected via an OTT connection 550 terminating between the UE 530 and the host computer 510. When providing services to remote users, host application 512 can provide user data sent using OTT connection 550.

[0114] The communication system 500 also includes a base station 520 installed in the telecommunications system, which includes hardware 525 enabling it to communicate with the host computer 510 and the UE 530. Hardware 525 may include: a communication interface 526 for establishing and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 500; and a radio interface 527 for establishing and maintaining connections with the coverage area served by the base station 520 (in...). Figure 10 At least one wireless connection 570 of UE 530 (not shown in the diagram). Communication interface 526 can be configured to facilitate connection 560 to host computer 510. Connection 560 can be a direct connection, or alternatively, connection 560 can be via the core network of a telecommunications network (in the diagram). Figure 10 (Not shown in the diagram) and / or via one or more intermediate networks outside the telecommunications network. In the illustrated embodiment, the hardware 525 of the base station 520 also includes processing circuitry 528, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 520 also has software 521 stored internally or accessible via an external connection.

[0115] The communication system 500 also includes the previously mentioned UE 530. The hardware 535 of the UE 530 may include a radio interface 537 configured to establish and maintain a wireless connection 570 with a base station serving the coverage area currently occupied by the UE 530. The hardware 535 of the UE 530 also includes processing circuitry 538, which may include one or more programmable processors, application-specific integrated circuits, field-programmable gate arrays, or combinations of such devices (not shown) suitable for executing instructions. The UE 530 also includes software 531, which is stored in or accessible to the UE 530 and can be executed by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 can be operated to provide services to human or non-human users via the UE 530 with the support of the host computer 510. In the host computer 510, a host application 512 executing can communicate with the client application 532 via an OTT connection 550 terminating between the UE 530 and the host computer 510. When providing services to a user, client application 532 can receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 can transmit both request data and user data. Client application 532 can interact with the user to generate the user data it provides.

[0116] It should be noted that Figure 10 The host computer 510, base station 520, and UE 530 shown can be respectively connected to Figure 9 The host computer 430, one of the base stations 412a, 412b, and 412c, and one of the UEs 491 and 492 are similar to or equivalent to each other. That is to say, the internal workings of these entities can be as follows: Figure 10 As shown, and independently, the surrounding network topology can be Figure 9 The network topology.

[0117] exist Figure 10 The OTT connection 550 has been abstractly depicted to illustrate communication between host computer 510 and UE 530 via base station 520, but no intermediate devices or the exact routing messages via these devices are explicitly mentioned. The network infrastructure can determine the route, which can be configured to be hidden from the service provider operating host computer 510 or both. While OTT connection 550 is active, the network infrastructure can further make decisions to dynamically change the route (e.g., based on load balancing considerations or network reconfiguration).

[0118] The wireless connection 570 between UE 530 and base station 520 is consistent with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT services provided to UE 530 using OTT connection 550, in which wireless connection 570 forms the final part. More specifically, the teachings of these embodiments can improve data rates, latency, and / or power consumption, and thus provide benefits such as reduced user wait times, relaxed file size limits, better responsiveness, and / or extended battery life.

[0119] Measurement procedures may be provided for monitoring data rates, latency, and other factors that are the subject of improvements in one or more embodiments. Optional network functions may also be present for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to changes in measurement results. The measurement procedures and / or network functions for reconfiguring the OTT connection 550 may be implemented in the software 511 and hardware 515 of the host computer 510, or in the software 531 and hardware 535 of the UE 530, or both. In embodiments, sensors (not shown) may be deployed in or associated with communication devices traversed by the OTT connection 550; the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities illustrated above, or by providing values ​​of other physical quantities from which the software 511, 531 can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not need to affect the base station 520 and may be unknown or imperceptible to the base station 520. Such 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 510 in measuring throughput, propagation time, latency, etc. The measurement can be achieved by software 511 and 531 using OTT connection 550 to send messages (particularly empty messages or "virtual" messages) while simultaneously monitoring propagation time, errors, etc.

[0120] Figure 11 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 11References. In step 610, the host computer provides user data. In sub-step 611 of step 610 (which may be optional), the host computer provides user data by executing a host application. In step 620, the host computer initiates a transmission to the UE carrying user data. In step 630 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station sends the user data carried in the host computer-initiated transmission to the UE. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0121] Figure 12 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 12 References. In step 710 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 720, the host computer initiates a transmission to the UE carrying user data. According to the teachings of the embodiments described throughout this disclosure, the transmission can be carried out via a base station. In step 730 (which may be optional), the UE receives the user data carried in the transmission.

[0122] Figure 13 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 9 and Figure 1 The host computers, base stations, and UEs described in section 0. For the sake of simplicity, this section includes only those related to... Figure 13References. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 of step 820 (which may be optional), the UE provides user data by executing a client application. In sub-step 811 of step 810 (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, in sub-step 830 (which may be optional), the UE initiates the transmission of user data to the host computer. In step 840 of the method, the host computer receives user data sent from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0123] Figure 14 This is a flowchart illustrating a method implemented in a communication system according to one embodiment. The communication system includes: a host computer, a base station, and a UE, which may be referenced... Figure 9 and Figure 10 The host computers, base stations, and UEs described herein. For the sake of simplicity, this section includes only descriptions of... Figure 14 References. In step 910 (which may be optional), the base station receives user data from the UE in accordance with the teachings throughout the embodiments described in this disclosure. In step 920 (which may be optional), the base station initiates a transmission of the received user data to the host computer. In a third step 930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

[0124] Figure 15 A method 1500 performed by a wireless device according to certain embodiments is described. At step 1502, the wireless device obtains a codebook constructed based on multicast and unicast configurations. At step 1504, based on this codebook, the wireless device sends feedback to network nodes regarding multicast transmissions and unicast data.

[0125] In a particular embodiment, the multicast configuration includes a first downlink data to uplink feedback timing set, and the unicast configuration includes a second downlink data to uplink feedback timing set.

[0126] In a particular embodiment, the first downlink-to-uplink feedback timing set includes a first TDRA list indicating the allocation of symbols for the downlink shared channel used for multicast transmission, and the second downlink-to-uplink feedback timing set includes a second TDRA list indicating the allocation of symbols for the downlink shared channel used for unicast data.

[0127] In a particular embodiment, the codebook is constructed based on the union of the first downlink data to the uplink feedback timing set and the second downlink data to the uplink feedback timing set.

[0128] In a particular embodiment, the number of downlink time slots associated with the codebook is determined based on at least one value from the union of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0129] In a particular embodiment, the number of feedback bits for each downlink time slot is affected by the number of redundant values ​​in the intersection of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0130] In a particular embodiment, the intersection includes at least one time slot sequence that overlaps within the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0131] In a particular embodiment, the number of downlink slots associated with the codebook is determined based on the number of values ​​in the union set.

[0132] In a particular embodiment, the union includes multicast and unicast configurations that do not overlap, and in the codebook, the number of feedback bits for each downlink time slot is determined by a first downlink data to uplink feedback timing set and a second downlink data to uplink feedback timing set.

[0133] In a specific embodiment, when only unicast or multicast services exist at each downlink time slot, there is no overlap between multicast and unicast configurations.

[0134] In a particular embodiment, the union includes the overlap between multicast and unicast configurations, and in the codebook, the number of feedback bits for each downlink slot is determined by the intersection of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0135] In a particular embodiment, when both unicast and multicast services exist at each downlink time slot, there is an overlap between the multicast configuration and the unicast configuration.

[0136] In a particular embodiment, the number of bits used for feedback for each downlink time slot is determined based on at least one value from the intersection of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0137] In certain embodiments, the multicast configuration includes the Physical Uplink Control Channel (PUCCH) configuration.

[0138] In a particular embodiment, the unicast configuration includes the Physical Uplink Control Channel (PUCCH) configuration.

[0139] In a particular embodiment, obtaining the codebook includes constructing the codebook.

[0140] In a particular embodiment, obtaining the codebook includes receiving the codebook from a network node.

[0141] In a particular embodiment, the wireless device receives at least one message from a network node, the at least one message including a multicast configuration and a unicast configuration.

[0142] In a particular embodiment, the wireless device includes a UE.

[0143] In various specific embodiments, the method may additionally or alternatively include one or more steps or features of the example embodiments in Group C below.

[0144] Figure 16 A wireless network (e.g.) is shown. Figure 4 The diagram shows a schematic block diagram of a virtual device 1600 in a wireless network. This device can be used in wireless devices or network nodes (e.g., Figure 4 This is implemented in the wireless device 110 or network node 160 shown. The device 1600 is operable to perform the reference... Figure 15 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 15 The method need not be performed solely by device 1600. At least some operations of the method may be performed by one or more other entities.

[0145] The virtual device 1600 may include processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage devices, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause the acquisition module 1610, the transmission module 1620, and any other suitable unit of the device 1600 to perform the corresponding functions described in one or more embodiments of this disclosure.

[0146] According to some embodiments, the acquisition module 1610 may perform certain acquisition functions of the device 1600. For example, the acquisition module 1610 may acquire a codebook constructed based on multicast and unicast configurations.

[0147] According to some embodiments, the sending module 1620 may perform certain sending functions of the device 1600. For example, the sending module 1620 may send feedback to network nodes regarding multicast and unicast data based on the codebook.

[0148] Optionally, in a particular embodiment, the virtual device may additionally include one or more modules for performing any steps in the example embodiments of Group C below or for providing any features in the example embodiments of Group C.

[0149] As used herein, the term module or unit may have a conventional meaning in the field of electronic, electrical and / or electronic equipment, and may include, for example, electrical and / or electronic circuits, devices, modules, processors, memories, logic solid-state and / or discrete devices, computer programs or instructions for performing various tasks, processes, calculations, outputs and / or display functions, such as those described herein.

[0150] Figure 17 A method performed by a network node according to certain embodiments is described. At step 1702, the network node obtains a codebook constructed based on multicast and unicast configurations. At step 1704, based on this codebook, the network node receives feedback from the wireless device regarding multicast transmissions and unicast data.

[0151] In a particular embodiment, the multicast configuration includes a first downlink data to uplink feedback timing set, and the unicast configuration includes a second downlink data to uplink feedback timing set.

[0152] In a particular embodiment, the first downlink-to-uplink feedback timing set includes a first TDRA list indicating the allocation of symbols for the downlink shared channel used for multicast transmission, and the second downlink-to-uplink feedback timing set includes a second TDRA list indicating the allocation of symbols for the downlink shared channel used for unicast data.

[0153] In a particular embodiment, the codebook is constructed based on the union of the first downlink data to the uplink feedback timing set and the second downlink data to the uplink feedback timing set.

[0154] In a particular embodiment, the number of downlink time slots associated with the codebook is determined based on at least one value from the union of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0155] In a particular embodiment, the number of feedback bits for each downlink time slot is affected by the number of redundant values ​​in the intersection of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0156] In a particular embodiment, the intersection includes at least one time slot sequence that overlaps within the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0157] In a particular embodiment, the number of downlink slots associated with the codebook is determined based on the number of values ​​in the union set.

[0158] In a particular embodiment, the union includes multicast and unicast configurations that do not overlap, and in the codebook, the number of feedback bits for each downlink time slot is determined by a first downlink data to uplink feedback timing set and a second downlink data to uplink feedback timing set.

[0159] In a specific embodiment, when only unicast or multicast services exist at each downlink time slot, there is no overlap between multicast and unicast configurations.

[0160] In a particular embodiment, the union includes the overlap between multicast and unicast configurations, and in the codebook, the number of feedback bits for each downlink slot is determined by the intersection of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0161] In a particular embodiment, when both unicast and multicast services exist at each downlink time slot, there is an overlap between the multicast configuration and the unicast configuration.

[0162] In a particular embodiment, the number of bits used for feedback for each downlink time slot is determined based on at least one value from the intersection of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set.

[0163] In a particular embodiment, the multicast configuration includes the PUCCH configuration.

[0164] In a particular embodiment, the unicast configuration includes the PUCCH configuration.

[0165] In a particular embodiment, obtaining the codebook includes constructing the codebook.

[0166] In a particular embodiment, the network node sends a codebook to the wireless device.

[0167] In a particular embodiment, a network node sends at least one message to a wireless device. This at least one message includes multicast configuration and unicast configuration.

[0168] In a particular embodiment, the wireless device includes a UE.

[0169] In a particular embodiment, the network node includes a gNB.

[0170] In various specific embodiments, the method may include one or more of any steps or features of the example embodiments in Group C below.

[0171] Figure 18 A wireless network (e.g.) is shown. Figure 4 The diagram shows a schematic block diagram of a virtual device 1800 in a wireless network. This device can be used in wireless devices or network nodes (e.g., Figure 4 This is implemented in the wireless device 110 or network node 160 shown. The device 1800 is operable to perform the reference... Figure 17 The example methods described herein, as well as any other possible processes or methods disclosed herein. It should also be understood that... Figure 17 The method need not be performed solely by device 1800. At least some operations of the method may be performed by one or more other entities.

[0172] The virtual device 1800 may include processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware, including digital signal processors (DSPs), application-specific digital logic, etc. The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory, optical storage devices, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more techniques described herein. In some implementations, the processing circuitry may be used to cause the acquisition module 1810, the receiving module 1820, and any other suitable unit of the device 1800 to perform corresponding functions according to one or more embodiments of this disclosure.

[0173] According to some embodiments, the obtaining module 1810 may perform certain obtaining functions of the device 1800. For example, the obtaining module 1810 may obtain a codebook constructed based on multicast and unicast configurations.

[0174] According to some embodiments, the receiving module 1820 may perform certain receiving functions of the device 1800. For example, the receiving module 1820 may receive feedback from the wireless device for multicast transmissions and unicast data based on the codebook.

[0175] Optionally, in a particular embodiment, the virtual device may additionally include one or more modules for performing any steps in the example embodiments of Group C below or for providing any features in the example embodiments of Group C.

[0176] Example Implementation

[0177] Group A Example Implementation

[0178] Example Implementation A1. A wireless device (110) including processing circuitry (120), the processing circuitry (120) being configured to perform... Figure 15 Method 1500 or any of the above embodiments thereof.

[0179] Example Implementation A2. A computer program including instructions that, when executed on a computer, perform... Figure 15 Method 1500 or any of the above embodiments thereof.

[0180] Example Implementation A3. A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform... Figure 15 Method 1500 or any of the above embodiments thereof.

[0181] Example Implementation A4. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform... Figure 15 Method 1500 or any of the embodiments described above.

[0182] Group B Example Implementation

[0183] Example Implementation B1. A network node (160) including processing circuitry (170) configured to perform... Figure 17 Method 1700 or any of the above embodiments thereof.

[0184] Example Implementation B2. A computer program including instructions that, when executed on a computer, perform... Figure 17 Method 1700 or any of the above embodiments thereof.

[0185] Example Implementation B3. A computer program product including a computer program, the computer program including instructions that, when executed on a computer, perform... Figure 17 Method 1700 or any of the above embodiments thereof.

[0186] Example Implementation B4. A non-transitory computer-readable medium storing instructions that, when executed by a computer, perform... Figure 17 Method 1700 or any of the embodiments described above.

[0187] Group C Example Implementation

[0188] Example Implementation C1. A wireless device, comprising:

[0189] The processing circuit is configured to execute Figure 15 Any step of method 1500 or any embodiment thereof described above; and

[0190] The power supply circuit is configured to supply power to the wireless device.

[0191] Example Implementation C2. A network node, comprising:

[0192] The processing circuit is configured to execute Figure 17 Any step of method 1700 or any embodiment thereof described above; and

[0193] The power supply circuit is configured to supply power to the wireless device.

[0194] Example Implementation C3. A wireless device comprising:

[0195] The antenna is configured to transmit and receive wireless signals;

[0196] A radio front-end circuit, connected to the antenna and processing circuitry and configured to modulate the signal transmitted between the antenna and the processing circuitry;

[0197] The processing circuit is configured to execute Figure 15 Any step of method 1500 or any embodiment thereof as described above;

[0198] An input interface, connected to the processing circuitry and configured to allow information to be input into the wireless device for processing by the processing circuitry;

[0199] The output interface is connected to the processing circuitry and configured to output information already processed by the processing circuitry from the wireless device; and

[0200] The battery is connected to the processing circuitry and configured to power wireless devices.

[0201] Example Implementation C4. A communication system including a host computer, the host computer comprising:

[0202] Processing circuitry is configured to provide user data; and

[0203] The communication interface is configured to forward user data to the cellular network for transmission to wireless devices.

[0204] The cellular network includes network nodes with radio interfaces and processing circuitry, the processing circuitry of which is configured to perform... Figure 17 Any step of method 1700 or any embodiment of the above embodiments thereof.

[0205] Example embodiment C5. The communication system according to the foregoing embodiments further includes a network node.

[0206] Example C6. The communication system according to the foregoing two embodiments further includes a wireless device, wherein the wireless device is configured to communicate with a network node.

[0207] Example Implementation C7. The communication system according to the foregoing three embodiments, wherein:

[0208] The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0209] The wireless device includes processing circuitry configured to execute client applications associated with a host application.

[0210] Example Implementation C8. A method implemented in a communication system including a host computer, a network node, and a wireless device, the method comprising:

[0211] At the host computer, user data is provided; and

[0212] At the host computer, a transmission is initiated to the wireless device via a cellular network including network nodes. This transmission carries user data, wherein the network node performs... Figure 17 Any step of method 1700 or any embodiment of the above embodiments thereof.

[0213] Example Implementation C9. The method according to the foregoing embodiments further includes: sending user data at a network node.

[0214] Example Implementation C10. The method according to the foregoing two embodiments, wherein user data is provided at a host computer by executing a host application, the method further includes: executing a client application associated with the host application at a wireless device.

[0215] Example Implementation C11. A wireless device configured to communicate with a network node, the wireless device including a radio interface and processing circuitry configured to perform the steps described in the foregoing three embodiments.

[0216] Example Implementation C12. A communication system including a host computer, the host computer comprising:

[0217] Processing circuitry is configured to provide user data; and

[0218] The communication interface is configured to forward user data to the cellular network for transmission to wireless devices.

[0219] The wireless device includes a radio interface and processing circuitry, and its components are configured to perform... Figure 15 Any step of method 1500 or any embodiment in the above embodiments.

[0220] Example embodiment C13. The communication system according to the foregoing embodiments, wherein the cellular network further includes network nodes configured to communicate with wireless devices.

[0221] Example Implementation C14. The communication system according to the foregoing two embodiments, wherein:

[0222] The host computer's processing circuitry is configured to execute host applications, thereby providing user data; and

[0223] The processing circuitry of the wireless device is configured to execute client applications associated with the host application.

[0224] Example Implementation C15. A method implemented in a communication system including a host computer, a network node, and a wireless device, the method comprising:

[0225] At the host computer, user data is provided; and

[0226] At the host computer, a transmission is initiated to the wireless device via a cellular network including network nodes. This transmission carries user data, wherein the wireless device performs... Figure 15 Any step of method 1500 or any embodiment of the above embodiments thereof.

[0227] Example embodiment C16. The method according to the foregoing embodiments further includes: receiving user data from a network node at a wireless device.

[0228] Example Implementation C17. A communication system including a host computer, the host computer comprising:

[0229] The communication interface is configured to receive user data originating from transmissions from wireless devices to network nodes.

[0230] The wireless device includes a radio interface and processing circuitry, the processing circuitry of which is configured to perform... Figure 15Any step of method 1500 or any embodiment in the above embodiments.

[0231] Example embodiment C18. The communication system according to the foregoing embodiments further includes a wireless device.

[0232] Example embodiment C19. The communication system according to the foregoing two embodiments further includes a network node, wherein the network node includes: a radio interface configured to communicate with a wireless device; and a communication interface configured to forward user data carried by a transmission from the wireless device to the network node to a host.

[0233] Example Implementation C20. The communication system according to the foregoing three embodiments, wherein:

[0234] The host computer's processing circuitry is configured to execute host applications; and

[0235] The processing circuitry of the wireless device is configured to execute client applications associated with the host application, thereby providing user data.

[0236] Example Implementation C21. The communication system according to the foregoing four embodiments, wherein:

[0237] The host computer's processing circuitry is configured to execute host applications, thereby providing requested data; and

[0238] The processing circuitry of the wireless device is configured to execute a client application associated with the host application, thereby providing user data in response to requested data.

[0239] Example Implementation C22. A method implemented in a communication system including a host computer, a network node, and a wireless device, the method comprising:

[0240] At the host computer, user data sent from the wireless device to the network node is received, wherein the wireless device performs... Figure 15 Any step of method 1500 or any embodiment thereof described above.

[0241] Example embodiment C23. The method according to the foregoing embodiments further includes: providing user data to a network node at the wireless device.

[0242] Example Implementation C24. The method according to the foregoing two embodiments further includes:

[0243] At the wireless device, a client application is executed to provide the user data to be sent; and

[0244] At the host computer, the host application associated with the client application is executed.

[0245] Example Implementation C25. The method according to the foregoing three embodiments further includes:

[0246] At the wireless device, execute the client application; and

[0247] At the wireless device, input data from the client application is received. This input data is provided on the host computer by executing a host application associated with the client application.

[0248] The user data to be sent is provided by the client application in response to the input data.

[0249] Example Implementation C26. A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from a wireless device transmitted to a network node, wherein the network node includes a radio interface and processing circuitry configured to perform... Figure 17 Any step of method 1700 or any embodiment of the above embodiments thereof.

[0250] Example embodiment C27. The communication system according to the foregoing embodiments further includes a network node.

[0251] Example embodiment C28. The communication system according to the foregoing two embodiments further includes a wireless device, wherein the wireless device is configured to communicate with a network node.

[0252] Example Implementation C29. The communication system according to the foregoing three embodiments, wherein:

[0253] The host computer's processing circuitry is configured to execute host applications;

[0254] The wireless device is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0255] Example Implementation C30. A method implemented in a communication system including a host computer, a network node, and a wireless device, the method comprising:

[0256] At the host computer, user data transmitted from the network node and already received from the wireless device is received from the base station, wherein the wireless device performs... Figure 15 Any step of method 1500 or any embodiment of the above embodiments thereof.

[0257] Example embodiment C31. The method according to the foregoing embodiments further includes: receiving user data from a wireless device at a network node.

[0258] Example Implementation C32. The method described in the foregoing two embodiments further includes: at the network node, initiating the transmission of the received user data to the host computer.

[0259] Example Implementation C33. The method according to any of the foregoing embodiments, wherein the network node includes a base station.

[0260] Example Implementation C34. The method according to any of the foregoing embodiments, wherein the wireless device includes a user equipment (UE).

[0261] abbreviation

[0262] At least some of the following abbreviations may be used in this disclosure. In the event of inconsistencies between abbreviations, the usage above shall prevail. If listed multiple times below, the first listing shall take precedence over any subsequent listing.

[0263] 1xRTT CDMA2000 1x Radio Transmission Technology

[0264] 3GPP Third Generation Partnership Project

[0265] 5G (Fifth Generation)

[0266] 5GS 5G system

[0267] 5QI 5G QoS identifier

[0268] ABS almost blank subframe

[0269] AN access network

[0270] AN access node

[0271] ANR Automatic Neighbor Relations

[0272] AP access point

[0273] ARQ (Automatic Repeat Request)

[0274] AS Access Layer

[0275] AWGN Additive White Gaussian Noise

[0276] BCCH Broadcast Control Channel

[0277] BCH Broadcast Channel

[0278] BLER block error rate

[0279] BS base station

[0280] BSC Base Station Controller

[0281] BTS base station transceiver station

[0282] CA carrier aggregation

[0283] CC carrier component

[0284] CCCH SDU Common Control Channel SDU

[0285] CDMA Code Division Multiple Access

[0286] CG Community Group

[0287] CGI Cell Global Identifier / Identifier

[0288] CIR channel impulse response

[0289] CN Core Network

[0290] CP cyclic prefix

[0291] CPICH Common Pilot Channel

[0292] CPICH Ec / No: Energy received by each CPICH chip divided by the power density in the frequency band.

[0293] CQI Channel Quality Information

[0294] C-RNTI Community RNTI

[0295] CSI Channel State Information

[0296] DCCH Dedicated Control Channel

[0297] DL downlink

[0298] DL-SCH Downlink Shared Channel

[0299] DM demodulation

[0300] DMRS demodulation reference signal

[0301] DRX discontinuous reception

[0302] DTX discontinuous transmission

[0303] DTCH Dedicated Service Channel

[0304] DUT (Device Under Test)

[0305] EARFCN evolved absolute radio frequency channel number

[0306] E-CID Enhanced Cell ID (Location Method)

[0307] ECGI evolved from CGI

[0308] E-SMLC Evolution Service Mobile Location Center

[0309] ECGI evolved from CGI

[0310] eMBB Enhanced Mobile Broadband

[0311] eNB E-UTRAN NodeB / eNodeB

[0312] EPDCCH Enhanced Physical Downlink Control Channel

[0313] EPS Evolution of Grouping Systems

[0314] E-SMLC Evolution Service Mobile Location Center

[0315] E-UTRA evolved from UTRA

[0316] E-UTRAN evolved universal terrestrial radio access network

[0317] FDD (Frequency Division Duplex)

[0318] FFS requires further research.

[0319] GERN GSM EDGE radio access network

[0320] gNB gNode B (Base station in NR; Node B that supports NR and connections to NGC)

[0321] GNSS Global Navigation Satellite System

[0322] GSM Global Mobile Communication System

[0323] HARQ Hybrid Automatic Repeat Request

[0324] HO switch

[0325] HSPA High-Speed ​​Packet Access

[0326] HRPD High-Speed ​​Packet Data

[0327] LOS (Location of View)

[0328] LPP LTE positioning protocol

[0329] LTE Long Term Evolution

[0330] M2M (Machine to Machine)

[0331] MAC Media Access Control

[0332] MBB Mobile Broadband

[0333] MBMS Multimedia Broadcast / Multicast Service

[0334] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0335] MBSFN ABS MBSFN almost blank subframes

[0336] MDT road test minimization

[0337] MIB (Master Information Block)

[0338] MME (Mobility Management Entity)

[0339] MRTD Maximum Receive Timing Difference

[0340] MSC Mobile Switching Center

[0341] MTC Machine Type Communication

[0342] NGC Next Generation Core Network

[0343] PDCCH Narrowband Physical Downlink Control Channel

[0344] NR New Radio

[0345] OCNG OFDMA Channel Noise Generator

[0346] OFDM (Orthogonal Frequency Division Multiplexing)

[0347] OFDMA (Orthogonal Frequency Division Multiple Access)

[0348] OSS Operation Support System

[0349] OTDOA Observation Time Difference

[0350] O&M Operations and Maintenance

[0351] PBCH (Physical Broadcast Channel)

[0352] P-CCPCH Main Common Control Physical Channel

[0353] Pcell main cell

[0354] PCFICH Physical Control Format Indicator Channel

[0355] PCH Paging Channel

[0356] PCI Physical Cell Identifier / Identifier

[0357] PDCCH (Physical Downlink Control Channel)

[0358] PDP distribution delay distribution

[0359] PDSCH (Physical Downlink Shared Channel)

[0360] PGW Packet Gateway

[0361] PHICH Physical Hybrid ARQ Indicator Channel

[0362] PLMN Public Land Mobile Network

[0363] PMI Precoding Matrix Indicator

[0364] PRACH (Physical Random Access Channel)

[0365] PRS Positioning Reference Signal

[0366] PS Packet Switching

[0367] PSCell main SCell

[0368] PSC Main Service Cell

[0369] PSS Master Synchronization Signal

[0370] PUCCH (Physical Uplink Control Channel)

[0371] PUSCH Physical Uplink Shared Channel

[0372] QAM Quadrature Amplitude Modulation

[0373] PACH Random Access Channel

[0374] RAB Radio Access Bearer

[0375] RAN (Radio Access Network)

[0376] RANAP Radio Access Network Application Section

[0377] RAT Radio Access Technology

[0378] RF (Radio Frequency)

[0379] RLM Radio Link Monitoring

[0380] RNC Radio Network Controller

[0381] RNTI (Radio Network Temporary Identifier)

[0382] RRC Radio Resource Control

[0383] RRM Radio Resource Management

[0384] RRH Remote Radio Header

[0385] RRU Remote Radio Unit

[0386] RS reference signal

[0387] RSCP Received Signal Code Power

[0388] RSRP reference signal received power

[0389] RSRQ reference signal reception quality

[0390] RSSI Received Signal Strength Indicator

[0391] RSTD (Reference Signal Time Difference)

[0392] RV Redundant Version

[0393] RX receiver

[0394] RWR has a redirected release.

[0395] SCC secondary component carrier

[0396] SCH Synchronization Channel

[0397] Scell ​​auxiliary cell

[0398] SCG Auxiliary Community Group

[0399] SCS Subcarrier Spacing

[0400] SDU Service Data Unit

[0401] SeNB auxiliary eNodeB

[0402] SFN system frame number

[0403] SGW Service Gateway

[0404] SI System Information

[0405] SIB System Information Block

[0406] SIB1 System Information Block Type 1

[0407] SINR (Signal-to-Interference-plus-Noise Ratio)

[0408] SNR (Signal-to-Noise Ratio)

[0409] S-NSSAI Single Network Slice Selection Auxiliary Information

[0410] SON Self-Organizing Network

[0411] SS synchronization signal

[0412] SSC Ancillary Service Community

[0413] SSS auxiliary synchronization signal

[0414] TBS (Transfer Block Size)

[0415] TDD (Time Division Duplex)

[0416] TDOA arrival time difference

[0417] TOA Arrival Time

[0418] TSS Level 3 Synchronization Signal

[0419] TTI Transmission Time Interval

[0420] TX transmitter

[0421] ARFCN UMTS Absolute Radio Frequency Channel Number

[0422] UE User Equipment

[0423] UL uplink

[0424] UMTS (Universal Mobile Telecommunications System)

[0425] USIM Universal Subscriber Identification Module

[0426] UTDOA uplink arrival time difference

[0427] UTRA Universal Terrestrial Radio Access

[0428] UTRAN Universal Terrestrial Radio Access Network

[0429] WCDMA Wide CDMA

[0430] WLAN wide area network

[0431] Support

[0432] Modifications, additions, or omissions may be made to the systems and apparatus described herein without departing from the scope of this disclosure. Components of the systems and apparatus may be integrated or separated. Furthermore, the operation of the systems and apparatus may be performed by more components, fewer components, or other components. Additionally, any suitable logic, including software, hardware, and / or other logic, may be used to perform the operation of the systems and apparatus. As used herein, “each” refers to each member of a set or each member of a subset of a set.

[0433] Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of this disclosure. The methods may include more, fewer, or other steps. Furthermore, the steps may be performed in any suitable order.

[0434] Although this disclosure has been described with reference to specific embodiments, changes and arrangements of the embodiments will be apparent to those skilled in the art. Therefore, the above description of the embodiments does not limit this disclosure. Other changes, substitutions, and variations may be made without departing from the spirit and scope of this disclosure.

Claims

1. A method (1500) performed by a wireless device (110), the method comprising: Obtain a codebook (1502) based on a first downlink data-to-uplink feedback timing set (30) for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set (31) for feedback associated with unicast downlink data, wherein the number of downlink slots associated with the codebook is determined based on the union of the first downlink data-to-uplink feedback timing set and the second downlink data-to-uplink feedback timing set; and Based on the codebook, a feedback (1504) is sent to the network node (160). The number of feedback bits (32) in the codebook for downlink slots associated with the codebook is determined based on the union of a first Time Domain Resource Allocation (TDRA) list and a second TDRA list, wherein the first TDRA list indicates possible allocations of symbols for the downlink shared channel used for multicast downlink data, and wherein the second TDRA list indicates possible allocations of symbols for the downlink shared channel used for unicast downlink data. Wherein, there is an overlap (33) between the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set, wherein the overlap corresponds to one or more downlink time slots in the downlink time slots associated with the codebook, and wherein the number of feedback bits in the codebook for each downlink time slot from the overlap is determined based on the union of the first TDRA list and the second TDRA list, and in: The first downlink data to uplink feedback timing set includes one or more first values ​​(34) not included in the second downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more first values ​​is determined by the first TDRA list; and / or The second downlink data to uplink feedback timing set includes one or more second values ​​(35) not included in the first downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more second values ​​is determined by the second TDRA list.

2. The method according to claim 1, wherein, The feedback sent is for both multicast downlink data and unicast downlink data.

3. The method according to any one of the preceding claims, wherein, The first downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for multicast, and the first downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

4. The method according to any one of the preceding claims, wherein, The second downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for unicast, and the second downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

5. The method according to claim 4, wherein, The rollback DCI format is DCI format 1_0.

6. The method according to any one of the preceding claims, wherein, The first TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

7. The method according to any one of the preceding claims, wherein, The second TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

8. The method according to any one of the preceding claims, wherein, Obtaining the codebook includes constructing the codebook.

9. The method according to any one of the preceding claims further includes receiving at least one message from the network node, the at least one message including a multicast configuration and a unicast configuration, the multicast configuration including the first downlink data to uplink feedback timing set, and the unicast configuration including the second downlink data to uplink feedback timing set.

10. The method according to any one of the preceding claims, wherein, The codebook is a Type 1 Hybrid Automatic Repeat Request-ACK codebook.

11. A wireless device (110) including a processing circuit (120) configured to: A codebook is obtained, the codebook being based on a first downlink data-to-uplink feedback timing set (30) for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set (31) for feedback associated with unicast downlink data, wherein, The number of downlink time slots associated with the codebook is determined based on the union of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set; as well as Based on the codebook, feedback is sent to network node (160). The number of feedback bits (32) in the codebook for downlink slots associated with the codebook is determined based on the union of a first Time Domain Resource Allocation (TDRA) list and a second TDRA list, wherein the first TDRA list indicates possible allocations of symbols for the downlink shared channel used for multicast downlink data, and wherein the second TDRA list indicates possible allocations of symbols for the downlink shared channel used for unicast downlink data. Wherein, there is an overlap (33) between the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set, wherein the overlap corresponds to one or more downlink time slots in the downlink time slots associated with the codebook, and wherein the number of feedback bits in the codebook for each downlink time slot from the overlap is determined based on the union of the first TDRA list and the second TDRA list, and in: The first downlink data to uplink feedback timing set includes one or more first values ​​(34) not included in the second downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more first values ​​is determined by the first TDRA list; and / or The second downlink data to uplink feedback timing set includes one or more second values ​​(35) not included in the first downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more second values ​​is determined by the second TDRA list.

12. The wireless device according to claim 11, wherein, The feedback sent is for both multicast downlink data and unicast downlink data.

13. The wireless device according to any one of claims 11 to 12, wherein, The first downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for multicast, and the first downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

14. The wireless device according to any one of claims 11 to 13, wherein, The second downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for unicast, and the second downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

15. The wireless device according to claim 14, wherein, The rollback DCI format is DCI format 1_0.

16. The wireless device according to any one of claims 11 to 15, wherein, The first TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

17. The wireless device according to any one of claims 11 to 16, wherein, The second TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

18. The wireless device according to any one of claims 11 to 17, wherein, The processing circuit is configured to obtain the codebook by constructing the codebook.

19. The wireless device according to any one of claims 11 to 18, wherein, The processing circuit is further configured to receive at least one message from the network node, the at least one message including a multicast configuration and a unicast configuration, the multicast configuration including the first downlink data to uplink feedback timing set, and the unicast configuration including the second downlink data to uplink feedback timing set.

20. The wireless device according to any one of claims 11 to 19, wherein, The codebook is a Type 1 Hybrid Automatic Repeat Request-ACK codebook.

21. A method (1700) performed by a network node (160), the method comprising: Obtain a codebook (1702) based on a first downlink data-to-uplink feedback timing set (30) for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set (31) for feedback associated with unicast downlink data, wherein the number of downlink slots associated with the codebook is determined based on the union of the first downlink data-to-uplink feedback timing set and the second downlink data-to-uplink feedback timing set; and Based on the codebook, feedback is received from the wireless device (110) (1704). The number of feedback bits (32) in the codebook for downlink slots associated with the codebook is determined based on the union of a first Time Domain Resource Allocation (TDRA) list and a second TDRA list, wherein the first TDRA list indicates possible allocations of symbols for the downlink shared channel used for multicast downlink data, and wherein the second TDRA list indicates possible allocations of symbols for the downlink shared channel used for unicast downlink data. Wherein, there is an overlap (33) between the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set, wherein the overlap corresponds to one or more downlink time slots in the downlink time slots associated with the codebook, and wherein the number of feedback bits in the codebook for each downlink time slot from the overlap is determined based on the union of the first TDRA list and the second TDRA list, and in: The first downlink data to uplink feedback timing set includes one or more first values ​​(34) not included in the second downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more first values ​​is determined by the first TDRA list; and / or The second downlink data to uplink feedback timing set includes one or more second values ​​(35) not included in the first downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more second values ​​is determined by the second TDRA list.

22. The method according to claim 21, wherein, The feedback received is for both multicast downlink data and unicast downlink data.

23. The method according to any one of claims 21 to 22, wherein, The first downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for multicast, and the first downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

24. The method according to any one of claims 21 to 23, wherein, The second downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for unicast, and the second downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

25. The method according to claim 24, wherein, The rollback DCI format is DCI format 1_0.

26. The method according to any one of claims 21 to 25, wherein, The first TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

27. The method according to any one of claims 21 to 26, wherein, The second TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

28. The method according to any one of claims 21 to 27, wherein, Obtaining the codebook includes constructing the codebook.

29. The method of any one of claims 21 to 28, further comprising sending at least one message to the wireless device, the at least one message including a multicast configuration and a unicast configuration, the multicast configuration including the first downlink data to uplink feedback timing set, and the unicast configuration including the second downlink data to uplink feedback timing set.

30. The method according to any one of claims 21 to 29, wherein, The codebook is a Type 1 Hybrid Automatic Repeat Request-ACK codebook.

31. A network node (160) including processing circuitry (170), said processing circuitry (170) being configured to: A codebook is obtained, the codebook being based on a first downlink data-to-uplink feedback timing set (30) for feedback associated with multicast downlink data and a second downlink data-to-uplink feedback timing set (31) for feedback associated with unicast downlink data, wherein, The number of downlink time slots associated with the codebook is determined based on the union of the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set; as well as Based on the codebook, feedback is received from the wireless device (110). The number of feedback bits (32) in the codebook for downlink slots associated with the codebook is determined based on the union of a first Time Domain Resource Allocation (TDRA) list and a second TDRA list, wherein the first TDRA list indicates possible allocations of symbols for the downlink shared channel used for multicast downlink data, and wherein the second TDRA list indicates possible allocations of symbols for the downlink shared channel used for unicast downlink data. Wherein, there is an overlap (33) between the first downlink data to uplink feedback timing set and the second downlink data to uplink feedback timing set, wherein the overlap corresponds to one or more downlink time slots in the downlink time slots associated with the codebook, and wherein the number of feedback bits in the codebook for each downlink time slot from the overlap is determined based on the union of the first TDRA list and the second TDRA list, and in: The first downlink data to uplink feedback timing set includes one or more first values ​​(34) not included in the second downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more first values ​​is determined by the first TDRA list; and / or The second downlink data to uplink feedback timing set includes one or more second values ​​(35) not included in the first downlink data to uplink feedback timing set, and in the codebook, the number of feedback bits for each downlink slot corresponding to the one or more second values ​​is determined by the second TDRA list.

32. The network node according to claim 31, wherein, The feedback received is for both multicast downlink data and unicast downlink data.

33. The network node according to any one of claims 31 to 32, wherein, The first downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for multicast, and the first downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

34. The network node according to any one of claims 31 to 33, wherein, The second downlink data to uplink feedback timing set is configured in the physical uplink control channel (PUCCH) configuration, or the downlink control information (DCI) format is used for unicast, and the second downlink data to uplink feedback timing set is a predefined set {1, 2, 3, 4, 5, 6, 7, 8}.

35. The network node according to claim 34, wherein, The rollback DCI format is DCI format 1_0.

36. The network node according to any one of claims 31 to 35, wherein, The first TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

37. The network node according to any one of claims 31 to 36, wherein, The second TDRA list is configured by the Physical Downlink Shared Channel (PDSCH) configuration.

38. The network node according to any one of claims 31 to 37, wherein, The processing circuit is configured to obtain the codebook by constructing the codebook.

39. The network node according to any one of claims 31 to 38, wherein, The processing circuitry is further configured to send at least one message to the wireless device, the at least one message including a multicast configuration and a unicast configuration, the multicast configuration including the first downlink data to uplink feedback timing set, and the unicast configuration including the second downlink data to uplink feedback timing set.

40. The network node according to any one of claims 31 to 39, wherein, The codebook is a Type 1 Hybrid Automatic Repeat Request-ACK codebook.

Images