System and method for monitoring a physical downlink control channel

By configuring additional processing time gaps and offsets for low-priority channels within PDCCH monitoring spans, the challenge of simultaneous uRLLC and eMBB processing is addressed, ensuring efficient handling of both channel types with minimal latency impact.

DE102020124098B4Active Publication Date: 2026-03-12SAMSUNG ELECTRONICS CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-09-16
Publication Date
2026-03-12

AI Technical Summary

Technical Problem

Existing 5G UE devices face challenges in efficiently processing both high-priority uRLLC and low-priority eMBB channels due to conflicting processing requirements, leading to difficulties in meeting latency schedules for eMBB processing when prioritizing uRLLC.

Method used

The solution involves configuring additional processing time gaps and offsets based on UE capacity parameters for low-priority channels within PDCCH monitoring spans, allowing UEs to process both uRLLC and eMBB channels without significantly impacting their respective latency requirements.

Benefits of technology

This approach enables UEs to process both high-priority uRLLC and low-priority eMBB channels efficiently, maintaining uRLLC latency while adjusting eMBB latency by a small amount, thus optimizing overall channel processing without compromising performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

Method for monitoring a physical downlink control channel (PDCCH) by a base station (BS), wherein the method includes the following steps: Setting an initial time gap from one end of the PDCCH to the beginning of a common physical downlink channel (PDSCH); Setting a second time gap from one end of the PDSCH to the beginning of a physical uplink control channel (PUCH); Configuring a high-priority channel and a low-priority channel within a PDCCH monitoring span; Received from a user device (UE) of at least one parameter indicating a minimum amount of additional time required by the UE to process the low-priority channel; and based on at least one parameter, configuring the UE with at least one offset used to increase the first time gap and / or the second time gap.
Need to check novelty before this filing date? Find Prior Art

Description

AREA

[0001] The present disclosure relates generally to channel monitoring and in particular to the monitoring of a physical downlink control channel (PDCCH) for a span configured for both high priority channels and low priority channels. BACKGROUND

[0002] Release 16 (rel-16) of the 5th Generation (5G) 3rd Generation Partnership Project (3GPP) introduced enhanced PDCCH monitoring events for highly reliable, low-latency communication (uRLLC). Furthermore, the capabilities of the user device's (UE) control channel element (CCE) and blind coding (BD) were defined per span, rather than per time slot. A span is a number of consecutive symbols within a time slot in which the UE is configured to monitor the PDCCH. A span is defined based on configured search spaces (SSs) and monitoring events (MOs) for a given serving cell, as well as on a set (X, Y) reported by a UE. X is the gap between the start of two consecutive spans, and Y is the span length in symbols.A span begins at the first symbol where a PDCCH-MO starts and ends at the last symbol where the PDCCH-MO ends. The same span pattern is repeated in each time niche.

[0003] For the 5G Release 15 (rel-15) capability, BD / CCE limits are defined per time niche depending on the cell's sub-carrier spacing (SCS). For the 5G rel-16 capability, the BD / CCE limits can be defined per span.

[0004] If a UE supports both 5G-rel-15 capability and 5G-rel-16 capability, PDCCH monitoring is performed for both Enhanced Mobile Broadband (eMBB) (low priority channels) and uRLLC (high priority channels).

[0005] For a 5G rel-16 UE supporting enhanced PDCCH monitoring capability, PDCCH monitoring based on a 5G rel-15 capability can be configured for an eMBB and PDCCH monitoring based on a 5G rel-16 capability for the uRLLC with respect to the UE on the same carrier. Specifically, the UE is configured with mixed time-niche and span-based PDCCH monitoring on a serving cell. For the 5G rel-16 PDCCH monitoring capability, the limit on the maximum number of non-overlapping CCEs for a channel estimate per PCDDC monitoring span is identical across all different spans within a time niche.

[0006] The UE performs BD / CCE monitoring per time slot for the eMBB and per span for the uRLLC. The search spaces (SSs) for the uRLLC and the SSs for the eMBB can correspond to different control resource settings (CORESETs). The SSs of the uRLLC and eMBB also have different SS identifiers (IDs) if they share the same CORESET. The uRLLC and the eMBB can also be distinguished based on the format or size of their corresponding downlink control information (DCI). Accordingly, the UE is able to determine whether a given BD / CCE corresponds to the uRLLC or the eMBB before processing the corresponding PDCCH candidate.

[0007] If the UE has two processing pipelines, it can route the BD / CCE to one of them according to service type or priority (e.g., the high-priority uRLLC or the low-priority eMBB). Alternatively, if the UE has only one pipeline, it prioritizes the uRLLC's BD / CCE candidates over the eMBB's BD / CCE candidates. For example, the UE might first process all the uRLLC's BD / CCE candidates within a given timeframe, and only after completing this does it begin processing the eMBB's BD / CCE candidates. However, such prioritization can make it difficult to meet a schedule for eMBB processing.

