Electronic device and method in wireless communication system

Abstract

The present disclosure relates to an electronic device and a method in a wireless communication system. Provided is an electronic device on a control side in a wireless communication system, comprising a processing circuit configured to send common downlink control information (DCI) for terminal side devices in the wireless communication system, wherein the common DCI indicates at least one of the release of one or more semi-persistent schedulings (SPSs) used for each of multiple terminal side devices and the release of one or more configured grants (CGs) used for each of the multiple terminal side devices.

Description

Electronic device and method in wireless communication system

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311117790.7 filed on August 31, 2023, the entirety of which is incorporated herein by reference. Technical Field

[0003] The present disclosure relates to electronic devices and methods in a wireless communication system, and more particularly, to electronic devices and methods for providing scheduling through Downlink Control Information (DCI) in a wireless communication system. Background Art

[0004] With the development and widespread application of mobile internet technology, more and more devices are connected to mobile networks, and new services and applications are emerging. To meet people's communication needs, fifth-generation mobile communication technology (abbreviated as 5G or 5G technology) has become a hot topic of discussion and research in the communications industry and academia. Fifth-generation mobile communication technology is the latest generation of cellular mobile communication technology, with performance goals of high data rates, reduced latency, energy conservation, cost reduction, increased system capacity, and large-scale device connectivity.

[0005] Thanks to the advancement of wireless communication technology, many application scenarios are gaining increasing attention. For example, extended reality (XR) is one of the most important 5G media applications currently being researched in the industry. XR is a general term for all human-computer interactions that combine the real and the virtual, enabled by computer technology and wearable devices. It can include different types of reality, such as virtual reality (VR), augmented reality (AR), and mixed reality (MR). New services such as the Metaverse and cloud gaming also include these.

[0006] Unless otherwise indicated, it should not be assumed that any of the approaches described in this section qualify as prior art merely by virtue of their inclusion in this section. Likewise, unless otherwise indicated, it should not be assumed that problems identified with respect to one or more approaches qualify as prior art based on this section.

[0007] Summary of the Invention

[0008] The present disclosure provides an electronic device and method in a wireless communication system, which can improve the configuration of downlink control information (DCI) in the wireless communication system, and in particular can provide an enhanced scheduling solution using the improved downlink control information (DCI).

[0009] One aspect of the present disclosure relates to an electronic device on the control side of a wireless communication system, comprising a processing circuit configured to: send common downlink control information (DCI) for a terminal side device in the wireless communication system, indicating at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in a plurality of terminal side devices.

[0010] Another aspect of the present disclosure relates to a method for a control side in a wireless communication system, the method comprising: sending common downlink control information (DCI) for a terminal side device in the wireless communication system, indicating at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in a plurality of terminal side devices.

[0011] Another aspect of the present disclosure relates to an electronic device on the terminal side of a wireless communication system, including a processing circuit, which is configured to: receive common downlink control information (DCI) for multiple terminal side devices in the wireless communication system from a control side in the wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each of the multiple terminal side devices.

[0012] Another aspect of the present disclosure relates to a method for a terminal side in a wireless communication system, the method comprising: receiving common downlink control information (DCI) for multiple terminal side devices in the wireless communication system from a control side in the wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each of the multiple terminal side devices.

[0013] Yet another aspect of the present disclosure relates to a non-transitory computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, enable the processor to implement the method described herein.

[0014] Yet another aspect of the present disclosure relates to a wireless communication device. According to one embodiment, the wireless communication device includes: a processor and a storage device, wherein the storage device stores executable instructions, which, when executed by the processor, enable the processor to implement the method described herein.

[0015] Yet another aspect of the present disclosure relates to a computer program product comprising a computer program / instructions which, when executed by a processor, implement the steps of the method described herein.

[0016] Yet another aspect of the present disclosure relates to a computer program comprising program code, which, when executed by a processor, implements the steps of the method described herein.

[0017] The above summary is provided to summarize some exemplary embodiments in order to provide a basic understanding of various aspects of the subject matter described herein. Therefore, the above features are merely examples and should not be construed as narrowing the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the detailed description described below in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other objects and advantages of the present disclosure will be further described below in conjunction with specific embodiments and with reference to the accompanying drawings. In the accompanying drawings, identical or corresponding technical features or components will be represented by identical or corresponding reference numerals.

[0019] FIG1 is a simplified diagram illustrating the architecture of an NR communication system.

[0020] 2A and 2B illustrate the NR radio protocol architecture for the user plane and control plane, respectively.

[0021] Figure 3 illustrates the frame structure used in 5G NR.

[0022] FIG4 illustrates a schematic diagram of scheduling through common DCI in wireless communications according to an embodiment of the present disclosure.

[0023] FIG5A illustrates a block diagram of an electronic device on the control side in a wireless communication system according to an embodiment of the present disclosure, and FIG5B illustrates a flow chart of a method on the control side in wireless optical communication according to an embodiment of the present disclosure.

[0024] 6A and 6B illustrate configuration examples of common downlink control information (DCI) according to an embodiment of the present disclosure.

[0025] FIG7A illustrates a block diagram of an electronic device on a terminal side in a wireless communication system according to an embodiment of the present disclosure, and FIG7B illustrates a flowchart of a method on a terminal side in wireless optical communication according to an embodiment of the present disclosure.

[0026] FIG8 illustrates a schematic application diagram of common DCI in wireless communication according to an embodiment of the present disclosure.

[0027] FIG9 illustrates a schematic signaling diagram of common DCI in wireless communication according to an embodiment of the present disclosure.

[0028] FIG. 10A illustrates a schematic diagram of control resource allocation for conventional DCI scheduling, and FIG. 10B illustrates a schematic diagram of control resource allocation according to an embodiment of the present disclosure.

[0029] 11A to 11C illustrate exemplary signaling diagrams for wireless communications to which common DCI is applied according to an embodiment of the present disclosure.

[0030] FIG. 12 is a block diagram schematically showing an example structure of a personal computer as an information processing apparatus employable in an embodiment of the present disclosure.

[0031] FIG13 is a block diagram illustrating a first example of a schematic configuration of a gNB to which the technology of the present disclosure may be applied.

[0032] FIG14 is a block diagram illustrating a second example of a schematic configuration of a gNB to which the technology of the present disclosure may be applied.

[0033] FIG. 15 is a block diagram illustrating an example of a schematic configuration of a communication device to which the technology of the present disclosure can be applied.

[0034] FIG. 16 is a block diagram showing an example of a schematic configuration of a car navigation device to which the technology of the present disclosure can be applied.

[0035] While the embodiments described in this disclosure may be susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and are herein described in detail. However, it should be understood that the drawings and detailed description thereof are not intended to limit the embodiments to the particular forms disclosed, but on the contrary, the intent is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the claims. DETAILED DESCRIPTION

[0036] Exemplary embodiments of the present disclosure will be described below with reference to the accompanying drawings. For the sake of clarity and conciseness, not all features of the embodiments are described in the specification. However, it should be understood that many implementation-specific settings must be made in the process of implementing the embodiments in order to achieve the developer's specific goals, such as meeting those restrictions related to equipment and services, and these restrictions may vary depending on the implementation. In addition, it should be understood that although the development work may be very complex and time-consuming, it is only a routine task for those skilled in the art who benefit from the contents of this disclosure.

[0037] In addition, in order to avoid obscuring the present disclosure with unnecessary details, only the processing steps and / or device structures that are closely related to at least the solution according to the present disclosure are shown in the drawings, while other details that are not closely related to the present disclosure are omitted. It should also be noted that similar reference numerals and letters in the drawings indicate similar items, and therefore once an item is defined in one drawing, it does not need to be discussed again for subsequent drawings.

[0038] In the present disclosure, the terms "first," "second," etc. are used merely to distinguish between elements or steps, but are not intended to indicate temporal order, priority, or importance.

[0039] For ease of explanation, various aspects of the present disclosure will be described below in the context of 5G NR. However, it should be noted that this does not limit the scope of application of the present disclosure, and one or more aspects of the present disclosure may also be applied to existing wireless communication systems such as 4G LTE / LTE-A or various wireless communication systems to be developed in the future. The architecture, entities, functions, processes, etc. mentioned in the following description may have corresponding structures in NR or other communication standards.

[0040] Figure 1 is a simplified diagram illustrating the architecture of a 5G NR communication system. As shown in Figure 1, the 5G Core Network (5GC) may include various appropriate functional units, such as the Access and Mobility Management Function (AMF), the User Port Function (UPF), and so on. On the network side, the Radio Access Network (NG-RAN) nodes of the NR communication system may include gNBs and / or ng-eNBs. A gNB is a node newly defined in the 5G NR communication standard. It connects to the 5G Core Network (5GC) via an NG interface and provides NR user plane and control plane protocols for termination with terminal devices (also referred to as "user equipment," hereinafter referred to as "UE"). An ng-eNB is a node defined for compatibility with 4G LTE communication systems. It may be an upgrade of the evolved Node B (eNB) of the LTE radio access network. It connects the device to the 5G Core Network via an NG interface and provides Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocols for termination with the UE. An Xn interface is provided between NG-RAN nodes (e.g., gNBs and ng-eNBs) to facilitate communication between the nodes. In the following text, gNB and ng-eNB are collectively referred to as "base stations".

[0041] However, it should be noted that the term "base station" as used in this disclosure is not limited to the two aforementioned nodes, but rather is an example of a control device in a wireless communication system, and has the full breadth of its general meaning. For example, in addition to the gNB and ng-eNB specified in the 5G communication standard, depending on the scenario in which the technical solutions of this disclosure are applied, a "base station" may also refer to, for example, an eNB, a remote radio head, a wireless access point, a relay node in an LTE communication system, or a communication device or component thereof that performs similar control functions.

[0042] In addition, the term "UE" as used in this disclosure has its full breadth of its ordinary meaning, including various terminal devices or vehicle-mounted devices that communicate with a base station. As an example, a UE can be a terminal device or its components such as a mobile phone, laptop computer, tablet computer, vehicle-mounted communication device, etc.

[0043] Next, the NR radio protocol architecture for the base station and UE in Figure 1 is described in conjunction with Figures 2A and 2B. Figure 2A shows the radio protocol stack for the user plane of the UE and the base station, and Figure 2B shows the radio protocol stack for the control plane of the UE and the base station.

[0044] Layer 1 (L1) of the radio protocol stack is the lowest layer and may include a physical layer (PHY). The L1 layer implements various physical layer signal processing to provide a transparent transmission function of a signal.

[0045] Layer 2 (L2) of the radio protocol stack sits above the physical layer and is responsible for managing the radio link between the UE and the base station. In the user plane, the L2 layer includes the Medium Access Control (MAC) sublayer, the Radio Link Control (RLC) sublayer, the Packet Data Convergence Protocol (PDCP) sublayer, and the Service Data Adaptation Protocol (SDAP) sublayer. Furthermore, in the control plane, the L2 layer includes the MAC sublayer, the RLC sublayer, and the PDCP sublayer. The relationship between these sublayers is that the physical layer provides transport channels for the MAC sublayer, the MAC sublayer provides logical channels for the RLC sublayer, the RLC sublayer provides RLC channels for the PDCP sublayer, and the PDCP sublayer provides radio bearers for the SDAP sublayer.

[0046] In the control plane, both the UE and the base station also include the Radio Resource Control (RRC) sublayer in Layer 3 (L3). The RRC sublayer is responsible for obtaining radio resources (i.e., radio bearers) and configuring underlying layers using RRC signaling. Additionally, the Non-Access Stratum (NAS) control protocol in the UE performs functions such as authentication, mobility management, and security control.

[0047] In 5G NR, both downlink (DL) and uplink (UL) transmissions are organized into frames. Figure 3 shows a diagram of the frame structure in a 5G communication system. As a fixed structure compatible with LTE / LTE-A, the frame in NR also has a length of 10ms and consists of 10 equally sized subframes, each of which is 1ms. Unlike LTE / LTE-A, the frame structure in NR has a flexible structure that depends on the subcarrier spacing. Each subframe has a configurable time slots, such as 1, 2, 4, 8, 16. Each time slot also has a configurable OFDM symbols, for a normal cyclic prefix, each time slot contains 14 consecutive OFDM symbols, while for an extended cyclic prefix, each time slot includes 12 consecutive OFDM symbols. In the frequency domain dimension, each time slot includes a number of resource blocks (RBs), and each resource block contains 12 consecutive subcarriers (also called subcarriers) in the frequency domain. Therefore, a resource grid can be used to represent the resource elements (REs) in the time slot, as shown in Figure 3. The resource blocks available for uplink and downlink transmission can be divided into a data segment and a control segment. The resource elements in the control segment can be allocated for transmitting control information. The data segment can include all resource elements not included in the control segment for transmitting data to the UE or base station.

[0048] Time domain resources can be scheduled at various granularities, such as a single time slot, multiple consecutive time slots (also known as aggregated time slots), or partial OFDM symbols within a single time slot (also known as mini-slots). Frequency domain resources are generally scheduled in RB units and can be divided into different types depending on whether the scheduled RBs are contiguous.

[0049] For uplink or downlink transmissions, the base station can send downlink control information (DCI) via the physical downlink control channel (PDCCH) to indicate the scheduled time-frequency transmission resources. The base station can schedule transmission resources for the UE in every transmission time interval (TTI). This scheduling method is called dynamic scheduling (DG).

[0050] In order to save PDCCH resources, the base station can also adopt a non-dynamic scheduling method and send a periodically valid scheduling command to the UE, thereby periodically allocating transmission resources to the UE. For physical downlink shared channel (PDSCH) transmission in the downlink direction, semi-persistent scheduling (SPS) can be used, also known as semi-static scheduling. Simply put, the base station can send a downlink assignment (DL assignment) to the UE via PDCCH, so that after each period, the UE can use the allocated SPS resources to receive data without the need for the base station to send a scheduling command every time. For physical uplink shared channel (PUSCH) transmission in the uplink direction, a configured grant (CG) can be used. That is, the base station can configure an uplink grant (UL grant) for the UE through high-level parameters such as configuredGrantConfig to indicate the periodic uplink transmission resources that the UE can use. There are two types of CGs: CG Type 1, where the UE can directly use the configured resources to upload data without DCI activation; and CG Type 2, where the base station needs to activate the uplink grant before the UE uses the configured resources.

[0051] The base station can send verification of SPS or CG (Type 2) to the UE via DCI carried on PDCCH. As used in this disclosure, "verification" includes activation (Activation) or release (Release), and release is sometimes also called deactivation (Deactivation). In order to receive DCI, the UE can monitor PDCCH candidates in one or more configured search space sets. The set of PDCCH candidates to be monitored by the UE is defined according to the PDCCH search space set. The search space set can be a common search space (CSS) set or a user-specific search space (USS) set. Based on the information indicated in the received DCI, the UE can verify (activate / release) the DL SPS or UL CG accordingly.

