System and method for span-based monitoring of physical downlink control channel (PDCCH)

Abstract

Disclosed are a system and method for span-based monitoring of a physical downlink control channel (PDCCH), the method comprising transmitting, by a user equipment (UE), first information indicating that the UE supports a first set of capabilities and a second set of capabilities different from the first set of capabilities, determining, by the UE, whether the monitored span pattern satisfies a first span pattern associated with the first set of capabilities, and performing, by the UE, span-based monitoring of the PDCCH based on a first value associated with the first set of capabilities or based on a second value associated with the second set of capabilities.

Description

[0001] This application claims priority to and the benefit of U.S. Provisional Application No. 63 / 545,312, filed on October 23, 2023, entitled “UE Capability Signaling Design for a Single Function with Different Application Restrictions in Multiple Different Versions of Cellular Communication Specifications,” U.S. Provisional Application No. 63 / 543,658, filed on October 11, 2023, entitled “UE Capability Signaling Design for a Single Function with Different Application Restrictions in Multiple Different Versions of Cellular Communication Specifications,” and U.S. Application No. 18 / 905,800, filed on October 03, 2024, the entire disclosures of all of which are incorporated herein by reference. Technical Field

[0002] Aspects of embodiments of the present disclosure relate to wireless communications.For example, aspects of embodiments of the present disclosure relate to improved systems and methods for span-based monitoring of a physical downlink control channel (PDCCH). Background Art

[0003] Modern communication equipment (e.g., mobile phones, vehicles, laptops, satellites, etc.), also referred to as user equipment (UE), can communicate with a network node (e.g., a base station, also referred to as a gNB) to receive data from a network associated with the network node and to send data to a network associated with the network node. The UE can perform capability signaling by sending (e.g., by reporting) information to the network node to indicate the features that the UE can support. The network node can configure resources for the UE based on the reported capabilities of the UE. For example, the network node can send a PDCCH monitoring opportunity configuration to the UE based on the reported capabilities. The PDCCH monitoring opportunity configuration can be a resource configured by the network node for the UE to use when monitoring control information from the network node. The UE can perform span-based monitoring of the PDCCH based on the PDCCH monitoring opportunity configuration. The UE can perform monitoring of scheduling information from the network node based on the PDCCH monitoring opportunity configuration. The PDCCH monitoring opportunity configuration can be associated with various span modes for the UE to use when performing span-based monitoring of the PDCCH. In some cases, some reported capabilities may lead to ambiguity (e.g., may lead to uncertainty) in how a network node may configure monitoring resources for a UE and / or how a UE may perform span-based monitoring of a PDCCH. For example, two or more reported capabilities from a UE may include conflicting information, which may prevent the communication system from operating normally.

[0004] The above information disclosed in this Background section is for enhancement of understanding of the background of the present disclosure and therefore it may contain information that does not constitute the prior art. Summary of the invention

[0005] Release 16 of the 3rd Generation Partnership Project (3GPP) specification (hereinafter referred to as "Release 16") provides PDCCH monitoring and includes feature group (FG) 11-2. Release 16 also provides FG 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f and 11-2g as supplementary capabilities for supporting the operation of FG 11-2. Release 17 of the 3GPP specification (hereinafter referred to as "Release 17") provides a repeated function, the repeated function is based on span-based monitoring, and includes FG 23-2-1e as another supplementary capability for supporting the operation of FG 11-2.

[0006] FG 11-2 provides various span modes for performing span-based monitoring of the PDCCH. As discussed in further detail below, different span modes may provide different balances between the scheduling delay of the system and the monitoring burden on the UE. For example, Release 16 and Release 17 capabilities may be associated with span modes (7,3), (4,3), and (2,2). Based on the (2,2) span mode, the UE may experience a monitoring burden that is difficult (e.g., too difficult) for some UEs.

[0007] Release 18 of the 3GPP specification (hereinafter referred to as "Release 18") provides a modified (e.g., relaxed) version of the (2,2) span mode and includes FG 55-6. Release 18 also provides FG55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, and 55-6h as supplementary capabilities for supporting the operation of FG55-6. Each of FG 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, and 55-6h is created to mirror each of FG 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e, respectively. For example, FG 55-6a mirrors FG 11-2a, FG55-6g mirrors FG 11-2g, and FG 55-6h mirrors FG 23-2-1e.

[0008] A modified version of the (2,2) span mode (hereinafter referred to as “relaxed (2,2)”) may reduce the monitoring burden on UEs and make it easier for some UEs to perform span-based monitoring of PDCCH similar to but relaxed (2,2) span mode (hereinafter referred to as “original (2,2)”). The mirroring of FG 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g and 55-6h with their counterparts in FG 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g and 23-2-1e enables the UE to send information indicating support for Release 18 capabilities (e.g., FG 55-6 and its supplementary capabilities) instead of also indicating support for Release 16 and Release 17 capabilities (e.g., FG 11-2 and its supplementary capabilities).

[0009] However, when a UE that is not capable of supporting the original (2,2) supports other span modes (such as (4,3) and (7,3) from FG 11-2) while also indicating support for one or more of the supplementary capabilities of FG 11-2 (e.g., one or more of 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e) and support for the relaxed (2,2) in FG 55-6, ambiguity (e.g., uncertainty) may occur. The ambiguity may prevent the system from operating normally. For example, ambiguous capability signaling may cause the system to drop calls.

[0010] To overcome these issues, this document describes systems and methods for communicating information for span-based monitoring of PDCCH when a UE is capable of supporting both: (i) features from a first capability set associated with Release 18, including one or more of FGs 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, and 55-6h (also referred to herein as 55-6x), and (ii) features from a second capability set associated with Release 16 and Release 17, including FGs 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e (also referred to herein as 11-2x).

[0011] Some embodiments of the present disclosure involve sending information by a UE (e.g., via capability signaling) to indicate capabilities that, when reported together or otherwise, may cause ambiguity caused by two versions of similar supplemental capabilities from 11-2x (e.g., 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e) and 55-6x (e.g., 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, and 55-6h), which may be indicated (e.g., simultaneously) by a UE supporting the following modes: (i) a mode from 11-2 in addition to the original (2,2) and (ii) a relaxed (2,2) span mode.

[0012] Some embodiments of the present disclosure relate to determining (e.g., detecting) a span pattern configured by a serving cell by a UE capable of performing features associated with Release 18 and capable of performing features associated with Release 16 and / or Release 17, and performing span-based monitoring of a PDCCH based on the determined (e.g., detected) span pattern.

[0013] Some embodiments of the present disclosure relate to using, by a network node, a union of supported span modes associated with Release 16, Release 17, and Release 18 when the UE is capable of monitoring multiple combinations of span modes and the UE is capable of performing features associated with Release 18 and is capable of performing features associated with Release 16 and / or Release 17.

[0014] Some embodiments of the present disclosure relate to determining, by a UE, features and values ​​associated with the features to report and use in performing span-based monitoring of a PDCCH when the UE is capable of performing features associated with Release-16, Release-17, and Release-18.

[0015] The above-described method improves upon previous methods by reducing the risk that the network may not operate correctly based on ambiguous information associated with a UE reporting support for similar capabilities according to Release 16, Release 17 and Release 18 (eg, conflicting capabilities).

[0016] According to some embodiments of the present disclosure, a method for span-based monitoring of PDCCH includes: sending, by a user equipment (UE), first information indicating that the UE supports a first capability set and a second capability set different from the first capability set, determining, by the UE, whether a monitored span pattern satisfies a first span pattern associated with the first capability set, and performing, by the UE, span-based monitoring of a physical downlink control channel (PDCCH) based on a first value associated with the first capability set or based on a second value associated with the second capability set.

[0017] The first information may include a first value, the first span mode may be a relaxed (2,2) span mode, the relaxed (2,2) span mode includes a span of two symbols, a span gap of two symbols, and one or more additional symbols between the spans, the monitored span mode may satisfy the relaxed (2,2) span mode, and the execution may be based on the first value.

[0018] The first information may include a second value, the monitored span pattern may satisfy a second span pattern that is not the relaxed (2,2) span pattern, the second span pattern may be associated with a second capability set, and the performing may be based on the second value.

[0019] The first capability set may include one or more of feature groups 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, or 55-6h, and the second capability set may include one or more of feature groups 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, or 23-2-1e.

[0020] The method may also include receiving, by the UE as part of a carrier aggregation (CA) transmission or a dual connectivity (DC) transmission, multiple PDCCH monitoring timing configurations associated with corresponding cells among multiple cells serving the UE, wherein determining, by the UE, whether a monitored span pattern satisfies a first span pattern includes: determining the number of cells associated with the multiple PDCCH monitoring timing configurations that satisfy the first span pattern, and performing span-based monitoring of the PDCCH based on a first capability set based on the number of cells satisfying a first threshold.

[0021] The first threshold may be more likely to trigger use of the first set of capabilities.

[0022] The first threshold may correspond to a number of cells greater than or equal to one.

[0023] The method may further include performing span-based monitoring of the PDCCH based on a second value based on the number of cells not satisfying the first threshold.

[0024] The first threshold may be more likely to trigger use of the second set of capabilities.

