Method and apparatus for ss / pbch block frequency location indication

Abstract

The disclosure relates to a communication method and system for converging a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system with a technology for Internet of Things (IoT). The disclosure can be applied to smart services based on 5G communication technologies and IoT-related technologies, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. A UE in a wireless communication system is provided. The UE includes a transceiver configured to receive, from a BS, a SS / PBCH block including a PBCH using a first frequency location (GSCN-Current) through a downlink channel, the GSCN-Current being based on a set of predefined synchronization raster determined by a Global Synchronization Channel Number (GSCN). The UE also includes a processor operably connected to the transceiver, the processor configured to determine the SS / PBCH block, identify a content of the PBCH included in the determined SS / PBCH block, determine a configuration of at least one of the SS / PBCH block associated with a PDCCH including scheduling information for RMSI with respect to the GSCN-Current or the SS / PBCH block not associated with the PDCCH including scheduling information for RMSI with respect to the GSCN-Current.

Description

[0001] This case is a divisional application of the invention patent application filed on December 21, 2018, with application number 201880081964.X and invention title "Method and apparatus for indicating frequency position of SS / PBCH block". Technical Field

[0002] This application generally relates to signal indication. More specifically, this disclosure relates to SS / PBCH block frequency location indication in advanced wireless communication systems. Background Technology

[0003] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO (multiple-input multiple-output), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed in 5G communication systems. Furthermore, in 5G communication systems, development is underway to improve system networks based on advanced small cells, radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-points (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

[0004] The internet is a human-centric network of connections where humans generate and consume information. Now, the internet is evolving into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, combining IoT technology with big data processing technology through connections to cloud servers. Because IoT implementation requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). This IoT environment can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated among connected things. Through the integration and combination of existing information technology (IT) and various industrial applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0005] Consistent with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be seen as an example of the convergence between 5G and IoT technologies.

[0006] For new radio (NR) licensed spectrum, each synchronization and physical broadcasting channel (PBCH) signal block (SS / PBCH block) includes one symbol for the NR primary synchronization signal (NR-PSS), two symbols for the NR-PBCH, and one symbol for both the NR secondary synchronization signal (NR-SSS) and the NR-PBCH. These four symbols are consecutively mapped and time-division multiplexed. NR-SS is a unified design for all supported carrier frequency ranges in NR, including the NR-PSS and NR-SSS sequence designs. The transmission bandwidth of NR-PSS and NR-SSS is less than the transmission bandwidth of the entire SS / PBCH block. For initial cell selection of NR cells, the UE assumes a default SS burst set period of 20ms and uses it to detect non-independent NR cells. The network provides the UE with one SS burst set period for each frequency carrier and information for deriving measurement timing / duration. The Physical Downlink Shared Channel (PDSCH) carries the Remaining Minimum System Information (RMSI) in addition to the Master Information Block (MIB). This PDSCH contains scheduling information carried by the corresponding Physical Downlink Control Channel (PDCCH). The Control Resource Set (CORESET) used to receive the Common Control Channel needs to be configured and can be transmitted in the PBCH. Summary of the Invention

[0007] Technical issues

[0008] Embodiments of this disclosure provide SS / PBCH block frequency location indication in advanced wireless communication systems.

[0009] Technical solution

[0010] According to embodiments of this disclosure, a method performed by a terminal in a communication system is provided, the method comprising: receiving a first synchronization signal / physical broadcast channel (SS / PBCH) block from a base station; identifying a control resource set (CORESET) for a residual minimum system information (RMSI) corresponding to the first SS / PBCH block that does not exist based on a subcarrier offset value identified using the first SS / PBCH block; and identifying a second SS / PBCH block having a Global Synchronization Channel Number (GSCN) value for the second SS / PBCH block having a CORESET for the RMSI, or a second SS / PBCH block not existing within the GSCN range, based on the subcarrier offset value; wherein, in the frequency range FR 1 and the subcarrier offset value corresponding to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value; and wherein, in the frequency range FR 1 and the subcarrier offset value corresponding to 31, the second SS / PBCH block does not exist within the GSCN range.

[0011] According to an embodiment of this disclosure, a method performed by a base station in a communication system is provided, the method comprising: transmitting a first synchronization signal / physical broadcast channel (SS / PBCH) block; wherein, based on a subcarrier offset value included in the first SS / PBCH block, if a control resource set (CORESET) for a residual minimum system information (RMSI) corresponding to the first SS / PBCH block does not exist, a second SS / PBCH block having a Global Synchronization Channel Number (GSCN) value for the CORESET for the RMSI or not existing within the GSCN range is identified based on the subcarrier offset value; wherein, in a frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value; and wherein, in a frequency range FR 1 and the subcarrier offset value corresponds to 31, the second SS / PBCH block does not exist within the GSCN range.

[0012] According to an embodiment of this disclosure, a terminal in a communication system is provided, the terminal comprising: a transceiver; and a controller coupled to the transceiver and configured to: receive a first synchronization signal / physical broadcast channel (SS / PBCH) block from a base station; identify a control resource set (CORESET) for a residual minimum system information (RMSI) corresponding to the first SS / PBCH block that does not exist based on a subcarrier offset value identified using the first SS / PBCH block; and identify a second SS / PBCH block having a Global Synchronization Channel Number (GSCN) value for the CORESET for the RMSI, or a second SS / PBCH block not existing within a GSCN range, based on the subcarrier offset value; wherein, in the frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value, and wherein, in the frequency range FR 1, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value, and wherein, in the frequency range FR 1, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block. 1. In the case where the subcarrier offset value corresponds to 31, the second SS / PBCH block does not exist within the GSCN range.

[0013] According to an embodiment of this disclosure, a base station in a communication system is provided, the base station comprising: a transceiver; and a controller coupled to the transceiver and configured to: transmit a first synchronization signal / physical broadcast channel (SS / PBCH) block; wherein, based on the subcarrier offset value included in the first SS / PBCH block, if a control resource set (CORESET) for a residual minimum system information (RMSI) corresponding to the first SS / PBCH block does not exist, the Global Synchronization Channel Number (GSCN) value of a second SS / PBCH block having a CORESET for the RMSI or a second SS / PBCH block not existing within the GSCN range is identified based on the subcarrier offset value; wherein, in the frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value, and wherein, in the frequency range FR 1, if a control resource set (CORESET) for a residual minimum system information (RMSI) corresponding to the first SS / PBCH block does not exist, the GSCN value of the second SS / PBCH block is identified based on the subcarrier offset value; and wherein, in the frequency range FR 1, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and physical downlink control channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value; and wherein, in the frequency range FR 1, the GSCN value of the second SS / PBCH block is indicated by the subcarrier offset value; and wherein, in the frequency range FR 1, the GSCN 1. In the case where the subcarrier offset value corresponds to 31, the second SS / PBCH block does not exist within the GSCN range.

[0014] In one embodiment, a base station (BS) is provided in a wireless communication system. The BS includes a processor configured to: generate a synchronization signal and physical broadcast channel (SS / PBCH) block; and generate a global synchronization channel number based on the global synchronization channel number. The system identifies a first frequency position (GSCN-Current) based on a set of predefined synchronization grids determined by the GSCN number (GSCN); transmits SS / PBCH blocks based on the GSCN-Current by determining at least one of the following configurations: SS / PBCH blocks associated with a Physical Downlink Control Channel (PDCCH) including scheduling information for the Residual Minimum System Information (RMSI) of the GSCN-Current, or SS / PBCH blocks not associated with a PDCCH including scheduling information for the RMSI of the GSCN-Current; when an SS / PBCH block is not associated with a PDCCH including scheduling information for the RMSI of the GSCN-Current, the system determines a configuration including at least one of a frequency range or a second frequency position in which other SS / PBCH blocks configured with PDCCHs including scheduling information for the RMSI are not transmitted, the frequency range being determined based on the GSCN; and other SS / PBCH blocks configured with PDCCHs including scheduling information for the RMSI are transmitted at the second frequency position, the second frequency position being determined based on the GSCN; and, based on the determined configuration, identifies the contents of the PBCH included in the SS / PBCH block. The BS also includes a transceiver operably connected to the processor, which is configured to transmit SS / PBCH blocks, including PBCH, to user equipment (UE) via a downlink channel using GSCN-Current.

[0015] In another embodiment, a user equipment (UE) is provided in a wireless communication system. The UE includes a transceiver configured to receive, via a downlink channel, a synchronization signal including a PBCH and a physical broadcast channel (SS / PBCH) block from a base station (BS) using a first frequency position (GSCN-Current), the GSCN-Current being based on a set of predefined synchronization grids determined by a Global Synchronization Channel Number (GSCN). The UE also includes a processor operatively connected to the transceiver, the processor being configured to: decode a PBCH included in an SS / PBCH block; identify the contents of the decoded PBCH; determine a configuration for at least one of an SS / PBCH block associated with a physical downlink control channel (PDCCH) including scheduling information for the residual minimum system information (RMSI) regarding the GSCN-Current, or an SS / PBCH block not associated with a PDCCH including scheduling information for the RMSI regarding the GSCN-Current; and when an SS / PBCH block is not associated with a PDCCH including scheduling information for the RMSI regarding the GSCN-Current, determine a configuration including at least one of a frequency range or a second frequency location in which other SS / PBCH blocks configured with scheduling information for the PDCCH including the scheduling information for the RMSI are not transmitted, the frequency range being determined based on the GSCN, and other SS / PBCH blocks configured with scheduling information for the PDCCH including the scheduling information for the RMSI being transmitted at the second frequency location, the GSCN-Current being determined based on the GSCN.

[0016] In another embodiment, a method for a user equipment (UE) in a wireless communication system is provided. The method includes: receiving from a base station (BS) a block of synchronization signals including a PBCH and a physical broadcast channel (SS / PBCH) via a downlink channel using a first frequency position (GSCN-Current), the GSCN-Current being based on a set of predefined synchronization grids determined by a Global Synchronization Channel Number (GSCN); decoding the PBCH included in the received SS / PBCH block; identifying the content of the decoded PBCH; and determining whether the SS / PBCH block is associated with a physical downlink control channel (PDCCH) including scheduling information for the GSCN-Current, or not associated with a physical downlink control channel (PDCCH) including scheduling information for the GSCN-Current. The configuration includes at least one of the SS / PBCH blocks associated with the PDCCH containing scheduling information for the RMSI of the Current; when the SS / PBCH block is not associated with a PDCCH containing scheduling information for the RMSI of the GSCN-Current, the configuration is determined to include at least one of a frequency range or a second frequency location, in which other SS / PBCH blocks with PDCCHs containing scheduling information for the RMSI are not transmitted, the frequency range being determined based on the GSCN, and other SS / PBCH blocks with PDCCHs containing scheduling information for the RMSI are transmitted at the second frequency location, the GSCN-Current being determined based on the GSCN.

[0017] Other technical features will be apparent to those skilled in the art from the following figures, description and claims.

[0018] Before proceeding with the detailed implementation below, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives encompass both direct and indirect communication. The terms “comprising” and “including,” and their derivatives mean including but not limited to. The term “or” is inclusive, meaning and / or. The phrase “associated,” and its derivatives mean including, being included in, interconnected with, containing, being contained within, connected to or connected to, coupled to or coupled with, communicable with, cooperating with, intertwined, juxtaposed, proximate, combined to or combined with, having, possessing the properties of, having a relationship with or related to, etc. The term “controller” means any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, local or remote. When used with a list of items, the phrase "at least one of..." means that different combinations of one or more items from the list can be used, and it may be necessary to use only one item from the list. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A and B and C.

[0019] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transport transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored and media in which data can be stored and subsequently rewritten (such as rewritable optical discs or erasable memory devices).

[0020] This patent document provides definitions for other specific words and phrases throughout. Those skilled in the art will understand that, in many cases, but not in most, such definitions apply to both the prior and future use of the words and phrases defined herein.

[0021] Beneficial effects of the invention

[0022] Embodiments of this disclosure provide SS / PBCH block frequency location indication in advanced wireless communication systems. Attached Figure Description

[0023] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0024] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0025] Figure 2 An example eNB according to an embodiment of this disclosure is shown;

[0026] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0027] Figure 4A A high-level diagram of an orthogonal frequency division multiple access transmission path according to an embodiment of the present disclosure is shown;

[0028] Figure 4B A high-level diagram of an orthogonal frequency division multiple access (OFDM) receiving path according to an embodiment of the present disclosure is shown;

[0029] Figure 5 A block diagram of a PDSCH transmitter in a subframe according to an embodiment of the present disclosure is shown;

[0030] Figure 6 A receiver block diagram of a PDSCH in a subframe according to an embodiment of the present disclosure is shown;

[0031] Figure 7 A block diagram of a PUSCH transmitter in a subframe according to an embodiment of the present disclosure is shown;

[0032] Figure 8 A receiver block diagram of the PUSCH in a subframe according to an embodiment of the present disclosure is shown;

[0033] Figure 9 An example time-domain location for PSS / SSS mapping for FDD and TDD according to embodiments of this disclosure is shown;

[0034] Figure 10An example SS / PBCH block multiplexed with RMSI's CORESET according to an embodiment of this disclosure is shown;

[0035] Figure 11 A flowchart of a method for a UE according to an embodiment of the present disclosure is shown; and

[0036] Figure 12 A flowchart of a method for a BS according to an embodiment of the present disclosure is shown. Detailed Implementation

[0037] The following discussion Figures 1 to 12 The various embodiments used to describe the principles of this disclosure in this patent document are by way of illustration only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or device.

[0038] The following documents and standards are incorporated herein by reference, as if fully set forth herein: 3GPP TS 36.211v13.2.0, “E-UTRA, Physical channels and modulation”; 3GPP TS 36.212v13.2.0, “E-UTRA, Multiplexing and Channel coding”; 3GPP TS 36.213v13.2.0, “E-UTRA, Physical Layer Procedures”; 3GPP TS 36.321v13.2.0, “E-UTRA, Medium Access Control (MAC) protocol specification”; and 3GPP TS 36.331v13.2.0, “E-UTRA, Radio Resource Control (RRC) protocol specification”.

[0039] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".

[0040] 5G communication systems are designed to be implemented in higher frequency (millimeter wave) bands (e.g., the 60 GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission coverage, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0041] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul communication, mobile networks, cooperative communication, coordinated multipoint (CoMP) transmission and reception, interference mitigation and elimination, etc.

[0042] In 5G systems, hybrid frequency shift keying and orthogonal amplitude modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as adaptive modulation and coding (AMC) technologies, as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0043] The following Figures 1-4B Various embodiments are described in wireless communication systems and implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication technologies. Figures 1-3 The description does not imply any physical or architectural limitation on how different embodiments are implemented. Different embodiments of this disclosure can be implemented in any suitably arranged communication system.

[0044] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The embodiments of the wireless network shown are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0045] like Figure 1 As shown, the wireless network includes eNB101, eNB102, and eNB103. eNB101 communicates with eNB102 and eNB103. eNB101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data network).

[0046] eNB 102 provides wireless broadband access to network 130 to a first plurality of UEs within its coverage area 120. The first plurality of UEs includes: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a mobile phone, wireless laptop, wireless PDA, etc. eNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of the eNBs 101-103 may communicate with each other and with the UEs 111-116 using 5G, LTE, LTE-A, WiMAX, WiFi or other wireless communication technologies.