[0052] Traditionally, SPS and CG activation and release can only be verified separately by the DL DCI and UL DCI of a single UE. In particular, DCI is scheduled for activation and / or release on a UE-by-UE basis. For example, a single DCI can only be used for either SPS verification or CG verification. Specifically, one downlink DCI (DL DCI) can be used to activate one SPS, or to release k (k ≥ 1, the value of k can be configured by RRC parameters) SPSs; one uplink DCI (UL DCI) can be used to activate one CG, or to release k (k ≥ 1) CGs.

[0053] However, the emergence of new communication services places higher demands on existing uplink and downlink resource configuration and verification methods. In particular, compared to traditional communication services, new services such as XR have unique service characteristics and design requirements for energy saving and capacity enhancement, such as the following KPI requirements and special traffic models:

[0054] (1) KPI requirements: XR services are promoted by multiple KPIs. Currently known service requirements include user energy saving, large capacity, low latency, high throughput, large coverage, support for good mobility, variable data packet size, and Quality of Service (QoS).

[0055] (2) Special service model: The currently established XR data model includes the following features: multiple uplink and downlink data streams, and the video and audio data streams have large data volumes; the data streams are periodic, with typical values ​​such as 60fps (frame per second) or 4ms, and also have non-integer periods, such as 30fps; the downlink data arrival has network jitter, and the uplink data packets generate optional data jitter.

[0056] In addition, the special features of new services and new scenarios, especially multimodal data streams, will further increase the number and amount of data streams contained in XR services, bringing greater challenges to meeting comprehensive KPI requirements, and may especially challenge existing uplink and downlink resource configuration and verification methods.

[0057] Specifically, on the one hand, multiple periodic data streams require the configuration of multiple SPSs and CGs to reduce the high energy consumption caused by frequent DG DCI overhead, and the non-integer period of the data stream will cause multiple SPSs / CGs to equivalently implement a non-integer period (30fps corresponds to a 33.33ms period, and 60fps corresponds to a 16.67ms period). Since the existing standard does not have SPSs and CGs configured with non-integer periods, multiple SPSs / CGs can be configured (such as three SPS / CG indexes within 50ms, all with a period of 50ms, but starting at 0ms, 16ms, and 33ms within 50ms), so that the period within 50ms is aligned with the service and does not cause delays. This will result in the issuance of more SPS / CG configurations and their verification (activation and release) DCI.

[0058] On the other hand, the variable packet size means that the SPS / CG configured for each flow needs to be flexibly indicated for its activation and release, so it is necessary to flexibly adjust the SPS / CG resources to better match the actual arriving data.

[0059] As XR supports more UEs and each UE needs to transmit more data streams (multimodal data streams), more SPS / CG and corresponding activation / release DCI will be issued to multiple UEs. This further increases the DCI in the DRX ON (activation cycle), which not only includes the already increased data scheduling DCI, but also a large number of SPS / CG activation / deactivation DCI. The issuance of a large number of SPS and CG verification DCI to multiple UEs will involve more control DCI overhead, which will lead to insufficient PDCCH resources, which in turn may cause low-priority DCI to be delayed to the next time slot, bringing the risk of increased delay exceeding the packet delay budget (PDB). Here, the packet delay budget PDB can refer to the upper limit of the time that a data packet / data packet can be delayed in data transmission, that is, how long the data packet / data packet should be sent. If it is not sent, it is considered to have exceeded the PDB and does not meet the PDB requirements. In other words, in a multi-UE scenario, sending a scheduling DCI to each UE for release (FDRA, MCS, RV fields set to default values) according to the conventional method will accelerate the exhaustion of PDCCH resources and increase transmission delay.

[0060] Therefore, there is a need for enhanced uplink and downlink resource scheduling solutions to adapt to various existing or emerging service scenarios. In particular, it is hoped that flexible activation and release can achieve efficient use of SPS / CG resources while meeting data transmission latency and reducing power consumption.

[0061] In view of this, an improved solution is proposed in the present disclosure. In particular, a DCI that can be shared by multiple terminal side devices (or user equipment, which may also be referred to as "user" or "UE") is proposed to simultaneously indicate the verification of SPS and / or CG of multiple terminal side devices, including the release and / or activation of SPS / CG. In the context of the present disclosure, the DCI shared by multiple terminal side devices may be referred to as common DCI. Compared with the traditional UE-by-UE scheduling of DCI for activation and release, from the perspective of system resources, the use of common DCI can save PDCCH resource configuration. In addition, the number of blind detections required for public DCI decoding is less than that for UE-by-UE scheduling of DCI, so UE energy saving can also be achieved. It should be noted that the public DCI according to the present disclosure can be used for downlink DCI, uplink DCI, or both uplink DCI and downlink DCI.

[0062] The following describes embodiments of the present disclosure in detail. Typically, a wireless communication system or radio system includes at least a terminal side and a control side. In the present disclosure, the term "terminal side" has its full meaning and generally refers to the side of the system that can access / connect to the communication network to perform communication operations. The term "control side" has its full meaning and refers to the side that can provide information to the terminal side of the system to control / process its communication operations accordingly. In some embodiments, the control side can be used interchangeably with the transmitting side, which can also communicate data with the terminal side.

[0063] The terminal side device may include various appropriate devices, which may correspondingly include a terminal device in a communication system. In the present disclosure, the term "terminal device" has the full breadth of its usual meaning, and at least includes a terminal device that receives a signal from a transmitting side device to facilitate communication as part of a wireless communication system or a radio system. As an example, the terminal device may be, for example, a terminal device such as a wireless relay, a micro base station, a router, a user device, or a communication device that performs similar functions. In the present disclosure, "terminal device" and "user equipment (UE)" may be used interchangeably, or the "terminal device" may be combined with the "user equipment" or implemented as part of the "user equipment". In the present disclosure, the term "user equipment (UE)" has the full breadth of its usual meaning, and as an example, the user equipment may be, for example, a terminal device such as a mobile phone, a laptop, a tablet computer, an in-vehicle communication device, or a communication device that performs similar functions.

[0064] The control side device or the transmitting side device may include various appropriate devices, such as a base station in a wireless communication system (such as a cellular communication system, a V2X system, etc.), a control device, a server or MEC, a repeater or a roadside unit (RSU), etc. In the present disclosure, the term "base station" has the full breadth of its usual meaning, and as an example, the base station may be, for example, an eNB that complies with the 4G communication standard, a gNB that complies with the 5G communication standard, a remote radio head, a wireless access point, an aircraft control tower, or a communication device that performs similar functions. In addition, in the present disclosure, the control side device may include any other appropriate device in the network. For example, in a 5G network implementation, the control side device may be implemented by an appropriate function / unit / module / device in the 5G core network, for example, corresponding to the AF in the 5G core network.

[0065] Figure 4 illustrates a schematic diagram of a control side device performing scheduling verification of multiple terminal side devices through a public DCI in wireless communication according to an embodiment of the present disclosure. On the one hand, the control side device sets a public DCI and related parameters, wherein the public DCI indicates information associated with the SPS / CG verification of multiple terminal side devices, and the SPS / CG verification may include at least one of release and activation, especially the release of the SPS / CG of each user. For example, the base station can configure a corresponding SPS / CG verification combination for each UE in a plurality of UEs through RRC parameters, and each verification combination can at least include one or more indexes (SPS indexes) of the SPS to be verified and / or one or more indexes (CG indexes) of the CG to be verified. The public DCI can be in various appropriate formats, as described in detail below. It should be noted that in the context of the present disclosure, "SPS / CG" is substantially equivalent to "SPS and / or CG" and "at least one of SPS and CG" and can be used interchangeably. On this basis, any operation or any information associated with SPS / CG may indicate that the operation or information involves at least one of SPS and CG.

[0066] It should be noted that in the embodiments of the present disclosure, for multiple terminal-side devices, such as multiple terminal-side devices in a specific cell or a specific area, a common DCI will be generated and issued to all terminal-side devices, even if some of the terminal-side devices may not perform SPS / CG verification. Alternatively, in other embodiments, a common DCI may be generated and issued only for at least one terminal-side device that is to perform scheduling verification, while no common DCI is generated for terminal-side devices that are not to perform scheduling verification.

[0067] On the other hand, each terminal side device, in particular, the electronic device used for the terminal side device, receives the public DCI and parses it, such as performing blind detection, so as to obtain an indication of SPS / CG verification for it and perform corresponding SPS / CG verification according to the indication.

[0068] Furthermore, additionally, with respect to the verification performed using the common DCI proposed in the present disclosure, each of the multiple UEs may also perform feedback on the common DCI, for example, may perform HARQ ACK / NACK feedback on the DCI.

[0069] The following describes a control-side electronic device of a wireless communication system according to an embodiment of the present disclosure. In the present disclosure, the control-side electronic device may include any suitable electronic device for controlling a side device (e.g., a base station or other such device), such as associated with the control-side device, or even the control-side device itself. In particular, the control-side electronic device is capable of sending a common DCI to multiple terminal-side devices to enable SPS / CG verification of multiple terminal-side devices.

[0070] 5A shows a schematic block diagram of a control-side electronic device of a wireless communication system according to an embodiment of the present disclosure. The control-side electronic device 500 includes a processing circuit 502 configured to send common downlink control information (DCI) for terminal-side devices in the wireless communication system, indicating verification of one or more semi-persistent scheduling (SPS) and / or verification of one or more configuration grants (CG) for each of a plurality of terminal-side devices.

[0071] In an embodiment of the present disclosure, the verification of the semi-persistent scheduling (SPS) and / or the verification of the configuration authorization (CG) of the terminal side device may refer to at least one of the SPS verification and the CG verification of the terminal side device, that is, the terminal side device may involve any of SPS verification only, CG verification only, SPS verification and CG verification. It should be noted that in an embodiment of the present disclosure, the verification of one or more SPSs and / or one or more CGs for each of a plurality of terminal side devices may include a variety of possible verification situations. For example, among a plurality of terminal side devices, some terminal side devices only perform SPS verification, and other terminal side devices only perform CG verification. For another example, among a plurality of terminal side devices, some terminal side devices only perform SPS verification or only CG verification, and other terminal side devices may even involve both SPS verification and CG verification.

[0072] In the context of the present disclosure, verification may include at least one of activation and release. As an example, SPS verification may include any one of SPS release, SPS activation, SPS activation and release. Similarly, CG verification may include any one of CG release, CG activation, CG activation and release. It should be noted that in an embodiment of the present disclosure, the verification of one or more SPSs and / or one or more CGs for each terminal side device in a plurality of terminal side devices may include a variety of possible operating conditions. In particular, on the basis of the above-mentioned verification combination, for each of the SPS verification and CG verification of each terminal side device, at least one of activation and release may also be performed as described above. In one example, at least one terminal side device may include at least one SPS verification, including only SPS release, only SPS activation, or any one of SPS activation and release. In one example, at least one terminal side device may include at least one CG verification, including only CG release, only CG activation, or any one of CG activation and release.

[0073] Preferably, in an embodiment of the present disclosure, the processing circuit is configured to send common downlink control information (DCI) for a terminal side device in a wireless communication system, which indicates the release / deactivation of one or more semi-persistent scheduling (SPS) and / or the release / deactivation of one or more configuration grants (CG) for each terminal side device in a plurality of terminal side devices. The following also mainly describes the implementation according to an embodiment of the present disclosure with respect to the case where the common DCI is used for SPS / CG release. It should be noted that the activation of SPS / CG of multiple terminal side devices can also utilize the concept of common DCI, but the configuration, information contained, format, etc. of the common DCI may be different.

[0074] In some embodiments, common downlink control information (DCI) for multiple terminal side devices may include information blocks for each terminal side device respectively to indicate the verification of one or more semi-persistent scheduling (SPS) and / or one or more configuration authorization (CG) of the terminal side device. In particular, each information block may correspond to a terminal side device and may indicate SPS / CG verification for the terminal side device, preferably SPS / CG release. Thus, in operation, each terminal side device, in particular the electronic device used for the terminal side device, can parse the information block corresponding to the terminal side device from the common downlink control information (DCI), and then perform corresponding verification operations according to the indication information in the information block. Here, the parsing can be implemented in various ways in the art, especially including blind detection of common DCI, etc., which will not be described in detail here.

[0075] In some embodiments of the present disclosure, the correspondence between each terminal side device in a plurality of terminal side devices and each information block in a public DCI can be pre-set and notified to the terminal side in an appropriate manner. As an example, the correspondence may include a one-to-one correspondence between the terminal side device and the information block in the public DCI, or a one-to-many correspondence between the terminal side device and the information block in the public DCI, etc. For example, each information block may be indicated by at least one of a block identifier (ID), a block position, a block size, etc., and corresponds to the identifier of the terminal side device. Here, the block position can be indicated by various appropriate position-related information, including at least one of the starting position and the ending position of the information block, which can, for example, directly reuse a standard indication method (such as the position indication of DCI2-6) to inform the terminal side device. In particular, knowing the starting position or the ending position of the block position and the block size, the message block corresponding to the terminal side device can be determined. Of course, the block size can also be a default size, or the UE can be notified in advance in the system. In this way, when the terminal side device receives the public DCI, it can parse the corresponding information block based on the correspondence between it and the information block, such as the corresponding block ID, block position, etc., to obtain the relevant indication information for the SPS / CG verification of the terminal side device.

[0076] In some embodiments, information related to the correspondence between the terminal side device and the information block is pre-notified to multiple terminal side devices before the DCI is issued. For example, the ID information of the public DCI (for example, when there is more than one public DCI) and the information related to the correspondence between the information block in the public DCI and the terminal side device, such as the ID of the information block corresponding to the terminal side device, can be pre-notified to each terminal side device, so that the terminal side device can obtain the corresponding information block according to the correspondence when receiving the public DCI with the ID information. For example, the relevant information of the correspondence can be notified to the terminal side through RRC signaling.

[0077] In some embodiments of the present disclosure, taking into account a certain degree of user flexibility, the size of the public DCI also needs to appropriately support variability (taking into account different numbers of MUs), that is, the size of the public DCI is variable and can be set in advance. As an example, a public DCI size list can be set in the RRC parameters (for example, by the parameter sizeListDCI), including various possible public DCI sizes. In one implementation, if the public DCI size is not specifically set, a certain size in the size list can be activated by the MAC CE during operation, and associated parameters such as the position-related information of the information blocks corresponding to each UE in the public DCI can also be used as relevant information of the corresponding relationship and need to be indicated by the MAC CE and notified to the UE. In some embodiments of the present disclosure, the position-related information can include various appropriate information related to the position of the information block, such as information that can be used to determine the position of the information block, including but not limited to the information block ID, the information block position (for example, it can be indicated by a standard indication method (such as the position indication of DCI2-6)), the information block size, etc.

[0078] According to some embodiments of the present disclosure, the processing circuit is further configured to: set at least one of the following parameters: size information indicating the size of the common DCI; and position-related information, from which the position of the information block corresponding to each terminal side device in the common DCI can be derived. It should be noted that such parameters indicating common DCI-related information may belong to high-level parameters, such as RRC parameters. For example, the size information may be indicated by sizeDCI and may be sent to each terminal side device in an appropriate manner, such as through appropriate RRC signaling. As an example, multiple terminal side devices may be informed in advance, such as when the system is constructed, or before the DCI is issued.

