Verifying pre-configured resources in inactive state

JP7584053B2Active Publication Date: 2024-11-15OFINNO LLC
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023501071
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Priority Date
2020-07-07
Filing Date
2021-07-07
Publication Date
2024-11-15
Estimated Expiration
2041-07-07

AI Technical Summary

Benefits of technology

【0002】 本開示では、さまざまな実施形態が、開示された技術がどのように実装され得るか、および/または開示された技術がどのように環境およびシナリオで実践され得るかの実施例として提示される。関連技術分野の当業者には、範囲から逸脱することなく、形態および詳細のさまざまな変更を行うことができることは明らかであろう。実際、明細書を読んだ後、代替的な実施形態を実装する方法が関連技術分野の当業者に明らかになるであろう。本実施形態は、例示的な実施形態のいずれによっても限定されるべきではない。本開示の実施形態は、添付図面を参照して説明される。開示された例示的実施形態からの制限、特徴、および/または要素が組み合わせられ、本開示の範囲内でさらなる実施形態を作成することができる。機能と利点を強調する図は、例としてのみ示される。開示されたアーキテクチャーは、示される以外の方式で利用することができるように、十分に柔軟で構成可能である。例えば、いかなるフローチャートにリストされたアクションも、いくつかの実施形態で再配列され、または任意選択としてのみ使用され得る。 本発明は、例えば、以下を提供する。 (項目1) 方法であって、 無線リソース制御(RRC)接続状態の無線デバイスによって、RRC非アクティブ状態の間の送信で使用するための構成パラメーターを含むRRCリリースメッセージを受信することであって、前記構成パラメーターが、 セルの複数のSSBのうちの第一の同期信号ブロック(SSB)の識別子と、 前記RRC非アクティブ状態中に前記送信で使用するための、前記第一のSSBに対応するアップリンクリソースの一つまたは複数のリソースパラメーターと、 前記アップリンクソースを介した前記送信を検証するための第一の閾値と、を含む、受信することと、 前記RRCリリースメッセージに基づき、前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記アップリンクリソースが、前記RRC非アクティブ状態の間の前記送信における使用に有効であると決定することであって、前記決定が、前記第一のSSBのビーム測定値が前記第一の閾値以上であることに基づく、決定することと、 前記決定に基づき、前記アップリンクリソースを介してトランスポートブロックを送信することと、を含む、方法。 (項目2) 方法であって、 無線デバイスによって、非アクティブ状態で使用するためのアップリンクリソースを示す無線リソース制御(RRC)リリースメッセージを受信することであって、前記アップリンクリソースが、複数のSSBのうち第一の同期信号ブロック(SSB)と関連付けられる、受信することと、 前記アップリンクリソースが前記非アクティブ状態での使用に有効であると決定することに基づき、前記アップリンクリソースを介してトランスポートブロックを送信することであって、前記決定が、前記第一のSSBのビーム測定値が第一の閾値以上であることに基づく、送信することと、を含む、方法。 (項目3) 前記RRCリリースメッセージが、 前記複数のSSBのうちの前記第一のSSBの識別子と、 前記非アクティブ状態で使用するための、前記第一のSSBに対応する前記アップリンクリソースの一つまたは複数のリソースパラメーターと、を含む、項目2に記載の方法。 (項目4) 前記無線デバイスが接続状態にある状態で前記RRCリリースメッセージを受信することをさらに含む、項目2~3のいずれか一項に記載の方法。 (項目5) 前記接続状態がRRC接続状態を含む、項目4に記載の方法。 (項目6) 前記RRCリリースメッセージが、前記非アクティブ状態の間の送信で使用するための構成パラメーターを含む、項目2~5のいずれか一項に記載の方法。 (項目7) 前記RRCリリースメッセージが、前記アップリンクソースを介した前記送信を検証するための前記第一の閾値を含む、項目2~6のいずれか一項に記載の方法。 (項目8) 前記RRCリリースメッセージに基づき、前記接続状態から前記非アクティブ状態に移行することをさらに含む、項目2~7のいずれか一項に記載の方法。 (項目9) 前記アップリンクリソースが有効であることの前記決定が、前記第一のSSBの前記ビーム測定値が第二の閾値未満であることにさらに基づく、項目2~8のいずれか一項に記載の方法。 (項目10) 前記RRCリリースメッセージが、前記第二の閾値を示す、項目9に記載の方法。 (項目11) 前記第一の閾値と前記第二の閾値が、 1ミリワットを基準としデシベルの絶対値である、または 前記ビーム測定値の前に決定された第二のビーム測定値を基準とし、デシベルの相対値である、項目9~10のいずれか一項に記載の方法。 (項目12) 前記ビーム測定値が、前記第一のSSBの基準信号受信電力(RSRP)である、項目2~11のいずれか一項に記載の方法。 (項目13) 前記アップリンクリソースが有効であることを前記決定することが、前記複数のSSBのうちの一つまたは複数のSSBに基づき、前記セルのセル測定値を決定することをさらに含む、項目2~12のいずれか一項に記載の方法。 (項目14) 前記セル測定値が、前記複数のSSBのうちの二つ以上のSSBに基づき決定される、項目13に記載の方法。 (項目15) 前記アップリンクリソースが有効であることの前記決定が、前記一つまたは複数のSSBが前記第一のSSBを含むことにさらに基づく、項目13~14のいずれか一項に記載の方法。 (項目16) 前記セル測定値が第三の閾値以上であることに基づき、複数のセルから前記セルを選択することをさらに含む、項目13~15のいずれか一項に記載の方法。 (項目17) 前記一つまたは複数のSSBの数を示す、前記セルのシステム情報を受信することをさらに含む、項目13~16のいずれか一項に記載の方法。 (項目18) 前記セル測定値が、前記一つまたは複数のSSBのRSRPに基づく、項目13~17のいずれか一項に記載の方法。 (項目19) 前記セル測定値が、前記一つまたは複数のSSBの前記RSRPの平均値である、項目18に記載の方法。 (項目20) 前記複数のSSBの前記RSRPに基づき、前記複数のSSBから前記一つまたは複数のSSBを選択することをさらに含む、項目13~19のいずれか一項に記載の方法。 (項目21) 前記送信することが、前記無線デバイスが前記非アクティブ状態にある状態で前記トランスポートブロックを送信することを含む、項目2~20のいずれか一項に記載の方法。 (項目22) 前記RRCリリースメッセージが、前記非アクティブ状態で使用するための、前記第一のSSBに関連付けられる第二のアップリンクリソースの一つまたは複数の第二のリソースパラメーターをさらに含む、項目2~21のいずれか一項に記載の方法。 (項目23) 前記第一のSSBに関連付けられる前記第二のアップリンクリソースが、前記非アクティブ状態での使用に無効であると決定することをさらに含む、項目22に記載の方法。 (項目24) 前記第二のアップリンクリソースが無効であるとの前記決定が、前記第一のSSBの第二のビーム測定値が前記第一の閾値未満であるか、または第二の閾値以上であることに基づく、項目23に記載の方法。 (項目25) 前記第二のアップリンクリソースが無効であるとの前記決定が、前記第一のSSBの第二のビーム測定値が前記第一の閾値と前記第二の閾値との間にないことに基づく、項目23に記載の方法。 (項目26) 前記複数のSSBのうちの一つまたは複数の第二のSSBに基づき、前記セルの第二のセル測定値を決定することをさらに含む、項目23~25のいずれか一項に記載の方法。 (項目27) 前記第二のアップリンクリソースが無効であるとの前記決定が、前記一つまたは複数の第二のSSBが前記第一のSSBを含まないことにさらに基づく、項目26に記載の方法。 (項目28) 前記第二のアップリンクリソースが無効であるとの前記決定に基づきランダムアクセス手順を開始することをさらに含む、項目23~27のいずれか一項に記載の方法。 (項目29) 前記非アクティブ状態がRRC非アクティブ状態を含む、項目2~28のいずれか一項に記載の方法。 (項目30) 前記非アクティブ状態がRRCアイドル状態を含む、項目2~29のいずれか一項に記載の方法。 (項目31) 方法であって、 無線リソース制御(RRC)接続状態の無線デバイスによって、RRC非アクティブ状態で使用するためのアップリンクリソースを示すRRCリリースメッセージを受信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、受信することと、 前記RRCリリースメッセージに基づき、前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記アップリンクリソースが、前記RRC非アクティブ状態での使用に有効であると決定することであって、前記決定が、前記第一のSSBのビーム測定値が第一の閾値以上であることに基づく、決定することと、 前記決定に基づき、前記アップリンクリソースを介してトランスポートブロックを送信することと、を含む、方法。 (項目32) 前記RRCリリースメッセージが、RRC非アクティブ状態の間の送信で使用するための構成パラメーターを含み、前記構成パラメーターが、 前記セルの前記複数のSSBのうちの前記第一のSSBの識別子と、 前記RRC非アクティブ状態中に前記送信で使用するための、前記第一のSSBに対応する前記アップリンクリソースの一つまたは複数のリソースパラメーターと、 前記アップリンクソースを介して前記送信を検証するための前記第一の閾値と、を含む、項目31に記載の方法。 (項目33) 前記アップリンクリソースが有効であるとの前記決定が、前記第一のSSBの前記ビーム測定値が第二の閾値未満であることにさらに基づく、項目31~32のいずれか一項に記載の方法。 (項目34) 前記RRCリリースメッセージが、前記第一の閾値および第二の閾値を示す、項目33に記載の方法。 (項目35) 前記第一の閾値および前記第二の閾値が、1ミリワットを基準としデシベルの絶対値である、項目34に記載の方法。 (項目36) 前記第一の閾値および前記第二の閾値が、前記ビーム測定値の前に決定される第二のビーム測定値を基準としてデシベルの相対値である、項目34~35のいずれか一項に記載の方法。 (項目37) 前記RRCリリースメッセージが、前記RRC非アクティブ状態で使用するための前記第一のSSBに関連付けられる第二のアップリンクリソースの一つまたは複数の第二のリソースパラメーターを含む、項目31~36のいずれか一項に記載の方法。 (項目38) 前記第一のSSBに関連付けられる前記第二のアップリンクリソースが、前記RRC非アクティブ状態での使用に無効であると決定することをさらに含む、項目37に記載の方法。 (項目39) 前記第二のアップリンクリソースが無効であることの前記決定が、前記第一のSSBの第二のビーム測定値が前記第一の閾値未満であるか、または第二の閾値以上であることに基づく、項目38に記載の方法。 (項目40) 前記複数のSSBのうちの一つまたは複数の第二のSSBに基づき、前記セルの第二のセル測定値を決定することをさらに含む、項目38~39のいずれか一項に記載の方法。 (項目41) 前記第二のアップリンクリソースが無効であるとの前記決定が、前記一つまたは複数の第二のSSBが前記第一のSSBを含まないことにさらに基づく、項目40に記載の方法。 (項目42) 前記第二のアップリンクリソースが無効であるとの前記決定に基づきランダムアクセス手順を開始することをさらに含む、項目40~41のいずれか一項に記載の方法。 (項目43) 方法であって、 無線リソース制御(RRC)接続状態の無線デバイスによって、RRC非アクティブ状態で使用するためのアップリンクリソースを示すRRCリリースメッセージを受信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、受信することと、 前記RRCリリースメッセージに基づき、前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記アップリンクリソースが、前記RRC非アクティブ状態で使用するのに無効であると決定することであって、前記決定が、 前記第一のSSBの同期信号(SS)RSRPが、第一の閾値よりも小さいこと、および 前記複数のSSBのうちの一つまたは複数のSSBのサービングセルRSRPが、第二の閾値以上であることに基づく、決定することと、 前記決定に基づき、前記ランダムアクセス手順のプリアンブルを送信することと、を含む、方法。 (項目44) 前記アップリンクリソースが無効であるとの前記決定が、前記非アクティブ状態のデータ到着に応答している、項目43に記載の方法。 (項目45) 方法であって、 無線リソース制御(RRC)接続状態の無線デバイスによって、RRC非アクティブ状態で使用するためのアップリンクリソースを示すRRCリリースメッセージを受信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、受信することと、 前記RRCリリースメッセージに基づき、前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記複数のSSBのうちの一つまたは複数のSSBを選択して、タイミングアドバンス値を検証することと、 前記アップリンクリソースを、 前記一つまたは複数のSSBの基準信号受信電力(RSRP)が範囲内にあること、および 前記一つまたは複数のSSBが前記第一のSSBを含むことに基づき、検証することと、 前記RRC非アクティブ状態で、前記第一のSSBに関連付けられる前記アップリンクリソースを介してトランスポートブロックを送信することと、を含む、方法。 (項目46) 方法であって、 無線リソース制御(RRC)接続状態の無線デバイスによって、RRC非アクティブ状態で使用するためのアップリンクリソースを示すRRCリリースメッセージを受信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、受信することと、 前記RRCリリースメッセージに基づき、前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記複数のSSBのうちの一つまたは複数のSSBを選択して、タイミングアドバンス値を検証することと、 前記RRC非アクティブ状態で使用するために、 前記一つまたは複数のSSBの基準信号受信電力(RSRP)が範囲外であること、または 前記一つまたは複数のSSBが前記第一のSSBを含まないことに基づき、前記アップリンクリソースを無効化することと、 前記アップリンクリソースが無効化されることに基づき、ランダムアクセスプリアンブルを送信することと、を含む、方法。 (項目47) 一つまたは複数のプロセッサーと、前記一つまたは複数のプロセッサーによって実行されるとき、無線デバイスに、項目1~46のいずれか一項に記載の方法を実施させる命令を格納するメモリーと、を含む、無線デバイス。 (項目48) 一つまたは複数のプロセッサーによって実行されるとき、前記一つまたは複数のプロセッサーに項目1~46のいずれか一項に記載の方法を実行させる命令を含む、非一時的コンピューター可読媒体。 (項目49) 方法であって、 基地局によって、無線リソース制御(RRC)接続状態の無線デバイスに、前記無線デバイスがRRC非アクティブ状態の間の送信で使用する構成パラメーターを含むRRCリリースメッセージを送信することであって、前記構成パラメーターが、 セルの複数のSSBのうちの第一の同期信号ブロック(SSB)の識別子と、 RRC非アクティブ状態中に前記送信で使用するための、前記第一のSSBに対応するアップリンクリソースの一つまたは複数のリソースパラメーターと、 前記アップリンクソースを介した前記送信を検証するための第一の閾値および第二の閾値と、を含む、送信することと、 前記RRCリリースメッセージに基づき、前記無線デバイスのRRC状態を前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記アップリンクリソースを介して、前記アップリンクリソースが前記RRC非アクティブ状態の間の前記送信における使用に有効であるとの決定に基づきトランスポートブロックを受信することであって、前記アップリンクリソースが有効であることが、前記第一のSSBのビーム測定値が、 前記第一の閾値以上であること、および 前記第二の閾値未満であることに基づく、受信することと、を含む、方法。 (項目50) 方法であって、 基地局によって無線デバイスに、非アクティブ状態で使用するためにアップリンクリソースを示す無線リソース制御(RRC)リリースメッセージを送信することであって、前記アップリンクリソースが複数のSSBのうち第一の同期信号ブロック(SSB)と関連付けられる、送信することと、 前記アップリンクリソースを介して、前記アップリンクリソースが前記RRC非アクティブ状態での使用に有効であるとの決定に基づき、トランスポートブロックを受信することであって、前記アップリンクリソースが有効であることが、前記第一のSSBのビーム測定値が第一の閾値以上であることに基づく、受信することとを含む、方法。 (項目51) 前記RRCリリースメッセージが、 複数のSSBのうちの前記第一のSSBの識別子と、 前記非アクティブ状態で使用するための、前記第一のSSBに対応する前記アップリンクリソースの一つまたは複数のリソースパラメーターと、を含む、項目50に記載の方法。 (項目52) 前記無線デバイスに、前記無線デバイスが接続状態にある状態で前記RRCリリースメッセージを送信することをさらに含む、項目50~51のいずれか一項に記載の方法。 (項目53) 前記接続状態が、RRC接続状態を含む、項目52に記載の方法。 (項目54) 前記RRCリリースメッセージが、前記無線デバイスが前記非アクティブ状態の間の送信に使用する構成パラメーターを含む、項目50~51に記載の方法。 (項目55) 前記RRCリリースメッセージが、前記無線デバイスが前記アップリンクソースを介した前記送信を検証するための前記第一の閾値を含む、項目50~52に記載の方法。 (項目56) 前記RRCリリースメッセージに基づき、かつ前記無線デバイスの前記RRC状態について、前記接続状態から前記非アクティブ状態に移行することをさらに含む、項目50~53に記載の方法。 (項目57) 前記アップリンクリソースが有効であるとの前記決定が、前記第一のSSBの前記ビーム測定値が、第二の閾値未満であることにさらに基づく、項目50~56に記載の方法。 (項目58) 前記RRCリリースメッセージは、前記第二の閾値を示す、項目57に記載の方法。 (項目59) 前記第一の閾値と前記第二の閾値が、 1ミリワットを基準としデシベルの絶対値である、または 前記ビーム測定値の前に決定された第二のビーム測定値を基準とし、デシベルの相対値である、項目57~58のいずれか一項に記載の方法。 (項目60) 前記ビーム測定値が、前記第一のSSBの基準信号受信電力(RSRP)である、項目50~59のいずれか一項に記載の方法。 (項目61) 前記アップリンクリソースが有効であると前記決定することが、前記複数のSSBのうちの一つまたは複数のSSBに基づき、前記セルのセル測定値を決定することを含む、項目50~60のいずれか一項に記載の方法。 (項目62) 前記セル測定値が、前記複数のSSBのうちの二つ以上のSSBに基づき決定される、項目61に記載の方法。 (項目63) 前記アップリンクリソースが有効であることが、前記一つまたは複数のSSBが前記第一のSSBを含むことにさらに基づく、項目61~62のいずれか一項に記載の方法。 (項目64) 前記アップリンクリソースが有効であることが、前記セル測定値が第三の閾値以上であることに基づき、複数のセルから、選択された前記セルにさらに基づく、項目61~63のいずれか一項に記載の方法。 (項目65) 前記一つまたは複数のSSBの数を示す、前記セルのシステム情報を送信することをさらに含む、項目61~64のいずれか一項に記載の方法。 (項目66) 前記セル測定値が、前記一つまたは複数のSSBのRSRPに基づく、項目61~65のいずれか一項に記載の方法。 (項目67) 前記セル測定値が、前記一つまたは複数のSSBの前記RSRPの平均値である、項目66に記載の方法。 (項目68) 前記複数のSSBの前記RSRPに基づき、前記複数のSSBのうちの前記一つまたは複数のSSBを選択することをさらに含む、項目61~67のいずれか一項に記載の方法。 (項目69) 前記受信することが、前記無線デバイスが前記非アクティブ状態にある状態で前記トランスポートブロックを受信することを含む、項目50~68のいずれか一項に記載の方法。 (項目70) 前記RRCリリースメッセージが、前記非アクティブ状態で使用するために、前記第一のSSBに関連付けられる第二のアップリンクリソースの一つまたは複数の第二のリソースパラメーターをさらに含む、項目50~69のいずれか一項に記載の方法。 (項目71) 前記第二のアップリンクリソースの使用が前記RRC非アクティブ状態で無効化されることを決定することをさらに含む、項目70に記載の方法。 (項目72) 前記RRC非アクティブ状態で前記第一のSSBに関連付けられる前記第二のアップリンクリソースを介した送信なしを決定することをさらに含み、前記送信なしの決定が、前記第二のアップリンクリソースの前記使用が前記RRC非アクティブ状態で無効化されることに基づく、項目71に記載の方法。 (項目73) 前記第二のアップリンクリソースを介した送信なしの前記決定が、前記第一のSSBの第二のビーム測定値が、前記第一の閾値未満であるか、または第二の閾値以上であることに基づく、項目72に記載の方法。 (項目74) 前記第二のアップリンクリソースを介した送信なしの前記決定が、前記第一のSSBの第二のビーム測定値が前記第一の閾値と前記第二の閾値との間にはないことに基づく、項目72に記載の方法。 (項目75) 前記第二のアップリンクリソースを介した送信なしの前記決定が、前記複数のSSBのうちの一つまたは複数の第二のSSBに基づき測定される、前記セルの第二のセル測定値に基づく、項目70~74のいずれか一項に記載の方法。 (項目76) 前記第二のアップリンクリソースを介した送信なしの前記決定が、前記一つまたは複数の第二のSSBが前記第一のSSBを含まないことにさらに基づく、項目75に記載の方法。 (項目77) 前記第二のアップリンクリソースが無効であるとの前記決定に基づき開始されるランダムアクセス手順のプリアンブルを受信することをさらに含む、項目70~76のいずれか一項に記載の方法。 (項目78) 前記非アクティブ状態が、RRC非アクティブ状態を含む、項目50~77のいずれか一項に記載の方法。 (項目79) 前記非アクティブ状態が、RRCアイドル状態を含む、項目50~78のいずれか一項に記載の方法。 (項目80) 方法であって、 基地局によって、無線リソース制御(RRC)接続状態の無線デバイスに、前記無線デバイスがRRC非アクティブ状態で使用するためのアップリンクリソースを示す、RRCリリースメッセージを送信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、送信することと、 前記RRCリリースメッセージに基づき、前記無線デバイスのRRC状態を前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記アップリンクリソースを介して送信なしを受信することを決定することであって、前記決定が、前記アップリンクリソースが、 前記第一のSSBの同期信号(SS)RSRPが、第一の閾値よりも小さいこと、および 前記複数のSSBのうちの一つまたは複数のSSBのサービングセルRSRPが、第二の閾値以上であることに基づき無効であることを示す、決定することと、 前記アップリンクリソースが無効であることに基づき、前記ランダムアクセス手順のプリアンブルを受信することと、を含む、方法。 (項目81) 方法であって、 基地局によって、無線リソース制御(RRC)接続状態の無線デバイスに、RRC非アクティブ状態で使用するためのアップリンクリソースを示すRRCリリースメッセージを送信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、送信することと、 前記RRCリリースメッセージに基づき、前記無線デバイスのRRC状態を前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記RRC非アクティブ状態の前記無線デバイスから、前記第一のSSBに関連付けられる前記アップリンクリソースを介してトランスポートブロックを受信することであって、前記受信が、前記アップリンクリソースが、 タイミングアドバンス値を検証するために前記複数のSSBから選択される一つまたは複数のSSB、 前記一つまたは複数のSSBの基準信号受信電力(RSRP)が範囲内にあること、および 前記一つまたは複数のSSBが前記第一のSSBを含むことに基づき無効化されることに基づく、受信することと、を含む、方法。 (項目82) 方法であって、 基地局によって、無線リソース制御(RRC)接続状態の無線デバイスに、RRC非アクティブ状態で使用するためのアップリンクリソースを示すRRCリリースメッセージを送信することであって、前記アップリンクリソースが、セルの複数のSSBのうちの第一の同期信号ブロック(SSB)と関連付けられる、送信することと、 前記RRCリリースメッセージに基づき、前記無線デバイスのRRC状態を前記RRC接続状態から前記RRC非アクティブ状態に移行することと、 前記RRC非アクティブ状態の前記無線デバイスから、ランダムアクセスプリアンブルを受信することであって、前記受信が、前記アップリンクリソースが、 タイミングアドバンス値を検証するために前記複数のSSBから選択される一つまたは複数のSSB、および 少なくとも下記のうちの一つ: 前記一つまたは複数のSSBの基準信号受信電力(RSRP)が範囲外であること、または 前記一つまたは複数のSSBが、前記第一のSSBを含まないこと、に基づき無効化されることに基づく、受信することと、を含む、方法。 (項目83) 一つまたは複数のプロセッサーと、前記一つまたは複数のプロセッサーによって実行されるときに、前記無線デバイスに項目50~82のいずれか一項に記載の方法を実施させる命令を記憶するメモリーと、を含む、基地局。 (項目84) 一つまたは複数のプロセッサーによって実行されるとき、前記一つまたは複数のプロセッサーに項目50~82のいずれか一項に記載の方法を実施させる命令を含む、非一時的コンピューター可読媒体。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007584053000001
    Figure 0007584053000001
  • Figure 0007584053000002
    Figure 0007584053000002
  • Figure 0007584053000003
    Figure 0007584053000003
Patent Text Reader

Abstract

In some embodiments, a wireless device receives a radio resource control (RRC) release message including an identifier of a first synchronization signal block (SSB) among a plurality of SSBs for use in an RRC inactive state and one or more resource parameters for an uplink resource corresponding to the first SSB. The wireless device transmits a transport block via the uplink resource based on determining that the uplink resource is valid for use in the RRC inactive state. The wireless device determines that the uplink resource is valid based on a beam measurement value for the first SSB being greater than or equal to a first threshold.
Need to check novelty before this filing date? Find Prior Art

Description

[Background technology]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Provisional Patent Application No. 63 / 049,050, filed July 7, 2020, which is incorporated by reference in its entirety herein. Summary of the Invention [Means for solving the problem]

