Terminal and communication method

Abstract

A terminal according to the present invention comprises: a reception unit configured so that a SS / PBCH block (SSB) is received and a physical downlink control channel (PDCCH) for transmitting downlink control information (DCI) for scheduling one or more physical download shared channels (PDSCH) for transmitting system information block 1 (SIB1) or another SIB is received in a non-terrestrial network (NTN); and a control unit configured so that SIB1 or the other SIB is divided, and SIB1 or the other SIB is acquired from the one or more PDSCH including the divided SIB1 or other SIB.

Description

Terminal and communication method

[0001] The present invention relates to a terminal and a communication method in a wireless communication system.

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that satisfy the requirements of a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (for example, Non-Patent Document 1).

[0003] Currently, non-terrestrial networks (NTNs) are being considered, which use non-terrestrial networks such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost considerations (e.g., Non-Patent Documents 2 and 3).

[0004] 3GPP TS 38.300 V18.0.0 (2023-12) 3GPP TR 38.821 V16.2.0 (2023-03) Konishi et al., "A Study on Downlink Spectrum Sharing in HAPS Mobile Communication Systems," IEICE General Conference, B-17-1, 2020 3GPP TS 38.211 V18.1.0 (2023-12) 3GPP TSG RAN Meeting #102, RP-234078, December 2023

[0005] Upper layer packets (e.g., system information) may be segmented into multiple transport blocks. An efficient scheduling mechanism with segmentation needs to be defined. If no scheduling mechanism is defined, it will be difficult or impossible to apply segmentation.

[0006] The present invention has been made in view of the above points, and aims to introduce a scheduling mechanism that supports the division of an upper layer packet into multiple transport blocks.

[0007] According to the disclosed technology, there is provided a terminal in an NTN (Non-Terrestrial Network), which includes: a receiving unit that receives an SSB (SS / PBCH Block) and receives a PDCCH (Physical Downlink Control Channel) that carries Downlink Control Information (DCI) that schedules one or more PDSCHs (Physical Downlink Shared Channels) that carry SIB1 (System Information Block 1) or other SIBs; and a control unit that applies segmentation to the SIB1 or other SIBs and acquires the SIB1 or other SIBs from the one or more PDSCHs that include the segmented SIB1 or other SIBs.

[0008] According to the disclosed technique, a scheduling mechanism can be introduced that supports splitting a higher layer packet into multiple transport blocks.

[0009] 1 is a diagram showing an example (1) of an NTN. 2 is a diagram showing an example (2) of an NTN. 3 is a diagram showing an example (3) of an NTN. 4 is a diagram showing an example (4) of an NTN. 5 is a diagram showing an example (5) of an NTN. 6 is a flowchart for explaining an example of PDSCH reception in an embodiment of the present invention. 7 is a diagram showing an example (1) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied in an embodiment of the present invention. 8 is a diagram showing an example (2) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied in an embodiment of the present invention. 9 is a diagram showing an example (3) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied in an embodiment of the present invention. 10 is a diagram showing an example (4) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied in an embodiment of the present invention. 11 is a diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. 12 is a diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. 13 is a diagram showing an example of the hardware configuration of a base station 10 or a terminal 20 in an embodiment of the present invention. 14 is a diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0010] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0011] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR), unless otherwise specified.

[0012] In addition, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In addition, the above-mentioned terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, etc. However, even if a signal is used in NR, it is not necessarily stated as "NR-".

[0013] Furthermore, in the embodiment of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0014] Furthermore, in the embodiments of the present invention, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0015] FIG. 1 shows an example of an NTN (1). A Non-Terrestrial Network (NTN) uses non-terrestrial devices, such as satellites, to provide services to areas that cannot be covered by terrestrial 5G networks, primarily due to cost considerations. NTN can also provide more reliable services. For example, it is expected to be applied to IoT (Internet of Things), ships, buses, trains, and critical communications. NTN also has scalability through efficient multicast or broadcast.

[0016] As an example of an NTN, as shown in FIG. 1, a satellite 10A can retransmit signals transmitted from a terrestrial base station 10B to provide service to areas where terrestrial base stations are not located, such as mountainous regions.

[0017] The terrestrial 5G network may have the following configuration. The terrestrial 5G network includes one or more base stations 10 and terminals 20. The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminals 20. The physical resources of the wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminals 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, via NR-PBCH, and is also called broadcast information.

[0018] The base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via an SCell (Secondary Cell) and a PCell (Primary Cell) using CA (Carrier Aggregation).

[0019] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, an M2M (Machine-to-Machine) communication module, etc. The terminal 20 receives control signals or data from the base station 10 via DL and transmits control signals or data to the base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.

[0020] Figure 2 shows an example of an NTN (2). The area of ​​each cell or beam in an NTN is much larger than that of a terrestrial network (TN). Figure 2 shows an example of an NTN configured with retransmission by satellite. The connection between the satellite 10A and the NTN gateway 10B is called a feeder link, and the connection between the satellite 10A and the UE 20 is called a service link.

[0021] 2, the difference in delay between UE 20A on the near side and UE 20B on the far side is, for example, 10.3 ms in the case of GEO (Geosynchronous Orbit) and 3.2 ms in the case of LEO (Low Earth Orbit). Also, the beam size in NTN is, for example, 3500 km in the case of GEO and 1000 km in the case of LEO.