[0079] According to other embodiments of the present disclosure, the correspondence between the terminal-side device and the information block can be set by default. For example, the terminal-side device and the information block can be arranged in the same order, numbered in the same manner, etc., and the terminal-side device and the information block with the same number are corresponding by default. Therefore, during the parsing process, the terminal-side device can directly find the information block with the same number to obtain relevant indication information from it. Of course, the default correspondence can also be other correspondences, such as reverse correspondence, etc. This situation is particularly suitable for situations where the size of public DCI, information blocks, etc. is fixed and known, and will not be described in detail here.

[0080] According to some embodiments of the present disclosure, the relevant information of the correspondence relationship can even be included in the DCI and as separate information outside the information block for each terminal side device, so that each terminal side device can read the relevant information of the correspondence relationship when parsing the public DCI to obtain the information block corresponding to it. In particular, in some embodiments, the public DCI may also include relevant information indicating the correspondence relationship between the information block it contains and multiple terminal side devices.

[0081] According to an embodiment of the present disclosure, common downlink control information (DCI), especially information blocks therein, is set to an appropriate format, especially including various appropriate information. In particular, each information block in the common DCI can be of the same format, for example, including the same type of information.

[0082] According to some embodiments of the present disclosure, for each terminal side device, the information block may also include at least identification information, which is related to the semi-persistent scheduling (SPS) and / or configuration grant (CG) to be verified and indicates the SPS / CG to be verified. In particular, the identification information may include at least one of identification information associated with the SPS to be verified and identification information associated with the CG to be verified.

[0083] In some embodiments, the identification information may include various information, including but not limited to at least one of type information, operation information, index information, flow information, etc.

[0084] In particular, in some embodiments, the information block may include at least index information, which may indicate the SPS / CG to be verified. The index information may, for example, include at least one of the ID of the SPS / CG to be verified, the position of the SPS / CG, etc., to indicate which SPS / CG or SPSs / CGs are to be verified. For example, the ID of the SPS / CG may directly indicate the SPS / CG to be verified, or, as an alternative, the position of the SPS / CG may indicate the SPS / CG at that position in the sequence of the SPS / CG to be verified for verification. The index information is also represented in various appropriate ways, which will be described in detail below.

[0085] In some embodiments, optionally or additionally, the identification information may further include type information, which may indicate whether the SPS or CG to be verified is SPS. The type information may include various appropriate representations. In some examples, different values ​​may be set for SPS and CG, respectively, to facilitate differentiation. As an example, a binary value may be used to distinguish between SPS and CG, which is referred to as an uplink and downlink indication, such as a 1-bit value, where a value of 0 indicates CG and a value of 1 indicates SPS, and vice versa.

[0086] In some embodiments, the identification information may include at least one information pair, each information pair may include type information and an index of a schedule to be verified under the type. As an example, an information pair may include a verification type information and one or more index information, for example, an SPS and one or more SPS indexes, in particular, depending on the field size, the one or more SPS indexes may include all SPSs to be verified, or at least some of the SPSs to be verified. This is also applicable to CG verification.

[0087] In some embodiments, as an alternative, type information is not required in the identification information. In particular, if the type to be verified has been determined, there is no need to include this type information. As an example, in the case where it is known or determined by default that only SPS verification is required, for example, the public DCI is applied for verification scheduling only when it has been pre-set that only SPS verification is required, and the identification information may only include the index information of the SPS. The same applies to the case of CG verification. As another example, this type information may be included in the public DCI in various appropriate ways, such as being included in the public DCI but outside each information block, or even outside the public DCI and notified in advance to each terminal side device, such as through RRC signaling. This is particularly suitable for the case of verifying only SPS or only CG.

[0088] According to an embodiment of the present disclosure, optionally or additionally, the public DCI may further include operation information, which may indicate the operation type of the SPS / CG verification, for example, the information may indicate that the verification operation is at least one of activation and release. In particular, in some embodiments, the SPS / CG verification operation may include any one of activation only, release only, or activation and release.

[0089] In some embodiments, the operation information may include various appropriate representations. In some examples, corresponding different values, such as different numerical values, different characters, etc., may be set for activation and release to distinguish different operation types. For example, different numerical values ​​and characters are used to distinguish between activation, release, and neither activation nor release. In particular, when "neither activation nor release" is set, the other information in the information block may all be set to null. As another example, when public DCI information is only issued when activation and / or release is to be performed, that is, public DCI information only involves terminal side devices to be activated and / or released, and does not involve terminal side devices that do not activate or release, then activation and release can be indicated in a binary manner. For example, in the case of a binary manner, a value of 1 indicates activation and a value of 0 indicates release. It should be noted that this situation may correspond to different types of verification, where activation and release may occur. For example, an SPS may be released or activated, while a CG may be released or activated; or even an SPS or CG may have both activation and release.

[0090] In some embodiments, when the operation type is only one type, such as release, the operation information can use a binary method to indicate whether to perform the release. In some embodiments, for each terminal side device, the information block also includes a release indication, which indicates whether to perform the release of semi-persistent scheduling (SPS) and / or configuration authorization (CG). It can be a binary method, such as a release indication, for notifying the release or not. For example, the release indication is 1 bit, the value 0 indicates not to release, the value 1 indicates release, or vice versa. The same applies to the operation type, especially the case of activation only.

[0091] It should be noted that, as an alternative, the operation information is not required. In particular, if the type of operation to be performed has been determined, there is no need to include this operation information. As an example, when it is known by default or it has been determined that only release is to be performed, for example, when only release (CG release and / or SPS release) has been pre-set, public DCI is applied for verification scheduling, that is, public DCI is only applicable to the case of SPS / CG release, which is set by default, so that signaling communication can be appropriately simplified. The identification information may not include operation information, but only include index information of SPS / CG, and optional SPS / CG type information.

[0092] In some embodiments of the present disclosure, the operational information may also be included in the public DCI in other appropriate ways. For example, the operational information may be included in the public DCI but outside of each information block, or even outside of the public DCI and communicated in advance to each terminal-side device, for example, via RRC signaling. This is particularly suitable for situations where it is known or determined that the public DCI is for release-only or activation-only purposes.

[0093] In some embodiments, optionally or additionally, the identification information may include stream information, which may also be referred to as a stream identifier, indicating to which stream the SPS and / or CG indicated by the identification information belongs. In particular, in the case where there may be multiple streams, the information block may include an identifier of the data stream to which the SPS / CG to be verified of each terminal side device belongs, which may be in various appropriate forms, such as numbers, characters, etc., as long as different data streams can be distinguished. It should be noted that in the context of the present application, stream information may not be necessary. For example, stream information may not be set and provided when it is stipulated by default or determined that a public DCI is generated and provided only for a specific data stream. As another example, the stream information may be included separately in the public DCI and outside of each information, or even outside the public DCI and sent to multiple terminal side devices before the public DCI, for example, by RRC signaling, which is particularly suitable for the case where the public DCI is for the same data stream.

[0094] As can be seen from the above, according to an embodiment of the present disclosure, as a setting of a public DCI, for each electronic device on the terminal side, its corresponding information block may contain at least index information, indicating the SPS / CG scheduling to be verified, and additionally or optionally, may contain at least one of type information, operation information, and flow information, all of which may be included in the verification identification information according to an embodiment of the present disclosure. It should be noted that type information, operation information, and flow information are not required. For example, in the case of default agreement or regulation, depending on the pre-agreed situation, type information, operation information, and flow information may not be included in the information block, or may be included in the public DCI outside the information block, or even pre-informed to the terminal side device before the DCI is issued, as described above.

[0095] According to an embodiment of the present disclosure, the information block of the terminal side device may further include offset information, which may be related to the execution of the verification, for example, and may indicate the time when the verification indicated in the information block is executed. In some embodiments, for each terminal side device, the information block may further include effective time information as offset information, and the value of the effective time information may correspond to a time value, which indicates how long the terminal side device will wait after receiving and parsing the public DCI before performing the verification indicated by the public DCI. In some examples, the effective time is set to 0, that is, the verification operation is performed immediately after parsing the public DCI, which may correspond to a default situation, such as a situation where there is no effective time information in the information block.

[0096] In some embodiments, the effective time information can be set in a variety of appropriate ways. In some embodiments, a corresponding effective time can be set for each verification type (e.g., SPS or CG), each operation type (e.g., activation or release), and even each verification index, so that after the terminal side device receives and parses the public DCI, it can perform its own verification to be performed at the time indicated by the effective time information. In some embodiments, the configuration of the effective time information can also be further simplified. As an example, the same effective time information can be set for all SPS / CGs to be verified of the terminal side device. As another example, the same effective time information can be set for a specific type of verification operation. As another example, the same effective time information can even be set for all terminal side devices.

[0097] It should be noted that, as an alternative, the effective time information is not necessary. In particular, the effective time information can be set by default, or set by default to a specific value, which is suitable for verification of all devices for a specific type, a specific operating mode, or even for verification of all types and all operating modes. As an example, the effective time information can be set to a specific value for release. As another example, the effective time information can be confirmed or set to 0 by default, that is, once the relevant information verified in the DCI is detected, the corresponding operation is performed immediately. As yet another example, the effective time information can be notified to each terminal side device in advance outside the DCI, for example, it can be notified through RRC signaling.

[0098] 6A schematically illustrates the configuration of each information block in the public DCI, wherein each information block may include type information, operation information, index information, stream information, offset (e.g., effective time information), etc. As an example, for a terminal side device, when releasing and activating the SPS, and releasing and activating the CG, its corresponding information block may respectively include information fields in the following forms: (SPS, release, SPS index, stream ID, effective time, etc.), (SPS, activation, SPS index, stream ID, effective time, etc.), (CG, release, CG index, stream ID, effective time, etc.), (CG, activation, CG index, stream ID, effective time, etc.). Of course, when only one or more of SPS release, SPS activation, CG release, and CG activation are performed, the information block will only contain the corresponding one or more of the above information. 6B shows the configuration of each information block in the public DCI in the case of only releasing the operation, where UL / DL is indicated as an example of type information, and can be indicated as CG (corresponding to UL) or SPS (corresponding to DL), and ID / INDEX is an example of index information, and its format will be described in detail later. It should be understood that the fields described or shown do not represent all fields of the DCI, and depending on different DCI formats and different scrambling, one or some fields may not exist, or be included in or outside the information block. For example, each information block may include index information, effective time information, while type information, operation information, and flow information may be located outside the information block. It should be noted that the public DCI according to the present disclosure can be set in a variety of appropriate ways. As an example, it can be implemented in a communication protocol. For example, it is implemented by adding a new DCI format in the current protocol.

[0099] The following describes an exemplary format configuration of a public DCI according to an embodiment of the present disclosure. It should be noted that the public DCI can be a newly designed DCI format with a newly designed format, such as DCI format 2-8. As an example, DCI format 2-8 can be used to notify one or more UEs of SPS / CG release information. The following information can be transmitted via DCI format 2-8, which has a CRC scrambled by a common CS-RNTI:

[0100] -Block number: e.g. block 1, block 2, ..., block N

[0101] Among them, the above-mentioned block number information indicates that the N information blocks contained in the DCI correspond to one or more UEs respectively. The starting position of a block is determined by the high-level parameters provided by the high-level layer for the UE configured with the block. The parameter can be, for example, a position-related parameter, which can be expressed as release-PositionDCI-2-8.

[0102] In particular, if the UE is configured with higher layer parameters, especially common CS-RNTI and DCI ormt 2-8, the higher layer configures a block for the UE, corresponding to the aforementioned identification information, in which the following fields are defined:

[0103] - Release indication, which can be a binary value, 1 bit, indicating release or non-release. If there is no indication of release, that is, non-release, other fields in this block can be set to specific values, such as all 0s or other appropriate default values. It should be noted that this field can be optional;

[0104] - UL / DL indication, which can be a binary value (1 bit) indicating SPS or CG;

[0105] - Index information (ID / INDEX), which may contain an appropriate number of bits to indicate the SPS and / or CG to be released, such as an identifier of the SPS / CG to be released, for example, 1 bit to indicate the type of indication (ID or INDEX), 4 bits when the number of HARQ IDs = 16; 5 bits when the number of HARQ IDs = 32; if the ID value or INDEX value requires, Ceil[log(sizeof(RRC parameter))] bits. If the ULDL indicates SPS, the INDEX in this field is associated with the RRC parameter SPS-ConfigDeactivationStateList; if the ULDL indicates CG, the INDEX in this field is associated with ConfiguredGrantConfigType 2 DeactivationStatelist. If the newly designed parameter mixSPSConfigType 2 DeactivationStatelist is supported in the RRC configuration, an additional bit (e.g., 1 bit) is required to indicate whether the index is associated with the newly designed parameter or with the two traditional parameters;

[0106] - Stream information, which can be represented by a stream ID (Stream ID), which can be associated with an ID / INDEX to indicate which stream the ID / INDEX is intended for. It should be noted that stream information is optional;

[0107] - Offset, which can be x bits, indicating that after the offset, the indication will be applied. It should be noted that the offset is optional;

[0108] - Reserved bit.

[0109] The size of DCI format 2_8 is indicated by the higher layer parameter "DCI size" (e.g., sizeDCI-2-8), alternatively, if the parameter DCI size is not configured, the appropriate size can be activated or selected by the MAC CE from the higher layer parameter "DCI size list" (e.g., sizeListDCI-2-8).

[0110] It should be noted that the public DCI according to the embodiments of the present disclosure may have a newly designed DCI format and be added to the current protocol as a modification, for example, as DCI-format 2.8. The following shows a textual description of DCI-format 2.8 that may be added to the current protocol.

[0111] DCI format 2_8 is used for notifying the SPS / CG release information for one or more UEs.

[0112] The following information is transmitted by means of the DCI format 2_8 with CRC scrambled by commonCS-RNTI:

[0113] -block number 1,block number 2,…,block number N

[0114] where the starting position of a block is determined by the parameter release-PositionDCI-2-8 provided by higher layers for the UE configured with the block.

[0115] If the UE is configured with higher layer parameter commonCS-RNTI and dci-Format2-8,one block is configured for the UE by higher layers,with the following fields defined for the block:

[0116] -Release indication-1 bit(release or not).If not release is indicated,other fields can be set to special value like all 0.This field can be optional.

[0117] -ULDL indication-1 bit.(SPS or CG)

[0118] -ID / INDEX–1bit tell which type for indication(ID or INDEX),and 4 bit when HARQ ID number=16;5 bit when HARQ ID number=32;Ceil[log(sizeof(RRC parameter))]bit if needed for the ID value or INDEX value.if ULDL indicates SPS,then INDEX in this field associate to RRC parameter sps-ConfigDeactivationStateList,if ULDL indicates CG,then INDEX in this field associate to ConfiguredGrantConfigType2DeactivationStateList.if mixSPSConfigType2DeactivationStateList is supported in RRC configuration,then another extra bit(1bit)is needed to indicate INDEX is associated with this parameter or legacy two parameter.

