System information validity reporting

Abstract

A method, apparatus, and computer program product are provided. In the context of a method, the method includes receiving a system information block 19. The method includes determining a validity duration that is carried by or provided by the system information block 19. The method includes generating an indication of the validity duration. The method includes transmitting, to a network node, the indication of the validity duration that is carried by or provided by the system information block 19.

Description

SYSTEM INFORMATION VALIDITY REPORTINGTECHNOLOGICAL FIELD

[0001] An example embodiment relates generally to system information blocks, and, more particularly, to reporting validity durations associated with system information blocks.BACKGROUND

[0002] Half-duplex devices cannot receive and transmit simultaneously. In terrestrial networks, these devices are relatively easy to handle because the round-trip time (RTT) in such a network is limited. Thus, the network may determine whether uplink and downlink will collide. In traditional terrestrial networks, a network node is able to keep track of the timing advance commands provided to the user equipment over time and therefore have a reasonable understanding of the timing advance that is being applied at the user equipment side. A halfduplex user equipment (HD-UE) in paired spectrum is not capable of simultaneous transmissions and receptions on a serving cell with paired spectrum. An HD-UE does not expect to detect a DCI format scheduling a reception in a set of symbols and detect a DCI format scheduling an uplink transmission in any symbol from the set of symbols. If a HD-UE is configured by higher layers to receive a physical downlink control channel, physical downlink shared channel, channel state information-reference signal, or downlink positioning reference signal in a set of signals, the HD-UE receives the physical downlink control channel, physical downlink shared channel, channel state information-reference signal, or downlink positioning reference if the HD-UE does not detect a downlink control information format that indicates to the HD-UE to transmit a physical downlink control channel, physical downlink shared channel, channel state informationreference signal, or downlink positioning reference in at least one symbol of a set of symbols. Otherwise, the HD-UE does not receive the physical downlink control channel, physical downlink shared channel, channel state information-reference signal, or downlink positioning reference in the set of symbols.

[0003] In non-terrestrial networks, the RTT is longer and with large variation within a cell. For example, the differential delay in a cell deployed by a low-earth orbit satellite at 600 km altitude exceeds 3 milliseconds (ms). Such large uncertainty makes it difficult for the network to determine whether uplink and downlink transmissions will collide in a specific user equipment.

[0004] In internet of things non-terrestrial networks, half-duplex devices are supported. The collision rules for these networks and only define that a user equipment will not receive a downlink subframe before and after an uplink subframe. For type B half-duplex frequency division duplexing operation, guard periods (i.e., half-duplex guard subframes), are created by a user equipment by not receiving a downlink subframe immediately preceding an uplink subframe from the same user equipment and not receiving a downlink subframe immediately following an uplink subframe from the same user equipment. One approach to handling timing uncertainty is that the user equipment reports the timing advance which it applies so that a base station may estimate when the user equipment will start uplink transmission and receive downlink transmission. In non-terrestrial networks, the user equipment may be responsible for precompensating uplink transmissions by setting its timing advance based on the current user equipment position, satellite position, and feeder link delay, or alternately based on a received timing advance commands from the network that will adjust the pre-compensation in the uplink transmission by the user equipment. Satellite position and feeder link delay are part of satellite assistance information provided to a user equipment via a system information block 19 (SIB 19) and are essential system information for the user equipment.

[0005] A user equipment applies a system information acquisition procedure to acquire access stratum, non-access stratum, and positioning assistance data information. A user equipment may apply this procedure in a radio resource control idle mode, a radio resource control inactive mode, or a radio resource control connected mode. User equipment devices in idle or inactive modes will ensure that they have a valid version of at least a master information block, system information blocks 1-4. In addition, if the user equipment is accessing new radio via a nonterrestrial network, it will ensure it has a valid version of a SIB 19. A user equipment in a radio resource control connected mode which has received a SIB 19 in a non-terrestrial network cell will attempt to re-acquire a SIB 19 before the end of a duration indicated by ntn- UlSyncValidityDuration and epochTime by user equipment implementation.

[0006] For system information message acquisition, physical downlink control channel monitoring occasions are determined according to searchSpaceOtherSystemlnformation. If searchSpaceOtherSystemlnformation is set to zero, physical downlink control channel monitoring occasions for system information message reception in a system information window are the same as physical downlink control channel monitoring occasions for system informationblock 1. If searchSpaceOtherSystemlnformation is not set to zero, physical downlink control channel monitoring occasions for a system information message are determined based on search space indicated by searchSpaceOtherSystemlnformation.

[0007] When acquiring a system information message, a user equipment determines the start of a system information window for the message. If the system information message is configured in the schedulinglnfoList, the user equipment determines a number n which corresponds to the order of entry in the list of system information messages configured by schedulinglnfoList in si- Schedulinglnfo in system information block 1. The user equipment determines the integer value x=(n-l)*w, where w is the si-Window Length. The system information window starts with the slot a, where a x mod N, in the radio frame for which system from number mod T=FLOOR(x / N), where T is the si-Periodicity of the system information message and N is the number of slots in a radio frame. The user equipment receives a physical downlink control channel containing the scheduling radio network temporary identifier (i.e. system information radio network temporary identifier in the physical downlink control channel monitoring occasions for system information message acquisition) from the start of the system information window and continues until (i) the end of the system information window whose absolute length in time is given by si- WindowLength, or (ii) until the system information message was received. A user equipment in a radio resource control connected mode may stop physical downlink control channel monitoring during the system information window for the concerned system information message when the needed system information blocks are acquired.

[0008] The scheduling of each system information block is defined in an information element SI- Schedulinglnfo. This information element includes si-Periodicity defining a periodicity of the system information message in radio frames (e.g., 8 radio frames, 16 radio frames, and so on) and si-Window Length defining the length of the system information scheduling window (e.g., 5 slots, 10 slots, and so on), with si-Windo Length being shorter than or equal to si-Periodicity.

[0009] In both internet of things and new radio non-terrestrial networks, the user equipment may be capable of reporting its timing advance via a medium access control control element (MAC CE) report. The parameter uplink-TA-Reporting-rl7 indicates whether the user equipment supports user equipment reporting of information related to timing advance pre-compensation. The timing advance reporting procedure is used in a non-terrestrial network or an air to ground network to provide a network node with an estimate of the user equipment’s timing advancevalue. The timing advance report MAC CE includes a timing advance (TA) field indicating the least integer number of slots for the non-terrestrial network (using subcarrier spacing of 15 kHz) greater than or equal to the timing advance value. Only values 1 ... 56 are used and the length of the filed is 14 bits.