[0025] The first threshold may correspond to a number of cells equal to a total number of cells serving the UE.

[0026] Based on determining that cells in a plurality of cells serving the UE are not aligned, span-based monitoring of a physical downlink control channel (PDCCH) may be performed based on a number of cells associated with the plurality of PDCCH monitoring opportunity configurations satisfying a first span pattern.

[0027] According to other embodiments of the present disclosure, a method for span-based monitoring of PDCCH includes sending first information by a user equipment (UE), the first information indicating that the UE is capable of monitoring multiple span mode combinations, and the UE supports a first capability set and a second capability set, and based on the union of the span modes supported in the first capability set and the span modes supported in the second capability set, the UE performs span-based monitoring of a physical downlink control channel (PDCCH).

[0028] Performing span-based monitoring of the PDCCH based on the transmission of the first information may include determining a per-span blind decoding (BD) or determining a per-span control channel element (CCE) based on a union of span modes supported in the first capability set and span modes supported in the second capability set.

[0029] The first capability set may include one or more of feature groups 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, or 55-6h, and the second capability set may include one or more of feature groups 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, or 23-2-1e.

[0030] According to other embodiments of the present disclosure, a method for span-based monitoring of PDCCH includes: sending, by a user equipment (UE) capable of supporting a first capability set and a second capability set, first information indicating whether the UE is capable of supporting the first capability set and / or the second capability set, and performing, by the UE, span-based monitoring of PDCCH based on the sending of the first information, wherein the first capability set includes features associated with a first span mode, and wherein the second capability set includes features associated with a second span mode.

[0031] The first span mode may be a relaxed (2,2) span mode, and the first information may include only features of a set selected from the first capability set and the second capability set, so that the UE does not send information indicating that the UE can support features from both the first capability set and the second capability set.

[0032] The method may further include receiving, by the UE, information indicating only one set selected from the first capability set and the second capability set as including valid features associated with the network node, wherein the first information includes only features of the one set selected from the first capability set and the second capability set.

[0033] The first information may indicate that the UE is capable of supporting both the first capability set and the second capability set, and each of the first values ​​provided in the first information for the first capability set may be equal to a corresponding value in the second values ​​provided in the first information for the second capability set.

[0034] The first information may indicate a selected value selected from between two values ​​based on the selected value being a smaller value of the two values, the two values ​​including a first value of the first characteristic of the first capability set and a second value of the corresponding first characteristic of the second capability set.

[0035] The first information may indicate a selected value selected from between two values ​​based on the selected value being a larger value of the two values, the two values ​​including a first value of the first characteristic of the first capability set and a second value of the corresponding first characteristic of the second capability set. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The above and other aspects of the present disclosure will be more clearly understood from the following detailed description of illustrative, non-limiting embodiments with reference to the accompanying drawings.

[0037] Figure 1A is a block diagram illustrating a system for transmitting information for performing span-based monitoring of a PDCCH according to some embodiments of the present disclosure.

[0038] Figure 1B is a block diagram depicting the relationship between feature groups from Release 16, Release 17, and Release 18 according to some embodiments of the present disclosure.

[0039] Figure 2 It is a depiction Figure 1A Block diagram of transmission of component carriers in a system.

[0040] FIG. 3A to FIG. 11B is a 3GPP table entry from the UE feature list for capability sets associated with Release-16 and Release-17.

[0041] Figure 3A is a diagram depicting a table entry from the Radio Access Network 1 (RAN1) UE Features List with index number 11-2. Figure 3B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2. Figure 4A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2a. Figure 4B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2a. Figure 5A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2b. Figure 5B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2b. Fig. 6A is a diagram depicting a table entry from the RAN1 UE features list of index number 11-2c. Figure 6B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2c. Fig. 7A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2d. Figure 7B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2d. Fig. 8A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2e. Figure 8B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2e. Figure 8C is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2e. Fig. 9A is a diagram depicting a table entry from the RAN1 UE feature list with index number 11-2f. Fig. 9B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2f. Fig. 10A is a diagram depicting a table entry from the RAN1 UE feature list with index number 11-2g. Fig. 10B is a diagram depicting additional table entries from the RAN1 UE Features List with index number 11-2g. Fig.11A is a diagram depicting a table entry from the RAN1 UE Features List with index number 23-2-1e. Fig. 11B is a diagram depicting additional table entries from the RAN1 UE Features List with index number 23-2-1e.

[0042] It should be understood that for convenience, selected table entries from the RAN1 UE feature list are provided herein. A person skilled in the art will understand the contents of the table and how to find the information contained therein.

[0043] Figures 12 to 20 is the 3GPP table entry from the UE feature list for the capability set associated with Release-18. Figures 12 to 20 Column 9 includes proposed comments (in bold) according to some embodiments of the present disclosure.

[0044] Fig.12 is a diagram depicting a table entry in the RAN1 UE feature list from index number 55-6 including proposed annotations according to some embodiments of the present disclosure. Fig.13 is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55 - 6a including proposed annotations according to some embodiments of the present disclosure. Fig.14is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55-6b including proposed annotations according to some embodiments of the present disclosure. Fig.15 is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55 - 6c including proposed annotations according to some embodiments of the present disclosure. Fig.16 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6d including proposed annotations according to some embodiments of the present disclosure. Fig.17 is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55-6e including proposed annotations according to some embodiments of the present disclosure. Fig.18 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6f including proposed annotations according to some embodiments of the present disclosure. Fig.19 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6g including proposed annotations according to some embodiments of the present disclosure. Fig. 20 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6h including proposed annotations according to some embodiments of the present disclosure.

[0045] Fig.21 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a UE indicating support for only one set from a first capability set and a second capability set according to some embodiments of the present disclosure.

[0046] Fig. 22 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a UE receiving an explicit indication of which capability set is valid according to some embodiments of the present disclosure.

[0047] Fig.23 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a UE indicating the same value for a first capability set and a second capability set according to some embodiments of the present disclosure.

[0048] Fig.24 is a flow chart depicting a method for span-based monitoring of a PDCCH based on selecting a selected value from two sets as the smaller of two values, according to some embodiments of the present disclosure.

[0049] Fig.25 is a flow chart depicting a method for span-based monitoring of a PDCCH based on selecting a selected value from two sets as a larger value of two values ​​according to some embodiments of the present disclosure.

[0050] Fig.26 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a span pattern of monitoring from a network node according to some embodiments of the present disclosure.

[0051] Fig. 27 is a flow chart depicting a method for span-based monitoring of a PDCCH when the number of monitored span patterns exceeds a threshold according to some embodiments of the present disclosure.

[0052] Fig.28 is a flow chart depicting a method for span-based monitoring of PDCCH based on determining cell misalignment according to some embodiments of the present disclosure.

[0053] Fig.29 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a union of supported span modes from two capability sets according to some embodiments of the present disclosure.

[0054] Fig.30 is a block diagram of an electronic device in a network environment according to some embodiments of the present disclosure. DETAILED DESCRIPTION

[0055] In the following detailed description, many specific details are set forth in order to provide a thorough understanding of the present disclosure. However, those skilled in the art will appreciate that the disclosed aspects may be implemented without these specific details. In other instances, well-known methods, processes, components, and circuits are not described in detail to avoid obscuring the subject matter disclosed herein.

[0056] References throughout this specification to "one embodiment" or "embodiment" mean that the specific features, structures or characteristics described in conjunction with the embodiment may be included in at least one embodiment disclosed herein. Therefore, the phrases "in one embodiment" or "in an embodiment" or "according to an embodiment" (or other phrases with similar meanings) that appear in various places throughout this specification may not necessarily all refer to the same embodiment. In addition, specific features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the word "exemplary" means "used as an example, instance or illustration". Any embodiment described herein as "exemplary" should not be interpreted as necessarily being preferred or advantageous over other embodiments. In addition, specific features, structures or characteristics may be combined in any suitable manner in one or more embodiments. In addition, depending on the context discussed herein, singular terms may include corresponding plural forms, and plural terms may include corresponding singular forms. Similarly, hyphenated terms (e.g., "two-dimensional", "predetermined", "pixel-specific", etc.) may occasionally be used interchangeably with corresponding non-hyphenated versions (e.g., "two-dimensional", "predetermined", "pixel-specific", etc.), and capitalized terms (e.g., "counter clock", "row select", "pixel output", etc.) may be used interchangeably with corresponding non-capitalized versions (e.g., "counter clock", "row select", "pixel output", etc.). Such occasional interchangeable usage should not be considered inconsistent with each other.

[0057] In addition, depending on the context discussed herein, singular terms may include corresponding plural forms, and plural terms may include corresponding singular forms. It should also be noted that the various drawings (including component drawings) shown and discussed herein are for illustrative purposes only and are not drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. In addition, reference numerals are repeated in the drawings to indicate corresponding and / or similar elements, if deemed appropriate.

[0058] The terms used herein are only used for the purpose of describing some example embodiments and are not intended to limit the claimed subject matter. As used herein, unless the context clearly indicates otherwise, the singular form is intended to also include the plural form. It will be further understood that when used in this specification, the terms "include" and / or "comprise" specify the presence of the features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0059] It will be understood that when an element or layer is referred to as being on, "connected to" or "coupled to" another element or layer, it may be directly on, connected to or coupled to another element or layer, or there may be intermediate elements or layers. In contrast, when an element is referred to as being "directly on," "directly connected to" or "directly coupled to" another element or layer, there are no intermediate elements or layers. The same reference numerals always refer to the same element. As used herein, the terms "or" and "and / or" include any and all combinations of one or more of the associated listed items.