[0119] Optionally,Stream ID can be associated with ID / INDEX to indicate which stream the ID / INDEX is intends for.

[0120] -Offset-x bit.Optionally(After Offset,the indication will apply)

[0121] -Reserved bit

[0122] The size of DCI format 2_8 is indicated by the higher layer parameter sizeDCI-2-8.

[0123] The following describes an exemplary configuration of the index information contained in each information block in the public DCI, especially the verification identification information, according to an embodiment of the present disclosure. According to an embodiment of the present disclosure, the index information may include an ID or INDEX indication corresponding to the identification of the SPS or CG. The ID may indicate a single SPS ID or CG ID, as is conventional. Alternatively, the identification information may include an INDEX, which may indicate a group of SPSs, or a group of CGs, or a group of mixed SPSs and CGs.

[0124] It should be noted that the index information can be set by various appropriate methods. In some embodiments, the index information can be set by modifying the RRC parameters and setting a specific value related to the verification status in a specific field of the DCI. That is, the specific field may correspond to the index information. According to some embodiments of the present disclosure, the processing circuit is also configured to configure radio resource control (RRC) parameters for multiple terminal side devices, and the RRC parameters specify at least one combination for each of the multiple terminal side devices, each combination containing one or more SPS indexes and one or more CG indexes, wherein the information block corresponding to the terminal side device in the public DCI indicates at least one of the at least one combination to verify the SPS identified by the one or more SPS indexes in the combination and the CG identified by the one or more CG indexes in the combination. In particular, as an example, a verification state, such as at least one of an activation state and a release state, can be set in an RRC parameter, and the verification state can be mapped to one or more SPS configurations and / or one or more CG configurations, and then a specific field of the public DCI, such as the "HARQ process number" field contained in each information block, can be set to a specific value indicating an entry corresponding to a deactivation state, so that the UE will verify a group of SPSs and / or a group of CGs indicated in the verification state. The following will take release / deactivation as an example, but it should be noted that the index information related to activation verification can also be set accordingly in a similar manner.

[0125] In one example, the base station may modify / extend the information element sps-ConfigDeactivationStateList in the RRC parameter BWP-DownlinkDedicated, which indicates a list of deactivation states, and at least one deactivation state may be mapped to a set of SPS configurations (including a single or multiple SPS indexes). Subsequently, the base station may send down a common DCI, in which the corresponding field of the corresponding information block in the common DCI (e.g., the "HARQ process number" field) is set to a specific value indicating an entry corresponding to a certain deactivation state, so that the UE will deactivate (release) a set of SPSs indicated in the deactivation state. In the case of an extended deactivation state list, if the number of entries in the list exceeds a limit (e.g., the maximum number of HARQ processes, 16 or 32), the bits required for the "HARQ process number" field in the DCI may need to be increased, for example, from 4 or 5 bits to more bits, such as to ceil[log2((size of sps-ConfigDeactivationStateList))], where the function ceil[x] represents the smallest positive integer greater than or equal to x, so that the "HARQ process number" in the DCI can indicate all deactivation states listed in the sps-ConfigDeactivationStateList.

[0126] As another example, the base station may modify / extend the information element ConfiguredGrantConfigType2DeactivationStateList in the RRC parameter BWP-UplinkDedicated, which indicates a list of deactivation states. According to this exemplary embodiment, at least one deactivation state may be mapped to a set of CG configurations (including single or multiple CG indexes). Subsequently, the base station may issue a common DCI in which the corresponding field of the corresponding information block in the DCI (e.g., the "HARQ process number" field) is set to a specific value corresponding to a certain deactivation state, so that the UE will deactivate (release) a set of CGs indicated in the deactivation state. If the number of entries in the list exceeds a limit (e.g., the maximum number of HARQ processes, 16 or 32), the bits required for the "HARQ process number" field in the DCI may need to be increased, for example, from 4 or 5 bits to more bits, such as to ceil[log2((size of ConfiguredGrantConfigType2DeactivationStateList))], so that the "HARQ process number" in the DCI can indicate all deactivation states listed in ConfiguredGrantConfigType2DeactivationStateList.

[0127] As yet another example, alternatively, in addition to reusing existing RRC parameters, new RRC parameters may be defined. For example, DLCGType2sps-ConfigDeactivationStateList and / or ULCGType2sps-ConfigDeactivationStateList may be defined, which may also be referred to as mixSPSConfigType2DeactivationStateList, which may specify deactivation states, wherein at least one deactivation state may be mapped to a set of CG configurations (including a single or multiple CG indexes) and / or a set of SPS configurations (including a single or multiple SPS indexes). In particular, the above parameters may specify the deactivation of SPS, the deactivation of CG, or even the deactivation of both SPS and CG. The base station may then use the corresponding field (e.g., the "HARQ process number" field) of the corresponding information block in the common DCI (e.g., common DL DCI and / or common UL DCI) to indicate a specific deactivation state, such as only SPS deactivation, only CG deactivation, both SPS deactivation and CG deactivation, so that the UE can release the indicated SPS and / or CG.

[0128] As an example, a common DCI may be set up so that the "HARQ process number" field of each of its information blocks can indicate the release of both the CG and the SPS. In particular, the "HARQ process number" field may include at least two HARQ IDs, wherein the first HARQ ID may indicate the release of the corresponding CG according to the configuration of the conventional UL DCI, while the subsequent HARQ IDs additionally indicate the release of the SPS and / or CG. For example, the subsequent HARQ IDs may be associated with one or more SPSs to be released, and one or more other CGs with one or more SPSs, respectively. Alternatively, the first HARQ ID may also indicate the release of the corresponding SPS according to the configuration of the conventional DL DCI. In this case, if the bits required for the "HARQ process number" field in the DCI may need to be increased, appropriate bits may be added depending on the SPS or CG, as described above.

[0129] It should be noted that the above RRC parameter settings and HARQ ID settings for SPS and CG release can be equally applied to SPS and CG activation. In addition, the above implementation of the embodiment of the present disclosure can also be applied to the activation and / or release of SPS, and the activation and / or release of CG.

[0130] According to this exemplary embodiment, the base station may also specify both activation and release in the public DCI, such as by setting RRC parameters or a specific field in the DCI (e.g., a HARQ ID field) to indicate both SPS and CG, such as a mixed SPS and CG. For example, this may be achieved by including the HARQ ID associated with the SPS and / or CG to be verified in each information block of the public DCI and setting it to a specific value to achieve flexible verification of the SPS and / or CG. Both SPS and CG may include a variety of appropriate combinations, such as "SPS verification (activation / release) + CG release", "CG verification (activation / release) + SPS release", "SPS verification (activation / release) + CG activation", "SPS verification (activation / release) + CG activation", etc. In general, "SPS verification + SPS release" or "SPS verification + CG release" can be implemented using DL DCI, and "CG verification + SPS release" or "CG verification + CG release" can be implemented using UL DCI. In terms of standard changes, "SPS verification + SPS release" can be implemented using DL DCI, and "CG verification + CG release" can be implemented using UL DCI. The specific combination format can be configured by RRC, activated by MAC CE, or by adding a bit indication in DCI, or a combination of RRC configuration, MAC CE activation, and DCI indication, as long as the base station and UE can reach a consensus on the understanding of the corresponding fields in DCI.

[0131] According to an exemplary embodiment of the present disclosure, the format of the public DCI can be appropriately simplified. In particular, when appropriate information blocks are included for multiple terminal-side devices as described above, the traditional default field of the DCI for a single UE can be omitted, which can simplify the format of the public DCI, save DCI size, and facilitate fast blind detection.

[0132] In some exemplary embodiments, a simplified DCI format may be newly defined, primarily for the simultaneous release of SPS and CG. This simplified DCI retains the use of CS-RNTI (Configuration Scheduling-Radio Network Temporary Identity) scrambling, and its "HARQ Process Number" field includes multiple HARQ IDs associated with one or more SPSs and one or more CGs to be released. Other fields may be ignored, including but not limited to at least one of the following fields:

[0133] -DCI format identifier;

[0134] - New Data Indicator (NDI);

[0135] - Data Field Indicator (FDI) flag;

[0136] -Time domain resource allocation;

[0137] - Frequency domain resource allocation;

[0138] -PDSCH to HARQ feedback timing indicator;

[0139] - Redundancy Version (RV);

[0140] - Modulation and Coding Scheme (MCS).

[0141] It should be noted that since this public DCI is a newly defined format, the base station needs to pre-configure the DCI format to the UE through higher-layer parameters and configure the PDCCH candidates carrying the DCI in the UE's search space. This allows the UE to receive and understand this DCI and release the SPS and CG associated with all HARQ IDs included in its "HARQ Process Number" field.

[0142] According to some embodiments of the present disclosure, the public DCI can be appropriately configured to indicate that the public DCI is for verification of the SPS and / or CG of multiple terminal side devices. In some embodiments, the processing circuit is further configured to: scramble the public RNTI configuration to the public DCI to indicate that the public DCI is for verification of the SPS and / or CG of multiple terminal devices. Here, the public RNTI can be various appropriate representations, such as CS-RNTI, and can be appropriately set, for example, as in the CS-RNTI in the art, and will not be described in detail here.

[0143] According to some embodiments of the present disclosure, in order for the terminal side device to properly and accurately parse the public DCI, relevant information about the public DCI needs to be sent to multiple terminal side devices. In some embodiments, the processing circuit is further configured to send a common search space (CSS) configuration corresponding to the public DCI, so that the terminal side device can process the public DCI in the common search space. In particular, the CSS configuration can be configured by the base station side device and sent to the terminal side device. As an example, the CSS configuration may specifically further include candidate configuration, monitoring period (period and offset), monitoring occasion (monitoring occasion) and other configurations, and reference may be made to the configuration of the existing CSS. Optionally, it is not excluded that the candidate corresponding to the DCI may also be configured in other SSs. In some embodiments, the processing circuit is further configured to configure the format of the public DCI through RRC signaling, and configure a physical downlink control channel (PDCCH) including the public DCI in the search space of the UE.

[0144] According to an embodiment of the present disclosure, a common DCI may include a DCI for scheduling various channels. In some embodiments, the common DCI may include a DCI for scheduling a physical downlink shared channel (PDSCH), and include identification information associated with an SPS to be activated or released and identification information associated with one or more CGs or SPSs to be released. In other embodiments, the common DCI may include a DCI for scheduling a physical uplink shared channel (PUSCH), and include identification information associated with a CG to be activated or released and identification information associated with one or more SPSs or CGs to be released. In still other embodiments, the common DCI may include at least one of a synthesized DCI synthesized by a downlink DCI for scheduling a physical downlink shared channel (PDSCH) and an uplink DCI for scheduling a physical uplink shared channel (PUSCH), wherein the downlink DCI may include verification of the one or more SPSs, and the uplink DCI may include verification of the one or more CGs.

[0145] In the structural examples of the above-mentioned devices, the processing circuit can be in the form of a general-purpose processor or a dedicated processing circuit, such as an ASIC. For example, the processing circuit can be constructed by a circuit (hardware) or a central processing device (such as a central processing unit (CPU)). In addition, the processing circuit can carry a program (software) for making the circuit (hardware) or the central processing device work. The program can be stored in a memory (such as, arranged in a memory) or an external storage medium connected from the outside, and downloaded via a network (such as, the Internet).

[0146] According to one embodiment, the processing circuit 502 may include various units for implementing the above operations accordingly, for example, a sending unit 504, configured to send common downlink control information (DCI) for a terminal side device in a wireless communication system, which indicates verification of one or more semi-persistent scheduling (SPS) and / or verification of one or more configuration grants (CG) for each of a plurality of terminal side devices.

[0147] In some embodiments, the processing circuit may also include a parameter setting unit 506, which is configured to set at least one of the public CS-RNTI configuration for scrambling the public DCI, the public search space configuration corresponding to the public DCI, the public DCI size, and related information on the correspondence between the information block in the public DCI and each terminal side device, and the sending unit may be configured to send the configured parameters.

[0148] In some embodiments, the processing circuit may be further configured to scramble the common DCI using a common CS-RNTI configuration.

[0149] In some embodiments, the processing circuit may also be configured to configure radio resource control (RRC) parameters to the terminal device, the RRC parameters specifying at least one combination for the terminal device, each combination comprising one or more SPS indexes and one or more CG indexes, wherein the information block corresponding to the terminal device in the public DCI indicates one of the at least one combinations to verify the SPS identified by one or more SPS indexes in the combination and the CG identified by one or more CG indexes in the combination.

[0150] The above-mentioned various units can be operated as described above and will not be described in detail here. It should be noted that the above-mentioned various units are only logical modules divided according to the specific functions implemented, rather than being used to limit the specific implementation mode, for example, can be implemented in the form of software, hardware or a combination of software and hardware. In actual implementation, the above-mentioned various units can be implemented as independent physical entities, or can also be implemented by a single entity (for example, a processor (CPU or DSP, etc.), an integrated circuit, etc.). It should be noted that although the various units are shown as discrete units in Figure 5A, one or more of these units can also be merged into one unit, or split into multiple units. In addition, the above-mentioned various units are shown with dotted lines in the accompanying drawings to indicate that these units may not actually exist, and the operations / functions they implement can be implemented by the processing circuit itself.

[0151] It should be understood that Figure 5A is only a schematic structural configuration of the control-side electronic device. Optionally, the control-side electronic device 500 may also include other components not shown, such as memory, radio frequency link, baseband processing unit, network interface, controller, etc. The processing circuit may be associated with the memory and / or antenna. For example, the processing circuit may be directly or indirectly (for example, other components may be connected in between) connected to the memory to access data. The memory can store various information obtained and generated by the processing circuit 502. The memory may also be located within the control-side electronic device but outside the processing circuit, or even outside the control-side electronic device. The memory may be volatile memory and / or non-volatile memory. For example, the memory may include, but is not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), read-only memory (ROM), and flash memory.

[0152] For example, the processing circuit has a communication unit for various communications, such as data transmission, command communication, etc. The communication unit can be various appropriate communication components, such as an antenna, and the processing circuit can be directly or indirectly connected to the antenna to send information and receive requests / commands via the antenna. For example, as an example, the antenna can be an omnidirectional antenna and / or a directional antenna, which can be implemented in various ways, such as an antenna array (such as both an omnidirectional antenna and a directional antenna, or a single antenna array that can achieve the functions of both an omnidirectional antenna and a directional antenna) and / or a radio frequency link and other communication components, which will not be described in detail here. As an example, the antenna can also be included in the processing circuit, or outside the processing circuit. It can even be coupled / attached to the electronic device 500 without being included in the electronic device 500.

[0153] A method for a control side in a wireless communication system according to an embodiment of the present disclosure will be described below with reference to the accompanying drawings. FIG5B shows a flowchart of a method 510 for a control side in a wireless communication system according to an embodiment of the present disclosure.

