Channel grid and synchronization signal grid for NR unlicensed spectrum

Abstract

Disclosed herein are systems and methods for determining a channel grid and synchronization signal grid for a New Radio (NR) unlicensed spectrum. For each of a plurality of data objects, an NR channel grid position is determined using an absolute radio frequency channel number (NR‑ARFCN). For each corresponding NR channel, a global synchronization channel number (GSCN), a number of physical resource blocks (PRBs) based on a channel subcarrier spacing (SCS), an NR channel grid position arrangement, channel edges, synchronization signal and physical broadcast channel (SSB) edges, and an SSB grid position are calculated. The plurality of data objects may then be down-selected based on, for example, corresponding long term evolution (LTE) channel grid positions and / or entries of a second plurality of data objects calculated for NR channels using a second SCS.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 847,770, filed on May 14, 2019, entitled “CHANNEL RASTER AND SYNCHRONIZATION SIGNAL RASTER FOR NR UNLICENSED SPECTRUM,” which is hereby incorporated by reference in its entirety. Technical Field

[0003] The present application relates generally to wireless communication systems, and more particularly to channel grids and synchronization signal grids for new radio unlicensed spectrum. Background Art

[0004] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is generally referred to by industry organizations as Worldwide Interoperability for Microwave Access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to by industry organizations as Wi-Fi. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0005] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0006] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency Range 1 (FR1) includes frequency bands below 6 GHz, some of which may be used by previous standards but can potentially be expanded to cover potential new spectrum products from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) includes frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 have a shorter range but higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0008] Figure 1 A diagram is shown of two adjacent New Radio (NR) cells operating with 15 kHz subcarrier spacing (SCS), the two cells being arranged in the center of a 20 MHz frequency band.

[0009] Figure 2 A diagram is shown of two adjacent New Radio (NR) cells operating with 30 kHz subcarrier spacing (SCS), the two cells being arranged in the center of a 20 MHz frequency band.

[0010] Figure 3 A diagram of a pair of New Radio (NR) channels having channel grid positions and synchronization signal and physical broadcast channel (SSB) grid positions calculated using the methods disclosed herein is shown.

[0011] Figure 4 A method of determining characteristics of a New Radio (NR) channel according to embodiments disclosed herein is shown.

[0012] Figure 5 An exemplary service-oriented architecture according to certain embodiments is shown.

[0013] Figure 6 A UE according to one embodiment is shown.

[0014] Figure 7 A network node according to one embodiment is shown.

[0015] Figure 8 Components according to one embodiment are shown. DETAILED DESCRIPTION

[0016] The following specific embodiments relate to the accompanying drawings. The same figure numbers may be used to identify the same or similar elements in different drawings. In the following description, for the purpose of illustration and not limitation, specific details, such as specific structures, architectures, interfaces, technologies, etc., are set forth to provide a thorough understanding of various aspects of various embodiments. However, it will be apparent to those skilled in the art who benefit from the present disclosure that various aspects of various embodiments may be practiced in other examples that deviate from these specific details. In some cases, descriptions of well-known devices, circuits, and methods are omitted so that the description of various embodiments will not be obscured by unnecessary details. For the purposes of this document, the phrase "A or B" refers to (A), (B), or (A and B).

[0017] The LTE channel grid is the center frequency locations where the wireless system can deploy cells. These locations are the center frequencies of the carrier and may correspond to the DC subcarrier of the cell. In the unlicensed band, the LTE channel grid is in units of non-overlapping 20 MHz, where two non-overlapping 20 MHz are usually adjacent to each other (without any frequency gap in between). More specifically, the LTE channel grid is on {5160, 5180, 5200, 5220, 5240, 5260, 5280, 5300, 5320, 5340} MHz for UNII-1 band, {5480, 5500, 5520, 5540, 5560, 5580, 5600, 5620, 5640, 5660, 5680, 5700, 5720} MHz for UNII-2 band, and on {5745, 5765, 5785, 5805, 5825, 5845, 5865, 5885, 5905} MHz for UNII-3 band.

[0018] The radio frequency (RF) reference frequency is specified by an NR absolute radio frequency channel number (NR-ARFCN) in the range [0…3279165] on the global frequency grid (i.e., the NR channel grid). The NR-ARFCN is associated with the RF reference frequency F in MHz. REFThe relationship between is given by the following formula, where F REF-Offs and N REF-Offs Given in the following table, and N REF For NR-ARFCN:

[0019] F REF =F REF-Offs +ΔF Global (N REF –N REF-Offs )

[0020] Table 1. NR-ARFCN parameters for the global frequency grid

[0021]

[0022]

[0023] The channel grid defines a subset of RF reference frequencies that can be used to identify RF channel locations in uplink and downlink. The RF reference frequencies for RF channels are mapped to resource elements on the carrier. The mapping between RF reference frequencies on the channel grid and corresponding resource elements is given in Table 2 and can be used to identify RF channel locations.

[0024] Table 2: Mapping of channel grid to resource elements

[0025]

[0026] The mapping depends on the total number of resource blocks (RBs) allocated in the channel and is applicable to both uplink (UL) and downlink (DL). The mapping must be applicable to at least one parameter set supported by the base station (BS). In addition, k is the subcarrier index (or resource element index in the frequency domain), n is the subcarrier index (or resource element index in the frequency domain), and n is the subcarrier index (or resource element index in the frequency domain). PRB is the physical resource block (PRB) index, and N RB (Also denoted as N_RB or N RB ) is the number of PRBs in the cell.

[0027] The synchronization raster indicates the frequency locations of synchronization blocks that the UE can use for system acquisition when explicit signaling of the synchronization block locations is not present. The global synchronization raster is defined for all frequencies. The frequency locations of synchronization signal (SS) blocks are defined as SS blocks with corresponding global synchronization channel numbers (GSCN). REF . SS is defined for all frequency ranges REF The parameters of GSCN are shown in Table 3. The synchronization grid and subcarrier spacing of the synchronization block are defined separately for each frequency band.

[0028] Table 3: GSCN parameters for the global frequency grid

[0029]

[0030]

[0031] The mapping between the synchronization raster and the corresponding resource elements of the SS block is given in Table 4. This mapping depends on the total number of RBs allocated in the channel and is applicable to both UL and DL.

[0032] Table 4: Mapping of synchronization grid to SS block resource elements