[0060] As used herein, the terms "first", "second", etc. are used as labels for the nouns that follow them, and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.) unless explicitly defined as such. In addition, the same reference numerals may be used across two or more figures to refer to parts, components, blocks, circuits, units, or modules having the same or similar functions. However, this usage is only for simplicity of illustration and ease of discussion; it does not imply that the construction or architectural details of such components or units are the same in all embodiments, or that such commonly referenced parts / modules are the only way to implement some example embodiments disclosed herein.

[0061] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the subject matter belongs. It will be further understood that terms (such as those defined in commonly used dictionaries) should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and will not be interpreted in an idealized or overly formal sense unless explicitly so defined herein.

[0062] As used herein, the term "module" refers to any combination of software, firmware, and / or hardware configured to provide the functionality described herein in conjunction with the module. For example, software may be implemented as a software package, code, and / or instruction set or instructions, and the term "hardware" as used in any embodiment described herein may include, for example, individually or in any combination, assemblies, hardwired circuits, programmable circuits, state machine circuits, and / or firmware storing instructions executed by programmable circuits. Modules may be implemented collectively or individually as circuits that form part of a larger system, such as, but not limited to, an integrated circuit (IC), a system on a chip (SoC), an assembly, etc.

[0063] The electronic or electrical devices and / or any other related devices or components according to the embodiments of the present disclosure described herein may be implemented using any suitable hardware, firmware (e.g., application specific integrated circuits (ASICs)), software, or a combination of software, firmware, and hardware. For example, the various components of these devices may be formed on an integrated circuit (IC) chip or on separate IC chips. In addition, the various components of these devices may be implemented on a flexible printed circuit film, a tape carrier package (TCP), a printed circuit board (PCB), or formed on a substrate. In addition, the various components of these devices may be processes or threads running on one or more processors in one or more computing devices, executing computer program instructions and interacting with other system components to perform the various functions described herein. The computer program instructions are stored in a memory, which may be implemented in a computing device using a standard memory device (such as, for example, a random access memory (RAM)). The computer program instructions may also be stored in other non-transitory computer-readable media, such as, for example, a CD-ROM, a flash drive, etc. In addition, it should be appreciated by those skilled in the art that, without departing from the spirit and scope of the exemplary embodiments of the present disclosure, the functions of various computing devices may be combined or integrated into a single computing device, or the functions of a particular computing device may be distributed on one or more other computing devices.

[0064] Figure 1A is a block diagram illustrating a system for transmitting information for performing span-based monitoring of a PDCCH according to some embodiments of the present disclosure.

[0065] Figure 1B is a block diagram depicting the relationship between feature groups from Release 16, Release 17, and Release 18 according to some embodiments of the present disclosure.

[0066] Figure 2 It is a depiction Figure 1A Block diagram of transmission of component carriers in a system.

[0067] FIG. 3A to FIG. 11B is a 3GPP table entry from the UE feature list for capability sets associated with Release-16 and Release-17.

[0068] Figure 3A is a diagram depicting a table entry from the Radio Access Network 1 (RAN1) UE Features List with index number 11-2. Figure 3B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2. Figure 4A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2a. Figure 4B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2a. Figure 5A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2b. Figure 5B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2b. Fig. 6A is a diagram depicting a table entry from the RAN1 UE features list of index number 11-2c. Figure 6B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2c. Fig. 7A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2d. Figure 7B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2d. Fig. 8A is a diagram depicting a table entry from the RAN1 UE features list with index number 11-2e. Figure 8B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2e. Figure 8C is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2e. Fig. 9A is a diagram depicting a table entry from the RAN1 UE feature list with index number 11-2f. Fig. 9B is a diagram depicting an additional table entry from the RAN1 UE Features List with index number 11-2f. Fig. 10A is a diagram depicting a table entry from the RAN1 UE feature list with index number 11-2g. Fig. 10B is a diagram depicting additional table entries from the RAN1 UE Features List with index number 11-2g. Fig.11A is a diagram depicting a table entry from the RAN1 UE Features List with index number 23-2-1e. Fig. 11B is a diagram depicting additional table entries from the RAN1 UE Features List with index number 23-2-1e.

[0069] Figures 12 to 20 is the 3GPP table entry from the UE feature list for the capability set associated with Release-18. Figures 12 to 20 Column 9 includes proposed comments (in bold) according to some embodiments of the present disclosure.

[0070] Fig.12 is a diagram depicting a table entry in the RAN1 UE feature list from index number 55-6 including proposed annotations according to some embodiments of the present disclosure. Fig.13 is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55 - 6a including proposed annotations according to some embodiments of the present disclosure. Fig.14is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55-6b including proposed annotations according to some embodiments of the present disclosure. Fig.15 is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55 - 6c including proposed annotations according to some embodiments of the present disclosure. Fig.16 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6d including proposed annotations according to some embodiments of the present disclosure. Fig.17 is a diagram depicting additional table entries from the RAN1 UE feature list of index number 55-6e including proposed annotations according to some embodiments of the present disclosure. Fig.18 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6f including proposed annotations according to some embodiments of the present disclosure. Fig.19 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6g including proposed annotations according to some embodiments of the present disclosure. Fig. 20 is a diagram depicting additional table entries from the RAN1 UE feature list at index number 55-6h including proposed annotations according to some embodiments of the present disclosure.

[0071] As discussed above, modern communication equipment (e.g., mobile phones, vehicles, laptops, satellites, etc.), also referred to as user equipment (UE), can communicate with a network node (e.g., a base station) to receive data from a network associated with the network node and to send data to a network associated with the network node.