[0154] In step S511 (sending step), common downlink control information (DCI) for the terminal side device in the wireless communication system is sent, which indicates the verification of one or more semi-persistent scheduling (SPS) and / or one or more configuration authorization (CG) for each terminal side device in a plurality of terminal side devices.

[0155] In some embodiments, the method may further include a parameter setting step for setting at least one of a public CS-RNTI configuration for scrambling the public DCI, a public search space configuration corresponding to the public DCI, a public DCI size, and a correspondence between information blocks in the public DCI and each terminal-side device, and the sending step may send the configured parameters. It should be noted that this step may be performed before the sending step and is optional.

[0156] In some embodiments, the method may further include a step of scrambling the public DCI using a public CS-RNTI configuration. The scrambling step may be performed before the sending step, and the step may also be included in the parameter setting step, or may be outside the parameter setting step.

[0157] In some embodiments, the method may further include configuring radio resource control (RRC) parameters to the terminal device, the RRC parameters specifying at least one combination for the terminal device, each combination comprising one or more SPS indexes and one or more CG indexes, wherein the information block corresponding to the terminal device in the public DCI indicates one of the at least one combinations to verify the SPS identified by one or more SPS indexes in the combination and the CG identified by one or more CG indexes in the combination.

[0158] It should be noted that these steps can be executed by the electronic device on the control side according to the embodiment of the present disclosure described above, for example, can be executed by corresponding units of the electronic device on the control side according to the embodiment of the present disclosure described above.

[0159] The following describes the terminal side solution according to an embodiment of the present disclosure with reference to the accompanying drawings. Figure 7A shows a block diagram of an electronic device on the terminal side according to an embodiment of the present disclosure. In the embodiment of the present disclosure, the electronic device on the terminal side can be applied to a terminal side device, such as the various terminal devices described above, especially UE, etc. For example, the terminal side electronic device can be any appropriate electronic device associated with the terminal side device, or even the terminal side device itself.

[0160] The terminal side electronic device 700 includes a processing circuit 702, which can be configured to receive common downlink control information (DCI) from the control side electronic device, which indicates the verification of one or more semi-persistent scheduling (SPS) and / or one or more configuration authorizations (CG) for each terminal side electronic device including multiple terminal side electronic devices.

[0161] In some embodiments, the terminal-side electronic device receives the common DCI via RRC signaling.

[0162] In some embodiments, the terminal side electronic device also receives at least one of a public search space configuration corresponding to the public DCI, a public DCI size, and a correspondence between an information block in the public DCI and each terminal side device.

[0163] In some embodiments, the processing circuit is further configured to perform blind detection on the received public DCI, and obtain an information block corresponding to the terminal side device associated with the electronic device from the public DCI, where the information block contains at least index information indicating the SPS and / or CG to be verified.

[0164] In some embodiments, the processing circuit can also be configured to perform SPS and / or CG verification indicated by the information block based on information in the public DCI corresponding to the terminal side device associated with the electronic device, at least based on index information.

[0165] In some embodiments, after receiving and processing the common DCI, the processing circuit may further perform feedback, such as HARQ ACK / NACK feedback.

[0166] Similarly, the terminal side electronic device can be implemented in various appropriate ways. According to one embodiment, the processing circuit 702 may include various units for implementing the above operations accordingly, for example, a receiving unit 704, which is configured to receive common downlink control information (DCI) from the control side electronic device, which indicates the verification of one or more semi-persistent scheduling (SPS) and / or one or more configuration authorizations (CG) for each terminal side electronic device including multiple terminal side electronic devices.

[0167] In some embodiments, the processing circuit may also include a detection unit 706 configured to perform blind detection on the received public DCI, thereby obtaining an information block corresponding to the electronic device from the public DCI, and the information block at least contains index information indicating the SPS and / or CG to be verified.

[0168] In some embodiments, the processing circuit may also include a verification unit 708 configured to perform SPS and / or CG verification indicated by the information block corresponding to the electronic device in the public DCI based on information, at least based on index information.

[0169] It should be noted that the above-mentioned units are merely logical modules divided according to the specific functions they implement, and are not intended to limit the specific implementation methods. Similar to the description of the control side above, they will not be described in detail here. In addition, similar to the description of the control side above, the electronic device on the receiving side may also include additional or additional units / devices, such as memory, communication units, etc., which will not be described in detail here.

[0170] A method used in a wireless communication system according to an embodiment of the present disclosure will be described below with reference to the accompanying drawings. FIG7B shows a flowchart of a method 710 used on a terminal side in a wireless communication system according to an embodiment of the present disclosure.

[0171] In step S711 (receiving step), common downlink control information (DCI) is received from the control side electronic device, which indicates verification of one or more semi-persistent scheduling (SPS) and / or one or more configuration authorization (CG) for each terminal side electronic device including multiple terminal side electronic devices.

[0172] In some embodiments, the method may further include a detection step (S712), performing a blind detection on the received public DCI, thereby obtaining an information block corresponding to the electronic device, the information block containing at least index information indicating the SPS and / or CG to be verified.

[0173] In some embodiments, the method may further include a verification step (S713), performing SPS and / or CG verification indicated by the information block based on information in the public DCI corresponding to the electronic device, at least based on index information.

[0174] It should be noted that these steps can be executed by the aforementioned terminal-side electronic device according to the embodiment of the present disclosure, in particular, by corresponding units of the aforementioned terminal-side electronic device according to the embodiment of the present disclosure.

[0175] The following will exemplarily describe an exemplary implementation of resource scheduling based on public DCI according to an embodiment of the present disclosure with reference to the accompanying drawings. It should be noted that the following description mainly uses release as an example, but it should be noted that the embodiments of the present disclosure are also applicable to activation, as well as both activation and release, and can be implemented similarly.

[0176] FIG8 shows an example of the application of a common DCI in a communication process according to an embodiment of the present disclosure, particularly for release during a communication process. In particular, as shown in FIG8 , one or more SPS / CGs, also referred to as SPS / CG occasions, may be activated by an activation DCI or a reactivation DCI to schedule resources for data transmission, and after performing certain data transmissions, a release DCI may be issued to release the SPS / CG occasion.

[0177] As an alternative to or in combination with the conventional release DCI issued for a single UE, a common release DCI can be issued for multiple UEs, which can be carried by the common DCI according to the embodiment of the present disclosure, where the number of multiple UEs is N. This solution can be used as a replacement for the conventional solution, for example, to generate and issue a common DCI for multiple UEs. This solution can be used as a supplement to the conventional solution, for example, in combination with the release DCI for a single UE, a common DCI for multiple UEs is also issued. In this way, using the common DCI alone or in conjunction with the conventional solution can save the total SPS / CG management signaling overhead.

[0178] FIG9 shows a signaling interaction diagram for applying common DCI according to an embodiment of the present disclosure.

[0179] First, the base station (e.g., gNB) sets and sends down the parameters. On the basis of the conventional RRC configuration, new RRC parameters can be added and sent down. The new RRC parameters may include parameters required to support the public DCI according to the embodiments of the present disclosure, such as the public-RNTI as described above, the public search space for public DCI, the public DCI size list or public DCI size information, information related to the position of the information block in the public DCI, and so on. In addition, in the case where the public DCI supports verification of both the SPS and CG of the terminal side device, the new RRC parameters may also include mixSPSConfigType2DeactivationStateList, which may specify at least one combination of CG indexes and at least one combination of SPS indexes, as described above. In some implementations, if the RRC is configured with a DCI size list but no public DCI size information is configured, one size in the DCI size list may be activated through MAC CE to be set as the public DCI size information, and the base station may inform each UE of the information related to the position of the information block corresponding to each UE in the public DCI.

[0180] Then, the base station sends common DCI information to multiple UEs to instruct each UE to deactivate SPS / CG. Here, the common DCI can be identified as DCI 2-8, as described above.

[0181] After receiving the public DCI, each UE blindly detects the received public DCI, obtains the index (e.g., ID / INDEX) of the deactivated SPS / CG, and then deactivates the SPS / CG indicated by the ID / INDEX. In particular, if the information block of the public DCI specifies effective time information for the UE, the indicated SPS / CG can be deactivated after the effective time. As another example, if there is no effective time information, the indicated SPS / CG can be deactivated immediately.

[0182] Finally, each UE feeds back HARQ ACK / NACK for the common DCI to the base station.

[0183] The following will describe the base station control resource allocation implemented via public DCI according to an embodiment of the present disclosure in conjunction with the accompanying drawings. Figure 10A shows the base station resource allocation status when conventional scheduling DCI is issued UE by UE to perform operations. It can be seen that the resource allocation for each UE is scattered and the resource utilization efficiency is low. In particular, in the conventional implementation, the activation and release of SPS / CG require separate DCI. This ultimately results in a large number of SPS and CG configurations and real-time / flexible SPS / CG verification DCI issuance. In order to blindly detect each DCI, the UE needs to traverse the PDCCH search space, resulting in a large amount of energy consumption.

[0184] In contrast, in an embodiment of the present disclosure, the scheduling DCI for each UE can be centralized by utilizing common DCI, thereby reducing blind detection overhead, enabling batch verification of the SPS / CG of multiple users, especially batch release, thereby improving the resource utilization efficiency of PDCCH, as shown in FIG10B .

[0185] In particular, on the one hand, since the blind detection order of DCI decoding is to decode the public DCI candidates first and then the scheduling DCI candidates, compared with the conventional use of scheduling DCI to indicate the SPS / CG deactivation of the UE, the public DCI indication according to the present disclosure has fewer blind detection times, thereby saving UE blind detection energy consumption and improving UE energy saving.

[0186] In addition, when conventionally using a scheduling DCI for each UE to indicate a release, the DCI still contains fields such as FDRA, MCS, and RV (default values). Correctly decoding these fields is only used to characterize the SPS / CG release operation. The specific values ​​of these fields have no practical significance, which is equivalent to wasting the UE's ability to correctly decode (decoded but not used much). However, according to the embodiment of the present disclosure, these fields may not be included in the public DCI design, so that the SPS / CG release indication for each UE may only require about 10 bits. Therefore, the conventional scheduling DCI size (for example, a maximum of 140 bits) used to indicate a release to a UE will be much larger (14 times) than the number of bits required for the public DCI to indicate a release to a UE. In other words, the number of bits required for a scheduling DCI in the original conventional scheme to implement a UE release indication can support the release indication of multiple (14) UEs in the indication framework of the public DCI format. Therefore, the release indication efficiency is improved: the release indication efficiency is improved many times (14 times), and the energy consumption of the public framework is even lower.

[0187] In addition, when the common DCI according to the embodiment of the present disclosure is applied to indicate DCI for multiple UEs, PDCCH resources can be greatly saved, even several times. The saved PDCCH resources can be used to enhance the reliability of other scheduled DCIs, thereby achieving enhanced data scheduling capacity, and can also be used to support other normal data scheduling DCIs to be sent with a larger AL, thereby improving DCI decoding accuracy, performing timely PDSCH data scheduling, and avoiding DCI decoding errors that lead to inability to receive PDSCH and resulting in throughput loss and increased data scheduling delay caused by DCI retransmission. On the other hand, it can also be directly used to support more UEs to achieve capacity enhancement.

[0188] Furthermore, in scenarios involving multi-user, multi-data stream, and large data volumes, conventional UE-by-UE DCI scheduling, using limited PDCCH resources, can result in some low-priority data being delayed. However, the disclosed solution utilizes public DCI to conserve PDCCH resources. These saved PDCCH resources can be used to schedule DCI in the current time slot that would otherwise be delayed to the next time slot due to insufficient PDCCH resources. This reduces packet transmission latency and better meets XR packet delay budget (PDB) requirements.

[0189] The following will describe the use of SPS&CG simultaneous verification according to an embodiment of the present disclosure in conjunction with an exemplary XR business scenario. It should be noted that XR business is only an example listed for ease of understanding and is not intended to limit the scope of application of the technology of the present disclosure. For ease of understanding, an AR scenario model is assumed here. The data flow of the business includes two downlink (DL) data streams (I stream + P stream) and at least one uplink (UL) data stream.

[0190] It should be pointed out that in the implementation example according to the embodiment of the present disclosure, corresponding activation and / or release can be performed after the data stream arrives. For example, when data transmission is required after the transmission data stream arrives, the corresponding resource scheduling can be activated; or when the data stream transmission is relatively small or basically completed, in order to save resources, the corresponding resource scheduling can be released, thereby performing flexible resource scheduling.

[0191] Figure 11A shows a signaling flow chart for a first example. In this example, applying common DCI to multiple UEs can achieve at least one of CG release and SPS release. The base station configures and issues RRC parameters for the multiple UEs. Furthermore, the base station configures a common DCI format and a search space including PDCCH candidates carrying the DCI, such as the common DCI according to an exemplary embodiment of the present disclosure, for the multiple UEs via RRC signaling.

[0192] After the downlink data flow (DL flow) arrives, the base station can send an SPS activation DCI to each UE, and after receiving verification feedback (e.g., HARQ-ACK) from the UE, perform downlink data transmission. After a period of transmission, if the data to be transmitted is basically transmitted, the relevant resources can be released by sending an SPS release DCI. Here, the sending of the SPS release DCI can adopt a conventional release DCI method, that is, sending an SPS release DCI to each UE one by one to achieve resource release, and receiving verification feedback (e.g., HARQ-ACK) from the UE. Additionally or alternatively, the public DCI disclosed in the present invention can also be sent, so that each UE can blindly detect the public DCI and obtain the information of the information block in the public DCI corresponding thereto, so that the SPS release can be performed based on the information of the information block, especially the SPS indicated by the index information therein. It should be noted that the SPS release here is only optional, and is therefore indicated by a dotted line in the accompanying drawings.

[0193] Then, after the uplink data flow (UL flow) arrives, the base station can send a CG activation DCI to each UE, and each UE can perform uplink data transmission after receiving and verifying the CG activation DCI. After a period of transmission, if the data to be transmitted is basically transmitted, the relevant resources can be released by sending a CG release DCI. The CG release DCI here can be sent in a conventional manner, such as sending the CG release DCI for each UE one by one, and additionally or alternatively, the public DCI disclosed in the present invention can also be sent, so that each UE can blindly detect the public DCI and obtain the information of the corresponding information block in the public DCI, so that the CG release can be performed based on the information of the information block, especially the CG indicated by the index information therein.

[0194] Although the figure shows that the common scheduling DCI involves either CG release or SPS release, for example, the common scheduling DCI involves SPS release after downlink data transmission, and the common scheduling DCI involves CG release after uplink data transmission, it should be noted that in the implementation of this example, the common scheduling DCI may involve both CG release and SPS release. For example, it is possible to consider not performing SPS release after downlink data transmission, but performing both SPS release and CG release through common scheduling DCI after uplink data transmission.

[0195] It should be noted that although the figure shows that downlink data transmission is performed first and then uplink data transmission, this data flow order is merely exemplary. In some implementations, uplink data transmission may be performed first and then downlink data transmission. Accordingly, in a manner similar to the above signaling, CG release may be performed first using common scheduling DCI, and then SPS release may be performed using common scheduling DCI, the latter performing both CG release and SPS release.

