Mechanism for monitoring system information
By configuring system information windows and conflict handling windows for user equipment, the conflict problem between uplink and downlink transmission in non-terrestrial networks was resolved, ensuring the reception of important information and improving the coordination and consistency between the network and user equipment.
Patent Information
- Application Number
- CN202480090601.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-04
- Publication Date
- 2026-11-10
AI Technical Summary
In non-terrestrial networks, due to the longer and more variable round-trip time (RTT), it is difficult for the network to determine whether uplink and downlink transmissions will conflict in a particular user equipment, making it difficult for half-duplex devices to process system information blocks.
By configuring system information windows and conflict handling windows for user equipment, priority link directions are determined to ensure that the reception of important information takes precedence over uplink transmission, thus resolving conflict handling.
It enables conflict resolution for uplink and downlink transmissions in non-terrestrial networks, ensuring the reception of important information and improving coordination and consistency between the network and user equipment.
Smart Images

Figure CN123077227A_ABST
Abstract
Description
Technical Field
[0001] The various exemplary embodiments disclosed herein relate generally to the telecommunications field, and more particularly to methods, apparatus, devices, and computer-readable storage media for monitoring system information. Background Technology
[0002] Half-duplex devices cannot simultaneously receive and transmit. In terrestrial networks, these devices are relatively easy to handle because the round-trip time (RTT) is finite, allowing the network to determine whether uplink and downlink transmissions will conflict. In traditional terrestrial networks, the gNB will also be able to track timing advance commands already provided to the user equipment (UE) over time and therefore have a reasonable understanding of the timing advance applied at the UE side. However, the challenge lies in non-terrestrial networks (NTNs), where the RTT is longer and varies significantly within the cell. For example, the differential latency in a cell deployed at a satellite altitude of 600 km exceeds 3 ms. Such large uncertainties make it difficult for the network to determine whether uplink and downlink transmissions will conflict in a particular UE. Summary of the Invention
[0003] In a first aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to: receive a first configuration of a system information window from a second apparatus, wherein the system information window includes a plurality of monitoring opportunities for scheduling downlink control information of system information blocks; receive from the second apparatus an instruction for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with a monitoring opportunity for the downlink control information or a downlink transmission carrying the system information block; determine, based on at least one of the following, whether monitoring the downlink control information or receiving the system information block takes precedence over the uplink transmission: the position of the monitoring opportunity for the system information block in the system information window, the number of monitoring opportunities for scheduling the system information block, or whether the system information block has been previously received; and monitor the system information block or perform the uplink transmission based on the determination.
[0004] In a second aspect of this disclosure, a first apparatus is provided. The first apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus to: receive a first configuration of a conflict resolution window from a second apparatus; determine a prioritized link direction based on a first priority criterion for the conflict resolution window, based on determining that a link direction conflict exists in the conflict resolution window; and perform transmission or reception based on the prioritized link direction.
[0005] In a third aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to: send a first configuration of a system information window to a first apparatus, wherein the system information window includes a plurality of monitoring opportunities for scheduling downlink control information of system information blocks; and send an instruction to the first apparatus for scheduling an uplink transmission, the uplink transmission being at least one of: monitoring the downlink control information or within the system information window, wherein whether monitoring the downlink control information or receiving at least one of the system information blocks takes precedence over the uplink transmission is based on at least one of: the position of the monitoring opportunity for the system information block within the system information window, the number of monitoring opportunities for scheduling the system information block, or whether the system information block has been previously received.
[0006] In a fourth aspect of this disclosure, a second apparatus is provided. The second apparatus includes: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus to: send a first configuration of a conflict resolution window to a first apparatus, wherein a first priority criterion is applied to the conflict resolution window.
[0007] In a fifth aspect of this disclosure, a method is provided. The method includes: receiving from a second device a first configuration of a system information window, wherein the system information window includes a plurality of monitoring opportunities for scheduling downlink control information of a system information block; receiving from the second device an instruction for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with a monitoring opportunity for the downlink control information or a downlink transmission carrying the system information block; determining, based on at least one of: the position of the monitoring opportunity for the system information block in the system information window, the number of monitoring opportunities for scheduling the system information block, or whether the system information block has been previously received; and monitoring the system information block or performing the uplink transmission based on the determination.
[0008] In a sixth aspect of this disclosure, a method is provided. The method includes: receiving a first configuration of a conflict resolution window from a second device; determining a prioritized link direction based on a determination that a link direction conflict exists in the conflict resolution window, based on a first priority criterion for the conflict resolution window, and performing transmission or reception based on the prioritized link direction.
[0009] In a seventh aspect of this disclosure, a method is provided. The method includes: sending a first configuration of a system information window to a first device, wherein the system information window includes a plurality of monitoring times for scheduling downlink control information of system information blocks; and sending an instruction to the first device for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with either a monitoring time for the downlink control information or a downlink transmission carrying the system information block, wherein whether monitoring the downlink control information or receiving the system information block takes precedence over the uplink transmission is based on at least one of: the position of the monitoring time for the system information block in the system information window, the number of monitoring times for scheduling the system information block, or whether the system information block has been previously received.
[0010] In an eighth aspect of this disclosure, a method is provided. The method includes: sending a first configuration of a conflict resolution window to a first device, wherein a first priority criterion is configured for the conflict resolution window.
[0011] In a ninth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving a first configuration of a system information window from a second apparatus, wherein the system information window includes a plurality of monitoring times for scheduling downlink control information of system information blocks; components for receiving from the second apparatus an indication for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with a monitoring time for the downlink control information or a downlink transmission carrying the system information block; components for determining whether to prioritize monitoring the downlink control information or receiving at least one of the system information blocks over the uplink transmission based on at least one of the following: the position of the monitoring time for the system information block in the system information window, the number of monitoring times for scheduling the system information block, or whether the system information block has been previously received; and components for monitoring the system information block or performing the uplink transmission based on the determination.
[0012] In a tenth aspect of this disclosure, a first apparatus is provided. The first apparatus includes: components for receiving a first configuration of a conflict resolution window from a second apparatus; components for determining a prioritized link direction based on a first priority criterion for the conflict resolution window, based on determining that a link direction conflict exists in the conflict resolution window; and components for performing transmission or reception based on the prioritized link direction.
[0013] In an eleventh aspect of this disclosure, a second apparatus is provided. The second apparatus includes: components for sending a first configuration of a system information window to a first apparatus, wherein the system information window includes a plurality of monitoring times for system information blocks; and components for sending an instruction to the first apparatus for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with a monitoring time for downlink control information or a downlink transmission carrying the system information block, wherein whether monitoring downlink control information or receiving at least one system information block takes precedence over the uplink transmission is based on at least one of: the position of the monitoring time for the system information block in the system information window, the number of monitoring times for scheduling the system information block, or whether the system information block has been previously received.
[0014] In a twelfth aspect of this disclosure, a second apparatus is provided. The second apparatus includes components for transmitting a first configuration of a conflict resolution window to a first apparatus, wherein a first priority criterion is configured for the conflict resolution window.
[0015] In a thirteenth aspect of this disclosure, a computer-readable medium is provided. The computer-readable medium includes instructions stored thereon for causing a device to perform at least the method according to any one of the fifth, sixth, seventh, or eighth aspects.
[0016] It should be understood that the summary portion is not intended to identify key or essential features of the embodiments of this disclosure, nor is it intended to limit the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description
[0017] Some exemplary embodiments will now be described with reference to the accompanying drawings, in which: Figure 1 An example communication environment in which example embodiments of this disclosure may be implemented is shown; Figure 2 The signaling flow for conflict handling according to some example embodiments of this disclosure is shown; Figure 3A and Figure 3B Schematic diagrams of system information windows according to some example embodiments of the present disclosure are shown respectively; Figure 4 The signaling flow for conflict handling according to some other example embodiments of this disclosure is shown; Figure 5 Schematic diagrams of conflict resolution windows according to some example embodiments of the present disclosure are shown respectively; Figure 6 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 7 A flowchart is shown illustrating a method implemented at a first device according to some exemplary embodiments of the present disclosure; Figure 8 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 9 A flowchart is shown illustrating a method implemented at a second device according to some example embodiments of the present disclosure; Figure 10 A simplified block diagram of a device suitable for implementing example embodiments of the present disclosure is shown; and Figure 11 A block diagram of an example computer-readable medium according to some example embodiments of the present disclosure is shown.
[0018] In all the accompanying drawings, the same or similar reference numerals denote the same or similar elements. Detailed Implementation
[0019] The principles of this disclosure will now be described with reference to some exemplary embodiments. It should be understood that these embodiments are described for illustrative purposes only and to assist those skilled in the art in understanding and implementing this disclosure, and do not imply any limitation on the scope of this disclosure. The embodiments described herein can be implemented in various ways other than those described below.
[0020] In the following description and claims, unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.
[0021] References to "an embodiment," "embodiment," "example embodiment," etc., in this disclosure indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes that particular feature, structure, or characteristic. Furthermore, such phrases do not necessarily refer to the same embodiment. Additionally, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is believed that incorporating other embodiments, whether explicitly described or not, to affect such a feature, structure, or characteristic is within the knowledge of those skilled in the art.
[0022] It should be understood that although terms such as "first," "second," etc., preceding nouns may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another, and they do not restrict the order of the nouns. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.
[0023] As used herein, “at least one of the following: a list of two or more elements” and “at least one of the following: a list of two or more elements” and similar wording (where the list of two or more elements is connected by “and” or “or”) means at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.
[0024] As used herein, unless explicitly stated otherwise, the execution step “in response to A” does not indicate that the step is performed immediately after “A” occurs, and may include one or more intermediate steps.
[0025] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the exemplary embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that, when used herein, the terms “comprising,” “including,” “having,” “possessing,” “containing,” and / or “covering” specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0026] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation only in analog and / or digital circuits) and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of analog and / or digital hardware (multiple) circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device such as a mobile phone or server to perform various functions, and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to operate, but may be absent when the software is not required to operate.
[0027] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers implementations of hardware circuitry or processors (or processors in general) and their accompanying software and / or firmware. The term "circuit" also covers, for example and if applicable to a particular claim element, baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or network devices.
[0028] As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as New Radio (NR), Long Term Evolution (LTE), LTE-A Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), etc. Furthermore, communication between terminal devices and network devices in a communication network can be performed according to any suitable generation of communication protocol, including but not limited to first-generation (1G), second-generation (2G), 2.5G, 2.75G, third-generation (3G), fourth-generation (4G), 4.5G, fifth-generation (5G), 5.5G, sixth-generation (6G) communication protocols and / or any other currently known or future-developed protocols. Embodiments of this disclosure can be applied to various communication systems. Given the rapid development of communications, there will certainly be future types of communication technologies and systems that embody the future types of this disclosure. This should not be construed as limiting the scope of this disclosure to the aforementioned systems.
[0029] As used herein, the term "network device" refers to a node in a communications network through which terminal devices access the network and receive services. Depending on the terminology and technology applied, a network device can refer to a base station (BS) or access point (AP), such as a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NRNB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an integrated access and backhaul (IAB) node, a low-power node (such as a femtosecond or picosecond), a non-terrestrial network (NTN) or non-terrestrial network equipment (such as satellite network equipment, low Earth orbit (LEO) satellites, and geostationary orbit (GEO) satellites), an aircraft network equipment, etc. In some example embodiments, the radio access network (RAN) split architecture includes a centralized unit (CU) and a distributed unit (DU) at the IAB host node. The IAB node includes a mobile terminal (IAB-MT) portion that behaves as a UE facing the parent node, and the DU portion of the IAB node behaves as a base station facing the next-hop IAB node.
[0030] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). Terminal devices may include, but are not limited to, mobile phones, cellular phones, smartphones, Voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable terminal devices, personal digital assistants (PDAs), portable computers, desktop computers, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback facilities, in-vehicle wireless terminal devices, wireless endpoints, mobile stations, laptop embedded devices (LEE), laptop mounted devices (LME), USB dongles, smart devices, wireless customer premises equipment (CPE), Internet of Things (IoT) devices, watches or other wearable devices, head-mounted displays (HMDs), vehicles, drones, medical devices and applications (e.g., remote surgery), industrial devices and applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. The terminal device may also correspond to the mobile terminal (MT) portion of an IAB node (e.g., a relay node). In the following description, the terms "terminal device," "communication device," "terminal," "user equipment," and "UE" are used interchangeably.
[0031] As used herein, the terms “resource,” “transmission resource,” “resource block,” “physical resource block” (PRB), “uplink resource,” or “downlink resource” can refer to any resource used to perform communication, such as communication between a terminal device and a network device, including resources in the time domain, frequency domain, spatial domain, code domain, or any other combination of time, frequency, spatial, and / or code domain resources used to enable communication. In the following, unless explicitly stated otherwise, resources in both the frequency and time domains will be used as examples of transmission resources used to describe some exemplary embodiments of this disclosure. Note that the exemplary embodiments of this disclosure are equally applicable to other resources in other domains.
[0032] The term "System Information Block (SIB)" as used herein can refer to information containing Radio Resource Configuration (RRC) information common to all UEs. The term "System Information Window" can refer to the duration during which system information can be received / transmitted. The term "Monitoring Timing" as used herein can refer to a set of time-domain resources during which control information (such as SIBs or Downlink Control Information (DCI)) can be monitored / received. The term "Collision Resolution Window" as used herein can refer to the duration during which transmission collisions are processed / resolved based on configured rules.
[0033] Figure 1 An example communication environment 100 in which exemplary embodiments of the present disclosure can be implemented is shown. In communication environment 100, a plurality of communication devices, including a first device 110 and a second device 120, can communicate with each other. Figure 1 In the example, the first device 110 can be a UE, and the second device 120 can be a base station / gNB serving the UE. The service area of network device 120 can be referred to as cell 102.
[0034] It should be understood that Figure 1 The number of devices and their connections shown are for illustrative purposes only and do not imply any limitation. Communication environment 100 may include any suitable number of devices configured to implement the exemplary embodiments of this disclosure. Although not shown, it will be appreciated that one or more additional devices may be located in cell 102, and one or more additional cells may be deployed in communication environment 100. Note that although shown as a network device, the second device 120 may be another device besides a network device. Although shown as a terminal device, the first device 110 may be another device besides a terminal device.
[0035] In the following description, for illustrative purposes, some example embodiments are described in which the first device 110 operates as a UE and the second device 120 operates as a base station. However, in some example embodiments, the operations described in connection with the terminal device can be implemented at the network device or other device, and the operations described in connection with the network device can be implemented at the terminal device or other device.
[0036] In some example embodiments, the link from the second device 120 to the first device 110 is referred to as a downlink (DL), and the link from the first device 110 to the second device 120 is referred to as an uplink (UL). In the DL, the second device 120 is a transmitting (TX) device (or transmitter), and the first device 110 is a receiving (RX) device (or receiver). In the UL, the first device 110 is a TX device (or transmitter), and the second device 120 is an RX device (or receiver).
[0037] Communication in communication environment 100 can be implemented according to any suitable communication protocol(s), including but not limited to cellular communication protocols such as first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), fifth-generation (5G), 5.5G, and sixth-generation (6G), wireless local network communication protocols such as IEEE 802.11, and / or any other currently known or future-developed protocols. Furthermore, communication can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiplexing (OFDM), Discrete Fourier Transform Extended OFDM (DFT-s-OFDM), and / or any other currently known or future-developed technologies.
[0038] As described above, a half-duplex UE (HD-UE) is proposed. An HD-UE in paired spectrum may not be able to simultaneously transmit and receive on a serving cell with paired spectrum. The HD-UE may not expect to detect the format of the downlink control information (DCI) received in a set of symbols, and the format of the DCI transmitted in any symbol of that set of symbols. If the HD-UE is configured by a higher layer to receive the Physical Downlink Control Channel (PDCCH), or Physical Downlink Shared Channel (PDSCH), or Channel State Information Reference Signal (CSI-RS), or Downlink Positioning Reference Signal (DLPRS) in a set of symbols, then if the HD-UE does not detect a DCI format instructing it to transmit PUSCH, or PUCCH, or PRACH, or SRS in at least one symbol in that set of symbols, the HD-UE may receive PDCCH, or PDSCH, or CSI-RS, or DLPRS; otherwise, the HD-UE will not receive PDCCH, or PDSCH, or CSI-RS, or DLPRS in that set of symbols.
[0039] In some solutions, for Type B half-duplex FDD operation, guard periods (each guard period is called a half-duplex guard subframe) are created by the UE by not receiving downlink subframes immediately preceding uplink subframes from the same UE, and not receiving downlink subframes immediately following uplink subframes from the same UE. One approach to handling timing uncertainties is for the UE to report its application's timing advance (TA), allowing the base station to estimate when the UE will begin uplink transmissions and receive downlink transmissions. TA reports can be specified for both NR and IoTNTN, and can therefore be used to enable the base station to determine if a conflict will occur.
[0040] In some solutions, within the NTN, the UE is responsible for pre-compensating uplink transmissions by setting its TA based on the current UE location, satellite location, and feeder link delay. The latter two are part of satellite-aided information, provided to the UE via SIB19, and constitute the UE's basic system information.
[0041] In some solutions, the UE can apply a System Information (SI) acquisition procedure to obtain location assistance data. UEs in RRC idle and RRC inactive states can ensure that they have (at least) valid versions of the Master Information Block (MIB), SIB1 through SIB4, SIB5 (if the UE supports E-UTRA), SIB11 (if the UE is configured for idle / inactive measurements), SIB12 (if the UE is capable of NR sidelink communication / discovery and is configured by higher layers to receive or send NR sidelink communication / discovery), SIB13, SIB14 (if the UE is capable of V2X sidelink communication and is configured by higher layers to receive or send V2X sidelink communication), SIB15 (if the UE is configured by higher layers to report disaster roaming related information), SIB16 (if the UE is capable of slice-based cell reselection and the UE receives NSAG information for cell reselection from higher layers), SIB17 (if the UE is using TRS resources to conserve power in RRC idle and RRC inactive states), SIB19 (if the UE is accessing NR via NTN), and SIB22 (for ATG access). When SIB19 is received in an NTN cell, a UE in RRC connected state can: start or restart the T430 of the serving cell from the subframe indicated by the epochTime of the serving cell, where the timer value of the serving cell is set to ntn-UlSyncValidityDuration. If SatSwitchWithReSync and t-Service are included, and the UE can support hard satellite handover with resynchronization, and if t-ServiceStart is included and the UE supports soft satellite handover with resynchronization, then the UE can perform a satellite handover with resynchronization between the time indicated by t-ServiceStart and the time indicated by t-Service of the serving cell. Alternatively, the UE can perform a satellite handover with resynchronization at the time indicated by t-Service of the serving cell. The UE can implement this by... ntn- UlSyncValidityDuration and epochTime Attempt to reacquire SIB19 before the indicated duration expires.
[0042] In some solutions, for SI message acquisition, based on searchSpaceOtherSystemInformation Determine the timing of PDCCH (multiple) monitoring. If searchSpaceOtherSystemInformationIf set to zero, the PDCCH monitoring timing for SI message reception in the SI window can be the same as the PDCCH monitoring timing for SIB1. If s earchSpaceOtherSystemInformation If not set to zero, it can be based on... searchSpaceOtherSys temInformation The indicated search space determines the PDCCH monitoring timing for the SI message. The PDCCH monitoring timings for the SI message that do not overlap with the UL symbol (determined according to tdd-UL-DL-ConfigurationCommon) are sequentially numbered from the beginning in the SI window. The [x×N+K]th (or more) PDCCH monitoring timings for the SI message in the SI window can correspond to the Kth transmitted synchronization signal block (SSB), where x = 0, 1, ..., X-1, K = 1, 2, ..., N, and N is determined according to SIB1. ssb- PositionsInBurst The number of SSBs actually transmitted is determined, and X equals CEIL (number of PDCCH monitoring opportunities in the SI window / N). The actually transmitted SSBs are numbered sequentially from the beginning in ascending order of their SSB indices. The UE may assume that, within the SI window, the PDCCH for the SI message is transmitted in at least one PDCCH monitoring opportunity corresponding to each transmitted SSB, and therefore the selection of the SSB for receiving the SI message depends on the UE implementation.
[0043] When the UE receives the SI message, it can: 1> The following determines the start of the SI window for the relevant SI message: 2> If relevant SI messages are configured in schedulingInfoList: 3> For the relevant SI message, determine the number n corresponding to the order of the entries in the SI message list configured by schedulingInfoList in si-SchedulingInfo in SIB1; 3> Determine the integer value x = (n-1) × w, where w is si - WindowLength; 3> The SI window begins in slot #a of a radio frame of SFN mod T=FLOOR(x / N), where a=x mod N, where T is the quasi-period of the associated SI message and N is the number of slots in the radio frame as specified in Technical Specification (TS) 38.213
[13] ; 2> Otherwise, if the relevant SI message is configured in schedulingInfoList2; 3> Determine the integer value x = (si - WindowPosition - 1) × w, where w is si - WindowLength; 3> The SI window begins with slot #a in a radio frame of SFN mod T=FLOOR(x / N), where a=x mod N, where T is the quasi-period of the relevant SI message, and N is the number of slots in a radio frame specified in TS 38.213
[13] ; … 1> Receive the PDCCH containing the scheduled RNTI from the beginning of the SI window, i.e., the SI-RNTI during the monitoring of (multiple) PDCCHs used for SI message acquisition, and continue until the end of the SI window, the absolute time length of the SI window is given by si-WindowLength, or until the SI message is received; 1> If an SI message is not received at the end of the SI window, the relevant SI message will be received again at the next SI window time during the current modification period; 1> If all(multiple) SIBs and / or (multiple) posSIBs requested in the DedicatedSIBRequest message have been retrieved: 2> If running, stop timer T350.
[0044] In some solutions, if the UE can acquire broadcast SI messages without interrupting unicast or MBS multicast data reception (i.e., broadcast and unicast / MBS multicast beams are quasi-co-located), then only the UE needs to acquire broadcast SI messages. The UE may not need to monitor the PDCCH(s) corresponding to each transmitted SSB within the SI window. If no relevant SI message is received in the current modification period, the processing of SI message acquisition is left to the UE. When acquiring the requested SSB(s), a UE in RRC connected state can stop PDCCH monitoring for the relevant SI message during the SI window.
[0045] This is problematic in NTN, where the UE must maintain a valid SIB19 to properly pre-compensate uplink transmissions; that is, the UE needs to read a new SIB19 before the validity timer for the SIB19 expires. If the UE does not have a valid SIB19, it is not allowed to send scheduled PUSCH, PUCCH, Physical Random Access Channel (PRACH), or Sound Reference Signal (SRS) under any circumstances (because the expiration of the ephemeris information validity timer will cause the UE to automatically lose its UL synchronization).
[0046] An example solution would be to change the rules to prioritize SIB19, but the challenge is that the network doesn't know when the UE will attempt to acquire SIB19. The expected network configuration would be that the gNB provides SIB19 periodically for a much shorter duration compared to its validity period. Reacquisition of SIB19 is based on its validity period, which is transmitted in the information element NTN-Config.
[0047] It can be seen that the effective duration ranges from 5 seconds to several minutes, and since the SI period is 8-512 radio frames (each radio frame is 10ms long), the number of SI windows within this range can be quite large. Furthermore, the SI window length is 5-1280 time slots, and depending on the search space configuration, there can be many PDCCH monitoring opportunities (used for scheduling SIBs) within each SI window. If the network is configured to provide SIB19 approximately every 1 second, and the effective duration is 10 seconds, the UE has the opportunity to monitor every second, but in principle, it only needs to actually read SIB19 every 10 seconds (or even every 20 seconds if the UE supports "backpropagation" and the gNB provides future ephemeris information). However, the network will not know which SIB scheduling window within the SIB scheduling window the UE will actually read SIB19 during the effective duration.
[0048] This means the network scheduler will have to block a significant amount of uplink resources because they conflict with PDCCH monitoring timing, which may potentially include SIB19 scheduling that the UE might need (due to the validity timer nearing expiration). Furthermore, when considering TA mismatch between the actual TA used by the UE and the assumed TA at the gNB based on available TA reports, can existing processing rules be reused or updated for the following situations: Situation 1: Conflict between dynamically scheduled DL reception and semi-statically configured UL transmission; Situation 2: Conflict between semi-statically configured DL reception and dynamically scheduled UL transmission; Situation 3: Conflict between semi-statically configured DL reception and semi-statically configured UL transmission; Situation 4: Conflict between dynamically scheduled DL reception and dynamically scheduled UL transmission; Situation 5: Conflict between configured SSB and dynamically scheduled or configured UL transmission; Situation 6: Conflict between dynamic or semi-static DL and valid RO; Situation 7: Conflict due to direction switching.
[0049] In the example solution, certain SI windows can be served, meaning that the current conflict rules will not apply within the window, and the UE can preferentially receive SIB19. This solution does not consider when an individual UE previously acquired SIB19, and therefore, for some UEs, their preferred SIB19 SI window being far from the reserved window may be inconvenient, causing the UE to receive SIB19 "prematurely" relative to the expiration of the potential validity timer. Furthermore, the SI window (up to 1280 slots) can include many PDCCH monitoring opportunities (depending on the search space configuration), where the UE will only need one or a few PDCCH monitoring opportunities to acquire SIB19. Therefore, blocking all PDCCH monitoring opportunities within the SI window is suboptimal.
[0050] According to some example embodiments of this disclosure, a solution for conflict resolution is provided. Specifically, the UE can be configured by the network to prioritize monitoring of a subset of configured PDCCH monitoring timings within an SI window. Furthermore, it proposes a conflict resolution window where the UE will prioritize a configured direction (i.e., UL or DL or other, such as sidelinks), whereby the UE can prioritize PDCCH monitoring and associated PDSCH over scheduled UL transmissions within the window. In this way, it can resolve conflicts, thereby ensuring the reception of critical information. Moreover, it enables the network and the UE to have a consistent understanding of when the UE will prioritize SIB19 reception over uplink transmissions.
[0051] Exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. For illustrative purposes, exemplary embodiments are described with reference to SIB reception. Note that the exemplary embodiments of the present disclosure can be implemented in any suitable scenario.
[0052] Figure 2 A signaling flow 200 for distributed feedback according to some example embodiments of this disclosure is illustrated. For illustrative purposes, reference is made to... Figure 1 The first device 110 and the second device 120 shown are used to describe the signaling flow 200.
[0053] The second device 120 sends (2010) the first configuration of the system information window to the first device 110. In other words, the first device 110 receives (2010) the first configuration of the system information window from the second device 120. In some embodiments, the first configuration may indicate the start time and duration of the system information window. Alternatively or additionally, the first configuration may indicate the start time and end time of the system information window. For example, as... Figure 3A and Figure 3B As shown, the first configuration can instruct the system information window 310. Table 1 below shows an example of the first configuration of the system information window. Note that Table 1 is only an example and not a limitation.
[0054] Table 1
[0055] The system information window includes multiple monitoring opportunities for downlink control information (DCI) used to schedule the SIB. For example, such as... Figure 3A and Figure 3B As shown, the system information window 310 may include monitoring times 320-1, 320-2, 320-3, 320-4, 320-5, 320-6, 320-7, and 320-8. DCIs for scheduling the SIB can be sent / received on one or more of these monitoring times. Note that... Figure 3A and Figure 3B The number of monitoring opportunities shown is merely an example and not a limitation. Table 2 below shows an example of the Information Element (IE) search space. Note that Table 2 is merely an example and not a limitation. It can be seen that PDCCH monitoring is defined as having a period in slots, a duration in slots, and then the number of symbols of the PDCCH monitored per slot with the duration. Therefore, there can be one or more PDCCH monitoring opportunities for the DCI used to schedule the SIB.
[0056] Table 2
[0057] In some example embodiments, within the system information window, a set of monitoring opportunities may take precedence over uplink transmissions. In other words, if uplink transmissions conflict with at least one of the following: SIB reception and / or monitoring the DCI that schedules the SIB during that set of monitoring opportunities, the first device 110 may prefer to monitor the DCI and / or SIB reception rather than uplink transmissions.
[0058] In some example embodiments, the second device 120 may send (2015) a second configuration indicating a set of monitoring times among a plurality of monitoring times to the first device 110. In other words, the first device 110 may receive (2015) the second configuration from the second device 120.
[0059] In some example embodiments, the first device 110 may prioritize X first monitoring opportunities within the system information window over scheduled uplink transmissions, while ignoring the remaining Y monitoring opportunities if the second device 120 schedules uplink transmissions. In this case, X and Y are integers, and the sum of X and Y may equal the number of monitoring opportunities in the system information window. For example, as... Figure 3AAs shown, the first device 110 can prioritize the first four monitoring opportunities within the system information window 310 (i.e., monitoring opportunities 320-1, 320-2, 320-3, and 320-4), and if uplink transmission is scheduled, the remaining four monitoring opportunities (i.e., monitoring opportunities 320-5, 320-6, 320-7, and 320-8) can be ignored. Note that... Figure 3A The number of monitoring opportunities in this group shown is merely an example and not a limitation.
[0060] In some example embodiments, the second configuration may indicate the number of monitoring moments in the group of monitoring moments 310. For example, as Figure 3A As shown, the second configuration can indicate four monitoring times in the group of monitoring times 310.
[0061] Alternatively, the second configuration can indicate a time window relative to the start of the system information window and include the timeframe for that set of monitoring events. For example, as Figure 3B As shown, time window 330' may include monitoring opportunities 320-1, 320-2, 320-3, and 320-4. A second configuration may indicate time window 330' relative to the start 340 of system information window 310.
[0062] In some other embodiments, this set of monitoring timings may correspond to a configured window in which monitoring system information blocks take precedence over uplink transmissions. As an example, such as... Figure 5 As shown, the monitoring times 520-1, 520-2, 520-3, 520-4, and 520-5 correspond to the configured window 510. Note that... Figure 5 The number of monitoring times shown in this set of monitoring times is merely an example and not a limitation. In some example embodiments, the configuration windows for conflict handling are periodically distributed within the system information window. For example, the system information window may include windows for one or more configurations for conflict handling.
[0063] In some example embodiments, network configuration can determine which link direction is prioritized within a configuration window for conflict resolution. In some example embodiments, the DL direction may be prioritized. In this case, if a conflict occurs within the configuration window, the first device 110 may prioritize DL reception over UL transmission. Alternatively, the UL direction may be prioritized. In this case, if a conflict occurs within the configuration window, the first device 110 may prioritize UL transmission over DL reception. In some other embodiments, the SL direction may be prioritized.
[0064] In some example embodiments, the start and duration of the configured window can be configured by a second device. Alternatively, the start and duration of the configured window can be predefined. For example, such as... Figure 5 As shown, the start 530 and duration of the configured window 510 can be configured or predefined. In some example embodiments, the start and duration of the configured window can be relative to the system information window. Alternatively, the start and duration of the configured window can be absolute values.
[0065] In some example embodiments, a set of downlink channels that take priority over uplink channels can be within a configured window. For example, a configured window can be defined to prioritize only one set of DL channels / signals (e.g., PDCCH monitoring) without prioritizing other DL channels / signals. Alternatively, all downlink channels that take priority over uplink channels can be within a configured window. For example, a configured window can be defined to prioritize all DL channels / signals over UL channels / signals.
[0066] In some example embodiments, the configured window may be specific to the first device 110. In some example embodiments, the size of the configured window may be based on the duration for which the first device 110 reads the downlink channel. For example, the size of the window may be based on the time for which the UE reports / requests to read the DL channel, such as the PDCCH that includes the PDSCH when scheduling SIB19.
[0067] Alternatively, the start time of the configured window can be based on the last time a system information block was successfully read. For example, the start time of the window can be based on the time when the UE reported the last successful read of SIB19. Successfully reading SIB19 can refer to successfully receiving and / or decoding the SIB.
[0068] In some example embodiments, the number of monitoring opportunities in this set of monitoring opportunities may be based on the overlap between the search space configuration and the system information window. For example, the number X may be the number of monitoring opportunities based on the overlap between the search space configuration and the system information window.
[0069] Alternatively, the number of monitoring opportunities in this set of monitoring opportunities can be based on the overlap between the physical downlink control channel monitoring opportunities used for system information and the system information window. For example, the number X can be the monitoring opportunities based on the overlap of the PDCCH monitoring opportunities and the system information window (or the configuration window used for the conflict window).
[0070] The second device 120 sends (2020) an instruction to the first device 110 for scheduling an uplink transmission that at least partially overlaps with a downlink transmission carrying system information blocks during a monitoring period for downlink control information within the system information window. In other words, the first device 110 receives from the second device 120 an instruction for scheduling the uplink transmission that at least partially overlaps with a downlink transmission carrying system information blocks during a monitoring period for downlink control information within the system information window.
[0071] The first device 110 determines (2030) whether to prioritize at least one of monitoring the DCI or receiving the SIB over the uplink transmission based on one or more of the following: the position of the monitoring timing for the system information block in the system information window, the number of monitoring timings for scheduling the system information block, or whether a system information block has been previously received. In some example embodiments, the first device 110 may monitor (2040) the SIB based on this determination. For example, monitoring (2040) the SIB may include monitoring the DCI for scheduling the SIB. As another example, monitoring (2040) the SIB may include receiving the SIB. Alternatively, the first device 110 may send (2040') the uplink transmission based on this determination. In this way, the UE can receive the SIB in a timely manner and avoid unnecessary delays for the uplink transmission. Example embodiments are described in detail below.
[0072] In some example embodiments, if the location of the monitoring opportunity for system information is within the group of monitoring opportunities in the system information window, the first device 110 may prioritize at least one of the following over uplink transmission: monitoring the reception of DCI or SIB. That is, if the location of the monitoring opportunity for system information is within the group of monitoring opportunities in the system information window, the first device 110 may perform monitoring of DCI or reception of SIB. For example, if the next monitoring opportunity is part of X1 (X1 is an integer) first monitoring opportunities in the system information window, the first device 110 may prioritize downlink reception if downlink reception is scheduled. For example, as... Figure 3A As shown, if the location of a monitoring opportunity for a system information block (such as monitoring opportunity 320-2) is within the set of monitoring opportunities 330, then the first device 110 can monitor the system information block. For example, if a scheduled uplink transmission conflicts with the reception of an SIB during monitoring opportunity 320-2, then the first device 110 can monitor the system information block during monitoring opportunity 320-2 and skip the uplink transmission. In some example embodiments, X1 may begin at an offset from the start of the system information window, and the value of X1 may be configured by the second device 120.
[0073] In some other example embodiments, if the next monitoring opportunity is within X2ms from the start of the system information window, then if downlink reception is scheduled, the first device 110 can prioritize downlink reception. For example, as Figure 3B As shown, if the location of the monitoring opportunity for the system information block is within the duration 330', the first device 110 can monitor the system information block.
[0074] Alternatively, if the location of the monitoring opportunity for system information is outside (i.e., not included in) the group of monitoring opportunities in the system information window, the first device 110 may prioritize uplink transmission over monitoring of DCI and / or reception of SIB. That is, if the location of the monitoring opportunity for system information is not within the group of monitoring opportunities in the system information window, the first device 110 may perform uplink transmission. For example, if the next monitoring opportunity is not part of X1 first monitoring opportunities in the system information window, the first device 110 may prioritize uplink transmission if it is scheduled. For example, as... Figure 3A As shown, if the location of a monitoring opportunity for a system information block (such as monitoring opportunity 320-6) is outside the set of monitoring opportunities 330, the first device 110 can perform an uplink transmission. For example, if the scheduled uplink transmission conflicts with the reception of the SIB during monitoring opportunity 320-6, the first device 110 can perform the uplink transmission and skip monitoring the SIB during monitoring opportunity 320-6.
[0075] In some other example embodiments, if the next monitoring opportunity is beyond X2ms (where X2 can be any suitable value) from the start of the system information window, then if uplink transmission is scheduled, the first device 110 can prioritize uplink transmission. For example, as Figure 3B As shown, if the location of the monitoring timing for the system information block is outside the duration 330', the first device 110 can perform an uplink transmission. In some example embodiments, X2 can start at an offset from the beginning of the system information window, and the value of X2 can be configured by the second device 120.
[0076] In some example embodiments, if the number of monitoring occasions in the subset of monitoring occasions where system information blocks are scheduled is less than a threshold number, the first device 110 may prioritize monitoring the system information blocks over uplink transmission during the subset of monitoring occasions or the group of monitoring occasions. In some example embodiments, if the second device 120 schedules the SIB only in a subset (e.g., Z monitoring occasions) of the group of monitoring occasions (e.g., X monitoring occasions, Z<X), the first device 110 may defer the time to apply the recovered collision rule to allow the group of monitoring occasions that actually result in the scheduling of SIB19, which means the rule is not recovered until after the first X monitoring occasions. In some other example embodiments, the collision rule may be recovered when X or Z is achieved. For example, as Figure 3B shown, if X is 5 and Z is 3 and the second device 120 schedules the system information blocks in monitoring occasions 320-1, 320-2 and 320-6, the second device may recover the rule after 5 monitoring occasions.
[0077] In some example embodiments, if the number of monitoring occasions at which system information blocks are scheduled is less than a threshold number, the first device 110 may prioritize monitoring the system information blocks over uplink transmission during the subset of monitoring occasions or the group of monitoring occasions. For example, as Figure 3B shown, if the number of monitoring occasions at which system information blocks are scheduled is less than a threshold number, the first device 110 may prioritize monitoring the system information blocks over uplink transmission during the subset 350' of monitoring occasions or the group 330' of monitoring occasions.
[0078] In some example embodiments, if the number of monitoring occasions in the subset of monitoring occasions where system information blocks are scheduled is less than a threshold number, and the monitoring occasion for system information is outside the subset of monitoring occasions or the group of monitoring occasions, the first device 110 may perform uplink transmission. The threshold number may be any suitable value. For example, as Figure 3B shown, if the number of monitoring occasions at which system information blocks are scheduled is less than a threshold number, and the monitoring occasion is outside the subset 350' of monitoring occasions, the first device 110 may perform uplink transmission. As another example, if the number of monitoring occasions at which system information blocks are scheduled is less than a threshold number, and the monitoring occasion is outside the group 330' of monitoring occasions, the first device 110 may perform uplink transmission.
[0079] In some other example embodiments, if the number of monitoring occasions at which system information blocks are scheduled is equal to or greater than a threshold number, and the monitoring occasion for system information is outside the subset of monitoring occasions, the first device 110 may perform uplink transmission. For example, as Figure 3BAs shown, if the number of monitoring opportunities scheduled for the system information block is equal to or greater than the threshold number, and the monitoring opportunity for the system information is outside the subset 350' of the monitoring opportunities, then the first device 110 can perform uplink transmission.
[0080] In some example embodiments, the number of monitoring moments in the group of monitoring moments, or the duration of the group of monitoring moments, may correspond to UE capabilities. For example, if the UE has limited reception capabilities or is in poor coverage conditions, the UE may require multiple PDCCH and PDSCH receptions to fully receive and decode the associated SIB. Therefore, the UE may report the value of X to the network. For example, the first device 110 may send information to the second device 120 indicating the number of monitoring moments required to monitor the system information block, or the duration of the group of monitoring moments.
[0081] In some example embodiments, if the first device 110 receives SIB19 and this reception occurs before the conflict rule is restored, the first device 110 may notify the second device 120. The notification can then cause the rule to be restored (i.e., the uplink is prioritized). For example, the first device 110 may send an indication to the second device regarding the reception of the system information block. In some example embodiments, if the system information block is received in the current system information window, the first device 110 may send an indication to the second device regarding the reception of the system information block. In some other example embodiments, if the system information block is received in another system information window within the same system information modification window as the current system information window, the first device 110 may send an indication to the second device regarding the reception of the system information block.
[0082] In some example embodiments, if a system information block has been previously received, the first device 110 may prioritize uplink transmission over the DCI of monitoring and / or receiving the SIB. For example, if the system information block is received in a system information window, or if the system information block is received in another system information window within the same system information modification window as the current system information window, the first device 110 may perform the uplink transmission. The system information within the same system information modification window may remain unchanged. For example, such as Figure 3A As shown, if a system information block is received in system information window 310, the first device 110 can prioritize uplink transmission. Alternatively, if the received system information block is in another system information window (not shown) within the same system information modification window as system information window 310, the first device 110 can prioritize uplink transmission.
[0083] Alternatively, if no system information block has been received previously, the first device 110 may prioritize the monitoring of the DCI of the scheduling SIB and / or the reception of the SIB over uplink transmission. For example, if the first device 110 does not receive the system information block in the system information modification window that includes the system information block, the first device 110 may monitor the system information block.
[0084] In some example embodiments, if a system information block is received before a certain time, the first device 110 may send an indication of the reception of the system information block. For example, the first device 110 may be configured to report only the SIB19 reception if the SIB19 reception occurs T seconds before the conflict rule is restored based on the above options (e.g., T seconds before the Xth PDCCH monitoring time).
[0085] In some example embodiments, the indication is sent via signaling dedicated to the first device. For example, the first device 110 may provide notification via a UE-dedicated signaling channel pre-configured for the UE, meaning that the first device 110 knows the exact time and resources available for providing the indication. The availability of the configured resources may also be conditional on parameters Z and X. One channel that can be used to provide the signaling would be PRACH, where a dedicated random access preamble can be used for such an indication.
[0086] According to the reference Figure 2 The described example implementation enables the network and the UE to have a consistent understanding of when the UE can prioritize SIB19 reception over uplink transmissions. Furthermore, it provides the UE with the opportunity to acquire SIB19 while simultaneously providing the network with the option to schedule uplink transmissions, which conflicts with the timing of PDCCH monitoring for SIB19.
[0087] Figure 4 A signaling flow 400 for distributed feedback according to some example embodiments of this disclosure is illustrated. For illustrative purposes, reference is made to... Figure 1 The first device 110 and the second device 120 shown are used to describe the signaling flow 400.
[0088] The second device 120 sends (4010) a first configuration of the conflict resolution window to the first device 110. In other words, the first device 110 receives (4010) the first configuration of the conflict resolution window from the second device 120. In some embodiments, the first configuration may indicate the start time and duration of the conflict resolution window. Alternatively or additionally, the first configuration may indicate the start and end times of the conflict resolution window. For example, as... Figure 5 As shown, the first configuration can indicate the conflict handling window 510.
[0089] In some example embodiments, the collision handling window is localized or distributed. Alternatively or additionally, the collision handling window is periodic or aperiodic. In some other example embodiments, the collision handling window is semi-statically or dynamically configured. In some example embodiments, the collision handling window is used for at least one of the following: all channels or subsets of channels in the uplink, all channels or subsets of channels in the downlink, all signals or subsets of signals in the uplink, or all signals or subsets of signals in the downlink.
[0090] If a link direction conflict exists within the conflict resolution window, the first device 110 determines (4020) a prioritized link direction based on a first priority criterion. The first device 110 may then perform (4030) transmission based on this prioritized link direction. Alternatively, the first device 110 may perform (4030') reception based on this prioritized link direction. In some example embodiments, the priority link direction in the configuration window used for conflict resolution can be determined by network configuration. That is, the first priority criterion can be configured by the second device 120. Alternatively, the first priority criterion can be predefined.
[0091] In some example embodiments, a first priority criterion may indicate that the DL direction is prioritized. In this case, if a conflict occurs within the conflict resolution window, the first device 110 may perform DL reception before UL transmission. For example, as Figure 5 As shown, if a conflict occurs in a conflict handling window 510 (such as monitoring timing 520-2), the first device 110 may perform DL reception instead of UL transmission in the conflict handling window 510.
[0092] Alternatively, a first priority criterion may indicate that the UL direction is prioritized. In this case, if a conflict occurs within the conflict resolution window, the first device 110 may perform UL transmission before DL reception. In some other embodiments, a first priority criterion may indicate that the DL direction is prioritized.
[0093] In some example embodiments, the prioritized link direction in the conflict resolution window may be a configured link direction from the second device 120. Alternatively, the prioritized link direction in the conflict resolution window may be a low-priority link direction based on a second priority criterion applied in the absence of a conflict resolution window.
[0094] In some example embodiments, the first device 110 may change the first priority criterion to a second priority criterion at the end of the conflict resolution window or after the end of the conflict resolution window. For example, as Figure 5As shown, the first device 110 can change the first priority criterion to a second priority criterion at or after the end of the conflict handling window 540. As an example, if the first priority criterion indicates that the DL direction is prioritized and the second priority criterion indicates that the UL direction is prioritized, and if a conflict occurs after the end of the conflict handling window 510 540 (such as during monitoring periods 520-6), the first device 110 can prioritize UL reception over DL transmission during monitoring periods 520-6. In some example embodiments, if there is no link direction conflict in the link direction conflict window, the first device 110 can perform link direction processing without changing the priority. For example, if there is no conflict in the conflict window 510, the first device 110 can perform reception or transmission based on the second priority criterion.
[0095] According to the reference Figure 4 The example embodiments described provide a window when conflict handling is configured to enable the network and UE to reach a consensus on "prioritizing PDCCH reception" or "prioritizing in any UL / DL conflict", thus giving the UE the opportunity to prioritize UL or DL as required.
[0096] It should be noted that, for reference Figures 2 to 5 The described example embodiments can be implemented independently. Alternatively, refer to... Figures 2 to 5 The example embodiments described can be combined in any suitable manner.
[0097] Figure 6 A flowchart of an example method 600 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 600 is described from the angle of the first device 110 in the middle.
[0098] In box 610, the first device receives a first configuration of the system information window from the second device. The system information window includes multiple monitoring opportunities used to schedule downlink control information for system information blocks.
[0099] At box 620, the first device receives from the second device an instruction for scheduling an uplink transmission that at least partially overlaps with a downlink transmission carrying system information blocks within the system information window, either for monitoring downlink control information.
[0100] At box 630, the first device determines whether to prioritize monitoring downlink control information, receiving system information blocks, or uplink transmissions based on at least one of the following: the position of the monitoring timing for system information blocks in the system information window, the number of monitoring timings for scheduling system information blocks, or whether system information blocks have been received previously.
[0101] In box 640, the first device uses this determination to monitor system information blocks or perform uplink transmissions.
[0102] In some example implementations, a set of monitoring times among multiple monitoring times takes precedence over uplink transmission within the system information window.
[0103] In some example embodiments, method 600 further includes: monitoring a system information block based on the determination that the location of the monitoring timing for system information is within the set of monitoring timings in the system information window; or performing uplink transmission based on the determination that the location of the monitoring timing for system information is outside the set of monitoring timings in the system information window.
[0104] In some example embodiments, method 600 further includes receiving a second configuration from a second device, the second configuration indicating the set of monitoring times among a plurality of monitoring times.
[0105] In some example embodiments, the second configuration indicates the number of monitoring times in the set of monitoring times, or the second configuration indicates a time window that includes the set of monitoring times relative to the start of the system information window.
[0106] In some example embodiments, this set of monitoring times corresponds to a configured window in which monitoring system information blocks take precedence over uplink transmissions.
[0107] In some example implementations, the configured windows are distributed periodically within the system information window.
[0108] In some example implementations, a set of downlink channels that take precedence over uplink channels are within a configured window, or all downlink channels that take precedence over uplink channels are within a configured window.
[0109] In some example embodiments, the configuration window for monitoring system information blocks takes precedence over uplink transmissions and is specific to the first device.
[0110] In some example embodiments, the size of the configured window is based on the duration for which the downlink channel is read by the first device, or the start time of the configured window is based on the last time a system information block was successfully read.
[0111] In some example embodiments, the number of monitoring opportunities in this set of monitoring opportunities is based on the overlap between the physical downlink control channel monitoring opportunities used for system information and the system information window.
[0112] In some example embodiments, method 600 further includes prioritizing the monitoring of system information blocks over uplink transmission during a subset of monitoring opportunities or the set of monitoring opportunities, based on the determination that the number of monitoring opportunities in which system information blocks are scheduled is less than a threshold number.
[0113] In some example embodiments, method 600 further includes: performing uplink transmission based on determining that the number of monitoring opportunities in which the system information block is scheduled is less than a threshold number and that the monitoring opportunities for the system information are a subset of the monitoring opportunities or outside the set of monitoring opportunities.
[0114] In some example embodiments, method 600 further includes: performing uplink transmission based on the determination that the number of monitoring opportunities for system information blocks scheduled is equal to or greater than a threshold number and that the monitoring opportunities for system information are outside a subset of the monitoring opportunities.
[0115] In some example embodiments, method 600 further includes transmitting to a second device information indicating the number of monitoring opportunities required for a monitoring system information block or the duration of such a set of monitoring opportunities.
[0116] In some example embodiments, method 600 further includes sending an instruction to a second device regarding the receipt of a system information block.
[0117] In some example embodiments, method 600 further includes: performing uplink transmission based on the determination of previously received system information blocks; or monitoring system information blocks based on the determination that no system information has been previously received.
[0118] In some example embodiments, method 600 further includes: based on determining that the system information block was received before a certain time, sending an indication regarding the reception of the system information block.
[0119] In some example embodiments, the instruction is sent via signaling dedicated to the first device.
[0120] In some example embodiments, the first device is a terminal device, and the second device is a network device.
[0121] Figure 7 A flowchart of an example method 700 implemented at a first device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 700 is described from the angle of the first device 110 in the middle.
[0122] In box 710, the first device receives a first configuration of the conflict handling window from the second device.
[0123] At box 720, based on the determination that a link direction conflict exists in the conflict resolution window, the first device determines the priority link direction based on a first priority criterion for the conflict resolution window.
[0124] At box 730, the first device performs transmission or reception based on the prioritized link direction.
[0125] In some example embodiments, the prioritized link direction in the conflict resolution window is one of the following: a configured link direction from the second device, or a link direction with low priority based on a second priority criterion applied in the absence of a conflict resolution window.
[0126] In some example embodiments, the first device changes the first priority criterion to a second priority criterion at the end of the conflict resolution window or after the end of the conflict resolution window.
[0127] In some example embodiments, the first device performs link direction processing without changing the priority, based on the determination that there is no link direction conflict in the link direction conflict window.
[0128] In some example embodiments, the conflict resolution window is localized or distributed, or it is periodic or aperiodic, or it is semi-statically or dynamically configured.
[0129] In some example embodiments, the conflict handling window is used for at least one of the following: all channels or subsets of channels in the uplink, all channels or subsets of channels in the downlink, all signals or subsets of signals in the uplink, or all signals or subsets of signals in the downlink.
[0130] In some example embodiments, the first device is a terminal device, and the second device is a network device.
[0131] Figure 8 A flowchart of an example method 800 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 800 is described by the angle of the second device 120 in the middle.
[0132] In box 810, the second device sends a first configuration of the system information window to the first device. The system information window includes multiple monitoring opportunities used to schedule downlink control information for system information blocks.
[0133] At box 820, the second device sends an instruction to the first device for scheduling an uplink transmission that at least partially overlaps with a monitoring timing for downlink control information or a downlink transmission carrying a system information block within the system information window, wherein whether monitoring downlink control information or receiving a system information block takes precedence over the uplink transmission is based on at least one of the following: the position of the monitoring timing for the system information block in the system information window, the number of monitoring timings for scheduling system information blocks, or whether a system information block has been previously received.
[0134] In some example implementations, within the system information window, a set of monitoring times from multiple monitoring times takes precedence over uplink transmissions.
[0135] In some example embodiments, the second device is configured to send a second configuration to the first device, the second device indicating the set of monitoring times among a plurality of monitoring times.
[0136] In some example embodiments, the second configuration indicates the number of monitoring times in the set of monitoring times, or the second configuration indicates a time window that includes the set of monitoring times relative to the start of the system information window.
[0137] In some example embodiments, this set of monitoring timings corresponds to a configured window for conflict resolution, in which monitoring system information blocks take precedence over uplink transmissions.
[0138] In some example implementations, the configured windows are distributed periodically within the system information window.
[0139] In some example implementations, a set of downlink channels that take precedence over uplink channels are within a configured window, or all downlink channels that take precedence over uplink channels are within a configured window.
[0140] In some example embodiments, the configuration window for monitoring system information blocks takes precedence over uplink transmissions and is specific to the first device.
[0141] In some example embodiments, the size of the configured window is based on the duration for which the downlink channel is read by the first device, or the start time of the configured window is based on the last time a system information block was successfully read.
[0142] In some example embodiments, the number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the search space configuration and the system information window, or the number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the physical downlink control channel monitoring opportunities for system information and the system information window.
[0143] In some example embodiments, system information blocks are scheduled within a subset of the monitoring times of this set of monitoring times.
[0144] In some example embodiments, the second device receives information from the first device indicating the number of monitoring opportunities required for a monitoring system information block or the duration of that set of monitoring opportunities.
[0145] In some example embodiments, the second device receives an instruction from the first device regarding the receipt of a system information block.
[0146] In some example embodiments, the instruction is sent via signaling dedicated to the first device.
[0147] Figure 9 A flowchart of an example method 900 implemented at a second device according to some example embodiments of the present disclosure is shown. For the purposes of discussion, [the following will be discussed]. Figure 1 Method 1000 is described by the angle of the second device 120 in the middle.
[0148] At frame 910, the second device transmits a first configuration of the conflict resolution window to the first device, wherein a first priority criterion applies to the conflict resolution window.
[0149] At frame 920, the second device can perform transmission or reception.
[0150] In some example embodiments, the prioritized link direction in the conflict resolution window is one of the following: a configured link direction from the second device, or a link direction with low priority based on a second priority criterion applied in the absence of a conflict resolution window.
[0151] In some example embodiments, the first priority criterion is changed to the second priority criterion at or after the end of the conflict resolution window.
[0152] In some example implementations, link direction processing is performed without changing the priority, based on the determination that there is no link direction conflict in the link direction conflict window.
[0153] In some example embodiments, the conflict resolution window is localized or distributed, or it is periodic or aperiodic, or it is semi-statically or dynamically configured.
[0154] In some example embodiments, the conflict handling window is used for at least one of the following: all channels or subsets of channels in the uplink, all channels or subsets of channels in the downlink, all signals or subsets of signals in the uplink, or all signals or subsets of signals in the downlink.
[0155] In some example embodiments, the first device is a terminal device, and the second device is a network device.
[0156] In some example embodiments, a first means capable of performing any of the methods in method 600 (e.g., Figure 1 The first device 110 may include a component for performing a corresponding operation of method 600. This component can be implemented in any suitable form. For example, the component can be implemented in a circuit or software module. The first device can be implemented as... Figure 1 The first device 110 or included in Figure 1 The first device 110 in the middle.
[0157] In some example embodiments, the first device includes: components for receiving a first configuration of a system information window from a second device, wherein the system information window includes a plurality of monitoring opportunities for scheduling downlink control information of a system information block; components for receiving from the second device an indication for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with a monitoring opportunity for the downlink control information or a downlink transmission carrying the system information block; components for determining whether to prioritize monitoring the downlink control information or receiving at least one of the system information blocks over the uplink transmission based on at least one of the following: the position of the monitoring opportunity for the system information block in the system information window, the number of monitoring opportunities for scheduling the system information block, or whether the system information block has been previously received; and components for monitoring the system information block or performing the uplink transmission based on the determination.
[0158] In some example implementations, within the system information window, a set of monitoring times from multiple monitoring times takes precedence over uplink transmissions.
[0159] In some example embodiments, the first apparatus further includes: a component for monitoring a system information block based on the location of the monitoring timing for system information being within the set of monitoring timings in the system information window; or a component for performing uplink transmission based on the location of the monitoring timing for system information being outside the set of monitoring timings in the system information window.
[0160] In some example embodiments, the first device further includes a component for receiving a second configuration from the second device, the second configuration indicating the set of monitoring times among a plurality of monitoring times.
[0161] In some example embodiments, the second configuration indicates the number of monitoring times in the set of monitoring times, or the second configuration indicates a time window that includes the set of monitoring times relative to the start of the system information window.
[0162] In some example embodiments, this set of monitoring times corresponds to a configured window in which monitoring system information blocks take precedence over uplink transmissions.
[0163] In some example implementations, the configured windows are distributed periodically within the system information window.
[0164] In some example implementations, a set of downlink channels that take precedence over uplink channels are within a configured window, or all downlink channels that take precedence over uplink channels are within a configured window.
[0165] In some example embodiments, the monitoring system information block takes precedence over the configured window of the uplink transmission specific to the first device.
[0166] In some example embodiments, the size of the configured window is based on the duration for which the downlink channel is read by the first device, or the start time of the configured window is based on the last time a system information block was successfully read.
[0167] In some example embodiments, the number of monitoring opportunities in this set of monitoring opportunities is based on the overlap between the physical downlink control channel monitoring opportunities used for system information and the system information window.
[0168] In some example embodiments, the first apparatus further includes a component for prioritizing the monitoring of system information blocks over uplink transmission during a subset of monitoring opportunities or the set of monitoring opportunities, based on the determination that the number of monitoring opportunities in which system information blocks are scheduled is less than a threshold number.
[0169] In some example embodiments, the first apparatus further includes a component for performing uplink transmission based on determining that the number of monitoring opportunities in which the system information block is scheduled is less than a threshold number and that the monitoring opportunities for the system information are a subset of the monitoring opportunities or outside of the set of monitoring opportunities.
[0170] In some example embodiments, the first apparatus further includes a component for performing uplink transmission based on the fact that the number of monitoring opportunities for determining that the system information block is scheduled is equal to or greater than a threshold number and that the monitoring opportunities for the system information are outside a subset of the monitoring opportunities.
[0171] In some example embodiments, the first device further includes: for sending information to the second device, the information indicating the number of monitoring opportunities required for the monitoring system information block or the duration of the set of monitoring opportunities.
[0172] In some example embodiments, the first device further includes a component for sending an instruction to the second device regarding the receipt of a system information block.
[0173] In some example embodiments, the first device further includes: a component for performing uplink transmission based on determining that a system information block has been previously received; or a component for monitoring system information blocks based on determining that no system information has been previously received.
[0174] In some example embodiments, the first device further includes a component for sending an indication regarding the reception of the system information block based on determining that the system information block was received before a certain time.
[0175] In some example embodiments, the instruction is sent via signaling dedicated to the first device.
[0176] In some example embodiments, the first device is a terminal device, and the second device is a network device.
[0177] In some example embodiments, a first means capable of performing any of the methods in method 700 (e.g., Figure 1 The first device 110 may include a component for performing the corresponding operation of method 700. This component can be implemented in any suitable form. For example, the component can be implemented in a circuit or software module. The first device can be implemented as... Figure 1 The first device 110 or included in Figure 1 The first device 110 in the middle.
[0178] In some example embodiments, the first device includes: components for receiving a first configuration of a conflict resolution window from a second device; components for determining a prioritized link direction based on a first priority criterion for the conflict resolution window, based on determining that a link direction conflict exists in the conflict resolution window; and components for performing transmission or reception based on the prioritized link direction.
[0179] In some example embodiments, the prioritized link direction in the conflict resolution window is one of the following: a configured link direction from the second device, or a link direction with low priority based on a second priority criterion applied in the absence of a conflict resolution window.
[0180] In some example embodiments, the first device includes a component for changing a first priority criterion to a second priority criterion at the end of or after the end of a conflict resolution window.
[0181] In some example embodiments, the first device includes a component for performing link direction processing without changing the prioritization based on determining that there is no link direction conflict in the link direction conflict window.
[0182] In some example embodiments, the conflict resolution window is localized or distributed, or it is periodic or aperiodic, or it is semi-statically or dynamically configured.
[0183] In some example embodiments, the conflict handling window is used for at least one of the following: all channels or subsets of channels in the uplink, all channels or subsets of channels in the downlink, all signals or subsets of signals in the uplink, or all signals or subsets of signals in the downlink.
[0184] In some example embodiments, the first device is a terminal device, and the second device is a network device.
[0185] In some example embodiments, a second means capable of performing any of the methods in method 800 (e.g., Figure 1 The second device 120 may include a component for performing the corresponding operation of method 800. This component can be implemented in any suitable form. For example, the component can be implemented in a circuit or software module. The second device can be implemented as... Figure 1 The second device 120 is included in Figure 1 The second device 120 in the middle.
[0186] In some example embodiments, the second device includes: a component for sending a first configuration of a system information window to the first device, wherein the system information window includes a plurality of monitoring opportunities for scheduling downlink control information of system information blocks; and a component for sending an indication to the first device for scheduling an uplink transmission, the uplink transmission at least partially overlapping within the system information window with a monitoring opportunity for the downlink control information or a downlink transmission carrying the system information block, wherein whether monitoring the downlink control information or receiving the system information block takes precedence over the uplink transmission is based on at least one of the following: the position of the monitoring opportunity for the system information block in the system information window, the number of monitoring opportunities for scheduling the system information block, or whether the system information block has been previously received.
[0187] In some example implementations, within the system information window, a set of monitoring times from multiple monitoring times takes precedence over uplink transmissions.
[0188] In some example embodiments, the second device includes a component for sending a second configuration to the first device, the second configuration indicating the set of monitoring times among a plurality of monitoring times.
[0189] In some example embodiments, the second configuration indicates the number of monitoring times in the set of monitoring times, or the second configuration indicates a time window that includes the set of monitoring times relative to the start of the system information window.
[0190] In some example embodiments, this set of monitoring times corresponds to a configured window in which monitoring system information blocks take precedence over uplink transmissions.
[0191] In some example implementations, the configured windows for conflict handling are periodically distributed within the system information window.
[0192] In some example implementations, a set of downlink channels that take precedence over uplink channels are within a configured window, or all downlink channels that take precedence over uplink channels are within a configured window.
[0193] In some example embodiments, the configuration window for monitoring system information blocks takes precedence over uplink transmissions and is specific to the first device.
[0194] In some example embodiments, the size of the configured window is based on the duration for which the downlink channel is read by the first device, or the start time of the configured window is based on the last time a system information block was successfully read.
[0195] In some example embodiments, the number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the search space configuration and the system information window, or the number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the physical downlink control channel monitoring opportunities for system information and the system information window.
[0196] In some example embodiments, system information blocks are scheduled within a subset of the monitoring times of this set of monitoring times.
[0197] In some example embodiments, the second device includes a component for receiving information from the first device, the information indicating the number of monitoring opportunities required for a monitoring system information block or the duration of such a set of monitoring opportunities.
[0198] In some example embodiments, the second device includes a component for receiving an instruction from the first device regarding the reception of a system information block.
[0199] In some example embodiments, the instruction is sent via signaling dedicated to the first device.
[0200] In some example embodiments, a second means capable of performing any of the methods in method 900 (e.g., Figure 1The second device 120 may include components for performing the corresponding operations of method 1000. These components can be implemented in any suitable form. For example, the components can be implemented in a circuit or software module. The second device can be implemented as... Figure 1 The second device 120 is included in Figure 1 The second device 120 in the middle.
[0201] In some example embodiments, the second device includes a component for sending a first configuration of a conflict resolution window to the first device, wherein a first priority criterion is applied to the conflict resolution window.
[0202] In some example embodiments, the prioritized link direction in the conflict resolution window is one of the following: a link direction configured from the second device, or a link direction with low priority based on a second priority criterion applied in the absence of a conflict resolution window.
[0203] In some example embodiments, the first priority criterion is changed to the second priority criterion at the end of the conflict resolution window or after the end of the conflict resolution window.
[0204] In some example implementations, link direction processing is performed without changing the priority, based on the determination that there is no link direction conflict in the link direction conflict window.
[0205] In some example embodiments, the conflict resolution window is localized or distributed, or it is periodic or aperiodic, or it is semi-statically or dynamically configured.
[0206] In some example embodiments, the conflict handling window is used for at least one of the following: all channels or subsets of channels in the uplink, all channels or subsets of channels in the downlink, all signals or subsets of signals in the uplink, or all signals or subsets of signals in the downlink.
[0207] In some example embodiments, the first device is a terminal device, and the second device is a network device.
[0208] Figure 10 This is a simplified block diagram of a device 1000 suitable for implementing exemplary embodiments of the present disclosure. The device 1000 can be provided to implement a communication device, for example, as... Figure 1 The first device 110 or the second device 120 shown. As shown, device 1000 includes one or more processors 1010, one or more memories 1020 coupled to processor 1010, and one or more communication modules 1040 coupled to processor 1010.
[0209] Communication module 1040 is used for bidirectional communication. Communication module 1040 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interface can represent any interface required for communication with other network elements. In some example embodiments, communication module 1040 may include at least one antenna.
[0210] As a non-limiting example, processor 1010 can be any type suitable for a local technology network and can include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), and processor based on a multi-core processor architecture. Device 1000 can have multiple processors, such as application-specific integrated circuit chips that are time-dependent on a clock of a synchronous main processor.
[0211] Memory 1020 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 1024, electrically programmable read-only memory (EPROM), flash memory, hard disk, optical disc (CD), digital video disc (DVD), optical disc, laser disc, and other magnetic and / or optical storage. Examples of volatile memories include, but are not limited to, random access memory (RAM) 1022 and other volatile memories that cannot be retained during power outages.
[0212] Computer program 1030 includes computer-executable instructions that are executed by an associated processor 1010. The instructions of program 1030 may include instructions for performing operations / actions of some example embodiments of this disclosure. Program 1030 may be stored in memory (e.g., ROM 1024). Processor 1010 can perform any suitable actions and processes by loading program 1030 into RAM 1022.
[0213] The exemplary embodiments of this disclosure can be implemented by program 1030, enabling device 1000 to execute as described in the reference. Figures 2 to 9 Any process discussed in this disclosure. Exemplary embodiments of this disclosure may also be implemented by hardware or by a combination of software and hardware.
[0214] In some example embodiments, program 1030 may be tangibly contained in a computer-readable medium, which may be included in device 1000 (such as in memory 1020) or in other storage devices accessible by device 1000. Device 1000 may load program 1030 from the computer-readable medium into RAM 1022 for execution. In some example embodiments, the computer-readable medium may include any type of non-transitory storage medium, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. As used herein, the term "non-transitory" is a limitation on the medium itself (i.e., tangible, not tactile), rather than a limitation on the persistence of data storage (e.g., RAM and ROM).
[0215] Figure 11 An example of a computer-readable medium 1100 is shown, which may be in the form of a CD, DVD, or other optical storage disc. The computer-readable medium 1100 has a program 1030 stored thereon.
[0216] Generally, the various embodiments of this disclosure can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. Some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of this disclosure are illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, apparatuses, systems, techniques, or methods described herein can be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof.
[0217] Some exemplary embodiments of this disclosure also provide at least one computer program product tangibly stored on a computer-readable medium, such as a non-transitory computer-readable medium. The computer program product includes computer-executable instructions that execute in a device on a target physical or virtual processor, such as those included in a program module, to perform any of the methods described above. Typically, a program module includes routines, programs, libraries, objects, classes, components, data structures, etc., that perform a particular task or implement a particular abstract data type. In various embodiments, the functionality of a program module can be combined or split among program modules as needed. The machine-executable instructions for a program module can execute within a local or distributed device. In a distributed device, the program module can reside in both local and remote storage media.
[0218] Program code used to perform the methods of this disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus, such that when executed by the processor or controller, the program code causes the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may be executed entirely on a machine, partially on a machine, as a stand-alone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0219] In the context of this disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus, or processor to perform the various processes and operations described above. Examples of carriers include signals, computer-readable media, etc.
[0220] Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable media can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatuses, or devices, or any suitable combination thereof. More specific examples of computer-readable storage media will include electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable optical disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.
[0221] Furthermore, although operations are described in a specific order, this should not be construed as requiring that such operations be performed in the specific order shown or sequentially, or that all shown operations be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be construed as limiting the scope of this disclosure, but rather as a description of features that may be specific to particular embodiments. Unless explicitly stated otherwise, certain features described in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, unless explicitly stated otherwise, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments.
[0222] Although this disclosure has been described in language specific to structural features and / or methodological actions, it should be understood that the disclosure as defined in the appended claims is not necessarily limited to the specific features or actions described above. Rather, the specific features and actions described above are disclosed as examples of implementing the claims.
Claims
1. A first device, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first device to: The system information window is received from the second device as a first configuration, wherein the system information window includes multiple monitoring opportunities, and the multiple monitoring opportunities are used to schedule downlink control information of the system information block; The system receives an instruction from the second device to schedule an uplink transmission, the uplink transmission at least partially overlapping with a monitoring timing for the downlink control information or a downlink transmission carrying the system information block within the system information window. Whether to prioritize monitoring the downlink control information or receiving the system information block over the uplink transmission is determined based on at least one of the following: the position of the system information block monitoring timing in the system information window, the number of system information block monitoring timings scheduled, or whether the system information block has been received previously; as well as Based on the determination, monitor the system information block or execute the uplink transmission.
2. The first apparatus according to claim 1, wherein one set of monitoring times among the plurality of monitoring times takes precedence over the uplink transmission within the system information window.
3. The first apparatus according to claim 2, wherein the first apparatus is made to: Based on the location of the determined monitoring timing for the system information within the set of monitoring timings in the system information window, the system information block is monitored; or The uplink transmission is performed based on the location of the monitoring timing for the system information being outside the set of monitoring timings in the system information window.
4. The first apparatus according to claim 2, wherein the first apparatus is made to: Receives a second configuration from the second device, the second configuration indicating the set of monitoring times among the plurality of monitoring times.
5. The first apparatus according to claim 4, wherein the second configuration indicates the number of monitoring opportunities in the set of monitoring opportunities, or The second configuration indicates a time window relative to the start of the system information window and includes the set of monitoring opportunities.
6. The first apparatus according to claim 2, wherein the set of monitoring opportunities corresponds to a configured window, wherein monitoring the system information block takes precedence over uplink transmission within the configured window.
7. The first apparatus of claim 6, wherein the configured windows are periodically distributed within the system information window.
8. The first apparatus of claim 6, wherein a set of downlink channels, prior to the uplink channels, is within the configured window, or All downlink channels that take priority over the uplink channel are within the configured window.
9. The first apparatus of claim 2, wherein a configured window for monitoring the system information block takes precedence over uplink transmission is specific to the first apparatus.
10. The first apparatus according to any one of claims 6-9, wherein the size of the configured window is based on the duration for which the first apparatus reads the downlink channel, or The start time of the configured window is based on the last time the system information block was successfully read.
11. The first apparatus according to claim 2, wherein the number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the search space configuration and the system information window, or The number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the physical downlink control channel monitoring opportunities used for system information and the system information window.
12. The first apparatus according to claim 2, wherein the first apparatus is made to: Based on the determination that the number of monitoring opportunities in which the system information block is scheduled is less than a threshold number, monitoring the system information block is prioritized over the uplink transmission during a subset of monitoring opportunities or a set of monitoring opportunities.
13. The first device according to claim 2, wherein the first device is made to: The uplink transmission is performed based on the fact that the number of monitoring opportunities for which the system information block is scheduled is less than a threshold number and the monitoring opportunity for the system information is outside a subset of monitoring opportunities or the set of monitoring opportunities.
14. The first device according to claim 2, wherein the first device is made to: The uplink transmission is performed based on the fact that the number of monitoring opportunities for which the system information block is scheduled is equal to or greater than a threshold number and the monitoring opportunities for the system information are outside a subset of the monitoring opportunities.
15. The first device according to any one of claims 2-14, wherein the first device is made to: The second device is sent information indicating the number of monitoring opportunities required to monitor the system information block or the duration of the set of monitoring opportunities.
16. The first apparatus according to claim 1, wherein the first apparatus is made to: Send an instruction to the second device regarding the receipt of the system information block.
17. The first device according to claim 1 or 16, wherein the first device is made to: Based on the previously received system information block, the uplink transmission is performed; or Based on the determination that the system information block has not been previously received, the system information block is monitored.
18. The first device according to claim 16, wherein the first device is made to: Based on the determination that the system information block was received before a certain time, the indication is sent regarding the reception of the system information block.
19. The first device according to any one of claims 16-18, wherein the instruction is transmitted via signaling dedicated to the first device.
20. The first device according to any one of claims 1-20, wherein the first device is a terminal device and the second device is a network device.
21. A first device, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the first device to: Receive the first configuration of the conflict handling window from the second device; Based on the determination that a link direction conflict exists within the conflict resolution window, the prioritized link direction is determined based on a first priority criterion for the conflict resolution window. Transmission or reception is performed based on the prioritized link direction.
22. The first apparatus of claim 21, wherein the prioritized link direction in the conflict resolution window is one of the following: The configured link direction from the second device, or The link direction with low priority is based on the second priority criterion applied in the absence of the conflict resolution window.
23. The first device according to claim 21 or 22, wherein the first device is made to: At the end of the conflict resolution window or after the end of the conflict resolution window, the first priority criterion is changed to the second priority criterion.
24. The first device according to claim 21 or 22, wherein the first device is made to: Based on the determination that there is no link direction conflict in the conflict window, link direction processing is performed without changing the priority.
25. The first apparatus according to claim 21 or 22, wherein the conflict handling window is localized or distributed, or The conflict handling window is either periodic or non-periodic, or The conflict handling window is either semi-statically or dynamically configured.
26. The first apparatus according to claim 20 or 21, wherein the conflict resolution window is used for at least one of the following: All channels or subsets of channels in the uplink. All channels or subsets of channels in the downlink. All signals or subsets of signals in the uplink, or All signals or subsets of signals in the downlink.
27. The first device according to any one of claims 21-26, wherein the first device is a terminal device and the second device is a network device.
28. A second device, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the second device to: Send a first configuration of a system information window to a first device, wherein the system information window includes multiple monitoring opportunities, the multiple monitoring opportunities being used to schedule downlink control information of system information blocks; as well as An instruction for scheduling uplink transmissions is sent to the first device, wherein the uplink transmissions at least partially overlap with the monitoring timing for the downlink control information or the downlink transmission carrying the system information block within the system information window, wherein whether monitoring the downlink control information or receiving the system information block takes precedence over the uplink transmission is based on at least one of the following: the position of the monitoring timing for the system information block in the system information window, the number of monitoring timings for scheduling the system information block, or whether the system information block has been previously received.
29. The second apparatus of claim 28, wherein a set of monitoring times among the plurality of monitoring times takes precedence over the uplink transmission within the system information window.
30. The second device according to claim 29, wherein the second device is made to: A second configuration is sent to the first device, the second device indicating the set of monitoring times among the plurality of monitoring times.
31. The second apparatus of claim 30, wherein the second configuration indicates the number of monitoring opportunities in the set of monitoring opportunities, or The second configuration indicates a time window relative to the start of the system information window and includes the set of monitoring opportunities.
32. The second apparatus of claim 29, wherein the set of monitoring opportunities corresponds to a configured window in which monitoring of the system information block takes precedence over uplink transmission.
33. The second apparatus according to claim 32, wherein, The configured windows are periodically distributed within the system information window.
34. The second apparatus of claim 32, wherein a set of downlink channels, prior to the uplink channels, is within the configured window, or All downlink channels that take priority over the uplink channel are within the configured window.
35. The second apparatus of claim 29, wherein the window in which the configuration of monitoring the system information block takes precedence over uplink transmission is specific to the first apparatus.
36. The second apparatus according to any one of claims 32-34, wherein the size of the configured window is based on the duration for which the first apparatus reads the downlink channel, or The start time of the configured window is based on the last time the system information block was successfully read.
37. The second apparatus of claim 29, wherein the number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the search space configuration and the system information window, or The number of monitoring opportunities in the set of monitoring opportunities is based on the overlap between the physical downlink control channel monitoring opportunities used for system information and the system information window.
38. The second apparatus according to claim 29, wherein the system information block is scheduled in a subset of the monitoring times in the set of monitoring times.
39. The second device according to any one of claims 29-38, wherein the second device is made to: Information is received from the first device indicating the number of monitoring opportunities required to monitor the system information block or the duration of a set of monitoring opportunities.
40. The second device according to claim 28, wherein the second device is made to: Receive an instruction from the first device regarding the receipt of the system information block.
41. The second device according to claim 40, wherein the instruction is transmitted via signaling dedicated to the first device.
42. A second device, comprising: At least one processor; as well as At least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the second device to: A first configuration of a conflict resolution window is sent to a first device, wherein a first priority criterion is applied to the conflict resolution window.
43. The second apparatus of claim 42, wherein the prioritized link direction in the conflict resolution window is one of the following: The configured link direction from the second device, or The link direction with low priority is based on the second priority criterion applied in the absence of the conflict resolution window.
44. The second apparatus according to claim 42 or 43, wherein at the end of the conflict resolution window or after the end of the conflict resolution window, the first priority criterion is changed to the second priority criterion.
45. The second apparatus according to claim 42 or 43, wherein link direction processing is performed without changing the priority based on determining that there is no link direction conflict in the conflict window.
46. The second apparatus according to claim 42 or 43, wherein the conflict handling window is localized or distributed, or The conflict handling window is either periodic or non-periodic, or The conflict handling window is either semi-statically or dynamically configured.
47. The second apparatus according to claim 42 or 43, wherein the conflict resolution window is used for at least one of the following: All channels or subsets of channels in the uplink. All channels or subsets of channels in the downlink. All signals or subsets of signals in the uplink, or All signals or subsets of signals in the downlink.
48. The second device according to any one of claims 42-48, wherein the first device is a terminal device and the second device is a network device.
49. A method comprising: The system information window is first configured to be received from the second device at the first device, wherein the system information window includes multiple monitoring opportunities for scheduling downlink control information of system information blocks; The system receives an instruction from the second device to schedule an uplink transmission, the uplink transmission at least partially overlapping with a monitoring timing for the downlink control information or a downlink transmission carrying the system information block within the system information window. Whether to prioritize monitoring the downlink control information or receiving the system information block over the uplink transmission is determined based on at least one of the following: the position of the system information block monitoring timing in the system information window, the number of system information block monitoring timings scheduled, or whether the system information block has been received previously; Based on the determination, monitor the system information block or execute the uplink transmission.
50. A method comprising: Receive the first configuration of the conflict handling window from the second device at the first device; Based on the determination that a link direction conflict exists in the conflict resolution window, the priority link direction is determined based on a first priority criterion for the conflict resolution window. Transmission or reception is performed based on the prioritized link direction.
51. A method comprising: The first configuration of the system information window is sent from the second device to the first device, wherein the system information window includes multiple monitoring opportunities, and the multiple monitoring opportunities are used to schedule downlink control information of the system information block; An instruction for scheduling uplink transmissions is sent to the first device, wherein the uplink transmissions at least partially overlap with the monitoring timing for the downlink control information or the downlink transmission carrying the system information block within the system information window, wherein whether monitoring the downlink control information or receiving the system information block takes precedence over the uplink transmission is based on at least one of the following: the position of the monitoring timing for the system information block in the system information window, the number of monitoring timings for scheduling the system information block, or whether the system information block has been previously received.
52. A method comprising: A first configuration of a conflict resolution window is sent from the second device to the first device, wherein a first priority criterion is applied to the conflict resolution window.
53. A first device, comprising: A component for receiving a first configuration of a system information window from a second device, wherein the system information window includes multiple monitoring opportunities for scheduling downlink control information of system information blocks; A component for receiving from the second device an instruction for scheduling uplink transmissions, wherein the uplink transmissions at least partially overlap with the monitoring timing for the downlink control information or a downlink transmission carrying the system information block within the system information window; A component for determining whether to prioritize monitoring the downlink control information or receiving at least one of the system information blocks over the uplink transmission based on at least one of the following: the position of the system information block monitoring timing in the system information window, the number of system information block monitoring timings scheduled, or whether the system information block has been previously received; as well as A component used to monitor the system information block or perform the uplink transmission based on the determination.
54. A first device, comprising: Components for receiving the first configuration of the conflict handling window from the second device; A component for determining a prioritized link direction based on a first priority criterion for the conflict resolution window, based on the determination that a link direction conflict exists in the conflict resolution window; as well as A component for performing transmission or reception based on the prioritized link direction.
55. A second device, comprising: A component for sending a first configuration of a system information window to a first device, wherein the system information window includes multiple monitoring opportunities, the multiple monitoring opportunities being used to schedule downlink control information of system information blocks; as well as A component for sending an instruction to the first device for scheduling an uplink transmission, wherein the uplink transmission at least partially overlaps with a monitoring timing for the downlink control information or a downlink transmission carrying the system information block within the system information window, wherein whether monitoring the downlink control information or receiving the system information block takes precedence over the uplink transmission is based on at least one of the following: the position of the monitoring timing for the system information block in the system information window, the number of monitoring timings for scheduling the system information block, or whether the system information block has been previously received.
56. A second device, comprising: A component for sending a first configuration of a conflict resolution window to a first device, wherein a first priority criterion applies to the conflict resolution window.
57. A computer-readable medium comprising instructions stored thereon for causing a device to perform at least the method of any one of claims 49-52.