[0072] Reference Figure 1A , system 1 may include a UE 105 and a network node 110 (e.g., a gNodeB, also referred to as a “base station”) in communication with each other. The network node 110 may be associated with a release version 50, and the release version 50 is associated with whether the network node 110 supports capabilities associated with release 16, release 17, and / or release 18. The UE 105 may not be aware of the release version 50 of the network node 110. The UE 105 may include a radio transceiver 115 and means for processing. The means for processing may include means for performing various methods disclosed herein (e.g., Figure 21 to Figure 29 The radio transceiver 115 can communicate with the communication module 3090 (see Fig.30 ) corresponds to. The processing circuit 120 may be connected to the processor 3020 (see Fig.30) corresponds. The processing circuit 120 may receive transmissions from the network node 110 via the radio transceiver 115, and the processing circuit 120 may send signals to the network node 110 via the radio transceiver 115. The transmission from the network node 110 may be provided to the UE 105 via a downlink (DL) transmission 10. The transmission from the UE 105 may be provided to the network node 110 via an uplink (UL) transmission 20.

[0073] Aspects of some embodiments of the present disclosure are associated with capability signaling by a UE for performing span-based monitoring of a PDCCH.

[0074] UE capability signaling refers to a mechanism by which the UE 105 may inform the network node 110 of the ability of the UE 105 to perform certain features. For example, the UE may signal its ability to perform certain features via a given UE capability signaling mechanism. As part of the configuration process, the UE 105 may send capability information to perform capability signaling. For example, the network node 110 may configure resources (e.g., monitoring opportunity configuration) for use by the UE 105 based on the capability information provided by the UE 105. The network node 110 may send a capability request to the UE 105 via a DL transmission 10. The UE 105 may send capability information to the network node 110 via an UL transmission 20. The monitoring opportunity configuration may be provided by the network node 110 via a DL transmission 10.

[0075] UE 105 may report its capabilities using one or more of the following mechanisms in accordance with 3GPP. UE 105 may report its ability to perform certain features in any scenario. For example, the UE may report its capabilities on a per-UE basis, indicating that the UE 105 may perform the reported capabilities in any scenario (e.g., in any given frequency band, etc.). UE 105 may report its ability to perform certain features in a specific frequency band. For example, the UE may report its capabilities on a per-band basis, indicating that the UE 105 may perform the reported capabilities in a specific frequency band. The UE may report its ability to perform certain features in a specific frequency band combination used for carrier aggregation (CA). For example, the UE may report its capabilities on a per-band combination (or per BC) basis, indicating that the UE 105 may perform the reported capabilities in a specific frequency band combination. The UE may report its ability to perform certain features in one or more specific frequency bands in a specific frequency band combination used for CA. For example, a mechanism called feature sets may be used to allow such flexibility in reporting, and the UE may report its capabilities on a per-feature set (or per-FS) basis, indicating that the UE 105 may perform the reported capabilities in one or more specific bands in a specific band combination. The UE may report its capabilities to perform certain features in one or more specific component carriers (CCs) in a specific band combination used for CA. For example, a mechanism called per-CC feature sets may be used to allow such flexibility in reporting, and the UE may report its capabilities on a per-CC per-feature set (or per-FSPC) basis, indicating that the UE 105 may perform the reported capabilities in one or more specific CCs in a specific band combination. A band combination refers to a collection of frequency bands that represent a CA configuration (e.g., as described in 3GPP specification 38.101).

[0076] The flexibility of the UE for declaring support for certain features (e.g., for sending capability information) may be increased from a per-UE basis to a per-band basis, to a per-band combination (or per-BC) basis, to a per-feature set (or per-FS) basis, to a per-CC per-feature set (or per-FSPC) basis. For example, if feature A and feature B are per-FSPC, the UE may have full flexibility to support only one of features A and B in each CC. However, if those features are per-UE, the UE may support only or only not support a given feature. The tradeoff for increased flexibility is greater overhead in signaling. Therefore, when determining how UE support for certain features may be declared (e.g., signaled), the complexity of the given feature in the UE implementation and the associated signaling overhead may be considered.

[0077] In 3GPP, capability signaling may depend on each version of the 3GPP specification. In some cases, capability signaling designed for a certain function in one version may create challenging situations for the UE. In this case, a more precise statement of feature support may be introduced in a later version. Similarly, when considering the simultaneous operation of a mandatory function with another function, a certain function that is a mandatory function supported by the UE may create challenging situations for the UE. In this case, a new capability signaling solution may be introduced in a later version to indicate support for simultaneous operation. Aspects of embodiments of the present disclosure provide solutions for handling the interaction between previous capability signaling (e.g., related to Release 16 and Release 17) and new capability signaling (e.g., related to Release 18) regarding the same or similar functions.

[0078] As described above, in Release 16, Release 17 and Release 18, this happens with span-based monitoring of the PDCCH.

[0079] Release 16 provides UE capabilities related to span-based monitoring of PDCCH and includes FG 11-2 (see Figure 3A and Figure 3B Release 16 also provides FG 11-2a as a supplementary capability to support the operation of FG 11-2 (see Figure 4A and Figure 4B ), 11-2b (see Figure 5A and Figure 5B )、11-2c(See Fig. 6A and Figure 6B ), 11-2d (see Fig. 7A and Figure 7B ), 11-2e (see Fig. 8A , Figure 8B and Figure 8C )、11-2f(See Fig. 9A and Fig. 9B ) and 11-2g (see Fig. 10A and Fig. 10B ).For example, Figure 4A , Figure 5A , Fig. 6A , Fig. 7A , Fig. 8A , Fig. 9A and Fig. 10A Column 4 in each of the 11-2 indicates 11-2 or another supplementary capability (e.g., 11-2b) as a prerequisite feature group. Release 17 provides a repeat function that is based on span-based monitoring and includes FG 23-2-1e as another supplementary capability for supporting the operation of FG 11-2 (see Fig.11A and Fig. 11B ).For example, Fig.11AColumn 5 in indicates 11-2 as a prerequisite feature group.

[0080] FG 11-2 provides various span modes for performing span-based monitoring of PDCCH. For example, Figure 3B Column 7 of indicates the span patterns (7,3), (4,3), and (2,2). Figure 2 As discussed in further detail, different span modes may provide different trade-offs between scheduling delays for the system and monitoring burden on the UE. For example, Release 16 and Release 17 capabilities may be associated with span modes (7,3), (4,3), and (2,2) (e.g., original (2,2)). Based on the original (2,2), the UE may experience a monitoring burden that is difficult (e.g., too difficult) for some UEs.

[0081] In Release 17, the PDCCH repetition functionality was introduced, and the UE capability to support PDCCH repetition was introduced together with the span-based monitoring of Release 16 (see Fig.11A and Fig. 11B ).

[0082] "Span" is defined in 3GPP 38.213 as follows.

[0083] "The UE may indicate the capability to monitor PDCCH according to one or more of the combinations (X,Y) = (2,2), (4,3) and (7,3) of per SCS [subcarrier spacing] configurations for μ = 0 and μ = 1 [where μ refers to the subcarrier spacing and the UE may declare different subcarrier spacings for span modes]. A span is the number of consecutive symbols in a slot that the UE is configured to monitor PDCCH. Each PDCCH monitoring opportunity is within a span. If the UE monitors PDCCH on a cell according to the combination (X,Y), the UE supports PDCCH monitoring opportunities in any symbol of a slot with a minimum time interval of X symbols between the first symbols of two consecutive spans (including spans). A span starts at the first symbol where a PDCCH monitoring opportunity starts and ends at the last symbol where a PDCCH monitoring opportunity ends, where the number of symbols of a span is at most 'Y'."

[0084] As described in 11-2, a set of one or more elements with span modes (2,2), (4,3) and (7,3) may be reported for each subcarrier spacing (SCS) and processing type. However, in Release 18, supporting (2,2) was determined to be too difficult for some UEs, and a relaxed (2,2) was introduced with corresponding UE capabilities (see Fig.12 ).For example, Fig.12Column 4 of indicates that (2,2) span-based PDCCH monitoring is supported according to FG 11-2, with an additional restriction that there is at least one Orthogonal Frequency Division Multiplexing (OFDM) symbol gap between two PDCCH monitoring opportunities.

[0085] That is, version 18 provides a modified (e.g., relaxed (2,2)) version of the original (2,2) and includes FG55-6 (see Fig.12 Release 18 also provides FG 55-6a as a supplementary capability for supporting the operation of FG 55-6 (see Fig.13 ), 55-6b (see Fig.14 ), 55-6c (see Fig.15 ), 55-6d (see Fig.16 ), 55-6e (see Fig.17 ), 55-6f (see Fig.18 )、55-6g(see Fig.19 ) and 55-6h (see Fig. 20 ). Each of FG 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, and 55-6h is created to mirror each of FG 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e, respectively. That is, there is a one-to-one correspondence between each of FG 11-2a to 11-2g, 23-2-1e and each of 55-6a to 55-6h. For example, FG 55-6a mirrors FG 11-2a, FG 55-6g mirrors FG 11-2g, and FG 55-6h mirrors FG 23-2-1e.

[0086] For example, and with reference to Figure 1B , the feature groups FG associated with version 18 (e.g., FG55-6 to 55-6h) can be considered to be in the first capability set S1, and the feature groups FG associated with versions 16 and 17 (e.g., FG 11-2 to 11-2g and FG 23-2-1e) can be considered to be in the second capability set S2. By comparing FIG. 4A to FIG. 20 As can be seen from the correspondence table, FG 55-6a mirrors FG 11-2a, FG 55-6b mirrors FG 11-2b, FG 55-6c mirrors FG 11-2c, FG 55-6d mirrors FG 11-2d, FG55-6e mirrors FG 11-2e, FG 55-6f mirrors FG 11-2f, FG 55-6g mirrors FG 11-2g and FG 55-6h mirrors FG23-2-1e.

[0087] As described above, the relaxed (2,2) may reduce the monitoring burden on UEs and make it easier for some UEs to perform span-based monitoring of PDCCH similar to the original (2,2) span pattern but with the relaxed span.

[0088] Reference Figure 2 , to describe the difference between the original (2,2) and the relaxed (2,2), an example is provided in which the network node 110 configures a plurality of PDCCH monitoring opportunity configurations MOC associated with corresponding cells in a plurality of cells (e.g., a plurality of component carriers CC) serving the UE 105. For example, the span pattern SP1 associated with the component carrier CC1 may include a span pattern (7,3), in which the span gap X is equal to 7 (e.g., 7 symbols) and the span Y (e.g., span length Y) is equal to 3 (e.g., 3 symbols). The span gap X of the component carrier CC1 starts with the first symbol SM1 (e.g., the first OFDM symbol) and ends with the seventh symbol SM7. The span pattern (7,3) may be repeated so that the search space (e.g., monitoring opportunity) corresponds to the span Y. For example, the UE may perform span-based monitoring of the PDCCH based on span mode (7, 3) by monitoring PDCCH information from the network node 110 during span Y and by not monitoring between span Y (e.g., performing other tasks, such as receiving a physical downlink shared channel (PDSCH)). The span mode (7, 3) may result in a relatively larger scheduling delay than the span mode (4, 3) because the span mode (7, 3) causes the network node to wait longer between span Y to send information to the UE 105. For example, the span mode SP2 associated with the component carrier CC2 may include the span mode (4, 3) in which the span gap X is equal to 4 and the span Y is equal to 3. Based on the span mode (4, 3), the network node 110 waits for a shorter duration and the UE 105 monitors for a longer duration.

[0089] The span pattern SP3 associated with component carrier CC3 may include a span pattern (2,2) (e.g., original (2,2)), where the span gap X is equal to 2 and the span Y is equal to 2. The network node 110 does not wait for any duration to send information to the UE 105, and the UE 105 continuously monitors based on the span pattern (2,2). Because the UE 105 continuously monitors based on the original (2,2), the original (2,2) may be too difficult for some UEs. The span pattern SP4 associated with component carrier CC4 may include a relaxed (2,2), where the span gap X is equal to 2 and the span Y is equal to 2, and one or more additional symbols are provided between spans (e.g., between two PDCCH monitoring opportunities) to make it easier for the UE to perform span-based monitoring of the PDCCH similar to the original (2,2).

[0090] Because FG 55-6 and its supplementary capabilities are associated with the relaxed (2,2) and FG 11-2 and its supplementary capabilities are associated with the original (2,2), the mirroring of FG 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g and 55-6h with their counterparts in FG 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g and 23-2-1e enables the UE to send information indicating support for Release 18 capabilities (e.g., FG 55-6 and its supplementary capabilities) instead of also indicating support for Release 16 and Release 17 capabilities (e.g., FG 11-2 and its supplementary capabilities).

[0091] However, when a UE that is not capable of supporting the original (2,2) supports other span modes (such as (4,3) and (7,3) from FG 11-2) while also indicating support for one or more of the supplementary capabilities of FG 11-2 (e.g., one or more of 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e) and support for the relaxed (2,2) in FG 55-6, ambiguity (e.g., uncertainty) may occur. The ambiguity may prevent the system 1 from operating normally. For example, the ambiguity may cause the system 1 to drop calls.

[0092] To overcome these issues, this document describes systems and methods for communicating information for span-based monitoring of PDCCH when a UE is capable of supporting both: (i) features from a first capability set associated with Release 18, including one or more of FGs 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, and 55-6h and (ii) features from a second capability set associated with Release 16 and Release 17, including FGs 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, and 23-2-1e.

[0093] Fig.21 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a UE indicating support for only one set from a first capability set and a second capability set according to some embodiments of the present disclosure.

[0094] If the UE does not support FG 11-2 and its supplementary capabilities (FG 11-2a to 11-2g and 23-2-1e), the introduction of FG55-6a to 55-6h will not cause any problems. Therefore, a solution for eliminating ambiguity is to make the UE comply with the following rule: if the UE indicates support for FG 55-6 and any one of the supplementary capabilities FG 55-6a to 55-6h, it may not indicate support for FG 11-2 and some or all of the supplementary capabilities FG11-2a to 11-2g and 23-2-1e corresponding to the indicated one (or more) of FG55-6a to 55-6h.

[0095] For example and with reference to Fig.21 In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2100 including one or more of the following operations. The UE may send first information indicating whether the UE is capable of supporting the first capability set and / or the second capability set to a network node (operation 2101). The UE may perform span-based monitoring based on the sending of the first information (operation 2102). The first information may include only one set selected from the first capability set and the second capability set, so that the UE does not send information indicating that the UE is capable of supporting features (e.g., mirrored features) from both the first capability set and the second capability set.

[0096] However, since span mode (2,2) (original (2,2)) is the only span mode relaxed in 55-6, the UE may not have a problem supporting span modes (4,3) and (7,3) under FG 11-2. When the UE supports FG 11-2 and all supplementary capabilities FG 11-2a to 11-2g and 23-2-1e, and if the UE also supports FG 55-6 and supplementary capabilities FG 55-6a to 55-6h, each of FG 11-2a to 11-2g and 23-2-1e and each of FG 55-6a to 55-6h creates two values ​​(e.g., two versions) of capabilities that may not match. In this case, because the UE does not know the release version of the network node to which the UE is connected, and the UE does not know whether the network node correctly understands FG 55-6 and supplementary capabilities FG 55-6a to 55-6h, the UE may not know which of the supplementary capabilities FG 11-2a to 11-2g and 23-2-1e or supplementary capabilities 55-6a to 55-6h is valid for the network node to which the UE is connected. Therefore, this ambiguity may be removed based on one of the following methods for improved (e.g., for appropriate) operation.

[0097] Fig. 22is a flow chart depicting a method for span-based monitoring of a PDCCH based on a UE receiving an explicit indication of which capability set is valid according to some embodiments of the present disclosure.

[0098] In some embodiments, explicit signaling may be provided from the network node to the UE to indicate which capability set between FGs 11-2a to 11-2g and 23-2-1e and FGs 55-6a to 55-6h is valid for the network node. In some embodiments, such a message may be provided via Radio Resource Control (RRC).

[0099] For example and with reference to Fig. 22 In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2200 including one or more of the following operations. The UE may send first information indicating whether the UE is capable of supporting the first capability set and / or the second capability set to a network node (operation 2201). The UE may receive information indicating only one set selected from the first capability set and the second capability set as including valid features associated with the network node (operation 2202). The UE may perform span-based monitoring based on the sending of the first information and based on the receiving of the information indicating only one set (operation 2203). The first information may include only features of one set selected from the first capability set and the second capability set.

[0100] Fig.23 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a UE indicating the same value for a first capability set and a second capability set according to some embodiments of the present disclosure.

[0101] In some embodiments, if the UE indicates both 11-2x (e.g., FG 11-2a to 11-2g) and 55-6x (e.g., FG 55-6a to 55-6g) or both FG 23-2-1e and FG 55-6h, the UE may indicate the same value for 11-2x and 55-6x and 23-2-1e and 55-6h. If the UE indicates only one of 11-2x and 55-6x or only one of 23-2-1e and 55-6h, the UE may indicate only 11-2x or 23-2-1e. This method can remove ambiguity without explicit (e.g., without developing detailed) signaling.

[0102] For example and with reference to Fig.23In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2300 including one or more of the following operations. The UE may send first information to a network node indicating that the UE is capable of supporting both the first capability set and the second capability set (operation 2301). The UE may perform span-based monitoring based on the sending of the first information (operation 2302). The first information may include a first value provided for the first capability set, the first value being equal to a corresponding value in a second value provided for the second capability set in the first information.

[0103] Fig.24 is a flow chart depicting a method for span-based monitoring of a PDCCH based on selecting a selected value from two sets as a smaller of two values, according to some embodiments of the present disclosure.

[0104] In some embodiments, in order to provide a solution with improved signaling overhead and less restrictions, the UE may perform span-based monitoring of the PDCCH based on sending first information indicating a smaller value between each of FGs 11-2a to 11-2g and 23-2-1e and each of FGs 55-6a to 55-6h. This method may provide a relatively simple UE implementation.

[0105] For example and with reference to Fig.24 In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2400 including one or more of the following operations. The UE may send first information to a network node indicating that the UE is capable of supporting both the first capability set and the second capability set (operation 2401). The UE may perform span-based monitoring based on sending a value selected between two values ​​in the first information (operation 2402). The two values ​​may include a first value of a first characteristic of the first capability set (e.g., from a first characteristic corresponding to FG 55-6a). Fig.13 3) and a second value of the corresponding first feature of the second capability set (e.g., from the first component in column 4 corresponding to FG 11-2a). Figure 4A The selected value provided in the first information may be the smaller of the two values ​​(eg, the value 3).

[0106] Fig.25 is a flow chart depicting a method for span-based monitoring of a PDCCH based on selecting a selected value from two sets as a larger value of two values ​​according to some embodiments of the present disclosure.

[0107] In some embodiments, in order to provide a solution with improved signaling overhead and less restrictions, the UE may perform span-based monitoring of the PDCCH based on sending first information indicating a larger value between each of FGs 11-2a to 11-2g and 23-2-1e and each of FGs 55-6a to 55-6h. This method may provide relatively flexible system operation.

[0108] For example and with reference to Fig.25 In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2500 including one or more of the following operations. The UE may send first information to a network node indicating whether the UE is capable of supporting both the first capability set and the second capability set (operation 2501). The UE may perform span-based monitoring based on sending a value selected between two values ​​in the first information (operation 2502). The two values ​​may include a first value of a first feature of the first capability set (e.g., from a first feature corresponding to FG 55-6a). Fig.13 3) and a second value of the corresponding first characteristic of the second capability set (e.g., from the first component of column 4 corresponding to FG 11-2a). Figure 4A The selected value provided in the first information may be the larger of the two values ​​(eg, the value 16).

[0109] Fig.26 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a span pattern of monitoring from a network node according to some embodiments of the present disclosure.

[0110] In some embodiments, in order to provide a solution with improved signaling overhead and fewer restrictions, if the UE also indicates support for FG 55-6, the UE may not indicate (for example, the UE may comply with a rule that does not allow the UE to indicate) support for span mode (2,2) in FG11-2. When the PDCCH monitoring timing configuration of the network node satisfies the relaxed (2,2), the UE may consider the values ​​in FG 55-6a to 55-6h to be valid. Otherwise, if the PDCCH monitoring timing configuration of the network node does not satisfy the relaxed (2,2), the UE may consider the values ​​in FG 11-2a to 11-2g and 23-2-1e to be valid.

[0111] For example and with reference to Fig.26In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2600 including one or more of the following operations. The UE may send first information to a network node indicating that the UE is capable of supporting both the first capability set and the second capability set (operation 2601). The UE may determine (e.g., may detect) a monitored span pattern from the network node (operation 2602). As used herein, "monitored span pattern" refers to a span pattern received by the UE for the UE to determine a pattern type associated with the monitored span pattern. For example, the UE may receive a configured span pattern (e.g., a monitored span pattern) from a serving cell. The UE may determine whether the monitored span pattern satisfies (e.g., whether the monitored span pattern is) relaxed (2,2) (operation 2603). For example, the UE may determine that the monitored span pattern does satisfy the relaxed (2, 2) or that the monitored span pattern does not satisfy the relaxed (2, 2) (e.g., satisfies span pattern (4, 3) or (7, 3)). The UE may perform span-based monitoring of the PDCCH based on the monitored span pattern and the corresponding value (operation 2604).

[0112] For example, based on determining whether the monitored span pattern satisfies the relaxed (2,2), the UE may perform span-based monitoring of the PDCCH based on a corresponding value from a first set S1 (e.g., FG 55-6x) or based on a value from a second set S2 (e.g., FG11-2x). For example, the value from the first set S1 may include a corresponding value from FG 55-6a. Fig.13 The values ​​from the second set S2 may include the values ​​from the corresponding FG 11-2a. Figure 4A The value of the first component in column 3 is 16.

[0113] In other words, based on (e.g., in response to) determining that the monitored span pattern satisfies the relaxed (2, 2), the UE may perform span-based monitoring of the PDCCH based on a corresponding value from the first set S1 (e.g., a value from feature group 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, or 55-6h). And based on (e.g., in response to) determining that the monitored span pattern satisfies a span pattern that is not relaxed (2, 2) (e.g., a span pattern that satisfies (4, 3) or (7, 3)), the UE may perform span-based monitoring of the PDCCH based on a corresponding value from the second set S2 (e.g., a value from feature group 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, or 23-2-1e).

[0114] Fig. 27 is a flow chart depicting a method for span-based monitoring of a PDCCH when the number of monitored span patterns exceeds a threshold according to some embodiments of the present disclosure.

[0115] When the UE supports multiple cells in CA or dual connectivity (DC), some cells (e.g., some component carriers CC) may have a PDCCH monitoring timing configuration that satisfies the relaxed (2,2), and other cells may have a PDCCH monitoring timing configuration that satisfies (4,3) or (7,3). In this case, a common method (e.g., a common restriction or condition) may be implemented for all cells serving the UE. For example, if multiple (e.g., a predetermined number) cells have a PDCCH monitoring timing configuration that satisfies the relaxed (2,2), FG 55-6a to 55-6h may be considered valid (e.g., may be used for span-based monitoring of the PDCCH). In some embodiments, the number may be 1, which would correspond to "if any cell" (e.g., if any cell satisfies the relaxed (2,2)). This feature corresponds to the following language adopted for pdcch-MonitoringMixed-r18 in 3GPP specification (e.g., 5G specification) 38.306: "When a UE reports both pdcch-MonitoringMixed-r16 and this capability, if the configured span pattern of any serving cell satisfies pdcch-MonitoringSpan2-2-r18, the value reported in this capability is used." This feature also corresponds to Figures 13 to 20 The following language set out in bold in column 9 of corresponds to: "When the UE reports both FG 11-2a and this [55-6x], if the configured span pattern of any serving cell satisfies FG55-6, the value reported in this FG [55-6x] is used."

[0116] Another example would be "if all cells" (eg, if all cells satisfy the relaxed (2,2)).

[0117] A smaller number will promote the use of values ​​in FGs 55-6a to 55-6h. For example, a smaller number may make it more likely that Release 18 capabilities will be used. A larger number will promote the use of values ​​in FGs 11-2a to 11-2g and 23-2-1e. For example, a larger number may make it more likely that Release 16 and Release 17 capabilities will be used. In some embodiments, a smaller number may be selected based on the view that the implementation of the original (2,2) is challenging. In some embodiments, a larger number may be selected to promote the use of FGs 11-2a to 11-2g and 23-2-1e, which are more widely available features (e.g., functions) in earlier versions of the 3GPP specification.

[0118] For example and with reference to Fig. 27 In some embodiments, a UE capable of supporting a first capability set (e.g., including Release 18 capabilities) and a second capability set (e.g., including Release 16 and Release 17 capabilities) may perform a method 2700 including one or more of the following operations. The UE may send first information to a network node indicating that the UE is capable of supporting both the first capability set and the second capability set (operation 2701). The UE may receive a plurality of PDCCH monitoring opportunity configurations associated with corresponding cells in a plurality of cells serving the UE as part of a CA transmission or a DC transmission (operation 2702). The UE may determine (e.g., may detect) a span pattern of monitoring from a plurality of cells (operation 2703). The UE may determine whether the number of span patterns of monitoring that satisfy a relaxed (2, 2) meets (e.g., exceeds) a threshold (operation 2704). The UE may perform span-based monitoring of the PDCCH based on whether the number of span patterns of monitoring that satisfy a relaxed (2, 2) exceeds a threshold (operation 2705). In some embodiments, the threshold may be a number that is more likely to trigger the use of Release 18 capabilities. For example, the threshold may correspond to a number 1 (e.g., if the monitored span pattern from one cell satisfies the relaxed (2,2), then Release 18 capabilities are used). In some embodiments, the threshold may be a number that is more likely to trigger the use of Release 16 and Release 17 capabilities. For example, the threshold may correspond to all cells (e.g., may correspond to the total number of cells serving the UE, such that if the monitored span pattern from all cells satisfies the relaxed (2,2), then Release 18 capabilities are used).

[0119] Fig.28 is a flow chart depicting a method for span-based monitoring of PDCCH based on determining cell misalignment according to some embodiments of the present disclosure.

[0120] The span pattern of the PDCCH monitoring occasions may be "aligned" as described in component 2 of 55-6a (see Fig.13 4). As described above, in some cases, only some cells may satisfy the relaxed (2,2), but this problem may not occur (e.g., may not appear) when the span patterns of all cells are aligned. For example, when all cells are aligned, all cells may or may not satisfy the relaxed (2,2). In this case, the restrictions (e.g., conditions) described above with respect to method 2700 may be applied only when the span patterns of the cells are not aligned (e.g., when the span patterns are "non-aligned").

[0121] For example and with reference to Fig.28In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2800 including one or more of the following operations. The UE may send first information to a network node indicating that the UE is capable of supporting both the first capability set and the second capability set (operation 2801). The UE may receive a plurality of PDCCH monitoring opportunity configurations associated with corresponding cells in a plurality of cells serving the UE as part of a CA transmission or a DC transmission (operation 2802). The UE may determine whether the plurality of cells serving the UE are aligned or misaligned (e.g., non-aligned) (operation 2803). Based on determining that the cells in the plurality of cells are misaligned, the UE may determine (e.g., may detect) a span pattern of monitoring from the plurality of cells (operation 2804). The UE may determine whether the number of span patterns of monitoring that satisfy the relaxed (2,2) exceeds a threshold (operation 2805). The UE may perform span-based monitoring of the PDCCH based on whether the number of span patterns satisfying the relaxed (2, 2) monitoring exceeds a threshold (operation 2806).

[0122] Except for FG 11-2b, the reporting granularity for each of FGs 11-2a to 11-2g is per BC, while the reporting granularity for each of FGs 55-6a to 55-6g is per FS. Per BC here (e.g., for FGs 55-6a to 55-6g) may be more natural because the components in FGs 11-2a to 11-2g may affect all serving cells together. In the case of per FS granularity for each of FGs 55-6a to 55-6h, there may be ambiguity if the UE signals different values ​​for different frequency bands in the BC. To avoid such ambiguity, in some embodiments, the UE may indicate the same value for all serving cells. For example, the UE may indicate the same value for the same position in all FeatureSetsPerBands in the indicated FeatureSetCombination. In some embodiments, the UE may be allowed to indicate a value in one or some of the FeatureSetsPerBands while ensuring that all reported values ​​(e.g., all reported values) have the same value. For example, the UE may indicate the same value or no indication (e.g., no value) for the same position in all FeatureSetsPerBands in the indicated FeatureSetCombination. The problem described here may occur because the granularity (e.g., reporting granularity) used for each of FGs 55-6a to 55-6h is too fine. Therefore, in some embodiments, the problem can be solved by making the granularity per BC rather than per FS. In other words, because FGs 55-6a to 55-6h are created as counterparts to FGs 11-2a to 11-2g (and 23-2-1e) from earlier versions (e.g., because FGs 55-6a to 55-6h are mirrored), the granularity of these new capabilities (e.g., FGs 55-6a to 55-6h) may be modified to have the same granularity as their earlier version counterparts (e.g., FGs 11-2a to 11-2g and 23-2-1e).

[0123] Fig.29 is a flow chart depicting a method for span-based monitoring of a PDCCH based on a union of supported span modes from two capability sets according to some embodiments of the present disclosure.

[0124] As described above, a set having one or more elements of (2,2), (4,3), and (7,3) may be reported in FG 11-2 for each SCS and processing type. It may be advantageous to define (e.g., more clearly define) this set concept (e.g., set symbol) in the 3GPP specification because the set (e.g., multiple (X,Y) combinations discussed in the referenced portion of 3GPP specification 38.213 below) may be used to determine the maximum number of PDCCH processes as described in 3GPP specification 38.213.

[0125] The relevant part of 3GPP specification 38.213 indicates the following.

[0126] If the UE indicates the capability to monitor PDCCH according to multiple (X,Y) combinations and the configuration of the search space set for PDCCH monitoring on the cell given to the UE results in a separation of every two consecutive PDCCH monitoring spans being equal to or greater than the value of X for one or more of the multiple combinations (X,Y), the UE monitors the PDCCH on the cell according to a combination (X,Y) from one or more of the multiple combinations (X,Y), the combination (X,Y) being defined in Table 10.1-2A and Table 10.1-3A [of 3GPP specification 38.213] and The UE is expected to monitor PDCCH according to the same combination (X,Y) in every slot on the active DL BWP [bandwidth part] of the cell.

[0127] Refers to the maximum number of blind decoding (BD). Refers to the maximum number of non-overlapping control channel elements (CCEs) per span. Each span mode may have Each span mode can have different values ​​for different values ​​of .

[0128] Thus, when the UE indicates FG 11-2 with one or more elements of (2,2), (4,3), and (7,3), and if the UE also supports FG 55-6, the UE may indicate support for relaxed (2,2) in addition to the set reported in FG 11-2. In this case, a new definition of the set of (2,2), (4,3), and (7,3) may be created by taking the union of the set in FG 11-2 and {(2,2)} in FG 55-6 (e.g., relaxed (2,2)). For each FS in which support for both FG 11-2 and FG55-6 is indicated, this union operation may be completed (e.g., may be performed) for each SCS and each processing type.

[0129] For example and with reference to Fig.29 In some embodiments, a UE capable of supporting a first capability set (e.g., including capabilities of Release 18) and a second capability set (e.g., including capabilities of Release 16 and Release 17) may perform a method 2900 including one or more of the following operations. The UE may send first information to a network node indicating that (i) the UE is capable of monitoring multiple span mode combinations and (ii) the UE is capable of supporting both the first capability set and the second capability set (operation 2901). Based on a union of span modes supported in the first capability set and span modes supported in the second capability set, the UE may perform span-based monitoring of a PDCCH (operation 2902). For example, the UE may determine a per-span blind decoding (BD) or may determine a per-span control channel element (CCE) based on a union of span modes supported in the first capability set and span modes supported in the second capability set. This feature corresponds to the following language adopted in 3GPP specification (e.g., 5G specification) 38.306 for pdcch-MonitoringSpan2-2-r18: "When the UE reports both pdcch-Monitoring-r16 and this capability, the union of the span modes supported in pdcch-Monitoring-r16 and this capability establishes multiple combinations (X,Y) for determining the per-span BD / CCE restriction as described in clause 10 of TS 38.213." This feature also corresponds to Fig.12 The language set out in bold in column 9 of corresponds to: "When the UE reports both FG 11-2 and this [55-6], as described in clause 10 of TS 38.213, the union of the span modes supported in FG 11-2 and this [55-6] establishes multiple combinations (X,Y) for determining the BD / CCE limit per span."

[0130] Fig.30 is a block diagram of an electronic device in a network environment according to some embodiments of the present disclosure.

[0131] Reference Fig.30, the electronic device 3001 in the network environment 3000 may communicate with the electronic device 3002 via a first network 3098 (e.g., a short-range wireless communication network), or communicate with the electronic device 3004 or the server 3008 via a second network 3099 (e.g., a long-range wireless communication network). The electronic device 3001 may communicate with the electronic device 3004 via the server 3008. The electronic device 3001 may include a processor 3020, a memory 3030, an input device 3040, a sound output device 3055, a display device 3060, an audio module 3070, a sensor module 3076, an interface 3077, a haptic module 3079, a camera module 3080, a power management module 3088, a battery 3089, a communication module 3090, a subscriber identification module (SIM) card 3096, and / or an antenna module 3097. In one embodiment, at least one of the components (e.g., display device 3060 or camera module 3080) may be omitted from electronic device 3001, or one or more other components may be added to electronic device 3001. Some of the components may be implemented as a single integrated circuit (IC). For example, sensor module 3076 (e.g., fingerprint sensor, iris sensor, or illumination sensor) may be embedded in display device 3060 (e.g., display).

[0132] The processor 3020 may execute software (eg, program 3040 ) to control at least one other component (eg, hardware component or software component) of the electronic device 3001 connected to the processor 3020 , and may perform various data processing or calculations.

[0133] As at least part of the data processing or calculation, the processor 3020 may load commands or data received from another component (e.g., the sensor module 3076 or the communication module 3090) into the volatile memory 3032, may process the commands or data stored in the volatile memory 3032, and may store the resultant data in the non-volatile memory 3034. The processor 3020 may include a main processor 3021 (e.g., a CPU or an application processor (AP)) and an auxiliary processor 3023 (e.g., a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP)) that is operationally independent or combined with the main processor 3021. Additionally or alternatively, the auxiliary processor 3023 may be adapted to consume less power than the main processor 3021, or to perform a specific function. The auxiliary processor 3023 may be implemented to be separate from the main processor 3021, or to be implemented as part of the main processor 3021.