[0008] Publication US 2018 / 0352601A1 discloses an operating procedure for an end device in a mobile communications system. The operating procedure may include: starting a T310 timer when a physical layer out-of-sync occurs in a PDCCH transmitted by the first base station; determining that a RLF occurs if the PDCCH does not return to a physical layer synchronization state by the time the T310 timer expires; performing a recovery of the PDCP and RLC layers for all radio carriers except one SRB0; suspending all radio carriers except the SRB0; performing an RRC reconnection with a second base station selected by cell selection; and resuming all radio carriers if the RRC reconnection with the second base station is successful. SUMMARY

[0009] According to one embodiment, a method for monitoring a PDCCH by a base station (BS) is provided. A first time gap is set from one end of the PDCCH to the beginning of a physical downlink shared channel (PDSCH). A second time gap is set from one end of the PDSCH to the beginning of a physical uplink control channel (PUCCH). A high-priority channel and a low-priority channel are configured within a PDCCH monitoring span. At least one parameter indicating a minimum amount of additional time required by the UE to process the low-priority channel is received by the UE. Based on this at least one parameter, the UE is configured with at least one offset, which is used to increase at least the first time gap and / or the second time gap.

[0010] According to one embodiment, a method for monitoring a PDCCH by a BS is provided. A first time gap is set from one end of the PDCCH to the beginning of a physical uplink shared channel (PDSCH). A second time gap is set from one end of the PDSCH to the beginning of a physical uplink control channel (PUCCH). A high-priority channel and a low-priority channel are configured within a PDCCH monitoring span. A parameter indicating the minimum amount of additional time required by the UE to process the low-priority channel is received by the UE. Based on this parameter, the UE is configured with at least one offset, which is used to increase the first time gap and / or the second time gap.

[0011] According to one embodiment, a method for monitoring a PDCCH by a BS is provided. A time gap is set from one end of the PDCCH to the beginning of a physical uplink shared channel (PUSCH). A high-priority channel and a low-priority channel are set within a PDCCH monitoring span. A parameter indicating the minimum amount of additional time required by the UE to process the low-priority channel is received by the UE. Based on this parameter, the UE is configured with an offset that is used to increase the first time gap.

[0012] According to one embodiment, a method for monitoring a PDCCH by a UE is provided. At least one parameter, indicating a minimum amount of additional time required by the UE for processing the low-priority channel, is transmitted to a BS when the BS configures a high-priority channel and the low-priority channel within a PDCCH monitoring span. At least one offset, based on this parameter, is received by the BS. A first time gap and / or a second time gap is increased based on this offset. The first time gap is set from one end of the PDCCH to the beginning of a PDSCH, and the second time gap is set from one end of the PDSCH to the beginning of a PUCCH.

[0013] According to one embodiment, a method for monitoring a PDCCH by a UE is provided. A parameter indicating a minimum amount of additional time required by the UE to process the low-priority channel is transmitted to a BS when the BS configures a high-priority channel and the low-priority channel within a PDCCH monitoring span. An offset based on this parameter is received by the BS. A time gap is increased based on this offset. The time gap is set from one end of the PDCCH to the beginning of a PUSCH.

[0014] According to one embodiment, a BS is provided that includes a processor and a non-transitory, computer-readable storage medium that stores instructions. Upon execution, the instructions cause the processor to: set a first time gap from the end of a PDCCH to the beginning of a PDSCH; set a second time gap from the end of the PDSCH to the beginning of a PUCCH; configure a high-priority channel and a low-priority channel within a PDCCH monitoring span; receive at least one parameter from a UE indicating a minimum amount of additional time required by the UE to process the low-priority channel; and, based on this at least one parameter, configure the UE with at least one offset used to increase the first time gap and / or the second time gap.

[0015] According to one embodiment, a BS is provided that includes a processor and a non-transitory, computer-readable storage medium that stores instructions. Upon execution, the instructions cause the processor to: set a time gap from the end of a PDCCH to the beginning of a PUSCH; configure a high-priority channel and a low-priority channel within a PDCCH monitoring span; receive at least one parameter from a UE indicating a minimum amount of additional time required by the UE to process the low-priority channel; and, based on this parameter, configure the UE with an offset used to increase the time gap.

[0016] According to one embodiment, a UE is provided that includes a processor and a non-transitory, computer-readable storage medium that stores instructions. Upon execution, the instructions cause the processor to: transmit at least one parameter, indicating a minimum amount of additional time required by the UE to process the low-priority channel, to a Bs when the Bs configures a high-priority channel and a low-priority channel within a PDCCH monitoring span; receive from the Bs at least one offset based on the at least one parameter; and increase at least one first time gap and / or a second time gap based on the at least one offset. The first time gap is set from one end of a PDCCH to the beginning of a PDSCH, and the second time gap is set from one end of the PDSCH to the beginning of a PUCCH.

[0017] According to one embodiment, a UE is provided that includes a processor and a non-transitory, computer-readable storage medium that stores instructions. Upon execution, the instructions cause the processor to: transmit a parameter, indicating a minimum amount of additional time required by the UE to process the low-priority channel, to a BS when the BS configures a high-priority channel and a low-priority channel within a PDCCH monitoring span; receive an offset from the BS based on the parameter; and increase a time gap based on at least one offset. The time gap is set from one end of a PDCCH to the beginning of a PUSCH. BRIEF DESCRIPTION OF THE DRAWING