[0010] Collision rules for HD RedCap devices define that they shall transmit physical uplink shared channel, physical uplink control channel, physical random access channel, or sounding reference signal (if triggered by a downlink control information, as they are dynamically scheduled by a network node) despite a collision with physical downlink control channel or physical downlink shared channel reception configured by higher layers. This may be problematic in non-terrestrial networks where the user equipment has to maintain a valid SIB 19 in order to be able to pre-compensate uplink transmissions correctly. If the user equipment does not have a valid SIB 19, it is not allowed to transmit scheduled physical uplink shared channel, physical uplink control channel, physical random access channel, or sounding reference signal any way due to a loss of uplink synchronization at the time that the validity timer expires. In addition, this may create conflict - if the user equipment (UE) does not acquire the SIB 19 with updated information, it may not be able to maintain the uplink (UL) synchronization, and hence may have to block the UL transmissions (which it would otherwise have to prioritize).

[0011] The network is not aware when the user equipment is attempting to acquire the SIB 19. The expected configuration for the network is that a gNB would provide the SIB 19 with a shorter periodicity compared to the validity duration. The re-acquisition of SIB 19 may be based on the validity duration conveyed in the information element NTN-CONFIG. The validity duration configured by the network for assistance information (i.e., Serving and / or neighbour satellite ephemeris and common timing advance parameters) indicates a maximum time duration (from epochTime) during which the user equipment may apply assistance information without having new assistance information.

[0012] The network does not know during which scheduling window during a validity duration the user equipment will read a SIB 19. A network scheduler must block a very large amount of uplink resources because they collide with a physical downlink channel monitoring occasion, which may potentially include a SIB 19 scheduling which the user equipment is potentially in need of. A solution is needed to enable the network scheduler to not block all physical downlinkcontrol channel monitoring occasions related to SIB 19 scheduling, while at the same time enabling a user equipment to acquire a SIB 19 timely.BRIEF SUMMARY

[0013] In one or more embodiments, a user equipment (110) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to determine a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an indication (420) of the validity duration (416). The user equipment (110) is further caused to transmit (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0014] In one or more embodiments, a network node (112) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the network node (112) to receive (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The network node (112) is further caused to, based on the indication (420), schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0015] In one or more embodiments, a user equipment (110) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). The user equipment (110) is further caused to transmit (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0016] In one or more embodiments, a network node (112) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the network node (112) to receive (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system informationblock 19 (414). The network node (112) is further caused to determine, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0017] In one or more embodiments, a user equipment (110) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (110) to receive (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment in response to the system information block 19 (414) and the indication. The user equipment (110) is further caused to transmit, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0018] In one or more embodiments, a network node (112) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the network node (112) to transmit (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to receive, from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0019] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (110) and performs receiving (418) a system information block 19 (414). The method further includes determining a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes generating an indication (420) of the validity duration (416). The method further includes transmitting (422), toa network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0020] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes receiving (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The method further includes, based on the indication (420), scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0021] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (110) and includes receiving (418) a system information block 19 (414). The user equipment (110) further includes generating an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). The user equipment (110) further includes transmitting (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0022] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes receiving (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The method further includes determining, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0023] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (110) and includes receiving (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes generating an acknowledgment in response to the system information block 19 (414) and the indication. The method further includes transmitting,to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0024] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes transmitting (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes receiving from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The method further includes scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0025] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (110), cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to determine a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an indication (420) of the validity duration (416). The user equipment (110) is further caused to transmit (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0026] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to receive (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The network node (112) is further caused to, based on the indication (420), schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0027] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (110), cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). Theuser equipment (110) is further caused to transmit (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0028] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to receive (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The network node (112) is further caused to determine, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0029] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (110), cause the user equipment (110) to receive (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment in response to the system information block 19 (414) and the indication. The user equipment (110) is further caused to transmit, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0030] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to transmit (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to receive, from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The network node (112) is further caused to schedule (424) one or more uplink transmissions (428)for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0031] In one or more embodiments, a user equipment (110) is provided that includes means for receiving (418) a system information block 19 (414). The user equipment (110) further includes means for determining a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) further includes means for generating an indication (420) of the validity duration (416). The user equipment (110) further includes means for transmitting (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0032] In one or more embodiments, a network node (112) is provided that includes means for receiving (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The network node (112) further includes means for, based on the indication (420), scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0033] In one or more embodiments, a user equipment (110) is provided that includes means for receiving (418) a system information block 19 (414). The user equipment (110) further includes means for generating an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). The user equipment (110) further includes means for transmitting (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0034] In one or more embodiments, a network node (112) is provided that includes means for receiving (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The network node (112) further includes means for determining, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) further includes means for scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0035] In one or more embodiments, a user equipment (110) is provided that includes means for receiving (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) further includes means for generating an acknowledgment in response to the system information block 19 (414) and the indication. The user equipment (110) further includes means for transmitting, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0036] In one or more embodiments, a network node (112) is provided that includes means for transmitting (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) further includes means for receiving, from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The network node (112) further includes means for scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).BRIEF DESCRIPTION OF THE DRAWINGS

[0037] Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and where:

[0038] FIG. 1 is a block diagram of a system including a user equipment and a network node, configured to communicate at least via uplink and downlink transmission in accordance with an example embodiment of the present disclosure;

[0039] FIG. 2 is a block diagram of an example communication system in which the system of FIG. 1 may be deployed in accordance with an example embodiment of the present disclosure;

[0040] FIG. 3 illustrates an information element in accordance with previous embodiments;

[0041] FIG. 4 illustrates an example signaling diagram of a user equipment transmitting an indication of a SIB 19 validity duration to a network in accordance with an example embodiment of the present disclosure;

[0042] FIG. 5 illustrates an example signaling diagram of a network performing a dedicated transmission of a SIB 19 including a validity duration in accordance with an example embodiment of the present disclosure;

[0043] FIG. 6 is a flowchart illustrating operations performed by a user equipment in order to transmit an indication of a validity duration carried or provided by a system information block 19 in accordance with an example embodiment of the present disclosure;

[0044] FIG. 7 is a flowchart illustrating operations performed by a network node in order to schedule uplink transmissions during a validity duration in accordance with example embodiments of the present disclosure;

[0045] FIG. 8 is a flowchart illustrating operations performed by a user equipment in order to transmit an acknowledgment indicating a time instance at which the user equipment received a system information block 19 in accordance with example embodiments of the present disclosure;

[0046] FIG. 9 is a flowchart illustrating operations performed by a network node in order to schedule one or more uplink transmissions during a validity duration determined from a time at which a user equipment received a system information block 19 in accordance with example embodiments of the present disclosure;