[0002] In this disclosure, various embodiments are presented as examples of how the disclosed technology may be implemented and / or how the disclosed technology may be practiced in environments and scenarios. It will be apparent to one skilled in the relevant art that various changes in form and details may be made without departing from the scope. Indeed, after reading the specification, it will be apparent to one skilled in the relevant art how to implement alternative embodiments. The present embodiments should not be limited by any of the exemplary embodiments. The embodiments of the present disclosure are described with reference to the accompanying drawings. Limitations, features, and / or elements from the disclosed exemplary embodiments may be combined to create further embodiments within the scope of the present disclosure. The figures that highlight features and advantages are shown by way of example only. The disclosed architecture is sufficiently flexible and configurable to be utilized in ways other than those shown. For example, the actions listed in any flowchart may be rearranged in some embodiments or used only as options. The present invention provides, for example, the following: (Item 1) 1. A method comprising: receiving, by a wireless device in a radio resource control (RRC) connected state, an RRC release message including configuration parameters for use in transmissions during an RRC inactive state, the configuration parameters comprising: an identifier of a first synchronization signal block (SSB) among a plurality of SSBs of a cell; one or more resource parameters for uplink resources corresponding to the first SSB for use in the transmission during the RRC inactive state; a first threshold for validating the transmission via the uplink source; transitioning from the RRC connected state to the RRC inactive state based on the RRC release message; determining that the uplink resources are available for use in the transmission during the RRC inactive state, the determination being based on a beam measurement value of the first SSB being greater than or equal to the first threshold; and transmitting a transport block over the uplink resources based on the determination. (Item 2) 1. A method comprising: receiving, by the wireless device, a radio resource control (RRC) release message indicating uplink resources for use in an inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs; and transmitting a transport block via the uplink resource based on determining that the uplink resource is available for use in the inactive state, the determination being based on a beam measurement value of the first SSB being greater than or equal to a first threshold. (Item 3) The RRC release message: an identifier of the first SSB of the plurality of SSBs; and one or more resource parameters of the uplink resource corresponding to the first SSB for use in the inactive state. (Item 4) The method according to any one of claims 2 to 3, further comprising receiving the RRC release message while the wireless device is in a connected state. (Item 5) 5. The method of claim 4, wherein the connection state includes an RRC connection state. (Item 6) 6. The method according to any one of claims 2 to 5, wherein the RRC release message includes configuration parameters for use in transmissions during the inactive state. (Item 7) 7. The method according to any one of items 2 to 6, wherein the RRC release message includes the first threshold value for validating the transmission via the uplink source. (Item 8) The method according to any one of claims 2 to 7, further comprising transitioning from the connected state to the inactive state based on the RRC release message. (Item 9) 9. A method according to any one of items 2 to 8, wherein the determination that the uplink resource is valid is further based on the beam measurement value of the first SSB being less than a second threshold. (Item 10) 10. The method of claim 9, wherein the RRC release message indicates the second threshold. (Item 11) The first threshold value and the second threshold value are Absolute value in decibels relative to 1 milliwatt, or 11. The method according to any one of items 9 to 10, wherein the beam measurement value is based on a second beam measurement value determined before the beam measurement value and is a relative value in decibels. (Item 12) 12. The method according to any one of items 2 to 11, wherein the beam measurement value is a reference signal received power (RSRP) of the first SSB. (Item 13) 13. The method according to any one of claims 2 to 12, wherein the determining that the uplink resources are valid further comprises determining cell measurements for the cell based on one or more SSBs of the plurality of SSBs. (Item 14) Item 14. The method of item 13, wherein the cell measurement value is determined based on two or more SSBs of the plurality of SSBs. (Item 15) 15. The method according to any one of claims 13 to 14, wherein the determination that the uplink resources are valid is further based on the one or more SSBs including the first SSB. (Item 16) 16. The method according to any one of items 13 to 15, further comprising selecting the cell from a plurality of cells based on the cell measurement value being equal to or greater than a third threshold. (Item 17) 17. The method according to any one of claims 13 to 16, further comprising receiving system information for the cell indicating the number of the one or more SSBs. (Item 18) 18. The method according to any one of claims 13 to 17, wherein the cell measurement values ​​are based on RSRPs of the one or more SSBs. (Item 19) 20. The method of claim 18, wherein the cell measurement value is an average value of the RSRP of the one or more SSBs. (Item 20) 20. The method according to any one of claims 13 to 19, further comprising selecting the one or more SSBs from the plurality of SSBs based on the RSRPs of the plurality of SSBs. (Item 21) 21. The method according to any one of claims 2 to 20, wherein the transmitting step includes transmitting the transport block while the wireless device is in the inactive state. (Item 22) 22. The method according to any one of claims 2 to 21, wherein the RRC release message further includes one or more second resource parameters of a second uplink resource associated with the first SSB for use in the inactive state. (Item 23) 23. The method of claim 22, further comprising determining that the second uplink resource associated with the first SSB is invalid for use in the inactive state. (Item 24) 24. The method of claim 23, wherein the determination that the second uplink resource is invalid is based on a second beam measurement value of the first SSB being less than the first threshold or greater than or equal to a second threshold. (Item 25) 24. The method of claim 23, wherein the determination that the second uplink resource is invalid is based on a second beam measurement value of the first SSB not being between the first threshold and the second threshold. (Item 26) 26. The method of any one of claims 23 to 25, further comprising determining a second cell measurement value for the cell based on one or more second SSBs of the plurality of SSBs. (Item 27) 27. The method of claim 26, wherein the determination that the second uplink resource is invalid is further based on the one or more second SSBs not including the first SSB. (Item 28) 28. The method of any one of claims 23 to 27, further comprising initiating a random access procedure based on the determination that the second uplink resource is invalid. (Item 29) 29. The method according to any one of claims 2 to 28, wherein the inactive state comprises an RRC inactive state. (Item 30) 30. The method according to any one of claims 2 to 29, wherein the inactive state comprises an RRC idle state. (Item 31) 1. A method comprising: receiving, by a wireless device in a Radio Resource Control (RRC) connected state, an RRC release message indicating uplink resources for use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning from the RRC connected state to the RRC inactive state based on the RRC release message; determining that the uplink resources are available for use in the RRC inactive state, the determination being based on a beam measurement value of the first SSB being greater than or equal to a first threshold; and transmitting a transport block over the uplink resources based on the determination. (Item 32) the RRC release message includes configuration parameters for use in transmissions during an RRC inactive state, the configuration parameters comprising: an identity of the first SSB of the plurality of SSBs of the cell; one or more resource parameters of the uplink resources corresponding to the first SSB for use in the transmission during the RRC inactive state; 32. The method of claim 31, further comprising: the first threshold for validating the transmission via the uplink source. (Item 33) A method according to any one of items 31 to 32, wherein the determination that the uplink resource is valid is further based on the beam measurement value of the first SSB being less than a second threshold. (Item 34) Item 34. The method of item 33, wherein the RRC release message indicates the first threshold and the second threshold. (Item 35) 35. The method of claim 34, wherein the first threshold and the second threshold are absolute values ​​in decibels referenced to 1 milliwatt. (Item 36) 36. The method of any one of items 34 to 35, wherein the first threshold and the second threshold are relative values ​​in decibels based on a second beam measurement value determined prior to the beam measurement value. (Item 37) 37. A method according to any one of claims 31 to 36, wherein the RRC release message includes one or more second resource parameters of a second uplink resource associated with the first SSB for use in the RRC inactive state. (Item 38) 38. The method of claim 37, further comprising determining that the second uplink resource associated with the first SSB is invalid for use in the RRC inactive state. (Item 39) Item 39. The method of item 38, wherein the determination that the second uplink resource is invalid is based on a second beam measurement value of the first SSB being less than the first threshold or greater than or equal to a second threshold. (Item 40) 40. The method of any one of items 38 to 39, further comprising determining a second cell measurement value for the cell based on one or more second SSBs of the plurality of SSBs. (Item 41) 41. The method of claim 40, wherein the determination that the second uplink resource is invalid is further based on the one or more second SSBs not including the first SSB. (Item 42) 42. The method according to any one of claims 40 to 41, further comprising initiating a random access procedure based on the determination that the second uplink resource is invalid. (Item 43) 1. A method comprising: receiving, by a wireless device in a Radio Resource Control (RRC) connected state, an RRC release message indicating uplink resources for use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning from the RRC connected state to the RRC inactive state based on the RRC release message; determining that the uplink resources are invalid for use in the RRC inactive state, the determining comprising: a synchronization signal (SS) RSRP of the first SSB is less than a first threshold; and determining based on a serving cell RSRP of one or more SSBs of the plurality of SSBs being greater than or equal to a second threshold; and transmitting a preamble for the random access procedure based on the determination. (Item 44) 44. The method of claim 43, wherein the determination that the uplink resources are invalid is in response to data arrival in the inactive state. (Item 45) 1. A method comprising: receiving, by a wireless device in a Radio Resource Control (RRC) connected state, an RRC release message indicating uplink resources for use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning from the RRC connected state to the RRC inactive state based on the RRC release message; selecting one or more SSBs of the plurality of SSBs and verifying a timing advance value; The uplink resource, the Reference Signal Received Power (RSRP) of the one or more SSBs is within range; and verifying that the one or more SSBs include the first SSB; and transmitting a transport block over the uplink resources associated with the first SSB in the RRC inactive state. (Item 46) 1. A method comprising: receiving, by a wireless device in a Radio Resource Control (RRC) connected state, an RRC release message indicating uplink resources for use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning from the RRC connected state to the RRC inactive state based on the RRC release message; selecting one or more SSBs of the plurality of SSBs and verifying a timing advance value; For use in the RRC inactive state: the Reference Signal Received Power (RSRP) of said one or more SSBs is out of range, or Disabling the uplink resources based on the one or more SSBs not including the first SSB; and transmitting a random access preamble based on the uplink resource being disabled. (Item 47) A wireless device comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to implement a method according to any one of items 1 to 46. (Item 48) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 1 to 46. (Item 49) 1. A method comprising: transmitting, by a base station, to a wireless device in a radio resource control (RRC) connected state, an RRC release message including configuration parameters for use by the wireless device in transmissions during an RRC inactive state, the configuration parameters comprising: an identifier of a first synchronization signal block (SSB) among a plurality of SSBs of a cell; one or more resource parameters for uplink resources corresponding to the first SSB for use in the transmission during an RRC inactive state; transmitting, comprising a first threshold and a second threshold for validating the transmission via the uplink source; transitioning an RRC state of the wireless device from the RRC connected state to the RRC inactive state based on the RRC release message; receiving, via the uplink resource, a transport block based on a determination that the uplink resource is valid for use in the transmission during the RRC inactive state, the validity of the uplink resource being determined by beam measurements of the first SSB, being equal to or greater than the first threshold; and and receiving based on the second threshold being less than the second threshold. (Item 50) 1. A method comprising: transmitting, by the base station to the wireless device, a radio resource control (RRC) release message indicating uplink resources for use in an inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs; and receiving a transport block via the uplink resource based on a determination that the uplink resource is valid for use in the RRC inactive state, the validity of the uplink resource being based on a beam measurement value of the first SSB being greater than or equal to a first threshold. (Item 51) The RRC release message: an identifier of the first SSB among a plurality of SSBs; and one or more resource parameters of the uplink resource corresponding to the first SSB for use in the inactive state. (Item 52) 52. The method according to any one of items 50 to 51, further comprising sending the RRC release message to the wireless device while the wireless device is in a connected state. (Item 53) 53. The method of claim 52, wherein the connection state includes an RRC connection state. (Item 54) 52. The method according to claim 50, wherein the RRC release message includes configuration parameters that the wireless device uses for transmission during the inactive state. (Item 55) 53. The method according to any one of items 50 to 52, wherein the RRC release message includes the first threshold value for the wireless device to verify the transmission via the uplink source. (Item 56) 54. The method according to any one of claims 50 to 53, further comprising transitioning the RRC state of the wireless device from the connected state to the inactive state based on the RRC release message. (Item 57) 57. The method of any one of items 50 to 56, wherein the determination that the uplink resource is valid is further based on the beam measurement value of the first SSB being less than a second threshold. (Item 58) 58. The method of claim 57, wherein the RRC release message indicates the second threshold. (Item 59) The first threshold value and the second threshold value are Absolute value in decibels relative to 1 milliwatt, or 59. The method according to any one of items 57 to 58, wherein the beam measurement value is referenced to a second beam measurement value determined before the beam measurement value and is a relative value in decibels. (Item 60) 60. A method according to any one of items 50 to 59, wherein the beam measurement value is a reference signal received power (RSRP) of the first SSB. (Item 61) 61. The method according to any one of claims 50 to 60, wherein determining that the uplink resources are valid comprises determining cell measurements for the cell based on one or more SSBs of the plurality of SSBs. (Item 62) Item 62. The method of item 61, wherein the cell measurement value is determined based on two or more SSBs of the plurality of SSBs. (Item 63) 63. The method of any one of items 61 to 62, wherein the uplink resources being available is further based on the one or more SSBs including the first SSB. (Item 64) Item 64. The method according to any one of items 61 to 63, wherein the availability of the uplink resources is further based on the cell being selected from a plurality of cells based on the cell measurement value being greater than or equal to a third threshold. (Item 65) 65. The method according to any one of claims 61 to 64, further comprising transmitting system information of the cell indicating the number of the one or more SSBs. (Item 66) 66. The method according to any one of claims 61 to 65, wherein the cell measurement values ​​are based on RSRPs of the one or more SSBs. (Item 67) Item 67. The method of item 66, wherein the cell measurement value is an average value of the RSRP of the one or more SSBs. (Item 68) 68. The method according to any one of claims 61 to 67, further comprising selecting the one or more SSBs from the plurality of SSBs based on the RSRPs of the plurality of SSBs. (Item 69) Item 69. The method of any one of items 50 to 68, wherein the receiving includes receiving the transport block while the wireless device is in the inactive state. (Item 70) 70. A method according to any one of claims 50 to 69, wherein the RRC release message further includes one or more second resource parameters of a second uplink resource associated with the first SSB for use in the inactive state. (Item 71) 71. The method of claim 70, further comprising determining that use of the second uplink resource is disabled in the RRC inactive state. (Item 72) 72. The method of claim 71, further comprising determining no transmission via the second uplink resource associated with the first SSB in the RRC inactive state, the determination of no transmission being based on the use of the second uplink resource being disabled in the RRC inactive state. (Item 73) 73. The method of claim 72, wherein the decision not to transmit via the second uplink resource is based on a second beam measurement value of the first SSB being less than the first threshold or greater than or equal to a second threshold. (Item 74) 73. The method of claim 72, wherein the decision not to transmit via the second uplink resource is based on a second beam measurement value of the first SSB not being between the first threshold and the second threshold. (Item 75) 75. A method according to any one of items 70 to 74, wherein the decision not to transmit via the second uplink resource is based on a second cell measurement value of the cell, the second cell measurement value being measured based on one or more second SSBs of the plurality of SSBs. (Item 76) Item 76. The method of item 75, wherein the decision not to transmit via the second uplink resource is further based on the one or more second SSBs not including the first SSB. (Item 77) 77. The method of any one of items 70 to 76, further comprising receiving a preamble for a random access procedure initiated based on the determination that the second uplink resource is invalid. (Item 78) 78. A method according to any one of claims 50 to 77, wherein the inactive state comprises an RRC inactive state. (Item 79) 79. A method according to any one of claims 50 to 78, wherein the inactive state comprises an RRC idle state. (Item 80) 1. A method comprising: transmitting, by a base station, a Radio Resource Control (RRC) release message to a wireless device in an RRC connected state, indicating uplink resources for the wireless device to use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning an RRC state of the wireless device from the RRC connected state to the RRC inactive state based on the RRC release message; determining to receive no transmission over the uplink resource, the determining comprising: a synchronization signal (SS) RSRP of the first SSB is less than a first threshold; and determining, based on a serving cell RSRP of one or more SSBs among the plurality of SSBs being equal to or greater than a second threshold, that the serving cell RSRP of the one or more SSBs is invalid; receiving a preamble for the random access procedure based on the uplink resource being invalid. (Item 81) 1. A method comprising: transmitting, by a base station, a Radio Resource Control (RRC) release message to a wireless device in an RRC connected state indicating uplink resources for use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning an RRC state of the wireless device from the RRC connected state to the RRC inactive state based on the RRC release message; receiving a transport block from the wireless device in the RRC inactive state over the uplink resources associated with the first SSB, the receiving comprising: one or more SSBs selected from said plurality of SSBs for verifying a timing advance value; the Reference Signal Received Power (RSRP) of the one or more SSBs is within range; and and receiving, based on the one or more SSBs being disabled based on including the first SSB. (Item 82) 1. A method comprising: transmitting, by a base station, a Radio Resource Control (RRC) release message to a wireless device in an RRC connected state indicating uplink resources for use in an RRC inactive state, the uplink resources being associated with a first synchronization signal block (SSB) of a plurality of SSBs of a cell; transitioning an RRC state of the wireless device from the RRC connected state to the RRC inactive state based on the RRC release message; receiving a random access preamble from the wireless device in the RRC inactive state, the receiving determining whether the uplink resource is: one or more SSBs selected from the plurality of SSBs for verifying a timing advance value; and At least one of the following: the Reference Signal Received Power (RSRP) of said one or more SSBs is out of range, or and receiving, based on the one or more SSBs being disabled based on not including the first SSB. (Item 83) A base station comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the wireless device to implement a method according to any one of items 50 to 82. (Item 84) A non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method of any one of items 50 to 82. [Brief description of the drawings]

[0003] Some examples of various embodiments of the present disclosure are described herein with reference to the drawings.

[0004] [Figure 1] 1A and 1B show an example of a mobile communication network in which embodiments of the present disclosure may be implemented.

[0005] [Diagram 2] 2A and 2B show the New Radio (NR) user plane and control plane protocol stacks, respectively.

[0006] [Diagram 3] FIG. 3 shows an example of services provided between protocol layers of the NR user plane protocol stack of FIG. 2A.

[0007] [Figure 4A] FIG. 4A shows an example downlink data flow through the NR user plane protocol stack of FIG. 2A.

[0008] [Figure 4B] FIG. 4B shows an example format of a MAC subheader in a MAC PDU.

[0009] [Diagram 5] 5A and 5B show the mapping between downlink and uplink logical, transport and physical channels, respectively.

[0010] [Figure 6] FIG. 6 is an exemplary diagram illustrating RRC state transitions of a UE.

[0011] [Figure 7]FIG. 7 shows an example of the structure of an NR frame in which OFDM symbols are grouped.

[0012] [Figure 8] FIG. 8 shows an example of a slot configuration in the time and frequency domain of an NR carrier.

[0013] [Figure 9] FIG. 9 shows an example of bandwidth adaptation using three configured BWPs for an NR carrier.

[0014] [Figure 10A] FIG. 10A shows three carrier aggregation configurations with two component carriers.

[0015] [Figure 10B] FIG. 10B shows an example of how aggregation cells can be arranged into one or more PUCCH groups.

[0016] [Figure 11A] FIG. 11A shows an example of an SS / PBCH block structure and location.

[0017] [Figure 11B] FIG. 11B shows an example of CSI-RS mapped to the time and frequency domain.

[0018] [Figure 12] 12A and 12B show examples of three downlink and uplink beam management procedures, respectively.

[0019] [Figure 13] 13A, 13B, and 13C show a four-step contention-based random access procedure, a two-step contention-free random access procedure, and an alternative two-step random access procedure, respectively.

[0020] [Figure 14A] FIG. 14A shows an example of a CORESET configuration for bandwidth portions.

[0021] [Figure 14B] FIG. 14B shows an example of CCE to REG mapping for DCI transmission on CORESET and PDCCH processing.

[0022] [Figure 15] FIG. 15 illustrates an embodiment of a wireless device communicating with a base station.

[0023] [Figure 16] 16A, 16B, 16C, and 16D show example structures for uplink and downlink transmission.

[0024] [Figure 17] FIG. 17 is an example of one or more data packet transmissions in an RRC_INACTIVE state (or an RRC_IDLE state) according to one aspect of an embodiment of the present disclosure.

[0025] [Figure 18A] FIG. 18A is an example of a (pre)configured grant indicating one or more uplink radio resources in a non-RRC_CONNECTED state (e.g., an RRC_INACTIVE state and / or an RRC_IDLE state) according to one aspect of an embodiment of the present disclosure.

[0026] [Figure 18B] FIG. 18B is an example of a (pre)configured grant indicating one or more uplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE state) in accordance with an aspect of an embodiment of the present disclosure.

[0027] [Figure 19]FIG. 19 is an example of one or more data packet transmissions in a Non-RRC_CONNECTED (eg, RRC_INACTIVE and / or RRC_IDLE) state in accordance with one aspect of an embodiment of the present disclosure.

[0028] [Figure 20] FIG. 20 is an example of one or more data packet transmissions in a Non-RRC_CONNECTED (eg, RRC_INACTIVE and / or RRC_IDLE) state in accordance with one aspect of an embodiment of the present disclosure.

[0029] [Figure 21A] FIG. 21A is an example of TA validation according to one aspect of an embodiment of the present disclosure.

[0030] [Figure 21B] FIG. 21B is an example of TA validation according to one aspect of an embodiment of the present disclosure.

[0031] [Figure 22] FIG. 22 is an example of a geographical display of increasing and / or decreasing thresholds according to one aspect of an embodiment of the present disclosure.

[0032] [Diagram 23] FIG. 23 is an example of one or more radio resources in a BWP (eg, DL BWP and / or UL BWP) according to one aspect of an embodiment of the present disclosure.

[0033] [Figure 24] FIG. 24 is an example of beam management for transmission and / or reception in a Non-RRC_CONNECTED state in accordance with one aspect of an embodiment of the present disclosure.

[0034] [Diagram 25] FIG. 25 is an example of DL RS selection relative to cell measurements according to one aspect of an embodiment of the present disclosure.

[0035] [Figure 26] FIG. 26 is an example of beam verification according to one aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] The embodiments may be configured to operate as desired. The disclosed mechanisms may be executed when certain criteria are met, for example, in a wireless device, a base station, a wireless environment, a network, a combination of the above, etc. Exemplary criteria may be based at least in part, for example, on wireless device or network node configuration, traffic load, initial system settings, packet size, traffic characteristics, a combination of the above, etc. Once one or more criteria are met, various exemplary embodiments may be applied. Thus, it may be possible to implement exemplary embodiments that selectively implement the disclosed protocols.

[0037] A base station may communicate with a mix of wireless devices. Wireless devices and / or base stations may support multiple technologies and / or multiple releases of the same technology. Wireless devices may have some specific capabilities depending on the category and / or capabilities of the wireless devices. When the disclosure refers to a base station communicating with multiple wireless devices, the disclosure may refer to a subset of all wireless devices in the coverage area. The disclosure may refer to multiple wireless devices of a given LTE or 5G release, for example, that include a given capability and are in a given sector of the base station. Multiple wireless devices in the disclosure may refer to selected multiple wireless devices and / or a subset of all wireless devices in the coverage area that perform according to the disclosed methods, etc. There may be multiple base stations or multiple wireless devices in a coverage area that may not comply with the disclosed methods. For example, those wireless devices or base stations perform based on older releases of LTE or 5G technology.

[0038] As used herein, the terms "a" and "an" and similar terms are interpreted as "at least one" and "one or more." Similarly, any term ending with the suffix "(s)" should be interpreted as "at least one" and "one or more." As used herein, the term "may" is interpreted as "may be, for example." In other words, the term "may" indicates that the phrase following the term "may" is one example of multiple suitable possibilities, and may or may not be used by one or more of the various embodiments. As used herein, the terms "comprises" and "consists of" recite one or more components of a described element. The term "comprises" is interchangeable with "includes" and does not exclude unrecited components included in a described element. In contrast, "consists of" provides a complete recitation of one or more components of a described element. As used herein, the term "based on" should be interpreted as "based at least in part on" rather than, for example, "based only on." As used herein, the term "and / or" refers to any possible combination of the listed elements. For example, "A, B, and / or C" can refer to A, B, C, A and B, A and C, B and C, or A, B, and C.

[0039] If A and B are sets and every element of A is also an element of B, then A is said to be a subset of B. Only non-empty sets and subsets are considered herein. For example, possible subsets of B={cell1, cell2} are {cell1}, {cell2}, and {cell1, cell2}. The phrase "based on" (or equivalently "based at least on") indicates that the phrase following the term "based on" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "in response to" (or equivalently "at least in response to") indicates that the phrase following the phrase "in response to" is one example of many suitable possibilities that may or may not be used in one or more of the various embodiments. The phrase "adopted / used" (or, equivalently, "at least adopted / used") indicates that the phrase following the phrase "adopted / used" is one example of many suitable possibilities that may or may not be used in one or more of various embodiments.

[0040] The term configured may relate to the capacity of a device, whether the device is in an operational or non-operational state. Configured may also refer to a particular setting of a device that affects the operational characteristics of the device, whether the device is in an operational or non-operational state. In other words, hardware, software, firmware, registers, memory values, etc. may be "configured" within a device, whether the device is in an operational or non-operational state, to provide the device with a particular characteristic. A term such as "a control message originating in a device" may mean that the control message has parameters that can be used to configure a particular characteristic in the device or can be used to implement a particular action in the device, whether the device is in an operational or non-operational state.

[0041] In this disclosure, a parameter (or equivalently referred to as a field, or information element: IE) can contain one or more information objects, which can contain one or more other objects. For example, if parameter (IE)N contains parameter (IE)M, which contains parameter (IE)K, which contains parameter (IE)J, then, e.g., N contains K and N contains J. In an example embodiment, when one or more messages contain multiple parameters, it means that a parameter of the multiple parameters is included in at least one of the one or more messages, but need not be included in each of the one or more messages.

[0042] Furthermore, many features presented above are described as optional through the use of "may" or through the use of parentheses. For the sake of brevity and readability, this disclosure does not explicitly describe each and every variation that may be obtained by selecting from a set of optional features. This disclosure should be construed as explicitly disclosing all such variations. For example, a system described as having three optional features can be embodied in seven ways, i.e., with only one of the three possible features, any two of the three features, or three of the three features.

[0043] Many of the elements described in the disclosed embodiments may be implemented as modules, where a module is defined as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure may be implemented in hardware, software in combination with hardware, firmware, wetware (e.g., hardware with biological elements), or a combination thereof, which may be behaviorally equivalent. For example, a module may be implemented in software routines written in a computer language configured to run on a hardware machine (C, C++, Fortran, Java, Basic, Matlab, etc.) or Simulink, Stateflow, GNU Octave, or LabVIEW MathScript. It may also be possible to implement modules using physical hardware that incorporates discrete or programmable analog, digital, and / or quantum hardware. Examples of programmable hardware include computers, microcontrollers, microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), and complex programmable logic devices (CPLDs). Computers, microcontrollers, and microprocessors are programmed using languages ​​such as assembly, C, C++, etc. FPGAs, ASICs, and CPLDs are often programmed using Hardware Description Languages ​​(HDLs) such as Verilog or VHSIC Hardware Description Language (VHDL), which configure the connections between the internal hardware modules with fewer functions of the programmable device. To achieve a functional modular result, the above techniques are often used in combination.

[0044] 1A illustrates an example of a mobile communication network 100 in which an embodiment of the present disclosure may be implemented. The mobile communication network 100 may be, for example, a public land mobile network (PLMN) run by a network operator. As shown in FIG. 1A, the mobile communication network 100 includes a core network (CN) 102, a radio access network (RAN) 104, and a wireless device 106.

[0045] The CN 102 may provide the wireless device 106 with an interface to one or more data networks (DNs), such as a public DN (e.g., the Internet), a private DN, and / or an intra-operator DN. As part of its interfacing function, the CN 102 may set up an end-to-end connection between the wireless device 106 and one or more DNs, authenticate the wireless device 106, and provide charging functionality.

[0046] The RAN 104 may connect the CN 102 to the wireless devices 106 via wireless communication over the air interface. As part of the wireless communication, the RAN 104 may provide scheduling, radio resource management, and retransmission protocols. The communication direction from the RAN 104 to the wireless devices 106 over the air interface is known as the downlink, and the communication direction from the wireless devices 106 to the RAN 104 over the air interface is known as the uplink. The downlink transmission may be separated from the uplink transmission using frequency division duplexing (FDD), time division duplexing (TDD), and / or some combination of the two duplexing techniques.

[0047] The term wireless device may be used throughout this disclosure to refer to and encompass any mobile or fixed (non-portable) device for which wireless communication is required or available. For example, a wireless device may be a phone, a smartphone, a tablet, a computer, a laptop, a sensor, a meter, a wearable device, an Internet of Things (IoT) device, a vehicular roadside unit (RSU), a relay node, an automobile, and / or any combination thereof. The term wireless device encompasses other terms, including user equipment (UE), user terminal (UT), access terminal (AT), mobile station, handset, wireless transmit / receive unit (WTRU), and / or wireless communication device.

[0048] The RAN 104 may include one or more base stations (not shown). The term base station may be used throughout this disclosure to refer to and encompass a Node B (associated with UMTS and / or 3G standards), an evolved Node B (eNB, associated with E-UTRA and / or 4G standards), a remote radio head (RRH), a baseband processing unit coupled to one or more RRHs, a repeater or relay node used to extend the coverage area of ​​a donor node, a next generation evolved Node B (ng-eNB), a generation Node B (gNB, associated with NR and / or 5G standards), an access point (AP, e.g., associated with WiFi or other suitable wireless communication standard), and / or any combination thereof. A base station may include at least one gNB central unit (gNB-CU) and at least one gNB distributed unit (gNB-DU).

[0049] The base stations included in the RAN 104 may include one or more sets of antennas for communicating over the air interface with the wireless devices 106. For example, one or more base stations may include three sets of antennas for controlling three cells (or sectors) respectively. The size of a cell may be determined by the range over which a receiver (e.g., a base station receiver) can successfully receive a transmission from a transmitter (e.g., a wireless device transmitter) operating in the cell. Together, the cells of the base stations may provide wireless coverage to the wireless devices 106 over a wide geographic area to support wireless device mobility.

[0050] In addition to three sector sites, other implementations of base stations are possible. For example, one or more base stations of the RAN 104 may be implemented as sector sites having more or less than three sectors. One or more base stations of the RAN 104 may be implemented as an access point, as a baseband processing unit coupled to multiple remote radio heads (RRHs), and / or as a repeater or relay node used to extend the coverage area of ​​a donor node. The baseband processing unit coupled to the RRHs may be part of a centralized or cloud RAN architecture, and the baseband processing unit may be centralized or virtualized within a pool of baseband processing units. The repeater node may amplify and rebroadcast the wireless signal received from the donor node. The relay node may perform the same / similar functions as the repeater node, but may decode the wireless signal received from the donor node and remove noise before amplifying and rebroadcasting the wireless signal.

[0051] The RAN 104 may be deployed as a homogeneous network of macrocell base stations with similar antenna patterns and similar high-level transmit power. The RAN 104 may be deployed as a heterogeneous network. In a heterogeneous network, small cell base stations may be used to provide small coverage areas, e.g., coverage areas that overlap with the relatively large coverage areas provided by macrocell base stations. Small coverage areas may be provided in areas of high data traffic (or so-called hot spots) or areas where macrocell coverage is weak. Examples of small cell base stations include, in order of decreasing coverage area, microcell base stations, picocell base stations, and femtocell or home base stations.

[0052] The Third Generation Partnership Project (3GPP®) was formed in 1998 to provide global standardization of specifications for mobile communication networks similar to the mobile communication network 100 of FIG. 1A. To date, 3GPP® has produced specifications for three generations of mobile networks: a third generation (3G) network known as Universal Mobile Telecommunications System (UMTS), a fourth generation (4G) network known as Long Term Evolution (LTE), and a fifth generation (5G) network known as 5G System (5GS). Embodiments of the present disclosure are described with reference to a RAN of a 3GPP® 5G network, referred to as Next Generation RAN (NG-RAN). The embodiments may be applicable to the RAN of other mobile communication networks, such as the RAN 104 of FIG. 1A, RANs of earlier 3G and 4G networks, and future networks yet to be specified (e.g., a 3GPP® 6G network). NG-RAN implements the 5G radio access technology known as New Radio (NR), and may be provisioned to implement other radio access technologies, including 4G radio access technologies or non-3GPP radio access technologies.

[0053] FIG. 1B illustrates another example mobile communication network 150 in which embodiments of the present disclosure may be implemented. The mobile communication network 150 may be, for example, a PLMN run by a network operator. As shown in FIG. 1B, the mobile communication network 150 includes a 5G core network (5G-CN) 152, an NG-RAN 154, and a UE 156A and a UE 156B (collectively, UE 156). These components may be implemented and operate in the same or similar manner as the corresponding components described with respect to FIG. 1A.

[0054] 5G-CN 152 provides UE 156 with an interface to one or more DNs, such as a public DN (e.g., Internet), a private DN, and / or an intra-operator DN. As part of the interface function, 5G-CN 152 may set up an end-to-end connection between UE 156 and one or more DNs, authenticate UE 156, and provide charging functions. Compared to the CNs of 3GPP 4G networks, the base of 5G-CN 152 may be a service-based architecture. This means that the architecture of the nodes constituting 5G-CN 152 may be defined as a network function that provides services via interfaces to other network functions. The network functions of 5G-CN 152 may be implemented in several ways: as network elements on dedicated or shared hardware, as software instances running on dedicated or shared hardware, or as virtualized functions instantiated on a platform (e.g., a cloud-based platform).

[0055] As shown in FIG. 1B, the 5G-CN 152 includes an Access and Mobility Management Function (AMF) 158A and a User Plane Function (UPF) 158B, as shown in FIG. 1B as one component AMF / UPF 158 for ease of explanation. The UPF 158B may act as a gateway between the NG-RAN 154 and one or more DNs. The UPF 158B may perform functions such as packet routing and forwarding, packet inspection and enforcement of user plane policy rules, traffic usage reporting, uplink classification to support routing of traffic flows to one or more DNs, quality of service (QoS) processing for the user plane (e.g., packet filtering, gating, uplink / downlink rate enforcement, and uplink traffic validation), downlink packet buffering, and downlink data notification triggers. The UPF 158B may act as an anchor point for intra / inter radio access technology (RAT) mobility, an external protocol (or packet) data unit (PDU) session point interconnected to one or more DNs, and / or a branching point to support multi-homed PDU sessions. The UE 156 may be configured to receive services via a PDU session, which is a logical connection between the UE and the DN.

[0056] The AMF 158A may perform functions such as termination of Non-Access Stratum (NAS) signaling, NAS signaling security, Access Stratum (AS) security control, inter-CN node signaling for mobility between 3GPP® access networks, idle mode UE reachability (e.g., control and execution of paging retransmissions), registration area management, intra-system and inter-system mobility support, access authentication, access authorization including checking roaming rights, mobility management control (subscription and policy), support for network slicing, and / or selection of a Session Management Function (SMF). NAS may refer to a function operating between the CN and the UE, and AS may refer to a function operating between the UE and the RAN.

[0057] 5G-CN 152 may include one or more additional network functions not shown in FIG. 1B for clarity. For example, 5G-CN 152 may include one or more of a Session Management Function (SMF), an NR Repository Function (NRF), a Policy Control Function (PCF), a Network Exposure Function (NEF), a Unified Data Management (UDM), an Application Function (AF), and / or an Authentication Server Function (AUSF).

[0058] The NG-RAN 154 may connect the 5G-CN 152 to the UE 156 via wireless communication over the air interface. The NG-RAN 154 may include one or more gNBs (collectively gNB 160), illustrated as gNB 160A and gNB 160B, and / or one or more ng-eNBs (collectively ng-eNB 162), illustrated as ng-eNB 162A and ng-eNB 162B. The gNBs 160 and ng-eNB 162 may more generally be referred to as base stations. The gNBs 160 and ng-eNB 162 may include one or more sets of antennas for communicating with the UE 156 over the air interface. For example, one or more of the gNBs 160 and / or one or more of the ng-eNBs 162 may include three sets of antennas for controlling three cells (or sectors), respectively. Together, the gNB160 and ng-eNB162 cells may provide radio coverage to the UE156 over a wide geographic area to support UE mobility.

[0059] As shown in FIG. 1B, the gNB 160 and / or the ng-eNB 162 may be connected to the 5G-CN 152 by an NG interface and to other base stations by an Xn interface. The NG and Xn interfaces may be established using direct physical connections and / or indirect connections over an underlying transport network, such as an Internet Protocol (IP) transport network. The gNB 160 and / or the ng-eNB 162 may be connected to the UE 156 by a Uu interface. For example, as shown in FIG. 1B, the gNB 160A may be connected to the UE 156A by a Uu interface. The NG, Xn, and Uu interfaces are associated with protocol stacks. The protocol stacks associated with the interfaces may be used by the network elements of FIG. 1B to exchange data and signaling messages and may include two planes: a user plane and a control plane. The user plane may process data of interest to a user. The control plane may process signaling messages of interest to the network elements.

[0060] The gNB 160 and / or ng-eNB 162 may be connected to one or more AMF / UPF functions of the 5G-CN 152, such as the AMF / UPF 158, by one or more NG interfaces. For example, the gNB 160A may be connected to the UPF 158B of the AMF / UPF 158 by an NG User Plane (NG-U) interface. The NG-U interface may provide for the provision of user plane PDUs between the gNB 160A and the UPF 158B (e.g., non-guaranteed delivery). The gNB 160A may be connected to the AMF 158A using an NG Control Plane (NG-C) interface. The NG-C interface may provide, for example, NG interface management, UE context management, UE mobility management, forwarding of NAS messages, paging, PDU session management, and configuration forwarding and / or alert message transmission.

[0061] The gNB 160 may provide NR user plane and control plane protocol terminations towards the UE 156 on the Uu interface. For example, the gNB 160A may provide NR user plane and control plane protocol terminations towards the UE 156A on the Uu interface associated with a first protocol stack. The ng-eNB 162 may provide Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards the UE 156 on the Uu interface, where E-UTRA refers to a 3GPP 4G radio access technology. For example, the ng-eNB 162B may provide E-UTRA user plane and control plane protocol terminations towards the UE 156B on the Uu interface associated with a second protocol stack.

[0062] The 5G-CN 152 has been described as being configured to handle NR and 4G radio access. Those skilled in the art will appreciate that it may be possible for the NR to connect to a 4G core network in a mode known as "non-standalone operation." In non-standalone operation, the 4G core network is used to provide (or at least support) control plane functions (e.g., initial access, mobility, and paging). Although only one AMF / UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may be connected to multiple AMF / UPF nodes to provide redundancy and / or load sharing across multiple AMF / UPF nodes.

[0063] 1B, interfaces between network elements (e.g., Uu, Xn, and NG interfaces) may be associated with protocol stacks that the network elements use to exchange data and signaling messages. The protocol stacks may include two planes: a user plane and a control plane. The user plane may handle data of interest to a user, and the control plane may handle signaling messages of interest to the network elements.

[0064] Figures 2A and 2B show examples of NR user plane and NR control plane protocol stacks, respectively, for the Uu interface between a UE 210 and a gNB 220. The protocol stacks shown in Figures 2A and 2B may be the same or similar to those used for the Uu interface between a UE 156A and a gNB 160A shown in Figure 1B, for example.

[0065] 2A shows an NR user plane protocol stack including five layers implemented in the UE 210 and the gNB 220. At the bottom of the protocol stack, physical layers (PHYs) 211 and 221 may provide transport services to the upper layers of the protocol stack and may correspond to layer 1 of the Open Systems Interconnection (OSI) model. The next four protocols above the PHYs 211 and 221 include media access control layers (MAC) 212 and 222, radio link control layers (RLC) 213 and 223, packet data convergence protocol layers (PDCP) 214 and 224, and service data application protocol layers (SDAP) 215 and 225. Together, these four protocols may constitute layer 2 or the data link layer of the OSI model.

[0066] FIG. 3 illustrates an example of services provided between protocol layers of the NR user plane protocol stack. Starting from the top of FIG. 2A and FIG. 3, the SDAPs 215 and 225 may perform QoS flow processing. The UE 210 may receive services via a PDU session, which may be a logical connection between the UE 210 and the DN. The PDU session may have one or more QoS flows. The UPF (e.g., UPF 158B) of the CN may map IP packets to one or more QoS flows of the PDU session based on the QoS requirements (e.g., in terms of delay, data rate, and / or error rate). The SDAPs 215 and 225 may perform mapping / de-mapping between one or more QoS flows and one or more data radio bearers. The mapping / de-mapping between the QoS flows and the data radio bearers may be determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210 may be informed of the mapping between the QoS flows and the data radio bearers via reflected mapping or control signaling received from the gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 may mark the downlink packets with a QoS flow indicator (QFI) that can be observed by the SDAP 215 at the UE 210 to determine mapping / demapping between QoS flows and data radio bearers.

