WO2025208577A1 - Mécanisme de surveillance d'informations de système - Google Patents

Mécanisme de surveillance d'informations de système

Info

Publication number
WO2025208577A1
WO2025208577A1 PCT/CN2024/086183 CN2024086183W WO2025208577A1 WO 2025208577 A1 WO2025208577 A1 WO 2025208577A1 CN 2024086183 W CN2024086183 W CN 2024086183W WO 2025208577 A1 WO2025208577 A1 WO 2025208577A1
Authority
WO
WIPO (PCT)
Prior art keywords
system information
window
monitoring
information block
monitoring occasions
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/086183
Other languages
English (en)
Inventor
Mads LAURIDSEN
Frank Frederiksen
Jingyuan Sun
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and Networks Oy
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co Ltd, Nokia Solutions and Networks Oy, Nokia Technologies Oy filed Critical Nokia Shanghai Bell Co Ltd
Priority to PCT/CN2024/086183 priority Critical patent/WO2025208577A1/fr
Publication of WO2025208577A1 publication Critical patent/WO2025208577A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signalling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signalling for the administration of the divided path, e.g. signalling of configuration information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/14—Two-way operation using the same type of signal, i.e. duplex
    • H04L5/16—Half-duplex systems; Simplex/duplex switching; Transmission of break signals non-automatically inverting the direction of transmission
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0026—Division using four or more dimensions, e.g. beam steering or quasi-co-location [QCL]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0032—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation
    • H04L5/0033—Distributed allocation, i.e. involving a plurality of allocating devices, each making partial allocation each allocating device acting autonomously, i.e. without negotiation with other allocating devices