[0134] When the main processor 3021 is in an inactive (e.g., sleep) state, the auxiliary processor 3023 (rather than the main processor 3021) may control at least some of the functions or states related to at least one component (e.g., the display device 3060, the sensor module 3076, or the communication module 3090), or when the main processor 3021 is in an active state (e.g., running an application), the auxiliary processor 3023 may control at least some of the functions or states related to at least one component (e.g., the display device 3060, the sensor module 3076, or the communication module 3090) among the components of the electronic device 3001 together with the main processor 3021. The auxiliary processor 3023 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., a camera module 3080 or a communication module 3090) that is functionally related to the auxiliary processor 3023.

[0135] The memory 3030 may store various data used by at least one component of the electronic device 3001 (e.g., the processor 3020 or the sensor module 3076). The various data may include, for example, software (e.g., program 3040) and input data or output data for commands related thereto. The memory 3030 may include a volatile memory 3032 or a non-volatile memory 3034.

[0136] The program 3040 may be stored as software in the memory 3030 , and the program 3040 may include, for example, an operating system (OS) 3042 , middleware 3044 , or an application 3046 .

[0137] The input device 3050 may receive a command or data to be used by another component (eg, processor 3020) of the electronic device 3001 from outside (eg, a user) of the electronic device 3001. The input device 3050 may include, for example, a microphone, a mouse, or a keyboard.