[0033] Resource element index k of SS block 0 <![CDATA[The number of physical resource blocks n of the SS block PRB > <![CDATA[n PRB =10]]>

[0034] Due to the limited granularity of the NR channel grid frequency positions, it is not possible to completely align them with the LTE channel grid for the same unlicensed band without modification. However, due to the coexistence between Wi-Fi systems and LTE unlicensed systems that may operate in the same band, the NR unlicensed system may find it beneficial to use similar (if not identical) channel grid entries.

[0035] The NR channel grid positions for unlicensed bands can be changed so that they are identical to the LTE channel grid positions. However, in such deployments (with the same LTE channel grid positions) due to the guard bands required by the NR cells, two adjacent cells cannot be arranged on the same subcarrier grid nor on the same PRB grid. This is Figure 1 and Figure 2 This is obvious from the diagram. Figure 1 A diagram 100 is shown of two adjacent NR cells operating with 15 kHz subcarrier spacing, the two cells being arranged in the center of a 20 MHz frequency band. In this case, the gap between the two occupied frequencies cannot be divided by the 15 kHz subcarrier spacing being operated.

[0036] A similar situation is shown in Figure 2 middle. Figure 2 A diagram 200 is shown of two adjacent NR cells operating with 30kHz subcarrier spacing, arranged at the center of a 20MHz frequency band. In this case, the subcarrier grid (which is a regular pattern and period of the centers of the subcarrier positions) between the two cells will not align, and therefore, the transceiver may not be able to perform a single inverse FFT and FFT operation to process the signals from both cells simultaneously. (It should be noted that in Figure 1 and Figure 2In NR, the "center" of the 20MHz band does not necessarily mean exactly in the center so as to have the same guard bandwidth at either edge of the bandwidth. Due to the fact that there is always an even number of subcarriers, the center of the NR carrier will be offset by 1 / 2 subcarrier. Therefore, in order to position the channel grid position at the center of a subcarrier, the overall bandwidth will be offset by 1 / 2 subcarrier. )

[0037] Therefore, the selection of NR channel grid location becomes an important factor to allow supporting subcarrier and PRB grid alignment in order to achieve efficient transceiver design for multiple component carrier operation (i.e., multiple cell operation).

[0038] In addition, the process of selecting the NR channel grid position also needs to take into account the synchronization signal and physical broadcast channel (referred to herein as SSB and / or SS blocks) grid entries (also referred to herein as SSB grid entries, SSB grid positions, SSB grid values, SSB grid points and / or SS grids). The SSB grid entry is the center of the SSB that needs to be located within the cell. The subcarrier grid of the SSB also needs to be aligned with the subcarrier grid of the rest of the cell to ensure orthogonal transmission of the SSB and the rest of the system when the same subcarrier spacing is used for both the SSB and the rest of the system. Therefore, the combination of the SSB grid position and the NR channel grid position should be selected so that the operating cell fits within the 20MHz LTE channel (to achieve effective coexistence), allows alignment of subcarriers and PRB grids between cells, and allows alignment of subcarriers (and possible PRB grids) between the SSB and the cell's signals and the rest of the channel.

[0039] This process is not trivial and requires a significant amount of engineering work. The present disclosure addresses the problem of how NR channels and SSB grid entries may be selected, and proposes channels and SSB grid entries that provide many benefits to transceiver design.

[0040] There is no known solution that addresses PRB grid alignment between cells, PRB grid alignment between SSBs and the rest of the signal / channel of a cell, and alignment of 20 MHz channel deployments between LTE, NR, and Wi-Fi systems.

[0041] The proposed NR channel and SSB grid entries will allow the deployment of cells in carrier aggregation using a single FFT (and inverse FFT) in the transceiver. In addition, by also supporting PRB grid alignment between cells and between SSBs and the rest of the signal in the channel, it will allow efficient use of spectrum and even further simplify the transceiver implementation.

[0042] The NR channel grid is given as F REF =F REF-Offs +ΔFGlobal (N REF –N REF-Offs ), where ΔF Global =15kHz, F REF-Offs =3000MHz, and N REF-Offs =600000.

[0043] N for a system operating at 30kHz REF Selected from the set {744000,745344,746664,748008,749328,750672,751992,753336,754656,754668,754680,756000,765336,766656,766668,766680,768000,769344,7 70664,772008,773328,774672,775992,777336,778656,778668,778680,780000,781344,783000,784344,785664,787008,788328,789672,790992,792336,7 93656,793668,793680,744660,746004,747324,748668,749988,750000,750012,751332,752676,753996,755340,765996,767340,768660,770004,771324,7 72668,773988,774000,774012,775332,776676,777996,779340,780660,783660,785004,786324,787668,788988,789000,789012,790332,791676,792996}.

[0044] N for a system operating at 15kHz REFSelected from the set {744000,744006,745344,746664,746670,748008,749328,749334,750672,751992,51998,753336,754656,754662,756000,756006,765336,766656,766662,768000,768006,69344,770664,770670,772008,7 73328,773334,774672,775992,775998,777336,78656,778662,780000,780006,781344,783000,783006,784344,785664,785670,787008,788328,788334,789672,790992,790998,792336,793656,793662,744660 ,744666,746004,747324,47330,748668,749988,749994,750000,750012,751332,751338,752676,753996,754002,755340,765996,766002,767340,768660,768666,770004,771324,771330,772668,773988,7739 94,774000,774012,775332,775338,776676,777996,778002,779340,780660,780666,783660,783666,785004,786324,786330,787668,788988,788994,789000,789012,790332,790338,791676,792996,793002}.

[0045] The SSB grid is given by "3000MHz+N*1.44MHz", where N is a value ranging from 0 to 14756, and the GSCN is given by "7499+N". The GSC is chosen to be K+ taken from the set {8996,9010,9023,9037,9051,9065,9079,9093,9107,9121,9218,9232,9232,9232,9246,9260,9273,9287,9301,9315,9329,9343,9357,9357,9357,9371,9 385,9402,9416,9430,9444,9457,9471,9485,9499,9513,9513,9513,8996,9010,9023,9037,9051,9065,9079,9093,9107,9218,9232,9246,9260,9273,9287}, where K = 0…6.

[0046] The present disclosure allows for simplified transceiver implementations that will save power consumption and reduce initial access acquisition (e.g., the time taken to find a suitable cell) latency for NR in unlicensed spectrum.

[0047] Possible channels and SSB grid entries that provide benefits to a transceiver implementation can be calculated as follows:

[0048] Use Formula F REF =F REF-Offs +ΔF Global (N REF –N REF-Offs ) calculates the NR-ARFCN value between 5GHz and 6GHz (unlicensed spectrum).

[0049] Calculate the GSCN value on a 1.44MHz (or multiple of 1.44MHz) grid using the formula 3000MHz+N*1.44MHz, where N=0:14756. Note: NR-ARFCN values ​​are arranged on a 15 / 30 / 60kHz grid. In LTE, channels are arranged on a 100kHz grid. The NR channel center frequency value should be as close as possible to the LTE channel center frequency.

[0050] Based on the subcarrier spacing and channel bandwidth, determine the maximum transmission bandwidth. For this purpose, the following table can be used.

[0051] Table 5: Maximum transmission bandwidth configuration N RB

[0052]

[0053] The following table is used to determine the arrangement of the channel grid based on the number of PRBs.

[0054] Table 6: Mapping of channel grid to resource elements

[0055]

[0056] The edge and occupied channel BW (OCB) of the channel are calculated based on the arrangement of the channel grid.

[0057] The SSB block is 20 PRBs wide and is positioned so that the grid is located on the 0th subcarrier of the 10th PRB. The SS block must be located within the channel. The SSB grid values ​​are located on a 1.44MHz grid and the channel grid points are located on a 15 / 30 / 60kHz grid. The SSB grid points are chosen so that they also coincide with the channel grid grid. The grid points are assumed to be located at the center of the subcarriers.

[0058] The guard band value is calculated from the edge of the channel. The minimum guard band requirement must be met.

[0059] Table 7: Minimum guard band for each UE channel bandwidth and SCS (kHz)

[0060]

[0061] NOTE: The calculation of channel, OCB and guard band must consider 1 subcarrier for the channel raster.

[0062] k SSB (also denoted herein as k_SSB) is the number of subcarriers between the SSB block edge and the channel edge on both sides of the OCB. k is calculated SSB value.

[0063] The number of PRBs in a channel is calculated by subtracting the guard band from the OCB.

[0064] Figure 3 A diagram 300 of a pair of NR channels is shown with channel grid positions and SSB grid positions calculated using the methods disclosed herein. Figure 3 The NR channels may correspond to calculations performed using the process just described.

[0065] The steps listed above generate all possible channel raster and SSB raster entries that meet the following four criteria:

[0066] First, the SS block must be located within the occupied channel bandwidth.

[0067] Second, the PRBs in the SS blocks and channels must be aligned on the same grid (so that k SSB =0).

[0068] Third, PRBs in cells located in different channels must be aligned on the same PRB grid. This can be checked by ensuring that the frequency difference between the first subcarriers occupying the channel bandwidth in different cells is an integer multiple of the single PRB bandwidth.

[0069] Fourth, the minimum guard band requirement must be met.

[0070] Conditions for selecting entries down through all possible channel raster and SSB raster entries

[0071] The possible channel grid and SSB grid entries that can be calculated (e.g., as discussed above) can be further down-selected. Additional down-selection allows a single NR channel entry per 20 MHz to be supported, which can significantly simplify the initial access process and delays involved in searching for a valid SSB.

[0072] For the 30kHz data subcarrier spacing case, select an NR channel grid entry point that allows support for at least 50 PRBs within the 20MHz LTE channel band and at least 105 PRBs within the 40MHz channel band. For the 15kHz data subcarrier spacing case, select an NR channel grid entry point that allows support for at least 104 PRBs within the 20MHz LTE channel band and at least 214 PRBs within the 40MHz channel band. Whether a certain number of PRBs can be used for the NR channel grid entry point can be determined by calculating the available guard bands on the left and right sides of the occupied system bandwidth. The calculated guard band must be greater than the minimum guard band requirements specified in TS38.101-1 and TS38.104.

[0073] Additionally, NR channel grid entry points are selected that allow alignment of the PRB grid between different component carriers. This can be performed by selecting NR channel grid entry points with a specific number of PRBs that have an integer multiple of 12x30kHz difference between the first subcarriers that occupy the system bandwidth. This can also be performed by selecting NR channel grid entry points with an integer multiple of 12×2 N REF The channel grid entry point of the value to execute.

[0074] In addition, the NR channel grid entry points are selected that allow PRB grid alignment between the SSB PRBs and the common PRB grid. This is equivalent to finding the NR channel grid entry points that allow k SSB Grid entry point with parameter equal to 0.

[0075] If an NR channel grid entry point is selected with a specific number of PRBs, where the remainder of these PRBs when divided by 12x30kHz at the first carrier frequency position of the occupied system bandwidth is 120kHz (or, equivalently, N REFThe remainder after division by 12x2 is 0), the conditions regarding alignment of PRB grids between different component carriers and alignment of PRB grids between SSB PRBs and a common PRB grid can be satisfied simultaneously.

[0076] Finally, a set of SSB grid entry points (range of GSCN values) is found that allows the SSBs to be placed within the occupied system bandwidth when paired with a selected NR channel grid entry point with a specific number of PRBs.

[0077] Select Process Flow Down

[0078] Use the following criteria and / or alternatives to select entries from among all available channel and SSB grid entries:

[0079] First, the PRBs of the channel and SS blocks must be aligned on the same grid. This requirement is met if the OCB start position has the same remainder value when divided by "subcarrier spacing * 12".

[0080] If the first condition is met, the channel grid points can be further selected downward to ensure that k SSB = 0. Then there are two alternatives regarding the number of PRBs: 1) ensure that all channels have the same number of PRBs, or 2) select the maximum number of available PRBs based on the SCS. If option 1 is selected, the PRBs of 15kHz and 30kHz channel spacing are aligned by using the same channel grid points for 20MHz and 40MHz channel bandwidths.

