Method and system for accessing cell information for management

Abstract

The base station distributed unit sends, to a base station central unit, an indication that one or more cells are associated with a first closed access group. The base station distributed unit receives, from the base station central unit, a context configuration message comprising cell configuration parameters for the one or more cells for a wireless device.

Description

[0001] Divisional Application

[0002] This application is a divisional application of application number 2020800402291, filed March 27, 2020, entitled “Method and System for Access Management Cell Information.”

[0003] Cross Reference to Related Applications

[0004] This application claims the benefit of U.S. Provisional Application No. 62 / 824,823, filed March 27, 2019, which is hereby incorporated by reference in its entirety. BRIEF DESCRIPTION OF DRAWINGS

[0005] Examples of several of the various embodiments of the present disclosure are described herein with reference to the accompanying drawings.

[0006] Figure 1 is a diagram of an example RAN architecture in aspects of embodiments according to the present disclosure;

[0007] Figure 2A is a diagram of an example user plane protocol stack in aspects of embodiments according to the present disclosure;

[0008] Figure 2B is a diagram of an example control plane protocol stack in aspects of embodiments according to the present disclosure;

[0009] Figure 3 is a diagram of an example wireless device and two base stations in aspects of embodiments according to the present disclosure;

[0010] Figure 4A , Figure 4B , Figure 4C and Figure 4D are example diagrams of uplink and downlink signal transmissions in aspects of embodiments according to the present disclosure;

[0011] Figure 5A is a diagram of an example uplink channel mapping and example uplink physical signals in aspects of embodiments according to the present disclosure;

[0012] Figure 5B is a diagram of an example downlink channel mapping and example downlink physical signals in aspects of embodiments according to the present disclosure;

[0013] Figure 6 is a diagram depicting example transmission or reception times of a carrier in aspects of embodiments according to the present disclosure;

[0014] Figure 7A and Figure 7B are diagrams depicting example sets of OFDM subcarriers in aspects of embodiments according to the present disclosure;

[0015] Figure 8 is a diagram depicting example OFDM radio resources according to aspects of an embodiment of the present disclosure;

[0016] Figure 9A is a diagram depicting example CSI-RS and / or SS block transmissions in a multi-beam system;

[0017] Figure 9B is a diagram depicting an example downlink beam management procedure according to aspects of an embodiment of the present disclosure;

[0018] Figure 10 is an example diagram of a configured BWP in accordance with aspects of an embodiment of the present disclosure;

[0019] Figure 11A and Figure 11B is a diagram of example multi-connectivity according to aspects of an embodiment of the present disclosure;

[0020] Figure 12 is a diagram of an example random access procedure according to aspects of an embodiment of the present disclosure;

[0021] Figure 13 is a structure of an example MAC entity according to aspects of an embodiment of the present disclosure;

[0022] Figure 14 is a diagram of an exemplary RAN architecture according to an aspect of an embodiment of the present disclosure;

[0023] Figure 15 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0024] Figure 16 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0025] Figure 17 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0026] Figure 18 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0027] Figure 19 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0028] Figure 20 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0029] Figure 21 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0030] Figure 22 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0031] Figure 23 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0032] Figure 24 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0033] Figure 25 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0034] Figure 26 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0035] Figure 27 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0036] Figure 28 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0037] Figure 29 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0038] Figure 30 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0039] Figure 31 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0040] Figure 32 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0041] Figure 33 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0042] Figure 34 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0043] Figure 35 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0044] Figure 36 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0045] Figure 37 is an exemplary diagram of one aspect of an embodiment of the present disclosure;

[0046] Figure 38 is an exemplary diagram of one aspect of an embodiment of the present disclosure. DETAILED DESCRIPTION

[0047] Exemplary embodiments of the present disclosure enable operation of a wireless communication system. Embodiments of the technology disclosed herein can be employed in the technical field of multi-carrier communication systems. More specifically, embodiments of the technology disclosed herein can relate to radio access networks in multi-carrier communication systems.

[0048] The following acronyms are used throughout the present disclosure:

[0049] 3GPP Third Generation Partnership Project

[0050] 5GC 5G Core Network

[0051] ACK Acknowledgement

[0052] AMF Access and Mobility Management Function

[0053] ARQ Automatic Repeat reQuest

[0054] AS Access Stratum

[0055] ASIC Application Specific Integrated Circuit

[0056] BA Bandwidth Adaptation

[0057] BCCH Broadcast Control Channel

[0058] BCH Broadcast Channel

[0059] BPSK Binary Phase Shift Keying

[0060] BWP Bandwidth Part

[0061] CA Carrier Aggregation

[0062] CC Component Carrier

[0063] CCCH Common Control Channel

[0064] CDMA Code Division Multiple Access

[0065] CN Core Network

[0066] CP Cyclic Prefix

[0067] CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplexing

[0068] C-RNTI Cell-Radio Network Temporary Identifier

[0069] CS Configured Scheduling

[0070] CSI Channel State Information

[0071] CSI-RS Channel State Information-Reference Signal

[0072] CQI channel quality indicator

[0073] CSS common search space

[0074] CU center unit

[0075] DC dual connectivity

[0076] DCCH dedicated control channel

[0077] DCI downlink control information

[0078] DL downlink

[0079] DL-SCH downlink shared channel

[0080] DM-RS demodulation reference signal

[0081] DRB data radio bearer

[0082] DRX discontinuous reception

[0083] DTCH dedicated traffic channel

[0084] DU distribution unit

[0085] EPC evolved packet core

[0086] E-UTRA evolved UMTS terrestrial radio access

[0087] E-UTRAN evolved universal terrestrial radio access network

[0088] FDD frequency division duplex

[0089] FPGA field programmable gate array

[0090] F1-C F1 -control plane

[0091] F1-U F1 -user plane

[0092] gNB next generation node B

[0093] HARQ hybrid automatic repeat request

[0094] HDL hardware description language

[0095] IE information element

[0096] IP internet protocol

[0097] LCID logical channel identifier

[0098] LTE long term evolution

[0099] MAC medium access control

[0100] MCG master cell group

[0101] MCS modulation and coding scheme

[0102] MeNB master evolved NodeB

[0103] MIB master information block

[0104] MME mobility management entity

[0105] MN master node

[0106] NACK negative acknowledgement

[0107] NAS non-access stratum

[0108] NG CP next generation control plane

[0109] NGC next generation core

[0110] NG-C NG-control plane

[0111] ng-eNB next generation evolved NodeB

[0112] NG-U NG-user plane

[0113] NR new radio

[0114] NR MAC new radio MAC

[0115] NR PDCP new radio PDCP

[0116] NR PHY new radio physical

[0117] NR RLC new radio RLC

[0118] NR RRC new radio RRC

[0119] NSSAI network slice selection assistance information

[0120] O&M operation and maintenance

[0121] OFDM orthogonal frequency division multiplexing

[0122] PBCH physical broadcast channel

[0123] PCC primary component carrier

[0124] PCCH paging control channel

[0125] PCell primary cell

[0126] PCH paging channel

[0127] PDCCH physical downlink control channel

[0128] PDCP packet data convergence protocol

[0129] PDSCH physical downlink shared channel

[0130] PDU protocol data unit

[0131] PHICH physical HARQ indicator channel

[0132] PHY physical

[0133] PLMN public land mobile network

[0134] PMI precoding matrix indicator

[0135] PRACH physical random access channel

[0136] PRB physical resource block

[0137] PSCell primary secondary cell

[0138] PSS primary synchronization signal

[0139] pTAG primary timing advance group

[0140] PT-RS phase tracking reference signal

[0141] PUCCH physical uplink control channel

[0142] PUSCH physical uplink shared channel

[0143] QAM quadrature amplitude modulation

[0144] QFI quality of service indicator

[0145] QoS quality of service

[0146] QPSK quadrature phase shift keying

[0147] RA random access

[0148] RACH random access channel

[0149] RAN radio access network

[0150] RAT radio access technology

[0151] RA-RNTI random access-radio network temporary identifier

[0152] RB resource block

[0153] RBG resource block group

[0154] RI rank indicator

[0155] RLC radio link control

[0156] RRC radio resource control

[0157] RS reference signal

[0158] RSRP reference signal received power

[0159] SCC secondary component carrier

[0160] SCell secondary cell

[0161] SCG secondary cell group

[0162] SC-FDMA single carrier-frequency division multiple access

[0163] SDAP service data adaptation protocol

[0164] SDU service data unit

[0165] SeNB secondary evolved node B

[0166] SFN system frame number

[0167] S-GW serving gateway

[0168] SI system information

[0169] SIB system information block

[0170] SMF session management function

[0171] SN secondary node

[0172] SpCell special cell

[0173] SRB signaling radio bearer

[0174] SRS sounding reference signal

[0175] SS synchronization signal

[0176] SSS secondary synchronization signal

[0177] sTAG secondary timing advance group

[0178] TA timing advance

[0179] TAG timing advance group

[0180] TAI tracking area identifier

[0181] TAT time alignment timer

[0182] TB transport block

[0183] TC-RNTI temporary cell-radio network temporary identifier

[0184] TDD time division duplex

[0185] TDMA time division multiple access

[0186] TTI transmission time interval

[0187] UCI uplink control information

[0188] UE user equipment

[0189] UL uplink

[0190] UL-SCH uplink shared channel

[0191] UPF user plane function

[0192] UPGW user plane gateway

[0193] VHDL VHSIC hardware description language

[0194] Xn-C Xn-control plane

[0195] Xn-U Xn-user plane

[0196] The exemplary embodiments of the present disclosure can be implemented using various physical layer modulation and transmission mechanisms. Exemplary transmission mechanisms can include, but are not limited to, code division multiple access (CDMA), orthogonal frequency division multiple access (OFDMA), time division multiple access (TDMA), wavelet techniques, etc. Hybrid transmitter mechanisms, such as TDMA / CDMA and OFDM / CDMA, can also be employed. Various modulation schemes can be applied to the transmission of signals in the physical layer. Examples of modulation schemes include, but are not limited to, phase, amplitude, code, combinations of these, etc. Exemplary radio transmission methods can implement quadrature amplitude modulation (QAM) using binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), 16-QAM, 64-QAM, 256-QAM, etc. Physical radio transmission can be enhanced by dynamically or semi-dynamically changing the modulation and coding schemes according to transmission requirements and radio conditions.

[0197] Figure 1is an example radio access network (RAN) architecture in accordance with aspects of embodiments of the present disclosure. As shown in this example, a RAN node can be a next generation Node B (gNB) (e.g., 120A, 120B) that provides New Radio (NR) user plane and control plane protocol terminations towards a first wireless device (e.g., 110A). In an example, the RAN node can be a next generation evolved Node B (ng-eNB) (e.g., 120C, 120D) that provides Evolved UMTS Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations towards a second wireless device (e.g., 110B). The first wireless device can communicate with the gNB over a Uu interface. The second wireless device can communicate with the ng-eNB over a Uu interface.

[0198] The gNB or ng-eNB can host, for example, radio resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of access and mobility management function (AMF) at user equipment (UE) attachment, routing of user plane and control plane data, connection setup and release, scheduling and transmission of paging messages (originated from the AMF), scheduling and transmission of system broadcast information (originated from the AMF or operation and maintenance (O&M)), measurement and measurement reporting configuration, transport level packet marking in uplink, session management, network slice support, quality of service (QoS) flow management and mapping to data radio bearers, support for UEs in RRC INACTIVE state, distribution function for non-access stratum (NAS) messages, RAN sharing, and dual connectivity or tight interworking between NR and E-UTRA.

[0199] In an example, one or more gNBs and / or one or more ng-eNBs can be interconnected through an Xn interface. The gNB or ng-eNB can be connected to a 5G core network (5GC) through an NG interface. In an example, the 5GC can include one or more AMF / user plane function (UPF) functions (e.g., 130A or 130B). The gNB or ng-eNB can be connected to a UPF through an NG user plane (NG-U) interface. The NG-U interface can provide delivery (e.g., non-guaranteed delivery) of user plane protocol data units (PDUs) between the RAN node and the UPF. The gNB or ng-eNB can be connected to an AMF through an NG control plane (NG-C) interface. The NG-C interface can provide functions such as NG interface management, UE context management, UE mobility management, transfer of NAS messages, paging, PDU session management, configuration transfer, or warning message transmission, among others.

[0200] In an example, a UPF can host, e.g., user plane portion of anchor point for intra- / inter-Radio Access Technology (RAT) mobility (when applicable), external PDU session point of interconnect to Data Network, packet routing and forwarding, packet inspection and policy rule enforcement, traffic usage reporting, uplink classifier to support routing of traffic flows to a Data Network, branching point to support multi-homed PDU session, QoS handling for user plane (e.g., packet filtering, gating), uplink (UL) / downlink (DL) rate enforcement, uplink traffic verification (e.g., Service Data Flow (SDF) to QoS flow mapping), downlink packet buffering, and / or downlink data notification triggering, etc. functions.

[0201] In an example, an AMF can host, e.g., NAS signaling termination, NAS signaling security, access stratum (AS) security control, inter-core network (CN) node signaling for mobility between 3rd Generation Partnership Project (3GPP) access networks, idle mode UE reachability (e.g., control and execution of paging retransmission), registration area management, support of network slice and / or session management function (SMF) selection, etc. functions.

[0202] Figure 2Ais an example user plane protocol stack, where service data adaptation protocol (SDAP) (e.g., 211 and 221), packet data convergence protocol (PDCP) (e.g., 212 and 222), radio link control (RLC) (e.g., 213 and 223), and medium access control (MAC) (e.g., 214 and 224) sub-layers, and physical (PHY) (e.g., 215 and 225) layer can be terminated in a wireless device (e.g., 110) and a gNB (e.g., 120) on the network side. In an example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In an example, services and functions of the MAC sub-layer can include mapping between logical channels and transport channels, multiplexing / de-multiplexing of MAC service data units (SDUs) belonging to one or different logical channels into / from transport blocks (TBs) delivered to / from the PHY layer, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ) (e.g., one HARQ entity per carrier in case of carrier aggregation (CA)), priority handling between UEs through dynamic scheduling, priority handling between logical channels of one UE through logical channel prioritization and / or padding. The MAC entity can support one or multiple numerologies and / or transmission timings. In an example, mapping restrictions in logical channel prioritization can control which numerology and / or transmission timing a logical channel can use. In an example, the RLC sub-layer can support transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM) transmission modes. RLC configuration can be per logical channel, independent of numerology and / or transmission time interval (TTI) duration. In an example, automatic repeat request (ARQ) can operate on any numerology and / or TTI duration that a logical channel is configured for. In an example, services and functions of the PDCP layer for the user plane can include sequence numbering, header compression and decompression, transfer of user data, reordering and duplicate detection, PDCP PDU routing (e.g., in case of split bearers), retransmission of PDCP SDUs, ciphering, deciphering, and integrity protection, PDCP SDU discard, PDCP re-establishment and data recovery for RLC AM, and / or duplication of PDCP PDUs. In an example, services and functions of the SDAP can include mapping between QoS flows and data radio bearers. In an example, services and functions of the SDAP can include mapping of quality of service indicators (QFIs) in DL and UL packets. In an example, a protocol entity of the SDAP can be configured for individual PDU sessions.

[0203] Figure 2Bis an example control plane protocol stack, where PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244) sublayers and PHY (e.g., 236 and 245) layer can be terminated and perform the above-mentioned services and functions in the wireless device (e.g., 110) and gNB (e.g., 120) on the network side. In an example, RRC (e.g., 232 and 241) can be terminated in the wireless device and gNB on the network side. In an example, the services and functions of RRC can include: broadcast of system information related to AS and NAS, paging initiated by 5GC or RAN, establishment, maintenance and release of an RRC connection between the UE and RAN, security functions including key management, establishment, configuration, maintenance and release of Signaling Radio Bearers (SRBs) and Data Radio Bearers (DRBs), mobility functions, QoS management functions, UE measurement reporting and control of reporting, detection of and recovery from radio link failure, and / or transfer of NAS messages to / from NAS. In an example, NAS control protocol (e.g., 231, 251) can be terminated in the wireless device and AMF (e.g., 130) on the network side, and can perform, for example, the following functions: authentication, mobility management between the UE and AMF for 3GPP access and non-3GPP access, and session management between the UE and SMF for 3GPP access and non-3GPP access.

[0204] In an example, a base station may configure multiple logical channels for a wireless device. A logical channel in the multiple logical channels may correspond to a radio bearer, and the radio bearer may be associated with a QoS requirement. In an example, the base station may configure the logical channel to be mapped to one or more TTIs / parameter sets in a plurality of TTIs / parameter sets. The wireless device may receive downlink control information (DCI) indicating an uplink grant via a physical downlink control channel (PDCCH). In an example, the uplink grant may be for a first TTI / parameter set and may indicate uplink resources for transmission of a transport block. The base station may configure each of the multiple logical channels with one or more parameters to be used by a logical channel prioritization procedure at a MAC layer of the wireless device. The one or more parameters may include a priority, a prioritized bit rate, etc. A logical channel in the multiple logical channels may correspond to one or more buffers including data associated with the logical channel. The logical channel prioritization procedure may allocate uplink resources to one or more first logical channels and / or one or more MAC control elements (CEs) in the multiple logical channels. The one or more first logical channels may be mapped to a first TTI / parameter set. The MAC layer at the wireless device may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) in a MAC PDU (e.g., a transport block). In an example, the MAC PDU may include a MAC header including multiple MAC subheaders. A MAC subheader in the multiple MAC subheaders may correspond to a MAC CE or MAC SDU (logical channel) in one or more MAC CEs and / or one or more MAC SDUs. In an example, a MAC CE or a logical channel may be configured with a logical channel identifier (LCID). In an example, the LCID for the logical channel or MAC CE may be fixed / preconfigured. In an example, the LCID for the logical channel or MAC CE may be configured for the wireless device by the base station. The MAC subheader corresponding to the MAC CE or MAC SDU may include the LCID associated with the MAC CE or MAC SDU.

[0205] In an example, a base station can activate and / or deactivate and / or affect one or more procedures (e.g., set a value of one or more parameters of one or more procedures or start and / or stop one or more timers of one or more procedures) at a wireless device by employing one or more MAC commands. The one or more MAC commands can comprise one or more MAC control elements. In an example, the one or more procedures can comprise activation and / or deactivation of PDCP packet duplication for one or more radio bearers. The base station can transmit a MAC CE comprising one or more fields, a value of the field(s) indicating activation and / or deactivation of PDCP duplication for one or more radio bearers. In an example, the one or more procedures can comprise channel state information (CSI) transmission on one or more cells. The base station can transmit one or more MAC CEs on one or more cells indicating activation and / or deactivation of CSI transmission. In an example, the one or more procedures can comprise activation or deactivation of one or more secondary cells. In an example, the base station can transmit a MAC CE indicating activation or deactivation of one or more secondary cells. In an example, the base station can transmit one or more MAC CEs indicating starting and / or stopping one or more discontinuous reception (DRX) timers at the wireless device. In an example, the base station can transmit one or more MAC CEs indicating one or more timing advance group (TAG) one or more timing advance values.

[0206] Figure 3 is a block diagram of a base station (base station 1, 120A and base station 2, 120B) and a wireless device 110. The wireless device can be referred to as a UE. The base station can be referred to as a NB, eNB, gNB, and / or ng-eNB. In an example, the wireless device and / or the base station can function as a relay node. Base station 1, 120A can comprise at least one communication interface 320A (e.g., a wireless modem, an antenna, a wired modem, etc.), at least one processor 321A, and at least one set of program code instructions 323A stored in a non-transitory memory 322A and executable by the at least one processor 321A. Base station 2, 120B can comprise at least one communication interface 320B, at least one processor 321B, and at least one set of program code instructions 323B stored in a non-transitory memory 322B and executable by the at least one processor 321B.

[0207] A base station can comprise a number of sectors, e.g., 1, 2, 3, 4, or 6 sectors. A base station can comprise a number of cells, e.g., ranging from 1 to 50 cells or more. Cells can be classified, e.g., as a primary cell or a secondary cell. One serving cell can provide NAS (non-access stratum) mobility information (e.g., tracking area identifier (TAI)) at radio resource control (RRC) connection setup / reestablishment / handover. One serving cell can provide security input at RRC connection reestablishment / handover. This cell can be referred to as the primary cell (PCell). In the downlink, the carrier corresponding to the PCell can be the DL primary component carrier (PCC), while in the uplink, the carrier can be the UL PCC. Depending on the wireless device capability, a secondary cell (SCell) can be configured to form a serving cell set together with the PCell. In the downlink, the carrier corresponding to the SCell can be a downlink secondary component carrier (DL SCC), while in the uplink, the carrier can be an uplink secondary component carrier (UL SCC). A SCell can or can not have an uplink carrier.