[0022] FIG. 3 is a diagram showing an example (3) of an NTN. As shown in FIG. 3, an NTN is realized by a satellite in space or a flying object in the air. For example, a GEO satellite may be a satellite located at an altitude of 35,786 km and having a geostationary orbit. For example, a LEO satellite may be a satellite located at an altitude of 500-2000 km and orbiting every 88-127 minutes. For example, a HAPS (High Altitude Platform Station) may be a flying object located at an altitude of 8-50 km and performing circular flight.

[0023] As shown in Figure 3, GEO satellites, LEO satellites, and HAPS aircraft may be connected to ground stations (gNBs) via gateways. The service areas may be larger in the order of HAPS, LEO, and GEO.

[0024] For example, NTN can extend the coverage of 5G networks to unserved or served areas. Furthermore, for example, NTN can improve the continuity, availability, and reliability of services on ships, buses, trains, or other critical communications. The NTN may be signaled by transmitting dedicated parameters to the terminal 20, and the dedicated parameters may be, for example, parameters related to determining a timing advance (TA) based on information related to satellites or aircraft.

[0025] Figure 4 is a diagram showing an example of an NTN (4). Figure 4 shows an example of an NTN network architecture assumed in the case of transparent payload. As shown in Figure 4, a CN (Core Network) 10D, a gNB 10C, and a gateway 10B are connected. The gateway 10B is connected to a satellite 10A via a feeder link. The satellite 10A is connected to a terminal 20A or a VSAT (Very Small Aperture Terminal) 20B via a service link. An NR Uu is established between the gNB 10C and the terminal 20A or the VSAT 20B.

[0026] Furthermore, the assumed network architecture of the NTN may employ FDD or may be capable of TDD. Terrestrial cells may be fixed or mobile. The terminal 20 may have the capability to support the Global Navigation Satellite System (GNSS). For example, a power class 3 handheld device may be assumed in FR1. At least in FR2, a VSAT device may be assumed.

[0027] The NTN network architecture may also assume regenerative payloads. For example, gNB functionality may be mounted on a satellite or air vehicle. Alternatively, a gNB-DU may be mounted on a satellite or air vehicle, and a gNB-CU may be deployed as a ground station.

[0028] Figure 5 is a diagram showing an example of an NTN (5). As shown in Figure 5, the TA in the NTN includes a common TA corresponding to the distance from the satellite / HAPS 10A to the reference point (RP) in the feeder link, and a UE-specific TA corresponding to the distance from the satellite / HAPS 10A to the UE 20 in the service link. The TA of the service link is a UE-specific TA and varies depending on the location of the UE 20. Note that the feeder link includes a delay that is transparent to the user and corresponds to the distance from the reference point to the gNB / gateway 10B.

[0029] The reference point for UL synchronization may be determined by the network implementation. For example, the reference point may be any point on the satellite, gNB, GW, or feeder link. At the gNB or GW, the DL and UL time domains may be aligned to facilitate implementation. At the satellite, UE operations related to common TA may not be performed to reduce UE load.

[0030] The TA in NTN may be calculated, for example, as TTA = (NTA + NTA, UE-specific + NTA, common + NTA, offset) x TC (see Non-Patent Document 4).

[0031] NTA is 0 for PRACH and is notified by a TA command by MAC-CE (Medium Access Control - Control Element). NTA may be a closed-loop TA.

[0032] NTA,UE-specific is a TA specific to the UE. NTA,UE-specific may be a value estimated by the UE itself to compensate in advance for the delay of the service link. NTA,UE-specific is calculated based on the UE's position and the celestial orbit of the serving satellite.

[0033] NTA,common is a common TA controlled by the network. Hereinafter, NTA,common is also referred to as common TA. For example, if the reference point is a satellite, a value of 0 is supported. NTA,offset may be a fixed value used for TA calculation defined in the specification.

[0034] Downlink coverage extension in NTNs has been considered (see Non-Patent Document 5). Also, taking into account NTN deployment constraints such as payload power limitations, large satellite footprints, and limited feeder link bandwidth, the downlink coverage provides optimized performance, especially when addressing handset terminals (including smartphones with -5.5 dBi antenna gain).

[0035] DL coverage extension is needed to accommodate satellite payload constraints where limited power and limited feeder link bandwidth may not allow all beams to be activated at a given time with the "nominal" EIRP density (see 3GPP TS 2.0, section 6.1.1) per beam, while maximizing the number of beams that can be activated simultaneously and ensuring that all user terminals across the satellite footprint can be served, while ensuring that all satellite radio cells remain viable even when there is no traffic, allowing new users to join or preventing impact on end-user QoS.

[0036] DL coverage extension is a link level improvement to improve the link margin of selected physical channels to accommodate the reduction in EIRP in FR1-NTN, and link margin improvement for physical channels (e.g., PDSCH and PDCCH) can be considered without affecting the SSB design.

[0037] DL coverage extension also takes system level considerations into account to support efficient dynamic and flexible power sharing between beams or different beam patterns / sizes (i.e., wide or narrow) across the satellite footprint for FR1-NTN and FR2-NTN.

[0038] A beneficial downlink coverage extension is being considered that targets support for additional reference satellite payload parameters covering both Geostationary Orbit (GSO) and non-GSO (NGSO) constellations operating in FR1-NTN or FR2-NTN.