[0067] PDCP 214 and PDCP 224 may perform header compression / decompression to reduce the amount of data that needs to be transmitted over the air interface, encryption / decryption to prevent unauthorized decryption of data transmitted over the air interface, and integrity protection (to ensure that control messages originate from the intended source). PDCP 214 and 224 may perform retransmission of untransmitted packets, in-sequence delivery and resequencing of packets, and elimination of duplicate received packets, for intra-gNB handover, for example. PDCP 214 and 224 may perform packet duplication to improve the likelihood of a packet being received and to eliminate any duplicate packets at the receiver. Packet duplication may be useful for services that require high reliability.

[0068] Although not shown in FIG. 3, the PDCPs 214 and 224 may perform mapping / demapping between split radio bearers and RLC channels in a dual connectivity scenario. Dual connectivity is a technique that allows a UE to connect to two cells, or more generally, two cell groups, a master cell group (MCG) and a secondary cell group (SCG). A split bearer is when a single radio bearer, such as one of the radio bearers provided by the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, is handled by a cell group in dual connectivity. The PDCPs 214 and 224 may map / demap the split radio bearer between the RLC channels belonging to the cell group.

[0069] The RLCs 213 and 223 may perform segmentation, retransmission through automatic repeat request (ARQ), and removal of duplicate data units received from the MACs 212 and 222, respectively. The RLCs 213 and 223 may support three transmission modes: transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). Based on the transmission mode in which the RLC is operating, the RLC may perform one or more of the indicated functions. This RLC configuration may be per logical channel independent of numerology and / or transmission time interval (TTI) duration. As shown in FIG. 3, the RLCs 213 and 223 may provide RLC channels as services to the PDCPs 214 and 224, respectively.

[0070] The MAC 212 and MAC 222 may perform multiplexing / demultiplexing of logical channels and / or mapping between logical channels and transport channels. Multiplexing / demultiplexing may include multiplexing / demultiplexing of data units belonging to one or more logical channels to / from transport blocks (TBs) delivered to / from the PHYs 211 and 221. The MAC 222 may be configured to perform scheduling, scheduling information reporting, and priority handling between UEs by dynamic scheduling. Scheduling may be performed at the gNB 220 (at the MAC 222) for downlink and uplink. The MAC 212 and 222 may be configured to perform error correction, priority handling between logical channels of the UE 210 by logical channel prioritization, and / or padding through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in case of carrier aggregation (CA)). The MAC 212 and MAC 222 may support one or more numerologies and / or transmission timings. In one embodiment, mapping restrictions on logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. As shown in Figure 3, MACs 212 and 222 can offer logical channels to RLCs 213 and 223 as services.

[0071] The PHYs 211 and 221 may perform mapping of transport channels to physical channels and digital and analog signal processing functions to transmit and receive information over the air interface. These digital and analog signal processing functions may include, for example, encoding / decoding and modulation / demodulation. The PHYs 211 and 221 may perform multi-antenna mapping. As shown in FIG. 3, the PHYs 211 and 221 may provide one or more transport channels to the MACs 212 and 222 as a service.

[0072] 4A illustrates an example of a downlink data flow through an NR user plane protocol stack. FIG. 4A illustrates a downlink data flow of three IP packets (n, n+1, and m) through the NR user plane protocol stack, generating two TBs at the gNB 220. The uplink data flow through the NR user plane protocol stack may be similar to the downlink data flow illustrated in FIG. 4A.

[0073] The downlink data flow in FIG. 4A begins when the SDAP 225 receives three IP packets from one or more QoS flows and maps the three packets to radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 to the first radio bearer 402 and maps IP packet m to the second radio bearer 404. An SDAP header (labeled "H" in FIG. 4A) is added to the IP packets. Data units from / to the higher protocol layer are called service data units (SDUs) of the lower protocol layer, and data units to / from the lower protocol layer are called protocol data units (PDUs) of the higher protocol layer. As shown in FIG. 4A, the data units from the SDAP 225 are the SDUs of the lower protocol layer PDCP 224 and the PDUs of the SDAP 225.

[0074] The remaining protocol layers in FIG. 4A may perform the relevant functions (e.g., with respect to FIG. 3), add corresponding headers, and forward the respective outputs to the next lower layer. For example, PDCP 224 may perform IP header compression and encryption and forward its output to RLC 223. RLC 223 may optionally perform segmentation (e.g., as shown for IP packet m in FIG. 4A) and forward its output to MAC 222. MAC 222 may multiplex several RLC PDUs and may attach MAC subheaders to the RLC PDUs to form a transport block. In NR, the MAC subheader may be distributed throughout the MAC PDU, as shown in FIG. 4A. In LTE, the MAC subheader may be placed entirely at the beginning of the MAC PDU. The NR MAC PDU structure may reduce processing time and associated delays because the MAC PDU subheaders may be calculated before the complete MAC PDU is assembled.

[0075] 4B shows an example format of a MAC subheader in a MAC PDU. The MAC subheader includes an SDU length field to indicate the length (e.g., in bytes) of the MAC SDU that the MAC subheader corresponds to, a logical channel identifier (LCID) field to identify the logical channel that the MAC SDU initiated to assist in the demultiplexing process, a flag (F) to indicate the size of the SDU length field, and a reserved bit (R) field for future use.

[0076] FIG. 4B further illustrates a MAC Control Element (CE) inserted into the MAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4B illustrates two MAC CEs inserted into the MAC PDU. The MAC CEs may be inserted at the beginning of the MAC PDU for downlink transmission (as shown in FIG. 4B) and at the end of the MAC PDU for uplink transmission. The MAC CEs may be used for in-band control signaling. Examples of MAC CEs include scheduling-related MAC CEs, such as buffer status reports and power headroom reports, activation / deactivation MAC CEs, such as for PDCP duplicate detection activation / deactivation, channel state information (CSI) reports, sounding reference signal (SRS) transmissions, and pre-configured components, discontinuous reception (DRX)-related MAC CEs, timing advance MAC CEs, and random access-related MAC CEs. The MAC CEs may be preceded by a MAC subheader of a format similar to that described for the MAC SDU and may be identified with a reserved value in the LCID field indicating the type of control information included in the MAC CE.

[0077] Before describing the NR control plane protocol stack, we first describe logical, transport, and physical channels and the mapping between channel types. One or more channels may be used to perform functions related to the NR control plane protocol stack, as described below.

[0078] 5A and 5B show the mapping between logical, transport, and physical channels for the downlink and uplink, respectively. Information is transmitted through channels between the RLC, MAC, and PHY of the NR protocol stack. Logical channels can be used between the RLC and MAC and can be classified as control channels, which carry control and configuration information in the NR control plane, or as traffic channels, which carry data in the NR user plane. Logical channels can be classified as dedicated logical channels, which are dedicated to a particular UE, or as common logical channels, which can be used by multiple UEs. Logical channels can also be defined by the type of information they carry. The set of logical channels defined by NR includes, for example, - a paging control channel (PCCH) for displaying paging messages used to page UEs whose location is not known to the network at the cell level; A Broadcast Control Channel (BCCH) for conveying system information messages in the form of a Master Information Block (MIB) and several System Information Blocks (SIBs), which may be used by UEs to obtain information about how the cell is configured and how to operate within the cell; and - a Common Control Channel (CCCH) for transmitting control messages together with random access; - a dedicated control channel (DCCH) for transmitting control messages to and from a specific UE to configure the UE; - Dedicated Traffic Channel (DTCH) for transmitting user data to and from a specific UE.

[0079] Transport channels are used between the MAC and PHY layers and may be defined by how they transmit the information they transmit over the air interface. The set of transport channels defined by NR includes, for example: A paging channel (PCH) for transmitting paging messages originating from the PCCH; - a Broadcast Channel (BCH) for carrying the MIB from the BCCH; - a downlink shared channel (DL-SCH) for transmission of downlink data and signaling messages, including SIBs from the BCCH; - an uplink shared channel (UL-SCH) for transmitting uplink data and signaling messages; A Random Access Channel (RACH) that allows a UE to connect to the network without prior scheduling.

[0080] The PHY can pass information between processing levels of the PHY using physical channels. A physical channel may have an associated set of time-frequency resources for carrying information of one or more transport channels. The PHY generates control information to support the lower level operation of the PHY and may provide control information to the lower levels of the PHY via physical control channels known as L1 / L2 control channels. The set of physical channels and physical control channels defined by NR includes, for example: - a Physical Broadcast Channel (PBCH) for carrying the MIB from the BCH; A Physical Downlink Shared Channel (PDSCH) for carrying downlink data and signaling messages from the DL-SCH and paging messages from the PCH; A Physical Downlink Control Channel (PDCCH) for carrying downlink control information (DCI), which may include downlink scheduling commands, uplink scheduling grants, and uplink power control commands; A physical uplink shared channel (PUSCH) for carrying uplink data and signaling messages from the UL-SCH and, in some examples, uplink control information (UCI) as described below; A physical uplink control channel (PUCCH) for carrying UCI, which may include a HARQ acknowledgement, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (RI), and a scheduling request (SR); A Physical Random Access Channel (PRACH) for random access.

[0081] Similar to the physical control channel, the physical layer generates physical signals to support the low-level operations of the physical layer. As shown in Figures 5A and 5B, the physical layer signals defined by NR include the Primary Synchronization Signal (PSS), the Secondary Synchronization Signal (SSS), the Channel State Information Reference Signal (CSI-RS), the Demodulation Reference Signal (DMRS), the Sounding Reference Signal (SRS), and the Phase Tracking Reference Signal (PT-RS). These physical layer signals are described in more detail below.

[0082] 2B shows an example of an NR control plane protocol stack. In FIG. 2B, the NR control plane protocol stack may use the first four protocol layers that are the same / similar to the example NR user plane protocol stack. These four protocol layers include PHY 211 and 221, MAC 212 and 222, RLC 213 and 223, and PDCP 214 and 224. Instead of having SDAP 215 and 225 at the top of the stack as in the NR user plane protocol stack, the NR control plane stack has radio resource control (RRC) 216 and 226, and NAS protocols 217 and 237 at the top of the NR control plane protocol stack.

[0083] The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 (e.g., AMF 158A), or more generally, between the UE 210 and the CN. The NAS protocols 217 and 237 may provide control plane functions between the UE 210 and the AMF 230 via signaling messages called NAS messages. There is no direct path between the UE 210 and the AMF 230 over which NAS messages can be transmitted. NAS messages may be transmitted using the AS of the Uu and NG interfaces. The NAS protocols 217 and 237 may provide control plane functions such as authentication, security, connection setup, mobility management, and session management.

[0084] The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220, or more generally, between the UE 210 and the RAN. The RRCs 216 and 226 may provide a control plane function between the UE 210 and the gNB 220 via signaling messages called RRC messages. The RRC messages may be transmitted between the UE 210 and the RAN using signaling radio bearers and the same / similar PDCP, RLC, MAC, and PHY protocol layers. The MAC may multiplex the control plane and user plane data within the same transport block (TB). The RRCs 216 and 226 may provide control plane functions such as broadcasting system information related to the AS and the NAS, paging initiated by the CN or the RAN, establishment, maintenance, and release of an RRC connection between the UE 210 and the RAN, security functions including key management, establishment, configuration, maintenance, and release of signaling and data radio bearers, mobility functions, QoS management functions, control of UE measurement reporting and reporting, radio link failure (RLF) detection and recovery, and / or NAS message forwarding. As part of establishing an RRC connection, the RRCs 216 and 226 may establish an RRC context, which may involve setting parameters for communications between the UE 210 and the RAN.

[0085] FIG. 6 is an example diagram illustrating RRC state transitions of a UE. The UE may be the same as or similar to the wireless device 106 shown in FIG. 1A, the UE 210 shown in FIG. 2A and FIG. 2B, or any other wireless device described in this disclosure. As shown in FIG. 6, the UE may be in at least one of three RRC states: RRC connected 602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRC inactive 606 (e.g., RRC_INACTIVE).

[0086] In the RRC connection 602, the UE has an established RRC context and may have at least one RRC connection with a base station. The base station may be similar to one of one or more base stations included in the RAN 104 shown in FIG. 1A, one of the gNB 160 or ng-eNB 162 shown in FIG. 1B, the gNB 220 shown in FIG. 2A and FIG. 2B, or any other base station described in this disclosure. The base station to which the UE is connected may have an RRC context for the UE. The RRC context, referred to as the UE context, may include parameters for communication between the UE and the base station. These parameters may include, for example, one or more AS contexts, one or more radio link configuration parameters, bearer configuration information (e.g., related to data radio bearers, signaling radio bearers, logical channels, QoS flows, and / or PDU sessions), security information, and / or PHY, MAC, RLC, PDCP, and / or SDAP layer configuration information. In the RRC connection 602, the mobility of the UE may be managed by the RAN (e.g., the RAN 104 or the NG-RAN 154). The UE may measure signal levels (e.g., reference signal levels) from the serving cell and neighboring cells and report these measurements to the base station currently serving the UE. The UE's serving base station may request a handover to a cell of one of the neighboring base stations based on the reported measurements. The RRC state may transition from RRC Connected 602 to RRC Idle 604 via a Connection Release procedure 608 or to RRC Inactive 606 via a Connection Deactivation procedure 610.

[0087] In RRC Idle 604, no RRC context may be established for the UE. In RRC Idle 604, the UE may not have an RRC connection with a base station. During RRC Idle 604, the UE may be in a sleep state most of the time (e.g., to conserve battery power). The UE may wake up periodically (e.g., once every discontinuous reception cycle) to monitor for paging messages from the RAN. UE mobility may be managed by the UE through a procedure known as cell reselection. The RRC state may transition from RRC Idle 604 to RRC Connected 602 via a connection establishment procedure 612, which may involve a random access procedure as discussed in more detail below.

[0088] In RRC Inactive 606, previously established RRC context is maintained in the UE and base station. This allows for faster transition to RRC Connected 602 with reduced signaling overhead compared to transition from RRC Idle 604 to RRC Connected 602. In RRC Inactive 606, the UE is in a sleep state and UE mobility may be managed by the UE through cell reselection. The RRC state may transition from RRC Inactive 606 to RRC Connected 602 by a Connection Resume procedure 614 or to RRC Idle 604 via a Connection Release procedure 616 that is the same as or similar to the Connection Release procedure 608.

[0089] The RRC states may be associated with mobility management mechanisms. In RRC Idle 604 and RRC Inactive 606, mobility is managed by the UE through cell reselection. The purpose of mobility management in RRC Idle 604 and RRC Inactive 606 is to allow the network to inform the UE of events via paging messages without broadcasting the paging messages throughout the entire mobile communication network. The mobility management mechanisms used in RRC Idle 604 and RRC Inactive 606 may allow the network to track the UE on a cell group level, so that paging messages may be broadcast on cells of the cell group in which the UE is currently located instead of the entire mobile communication network. The mobility management mechanisms in RRC Idle 604 and RRC Inactive 606 track the UE on a cell group level. They may do so using different granularity of grouping. For example, there may be three levels of granularity of cell grouping: individual cells, cells within a RAN area identified by a RAN Area Identifier (RAI), and cells within a group of RAN areas called tracking areas and identified by a Tracking Area Identifier (TAI).

[0090] The tracking area may be used to track the UE at the CN level. The CN (e.g., CN 102 or 5G-CN 152) may provide the UE with a list of TAIs associated with the UE registration area. If the UE moves through cell reselection to a cell associated with a TAI that is not included in the list of TAIs associated with the UE registration area, the UE may perform a registration update with the CN to allow the CN to update the UE's location and provide the UE with a new UE registration area.

[0091] The RAN area may be used to track the UE at the RAN level. For a UE in RRC inactive 606 state, the UE may be assigned a RAN notification area. The RAN notification area may include one or more cell identities, a list of RAIs, or a list of TAIs. In one embodiment, a base station may belong to one or more RAN notification areas. In one embodiment, a cell may belong to one or more RAN notification areas. If the UE moves through cell reselection to a cell that is not included in the RAN notification area assigned to the UE, the UE may perform a notification area update with the RAN to update the RAN notification area of ​​the UE.

[0092] A base station that stores an RRC context for a UE or a last serving base station for the UE may be referred to as an anchor base station. The anchor base station may maintain the RRC context for the UE at least during the time the UE remains in the RAN notification area of ​​the anchor base station and / or during the time the UE remains in RRC inactive 606.

[0093] A gNB, such as gNB 160 in FIG. 1B, can be divided into two parts: a central unit (gNB-CU) and one or more distributed units (gNB-DU). The gNB-CU can be coupled to one or more gNB-DUs using an F1 interface. The gNB-CU can include RRC, PDCP, and SDAP. The gNB-DU can include RLC, MAC, and PHY.

[0094] In NR, physical signals and physical channels (FIGS. 5A and 5B) may be mapped onto orthogonal frequency division multiplexing (OFDM) symbols. OFDM is a multicarrier communication scheme that transmits data on F orthogonal subcarriers (or tones). Before transmission, the data may be mapped to a series of complex symbols (e.g., M-quadrature amplitude modulation (M-QAM) or M-phase shift keying (M-PSK) symbols), which are called source symbols and are split into F parallel symbol streams. The F parallel symbol streams may be treated as if they were in the frequency domain and used as input to an inverse fast Fourier transform (IFFT) block that transforms them to the time domain. The IFFT block may take F source symbols, one at a time, from each of the F parallel symbol streams and use each source symbol to modulate the amplitude and phase of one of the F sinusoidal basis functions corresponding to the F orthogonal subcarriers. The output of the IFFT block may be F time domain samples that represent a sum of the F orthogonal subcarriers. The F time domain samples may form a single OFDM symbol. After some processing (e.g., adding a cyclic prefix) and upconversion, the OFDM symbols provided by the IFFT block may be transmitted over the air interface at a carrier frequency. The F parallel symbol streams may be mixed using an FFT block before being processed by the IFFT block. This processing produces Discrete Fourier Transform (DFT) pre-coded OFDM symbols, which can be used by UEs in the uplink to reduce the peak-to-average power ratio (PAPR). Inverse processing may be performed on the OFDM symbols at the receiver using an FFT block to recover the data mapped to the source symbols.

[0095] FIG. 7 shows an example of an NR frame configuration in which OFDM symbols are grouped. The NR frame may be identified by a system frame number (SFN). The SFN may repeat at a period of 1024 frames. As shown, one NR frame may be 10 milliseconds (ms) in duration and may include 10 subframes, each of which is 1 ms in duration. The subframes may be divided into slots, each of which includes, for example, 14 OFDM symbols per slot.

[0096] The duration of a slot may depend on the numerology used for the OFDM symbol of the slot. In NR, flexible numerology is supported to accommodate different cell deployments (e.g., cells with carrier frequencies less than 1 GHz up to cells with carrier frequencies in the mm-wave range). Numerology may be defined in terms of subcarrier spacing and cyclic prefix duration. For numerology in NR, subcarrier spacing may be scaled up by powers of two from a baseline subcarrier spacing of 15 kHz, and cyclic prefix duration may be scaled down by powers of two from a baseline cyclic prefix duration of 4.7 μs. For example, NR defines numerology with the following subcarrier spacing / cyclic prefix duration combinations: 15 kHz / 4.7 μs, 30 kHz / 2.3 μs, 60 kHz / 1.2 μs, 120 kHz / 0.59 μs, and 240 kHz / 0.29 μs.

[0097] A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols). Numerologies with higher subcarrier spacing have shorter slot durations and correspondingly more slots per subframe. Figure 7 illustrates this numerology-dependent slot duration and slot-per-subframe transmission structure (for ease of illustration, a numerology with 240 kHz subcarrier spacing is not shown in Figure 7). Subframes in NR may be used as numerology-independent time references, while slots may be used as units around which uplink and downlink transmissions are scheduled. To support low latency, scheduling in NR is decoupled from slot duration and may start with any OFDM symbol and end with as many symbols as necessary for transmission. These partial slot transmissions may be referred to as minislot or subslot transmissions.

[0098] FIG. 8 shows an example of a slot configuration in the time and frequency domain of an NR carrier. A slot includes resource elements (REs) and resource blocks (RBs). An RE is the smallest physical resource in NR. An RE spans one OFDM symbol in the time domain by one subcarrier in the frequency domain as shown in FIG. 8. An RB spans 12 consecutive REs in the frequency domain as shown in FIG. 8. An NR carrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers. Such limitations, if used, may limit an NR carrier to 50, 100, 200, and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz, respectively, and the 400 MHz bandwidth may be set based on the 400 MHz per carrier bandwidth limitation.

[0099] Figure 8 shows a single numerology used across the entire bandwidth of an NR carrier. In other example configurations, multiple numerologies may be supported on the same carrier.

[0100] NR may support a wide range of carrier bandwidths (e.g., up to 400 MHz with 120 kHz subcarrier spacing). Not all UEs may be able to receive the full carrier bandwidth (e.g., hardware limitations, etc.). Also, receiving the full carrier bandwidth may be prohibitive from a UE power consumption perspective. In one embodiment, to reduce power consumption and / or for other purposes, the UE may adapt the size of its reception bandwidth based on the amount of traffic the UE plans to receive. This is referred to as bandwidth adaptation.

[0101] NR defines a bandwidth portion (BWP) to support UEs that cannot receive the entire carrier bandwidth and to support bandwidth adaptation. In one embodiment, a BWP may be defined by a subset of contiguous RBs on a carrier. A UE may be configured (e.g., via the RRC layer) with one or more downlink BWPs and one or more uplink BWPs per serving cell (e.g., up to four downlink BWPs and up to four uplink BWPs per serving cell). At a given time, one or more of the BWPs configured for a serving cell may be active. These one or more BWPs may be referred to as the active BWPs of the serving cell. When a serving cell is configured with a secondary uplink carrier, the serving cell may have one or more first active BWPs on the uplink carrier and one or more second active BWPs on the secondary uplink carrier.

[0102] For unpaired spectrum, a downlink BWP from a set of configured downlink BWPs may be linked with an uplink BWP from a set of configured uplink BWPs if the downlink BWP index of the downlink BWP and the uplink BWP index of the uplink BWP are the same. For unpaired spectrum, the UE may expect the center frequency of the downlink BWP to be the same as the center frequency of the uplink BWP.

[0103] For a downlink BWP in a set of configured downlink BWPs on a primary cell (PCell), the base station may configure the UE with one or more control resource sets (CORESETs) for at least one search space. A search space is a set of locations in the time and frequency domain where the UE can find control information. The search space may be a UE-specific search space or a common search space (potentially usable by multiple UEs). For example, the base station may configure the UE with a common search space on a PCell or a primary secondary cell (PSCell) in an active downlink BWP.

[0104] For an uplink BWP in a set of configured uplink BWPs, the BS may configure the UE with one or more resource sets for one or more PUCCH transmissions. The UE may receive downlink receptions (e.g., PDCCH or PDSCH) in the downlink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix duration) for the downlink BWP. The UE may transmit uplink transmissions (e.g., PUCCH or PUSCH) in the uplink BWP according to the configured numerology (e.g., subcarrier spacing and cyclic prefix length for the uplink BWP).

[0105] One or more BWP indicator fields may be provided in the downlink control information (DCI). The value of the BWP indicator field may indicate which BWP of a set of configured BWPs is an active downlink BWP for one or more downlink receptions. The value of the one or more BWP indicator fields may indicate an active uplink BWP for one or more uplink transmissions.

[0106] The base station may semi-statically configure the UE with a default downlink BWP in a set of configured downlink BWPs associated with the PCell. If the base station does not provide a default downlink BWP for the UE, the default downlink BWP may be the initial active downlink BWP. The UE may determine which BWP is the initial active downlink BWP based on the CORESET configuration obtained using the PBCH.

[0107] The base station may configure the UE with a BWP inactivity timer value for the PCell. The UE may start or restart the BWP inactivity timer at any appropriate time. For example, the UE may start or restart the BWP inactivity timer when (a) the UE detects a DCI indicating an active downlink BWP other than a default downlink BWP for paired spectrum operation, or (b) the UE detects a DCI indicating an active downlink BWP or an active uplink BWP other than a default downlink BWP or an uplink BWP for unpaired spectrum operation. If the UE does not detect a DCI for a certain period of time (e.g., 1 ms or 0.5 ms), the UE may run the BWP inactivity timer towards expiration (e.g., increasing it from zero to the BWP inactivity timer value or decreasing it from the BWP inactivity timer value to zero). When the BWP inactivity timer expires, the UE may be switched from the active downlink BWP to the default downlink BWP.

[0108] In one embodiment, a base station may semi-statically configure a UE with one or more BWPs, and the UE may switch the active BWP from a first BWP to a second BWP in response to receiving a DCI indicating the second BWP as the active BWP and / or in response to expiration of a BWP inactivity timer (e.g., if the second BWP is a default BWP).

[0109] Downlink and uplink BWP switching (BWP switching refers to switching from a currently active BWP to a currently not active BWP) may be performed independently in paired spectrum. In unpaired spectrum, downlink and uplink BWP switching may be performed simultaneously. Switching between configured BWPs may occur based on RRC signaling, DCI, expiration of a BWP inactivity timer, and / or initiation of random access.

[0110] FIG. 9 illustrates an example of bandwidth adaptation using three configured BWPs for an NR carrier. A UE configured with three BWPs may switch from one BWP to another BWP at a switching point. In the example illustrated in FIG. 9, the BWPs include BWP 902 with a bandwidth of 40 MHz and a subcarrier spacing of 15 kHz, BWP 904 with a bandwidth of 10 MHz and a subcarrier spacing of 15 kHz, and BWP 906 with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. BWP 902 may be the initial active BWP, and BWP 904 may be the default BWP. The UE may switch between the BWPs at a switching point. In the example of FIG. 9, the UE may switch from BWP 902 to BWP 904 at switching point 908. The switching at switching point 908 may occur for any suitable reason, for example, in response to expiration of a BWP inactivity timer (indicating switching to the default BWP) and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 906 at switching point 910 in response to receiving a DCI indicating BWP 906 as the active BWP. The UE may switch from the active BWP 906 to BWP 904 at switching point 912 in response to expiration of a BWP inactivity timer and / or in response to receiving a DCI indicating BWP 904 as the active BWP. The UE may switch from the active BWP 904 to BWP 902 at switching point 914 in response to receiving a DCI indicating BWP 902 as the active BWP.

[0111] If the UE is configured for a secondary cell with a default downlink BWP in the set of configured downlink BWPs and timer values, the UE procedures for switching the BWP on the secondary cell may be the same / similar to those on the primary cell, e.g., the UE may use timer values ​​and default downlink BWPs for the secondary cell in the same / similar manner that the UE uses these values ​​for the primary cell.

[0112] To provide a larger data rate, carrier aggregation (CA) can be used to aggregate two or more carriers and transmit simultaneously to and from the same UE. The aggregated carriers in CA may be called component carriers (CCs). When using CA, there are many serving cells for the UE and one cell for the CC. The CC can have three configurations in the frequency domain:

[0113] 10A shows three CA configurations with two CCs. In the intra-band, contiguous configuration 1002, the two CCs are aggregated in the same frequency band (frequency band A) and are located immediately adjacent to each other in the frequency band. In the intra-band, non-contiguous configuration 1004, the two CCs are aggregated in the same frequency band (frequency band A) and are separated in frequency bands by a gap. In the intra-band configuration 1006, the two CCs are located in frequency bands (frequency band A and frequency band B).

[0114] In one embodiment, up to 32 CCs may be aggregated. The aggregated CCs may have the same or different bandwidths, subcarrier spacing, and / or duplexing schemes (TDD or FDD). A serving cell of a UE using CA may have a downlink CC. For FDD, one or more uplink CCs may optionally be configured for the serving cell. Being able to aggregate more downlink carriers than uplink carriers may be useful, for example, when a UE has more data traffic in the downlink than in the uplink.

[0115] When using CA, one of the aggregation cells of the UE may be referred to as a primary cell (PCell). The PCell may be a serving cell to which the UE initially connects in RRC connection establishment, re-establishment, and / or handover. The PCell may provide the UE with NAS mobility information and security inputs. The UE may have different PCells. In the downlink, the carrier corresponding to the PCell may be referred to as a downlink primary CC (DL PCC). In the uplink, the carrier corresponding to the PCell may be referred to as an uplink primary CC (UL PCC). The other aggregation cells of the UE may be referred to as secondary cells (SCells). In one embodiment, the SCell may be configured after the PCell is configured for the UE. For example, the SCell may be configured via an RRC connection reconfiguration procedure. In the downlink, the carrier corresponding to the SCell may be referred to as a downlink secondary CC (DL SCC). In the uplink, the carrier corresponding to the SCell may be referred to as an uplink secondary CC (UL SCC).

[0116] A configured SCell for a UE may be activated and deactivated based on, for example, traffic and channel conditions. Deactivation of a SCell may mean that PDCCH and PDSCH reception on the SCell is deactivated and PUSCH, SRS, and CQI transmission on the SCell is deactivated. A configured SCell may be activated and deactivated using a MAC CE with respect to FIG. 4B. For example, the MAC CE may use a bitmap (e.g., one bit per SCell) to indicate which SCell (e.g., among a subset of configured SCells) for a UE is activated or deactivated. A configured SCell may be deactivated in response to expiration of a SCell deactivation timer (e.g., one SCell deactivation timer per SCell).

[0117] Downlink control information such as a cell's scheduling assignment and scheduling grant may be transmitted on the cell corresponding to the assignment and grant, known as self-scheduling. DCI for a cell may be transmitted on another cell, known as cross-carrier scheduling. Uplink control information for aggregation cells (e.g., HARQ acknowledgement and channel state feedback such as CQI, PMI, and / or RI) may be transmitted on the PUCCH of the PCell. A large number of aggregated downlink CCs may overload the PUCCH of the PCell. A cell may be divided into multiple PUCCH groups.

[0118] FIG. 10B illustrates an example of how aggregation cells may be configured into one or more PUCCH groups. The PUCCH group 1010 and the PUCCH group 1050 may each include one or more downlink CCs. In the example of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: PCell 1011, SCell 1012, and SCell 1013. The PUCCH group 1050 includes three downlink CCs: PCell 1051, SCell 1052, and SCell 1053 in this example. One or more uplink CCs may be configured as PCell 1021, SCell 1022, and SCell 1023. One or more other uplink CCs may be configured as Primary SCell (PSCell) 1061, SCell 1062, and SCell 1063. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1010, denoted as UCI 1031, UCI 1032, and UCI 1033, may be transmitted on the uplink of PCell 1021. Uplink control information (UCI) associated with downlink CCs of PUCCH group 1050, denoted as UCI 1071, UCI 1072, and UCI 1073, may be transmitted on the uplink of PSCell 1061. In one embodiment, if the aggregation cells depicted in FIG. 10B are not divided into PUCCH group 1010 and PUCCH group 1050, a single uplink PCell and PCell for transmitting UCI associated with downlink CCs may be overloaded. By dividing the transmission of UCI between PCell 1021 and PSCell 1061, the overload may be prevented.

[0119] A cell including a downlink carrier and an optional uplink carrier may be assigned a physical cell ID and a cell index. The physical cell ID or cell index may identify the downlink carrier and / or uplink carrier of a cell, depending on, for example, the context in which the physical cell ID is used. The physical cell ID may be determined using a synchronization signal transmitted on a downlink component carrier. The cell index may be determined using an RRC message. In this disclosure, the physical cell ID may be referred to as a carrier ID. The cell index may be referred to as a carrier index. For example, when this disclosure refers to a first physical cell ID for a first downlink carrier, this disclosure may mean that the first physical cell ID is for a cell including the first downlink carrier. The same concept may apply, for example, to carrier activation. When this disclosure indicates that a first carrier is activated, this specification may mean that the cell including the first carrier is activated.

[0120] In CA, the multi-carrier nature of the PHY may be exposed to the MAC. In one embodiment, a HARQ entity may operate on a serving cell. Transport blocks may be generated per assignment / grant per serving cell. Transport blocks and potential HARQ retransmissions of transport blocks may be mapped to the serving cell.

[0121] In the downlink, a base station may transmit (e.g., unicast, multicast, and / or broadcast) one or more reference signals (RS) (e.g., PSS, SSS, CSI-RS, DMRS, and / or PT-RS as shown in FIG. 5A) to the UE. In the uplink, the UE may transmit one or more RS to the base station (e.g., DMRS, PT-RS, and / or SRS as shown in FIG. 5B). The PSS and SSS may be transmitted by the base station and used by the UE to synchronize the UE to the base station. The PSS and SSS may be provided in a synchronization signal (SS) / physical broadcast channel (PBCH) block that includes the PSS, SSS, and PBCH. The base station may periodically transmit bursts of the SS / PBCH block.

[0122] FIG. 11A illustrates an example of a structure and location of an SS / PBCH block. A burst of SS / PBCH blocks may include one or more SS / PBCH blocks (e.g., four SS / PBCH blocks as shown in FIG. 11A). A burst may be transmitted periodically (e.g., every two frames or every 20 ms). A burst may be limited to a half frame (e.g., the first half frame having a duration of 5 ms). It will be appreciated that FIG. 11A is an example, and these parameters (number of SS / PBCH blocks per burst, periodicity of the burst, location of the burst within a frame) may be configured based on, for example, the carrier frequency of the cell in which the SS / PBCH block is transmitted, the numerology or subcarrier spacing of the cell, configuration by the network (e.g., using RRC signaling), or any other suitable factor. In one example, the UE may assume a subcarrier spacing for the SS / PBCH block based on the monitored carrier frequency, unless the wireless network configures the UE to assume a different subcarrier spacing.