[0047] FIG. 10 is a flowchart illustrating operations performed by a user equipment in order to transmit an acknowledgment in response to a system information block 19 and an indication of validity duration carried or provided by the system information block 19 in accordance with example embodiments of the present disclosure; and

[0048] FIG. 11 is a flowchart illustrating operations performed by a network node in order to schedule uplink transmissions during a validity duration which is indicated to a user equipment through a radio resource control message in accordance with example embodiments of the present disclosure.DETAILED DESCRIPTION

[0049] Some embodiments of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments are shown. Indeed, various embodiments may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like referencenumerals refer to like elements throughout. As used herein, the terms “data,” “content,” “information,” and similar terms may be used interchangeably to refer to data capable of being transmitted, received and / or stored in accordance with embodiments of the present disclosure. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present disclosure.

[0050] Additionally, as used herein, the term “circuitry” refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and / or digital circuitry); (b) combinations of circuits and computer program product(s) including software and / or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. This definition of “circuitry” applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term “circuitry” also includes an implementation including one or more processors and / or portion(s) thereof and accompanying software and / or firmware. As another example, the term “circuitry” as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, other network device (such as a core network apparatus), field programmable gate array, and / or other computing device.

[0051] As used herein, the term “computer-readable medium” refers to non-transitory storage hardware, non-transitory storage device or non-transitory computer system memory that may be accessed by a controller, a microcontroller, a computational system or a module of a computational system to encored thereon computer-executable instructions or software programs. A non-transitory “computer readable medium” may be accessed by a computational system or a module of a computational system to retrieve and / or execute the computerexecutable instructions or software programs encoded on the medium. Examples of non- transitory computer-readable media may include, but are not limited to, one or more types of hardware memory, non-transitory tangible media (for example, one or more magnetic storage disks, one or more optical disks, one or more universal synchronous bus (USB) flash drives), computer system memory or random-access memory (such as dynamic random access memory(DRAM), static random access memory (SRAM), extended data out random access memory (EDO RAM), and the like.

[0052] As illustrated in FIG. 1, a system 100 is provided in accordance with an example embodiment in order to extend measurement periods. Although the system may be configured in various manners, the system of one embodiment is depicted in FIG. 1 and includes user equipment 110 and network node 112 configured to communicate via uplink and downlink transmission and reception beams. Although one user equipment and one network node are depicted, the system may include and the user equipment 110 and network node 112 may communicate with additional user equipment and network nodes in other embodiments. In one or more embodiments, the user equipment 110 and network node 112 may be configured to support, for example, 5G, 5G advanced, or 6G. In one or more embodiments, the system 100 may support carrier aggregation and / or dual connectivity. As described below, the system may support non-terrestrial networks and mobile originated traffic.

[0053] The data that is transmitted via the uplink and downlink beams between the user equipment 110 and network node 112 may be any of a wide variety of data including, but not limited to digital imagery data including video data, audio data as well as data provided by sensors, radars, telescopes and radio receivers. In at least some instances, the data is encoded prior to communication of the data via the uplink and downlink beams and decoded upon reception. The resulting data received may be utilized for a variety of purposes including presentation to a user, storage of the data for subsequent use and / or provision of the data to one or more applications, such as applications that perform statistical inference on the data for various purposes including object recognition, image classification, spectrum sensing, speech transcription and / or prediction or detection of events.

[0054] The user equipment 110 of FIG. 1 (also called UE, user device, user terminal, terminal device, etc.) illustrates a type of an apparatus which resources on an air interface are allocated and assigned. The user equipment 110 typically refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: a mobile station (mobile phone), smartphone, personal digital assistance (PDA), handset, device using a wireless modem (alarm or measurement device, etc.), laptop and / or touch screen computer, tablet, game console, notebook, and multimedia device. User equipment 110 may alsobe a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human- to-human or human- to-computer interaction. The user equipment 110 may also be called a subscriber unit, mobile station, remote terminal, access terminal, user terminal, or user equipment (UE) just to mention but a few names or apparatuses.

[0055] The network node 112 of FIG. 1 may include, for example, base stations such as remote radio heads (RRHs), transmission reception points (TRPs), access points, node Bs (e.g., eNB, gNB) or other transmission sources. The network node 112 may be configured to communicate with user equipment 110 via a network. The network node 112 may be accessed through a gateway.

[0056] FIG. 2 depicts an example apparatus 200 that may be configured to function as user equipment 110, network node 112, and / or satellites 114-118. As shown in FIG. 2, the apparatus includes, is associated with, or is in communications with processing circuitry 220, a memory 240, and a communication interface 260. The processing circuitry 220 may be in communication with the memory device 240 via a bus for passing information among components of the apparatus. The memory device may be non-transitory and may include, for example, one or more volatile and / or non-volatile memories. In other words, for example, the memory device may be an electronic storage device (e.g., a computer readable storage medium) including gates configured to store data (e.g., bits) that may be retrievable by a machine (e.g., a computing device like the processing circuitry). The memory device may be configured to store information, data, content, applications, instructions, or the like for enabling the apparatus to carry out various functions in accordance with an example embodiment of the present disclosure. For example, the memory device could be configured to buffer input data for processing by the processing circuitry. Additionally or alternatively, the memory device could be configured to store instructions for execution by the processing circuitry.

[0057] The apparatus 200 may, in some embodiments, be embodied in various computing devices described as above. However, in some embodiments, the apparatus may be embodied as a chip or chip set. In other words, the apparatus may include one or more physical packages (e.g., chips) including materials, components and / or wires on a structural assembly (e.g., a baseboard). The structural assembly may provide physical strength, conservation of size, and / or limitation of electrical interaction for component circuitry included thereon. The apparatus maytherefore, in some cases, be configured to implement an embodiment on a single chip or as a single “system on a chip.” As such, in some cases, a chip or chipset may constitute means for performing one or more operations for providing the functionalities described herein.

[0058] The processing circuitry 220, also referenced as a processor, may be embodied in a number of different ways. For example, the processing circuitry may be embodied as one or more of various hardware processing means such as a coprocessor, a microprocessor, a controller, a digital signal processor (DSP), a processing element with or without an accompanying DSP, or various other circuitry including integrated circuits such as, for example, an ASIC (application specific integrated circuit), an FPGA (field programmable gate array), a microcontroller unit (MCU), a hardware accelerator, a special-purpose computer chip, or the like. As such, in some embodiments, the processing circuitry may include one or more processing cores configured to perform independently. A multi-core processing circuitry may enable multiprocessing within a single physical package. Additionally or alternatively, the processing circuitry may include one or more processors configured in tandem via the bus to enable independent execution of instructions, pipelining, and / or multithreading.

[0059] In an example embodiment, the processing circuitry 220 may be configured to execute instructions stored in the memory device 240 or otherwise accessible to the processing circuitry. Alternatively or additionally, the processing circuitry may be configured to execute hardcoded functionality. As such, whether configured by hardware or software methods, or by a combination thereof, the processing circuitry may represent an entity (e.g., physically embodied in circuitry) capable of performing operations according to an embodiment of the present disclosure while configured accordingly. Thus, for example, when the processing circuitry is embodied as an ASIC, FPGA or the like, the processing circuitry may be specifically configured hardware for conducting the operations described herein. Alternatively, as another example, when the processing circuitry is embodied as an executor of instructions, the instructions may specifically configure the processor to perform the algorithms and / or operations described herein when the instructions are executed. However, in some cases, the processing circuitry may be a processor of a specific device (e.g., an image or video processing system) configured to employ an embodiment by further configuration of the processing circuitry by instructions for performing the algorithms and / or operations described herein. The processing circuitry mayinclude, among other things, a clock, an arithmetic logic unit (ALU) and logic gates configured to support operation of the processing circuitry.

[0060] The communication interface 260 may be any means such as a device or circuitry embodied in either hardware or a combination of hardware and software that is configured to receive and / or transmit data including media content in the form of video or image files, one or more audio tracks or the like. In this regard, the communication interface may include, for example, an antenna (or multiple antennas) and supporting hardware and / or software for enabling communications with a wireless communication network. Additionally or alternatively, the communication interface may include the circuitry for interacting with the antenna(s) to cause transmission of signals via the antenna(s) or to handle receipt of signals received via the antenna(s). In some environments, the communications interface may alternatively or also support wired communication. As such, for example, the communication interface may include a communication modem and / or other hardware / software for supporting communication via cable, digital subscriber line (DSL), universal serial bus (USB) or other mechanisms.

[0061] Turning now to FIG. 3, an information element NTN-Config 300 is provided in accordance with previous embodiments. The network is not aware when the user equipment is attempting to acquire the SIB 19. The expected configuration for the network is that a gNB would provide the SIB 19 with a shorter periodicity compared to the validity duration. The reacquisition of SIB 19 is based on the validity duration conveyed in the information element 300. The validity duration is configured by the network in parameter ntn-UlSyncValidity for assistance information (i.e., Serving and / or neighbour satellite ephemeris and common timing advance parameters) indicates a maximum time duration (from epochTime) during which the user equipment may apply assistance information without having acquired new assistance information. The unit of parameter 302 is a second (i.e., s5 indicates 5 seconds, slO indicates 10 seconds, and so on). Parameter 302 applies to both connected and idle mode user equipment devices. If parameter 302 is empty in information element 300 provided via non-terrestrial network NeighCellConfig, the user equipment uses a validity duration from serving cell assistance information. The parameter 302 is excluded when determining changes in system information (i.e., changes of parameter 302 should neither result in system information change notifications nor in a modification of valueTag in system information block 1). Parameter 302 is only updated when at least one of epochTime, ta-Info, or ephemerisinfo is updated.

[0062] The range of parameter 302 is between 5 second and several minutes and the number of system information windows within such a range may be large since the system information periodicity is 8-152 radio frames (a radio frame being 10 ms long). Furthermore, the system information window length is 5-1280 slots and there may thus be many physical downlink control channel monitoring occasions (for scheduling the system information block) within each system information window. If a network configures for a SIB 19 to be provided roughly every 1 second, while the validity duration indicated by parameter 302 is 10 seconds, the user equipment has an opportunity to monitor every second but would in principle only need to actually read the SIB 19 every 10 seconds (or 20 seconds in case the network provides ephemeris information pointing to the future under the condition that the user equipment supports “backwards propagation” of the provided ephemeris information). However, the network will not know during which of the SIB scheduling windows during a validity duration indicated by parameter 302 the user equipment will actually read the SIB 19.

[0063] Turning now to FIG. 4, an example signaling diagram where a user equipment indicates a validity duration of a SIB 19 to a network node is provide in accordance with an example embodiment of the present disclosure. In one or more embodiments, a network node 112 broadcasts a SIB 19414. In some examples, during time 412, the user equipment 110 does not yet receive the SIB 19414. For example, user equipment 110 may be prioritizing uplink transmission during time 412.

[0064] In one or more embodiments, at operation 418, a user equipment 110 receives the SIB19 414. In some examples, the user equipment 110 determines a validity duration 416 that is carried by or provided by the SIB 19 414.

[0065] In some examples, the user equipment 110 generates an indication 420 of the validity duration 416. In one or more embodiments, at operation 422, the user equipment 110 transmits the indication 420 to the network node 112. In some examples, the indication 420 is provided as part of a timing advance report MAC CE if the user equipment 110 is capable of providing the timing advance report. In some examples, an additional octet may be added or some of the unused bits may be used (e.g., using more than 6 bits out of 14 available in the timing advance field).

[0066] In some examples, the indication 420 is provided in a new dedicated MAC CE. The example user equipment 110 may multiplex the MAC CE with other uplink data as per legacy means.

[0067] In some examples, the indication 420 is provided as part of uplink control information. In some examples, this may include HARQ feedback, scheduling request, link recovery request, channel state information, and / or the like. In some examples, the uplink control information may be transmitted on a physical uplink control channel or a physical uplink shared channel.

[0068] In some examples, the indication 420 indicates the last time the user equipment 110 read the SIB19414. For example, the indication 420 may indicate the Coordinated Universal Time (UTC) or system frame number (SFN) of an actual reception or define the first slot of a corresponding system information window, where the SIB 19 414 was acquired. Additionally or alternatively, the indication may be the relative time since the user equipment 110 acquired the SIB19414 (e.g., X seconds / frames / subframes).

[0069] In some examples, the indication 420 indicates that the user equipment 110 acquired the SIB 19 414 in a current system information window. In some examples, the indication 420 indicates that the user equipment 110 acquired the SIB 19414 in a previous system information window.

[0070] In some examples, the indication 420 indicates the version number of SIB 19414. In some examples, this is added to the SIB 19414 set of information elements. In some examples, the version number is linked to a system information window or increment with each SIB 19 scheduling within the system information window.

[0071] In some examples, the indication 420 indicates a remaining time until the SIB 19 expires. For example, the indication 420 may indicate that the remaining validity duration 416 is equal to an epoch time plus a validity duration minus a current time.

[0072] In some examples, the indication 420 indicates an absolute time in which the SIB19 414 will expire. For example, the absolute time 420 may be given as UTC or SFN.

[0073] In some examples, the indication 420 indicates a number of system information windows until a user equipment 110 attempts a first reread of the SIB19 414.

[0074] In one or more embodiments, at operation 424, the network node 112 schedules uplink transmissions 428 during the validity duration 416. During the validity duration 416, the user equipment 110 changes the collision rule and prioritized 426 uplink transmission. In someexamples, the uplink transmissions 428 collide with physical downlink control channel monitoring occasions for SIB 19 scheduling. In some examples, the network node 112 and user equipment 110 schedule uplink transitions during the validity duration 416 since they both know that SIB 19 414 remains valid and when the user equipment 110 will attempt to reacquire the SIB 19. Therefore, the example network node 112 knows which SIB 19 scheduling occasions the user equipment may use and thus prioritize 432 over uplink transmissions. The example network node 112 will also know which scheduling occasions the user equipment 110 will not use and thus may schedule 424 uplink transmissions 428 which the user equipment will prioritize 426. The example indication 420 of SIB 19414 will define whether the collision rule results in user equipment 110 prioritizes SIB 19 downlink reception or uplink transmission. In some examples, the network node 112 and user equipment 110 have an aligned understanding of when the user equipment 110 will prioritize 432 SIB19434 reception over uplink transmissions 428. In some examples, the network node is able to schedule 424 uplink transmissions 428 which would otherwise be blocked by downlink reception of SIB 19434, therefore enhancing scheduling flexibility and resource utilization. In some embodiments, the example indication may also apply to other SIBs essential to half-duplex devices operation.

[0075] In one or more embodiments, user equipment 110 determines at time 430 to reacquire a subsequent SIB 19434 including a subsequent validity duration 436. In one or more embodiments, the user equipment 110 changes the collision rule to prioritize 432 SIB 19 reception at the time 430.

[0076] In some embodiments, a conservative user equipment 110 may attempt to require SIB 19 at time 430 long before the expiry of validity duration 416 (e.g., X system information windows / physical downlink control channel monitoring occasions before the expiration of validity duration 416). In some embodiments, an aggressive user equipment 110 may attempt to acquire the new SIB 19 434 at a time 430 shortly before the expiry of the validity duration 416 (e.g., in the last system information window before the expiry). In further embodiments, a user equipment 110 in poor radio coverage may need repetitions of SIB 19 434 and therefore attempt to acquire SIB19434 long before the expiry of the current validity duration 416 (e.g., X system information windows / physical downlink control channel monitoring occasions before the expiry). As such, there may be a user equipment 110 specific safety margin such that the user equipment 110 is defined to be unavailable for uplink transmissions 428 during the validityduration 416. In some examples, the user equipment 110 capability may define the safety margin. In some examples, the user equipment 110 signals the safety margin as part of indication 420. In some examples, the user equipment 110 signals the safety margin as part of radio resource control signaling. In some examples, the user equipment 110 accounts for the safety margin when transmitting 422 the indication 420 (e.g., the user equipment 110 subtracts the safety margin from the reported validity duration 416). In some examples, the safety margin is a hard- coded maximum time to acquire a new SIB 19.

[0077] Turning now to FIG. 5, a signaling diagram 500 is provided where the SIB19414 is transmitted 502 to the user equipment 110 from the network node 112 via a dedicated transmission 504. In some examples, the dedicated transmission 504 is a radio resource control message. In some examples, the user equipment 110 responds by transmitting an acknowledgment (e.g., a hybrid automatic repeat request acknowledgment) or by transmitting an acknowledgement as part of the Radio Link Control protocol. Based on the acknowledgment, the example network node 112 knows the validity duration 416 of the SIB 19 414 acquired by the user equipment 110. In some examples, the network node 112 may operate in a single-shot mode, where a single provisioning of SIB 19 414 opens a window of given duration where the user equipment 110 does not need to read the broadcast information (i.e., the user equipment prioritizes 426 uplink scheduling). In some examples, the network node 112 may provide the user equipment 110 with a new SIB 19 information element using dedicated signaling or by providing the information content of SIB 19 through other dedicated signaling, extending the window where the user equipment 110 does not have to read the SIB 19 from the broadcast information. In some examples, the network node 112 is never in doubt of the validity time 116 due to radio resource control information being acknowledged by the user equipment 110.

[0078] In some examples, hybrid automatic repeat request feedback on a per- hybrid automatic repeat request process may be disabled to avoid stalling due to a long RTT. If hybrid automatic repeat request feedback is disabled for a message, a user equipment 110 may not change priority of uplink or downlink transmissions.

[0079] Turning now to FIG. 6, an example flowchart is illustrated for a process 600 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a user equipment (110) in order to transmit an indication of a validity duration.

[0080] As shown in block 602 of FIG. 6, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for receiving (418) a system information block 19 (414). In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space. In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0081] As shown in block 604 of FIG. 6, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for determining a validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the user equipment (110) is further caused to prioritize (426) uplink transmissions (428) during the validity duration (416). In one or more embodiments, the user equipment (110) is further caused to prioritize (432) reception of a subsequent system information block 19 (434) after the validity duration (416).

