WO2023131420A1 - Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios - Google Patents

Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios Download PDF

Info

Publication number
WO2023131420A1
WO2023131420A1 PCT/EP2022/050332 EP2022050332W WO2023131420A1 WO 2023131420 A1 WO2023131420 A1 WO 2023131420A1 EP 2022050332 W EP2022050332 W EP 2022050332W WO 2023131420 A1 WO2023131420 A1 WO 2023131420A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
sib
segment
network device
network
Prior art date
Application number
PCT/EP2022/050332
Other languages
French (fr)
Inventor
Rafhael MEDEIROS DE AMORIM
Mads LAURIDSEN
Original Assignee
Nokia Technologies Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/EP2022/050332 priority Critical patent/WO2023131420A1/en
Publication of WO2023131420A1 publication Critical patent/WO2023131420A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W48/00Access restriction; Network selection; Access point selection
    • H04W48/08Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W84/00Network topologies
    • H04W84/02Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04Large scale networks; Deep hierarchical networks
    • H04W84/06Airborne or Satellite Networks

Definitions

  • This description relates to wireless communications.
  • a communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
  • LTE Long Term Evolution
  • APs base stations or access points
  • eNBs enhanced Node AP
  • UE user equipments
  • LTE has included a number of improvements or developments.
  • 5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G & 4G wireless networks.
  • 5G is also targeted at the new emerging use cases in addition to mobile broadband.
  • a goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security.
  • 5G NR may also scale to efficiently connect the massive Internet of Things (loT) and may offer new types of mission-critical services. For example, ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency.
  • URLLC ultra-reliable and low-latency communications
  • a device, a system, a non-transitory computer-readable medium having stored thereon computer executable program code which can be executed on a computer system
  • a method can perform a process with a method including receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping, identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information, and receiving, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
  • SIB system information broadcast
  • Implementations can include one or more of the following features.
  • the method can further include estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
  • the method can further include determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell re-selection information.
  • the cell re-selection information can be associated with at least one of intrafrequency re-selection, inter-frequency re-selection, and inter-RAT re-selection.
  • the UE required assistance information can be associated with reference signal information.
  • the method can further include determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
  • the at least one relevant segment can be determined based on a reference signal’s location in time.
  • the at least one relevant segment can include satellite assistance information.
  • the SIB segment mapping can associate each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
  • a coverage time interval of at least one of the network device and at least one second network device can be based on the coverage time and a movement vector.
  • the SIB segment mapping can indicate a time interval with no network device coverage.
  • the method can further include switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
  • the UE can determine not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
  • the method can further include communicating, by the UE to the network device, a request for the at least one relevant segment.
  • the receiving of the SIB segment mapping can be in response to the communicated request.
  • the SIB segment mapping can be received in a message communicated to one of the UE or a group of identified UEs.
  • the request for the SIB segment mapping can includes information about the UE and the received SIB segment mapping can include a modified mapping based on the information about the UE.
  • a device, a system, a non-transitory computer- readable medium having stored thereon computer executable program code which can be executed on a computer system
  • a method can perform a process with a method including generating, by a network device, a system information broadcast (SIB) segment mapping, broadcasting, by the network device, the SIB segment mapping, generating, by the network device, a plurality of datasets each including network information, and broadcasting, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
  • SIB system information broadcast
  • the network information can include non-terrestrial network (NTN) information.
  • the network information can include at least one of intra-frequency information, interfrequency information, and inter-RAT information.
  • the intra-frequency information can include cell priority
  • the inter-frequency information can include frequency range
  • the inter-RAT information can include a radio access technology (RAT) associated with a neighbor cell.
  • the network information can include a list of reference signal configurations.
  • the SIB segment mapping can be configured to associate an SIB transmission occasion with different datasets and the association of the dataset with the SIB transmission occasion can refer to one of the content of each dataset or a segmenting criteria used for generating of each dataset.
  • the method can further include receiving, by the network device from a user equipment (UE), a request for at least one relevant segment and communicating, by the network device to the UE, the at least one relevant segment in response to the request.
  • the SIB segment mapping can be modified based on information about the UE.
  • the generating of the SIB segment mapping can include generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time, dividing the period of time into a number of segments of equal time duration, associating a subset of the network devices with each of the segments, and including satellite information associated with each of the subset of the network devices in the corresponding segment.
  • the method can further include segmenting at least one block of satellite information based on the SIB segment mapping.
  • FIG. 1 is a block diagram of a wireless network according to an example embodiment.
  • FIG. 2 is a block diagram illustrating a signal flow for segmented system information block segmentation in a network according to an example embodiment.
  • FIG. 3 is a block diagram illustrating a signal flow for segmented system information block segmentation in a non-terrestrial network according to an example embodiment.
  • FIG. 4 is a block diagram illustrating communication of a segmented system information block according to an example embodiment.
  • FIG. 5 is a block diagram of a method illustrating communication of a segmented SIB according to an example embodiment.
  • FIG. 6 is a block diagram of a method illustrating user equipment communication of a segmented SIB according to an example embodiment.
  • FIG. 7 is a block diagram of a method illustrating network device communication of a segmented SIB according to an example embodiment.
  • FIG. 8 is a block diagram of a wireless station or wireless node (e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU- CP, CU-CP, ... or other node) according to an example embodiment.
  • a wireless station or wireless node e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU- CP, CU-CP, ... or other node
  • FIG. 1 is a block diagram of a wireless network 130 according to an example embodiment.
  • user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs) may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a BS, next generation Node B (gNB), a next generation enhanced Node B (ng-eNB), or a network node.
  • AP access point
  • eNB enhanced Node B
  • gNB next generation Node B
  • ng-eNB next generation enhanced Node B
  • ng-eNB next generation enhanced Node B
  • a BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as (e.g., such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS).
  • a BS e.g., access point (AP), base station (BS) or (e)Node B (eNB), BS, RAN node
  • AP access point
  • BS base station
  • eNB Node B
  • BS RAN node
  • RAN node may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head.
  • BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided.
  • BS 134 is also connected to a core network 150 via a SI interface or NG interface 151. This is merely one simple example of a wireless network, and others may be used.
  • a base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network.
  • a BS (or a RAN node) may be or may include (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB), a non-terrestrial network (NTN) device, a satellite repeater, or other terrestrial or non-terrestrial network node.
  • AP access point
  • gNB gNode
  • eNB evolved Node
  • DU distributed unit
  • NTN non-terrestrial network
  • satellite repeater or other terrestrial or non-terrestrial network node.
  • a BS may include: a distributed unit (DU) network entity, such as a gNB-distributed unit (gNB- DU), and a centralized unit (CU) that may control multiple DUs.
  • the centralized unit (CU) may be split or divided into: a control plane entity, such as a gNB-centralized (or central) unit-control plane (gNB-CU-CP), and an user plane entity, such as a gNB-centralized (or central) unit-user plane (gNB-CU-UP).
  • the CU sub-entities may be provided as different logical entities or different software entities (e.g., as separate or distinct software entities, which communicate), which may be running or provided on the same hardware or server, in the cloud, etc., or may be provided on different hardware, systems or servers, e.g., physically separated or running on different systems, hardware or servers.
  • a distributed unit may provide or establish wireless communications with one or more UEs.
  • a DUs may provide one or more cells, and may allow UEs to communicate with and/or establish a connection to the DU in order to receive wireless services, such as allowing the UE to send or receive data.
  • a centralized (or central) unit may provide control functions and/or data-plane functions for one or more connected DUs, e.g., including control functions such as gNB control of transfer of user data, mobility control, radio access network sharing, positioning, session management etc., except those functions allocated exclusively to the DU.
  • CU may control the operation of DUs (e.g., a CU communicates with one or more DUs) over a front-haul (Fs) interface.
  • Fs front-haul
  • a BS node e.g., BS, eNB, gNB, NTN, CU/DU, ...
  • a radio access network may be part of a mobile telecommunication system.
  • a RAN radio access network
  • the RAN (RAN nodes, such as BSs or gNBs) may reside between one or more user devices or UEs and a core network.
  • each RAN node e.g., BS, eNB, gNB, CU/DU, ...
  • BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node.
  • Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and/or receiving data from one or more of the UEs.
  • a RAN node may forward data to the UE that is received from a network or the core network, and/or forward data received from the UE to the network or core network.
  • RAN nodes e.g., BS, eNB, gNB, CU/DU, ...
  • a base station may also be DU (Distributed Unit) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). DU facilitates the access link connection(s) for an IAB node.
  • IAB Integrated Access and Backhaul
  • a user device may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM) (which may be referred to as Universal SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, and a multimedia device, as examples, or any other wireless device.
  • SIM subscriber identification module
  • a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network.
  • a user device may be also MT (Mobile Termination) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). MT facilitates the backhaul connection for an IAB node.
  • IAB Integrated Access and Backhaul
  • core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • EPC Evolved Packet Core
  • MME mobility management entity
  • gateways may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks.
  • 5G which may be referred to as New Radio (NR)
  • NR New Radio
  • 5G/NR New Radio
  • 5G/NR New Radio
  • 5GC New Radio
  • 5G/NR New Radio
  • the various example embodiments or techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types.
  • New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), massive MTC (mMTC), Internet of Things (loT), and/or narrowband loT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC).
  • MTC machine type communications
  • eMTC enhanced machine type communication
  • mMTC massive MTC
  • LoT Internet of Things
  • URLLC ultra-reliable and low-latency communications
  • Many of these new 5G (NR) - related applications may require generally higher performance than previous wireless networks.
  • loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices.
  • many sensor type applications or devices may monitor a physical condition or a status and may send a report to a server or other network device, e.g., when an event occurs.
  • Machine Type Communications MTC, or Machine to Machine communications
  • MTC Machine Type Communications
  • eMBB Enhanced mobile broadband
  • Ultra-reliable and low-latency communications is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems.
  • 5G New Radio
  • 3 GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10' 5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example.
  • BLER block error rate
  • U-Plane user/data plane
  • a URLLC UE may require much shorter latency, as compared to an eMBB UE (or an eMBB application running on a UE).
  • the various example embodiments may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE- A, 5G (New Radio (NR)), cmWave, and/or mmWave band networks, loT, Narrowband loT (NB-IoT), MTC, eMTC, mMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology.
  • LTE Long Term Evolution
  • LTE- A Fifth Generation
  • 5G New Radio
  • cmWave and/or mmWave band networks
  • loT loT
  • Narrowband loT NB-IoT
  • a connected mode e.g., RRC-Connected
  • the UE is connected to a BS/gNB, and the UE may receive data, and may send data (based on receiving an uplink grant).
  • UE mobility may be controlled by the gNB or network.
  • a UE may, for example, transition from a connected state (e.g., RRC Connected) to an unconnected state, such as an Idle state (e.g., RRC Idle) or Inactive state (e.g., RRC Inactive), e.g., in which the UE may sleep (a low power state) much of the time while in Idle or Inactive state.
  • a connected state e.g., RRC Connected
  • an Idle state e.g., RRC Idle
  • Inactive state e.g., in which the UE may sleep (a low power state) much of the time while in Idle or Inactive state.
  • Idle state or Inactive state the UE does not have a connection established with any cell, and mobility (e.g., determining which cell the UE will be camped on or which cell to select as the serving cell for the UE) is controlled by the UE.
  • Inactive state may also be referred to as a suspended state of the UE. While in Idle state or Inactive state, the UE may sleep much of the time, and then periodically wake (e.g., changing from a low power state to a full-power state) to perform one or more tasks or processes, e.g., such as receiving system information from the cell the UE may be camped on (the serving cell for the UE while in Idle state or Inactive state), detecting a paging message (a paging message detected by the UE may indicate that the network has data for downlink transmission to the UE), and/or performing a cell search and cell reselection process in which the UE may measure reference signals from various cells, and then select a cell (or reselect the same cell) to camp on (as the serving cell), based on the received signals from various cells.
  • a paging message a paging message detected by the UE may indicate that the network has data for downlink transmission to the UE
  • cell selection may include selecting a cell that has a strongest reference signal received power (RSRP) and/or reference signal received quality (RSRQ), or other signal parameter.
  • RSRP reference signal received power
  • RSRQ reference signal received quality
  • the serving cell may be referred to as the cell the UE has camped on.
  • a UE may typically receive system information (e.g., via receiving one or more broadcast system information blocks (SIBs)) from the serving cell (or the cell the UE is camping on) while the UE is awake in Idle state or Inactive state.
  • SIBs broadcast system information blocks
  • a UE when a UE is in Idle state, there is no RRC context (the parameters necessary for communication between the UE and network) for the UE stored by the radio access network (BS/gNB) or UE. No uplink synchronization is maintained by the UE, and no data transfer may take place, as the UE sleeps most of the time to conserve battery consumption.
  • the UE may wake periodically to receive paging messages and perform cell reselection, based on reference signal measurements. UE mobility is handled by the UE via cell reselection.
  • An uplink transmission that may be performed by the UE in Idle mode is the random access (RACH) procedure or messages, that may be used for the UE to transition from Idle state to Connected state with respect to a cell or gNB.
  • RACH random access
  • Inactive state (at least some) RRC context for the UE is stored at both the UE and the gNB, e.g., to allow the UE to more quickly transition from Inactive state to Connected state, e.g., since at least some RRC context for the UE may already be in place at the UE and the gNB (e.g., such as an inactive-radio network temporary identifier (I-RNU) assigned to the UE).
  • I-RNU inactive-radio network temporary identifier
  • the Inactive UE is allowed to sleep (or enter a low power state), and periodically wake to receive paging messages and/or perform cell reselection, e.g., in a same or similar manner as I
  • a satellite constellation can provide discontinuous coverage on Earth using sparse satellite constellations.
  • satellite constellations can include a satellite configured to provide coverage to a certain area for some time after which there will be a period, where there is no NTN coverage in the area.
  • the satellite availability time and the time between satellite availability depends on the UE location and the satellite constellation, the radiofrequency beam pointing by the satellite, and both time intervals will also vary due to Earth rotation.
  • Discontinuous coverage can impact both connected (e.g., RRC Connected) and idle (e.g., RRC Idle) UEs.
  • Connected UE(s) may need enhancement to declare Radio Link Failure fast when the satellite has disappeared and to not continue cell search.
  • Idle UE(s) can save energy if the UE(s) know when to search for the next cell and when to monitor for paging (e.g., when there is coverage). Both scenarios can benefit from knowledge about when coverage appear s/disappears in the specific area.
  • Satellite assistance e.g., ephemeris information
  • broadcast system information e.g., PCI and frequency information
  • UE location information can be used to help UE(s) in an loT NTN system perform measurement and cell selection and/or reselection.
  • Satellite assistance information e.g., ephemeris information
  • the UE(s) can be configured to predict discontinuous coverage based on the satellite assistance information. If possible (or reasonable), the UE(s) may not attempt to camp or connect when there is no satellite coverage. If possible (or reasonable), the network may not try to reach UE(s), that are out of coverage.
  • Implementations can include a configuration where the UE and the network can be synchronized when the UE is active (e.g., awake) and reachable (e.g., for paging). Provisioning of satellite assistance information can be performed using System Information (SI) message(s) for loT NTN.
  • SI System Information
  • the ephemeris and assistance information can be provided using System Information (SI) message(s) for loT NTN, can be used for the handling of coverage holes or discontinuous satellite coverage power efficiently, and can be used to predict discontinuous coverage.
  • SI System Information
  • the ephemeris and assistance information can also be used for power savings in idle mode for NTN IOT devices and to relaxed monitoring and SI acquisition.
  • the ephemeris information is heavy in terms of overhead (approximately 17-18 bytes).
  • other information e.g., frequency of transmission for different carriers, doppler compensation, PLMNs, and/or the like
  • Example implementations can provide relaxed and power efficient monitoring of SI information for UEs with limited energy constraints (e.g., NB-IoT), enable prediction of discontinuous coverage for different long DRX settings, and minimize the massive overhead in the SI payload.
  • energy constraints e.g., NB-IoT
  • An example implementation can enable flexibility for a BS in terms of overhead associated with assistance information provided in NTN System Information (SI) messages, updates, and the like.
  • the example implementation can split information from a SI message (NTN System Information Block (SIB) or SIB containing NTN data) data across multiple SI transmit occasions.
  • SIB SI message
  • SIB containing NTN data SIB containing NTN data
  • the example implementation can provide rules that enables the UE to determine how the information of one SI message is distributed in the different SI occasions by providing support for UE selection of SI occasions to monitor.
  • UEs that are in the connected mode can request a dedicated transmission of the System Information Block (SIB). For example, the request can be for selected segments of the SI message, and not for the entire SI message.
  • SIB System Information Block
  • the BS can be broadcasting one SIB with NTN related information, one NTN-specific SIB, or one dedicated neighbor-satellite NTN SIB, such that the information associated with a neighbor satellite is transmitted.
  • Each entry on the neighbor-satellite information can correspond to a different satellite and/or a different passing of a same satellite.
  • the neighbor-satellite information can also include descriptors for an orbit that may be common for several satellites.
  • Some specifications can provide a dedicated SIB request procedure, where UEs can receive and/or require, via RRC, the contents of a given SIB message.
  • FIG. 2 is a block diagram illustrating a signal flow for segmented system information block segmentation in a network according to an example embodiment.
  • a network e.g., a terrestrial network, a non-terrestrial network (NTN), and/or the like
  • UE user equipment
  • NTN non-terrestrial network
  • the network device(s) 210 can be a combination of devices.
  • the network device(s) 210 can represent a base station (BS), a gNB, an eNB, an NTN device, an NTN device and a core network device (or entity), the network device(s) 210 can represent an NTN device and an NTN control device (or entity), the network device(s) 210 can represent a terrestrial base station, a base station onboard a satellite, a satellite as a repeater, and any other similar combination of NTN devices and/or terrestrial network devices.
  • a single device and/or the combination of devices can sometimes be referred to as a network device, a network system, and/or the like.
  • the UE 205 can be a user device, a user terminal, a mobile device, a stationary device, an internet of things (loT) device, a narrowband (NB) loT device , any wirelessly (or cellular) connected device, and/or the like.
  • LoT internet of things
  • NB narrowband
  • an SIB occasion is divided into a number of SIB segments by the network device 210.
  • the above mentioned period of time e.g., 16, 24, 36, hours and the like
  • a valid dataset of network (e.g., NTN) devices can be divided into segments of equal time duration (e.g., 1, 2, 4, hours and the like).
  • an SIB can include cell re-selection information used for intra-frequency, inter-frequency, and/or inter-RAT cell re-selection.
  • the SIB can be divided into, for example, three (3) segments.
  • a first SIB segment can include intra-frequency information
  • a second SIB segment can include inter-frequency
  • a third SIB segment can include inter-RAT information.
  • a UE e.g., a RRC Idle UE
  • a list of reference signals e.g., CSI-RS
  • the list of reference signals could be segmented into subsets of reference signals and the UE can be configured to receive one or more subset of reference signals.
  • the UE may only support a subset of the frequencies and RATs that are listed in the SIB. Therefore, the UE can be configured to determine a subset of relevant cell re-selection information based on UE capability (e.g., frequency band and RAT support).
  • each SIB segment can be transmitted (block 235) in a same and/or different SIB occasions.
  • the SIB segments can include, for example, satellite information (e.g., satellite availability for wireless service to a coverage area, cell re-selection information, reference signal information, and/or the like.
  • the SIB segment mapping can be configured to map network information (e.g., network information useful for a UE operation).
  • the SIB segment mapping can map an SIB segment to network information including, for example, a satellite available for wireless service to a coverage area at (or over) a time period, cell re-selection information, reference signal information, and/or the like.
  • SIB segment mapping may be valid for a period of time (e.g., 2, 4, 8, 16, 24, 36, hours and the like).
  • the network device 210 can communicate (e.g., broadcast) a message (block 325) that is received by the UE 205.
  • the message can include the SIB segment mapping.
  • the UE 205 can use the SIB segment mapping to identify segment(s) of an SIB occasion. More specifically, in block 240, the UE 205 can identify relevant segment(s) of an SIB occasion based on the SIB segment mapping and a network requirement(s).
  • the relevant segment(s) of the SIB occasion can be the SIB segments that indicate (or may indicate, or may include) network information (e.g., network information useful for a UE operation) of interest to the UE 205.
  • dataset(s) including network information is generated by the network device 210.
  • the dataset(s) can include network information corresponding a satellite in a satellite constellation, cell re-selection information, reference signal information, and/or the like.
  • the network information can include nonterrestrial network (NTN) information such as, for example, a satellite ephemeris, K offset, K mac, common delay (and potentially the first, second and third order parameters), doppler pre-compensation, and/or the like.
  • NTN nonterrestrial network
  • the network information can include intra-frequency information, inter-frequency information, and/or inter-RAT information.
  • the intra-frequency information can include cell priority (e.g., top priority cells can be in a first segment, lower priority cells can be in a second segment, and lowest priority cells can be in a third segment),
  • the inter-frequency information can include frequency range(s) that can be segmented according to frequency layers (e.g., frequency range 0 - 2 GHz in a first segment, 2 - 4 GHz in a second segment, 4 - 6 GHz in a third segment, and the like)
  • the inter-RAT information can include a radio access technology (e.g., 5GNR, 4GLTE, 4G GSM, 3G, 2G, WI-FI, and the like) associated with a neighbor cell and.
  • the network information can include a subset(s) of reference signals.
  • the network device 210 can be configured to divide a list of reference signals into subset(s) of reference signals and the network information can include one or more subset(s) of reference signals and the corresponding reference signal configuration.
  • the network information can be based on reference signal time location and spatial domain and the UE could determine which segments are relevant segment(s) based on how the reference signals are located in time, spatial domain (e.g., selecting CSI-RS that are transmitted in the UE’s current and neighbor beams), and/or the like.
  • a subset of a system information message including the relevant segments is received (e.g., processed) by the UE 205 based on the SIB segment mapping.
  • the UE 205 can ignore (e.g., not receive, not process) the remainder (e.g., not relevant) segments.
  • the relevant segments can include all of the necessary data or information. Therefore, the UE 205 can process the relevant segment without waiting for any other SIB occasions. In other words, the UE 205 can begin processing the relevant segment as soon as the reception of the relevant segment is completed.
  • NTN non-terrestrial network
  • these elements, components, devices, functions, operations, and/or the like can be applicable to other types of network (e.g., terrestrial network) elements, components, devices, functions, operations, and/or the like even should this not be explicitly stated when referring to these elements, components, devices, functions, operations, and/or the like.
  • FIG. 3 is a block diagram illustrating a signal flow in a non-terrestrial network according to an example embodiment.
  • a non-terrestrial network includes a user equipment (UE) 305 and a network device(s) 310.
  • the network device(s) 310 can be a combination of devices.
  • the network device(s) 310 can represent an NTN device and a core network device (or entity)
  • the network device(s) 310 can represent an NTN device and an NTN control device (or entity)
  • the network device(s) 310 can represent a base station onboard a satellite, a satellite as a repeater and a terrestrial base station, and any other similar combination of NTN devices and/or terrestrial network devices.
  • the UE 305 can be a user device, a user terminal, a mobile device, a stationary device, an internet of things (loT) device, any wirelessly (or cellular) connected device, and/or the like.
  • LoT internet of things
  • a dataset of network (e.g., NTN) devices that are relevant for a coverage area is generated by the network device 310.
  • the dataset of network devices can be valid for a period of time (e.g., 16, 24, 36, hours and the like).
  • the network device 310 can identify network device(s) (possibly including network device 310) that can be configured to provide wireless service to a coverage area (e.g., cell 136) and/or a plurality of cells and when the identified network devices can provide the wireless service to the coverage area.
  • Example implementations can include satellite constellations configured to provide discontinuous coverage on Earth using sparse satellite constellations.
  • satellite constellations can include a satellite configured to provide coverage to a certain area for some time after which there will be a period, where there is no NTN coverage in the area.
  • the satellite availability time and the time between satellite availability depends on the UE location and the satellite constellation, and both time intervals will also vary due to Earth rotation.
  • the dataset of network (e.g., NTN) devices can be generated based on information about the satellites in a satellite constellation, the satellite availability time, and the time between satellite availability.
  • the satellite availability time, and the time between satellite availability can be based on satellite(s) coverage time(s) and satellite movement vector(s) (that can take into consideration the rotation of the Earth).
  • the mapping of satellite position to a coverage can include, for example, the UE and/or network can determine the coverage on earth for a given satellite based on information about the satellite’s footprint (e.g., a circle below the satellite (circle center is linked to nadir of satellite) with a given radius) and/or based on the minimum elevation angle (e.g., if the angle between UE and satellite is above the minimum there is likely radio coverage).
  • satellites may not provide coverage on the exact same area. Instead, satellites may only have a partial overlap.
  • the network device may filter such that only satellites provide 50 % (X) overlapping coverage with the current coverage are included in the SI.
  • a period of time is divided into a number of segments of equal time duration by the network device 310.
  • the above mentioned period of time e.g., 16, 24, 36, hours and the like
  • a valid dataset of network (e.g., NTN) devices can be divided into segments of equal time duration (e.g., 1, 2, 4, hours and the like).
  • the segments can be referred to as SIB segments.
  • each SIB segment can be transmitted (block 355) in different SIB occasions.
  • an SIB segment mapping is generated by the network device 310.
  • the SIB segments e.g., the segments of equal time duration
  • the SIB segment mapping can be configured to map a satellite to an SIB segment.
  • the SIB segment mapping can map an SIB segment to a satellite available for wireless service to a coverage area at (or over) a time period. SIB segment mapping may be valid for the period of time (e.g., 16, 24, 36, hours and the like) discussed above.
  • a network connection time requirement(s) for the UE 305 is determined by the UE 305.
  • the network connection time requirement(s) can be based on a next time(s) that the UE 305 may need a wireless connection to, for example, upload/download data, communicate/receive a message, monitor for paging, and/or the like.
  • the network connection time requirement(s) can be a time, a time period, a time window, and/or the like that UE 305 may be (should be, may need to be) in an active state (e.g., awake and/or monitoring for paging) as opposed to an inactive state (e.g., asleep).
  • the network device 310 can communicate (e.g., broadcast) a message (block 335) that is received by the UE 305.
  • the message can include the SIB segment mapping (as generated in block 325).
  • the UE 305 can use the SIB segment mapping to identify segment(s) of an SIB occasion. More specifically, in block 340, the UE 305 can identify relevant segment(s) of an SIB occasion based on the SIB segment mapping and the network connection state time requirement(s).
  • the relevant segment(s) of the SIB occasion can be the SIB segments that indicate (or may indicate) a satellite available for wireless service to a coverage area including the UE 305 when the UE 305 should be in an active state and needs or may need a wireless connection.
  • sub-dataset(s) including NTN information is generated by the network device 310.
  • the sub-dataset(s) can be portions of the dataset of network devices.
  • each sub-dataset includes NTN information corresponding to a network device (e.g., a satellite in the satellite constellation configured to provide discontinuous coverage).
  • the NTN information can be a satellite ephemeris, K offset, K mac, common delay (and potentially the first, second and third order parameters), doppler pre-compensation, and/or the like.
  • segmented system information messages can be individually broadcasted by the network device 310.
  • Each segmented system information message can include at least one of the sub-datasets.
  • the sub-dataset(s) that are included in a segmented system information message can be based on the SIB segment mapping.
  • a subset of a system information message including the relevant segments is received (e.g., processed) by the UE 305 based on the SIB segment mapping.
  • the UE 305 can ignore (e.g., not receive, not process) the remainder (e.g., not relevant) segments.
  • the relevant segments can include all of the necessary data or information. Therefore, the UE 305 can process the relevant segment without waiting for any other SIB occasions. In other words, the UE 305 can begin processing the relevant segment as soon as the reception of the relevant segment is completed.
  • the UE 305 can switch from an inactive state to an active state based on information associated with a coverage time of an NTN device included in the relevant segment(s). For example, in a time period (e.g., +6 to +8 hours) associated with a relevant segment, the UE 305 can switch to an active state. The UE 305 can then, for example, receive and/or communicate (block 365) a message to and/or from the NTN device associated with the relevant segment.
  • a time period e.g., +6 to +8 hours
  • the UE 305 can connect (e.g., RRC_Connected) with the NTN device (that may or may not include network device 310) associated with the relevant segment and communicate the message. If the UE 305 is to receive a message from the NTN device associated with the relevant segment, the UE 305 can receive the message with or without connecting to the NTN device associated with the relevant segment.
  • RRC_Connected e.g., RRC_Connected
  • FIG. 4 is a block diagram illustrating communication of a segmented system information block (SIB) according to an example embodiment.
  • SIB system information block
  • a number of satellites 410 can be expected to cover a given area at some point in different time intervals 405.
  • there is irregular coverage and at some intervals one satellite is expected (e.g., between T and 2T).
  • two intervals where more than one satellite is expected e.g., two between 0 and T and three between 2T and 3T. Not shown is the possibility that in some intervals zero satellites may be expected.
  • SIB occasion 415-A shows an SIB that includes an NTN info segment, an A segment, a B segment, and a C segment.
  • the A segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 0 and T.
  • the B segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between T and 2T.
  • the C segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 2T and 3T.
  • SIB occasions 415-B and 415-C each show an SIB that includes the same segments as SIB occasion 415-A.
  • the same SIB is repeatedly transmitted with some SIB transmission periodicity.
  • the UE may determine only to receive segment 415-B if the associated interval T to 2T fits the future communication needs of the UE.
  • SIB occasion 420-A shows an SIB that includes an NTN info segment and the A segment
  • SIB occasion 420-B shows an SIB that includes an NTN info segment and the B segment
  • SIB occasion 420-C shows an SIB that includes an NTN info segment and the C segment.
  • the A segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 0 and T.
  • the B segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between T and 2T.
  • the C segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 2T and 3T.
  • the first implementation may trigger a system information update indication to the UE(s), whereas the second implementation does not trigger a system information update indication to the UE(s).
  • the NTN info segment may include information associated with the current satellite and/or cell and may be an optional segment.
  • An example implementation can enable flexibility for a BS in terms of overhead associated with assistance information provided in NTN System Information (SI) messages, updates, and the like.
  • the example implementation can split information from a SI message (NTN System Information Block (SIB) or SIB containing NTN data) data across multiple SI transmit occasions.
  • SIB NTN System Information Block
  • the example implementation can provide rules that enables the UE to determine how the information of one SI message is distributed in the different SI occasions by providing support for UE selection of SI occasions to monitor.
  • the implementation framework can also provide that the different SI segments (e.g., different to each other) can be transmitted without triggering SI modifications. Not triggering SI modifications, can be advantageous by saving power in that SI modifications can require UEs camped or connected to the cell to reacquire all Sis (or reacquire according to systemlnfoValueTagSI if used).
  • the network device can estimate, using, for example, a satellite control center assistance, a full list of information of satellites or the passing of satellites that are relevant for the current coverage area.
  • This full list can be called the dataset.
  • the segments can be called or include sub-datasets.
  • Each sub-dataset can be transmitted in different SIB occasions.
  • the most optimistic SIB assumption could be only the first three (3) satellites. In this example, it means that no prediction can be made past 2T, using the maximum transport block size, which is likely not enough for loT devices with long DRX or PSM active. Therefore, the loT device could become active (e.g., wake-up) with no satellite in range (e.g., in the dark).
  • the satellite may need to proceed with new scanning to find suitable satellites or may need to wake up early to acquire information about the next T (e.g., from 2T to 3T).
  • T e.g., from 2T to 3T.
  • SIB1 which is a pointer for the other SIBs
  • SIB containing information assistance for neighbor-satellites a new set of parameter(s) can be introduced.
  • the parameters can be, for example, a time window size for a SIB segment, size of sequence (or number of SIB segments), a modification interval for SIB segment(s), and/or a version number of the current transmission or the start point of the dataset.
  • the modification interval for SIB segment(s) can be the period for the transmission of one SIB segment in the SI. For example, if the modification interval is set equal to one Si-Window then one SIB segment is transmitted in all SIB occasions within the Si-Window. In the next SI window, the SIB version associated to the next segment of time is transmitted.
  • the version number of the current transmission or the start point of the dataset can indicate the SIB segment index for the current SIB occasion (ex: 3 of 9, if the third segment out of nine is being transmitted in the current SIB version). Or the starting point of the data set (in SFN, SIB occasion or else).
  • the version can allow the UE to traceback the occasion for each segment. From the UE point of view, after reading one SIB occasion, the UE can determine to which segment of time each SIB transmission corresponds. The UE can estimate the segment of times that are relevant for the next UE active (e.g., wake-up) times.
  • UEs that are in the connected mode can request a dedicated transmission of the System Information Block (SIB).
  • SIB System Information Block
  • the BS can be broadcasting one SIB with NTN related information, one NTN-specific SIB, or one dedicated neighbor-satellite NTN SIB, such that the information associated with a neighbor satellite is transmitted.
  • Each entry on the neighbor-satellite information can correspond to a different satellite and/or a different passing of a same satellite.
  • the neighbor-satellite information can also include descriptors for an orbit that may be common for several satellites.
  • Some specifications can provide a dedicated SIB request procedure, where UEs can require, via RRC, the contents of a given SIB message. For example, for a UE in RRC CONNECTED, the network can provide system information through dedicated signaling using the RRCReconfiguration message (e.g., if the UE has an active BWP with no common search space configured to monitor system information or paging).
  • an example implementation can be implemented via RRCSystemlnfoRequest message.
  • the UE configures the requested- Si-List or contains a list of requested SI messages.
  • first bit corresponds to first/leftmost listed SI message
  • second bit corresponds to second listed SI message, and so on.
  • example implementations can include modifications on this procedure, to provide solution for different scenarios.
  • the UE may provide a list of segments the UE is interested in. Or request for the full contents (full dataset of SIB). For example, if the bit corresponding to the SI that contains the neighbor cell list (e.g., called SI nl) in requested-SI-List is set enabled, this enables an additional parameter (e.g., requested-segments-SI nl-list). One bit can represent each segment in this case.
  • the network may limit the number of requests for the full list or parts of the list. The request can be made available for power harvesting UEs and not for other UEs.
  • the network may not need to repeat the common information of every SI nl version, but just append the list of different segments at the end of the first version transmitted in RRC response.
  • the request may be relative only to the neighbor cell list within SI nl, if other NTN is also part of the same SI.
  • the network can be configured to determine to reply a UE request using the group identity (e.g., G-RNTI), when the UE is part of a group, such that the whole group can have access to one information via one request only, minimizing possible overheads.
  • group identity e.g., G-RNTI
  • some (or even most) intervals may not contain relevant satellites. Therefore, the sequence definition may also contain indication of which intervals do not have a satellite (e.g., are empty) and these datasets are skipped from the calculations. The calculations of active (e.g., wake-up) time intervals at the UE side are done accordingly.
  • the multiple repetitions of a SIB within a SI- window are assumed to be the same, as they may be used for different SSB (beams). But, in case of quasi-collocated or collocated beams, or the case where the NTN SIB is repeated across all beams, one alternative implementation possible may be that each SI occasion conveys a different SIB segment within the same Si-window.
  • the SIB segments are not provided sequentially, but instead in a prioritized order.
  • the network may provide sets 1 and 2, which define the most imminent coverage opportunities, more frequently than the remaining sets. Potential sequences could be ⁇ 1, 2, 3, 1, 2, 4, 1, 2, 5, 1, 2, 6 ⁇ and ⁇ 1, 3, 2, 4, 1, 5, 2, 6 ⁇ .
  • FIG. 5 is a block diagram of a method illustrating communication of a segmented SIB in a UE according to an example embodiment.
  • delay requirements are determined.
  • the delay requirements can be based on and/or include QoS, paging, UL data, and/or the like.
  • the UE can be a narrowband (NB) loT device.
  • the NB loT device can have minimum QoS requirements and paging requirements in order to communicate with a network device.
  • a network connection should be available for communication (UL and/or DL) in four (4) hour increments (e.g., every other time.
  • a network connection should be available for paging daily (e.g., once in a 24 hour span). Therefore, a delay requirement for the UE can be 24 hours (or a range, e.g., every 20 to 30 hours). Other delay requirements (e.g., for the same or additional applications) may also need to be met.
  • step S510 when a connection is needed is estimated based on delay requirements.
  • the delay requirements can include (or indicate) times (e.g., a range of time, time increments, and/or the like).
  • the delay requirements can be based on, for example, a QoS associated with connection requirements. Therefore, when a connection is needed can be based on the included (or indicated) times (e.g., a range of time, time increments, and/or the like).
  • connections can be needed in four (4) hour increments (e.g., every 3.5 to
  • an SIB configuration of multiple segments is received.
  • an SIB segment mapping can be received from a network device (e.g., a serving satellite).
  • SIB segments e.g., the segments of equal time duration
  • the SIB segment mapping can be configured to map a satellite to an SIB segment.
  • the SIB segment mapping can map an SIB segment to a satellite available for wireless service to a coverage area at (or over) a time period.
  • the UE can consider UE movement.
  • the UE can estimate location at a future point in time such that the UE can determine if the coverage of the future satellites is available also at that future location.
  • SIB segment mapping may be valid for the period of time (e.g., 16, 24, 36, hours and the like) discussed above.
  • step S520 relevant segment(s) of the SIB are identified based on when the connection is needed, and coverage is available.
  • a plurality of satellites can be available to a coverage area over a time period (e.g., available every ’/ 2 hour, available non-incrementally, with some availability and some non-availability, and/or the like).
  • An SIB can be used to indicate the availability of each of the plurality of satellites. Therefore, the SIB segment mapping can be used to identify the relevant segment(s) of the SIB.
  • the SIB segment mapping can be used to identify the broadcasted SIB segments to process.
  • some SIB segments can be processed (e.g., received) and some SIB segments can be ignored (e.g., not processed, not received) based on the identified (SIB segments to be processed) SIB segments and the SIB segment mapping (some indication of when, which, an order, and/or the like) of the broadcasted SIB segments.
  • the UE can complete the processing of the received SIB segment without waiting for another (e.g., to be received or processed) SIB segment.
  • step S530 the UE (optionally) becomes active (sometimes referred to as waking up) according to coverage indicated by received segment(s).
  • the QoS of an application (and/or a plurality of applications) executing on the UE can include a requirement for when a network connection should be available. Therefore, the UE can switch to an active mode to perform the process associated with the QoS of the application(s) using the information (e.g., coverage) received in a relevant SIB segment.
  • the UE may or may not connect to the satellite serving the coverage area.
  • to communicate and/or receive data e.g., via an UL/DL connection
  • the UE can connect with the satellite serving the coverage area.
  • the UE is to receive broadcast or paging data, there may be no need for the UE to connect with the satellite serving the coverage area.
  • the ephemeris and assistance information can be provided using System Information (SI) message(s) for loT NTN, can be used for the handling of coverage holes or discontinuous satellite coverage power efficiently, and can be used to predict discontinuous coverage.
  • SI System Information
  • the ephemeris and assistance information can also be used for power savings in idle mode for NTN IOT devices and to relaxed monitoring and SI acquisition.
  • the ephemeris information is heavy in terms of overhead (approximately 17-18 bytes).
  • other information e.g., frequency of transmission for different carriers, doppler compensation, PLMNs, and/or the like
  • the neighbor cell information is expected to be signaled in the same NTN SI as other NTN specific information: serving satellite ephemeris, K offset, K mac, common delay (and potentially the first, second and third order parameters), doppler pre-compensation and others.
  • serving satellite ephemeris K offset
  • K mac common delay
  • doppler pre-compensation doppler pre-compensation and others.
  • the 3GPP specifications clarify in TS 38.331, Section 5.2.1, “The physical layer imposes a limit to the maximum size a SIB can take.
  • the maximum SIB1 or SI message size is 2976 bits.”. In total, the maximum SI size allowed is 372 bytes (2976 bits).
  • the space left for broadcasting neighbor satellite information would allow the broadcasting of 12-16 satellites’ information, with the caveats about loss of precision associated with transmitting basic instantaneous orbital information only: in the order of -20 seconds for prediction windows of -12 hours, up to -230 seconds for prediction windows of -84 hours.
  • the UE(s) are already more sensitive to power constraints than a regular UE.
  • the UE(s) may rely on repetitions to acquire information, which may lead to the time to receive the SIB is prolonged (especially for cell edge users) the larger the payload is, therefore impacting the power consumption.
  • the loT technologies (NB-IoT and eMTC) have a reduced maximum transport block size.
  • the 36.331 states on Section 5.2.1, “For BL UEs and UEs in CE, the maximum SIB and SI message size is 936 bits.
  • the maximum SIB and SI message size is 680 bits.”
  • the limit of 680 bits would be at the best-case scenario large enough to convey the ephemeris for only five (5) satellites. However, even five (5) satellites might be unrealistic. For example, the times for “switching on and off’ the signal transmission from the satellite in an area can require additional overhead on top of interference. This limited number of information, in certain scenarios, would not be able to provide information far away in the future, for example, for a UE expected to estimate coverage one day in the future due to long extended DRX settings (loT devices) or PSM (Power Saving Mode). And even if the cases where multiple satellites are reported in NR, it may not be an efficient resource usage reserving a heavy overhead of 2976 bits that is frequently transmitted in the NTN SI, specially considering that the NTN already tends to less efficient PHY usage.
  • FIG. 6 is a block diagram of a method illustrating user equipment communication of a segmented SIB according to an example embodiment.
  • the method including, in step S610 receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping.
  • SIB system information broadcast
  • step S620 identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information.
  • Example 2 The method of Example 1 can further include estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
  • Example 3 The method of Example 1 can further include determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell re-selection information.
  • Example 4 The method of Example 3, wherein the cell re-selection information can be associated with at least one of intra-frequency re-selection, interfrequency re-selection, and inter-RAT re-selection.
  • Example 5 The method of Example 1, wherein the UE required assistance information can be associated with reference signal information.
  • Example 6 The method of Example 5 can further include determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
  • Example 7 The method of Example 5 or example 6, wherein the at least one relevant segment can be determined based on a reference signal’s location in time.
  • Example 8 The method of Example 1, wherein the at least one relevant segment can include satellite assistance information.
  • Example 9 The method of any of Example 1 to Example 8, wherein the SIB segment mapping can associate each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
  • Example 10 The method of Example 9, wherein a coverage time interval of at least one of the network device and at least one second network device can be based on the coverage time and a movement vector.
  • the position vector, the movement vector, and/or orbital information can be included in an ephemeris associated with at least one satellite. Orbital information can be used in addition to and/or in place of a movement vector to determine a coverage time interval.
  • Example 11 The method of any of Example 1 to Example 10, wherein the SIB segment mapping can indicate a time interval with no network device coverage.
  • Example 12 The method of any of Example 1 to Example 11 can further include switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
  • Example 13 The method of any of Example 1 to Example 12, wherein the UE determines not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
  • Example 14 The method of any of Example 1 to Example 13 can further include communicating, by the UE to the network device, a request for the at least one relevant segment.
  • Example 15 The method of Example 14, wherein the receiving of the SIB segment mapping can be in response to the communicated request.
  • Example 16 The method of Example 15, wherein the SIB segment mapping can be received in a message communicated to one of the UE or a group of identified UEs.
  • Example 17 The method of any of Example 14 to Example 16, wherein the request for the SIB segment mapping can includes information about the UE and the received SIB segment mapping can include a modified mapping based on the information about the UE.
  • FIG. 7 is a block diagram of a method illustrating network device communication of a segmented SIB according to an example embodiment.
  • the method including, in step S710 generating, by a network device, a system information broadcast (SIB) segment mapping.
  • SIB system information broadcast
  • step S720 broadcasting, by the network device, the SIB segment mapping.
  • step S730 generating, by the network device, a plurality of datasets each including network information.
  • step S740 broadcasting, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
  • Example 19 The method of Example 18, wherein the network information can include non-terrestrial network (NTN) information.
  • NTN non-terrestrial network
  • Example 20 The method of Example 18, wherein the network information can include at least one of intra-frequency information, inter-frequency information, and inter-RAT information.
  • Example 21 The method of Example 20, wherein the intra-frequency information can include cell priority, the inter-frequency information can include frequency range, and the inter-RAT information can include a radio access technology (RAT) associated with a neighbor cell.
  • RAT radio access technology
  • Example 22 The method of Example 18, wherein the network information can include a list of reference signal configurations.
  • Example 23 The method of Example 18, wherein the SIB segment mapping can be configured to associate an SIB transmission occasion with different datasets and the association of the dataset with the SIB transmission occasion can refer to one of the content of each dataset or a segmenting criteria used for generating of each dataset.
  • Example 24 The method of Example 18 can further include receiving, by the network device from a user equipment (UE), a request for at least one relevant segment and communicating, by the network device to the UE, the at least one relevant segment in response to the request.
  • UE user equipment
  • Example 25 The method of Example 18, wherein the SIB segment mapping can be modified based on information about the UE.
  • Example 26 The method of any of Example 18 to Example 25, wherein the generating of the SIB segment mapping can include generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time, dividing the period of time into a number of segments of equal time duration, associating a subset of the network devices with each of the segments, and including satellite information associated with each of the subset of the network devices in the corresponding segment.
  • Example 27 The method of any of Example 18 to Example 25 can further include segmenting at least one block of satellite information based on the SIB segment mapping.
  • Example 28 A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of Examples 1-27.
  • Example 29 An apparatus comprising means for performing the method of any of Examples 1-27.
  • Example 30 An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of Examples 1 -27.
  • FIG. 8 is a block diagram of a wireless station 800 or wireless node or network node 800 according to an example embodiment.
  • the wireless node or wireless station or network node 800 may include, e.g., one or more of an AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-UP, ... or other node) according to an example embodiment.
  • the wireless station 800 may include, for example, one or more (e.g., two as shown in FIG. 8) radio frequency (RF) or wireless transceivers 802A, 802B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals.
  • the wireless station also includes a processor or control unit/entity (controller) 804 to execute instructions or software and control transmission and receptions of signals, and a memory 806 to store data and/or instructions.
  • Processor 804 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein.
  • Processor 804 which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 802 (802A or 802B).
  • Processor 804 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 802, for example).
  • Processor 804 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above.
  • Processor 804 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these.
  • processor 804 and transceiver 802 together may be considered as a wireless transmitter/receiver system, for example.
  • a controller (or processor) 808 may execute software and instructions, and may provide overall control for the station 800, and may provide control for other systems not shown in FIG. 8, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 800, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
  • a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 804, or other controller or processor, performing one or more of the functions or tasks described above.
  • RF or wireless transceiver(s) 802A/802B may receive signals or data and/or transmit or send signals or data.
  • Processor 804 (and possibly transceivers 802A/802B) may control the RF or wireless transceiver 802A or 802B to receive, send, broadcast or transmit signals or data.
  • the example embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems.
  • Another example of a suitable communications system is the 5G system. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Example embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them.
  • Example embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers.
  • Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium.
  • Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and/or programs and/or software embodiments that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks.
  • embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
  • MTC machine type communications
  • IOT Internet of Things
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program.
  • carrier include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • example embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities).
  • CPS may enable the embodiment and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations.
  • ICT devices sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.
  • a computer program such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment.
  • a computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
  • Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
  • FPGA field programmable gate array
  • ASIC application-specific integrated circuit
  • processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset.
  • a processor will receive instructions and data from a read-only memory or a random access memory or both.
  • Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data.
  • a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks.
  • Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.
  • semiconductor memory devices e.g., EPROM, EEPROM, and flash memory devices
  • magnetic disks e.g., internal hard disks or removable disks
  • magneto-optical disks e.g., CD-ROM and DVD-ROM disks.
  • the processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
  • embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer.
  • a display device e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor
  • a user interface such as a keyboard and a pointing device, e.g., a mouse or a trackball
  • Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
  • Example embodiments may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such back-end, middleware, or front-end components.
  • Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
  • LAN local area network
  • WAN wide area network