[0208] A physical cell ID and a cell index can be assigned for a cell comprising a downlink carrier and an optional uplink carrier. A carrier (downlink or uplink) can belong to one cell. A cell ID or a cell index can also identify a downlink carrier or an uplink carrier of a cell (depending on the context in which it is used). In this disclosure, a cell ID can equally refer to a carrier ID, and a cell index can be referred to as a carrier index. In embodiments, a physical cell ID or a cell index can be assigned to a cell. A cell ID can be determined using a synchronization signal transmitted on a downlink carrier. A cell index can be determined using an RRC message. For example, when this disclosure refers to a first physical cell ID of a first downlink carrier, this disclosure can mean that the first physical cell ID is for a cell comprising the first downlink carrier. The same concept can apply to, e.g., carrier activation. When this disclosure indicates that a first carrier is activated, this specification can equally mean that a cell comprising the first carrier is activated.

[0209] A base station can transmit one or more messages (e.g., RRC messages) comprising a plurality of configuration parameters of one or more cells to a wireless device. The one or more cells can comprise at least one primary cell and at least one secondary cell. In an example, the RRC messages can be broadcasted or unicast to the wireless device. In an example, the configuration parameters can comprise common parameters and dedicated parameters.

[0210] Services and / or functions of the RRC sublayer can include at least one of the following: broadcasting of system information related to AS and NAS; paging initiated by 5GC and / or NG-RAN; establishment, maintenance and / or release of an RRC connection between the wireless device and the NG-RAN, which can include at least one of addition, modification, and release of carrier aggregation; or addition, modification, and / or release of dual connectivity within NR or between E-UTRA and NR. Services and / or functions of the RRC sublayer can additionally include at least one of security functions with: key management; establishment, configuration, maintenance and / or release of signaling radio bearers (SRBs) and / or data radio bearers (DRBs); mobility functions, which can include at least one of handover (e.g., intra-NR mobility or inter-RAT mobility) and context transfer; or wireless device cell selection and reselection and control of cell selection and reselection. Services and / or functions of the RRC sublayer can additionally include at least one of the following: QoS management functions; wireless device measurement configuration / reporting; detection of radio link failure and / or recovery from radio link failure; or transfer of NAS messages from the wireless device to a core network entity (e.g., AMF, mobility management entity (MME)) / from the core network entity to the wireless device.

[0211] The RRC sublayer can support an RRC_Idle state, an RRC_Inactive state, and / or an RRC_Connected state of the wireless device. In the RRC_Idle state, the wireless device can perform at least one of the following: Public Land Mobile Network (PLMN) selection; receiving broadcasted system information; cell selection / reselection; monitoring / receiving paging for mobile terminated data initiated by the 5GC; paging for mobile terminated data area managed by the 5GC; or DRX for CN paging configured via NAS. In the RRC_Inactive state, the wireless device can perform at least one of the following: receiving broadcasted system information; cell selection / reselection; monitoring / receiving RAN / CN paging initiated by the NG-RAN / 5GC; RAN-based notification area (RNA) managed by the NG-RAN; or DRX for RAN / CN paging configured by the NG-RAN / NAS. In the RRC_Idle state of the wireless device, the base station (e.g., the NG-RAN) can maintain a 5GC-NG-RAN connection (both C / U-planes) for the wireless device; and / or store a UE AS context for the wireless device. In the RRC_Connected state of the wireless device, the base station (e.g., the NG-RAN) can perform at least one of the following: establish a 5GC-NG-RAN connection (both C / U-planes) for the wireless device; store a UE AS context for the wireless device; transmit / receive unicast data to / from the wireless device; or network-controlled mobility based on measurement results received from the wireless device. In the RRC_Connected state of the wireless device, the NG-RAN can know a cell to which the wireless device belongs.

[0212] System information (SI) can be divided into minimum SI and other SI. The minimum SI can be broadcasted periodically. The minimum SI can include basic information required for initial access and information for acquiring any other SI that is broadcasted periodically or provided on demand, i.e., scheduling information. The other SI can be broadcasted, or provided in a dedicated manner, or triggered by the network, or upon request of the wireless device. The minimum SI can be transmitted via two different downlink channels using different messages (e.g., MasterInformationBlock and SystemInformationBlockType1). Another SI can be transmitted via SystemInformationBlockType2. For a wireless device in an RRC_Connected state, dedicated RRC signaling can be used for the request and delivery of the other SI. For a wireless device in an RRC_Idle state and / or an RRC_Inactive state, the request can trigger a random access procedure.

[0213] A wireless device can report radio access capability information, which can be static. The base station can request the wireless device to report capabilities based on the frequency band information. When permitted by the network, the wireless device can send a temporary capability restriction request to signal the limited availability of certain capabilities to the base station (e.g., due to hardware sharing, interference, or overheating). The base station can confirm or deny the request. Temporary capability restrictions can be transparent to the 5GC (e.g., only static capabilities can be stored in the 5GC).

[0214] When CA is configured, the wireless device may establish an RRC connection with the network. During RRC connection establishment / reestablishment / handover procedures, a serving cell may provide NAS mobility information and, during RRC connection reestablishment / handover, a serving cell may provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, an SCell may be configured to form a serving cell set together with the PCell. The configured serving cell set for the wireless device may include one PCell and one or more SCells.

[0215] The reconfiguration, addition, and removal of SCells can be performed by RRC. During intra-NR handovers, RRC can also add, remove, or reconfigure SCells for use with the target PCell. When adding a new SCell, dedicated RRC signaling can be used to send all system information required by the SCell. This means that when in connected mode, wireless devices may not need to obtain broadcast system information directly from the SCell.

[0216] The purpose of the RRC connection reconfiguration procedure may be to modify the RRC connection (e.g., to establish, modify and / or release RBs, perform handover, set up, modify and / or release measurements, add, modify and / or release SCells and cell groups). As part of the RRC connection reconfiguration procedure, NAS-specific information may be passed from the network to the wireless device. The RRCConnectionReconfiguration message may be a command to modify the RRC connection. It may convey information for measurement configuration, mobility control, radio resource configuration (e.g., RBs, MAC primary configuration, and physical channel configuration), including any associated dedicated NAS information and security configuration. If the received RRC connection reconfiguration message includes sCellToReleaseList, the wireless device may perform an SCell release. If the received RRC connection reconfiguration message includes sCellToAddModList, the wireless device may perform an SCell addition or modification.

[0217] An RRC connection setup (or reestablishment, resume) procedure can be to setup (or reestablish, resume) an RRC connection. The RRC connection setup procedure can include SRB1 setup. The RRC connection setup procedure can be used to transfer initial NAS dedicated information / message from the wireless device to the E-UTRAN. The RRCConnectionReestablishment message can be used to reestablish SRB1.

[0218] A measurement reporting procedure can be to transfer measurement results from the wireless device to the NG-RAN. The wireless device can initiate the measurement reporting procedure after successful security activation. The measurement results can be transmitted using a measurement reporting message.

[0219] The wireless device 110 can include at least one communication interface 310 (e.g., a wireless modem, antenna, etc.), at least one processor 314, and at least one set of program code instructions 316 stored in non-transitory memory 315 and executable by the at least one processor 314. The wireless device 110 can also include at least one of the following: at least one speaker / microphone 311, at least one keypad 312, at least one display / touchpad 313, at least one power supply 317, at least one global positioning satellite (GPS) chipset 318, and other peripherals 319.

[0220] The processor 314 of the wireless device 110, the processor 321A of the base station 1 120A, and / or the processor 321B of the base station 2 120B can include at least one of the following: a general purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application specific integrated circuit (ASIC), a field

[0221] The processor 314 of the wireless device 110 can be connected to the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313. The processor 314 can receive user input data from and / or supply user output data to the speaker / microphone 311, the keypad 312, and / or the display / touchpad 313. The processor 314 in the wireless device 110 can receive power from the power supply 317, and / or can be configured to distribute the power to the other components in the wireless device 110. The power supply 317 can comprise at least one of a dry battery, a solar cell, a fuel cell, and / or the like. The processor 314 can be connected to the GPS chipset 318. The GPS chipset 318 can be configured to provide geographic location information of the wireless device 110.

[0222] The processor 314 of the wireless device 110 can also be connected to other peripherals 319, which can include one or more software and / or hardware modules that provide additional features and / or functionality. For example, the peripherals 319 can include at least one of an accelerometer, a satellite transceiver, a digital camera, a Universal Serial Bus (USB) port, a hands-free headset, a frequency modulated (FM) radio unit, a media player, an Internet browser, and / or the like.

[0223] The communication interface 320A of the base station 1, 120A and / or the communication interface 320B of the base station 2, 120B can be configured to communicate with the communication interface 310 of the wireless device 110 via the wireless link 330A and / or the wireless link 330B, respectively. In an example, the communication interface 320A of the base station 1, 120A can communicate with the communication interface 320B of the base station 2 and other RAN and core network nodes.

[0224] The wireless link 330A and / or the wireless link 330B can comprise at least one of a bi-directional link and / or a directional link. The communication interface 310 of the wireless device 110 can be configured to communicate with the communication interface 320A of the base station 1, 120A and / or with the communication interface 320B of the base station 2, 120B. The base station 1, 120A and the wireless device 110 and / or the base station 2, 120B and the wireless device 110 can be configured to transmit and receive transport blocks via the wireless link 330A and / or via the wireless link 330B, respectively. The wireless link 330A and / or the wireless link 330B can employ at least one frequency carrier. According to some different aspects of embodiments, one or more transceivers can be employed. A transceiver can be a device that includes both a transmitter and a receiver. Transceivers can be used in, for example, wireless devices, base stations, relay nodes, and / or the like. In Figure 4A 、 Figure 4B 、 Figure 4C 、 Figure 4D 、 Figure 6 、 Figure 7A , Figure 7B , Figure 8 Exemplary embodiments of radio technologies implemented in the communication interfaces 310, 320A, 320B and the wireless links 330A, 330B are shown in the related text.

[0225] In examples, other nodes in the wireless network (e.g., AMF, UPF, SMF, etc.) can include one or more communication interfaces, one or more processors, and memory storing instructions.

[0226] A node (e.g., wireless device, base station, AMF, SMF, UPF, server, switch, antenna, etc.) can include one or more processors and memory storing instructions that, when executed by the one or more processors, cause the node to perform certain processes and / or functions. Exemplary embodiments can implement operations for single-carrier and / or multi-carrier communications. Other exemplary embodiments can include a non-transitory, tangible computer-readable medium comprising instructions executable by one or more processors to cause operations for single-carrier and / or multi-carrier communications. Still other exemplary embodiments can include an article of manufacture that comprises a non-transitory, tangible computer-readable machine accessible medium having instructions encoded thereon for enabling programmable hardware to cause a node to implement operations for single-carrier and / or multi-carrier communications. The node can include a processor, memory, interface, etc.

[0227] An interface can include at least one of a hardware interface, a firmware interface, a software interface, and / or combinations thereof. A hardware interface can include a connector, a wire, an electronic device such as a driver, an amplifier, etc. A software interface can include code stored in a memory device to implement one or more protocols, protocol layers, communication devices, device drivers, combinations thereof, etc. A firmware interface can include a combination of embedded hardware and code stored in and / or communicating with a memory device to implement connections, electronic device operations, one or more protocols, protocol layers, communication drivers, device drivers, hardware operations, combinations thereof, etc.

[0228] Figure 4A , Figure 4B , Figure 4C and Figure 4D are example diagrams of uplink and downlink signal transmissions in accordance with aspects of embodiments of the present disclosure. Figure 4AAn example uplink transmitter for at least one physical channel is shown. A baseband signal representing a physical uplink shared channel can perform one or more functions. The one or more functions can include at least one of: scrambling; modulating scrambled 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 of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single-carrier frequency-division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission can be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission can be generated by Figure 4A mapping of complex-valued modulation symbols onto one or several transmission layers; transform precoding to generate complex-valued symbols; precoding of complex-valued symbols; mapping of precoded complex-valued symbols to resource elements; generating a complex-valued time-domain single-carrier frequency-division multiple access (SC-FDMA) or CP-OFDM signal for an antenna port; and / or the like. In an example, when transform precoding is enabled, a SC-FDMA signal for uplink transmission can be generated. In an example, when transform precoding is not enabled, a CP-OFDM signal for uplink transmission can be generated by

[0229] An example structure of modulation and upconversion of a carrier frequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-valued physical random access channel (PRACH) baseband signal is shown in Figure 4B Filtering can be employed prior to transmission.

[0230] Figure 4C An example structure for downlink transmission is shown in. A baseband signal representing a downlink physical 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 a physical channel; modulating scrambled bits to generate complex-valued modulation symbols; mapping complex-valued modulation symbols onto one or several transmission layers; precoding of complex-valued modulation symbols on layers for transmission on an antenna port; mapping of complex-valued modulation symbols for an antenna port to resource elements; generating a complex-valued time-domain OFDM signal for an antenna port; and / or the like. These functions are shown as examples, and other mechanisms can be implemented in various embodiments.

[0231] In an example, a gNB can transmit a first symbol and a second symbol on an antenna port to a wireless device. The wireless device can infer a channel (e.g., a fading gain, a multipath delay, and / or the like) for communicating a second symbol on an antenna port from a channel for communicating a first symbol on the antenna port. In an example, a first antenna port and a second antenna port can be quasi co-located if one or more large-scale properties of a channel for communicating a first symbol on a first antenna port can be inferred from a channel for communicating a second symbol on a second antenna port. The one or more large-scale properties can include at least one of: a delay spread; a Doppler spread; a Doppler shift; an average gain; an average delay; and / or a spatial receive (Rx) parameter.

[0232] Example modulation and upconversion of the carrier frequency of a complex-valued OFDM baseband signal for an antenna port is shown in Figure 4D Filtering can be employed prior to transmission.

[0233] Figure 5A is a diagram of example uplink channel mappings and example uplink physical signals. Figure 5B is a diagram of example downlink channel mappings and downlink physical signals. In an example, the physical layer can provide one or more information transfer services to the MAC and / or one or more higher layers. By way of example, the physical layer can provide the one or more information transfer services to the MAC via one or more transport channels. An information transfer service can indicate the manner and characteristics of transferring data over a radio interface.

[0234] In an example embodiment, a radio network can include one or more downlink and / or uplink transport channels. By way of example, Figure 5A is a diagram showing example uplink transport channels including an uplink shared channel (UL-SCH) 501 and a random access channel (RACH) 502. Figure 5B is a diagram showing example downlink transport channels including a downlink shared channel (DL-SCH) 511, a paging channel (PCH) 512, and a broadcast channel (BCH) 513. Transport channels can be mapped to one or more corresponding physical channels. By way of example, the UL-SCH 501 can be mapped to a physical uplink shared channel (PUSCH) 503. The RACH 502 can be mapped to a PRACH 505. The DL-SCH 511 and the PCH 512 can be mapped to a physical downlink shared channel (PDSCH) 514. The BCH 513 can be mapped to a physical broadcast channel (PBCH) 516.

[0235] There can be one or more physical channels without a corresponding transport channel. The one or more physical channels can be used for uplink control information (UCI) 509 and / or downlink control information (DCI) 517. For example, a physical uplink control channel (PUCCH) 504 can carry UCI 509 from a UE to a base station. For example, a physical downlink control channel (PDCCH) 515 can carry DCI 517 from a base station to a UE. NR can support UCI 509 multiplexing in PUSCH 503 when UCI 509 and PUSCH 503 transmissions can at least partially coincide in a slot. UCI 509 can include at least one of CSI, an acknowledgement (ACK) / negative acknowledgement (NACK), and / or a scheduling request. DCI 517 on PDCCH 515 can indicate at least one of the following: one or more downlink assignments and / or one or more uplink scheduling grants.

[0236] In uplink, a UE can transmit one or more reference signals (RSs) to a base station. For example, the one or more RSs can be at least one of a demodulation-RS (DM-RS) 506, a phase tracking-RS (PT-RS) 507, and / or a sounding RS (SRS) 508. In downlink, a base station can transmit (e.g., unicast, multicast, and / or broadcast) one or more RSs to a UE. For example, the one or more RSs can be at least one of a primary synchronization signal (PSS) / secondary synchronization signal (SSS) 521, a CSI-RS 522, a DM-RS 523, and / or a PT-RS 524.

[0237] In an example, the UE can transmit one or more uplink DM-RS 506 to the base station for channel estimation, e.g., for coherent demodulation of one or more uplink physical channels, e.g., PUSCH 503 and / or PUCCH 504. For example, the UE can transmit at least one uplink DM-RS 506 with the PUSCH 503 and / or PUCCH 504 to the base station, where the at least one uplink DM-RS 506 can span a same frequency range as the corresponding physical channel. In an example, the base station can configure the UE with one or more uplink DM-RS configurations. The at least one DM-RS configuration can support a front-loaded DM-RS pattern. The front-loaded DM-RS can be mapped on one or more OFDM symbols, e.g., 1 or 2 adjacent OFDM symbols. One or more additional uplink DM-RS can be configured to be transmitted at one or more symbols of the PUSCH and / or PUCCH. The base station can semi- statically configure the UE with a maximum number of front-loaded DM-RS symbols for the PUSCH and / or PUCCH. For example, the UE can schedule for single-symbol DM-RS and / or double-symbol DM-RS based on the maximum number of front-loaded DM-RS symbols, where the base station can configure the UE with one or more additional uplink DM-RS for the PUSCH and / or PUCCH. A new radio network can support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, where the DM-RS locations, the DM-RS pattern, and / or the scrambling sequence can be the same or different.

[0238] In an example, the presence of uplink PT-RS 507 can be dependent on RRC configuration. For example, the presence of uplink PT-RS can be UE- specifically configured. For example, the presence and / or pattern of uplink PT-RS 507 in a scheduled resource can be UE- specifically configured through a combination of RRC signaling and / or association with one or more parameters (e.g., modulation and coding scheme (MCS)) that can be indicated by DCI for other purposes. When configured, the dynamic presence of uplink PT-RS 507 can be associated with one or more DCI parameters including at least MCS. A radio network can support multiple uplink PT-RS densities defined in time domain / frequency domain. When present, a frequency domain density can be associated with at least one configuration of a scheduled bandwidth. The UE can take a same precoding for DMRS ports and PT-RS ports. The number of PT-RS ports can be fewer than the number of DM-RS ports in a scheduled resource. For example, the uplink PT-RS 507 can be confined in a scheduled time / frequency duration of the UE.

[0239] In an example, a UE can transmit SRS 508 to a base station for channel state estimation to support uplink channel dependent scheduling and / or link adaptation. For example, the SRS 508 transmitted by the UE can allow the base station to estimate the uplink channel state at one or more different frequencies. The base station scheduler can employ the uplink channel state to assign one or more resource blocks of high quality for uplink PUSCH transmissions from the UE. The base station can semi- statically configure the UE with one or more SRS resource sets. For an SRS resource set, the base station can configure the UE with one or more SRS resources. SRS resource set applicability can be configured by a higher layer (e.g., RRC) parameter. For example, when the higher layer parameter indicates beam management, SRS resources in each of the one or more SRS resource sets can be transmitted at a time. The UE can transmit one or more SRS resources in different SRS resource sets simultaneously. A new radio network can support aperiodic, periodic, and / or semi-persistent SRS transmissions. The UE can transmit SRS resources based on one or more trigger types, which can include higher layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format can be employed for the UE to select at least one of the one or more configured SRS resource sets). SRS trigger type 0 can refer to SRS triggered based on higher layer signaling. SRS trigger type 1 can refer to SRS triggered based on one or more DCI formats. In an example, when PUSCH 503 and SRS 508 are transmitted in the same slot, the UE can be configured to transmit SRS 508 after the transmission of PUSCH 503 and corresponding uplink DM-RS 506.