[0018] The foregoing and further aspects, features and advantages of certain embodiments of the present disclosure are explained in more detail below with reference to the detailed description in conjunction with the accompanying drawing. The drawing shows: Fig. 1 a diagram representing a span configured with two MOs for the uRLLC and one MO for the eMBB according to one embodiment; Fig. 2 a diagram representing a span configured with two MOs for the uRLLC and one MO for the eMBB according to one embodiment; Fig. 3 a flowchart illustrating a method for monitoring a PDCCH by a BS according to an embodiment; Fig. 4 a flowchart illustrating a method for monitoring a PDCCH by a BS according to a further embodiment; Fig. 5 a flowchart illustrating a method for monitoring a PDCCH by an UE according to an embodiment; Fig. 6 a flowchart illustrating a method for monitoring a PDCCH by an UE according to a further embodiment; and Fig. 7 A block diagram of an electronic device in a network environment according to one embodiment. DETAILED DESCRIPTION

[0019] The embodiments of the present disclosure are explained in more detail below with reference to the accompanying drawing. It should be noted that identical elements are designated by identical reference numerals, even though they are shown in different drawings. Specific details in the following description, such as detailed configurations and components, are provided solely to enhance the overall understanding of the embodiments of the present disclosure. Those skilled in the art should therefore be aware that various changes and modifications to the embodiments described herein can be made without departing from the scope of protection of the present invention. Furthermore, for the sake of simplicity, explanations of well-known functions and constructions are omitted.The terms described below are defined in light of the functions presented in this disclosure and may vary depending on the user, user intent, or user habits. Therefore, any definition of these terms must always be made in relation to the content throughout the specification.

[0020] The present disclosure may include various modifications and embodiments, some of which are explained in detail below with reference to the accompanying drawing. It should be noted, however, that while the present disclosure is not limited to these embodiments, all modifications, equivalents, and alternatives fall within the scope of protection of the present disclosure.

[0021] Even though terms containing an ordinal number, such as first, second, etc., are used to explain different elements, the structural elements themselves are not restricted by these terms. The terms merely serve to distinguish one element from another. Without deviating from the scope of the present invention, for example, a first structural element can be referred to as a second structural element. Likewise, the second structural element can also be referred to as a first structural element. The term "and / or" used herein includes any or all combinations of one or more associated terms.

[0022] The terms used herein serve only to describe different embodiments of the present disclosure and are not intended to limit the present disclosure in any way. Unless otherwise indicated, singular forms in the text also include plural forms. It is noted in the present disclosure that the terms "include" or "have" indicate the presence of a feature, number, step, process, structural element, parts, or a combination thereof, and do not exclude the presence or possibility of adding one or more other features, numbers, processes, structural elements, parts, or combinations thereof.

[0023] Unless otherwise defined, all terms used herein have the same meaning as would be apparent to a person skilled in the art in the field to which this disclosure relates. Terms as defined in a commonly used dictionary are to be interpreted as being identical in meaning to the contact-related meaning in the relevant field of technology and are not to be interpreted as having an ideal or overly formal meaning, unless this is clearly defined in this disclosure.

[0024] The electronic device according to one embodiment can be one of various types of electronic devices. The electronic devices can include, for example, a portable communication device (e.g., a smartphone), a computer, a portable multimedia device, a portable medical device, a camera, a portable appliance, or a household appliance. According to one embodiment of the disclosure, an electronic device is not limited to the devices described above.

[0025] The terms used in this disclosure are not intended to limit the disclosure itself, but rather to encompass various modifications, correspondences, or substitutions for a corresponding embodiment. With respect to the descriptions of the accompanying drawing, identical reference numerals may be used to designate identical or related elements. A singular form of a noun corresponding to an element may include one or more things, unless the relevant context clearly indicates otherwise. The phrases "A or B," "at least one of A and B," "at least one of A or B," "A, B, or C," "at least one of A, B, and C," and "at least one of A, B, or C" used herein may each include all possible combinations of the elements numbered below in a corresponding phrase. The terms "1.," "2.," and "3.The terms “first” and “second” can be used to distinguish one component from another, but should not restrict the components in other aspects (e.g., meaning or order). When another element (e.g., a second element) is referred to as “coupled with,” “coupled to,” or “connected to,” with or without the term “operative” or “communicative,” this means that the element can be wirelessly coupled to the other element (e.g., wired) or directly via a third element.

[0026] The term "module" as used herein can encompass a unit implemented in hardware, software, or firmware and can be used interchangeably with other terms such as "logic," "logic block," "part," and "circuit arrangements." A module can be a single integral component or a minimal unit or part thereof configured to perform one or more functions. According to one embodiment, for example, a module can be implemented in the form of an application-specific integrated circuit (ASIC).

[0027] According to one embodiment, an additional minimum processing time is provided for the eMBB, PDCCH, PDSCH, PUSCH, or other types of eMBB channels when a UE operates in mixed mode on a serving cell in a time-niche and span-based manner and cannot process both uRLLC and eMBB traffic simultaneously. The additional processing time is determined according to UE capacity signaling and RRC configuration signaling.