[0081] Figure 4 A method 400 of determining characteristics of an NR channel according to embodiments disclosed herein is shown. The method 400 includes calculating an ARFCN value and a GSCN value in block 402.

[0082] The method 400 also includes, at block 404, selecting a number of PRBs based on the SCS.

[0083] The method 400 also includes determining whether the number of PRBs mod 2 is equal to zero (in other words, whether the number of PRBs is an even number) in decision block 406. If so, the method continues in block 408 to determine that the NR channel grid position is located at the element of the PRB with index k=0. If not, the method continues in block 424 to determine that the NR channel grid position is located at the element of the PRB with index k=6.

[0084] The method 400 also includes, in block 410, calculating the NR channel edge and the OCB edge based on the NR channel center frequency and the NR channel grid arrangement.

[0085] The method 400 also includes calculating the SS block edge in block 412 to ensure that it is within the NR channel.

[0086] The method 400 also includes ensuring, in block 414 , that a minimum guard band is available on both edges of the OCB.

[0087] The method 400 also includes checking in block 416 whether mod(OCB start position, SCS*12)=X to ensure that the PRBs of the OCBs of different NR channels are aligned to the PBR grid.

[0088] The method 400 also includes checking whether k_SSB=0 in block 418 .

[0089] Method 400 may also include one of block 420 and block 422. In block 420, each channel may select a maximum number of PRBs. This may result in maximum spectral efficiency. In block 422, each NR channel selects the same number of PRBs. This may result in alignment of the 15 kHz and 30 kHz PRBs by using the same NR channel grid points (20 MHz and 40 MHz).

[0090] Example channel grid and SSB grid entry set for 30kHz

[0091] Table 8 and Table 9 are an example of 30kHz channel and SSB grid entries.

[0092] The "LTE Channel Raster [kHz]" column contains the relevant channel raster entries for LTE, and the "BW" column specifies the channel bandwidths to which the channel raster entry applies. For an entry of 20 / 60 / 100, this means that the entry applies to 20 MHz, 60 MHz, and 100 MHz. For an entry of 40 / 80, this means that the entry applies to 40 MHz and 80 MHz. The "NR Channel Raster" and "NR-ARFCN" columns provide the NR channel raster frequency positions and their corresponding N REF value. The "N_PRB" column shows the number of PRBs available for the channel. The "SS Grid" column and the "GSCN" column show an exemplary location of the SSB frequency position and its corresponding GSCN value. It should be noted that any GSCN value between the value specified by the minimum GSCN and the value specified by the maximum GSCN can be used for the NR channel grid entry (row). It should also be noted that if GSCN (minimum GSCN + K) is used for one of the NR channel grid entries, the same K value should be used for all channel grid entries specified in the table.

[0093] Table 8

[0094]

[0095]

[0096]

[0097] The "k_SSB" column provides the k_SSB parameter for the selected SSB grid entry and NR channel grid entry combination. The "RB Offset (Left)" column and the "RB Offset (Right)" column provide the number of PRBs available to the left and right of the SSB. With 3 PB offsets on the left and 27 RB offsets on the right, this means that within the occupied channel bandwidth, there are 3 lower frequency PRBs, followed by SSBs (which are 20 PRBs), followed by 27 higher frequency PRBs. In this case, the "Occupied Channel Start Point" column and the "Occupied Channel End Point" column represent the center frequencies of the first subcarrier (i.e., the lowest frequency subcarrier) and the last subcarrier (i.e., the highest frequency subcarrier) of the occupied channel bandwidth, respectively.

[0098] The "Left Guard" and "Right Guard" columns represent the remaining guard bands outside the occupied channel bandwidth. The "SSB Start Point" and "SSB End Point" columns represent the center frequencies of the first subcarrier (i.e., the subcarrier with the lowest frequency) and the last subcarrier (i.e., the subcarrier with the highest frequency) of the SSB, respectively.

[0099] Table 9

[0100]

[0101]

[0102]

[0103] Example channel grid and SSB grid entry set for 15kHz

[0104] Table 10 and Table 11 are an example of a 15kHz channel and SSB grid entry.

[0105] Table 10

[0106]

[0107]

[0108]

[0109] Table 11

[0110]

[0111]

[0112]

[0113]

[0114] Example channel grid and SSB grid entry set for 30kHz and 15kHz, where each LTE 20MHz channel has 1 unique channel grid entry

[0115] In the exemplary channel grids and SSB grid entries shown in Tables 8, 9, 10, and 11, there may be multiple entries corresponding to the same LTE channel grid. To avoid additional channel grid entries, further down selection may be performed to select NR channel grid entries that support only 50 PRBs and only 1 NR channel entry per LTE channel grid entry for 20 MHz channels, and select NR channel grid entries that support only 104 PRBs or 106 PRBs for 40 MHz channels.

[0116] Table 12 shows the NR channel grid entries applicable for both 30kHz data subcarrier operations.

[0117] Table 12

[0118]

[0119]

[0120]

[0121] Example channel grid and SSB grid entry set for 30kHz and 15kHz, where each LTE 20MHz channel has 1 unique channel grid entry, which results in the same channel grid entry between 30kHz and 15kHz

[0122] In the exemplary channel grids and SSB grid entries shown in Tables 8, 9, 10, and 11, there may be multiple entries corresponding to the same LTE channel grid. To avoid additional channel grid entries, further down selection may be performed to select an NR channel grid entry that supports only 50 PRBs and only 1 NR channel entry per LTE channel grid entry for a 20 MHz channel, and an NR channel grid entry that supports only 104 PRBs or 106 PRBs for a 40 MHz channel. In addition, an NR channel grid entry common to both 15 kHz and 30 kHz may be selected.

[0123] Tables 13 and 14 show NR channel grid entries applicable to both 30kHz and 15KHz data subcarrier operations. This compresses the total number of channel entries on all data subcarriers. The NR channel grid entries of Tables 13 and 14 should be the same. However, the supported GSCN range may be slightly different for each channel grid entry. In order to support both 30kHz and 15kHz, a GSCN should be selected so that the same GSCN can support both 30kHz and 15kHz data subcarrier operations.

[0124] Table 13

[0125]

[0126]

[0127]

[0128]

[0129] Table 14

[0130]

[0131] Example channel grid and SSB grid entry set for 30kHz and 15kHz, where each LTE 20MHz channel has 1 unique channel grid entry, which maximizes the number of supported PRBs

[0132] The exemplary channel grid and SSB grid entries shown in Tables 8 to 14 provide channel grid entries with a uniform number of PRBs that are supported in the channel. Additional system capacity can be squeezed out of certain NR channel grid points by utilizing more PRBs that still meet all of the above conditions (e.g., minimum guard band, PRB grid alignment, PRB and SSB PRB grid alignment, etc.).

[0133] Therefore, a downward selection is performed to select the NR channel raster entry that supports the maximum number of PRBs for 20MHz and only selects 1 NR channel entry per LTE channel raster entry. This is shown in Tables 15 and 16. This may result in slightly different NR channel raster entries for the 30kHz and 15kHz data subcarrier cases.

[0134] Table 15

[0135]

[0136]

[0137] Table 16

[0138]

[0139]

[0140] Exemplary System Architecture

[0141] In certain embodiments, the 5G system architecture supports data connectivity and services, enabling deployment to use technologies such as network function virtualization and software defined networks. The 5G system architecture can utilize service-based interactions between control plane network functions. Separating user plane functions from control plane functions allows independent scalability, evolution, and flexible deployment (e.g., centralized locations or distributed (remote) locations). Modular function design allows functional reuse, and flexible and effective network slicing can be achieved. Network functions and their network function services can interact with another NF and its network function services directly or indirectly via a service communication agent. Another intermediate function can help route control plane messages. The architecture minimizes the dependency between AN and CN. The architecture may include an aggregated core network with a public AN-CN interface that integrates different access types (e.g., 3GPP access and non-3GPP access). The architecture may also support a unified authentication framework, stateless NFs with decoupling of computing resources from storage resources, capability exposure, concurrent access to local and centralized services (to support low-latency services and access to local data networks, user plane functions may be deployed near the AN), and / or roaming in the visited PLMN with both home-routed traffic as well as local breakout traffic.