[0138] The sound output device 3055 can output sound signals to the outside of the electronic device 3001. The sound output device 3055 may include, for example, a speaker or a receiver. The speaker can be used for general purposes such as playing multimedia or recording, and the receiver can be used to receive incoming calls. The receiver can be implemented as a separate speaker or as part of the speaker.

[0139] The display device 3060 may visually provide information to the outside (e.g., user) of the electronic device 3001. The display device 3060 may include, for example, a display, a holographic device, or a projector and may include a control circuit for controlling a corresponding one of the display, the holographic device, and the projector. The display device 3060 may include a touch circuit adapted to detect a touch or may include a sensor circuit (e.g., a pressure sensor) adapted to measure the strength of a force caused by a touch.

[0140] The audio module 3070 can convert sound into an electrical signal, or vice versa. The audio module 3070 can obtain sound via the input device 3050, or can output sound via the sound output device 3055 or an earphone of an external electronic device 3002 directly (e.g., wired) or wirelessly connected to the electronic device 3001.

[0141] The sensor module 3076 may detect an operating state (e.g., power or temperature) of the electronic device 3001 or an environmental state (e.g., a state of a user) outside the electronic device 3001. The sensor module 3076 may then generate an electrical signal or data value corresponding to the detected state. The sensor module 3076 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, and / or an illumination sensor.