Definitions

  • Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to methods, devices, apparatuses and computer readable storage medium for monitoring system information.
  • a first apparatus comprises 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, from a second apparatus, a first configuration of a system information window, wherein the system information window comprises a plurality of monitoring occasions for downlink control information scheduling a system information block; receive, from the second apparatus, an indication for scheduling an uplink transmission that at least partially overlaps with a monitoring occasion for the downlink control information or a downlink transmission carrying the system information block within the system information window; determine whether to prioritize at least one of: monitoring the downlink control information or a reception of the system information block over the uplink transmission based on at least one of: a position of a monitoring occasion for the system information block in the system information window, a number of monitoring occasions where the system information block was scheduled, or whether the system information block is received previously; and monitor the system information block or perform the uplink transmission based on the determining.
  • a first apparatus comprises 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, from a second apparatus, a first configuration of a collision handling window; based on a determination that there is link direction collision in the collision handling window, determine a prioritized link direction based on a first prioritization criterion for the collision handling window, perform a transmission or a reception based on the prioritized link direction.
  • a second apparatus comprises 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: transmit, to a first apparatus, a first configuration of a collision handling window, wherein a first prioritization criterion is for the collision handling window.
  • a method comprises: receiving, from a second apparatus, a first configuration of a collision handling window; based on a determination that there is link direction collision in the collision handling window, determining a prioritized link direction based on a first prioritization criterion for the collision handling window, performing a transmission or a reception based on the prioritized link direction.
  • FIG. 3A and FIG. 3B illustrate schematic diagrams of system information window in accordance with some example embodiments of the present disclosure, respectively;
  • FIG. 5 illustrates a schematic diagram of collision handling window in accordance with some example embodiments of the present disclosure, respectively;
  • FIG. 7 illustrates a flowchart of a method implemented at a first apparatus in accordance with some example embodiments of the present disclosure
  • FIG. 8 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure
  • FIG. 9 illustrates a flowchart of a method implemented at a second apparatus in accordance with some example embodiments of the present disclosure
  • FIG. 10 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure.
  • circuitry may refer to one or more or all of the following:
  • circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and/or firmware.
  • circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.
  • the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols, including, but not limited to, the first generation (1G) , the second generation (2G) , 2.5G, 2.75G, the third generation (3G) , the fourth generation (4G) , 4.5G, the fifth generation (5G) , 5.5G, the sixth generation (6G) communication protocols, and/or any other protocols either currently known or to be developed in the future.
  • Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.
  • the term “network device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom.
  • the network device may refer to a base station (BS) or an access point (AP) , for example, a node B (NodeB or NB) , an evolved NodeB (eNodeB or eNB) , an NR NB (also referred to as a gNB) , a Remote Radio Unit (RRU) , a radio header (RH) , a remote radio head (RRH) , a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology
  • An example solution would be to change the rule such that SIB19 is prioritized, but the challenge is that the network is not aware when the UE is attempting to acquire the SIB19.
  • the expected network configuration for a network would be that the gNB would provide the SIB19 with a much shorter periodicity compared to the validity duration.
  • the re-acquisition of SIB19 is based on the validity duration, which is conveyed in the information element NTN-Config.
  • SIB19 If a network configures for SIB19 to be provided roughly every 1 second, while the validity duration is 10 seconds the UE has the opportunity to monitor every second, but would in principle only need to actually read the SIB19 every 10 seconds (or even 20 seconds in case the gNB provides ephemeris information pointing into the future under the condition that the UE supports “backwards propagation” ) . However, the network will not know during which of the SIB scheduling windows during a validity duration the UE will actually read the SIB19.
  • SI windows may be served, which means the current collision rule would not apply within the window and instead the UE can prioritize the reception of the SIB19.
  • the solution does not consider when the individual UE previously acquired the SIB19 and therefore it may be inconvenient to some UEs that their preferred SIB19 SI window is far from a reserved window, which results in the UE receiving the SIB19 “too early” relative to a potential validity timer expiry.
  • a SI window (being up to 1280 slots long) may include many PDCCH monitoring occasions (depending on the search space configuration) of which the UE only would need one or a few to acquire the SIB19. It is therefore suboptimal to block all PDCCH monitoring occasions in a SI window.
  • FIG. 2 illustrates signaling flow 200 of distributed feedback in accordance with some example embodiments of the present disclosure.
  • the signaling flow 200 is described with reference to the first device 110 and the second device 120 shown in FIG. 1.
  • the system information window includes a plurality of monitoring occasions for downlink control information (DCI) scheduling a SIB.
  • the system information window 310 may include monitoring occasions 320-1, 320-2, 320-3, 320-4, 320-5, 320-6, 320-7 and 320-8.
  • the DCI scheduling the SIB may be transmitted/received on one or more of these monitoring occasions.
  • Table 2 shows an example of information element (IE) search space. It is noted that Table 2 is only an example not limitation.
  • IE information element
  • Table 2 is only an example not limitation.
  • the PDCCH monitoring is defined with a periodicity in slots, a duration in slots and then number of symbols to monitor PDCCH per slot of the duration. Thus, there can be one or more PDCCH monitoring occasions for the DCI scheduling the SIB.
  • the second device 120 may transmit (2015) a second configuration indicating a set of monitoring occasions in the plurality of monitoring occasions to the first device 110.
  • the first device 110 may receive (2015) the second configuration from the second device 120.
  • the second configuration may indicate a time window including the set of monitoring occasions relative to a start of the system information window.
  • the time window 330’ may include the monitoring occasions 320-1, 320-2, 320-3 and 320-4.
  • the second configuration may indicate the time window 330’ relative to the start 340 of the system information window 310.
  • the configured window may be specific to the first device 110.
  • a size of the configured window may be based on a time duration for reading a downlink channel by the first device 110.
  • the size of the window may be based on UE reported/requested time to read the DL channel, e.g. PDCCH including PDSCH when scheduling SIB19.
  • the second device 120 transmits (2020) an indication for scheduling an uplink transmission that at least partially overlaps with a monitoring occasion for the downlink control information or a downlink transmission carrying the system information block within the system information window to the first device 110.
  • the first device 110 receives the indication for scheduling the uplink transmission that at least partially overlaps with a monitoring occasion for the downlink control information or a downlink transmission carrying the system information block within the system information window from the second device 120.
  • the first device 110 determines (2030) whether to prioritize at least one of: monitoring the DCI or a reception of the SIB over the uplink transmission based on one or more off a position of a monitoring occasion for the system information block in the system information window, a number of monitoring occasions where the system information block was scheduled, or whether the system information block is received previously.
  • the first device 110 may monitor (2040) the SIB based on the determining.
  • monitoring (2040) the SIB may include monitoring the DCI scheduling the SIB.
  • monitoring (2040) the SIB may include receiving the SIB.
  • the first device 110 may transmit (2040’) the uplink transmission based on the determining. In this way, the UE can receive the SIB timely and avoid unnecessary latency for uplink transmission. Example embodiments are described below in details.
  • the first device 110 may prioritize at least one of: monitoring the DCI or the reception of the SIB over the uplink transmission. That is, if the position of the monitoring occasion for the system information is in the set of monitoring occasions in the system information window, the first device 110 may perform the monitoring of the DCI or the reception of the SIB. For example, ifa next monitoring occasion is part of X1 (X1 is an integer number) first monitoring occasions in the system information window, the first device 110 may prioritize downlink reception, if the downlink reception is scheduled. For example, as shown in FIG.
  • the first device 110 may prioritize downlink reception, if the downlink reception is scheduled. For example, as shown in FIG. 3B, if the position of the monitoring occasion for the system information block is in the time duration 330’, the first device 110 may monitor the system information block.
  • the first device 110 may prioritize the uplink transmission over the monitoring of the DCI and/or the reception of the SIB. That is, if the position monitoring occasion for the system information is not in the set of monitoring occasions in the system information window, the first device 110 may perform the uplink transmission. For example, if a next monitoring occasion is not part of X1 first monitoring occasions in the system information window, the first device 110 may prioritize uplink transmission, if the uplink transmission is scheduled. For example, as shown in FIG.
  • the first device 110 may prioritize monitoring the system information block over the uplink transmission during the subset of monitoring occasions or the set of monitoring occasions.
  • the second device 120 may shift the time to apply the reverted collision rule to allow the set of monitoring occasions that actually result in SIB19 scheduling, which means that the rule is reverted later than the first X monitoring occasions.
  • the collision rule may be reverted when either X or Z is achieved. For example, as shown in FIG. 3B, ifX is 5 and Z is 3 and the second device 120 schedules the system information block in monitoring occasions 320-1, 320-2 and 320-6, the second device may revert the rule after 5 monitoring occasions.
  • the first device 110 may perform the uplink transmission. For example, as shown in FIG. 3B, if the number of monitoring occasions where the system information block was scheduled is equal to or larger than the threshold number and the monitoring occasion for the system information is out the subset 350’ of monitoring occasions, the first device 110 may perform the uplink transmission.
  • the first device 110 may notify the second device 120 when it has received the SIB19 if the reception happens before the collision rule is reverted. The notification may then cause the rule to be reverted (i.e. uplink is prioritized) .
  • the first device 110 may transmit, to the second device, an indication regarding the reception of the system information block.
  • the first device 110 may transmit, to the second device, an indication regarding the reception of the system information block.
  • the first device 110 may transmit, to the second device, an indication regarding the reception of the system information block.
  • the first device 110 may prioritize the uplink transmission over the monitoring of the DCI scheduling the SIB and/or the reception of the SIB. For example, if the system information block is received in the system information window or if the system information block is received in another system information window which is in 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 not change. For example, as shown in FIG. 3A, if the system information block was received in the system information window 310, the first device 110 may prioritize the uplink transmission. Alternatively, if the system information block was received is another system information window (not shown) which is in the same system information modification window as the system information window 310, the first device 110 may prioritize the uplink transmission.
  • the indication is transmitted via a signaling dedicated to the first apparatus.
  • the first device 110 may provide the notification through a UE dedicated signaling channel which is pre-configured for the UE, which means that the first device 110 knows the exact time and resource to provide the indication.
  • the availability of the configured resource may also be conditional on the parameters Z and X.
  • One channel that could be used to provide the signaling would be the PRACH, where a dedicated random-access preamble could be used for such indication.
  • the first device 110 determines (4020) a prioritized link direction based on a first prioritization criterion, if there is a link direction collision in the collision handling window.
  • the first device 110 may perform (4030) a transmission based on the prioritized link direction.
  • the first device 110 may perform (4030’) a reception based on the prioritized link direction.
  • which link direction is prioritized in the configured window for collision handling may be determined by a network configuration. That is, the first prioritization criterion may be configured by the second device 120. Alternatively, the first prioritization criterion may be predefined.
  • the first device 110 may change the first prioritization criterion to the second prioritization criterion, at or after an end of collision handling window. For example, as shown in FIG. 5, the first device 110 may change the first prioritization criterion to the second prioritization criterion, at or after an end 540 of collision handling window.
  • the first prioritization criterion indicates that a DL direction is prioritized and the second prioritization criterion indicates that an UL direction is prioritized
  • the first device 110 may perform the UL reception over DL transmission in the monitoring occasion 520-6.
  • the method 600 further comprises: based on a determination that the position of the monitoring occasion for the system information is in the set of monitoring occasions in the system information window, monitoring the system information block; or based on a determination that the position of the monitoring occasion for the system information is out of the set of monitoring occasions in the system information window, performing the uplink transmission.
  • the set of monitoring occasions corresponds to a configured window in which monitoring the system information block is prioritized over uplink transmission.
  • a size of the configured window is based on a time duration for reading a downlink channel by the first apparatus, or wherein a start time of the configured window is based on a last time of reading the system information block successfully.
  • the number of monitoring occasions in the set of monitoring occasions is based on an overlapped part between physical downlink control channel monitoring occasions for the system information and the system information window.
  • the method 600 further comprises: based on a determination that the number of monitoring occasions s where the system information block was scheduled is equal to or larger than a threshold number and the monitoring occasion for the system information is out a subset of monitoring occasions, performing the uplink transmission.
  • the method 600 further comprises: based on a determination that the system information block is received previously, performing the uplink transmission; or based on a determination that the system information is not received previously, monitoring the system information block.
  • the indication is transmitted via a signaling dedicated to the first apparatus.
  • the first apparatus is a terminal device
  • the second apparatus is a network device.
  • FIG. 7 shows a flowchart of an example method 700 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 700 will be described from the perspective of the first device 110 in FIG. 1.
  • the first device performs a transmission or a reception based on the prioritized link direction.
  • the prioritized link direction in the collision handling window is one of the following: a configured link direction from the second apparatus, or a link direction with low priority based on a second prioritization criterion which is applied in an absence of the collision handling window.
  • the first apparatus is caused to: changing the first prioritization criterion to the second prioritization criterion, at or after an end of collision handling window.
  • the first apparatus is caused to: based on a determination that there is no link direction collision in the link direction collision window, performing a link direction processing without changing prioritization.
  • the collision handling window is localized or distributed, or wherein the collision handling window is periodic or aperiodic, or wherein the collision handling window is semi-static configured or dynamic configured.
  • the collision handling window is used for at least one of: all channels or a subset of channels in uplink, all channels or a subset of channels in downlink, all signals or a subset of signals in uplink, or all signals or a subset of signals in downlink.
  • the first apparatus is a terminal device
  • the second apparatus is a network device.
  • FIG. 8 shows a flowchart of an example method 800 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 800 will be described from the perspective of the second device 120 in FIG. 1.
  • the second apparatus transmits, to a first apparatus, a first configuration of a system information window.
  • the system information window comprises a plurality of monitoring occasions for downlink control information scheduling a system information block.
  • the second apparatus transmits, to the first apparatus, an indication for scheduling an uplink transmission that at least partially overlaps with a monitoring occasion for the downlink control information or a downlink transmission carrying the system information block within the system information window, wherein whether to prioritize at least one of: monitoring the downlink control information or a reception of the system information block over the uplink transmission is based on at least one of: a position of a monitoring occasion for the system information block in the system information window, a number of monitoring occasions where the system information block was scheduled, or whether the system information block is received previously.
  • a set of monitoring occasions in the plurality of monitoring occasions is prioritized over the uplink transmission within the system information window.
  • the second apparatus is caused to: transmitting, to the first apparatus, a second configuration indicating the set of monitoring occasions in the plurality of monitoring occasions.
  • the second configuration indicates the number of monitoring occasions in the set of monitoring occasions, or wherein the second configuration indicates a time window including the set of monitoring occasions relative to a start of the system information window.
  • the set of monitoring occasions corresponds to a configured window for collision handling in which monitoring the system information block is prioritized than uplink transmission.
  • a set of downlink channels prioritized over uplink channels is within the configured window, or wherein all downlink channels prioritized over the uplink channels are within the configured window.
  • a size of the configured window is based on a time duration for reading a downlink channel by the first apparatus, or wherein a start time of the configured window is based on a last time of reading the system information block successfully.
  • the number of monitoring occasions in the set of monitoring occasions is based on an overlapped part of search space configuration and the system information window, or wherein the number of monitoring occasions in the set of monitoring occasions is based on an overlapped part between physical downlink control channel monitoring occasions for the system information and the system information window.
  • the system information block is scheduled in a subset of monitoring occasions of the set of monitoring occasions.
  • the second apparatus is caused to: receiving, from the first apparatus, an indication regarding the reception of the system information block.
  • FIG. 9 shows a flowchart of an example method 900 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the second device 120 in FIG. 1.
  • the second apparatus transmits, to a first apparatus, a first configuration of a collision handling window, wherein a first prioritization criterion is for the collision handling window.
  • the second apparatus may perform a transmission or a reception.
  • a prioritized link direction in the collision handling window is one of the following: a configured link direction from the second apparatus, or a link direction with low priority based on a second prioritization criterion which is applied in an absence of the collision handling window.
  • the first prioritization criterion is changed to the second prioritization criterion, at or after an end of collision handling window.
  • a link direction processing is performed without changing prioritization.
  • the collision handling window is localized or distributed, or wherein the collision handling window is periodic or aperiodic, or wherein the collision handling window is semi-static configured or dynamic configured.
  • the collision handling window is used for at least one of: all channels or a subset of channels in uplink, all channels or a subset of channels in downlink, all signals or a subset of signals in uplink, or all signals or a subset of signals in downlink.
  • the first apparatus is a terminal device
  • the second apparatus is a network device.
  • a first apparatus capable of performing any of the method 600 may comprise means for performing the respective operations of the method 600.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the first apparatus may be implemented as or included in the first device 110 in FIG. 1.
  • the first apparatus comprises means for receiving, from a second apparatus, a first configuration of a system information window, wherein the system information window comprises a plurality of monitoring occasions for downlink control information scheduling a system information block; means for receiving, from the second apparatus, an indication for scheduling an uplink transmission that at least partially overlaps with a monitoring occasion for the downlink control information or a downlink transmission carrying the system information block within the system information window; means for determining whether to prioritize at least one of: monitoring the downlink control information or a reception of the system information block over the uplink transmission based on at least one of: a position of a monitoring occasion for the system information block in the system information window, a number of monitoring occasions where the system information block was scheduled, or whether the system information block is received previously; and means for monitoring the system information block or perform the uplink transmission based on the determining.
  • a set of monitoring occasions in the plurality of monitoring occasions is prioritized over the uplink transmission within the system information window.
  • the first apparatus further comprises: means for receiving, from the second apparatus, a second configuration indicating the set of monitoring occasions in the plurality of monitoring occasions.
  • the second configuration indicates the number of monitoring occasions in the set of monitoring occasions, or wherein the second configuration indicates a time window including the set of monitoring occasions relative to a start of the system information window.
  • the set of monitoring occasions corresponds to a configured window in which monitoring the system information block is prioritized over uplink transmission.
  • a set of downlink channels prioritized over uplink channels is within the configured window, or wherein all downlink channels prioritized over the uplink channels are within the configured window.
  • a configured window in which monitoring the system information block is prioritized over uplink transmission is specific to the first apparatus.
  • a size of the configured window is based on a time duration for reading a downlink channel by the first apparatus, or wherein a start time of the configured window is based on a last time of reading the system information block successfully.
  • the number of monitoring occasions in the set of monitoring occasions is based on an overlapped part between physical downlink control channel monitoring occasions for the system information and the system information window.
  • the first apparatus further comprises: means for based on a determination that the number of monitoring occasions where the system information block was scheduled is less than a threshold number and the monitoring occasion for the system information is out of a subset of monitoring occasions or the set of monitoring occasions, performing the uplink transmission.
  • the first apparatus further comprises: means for based on a determination that the number of monitoring occasions where the system information block was scheduled is equal to or larger than a threshold number and the monitoring occasion for the system information is out a subset of monitoring occasions, performing the uplink transmission.
  • the first apparatus further comprises: means for transmitting, to the second apparatus, an indication regarding the reception of the system information block.
  • the first apparatus further comprises: means for based on a determination that the system information block is received previously, performing the uplink transmission; or means for based on a determination that the system information is not received previously, monitoring the system information block.
  • the first apparatus further comprises: means for based on a determination that the system information block is received before a time instant, transmitting the indication regarding the reception of the system information block.
  • the indication is transmitted via a signaling dedicated to the first apparatus.
  • the first apparatus is a terminal device
  • the second apparatus is a network device.
  • a first apparatus capable of performing any of the method 700 may comprise means for performing the respective operations of the method 700.
  • the means may be implemented in any suitable form.
  • the means may be implemented in a circuitry or software module.
  • the first apparatus may be implemented as or included in the first device 110 in FIG. 1.
  • the first apparatus comprises means for receiving, from a second apparatus, a first configuration of a collision handling window; means for based on a determination that there is link direction collision in the collision handling window, determining a prioritized link direction based on a first prioritization criterion for the collision handling window, means for performing a transmission or a reception based on the prioritized link direction.
  • a set of downlink channels prioritized over uplink channels is within the configured window, or wherein all downlink channels prioritized over the uplink channels are within the configured window.
  • the collision handling window is used for at least one of: all channels or a subset of channels in uplink, all channels or a subset of channels in downlink, all signals or a subset of signals in uplink, or all signals or a subs et of signals in downlink.
  • the program 1030 may be tangibly contained in a computer readable medium which may be included in the device 1000 (such as in the memory 1020) or other storage devices that are accessible by the device 1000.
  • the device 1000 may load the program 1030 from the computer readable medium to the RAM 1022 for execution.
  • the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like.
  • the term “non-transitory, ” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM) .
  • Program code for carrying out methods of the present 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 the program code, when executed by the processor or controller, cause the functions/operations specified in the flowcharts and/or block diagrams to be implemented.
  • the program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
  • the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above.
  • Examples of the carrier include a signal, computer readable medium, and the like.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM) , a read-only memory (ROM) , an erasable programmable read-only memory (EPROM or Flash memory) , an optical fiber, a portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Des exemples de modes de réalisation de la présente divulgation concernent la surveillance d'informations de système. Un procédé consiste à recevoir, en provenance d'un second appareil, une première configuration d'une fenêtre d'informations de système, la fenêtre d'informations de système comprenant une pluralité d'occasions de surveillance pour un bloc d'informations de système ; recevoir, en provenance du second appareil, une indication pour planifier une transmission en liaison montante qui se trouve à l'intérieur de la fenêtre d'informations de système ; déterminer s'il faut hiérarchiser une réception du bloc d'informations de système ou la transmission en liaison montante sur la base d'au moins l'un parmi : une position d'une occasion de surveillance pour le bloc d'informations de système dans la fenêtre d'informations de système, un nombre d'occasions de surveillance pendant lesquelles le bloc d'informations de système a été planifié, ou si le bloc d'informations de système est reçu précédemment ; et surveiller le bloc d'informations de système ou effectuer la transmission en liaison montante sur la base de la détermination.