[0142] The 5G architecture may be defined as service-based, and the interactions between network functions may include a service-based representation, where a network function (e.g., AMF) within the control plane enables other authorized network functions to access its services. The service-based representation may also include a point-to-point reference point. The reference point representation may also be used to show the interactions between NF services in a network function described by a point-to-point reference point (e.g., N11) between any two network functions (e.g., AMF and SMF).

[0143] Figure 5 A service-oriented architecture 500 in 5GS according to one embodiment is shown. As described in 3GPP TS 23.501, the service-oriented architecture 500 includes NFs such as NSSF 502, NEF 504, NRF 506, PCF 508, UDM 510, AUSF 512, AMF 514, and SMF 516 to communicate with UE 520, (R)AN 522, UPF 524, and DN 526. NFs and NF services can communicate directly (referred to as direct communication) or indirectly via SCP 518 (referred to as indirect communication). Figure 5Also shown are corresponding service interfaces including Nutm, Naf, Nudm, Npcf, Nsmf, Nnrf, Namf, Nnef, Nnssf and Nausf and reference points N1, N2, N3, N4 and N6. Figure 5 Some exemplary functions provided by the NF shown.

[0144] The NSSF 502 supports functions such as: selecting a set of network slice instances to serve the UE; determining the allowed NSSAIs and, if necessary, determining the mapping to the subscribed S-NSSAI; determining the configured NSSAI and, if necessary, determining the mapping to the subscribed S-NSSAI; and / or determining the set of AMFs to be used to serve the UE, or determining a list of candidate AMFs based on the configuration, possibly by querying the NRF.

[0145] NEF 504 supports the exposure of capabilities and events. NF capabilities and events can be securely exposed by NEF 504 (e.g., for third parties, application functions and / or edge computing). NEF 504 can store / retrieve information as structured data using a standardized interface (Nudr) to UDR. NEF 504 can also securely provide information to the 3GPP network from external applications, and can provide application functions to securely provide information (e.g., expected UE behavior, 5GLAN group information, and service-specific information) to the 3GPP network, where NEF 504 can authenticate and authorize and help limit application functions. NEF 504 can provide internal-external information conversion by converting between information exchanged with AF and information exchanged with internal network functions. For example, NEF 504 converts between AF service identifiers and internal 5G core information (such as DNN and S-NSSAI). NEF 504 can handle the masking of network and user sensitive information of external AF according to network policy. NEF 504 may receive information from other network functions (based on the exposed capabilities of other network functions) and store the received information as structured data using a standardized interface to UDR. The stored information may then be accessed by NEF 504 and re-exposed to other network functions and application functions, and used for other purposes such as analysis. For external exposure of services related to a specific UE, NEF 504 may reside in the HPLMN. Depending on the operator agreement, the NEF 504 in the HPLMN may have an interface with the NF in the VPLMN. SCEF+NEF may be used for service exposure when the UE is able to switch between EPC and 5GC.

[0146] The NRF 506 supports the service discovery function by receiving NF discovery requests from NF instances or SCPs and providing information of the discovered NF instances to the NF instances or SCPs. The NRF 506 may also support P-CSCF discovery (a special case of SMF discovery of AFs), maintain NF profiles of available NF instances and their supported services, and / or notify subscribed NF service consumers or SCPs of newly registered / updated / deregistered NF instances together with their NF services. In the context of network slicing, based on the network specific implementation, multiple NRFs may be deployed at different levels, such as PLMN level (NRF configured with information of the entire PLMN), shared slice level (NRF configured with information belonging to a network slice set), and / or slice specific level (NRF configured with information belonging to S-NSSAI). In the context of roaming, multiple NRFs may be deployed in different networks, wherein the NRF in the visited PLMN (referred to as vNRF) is configured with information of the visited PLMN, and wherein the NRF in the home PLMN (referred to as hNRF) is configured with information of the home PLMN, referenced by the vNRF via the N27 interface.

[0147] The PCF 508 supports a unified policy framework to govern network behavior. The PCF 508 provides policy rules for control plane functions to implement them. The PCF 508 accesses subscription information related to policy decisions in a unified data repository (UDR). The PCF 508 can access a UDR located in the same PLMN as the PCF.

[0148] The UDM 510 supports the generation of 3GPP AKA authentication credentials, user identification processing (e.g., storage and management of SUPI for each subscriber in the 5G system), unhiding of the privacy-preserving subscription identifier (SUCI), access authorization based on subscription data (e.g., roaming restrictions), UE's serving NF registration management (e.g., storing the service AMF for the UE, storing the PDU session storage service SMF for the UE), service / session continuity (e.g., by maintaining the SMF / DNN allocation for ongoing sessions), MT-SMS delivery, lawful interception functions (especially in outbound roaming situations where the UDM is the only contact point for the LI), subscription management, SMS management, 5G LAN group management processing, and / or external parameter configuration (expected UE behavior parameters or network configuration parameters). To provide such functions, the UDM 510 uses subscription data (including authentication data) that can be stored in the UDR, in which case the UDM implements the application logic and may not require internal user data storage, and several different UDMs can serve the same user in different transactions. The UDM 510 can be located in the HPLMN of the subscriber it serves and can access the information of the UDR located in the same PLMN.

[0149] AF 528 interacts with the core network to provide services such as supporting: application impact on traffic routing; access to NEF 504; interaction with the policy framework for policy control; and / or IMS interaction with 5GC. Based on operator deployment, application functions that are considered to be trusted by the operator may be allowed to interact directly with related network functions. Application functions that the operator does not allow direct access to network functions may interact with related network functions using an external exposure framework via NEF 504.

[0150] AUSF 512 supports authentication for 3GPP access and untrusted non-3GPP access. AUSF 512 may also provide support for network slice-specific authentication and authorization.

[0151] AMF 514 supports termination of RAN CP interface (N2), termination of NAS (N1) for NAS encryption and integrity protection, registration management, connection management, reachability management, mobility management, lawful interception (for AMF events and interface to LI system), transmission of SM messages between UE and SMF, transparent proxy for routing SM messages, access authentication, access authorization, transmission of SMS messages between UE and SMSF, SEAF, location service management for regulatory services, transmission of location service messages between UE and LMF and between RAN and LMF, EPS bearer ID allocation for interworking with EPS, UE mobility event notification, control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, configuration of external parameters (expected UE behavior parameters or network configuration parameters) and / or network slice-specific authentication and authorization. Some or all of the AMF functions may be supported in a single instance of AMF 514. Regardless of the number of network functions, in some embodiments, only one NAS interface instance per access network between UE and CN terminates at one of the network functions that implements at least NAS security and mobility management. AMF 514 may also include policy-related functions.

[0152] In addition to the above functions, AMF 514 may also include the following functions to support non-3GPP access networks: support N2 interface with N3IWF / TNGF, on which some information (e.g., 3GPP cell identity) and procedures (e.g., handover related) defined on 3GPP access may not be applicable, and non-3GPP access specific information not applicable to 3GPP access may be applied; support NAS signaling with UE through N3IWF / TNGF, where some procedures supported by NAS signaling through 3GPP access may not be applicable to untrusted non-3GPP (e.g., paging) access; support verification of UE connected through N3IWF / TNGF; management of mobility, authentication and separate security context states of UE connected via non-3GPP access or simultaneously connected via 3GPP access or non-3GPP access; support coordinated RM management context valid on 3GPP access and non-3GPP access; and / or support dedicated CM management context for UE connected via non-3GPP access. It may not be necessary to support all of the above functions in the instance of network slicing.