[0082] As shown in block 606 of FIG. 6, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for generating an indication (420) of the validity duration (416). In one or more embodiments, the user equipment (110) is further caused to determine a safety margin which is included in the indication (420), wherein the safety margin is specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire. In one or more embodiments, the indication (420) is a part of one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information. In one or more embodiments, the indication (420) includes at least one or a combination of a time instance at which the user equipment (110) read the system information block 19 (414), a version number of the system information block 19 (414), a remaining time duration until the system information block 19 (414) expires, an absolute time in which the system information block 19 (414) will expire, and a number of system information windows until the user equipment (110) attempts a first reread of the system information block 19 (414).

[0083] As shown in block 608 of FIG. 6, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), thelike, for transmitting (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0084] Turning now to FIG. 7, an example flowchart is illustrated for a process 700 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a network node (112) in order to schedule uplink transmissions.

[0085] As shown in block 702 of FIG. 7, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for receiving (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). In one or more embodiments, the indication (420) further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin. In one or more embodiments, the indication (420) is provided in one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information. In one or more embodiments, the indication (420) comprises at least one or a combination of a time instance at which the user equipment (110) read the system information block 19 (414), a version number of the system information block 19 (414), a remaining time duration until the system information block 19 (414) expires, an absolute time in which the system information block 19 (414) will expire, and a number of system information windows until the user equipment (110) attempts a first reread of the system information block 19 (414).