[0196] FIG11B shows a signaling flow chart for a second example. In this example, a common DCI is applied to multiple UEs to implement at least one of releasing and activating SPS / CG. The base station configures and issues RRC parameters for the multiple UEs. Furthermore, the base station configures a common DCI format and a search space including PDCCH candidates carrying the DCI for the multiple UEs via RRC signaling, such as the common DCI according to an exemplary embodiment of the present disclosure, similar to FIG11A .

[0197] After the downlink data stream (DL stream) arrives, the base station can send an SPS activation DCI to each UE and perform downlink data transmission after receiving verification feedback (e.g., HARQ-ACK) from the UE. After a period of transmission, if the data to be transmitted is basically completed, the relevant resources can be released by sending an SPS release DCI. Here, the SPS release DCI can be sent in a conventional release DCI manner. Additionally or alternatively, the public DCI of the present disclosure can also be sent, similar to Figure 11A.

[0198] At this time, when the uplink data flow arrives, the base station can send a CG activation DCI to each UE. The CG activation DCI here can be sent in a conventional activation DCI manner, that is, the CG activation DCI for the UE is sent one by one. Additionally or alternatively, a public scheduling DCI can be used to perform CG activation, so that each UE can blindly detect the public DCI and obtain the information of the corresponding information block in the public DCI, so that the CG release can be performed based on the information of the information block, especially the CG indicated by the index information. In addition, in another implementation, it is set to use public scheduling DCI to perform both SPS release and CG activation. It should be noted that the CG activation using public DCI here is only optional, and is therefore indicated by a dotted line in the accompanying drawings.

[0199] Then, after a period of transmission, if the data to be transmitted is basically transmitted, the relevant resources can be released by sending a CG release DCI. The CG release DCI here can be sent in a conventional manner, and in addition or alternatively, the public DCI disclosed in the present invention can also be sent. In addition, it should be noted that in the implementation of this example, the public scheduling DCI may involve both CG release and SPS release. For example, it can be considered that no SPS release is performed after downlink data transmission, and after uplink data transmission, both SPS release and CG release are performed through public scheduling DCI.

[0200] It should be noted that although the figure shows downlink data transmission first and then uplink data transmission, this data flow order is merely exemplary. In some implementations, uplink data transmission may be performed first and then downlink data transmission. Accordingly, in a manner similar to the above signaling, common scheduling DCI is used to perform at least one of SPS / CG release and activation.

[0201] In addition, it should be noted that the use of public scheduling DCI in this example to perform at least one of SPS / CG release and activation can also be applied to only downlink data flow, or only downlink data flow. In particular, as an example, if a new downlink data flow arrives after a period of time after the previous downlink data transmission, an SPS activation DCI can be issued here to schedule resources for data transmission, and additionally or alternatively, depending on the situation of the previous downlink data transmission, an SPS release DCI can also be issued to release the previously utilized resources. Here, the SPS activation, SPS release, and even both the SPS activation and SPS release can be issued for execution using the public scheduling DCI disclosed in the present invention. This also applies to the situation where a new uplink data flow arrives after a period of time after the previous uplink data transmission.

[0202] Figure 11C shows a signaling flow chart for a third example. In this example, applying common DCI to multiple UEs can achieve at least one of CG activation and SPS activation. The base station configures and issues RRC parameters for the multiple UEs. Furthermore, the base station configures a common DCI format and a search space including PDCCH candidates carrying the DCI, such as the common DCI according to an exemplary embodiment of the present disclosure, for the multiple UEs via RRC signaling.

[0203] After the downlink data flow (DL flow) arrives, the base station can send SPS activation DCI to each UE. The SPS activation DCI here can be sent in a conventional manner, and additionally or alternatively, the public DCI disclosed in this disclosure can also be sent, similar to Figure 11B.

[0204] Then, after the uplink data stream (UL stream) arrives, the base station can send a CG activation DCI to each UE. The CG activation DCI here can be sent in a conventional manner, and additionally or alternatively, the public DCI of the present disclosure can also be sent, similar to Figure 11B. It should be noted that in the implementation of this example, the public scheduling DCI may involve both CG activation and SPS activation. For example, after both the uplink data stream and the downlink data stream arrive, the public scheduling DCI is sent to perform both CG activation and SPS activation.

[0205] Then, for the activated DCI, upon receiving verification feedback (eg, HARQ-ACK) from the UE, corresponding data transmission, such as uplink data transmission and downlink data transmission, may be performed.

[0206] It should be noted that the above description is merely exemplary. The embodiments of the present disclosure may also be implemented in any other appropriate manner, while still achieving the advantageous effects obtained by the embodiments of the present disclosure. Moreover, the embodiments of the present disclosure may also be applied to other similar application examples, while still achieving the advantageous effects obtained by the embodiments of the present disclosure.

[0207] It should be understood that the machine-executable instructions in the machine-readable storage medium or program product according to the embodiments of the present disclosure can be configured to perform operations corresponding to the above-mentioned device and method embodiments. When referring to the above-mentioned device and method embodiments, the embodiments of the machine-readable storage medium or program product are clear to those skilled in the art and are therefore not described again. Machine-readable storage media and program products for carrying or including the above-mentioned machine-executable instructions also fall within the scope of the present disclosure. Such storage media may include, but are not limited to, floppy disks, optical disks, magneto-optical disks, memory cards, memory sticks, and the like.

[0208] In addition, it should be understood that the above series of processes and devices can also be implemented by software and / or firmware. In the case of implementation by software and / or firmware, it is uploaded from a storage medium or network to a computer with a dedicated hardware structure and installed to implement various operations according to the embodiments of the present disclosure.

[0209] [Application Examples of the Present Disclosure]

[0210] Figure 12 shows an example block diagram of a computer that can be implemented as a terminal device or a control device according to an embodiment of the present disclosure. For example, the computer shown in Figure 12 can be installed with programs that constitute the software, and when the computer is installed with various programs, it can perform various operations, functions, etc. according to the embodiments of the present disclosure.

[0211] 12 , a central processing unit (CPU) 1301 executes various processes according to a program stored in a read-only memory (ROM) 1302 or a program loaded from a storage section 1308 to a random access memory (RAM) 1303. In the RAM 1303, data required when the CPU 1301 executes various processes and the like is also stored as needed.

[0212] The CPU 1301, the ROM 1302, and the RAM 1303 are connected to one another via a bus 1304. An input / output interface 1305 is also connected to the bus 1304.

[0213] The following components are connected to the input / output interface 1305: an input section 1306 including a keyboard, a mouse, etc.; an output section 1307 including a display such as a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 1308 including a hard disk, etc.; and a communication section 1309 including a network interface card such as a LAN card, a modem, etc. The communication section 1309 performs communication processing via a network such as the Internet.

[0214] A drive 1310 is also connected to the input / output interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is mounted on the drive 1310 as needed so that a computer program read therefrom is installed in the storage section 1308 as needed.

[0215] In the case of realizing the above-described series of processing by software, a program constituting the software is installed from a network such as the Internet or a storage medium such as the removable medium 1311 .

[0216] Those skilled in the art will appreciate that such storage media are not limited to the removable media 1311 shown in FIG12 , which stores programs therein and is distributed separately from the device to provide the programs to users. Examples of the removable media 1311 include magnetic disks (including floppy disks (registered trademark)), optical disks (including compact disk read-only memories (CD-ROMs) and digital versatile disks (DVDs)), magneto-optical disks (including minidiscs (MDs) (registered trademark)), and semiconductor memories. Alternatively, the storage medium may be the ROM 1302, a hard disk included in the storage section 1308, or the like, in which the programs are stored and distributed to users together with the device containing them.

[0217] The techniques described in this disclosure can be applied to a variety of products.

[0218] For example, the electronic device 500 according to an embodiment of the present disclosure may be implemented as various base stations or installed in a base station, and the electronic device 700 may be implemented as various user equipments or installed in various user equipments.

[0219] The communication method according to the embodiments of the present disclosure can be implemented by various base stations or user equipment; the methods and operations according to the embodiments of the present disclosure can be embodied as computer-executable instructions, stored in a non-temporary computer-readable storage medium, and can be executed by various base stations or user equipment to implement one or more functions described above.

[0220] The technology according to the embodiments of the present disclosure can be made into various computer program products, which can be used in various base stations or user equipments to implement one or more functions described above.

[0221] The base station referred to in this disclosure can be implemented as any type of base station, preferably, such as the macro gNB and ng-eNB defined in the 3GPP 5GNR standard. The gNB can be a gNB that covers a cell smaller than a macro cell, such as a pico gNB, micro gNB, and home (femto) gNB. Alternatively, the base station can be implemented as any other type of base station, such as a NodeB, eNodeB, and base transceiver station (BTS). The base station may also include: a main body configured to control wireless communications and one or more remote radio heads (RRHs) located separately from the main body, wireless relay stations, drone towers, control nodes in automated factories, etc.

[0222] The user equipment can be implemented as a mobile terminal (such as a smartphone, a tablet personal computer (PC), a notebook PC, a portable game terminal, a portable / dongle-type mobile router, and a digital camera) or an in-vehicle terminal (such as a car navigation device). The user equipment can also be implemented as a terminal that performs machine-to-machine (M2M) communication (also known as a machine-type communication (MTC) terminal), a drone, a sensor and actuator in an automated factory, etc. In addition, the user equipment can be a wireless communication module (such as an integrated circuit module including a single chip) installed on each of the above terminals.

[0223] First application example of base station

[0224] FIG13 is a block diagram illustrating a first example of a schematic configuration of a base station to which the techniques of this disclosure may be applied. In FIG13 , the base station may be implemented as gNB 1400. gNB 1400 includes multiple antennas 1410 and base station equipment 1420. Base station equipment 1420 and each antenna 1410 may be connected to each other via an RF cable. In one implementation, gNB 1400 (or base station equipment 1420) herein may correspond to the aforementioned control-side device.

[0225] Antenna 1410 includes multiple antenna elements. Antenna 1410 can be arranged in an antenna array matrix, for example, and used by base station device 1420 to transmit and receive wireless signals. For example, multiple antennas 1410 can be compatible with multiple frequency bands used by gNB 1400.

[0226] The base station device 1420 includes a controller 1421 , a memory 1422 , a network interface 1423 , and a wireless communication interface 1425 .

[0227] The controller 1421 may be, for example, a CPU or DSP, and operates various higher-layer functions of the base station device 1420. For example, the controller 1421 may include the processing circuit 502 described above, execute the communication method described in FIG. 5B , or control various components of the base station device. For example, the controller 1421 generates data packets based on data in the signal processed by the wireless communication interface 1425 and transmits the generated packets via the network interface 1423. The controller 1421 may bundle data from multiple baseband processors to generate bundled packets and transmit the generated bundled packets. The controller 1421 may have logic functions for performing control such as radio resource control, radio bearer control, mobility management, admission control, and scheduling. This control may be performed in conjunction with nearby gNBs or core network nodes. The memory 1422 includes RAM and ROM and stores programs executed by the controller 1421 and various types of control data (such as terminal lists, transmission power data, and scheduling data).

[0228] The network interface 1423 is a communication interface for connecting the base station device 1420 to the core network 1424 (e.g., a 5G core network). The controller 1421 can communicate with the core network node or another gNB via the network interface 1423. In this case, the gNB 1400 and the core network node or other gNB can be connected to each other via logical interfaces (such as NG interfaces and Xn interfaces). The network interface 1423 can also be a wired communication interface or a wireless communication interface for wireless backhaul. If the network interface 1423 is a wireless communication interface, the network interface 1423 can use a higher frequency band for wireless communication than the frequency band used by the wireless communication interface 1425.

[0229] The wireless communication interface 1425 supports any cellular communication scheme (such as 5G NR) and provides wireless connectivity to terminals located in the cell of the gNB 1400 via the antenna 1410. The wireless communication interface 1425 may typically include, for example, a baseband (BB) processor 1426 and RF circuitry 1427. The BB processor 1426 can perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and various types of signal processing at various layers (e.g., the physical layer, MAC layer, RLC layer, PDCP layer, and SDAP layer). In place of the controller 1421, the BB processor 1426 may perform some or all of the aforementioned logical functions. The BB processor 1426 may be a memory that stores communication control programs, or a module including a processor configured to execute programs and associated circuitry. Program updates can modify the functionality of the BB processor 1426. This module may be a card or blade inserted into a slot in the base station device 1420. Alternatively, it may be a chip mounted on the card or blade. Meanwhile, the RF circuit 1427 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 1410. Although FIG13 shows an example in which one RF circuit 1427 is connected to one antenna 1410, the present disclosure is not limited to this illustration, and one RF circuit 1427 may be connected to multiple antennas 1410 at the same time.

[0230] As shown in Figure 13 , the wireless communication interface 1425 may include multiple BB processors 1426. For example, multiple BB processors 1426 may be compatible with multiple frequency bands used by gNB 1400. As shown in Figure 13 , the wireless communication interface 1425 may include multiple RF circuits 1427. For example, multiple RF circuits 1427 may be compatible with multiple antenna elements. While Figure 13 illustrates an example in which the wireless communication interface 1425 includes multiple BB processors 1426 and multiple RF circuits 1427, the wireless communication interface 1425 may also include a single BB processor 1426 or a single RF circuit 1427.

[0231] In the gNB 1400 shown in FIG13 , one or more units (e.g., the transmitting unit 504) included in the processing circuit 502 described with reference to FIG5A may be implemented in the wireless communication interface 1425. Alternatively, at least a portion of these components may be implemented in the controller 1421. For example, the gNB 1400 may include a portion (e.g., the BB processor 1426) or the entirety of the wireless communication interface 1425, and / or include a module of the controller 1421, and one or more components may be implemented in the module. In this case, the module may store a program that allows the processor to function as one or more components (in other words, a program that allows the processor to perform the operations of one or more components) and may execute the program. As another example, the program that allows the processor to function as one or more components may be installed in the gNB 1400, and the wireless communication interface 1425 (e.g., the BB processor 1426) and / or the controller 1421 may execute the program. As described above, gNB 1400, base station device 1420, or a module may be provided as a device including one or more components, and a program for allowing a processor to function as one or more components may be provided. In addition, a readable medium having the program recorded therein may be provided.

[0232] Second application example of base station

[0233] FIG14 is a block diagram illustrating a second example of a schematic configuration of a base station to which the technology of the present disclosure can be applied. In FIG14 , the base station is illustrated as a gNB 1530. The gNB 1530 includes multiple antennas 1540, a base station device 1550, and an RRH 1560. The RRH 1560 and each antenna 1540 can be connected to each other via an RF cable. The base station device 1550 and the RRH 1560 can be connected to each other via a high-speed line such as an optical fiber cable. In one implementation, the gNB 1530 (or base station device 1550) herein may correspond to the base station device 200 described above.

[0234] Antenna 1540 includes multiple antenna elements. Antenna 1540 can be arranged in an antenna array matrix, for example, and is used by base station device 1550 to transmit and receive wireless signals. For example, multiple antennas 1540 can be compatible with multiple frequency bands used by gNB 1530.