Abstract

Various techniques are provided for a method including receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping, identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information, and receiving, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.

Description

EFFICIENT USAGE OF SI SIGNALLING FOR NEIGHBOR SATELLITE INDICATION IN SPARSE COVERAGE SCENARIOS
TECHNICAL FIELD
[0001] This description relates to wireless communications.
BACKGROUND
[0002] A communication system may be a facility that enables communication between two or more nodes or devices, such as fixed or mobile communication devices. Signals can be carried on wired or wireless carriers.
[0003] An example of a cellular communication system is an architecture that is being standardized by the 3rd Generation Partnership Project (3GPP). A recent development in this field is often referred to as the long-term evolution (LTE) of the Universal Mobile Telecommunications System (UMTS) radio-access technology. E- UTRA (evolved UMTS Terrestrial Radio Access) is the air interface of 3GPP's Long Term Evolution (LTE) upgrade path for mobile networks. In LTE, base stations or access points (APs), which are referred to as enhanced Node AP (eNBs), provide wireless access within a coverage area or cell. In LTE, mobile devices, or mobile stations are referred to as user equipments (UE). LTE has included a number of improvements or developments. Aspects of LTE are also continuing to improve.5G New Radio (NR) development is part of a continued mobile broadband evolution process to meet the requirements of 5G, similar to earlier evolution of 3G & 4G wireless networks. 5G is also targeted at the new emerging use cases in addition to mobile broadband. A goal of 5G is to provide significant improvement in wireless performance, which may include new levels of data rate, latency, reliability, and security. 5G NR may also scale to efficiently connect the massive Internet of Things (loT) and may offer new types of mission-critical services. For example, ultra-reliable and low-latency communications (URLLC) devices may require high reliability and very low latency.
SUMMARY
[0004] In a general aspect, a device, a system, a non-transitory computer-readable medium (having stored thereon computer executable program code which can be executed on a computer system), and/or a method can perform a process with a method including receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping, identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information, and receiving, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
[0005] Implementations can include one or more of the following features. For example, the method can further include estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement. The method can further include determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell re-selection information. The cell re-selection information can be associated with at least one of intrafrequency re-selection, inter-frequency re-selection, and inter-RAT re-selection. The UE required assistance information can be associated with reference signal information. The method can further include determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals. The at least one relevant segment can be determined based on a reference signal’s location in time. The at least one relevant segment can include satellite assistance information.
[0006] The SIB segment mapping can associate each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device. A coverage time interval of at least one of the network device and at least one second network device can be based on the coverage time and a movement vector. The SIB segment mapping can indicate a time interval with no network device coverage. The method can further include switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment. The UE can determine not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment. The method can further include communicating, by the UE to the network device, a request for the at least one relevant segment. The receiving of the SIB segment mapping can be in response to the communicated request. The SIB segment mapping can be received in a message communicated to one of the UE or a group of identified UEs. The request for the SIB segment mapping can includes information about the UE and the received SIB segment mapping can include a modified mapping based on the information about the UE.
[0007] In another general aspect, a device, a system, a non-transitory computer- readable medium (having stored thereon computer executable program code which can be executed on a computer system), and/or a method can perform a process with a method including generating, by a network device, a system information broadcast (SIB) segment mapping, broadcasting, by the network device, the SIB segment mapping, generating, by the network device, a plurality of datasets each including network information, and broadcasting, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
[0008] Implementations can include one or more of the following features. For example, the network information can include non-terrestrial network (NTN) information. The network information can include at least one of intra-frequency information, interfrequency information, and inter-RAT information. The intra-frequency information can include cell priority, the inter-frequency information can include frequency range, and the inter-RAT information can include a radio access technology (RAT) associated with a neighbor cell. The network information can include a list of reference signal configurations. The SIB segment mapping can be configured to associate an SIB transmission occasion with different datasets and the association of the dataset with the SIB transmission occasion can refer to one of the content of each dataset or a segmenting criteria used for generating of each dataset.
[0009] The method can further include receiving, by the network device from a user equipment (UE), a request for at least one relevant segment and communicating, by the network device to the UE, the at least one relevant segment in response to the request. The SIB segment mapping can be modified based on information about the UE. The generating of the SIB segment mapping can include generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time, dividing the period of time into a number of segments of equal time duration, associating a subset of the network devices with each of the segments, and including satellite information associated with each of the subset of the network devices in the corresponding segment. The method can further include segmenting at least one block of satellite information based on the SIB segment mapping.
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] The details of one or more examples of embodiments are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims.
[0011] FIG. 1 is a block diagram of a wireless network according to an example embodiment.
[0012] FIG. 2 is a block diagram illustrating a signal flow for segmented system information block segmentation in a network according to an example embodiment.
[0013] FIG. 3 is a block diagram illustrating a signal flow for segmented system information block segmentation in a non-terrestrial network according to an example embodiment.
[0014] FIG. 4 is a block diagram illustrating communication of a segmented system information block according to an example embodiment.
[0015] FIG. 5 is a block diagram of a method illustrating communication of a segmented SIB according to an example embodiment.
[0016] FIG. 6 is a block diagram of a method illustrating user equipment communication of a segmented SIB according to an example embodiment.
[0017] FIG. 7 is a block diagram of a method illustrating network device communication of a segmented SIB according to an example embodiment.
[0018] FIG. 8 is a block diagram of a wireless station or wireless node (e.g., AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU- CP, CU-CP, ... or other node) according to an example embodiment.
DETAILED DESCRIPTION
[0019] FIG. 1 is a block diagram of a wireless network 130 according to an example embodiment. In the wireless network 130 of FIG. 1, user devices 131, 132, 133 and 135, which may also be referred to as mobile stations (MSs) or user equipment (UEs), may be connected (and in communication) with a base station (BS) 134, which may also be referred to as an access point (AP), an enhanced Node B (eNB), a BS, next generation Node B (gNB), a next generation enhanced Node B (ng-eNB), or a network node. The terms user device and user equipment (UE) may be used interchangeably. A BS may also include or may be referred to as a RAN (radio access network) node, and may include a portion of a BS or a portion of a RAN node, such as (e.g., such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS). At least part of the functionalities of a BS (e.g., access point (AP), base station (BS) or (e)Node B (eNB), BS, RAN node) may also be carried out by any node, server or host which may be operably coupled to a transceiver, such as a remote radio head. BS (or AP) 134 provides wireless coverage within a cell 136, including to user devices (or UEs) 131, 132, 133 and 135. Although only four user devices (or UEs) are shown as being connected or attached to BS 134, any number of user devices may be provided. BS 134 is also connected to a core network 150 via a SI interface or NG interface 151. This is merely one simple example of a wireless network, and others may be used.
[0020] A base station (e.g., such as BS 134) is an example of a radio access network (RAN) node within a wireless network. A BS (or a RAN node) may be or may include (or may alternatively be referred to as), e.g., an access point (AP), a gNB, an eNB, or portion thereof (such as a centralized unit (CU) and/or a distributed unit (DU) in the case of a split BS or split gNB), a non-terrestrial network (NTN) device, a satellite repeater, or other terrestrial or non-terrestrial network node. For example, a BS (or gNB) may include: a distributed unit (DU) network entity, such as a gNB-distributed unit (gNB- DU), and a centralized unit (CU) that may control multiple DUs. In some cases, for example, the centralized unit (CU) may be split or divided into: a control plane entity, such as a gNB-centralized (or central) unit-control plane (gNB-CU-CP), and an user plane entity, such as a gNB-centralized (or central) unit-user plane (gNB-CU-UP). For example, the CU sub-entities (gNB-CU-CP, gNB-CU-UP) may be provided as different logical entities or different software entities (e.g., as separate or distinct software entities, which communicate), which may be running or provided on the same hardware or server, in the cloud, etc., or may be provided on different hardware, systems or servers, e.g., physically separated or running on different systems, hardware or servers.
[0021] As noted, in a split configuration of a gNB/BS, the gNB functionality may be split into a DU and a CU. A distributed unit (DU) may provide or establish wireless communications with one or more UEs. Thus, a DUs may provide one or more cells, and may allow UEs to communicate with and/or establish a connection to the DU in order to receive wireless services, such as allowing the UE to send or receive data. A centralized (or central) unit (CU) may provide control functions and/or data-plane functions for one or more connected DUs, e.g., including control functions such as gNB control of transfer of user data, mobility control, radio access network sharing, positioning, session management etc., except those functions allocated exclusively to the DU. CU may control the operation of DUs (e.g., a CU communicates with one or more DUs) over a front-haul (Fs) interface.
[0022] According to an illustrative example, in general, a BS node (e.g., BS, eNB, gNB, NTN, CU/DU, ... ) or a radio access network (RAN) may be part of a mobile telecommunication system. A RAN (radio access network) may include one or more BSs or RAN nodes that implement a radio access technology, e.g., to allow one or more UEs to have access to a network or core network. Thus, for example, the RAN (RAN nodes, such as BSs or gNBs) may reside between one or more user devices or UEs and a core network. According to an example embodiment, each RAN node (e.g., BS, eNB, gNB, CU/DU, ... ) or BS may provide one or more wireless communication services for one or more UEs or user devices, e.g., to allow the UEs to have wireless access to a network, via the RAN node. Each RAN node or BS may perform or provide wireless communication services, e.g., such as allowing UEs or user devices to establish a wireless connection to the RAN node, and sending data to and/or receiving data from one or more of the UEs. For example, after establishing a connection to a UE, a RAN node (e.g., BS, eNB, gNB, CU/DU, ... ) may forward data to the UE that is received from a network or the core network, and/or forward data received from the UE to the network or core network. RAN nodes (e.g., BS, eNB, gNB, CU/DU, ... ) may perform a wide variety of other wireless functions or services, e.g., such as broadcasting control information (e.g., such as system information) to UEs, paging UEs when there is data to be delivered to the UE, assisting in handover of a UE between cells, scheduling of resources for uplink data transmission from the UE(s) and downlink data transmission to UE(s), sending control information to configure one or more UEs, and the like. These are a few examples of one or more functions that a RAN node or BS may perform. A base station may also be DU (Distributed Unit) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). DU facilitates the access link connection(s) for an IAB node.
[0023] A user device (user terminal, user equipment (UE), mobile terminal, handheld wireless device, etc.) may refer to a portable computing device that includes wireless mobile communication devices operating either with or without a subscriber identification module (SIM) (which may be referred to as Universal SIM), including, but not limited to, the following types of devices: a mobile station (MS), a mobile phone, a cell phone, a smartphone, a personal digital assistant (PDA), a handset, a device using a wireless modem (alarm or measurement device, etc.), a laptop and/or touch screen computer, a tablet, a phablet, a game console, a notebook, a vehicle, a sensor, and a multimedia device, as examples, or any other wireless device. It should be appreciated that a user device may also be (or may include) a nearly exclusive uplink only device, of which an example is a camera or video camera loading images or video clips to a network. A user device may be also MT (Mobile Termination) part of IAB (Integrated Access and Backhaul) node (a.k.a. a relay node). MT facilitates the backhaul connection for an IAB node.
[0024] In LTE (as an illustrative example), core network 150 may be referred to as Evolved Packet Core (EPC), which may include a mobility management entity (MME) which may handle or assist with mobility/handover of user devices between BSs, one or more gateways that may forward data and control signals between the BSs and packet data networks or the Internet, and other control functions or blocks. Other types of wireless networks, such as 5G (which may be referred to as New Radio (NR)) may also include a core network (e.g., which may be referred to as 5GC in 5G/NR).In addition, by way of illustrative example, the various example embodiments or techniques described herein may be applied to various types of user devices or data service types, or may apply to user devices that may have multiple applications running thereon that may be of different data service types. New Radio (5G) development may support a number of different applications or a number of different data service types, such as for example: machine type communications (MTC), enhanced machine type communication (eMTC), massive MTC (mMTC), Internet of Things (loT), and/or narrowband loT user devices, enhanced mobile broadband (eMBB), and ultra-reliable and low-latency communications (URLLC). Many of these new 5G (NR) - related applications may require generally higher performance than previous wireless networks.
[0025] loT may refer to an ever-growing group of objects that may have Internet or network connectivity, so that these objects may send information to and receive information from other network devices. For example, many sensor type applications or devices may monitor a physical condition or a status and may send a report to a server or other network device, e.g., when an event occurs. Machine Type Communications (MTC, or Machine to Machine communications) may, for example, be characterized by fully automatic data generation, exchange, processing and actuation among intelligent machines, with or without intervention of humans. Enhanced mobile broadband (eMBB) may support much higher data rates than currently available in LTE.
[0026] Ultra-reliable and low-latency communications (URLLC) is a new data service type, or new usage scenario, which may be supported for New Radio (5G) systems. This enables emerging new applications and services, such as industrial automations, autonomous driving, vehicular safety, e-health services, and so on. 3 GPP targets in providing connectivity with reliability corresponding to block error rate (BLER) of 10'5 and up to 1 ms U-Plane (user/data plane) latency, by way of illustrative example. Thus, for example, URLLC user devices/UEs may require a significantly lower block error rate than other types of user devices/UEs as well as low latency (with or without requirement for simultaneous high reliability). Thus, for example, a URLLC UE (or URLLC application on a UE) may require much shorter latency, as compared to an eMBB UE (or an eMBB application running on a UE).The various example embodiments may be applied to a wide variety of wireless technologies or wireless networks, such as LTE, LTE- A, 5G (New Radio (NR)), cmWave, and/or mmWave band networks, loT, Narrowband loT (NB-IoT), MTC, eMTC, mMTC, eMBB, URLLC, etc., or any other wireless network or wireless technology. These example networks, technologies or data service types are provided only as illustrative examples. [0027] In a connected mode (e.g., RRC-Connected) with respect to a cell (or gNB or DU), the UE is connected to a BS/gNB, and the UE may receive data, and may send data (based on receiving an uplink grant). Also, in a connected mode, UE mobility may be controlled by the gNB or network.
[0028] In order to conserve power, a UE may, for example, transition from a connected state (e.g., RRC Connected) to an unconnected state, such as an Idle state (e.g., RRC Idle) or Inactive state (e.g., RRC Inactive), e.g., in which the UE may sleep (a low power state) much of the time while in Idle or Inactive state. In Idle state or Inactive state, the UE does not have a connection established with any cell, and mobility (e.g., determining which cell the UE will be camped on or which cell to select as the serving cell for the UE) is controlled by the UE. Inactive state (e.g., RRC Inactive) may also be referred to as a suspended state of the UE. While in Idle state or Inactive state, the UE may sleep much of the time, and then periodically wake (e.g., changing from a low power state to a full-power state) to perform one or more tasks or processes, e.g., such as receiving system information from the cell the UE may be camped on (the serving cell for the UE while in Idle state or Inactive state), detecting a paging message (a paging message detected by the UE may indicate that the network has data for downlink transmission to the UE), and/or performing a cell search and cell reselection process in which the UE may measure reference signals from various cells, and then select a cell (or reselect the same cell) to camp on (as the serving cell), based on the received signals from various cells. Thus, as an example, cell selection may include selecting a cell that has a strongest reference signal received power (RSRP) and/or reference signal received quality (RSRQ), or other signal parameter. Thus, in Idle state or Inactive state, the serving cell may be referred to as the cell the UE has camped on. For example, a UE may typically receive system information (e.g., via receiving one or more broadcast system information blocks (SIBs)) from the serving cell (or the cell the UE is camping on) while the UE is awake in Idle state or Inactive state.
[0029] As noted, when a UE is in Idle state, there is no RRC context (the parameters necessary for communication between the UE and network) for the UE stored by the radio access network (BS/gNB) or UE. No uplink synchronization is maintained by the UE, and no data transfer may take place, as the UE sleeps most of the time to conserve battery consumption. The UE may wake periodically to receive paging messages and perform cell reselection, based on reference signal measurements. UE mobility is handled by the UE via cell reselection. An uplink transmission that may be performed by the UE in Idle mode is the random access (RACH) procedure or messages, that may be used for the UE to transition from Idle state to Connected state with respect to a cell or gNB.In Inactive state, (at least some) RRC context for the UE is stored at both the UE and the gNB, e.g., to allow the UE to more quickly transition from Inactive state to Connected state, e.g., since at least some RRC context for the UE may already be in place at the UE and the gNB (e.g., such as an inactive-radio network temporary identifier (I-RNU) assigned to the UE). At the same time, the Inactive UE is allowed to sleep (or enter a low power state), and periodically wake to receive paging messages and/or perform cell reselection, e.g., in a same or similar manner as Idle state.
[0030] A satellite constellation can provide discontinuous coverage on Earth using sparse satellite constellations. In other words, satellite constellations can include a satellite configured to provide coverage to a certain area for some time after which there will be a period, where there is no NTN coverage in the area. The satellite availability time and the time between satellite availability depends on the UE location and the satellite constellation, the radiofrequency beam pointing by the satellite, and both time intervals will also vary due to Earth rotation.
[0031] Discontinuous coverage can impact both connected (e.g., RRC Connected) and idle (e.g., RRC Idle) UEs. Connected UE(s) may need enhancement to declare Radio Link Failure fast when the satellite has disappeared and to not continue cell search. Idle UE(s) can save energy if the UE(s) know when to search for the next cell and when to monitor for paging (e.g., when there is coverage). Both scenarios can benefit from knowledge about when coverage appear s/disappears in the specific area.
[0032] Satellite assistance (e.g., ephemeris information), broadcast system information (e.g., PCI and frequency information) and UE location information can be used to help UE(s) in an loT NTN system perform measurement and cell selection and/or reselection. Satellite assistance information (e.g., ephemeris information) can be used for the handling of coverage holes or discontinuous satellite coverage efficiently (e.g., power efficient). The UE(s) can be configured to predict discontinuous coverage based on the satellite assistance information. If possible (or reasonable), the UE(s) may not attempt to camp or connect when there is no satellite coverage. If possible (or reasonable), the network may not try to reach UE(s), that are out of coverage. Implementations can include a configuration where the UE and the network can be synchronized when the UE is active (e.g., awake) and reachable (e.g., for paging). Provisioning of satellite assistance information can be performed using System Information (SI) message(s) for loT NTN.
[0033] The ephemeris and assistance information can be provided using System Information (SI) message(s) for loT NTN, can be used for the handling of coverage holes or discontinuous satellite coverage power efficiently, and can be used to predict discontinuous coverage. The ephemeris and assistance information can also be used for power savings in idle mode for NTN IOT devices and to relaxed monitoring and SI acquisition. However, the ephemeris information is heavy in terms of overhead (approximately 17-18 bytes). In addition, other information (e.g., frequency of transmission for different carriers, doppler compensation, PLMNs, and/or the like) may also be included in SI message(s) to minimize the search space of UEs in discontinuous coverage. Therefore, approximately 20 bytes or more may be needed for transmitting information associated with one single satellite.
[0034] Accordingly, the problem addressed by example implementations is how to provide information about discontinuous coverage to UEs in a signalling efficient way for connected UEs and/or UEs in Idle Mode. Example implementations can provide relaxed and power efficient monitoring of SI information for UEs with limited energy constraints (e.g., NB-IoT), enable prediction of discontinuous coverage for different long DRX settings, and minimize the massive overhead in the SI payload.
[0035] An example implementation can enable flexibility for a BS in terms of overhead associated with assistance information provided in NTN System Information (SI) messages, updates, and the like. The example implementation can split information from a SI message (NTN System Information Block (SIB) or SIB containing NTN data) data across multiple SI transmit occasions. The example implementation can provide rules that enables the UE to determine how the information of one SI message is distributed in the different SI occasions by providing support for UE selection of SI occasions to monitor. [0036] In another (or additional or supplemental) implementation UEs that are in the connected mode can request a dedicated transmission of the System Information Block (SIB). For example, the request can be for selected segments of the SI message, and not for the entire SI message. The BS can be broadcasting one SIB with NTN related information, one NTN-specific SIB, or one dedicated neighbor-satellite NTN SIB, such that the information associated with a neighbor satellite is transmitted. Each entry on the neighbor-satellite information can correspond to a different satellite and/or a different passing of a same satellite. The neighbor-satellite information can also include descriptors for an orbit that may be common for several satellites. Some specifications can provide a dedicated SIB request procedure, where UEs can receive and/or require, via RRC, the contents of a given SIB message.
[0037] FIG. 2 is a block diagram illustrating a signal flow for segmented system information block segmentation in a network according to an example embodiment. As shown in FIG. 3, a network (e.g., a terrestrial network, a non-terrestrial network (NTN), and/or the like) includes a user equipment (UE) 205 and a network device(s) 210. The network device(s) 210 can be a combination of devices. For example, the network device(s) 210 can represent a base station (BS), a gNB, an eNB, an NTN device, an NTN device and a core network device (or entity), the network device(s) 210 can represent an NTN device and an NTN control device (or entity), the network device(s) 210 can represent a terrestrial base station, a base station onboard a satellite, a satellite as a repeater, and any other similar combination of NTN devices and/or terrestrial network devices. A single device and/or the combination of devices can sometimes be referred to as a network device, a network system, and/or the like. The UE 205 can be a user device, a user terminal, a mobile device, a stationary device, an internet of things (loT) device, a narrowband (NB) loT device , any wirelessly (or cellular) connected device, and/or the like.
[0038] In block 215 an SIB occasion is divided into a number of SIB segments by the network device 210. For example, the above mentioned period of time (e.g., 16, 24, 36, hours and the like) for a valid dataset of network (e.g., NTN) devices can be divided into segments of equal time duration (e.g., 1, 2, 4, hours and the like). For example, an SIB can include cell re-selection information used for intra-frequency, inter-frequency, and/or inter-RAT cell re-selection. The SIB can be divided into, for example, three (3) segments. A first SIB segment can include intra-frequency information, a second SIB segment can include inter-frequency, and a third SIB segment can include inter-RAT information. For example, a UE (e.g., a RRC Idle UE) can be configured to receive reference signals (e.g., CSI-RS). A list of reference signals (e.g., CSI-RS) may be long. Therefore, the list of reference signals could be segmented into subsets of reference signals and the UE can be configured to receive one or more subset of reference signals. The UE may only support a subset of the frequencies and RATs that are listed in the SIB. Therefore, the UE can be configured to determine a subset of relevant cell re-selection information based on UE capability (e.g., frequency band and RAT support). In an example implementation, each SIB segment can be transmitted (block 235) in a same and/or different SIB occasions.
[0039] 210. The SIB segments can include, for example, satellite information (e.g., satellite availability for wireless service to a coverage area, cell re-selection information, reference signal information, and/or the like. The SIB segment mapping can be configured to map network information (e.g., network information useful for a UE operation). In other words, the SIB segment mapping can map an SIB segment to network information including, for example, a satellite available for wireless service to a coverage area at (or over) a time period, cell re-selection information, reference signal information, and/or the like. SIB segment mapping may be valid for a period of time (e.g., 2, 4, 8, 16, 24, 36, hours and the like).
[0040] The network device 210 can communicate (e.g., broadcast) a message (block 325) that is received by the UE 205. The message can include the SIB segment mapping. The UE 205 can use the SIB segment mapping to identify segment(s) of an SIB occasion. More specifically, in block 240, the UE 205 can identify relevant segment(s) of an SIB occasion based on the SIB segment mapping and a network requirement(s). The relevant segment(s) of the SIB occasion can be the SIB segments that indicate (or may indicate, or may include) network information (e.g., network information useful for a UE operation) of interest to the UE 205.
[0041] In block 230 dataset(s) including network information is generated by the network device 210. The dataset(s) can include network information corresponding a satellite in a satellite constellation, cell re-selection information, reference signal information, and/or the like. For example, the network information can include nonterrestrial network (NTN) information such as, for example, a satellite ephemeris, K offset, K mac, common delay (and potentially the first, second and third order parameters), doppler pre-compensation, and/or the like. For example, the network information can include intra-frequency information, inter-frequency information, and/or inter-RAT information. In an example implementation, the intra-frequency information can include cell priority (e.g., top priority cells can be in a first segment, lower priority cells can be in a second segment, and lowest priority cells can be in a third segment), the inter-frequency information can include frequency range(s) that can be segmented according to frequency layers (e.g., frequency range 0 - 2 GHz in a first segment, 2 - 4 GHz in a second segment, 4 - 6 GHz in a third segment, and the like), and the inter-RAT information can include a radio access technology (e.g., 5GNR, 4GLTE, 4G GSM, 3G, 2G, WI-FI, and the like) associated with a neighbor cell and. For example, the network information can include a subset(s) of reference signals. In an example implementation, the network device 210 can be configured to divide a list of reference signals into subset(s) of reference signals and the network information can include one or more subset(s) of reference signals and the corresponding reference signal configuration. For example, the network information can be based on reference signal time location and spatial domain and the UE could determine which segments are relevant segment(s) based on how the reference signals are located in time, spatial domain (e.g., selecting CSI-RS that are transmitted in the UE’s current and neighbor beams), and/or the like.
[0042] In block 245 a subset of a system information message including the relevant segments is received (e.g., processed) by the UE 205 based on the SIB segment mapping. The UE 205 can ignore (e.g., not receive, not process) the remainder (e.g., not relevant) segments. In addition, the relevant segments can include all of the necessary data or information. Therefore, the UE 205 can process the relevant segment without waiting for any other SIB occasions. In other words, the UE 205 can begin processing the relevant segment as soon as the reception of the relevant segment is completed.
[0043] Continuing below, by way of example, some elements, components, devices, functions, operations, and/or the like may refer to non-terrestrial network (NTN) elements, components, devices, functions, operations, and/or the like. However, these elements, components, devices, functions, operations, and/or the like (or portions thereof) can be applicable to other types of network (e.g., terrestrial network) elements, components, devices, functions, operations, and/or the like even should this not be explicitly stated when referring to these elements, components, devices, functions, operations, and/or the like.
[0044] FIG. 3 is a block diagram illustrating a signal flow in a non-terrestrial network according to an example embodiment. As shown in FIG. 3, a non-terrestrial network (NTN) includes a user equipment (UE) 305 and a network device(s) 310. The network device(s) 310 can be a combination of devices. For example, the network device(s) 310 can represent an NTN device and a core network device (or entity), the network device(s) 310 can represent an NTN device and an NTN control device (or entity), the network device(s) 310 can represent a base station onboard a satellite, a satellite as a repeater and a terrestrial base station, and any other similar combination of NTN devices and/or terrestrial network devices. A single device and/or the combination of devices can sometimes be referred to as an NTN device, an NTN system, and/or the like. The UE 305 can be a user device, a user terminal, a mobile device, a stationary device, an internet of things (loT) device, any wirelessly (or cellular) connected device, and/or the like.
[0045] In block 315 a dataset of network (e.g., NTN) devices that are relevant for a coverage area is generated by the network device 310. The dataset of network devices can be valid for a period of time (e.g., 16, 24, 36, hours and the like). For example, the network device 310 can identify network device(s) (possibly including network device 310) that can be configured to provide wireless service to a coverage area (e.g., cell 136) and/or a plurality of cells and when the identified network devices can provide the wireless service to the coverage area. Example implementations can include satellite constellations configured to provide discontinuous coverage on Earth using sparse satellite constellations. In other words, satellite constellations can include a satellite configured to provide coverage to a certain area for some time after which there will be a period, where there is no NTN coverage in the area. The satellite availability time and the time between satellite availability depends on the UE location and the satellite constellation, and both time intervals will also vary due to Earth rotation. Accordingly, the dataset of network (e.g., NTN) devices can be generated based on information about the satellites in a satellite constellation, the satellite availability time, and the time between satellite availability. The satellite availability time, and the time between satellite availability can be based on satellite(s) coverage time(s) and satellite movement vector(s) (that can take into consideration the rotation of the Earth).
[0046] The mapping of satellite position to a coverage can include, for example, the UE and/or network can determine the coverage on earth for a given satellite based on information about the satellite’s footprint (e.g., a circle below the satellite (circle center is linked to nadir of satellite) with a given radius) and/or based on the minimum elevation angle (e.g., if the angle between UE and satellite is above the minimum there is likely radio coverage). In some cases, satellites may not provide coverage on the exact same area. Instead, satellites may only have a partial overlap. The network device may filter such that only satellites provide 50 % (X) overlapping coverage with the current coverage are included in the SI. In block 320 a period of time is divided into a number of segments of equal time duration by the network device 310. For example, the above mentioned period of time (e.g., 16, 24, 36, hours and the like) for a valid dataset of network (e.g., NTN) devices can be divided into segments of equal time duration (e.g., 1, 2, 4, hours and the like). As an example, the network device 310 can divide the period of time, X, into Y segments of equal time duration, Z (e.g., X= 36 hours, Y=9 segments and Z= 4 hours). The segments can be referred to as SIB segments. In an example implementation, each SIB segment can be transmitted (block 355) in different SIB occasions.
[0047] In block 325 an SIB segment mapping is generated by the network device 310. As discussed above, the SIB segments (e.g., the segments of equal time duration) can include satellite information including satellite availability based on satellite(s) coverage time(s) indicating satellite availability for wireless service to a coverage area. The SIB segment mapping can be configured to map a satellite to an SIB segment. In other words, the SIB segment mapping can map an SIB segment to a satellite available for wireless service to a coverage area at (or over) a time period. SIB segment mapping may be valid for the period of time (e.g., 16, 24, 36, hours and the like) discussed above.
[0048] In block 330 a network connection time requirement(s) for the UE 305 is determined by the UE 305. The network connection time requirement(s) can be based on a next time(s) that the UE 305 may need a wireless connection to, for example, upload/download data, communicate/receive a message, monitor for paging, and/or the like. In other words, the network connection time requirement(s) can be a time, a time period, a time window, and/or the like that UE 305 may be (should be, may need to be) in an active state (e.g., awake and/or monitoring for paging) as opposed to an inactive state (e.g., asleep).
[0049] The network device 310 can communicate (e.g., broadcast) a message (block 335) that is received by the UE 305. The message can include the SIB segment mapping (as generated in block 325). The UE 305 can use the SIB segment mapping to identify segment(s) of an SIB occasion. More specifically, in block 340, the UE 305 can identify relevant segment(s) of an SIB occasion based on the SIB segment mapping and the network connection state time requirement(s). The relevant segment(s) of the SIB occasion can be the SIB segments that indicate (or may indicate) a satellite available for wireless service to a coverage area including the UE 305 when the UE 305 should be in an active state and needs or may need a wireless connection.
[0050] In block 345 sub-dataset(s) including NTN information is generated by the network device 310. The sub-dataset(s) can be portions of the dataset of network devices. In an example implementation, each sub-dataset includes NTN information corresponding to a network device (e.g., a satellite in the satellite constellation configured to provide discontinuous coverage). The NTN information can be a satellite ephemeris, K offset, K mac, common delay (and potentially the first, second and third order parameters), doppler pre-compensation, and/or the like.
[0051] In block 350 segmented system information messages can be individually broadcasted by the network device 310. Each segmented system information message can include at least one of the sub-datasets. The sub-dataset(s) that are included in a segmented system information message can be based on the SIB segment mapping.
[0052] In block 355 a subset of a system information message including the relevant segments is received (e.g., processed) by the UE 305 based on the SIB segment mapping. The UE 305 can ignore (e.g., not receive, not process) the remainder (e.g., not relevant) segments. In addition, the relevant segments can include all of the necessary data or information. Therefore, the UE 305 can process the relevant segment without waiting for any other SIB occasions. In other words, the UE 305 can begin processing the relevant segment as soon as the reception of the relevant segment is completed.
[0053] In block 360 the UE 305 can switch from an inactive state to an active state based on information associated with a coverage time of an NTN device included in the relevant segment(s). For example, in a time period (e.g., +6 to +8 hours) associated with a relevant segment, the UE 305 can switch to an active state. The UE 305 can then, for example, receive and/or communicate (block 365) a message to and/or from the NTN device associated with the relevant segment. For example, if the UE 305 is to communicate a message to the NTN device associated with the relevant segment, the UE 305 can connect (e.g., RRC_Connected) with the NTN device (that may or may not include network device 310) associated with the relevant segment and communicate the message. If the UE 305 is to receive a message from the NTN device associated with the relevant segment, the UE 305 can receive the message with or without connecting to the NTN device associated with the relevant segment.
[0054] FIG. 4 is a block diagram illustrating communication of a segmented system information block (SIB) according to an example embodiment. As shown in FIG. 4 a number of satellites 410 can be expected to cover a given area at some point in different time intervals 405. In the example of FIG. 4, there is irregular coverage, and at some intervals one satellite is expected (e.g., between T and 2T). In addition, illustrated are two intervals where more than one satellite is expected (e.g., two between 0 and T and three between 2T and 3T). Not shown is the possibility that in some intervals zero satellites may be expected.
[0055] In a first SIB segment implementation, SIB occasion 415-A shows an SIB that includes an NTN info segment, an A segment, a B segment, and a C segment. The A segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 0 and T. The B segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between T and 2T. The C segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 2T and 3T. SIB occasions 415-B and 415-C each show an SIB that includes the same segments as SIB occasion 415-A. In the first implementation, the same SIB is repeatedly transmitted with some SIB transmission periodicity. The UE may determine only to receive segment 415-B if the associated interval T to 2T fits the future communication needs of the UE.
[0056] In a second SIB segment implementation, SIB occasion 420-A shows an SIB that includes an NTN info segment and the A segment, SIB occasion 420-B shows an SIB that includes an NTN info segment and the B segment, and SIB occasion 420-C shows an SIB that includes an NTN info segment and the C segment. The A segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 0 and T. The B segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between T and 2T. The C segment includes (or is mapped to) sub-datasets associated with the satellites 410 available in the time interval between 2T and 3T. In the second implementation, a different SIB is transmitted in each SIB occasion, the transmissions are with some SIB transmission periodicity. The first implementation may trigger a system information update indication to the UE(s), whereas the second implementation does not trigger a system information update indication to the UE(s). The NTN info segment may include information associated with the current satellite and/or cell and may be an optional segment.
[0057] An example implementation can enable flexibility for a BS in terms of overhead associated with assistance information provided in NTN System Information (SI) messages, updates, and the like. The example implementation can split information from a SI message (NTN System Information Block (SIB) or SIB containing NTN data) data across multiple SI transmit occasions. The example implementation can provide rules that enables the UE to determine how the information of one SI message is distributed in the different SI occasions by providing support for UE selection of SI occasions to monitor. The implementation framework can also provide that the different SI segments (e.g., different to each other) can be transmitted without triggering SI modifications. Not triggering SI modifications, can be advantageous by saving power in that SI modifications can require UEs camped or connected to the cell to reacquire all Sis (or reacquire according to systemlnfoValueTagSI if used).
[0058] In an example implementation, the network device (e.g., NTN device, NTN system device, and/or the like) can estimate, using, for example, a satellite control center assistance, a full list of information of satellites or the passing of satellites that are relevant for the current coverage area. The estimation can be done for a period X (for example X = 36 hours). This full list can be called the dataset. The network device can divide the period (X) into Y segments of equal duration, Z (e.g., X = 36 hours, Y = 9 segments and Z = 4 hours). The segments can be called or include sub-datasets. Each sub-dataset can be transmitted in different SIB occasions. A SIB occasion that contains a specific sub-dataset can be called an SIB segments (e.g., with Y=9 there are 9 SIB segments).
[0059] Referring to FIG. 4, illustrated is the number of satellites 410 expected to cover a given area at some point in different time intervals. There is irregular coverage, and at some intervals one or more satellites is expected (noting that zero satellites can be expected which is not shown). As an example, for an loT (or NB-IOT) device, the most optimistic SIB assumption could be only the first three (3) satellites. In this example, it means that no prediction can be made past 2T, using the maximum transport block size, which is likely not enough for loT devices with long DRX or PSM active. Therefore, the loT device could become active (e.g., wake-up) with no satellite in range (e.g., in the dark).
[0060] Therefore, the satellite may need to proceed with new scanning to find suitable satellites or may need to wake up early to acquire information about the next T (e.g., from 2T to 3T). If interval segmentation of T is used, all of the six (6) satellites depicted can be conveyed, in groups of at most three (3) satellites at a time, which would still leave room in the SIB. In a different SIB (for example SIB1 which is a pointer for the other SIBs) or in the SIB containing information assistance for neighbor-satellites. In an example implementation, a new set of parameter(s) can be introduced. The parameters can be, for example, a time window size for a SIB segment, size of sequence (or number of SIB segments), a modification interval for SIB segment(s), and/or a version number of the current transmission or the start point of the dataset.
[0061] The time window size for a SIB segment can be the duration of a segment in time (e.g., in the example above, Z = 4 hours). The size of sequence can be the total number of different SIB sequences (or sub-datasets) available in the dataset (e.g., in the example, Y=9 segments). The modification interval for SIB segment(s) can be the period for the transmission of one SIB segment in the SI. For example, if the modification interval is set equal to one Si-Window then one SIB segment is transmitted in all SIB occasions within the Si-Window. In the next SI window, the SIB version associated to the next segment of time is transmitted. The version number of the current transmission or the start point of the dataset can indicate the SIB segment index for the current SIB occasion (ex: 3 of 9, if the third segment out of nine is being transmitted in the current SIB version). Or the starting point of the data set (in SFN, SIB occasion or else). The version can allow the UE to traceback the occasion for each segment. From the UE point of view, after reading one SIB occasion, the UE can determine to which segment of time each SIB transmission corresponds. The UE can estimate the segment of times that are relevant for the next UE active (e.g., wake-up) times.
[0062] In another (or additional or supplemental) implementation UEs that are in the connected mode can request a dedicated transmission of the System Information Block (SIB). For example, the request can be for selected segments of the SI message, and not for the entire SI message. The BS can be broadcasting one SIB with NTN related information, one NTN-specific SIB, or one dedicated neighbor-satellite NTN SIB, such that the information associated with a neighbor satellite is transmitted. Each entry on the neighbor-satellite information can correspond to a different satellite and/or a different passing of a same satellite. The neighbor-satellite information can also include descriptors for an orbit that may be common for several satellites.
[0063] Some specifications can provide a dedicated SIB request procedure, where UEs can require, via RRC, the contents of a given SIB message. For example, for a UE in RRC CONNECTED, the network can provide system information through dedicated signaling using the RRCReconfiguration message (e.g., if the UE has an active BWP with no common search space configured to monitor system information or paging).
Therefore, an example implementation can be implemented via RRCSystemlnfoRequest message. In which the UE configures the requested- Si-List or contains a list of requested SI messages. According to the order of entry in the list of SI messages configured by schedulinglnfoList in si-Schedulinglnfo in SIB1, first bit corresponds to first/leftmost listed SI message, second bit corresponds to second listed SI message, and so on.
[0064] Therefore, example implementations can include modifications on this procedure, to provide solution for different scenarios. For example, the UE may provide a list of segments the UE is interested in. Or request for the full contents (full dataset of SIB). For example, if the bit corresponding to the SI that contains the neighbor cell list (e.g., called SI nl) in requested-SI-List is set enabled, this enables an additional parameter (e.g., requested-segments-SI nl-list). One bit can represent each segment in this case. For overhead purposes, the network may limit the number of requests for the full list or parts of the list. The request can be made available for power harvesting UEs and not for other UEs.
[0065] The network may not need to repeat the common information of every SI nl version, but just append the list of different segments at the end of the first version transmitted in RRC response. In another implementation, the request may be relative only to the neighbor cell list within SI nl, if other NTN is also part of the same SI. In another implementation, the network can be configured to determine to reply a UE request using the group identity (e.g., G-RNTI), when the UE is part of a group, such that the whole group can have access to one information via one request only, minimizing possible overheads.
[0066] In some implementations, some (or even most) intervals may not contain relevant satellites. Therefore, the sequence definition may also contain indication of which intervals do not have a satellite (e.g., are empty) and these datasets are skipped from the calculations. The calculations of active (e.g., wake-up) time intervals at the UE side are done accordingly. In 5G specifications, the multiple repetitions of a SIB within a SI- window, are assumed to be the same, as they may be used for different SSB (beams). But, in case of quasi-collocated or collocated beams, or the case where the NTN SIB is repeated across all beams, one alternative implementation possible may be that each SI occasion conveys a different SIB segment within the same Si-window. In an alternative (or additional) implementation, the SIB segments are not provided sequentially, but instead in a prioritized order. For example, the network may provide sets 1 and 2, which define the most imminent coverage opportunities, more frequently than the remaining sets. Potential sequences could be {1, 2, 3, 1, 2, 4, 1, 2, 5, 1, 2, 6} and {1, 3, 2, 4, 1, 5, 2, 6}.
[0067] FIG. 5 is a block diagram of a method illustrating communication of a segmented SIB in a UE according to an example embodiment. As shown in FIG. 5, in step S505 delay requirements are determined. The delay requirements can be based on and/or include QoS, paging, UL data, and/or the like. For example, the UE can be a narrowband (NB) loT device. The NB loT device can have minimum QoS requirements and paging requirements in order to communicate with a network device. For example, according to the QoS of an application executing on the UE, a network connection should be available for communication (UL and/or DL) in four (4) hour increments (e.g., every
3.5 to 4.5 hours). Therefore, a delay requirement for the UE can be 4 hours (e.g., T=0, 4, 8, 12 ... ). As another example, according to the QoS of an application (the same application or a different application) executing on the UE, a network connection should be available for paging daily (e.g., once in a 24 hour span). Therefore, a delay requirement for the UE can be 24 hours (or a range, e.g., every 20 to 30 hours). Other delay requirements (e.g., for the same or additional applications) may also need to be met.
[0068] In step S510 when a connection is needed is estimated based on delay requirements. For example, as discussed above, the delay requirements can include (or indicate) times (e.g., a range of time, time increments, and/or the like). In addition, the delay requirements can be based on, for example, a QoS associated with connection requirements. Therefore, when a connection is needed can be based on the included (or indicated) times (e.g., a range of time, time increments, and/or the like). Continuing the above example, connections can be needed in four (4) hour increments (e.g., every 3.5 to
4.5 hours). Therefore, the UE can need a connection at, for example, T=0, 4, 8, 12 and so forth.
[0069] In step S515 an SIB configuration of multiple segments is received. For example, an SIB segment mapping can be received from a network device (e.g., a serving satellite). As discussed above, SIB segments (e.g., the segments of equal time duration) can include satellite information including satellite availability based on satellite(s) coverage time(s) indicating satellite availability for wireless service to a coverage area. The SIB segment mapping can be configured to map a satellite to an SIB segment. In other words, the SIB segment mapping can map an SIB segment to a satellite available for wireless service to a coverage area at (or over) a time period. In addition, the UE can consider UE movement. For example, the UE can estimate location at a future point in time such that the UE can determine if the coverage of the future satellites is available also at that future location. SIB segment mapping may be valid for the period of time (e.g., 16, 24, 36, hours and the like) discussed above.
[0070] In step S520 relevant segment(s) of the SIB are identified based on when the connection is needed, and coverage is available. For example, a plurality of satellites can be available to a coverage area over a time period (e.g., available every ’/2 hour, available non-incrementally, with some availability and some non-availability, and/or the like). An SIB can be used to indicate the availability of each of the plurality of satellites. Therefore, the SIB segment mapping can be used to identify the relevant segment(s) of the SIB.
[0071] In step S525 relevant segment(s) of the SIB are received. For example, the SIB segment mapping can be used to identify the broadcasted SIB segments to process. In other words, some SIB segments can be processed (e.g., received) and some SIB segments can be ignored (e.g., not processed, not received) based on the identified (SIB segments to be processed) SIB segments and the SIB segment mapping (some indication of when, which, an order, and/or the like) of the broadcasted SIB segments. In some implementations, the UE can complete the processing of the received SIB segment without waiting for another (e.g., to be received or processed) SIB segment.
[0072] In step S530 the UE (optionally) becomes active (sometimes referred to as waking up) according to coverage indicated by received segment(s). For example, as mentioned above, the QoS of an application (and/or a plurality of applications) executing on the UE can include a requirement for when a network connection should be available. Therefore, the UE can switch to an active mode to perform the process associated with the QoS of the application(s) using the information (e.g., coverage) received in a relevant SIB segment. The UE may or may not connect to the satellite serving the coverage area. For example, to communicate and/or receive data (e.g., via an UL/DL connection) the UE can connect with the satellite serving the coverage area. However, if the UE is to receive broadcast or paging data, there may be no need for the UE to connect with the satellite serving the coverage area.
[0073] As discussed above, the ephemeris and assistance information can be provided using System Information (SI) message(s) for loT NTN, can be used for the handling of coverage holes or discontinuous satellite coverage power efficiently, and can be used to predict discontinuous coverage. The ephemeris and assistance information can also be used for power savings in idle mode for NTN IOT devices and to relaxed monitoring and SI acquisition. However, the ephemeris information is heavy in terms of overhead (approximately 17-18 bytes). In addition, other information (e.g., frequency of transmission for different carriers, doppler compensation, PLMNs, and/or the like) may also be included in SI message(s) to minimize the search space of UEs in discontinuous coverage. Therefore, approximately 20 bytes or more may be needed for transmitting information associated with one single satellite.
[0074] In addition (additional details regarding the problem to be solved by the described example implementations), the neighbor cell information is expected to be signaled in the same NTN SI as other NTN specific information: serving satellite ephemeris, K offset, K mac, common delay (and potentially the first, second and third order parameters), doppler pre-compensation and others. As the 3GPP specifications clarify in TS 38.331, Section 5.2.1, “The physical layer imposes a limit to the maximum size a SIB can take. The maximum SIB1 or SI message size is 2976 bits.”. In total, the maximum SI size allowed is 372 bytes (2976 bits). Assuming several bytes are used for the minimum NTN assistance information for the serving satellite, the space left for broadcasting neighbor satellite information would allow the broadcasting of 12-16 satellites’ information, with the caveats about loss of precision associated with transmitting basic instantaneous orbital information only: in the order of -20 seconds for prediction windows of -12 hours, up to -230 seconds for prediction windows of -84 hours.
[0075] This problem is further magnified for loT over NTN. The reasons are manyfold. First, the UE(s) are already more sensitive to power constraints than a regular UE. In addition, the UE(s) may rely on repetitions to acquire information, which may lead to the time to receive the SIB is prolonged (especially for cell edge users) the larger the payload is, therefore impacting the power consumption. And most importantly, the loT technologies (NB-IoT and eMTC) have a reduced maximum transport block size. For example, the 36.331 states on Section 5.2.1, “For BL UEs and UEs in CE, the maximum SIB and SI message size is 936 bits. For NB-IoT, the maximum SIB and SI message size is 680 bits.” The limit of 680 bits would be at the best-case scenario large enough to convey the ephemeris for only five (5) satellites. However, even five (5) satellites might be unrealistic. For example, the times for “switching on and off’ the signal transmission from the satellite in an area can require additional overhead on top of interference. This limited number of information, in certain scenarios, would not be able to provide information far away in the future, for example, for a UE expected to estimate coverage one day in the future due to long extended DRX settings (loT devices) or PSM (Power Saving Mode). And even if the cases where multiple satellites are reported in NR, it may not be an efficient resource usage reserving a heavy overhead of 2976 bits that is frequently transmitted in the NTN SI, specially considering that the NTN already tends to less efficient PHY usage.
[0076] Example 1. FIG. 6 is a block diagram of a method illustrating user equipment communication of a segmented SIB according to an example embodiment. The method including, in step S610 receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping. In step S620 identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information. In step 630 receiving, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
[0077] Example 2. The method of Example 1 can further include estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
[0078] Example 3. The method of Example 1 can further include determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell re-selection information.
[0079] Example 4. The method of Example 3, wherein the cell re-selection information can be associated with at least one of intra-frequency re-selection, interfrequency re-selection, and inter-RAT re-selection.
[0080] Example 5. The method of Example 1, wherein the UE required assistance information can be associated with reference signal information.
[0081] Example 6. The method of Example 5 can further include determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
[0082] Example 7. The method of Example 5 or example 6, wherein the at least one relevant segment can be determined based on a reference signal’s location in time. [0083] Example 8. The method of Example 1, wherein the at least one relevant segment can include satellite assistance information.
[0084] Example 9. The method of any of Example 1 to Example 8, wherein the SIB segment mapping can associate each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
[0085] Example 10. The method of Example 9, wherein a coverage time interval of at least one of the network device and at least one second network device can be based on the coverage time and a movement vector. The position vector, the movement vector, and/or orbital information can be included in an ephemeris associated with at least one satellite. Orbital information can be used in addition to and/or in place of a movement vector to determine a coverage time interval.
[0086] Example 11. The method of any of Example 1 to Example 10, wherein the SIB segment mapping can indicate a time interval with no network device coverage.
[0087] Example 12. The method of any of Example 1 to Example 11 can further include switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
[0088] Example 13. The method of any of Example 1 to Example 12, wherein the UE determines not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
[0089] Example 14. The method of any of Example 1 to Example 13 can further include communicating, by the UE to the network device, a request for the at least one relevant segment.
[0090] Example 15. The method of Example 14, wherein the receiving of the SIB segment mapping can be in response to the communicated request.
[0091] Example 16. The method of Example 15, wherein the SIB segment mapping can be received in a message communicated to one of the UE or a group of identified UEs.
[0092] Example 17. The method of any of Example 14 to Example 16, wherein the request for the SIB segment mapping can includes information about the UE and the received SIB segment mapping can include a modified mapping based on the information about the UE.
[0093] Example 18. FIG. 7 is a block diagram of a method illustrating network device communication of a segmented SIB according to an example embodiment. The method including, in step S710 generating, by a network device, a system information broadcast (SIB) segment mapping. In step S720 broadcasting, by the network device, the SIB segment mapping. In step S730 generating, by the network device, a plurality of datasets each including network information. In step S740 broadcasting, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
[0094] Example 19. The method of Example 18, wherein the network information can include non-terrestrial network (NTN) information.
[0095] Example 20. The method of Example 18, wherein the network information can include at least one of intra-frequency information, inter-frequency information, and inter-RAT information.
[0096] Example 21. The method of Example 20, wherein the intra-frequency information can include cell priority, the inter-frequency information can include frequency range, and the inter-RAT information can include a radio access technology (RAT) associated with a neighbor cell.
[0097] Example 22. The method of Example 18, wherein the network information can include a list of reference signal configurations.
[0098] Example 23. The method of Example 18, wherein the SIB segment mapping can be configured to associate an SIB transmission occasion with different datasets and the association of the dataset with the SIB transmission occasion can refer to one of the content of each dataset or a segmenting criteria used for generating of each dataset.
[0099] Example 24. The method of Example 18 can further include receiving, by the network device from a user equipment (UE), a request for at least one relevant segment and communicating, by the network device to the UE, the at least one relevant segment in response to the request.
[0100] Example 25. The method of Example 18, wherein the SIB segment mapping can be modified based on information about the UE.
[0101] Example 26. The method of any of Example 18 to Example 25, wherein the generating of the SIB segment mapping can include generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time, dividing the period of time into a number of segments of equal time duration, associating a subset of the network devices with each of the segments, and including satellite information associated with each of the subset of the network devices in the corresponding segment.
[0102] Example 27. The method of any of Example 18 to Example 25 can further include segmenting at least one block of satellite information based on the SIB segment mapping.
[0103] Example 28. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to perform the method of any of Examples 1-27.
[0104] Example 29. An apparatus comprising means for performing the method of any of Examples 1-27.
[0105] Example 30. An apparatus comprising at least one processor and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform the method of any of Examples 1 -27.
[0106] FIG. 8 is a block diagram of a wireless station 800 or wireless node or network node 800 according to an example embodiment. The wireless node or wireless station or network node 800 may include, e.g., one or more of an AP, BS, gNB, RAN node, relay node, UE or user device, network node, network entity, DU, CU-CP, CU-UP, ... or other node) according to an example embodiment.
[0107] The wireless station 800 may include, for example, one or more (e.g., two as shown in FIG. 8) radio frequency (RF) or wireless transceivers 802A, 802B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. The wireless station also includes a processor or control unit/entity (controller) 804 to execute instructions or software and control transmission and receptions of signals, and a memory 806 to store data and/or instructions.
[0108] Processor 804 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 804, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 802 (802A or 802B). Processor 804 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 802, for example). Processor 804 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 804 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and/or any combination of these. Using other terminology, processor 804 and transceiver 802 together may be considered as a wireless transmitter/receiver system, for example.
[0109] In addition, referring to FIG. 8, a controller (or processor) 808 may execute software and instructions, and may provide overall control for the station 800, and may provide control for other systems not shown in FIG. 8, such as controlling input/output devices (e.g., display, keypad), and/or may execute software for one or more applications that may be provided on wireless station 800, such as, for example, an email program, audio/video applications, a word processor, a Voice over IP application, or other application or software.
[0110] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 804, or other controller or processor, performing one or more of the functions or tasks described above.
[0111] According to another example embodiment, RF or wireless transceiver(s) 802A/802B may receive signals or data and/or transmit or send signals or data. Processor 804 (and possibly transceivers 802A/802B) may control the RF or wireless transceiver 802A or 802B to receive, send, broadcast or transmit signals or data.
[0112] The example embodiments are not, however, restricted to the system that is given as an example, but a person skilled in the art may apply the solution to other communication systems. Another example of a suitable communications system is the 5G system. It is assumed that network architecture in 5G will be quite similar to that of the LTE-advanced. 5G is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
[0113] It should be appreciated that future networks will most probably utilize network functions virtualization (NFV) which is a network architecture concept that proposes virtualizing network node functions into “building blocks” or entities that may be operationally connected or linked together to provide services. A virtualized network function (VNF) may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized. In radio communications this may mean node operations may be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.
[0114] Example embodiments of the various techniques described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Example embodiments may be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. Embodiments may also be provided on a computer readable medium or computer readable storage medium, which may be a non-transitory medium. Embodiments of the various techniques may also include embodiments provided via transitory signals or media, and/or programs and/or software embodiments that are downloadable via the Internet or other network(s), either wired networks and/or wireless networks. In addition, embodiments may be provided via machine type communications (MTC), and also via an Internet of Things (IOT).
[0115] The computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, distribution medium, or computer readable medium, which may be any entity or device capable of carrying the program. Such carriers include a record medium, computer memory, read-only memory, photoelectrical and/or electrical carrier signal, telecommunications signal, and software distribution package, for example. Depending on the processing power needed, the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
[0116] Furthermore, example embodiments of the various techniques described herein may use a cyber-physical system (CPS) (a system of collaborating computational elements controlling physical entities). CPS may enable the embodiment and exploitation of massive amounts of interconnected ICT devices (sensors, actuators, processors microcontrollers, ...) embedded in physical objects at different locations. Mobile cyber physical systems, in which the physical system in question has inherent mobility, are a subcategory of cyber-physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals. The rise in popularity of smartphones has increased interest in the area of mobile cyber-physical systems. Therefore, various embodiments of techniques described herein may be provided via one or more of these technologies.
[0117] A computer program, such as the computer program(s) described above, can be written in any form of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit or part of it suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
[0118] Method steps may be performed by one or more programmable processors executing a computer program or computer program portions to perform functions by operating on input data and generating output. Method steps also may be performed by, and an apparatus may be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
[0119] Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer, chip or chipset. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. Elements of a computer may include at least one processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer also may include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, special purpose logic circuitry.
[0120] To provide for interaction with a user, embodiments may be implemented on a computer having a display device, e.g., a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user and a user interface, such as a keyboard and a pointing device, e.g., a mouse or a trackball, by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
[0121] Example embodiments may be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an embodiment, or any combination of such back-end, middleware, or front-end components. Components may be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (LAN) and a wide area network (WAN), e.g., the Internet.
[0122] While certain features of the described embodiments have been illustrated as described herein, many modifications, substitutions, changes and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the various embodiments.