[0028] Thus, the UE is able to process both eMBB and uRLLC control and data channels without significantly impacting their respective requirements. A uRLLC latency requirement remains unchanged, whereas an eMBB latency requirement is adjusted by a small amount.

[0029] By relaxing the eMBB processing time, the UE processes the eMBB with an increased time gap from PDCCH to PDSCH or PDSCH to PUCCH or PDCCH to PUSCH.

[0030] Initially referring to Fig. Figure 1 shows a span configured with two MOs for the uRLLC and one MO for the eMBB according to one embodiment. Within a span 102 of the PDCCH, the UE performs B / CCE processing for the uRLLC at a first MO, MO1 104, and a third MO, MO3 108. When the processing in MO1 104 and MO3 108 is complete, the UE performs BD / CCE processing for an eMBB at a second MO, MO2 106.

[0031] If MO1 104 and MO3 108 do not exist in span 102 and only the eMBB is scheduled in MO2 106, a scheduling offset gap T0 and an automatic PDSCH-to-hybrid repeat request (HARQ) gap T1 are set based on minimum processing time capacities. T0 is the time gap between the end of the PDCCH in span 102 and the beginning of an eMBB-PDSCH 110. T1 is the time gap between the end of the eMBB-PDSCH 110 and the beginning of an eMBB-HARQ acknowledgment (ACK) 112 (i.e., PUCCH). T0 is determined by the Time Domain Resource Allocation (TDRA) area in an eMBB-DCI, and T1 is determined by the time niche-based PDSCH-to-HARQ-ACK gap field and the PUCCH format indicator (PFI) field in an eMBB-DCI.

[0032] However, with the addition of MO1 104 and MO3 108 to span 102 and the resulting processing of both the eMBB and the uRLLC in span 102, the eMBB processing time is eased by adding an offset. d0≥d0offset,cap to T0 and / or an offset d1≥d1offset,cap enabled to T1.

[0033] The parameter d0offset,cap is a UE capacity parameter that indicates the minimum additional time the UE requires for PDSCH reception on the eMBB-PDSCH 110. The parameter d1offset,cap is a UE capacity parameter that indicates the minimum additional time the UE requires for HARQ-ACK preparation for the eMBB-HARQ-ACK 112. These two parameters are provided to a BS by the UE. The parameter d0offset,cap can be reported for different values ​​from an SCS (planning cell and planned cell), and the parameter d1offset,cap can be reported for different values ​​of an SCS (planned cell and UL cell for a PUCCH transmission).

[0034] The BS determines the offsets d0 and d1 based on the corresponding received parameters and configures the UE via the RRC. Specifically, the offset d0 is added to T0 to increase the time between the PDCCH and the PDSCH, and the offset d1 is added to T1 to increase the time between the PDSCH and the HARQ-ACK (PUCCH). The UE can be configured with the offset d0 for different values ​​of an SCS (scheduling cell and scheduled cell), and can be configured with the offset d1 for different values ​​of an SCS (scheduled cell and UL cell for a PUCCH transmission).

[0035] With reference to Fig. Figure 2 shows a diagram representing a span according to a further embodiment configured with two MOs for a uRLLC and one MO for the eMBB. Similar to the embodiment of Fig. 1. The UE performs the BD / CCE processing for the uRLLC at a first MO, MO1 204 and a third MO, MO3 208 within a span 202 of the PDCCH. After completion of the processing of MO1 204 and MO3 208, the UE performs the BD / CCE processing for the eMBB at a second MO, MO2 206.

[0036] If MO1 204 and MO3 208 do not exist in span 202, and only one eMBB is planned in MO2 206, a scheduling offset gap T2 is set based on a minimum processing time capacity. T2 is the time gap between the end of the PDCCH and the beginning of an eMBB push 214. T2 is determined by the eMBB DCI.

[0037] With the addition of MO1 204 and MO3 208 to span 202 and the resulting processing of both the eMBB and the uRLLC in span 202, the eMBB processing time is eased by adding an offset. d2≥d2offset,cap to T2. The parameter d2offset,cap This is a UE capacity parameter that indicates the minimum additional time the UE requires for PUSCH transmission at the eMBB-PUSCH 214. The parameter is provided to the BS by the UE. The parameter can be reported for different SCS values ​​(scheduling cell and PUSHC cell).

[0038] The BS determines the offset d2 based on the received parameter and configures the UE via the RRC. Specifically, the offset d2 is added to T2 to increase the time between PDCCH and PUSCH. The UE can be configured with the offset d2 for different SCS values ​​(planning cell and PUSHC cell).

[0039] According to one embodiment, the UE also adds the offset d0≥d0offset,cap d0 added to T0, the offset d1≥d1offset,cap to T1 and / or the offset d2≥d2offset,cap Regarding T2, if different service types or priorities (uRLLC with high priority and eMBB with low priority) are configured with corresponding different MOs in a time slot and not in a span, as described above in Fig. 1 and Fig. 2 is described.