[0039] Assuming power sharing between satellite beams or different satellite beam patterns / sizes (i.e., wide or narrow) across the satellite footprint, additional reference satellite payload parameters are defined whereby satellite beams may not all be active simultaneously or may be active at less than the nominal EIRP density per satellite beam (see 3GPP TS 2.0, section 6.1.1) due to limited power and limited feeder link bandwidth.

[0040] Corresponding power sharing assumptions, required link-level and system-level assessment methods, and associated KPIs (Key Performance Indicators) for coverage assessment are defined to enable identification of physical channel / signal and system-level aspects requiring enhancement.

[0041] Consider and, if necessary, identify solutions including link-level extensions for FR1-NTN (e.g., for PDCCH, PDSCH) and / or system-level extensions for FR1-NTN and / or FR2-NTN to enable dynamic and flexible power sharing between satellite beams or between different satellite beam patterns / sizes (i.e., wide or narrow) across the satellite footprint.

[0042] For example, SSB channel enhancement is not considered. For example, in the case of a smartphone in FR1-NTN, the terminal antenna gain is assumed to be -5.5 dBi, the terminal is assumed to be a full-duplex terminal, and at least 2 Rx is considered in the terminal. For example, the NGSO that is given priority may be LEO Set-1 @ 600 km. For example, Rel-18 network energy saving technology should be considered as a baseline in system-level studies.

[0043] In NTN, SIB reception according to the existing NR specifications may not provide sufficient Block Error Rate (BLER) performance, so some extensions may be introduced to extend the coverage of SIB1. For example, coverage extensions of SIB1, SIB19, SIB25, SIB6, SIB7, or any other SIB may be introduced.

[0044] For example, according to the LLS results on PDSCH SIB1 coverage evaluation collected from different sources, it is as follows:

[0045] For PDSCH carrying SIB1 option 1 (payload size 800 bits), it is observed that the required SNR (Signal to noise ratio) is equal to -5.8 dB (14 sources) on average.

[0046] For PDSCH carrying SIB1 option 2 (payload size 1280 bits), it is observed that the required SNR is equal to -3.4 dB (12 sources) on average.

[0047] For parameters LEO 600 km, Set 1-1FR1 and 1-2FR1, 14 sources observed no coverage gap for PDSCH with SIB1 option 1. The coverage margin averages about 3.9 dB compared to a CNR (Carrier-to-Noise Ratio) of −1.9 dB. 12 sources observed no coverage gap for PDSCH with SIB1 option 2. The coverage margin averages about 1.5 dB compared to a CNR of −1.9 dB.

[0048] For parameters LEO 600 km, Set 1-3FR1, 11 sources observed a coverage gap for PDSCH with SIB1 option 1. Compared to a CNR of -9.9 dB, the coverage gap averages about 4.1 dB. One source observed no coverage gap for PDSCH with SIB1 option 1. Compared to a CNR of -9.9 dB, the coverage margin is 3.4 dB. Ten sources observed a coverage gap for PDSCH with SIB1 option 2. Compared to a CNR of -9.9 dB, the coverage gap averages about 6.5 dB.

[0049] Note that some results assumed the combination of SIB1 (SIB1 is repeated within 160 ms), and some results did not assume the combination of SIB1. Note that the above results were obtained independently of the performance of other channels or signals, and do not imply successful reception of other channels or signals before or after detection of the PDSCH carrying SIB1.

[0050] According to the LLS results on PDSCH SIB19 coverage evaluation collected from different sources, the following are found:

[0051] It is observed that the SNR required for the PDSCH carrying SIB19 is equal to -6.9 dB (14 sources) on average. With parameters LEO600 km, Set1-1FR1 and 1-2FR1, 12 sources observed no coverage gap for the PDSCH with SIB19. The coverage margin is about 4.2 dB on average compared to a CNR of -1.9 dB. With parameters LEO600 km, Set1-3FR1, 10 sources observed a coverage gap for the PDSCH with SIB19. The coverage gap is about 3.5 dB on average compared to a CNR of -9.9 dB.

[0052] Note that all the above results did not assume the combination of SIB19. Note that the above results were obtained independently of the performance of other channels or signals, and do not imply successful reception of other channels or signals before or after detection of the PDSCH carrying SIB19.

[0053] In a practical NTN, the duration for which each beam is available is limited. For example, with approximately 1000 beams per satellite, the maximum number of simultaneously active beams is expected to be approximately 200 or less. For each beam, SSB and / or SIB can only be transmitted within a limited time interval. Any coverage extension mechanism introduced for SIB needs to be feasible under the above constraints. Note that repetition may be replaced by aggregation.

[0054] Upper layer packets (e.g., system information) may be segmented into multiple transport blocks. An efficient scheduling mechanism with segmentation needs to be defined. If no scheduling mechanism is defined, it will be difficult or impossible to apply segmentation.

[0055] 6 is a flowchart illustrating an example of PDSCH reception according to an embodiment of the present invention. In step S101, the terminal 20 receives an SSB. In step S102, the terminal 20 receives a CORESET0 (Control Resource Set 0)-PDCCH. CORESET0 corresponds to the resources of the PDCCH for SIB1. In step S103, the terminal 20 receives one or more PDSCHs scheduled by DCI carried by the PDCCH. A transport block including the divided SIB1 is transmitted in each of the one or more PDSCHs. The terminal 20 may perform decoding of each transport block to obtain SIB1.

