Method, communication device and network infrastructure equipment
By transmitting activation and update messages in the wireless communication network, configuring the communication device to monitor multiple periodic scheduling windows, and using update DCI to adjust parameters, the efficiency and delay problems of the wireless communication network in handling multiple data traffic scenarios is solved, and the efficiency and delay problems of the wireless communication network are improved. Support capabilities for URLLC and eMBB services.
Patent Information
- Application Number
- CN202380028415.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-03-29
- Filing Date
- 2023-03-09
- Publication Date
- 2024-11-01
AI Technical Summary
Currently, wireless communication networks are difficult to effectively support data traffic of different applications and characteristics, especially in scenarios with high data volume and low latency requirements, such as ultra-reliable low-latency communication (URLLC) and enhanced mobile broadband (eMBB) services, resulting in the network Challenges when dealing with multiple traffic profiles and requirements.
By transmitting activation messages and update messages to the communication device, configuring them to monitor multiple periodic scheduling windows, and performing downlink transmissions based on the updated parameter set, the parameters of the SPS instance are dynamically adjusted using Update DCI (U-DCI), for example, Transmission block size and modulation coding scheme to adapt to different flow characteristics.
It improves the processing capability and efficiency of the network in different traffic scenarios, reduces resource waste, reduces control channel overhead, and enhances the ability to support non-integer cycle traffic and jitter characteristics.
Smart Images