[0047] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmit point (TP), transmit-receive point (TRP), enhanced base station (eNodeB or eNB), 5G base station (gNB), macro cell, femtocell, WiFi access point (AP), or other wirelessly enabled device. A base station can provide wireless access according to one or more wireless communication protocols, such as 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document, referring to a network infrastructure component that provides wireless access to a remote terminal. Furthermore, depending on the network type, the terms "user equipment" or "UE" can refer to any component such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user equipment." For convenience, the terms "user equipment" and "UE" as used in this patent document refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or a fixed device as commonly considered (such as a desktop computer or vending machine).

[0048] The dashed lines indicate the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative and explanatory purposes only. It should be clearly understood that coverage areas associated with the eNB, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the eNB and variations in the radio environment associated with natural and man-made obstacles.

[0049] As described in more detail below, one or more of UEs 111-116 include a circuitry, programming, or a combination thereof for effective SS / PBCH block frequency location indication. In some embodiments, one or more of eNBs 101-103 include a circuitry, programming, or a combination thereof for effective SS / PBCH block frequency location indication.

[0050] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1 Various modifications can be made. For example, the wireless network can include any number of eNBs and any number of UEs in any suitable arrangement. Furthermore, eNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Similarly, each eNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Additionally, eNBs 101, 102, and / or 103 can provide access to other or additional external networks (such as external telephone networks or other types of data networks).

[0051] Figure 2 An example eNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of eNB 102 shown is for illustrative purposes only, and Figure 1 eNBs 101 and 103 can have the same or similar configurations. However, eNBs come in a wide variety of configurations, and Figure 2 This disclosure is not intended to limit the scope to any particular implementation of the eNB.

[0052] like Figure 2 As shown, the eNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, a transmit (TX) processing circuitry system 215, and a receive (RX) processing circuitry system 220. The eNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0053] RF transceivers 210a-210n receive input RF signals, such as signals transmitted by a UE in network 100, from antennas 205a-205n. RF transceivers 210a-210n down-convert the input RF signals to generate an IF signal or a baseband signal. The IF signal or baseband signal is sent to RX processing circuitry system 220, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband signal or IF signal. RX processing circuitry system 220 transmits the processed baseband signal to controller / processor 225 for further processing.

[0054] The TX processing circuitry 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 225. The TX processing circuitry 215 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband signal or IF signal. RF transceivers 210a-210n receive the processed baseband signal or IF signal from the TX processing circuitry 215 and up-convert the baseband signal or IF signal into an RF signal for transmission via antennas 205a-205n.

[0055] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the eNB 102. For example, the controller / processor 225 may, based on well-known principles, control the reception of forward channel signals and the transmission of reverse channel signals via RF transceivers 210a-210n, RX processing circuitry 220, and TX processing circuitry 215. The controller / processor 225 may also support additional functions, such as more advanced wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations, where the output signals from multiple antennas 205a-205n are weighted differently to effectively steer the output signals in a desired direction. The controller / processor 225 may support any of a wide variety of other functions within the eNB 102.

[0056] The controller / processor 225 is also capable of executing programs and other processes, such as an operating system, residing in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as needed by the executing process.

[0057] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the eNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 235 can support communication via any suitable wired or wireless connection(s). For example, when the eNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G, LTE, or LTE-A), interface 235 can allow the eNB 102 to communicate with other eNBs via a wired or wireless backhaul connection. When the eNB 102 is implemented as an access point, interface 235 can allow the eNB 102 to communicate via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). Interface 235 includes any suitable architecture supporting communication via wired or wireless connections, such as Ethernet or RF transceivers.

[0058] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, while another portion of memory 230 may include flash memory or other ROM.

[0059] although Figure 2 An example of an eNB 102 is shown, but more can be found on other eNBs. Figure 2 Various changes can be made. For example, eNB 102 can include any number of Figure 2 Each component is shown. As a specific example, an access point may include multiple interfaces 235, and a controller / processor 225 may support routing functionality to route data between different network addresses. As another specific example, although shown as a single instance including TX processing circuitry system 215 and a single instance including RX processing circuitry system 220, the eNB 102 may include multiple instances of each (such as one per RF transceiver). Furthermore, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0060] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only. Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0061] like Figure 3As shown, UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuitry 315, a microphone 320, and a receive (RX) processing circuitry 325. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface 345, a touchscreen 350, a display 355, and memory 360. Memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0062] RF transceiver 310 receives an input RF signal transmitted from an eNB of network 100 via antenna 305. RF transceiver 310 down-converts the input RF signal to generate an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 transmits the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (e.g., for web browsing data).

[0063] The TX processing circuitry 315 receives analog or digital voice data from the microphone 320, or baseband data (such as web data, email, or interactive video game data) from the processor 340. The TX processing circuitry 315 encodes, multiplexes, and / or digitizes the output baseband data to generate a processed baseband signal or IF signal. The RF transceiver 310 receives the processed baseband signal or IF signal from the TX processing circuitry 315 and up-converts it into an RF signal for transmission via the antenna 305.

[0064] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals through RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315, based on well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0065] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as processes for CSI reporting on PUCCH. Processor 340 can move data into or out of memory 360 as required by the executing processes. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from eNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0066] The processor 340 is also coupled to the touchscreen 350 and the display 355. The operator of the UE 116 can use the touchscreen 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of displaying text (such as from a website) and / or at least limited graphics.

[0067] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), while another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0068] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile devices or fixed devices.

[0069] Figure 4A This is a high-level diagram of the transmission path circuitry system. For example, the transmission path circuitry system can be used for orthogonal frequency division multiple access (OFDMA) communication. Figure 4B This is a high-level diagram of the receive path circuitry system. For example, the receive path circuitry system can be used in Orthogonal Frequency Division Multiple Access (OFDMA) communication. Figure 4A and Figure 4BIn the context of downlink communication, the transmission path circuitry can be implemented in the base station (eNB) 102 or a relay station, and the receive path circuitry can be implemented in the user equipment (e.g., Figure 1 The user equipment 116) is implemented in other examples. For uplink communication, the receive path circuit system 450 can be implemented in the base station (e.g., Figure 1 Implemented in the eNB 102 or relay station, and the transmission path circuit system can be in the user equipment (e.g., Figure 1 Implemented in user equipment 116).

[0070] The transmission path circuitry includes a channel coding and modulation block 405, a serial-to-parallel (S-to-P) block 410, an N-size Inverse Fast Fourier Transform (IFFT) block 415, a parallel-to-serial (P-to-S) block 420, a cyclic prefix addition block 425, and an up-converter (UC) 430. The receive path circuitry includes a down-converter (DC) 455, a cyclic prefix removal block 460, a serial-to-parallel (S-to-P) block 465, an N-size Fast Fourier Transform (FFT) block 470, a parallel-to-serial (P-to-S) block 475, and a channel decoding and demodulation block 480.

[0071] Figure 4A400 and Figure 4B At least some of the components in 450 can be implemented in software, while others can be implemented in configurable hardware or a combination of software and configurable hardware. Specifically, note that the FFT and IFFT blocks described in this disclosure can be implemented as configurable software algorithms, wherein the value of size N can be modified according to the implementation method.

[0072] Furthermore, although this disclosure pertains to embodiments implementing the Fast Fourier Transform (FFT) and Inverse Fast Fourier Transform (IFFT), this is by way of illustration only and should not be construed as limiting the scope of this disclosure. It is understood that in alternative embodiments of this disclosure, the FFT and IFFT functions can be readily replaced by the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions, respectively. It is understood that for the DFT and IDFT functions, the value of variable N can be any integer (i.e., 1, 4, 3, 4, etc.), while for the FFT and IFFT functions, the value of variable N can be any integer that is a power of 2 (i.e., 1, 2, 4, 8, 16, etc.).

[0073] In the transmission path circuitry system 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., LDPC coding), and modulates (e.g., Quadrature Phase Shift Keying (QPSK) or Quadrature Amplitude Modulation (QAM)) the input bits to produce a sequence of frequency-domain modulated symbols. The serial-to-parallel block 410 converts (i.e., demultiplexes) the serial modulated symbols into parallel data to produce N parallel symbol streams, where N is the IFFT / FFT size used in BS 102 and UE 116. Then, an N-sized IFFT block 415 performs an IFFT operation on the N parallel symbol streams to produce a time-domain output signal. The parallel-to-serial block 420 converts (i.e., multiplexes) the parallel time-domain output symbols from the N-sized IFFT block 415 to produce a serial time-domain signal. A cyclic prefix addition block 425 then inserts a cyclic prefix into the time-domain signal. Finally, an upconverter 430 modulates (i.e., upconverts) the output of the cyclic prefix addition block 425 to an RF frequency for transmission via the wireless channel. The signal can also be filtered in baseband before being converted to the RF frequency.

[0074] The transmitted RF signal arrives at UE 116 after passing through the wireless channel and performs the opposite operation to that at eNB 102. Downconverter 455 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 460 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 465 converts the time-domain baseband signal into a parallel time-domain signal. Then, an N-size FFT block 470 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 475 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 480 demodulates the modulated symbols and then decodes them to recover the original input data stream.

[0075] Each of eNBs 101-103 can implement a transmission path similar to that used for transmission to user equipments 111-116 in the downlink, and can implement a reception path similar to that used for reception from user equipments 111-116 in the uplink. Similarly, each of user equipments 111-116 can implement a transmission path corresponding to the architecture used for transmission to eNBs 101-103 in the uplink, and can implement a reception path corresponding to the architecture used for reception from eNBs 101-103 in the downlink.

[0076] 5G communication system use cases have been identified and described. These use cases can be broadly categorized into three distinct groups. In one example, enhanced mobile broadband (eMBB) was identified as handling high bit / second requirements while having less stringent latency and reliability requirements. In another example, ultra-reliable and low latency (URLL) was identified with less stringent bit / second requirements. In yet another example, massive machine-type communication (mMTC) was identified as a system where the number of devices can reach up to [number missing] per km. 2 100,000 to 1 million units, but reliability / throughput / latency requirements may not be as stringent. This scenario may also involve power efficiency requirements, as battery consumption should be minimized as much as possible.

[0077] A communication system includes a downlink (DL) that transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE) and an uplink (UL) that transmits signals from the UE to a receiving point such as a NodeB. A UE, often also referred to as a terminal or mobile station, can be fixed or mobile and can be a cellular phone, personal computer device, or automated device. An eNodeB is typically a fixed station and may also be referred to as an access point or other equivalent terms. For LTE systems, a NodeB is typically referred to as an eNodeB.

[0078] In communication systems such as LTE, DL signals can include data signals that transmit information content, control signals that transmit DL control information (DCI), and reference signals (RS), also known as pilot signals. The eNodeB transmits data information through the physical DL shared channel (PDSCH). The eNodeB transmits DCI through the physical DL control channel (PDCCH) or the enhanced PDCCH (EPDCCH).

[0079] The eNodeB transmits acknowledgment information in response to data transmission blocks (TB) from the UE in the physical hybrid ARQ indicator channel (PHICH). The eNodeB transmits one or more types of RS, including UE-common RS (CRS), channel state information RS (CSI-RS), or demodulation RS (DMRS). CRS is transmitted over the DL system bandwidth (BW), and the UE can use CRS to obtain channel estimates for demodulating data or control information or performing measurements. To reduce CRS overhead, the eNodeB can transmit CSI-RS at a lower density than CRS in the time and / or frequency domains. DMRS can only be transmitted in the BW of the corresponding PDSCH or EPDCCH, and the UE can use DMRS to demodulate data or control information in the PDSCH or EPDCCH, respectively. The transmission time interval of the DL channel is called a subframe and can have a duration of, for example, 1 millisecond.

[0080] The DL signal also includes a logical channel for transmitting system control information. When the BCCH transmits the master information block (MIB), it is mapped to a transport channel called the broadcast channel (BCH), or when the BCCH transmits the system information block (SIB), it is mapped to the DL shared channel (DL-SCH). Most system information is included in different SIBs transmitted using the DL-SCH. The presence of system information on the DL-SCH in a subframe can be indicated by the corresponding PDCCH transmitting a codeword with a cyclic redundancy check (CRC) scrambled with special system information RNTI (SI-RNTI). Alternatively, scheduling information for SIB transmission can be provided in an earlier SIB, and scheduling information for the first SIB (SIB-1) can be provided by the MIB.

[0081] DL resource allocation is performed on a per-subframe and per-set-physical-resource-block (PRB) basis. A transmission bandwidth (BW) comprises frequency resource elements called resource blocks (RBs). Each RB includes... Each subcarrier or resource element (RE) can have 12 REs. A unit of one RB on a subframe is called a PRB. The total number of BWs for PDSCH transmissions... One RE can be allocated to the UE. PDSCH RB.

[0082] UL signals can include data signals for transmitting data information, control signals for transmitting UL control information (UCI), and UL RS. UL RS includes DMRS and Sounding RS (SRS). The UE only transmits DMRS in the corresponding PUSCH or PUCCH BW. The eNodeB can use DMRS to demodulate data signals or UCI signals. The UE transmits SRS to provide UL CSI to the eNodeB. The UE transmits data information or UCI through the corresponding physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). If the UE needs to transmit data information and UCI in the same UL subframe, the UE can multiplex both in the PUSCH. The UCI includes a Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) message, a scheduling request (SR), a rank indicator (RI), and channel state information (CSI). The HARQ-ACK message indicates whether a data TB has been correctly (ACKed) or incorrectly (NACKed) detected in the PDSCH, or whether a PDCCH has been absent (DTX). The SR indicates whether the UE has data in its buffer. The CSI enables the eNodeB to perform link adaptation for PDSCH transmission to the UE. The UE also transmits HARQ-ACK information in response to the detection of a PDCCH / EPDCCH indicating the release of a semi-persistently scheduled PDSCH.

[0083] A UL subframe consists of two time slots. Each time slot includes a space for transmitting data information, UCI, DMRS, or SRS. One symbol. The frequency resource unit of the UL system BW is RB. For the total transmission of BW One RE, assign N to the UE RB RB. For PUCCH, N RB =1. The last subframe symbol can be used to multiplex SRS transmissions from one or more UEs. The number of subframe symbols available for data / UCI / DMRS transmissions is Where the last subframe symbol is used to transmit SRS, then N SRS =1, otherwise N SRS =0.

[0084] Figure 5 A block diagram 500 of a PDSCH transmitter in a subframe according to an embodiment of the present disclosure is shown. Figure 5 The embodiment of the transmitter block diagram 500 shown is for illustrative purposes only. Figure 5 This disclosure is not intended to limit the scope to any particular implementation of the transmitter block diagram 500.

[0085] like Figure 5 As shown, information bits 510 are encoded by encoder 520 (such as a turbo encoder) and modulated by modulator 530 (e.g., using quadrature phase shift keying (QPSK) modulation). Serial-to-parallel (S / P) converter 540 generates M modulation symbols, which are then provided to mapper 550 to map to REs selected by transmission BW selection unit 555 for the assigned PDSCH transmission BW. Unit 560 applies inverse fast Fourier transform (IFFT), and the output is then serialized by parallel-to-serial (P / S) converter 570 to create a time-domain signal, filtered by filter 580, and transmitted as signal 590. Additional features such as data scrambling, cyclic prefix insertion, time windowing, and interleaving are well known in the art and are not shown for simplicity.