[0123] An SS / PBCH block may span one or more OFDM symbols in the time domain (e.g., four OFDM symbols as shown in the example of FIG. 11A) and one or more subcarriers in the frequency domain (e.g., 240 consecutive subcarriers). The PSS, SSS, and PBCH may have a common center frequency. The PSS may be transmitted first and may span, for example, one OFDM symbol and 127 subcarriers. The SSS may be transmitted after the PSS (e.g., the last two symbols) and may span one OFDM symbol and 127 subcarriers. The PBCH may be transmitted after the PSS (e.g., over the next three OFDM symbols) and may span 240 subcarriers.

[0124] The location of the SS / PBCH block in the time and frequency domain may not be known to the UE (e.g., when the UE is searching for a cell). To find and select a cell, the UE may monitor the carrier for a PSS. For example, the UE may monitor a frequency location within the carrier. If the PSS is not found after a certain period of time (e.g., 20 ms), the UE may search for a PSS at a different frequency location within the carrier as indicated by the synchronization raster. If the PSS is found at a location in the time and frequency domain, the UE may determine the location of the SSS and PBCH, respectively, based on the known structure of the SS / PBCH block. The SS / PBCH block may be a cell-defined SS block (CD-SSB). In one embodiment, a primary cell may be associated with a CD-SSB. The CD-SSB may be located on the synchronization raster. In one embodiment, cell selection / search and / or reselection may be based on the CD-SSB.

[0125] The SS / PBCH block may be used by the UE to determine one or more parameters of the cell. For example, the UE may determine a physical cell identifier (PCI) of the cell based on the PSS and SSS sequences, respectively. The UE may determine a location of a frame boundary of the cell based on the location of the SS / PBCH block. For example, the SS / PBCH block may indicate that it was transmitted according to a transmission pattern, where the SS / PBCH block is a known distance from a frame boundary.

[0126] The PBCH may use QPSK modulation and may use forward error correction (FEC). The FEC may use polar coding. One or more symbols spanned by the PBCH may carry one or more DMRS for demodulation of the PBCH. The PBCH may include an indication of the cell's current system frame number (SFN) and / or SS / PBCH block timing index. These parameters may facilitate time synchronization of the UE to the base station. The PBCH may include a Master Information Block (MIB) used to provide one or more parameters to the UE. The MIB may be used by the UE to find the remaining minimum system information (RMSI) associated with the cell. The RMSI may include a System Information Block Type 1 (SIB1). The SIB1 may include information necessary for the UE to access the cell. The UE may use one or more parameters of the MIB to monitor the PDCCH, which may be used to schedule the PDSCH. The PDSCH may include SIB1. The SIB1 may be decoded using the parameters provided in the MIB. The PBCH may indicate the absence of SIB1. Based on the PBCH indicating that SIB1 is not present, the UE may point to a frequency, and the UE may search for an SS / PBCH block on the frequency to which the UE is pointed.

[0127] The UE may assume that one or more SS / PBCH blocks transmitted with the same SS / PBCH block index are quasi-co-located (QCL'd) (e.g., have the same / similar Doppler spread, Doppler shift, average gain, average delay, and / or spatial Rx parameters). The UE may not assume that the QCL's for the SS / PBCH block transmissions have different SS / PBCH block indices.

[0128] SS / PBCH blocks (e.g., blocks within a half frame) may be transmitted in spatial directions (e.g., using different beams across the coverage area of ​​a cell). In one embodiment, a first SS / PBCH block may be transmitted in a first spatial direction using a first beam, and a second SS / PBCH block may be transmitted in a second spatial direction using a second beam.

[0129] In one embodiment, within the frequency span of a carrier, a base station may transmit multiple SS / PBCH blocks. In one embodiment, a first PCI of a first SS / PBCH block of the multiple SS / PBCH blocks may be different from a second PCI of a second SS / PBCH block of the multiple SS / PBCH blocks. The PCIs of SS / PBCH blocks transmitted at different frequency locations may be different or may be the same.

[0130] The CSI-RS may be transmitted by a base station and used by a UE to obtain channel state information (CSI). The base station may configure the UE with one or more CSI-RS for channel estimation or any other suitable purpose. The base station may configure the UE with one or more of the same / similar CSI-RS. The UE may measure one or more CSI-RS. The UE may estimate downlink channel conditions and / or generate a CSI report based on measurements of one or more downlink CSI-RS. The UE may provide the CSI report to the base station. The base station may perform link adaptation using feedback provided by the UE (e.g., estimated downlink channel conditions).

[0131] A base station may semi-statically configure a UE with one or more CSI-RS resource sets. The CSI-RS resources may be associated with a location and periodicity in the time and frequency domain. The base station may selectively activate and / or deactivate CSI-RS resources. The base station may indicate to the UE that CSI-RS resources in a CSI-RS resource set are activated and / or deactivated.

[0132] The base station may configure the UE to report CSI measurements. The base station may configure the UE to provide CSI reports periodically, aperiodically, or semi-persistently. For periodic CSI reporting, the UE may be configured with the timing and / or periodicity of the CSI reports. For aperiodic CSI reporting, the base station may request the CSI reports. For example, the base station may instruct the UE to measure configured CSI-RS resources and provide CSI reports on the measurements. For semi-persistent CSI reporting, the base station may configure the UE to send periodic reports periodically and selectively start or stop. The base station may configure the UE with the CSI-RS resource set and CSI reports using RRC signaling.

[0133] The CSI-RS configuration may include, for example, one or more parameters indicating up to 32 antenna ports. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and control resource set (CORESET) if the downlink CSI-RS and CORESET are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside of a physical resource block (PRB) configured for CORESET. The UE may be configured to use the same OFDM symbol for the downlink CSI-RS and SS / PBCH block if the downlink CSI-RS and SS / PBCH block are spatially QCL'd and resource elements associated with the downlink CSI-RS are outside of a PRB configured for the SS / PBCH block.

[0134] The downlink DMRS may be transmitted by a base station and may be used by a UE for channel estimation. For example, the downlink DMRS may be used for coherent demodulation of one or more downlink physical channels (e.g., PDSCH). An NR network may support one or more variable and / or configurable DMRS patterns for data demodulation. At least one downlink DMRS configuration may support a frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statically configure the UE with the number (e.g., maximum number) of frontloaded DMRS symbols of the PDSCH. The DMRS configuration may support one or more DMRS ports. For example, in the case of single-user MIMO, the DMRS configuration may support up to eight orthogonal downlink DMRS ports per UE. In the case of multi-user MIMO, the DMRS configuration may support up to four orthogonal downlink DMRS ports per UE. The wireless network may support a common DMRS structure for downlink and uplink (e.g., at least for CP-OFDM). The DMRS position, DMRS pattern, and / or scrambling sequence may be the same or different. The base station may transmit the downlink DMRS and corresponding PDSCH using the same precoding matrix. The UE may use one or more downlink DMRS for coherent demodulation / channel estimation of the PDSCH.

[0135] In one embodiment, a transmitter (e.g., a base station) may use a precoder matrix for a portion of a transmission bandwidth. For example, the transmitter may use a first precoder matrix for a first bandwidth and a second precoder matrix for a second bandwidth. The first precoder matrix and the second precoder matrix may be different based on the first bandwidth being different from the second bandwidth. The UE may assume that the same precoding matrix is ​​used across a set of PRBs. The set of PRBs may be denoted as a precoding resource block group (PRG).

[0136] The PDSCH may include one or more layers. The UE may assume that at least one symbol with a DMRS is present on one or more layers of the PDSCH. Higher layers may configure up to three DMRS for the PDSCH.

[0137] The downlink PT-RS may be transmitted by the base station and may be used by the UE for phase noise compensation. Whether the downlink PT-RS is present depends on the RRC configuration. The presence and / or pattern of the downlink PT-RS may be configured on a UE-specific basis using a combination of RRC signaling and / or an association with one or more parameters used for other purposes (e.g., modulation and coding scheme (MCS)) that may be indicated by DCI. If configured, the dynamic presence of the downlink PT-RS may be associated with one or more DCI parameters including at least the MCS. The NR network may support multiple PT-RS densities defined in the time and / or frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. The downlink PT-RS may be restricted to the scheduled time / frequency period of the UE. The downlink PT-RS may be transmitted on symbols to facilitate phase tracking at the receiver.

[0138] The UE may transmit an uplink DMRS to a base station for channel estimation. For example, the base station may use the uplink DMRS for coherent demodulation of one or more uplink physical channels. For example, the UE may transmit the uplink DMRS on a PUSCH and / or a PUCCH. The uplink DM-RS may span a range of frequencies similar to the range of frequencies associated with the corresponding physical channel. The base station may configure the UE with one or more uplink DMRS configurations. At least one DMRS configuration may support a frontloaded DMRS pattern. The frontloaded DMRS may be mapped to one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more uplink DMRS may be configured to transmit on one or more symbols of the PUSCH and / or the PUCCH. The base station may semi-statically configure the UE with a number (e.g., a maximum number) of frontloaded DMRS symbols for the PUSCH and / or the PUCCH that the UE may use to schedule single-symbol DMRS and / or dual-symbol DMRS. An NR network may support a common DMRS structure for the downlink and uplink (e.g., for cyclic prefix orthogonal frequency division multiplexing (CP-OFDM)), where the DMRS location, DMRS pattern, and / or scrambling sequence for the DMRS may be the same or different.

[0139] The PUSCH may include one or more layers, and the UE may transmit at least one symbol having a DMRS present on one or more layers of the PUSCH. In one embodiment, higher layers may configure up to three DMRSs for the PUSCH.

[0140] An uplink PT-RS (which may be used by the base station for phase tracking and / or phase noise compensation) may or may not be present depending on the RRC configuration of the UE. The presence and / or pattern of the uplink PT-RS may be configured on a UE-specific basis by a combination of one or more parameters used for other purposes (e.g., Modulation and Coding Scheme (MCS)) that may be indicated by RRC signaling and / or DCI. If configured, the dynamic presence of the uplink PT-RS may be associated with one or more DCI parameters including at least the MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. The frequency domain density, if present, may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS and PT-RS ports. The number of PT-RS ports may be less than the number of DMRS ports in the scheduled resources. For example, the uplink PT-RS may be restricted to the scheduled time / frequency period of the UE.

[0141] The SRS may be transmitted by the UE to the base station for channel condition estimation to support uplink channel dependent scheduling and / or link adaptation. The SRS transmitted by the UE may enable the base station to estimate uplink channel conditions at one or more frequencies. The base station scheduler may use the estimated uplink channel conditions to allocate one or more resource blocks for uplink PUSCH transmission from the UE. The base station may semi-statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station may configure the UE with one or more SRS resources. The SRS resource set applicability may be configured by higher layer (e.g., RRC) parameters. For example, if the higher layer parameters indicate beam management, the SRS resources in one or more SRS resource sets (e.g., having the same / similar time domain behavior, periodicity, aperiodicity, and / or the like) may be transmitted instantaneously (e.g., simultaneously). The UE may transmit one or more SRS resources in the SRS resource set. An NR network may support aperiodic, periodic, and / or semi-persistent SRS transmission. The UE may transmit SRS resources based on one or more trigger types, which may include higher layer signaling (e.g., RRC) and / or one or more DCI formats. In one embodiment, at least one DCI format may be used for the UE to select at least one of one or more configured SRS resource sets. SRS trigger type 0 may refer to SRS triggered based on higher layer signaling. SRS trigger type 1 may refer to SRS triggered based on one or more DCI formats. In one embodiment, if the PUSCH and SRS are transmitted in the same slot, the UE may be configured to transmit the SRS after the transmission of the PUSCH and the corresponding uplink DMRS.

[0142] The base station may quasi-statistically configure the UE with one or more SRS configuration parameters indicating at least one of an SRS resource configuration identifier, a number of SRS ports, a time domain behavior of the SRS resource configuration (e.g., an indication of periodic, semi-persistent, or aperiodic SRS), a slot, minislot, and / or subframe level periodicity, an offset for periodic and / or aperiodic SRS resources, a number of OFDM symbols in the SRS resource, a starting OFDM symbol of the SRS resource, an SRS bandwidth, a frequency hopping bandwidth, a periodic shift, and / or an SRS sequence ID.

[0143] The antenna ports are defined such that a channel on which a symbol on an antenna port is carried can be inferred from a channel on which another symbol on the same antenna port is carried. When a first symbol and a second symbol are transmitted on the same antenna port, a receiver may infer a channel (e.g., fade gain, multipath delay, and / or the like) for carrying a second symbol on an antenna port from the channel for carrying the first symbol on the antenna port. A first antenna port and a second antenna port may be referred to as quasi-collocated (QCLed) if one or more large-scale characteristics of the channel on which the first symbol on the first antenna port is conveyed can be inferred from the channel on which the second symbol of the second antenna port is transmitted. The one or more large-scale characteristics may include at least one of delay spread, Doppler spread, Doppler shift, average gain, average delay, and / or spatial receive (Rx) parameters.

[0144] In a channel using beamforming, beam management is required. Beam management may include beam measurement, beam selection, and beam indication. A beam may be associated with one or more reference signals. For example, a beam may be identified by one or more beamforming reference signals. The UE may perform downlink beam measurement based on a downlink reference signal (e.g., a channel state information reference signal (CSI-RS)) and generate a beam measurement report. The UE may perform a downlink beam measurement procedure after an RRC connection is set up with the base station.

[0145] FIG. 11B illustrates an example of a channel state information reference signal (CSI-RS) mapped to the time and frequency domain. The squares illustrated in FIG. 11B may span resource blocks (RBs) within the bandwidth of a cell. The base station may transmit one or more RRC messages including a CSI-RS resource configuration parameter indicating one or more CSI-RS. One or more of the following parameters may be set by higher layer signaling (e.g., RRC and / or MAC signaling) for the CSI-RS resource configuration: CSI-RS resource configuration identity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol and resource element (RE) location within a subframe), CSI-RS subframe configuration (e.g., subframe position, offset, and radio frame periodicity), CSI-RS power parameters, CSI-RS sequence parameters, code division multiplexing (CDM) type parameters, frequency density, transmit comb, quasi-collocation (QCL) parameters (e.g., QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist, csi-rs-configZPid, qcl-csi-rs-configNZPid), and / or other radio resource parameters.

[0146] The three beams shown in FIG. 11B may be configured for a UE in a UE-specific configuration. Three beams are shown in FIG. 11B (Beam #1, Beam #2, and Beam #3), and more or less beams may be configured. Beam #1 may be assigned with CSI-RS 1101, which may be transmitted on one or more subcarriers in the RB of the first symbol. Beam #2 may be assigned with CSI-RS 1102, which may be transmitted on one or more subcarriers in the RB of the second symbol. Beam #3 may be assigned with CSI-RS 1103, which may be transmitted on one or more subcarriers in the RB of the third symbol. By using frequency division multiplexing (FDM), the base station may transmit another CSI-RS associated with another UE's beam using other subcarriers (e.g., not used to transmit CSI-RS 1101) in the same RB. By using time domain multiplexing (TDM), the beam used for a UE may be configured such that the UE's beam uses symbols from the other UE's beam.

[0147] The CSI-RS (e.g., CSI-RS 1101, 1102, 1103) shown in FIG. 11B may be transmitted by a base station and used by a UE for one or more measurements. For example, the UE may measure the reference signal received power (RSRP) of the configured CSI-RS resources. The base station may configure the UE with a reporting configuration, and the UE may report the RSRP measurements to the network (e.g., via one or more base stations) based on the reporting configuration. In one embodiment, the base station may determine one or more transmission configuration indication (TCI) states including some reference signals based on the reported measurement results. In one embodiment, the base station may indicate one or more TCI states to the UE (e.g., via RRC signaling, MAC CE, and / or DCI). The UE may receive a downlink transmission with a receive (Rx) beam determined based on the one or more TCI states. In one embodiment, the UE may or may not have beam correspondence capability. If the UE has beam correspondence capability, the UE may determine a spatial domain filter of a transmit (Tx) beam based on the spatial domain filter of the corresponding Rx beam. If the UE does not have beam correspondence capability, the UE may perform an uplink beam selection procedure to determine a spatial domain filter of the Tx beam. The UE may perform an uplink beam selection procedure based on one or more sounding reference signal (SRS) resources configured for the UE by the base station. The base station may select and indicate an uplink beam for the UE based on measurements of one or more SRS resources transmitted by the UE.

[0148] In a beam management procedure, the UE may evaluate (e.g., measure) channel quality of one or more beam pair links, including a transmit beam transmitted by the base station and a receive beam received by the UE. Based on the evaluation, the UE may transmit a beam measurement report indicating one or more beam pair quality parameters including, for example, one or more beam identities (e.g., beam index, reference signal index, or the like), RSRP, a precoding matrix indicator (PMI), a channel quality indicator (CQI), and / or a rank indicator (RI).

[0149] FIG. 12A shows examples of three downlink beam management procedures, P1, P2, and P3. Procedure P1 may enable UE measurements at a transmit (Tx) beam of a transmit receive point (TRP) (or multiple TRPs) to support selection of, for example, one or more base station Tx beams and / or UE Rx beams (shown as ellipses in the top and bottom rows of P1, respectively). Beamforming at a TRP may include a Tx beam sweep for a set of beams (shown as an ellipse rotating counterclockwise as shown by the dashed arrows in the top rows of P1 and P2). Beamforming at a UE may include a Rx beam sweep for a set of beams (shown as an ellipse rotating clockwise as shown by the dashed arrows in the bottom rows of P1 and P3). Procedure P2 may be used to enable UE measurements at a Tx beam of a TRP (shown as an ellipse rotating counterclockwise as shown by the dashed arrows in the top row of P2). The UE and / or the base station may perform procedure P2 using a smaller set of beams than used in procedure P1 or using narrower beams than used in procedure P1, which may be referred to as beam refinement. The UE may perform procedure P3 for Rx beam determination by using the same Tx beam at the base station and sweeping the Rx beams at the UE.

[0150] FIG. 12B shows examples of three uplink beam management procedures, U1, U2, and U3. Procedure U1 may be used, for example, to enable the base station to perform measurements on the UE's Tx beams to support selection of one or more UE Tx beams and / or base station Rx beams (shown as ellipses in the top and bottom rows of U1, respectively). Beamforming at the UE may include, for example, a Tx beam sweep from a set of beams (shown as ellipses rotated clockwise as shown by dashed arrows in the bottom rows of U1 and U3). Beamforming at the base station may include, for example, a Rx beam sweep from a set of beams (shown as ellipses rotated counterclockwise as shown by dashed arrows in the top rows of U1 and U2). Procedure U2 may be used to enable the base station to adjust its Rx beam when the UE uses a fixed Tx beam. The UE and / or base station may implement procedure U2 using a smaller set of beams than used in procedure P1 or using narrower beams than used in procedure P1. This may be called beam refinement. The UE may perform procedure U3 to adjust its Tx beam when the base station uses a fixed Rx beam.

[0151] The UE may initiate a Beam Failure Recovery (BFR) procedure based on the detection of a beam failure. The UE may transmit a BFR request (e.g., a preamble, UCI, SR, MAC CE, and / or the like) based on the initiation of the BFR procedure. The UE may detect a beam failure based on a determination that the quality of the beam pair link of the associated control channel is unsatisfactory (e.g., has an error rate higher than an error rate threshold, a received signal power lower than a received signal power threshold, a timer expires, and / or the like).

[0152] The UE may measure the quality of the beam-pair link using one or more reference signals (RSs), including one or more SS / PBCH blocks, one or more CSI-RS resources, and / or one or more demodulation reference signals (DMRSs). The quality of the beam-pair link may be based on one or more of a block error rate (BLER), an RSRP value, a signal-to-interference-plus-noise ratio (SINR) value, a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resources. The base station may indicate that the RS resources are quasi-co-located (QCLed) with one or more DM-RSs of a channel (e.g., a control channel, a shared data channel, and / or the like). The RS resources and one or more DMRSs of the channel may be QCLed when the channel characteristics (e.g., Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameters, fade, and / or the like) from a transmission to the UE over the RS resources are similar or identical to the channel characteristics from a transmission to the UE over the channel.

[0153] The network (e.g., gNB and / or ng-eNB of the network) and / or the UE may initiate a random access procedure. A UE in RRC_IDLE state and / or a UE in RRC_INACTIVE state may initiate a random access procedure to request a connection setup to the network. The UE may initiate a random access procedure from the RRC_CONNECTED state. The UE may initiate a random access procedure to request uplink resources (e.g., for uplink transmission of SR when there are no available PUCCH resources) and / or to acquire uplink timing (e.g., when the uplink synchronization state is not synchronized). The UE may initiate a random access procedure and request one or more system information blocks (SIBs) (e.g., SIB2, SIB3, and / or other system information such as similar). The UE may initiate a random access procedure for a beam failure recovery request. The network may initiate a random access procedure to establish time alignment for handover and / or for SCell addition.

[0154] FIG. 13A shows a four-step contention-based random access procedure. Before the procedure begins, the base station may transmit a configuration message 1310 to the UE. FIG. 13A includes the transmission of four messages: Msg1 1311, Msg2 1312, Msg3 1313, and Msg4 1314. Msg1 1311 may include and / or be referred to as a preamble (or random access preamble). Msg2 1312 may include and / or be referred to as a random access response (RAR).

[0155] The configuration message 1310 may be transmitted, for example, using one or more RRC messages. The one or more RRC messages may indicate one or more Random Access Channel (RACH) parameters to the UE. The one or more RACH parameters may include at least one of general parameters (e.g., RACH-configGeneral), cell-specific parameters (e.g., RACH-ConfigCommon), and / or dedicated parameters (e.g., RACH-configDedicated) for one or more random access procedures. The base station may broadcast or multicast the one or more RRC messages to the one or more UEs. The one or more RRC messages may be UE-specific (e.g., dedicated RRC messages transmitted to the UE in RRC_CONNECTED and / or RRC_INACTIVE states). The UE may determine time-frequency resources and / or uplink transmit power for transmission of Msg1 1311 and / or Msg3 1313 based on the one or more RACH parameters. Based on the one or more RACH parameters, the UE may determine the receive timing and downlink channel for receiving Msg2 1312 and Msg4 1314.

[0156] The one or more RACH parameters provided in the configuration message 1310 may indicate one or more physical RACH (PRACH) opportunities available for transmission of Msg1 1311. The one or more PRACH opportunities may be predefined. The one or more RACH parameters may indicate one or more available sets of one or more PRACH opportunities (e.g., prach-ConfigIndex). The one or more RACH parameters may indicate an association between (a) one or more PRACH opportunities and (b) one or more reference signals. The one or more RACH parameters may indicate an association between (a) one or more preambles and (b) one or more reference signals. The one or more reference signals may be SS / PBCH blocks and / or CSI-RS. For example, the one or more RACH parameters may indicate the number of SS / PBCH blocks mapped to the PRACH opportunities and / or the number of preambles mapped to the SS / PBCH blocks.

[0157] The one or more RACH parameters provided in the configuration message 1310 may be used to determine the uplink transmission power of Msg1 1311 and / or Msg3 1313. For example, the one or more RACH parameters may indicate a reference power for the preamble transmission (e.g., a received target power and / or an initial power of the preamble transmission). There may be one or more power offsets indicated by the one or more RACH parameters. For example, the one or more RACH parameters may indicate a power ramping step, a power offset between SSB and CSI-RS, a power offset between the transmissions of Msg1 1311 and Msg3 1313, and / or a power offset value between preamble groups. The one or more RACH parameters may indicate one or more thresholds for which the UE may determine at least one reference signal (e.g., SSB and / or CSI-RS) and / or uplink carrier (e.g., a normal uplink (NUL) carrier and / or a complementary uplink (SUL) carrier).

[0158] Msg1 1311 may include one or more preamble transmissions (e.g., a preamble transmission and one or more preamble retransmissions). The RRC message may be used to configure one or more preamble groups (e.g., Group A and / or Group B). The preamble group may include one or more preambles. The UE may determine the preamble group based on a path loss measurement and / or a size of Msg3 1313. The UE may measure the RSRP of one or more reference signals (e.g., SSB and / or CSI-RS) and determine at least one reference signal having an RSRP above an RSRP threshold (e.g., rsrp-ThresholdSSB and / or rsrp-ThresholdCSI-RS). The UE may select one or more reference signals and / or at least one preamble associated with the selected preamble group, for example, if an association between the one or more preambles and the at least one reference signal is configured by the RRC message.

[0159] The UE may determine the preamble based on one or more RACH parameters provided in the configuration message 1310. For example, the UE may determine the preamble based on a path loss measurement, an RSRP measurement, and / or a size of Msg3 1313. As another example, the one or more RACH parameters may indicate one or more thresholds for determining a preamble format, a maximum number of preamble transmissions, and / or one or more preamble groups (e.g., Group A and Group B). The base station may configure the UE with an association between one or more preambles and one or more reference signals (e.g., SSB and / or CSI-RS) using the one or more RACH parameters. If an association is configured, the UE may determine a preamble to include in Msg1 1311 based on the association. Msg1 1311 may be transmitted to the base station via one or more PRACH opportunities. The UE may use one or more reference signals (e.g., SSB and / or CSI-RS) for preamble selection and PRACH opportunity determination. One or more RACH parameters (eg, ra-ssb-OccasionMskIndex and / or ra-OccasionList) may indicate an association between a PRACH occasion and one or more reference signals.

[0160] The UE may perform a preamble retransmission if no response is received after the preamble transmission. The UE may increase the uplink transmit power for the preamble retransmission. The UE may select an initial preamble transmit power based on a path loss measurement and / or a target received preamble power configured by the network. The UE may decide to retransmit the preamble and may ramp up the uplink transmit power. The UE may receive one or more RACH parameters (e.g., PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step of the preamble retransmission. The ramping step may be the amount of incremental increase of the uplink transmit power for the retransmission. If the UE determines a reference signal (e.g., SSB and / or CSI-RS) that is the same as the previous preamble transmission, the UE may ramp up the uplink transmit power. The UE may count the number of preamble transmissions and / or retransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE may determine that the random access procedure has completed unsuccessfully, for example, if the number of preamble transmissions exceeds a threshold configured by one or more RACH parameters (eg, preambleTransMax).

[0161] Msg2 1312 received by the UE may include an RAR. In some scenarios, Msg2 1312 may include multiple RARs corresponding to multiple UEs. Msg2 1312 may be received after or in response to the transmission of Msg1 1311. Msg2 1312 may be scheduled on the DL-SCH and indicated on the PDCCH using a Random Access RNTI (RA-RNTI). Msg2 1312 may indicate that Msg1 1311 was received by the base station. Msg2 1312 may include a time alignment command that the UE may use to adjust the UE's transmission timing, a scheduling grant for the transmission of Msg3 1313, and / or a Temporary Cell RNTI (TC-RNTI). After transmitting the preamble, the UE may begin a time window (e.g., ra-ResponseWindow) to monitor the PDCCH for Msg2 1312. The UE may determine when to start the time window based on the PRACH opportunity that the UE uses to transmit the preamble. For example, the UE may start the time window one or more symbols after the last symbol of the preamble (e.g., on the first PDCCH opportunity from the end of the preamble transmission). The one or more symbols may be determined based on numerology. The PDCCH may be within a common search space (e.g., Type1-PDCCH common search space) configured by the RRC message. The UE may identify the RAR based on a Radio Network Temporary Identifier (RNTI). The RNTI may be used in response to one or more events that initiate the random access procedure. The UE may use a Random Access RNTI (RA-RNTI). The RA-RNTI may be associated with the PRACH opportunity on which the UE transmits the preamble. For example, the UE may determine the RA-RNTI based on an OFDM symbol index, a slot index, a frequency domain index, and / or a UL carrier indicator of the PRACH opportunity. Examples of the RA-RNTI may be as follows: RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id Here, s_id may be the index of the first OFDM symbol of the PRACH opportunity (e.g., 0≦s_id<14), t_id may be the index of the first slot of the PRACH opportunity in the system frame (e.g., 0≦t_id<80), f_id may be the index of the PRACH opportunity in the frequency domain (e.g., 0≦f_id<8), and ul_carrier_id may be the UL carrier used for preamble transmission (e.g., 0 for NUL carrier and 1 for SUL carrier). The UE may transmit Msg3 1313 in response to successful reception of Msg2 1312 (e.g., using resources identified in Msg2 1312). Msg3 1313 may be used for contention resolution, for example, in the contention-based random access procedure shown in FIG. 13A. In some scenarios, multiple UEs may transmit the same preamble to the base station, and the base station may provide the UE with a corresponding RAR. If multiple UEs interpret the RAR as corresponding to themselves, a mismatch may occur. Contention resolution (e.g., use of Msg3 1313 and Msg4 1314) may be used to increase the likelihood that a UE does not mistakenly use the identity of another UE. To perform contention resolution, the UE may include a device identifier in Msg3 1313 (e.g., C-RNTI, if assigned, TC-RNTI included in Msg2 1312, and / or any other suitable identifier).

[0162] Msg4 1314 may be received after or in response to the transmission of Msg3 1313. If a C-RNTI was included in Msg3 1313, the base station uses the C-RNTI to address the UE on the PDCCH. If the UE's unique C-RNTI is detected on the PDCCH, the random access procedure is determined to have been completed successfully. If a TC-RNTI is included in Msg3 1313 (e.g., the UE is in an RRC_IDLE state or is otherwise not connected to the base station), Msg4 1314 is received using the DL-SCH associated with the TC-RNTI. If the MAC PDU is successfully decoded and the MAC PDU matches the CCCH SDU sent (e.g., transmitted) in Msg3 1313 or otherwise includes a corresponding UE contention resolution identity MAC CE, the UE may determine that contention resolution was successful and / or the UE may determine that the random access procedure was completed successfully.

[0163] The UE may be configured with a complementary uplink (SUL) carrier and a normal uplink (NUL) carrier. Initial access (e.g., random access procedure) may be supported on the uplink carrier. For example, the base station may configure the UE with two separate RACH configurations, one for the SUL carrier and the other for the NUL carrier. For random access in a cell configured with the SUL carrier, the network may indicate which carrier (NUL or SUL) to use. The UE may determine the SUL carrier, for example, if the measured quality of one or more reference signals is below a broadcast threshold. Uplink transmissions of the random access procedure (e.g., Msg1 1311 and / or Msg3 1313) may remain on the selected carrier. The UE may switch uplink carriers during the random access procedure (e.g., between Msg1 1311 and Msg3 1313) in one or more instances. For example, the UE may determine and / or switch uplink carriers for Msg1 1311 and / or Msg3 1313 based on a channel clear assessment (eg, listen-before-talk).

[0164] FIG. 13B illustrates a two-step contention-free random access procedure. Similar to the four-step contention-based random access procedure illustrated in FIG. 13A, the base station may transmit a configuration message 1320 to the UE before the procedure begins. The configuration message 1320 may be similar in some respects to the configuration message 1310. FIG. 13B includes the transmission of two messages, Msg1 1321 and Msg2 1322. Msg1 1321 and Msg2 1322 may be similar in some respects to Msg1 1311 and Msg2 1312, respectively, illustrated in FIG. 13A. As can be seen from FIG. 13A and FIG. 13B, the contention-free random access procedure may not include messages similar to Msg3 1313 and / or Msg4 1314.

[0165] The contention-free random access procedure shown in Figure 13B may be initiated for beam failure recovery, other SI requests, SCell addition, and / or handover. For example, the base station may indicate or assign to the UE the preamble to be used for Msg1 1321. The UE may receive an indication of the preamble (e.g., ra-PreambleIndex) from the base station via PDCCH and / or RRC.

[0166] After transmitting the preamble, the UE may start a time window (e.g., ra-ResponseWindow) to monitor the PDCCH of the RAR. In the case of a beam failure recovery request, the base station may configure the UE with a separate time window and / or separate PDCCH within the search space indicated by the RRC message (e.g., recoverySearchSpaceId). The UE may monitor for PDCCH transmissions addressed to the Cell RNTI (C-RNTI) on the search space. In the contention-free random access procedure shown in FIG. 13B, the UE may determine that the random access procedure is successfully completed after or in response to transmitting Msg1 1321 and receiving the corresponding Msg2 1322. The UE may determine that the random access procedure is successfully completed, for example, if the PDCCH transmission is addressed to the C-RNTI. The UE may determine that the random access procedure is successfully completed, for example, if the UE receives an RAR including a preamble identifier corresponding to a preamble transmitted by the UE and / or if the RAR includes a MAC sub-PDU including a preamble identifier. The UE may determine the response as an indication of confirmation to the SI request.

[0167] Figure 13C shows another two-step random access procedure. Similar to the random access procedure shown in Figures 13A and 13B, the base station can transmit a configuration message 1330 to the UE before the procedure begins. The configuration message 1330 can be similar in some respects to the configuration message 1310 and / or the configuration message 1320. Figure 13C includes the transmission of two messages, namely, Msg A 1331 and Msg B 1332.

[0168] Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A 1331 may include one or more transmissions of a preamble 1341 and / or one or more transmissions of a transport block 1342. The transport block 1342 may include content similar and / or equivalent to the content of Msg3 1313 shown in FIG. 13A. The transport block 1342 may include UCI (e.g., SR, HARQ ACK / NACK, and / or similar). The UE may receive Msg B 1332 after or in response to the transmission of Msg A 1331. Msg B 1332 may include content similar and / or equivalent to the content of Msg2 1312 (e.g., RAR) shown in FIG. 13A and 13B and / or the content of Msg4 1314 shown in FIG. 13A.

[0169] The UE may initiate the two-step random access procedure of FIG. 13C for licensed and / or unlicensed spectrum. The UE may determine whether to initiate the two-step random access procedure based on one or more factors. The one or more factors may be the radio access technology in use (e.g., LTE, NR, and / or the like), whether the UE has a valid TA, the cell size, the RRC state of the UE, the type of spectrum (e.g., licensed vs. unlicensed), and / or any other suitable factor.

[0170] The UE may determine radio resources and / or uplink transmit power for the preamble 1341 and / or the transport block 1342 included in Msg A 1331 based on the two-step RACH parameters included in the configuration message 1330. The RACH parameters may indicate a modulation and coding scheme (MCS), time-frequency resources, and / or power control for the preamble 1341 and / or the transport block 1342. The time-frequency resources for transmission of the preamble 1341 (e.g., PRACH) and the time-frequency resources for transmission of the transport block 1342 (e.g., PUSCH) may be multiplexed using FDM, TDM, and / or CDM. The RACH parameters may enable the UE to determine the receive timing and downlink channel for monitoring and / or receiving Msg B 1332.

[0171] The transport block 1342 may include data (e.g., delay sensitive data), a UE identifier, security information, and / or device information (e.g., International Mobile Subscriber Identity (IMSI)). The base station may send Msg B 1332 in response to Msg A 1331. Msg B 1332 may include at least one of a preamble identifier, a timing advance command, a power control command, an uplink grant (e.g., radio resource allocation and / or MCS), a UE identifier for contention resolution, and / or an RNTI (e.g., C-RNTI or TC-RNTI). The UE may determine that the two-step random access procedure is successfully completed if the preamble identifier in Msg B 1332 matches the preamble transmitted by the UE and / or the UE identifier in Msg B 1332 matches the UE identifier (e.g., transport block 1342) in Msg A 1331.

[0172] The UE and the base station may exchange control signaling, which may be referred to as L1 / L2 control signaling, and may originate from the PHY layer (e.g., Layer 1) and / or the MAC layer (e.g., Layer 2). The control signaling may include downlink control signaling transmitted from the base station to the UE and / or uplink control signaling transmitted from the UE to the base station.

[0173] The downlink control signaling may include downlink scheduling assignments, uplink scheduling grants indicating uplink radio resources and / or transport formats, slot format information, preemption indications, power control commands, and / or any other suitable signaling. A UE may receive the downlink control signaling in a payload transmitted by a base station on a Physical Downlink Control Channel (PDCCH). The payload transmitted on the PDCCH may be referred to as Downlink Control Information (DCI). In some scenarios, the PDCCH may be a Group Common PDCCH (GC-PDCCH) that is common to a group of UEs.

[0174] The base station may attach one or more cyclic redundancy check (CRC) parity bits to the DCI to facilitate detection of transmission errors. If the DCI is intended for a UE (or a group of UEs), the base station may scramble the CRC parity bits with an identifier of the UE (or an identifier of the group of UEs). Scrambling the CRC parity bits with an identifier may include a modulo-2 addition (or exclusive OR operation) of the identifier value and the CRC parity bits. The identifier may include a Radio Network Temporary Identifier (RNTI), which is a 16-bit value.

[0175] DCIs may be used for different purposes. The purpose may be indicated by the type of RNTI used to scramble the CRC parity bits. For example, a DCI with CRC parity bits scrambled with a paging RNTI (P-RNTI) may indicate paging information and / or system information change notification. The P-RNTI may be predefined as "FFFE" in hexadecimal. A DCI with CRC parity bits scrambled with a system information RNTI (SI-RNTI) may indicate a broadcast transmission of system information. The SI-RNTI may be predefined as "FFFF" in hexadecimal. A DCI with CRC parity bits scrambled with a random access RNTI (RA-RNTI) may indicate a random access response (RAR). A DCI with CRC parity bits scrambled with a cell RNTI (C-RNTI) may indicate a unicast transmission of a dynamic schedule and / or a random access of a PDCCH order trigger. A DCI with CRC parity bits scrambled with the Temporary Cell RNTI (TC-RNTI) may indicate contention resolution (e.g., Msg3 similar to Msg3 1313 shown in FIG. 13A). Encodings of other RNTIs configured in the UE by the base station include Configured Scheduling RNTI (CS-RNTI), Transmit Power Control-PUCCH RNTI (TPC-PUCCH-RNTI), Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI), Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), Interruption RNTI (INT-RNTI), Slot Format Indication RNTI (SFI-RNTI), Semi-Persistent CSI RNTI (SP-CSI-RNTI), Modulation and Coding Scheme Cell RNTI (MCS-C-RNTI), and / or the like.

