Paging for unauthorized new radio

Abstract

Methods and apparatus for paging for an unlicensed new radio (NR-U) are disclosed. These methods include means for performing paging using a plurality of paging operations (POs) during a DRX cycle, performing paging using a paging window, performing paging using a PO composed of a plurality of sweeps and / or iterations, signaling a DL channel access indication for paging, and performing paging using a dynamic DRX. According to one embodiment, the apparatus may receive a signal comprising a plurality of POs, each PO comprising a plurality of physical downlink control channel (PDCCH) monitoring operations. The apparatus may monitor a portion of the plurality of paging operations based on the reception of an identifier associated with the apparatus. The apparatus may detect paging downlink control information (DCI) in a PDCCH monitoring operation among the plurality of PDCCH monitoring operations in the monitored portion.

Description

Technology Field

[0001] 관련 출원들에 대한 상호 참조

[0002] This application claims the benefit of U.S. provisional patent application No. 62 / 736,850 filed on September 26, 2018, the entirety of which is incorporated herein by reference. Background Technology

[0003] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities, encompassing research on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has initiated standardization work for a next-generation cellular technology called New Radio (NR), also referred to as "5G."

[0004] This summary is provided to introduce, in a simplified form, selected from the concepts further described in the following detailed description. This summary is not intended to identify the principal or essential features of the claimed subject matter, nor is it used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to any or all limitations addressing any of the disadvantages mentioned in any part of this disclosure.

[0005] Methods and apparatus for paging for unlicensed new radio (NR-U) are described herein. These methods include means for performing paging using a plurality of paging occasions (PO) during a DRX cycle, performing paging using a paging window, performing paging using a PO composed of a plurality of sweeps and / or iterations, signaling a DL channel access indication for paging, and performing paging using a dynamic DRX. According to one embodiment, the device may receive a signal comprising a plurality of POs, each PO comprising a plurality of physical downlink control channel (PDCCH) monitoring occasions. The device may monitor a portion of the plurality of paging occasions based on the reception of an identifier associated with the device. The device may detect paging downlink control information (DCI) in a PDCCH monitoring occasion among the plurality of PDCCH monitoring occasions in the monitored portion. Brief explanation of the drawing

[0006] A more detailed understanding can be obtained from the following description, given as an example in relation to the attached drawings. Figure 1 is a diagram of a bandwidth adaptation (BA) example. FIG. 2 is a diagram of exemplary multiplexing of phasing accounts (POs) in time and frequency domains. Figure 3 is a diagram of an exemplary time-division multiplexing of consecutive POs. Figure 4 is a diagram of an exemplary time-division multiplexing of discontinuous POs. Figure 5 is a diagram of an exemplary time-division multiplexing of discontinuous POs. Figure 6 is a diagram of exemplary time and frequency division multiplexing of consecutive POs. Figure 7 is a diagram of exemplary frequency division multiplexing of monitored POs. FIG. 8 is an exemplary configuration having non-contiguous POs in a paging search space. FIG. 9 is an exemplary configuration having adjacent POs in a pagination search space. FIG. 10a is a diagram of an exemplary configuration of POs from different PDCCH monitoring occupation groups. FIG. 10b is a diagram of another exemplary configuration of POs from different PDCCH monitoring occupation groups. FIG. 11a is an exemplary configuration for monitoring POs in multiple PFs. FIG. 11b is another exemplary configuration for monitoring POs in multiple PFs. Figure 12 is a flowchart of an exemplary algorithm that can determine whether subsequent POs should be monitored. Figure 13 is a flowchart of an exemplary algorithm of an alternative that can determine whether subsequent POs should be monitored. Figure 14 is a drawing of an exemplary paging monitoring window. FIG. 15 is a drawing of an exemplary PO for a scenario having multiple sweeps. Figure 16 is a drawing of an exemplary PO for a scenario with repetition. FIG. 17 is a drawing of an exemplary PO for a scenario having multiple sweeps and / or repetitions. Figure 18 is a drawing of an extended PO with T=32, N=16, Ns=4, M=2 and S=3. FIG. 19 is a diagram of an exemplary procedure for signaling a DL channel access indication for paging using a paging DCI (LBT success on the first attempt). FIG. 20 is a diagram of an exemplary procedure for signaling a DL channel access indication for paging using a paging DCI (LBT success on the second attempt). FIG. 21a illustrates an exemplary communication system in which the methods and devices described and claimed herein may be implemented. FIG. 21b is a block diagram of an exemplary device or apparatus configured for wireless communications according to embodiments illustrated in this specification, such as, for example, a wireless transmission / reception unit (WTRU). FIG. 21c is a system diagram of a RAN and a core network according to an embodiment. FIG. 21d is a system diagram of a RAN and a core network according to an embodiment. FIG. 21e is a system diagram of a RAN and a core network according to an embodiment. FIG. 21f is a block diagram of an exemplary computing system in which one or more devices of the communication networks shown in FIG. 21a, FIG. 21c, FIG. 21d and FIG. 21e may be implemented. FIG. 21g illustrates an exemplary communication system in which the methods and devices described and claimed herein may be implemented. Specific details for implementing the invention

[0007] Methods and apparatus for paging for unlicensed new radio (NR-U) are described herein. According to embodiments described herein, the apparatus may receive a signal comprising a plurality of POs, each PO comprising a plurality of Physical Downlink Control Channel (PDCCH) monitoring operations. The apparatus may monitor a portion of a plurality of paging operations based on the reception of an identifier associated with the apparatus. The apparatus may detect paging downlink control information (DCI) from a PDCCH monitoring operation among the plurality of PDCCH monitoring operations in the monitored portion.

[0008] The following is a list of abbreviations that may appear in the following description. Unless otherwise specified, abbreviations used in this specification refer to the corresponding terms listed below:

[0009] BA Bandwidth Adaption

[0010] BWP Bandwidth Part

[0011] CAI Channel Access Indication

[0012] CORESET Control Resource Set

[0013] DCI Downlink Control Information

[0014] DL Downlink

[0015] DRS Discovery Reference Signal

[0016] DRX Discontinuous Reception

[0017] DwPTS Downlink Pilot Timeslot

[0018] eNB Evolved Node B

[0019] gNB NR NodeB

[0020] IE Information Element

[0021] L1 Layer 1

[0022] LAA License Assisted Access

[0023] LBT Listen-Before-Talk

[0024] LTE Long Term Evolution

[0025] MAC Medium Access Control

[0026] MT Mobile Terminated

[0027] NR New Radio

[0028] NR-U NR Unlicensed

[0029] OFDM Orthogonal Frequency Division Multiplexing

[0030] PDCCH Physical Downlink Control Channel

[0031] PF Paging Frame

[0032] PHY Physical Layer

[0033] PO Paging Occasion

[0034] P-RNTI Paging Radio Network Temporary Identifier

[0035] PSB Paging Subband

[0036] PWS Public Warning System

[0037] RAN Radio Access Network

[0038] RNTI Radio Network Temporary Identifier

[0039] RRC Radio Resource Control

[0040] RRM Radio Resource Management

[0041] SCell Secondary Cell

[0042] SI System Information

[0043] SpCell Special Cell

[0044] SS Synchronization Signal

[0045] SSB SS Block

[0046] TRP Transmission and Reception Point

[0047] UE User Equipment

[0048] UL Uplink

[0049] Carrier aggregation with at least one SCell operating in the unlicensed spectrum may be referred to as Licensed-Assisted Access (LAA). Thus, in an LAA, a configured set of serving cells for a UE may include at least one SCell operating in the unlicensed spectrum according to frame structure type 3, and may also be called an LAA SCell. Typically, LAA SCells can function as regular SCells.

[0050] The LAA eNB and UE may apply Listen-Before-Talk (LBT) before performing transmission on the LAA SCell. When LBT is applied, the transmitter may listen to / sens the channel to determine whether the channel is free or in use. If the channel is determined to be free, the transmitter may perform transmission; otherwise, it may not perform transmission. The LAA eNB may continue to satisfy the LAA maximum energy detection threshold requirements by utilizing channel access signals from other technologies, for example, for the purpose of LAA channel access.

[0051] LTE frame structure type 3 can be applied to LAA secondary cell operations that typically have only a normal circular prefix. Each radio frame is T f = 307200ㆍ T s = length that can be 10ms and is numbered from 0 to 19. T slot = 15360ㆍ T s = It can be composed of 20 slots of 0.5ms. A subframe can be defined as 2 consecutive slots, where subframe i can be composed of slots i and 2i+1.

[0052] Ten subframes within a radio frame may be available for downlink or uplink transmissions. Downlink transmissions may occupy one or more consecutive subframes, for example, starting anywhere within a subframe and being fully occupied, or ending with the last subframe following one of the DwPTS. Uplink transmissions may occupy one or more consecutive subframes.

[0053] The UE may utilize discontinuous reception (DRX) in the RRC_IDLE and RRC_INACTIVE states to reduce power consumption. The UE may monitor one paging occupation (PO) per DRX cycle. A PO may be a set of PDCCH monitoring occupations and may consist of multiple time slots (e.g., subframes or OFDM symbols) in which paging downlink control information (DCI) can be transmitted. A paging frame (PF) is a radio frame and may include one or more PO(s) or the start point of a PO.

[0054] In multi-beam operations, the length of a single PO may be a period of beam sweeping, and the UE may assume that the same paging message is repeated in all beams of the sweeping pattern, and thus the selection of beam(s) for receiving the paging message may depend on the UE implementation. The paging message may be the same for both RAN-initiated paging and CN-initiated paging.

[0055] The UE can initiate the RRC connection resumption procedure when it receives RAN paging. If the UE receives CN initiation paging while in the RRC_INACTIVE state, the UE can move to RRC_IDLE and notify the NAS.

[0056] PF and PO can be determined by the following formulas. The SFN for PF can be determined by (SFN + PF_offset) mod T = (T div N)*(UE_ID mod N).

[0057] The index (i_s) marking the start of the set of PDCCH monitoring operations for the paging DCI can be determined by i_s = floor(UE_ID / N) mod Ns.

[0058] PDCCH monitoring accounts for paging, when configured, paging-SearchSpace and firstPDCCH-MonitoringOccasionOfPO It can be determined accordingly. Otherwise, PDCCH monitoring accounts for paging can be determined according to the default association (i.e., PDCCH monitoring accounts for paging can be the same as those for RMSI).

[0059] For default association, Ns can be 1 or 2. If Ns=1, there can be only one PO starting from PF. If Ns=2, the PO can be in the first half-frame (i_s=0) or the second half-frame (i_s=1) of PF.