[0086] Figure 6 A receiver block diagram 600 of a PDSCH in a subframe according to an embodiment of the present disclosure is shown. Figure 6 The embodiment of block diagram 600 shown is for illustrative purposes only. Figure 6 The scope of this disclosure is not limited to any particular embodiment of FIG600.

[0087] like Figure 6 As shown, the received signal 610 is filtered by filter 620, the RE 630 for the allocated receive BW is selected by BW selector 635, unit 640 applies Fast Fourier Transform (FFT), and the output is serialized by parallel-to-serial converter 650. Subsequently, demodulator 660 coherently demodulates the data symbols by applying a channel estimate obtained from DMRS or CRS (not shown), and decoder 670, such as a turbo decoder, decodes the demodulated data to provide an estimate of information data bits 680. For simplicity, additional functions such as time windows, cyclic prefix removal, descrambling, channel estimation, and deinterleaving are not shown.

[0088] Figure 7 A block diagram 700 of a PUSCH transmitter in a subframe according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of block diagram 700 shown is for illustrative purposes only. Figure 7 This disclosure is not intended to limit the scope to any particular implementation of block diagram 700.

[0089] like Figure 7 As shown, information data bits 710 are encoded by encoder 720 (such as a turbo encoder) and modulated by modulator 730. Discrete Fourier Transform (DFT) unit 740 applies DFT to the modulated data bits, RE 750 corresponding to the assigned PUSCH transmission BW is selected by transmission BW selection unit 755, unit 760 applies IFFT, and after cyclic prefix insertion (not shown), filtering is applied by filter 770, and transmission signal 780 is transmitted.

[0090] Figure 8 A receiver block diagram 800 for a PUSCH in a subframe according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of block diagram 800 shown is for illustrative purposes only. Figure 8 This disclosure is not intended to limit the scope to any particular implementation of block diagram 800.

[0091] like Figure 8 As shown, the received signal 810 is filtered by filter 820. Subsequently, after removing the cyclic prefix (not shown), unit 830 applies FFT, RE 840 corresponding to the assigned PUSCH receive BW is selected by receive BW selector 845, unit 850 applies inverse DFT (IDFT), demodulator 860 performs coherent demodulation of data symbols by applying channel estimation obtained from DMRS (not shown), and decoder 870, such as turbo decoder, decodes the demodulated data to provide an estimate of information data bits 880.

[0092] In next-generation cellular systems, various use cases are anticipated to exceed the capabilities of LTE systems. Systems known as 5G, or fifth-generation cellular systems, capable of operating below and above 6 GHz (e.g., in the millimeter wave range), are among the needs. In 3GPP TR 22.891, 74 5G use cases have been identified and described; these use cases can be broadly categorized into three groups. The first group, called “enhanced mobile broadband (eMBB),” targets high data rate services with less stringent latency and reliability requirements. The second group, called “ultra-reliable and low-latency (URLL),” targets applications with less stringent data rate requirements but lower latency tolerance. The third group, called “massive MTC (mMTC),” targets applications such as per-km... 2 There are a large number of low-power devices connected, with less stringent requirements for reliability, data rate, and latency.

[0093] To enable 5G networks to support diverse services with varying Quality of Service (QoS), an implementation known as network slicing has been identified in the LTE specification. Flexible and independent frame or subframe designs are utilized to efficiently leverage PHY resources and multiplex various slices (with different resource allocation schemes, parameter sets, and scheduling strategies) within the DL-SCH.

[0094] Power consumption and battery life are critical for devices in the Internet of Things (IoT). In narrowband IoT (NB-IoT) or enhanced machine-type communication (eMTC) systems, power saving mode (PSM) or extended discontinuous reception (eDRX) mode can be configured to conserve power. However, in PSM or eDRX mode, the UE cannot listen for paging messages during sleep. In some IoT applications, the UE needs to establish a connection with the network within a certain period after receiving a network command. UEs with this requirement cannot be configured using PSM or eDRX modes with relatively long periods.

[0095] In enhanced versions of NB-IoT and eMTC systems, wake-up or sleep signals / channels were introduced after learning and research to enable UE paging while conserving power. The wake-up signal / channel is configured to wake the UE, meaning the UE needs to continue monitoring the subsequent MTC Physical Downlink Control Channel (MPDCCH) used to indicate paging messages. The sleep signal / channel is configured to instruct the UE to enter a sleep state, meaning the UE does not need to monitor the subsequent MPDCCH used to indicate paging messages.

[0096] In multi-carrier systems, the carrier transmitting synchronization signals is called the anchor carrier, while in LTE systems, paging signals are transmitted on the anchor carrier. In NB-IoT systems, a scheme for transmitting paging messages on non-anchor carriers is introduced. In eMTC systems, multiple narrowbands are defined, one of which has six Physical Resource Blocks (PRBs), and the concept of a paging narrowband is introduced. Furthermore, in eMTC systems, the downlink control channel MPDCCH used for MTC is configured to indicate paging messages, and different UEs can monitor the MPDCCH on different narrowbands. Similarly, in the ongoing 5G New Radio (NR) systems, there are situations where the UE's bandwidth is less than the system bandwidth, and in such cases, multiple bandwidth portions can be defined for the paging channel. How to transmit and receive wake-up or sleep signals in multi-carrier, narrowband, or partial bandwidth scenarios remains an unresolved issue.

[0097] Figure 9 An example time-domain location 900 is shown for PSS / SSS mapping for FDD and TDD according to an embodiment of the present disclosure. Figure 9 The embodiment of time-domain position 900 shown is for illustrative purposes only. Figure 9 This disclosure is not intended to limit the scope to any particular implementation.

[0098] refer to Figure 9 In the FDD case, within each frame (905), the PSS (925) is transmitted in the last symbol of the first time slot of subframes 0 and 5 (910 and 915), where each subframe comprises two time slots. The SSS (920) is transmitted in the penultimate symbol of the same time slot. In the TDD case, within each frame (955), the PSS (990) is transmitted in the third symbol of subframes 1 and 6 (965 and 980), while the SSS (985) is transmitted in the last symbol of subframes 0 and 5 (960 and 970). This difference allows for duplex scheme detection on the cell. The resource elements of the PSS and SSS cannot be used to transmit any other type of DL signal.

[0099] In this disclosure, for the sake of brevity, both FDD and TDD are considered as duplexing methods for both DL signaling and UL signaling. Although the exemplary description and embodiments below assume Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA), this disclosure can be extended to other OFDM-based transmission waveforms or multiple access schemes, such as filtered OFDM (F-OFDM).

[0100] This disclosure covers several components that can be used in combination or together, or can work as a standalone solution.

[0101] A communication system includes a downlink (DL) that transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE), and an uplink (UL) that transmits signals from the UE to a receiving point such as a NodeB. A UE, often also called a terminal or mobile station, can be fixed or mobile and can be a cellular phone, personal computer device, or automated device. An eNodeB is typically a fixed station and may also be called an access point or other equivalent terms. For LTE systems, a NodeB is typically referred to as an eNodeB. For NR systems, a NodeB is typically referred to as a gNodeB.

[0102] In this disclosure, a parameter set refers to a set of signal parameters, which may include subframe duration, subcarrier spacing, cyclic prefix length, transmission bandwidth, or any combination of these signal parameters.

[0103] For initial LTE access, the primary synchronization signal and secondary synchronization signals (PSS and SSS, respectively) are used for coarse timing and frequency synchronization, as well as cell ID acquisition. Since the PSS / SSS are transmitted twice every 10ms radio frame, and time-domain enumeration is introduced regarding the system frame number (SFN, included in the MIB), frame timing is detected from the PSS / SSS to avoid increasing the detection burden from the PBCH. Furthermore, the cyclic prefix (CP) length and (if unknown) duplex scheme can be detected from the PSS / SSS.

[0104] The PSS is constructed from a 63-bit frequency-domain ZC sequence, with its middle element truncated to avoid using DC subcarriers. Three roots are chosen for the PSS to represent the three physical layer identifiers within each cell group. The SSS sequence is based on the maximum-length sequence (also known as the M-sequence).

[0105] Each SSS sequence is constructed by interleaving two BPSK modulation sequences of length 31 in the frequency domain, where the two source sequences before modulation are different cyclic shifts of the same M sequence. The cyclic shift index is constructed from the physical cell ID group. Since PSS / SSS detection can be erroneous (e.g., due to the non-ideal nature of the autocorrelation and cross-correlation properties of PSS / SSS and the lack of CRC protection), the cell ID detected from PSS / SSS is assumed to be occasionally confirmed via PBCH detection.

[0106] The PBCH is primarily used to represent the Master Block Information (MIB) using signals. It consists of DL and UL system bandwidth information (3 bits), PHICH information (3 bits), and SFN (8 bits). Ten reserved bits are added (for other uses such as MTC), bringing the MIB payload to 24 bits. After adding a 16-bit CRC, 1 / 3 rate-trimmed convolutional coding, 4x repetition, and QPSK modulation are applied to a 40-bit codeword. The resulting QPSK symbol stream is transmitted across four subframes distributed across four radio frames. In addition to detecting the MIB, the number of CRS ports also needs to be blindly detected for the PBCH.

[0107] For NR licensed spectrum, each synchronization and PBCH signal block (SS / PBCH block) includes one symbol for NR-PSS, two symbols for NR-PBCH, and one symbol for NR-SSS and NR-PBCH, where these four symbols are consecutively mapped and time-division multiplexed. NR-SS is a unified design for all supported carrier frequency ranges in NR, including NR-PSS and NR-SSS sequence designs. The transmission bandwidth of NR-PSS and NR-SSS (e.g., 12 PRBs) is less than the transmission bandwidth of the entire SS / PBCH block (e.g., 20 PRBs). For initial cell selection of NR cells, the UE assumes a default SS burst set period of 20ms, and to detect non-independent NR cells, the network provides the UE with one SS burst set period for each frequency carrier and information for deriving measurement timing / duration, if possible.

[0108] A control resource set (CORESET) needs to be configured for receiving common control channels (such as RMSI, OSI, SIBx, RAR, etc.). According to the latest 3GPP RAN1 protocol, one CORESET configuration is provided via PBCH (or MIB) for at least RMSI scheduling, and another CORESET configuration is provided via RMSI (or SIB1) for at least RAR scheduling. A CORESET can be characterized by time slot timing, the number of OFDM symbols in each time slot, and frequency resources. These CORESET attributes are indicated or pre-configured for each CORESET.

[0109] For RMSI / SIB scheduling, the CORESET attribute is provided in the PBCH. For RAR scheduling, the CORESET attribute is provided in the RMSI. Among these CORESET attributes configured by PBCH / RMSI, the OFDM symbol count and frequency resources can be applied to all common channels (e.g., SIBx / RAR, etc.), but time slot timing can be specifically determined for different SIBx / RARs. In NR, multiple SS / PBCH blocks within a wideband carrier are supported, and some SS / PBCH blocks on the same carrier may not all be associated with an RMSI. For SS / PBCH blocks without an associated RMSI, one code-point within the PRB grid offset indicator (e.g., 4 bits for >6GHz and 5 bits for <6GHz) is used to indicate the absence of an RMSI, and in one example, the 8 bits used for RMSI CORESET and search space configuration in the MIB can be used for other purposes.

[0110] This disclosure considers the use of the 8 bits used for RMSI CORESET and search space configuration in the MIB when the indication does not have an associated RMSI, as well as the potential use of other fields or reserved code points.

[0111] In one embodiment, when multiple SS / PBCH blocks are supported over broadband, at least one of the SS / PBCH blocks may be located on a predefined synchronization grid to define the cell for initial access purposes. For SS / PBCH blocks that may or may not be associated with an RMSI, and whether an associated RMSI exists, this is indicated by code points within the PRB grid offset indicator. If the UE successfully detects an SS / PBCH block on the synchronization grid and further detects no RMSI associated with the SS / PBCH block, the UE can utilize the field initially used for RMSI configuration (e.g., 8 bits) to indicate the precise location of the next or other SS / PBCH blocks, allowing the UE to skip some synchronization grid locations for blind searching.

[0112] In one sub-implementation, some other fields in the PBCH content, or some reserved code points from one or more other fields in the PBCH content, can be combined with the 8 bits used for RMSI CORESET configuration to obtain a wider indication range. For example, if an additional bit can be combined, the indication range can be extended to 511 or 512 (depending on which code point indicates that there is no cell-defining SS / PBCH block in the frequency band). For another example, if up to four other reserved code points can be combined, the indication range can be extended to as high as 1023 or 1024 (depending on which code point indicates that there is no cell-defining SS / PBCH block in the frequency band).

[0113] In one embodiment, the exact location of the synchronization grid associated with the next SS / PBCH block and RMSI can be determined, where each code point represents the exact location of the synchronization grid from which the SS / PBCH block can be located. After decoding the code points, the UE can directly find the frequency location of the synchronization grid that the UE can search for.

[0114] In one sub-implementation, the relative position of the synchronization grid leading to the detected SS / PBCH block is measured by the number of synchronization grids, where the number is always non-negative, meaning the relative position is always defined along the initial cell search order within the frequency band. It is necessary to define a code point for the "0" relative position of the next SS / PBCH block because this code point can indicate that no cell with an associated RMSI defines an SS / PBCH block within the indication capability (e.g., for a bandwidth of 255 synchronization grids using 8 bits), and the UE can skip all possible synchronization grids within the search range and continue performing a blind search from the first synchronization grid whose relative position has exceeded the search range from the current SS / PBCH block.

[0115] Table 1

[0116] Configuration index in pdcch-ConfigSIB1 GSCN for cell definition SS / PBCH blocks 0 No cell definition SS / PBCH was found in the search scope. 1 GSCN-Current+1 2 GSCN-Current+2 ... ... i GSCN-Current+i ... ... 255 GSCN-Current+255

[0117] Table 1. pdcch-ConfigSIB1 (e.g., 8 bits)

[0118] In Table 1, GSCN-Current is the Global Synchronization Channel Number (GSCN) value indicating the current SS / PBCH block for which no RMSI exists. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value from {r_0, r_1, r_2, r_3}, then no associated RMSI exists, and the UE may assume that the mapping from pdcch-ConfigSIB1 to the GSCN of the synchronization grid is according to Table 1. The UE can search for the synchronization grid within the search band to obtain the cell-defined SS / PBCH block, and the UE assumes that if pdcch-ConfigSIB1 = 0, then there is no cell-defined SS / PBCH block within the range of GSCN-Current to GSCN-Current+255.

[0119] Note that Table 1 can be given equivalently by formula. In the initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value in {r_0,r_1,r_2,r_3}, which corresponds to the index-reserved-ssb-SubcarrierOffset taking a value in {0,1,2,3}, then no associated RMSI exists, and the UE may assume that when pdcch-ConfigSIB1>1, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB=GSCN-Current+pdcch-ConfigSIB1, and the UE can search for this synchronization grid within the search band to obtain the cell-defined SS / PBCH block; and the UE assumes that if pdcch-ConfigSIB1>1, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB=GSCN-Current+pdcch-ConfigSIB1, .... If ch-ConfigSIB1 = 0, then there are no cell-defined SS / PBCH blocks in the range from GSCN-Current to GSCN-Current+255. Here, GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value of the current SS / PBCH block indicating that no RMSI exists, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (taken from {0,1,2,3}), and pdcch-ConfigSIB1 takes the value from {0,1,...,254,255}.