[0086] As shown in block 704 of FIG. 7, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for, based on the indication (420), scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space. In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0087] Turning now to FIG. 8, an example flowchart is illustrated for a process 800 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a user equipment (110) in order to transmit an acknowledgment indicating a time instance when the user equipment (110) received a system information block 19.

[0088] As shown in block 802 of FIG. 8, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for receiving (418) a system information block 19 (414). In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space. In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0089] As shown in block 804 of FIG. 8, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for generating an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). In one or more embodiments, the user equipment (110) is further caused to determine a safety margin which is included in the acknowledgment specific to the user equipment (110) and prior to an absolute time at which the system information block 19 (414) will expire. In one or more embodiments, the acknowledgment (420) is part of at least one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0090] As shown in block 806 of FIG. 8, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for transmitting (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414). In one or more embodiments, the user equipment (110) is further caused to determine, based on the time instance at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the user equipment (110) is further caused to prioritize (426) uplink transmissions (428) during the validity duration (416). In one or more embodiments, theuser equipment (110) is further caused to prioritize reception of a subsequent system information block 19 (434) after the validity duration (416).

[0091] Turning now to FIG. 9, an example flowchart is illustrated for a process 900 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a network node (112) in order to schedule uplink transmissions during a validity duration determined based on an acknowledgment.