[0060] In the case of non-default association (i.e., paging-SearchSpace (when used), the UE can monitor the (i_s+1)th PO, which the first PO can start from in the PF. PDCCH monitoring accounts for paging that do not overlap with UL symbols can be numbered sequentially from zero, starting from the first PDCCH monitoring account for paging in the PF. firstPDCCH-MonitoringOccasionOfPO When exists, the (i_s+1)th PO is firstPDCCH-MonitoringOccasionOfPO A set of 'S' consecutive PDCCH monitoring accounts for paging starting from the PDCCH monitoring account indicated by (i.e., firstPDCCH-MonitoringOccasionOfPO It may be the (i_s+1)th value of the parameter. Otherwise, the (i_s+1)th PO may be a set of 'S' consecutive PDCCH monitoring accounts for paging, starting from the (i_s*S)th PDCCH monitoring account for paging, where 'S' is SystemInformationBlock1 It may be the number of actual transmitted SSBs determined by ssb-PositionsInBurst. The Kth PDCCH monitoring operation for paging in PO may correspond to the Kth transmitted SSB.

[0061] The following parameters may be used in the calculation of the aforementioned PF and i_s:

[0062] (1) T: UE's DRX cycle (if T is configured by RRC or higher layers, it may be determined by the shortest of the UE-specific DRX values ​​and the default DRX value broadcast from system information. If the UE-specific DRX is not configured by RRC or higher layers, the default value may be applied);

[0063] (2) N: the total number of paging frames in T;

[0064] (3) Ns: the number of paging accounts for PF;

[0065] (4) PF_offset: The offset used to determine the PF;

[0066] (5) UE_ID: 5G-S-TMSI mod 1024.

[0067] The parameters N, Ns, first-PDCCH-MonitoringOccasionOfPO, PF_offset, and the length of the default DRX cycle are SIB1 It can be signaled in. If the UE does not have a 5G-S-TMSI, for example, if the UE has not yet registered with the network, the UE may use the identity UE_ID=0 in the above PF and i_s formulas as a default. The 5G-S-TMSI can be a bit string of 48 bits in length. The 5G-S-TMSI in the above formulas can be interpreted as a binary number where the leftmost bit represents the most significant bit.

[0068] Table 1 below shows the information that can be transmitted by DCI format 1_0 with a CRC scrambled by P-RNTI.

[0069]

[0070]

[0071] Table 2 below shows the information that can be transmitted by DCI format 1_0 with a CRC scrambled by P-RNTI.

[0072] Table 2

[0073]

[0074] By Bandwidth Adaptation (BA), the receiving and transmitting bandwidths of the UE typically do not need to be as large as the cell's bandwidth and can be adjusted; their width can be ordered to change (e.g., to be reduced during periods of low activity to save power), their position can be shifted in the frequency domain (e.g., to increase scheduling flexibility), and their subcarrier spacing can be ordered to change (e.g., to allow different services). A subset of the cell's total cell bandwidth may be referred to as a Bandwidth Part (BWP), and BA can be achieved by configuring the UE with BWP(s) and informing the UE which of the configured BWPs is the currently active BWP.

[0075] FIG. 1 illustrates an example of a BA (100). In the example of FIG. 1, three different BWPs are illustrated for time (102) and frequency: BWP1 (110), BWP2 (111), and BWP3 (112). The BWPs may be configured as follows: BWP1 (110) may have a width of 40 MHz and a subcarrier spacing of 15 kHz; BWP2 (111) may have a width of 10 MHz and a subcarrier spacing of 15 kHz; and BWP3 (112) may have a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0076] A serving cell may consist of up to four BWPs, and typically, for an active serving cell, one active BWP exists at any given time. BWP switching for a serving cell can be used to activate an inactive BWP and deactivate an active BWP at a time, and can be controlled by a PDCCH indicating downlink assignment or uplink acknowledgment. Upon addition of a SpCell (special cell) or activation of a SCell, one BWP may be initially active without receiving a PDCCH indicating downlink assignment or uplink acknowledgment. The active BWP for a serving cell may be indicated by an RRC or a PDCCH. For unpaired spectrum, a DL BWP may be paired with a UL BWP, and BWP switching may be common to both UL and DL.

[0077] The embodiments described herein address several issues in conventional paging procedures. In the case of NR, the UE monitors one PO per DRX cycle, where the PO may be a set of PDCCH monitoring operations, each corresponding to a fixed time instance (e.g., one or more OFDM symbols) within a paging frame (PF), where a paging DCI may be transmitted. In the case of NR-U, the gNB may need to perform an LBT before performing DL transmissions, which may prevent the gNB from transmitting a paging DCI during the PO. This may result in the gNB having to wait a full DRX cycle before attempting to page the UE again, which may be unacceptable in some scenarios, for example, when paging the UE to establish a Mobile Terminated (MT) call for a low system access latency service or when transmitting a Public Warning System (PWS) indication. Additionally, NR introduced the RRC_INACTIVE state, intended to allow, for example, a UE to transition from a low-power state to a fully connected state very quickly and efficiently. In the case of NR-U, the benefits of this state may be lost if the paging procedure is severely affected by LBT. Therefore, it is necessary to improve the NR-U paging procedure to ensure that the UE can be paged reliably and to avoid causing excessive latency.

[0078] The embodiments disclosed in this specification include the following solutions to the problems described above:

[0079] (1) For example, methods for performing paging using multiple POs during a DRX cycle as follows:

[0080] A method for a UE to monitor multiple POs during a DRX cycle - the POs to be monitored may be multiplexed in time and / or frequency domains -;

[0081] One or more UEs Paging-SearchSpace A method for selecting POs to monitor from the field during the DRX cycle;

[0082] A method for a UE to select POs to monitor during a DRX cycle from one or more PDCCH monitoring occupation groups;

[0083] A method for a UE to select POs to monitor during a DRX cycle from POs associated with multiple PFs;

[0084] A method for determining the next PO to monitor in a DRX cycle based on a set of configured rules by a UE;

[0085] A method for a UE to monitor POs configured for multiple BWPs / subbands; and

[0086] A method for determining when subsequent POs configured by the UE in a DRX cycle should be monitored.

[0087] (2) For example, methods for performing paging using a paging window as follows:

[0088] A method for defining a flexible starting point for a PO.

[0089] (3) Methods for performing paging using a PO composed of multiple sweeps / repetitions as follows:

[0090] PO is defined as a set of successive PDCCH monitoring operations that can be used for the transmission of paging DCI using multiple sweeps and / or iterations.

[0091] (4) Methods for signaling DL channel access indication for paging, for example, as follows:

[0092] A method for signaling DL channel access indication via paging DCI.

[0093] (5) For example, methods for performing paging using dynamic DRX as follows:

[0094] A method for dynamically adapting the DRX cycle when the UE detects whether the gNB was able to acquire the channel during PO.

[0095] FIG. 2 is an example (200) of multiplexing POs in time and frequency domains according to one embodiment, which may be used in combination with any of the embodiments described herein. FIG. 2 illustrates a plurality of POs (210) multiplexed in a time domain (202) and a frequency domain (201). As illustrated in the example of FIG. 2, to improve the robustness of the paging procedure, a UE may monitor one or more of the POs (210) during a DRX cycle, wherein one or more POs (210) to be monitored may be multiplexed in the time domain (202) and / or the frequency domain (201). The number of POs (210) to be monitored during a DRX cycle may be pre-configured or configured by upper layers using broadcast or dedicated signaling, and may depend, for example, on service type, system access latency requirements, power consumption requirements.

[0096] For example, the PCCH-Config field included in the DownlinkConfigCommonSIB IE can be used to signal a parameter, e.g., Nm, which is used to configure the number of POs to be monitored during a DRX cycle. For illustrative purposes, a scenario in which the parameter Nm can be set to a value equal to 1, 2, 4, or 8 is considered herein. The parameter can be signaled using the PCCH-Config field defined as shown below. In this example, when the parameter Nm is not explicitly signaled, a default value of 1 may be assumed. Support for extensions to other parameters signaled via the IE, e.g., additional SCSs, Ns values, N values, PF offset values, etc., may be performed in a manner similar to that exemplified below.

[0097]

[0098] FIG. 3 is an example (300) of monitoring a plurality of consecutive POs multiplexed in the time domain according to one embodiment which may be used in combination with any of the embodiments described herein. In the example of FIG. 3, the UE may be configured to monitor a plurality of POs for a DRX cycle, e.g., Nm, wherein the monitored POs may correspond to a set of POs multiplexed in the time domain. The POs to be monitored may be associated with a PF having an SFN determined by the formula: (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N). For example, the monitored POs may correspond to a set of consecutive POs that can be multiplexed in the time domain, wherein the UEs are distributed among different sets of consecutive POs based on UE_ID. In an embodiment, index i_s mcan indicate the start of the set of PDCCH monitoring operations for the paging DCI of the m-th monitored PO, where 1 ≤ m ≤ Ns is the formula: i_s m = can be determined by (floor (UE_ID / N) + (m - 1)) mod Ns.

[0099] Table 3 below shows the results of calculations for the three different UEs shown in FIG. 3, namely UE1 (302), UE33 (303), and UE225 (304), for the scenario T=32, N=16, Ns=8, and Nm=4.

[0100] Table 3

[0101]

[0102] Referring to FIG. 3, a plurality of POs (310, 311, 312, 313, 314, 315, 316, and 317) within a time domain (301) are illustrated. UE1 (302) can monitor POs (320) during POs (310, 311, 312, 313) and does not monitor POs (321) during POs (314, 315, 316, and 317). UE33 (303) can monitor POs (323) during POs (312, 313, 314, and 315) and does not monitor POs (322) during POs (310, 311, 316, and 317). UE225 (304) can monitor POs (324) during POs (310, 311, 316, and 317) and does not monitor POs (325) during POs (312, 313, 314, and 315).

[0103] FIG. 4 is an example (400) of monitoring a plurality of discontinuous POs multiplexed in the time domain according to one embodiment, which can be used in combination with any of the embodiments described herein. The channel access probability for POs multiplexed in the time domain can be highly correlated, particularly when POs occur close to each other in time. To address this problem, as illustrated in the example of FIG. 4, a UE may be configured to monitor a set of discontinuous POs multiplexed in the time domain, wherein UEs may be distributed across different sets of discontinuous POs based on UE_ID. In an embodiment, index i_s m can indicate the start of the set of PDCCH monitoring operations for the paging DCI of the m-th monitored PO, where 1 ≤ m ≤ Ns is the formula: i_s m = can be determined by (floor (UE_ID / N) + (Ns div Nm) * (m - 1)) mod Ns.

[0104] Table 4 shows the results of calculations for the three different UEs shown in FIG. 4, namely UE1 (402), UE17 (403), and UE33 (404), for the scenario where T=32, N=16, Ns=8, and Nm=4.

[0105] Table 4

[0106]

[0107] Referring to FIG. 4, a plurality of POs (410, 411, 412, 413, 414, 415, 416, and 417) within a time domain (401) are illustrated. UE1 (402) can monitor POs (420) during POs (410, 412, 414, and 416) and does not monitor POs (421) during POs (411, 413, 415, and 417). UE17 (403) can monitor POs (423) during POs (411, 413, 415, and 417) and does not monitor POs (422) during POs (410, 412, 414, and 416). UE33 (404) can monitor POs (424) during POs (410, 412, 414, and 416) and does not monitor POs (425) during POs (411, 413, 415, and 417).

[0108] FIG. 5 is another example (500) of monitoring a plurality of discontinuous POs multiplexed in the time domain according to one embodiment, which can be used in combination with any of the embodiments described in this specification.

[0109] Table 5 shows the results of calculations for the three different UEs shown in FIG. 5, namely UE1 (502), UE17 (503), and UE33 (504), for the scenario where T=32, N=16, Ns=8, and Nm=2.

[0110]

[0111]

[0112] Referring to FIG. 5, a plurality of POs (510, 511, 512, 513, 514, 515, 516, and 517) within a time domain (501) are illustrated. UE1 (502) can monitor POs (520) during POs (510 and 514) and does not monitor POs (521) during POs (511, 512, 513, 515, 516, and 517). UE17 (503) can monitor POs (523) during POs (511 and 515) and does not monitor POs (522) during POs (510, 512, 513, 514, 516, and 517). UE33 (504) can monitor POs (525) during POs (512 and 516) and does not monitor POs (524) during POs (510, 511, 513, 514, 515, and 517).

[0113] FIG. 6 is another example (600) of monitoring multiplexed POs in the time and frequency domains according to one embodiment that may be used in combination with any of the embodiments described herein. For broadband carriers, the DL channel may be divided into subbands, where LBT may be performed independently on each subband. A paging subband (PSB) may be defined as a subband where a UE can monitor PDCCH for paging. In the example of FIG. 6, the UE may be configured to monitor PDCCH for paging on one or more PSBs during a DRX cycle, wherein the UEs may be distributed across different PSBs based on UE_ID. The UE may monitor for paging on different PSBs during each monitored PO of the DRX cycle, wherein the PSB on which paging is monitored by the UE during the m-th monitored PO is formula: PSB m = (floor(UE_ID / (N*Ns)) + (m - 1)) mod N PSB It can be determined by.

[0114] Table 6 shows the results of calculations for three different UEs, namely UE1, UE33, and UE225, for a scenario where UEs monitor consecutive POs and T=32, N=16, Ns=8, Nm=4, and Npsb=4.

[0115] Table 6

[0116]

[0117] Referring to FIG. 6, a plurality of POs (610, 611, 612, 613, 614, 615, 616, and 617) and a plurality of sub-bands, namely sub-band 3 (602), sub-band 2 (603), sub-band 1 (604), and sub-band 0 (605), are shown in the time domain (601). UE1 can monitor the POs (621). UE33 can monitor the POs (622). UE225 can monitor the POs (620). The UEs do not monitor the POs (623).

[0118] FIG. 7 is an example (700) of monitoring multiplexed POs only in the frequency domain according to one embodiment that can be used in combination with any of the embodiments described herein. In the example of FIG. 7, the UE can monitor multiplexed POs only in the frequency domain during the DRX cycle. Referring to FIG. 7, the POs are multiplexed at a frequency where T=32, N=16, Ns=8, Nm=4, and Npsb=4. FIG. 7 illustrates a plurality of POs (710, 711, 712, 713, 714, 715, 716, 717) and a plurality of subbands, namely subband 3 (702), subband 2 (703), subband 1 (704), and subband 0 (705) within the time domain (701). UE1 can monitor the POs (720). UE33 can monitor the POs (721). UE225 can monitor POs (722). UEs do not monitor POs (723).

[0119] The following is an example of a PCCH-Config information element (IE) that can be used to signal the parameters described in this specification:

[0120]

[0121] Table 7

[0122]

[0123] PDCCH-ConfigCommon Signaled through IE Paging-SearchSpace The field can be used to configure the non-default associations of POs and SSBs. In the case of NR-U, multiple fields are used to configure the set of POs that the UE will monitor during the DRX cycle. Paging-SearchSpace Fields may be used. POs to be monitored may be associated with a PF having an SFN, which can be determined by the formula: (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N). An index (i_s) marking the start of the set of PDCCH monitoring accounts for the paging DCI may be determined by i_s = floor (UE_ID / N) mod Ns.

[0124] The set of POs to be monitored during the DRX cycle consists of Nm. Paging-SearchSpaces Each can be composed of the (i_s+1)th PO. The POs in each paging search space can be organized as illustrated in the examples of FIGS. 8 and 9, thereby allowing the POs monitored by a given UE during a DRX cycle to be grouped together in time or distributed in time.

[0125] FIG. 8 is an example (800) of an exemplary configuration having non-adjacent POs in a paging search space according to one embodiment, which may be used in combination with any of the embodiments described herein. Each paging search space in this example includes a plurality of non-adjacent POs, each comprising one or more PDCCH monitoring operations. The example of FIG. 8 illustrates paging-searchspace 4 (840) and PO1 (841), PO2 (842), PO3 (843), and PO4 (844) for a time domain (804). FIG. 8 also illustrates paging-searchspace 3 (830) and PO1 (831), PO2 (832), PO3 (833), and PO4 (834) for a time domain (803). FIG. 8 also illustrates paging-searchspace 2 (820) and PO1 (821), PO2 (822), PO3 (823) and PO4 (824) for the time domain (802). FIG. 8 also illustrates paging-searchspace 1 (810) and PO1 (811), PO2 (812), PO3 (813) and PO4 (814) for the time domain (801).

[0126] FIG. 9 is an example (900) of an exemplary configuration having adjacent POs in a paging-searchspace according to one embodiment, which may be used in combination with any of the embodiments described herein. Each paging-searchspace in this example includes a plurality of adjacent POs, each comprising one or more PDCCH monitoring operations. The example of FIG. 9 illustrates paging-searchspace 4 (940) and PO1 (941), PO2 (942), PO3 (943), and PO4 (944) for a time domain (904). FIG. 9 also illustrates paging-searchspace 3 (930) and PO1 (931), PO2 (932), PO3 (933), and PO4 (934) for a time domain (903). FIG. 9 also illustrates paging-searchspace 2 (920) and PO1 (921), PO2 (922), PO3 (923) and PO4 (924) for the time domain (902). FIG. 9 also illustrates paging-searchspace 1 (910) and PO1 (911), PO2 (912), PO3 (913) and PO4 (914) for the time domain (901).

[0127] The following can be used to configure the aforementioned multiple pagination search spaces PDCCH-ConfigCommon This is an example of IE:

[0128]

[0129] Table 8

[0130]

[0131]

[0132] A UE may be configured to monitor multiple POs during a DRX cycle, wherein the monitored POs may be associated with multiple groups of PDCCH monitoring operations. In this embodiment, the POs to be monitored may be associated with a PF having an SFN that can be determined by the formula: (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N). An index (i_s) marking the start of the set of PDCCH monitoring operations for the paging DCI in each group may be determined by i_s = floor (UE_ID / N) mod Ns.

[0133] The set of POs monitored by the UE during the DRX cycle may consist of the (i_s+1)th PO selected from each configured group of PDCCH monitoring operations.

[0134] Multiple sets of PDCCH monitoring operations can be configured by upper layers using broadcast or dedicated signaling.

[0135] FIG. 10a is an example (1000) of interleaved POs from different PDCCH monitoring occupation groups according to one embodiment, which may be used in combination with any of the embodiments described herein. Each PO in this example comprises one or more PDCCH monitoring occupations. The example of FIG. 10a illustrates each PO from different PDCCH monitoring occupation groups interleaved with other POs of different monitoring occupation groups. PDCCH monitoring occupations within each group may be organized into POs and interleaved with respect to a time domain (1001) as follows: PO 1,1 , PO 2,1 , PO 3,1 , PO 4,1 , PO 1,2 , PO 2,2 , PO 3,2 , PO 4,2, PO 1,3 , PO 2,3 , PO 3,3 , PO 4,3 , PO 1,4 , PO 2,4 , PO 3,4 , and PO 4,4 The indices of the POs shown in Fig. 10a are the PDCCH monitoring occupation group and PO number.

[0136] FIG. 10b is an example of non-interleaved POs from different PDCCH monitoring occupation groups according to one embodiment, which may be used in combination with any of the embodiments described herein. Each PO in this example comprises one or more PDCCH monitoring occupations. The PDCCH monitoring occupations within each group may be organized into POs for a time domain (1002) as follows: PO 1,1 , PO 1,2 , PO 1,3 , PO 1,4 , PO 2,1 , PO 2,2 , PO 2,3 , PO 2,4 , PO 3,1 , PO 3,2 , PO 3,3 , PO 3,4 , PO 4,1 , PO 4,2 , PO 4,3 , and PO 4,4 The indices of the POs shown in Fig. 10b are the PDCCH monitoring occupation group and PO number.

[0137] for example, PCCH-Config Included in IE firstPDCCH-MonitoringOccasionOfPO The field can be defined as shown below to enable the UE to monitor POs associated with up to four different groups of PDCCH monitoring operations:

[0138]

[0139] Table 9

[0140]

[0141] The UE may be configured to monitor multiple POs during a DRX cycle, wherein the monitored POs may be associated with multiple PFs. In this embodiment, the POs to be monitored are given by the formula: (SFN + PF_offset m It can be associated with PFs having an SFN that can be determined by ) mod T = (T div N) * (UE_ID mod N), where PF_offset m is the offset associated with the m-th PF containing one or more POs to be monitored during the DRX cycle. The index (i_s) marking the start of the set of PDCCH monitoring operations for the paging DCI in each PF can be determined by the formula: i_s = floor(UE_ID / N) mod Ns.

[0142] The set of PF_offsets used can be configured by upper layers using broadcast or dedicated signaling. For example, PCCH-Config Included in IE nAndPagingFrameOffset The field can be defined as follows to allow the UE to monitor POs associated with up to 4 PFs:

[0143]

[0144] FIG. 11a is an example (1100) of monitoring adjacent PFs according to one embodiment, which can be used in combination with any of the embodiments described herein. The example of FIG. 11a illustrates each PF and its offset, namely PF (1101) and PF_Offset1 (1111), PF (1102) and PF_Offset2 (1112), PF (1103) and PF_Offset3 (1113), and PF (1104) and PF_Offset4 (1114).

[0145] FIG. 11b is an example of monitoring non-adjacent PFs according to one embodiment, which may be used in combination with any of the embodiments described herein. The example of FIG. 11b illustrates each PF and its offset, namely PF (1121) and PF_Offset1 (1131), PF (1122) and PF_Offset2 (1132), PF (1123) and PF_Offset3 (1133), and PF (1124) and PF_Offset4 (1134).

[0146] Rule-based methods can be used to determine additional POs that can be monitored during the DRX cycle. The PF SFN and index i_s corresponding to the first PO to be monitored during the DRX cycle can be determined using the formulas: (SFN + PF_offset) mod T = (T div N) * (UE_ID mod N) and i_s = floor (UE_ID / N) mod Ns.

[0147] The UE may monitor additional POs during a DRX cycle, for example, if the UE determines that the gNB was unable to acquire a DL channel to transmit a paging DCI during a PO. The UE may use the methods described herein to determine whether the gNB has acquired a DL channel. The use of alternative methods that may be used to determine whether the gNB has acquired a DL channel (e.g., detection of a Discovery Reference Signal (DRS), a Channel Access Indication (CAI) signal, or any other signal transmitted by the gNB) is not excluded.

[0148] The embodiments include methods for monitoring the next PO. The UE can monitor the next PO associated with the PF, where the index of the next PO is i_s next_POThis can be calculated as = i_s + 1, where i_s < (Ns - 1). In scenarios where the monitored PO is the last PO associated with PF - i_s = (Ns - 1), the UE may stop monitoring additional POs during the DRX cycle. Alternatively, the UE may monitor the PO associated with the next PF, where the SFN of the next PF is SFN Next_PF = SFN PF It can be calculated as + floor(T / N).

[0149] The UE can monitor up to m POs during the DRX cycle, where the number m can be predefined or configured by the layers using broadcast or dedicated signaling. The UE can be configured to monitor more than one PO in the PF.

[0150] When the UE detects an LBT failure in a PO, if the UE can determine, using the methods described herein, whether the gNB has acquired a DL channel or any alternative method (e.g., detection of a Discovery Reference Signal (DRS), a CAI signal, or any other signal transmitted by the gNB), the UE may monitor up to a maximum of k consecutive POs following the first PO in which the UE detects an LBT failure within a DRX cycle. The UE may monitor additional POs, for example, until the UE detects an LBT success (or equivalently until there is no LBT failure) or until the UE monitors k consecutive POs following the first PO in which the UE detects an LBT failure without an LBT success. The monitored additional POs may belong to the same PF or to different PFs. The parameter k may be configured for the UE by the gNB or may be specified as a predefined value(s). The values ​​of parameter k may depend, for example, on service requirements and / or UE power saving settings / preferences.

[0151] In another alternative, when the UE detects an LBT failure in a PO, the UE may monitor up to a maximum of the next k additional POs following the first PO in which the UE detects the LBT failure within a DRX cycle. The additional monitored POs may be separated from each other in time by time intervals that can be expressed in terms of subframes and / or slots and / or mini-slots and / or symbols. The UE may monitor the additional POs, for example, until the UE detects an LBT success (or equivalently until there is no LBT failure) or until the UE has monitored k consecutive POs following the first PO in which the UE detects an LBT failure without an LBT success. The additional monitored POs may belong to the same PF or to different PFs. The parameter k may be configured for the UE by the gNB or may be specified as a fixed value(s). The values ​​of the parameter k may depend, for example, on service requirements and / or UE power saving settings / preferences. Similarly, the time interval between additional monitored POs can be configured for the UE by the gNB or specified by predefined value(s). The values ​​of the timer interval between additional monitored POs may depend, for example, on service requirements and / or UE power saving settings / preferences.

[0152] When the UE detects an LBT failure in a PDCCH monitoring opportunity within a PO, the UE may monitor up to a maximum of the following k consecutive additional PDCCH monitoring opportunities following the first PDCCH monitoring opportunity in which the UE detects the LBT failure within a DRX cycle, typically. The UE may monitor additional PDCCH opportunities, for example, until the UE detects an LBT success (or equivalently until there is no LBT failure) or until the UE monitors k consecutive PDCCH monitoring opportunities following the first PDCCH opportunity in which the UE detects an LBT failure without an LBT success. The additional consecutive PDCCH monitoring opportunities may belong to the same PO and / or the same PF, or to different POs and / or different PFs. Additionally, the additional consecutive PDCCH opportunities may be structured to be indexed as consecutive PDCCH opportunities in the time domain and / or frequency domain. The parameter k may be configured for the UE by the NB or may be specified as a predefined value(s). The values ​​of parameter k may depend, for example, on service requirements and / or UE power saving settings / preferences.

[0153] When the UE detects an LBT failure at a PDCCH monitoring opportunity within a PO, the UE may monitor up to the maximum of the next k PDCCH monitoring opportunities following the first PDCCH monitoring opportunity in which the UE detects the LBT failure within a DRX cycle, typically. The monitored PDCCH opportunities may be separated from each other by a time interval configurable in time and / or a configurable distance in the frequency domain. In the time domain, the distance between PDCCH monitoring opportunities may be expressed in terms of subframes and / or slots and / or mini-slots and / or symbols. The UE may monitor the PDCCH, for example, until the UE detects an LBT success (or equivalently until there is no LBT failure) or until the UE monitors k consecutive PDCCH monitoring opportunities following the first PDCCH monitoring opportunity in which the UE detects an LBT failure without an LBT success. The monitored PDCCH monitoring opportunities may belong to the same PO and / or the same PF, or to different POs and / or different PFs. Additionally, consecutive PDCCH opportunities can be structured to be indexed as consecutive PDCCH opportunities in the time domain and / or frequency domain. In this case, the distance between additional PDCCH monitoring opportunities within a DRX cycle can be expressed in terms of the difference between two additional PDCCH monitoring opportunities. Parameter k can be configured for the UE by the NB or specified as a fixed value(s). The values ​​of parameter k may depend, for example, on service requirements and / or UE power saving settings / preferences. Similarly, the time interval between additional monitored POs can be configured for the UE by the NB or specified as a predefined value(s). The values ​​of the timer interval between additional monitored POs may depend, for example, on service requirements and / or UE power saving settings / preferences.

[0154] During the PO, the UE can monitor POs configured for multiple paging BWPs, where a paging BWP is a BWP for which the UE can monitor PDCCH for paging. A common paging configuration may be used for each paging BWP. Alternatively, the configuration used for each paging BWP may be configured independently. In an embodiment, if the gNB acquires access to more than one paging BWP configured for a given UE during the PO, the gNB may page the UE on all paging BWPs for which access was acquired. The UE may then attempt to receive a paging DCI on any of the paging BWPs that the UE determines the gNB has access to. Alternatively, paging BWPs may be ranked, and if the gNB acquires access to more than one paging BWP configured for a given UE during the PO, the gNB may page the UE using the highest-ranked paging BWP. The UE may then attempt to receive the paging DCI on the highest-ranking paging BWP that the UE determines the gNB has access to. The same procedures may also be applied to scenarios where the DL channel can be partitioned into subbands, and the UE may monitor the POs configured for multiple paging subbands during the PO.

[0155] When determining the number of POs that a UE can monitor per DRX cycle, there may be a trade-off between paging reliability and UE power consumption. Increasing the number of POs monitored by the UE per DRX cycle can improve paging reliability but can also increase UE power consumption. Generally, to optimize power consumption, the UE may monitor subsequent POs only during the DRX cycle under specific conditions.

[0156] FIG. 12 is a flowchart of an exemplary algorithm (1200) capable of determining whether subsequent POs should be monitored according to one embodiment, which can be used in combination with any of the embodiments described herein. When the UE detects that the gNB could not obtain access to the DL channel for the transmission of the paging DCI, the UE may monitor subsequent POs only during the DRX cycle. In the example of FIG. 12, PO i is in the DRX cycle i It can respond to the nth monitored PO, and here i =1 could be the first monitored PO in the DRX cycle, and i =2 could be the second monitored PO in the DRX cycle, and the same applies to other things. In the DRX cycle i The th monitored PO is i = m In this case, it may not necessarily correspond to the (i_sm+1)th PO. Referring to Fig. 12, m is set to 1 (step 1201). UE PO m If CAI is detected during (step 1202), the UE PO m Monitors (step 1205). Otherwise, the UE m Increment (step 1203), m < Nm If (step 1204), repeat the process.

[0157] The same mechanism is also applicable to determine the number of PDCCH monitoring operations to monitor for modalities in which the PO consists of multiple sweeps / repetitions, e.g., extended POs.

[0158] In some configurations, paging capacity may not be sufficient to page all UEs that may need to be paged during a given PO. In this scenario, it may be desirable for the UE to monitor subsequent POs during the DRX cycle. To enable this behavior, in an embodiment, the gNB may provide the UE with an indication to signal that subsequent POs should be monitored when paging capacity was insufficient to page all UEs that may need to be paged during a given PO. In an embodiment, the paging DCI may include a field such as excess paging capacity, as shown in Table 10 below, to indicate that paging capacity was insufficient to page all UEs that may need to be paged during a PO.

[0159]

[0160]

[0161] FIG. 13 is a flowchart of an exemplary algorithm (1300) that can determine whether subsequent POs should be monitored according to one embodiment, which can be used in combination with any of the embodiments described herein. The exemplary algorithm (1300) of FIG. 13 can check whether the paging capacity has been exceeded for a PO and whether a UE ID is included in a paging message when determining whether a UE should monitor subsequent POs during a DRX cycle. Alternatively, this indication may be included as a field within a paging message signaled via RRC. PO i is in the DRX cycle i It can respond to the nth monitored PO, and here i =1 is the first monitored in the DRX cycle PO It could be, i =2 is the second monitored in the DRX cycle PO It could be, and the same applies to other things. In the DRX cycle i The ninth monitored PO Is i = m When (i_sm+1)th PO It may not necessarily correspond to. Referring to Fig. 13, m is set to 1 (step 1301). UE PO m If CAI is detected during (step 1302), the UE PO m Monitors (step 1305). Otherwise, the UE m Increment (step 1303), m < Nm (Step 1304) If this is the case, the process is repeated. The UE can determine whether a paging DCI is received (Step 1306). If a paging DCI is received, the UE can determine whether the paging capacity is exceeded (Step 1306). If the paging capacity is exceeded, the UE can determine whether the UE ID is in the paging message (Step 1308).

[0162] In the case of NR, PO may be a set of PDCCH monitoring operations, each corresponding to a fixed time instance (e.g., one or more OFDM symbols) within the PF where a paging DCI can be transmitted. If the gNB cannot acquire the DL channel prior to the start of the first PDCCH monitoring operation in the PO, the gNB may have to wait a full DRX cycle before attempting to page the UE again, even if the channel becomes idle immediately after the start of the PO, for example, after a few symbols following the start of the PO. To reduce the latency associated with paging the UE to the NR-U, in this embodiment, the PO may be defined to start at a flexible starting point within the paging monitoring window.

[0163] FIG. 14 is a drawing of an exemplary paging monitoring window (1400) according to one embodiment that may be used in combination with any of the embodiments described herein. The starting point of the PO (1404), i.e., the PO offset (1403), may be defined to occur at a flexible location (e.g., symbol / slot x) within the paging monitoring window (1402), wherein the maximum value of the PO offset (1403) may be specified or configured by upper layers using broadcast or dedicated signaling, for example, as a field included in the PCCH-Config IE.

[0164] In multi-beam operations, the length of a single PO can be defined as one or more periods of beam sweeping, and the UE can assume that the same paging message is repeated in all beams of the sweeping pattern. Then, the PO is It can be defined as a set of continuous PDCCH monitoring operations, where N SSB Is SystemInformationBlock1 Parameters in ssb-PositionsInBurst It may be the number of actual transmitted SSBs determined according to, and M n can be the number of sweeps used for paging transmissions. The Kth PDCCH monitoring account for paging in PO is ( K mod N SSB It can correspond to the )th transmitted SSB.

[0165] FIG. 15 is according to one embodiment which can be used in combination with any of the embodiments described herein. N SSB =3 and MFigure 15 is a drawing (1500) of an exemplary PO for a scenario in which =3. Figure 15 illustrates a PO (1501) comprising a plurality of sweeps, namely sweep 1 (1511), sweep 2 (1512), and sweep 3 (1513). Sweep 1 (1511) includes PDCCH MO0 (1520) sweeping beam 0 (1530), PDCCH MO1 (1521) sweeping beam 1 (1531), and PDCCH MO2 (1522) sweeping beam 2 (1532). Sweep 2 (1512) includes PDCCH MO3 (1523) sweeping beam 0 (1530), PDCCH MO4 (1524) sweeping beam 1 (1531), and PDCCH MO5 (1525) sweeping beam 2 (1532). Sweep 3 (1513) includes PDCCH MO6 (1526) sweeping beam 0 (1530), PDCCH MO7 (1527) sweeping beam 1 (1531), and PDCCH MO8 (1528) sweeping beam 2 (1532).

[0166] Alternatively, PO is It can be defined as a set of continuous PDCCH monitoring operations, where N SSB may be the actual number of transmitted SSBs determined by the parameter ssb-PositionsInBurst in SystemInformationBlock1, and R n can be the number of iterations used for paging transmissions. In this example, the Kth PDCCH monitoring account for paging in the PO is ( floor(K / R) It can correspond to the )th transmitted SSB.

[0167] FIG. 16 is according to one embodiment which can be used in combination with any of the embodiments described herein. N SSB =3 and R= This is a drawing (1600) of an exemplary PO for a 3-person scenario. FIG. 16 illustrates a PO (1601) comprising a plurality of MOs, namely PDCCH MO0 (1610) sweeping beam 0 (1620), PDCCH MO1 (1611) sweeping beam 0 (1620), and PDCCH MO2 (1612) sweeping beam 0 (1620), PDCCH MO3 (1613) sweeping beam 1 (1621), PDCCH MO4 (1614) sweeping beam 1 (1621), PDCCH MO5 (1615) sweeping beam 1 (1621), PDCCH MO6 (1616) sweeping beam 2 (1622), PDCCH MO7 (1617) sweeping beam 2 (1622), and PDCCH MO8 (1618) sweeping beam 2 (1622).

[0168] In another aspect, PO is It can be defined as a set of continuous PDCCH monitoring operations, where N SSB may be the actual number of transmitted SSBs determined by the parameter ssb-PositionsInBurst in SystemInformationBlock1, and R can be the number of iterations used for paging transfers, and M n can be the number of sweeps used for paging transmissions. In this example, the Kth PDCCH monitoring account for paging in the PO is ( It can correspond to the )th transmitted SSB.

[0169] FIG. 17 is according to one embodiment which can be used in combination with any of the embodiments described herein. N SSB =3, R =2 and MFigure 17 illustrates an exemplary PO (1700) for a scenario involving two people. Figure 17 illustrates a PO (1701) comprising a plurality of sweeps, namely sweep 1 (1711) and sweep 2 (1712). Sweep 1 (1711) includes PDCCH MO0 (1720) sweeping beam 0 (1740), PDCCH MO1 (1721) sweeping beam 0 (1740), PDCCH MO2 (1722) sweeping beam 1 (1741), PDCCH MO3 (1723) sweeping beam 1 (1741), PDCCH MO4 (1724) sweeping beam 2 (1742), and PDCCH MO5 (1725) sweeping beam 2 (1742). Sweep 2 (1712) is PDCCH MO6 (1726) sweeping beam 0 (1740), PDCCH MO7 (1727) sweeping beam 0 (1740), PDCCH MO8 (1728) sweeping beam 1 (1741), PDCCH MO9 (1729) sweeping beam 1 (1741), PDCCH MO 10 (1730) Sweeping beam 2 (1742), and PDCCH MO 11 (1731) Includes sweeping beam 2 (1742).

[0170] Parameters M and / or R may be signaled via higher layers, e.g., RRC. For example, the PCCH-Config field included in DownlinkConfigCommonSIB IE may be used to signal these parameters. The parameters may take continuous or discontinuous integer values. For illustrative purposes, a scenario in which parameters M and R may be set to values ​​such as 1, 2, 4, or 8 is considered herein. The parameters may be signaled using the PCCH-Config field defined as shown below. In this example, when parameters M and R are not explicitly signaled, a default value of 1 may be assumed. Support for extensions to other parameters signaled via IE, e.g., additional SCSs, Ns values, N values, PF offset values, etc., may also be performed in a manner similar to that exemplified below.

[0171]

[0172] In the above embodiments, SystemInformationBlock1 Parameters in ssb-PositionsInBurst The notation used to refer to the number of transmitted SSBs determined by is N SSB Instead, it may correspond to parameter S. This alternative notation is that PO for the aspects described herein ( S × M ), ( S × R ) or ( S × R × M ) Corresponds to what is defined as a set of continuous PDCCH monitoring operations.

[0173] A PO defined according to embodiments of methods for performing pagination using a PO composed of a plurality of sweeps / repetitions described in this specification may be referred to as an extended PO. For example, a PO ( S × MAn embodiment defined as a set of successive PDCCH monitoring operations is considered herein. Additional PDCCH monitoring operations including a PO for a scenario where M>1 can be viewed as extensions to the PO.

[0174] FIG. 18 is an example (1800) of monitoring extended POs according to one embodiment, which may be used in combination with any of the embodiments described herein. Referring to FIG. 18, a plurality of extended POs (1810, 1811, 1812, and 1813) are shown. UE1 (1801) can monitor PDCCH monitoring incidents during the extended PO (1810) and does not monitor during the extended POs (1811, 1812, and 1813). UE17 (1802) can monitor PDCCH monitoring incidents during the extended PO (1811) and does not monitor during the extended POs (1810, 1812, and 1813). UE33 (1803) can monitor PDCCH monitoring operations during the extended PO (1812) and does not monitor during the extended POs (1810, 1811, and 1813). UE49 (1804) can monitor PDCCH monitoring operations during the extended PO (1813) and does not monitor during the extended POs (1810, 1811, and 1812).

[0175] The K-th PDCCH monitoring account for paging in set m of POs corresponds to the K-th transmitted SSB, where m = 1, 2, ..., M is the m-th set of consecutive PDCCH monitoring operations in PO. This can also be referred to as the [(m-1)*S+K]-th PDCCH monitoring operation for paging in PO.

[0176] When the parameter firstPDCCH-MonitoringOccasionOfPO exists in a configuration provided by upper layers, e.g., PCCH-Config, the starting PDCCH monitoring occupation number of the (i_s+1)th PO is the (i_s+1)th value of the firstPDCCH-MonitoringOccasionOfPO parameter; otherwise, this is equal to i_s*S*M.

[0177] Table 11 shows the results of the i_s calculation of the extended PO for four different UEs and the (i_s+1)th PO starting PDCCH monitoring account number for the scenario T=32, N=16, Ns=4, M=2, and S=3. In this example, the SFN for the PF is the same for each UE, but each UE is distributed across different POs within the PF and thus monitors different sets of PDCCH monitoring accounts for paging as exemplified in Figure 18.

[0178] Table 11

[0179]

[0180] To optimize power consumption, if the UE determines that the gNB has acquired access to a channel during a monitored PDCCH occupation, the UE does not need to monitor subsequent PDCCH monitoring occupations corresponding to the same PO, whereby the UE may use any of the methods for signaling a DL channel access indication for paging as described herein.

[0181] For example, if a UE receives a PDCCH transmission with a CRC scrambled by P-RNTI in a PDCCH monitoring account for a PO, the UE can assume that the gNB was able to access the channel and therefore does not need to monitor subsequent PDCCH monitoring accounts corresponding to the same PO.

[0182] In the case of NR, the gNB may transmit paging DCI only when one or more UEs need to be paged during PO. If a UE fails to detect DCI format 1_0 with a CRC scrambled by P-RNTI during PO, the UE may assume that it was not paged and may enter DRX until the next PO. In an embodiment, in the case of NR-U, the gNB behavior may be modified so that paging DCI can be transmitted during all POs regardless of whether any UEs need to be paged during PO. If a UE fails to detect DCI format 1_0 with a CRC scrambled by P-RNTI during PO, the UE may assume that the gNB could not access the DL channel to transmit paging DCI, and the UE may adapt its behavior accordingly using the methods described herein. When a paging DCI is received by the UE during PO, the paging DCI can be processed according to its contents; if a short message exists within the DCI, it is read, and if scheduling information for paging exists within the DCI, the PDSCH carrying the paging message is decoded.

[0183] To handle a scenario where a paging DCI is transmitted but there are no paged UEs, the gNB may indicate that a short message exists within the DCI, and the bits of the short message field may be set to a predefined value indicating that no UEs have been paged, where the predefined value may be specified.

[0184] Alternatively, the short message indicator field may be defined as shown in Table 12 to represent this scenario. Also, in another alternative, the paging DCI may include a field to indicate whether any of the UEs have been paged, such as a paging indicator.

[0185] Table 12

[0186]

[0187] FIG. 19 is a flowchart for an exemplary procedure (1900) for signaling a DL CAI to paginate using a pagination DCI according to one embodiment, which may be used in combination with any of the embodiments described herein. In the example of FIG. 19, a gNB obtains access to a DL channel in a first attempt. Referring to FIG. 19, the gNB (1902) can perform an LBT on the DL and obtain access to the channel (step 1911). The gNB (1902) can transmit a pagination DCI during a PO using the mechanisms proposed herein to indicate that there are no UEs being paginated (step 1912). The UE (1901) can process the pagination DCI, determine that there are no UEs being paginated, and enter the DRX (step 1913). During a subsequent DRX cycle, the gNB (1902) can perform an LBT on the DL and acquire access to the channel (step 1914). The gNB (1902) can transmit a paging DCI during the PO using the mechanisms proposed herein to indicate that there is one or more UEs being paged (step 1915). The UE (1901) can process the paging DCI, determine that there is one or more UEs being paged, and prepare to receive a PDSCH carrying a paging message (step 1916). The gNB (1902) can transmit a paging message (step 1917). The UE (1901) can process the paging message and, if paged (i.e., if the paging message contains a paging record containing the UE's identity), (re)establish a connection with the network; otherwise, the UE enters the DRX (step 1918).

[0188] FIG. 20 is a flowchart for another exemplary procedure (2000) for signaling a DL CAI to paginate using a pagination DCI according to one embodiment, which may be used in combination with any of the embodiments described herein. In the example of FIG. 20, the gNB does not acquire access to the channel in the first attempt but acquires access to the DL channel in the second attempt. Referring to FIG. 20, the gNB (2002) performs an LBT on the DL but does not acquire access to the channel (step 2011). The gNB (2002) does not transmit the pagination DCI (step 2012). The UE (2001) fails to decode the pagination DCI and determines that the gNB could not access the DL channel for the transmission of the pagination DCI, where the UE can adapt its behavior for monitoring subsequent POs using the mechanisms described herein (step 2013). During the same DRX cycle, the gNB (2002) can perform an LBT on the DL and acquire access to the channel (step 2014). The gNB (2002) can transmit a paging DCI for a subsequent PO using the mechanisms proposed herein to indicate that there is one or more UEs being paged (step 2015). The UE (2001) can process the paging DCI, determine that there is one or more UEs being paged, and prepare to receive a PDSCH carrying a paging message (step 2016). The gNB (2002) can transmit a paging message (step 2018). The UE (2001) can process the paging message and, if paged (i.e., if the paging message contains a paging record containing the UE's identity), (re)establish a connection with the network; otherwise, the UE enters the DRX (step 2018).

[0189] In other alternatives, the UE may determine that the gNB has acquired access to the channel if, in any of the sets of search spaces monitored during PO, the UE receives a PDCCH or detects a signal transmitted by the gNB, such as a CAI signal, a demodulation reference signal (DMRS), etc.

[0190] In one embodiment, a DCI-based CAI may be used. A new DCI format consisting of parameters for indicating the Channel Occupancy Time (COT) as shown in Table 13 is defined and can be transmitted over a PDCCH masked with an RNTI, for example, a CAI-RNTI, which is used to indicate DL channel access.

[0191]

[0192]

[0193] In another embodiment, a discovery reference signal (DRS) transmitted by the gNB may be used to indicate that the gNB has acquired access to the channel. DRSs may be transmitted in symbols prior to the PO and may also include channel access information, such as the duration of the COT, the subbands where channel access was acquired, thereby allowing the UE to determine which PDCCH monitoring operations the gNB will access the channel during.

[0194] Before paging a UE for an NR-U, the gNB may perform an LBT. If the gNB is unable to acquire a channel during the configured PO for a given UE, the gNB may have to wait a full DRX cycle before attempting to page the UE again. In an embodiment, to reduce the latency associated with paging the UE when the gNB is unable to acquire a channel during the configured PO for a given UE, the DRX cycle may be dynamically reduced, so that the gNB may not have to wait a full DRX cycle before attempting to page the UE again. The reduced DRX cycle may remain valid for a given amount of time or until an event occurs, for example, until the gNB can acquire a channel for a number of consecutive POs. After that, the DRX cycle may be dynamically increased to the original value or an intermediate value, which may then remain valid for a given amount of time or until an event occurs.

[0195] 3GPP develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities, including research on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), and LTE-Advanced standards. 3GPP has initiated standardization work for next-generation cellular technology called New Radio (NR), also referred to as "5G." The development of 3GPP NR standards is expected to include the definition of next-generation radio access technology (new RAT), which is anticipated to include the provision of new flexible radio access below 6 GHz and new ultra-mobile broadband radio access above 6 GHz. Flexible radio access is expected to consist of new non-backwards compatible radio access in the new spectrum below 6 GHz, which is expected to include different modes of operation that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with diverging requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum to provide opportunities for ultra-mobile broadband access for, for example, indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with flexible radio access below 6 GHz by utilizing cmWave and mmWave-specific design optimizations.

[0196] 3GPP has identified various use cases expected to be supported by NR, which result in a wide range of user experience requirements for data rates, latency, and mobility. Use cases include the following general categories: enhanced mobile broadband (e.g., broadband access in dense areas, indoor ultra-high broadband access, broadband access in crowds, 50+ Mbps everywhere, ultra-low cost broadband access, mobile broadband in vehicles), critical communications, massive machine type communications, network operations (e.g., network slicing, routing, migration and interoperability, energy saving), and eV2X (enhanced vehicle-to-everything) communications, which may include any of V2V (Vehicle-to-Vehicle Communication), V2I (Vehicle-to-Infrastructure Communication), V2N (Vehicle-to-Network Communication), V2P (Vehicle-to-Pedestrian Communication), and vehicle communications with other entities. Specific services and applications in these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, vehicle erecall, disaster alerts, real-time games, multi-party video calls, autonomous driving, augmented reality, the Internet of Tactile Things, and virtual reality. All of these use cases and others are considered herein.

[0197] FIG. 21a illustrates an exemplary communication system (100) in which the methods and devices described and claimed in this specification may be implemented. As illustrated, an exemplary communication system (100) may include wireless transmit / receive units (WTRUs) (102a, 102b, 102c, 102d, 102e, 102f and / or 102g) (which may be generally or collectively referred to as WTRU (102)), a radio access network (RAN) (103 / 104 / 105 / 103b / 104b / 105b), a core network (106 / 107 / 109), a public switched telephone network (PSTN) (108), the Internet (110), other networks (112), and a V2X server (or ProSe function and server) (113), but it will be understood that the disclosed embodiments consider any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs (102a, 102b, 102c, 102d, 102e, 102f, 102g) may be any type of device or apparatus configured to operate and / or communicate in a wireless environment.It is understood that each WTRU (102a, 102b, 102c, 102d, 102e, 102f, 102g) is illustrated as a hand-held wireless communication device in FIG. 21a through 21e, but for a wide range of use cases considered for 5G wireless communications, each WTRU may include, or be implemented as any type of device or device configured to transmit and / or receive wireless signals, including, only examples, user equipment (UE), mobile station, fixed or mobile subscriber unit, pager, cellular phone, personal digital assistant (PDA), smartphone, laptop, tablet, netbook, notebook computer, personal computer, wireless sensor, consumer electronics, wearable device such as smart watch or smart clothing, medical or eHealth device, robot, industrial equipment, drone, vehicle such as passenger car, truck, train, or airplane.

[0198] The communication system (100) may also include a base station (114a) and a base station (114b). The base stations (114a) may be any type of device configured to wirelessly interface with at least one of the WTRUs (102a, 102b, 102c) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), and / or other networks (112). Base stations (114b) may be any type of device configured to interface wired and / or wirelessly with at least one of Remote Radio Heads (RRHs) (118a, 118b), Transmission and Reception Points (TRPs) (119a, 119b) and / or Roadside Units (RSUs) (120a, 120b) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), other networks (112) and / or a V2X server (or ProSe function and server) (113). RRHs (118a, 118b) may be any type of device configured to wirelessly interface with at least one of WTRUs (102c) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), and / or other networks (112). TRPs (119a, 119b) may be any type of device configured to wirelessly interface with at least one of WTRUs (102d) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), and / or other networks (112).The RSUs (120a and 120b) may be any type of device configured to wirelessly interface with at least one of the WTRUs (102e or 102f) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), other networks (112) and / or a V2X server (or ProSe function and server) (113). For example, the base stations (114a, 114b) may be a base transceiver station (BTS), Node-B, eNode B, Home Node B, Home eNode B, site controller, access point (AP), wireless router, etc. Although the base stations (114a, 114b) are each depicted as a single element, it will be well known that the base stations (114a, 114b) may include any number of interconnected base stations and / or network elements.