[0120] Table 2

[0121]

[0122]

[0123] Reserved code points in Table 2. pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset

[0124] In Table 2, GSCN-Current is the GSCN value indicating the current SS / PBCH block for which no RMSI exists. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value from {r_0,r_1,r_2,r_3}, then no associated RMSI exists. The UE may also assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization grid is based on Table 2. The UE can search the synchronization grid within the search band to obtain the cell-defined SS / PBCH block. Furthermore, the UE assumes that if {ssb-SubcarrierOffset,pdcch-ConfigSIB1} = {r_0,0}, then no cell-defined SS / PBCH block exists within the range of GSCN-Current to GSCN-Current+1023.

[0125] Note that Table 2 can be given equivalently by formula. In the initial cell selection, the UE can assume that if the higher-layer parameter ssb-SubcarrierOffset takes values ​​from {r_0,r_1,r_2,r_3}, which correspond to index-reserved-ssb-SubcarrierOffset taking values ​​from {0,1,2,3} respectively, then no associated RMSI exists. Furthermore, the UE can assume that when {index-reserved-ssb-SubcarrierOffset,pdcch-ConfigSIB1}{0,0}, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current + 256 * index-reserved-ssb-SubcarrierOffset + pdcch-ConfigSIB1. The UE can search for this synchronization grid within the search band to obtain the cell definition S. The UE assumes that if {index-reserved-ssb-SubcarrierOffset,pdcch-ConfigSIB1} = {0,0}, then there is no cell-defined SS / PBCH block within the range of GSCN-Current to GSCN-Current+1023. Here, GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value of the current SS / PBCH block indicating that no RMSI exists, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (taken from {0,1,2,3}), and pdcch-ConfigSIB1 takes the value from {0,1,...,254,255}.

[0126] In another sub-implementation, the relative position to the detected SS / PBCH block is measured by the number of synchronization grids (i.e., the GSCN value), where the number can be positive or negative to define the relative position on either side of the SS / PBCH block. In one example, a code point defining the "0" relative position of the next SS / PBCH block can indicate that there is no SS / PBCH synchronized with an associated RMSI within the indication capability (e.g., for a bandwidth of 255 synchronization grids using 8 bits), and the UE can skip all synchronization grids in the table and continue performing a blind search on the remaining synchronization grids.

[0127] In one example, more code points can indicate that there are no such cell-defined SS / PBCH blocks in the range, where the range is given by the GSCN index (e.g., start and end GSCN).

[0128] Table 3

[0129] Configuration index in pdcch-ConfigSIB1 GSCN for cell definition SS / PBCH blocks 0 No cell-defined SS / PBCH blocks were found in the search area. 1 GSCN-Current+1 2 GSCN-Current+2 ... ... 127 GSCN-Current+127 128 GSCN-Current-1 129 GSCN-Current-2 ... ... 255 GSCN-Current-128

[0130] Table 3. pdcch-ConfigSIB1 (e.g., 8 bits)

[0131] In Table 3, GSCN-Current is the GSCN value indicating the current SS / PBCH block for which no RMSI exists. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value from {r_0, r_1, r_2, r_3}, then no associated RMSI exists, and the UE may assume that the mapping from pdcch-ConfigSIB1 to the GSCN of the synchronization grid is according to Table 3. The UE can search for the synchronization grid within the search band to obtain the cell-defined SS / PBCH block, and the UE assumes that if pdcch-ConfigSIB1 = 0, then no cell-defined SS / PBCH block exists within the range of GSCN-Current-128 to GSCN-Current+127.

[0132] Note that Table 3 can be equivalently given by a formula. In initial cell selection, the UE may assume that if the higher layer parameter ssb-SubcarrierOffset takes values from {r_0, r_1, r_2, r_3}, which respectively correspond to the index-reserved-ssb-SubcarrierOffset taking values from {0, 1, 2, 3}, then there is no associated RMSI, and the UE may assume that when 0 < pdcch-ConfigSIB1 < 128, the GSCN of the synchronization raster is calculated according to GSCN-cell-defined-SSB = GSCN-Current + pdcch-ConfigSIB1; when pdcch-ConfigSIB1 > 128, the GSCN of the synchronization raster is calculated according to GSCN-cell-defined-SSB = GSCN-Current - pdcch-ConfigSIB1. The UE can search for this synchronization raster within the search band to obtain the cell-defined SS / PBCH block, and the UE assumes that if pdcch-ConfigSIB1 = 0, there is no cell-defined SS / PBCH block within the range of GSCN-Current - 128 to GSCN-Current + 127. Here, GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value of the current SS / PBCH block for which it is indicated that there is no RMSI, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (taking values from {0, 1, 2, 3}), and pdcch-ConfigSIB1 takes values from {0, 1,..., 254, 255}.

[0133]

Table 4

[0134]

[0135]

[0136] Table 4. Reserved code points in pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset

[0137] In Table 4, GSCN-Current is the GSCN value indicating the current SS / PBCH block for which no RMSI exists. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value in {r_0, r_1, r_2, r_3}, then no associated RMSI exists. The UE may also assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization grid is based on Table 4. The UE can search the synchronization grid within the search band to obtain the cell-defined SS / PBCH block. Furthermore, the UE assumes that if {ssb-SubcarrierOffset, pdcch-ConfigSIB1} = {r_0, 0}, then no cell-defined SS / PBCH block exists within the range of GSCN-Current-512 to GSCN-Current+511.

[0138] Note that Table 4 can be given by equivalent formulas. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes values ​​from {r_0,r_1,r_2,r_3}, which correspond to index-reserved-ssb-SubcarrierOffset taking values ​​from {0,1,2,3} respectively, then no associated RMSI exists. Furthermore, the UE may assume that when reserved-ssb-SubcarrierOffset < 2 and {index-reserved-ssb-SubcarrierOffset,pdcch-ConfigSIB1} {0,0}, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current + 256 * index-reserved-ssb-SubcarrierOffset + pdcch-ConfigSIB1; and when index-reserved-ssb-SubcarrierOffset > 1, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current + 256 * index-reserved-ssb-SubcarrierOffset + pdcch-ConfigSIB1. The value t-256*(index-reserved-ssb-SubcarrierOffset-2)-pdcch-ConfigSIB1 is used to calculate the synchronization grid within the search band to obtain the cell definition SS / PBCH block. The UE assumes that if {index-reserved-ssb-SubcarrierOffset,pdcch-ConfigSIB1}={0,0}, then there is no cell definition SS within the range of GSCN-Current-512 to GSCN-Current+511. / PBCH block, where GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value of the current SS / PBCH block indicating that no RMSI exists, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (taken from {0,1,2,3}), and pdcch-ConfigSIB1 takes the value from {0,1,...,254,255}.

[0139] Table 5

[0140]

[0141]

[0142]

[0143] Table 5. Reserved code points in pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset, and one of the reserved bits of the MSB used to indicate the subcarrier offset in FR1 (e.g., ), to provide instructions for FR1.

[0144] Table 6

[0145]

[0146]

[0147] Reserved code points in Table 6.pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset for indication of FR2.

[0148] In Tables 5 and 6, GSCN-Current is the GSCN value indicating the absence of an RMSI in the current SS / PBCH block. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value from {12,13,14,15} (or equivalently {r_0,r_1,r_2,r_3}), then no associated RMSI exists, and the UE may assume that ssb-SubcarrierOffset... (For FR1 only) and the mapping of pdcch-ConfigSIB1 to the GSCN of the synchronization grid are based on Tables 5 and 6. The UE can search for the synchronization grid within the search band to obtain the cell definition SS / PBCH block, and the UE assumes that if ssb-SubcarrierOffset = 14 or 15, there is no cell definition SS / PBCH block in the given range.

[0149] Note that Tables 5 and 6 can be given equivalently by formulas. In the initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes values ​​from {12,13,14,15} (or equivalently {r_0,r_1,r_2,r_3}), then no associated RMSI exists, and the UE may assume that when ssb-SubcarrierOffset = 12, the GSCN of the synchronization grid is based on GSCN-cell-defined-SSB = GSCN-Current + 256*a. SSB+pdcch-ConfigSIB1+1 is calculated; when ssb-SubcarrierOffset=13, the GSCN of the synchronization raster is based on GSCN-cell-defined-SSB=GSCN-Current-256*a SSB The UE can search for the synchronization grid within the search band to obtain the cell definition SS / PBCH block, calculated by -pdcch-ConfigSIB1-1; and the UE assumes that if ssb-SubcarrierOffset = 14 or 15, then from GSCN-Current-(512*a SSB +256*(ssb-SubcarrierOffset-14)+pdcch-ConfigSIB1) / 32 to GSCN-Current+(512*a SSB There are no cell-defined SS / PBCH blocks within the range of +256*(ssb-SubcarrierOffset-14)+pdcch-ConfigSIB1)mod32, where GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, and GSCN-Current is the GSCN value of the current SS / PBCH block indicating that no RMSI exists. SSB For FR1 is For FR2 being 0, ssb-SubcarrierOffset takes values ​​from {12,13,14,15}, and pdcch-ConfigSIB1 takes values ​​from {0,1,...,254,255}.

[0150] Table 7

[0151]

[0152]

[0153]

[0154] Table 7. Reserved code points in pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset, and one of the reserved bits of the MSB used to indicate the subcarrier offset in FR1 (e.g., ), to provide instructions for FR1.

[0155] Table 8

[0156]

[0157] Table 8. Using reserved code points in pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset for indication against FR2

[0158] In Tables 7 and 8, GSCN-Current is the GSCN value indicating the current SS / PBCH block where no RMSI exists. During initial cell selection, the UE may assume that the higher-layer parameter ssb-SubcarrierOffset takes a value from {12, 13, 14, 15} for FR2 or for FR1... In the case where the values ​​are {8, 9, 10, 11, 12, 13, 14, 15} (equivalent to k_SSB taking values ​​from {12, 13, 14, 15} for FR2 and from {24, 25, 26, 27, 28, 29, 30, 31} for FR1 respectively), then no associated RMSI exists, and the UE can assume ssb-SubcarrierOffset, (For FR1 only) and the mapping of pdcch-ConfigSIB1 to the GSCN of the synchronization grid are based on Tables 7 and 8. The UE can search for the synchronization grid within the search band to obtain the cell definition SS / PBCH block, and the UE assumes that if for FR2, ssb-SubcarrierOffset = 15, and for FR1, ssb-SubcarrierOffset = 15 and There are no cell-defined SS / PBCH blocks within the given range of GSCN-Current-pdcch-ConfigSIB1 / 16 to GSCN-Current+pdcch-ConfigSIB1mod16.

[0159] Note that Tables 7 and 8 can be given equivalently by formulas. In the initial cell selection, the UE can assume that the higher-layer parameter ssb-SubcarrierOffset takes a value from {12, 13, 14, 15} for FR2 or for FR1... In the case where the values ​​are {8, 9, 10, 11, 12, 13, 14, 15} (equivalent to k_SSB taking values ​​from {12, 13, 14, 15} for FR2 and from {24, 25, 26, 27, 28, 29, 30, 31} for FR1 respectively), then no associated RMSI exists, and the UE can assume that when... Furthermore, when ssb-SubcarrierOffset = 8, 9, or 10, for FR1, the GSCN of the synchronization raster is calculated based on: GSCN-cell-defined-SSB = GSCN-Current + 256 * (ssb-SubcarrierOffset - 8) + pdcch-ConfigSIB1 + 1; when Furthermore, when ssb-SubcarrierOffset = 11, 12, or 13, for FR1, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current-256 * (ssb-SubcarrierOffset-11) - pdcch-ConfigSIB1 - 1; when ssb-SubcarrierOffset = 12, for FR2, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current + pdcc. h-ConfigSIB1+1 is calculated; when ssb-SubcarrierOffset = 13, for FR2, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current-pdcch-ConfigSIB1-1, and the UE can search for this synchronization grid within the search band to obtain the cell-defined SS / PBCH block; and the UE assumes that if for FR2, ssb-SubcarrierOffset = 15, and for FR1, ssb-SubcarrierOffset = 15 and There are no cell-defined SS / PBCH blocks within the given range of GSCN-Current-pdcch-ConfigSIB1 / 16 to GSCN-Current+pdcch-ConfigSIB1 mod16, where GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, and GSCN-Current is the GSCN value of the current SS / PBCH block indicating the absence of an RMSI. Note that a special case is when pdcch-ConfigSIB1 = 0, the given range is equivalent to a single GSCN point GSCN-Current, and the UE assumes that the absence of a cell-defined SS / PBCH block at GSCN-Current is equivalent to the absence of further information about the next cell-defined SS / PBCH block.

[0160] Table 9

[0161]

[0162]

[0163] Table 9. Reserved code points in pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset, and one of the reserved bits of the MSB used to indicate the subcarrier offset in FR1 (e.g., ), to provide instructions for FR1.

[0164] Table 10

[0165]

[0166]

[0167] Reserved code points in Table 10.pdcch-ConfigSIB1 (e.g., 8 bits) and ssb-SubcarrierOffset for indication against FR2.

[0168] In Tables 9 and 10, GSCN-Current is the GSCN value indicating that no RMSI exists in the current SS / PBCH block. During initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value from {12,13,14,15} (or equivalently {r_0,r_1,r_2,r_3}), then no associated RMSI exists, and the UE may assume that ssb-SubcarrierOffset... (For FR1 only) The mapping of pdcch-ConfigSIB1 to the GSCN of the synchronization grid is based on Tables 9 and 10. The UE can search for the synchronization grid within the search band to obtain the cell definition SS / PBCH block, and the UE assumes that if ssb-SubcarrierOffset = 15 for FR1, then from arrive There are no cell-defined SS / PBCH blocks within the given range, and if for FR2, ssb-SubcarrierOffset = 15 or 14, then there are no cell-defined SS / PBCH blocks within the given range from GSCN-Current-((ssb-SubcarrierOffset-14)*256+pdcch-ConfigSIB1) / 32 to GSCN-Current+((ssb-SubcarrierOffset-14)*256+pdcch-ConfigSIB1)mod32.

[0169] Note that Tables 9 and 10 can be given equivalently by formulas. In the initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes values ​​in {12, 13, 14, 15} (or equivalently {r_0, r_1, r_2, r_3}), then no associated RMSI exists, and the UE may assume that when... When ssb-SubcarrierOffset = 0 and ssb-SubcarrierOffset = 12 or 13, 14, for FR1, the GSCN of the synchronization raster is calculated based on GSCN-cell-defined-SSB = GSCN-Current + 256 * (ssb-SubcarrierOffset - 12) + pdcch-ConfigSIB1 + 1; when Furthermore, when ssb-SubcarrierOffset = 12, 13, or 14, for FR1, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current-256 * (ssb-SubcarrierOffset-12) - pdcch-ConfigSIB1 - 1; when ssb-SubcarrierOffset = 12, for FR2, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-Current + pdcch-ConfigSIB1 + 1; when ssb-SubcarrierOffset = 13, for FR2, the GSCN of the synchronization grid... It is calculated based on GSCN-cell-defined-SSB = GSCN-Current-pdcch-ConfigSIB1 - 1. The UE can search for this synchronization grid within the search band to obtain the cell-defined SS / PBCH block. The UE assumes that if ssb-SubcarrierOffset = 15 for FR1 and ssb-SubcarrierOffset = 15 or 14 for FR2, then there is no cell-defined SS / PBCH block within the given range from GSCN-Current - (a*256 + pdcch-ConfigSIB1) / 32 to GSCN-Current + (a*256 + pdcch-ConfigSIB1) mod 32, where for FR1... For FR2, a = (ssb-SubcarrierOffset-14), and GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block, GSCN-Current is the GSCN value of the current SS / PBCH block indicating that no RMSI exists, ssb-SubcarrierOffset is taken from {12,13,14,15}, and pdcch-ConfigSIB1 is taken from {0,1,...,254,255}.