[0240] In an example, a base station can semi- statically configure a UE with one or more SRS configuration parameters indicating at least one of: SRS resource configuration identifier, number of SRS ports, time domain behavior of SRS resource configuration (e.g., indication of periodic, semi-persistent, or aperiodic SRS), slot (mini-slot and / or subframe) level periodicity and / or offset for periodic and / or aperiodic SRS resources, number of OFDM symbols in SRS resource, starting OFDM symbol of SRS resource, SRS bandwidth, frequency hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0241] In an example, in the time domain, an SS / PBCH block can include one or more OFDM symbols within the SS / PBCH block (e.g., 4 OFDM symbols numbered in increasing order from 0 to 3). The SS / PBCH block can include a PSS / SSS 521 and a PBCH 516. In an example, in the frequency domain, an SS / PBCH block can include one or more contiguous subcarriers within the SS / PBCH block (e.g., 240 contiguous subcarriers, subcarriers numbered in increasing order from 0 to 239). For example, the PSS / SSS 521 can occupy 1 OFDM symbol and 127 subcarriers. For example, the PBCH 516 can span 3 OFDM symbols and 240 subcarriers. A UE can assume that one or more SS / PBCH blocks transmitted with the same block index can be quasi co-located, e.g., with respect to Doppler spread, Doppler shift, average gain, average delay, and spatial Rx parameters. A UE can not assume quasi co-location of other SS / PBCH block transmissions. The periodicity of SS / PBCH blocks can be configured by the radio network (e.g., through RRC signaling), and one or more time locations at which an SS / PBCH block can be transmitted can be determined by a subcarrier spacing. In an example, a UE can assume a band-specific subcarrier spacing for SS / PBCH blocks unless the radio network has configured the UE to employ a different subcarrier spacing.

[0242] In an example, downlink CSI-RS 522 can be employed for UEs to obtain channel state information. A radio network can support periodic, aperiodic, and / or semi-persistent transmission of downlink CSI-RS 522. For example, a base station can utilize periodic transmission of downlink CSI-RS 522 to semi-statistically configure and / or reconfigure a UE. A configured CSI-RS resource can be activated and / or deactivated. For semi-persistent transmission, activation and / or deactivation of a CSI-RS resource can be dynamically triggered. In an example, a CSI-RS configuration can include one or more parameters indicating at least a number of antenna ports. For example, a base station can configure a UE with 32 ports. A base station can semi-statistically configure a UE with one or more CSI-RS resource sets. One or more CSI-RS resources can be allocated to one or more UEs from one or more CSI-RS resource sets. For example, a base station can semi-statistically configure one or more parameters indicating a CSI RS resource mapping, e.g., a time domain location of one or more CSI-RS resources, a bandwidth of a CSI-RS resource, and / or a periodicity. In an example, a UE can be configured to employ a same OFDM symbol for a downlink CSI-RS 522 and a control resource set (CORESET) when the downlink CSI-RS 522 and the CORESET are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are outside PRBs configured for the CORESET. In an example, a UE can be configured to employ a same OFDM symbol for a downlink CSI-RS 522 and a SSB / PBCH when the downlink CSI-RS 522 and the SSB / PBCH are spatially quasi co-located and resource elements associated with the downlink CSI-RS 522 are outside PRBs configured for the SSB / PBCH.

[0243] In an example, the UE can transmit one or more downlink DM-RS 523 to the base station for channel estimation, e.g., for coherent demodulation of one or more downlink physical channels (e.g., PDSCH 514). By way of example, the radio network can support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration can support a front-loaded DM-RS pattern. The front-loaded DM-RS can be mapped on one or more OFDM symbols (e.g., 1 or 2 adjacent OFDM symbols). The base station can semi- statically configure the UE with a maximum number of front-loaded DM-RS symbols for PDSCH 514. By way of example, the DM-RS configuration can support one or more DM-RS ports. By way of example, for single user-MIMO, the DM-RS configuration can support at least 8 orthogonal downlink DM-RS ports. By way of example, for multi user-MIMO, the DM-RS configuration can support 12 orthogonal downlink DM-RS ports. The radio network can support, e.g., at least for CP-OFDM, a common DM-RS structure for DL and UL, where the DM-RS locations, the DM-RS patterns, and / or the scrambling sequences can be the same or different.

[0244] In an example, the presence or absence of downlink PT-RS 524 can be dependent on RRC configuration. By way of example, the presence of downlink PT-RS 524 can be UE- specifically configured. By way of example, the presence and / or pattern of downlink PT-RS 524 in a scheduled resource can be UE specifically configured through a combination of RRC signaling and / or association with one or more parameters (e.g., MCS) that can be indicated by DCI for other purposes. When configured, the dynamic presence of downlink PT-RS 524 can be associated with one or more DCI parameters including at least MCS. The radio network can support multiple PT-RS densities defined in time domain / frequency domain. When present, the frequency domain density can be associated with at least one configuration of the scheduled bandwidth. The UE can take the same precoding for the DMRS ports and the PT-RS ports. The number of PT-RS ports can be fewer than the number of DM-RS ports in the scheduled resource. By way of example, downlink PT-RS 524 can be confined in the scheduled time / frequency duration of the UE.

[0245] Figure 6 is a diagram depicting example transmit and receive times for carriers in accordance with an aspect of embodiments of the present disclosure. A multi-carrier OFDM communication system can include one or more carriers, e.g., ranging from 1 to 32 carriers in case of carrier aggregation, or ranging from 1 to 64 carriers in case of dual connectivity. Different radio frame structures can be supported (e.g., for FDD and for TDD duplexing mechanisms). Figure 6 Example frame timing is shown. Downlink and uplink transmissions can be organized into radio frames 601. In this example, the radio frame duration is 10 milliseconds. In this example, the 10 millisecond radio frame 601 can be divided into ten equally sized subframes 602 with a 1 millisecond duration. One or more subframes can include one or more slots (e.g., slots 603 and 605), depending on the subcarrier spacing and / or CP length. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz subcarrier spacing can include one, two, four, eight, sixteen, and thirty-two slots, respectively. In Figure 6 In the example, a subframe can be divided into two equally sized slots 603 with a 0.5 millisecond duration. For example, at 10 millisecond intervals, 10 subframes can be used for downlink transmissions and 10 subframes can be used for uplink transmissions. Uplink and downlink transmissions can be split in the frequency domain. One or more slots can include a number of OFDM symbols 604. The number of OFDM symbols 604 in a slot 605 can depend on the cyclic prefix length. For example, for the same subcarrier spacing up to 480 kHz with normal CP, a slot can be 14 OFDM symbols. For the same subcarrier spacing of 60 kHz with extended CP, a slot can be 12 OFDM symbols. A slot can contain downlink, uplink, or downlink and uplink portions, among others.

[0246] Figure 7Ais a diagram depicting an example set of OFDM subcarriers in accordance with aspects of embodiments of the present disclosure. In an example, a gNB can communicate with a wireless device using a carrier having an example channel bandwidth 700. One or more arrows in the diagram can depict subcarriers in a multi-carrier OFDM system. The OFDM system can use, for example, OFDM technology, SC-FDMA technology, or the like. In an example, arrow 701 shows a subcarrier transmitting an information symbol. In an example, a subcarrier spacing 702 between two consecutive subcarriers in the carrier can be any one of 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz, or the like. In an example, different subcarrier spacings can correspond to different transmission numerologies. In an example, a transmission numerology can include at least: a numerology index; a value of a subcarrier spacing; a type of cyclic prefix (CP). In an example, a gNB can transmit to / receive from a UE on a number of subcarriers 703 in the carrier. In an example, due to guard bands 704 and 705, a bandwidth occupied by the number of subcarriers 703 (a transmission bandwidth) can be less than the channel bandwidth 700 of the carrier. In an example, the guard bands 704 and 705 can be used to reduce interference to and from one or more neighboring carriers. The number of subcarriers in the carrier (the transmission bandwidth) can depend on the channel bandwidth of the carrier and the subcarrier spacing. For example, for a carrier having a 20 MHz channel bandwidth and a 15 KHz subcarrier spacing, the transmission bandwidth can be a number of 1024 subcarriers.

[0247] In an example, when configured with CA, a gNB and a wireless device can communicate with multiple CCs. In an example, if CA is supported, different component carriers can have different bandwidths and / or subcarrier spacings. In an example, a gNB can transmit a first type of service to a UE on a first component carrier. The gNB can transmit a second type of service to the UE on a second component carrier. Different types of services can have different service requirements (e.g., data rate, latency, reliability), which can be suitable for transmission via different component carriers having different subcarrier spacings and / or bandwidths. Figure 7B An example embodiment is shown. A first component carrier can include a first number of subcarriers 706 having a first subcarrier spacing 709. A second component carrier can include a second number of subcarriers 707 having a second subcarrier spacing 710. A third component carrier can include a third number of subcarriers 708 having a third subcarrier spacing 711. Carriers in a multi-carrier OFDM communication system can be contiguous carriers, non-contiguous carriers, or a combination of contiguous and non-contiguous carriers.

[0248] Figure 88 is a diagram illustrating OFDM radio resources according to aspects of an embodiment of the present disclosure. In an example, a carrier may have a transmission bandwidth 801. In an example, a resource grid may be structured in the frequency domain 802 and the time domain 803. In an example, the resource grid may include a first number of OFDM symbols and a second number of resource blocks in a subframe, starting from a common resource block for transmitting a parameter set and a carrier indicated by higher layer signaling (e.g., RRC signaling). In an example, in the resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element 805. In an example, depending on the parameter set associated with the carrier, the subframe may include a first number of OFDM symbols 807. For example, when the subcarrier spacing of the parameter set of the carrier is 15 kHz, the subframe may have 14 OFDM symbols for the carrier. When the subcarrier spacing of the parameter set is 30 kHz, the subframe may have 28 OFDM symbols. When the subcarrier spacing of the parameter set is 60 kHz, the subframe may have 56 OFDM symbols, and so on. In an example, the second number of resource blocks included in the resource grid of the carrier may depend on the bandwidth and the numerology of the carrier.

[0249] like Figure 8 As shown, resource block 806 may include 12 subcarriers. In an example, multiple resource blocks may be grouped into resource block groups (RBGs) 804. In an example, the size of the RBGs may depend on at least one of: an RRC message indicating the RBG size configuration; the size of the carrier bandwidth; or the size of a bandwidth portion of the carrier. In an example, the carrier may include multiple bandwidth portions. A first bandwidth portion of the carrier may have a different frequency location and / or bandwidth than a second bandwidth portion of the carrier.

[0250] In an example, a gNB may transmit downlink control information including downlink or uplink resource block assignments to a wireless device. The base station may transmit or receive data packets (e.g., transport blocks) to or from the wireless device that are scheduled and transmitted over one or more resource blocks and one or more time slots based on the downlink control information and / or parameters in one or more RRC messages. In an example, a start symbol of a first time slot relative to the one or more time slots may be indicated to the wireless device. In an example, the gNB may transmit or receive data packets to or from the wireless device that are scheduled over one or more RBGs and one or more time slots.

[0251] In an example, a gNB can transmit downlink control information including a downlink assignment to a wireless device via one or more PDCCHs. The downlink assignment can include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to a DL-SCH. In an example, the resource allocation can include parameters of a resource block allocation; and / or a time slot allocation. In an example, a gNB can dynamically allocate resources to a wireless device via a cell-radio network temporary identifier (C-RNTI) on one or more PDCCHs. The wireless device can monitor the one or more PDCCHs to find possible allocations when its downlink reception is enabled. When the one or more PDCCHs are successfully detected, the wireless device can receive one or more downlink data packets on one or more PDSCHs scheduled by the one or more PDCCHs.

[0252] In an example, a gNB can allocate configured scheduling (CS) resources for downlink transmissions to a wireless device. The gNB can transmit one or more RRC messages indicating a periodicity of CS grants. The gNB can transmit DCI via a PDCCH addressed to a configured scheduling-RNTI (CS-RNTI) activating the CS resources. The DCI can include parameters indicating that a downlink grant is a CS grant. The CS grant can be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivation.

[0253] In an example, a gNB can transmit downlink control information including an uplink grant to a wireless device via one or more PDCCHs. The uplink grant can include parameters indicating at least a modulation and coding format; a resource allocation; and / or HARQ information related to a UL-SCH. In an example, the resource allocation can include parameters of a resource block allocation; and / or a time slot allocation. In an example, a gNB can dynamically allocate resources to a wireless device via a C-RNTI on one or more PDCCHs. The wireless device can monitor the one or more PDCCHs to find possible resource allocations. When the one or more PDCCHs are successfully detected, the wireless device can transmit one or more uplink data packets via one or more PUSCHs scheduled by the one or more PDCCHs.

[0254] In an example, a gNB can allocate CS resources for uplink data transmissions to a wireless device. The gNB can transmit one or more RRC messages indicating a periodicity of CS grants. The gNB can transmit DCI via a PDCCH addressed to a CS-RNTI activating the CS resources. The DCI can include parameters indicating that an uplink grant is a CS grant. The CS grant can be implicitly reused according to the periodicity defined by the one or more RRC messages until deactivation.

[0255] In an example, a base station can transmit DCI / control signaling via a PDCCH. The DCI can take a certain format among a plurality of formats. The DCI can include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ related parameters, MCS), a request for CSI (e.g., aperiodic CQI reporting), a request for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmission / reception timing, HARQ feedback timing, etc.), and / or the like. In an example, the DCI can indicate an uplink grant including transmission parameters for one or more transport blocks. In an example, the DCI can indicate a downlink assignment indicating parameters for receiving one or more transport blocks. In an example, a base station can use the DCI to initiate a contention-free random access at a wireless device. In an example, a base station can transmit a DCI including a slot format indicator (SFI) informing a slot format. In an example, a base station can transmit a DCI including a pre-emption indication informing one or more PRBs and / or one or more OFDM symbols where a UE can assume no transmission intended for the UE. In an example, a base station can transmit a DCI for group power control for PUCCH or PUSCH or SRS. In an example, the DCI can correspond to an RNTI. In an example, a wireless device can obtain an RNTI (e.g., C-RNTI) in response to completing an initial access. In an example, a base station can configure an RNTI (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI) for a wireless device. In an example, a wireless device can calculate an RNTI (e.g., the wireless device can calculate a RA-RNTI based on a resource used to transmit a preamble). In an example, an RNTI can have a preconfigured value (e.g., P-RNTI or SI-RNTI). In an example, a wireless device can monitor a group common search space, which can be used by a base station to transmit a DCI intended for a group of UEs. In an example, a group common DCI can correspond to an RNTI commonly configured for a group of UEs. In an example, a wireless device can monitor a UE specific search space. In an example, a UE specific DCI can correspond to an RNTI configured for a wireless device.

[0256] An NR system can support single-beam operation and / or multi-beam operation. In multi-beam operation, a base station can perform downlink beam sweeping to provide coverage for common control channels and / or downlink SS blocks, which can include at least PSS, SSS, and / or PBCH. A wireless device can use one or more RSs to measure the quality of a beam pair link. One or more SS blocks, or one or more CSI-RS resources associated with a CSI-RS resource index (CRI), or one or more DM-RSs of a PBCH can be used as RSs for measuring the quality of a beam pair link. The quality of a beam pair link can be defined as a reference signal received power (RSRP) value, or a reference signal received quality (RSRQ) value, and / or a CSI value measured on the RS resource. The base station can indicate whether the RS resource used to measure the quality of a beam pair link is quasi co-located (QCLed) with a DM-RS of a control channel. A RS resource and a DM-RS of a control channel can be referred to as QCLed when channel properties from a transmission to a wireless device on the RS and from a transmission to the wireless device on the control channel are similar or the same under a configured criteria. In multi-beam operation, a wireless device can perform uplink beam sweeping to access a cell.

[0257] In an example, a wireless device can be configured to monitor PDCCH on one or more beam pair links simultaneously depending on the capability of the wireless device. This can increase robustness with respect to beam pair link blockage. A base station can transmit one or more messages to configure the wireless device to monitor PDCCH on one or more beam pair links in different PDCCH OFDM symbols. For example, the base station can transmit higher layer signaling (e.g., RRC signaling) or a MAC CE that includes parameters regarding Rx beam settings of the wireless device for monitoring PDCCH on one or more beam pair links. The base station can transmit one or more DL RS antenna ports (e.g., cell-specific CSI-RS, or wireless device-specific CSI-RS, or SS blocks, or PBCH with or without DM-RS) and an indication of a spatial QCL assumption between the one or more DL RS antenna ports and one or more DL RS antenna ports used for demodulating a DL control channel. Signaling for beam indication for PDCCH can be MAC CE signaling, or RRC signaling, or DCI signaling, or a specification-transparent and / or implicit method, and a combination of these signaling methods.

[0258] For reception of unicast DL data channel, the base station can indicate spatial QCL parameters between one or more DL RS antenna ports and one or more DM-RS antenna ports of the DL data channel. The base station can transmit a DCI (e.g., downlink grant) including information indicating one or more RS antenna ports. The information can indicate one or more RS antenna ports that can be QCLed with one or more DM-RS antenna ports. Different sets of one or more DM-RS antenna ports for the DL data channel can be indicated as QCLed with different sets of one or more RS antenna ports.

[0259] Figure 9A is an example of beam sweeping in a DL channel. In RRC_INACTIVE state or RRC_IDLE state, the wireless device can assume that SS blocks form SS burst 940 and SS burst set 950. The SS burst set 950 can have a given periodicity. For example, in multi-beam operation, the base station 120 can transmit SS blocks in multiple beams together forming SS burst 940. One or more SS blocks can be transmitted on one beam. If multiple SS bursts 940 are transmitted together with multiple beams, the SS bursts together can form SS burst set 950.

[0260] The wireless device can additionally use CSI-RS to estimate beam quality of a link between the wireless device and the base station in multi-beam operation. A beam can be associated with a CSI-RS. For example, the wireless device can report a beam index based on RSRP measurement on the CSI-RS as indicated in CRI for downlink beam selection and associated with a RSRP value of the beam. The CSI-RS can be transmitted on a CSI-RS resource including at least one of one or more antenna ports, one or more time or frequency radio resources. The CSI-RS resource can be configured by common RRC signaling in a cell-specific manner or by dedicated RRC signaling and / or L1 / L2 signaling in a wireless device-specific manner. A plurality of wireless devices covered by a cell can measure a cell-specific CSI-RS resource. A dedicated subset of wireless devices covered by a cell can measure a wireless device-specific CSI-RS resource.

[0261] The CSI-RS resource can be transmitted periodically or using aperiodic transmission or using multi-shot or semi-persistent transmission. For example, in periodic transmission in Figure 9A In periodic transmission, the base station 120 can periodically transmit a configured CSI-RS resource 940 using a configured periodicity in time domain. In aperiodic transmission, the configured CSI-RS resource can be transmitted in a dedicated time slot. In multi-shot or semi-persistent transmission, the configured CSI-RS resource can be transmitted within a configured period. The beam for CSI-RS transmission can have a different beam width than the beam for SS block transmission.

[0262] Figure 9B are examples of beam management procedures in an example new radio network. Base stations 120 and / or wireless devices 110 can perform downlink L1 / L2 beam management procedures. One or more of the following downlink L1 / L2 beam management procedures can be performed within one or more wireless devices 110 and one or more base stations 120. In an example, a P-1 procedure 910 can be used to enable a wireless device 110 to measure one or more transmit (Tx) beams associated with a base station 120 to support selection of a first set of Tx beams associated with the base station 120 and a first set of Rx beams associated with the wireless device 110. To enable beamforming at the base station 120, the base station 120 can sweep a set of different Tx beams. To enable beamforming at the wireless device 110, the wireless device 110 can sweep a set of different Rx beams. In an example, a P-2 procedure 920 can be used to enable a wireless device 110 to measure one or more Tx beams associated with a base station 120 to possibly change the first set of Tx beams associated with the base station 120. The P-2 procedure 920 can be performed on a set of possibly smaller beams for beam refinement compared to the P-1 procedure 910. The P-2 procedure 920 can be a special case of the P-1 procedure 910. In an example, a P-3 procedure 930 can be used to enable a wireless device 110 to measure at least one Tx beam associated with a base station 120 to change the first set of Rx beams associated with the wireless device 110. X In an example, a P-2 procedure 920 can be used to enable a wireless device 110 to measure one or more Tx beams associated with a base station 120 to possibly change the first set of Tx beams associated with the base station 120. The P-2 procedure 920 can be performed on a set of possibly smaller beams for beam refinement compared to the P-1 procedure 910. The P-2 procedure 920 can be a special case of the P-1 procedure 910. In an example, a P-3 procedure 930 can be used to enable a wireless device 110 to measure at least one Tx beam associated with a base station 120 to change the first set of Rx beams associated with the wireless device 110.