[0153] SMF 516 supports session management (e.g., session establishment, modification, and release, including tunnel maintenance between UPF and AN nodes), UE IP address allocation and management (including optional authorization) (where the UE IP address can be received from the UPF or from an external data network), DHCPv4 (server and client) and DHCPv6 (server and client) functions, functions for responding to address resolution protocol requests and / or IPv6 neighbor request requests based on local cache information of Ethernet PDUs (e.g., SMF responds to ARP and / or IPv6 neighbor request requests by providing a MAC address corresponding to the IP address sent in the request), selection and control of user plane functions (including controlling the UPF to proxy ARP or IPv6 neighbor discovery or forwarding all ARP / IPv6 neighbor request traffic to the SMF for Ethernet PDU sessions), traffic steering configuration at the UPF to route traffic to the appropriate destination, 5G VN group management (e.g., maintaining the topology of the PSA UPFs involved, in the PSA Establish and publish N19 tunnels between UPFs, configure traffic forwarding at UPF to apply local switching and / or N6-based forwarding or N19-based forwarding), terminate interfaces towards policy control functions, lawful interception (for SM events and interfaces to LI systems), charge data collection and support charging interfaces, control and coordinate charging data collection at UPF, terminate the SM part of NAS messages, downlink data notification, initiator of AN-specific SM information sent to AN via AMF over N2, determination of SSC mode for session, control plane CIoT 5GS optimization, header compression, act as I-SMF in deployments where I-SMF can be inserted / removed / relocated, configure external parameters (expected UE behavior parameters or network configuration parameters), P-CSCF discovery for IMS services, roaming functions (e.g., handle local implementation to apply QoS SLA (VPLMN), charging data collection and charging interface (VPLMN) and / or lawful interception (in VPLMN for SM events and interface to LI system), interaction with external DN to transmit signaling for PDU session authentication / authorization for external DN and / or instructing UPF and NG-RAN to perform redundant transmission on N3 / N9 interface. Some or all of the SMF functions may be supported in a single instance of SMF. However, in some embodiments, not all functions need to be supported in an instance of a network slice. In addition to the functions, SMF 516 may include policy-related functions.

[0154] SCP 518 includes one or more of the following functions: indirect communication; delegated discovery; message forwarding and routing to destination NF / NF service; communication security (e.g., authorization of NF service consumer to access NF service manufacturer API), load balancing, monitoring, overload control, etc.; and / or optionally interacting with UDR to resolve UDM group ID / UDR group ID / AUSF group ID / PCF group ID / CHF group ID / HSS group ID based on UE identity (e.g., SUPI or IMPI / IMPU). Some or all of the SCP functions may be supported in a single instance of SCP. In some embodiments, SCP 518 may be deployed in a distributed manner and / or more than one SCP may be present in the communication path between NF services. SCP may be deployed at PLMN level, shared slice level, and slice-specific level. Operator deployment may be left to ensure that SCP can communicate with relevant NRFs.

[0155] UE 520 may include a device with radio communication capabilities. For example, UE 520 may include a smart phone (e.g., a handheld touch screen mobile computing device that can be connected to one or more cellular networks). UE 520 may also include any mobile or non-mobile computing device, such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handheld device, or any computing device including a wireless communication interface. UE is also referred to as a client, a mobile phone, a mobile device, a mobile terminal, a user terminal, a mobile unit, a mobile station, a mobile user, a subscriber, a user, a remote station, an access agent, a user agent, a receiver, a radio equipment, a reconfigurable radio equipment, or a reconfigurable mobile device. UE 520 may include an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. IoT UE may utilize technology (e.g., M2M, MTC, or mMTC technology) to exchange data with an MTC server or device via a PLMN, other UEs using ProSe or D2D communication, a sensor network, or an IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0156] UE 520 may be configured to be connected or communicatively coupled to (R)AN 522 via a radio interface 530, which may be a physical communication interface or layer configured to operate with a cellular communication protocol such as a GSM protocol, a CDMA network protocol, a push-to-talk (PTT) protocol, a cellular PTT (POC) protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, etc. For example, UE 520 and (R)AN 522 may use a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack including a PHY layer, a MAC layer, an RLC layer, a PDCP layer, and an RRC layer. DL transmissions may be from (R)AN 522 to UE 520, and UL transmissions may be from UE 520 to (R)AN 522. UE 520 may also communicate directly with another UE (not shown) using a side link for D2D, P2P, and / or ProSe communication. For example, the ProSe interface may include one or more logical channels, including but not limited to a physical sidelink control channel (PSCCH), a physical sidelink shared channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0157] (R)AN 522 may include one or more access nodes, which may be referred to as base stations (BS), node Bs, evolved node Bs (eNBs), next generation node Bs (gNBs), RAN nodes, controllers, transmission reception points (TRPs), etc., and may include ground stations (e.g., terrestrial access points) or satellite stations, which provide coverage within a geographic area (e.g., a cell). (R)AN 522 may include one or more RAN nodes for providing macro cells, pico cells, femto cells, or other types of cells. A macro cell may cover a relatively large geographic area (e.g., several thousand meters in radius) and may allow unrestricted access to a UE with a service subscription. A pico cell may cover a relatively small geographic area and may allow unrestricted access to a UE with a service subscription. A femto cell may cover a relatively small geographic area (e.g., a home) and may allow restricted access to a UE associated with the femto cell (e.g., a UE in a closed subscriber group (CSG), a UE of a user in a home, etc.).

[0158] Although not shown, multiple RAN nodes (such as (R)AN 522) may be used, with an Xn interface defined between two or more nodes. In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 520 in connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in connected mode between one or more (R)AN nodes. The mobility support may include context transfer from an old (source) serving (R)AN node to a new (target) serving (R)AN node; and control of a user plane tunnel between an old (source) serving (R)AN node and a new (target) serving (R)AN node.

[0159] UPF 524 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point interconnected with DN 526, and a branch point to support multi-homed PDU sessions. UPF 524 may also perform packet routing and forwarding, packet inspection, user plane portion of policy rule enforcement, lawful interception of packets (UP collection); traffic usage reporting, QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and downlink packet buffering and downlink data notification triggering. UPF 524 may include an uplink classifier for supporting routing of traffic flows to data networks. DN 526 may represent various network operator services, Internet access, or third-party services. DN 526 may include, for example, an application server.

[0160] Figure 6 600 is a block diagram of an exemplary UE 600 that can be configured according to various embodiments of the present disclosure, including by executing instructions corresponding to any exemplary method and / or process described herein on a computer readable medium. The UE 600 includes one or more processors 602, a transceiver 604, a memory 606, a user interface 608, and a control interface 610.

[0161] The one or more processors 602 may include, for example, an application processor, an audio digital signal processor, a central processing unit, and / or one or more baseband processors. Each of the one or more processors 602 may include an internal memory and / or may include an interface for communicating with an external memory (including memory 606). The internal or external memory may store software code, programs, and / or instructions for execution by the one or more processors 602 to configure and / or facilitate UE 600 to perform various operations, including the operations described herein. For example, the execution of the instructions may configure UE 600 to communicate using one or more wired or wireless communication protocols (including one or more wireless communication protocols standardized by 3GPP, such as those commonly referred to as 5G / NR, LTE, LTE-A, UMTS, HSPA, GSM, GPRS, EDGE, etc.) or any other current or future protocol that may be used in conjunction with the one or more transceivers 604, user interface 608, and / or control interface 610. For another example, the one or more processors 602 may execute program code stored in the memory 606 or other memory corresponding to the MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP (e.g., for NR and / or LTE). For another example, the processor 602 may execute program code stored in the memory 606 or other memory, which together with the one or more transceivers 604 implements corresponding PHY layer protocols, such as orthogonal frequency division multiplexing (OFDM), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA).

[0162] The memory 606 may include a memory area for the one or more processors 602 to store variables used in protocols, configurations, controls, and other functions of the UE 600 (including operations corresponding to or including any of the exemplary methods and / or processes described herein). In addition, the memory 606 may include non-volatile memory (e.g., flash memory), volatile memory (e.g., static or dynamic RAM), or a combination thereof. In addition, the memory 606 may interact with a memory slot through which removable memory cards of one or more formats (e.g., SD card, memory stick, compact flash, etc.) may be inserted and removed.

[0163] The one or more transceivers 604 may include radio frequency transmitter and / or receiver circuits that facilitate the UE 600 to communicate with other devices supporting similar wireless communication standards and / or protocols. For example, the one or more transceivers 604 may include switches, mixer circuits, amplifier circuits, filter circuits, and synthesizer circuits. Such RF circuit systems may include a receive signal path having a circuit for down-converting an RF signal received from a front-end module (FEM) and providing a baseband signal to a baseband processor of the one or more processors 602. The RF circuit may also include a transmit signal path, which may include a circuit for up-converting a baseband signal provided by a baseband processor and providing an RF output signal for transmission to the FEM. The FEM may include a receive signal path, which may include a circuit configured to operate on an RF signal received from one or more antennas, amplify the receive signal, and provide an amplified version of the receive signal to the RF circuit for further processing. The FEM may also include a transmit signal path, which may include a circuit configured to amplify a transmit signal provided by the RF circuit for transmission by one or more antennas. In various embodiments, amplification through the transmit or receive signal path may be accomplished in the RF circuitry only, in the FEM only, or in both the RF circuitry and the FEM circuitry. In some embodiments, the FEM circuitry may include a TX / RX switch to switch between transmit mode and receive mode operation.

[0164] In some exemplary embodiments, the one or more transceivers 604 include transmitters and receivers that enable the device 1200 to communicate with various 5G / NR networks according to various protocols and / or methods proposed for standardization by 3GPP and / or other standards bodies. For example, such functionality may operate in cooperation with the one or more processors 602 to implement a PHY layer based on OFDM, OFDMA, and / or SC-FDMA techniques, such as described herein with reference to other figures.