[0056] Operation 1) The case of receiving SIB1 divided into multiple transport blocks will be described below. Each portion of the divided SIB1-PDSCH is called a segment. One segment may correspond to one transport block or one PDSCH. Note that the terminal 20 may determine the number of segments, the segment length (number of symbols), and some or all of the start symbols of multiple PDSCHs (segments) carrying SIB1. The start symbols and start positions may be interchangeable. Operation 1a) In the divided SIB1-PDSCH, the number of symbols and / or segment length and / or start symbol may differ between segments. Note that SIB1-PDSCH may refer to the PDSCH carrying SIB1.

[0057] Although the initial slot includes an SSB in the figure, the initial slot does not have to include an SSB. Although the non-initial slot does not include an SSB in the figure, the non-initial slot may include an SSB.

[0058] Action 1a1) The length and / or starting symbol of the first segment may be signaled in the scheduling DCI. Action 1a2-A) The length and / or starting symbol of the subsequent segments may be fixed. For example, the length of the subsequent segments may be 14 symbols, which is the maximum available length. For example, the starting position of the subsequent segments may be the first symbol of a slot. For example, the starting position of the subsequent segments may be the symbol immediately after the CORESET0 symbol in the slot. For example, the starting position of the subsequent segments may be the symbol immediately after the SSB symbol in the slot.

[0059] 7 is a diagram showing an example (1) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied according to an embodiment of the present invention. FIG. 7 is an example showing operation 1a1) and operation 1a2-A). As shown in FIG. 7, the DCI carried by the CORESET0-PDCCH may schedule the first segmented SIB1-PDSCH (segment 0 (TB0)). Also, as shown in FIG. 7, the first SIB1-PDSCH may start immediately after the SSB. Also, as shown in FIG. 7, the segmented SIB1-PDSCH (segment 1 (TB1)) in the subsequent slot may start at the beginning of the slot and may have a length of 14 symbols.

[0060] Action 1a2-B) The lengths and / or starting symbols of the first and subsequent segments may be signaled within the same scheduling DCI. i.e. a single DCI may schedule more than one PDSCH segment. For example, the Start and Length Indicator Values ​​(SLIVs) of the first and subsequent segments may be signaled. Alternatively, the start positions of the first and subsequent segments may be signaled, with the length of the segments being the maximum available length. For example, the same SLIV may be applied to the first and subsequent segments.

[0061] For example, each segment may have the same length and start at the symbol immediately following the end symbol of the previous segment, i.e., a mechanism such as PUSCH repetition type B may be used.

[0062] The scheduling DCI may allow scheduling of up to 14 starting positions plus length. For example, the first or nominal segment may not cross a slot boundary.

[0063] The scheduling DCI may allow scheduling of up to 27 starting positions plus length. For example, the first or nominal segment may cross a slot boundary.

[0064] A segment that crosses a slot boundary may be split into two actual segments.

[0065] 8 is a diagram showing an example (2) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied according to an embodiment of the present invention. FIG. 8 is an example showing operation 1a1) and operation 1a2-B). As shown in FIG. 8, the DCI carried by the CORESET0-PDCCH may schedule the first segmented SIB1-PDSCH (segment 0 (TB0)) and the subsequent segmented SIB1-PDSCH (segment 1 (TB1)). Also, as shown in FIG. 8, the first SIB1-PDSCH segment may start immediately after the SSB. Also, as shown in FIG. 8, the SIB1-PDSCH segment in the subsequent slot may start at the beginning of the slot and may be 14 symbols in length.

[0066] Action 1a2-C) The length and / or starting symbol of the first and subsequent segments may be signaled in different scheduling DCIs, e.g., when the number of segments is signaled by the first PDCCH, each subsequent SIB1-PDSCH segment may be associated with another PDCCH and DCI.

[0067] 9 is a diagram showing an example (3) of receiving a PDSCH carrying an SIB1 to which segmentation has been applied in an embodiment of the present invention. FIG. 9 is an example showing operation 1a1) and operation 1a2-C). As shown in FIG. 9, the DCI carried by the CORESET0-PDCCH schedules the first SIB1-PDSCH, and each subsequent SIB1-PDSCH segment may be scheduled by another CORESET0-PDCCH. Also, as shown in FIG. 9, the first SIB1-PDSCH segment may start immediately after the SSB. Also, as shown in FIG. 9, the SIB1-PDSCH segments in subsequent slots may start immediately after the CORESET0-PDCCH that schedules the segment.

[0068] Action 1a2-D) The length and / or starting symbol of a subsequent segment may be determined based on whether an SSB is transmitted in that slot. For example, if an SSB is transmitted, the SLIV may be the same as that of the first segment, and if an SSB is not transmitted, the SLIV may be a fixed value. For example, if an SSB is transmitted in both the first slot and the slot in which the segment is transmitted, the SLIV may be the same as that of the first segment, and if not, the SLIV may be a fixed value.

[0069] Action 1a3) The transport block size (TBS) may be determined based on at least one of 1)-5) below.

[0070] 1) The TBS of the first segment may be determined based on the starting symbol and length of the segment.

[0071] 2) The TBS of a subsequent segment may be the same as the TBS of the first segment, regardless of the starting symbol and length of the subsequent segment, or the TBS of a subsequent segment may be the same as the TBS of the first segment, regardless of the starting symbol and length of the subsequent segment.