Claims

WHAT IS CLAIMED IS:
1. A method comprising: receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping; identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information; and receiving, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
2. The method of claim 1, further comprising: estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
3. The method of claim 1, further comprising: determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell reselection information.
4. The method of claim 3, wherein the cell re-selection information is associated with at least one of intra-frequency re-selection, inter-frequency re-selection, and inter- RAT re-selection.
5. The method of claim 1, wherein the UE required assistance information is associated with reference signal information.
6. The method of claim 5, further comprising: determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
35
7. The method of claim 5 or claim 6, wherein the at least one relevant segment is determined based on a reference signal’s location in time.
8. The method of claim 1, wherein the at least one relevant segment includes satellite assistance information.
9. The method of any of claim 1 to claim 8, wherein the SIB segment mapping associates each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
10. The method of claim 9, wherein a coverage time interval of at least one of the network device and at least one second network device is based on the coverage time and a movement vector.
11. The method of any of claim 1 to claim 10, wherein the SIB segment mapping indicates a time interval with no network device coverage.
12. The method of any of claim 1 to claim 11, further comprising: switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
13. The method of any of claim 1 to claim 12, wherein the UE determines not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
14. The method of any of claim 1 to claim 13, further comprising: communicating, by the UE to the network device, a request for the at least one relevant segment.
36
15. The method of claim 14, wherein the receiving of the SIB segment mapping is in response to the communicated request.
16. The method of claim 15, wherein the SIB segment mapping is received in a message communicated to one of the UE or a group of identified UEs.
17. The method of any of claim 14 to claim 16, wherein the request for the SIB segment mapping includes information about the UE, and the received SIB segment mapping includes a modified mapping based on the information about the UE.
18. A method comprising: generating, by a network device, a system information broadcast (SIB) segment mapping; broadcasting, by the network device, the SIB segment mapping; generating, by the network device, a plurality of datasets each including network information; and broadcasting, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
19. The method of claim 18, wherein the network information includes non-terrestrial network (NTN) information.
20. The method of claim 18, wherein the network information includes at least one of intra-frequency information, inter-frequency information, and inter-RAT information.
21. The method of claim 20, wherein the intra-frequency information includes cell priority, the inter-frequency information includes frequency range, and the inter-RAT information includes a radio access technology (RAT) associated with a neighbor cell.
22. The method of claim 18, wherein the network information includes a list of reference signal configurations.
23. The method of claim 18, wherein the SIB segment mapping is configured to associate an SIB transmission occasion with different datasets, and the association of the dataset with the SIB transmission occasion refers to one of a content of each dataset or a segmenting criteria used for generating of each dataset.
24. The method of claim 18, further comprising: receiving, by the network device from a user equipment (UE), a request for at least one relevant segment; and communicating, by the network device to the UE, the at least one relevant segment in response to the request.
25. The method of claim 24, wherein the SIB segment mapping is modified based on information about the UE.
26. The method of any of claim 18 to claim 25, wherein the generating of the SIB segment mapping includes: generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time; dividing the period of time into a number of segments of equal time duration; associating a subset of the network devices with each of the segments; and including satellite information associated with each of the subset of the network devices in the corresponding segment.
27. The method of any of claim 18 to claim 26, further comprising: segmenting at least one block of satellite information based on the SIB segment mapping.
28. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to: receive, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping; identify, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information; and receive, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
29. The non-transitory computer-readable storage medium of claim 28, the instructions further causing a computing system to: estimate, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
30. The non-transitory computer-readable storage medium of claim 28, the instructions further causing a computing system to: determine, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell reselection information.
31. The non-transitory computer-readable storage medium of claim 30, wherein the cell re-selection information is associated with at least one of intra-frequency reselection, inter-frequency re-selection, and inter-RAT re-selection.
32. The non-transitory computer-readable storage medium of claim 28, wherein the UE required assistance information is associated with reference signal information.
39
33. The non-transitory computer-readable storage medium of claim 32, the instructions further causing a computing system to: determine, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
34. The non-transitory computer-readable storage medium of claim 32 or claim 33, wherein the at least one relevant segment is determined based on a reference signal’s location in time.
35. The non-transitory computer-readable storage medium of claim 28, wherein the at least one relevant segment includes satellite assistance information.
36. The non-transitory computer-readable storage medium of any of claim 28 to claim 8, wherein the SIB segment mapping associates each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
37. The non-transitory computer-readable storage medium of claim 36, wherein a coverage time interval of at least one of the network device and at least one second network device is based on the coverage time and a movement vector.
38. The non-transitory computer-readable storage medium of any of claim 28 to claim
37, wherein the SIB segment mapping indicates a time interval with no network device coverage.
39. The non-transitory computer-readable storage medium of any of claim 28 to claim
38, the instructions further causing a computing system to: switch, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
40
40. The non-transitory computer-readable storage medium of any of claim 28 to claim 39, wherein the UE determines not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
41. The non-transitory computer-readable storage medium of any of claim 28 to claim 40, the instructions further causing a computing system to: communicate, by the UE to the network device, a request for the at least one relevant segment.
42. The non-transitory computer-readable storage medium of claim 41, wherein the receiving of the SIB segment mapping is in response to the communicated request.
43. The non-transitory computer-readable storage medium of claim 42, wherein the SIB segment mapping is received in a message communicated to one of the UE or a group of identified UEs.
44. The non-transitory computer-readable storage medium of any of claim 41 to claim 43, wherein the request for the SIB segment mapping includes information about the UE, and the received SIB segment mapping includes a modified mapping based on the information about the UE.
45. A non-transitory computer-readable storage medium comprising instructions stored thereon that, when executed by at least one processor, are configured to cause a computing system to: generate, by a network device, a system information broadcast (SIB) segment mapping; broadcast, by the network device, the SIB segment mapping; generate, by the network device, a plurality of datasets each including network information; and
41 broadcast, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
46. The non-transitory computer-readable storage medium of claim 45, wherein the network information includes non-terrestrial network (NTN) information.
47. The non-transitory computer-readable storage medium of claim 45, wherein the network information includes at least one of intra-frequency information, inter-frequency information, and inter-RAT information.
48. The non-transitory computer-readable storage medium of claim 47, wherein the intra-frequency information includes cell priority, the inter-frequency information includes frequency range, and the inter-RAT information includes a radio access technology (RAT) associated with a neighbor cell.
49. The non-transitory computer-readable storage medium of claim 45, wherein the network information includes a list of reference signal configurations.
50. The non-transitory computer-readable storage medium of claim 45, wherein the SIB segment mapping is configured to associate an SIB transmission occasion with different datasets, and the association of the dataset with the SIB transmission occasion refers to one of a content of each dataset or a segmenting criteria used for generating of each dataset.
51. The non-transitory computer-readable storage medium of claim 45, the instructions further causing a computing system to: receive, by the network device from a user equipment (UE), a request for at least one relevant segment; and communicate, by the network device to the UE, the at least one relevant segment in response to the request.
42
52. The non-transitory computer-readable storage medium of claim 51, wherein the SIB segment mapping is modified based on information about the UE.
53. The non-transitory computer-readable storage medium of any of claim 45 to claim
52, wherein the generating of the SIB segment mapping includes: generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time; dividing the period of time into a number of segments of equal time duration; associating a subset of the network devices with each of the segments; and including satellite information associated with each of the subset of the network devices in the corresponding segment.
54. The non-transitory computer-readable storage medium of any of claim 45 to claim
53, the instructions further causing a computing system to: segment at least one block of satellite information based on the SIB segment mapping.
55. An apparatus comprising means for: receiving, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping; identifying, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information; and receiving, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
56. The apparatus of claim 55, further comprising means for: estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
43
57. The apparatus of claim 55, further comprising means for: determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell reselection information.
58. The apparatus of claim 57, wherein the cell re-selection information is associated with at least one of intra-frequency re-selection, inter-frequency re-selection, and inter- RAT re-selection.
59. The apparatus of claim 55, wherein the UE required assistance information is associated with reference signal information.
60. The apparatus of claim 59, further comprising means for: determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
61. The apparatus of claim 59 or claim 60, wherein the at least one relevant segment is determined based on a reference signal’s location in time.
62. The apparatus of claim 55, wherein the at least one relevant segment includes satellite assistance information.
63. The apparatus of any of claim 55 to claim 62, wherein the SIB segment mapping associates each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
64. The apparatus of claim 63, wherein a coverage time interval of at least one of the network device and at least one second network device is based on the coverage time and a movement vector.
44
65. The apparatus of any of claim 55 to claim 64, wherein the SIB segment mapping indicates a time interval with no network device coverage.
66. The apparatus of any of claim 55 to claim 65, further comprising means for: switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
67. The apparatus of any of claim 55 to claim 66, wherein the UE determines not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
68. The apparatus of any of claim 55 to claim 67, further comprising means for: communicating, by the UE to the network device, a request for the at least one relevant segment.
69. The apparatus of claim 68, wherein the receiving of the SIB segment mapping is in response to the communicated request.
70. The apparatus of claim 69, wherein the SIB segment mapping is received in a message communicated to one of the UE or a group of identified UEs.
71. The apparatus of any of claim 68 to claim 70, wherein the request for the SIB segment mapping includes information about the UE, and the received SIB segment mapping includes a modified mapping based on the information about the UE.
72. An apparatus comprising means for: generating, by a network device, a system information broadcast (SIB) segment mapping; broadcasting, by the network device, the SIB segment mapping;
45 generating, by the network device, a plurality of datasets each including network information; and broadcasting, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
73. The apparatus of claim 72, wherein the network information includes nonterrestrial network (NTN) information.
74. The apparatus of claim 72, wherein the network information includes at least one of intra-frequency information, inter-frequency information, and inter-RAT information.
75. The apparatus of claim 74, wherein the intra-frequency information includes cell priority, the inter-frequency information includes frequency range, and the inter-RAT information includes a radio access technology (RAT) associated with a neighbor cell.
76. The apparatus of claim 72, wherein the network information includes a list of reference signal configurations.
77. The apparatus of claim 72, wherein the SIB segment mapping is configured to associate an SIB transmission occasion with different datasets, and the association of the dataset with the SIB transmission occasion refers to one of a content of each dataset or a segmenting criteria used for generating of each dataset.
78. The apparatus of claim 72, further comprising means for: receiving, by the network device from a user equipment (UE), a request for at least one relevant segment; and communicating, by the network device to the UE, the at least one relevant segment in response to the request.
46
79. The apparatus of claim 78, wherein the SIB segment mapping is modified based on information about the UE.
80. The apparatus of any of claim 72 to claim 79, wherein the generating of the SIB segment mapping includes: generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time; dividing the period of time into a number of segments of equal time duration; associating a subset of the network devices with each of the segments; and including satellite information associated with each of the subset of the network devices in the corresponding segment.
81. The apparatus of any of claim 72 to claim 80, further comprising means for: segmenting at least one block of satellite information based on the SIB segment mapping.
82. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: receive, by a user equipment (UE) from a network device, a system information broadcast (SIB) segment mapping; identify, by the UE, at least one relevant segment of at least one SIB occasion based on the SIB segment mapping and a UE required assistance information; and receive, by the UE, based on the SIB segment mapping, a subset of a system information message including the at least one relevant segment.
83. The apparatus of claim 82, further causing the apparatus to:
47 estimating, by the UE, at least one next network connect state time requirement, wherein the UE required assistance information is the at least one next network connect state time requirement.
84. The apparatus of claim 82, further causing the apparatus to: determining, by the UE, a subset of relevant cell re-selection information based on UE capability, wherein the UE required assistance information is relevant cell reselection information.
85. The apparatus of claim 84, wherein the cell re-selection information is associated with at least one of intra-frequency re-selection, inter-frequency re-selection, and inter- RAT re-selection.
86. The apparatus of claim 82, wherein the UE required assistance information is associated with reference signal information.
87. The apparatus of claim 86, further causing the apparatus to: determining, by the UE, a subset of relevant reference signals based on at least one of a time requirement and a spatial domain requirement, wherein the UE required assistance information includes the subset of relevant reference signals.
88. The apparatus of claim 86 or claim 87, wherein the at least one relevant segment is determined based on a reference signal’s location in time.
89. The apparatus of claim 82, wherein the at least one relevant segment includes satellite assistance information.
90. The apparatus of any of claim 82 to claim 89, wherein the SIB segment mapping associates each of a plurality of SIB occasions to a coverage time of at least one of the network device and at least one second network device.
48
91. The apparatus of claim 90, wherein a coverage time interval of at least one of the network device and at least one second network device is based on the coverage time and a movement vector.
92. The apparatus of any of claim 82 to claim 91, wherein the SIB segment mapping indicates a time interval with no network device coverage.
93. The apparatus of any of claim 82 to claim 92, further causing the apparatus to: switching, by the UE, from an inactive state to an active state based on information associated with a coverage time of a network device included in the at least one relevant segment.
94. The apparatus of any of claim 82 to claim 93, wherein the UE determines not to receive the broadcast, by the network device, of a system information message that does not include the at least one relevant segment.
95. The apparatus of any of claim 82 to claim 94, further causing the apparatus to: communicating, by the UE to the network device, a request for the at least one relevant segment.
96. The apparatus of claim 95, wherein the receiving of the SIB segment mapping is in response to the communicated request.
97. The apparatus of claim 96, wherein the SIB segment mapping is received in a message communicated to one of the UE or a group of identified UEs.
98. The apparatus of any of claim 95 to claim 97, wherein the request for the SIB segment mapping includes information about the UE, and the received SIB segment mapping includes a modified mapping based on the information about the UE.
49
99. An apparatus comprising: at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to: generate, by a network device, a system information broadcast (SIB) segment mapping; broadcast, by the network device, the SIB segment mapping; generate, by the network device, a plurality of datasets each including network information; and broadcast, by the network device, a plurality of segmented system information messages each including at least one of the plurality of datasets.
100. The apparatus of claim 99, wherein the network information includes nonterrestrial network (NTN) information.
101. The apparatus of claim 99, wherein the network information includes at least one of intra-frequency information, inter-frequency information, and inter-RAT information.
102. The apparatus of claim 101, wherein the intra-frequency information includes cell priority, the inter-frequency information includes frequency range, and the inter-RAT information includes a radio access technology (RAT) associated with a neighbor cell.
103. The apparatus of claim 99, wherein the network information includes a list of reference signal configurations.
104. The apparatus of claim 99, wherein the SIB segment mapping is configured to associate an SIB transmission occasion with different datasets, and
50 the association of the dataset with the SIB transmission occasion refers to one of a content of each dataset or a segmenting criteria used for generating of each dataset.
105. The apparatus of claim 99, further causing the apparatus to: receiving, by the network device from a user equipment (UE), a request for at least one relevant segment; and communicating, by the network device to the UE, the at least one relevant segment in response to the request.
106. The apparatus of claim 105, wherein the SIB segment mapping is modified based on information about the UE.
107. The apparatus of any of claim 99 to claim 106, wherein the generating of the SIB segment mapping includes: generating, by the network device, a dataset of network devices that are relevant for a coverage area, wherein the dataset is valid for a period of time; dividing the period of time into a number of segments of equal time duration; associating a subset of the network devices with each of the segments; and including satellite information associated with each of the subset of the network devices in the corresponding segment.
108. The apparatus of any of claim 99 to claim 107, further causing the apparatus to: segmenting at least one block of satellite information based on the SIB segment mapping.
51
PCT/EP2022/050332 2022-01-10 2022-01-10 Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios WO2023131420A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/050332 WO2023131420A1 (en) 2022-01-10 2022-01-10 Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2022/050332 WO2023131420A1 (en) 2022-01-10 2022-01-10 Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios

Publications (1)

Publication Number Publication Date
WO2023131420A1 true WO2023131420A1 (en) 2023-07-13

Family

ID=80050824

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2022/050332 WO2023131420A1 (en) 2022-01-10 2022-01-10 Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios

Country Status (1)

Country Link
WO (1) WO2023131420A1 (en)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019030732A1 (en) * 2017-08-11 2019-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Broadcasting of positioning information in wireless communication networks

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019030732A1 (en) * 2017-08-11 2019-02-14 Telefonaktiebolaget Lm Ericsson (Publ) Broadcasting of positioning information in wireless communication networks

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
NOKIA ET AL: "Discussion on remaining aspects of discontinuous coverage in IoT NTN", vol. RAN WG2, no. Electronic; 20220117 - 20220125, 11 January 2022 (2022-01-11), XP052094122, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_116bis-e/Docs/R2-2201009.zip R2-2201009 Discussion on remaining aspects of discontinuous coverage in IoT NTN.docx> [retrieved on 20220111] *
NOKIA ET AL: "IDLE mode aspects for Non-Terrestrial Networks (NTN)", vol. RAN WG2, no. Electronic; 20201102 - 20201113, 22 October 2020 (2020-10-22), XP051941414, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG2_RL2/TSGR2_112-e/Docs/R2-2009774.zip R2-2009774 IDLE mode aspects for Non-Terrestrial Networks (NTN).docx> [retrieved on 20201022] *
QUALCOMM INCORPORATED: "Broadcast of Positioning Assistance Data", vol. RAN WG2, no. Prague, CZ; 20171009 - 20171013, 8 October 2017 (2017-10-08), XP051343051, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN2/Docs/> [retrieved on 20171008] *