[0176] Depending on the purpose and / or content of the DCI, the base station may transmit the DCI in one or more DCI formats. For example, DCI format 0_0 may be used for scheduling the PUSCH in the cell. DCI format 0_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 0_1 ​​may be used for scheduling the PUSCH in the cell (e.g., has a larger DCI payload than DCI format 0_0). DCI format 1_0 may be used for scheduling the PDSCH in the cell. DCI format 1_0 may be a fallback DCI format (e.g., has a compact DCI payload). DCI format 1_1 may be used for scheduling the PDSCH in the cell (e.g., has a larger DCI payload than DCI format 1_0). DCI format 2_0 may be used to provide a slot format indication to a group of UEs. DCI format 2_1 may be used to inform a group of UEs of the physical resource blocks and / or OFDM symbols that the UE assumes are not intended for transmission to the UE. DCI format 2_2 may be used for transmission of transmit power control (TPC) commands for PUCCH or PUSCH. DCI format 2_3 may be used for transmission of a group of TPC commands for SRS transmission by one or more UEs. DCI formats for new features may be defined in future releases. DCI formats may have different DCI sizes or share the same DCI size.

[0177] After scrambling the DCI with the RNTI, the base station may process the DCI using channel coding (e.g., polar coding), rate matching, scrambling, and / or QPSK modulation. The base station may map the coded and modulated DCI onto resource elements used and / or configured for the PDCCH. Based on the payload size of the DCI and / or the coverage of the base station, the base station may transmit the DCI via the PDCCH occupying several consecutive control channel elements (CCEs). The number of consecutive CCEs (called an aggregation level) may be 1, 2, 4, 8, 16, and / or any other suitable number. A CCE may include a number of resource element groups (REGs) (e.g., 6). A REG may include a resource block within an OFDM symbol. The mapping of the coded and modulated DCI onto resource elements may be based on a mapping of CCEs and REGs (e.g., CCE to REG mapping).

[0178] FIG. 14A illustrates an example of a CORESET configuration for a bandwidth portion. A base station may transmit DCI via a PDCCH on one or more control resource sets (CORESETs). A CORESET may include time-frequency resources on which a UE attempts to decode DCI using one or more search spaces. A base station may configure a CORESET in the time-frequency domain. In the example of FIG. 14A, a first CORESET 1401 and a second CORESET 1402 occur at a first symbol in a slot. The first CORESET 1401 overlaps with the second CORESET 1402 in the frequency domain. A third CORESET 1403 occurs at a third symbol in a slot. A fourth CORESET 1404 occurs at a seventh symbol of a slot. The CORESETs may have different numbers of resource blocks in the frequency domain.

[0179] FIG. 14B illustrates an example of CCE-to-REG mapping for DCI transmission on a CORESET and PDCCH processing. The CCE-to-REG mapping may be interleaved (e.g., for the purpose of providing frequency diversity) or non-interleaved (e.g., for the purpose of facilitating interference coordination and / or frequency selective transmission of control channels). A base station may perform different or identical CCE-to-REG mappings on different CORESETs. A CORESET may be associated with a CCE-to-REG mapping by an RRC configuration. A CORESET may be configured with an antenna port quasi-co-location (QCL) parameter. The QCL parameter of an antenna port may indicate the QCL information of a demodulation reference signal (DMRS) for PDCCH reception in the CORESET.

[0180] The base station may send an RRC message to the UE including configuration parameters of one or more CORESETs and one or more search space sets. The configuration parameters may indicate an association between the search space set and the CORESET. The search space set may include a set of PDCCH candidates formed by CCEs at a given aggregation level. The configuration parameters may indicate the number of PDCCH candidates monitored per aggregation level, a PDCCH monitoring periodicity and a PDCCH monitoring pattern, one or more DCI formats monitored by the UE, and / or whether the search space set is a common search space set or a UE-specific search space set. The set of CCEs in the common search space set may be predefined and known to the UE. The set of CCEs in the UE-specific search space set may be configured based on the UE's identity (e.g., C-RNTI).

[0181] As shown in FIG. 14B, the UE may determine time-frequency resources of the CORESET based on the RRC message. The UE may determine CCE-REG mapping (e.g., interleaved or non-interleaved, and / or mapping parameters) for the CORESET based on configuration parameters of the CORESET. The UE may determine the number of search space sets (e.g., up to 10) configured on the CORESET based on the RRC message. The UE may monitor a set of PDCCH candidates according to configuration parameters of the search space sets. The UE may monitor a set of PDCCH candidates in one or more CORESETs to detect one or more DCIs. The monitoring may include decoding one or more PDCCH candidates of the set of PDCCH candidates according to a monitored DCI format. The monitoring may include decoding DCI content of one or more PDCCH candidates having possible (or configured) PDCCH positions, possible (or configured) PDCCH formats (e.g., number of CCEs in a common search space, number of PDCCH candidates, and / or number of PDCCH candidates in a UE-specific search space), and possible (or configured) DCI formats. The decoding may be referred to as blind-blind-combined-blind decoding. The UE may determine a valid DCI for the UE in response to a CRC check (e.g., scrambling bits to CRC parity bits of the DCI matching the RNTI value). The UE may process information included in the DCI (e.g., scheduling assignment, uplink grant, power control, slot format indication, downlink preemption, and / or the like).

[0182] The UE may transmit uplink control signaling (e.g., uplink control information (UCI)) to the base station. The uplink control signaling may include a hybrid automatic repeat request (HARQ) acknowledgement for the received DL-SCH transport block. The UE may transmit the HARQ acknowledgement after receiving the DL-SCH transport block. The uplink control signaling may include channel state information (CSI) indicating a channel quality of the physical downlink channel. The UE may transmit the CSI to the base station. The base station may determine transmission format parameters (e.g., including multiple antennas and beamforming schemes) for the downlink transmission based on the received CSI. The uplink control signaling may include a scheduling request (SR). The UE may transmit an SR indicating that uplink data is available to be transmitted to the base station. The UE may transmit the UCI (e.g., a HARQ acknowledgement (HARQ-ACK), a CSI report, an SR, etc.) via a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH). A UE may transmit uplink control signaling via the PUCCH using one of several PUCCH formats.

[0183] There may be five PUCCH formats, and the UE may determine the PUCCH format based on the size of the UCI (e.g., the number of uplink symbols for UCI transmission and the number of UCI bits). PUCCH format 0 may have a length of one or two OFDM symbols and may include two or less bits. The UE may transmit UCI on PUCCH resources using PUCCH format 0 if the transmission is more than one or two symbols and the number of HARQ-ACK information bits with positive or negative SR (HARQ-ACK / SR bits) is one or two. PUCCH format 1 may occupy between 4-14 OFDM symbols and may include two or less bits. The UE may use PUCCH format 1 if the transmission is four or more symbols and the number of HARQ-ACK / SR bits is one or two. PUCCH format 2 may occupy one or two OFDM symbols and may include more than two bits. The UE may use PUCCH format 2 if the transmission is more than one or two symbols and the number of UCI bits is two or more. PUCCH format 3 may occupy between 4 and 14 OFDM symbols and may include more than 2 bits. The UE may use PUCCH format 3 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource does not include an orthogonal cover code. PUCCH format 4 may occupy between 4 and 14 OFDM symbols and may include more than 2 bits. The UE may use PUCCH format 4 if the transmission is four or more symbols, the number of UCI bits is two or more, and the PUCCH resource includes an orthogonal cover code.

[0184] The base station may transmit configuration parameters of multiple PUCCH resource sets to the UE, for example, using an RRC message. Multiple PUCCH resource sets (e.g., up to four sets) may be configured on the uplink BWP of the cell. A PUCCH resource set may be configured with a PUCCH resource set index, multiple PUCCH resources with PUCCH resources identified by a PUCCH resource identifier (e.g., pucch-Resourceid), and / or a number (e.g., a maximum number) of UCI information bits that the UE may transmit using one of the multiple PUCCH resources in the PUCCH resource set. When configured with multiple PUCCH resource sets, the UE may select one of the multiple PUCCH resource sets based on a total bit length of the UCI information bits (e.g., HARQ-ACK, SR, and / or CSI). If the total bit length of the UCI information bits is less than or equal to two, the UE may select a first PUCCH resource set with a PUCCH resource set index equal to "0". If the total bit length of the UCI information bits is greater than 2 and less than or equal to the first configuration value, the UE may select a second PUCCH resource set having a PUCCH resource set index equal to "1". If the total bit length of the UCI information bits is greater than the first configuration value and less than or equal to the second configuration value, the UE may select a third PUCCH resource set having a PUCCH resource set index equal to "2". If the total bit length of the UCI information bits is greater than the second configuration value and less than or equal to a third value (e.g., 1406), the UE may select a fourth PUCCH resource set having a PUCCH resource set index equal to "3".

[0185] After determining a PUCCH resource set from the multiple PUCCH resource sets, the UE may determine a PUCCH resource from the PUCCH resource set for UCI (HARQ-ACK, CSI, and / or SR) transmission. The UE may determine the PUCCH resource based on a PUCCH resource indicator in a DCI (e.g., DCI format 1_0 or DCI format 1_1) received on a PDCCH. The 3-bit PUCCH resource indicator of the DCI may indicate one of the eight PUCCH resources in the PUCCH resource set. Based on the PUCCH resource indicator, the UE may transmit the UCI (HARQ-ACK, CSI, and / or SR) using the PUCCH resource indicated by the PUCCH resource indicator in the DCI.

[0186] FIG. 15 illustrates an example of a wireless device 1502 communicating with a base station 1504 according to an embodiment of the disclosure. The wireless device 1502 and the base station 1504 may be part of a mobile communication network, such as the mobile communication network 100 shown in FIG. 1A, the mobile communication network 150 shown in FIG. 1B, or other communication network. Only one wireless device 1502 and one base station 1504 are shown in FIG. 15. However, it will be understood that the mobile communication network may include multiple UEs and / or multiple base stations having the same or similar configuration as that shown in FIG. 15.

[0187] The base station 1504 may connect the wireless device 1502 to a core network (not shown) via wireless communication over an air interface (or radio interface) 1506. The communication direction from the base station 1504 to the wireless device 1502 over the air interface 1506 is known as the downlink, and the communication direction from the wireless device 1502 to the base station 1504 over the air interface is known as the uplink. The downlink transmission may be separated from the uplink transmission using FDD, TDD, and / or some combination of the two duplexing techniques.

[0188] In the downlink, data transmitted from the base station 1504 to the wireless device 1502 may be provided to the processing system 1508 of the base station 1504. The data may be provided to the processing system 1508 by, for example, a core network. In the uplink, data transmitted from the wireless device 1502 to the base station 1504 may be provided to the processing system 1518 of the wireless device 1502. The processing system 1508 and the processing system 1518 may implement Layer 3 and Layer 2 OSI functions to process the data for transmission. Layer 2 may include, for example, with respect to Figures 2A, 2B, 3, and 4A, the SDAP layer, the PDCP layer, the RLC layer, and the MAC layer. Layer 3 may include, for example, with respect to Figure 2B, the RRC layer.

[0189] After being processed by the processing system 1508, data to be transmitted to the wireless device 1502 may be provided to a transmit processing system 1510 of the base station 1504. Similarly, after being processed by the processing system 1518, data to be transmitted to the base station 1504 may be provided to a transmit processing system 1520 of the wireless device 1502. The transmit processing system 1510 and the transmit processing system 1520 may implement Layer 1 OSI functions. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For transmit processing, the PHY layer may perform, for example, forward error correction coding of transport channels, interleaving, rate matching, mapping of transport channels to physical channels, modulation of physical channels, multiple input multiple output (MIMO) or multi-antenna processing, and / or the like.

[0190] In the base station 1504, a receive processing system 1512 may receive uplink transmissions from the wireless device 1502. In the wireless device 1502, a receive processing system 1522 may receive downlink transmissions from the base station 1504. The receive processing system 1512 and the receive processing system 1522 may implement the OSI functions of Layer 1. Layer 1 may include the PHY layer with respect to FIGS. 2A, 2B, 3, and 4A. For receive processing, the PHY layer may perform, for example, error detection, forward error correction decoding, deinterleaving, demapping of transport channels to physical channels, demodulation of physical channels, MIMO or multi-antenna processing, and / or the like.

[0191] 15, the wireless device 1502 and the base station 1504 may include multiple antennas. The multiple antennas may be used to implement one or more MIMO or multi-antenna techniques, such as spatial multiplexing (e.g., single-user MIMO or multi-user MIMO), transmit / receive diversity, and / or beamforming. In other examples, the wireless device 1502 and / or the base station 1504 may have a single antenna.

[0192] Processing system 1508 and processing system 1518 may be associated with memory 1514 and memory 1524, respectively. Memory 1514 and memory 1524 (e.g., one or more non-transitory computer-readable media) may store computer program instructions or code that may be executed by processing system 1508 and / or processing system 1518 to perform one or more functions discussed in the present application. Although not shown in FIG. 15 , transmit processing system 1510, transmit processing system 1520, receive processing system 1512, and / or receive processing system 1522 may be coupled to memory (e.g., one or more non-transitory computer-readable media) that stores computer program instructions or code that may be executed to perform one or more of their respective functions.

[0193] The processing system 1508 and / or the processing system 1518 may include one or more controllers and / or one or more processors. The one or more controllers and / or the one or more processors may include, for example, a general purpose processor, a digital signal processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic devices, discrete gate and / or transistor logic, discrete hardware components, on-board units, or any combination thereof. The processing system 1508 and / or the processing system 1518 may perform at least one of signal coding / processing, data processing, power control, input / output processing, and / or any other functionality that may enable the wireless device 1502 and the base station 1504 to operate in a wireless environment.

[0194] The processing system 1508 and / or the processing system 1518 may be connected to one or more peripheral devices 1516 and one or more peripheral devices 1526, respectively. The one or more peripheral devices 1516 and one or more peripheral devices 1526 may include software and / or hardware that provide features and / or functionality, such as a speaker, a microphone, a keypad, a display, a touchpad, a power source, a satellite transceiver, a universal serial bus (USB) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an Internet browser, an electronic control unit (e.g., for a vehicle), and / or one or more sensors (e.g., an accelerometer, a gyroscope, a temperature sensor, a radar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, a camera, and / or the like). The processing system 1508 and / or the processing system 1518 may receive user input data and / or provide user output data from the one or more peripheral devices 1516 and / or the one or more peripheral devices 1526. The processing system 1518 in the wireless device 1502 can receive power from a power source and / or can be configured to distribute power to other components in the wireless device 1502. The power source may include one or more power sources, such as a battery, a solar cell, a fuel cell, or any combination thereof. The processing system 1508 and / or the processing system 1518 may be connected to a GPS chipset 1517 and a GPS chipset 1527, respectively. The GPS chipset 1517 and the GPS chipset 1527 may be configured to provide geographic location information of the wireless device 1502 and the base station 1504, respectively.

[0195] FIG. 16A illustrates an example structure for uplink transmission. A baseband signal representing a physical uplink shared channel may perform one or more functions. The one or more functions may include at least one of: scrambling, modulating scramble bits to generate complex-valued symbols, mapping complex-valued modulation symbols onto one or several transmission layers, transform precoding to generate complex-valued symbols, precoding the complex-valued symbols, mapping the precoded complex-valued symbols onto resource elements, generating complex-valued time-domain single carrier frequency division multiple access (SC-FDMA) or CP-OFDM signals to antenna ports, and / or the like. In one example, if transform precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, if transform precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated according to FIG. 16A. These functions are illustrated as examples, and it is anticipated that other mechanisms may be implemented in various embodiments.

[0196] 16B shows an example structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued SC-FDMA or CP-OFDM baseband signal and / or a complex-valued Physical Random Access Channel (PRACH) baseband signal for an antenna port. Filtering may be used before transmission.

[0197] 16C illustrates an exemplary structure of a downlink transmission. A baseband signal representing a physical downlink channel can perform one or more functions. The one or more functions can include scrambling of coded bits in a codeword to be transmitted on the physical channel, modulation of the scrambled bits to generate complex-valued modulation symbols, mapping of the complex-valued modulation symbols onto one or several transmission layers, precoding of the complex-valued modulation symbols on the layers for transmission on the antenna ports, mapping of the complex-valued modulation symbols of the antenna ports to resource elements, generation of a complex-valued time-domain OFDM signal per antenna port, and / or the like. These functions are illustrated as examples, and it is anticipated that other mechanisms can be implemented in various embodiments.

[0198] 16D shows another example structure for modulation and upconversion of a baseband signal to a carrier frequency. The baseband signal may be a complex-valued OFDM baseband signal for an antenna port. Filtering may be used before transmission.

[0199] The wireless device may receive one or more messages (e.g., RRC messages) from a base station including configuration parameters for multiple cells (e.g., primary cell, secondary cell). The wireless device may communicate with at least one base station (e.g., two or more base stations for dual connectivity) via the multiple cells. The one or more messages (e.g., as part of the configuration parameters) may include physical, MAC, RLC, PCDP, SDAP, RRC layer parameters for configuring the wireless device. For example, the configuration parameters may include parameters for configuring physical and MAC layer channels, bearers, etc. For example, the configuration parameters may include parameters indicating values ​​of timers for the physical layer, MAC layer, RLC layer, PCDP layer, SDAP layer, RRC layer, and / or communication channels.

[0200] A timer may begin execution when started and continue to execute until stopped or expires. A timer may be started if not running or restarted if running. A timer may be associated with a value (e.g., a timer may be started or restarted from a value, or may be started from zero and expire when the value is reached). A timer's duration may not be updated until the timer is stopped or expires (e.g., by BWP switching). A timer may be used to measure a period / window of a process. When this specification refers to implementations and procedures related to one or more timers, it will be understood that there are multiple ways to implement one or more timers. For example, it will be understood that one or more of multiple ways to implement a timer may be used to measure the period / window of a procedure. For example, a random access response window timer may be used to measure a window time for receiving a random access response. In one embodiment, the time difference between two timestamps may be used instead of the start and expiration of the random access response window timer. When a timer is restarted, the process for measuring the time window may be restarted. Other example implementations may be provided for restarting the measurement of the time window.

[0201] The wireless device may not perform (e.g., may not be permitted to perform or may be prohibited from performing) uplink data transmission in the RRC_INACTIVE state and / or the RRC_IDLE state. In such a case, the wireless device may connect (e.g., set up, (re)establish, and / or resume) to the network for transmission of DL (e.g., mobile terminated (MT)) data and / or UL (e.g., mobile originated (MO)) data. For example, the wireless device may perform one or more procedures (e.g., connection setup procedures) to connect to the network in the RRC_INACTIVE state (or the RRC-IDLE state). For example, the wireless device may perform one or more procedures (e.g., connection setup or resume procedures) when, for example, DL (e.g., mobile terminated (MT)) and / or UL (e.g., mobile originated (MO)) data is available in a buffer. Based on the one or more procedures (e.g., in response to successful completion of the connection setup or resume procedures), the RRC state of the wireless device may transition from the RRC_INACTIVE state (or the RRC_IDLE state) to the RRC_CONNECTED state. In the RRC_CONNECTED state, the wireless device may receive DL transmissions (e.g., receive DL data) and / or perform UL transmissions (e.g., transmit UL data). The wireless device may transition from the RRC_CONNECTED state to an RRC_INACTIVE state (or an RRC_IDLE state), for example, after or in response to there being no more DL data (e.g., to be received) and / or no more UL data (e.g., to be transmitted) in the buffer. To transition from the RRC_CONNECTED state to the RRC_INACTIVE state, the wireless device may perform a connection release procedure. The connection release procedure (e.g., an RRC release procedure) may transition the RRC state from the RRC_CONNECTED state to the RRC_INACTIVE state (or RRC_IDLE).

[0202] Frequent RRC state transitions between the RRC_INACTIVE state (or the RRC_IDLE state) and the RRC_CONNECTED state may require the wireless device to transmit and / or receive multiple control signals at different layers (e.g., RRC messages, MAC CE, and / or DCI). For example, for an RRC connection setup, the wireless device may send an RRC connection setup request to a base station and receive an RRC connection setup message in response to the RRC connection setup request. For example, for an RRC connection resumption, the wireless device may send an RRC connection resumption request to the base station and receive an RRC connection resumption message in response to the RRC connection resumption request. For example, for an RRC connection release, the wireless device may receive an RRC connection release request from the base station. For example, it may be inefficient for a wireless device to make (or resume) a connection to the network (e.g., transition from RRC_INACTIVE or RRC_IDLE to RRC_CONNECTED) for a DL and / or UL transmission of small data available (or arriving) in the RRC_INACTIVE state (or RRC_IDLE state) and then release the connection (transition from RRC_CONNECTED to RRC_INACTIVE or RRC_IDLE) before or in response to performing a DL and / or UL transmission of small data in RRC_CONNECTED. This may increase unnecessary power consumption and / or signaling overhead. For example, the signaling overhead (e.g., control signaling overhead) required to transmit a payload may be larger than the payload. For example, frequent RRC state transitions for small and infrequent DL and / or UL data packets may cause unnecessary power consumption and signaling overhead in the wireless device.

[0203] Examples of small, infrequent data packets could include traffic generated from smartphone applications, instant messaging (IM) services, heartbeat / keep-alive traffic from IM / email clients and other apps, miscellaneous apps, non-smartphone apps, wearables (e.g., location), sensors (e.g., to send temperature, pressure readings periodically or in an event-triggered manner), and / or push notifications from smart meters and smart meter networks sending meter readings.

[0204] The wireless device may perform uplink data transmission in the RRC_INACTIVE state (or the RRC_IDLE state). For example, the wireless device may transmit one or more data packets in the RRC_INACTIVE state (and / or the RRC_IDLE state). For example, the wireless device may receive scheduling information (e.g., an RRC message) from a base station indicating one or more uplink radio resources of the RRC_INACTIVE state of the wireless device. The one or more uplink radio resources may be for infrequent data transmission. The one or more uplink radio resources may be for non-periodic data transmission. The one or more uplink radio resources may be for periodic data transmission. The wireless device may transmit one or more data packets over the one or more radio resources while maintaining its RRC state as the RRC_INACTIVE state (and / or the RRC_IDLE state). For example, the wireless device may not transition its RRC state to RRC_CONNECTED to transmit one or more data packets over the one or more radio resources. Uplink transmission via one or more radio resources in the RRC_INACTIVE state (or RRC_IDLE state) may be efficient and flexible (e.g., for short data bursts with low throughput). Uplink transmission via one or more radio resources in the RRC_INACTIVE state (or RRC_IDLE state) may provide an efficient signaling mechanism (e.g., signaling overhead is less than payload). Uplink transmission via one or more radio resources in the RRC_INACTIVE state (or RRC_IDLE state) may reduce signaling overhead. Uplink transmission via one or more radio resources in the RRC_INACTIVE state (or RRC_IDLE state) may improve battery performance of the wireless device. For example, a wireless device with intermittent small data packets in the RRC_INACTIVE state (or RRC_IDLE state) may benefit from such uplink transmission in the RRC_INACTIVE state (or RRC_IDLE state).

[0205] Herein, uplink data transmission in the RRC_INACTIVE state may be compatible with uplink data transmission in the RRC_IDLE state. For example, procedures, configuration parameters, and / or functional descriptions related to uplink data transmission in the RRC_INACTIVE state may be applicable to and / or available for the RRC_IDLE state, for example, unless specified for the RRC_IDLE state. Herein, procedures, configuration parameters, and / or functional descriptions related to uplink data transmission in the RRC_IDLE state may be applicable to and / or available for the RRC_INACTIVE state, for example, unless specified for the RRC_INACTIVE state. For example, if the RRC_CONNECTED and / or RRC_IDLE states are RRC states that the wireless device has, procedures, configuration parameters, and / or functional descriptions related to uplink data transmission in the RRC_INACTIVE state described herein may be applicable to and / or available for the RRC_IDLE state of the wireless device. For example, if the RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE states are RRC states that a wireless device has, then the procedures, configuration parameters, and / or functional descriptions related to uplink data transmission described herein may be applicable to and / or available for the RRC_INACTIVE and / or RRC_IDLE states of the wireless device.

[0206] FIG. 17 is an example of one or more data packet transmissions in an RRC_INACTIVE state (or an RRC_IDLE state) according to an aspect of an embodiment of the present disclosure. The one or more data packet transmissions in FIG. 17 are applicable to one or more example embodiments herein. The wireless device may receive an RRC message configuring uplink resources. The RRC message may be an RRC release message. The uplink resources may be available, scheduled, and / or configured in the RRC_INACTIVE state (and / or the RRC_IDLE state). For example, the wireless device may determine whether to use (and / or start, and / or activate) or deactivate (and / or clear, and / or suspend, and / or deactivate) the uplink resources based on the RRC state of the wireless device. The wireless device may receive radio resource configuration parameters for one or more uplink radio resources that the wireless device may use in the RRC_INACTIVE state (or the RRC_IDLE state). For example, one or more uplink radio resources may be (pre-)configured while the wireless device is in an RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE state. For example, the wireless device may receive an RRC message including radio resource configuration parameters for one or more uplink radio resources while the wireless device is in an RRC_CONNECTED state. The wireless device may not initiate (or activate) the one or more uplink radio resources while the wireless device is in an RRC_CONNECTED state. For example, an RRC release message may include radio resource configuration parameters for the one or more uplink radio resources. The wireless device may initiate (or activate) the one or more uplink radio resources after and / or in response to receiving the RRC release message. The wireless device may initiate (and / or activate and / or use) the one or more uplink radio resources after and / or in response to the RRC state of the wireless device being in an RRC_INACTIVE state (or an RRC_IDLE state).The wireless device may, for example, transmit one or more data packets over one or more uplink radio resources while maintaining the RRC state as an RRC_INACTIVE state (or an RRC_IDLE state) without transitioning to an RRC_CONNECTED state. The wireless device may decide to transition the RRC state from the RRC_INACTIVE state (or an RRC_IDLE state) to an RRC_CONNECTED state. After or in response to transitioning the RRC state to the RRC_CONNECTED state, the wireless device may decide to deactivate (and / or clear, and / or suspend, and / or deactivate) the use of one or more uplink resources.

[0207] In FIG. 17, the wireless device may determine to transition the RRC state of the wireless device from an RRC_CONNECTED state to an RRC_INACTIVE state (or an RRC_IDLE state). The wireless device may determine to transition the RRC state to an RRC_INACTIVE state (or an RRC_IDLE state) after or in response to receiving an RRC message. For example, the wireless device may receive an RRC message (e.g., an RRC release message) from a base station. The RRC message (e.g., an RRC release message) may indicate a release of the RRC connection from the network. In response to receiving the RRC message, the wireless device may perform an RRC release procedure. The RRC release procedure may include release of established radio bearers and / or configured radio resources. The RRC release procedure may include suspension of the RRC connection (e.g., if a signaling radio bearer (SRB) (e.g., SRB2) and / or at least one dedicated radio bearer (DRB) is set up) and / or suspension of established radio bearers. After receiving an RRC message (or performing an RRC release procedure) and / or in response thereto, the wireless device may decide to transition the RRC state of the wireless device from an RRC_CONNECTED state to an RRC_INACTIVE state (or an RRC_IDLE state).

[0208] In FIG. 17, the wireless device may determine to transition the RRC state of the wireless device from an RRC_INACTIVE state (or an RRC_IDLE state) to an RRC_CONNECTED state. For example, the wireless device may perform a random access procedure to transition to the RRC_CONNECTED state. The wireless device may perform (and / or initiate) a random access procedure for uplink transmission of uplink data, for example, coming during the RRC_INACTIVE state (or an RRC_IDLE state). The wireless device may perform the random access procedure after or in response to receiving a paging message in the RRC_INACTIVE state (or an RRC_IDLE state). The wireless device may, for example, periodically monitor a downlink control channel for paging messages. The wireless device may receive a paging message from a base station (or a network) indicating an identifier of the wireless device. The paging message may indicate that the wireless device will perform a random access procedure, for example, to make a connection to the network.