[0170] In one embodiment, 8 bits are used to indicate the frequency range within which the next SS / PBCH block associated with the RMSI can be located, where each of the 256 code points represents the frequency range within which the SS / PBCH block can be located. After decoding these 8 bits, if there are multiple synchronization grids within the indicated range, the UE can directly enter the indicated frequency range and blindly search for all synchronization grids within the indicated range; if there is only a single synchronization grid within the indicated range, the UE can directly search for the indicated synchronization grid.

[0171] In one example, in Table 11, for a given frequency band, it is assumed that the lowest carrier frequency is F_1 and the highest carrier frequency is F_2. The entire frequency band is divided into 256 frequency position ranges that may contain synchronization grids, where the interval between each range is I_F = (F_2 - F_1) / 255, and each of the 256 code points represents one of the frequency position ranges.

[0172] Table 11

[0173] Code point index Frequency location range containing (one or more) synchronization grids 1 [F_1,F_1+I_F) 2 [F_1+I_F,F_1+2*I_F) ... ... 255 [F_1+253*I_F,F_1+254*I_F) 256 [F_1+254*I_F,F_2]

[0174] Table 11. F_1 and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization grid (i.e., F_1 ​​is the position of the first synchronization grid in the given frequency band, and F_2 is the position of the last synchronization grid in the given frequency band).

[0175] In another example, in Table 12, for a given frequency band, assume the lowest carrier frequency is F_1, the highest carrier frequency is F_2, and the UE detects the current position (on the synchronization grid) of the SS / PBCH block without RMSI as F_S. The remaining portion of the frequency band to be searched is divided into 256 frequency position ranges that may contain the synchronization grid, where the interval between each range is I_F = (F_2 - F_c) / 255 if the search order is assumed to be from low to high in the frequency domain (while the interval between each range is I_F = (F_c - F_1) / 255 if the search order is assumed to be from high to low in the frequency domain), and each of the 256 code points represents one of the frequency position ranges.

[0176] Table 12

[0177]

[0178] Table 12. F_1 and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization grid (i.e., F_1 ​​is the position of the first synchronization grid in the given frequency band, and F_2 is the position of the last synchronization grid in the given frequency band).

[0179] In one embodiment, if there is only one synchronization grid in each indicated range (note that the ranges may be uneven), the foregoing embodiments are effectively equivalent to indicating the exact location of the synchronization grid in the frequency band. Still, one code point can be used to indicate that there is no cell-defined SS / PBCH block in the frequency band, and this code point can be a code point separate from the code point indicating the synchronization grid location, or a synchronization grid location in the frequency domain corresponding to the current search location (i.e., also on the synchronization grid).

[0180] In one sub-implementation, if the number of synchronization grates in a frequency band exceeds 255, some reserved bits in the PBCH content or some reserved code points from one or more other fields in the PBCH content can be combined with the 8 bits configured in the RMSICORESET to obtain a larger indication range. For example, if an additional bit can be combined, the indication range can be extended to 511 or 512 (depending on which code point indicates that there is no cell definition SS / PBCH block in the frequency band). As another example, if up to four other reserved code points can be combined, the indication range can be extended to as high as 1023 or 1024 (depending on which code point indicates that there is no cell definition SS / PBCH block in the frequency band), which may be more than sufficient for the grating index within the frequency band indicating NR.

[0181] In one example, another field in the PBCH contention or reserved code point can be used to indicate the band number, such that if the current synchronization grid of the SS / PBCH block is not associated with the RMSI, it is located in the overlapping bandwidth between the two bands.

[0182] In one example, as shown in Table 13, an 8-bit RMSI CORESET configuration (i.e., pdcch-ConfigSIB1) in the MIB and reserved code points in ssb-SubcarrierOffset (note that there are 4 reserved code points in ssb-SubcarrierOffset, which can be represented as r_0, r_1, r_2, r_3) are used, where GSCN-first is the first GSCN value of the current search band, GSCN-step-size is the step size of the GSCN values ​​of the current search band (e.g., the specific values ​​of GSCN-first and GSCN-step-size for each band can be found in the relevant wireless communication specifications), and a separate code point is used to indicate that there is no cell-defined SS / PBCH block in the current search band (e.g., ssb-SubcarrierOffset is r_0 and pdcch-ConfigSIB1 is 0).

[0183] In the initial cell selection, the UE can assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value in {r_0,r_1,r_2,r_3}, then no associated RMSI exists, and the UE can assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization grid is according to Table 13. The UE can search for the synchronization grid within the search band to obtain the cell definition SS / PBCH block. Note that the maximum number of GSCNs supported in the NR band is 620, which gives the determination that the GSCN range indicated in Table 13 is at most GSCN-first to GSCN-first+619*GSCN-step-size.

[0184] If new frequency bands are defined in NR, the indication range can be further expanded using the remaining reserved combinations of code points. For example, if the maximum number of GSCNs for the supported NR frequency bands is determined to be X, then the GSCN range indicated in Table 13 can be from GSCN-first to GSCN-first+(X-1)*GSCN-step-size. Note that the indication capability of Table 13 can be up to X 1023.

[0185] It should also be noted that Table 13 can be given equivalently by formula. In initial cell selection, the UE can assume that if the higher-layer parameter ssb-SubcarrierOffset takes values ​​from {r_0,r_1,r_2,r_3}, which correspond to index-reserved-ssb-SubcarrierOffset taking values ​​from {0,1,2,3} respectively, then no associated RMSI exists. Furthermore, the UE can assume that when {index-reserved-ssb-SubcarrierOffset,pdcch-ConfigSIB1}{0,0}, the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-first + 256 * index-reserved-ssb-SubcarrierOffset * GSCN-step-size + (pdcch-ConfigSIB1 - 1) * GSCN-step-size. The UE can then perform a search... The UE searches the synchronization grid within the frequency band to obtain the cell-defined SS / PBCH block. The UE assumes that if {index-reserved-ssb-SubcarrierOffset,pdcch-ConfigSIB1} = {0,0}, then there is no cell-defined SS / PBCH block in the current search band. Here, GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block in the current search band, GSCN-first is the first GSCN value in the current search band, GSCN-step-size is the step size of the GSCN values ​​in the current search band, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (taken from {0,1,2,3}), and pdcch-ConfigSIB1 takes values ​​from {0,1,...,254,255}.

[0186] In one embodiment, GSCN-cell-defined-SSB can be restricted to less than or equal to GSCN-first + 619 * GSCN-step-size, and all other code points are reserved for forward compatibility.

[0187] Table 13

[0188]

[0189]

[0190] Table 13. Indicative Capability

[0191] In another example, Table 14 shows the use of an 8-bit RMSI CORESET configuration (i.e., pdcch-ConfigSIB1) and reserved code points in the ssb-SubcarrierOffset of the MIB (note that there are 4 reserved code points in the ssb-SubcarrierOffset, which can be represented as r_0, r_1, r_2, r_3), where GSCN-first is the first GSCN value of the currently searched band, and GSCN-step-size is the step size of the GSCN values ​​of the currently searched band (e.g., the specific values ​​of GSCN-first and GSCN-step-size for each band can be found in the relevant wireless communication specifications), and no single code point is used to indicate that there is no cell-defined SS / PBCH block in the currently searched band, because the code point corresponding to the GSCN of the currently located SS / PBCH block is used to indicate the cell-defined SS / PBCH block in the currently searched band.

[0192] In the initial cell selection, the UE may assume that if the higher-layer parameter ssb-SubcarrierOffset takes a value in {r_0,r_1,r_2,r_3}, then no associated RMSI exists, and the UE may assume that the mapping of ssb-SubcarrierOffset and pdcch-ConfigSIB1 to the GSCN of the synchronization grid is according to Table 14. The UE may search for the synchronization grid within the search band to obtain the cell definition SS / PBCH block.

[0193] The UE assumes that if the GSCN of the cell-defined SS / PBCH block determined by Table 14 is equal to the GSCN of the current SS / PBCH block, then there is no cell-defined SS / PBCH block in the current search band. Note that the maximum number of GSCNs supported in the NR band is 620, which gives the determination that the GSCN range indicated in Table 14 is at most from GSCN-first to GSCN-first + 619 * GSCN-step-size.

[0194] If new frequency bands are defined in NR, the indication range can be further expanded using the remaining reserved combinations of code points. For example, if the maximum number of GSCNs for the supported NR frequency bands is determined to be X, then the GSCN range indicated in Table 14 could be from GSCN-first to GSCN-first+(X-1)*GSCN-step-size. Note that the indication capability of Table 14 can be X up to 1024. Also note that Table 14 can be given equivalently by formula.

[0195] In the initial cell selection, the UE can assume that if the higher-layer parameter ssb-SubcarrierOffset takes values ​​from {r_0,r_1,r_2,r_3}, which correspond to index-reserved-ssb-SubcarrierOffset taking values ​​from {0,1,2,3} respectively, then no associated RMSI exists. Furthermore, the UE can assume that the GSCN of the synchronization grid is calculated based on GSCN-cell-defined-SSB = GSCN-first + 256 * index-reserved-ssb-SubcarrierOffset * GSCN-step-size + pdcch-ConfigSIB1 * GSCN-step-size. The UE can then search for this synchronization grid within the search band to obtain the cell definition SS / PB. The UE assumes that if GSCN-cell-defined-SSB equals the GSCN of the current SS / PBCH block, then there is no cell-defined SS / PBCH block in the current search band. Here, GSCN-cell-defined-SSB is the GSCN of the next cell-defined SS / PBCH block in the current search band, GSCN-first is the first GSCN value in the current search band, GSCN-step-size is the step size of the GSCN values ​​in the current search band, index-reserved-ssb-SubcarrierOffset is the index of the reserved code point in ssb-SubcarrierOffset (taken from {0,1,2,3}), and pdcch-ConfigSIB1 takes a value from {0,1,...,254,255}. In one embodiment, GSCN-cell-defined-SSB can be restricted to be less than or equal to GSCN-first + 619 * GSCN-step-size, and all other code points are reserved for forward compatibility.

[0196] Table 14

[0197]

[0198]

[0199] Table 14. Indicative Capability

[0200] In one embodiment, a field in the PBCH payload is used as a bitmap indicating the frequency locations or carrier ranges within which the SS / PBCH(one or more) blocks associated with the RMSI can reside. After decoding the fields in the PBCH payload, the UE can find all frequency location ranges within which the SS / PBCH(one or more) blocks associated with the RMSI can reside. The UE can select one of the indicated location ranges (e.g., represented as "1" in the bitmap for that frequency range) and blindly search all synchronization grids within the indicated range.

[0201] For an example, assume the lowest carrier frequency is F_1 and the highest carrier frequency is F_2. The entire frequency band is divided into N frequency location ranges that may contain synchronization grids: [F_1, F_1+I_F), [F_1+I_F, F_1+2*I_F), ..., [F_1+(N-1)*I_F, F_2], where the interval between each range is I_F = (F_2-F_1) / (N-1), and each of the 2^N code points represents a bitmap indicating which of the N ranges contains the SS / PBCH block with RMSI. Table 15 shows an example with N=8. Table 16 shows an example with N=4.

[0202] Table 15

[0203] Code point index A bitmap indicating the frequency location range containing one or more synchronization grids. 1 00000000 2 00000001 ... ... 255 11111110 256 11111111

[0204] Table 15. N = 8, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization grid (i.e., F_1 ​​is the position of the first synchronization grid in the given frequency band, and F_2 is the position of the last synchronization grid in the given frequency band).

[0205] Table 16

[0206] Code point index A bitmap indicating the frequency location range containing one or more synchronization grids. 1 0000 2 0001 ... ... 15 1110 16 1111

[0207] Table 16. When N = 4, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization grid (i.e., F_1 ​​is the position of the first synchronization grid in the given frequency band, and F_2 is the position of the last synchronization grid in the given frequency band).

[0208] In another example, assume the lowest carrier frequency is F_1, the highest carrier frequency is F_2, and the UE detects the current position (on the synchronization grid) of the SS / PBCH block without RMSI as F_S. The remaining portion of the frequency band to be searched is divided into N frequency position ranges that may contain the synchronization grid: [F_c, F_c+I_F), [F_c+I_F, F_c+2*I_F), ..., [F_c+(N-1)*I_F, F_2], where, if the search order is assumed to be from low to high in the frequency domain, the interval of each range is I_F = (F_2-F_c) / (N-1) (if the search order is assumed to be from low to high in the frequency domain, the interval of each range is I_F = (F_2-F_c) / (N-1)). In the domain, from high to low, the interval of each range is I_F = (F_c - F_1) / (N-1), and the ranges are [F_1, F_1 ​​+ I_F), [F_1 + I_F, F_1 ​​+ 2 * I_F), ..., [F_1 + (N-1) * I_F, F_c]), and each of the 2^N code points represents a bitmap that indicates which of the N ranges contains the SS / PBCH block with RMSI. Table 17 shows an example for N = 8, and Table 18 shows an example for N = 4.

[0209] Table 17

[0210] Code point index A bitmap indicating the frequency location range containing one or more synchronization grids. 1 00000000 2 00000001 ... ... 255 11111110 256 11111111

[0211] Table 17. N = 8, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization grid (i.e., F_1 ​​is the position of the first synchronization grid in the given frequency band, and F_2 is the position of the last synchronization grid in the given frequency band).

[0212] Table 18

[0213] Code point index A bitmap indicating the frequency location range containing one or more synchronization grids. 1 0000 2 0001 ... ... 15 1110 16 1111

[0214] Table 18. When N = 4, F_1 ​​and F_2 can be defined as the lowest and highest carrier frequencies of the bandwidth containing the synchronization grid (i.e., F_1 ​​is the position of the first synchronization grid in the given frequency band, and F_2 is the position of the last synchronization grid in the given frequency band).

[0215] In one embodiment, when multiple SS / PBCH blocks are supported over the broadband, there may be SS / PBCH blocks that are not located on the synchronization grid. For those SS / PBCH blocks that may or may not be associated with the RMSI, and whether an associated RMSI exists, the code points within the PRB grid offset indicator are used to indicate this. If the UE successfully detects an SS / PBCH block on the synchronization grid, and further detects that no RMSI is associated with the SS / PBCH block, the UE can utilize the 8 bits initially used for RMSI configuration to indicate the precise location of the next or other SS / PBCH blocks on the synchronization grid, allowing the UE to skip some synchronization grid locations for blind searching. If the indicated SS / PBCH(one or more) is located on the synchronization grid, all indication methods in Component I can be reused here.