[0142] The interface 3077 may support one or more specific protocols to be used to connect the electronic device 3001 directly (e.g., wired) or wirelessly to the external electronic device 3002. The interface 3077 may include, for example, a high-definition multimedia interface (HDMI), a universal serial bus (USB) interface, a secure digital (SD) card interface, or an audio interface.

[0143] The connection end 3078 may include a connector via which the electronic device 3001 may be physically connected to the external electronic device 3002. The connection end 3078 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (eg, a headphone connector).

[0144] The haptic module 3079 may convert the electrical signal into a mechanical stimulus (eg, vibration or motion) or an electrical stimulus that may be recognized by the user via the sense of touch or kinesthetic sense. The haptic module 3079 may include, for example, a motor, a piezoelectric element, or an electrical stimulator.

[0145] The camera module 3080 may capture still images or moving images. The camera module 3080 may include one or more lenses, an image sensor, an image signal processor, or a flash. The power management module 3088 may manage the power supply to the electronic device 3001. The power management module 3088 may be implemented as at least part of a power management integrated circuit (PMIC), for example.

[0146] The battery 3089 may power at least one component of the electronic device 3001. The battery 3089 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

[0147] The communication module 3090 may support the establishment of a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 3001 and an external electronic device (e.g., electronic device 3002, electronic device 3004, or server 3008), and may support communication via the established communication channel. The communication module 3090 may include one or more communication processors capable of operating independently from the processor 3020 (e.g., AP), and may support direct (e.g., wired) communication or wireless communication. The communication module 3090 may include a wireless communication module 3092 (e.g., a cellular communication module, a short-range wireless communication module, or a global navigation satellite system (GNSS) communication module) or a wired communication module 3094 (e.g., a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding one of these communication modules can communicate with an external electronic device via a first network 3098 (e.g., a short-range communication network such as Bluetooth™, Wireless Fidelity (Wi-Fi) Direct, or Infrared Data Association (IrDA) standard) or via a second network 3099 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network (e.g., a LAN or a wide area network (WAN))). These various types of communication modules can be implemented as a single component (e.g., a single IC), or these various types of communication modules can be implemented as multiple components separated from each other (e.g., multiple ICs). The wireless communication module 3092 can identify and authenticate the electronic device 3001 in a communication network (such as the first network 3098 or the second network 3099) using user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 3096.