[0092] As shown in block 902 of FIG. 9, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for receiving (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). In one or more embodiments, the acknowledgment (420) further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin. In one or more embodiments, the acknowledgment (420) is provided in one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information. In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space. In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0093] As shown in block 904 of FIG. 9, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for determining, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414).

[0094] As shown in block 906 of FIG. 9, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0095] Turning now to FIG. 10, an example flowchart is illustrated for a process 1000 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a user equipment (110) in order to transmit an acknowledgment in response to a radio resource control message including an indication of a validity duration.

[0096] As shown in block 1002 of FIG. 10, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for receiving (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the indication includes a version number of the system information block 19 (414). In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space. In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0097] As shown in block 1004 of FIG. 10, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for generating an acknowledgment in response to the system information block 19 (414) and the indication. In one or more embodiments, the user equipment (110) is further caused to determine a safety margin which is included in the acknowledgment specific to the user equipment (110) and prior to an absolute time at which the system information block 19 (414) will expire.

[0098] As shown in block 1006 of FIG. 10, the apparatus embodied by the user equipment (110) includes means, such as the processing circuitry (220), the communication interface (260), the like, for transmitting, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication. In one or more embodiments, the user equipment (110) is further caused to prioritize (426) uplink transmissions (428) during the validity duration (416) of the system information block 19 (414). In one or more embodiments, the user equipment (110) is further caused to prioritize (432) reception of a subsequent system information block 19 (434) after the validity duration (416) of the system information block 19 (414).

[0099] Turning now to FIG. 11, an example flowchart is illustrated for a process 1100 performed by an apparatus embodied by, associated with or otherwise in communication with (hereinafter generally referenced as being embodied by) a network node (112) in order to transmit a radio resource control message indicating a validity duration and schedule uplink transmissions during the validity duration.

[0100] As shown in block 1102 of FIG. 11, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for transmitting (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the indication comprises a version number of the system information block 19. In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space. In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0101] As shown in block 1104 of FIG. 11, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for receiving, from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. In one or more embodiments, the acknowledgment further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0102] As shown in block 1106 of FIG. 9, the apparatus embodied by the network node (112) includes means, such as the processing circuitry (220), the communication interface (260), the like, for scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0103] FIGS. 6-11 illustrate flowcharts depicting methods according to an example embodiment of the present disclosure. It will be understood that each block of the flowcharts and combination of blocks in the flowcharts may be implemented by various means, such as hardware, firmware, processor, circuitry, and / or other communication devices associated with execution of softwareincluding one or more computer program instructions. For example, one or more of the procedures described above may be embodied by computer program instructions. In this regard, the computer program instructions which embody the procedures described above may be stored by a memory device 240 of an apparatus employing an embodiment and executed by a processor 220. As will be appreciated, any such computer program instructions may be loaded into a computer or other programmable apparatus (for example, hardware) to produce a machine, such that the resulting computer or other programmable apparatus implements the functions specified in the flowchart blocks. These computer program instructions may also be stored in a computer-readable memory that may direct a computer or other programmable apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture the execution of which implements the function specified in the flowchart blocks. The computer program instructions may also be loaded into a computer or other programmable apparatus to cause a series of operations to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide operations for implementing the functions specified in the flowchart blocks.

[0104] Accordingly, blocks of the flowcharts support combinations of means for performing the specified functions and combinations of operations for performing the specified functions for performing the specified functions. It will also be understood that one or more blocks of the flowcharts, and combinations of blocks in the flowcharts, may be implemented by special purpose hardware-based computer systems which perform the specified functions, or combinations of special purpose hardware and computer instructions.

[0105] In one or more embodiments, a user equipment (110) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to determine a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an indication (420) of the validity duration (416). The user equipment (110) is further caused to transmit (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0106] In one or more embodiments, the user equipment (110) is further caused to determine a safety margin which is included in the indication (420), wherein the safety margin is specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire.

[0107] In one or more embodiments, the user equipment (110) is caused to perform at least one or a combination of prioritize (426) uplink transmissions (428) during the validity duration (416). The user equipment (110) is further caused to prioritize (432) reception of a subsequent system information block 19 (434) after the validity duration (416).

[0108] In one or more embodiments, the indication (420) is a part of one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0109] In one or more embodiments, the indication (420) includes at least one or a combination of a time instance at which the user equipment (110) read the system information block 19 (414), a version number of the system information block 19 (414), a remaining time duration until the system information block 19 (414) expires, an absolute time in which the system information block 19 (414) will expire, and a number of system information windows until the user equipment (110) attempts a first reread of the system information block 19 (414).

[0110] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0111] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0112] In one or more embodiments, a network node (112) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the network node (112) to receive (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The network node (112) is further caused to, based on the indication (420), schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0113] In one or more embodiments, the indication (420) further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safetymargin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0114] In one or more embodiments, the indication (420) is provided in one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0115] In one or more embodiments, the indication (420) includes at least one or a combination of a time instance at which the user equipment (110) read the system information block 19 (414), a version number of the system information block 19 (414), a remaining time duration until the system information block 19 (414) expires, an absolute time in which the system information block 19 (414) will expire, and a number of system information windows until the user equipment (110) attempts a first reread of the system information block 19 (414).

[0116] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0117] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0118] In one or more embodiments, a user equipment (110) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). The user equipment (110) is further caused to transmit (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0119] In one or more embodiments, the user equipment (110) is further caused to determine a safety margin which is included in the acknowledgment specific to the user equipment (110) and prior to an absolute time at which the system information block 19 (414) will expire.