[0263] Wireless devices 110 can transmit one or more beam management reports to base stations 120. In one or more beam management reports, wireless devices 110 can indicate some beam pair quality parameters including at least: one or more beam identifications of a subset of configured beams; RSRP; precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI). Based on the one or more beam management reports, base stations 120 can transmit a signal to wireless devices 110 indicating that one or more beam pair links are one or more serving beams. Base stations 120 can use the one or more serving beams to transmit PDCCH and PDSCH for wireless devices 110.

[0264] In example embodiments, a new radio network can support bandwidth adaptation (BA). In an example, a reception and / or transmission bandwidth configured by a UE employing BA can not be large. For example, the reception and / or transmission bandwidth can not be as large as a bandwidth of a cell. The reception and / or transmission bandwidth can be adjustable. For example, a UE can change the reception and / or transmission bandwidth, e.g., to shrink during a low activity period to save power. For example, a UE can change a location of the reception and / or transmission bandwidth in the frequency domain, e.g., to increase scheduling flexibility. For example, a UE can change a subcarrier spacing, e.g., to allow for different services.

[0265] In example embodiments, a subset of a total cell bandwidth of a cell can be referred to as a bandwidth part (BWP). A base station can configure a UE with one or more BWPs to enable BA. For example, a base station can indicate to a UE which of the one or more (configured) BWPs is an active BWP.

[0266] Figure 10 is an example diagram of 3 configured BWPs: BWP1 (1010 and 1050), 40 MHz wide, 15 kHz subcarrier spacing; BWP2 (1020 and 1040), 10 MHz wide, 15 kHz subcarrier spacing; BWP3 1030, 20 MHz wide, 60 kHz subcarrier spacing.

[0267] In an example, a UE configured for operation in one or more BWPs of a cell can be configured by one or more higher layers (e.g., RRC layer) of the cell with a set of one or more BWPs (e.g., up to four BWPs) for the UE (DL BWP set) to receive in a DL bandwidth through at least one parameter DL-BWP, and a set of one or more BWPs (e.g., up to four BWPs) for the UE (UL BWP set) to transmit in a UL bandwidth through at least one parameter UL-BWP for the cell.

[0268] To enable BA on a PCell, a base station can configure a UE with one or more pairs of UL and DL BWPs. To enable BA on an SCell (e.g., in the case of CA), a base station can configure a UE with at least one or more DL BWPs (e.g., possibly none in UL).

[0269] In an example, an initial active DL BWP can be defined by at least one of a location and a number of contiguous PRBs of a control resource set for at least one common search space, a subcarrier spacing, or a cyclic prefix. For operation on a PCell, one or more higher layer parameters can indicate at least one initial UL BWP for a random access procedure. If a UE is configured with a secondary carrier on a primary cell, the UE can be configured with an initial BWP for a random access procedure on the secondary carrier.

[0270] In an example, for unpaired spectrum operation, a UE can expect that a center frequency of a DL BWP can be the same as a center frequency of an UL BWP.

[0271] For example, for a DL BWP or an UL BWP in a set of one or more DL BWPs or one or more UL BWPs, respectively, a base station can semi-statically configure a UE for a cell with one or more parameters indicating at least one of: a subcarrier spacing; a cyclic prefix; a number of contiguous PRBs; an index in a set of one or more DL BWPs and / or one or more UL BWPs; a link between a DL BWP and an UL BWP from a set of configured DL BWPs and UL BWPs; a DCI detection for a PDSCH reception timing; a PDSCH reception for a HARQ-ACK transmission timing value; a DCI detection for a PUSCH transmission timing value; an offset of a first PRB of a DL bandwidth or an UL bandwidth with respect to a first PRB of a bandwidth, respectively.

[0272] In an example, for a DL BWP in a set of one or more DL BWPs on a PCell, a base station can configure a UE with one or more control resource sets for at least one type of common search space and / or one UE-specific search space. For example, a base station can not configure a UE without a common search space on a PCell or a PSCell in an active DL BWP.

[0273] For an UL BWP in a set of one or more UL BWPs, a base station can configure a UE with one or more resource sets for one or more PUCCH transmissions.

[0274] In an example, if a DCI includes a BWP indicator field, a BWP indicator field value can indicate an active DL BWP from a set of configured DL BWPs for one or more DL receptions. If a DCI includes a BWP indicator field, a BWP indicator field value can indicate an active UL BWP from a set of configured UL BWPs for one or more UL transmissions.

[0275] In an example, for a PCell, the base station can semi-statistically configure the UE with a default DL BWP among the configured DL BWPs. If the UE is not provided with a default DL BWP, the default BWP can be the initial active DL BWP.

[0276] In an example, the base station can configure the UE with a timer value for a PCell. For example, when the UE detects a DCI indicating an active DL BWP other than the default DL BWP for a paired spectrum operation or when the UE detects a DCI indicating an active DL BWP or UL BWP other than the default DL BWP or UL BWP for an unpaired spectrum operation, the UE can start a timer referred to as a BWP inactivity timer. If the UE does not detect a DCI during an interval for a paired spectrum operation or for an unpaired spectrum operation, the UE can increment the timer by an interval of a first value (e.g., the first value can be 1 millisecond or 0.5 milliseconds). In an example, the timer can expire when the timer is equal to the timer value. When the timer expires, the UE can switch from the active DL BWP to the default DL BWP.

[0277] In an example, the base station can semi-statistically configure the UE with one or more BWPs. The UE can switch the active BWP from a first BWP to a second BWP (e.g., the second BWP can be a default BWP) in response to receiving a DCI indicating the second BWP as an active BWP and / or in response to an expiration of a BWP inactivity timer. For example, Figure 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) can be a default BWP. BWP1 (1010) can be an initial active BWP. In an example, the UE can switch the active BWP from BWP1 1010 to BWP2 1020 in response to an expiration of a BWP inactivity timer. For example, the UE can switch the active BWP from BWP2 1020 to BWP3 1030 in response to receiving a DCI indicating BWP3 1030 as an active BWP. Switching the active BWP from BWP3 1030 to BWP2 1040 and / or from BWP2 1040 to BWP1 1050 can be in response to receiving a DCI indicating an active BWP and / or in response to an expiration of a BWP inactivity timer.

[0278] In an example, if a UE is configured with a default DL BWP among the configured DL BWPs and a timer value for a secondary cell, the UE procedure on the secondary cell can be the same as the UE procedure on a primary cell using the timer value for the secondary cell and the default DL BWP for the secondary cell.

[0279] In an example, if the base station configures the UE with a first active DL BWP and a first active UL BWP on a secondary cell or carrier, the UE can use the indicated DL BWP and the indicated UL BWP on the secondary cell as the respective first active DL BWP and first active UL BWP on the secondary cell or carrier.

[0280] Figure 11A and Figure 11B Packet flows employing multi-connectivity (e.g., dual connectivity, multi-connectivity, tight interworking, etc.) are shown. Figure 11A is an example diagram of a protocol structure of a wireless device 110 (e.g., UE) with CA and / or multi-connectivity in accordance with aspects of the embodiments. Figure 11B is an example diagram of a protocol structure of a plurality of base stations with CA and / or multi-connectivity in accordance with aspects of the embodiments. The plurality of base stations can include a master node MN 1130 (e.g., master node, master base station, master gNB, master eNB, etc.) and a secondary node SN 1150 (e.g., secondary node, secondary base station, secondary gNB, secondary eNB, etc.). The master node 1130 and the secondary node 1150 can work together to communicate with the wireless device 110.

[0281] When a wireless device 110 is configured with multi-connectivity, a wireless device 110 that supports multiple reception / transmission functions in RRC connected state can be configured to utilize radio resources provided by multiple schedulers of multiple base stations. The multiple base stations can be interconnected via a non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, etc.). The base stations involved in multi-connectivity for a certain wireless device can perform at least one of two different roles: a base station can act as a master base station or a secondary base station. In multi-connectivity, a wireless device can be connected to one master base station and one or more secondary base stations. In an example, a master base station (e.g., MN 1130) can provide a master cell group (MCG) including a master cell and / or one or more secondary cells for a wireless device (e.g., wireless device 110). A secondary base station (e.g., SN 1150) can provide a secondary cell group (SCG) including a primary secondary cell (PSCell) and / or one or more secondary cells for a wireless device (e.g., wireless device 110).

[0282] In multi-connectivity, the radio protocol architecture employed by a bearer can depend on how the bearer is setup. In an example, three different types of bearer setup options can be supported: MCG bearers, SCG bearers, and / or split bearers. A wireless device can receive / transmit packets for MCG bearers via one or more cells of the MCG, and / or can receive / transmit packets for SCG bearers via one or more cells of the SCG. Multi-connectivity can also be described as having at least one bearer configured to use radio resources provided by a secondary base station. Multi-connectivity can or can not be configured / implemented in some example embodiments.

[0283] In an example, a wireless device (e.g., wireless device 110) can transmit and / or receive packets for MCG bearers via a SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC 1114), and a MAC layer (e.g., MN MAC 1118); transmit and / or receive packets for split bearers via a SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112), one of a primary or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116), and one of a primary or secondary MAC layer (e.g., MN MAC 1118, SN MAC 1119); and / or transmit and / or receive packets for SCG bearers via a SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC 1117), and a MAC layer (e.g., MN MAC 1119).

[0284] In an example, a master base station (e.g., MN 1130) and / or a secondary base station (e.g., SN 1150) can: transmit / receive packets for MCG bearers via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121, NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125), and a master node MAC layer (e.g., MN MAC 1128); transmit / receive packets for SCG bearers via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NR PDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147), and a secondary node MAC layer (e.g., SN MAC 1148); transmit / receive packets for split bearers via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NR PDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SN RLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g., MN MAC 1128, SN MAC 1148).

[0285] In multi-connectivity, a wireless device can be configured multiple MAC entities: one MAC entity for a primary base station (e.g., MN MAC 1118), and other MAC entities for secondary base stations (e.g., SN MAC 1119). In multi-connectivity, a configured set of serving cells for a wireless device can include two subsets: a MCG including serving cells of a primary base station, and a SCG including serving cells of secondary base stations. For a SCG, one or more of the following configurations can apply: at least one cell of the SCG has a configured UL CC, and at least one cell of the SCG, referred to as a primary secondary cell (PSCell, PCell of the SCG, or sometimes referred to as PCell), is configured with PUCCH resources; there can be at least one SCG bearer or one split bearer when a SCG is configured; upon detecting a physical layer problem or a random access problem on the PSCell, or a number of NR RLC retransmissions associated with the SCG has been reached, or detecting an access problem on the PSCell during a SCG addition or a SCG change: an RRC connection re-establishment procedure can not be triggered, UL transmissions to cells of the SCG can be stopped, the primary base station can be informed by the wireless device of a SCG failure type, for split bearers, DL data transfer on the primary base station can be maintained; NR RLC Acknowledged Mode (AM) bearers can be configured for split bearers; a PCell and / or a PSCell can or can not be de-activated; a SCG change procedure (e.g., using security key change and RACH procedure) can be used to change a PSCell; and / or a change of bearer type between a split bearer and a SCG bearer, or a simultaneous configuration of a SCG and a split bearer, can or can not be supported.

[0286] With respect to the interaction between the primary base station and the secondary base station for multi-connectivity, one or more of the following can apply: the primary base station and / or the secondary base station can maintain the RRM measurement configuration of the wireless device; the primary base station can decide to request the secondary base station to provide additional resources (e.g., serving cells) for the wireless device (e.g., based on the received measurement report, traffic conditions, and / or bearer types); upon receiving the request from the primary base station, the secondary base station can create / modify a container that can result in configuring additional serving cells for the wireless device (or determine that the secondary base station has no resources available to do so); for UE capability coordination, the primary base station can provide the (partial) AS configuration and UE capability to the secondary base station; the primary base station and the secondary base station can exchange information about the UE configuration by employing an RRC container (inter-node message) carried via Xn message; the secondary base station can initiate reconfiguration of the secondary base station existing serving cells (e.g., towards PUCCH of the secondary base station); the secondary base station can decide which cell is the PSCell within the SCG; the primary base station can change or not change the content of the RRC configuration provided by the secondary base station; in the case of SCG addition and / or SCG SCell addition, the primary base station can provide the latest (or most recent) measurement results for one or more SCG cells; the primary base station and the secondary base station can receive information of SFN and / or subframe offset of each other from OAM and / or via Xn interface (e.g., for the purpose of DRX alignment and / or identification of measurement gaps). In an example, when a new SCG SCell is added, dedicated RRC signaling can be used to send the system information required for the CA cell, except for the SFN obtained from the MIB of the PSCell of the SCG.

[0287] Figure 12 is an example diagram of a random access procedure. One or more events can trigger the random access procedure. For example, the one or more events can be at least one of: initial access from RRC_IDLE, RRC connection reestablishment procedure, handover, DL or UL data arrival during RRC_CONNECTED when the UL synchronization status is non-synchronized, transition from RRC_Inactive, and / or request for other system information. For example, a PDCCH order, a MAC entity, and / or a beam failure indication can initiate the random access procedure.

[0288] In example embodiments, the random access procedure can be at least one of a contention-based random access procedure and a contention-free random access procedure. For example, the contention-based random access procedure can include one or more Msg 1 1220 transmissions, one or more Msg2 1230 transmissions, one or more Msg3 1240 transmissions, and contention resolution 1250. For example, the contention-free random access procedure can include one or more Msg 1 1220 transmissions and one or more Msg2 1230 transmissions.

[0289] In an example, a base station can transmit (e.g., unicast, multicast, or broadcast) a RACH configuration 1210 to a UE via one or more beams. The RACH configuration 1210 can include one or more parameters indicating at least one of the following: a set of available PRACH resources for transmission of random access preambles, an initial preamble power (e.g., random access preamble initial received target power), an RSRP threshold for selecting an SS block and corresponding PRACH resource, a power ramping factor (e.g., random access preamble power ramping step), a random access preamble index, a maximum number of preamble transmissions, preamble groups A and group B, a threshold to determine a random access preamble group (e.g., message size), a set of one or more random access preambles and corresponding PRACH resources (if any) for a system information request, a set of one or more random access preambles and corresponding PRACH resources (if any) for a beam failure recovery request, a time window to monitor a RA response, a time window to monitor a response for a beam failure recovery request, and / or a contention resolution timer.

[0290] In an example, the Msgl 1220 can be one or more transmissions of a random access preamble. For a contention-based random access procedure, a UE can select an SS block with an RSRP above an RSRP threshold. If there is a random access preamble group B, the UE can select one or more random access preambles from group A or group B depending on a potential Msg3 1240 size. If there is no random access preamble group B, the UE can select one or more random access preambles from group A. The UE can randomly (e.g., with equal probability or a normal distribution) select a random access preamble index from one or more random access preambles associated with the selected group. If the base station semi-statistically configures the UE with an association between random access preambles and SS blocks, the UE can randomly select a random access preamble index from one or more random access preambles associated with the selected SS block and the selected group with equal probability.

[0291] For example, a UE can initiate a contention-free random access procedure based on a beam failure indication from a lower layer. For example, a base station can semi- statically configure a UE with one or more contention-free PRACH resources for a beam failure recovery request associated with at least one of SS blocks and / or CSI-RSs. If at least one of the SS blocks with RSRP above a first RSRP threshold among the associated SS blocks or at least one of the CSI-RSs with RSRP above a second RSRP threshold among the associated CSI-RSs is available, the UE can select a random access preamble index corresponding to the selected SS block or CSI-RS from a set of one or more random access preambles for the beam failure recovery request.

[0292] For example, a UE can receive a random access preamble index from a base station via PDCCH or RRC for a contention-free random access procedure. If the base station does not configure the UE with at least one contention-free PRACH resource associated with SS blocks or CSI-RSs, the UE can select a random access preamble index. If the base station configures the UE with one or more contention-free PRACH resources associated with SS blocks and at least one SS block with RSRP above a first RSRP threshold among the associated SS blocks is available, the UE can select the at least one SS block and select a random access preamble corresponding to the at least one SS block. If the base station configures the UE with one or more contention-free PRACH resources associated with CSI-RSs and at least one CSI-RS with RSRP above a second RSRP threshold among the associated CSI-RSs is available, the UE can select the at least one CSI-RS and select a random access preamble corresponding to the at least one CSI-RS.

[0293] The UE can perform one or more Msgl 1220 transmissions by transmitting a selected random access preamble. For example, if the UE selects an SS block and is configured with an association between one or more PRACH occasions and one or more SS blocks, the UE can determine a PRACH occasion from the one or more PRACH occasions that corresponds to the selected SS block. For example, if the UE selects a CSI-RS and is configured with an association between one or more PRACH occasions and one or more CSI-RSs, the UE can determine a PRACH occasion from the one or more PRACH occasions that corresponds to the selected CSI-RS. The UE can transmit the selected random access preamble to the base station via the selected PRACH occasion. The UE can determine a transmit power for transmitting the selected random access preamble based at least on an initial preamble power and a power ramping factor. The UE can determine a RA-RNTI associated with the selected PRACH occasion in which the selected random access preamble is transmitted. For example, the UE can not determine a RA-RNTI for a beam failure recovery request. The UE can determine the RA-RNTI based at least on an index of a first OFDM symbol and an index of a first slot of the selected PRACH occasion and / or an uplink carrier index for the transmission of the Msgl 1220.

[0294] In an example, the UE can receive a random access response Msg 2 1230 from the base station. The UE can start a time window (e.g., ra-ResponseWindow) to monitor for a random access response. For a beam failure recovery request, the base station can configure the UE with a different time window (e.g., bfr-ResponseWindow) to monitor for a response to the beam failure recovery request. For example, the UE can start the time window (e.g., ra-ResponseWindow or bfr-ResponseWindow) at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of the preamble transmission. If the UE transmits multiple preambles, the UE can start the time window at a start of a first PDCCH occasion after a fixed duration of one or more symbols from an end of the first preamble transmission. The UE can monitor a PDCCH of the cell for at least one random access response identified by a RA-RNTI or for at least one response to a beam failure recovery request identified by a C-RNTI while a timer of the time window is running.

[0295] In an example, the UE can consider the reception of the random access response successful if the at least one random access response includes a random access preamble identifier corresponding to the random access preamble transmitted by the UE. The UE can consider the contention-free random access procedure successfully completed if the reception of the random access response is successful. The UE can consider the contention-free random access procedure successfully completed if the PDCCH transmission is addressed to the C-RNTI. In an example, the UE can consider the random access procedure successfully completed if the at least one random access response includes only the random access preamble identifier, and can indicate reception of an acknowledgement to the upper layer's system information request. If the UE has signaled multiple preamble transmissions, the UE can stop transmitting the remaining preambles, if any, in response to successfully receiving the corresponding random access response.

[0296] In an example, the UE can perform one or more Msg 3 1240 transmissions (e.g., for a contention-based random access procedure) in response to successful reception of the random access response. The UE can adjust the uplink transmission timing based on the timing advance command indicated by the random access response, and can transmit one or more transport blocks based on the uplink grant indicated by the random access response. The subcarrier spacing for the PUSCH transmission for Msg3 1240 can be provided by at least one higher layer (e.g., RRC) parameter. The UE can transmit the random access preamble via PRACH and transmit the Msg3 1240 via PUSCH on the same cell. The base station can indicate the UL BWP for the PUSCH transmission for Msg3 1240 via a system information block. The UE can use HARQ to retransmit the Msg 3 1240.

[0297] In an example, multiple UEs can perform Msg 1 1220 by transmitting the same preamble to the base station and receive the same random access response from the base station including an identity (e.g., TC-RNTI). Contention resolution 1250 can ensure that the UE does not mistakenly use another UE’s identity. For example, contention resolution 1250 can be based on C-RNTI on PDCCH or UE contention resolution identity on DL-SCH. For example, if the base station assigns a C-RNTI to the UE, the UE can perform contention resolution 1250 based on reception of PDCCH transmission addressed to the C-RNTI. In response to detecting the C-RNTI on PDCCH, the UE can consider contention resolution 1250 successful and can consider the random access procedure successfully completed. If the UE does not have a valid C-RNTI, contention resolution can be addressed by employing the TC-RNTI. For example, if a MAC PDU is successfully decoded and the MAC PDU includes a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg 3 1250, the UE can consider contention resolution 1250 successful and can consider the random access procedure successfully completed.