Figure CN118891950A_ABST
Abstract
Description
[0001] This application claims the Paris Convention priority of European Patent Application No. 22165239.9 filed on March 29, 2022, the contents of which are incorporated herein by reference. Technical Field
[0002] The present disclosure relates to a communication device, a network infrastructure equipment and a method of operating a communication device to receive data from a wireless communication network. Background Art
[0003] The "background" description provided herein is for the purpose of generally presenting the context of the present disclosure. The work performed by the presently designated inventors described in this background section, and aspects that may not qualify as prior art at the time of filing, are not admitted, either explicitly or implicitly, to be prior art to the present disclosure.
[0004] The latest generation of mobile telecommunication systems, such as those based on the UMTS and Long Term Evolution (LTE) architectures defined by 3GPP, are capable of supporting a wider range of services than the simple voice and messaging services provided by previous generations of mobile telecommunication systems. For example, using the improved radio interface and enhanced data rates provided by LTE systems, users are able to enjoy high data rate applications, such as mobile video streaming and mobile video conferencing, which were previously available only via fixed line data connections. As a result, there is a strong demand to deploy such networks, and it is expected that the coverage areas of these networks (i.e., the geographic locations where the networks can be accessed) will continue to increase rapidly.
[0005] The current generation of wireless communication networks is expected to routinely and efficiently support communications with an ever-increasing range of devices that are associated with a wider range of data traffic profiles and types. For example, wireless communication networks are expected to efficiently support communications with devices including reduced complexity devices, machine type communication (MTC) devices, high-resolution video displays, virtual reality headsets, and the like. Some of these different types of devices may be deployed in very large numbers, such as low-complexity devices used to support the "Internet of Things", and may typically be associated with the transmission of relatively small amounts of data with relatively high delay tolerance. Other types of devices (e.g., supporting high-definition video streaming) may be associated with the transmission of relatively large amounts of data with relatively low delay tolerance. Other types of devices, such as for autonomous vehicle communications and for other critical applications, may be characterized by data that should be transmitted over the network with low latency and high reliability. Depending on the application being run, a single device type may also be associated with different traffic profiles / characteristics. For example, different considerations may apply to effectively support data exchange with a smartphone when the smartphone is running a video streaming application (high downlink data) compared to when the smartphone is running an Internet browsing application (sporadic uplink and downlink data) or when it is used for voice communications by emergency responders in an emergency situation (data subject to strict reliability and latency requirements).
[0006] In view of this, there is a desire for current wireless communication networks (e.g., those that may be referred to as 5G or new radio (NR) systems / new radio access technology (RAT) systems) and future iterations / versions of existing systems to effectively support connectivity with a wide range of devices associated with different applications and different characteristic data traffic profiles and requirements.
[0007] An example of a new service is referred to as an ultra-reliable low latency communication (URLLC) service, which, as the name implies, requires the transmission of data units or packets with high reliability and low communication latency. Another example of a new service is an enhanced mobile broadband (eMBB) service, which is characterized by the requirement to support high capacity of up to 20 Gb / s. Therefore, URLLC and eMBB type services represent challenging examples for both LTE type communication systems and 5G / NR communication systems.
[0008] 5G NR has continued to evolve and the current agenda includes 5G-NR-Advanced, where some further enhancements are expected, especially to support new use cases / scenarios with higher requirements. The increasing number of different types of network infrastructure equipment and terminal devices associated with different traffic profiles brings new challenges for efficiently handling communications in wireless communication systems, which need to be addressed. Summary of the invention
[0009] The present disclosure may help solve or alleviate at least some of the above-mentioned problems.
[0010] According to a first aspect, a method for infrastructure equipment is provided, the method comprising: transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor multiple periodic scheduling windows for downlink transmission, wherein the activation message indicates an initial parameter set for the downlink transmission; transmitting an update message to the communication device, wherein the update message indicates an updated parameter set for one or more of the downlink transmissions; and transmitting a downlink transmission to the communication device and during a scheduling window in the multiple periodic scheduling windows based on the updated parameter set.
[0011] According to a second aspect, a method for a communication device is provided, the method comprising: receiving an activation message from an infrastructure device, wherein the activation message configures the communication device to monitor multiple periodic scheduling windows for downlink transmission, wherein the activation message indicates an initial parameter set for the downlink transmission; receiving an update message from the infrastructure device, wherein the update message indicates an updated parameter set for one or more downlink transmissions; monitoring a scheduling window in the multiple periodic scheduling windows; and receiving a downlink transmission from the infrastructure device and during the scheduling window based on the updated parameter set.
[0012] Various aspects and features of the present disclosure are defined in the following claims.
[0013] It should be understood that both the foregoing general description and the following detailed description are exemplary rather than restrictive of the present technology. The described embodiments and other advantages will be best understood by reference to the following detailed description taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0014] A more complete appreciation of the present disclosure and many of its attendant advantages will be readily obtained as the present disclosure becomes better understood by reference to the following detailed description when considered in conjunction with the accompanying drawings, wherein like reference numerals designate identical or corresponding parts throughout the several views, and wherein:
[0015] Figure 1 Some aspects of an LTE-type wireless communication system that may be configured to operate in accordance with certain embodiments of the present disclosure are schematically represented.
[0016] Figure 2 Some aspects of a new radio access technology (RAT) wireless communication system that may be configured to operate in accordance with certain embodiments of the present disclosure are schematically represented.
[0017] Figure 3 is a schematic block diagram of exemplary infrastructure equipment and communication devices that may be configured to operate in accordance with certain embodiments of the present disclosure.
[0018] Figure 4 is an illustrative representation of communication resources in time and frequency of uplink and downlink channels of a time-division wireless access interface, wherein multiple hybrid automatic repeat request acknowledgements (HARQ-ACKs) may be multiplexed onto a single physical uplink control channel (PUCCH).
[0019] Figure 5 is an illustrative representation of communication resources in time and frequency for uplink and downlink channels of a time-division wireless access interface, wherein a PUCCH resource indicator is used to indicate to which PUCCH a HARQ-ACK may be multiplexed.
[0020] Figure 6 is an illustrative representation of communication resources in time and frequency for uplink and downlink channels of a time-division wireless access interface, wherein an example of a sub-slot based PUCCH is shown.
[0021] Figure 7 is an illustrative representation of communication resources in time and frequency for uplink and downlink channels of a time-division wireless access interface, wherein multiple HARQ-ACKs for a semi-persistent scheduling (SPS) physical downlink shared channel (PDSCH) are multiplexed onto a single PUCCH in each subslot.
[0022] Figure 8 is an illustrative example of a non-integer packet period.
[0023] Fig. 9 is an illustrative example of the variability of packet size and timing for a particular flow.
[0024] Fig.10 is an illustrative example of jitter in packet arrival.
[0025] Fig.11 is an illustrative example of a technique for handling jitter in packet arrivals.
[0026] Fig.12 is an illustrative example of variable packet size for periodic traffic.
[0027] Fig.13 is an illustrative example of a technique for handling variable packet sizes for periodic traffic.
[0028] Fig.14 is an illustrative example of a technique for handling variable packet sizes for periodic traffic.
[0029] Fig.15 An exemplary technique for transmitting an update DCI message according to the present disclosure is shown.
[0030] Fig.16A is an illustrative example of updating DCI.
[0031] Fig. 16B is an illustrative example of updating DCI.
[0032] Fig. 16C is an illustrative example of updating DCI.
[0033] Fig.16D is an illustrative example of updating DCI.
[0034] Fig.17A is an illustrative example of using update DCI to provide additional information about the PDSCH.
[0035] Fig. 17B is an illustrative example of using update DCI to provide additional information about the PDSCH.
[0036] Fig. 17C is an illustrative example of using update DCI to provide additional information about the PDSCH.
[0037] Fig.18 An exemplary technique for transmitting an update DCI message according to the present disclosure is shown.
[0038] Fig.19 is an illustrative example of updating the transmission timing of a DCI message.
[0039] Fig. 20A is an illustrative example of using an update DCI message to temporarily change PDSCH parameters.
[0040] Fig. 20B is an illustrative example of using an update DCI message to temporarily change PDSCH parameters.
[0041] Fig.21 is an illustrative example of using an Update DCI message to modify the timing of an SPS opportunity.
[0042] Fig. 22 An exemplary technique for transmitting an update DCI message according to the present disclosure is shown.
[0043] Fig.23 A flow chart showing an exemplary method for infrastructure equipment according to the present disclosure is shown.
[0044] Fig.24 A flow chart of an exemplary method for a communication device according to the present disclosure is shown. DETAILED DESCRIPTION
[0045] Advanced long-term evolution radio access technology (4G)
[0046] Figure 1 A schematic diagram is provided showing some basic functions of a mobile telecommunication network / system 6 that typically operates according to LTE principles, but which may also support other radio access technologies, and which may be suitable for implementing embodiments of the present disclosure as described herein. Figure 1 Certain aspects of the various elements and their corresponding modes of operation are well known and defined in relevant standards managed by the 3GPP (RTM) body and are also described in a number of books on the subject, for example, Holma H. and Toskala A [1]. It should be understood that operational aspects of the telecommunications network discussed herein that are not specifically described (e.g., relating to specific communication protocols and physical channels used for communication between different elements) may be implemented in accordance with any known techniques, for example, in accordance with relevant standards and known proposed amendments and supplements to relevant standards.
[0047] The network 6 comprises a plurality of base stations 1 connected to a core network 2. Each base station provides a coverage area 3 (ie, a cell) within which data can be communicated to and from a communication device 4. Although each base station 1 is Figure 1 Although shown as a single entity in the figure, those skilled in the art will understand that some functions of a base station may be performed by different interconnected elements, such as antennas (or antennae), remote radio heads, amplifiers, etc. Collectively, one or more base stations may form a wireless access network.
[0048] Data is transmitted from the base stations 1 to communication devices or mobile terminals (MTs) 4 within their respective coverage areas 3 via radio downlinks. Data is transmitted from the communication devices 4 to the base stations 1 via radio uplinks. The core network 2 routes data to and from the communication devices 4 via the respective base stations 1, and provides functions such as authentication, mobility management, charging, etc. The communication or terminal device 4 may also be referred to as a mobile station, user equipment (UE), user terminal, mobile radio, communication device, etc. The services provided by the core network 2 may include connection to the Internet or to an external telephone service. The core network 2 may further track the location of the communication device 4 so that it can effectively contact (i.e., page) the communication device 4 for transmitting downlink data to the communication device 4.
[0049] Base stations, as examples of network infrastructure equipment, may also be referred to as transceiver stations, Node Bs, e-Node Bs, eNBs, g-Node Bs, gNBs, etc. In this regard, different terms are often associated with different generations of wireless telecommunication systems for elements that provide broadly comparable functionality. However, exemplary embodiments of the present disclosure may be implemented equally in different generations of wireless telecommunication systems, and for simplicity, certain terms may be used regardless of the underlying network architecture. That is, the use of particular terms associated with certain exemplary implementations is not intended to indicate that these implementations are limited to the particular generation of networks to which the particular terms may be most associated.
[0050] New Radio Access Technology (5G(NR))
[0051] exist Figure 2 An exemplary configuration of a wireless communication network is shown in FIG, which uses some of the terms proposed and used for NR and 5G. Figure 2 In the figure, a plurality of transmission and reception points (TRPs) 10 are connected to distributed control units (DUs) 41, 42 via connection interfaces represented by lines 16. Each TRP 10 is arranged to transmit and receive signals within a radio frequency bandwidth available for the wireless communication network via a wireless access interface. Therefore, within the range of radio communication via the wireless access interface, each TRP 10 forms a cell of the wireless communication network, as represented by circle 12. Therefore, a wireless communication device 14 within the radio communication range provided by the cell 12 can transmit signals to and receive signals from the TRP 10 via the wireless access interface. Each of the distributed units 41, 42 is connected to a central unit (CU) 40 (which may be referred to as a control node) via an interface 46. The central unit 40 is then connected to a core network 20, which may contain all other functions required for transmitting data to and from wireless communication devices, and the core network 20 may be connected to other networks 30.
[0052] Figure 2 The elements of the wireless access network shown in FIG. 1 may be arranged in a manner similar to that described with respect to FIG. Figure 1 The examples described above operate in a manner consistent with the respective elements of the LTE network. It should be appreciated that Figure 2 The operational aspects of the telecommunications network represented in and the operational aspects of other networks discussed herein according to embodiments of the present disclosure (not specifically described (e.g., with respect to specific communication protocols and physical channels used for communication between different elements)) may be implemented according to any known technology, for example, according to currently used methods for implementing such operational aspects of wireless telecommunications systems (e.g., in accordance with relevant standards).
[0053] Figure 2The TRP 10 may partially have functionality corresponding to a base station or eNodeB of an LTE network. Similarly, the communication device 14 may have functionality corresponding to a communication device 4 known for operating with an LTE network. Therefore, it should be understood that operational aspects of the new RAT network (e.g., related to specific communication protocols and physical channels used for communication between different elements) may be different from those known from LTE or other known mobile telecommunication standards. However, it should also be understood that each core network component, base station, and communication device of the new RAT network is similar in function to the core network component, base station, and communication device of the LTE wireless communication network, respectively.
[0054] In terms of a wide range of top-level features, it can be broadly considered that the connection to Figure 2 The core network 20 of the new RAT telecommunication system represented in Figure 1 The core network 2 shown in FIG. 1 corresponds to the core network 2 shown in FIG. 1 , and the corresponding central unit 40 and its associated distributed units / TRP 10 can be broadly considered to provide corresponding Figure 1 The term network infrastructure equipment / access node may be used to cover both these elements of the wireless communication system and the more conventional base station type elements. Depending on the application to be implemented, the responsibility for scheduling transmissions scheduled over the radio interface between the various distributed units and the communication devices may lie with the control node / central unit and / or the distributed units / TRP. Figure 2 1 shows a communication device 14 within the coverage area of the first communication cell 12. Thus, the communication device 14 can exchange signaling with the first central unit 40 in the first communication cell 12 via one of the distributed units / TRPs 10 associated with the first communication cell 12.
[0055] It should also be understood that Figure 2 It only represents one example of the proposed architecture for a new RAT-based telecommunication system, wherein the method according to the principles described herein may be employed and the functionalities disclosed herein may also be applied to wireless telecommunication systems having different architectures.
[0056] Therefore, according to various architectures (such as Figure 1 and Figure 2), certain embodiments of the present disclosure as discussed herein may be implemented in a wireless telecommunications system / network. Therefore, it should be appreciated that the specific wireless telecommunications architecture in any given implementation is not of primary significance to the principles described herein. In this regard, certain embodiments of the present disclosure may be generally described in the context of communications between network infrastructure equipment / access nodes and communication devices, wherein the specific characteristics of the network infrastructure equipment / access nodes and communication devices will depend on the network infrastructure to be implemented. For example, in some cases, the network infrastructure equipment / access nodes may include base stations, such as Figure 1 The LTE type base station 1 shown is suitable for providing functions according to the principles described herein, and in other examples, the network infrastructure equipment may include Figure 2 A control unit / control node 40 and / or a TRP 10 of the kind shown in FIG. 1 is adapted to provide functionality according to the principles described herein.
[0057] Figure 2 A more detailed diagram of some components of the network is shown in Figure 3 Provided. Figure 3 As a simplified representation, Figure 2 The TRP 10 shown in FIG. 1 includes a wireless transmitter 30, a wireless receiver 32, and a controller or control processor 34, which is operable to control the transmitter 30 and the wireless receiver 32 to transmit and receive radio signals to one or more UEs 14 within the cell 12 formed by the TRP 10. Figure 3 As shown in the figure, according to normal operation, the exemplary UE14 is shown to include corresponding transmitter circuits 49, receiver circuits 48 and controller circuits 44, and the controller circuits 44 are configured to control the transmitter circuits 49 and the receiver circuits 48 to transmit signals representing uplink data to the wireless communication network via the wireless access interface formed by TRP10 and to receive downlink data as signals transmitted by the transmitter circuits 30 and received by the receiver circuits 48.
[0058] The transmitter circuits 30, 49 and the receiver circuits 32, 48 (as well as other transmitters, receivers, and transceivers described in accordance with the examples and embodiments of the present disclosure) may include radio frequency filters and amplifiers as well as signal processing components and devices to transmit and receive radio signals, for example, in accordance with the 5G / NR standard. The controller circuits 34, 44 (as well as other controllers described in accordance with the examples and embodiments of the present disclosure) may be, for example, a microprocessor, a CPU, or a dedicated chipset configured to execute instructions stored on a computer-readable medium (such as a non-volatile memory). The processing steps described herein may be performed, for example, by a microprocessor in combination with a random access memory, operating in accordance with instructions stored on a computer-readable medium. For ease of representation, the transmitters, receivers, and controllers are described in FIG. Figure 3 Schematically shown as separate elements in the figure. However, it will be appreciated that the functionality of these elements may be provided in a variety of different ways, for example, using one or more appropriately programmed programmable computers, or one or more appropriately configured application specific integrated circuits / circuits / chips / chip sets. As will be appreciated, the infrastructure equipment / TRP / base station and the UE / communication device will typically include various other elements associated with their operational functionality.
[0059] like Figure 3 As shown, TRP 10 also includes a network interface 50 that is connected to DU 42 via physical interface 16. Thus, network interface 50 provides a communication link for data and signaling traffic from TRP 10 to core network 20 via DU 42 and CU 40.
[0060] The interface 46 between DU42 and CU40 is called the F1 interface, which can be a physical or logical interface. The F1 interface 46 between CU and DU can be operated according to the 3GPP TS 38.470 and 3GPP TS 38.473 specifications, and can be formed by optical fiber or other wired or wireless high-bandwidth connections. In one example, the connection 16 from TRP10 to DU42 is via optical fiber. The connection between TRP10 and the core network 20 can generally be referred to as backhaul, which includes the interface 16 from the network interface 50 of TRP10 to DU42 and the F1 interface 46 from DU42 to CU40.
[0061] eURLLC and eMBB
[0062] Systems incorporating NR technology are expected to support different services (or service types), which may be characterized by different requirements for latency, data rate, and / or reliability. For example, enhanced mobile broadband (eMBB) services are characterized by requirements to support high capacity up to 20 Gb / s. Requirements for ultra-reliable and low-latency communications (URLLC) services are for 1–10 Gb / s of data within 1 ms. -5(99.999%) or higher (99.9999%) reliability for a single transmission of a 32-byte packet from the radio protocol layer 2 / 3 SDU entry point to the radio protocol layer 2 / 3 SDU exit point of the radio interface [2].
[0063] Massive machine type communication (mMTC) is another example of a service that can be supported by NR-based communication networks. In addition, the system can be expected to support further enhancements related to the Industrial Internet of Things (IIoT) to support services with new requirements for high availability, high reliability, low latency, and in some cases high precision positioning.
[0064] Enhanced URLLC (eURLLC) [3] specifies features that require high reliability and low latency, such as factory automation, transportation industry, power distribution, etc. in 5G systems. eURLLC is further enhanced to IIoT-URLLC [4], which aims to enhance UE feedback for hybrid automatic repeat request acknowledgement (HARQ-ACK) signaling for downlink transmission (e.g., PDSCH), increase signaling bits for sub-band CQI, URLCC operation in unlicensed bands, and intra-UE UCI multiplexing of different L1 priorities.
[0065] PDSCH HARQ-ACK / NACK signaling
[0066] Typically, as will be appreciated, hybrid automatic repeat request (HARQ) feedback is transmitted by a communication device (UE) to an infrastructure device (such as a gNB) with respect to a scheduled physical downlink shared channel (PDSCH) to inform the infrastructure device whether the communication device has successfully decoded the corresponding PDSCH. Each PDSCH may be transmitted according to a different HARQ process, which may be assigned a specific HARQ process number (HPN) to identify the HARQ process for that PDSCH. The HPN number may be assigned by an infrastructure device (such as a gNB) in a wireless communication network. Each HARQ process involves transmitting a HARQ acknowledgement (i.e., ACK) or a HARQ negative acknowledgement (i.e., NACK), depending on whether the PDSCH transmitted according to that HARQ process was successfully received / decoded. For example, if the PDSCH was successfully received / decoded, the receiving communication device will send a HARQ acknowledgement (i.e., ACK), and if the transmission was not successfully received, the communication device will send a HARQ negative acknowledgement (i.e., NACK).
[0067] It will be appreciated by those skilled in the art that reference to "HARQ-ACK" may mean either "ACK" or "NACK" and is therefore used when there is no need to distinguish between "ACK" and "NACK".
[0068] For the scheduled transmission of downlink data from an infrastructure device to a communication apparatus in a wireless communication network, it is common for the infrastructure device to first send control signaling, e.g. on a downlink control channel (e.g. PDCCH - Physical Downlink Control Channel), which includes downlink control information (DCI) indicating (authorizing) downlink resources to be used for transmitting the data, e.g. on a downlink shared channel (such as PDSCH).
[0069] Based on the DCI, the communication device may determine uplink resources for sending uplink control information (UCI) including an ACK or NACK for the data, for example, on an uplink control channel such as PUCCH, although it may also be on an uplink shared channel such as PUSCH. The communication device then attempts to receive the data on the indicated resources on the PDSCH. If the communication device successfully decodes the data, the communication device transmits the UCI including the ACK on the determined uplink resources. If the communication device does not successfully decode the data, the communication device transmits the UCI including the NACK on the determined uplink resources. This allows the infrastructure equipment to determine whether it should schedule a retransmission of the data.
[0070] To provide some specific examples, certain examples will be described herein in the context of HARQ-ACK transmissions for downlink transmissions of data associated with XR applications, where URLLC functionality is relevant and terminology is used, for example, with respect to channel names (such as PUCCH and PDSCH) and signaling names (such as DCI and UCI) that are commonly used in conjunction with current 3GPP wireless communication networks. However, it should be understood that this is merely for convenience and that, in general, the methods discussed herein may be applied to other service types and in wireless communication networks that use different terminology. Thus, unless the context requires otherwise, references to PUCCH herein should be understood to refer generally to the physical uplink control channel, rather than specifically to a specific format of the physical uplink control channel, and so forth for other channels and terminology that may be referred to herein.
[0071] As will be appreciated, the resources of the wireless access interface comprise a grid of communication resources (ie, a radio frame structure) spanning frequency and time. The frequency dimension is divided into subcarriers and the time dimension is divided into OFDM symbols, which are grouped into slots and subslots.
[0072] PDSCH HARQ-ACK feedback
[0073] In the dynamic grant PDSCH (DG-PDSCH), the gNB dynamically indicates PDSCH resources using the DL grant carried by the downlink control information (DCI) in the physical downlink control channel (PDCCH).
[0074] PDSCH is transmitted using HARQ transmission, where for a PDSCH ending in slot n, the corresponding physical uplink control channel (PUCCH) carrying HARQ-ACK is transmitted in slot n+K1. Here, in the dynamically granted PDSCH, the value of K1 is indicated in the field "PDSCH to HARQ_Feedback Timing Indicator" of the DL grant (carried by DCI format 1_0, DCI format 1_1, or DCI format 1_2). Multiple (different) PDSCHs can point to the same slot to transmit their respective HARQ-ACKs, and these HARQ-ACKs (in the same slot) are multiplexed into a single PUCCH. Therefore, the PUCCH may contain multiple HARQ-ACKs for multiple PDSCHs.
[0075] Figure 4 Such an example is shown in FIG, where, on the DL of the wireless access interface 102, three DL grants are transmitted to the UE via DCI#1, DCI#2, and DCI#3 in time slots n, n+1, and n+2, respectively. DCI#1, DCI#2, and DCI#3 schedule PDSCH#1, PDSCH#2, and PDSCH#3, respectively, as shown by arrows 112, 114, and 116. DCI#1, DCI#2, and DCI#3 also indicate K1=3, K1=2, and K1=1, respectively, which determines the uplink channel resources of the UL channel 101, as shown by arrows 120, 122, and 124. Because the K1 value indicates that the HARQ-ACK feedback for PDSCH#1, PDSCH#2, and PDSCH#3 are all transmitted in time slot n+4, the UE multiplexes all of these HARQ-ACKs into a single PUCCH, i.e., PUCCH#1. The PUCCH multiplexing window is the time window in which the PDSCH can be multiplexed into the single PUCCH, and the size of the PUCCH multiplexing window depends on the range of K1 values. Figure 4 In the example of , the PUCCH multiplexing window is from slot n to slot n+3 (ie, between time t0 and time t7), which means that the maximum K1 value is 4 slots.
[0076] In some examples, only one PUCCH per time slot is allowed to carry HARQ-ACK for the same UE, even if different PUCCHs do not overlap in time, they are still considered to be in conflict. The PUCCH resources are indicated in the "PUCCH Resource Indicator" (PRI) field in the DL grant. Each DL grant may indicate different PUCCH resources, but the UE will follow the PRI indicated in the last PDSCH in the PUCCH multiplexing window, because the UE only knows the total number of HARQ-ACK bits after receiving the last PDSCH.
[0077] exist Figure 5 This example is shown in Figure 4 , where DCI#1 and DCI#2 indicate PUCCH#1 for HARQ-ACK corresponding to PDSCH#1 and PDSCH#2, but DCI#3 indicates PUCCH#2 for HARQ-ACK corresponding to PDSCH#3, as shown by arrows 212, 216, and 218. Here, PUCCH#1 and PUCCH#2 do not overlap in time. Since DCI#3 schedules the last PDSCH, i.e., PDSCH#3, in the multiplexing window, the UE uses PUCCH#2 to carry HARQ-ACK for PDSCH#1, PDSCH#2, and PDSCH#3, as shown by arrows 208, 210, and 212. It should be noted here that if PUCCHs carrying other UCIs (such as SR (scheduling request)) do not overlap in time, they can be transmitted separately to the PUCCH carrying HARQ-ACK in the same time slot.
[0078] Subslot PUCCH has been introduced for eURLLC to carry HARQ-ACK for URLLC PDSCH. Subslot-based PUCCH allows more than one PUCCH carrying HARQ-ACK to be transmitted within a slot. This provides more opportunities for PUCCH carrying HARQ-ACK for PDSCH to be transmitted within a slot, thereby reducing the delay of HARQ-ACK feedback. In subslot-based PUCCH, the granularity of the K1 parameter (i.e., the time difference between the end of the PDSCH and the start of its corresponding PUCCH) is in units of subslots instead of slots, where the subslot size can be two symbols or seven symbols.
[0079] Figure 6 An example of this is shown in Figure 4 and 5, where the subslot size is equal to seven symbols (i.e., half a slot), and the subslots are labeled m, m+1, m+2, etc. PDSCH#1 is transmitted in slot n+1, but for the subslot-based HARQ-ACK PUCCH, it is considered to be transmitted in subslot m+2, and here K1=6, which means that the corresponding HARQ-ACK is in subslot m+2+K1=m+8. PDSCH#2 is transmitted in slot n+2, but occupies subslots m+4 and m+5. The reference for K1 is relative to the subslot at which the PDSCH ends, and in this case, PDSCH#2 ends in subslot m+5. The DL grant in DCI#2 that schedules PDSCH#2 indicates K1=4, which schedules PUCCH for its HARQ-ACK in subslot m+5+K1=subslot m+9.
[0080] Semi-persistent scheduling (SPS)
[0081] As is well known to those skilled in the art, the gNB uses PDSCH for downlink data transmission to the UE. The PDSCH resources used for PDSCH transmission can be dynamically scheduled by the gNB or through the allocation of semi-persistent scheduling (SPS) resources.
[0082] Similarly, the use of SPS in the downlink reduces latency, particularly for regular and periodic traffic, for the use of configured grants (CGs) in the uplink. The gNB is required to explicitly activate and deactivate SPS resources when it determines that they may be needed. These SPS resources are typically configured via radio resource control (RRC) signaling and occur periodically with each SPS PDSCH opportunity having a preconfigured and fixed duration. This allows the gNB to schedule traffic with a known periodicity and packet size. The gNB may or may not transmit any PDSCH in any given SPS PDSCH opportunity and therefore requires the UE to monitor each SPS PDSCH opportunity for potential PDSCH transmissions.
[0083] In some implementations, the UE may be configured with only one SPS PDSCH, and the SPS PDSCH is activated using an activation DCI (format 1_0 or 1_1) with a cyclic redundancy code (CRC) scrambled with the configured scheduling radio network temporary identifier (CS-RNTI). Once the SPS PDSCH is activated, the UE will monitor the potential PDSCH in each SPS PDSCH opportunity configured by the SPS PDSCH without any DL grant until the SPS PDSCH is deactivated. The deactivation of the SPS PDSCH is indicated via a deactivation DCI scrambled with the CS-RNTI. The UE provides HARQ-ACK feedback for the deactivation DCI, but does not provide HARQ-ACK feedback for the activation DCI.
[0084] Similar to DG-PDSCH, the timeslot containing PUCCH resources for HARQ-ACK corresponding to SPS PDSCH is indicated using the K1 value in the field "PDSCH to HARQ_Feedback Timing Indicator" of the activation DCI. Since dynamic grants are not used for SPS PDSCH, this K1 value is applied to each SPS PDSCH opportunity and is only updated after it has been deactivated and reactivated using another activation DCI with a different K1 value.
[0085] Since there is only one SPS PDSCH, PUCCH format 0 or 1 is used to carry HARQ-ACK feedback. If the PUCCH collides with the PUCCH carrying HARQ-ACK feedback for the DG-PDSCH, the HARQ-ACK of the SPS PDSCH is multiplexed into the PUCCH corresponding to the DG-PDSCH.
[0086] In a more recent implementation, the UE may be configured with up to eight SPS PDSCHs, each of which has an RRC-configured SPS configuration index. Each SPS PDSCH is activated individually by a DCI (format 1_0, 1_1, 1_2) with a CRC scrambled with a CS-RNTI, where the DCI indicates the SPS configuration index of the SPS PDSCH to be activated. However, a single deactivation DCI may be used to deactivate multiple SPS PDSCHs. Similar to older implementations, the UE provides HARQ-ACK feedback for the deactivation DCI, but does not provide feedback for the activation DCI.
[0087] The slot or subslot containing the PUCCH resources for HARQ-ACK feedback corresponding to the SPS PDSCH opportunity is determined using the K1 value indicated in the activation DCI.Because each SPS PDSCH configuration is activated separately, different SPS PDSCHs may be indicated with different K1 values.
[0088] Since different K1 values can be used for different SPS PDSCH configurations, HARQ-ACKs for multiple SPS PDSCHs may point to the same time slot or sub-time slot, and in such a case, these HARQ-ACKs are multiplexed into a single PUCCH. For multiple SPS PDSCH configurations, PUCCH formats 2, 3, and 4 (in addition to PUCCH formats 0 and 1) can be used to carry multiple HARQ-ACKs for SPS PDSCH. Here, the HARQ-ACKs in the PUCCH are sorted in ascending order according to the DL time slots used for each SPS PDSCH configuration index, and then sorted in ascending order of the SPS PDSCH configuration index. It should be noted here that because the K1 value is usually fixed per SPS PDSCH, two or more SPS PDSCHs with the same index cannot be multiplexed into the PUCCH.
[0089] exist Figure 7 An example of this situation is shown in FIG, where the UE is configured with three SPS PDSCHs labeled SPS#1, SPS#2, and SPS#3 with different periods, which are configured by RRC with SPS configuration indices 1, 2, and 3, respectively. SPS#1, SPS#2, and SPS#3 are activated with K1=3, K1=4, and K1=1, respectively. These K1 values result in the PUCCHs for HARQ-ACK feedback corresponding to SPS#2 in slot n, SPS#1 in slot n+1, and SPS#3 in slot n+3 being in the same slot, i.e., carried by PUCCH#2 in slot n+4, as shown by arrows 262, 264, 266, 268. Therefore, PUCCH#2 provides 3 HARQ-ACKs labeled {ACK#1, ACK#2, ACK#3} to SPS#1, SPS#2 and SPS#3 respectively according to its SPS PDSCH configuration index (it can be seen that in this example, there is only one unique SPS PDSCH with HARQ-ACK multiplexed into PUCCH#2 per DL time slot).
[0090] In some implementations, when the PUCCH for the SPS PDSCH collides with the PUCCH for the DG-PDSCH, their HARQ-ACKs are multiplexed, where the SPS PDSCH HARQ-ACKs are appended to those for the DG-PDSCH if they have the same priority. Otherwise, one of the PUCCHs is prioritized.
[0091] Extended Reality (XR) and Cloud Gaming
[0092] Extended Reality (XR) refers to different types of augmented, virtual and hybrid environments and use cases where human-to-machine and human-to-human communications are performed with the assistance of handheld and wearable end-user devices (UE). Cloud gaming is another feature where game support is distributed across the network. XR and cloud gaming are considered important for NR Rel-18 and above (also known as Advanced 5G). Therefore, a Rel-18 study item on XR has been approved in 3GPP [5] to study potential enhancements to traditional 5G systems for supporting XR traffic.
[0093] XR traffic is rich in video, especially in the downlink, with a typical frame rate of 60 Hz [2], which results in data transmission with non-integer periodicity in NR, i.e., the period of the data transmission frame is not an integer number of subframes, in this example, the period is 16.67 ms. However, SPS uses integer periodicity (e.g., in 1 ms increments), and therefore there is a difference between the PDSCH arrival time and the start of the nearest SPS. This difference (or delay) is denoted as Δ SPS-XR And it will increase with each SPS, such as Figure 8 Specifically, since the period of XR packet arrival is P XR = 16.667ms, and since SPS uses integer cycles, configure P SPS = 17 ms SPS period. At time t0, an activation DCI (A-DCI) is transmitted to the UE to activate SPS, and for the first SPS opportunity, the PDSCH packet arrives matching (ie, identical to) the start of the SPS PDSCH, ie, Δ SPS-XR = 0. In the second SPS opportunity, the PDSCH packet arrives at time t4, and the SPS PDSCH starts at time t5, and therefore there is Δ SPS-XR =17ms-16.667ms=0.333ms delay. The third SPS opportunity at time t8 and time t 11 In the fourth SPS opportunity, the delay Δ SPS-XR Increased to 0.6667ms, delay Δ SPS-XR =1 ms. In other words, the timing of PDSCH and SPS opportunities is off for the entire time slot.
[0094] Furthermore, packets destined for the UE may experience random jitter arriving at the gNB due to varying frame coding delays and network delivery times. Fig. 9The frame rate and jitter of the DL traffic are shown in FIG. 302. The packet arrival times 302 may be subject to jitter, whereby, as examples, the probability distribution is a normal or Gaussian distribution, a Poisson distribution, or another such suitable distribution. The non-integer and jittery nature of XR traffic is referred to as quasi-periodic traffic. In conventional 5G systems, traffic with a known period and packet size (e.g., voice) is typically supported using a semi-persistently scheduled (SPS) PDSCH and a configured grant PUSCH (CG-PUSCH). Fig. 9 As shown, the packet size 301 of XR traffic may also not be constant and may similarly follow a probability distribution. This will be discussed in more detail later.
[0095] Although the packet arrival of packets for some services (e.g., XR services) may be periodic, the actual arrival time of the packets may experience jitter, causing them to be within the jitter time window T Jitter Arrived randomly within. Fig.10 An example is shown in FIG. 1 , where an XR application transmits data over a certain bandwidth, generating data packets as packets with a period P App periodic flow. Fig. 9 A representation of data transmission on a PDSCH resource scheduled as an SPS resource is provided, wherein in two exemplary jitter time windows T Jitter 128, each of the four boxes 262 is represented by a simplified representation of Figures 4 to 7 However, this traffic is subject to jitter, so the actual packet arrivals fall into the time window T Jitter In this example, the first jitter time window starts at time t0, where a packet can arrive within this time window between time t0 and t4, and the packet arrives at time t1. The next packet arrives later at time P App After that, the packet arrives, starting at time t5, and here again the packet can arrive at any time within the jitter time window between t5 and t9. In the second example, the packet arrives at time t8, which is towards the jitter time window T Jitter as shown in shaded box 402.
[0096] The SPS configuration provides the UE with PDSCH resources with a deterministic periodicity, which can be 1 to 640 time slots. It can be appreciated that such a deterministic periodicity configuration is not suitable for traffic that is subject to jitter. In one example, in order to handle jitter and enable data to be reliably received by the UE, multiple SPS configurations are used, where each SPS configuration can be activated with a different start offset, i.e., a different K0, as indicated in the DCI field "Time Domain Resource Allocation" (TDRA). That is, the SPS resources can be over-configured to support jitter. Fig. 9In the example of FIG. 1 , the UE may be configured with 4 SPS PDSCH configurations, so that the 4 SPSs fall within the jitter time window and each has a P APP cycle. Fig.11 For the sake of brevity, only Fig.10 and 11 In this figure, the UE configuration is marked as having a period P App , but with different offsets of #1, #2, #3 and #4. Therefore, by configuring multiple SPS resources, whenever packet data arrives within the jitter time window, the UE can be provided with PDSCH resources. As will be understood from consideration of the two figures, the transmission of data in each figure occurs in SPS #2 in the first jitter window 128, and in SPS #4 in the second jitter window 130. However, this is not a restriction on the SPS resources in which the PDSCH can be transmitted, and data can be transmitted in any resource, as governed by the probability distribution.
[0097] Transport block size
[0098] Another characteristic of XR traffic is that the amount of application data arriving at a UE in a given time period is not constant. Instead, the amount of application data included in a PDSCH transmission may vary, for example, within a given range. As such, a PDSCH transmission for XR traffic may have a non-fixed transport block size (TBS). Fig.12 An example is shown in FIG. 1 , where the XR traffic has P XR At the first SPS timing, application data uses PDSCH with TBS=100 bits, at the second SPS timing, application data uses PDSCH with TBS=300 bits, and at the third SPS timing, application data uses PDSCH with TBS=200 bits. However, generally for a given SPS configuration, the TBS used for PDSCH is fixed.
[0099] Fig.13 A conventional approach for managing variable application data volumes is shown, where SPS resources are over-configured. For example, to support non-fixed application data sizes for PDSCH, an SPS instance may be activated with a large TBS for PDSCH to ensure that the maximum packet size can be carried. For smaller packet sizes, the PDSCH is padded (e.g., with zeros) to ensure that the total TBS for each PDSCH is the same. For example, if the maximum TBS is 300 bits, the gNB may activate an SPS with a configuration of TBS = 300 bits for the PDSCH, such as Fig.13As shown. At the first SPS opportunity, the application data requires TBS=100 bits, but since SPS is activated with PDSCH TBS=300 bits, 200 bits of padding are added to the PDSCH. At the second SPS opportunity, the application data requires TBS=300 bits, and no padding bits are needed here. At the third SPS opportunity, the application data requires TBS=200 bits, and therefore 100 bits of padding are required. While this allows variable packet sizes across SPS opportunities, this approach involves over-configuration of SPS resources and is therefore inefficient.
[0100] Another method to support XR traffic with changed application data size is to deactivate the SPS instance and reactivate it with different parameters (e.g., MCS (Modulation and Coding Scheme), FDRA (Frequency Resource), and TDRA (Time Resource)) so that it provides the required TBS to carry the application data. Fig.14 Error! Reference source not found is shown in Figure 1, where at time t0, an activation DCI (A-DCI) is transmitted to the UE, which uses PDSCH TBS = 100 bits to activate SPS. After transmitting PDSCH at the first SPS opportunity, the gNB transmits a deactivation DCI (D-DCI) to deactivate SPS, followed by an activation DCI to reactivate SPS with PDSCH TBS = 300 bits, thereby carrying the added application data at the second SPS opportunity. At time t 10 , transmit another deactivation DCI to deactivate SPS again, followed by 12 The activation DCI of the PDSCH TBS of the third SPS opportunity is changed to TBS=200 bits. This implementation consumes high DCI overhead because each change requires deactivation DCI and activation DCI. If the PDSCH TBS needs to change very frequently, the DCI overhead may be higher than using a dynamically granted PDSCH (i.e., where each PDSCH is scheduled individually and dynamically).
[0101] Recognizing these limitations in conventional SPS implementations, the inventors have discovered improved implementations of SPS PDSCH transmissions (eg, XR traffic) that address at least some of these shortcomings.
[0102] Update DCI
[0103] Embodiments of the present disclosure involve the introduction of Update-DCI (U-DCI) to update one or more parameters for one or more SPS instances. That is, U-DCI may be transmitted by the gNB to the UE to update the configuration of the SPS instance for one or more occasions of the SPS instance. This is achieved without sending D-DCI to the UE. This is in contrast to traditional SPS implementations, in which, in order to change SPS parameters (e.g., MCS or TBS), the gNB needs to deactivate SPS (using D-DCI) and then reactivate SPS again using different parameters in A-DCI (see, e.g., Fig.14 ). The following implementation describes the transmission of the updated DCI.
[0104] In one example, U-DCI is embedded in the PDSCH of SPS. That is, DCI bits are transmitted using PDSCH during SPS opportunities. Fig.15 An example is shown in FIG, where at time t0, A-DCI 1510 activates SPS with PDSCH TBS=100 bits. At time t2, at the first SPS opportunity, PDSCH 1520A is transmitted with TBS=100 bits. At time t8, at the second SPS opportunity, application data requires TBS=300 bits, and according to the example, embedded U-DCI 1530A is transmitted with PDSCH 1520B at the second SPS opportunity, indicating that the TBS of PDSCH has changed to 300 bits. At the third SPS opportunity, PDSCH 1520C is transmitted with embedded U-DCI 1530B indicating that the PDSCH TBS has changed to 200 bits.
[0105] and Fig.13 Compared with the traditional method, this implementation does not need to over-configure PDSCH TBS and use padding bits, thereby saving resources. Fig.14 Compared with the traditional method in , this example also has significantly less PDCCH overhead Error! Reference source not found.
[0106] There are many ways to include U-DCI in PDSCH. For example, U-DCI and application data in PDCSH can be encoded differently. For example, the control information in U-DCI can be encoded using Polar coding or Reed-Muller coding, and the application data for PDSCH can be encoded using low-density parity check (LDPC). In another example, the application data in U-DCI and PDCSH can be encoded with different coding rates. In another example, U-DCI and application data in PDSCH are modulated separately. For example, U-DCI can be modulated with BPSK or QPSK, and the application data of PDSCH can be modulated with a higher modulation scheme (e.g., 16, 64 or 256QAM). In other words, U-DCI can be modulated using a lower-order modulation scheme, and the application data for PDSCH can be modulated using a higher-order modulation scheme. Lower-order modulation schemes are more robust than higher-order modulation schemes, and U-DCI requires high reliability to ensure that subsequent downlink transmissions can be correctly decoded.
[0107] In some examples, the U-DCI may be mapped to a specific location within the PDSCH. For example, the U-DCI may be mapped to a specific orthogonal frequency division multiplexing (OFDM) symbol of the PDSCH. Fig.16A An example of this arrangement is shown. Fig.16A , an OFDM symbol including U-DCI 1630 (e.g., a U-DCI modulation symbol) is mapped to an OFDM symbol earlier than a symbol of application data 1620 for PDSCH. PDSCH starts from the second OFDM symbol and has a duration of 11 OFDM symbols, wherein the first OFDM symbol of PDSCH (i.e., the second OFDM symbol of the time slot) contains a demodulation reference signal (DMRS) 1640. The second OFDM symbol of PDSCH (i.e., the third OFDM symbol of the time slot) includes U-DCI 1630, which is mapped first according to this example. It should be understood that U-DCI 1630 does not need to occupy the entire OFDM symbol, i.e., does not need to occupy all physical resource blocks (PRBs) allocated to PDSCH on the OFDM symbol, but may occupy a predetermined set of PRBs.
[0108] The benefit of this example is that the UE can first decode the U-DCI 1630 to determine the PDSCH parameters such as TBS, i.e., the MCS, frequency and time resources used for the PDSCH. That is, once the U-DCI 1630 is decoded, the UE can start decoding the rest of the PDSCH. When decoding the PDSCH, in some examples, the UE can avoid the U-DCI 1630 resource elements (REs), i.e., the REs containing the U-DCI 1630 are not part of the application data 1620 in the rest of the PDSCH. In addition, the UE can use the U-DCI 1630 as an additional reference signal to improve its channel estimation.
[0109] In another example, U-DCI 1630 may be mapped to known (ie, pre-configured) frequency and time resources (ie, OFDM symbols and RBs) of an SPS opportunity, such as Fig. 16B This recognizes that without reading the U-DCI 1630, the UE may not know the frequency and time resources of the PDSCH, and therefore by fixing the U-DCI 1630 position at each SPS opportunity, the UE knows where to decode the U-DCI 1630. For example, in Fig. 16B , the frequency resources are fixed to X RBs at each SPS opportunity after SPS is activated, and always start at the second OFDM symbol. The first OFDM symbol of PDSCH contains DMRS, and according to this example, the second OFDM symbol of PDSCH always contains U-DCI 1630, thereby fixing the frequency and time resources of U-DCI 1630. However, it should be understood that U-DCI 1630 does not necessarily need to be located in the second OFDM symbol, but can be configured to always be located in essentially any OFDM symbol. For example, if the PDSCH has a minimum duration of 5 OFDM symbols, U-DCI 1630 can always be mapped to any one of OFDM symbols 2-5. In addition, the total number of OFDM symbols of PDSCH can be changed to suit the required TBS. For example, in Fig. 16B In the example, at the first SPS time, the PDSCH occupies 11 OFDM symbols, of which the last 9 OFDM symbols carry 300 information bits, and at the second SPS time, the PDSCH includes 5 OFDM symbols, of which the last 3 OFDM symbols carry 100 information bits. In this example, the U-DCI 1630 indicates a change in the number of OFDM symbols (i.e., size) of the PDSCH.
[0110] In another example, U-DCI is distributed over known frequency and time resources, ie, resource elements (REs), at SPS opportunities. Allocating U-DCI provides some diversity gain for the U-DCI data. Fig. 16CAn example Error! Reference source not found is shown, in which U-DCI 1631 is distributed over X RBs and 4 OFDM symbols of the PDSCH. At the first SPS opportunity, the UE will extract the distributed U-DCI 1631, and after decoding, the UE knows that the PDSCH has TBS=300 bits and occupies 11 OFDM symbols. At the second SPS opportunity, the UE extracts U-DCI 1631 from the same frequency and time position in the time slot, and after decoding U-DCI 1631, the UE determines that the PDSCH is 5 OFDM symbols long. In this example, the minimum duration of the PDSCH is 5 OFDM symbols, so U-DCI 1631 is distributed only over the minimum number of OFDM symbols (ie, OFDM symbols 2-5), which is independent of the size of the PDSCH. In addition, U-DCI 1631 may have a fixed number (X) of RBs to ensure that the REs within these resources are mapped to U-DCI 1631. The distribution of U-DCI 1631 may be known in advance and provided to the UE (eg, via RRC signaling, or may be provided in an activation DCI, or defined in the specification).
[0111] In another example, the PDSCH may include an indicator 1650 indicating whether the U-DCI 1635 is present. The indicator 1650 may be a reserved allocation for the PDSCH having a resource size that is typically much smaller than the U-DCI 1635, and may be part of the U-DCI or a separate resource, such as Fig.16D As shown. For example, indicator 1650 can be an RE within U-DCI 1635, or generally within the entire PDSCH time slot. In some examples, indicator 1650 can be represented as one bit. In such an example, if the bit has a value of 1, this can indicate that there are some resources allocated for U-DCI 1635. If the bit has a value of 0, this can indicate that there is no U-DCI 1635 at this particular SPS opportunity, and in some cases, U-DCI 1635 resources can be allocated for application data within the PDSCH.
[0112] Configuration information (eg, location, format, coding, modulation) for the U-DCI may be configured (ie, provided to the UE) via RRC signaling, or may be included within an activation DCI for an SPS instance.
[0113] In some examples, the U-DCI may indicate that an additional PDSCH transmission is expected at a specific time after the SPS opportunity. Thus, the UE may monitor the additional PDSCH transmission, which may fall outside the SPS opportunity. In such an example, the PDSCH within the SPS opportunity may follow the parameters set in the U-DCI. The parameters of the additional PDSCH indicated by the U-DCI (e.g., the time, frequency, and TBS of the PDSCH) may be predetermined, that is, the additional PDSCH may have a different TBS from the PDSCH in the SPS opportunity. For example, the PDSCH parameters of the additional PDSCH may be configured via RRC signaling, or the PDSCH parameters of the additional PDSCH may be the same as the current SPS opportunity. In other words, the TBS may be the same as the current SPS opportunity, but the start time of the additional PDSCH may be at a known offset from the SPS opportunity. Alternatively, the start time of the additional PDSCH may be indicated by the U-DCI. Fig.17A An example of this is shown in , where at time t0, A-DCI 1710 is transmitted to the UE to activate SPS#1 and the first SPS opportunity of SPS#1 starts at time t2, where a first PDSCH 1720A is transmitted. At the second opportunity of SPS#1 at time t4, a second PDSCH 1720B is transmitted, which includes a U-DCI 1730 indicating the parameters of SPS#1, and according to this example, it also indicates an additional PDSCH 1721 to start at time t6.
[0114] In another example, the U-DCI may indicate that the PDSCH application data of the current SPS opportunity is delayed, for example, delayed by X. Delay time slots. Delay May be configurable by RRC signaling indicated in an activation DCI, indicated in a U-DCI, or may be predetermined (ie fixed in the specification).This example facilitates mitigation of jitter (discussed above) and non-integer periodicity associated with XR traffic. Fig. 17B An example of such an arrangement is shown in FIG, where the XR traffic is subjected to a jitter window T Jitter =4ms jitter. At time t0, A-DCI 1710 is sent to the UE to activate SPS#1 starting at time t2. The first SPS opportunity of SPS#1 at time t2 includes PDSCH 1720A, and the UE decodes the PDSCH. At the second SPS opportunity at time t5, the PDSCH arrives 2ms later due to jitter. According to this example, U-DCI 1730 is transmitted at time t5 and may indicate a value X Delay=2ms, indicating that the current SPS#1 opportunity does not contain application data (i.e., the payload of the PDSCH at t5 includes only U-DCI) and that the PDSCH 1720B containing application data is delayed by 2ms to time t7. The UE also knows that it has not received the application data, but this is expected at a later time, and therefore the UE refrains from transmitting a NACK. For other purposes / other UEs, the gNB may allocate unused PDSCH allocations at SPS#1 opportunities. Therefore, high resource utilization can be maintained.
[0115] In a similar example, the delayed SPS opportunity may be further delayed by a subsequent U-DCI. Fig. 17C An example is shown in FIG. 1 , where X Delay = 1 time slot (or 1 ms), and XR traffic suffers from T Jitter =4ms jitter. At time t0, A-DCI 1710 is sent to the UE to activate SPS #1, where the first SPS opportunity of SPS #1 starts at time t2 and may include PDSCH 1720A. At the second SPS opportunity at time t5, the application data of the PDSCH is delayed due to jitter, however, U-DCI 1731A indicating that the application data of the PDSCH is delayed is transmitted to the UE. When U-DCI 1731A is transmitted at t5, the gNB may not know when the application data will be transmitted at that time, and therefore the second SPS opportunity may be delayed by only a single timeslot to start at time t6. At time t6, the application data may still not have been transmitted, and therefore, another U-DCI 1731B may be transmitted by the gNB, which delays the second SPS opportunity by another timeslot to t7. At time t7, PDSCH 1720C including application data arrives and is transmitted in the delayed SPS opportunity for SPS #1, wherein the delayed PDSCH 1720C may optionally include U-DCI 1731C. In other words, U-DCI 1731A, 1731B are present in the initially scheduled SPS opportunity (which does not include application data) and the delayed SPS opportunity (including application data). This is useful for situations where the actual arrival of application data for PDSCH 1720C is unknown at the SPS opportunity.
[0116] Although the above examples of U-DCI indicate that PDSCH is delayed or additional PDSCH is expected (e.g., Fig.17A , 17B and 17C) are described with respect to U-DCI embedded within PDCSH, it should be understood that these techniques are also applicable to other U-DCI implementations, such as those described below.
[0117] Instead of being embedded within the PDSCH, the U-DCI may instead be carried by the PDCCH sent prior to the PDSCH. Fig.18 An example is shown in FIG. 1 , where SPS is activated at time t0 using activation DCI (A-DCI) 1810 with PDSCH TBS=100 bits. PDSCH 1820A with TBS=100 bits may then be transmitted at time t2. At time t6, PDSCH 1820B indicating SPS is transmitted to the UE with the TBS changed to 300 bits of U-DCI 1830A. Similarly, at time t 12 , another U-DCI 1830B may be transmitted to indicate another change of the PDSCH 1820V TBS of the SPS to 200 bits. The method may also be applied to multiple UEs, where the U-DCI may be a group common DCI (GC-DCI) carried by the PDCCH, where the GC-DCI addresses multiple UEs in one DCI. The update in the GC-DCI may then be applied to the next SPS of each UE.
[0118] When the gNB is configured to transmit U-DCI 1830 in the PDCCH, the gNB does not need to transmit U-DCI 1830 before each SPS opportunity if there is no change to the PDSCH. However, the UE must monitor each PDCCH search space configured with U-DCI 1830. For example, U-DCI 1830 may be transmitted before the scheduled SPS opportunity (or at reference time T ref Before) and in the time window T win Inside T offset is transmitted in a predetermined position, such as Fig.19 As shown. The UE may expect to receive U-DCI 1830 in the given time window. If U-DCI 1830 is not received in the time window, the UE may determine that there is no update for the upcoming SPS opportunity and instead assume a specific configuration (e.g., a previous configuration or a default configuration). In some examples, T offset Can be configured to be larger than the expected negative jitter of XR traffic arriving.
[0119] In some examples, the parameters in the U-DCI are used for a specific number of SPS opportunities, e.g., the next X SPS SPS timing, or until another U-DCI is sent, whichever comes first. SPS After the SPS opportunity and if there are no further U-DCI transmissions, the SPS reverts to the original parameters from the A-DCI. Fig. 20AAn example is shown where A-DCI activates SPS at time t0 using PDSCH TBS=200 bits. The first SPS opportunity at time t2 has PDSCH TBS=200 bits following the A-DCI parameters. The second SPS opportunity also follows the A-DCI parameters and has PDSCH TBS=200 bits. At time t6, U-DCI updates the PDSCH TBS for SPS to 300 bits, and in this example X SPS =3. According to this embodiment, the following three SPS opportunities (i.e., time t8, t 10 and t 12 The third, fourth and fifth SPS opportunities of t have PDSCH TBS=300 bits respectively. 14 At the sixth SPS opportunity, the PDSCH TBS is restored to 200 bits following the A-DCI parameters. This is particularly beneficial if a brief rise in business traffic is expected.
[0120] Fig. 20B Another example is shown in FIG. 1 , where at time t0, A-DCI once again uses PDSCH TBS=200 bits to activate SPS. At time t6, U-DCI updates SPS PDSCH TBS to 300 bits, where X SPS =2, that is, the following two SPS opportunities (i.e., at time t8 and t 12 The third and fourth SPS opportunities of the same period will use PDSCH TBS = 300 bits respectively). However, before the fourth SPS opportunity begins, at time t 10 , transmit another U-DCI to the UE, which updates the SPS PDSCH TBS to 100 bits. SPS The counter is reset and at time t 12 and t 14 The fourth and fifth SPS opportunities of the U-DCI will use PDSCH TBS = 100 bits respectively. SPS After the SPS opportunity, at time t 16 At the sixth SPS opportunity, the SPS is restored to the original A-DCI parameters, that is, the PDSCH TBS is restored to 200 bits.
[0121] In some implementations, X SPS It can be 1 so that the updated PDSCH parameters are only applicable to one SPS opportunity. SPS May be infinite (e.g., indicated by a value of 0 in U-DCI), so that the updated PDSCH parameters are applicable until another U-DCI update parameter or SPS is deactivated. Parameter X SPSIt can be RRC configured for each SPS configuration or for several SPS configurations, indicated in the activation DCI, indicated in the U-DCI, or defined in the specification. Fig. 20A and 20B The examples discussed (i.e., applying U-DCI to a set number of SPS opportunities) are shown in the context of U-DCI transmitted separately from the PDSCH (as PDCCH), but these examples are equally applicable to other U-DCI implementations discussed above (e.g., embedded U-DCI) and below.
[0122] Since the PDCCH-based U-DCI is transmitted before the start of the SPS PDSCH, the start offset of the SPS instance can be changed in addition to the TBS of the PDSCH. The U-DCI can indicate a different time domain resource allocation (TDRA) index with an earlier or later K0 value, which is beneficial for XR traffic with non-integer periodicity. Fig.21 An example is shown in FIG. 1 , where the XR cycle is P XR =16.667ms (60Hz). At time t0, with a period P SPS = 17 ms SPS is activated by A-DCI 2010, and the first SPS opportunity 2040A occurs at time t2, which matches the arrival of PDSCH 2020A carrying XR traffic. At the second SPS opportunity 2040B and the third SPS opportunity 2040C at time t5 and t8, respectively, the delay Δ SPS-XR and the SPS used to transmit them increases, i.e., Δ SPS-XR = 0.333 ms and 0.667 ms (in the second SPS opportunity 2040B and the third SPS opportunity 2040C, respectively). Before the expected arrival of the fourth PDSCH 2020D carrying XR traffic, at time t 10 The U-DCI 2030 is transmitted to the UE, wherein the U-DCI 2030 indicates a new start offset of the SPS, so that the upcoming SPS, that is, the fourth SPS opportunity 2040D is offset 1 ms earlier in time. Therefore, the fourth SPS opportunity 2040D is at time t 12 Starting 1 ms earlier, this matches the arrival of PDSCH 2020D carrying XR traffic. If U-DCI 2030 is not used, the fourth SPS opportunity 2040D will instead be at time t 13 This will lead to Δ SPS-XR =1ms.
[0123] In some examples, when the UE successfully receives the U-DCI, the UE feeds back a HARQ-ACK so that the gNB knows that the UE has received the U-DCI. This ensures that the UE receives updated parameters, because if the UE fails to receive the U-DCI, the UE may continuously fail to decode the parameters for X. SPS PDSCH of SPS opportunity. HARQ-ACK can be transmitted in PUCCH, for example.
[0124] As an alternative to embedding U-DCI in PDSCH or transmitting U-DCI as PDCCH, U-DCI may be transmitted via a demodulation reference signal (DMRS) for PDSCH. Specifically, each SPS instance may be configured with two or more DMRSs, where each DMRS indicates a parameter set for PDSCH transmission. Fig. 22 An example is shown in which an SPS instance is configured with two different DMRS 2230 at different SPS opportunities, namely, DMRS #1 2230A and DMRS #2 2230B. DMRS #1 2230A indicates a set of predefined parameters that give PDSCH 2220A TBS=300 bits, while DMRS #2 2230B indicates another set of parameters that give PDSCH 2220BTBS=100 bits. In this example, DMRS 2230 is transmitted in the first OFDM symbol of PDSCH 2220, which allows the UE to determine the parameters for decoding PDSCH 2220. At the first SPS opportunity, DMRS #1 2230A is used, and therefore the corresponding PDSCH 2220A has TBS=300 bits, while at the second SPS opportunity, DMRS #2 2230B is used, which indicates that PDSCH 2220B TBS=100 bits. In other words, the UE may determine a specific set of parameters to use for SPS based on a lookup based on the specific DMRS 2230 being used.
[0125] It should be understood that although Fig. 22 The example in shows only two DMRS, but this example is not limited to 2 DMRS and each SPS instance can be configured with more than 2 DMRS. In addition, a default DMRS can be defined for each SPS instance so that the default DMRS can be used for at least the first SPS opportunity after the SPS instance is activated using the activation DCI. In addition, although specific examples are discussed with respect to a single U-DCI implementation (e.g., embedded in PDSCH, transmitted via PDCCH, or indicated by DMRS). It should be recognized that all examples discussed herein can be used regardless of the specific U-DCI implementation.
[0126] In addition, the precise format of U-DCI can take many different forms. For example, U-DCI may have the same format as Activation DCI (A-DCI). In particular, the A-DCI format includes the parameters required to change the TBS (i.e., by changing the MCS, TDRA, and FDRA) and the start offset (i.e., by changing the TDRA) of the SPS instance, but U-DCI can change these parameters for existing SPS instances without the deactivation of the SPS instance. In some examples, U-DCI can use a specific RNTI to distinguish U-DCI from DL authorization (e.g., for dynamic PDSCH). For example, the CRC of U-DCI can be masked with CS-RNTI. In some examples, the cyclic redundancy check (CRC) of U-DCI can be scrambled with a dedicated radio network temporary identifier (RNTI). For example, an update RNTI (U-RNTI) with a specific ID can be used specifically for U-DCI transmission.
[0127] In the current 3GPP specification, the SPS index is indicated using the HARQ process number (HPN) field in the activation and deactivation DCI transmission in combination with a new data indicator (NDI=0). That is, if a specific SPS instance with a specific SPS index has not been activated, the HPN pointing to the SPS index with NDI=0 indicates to the UE that it should activate the SPS instance with the specific SPS index. If a specific SPS instance with a specific SPS index has been activated, the HPN pointing to the SPS index with NDI=0 will indicate to the UE that it should deactivate the SPS instance. According to the example of the present disclosure, U-DCI may be different from activation DCI and deactivation DCI because U-DCI may use the HPN field to point to an activated SPS instance with a specific SPS index (with a non-zero NDI value (e.g., NDI=1)). Upon receiving a DCI with a non-zero NDI value, the UE knows to update the parameters of the activated SPS instance for the specific SPS instance according to the parameters set forth in the U-DCI. When this format is used for U-DCI, the U-DCI may use the same CS-RNTI as the activation DCI and deactivation DCI messages.
[0128] Although U-DCI may indicate all parameters of an SPS instance, a given U-DCI may change only a subset of the parameters. That is, the U-DCI may change only a subset of the parameters of an SPS instance. Thus, the U-DCI may indicate values for all parameters of an SPS instance, where the unchanged values are included in the U-DCI and are the same as the values included in the A-DCI, or the U-DCI may include only values for the changed parameters. That is, the U-DCI may only contain a subset of the information / parameters of the A-DCI. This reduces the amount of data transmitted as part of the U-DCI.
[0129] In some examples, the U-DCI may include an update index corresponding to a predefined parameter set for the SPS instance. That is, the U-DCI may include a specific update index, which the UE uses to look up the parameter set in a predefined list or table of parameter sets, and uses the parameter set corresponding to the update index for the SPS instance. Thus, the size of the U-DCI can be kept small while still providing the UE with updated parameters for the SPS instance. An example is shown in Table 1 below, where the lookup table contains 8 update indexes (i.e., only 3 bits are required in the U-DCI), and where each update index corresponds to a set of parameters (e.g., MCS, TDRA, and FDRA). The U-DCI indicates an update index, for example, update index = 4, and the UE looks up the update index in the table and applies the values of MCS = 7, 6 OFDM symbols, and 30 RBs to the SPS instance.
[0130]
[0131]
[0132] Table 1: Example lookup table for PDSCH parameters
[0133] It should be understood that parameters other than MCS, TDRA, and FDRA may be used in the lookup table. In addition, in some examples, the U-DCI may indicate an offset index, rather than an update index, which increases or decreases the value of the update index maintained by the UE. For example, if the current update index is 5 (as per Table 1), this corresponds to setting MCS=7, 12 OFDM symbols, and 30 RBs, and if the U-DCI indicates an offset index of -2, the UE reduces its update index by 2, i.e., from 5 to 3. Thus, the UE then uses the parameters corresponding to the update index 3 in Table 1, i.e., MCS=5, 10 OFDM symbols, and 20 RBs.
[0134] In some examples, a default index of the lookup table is assumed when an activation DCI is received. This recognizes that the update index may not be included in the activation DCI, and therefore the default index is assumed for the case where the U-DCI indicates an offset index. That is, the activation DCI does not need to use the parameter set included in the lookup table, and essentially any parameter may be used. Thus, if a subsequent U-DCI is received that includes an offset index, the default index may be used in order to correctly interpret the offset index. For example, the default index may be 1 (corresponding to MCS=3, 10 OFDM symbols, and 10 RBs in Table 1), but the A-DCI may activate an SPS instance with MCS=5, 7 OFDM symbols, and 15 RBs, which does not correspond to any update index in the lookup table. Thus, if the U-DCI transmission includes an offset index of 2, the UE may increase the value of its update index from a default value of 1 to a value of 3, and use the corresponding parameters of index=3 in the lookup table (MCS=5, 10 OFDM symbols, and 20 RBs in the example of Table 1). Another additional U-DCI may indicate an offset index of 1, and the UE will then use the update index in the lookup table = 3 + 1 = 4 (MCS = 7, 6 OFDM symbols and 30 RBs in the example of Table 1). That is, the default index is the starting point of the first U-DCI indication of the offset index. Indicating only the update index of the lookup table requires only a small number of bits, which may be particularly advantageous for GC-DCI based U-DCI in some cases, because the update must be sent to multiple UEs.
[0135] Fig.23 A flow chart of an exemplary method for an infrastructure device according to the present disclosure is shown. The method includes a step 2310 of transmitting an activation message, the activation message configuring the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions. The activation message indicates an initial parameter set for the downlink transmissions. The method then includes a step 2320 of transmitting an update message, wherein the update message indicates an updated parameter set for one or more downlink transmissions. The method includes another step 2330 of transmitting a downlink transmission according to the updated parameter set. Fig.24 A flow chart of an exemplary method for a communication device according to the present disclosure is shown. The method includes a step 2410 of receiving an activation message, which configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions. The activation message indicates an initial parameter set for the downlink transmissions. The method then includes a step 2420 of receiving an update message, wherein the update message indicates an updated parameter set for one or more downlink transmissions. The method also includes a step 2430 of monitoring the scheduling windows, and also includes a step 2440 of receiving a downlink transmission according to the updated parameter set.
[0136] Thus, from one perspective, methods and apparatus for updating parameters of scheduled downlink transmissions have been described. A method for an infrastructure device, comprising: transmitting an activation message (e.g., activating a DCI) to a communication device, wherein the activation message configures the communication device to monitor multiple periodic scheduling windows (e.g., multiple SPS opportunities) for downlink transmissions (e.g., PDSCH), wherein the activation message indicates an initial set of parameters (e.g., transport block size) for the downlink transmission. The method comprises: transmitting an update message to the communication device (e.g., via downlink control information), wherein the update message indicates an updated set of parameters for one or more of the downlink transmissions (without deactivating the SPS instances), and transmitting a downlink transmission to the communication device and during a scheduling window in the multiple periodic scheduling windows based on the updated set of parameters.
[0137] The following numbered clauses provide further exemplary aspects and features of the present technology:
[0138] 1. A method for an infrastructure device, the method comprising:
[0139] transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions;
[0140] transmitting an update message to the communication device, wherein the update message indicates an updated set of parameters for one or more downlink transmissions; and
[0141] A downlink transmission is transmitted to the communications device according to the updated set of parameters and during a scheduling window in a plurality of periodic scheduling windows.
[0142] 2. A method according to clause 1, wherein the update message is embedded in the payload of the downlink transmission.
[0143] 3. A method according to clause 2, wherein the update message is encoded differently as payload data of a downlink transmission.
[0144] 4. A method according to clause 2 or clause 3, wherein the update message is modulated differently as payload data for downlink transmission.
[0145] 5. A method according to any of clauses 2-4, wherein the update message is mapped to a predetermined frequency resource of the downlink transmission.
[0146] 6. A method according to any of clauses 2-5, wherein the update message is distributed across a plurality of time resources within a payload of a downlink transmission.
[0147] 7. A method according to any of clauses 2-6, wherein the update message is included at the beginning of the payload of the downlink transmission.
[0148] 8. A method according to any of clauses 2-7, wherein the downlink transmission comprises an update indicator configured to indicate the presence of an update message within the downlink transmission.
[0149] 9. The method of clause 1, wherein the update message is transmitted prior to the downlink transmission.
[0150] 10. A method according to clause 9, wherein the update message is transmitted in a control channel transmission.
[0151] 11. A method according to clause 9 or 10, wherein the updated set of parameters indicates an earlier timing for the scheduling window.
[0152] 12. A method according to any of clauses 9-11, wherein the update message is transmitted in a predetermined update window before the scheduling window.
[0153] 13. The method according to any of clauses 9-12, wherein the update message is transmitted to a plurality of communication devices.
[0154] 14. The method of clause 1, wherein the update message is included within a demodulation reference signal of the downlink transmission.
[0155] 15. A method according to any preceding clause, wherein the update message instructs the communication device to monitor for further downlink transmissions scheduled after the downlink transmission, and
[0156] Therein, the method further comprises transmitting an additional downlink transmission to the communication device.
[0157] 16. A method according to clause 15, wherein the payload of the downlink transmission comprises only the update message.
[0158] 17. A method according to any of the preceding clauses, wherein the parameter set indicates a change in one or more of:
[0159] Transport block size for downlink transmissions;
[0160] Frequency allocation for downlink transmission;
[0161] Timing of downlink transmissions; and
[0162] Modulation and / or coding rate for downlink transmissions.
[0163] 18. A method according to any preceding clause, wherein the update message indicates that the updated parameter set is applicable without limitation to subsequent downlink transmissions.
[0164] 19. A method according to any of clauses 1 to 17, wherein the update message indicates that the updated set of parameters applies to a fixed number of downlink transmissions.
[0165] 20. A method according to any preceding clause, further comprising receiving from the communication device an acknowledgement that the communication device received the update message.
[0166] 21. A method according to any of the preceding clauses, wherein the update message has the same format as the activation message.
[0167] 22. A method according to any of the preceding clauses, wherein the update message comprises a subset of the parameter set, wherein each parameter of the subset is updated in the updated parameter set.
[0168] 23. A method according to any of clauses 1-20, wherein the updated set of parameters is predetermined, and wherein the update message comprises an index corresponding to the updated set of parameters.
[0169] 24. A method according to any of clauses 1-20, wherein the update message comprises an offset value indicating a change in an index corresponding to a particular parameter set.
[0170] 25. A method according to any preceding clause, wherein a cyclic redundancy check of the update message is scrambled using a unique radio network temporary identifier.
[0171] 26. A method according to any of the preceding clauses, further comprising:
[0172] A downlink transmission is transmitted to the communication device prior to the update message and during a scheduling window in a plurality of periodic scheduling windows according to the initial set of parameters.
[0173] 27. An infrastructure device comprising:
[0174] a transceiver configured to transmit signals to and / or receive signals from a communication device via a radio interface provided by the infrastructure equipment, and
[0175] A controller, in combination with the transceiver, is configured to:
[0176] transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions;
[0177] transmitting an update message to the communication device, wherein the update DCI message indicates an updated parameter set for one or more downlink transmissions; and
[0178] A downlink transmission is transmitted to the communications device according to the updated set of parameters and during a scheduling window in a plurality of periodic scheduling windows.
[0179] 28. A circuit for communication, the circuit comprising:
[0180] transceiver circuitry configured to transmit signals to and / or receive signals from a communication device via a radio interface provided by the infrastructure equipment, and
[0181] A controller circuit, in combination with the transceiver circuit, is configured to:
[0182] transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions;
[0183] transmitting an update message to the communication device, wherein the update DCI message indicates an updated parameter set for one or more downlink transmissions; and
[0184] A downlink transmission is transmitted to the communications device according to the updated set of parameters and during a scheduling window in a plurality of periodic scheduling windows.
[0185] 29. A method for a communication device, the method comprising:
[0186] receiving an activation message from the infrastructure equipment, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions;
[0187] receiving an update message from the infrastructure device, wherein the update message indicates an updated set of parameters for one or more downlink transmissions;
[0188] monitoring a scheduling window among the plurality of periodic scheduling windows; and
[0189] A downlink transmission is received from the infrastructure device and during the scheduling window according to the updated set of parameters.
[0190] 30. A method as described in clause 29, wherein the update message is embedded within a payload of a downlink transmission.
[0191] 31. A method according to clause 30, wherein the update message is encoded differently as payload data of a downlink transmission.
[0192] 32. A method according to clause 30 or clause 31, wherein the update message is modulated differently as payload data for a downlink transmission.
[0193] 33. A method according to any of clauses 30-32, wherein the update message is mapped to predetermined frequency resources of the downlink transmission.
[0194] 34. A method according to any of clauses 30-33, wherein the update message is distributed across a plurality of time resources within a payload of a downlink transmission.
[0195] 35. A method according to any of clauses 30-34, wherein the update message is included at the beginning of a payload of the downlink transmission.
[0196] 36. A method as described in any of clauses 30-35, wherein the downlink transmission comprises an update indicator configured to indicate the presence of an update message within the downlink transmission.
[0197] 37. A method according to clause 29, wherein the update message is transmitted prior to the downlink transmission.
[0198] 38. A method according to clause 37, wherein the update message is transmitted in a control channel transmission.
[0199] 39. A method according to clause 37 or 38, wherein the updated set of parameters indicates an earlier timing for the scheduling window.
[0200] 40. A method according to any of clauses 37-39, wherein the update message is transmitted in a predetermined update window preceding the scheduling window.
[0201] 41. A method according to any of clauses 37-40, wherein the update message is transmitted to a plurality of communication devices.
[0202] 42. A method according to clause 29, wherein the update message is included within a demodulation reference signal of the downlink transmission.
[0203] 43. A method according to any of clauses 29-42, wherein the update message instructs the communication device to monitor for further downlink transmissions scheduled after the downlink transmission, and
[0204] Therein, the method further comprises transmitting an additional downlink transmission to the communication device.
[0205] 44. A method according to clause 43, wherein the payload of the downlink transmission comprises only the update message.
[0206] 45. A method according to any of clauses 29-44, wherein the parameter set indicates a change in one or more of:
[0207] Transport block size for downlink transmissions;
[0208] Frequency allocation for downlink transmission;
[0209] Timing of downlink transmissions; and
[0210] Modulation and / or coding rate for downlink transmissions.
[0211] 46. A method according to any of clauses 29-45, wherein the update message indicates that the updated set of parameters applies without qualification to subsequent downlink transmissions.
[0212] 47. A method according to any of clauses 29-46, wherein the update message indicates that the updated set of parameters applies to a fixed number of downlink transmissions.
[0213] 48. A method according to any of clauses 29-47, further comprising receiving from the communication device an acknowledgement that the communication device received the update message.
[0214] 49. A method according to any of clauses 29-48, wherein the update message has the same format as the activation message.
[0215] 50. A method according to any of clauses 29-49, wherein the update message comprises a subset of the parameter set, wherein each parameter of the subset is updated in the updated parameter set.
[0216] 51. A method according to any of clauses 29-48, wherein the updated set of parameters is predetermined, and wherein the update message comprises an index corresponding to the updated set of parameters.
[0217] 52. A method according to any of clauses 29-48, wherein the update message comprises an offset value indicating a change in an index corresponding to a particular parameter set.
[0218] 53. The method according to any one of clauses 29-52, further comprising:
[0219] A downlink transmission is transmitted to the communication device prior to the update message and during a scheduling window in a plurality of periodic scheduling windows according to the initial set of parameters.
[0220] 54. A communication device, comprising:
[0221] a transceiver configured to transmit signals to and / or receive signals from infrastructure equipment of the wireless communication network via a radio interface provided by the wireless communication network, and
[0222] A controller, in combination with the transceiver, is configured to:
[0223] receiving an activation message from the infrastructure equipment, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions;
[0224] receiving an update message from the infrastructure device, wherein the update message indicates an updated set of parameters for one or more downlink transmissions;
[0225] monitoring a scheduling window among the plurality of periodic scheduling windows; and
[0226] A downlink transmission is received from the infrastructure device and during the scheduling window according to the updated set of parameters.
[0227] 55. A circuit for a communication device, comprising:
[0228] transceiver circuitry configured to transmit signals to and / or receive signals from infrastructure equipment of the wireless communication network via a radio interface provided by the wireless communication network, and
[0229] A controller circuit, in combination with the transceiver circuit, is configured to:
[0230] receiving an activation message from the infrastructure equipment, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions;
[0231] receiving an update message from the infrastructure device, wherein the update message indicates an updated set of parameters for one or more downlink transmissions;
[0232] monitoring a scheduling window among the plurality of periodic scheduling windows; and
[0233] A downlink transmission is received from the infrastructure device and during the scheduling window according to the updated set of parameters.
[0234] It should be understood that for clarity, the above description has described the embodiments with reference to different functional units, circuits and / or processors. However, it is apparent that any suitable distribution of functions between different functional units, circuits and / or processors may be used without departing from the embodiments.
[0235] The described embodiments can be implemented in any suitable form, including hardware, software, firmware or any combination of these. The described embodiments can be optionally implemented at least in part as computer software running on one or more data processors and / or digital signal processors. The elements and components of any embodiment can be implemented physically, functionally and logically in any suitable manner. In fact, the function can be implemented in a single unit, in multiple units or as a part of other functional units. In this way, the disclosed embodiments can be implemented in a single unit, or can be physically and functionally distributed between different units, circuits and / or processors.
[0236] Although the present disclosure has been described in conjunction with some embodiments, the present disclosure is not limited to the specific forms set forth herein. In addition, although features appear to be described in conjunction with specific embodiments, those skilled in the art will recognize that the different features of the described embodiments can be combined in any manner suitable for implementing the technology.
[0237] References
[0238] [1]Holma H. and Toskala A, "LTE for UMTS OFDMA and SC-FDMA based radioaccess", John Wiley and Sons, 2009.
[0239] [2]RP-190726, "Physical layer enhancements for NR ultra-reliable and low latency communication (URLLC)", Huawei, HiSilicon, RAN#83.
[0240] [3]RP-201310, "Revised WID: Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR," Nokia, Nokia Shanghai Bell, RAN#88e.
[0241] [4] European Patent Application No. 20155210.6, “Intra-UE Multiplexing Indicator”.
[0242] [5]RP-213587, “Study on XR Enhancements for NR”,Nokia,RAN#94e
Claims
1. A method for infrastructure equipment, the method comprising: transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions; transmitting an update message to the communication device, wherein the update message indicates an updated set of parameters for one or more of the downlink transmissions; and A downlink transmission is transmitted to the communications device and during a scheduling window of the plurality of periodic scheduling windows in accordance with the updated set of parameters.
2. The method according to claim 1, wherein: The update message is embedded within a payload of the downlink transmission.
3. The method according to claim 2, wherein: The update message is differently encoded as payload data of the downlink transmission.
4. The method according to claim 2, wherein: The update message is modulated differently as payload data for the downlink transmission.
5. The method according to claim 2, wherein: The update message is mapped to a predetermined frequency resource of the downlink transmission.
6. The method according to claim 2, wherein: The update message is distributed across a plurality of time resources within a payload of the downlink transmission.
7. The method according to claim 2, wherein: The update message is included at the beginning of a payload of the downlink transmission.
8. The method according to claim 2, wherein: The downlink transmission includes an update indicator configured to indicate the presence of the update message in the downlink transmission.
9. The method according to claim 1, wherein: The update message is transmitted prior to the downlink transmission.
10. The method according to claim 9, wherein: The update message is transmitted in a control channel transmission.
11. The method according to claim 9, wherein: The updated set of parameters indicates an earlier timing for the scheduling window.
12. The method according to claim 9, wherein: The update message is transmitted in a predetermined update window prior to the scheduling window.
13. The method according to claim 9, wherein: The update message is transmitted to a plurality of communication devices.
14. The method according to claim 1, wherein: The update message is included in a demodulation reference signal of the downlink transmission.
15. The method according to claim 1, wherein: The update message instructs the communication device to monitor for a further downlink transmission scheduled after the downlink transmission, and wherein the method further comprises transmitting the further downlink transmission to the communication device.
16. The method according to claim 15, wherein: The payload of the downlink transmission includes only the update message.
17. The method according to claim 1, wherein: The parameter set indicates changes to one or more of: a transport block size for the downlink transmission; frequency allocation of said downlink transmissions; the timing of the downlink transmissions; and The modulation and / or coding rate of the downlink transmission.
18. The method according to claim 1, wherein: The update message indicates that the updated parameter set is applicable to subsequent downlink transmissions without limitation.
19. The method according to claim 1, wherein: The update message indicates that the updated parameter set is applicable to a fixed number of downlink transmissions.
20. The method of claim 1, further comprising receiving from the communication device an acknowledgement that the communication device received the update message.
21. The method according to claim 1, wherein: The update message has the same format as the activation message.
22. The method according to claim 1, wherein: The update message includes a subset of the parameter set, wherein each parameter of the subset is updated in the updated parameter set.
23. The method according to claim 1, wherein: The updated parameter set is predetermined, and wherein the update message includes an index corresponding to the updated parameter set.
24. The method according to claim 1, wherein: The update message includes an offset value indicating a change of an index corresponding to a specific parameter set.
25. The method of claim 1, wherein: A cyclic redundancy check of the update message is scrambled using the unique radio network temporary identifier.
26. The method of claim 1, further comprising: A downlink transmission is transmitted to the communication device prior to the update message and during a scheduling window of the plurality of periodic scheduling windows according to the initial set of parameters.
27. An infrastructure device comprising: a transceiver configured to transmit signals to and / or receive signals from a communication device via a radio interface provided by the infrastructure equipment, and A controller, in combination with the transceiver, is configured to: transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial parameter set for the downlink transmissions; transmitting an update message to the communication device, wherein the update DCI message indicates an updated parameter set for one or more of the downlink transmissions; and A downlink transmission is transmitted to the communications device and during a scheduling window of the plurality of periodic scheduling windows in accordance with the updated set of parameters.
28. A circuit for communication, the circuit comprising: transceiver circuitry configured to transmit signals to and / or receive signals from a communication device via a radio interface provided by the infrastructure equipment, and A controller circuit, in combination with the transceiver circuit, is configured to: transmitting an activation message to a communication device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial parameter set for the downlink transmissions; transmitting an update message to the communication device, wherein the update DCI message indicates an updated parameter set for one or more of the downlink transmissions; and A downlink transmission is transmitted to the communications device and during a scheduling window of the plurality of periodic scheduling windows in accordance with the updated set of parameters.
29. A method for a communication device, the method comprising: receiving an activation message from an infrastructure device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions; receiving an update message from the infrastructure device, wherein the update message indicates an updated set of parameters for one or more of the downlink transmissions; monitoring a scheduling window among the plurality of periodic scheduling windows; and A downlink transmission is received from the infrastructure device and during the scheduling window according to the updated set of parameters.
30. The method of claim 29, wherein: The update message is embedded within a payload of the downlink transmission.
31. The method according to claim 30, wherein: The update message is differently encoded as payload data of the downlink transmission.
32. The method of claim 30, wherein: The update message is modulated differently as payload data for the downlink transmission.
33. The method of claim 30, wherein: The update message is mapped to a predetermined frequency resource of the downlink transmission.
34. The method of claim 30, wherein: The update message is distributed across a plurality of time resources within a payload of the downlink transmission.
35. The method of claim 30, wherein: The update message is included at the beginning of a payload of the downlink transmission.
36. The method of claim 30, wherein: The downlink transmission includes an update indicator configured to indicate the presence of the update message in the downlink transmission.
37. The method of claim 29, wherein: The update message is transmitted prior to the downlink transmission.
38. The method of claim 37, wherein: The update message is transmitted in a control channel transmission.
39. The method of claim 37, wherein: The updated set of parameters indicates an earlier timing for the scheduling window.
40. The method of claim 37, wherein: The update message is transmitted in a predetermined update window prior to the scheduling window.
41. The method of claim 37, wherein: The update message is transmitted to a plurality of communication devices.
42. The method of claim 29, wherein: The update message is included in a demodulation reference signal of the downlink transmission.
43. The method of claim 29, wherein: The update message instructs the communication device to monitor for a further downlink transmission scheduled after the downlink transmission, and wherein the method further comprises transmitting the further downlink transmission to the communication device.
44. The method of claim 43, wherein: The payload of the downlink transmission includes only the update message.
45. The method of claim 29, wherein: The parameter set indicates changes to one or more of: a transport block size for the downlink transmission; frequency allocation of said downlink transmissions; the timing of the downlink transmissions; and The modulation and / or coding rate of the downlink transmission.
46. The method of claim 29, wherein: The update message indicates that the updated parameter set is applicable to subsequent downlink transmissions without limitation.
47. The method of claim 29, wherein: The update message indicates that the updated parameter set is applicable to a fixed number of downlink transmissions.
48. The method of claim 29, further comprising receiving from the communication device an acknowledgement that the communication device received the update message.
49. The method of claim 29, wherein: The update message has the same format as the activation message.
50. The method of claim 29, wherein: The update message includes a subset of the parameter set, wherein each parameter of the subset is updated in the updated parameter set.
51. The method of claim 29, wherein: The updated parameter set is predetermined, and wherein the update message includes an index corresponding to the updated parameter set.
52. The method of claim 29, wherein: The update message includes an offset value indicating a change of an index corresponding to a specific parameter set.
53. The method of claim 29, further comprising: A downlink transmission is transmitted to the communication device prior to the update message and during a scheduling window of the plurality of periodic scheduling windows according to the initial set of parameters.
54. A communication device, comprising: a transceiver configured to transmit signals to and / or receive signals from infrastructure equipment of a wireless communication network via a radio interface provided by the wireless communication network, and A controller, in combination with the transceiver, is configured to: receiving an activation message from an infrastructure device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions; receiving an update message from the infrastructure device, wherein the update message indicates an updated set of parameters for one or more of the downlink transmissions; monitoring a scheduling window among the plurality of periodic scheduling windows; and A downlink transmission is received from the infrastructure device and during the scheduling window according to the updated set of parameters.
55. A circuit for a communication device, comprising: transceiver circuitry configured to transmit signals to and / or receive signals from infrastructure equipment of a wireless communication network via a radio interface provided by the wireless communication network, and A controller circuit, in combination with the transceiver circuit, is configured to: receiving an activation message from an infrastructure device, wherein the activation message configures the communication device to monitor a plurality of periodic scheduling windows for downlink transmissions, wherein the activation message indicates an initial set of parameters for the downlink transmissions; receiving an update message from the infrastructure device, wherein the update message indicates an updated set of parameters for one or more of the downlink transmissions; monitoring a scheduling window among the plurality of periodic scheduling windows; and A downlink transmission is received from the infrastructure device and during the scheduling window according to the updated set of parameters.
Citation Information
Patent Citations
Polymeric ultraviolet light stabilisers containing hindered alkyl amines and polymer compositions containing them
EP0002022A1