[0199] A base station (114a) may be part of a RAN (103 / 104 / 105), which may also include other base stations and / or network elements (not shown), such as a base station controller (BSC), a radio network controller (RNC), relay nodes, etc. A base station (114b) may be part of a RAN (103b / 104b / 105b), which may also include other base stations and / or network elements (not shown), such as a BSC, RNC, relay nodes, etc. A base station (114a) may be configured to transmit and / or receive radio signals within a specific geographical area that may be referred to as a cell (not shown). A base station (114b) may be configured to transmit and / or receive wired and / or radio signals within a specific geographical area that may be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, a cell associated with a base station (114a) may be divided into three sectors. Accordingly, in an embodiment, the base station (114a) may include three transceivers, for example, one for each sector of the cell. In an embodiment, the base station (114a) may utilize multiple-input multiple-output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell.

[0200] Base stations (114a) can communicate with one or more of WTRUs (102a, 102b, 102c) via an air interface (115 / 116 / 117) which may be any suitable radio communication link (e.g., RF (radio frequency), microwave, IR (infrared), UV (ultraviolet), visible light, cmWave, mmWave, etc.). The air interface (115 / 116 / 117) may be established using any suitable radio access technology (RAT).

[0201] Base stations (114b) may communicate with one or more of RRHs (118a, 118b), TRPs (119a, 119b) and / or RSUs (120a, 120b) via a wired or air interface (115b / 116b / 117b), which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface (115b / 116b / 117b) may be established using any suitable RAT.