[0072] 3) The TBS of the subsequent segment may be the same as the TBS of the initial segment determined based on the starting symbol and length of the initial segment. Alternatively, the TBS of the subsequent segment may be the same as the TBS of the initial segment determined based on the starting symbol and length of the subsequent segment. For example, this may be applied to operation 1a2-B) or operation 1a2-C).

[0073] 4) The TBS of a subsequent segment may be the same as the TBS of the first segment if the scheduling DCI indicates an MCS index associated with "reserved". For example, this may apply to action 1a2-B) or action 1a2-C). 5) The TBS of a subsequent segment may be the same as or different from the TBS of the first segment. Also, the TBS of segments may be the same or different between segments.

[0074] Action 1b) When DCI format 1_0 in CORESET0 is used for notification related to SIB1-PDSCH splitting, for example in action 1a), at least one of the following fields may be included in the notification:

[0075] Action 1b1) A Time Domain Resource Allocation (TDRA) field may be included in the notification, for example one or more MSBs may be defined for the field.

[0076] Action 1b2) An MCS field may be included in the field. For example, one or more MSBs may be defined in the field. In this case, the maximum value indicated by the remaining consecutive bits including the LSBs may be associated with QPSK and a "reserved" target code rate (and spectral efficiency). That is, the maximum value may be associated with MCS index 29 in Table 1.

[0077]

[0078] For example, if three consecutive bits including the LSB are used for MCS indication, MCS index 0, 1, 2, 3, 4, 5, 6 or 29 in Table 1 can be indicated.

[0079] Action 1b3) One or more reserved bits may be included in the notification. For example, one or more new dedicated fields may be defined for the reserved bits. For example, a field indicating segment-related information may be defined. The segment-related information may be, but is not limited to, the segment number, the segment index, or the segment type. For example, a TDRA field for the following segment may be defined.

[0080] Operation 2) The case of receiving another SIB will be described below. The other SIB may be, for example, SIB19, SIB25, SIB6, SIB7, etc., and will hereinafter be referred to as "SIBX." The terminal 20 receives a PDCCH that schedules the SIBX. The terminal 20 receives a PDSCH that carries the SIBX to which segmentation has been applied, which is scheduled by the DCI carried by the PDCCH. Note that the terminal 20 may determine the number of segments, the length of the segments (number of symbols), and some or all of the start symbols of the PDSCH that carries the SIBX. The start symbol and start position may be interchangeable.

[0081] Action 2a) In the SIBX-PDSCH segments, the number of symbols and / or the length and / or starting symbol of the segments can vary between segments. Note that SIBX-PDSCH may refer to the PDSCH carrying the SIBX.

[0082] Although the initial slot includes an SSB in the figure, the initial slot does not have to include an SSB. Although the non-initial slot does not include an SSB in the figure, the non-initial slot may include an SSB.

[0083] Action 2a1) The length and / or starting symbol of the first segment may be signaled in the scheduling DCI.

[0084] Action 2a1′) The length and / or starting symbol of the initial segment may be determined based on SIB1. For example, the length and / or starting symbol of the initial segment may be determined based on settings included in SIB1.

[0085] Action 2a2-A) The length and / or starting symbol of the subsequent segment may be fixed. For example, the length of the subsequent segment may be 14 symbols, which is the maximum available length. For example, the starting position of the subsequent segment may be the first symbol of a slot. For example, the starting position of the subsequent segment may be the symbol immediately after the PDCCH symbol in that slot. For example, the starting position of the subsequent segment may be the symbol immediately after the SSB symbol in that slot.

[0086] FIG. 7 is a diagram showing an example (1) of receiving a PDSCH carrying a SIBX to which segmentation has been applied according to an embodiment of the present invention. The CORESET0-PDCCH in FIG. 7 may be replaced with a PDCCH. FIG. 7 is an example showing operation 2a1) and operation 2a2-A). As shown in FIG. 7, the DCI carried by the PDCCH may schedule the first SIBX-PDSCH. Also, as shown in FIG. 7, the first SIBx-PDSCH segment may start immediately after the SSB. Also, as shown in FIG. 7, the SIBX-PDSCH segment in a subsequent slot may start at the beginning of the slot and may be 14 symbols long.

[0087] Action 2a2-B) The lengths and / or starting symbols of the first and subsequent segments may be signaled in the same Scheduling DCI. For example, the SLIVs (Start and Length Indicator Values) of the first and subsequent segments may be signaled. Alternatively, the start positions of the first and subsequent segments may be signaled, with the length of the segments being the maximum available length. For example, the same SLIV may be applied to the first and subsequent segments.

[0088] For example, each segment may have the same length and start at the symbol immediately following the end symbol of the previous segment, i.e., a mechanism such as PUSCH repetition type B may be used.

[0089] The scheduling DCI may allow scheduling of up to 14 starting positions plus length. For example, the first or nominal segment may not cross a slot boundary.

[0090] The scheduling DCI may allow scheduling of up to 27 starting positions plus length. For example, the first or nominal segment may cross a slot boundary.

[0091] A segment that crosses a slot boundary may be split into two actual segments.