[0040] An aperiodic channel state information (CSI) request / response time offset or a probe reference signal (SRS) transmission time offset can be described as a time gap T other must be defined. If different service types or priorities (uRLLC with high priority and eMBB with low priority) have corresponding different MOs configured in a time slot or PDCCH-MO span, the UE can apply an offset. other ≥ other offset, cap to T other add. The time gap T other is displayed in an eMBB-DCI. The parameter dotheroffset,cap `d` is a UE capacity parameter that indicates the minimum additional time the UE requires for eMBB processing. The UE provides this parameter to the BS, and the BS configures the UE with the offset `d`. other via RRC signaling.

[0041] Planning time gaps T i and added offsets d iPlanning time gaps T can be defined in terms of time (seconds) or OFDM symbols (OS). i and added offsets d i can be a function of a numerology or SCS of the serving cell (planned or planning).

[0042] The UE can assume a relaxation of the eMBB processing time (i.e., that one or more of the added offsets are non-zero) if the uRLLC traffic is scheduled in the uRLLC MOs within the span or time slot. Specifically, no eMBB relaxation is assumed if the uRLLC is not scheduled within the span or time slot.

[0043] The UE can assume that the relaxation is not intended for eMBB processing time (i.e., that the added offsets are zeros) if a first minimum number of OFDM symbols between a terminating symbol of the last uRLLC MO (e.g., MO1 104 of Fig. 1 or the MO1 204 from Fig. 2) and a starting symbol of the eMBB-MO (e.g. the MO2 106 from Fig. 1 or the MO2 206 from Fig. 2) is, and if a second minimum number of symbols exists between the ending symbol of the eMBB-MO (e.g., the MO2 106 of Fig. 1 or the MO2 206 from Fig. 2) and a starting symbol of the next uRLLC-MO (e.g., the MO3 108 of Fig. 1 or the MO3 208 from Fig. 2) is present.

[0044] Fig. 3 is a flowchart that illustrates a method for monitoring a PDCCH by a BS according to one embodiment. In particular, the flowchart corresponds to Fig. 3 of the in Fig. 1. Depiction of the embodiment shown.

[0045] At 203, a first time gap is set from one end of the PDCCH to the beginning of a PDSCH. At 304, a second time gap is set from one end of the PDSCH to the beginning of a PUCCH. The first and second time gaps are set based on a configuration of the low-priority channel (excluding the high-priority channel) within a PDCCH monitoring span. The PDCCH monitoring span is intended for either BD or CCE monitoring and is configured as a single time niche or as a set of multiple spans within a single time niche.

[0046] In port 306, a high-priority channel and a low-priority channel are configured within the PDCCH monitoring span. The high-priority channel can be configured as a uRLLC service type, and the low-priority channel can be configured as an eMBB service type.

[0047] At least one parameter is received on port 308, indicating a minimum amount of additional time required by the UE to process the low-priority channel. This parameter may include a first parameter indicating a minimum amount of additional time required by the UE for PDSCH reception, and a second parameter indicating a minimum amount of additional time required by the UE for HARQ-ACK preparation.

[0048] At 310, the UE is configured based on at least one parameter with at least one offset, which serves to increase the first time gap and / or the second time gap. The UE can be configured by the BS via RRC signaling. The at least one offset can include a first offset based on the first parameter to increase the first time gap, and a second offset based on the second parameter to increase the second time gap.

[0049] Fig. 4 is a flowchart illustrating a method for monitoring the PDCCH by a BS according to a further embodiment. In particular, the flowchart corresponds to Fig. 4 of the in Fig. 2 depicted embodiment.

[0050] At 402, a time gap is set from one end of the PDCCH to the beginning of a PUSCH. The time gap is set based on a configuration of the low-priority channel (excluding the high-priority channel) within a PDCCH monitoring span. The PDCCH monitoring span is used for either BD or CCE monitoring and is configured as a single time niche or as a set of multiple spans within a single time niche.

[0051] In the 404 configuration, a high-priority channel and a low-priority channel are configured within a PDCCH monitoring span. The high-priority channel can be embodied as a uRLLC service type, and the low-priority channel can be embodied as an eMBB service type.

[0052] With code 406, a parameter is received from a UE (Unified Unit) indicating a minimum amount of additional time required by the UE to process the low-priority channel. This parameter indicates a minimum amount of additional time required by the UE for push transmission. With code 408, the UE is configured with an offset based on this parameter, which is used to increase the time gap. The UE can be configured by the BS (Building Services) via RRC (Remote Control Circuit) signaling.

[0053] Referring to Fig. Figure 5 presents a flowchart illustrating a method for monitoring a PDCCH by a UE according to one embodiment. In particular, the flowchart corresponds to Fig. 5 of the embodiment, which is in Fig. 1 is shown.

[0054] With a 502 error, at least one parameter is passed to a BS indicating a minimum amount of additional time required by the UE to process a low-priority channel when the BS configures a high-priority channel and the low-priority channel within a PDCCH monitoring span. The high-priority channel can be implemented as a uRLLC service type, and the low-priority channel can be implemented as an eMBB service type. The PDCCH monitoring span is used for either BD or CCE monitoring and is implemented as a single time niche or as a plurality of spans within a single time niche.