[0120] In one or more embodiments, the user equipment (110) is further caused to determine, based on the time instance at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the user equipment (110) is further caused toprioritize (426) uplink transmissions (428) during the validity duration (416). In one or more embodiments, the user equipment (110) is further caused to prioritize reception of a subsequent system information block 19 (434) after the validity duration (416).

[0121] In one or more embodiments, the acknowledgment (420) is part of at least one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0122] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0123] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0124] In one or more embodiments, a network node (112) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the network node (112) to receive (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The network node (112) is further caused to determine, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0125] In one or more embodiments, the acknowledgment (420) further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0126] In one or more embodiments, the acknowledgment (420) is provided in one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0127] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0128] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0129] In one or more embodiments, a user equipment (110) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the user equipment (110) to receive (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment in response to the system information block 19 (414) and the indication. The user equipment (110) is further caused to transmit, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0130] In one or more embodiments, the user equipment (110) is further caused to determine a safety margin which is included in the acknowledgment specific to the user equipment (110) and prior to an absolute time at which the system information block 19 (414) will expire.

[0131] In one or more embodiments, the user equipment (110) is further caused to prioritize (426) uplink transmissions (428) during the validity duration (416) of the system information block 19 (414). The user equipment (110) is further caused to prioritize (432) reception of a subsequent system information block 19 (434) after the validity duration (416) of the system information block 19 (414).

[0132] In one or more embodiments, the indication includes a version number of the system information block 19 (414).

[0133] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0134] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0135] In one or more embodiments, a network node (112) is provided, including at least one processor and at least one memory storing instructions that, when executed by the processor, cause the network node (112) to transmit (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to receive, from the user equipment (110), anacknowledgment in response to the system information block 19 (414) and the indication. The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0136] In one or more embodiments, the acknowledgment further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0137] In one or more embodiments, the indication includes a version number of the system information block 19.

[0138] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0139] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0140] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (110) and performs receiving (418) a system information block 19 (414). The method further includes determining a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes generating an indication (420) of the validity duration (416). The method further includes transmitting (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0141] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes receiving (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The method further includes, based on the indication (420), scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0142] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (110) and includes receiving (418) a system information block 19 (414). The user equipment (110) further includes generating an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19(414). The user equipment (110) further includes transmitting (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0143] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes receiving (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The method further includes determining, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0144] In one or more embodiments, a computer-implemented method is provided that is performed by a user equipment (110) and includes receiving (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes generating an acknowledgment in response to the system information block 19 (414) and the indication. The method further includes transmitting, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0145] In one or more embodiments, a computer-implemented method is provided that is performed by a network node (112) and includes transmitting (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The method further includes receiving from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The method further includes scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0146] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (110), causethe user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to determine a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an indication (420) of the validity duration (416). The user equipment (110) is further caused to transmit (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0147] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to receive (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The network node (112) is further caused to, based on the indication (420), schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0148] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (110), cause the user equipment (110) to receive (418) a system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). The user equipment (110) is further caused to transmit (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0149] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to receive (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The network node (112) is further caused to determine, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0150] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a user equipment (110), cause the user equipment (110) to receive (502), from a network node (112), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) is further caused to generate an acknowledgment in response to the system information block 19 (414) and the indication. The user equipment (110) is further caused to transmit, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0151] In one or more embodiments, a non-transitory computer readable storage medium is provided including computer instructions that, when executed by a network node (112), cause the network node (112) to transmit (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) is further caused to receive, from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The network node (112) is further caused to schedule (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0152] In one or more embodiments, a user equipment (110) is provided that includes means for receiving (418) a system information block 19 (414). The user equipment (110) further includes means for determining a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) further includes means for generating an indication (420) of the validity duration (416). The user equipment (110) further includes means for transmitting (422), to a network node (112), the indication (420) of the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0153] In one or more embodiments, the user equipment (110) further includes means for determining a safety margin which is included in the indication (420), wherein the safety margin is specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire.

[0154] In one or more embodiments, the user equipment (110) further includes means for prioritizing (426) uplink transmissions (428) during the validity duration (416). The user equipment further includes means for prioritizing (432) reception of a subsequent system information block 19 (434) after the validity duration (416).

[0155] In one or more embodiments, the indication (420) is a part of one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0156] In one or more embodiments, the indication (420) includes at least one or a combination of a time instance at which the user equipment (110) read the system information block 19 (414), a version number of the system information block 19 (414), a remaining time duration until the system information block 19 (414) expires, an absolute time in which the system information block 19 (414) will expire, and a number of system information windows until the user equipment (110) attempts a first reread of the system information block 19 (414).

[0157] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0158] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0159] In one or more embodiments, a network node (112) is provided that includes means for receiving (422), from a user equipment (110), an indication (420) of a validity duration (416) that is carried or provided by a system information block 19 (414). The network node (112) further includes means for, based on the indication (420), scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried by or provided by the system information block 19 (414).

[0160] In one or more embodiments, the indication (420) further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0161] In one or more embodiments, the indication (420) is provided in one or a combination of a timing advance report which is delivered / indicated by a medium access control control element(MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0162] In one or more embodiments, the indication (420) includes at least one or a combination of a time instance at which the user equipment (110) read the system information block 19 (414), a version number of the system information block 19 (414), a remaining time duration until the system information block 19 (414) expires, an absolute time in which the system information block 19 (414) will expire, and a number of system information windows until the user equipment (110) attempts a first reread of the system information block 19 (414).

[0163] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0164] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0165] In one or more embodiments, a user equipment (110) is provided that includes means for receiving (418) a system information block 19 (414). The user equipment (110) further includes means for generating an acknowledgment (420) indicating a time instance at which the user equipment (110) received the system information block 19 (414). The user equipment (110) further includes means for transmitting (422), to a network node (112), the acknowledgment (420) indicating the time instance at which the user equipment (110) received the system information block 19 (414).

[0166] In one or more embodiments, the user equipment (110) further includes means for transmitting a safety margin which is included in the acknowledgment specific to the user equipment (110) and prior to an absolute time at which the system information block 19 (414) will expire.

[0167] In one or more embodiments, the user equipment (110) further includes means for determining, based on the time instance at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). In one or more embodiments, the user equipment (110) further includes means for prioritizing (426) uplink transmissions (428) during the validity duration (416). In one or more embodiments, the user equipment (110) further includes means for prioritizing reception of a subsequent system information block 19 (434) after the validity duration (416).