[0092] FIG. 8 is a diagram showing an example (2) of receiving a PDSCH carrying a SIBX to which segmentation has been applied according to an embodiment of the present invention. The CORESET0-PDCCH in FIG. 8 may be replaced with a PDCCH. FIG. 8 is an example showing operation 2a1) and operation 2a2-B). As shown in FIG. 8, the DCI carried by the PDCCH may schedule the first SIBX-PDSCH segment and subsequent SIBX-PDSCH segments. Also, as shown in FIG. 8, the first SIBX-PDSCH segment may start immediately after the SSB. Also, as shown in FIG. 8, the SIBX-PDSCH segment in the subsequent slot may start at the beginning of the slot and may be 14 symbols long.

[0093] Action 2a2-C) The length and / or starting symbol of the first and subsequent segments may be signaled in different scheduling DCIs. For example, when the number of segments is signaled by the first PDCCH, each subsequent SIBX-PDSCH segment may be associated with another PDCCH and DCI that may schedule the same transport block and signal a SLIV.

[0094] Figure 9 is a diagram showing an example (3) of receiving a PDSCH carrying a SIBX to which segmentation has been applied according to an embodiment of the present invention. The CORESET0-PDCCH in Figure 9 may be replaced with a PDCCH. Figure 9 is an example showing operation 2a1) and operation 2a2-C). As shown in Figure 9, the DCI carried by the PDCCH may schedule the first SIBX-PDSCH segment, and each subsequent SIBX-PDSCH segment may be scheduled by another PDCCH. Also, as shown in Figure 9, the first SIBX-PDSCH segment may start immediately after the SSB. Also, as shown in Figure 9, the SIBX-PDSCH segments in subsequent slots may start immediately after the PDCCH that schedules the segment.

[0095] Action 2a2-D) The length and / or starting symbol of a subsequent segment may be determined based on whether an SSB is transmitted in that slot. For example, if an SSB is transmitted, the SLIV may be the same as that of the first segment, and if an SSB is not transmitted, the SLIV may be a fixed value. For example, if an SSB is transmitted in both the first slot and the slot in which the segment is transmitted, the SLIV may be the same as that of the first segment, and if not, the SLIV may be a fixed value.

[0096] Action 2a2-E) The length and / or starting symbol of the subsequent segment may be determined based on SIB1. For example, the length and / or starting symbol of the subsequent segment may be determined based on the settings included in SIB1.

[0097] Action 2a3) The transport block size (TBS) may be determined based on at least one of 1)-4) below.

[0098] 1) The TBS of the first segment may be determined based on the starting symbol and length of the segment.

[0099] 2) The TBS of a subsequent segment may be the same as the TBS of the first segment, regardless of the starting symbol and length of the subsequent segment, or the TBS of a subsequent segment may be the same as the TBS of the first segment, regardless of the starting symbol and length of the subsequent segment.

[0100] 3) The TBS of the subsequent segment may be the same as the TBS of the initial segment determined based on the starting symbol and length of the initial segment. Alternatively, the TBS of the subsequent segment may be the same as the TBS of the initial segment determined based on the starting symbol and length of the subsequent segment. For example, this may be applied to operation 2a2-B) or operation 2a2-C).

[0101] 4) The TBS of a subsequent segment may be the same as the TBS of the first segment if the scheduling DCI indicates an MCS index associated with "reserved". For example, this may apply to action 2a2-B) or action 2a2-C). 5) The TBS of a subsequent segment may be the same as or different from the TBS of the first segment. Also, the TBS of segments may be the same or different between segments.

[0102] Action 2b) When DCI format 1_0 is used for a notification related to a SIBX-PDSCH segment, for example in action 2a), at least one of the following fields may be included in the notification:

[0103] Action 2b1) A Time Domain Resource Allocation (TDRA) field may be included in the notification, for example one or more MSBs may be defined for this field.

[0104] Action 2b2) An MCS field may be included in the field. For example, one or more MSBs may be defined in the field. In this case, the maximum value indicated by the remaining consecutive bits including the LSBs may be associated with QPSK and a "reserved" target code rate (and spectral efficiency). That is, the maximum value may be associated with MCS index 29 in Table 1.

[0105] For example, if three consecutive bits including the LSB are used for MCS indication, MCS index 0, 1, 2, 3, 4, 5, 6 or 29 in Table 1 can be indicated.

[0106] Action 2b3) One or more reserved bits may be included in the notification. For example, one or more new dedicated fields may be defined for the reserved bits. For example, a field indicating segment-related information may be defined. The segment-related information may be, but is not limited to, the segment number, the segment index, or the segment type. For example, a TDRA field for the following segment may be defined.

[0107] Action 2b4) One or more fields may be determined based on SIB1. For example, one or more fields may be determined based on settings included in SIB1.

[0108] Operation 3) The above-mentioned operations 1) and 2) may be applied or executed as follows. Note that SIB19 may be replaced with other SIBs (e.g., SIB6, SIB7, i.e., SIBs related to Earthquake Early Warnings, etc.). Furthermore, other SIBs (e.g., SIB6, SIB7, i.e., SIBs related to Earthquake Early Warnings, etc.) may be applied or executed together with SIB19.

[0109] Action 3a) The same action may be applied even when receiving different SIBs.

[0110] Action 3b) Different actions may be applied between the reception of two SIBs. For example, different actions may be applied between SIB1 and SIB19. For example, different actions may be applied between SIB1 and other SIBs. For example, different actions may be applied between SIB1 and / or SIB19 and other SIBs (i.e., SIBs other than SIB1 and SIB19).