[0055] At least one parameter can be a first parameter indicating a minimum amount of additional time required by the UE for PDSCH reception, and a second parameter indicating a minimum amount of additional time required by the UE for HARQ-ACK preparation.

[0056] At 504, at least one offset based on at least one parameter is received from the BS. At 506, a first time gap and / or a second time gap is increased based on this offset. The UE can be configured by the BS via RRC signaling. The first time gap is set from one end of the PDCCH to the beginning of a PDSCH, and the second time gap is set from one end of the PDSCH to the beginning of a PUCCH. The first and second time gaps are initially set based on a configuration of the low-priority channel (excluding the high-priority channel) within the PDCCH monitoring span.

[0057] At least one offset can be a first offset based on the first parameter to increase the first time gap, and a second offset based on the second parameter to increase the second time gap.

[0058] Fig. 6 is a flowchart that illustrates a method for monitoring a PDCCH by a UE according to a further embodiment. In particular, the flowchart corresponds to Fig. 6 of the in Fig. 2 depicted embodiment.

[0059] In parameter 602, a parameter is transmitted to a base station indicating the minimum amount of additional time required by the UE to process a low-priority channel when the BS configures a high-priority channel and the low-priority channel within a PDCCH monitoring span. The high-priority channel can be implemented as a uRLLC service type, and the low-priority channel can be implemented as an eMBB service type. The parameter indicates the minimum amount of additional time required by the UE for PUSCH transmission. The PDCCH monitoring span is used for either BD or CCE monitoring and is implemented as a single time niche or as a set of multiple spans within a single time niche.

[0060] At 604, an offset based on a parameter is received from the BS. At 606, a time gap is increased based on the offset. The UE can be configured by the BS via RRC signaling. The time gap is set from one end of the PDCCH to the beginning of a PUSCH. The time gap is initially set based on a configuration of the low-priority channel (excluding the high-priority channel) within the PDCCH monitoring span.

[0061] Fig. Figure 7 is a block diagram of an electronic device in a network environment according to one embodiment. Referring to Fig.7. An electronic device 701 in a network environment 700 can communicate with an electronic device 702 via a first network 798 (e.g., a short-range wireless communication network), or with an electronic device 704 or a server 708 via a second network 799 (e.g., a long-range wireless communication network). The electronic device 701 can communicate with the electronic device 704 via the server 708. The electronic device 701 can include a processor 720, a memory 730, an input device 750, a second output device 755, a display device 760, an audio module 770, a sensor module 776, an interface 777, a haptic module 779, a camera module 780, a power management module 788, a battery 789, a communication module 790, a subscriber identification module (SIM) 796, or an antenna module 797. In one embodiment, at least one (e.g.,B. the display device 760 or the camera module 780) can be omitted from the components of the electronic device 701, or one or more components of the electronic device 701 can be added. Some of the components can be implemented as a single integrated circuit (IC). The sensor module 776 (e.g. a fingerprint sensor, an iris sensor, or an illuminance sensor) can be embedded in the display device 760 (e.g. a display).

[0062] The processor 720 can, for example, execute software (e.g., a program 740) to control at least one other component (e.g., a hardware or software component) of the electronic device 701 coupled to the processor 720, and can perform various data processing and calculations. As at least part of the data processing or calculations, the processor 720 can load an instruction or data received from another component (e.g., the sensor module 776 or the communication module 790) into a volatile memory 732, process the instruction or data stored in the volatile memory 732, and store the resulting data in a non-volatile memory 734. The processor 720 can include a main processor 721 (e.g., a central processing unit (CPU) or an application processor (AP)) and an auxiliary processor 723 (e.g., a memory module).The auxiliary processor 723 may include a graphics processing unit (GPU), an image signal processor (ISP), a sensor hub processor, or a communication processor (CP), which can operate independently of or in conjunction with the main processor 721. Additionally or alternatively, the auxiliary processor 723 may be configured to consume less power than the main processor 721 or to perform a special function. The auxiliary processor 723 may be implemented separately from or as part of the main processor 721.

[0063] The auxiliary processor 723 can, instead of the main processor 721, while the main processor 721 is in an inactive (e.g., standby) state, control at least some of the functions or states related to at least one component (e.g., the display device 760, the sensor module 776, or the communication module 790) of the components of the electronic device 701, or control them together with the main processor 721 while the main processor 721 is in an active state (e.g., executing an application). The auxiliary processor 723 (e.g., an image signal processor or a communication processor) can be implemented as part of another component (e.g., the camera module 780 or the communication module 790) that is functionally related to the auxiliary processor 723.

[0064] Memory 730 can store various data used by at least one component (e.g., processor 720 or sensor module 776) of electronic device 701. This data can include, for example, software (e.g., program 740) that inputs data or outputs data for a related instruction. Memory 730 can include volatile memory 732 or non-volatile memory 734.

[0065] The program 740 can be stored as software in memory 730 and can include, for example, an operating system (OS) 742, middleware 744, or an application 746.

[0066] The input device 750 can receive a command or data from outside (e.g., a user) the electronic device 701, which is to be used by another component (e.g., the processor 720). The input device 750 can include, for example, a microphone, a mouse, or a keyboard.