[0216] In another embodiment, when multiple SS / PBCH blocks are supported over the broadband, there may be SS / PBCH blocks that are not located on the synchronization grid. For those SS / PBCH blocks that may or may not be associated with an RMSI, and whether an associated RMSI exists, the code points within the PRB grid offset indicator are used to indicate this. If the UE successfully detects that an SS / PBCH block is not on the synchronization grid, and further detects that there is no RMSI associated with the SS / PBCH block, the UE can utilize the 8 bits initially used for RMSI configuration to indicate the precise location of the next or other SS / PBCH blocks that may or may not be on the synchronization grid and may or may not have an associated RMSI.

[0217] In one example, 8 bits are used to indicate the exact location of another SS / PBCH block, which may or may not have an associated RMSI. Each of the 256 code points represents the exact relative location compared to the current SS / PBCH block without an RMSI. After decoding these 8 bits from the MIB, the UE can directly find the frequency location of the other indicated SS / PBCH block. The relative position of the current synchronization grid up to the detected SS / PBCH block is measured by the number of PRBs based on the SS parameter set for that frequency band, where the number is always non-negative, meaning the relative position is always defined according to the initial cell search order within that frequency band. It is necessary to define the code point for the "0" relative position of the next SS / PBCH block because the code point can use 8 bits within the indication capability (e.g., for the bandwidth of 255 PRBs) to indicate an SS / PBCH synchronization without an associated RMSI, and the UE can skip all 255 possible PRBs used to search for the SS / PBCH block.

[0218] In another embodiment, when multiple SS / PBCH blocks are supported over a broadband area, there may be SS / PBCH blocks that are not located on the synchronization grid. For those SS / PBCH blocks that may or may not be associated with the RMSI, and whether an associated RMSI exists, it is indicated by the code point within the PRB grid offset indicator (i.e., the reserved code point in ssb-SubcarrierOffset, e.g., r_0). The 8 bits of pdcch-ConfigSIB1 can be reserved for other purposes (e.g., measurement parameter configuration).

[0219] At least some or all of the following fields are provided in the content of the compact DCI format dedicated to the common control channel, which may include at least one of transmitting Residual Minimal System Information (RMSI), broadcasting other system information (OSI), paging, and random access response (RAR) in 4-step RACH or 2-step RACH.

[0220] Generally, two types of PDSCH resource allocation are defined, where type 0 uses a bitmap to indicate resource allocation with configurable granularity of frequency resources determined by the size of the BWP (e.g., an RBG typically consists of multiple VRBs), and type 1 uses a resource indication value (RIV) to indicate the length of consecutive VRBs and the starting VRB in the frequency domain with a granularity of 1 VRB.

[0221] In one embodiment, for the common control channel provided in this disclosure, only a single type of resource allocation scheme is supported in the compact DCI format, and header bits are not inherently required to indicate the type of resource allocation (or header bits with fixed values ​​indicating the single supported type of resource allocation are still retained).

[0222] In one example, since all UEs in the cell can receive messages for the common control channel, it is beneficial to try to maximize the utilization of the configured resources at a granularity of X VRBs. Therefore, only Type 1 resource allocation schemes are supported in the compact DCI format. Generally, the bit width used to define the Type 1 resource allocation of the RIV can be related to the size of the BWP; however, for the common control channel provided in this disclosure, the definition of the RIV can be optimized because the size of the BWP used for PDSCH is not as flexible as that of regular PDSCH data.

[0223] In one example, the size of the BWP used to define the RIV is fixed for all common control channels, for example, 96 (this is the maximum number of RBs in the CORESET BW configured in the MIB). Then, the bit width of this field is common for all common control channels. The RIV can be defined as RIV = 96 * (L_VRB - 1) + S_VRB, where L_VRB is the length of the VRB and S_VRB is the starting VRB index.

[0224] Figure 10 An example SS / PBCH block 1000 multiplexed with RMSI CORESET according to an embodiment of this disclosure is shown. Figure 10 The embodiment of the SS / PBCH block 1000 multiplexed with RMSI's CORESET shown is for illustrative purposes only. Figure 10 This disclosure is not intended to limit the scope to any particular implementation.

[0225] Note that a special sub-example of the above example is where L_VRB = CORESET_BW and S_VRB = 0, which means that PDSCH BW is the same as CORESET_BW and can be applied to some multiplexing patterns (e.g., at least for...). Figure 10 In modes 2 and / or 3, and / or some cases of mode 1, where PDSCH coverage is limited (e.g., with a small BW and / or a small number of OFDM symbols). In the sub-example, no bits are required, and in the specification, the RIV values ​​(or equivalent L_VRB and S_VRB) can be hardcoded.

[0226] In another example, the size of the BWP of the RIV is defined as equal to the actual CORESET BW configured in the MIB, and can be different for different common control channels. The RIV can be defined as RIV = CORESET_BW * (L_VRB - 1) + S_VRB, where L_VRB is the length of the VRB, S_VRB is the starting VRB index, and CORESET_BW is the BW of the CORESET configured in the MIB.

[0227] Note that a specific sub-example of this example is where L_VRB = CORESET_BW and S_VRB = 0, which means that PDSCH BW is the same as CORESET_BW and can be applied to some multiplexing patterns (e.g., at least for...). Figure 10 In this sub-example, modes 2 and / or 3, and / or some cases of mode 1, where PDSCH coverage is limited (e.g., with a small BW and / or a small number of OFDM symbols). In this sub-example, no bits are required, and the RIV values ​​(or equivalent L_VRB and S_VRB) can be hard-coded in the specification.

[0228] In one example (which can be applied to all the examples above), the length of consecutive VRBs and the starting VRB can be configured based on the CCE number (#), for example, to make the coverage of PDCCH and PDSCH compatible.

[0229] In the aforementioned embodiments / examples of the Type 1 resource allocation scheme, X is the number of VRBs as the resource allocation granularity. Note that the value of X determines the number of bits representing the frequency domain resource field. For example, the number of bits can be determined according to log2[(N_RB^BWP / X)*(N_RB^BWP / X+1) / 2], where N_RB^BWP is the number of RBs in the provided BWP, and for RMSI, N_RB^BWP can be the same as the CORESET BW in terms of RBs.

[0230] In one example, X is predefined in the specification and takes a common value for cases using a Type 1 resource allocation scheme. For example, X = 1 corresponds to the most flexible resource allocation, but may require more bits to represent the field. For other instances, X = 2, 4, or 6 correspond to less flexible resource allocations compared to X = 1, but may require fewer bits. In yet another instance, X has the same granularity as the interleaver.

[0231] In another example, X is predefined in the specification, and specific values ​​are defined based on the CORESET BW. In this example, X can have multiple values ​​depending on the CORESET BW. The purpose of this multi-granularity of X is to attempt to align the number of bits used to represent the frequency domain resource field when the total BW is different; for example, CORESET BW / X in RBs is constant at least for some values ​​of CORESET BW. Tables 11 to 13 show some specific instances of this example.

[0232] Table 19

[0233]

[0234] Table 19. Core Set BW / X in RB units [Table 20]

[0235]

[0236] Table 20. CORESET BW / X in RB units [Table 21]

[0237]

[0238]

[0239] Table 21. Core Set BW / X in RB units

[0240] In another example, X can be configured by the RRC and assumed by the UE as a default value during initial access. For example, the default X = 1, which corresponds to the most flexible resource allocation scenario, but may require more bits to represent the field; for example, 13 bits are needed for a CORESET BW as 96 RBs. For other instances, the default X = 2, 4, or 6, which corresponds to a less flexible resource allocation scenario compared to X = 1, but may require fewer bits. For yet another instance, the default X is the same as the granularity of the interleaver.

[0241] In another embodiment, for the common control channel provided in this disclosure, two types of resource allocation schemes are supported in the compact DCI format to give full flexibility to the allocation of PDSCH resources in the frequency domain, and the definition of the bitmap in type 0 and the definition of RIV in type 1 can refer to the definition in the general case, or use the definition described in the above embodiments, wherein only type 1 resource allocation is supported.

[0242] Generally, for type 1 resource allocation, block-interleaved VRB-to-PRB mapping is supported to obtain frequency diversity gain, and the indication of block-interleaved or non-block-interleaved VRB-to-PRB mapping can be carried by a single bit in the DCI format.

[0243] In one embodiment, for the common control channel provided in this disclosure, if only a Type 1 resource allocation scheme is supported, only block-interleaved VRB-to-PRB mapping is supported to obtain frequency diversity gain, and no indication is required in the compact DCI format. In this case, because only the initial active BWP is used to transmit the common control channel, the block-interleaved VRB-to-PRB mapping can be performed within the entire initial active BWP, which is much simpler than the general case where multiple BWPs may exist and overlap. In this embodiment, the fields of the VRB-to-PRB mapping can be hardcoded in the specification as block-interleaved VRB-to-PRB mapping, and the block size used for interleaving can also be hardcoded in the specification (e.g., the same granularity as the resource allocation).

[0244] In another embodiment, for the common control channel provided in this disclosure, both block-interleaved and non-block-interleaved VRB-to-PRB mappings are supported, and one bit in the compact DCI format is used to indicate the VRB-to-PRB mapping mode (e.g., block-interleaved or non-block-interleaved).

[0245] Generally, time-domain PDSCH resources are characterized by the time-slot level timing difference (e.g., denoted as T_slot) between the time slot containing the corresponding CORESET and the time slot containing the PDSCH, as well as the length of the starting OFDM symbol (e.g., denoted as S_sym) and the OFDM symbol of the PDSCH within the time slot (e.g., denoted as L_sym).

[0246] In one embodiment, for the common control channel provided in this disclosure, time-domain PDSCH resources can be defined according to the multiplexing mode of SS / PBCH blocks and CORESET / PDSCH. Note that, as Figure 10 As shown, NR supports three multiplexing modes: SS / PBCH blocks and CORESET / PDSCH.

[0247] In one example, Mode 1 refers to a multiplexing mode where the SS / PBCH block and the RMSI CORESET occur in different time instances, and the SS / PBCH block TX BW and the initial activity DL BWP containing the RMSI CORESET overlap. Note that the time difference between the SS / PBCH block and the CORESET / PDSCH can be 0 or greater than one time slot.

[0248] In another example, mode 2 refers to a reuse mode in which the SS / PBCH block and the RMSI CORESET occur in different time instances, and the SS / PBCH block TX BW and the initial activity DL BWP containing the RMSI CORESET do not overlap.

[0249] In yet another example, mode 3 refers to a reuse mode in which the SS / PBCH block and the RMSI CORESET occur in the same time instance, and the SS / PBCH block TX BW and the initial activity DL BWP containing the RMSI CORESET do not overlap.

[0250] In one example, if the multiplexing mode of the SS / PBCH block and CORESET / PDSCH is configured to mode 1, as indicated in the MIB of the NR-PBCH within the SS / PBCH block, then T_slot can be a configurable integer with several values, and S_sym and L_sym can be jointly encoded into RIV. For example, slot-level differential T_slot can be configured from 0, 2*u, 5*u, 7*u for <6GHz, and from 0, 2.5*u, 5*u, 7.5*u for >6GHz, where u = SS_SCS / 15kHz. In another instance, S_sym and L_sym can be jointly encoded into RIV according to the following formula: if L_sym-1 < 7, then RIV = 14*(L_sym-1) + S_sym; otherwise, RIV = 14*(14-L_sym+1) + (14-1-S_sym).

[0251] In one instance, the temporal PDSCH resources of mode 1 (e.g., L_sym, S_sym, and T_slot) can be determined based on the value M in the parameter table of PDCCH monitoring timing, where M refers to the time difference (measured in slots) between slots containing CORESETs corresponding to SS / PBCH blocks at indices i and i+1.

[0252] In one example, if M=2, then T_slot>0, which means that cross-slot scheduling of PDSCH can be supported if the time slot difference between CORESETs is 2 time slots.

[0253] In one example, if M = 1 / 2 and M = 1, then T_slot = 0, which means that if the time slot difference between CORESETs is 1 / 2 time slot and 1 time slot, then simultaneous time slot scheduling of PDSCH can be supported.

[0254] In such an example, the time-domain PDSCH resources of Mode 1 (e.g., L_sym, S_sym, and T_slot) can be determined based on the RMSI configuration in the MIB (i.e., RMSI-PDCCH-Config). If a 4-bit table containing up to 16 configurations is defined for the PDSCH time-domain resources in general, then at least one configuration in that table can be used for each configuration of RMSI (i.e., each value of RMSI-PDCCH-Config).

[0255] In one specific example, if there is only one configuration in the table for each configuration of RMSI, then the association can be hardcoded in the specification, and the field does not require any bits. In another specific example, if there are at most Y configurations in the table for each configuration of RMSI, then the field requires at most log2(Y) bits, for example, Y=4 for a comprehensive example regarding complexity and flexibility.

[0256] In another example, the foregoing embodiments / examples can be combined with or stand alone with this example, and the scrambling sequence of PDCCH within CORESET can be based on the SS / PBCH block index, so that the UE can detect the SS / PBCH block index during the monitoring window duration and save some SS / PBCH block transmissions.

[0257] In another example, if the multiplexing mode of the SS / PBCH block and CORESET / PDSCH is configured as Mode 2, indicated in the MIB of the NR-PBCH within the SS / PBCH block, then T_slot can be hardcoded to 0 (or the field is absent in the DCI format for Mode 2), and S_sym and L_sym can be determined by the symbols within the time slot mapped for the SS / PBCH block (e.g., determined based on the SS block index I_SSB and the subcarrier spacing SCS_SS of the SS / PBCH block). Note that in one embodiment, S_sym and L_sym can still be jointly encoded via RIV using the same method as in Mode 1, or in the specification, S_sym and L_sym can be hardcoded and the field for time-domain PDSCH resources in the DCI format is not required.

[0258] In one instance, S_sym can be a symbol mapped to the first symbol of the corresponding SS / PBCH block (i.e., a symbol mapped to NR-PSS), and L_sym can be hardcoded to 4. Table 22 shows an example list of this instance.

[0259] Table 22

[0260]

[0261]

[0262] Table 22. S_sym and L_sym

[0263] In another instance, S_sym can be a symbol mapped to the first symbol of the corresponding SS / PBCH block (i.e., a symbol mapped to the NR-PSS, and the specific value of T_slot for each SCS_SS can be obtained by referring to Table 22), and L_sym can be configured (e.g., it can be configured in 1, 2, 3 and 4).

[0264] In yet another example, if the multiplexing mode of the SS / PBCH block and CORESET / PDSCH is configured as Mode 3, indicated in the MIB of the NR-PBCH within the SS / PBCH block, then T_slot can be hardcoded to 0 (or the field is absent in the DCI format for Mode 3), and S_sym and L_sym can be determined by the symbols within the time slot mapped for the SS / PBCH block (e.g., determined based on the SS block index I_SSB and the subcarrier spacing SCS_SS of the SS / PBCH block). Note that in one embodiment, S_sym and L_sym can still be jointly encoded via RIV using the same method as in Mode 1, or in the specification, S_sym and L_sym can be hardcoded without requiring the field for time-domain PDSCH resources in the DCI format.

[0265] In one instance, S_sym can be a symbol mapped to the third symbol of the corresponding SS / PBCH block (i.e., a symbol mapped to NR-SSS and NR-PBCH), and L_sym can be hardcoded to 2. Table 23 shows an example list of this instance.

[0266] Table 23

[0267]

[0268] Table 23. S_sym and L_sym

[0269] In another embodiment, for the common control channel provided in this disclosure, time-domain PDSCH resources can be jointly encoded with frequency-domain PDSCH resources, and defined according to the multiplexing mode of SS / PBCH blocks and CORESET / PDSCH (using the same or different bit widths for each multiplexing mode). Note that, as Figure 10 As shown, NR supports three multiplexing modes: SS / PBCH blocks and CORESET / PDSCH.

[0270] In one example, if the multiplexing mode of the SS / PBCH block and CORESET / PDSCH is configured to mode 1, then time-domain and frequency-domain resources can be jointly encoded, where the total number of REs is configurable. In one example, from the perspective of similar coverage, the total number of REs is compatible with the number of CCEs in the CORESET.

[0271] In another example, if the multiplexing mode of the SS / PBCH block and CORESET / PDSCH is configured as mode 2, then the time-domain resources and frequency-domain resources can be jointly encoded, where both the time-domain resources and frequency-domain resources are hard-coded.

[0272] In another example, if the multiplexing mode of the SS / PBCH block and CORESET / PDSCH is configured as mode 3, then the time-domain resources and frequency-domain resources can be jointly encoded, wherein both the time-domain resources and frequency-domain resources are hard-coded.

[0273] Generally, the modulation and coding scheme of the PDSCH is captured by the MCS table. In one embodiment, for the common control channel provided in this disclosure, the modulation and coding scheme of the PDSCH can be captured by a compact version of the MCS table, wherein only low-order modulation schemes are supported in the compact DCI format, such that the bit width of this field in the compact DCI format can be smaller than the bit width in other DCI formats.

[0274] In one embodiment, within all the common control channels provided in this disclosure, some channels, such as Broadcast OSI and RMSI, encode messages into multiple blocks and map them for different transmissions, requiring redundant versions to label different encoded blocks. Therefore, only for those channels can the compact DCI format have redundant version fields with different values ​​(e.g., four values ​​represented by 2 bits or eight values ​​represented by 3 bits), while for other channels, the compact DCI format can use the corresponding fields as default values ​​(e.g., 0).

[0275] In another embodiment, among all the common control channels provided in this disclosure, some channels, such as Broadcast OSI and RMSI, encode messages into multiple blocks and map them for different transmissions, making it necessary to use redundant versions to mark different encoded blocks. The redundant versions can be determined based on the SFN value (i.e., timing within the TTI) and are known to the UE, so that no bits of the redundant version field are needed for the common control channels provided in this disclosure.

[0276] Generally, TPC (Transmission Power Control) commands can be transmitted as part of the DCI format within a common search space. In one embodiment, for the common control channel provided in this disclosure, the compact DCI format may have a field for the TPC command used for PUCCH (e.g., having 2 bits). In another embodiment, for the common control channel provided in this disclosure, the compact DCI format field is not required prior to the RRC connection.

[0277] A header field for a compact DCI format is only required when the compact DCI format used for the common control channel has the same DCI size as another DCI format (e.g., another compact DCI format for msg4 used for RACH or some fallback DCI formats). In this case, the header field is used to distinguish between different DCI formats. If there is no DCI format with the same DCI size as the compact DCI format used for the common control channel, then a header field is essentially not required.

[0278] Generally, this flag is used to indicate whether reserved resources in both the frequency and time domains are excluded from the rectangular resources allocated for the PDSCH, where the reserved resources can be used for other purposes, such as forward compatibility or LTE-NR coexistence. In one embodiment, for the same purpose, this flag(s) still exist for the compact DCI format designed for the common control channel. In another embodiment, this field does not exist before RRC connection and is not required for the common control channel provided in this disclosure.

[0279] At least some or all of the following fields are not provided in the content of the compact DCI format designed specifically for the common control channel, which may include at least one of the transmissions of RMSI, OSI, paging and RAR.

[0280] The common control channel provided in this disclosure is primarily for initial access purposes; therefore, it is not necessary to configure or indicate the carrier and BWP used to transmit the common control channel provided in this disclosure. In one embodiment, the compact DCI format of the common control channel provided in this disclosure does not include fields for carrier indicator or BWP indicator.

[0281] In one embodiment, the bundle size of the PDSCH of the common control channel provided in this disclosure is fixed (e.g., 6 PRBs), and the compact DCI format of the common control channel provided in this disclosure does not include a field for the bundle size indicator.

[0282] The common control channel provided in this disclosure may not have new data transmissions; therefore, the new data indicator is not applicable. In one embodiment, the compact DCI format of the common control channel provided in this disclosure does not include a field for the new data indicator.

[0283] The common control channel provided in this disclosure may have only a single codeword, and the parameters associated with the second codeword may not be applicable to the common control channel. In one embodiment, the compact DCI format of the common control channel provided in this disclosure does not include fields of parameters of the second codeword (including modulation and coding schemes, new data indicators, and redundant versions).

[0284] The common control channel provided in this disclosure may not have any HARQ procedure, and the parameters related to HARQ may not be applicable to the common control channel. In one embodiment, the compact DCI format of the common control channel provided in this disclosure does not include the fields of parameters for the HARQ procedure (including HARQ procedure number, CBGFI, CBGTI, ACK / NACK resource index, HARQ timing indicator, and downlink allocation index).

[0285] Note that in one embodiment, if the compact DCI format is also applicable to RACH's msg4, then HARQ procedure-related parameters can be provided as fields in the compact DCI format.

[0286] The common control channel provided in this disclosure may not have multiple configurations of antenna ports and may only support single-layer transmission, such that the configuration of one or more antenna ports can be fixed for the PDSCH of the common control channel. In one embodiment, the compact DCI format of the common control channel provided in this disclosure does not include a field for one or more antenna ports.

[0287] Generally, the Transmission Configuration Indication (TCI) is used to provide beamforming to indicate, at least relative to the spatial QCL parameters, the QCL assumption between (one or more) DL RS antenna ports and (one or more) DMRS antenna ports of the DL data channel. For the common control channel provided in this disclosure, the common control channel is QCL-Q ...

[0288] An example of a compact DCI format design for a common control channel is shown in Table 24, where the total DCI size is approximately 20 to 30 bits, which is much smaller than other DCI formats (e.g., at least approximately 40 to 50 bits).

[0289] Table 24

[0290] Fields Number of bits Frequency domain PDSCH resources 13 Time-domain PDSCH resources ≤4 VRB to PRB mapping type 1 Reserved resource set on / off 2 Modulation and coding schemes <5 Redundant version 2 PUCCH's TPC command 2

[0291] Table 24. Compact DCI Format Design

[0292] Another example of a compact DCI format design for a common control channel is shown in Table 25, where the total DCI size is based on the SS / PBCH block and CORESET multiplexing mode, with the total DCI size being approximately 15 bits for mode 1 and less than 5 bits for modes 2 and 3.

[0293] Table 25

[0294] Fields Number of bits in multiplexing mode 1 Number of bits in multiplexing modes 2 and 3 Frequency domain PDSCH resources 13 ≤13 Time-domain PDSCH resources ≤2 0 Modulation and coding schemes <5 <5

[0295] Table 25. Compact DCI Format Design

[0296] The DMRS sequence of PDCCH is composed of a QPSK modulated Glow sequence, which is an XOR of two M sequences of length L, one of which is s A (n) is generated by g A (x) and initial condition c A Another M sequence was generated. B (n) is generated by g B (x) and initial condition c B The generated output shift offset Nc exists (e.g., Nc = 1600 in LTE) such that the QPSK modulated Glow sequence s(n) = (1 - 2 * (s A (2n+Nc)+s B (2n+Nc))mod2)) / v2+j*(1-2*((s A (2n+Nc+1)+s B (2n+Nc+1))mod2)) / v2 and s(n) are truncated to the desired DMRS sequence length N_DMRS. The length L of the Glide sequence is the same as that of the LTE-CRS (e.g., 2^31-1), and one of the M sequences s A (n) by g A (x)=x 31 +x 3 +1 is given, and its initial condition c A Fixed (e.g., c) A =1), while another M sequence s B (n) by g B (x)=x 31 +x 3 +x 2 +x+1 is given, and its initial condition c B Initial condition c B Carrying an ID (cell ID or C-RNTI) and a timing-related index, the DMRS sequence changes over time.