[0165] The user interface 608 may take various forms according to a particular embodiment, or may not be present in the UE 600. In some embodiments, the user interface 608 includes a microphone, a speaker, a slidable button, a depressible button, a display, a touch screen display, a mechanical or virtual keypad, a mechanical or virtual keyboard, and / or any other user interface feature that is typically present on a mobile phone. In other embodiments, the UE 600 may include a tablet computing device with a larger touch screen display. In such embodiments, one or more of the mechanical features of the user interface 608 may be replaced by a virtual user interface feature (e.g., a virtual keypad, a virtual button, etc.) that is equivalent or functionally equivalent to that implemented using a touch screen display, as is familiar to those of ordinary skill in the art. In other embodiments, the UE 600 may be a digital computing device, such as a laptop computer, a desktop computer, a workstation, etc., which includes a mechanical keyboard that may be integrated, detachable, or detachable according to a particular exemplary embodiment. Such a digital computing device may also include a touch screen display. Many exemplary embodiments of the UE 600 with a touch screen display are capable of receiving user input, such as input related to the exemplary methods and / or processes described herein or known to those of ordinary skill in the art.

[0166] In some exemplary embodiments of the present disclosure, UE 600 includes an orientation sensor that can be used in various ways by the features and functions of UE 600. For example, UE 600 can use the output of the orientation sensor to determine when a user has changed the physical orientation of the touch screen display of UE 600. The indication signal from the orientation sensor can be used for any application executed on UE 600, so that the application can automatically change the orientation of the screen display (e.g., from portrait to landscape) when the indication signal indicates an approximately 90-degree change in the physical orientation of the device. In this way, regardless of the physical orientation of the device, the application can maintain the screen display in a user-readable manner. In addition, the output of the orientation sensor can be used in conjunction with various exemplary embodiments of the present disclosure.

[0167] The control interface 610 can take various forms depending on the particular implementation. For example, the control interface 610 can include an RS-232 interface, an RS-485 interface, a USB interface, an HDMI interface, a Bluetooth interface, an IEEE ("FireWire") interface, an I 2 C interface, PCMCIA interface, etc. In some exemplary embodiments of the present disclosure, the control interface 1260 may include an IEEE 802.3 Ethernet interface, such as described above. In some exemplary embodiments of the present disclosure, the control interface 610 may include an analog interface circuit, which includes, for example, one or more digital-to-analog (D / A) converters and / or analog-to-digital (A / D) converters.

[0168] Those skilled in the art will recognize that the above list of features, interfaces, and radio frequency communication standards is merely exemplary and does not limit the scope of the present disclosure. Figure 6 The UE 600 may include more functions as shown, including, for example, video and / or still image cameras, microphones, media players and / or recorders, etc. In addition, the one or more transceivers 604 may include circuits for communicating using additional radio frequency communication standards including Bluetooth, GPS and / or others. In addition, the one or more processors 602 may execute software code stored in the memory 606 to control such additional functions. For example, the directional speed and / or position estimate output from the GPS receiver may be used for any application executed on the UE 600, including various exemplary methods and / or computer-readable media according to various exemplary embodiments of the present disclosure.

[0169] Figure 7 is a block diagram of an exemplary network node 700 that may be configured according to various embodiments of the present disclosure, including by executing instructions on a computer-readable medium corresponding to any of the exemplary methods and / or processes described herein.

[0170] The network node 700 includes one or more processors 702, a radio network interface 704, a memory 706, a core network interface 708 and other interfaces 710. The network node 700 may include, for example, a base station, an eNB, a gNB, an access node or a component thereof.

[0171] The one or more processors 702 may include any type of processor or processing circuit, and may be configured to perform one of the methods or processes disclosed herein. The memory 706 may store software codes, programs and / or instructions executed by the one or more processors 702 to configure the network node 700 to perform various operations, including the operations described herein. For example, the execution of such storage instructions may configure the network node 700 to communicate with one or more other devices using protocols (including one or more methods and / or processes described above) according to various embodiments of the present disclosure. In addition, the execution of such storage instructions may also configure and / or facilitate the network node 700 to communicate with one or more other devices using other protocols or protocol layers (such as one or more of the PHY, MAC, RLC, PDCP and RRC layer protocols standardized by 3GPP for LTE, LTE-A and / or NR, or any other high-level protocol used in combination with the radio network interface 704 and the core network interface 708). By way of example and not limitation, the core network interface 708 includes an S1 interface, and the radio network interface 704 may include a Uu interface, such as standardized by 3GPP. The memory 706 may also store variables used in the protocol, configuration, control and other functions of the network node 700. Thus, the memory 706 may include non-volatile memory (e.g., flash memory, hard disk, etc.), volatile memory (e.g., static or dynamic RAM), network-based (e.g., "cloud") storage, or a combination thereof.

[0172] The radio network interface 704 may include a transmitter, a receiver, a signal processor, an ASIC, an antenna, a beamforming unit, and other circuits that enable the network node 700 to communicate with other equipment (in some embodiments, such as multiple compatible user equipment (UE)). In some embodiments, the network node 700 may include various protocols or protocol layers, such as PHY, MAC, RLC, PDCP, and RRC layer protocols standardized by 3GPP for LTE, LTE-A, and / or 5G / NR. According to other embodiments of the present disclosure, the radio network interface 704 may include a PHY layer based on OFDM, OFDMA, and / or SC-FDMA technology. In some embodiments, the functions of such a PHY layer may be provided collaboratively by the radio network interface 704 and the one or more processors 702.

[0173] The core network interface 708 may include a transmitter, a receiver, and other circuits that enable the network node 700 to communicate with other equipment in the core network (in some embodiments, such as circuit switching (CS) and / or packet switching core (PS) network). In some embodiments, the core network interface 708 may include an S1 interface standardized by 3GPP. In some embodiments, the core network interface 708 may include one or more interfaces to one or more SGWs, MEEs, GSNs, GSNs, and other physical devices, including functions known to those of ordinary skill in the art present in GERAN, UTRAN, E-UTRAN, and CDMA2000 core networks. In some embodiments, these one or more interfaces may be multiplexed together on a single physical interface. In some embodiments, the lower layer of the core network interface 708 may include one or more of asynchronous transfer mode (ATM), Internet Protocol (IP) on Ethernet, SDH on optical fiber, T1 / E1 / PDH on copper wire, microwave radio, or other wired or wireless transmission technologies known to those of ordinary skill in the art.

[0174] Other interfaces 710 may include transmitters, receivers, and other circuits that enable network node 700 to communicate with external networks, computers, databases, etc., for operation, management, and maintenance of network node 700 or other network devices operably connected thereto.

[0175] Figure 8 8 is a block diagram illustrating a component 800 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Figure 8 A diagrammatic representation of hardware resources 802 is shown, including one or more processors 812 (or processor cores), one or more memory / storage devices 818, and one or more communication resources 820, each of which may be communicatively coupled via a bus 822. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 804 may be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 802.

[0176] Processor 812 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) (such as a baseband processor), an application specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 814 and processor 816.

[0177] The memory / storage device 818 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 818 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory, etc.

[0178] The communication resources 820 may include an interconnect or network interface component or other suitable device to communicate with one or more peripheral devices 806 or one or more databases 808 via the network 810. For example, the communication resources 820 may include a wired communication component (e.g., for coupling via a universal serial bus (USB)), a cellular communication component, an NFC component, Parts (e.g. Low power consumption), components and other communication components.

[0179] The instructions 824 may include software, programs, applications, applet, apps, or other executable code for causing at least any one of the processors 812 to perform any one or more of the methodologies discussed herein. The instructions 824 may reside in whole or in part within at least one of the processor 812 (e.g., within a cache memory of the processor), the memory / storage device 818, or any suitable combination thereof. In addition, any portion of the instructions 824 may be transferred to the hardware resources 802 from any combination of the peripheral device 806 or the database 808. Thus, the memory of the processor 812, the memory / storage device 818, the peripheral device 806, and the database 808 are examples of computer-readable and machine-readable media.

[0180] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods described in the following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following embodiments. For another example, the circuits associated with the UE, base station, network element, etc. described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the embodiments shown in the examples section below.

[0181] Examples

[0182] The following examples relate to additional embodiments.

[0183] Embodiment 1 is a method for determining a plurality of data objects, each data object corresponding to a new radio (NR) channel using a first subcarrier spacing (SCS) and including an NR channel grid position and a synchronization signal and physical broadcast channel (SSB) grid position of each NR channel; the method comprising: for each data object, determining the NR channel grid position, wherein the NR channel grid position comprises a radio frequency (RF) reference frequency calculated using an absolute radio frequency channel number (NR-ARFCN); calculating a global synchronization channel number (GSCN) value of the NR channel corresponding to each data object; determining the NR channel (NR) corresponding to each data object based on the first SCS and a given bandwidth of the NR channel; RB ) of the given NR channel; determining the arrangement of the NR channel grid positions of each data object; calculating the edge of each NR channel corresponding to each data object based on the center frequency of the given NR channel and the arrangement of the NR channel grid positions of the data object; calculating the edge of the SSB of the NR channel corresponding to each data object based on the edge of the given NR channel; and determining the SSB grid position of each data object based on the edge of the SSB of the NR channel corresponding to the data object.