[0209] The wireless device may receive a message including one or more configurations. The configuration of the one or more configurations may include an identifier (or index) of the configuration. Each of the one or more configurations may include radio resource configuration parameters of one or more uplink radio resources that the wireless device may use in an RRC_INACTIVE state (or an RRC_IDLE state).

[0210] The wireless device may receive an RRC message indicating one or more uplink radio resources that the wireless device uses in a Non-RRC_CONNECTED state (e.g., RRC_INACTIVE and / or RRC_IDLE). The one or more uplink radio resources in the Non-RRC_CONNECTED state may be, for example, one-time use resources for a single transmission. The one or more uplink radio resources in the Non-RRC_CONNECTED state may be, for example, periodic resources for one or more uplink transmissions. The one or more uplink radio resources in the Non-RRC_CONNECTED state may be referred to as various names in different systems and / or implementations. The one or more uplink radio resources in the Non-RRC_CONNECTED state may be referred to as pre-configured uplink resources (PUR). An uplink grant indicating the one or more uplink radio resources in the Non-RRC_CONNECTED state may be referred to as a (pre-)configured grant. The (pre-)configured grant may include multiple types. For example, the (pre-)configured grant may include a (pre-)configured grant type 1 and / or a (pre-)configured grant type 2. The one or more uplink radio resources determined (and / or indicated) by the (pre-)configured grant type 1 may not require an indication to (re)initiate (and / or (re)activate) the one or more uplink radio resources, e.g., after or in response to receiving an RRC message indicating the one or more uplink radio resources in a Non-RRC_CONNECTED state. For example, the wireless device may (re)initiate (and / or (re)activate) the one or more uplink radio resources after or in response to receiving an RRC message including a (pre-)configured grant type 1 indicating the one or more uplink radio resources in a Non-RRC_CONNECTED state.The one or more uplink radio resources determined (and / or indicated) by the (pre-)configured grant type 2 may require an indication to (re)initiate (and / or (re)activate) the one or more uplink radio resources after or in response to receiving an RRC message including a (pre-)configured grant type 2 indicating the one or more uplink radio resources. For example, the wireless device may not (re)initiate (and / or (re)activate) the one or more uplink radio resources after or in response to receiving an RRC message including a (pre-)configured grant type 2 indicating the one or more uplink radio resources. For example, the wireless device may (re)initiate (and / or (re)activate) the one or more uplink radio resources after or in response to receiving an indication to (re)initiate (and / or (re)activate) the one or more uplink radio resources in the Non-RRC_CONNECTED state. The wireless device may receive an indication after or in response to receiving an RRC message including a (pre-)configured grant type 2 indicating the one or more uplink radio resources. An uplink grant indicating one or more uplink radio resources in a Non-RRC_CONNECTED state may be referred to as a (pre-)configured grant having a particular type indicator, e.g., (pre-)configured grant type 3, 4, etc. For example, (pre-)configured grant type 1 and (pre-)configured grant type 2 may indicate one or more (periodic) uplink grants in an RRC_CONNECTED state. For example, (pre-)configured grant type 3 (and / or other types of (pre-)configured grants) may indicate one or more (periodic) uplink grants in a Non-RRC_CONNECTED state.

[0211] FIG. 18A is an example of a (pre-)configured grant indicating one or more uplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE state) according to an aspect of an embodiment of the present disclosure. The (pre-)configured grant of FIG. 18A may not require an additional activation message (e.g., DCI, MAC CE, and / or RRC) to activate (and / or initiate) the one or more uplink radio resources (and / or the (pre-)configured grant). For example, the wireless device may receive an RRC message including configuration parameters of the (pre-)configured grant of the cell. For example, the RRC message may be an RRC release message. After receiving or in response to the RRC message, the wireless device may determine (and / or store) the (pre-)configured grant for the cell. After receiving or in response to the RRC message, the wireless device may (re-)initiate (or activate) the (pre-)configured grant. One or more uplink radio resources (and / or (pre)configured grants) may be activated and / or started (or enabled) in the RRC_INACTIVE state. For example, the wireless device may (re)initiate (or activate) a (pre)configured grant to start at (and / or from) a time reference. For example, the time reference may be a symbol, a slot, a subframe, a SFN, and / or a hyper-SFN (H-SFN). For example, an H-SFN includes one or more SFNs (e.g., 1024 SFNs). For example, the time reference may be one or more combinations of a symbol, a slot, a subframe, a SFN, and / or a hyper-SFN (H-SFN). For example, the time reference may be a symbol of a slot of an SFN of an H-SFN indicated by a configuration parameter (e.g., a time domain offset) (e.g., indicating an H-SFN, an SFN, and / or a slot), and a symbol number S (e.g., indicating a symbol). For example, the wireless device may determine that the (pre)configured grant (re)occurs with a periodicity indicated by a configuration parameter.The wireless device may connect to a network (or base station). The wireless device may perform an RRC connection setup procedure and / or an RRC connection resume procedure to make the connection. For example, the wireless device may send an RRC connection setup request (e.g., for an RRC connection setup procedure) and / or an RRC connection resume request (e.g., for an RRC connection resume procedure). The wireless device may receive a response from the base station indicating completion of the RRC connection. For example, the wireless device may receive an RRC connection setup complete (e.g., for an RRC connection setup procedure). For example, the wireless device may receive an RRC connection resume complete (e.g., for an RRC connection resume procedure). In the RRC_CONNECTED state, one or more uplink radio resources (and / or (pre)configured grants) may be deactivated and / or suspended (cleared and / or disabled) in the RRC_CONNECTED state. For example, one or more uplink radio resources (and / or (pre)configured grants) may be deactivated and / or suspended (cleared and / or disabled) after or in response to connecting to the base station of FIG. 18A (e.g., after or in response to receiving an RRC connection setup and / or resumption completion).

[0212] FIG. 18B is an example of a (pre-)configured grant indicating one or more uplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE state) according to aspects of an embodiment of the present disclosure. FIG. 18B may require an additional activation message (e.g., DCI, MAC CE, and / or RRC) to activate (and / or initiate) the one or more uplink radio resources (and / or the (pre-)configured grant). For example, the wireless device may receive an RRC message including configuration parameters of the (pre-)configured grant for the cell. After receiving or in response to the RRC message, the wireless device may determine (and / or store) the (pre-)configured grant for the cell. For example, the RRC message may be an RRC release message. After receiving or in response to the RRC message, the wireless device may not (re-)initiate (or activate) the (pre-)configured grant, for example, until the wireless device receives an additional activation message (e.g., DCI, MAC CE, and / or RRC). The wireless device may monitor the PDCCH in the Non-RRC_CONNECTED state to receive additional wake-up messages. The wireless device may receive additional wake-up messages (e.g., DCI, MAC CE, and / or RRC) after or in response to receiving the RRC message. The DCI carried by the PDCCH may be the additional wake-up message. The MAC CE and / or RRC message received based on the downlink assignment of the DCI carried by the PDCCH may be the additional wake-up message. The configuration parameters in the RRC message may indicate the time and frequency resource allocation of the PDCCH, the monitoring occasions of the PDCCH, and / or the monitoring periodicity of the PDCCH. The wireless device may determine that the (pre-)configured grants (re)occur with a periodicity indicated by the configuration parameters and / or the timing offset reference (e.g., H-SFN, SFN, slot and / or symbol).For example, the wireless device may determine the SFN (e.g., of the H-SFN), slot and / or symbol based on the reception timing of the additional activation message received via the PDCCH. The wireless device may receive an activation deactivation message indicating to deactivate and / or suspend (clear and / or disable) one or more uplink radio resources (and / or (pre)configured grants). The wireless device may receive the activation deactivation message in a Non-RRC_CONNECTED state. The wireless device may connect to the network (or base station). The wireless device may perform an RRC connection setup procedure and / or an RRC connection resumption procedure to make the connection. For example, the wireless device may send an RRC connection setup request (e.g., for an RRC connection setup procedure) and / or an RRC connection resumption request (e.g., for an RRC connection resumption procedure). The wireless device may receive a response from the base station indicating completion of the RRC connection. For example, the wireless device may receive an RRC connection setup complete (e.g., for an RRC connection setup procedure). For example, the wireless device may receive an RRC connection resumption complete (e.g., for an RRC connection resumption procedure). After or in response to the connection, the RRC state of the wireless device may be transitioned to an RRC_CONNECTED state. One or more uplink radio resources (and / or (pre)configured grants) may be deactivated and / or suspended (cleared and / or disabled), for example, after or in response to the RRC state being in the RRC_CONNECTED state. For example, one or more uplink radio resources (and / or (pre)configured grants) may be deactivated and / or suspended (cleared and / or disabled) after or in response to the connection to the base station of FIG. 18B (e.g., after or in response to receiving an RRC connection setup and / or resumption completion).

[0213] The one or more uplink radio resources in the Non-RRC_CONNECTED state may be configured by a higher layer, e.g., the RRC layer and / or the MAC layer. For example, the wireless device may receive from a base station a message (e.g., an RRC message) including one or more configuration parameters for transmitting uplink data via the one or more uplink radio resources in the Non-RRC_CONNECTED state.

[0214] In one example, the one or more configuration parameters may indicate an RNTI for transmission of uplink data over one or more uplink radio resources in the Non-RRC_CONNECTED state. The RNTI may be an identifier of the wireless device. C-RNTI. The RNTI may be a C-RNTI. The RNTI may be a preconfigured uplink resource C-RNTI (PUR-C-RNTI or PUR-RNTI). The wireless device may monitor the PDCCH using the RNTI. For example, the wireless device may monitor the PDCCH using the RNTI after or in response to transmission of uplink data over one or more uplink radio resources. For example, the wireless device may receive a DCI with a CRC scrambled by the RNTI over the PDCCH. The DCI may indicate a positive acknowledgement of the transmission of the uplink data. The DCI may indicate a negative acknowledgement of the transmission of the uplink data. The DCI may indicate a retransmission of the transmission of the uplink data. The DCI may indicate an uplink grant for the retransmission. The DCI may indicate an updated parameter value of the one or more configuration parameters. For example, the DCI may indicate a (e.g., new or updated) timing advance value for transmitting uplink data over one or more uplink radio resources in the Non-RRC_CONNECTED state. The DCI may indicate a trigger for an RA procedure. The one or more configuration parameters may indicate a duration of a response window (e.g., example parameter name: ResponseWindowSize). The wireless device may monitor the PDCCH during the response window to receive a response (e.g., DCI) to the transmission of data from the base station.

[0215] In one example, the one or more configuration parameters may indicate a number of skipped uplink grants (and / or resource opportunities) (e.g., an example parameter name: ImplicitReleaseAfter). Based on the indicated number, the wireless device may decide to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters. This release (clear, deactivate, discard, and / or suspend) mechanism may be referred to as implicit resource release, implicit preconfigured uplink resource release, or the like. The number of skipped uplink grants (or resource opportunities) indicated by the one or more configuration parameters may be the number of skipped (and / or empty) consecutive uplink grants (and / or resource opportunities). For example, after or in response to a determination that the wireless device may skip N opportunities (e.g., N consecutive opportunities) of one or more uplink radio resources or may not transmit an uplink packet over one or more uplink radio resources for N times (e.g., N=number of skipped uplink grants and / or resource opportunities), the wireless device may release (clear, deactivate, discard, and / or suspend) the one or more uplink radio resources, the uplink grants indicating the one or more uplink radio resources, and / or one or more configuration parameters. The wireless device may not apply (or use) an implicit resource release (e.g., an implicitly preconfigured uplink resource release, etc.), for example, if the one or more configuration parameters do not include a parameter (and / or resource opportunities) indicating the number of skipped uplink grants (e.g., if ImplicitReleaseAfter is not present in the one or more configuration parameters).

[0216] FIG. 19 is an example of one or more data packet transmissions in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE) state according to an aspect of an embodiment of the present disclosure. The wireless device may receive an RRC message configuring uplink resources. The uplink resources may be available, scheduled, and / or configured in the Non-RRC_CONNECTED state. The wireless device may not transmit an uplink packet on one or more opportunities of the uplink resources. The wireless device may count the one or more opportunities. The wireless device may determine to release (e.g., at least one of release, clear, deactivate, and / or suspend) the uplink resources, such as when a number of one or more opportunities that the wireless device skips (and / or does not use) to transmit an uplink packet is equal to a threshold value. For example, the number of one or more opportunities may be a number of consecutive one or more opportunities of the uplink resources that the wireless device skips (and / or does not use).

[0217] The wireless device may count the number of skipped uplink grants (and / or resource opportunities) to determine, for example, whether to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters. For example, m is the number of skipped uplink grants (and / or resource opportunities) that the wireless device counts. The wireless device may determine to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants, and / or one or more configuration parameters, for example, when m reaches (e.g., equals) a threshold value. The threshold value may be configurable, for example, the threshold value may be one, two, three, four, eight, etc., depending on the one or more configuration parameters. For example, the one or more configuration parameters may indicate that the threshold value is not configured (e.g., threshold value=disabled). For example, the wireless device may determine that implicit resource release is not applied (eg, disabled) if, for example, one or more configuration parameters do not include a threshold value.

[0218] The wireless device may count the number of skipped uplink grants (and / or resource opportunities) with a counter. The value of the counter may be referred to as m. The counter may be implemented in one or more ways. For example, the value of the counter may be increased or decreased based on the implemented counter. For example, the counter may be an up counter that counts the number of skipped uplink grants (and / or resource opportunities) in ascending order. In this case, the wireless device may decide to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters, for example, when the value of the counter m reaches a threshold. For example, the counter may be a down counter that counts the number of skipped ascending uplink grants (and / or resource opportunities) in descending order. In this case, the wireless device may, for example, decide to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters if the value of the counter may reach zero (or a second predetermined value) starting from a threshold value (or a first predetermined value). For both counters, the wireless device may, for example, decide to release (clear, deactivate, discard, and / or suspend) one or more uplink radio resources, uplink grants indicating one or more uplink radio resources, and / or one or more configuration parameters if the number of skipped uplink grants (and / or resource opportunities) counted by the wireless device counter reaches a threshold value. In the exemplary embodiment herein, the mechanism introduced based on an up counter may be implemented based on a down counter.

[0219] The wireless device may determine to increase m based on at least one of the following: The wireless device may increase m, for example, if a radio resource opportunity of one or more uplink radio resources is not used (e.g., the wireless device may increase m if the wireless device does not transmit a data packet via a radio resource opportunity of one or more uplink radio resources). The wireless device may increase m, for example, if a radio resource opportunity of one or more uplink radio resources is not used while the wireless device is Non-RRC_CONNECTED. The wireless device may increase m, for example, if no MAC PDU is generated for the uplink grant and / or resource opportunity (e.g., an uplink grant of one or more uplink radio resources and / or a resource opportunity of one or more uplink radio resources). The wireless device may increase m, for example, when a radio resource opportunity of one or more uplink radio resources is used (e.g., the wireless device transmits a data packet via a radio resource opportunity of one or more uplink radio resources) but no response (e.g., one or more HARQ ACKs, HARQ NACKs, L2 (e.g., MAC CE) responses, and / or L3 (e.g., RRC message) responses) corresponding to the data packet is received. The wireless device may increase m, for example, when the wireless device skips a radio resource opportunity of one or more uplink radio resources due to a barring of access to a cell in which the one or more uplink radio resources are configured. The wireless device may increase m, for example, when the wireless device skips a radio resource opportunity of one or more uplink radio resources because the wireless device is in a waiting time (and / or an extended waiting time). The waiting time (and / or an extended waiting time) may define how many seconds the wireless device waits after or in response to receiving an RRC connection rejection before transmitting an RRC connection request message.

[0220] The base station (e.g., network) may maintain a counter synchronized with the wireless device. The base station (e.g., network) may determine to increase m based on at least the following: The base station (e.g., network) may increase m, for example, if the base station does not receive an uplink packet via a radio resource opportunity of one or more uplink radio resources. The base station (e.g., network) may increase m, for example, while the wireless device is Non-RRC_CONNECTED. The base station (e.g., network) may increase m, for example, if the base station (e.g., network) does not transmit a response (e.g., HARQ feedback (ACK and / or NACK)). For example, the base station (e.g., network) may increase m, for example, if the base station receives an uplink packet via a radio resource opportunity of one or more uplink radio resources but does not transmit a response to the uplink packet to the wireless device. For example, the response may be HARQ ACK feedback. For example, the response may be HARQ NACK feedback. For example, the response may be an L2 (e.g., MAC CE) response and / or an L3 (e.g., RRC message) response. The base station (e.g., network) may increase m, for example, when a radio resource opportunity for one or more uplink radio resources is skipped by the wireless device due to a barring of access to a cell in which one or more uplink radio resources are configured. The base station (e.g., network) may increase m, for example, when a radio resource opportunity for one or more uplink radio resources is skipped by the wireless device because the wireless device is in a waiting time (and / or an extended waiting time). The waiting time (and / or extended waiting time) may define how many seconds the wireless device waits after receiving or in response to an RRC connection rejection before transmitting an RRC connection request message.

[0221] The wireless device may determine not to increase m based on at least one of the following: The wireless device may not increase m, for example, while the wireless device is in an RRC_CONNECTED state. The wireless device may not increase m, for example, after or in response to one or more uplink radio resources of the wireless device being suspended (deactivated and / or cleared). The wireless device may not increase m, for example, while a prohibition timer of the wireless device is running. For example, the wireless device may determine the time before an access attempt is made after or in response to an access attempt being prohibited in an access prohibition check based on a prohibition timer (e.g., when the prohibition timer expires). The base station (e.g., network) may maintain the counters in sync with the wireless device. The base station (e.g., network) may determine not to increase m based on at least the following: The base station (e.g., network) may not increase m, for example, while the wireless device is in an RRC_CONNECTED state. The base station (e.g., network) may not increase m, for example, after or in response to one or more uplink radio resources of the wireless device being suspended (deactivated and / or cleared). The base station (e.g., network) may not increase m, for example, while the prohibition timer of the wireless device is running. For example, the wireless device may determine the time before an access attempt is made after or in response to an access attempt being barred by an access barring check based on the prohibition timer (e.g., when the prohibition timer expires).

[0222] The wireless device may reset the counter based on at least one of the following: The wireless device resets (e.g., to zero, in the case of an up counter) after or in response to a successful communication between the wireless device and a base station (e.g., a network). For example, the wireless device resets (e.g., to zero, in the case of an up counter) after or in response to receiving an ACK corresponding to an uplink transmission over one or more uplink radio resources. The wireless device may be in a Non-RRC_CONNECTED state. For example, the wireless device resets (e.g., to zero, in the case of an up counter) after or in response to transmitting an ACK corresponding to receiving a downlink data packet from a base station (e.g., a network) in a Non-RRC_CONNECTED state. For example, the wireless device may not be reset after or in response to a successful communication while the wireless device is in an RRC_CONNECTED state. The base station (e.g., a network) may reset the counter based on at least one of the following: The base station (e.g., network) resets (e.g., to zero in the case of an up counter) after or in response to a successful communication between the wireless device and the base station (e.g., network). For example, the base station (e.g., network) resets (e.g., to zero in the case of an up counter) after or in response to an ACK corresponding to an uplink transmission performed by the wireless device over one or more uplink radio resources. The wireless device may perform an uplink transmission in a Non-RRC_CONNECTED state. For example, the base station (e.g., network) resets (e.g., to zero in the case of an up counter) after or in response to receiving, from the wireless device, an ACK corresponding to a downlink data packet transmitted to the wireless device while the wireless device is in a Non-RRC_CONNECTED state. For example, the base station (e.g., network) may not be reset after or in response to a successful communication while the wireless device is in an RRC_CONNECTED state.

[0223] In an embodiment, the one or more configuration parameters may indicate a value of a Time Alignment Timer (TAT) (e.g., example parameter name: TimeAlignmentTimer) for a cell (and / or a cell group that includes the cell) for which one or more uplink radio resources in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE) state are configured. A cell group that includes the cell may be referred to as a Timing Advance Group (TAG). The value of the TAT may indicate a time for which a timing advance offset value is valid and / or may be used to adjust uplink timing for uplink transmissions to the cell (and / or cells in the cell group). For example, the value of the TAT may determine how long a wireless device determines that a cell (and / or cells belonging to an associated TAG) are uplink time aligned. The wireless device may determine (or adjust) uplink timing of an uplink transmission (e.g., PRACH, PUSCH, SRS, and / or PUCCH transmission) on a cell (and / or a cell of a cell group) based on the timing advance offset value. For example, the timing advance offset value may indicate an amount (and / or length) by which uplink timing for an uplink transmission is delayed or advanced for uplink synchronization. For example, the wireless device may perform the TAT for a time interval (and / or duration) indicated by the value of the TAT. The wireless device may determine that the timing advance offset value is valid (and / or used) to adjust uplink timing for an uplink transmission on a cell (or a cell in a cell group) while the TAT is operating. The wireless device may determine that an uplink from the wireless device to a cell (e.g., a base station) is not synchronized if, for example, a TAT associated with a cell group (e.g., a TAG) to which the cell belongs is not operating and / or has expired.For example, the wireless device may stop to perform uplink transmission on a cell (and / or a cell in a cell group) when, for example, a TAT associated with a cell group (e.g., TAG) to which the cell belongs is not operational and / or expired. The wireless device may stop uplink transmission of a cell due to, for example, the fact that a (e.g., maximum) uplink transmission timing difference between TAGs of the wireless device or a (e.g., maximum) uplink transmission timing difference between TAGs of any MAC entity (e.g., two MAC entities configured for dual connectivity) of the wireless device is exceeded, and the wireless device may determine that a TAT associated with the cell has expired. The wireless device may perform random access preamble (re)transmission and / or MSG A (re)transmission when, for example, a TAT associated with a cell group (e.g., TAG) to which the cell belongs is not operational and / or expired. The wireless device may (re)start the TAT after or in response to receiving a timing advance command indicating (new and / or updated) timing advance offset values ​​for a cell (and / or cells in a cell group). The timing advance command may be received as a MAC CE and / or DCI. The timing advance command may indicate timing advance offset values ​​for cells for which one or more uplink radio resources are in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE) state.

[0224] The wireless device may (re)start the time alignment timer after or in response to transitioning to Non-RRC_CONNECTED, for example, if the wireless device receives (and / or is configured with) one or more uplink radio resources for the Non-RRC_CONNECTED state. For example, the wireless device may (re)start the time alignment timer after or in response to receiving a configuration parameter associated with the time alignment timer (e.g., a timer value for the time alignment timer). The wireless device may (re)start the time alignment timer after or in response to receiving a timing advance offset value. The wireless device may receive a lower layer control message (e.g., DCI or PDCCH) indicating the timing advance offset value. The wireless device may receive a MAC layer control message (e.g., MAC CE and / or RAR) indicating the timing advance offset value. For example, the wireless device may (re)start the time alignment timer after or in response to receiving a timing advance command MAC control element and / or a PDCCH indicating a timing advance adjustment. The wireless device may determine that the timing advance offset value is valid at least while the TAT is operating. The wireless device may verify the TA value based on one or more verification conditions. The wireless device may (re)start the time alignment timer after or in response to determining that the TA is verified. For example, if the TAT has operated for a time interval (or duration) indicated by the value of the TAT, the wireless device may determine that the TAT has expired. The wireless device may determine that the timing advance offset value is invalid in response to expiration of the TAT.

[0225] Terms used herein may be referred to interchangeably and / or as one or more different terms. For example, a timing advance value may be referred to as a timing alignment value. For example, a timing advance offset value may be referred to as a timing alignment offset value. For example, a timing alignment timer may be referred to as a time alignment timer, a timing advance timer, and / or a time advance timer. For example, a timing advance group may be referred to as a timing alignment group.

[0226] In an embodiment, the one or more configuration parameters may indicate a number of opportunities for one or more uplink radio resources (e.g., an example parameter name: NumOccasions). The number of opportunities may indicate that one or more uplink radio resources are one-time use resources (or grants) for a single uplink transmission. The number of opportunities may indicate that one or more uplink radio resources are multiple uplink radio resources. The number of opportunities may indicate that one or more uplink radio resources are one or more periodic radio resources.

[0227] In one example, the one or more configuration parameters may indicate a time domain resource allocation of one or more uplink radio resources. For example, the one or more configuration parameters may indicate a periodicity (e.g., example parameter name: Periodicity) of one or more uplink radio resources in a Non-RRC_CONNECTED state. For example, the one or more configuration parameters may include a time offset. The time offset may be a time domain offset with respect to (and / or associated with) a time reference. The time reference may be a specific SFN (e.g., of H-SFN), a specific subframe number, a specific slot number, a specific symbol number, and / or a combination thereof. The time reference may be predefined (e.g., SFN=0 and / or H-SFN=0). The time reference may be a predefined value (e.g., SFN=0 and / or H-SFN=0), for example, if a field of the time reference is not present in the one or more configuration parameters. For example, the wireless device may receive one or more uplink grants, for example, indicated by the one or more configuration parameters. The one or more uplink grants may indicate one or more uplink radio resources. The one or more uplink radio resources may start at a symbol (of a slot of an SFN of an H-SFN) indicated by the time offset. The one or more uplink radio resources may occur periodically from the symbol with periodicity. For example, the wireless device may determine that, e.g., sequentially, an Nth uplink grant of the one or more uplink grants occurs at a transmission time interval (TTI, e.g., slot, minislot, symbol) based on the time offset and the N*periodicity. The time offset may be defined in terms of a number of symbols, a number of slots, a number of subframes, a number of SFNs, a number of H-SFNs, and / or combinations thereof. For example, the one or more configuration parameters may include a parameter, timeDomainOffset, etc. For example, timeDomainOffset indicates a time offset received by the wireless device from the base station.For example, the one or more configuration parameters may include a parameter, timeReferenceSFN, or the like (e.g., a time reference defined in terms of SFN and / or H-SFN). For example, timeReferenceSFN indicates SFN as a time reference used to determine a time offset of resources in the time domain. For example, SFN may be repeated with a period of 1024 frames. For example, a wireless device may receive one or more configuration parameters indicating timeReferenceSFN=0 via SFN=3. For example, timeReferenceSFN=0 may indicate time reference SFN=0, which is SFN 3 before SFN=3. For example, timeReferenceSFN=0 may indicate time reference SFN=0, which is SFN 1021 after SFN=3. For example, a wireless device may determine the closest SFN in the indicated number prior to receiving a configured grant configuration. For example, in the above example, a wireless device may determine that timeReferenceSFN=0 indicates time reference SFN=0, which is SFN 3 before SFN=3. For example, the wireless device may determine that the Nth uplink grant occurs (and / or the uplink grant reoccurs), eg, consecutively, in symbols for: [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in the frame×numberOfSymbolsPerSlot)+symbol number in the slot]= (timeReferenceSFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+timeDomainOffset×numberOfSymbolsPerSlot+S+N×periodicity) modulo (1024 × numberOfSlotsPerFrame×numberOfSymbolsPerSlot). For example, numberOfSlotsPerFrame is the number of slots in a frame. For example, numberOfSymbolsPerSlot is the number of symbols in a slot. For example, periodicity is the periodicity of one or more uplink radio resources indicated by one or more configuration parameters. For example, S is the symbol number (or symbol offset) indicated by one or more configuration parameters. The above determination of the Nth uplink grant may not require an additional activation message (e.g., DCI, MAC CE, and / or RRC) for the (pre-)configured grant of FIG. 18A to activate (and / or initiate) one or more uplink radio resources (and / or (pre-)configured grants). For example, the wireless device may determine that the Nth uplink grant occurs (and / or the uplink grant reoccurs), eg, consecutively, in symbols for: [(SFN×numberOfSlotsPerFrame×numberOfSymbolsPerSlot)+(slot number in the frame×numberOfSymbolsPerSlot)+symbol number in the slot]=[(SFNstart time×numberOfSlotsPerFrame×numberOfSymbolsPerSlot+slotstart time×numberOfSymbolsPerSlot+symbolstart time)+N×periodicity] modulo(1024×numberOfSlotsPerFrame×numberOfSymbolsPerSlot). The determination of the Nth uplink grant above may require an additional activation message (e.g., DCI, MAC CE, and / or RRC) for the (pre-)configured grant of FIG. 18B to activate (and / or initiate) one or more uplink radio resources (and / or (pre-)configured grants). For example, SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, at which one or more uplink grants are (re-)initialized. For example, the SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol, respectively, at the time when the wireless device receives an indication (e.g., DCI) to (re)initialize (and / or (re)start) one or more uplink grants. For example, the SFNstart time, slotstart time, and symbolstart time are the SFN, slot, and symbol of a PUSCH transmission opportunity at which one or more uplink grants are (re)initialized. For example, the PUSCH transmission opportunity is the first PUSCH opportunity at which one or more uplink grants are (re)initialized.

[0228] The wireless device may (re)initiate transmission via one or more uplink radio resources in the Non-RRC_CONNECTED state based on one or more conditions. For example, the wireless device may receive a configuration parameter indicating one or more conditions. For example, the wireless device may determine whether a cell for which one or more uplink radio resources in the Non-RRC_CONNECTED state are configured supports transmission via one or more uplink radio resources. For example, the wireless device may receive an RRC message (e.g., an SIB). The RRC message may include a configuration parameter indicating whether the cell supports transmission via one or more uplink radio resources. The configuration parameter may indicate a type of transmission supported (or available) via the one or more uplink radio resources. For example, the type may include a control plane (CP) transmission and / or a user plane (UP) transmission. The configuration parameter may indicate which type of network to which the cell is connected supports transmission via one or more uplink radio resources. Depending on the type of network to which the cell is connected, the wireless device may determine whether transmission via one or more uplink radio resources is supported in the cell. For example, the type of network may include one or more generations of a network system (e.g., 5G Core, Evolved Packet Core (EPC), and / or the like) and / or one or more radio technologies (e.g., Wifi, 5G, Bluetooth, and / or the like). For example, the configuration parameters may indicate which type of spectrum (and / or frequency band) supports transmission over one or more uplink radio resources. For example, the type of spectrum may include licensed spectrum and / or unlicensed spectrum. For example, the type of spectrum may include Citizens Broadband Radio Service (CBRS) bands (e.g., wideband in the 3.5 GHz range). For example, the type of spectrum may include mmWave bands (e.g., above 30 GHz).The configuration parameters of the RRC message may indicate a combination of the type of network, the type of spectrum, and / or the type of transmission. For example, in the RRC message, cp-PUR-5GC (e.g., the parameter value may be 'true' / 'false' or 'enabled' / 'disabled') indicates whether CP transmission using PUR is supported in the cell when connected to a 5G core network. For example, the parameter cp-PUR-EPC in the RRC message (e.g., the parameter value may be 'true' / 'false' or 'enabled' / 'disabled') indicates whether CP transmission using PUR is supported in the cell when connected to an EPC. For example, if the RRC message received from the cell indicates cp-PUR-EPC='true' (or 'enabled'), the wireless device determines that PUR is supported in the cell when connected to an EPC.

[0229] The wireless device may (re)initiate transmission over one or more uplink radio resources in the Non-RRC_CONNECTED state based on one or more conditions. For example, the wireless device may (re)initiate transmission over one or more uplink radio resources in the Non-RRC_CONNECTED state if, for example, at least one of the following conditions is met: The wireless device has a valid configuration of one or more uplink radio resources. The wireless device has a valid timing advance value. The wireless device triggers to request establishment of an RRC connection. The wireless device triggers to request resumption of an RRC connection. The wireless device has a valid saved value of a security parameter (e.g., nextHopChainingCount provided in an RRCConnectionRelease message indicating a pause during a previous pause procedure). The wireless device triggers a mobile originated call establishment or resumption request and / or the establishment cause is mo-Data or mo-ExceptionData or delayTolerantAccess. and / or the size of the MAC PDU (e.g., including the entire UL data) is expected to be less than or equal to the transport block size (TBS) configured for PUR.

[0230] For example, the wireless device may determine whether the wireless device has a valid timing advance value based on one or more validation conditions (e.g., TAT-based validation and / or measurement-based validation). For example, the wireless device may determine that a configuration of one or more uplink radio resources is valid based on, e.g., a configuration parameter of the one or more uplink radio resources indicating validity of the configuration. For example, the wireless device receives a message including a configuration parameter. The configuration is valid, e.g., if a field config in the message is set to setup (e.g., true). For example, the configuration is valid, e.g., if a field config is set to release (e.g., false).

[0231] The wireless device may determine whether the timing advance value is valid to be transmitted via one or more uplink radio resources in the Non-RRC_CONNECTED state based on one or more verification conditions. For example, the one or more verification conditions may include a TAT-based verification and / or a measurement-based verification. The wireless device may determine to apply a configured condition during one or more verification conditions. For example, the wireless device receives a message including a configuration parameter of a first verification condition (e.g., TAT-based evaluation) during one or more verification conditions. The message may not include a configuration parameter of a second verification condition (e.g., measurement-based verification) of the one or more verification conditions. In this case, the wireless device may determine whether the timing advance value is valid based on at least the first verification condition. For example, if the message includes configuration parameters of the first verification condition (e.g., TAT-based verification) and the second verification condition (e.g., measurement-based verification), the wireless device may determine whether the timing advance value is valid based on at least the first verification condition and the second verification condition.