[0148] The antenna module 3097 may transmit or receive a signal or power to or from the outside of the electronic device 3001 (e.g., an external electronic device). The antenna module 3097 may include one or more antennas. The communication module 3090 (e.g., the wireless communication module 3092) may select at least one of the one or more antennas suitable for a communication scheme used in a communication network (such as the first network 3098 or the second network 3099). A signal or power may then be transmitted or received between the communication module 3090 and the external electronic device via the selected at least one antenna.

[0149] A command or data may be sent or received between the electronic device 3001 and the external electronic device 3004 via the server 3008 connected to the second network 3099. Each of the electronic device 3002 and the electronic device 3004 may be a device of the same type as the electronic device 3001, or a device of a different type from the electronic device 3001. All or some operations to be executed on the electronic device 3001 may be executed on one or more of the external electronic device 3002, the external electronic device 3004, or the server 3008. For example, if the electronic device 3001 should automatically execute a function or service or should execute a function or service in response to a request from a user or another device, the electronic device 3001 may request the one or more external electronic devices to execute at least part of the function or service instead of executing the function or service, or the electronic device 3001 may request the one or more external electronic devices to execute at least part of the function or service in addition to executing the function or service. The one or more external electronic devices that receive the request may execute the requested at least part of the function or service, or execute another function or another service related to the request, and transmit the result of the execution to the electronic device 3001. The electronic device 3001 may provide the result as at least a partial reply to the request with or without further processing the result. To this end, for example, cloud computing technology, distributed computing technology, or client-server computing technology may be used.

[0150] The subject matter and the embodiments of the operations described in this specification may be implemented in digital electronic circuits, or in computer software, firmware or hardware (including the structures disclosed in this specification and their structural equivalents), or in a combination of one or more of them. The embodiments of the subject matter described in this specification may be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage medium for execution by a data processing device or for controlling the operation of the data processing device. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagation signal, for example, a machine-generated electrical, optical or electromagnetic signal, which is generated to encode information for transmission to a suitable receiver device for execution by a data processing device. The computer storage medium may be a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof, or may be included in a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination thereof. In addition, although a computer storage medium is not a propagation signal, a computer storage medium may be a source or destination of computer program instructions encoded in an artificially generated propagation signal. The computer storage medium may also be, or be included in, one or more separate physical components or media (e.g., multiple CDs, disks, or other storage devices). In addition, the operations described in this specification may be implemented as operations performed by a data processing device on data stored on one or more computer-readable storage devices or received from other sources.

[0151] Although this specification may contain many specific implementation details, the implementation details should not be interpreted as a limitation on the scope of any claimed subject matter, but rather as a description of features specific to a particular embodiment. Certain features described in the context of a separate embodiment in this specification may also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination. In addition, although features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from the claimed combination may be excluded from the combination in some cases, and the claimed combination may involve a sub-combination or a variation of the sub-combination.

[0152] Similarly, although operations may be depicted in the accompanying drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequence, or that all of the illustrated operations be performed, to achieve the desired results. In some cases, multitasking and parallel processing may be advantageous. In addition, the separation of various system components in the above-described embodiments should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.

[0153] Thus, specific embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the actions set forth in the claims can be performed in a different order and still achieve the desired results. Additionally, the processes depicted in the accompanying drawings do not necessarily require the particular order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing may be advantageous.

[0154] As those skilled in the art will recognize, the innovative concepts described herein may be modified and varied over a wide range of applications. Therefore, the scope of the claimed subject matter should not be limited to any specific exemplary teachings discussed above, but rather is defined by the appended claims, with functional equivalents thereof being included therein.

Claims

1. A method for span-based monitoring of a physical downlink control channel (PDCCH), comprising: Sending, by a user equipment UE, first information indicating that the UE supports a first capability set and a second capability set different from the first capability set; determining, by the UE, whether the monitored span pattern satisfies a first span pattern associated with a first capability set; as well as Span-based monitoring of the PDCCH is performed by the UE based on a first value associated with a first capability set or based on a second value associated with a second capability set.

2. The method according to claim 1, wherein: The first information includes a first value; The first span mode is a relaxed (2,2) span mode, the relaxed (2,2) span mode including a span of two symbols, a span gap of two symbols, and one or more additional symbols between the spans; The monitored span pattern satisfies the relaxed (2,2) span pattern; and The performing is based on the first value.

3. The method according to claim 1, wherein: The first information includes a second value; The monitored span pattern satisfies a second span pattern that is not a relaxed (2,2) span pattern, the second span pattern being associated with a second capability set; and The performing is based on a second value.

4. The method according to claim 1, wherein: The first capability set includes one or more of feature groups 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, or 55-6h; and The second capability set includes one or more of feature groups 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, or 23-2-1e.

5. The method according to claim 1, further comprising: receiving, by the UE as part of a carrier aggregation (CA) transmission or a dual connectivity (DC) transmission, a plurality of PDCCH monitoring opportunity configurations associated with corresponding cells in a plurality of cells serving the UE, in: Determining, by the UE, whether the monitored span pattern satisfies a first span pattern comprises: determining whether the number of cells associated with the plurality of PDCCH monitoring opportunity configurations satisfying the first span pattern satisfies a first threshold; and Performing, by the UE, span-based monitoring of the PDCCH based on a first value associated with the first capability set or based on a second value associated with the second capability set includes performing span-based monitoring of the PDCCH based on the first value based on the number of cells satisfying a first threshold.

6. The method according to claim 5, wherein: The first threshold is more likely to trigger use of the first set of capabilities.

7. The method according to claim 6, wherein: The first threshold corresponds to the number of cells being greater than or equal to one.

8. The method according to claim 5, wherein: Performing, by the UE, span-based monitoring of the PDCCH based on a first value associated with the first capability set or based on a second value associated with the second capability set includes: based on the number of cells not satisfying a first threshold, performing span-based monitoring of the PDCCH based on the second value.

9. The method according to claim 8, wherein: The first threshold is more likely to trigger use of the second set of capabilities.

10. The method according to claim 9, wherein: The first threshold corresponds to a number of the cells equal to a total number of cells serving the UE.

11. The method according to claim 5, wherein: Based on determining that cells in the plurality of cells serving the UE are not aligned, span-based monitoring of the PDCCH is performed based on a number of the cells associated with the plurality of PDCCH monitoring opportunity configurations that satisfy a first span pattern.

12. A span-based monitoring method for a physical downlink control channel (PDCCH), comprising: The user equipment UE sends first information, where the first information indicates: The UE is capable of monitoring a plurality of span pattern combinations; and The UE supports a first capability set and a second capability set; as well as Based on a union of the supported span modes in the first capability set and the supported span modes in the second capability set, span-based monitoring of the PDCCH is performed by the UE.

13. The method according to claim 12, wherein: Performing span-based monitoring of PDCCH based on the union of supported span modes in the first capability set and supported span modes in the second capability set includes: determining blind decoding BD per span or determining control channel element CCE per span based on the union of supported span modes in the first capability set and supported span modes in the second capability set.

14. The method of claim 12, wherein: The first capability set includes one or more of feature groups 55-6, 55-6a, 55-6b, 55-6c, 55-6d, 55-6e, 55-6f, 55-6g, or 55-6h; and The second capability set includes one or more of feature groups 11-2, 11-2a, 11-2b, 11-2c, 11-2d, 11-2e, 11-2f, 11-2g, or 23-2-1e.

15. A method for span-based monitoring of a physical downlink control channel (PDCCH), comprising: Sending, by a user equipment UE capable of supporting a first capability set and a second capability set, first information indicating whether the UE is capable of supporting the first capability set and / or the second capability set; as well as performing, by the UE, span-based monitoring of the PDCCH based on sending of the first information, wherein the first capability set includes features associated with a first span mode, and The second capability set includes features associated with a second span mode.

16. The method of claim 15, wherein: The first span pattern is a relaxed (2,2) span pattern; and The first information includes only features of one set selected from the first capability set and the second capability set, so that the UE does not send information indicating that the UE can support features from both the first capability set and the second capability set.

17. The method according to claim 15, further comprising: receiving, by the UE, information indicating that only one of the first capability set and the second capability set is selected as including valid features associated with the network node, The first information only includes features of the one set selected from the first capability set and the second capability set.

18. The method of claim 15, wherein: The first information indicates that the UE is capable of supporting both a first capability set and a second capability set; and Each of the first values ​​provided in the first information for the first capability set is equal to a corresponding value in the second values ​​provided in the first information for the second capability set.

19. The method according to claim 15, wherein: The first information indicates a selected value selected from between two values ​​based on the selected value being a smaller value of the two values, the two values ​​including a first value of a first feature of a first capability set and a second value of a corresponding first feature of a second capability set.

20. The method according to claim 15, wherein: The first information indicates a selected value selected from between two values ​​based on the selected value being a larger value of the two values, the two values ​​including a first value of a first feature of a first capability set and a second value of a corresponding first feature of a second capability set.

Images