[0184] Embodiment 2 is a method according to embodiment 1, and the method further includes removing all data objects from the multiple data objects except for reserved data objects including NR channel grid positions corresponding to the same Long Term Evolution (LTE) channel grid position in the multiple data objects.

[0185] Embodiment 3 is a method according to embodiment 2, wherein the reserved data object including the NR channel grid position corresponding to the same long term evolution (LTE) channel grid position in the plurality of data objects is selected for reservation because the N channel corresponding to the data object is RB is equal to or greater than the N corresponding to the NR channel of each of the other data objects in the plurality of data objects including the NR channel grid position corresponding to the same Long Term Evolution (LTE) channel grid position RB .

[0186] Embodiment 4 is a method according to embodiment 1, wherein the method further includes removing from the plurality of data objects each data object including an NR channel grid position that does not match an NR channel grid position of any data object in a second plurality of data objects, wherein the second plurality of data objects each correspond to an NR channel using a second SCS.

[0187] Embodiment 5 is a method according to any one of embodiments 1 to 4, wherein the RF reference frequency is calculated using the following formula: REF =F REF-Offs +ΔF Global (N REF –N REF-Offs ), where: F REF is the given RF reference frequency; F REF-Offs is the reference frequency offset; ΔF Global is the granularity of the global frequency grid; N REF is the NR-ARFCN of the given reference frequency; and N REF-Offs is the NR-ARFCN offset.

[0188] Embodiment 6 is a method according to any one of embodiments 1 to 5, wherein N is determined according to the following table RB :

[0189]

[0190]

[0191] Embodiment 7 is a method according to any one of embodiments 1 to 6, wherein the arrangement for the NR channel grid position each includes: the number of physical resource blocks (PRBs) of the NR channel corresponding to the data object including the NR channel grid position; and the resource element index of the resource element corresponding to the NR channel grid position within the PRB.

[0192] Embodiment 8 is a method according to embodiment 7, wherein the resource element index of the resource element corresponding to the NR channel grid position within the PRB can be determined based on whether the number of PRBs corresponding to the NR channel of the data object including the NR channel grid position is an even number or an odd number.

[0193] Embodiment 9 is a method according to any one of embodiments 1 to 8, the method further comprising: calculating an occupied channel BW (OCB) for each NR channel corresponding to each data object; and determining whether a minimum guard band is available for each NR channel for each data object on two edges of the OCB corresponding to a given channel.

[0194] Embodiment 10 is a non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium comprising instructions, which when executed by a computer cause the computer to: determine a NR channel grid position of a new radio (NR) channel, wherein the NR channel grid position comprises a radio frequency (RF) reference frequency calculated using an absolute radio frequency channel number (NR-ARFCN); calculate a global synchronization channel number (GSCN) value for the NR channel; determine the NR channel (NR) based on a subcarrier spacing (SCS) used by the NR channel and a bandwidth of the NR channel; RB ) of the NR channel; determining the arrangement of the NR channel grid positions; calculating the edge of the NR channel based on the center frequency of the NR channel and the arrangement of the NR channel grid positions in the channel; calculating the edge of the synchronization signal and physical broadcast channel (SSB) of the NR channel based on the edge of the NR channel; and determining the SSB grid position of the NR channel based on the edge of the SSB.

[0195] Embodiment 11 is a non-transitory computer readable storage medium according to embodiment 10, wherein the RF reference frequency is calculated using the following formula: REF =F REF-Offs +ΔF Global (N REF –N REF-Offs ), where: F REF is the RF reference frequency; F REF-Offs is the reference frequency offset; ΔF Global is the granularity of the global frequency grid; N REF is the NR-ARFCN of the reference frequency; and N REF-Offs is the NR-ARFCN offset.

[0196] Embodiment 12 is a non-transitory computer-readable storage medium according to any one of embodiments 10 to 11, wherein N is determined according to the following table: RB :

[0197]

[0198] Embodiment 13 is a non-transitory computer-readable storage medium according to any one of embodiments 10 to 12, wherein the arrangement for the NR channel grid position includes: the number of physical resource blocks (PRBs) of the channel corresponding to the NR channel grid position; and the resource element index of the resource element corresponding to the NR channel grid position within the PRB.

[0199] Embodiment 14 is a non-transitory computer-readable storage medium according to embodiment 13, wherein based on whether the number of PRBs of the NR channel is even or odd, the resource element index of the resource element corresponding to the NR channel grid position within the PRB can be determined.

[0200] Embodiment 15 is a non-transitory computer-readable storage medium according to any one of embodiments 10 to 15, wherein the non-transitory computer-readable storage medium also includes instructions, which, when executed by a computer, causes the computer to: calculate the occupied channel BW (OCB) of the NR channel; and determine whether a minimum guard band is available for the channel on both edges of the OCB.

[0201] Embodiment 16 is a non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: downwardly select from a plurality of data objects, each data object corresponding to a new radio (NR) channel using a first subcarrier spacing (SCS) and including an NR channel grid position and a synchronization signal and physical broadcast channel (SSB) grid position for each NR channel using the first SCS, wherein the downward selection is performed by removing all data objects except for a reserved data object including an NR channel grid position corresponding to the same long term evolution (LTE) channel grid position in the plurality of data objects.

[0202] Embodiment 17 is a non-transitory computer-readable storage medium according to embodiment 16, wherein the reserved data object including the NR channel grid position corresponding to the same long term evolution (LTE) channel grid position in the plurality of data objects is selected for reservation because it includes N RB , the N RB is equal to or greater than N of each of the other data objects in the plurality of data objects including the NR channel grid position corresponding to the same Long Term Evolution (LTE) channel grid position RB .

[0203] Embodiment 18 is a non-transitory computer-readable storage medium according to embodiment 16, wherein the downward selection is also performed by removing each data object including an NR channel grid position that does not match the NR channel grid position of any data object in a second plurality of data objects, each of the second plurality of data objects corresponding to an NR channel using a second SCS.

[0204] Example 19 may include utilizing F REF A method of operating an NR cellular system by using a channel grid entry between a set of values ​​of REF =F REF-Offs +ΔFGlobal (N REF –N REF-Offs ), and ΔF Global =15kHz, F REF-Offs =3000MHz, N REF-Offs =600000, and N REF{744000,745344,746664,748008,749328,750672,751992,753336,754656,754668,754680,756000,765336,766656,766668,766680,768000,7693 44,770664,772008,773328,774672,775992,777336,778656,778668,778680,780000,781344,783000,784344,785664,787008,788328,789672,790 992,792336,793656,793668,793680,744660,746004,747324,748668,749988,750000,750012,751332,752676,753996,755340,765996,767340,76 8660,770004,771324,772668,773988,774000,774012,775332,776676,777996,779340,780660,783660,785004,786324,787668,788988,789000,7 89012,790332,791676,792996} or {744000,744006,745344,746664,746670,748008,749328,749334,750672,751992,51998,753336,754656,754662 ,756000,756006,765336,766656,766662,768000,768006,69344,770664,770670,772008,773328,773334,774672,775992,775998,777336,78656, 778662,780000,780006,781344,783000,783006,784344,785664,785670,787008,788328,788334,789672,790992,790998,792336,793656,793662 ,744660,744666,746004,747324,47330,748668,749988,749994,750000,750012,751332,751338,752676,753996,754002,755340,765996,766002,767340,768660,768666,770004,771324,771330,772668,773988,7739 94,774000,774012,775332,775338,776676,777996,778002,779340,78 0660,780666,783660,783666,785004,786324,786330,787668,788988, One of 788994,789000,789012,790332,790338,791676,792996,793002}. ,

[0205] Embodiment 20 may include the method of embodiment 1 or some other embodiments herein, wherein the NR channel grid entry is selected from a subset of entries according to claim 1, wherein the subset is F REF The set of values ​​of , where F REF =F REF-Offs +ΔF Global (N REF –N REF-Offs ), and ΔF Global =15kHz, F REF-Offs =3000MHz, N REF-Offs =600000, and N REF {744000,745344,746664,748008,749328,750672,751992,753336,754668,756000,765336,766668,768000,769344,770664,772008,773328,774672,775992,777336,778668,780000,781344,783000,784344,785664,787008,788328,789672,790992,792 336,793668,744660,746004,747324,748668,750000,751332,752676,753996,755340,765996,767340,768660,770004,771324,772668,774000,775332,776676,777996,779340,780660,783660,785004,786324,787668,789000,790332,791676,792996}.