[0298] Figure 13 is an example structure of a MAC entity in accordance with aspects of an embodiment. In an example, a wireless device can be configured to operate in a multi-connectivity mode. A wireless device in RRC CONNECTED with multiple RX / TX can be configured to utilize radio resources provided by multiple schedulers located in multiple base stations. The multiple base stations can be connected through a non-ideal or ideal backhaul over an Xn interface. In an example, a base station of the multiple base stations can act as a primary base station or a secondary base station. The wireless device can be connected to one primary base station and one or more secondary base stations. The wireless device can be configured with multiple MAC entities, e.g., one MAC entity for the primary base station, and one or more other MAC entities for the one or more secondary base stations. In an example, a configured set of serving cells for the wireless device can include two subsets: a MCG including serving cells of the primary base station; and one or more SCGs including serving cells of the one or more secondary base stations. Figure 13 An example structure of a MAC entity is shown when a MCG and an SCG are configured for a wireless device.

[0299] In an example, at least one cell in the SCG can have a configured UL CC, where the cell of the at least one cell can be referred to as a PSCell or a PCell of the SCG, or sometimes simply a PCell. The PSCell can be configured with a PUCCH resource. In an example, when the SCG is configured, there can be at least one SCG bearer or one split bearer. In an example, upon detecting a physical layer problem or a random access problem on the PSCell, or upon reaching a number of RLC retransmissions associated with the SCG, or upon detecting an access problem on the PSCell during an SCG addition or an SCG change: an RRC connection re-establishment procedure can not be triggered, UL transmissions to the cells of the SCG can be stopped, the UE can inform the primary base station of a SCG failure type, and DL data transfer on the primary base station can be maintained.

[0300] In an example, a MAC sublayer can provide services such as data transfer and radio resource allocation to upper layers (e.g., 1310 or 1320). The MAC sublayer can include multiple MAC entities (e.g., 1350 and 1360). The MAC sublayer can provide data transfer services on logical channels. To accommodate different kinds of data transfer services, multiple types of logical channels can be defined. A logical channel can support transfer of a particular type of information. Logical channel types can be defined by what information is transferred (e.g., control or data). For example, BCCH, PCCH, CCCH, and DCCH can be control channels, and DTCH can be a traffic channel. In an example, a first MAC entity (e.g., 1310) can provide services on PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In an example, a second MAC entity (e.g., 1320) can provide services on BCCH, DCCH, DTCH, and MAC control elements.

[0301] The MAC sublayer can expect services from the physical layer (e.g., 1330 or 1340), such as data transfer services, signaling of HARQ feedback, scheduling requests, or signaling of measurement values (e.g., CQI). In an example, in dual connectivity, a wireless device can be configured with two MAC entities: one for the MCG and one for the SCG. The MAC entities of the wireless device can handle multiple transport channels. In an example, a first MAC entity can handle first transport channels, including PCCH of the MCG, a first BCH of the MCG, one or more first DL-SCHs of the MCG, one or more first UL-SCHs of the MCG, and one or more first RACHs of the MCG. In an example, a second MAC entity can handle second transport channels, including a second BCH of the SCG, one or more second DL-SCHs of the SCG, one or more second UL-SCHs of the SCG, and one or more second RACHs of the SCG.

[0302] In an example, if a MAC entity is configured with one or more SCells, there can be multiple DL-SCHs per MAC entity and there can be multiple UL-SCHs and multiple RACHs. In an example, there can be one DL-SCH and UL-SCH on the SpCell. In an example, for SCells, there can be one DL-SCH, zero or one UL-SCH, and zero or one RACH. The DL-SCH can support reception with different numerologies and / or TTI durations within a MAC entity. The UL-SCH can also support transmission with different numerologies and / or TTI durations within a MAC entity.

[0303] In an example, a MAC sublayer can support different functions and can utilize control (e.g., 1355 or 1365) elements to control the functions. The functions performed by a MAC entity can include mapping between logical channels and transport channels (e.g., in uplink or downlink), multiplexing (e.g., 1352 or 1362) of MAC SDUs from one or different logical channels into transport blocks (TB) to be delivered to the physical layer on the transport channel (e.g., in uplink), demultiplexing (e.g., 1352 or 1362) of MAC SDUs to one or different logical channels from transport blocks (TB) delivered from the physical layer on the transport channel (e.g., in downlink), scheduling information reporting (e.g., in uplink), error correction through HARQ in uplink or downlink (e.g., 1363), and logical channel prioritization in uplink (e.g., 1351 or 1361). A MAC entity can handle a random access procedure (e.g., 1354 or 1364).

[0304] Figure 14 is an example diagram of a RAN architecture including one or more base stations. In an example, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) can be supported at a node. A base station (e.g., gNB 120A or 120B) can include a base station central unit (CU) (e.g., gNB-CU 1420A or 1420B) and at least one base station distributed unit (DU) (e.g., gNB-DU 1430A, 1430B, 1430C, or 1430D) (if functional split is configured). Upper layer protocol layers of a base station can be located in a base station CU, and lower layers of a base station can be located in a base station DU. An F1 interface (e.g., CU-DU interface) connecting a base station CU and a base station DU can be ideal or non-ideal backhaul. F1-C can provide control plane connection over the F1 interface, and F1-U can provide user plane connection over the F1 interface. In an example, an Xn interface can be configured between base station CUs.

[0305] In an example, the base station CU can include RRC functions, SDAP layer, and PDCP layer, and the base station DU can include RLC layer, MAC layer, and PHY layer. In an example, various function split options between the base station CU and the base station DU are possible by locating different combinations of upper protocol layers (RAN functions) in the base station CU and lower protocol layers (RAN functions) in the base station DU. The function split can support flexibility in moving protocol layers between the base station CU and the base station DU depending on service requirements and / or network environment.

[0306] In an example, the function split options can be configured per base station, per base station CU, per base station DU, per UE, per bearer, per slice layer, or at other granularity. In per base station CU split, the base station CU can have a fixed split option, and the base station DU can be configured to match the split option of the base station CU. In per base station DU split, the base station DU can be configured with different split options, and the base station CU can provide different split options for different base station DUs. In per UE split, the base station (base station CU and at least one base station DU) can provide different split options for different wireless devices. In per bearer split, different split options can be used for different bearers. In per slice layer stitching, different split options can be applied for different slice layers.

[0307] Figure 15is an example diagram showing RRC state transitions of a wireless device. In an example, a wireless device can be in at least one of an RRC connected state (e.g., RRC connected 1530, RRC_Connected), an RRC idle state (e.g., RRC idle 1510, RRC ldle), and / or an RRC inactive state (e.g., RRC inactive 1520, RRC lnlactive). In an example, in the RRC connected state, the wireless device can have at least one RRC connection with at least one base station (e.g., gNB and / or eNB), which can have a UE context of the wireless device. The UE context (e.g., wireless device context) can include at least one of an access stratum context, one or more radio link configuration parameters, bearer (e.g., data radio bearer (DRB), signaling radio bearer (SRB), logical channel, QoS flow, PDU session, etc.) configuration information, security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and / or similar configuration information for the wireless device. In an example, in the RRC idle state, the wireless device can not have an RRC connection with a base station, and a UE context of the wireless device can not be stored in the base station. In an example, in the RRC inactive state, the wireless device can not have an RRC connection with a base station. A UE context of the wireless device can be stored in a base station, which can be referred to as an anchor base station (e.g., last serving base station).

[0308] In an example, a wireless device can transition a UE RRC state between the RRC idle state and the RRC connected state in two ways (e.g., connection release 1540 or connection setup 1550; or connection reestablishment), and / or between the RRC inactive state and the RRC connected state in two ways (e.g., connection deactivation 1570 or connection resume 1580). In an example, a wireless device can transition its RRC state from the RRC inactive state to the RRC idle state (e.g., connection release 1560).

[0309] In an example, an anchor base station can be a base station that can maintain a UE context (wireless device context) of a wireless device at least during a time period that the wireless device stays in a RAN notification area (RNA) of the anchor base station and / or the wireless device stays in the RRC inactive state. In an example, an anchor base station can be a base station that a wireless device in the RRC inactive state last connected to in the latest RRC connected state, or a base station that the wireless device last performed a RNA update procedure at. In an example, an RNA can include one or more cells operated by one or more base stations. In an example, a base station can belong to one or more RNAs. In an example, a cell can belong to one or more RNAs.

[0310] In an example, a wireless device can transition from a RRC connected state to a RRC inactive state in a base station. The wireless device can receive RNA information from the base station. The RNA information can include at least one of an RNA identifier, one or more cell identifiers of one or more cells of the RNA, a base station identifier, an IP address of the base station, an AS context identifier of the wireless device, a resume identifier, and / or the like.

[0311] In an example, an anchor base station can broadcast a message (e.g., a RAN paging message) to reach the wireless device in the RRC inactive state to the base stations of the RNA, and / or a base station receiving the message from the anchor base station can broadcast and / or multicast another message (e.g., a paging message) over the air interface to the wireless devices in its coverage area, cell coverage area, and / or beam coverage area associated with the RNA.

[0312] In an example, when the wireless device in the RRC inactive state moves into a new RNA, the wireless device can perform a RNA update (RNAU) procedure, which can include a random access procedure of the wireless device and / or a UE context retrieval procedure. The UE context retrieval can include the base station receiving a random access preamble from the wireless device and the base station retrieving a UE context of the wireless device from an old anchor base station. The retrieving can include sending a retrieve UE context request message including the resume identifier to the old anchor base station and receiving a retrieve UE context response message including the UE context of the wireless device from the old anchor base station.

[0313] In an example embodiment, a wireless device in the RRC inactive state can select a cell to camp on based on measurement results of at least one or more cells, a cell the wireless device can monitor for a RNA paging message, and / or a core network paging message from a base station. In an example, a wireless device in the RRC inactive state can select a cell to perform a random access procedure to resume a RRC connection and / or to transmit one or more packets to a base station (e.g., to a network). In an example, if the selected cell belongs to a different RNA than the RNA of the wireless device in the RRC inactive state, the wireless device can initiate a random access procedure to perform a RNA update procedure. In an example, if the wireless device in the RRC inactive state has one or more packets in a buffer to transmit to the network, the wireless device can initiate a random access procedure to transmit the one or more packets to a base station of the cell selected by the wireless device. The random access procedure can be performed between the wireless device and the base station with two messages (e.g., 2-step random access) and / or four messages (e.g., 4-step random access).

[0314] In an example embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC inactive state can retrieve a UE context for the wireless device by transmitting a Retrieve UE Context Request message for the wireless device to an anchor base station of the wireless device based on at least one of an AS context identifier, an RNA identifier, a base station identifier, a resume identifier, and / or a cell identifier received from the wireless device. In response to retrieving the UE context, the base station can transmit a Path Switch Request for the wireless device to a core network entity (e.g., an AMF, an MME, etc.). The core network entity can update one or more bearer downlink tunnel endpoint identifiers established for the wireless device between a user plane core network entity (e.g., a UPF, an S-GW, etc.) and a RAN node (e.g., a base station), for example, changing the downlink tunnel endpoint identifier from an address of the anchor base station to an address of the base station.

[0315] In an example, when a cell is configured with at least one closed access group (CAG) for a non-public network (NPN), the wireless device can need membership in one of the at least one CAG (e.g., need to be verified to access the at least one CAG) to access the cell and / or the NPN. In existing technologies for a base station configured with a split central unit and distributed unit (e.g., a CU-DU split base station), a base station central unit can request a base station distributed unit to configure a cell of a CAG for a wireless device that is not allowed to access the CAG, and / or the base station distributed unit can reject the request due to invalid membership of the wireless device for the CAG. In existing technologies, a base station central unit can send a paging message for a wireless device that is not allowed to access a CAG to a base station that only serves a cell of the CAG, and / or a base station distributed unit can not transmit a paging indication via any serving cell due to invalid membership of the wireless device. Existing interactions between a base station central unit and a base station distributed unit can increase unnecessary signaling for a CAG cell and / or a CAG wireless device. Implementations of existing technologies can increase inefficient signaling and / or decrease communication reliability for a wireless device. There is a need for an enhanced communication mechanism to obtain CAG support.

[0316] In existing technologies, when a wireless device is only allowed to access a first CAG, a base station central unit can send a paging message (e.g., a core network paging and / or a RAN paging) for the wireless device to a base station distributed unit that does not have a cell for the first CAG. It is inefficient to send a paging message for the wireless device using the first CAG to a base station distributed device that does not support the first CAG. Based on the paging message, the base station distributed unit can further send a paging indication via multiple cells that do not support the first CAG. Such implementations can increase inefficient radio resource utilization.

[0317] Exemplary embodiments can support information sharing between a base station central unit and a base station distributed unit for CAG cell configuration. Implementations of exemplary embodiments can support selectively configuring a cell for a wireless device based on CAG membership of the wireless device by providing a CAG cell information sharing mechanism over a Fl interface. Implementations of exemplary embodiments can support paging a wireless device via a selected base station distributed unit based on CAG membership of the wireless device by providing a CAG cell information sharing mechanism over a Fl interface. Exemplary embodiments can reduce unnecessary signaling for CAG cells and improve signaling efficiency between network nodes.

[0318] In an example, if a base station distributed unit only indicates to a base station central unit that a cell is for CAG when the cell allows non-CAG member access, the base station central unit can not attempt to configure the cell for non-member wireless devices for CAG even though the non-member wireless devices can access the cell. Such implementations can increase inefficient radio resource utilization. Exemplary embodiments can support a base station distributed unit indicating to a base station central unit whether a cell of a CAG allows non-CAG member access to the cell. Exemplary embodiments can improve resource utilization efficiency.

[0319] In prior art, if a paging message for a wireless device is received from a base station central unit, a base station distributed unit can transmit / broadcast a paging indication via one or more cells that do not support a first CAG when the wireless device is only allowed to access cells of the first CAG. Transmitting / broadcasting a paging indication for a wireless device via one or more cells that do not support a first CAG increases inefficient signaling and inefficient radio resource utilization. In prior art, if a paging message for a wireless device is received from a base station central unit, a base station distributed unit can transmit / broadcast a paging indication via one or more cells that only support one or more second CAGs to which the wireless device is not allowed to access. Transmitting / broadcasting a paging indication for a wireless device via one or more cells that only support one or more second CAGs increases inefficient signaling and inefficient radio resource utilization. Exemplary embodiments can support a base station distributed unit receiving a paging message from a base station central unit indicating whether the paging message is for a wireless device that is only allowed to access a first CAG. Exemplary embodiments can support a base station distributed unit receiving a paging message from a base station central unit indicating one or more CAGs to which a wireless device is allowed to access. Exemplary embodiments can improve efficiency of signaling and radio resource utilization.

[0320] A non-public network (NPN) can be intended for use by a private entity, such as an enterprise, and can be deployed in various configurations utilizing both virtual and physical elements. An NPN can be deployed as a standalone network (i.e., a standalone non-public network (SNPN)). As an alternative implementation, an NPN can be hosted by a PLMN and can be provided as a slice of a PLMN (i.e., a public network integrated NPN).

[0321] A public network integrated NPN can be an NPN provided via a PLMN, for example, by means of a dedicated DNN or through allocation of one (or more) network slice instance to the NPN. When an NPN is provided via a PLMN, a wireless device can have a subscription to the PLMN. Access control can also be applied using a closed access group (CAG) since the network slice cannot prevent a wireless device from attempting to access the network in areas where the wireless device is not allowed to use the network slice allocated for the NPN.

[0322] A CAG can identify a group of subscribers that are permitted to access one or more cells associated with the CAG. In an example, a CAG is used for a public network integrated NPN to prevent one or more wireless devices that are not allowed to access the NPN via the one or more associated cells from automatically selecting and accessing the one or more associated cells.

[0323] In an example, a CAG is identified by a CAG identifier that is unique within the range of PLMN IDs. A CAG cell can broadcast one or more CAG identifiers for each PLMN. Assume that a base station (e.g., NG-RAN) supports a total of twelve CAG identifiers to be broadcast. In addition, a CAG cell can broadcast a human-readable network name for each CAG identifier. In an example, the human-readable network name can be an enterprise name and is used to present to a user when the user requests manual CAG selection.

[0324] To support a CAG, a wireless device can be configured using a UE configuration update procedure to obtain access and mobility management related parameters with CAG information included as part of mobility restrictions in a subscription. The CAG information can include a list of allowed CAGs (i.e., a list of CAG identifiers that the UE is allowed to access), an indication of whether the UE is only allowed to access the 5GS via CAG cells, and the like. In an example, the indication is a CAG restriction indicator.

[0325] To support CAG, a base station can broadcast CAG related information via a cell. In an example, a cell that broadcasts one or more CAG identities can be a CAG cell. In an example, a cell that does not broadcast any CAG identities can be a non-CAG cell. In an example, the CAG related information can include an indication that only CAG capable wireless devices are allowed to access. The CAG cells and non-CAG cells can broadcast the indication. The indication for a CAG cell can be positive and the indication for a non-CAG cell can be negative. In an example, a wireless device can determine whether to access a cell based on the CAG related information. Mobility of the wireless device (e.g., for camping, handover, cell reselection) can be controlled / restricted by the CAG information of the wireless device and the CAG related information of the base station / cell.

[0326] Figure 16 and Figure 17 Examples of CAG and / or CAG cell deployment are shown. The coverage area of a first CAG can overlap with a second CAG. A CAG can cover a portion of a PLMN network. An NPN can configure multiple CAGs to implement differentiated access control for different UEs or different areas. Multiple CAGs of different NPNs can share the same cell.

[0327] In an example, a base station can use a CAG identifier to select an appropriate AMF, the wireless device is configured with CAG identifier 1 (CAG 1), and is accessing the base station via system information broadcasting CAG 1, CAG 2. The wireless device can send a radio resource control (RRC) message after completing RRC connection setup with the base station, requesting a connection transition from CM-IDLE to CM-CONNECTED. In an example, the RRC message is an RRC connection setup complete message. The RRC message can include a NAS request message and an access network (AN) parameter. In an example, the NAS request message is a registration request message or a service request message. In an example, the AN parameter can include a CAG identifier (CAG 1). The base station can check whether the cell supports the CAG identifier in the AN parameter. The base station can select an appropriate AMF based on the CAG identifier (CAG 1). In an example, two or more AMFs can be connected with the base station, and some AMFs can not support CAG1 or a slice corresponding to CAG 1. The base station can send a N2 message including the NAS message and the CAG identifier in the RRC message to the AMF.

[0328] In an example, the AMF can have context information of the wireless device including a CAG white list, and the CAG white list includes CAG 1. In this case, the AMF can determine to allow the wireless device to access the 5GS via the base station, and can send a NAS accept message to the wireless device in response to the determination.

[0329] In an example, if the AMF has the context information of the wireless device but does not have the CAG identifier (CAG 1), the AMF can check with the UDM whether the UE is allowed to access the base station. If the wireless device is allowed to access the cell with CAG 1, the AMF can include CAG 1 in the CAG whitelist of the wireless device and send a NAS accept message to the wireless device. If the wireless device is not allowed to access the cell with CAG 1, the AMF can reject the wireless device by sending a NAS reject message.

[0330] In an example, if the AMF does not have the context information of the wireless device (this can be the case of initial registration), the AMF can interact with the UDM and check whether the UE is allowed to access the base station. If the wireless device is allowed to access the cell with CAG 1, the AMF can include CAG 1 in the CAG whitelist of the wireless device and send a NAS accept message (i.e., registration accept) to the wireless device. If the wireless device is not allowed to access the cell with CAG 1, the AMF can reject the wireless device (i.e., registration reject) by sending a NAS reject message.

[0331] The wireless device can access the base station in a non-CAG cell. The wireless device can send a radio resource control (RRC) message after completing the RRC connection setup with the base station, requesting a connection transition from CM-IDLE to CM-CONNECTED. In an example, the RRC message is an RRC connection setup complete message. The RRC message can include a NAS request message and an access network (AN) parameter. In an example, the NAS request message is a registration request message or a service request message. The base station can send a N2 message to the AMF including the NAS message in the RRC message. In an example, the N2 message does not include any CAG identifier.

[0332] In an example, the AMF can have the context information of the wireless device including a CAG restriction indicator. The AMF can determine whether to allow the wireless device to access the 5GS via the base station (non-CAG cell) based on the CAG restriction indicator of the wireless device. In an example, the AMF can determine to allow the wireless device to access the 5GS via the non-CAG cell in response to the CAG restriction indicator being a negative value (i.e., the CAG restriction indicator indicates that the wireless device is not restricted to access the 5GS only via CAG cells). The AMF can send a NAS accept message to the wireless device in response to the determination. In an example, the AMF can determine not to allow the wireless device to access the 5GS via the non-CAG cell in response to the CAG restriction indicator being a positive value (i.e., the CAG restriction indicator indicates that the wireless device is restricted to access the 5GS only via CAG cells). The AMF can send a NAS reject message to the wireless device with an appropriate cause value in response to the determination. In an example, the cause value can indicate that the request is rejected because the wireless device accesses via non-CAG cells.