[0202] The RRHs (118a, 118b), TRPs (119a, 119b) and / or RSUs (120a, 120b) may communicate with one or more of the WTRUs (102c, 102d, 102e, 102f) via an air interface (115c / 116c / 117c), which may be any suitable radio communication link (e.g., RF (radio frequency), microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface (115c / 116c / 117c) may be established using any suitable RAT.

[0203] The WTRUs (102a, 102b, 102c, 102d, 102e, 102f and / or 102g) can communicate with each other via an air interface (115d / 116d / 117d) (not shown in the drawings), which may be any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface (115d / 116d / 117d) may be established using any suitable RAT.

[0204] More specifically, as previously discussed, the communication system (100) may be a multiple access system and may use one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations (114a) and WTRUs (102a, 102b, 102c) in RAN (103 / 104 / 105), or RRHs (118a, 118b), TRPs (119a, 119b), and RSUs (120a, 120b) and WTRUs (102c, 102d, 102e, 102f) in RAN (103b / 104b / 105b) can implement radio technology such as UTRA (UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access), which can establish air interfaces (115 / 116 / 117 or 115c / 116c / 117c) respectively using WCDMA (wideband CDMA). WCDMA may include communication protocols such as HSPA (High-Speed ​​Packet Access) and / or HSPA+ (Evolved HSPA). HSPA may include HSDPA (High-Speed ​​Downlink Packet Access) and / or HSUPA (High-Speed ​​Uplink Packet Access).

[0205] In an embodiment, the base station (114a) and WTRUs (102a, 102b, 102c), or RRHs (118a, 118b), TRPs (119a, 119b) and / or RSUs (120a, 120b) and WTRUs (102c, 102d) in the RAN (103b / 104b / 105b) may implement radio technology such as E-UTRA (Evolved UMTS Terrestrial Radio Access), which can establish air interfaces (115 / 116 / 117 or 115c / 116c / 117c) respectively using LTE (Long Term Evolution) and / or LTE-A (LTE-Advanced). In the future, the air interfaces (115 / 116 / 117) may implement 3GPP NR technology. LTE and LTE-A technologies include LTE D2D and V2X technologies and interfaces (such as sidelink communication). 3GPP NR technologies include NR V2X technologies and interfaces (such as sidelink communication).

[0206] In an embodiment, the base station (114a) and WTRUs (102a, 102b, 102c) in the RAN (103 / 104 / 105), or RRHs (118a, 118b), TRPs (119a, 119b) and / or RSUs (120a, 120b) and WTRUs (102c, 102d, 102e, 102f) in the RAN (103b / 104b / 105b) are IEEE 802.16 (e.g., WiMAX (Worldwide Interoperability for Microwave Access)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, IS-2000 (Interim Standard 2000), IS-95 (Interim Standard 95), IS-856 (Interim Standard 856), Radio technologies such as GSM (Global System for Mobile communications), EDGE (Enhanced Data rates for GSM Evolution), and GERAN (GSM EDGE) can be implemented.

[0207] The base station (114c) in FIG. 21a may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and may utilize any suitable RAT to facilitate wireless connectivity in a localized area such as a place of use, a home, a vehicle, a campus, etc. In an embodiment, the base station (114c) and WTRUs (102e) may implement radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). In an embodiment, the base station (114c) and WTRUs (102d) may implement radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another embodiment, the base station (114c) and WTRUs (102e) may use a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell. As illustrated in FIG. 21a, the base station (114b) may have direct access to the Internet (110). Thus, the base station (114c) may not be required to access the Internet (110) through the core network (106 / 107 / 109).

[0208] The RAN (103 / 104 / 105) and / or RAN (103b / 104b / 105b) may communicate with a core network (106 / 107 / 109), which may be any type of network configured to provide voice, data, applications, and VoIP (voice over internet protocol) services to one or more of the WTRUs (102a, 102b, 102c, 102d). For example, the core network (106 / 107 / 109) may provide call control, billing services, mobile location-based services, prepaid calling, internet access, video distribution, etc., and / or perform high-level security functions such as user authentication.

[0209] Although not illustrated in FIG. 21a, it will be understood that the RAN (103 / 104 / 105) and / or RAN (103b / 104b / 105b) and / or core network (106 / 107 / 109) may communicate directly or indirectly with other RANs using the same RAT or different RAT as the RAN (103 / 104 / 105) and / or RAN (103b / 104b / 105b). For example, in addition to being connected to the RAN (103 / 104 / 105) and / or RAN (103b / 104b / 105b) which can use E-UTRA radio technology, the core network (106 / 107 / 109) may also communicate with other RANs (not illustrated) which use GSM radio technology.

[0210] The core network (106 / 107 / 109) may also serve as a gateway for WTRUs (102a, 102b, 102c, 102d, 102e) to access the PSTN (108), the Internet (110), and / or other networks (112). The PSTN (108) may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet (110) may include a global system of interconnected computer networks and devices that utilize common communication protocols such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Protocol (IP) in the TCP / IP Internet protocol set. The networks (112) may include wired or wireless communication networks owned and / or operated by other service providers. For example, networks (112) may include other core networks connected to one or more RANs that can use the same RAT or a different RAT as RAN (103 / 104 / 105) and / or RAN (103b / 104b / 105b).

[0211] Some or all of the WTRUs (102a, 102b, 102c, 102d) in the communication system (100) may include multi-mode capabilities, and for example, the WTRUs (102a, 102b, 102c, 102d and 102e) may include multiple transceivers for communicating with different wireless networks through different wireless links. For example, the WTRU (102e) illustrated in FIG. 21a may be configured to communicate with a base station (114a) capable of using cellular-based radio technology and to communicate with a base station (114c) capable of using IEEE 802 radio technology.

[0212] FIG. 21b is a block diagram of an exemplary device or apparatus configured for wireless communications according to the embodiments illustrated herein, such as, for example, a WTRU (102). As illustrated in FIG. 21b, the exemplary WTRU (102) may include a processor (118), a transceiver (120), a transmission / reception element (122), a speaker / microphone (124), a keypad (126), a display / touchpad / indicator (128), non-removable memory (130), removable memory (132), a power supply (134), a GPS (global positioning system) chipset (136), and other peripherals (138). It will be understood that, while remaining consistent with the embodiments, the WTRU (102) may include any subcombination of the aforementioned elements. Additionally, embodiments take into account that a node comprising, among other things that the base station (114a and 114b) and / or base station (114a and 114b) may represent, but is not limited to, a transceiver station (BTS), Node-B, site controller, access point (AP), home node-B, evolved home node-B (eNodeB), home evolved node-B (HeNB), home evolved node-B gateway, and proxy node may include some or all of the elements illustrated in FIG. 21b and described herein.

[0213] The processor (118) may be a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) circuit, any other type of integrated circuit (IC), a state machine, etc. The processor (118) may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable the WTRU (102) to operate in a wireless environment. The processor (118) may be coupled to a transceiver (120), and the transceiver (120) may be coupled to a transmission / reception element (122). FIG. 21b illustrates the processor (118) and transceiver (120) as separate components, but it will be understood that the processor (118) and transceiver (120) may be integrated together in an electronic package or chip.