Similar Documents

Publication Publication Date Title
US11323944B2 (en) Virtual tracking or registration areas for non terrestrial networks
US10674380B2 (en) On-demand system information for wireless terminal in connected state
US20230076409A1 (en) Methods, apparatus, and systems for operational procedures supporting a zero-energy air-interface
US20180049080A1 (en) Network controlled sharing of measurement gaps for intra and inter frequency measurements for wireless networks
US20210345211A1 (en) Timing advance for rach-less backhaul handover
US20240007840A1 (en) Method for secondary cell state configuration, user equipment, and storage medium
US20230209420A1 (en) Transmission parameter obtaining method, apparatus, and system
WO2012127279A1 (en) Switching cells on and off on a need basis in a wireless communications system
CN115868211A (en) Tracking area code transmissions in non-terrestrial networks
US11895542B2 (en) Reducing handover interruption with two transmitters and receivers
US20230276324A1 (en) Cell Reselection-Related Information Associated with Network Slice or Closed Access Group For Wireless Networks
US20230403591A1 (en) Group based beam reporting
CN110115097A (en) Method and apparatus for supporting wave beam management within a wireless communication network
EP3790323A1 (en) Triggering channel state information outside active time
US20230379865A1 (en) Request procedure for positioning reference signals for wireless networks
US20220232440A1 (en) Configuration of carriers for non-mobility related purposes
WO2017176293A1 (en) Dynamic deactivation of cells while accomodating idle user devices in a wireless network
WO2022027407A1 (en) Methods, apparatus and systems for scheduling and transmission of system information in wireless communication
US20230164646A1 (en) Utilization of regular measurements for early measurement reporting
WO2023131420A1 (en) Efficient usage of si signalling for neighbor satellite indication in sparse coverage scenarios
EP4070619A1 (en) Multi-usim ue assistance information with unavailable time
US20240147285A1 (en) User context aware ml based csi measurement relaxation
WO2023046306A1 (en) Conditional device paging in discontinuous reception (drx)
US20240015759A1 (en) Adaptive Configuration for Monitoring a Downlink Control Channel
WO2019028838A1 (en) Network slice-specific paging cycles for wireless networks

Legal Events

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

Ref document number: 22700907

Country of ref document: EP

Kind code of ref document: A1