[0297] In one embodiment, the timing-related index includes a time slot index and a symbol index, and the initial condition is the product of the ID and the timing-related index.

[0298] In one example, c B= mod(c_1*(N_ID+1)*(14*N_slot+N_symbol+1)+c_2*(14*N_slot+N_symbol+1)+c_3*(N_ID+1),2^31), where c_1, c_2, and c_3 are predefined integers. Note that in this example, c_1 > 2^12 is required for mod 2^31 to be valid.

[0299] In another example, c B = mod(c_1*(2*N_ID+1)*(14*N_slot+N_symbol+1)+c_2*(14*N_slot+N_symbol+1)+c_3*(2*N_ID+1),2^31), where c_1, c_2, and c_3 are predefined integers. Note that in this example, c_1 > 2^11 is required for mod 2^31 to be valid.

[0300] In another example, c B = c_1*(N_ID+1)*(14*N_slot+N_symbol+1)+c_2*(14*N_slot+N_symbol+1)+c_3*(N_ID+1), where c_1, c_2, and c_3 are predefined integers. Note that in this example, c_1 ≤ 2^12. In one instance, c_1 = 2, c_2 = 2^12, and c_3 = 0, that is, c B =2*(N_ID+1)*(14*N_slot+N_symbol+1)+2^12*(14*N_slot+N_symbol+1).

[0301] In another example, c B = c_1*(2*N_ID+1)*(14*N_slot+N_symbol+1)+c_2*(14*N_slot+N_symbol+1)+c_3*(2*N_ID+1), where c_1, c_2, and c_3 are predefined integers. Note that in this example, c_1≤2^11.

[0302] Figure 11 A flowchart of a method 1100 for a UE according to an embodiment of the present disclosure is shown. Figure 11 The embodiments of method 1100 shown are for illustrative purposes only. Figure 11 This disclosure is not intended to limit the scope to any particular implementation.

[0303] like Figure 11 As shown, method 1100 begins with "Start". In step 1102, the UE (e.g., as...) Figure 1As shown in 111-116), the system receives synchronization signals and physical broadcast channel (SS / PBCH) blocks from the base station (BS) via the downlink channel using the first frequency position (GSCN-Current), whereby the GSCN-Current is based on a set of predefined synchronization grids determined by the Global Synchronization Channel Number (GSCN).

[0304] In one embodiment, in step 1102, the SS / PBCH block associated with the PDCCH, which includes scheduling information for the RMSI of the determined GSCN-Current, is indicated by at least one of the following: for the first carrier frequency range, the ssb-SubcarrierOffset field in the content of the PBCH based on values ​​in {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15}, and the ssb-SubcarrierOffset field in the content of the PBCH with a value of 0. Fields; for the first carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content based on values ​​in {0,1,2,3,4,5,6,7} and the ssb-SubcarrierOffset field in the PBCH content with a value of 1. The field; or for the second carrier frequency range, the ssb-SubcarrierOffset field in the contents of the PBCH based on the values ​​in {0,1,2,3,4,5,6,7,8,9,10,11}.

[0305] In one embodiment, in step 1102, SS / PBCH blocks not associated with PDCCHs including scheduling information for the RMSI of the determined GSCN-Current are indicated by at least one of the following: for a first frequency range, the ssb-SubcarrierOffset field in the content of the PBCH based on values ​​in {8,9,10,11,12,13,14,15} and the ssb-SubcarrierOffset field in the content of the PBCH with a value of 1. The field; or for the second frequency range, the ssb-SubcarrierOffset field in the contents of the PBCH based on the values ​​in {12,13,14,15}.

[0306] In such an embodiment, the frequency range in which other SS / PBCH blocks of the PDCCH configured with scheduling information including RMSI are not transmitted is indicated by at least one of the following: for the first carrier frequency range, when the value of the ssb-SubcarrierOffset field in the content of the PBCH is 15 and the content of the PBCH... The values ​​of the field GSCN-Current-pdcch-ConfigSIB1 / 16 to GSCN-Current+pdcch-ConfigSIB1 mod 16 are 1; or for the second carrier frequency range, the values ​​of the ssb-SubcarrierOffset field in the PBCH content are 15. In such an embodiment, pdcch-ConfigSIB1 includes 8 bits in the PBCH content.

[0307] In such an embodiment, when pdcch-ConfigSIB1 = 0, the frequency range of other SS / PBCH blocks in which PDCCHs configured with scheduling information including RMSI are not transmitted is given by GSCN-Current.

[0308] In such an embodiment, the second frequency position on which other SS / PBCH blocks configured with scheduling information for RMSI are transmitted in a PDCCH is indicated by at least one of the following: for the first carrier frequency range 1, when the ssb-SubcarrierOffset field in the content of the PBCH is based on a value in {8,9,10} and the content of the PBCH... The value of the field is 1 when GSCN-Current+256*(ssb-SubcarrierOffset-8)+pdcch-ConfigSIB1+1; for the first carrier frequency range 1, when the ssb-SubcarrierOffset field in the PBCH content is based on the value in {11,12,13} and the PBCH content... The value of the field is 1 when GSCN-Current-256*(ssb-SubcarrierOffset-11)-pdcch-ConfigSIB1-1; for the second carrier frequency range, the value of the ssb-SubcarrierOffset field in the PBCH content is 12 when GSCN-Current+pdcch-ConfigSIB1+1; or for the second carrier frequency range, the value of the ssb-SubcarrierOffset field in the PBCH content is 13 when GSCN-Current-pdcch-ConfigSIB1-1.

[0309] In such an embodiment, pdcch-ConfigSIB1 is 8 bits long in the content of PBCH.

[0310] In one embodiment, when the SS / PBCH block is configured with a PDCCH including scheduling information for the determined RMSI of the GSCN-Current, the processor is further configured to determine the scheduling information for the RMSI based on the SS / PBCH block and the multiplexing mode of the control resource set (CORESET) including the PDCCH, the scheduling information for the RMSI including at least the time-domain resource allocation of the physical downlink shared channel (PDSCH) for the RMSI.

[0311] In step 1104, the UE decodes the PBCH included in the received SS / PBCH block.

[0312] In step 1106, the UE identifies the contents of the decoded PBCH.

[0313] In step 1108, the UE determines the configuration of at least one of the following: an SS / PBCH block associated with a physical downlink control channel (PDCCH) that includes scheduling information for the residual minimum system information (RMSI) regarding the GSCN-Current, or an SS / PBCH block not associated with a PDCCH that includes scheduling information for the RMSI regarding the GSCN-Current.

[0314] In step 1110, when an SS / PBCH block is not associated with a PDCCH that includes scheduling information for the RMSI regarding the GSCN-Current, the UE determines that the configuration includes at least one of the following: a frequency range in which no other SS / PBCH blocks configured with PDCCHs including scheduling information for the RMSI are transmitted, the frequency range being determined based on the GSCN; or a second frequency location in which other SS / PBCH blocks configured with PDCCHs including scheduling information for the RMSI are transmitted, the GSCN-Current being determined based on the GSCN.