[0232] For example, for a TAT-based validation, the wireless device may determine validity of a timing advance value based on the TAT. The wireless device may receive an RRC message including a value of the TAT. The TAT may be for a cell (and / or a TAG including the cell) for which one or more uplink radio resources in a Non-RRC_CONNECTED state are configured. The wireless device may determine that a timing advance value of a transmission over the one or more uplink radio resources is valid, for example, if the TAT is operational. The wireless device may determine that validation of the timing advance value of a transmission is not based on at least the TAT, for example, if a value of the TAT is not configured (e.g., the RRC message does not include a value of the TAT).

[0233] FIG. 20 is an example of one or more data packet transmissions in a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE) state according to an aspect of an embodiment of the present disclosure. A wireless device may receive an RRC message including configuration parameters for uplink resources in the Non-RRC_CONNECTED state. The uplink resources may be available, scheduled, and / or configured in the Non-RRC_CONNECTED state. The wireless device may transmit an uplink packet over an opportunity in one of the uplink resources if, for example, a TA value for the transmission is verified. The wireless device may determine (e.g., verify) that a TA value is valid to be used for one or more data packet transmissions in the Non-RRC_CONNECTED state if, for example, a TAT is running. For example, the wireless device may transmit data over uplink resources in the Non-RRC_CONNECTED state if, for example, the wireless device may determine (e.g., verify) a TA value as valid and / or if the TAT is running. For example, the wireless device may determine that a TA value is invalid if a TAT is not running (and / or has expired). The wireless device may stop (eg, be prohibited from) uplink transmissions over the uplink resources.

[0234] For example, for measurement-based validation, the wireless device may determine based on measurements of DL RSs of a cell for which one or more uplink radio resources are configured. The DL RS may be an SSB, a CSI-RS, a cell-specific RS, etc. For example, the wireless device may determine whether a timing advance value of a transmission over one or more uplink radio resources is valid based on measurements of the DL RS. For example, the measurements of the DL RSs of the cell may be cell measurement quantities (e.g., RSRP, RSRQ, RSSI, etc.). The measurements of the DL RSs may be referred to as serving cell measurements, cell measurements, and / or the like. For example, the wireless device may receive an RRC message including one or more thresholds. For example, the wireless device may measure a received signal strength of at least one DL RS received from a cell (e.g., TRP) for which one or more uplink radio resources are configured. The at least one DL RS may include a synchronization signal (PSS and / or SSS), a CSI-RS, and / or a cell-specific RS. For example, the measurement of the received signal strength is an RSRP of the at least one DL RS. For example, the measurement is an RSRQ and / or a received signal strength indicator (RSSI). The wireless device may determine that a timing advance value for transmission over one or more uplink radio resources is valid, for example, if the measurement is within a range indicated by one or more thresholds. For example, the wireless device may determine that a timing advance value for transmission over one or more uplink radio resources is valid, for example, if the measurement has not changed beyond a range indicated by one or more thresholds since the wireless device measured the previous DL RS. For example, the wireless device measured the previous DL RS based on a measurement configuration that schedules the one or more measurements, for example, independent of resource allocation of the uplink resources. For example, the wireless device measured the previous DL RS for the last TA verification performed by the wireless device for transmission over one or more uplink radio resources.

[0235] The one or more thresholds of the measurement include an increase threshold and / or a decrease threshold. For example, the increase threshold and / or the decrease threshold may indicate a threshold for a change in a measurement value of at least one DL RS in a cell. For example, the increase threshold and / or the decrease threshold may indicate a range in which the wireless device determines that a TA value is valid (e.g., to be used for transmission over one or more uplink radio resources in a Non-RRC_CONNECTED state). For example, the range may indicate a certain region of the cell (e.g., a certain coverage tier of the cell, e.g., a central region, a cell edge region, etc.) in which the TA value is to be used for transmission over one or more uplink radio resources in a Non-RRC_CONNECTED state.

[0236] The increase threshold and / or decrease threshold may indicate the threshold in dBm. For example, the wireless device determines the TA value to be valid, for example, when the measurement value of the DL RS of the cell is less than the increase threshold. For example, the wireless device determines the TA value to be valid, for example, when the measurement value of the DL RS of the cell is equal to or greater than the decrease threshold. For example, the wireless device determines the TA value to be invalid, for example, when the measurement value of the DL RS of the cell is equal to or greater than the increase threshold and / or when the measurement value of the DL RS of the cell is less than the decrease threshold.

[0237] FIG. 21A is an example of TA verification according to one aspect of an embodiment of the present disclosure. A wireless device may receive a message (e.g., an RRC message) including an increase threshold and / or a decrease threshold. For example, the increase threshold and / or the decrease threshold may be an absolute value of a threshold (e.g., in dBm). The TA value may be used for transmission in one or more radio resources in the Non-RRC_CONNECTED state, for example, if a measurement value (e.g., RSRP) is in an RSRP range indicated by the increase threshold and / or the decrease threshold. For example, if the measurement value (e.g., RSRP) is less than the increase threshold and / or higher than the decrease threshold, the wireless device may determine that the TA value is valid. For example, if the measurement value (e.g., RSRP) is higher (or equal) than the increase threshold and / or lower than the decrease threshold, the wireless device may determine that the TA value is invalid.

[0238] The increase threshold and / or decrease threshold may indicate a value, e.g., in dB, for the TA verification. For example, the wireless device determines the TA value to be valid, e.g., if the measurement value of the DL RS of the cell has not increased beyond the increase threshold. For example, the wireless device determines the TA value to be valid, e.g., if the measurement value of the DL RS of the cell has not decreased beyond the decrease threshold. For example, the wireless device determines the TA value to be invalid, e.g., if the measurement value of the DL RS of the cell has increased more than the increase threshold and / or if the measurement value of the DL RS of the cell has decreased more than the decrease threshold. The wireless device may determine how much the measurement value has changed (e.g., not increased and / or not decreased) based on a reference measurement value. For example, the reference measurement value is one or more measurements performed for the last TA verification. For example, the last TA verification may be performed by the wireless device for transmitting over one or more uplink radio resources in the Non-RRC_CONNECTED state.

[0239] FIG. 21B is an example of TA validation according to one aspect of an embodiment of the present disclosure. A wireless device may receive a message (e.g., an RRC message) including an increase threshold and / or a decrease threshold. For example, the increase threshold and / or the decrease threshold may be a threshold value relative to a reference measurement (e.g., in dB). For example, when a wireless device determines whether a TA value is valid to be used for transmission, the wireless device may compare the measurement to the reference measurement. For example, the wireless device may determine that the TA value is valid if, for example, a measurement value of a DL RS of a cell has not increased beyond an increase threshold and / or a measurement value of a DL RS of a cell has not decreased beyond a decrease threshold. Otherwise, the wireless device may determine that the TA value is invalid to be used for transmission over one or more radio resources in a Non-RRC_CONNECTED state.

[0240] FIG. 22 is a geographical example of an increase threshold and / or decrease threshold according to an aspect of an embodiment of the present disclosure. The distance between a cell and a wireless device and the measurement of the signal strength (e.g., RSRP) of the DL RS transmitted from the cell may have an inverse proportional relationship. For example, the greater the distance between the cell and the wireless device, the smaller the measurement of the DL RS (e.g., RSRP). For example, the closer the wireless device is to the cell, the larger the measurement may be. If the measurement (and / or the change in the measurement) is greater than the increase threshold, the wireless device may determine that the TA value is invalid to be used for transmission. For example, the smaller the measurement is, the smaller the wireless device is moving away from the cell. If the measurement (and / or the change in the measurement) of the received signal strength is less than the decrease threshold, the wireless device may determine that the TA value is invalid to be used for transmission. As shown in FIG. 22, the wireless device may determine that the TA value is valid, for example, when the wireless device moves around while keeping a distance from the cell. For example, in this case, the measurement (and / or the change in the measurement) is greater than the decrease threshold and / or is less than the increase threshold.

[0241] The wireless device may receive a message including an increase threshold and a decrease threshold. In this case, the wireless device may use an increase threshold and a decrease threshold for TA verification as a disclosed example according to an aspect of an embodiment of the present disclosure. The wireless device may receive a message including one of the increase threshold and / or the decrease threshold. In this case, the wireless device may use one of the increase threshold and / or the decrease threshold as a disclosed example according to an aspect of an embodiment of the present disclosure. For example, a wireless device in a cell edge region may receive a message including an increase threshold. For example, a wireless device in a cell center region may receive a message including a decrease threshold. The increase threshold and the decrease threshold may not be present in the message. For example, the wireless device may receive a message that does not include field values ​​for the increase threshold and the decrease threshold. In this case, the wireless device may determine that the TA verification is not based on at least measurements (e.g., RSRP, RSRP, and / or RSSI). For example, if the increase threshold and the decrease threshold are not configured, the TA verification based on changes in cell measurements (e.g., RSRP, RSRP, and / or RSSI) is not applied.

[0242] After or in response to transmitting data over one or more uplink radio resources, the wireless device may monitor a PDCCH identified by the RNTI during a response window. For example, the wireless device may receive a message (e.g., an RRC message) indicating the RNTI and / or a size of the response window (e.g., an example parameter name: ResponseWindowsTimer, etc.). The response window may start from a reference time associated with forwarding data over one or more uplink radio resources. For example, the reference time may be a transmission time interval (e.g., a frame, a subframe, a slot, and / or a symbol) during which the wireless device transmits data over one or more uplink radio resources. For example, the reference time may include an end of the corresponding PUSCH transmission (e.g., a transmission of data over one or more uplink radio resources). For example, the reference time may be the first PDCCH opportunity from the end of the corresponding PUSCH transmission (e.g., a transmission of data over one or more uplink radio resources). The reference time may further include a time offset (e.g., predefined or configured in the RRC). For example, the reference time may be a subframe (or slot) including an end of the corresponding PUSCH transmission plus the time offset. For example, the reference time may be the first PDCCH opportunity from the end of the corresponding PUSCH transmission plus a time offset.

[0243] The wireless device may receive a control message (e.g., DCI) over the PDCCH during the time window (e.g., while the ResponseWindowsTimer is running). For example, the received control message (e.g., DCI) may have a CRC scrambled by an RNTI that the wireless device receives for transmission over one or more radio resources in the Non-RRC_CONNECTED state. The control message (e.g., DCI) may include an uplink grant for retransmission of data. The wireless device may (re)start the time window (e.g., ResponseWindowsTimer) after or in response to receiving the uplink grant. For example, the time window (re)starts at the last slot (subframe, symbol) of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant. For example, the time window (re)starts at the first PDCCH opportunity from the end of the PUSCH transmission corresponding to the retransmission indicated by the uplink grant. The control message (e.g., DCI) may indicate an acknowledgement (e.g., L1 ACK) for the transmission of data over one or more radio resources in the Non-RRC_CONNECTED state. In this case, the wireless device may stop the time window (e.g., ResponseWindowsTimer) and / or determine that the transmission of data over one or more radio resources is successful. The control message (e.g., DCI) may include a downlink assignment of a PDSCH including a MAC PDU. If the wireless device successfully decodes the MAC PDU, the wireless device may stop the time window (e.g., ResponseWindowsTimer) and / or determine that the transmission of data over one or more radio resources is successful. The control message (e.g., DCI) may indicate a failure of the transmission of data (e.g., fallback). The wireless device may determine to stop the time window (e.g., ResponseWindowsTimer) after or in response to receiving a control message indicating a failure (e.g., fallback).The wireless device may determine that transmission of data over one or more radio resources has failed, for example, after or in response to receiving a control message indicating a failure (e.g., fallback). The wireless device may initiate a random access procedure, for example, after or in response to receiving a control message indicating a failure (e.g., fallback). The wireless device may initiate a random access procedure, for example, after or in response to receiving a control message indicating a failure (e.g., fallback). The wireless device may determine that a time window (e.g., ResponseWindowsTimer) has expired. The wireless device may determine that a preconfigured uplink grant has been skipped and that a PUR transmission has failed after or in response to expiration of the time window.

[0244] The wireless device and / or base station may use HARQ operations and / or processes for one or more retransmissions of an uplink transmission in a Non-RRC_CONNECTED state. For example, the wireless device may transmit a data packet via one or more uplink radio resources configured for a Non-RRC_CONNECTED state (e.g., as shown in FIG. 17). The wireless device may monitor the PDCCH, for example, after or in response to the transmission of the data packet while maintaining the RRC state as a Non-RRC_CONNECTED state. The wireless device may receive a DCI via the PDCCH that may indicate an uplink grant for retransmission of the data packet. The uplink grant may indicate one of the one or more uplink radio resources as the uplink radio resource for the retransmission. The uplink grant may indicate an uplink radio resource that is independent (e.g., assigned separately) from the one or more uplink radio resources for the retransmission. The wireless device may receive an indication (e.g., a different type of DCI) indicating to perform an RA procedure, for example, instead of an uplink grant. The indication may indicate a failure to transmit the data packet. The wireless device may transition to an RRC CONNECTED state, e.g., an RRC connection setup procedure and / or an RRC restart procedure. The wireless device may initiate (or perform) an RRC connection setup procedure and / or an RRC restart procedure based on an RA procedure. The wireless device may initiate an RA procedure based on receiving an indication (e.g., indicating that the wireless device performs an RA procedure). The wireless device may initiate an RA procedure based on receiving a paging message (e.g., indicating that the wireless device performs an RA procedure) and / or based on the arrival of an uplink packet. While the wireless device is in the RRC CONNECTED state, one or more uplink radio resources configured for a Non-RRC_CONNECTED state are not used.The wireless device may not transmit (and / or may stop transmitting) data packets over one or more uplink radio resources, for example, when the RRC state is the RRC_CONNECTED state. For example, the wireless device may release (clear, deactivate, suspend, and / or discard) one or more uplink radio resources configured for a Non-RRC_CONNECTED state and / or an uplink grant indicating one or more uplink radio resources after or in response to the RRC state transitioning to the RRC CONNECTED state. For example, the wireless device may suspend one or more uplink radio resources configured for a Non-RRC_CONNECTED state and / or an uplink grant indicating one or more uplink radio resources after or in response to the RRC state transitioning to the RRC CONNECTED state.

[0245] The wireless device may transmit a message (e.g., an RRC message such as a PURConfigurationRequest) requesting one or more parameters of a (pre-)configured grant indicating one or more uplink radio resources in a Non-RRC_CONNECTED state (e.g., RRC_INACTIVE and / or RRC_IDLE). The wireless device may initiate a procedure, such as, for example, a UE initiated procedure, to transmit the message. The wireless device may transmit the message in response to receiving a request from a base station, for example, a BS initiated procedure. The wireless device may transmit the message while the wireless device is in any of the RRC states, RRC_CONNECTED, RRC_INACTIVE, and / or RRC_IDLE. The wireless device may transmit the message while the wireless device is in a particular RRC state. For example, the wireless device may transmit the message while the wireless device is in a Non-RRC_CONNECTED state. For example, the wireless device may transmit the message while the wireless device is in an RRC_CONNECTED state. The message may indicate data traffic information. For example, the message may indicate a number of times of one or more uplink radio resources in the Non-RRC_CONNECTED state, e.g., an exemplary parameter, requestedNumOccasions. For example, the message may indicate a periodicity of one or more uplink radio resources in the Non-RRC_CONNECTED state, e.g., an exemplary parameter, requestedPeriodicity. For example, the message may indicate a TB size of data packets to be transmitted over one or more uplink radio resources in the Non-RRC_CONNECTED state, e.g., an exemplary parameter, requestedTBS. For example, the message may indicate a time offset for one or more uplink radio resources in the Non-RRC_CONNECTED state, e.g., an exemplary parameter, requestedTimeOffset. The wireless device may not receive (e.g., expect to receive) a response to the message from the base station.For example, the wireless device may receive from the base station one or more configuration parameters for transmitting uplink data over one or more uplink radio resources in the Non-RRC_CONNECTED state.

[0246] The wireless device may be configured with an operating band of a cell for transmitting in a Non-RRC_CONNECTED state. The operating band for transmitting may be a carrier bandwidth. The operating band may include a DL band and / or a UL band. The operating band for transmitting may be a BWP. The BWP may include a DL BWP (e.g., a DL band) and / or a UL BWP (e.g., a UL band). For example, the wireless device may receive a message (e.g., an RRC message and / or an RRC release message) including a configuration of an operating band for transmitting and receiving in a Non-RRC_CONNECTED state in a cell. The message may indicate a configuration based on a number of RBs (or PRBs) and a frequency location (e.g., a location of a center frequency). The configuration may indicate a numerology (e.g., subcarrier spacing) to be used in the operating band. The configuration may indicate separate numerologies (e.g., subcarrier spacing) for the DL band (e.g., DL BWP) and the UL band (e.g., UL BWP). The numerology (e.g., subcarrier spacing) configured for the DL band (e.g., DL BWP) and the UL band (e.g., UL BWP) may be different or the same.

[0247] The message may indicate the location and range of the operating band (e.g., start, size and / or center frequency and bandwidth, etc.). The location and range of the operating band (e.g., start, size and / or center frequency and bandwidth, etc.) may be defined in terms of resource units (e.g., RBs and / or PRBs), e.g., as multiples of resource units. The location and range of the operating band may be at least a portion of one carrier of the cell. The message may indicate the location and range of the operating band based on a frequency offset and bandwidth relative to a center frequency of the carrier bandwidth of the cell. The message may indicate the location and range of the operating band based on a frequency offset and bandwidth of the operating band relative to a center frequency (e.g., initial BWP) at which a synchronization signal detected by the wireless device is located.

[0248] The message may indicate numerology information (e.g., micro- and / or subcarrier spacing) used in the operating band. The wireless device may determine the RE structure from the numerology information. The message may include configuration parameters for the control channel (e.g., PDCCH and / or PUCCH), the data channel (e.g., PDSCH and / or PUSCH), and / or the reference signal (SSB, CSI-RS, and / or SRS). The message may indicate a frequency location of the control channel, the data channel, and / or the reference signal based on a frequency offset relative to a reference location in the operating band. For example, the reference location may be a point where a start point (and / or an end point) of the first RB coincides with a start point (and / or an end point) of the operating band. For example, one or more radio resources in the Non-RRC_CONNECTED state may be assigned to a start point (e.g., having a frequency offset from the reference location) with a size defined in terms of a number of RBs (or PRBs). The wireless device may determine a location and / or a size of the control channel, the data channel, and / or the reference signal based on the determined RE structure.

[0249] One or more radio resources in the Non-RRC_CONNECTED state may be assigned to an operating band including one or more subbands (e.g., BWP). For example, one or more radio resources in the Non-RRC_CONNECTED state may be assigned to a specific subband in the operating band. For example, a message received by a wireless device may indicate an operating band including one or more subbands (e.g., BWP). The message may indicate one or more subbands having distinct locations (e.g., frequency locations), sizes (e.g., bandwidths), and / or numerologies (e.g., subcarrier spacing). The RE structure for configuring one or more subbands and the RE structure for configuring the operating band may be different. A DL band (e.g., DL BWP) and a UL band (e.g., UL BWP) may be configured separately. For example, the DL band and the UL band may have different configuration information, for example, with respect to frequency locations and numerologies (e.g., subcarrier spacing). For example, the wireless device may receive DL control messages (e.g., DCI via PDCCH) and / or DL ​​data (e.g., transport blocks via PDSCH) based on information of an operating band of a DL band (and / or sub-band). The wireless device may transmit UL control (e.g., PUCCH) and / or UL data (e.g., transport blocks via PUSCH) based on information of an operating band (and / or sub-band) configured in a UL band. For example, one or more radio resources in a Non-RRC_CONNECTED state may be assigned per sub-band. For example, the frequency location and / or the size of the one or more radio resources may be per sub-band.

[0250] For transmissions over one or more radio resources in the Non-RRC_CONNECTED state, the base station may send a message (e.g., an RRC message) to the wireless device to configure configuration parameters. The configuration parameters may include one or more fields indicating at least one of the following: an antenna port used for transmissions over one or more radio resources in the Non-RRC_CONNECTED state; a DMRS configuration used for transmissions over one or more radio resources in the Non-RRC_CONNECTED state; a (pre-)configured grant timer value (e.g., the (pre-)configured grant timer may be a multiple of a period); a frequency domain resource allocation; a frequency hopping configuration (e.g., intra-slot frequency hopping and / or inter-slot frequency hopping. If the field is not present, frequency hopping is not configured); a frequency hopping offset, for example, to be used if frequency hopping is enabled; an MCS table that the wireless device can use for PUSCH (e.g., PUSCH with / without transform precoding). For transmissions over one or more radio resources in the Non-RRC_CONNECTED state, for example, if the field is not present, the wireless device may determine a predefined MCS (e.g., qam64). The modulation order, code rate and / or TB size for the transmission over the one or more radio resources. The number of HARQ processes configured for transmission over the one or more radio resources in the NON-RRC_CONNECTED state. The uplink power control parameters for the transmission over the one or more radio resources, e.g., a closed-loop uplink power control indicator and / or index, one or more reference power values ​​(e.g., p0), and / or a path loss scaling value (e.g., Alpha). The periodicity of the one or more radio resources, e.g., a valid periodicity value, may be determined (predefined) based on a numerology (e.g., subcarrier spacing) and / or the periodicity may be an absolute time value and / or may be defined in terms of TTI (symbol, slot, subframe, system frame, and / or any combination thereof).RBG size for PUSCH transmission over one or more radio resources; Redundancy version (RV) sequence (e.g., [0 2 3 1], [0 3 0 3]) for transmission over one or more radio resources; Number of repetitions for transmission over one or more radio resources; Activation type indicator indicating whether additional activation messages (e.g., DCI, MAC CE, and / or RRC) are required to activate one or more radio resources (e.g., Figures 18A and 18B); SRS resource indicator indicating the SRS resource to be used; Time domain assignment indicating the starting symbol (e.g., the starting symbol number (or symbol offset) S used to determine the Nth uplink grant) and length L (e.g., the value of the time domain assignment can be a combination of starting symbol and length); PUSCH mapping type for transmission over one or more radio resources; Time domain offset defined with respect to a time reference (e.g., SFN=0 and / or timeReferenceSFN); Indicator indicating whether the beta offset value is dynamically or semi-statically configured. Here, the beta offset value is used to determine the uplink power and / or UCI multiplexing of the PUSCH transmission over one or more radio resources.

[0251] One or more radio resources may be configured with a particular BWP. For example, the wireless device may receive a message (e.g., an RRC message) including configuration parameters for the particular BWP. The particular BWP may include a DL BWP and / or a UL BWP. The configuration parameters may indicate a numerology (e.g., subcarrier spacing) used for the particular BWP. The configuration parameters may indicate a numerology to be applied for the DL BWP and / or the UL BWP. The configuration parameters may include separate fields and / or indicators indicating the numerology used for the DL BWP and / or the UL BWP, respectively. The numerology used for the DL BWP and / or the UL BWP may be the same or different. The configuration parameters may indicate radio resource configuration parameters for DL ​​and / or UL control channels (e.g., PDCCH and / or PUCCH) used for transmission over the one or more radio resources. The configuration parameters may be radio resource configuration parameters for DL ​​and / or UL data channels (e.g., PDSCH and / or PUSCH) used for transmission over the one or more radio resources. DL control and / or data channels (e.g., PDCCH and / or PDSCH) may be configured within a DL BWP. UL control and / or data channels (e.g., PUCCH and / or PUSCH) may be configured within a UL BWP.

[0252] The particular BWP may be an initial BWP. For example, the DL BWP of the particular BWP may be an initial DL BWP. For example, the UL BWP of the particular BWP may be an initial UL BWP. The particular BWP may be configured separately from the initial BWP. For example, the DL BWP of the particular BWP may be a different form than the initial DL BWP. For example, the UL BWP of the particular BWP may be different from the initial UL BWP. For example, one or more radio resources may be associated with a DL BWP and / or a UL BWP. For example, a PDCCH (e.g., an ACK, NACK, and / or fallback response transmitted via one or more radio resources) and / or a PDSCH (e.g., an RRC response to an RRC message transmitted via one or more radio resources) associated with a transmission via one or more radio resources may be configured with a DL BWP. For example, a PUCCH (e.g., a response to an ACK and / or NACK to a PDSCH) and / or a PUSCH (e.g., data via one or more radio resources associated with a transmission via one or more radio resources) may be configured with a UL BWP. The wireless device may determine that a particular BWP (e.g., a DL BWP and / or a UL BWP) is an initial BWP (e.g., an initial DL BWP and / or an initial UL BWP, respectively) if, for example, a field indicating a configuration (e.g., a frequency location, a bandwidth, and / or a numerology (e.g., subcarrier spacing)) of a particular BWP that differs from the initial BWP is not present in the configuration parameters indicating one or more radio resources.

[0253] The particular BWP may be the last BWP that the wireless device used in RRC_CONNECTED. For example, the DL BWP of the particular BWP may be the last DL BWP that the wireless device uses in the RRC_CONNECTED state. For example, the UL BWP of the particular BWP may be the last UL BWP that the wireless device uses in RRC_CONNECTED. For example, the wireless device may transition from the RRC_CONNECTED state to a Non-RRC_CONNECTED (e.g., RRC_INACTIVE and / or RRC_IDLE) state. The BWP (e.g., the last DL BWP and / or the last UL BWP) that the wireless device uses in the RRC_CONNECTED state may be used in the transitioned Non-RRC_CONNECTED state. The wireless device may, for example, determine that a particular BWP (e.g., a DL BWP and / or a UL BWP) is a BWP (e.g., the last DL BWP and / or the last UL BWP, respectively) if, for example, a field indicating a configuration (e.g., a frequency location, bandwidth, and / or a numerology (e.g., subcarrier spacing)) of the particular BWP that is different from the last BWP is not present in the configuration parameters indicating one or more radio resources.

[0254] A particular BWP may be configured separately from the initial BWP. For example, the DL BWP of a particular BWP may be of a different form than the initial DL BWP. For example, the UL BWP of a particular BWP may be different from the initial UL BWP. For example, one or more radio resources may be associated with a DL BWP and / or a UL BWP. For example, a PDCCH (e.g., an ACK, NACK, and / or fallback response transmitted via one or more radio resources) and / or a PDSCH (e.g., an RRC response to an RRC message transmitted via one or more radio resources) associated with a transmission via one or more radio resources may be configured with a DL BWP. For example, a PUCCH (e.g., a response to an ACK and / or NACK to a PDSCH) and / or a PUSCH (e.g., data via one or more radio resources associated with a transmission via one or more radio resources) may be configured with a UL BWP.

[0255] FIG. 23 is an example of one or more radio resources in a BWP (e.g., DL BWP and / or UL BWP) according to an aspect of an embodiment of the present disclosure. The wireless device may receive a message (e.g., a broadcast message and / or a wireless device specific RRC message) including configuration parameters of an initial BWP (e.g., initial DL BWP and / or initial UL BWP). The initial BWP may be for cell search and / or initial / random access. For example, the wireless device may receive an SSB (e.g., a cell-defined SSB) via the initial DL BWP. For example, the wireless device may perform a random access procedure via the initial BWP. For example, the wireless device may transmit Msg1, Msg3, and / or Msg A via the initial UL BWP. The wireless device may receive Msg2, Msg4, and / or Msg B via the initial DL BWP. The one or more radio resources configured for transmission in Non-RRC_CONNECTED may be configured in a BWP different from the initial BWP. The BWP may be the last BWP that the wireless device uses in the RRC_CONNECTED state (e.g., before transitioning to a Non-RRC_CONNECTED state). The BWP may be for transmission and / or reception for a Non-RRC_CONNECTED wireless device. One or more radio resources for transmission may be configured in the UL BWP of the BWP. The PDCCH and / or PDSCH may be configured in the DL BWP of the BWP. The wireless device may deactivate the BWP, for example, when the RRC state of the wireless device changes (e.g., to an RRC_CONNECTED state). One or more radio resources and / or PUCCH associated with a transmission in the Non-RRC_CONNECTED state may be configured in an initial UL BWP. The PDCCH and / or PDSCH associated with a transmission in the Non-RRC_CONNECTED state may be configured in an initial DL BWP. The message may indicate whether the BWP is configured separately from the initial BWP.

[0256] The wireless device may perform downlink and / or uplink beam management in a Non-RRC_CONNECTED state with the base station. Downlink and / or uplink beam management may include downlink and / or uplink beam measurement procedures, (re)configuration of one or more beams, beam activation of one or more beams, and beam selection between one or more beams.

[0257] An indicator of a reference signal in the downlink and / or uplink beam management may indicate a beam (e.g., a TX beam and / or an RX beam of the wireless device) to use in the Non-RRC_CONNECTED state. For example, the wireless device may receive a message (e.g., an RRC message) including configuration parameters for one or more radio resources in the Non-RRC_CONNECTED state. The configuration parameters may indicate one or more reference signals. The one or more reference signals may include an SSB identified by an SSB index / identifier, a CSI-RS identified by a CSI-RS index / identifier (and / or a CSI-RS resource index / identifier). The one or more reference signals may include an SRS identified by an SRS index / identifier (e.g., an SRS resource index / identifier, an SRS resource set index / identifier, and / or a combination thereof). The reference signal may represent a particular beam. For example, an SSB may represent a wide beam. For example, a CSI-RS may represent a narrow beam. For example, an SRS may represent a TX beam of the wireless device.

[0258] The configuration parameters of the message may include indicators indicating which reference signals are associated with which transmissions (e.g., PUSCH, PUCCH, and / or SRS) and / or which receptions (e.g., PDCCH and / or PDSCH).

[0259] For example, the configuration parameters may include an indicator indicating which reference signals are associated with reception of data (e.g., PDSCH) and / or control signals (e.g., PDCCH) in the Non-RRC_CONNECTED state. For example, the data and / or control signals may be associated with transmission over one or more radio resources in the Non-RRC_CONNECTED state. For example, the reception may be for receiving a response to a transmission (e.g., an RRC response over the PDSCH and / or an L1 ACK / NACK / fallback over the PDCCH). For example, the indicator may be a parameter for configuring a QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and the DM-RS port of the PDSCH, the DM-RS port of the PDCCH, and / or the CSI-RS port of the CSI-RS resource. The parameter may include one or more TCI states. Each of the one or more TCI states may include at least one of one or more DL RS (e.g., SSB, CSI-RS, any combination), cell index / identifier, BWP index / identifier, and / or QCL relationship type (e.g., one or more large-scale characteristics). For example, the indicator may be a TCI state of a particular channel configuration (e.g., PDSCH, PDCCH (e.g., CORESET)). For example, a PDSCH and / or PDCCH (e.g., CORESET) configuration may include at least one of one or more TCI states. For example, a TCI state of a PDSCH may indicate a QCL relationship between one or more DL reference signals (e.g., SSB and / or CSI-RS) and a DM-RS port of the PDSCH. The wireless device may determine an RX beam to be used to receive data via the PDSCH based on the TCI state (e.g., the QCL relationship of the TCI state). For example, the TCI state of the PDCCH may indicate the QCL relationship between one or more DL reference signals (eg, SSB and / or CSI-RS) and the DM-RS port of the PDCCH.The wireless device may determine an RX beam to be used to receive control signals via the PDCCH based on the TCI state (e.g., a QCL relationship of the TCI state).

[0260] A wireless device may receive one or more messages that (re)configure, update, and / or activate a TCI state of a PDSCH and / or a PDCCH (e.g., CORESET). For example, a first control message (e.g., an RRC message) that the wireless device receives may indicate at least one TCI state used for a PDSCH and / or a PDCCH (e.g., CORESET). For example, a first control message (e.g., an RRC message) that the wireless device receives may indicate one or more TCI states. A second control message (e.g., another RRC message, a DCI, and / or a MAC CE) that the wireless device receives may indicate at least one of the one or more TCI states used for a PDSCH and / or a PDCCH (e.g., CORESET). For example, a first control message (e.g., an RRC message) that the wireless device receives may indicate one or more TCI states. A second control message (e.g., an RRC message, a MAC CE, and / or a DCI) that the wireless device receives may indicate (or activate) at least a first one of the one or more TCI states. A third control message (e.g., an RRC message, a MAC CE, and / or a DCI) received by the wireless device may indicate at least a second one of the at least a first one of the one or more TCI states used for the PDSCH and / or PDCCH (e.g., CORESET).

[0261] The wireless device may receive configuration parameters that include indicators indicating which reference signals are associated with data (e.g., PUSCH) and / or control signal (e.g., PUCCH) transmissions related to transmission over one or more radio resources.

[0262] For example, the indicator may include spatial relationship information. The spatial relationship information may be for transmission via PUSCH, PUCCH, and / or SRS. The wireless device may determine (e.g., identify) the particular spatial relationship information based on an index and / or identifier of the particular spatial relationship information. The spatial relationship information may indicate at least one of a cell index / identifier, one or more DL RSs (e.g., SSB, CSI-RS, and / or any combination thereof), an SRS resource index / identifier, a BWP index / identifier, a path loss criterion RS index / identifier, and / or a power control parameter. The wireless device may determine an antenna port and / or a precoder to be used for transmission via PUSCH and / or PUCCH based on the spatial relationship information.