[0206] Embodiment 21 may include a method according to embodiment 1 or 2 or some other embodiments herein, wherein the corresponding SSB grid entry for a given NR channel entry is given by "3000MHz+N*1.44MHz", where N is a value ranging from 0 to 14756, and the GSCN is given as "7499+N", where the GSCN is K+taken from the set {8996,9010,9023,9037,9051,9065,9079,9093,9107,9121,9218,9232,9232,9232,9246, 7,9260,9273,9287,9301,9315,9329,9343,9357,9357,9357,9371,9385,9402,9416,9430,9444,9457,9471,9485,9499,9513,9513,9513,8996,9010,9023,9037,9051,9065,9079,9093,9107,9218,9232,9246,9260,9273,9287}, where K = 0...6.

[0207] Embodiment 22 may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0208] Embodiment 23 may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0209] Embodiment 24 may include an apparatus comprising logic components, modules, or circuits for performing one or more elements of the method described in or related to any of the above embodiments or any other method or process described herein.

[0210] Embodiment 25 may include methods, techniques or processes, or parts or components thereof, as described in or related to any of the above embodiments.

[0211] Embodiment 26 may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, or process, or part thereof, described in any one of the above embodiments or related thereto.

[0212] Embodiment 27 may include a signal or a portion or component thereof as described in or related to any one of the above embodiments.

[0213] Embodiment 28 may include a datagram, packet, frame, segment, protocol data unit (PDU) or message, or a portion or component thereof, as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0214] Embodiment 29 may include a signal encoded with data or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0215] Embodiment 30 may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in any of the above embodiments or related thereto, or as otherwise described in the present disclosure.

[0216] Embodiment 31 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any of the above embodiments.

[0217] Embodiment 32 may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, as described in or related to any of the above embodiments.

[0218] Embodiment 33 may include signals in a wireless network as shown and described herein.

[0219] Embodiment 34 may include a method of communicating in a wireless network as shown and described herein.

[0220] Embodiment 35 may include a system for providing wireless communications as shown and described herein.

[0221] Embodiment 36 may include an apparatus for providing wireless communications as shown and described herein.

[0222] Unless explicitly stated otherwise, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. Modifications and variations are possible in view of the above teachings or may be obtained from the practice of the various embodiments.

[0223] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0224] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0225] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0226] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways to implement both the processes and the apparatus described herein. Therefore, the embodiments of the present invention are to be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A method of determining a plurality of data objects, each data object corresponding to a new radio (NR) channel using a first subcarrier spacing (SCS) and comprising an NR channel grid position and a synchronization signal and physical broadcast channel (SSB) grid position of each NR channel; the method comprising: For each data object, determining the NR channel grid position, wherein the NR channel grid position comprises a radio frequency (RF) reference frequency calculated using an absolute radio frequency channel number (NR-ARFCN); removing from the plurality of data objects each data object that includes an NR channel grid position that does not match an NR channel grid position of any data object in a second plurality of data objects, the second plurality of data objects each corresponding to an NR channel using a second SCS; Calculating a global synchronization channel number (GSCN) value of the NR channel corresponding to each data object; Determine the number of physical resource blocks (PRBs) (N) of the NR channel corresponding to each data object based on the first SCS and the bandwidth of a given NR channel. RB ); determining an arrangement of the NR channel grid positions for each data object; calculating an edge of each NR channel corresponding to each data object based on a center frequency of the given NR channel and the arrangement of the NR channel grid positions of the data objects; Calculate an edge of the SSB of the NR channel corresponding to each data object based on the edge of the given NR channel; The SSB grid position of each data object is determined based on the edge of the SSB of the NR channel corresponding to the data object.

2. The method of claim 1 , further comprising removing from the plurality of data objects all data objects except for reserved data objects including NR channel grid positions corresponding to the same Long Term Evolution (LTE) channel grid position in the plurality of data objects.

3. The method of claim 2, wherein the reserved data object including the NR channel grid position corresponding to the same Long Term Evolution (LTE) channel grid position among the plurality of data objects is selected for reservation because the N channel corresponding to the data object is RB is equal to or greater than the N corresponding to the NR channel of each of the other data objects in the plurality of data objects including the NR channel grid position corresponding to the same Long Term Evolution (LTE) channel grid position RB .

4. The method according to claim 1, further comprising: Calculate the occupied channel BW (OCB) of each NR channel corresponding to each data object; as well as Determine whether a minimum guard band is available for each NR channel for each data object on both edges of the OCB corresponding to a given channel.

5. The method according to any one of claims 1 to 4, wherein the RF reference frequency is calculated using the following formula: F REF =F REF-Offs +ΔF Global (N REF –N REF-Offs ) in: F REF is a given RF reference frequency; F REF-Offs is the reference frequency offset; ΔF Global is the granularity of the global frequency grid; N REF is the NR-ARFCN of the given RF reference frequency; and N REF-Offs is the NR-ARFCN offset.

6. The method according to any one of claims 1 to 4, wherein the N RB ： 7. The method according to any one of claims 1 to 4, wherein the arrangements for the NR channel grid positions each comprise: a physical resource block (PRB) number of the NR channel corresponding to the data object including the NR channel grid position; as well as The resource element index of the resource element corresponding to the NR channel grid position within the PRB.

8. The method of claim 7 , wherein the resource element index of the resource element corresponding to the NR channel grid position within the PRB is determined based on whether the number of PRBs corresponding to the NR channel of the data object including the NR channel grid position is even or odd.

9. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: determining a new radio (NR) channel grid position for a NR channel, wherein the NR channel grid position comprises a radio frequency (RF) reference frequency calculated using an absolute radio frequency channel number (NR-ARFCN); removing, from a plurality of data objects, each data object including an NR channel grid position that does not match an NR channel grid position of any data object in a second plurality of data objects, each data object in the plurality of data objects corresponding to a new radio (NR) channel using a first subcarrier spacing (SCS) and including an NR channel grid position and a synchronization signal and physical broadcast channel (SSB) grid position for each NR channel using the first SCS, the second plurality of data objects each corresponding to an NR channel using a second SCS; Calculate a global synchronization channel number (GSCN) value of the NR channel; The number of physical resource blocks (PRBs) (N) of the NR channel is determined based on a subcarrier spacing (SCS) used by the NR channel and a bandwidth of the NR channel. RB ); Determining the arrangement of the NR channel grid positions; calculating an edge of the NR channel based on a center frequency of the NR channel and the arrangement of the NR channel grid positions in the channel; Calculating an edge of a synchronization signal and a physical broadcast channel (SSB) of the NR channel based on the edge of the NR channel; as well as An SSB grid position of the NR channel is determined based on the edge of the SSB.

10. The non-transitory computer readable storage medium of claim 9, wherein the RF reference frequency is calculated using the following formula: F REF =F REF-Offs +ΔF Global (N REF –N REF-Offs ) in: F REF is the RF reference frequency; F REF-Offs is the reference frequency offset; ΔF Global is the granularity of the global frequency grid; N REF is the NR-ARFCN of the RF reference frequency; and N REF-Offs is the NR-ARFCN offset.

11. The non-transitory computer-readable storage medium according to any one of claims 9 to 10, wherein the N is determined according to the following table: RB :

12. The non-transitory computer-readable storage medium of any one of claims 9 to 10, wherein the arrangement for the NR channel grid positions comprises: a number of physical resource blocks (PRBs) of the channel corresponding to the NR channel grid position; as well as The resource element index of the resource element corresponding to the NR channel grid position within the PRB.

13. The non-transitory computer-readable storage medium of claim 12, wherein the resource element index of the resource element corresponding to the NR channel grid position within the PRB is determined based on whether the number of PRBs for the NR channel is even or odd.

14. A non-transitory computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to: Down-selecting from a plurality of data objects, each data object corresponding to a new radio (NR) channel using a first subcarrier spacing (SCS) and including an NR channel grid position and a synchronization signal and physical broadcast channel (SSB) grid position for each NR channel using the first SCS, wherein the down-selecting is performed by removing all data objects except for retained data objects in the plurality of data objects including an NR channel grid position corresponding to the same long term evolution (LTE) channel grid position, and wherein the down-selecting is also performed by removing each data object including an NR channel grid position that does not match an NR channel grid position of any data object in a second plurality of data objects, each of the second plurality of data objects corresponding to an NR channel using a second SCS.

15. The non-transitory computer-readable storage medium of claim 14, wherein the reserved data object of the plurality of data objects including an NR channel grid position corresponding to the same Long Term Evolution (LTE) channel grid position is selected for reservation because the N channel corresponding to the data object is RB is equal to or greater than the N corresponding to the NR channel of each of the other data objects in the plurality of data objects including the NR channel grid position corresponding to the same Long Term Evolution (LTE) channel grid position RB .

Images