[0315] Figure 12 A flowchart of a method 1200 for a BS according to an embodiment of the present disclosure is shown. Figure 12 The embodiments of method 1200 shown are for illustrative purposes only. Figure 12 This disclosure is not intended to limit the scope to any particular implementation.

[0316] like Figure 12 As shown, method 1200 begins at step 1202. BS is (for example, as...) Figure 1 (See 101-103). In step 1202, the BS generates the synchronization signal and physical broadcast channel (SS / PBCH) block.

[0317] In one embodiment, in step 1202, the SS / PBCH block associated with the PDCCH, which includes scheduling information for the RMSI of the determined GSCN-Current, is indicated by at least one of the following: for the first carrier frequency range, the ssb-SubcarrierOffset field in the content of the PBCH based on values ​​in {0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15} and the ssb-SubcarrierOffset field in the content of the PBCH with a value of 0. Fields; for the first carrier frequency range, the ssb-SubcarrierOffset field in the PBCH content based on values ​​in {0,1,2,3,4,5,6,7} and the ssb-SubcarrierOffset field in the PBCH content with a value of 1. The field; or for the second carrier frequency range, the ssb-SubcarrierOffset field in the contents of the PBCH based on the values ​​in {0,1,2,3,4,5,6,7,8,9,10,11}.

[0318] In one embodiment, in step 1202, SS / PBCH blocks not associated with PDCCHs including scheduling information for the RMSI of the determined GSCN-Current are indicated by at least one of the following: for a first frequency range, the ssb-SubcarrierOffset field in the content of the PBCH based on values ​​in {8,9,10,11,12,13,14,15} and the ssb-SubcarrierOffset field in the content of the PBCH with a value of 1. The field; or for the second frequency range, the ssb-SubcarrierOffset field in the contents of the PBCH based on the values ​​in {12,13,14,15}.

[0319] In such an embodiment, the frequency range in which other SS / PBCH blocks of the PDCCH configured with scheduling information including RMSI are not transmitted is indicated by at least one of the following: for the first carrier frequency range, when the value of the ssb-SubcarrierOffset field in the content of the PBCH is 15 and the content of the PBCH... The values ​​of the fields are 1 for GSCN-Current-pdcch-ConfigSIB1 / 16 to GSCN-Current+pdcch-ConfigSIB1 mod 16; or for the second carrier frequency range, the values ​​of the ssb-SubcarrierOffset field in the PBCH content are 15 for GSCN-Current-pdcch-ConfigSIB1 / 16 to GSCN-Current+pdcch-ConfigSIB1 mod 16.

[0320] In such an embodiment, pdcch-ConfigSIB1 includes an 8-bit length in the content of PBCH.

[0321] In such an embodiment, when pdcch-ConfigSIB1 = 0, the frequency range of other SS / PBCH blocks in which PDCCHs configured with scheduling information including RMSI are not transmitted is given by GSCN-Current.

[0322] In such an embodiment, the second frequency position on which other SS / PBCH blocks configured with scheduling information for RMSI are transmitted in a PDCCH is indicated by at least one of the following: for the first carrier frequency range 1, when the ssb-SubcarrierOffset field in the content of the PBCH is based on a value in {8,9,10} and the content of the PBCH... The value of the field is 1 when GSCN-Current+256*(ssb-SubcarrierOffset-8)+pdcch-ConfigSIB1+1; for the first carrier frequency range 1, when the ssb-SubcarrierOffset field in the PBCH content is based on the value in {11,12,13} and the PBCH content... The value of the field is 1 when GSCN-Current-256*(ssb-SubcarrierOffset-11)-pdcch-ConfigSIB1-1; for the second carrier frequency range, the value of the ssb-SubcarrierOffset field in the PBCH content is 12 when GSCN-Current+pdcch-ConfigSIB1+1; or for the second carrier frequency range, the value of the ssb-SubcarrierOffset field in the PBCH content is 13 when GSCN-Current-pdcch-ConfigSIB1-1.

[0323] In such an embodiment, pdcch-ConfigSIB1 is 8 bits long in the content of PBCH, and the SS / PBCH block is configured with a PDCCH including scheduling information for the determined RMSI of the GSCN-Current. The scheduling information for RMSI is determined based on the SS / PBCH block and the multiplexing mode of the control resource set (CORESET) including the PDCCH. The scheduling information for RMSI includes at least the time-domain resource allocation of the physical downlink shared channel (PDSCH) for RMSI.

[0324] In step 1204, the BS identifies the first frequency position (GSCN-Current) based on a set of predefined synchronization grids determined by the Global Synchronization Channel Number (GSCN) to transmit the SS / PBCH block.

[0325] In step 1206, the BS determines, based on GSCN-Current, at least one of the following configurations: an SS / PBCH block associated with a physical downlink control channel (PDCCH) that includes scheduling information for the residual minimum system information (RMSI) regarding GSCN-Current; or an SS / PBCH block not associated with a PDCCH that includes scheduling information for the RMSI regarding GSCN-Current.

[0326] In step 1208, when an SS / PBCH block is not associated with a PDCCH that includes scheduling information for the RMSI regarding the GSCN-Current, the configuration is determined to include at least one of the following: a frequency range in which no other SS / PBCH blocks configured with PDCCHs including scheduling information for the RMSI are transmitted, the frequency range being determined based on the GSCN; or a second frequency position in which other SS / PBCH blocks configured with PDCCHs including scheduling information for the RMSI are transmitted, the GSCN-Current being determined based on the GSCN.

[0327] In step 1210, the BS identifies the contents of the PBCH included in the SS / PBCH block based on the determined configuration.

[0328] In step 1212, the BS transmits an SS / PBCH block, including the PBCH, to the user equipment (UE) via the downlink channel using GSCN-Current.

[0329] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to include such changes and modifications that fall within the scope of the appended claims.

[0330] Nothing described in this application should be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the patent subject matter is defined solely by the claims. Furthermore, none of the claims are intended to invoke 35 U.SC § 112(f) unless the word “means” is followed by a participle.

Claims

1. A method performed by a terminal in a communication system, the method comprising: Receive the first synchronization signal / physical broadcast channel (SS / PBCH) block from the base station; Based on the subcarrier offset value identified using the first SS / PBCH block, a control resource set CORESET corresponding to the first SS / PBCH block for the Remaining Minimum System Information (RMSI) is identified as nonexistent. and Based on the subcarrier offset value, identify the Global Synchronization Channel Number (GSCN) value of the second SS / PBCH block with the CORESET for the RMSI, or the second SS / PBCH block that does not exist within the GSCN range; Wherein, in the frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the Physical Downlink Control Channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value. Wherein, in the case of FR 1 and the subcarrier offset value corresponding to 31, the second SS / PBCH block does not exist within the GSCN range.

2. The method according to claim 1, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 24, the PDCCH information will indicate 1 to 256 as the GSCN offset. Wherein, when the subcarrier offset value corresponds to 25, the PDCCH information indicates 257 to 512 as the GSCN offset. Specifically, when the subcarrier offset value corresponds to 26, the PDCCH information will indicate GSCN offsets from 513 to 768. Wherein, if the subcarrier offset value corresponds to 27, the PDCCH information will indicate GSCN offset as -1 to -256. Wherein, when the subcarrier offset value corresponds to 28, the PDCCH information will indicate GSCN offset as -257 to -512, and Wherein, when the subcarrier offset value corresponds to 29, the PDCCH information will indicate GSCN offset as -513 to -768.

3. The method according to claim 1, in, The PDCCH information is 8 bits, and Wherein, when the subcarrier offset value corresponds to 31, the GSCN range is identified based on the GSCN value of the first SS / PBCH block, and the value associated with the GSCN range is indicated by the PDCCH information.

4. The method according to claim 1, in, In the case of FR 2 and the subcarrier offset corresponding to 12 or 13, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -256 to 256 according to the subcarrier offset value. Wherein, in the case of the values ​​of FR 2 and the subcarrier offset corresponding to 15, the second SS / PBCH block does not exist within the GSCN range.

5. The method of claim 4, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 12, the PDCCH information indicates 1 to 256 as the GSCN offset, and Wherein, when the subcarrier offset value corresponds to 13, the PDCCH information will indicate GSCN offset as -1 to -257.

6. A method performed by a base station in a communication system, the method comprising: Send the first synchronization signal / physical broadcast channel SS / PBCH block; In the case where, based on the subcarrier offset value included in the first SS / PBCH block, it is identified that there is no control resource set CORESET corresponding to the first SS / PBCH block for the Remaining Minimum System Information (RMSI), the Global Synchronization Channel Number (GSCN) value of the second SS / PBCH block having the CORESET for the RMSI or the second SS / PBCH block not existing within the GSCN range is identified based on the subcarrier offset value. Wherein, in the frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the Physical Downlink Control Channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value. Wherein, in the case of FR 1 and the subcarrier offset value corresponding to 31, the second SS / PBCH block does not exist within the GSCN range.

7. The method according to claim 6, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 24, the PDCCH information will indicate 1 to 256 as the GSCN offset. Wherein, when the subcarrier offset value corresponds to 25, the PDCCH information indicates 257 to 512 as the GSCN offset. Specifically, when the subcarrier offset value corresponds to 26, the PDCCH information will indicate GSCN offsets from 513 to 768. Wherein, if the subcarrier offset value corresponds to 27, the PDCCH information will indicate GSCN offset as -1 to -256. Wherein, when the subcarrier offset value corresponds to 28, the PDCCH information will indicate GSCN offset as -257 to -512, and Wherein, when the subcarrier offset value corresponds to 29, the PDCCH information will indicate GSCN offset as -513 to -768.

8. The method according to claim 6, in, The PDCCH information is 8 bits, and Wherein, when the subcarrier offset value corresponds to 31, the GSCN range is identified based on the GSCN value of the first SS / PBCH block, and the value associated with the GSCN range is indicated by the PDCCH information.

9. The method according to claim 6, in, In the case of FR 2 and the subcarrier offset corresponding to 12 or 13, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -256 to 256 according to the subcarrier offset value. Wherein, in the case of the values ​​of FR 2 and the subcarrier offset corresponding to 15, the second SS / PBCH block does not exist within the GSCN range.

10. The method according to claim 9, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 12, the PDCCH information indicates 1 to 256 as the GSCN offset, and Wherein, when the subcarrier offset value corresponds to 13, the PDCCH information will indicate GSCN offset as -1 to -257.

11. A terminal in a communication system, the terminal comprising: transceiver; as well as The controller, coupled to the transceiver and configured to: Receive the first synchronization signal / physical broadcast channel (SS / PBCH) block from the base station; Based on the subcarrier offset value identified using the first SS / PBCH block, a control resource set CORESET corresponding to the first SS / PBCH block for the Remaining Minimum System Information (RMSI) is identified as nonexistent. and Based on the subcarrier offset value, identify the Global Synchronization Channel Number (GSCN) value of the second SS / PBCH block with the CORESET for the RMSI, or the second SS / PBCH block that does not exist within the GSCN range; Wherein, in the frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the Physical Downlink Control Channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value, and Wherein, in the case of FR 1 and the subcarrier offset value corresponding to 31, the second SS / PBCH block does not exist within the GSCN range.

12. The terminal according to claim 11, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 24, the PDCCH information will indicate 1 to 256 as the GSCN offset. Wherein, when the subcarrier offset value corresponds to 25, the PDCCH information indicates 257 to 512 as the GSCN offset. Specifically, when the subcarrier offset value corresponds to 26, the PDCCH information will indicate GSCN offsets from 513 to 768. Wherein, if the subcarrier offset value corresponds to 27, the PDCCH information will indicate GSCN offset as -1 to -256. Wherein, when the subcarrier offset value corresponds to 28, the PDCCH information will indicate GSCN offset as -257 to -512, and Wherein, when the subcarrier offset value corresponds to 29, the PDCCH information will indicate GSCN offset as -513 to -768.

13. The terminal according to claim 11, in, The PDCCH information is 8 bits, and Wherein, when the subcarrier offset value corresponds to 31, the GSCN range is identified based on the GSCN value of the first SS / PBCH block, and the value associated with the GSCN range is indicated by the PDCCH information.

14. The terminal according to claim 11, in, In the case of FR 2 and the subcarrier offset corresponding to 12 or 13, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -256 to 256 according to the subcarrier offset value. Wherein, in the case of the values ​​of FR 2 and the subcarrier offset corresponding to 15, the second SS / PBCH block does not exist within the GSCN range.

15. The terminal according to claim 14, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 12, the PDCCH information indicates 1 to 256 as the GSCN offset, and Wherein, when the subcarrier offset value corresponds to 13, the PDCCH information will indicate GSCN offset as -1 to -257.

16. A base station in a communication system, the base station comprising: transceiver; as well as The controller, coupled to the transceiver and configured to: Send the first synchronization signal / physical broadcast channel SS / PBCH block; In the case where, based on the subcarrier offset value included in the first SS / PBCH block, it is identified that there is no control resource set CORESET corresponding to the first SS / PBCH block for the Remaining Minimum System Information (RMSI), the Global Synchronization Channel Number (GSCN) value of the second SS / PBCH block having the CORESET for the RMSI or the second SS / PBCH block not existing within the GSCN range is identified based on the subcarrier offset value. Wherein, in the frequency range FR 1 and the subcarrier offset value corresponds to one of 24 to 29, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the Physical Downlink Control Channel (PDCCH) information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -768 to 768 according to the subcarrier offset value, and Wherein, in the case of FR 1 and the subcarrier offset value corresponding to 31, the second SS / PBCH block does not exist within the GSCN range.

17. The base station according to claim 16, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 24, the PDCCH information will indicate 1 to 256 as the GSCN offset. Wherein, when the subcarrier offset value corresponds to 25, the PDCCH information indicates 257 to 512 as the GSCN offset. Specifically, when the subcarrier offset value corresponds to 26, the PDCCH information will indicate GSCN offsets from 513 to 768. Wherein, if the subcarrier offset value corresponds to 27, the PDCCH information will indicate GSCN offset as -1 to -256. Wherein, when the subcarrier offset value corresponds to 28, the PDCCH information will indicate GSCN offset as -257 to -512, and Wherein, when the subcarrier offset value corresponds to 29, the PDCCH information will indicate GSCN offset as -513 to -768.

18. The base station according to claim 16, in, The PDCCH information is 8 bits, and Wherein, when the subcarrier offset value corresponds to 31, the GSCN range is identified based on the GSCN value of the first SS / PBCH block, and the value associated with the GSCN range is indicated by the PDCCH information.

19. The base station according to claim 16, in, In the case of FR 2 and the subcarrier offset corresponding to 12 or 13, the GSCN value of the second SS / PBCH block is indicated by the GSCN value of the first SS / PBCH block and the PDCCH information included in the first SS / PBCH block, and the PDCCH information indicates different GSCN offset values ​​from -256 to 256 according to the subcarrier offset value. Wherein, in the case of the values ​​of FR 2 and the subcarrier offset corresponding to 15, the second SS / PBCH block does not exist within the GSCN range.

20. The base station according to claim 19, in, The PDCCH information is 8 bits. Wherein, when the subcarrier offset value corresponds to 12, the PDCCH information indicates 1 to 256 as the GSCN offset, and Wherein, when the subcarrier offset value corresponds to 13, the PDCCH information will indicate GSCN offset as -1 to -257.

Images