[0214] The transmission / reception element (122) may be configured to transmit a signal to a base station (e.g., base station (114a)) or receive a signal therefrom through an air interface (115 / 116 / 117). For example, in an embodiment, the transmission / reception element (122) may be an antenna configured to transmit and / or receive RF signals. In an embodiment, the transmission / reception element (122) may be an emitter / detector configured to transmit and / or receive IR, UV, or visible light signals, for example. In another embodiment, the transmission / reception element (122) may be configured to transmit and receive both RF and optical signals. It will be understood that the transmission / reception element (122) may be configured to transmit and / or receive any combination of wireless signals.

[0215] Additionally, although the transmission / reception element (122) is illustrated as a single element in FIG. 21b, the WTRU (102) may include any number of transmission / reception elements (122). More specifically, the WTRU (102) may utilize MIMO technology. Accordingly, in an embodiment, the WTRU (102) may include two or more transmission / reception elements (122) (e.g., multiple antennas) for transmitting and receiving wireless signals through the air interface (115 / 116 / 117).

[0216] The transceiver (120) may be configured to modulate signals to be transmitted by the transmitting / receiving element (122) and to demodulate signals received by the transmitting / receiving element (122). As previously discussed, the WTRU (102) may have multimode capabilities. Accordingly, the transceiver (120) may include multiple transceivers that enable the WTRU (102) to communicate through multiple RATs, such as UTRA and IEEE 802.11.