[0333] In an example, if the AMF does not have the context information of the wireless device (this can be the initial registration case), the AMF can interact with the UDM and check whether the UE is allowed to access via non-CAG cell based on the CAG Restriction Indicator of the wireless device. Based on the CAG Restriction Indicator of the wireless device, the AMF behavior is the same as the previous description.

[0334] In an example, as shown in Figure 18 , Figure 20 , Figure 22 , Figure 24 , Figure 26 and / or Figure 28 , a base station (e.g., gNB, eNB, gNB1, eNB1, etc.) can include a base station distributed unit (e.g., gNB-DU, distributed unit, DU, IAB-node, etc.) and a base station central unit (e.g., gNB-CU, central unit, CU, IAB-donor, etc.). The base station can also include a second base station distributed unit (e.g., gNB-DU2, second distributed unit, DU2, IAB-node2, etc.). The base station distributed unit can be connected to the base station central unit via an Fl interface (e.g., a direct interface). In an example, the base station distributed unit and / or the second base station distributed unit can include / provide lower layer functionality of the base station. The lower layer functionality can include at least one of: radio link control (RLC) layer functionality; medium access control (MAC) layer functionality; physical layer functionality; and / or a portion of the physical layer functionality. The base station central unit can include / provide upper layer functionality of the base station. The upper layer functionality can include at least one of: RRC functionality; service data adaptation protocol (SDAP) layer functionality; PDCP layer functionality; RLC layer functionality; MAC layer functionality; and / or a portion of the physical layer functionality. The base station distributed unit can be an integrated access and backhaul (IAB) node. The base station central unit can be an IAB donor. In an example, the base station and / or the base station central unit can be connected to an access and mobility management function (AMF) via an N2 interface (e.g., S1 interface, S1-C) (e.g., for control plane connection) and / or can be connected to a user plane function (UPF) via an N3 interface (e.g., S1 interface, S1-U) (e.g., for user connection plane). In an example, the base station and / or the base station central unit can be connected to a second base station (e.g., gNB2, eNB2, neighboring base station of the base station, etc.) via an Xn interface (e.g., X2 interface).

[0335] In an example, a base station distributed unit can transmit a configuration request message to a base station central unit, the configuration request message including cell information for one or more cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group. The base station distributed unit can receive a response message to the configuration request message.

[0336] In an example, as Figure 18 and / or Figure 19 shown, the base station central unit can determine, based on the cell information, cell configuration parameters for the one or more cells of the wireless device. The wireless device can be allowed access to the first closed access group. The base station distributed unit can receive, from the base station central unit, a context configuration request message including the cell configuration parameters for the one or more cells of the wireless device.

[0337] In an example, as Figure 22 and / or Figure 23 shown, the base station central unit can determine, based on the cell information, to transmit a paging message for a second wireless device to the base station distributed unit. The second wireless device can be allowed access to the first closed access group. The base station distributed unit can receive, from the base station central unit, the paging message for the second wireless device based on the cell information. The base station distributed unit can transmit a paging indication for the second wireless device in response to receiving the paging message.

[0338] The base station central unit can receive, from a second base station distributed unit, a second configuration request message including second cell information for one or more second cells (e.g., all serving cells) of the second base station distributed unit. The second cell information can indicate that the one or more second cells are not associated with a first closed access group (e.g., associated with a second closed access group). The base station central unit can determine, based on the second cell information, not to configure the one or more second cells of the second base station distributed unit for the wireless device. The base station central unit can determine, based on the second cell information, not to transmit a paging message for the wireless device to the second base station distributed unit.

[0339] In an example, a base station distributed unit can transmit a configuration request message (e.g., one or more configuration request messages) to a base station central unit, the configuration request message including cell information of one or more cells of the base station distributed unit. The one or more cells can be serving cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group (CAG). In an example, the one or more cells can belong to the first CAG. The first CAG can be associated with at least one of a first non-public network (NPN), a first network slice, and / or a first PLMN. A wireless device can access the first NPN via the one or more cells. The first CAG can be configured to perform access control for wireless devices that attempt to employ / access the first NPN. The first NPN can be assigned / configured with the first network slice (e.g., in a PLMN; e.g., in a first PLMN). In an example, the wireless device can employ / use the first PLMN to access / use the first NPN.

[0340] In an example, a base station distributed unit (e.g., an IAB-node) can select a base station central unit (e.g., an IAB-donor) based on a base station central unit that is supporting a first CAG. Transmitting a configuration request message to a base station central unit can be based on selecting a base station central unit (e.g., an IAB-donor) from the base station central unit that is supporting the first CAG. The base station distributed unit can receive a system information block including an identifier of the first CAG from the base station central unit. Selecting the base station central unit can be based on the system information block.

[0341] In an example, a base station distributed unit can transmit a configuration request message via an Fl interface (e.g., an interface between a base station central unit and a base station distributed unit). In an example, the configuration request message can include at least one of: an Fl message, an Fl setup request message; a base station distributed unit configuration update message (e.g., a gNB-DU configuration update message); a base station central unit configuration update acknowledgement message (e.g., a gNB-CU configuration update acknowledgement message), and / or the like. In an example, the configuration request message can include at least one of: a gNB-DU identifier of the base station distributed unit, a gNB-DU name of the base station distributed unit, gNB-DU RRC version information, and / or the like.

[0342] The one or more cells can be further associated with a second CAG. The second closed access group can be associated with at least one of: a second NPN, a second network slice, and / or a second PLMN. The one or more cells can be associated with multiple CAGs. The cell information of the one or more cells can indicate that the one or more cells are associated with multiple CAGs (e.g., a first CAG, a second CAG, and / or the like).

[0343] In an example, the cell information of the one or more cells can further indicate whether non-members of the first CAG are allowed to access a cell (e.g., closed cell or hybrid cell) in the one or more cells. If a cell in the one or more cells is a closed cell (e.g., CAG cell), the non-member wireless device can not be able to access the cell (e.g., membership verification can fail). If a cell in the one or more cells is a hybrid cell, the non-member wireless device can be able to access the cell and / or be able to use a limited QoS for the service (e.g., can be guaranteed with deprioritized, differentiated QoS compared to member wireless devices). In an example, the cell information of the one or more cells can indicate whether a second wireless device that is not a member of the first closed access group is allowed to access a cell (e.g., closed cell or hybrid cell) in the one or more cells.

[0344] In an example, the cell information of the one or more cells can include a physical cell identifier (PCI) that indicates a cell in the one or more cells. The PCI can further indicate whether non-members of the first CAG are allowed to access a cell (e.g., closed cell or hybrid cell) in the one or more cells. The PCI can further indicate whether a second wireless device that is not a member of the first closed access group is allowed to access a cell (e.g., closed cell or hybrid cell) in the one or more cells. The cell in the one or more cells can be at least one of a closed cell and / or a hybrid cell. In an example, a cell in a first range of PCIs (e.g., PCI = 1, 2...n-1) can be a normal cell (e.g., hybrid cell). In an example, a cell in a second range of PCIs (e.g., PCI = n, n+1...k) can be a CAG cell (e.g., closed cell).

[0345] In an example, the cell information of the one or more cells can include parameters of a cell (e.g., each cell) in the one or more cells. The parameters of the cell can include at least one of: gNB-DU system information, a cell identifier (e.g., global cell identifier, CGI, physical cell identifier, PCI, etc.), tracking area information (e.g., tracking area code, TAC, tracking area identifier, TAI, etc.), at least one PLMN identifier, a list of supported network slice layers (e.g., S-NSSAI, NSSAI; supported in a tracking area and / or cell), FDD and / or TDD configuration parameters, downlink and / or uplink frequency / bandwidth information (e.g., frequency offset, strip, bandwidth, bandwidth part configuration parameters, etc.), beam configuration parameters (e.g., SSB, CSI-RS, DM-RS parameters), measurement timing configuration information (e.g., SSB and / or RS configuration parameters for measurement; frequency / timing scheduling information), RAN area code, etc.

[0346] In an example, the base station distributed unit can receive a response message to the configuration request message. The base station distributed unit can receive the response message to the configuration request message in response to transmitting the configuration request message. The base station distributed unit can receive the response message via the Fl interface. In an example, the response message can comprise at least one of: an Fl message, an Fl setup response message, a base station distributed unit configuration update acknowledgement message (e.g., a gNB-DU configuration update acknowledgement message), and / or the like.

[0347] In an example, the response message can comprise at least one of: a gNB-CU name of the base station central unit, a cell identifier (e.g., a PCI, a CGI) of an active cell of one or more cells of the base station distributed unit, gNB-CU system information (e.g., a system information block, SIB) of the active cell of the one or more cells of the base station distributed unit, one or more PLMNs of the active cell of the one or more cells, and / or the like.

[0348] In an example, the response message can comprise a system information block (SIB) (e.g., at least one system information block) for a cell (e.g., an active cell, each active cell) of the one or more cells. The system information block can comprise an identifier (e.g., a PCI, a CGI) of the cell (e.g., the active cell) of the one or more cells. The system information block can comprise an identifier (e.g., a CAG ID) of a first CAG (e.g., and / or a second CAG, a plurality of CAGs) for the cell (e.g., the active cell) of the one or more cells. The base station distributed unit can transmit / broadcast the system information block (e.g., via a cell (e.g., a corresponding cell, a cell of the one or more cells) associated with the first closed access group) to one or more wireless devices. The system information block can further comprise at least one of: a network identifier of a first NPN associated with the first CAG; a first network slice selection assistance information (NSSAI) of a first network slice layer of the first CAG; and / or a first identifier of a first PLMN associated with the first CAG. The system information block can further comprise one or more cell identifiers of the one or more cells. The one or more wireless devices (e.g., members of the first CAG) can transmit a random access preamble to the base station distributed unit via the cell of the one or more cells based on the system information block (e.g., based on the identifier of the first CAG).

[0349] In an example, as Figure 24 and / or Figure 25As shown, the base station central unit (e.g., base station) can transmit, to the AMF, a second configuration request message including second cell information of the base station and / or the base station central unit based on the cell information (e.g., of the configuration request message). In an example, the base station central unit can transmit the second configuration request message via an N2 interface (e.g., an S1 interface). The second configuration request message can include at least one of: an NG setup request message (e.g., an S1 setup request message), a base station configuration update message (e.g., a RAN / gNB / eNB configuration update message), a core node configuration update acknowledgment message (e.g., an AMF / MME configuration update acknowledgment message), and / or the like.

[0350] In an example, the second cell information can include an identifier (e.g., a CAG ID) of a first CAG (e.g., a second CAG, a plurality of CAGs, and / or the like). The second cell information can include a list of CAGs associated with one or more serving cells (e.g., one or more cells) of the base station (e.g., the base station distributed unit and / or the base station central unit). The second cell information can include at least one of: an identifier (e.g., a PCI, a CGI, and / or the like) of a serving cell, an identifier (e.g., a first CAG, a second CAG, and / or the like) of a CAG associated with a serving cell, an identifier of an NPN (e.g., a first NPN, a second NPN, and / or the like) associated with a serving cell, an identifier (e.g., a first PLMN, a second PLMN, and / or the like) of a PLMN associated with a serving cell, and / or the like.

[0351] The second cell information can further indicate whether non-members of the first CAG are allowed to access at least one of the serving cells (e.g., a closed cell or a hybrid cell) of the base station that are associated with the first CAG. The second cell information can further indicate whether a second wireless device that is a non-member of the first CAG is allowed to access at least one of the serving cells (e.g., a closed cell or a hybrid cell) of the base station that are associated with the first CAG. The serving cell associated with the first CAG can be one of the one or more cells of the base station distributed unit.

[0352] In an example, the second cell information can further include at least one of: a list of tracking areas (TAs) supported by the base station (e.g., the base station central unit, the base station distributed unit, and / or the like), a list of PLMNs supported by the base station, a list of network slices supported by the base station and / or one or more of the TAs, and / or the like.

[0353] In an example, the AMF can determine a paging area (e.g., target base station for paging) for paging the wireless device based on the second cell information. In an example, to page a wireless device that is a member of a CAG, the AMF can transmit a paging message to a base station that supports the CAG (e.g., a cell that serves the CAG) or that serves a normal cell (e.g., a non-CAG cell, an open / public cell), and / or a hybrid cell. The AMF can send the paging message to the base station (e.g., base station central unit) to page the wireless device that is a member of a first CAG (e.g., a second CAG, a plurality of CAGs, etc.).

[0354] In an example, the base station central unit can receive, from the AMF, a second response message to the second configuration request message. In an example, the base station central unit can receive, from the AMF, the second response message to the second configuration request message in response to sending the second configuration request message. The base station central unit can receive the second response message via an NG interface (e.g., an SI interface). The second response message can include at least one of: an identifier of the AMF (e.g., an identifier of an MME, a GUAMI, etc.), an identifier of a supported PLMN, an identifier of a supported network slice (e.g., an NSSAI, an S-NSSAI), an identifier of a supported NPN, an identifier of a supported CAG (e.g., indicating whether the first CAG is allowed for the base station; if supported, an identifier of the first CAG), and / or the like.

[0355] In an example, the base station central unit can determine cell configuration parameters for one or more cells of the wireless device based on cell information of the one or more cells. The base station central unit can determine whether to configure at least one of the one or more cells for the wireless device based on the cell information. In an example, the base station central unit can configure the at least one of the one or more cells for the wireless device if the at least one of the one or more cells is associated with a first CAG and the wireless device is a member of the first CAG. In an example, the base station central unit can configure the at least one of the one or more cells for the wireless device if the at least one of the one or more cells is a normal cell (e.g., a non-CAG cell, an open cell, a public cell, etc.) and / or a hybrid cell associated with the first CAG and the wireless device is a member or a non-member of the first CAG. In an example, the base station central unit can not configure the at least one of the one or more cells for the wireless device if the at least one of the one or more cells is a closed cell (e.g., a CAG cell) associated with the first CAG and the wireless device is a non-member of the first CAG. In an example, the base station central unit can configure the at least one of the one or more cells for the wireless device to have limited QoS (e.g., downgraded / prioritized / differentiated QoS for bearers) if the at least one of the one or more cells is a hybrid cell (e.g., a CAG hybrid cell) associated with the first CAG and the wireless device is a non-member of the first CAG.

[0356] In an example, the base station central unit can further determine to configure the one or more cells for the wireless device based on at least one of: receiving (e.g., via an Xn / X2 interface and / or via an AMF) a handover request for the wireless device from a neighboring base station (e.g., a second base station); receiving a secondary node addition / configuration request message (e.g., a Snode / SgNB / SeNB addition request message, a Snode / SgNB / SeNB configuration update message, etc.) for the wireless device from a neighboring base station (e.g., a second base station); determining to handover (e.g., intra-base station and inter-base station distributed unit handover; intra-base station and intra-base station distributed unit handover, etc.) the wireless device to one of the one or more cells of the base station distributed unit; determining to add at least one of the one or more cells as at least one secondary cell of the wireless device; determining to add at least one of the one or more cells as a secondary cell group of the wireless device; determining to add the base station distributed unit as a secondary base station distributed unit for the wireless device; etc.

[0357] In an example, as Figure 20 and / or Figure 21As shown, the base station central unit can receive, from a second base station, a handover request message for a wireless device. In an example, the base station central unit can receive the handover request message for the wireless device from the second base station or from an AMF (e.g., the AMF can receive a handover required message from the second base station and send the handover request message to the base station central unit for handover). In an example, determining cell configuration parameters for one or more cells of the wireless device can be based on the handover request message. The handover request message can include an identifier (e.g., a CGI, a PCI) of a cell of the one or more cells as a handover target cell. The handover request message can include a measurement result (e.g., an RSRP, an RSRQ, etc.) of at least one cell of the one or more cells measured by the wireless device.

[0358] In an example, as shown, Figure 20 and / or Figure 21 As shown, the base station central unit can receive, from a second base station, a secondary node configuration request message (e.g., an S-node / SgNB / SeNB addition request message, an S-node / SgNB / SeNB configuration update message, etc.) for a wireless device. In an example, determining cell configuration parameters for one or more cells of the wireless device can be based on the secondary node configuration request message. The secondary node configuration request message can include an identifier (e.g., a CGI, a PCI) of a cell of the one or more cells as a target primary secondary cell (e.g., a PScell, a special cell, a Spcell, etc.) and / or a target secondary cell (Scell). The secondary node configuration request message can include a measurement result (e.g., an RSRP, an RSRQ, etc.) of at least one cell of the one or more cells measured by the wireless device.

[0359] In an example, the base station central unit can receive, from the wireless device (e.g., via the base station distributed unit and / or a second base station distributed unit), a measurement report including a measurement result (e.g., an RSRP, an RSRQ, etc.) of at least one cell of one or more cells. In an example, the base station central unit can determine, based on the measurement report, to handover the wireless device (e.g., an intra-base station and inter-base station distributed unit handover; an intra-base station and intra-base station distributed unit handover, etc.) to one of the one or more cells of the base station distributed unit. In an example, the base station central unit can determine, based on the measurement report, to add at least one of the one or more cells as at least one secondary cell of the wireless device. In an example, determining cell configuration parameters for the one or more cells of the wireless device can be based on determining to handover the wireless device to one of the one or more cells. In an example, determining cell configuration parameters for the one or more cells of the wireless device can be based on determining to add at least one of the one or more cells as at least one secondary cell for the wireless device.

[0360] In an example, a base station central unit can transmit, to a base station distributed unit, a context configuration request message including cell configuration parameters for one or more cells of a wireless device. In an example, as shown in Figure 18 and / or Figure 19 As shown in FIG. 8, a base station distributed unit can receive, from a base station central unit, a context configuration request message including cell configuration parameters for a wireless device. The wireless device is allowed to access a first CAG. In an example, the base station distributed unit can receive the context configuration request message via an Fl interface. In an example, the context configuration request message can include at least one of: a UE context setup request message; a UE context modification request message, a UE context modification confirm message, etc.

[0361] In an example, the cell configuration parameters can include an information element indicating that one of the one or more cells is configured as a primary cell (e.g., Pcell, primary secondary cell, PScell, special cell, Spcell, etc.) or a secondary cell (e.g., Scell, primary secondary cell, PScell, special cell, Spcell, etc.) for the wireless device. The information element of the cell configuration parameters can include at least one of: a cell identifier (e.g., CGI, PCI, etc.) of the cell; a cell index of the cell; uplink configuration information (e.g., indicating that the cell is configured with one of no uplink, supplemental uplink, and / or normal uplink); and / or a serving cell measurement object (e.g., a measurement object identifier, servingCellMO).

[0362] In an example, the cell configuration parameters can include at least one cell identifier of at least one candidate special cell (e.g., primary cell, Pcell, primary secondary cell, PScell, etc.) for the wireless device. The at least one candidate special cell can be associated with the first closed access group.

[0363] In an example, the context configuration request message can include bearer configuration parameters of one or more bearers of a first network slice layer associated with the first closed access group. The bearer configuration parameters can include at least one of: an identifier of the bearer (e.g., a signaling radio bearer, SRB, a data radio bearer, DRB), an identifier of a logical channel associated with the bearer, an identifier of a session (e.g., a PDU session) associated with the bearer, an identifier of a QoS flow associated with the bearer, a QoS parameter of the bearer (e.g., a QoS parameter of a session, a QoS flow, and / or a logical channel), a duplication indication of the bearer (e.g., indicating whether PDCP packet duplication is configured for the bearer), network slice layer information associated with the bearer (e.g., a network slice layer identifier, a NSSAI, a S-NSSAI; e.g., an identifier of the first network slice layer), a network identifier of a network associated with the bearer (e.g., a first NPN), etc.

[0364] The context configuration request message can include an identifier of at least one CAG (e.g., a first CAG) that the wireless device is allowed to access. The context configuration request message can include an identifier of at least one cell (e.g., one or more cells) that the wireless device is allowed to access. The context configuration request message can include an identifier of at least one cell (e.g., one or more cells) that the wireless device is configured with. The context configuration request message can include an identifier of the wireless device (e.g., an IMEI, a TMSI, a UE Fl identifier, a gNB-CU UE FlAP ID, a gNB-DU UE FlAP ID, etc.). The context configuration request message can further include RRC configuration parameters for the wireless device.