[0067] The sound output device 755 can output sound signals outside the electronic device 701. The sound output device 755 can include, for example, a loudspeaker or a receiver. The loudspeaker can be used for general purposes, such as playing back or recording multimedia, and the receiver can be used to receive an incoming call. The receiver can be implemented separately from or as part of the loudspeaker.

[0068] The display device 760 can visually provide information to the external environment (e.g., a user) of the electronic device 701. The display device 760 can, for example, include a display, a hologram device, or a projector, and a control circuit arrangement to control the display, hologram device, and projector. The display device 760 can include a touch circuit arrangement adapted to detect a touch, or a sensor circuit arrangement (e.g., a pressure sensor) adapted to measure the intensity of a force exerted by the touch.

[0069] The audio module 770 can convert a sound into an electrical signal and vice versa. The audio module 770 can detect the sound via the input device 750 or output the sound via the sound output device 755 or headphones directly (e.g., wired) or wirelessly coupled to the electronic device 701 via an external electronic device 702.

[0070] The sensor module 776 can detect an operating state (e.g., power or temperature) of the electronic device 701 or an environmental state (e.g., a user's state) outside the electronic device 701 and then generate an electrical signal or a data value according to the detected state. The sensor module 776 can include, for example, a gesture sensor, a gyroscope, an atmospheric pressure sensor, a magnetometer, an accelerometer, a grip sensor, a proximity sensor, a color sensor, an infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

[0071] The 777 interface can support one or more specified protocols for use by the electronic device 701, which is to be coupled directly (e.g., wired) or wirelessly with the external electronic device 702. The 777 interface can 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.

[0072] A connection port 778 can include a connector through which the electronic device 701 can be physically connected to the external electronic device 702. The connection port 778 can include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

[0073] The haptic module 779 can convert an electrical signal into a mechanical stimulus (e.g., a vibration or movement) or an electrical stimulus that can be perceived by the user through tactile or kinesthetic sensation. The haptic module 779 can, for example, include an electric motor, a piezoelectric element, or an electrical stimulator.

[0074] The 780 camera module can capture still or moving images. The 780 camera module can include one or more lenses, image sensors, image signal processors, or flash units.

[0075] The power management module 788 can manage the power supplied to the electronic device 701. The power management module 788 can be implemented as at least part of, for example, an integrated power management circuit (PMIC).

[0076] The battery 789 can supply power to at least one component of the electronic device 701. The battery 789 can, for example, include a non-rechargeable primary cell, a rechargeable secondary cell, or a fuel cell.

[0077] The Communication Module 790 can support the establishment of a direct (e.g., wired) or wireless communication channel between the Electronic Device 701 and the external electronic device (e.g., the Electronic Device 702, the Electronic Device 704, or the Server 708) and the execution of communication over the established communication channel. The Communication Module 790 can include one or more communication processors that can operate independently of the Processor 720 (e.g., the AP Processor) and supports direct (e.g., wired) or wireless communication. The Communication Module 790 can include a Wireless Communication Module 792 (e.g., a cellular communication module, a short-range wireless communication module, or a global satellite navigation (GNSS) communication module) or a Wired Communication Module 794 (e.g., a cellular communication module, a cellular communication module, or a cellular communication module).B. a local area network (LAN) communication module or a power line communication (PLC) module). A corresponding communication module can communicate with the external electronic device via the first network 798 (e.g., a short-range communication network such as Bluetooth®, Wireless-Fidelity (Wi-Fi) Direct, or an Infrared Data Association (IrDA) standard) or the second network 799 (e.g., a long-range communication network such as a cellular network, the Internet, or a computer network such as a LAN or a wide area network (WAN)). These different types of communication modules can be implemented as a single component (e.g., a single integrated circuit) or as multiple components (e.g., multiple integrated circuits) that are separate from one another.The wireless communication module 792 can identify and authenticate the electronic device 701 in a communication network, such as the first network 798 or the second network 799, using subscriber information (e.g. an International Mobile Subscriber Identity (IMSI)) stored in the subscriber identification module 796.

[0078] The antenna module 797 can transmit or receive a signal or power to or from outside (e.g., the external electrical device) the electronic device 701. The antenna module 797 can include one or more antennas, and at least one of these antennas, suitable for a communication scheme used in the communication network, such as the first network 798 or the second network 799, can be selected by, for example, the communication module 790 (e.g., the wireless communication module 792). The signal or power can then be transmitted or received between the communication module 790 and the external electrical device via the selected at least one antenna.

[0079] At least some of the components described above can be coupled together and communicate signals with each other via an inter-peripheral communication scheme (e.g. a bus, a general-purpose input / output (GPIO), a serial peripheral interface (SPI) or a mobile industrial processor interface (MIPI)).