PCT/CN2024/086183 2024-04-04 2024-04-04 Mécanisme de surveillance d'informations de système Pending WO2025208577A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/086183 WO2025208577A1 (fr) 2024-04-04 2024-04-04 Mécanisme de surveillance d'informations de système

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/086183 WO2025208577A1 (fr) 2024-04-04 2024-04-04 Mécanisme de surveillance d'informations de système

Publications (1)

Publication Number Publication Date
WO2025208577A1 true WO2025208577A1 (fr) 2025-10-09

Family

ID=97266064

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/086183 Pending WO2025208577A1 (fr) 2024-04-04 2024-04-04 Mécanisme de surveillance d'informations de système

Country Status (1)

Country Link
WO (1) WO2025208577A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111133708A (zh) * 2017-09-22 2020-05-08 诺基亚技术有限公司 使能在无线网络中基于数据传输的抢占来在下行链路子帧期间进行上行链路传输
US20220264464A1 (en) * 2019-07-26 2022-08-18 Lg Electronics Inc. Method for monitoring control channel, and device using method
US20230344580A1 (en) * 2022-04-22 2023-10-26 Ofinno, Llc Flexible Downlink Control Channel Monitoring for Downlink Repetitions

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111133708A (zh) * 2017-09-22 2020-05-08 诺基亚技术有限公司 使能在无线网络中基于数据传输的抢占来在下行链路子帧期间进行上行链路传输
US20220264464A1 (en) * 2019-07-26 2022-08-18 Lg Electronics Inc. Method for monitoring control channel, and device using method
US20230344580A1 (en) * 2022-04-22 2023-10-26 Ofinno, Llc Flexible Downlink Control Channel Monitoring for Downlink Repetitions