[0365] In an example, the base station distribution cell can receive, based on the cell information, a second context configuration request message including second cell configuration parameters for one or more cells of the second wireless device (e.g., not a first CAG member; e.g., if the one or more cells are hybrid cells).

[0366] In an example, the base station distribution unit can receive, based on the cell information, a third context configuration request message including third cell configuration parameters for one or more second cells of a third wireless device. The one or more second cells can be different from the one or more cells. The third wireless device can not be allowed to access the first CAG (e.g., the one or more cells are closed cells and / or CAG cells). The third wireless device can not be a member of the first CAG (e.g., the one or more cells are closed cells and / or CAG cells).

[0367] In an example, the base station distribution unit can configure the one or more cells for the wireless device based on the cell configuration parameters. In an example, the base station distribution unit can send, to the base station central unit, a context configuration response message acknowledging the context configuration for the wireless device in response to the context configuration request message. The context configuration response message can be based on configuring the cell configuration parameters at the base station distribution unit. The context configuration response message includes at least one of: a UE context setup response message and / or a UE context modification response message. The base station distribution unit can send the context configuration response message via the Fl interface. In an example, the context configuration response message can include at least one of: an identifier of the wireless device; a list of cells that cannot be configured for the wireless device (e.g., based on a CAG of the wireless device and / or the one or more cells; e.g., one of the one or more cells does not support the first CAG); a list of bearers that cannot be configured for the wireless device (e.g., based on a traffic load of the cell and / or the base station distribution unit); RRC parameters (e.g., configuration parameters of physical / MAC / RLC layers) for the wireless device, etc.

[0368] In an example, the base station central unit can determine configuration parameters (e.g., RRC parameters) for the wireless device based on the context configuration response message. In an example, the base station central unit can transmit / send a first RRC message (e.g., an RRC reconfiguration message, an RRC reestablishment message, an RRC setup message, an RRC resume message, etc.) including configuration parameters (e.g., RRC parameters for the wireless device) for one or more cells to the wireless device. In an example, the base station central unit can communicate / transmit / send the first RRC message to the wireless device via the base station distributed unit (e.g., or via a second base station distributed unit). In an example, the base station distributed unit can receive the first RRC message from the first base station central unit. The base station distributed unit can transmit / send / forward the first RRC message to the wireless device. In an example, the first RRC message can include at least one of: cell configuration parameters for one or more cells of the base station distributed unit; bearer configuration parameters for bearers (e.g., for the first NPN, the first network slice, the first session, etc.). In an example, if one or more cells configured for the wireless device are for an inter-base station handover or a secondary base station addition / configuration requested from a second base station, the first RRC message can be transmitted to the wireless device via the second base station (e.g., via a handover request acknowledge message or a node addition / modification request acknowledge message; and / or via a handover command message or an RRC reconfiguration message).

[0369] In an example, the second RRC message can include at least one of: a UE identifier of the wireless device (e.g., TMSI, C-RNTI, IMSI, S-TMSI, IMEI, etc.), a cell identifier of the wireless device (e.g., physical cell identifier PCI, global cell identifier GCI, CGI, cell index, etc.), cell information (e.g., cell index, cell group configuration, radio link failure timer and constants, RLM in-sync / out-of-sync thresholds, synchronization reconfiguration including t304 value, RACH configuration parameters including preamble index and / or RACH resources, carrier frequency information, bandwidth part configuration parameters, beam configuration parameters of SS beams and / or CSI-RS beams, transmission power configuration parameters including p-MAX / p-MgNB / p-SgNB, etc.) for one or more serving cells (e.g., one or more cells) of the wireless device, a bearer identifier of a bearer associated with a service for the wireless device, a logical channel identifier (index) of the bearer, a PDU session identifier (e.g., associated with) of the bearer, a QoS flow identifier of the bearer, network slice information (e.g., S-NSSAI, NSSAI) of a network slice associated with the bearer and / or service, an identifier of the network (e.g., first NPN), an identifier of a CAG (e.g., first CAG) that the wireless device is allowed to access, etc. In an example, the service associated with the bearer can include at least one of voice, ultra-reliable and low latency communication (URLLC), vehicle-to-everything (V2X) (e.g., V2I, V2V, V2P, etc.), emergency service, etc. In an example, the service associated with the bearer can include at least one of delay-tolerant service, Internet of Things (IoT) service,

[0370] In an example, the second RRC message can further include at least one of: an rrc-transaction identifier information element (IE), a radio resource configuration dedicated IE including one or more radio resource configuration parameters, measurement configuration parameters, mobility control information parameters, one or more NAS layer parameters, security parameters, antenna information parameters, secondary cell addition / modification parameters, secondary cell release parameters, WLAN configuration parameters, WLAN offload configuration parameters, LWA configuration parameters, LWIP configuration parameters, RCLWI configuration parameters, sidelink configuration parameters, V2X configuration parameters, uplink transmission power configuration parameters (e.g., p-MAX, p-MeNB, p-SeNB), power control mode information element, secondary cell group configuration parameters, etc.

[0371] In an example, the wireless device can be configured based on the configuration parameters of the first RRC message. The wireless device can transmit / send a second RRC message to the base station and / or the base station central unit, the second RRC message indicating successful completion of configuration of the configuration parameters for the one or more cells. The wireless device can transmit / send the second RRC message via the base station distributed unit (e.g., or via a second base station distributed unit). In an example, the base station distributed unit can receive the second RRC message from the wireless device. The base station distributed unit can transmit / forward the second RRC message to the base station central unit (e.g., via the Fl interface).

[0372] In an example, as Figure 22 and / or Figure 23 indicated, the base station distributed unit can receive, from the base station central unit and based on the cell information, a paging message (e.g., a core network paging and / or a RAN paging) for a second wireless device that is allowed to access the first CAG. The paging message can include at least one of: an identifier of the first CAG; and / or an indication field indicating that the second wireless device is only allowed to access CAG cells (e.g., not allowed to access non-CAG cells and / or normal / open cells).

[0373] In an example, if the second wireless device is a member of the first CAG, the base station central unit can select one or more base station distributed units that serve at least one cell associated with the first CAG and / or a normal cell, a non-CAG cell, or a hybrid cell associated with another CAG for which the wireless device is not a member. In an example, if the second wireless device is a member of the first CAG and is a UE with only one CAT (e.g., the second wireless device is only allowed to access CAG cells), the base station central unit can select one or more base station distributed units that serve at least one cell associated with the first CAG and / or a hybrid cell associated with another CAG for which the wireless device is not a member. If the second wireless device is a non-first CAG member, the base station central unit can select one or more base station distributed units that serve at least one cell that is a normal cell, a non-CAG cell, or a hybrid cell associated with a CAG (e.g., the first CAG). The base station central unit can send the paging message to the selected one or more base station distributed units for paging based on the membership of the wireless device.

[0374] In an example, the base station distributed unit can transmit a paging indication for the second wireless device based on the paging message (e.g., via the cell associated with the first CAG; e.g., via one or more cells). In an example, the base station distributed unit can receive at least one random access preamble from the second wireless device in response to the paging indication (e.g., via the cell associated with the first closed access group; e.g., via one or more cells). The wireless device can camp on the one or more cells based on the one or more cells being associated with the first CAG (e.g., based on a system information block including an identifier of the first CAG).

[0375] In an example, the base station distributed unit can receive / transmit a transport block from / to the wireless device via one or more cells and based on cell configuration parameters. The transport block can be for a first network slice layer associated with the first closed access group. The transport block can be forwarded to the base station distributed unit or can be transmitted by the base station central unit.

[0376] In an example, as shown in Figure 26 , Figure 27 , Figure 28 , Figure 29 , Figure 32 and / or Figure 33 , the base station distributed unit can receive, from the base station central unit, a configuration message including cell information of one or more cells of the base station distributed unit. In an example, the base station central unit can determine the cell information based on cell configuration information received from the AMF and / or the OAM. The cell information can indicate that the one or more cells are associated with the first CAG. The base station distributed unit can configure the one or more cells as the first CAG.

[0377] In an example, the base station distributed unit can transmit / broadcast a system information block including an identifier of the first CAG via the one or more cells. In an example, the base station distributed unit can receive a random access preamble from a wireless device (e.g., a member of the first CAG; or a non-member of the first CAG if the one or more cells are hybrid cells) that is allowed (e.g., via the one or more cells and / or based on the system information block) to access the first closed access group. The configuration message can include the system information block. The base station distributed unit can receive, from the base station central unit based on the cell information, a context configuration request message including cell configuration parameters for the one or more cells of the wireless device. The wireless device can be allowed to access the first CAG. The base station distributed unit can configure the one or more cells for the wireless device based on the cell information and / or the context configuration request message. The base station distributed unit can receive, from the base station central unit based on the cell information, a paging message for a second wireless device. The base station distributed unit can transmit a paging indication (e.g., associated with the paging message) for the wireless device based on the cell information and / or the paging message.

[0378] In an example, as shown in Figure 30 and / or Figure 31 The base station distributed unit can transmit, to the base station central unit, a configuration request message including cell information of one or more cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group. The base station distributed unit can receive a response message to the configuration request message. The base station distributed unit can receive, based on the cell information, a context configuration request message including cell configuration parameters for the one or more cells of the wireless device. The wireless device is allowed to access the first closed access group.

[0379] In an example, the base station distributed unit can include at least one of: a radio link control (RLC) layer function; a medium access control (MAC) layer function; a physical layer function; and / or a portion of the physical layer function. The base station distributed unit can be an integrated access and backhaul (IAB) node. The base station central unit can include at least one of: an RRC function; a service data adaptation protocol (SDAP) layer function; a packet data convergence protocol (PDCP) layer function; an RLC layer function; a MAC layer function; and / or a portion of the physical layer function. The base station central unit can be an IAB donor. The base station can include the base station central unit and the base station distributed unit.

[0380] In an example, the configuration request message can include at least one of: an Fl message, an Fl setup request message; a base station distributed unit configuration update message; and / or a base station central unit configuration update acknowledgement message. In an example, the cell information of the one or more cells can further indicate whether a second wireless device that is not a member of the first closed access group is allowed to access a cell (e.g., a closed cell or a hybrid cell) of the one or more cells. The cell information can include a physical cell identifier (PCI) indicating the cell of the one or more cells. The physical cell identifier can further indicate whether the second wireless device that is not a member of the first closed access group is allowed to access the cell (e.g., a closed cell or a hybrid cell) of the one or more cells. The cell of the one or more cells can be at least one of a closed cell and / or a hybrid cell. In an example, the base station distributed cell can receive, based on the cell information, a second context configuration request message including second cell configuration parameters for the one or more cells of the second wireless device.

[0381] In an example, one or more cells may belong to a first closed access group. One or more cells may further be associated with a second closed access group. The second closed access group may be associated with at least one of: a second non-public network (NPN), a second network slice, and / or a second public land mobile network (PLMN). The first closed access group may be associated with at least one of a first NPN, a first network slice, and / or a first PLMN.

[0382] In an example, the response message may include at least one of the following: an F1 message, an F1 setup response message, and / or a base station distributed unit configuration update confirmation message. The response message may include a system information block (SIB) for at least one of the one or more cells. The system information block may include an identifier of the first closed access group. The base station distributed unit may transmit / broadcast the system information block to the one or more wireless devices (e.g., via a cell (e.g., one or more cells) associated with the first closed access group). The system information block may also include at least one of the following: a network identifier of a first NPN associated with the first closed access group; first network slice selection assistance information (NSSAI) of a first network slice associated with the first closed access group; and / or a first identifier of a first PLMN associated with the first closed access group. The cell information and / or the system information block may also include one or more cell identifiers of one or more cells.

[0383] In an example, the context configuration request message may include at least one of the following: a user equipment (UE) context setup request message; a UE context modification request message; and / or a UE context modification confirmation message. The context configuration request message may include bearer configuration parameters for one or more bearers of a first network slice associated with a first closed access group. The cell configuration parameter may include an information element indicating whether a cell in the one or more cells is configured as a primary cell or a secondary cell for the wireless device. The information element of the cell configuration parameter may include at least one of the following: a cell identifier of the cell; a cell index of the cell; uplink configuration information (e.g., indicating that the cell is configured with one of no uplink, supplementary uplink, and / or normal uplink); and / or a serving cell measurement object (e.g., a measurement object identifier, servingCellMO). In an example, the cell configuration parameter may include at least one cell identifier for at least one candidate special cell for the wireless device. The at least one candidate special cell may be associated with the first closed access group.

[0384] In the example, Figure 20 and / or Figure 21As shown, the base station central unit can receive, from a second base station, a handover request message for a wireless device. The context configuration request message can be based on the handover request message. In an example, as shown, the base station central unit can receive, from the second base station, a secondary node configuration request message for the wireless device. The context configuration request message can be based on the secondary node configuration request message. Figure 20 and / or Figure 21 As shown, the base station central unit can receive, from a second base station, a handover request message for a wireless device. The context configuration request message can be based on the handover request message. In an example, as shown, the base station central unit can receive, from the second base station, a secondary node configuration request message for the wireless device. The context configuration request message can be based on the secondary node configuration request message.

[0385] In an example, the base station distributed unit can receive, based on the cell information, a third context configuration request message including third cell configuration parameters for one or more second cells of a third wireless device. The one or more second cells can be different from the one or more cells. The third wireless device can not be allowed to access the first closed access group. In an example, the wireless device can be a member of the first closed access group.

[0386] In an example, the base station distributed unit can configure, based on the cell configuration parameters, the one or more cells for the wireless device. The base station distributed unit can send, to the base station central unit, a context configuration response message acknowledging context configuration of the wireless device in response to the context configuration request message. The context configuration response message includes at least one of: a UE context setup response message and / or a UE context modification response message.

[0387] In an example, the base station distributed unit can receive, from the base station central unit, a first RRC message (e.g., RRC reconfiguration message, RRC reestablishment message, RRC setup message, RRC resume message, etc.) including configuration parameters of the one or more cells. The base station distributed unit can transmit / transmit / send / forward the first RRC message to the wireless device. In an example, the base station distributed unit can receive, from the wireless device, a second RRC message indicating successful completion of configuration of the configuration parameters of the one or more cells. The base station distributed unit can transmit / send / forward the second RRC message to the base station central unit.

[0388] In an example, the base station central unit can send, to an access and mobility management function (AMF), a second configuration request message including second cell information of a base station including the base station central unit based on the cell information. The second cell information can include an identifier of the first closed access group. The base station central unit can receive, from the AMF, a second response message to the second configuration request message. The second cell information can further indicate whether a second wireless device that is not a member of the first closed access group is allowed to access a cell (e.g., a closed cell or a hybrid cell) associated with the first closed access group. The cell associated with the first closed access group can be a serving cell of the base station. The cell can be one of the one or more cells of the base station distributed unit.

[0389] In an example, a base station distributed unit can receive, from a base station central unit, a paging message (e.g., a core network paging and / or a RAN paging) for a second wireless device allowed to access a first closed access group based on cell information. The paging message can include at least one of: an identifier of the first closed access group; and / or an indication field indicating that the second wireless device is only allowed to access CAG cells (e.g., not allowed to access non-CAG cells and / or normal / open cells). The base station distributed unit can transmit a paging indication for the second wireless device based on the paging message (e.g., via a cell associated with the first closed access group; e.g., via one or more cells).

[0390] In an example, a base station distributed unit can receive / transmit, from / to a wireless device, a transport block via one or more cells and based on cell configuration parameters. The transport block can be for a first network slice layer associated with a first closed access group.

[0391] In an example, a base station distributed unit (e.g., an IAB-node) can select a base station central unit (e.g., an IAB-donor) based on a base station central unit supporting a first closed access group. Transmitting a configuration request message to the base station central unit can be based on selecting the base station central unit (e.g., the IAB-donor) from the base station central unit supporting the first closed access group. The base station distributed unit can receive, from the base station central unit, a system information block including an identifier of the first closed access group. Selecting the base station central unit can be based on the system information block.

[0392] In an example, a base station central unit can receive, from a base station distributed unit, a configuration request message including cell information of one or more cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group. The base station central unit can transmit, to the base station distributed unit, a response message to the configuration request message. The base station central unit can determine cell configuration parameters for the one or more cells of the wireless device based on the cell information. The wireless device can be allowed to access the first closed access group. The base station central unit can transmit, to the base station distributed unit, a context configuration request message including the cell configuration parameters.

[0393] In an example, a base station distributed unit can transmit, to a base station central unit, a configuration request message including cell information of one or more cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group. The base station distributed unit can receive, from the base station central unit, a response message to the configuration request message. The base station distributed unit can receive a paging message for a wireless device based on the cell information. The wireless device can be allowed to access the first closed access group. The base station distributed unit can transmit a paging indication for the wireless device in response to receiving the paging message.

[0394] In an example, a base station central unit can receive, from a base station distributed unit, a configuration request message including cell information of one or more cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group. The base station central unit can transmit, to the base station distributed unit, a response message to the configuration request message. The base station central unit can determine to transmit a paging message to the base station distributed unit for a wireless device based on the cell information. The wireless device can be allowed to access the first closed access group. The base station central unit can transmit the paging message to the base station distributed unit for the wireless device. The base station central unit can receive, from a second base station distributed unit, a second configuration request message including second cell information of one or more second cells (e.g., all serving cells) of the second base station distributed unit. The second cell information can indicate that the one or more second cells are not associated with the first closed access group (e.g., associated with a second closed access group). The base station central unit can determine not to transmit the paging message to the second base station distributed unit for the wireless device based on the second cell information.

[0395] In an example, as shown in Figure 26 、 Figure 28 、 Figure 32 and / or Figure 33 , a base station distributed unit can receive, from a base station central unit, a configuration message including cell information of one or more cells of the base station distributed unit. The cell information can indicate that the one or more cells are associated with a first closed access group. The base station distributed unit can configure the one or more cells as the first closed access group. The base station distributed unit can transmit / broadcast, via the one or more cells, a system information block including an identifier of the first closed access group. In an example, the base station distributed unit can receive a random access preamble from a wireless device that is allowed to access the first closed access group (e.g., via the one or more cells and / or based on the system information block). The configuration message can include the system information block. The base station distributed unit can receive, from the base station central unit, a context configuration request message including cell configuration parameters for the one or more cells of the wireless device based on the cell information. The wireless device can be allowed to access the first closed access group.

[0396] Figure 34is an example diagram of aspects of embodiments of the present disclosure. At 3410, a base station central unit receives, from a base station distributed unit, an indication that one or more cells are associated with a first closed access group. The indication can be a message that includes one or more parameters of the base station distributed unit. The one or more parameters can indicate that the one or more cells are associated with the first closed access group. At 3420, the base station central unit determines, based on the indication, cell configuration parameters for the one or more cells of a wireless device. The wireless device can be a wireless device that is allowed to access the first closed access group. At 3430, the base station central unit sends, to the base station distributed unit, a context configuration message. The context configuration message can include the cell configuration parameters.

[0397] In an example, the base station central unit can receive, from a second base station, a handover request message for the wireless device, the handover request message indicating that the wireless device is allowed to access the first closed access group. The context configuration message can be based on the handover request message.

[0398] In an example, the base station central unit can receive, from the wireless device, a radio resource control (RRC) request message for the wireless device, the RRC request message indicating that the wireless device is allowed to access the first closed access group. The context configuration message can be based on the RRC request message.

[0399] In an example, the base station central unit receives, from an access and mobility management function, a wireless device context configuration request message for the wireless device, the wireless device context configuration request message indicating that the wireless device is allowed to access the first closed access group. The context configuration message is based on the wireless device context configuration request message.

[0400] In an example, the base station central unit includes a base station central unit and a base station distributed unit.

[0401] In an example, the message includes a Fl setup request message. In an example, the message includes a base station distributed unit configuration update message. In an example, the message includes a base station central unit configuration update acknowledgment message.

[0402] In an example, the one or more parameters indicate whether non-first closed access group members are allowed to access the one or more cells.

[0403] In an example, the first closed access group is associated with a first non-public network. In an example, the first closed access group is associated with a first network slice. In an example, the first closed access group is associated with a first public land mobile network (PLMN).

[0404] In an example, the base station central unit transmits, to the base station distributed unit, a response message to the message. In an example, the response message comprises a Fl setup response message. In an example, the response message comprises a base station distributed unit configuration update acknowledgement message.

[0405] In an example, the base station central unit transmits, to the base station distributed unit, a system information block for at least one cell of the one or more cells, the system information block comprising an identifier of the first closed access group.