[0263] For example, the indicator may be spatial relationship information of a particular channel configuration (e.g., srs-spatial-relation-information of PUSCH and / or pucch-spatial-relation-information of PUCCH). For example, a PUSCH configuration may include at least one spatial relationship information. For example, a PUCCH configuration may include at least one spatial relationship information. The spatial relationship information of PUSCH may be different from the one of PUCCH. The spatial relationship information of PUSCH may be the same as the one of PUCCH. The spatial relationship information of PUSCH and PUCCH may be configured separately and / or independently. There may be one or more spatial relationship information applied to PUSCH and PUCCH (and / or used for PUCCH).

[0264] The wireless device may determine an antenna port and / or a precoder to be used for the PUSCH based on the spatial relationship information of the PUSCH. For example, the wireless device receives a message including configuration parameters for transmission over one or more radio resources in a Non-RRC_CONNECTED state. The configuration parameters (e.g., an SRS resource indicator) may indicate an SRS resource of an SRS resource set. The SRS resource may include the spatial relationship information. The wireless device may determine to use the same antenna port as the SRS port of the SRS resource for transmission over the one or more radio resources. The wireless device may transmit data over the one or more radio resources using the same antenna port based on the determination.

[0265] For example, the wireless device may determine the antenna port and / or precoder used for the PUCCH based on the spatial relationship information of the PUCCH. For example, the wireless device may receive a message including configuration parameters of the PUCCH in the Non-RRC_CONNECTED state. The wireless device may transmit uplink control signals on the PDSCH in the Non-RRC_CONNECTED state via the PUCCH for HARQ feedback (e.g., ACK or NACK) for SR transmission and / or measurement report. The configuration parameters (e.g., PUCCH spatial relationship information) may indicate spatial settings (e.g., precoder and / or spatial domain filter) for the PUCCH transmission and parameters for PUCCH power control. The wireless device may determine a spatial domain filter to be used for reception of the DL RS indicated by the spatial relationship information for the PUCCH transmission in the Non-RRC_CONNECTED state. For example, if the spatial relationship information of the PUCCH includes an SSB index / identifier of the SSB, the wireless device may transmit the PUCCH using the same spatial domain filter as for reception of the SSB for the cell. For example, if the spatial relationship information of the PUCCH includes a CSI-RS index / identifier for the CSI-RS (e.g., an NZP-CSI-RS resource index / identifier), the wireless device may transmit the PUCCH using the same spatial domain filter as the reception of the CSI-RS for the cell. For example, if the spatial relationship information of the PUCCH includes an SRS index / identifier for the SRS (e.g., an SRS resource), the wireless device may transmit the PUCCH using the same spatial domain filter as the transmission of the SRS for the cell and / or UL BWP.

[0266] The wireless device may receive one or more messages that (re)configure, update, and / or activate spatial relationship information of the PUSCH, PUCCH, and / or SRS. For example, a first control message (e.g., an RRC message) that the wireless device receives may indicate at least one spatial relationship information used for the PUSCH, PUCCH, and / or SRS. For example, a first control message (e.g., an RRC message) that the wireless device receives may indicate the one or more spatial relationship information. A second control message (e.g., another RRC message, DCI, and / or MAC CE) that the wireless device receives may indicate at least one of the one or more spatial relationship information used for the PUSCH, PUCCH, and / or SRS. For example, a first control message (e.g., an RRC message) that the wireless device receives may indicate the one or more spatial relationship information. A second control message (e.g., an RRC message, MAC CE, and / or DCI) that the wireless device receives may indicate (or activate) at least a first one of the one or more spatial relationship information. A third control message (e.g., an RRC message, a MAC CE, and / or a DCI) received by the wireless device may indicate at least a second one of the at least a first one of the one or more spatial relationship information used for the PUSCH, the PUCCH, and / or the SRS.

[0267] FIG. 24 is an example of beam management for transmission and / or reception in a Non-RRC_CONNECTED state according to one aspect of an embodiment of the present disclosure. A wireless device may receive a message including configuration parameters for transmission / reception in a Non-RRC_CONNECTED state. The configuration parameters may indicate the configuration of radio resources of PUSCH, PDCCH, PDSCH, and / or PUCCH used in the Non-RRC_CONNECTED state. The configuration parameters may indicate one or more radio resources for uplink transmission (e.g., via PUSCH) in the Non-RRC_CONNECTED state. The configuration parameters may indicate which beam (e.g., reference signal) is used to transmit (e.g., via PUSCH and / or PUCCH) or receive (e.g., via PDSCH and / or PDCCH). For example, in FIG. 24, the wireless device transmits data via one or more radio resources in the Non-RRC_CONNECTED state using a first beam. The wireless device may start monitoring the PDCCH using a third beam. The wireless device may receive DCI including a downlink allocation of PDSCH via PDCCH. The wireless device may receive PDSCH using a fourth beam. The wireless device may transmit HARQ feedback (e.g., ACK or NACK) via PUCCH using a second beam. The base station may receive or transmit data using different beams and / or the same beam, e.g., a first beam for PUSCH reception, a second beam for PDCCH transmission, a third beam for PDSCH transmission, and / or a fourth beam for PUCCH reception. The wireless device may receive a second message (e.g., an RRC message, a MAC CE, DCI, and / or a combination thereof) to reconfigure, change, activate / deactivate, and / or update beam configurations of PUSCH, PDCCH, PDSCH, and / or PUCCH.

[0268] In the Non-RRC_CONNECTED state, the wireless device may perform one or more procedures, for example, the wireless device may perform a system information (SI) acquisition procedure, a cell (re)selection procedure, paging message reception, and / or data transmission over one or more radio resources in the Non-RRC_CONNECTED state.

[0269] For example, the wireless device may receive AS, NAS- and positioning assistance data information via an SI acquisition procedure. A wireless device in a non-RRC_CONNECTED state may determine valid versions of (at least) the MIB and / or one or more SIBs (e.g., SIB1-SIB4, SIB5, and / or SIB11) based on the SI acquisition procedure. The wireless device may initiate (perform) a system information (SI) acquisition procedure upon cell selection (e.g., upon power-up), cell reselection, return from out-of-coverage, after reconfiguration due to synchronization completion, after entering the network from another RAT, upon receiving an indication that the system information has changed (e.g., indication of a short message received at a paging occasion), upon receiving a Public Warning System (PWS) notification, upon receiving a positioning request from higher layers, and / or if there is no valid version of the SIB stored in the wireless device.

[0270] By performing one or more procedures, the wireless device may receive cell configuration parameters (e.g., in a MIB and / or SIB) of a cell in which one or more radio resources for transmission in a Non-RRC_CONNECTED state are configured for the wireless device. For example, in an SI acquisition procedure, the wireless device receives a MIB and / or SIB (e.g., SIB1 and / or any SIB broadcast / multicast / unicast). The MIB and / or SIB may indicate cell configuration parameters (e.g., numerology, UL / DL BWP configuration, transmit SSB, and / or random access configuration parameters) of the cell. The values ​​of the cell configuration parameters may be the same as the values ​​received by the wireless device at a reference time. For example, the reference time may be the time when the wireless device receives parameters (e.g., UL grant, periodicity, power control parameters, beam indicators, etc.) associated with one or more radio resources for transmission in a Non-RRC_CONNECTED state. For example, the reference time may be when the wireless device transitions an RRC state from an RRC_CONNECTED state to a Non-RRC_CONNECTED state and / or when the wireless device receives an RRC release message. For example, the reference time may be when the wireless device transmits data over one or more radio resources. For example, the reference time may be when the wireless device performs the last SI acquisition procedure. One or more values ​​of the cell configuration parameters of the cell may be different from the values ​​received by the wireless device at the reference time.

[0271] In multi-beam operation, a cell may, for example, transmit multiple DL RSs (e.g., multiple SSBs, CSI / RS, and / or the like) using multiple beams (e.g., TX beams of the cell). One or more radio resources of the Non-RRC_CONNECTED state configured in the cell may be configured with multiple beams. For example, a channel for transmission and / or reception in the Non-RRC_CONNECTED state (e.g., PDCCH, PDSCH, PUSCH, and / or PUCCH) may be associated with a first beam of the multiple beams. For example, the wireless device may receive a message (e.g., an RRC message, MAC CE, DCI, and / or any combination thereof) including a radio resource configuration parameter indicating an association between the channel and the first beam. For example, the radio resource configuration parameter may indicate that the beam configuration (e.g., TCI and / or spatial relationship information) of the channel includes a first DL RS of the multiple DL RSs. The first DL RS may represent a first beam (e.g., as shown in FIG. 24). For example, one of the multiple DL RSs may be associated with one or more channels (e.g., a PDCCH, a PDSCH, a PUSCH, and / or a PUCCH). The wireless device may determine an antenna port and / or a precoder (e.g., a spatial domain filter) to be used for transmission and / or reception performed over the channel based on the association. For example, the wireless device may determine an antenna port and / or a precoder (e.g., a spatial domain filter) based on one used to receive the first DL RS.

[0272] In multi-beam operation, the wireless device may determine cell measurement values ​​of a cell among multiple beams of the cell. The cell measurement values ​​(e.g., RSRP, RSRQ, RSSI, etc.) of the cell may be referred to as serving cell measurements, cell measurements, and / or the like. The wireless device may receive one or more DL RSs from the cell (and / or base station). The cell may transmit one or more DL RSs using multiple beams. The one or more DL RSs may be SSB, CSI-RS, and / or cell-specific RS, and / or any type of RS transmitted from the cell and / or for the wireless device. For example, each of the one or more DL RSs may represent and / or be associated with at least one of the multiple beams. For example, the wireless device may determine cell measurement values ​​based on measured power values ​​(e.g., RSRP, RSRQ, RSSI, and / or the like) of the one or more DL RSs received from the cell.

[0273] In multi-beam operation, the wireless device may determine a cell measurement value by a function (e.g., a linear average) of measured power values ​​of one or more DL RSs (e.g., RSRP, RSRQ, RSSI, and / or the like). The measured power values ​​of the DL RSs may be referred to as beam measurements of the DL RSs. For example, the wireless device may determine a cell measurement value as an average (e.g., a linear average) of measured power values ​​of one or more DL RSs and / or beam measurements of one or more DL RSs.

[0274] The wireless device may receive a message (e.g., a SIB and / or an RRC release message) including one or more parameters indicating how many DL RSs (e.g., beams) are used to determine the cell measurement value. The one or more parameters may include a first parameter indicating a number of the one or more DL RSs used to determine that the cell measurement value is less than or equal to a first threshold (e.g., nrofSS-BlocksToAverage, and / or maxRS-IndexCellQual). The one or more parameters may include a second parameter indicating a second threshold (e.g., absThreshSS-BlocksConsolidation, and / or threshRS-Index). The wireless device may select at least one DL RS from among the one or more DL RSs to determine the cell measurement value. For example, a measured power value of the at least one DL RS selected by the wireless device may be higher than the second threshold. For example, a number of the at least one DL RS may be less than or equal to the first threshold.

[0275] Among the one or more DL RSs, there may be M DL RSs with measured power values ​​higher than a second threshold. For example, if M is greater than the first threshold, the wireless device may select N DL RSs from among the M DL RSs (e.g., N≦first threshold). For example, the N DL RS may have the N highest measured power values ​​among the one or more DL RSs. For example, the wireless device may randomly select the N DL RSs from among the M DL RSs and / or from among the one or more DL RSs.

[0276] The first threshold may not be configured. In this case, the number of at least one DL RS that the wireless device selects from among the one or more DL RSs may be predefined (e.g., by an RRC message and / or a MIB / SIB) and / or may be semi-statically configured. For example, if the message received by the wireless device does not include a field indicating the first threshold (e.g., not configured and / or not indicated), the wireless device may select the cell measurement value based on the DL RS as the highest measured power value.

[0277] The second threshold may not be configured. In this case, the number of at least one DL RS that the wireless device selects from among one or more DL RSs may be predefined (e.g., by an RRC message and / or a MIB / SIB) and / or may be semi-statically configured. For example, if the message received by the wireless device does not include (e.g., is not configured and / or is not indicated) a file indicating the second threshold, the wireless device may select a cell measurement value based on the DL RS as the highest measured power value.

[0278] There may be cases where the measured power value of one or more DL RSs is equal to or less than the second threshold. In this case, the number of the at least one DL RS that the wireless device selects from among the one or more DL RSs may be predefined (e.g., by an RRC message and / or a MIB / SIB) and / or semi-statically configured. For example, the wireless device may select the cell measurement value as the highest measured power value based on the DL RS.

[0279] The wireless device may use cell measurement values ​​of the cells to validate transmissions (to the cell) and / or receptions (from the cell) in the Non-RRC_CONNECTED state. For example, the wireless device may determine whether a TA value is valid based on the cell measurement values ​​(e.g., serving cell RSRP value). For example, the wireless device may determine a TA value for a transmission over one or more radio resources in the Non-RRC_CONNECTED state if, for example, at least one of the following conditions is met: the TAT is running; the cell measurement value (e.g., serving cell RSRP measurement value) has not increased by more than an increase threshold (e.g., since the last TA validation); and / or the cell measurement value (e.g., serving cell RSRP measurement value) has not decreased by more than a decrease threshold (e.g., since the last TA validation).

[0280] The wireless device may receive one or more DL RSs from a cell configured with multi-beam operation. The wireless device may determine a cell measurement value by a function (e.g., average, linear average) of at least one DL RS measurement value (e.g., RSRP, RSRQ, RSSI, and / or the like) of the one or more DL RSs. The wireless device may select the at least one DL RS from among the one or more DL RSs using the measured power value of the one or more DL RSs. For example, the wireless device may select N DL RSs (N≧1) from among the one or more DL RSs to determine a cell measurement value. For example, the measurement value of the N DL RSs may be higher than a second threshold. For example, the measurement value of the N DL RSs may be the highest N value among the measurements of the one or more DL RSs. For example, as the wireless device moves,

[0281] FIG. 25 is an example of DL RS selection for cell measurement values ​​according to one aspect of an embodiment of the present disclosure. A wireless device may receive one or more DL RSs from a cell. In FIG. 25, the wireless device receives four DL RSs. The wireless device may select at least one DL RS from the one or more DL RSs to determine a cell measurement value. For example, at time T1, the wireless device may select DL RS3 and DL RS4 based on the measurement values ​​of the one or more DL RSs. For example, the measurement values ​​of DL RS3 and DL RS4 are the highest among the one or more DL RSs. The wireless device may move toward an area covered by DL RS1 and / or DL ​​RS2. At time T2, the wireless device may select DL RS1 and DL RS2 based on the measurement values ​​of the one or more DL RSs. For example, the measurement values ​​of DL RS1 and DL RS2 are the highest among the one or more DL RSs.

[0282] The broadcast and / or multicast messages (e.g., system information) may not include (e.g., do not indicate) configuration parameters dedicated to wireless devices. The broadcast and / or multicast messages (e.g., system information) may configure (e.g., provide) scheduling information for radio resources shared with multiple wireless devices. The broadcast and / or multicast messages (e.g., system information) may not configure (e.g., provide) scheduling information for radio resources dedicated to wireless devices (e.g., it may not be appropriate to do so).

[0283] The RRC reconfiguration message may be a message that the wireless device receives in an RRC_CONNECTED state. The RRC reconfiguration message may include configuration parameters of the SDT dedicated to the wireless device. The RRC reconfiguration message may not indicate a release of the connection from the network (e.g., a base station). For example, the RRC reconfiguration message may not indicate a transition from an RRC_CONNECTED state to a Non-RRC_CONNECTED state. The RRC reconfiguration message may not trigger an (RRC) connection release procedure. The wireless device may receive an RRC release message, for example, after receiving an RRC reconfiguration message. Radio channel conditions between the wireless device and the network (e.g., a base station) may change after receiving the RRC reconfiguration message and / or before receiving the RRC release message. For example, if the RRC reconfiguration message includes configuration parameters of the SDT, it may be too early for the network (e.g., a base station) to determine the configuration parameters of the SDT. Incorrect values ​​of the configuration parameters may increase the number of retransmissions and battery power of the wireless device. Incorrect values ​​of the configuration parameters may reduce reliability and / or increase latency of communications between the wireless device and the base station.

[0284] For example, it may be beneficial for the wireless device if a particular type of message indicates (and / or includes) configuration parameters of an SDT (e.g., one or more radio resources used in the Non-RRC_CONNECTED state) dedicated to the wireless device and / or a connection release from the network (e.g., a base station). For example, the particular type of message may be an RRC release message. The RRC message may indicate, for example, a transition from an RRC_CONNECTED state to a Non-RRC_CONNECTED state after or in response to receiving an RRC message. The wireless device may retrieve the configuration parameters of the RRC release message, for example, when the wireless device starts the SDT. The wireless device may use the configuration parameters of the SDT for transmission and / or reception of cells in the Non-RRC_CONNECTED state. The RRC release message may be one of the most recent messages (e.g., dedicated to the wireless device) that the wireless device receives before starting the SDT. For example, the configuration parameters of the RRC release message may be determined (by the base station) based on recent radio channel conditions between the wireless device and the base station. For example, configuration parameters determined based on recent wireless channel conditions may reduce battery power of the wireless device and / or improve reliability and latency of communications between the wireless device and a base station.

[0285] In an exemplary implementation, the RRC release message may include configuration parameters for the SDT. The configuration parameters may include an index (or identifier) ​​of a first synchronization signal block (SSB) of one or more SSBs, a time and frequency resource configuration of uplink resources used for the SDT in the Non-RRC_CONNECTED state, and / or a mapping indication (or association) between the first SSB and the uplink resources. In the claimed invention, even if the RRC release message configures the uplink resources of the first SSB, the wireless device verifies the resources by measuring the one or more SSBs. In an exemplary embodiment, the RRC release message includes configuration parameters for the one or more SSBs, the uplink resources for the SDT in the Non-RRC_CONNECTED state. The wireless device may receive an RRC release message including configuration parameters for the SDT, for example, in a Radio Resource Control (RRC) connected state, where the configuration parameters include an identifier of a first SSB of a cell, for use in the Non-RRC_CONNECTED state, and / or one or more resource parameters of the uplink resources corresponding to the first SSB. In one example, configuration in the RRC_CONNECTED state using an RRC reconfiguration message to grant uplink resources configured in the RRC_CONNECTED state may not be valid and / or may not be usable by the wireless device in the Non-RRC_CONNECTED state. Using an RRC release message instead of other messages (e.g., an RRC reconfiguration message, a broadcast message, a multicast message, and / or system information) provides additional benefits because the RRC release message is one of the most recent messages received (by the wireless device and from the base station) before starting the SDT in the Non-RRC_CONNECTED state. The base station may send configuration parameters of the first SSB and uplink resources in the RRC release message to configure the resources for the SDT and transition the wireless device to the Non-RRC_CONNECTED state.

[0286] In an exemplary implementation, the configuration parameters may include a first threshold for validating transmission over an uplink source used for SDT in the Non-RRC_CONNECTED state. The base station may transmit an RRC release message including the first threshold. The wireless device may determine that the uplink resource is valid for use in the Non-RRC_CONNECTED state, the determination being based on beam measurements of the first SSB being equal to or greater than the first threshold. For example, the base station can configure the first threshold based on the latest channel measurements and / or specific wireless device capabilities and parameters (e.g., using the RRC release message). Exemplary embodiments provide reduced signaling overhead and / or improved uplink transmission for wireless devices in the Non-RRC_CONNECTED state. The RRC release message is a unicast message dedicated to the wireless device (e.g., a unicast dedicated UE-specific message), and the base station can configure these parameters for the wireless device based on radio-specific parameters (e.g., channel conditions, capabilities, configuration, and / or the like).

[0287] In an example implementation, the RRC release message may include a second threshold for validating transmission over uplink resources used for SDT in the Non-RRC_CONNECTED state. In one embodiment, the configuration of the second threshold for validating transmission over uplink resources further improves the SDT of small data packets during the Non-RRC_CONNECTED state. The wireless device may determine that it is valid to use uplink resources for transmission of the SDT in the Non-RRC_CONNECTED state, the determination being based on beam measurements of the first SSB being greater than or equal to the first threshold and less than the second threshold. The configuration of the second threshold provides for the implementation of a more accurate validation mechanism for uplink resources (e.g., for transmission over the uplink resources) during the Non-RRC_CONNECTED state. For example, the configuration of the first and second thresholds may enable the wireless device to validate the uplink resources to reduce interference to the base station and / or other wireless devices. For example, the wireless device may disable transmission over uplink resources when the wireless device is very close to the base station and may generate additional interference to other nodes (when the received measurement value of the SSB exceeds a second threshold).

[0288] In existing techniques, a problem may occur in the Non-RRC_CONNECTED state when a cell measurement value of a cell is high (e.g., higher than a first threshold) while a beam measurement value associated with transmission and / or reception over one or more radio resources of the cell is low (e.g., below a second threshold). The wireless device may receive a wireless device-specific message (e.g., an RRC message, a MAC CE, a DCI, and / or any combination thereof) that (re)configures (changes and / or updates) a DL RS (e.g., TCI and / or spatial relationship information of a beam configuration). The wireless device-specific message may indicate that a DL RS may be associated with transmission and / or reception over one or more radio resources of the cell. The wireless device may determine that a measured power value of a DL RS of the cell is low (e.g., below a predefined and / or semi-statically configured threshold). For example, a measured power value of a DL RS may be dropped while a cell measurement value (and / or a change in the cell measurement value since the last validation) may be within a valid range (e.g., between an increase threshold and a decrease threshold). This may occur, for example, when one or more DL RSs of a cell that the wireless device selects to determine cell measurements may change while the wireless device holds (e.g., maintains) the DL RS as a beam configuration (e.g., TCI and / or spatial relationship information) of one or more radio resources until the wireless device receives a wireless device-specific message that allows it to (re)configure (change and / or update) the DL RS (e.g., TCI and / or spatial relationship information of the beam configuration). In this case, the wireless device may determine, based on the cell measurements, that transmission and / or reception via one or more radio resources of the cell is effective, for example, when a measured power value of the DL RS is low. For example, in existing technologies, the wireless device may not use a measured power value of the DL RS to determine the effectiveness of transmission and / or reception via one or more radio resources. A low power value of the DL RS results in a high rate of decoding failures of transmission and / or reception via one or more radio resources.For example, as the failure rate increases, delays and / or battery consumption of a wireless device increase due to retransmissions caused by decoding failures.

[0289] It may be necessary to enhance the verification of transmission and / or reception in the Non-RRC_CONNECTED state. In an example embodiment, the wireless device may determine whether to transmit and / or receive in the Non-RRC_CONNECTED state based on beam measurement values ​​of DL RSs (e.g., received from the cell). The wireless device may determine the measured power values ​​of DL RSs (e.g., RSRP, RSRQ, and / or RSSI) as the beam measurement values ​​of DL RSs. The enhanced verification based on beam measurements may be referred to as beam verification of the cell. For example, for beam verification, the wireless device may determine the validity of the transmission and / or reception using beam measurement values ​​of one or more DL RSs associated with the transmission and / or reception. For example, the wireless device may determine that the transmission and / or reception of the cell is invalid in the Non-RRC_CONNECTED state if, for example, the beam measurement value of at least one DL RS of the one or more DL RSs is out of range. In an example embodiment, the wireless device may not transmit and / or receive (e.g., skip, do not initiate, and / or skip initiation), for example, if the wireless device determines that the transmission and / or reception is invalid. The range may be configured and / or defined by one or more thresholds. For example, a message (e.g., an RRC message, a MAC CE, and / or a DCI) that the wireless device receives from the base station includes one or more thresholds.

[0290] In an example embodiment, measurements at different levels, e.g., cell level measurements and / or beam level measurements, may be used to verify transmission and / or reception in the Non-RRC_CONNECTED state. For example, the wireless device determines whether to transmit and / or receive via one or more radio resources based on a cell measurement value of the cell (e.g., a serving cell RSRP value) and / or a beam measurement value of at least one DL RS associated with the one or more radio resources (e.g., a measured RSRP value). The verification performed by the wireless device based on the cell measurement value may be a TA verification (e.g., as shown in FIG. 21A, FIG. 21B, and FIG. 22). For example, the TA verification based on the cell measurement value may determine whether to use a TA value for transmission in the Non-RRC_CONNECTED state. The verification performed by the wireless device based on the beam measurement value of the at least one DL RS may determine, for example, whether to expect a transmission and / or reception failure when the wireless device uses at least one DL RS (e.g., to determine an antenna port and / or a precoder) for transmission and / or reception. For example, the wireless device determines whether to (e.g., skip and / or start) or not transmit and / or receive over one or more radio resources using one or more DL RSs associated with the one or more radio resources based on the results of the beam verification. Beam verification in example embodiments can improve the spectral efficiency and / or reduce power consumption of the wireless device by reducing unnecessary transmission and / or reception over beams (e.g., DL RSs) that experience high losses in the channel between the wireless device and the base station.

[0291] FIG. 26 is an example of beam verification according to an aspect of an embodiment of the present disclosure. A wireless device may receive one or more DL RSs from a cell. In FIG. 26, a wireless device receives four DL RSs. The wireless device may receive an indication from a base station indicating that DL RS4 is associated with transmission and / or reception of a cell in a Non-RRC_CONNECTED state. For example, the wireless device may determine an antenna port and / or a precoder (e.g., a spatial domain filter) to be used for transmission and / or reception based on the indicated DL RS4. The wireless device may select at least one DL RS from among the one or more DL RSs and determine cell measurement values. For example, at time T1, the wireless device may determine cell measurement values ​​based on measured power values ​​of DL RS3 and DL RS4. The wireless device may perform transmission and / or reception based on a determination that the cell measurement value measured at time T1 is within a first valid range (e.g., a range defined based on the increase threshold and / or decrease threshold in the example of FIG. 21A and / or FIG. 21B) and / or the beam measurement value of DL RS4 is valid (e.g., within a second valid range) to be used for transmission and / or reception. At time T2, the wireless device may determine the cell measurement value based on the measured power values ​​of DL RS1 and DL RS2, while determining the beam measurement value based on the measured power value of DL RS4. The wireless device may determine that the cell measurement value measured at time T2 is within the first valid range. The wireless device may determine that the beam measurement value of DL RS4 at time T2 is invalid (e.g., outside the second valid range) to be used for transmission and / or reception. The wireless device may not perform transmission and / or reception (e.g., skip, skip starting, and / or not start) after or in response to the beam measurement value being determined to be invalid.

[0292] The wireless device may perform beam verification based on cell measurement values. The wireless device may determine cell measurement values ​​for verifying transmission and / or reception in the Non-RRC_CONNECTED state using one or more DL RSs among the multiple DL RSs of the cell. For example, the wireless device may use the cell measurement values ​​for TA verification. The wireless device may select one or more DL RSs based on measured power values ​​of the multiple DL RSs. For example, the measured power value of the one or more DL RSs may be the maximum value of N (e.g., N≧1) among the measured power values ​​of the multiple DL RSs. If the one or more DL RSs includes at least one DL RS, the wireless device may determine that one or more radio resources of the cell are valid to be used for transmission and / or reception in the Non-RRC_CONNECTED state. The wireless device may continue to perform one or more verifications based on one or more conditions, such as whether the TAT is operating (e.g., FIG. 20) and / or whether the cell measurement values ​​(and / or changes in the measurement values) are within range (e.g., FIG. 21A and FIG. 21B). If the one or more DL RSs does not include at least one DL RS, the wireless device may disable (e.g., decide not to use) the use of one or more radio resources for transmission and / or reception in Non-RRC_CONNECTED.

[0293] In Figure 26, at time T1, the wireless device may determine that one or more radio resources of the cell are valid for use in transmission and / or reception in the Non-RRC_CONNECTED state, e.g., after or in response to a cell measurement value determined based on DL RS4. For example, at time T2 in Figure 26, the wireless device may determine that one or more radio resources of the cell are invalid for use in transmission and / or reception in the Non-RRC_CONNECTED state, e.g., after or in response to a cell measurement value determined not based on DL RS4.

[0294] After or in response to beam verification indicating that one or more radio resources of the cell are invalid for use in transmission and / or reception, the wireless device may not perform (e.g., skip, do not start, skip initiation) transmission and / or reception. After or in response to beam verification indicating that one or more radio resources of the cell are invalid for use in transmission and / or reception, the wireless device may deactivate one or more radio resources and / or suspend configuration parameters and / or grants of one or more radio resources. After or in response to beam verification indicating that one or more radio resources of the cell are invalid ...

Claims

1. 1. A method comprising: receiving, by a wireless device (106) in a radio resource control (RRC) connected state, an RRC release message including configuration parameters for use in transmissions during an RRC inactive state, the configuration parameters comprising: an identifier of a first synchronization signal block (SSB) of a plurality of SSBs of a cell; one or more resource parameters for uplink resources corresponding to the first SSB for use in the transmission during the RRC inactive state; a first threshold for validating the transmission over the uplink resource; and transitioning, by the wireless device, from the RRC connected state to the RRC inactive state based on the RRC release message; determining, by the wireless device, that the uplink resources are available for use in the transmission during the RRC inactive state, the determination being based on a beam measurement value of the first SSB being equal to or greater than a reference signal received power (RSRP) measurement threshold based on the first threshold; transmitting a transport block over the uplink resources based on the determination; A method comprising:

2. 2. The method of claim 1, wherein the determination that the uplink resources are valid is further based on the beam measurement value of the first SSB being less than a second RSRP measurement value based on a second threshold.

3. The method of claim 2 , wherein the RRC release message indicates the second threshold value.

4. The method according to any one of claims 1 to 3, wherein the beam measurement value is a reference signal received power (RSRP) of the first SSB.

5. The method of any one of claims 1 to 4, wherein the transmitting comprises transmitting the transport block with the wireless device in the RRC inactive state.

6. A wireless device including one or more processors and a memory for storing instructions, which, when executed by the one or more processors, cause the wireless device to perform a method according to any one of claims 1 to 5.

7. A non-transitory computer-readable medium, the non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 1 to 5.

8. 1. A method comprising: transmitting, by a base station (160), to a wireless device (106) in a radio resource control (RRC) connected state, an RRC release message including configuration parameters for use by the wireless device in transmitting during an RRC inactive state, the configuration parameters comprising: an identifier of a first synchronization signal block (SSB) of a plurality of SSBs of a cell; one or more resource parameters for uplink resources corresponding to the first SSB for use in the transmission during the RRC inactive state; a first threshold for validating the transmission over the uplink resource; and transitioning, for the wireless device, from the RRC connected state to the RRC inactive state based on the RRC release message; receiving a transport block via the uplink resource based on a determination by the wireless device that the uplink resource is available for use in the transmission during the RRC inactive state, the determination being based on a beam measurement value of the first SSB being equal to or greater than a reference signal received power (RSRP) measurement threshold based on the first threshold; A method comprising:

9. 9. The method of claim 8, wherein the determination that the uplink resources are valid is further based on the beam measurement value of the first SSB being less than a second RSRP measurement value based on a second threshold.

10. The method of claim 9 , wherein the RRC release message indicates the second threshold.

11. A method according to any one of claims 8 to 10, wherein the beam measurement value is a reference signal received power (RSRP) of the first SSB.

12. The method of any one of claims 8 to 11, wherein the receiving comprises receiving the transport block with the wireless device in the RRC inactive state.

13. A base station, the base station including one or more processors and a memory for storing instructions, the instructions, when executed by the one or more processors, causing the base station to perform a method according to any one of claims 8 to 12.

14. A non-transitory computer-readable medium, the non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method according to any one of claims 8 to 12.

15. A system comprising:

1. A base station (160), the base station including one or more first processors and a first memory storing first instructions, the first instructions, when executed by the one or more first processors, transmitting to a wireless device (106) in a radio resource control (RRC) connected state an RRC release message including configuration parameters for use by the wireless device in transmissions during an RRC inactive state, the configuration parameters comprising: an identifier of a first synchronization signal block (SSB) of a plurality of SSBs of a cell; one or more resource parameters for uplink resources corresponding to the first SSB for use in the transmission during the RRC inactive state; a first threshold for validating the transmission over the uplink resource; and transitioning, for the wireless device, from the RRC connected state to the RRC inactive state based on the RRC release message; receiving, via the uplink resources, a transport block based on a determination that the uplink resources are available for use in the transmission during the RRC inactive state; a base station, 11. The wireless device, the wireless device including one or more second processors and a second memory storing second instructions, the second instructions, when executed by the one or more second processors, receiving an RRC release message in the RRC connected state; transitioning from the RRC connected state to the RRC inactive state based on the RRC release message; determining that the uplink resources are available for use in the transmission during the RRC inactive state, the determination being based on a beam measurement value of the first SSB being greater than or equal to a reference signal received power (RSRP) measurement threshold based on the first threshold; transmitting the transport block over the uplink resources based on the determination; a wireless device; Including, the system.

Citation Information

Patent Citations

  • Mobile communication system, terminal device, base station device, communication method and computer program

    JP2020027955A