[0217] The processor (118) of the WTRU (102) may be coupled to a speaker / microphone (124), a keypad (126), and / or displays / touchpads / indicators (128) (e.g., a liquid crystal display (LCD) display unit or an organic light emitting diode (OLED) display unit) and may receive user input data from them. The processor (118) may also output user data to the speaker / microphone (124), the keypad (126), and / or displays / touchpads / indicators (128). Additionally, the processor (118) may access information from any type of suitable memory, such as non-removable memory (130) and / or removable memory (132), and store data therein. Non-removable memory (130) may include random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory (132) may include a SIM (subscriber identity module) card, a memory stick, an SD (secure digital) memory card, etc. In an embodiment, the processor (118) may access information from memory that is not physically located on the WTRU (102), such as on a server or home computer (not shown), and store data therein.

[0218] The processor (118) may receive power from the power source (134) and may be configured to distribute and / or control power to other components in the WTRU (102). The power source (134) may be any suitable device for supplying power to the WTRU (102). For example, the power source (134) may include one or more dry cell batteries, solar cells, fuel cells, etc.

[0219] The processor (118) may also be coupled to a GPS chipset (136) which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU (102). In addition to or instead of information from the GPS chipset (136), the WTRU (102) may receive location information from a base station (e.g., base stations (114a, 114b)) via an air interface (115 / 116 / 117) and / or determine its location based on the timing of signals received from two or more nearby base stations. It will be understood that the WTRU (102) may obtain location information by any suitable location determination method while remaining consistent with the embodiment.