[0406] In an example, the base station central unit transmits, to the base station distributed unit, a second context configuration message. The second context configuration message can comprise second cell configuration parameters for one or more second cells of the second wireless device. The transmission of the second context configuration message can be based on the message. The one or more second cells can not comprise the one or more cells. The second wireless device can not be allowed to access the first closed access group.

[0407] In an example, the base station central unit receives, from the base station distributed unit, a context configuration response message acknowledging configuration of a context of the wireless device. The reception can be in response to the context configuration message.

[0408] In an example, the base station central unit transmits, to the wireless device via the base station distributed unit, a radio resource control (RRC) message comprising RRC configuration parameters for the one or more cells of the wireless device.

[0409] In an example, the base station central unit transmits, to the base station distributed unit, a paging message for a second wireless device allowed to access the first closed access group based on one or more parameters.

[0410] In an example, the base station central unit transmits, to the base station distributed unit, an identifier of the first closed access group, the identifier indicating that the base station central unit supports the first closed access group.

[0411] Figure 35 is an example diagram of aspects of embodiments of the present disclosure. At 3510, the base station distributed unit transmits, to the base station central unit, an indication that the one or more cells are associated with a first closed access group. The indication can be a list of the one or more cells associated with the first closed access group. The indication can be a message comprising one or more parameters of the base station distributed unit. The one or more parameters can indicate that the one or more cells are associated with the first closed access group. At 3520, the base station distributed unit receives, from the base station central unit, a context configuration message comprising cell configuration parameters for the one or more cells. The one or more cells can be for a wireless device. The wireless device can be allowed to access the first closed access group. The context configuration message can be based on the message.

[0412] In an example, the base station distributed unit includes a radio link control layer. In an example, the base station distributed unit includes a medium access control layer. In an example, the base station distributed unit includes a physical layer. In an example, the base station distributed unit includes a portion of a physical layer. In an example, the base station distributed unit is an integrated access and backhaul node.

[0413] In an example, the base station central unit includes a radio resource control layer. In an example, the base station central unit includes a service data adaptation protocol layer. In an example, the base station central unit includes a packet data convergence protocol layer. In an example, the base station central unit includes a radio link control layer. In an example, the base station central unit includes a medium access control layer. In an example, the base station central unit includes a portion of a physical layer. In an example, the base station central unit is an integrated access and backhaul donor.

[0414] In an example, the base station includes a base station central unit and a base station distributed unit.

[0415] In an example, the message includes a F1 setup request message. In an example, the message includes a base station distributed unit configuration update message. In an example, the message includes a base station central unit configuration update acknowledgement message.

[0416] In an example, the one or more parameters indicate whether non-first closed access group members are allowed to access the one or more cells. In an example, the one or more parameters include a physical cell identifier indicating a cell of the one or more cells. In an example, the one or more parameters include a physical cell identifier indicating whether non-first closed access group members are allowed to access a cell of the one or more cells.

[0417] In an example, the one or more cells are at least one of a closed cell or a hybrid cell. In an example, the one or more cells are further associated with a second closed access group.

[0418] In an example, the first closed access group is associated with a first non-public network. In an example, the first closed access group is associated with a first network slice. In an example, the first closed access group is associated with a first public land mobile network (PLMN).

[0419] In an example, the base station distributed unit receives a response message to the message from the base station central unit. In an example, the response message includes a F1 setup response message. In an example, the response message includes a base station distributed unit configuration update acknowledgement message.

[0420] In an example, the base station distributed unit receives, from the base station central unit, a system information block for at least one of the one or more cells. The system information block can include an identifier of the first closed access group. In an example, the base station distributed unit transmits the system information block to the one or more wireless devices. In an example, the system information block includes a network identifier of a first non-public network associated with the first closed access group. In an example, the system information block includes a first network slice selection assistance information (NSSAI) of a first network slice associated with the first closed access group. In an example, the system information block includes a first identifier of a first public land mobile network (PLMN) associated with the first closed access group.

[0421] In an example, the context configuration message includes a user equipment context setup request message. In an example, the context configuration message includes a user equipment context modification request message. In an example, the context configuration message includes a user equipment context modification confirm message. In an example, the context configuration message includes an identifier of the first closed access group. In an example, the context configuration message includes bearer configuration parameters for one or more bearers of a first network slice associated with the first closed access group.

[0422] In an example, the cell configuration parameters include at least one cell identifier for at least one candidate special cell for the wireless device. The at least one candidate special cell can be associated with the first closed access group.

[0423] In an example, the base station central unit receives, from a second base station, a handover request message for the wireless device, wherein the context configuration message is based on the handover request message.

[0424] In an example, the base station central unit receives, from a second base station, a secondary node configuration request message for the wireless device. The context configuration message can be based on the secondary node configuration request message.

[0425] In an example, the base station distributed unit receives a second context configuration message. The second context configuration message can include second cell configuration parameters for one or more second cells of a second wireless device. The one or more second cells can not include the one or more cells. The second wireless device can not be allowed to access the first closed access group.

[0426] In an example, the wireless device is a member of the first closed access group.

[0427] In an example, the base station distributed unit configures one or more cells of the wireless device based on the cell configuration parameters. In an example, the base station distributed unit sends a context configuration response message to the base station central unit acknowledging configuration of a context of the wireless device in response to the context configuration message. In an example, the context configuration response message comprises a user equipment context setup response message. In an example, the context configuration response message comprises a user equipment context modification response message.

[0428] In an example, the base station distributed unit receives a radio resource control (RRC) message from the base station central unit comprising RRC configuration parameters for one or more cells of the wireless device. In an example, the base station distributed unit sends the RRC message to the wireless device.

[0429] In an example, the base station distributed unit receives an RRC completion message from the wireless device indicating successful completion of configuration of the RRC configuration parameters for the one or more cells. In an example, the base station distributed unit sends the RRC completion message to the base station central unit.

[0430] In an example, the base station central unit sends a second configuration message comprising cell information of a base station to an access and mobility management function based on the one or more parameters, the base station comprising the base station central unit. The cell information can comprise an identifier of a first closed access group. In an example, the base station central unit receives a second configuration response message to the second configuration message.

[0431] In an example, the cell information indicates whether non-members of the first closed access group are allowed to access a cell associated with the first closed access group, the cell being a serving cell of the base station.

[0432] In an example, the base station distributed unit receives a paging message for a second wireless device allowed to access the first closed access group from the base station central unit based on the one or more parameters. In an example, the paging message comprises an identifier of the first closed access group. In an example, the paging message comprises a field indicating whether the second wireless device is allowed to access only closed access group cells. In an example, the base station distributed unit transmits a paging indication of the second wireless device based on the paging message. In an example, transmitting the paging indication comprises transmitting the paging indication via one or more cells associated with the first closed access group.

[0433] In an example, the base station distributed unit receives a transport block from the wireless device via one or more cells based on the cell configuration parameters. In an example, the base station distributed unit transmits the transport block to the wireless device via one or more cells based on the cell configuration parameters.

[0434] In an example, the base station distributed unit selects a base station central unit based on the base station central unit supporting a first closed access group, wherein the message is sent based on the selection.

[0435] In an example, the base station distributed unit receives, from the base station central unit, an identifier of the first closed access group, wherein the base station distributed unit is selected based on the identifier of the first closed access group.

[0436] Figure 36 is an example diagram of aspects of embodiments of the disclosure. At 3610, a base station central unit receives an indication that one or more cells are associated with a first closed access group. The indication can be a list of one or more cells that are associated with the first closed access group. The indication can be a message that includes one or more parameters of a base station distributed unit. The one or more parameters can indicate that the one or more cells are associated with the first closed access group. At 3620, the base station central unit determines to send a paging message to a wireless device. The wireless device can be allowed to access the first closed access group. At 3630, the base station central unit selects the base station distributed unit for transmission of the paging message based on the indication. At 3640, the base station central unit sends the paging message for the wireless device to the base station distributed unit.

[0437] In an example, the base station central unit receives, from an access and mobility management function, a core paging message for a wireless device. The core paging message can indicate a first closed access group. Sending the paging message to the base station distributed unit can be in response to the core paging message.

[0438] In an example, the base station central unit receives, from a second base station distributed unit, a second message that includes one or more second parameters of the second base station distributed unit. The one or more second parameters indicate that any of one or more second cells of the second base station distributed unit are not associated with the first closed access group.

[0439] In an example, the base station central unit determines, based on the second message, not to send a second paging message to the second base station distributed unit for the wireless device. The second paging message can be in response to the core paging message.

[0440] Figure 37 is an example diagram of aspects of embodiments of the disclosure. At 3710, a base station distributed unit sends, to a base station central unit, an indication that one or more cells are associated with a first closed access group. The indication can be a list of one or more cells that are associated with the first closed access group. The indication can be a message that includes one or more parameters of the base station distributed unit. The one or more parameters can indicate that the one or more cells are associated with the first closed access group. At 3720, the base station distributed unit receives, from the base station central unit, a paging message for a wireless device that is allowed to access the first closed access group.

[0441] In an example, the base station distributed unit transmits a paging indication for the wireless device in response to receiving the paging message. In an example, transmitting the paging indication includes transmitting the paging indication via one or more cells associated with the first closed access group.

[0442] In an example, the base station distributed unit receives a response message to the message from the base station central unit.

[0443] In an example, the paging message indicates the first closed access group.

[0444] Figure 38 An example diagram that is an aspect of embodiments of the disclosure. At 3810, the base station distributed unit receives an indication from the base station central unit that one or more cells are associated with a first closed access group. The indication can be a list of one or more cells associated with the first closed access group. The indication can be a message that includes one or more parameters of the base station distributed unit. The one or more parameters can indicate that the one or more cells are associated with the first closed access group. At 3820, the base station distributed unit configures the one or more cells as the first closed access group. At 3830, the base station distributed unit transmits, via the one or more cells, a system information block that includes an identifier of the first closed access group.

[0445] In an example, the message includes a system information block.

[0446] In an example, the base station distributed unit receives a random access preamble from the wireless device via the one or more cells based on the system information block.

[0447] In an example, the wireless device can be allowed to access the first closed access group.

[0448] In an example, the base station distributed unit receives a context configuration message from the base station central unit that includes cell configuration parameters for one or more cells of the wireless device. The cell configuration parameters can be based on the wireless device being allowed to access the first closed access group. The cell configuration parameters can be based on the one or more cells associated with the first closed access group.

[0449] Embodiments can be configured to operate as needed. The disclosed mechanisms can be performed when certain criteria are met, such as in a wireless device, a base station, a radio environment, a network, a combination of the above, etc. Example criteria can be based at least in part on, for example, wireless device or network node configuration, traffic load, initial system setup, packet size, traffic characteristics, a combination of the above, etc. Various example embodiments can be applied when one or more criteria are met. Thus, example embodiments that selectively implement the disclosed protocols can be implemented.

[0450] A base station can communicate with a mix of wireless devices. The wireless devices and / or the base station can support multiple technologies and / or multiple versions of the same technology. The wireless devices can have certain specific capabilities depending on the wireless device category and / or capabilities. The base station can comprise multiple sectors. When the present disclosure refers to a base station communicating with multiple wireless devices, the present disclosure can mean a subset of the total wireless devices in the coverage area. For example, the present disclosure can mean multiple wireless devices having a given capability and in a given sector of the base station of a given LTE or 5G version. The multiple wireless devices in the present disclosure can refer to a selected multiple wireless devices, and / or a subset of the total wireless devices in the coverage area performing the method of the disclosure, etc. There can be multiple base stations or multiple wireless devices in the coverage area that can not comply with the disclosed method, e.g., because these wireless devices or base stations perform based on an old version of the LTE or 5G technology.

[0451] In the present disclosure, “a” and “an” and similar phrases will be interpreted to mean “at least one” and “one or more.” Similarly, any term ending in “(s)” will be interpreted to mean “at least one” and “one or more.” In the present disclosure, the term “may” is interpreted to mean “may, for example.” In other words, the term “may” indicates that the phrase following the term “may” is an example of one of a number of suitable possibilities that can or can not be used in one or more of the various embodiments.

[0452] A is called a subset of B if every element of A is also an element of B. In the present specification, only non-empty sets and subsets are considered. For example, possible subsets of B = {cell1, cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on” (or equivalently “at least based on”) means that the phrase following the term “based on” is an example of one of a number of suitable possibilities that can or can not be used in one or more different embodiments. The phrase “in response to” (or equivalently “at least in response to”) means that the phrase following the term “in response to” is an example of one of a number of suitable possibilities that can or can not be used in one or more different embodiments. The phrase “in dependence of” (or equivalently “at least in dependence of”) means that the phrase following the term “in dependence of” is an example of one of a number of suitable possibilities that can or can not be used in one or more different embodiments. The phrase “employing / using” (or equivalently “at least employing / using”) means that the phrase following the term “employing / using” is an example of one of a number of suitable possibilities that can or can not be used in one or more different embodiments.

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

[0454] In this disclosure, various embodiments are disclosed. Limitations, features, and / or elements from the disclosed exemplary embodiments can be combined to create additional embodiments within the scope of this disclosure.

[0455] In this disclosure, a parameter (or equivalently, a field or information element: IE) can include one or more information objects, and an information object can include one or more other objects. For example, if parameter (IE) N includes parameter (IE) M, and parameter (IE) M includes parameter (IE) K, and parameter (IE) K includes parameter (information element) J. Then, for example, N includes K, and N includes J. In exemplary embodiments, when one or more messages include multiple parameters, it means that a parameter of the multiple parameters is in at least one of the one or more messages, but not necessarily in each of the one or more messages.

[0456] Further, many of the above-described features are described as optional through the use of "may" or the use of parentheses. For brevity and readability, this disclosure does not explicitly recite every permutation of features that can be obtained by selecting from among the described optional features. However, this disclosure should be interpreted to explicitly disclose all such permutations. For example, a system described as having three optional features can be embodied in seven different ways, namely having only one of the three possible features, having any two of the three possible features, or having all three of the three possible features.

[0457] Many of the elements described in the disclosed embodiments can be implemented as modules. A module is defined here as an element that performs a defined function and has a defined interface to other elements. The modules described in this disclosure can be implemented in hardware and / or software (including firmware, resident software, micro-code, etc.) and / or wetware (i.e., humans and / or animals) and can be one of the aforementioned types of modules, or include a combination of them. Furthermore, the modules may, in some embodiments, be implemented as software modules being loaded into one or more general purpose hardware computers or microcontrollers and caused to perform specified functions when carried out. Thus, the modules described herein may

[0458] The disclosure of this patent document incorporates material that is copyright protected. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.

[0459] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Numerous changes to the embodiments can be made in accordance with the disclosure herein without departing from the spirit or scope of the disclosure. Indeed, the disclosure can encompass a variety of forms that fall within the scope of the disclosure. Thus, the present embodiments should not be limited by any of the above described exemplary embodiments.

[0460] Further, it should be appreciated that any figures which highlight the functionality and advantages are presented for illustrative purposes only. The disclosed architecture is sufficiently flexible and configuration to allow for utilization in ways not presented herein.

[0461] Furthermore, the purpose of the abstract of the disclosure is to enable the U.S. Patent and Trademark Office and the public generally, especially scientists, engineers and practitioners in the art who are not familiar with patent or legal terms or terminology to determine quickly from a cursory inspection the nature and essence of the technical disclosure of the application. The abstract of the present disclosure is not intended to be limiting in any way.

[0462] Finally, it is intended that only claims which recite a purely structural limitation, i.e., a limitation solely in terms of means-plus-function, are to be construed in accordance with 35 U.S.C. 112, paragraph 6. To the extent that any limitation in a claim is intentionally functional, or is characterized as a means-plus-function, it is intended that the claim be construed under 35 U.S.C. 112, paragraph 6.

Claims

1. A method for managing cell information, comprising: Sending, by the base station central unit to the first base station distributed unit, a first indication that the first cell is associated with a first non-public network (NPN); receiving, by the base station central unit, first cell information from an access and mobility management function (AMF), the first cell information including a second indication that the wireless device supports a first NPN; sending, by the base station central unit, a first configuration request message to the first base station distributed unit, for configuring the first cell for the wireless device supporting the first NPN, wherein the first configuration request message includes cell configuration parameters of the first cell for the wireless device based on the first cell information received from the AMF; receiving, by the base station central unit, a second configuration request message from a second base station distributed unit, where the second configuration request message includes second cell information of a second cell of the second base station distributed unit, wherein the second cell information indicates that the second cell is not associated with the first NPN; as well as The base station central unit determines, based on the second cell information, that the second cell of the second base station distributed unit not be configured for the wireless device.

2. The method according to claim 1, wherein Sending the first indication further includes sending a cell identifier of the first cell together with the first indication to the first base station distributed unit in a configuration message, where the configuration message includes the cell identifier and the first indication.

3. The method according to claim 2, wherein: The configuration message indicates that the cell is associated with the first NPN.

4. The method of claim 1, further comprising receiving, by the base station central unit from the first base station distributed unit, a response indicating the configuration of the first cell.

5. The method according to claim 4, wherein The response confirms the configuration of the first cell for the wireless device. 6 . The method of claim 1 , further comprising sending, by the base station central unit, a radio resource control (RRC) message including configuration parameters of the first cell.

7. The method according to claim 6, wherein: The transmission is to the wireless device.

8. The method according to claim 6, wherein: The sending is via the first base station distributed unit.

9. The method of claim 1, wherein the first configuration request message is based on the wireless device supporting the first NPN.

10. The method according to claim 1, wherein The first cell is a serving cell.

11. A base station central unit for managing cell information, comprising: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the base station central unit to: sending a first indication to a first base station distributed unit that the first cell is associated with a first non-public network (NPN); receiving first cell information from an access and mobility management function (AMF), the first cell information including a second indication that the wireless device supports the first NPN; and sending, by the base station central unit, a first configuration request message to the first base station distributed unit, for configuring the first cell for the wireless device supporting the first NPN, wherein the first configuration request message includes cell configuration parameters of the first cell for the wireless device based on the first cell information received from the AMF; receiving, by the base station central unit, a second configuration request message from a second base station distributed unit, where the second configuration request message includes second cell information of a second cell of the second base station distributed unit, wherein the second cell information indicates that the second cell is not associated with the first NPN; as well as The base station central unit determines, based on the second cell information, that the second cell of the second base station distributed unit not be configured for the wireless device.

12. The base station central unit according to claim 11, wherein: The cell identifier of the first cell and the first indication are sent to the first base station distributed unit in a configuration message, where the configuration message includes the cell identifier and the first indication.

13. The base station central unit according to claim 12, wherein: The configuration message indicates that the first cell is associated with the first NPN.

14. The base station central unit of claim 11, further comprising receiving, by the base station central unit, a response from the first base station distributed unit indicating the configuration of the first cell.

15. The base station central unit according to claim 14, wherein: The response confirms the configuration of the first cell for the wireless device.

16. The base station central unit of claim 11, further comprising sending, by the base station central unit, a radio resource control (RRC) message including configuration parameters of the first cell.

17. The base station central unit according to claim 16, wherein: The transmission is to the wireless device.

18. The base station central unit according to claim 16, wherein: The sending is via the first base station distributed unit.

19. The base station central unit of claim 11, wherein the first configuration request message is based on the wireless device supporting the first NPN.

20. A system for managing cell information, comprising: A base station central unit comprising one or more first processors and a first memory storing instructions that, when executed by the one or more first processors, cause the base station central unit to: sending a first indication to a first base station distributed unit that the first cell is associated with a first non-public network (NPN); receiving a first cell message from an access and mobility management function (AMF), the first cell message including a second indication that the wireless device supports the first NPN; and sending, by the base station central unit, a first configuration request message to the first base station distributed unit, for configuring the first cell for the wireless device supporting the first NPN, wherein the first configuration request message includes cell configuration parameters of the first cell for the wireless device based on the first cell information received from the AMF; receiving, by the base station central unit, a second configuration request message from a second base station distributed unit, where the second configuration request message includes second cell information of a second cell of the second base station distributed unit, wherein the second cell information indicates that the second cell is not associated with the first NPN; as well as determining, by the base station central unit based on the second cell information, not to configure the second cell of the second base station distributed unit for the wireless device; the first base station distributed unit, wherein the first base station distributed unit comprises one or more second processors and a second memory storing instructions, the instructions, when executed by the one or more second processors, causing the first base station distributed unit to receive the first indication and the first configuration request message for configuring the first cell; as well as The second base station distributed unit, wherein the second base station distributed unit includes one or more third processors and a third memory storing instructions, and the instructions, when executed by the one or more third processors, cause the second base station distributed unit to send the second configuration request message to the base station central unit.

Images