[0235] Base station device 1550 includes a controller 1551, a memory 1552, a network interface 1553, a wireless communication interface 1555, and a connection interface 1557. Controller 1551, memory 1552, and network interface 1553 are the same as controller 1421, memory 1422, and network interface 1423 described with reference to FIG.

[0236] The wireless communication interface 1555 supports any cellular communication scheme (such as 5G NR) and provides wireless communication to terminals located in the sector corresponding to the RRH 1560 via the RRH 1560 and the antenna 1540. The wireless communication interface 1555 may generally include, for example, a BB processor 1556. The BB processor 1556 is identical to the BB processor 1426 described with reference to FIG. 13 , except that the BB processor 1556 is connected to the RF circuit 1564 of the RRH 1560 via the connection interface 1557. As shown in FIG. 14 , the wireless communication interface 1555 may include multiple BB processors 1556. For example, multiple BB processors 1556 may be compatible with multiple frequency bands used by the gNB 1530. Although FIG. 14 illustrates an example in which the wireless communication interface 1555 includes multiple BB processors 1556, the wireless communication interface 1555 may also include a single BB processor 1556.

[0237] The connection interface 1557 is an interface for connecting the base station device 1550 (wireless communication interface 1555) to the RRH 1560. The connection interface 1557 may also be a communication module for connecting the base station device 1550 (wireless communication interface 1555) to the RRH 1560 for communication in the high-speed line.

[0238] The RRH 1560 includes a connection interface 1561 and a wireless communication interface 1563 .

[0239] The connection interface 1561 is an interface for connecting the RRH 1560 (wireless communication interface 1563) to the base station device 1550. The connection interface 1561 may also be a communication module for communication in the above-mentioned high-speed line.

[0240] The wireless communication interface 1563 transmits and receives wireless signals via the antenna 1540. The wireless communication interface 1563 may generally include, for example, an RF circuit 1564. The RF circuit 1564 may include, for example, a mixer, a filter, and an amplifier, and transmits and receives wireless signals via the antenna 1540. Although FIG14 shows an example in which one RF circuit 1564 is connected to one antenna 1540, the present disclosure is not limited to this illustration, and one RF circuit 1564 may be connected to multiple antennas 1540 simultaneously.

[0241] As shown in FIG14 , the wireless communication interface 1563 may include multiple RF circuits 1564. For example, multiple RF circuits 1564 may support multiple antenna elements. Although FIG14 shows an example in which the wireless communication interface 1563 includes multiple RF circuits 1564, the wireless communication interface 1563 may also include a single RF circuit 1564.

[0242] In the gNB 1500 shown in FIG14 , one or more units (e.g., the transmitting unit 504) included in the processing circuit 502 described with reference to FIG5A may be implemented in the wireless communication interface 1525. Alternatively, at least a portion of these components may be implemented in the controller 1521. For example, the gNB 1500 may include a portion (e.g., the BB processor 1526) or the entirety of the wireless communication interface 1525 and / or include a module of the controller 1521, and one or more components may be implemented in the module. In this case, the module may store a program that allows the processor to function as one or more components (in other words, a program that allows the processor to perform the operations of one or more components) and may execute the program. As another example, the program that allows the processor to function as one or more components may be installed in the gNB 1500, and the wireless communication interface 1525 (e.g., the BB processor 1526) and / or the controller 1521 may execute the program. As described above, gNB 1500, base station device 1520, or a module may be provided as a device including one or more components, and a program for allowing a processor to function as one or more components may be provided. In addition, a readable medium having the program recorded therein may be provided.

[0243] First application example of user equipment

[0244] 15 is a block diagram illustrating an example of a schematic configuration of a communication device to which the technology of the present disclosure may be applied. In one example, the communication device may be implemented as a smartphone 1600 , which may be implemented as the electronic device 700 described in the present disclosure.

[0245] The smart phone 1600 includes a processor 1601, a memory 1602, a storage device 1603, an external connection interface 1604, a camera 1606, a sensor 1607, a microphone 1608, an input device 1609, a display device 1610, a speaker 1611, a wireless communication interface 1612, one or more antenna switches 1615, one or more antennas 1616, a bus 1617, a battery 1618 and an auxiliary controller 1619.

[0246] The processor 1601 may be, for example, a CPU or a system on a chip (SoC), and controls the functions of the application layer and other layers of the smartphone 1600. The processor 1601 may include or function as the processing circuit 702 described with reference to FIG7A. The memory 1602 includes RAM and ROM, and stores data and programs executed by the processor 1601 to implement the communication method described with reference to FIG7B. The storage device 1603 may include a storage medium such as a semiconductor memory and a hard disk. The external connection interface 1604 is an interface for connecting an external device (such as a memory card and a universal serial bus (USB) device) to the smartphone 1600.

[0247] The camera 1606 includes an image sensor (such as a charge coupled device (CCD) and a complementary metal oxide semiconductor (CMOS)) and generates a captured image. The sensor 1607 may include a group of sensors such as a measurement sensor, a gyroscope sensor, a geomagnetic sensor, and an acceleration sensor. The microphone 1608 converts the sound input to the smartphone 1600 into an audio signal. The input device 1609 includes, for example, a touch sensor, a keypad, a keyboard, a button, or a switch configured to detect a touch on the screen of the display device 1610, and receives an operation or information input from the user. The display device 1610 includes a screen (such as a liquid crystal display (LCD) and an organic light emitting diode (OLED) display) and displays the output image of the smartphone 1600. The speaker 1611 converts the audio signal output from the smartphone 1600 into sound.

[0248] The wireless communication interface 1612 supports any cellular communication scheme (such as 4G LTE or 5G NR, etc.) and performs wireless communication. The wireless communication interface 1612 may generally include, for example, a BB processor 1613 and an RF circuit 1614. The BB processor 1613 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 1614 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 1616. The wireless communication interface 1612 may be a chip module on which the BB processor 1613 and the RF circuit 1614 are integrated. As shown in FIG. 15 , the wireless communication interface 1612 may include multiple BB processors 1613 and multiple RF circuits 1614. Although FIG. 15 shows an example in which the wireless communication interface 1612 includes multiple BB processors 1613 and multiple RF circuits 1614, the wireless communication interface 1612 may also include a single BB processor 1613 or a single RF circuit 1614.

[0249] In addition, in addition to the cellular communication scheme, the wireless communication interface 1612 can support other types of wireless communication schemes, such as a short-range wireless communication scheme, a near field communication scheme, and a wireless local area network (LAN) scheme. In this case, the wireless communication interface 1612 may include a BB processor 1613 and an RF circuit 1614 for each wireless communication scheme.

[0250] Each of the antenna switches 1615 switches the connection destination of the antenna 1616 between a plurality of circuits (eg, circuits for different wireless communication schemes) included in the wireless communication interface 1612 .

[0251] The antenna 1616 includes a plurality of antenna elements. The antenna 1616 may be arranged in an antenna array matrix, for example, and is used for the wireless communication interface 1612 to transmit and receive wireless signals. The smartphone 1600 may include one or more antenna panels (not shown).

[0252] In addition, the smartphone 1600 may include an antenna 1616 for each wireless communication scheme. In this case, the antenna switch 1615 may be omitted from the configuration of the smartphone 1600.

[0253] The bus 1617 connects the processor 1601, the memory 1602, the storage device 1603, the external connection interface 1604, the camera 1606, the sensor 1607, the microphone 1608, the input device 1609, the display device 1610, the speaker 1611, the wireless communication interface 1612, and the auxiliary controller 1619. The battery 1618 supplies power to the various blocks of the smartphone 1600 shown in FIG15 via feeders, which are partially shown as dashed lines in the figure. The auxiliary controller 1619 operates the minimum necessary functions of the smartphone 1600, for example, in sleep mode.

[0254] In the smartphone 1600 shown in FIG15 , one or more components included in the processing circuit may be implemented in the wireless communication interface 1612, such as the receiving unit 704 of the processing circuit 702 described with reference to FIG7A . Alternatively, at least a portion of these components may be implemented in the processor 1601 or the auxiliary controller 1619. As an example, the smartphone 1600 includes a portion (e.g., the BB processor 1613) or the entirety of the wireless communication interface 1612, and / or a module including the processor 1601 and / or the auxiliary controller 1619, and one or more components may be implemented in the module. In this case, the module may store a program that allows the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of one or more components) and may execute the program. As another example, a program for allowing the processor to function as one or more components may be installed in the smartphone 1600, and the wireless communication interface 1612 (e.g., the BB processor 1613), the processor 1601, and / or the auxiliary controller 1619 may execute the program. As described above, the smartphone 1600 or module may be provided as a device including one or more components, and a program for allowing a processor to function as one or more components may be provided. In addition, a readable medium having the program recorded therein may be provided.

[0255] Second application example of user equipment

[0256] Figure 16 is a block diagram showing an example of a schematic configuration of a car navigation device 1720 to which the technology of the present disclosure can be applied. The car navigation device 1720 can be implemented as the electronic device 700 described with reference to Figure 7A. The car navigation device 1720 includes a processor 1721, a memory 1722, a global positioning system (GPS) module 1724, a sensor 1725, a data interface 1726, a content player 1727, a storage medium interface 1728, an input device 1729, a display device 1730, a speaker 1731, a wireless communication interface 1733, one or more antenna switches 1736, one or more antennas 1737, and a battery 1738. In one example, the car navigation device 1720 can be implemented as a UE described in the present disclosure.

[0257] The processor 1721 may be, for example, a CPU or an SoC, and controls a navigation function and other functions of the car navigation device 1720. The memory 1722 includes a RAM and a ROM, and stores data and programs executed by the processor 1721.

[0258] The GPS module 1724 uses GPS signals received from GPS satellites to measure the position (such as latitude, longitude, and altitude) of the car navigation device 1720. The sensor 1725 may include a group of sensors such as a gyroscope sensor, a geomagnetic sensor, and an air pressure sensor. The data interface 1726 is connected to, for example, the vehicle network 1741 via a terminal not shown, and obtains data generated by the vehicle (such as vehicle speed data).

[0259] The content player 1727 reproduces content stored in a storage medium (such as a CD or DVD) inserted into the storage medium interface 1728. The input device 1729 includes, for example, a touch sensor, button, or switch configured to detect a touch on the screen of the display device 1730, and receives operations or information input from the user. The display device 1730 includes a screen such as an LCD or OLED display and displays images of the navigation function or reproduced content. The speaker 1731 outputs sounds of the navigation function or reproduced content.

[0260] The wireless communication interface 1733 supports any cellular communication scheme (such as 4G LTE or 5G NR) and performs wireless communication. The wireless communication interface 1733 may generally include, for example, a BB processor 1734 and an RF circuit 1735. The BB processor 1734 may perform, for example, encoding / decoding, modulation / demodulation, and multiplexing / demultiplexing, and perform various types of signal processing for wireless communication. Meanwhile, the RF circuit 1735 may include, for example, a mixer, a filter, and an amplifier, and transmit and receive wireless signals via an antenna 1737. The wireless communication interface 1733 may also be a chip module on which the BB processor 1734 and the RF circuit 1735 are integrated. As shown in FIG16 , the wireless communication interface 1733 may include multiple BB processors 1734 and multiple RF circuits 1735. Although FIG16 shows an example in which the wireless communication interface 1733 includes multiple BB processors 1734 and multiple RF circuits 1735, the wireless communication interface 1733 may also include a single BB processor 1734 or a single RF circuit 1735.

[0261] In addition, in addition to the cellular communication scheme, the wireless communication interface 1733 can support other types of wireless communication schemes, such as short-range wireless communication schemes, near field communication schemes, and wireless LAN schemes. In this case, for each wireless communication scheme, the wireless communication interface 1733 can include a BB processor 1734 and an RF circuit 1735.

[0262] Each of the antenna switches 1736 switches a connection destination of the antenna 1737 between a plurality of circuits included in the wireless communication interface 1733 , such as circuits for different wireless communication schemes.

[0263] The antenna 1737 includes a plurality of antenna elements and may be arranged in an antenna array matrix, for example, and is used by the wireless communication interface 1733 to transmit and receive wireless signals.

[0264] In addition, the car navigation device 1720 may include an antenna 1737 for each wireless communication scheme. In this case, the antenna switch 1736 may be omitted from the configuration of the car navigation device 1720.

[0265] The battery 1738 supplies power to the respective blocks of the car navigation device 1720 shown in Fig. 16 via a feeder line, which is partially shown as a dotted line in the figure. The battery 1738 accumulates the power supplied from the vehicle.

[0266] In the car navigation device 1720 shown in FIG16 , one or more components included in the processing circuit may be implemented in the wireless communication interface 1733, such as the receiving unit 704 of the processing circuit 702 described with reference to FIG7A . Alternatively, at least a portion of these components may be implemented in the processor 1721. As an example, the car navigation device 1720 includes a portion (e.g., the BB processor 1734) or the entirety of the wireless communication interface 1733, and / or a module including the processor 1721, and one or more components may be implemented in the module. In this case, the module may store a program that allows the processor to function as one or more components (in other words, a program for allowing the processor to perform the operations of one or more components) and may execute the program. As another example, a program for allowing the processor to function as one or more components may be installed in the car navigation device 1720, and the wireless communication interface 1733 (e.g., the BB processor 1734) and / or the processor 1721 may execute the program. As described above, the car navigation device 1720 or a module may be provided as a device including one or more components, and a program for allowing the processor to function as one or more components may be provided. In addition, a readable medium having the program recorded therein can be provided.

[0267] The technology of the present disclosure can also be implemented as an in-vehicle system (or vehicle) 1740 including a car navigation device 1720, an in-vehicle network 1741, and one or more blocks of a vehicle module 1742. The vehicle module 1742 generates vehicle data (such as vehicle speed, engine speed, and fault information) and outputs the generated data to the in-vehicle network 1741.

[0268] The exemplary embodiments of the present disclosure are described above with reference to the accompanying drawings, but the present disclosure is certainly not limited to the above examples. Those skilled in the art may obtain various changes and modifications within the scope of the appended claims, and it should be understood that these changes and modifications will naturally fall within the technical scope of the present disclosure.

[0269] For example, a plurality of functions included in one unit in the above embodiments may be implemented by separate devices. Alternatively, a plurality of functions implemented by a plurality of units in the above embodiments may be implemented by separate devices, respectively. In addition, one of the above functions may be implemented by a plurality of units. Needless to say, such a configuration is included in the technical scope of the present disclosure.

[0270] In this specification, the steps described in the flowchart include not only processing executed in time series in the order described, but also processing executed in parallel or individually rather than necessarily in time series. In addition, even in the steps processed in time series, it goes without saying that the order can be changed as appropriate.

[0271] In addition, embodiments of the present disclosure may further include the following illustrative examples (EE).

[0272] EE 1. An electronic device on the control side of a wireless communication system, comprising a processing circuit, which is configured to send common downlink control information (DCI) for a terminal side device in the wireless communication system, indicating at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in a plurality of terminal side devices.