[0220] The processor (118) may be further coupled to other peripherals (138), which may include one or more software and / or hardware modules that provide additional features, functions and / or wired or wireless connectivity. For example, the peripherals (138) may include various sensors such as accelerometers, biometric (e.g., fingerprint) sensors, electronic compasses (e-compass), satellite transceivers, digital cameras (for photos or videos), USB (universal serial bus) ports or other interconnection interfaces, vibration devices, television transceivers, hands-free headsets, Bluetooth® modules, frequency modulation (FM) radio units, digital music players, media players, video game player modules, internet browsers, etc.

[0221] The WTRU (102) may be implemented in other devices or devices such as sensors, consumer electronics, wearable devices such as smartwatches or smart clothing, medical or eHealth devices, robots, industrial equipment, drones, automobiles, trucks, trains or airplanes. The WTRU (102) may be connected to other components, modules, or systems of such devices or devices through one or more interconnection interfaces, such as an interconnection interface that may include one of the peripheral devices (138).

[0222] FIG. 21c is a system diagram of a RAN (103) and a core network (106) according to an embodiment. As previously discussed, the RAN (103) may use UTRA radio technology to communicate with WTRUs (102a, 102b, and 102c) through an air interface (115). The RAN (103) may also communicate with the core network (106). As illustrated in FIG. 21c, the RAN (103) may include Node-Bs (140a, 140b, 140c), each of which may include one or more transceivers for communicating with WTRUs (102a, 102b, 102c) through an air interface (115). Node-Bs (140a, 140b, 140c) may each be associated with a specific cell (not shown) within the RAN (103). The RAN (103) may also include RNCs (142a, 142b). It will be understood that the RAN (103) may include any number of Node-Bs and RNCs while remaining consistent with the embodiment.

[0223] As illustrated in FIG. 21c, Node-Bs (140a, 140b) can communicate with RNC (142a). Additionally, Node-B (140c) can communicate with RNC (142b). Node-Bs (140a, 140b, 140c) can communicate with individual RNCs (142a, 142b) via an Iub interface. RNCs (142a, 142b) can communicate with each other via an Iur interface. Each of the RNCs (142a, 142b) can be configured to control individual Node-Bs (140a, 140b, 140c) connected to it. Additionally, each of the RNCs (142a, 142b) may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro-diversity, security functions, data encryption, etc.

[0224] The core network (106) illustrated in FIG. 21c may include a media gateway (MGW) (144), a mobile switching center (MSC) (146), a serving GPRS support node (SGSN) (148), and / or a gateway GPRS support node (GGSN) (150). Although each of the aforementioned elements is illustrated as part of the core network (106), it will be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0225] The RNC (142a) in the RAN (103) can be connected to the MSC (146) in the core network (106) via an IuCS interface. The MSC (146) can be connected to the MGW (144). The MSC (146) and the MGW (144) can provide the WTRUs (102a, 102b, 102c) with access to circuit-switched networks, such as the PSTN (108), to facilitate communication between the WTRUs (102a, 102b, 102c) and traditional land-line communication devices.

[0226] The RNC (142a) in the RAN (103) can also be connected to the SGSN (148) in the core network (106) via an IuPS interface. The SGSN (148) can be connected to the GGSN (150). The SGSN (148) and the GGSN (150) can provide the WTRUs (102a, 102b, 102c) with access to packet-switched networks, such as the Internet (110), to facilitate communication between the WTRUs (102a, 102b, 102c) and IP-enabled devices.

[0227] As previously discussed, the core network (106) may also be connected to networks (112) that may include other wired or wireless networks owned and / or operated by other service providers.

[0228] FIG. 21d is a system diagram of a RAN (104) and a core network (107) according to an embodiment. As previously discussed, the RAN (104) may use E-UTRA radio technology to communicate with WTRUs (102a, 102b, and 102c) through an air interface (116). The RAN (104) may also communicate with the core network (107).

[0229] The RAN (104) may include eNode-Bs (160a, 160b, 160c), but it will be understood that the RAN (104) may include any number of eNode-Bs while remaining consistent with the embodiment. Each of the eNode-Bs (160a, 160b, 160c) may include one or more transceivers to communicate with the WTRUs (102a, 102b, 102c) via the air interface (116). In the embodiment, the eNode-Bs (160a, 160b, 160c) may implement MIMO technology. Thus, for example, the eNode-B (160a) may use multiple antennas to transmit radio signals to the WTRU (102a) and receive radio signals from it.

[0230] Each of the eNode-Bs (160a, 160b, and 160c) may be associated with a specific cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users on the uplink and / or downlink, etc. As shown in FIG. 21d, the eNode-Bs (160a, 160b, 160c) may communicate with each other via an X2 interface.

[0231] The core network (107) illustrated in FIG. 21d may include a mobility management gateway (MME) (162), a serving gateway (164), and a packet data network (PDN) gateway (166). Although each of the aforementioned elements is illustrated as part of the core network (107), it will be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0232] The MME (162) can be connected to each of the eNode-Bs (160a, 160b, and 160c) in the RAN (104) via the S1 interface and can act as a control node. For example, the MME (162) can be responsible for authenticating users of the WTRUs (102a, 102b, 102c), enabling / disabling bearers, and selecting a specific serving gateway during the initial attach of the WTRUs (102a, 102b, 102c). The MME (162) can also provide control plane functions for switching between the RAN (104) and other RANs (not shown) using other radio technologies such as GSM or WCDMA.

[0233] The serving gateway (164) can be connected to each of the eNode-Bs (160a, 160b, and 160c) in the RAN (104) via the S1 interface. The serving gateway (164) can generally route and forward user data packets to and from the WTRUs (102a, 102b, 102c). The serving gateway (164) can also perform other functions such as anchoring user planes during inter-eNode B handovers, triggering paging when downlink data is available for the WTRUs (102a, 102b, 102c), and managing and storing the contexts of the WTRUs (102a, 102b, 102c).

[0234] The serving gateway (164) may also be connected to a PDN gateway (166) that can provide access to packet-switched networks, such as the Internet (110), to the WTRUs (102a, 102b, 102c) to facilitate communication between the WTRUs (102a, 102b, 102c) and IP-enabled devices.

[0235] The core network (107) can facilitate communication with other networks. For example, the core network (107) can provide the WTRUs (102a, 102b, 102c) with access to circuit-switched networks, such as the PSTN (108), to facilitate communication between the WTRUs (102a, 102b, 102c) and traditional ground communication devices. For example, the core network (107) may include an IP gateway (e.g., an IMS (IP multimedia subsystem) server) serving as an interface between the core network (107) and the PSTN (108), or may communicate with this IP gateway. Additionally, the core network (107) can provide the WTRUs (102a, 102b, 102c) with access to networks (112), which may include other wired or wireless networks owned and / or operated by other service providers.

[0236] FIG. 21e is a system diagram of a RAN (105) and a core network (109) according to an embodiment. The RAN (105) may be an access service network (ASN) that uses IEEE 802.16 radio technology to communicate with WTRUs (102a, 102b, and 102c) through an air interface (117). As further discussed below, communication links between different functional entities of the WTRUs (102a, 102b, 102c), the RAN (105), and the core network (109) may be defined as reference points.

[0237] As illustrated in FIG. 21e, the RAN (105) may include base stations (180a, 180b, 180c) and an ASN gateway (182), but it will be understood that the RAN (105) may include any number of base stations and ASN gateways while remaining consistent with the embodiment. Each of the base stations (180a, 180b, 180c) may be associated with a specific cell in the RAN (105) and may include one or more transceivers for communicating with WTRUs (102a, 102b, 102c) via an air interface (117). In the embodiment, the base stations (180a, 180b, 180c) may implement MIMO technology. Thus, for example, a base station (180a) may use multiple antennas to transmit radio signals to and from the WTRU (102a). Base stations (180a, 180b, 180c) can also provide mobility management functions such as handoff triggering, tunnel establishment, radio resource management, traffic classification, and quality of service (QoS) policy enforcement. The ASN gateway (182) can serve as a traffic aggregation point and can handle paging, caching of subscriber profiles, routing to the core network (109).

[0238] The air interface (117) between the WTRUs (102a, 102b, 102c) and the RAN (105) can be defined as an R1 reference point implementing the IEEE 802.16 specification. Additionally, each of the WTRUs (102a, 102b, 102c) can establish a logical interface (not shown) with the core network (109). The logical interface between the WTRUs (102a, 102b, 102c) and the core network (109) can be defined as an R2 reference point that can be used for authentication, authorization, IP host configuration management, and / or mobility management.

[0239] A communication link between each of the base stations (180a, 180b, and 180c) may be defined as an R8 reference point that includes protocols to facilitate WTRU handovers and data transmission between the base stations. A communication link between the base stations (180a, 180b, 180c) and the ASN gateway (182) may be defined as an R6 reference point. The R6 reference point may include protocols to facilitate mobility management based on mobility events associated with each of the WTRUs (102a, 102b, 102c).