[0168] In one or more embodiments, the acknowledgment (420) is part of at least one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0169] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0170] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0171] In one or more embodiments, a network node (112) is provided that includes means for receiving (422), from a user equipment (110), an acknowledgment (420) indicating a time instance at which the user equipment (110) received a system information block 19 (414). The network node (112) further includes means for determining, based on the time at which the user equipment (110) received the system information block 19 (414), a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) further includes means for scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0172] In one or more embodiments, the acknowledgment (420) further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0173] In one or more embodiments, the acknowledgment (420) is provided in one or a combination of a timing advance report which is delivered / indicated by a medium access control control element (MAC CE), a dedicated MAC CE, a user equipment (UE) dedicated uplink signaling channel, and an uplink control information.

[0174] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0175] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0176] In one or more embodiments, a user equipment (110) is provided that includes means for receiving (502), from a network node (112), a radio resource control message (504) including asystem information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The user equipment (110) further includes means for generating an acknowledgment in response to the system information block 19 (414) and the indication. The user equipment (110) further includes means for transmitting, to the network node (112), an acknowledgment in response to the system information block 19 (414) and the indication.

[0177] In one or more embodiments, the user equipment (110) further includes means for determining a safety margin which is included in the acknowledgment specific to the user equipment (110) and prior to an absolute time at which the system information block 19 (414) will expire.

[0178] In one or more embodiments, the user equipment (110) further includes means for prioritizing (426) uplink transmissions (428) during the validity duration (416) of the system information block 19 (414). The user equipment (110) further includes means for prioritizing (432) reception of a subsequent system information block 19 (434) after the validity duration (416) of the system information block 19 (414).

[0179] In one or more embodiments, the indication includes a version number of the system information block 19 (414).

[0180] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0181] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0182] In one or more embodiments, a network node (112) is provided that includes means for transmitting (502), to a user equipment (110), a radio resource control message (504) including a system information block 19 (414) and an indication of a validity duration (416) that is carried by or provided by the system information block 19 (414). The network node (112) further includes means for receiving, from the user equipment (110), an acknowledgment in response to the system information block 19 (414) and the indication. The network node (112) further includes means for scheduling (424) one or more uplink transmissions (428) for the user equipment (110) during the validity duration (416) that is carried or provided by the system information block 19 (414).

[0183] In one or more embodiments, the acknowledgment further includes a safety margin specific to the user equipment (110) and prior to an absolute time, wherein within the safety margin the system information block 19 (414) will expire, and wherein the network node (112) does not schedule (424) uplink transmissions (428) during the safety margin.

[0184] In one or more embodiments, the indication includes a version number of the system information block 19.

[0185] In one or more embodiments, the system information block 19 (414) includes information on the satellite position and speed in space.

[0186] In one or more embodiments, the validity duration defines a time duration that the user equipment (110) to see ephemeris information as valid.

[0187] Many modifications and other embodiments set forth herein will come to mind to one skilled in the art to which this disclosure pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the disclosure is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims.

[0188] Moreover, although the foregoing descriptions and the associated drawings describe example embodiments in the context of certain example combinations of elements and / or functions, it should be appreciated that different combinations of elements and / or functions may be provided by alternative embodiments without departing from the scope of the appended claims. In this regard, for example, different combinations of elements and / or functions than those explicitly described above are also contemplated as may be set forth in some of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

What is claimed is:

1. A user equipment, comprising: means for receiving a system information block 19; means for determining a validity duration that is carried by or provided by the system information block 19; means for generating an indication of the validity duration; and means for transmitting, to a network node, the indication of the validity duration that is carried by or provided by the system information block 19.

2. The user equipment of claim 1 , wherein the user equipment further includes means for determining a safety margin which is comprised in the indication, wherein the safety margin is specific to the user equipment and prior to an absolute time, wherein within the safety margin the system information block 19 will expire.

3. The user equipment of any one of claims 1-2, wherein the user equipment further includes at least one or a combination of: means for prioritizing uplink transmissions during the validity duration; and means for prioritizing reception of a subsequent system information block 19 after the validity duration.

4. The user equipment of any one of claims 1-3, wherein the indication is a part of one or a combination of: a timing advance report which is delivered / indicated by a medium access control control element (MAC CE); a dedicated MAC CE; a user equipment (UE) dedicated uplink signaling channel; and an uplink control information.

5. The user equipment of any one of claims 1-4, wherein the indication comprises at least one or a combination of:a time instance at which the user equipment read the system information block 19; a version number of the system information block 19; a remaining time duration until the system information block 19 expires; an absolute time in which the system information block 19 will expire; and a number of system information windows until the user equipment attempts a first reread of the system information block 19.

6. The user equipment of any one of claims 1-5, wherein the system information block 19 comprises information on the satellite position and speed in space.

7. The user equipment of any one of claims 1-5, wherein the validity duration defines a time duration that the user equipment to see ephemeris information as valid.

8. A network node, comprising: means for receiving, from a user equipment, an indication of a validity duration that is carried or provided by a system information block 19; and means for, based on the indication, scheduling one or more uplink transmissions for the user equipment during the validity duration that is carried by or provided by the system information block 19.

9. The network node of claim 8, wherein the indication further comprises a safety margin specific to the user equipment and prior to an absolute time, wherein within the safety margin the system information block 19 will expire, and wherein the network node does not schedule uplink transmissions during the safety margin.

10. The network node of any one of claims 8-9, wherein the indication is provided in one or a combination of: a timing advance report which is delivered / indicated by a medium access control control element (MAC CE); a dedicated MAC CE; a user equipment (UE) dedicated uplink signaling channel; andan uplink control information.

11. The network node of any one of claims 8-10, wherein the indication comprises at least one or a combination of: a time instance at which the user equipment read the system information block 19; a version number of the system information block 19; a remaining time duration until the system information block 19 expires; an absolute time in which the system information block 19 will expire; and a number of system information windows until the user equipment attempts a first reread of the system information block 19.

12. The network node of any one of claims 8-11, wherein the system information block 19 comprises information on the satellite position and speed in space.

13. The network node of any one of claims 8-12, wherein the validity duration defines a time duration that the user equipment to see ephemeris information as valid.

14. A computer-implemented method, comprising performing by a user equipment: receiving a system information block 19; determining a validity duration that is carried by or provided by the system information block 19; generating an indication of the validity duration; and transmitting, to a network node, the indication of the validity duration that is carried by or provided by the system information block 19.

15. A computer-implemented method, comprising performing by a network node: receiving, from a user equipment, an indication of a validity duration that is carried or provided by a system information block 19; and based on the indication, scheduling one or more uplink transmissions for the user equipment during the validity duration that is carried by or provided by the system information block 19.

Images