[0273] EE 2. An electronic device as described in EE 1, wherein the common downlink control information (DCI) includes an information block for each terminal side device respectively to indicate at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) of the terminal side device.

[0274] EE 3. The electronic device as described in EE 1, wherein, for each terminal side device, the information block includes index information indicating at least one of one or more SPSs to be released and one or more CGs to be released.

[0275] EE 4. An electronic device as described in EE 3, wherein the index information of the SPS and / or CG includes a HARQ ID associated with a separate SPS or CG, or an index associated with a group of SPSs or a group of CGs or a group containing both SPSs and CGs.

[0276] EE 5. The electronic device according to EE 1, wherein, for each terminal-side device, the information block further includes at least one of the following information:

[0277] Type information indicating whether to perform release of semi-persistent scheduling (SPS) or release of configuration grant (CG);

[0278] Operation information, which indicates whether the operation involves a release,

[0279] Stream information, which indicates to which stream the SPS and / or CG indicated by the index information in the information block belongs; and

[0280] The effective time information indicates how long the terminal side device should execute the release indicated by the public DCI after receiving the public DCI.

[0281] EE 6. The electronic device according to EE 1, wherein the processing circuit is further configured to set at least one of the following RRC parameters:

[0282] a common CS-RNTI configuration for scrambling the common DCI;

[0283] a common search space configuration (CSS) corresponding to the common DCI;

[0284] Common DCI size;

[0285] a list of candidate common DCI sizes; and

[0286] Related information on the correspondence between the information blocks in the public DCI and each terminal side device.

[0287] EE 7. The electronic device according to EE 1, wherein the processing circuit is further configured to:

[0288] The common CS-RNTI configuration is scrambled to the common DCI to indicate that the common DCI is used for verification of SPS and / or CG of multiple terminal devices.

[0289] EE 8. The electronic device according to EE 1, wherein the processing circuit is further configured to:

[0290] A public search space configuration corresponding to the public DCI is sent so that the terminal side device can process the public DCI in the public search space.

[0291] EE 9. The electronic device according to EE 1, wherein the processing circuit is further configured to send at least one of the following:

[0292] Size information, indicating the size of the public DCI; and

[0293] The location-related information can be used to derive the location of the information block corresponding to each terminal side device in the public DCI.

[0294] EE 10. The electronic device according to EE 1, wherein the processing circuit is further configured to:

[0295] Activate a specific DCI size from a list of candidate common DCI sizes via a MAC CE, and

[0296] Send the activated DCI size and the information related to the position of the information block corresponding to each terminal side device in the public DCI.

[0297] EE 11. An electronic device on a terminal side in a wireless communication system, comprising:

[0298] The processing circuit is configured to:

[0299] Receive common downlink control information (DCI) for multiple terminal side devices in the wireless communication system from the control side in the wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in the multiple terminal side devices.

[0300] EE 12. The electronic device according to EE 11, wherein the processing circuit is further configured to perform blind detection on the received common downlink control information (DCI) to determine the relevant information of the SPS and / or CG to be released contained in the information block corresponding to the terminal side device in the common DCI, wherein the relevant information includes at least index information indicating the SPS and / or CG to be released, and

[0301] The release of the indicated SPS and / or CG is performed based on at least the index information.

[0302] EE 13. The electronic device according to EE 11, wherein the processing circuit is further configured to receive a radio resource control (RRC) parameter from a control-side device, wherein the RRC parameter specifies at least one combination, each combination including one or more SPS indexes and one or more CG indexes.

[0303] The DCI indicates one of the at least one combinations to release the SPS identified by one or more SPS indices in the combination and / or the CG identified by one or more CG indices in the combination.

[0304] EE 14. The electronic device according to EE 11, wherein the processing circuit is further configured to receive, through RRC signaling, information about the format of the DCI and the configuration of a physical downlink control channel (PDCCH) including the DCI in the search space of the UE.

[0305] EE 15. The electronic device according to EE 11, wherein the processing circuit is further configured to provide feedback information after verification, wherein the feedback information includes HARQ ACK or HARQ NACK.

[0306] EE 16. A method for a control side in a wireless communication system, comprising:

[0307] Common downlink control information (DCI) is sent for terminal side devices in a wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in a plurality of terminal side devices.

[0308] EE 17. The method according to EE 16, further comprising setting at least one of the following RRC parameters:

[0309] a common CS-RNTI configuration for scrambling the common DCI;

[0310] a common search space configuration (CSS) corresponding to the common DCI;

[0311] Common DCI size;

[0312] a list of candidate common DCI sizes; and

[0313] Related information on the correspondence between the information blocks in the public DCI and each terminal side device.

[0314] EE 18. The method according to EE 16, further comprising:

[0315] The common CS-RNTI configuration is scrambled to the common DCI to indicate that the common DCI is used for verification of SPS and / or CG of multiple terminal devices.

[0316] EE 19. The method according to EE 16, further comprising:

[0317] A public search space configuration corresponding to the public DCI is sent so that the terminal side device can process the public DCI in the public search space.

[0318] EE 20. The method according to EE 16, further comprising sending at least one of the following:

[0319] Size information, indicating the size of the public DCI; and

[0320] The location-related information can be used to derive the location of the information block corresponding to each terminal side device in the public DCI.

[0321] EE 21. The method according to EE 16, further comprising:

[0322] Activate a specific DCI size from a list of candidate common DCI sizes via a MAC CE, and

[0323] Send the activated DCI size and the information related to the position of the information block corresponding to each terminal side device in the public DCI.

[0324] EE 22. A method used at a terminal side in a wireless communication system, comprising:

[0325] Receive common downlink control information (DCI) for multiple terminal side devices in the wireless communication system from the control side in the wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in the multiple terminal side devices.

[0326] EE 23. The method according to EE 22, further comprising:

[0327] Performing a blind check on the received common downlink control information (DCI) to determine the relevant information of the SPS and / or CG to be released contained in the information block corresponding to the terminal side device in the common DCI, wherein the relevant information includes at least index information indicating the SPS and / or CG to be released, and

[0328] The release of the indicated SPS and / or CG is performed based on at least the index information.

[0329] EE 24. The method according to EE 22 further includes: receiving a radio resource control (RRC) parameter from a control-side device, wherein the RRC parameter specifies at least one combination, each combination including one or more SPS indexes and one or more CG indexes,

[0330] The DCI indicates one of the at least one combinations to release the SPS identified by one or more SPS indices in the combination and / or the CG identified by one or more CG indices in the combination.

[0331] EE 25. The method as described in EE 22 further includes: receiving, through RRC signaling, information about the format of the DCI and the configuration of a physical downlink control channel (PDCCH) including the DCI in the search space of the UE.

[0332] EE 26. The method as described in EE 22 further includes: providing feedback information after verification, wherein the feedback information includes HARQ ACK or HARQ NACK.

[0333] EE 27. A non-transitory computer-readable storage medium storing executable instructions, wherein when the executable instructions are executed by a processor, the processor is enabled to implement the method according to any one of EEs 16 to 26.

[0334] EE 28. A wireless communication device comprising:

[0335] processor; and

[0336] A storage device storing executable instructions, wherein the executable instructions, when executed by a processor, enable the processor to implement the method according to any one of EEs 16 to 26.

[0337] EE 29. A computer program product comprising computer instructions, which are capable of implementing the method according to any one of EEs 16 to 26 when executed by a processor.

[0338] EE 30. A computer program comprising a program code, wherein the program code is capable of implementing the method according to any one of EEs 16 to 26 when executed by a processor.

[0339] Although the present disclosure and its advantages have been described in detail, it should be understood that various changes, substitutions and transformations can be made without departing from the spirit and scope of the present disclosure as defined by the appended claims. Moreover, the terms "comprises," "comprising," or any other variations thereof in the embodiments of the present disclosure are intended to cover non-exclusive inclusions, such that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article, or device. In the absence of further restrictions, an element defined by the statement "comprising a ..." does not exclude the presence of additional identical elements in the process, method, article, or device comprising the element.

[0340] Although some specific embodiments of the present disclosure have been described in detail, it should be understood by those skilled in the art that the above embodiments are merely illustrative and do not limit the scope of the present disclosure. It should be understood by those skilled in the art that the above embodiments may be combined, modified, or replaced without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.

Claims

1. An electronic device on the control side of a wireless communication system, comprising: The processing circuit is configured to: Common downlink control information (DCI) is sent for terminal side devices in a wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in multiple terminal side devices.

2. The electronic device according to claim 1, wherein: The common downlink control information (DCI) includes an information block for each terminal side device respectively to indicate at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) of the terminal side device.

3. The electronic device according to claim 1, wherein: For each terminal side device, the information block includes index information indicating at least one of one or more SPSs to be released and one or more CGs to be released.

4. The electronic device according to claim 3, wherein: The index information of the SPS and / or CG includes a HARQ ID associated with a single SPS or CG, or an index associated with a group of SPSs or a group of CGs or a group containing both SPSs and CGs.

5. The electronic device according to claim 1, wherein: For each terminal side device, the information block also includes at least one of the following information: Type information indicating whether to perform release of semi-persistent scheduling (SPS) or release of configuration grant (CG); Operation information, which indicates whether the operation involves a release, Stream information, which indicates to which stream the SPS and / or CG indicated by the index information in the information block belongs; and Effective time information, which indicates how long it takes for the terminal side device to execute the release indicated by the public DCI after receiving the public DCI.

6. The electronic device according to claim 1, wherein: The processing circuit is further configured to set at least one of the following RRC parameters: a common CS-RNTI configuration for scrambling the common DCI; a common search space configuration (CSS) corresponding to the common DCI; Common DCI size; A list of candidate common DCI sizes; as well as Relevant information on the correspondence between the information blocks in the public DCI and each terminal side device.

7. The electronic device according to claim 1, wherein: The processing circuit is further configured to: The common CS-RNTI configuration is scrambled to the common DCI to indicate that the common DCI is used for verification of SPS and / or CG of multiple terminal devices.

8. The electronic device according to claim 1, wherein: The processing circuit is further configured to: A common search space configuration corresponding to the common DCI is sent so that the terminal side device can process the common DCI in the common search space.

9. The electronic device according to claim 1, wherein: The processing circuit is further configured to send at least one of: Size information, indicating the size of the common DCI; and The location-related information can be used to derive the location of the information block corresponding to each terminal side device in the public DCI.

10. The electronic device according to claim 1, wherein: The processing circuit is further configured to: activating a specific DCI size from a list of candidate common DCI sizes via the MAC CE, and Send the activated DCI size and the information related to the position of the information block corresponding to each terminal side device in the public DCI.

11. An electronic device on a terminal side in a wireless communication system, comprising: The processing circuit is configured to: Common downlink control information (DCI) for multiple terminal side devices in the wireless communication system is received from the control side in the wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each of the multiple terminal side devices.

12. The electronic device according to claim 11, wherein: The processing circuit is further configured to perform a blind check on the received common downlink control information (DCI) to determine the relevant information of the SPS and / or CG to be released contained in the information block corresponding to the terminal side device in the common DCI, wherein the relevant information at least includes index information indicating the SPS and / or CG to be released, and The release of the indicated SPS and / or CG is performed based on at least the index information.

13. The electronic device according to claim 11, wherein: The processing circuit is further configured to receive a radio resource control (RRC) parameter from a control side, the RRC parameter specifying at least one combination, each combination comprising one or more SPS indexes and one or more CG indexes, The DCI indicates one of the at least one combinations to release the SPS identified by one or more SPS indices in the combination and / or the CG identified by one or more CG indices in the combination.

14. The electronic device according to claim 11, wherein: The processing circuit is further configured to receive information about the format of the DCI and the configuration of a physical downlink control channel (PDCCH) including the DCI in a search space of the UE through RRC signaling.

15. The electronic device according to claim 11, wherein: The processing circuit is further configured to provide feedback information after verification, wherein the feedback information comprises HARQ ACK or HARQ NACK.

16. A method for a control side in a wireless communication system, comprising: Common downlink control information (DCI) is sent for terminal side devices in a wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each terminal side device in multiple terminal side devices.

17. The method of claim 16, further comprising setting at least one of the following RRC parameters: a common CS-RNTI configuration for scrambling the common DCI; a common search space configuration (CSS) corresponding to the common DCI; Common DCI size; A list of candidate common DCI sizes; as well as Relevant information on the correspondence between the information blocks in the public DCI and each terminal side device.

18. The method of claim 16, further comprising: The common CS-RNTI configuration is scrambled to the common DCI to indicate that the common DCI is used for verification of SPS and / or CG of multiple terminal devices.

19. The method of claim 16, further comprising: A common search space configuration corresponding to the common DCI is sent so that the terminal side device can process the common DCI in the common search space.

20. The method of claim 16, further comprising sending at least one of: Size information, indicating the size of the common DCI; and The location-related information can be used to derive the location of the information block corresponding to each terminal side device in the public DCI.

21. The method of claim 16, further comprising: activating a specific DCI size from a list of candidate common DCI sizes via the MAC CE, and Send the activated DCI size and the information related to the position of the information block corresponding to each terminal side device in the public DCI.

22. A method for a terminal side in a wireless communication system, comprising: Common downlink control information (DCI) for multiple terminal side devices in the wireless communication system is received from the control side in the wireless communication system, which indicates at least one of the release of one or more semi-persistent scheduling (SPS) and the release of one or more configuration grants (CG) for each of the multiple terminal side devices.

23. The method of claim 22, further comprising: Performing a blind check on the received common downlink control information (DCI) to determine the relevant information of the SPS and / or CG to be released contained in the information block corresponding to the terminal side device in the common DCI, wherein the relevant information at least includes index information indicating the SPS and / or CG to be released, and The release of the indicated SPS and / or CG is performed based on at least the index information.

24. The method of claim 22, further comprising: receiving a radio resource control (RRC) parameter from a control side in a wireless communication system, the RRC parameter specifying at least one combination, each combination comprising one or more SPS indexes and one or more CG indexes, The DCI indicates one of the at least one combinations to release the SPS identified by one or more SPS indices in the combination and / or the CG identified by one or more CG indices in the combination.

25. The method of claim 22, further comprising: The configuration of the format of the DCI and the physical downlink control channel (PDCCH) including the DCI in the search space of the UE is received through RRC signaling.

26. The method of claim 22, further comprising: After verification, feedback information is provided, wherein the feedback information includes HARQ ACK or HARQ NACK.

27. A non-transitory computer-readable storage medium storing executable instructions, which when executed by a processor enable the processor to implement the method of any one of claims 16 to 26.

28. A wireless communication device, comprising: processor; as well as A storage device storing executable instructions, wherein the executable instructions, when executed by a processor, enable the processor to implement the method according to any one of claims 16 to 26.

29. A computer program product comprising computer instructions, which when executed by a processor can implement the method according to any one of claims 16 to 26.

30. A computer program comprising program code, which is capable of implementing the method according to any one of claims 16 to 26 when executed by a processor.

Images