[0240] As illustrated in FIG. 21e, the RAN (105) may be connected to the core network (109). The communication link between the RAN (105) and the core network (109) may be defined, for example, as an R3 reference point including protocols to facilitate data transmission and mobility management capabilities. The core network (109) may include a MIP-HA (mobile IP home agent) (184), an AAA (authentication, authorization, accounting) server (186), and a gateway (188). Although each of the aforementioned elements is illustrated as part of the core network (109), it will be understood that any of these elements may be owned and / or operated by an entity other than the core network operator.

[0241] The MIP-HA can manage IP addresses and enable WTRUs (102a, 102b, and 102c) to roam between different ASNs and / or different core networks. The MIP-HA (184) can provide WTRUs (102a, 102b, 102c) with access to packet-switched networks, such as the Internet (110), to facilitate communication between WTRUs (102a, 102b, 102c) and IP-enabled devices. The AAA server (186) can be responsible for user authentication and user service support. The gateway (188) can facilitate interworking with other networks. For example, the gateway (188) may provide the WTRUs (102a, 102b, 102c) with access to circuit-switched networks, such as the PSTN (108), to facilitate communication between the WTRUs (102a, 102b, 102c) and traditional ground communication devices. Additionally, the gateway (188) may provide the WTRUs (102a, 102b, 102c) with access to networks (112), which may include other wired or wireless networks owned and / or operated by other service providers.

[0242] Although not illustrated in FIG. 21e, it will be understood that the RAN (105) may be connected to other ASNs, and the core network (109) may be connected to other core networks. A communication link between the RAN (105) and other ASNs may be defined as an R4 reference point that may include protocols for coordinating the mobility of WTRUs (102a, 102b, 102c) between the RAN (105) and other ASNs. A communication link between the core network (109) and other core networks may be defined as an R5 reference point that may include protocols for facilitating interoperability between home core networks and visited core networks.

[0243] It is understood that the core network entities described herein and illustrated in FIGS. 21a, 21c, 21d, and 21e are identified by the names given to those entities in any existing 3GPP specifications, but in the future, those entities and functions may be identified by other names, and that some entities or functions may be combined in future specifications published by 3GPP, including future 3GPP NR specifications. Accordingly, the specific network entities and functions illustrated and described in FIGS. 21a, 21b, 21c, 21d, and 21e are provided merely as examples, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether currently defined or in the future.

[0244] FIG. 21f is a block diagram of an exemplary computing system (90) in which one or more devices of the communication networks illustrated in FIG. 21a, FIG. 21c, FIG. 21d, and FIG. 21e, such as specific nodes or functional entities in a RAN (103 / 104 / 105), a core network (106 / 107 / 109), a PSTN (108), the Internet (110), or other networks (112), may be implemented. The computing system (90) may include a computer or a server and may be controlled primarily by computer-readable instructions, which may be in the form of software, wherever such software is stored or accessed, or any means. Such computer-readable instructions may be executed within a processor (91) to cause the computing system (90) to perform a task. The processor (91) may be a general-purpose processor, a special-purpose processor, a conventional processor, a DSP, a plurality of microprocessors, one or more microprocessors associated with a DSP core, a controller, a microcontroller, ASICs, FPGA circuits, any other type of IC, a state machine, etc. The processor (91) may perform signal coding, data processing, power control, input / output processing, and / or any other functions that enable the computing system (90) to operate in a communication network. The coprocessor (81) is an optional processor distinct from the main processor (91) that may perform additional functions or assist the processor (91). The processor (91) and / or the coprocessor (81) may receive, generate, and process data related to the methods and devices disclosed herein.

[0245] During operation, the processor (91) fetches, decodes, and executes instructions and transmits information to and from other resources through a system bus (80), which is the main data transmission path of the computing system. Such a system bus connects components in the computing system (90) and defines a medium for data exchange. The system bus (80) typically includes data lines for transmitting data, address lines for transmitting addresses, and control lines for transmitting interrupts and operating the system bus. An example of such a system bus (80) is a PCI (Peripheral Component Interconnect) bus.

[0246] Memories coupled to the system bus (80) include RAM (82) and ROM (93). Such memories include circuitry that enables information to be stored and retrieved. ROMs (93) generally contain stored data that cannot be easily modified. Data stored in RAM (82) can be read or modified by the processor (91) or other hardware devices. Access to RAM (82) and / or ROM (93) can be controlled by a memory controller (92). The memory controller (92) can provide an address translation function that converts virtual addresses into physical addresses when instructions are executed. The memory controller (92) can also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in the first mode can only access memory mapped by its own process virtual address space; and the program cannot access memory in another process's virtual address space unless memory sharing between processes is established.

[0247] Additionally, the computing system (90) may include a peripheral device controller (83) responsible for communicating instructions from the processor (91) to peripheral devices such as a printer (94), keyboard (84), mouse (95), and disk drive (85).

[0248] A display (86) controlled by a display controller (96) is used to display visual output generated by a computing system (90). Such visual output may include text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). The display (86) may be implemented as a CRT-based video display, an LCD-based flat panel display, a gas plasma-based flat panel display, or a touch panel. The display controller (96) includes electronic components required to generate a video signal transmitted to the display (86).

[0249] Furthermore, the computing system (90) may include a communication circuit, such as a network adapter (97), which can be used to connect the computing system (90) to an external communication network, such as the RAN (103 / 104 / 105), core network (106 / 107 / 109), PSTN (108), the Internet (110), or other networks (112) of FIG. 21a, FIG. 21b, FIG. 21c, FIG. 21d and FIG. 21e, so that the computing system (90) can communicate with other nodes or functional entities of the networks. The communication circuit may be used, alone or in combination with the processor (91), to perform the transmission and reception steps of the specific devices, nodes, or functional entities described herein.

[0250] FIG. 21g illustrates an exemplary communication system (111) in which the methods and apparatuses described and claimed herein may be implemented. As illustrated, the exemplary communication system (111) may include wireless transmission / reception units (WTRUs) A, B, C, D, E, F, a base station, a V2X server, and RSUs A and B, but it will be understood that the disclosed embodiments consider any number of WTRUs, base stations, networks, and / or network elements. One or several or all of WTRUs A, B, C, D, E may be outside the range of the network (e.g., outside the cell coverage boundary shown by dashed lines in the drawing). WTRUs A, B, C form a V2X group, wherein WTRU A is the group leader and WTRUs B and C are group members. WTRUs A, B, C, D, E, F may communicate through a Uu interface or a sidelink (PC5) interface.

[0251] Any or all of the devices, systems, methods, and processes described herein may be implemented in the form of computer-executable instructions (i.e., program code) stored on a computer-readable storage medium, and it is understood that when executed by a processor such as a processor (118 or 91), the processor enables the system, methods, and processes described herein to perform and / or implement. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer-executable instructions executed on a processor of a device or computing system configured for wireless and / or wired network communications. A computer-readable storage medium includes volatile and non-volatile, removable and non-removable media implemented by any non-transient (e.g., tangible or physical) method or technique for storing information, but such a computer-readable storage medium does not include signals. Computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, DVD (digital versatile disks) or other optical disc storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other type of physical medium that can be used to store desired information and can be accessed by a computing system.

Claims

Claim 1 A WTRU comprising a wireless transmission / reception unit (WTRU), a processor, memory, and communication circuits, wherein the WTRU is connected to a network through the communication circuits, and wherein the WTRU receives a signal associated with unlicensed spectrum—wherein the signal is associated with a plurality of paging occasions, and each of the plurality of paging occasions includes a plurality of physical downlink control channel (PDCCH) monitoring occasions—; monitor a portion of the plurality of paging occasions based on the reception of an identifier associated with the WTRU; and to detect paging downlink control information (DCI) in a PDCCH monitoring occasion among the plurality of PDCCH monitoring occasions in the monitored portion—wherein the paging DCI includes a short message, and the short message indicates that the WTRU may stop monitoring subsequent PDCCH monitoring occasions in the portion of the plurality of paging occasions associated with the unlicensed spectrum. Claim 2 In claim 1, the plurality of PDCCH monitoring operations are WTRUs, which are continuous PDCCH monitoring operations. Claim 3 In paragraph 2, the continuous PDCCH monitoring accounts correspond to the amount of transmitted synchronization signal blocks (SSBs) and the amount of sweeps used for paging transmissions, WTRU. Claim 4 WTRU according to paragraph 2, wherein the monitoring comprises monitoring at least one second PDCCH monitoring account among the plurality of PDCCH monitoring accounts during a discontinuous receive (DRX) cycle based on a determination that the gNB could not acquire a downlink channel for transmitting the paging DCI during the portion. Claim 5 In paragraph 3, the amount of the transmitted SSBs is a WTRU composed of parameters included in a system information block (SIB). Claim 6 In paragraph 3, the Kth PDCCH monitoring account in the set m of the plurality of PDCCH monitoring accounts among the plurality of paging accounts is a WTRU corresponding to the Kth transmitted SSB. Claim 7 In paragraph 1, the WTRU that is being monitored is during a discontinuous reception (DRX) cycle. Claim 8 In claim 7, the monitored portion comprises a single paging arcade among the plurality of paging arcades during the DRX cycle, WTRU. Claim 9 In claim 7, the monitored portion comprises a plurality of paging arcades among the plurality of paging arcades during the DRX cycle, WTRU. Claim 10 In paragraph 9, the plurality of paging accounts are multiplexed in time, WTRU. Claim 11 In paragraph 9, the plurality of phasing occupations are WTRUs that are multiplexed at frequency. Claim 12 In claim 9, the plurality of paging accounts are WTRUs that are multiplexed in time and frequency. Claim 13 In claim 1, the plurality of PDCCH monitoring occupations are WTRUs that are continuous PDCCH monitoring occupations over time. Claim 14 In claim 1, the plurality of PDCCH monitoring occupations are PDCCH monitoring occupations that are discontinuous with respect to time, WTRU. Claim 15 In paragraph 1, the monitoring is a WTRU in one or more paging subbands of the received signal. Claim 16 In claim 1, the plurality of PDCCH monitoring occupations is associated with one or more repetitions of the transmission of the paging DCI by the gNB, WTRU. Claim 17 WTRU according to claim 1, further configured to detect a failure by gNB to acquire a downlink channel for transmitting the paging DCI during the portion, wherein the portion comprises only the PDCCH monitoring accounts among the plurality of PDCCH monitoring accounts following the failure. Claim 18 In paragraph 17, the WTRU is further configured to monitor up to the maximum of the next k consecutive additional PDCCH monitoring accounts among the plurality of PDCCH monitoring accounts after an LBT failure during a discontinuous receive (DRX) cycle. Claim 19 A method performed by a wireless transmission / reception unit (WTRU), comprising: receiving a signal associated with unlicensed spectrum—the signal being associated with a plurality of paging accounts, each of which paging accounts comprises a plurality of physical downlink control channel (PDCCH) monitoring accounts—; monitoring a portion of the plurality of paging accounts based on the reception of an identifier associated with the WTRU; and detecting paging downlink control information (DCI) from a PDCCH monitoring account among the plurality of PDCCH monitoring accounts in the monitored portion—the paging DCI comprising a short message, and the short message indicating that the WTRU may stop monitoring subsequent PDCCH monitoring accounts in the portion of the plurality of paging accounts associated with the unlicensed spectrum. Claim 20 In claim 19, the plurality of PDCCH monitoring accounts are successive PDCCH monitoring accounts corresponding to the amount of transmitted synchronization signal blocks (SSBs) and the amount of sweeps used for paging transmissions.

Images