[0080] Commands or data can be transmitted and received between the electronic device 701 and the external electronic device 704 via the sensor 708, which is coupled to the second network 799. The electronic devices 702 and 704 can each be of the same type as, or of a different type from, the electronic device 701. All or part of the operations to be performed on the electronic device 701 can be performed on one or more of the external electronic devices 702, 704, or 708. For example, if the electronic device 701If a function or service is to be performed automatically or in response to a request from a user or another device, the electronic device 701 may, instead of performing the function or service itself, or in addition to doing so, request one or more electronic devices to perform at least part of the function or service. The one or more electronic devices receiving the request may perform at least part of the requested function or service, or an additional function or service related to the request, and transmit a result of the performance to the electronic device 701. The electronic device 701 may provide the result, with or without further processing of the result, as at least part of a response to the request.Cloud computing, distributed computing, or client-server computing technology can be used for this purpose.

[0081] One embodiment can be implemented as software (e.g., the program 740) comprising one or more instructions stored in a memory medium (e.g., an internal memory 736 or an external memory 738) that is readable by a machine (e.g., the electronic device 701). A processor of the electronic device 701 can, for example, call and execute at least one of the one or more instructions stored in the memory medium, with or without the use of one or more other components, under the control of the processor. Thus, a machine can be operated to perform at least one function according to the at least one called instruction. The one or more instructions can comprise code generated by a compiler or code executable by an interpreter.A machine-readable storage medium can be provided in the form of a non-transitory storage medium. The term "non-transitory" indicates that the storage medium is a physical device and does not contain a signal (e.g., an electromagnetic wave); however, this term does not distinguish between the location where data is stored semi-permanently in the storage medium and the location where the data is stored temporarily.

[0082] According to one embodiment, a method of disclosure can be included and provided in a computer program product. The computer program product can be traded as a product between a seller and a buyer. The computer program product can be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)) or online via an application store (e.g., Play Store®) or directly between two user devices (e.g., smartphones). In the case of online distribution, at least a portion of the computer program product can be temporarily generated or at least temporarily stored in the machine-readable storage medium, such as memory on the manufacturer's server, an application store server, or a relay server.

[0083] According to one embodiment, each component (e.g., a module or a program) of the components described above can contain a single entity or multiple entities. One or more of the components described above can be omitted, or one or more additional components can be added. Alternatively or additionally, a plurality of components (e.g., modules or programs) can be integrated into a single component. In this case, the integrated component can still perform one or more functions from a respective plurality of components in the same or a similar manner as they were performed by a corresponding plurality of components before integration.Operations performed by the module, program, or other component can be sequential, parallel, repeated, or heuristic, or one or more operations can be performed in a different order or omitted, or one or more operations can be added.

[0084] Even if certain embodiments of the present disclosure have been explained in the detailed description thereof, the present disclosure can be modified in various ways without deviating from the scope of protection of the present disclosure. The scope of protection of the present disclosure is therefore to be determined not only in connection with the described embodiments, but rather on the basis of the attached claims and their equivalents.

Claims

[1] Method for monitoring a physical downlink control channel (PDCCH) by a base station (BS), wherein the method includes the following steps: Setting an initial time gap from one end of the PDCCH to the beginning of a common physical downlink channel (PDSCH); Setting a second time gap from one end of the PDSCH to the beginning of a physical uplink control channel (PUCH); Configuring a high-priority channel and a low-priority channel within a PDCCH monitoring span; Received from a user device (UE) of at least one parameter indicating a minimum amount of additional time required by the UE to process the low-priority channel; and based on at least one parameter, configuring the UE with at least one offset used to increase the first time gap and / or the second time gap. [2] Method according to claim 1, wherein the first time gap and the second time gap are set based on a configuration of the low priority channel, without the high priority channel, in the PDCCH monitoring span. [3] Method according to claim 1, wherein the high priority channel has an Ultra-reliable low-latency communication (uRLLC) service type and the low priority channel has an Enhanced mobile broadband (eMBB) service type. [4] Method according to claim 1, wherein receiving the at least one parameter comprises receiving: a first parameter indicating a minimum amount of the additional time required by the UE for PDSCH reception; and / or a second parameter that indicates a minimum amount of the additional time required by the UE for hybrid automatic repeat request (HARQ) acknowledgment (ACK) preparation. [5] The method of claim 4, wherein configuring the UE includes configuring the UE with: a first offset based on the first parameter to increase the first time gap; and / or a second offset based on the second parameter to increase the second time gap. [6] Method according to claim 1, wherein the UE is configured via a radio-resource-control (RRC) signaling system. [7] Method according to claim 1, wherein the PDCCH monitoring span is for blind detection (BD) and control channel element (CCE) monitoring, respectively. [8] Method according to claim 1, wherein the PDCCH monitoring span comprises a time niche or a plurality of spans within a time niche. [9] Method for monitoring a physical downlink control channel (PDCCH) by a base station (BS), wherein the method comprises: Setting a time gap from one end of the PDCCH to the beginning of a common physical uplink channel (PUSCH); Configuring a high-priority channel and a low-priority channel within a PDCCH monitoring span; Received from a user device (UE), a parameter indicating a minimum amount of additional time required by the UE to process the low-priority channel; and based on the parameter, configure the UE with an offset that is used to increase the time gap. [10] Method according to claim 9, wherein the time gap is set based on a configuration of the low priority channel, excluding the high priority channel, in the PDCCH monitoring span.

Citation Information

Patent Citations

  • Method for communicating in mobile communication system and apparatus for the same

    US20180352601A1