[0111] Action 3c) Reception of SIB19 may be treated independently from reception of other SIBs. For example, a System Information Indicator (SII) field = 0 may mean SIB1 or SIB19, and SII field = 1 may mean other SIBs (i.e., excluding SIB1 and SIB19). For example, the SII field may consist of 2 bits. SII = 00 may mean SIB1, SII = 01 may mean SIB19, SII = 10 may mean other SIBs (i.e., excluding SIB1 and SIB19), and SII = 11 may mean "reserved".

[0112] Operation 4) The division may be performed with repetitions. In the above operations, "segment" may be replaced with "repetition." Each repetition or each segment may be repeated consecutively in the time domain or may be repeated non-consecutively in the time domain.

[0113] 10 is a diagram showing an example (4) of receiving a PDSCH carrying a segmented SIB1 according to an embodiment of the present invention. As shown in (a), a repetition of a segment may be transmitted followed by a repetition of the next segment. Also, as shown in (b), one repetition of all segments may be transmitted followed by a repetition of all segments.

[0114] According to the above-described embodiment, the terminal 20 can receive system information for connecting to the divided NTN and connect to the NTN.

[0115] That is, a scheduling mechanism can be introduced that supports splitting upper layer packets into multiple transport blocks.

[0116] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0117] <Base Station 10> Fig. 11 is a diagram showing an example of the functional configuration of the base station 10 according to the embodiment of the present invention. As shown in Fig. 11, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 11 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations according to the embodiment of the present invention.

[0118] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 side and transmitting the signal wirelessly. The transmitter 110 also transmits inter-network node messages to other network nodes. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of higher layers from the received signals. The transmitter 110 also has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0119] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to communication in the NTN.

[0120] As described in the embodiments, the control unit 140 controls communication in the NTN. The control unit 140 also controls communication with the terminal 20 based on a UE capability report regarding radio parameters received from the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0121] <Terminal 20> Fig. 12 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Fig. 12, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 12 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention.

[0122] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 wirelessly receives various signals and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 120 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0123] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to communication in the NTN.

[0124] As described in the embodiments, the control unit 240 controls communications in the NTN. The signal transmission functional unit in the control unit 240 may be included in the transmitting unit 210, and the signal reception functional unit in the control unit 240 may be included in the receiving unit 220.

[0125] (Hardware Configuration) The block diagrams (FIGS. 11 and 12) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0126] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0127] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 13 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0128] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0129] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0130] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0131] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 11 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 12 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0132] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0133] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0134] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0135] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0136] Furthermore, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0137] Furthermore, the base station 10 and the terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0138] Fig. 14 shows an example configuration of a vehicle 2001. As shown in Fig. 14, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0139] The drive unit 2002 is configured, for example, by an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0140] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2029 provided in the vehicle 2001. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0141] The signals from the various sensors 2021 to 2029 include a current signal from a current sensor 2021 that senses the current of the motor, a front or rear wheel rotation speed signal obtained by a rotation speed sensor 2022, a front or rear wheel air pressure signal obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0142] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing (outputting) various types of information, such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information acquired from external devices via the communication module 2013 or the like to provide various types of multimedia information and multimedia services to the occupants of the vehicle 2001. The information service unit 2012 may include input devices (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, a touch panel, etc.) that accept input from the outside, and may also include output devices (e.g., a display, a speaker, an LED lamp, a touch panel, etc.) that output information to the outside.

[0143] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0144] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0145] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0146] The communication module 2013 may transmit at least one of signals from the above-mentioned various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on the signals, and information based on input from the outside (user) obtained via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc. may be referred to as input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above-mentioned input.

[0147] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0148] (Summary of Embodiments) As described above, according to the embodiments of the present invention, there is provided a terminal in an NTN (Non-Terrestrial Network), which includes: a receiving unit that receives an SSB (SS / PBCH Block), and receives a PDCCH (Physical Downlink Control Channel) that carries DCI (Downlink Control Information) that schedules one or more PDSCHs (Physical Downlink Shared Channels) that carry SIB1 (System Information Block 1) or other SIBs; and a control unit that applies segmentation to the SIB1 or other SIBs, and acquires the SIB1 or other SIBs from the one or more PDSCHs that include the segmented SIB1 or other SIBs.

[0149] With the above configuration, the terminal 20 can receive system information for connecting to the divided NTN and connect to the NTN. That is, a scheduling mechanism that supports dividing a higher layer packet into multiple transport blocks can be introduced.

[0150] The control unit may determine, based on the DCI, a length and a start position to be applied to a first segment of a PDSCH carrying the SIB1 or another SIB. With this configuration, the terminal 20 can receive system information for connecting to a divided NTN and connect to the NTN.

[0151] The control unit may determine the length to be applied to the subsequent segment of the PDSCH carrying the SIB1 or another SIB to be the maximum available length, and may determine the start position to be applied to the subsequent segment of the PDSCH carrying the SIB1 or another SIB to be the first symbol of a slot. With this configuration, the terminal 20 can receive system information for connecting to the divided NTNs and connect to the NTNs.

[0152] The control unit may determine, based on the DCI, a length and a start position to be applied to a first segment of a PDSCH carrying the SIB1 or another SIB, and may determine, based on the DCI, a length and a start position to be applied to subsequent segments of a PDSCH carrying the SIB1 or another SIB. With this configuration, the terminal 20 can receive system information for connecting to the divided NTNs and connect to the NTNs.