Similar Documents

Publication Publication Date Title
WO2023108516A1 (fr) Schéma de retransmisison aveugle améliorée
WO2020220375A1 (fr) Résolution de conflit pendant une procédure d'accès aléatoire
WO2025208577A1 (fr) Mécanisme de surveillance d'informations de système
WO2023065249A1 (fr) Accès aléatoire à une cellule secondaire
US20240259823A1 (en) Sidelink transmission enhancement
US20250300793A1 (en) Transmission configuration indicator state update
WO2025160922A1 (fr) Configuration de modes de fonctionnement pour duplex intégral sans chevauchement de sous-bande
WO2025208578A1 (fr) Transmission et réception de bloc d'informations de système à la demande
US12495449B2 (en) Determination for uplink repetitions
WO2024212064A1 (fr) Rapport de csi pour activation de cellule
US12531702B2 (en) Dynamic transmission configuration indicator activation
WO2024182934A1 (fr) Facilitation d'une opération de liaison montante dans une cellule secondaire sans bloc de signaux de synchronisation
WO2024216411A1 (fr) Indicateur de format de transmission pour créneau en duplex intégral sans chevauchement de sous-bande
WO2025171609A1 (fr) Activation de cellule
US20250039896A1 (en) Mechanism for repetition of downlink control information
EP4415297A1 (fr) Transmission d'informations de commande de liaison latérale correspondante à des ressources de signal de référence
WO2025030507A1 (fr) Transition d'état d'opération discontinue de cellule
WO2025065437A1 (fr) Activation de cellule
US20250267751A1 (en) Transmission configuration indicator activation
US20250055606A1 (en) Dynamic coexistence of physical sidelink feedback channel transmissions and sidelink reference signal transmissions
US20250056660A1 (en) Collision handling for interruptions and discontinuous reception operation
US20250081195A1 (en) Repetition of physical downlink control channel
WO2026030944A1 (fr) Fonctionnement de réseau économe en énergie
WO2024182932A1 (fr) Facilitation d'une opération de liaison montante dans une cellule secondaire sans bloc de signaux de synchronisation
WO2025030539A1 (fr) Transmission de csi-rs

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24933526

Country of ref document: EP

Kind code of ref document: A1