[0153] The receiving unit may receive a first DCI for scheduling a first segment of a PDSCH carrying the SIB1 or another SIB and a second DCI for scheduling a subsequent segment of the PDSCH carrying the SIB1 or another SIB, and the control unit may determine a length and a starting position to be applied to the first segment of the PDSCH carrying the SIB1 or another SIB based on the first DCI, and may determine a length and a starting position to be applied to the subsequent segment of the PDSCH carrying the SIB1 or another SIB based on the second DCI. With this configuration, the terminal 20 can receive system information for connecting to the divided NTNs and connect to the NTNs.

[0154] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the following procedures in an NTN (Non-Terrestrial Network): receiving an SSB (SS / PBCH Block), and receiving a PDCCH (Physical Downlink Control Channel) carrying DCI (Downlink Control Information) that schedules one or more PDSCHs (Physical Downlink Shared Channels) that carry SIB1 (System Information Block 1) or other SIBs; and applying segmentation to the SIB1 or other SIBs, and acquiring the SIB1 or other SIBs from the one or more PDSCHs that include the segmented SIB1 or other SIBs.

[0155] With the above configuration, the terminal 20 can receive system information for connecting to the divided NTN and connect to the NTN. That is, a scheduling mechanism that supports dividing a higher layer packet into multiple transport blocks can be introduced.

[0156] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

[0157] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling), broadcast information (Master Information Block (MIB), System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0158] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0159] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0160] In this specification, a specific operation described as being performed by the base station 10 may be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME or an S-GW). Although the above example illustrates a case where there is one other network node other than the base station 10, the other network node may be a combination of multiple other network nodes (such as an MME and an S-GW).

[0161] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0162] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0163] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0164] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0165] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0166] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0167] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0168] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0169] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0170] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0171] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0172] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can also be provided with communication services by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage.

[0173] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0174] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," and the like may be used interchangeably.

[0175] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0176] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0177] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0178] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

[0179] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0180] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0181] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0182] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0183] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

[0184] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0185] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0186] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0187] Numerology may be communication parameters that apply to the transmission and / or reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, specific windowing operations performed by the transceiver in the time domain, etc.

[0188] A slot may be composed of one or more symbols (such as an Orthogonal Frequency Division Multiplexing (OFDM) symbol or a Single Carrier Frequency Division Multiple Access (SC-FDMA) symbol) in the time domain. A slot may be a time unit based on numerology.

[0189] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0190] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0191] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc. instead of a subframe.

[0192] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station performs scheduling to allocate wireless resources (such as frequency bandwidth and transmission power that can be used by each terminal 20) to each terminal 20 in TTI units. Note that the definition of TTI is not limited to this.

[0193] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0194] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0195] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0196] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and greater than or equal to 1 ms.

[0197] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of the numerology, for example, 12. The number of subcarriers included in an RB may be determined based on the numerology.

[0198] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0199] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0200] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0201] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a Common Reference Point of the carrier. PRBs may be defined in a BWP and numbered within the BWP.

[0202] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0203] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0204] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples, and various changes may be made to the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc.

[0205] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0206] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0207] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0208] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0209] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. In an NTN (Non-Terrestrial Network), a terminal having: a receiving unit that receives an SSB (SS / PBCH Block) and receives a PDCCH (Physical Downlink Control Channel) that carries DCI (Downlink Control Information) that schedules one or more PDSCHs (Physical Downlink Shared Channels) that carry SIB1 (System Information Block 1) or other SIBs; and a control unit that applies division to the SIB1 or other SIBs and acquires the SIB1 or other SIBs from the one or more PDSCHs that include the divided SIB1 or other SIBs.

2. The terminal according to claim 1, wherein the control unit determines the length and start position to be applied to the first segment of the PDSCH carrying the SIB1 or another SIB based on the DCI.

3. The terminal according to claim 1, wherein the control unit determines the length to be applied to the subsequent segment of the PDSCH carrying the SIB1 or another SIB to be the maximum available length, and determines the start position to be applied to the subsequent segment of the PDSCH carrying the SIB1 or another SIB to be the first symbol of the slot.

4. The terminal of claim 1, wherein the control unit determines the length and starting position to be applied to the first segment of the PDSCH carrying the SIB1 or another SIB based on the DCI, and determines the length and starting position to be applied to subsequent segments of the PDSCH carrying the SIB1 or another SIB based on the DCI.

5. The terminal of claim 1, wherein the receiving unit receives a first DCI for scheduling a first segment of a PDSCH carrying SIB1 or another SIB and a second DCI for scheduling a subsequent segment of a PDSCH carrying SIB1 or another SIB, and the control unit determines a length and a starting position to be applied to the first segment of a PDSCH carrying SIB1 or another SIB based on the first DCI, and determines a length and a starting position to be applied to a subsequent segment of a PDSCH carrying SIB1 or another SIB based on the second DCI.

6. A communication method in which a terminal executes the following procedures in an NTN (Non-Terrestrial Network): receiving an SSB (SS / PBCH Block) and receiving a PDCCH (Physical Downlink Control Channel) carrying DCI (Downlink Control Information) that schedules one or more PDSCHs (Physical Downlink Shared Channels) carrying SIB1 (System Information Block 1) or other SIBs; and applying segmentation to the SIB1 or other SIBs, and acquiring the SIB1 or other SIBs from the one or more PDSCHs including the segmented SIB1 or other SIBs.

Images