Base station network sharing configuration

Abstract

A base station distributed unit receives a first message from a first base station central unit. The first message includes a first PLMN identifier of a first mobile phone system network (PLMN) of a first PLMN that includes the first base station central unit. The base station distributed unit receives a second message from a second base station central unit. The second message includes a second PLMN identifier of a second PLMN. The base station distributed unit transmits at least one system information block. At least one system information block includes a first PLMN identifier and a second PLMN identifier.

Description

Technology Field

[0001] 관련 출원의 교차 참조

[0002] This application claims priority to U.S. Provisional Application No. 62 / 683,373 filed June 11, 2018, and U.S. Provisional Application No. 62 / 696,912 filed July 12, 2018, the entirety of which is incorporated herein by reference. Brief explanation of the drawing

[0003] Some examples of the various embodiments of the present disclosure are described herein with reference to the drawings. FIG. 1 is a drawing of an exemplary RAN architecture according to one aspect of one embodiment of the present disclosure. FIG. 2a is a drawing of an exemplary user plane protocol stack according to one aspect of one embodiment of the present disclosure. FIG. 2b is a drawing of an exemplary control plane protocol stack according to one aspect of one embodiment of the present disclosure. FIG. 3 is a drawing of an exemplary wireless device and two base stations according to an aspect of one embodiment of the present disclosure. FIGS. 4a, FIGS. 4b, FIGS. 4c and FIGS. 4d are exemplary drawings for uplink and downlink signal transmission according to one aspect of one embodiment of the present disclosure. FIG. 5a is a diagram of exemplary uplink channel mapping and exemplary uplink physical layer signals according to one aspect of one embodiment of the present disclosure. FIG. 5b is a diagram of exemplary downlink channel mapping and exemplary downlink physical layer signals according to one aspect of one embodiment of the present disclosure. FIG. 6 is a drawing illustrating an exemplary frame structure according to one aspect of one embodiment of the present disclosure. FIGS. 7a and 7b are drawings illustrating exemplary sets of OFDM subcarriers according to one aspect of one embodiment of the present disclosure. FIG. 8 is a drawing illustrating exemplary OFDM radio resources according to one aspect of one embodiment of the present disclosure. FIG. 9a is a diagram illustrating exemplary CSI-RS and / or SS block transmission in a multi-beam system. FIG. 9b is a drawing illustrating an exemplary downlink beam management procedure according to one aspect of one embodiment of the present disclosure. FIG. 10 is an exemplary drawing of constructed BWPs according to one aspect of one embodiment of the present disclosure. FIGS. 11a and FIGS. 11b are drawings of an exemplary multiple connection according to one aspect of one embodiment of the present disclosure. FIG. 12 is a drawing of an exemplary optional access procedure according to one aspect of one embodiment of the present disclosure. FIG. 13 is a structure of exemplary MAC entities according to one aspect of one embodiment of the present disclosure. FIG. 14 is a drawing of an exemplary RAN architecture according to one aspect of one embodiment of the present disclosure. FIG. 15 is a drawing of exemplary RRC states according to one aspect of one embodiment of the present disclosure. FIG. 16 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 17 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 18 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 19 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 20 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 21 is an exemplary diagram illustrating a legacy base station shared network architecture. FIG. 22 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 23 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 24 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 25 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 26 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 27 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 28 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 29 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 30 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 31 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 32 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 33 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 34 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 35 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 36 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 37 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 38 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 39 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 40 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 41 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 42 is an exemplary drawing of one aspect of one embodiment of the present disclosure. FIG. 43 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 44 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 45 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 46 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 47 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 48 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 49 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 50 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 51 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 52 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 53 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 54 is a drawing of one aspect of an exemplary embodiment of the present disclosure. FIG. 55 is a drawing of one aspect of an exemplary embodiment of the present disclosure. Specific details for implementing the invention

[0004] The embodiments of the present disclosure enable the operation of wireless systems. The embodiments of the technology disclosed herein may be used in the field of technology for multi-carrier communication systems. More specifically, the embodiments of the technology disclosed herein may be related to wireless access technologies in multi-carrier communication systems.

[0005] The following abbreviations are used throughout this disclosure:

[0006]

[0007]

[0008]

[0009]

[0010]

[0011] Exemplary embodiments of the present disclosure may be implemented using various physical layer modulation and transmission mechanisms. Exemplary transmission mechanisms may include, but are not limited to, Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Time Division Multiple Access (TDMA), Wavelet technology, etc. Hybrid transmission mechanisms such as TDMA / CDMA and OFDM / CDMA may also be used. Various modulation schemes may be applied for signal transmission at the physical layer. Examples of modulation schemes include, but are not limited to, phase, amplitude, code, and combinations thereof. Exemplary wireless transmission methods may implement Orthogonal Amplitude Modulation (QAM), Orthogonal Phase Shift Keying (QPSK), 16-QAM, 64-QAM, 256-QAM, etc. using Binary Phase Shift Keying (BPSK). Physical layer wireless transmission may be enhanced by dynamically or semi-dynamically changing the modulation and coding schemes according to transmission requirements and wireless conditions.

[0012] FIG. 1 is an exemplary radio access network (RAN) architecture according to one aspect of one embodiment of the present disclosure. As illustrated in this example, a RAN node may be a gNB (e.g., 120A, 120B) providing NR user plane and control plane protocol terminations toward a first radio device (e.g., 110A). In one example, a RAN node may be a next-generation eNB (e.g., 124A, 124B) providing evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminations toward a second radio device (e.g., 110B). The first radio device may communicate with the gNB via a Uu interface. The second radio device may communicate with the ng-eNB via a Uu interface. In the present disclosure, the radio devices (110A and 110B) are structurally similar to the radio device (110). The base station (120A and / or 120B) may be structurally similar to the base station (120). The base station (120) may include at least one of a gNB (e.g., 122A and / or 122B), an ng-eNB (e.g., 124A and / or 124B), etc.

[0013] A gNB or ng-eNB can host functions such as wireless resource management and scheduling, IP header compression, encryption and integrity protection of data, selection of Access and Mobility Management Functions (AMF) upon connection of User Equipment (UE), routing of user plane data and control plane data, scheduling and transmission of paging messages (originating from AMF), scheduling and transmission of system broadcast information (originating from AMF or Operation and Maintenance (O&M)), measurement and measurement reporting configuration, transport-level packet marking on the uplink, session management, support for network slicing, Quality of Service (QoS) flow management and mapping to data wireless bearers, support for UEs in the RRC_INACTIVE state, distribution functions for Non-Access Layer (NAS) messages, RAN sharing, and duplex coupling or tight interoperability between NR and E-UTRA.

[0014] In one example, one or more gNBs and / or one or more ng-eNBs may be interconnected using an Xn interface. A gNB or ng-eNB may be connected to a 5G core network (5GC) via an NG interface. In one example, the 5GC may include one or more AMF / UPF (User Plan Function) functions (e.g., 130A or 130B). A gNB or ng-eNB may be connected to a UPF using an NG-User Plane (NG-U) interface. The NG-U interface may provide delivery of User Plane Protocol Data Units (PDUs) between a RAN node and a UPF (e.g., non-guaranteed delivery). A gNB or ng-eNB may be connected to an AMF using an NG-Control Plane (NG-C) interface. The NG-C interface can provide, for example, NG interface management, UE context management, UE mobility management, transmission of NAS messages, paging, PDU session management, configuration transmission and / or alert message transmission, combinations thereof.

[0015] In one example, the UPF may host functions such as an anchor point for mobility within / between Radio Access Technology (RAT) (where applicable), an external PDU session point for interconnection to a data network, packet routing and forwarding, the user plane portion for packet inspection and policy rule enforcement, traffic usage reporting, an uplink classifier supporting routing traffic flows to a data network, a branch point supporting multi-hom PDU sessions, QoS handling for the user plane (e.g., packet filtering), gating, uplink (UL) / downlink (DL) rate enforcement, uplink traffic validation (e.g., Service Data Flow (SDF) for QoS flow mapping), downlink packet buffering, and / or downlink data notification triggering.

[0016] In one example, the AMF may host functions such as NAS signaling termination, NAS signaling security, access layer (AS) security control, signaling between core network (CN) nodes for mobility between 3GPP access networks, reachability of idle mode UEs (e.g., control and execution of paging retransmission), registration area management, support for in-system and inter-system mobility, access authorization including checking roaming rights, mobility management control (subscription and policy), support for network slicing and / or session management functions (SMF).

[0017] FIG. 2a is an exemplary user plane protocol stack in which the Service Data Adaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data Conversion Protocol (PDCP) (e.g., 212 and 222), Wireless Link Control (RLC) (e.g., 213 and 223), and Media Access Control (MAC) (e.g., 214 and 224) lower layers and the Physical (PHY) (e.g., 215 and 225) layer can be terminated at the network side at a wireless device (e.g., 110) and a gNB (e.g., 120). In one example, the PHY layer provides transport services to higher layers (e.g., MAC, RRC, etc.). In one example, the services and functions of the MAC lower layer may include mapping between logical channels and transport channels, multiplexing / demultiplexing of MAC service data units (SDUs) to / from one or different logical channels in / of a transport block (TB) transmitted to / from the PHY layer, reporting of scheduling information, error correction through Hybrid Automatic Retransmission Request (HARQ) (e.g., one HARQ entity per carrier in the case of Carrier Bundle (CA)), prioritization among UEs using dynamic scheduling, and prioritization among the logical channels of a single UE using logical channel prioritization. A MAC entity may support one or more numerologies and / or transport timings. In one example, mapping limits of logical channel prioritization may control the numerologies and / or transport timings available to the logical channel. In one example, the RLC lower layer may support transport modes of transparent mode (TM), unacknowledged mode (UM), and acknowledged mode (AM). RLC configuration may be provided for each logical channel that does not depend on numerology and / or transmission time interval (TTI) duration. In one example, an Automatic Retransmission Request (ARQ) may operate at any numerology and / or TTI duration in which the logical channel is configured.For example, services and functions of the PDCP layer for the user plane may include sequence numbering, header compression and decompression, transmission of user data, re-request and duplication detection, PDCP PDU routing (e.g., for split bearers), PDCP SDU retransmission, encryption, decryption and integrity protection, PDCP SDU discarding, PDCP re-establishment and data recovery for RLC AM, and / or duplication of PDCP PDUs. In one example, services and functions of SDAP may include mapping between QoS flows and data wireless bearers. In one example, services and functions of SDAP may include mapping of Quality of Service Indicators (QFIs) of DL and UL packets. In one example, protocol entities of SDAP may be configured for individual PDU sessions.

[0018] FIG. 2b is an exemplary control plane protocol stack in which PDCP (e.g., 233 and 242), RLC (e.g., 234 and 243), MAC (e.g., 235 and 244) sublayers and PHY (e.g., 236 and 245) layers can be terminated at a wireless device (e.g., 110) and gNB (e.g., 120) on the network side and can perform the services and functions described above. In one example, RRC (e.g., 232 and 241) can be terminated at a wireless device and gNB on the network side. In one example, the services and functions of the RRC may include broadcasting system information related to the AS and NAS, paging initiated by the 5GC or RAN, establishing, maintaining, and releasing an RRC connection between the UE and the RAN, security functions including key management, establishing, configuring, maintaining, and releasing a signaling radio bearer (SRB) and a data radio bearer (DRB), mobility functions, QoS management functions, reporting of UE measurements and control of reports, detection of and recovery from radio link failures, and / or transmission of NAS messages from the UE to the NAS / from the NAS to the UE. In one example, the NAS control protocol (e.g., 231 and 251) may be terminated at the network side at the radio device and AMF (e.g., 130) and may perform functions such as authentication, mobility management between the UE and the AMF for 3GPP access and non-3GPP access, and session management between the UE and the SMF for 3GPP access and non-3GPP access.

[0019] In one example, a base station may configure multiple logical channels for a wireless device. A logical channel within the multiple logical channels may correspond to a wireless bearer, and the wireless bearer may be associated with QoS requirements. In one example, a base station may configure a logical channel mapped to one or more TTI / numericologies in a plurality of TTI / numericologies. The wireless device may receive downlink control information (DCI) through a physical layer downlink control channel (PDCCH) indicating an uplink acknowledgment. In one example, the uplink acknowledgment may be for a first TTI / numericology and may indicate uplink resources for the transmission of a transmission block. The base station may configure each logical channel within the multiple logical channels having one or more parameters to be used by a logical channel prioritization procedure at the MAC layer of the wireless device. One or more parameters may include priority, a prioritized data transmission rate (bit rate), etc. A logical channel within the multiple logical channels may correspond to one or more buffers containing data associated with the corresponding logical channel. A logical channel prioritization procedure may allocate uplink resources to multiple logical channels and / or one or more first logical channels within one or more MAC control elements (CEs). One or more first logical channels may be mapped to a first TTI / numerology. The MAC layer in a wireless device may multiplex one or more MAC CEs and / or one or more MAC SDUs (e.g., logical channels) within a MAC PDU (e.g., a transmission block). In one example, the MAC PDU may include a MAC header containing multiple MAC sub-headers. The MAC sub-headers of the multiple MAC sub-headers may correspond to a MAC CE or MAC SUD (logical channel) within one or more MAC CEs and / or one or more MAC SDUs.In one example, a MAC CE or a logical channel may be configured with a logical channel identifier (LCID). In one example, the LCID for the logical channel or MAC CE may be fixed or pre-configured. In one example, the LCID for the logical channel or MAC CE may be configured for a wireless device by a base station. A MAC sub-header corresponding to a MAC CE or MAC SDU may include an LCID associated with the MAC CE or MAC SDU.

[0020] In one example, a base station may enable and / or disable and / or affect one or more processes in a wireless device (e.g., set values ​​of one or more parameters of one or more processes, or start and / or stop of one or more timers of one or more processes) by using one or more MAC commands. One or more MAC commands may include one or more MAC control elements. In one example, one or more processes may include enabling and / or disabling PDCP packet duplication for one or more wireless bearers. The base station may transmit a MAC CE containing one or more fields, the values ​​of which may include enabling and / or disabling PDCP duplication for one or more wireless bearers. In one example, one or more processes may include transmitting Channel State Information (CSI) in one or more cells. The base station may transmit one or more MAC CEs indicating enabling and / or disabling CSI transmission in one or more cells. In one example, one or more processes may include enabling or disabling one or more auxiliary cells. In one example, the base station may transmit a MAC CE indicating the activation or deactivation of one or more auxiliary cells. In one example, the base station may transmit one or more MAC CEs indicating the start and / or stop of one or more discontinuous receive (DRX) timers in a wireless device. In one example, the base station may transmit one or more MAC CEs indicating one or more timing advance values ​​for one or more timing advance groups (TAGs).

[0021] FIG. 3 is a block diagram of base stations (base station 1 (120A) and base station 2 (120B)) and a wireless device (110). The wireless device may be referred to as a UE. The base station may be referred to as an NB, eNB, gNB, and / or ng-eNB. In one example, the wireless device and / or base station may operate as a relay node. Base station 1 (120A) may include 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) that can be stored in non-transient memory (322A) and executed by at least one processor (321A). Base station 2 (120B) may include at least one communication interface (320B), at least one processor (321B), and at least one set of at least one program code instructions (323B) stored in non-transient memory (322B) and executable by at least one processor (321B).

[0022] A base station may include multiple sectors, for example, 1, 2, 3, 4, or 6 sectors. A base station may include multiple cells, for example, a range of 1 to 50 or more cells. Cells may be classified, for example, as primary cells or auxiliary cells. In Radio Resource Control (RRC) connection establishment / re-establishment / handover, one serving cell may provide NAS (Non-Connection Layer) mobility information (e.g., Tracked Area Identifier (TAI)). In RRC connection re-establishment / handover, one serving cell may provide a security input. This cell may be referred to as a primary cell (PCell). In the downlink, the carrier corresponding to the PCell may be a DL primary element carrier (PCC), while in the uplink, the carrier may be a UL PCC. Depending on the capabilities of the radio device, auxiliary cells (SCells) may be configured to form a set of serving cells together with the PCell. The carrier wave corresponding to SCell in the downlink may be a downlink auxiliary component carrier wave (DL SCC), whereas the carrier wave in the uplink may be an uplink auxiliary component carrier wave (UL SCC). SCell may or may not have an uplink carrier wave.

[0023] A cell comprising a downlink carrier and optionally an uplink carrier may be assigned a physical layer cell ID and a cell index. A carrier (downlink or uplink) may belong to a single cell. The cell ID or cell index may also identify the downlink carrier or uplink carrier of a cell (depending on the context in which it is used). In the present disclosure, the cell ID may be referred to as the carrier ID, and the cell index may be referred to as the carrier index. In one embodiment, the physical layer cell ID or cell index may be assigned to a single cell. The cell ID may be determined using a synchronization signal transmitted over the downlink carrier. The cell index may be determined using RRC messages. For example, if the present disclosure refers to a first physical layer cell ID for a first downlink carrier, the present disclosure may mean that the first physical layer cell ID is for a cell comprising the first downlink carrier. The same concept may apply, for example, to carrier activation. Where the first carrier wave is shown to be activated in the present disclosure, the present specification may likewise mean that the cell containing the first carrier wave is activated.

[0024] A base station may transmit one or more messages (e.g., RRC messages) containing multiple configuration parameters for one or more cells to a wireless device. One or more cells may include at least one primary cell and at least one auxiliary cell. In one example, the RRC message may be broadcast or unicast to the wireless device. In one example, the configuration parameters may include common parameters and dedicated parameters.

[0025] Services and / or functions of the RRC lower layer may include at least one of establishing, maintaining, and / or releasing an RRC connection between a radio device and an NG-RAN, which may include at least one of broadcasting system information related to AS and NAS, paging initiated by 5GC and / or NG-RAN, adding, modifying, and releasing carrier bundles, or adding, modifying, and / or releasing duplex connections within the NR or between E-UTRA and the NR. Services and / or functions of the RRC lower layer may further include security functions including key management, mobility functions which may include at least one of establishing, configuring, maintaining, and / or releasing a signaling radio bearer (SRB) and / or data radio bearer (DRB), handover (e.g., movement within the NR or movement between RATs), and context transfer, or at least one of controlling radio device cell selection and deselection and cell selection and deselection. The services and / or functions of the RRC lower layer may further include at least one of QoS management functions, wireless device measurement configuration / reporting, detection and / or recovery of wireless link failures, or transmission of NAS messages from a wireless device to a core network entity (e.g., AMF, Mobility Management Entity (MME)) or from a core network entity to a wireless device.

[0026] The RRC sublayer may support an RRC_Idle state, an RRC_Inactive state, and / or an RRC_Connected state for a wireless device. In the RRC_Idle state, the wireless device may perform at least one of selecting a mobile phone system network (PLMN), receiving broadcasted system information, selecting / deselecting a cell, paging for mobile terminated data initiated by 5GC, paging for a mobile terminated data area managed by 5GC, or DRX for CN paging configured via NAS. In the RRC_Inactive state, the wireless device may perform at least one of receiving broadcasted system information, selecting / reselecting a cell, RAN / CN paging initiated by NG-RAN / 5GC, RAN-based notification area (RNA) managed by NG-RAN, or DRX for RAN / CN configured by NG-RAN / NAS. In the RRC_Idle state of the wireless device, the base station (e.g., NG-RAN) may maintain a 5GC-NG-RAN connection (both C / U planes) for the wireless device and / or store the UE AS context for the wireless device. In the RRC_Connected state of the wireless device, the base station (e.g., NG-RAN) may perform at least one of establishing a 5GC-NG-RAN connection (both C / U planes) for the wireless device, storing the UE AS context for the wireless device, transmitting / receiving unicast data to / from the wireless device, or performing network-control moves based on measurement results received from the wireless device. In the RRC_Connected state of the wireless device, the NG-RAN may know the cell to which the wireless device belongs.

[0027] System information (SI) may be divided into a minimum SI and other SIs. The minimum SI may be broadcast periodically. The minimum SI may include basic information required for initial connection, and information for acquiring any other SI that is periodically broadcast or provided according to demand, i.e., scheduling information. The other SI may be broadcast or provided in a dedicated manner, triggered by the network or by a request from a wireless device. The minimum SI consists of different messages (e.g., MasterInformationBlock and SystemInformationBlockType1 It can be transmitted through two different downlink channels using ). The other SI is SystemInformationBlockType2 It can be transmitted via. For a wireless device in the RRC_Connected state, dedicated RRC signaling may be used for requests and transmissions from other SIs. For a wireless device in the RRC_Idle state and / or RRC_Inactive state, the request may trigger a random access procedure.

[0028] A wireless device may report its wireless access performance information, which may be static. A base station may request the wireless device to report performances based on band information. Where permitted by the network, a request for temporary performance limitation (e.g., due to hardware sharing, interference, or overheating) may be transmitted by the wireless device to convey to the base station the limited availability of some performances. The base station may acknowledge or reject the request. Temporary performance limitation may be transparent to the 5GC (e.g., static performance may be stored in the 5GC).

[0029] When CA is configured, the wireless device may have an RRC connection with the network. During the RRC connection establishment / re-establishment / handover procedure, one serving cell may provide NAS mobility information, and during the RRC connection re-establishment / handover, one serving cell may provide security input. This cell may be referred to as a PCell. Depending on the capabilities of the wireless device, SCells may be configured to form a set of serving cells together with the PCell. A configured set of serving cells for the wireless device may include one PCell and one or more SCells.

[0030] The reconfiguration, addition, and removal of SCells can be performed by the RRC. During a handover within the NR, the RRC may add, remove, or reconfigure SCells for use in conjunction with the target PCell. When adding a new SCell, dedicated RRC signaling may be used to transmit all necessary system information of the SCell, meaning that in connection mode, wireless devices may not need to obtain broadcast system information directly from the SCells.

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

[0032] The RRC connection establishment (or re-establish, resume) procedure may be intended to establish (or re-establish, resume) an RRC connection. The RRC connection establishment procedure may include SRB1 establishment. The RRC connection establishment procedure may be used to transmit initial NAS-specific information / messages from a wireless device to the E-UTRAN. RRCConnectionReestablishment The message can be used to re-establish SRB1.

[0033] The measurement reporting procedure may be for transmitting measurement results from a wireless device to an NG-RAN. The wireless device may initiate the measurement reporting procedure after security activation is complete. Measurement report messages may be used to transmit measurement results.

[0034] The wireless device (110) may include at least one communication interface (310) (e.g., a wireless modem, an antenna, etc.), at least one processor (314), and at least one set of program code instructions (316) that can be stored in non-transient memory (315) and executed by at least one processor (314). The wireless device (110) may further include 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 GPS (global positioning system) chipset (318), and other peripherals (319).

[0035] The processor (314) of the wireless device (110), the processor (321A) of base station 1 (120A), and / or the processor (321B) of base station 2 (120B) may include at least one of a general-purpose processor, a digital signal processor (DSP), a controller, a microcontroller, an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) and / or other programmable logic device, discrete gate and / or transistor logic, discrete hardware components, etc. The processor (314) of the wireless device (110), the processor (321A) of base station 1 (120A), and / or the processor (321B) of base station 2 (120B) may perform at least one of signal encoding / processing, data processing, power control, input / output processing, and / or any other function that enables the wireless device (110), base station 1 (120A), and / or base station 2 (120B) to operate in a wireless environment.

[0036] The processor (314) of the wireless device (110) may be connected to a speaker / microphone (311), a keypad (312), and / or a display / touchpad (313). The processor (314) may receive user input data from the speaker / microphone (311), the keypad (312), and / or the display / touchpad (313), and / or provide user output data therefrom. The processor (314) of the wireless device (110) may receive power from a power source (317) and / or may be configured to distribute power to other components within the wireless device (110). The power source (317) may include at least one of one or more dry cells, solar cells, fuel cells, etc. The processor (314) may be connected to a GPS chipset (318). The GPS chipset (318) may be configured to provide geographic location information of the wireless device (110).

[0037] The processor (314) of the wireless device (110) may be further connected to other peripheral devices (319) that may include one or more software and / or hardware modules providing additional features and / or functions. For example, the peripheral devices (319) may include at least one of an accelerometer, a satellite transceiver, a digital camera, a USB (universal serial bus) port, a hands-free headset, a frequency modulation (FM) radio unit, a media player, an internet browser, etc.

[0038] The communication interface (320A) of base station 1 (120A) and / or the communication interface (320B) of base station 2 (120B) may each be configured to communicate with the communication interface (310) of the wireless device (110) via a wireless link (330A) and / or a wireless link (330B). In one example, the communication interface (320A) of base station 1 (120A) may communicate with the communication interface (320B) of base station 2, other RANs, and core network nodes.

[0039] The wireless link (330A) and / or the wireless link (330B) may include at least one of a bidirectional link and / or a unidirectional link. The communication interface (310) of the wireless device (110) may be configured to communicate with the communication interface (320A) of base station 1 (120A) and / or the communication interface (320B) of base station 2 (120B). Base station 1 (120A) and the wireless device (110) and / or base station 2 (120B) and the wireless device (110) may each be configured to transmit and receive transmission blocks through the wireless link (330A) and / or the wireless link (330B). The wireless link (330A) and / or the wireless link (330B) may utilize at least one frequency carrier wave. According to some of the various aspects of the embodiments, transceiver(s) may be used. The transceiver may be a device comprising both a transmitter and a receiver. Transceivers can be used in devices such as wireless devices, base stations, relay nodes, etc. Exemplary embodiments of wireless technology implemented in communication interfaces (310, 320A, 320B) and wireless links (330A, 330B) are described in FIG. 4a, 4b, 4c, 4d, 6, 7a, 7b, 8 and the related text.

[0040] In one example, other nodes within a wireless network (e.g., AMF, UPF, SMF, etc.) may include one or more communication interfaces, one or more processors, and memory storage instructions.

[0041] A node (e.g., a wireless device, base station, AMF, SMF, UPF, server, switch, antenna, etc.) may include one or more processors and memory storage instructions that, when executed by said one or more processors, cause the node to perform specific processes and / or functions. Exemplary embodiments may enable single-carrier and / or multi-carrier communication operations. Other exemplary embodiments may include a non-transient type (tangible) computer-readable medium comprising instructions executable by one or more processors to enable single-carrier and / or multi-carrier communication operations. Yet another exemplary embodiment may include an article of manufacture comprising a non-transient type computer-readable machine-accessible medium in which instructions are encoded to enable programmable hardware to enable the node to perform single-carrier and / or multi-carrier communication operations. The node may include a processor, memory, interface, etc.

[0042] The interface may include at least one of a hardware interface, a firmware interface, a software interface, and / or a combination thereof. The hardware interface may include electronic devices such as connectors, wires, and / or drivers and amplifiers. The software interface may include code stored in a memory device to implement protocol(s), protocol layers, communication drivers, device drivers, and / or combinations thereof. The firmware interface may include a combination of embedded hardware and code that is stored in a memory device and / or communicates with a memory device to implement connections, electronic device operations, protocol(s), protocol layers, communication drivers, device drivers, hardware operations, and / or combinations thereof.

[0043] FIGS. 4a, 4b, 4c, and 4d are exemplary drawings for uplink and downlink signal transmission according to one aspect of one embodiment of the present disclosure. FIG. 4a illustrates an exemplary uplink transmitter for at least one physical layer channel. A baseband signal representing a physical layer uplink shared channel may perform one or more functions. The one or more functions may include at least one of: scrambling; modulation of scrambling bits to generate complex-value symbols; mapping of complex-value modulation symbols to one or more transport layers; transform precoding to generate complex-value symbols; precoding of complex-value symbols; mapping of precoded complex-value symbols to resource elements; generation of a complex-value time-domain single carrier frequency division multiple access (SC-FDMA) signal or CP-OFDM signal for an antenna port. In one example, when conversion precoding is enabled, an SC-FDMA signal for uplink transmission may be generated. In one example, when conversion precoding is not enabled, a CP-OFDM signal for uplink transmission may be generated by FIG. 4a. These functions are illustrated as examples, and it can be anticipated that other mechanisms may be implemented in various embodiments.

[0044] An exemplary structure for modulating and up-converting a complex-value SC-FDMA or CP-OFDM baseband signal for an antenna port and / or a complex-value physical layer random access channel (PRACH) baseband signal to the carrier frequency is illustrated in FIG. 4b. Filtering may be used before transmission.

[0045] An exemplary structure for downlink transmission is illustrated in FIG. 4c. A baseband signal representing a downlink physical layer channel may perform one or more functions. The one or more functions may include: scrambling of encoded bits within a codeword to be transmitted over the physical layer channel; modulation of scrambled bits to generate complex-value modulation symbols; mapping of complex-value modulation symbols to one or more transport layers; precoding of complex-value modulation symbols over the transport layer for antenna ports; mapping of complex-value modulation symbols to resource elements for antenna ports; generation of complex-value time-domain OFDM signals for antenna ports; etc. These functions are illustrated as examples, and it can be anticipated that other mechanisms may be implemented in various embodiments.

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

[0047] An exemplary modulation and up-conversion of a complex-value OFDM baseband signal to the carrier frequency for an antenna port is illustrated in FIG. 4d. Filtering may be used before transmission.

[0048] FIG. 5a is a diagram of exemplary uplink channel mapping and exemplary uplink physical layer signals. FIG. 5b is a diagram of exemplary downlink channel mapping and downlink physical layer signals. In one example, the physical layer may provide one or more information transmission services to the MAC and / or one or more upper layers. For example, the physical layer may provide one or more information transmission services to the MAC through one or more transmission channels. An information transmission service may indicate how data with what characteristics is transmitted through a wireless interface.

[0049] In an exemplary embodiment, the wireless network may include one or more downlink and / or uplink transmission channels. For example, the drawing in FIG. 5a illustrates exemplary uplink transmission channels including an uplink shared channel (UL-SCH) (501) and a random access channel (RACH) (502). The drawing in FIG. 5b illustrates exemplary downlink transmission channels including a downlink shared channel (DL-SCH) (511), a paging channel (PCH) (512), and a broadcast channel (BCH) (513). The transmission channels may be mapped to one or more corresponding physical layer channels. For example, UL-SCH (501) may be mapped to a physical layer uplink shared channel (PUSCH) (503). RACH (502) may be mapped to PRACH (505). DL-SCH (511) and PCH (512) can be mapped to a physical layer downlink shared channel (PDSCH) (514). BCH (513) can be mapped to a physical layer broadcast channel (PBCH) (516).

[0050] One or more physical layer channels may not have corresponding transmission channels. The one or more physical layer channels may be used for uplink control information (UCI) (509) and / or downlink control information (DCI) (517). For example, a physical layer uplink control channel (PUCCH) (504) may carry UCI (509) from the UE to the base station. For example, a physical layer downlink control channel (PDCCH) (515) may carry DCI (517) from the base station to the UE. NR may support UCI (509) multiplexing in PUSCH (503) when UCI (509) and PUSCH (503) transmissions can be matched in at least one slot. UCI (509) may include at least one of CSI, acknowledgment (ACK) / negation acknowledgment (NACK), and / or scheduling request. The DCI (517) on the PDCCH (515) may represent at least one of one or more downlink assignments and / or one or more uplink scheduling approvals.

[0051] In the uplink, the UE may transmit one or more reference signals (RS) to the base station. For example, one or more RSs may 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 the downlink, the base station may transmit one or more RSs to the UE (e.g., unicast, multicast, and / or broadcast). For example, one or more RSs may 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).

[0052] In one example, the UE may transmit one or more uplink DM-RS (506) to a base station for channel estimation, for example, for coherent demodulation of one or more uplink physical layer channels (e.g., PUSCH (503) and / or PUCCH (504)). For example, the UE may transmit at least one uplink DM-RS (506) to a base station using PUSCH (503) and / or PUCCH (504), and at least one uplink DM-RS (506) may span the same frequency range as a corresponding physical layer channel. In one example, the base station may configure the UE to have one or more uplink DM-RS configurations. At least one DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped across one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). One or more additional uplink DM-RSs may be configured to transmit on one or more symbols of PUSCH and / or PUCCH. A base station may semi-statistically configure a UE to have a maximum number of front-loaded DM-RS symbols for PUSCH and / or PUCCH. For example, a UE may schedule single-symbol DM-RSs and / or dual-symbol DM-RSs based on the maximum number of front-loaded DM-RS symbols, and a base station may configure the UE to have one or more additional uplink DM-RSs for PUSCH and / or PUCCH. An NR network may support a common DM-RS structure for DL ​​and UL, for example, at least for CP-OFDM, and the DM-RS locations, DM-RS patterns, and / or scrambling sequences may be the same or different.

[0053] In one example, whether an uplink PT-RS (507) exists may be determined by the RRC configuration. For example, the presence of the uplink PT-RS may be configured specifically for the UE. For example, the presence and / or pattern of the uplink PT-RS (507) in a scheduled resource may be configured specifically for the UE by a combination of RRC signaling and one or more parameters used for other purposes indicated by the DCI (e.g., modulation and encoding scheme (MCS)). When configured, the dynamic presence of the uplink PT-RS (507) may be associated with at least one DCI parameter including the MCS. The wireless network may support multiple uplink PT-RS densities defined in the time / frequency domain. If present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be fewer than the number of DM-RS ports within the scheduled resources. For example, the uplink PT-RS (507) may be limited within the scheduled time / frequency duration for the UE.

[0054] In one example, the UE may transmit an SRS (508) to the base station for channel state estimation that supports uplink channel-dependent scheduling and / or link adaptation. For example, the SRS (508) transmitted by the UE may cause the base station to estimate the uplink channel state at one or more different frequencies. The base station scheduler may use the uplink channel state to allocate one or more blocks of good quality resources for uplink PUSCH transmissions from the UE. The base station may semi-statistically configure the UE to have one or more sets of SRS resources. In the case of SRS resource sets, the base station may configure the UE to have one or more SRS resources. SRS resource set applicability may be configured by upper layer (e.g., RRC) parameters. For example, if the upper layer parameter indicates beam management, the SRS resources of each of one or more SRS resource sets may be transmitted simultaneously. The UE may transmit one or more SRS resources within different SRS resource sets simultaneously. An NR network may support non-periodic, periodic, and / or semi-persistent SRS transmission. A UE may transmit SRS resources based on one or more trigger types, and said one or more trigger types may include upper layer signaling (e.g., RRC) and / or one or more DCI formats (e.g., at least one DCI format) may be used for the UE to select at least one of one or more configured sets of SRS resources. SRS trigger type 0 may refer to an SRS triggered based on upper layer signaling. SRS trigger type 1 may refer to an SRS triggered based on one or more DCI formats.In one example, when PUSCH (503) and SRS (508) are transmitted in the same slot, the UE may be configured to transmit SRS (508) after the transmission of PUSCH (503) and the corresponding uplink DM-RS (506).

[0055] In one example, the base station may semi-statistically configure the UE to have one or more SRS configuration parameters representing at least one of the following: an SRS resource configuration identifier, the number of SRS ports, the time-domain behavior of the SRS resource configuration (e.g., indication of periodic, semi-continuous, or non-periodic SRS), periodicity and / or offset at the slot (mini-slot, and / or subframe) level for periodic and / or non-periodic SRS resources, the number of OFDM symbols in the SRS resources, the start OFDM symbol of the SRS resources, SRS bandwidth, frequency hopping bandwidth, cyclic shift, and / or SRS sequence ID.

[0056] In one example, in the time domain, the SS / PBCH block may contain one or more OFDM symbols within the SS / PBCH block (e.g., four OFDM symbols numbered in increasing order from 0 to 3). The SS / PBCH block may contain a PSS / SSS (521) and a PBCH (516). In one example, in the frequency domain, the SS / PBCH block may contain one or more adjacent subcarriers within the SS / PBCH block (e.g., 240 adjacent subcarriers having subcarriers numbered in increasing order from 0 to 239). For example, the PSS / SSS (521) may occupy one OFDM symbol and 127 subcarriers. For example, the PBCH (516) may span three OFDM symbols and 240 subcarriers. A UE may assume that one or more SS / PBCH blocks transmitted using the same block index may be quasi-co-located with respect to, for example, Doppler spread, Doppler shift, mean gain, mean delay, and spatial Rx parameters. A UE may not assume that other SS / PBCH block transmissions are quasi-co-located. The periodicity of an SS / PBCH block may be configured by a radio network (e.g., by RRC signaling), and one or more time locations in which an SS / PBCH block may be transmitted may be determined by a subcarrier interval. In one example, a UE may assume a band-specific subcarrier interval for an SS / PBCH block, unless the radio network configures the UE to assume a different subcarrier interval.

[0057] In one example, the downlink CSI-RS (522) may be used for the UE to obtain channel state information. The wireless network may support periodic, non-periodic, and / or semi-continuous transmission of the downlink CSI-RS (522). For example, a base station may semi-statistically configure and / or reconfigure the UE to have periodic transmission of the downlink CSI-RS (522). The configured CSI-RS resources may be enabled and / or disabled. In the case of semi-continuous transmission, the enabling and / or disabling of the CSI-RS resources may be triggered dynamically. In one example, the CSI-RS configuration may include at least one parameter indicating the number of antenna ports. For example, the base station may configure the UE to have 32 ports. The base station may semi-statistically configure the UE to have one or more sets of CSI-RS resources. One or more CSI-RS resources may be allocated from one or more sets of CSI-RS resources to one or more UEs. For example, a base station may semi-statistically configure one or more parameters representing CSI-RS resource mapping, e.g., the time-domain location of one or more CSI-RS resources, the bandwidth of the CSI-RS resources, and / or periodicity. In one example, the UE may be configured to use the same OFDM symbols for the downlink CSI-RS (522) and the coreset if the downlink CSG-RS (522) and the control resource set (coreset) are spatially located in the same similar location and the resource elements associated with the downlink CSI-RS (522) are outside the PRB configured for the coreset.In one example, the UE may be configured to use the same OFDM symbols for the downlink CSI-RS (522) and SSB / PBCH when the downlink CSI-RS (522) and SSB / PBCH are spatially similarly located in the same position and the resource elements associated with the downlink CSI-RS (522) are outside the PRB configured for the SSB / PBCH.

[0058] In one example, the UE may transmit one or more downlink DM-RSs (523) for channel estimation to the base station for coherent demodulation of one or more downlink physical layer channels (e.g., PDSCH (514)). For example, the wireless network may support one or more variable and / or configurable DM-RS patterns for data demodulation. At least one downlink DM-RS configuration may support a front-loaded DM-RS pattern. A front-loaded DM-RS may be mapped across one or more OFDM symbols (e.g., one or two adjacent OFDM symbols). The base station may semi-statistically configure the UE to have a maximum number of front-loaded DM-RS symbols for the PDSCH (514). For example, the DM-RS configuration may support one or more DM-RS ports. For example, in the case of single-user MIMO, the DM-RS configuration may support at least eight orthogonal downlink DM-RS ports. For example, in the case of multi-user MIMO, the DM-RS configuration may support 12 orthogonal downlink DM-RS ports. The radio network may support a common DM-RS structure for DL ​​and UL, for example, at least for CP-OFDM, and the DM-RS locations, DM-RS patterns, and / or scrambling sequences may be the same or different.

[0059] In one example, whether a downlink PT-RS (524) exists may be determined by the RRC configuration. For example, the presence of the downlink PT-RS (524) may be configured specifically for the UE. For example, the presence and / or pattern of the downlink PT-RS (524) in a scheduled resource may be configured specifically for the UE by a combination of RRC signaling and association with one or more parameters used for other purposes (e.g., MCS) that may be indicated by DCI. When configured, the dynamic presence of the downlink PT-RS (524) may be associated with one or more DCI parameters, including at least the MCS. The wireless network may support multiple PT-RS densities defined in the time / frequency domain. If present, the frequency domain density may be associated with at least one configuration of the scheduled bandwidth. The UE may assume the same precoding for the DMRS port and the PT-RS port. The number of PT-RS ports may be fewer than the number of DM-RS ports within the scheduled resources. For example, the downlink PT-RS (524) may be limited to the scheduled time / frequency duration for the UE.

[0060] FIG. 6 is a drawing illustrating an exemplary frame structure for a carrier wave according to one aspect of one embodiment of the present disclosure. A multi-carrier OFDM communication system may include one or more carrier waves, for example, 1 to 32 carrier waves in the case of a carrier bundle, or 1 to 64 carrier waves in the case of a duplex connection. Different radio frame structures (e.g., for FDD and TDD duplex mechanisms) may be supported. FIG. 6 illustrates an exemplary frame structure. Downlink and uplink transmissions may consist of radio frames (601). In this example, the radio frame duration is 10 ms. In this example, the 10 ms radio frame (601) may be divided into 10 subframes (602) of equal size having a duration of 1 ms. The subframe(s) may include one or more different slots (e.g., slots (603 and 605)) depending on the subcarrier spacing and / or CP length. For example, subframes having subcarrier intervals of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, and 480 kHz may each contain 1, 2, 4, 8, 16, and 32 slots, respectively. In FIG. 6, a subframe may be divided into two slots (603) of the same size having a duration of 0.5 ms. For example, 10 subframes may be used for downlink transmission, and 10 subframes may be used for uplink transmissions within a 10 ms interval. Uplink and downlink transmissions may be separated in the frequency domain. The slot(s) may contain a plurality of OFDM symbols (604). The number of OFDM symbols (604) in a slot (605) may depend on the periodic prefix code length. For example, the slots can be 14 OFDM symbols for the same subcarrier spacing of up to 480 kHz with normal CP.The slots may be 12 OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP. The slots may include a downlink, an uplink, or a partial downlink and a partial uplink, etc.

[0061] FIG. 7a is a drawing illustrating an exemplary set of OFDM subcarriers according to one aspect of one embodiment of the present disclosure. In this example, a gNB may communicate with a wireless device having a carrier wave having, for example, a channel bandwidth (700). In the drawing, arrow(s) may illustrate subcarriers in a multi-carrier OFDM system. The OFDM system may use technologies such as OFDM technology, SC-FDMA technology, etc. In one example, an arrow (701) illustrates subcarrier transmission information symbols. In one example, the subcarrier spacing (702) between two adjacent subcarriers within the carrier wave may be any one of 15 KHz, 30 KHz, 60 KHz, 120 KHz, 240 KHz, etc. In one example, different subcarrier spacings may correspond to different transmission numerologies. In one example, the transmission numerology may include at least a numerology index, a value of the subcarrier spacing, and a type of periodic prefix code (CP). In one example, the gNB may transmit to and receive from the UE over a plurality of subcarriers (703) within the carrier wave. In one example, the bandwidth (transmission bandwidth) occupied by the plurality of subcarriers (703) may be smaller than the channel bandwidth (700) of the carrier wave due to guard bands (704 and 705). In one example, the guard bands (704 and 705) may be used to reduce interference to and from one or more neighboring carrier waves. The plurality of subcarriers (transmission bandwidth) within the carrier wave may depend on the channel bandwidth and subcarrier spacing of the carrier wave. For example, the transmission bandwidth for a carrier wave having a 20 MHz channel bandwidth and a 15 KHz subcarrier spacing can be in the number of 1024 subcarriers.

[0062] In one example, the gNB and the wireless device can communicate with multiple CCs when configured as CA. In one example, if CA is supported, different element carriers may have different bandwidths and / or subcarrier spacings. In one example, the gNB may transmit a first type of service to the UE over a first element carrier. The gNB may transmit a second type of service to the UE over a second element carrier. Different types of services may have different service requirements (e.g., data transmission rate, latency, reliability), which may be suitable for transmission over different element carriers having different subcarrier spacings and / or bandwidths. FIG. 7b illustrates an exemplary embodiment. The first element carrier may include a first number of subcarriers (706) having a first subcarrier spacing (709). The second element carrier may include a second number of subcarriers (707) having a second subcarrier spacing (710). The third element carrier may include a third number of subcarriers (708) having a third subcarrier interval (711). In a multi-carrier OFDM communication system, the carriers may be adjacent carriers, non-adjacent carriers, or a combination of adjacent carriers and non-adjacent carriers.

[0063] FIG. 8 is a diagram illustrating OFDM radio resources according to one aspect of one embodiment of the present disclosure. In one example, the carrier may have a transmission bandwidth (801). In one example, there may be a resource grid within the structure of the frequency domain (802) and the time domain (803). In one example, the resource grid may include a first number of OFDM symbols within a subframe and a second number of resource blocks starting from a common resource block indicated by transmission numerology and higher-level signaling for the carrier (e.g., RRC signaling). In one example, in the resource grid, a resource unit identified by a subcarrier index and a symbol index may be a resource element (805). In one example, the subframe may include a first number of OFDM symbols (807) that depend on the numerology associated with the carrier. For example, if the subcarrier spacing of the numerology of the carrier wave is 15 kHz, the subframe may have 14 OFDM symbols for the carrier wave. If the subcarrier spacing of the numerology is 30 kHz, the subframe may have 28 OFDM symbols. If the subcarrier spacing of the numerology is 60 kHz, the subframe may have 56 OFDM symbols, etc. In one example, the second number of resource blocks included in the resource grid of the carrier wave may vary depending on the bandwidth and numerology of the carrier wave.

[0064] As illustrated in FIG. 8, a resource block (806) may include 12 subcarriers. In one example, a plurality of resource blocks may be grouped into a resource block group (RBG) (804). For example, the size of the RBG 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 the carrier partial bandwidth. In one example, the carrier may include a plurality of partial bandwidths. The first partial bandwidth of the carrier may have a frequency position and / or bandwidth different from the second partial bandwidth of the carrier.

[0065] In one example, a gNB may transmit downlink control information to a wireless device, including downlink or uplink resource block allocation. A base station may transmit to or receive from a wireless device data packets (e.g., transmission blocks) that are scheduled and transmitted through one or more resource blocks and one or more slots according to parameters in the downlink control information and / or RRC message(s). In one example, a start symbol for the first slot of one or more slots may be indicated to the wireless device. In one example, a gNB may transmit to or receive from a wireless device data packets that are scheduled for one or more RBGs and one or more slots.

[0066] In one example, the gNB may transmit downlink control information, including downlink allocation, to a wireless device via one or more PDCCHs. Downlink allocation may include parameters representing at least HARQ information related to modulation and encoding formats, resource allocation, and / or DL-SCH. In one example, resource allocation may include parameters for resource block allocation and / or slot allocation. In one example, the gNB may dynamically allocate resources to the wireless device via a Cell-to-Radio Network Temporary Identifier (C-RNTI) on one or more PDCCHs. The wireless device may monitor one or more PDCCHs to find available allocations when downlink reception is enabled. If the wireless device successfully detects one or more PDCCHs, it may receive one or more downlink data packages on one or more PDSCHs scheduled by the one or more PDCCHs.

[0067] In one example, the gNB may allocate configuration scheduling (CS) resources for downlink transmission to a wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS acknowledgment. The gNB may transmit a DCI via a PDCCH addressed to a configuration scheduling-RNTI (CS-RNTI) that enables the CS resources. The DCI may include parameters indicating that the downlink acknowledgment is a CS acknowledgment. The CS acknowledgment may be implicitly reused according to the periodicity defined by one or more RRC messages until it is disabled.

[0068] In one example, the gNB may transmit downlink control information, including uplink acknowledgments, to a wireless device via one or more PDCCHs. The uplink acknowledgments may include parameters indicating at least HARQ information related to modulation and encoding formats, resource allocation, and / or UL-SCH. In one example, resource allocation may include parameters for resource block allocation and / or slot allocation. In one example, the gNB may dynamically allocate resources to the wireless device via C-RNTI on one or more PDCCHs. The wireless device may monitor one or more PDCCHs to find available resource allocations. If the wireless device successfully detects one or more PDCCHs, it may transmit one or more uplink data packages via one or more PUSCHs scheduled by the one or more PDCCHs.

[0069] In one example, the gNB may allocate CS resources for uplink data transmission to a wireless device. The gNB may transmit one or more RRC messages indicating the periodicity of the CS acknowledgment. The gNB may transmit a DCI via a PDCCH addressed to a CS-RNTI that enables the CS resources. The DCI may include parameters indicating that the uplink acknowledgment is a CS acknowledgment. The CS acknowledgment may be implicitly reused according to the periodicity defined by one or more RRC messages until it is disabled.

[0070] In one example, the base station may transmit DCI / control signaling via PDCCH. The DCI may take one of a plurality of formats. The DCI may include downlink and / or uplink scheduling information (e.g., resource allocation information, HARQ-related parameters, MCS), requests for CSI (e.g., non-periodic CQI reports), requests for SRS, uplink power control commands for one or more cells, one or more timing information (e.g., TB transmit / receive timing, HARQ feedback timing, etc.). In one example, the DCI may indicate an uplink acknowledgment including transmission parameters for one or more transmit blocks. In one example, the DCI may indicate a downlink allocation indicating parameters for receiving one or more transmit blocks. In one example, the DCI may be used by the base station to initiate contention-free random access from a wireless device. In one example, the base station may transmit a DCI including a Slot Format Indicator (SFI) that notifies a slot format. In one example, the base station may transmit a DCI containing a pre-emption indicator notifying PRB(s) and / or OFDM symbol(s), wherein the UE may assume that no transmission is intended for the UE. In one example, the base station may transmit a DCI for group power control of PUCCH, PUSCH, or SRS. In one example, the DCI may correspond to an RNTI. In one example, the radio device may acquire an RNTI in response to completing an initial access (e.g., C-RNTI). For example, the base station may configure an RNTI for the radio (e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, TPC-SRS-RNTI).For example, a wireless device can calculate an RNTI (for example, the wireless device can calculate an RA-RNTI based on the resources used for transmitting the preamble). In one example, the RNTI may have a pre-configured value (e.g., P-RNTI or SI-RNTI). In one example, the wireless device may monitor a group common search space that can be used by a base station to transmit DCIs intended for a group of UEs. In one example, the group common DCI may correspond to an RNTI configured commonly for a group of UEs. In one example, the wireless device may monitor a UE-specific search space. In one example, the UE-specific DCI may correspond to an RNTI configured for the wireless device.

[0071] The NR system may support single-beam operation and / or multi-beam operation. In multi-beam operation, the base station may perform downlink beam sweeping to provide coverage for common control channels and / or downlink SS blocks, which may include at least PSS, SSS, and / or PBCH. A radio device may measure the quality of a beam pair link using one or more RSs. 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 may be used as RSs to measure the quality of the beam pair link. The quality of the beam pair link may be defined by a Reference Signal Received Power (RSRP) value, a Reference Signal Received Quality (RSRQ) value, and / or CSI values ​​measured for the RS resources. The base station may indicate whether the RS resources used to measure the beam pair link quality are quasi-co-located (QCLed) similarly to the DM-RSs of the control channels. The RS resources and DM-RS of the control channel may be referred to as QCLed if the channel characteristics from transmission via RS to the wireless device and the channel characteristics from transmission on the control channel to the wireless device are similar or identical under configured criteria. In multi-beam operation, the wireless device may perform uplink beam sweeping to connect to a cell.

[0072] In one example, a wireless device may be configured to monitor a PDCCH simultaneously on one or more beam pair links depending on the capabilities of the wireless device. This can increase robustness against beam pair link blocking. A base station may transmit one or more messages to configure the wireless device to monitor a PDCCH on one or more beam pair links of different PDCCH OFDM symbols. For example, the base station may transmit upper layer signaling (e.g., RRC signaling) or MAC CE containing parameters related to the Rx beam settings of the wireless device for monitoring a PDCCH on one or more beam pair links. The base station may transmit an indication of a spatial QCL assumption between the DL RS antenna port(s) (e.g., a cell-specific CSI-RS, or a wireless device-specific CSI-RS, or an SS block, or a PBCH with or without DM-RSs of the PBCH) and the DL RS antenna port(s) for demodulation of the DL control channel. Signaling for beam indication for PDCCH may be MAC CE signaling, or RRC signaling, or DCI signaling, or transparent and / or implicit methods to the specification, and combinations of these signaling methods.

[0073] In the case of receiving a unicast DL data channel, the base station may indicate spatial QCL parameters between the DL RS antenna port(s) and the DM-RS antenna port(s) of the DL data channel. The base station may transmit a DCI (e.g., downlink acknowledgments) containing information indicating the RS antenna port(s). This information may indicate the RS antenna port(s) that can be QCL-ed with the DM-RS antenna port(s). Different sets of DM-RS antenna port(s) for the DL data channel may be indicated as being QCL-ed with different sets of RS antenna port(s).

[0074] FIG. 9a is an example of beam sweeping in a DL channel. In the RRC_INACTIVE or RRC_IDLE state, the wireless device may assume that SS blocks form an SS burst (940) and an SS burst set (950). The SS burst set (950) may have a given periodicity. For example, in a multi-beam operation, the base station (120) may transmit SS blocks to multiple beams that together form an SS burst (940). One or more SS blocks may be transmitted in a single beam. When multiple SS bursts (940) are transmitted in multiple beams, the SS bursts may together form an SS burst set (950).

[0075] A wireless device may further use CSI-RS in multi-beam operation to estimate the beam quality of links between the wireless device and the base station. A beam may be associated with CSI-RS. For example, the wireless device may report a beam index, such as one indicated in the CRI for downlink beam selection and associated with the RSRP value of the beam, based on RSRP measurements for CSI-RS. CSI-RS may be transmitted over a CSI-RS resource comprising at least one of one or more antenna ports and one or more time or frequency radio resources. The CSI-RS resource may be configured in a manner specific to the cell by common RRC signaling, or in a manner specific to the wireless device by dedicated RRC signaling and / or L1 / L2 signaling. Multiple wireless devices covered by a single cell may measure a CSI-RS resource specific to the cell. Some of the dedicated wireless devices covered by a single cell may measure a CSI-RS resource specific to the wireless device.

[0076] CSI-RS resources may be transmitted periodically, or transmitted using non-periodic transmission, multi-shot, or semi-continuous transmission. For example, in the periodic transmission of FIG. 9a, the base station (120) may periodically transmit the configured CSI-RS resources (940) using periodicity configured in the time domain. In non-periodic transmission, the configured CSI-RS resources may be transmitted in a dedicated time slot. In multi-shot or semi-continuous transmission, the configured CSI-RS resources may be transmitted within a configured period. The beam used for CSI-RS transmission may have a different beam width than the beam used for SS-block transmission.

[0077] FIG. 9b is an example of a beam management procedure in an exemplary NR network. A base station (120) and / or a wireless device (110) may perform a downlink L1 / L2 beam management procedure. One or more of the following downlink L1 / L2 beam management procedures may be performed within one or more wireless devices (110) and one or more base stations (120). In one example, the P-1 procedure (910) may be used to enable the wireless device (110) to measure one or more Tx beams associated with the base station (120) to support the selection of a first set of transmit (Tx) beams associated with the base station (120) and a first set of Rx beam(s) associated with the wireless device (110). For beamforming at the base station (120), the base station (120) may sweep a set of different Tx beams. For beamforming in the wireless device (110), the wireless device (110) may sweep different sets of Rx beams. In one example, the P-2 procedure (920) may be used to enable the wireless device (110) to measure one or more Tx beams associated with the base station (120) to possibly change a first set of Tx beams associated with the base station (120). The P-2 procedure (920) may be performed for a set of beams possibly smaller than in the P-1 procedure (910) for beam adjustment. The P-2 procedure (920) may be a special case of the P-1 procedure (910). In one example, the P-3 procedure (930) may be used to enable the wireless device (110) to measure at least one Tx beam associated with the base station (120) to change a first set of Rx beams associated with the wireless device (110).

[0078] A wireless device (110) may transmit one or more beam management reports to a base station (120). In one or more beam management reports, the wireless device (110) may indicate some beam pair quality parameters, including at least one or more beam identifications, RSRP, and a precoding matrix indicator (PMI) / channel quality indicator (CQI) / rank indicator (RI) of some of the configured beams. Based on one or more beam management reports, the base station (120) may transmit a signal to the wireless device (110) indicating that one or more beam pair links are one or more serving beams. The base station (120) may transmit PDCCH and PDSCH for the wireless device (110) using one or more serving beams.

[0079] In an exemplary embodiment, the NR network may support Bandwidth Adaptation (BA). In one example, the receive and / or transmit bandwidth configured by a UE utilizing BA may not be large. For example, the receive and / or transmit bandwidth may not be as large as the cell bandwidth. The receive and / or transmit bandwidth may be adjustable. For example, the UE may change the receive and / or transmit bandwidth to reduce it during periods of low activity, for example, to save power. For example, the UE may change the position of the receive and / or transmit bandwidth in the frequency domain to increase scheduling flexibility, for example. For example, the UE may change the subcarrier spacing to allow for different services, for example.

[0080] In an exemplary embodiment, a portion of the cell's total cell bandwidth may be referred to as partial bandwidth (BWP). A base station may configure a UE to have one or more BWPs to achieve BA. For example, the base station may indicate to the UE which of the one or more (configured) BWPs is the active BWP.

[0081] FIG. 10 is an exemplary drawing of three BWPs consisting of BWP1 (1010 and 1050) with a width of 40 MHz and a subcarrier spacing of 15 kHz, BWP2 (1020 and 1040) with a width of 10 MHz and a subcarrier spacing of 15 kHz, and BWP3 (1030) with a width of 20 MHz and a subcarrier spacing of 60 kHz.

[0082] For example, a UE configured to operate on one or more BWPs of a cell may be configured by one or more upper layers for the cell (e.g., RRC layer) to have at least one parameter (DL-BWP) to have a set of one or more BWPs (e.g., up to 4 BWPs) for the UE to receive in the DL bandwidth (DL BWP set) and at least one parameter for the cell (UL-BWP) to have a set of one or more BWPs (e.g., up to 4 BWPs) for the UE to transmit in the UL bandwidth (UL BWP set).

[0083] To enable BA on a PCell, the base station may configure the UE to have one or more pairs of UL and DL BWP. (e.g., for CA) To enable BA on a SCell, the base station may configure the UE to have at least one DL BWP (e.g., there may be no UL at all).

[0084] In one example, the initial active DL BWP may be defined by at least one of the location and number of adjacent PRBs for a set of control resources for at least one common search space, subcarrier spacing, or periodic prefix. To operate on a PCell, one or more upper-level parameters may represent at least one initial UL BWP for a random access procedure. If the UE is configured to have an auxiliary carrier on the main cell, the UE may be configured to have an initial BWP for a random access procedure on the auxiliary carrier.

[0085] In one example, for unpaired spectrum operation, the UE can expect that the center frequency for the DL BWP may be the same as the center frequency for the UL BWP.

[0086] For example, for a DL BWP or UL BWP of a set of one or more DL BWPs or one or more UL BWPs, the base station may semi-statistically configure a UE for a cell to have one or more parameters representing at least one of the following: subcarrier spacing, periodic cyclic code, number of adjacent PRBs, index of a set of one or more DL BWPs and / or one or more UL BWPs, link between a DL BWP and a UL BWP of one of the configured set of DL BWPs and UL BWPs, DCI detection for PDSCH receive timing, PDSCH receive for HARQ-ACK transmit timing value, DCI detection for PUSCH transmit timing value, offset of the first PRB of each DL bandwidth or UL bandwidth for the first PRB of the bandwidth.

[0087] In one example, for a DL BWP of a set of one or more DL BWPs on a PCell, the base station may configure the UE to have one or more sets of control resources for at least one type of common search space and / or search space specific to one UE. For example, the base station may not configure the UE without a common search space on the PCell or on the PSCell in an active DL BWP.

[0088] For a set of one or more UL BWPs, the base station may configure the UE to have one or more resource sets for one or more PUCCH transmissions.

[0089] In one example, if the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active DL BWP among a configured set of DL BWPs for receiving one or more DLs. If the DCI includes a BWP indicator field, the BWP indicator field value may indicate an active UL BWP among a configured set of UL BWPs for transmitting one or more ULs.

[0090] In one example, for a PCell, the base station may semi-statistically configure the UE to have a default DL BWP among the configured DL BWPs. If the UE is not provided with a default DL BWP, the default BWP may be the initial active DL BWP.

[0091] In one example, the base station may configure the UE to have a timer value for the PCell. For example, in the case of paired spectrum operation, when the UE detects a DCI indicating an active DL BWP other than the default DL BWP, or in the case of unpaired spectrum operation, when the UE detects a DCI indicating an active DL BWP or UL BWP other than the default DL BWP or UL BWP, the UE may initiate a timer referred to as the BWP inactive timer. In the case of paired spectrum operation or unpaired spectrum operation, if the UE does not detect a DCI during that period, the UE may increment the timer by a period of a first value (e.g., the first value may be 1 millisecond or 0.5 milliseconds). In one example, the timer may expire when the timer equals the timer value. The UE may switch from the active DL BWP to the default DL BWP when the timer expires.

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

[0093] In one example, when a UE is configured for an auxiliary cell having a default DL BWP and a timer value among the configured DL BWPs, the UE procedures on the auxiliary cell may be the same as those on the main cell using the timer value for the auxiliary cell and the default DL BWP for the auxiliary cell.

[0094] In one example, when a base station configures a UE to have a first active DL BWP and a first active UL BWP on an auxiliary cell or carrier wave, the UE may use the indicated DL BWP and the indicated UL BWP as the respective first active DL BWP and first active UL BWP on the auxiliary cell or carrier wave.

[0095] FIGS. 11a and 11b illustrate packet flow using multiple connections (e.g., dual connection, multiple connection, tight coupling, etc.). FIG. 11a is an exemplary diagram of the protocol structure of a wireless device (110) (e.g., UE) having CA and / or multiple connections according to one aspect of an embodiment. FIG. 11b is an exemplary diagram of the protocol structure of a plurality of base stations having CA and / or multiple connections according to one aspect of an embodiment. The plurality of base stations may include a master node, MN (1130) (e.g., master node, master base station, master gNB, master eNB, etc.) and an auxiliary node, SN (1150) (e.g., auxiliary node, auxiliary base station, auxiliary eNB, etc.). The master node (1130) and the auxiliary node (1150) may be coupled to communicate with the wireless device (110).

[0096] When multiple connections are configured for a wireless device (110), the wireless device (110), capable of supporting multiple receive / transmit functions in an RRC connection state, may be configured to utilize wireless resources provided by multiple schedulers of multiple base stations. Multiple base stations may be interconnected via non-ideal or ideal backhaul (e.g., Xn interface, X2 interface, etc.). A base station associated with multiple connections for a specific wireless device may perform at least one of two different roles, namely, the base station may operate as a master base station or as an auxiliary base station. In multiple connections, the wireless device may be connected to one master base station and one or more auxiliary base stations. In one example, the master base station (e.g., MN (1130)) may provide a master cell group (MCG) comprising a primary cell and / or one or more auxiliary cells for the wireless device (e.g., wireless device (110)). An auxiliary base station (e.g., SN (1150)) may provide a primary auxiliary cell (PSCell) and / or an auxiliary cell group (SCG) comprising one or more auxiliary cells for a wireless device (e.g., wireless device (110)).

[0097] In a multiple connection, the wireless protocol architecture used by the bearer may vary depending on how the bearer is set up. In one embodiment, three different types of bearer setup options may be supported: an MCG bearer, an SCG bearer, and / or a split bearer. A wireless device may receive / transmit packets from an MCG bearer through one or more cells of an MCG, and / or receive / transmit packets from an SCG bearer through one or more cells of an SCG. A multiple connection may also be described as having at least one bearer configured to use wireless resources provided by an auxiliary base station. A multiple connection may or may not be configured / implemented in some of the exemplary embodiments.

[0098] For example, a wireless device (e.g., wireless device (110)) includes: packets of an MCG bearer through an 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)); packets of a split bearer through an SDAP layer (e.g., SDAP (1110)), a PDCP layer (e.g., NR PDCP (1112)), one of a master or auxiliary RLC layer (e.g., MN RLC (1115), SL RLC (1116)), and one of a master or auxiliary MAC layer (e.g., MN MAC (1118), SN MAC (1119)); and / or packets of the SCG bearer can be transmitted and / or received through the SDAP layer (e.g., SDAP (1110)), PDCP layer (e.g., NR PDCP (1113)), RLC layer (e.g., SN RLC (1117)), and MAC layer (e.g., MN MAC (1119)).

[0099] In one example, a master base station (e.g., MN (1130)) and / or an auxiliary base station (e.g., SN (1150)) receive packets of an MCG bearer through the master or auxiliary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), the master or auxiliary node PDCP layer (e.g., NR PDCP (1121), NR PDCP (1142)), the master node RLC layer (e.g., MN RLC (1124), MN RLC (1125)), and the master node MAC layer (e.g., MN MAC (1128)); Packets of the SCG bearer through the master or secondary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), the master or secondary node PDCP layer (e.g., NR PDCP (1122), NR PDCP (1143)), the secondary node RLC layer (e.g., SN RLC (1146), SN RLC (1147)), and the secondary node MAC layer (e.g., SN MAC (1148)); Packets of the split bearer can be transmitted / received through the master or auxiliary node SDAP layer (e.g., SDAP (1120), SDAP (1140)), the master or auxiliary node PDCP layer (e.g., NR PDCP (1123), NR PDCP (1141)), the master or auxiliary node RLC layer (e.g., MN RLC (1126), SN RLC (1144), SN RLC (1145), MN RLC (1127)), and the master or auxiliary node MAC layer (e.g., MN MAC (1128), SN MAC (1148)).

[0100] In a multiple connection, the wireless device may be configured with multiple MAC entities, namely, one MAC entity for the master base station (e.g., MN MAC (1118)), and other MAC entities for the auxiliary base station (e.g., SN MAC (1119)). In a multiple connection, the configured set of serving cells for the wireless device may include two subsets, namely an MCG containing serving cells of the master base station and SCGs containing serving cells of the auxiliary base station. For the SCG, one or more of the following configurations may apply: at least one cell of the SCG has a configured UL CC, and at least one cell of the SCG named as the primary auxiliary cell (PSCcell, PCell of the SCG, or often referred to as PCell) is configured to have a PUCCH resource; if the SCG is configured, there may be at least one SCG bearer or one split bearer; When a physical layer problem or random access problem is detected for a PSCell, or when the number of NR RLC retransmissions reaches the number associated with the SCG, or when an access problem for a PSCell is detected during an SCG addition or SCG change, the RRC connection re-establishment procedure may not be triggered, UL transmissions for the cells of the SCG may be stopped, the master base station may be notified by a radio device of the SCG failure type to the split bearer, and DL data transmission through the master base station may be maintained; an NR RLC acknowledgment mode (AM) bearer may be configured for the split bearer; the PCell and / or PSCell may not be disabled; the PSCell may be changed using an SCG change procedure (e.g., security key change and RACH procedure); and / or a change in bearer type between the split bearer and the SCG bearer or simultaneous configuration of the SCG and the split bearer may or may not be supported.

[0101] Regarding the interaction between master base stations and auxiliary base stations for multiple connections, one or more of the following may apply: the master base station and / or auxiliary base stations may maintain RRM measurement configurations of the wireless device; the master base station may decide to request the auxiliary base station to provide additional resources (e.g., serving cells) for the wireless device (e.g., based on received measurement reports, traffic conditions, and / or bearer types); upon receiving a request from the master base station, the auxiliary base station may create / modify a container that may cause the configuration of additional serving cells for the wireless device (or determine that the auxiliary base station does not have the available resources to do so); for UE performance tuning, the master base station may provide AS configuration (part of) and provide UE performance to the auxiliary base station; the master base station and the auxiliary base station may exchange information regarding UE configuration using RRC containers (inter-node messages) transmitted by Xn messages; the auxiliary base station may initiate the reconfiguration of serving cells where the auxiliary base station exists (e.g., PUCCH for the auxiliary base station); The auxiliary base station can determine which cell is a PSCell within the SCG; the master base station may or may not change the contents of the RRC configuration provided by the auxiliary base station; in the case of SCG addition and / or SCG SCell addition, the master base station may provide the latest (or most recent) measurement results for the SCG cell(s); the master base station and the auxiliary base station may receive information about the SFN (e.g., for DRX alignment and / or identification of measurement gaps) and / or subframe offsets between each other from the OAM and / or via the Xn interface.In one example, when adding a new SCG SCell, dedicated RRC signaling may be used to transmit the necessary system information of the cell to the CA, except for the SFN obtained from the MIB of the SCG's PSCell.

[0102] FIG. 12 is an exemplary diagram of a random access procedure. One or more events may trigger a random access procedure. For example, one or more events may be at least one of the following: an initial connection from RRC_IDLE, an RRC connection re-establishment procedure, a handover, the arrival of DL or UL data during RRC_CONNECTED when the UL synchronization status becomes desynchronized, a transition from RRC_Inactive, and / or a request for other system information. For example, a PDCCH sequence, a MAC entity, and / or a beam failure indication may initiate a random access procedure.

[0103] In an exemplary embodiment, the random access procedure may 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 may include one or more Msg1 (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 may include one or more Msg1 (1220) transmissions and one or more Msg2 (1230) transmissions.

[0104] In one example, the base station can transmit the RACH configuration (1210) to the UE (e.g., unicast, multicast, or broadcast) through one or more beams. The RACH configuration (1210) may include one or more parameters representing at least one of the following: an available set of PRACH resources for transmitting random access preambles (e.g., random access preamble index), an RSRP threshold for selecting SS blocks and corresponding PRACH resources, a power-ramping factor (e.g., random access preamble power ramping step), a random access preamble index, preamble transmission, a maximum number of preamble groups A and B, a threshold for determining groups of random access preambles (e.g., message size), a set of one or more random access preambles for a system information request and corresponding PRACH resource(s), a set of one or more random access preambles for a beam fail recovery request and corresponding PRACH resource(s) (if applicable), a time period for monitoring RA response(s) (if applicable), a time period for monitoring response(s) to a beam fail recovery request, and / or a contention resolution timer.

[0105] In one example, Msg1 (1220) may be one or more transmissions of random access preambles. In the case of a contention-based random access procedure, the UE may select an SS block having an RSRP that exceeds the RSRP threshold. If a random access preamble group B exists, the UE may select one or more random access preambles from group A or group B according to the potential Msg3 (1240) size. If a random access preamble group B does not exist, the UE may select one or more random access preambles from group A. The UE may randomly select a random access preamble index from one or more random access preambles associated with the selected group (e.g., with equal probability or a normal distribution). If the base station semi-statistically configures the UE to have an association between the random access preambles and the SS blocks, the UE may randomly select a random access preamble index with equal probability from one or more random access preambles associated with the selected SS block and the selected group.

[0106] For example, the UE may initiate a contention-free random access procedure based on a beam failure indication from a lower layer. For example, the base station may semi-statistically configure the UE to have one or more contention-free PRACH resources for a beam failure recovery request associated with at least one of the SS blocks and / or CSI-RSs. If at least one of the associated SS blocks having an RSRP exceeding a first RSRP threshold, or at least one of the associated CSI-RSs having an RSRP exceeding a second RSRP threshold, is available, the UE may 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 a beam failure recovery request.

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

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

[0109] In one example, the UE may receive a random access response, Msg 2 (1230), from the base station. The UE may monitor the random access response during a time period (e.g., ra-ResponseWindow ) can be initiated. In the case of a beam failover request, the base station monitors the response to the beam failover request at different time zones (e.g., bfr-ResponseWindow The UE can be configured to have ). For example, the UE has a time zone (e.g., at the start of the first PDCCH situation after a fixed duration of one or more symbols following the end of the preamble transmission) ra-ResponseWindow or bfr-ResponseWindow ) can be started. If the UE transmits multiple preambles, the UE may start a time zone at the start of the first PDCCH situation after a fixed duration of one or more symbols from the end of the first preamble transmission. While the timer for the time zone is running, the UE may monitor the cell's PDCCH for at least one random access response identified by RA-RNTI or at least one response to a beam failure recovery request identified by C-RNTI.

[0110] In one example, if at least one random access response includes a random access preamble identifier corresponding to a random access preamble transmitted by the UE, the UE may consider the reception of the random access response successful. If the reception of the random access response is successful, the UE may consider the contention-free random access procedure to have been successfully completed. If the contention-free random access procedure is triggered for a beam failover request, the UE may consider the contention-free random access procedure to have been successful if the PDCCH transmission is addressed to C-RNTI. In one example, if at least one random access response includes a random access preamble identifier, the UE may consider the random access procedure to have been successfully completed and may indicate the reception of an acknowledgment for a system information request to upper layers. If the UE has signaled multiple preamble transmissions, the UE may stop the transmission of the remaining preambles (if any) in response to the successful reception of the corresponding random access response.

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

[0112] In one example, multiple UEs can perform Msg1 (1220) by transmitting the same preamble to a base station and receiving the same random access response from the base station containing an identity (e.g., TC-RNTI). Contention resolution (1250) can ensure that a UE does not incorrectly use another UE's identity. For example, contention resolution (1250) may be based on a C-RNTI on a PDCCH or a UE contention resolution identity on a DL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UE can perform contention resolution (1250) based on the reception of a PDCCH transmission addressed by the C-RNTI. In response to the detection of the C-RNTI on the PDCCH, the UE may consider the contention resolution (1250) to be successful and the random access procedure to be successfully completed. If the UE does not have a valid C-RNTI, the contention resolution can be addressed using the TC-RNTI. For example, if the MAC PDU is successfully decoded and the MAC PDU contains a UE contention resolution identity MAC CE that matches the CCCH SDU transmitted in Msg3 (1250), the UE can consider the contention resolution (1250) to be successful and the random access procedure to be successfully completed.

[0113] FIG. 13 is an exemplary structure for MAC entities according to one aspect of an embodiment. In one example, a wireless device may be configured to operate in a multiple connection mode. A wireless device that is RRC_CONNECTED with multiple RX / TX may be configured to utilize wireless resources provided by multiple schedulers located at multiple base stations. Multiple base stations may be connected via a non-ideal or ideal backhaul through an Xn interface. In one example, one base station among multiple base stations may operate as a master base station or as an auxiliary base station. The wireless device may be connected to one master base station and one or more auxiliary base stations. The wireless device may be configured to have multiple MAC entities, for example, one MAC entity for the master base station and one or more other MAC entities for the auxiliary base station(s). In one example, a configured set of serving cells for the wireless device may include two subsets, namely, an MCG containing serving cells of the master base station and one or more SCGs containing serving cells of the auxiliary base station(s). FIG. 13 illustrates an exemplary structure for MAC entities when MCG and SCG are configured for a wireless device.

[0114] In one example, at least one cell within the SCG may have a configured UL CC, and one of the at least one cells may be referred to as the PSCell or PCell of the SCG, or often simply referred to as the PCell. The PSCell may be configured to have a PUCCH resource. In one example, when the SCG is configured, there may be at least one SCG bearer or one split bearer. In one example, upon detection of a physical layer problem or random access problem for the PSCell, or when the number of RLC retransmissions associated with the SCG is reached, or upon detection of a connection problem for the PSCell during an SCG addition or SCG change, an RRC connection re-establishment procedure may not be triggered, UL transmissions toward the cells of the SCG may be stopped, the master base station may be notified by the UE of the SCG failure type, and DL data transmission through the master base station may be maintained.

[0115] In one example, the MAC lower layer may provide services such as data transmission to upper layers (e.g., 1310 or 1320) and wireless resource allocation. The MAC lower layer may include multiple MAC entities (e.g., 1350 and 1360). The MAC lower layer may provide data transmission services over logical channels. Multiple types of logical channels may be defined to accommodate various types of data transmission services. A logical channel may support the transmission of a specific type of information. The type of logical channel may be defined by what type of information (e.g., control or data) is transmitted. For example, BCCH, PCCH, CCCH, and DCCH may be control channels, and DTCH may be a traffic channel. In one example, the first MAC entity (e.g., 1310) may provide services for PCCH, BCCH, CCCH, DCCH, DTCH, and MAC control elements. In one example, a second MAC entity (e.g., 1320) can provide services for BCCH, DCCH, DTCH, and MAC control elements.

[0116] The MAC lower layer may be expected from physical layer services (e.g., 1330 or 1340), such as data transmission services, signaling of HARQ feedback, scheduling requests, or signaling of measurements (e.g., CQI). In one example, in a duplex connection, two MAC entities, namely a MAC entity for the MCG and a MAC entity for the SCG, may be configured for the wireless device. The MAC entity of the wireless device may handle multiple transmission channels. In one example, the first MAC entity may handle first transmission channels including the PCCH of the MCG, the 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 one example, the second MAC entity can process second transmission 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.

[0117] In one example, if a MAC entity consists of one or more SCells, there may be multiple DL-SCHs, multiple RACHs, and multiple UL-SCHs per MAC entity. In one example, there may be one DL-SCH and one UL-SCH on an SpCell. In one example, for a SCell, there may be one DL-SCH, zero or one UL-SCH, and zero or one RACH. A DL-SCH may support receptions using different numerologies and / or TTI periods within a MAC entity. Additionally, a UL-SCH may support transmissions using different numerologies and / or TTI periods within a MAC entity.

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

[0119] FIG. 14 is an exemplary diagram of a RAN architecture including one or more base stations. In one example, a protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and PHY) may be supported at the node. A base station (e.g., 120A or 120B) may 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)) when functional partitioning is configured. The upper protocol layers of the base station may be located within the base station (CU), and the lower layers of the base station may be located in the base stations (DU). An F1 interface (e.g., CU-DU interface) connecting the base station (CU) and the base stations (DU) may be an ideal or non-ideal backhaul. F1-C can provide control plane connectivity through the F1 interface, and F1-U can provide user plane connectivity through the F1 interface. In one example, the Xn interface can be configured between base station CUs.

[0120] In one example, the base station (CU) may include RRC functions, an SDAP layer, and a PDCP layer, and the base stations (DU) may include an RLC layer, a MAC layer, and a PHY layer. In one example, various functional partitioning options between the base station (CU) and the base stations (DU) may be possible by positioning different combinations of upper protocol layers (RAN functions) in the base station (CU) and different combinations of lower protocol layers (RAN functions) in the base stations (DU). Functional partitioning can support flexibility for moving protocol layers between the base station (CU) and the base stations (DU) depending on service requirements and / or network environments.

[0121] In one example, functional partitioning options may be configured per base station, per base station (CU), per base station (DU), per UE, per bearer, per slice, or with other granularities. When partitioning per base station (CU), the base station (CU) may have a fixed partitioning option, and the base stations (DU) may be configured to match the partitioning option of the base station (CU). When partitioning per base station (DU), the base station (DU) may be configured to have different partitioning options, and the base station (CU) may provide different partitioning options for different base stations (DU). When partitioning per UE, the base station (base station (CU) and at least one base station (DU)) may provide different partitioning options for different wireless devices. When partitioning per bearer, different partitioning options may be used for different bearers. When partitioning per slice, different partitioning options may be applied for different slices.

[0122] FIG. 15 is an exemplary diagram illustrating the transition of an RRC state of a wireless device. In one example, the wireless device may be in at least one RRC state among an RRC connected state (e.g., RRC Connected (1530), RRC_Connected), an RRC idle state (e.g., RRC Idle (1510), RRC_Idle), and / or an RRC inactive state (e.g., RRC Inactive (1520), RRC_Inactive). In one example, in the RRC connected state, the wireless device may have at least one RRC connection with at least one base station (e.g., gNB and / or eNB) that may have the UE context of the wireless device. A UE context (e.g., a wireless device context) may include at least one of an access layer context, one or more wireless link configuration parameters, bearer configuration information (e.g., data wireless bearer (DRB), signaling wireless bearer (SRB), logical channel, QoS flow, PDU session, etc.), security information, PHY / MAC / RLC / PDCP / SDAP layer configuration information, and other similar configuration information for a wireless device. In one example, in an RRC idle state, the wireless device may not have an RRC connection with a base station, and the UE context of the wireless device may not be stored at the base station. In one example, in an RRC inactive state, the wireless device may not have an RRC connection with a base station. The UE context of the wireless device may be stored at a base station that may be referred to as an anchor base station (e.g., an end-serving base station).

[0123] In one example, the wireless device may switch the UE RRC state bidirectionally between the RRC idle state and the RRC connected state (e.g., disconnect (1540) or establish connection (1550); or re-establish connection) and / or bidirectionally between the RRC inactive state and the RRC connected state (e.g., disable connection (1570) or resume connection (1580)). In one example, the wireless device may switch its RRC state from the RRC inactive state to the RRC idle state (e.g., disconnect (1560)).

[0124] In one example, the anchor base station may be a base station capable of maintaining the wireless device's UE context (wireless device context) during the period the wireless device remains within the anchor base station's RAN notification area (RNA) and / or during the period the wireless device remains in an RRC inactive state. In one example, the anchor base station may be a base station where the wireless device in an RRC inactive state was last connected in the most recent RRC connection state or where the wireless device last performed the RNA update procedure. In one example, the RNA may include one or more cells operated by one or more base stations. In one example, a base station may belong to one or more RNAs. In one example, a cell may belong to one or more RNAs.

[0125] In one example, the wireless device can switch the UE RRC state from the base station's RRC connected state to the RRC disabled state. The wireless device can receive RNA information from the base station. The RNA information may 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, the base station's IP address, the wireless device's AS context identifier, a resume identifier, etc.

[0126] For example, an anchor base station may broadcast a message (e.g., a RAN paging message) to base stations of RNA to reach radio devices in an RRC inactive state, and / or base stations receiving the message from the anchor base station may broadcast and / or multicast another message (e.g., a paging message) to radio devices in their coverage area, cell coverage area, and / or beam coverage area associated with RNA through a radio interface.

[0127] In one example, when a radio device in an RRC-inactive state moves to a new RNA, the radio device may perform an RNA update (RNAU) procedure that may include a random access procedure and / or a UE context retrieval procedure by the radio device. The UE context retrieval may include the step of receiving a random access preamble from the radio device by the base station, and the step of fetching the radio device's UE context by the base station from the previous anchor base station. The retrieval step may include the step of transmitting a retrieval UE context request message containing a resumption identifier to the previous anchor base station, and the step of receiving a retrieval UE context response message containing the radio device's UE context from the previous anchor base station.

[0128] In an exemplary embodiment, a wireless device in an RRC-inactive state may select a cell to communicate with, based on at least one measurement result for one or more cells, such that the wireless device can monitor RNA paging messages and / or core network paging messages from a base station. In one example, the wireless device in an RRC-inactive state may select a cell to perform an arbitrary access procedure to resume an RRC connection and / or transmit one or more packets to a base station (e.g., a network). In one example, if the selected cell belongs to an RNA different from the RNA for the wireless device in an RRC-inactive state, the wireless device may initiate an arbitrary access procedure to perform an RNA update procedure. In one example, if the wireless device in an RRC-inactive state has one or more packets in a buffer to transmit to a network, the wireless device may initiate an arbitrary access procedure to transmit one or more packets to the base station of the cell selected by the wireless device. The random access procedure can be performed using two messages (e.g., two-level random access) and / or four messages (e.g., four-level random access) between the wireless device and the base station.

[0129] In an exemplary embodiment, a base station receiving one or more uplink packets from a wireless device in an RRC-inactive state may fetch the UE context of the wireless device by transmitting a search UE context request message for the wireless device to the 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 resumption identifier, and / or a cell identifier received from the wireless device. In response to fetching the UE context, the base station may transmit a route switch request for the wireless device to a core network entity (e.g., AMF, MME, etc.). The core network entity may update the downlink tunnel endpoint identifier for one or more bearers established for the wireless device between a user plane core network entity (e.g., UPF, S-GW, etc.) and a RAN node (e.g., base station), for example, by changing the downlink tunnel endpoint identifier from the address of the anchor base station to the address of the base station.

[0130] A gNB can communicate with a wireless device through a wireless network utilizing one or more new radio (NR) technologies. The one or more wireless technologies may include at least one of a number of technologies related to the physical layer, a number of technologies related to the media access control layer, and / or a number of technologies related to the wireless resource control layer. Exemplary embodiments that enhance one or more wireless technologies can improve the performance of the wireless network. Exemplary embodiments can increase system throughput or the data rate of transmission. Exemplary embodiments can reduce battery consumption of the wireless device. Exemplary embodiments can improve the latency of data transmission between the gNB and the wireless device. Exemplary embodiments can improve the network coverage of the wireless network. Exemplary embodiments can improve the transmission efficiency of the wireless network.

[0131] In one example, depending on different operator strategies and rules and laws in different countries, many network-sharing scenarios may exist. Equivalent PLMN features can enable operators to share a common base station by utilizing specific parts of core networks shared among operators.

[0132] In one example, a network-sharing scenario allows operators to share networks and / or provide wireless services to their customers. For instance, one operator can use another operator's allocated spectrum to provide services to its subscribers. Geographically segmented networks, such as a scenario where cooperating operators cover different parts of a country, may be possible. An operator's core network may also be connected to multiple base stations.

[0133] In one example, at a specific time, it is important not only to consider the sharing solution but also how the sharing partners can evolve into more dedicated networks or more combined networks. The set of infrastructure sharing solutions and scenarios discussed in the industry may cover alternatives that include: alternative solutions targeting dedicated networks in the near future; solutions for infrastructure sharing that do not aim for immediate exit but are intended to be terminated, for example, if network capacity demand becomes excessive; and / or solutions for infrastructure sharing that aim for long-term sharing, which may, for example, be a case where one of the operators does not hold a frequency license. In one example, identifying, modifying, and adding appropriate functions in the network can lead to better sharing-network operations.

[0134] In one example, operators with multiple frequency allocations may share RAN elements rather than sharing radio frequencies. In this case, operators can directly access their dedicated carrier layer from the shared base station.

[0135] In one example, in this scenario, two (or more) operators with individual licenses can cover different parts of a country with their respective wireless access networks, but together provide full coverage of the country.

[0136] In one example, when two (or more) operators use country roaming for users (e.g., UEs), it may imply that one core network can be associated with a wireless access network. Caution may be required when coverage areas overlap, which can make this a valid shared network scenario.

[0137] In one example, operators may have their individual core networks connected to all radio access networks across the entire coverage area, for example, by utilizing the spectrum allocated to different operators in different parts of the coverage area. Multiple core network operators may exist within the shared radio access networks. The connection of core networks to the radio access networks (e.g., base stations) can be accomplished by connecting radio network controllers to all core network components of the operators or by sharing parts of the core network. Interface flex functionality can be introduced between common core network parts and radio access networks purely for load sharing.

[0138] In one example, in an area where two or more operators provide coverage, access rights may be restricted to allow the user to use the wireless access network provided by their home operator.

[0139] In one example, one operator may deploy coverage in a specific geographic area, and other operators may be allowed to use this coverage for their subscribers. Outside of this geographic area, coverage may be provided by said operators.

[0140] For example, in the case of two operators, a third party may provide RAN coverage for the subscribers of operators (A and B') in areas with high population density. In less dense areas, other RAN coverage is provided by operators (A) and (B), and subscribers in these areas may connect to their operators' access networks.

[0141] In one example, common spectrum network sharing may apply when one operator has a license or shares allocated spectrum with other operators; and / or when multiple operators decide to provide their allocated spectrum to a pool and share the entire spectrum (operators without allocated spectrum may also share this spectrum pool).

[0142] In one example, it is connected to the operator's core networks and / or shared wireless access network(s) (one wireless network controller for simplification). In this case, one or more core network operators may use interface flex between their core networks and shared wireless access networks. Operators (A and C) may not use multiple core network nodes (CN) and therefore may not need to use interface flex. Operator (B) may use multiple CNs and / or may have decided to use interface flex to enable domain-wide sharing of CNs.

[0143] In one example, core network entities connected to a wireless access network can be shared. Operations in shared networks may be at the discretion of the operator implementing the operation.

[0144] In a network sharing scenario, multiple wireless access networks can share a common network. Multiple RANs may belong to different PLMNs and network operators. Due to the deployment of operators, parts of the common core network or different nodes may be shared.

[0145] In one example, to fully support handovers, service differentiation, and access rights in shared networks, it may be necessary to identify the operator to which a user (e.g., UE) belongs and to group users based on this information. To avoid complex operational and maintenance procedures, such user classification may be general for functions within a shared network that require information regarding user identity. Network sharing may be an agreement between network operators and / or may be transparent to the user.

[0146] In one example, if network sharing exists between different operators and a user roams to that shared network, the user may register with a core network operator (among network sharing partners) with whom they have a roaming agreement, even if their home operator does not provide wireless coverage. The selection of a core network operator among the operators connected to the shared wireless access network may be manual (i.e., performed by the user after receiving a list of available core network operators) or automatic (i.e., performed by the UE based on user and operator preference settings).

[0147] In one example, the terminal may display the name of a core network operator (e.g., PLMN) registered by the user. The network sharing solution may support legacy UEs. In one example, the following two cases may be identified: manual network selection for roaming users; and / or network name display for roaming users. Service functions and requirements may not be limited by the network sharing scenario. The network operator may distinguish services provided by other network operators within the shared network.

[0148] In one example, the services and service functions provided may not be limited by the existence of network sharing. A network operator can distinguish services provided by other network operators within the shared network. The provision of services and service functions that can be provided by the network may not be limited by the existence of network sharing. A core network operator can distinguish services provided by other core network operators within the shared network. Access to service functions provided by the shared network can be controlled based on the core network operator to which the user is subscribed. Mobility in the shared network may not cause excessive interruption of services, whether controlled by the UE or by the network.

[0149] In one example, a subscriber can roam between different parts of a shared network without user intervention. The user experience while roaming on a shared network may be better than the user experience on a non-shared network. In some cases, user intervention may be required, for example, if a change to a different part of a shared network causes a change in service tariffs.

[0150] In one example, seamless handover between a shared network and a non-shared network can be supported. A user (e.g., a UE) can receive the same service level during and after the handover between the networks.

[0151] In one example, the network may access relevant subscriber information to determine a suitable candidate for handover. Examples of information (a non-exclusive list) that may be required to determine a candidate may include the subscription type (e.g., prepaid / postpaid), the subscriber's home network (in the case of roaming subscribers); the service(s) to be handed over; and the subscribed quality of service.

[0152] In one example, when a user is registered on a shared network, the control and wireless access technology of the PLMNs used within that shared network are under the full control of the network operator. This may not imply any restrictions on the manual or automatic selection of PLMNs that do not belong to the shared network to which the user is registered.

[0153] In one example, standards may specify mechanisms necessary to enable flexible allocation of inbound roaming operators among core network operators having roaming agreements with the same roaming partners. Core network operators may predefine the relative sharing of inbound roaming operators, and networks may accordingly be distributed to inbound roaming operators applying automatic network selection to different core networks connected to the radio access network. Core network operators may allow or force subscribers to re-select to another part of the shared network so that the relative sharing of inbound roaming operators is maintained.

[0154] For example, when mobility in a shared network is controlled by a UE (e.g., cell reselection), the operator can set parameters other than the wireless parameters that determine the most suitable candidate. Examples of such parameters include subscriber information, requested services, and network load. Billing solutions can support shared network architectures so that both end users and network sharing partners can be accurately billed for their use of the shared network.

[0155] In one example, a UE may apply system information acquisition procedures to obtain AS-system information and / or NAS-system information that may be broadcast by E-UTRAN and / or NR. The procedures may be applied to UEs in the RRC_IDLE, RRC_INACTIVE, and / or RRC_CONNECTED states.

[0156] In one example, the UE may apply the system information acquisition procedure when selecting (e.g., when power is supplied) and / or reselecting a cell, after a handover is completed, after entering E-UTRA / NR from another radio access technology (RAT), when receiving a notification that system information has changed, when receiving an indication of presence of an ETWS notification, when receiving a notification of presence of a CMAS notification, when receiving a notification that EAB parameters have changed, when receiving a request from the CDMA2000 upper layer, and / or when the maximum validity period is exceeded. In one example, the system information acquisition procedure may overwrite stored system information, and, for example, a delta configuration may not be applied to the system information and / or, unless explicitly specified otherwise, the UE terminates using a field if the system information acquisition procedure does not exist in the system information.

[0157] In one example, in the RRC_CONNECTED state, the BL UEs and / or UEs of CE may be required during a handover when T311 is running and a UE may be required to obtain system information and / or obtain the MasterInformationBlock within the target PCell. During the handover, the E-UTRAN / NR may provide the system information required by the UE in the RRC_CONNECTED (e.g., excluding MIB) state using RRC signaling, e.g., systemInformationBlockType1Dedicated and / or mobilityControlInfo.

[0158] In one example, the UE may be guaranteed to have a valid version of (at least) the following system information, also referred to as 'essential' system information, as defined below: 1> when in the RRC_IDLE / RRC_INACTIVE state; 3> when the UE is an NB-IoT UE; 4> MasterInformationBlock-NB and SystemInformationBlockType1-NB, as well as SystemInformationBlockType2-NB to SystemInformationBlockType5-NB, SystemInformationBlockType22-NB; 3> otherwise: 4> MasterInformationBlock and / or SystemInformationBlockType1 (or SystemInformationBlockType1-BR, depending on whether the UE is a BL UE or a UE within CE), as well as SystemInformationBlockType2 to SystemInformationBlockType8 (depending on support by the RATs of interest), SystemInformationBlockType17 (depending on support for RAN-assisted WLAN interworking); 2> If in RRC_CONNECTED state; and / or 2> If the UE is not a BL UE; and / or 2> If the UE is not within CE; and / or 2> If the UE is not an NB-IoT UE: 3> MasterInformationBlock, SystemInformationBlockType1 and / or SystemInformationBlockType2, as well as SystemInformationBlockType8 (depending on CDMA2000 support), SystemInformationBlockType17 (depending on RAN-auxiliary WLAN interworking support); 2> If in RRC_CONNECTED state and / or T311 is running;and / or 2> if the UE is a BL UE, or the UE is in CE, or the UE is an NB-IoT UE; 3> MasterInformationBlock (or MasterInformationBlock-NB in ​​NB-IoT), SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB in ​​NB-IoT) and / or SystemInformationBlockType2 (or SystemInformationBlockType2-NB in ​​NB-IoT), and / or SystemInformationBlockType22-NB for NB-IoT; 1> unless otherwise specified, delete stored system information 3 or 24 hours after the moment it is verified as valid; 1> If the systemInfoValueTag contained in SystemInformationBlockType1 (MasterInformationBlock-NB within NB-IoT) differs from one of the stored system information, and / or if the systemInfoValueTagSI is not broadcast when the UEs are NB-IoT UEs, BL UEs, and CE UEs, the stored system information, excluding SystemInformationBlockType10, SystemInformationBlockType11, systemInformationBlockType12, and / or systemInformationBlockType14 (systemInformationBlockType14-NB within NB-IoT), is deemed invalid;

[0159] In one example, the UE may: 1> apply a specified BCCH configuration or BR-BCCH configuration; 1> if the procedure is triggered by a system information change notification; 2> if the UE is using an idle / inactive DRX cycle longer than the correction cycle; 3> initiate the acquisition of required system information from the boundary of the next eDRX acquisition cycle; 2> otherwise, 3> initiate the acquisition of required system information from the start of the correction cycle following when the change notification was received; (the UE may continue using previously received system information until new system information is acquired) 1> if a UE is in the RRC_IDLE / RRC_INACTIVE state and / or if the UE enters a cell that does not store a valid version of the required system information while in the RRC_IDLE / RRC_INACTIVE state; 2> use the system information acquisition procedure to acquire the system information required in the RRC_IDLE / RRC_INACTIVE state; 1> After the UE has successfully completed a handover to a PCell that does not store a valid version of the system information required for the RRC_CONNECTED state: 2> Acquire the system information required for the RRC_CONNECTED state using the system information acquisition procedure; 2> If the system information of interest has been acquired: 3> Discard the corresponding radio resource configuration information contained in the previously received radioResourceConfigCommon within the dedicated message (if any); 1> Following a request from the CDMA2000 upper layer: 2> Acquire SystemInformationBlockType8;1> Do not initiate the transmission of the RRCConnectionReestablishmentRequest message without initiating the RRC connection establishment / resumption procedure until the UE has a valid version of SystemInformationBlockType2 (SystemInformationBlockType2-NB in ​​NB-IoT), as well as MasterInformationBlock (MasterInformationBlock-NB in ​​NB-IoT) and / or SystemInformationBlockType1 (SystemInformationBlockType1-NB in ​​NB-IoT), and / or SystemInformationBlockType22-NB in ​​the case of NB-IoT; 1> If broadcast, do not initiate the RRC connection establishment / resumption procedure under EAB until the UE has a valid version of SystemInformationBlockType14; 1> If the UE can use ETWS: 2> When entering a cell during the RRC_IDLE / RRC_INACTIVE state, following a successful handover or upon re-establishing a connection: 3> Discard previously buffered warningMessageSegment; 3> Clear current values ​​of messageIdentifier and serialNumber for SystemInformationBlockType11 (if any); 2> If the UE acquires SystemInformationBlockType1 following an ETWS indication, when entering a cell during the RRC_IDLE state, following a successful handover or upon re-establishing a connection: 3> If schedulingInfoList indicates that SystemInformationBlockType10 exists: 4> If the UE is in the CE: 5> Initiate acquiring SystemInformationBlockType10; 4> Otherwise, 5> Immediately initiate acquiring SystemInformationBlockType10;3> If schedulingInfoList indicates that SystemInformationBlockType11 exists: 4> Immediately initiate the acquisition of SystemInformationBlockType11; (Even if the systemInfoValueTag within SystemInformationBlockType1 has not changed, UEs may initiate the acquisition of SystemInformationBlockType10 and SystemInformationBlockType11 as described above);

[0160] 1> When the UE is able to use CMAS: 2> When entering a cell during the RRC_IDLE / RRC_INACTIVE state, following a successful handover or upon re-establishing a connection: 3> Discard any previously buffered warningMessageSegment; 3> Delete the stored values ​​of messageIdentifier and serialNumber for the SystemInformationBlockType12 associated with the discarded warningMessageSegment (if any); 2> When the UE acquires SystemInformationBlockType1 following a CMAS indication, when entering a cell during the RRC_IDLE / RRC_INACTIVE state, following a successful handover or upon re-establishing a connection: 3> When schedulingInfoList indicates that SystemInformationBlockType12 exists: 4> Acquire SystemInformationBlockType12; (The UE may initiate the acquisition of SystemInformationBlockType12 as described above, even if the systemInfoValueTag within SystemInformationBlockType1 has not changed)

[0161] 1> When the UE is interested in receiving MBMS services: 2> When the UE can receive MBMS: 3> When schedulingInfoList indicates that SystemInformationBlockType13 exists and the UE has not stored a valid version of this system information block: 4> Acquire SystemInformationBlockType13; 3> When SystemInformationBlockType13 exists within SystemInformationBlockType1-MBMS and the UE has not stored a valid version of this system information block: 4> Acquire SystemInformationBlockType13 from SystemInformationBlockType1-MBMS; 2> If the UE can receive SC-PTM: 3> If schedulingInfoList indicates that SystemInformationBlockType20 (SystemInformationBlockType20-NB within NB-IoT) exists or / or if the UE has not stored a valid version of this SystemInformationBlock: 4> Acquire SystemInformationBlockType20 (SystemInformationBlockType20-NB within NB-IoT); 2> If the UE can have MBMS service continuity: 3> If schedulingInfoList indicates that SystemInformationBlockType15 (SystemInformationBlockType15-NB within NB-IoT) exists or / or if the UE has not stored a valid version of this SystemInformationBlock: 4> Acquire SystemInformationBlockType15 (SystemInformationBlockType15-NB within NB-IoT);

[0162] 1> If the UE is capable of EAB: 2> If the UE has not saved a valid version of SystemInformationBlockType14 when entering the RRC_IDLE / RRC_INACTIVE state, and / or if the UE acquires SystemInformationBlockType1 following a notification of an EAB parameter change, and / or if entering a cell during the RRC_IDLE / RRC_INACTIVE state, or before establishing a connection when using an eDRX with a DRX period longer than the modification period: 3> If schedulingInfoList indicates that SystemInformationBlockType14 exists: 4> Immediately initiate the acquisition of SystemInformationBlockType14; 3> Otherwise: 4> Discard SystemInformationBlockType14 if received in advance; (Even if the systemInfoValueTag within SystemInformationBlockType1 has not changed, EAB-enabled UEs can initiate the acquisition of SystemInformationBlockType14 as described above) (EAB-enabled UEs can maintain the latest SystemInformationBlockType14 in the RRC_IDLE / RRC_INACTIVE state)

[0163] 1> If the UE is capable of and / or configured by upper layers to transmit or receive side-link communication: 2> If the cell used for side-link communication satisfies S-criteria; and / or 2> If schedulingInfoList indicates that SystemInformationBlockType18 exists or the UE has not stored a valid version of this System Information Block: 3> Acquire SystemInformationBlockType18; 1> If the UE is capable of and / or configured by upper layers to transmit or receive a side-link restoration guide on the main frequency: 2> If the serving cell / PCell's schedulingInfoList indicates that SystemInformationBlockType19 exists and / or if the UE has not stored a valid version of this System Information Block: 3> Acquire SystemInformationBlockType19; 1> If the UE can and / or can restore a lateral link, or if one or more frequencies included in discInterFreqList are included within SystemInformationBlockType19 or are frequencies configured by upper layers for the UE to receive lateral link restoration guidance: 2> If the SystemInformationBlockType19 of the serving cell / PCell does not provide corresponding receiving resources; and / or 2> If the schedulingInfoList of the cell on the frequency of interest indicates that SystemInformationBlockType19 exists or the UE has not stored a valid version of this SystemInformationBlock: 3> Acquire SystemInformationBlockType19;1> If the UE can and / or can restore a lateral link, or if one or more frequencies included in discInterFreqList are included within SystemInformationBlockType19 or are frequencies configured by upper layers for the UE to transmit a lateral link restoration guide: 2> If the SystemInformationBlockType19 of the serving cell / PCell includes discTxResourcesInterFreq which can be set to acquireSI-FromCarrier; and / or 2> If the schedulingInfoList of the cell on the frequency of interest indicates that SystemInformationBlockType19 exists, and the UE has not stored a valid version of this SystemInformationBlockType19: 3> Acquire SystemInformationBlockType19; 1> If the UE is an NB-IoT UE and / or ab-Enabled contained within the MasterInformationBlock-NB is set to TRUE: 2> The UE does not initiate the RRC connection establishment / resumption procedure for the connection cause (e.g., excluding mobile terminal calls) until it acquires the SystemInformationBlockType14-NB; 1> If the UE is capable of performing V2X sidelink communication on the frequency and / or is configured by upper layers to receive or transmit V2X sidelink communication: 2> If the schedulingInfoList on the serving cell / PCell indicates / indicates that SystemInformationBlockType21 exists or the UE has not stored a valid version of this SystemInformation Block; 3> Acquire SystemInformationBlockType21 from the serving cell / PCell;1> Where the UE is configured by upper layers to perform V2X sidelink communication or receive V2X sidelink communication on a frequency that may not be the primary frequency: 2> Where the SystemInformationBlockType21 of the serving cell / PCell does not provide a pool of receiving resources for V2X sidelink communication for the frequency of interest; and / or 2> Where the cell used for V2X sidelink communication on the frequency of interest satisfies S-criteria; and / or 2> Where the schedulingInfoList on the frequency of interest indicates that SystemInformationBlockType21 exists and the UE has not stored a valid version of this SystemInformationBlock: 3> Obtain SystemInformationBlockType21 from the frequency of interest; 1> if a UE is capable of or configured by upper layers to perform V2X sidelink communication on a frequency that may not be a primary frequency and / or may not be included in the v2x-InterFreqInfoList within the SystemInformationBlockType21 of the serving cell / PCell: 2> if the cell used for V2X sidelink communication on the frequency of interest satisfies S-criteria; and / or 2> if the schedulingInfoList on the frequency of interest indicates that SystemInformationBlockType21 exists or the UE has not stored a valid version of this SystemInformationBlock: 3> obtain SystemInformationBlockType21 from the frequency of interest;The UE may apply the received SIBs immediately; for example, the UE may not need to delay using the SIBs until SI messages are received. The UE may delay the application of the received SIBs until received RRC messages and / or RRC messages sent from the UE, for example, lower-level procedures associated with an ongoing random access procedure, are completed. While attempting to acquire a specific SIB, if the UE detects from the schedulingInfoList that the SIB may no longer exist, the UE may stop the attempt to acquire the specific SIB.

[0164] In one example, if the UE is in the RRC_IDLE / RRC_INACTIVE state or in the RRC_CONNECTED state while T311 is running; 2> if the UE cannot acquire MasterInformationBlock (MasterInformationBlock-NB within NB-IoT); and / or 2> if the UE is not a BL UE, is not in CE, is not in NB-IoT, and the UE cannot acquire SystemInformationBlockType1; and / or 2> if a BL UE or a UE in CE cannot acquire SystemInformationBlockType1-BR and / or if SystemInformationBlockType1-BR is not scheduled; and / or 2> if an NB-IoT UE cannot acquire SystemInformationBlockType1-NB; 3> if the cell can be considered forbidden; and / or 3> Restrictions may be performed as if intraFreqReselection is set to allow and / or csg-Indication is set to FALSE; 2> If the UE cannot acquire SystemInformationBlockType2 (or SystemInformationBlockType2-NB within NB-IoT) and / or, in the case of NB-IoT, SystemInformationBlockType22-NB (if scheduled): 3> ​​The cell may be treated as forbidden.

[0165] In one example, when a MasterInformationBlock message is received, the UE may: 1> apply the radio resource configuration contained in phich-Config; 1> if the UE is in the RRC_IDLE / RRC_INACTIVE state, or if the UE is in the RRC_CONNECTED state while T311 is running; 2> if the UE does not have stored valid system information for the cell of interest; 3> apply the received value of dl-Bandwidth to ul-Bandwidth until SystemInformationBlockType2 is received. In one example, when a MasterInformationBlock-NB message is received, the UE may: 1> apply the radio resource configuration contained according to operationModeInfo. In one example, UE requirements related to the contents of MasterInformationBlock-MBMS may not apply except those specified elsewhere, e.g., within a procedure using system information of interest, and / or within corresponding field descriptions.

[0166] In one example, if a UE receives SystemInformationBlockType1 or SystemInformationBlockType1-BR via broadcast and / or dedicated signaling, the UE may: 1> if cellAccessRelatedInfoList contains an entry with the PLMN-Identity of the selected PLMN; 2> in the remainder of the procedure, use the plmn-IdentityList, trackingAreaCode, and / or cellIdentity for the cell as received in the corresponding cellAccessRelatedInfoList containing the selected PLMN; 1> if in the RRC_IDLE / RRC_INACTIVE state or in the RRC_CONNECTED state while T311 is executed; and / or 1> if the UE is a Category 0 UE; and / or 1> if category0Allowed is not contained within SystemInformationBlockType1; 2> the cell may be considered forbidden; 1> If in the RRC_CONNECTED state while T311 is not executing, and / or if the UE supports multi-band cells as defined by bit 31 in featureGroupIndicators: 2> While in the RRC_CONNECTED state, freqBandIndicator and / or multiBandInfoList (if received) may be ignored; 2> cellIdentity may be forwarded to upper layers; 2> trackingAreaCode may be forwarded to upper layers; 1> Otherwise: 2> if the frequency band indicated in freqBandIndicator is part of the frequency bands supported by the UE and is not a downlink band;and / or 2> If the UE supports multiBandInfoList, and / or if one or more frequency bands listed in multiBandInfoList are part of the frequency bands supported by the UE and are not downlink bands: 3> cellIdentity can be forwarded to upper layers; 3> trackingAreaCode can be forwarded to upper layers; 3> ims-EmergencySupport (if present) can be forwarded to upper layers; 3> eCallOverIMS-Support (if present) can be forwarded to upper layers; 3> For a frequency band selected by the UE (from freqBandIndicator or multiBandInfoList), if freqBandInfo and / or multiBandInfoList-v10j0 exist and a multiNS-Pmax capable UE supports at least one additionalSpectrumEmission in the NS-PmaxList within freqBandInfo or multiBandInfoList-v10j0: 4> The additionalSpectrumEmission of the first list that can be supported among the values ​​contained in the NS-PmaxList within freqBandInfo or multiBandInfolist-v10j0 may be applied; 4> If additionalPmax exists in the same entry as the selected additionalSpectrumEmission within NS-PmaxList: 5> additionalPmax may be applied; 4> Otherwise: 5> p-Max may be applied; 3> Otherwise: 4> additionalSpectrumEmission and / or p-Max within SystemInformationBlockType2 may be applied; 2> Otherwise: 3> consider a cell can be considered forbidden;and / or restrictions can be performed as if 3> intraFreqReselection were set to notAllowed, and / or if csg-Indication were set to FALSE.;

[0167] In one example, upon receiving SystemInformationBlockType1-NB, the UE may: 1> if the frequency band indicated in freqBandIndicator is part of the frequency bands supported by the UE; and / or 1> if one or more frequency bands indicated in multiBandInfoList are part of the frequency bands supported by the UE: 2> forward cellIdentity to upper layers; 2> forward trackingAreaCode to upper layers; 2> if attachWithoutPDN-Connectivity is received for a selected PLMN: 3> forward attachWithoutPDN-Connectivity to upper layers; 2> otherwise, 3> indicate to upper layers that attachWithoutPDN-Connectivity does not exist; 2> For a frequency band selected by the UE (from freqBandIndicator or multiBandInfoList), if freqBandInfo exists and a multiNS-Pmax capable UE supports at least one additionalSpectrumEmission in the NS-PmaxList within freqBandInfo: 3> The additionalSpectrumEmission of the first list that is supported among the values ​​included in the NS-PmaxList within freqBandInfo may be applied; 3> If additionalPmax exists in the same entry as the selected additionalSpectrumEmission in the NS-PmaxList: 4> additionalPmax may be applied; 3> Otherwise: 4> p-Max may be applied; 2> Otherwise: 3> additionalSpectrumEmission and p-Max within SystemInformationBlockType2-NB may be applied;1> Otherwise: 2> The cell may be considered prohibited; and / or 2> Restrictions may be applied as if intraFreqReselection were set to notAllowed. In one example, UE requirements regarding the content of SystemInformationBlockType1-MBMS may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.;

[0168] In one example, when SystemInformation messages are received, UE requirements related to the contents of the SystemInformation messages may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0169] In one example, upon receiving SystemInformationBlockType2, the UE may: 1> apply the configuration contained in radioResourceConfigCommon; 1> if upper layers indicate that a paging cycle (specific to the UE) is configured: 2> apply the minimum paging cycle (specific to the UE) and the defaultPagingCycle contained in radioResourceConfigCommon; 1> if mbsfn-SubframeConfigList is included: 2> assume that DL allocation may occur in the MBSFN subframe contained in mbsfn-SubframeConfigList; 1> apply the specified PCCH configuration; 1> not apply timeAlignmentTimerCommon; 1> if the UE is in the RRC_CONNECTED state and is configured to have received RLF timers and constant values ​​within rlf-TimersAndConstants: 2> not update the values ​​of the timers and constants in ue-TimersAndConstants, except for the value of timer T300; 1> If in the RRC_CONNECTED state while T311 is not executing; and / or if the UE supports multi-band cells as defined by bit 31 in featureGroupIndicators or multipleNS-Pmax: 2> additionalSpectrumEmission and / or ul-CarrierFreq (if received) may be ignored while in the RRC_CONNECTED state; 1> if attachWithoutPDN-Connectivity is received for the selected PLMN: 2> attachWithoutPDN-Connectivity may be forwarded to upper layers; 1> otherwise: 2> attachWithoutPDN-Connectivity may be indicated to upper layers as not existing;1> If cp-CIoT-EPS-Optimisation is received for the selected PLMN: 2> cp-CIoT-EPS-Optimisation may be forwarded to the upper layers; 1> Otherwise: 2> cp-CIoT-EPS-Optimisation may be indicated to the upper layers as not existing; 1> If up-CIoT-EPS-Optimisation is received for the PLMN: 2> up-CIoT-EPS-Optimisation may be forwarded to the upper layers; 1> Otherwise: 2> up-CIoT-EPS-Optimisation may be indicated to the upper layers as not existing; 1> upperLayerIndication may be forwarded to the upper layers (if present for the selected PLMN), or this field may be indicated as non-existent; If SystemInformationBlockType2-NB is received, the UE: 1> may apply the configuration contained in radioResourceConfigCommon; 1> The defaultPagingCycle included in radioResourceConfigCommon can be applied; 1> When SystemInformationBlockType22-NB is scheduled: 2> Information transmitted within SystemInformationBlockType22-NB can be read and operated on; 1> The specified PCCH configuration can be applied. 1> When in the RRC_CONNECTED state and the UE is configured to have received RLF timers and constant values ​​within rlf-TimersAndConstants: 2> The values ​​of timers and constants in ue-TimersAndConstants are not updated except for the value of timer T300;

[0170] In one example, upon receiving SystemInformationBlockType3, the UE: 1> is in the RRC_IDLE / RRC_INACTIVE state and contains redistributionServingInfo, and if the UE is redistributable: 2> can perform the E-UTRAN inter-frequency redistribution procedure; 1> If in the RRC_IDLE / RRC_INACTIVE state, or in the RRC_CONNECTED state while T311 is running: 2> For the frequency band selected by the UE representing the carrying frequency of the serving cell, if freqBandInfo or multiBandInfoList-v10j0 exists within SystemInformationBlockType3 and / or if a multiNS-Pmax capable UE supports at least one additionalSpectrumEmission in NS-PmaxList within freqBandInfo or multiBandInfoList-v10j0: 3> Among the values ​​contained in NS-PmaxList within freqBandInfo or multiBandInfoList-v10j0, the additionalSpectrumEmission of the first list that is supported may be applied; 3> If additionalPmax exists in the same entry as the selected additionalSpectrumEmission within NS-PmaxList: 4> additionalPmax may be applied; 3> Otherwise: 4> p-Max may be applied; 2> Otherwise: 3> p-Max can be applied;

[0171] In one example, upon receiving SystemInformationBlockType3-NB, the UE may: 1> be in the RRC_IDLE state, or be in the RRC_CONNECTED state while T311 is executed; 2> for a frequency band selected by the UE representing the carrying frequency of the serving cell, if freqBandInfo or multiBandInfoList is in SystemInformationBlockType3-NB and / or if a multiNS-Pmax capable UE supports at least one additionalSpectrumEmission in NS-PmaxList within freqBandInfo or multiBandInfoList; 3> apply the additionalSpectrumEmission of the first list that is supported among the values ​​contained in NS-PmaxList within freqBandInfo or multiBandInfoList; 3> if additionalPmax exists in the same entry as the selected additionalSpectrumEmission in NS-PmaxList; 4> apply additionalPmax; 3> otherwise; 4> apply p-Max; 2> Otherwise: 3> p-Max can be applied.

[0172] In one example, when receiving SystemInformationBlockType4, UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType4 or SystemInformationBlockType4-NB) may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0173] In one example, upon receiving SystemInformationBlockType5, the UE: 1> is in the RRC_IDLE / RRC_INACTIVE state, contains redistributionInterFreqInfo, and if the UE is redistributable: 2> can perform the E-UTRAN inter-frequency redistribution procedure; 1> If in the RRC_IDLE / RRC_INACTIVE state, or in the RRC_CONNECTED state while T311 is running: 2> If the frequency band selected by the UE representing the unserved E UTRA carry frequency is not a downlink band: 3> For the selected frequency band, freqBandInfo or multiBandInfoList-v10j0 exists and / or multiNS-Pmax capable UE supports at least one additionalSpectrumEmission of NS-PmaxList within freqBandInfo or multiBandInfoList-v10j0: 4> Among the values ​​contained in NS-PmaxList within freqBandInfo or multiBandInfoList-v10j0, the additionalSpectrumEmission of the first list that can be supported may be applied; 4> If additionalPmax exists in the same entry as the selected additionalSpectrumEmission within NS-PmaxList: 5> additionalPmax may be applied; 4> Otherwise: 5> p-Max can be applied; 3> Otherwise: 4> p-Max can be applied;

[0174] In one example, upon receiving SystemInformationBlockType5-NB, the UE may: 1> be in the RRC_IDLE / RRC_INACTIVE state, or be in the RRC_CONNECTED state while T311 is executed; 2> for a frequency representing a non-serving NB-IoT carrier frequency selected (from multiBandInfoList) by the UE, if freqBandInfo exists and / or if a multiNS-Pmax capable UE supports at least one additionalSpectrumEmission in the NS-PmaxList within freqBandInfo; 3> apply the additionalSpectrumEmission of the first list that is supported among the values ​​contained in the NS-PmaxList within freqBandInfo; 3> if additionalPmax exists in the same entry as the selected additionalSpectrumEmission in the NS-PmaxList; 4> apply additionalPmax; 3> otherwise; 4> apply p-Max; 2> Otherwise: 3> p-Max can be applied;

[0175] In one example, when SystemInformationBlockType6 is received, UE requirements related to the contents of this SystemInformationBlock may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0176] In one example, UE requirements related to the content of this SystemInformationBlock may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0177] In one example, upon receiving SystemInformationBlockType8, the UE may: 1> if sib8-PerPLMN-List is included and the UE can share a network for CDMA2000: 2> apply the following CDMA2000 parameters corresponding to the RPLMN; 1> if systemTimeInfo is included: 2> forward systemTimeInfo to the CDMA2000 upper layers; 1> if the UE is in the RRC_IDLE state and searchWindowSize is included: 2> forward searchWindowSize to the CDMA2000 upper layers; 1> if parametersHRPD is included: 2> if the UE has not received preRegistrationInfoHRPD within the RRCConnectionReconfiguration message since entering this cell, forward preRegistrationInfoHRPD to the CDMA2000 upper layers; 2> If cellReselectionParametersHRPD is included: 3> neighCellList can be forwarded to CDMA2000 upper layers; 1> If parameters1XRTT is included: 2> If csfb-RegistrationParam1XRTT is included: 3> csfb-RegistrationParam1XRTT can be forwarded to CDMA2000 upper layers that can use this information to determine whether CS registration / re-registration is required toward the EUTRA cell's CDMA2000 1xRTT; 2> Otherwise: 3> It can indicate to CDMA2000 upper layers that CSFB registration to the CDMA2000 1xRTT may not be allowed; 2> If longCodeState1XRTT is included: 3> longCodeState1XRTT can be forwarded to CDMA2000 upper layers;2> If cellReselectionParameters1XRTT is included: 3> neighCellList can be forwarded to CDMA2000 upper layers; 2> If csfb-SupportForDualRxUEs is included: 3> csfb-SupportForDualRxUEs can be forwarded to CDMA2000 upper layers; 2> Otherwise: 3> The value of csfb-SupportForDualRxUEs can be set to FALSE and forwarded to CDMA2000 upper layers; 2> If ac-BarringConfig1XRTT is included: 3> ac-BarringConfig1XRTT can be forwarded to CDMA2000 upper layers; 2> If csfb-DualRxTxSupport is included: 3> csfb-DualRxTxSupport can be forwarded to CDMA2000 upper layers; 2> Otherwise: 3> You can forward to CDMA2000 upper layers by setting the value of csfb-DualRxTxSupport to FALSE.;

[0178] In one example, when receiving SystemInformationBlockType9, the UE may: 1> forward hnb-Name to upper layers if hnb-Name is included. In one example, when receiving SystemInformationBlockType10, the UE may: 1> forward the received warningType, messageIdentifier, and serialNumber to upper layers. In one example, when receiving SystemInformationBlockType11, the UE may: 1> if there are no current values ​​for messageIdentifier and serialNumber for SystemInformationBlockType11; and / or 1> If the received value of messageIdentifier or the received value of serialNumber, or both, differs from the current values ​​of messageIdentifier and serialNumber for SystemInformationBlockType11: 2> The received values ​​of messageIdentifier and serialNumber for SystemInformationBlockType11 may be used as the current values ​​of messageIdentifier and serialNumber for SystemInformationBlockType11; 2> The previously buffered warningMessageSegment may be discarded; 2> If a segment of a warning message is received: 3> The warning message may be assembled from the received warningMessageSegment; 3> The received warning message, messageIdentifier, serialNumber, and dataCodingScheme may be forwarded to upper layers; 3> Reception of SystemInformationBlockType11 may be stopped;3> The current values ​​of messageIdentifier and serialNumber for SystemInformationBlockType11 can be discarded; 2> Otherwise: 3> The received warningMessageSegment can be saved; 3> Reception of SystemInformationBlockType11 can be continued; 1> If segments of the warning message are received: 2> The warning message can be assembled from the received warningMessageSegment; 2> The received complete warning message, messageIdentifier, serialNumber and / or dataCodingScheme can be forwarded to upper layers; 2> Reception of SystemInformationBlockType11 can be stopped; 2> The current values ​​of messageIdentifier and / or serialNumber for SystemInformationBlockType11 can be discarded; 1> Otherwise: 2> The received warningMessageSegment can be saved; 2> Reception of SystemInformationBlockType11 can be continued; If a complete warning message is not assembled within a 3-hour period, the UE may discard the current values ​​of the messageIdentifier and / or serialNumber for the stored warningMessageSegment and / or SystemInformationBlockType11.

[0179] In one example, when receiving SystemInformationBlockType12, the UE may: 1> if SystemInformationBlockType12 contains a complete warning message; 2> forward the received warning message, messageIdentifier, serialNumber, and dataCodingScheme to upper layers; 2> continue receiving SystemInformationBlockType12; 1> otherwise; 2> if the received values ​​of messageIdentifier and serialNumber are the same as the pairs that the warning message may currently be assembled; 3> save the received warningMessageSegment; 3> if segments of the warning message are received; 4> assemble the warning message from the received warningMessageSegment; 4> forward the received warning message, messageIdentifier, serialNumber, and / or dataCodingScheme to upper layers; 4> The assembly of a warning message for this messageIdentifier and / or serialNumber may be stopped and / or the stored information maintained for this purpose may be deleted; 3> The reception of SystemInformationBlockType12 may be continued; 2> else if the received values ​​of messageIdentifier and / or serialNumber may not be equal to at least one of the pairs for which the warning message may currently be assembled: 3> The assembly of a warning message for this messageIdentifier and / or serialNumber pair may be initiated; 3> The received warningMessageSegment may be stored; 3> The reception of SystemInformationBlockType12 may be continued;If a complete warning message is not assembled within a 3-hour period, the UE may discard the associated values ​​of the messageIdentifier and / or serialNumber for the warningMessageSegment and / or SystemInformationBlockType12. The number of warning messages that the UE can reassemble simultaneously may be a function of the UE implementation.

[0180] In one example, when SystemInformationBlockType13 is received, UE requirements related to the contents of this SystemInformationBlock may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0181] In one example, when receiving a SystemInformationBlockType14, UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType14 or SystemInformationBlockType14-NB) may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0182] In one example, when SystemInformationBlockType15 is received, UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType15 or SystemInformationBlockType15-NB) may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0183] In one example, when SystemInformationBlockType16 is received, UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType16 or SystemInformationBlockType16-NB) may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0184] In one example, when receiving SystemInformationBlockType17, the UE may: 1> include wlan-OffloadConfigCommon corresponding to the RPLMN; 2> if the UE is not configured to have rclwi-Configuration with a command set to steerToWLAN; 3> apply wlan-Id-List corresponding to the RPLMN; 2> if the UE is not configured to have wlan-OffloadConfigDedicated; 3> apply wlan-OffloadConfigCommon corresponding to the RPLMN;

[0185] In one example, when a SystemInformationBlockType18 is received, the UE may: 1> if the SystemInformationBlockType18 message contains commConfig; 2> if configured to receive side-link communication; 3> starting from the next SC cycle, as defined by sc-Period, use the resource pool indicated by commRxPool for monitoring side-link communication; 2> if configured to transmit side-link communication; 3> starting from the next SC cycle, as defined by sc-Period, use the resource pool indicated by commTxPoolNormalCommon, commTxPoolNormalCommonExt, or commTxPoolExceptional for transmitting side-link communication.

[0186] In one example, upon receiving SystemInformationBlockType19, the UE may: 1> if the SystemInformationBlockType19 message contains discConfig or discConfigPS; 2> starting from the next search cycle defined by discPeriod, use resources designated as discRxPool, discRxResourcesInterFreq, or discRxPoolPS for lateral link search monitoring; 2> if the SystemInformationBlockType19 message contains discTxPoolCommon or discTxPoolPS-Common; if the UE is in the RRC_IDLE / RRC_INACTIVE state; 3> starting from the next search cycle defined by discPeriod, use resources designated as discTxPoolCommon or discTxPoolPS-Common for lateral link search guidance; 2> If the SystemInformationBlockType19 message contains discTxPowerInfo: 3> Power information contained in discTxPowerInfo can be used for lateral link search transmission on the serving frequency; 1> If the SystemInformationBlockType19 message contains discConfigRelay: 2> If the SystemInformationBlockType19 message contains txPowerInfo: 3> Power information contained in txPowerInfo can be used for lateral link search transmission on the corresponding unserved frequency.

[0187] In one example, when receiving a SystemInformationBlockType20, UE requirements related to the contents of this SystemInformationBlock (SystemInformationBlockType20 or SystemInformationBlockType20-NB) may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0188] In one example, when receiving SystemInformationBlockType21, the UE may: 1> if the SystemInformationBlockType21 message contains sl-V2X-ConfigCommon; 2> if configured to receive V2X sidelink communication; 3> use the resource pool indicated by v2x-CommRxPool of sl-V2X-ConfigCommon for monitoring V2X sidelink communication; 2> if configured to transmit V2X sidelink communication; 3> use the resource pool indicated by v2x-CommTxPoolNormalCommon, p2x-CommTxPoolNormalCommon, v2x-CommTxPoolNormal, p2x-CommTxPoolNormal, or v2x-CommTxPoolExceptional for transmitting V2X sidelink communication; 3> For V2X side-link communication transmission, CBR measurements can be performed on the transmission resource pool(s) represented by v2x-CommTxPoolNormalCommon, v2x-CommTxPoolNormal and v2x-CommTxPoolExceptional.

[0189] In one example, when receiving a SystemInformationBlockType22-NB, UE requirements related to the contents of this SystemInformationBlock may not apply except those specified elsewhere, e.g., within procedures using system information of interest, and / or within corresponding field descriptions.

[0190] In one example, when acquiring an SI message, the UE may: 1> determine the start of the SI-window for the SI message of interest as follows: 2> determine a number n corresponding to the order of the item in the list of SI messages configured by the schedulingInfoList in SystemInformationBlockType1 for the SI message of interest; 2> determine an integer value x = (n - 1)*w, where w may be the si-WindowLength; 2> the SI-window may start at subframe #a, where a = x mod 10 in a radio frame where SFN mod T = FLOOR(x / 10), where T may be the si-Periodicity of the SI message of interest; (E-UTRAN (e.g., NR, base station) may form an SI-window of 1 ms if SIs are scheduled before subframe #5 in radio frames where SFN mod 2 = 0) 1> DL-SCH may be received using SI-RNTI from the beginning of the SI-window and / or until an SI message is received, excluding the following subframes, until the end of the SI-window where the absolute length of time is given by si-WindowLength; 2> MBSFN subframes; 2> Uplink subframes of TDD; 1> If an SI message is not received due to the end of the SI-window, reception may be repeated in the next SI-window situation for an SI message of interest.

[0191] In one example, when acquiring an SI message, a BL UE or a UE within a CE or an NB-IoT UE may: 1> determine the start of the SI-window for the SI message of interest as follows: 2> determine a number n corresponding to the order of items in the list of SI messages configured by the schedulingInfoList of the SystemInformationBlockType1-BR (or SystemInformationBlockType1-NB of NB-IoT) for the SI message of interest; 2> determine an integer value x = (n - 1)*w, where w may be si-WindowLength-BR (or si-WindowLength of NB-IoT); 2> If the UE is an NB-IoT UE: 3> The SI-window may start at subframe #0 of the radio frame where (H-SFN * 1024 + SFN) mod T = FLOOR(x / 10) + Offset, where T is the si-Periodicity of the SI message of interest, and Offset is the offset of the start of the SI-Window (si-RadioFrameOffset); 2> Otherwise: 3> The SI-window may start at subframe #0 of the radio frame where SFN mod T = FLOOR(x / 10), where T is the si-Periodicity of the SI message of interest;1> If the UE is an NB-IoT UE: 2> Starting from radio frames as provided in si-RepetitionPattern and / or subframes as provided in downlinkBitmap, the UE may receive, accumulate, and / or continue SI message transmissions on the DL-SCH from the beginning of the SI-window until the end of the SI-window given by the absolute length of time as si-WindowLength, or until the successful decoding of accumulated SI message transmissions, excluding subframes used for the transmission of NPSS, NSSS, MasterInformationBlock-NB, and / or SystemInformationBlockType1-NB. If there are not enough subframes for a single SI message transmission within radio frames as provided in si-RepetitionPattern, the UE may continue to receive SI message transmissions within radio frames following the radio frame indicated in si-RepetitionPattern;1> Otherwise: 2> From the beginning of the SI-window, SI message transmissions can be received and / or accumulated on the DL-SCH over the narrowband provided by si-Narrowband, or can continue in radio frames as provided in si-RepetitionPattern and in subframes as provided in fdd-DownlinkOrTddSubframeBitmapBR within bandwidthReducedAccessRelatedInfo until the end of the SI-window where the absolute length of time is given by si-WindowLength-BR, in radio frames as provided in si-RepetitionPattern and in subframes as provided in fdd-DownlinkOrTddSubframeBitmapBR within bandwidthReducedAccessRelatedInfo, or until the successful decoding of the accumulated SI message transmissions; 1> If SI messages cannot be decoded from accumulated SI message transmissions due to the termination of the SI-window, reception and / or accumulation of SI message transmissions on the DL-SCH may be continued in the next SI-window situation for the SI message of interest.;

[0192] In one example, when acquiring an SI message from an MBMS-dedicated cell, the UE may: 1> determine the start of the SI-window for the SI message of interest as follows: 2> determine a number n corresponding to the order of items in the list of SI messages configured by the schedulingInfoList within the SystemInformationBlockType1-MBMS for the SI message of interest; 2> determine an integer value x = (n - 1)*w, where w may be the si-WindowLength; 2> the SI-window may start at subframe #a, where a = x mod 10 in a radio frame where SFN mod T = FLOOR(x / 10), and T may be the si-Periodicity of the SI message of interest; 1> DL-SCH can be received using SI-RNTI having a value from the beginning of the SI-window until the end of the SI-window, where the absolute length of time can be given as si-WindowLength, or until an SI message is received, excluding the following subframes: 2> MBSFN subframes; 1> If an SI message is not received due to the end of the SI-window, reception can be repeated for the SI message of interest in the next SI-window situation.

[0193] As illustrated in FIG. 21, in conventional wireless technologies, a base station can be shared by multiple network operators (e.g., multiple PLMNs). When a base station is shared by multiple operators, the protocol layers of the base station (e.g., physical, MAC, RLC, PDCP, RRC, SDAP) are shared by the multiple operators sharing the base station. In the example of FIG. 21, the gNB is shared by PLMN1 and PLMN2. The gNB communicates with the AMF of the 5G core network of PLMN1 and the AMF of the 5G core network of PLMN2. The gNB utilizes wireless protocol layers and control signaling for the transmission of packets from both PLMN1 and PLMN2.

[0194] For example, when a base station (e.g., gNB, eNB, BS) is utilized by multiple network operators (e.g., multiple PLMNs), the radio resource control parameters of serving cells and / or radio devices (e.g., UEs) can be configured commonly for multiple operators. In one example, when a base station is utilized by multiple operators, multiple operators can configure common cell radio resource control parameters for the base station. In existing technologies, when a base station is shared by multiple operators, the PHY / MAC / RLC / PDCP / RRC protocol layers are shared by multiple operators. In existing network sharing technologies, common configuration parameters and decision policies for serving cells for multiple operators can increase inefficient parameter settings and inappropriate decisions when serving radio devices of different operators that may have different network control policies. The implementation of existing parameter configuration mechanisms for a base station shared by multiple operators may not be efficient. Existing network sharing technologies (e.g., base station sharing) can reduce resource utilization and mobility performance for wireless devices associated with different operators. Existing network sharing technologies can increase call rejection rates and packet transmission delays when multiple operators share a base station. To improve network performance when wireless access networks are shared, the development of improved base station sharing architectures and processes is required.

[0195] Exemplary embodiments provide an enhanced network architecture for network sharing by implementing an enhanced base station sharing architecture and call / signaling processes. In an exemplary embodiment, a base station central unit (e.g., including RRC, PDCP, and / or SDAP layers) may be a non-shared node controlled by a network operator, and a base station distributed unit (e.g., including PHY, MAC, and / or RLC layers) may be a shared node shared by multiple network operators. Exemplary embodiments implement base station decision processes when multiple network operators share a base station distributed unit while implementing their own non-shared base station central units. An exemplary embodiment introduces a new network architecture including a shared base station distributed unit communicating with one or more non-shared base station central units. This new architecture introduces new challenges requiring the implementation of enhanced call / signaling processes. The new network structure and enhanced call / signaling processes improve the communication reliability and configuration flexibility of the wireless network. Exemplary embodiments enable multiple operators to apply individual parameters configured based on their individual policies by supporting different base station central units that individually determine their configuration parameters for a shared base station distributed unit. Exemplary embodiments can reduce connection failure rates and / or wireless quality degradation issues by introducing a shared base station distributed unit and can separate non-shared base station central units for multiple operators. Exemplary embodiments can improve communication reliability by supporting the sharing of a base station distributed unit for multiple base station central units of multiple operators.

[0196] Exemplary embodiments provide an enhanced network architecture for network sharing, e.g., a base station sharing architecture and processes. In an exemplary embodiment, a base station central unit including RRC, PDCP, and / or SDAP may be shared by a first set of one or more network operators, and a base station distributed unit may be a shared node shared by a second set of one or more network operators different from the first set of network operators. The implementation of such a complex network architecture requires the implementation of an enhanced call / signaling flow. An exemplary embodiment implements enhanced call / signaling processes to enable the current network architecture.

[0197] A wireless access network may be shared (e.g., utilized) by multiple operators (e.g., multiple PLMNs, multiple service operators, etc.). In one example, when a functional partition of gNBs (e.g., base station, eNB, RNC, etc.) is configured on multiple units (e.g., at least one base station central unit (e.g., gNB-CU) and / or at least one base station distributed unit (e.g., gNB-DU)), one of the partitioned units (e.g., at least one of the gNB-CU and / or gNB-DU) may be shared by multiple operators. In one example, when a gNB-DU is connected to multiple gNB-CUs (e.g., base station central unit; first gNB-CU and second gNB-CU), the gNB-DU may select a gNB-CU for a wireless device connected to the gNB-DU and / or may select a gNB-CU based on the load status of the gNB-CU. In conventional wireless technologies, a wireless device may transmit an RRC message. A gNB-DU receiving an RRC message may forward the RRC message to a gNB-CU that may be unsuitable for the wireless device (e.g., a gNB-CU that may not support the wireless device). The implementation of the existing RRC message delivery mechanism in the gNB-DU may not be efficient. Existing technology may increase connection latency and packet transmission delays of wireless devices and / or reduce connection reliability and mobility performance of wireless devices. Existing technology may increase call rejection rates and / or packet transmission delays when multiple gNB-CUs (e.g., multiple gNB-CUs operated by different operators) are connected to a single gNB-DU (e.g., a shared gNB-DU).

[0198] Exemplary embodiments improve the network node selection mechanism of a gNB-DU when multiple gNB-CUs are connected to a single gNB-DU (e.g., multiple gNB-CUs share a single gNB-DU, multiple operators share a base station and / or serving cell, multiple operators share a single gNB-DU, etc.). Exemplary embodiments improve the gNB-DU to support multiple gNB-CUs (e.g., multiple service operators, multiple operators, multiple PLMNs) by providing a gNB-CU selection mechanism of the gNB-DU for a wireless device. Exemplary embodiments improve the wireless device to provide gNB-CU information (e.g., gNB-CU identifier, gNB-identifier, gNB-CU address, gNB address, tracking area identifier, registration area identifier, etc.) through an uplink message (e.g., RRC message) for gNB-CU selection of the gNB-DU. Exemplary embodiments enhance a wireless device to provide service operator information (e.g., PLMN identifier, operator identifier, service operator identifier, cell identifier for the service operator, etc.) via an uplink message (e.g., RRC message) for selecting a gNB-CU of a gNB-DU. Exemplary embodiments enhance a wireless device to provide a cell identifier for a single service operator via an uplink message (e.g., RRC message) for selecting a core node of a gNB (e.g., AMF) and / or a gNB-CU of a gNB-DU (e.g., where multiple cell identifiers are configured for a single cell shared by multiple service operators).

[0199] Exemplary embodiments can reduce connection latency and packet transmission delay of wireless devices and / or increase connection reliability and mobility performance of wireless devices by introducing a gNB-CU (or core node, AMF) selection mechanism of a gNB-DU (or base station, gNB) for wireless devices. Exemplary embodiments can improve connection latency and communication reliability by supporting a gNB-CU selection mechanism of a gNB-DU for wireless devices when a single gNB-DU is connected to multiple gNB-CUs (e.g., of multiple service operators). Exemplary embodiments can improve connection latency and communication reliability by supporting a core node (AMF) selection mechanism of a base station (gNB) for wireless devices when a single gNB is connected to multiple AMFs (e.g., of multiple service operators).

[0200] In an exemplary embodiment, a gNB may be interpreted as an eNB, RNC, home eNB, home gNB, and / or any type of base station or access point. In an exemplary embodiment, a gNB-CU may be interpreted as a centralized base station (e.g., eNB-CU, RNC, access point center unit, etc.). In an exemplary embodiment, a gNB-DU may be interpreted as a distributed base station (e.g., eNB-DU, RRH, Transceiver / Receiver Point (TRP), access point distributed unit, etc.).

[0201] In one example, as illustrated in the exemplary drawings of FIG. 16, 17, 18, 19, 20, 21, 22, and / or FIG. 23, one or more base station central units (e.g., gNB-CU, central unit, CU, etc.) may be connected to one or more base station distributed units (e.g., gNB-DU, distributed unit, DU, etc.) through one or more interfaces (e.g., F1 interface). In one example, the base station may include one or more base station central units and one or more base station distributed units. In one example, a first base station central unit (e.g., a first gNB-CU, a first central unit, a first CU, a first access point CU, etc.) may be connected to a base station distributed unit (e.g., a gNB-DU, a distributed unit, a DU, an access point DU, etc.) through at least one first F1 interface (e.g., an F1 user plane (F1-U), an F1 control plane (F1-C)), and a second base station central unit (e.g., a second gNB-CU, a second central unit, a second CU, a second access point CU, etc.) may be connected to a base station distributed unit (e.g., connected to the first base station central unit) through at least one second F1 interface. In one example, a base station (e.g., a gNB) may include a first gNB-CU, a second gNB-CU, and / or a gNB-DU. In one example, the first base station may include a first gNB-CU and / or a gNB-DU. In one example, the second base station may include a second gNB-CU and / or gNB-DU.

[0202] In one example, the first gNB-CU and / or the second gNB-CU may include upper-layer control plane functions (e.g., RRC, etc.) and / or upper-layer user plane functions (e.g., SDAP, PDCP, etc.). The gNB-DU may include lower-layer functions (e.g., RLC, MAC, PHY, etc.). In one example, the first gNB-CU and / or the second gNB-CU may include at least an RRC lower-layer function. In one example, the gNB-DU may include at least a wireless transmitter and / or receiver for communication with wireless devices. In one example, the first gNB-CU and / or the second gNB-CU may include upper-layer functions (e.g., at least one of RRC, PDCP, SDAP, RLC, MAC, etc.). In one example, the gNB-DU may include lower-layer functions (e.g., at least one of PHY, MAC, etc.).

[0203] In one example, the first gNB-CU and / or the second gNB-CU can transmit / receive PDCP packets (e.g., PDCP PDUs and / or PDCP SDUs) to / from the gNB-DU via an F1 interface (e.g., at least one first F1 interface and / or at least one second F1 interface). The gNB-DU can forward (transmit) / receive PDCP packets to / from a wireless device via a wireless interface (e.g., a Uu interface, wireless). The gNB-DU can forward packets (e.g., PDCP packets, RLC packets, MAC packets) from the wireless device to the gNB-CU (e.g., the first gNB-CU or the second gNB-CU) and / or forward packets (e.g., PDCP packets, RLC packets, MAC packets) from the gNB-CU (e.g., the first gNB-CU or the second gNB-CU) to the wireless device. In one example, PDCP packets may be generated and transmitted by a wireless device and / or may be generated and transmitted by a gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU).

[0204] In one example, the first gNB-CU and / or the second gNB-CU may include a base station central unit control plane (e.g., gNB-CU-CP) and / or a base station central unit user plane (e.g., gNB-CU-UP). In one example, the gNB-CU-CP may include at least one RRC sub-layer function. The gNB-CU-UP may include SDAP sub-layer functions, PDCP sub-layer functions, etc. The gNB-CU-CP and the gNB-CU-UP may be connected to each other through an interface (e.g., E1 interface, E1-U, E1-C, etc.). In one example, a gNB-CU-CP (e.g., a first gNB-CU-CP of a first gNB-CU and / or a second gNB-CU-CP of a second gNB-CU) may be connected to a gNB-DU through an F1 control plane interface (F1-CP) (e.g., a first F1-CP of at least one first F1 interface and / or a second F1-CP of at least one second F1 interface). In one example, a gNB-CU-UP (e.g., a first gNB-CU-UP of a first gNB-CU and / or a second gNB-CU-UP of a second gNB-CU) may be connected to a gNB-DU through an F1 user plane interface (F1-UP) (e.g., a first F1-UP of at least one first F1 interface and / or a second F1-UP of at least one second F1 interface).

[0205] In one example, a gNB-DU may establish interface connections (e.g., F1 connection, F1 control plane connection, F1 user plane connection) with a plurality of gNB-CUs. The plurality of gNB-CUs may include a first gNB-CU and a second gNB-CU. In one example, the first gNB-CU may support (e.g., serve, belong to, provide, etc.) a first mobile phone system network (PLMN). In one example, the second gNB-CU may support (e.g., serve, belong to, provide, etc.) a second PLMN. In an exemplary embodiment, supporting a PLMN (e.g., the first PLMN, the second PLMN) may be interpreted as allowing / configuring to use a corresponding network node (e.g., the first gNB-CU, the second gNB-CU), a corresponding resource, and / or a corresponding cell for said PLMN. A network node supporting a PLMN can be interpreted as resources of the network node that can be used to operate the PLMN and / or service the wireless devices of the PLMN. A network node supporting a PLMN can be interpreted as the PLMN including the network node.

[0206] A PLMN may be a combination of wireless communication services provided by at least one operator in at least one country. A PLMN may include one or more cellular technologies, such as GSM / 2G, UMTS / 3G, LTE / 4G, 5G, etc., provided by at least one operator within at least one country. A PLMN may be referred to as a cellular network.

[0207] In one example, as illustrated in FIG. 41, a gNB-DU may be shared by a first PLMN and a second PLMN. The first gNB-CU and / or the second gNB-CU may be a gNB-CU that is not shared. The first gNB-CU may not be shared with the second PLMN. The second gNB-CU may not be shared with the first PLMN. Sharing network nodes (e.g., gNB, gNB-CU, gNB-DU, etc.) with PLMNs can be interpreted as sharing / using the resources of network nodes using PLMNs.

[0208] In one example, the first gNB-CU may be shared by the first PLMN and at least one third PLMN. In one example, the second gNB-CU may be shared by the second PLMN and at least one fourth PLMN. In one example, the gNB-DU may be shared by a plurality of PLMNs (e.g., a plurality of operators) including at least one of the first PLMN, the second PLMN, at least one third PLMN, and / or at least one fourth PLMN.

[0209] In one example, as illustrated in FIGS. 24, 25, 26, 27, 28, 29, 30 and / or 31, the first gNB-CU may transmit (or send) a first connection message to the gNB-DU. The first connection message may include an F1 setup response message in response to an F1 setup request message transmitted to the first gNB-CU by the gNB-DU. The F1 setup request message and the F1 setup response message may be messages for an F1 setup procedure to establish an F1 interface (e.g., at least one first F1 interface) between the first gNB-CU and the gNB-DU. In one example, the first connection message may include a gNB-CU configuration update message for configuration updates (e.g., configurations of the gNB-CU and / or gNB-DU) by the gNB-CU (e.g., the first gNB-CU). In response to receiving a gNB-CU configuration update message, the gNB-DU may transmit a gNB-CU configuration update confirmation message (or gNB-CU configuration update failure message) to the first gNB-CU, which may indicate that one or more configurations of the gNB-CU configuration update message (e.g., the first connection message) are applied (accepted) or failed (rejected) at the gNB-DU. The gNB-CU configuration update message and the gNB-CU configuration update confirmation message (and / or gNB-CU configuration update failure message) may be messages for a gNB-CU configuration update procedure. In one example, the first connection message may include a gNB-DU configuration update confirmation message (or gNB-DU configuration update failure message) in response to a gNB-DU configuration update message that may be transmitted to the first gNB-CU by the gNB-DU.The gNB-DU configuration update message and the gNB-DU configuration update confirmation message (and / or the gNB-DU configuration update failure message) may be messages for the gNB-DU configuration update procedure to update configurations (e.g., configurations of gNB-CU and / or gNB-DU) by gNB-DU.

[0210] In one example, as illustrated in the exemplary drawings of FIG. 32, FIG. 34, and / or FIG. 35, the first connection message may include a first PLMN identifier of a first PLMN supported (e.g., serviced) by a first gNB-CU. In an exemplary embodiment, supporting a PLMN (e.g., the first PLMN) may be interpreted as allowing / configuring to use a corresponding network node (e.g., the first gNB-CU), a corresponding resource, and / or a corresponding cell for the PLMN. In one example, the first PLMN may include a first gNB-CU. In one example, the first PLMN identifier may identify (or indicate) the PLMN of an operator (e.g., the first service operator), the operator (e.g., the first service operator), and / or the network serviced by the operator (e.g., the first service operator). The operator may be interpreted as a service operator / provider and / or a network operator / provider. In one example, the first connection message may further include at least one of the following: a message type of the first connection message; a transaction identifier (e.g., transaction ID) of a corresponding procedure (e.g., F1 setup procedure, gNB-CU configuration update procedure, gNB-DU configuration update procedure, etc.); a gNB-CU identifier of the first gNB-CU; a gNB-CU name of the first gNB-CU; one or more first cell identifiers of one or more first cells to be activated (e.g., cell global identifier (NR CGI), physical layer cell identifier (NR PCI)); and one or more second cell identifiers of one or more second cells to be deactivated (e.g., cell global identifier (NR CGI), physical layer cell identifier (NR PCI)). In one example, the first connection message may further include one or more serving cell identifiers of one or more serving cells associated with the first PLMN (e.g., one or more cells supporting the first PLMN and / or one or more cells used for the first PLMN).In one example, one or more serving cells may be cells of gNB-DU.

[0211] In one example, as illustrated in the exemplary drawing of FIG. 33, a first procedure initiation message (e.g., the first connection message may be a response message to the first procedure initiation message), e.g., an F1 setup request message and / or a gNB-DU configuration update message may include at least one of the following: a message type of the first procedure initiation message; a transaction identifier (e.g., transaction ID) of the corresponding procedure (e.g., F1 setup procedure, gNB-DU configuration update procedure, etc.); a gNB-DU identifier of the gNB-DU; a gNB-DU name of the gNB-DU; and serving cell configuration parameters of one or more serving cells of the gNB-DU (e.g., for adding / modifying / deleting / activating). In one example, the serving cell configuration parameters may include at least one of the following: serving cell information of the serving cell; gNB-DU system information of the serving cell. Serving cell information may include at least one of a cell identifier (e.g., NR CGI, NR PCI, previous NR CGI, previous NR PCI), a trace area code, a trace area identifier, one or more PLMN identifiers of one or more PLMNs supported by the serving cell, FDD configuration parameters (e.g., uplink frequency band (UL ARFCN), downlink frequency band (DL ARFCN), UL transmission bandwidth, DL transmission bandwidth, etc.), TDD configuration parameters (e.g., frequency band (ARFCN), transmission bandwidth, etc.), LAA configuration parameters (e.g., subframe type 3 configuration parameters), supplementary uplink (SUL) information, measurement timing configuration parameters, etc. In one example, gNB-DU system information may include at least one of a serving cell's master information block (MIB) message, a serving cell's system information block type 1 (SIB1) message, etc.

[0212] In one example, as illustrated in the exemplary drawing of FIG. 36, a first procedure response message (e.g., a response message to a first connection message), e.g., a gNB-CU configuration update confirmation message and / or a gNB-CU configuration update failure message may include at least one of the following: a message type of the first procedure response message; a transaction identifier of the corresponding procedure (e.g., a gNB-CU configuration update procedure, etc.) (e.g., a transaction ID); a gNB-DU identifier of the gNB-DU; a gNB-DU name of the gNB-DU; one or more cell identifiers of one or more cells that were successfully / failed to be activated or modified / added / deleted (e.g., NR CGI, NR PCI); a cause of successful / failed activation or a cause of modification / addition / deletion, etc.

[0213] In one example, based on a first connection message, the gNB-DU may configure one or more system parameters including at least one of F1 interface configuration parameters (e.g., one or more tunnel identifier configurations of one or more tunnels for one or more tunnels for the first gNB-CU), cell configuration parameters of one or more serving cells associated with the first gNB-CU (e.g., one or more serving cells used for the first gNB-CU and / or the first PLMN), resource configuration parameters (e.g., wireless resource configuration parameters), hardware configuration parameters (e.g., CPU, RAM, bus resources for the first gNB-CU and / or the first PLMN), one or more configuration parameters for one or more wireless devices, etc.

[0214] In one example, the second gNB-CU may transmit (send) a second connection message to the gNB-DU. The second connection message may include an F1 setup response message in response to an F1 setup request message transmitted to the second gNB-CU by the gNB-DU. The F1 setup request message and the F1 setup response message may be messages for the F1 setup procedure to establish an F1 interface (e.g., at least one second F1 interface) between the second gNB-CU and the gNB-DU. In one example, the second connection message may include a gNB-CU configuration update message for configuration updates (e.g., configurations of the gNB-CU and / or gNB-DU) by the gNB-CU (e.g., the second gNB-CU). In response to receiving a GNB-CU configuration update message, the gNB-DU may transmit a gNB-CU configuration update confirmation message (or gNB-CU configuration update failure message) to the second gNB-CU, which may indicate that one or more configurations of the gNB-CU configuration update message (e.g., the second connection message) are applied (accepted) or failed (rejected) at the gNB-DU. The gNB-CU configuration update message and the gNB-CU configuration update confirmation message (and / or gNB-CU configuration update failure message) may be messages for a gNB-CU configuration update procedure. In one example, the second connection message may include a gNB-DU configuration update confirmation message (or gNB-DU configuration update failure message) in response to a gNB-DU configuration update message that may be transmitted by the second gNB-CU to the gNB-DU. The gNB-DU configuration update message and the gNB-DU configuration update confirmation message (and / or the gNB-DU configuration update failure message) may be messages for the gNB-DU configuration update procedure to update configurations (e.g., configurations of gNB-CU and / or gNB-DU) by gNB-DU.

[0215] In one example, the second connection message may include a second PLMN identifier of a second PLMN supported (e.g., serviced) by a second gNB-CU. In an exemplary embodiment, supporting a PLMN (e.g., the second PLMN) may be interpreted as allowing / configuring to use a corresponding network node (e.g., the second gNB-CU), a corresponding resource, and / or a corresponding cell for the PLMN. In one example, the second PLMN may include a second gNB-CU. In one example, the second PLMN identifier may identify (or indicate) a PLMN of an operator (e.g., the second service operator), an operator (e.g., the second service operator), and / or a network serviced by an operator (e.g., the second service operator). In one example, the second connection message may further include at least one of the following: a message type of the second connection message; a transaction identifier (e.g., transaction ID) of a corresponding procedure (e.g., F1 setup procedure, gNB-CU configuration update procedure, gNB-DU configuration update procedure, etc.); a gNB-CU identifier of the second gNB-CU; a gNB-CU name of the second gNB-CU; one or more third cell identifiers of one or more third cells to be activated (e.g., cell global identifier (NR CGI), physical layer cell identifier (NR PCI)); and one or more fourth cell identifiers of one or more fourth cells to be deactivated (e.g., cell global identifier (NR CGI), physical layer cell identifier (NR PCI)). In one example, the second connection message may further include one or more serving cell identifiers of one or more serving cells associated with the second PLMN (e.g., one or more cells supporting the second PLMN and / or one or more cells used for the second PLMN). In one example, one or more serving cells may be cells of the gNB-DU.

[0216] In one example, a second procedure initiation message (e.g., the second connection message may be a response message to the second procedure initiation message), e.g., an F1 setup request message and / or a gNB-DU configuration update message, may include at least one of the following: a message type of the second procedure initiation message; a transaction identifier (e.g., transaction ID) of the corresponding procedure (e.g., F1 setup procedure, gNB-DU configuration update procedure, etc.); a gNB-DU identifier of the gNB-DU; a gNB-DU name of the gNB-DU; and serving cell configuration parameters of one or more cells of the gNB-DU (e.g., for adding / modifying / deleting / activating). In one example, the serving cell configuration parameters may include at least one of the following: serving cell information of the serving cell; gNB-DU system information of the serving cell. Serving cell information may include at least one of a cell identifier (e.g., NR CGI, NR PCI, previous NR CGI, previous NR PCI), a trace area code, a trace area identifier, one or more PLMN identifiers of one or more PLMNs supported by the serving cell, FDD configuration parameters (e.g., uplink frequency band (UL ARFCN), downlink frequency band (DL ARFCN), UL transmission bandwidth, DL transmission bandwidth, etc.), TDD configuration parameters (e.g., frequency band (ARFCN), transmission bandwidth, etc.), LAA configuration parameters (e.g., subframe type 3 configuration parameters), supplementary uplink (SUL) information, measurement timing configuration parameters, etc. In one example, gNB-DU system information may include at least one of a serving cell's master information block (MIB) message, a serving cell's system information block type 1 (SIB1) message, etc.

[0217] In one example, a second procedure response message (a response message to a second connection message), e.g., a gNB-CU configuration confirmation message and / or a gNB-CU configuration failure message, may include at least one of the following: a message type of the second procedure response message; a transaction identifier of the corresponding procedure (e.g., a gNB-CU configuration update procedure, etc.) (e.g., a transaction ID); a gNB-DU identifier of the gNB-DU; a gNB-DU name of the gNB-DU; one or more cell identifiers of one or more cells that were successfully / failed to activate or were modified / added / deleted (e.g., NR CGI, NR PCI); the cause of the success / failure of activation or the cause of the modification / addition / deletion.

[0218] In one example, based on a second connection message, the gNB-DU may configure one or more system parameters including at least one of F1 interface configuration parameters (e.g., configurations of one or more tunnel identifiers of one or more tunnels for the second gNB-CU), cell configuration parameters of one or more serving cells associated with the second gNB-CU (e.g., one or more serving cells used for the second gNB-CU and / or the second PLMN), resource configuration parameters (e.g., wireless resource configuration parameters), hardware configuration parameters (e.g., CPU, RAM, bus resources for the second gNB-CU and / or the second PLMN), etc.

[0219] In one example, based on a first connection message and / or a second connection message, the gNB-DU may support (e.g., serve, provide resources, etc.) the first PLMN and the second PLMN through the serving cell(s) of the gNB-DU. In one example, one or more first cells of the serving cells of the gNB-DU may support the first PLMN (and / or the first gNB-CU), or one or more second cells of the serving cells of the gNB-DU may support the second PLMN (and / or the second gNB-CU). In one example, one or more third cells of the gNB-DU may support both the first PLMN and the second PLMN. In one example, in response to receiving a first connection message, the gNB-DU may transmit to the first gNB-CU one or more first cell identifiers of one or more first cells supporting a first PLMN, and / or one or more third cell identifiers of one or more third cells supporting a first PLMN and a second PLMN. In one example, in response to receiving a second connection message, the gNB-DU may transmit to the second gNB-CU one or more second cell identifiers of one or more second cells supporting a second PLMN, and / or one or more third cell identifiers of one or more third cells supporting a first PLMN and a second PLMN.

[0220] In one example, a PLMN identifier (e.g., a first PLMN identifier and / or a second PLMN identifier) ​​may include at least one of an operator identifier of a service operator, a network identifier of a network serviced by a service operator, a service area identifier of a service area serviced by a service operator, and an identifier (identity) identifying a group of PLMNs / operators / service operators / networks / network areas / infrastructures. In one example, a PLMN (e.g., a first PLMN and / or a second PLMN) may be interpreted as at least one of an operator, a service operator, a network serviced by a service operator, a network area, a service area serviced by a service operator, a group of infrastructures, etc.

[0221] In one example, in response to receiving a second connection message, the gNB-DU may transmit (send) to the first gNB-CU a second PLMN identifier of a second PLMN supported (or serviced) by the gNB-DU (and / or serving cell of the gNB-DU), or transmit to the first gNB-CU a second gNB-CU identifier (e.g., second gNB-CU name, second gNB-CU IP address, etc.) of the second gNB-CU (e.g., the second gNB-CU identifier may indicate that the gNB-DU (and / or serving cell of the gNB-DU) services the second gNB-CU). In one example, in response to receiving a second connection message, the gNB-DU may transmit (transmit) one or more first cell identifiers of one or more first cells supporting a first PLMN, one or more second cell identifiers of one or more second cells supporting a second PLMN, and / or one or more third cell identifiers of one or more third cells supporting a first PLMN and a second PLMN.

[0222] In one example, in response to receiving a second connection message and / or based on a first connection message, the gNB-DU may transmit (send) to the second gNB-CU a first PLMN identifier of a first PLMN supported (or serviced) by the gNB-DU (and / or serving cell of the gNB-DU), or transmit to the second gNB-CU a first gNB-CU identifier (and / or first gNB-CU name, first gNB-CU IP address, etc.) of the first gNB-CU (e.g., the first gNB-CU identifier may indicate that the gNB-DU (and / or serving cell of the gNB-DU) services the first gNB-CU). In one example, in response to receiving a second connection message, the gNB-DU may transmit (send) to the second gNB-CU one or more first cell identifiers of one or more first cells supporting the first PLMN, one or more second cell identifiers of one or more second cells supporting the second PLMN, and / or one or more third cell identifiers of one or more third cells supporting the first PLMN and the second PLMN.

[0223] In one example, based on a first connection message and / or a second connection message, the gNB-DU may transmit (e.g., broadcast) at least one third message (e.g., one or more system information blocks, at least one system information block) comprising at least one of a first PLMN identifier and / or a second PLMN identifier. At least one third message may be transmitted via a wireless interface (e.g., via serving cells of the gNB-DU and / or a wireless interface). In one example, at least one third message may be one or more system information blocks (e.g., a master information block, a system information block type 1, a system information block type 2, a system information block type 3, etc.) (and / or may include them). In one example, at least one third message may be one or more radio resource control (RRC) messages for a radio device (e.g., an RRC connection setup message, an RRC connection resumption message, an RRC connection reconfiguration message, an RRC connection re-establishment message, etc.) (and / or may include the same). In one example, at least one third message may be transmitted through serving cells of a gNB-DU. In one example, at least one third message may be transmitted through at least one of one or more first cells supporting a first PLMN, one or more second cells supporting a second PLMN, and / or one or more third cells supporting both the first PLMN and the second PLMN.

[0224] In one example, at least one of the at least one third message transmitted through one or more third cells may include a first PLMN identifier and / or a second PLMN identifier (e.g., both the first PLMN identifier and the second PLMN identifier, or either the first PLMN identifier and the second PLMN identifier) ​​indicating that one or more third cells support (e.g., service, belong to, provide resources, etc.) the first PLMN (e.g., the first gNB-CU) and / or the second PLMN (e.g., the second gNB-CU).

[0225] In one example, the first of at least one third message transmitted through one or more first cells may include a first PLMN identifier indicating that one or more first cells support (e.g., service, belong to, provide resources, etc.) the first PLMN (e.g., the first gNB-CU). In one example, the second of at least one third message transmitted through one or more second cells may include a second PLMN identifier indicating that one or more second cells support (e.g., service, belong to, provide resources, etc.) the second PLMN (e.g., the second gNB-CU).

[0226] In one example, individual messages for different PLMNs (and / or different gNB-CUs) (e.g., distinct system information blocks, RRC messages) may be transmitted as at least one third message. In one example, the first individual message of at least one third message may include a first PLMN identifier and / or a first serving cell identifier of the serving cell to which the first individual message (and / or the second individual message) is transmitted. In one example, the second individual message of at least one third message may include a second PLMN identifier and / or a second serving cell identifier of the serving cell to which the second individual message (and / or the first individual message) is transmitted.

[0227] In one example, different cell identifiers (e.g., a first cell identifier and a second cell identifier) ​​for a serving cell (e.g., physically a single cell; e.g., having different global cell identifiers for multiple PLMNs) may be configured for different PLMNs (e.g., a first PLMN and a second PLMN) (e.g., when the serving cell is used to support / service the first PLMN and the second PLMN). In one example, the different cell identifiers may include a global cell identifier (GCI) and / or a cell global identifier (CGI), etc. In one example, different cell identifiers (e.g., a third cell identifier and a fourth cell identifier) ​​for a serving cell (e.g., a physically single cell) may be configured for different gNB-CUs and / or different gNBs (e.g., a first gNB-CU and a second gNB-CU; a first gNB of the first gNB-CU and a second gNB of the second gNB-CU) (e.g., when the serving cell is used by the first gNB-CU and the second gNB-CU). In one example, at least one third message may include at least one cell identifier of the serving cell to which the at least one third message is transmitted (e.g., including a first cell identifier for the first PLMN and / or a second cell identifier for the second PLMN). In one example, at least one third message may include at least one cell identifier of the serving cell to which the at least one third message is transmitted (including a third cell identifier for a first gNB-CU / first gNB and / or a fourth cell identifier for a second gNB-CU / second gNB). In one example, at least one cell identifier may include at least one of a cell identity, a cell ID, a physical layer cell identifier, a global cell identifier, etc.

[0228] In one example, at least one third message may include at least one trace area code (TAC) of a serving cell (and / or associated therewith) to which at least one third message may be transmitted. In one example, at least one TAC may be configured for different PLMNs (e.g., a first TAC of at least one TAC may be configured for a first PLMN; and / or a second TAC of at least one TAC may be configured for a second PLMN). In one example, at least one TAC may be configured for different gNB-CUs (e.g., a third TAC of at least one TAC may be configured for a first gNB-CU; and / or a fourth TAC of at least one TAC may be configured for a second gNB-CU). In one example, at least one TAC may include at least one of a first TAC, a second TAC, a third TAC, and / or a fourth TAC.

[0229] In one example, at least one third message may include at least one tracking area identifier (TAI) of a serving cell (and / or associated therewith) to which at least one third message may be transmitted. In one example, at least one TAI may be configured for different PLMNs (e.g., a first TAI of at least one TAI may be configured for a first PLMN; and / or a second TAI of at least one TAI may be configured for a second PLMN). In one example, at least one TAI may be configured for different gNB-CUs (e.g., a third TAI of at least one TAI may be configured for a first gNB-CU; and / or a fourth TAI of at least one TAI may be configured for a second gNB-CU). In one example, at least one TAI may include at least one of a first TAI, a second TAI, a third TAI, and / or a fourth TAI.

[0230] In one example, at least one third message may include one or more registration area codes (RACs) of a serving cell (and / or associated therewith) to which at least one third message may be transmitted. In one example, at least one RAC may be configured for different PLMNs (e.g., a first RAC of at least one RAC may be configured for a first PLMN; and / or a second RAC of at least one TAC may be configured for a second PLMN). In one example, at least one RAC may be configured for different gNB-CUs (e.g., a third RAC of at least one RAC may be configured for a first gNB-CU; and / or a fourth RAC of at least one RAC may be configured for a second gNB-CU). In one example, at least one RAC may include at least one of a first RAC, a second RAC, a third RAC, and / or a fourth RAC.

[0231] In one example, at least one third message may include at least one registration area identifier (RAI) of a serving cell to which at least one third message may be transmitted. In one example, at least one RAI may be configured for different PLMNs (e.g., a first RAI of at least one RAI may be configured for a first PLMN; and / or a second RAI of at least one RAI may be configured for a second PLMN). In one example, at least one RAI may be configured for different gNB-CUs (e.g., a third RAI of at least one RAI may be configured for a first gNB-CU; and / or a fourth RAI of at least one RAI may be configured for a second gNB-CU). In one example, at least one RAI may include at least one of a first RAI, a second RAI, a third RAI, and / or a fourth RAI.

[0232] In one example, at least one third message may include a first gNB-CU identifier of the first gNB-CU and / or a second gNB-CU identifier of the second gNB-CU. The first gNB-CU identifier may indicate that the serving cell to which the at least one third message is transmitted serves the first gNB-CU. The second gNB-CU identifier may indicate that the serving cell to which the at least one third message is transmitted serves the second gNB-CU.

[0233] In one example, at least one third message may include a first gNB identifier (e.g., a first base station identifier) ​​of a first gNB (e.g., a first base station) comprising a first gNB-CU and a gNB-DU. In one example, at least one third message may include a second gNB identifier (e.g., a second base station identifier) ​​of a second gNB (e.g., a second base station identifier) ​​comprising a second gNB-CU and a gNB-DU. In one example, the first gNB identifier (e.g., associated with the first gNB-CU and / or the first PLMN) and the second gNB identifier (e.g., associated with the second gNB-CU and / or the second PLMN) may be for a gNB (e.g., a base station; the first gNB and the second gNB are the same gNB) comprising a first gNB-CU, a second gNB-CU, and a gNB-DU. The first gNB identifier may be for the first gNB-CU and / or the first PLMN. The second gNB identifier may be for the second gNB-CU and / or the second PLMN. The first gNB identifier may indicate that the serving cell to which at least one third message is transmitted serves the first gNB, the first gNB-CU, and / or the first PLMN. The second gNB identifier may indicate that the serving cell to which at least one third message is transmitted serves the second gNB, the second gNB-CU, and / or the second PLMN.

[0234] In one example, at least one third message may include at least one RAN notification region (RNA) identifier (e.g., for a radio device in an RRC inactive state) of a serving cell (and / or associated therewith) to which at least one third message may be transmitted. In one example, at least one RNA identifier may be configured for different PLMNs (e.g., a first RNA identifier of at least one RNA identifier may be configured for a first PLMN; and / or a second RNA identifier of at least one RNA identifier may be configured for a second PLMN). In one example, at least one RNA identifier may be configured for different gNB-CUs (e.g., a third RNA identifier of at least one RNA identifier may be configured for a first gNB-CU; and / or a fourth RNA identifier of at least one RNA identifier may be configured for a second gNB-CU). In one example, at least one RNA identifier may include at least one of a first RNA identifier, a second RNA identifier, a third RNA identifier, and / or a fourth RNA identifier.

[0235] In one example, at least one third message may include at least one RAN area identifier (e.g., for a wireless device in an RRC-inactive state) of a serving cell (and / or associated therewith) to which at least one third message may be transmitted. In one example, at least one RAN area identifier may be configured for different PLMNs (e.g., a first RAN area identifier of at least one RAN area identifier may be configured for a first PLMN; and / or a second RAN area identifier of at least one RAN area identifier may be configured for a second PLMN). In one example, at least one RAN area identifier may be configured for different gNB-CUs (e.g., a third RAN area identifier of at least one RAN area identifier may be configured for a first gNB-CU; and / or a fourth RAN area identifier of at least one RAN area identifier may be configured for a second gNB-CU). In one example, at least one RAN region identifier may include at least one of a first RAN region identifier, a second RAN region identifier, a third RAN region identifier, and / or a fourth RAN region identifier.

[0236] In one example, at least one third message may include at least one resumption identifier (e.g., for a wireless device in an RRC-inactive state) for a serving cell (and / or associated therewith) to which at least one third message may be transmitted. In one example, at least one resumption identifier may be configured for different PLMNs (e.g., a first resumption identifier of at least one resumption identifier may be for a first PLMN; and / or a second resumption identifier of at least one resumption identifier may be for a second PLMN). In one example, at least one resumption identifier may be configured for different gNB-CUs (e.g., a third resumption identifier of at least one resumption identifier may be for a first gNB-CU; and / or a fourth resumption identifier of at least one resumption identifier may be for a second gNB-CU). In one example, at least one resumption identifier may include at least one of a first resumption identifier, a second resumption identifier, a third resumption identifier, and / or a fourth resumption identifier.

[0237] In one example, at least one third message may include at least one of a cell limit information element (IE), frequency in IE, closed subscriber group (CSG) indication, CSG identifier (e.g., CSG identity), cell selection IE including q-RxLevMin and / or q-RxLevMinOffset, frequency band information including p-Max, additionalPmax value and / or additionalSpectrumEmission value, scheduling information, TDD configuration information, system information window length, system information value tag, etc., for a serving cell in which at least one third message is received.

[0238] In one example, the gNB-DU can configure at least one third message and / or transmit (e.g., broadcast) at least one third message through a wireless interface (e.g., through serving cells of the gNB-DU and / or through a wireless interface).

[0239] In one example, the gNB-DU may configure at least one third message and / or transmit at least one third message to the first gNB-CU and / or the second gNB-CU through an F1 interface (e.g., at least one first F1 interface and / or at least one second F1 interface; e.g., through a gNB-DU configuration update message, an F1 setup request message, a gNB-CU configuration update confirmation message, a UL RRC message delivery message, a system information transmission message, etc.) (if the first gNB-CU is a master CU, the gNB-DU transmits at least one third message to the first gNB-CU). Based on at least one third message received from the gNB-DU, the first gNB-CU and / or the second gNB-CU may transmit at least one third message to the gNB-DU through an F1 interface (e.g., at least one first F1 interface and / or at least one second F1 interface; e.g., through a gNB-CU configuration update message, an F1 setup response message, a gNB-DU configuration update confirmation message, a DL RRC message delivery message, a system information delivery message, etc.) (if the first gNB-CU is a master CU, the first gNB-CU transmits at least one third message to the gNB-DU). In one example, in response to receiving at least one third message from the first gNB-CU and / or the second gNB-CU, the gNB-DU may transmit (and / or broadcast) at least one third message through a wireless interface (e.g., through serving cells of the gNB-DU and / or a wireless interface).

[0240] In one example, the gNB-DU may configure one or more parameters of at least one third message and / or transmit one or more parameters of at least one third message to the first gNB-CU and / or the second gNB-CU via an F1 interface (e.g., at least one first F1 interface and / or at least one second F1 interface; e.g., via a gNB-CU configuration update message, an F1 setup request message, a gNB-DU configuration update confirmation message, a UL RRC message delivery message, a system information delivery message, etc.) (if the first gNB-CU is a master CU, the gNB-DU transmits one or more parameters of at least one third message to the first gNB-CU). Based on one or more parameters of at least one third message, the first gNB-CU and / or the second gNB-CU may transmit at least one third message to the gNB-DU through an F1 interface (e.g., at least one first F1 interface and / or at least one second F1 interface; e.g., through a gNB-CU configuration update message, an F1 setup response message, a gNB-DU configuration update confirmation message, a DL RRC message delivery message, a system information delivery message, etc.) (if the first gNB-CU is a master CU, the first gNB-CU transmits at least one third message to the gNB-DU). In one example, in response to receiving at least one third message from the first gNB-CU and / or the second gNB-CU, the gNB-DU may transmit (and / or broadcast) at least one third message through a wireless interface (e.g., through serving cells of the gNB-DU and / or a wireless interface).

[0241] In one example, the gNB-DU may configure at least one system information block for a serving cell of the gNB-DU based on a first connection message and / or a second connection message (e.g., at least one third message, at least one element of the at least one third message, system information block type 1, and / or other types of system information blocks, e.g., SIB2, SIB3, etc.). In one example, at least one system information block may include at least one of a first PLMN identifier, a second PLMN identifier, a first parameter indicating that the serving cell supports the first PLMN (e.g., a first service operator, a first operator, a first network, etc.), a second parameter indicating that the serving cell supports the second PLMN (e.g., a second service operator, a second operator, a second network, etc.), a third parameter indicating that the serving cell is used by the first gNB-CU and / or the first gNB, and a fourth parameter indicating that the serving cell is used by the second gNB-CU and / or the second gNB. At least one system information block may further include at least one of the cell identifiers of the serving cell to which the at least one system information block is transmitted (a first cell identifier of the serving cell for the first PLMN, a second cell identifier of the serving cell for the second PLMN, a third cell identifier of the serving cell for the first gNB-CU / first gNB, a fourth cell identifier of the serving cell for the second gNB-CU / second gNB, etc.). The first parameter may include at least one of the first TAC, first TAI, first RAC, first RAI, first cell identifier, first gNB-CU identifier, first gNB identifier, first RNA identifier, first RAN region identifier, first resumption identifier, etc.The second parameter may include at least one of the second TAC, the second TAI, the second RAC, the second RAI, the second cell identifier, the second gNB-CU identifier, the second gNB identifier, the second RNA identifier, the second RAN region identifier, the second resumption identifier, etc. The third parameter may include at least one of the third TAC, the third TAI, the third RAC, the third RAI, the third cell identifier, the first gNB-CU identifier, the first gNB identifier, the third RNA identifier, the third RAN region identifier, the third resumption identifier, etc. The fourth parameter may include at least one of the fourth TAC, the fourth TAI, the fourth RAC, the fourth RAI, the fourth cell identifier, the second gNB-CU identifier, the second gNB identifier, the fourth RNA identifier, the fourth RAN region identifier, the fourth resumption identifier, etc.

[0242] In one example, based on the first PLMN identifier of the first PLMN and / or the second PLMN identifier of the second PLMN supported by the serving cell of the gNB-DU (e.g., received from the gNB-DU), and / or based on the first parameter, the second parameter, the third parameter, and / or the fourth parameter, the first gNB-CU may configure at least one system information block (e.g., system information block type 1, and / or other types of system information blocks, e.g., SIB2, SIB3, etc.) for the serving cell of the gNB-DU. In one example, the first gNB-CU may receive the first PLMN identifier and / or the second PLMN identifier from the gNB-DU and / or the second gNB-CU. In one example, the first gNB-CU may receive the first parameter, the second parameter, the third parameter, and / or the fourth parameter from the gNB-DU and / or the second gNB-CU. In one example, at least one system information block may include a first PLMN identifier, a second PLMN identifier, a first parameter indicating that the serving cell supports the first PLMN (e.g., a first service operator, a first operator, a first network, etc.), a second parameter indicating that the serving cell supports the second PLMN (e.g., a second service operator, a second operator, a second network, etc.), a third parameter indicating that the serving cell is used by the first gNB-CU and / or the first gNB, a fourth parameter indicating that the serving cell is used by the second gNB-CU and / or the second gNB, etc.At least one system information block may further include at least one of the cell identifiers of the serving cell to which the at least one system information block is transmitted (a first cell identifier of the serving cell for the first PLMN, a second cell identifier of the serving cell for the second PLMN, a third cell identifier of the serving cell for the first gNB-CU / first gNB, a fourth cell identifier of the serving cell for the second gNB-CU / second gNB, etc.). The first parameter may include at least one of the first TAC, first TAI, first RAC, first RAI, first cell identifier, first gNB-CU identifier, first gNB identifier, first RNA identifier, first RAN region identifier, first resumption identifier, etc. The second parameter may include at least one of the second TAC, second TAI, second RAC, second RAI, second cell identifier, second gNB-CU identifier, second gNB identifier, second RNA identifier, second RAN region identifier, second resumption identifier, etc. The third parameter may include at least one of the third TAC, the third TAI, the third RAC, the third RAI, the third cell identifier, the first gNB-CU identifier, the first gNB identifier, the third RNA identifier, the third RAN region identifier, the third resumption identifier, etc. The fourth parameter may include at least one of the fourth TAC, the fourth TAI, the fourth RAC, the fourth RAI, the fourth cell identifier, the second gNB-CU identifier, the second gNB identifier, the fourth RNA identifier, the fourth RAN region identifier, the fourth resumption identifier, etc.

[0243] In one example, the gNB-DU can transmit / broadcast at least one system information block configured by the gNB-DU and / or received from the first gNB-CU and / or the second gNB-CU (e.g., configured by the first gNB-CU and / or the second gNB-CU). The at least one system information block can be transmitted / broadcast to a plurality of wireless devices via a wireless interface.

[0244] In one example, individual cells of the gNB-DU may be configured for different PLMNs as illustrated in the exemplary drawings of FIG. 41 and / or FIG. 42. In one example, one or more first serving cells of the serving cells of the gNB-DU may support (e.g., service, belong to, provide resources, etc.) the first PLMN (and / or the first gNB-CU and / or the first gNB). At least one message of at least one third message (transmitted / broadcast from the gNB-DU to wireless devices through one or more first cells) may include a first PLMN identifier, a first gNB-CU identifier of the first gNB-CU, a first gNB identifier of the first gNB associated with the first gNB-CU, one or more first serving cell identifiers of one or more first serving cells, etc. In one example, one or more first serving cell identifiers may be transmitted from the gNB-DU to the first gNB-CU. In one example, one or more second serving cells of the serving cells of the gNB-DU may support (e.g., service, belong to, provide resources, etc.) the second PLMN (and / or the second gNB-CU and / or the second gNB). At least one message of at least one third message (transmitted / broadcast from the gNB-DU to wireless devices through one or more second cells) may include a second PLMN identifier, a second gNB-CU identifier of the second gNB-CU, a second gNB identifier of the second gNB associated with the second gNB-CU, one or more second serving cell identifiers of one or more second serving cells, etc. In one example, one or more second serving cell identifiers may be transmitted from the gNB-DU to the second gNB-CU.

[0245] In one example, as illustrated in the exemplary drawings of FIG. 41 and / or FIG. 42, common cells of gNB-DU may be configured for a plurality of PLMNs (e.g., a first PLMN and / or a second PLMN; a first gNB-CU and / or a second gNB-CU; and / or a first gNB and / or a second gNB). In one example, one or more third serving cells among the serving cells of gNB-DU may support (e.g., service, belong, provide resources, etc.) the first PLMN and the second PLMN (and / or the first gNB-CU and the second gNB-CU). At least one message of at least one third message (transmitted / broadcasted from the gNB-DU to wireless devices through one or more third serving cells) comprises a first PLMN identifier and a second PLMN identifier, a first gNB-CU identifier of the first gNB-CU and a second gNB-CU identifier of the second gNB-CU, a first gNB-CU identifier of the first gNB associated with the first gNB-CU and a second gNB-CU identifier of the second gNB associated with the second gNB-CU, one or more third serving cell identifiers of one or more third serving cells (e.g., where different (multiple) cell identifiers for one serving cell are configured for different PLMNs), one or more fourth serving cell identifiers of one or more third serving cells (or for the same) (associated with the first PLMN, the first gNB-CU, and / or the first gNB), (e.g., where different (multiple) cell identifiers for one serving cell are configured for different PLMNs) of one or more third serving cells (or for the same) It may include one or more fifth serving cell identifiers (associated with the second PLMN, the second gNB-CU, and / or the second gNB). In one example, one or more third serving cell identifiers, one or more fourth serving cell identifiers, and / or one or more fifth serving cell identifiers may be transferred from the gNB-DU to the first gNB-CU.In one example, one or more third serving cell identifiers, one or more fourth serving cell identifiers, and / or one or more fifth serving cell identifiers may be transferred from the gNB-DU to the second gNB-CU. In one example, the first gNB-CU may configure one or more fourth serving cell identifiers and transfer them to the gNB-DU. In one example, the second gNB-CU may configure one or more fifth serving cell identifiers and transfer them to the gNB-DU.

[0246] In one example, as illustrated in the exemplary drawing of FIG. 37, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include a plurality of configuration parameters or a plurality of configured system information blocks for a plurality of PLMNs (and / or for a plurality of gNB-CUs). At least one of the first gNB-CU and / or the second gNB-CU may receive parameters of another gNB-CU (e.g., each of the second gNB-CU or the first gNB-CU) via a gNB-DU and / or may configure at least one system information block. In one example, a base station distribution unit may receive one or more second configuration parameters associated with the second base station central unit and / or the second PLMN from the second base station central unit. The base station distribution unit may transmit one or more second configuration parameters to the first base station central unit. A base station distribution unit may receive from a first base station central unit at least one system information block comprising at least one of one or more first configuration parameters (e.g., and / or a first system information block) associated with the first base station central unit and / or the first PLMN, and / or one or more second configuration parameters (e.g., and / or a second system information block) associated with the second base station central unit and / or the second PLMN. The base station distribution unit may transmit (forward / broadcast) at least one system information block. The base station distribution unit may transmit at least one system information block to the second base station central unit.

[0247] In one example, as illustrated in the exemplary drawing of FIG. 37, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include a plurality of configuration parameters or a plurality of configured system information blocks for a plurality of PLMNs (and / or for a plurality of gNB-CUs). At least one of the first gNB-CU and / or the second gNB-CU may receive parameters of another gNB-CU (e.g., each of the second gNB-CU or the first gNB-CU) through an interface between the first gNB-CU and the second gNB-CU, and / or may configure at least one system information block. In one example, a base station distribution unit may receive from a first base station central unit at least one system information block comprising at least one of one or more first configuration parameters (e.g., and / or a first system information block) associated with the first base station central unit and / or the first PLMN, and / or one or more second configuration parameters (e.g., and / or a second system information block) associated with the second base station central unit and / or the second PLMN. The first base station central unit may receive one or more second configuration parameters from a second base station central unit (e.g., through an interface between the first gNB-CU and the second gNB-CU). The base station distribution unit may transmit (forward / broadcast) at least one system information block. In one example, the base station distribution unit may transmit at least one system information block to the second base station central unit.

[0248] In one example, as illustrated in the exemplary drawing of FIG. 38, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include a plurality of configuration parameters or a plurality of configured system information blocks for a plurality of PLMNs (and / or for a plurality of gNB-CUs). The gNB-DU may receive parameters of the first gNB-CU (e.g., the first PLMN) and / or the second gNB-CU (e.g., the second PLMN) from the first gNB-CU and / or the second gNB-CU, and / or may configure at least one system information block. In one example, the base station distribution unit may receive one or more first configuration parameters associated with the first base station central unit and / or the first PLMN from the first base station central unit. The base station distribution unit may receive one or more second configuration parameters associated with the second base station central unit and / or the second PLMN from the second base station central unit. A base station distribution unit may determine at least one system information block comprising at least one of one or more first configuration parameters (e.g., and / or a first system information block) associated with a first gNB-CU and / or a first PLMN, and / or one or more second configuration parameters (e.g., and / or a second system information block) associated with a second base station central unit and / or a second PLMN. (In one example, the base station distribution unit may transmit at least one system information block to the first base station central unit and / or the second base station central unit. The base station distribution unit may receive at least one system information block from the first base station central unit and / or the second base station central unit.) In one example, the base station distribution unit may transmit (forward / broadcast) at least one system information block.

[0249] In one example, as illustrated in the exemplary drawing of FIG. 38, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include a plurality of configuration parameters or a plurality of configured system information blocks for a plurality of PLMNs (and / or for a plurality of gNB-CUs). The gNB-DU may receive parameters of the first gNB-CU (e.g., the first PLMN) and / or the second gNB-CU (e.g., the second PLMN) from the first gNB-CU and / or the second gNB-CU. In one example, one of the first gNB-CU and the second gNB-CU may receive and / or transmit parameters of the other gNB-CU (e.g., the second gNB-CU or the first gNB-CU, respectively) through an interface between the first gNB-CU and the second gNB-CU to the gNB-DU. The gNB-DU can configure at least one system information block based on the above parameters. In one example, the base station distribution unit may receive from the first base station central unit at least one of one or more first configuration parameters associated with the first base station central unit and / or the first PLMN, and / or one or more second configuration parameters associated with the second base station central unit and / or the second PLMN. The first base station central unit may receive one or more second configuration parameters from the second base station central unit. The base station distribution unit may determine at least one system information block comprising one or more first configuration parameters associated with the first base station central unit and / or the first PLMN (e.g., and / or the first system information block), and / or one or more second configuration parameters associated with the second base station central unit and / or the second PLMN (e.g., and / or the second system information block).(In one example, the base station distribution unit may transmit at least one system information block to the first base station central unit and / or the second base station central unit. The base station distribution unit may receive at least one system information block from the first base station central unit and / or the second base station central unit.) In one example, the base station distribution unit may transmit (forward / broadcast) at least one system information block.

[0250] In one example, as illustrated in the exemplary drawing of FIG. 39, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include configuration parameters ((partially) common and / or (partially) individual) for a plurality of PLMNs (and / or for a plurality of gNB-CUs). At least one of the first gNB-CU and / or the second gNB-CU may receive parameters of another gNB-CU (e.g., each of the second gNB-CU or the first gNB-CU) via a gNB-DU and / or may constitute at least one system information block. In one example, a base station distribution unit may receive one or more second configuration parameters associated with the second base station central unit and / or the second PLMN from the second base station central unit. The base station distribution unit may transmit one or more second configuration parameters to the first base station central unit. A base station distribution unit may receive from a first base station central unit at least one system information block comprising one or more configuration parameters associated with the first PLMN and / or the second PLMN (and / or associated with the first base station central unit and / or the second base station central unit). The base station distribution unit may transmit (forward / broadcast) at least one system information block. The base station distribution unit may transmit at least one system information block to the second base station central unit.

[0251] In one example, as illustrated in the exemplary drawing of FIG. 39, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include configuration parameters ((partially) common and / or (partially) individual) for a plurality of PLMNs (and / or for a plurality of gNB-CUs). At least one of the first gNB-CU and / or the second gNB-CU may receive parameters of another gNB-CU (e.g., each of the second gNB-CU or the first gNB-CU) through an interface between the first gNB-CU and the second gNB-CU, and / or may configure at least one system information block. In one example, a base station distribution unit may receive from a first base station central unit at least one system information block containing one or more configuration parameters associated with the first PLMN and / or the second PLMN (and / or associated with the first base station central unit and / or the second base station central unit). The base station distribution unit can transmit (forward / broadcast) at least one system information block. The base station distribution unit can transmit at least one system information block to the second base station central unit.

[0252] In one example, as illustrated in the exemplary drawing of FIG. 40, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include configuration parameters ((partially) common and / or (partially) individual) for a plurality of PLMNs (and / or for a plurality of gNB-CUs). The gNB-DU may receive parameters of the first gNB-CU (e.g., the first PLMN) and / or the second gNB-CU (e.g., the second PLMN) from the first gNB-CU and / or the second gNB-CU, and / or may configure at least one system information block. In one example, the base station distribution unit may receive one or more first configuration parameters associated with the first base station central unit and / or the first PLMN from the first base station central unit and / or may receive one or more second configuration parameters associated with the second base station central unit and / or the second PLMN from the second base station central unit. In one example, the base station distribution unit may determine at least one system information block comprising one or more configuration parameters associated with the first PLMN and / or the second PLMN (and / or associated with the first base station central unit and / or the second base station central unit) based on one or more first configuration parameters and / or one or more second configuration parameters. (In one example, the base station distribution unit may transmit at least one system information block to the first base station central unit and / or the second base station central unit. The base station distribution unit may receive at least one system information block from the first base station central unit and / or the second base station central unit.) In one example, the base station distribution unit may transmit (forward / broadcast) at least one system information block.

[0253] In one example, as illustrated in the exemplary drawing of FIG. 40, at least one system information block (e.g., SIB1, SIB2, SIB3, SIB4, SIB5, etc.) may include configuration parameters ((partially) common and / or (partially) individual) for a plurality of PLMNs (and / or for a plurality of gNB-CUs). The gNB-DU may receive parameters of the first gNB-CU (e.g., the first PLMN) and / or the second gNB-CU (e.g., the second PLMN) from the first gNB-CU and / or the second gNB-CU. In one example, one of the first gNB-CU and the second gNB-CU may receive and / or transmit parameters of the other gNB-CU (e.g., the second gNB-CU or the first gNB-CU, respectively) through an interface between the first gNB-CU and the second gNB-CU to the gNB-DU. The gNB-DU can configure at least one system information block based on the above parameters. In one example, the base station distribution unit may receive from the first base station central unit at least one of one or more first configuration parameters associated with the first base station central unit and / or the first PLMN, and / or at least one of one or more second configuration parameters associated with the second base station central unit or the second PLMN. The first base station central unit may receive one or more second configuration parameters from the second base station central unit. Based on one or more first configuration parameters and / or one or more second configuration parameters, the base station distribution unit may determine at least one system information block comprising one or more configuration parameters associated with the first PLMN and / or the second PLMN (or associated with the first base station central unit and / or the second base station central unit). (In one example, the base station distribution unit may transmit at least one system information block to the first base station central unit and / or the second base station central unit.)A base station distribution unit can receive at least one system information block from a first base station central unit and / or a second base station central unit.) In one example, the base station distribution unit can transmit (forward / broadcast) at least one system information block.

[0254] In one example, a wireless device may select a serving cell of a gNB-DU based on at least one third message and / or at least one system information block. The wireless device may select / reselect a serving cell of a gNB-DU based on a first PLMN identifier and / or a second PLMN identifier of at least one third message. The wireless device may select / reselect a serving cell of a gNB-DU based on a first cell identifier, a second cell identifier, a third cell identifier, and / or a fourth cell identifier for a serving cell of at least one third message. The wireless device may select / reselect a serving cell of a gNB-DU based on a first gNB-CU identifier and / or a second gNB-CU identifier of at least one third message. The wireless device may select / reselect a serving cell of a gNB-DU based on a first gNB identifier associated with a first gNB-CU and / or a second gNB identifier associated with a second gNB-CU of at least one third message.

[0255] In one example, a wireless device may select / reselect a serving cell of a gNB-DU based on one or more elements of a first parameter, a second parameter, a third parameter, and / or a fourth parameter of at least one third message. The first parameter may include at least one of a first TAC, a first TAI, a first RAC, a first RAI, a first cell identifier, a first gNB-CU identifier, a first gNB identifier, a first RNA identifier, a first RAN region identifier, a first resumption identifier, etc. The second parameter may include at least one of a second TAC, a second TAI, a second RAC, a second RAI, a second cell identifier, a second gNB-CU identifier, a second gNB identifier, a second RNA identifier, a second RAN region identifier, a second resumption identifier, etc. The third parameter may include at least one of a third TAC, a third TAI, a third RAC, a third RAI, a third cell identifier, a first gNB-CU identifier, a first gNB identifier, a third RNA identifier, a third RAN region identifier, a third resumption identifier, etc. The fourth parameter may include at least one of a fourth TAC, a fourth TAI, a fourth RAC, a fourth RAI, a fourth cell identifier, a second gNB-CU identifier, a second gNB identifier, a fourth RNA identifier, a fourth RAN region identifier, a fourth resumption identifier, etc. In one example, the wireless device may be in an RRC idle state, an RRC inactive state, and / or an RRC connected state.

[0256] In one example, the wireless device may have a list of PLMN identifiers of PLMNs that are allowed (and / or available for access) (e.g., the list of PLMN identifiers may include PLMN identifiers of equivalent PLMNs). In response to at least one of a first PLMN and / or a second PLMN within the list of allowed PLMNs (e.g., and / or the first PLMN and / or the second PLMN may include equivalent PLMNs), the wireless device may select (and / or re-select) a serving cell of the gNB-DU. In one example, the wireless device may have a list of cell identifiers of cells that are allowed (and / or available for access). In response to at least one of a first cell identifier, a second cell identifier, a third cell identifier, and / or a fourth cell identifier within the list of cell identifiers of cells that are allowed for access, the wireless device may select (and / or re-select) a serving cell of the gNB-DU. In one example, the wireless device may have a list of networks that are allowed (and / or possible to connect to) (e.g., TAC, TAI, RAC, RAI, gNB-CU, gNB, RNA, RAN region, and / or re-identifier). In response to at least one element of the first parameter, second parameter, third parameter and / or fourth parameter within the list of networks that are allowed to connect, the wireless device may select (and / or re-select) a serving cell of the gNB-DU.

[0257] In one example, based on the selection of a serving cell of a gNB-DU by a wireless device, the wireless device may initiate one or more random access procedures to access the serving cell of the gNB-DU. The wireless device may transmit one or more random access preambles through the serving cell and may receive at least one random access response (RAR) for the one or more random access preambles from the gNB-DU through the serving cell. In one example, the wireless device may determine that one of the one or more random access procedures is being processed and / or is successful based on an interaction with the gNB-DU (including at least one of one or more random access preambles and / or at least one random access response).

[0258] In one example, based on the selection of a serving cell of the gNB-DU by the wireless device and / or based on one or more random access procedures of the wireless device, the gNB-DU may receive a first message (e.g., an RRC message, an RRC connection request message, an RRC connection setup complete message, an RRC connection resumption request message, an RRC connection resumption complete message, etc.) from the wireless device. In one example, in response to receiving at least one RAR for one or more random access preambles, the wireless device may transmit the first message (e.g., an RRC connection request message and / or an RRC connection resumption request message; e.g., message 3). The first message may include at least one of a first PLMN identifier (e.g., indicating that the wireless device can connect to the first PLMN) and / or a second PLMN identifier (e.g., indicating that the wireless device can connect to the second PLMN). In one example, the first PLMN identifier may include a first indication / index (e.g., one or more first bits) representing the first PLMN. In one example, the second PLMN identifier may include a second indication / index (e.g., one or more second bits) representing the second PLMN. In one example, the first message may include at least one of a first cell identifier (e.g., indicating that a wireless device can access / attempts to access the first cell and / or the first PLMN), a second cell identifier (e.g., indicating that a wireless device can access / attempts to access the second cell and / or the second PLMN), a third cell identifier (e.g., indicating that a wireless device can access / attempts to access the third cell and / or the first gNB-CU / first gNB), and / or a fourth cell identifier (e.g., indicating that a wireless device can access / attempts to access the fourth cell and / or the second gNB-CU / second gNB).A wireless device may transmit a first message based on at least one third message and / or at least one system information block. The wireless device may determine a first PLMN and / or a second PLMN based on the third message and / or at least one system information block. Based on the determination, the wireless device may include / add a first PLMN identifier (e.g., or a first cell identifier) ​​and / or a second PLMN identifier (e.g., or a second cell identifier) ​​within the first message.

[0259] In one example, the first message may include at least one of one or more first parameters, one or more second parameters, one or more third parameters, and / or one or more fourth parameters. One or more first parameters may indicate that the first message is for a connection to the first PLMN and / or a network associated with the first PLMN (e.g., trace area, registry area, RNA, RAN area, etc.). One or more second parameters may indicate that the first message is for a connection to the second PLMN and / or a network associated with the second PLMN (e.g., trace area, registry area, RNA, RAN area, etc.). One or more third parameters may indicate that the first message is for a connection to the first gNB-CU / first gNB and / or a network associated with the first gNB-CU / first gNB (e.g., trace area, registry area, RNA, RAN area, etc.). One or more fourth parameters may indicate that the first message is for a connection to the second gNB-CU / second gNB and / or the network associated with the second gNB-CU / second gNB (e.g., trace region, registration region, RNA, RAN region, etc.).

[0260] In one example, when a wireless device selects a serving cell and a first PLMN to connect to, the first message may include at least one of a first PLMN identifier, a first cell identifier (and / or a third cell identifier), a first gNB identifier, a first gNB-CU identifier, a first TAC, a first TAI, a first RAC, a first RAI, a first RNA identifier, a first RAN region identifier, a first resumption identifier, etc.

[0261] In one example, when a wireless device selects a serving cell and a second PLMN to connect to, the first message may include at least one of a second PLMN identifier, a second cell identifier (and / or a fourth cell identifier), a second gNB identifier, a second gNB-CU identifier, a second TAC, a second TAI, a second RAC, a second RAI, a second RNA identifier, a second RAN region identifier, a second resumption identifier, etc.

[0262] In one example, when a wireless device selects a serving cell and a first gNB-CU and / or a first gNB to connect to, the first message may include at least one of a first PLMN identifier, a third cell identifier (and / or a first cell identifier), a first gNB identifier, a first gNB-CU identifier, a third TAC, a third TAI, a third RAC, a third RAI, a third RNA identifier, a third RAN region identifier, a third resumption identifier, etc.

[0263] In one example, when a wireless device selects a serving cell and a second gNB-CU and / or a second gNB to connect to, the first message may include at least one of a second PLMN identifier, a fourth cell identifier (and / or a second cell identifier), a second gNB identifier, a second gNB-CU identifier, a fourth TAC, a fourth TAI, a fourth RAC, a fourth RAI, a fourth RNA identifier, a fourth RAN region identifier, a fourth resumption identifier, etc.

[0264] In one example, at least one of a first PLMN identifier, a first cell identifier, a first gNB identifier, and a first gNB-CU identifier, a first TAC, a first TAI, a first RAC, a first RAI, a first RNA identifier, a first RAN region identifier, a first resumption identifier, a second PLMN identifier, a second cell identifier, a second gNB identifier, a second gNB-CU identifier, a second TAC, a second TAI, a second RAC, a second RAI, a second RNA identifier, a second RAN region identifier, a second resumption identifier, a third cell identifier, a third TAC, a third TAI, a third RAC, a third RAI, a third RNA identifier, a third RAN region identifier, a third resumption identifier, a fourth cell identifier, a fourth TAC, a fourth TAI, a fourth RAC, a fourth RAI, a fourth RNA identifier, a fourth RAN region identifier, and / or at least one of a fourth resumption identifier together with the first message is a MAC control element (e.g., MAC CE) and / or physical layer control information (e.g., It can be transmitted from a wireless device to a gNB-DU (e.g., base station) via the UCI.

[0265] In one example, a selected PLMN identity (identifier) ​​information element of the first message may include at least one of a first PLMN identifier and / or a second PLMN identifier. In one example, if a wireless device is allowed (and / or enabled, enabled, authorized) to connect to (and / or use) the first PLMN, the first message may include the first PLMN identifier. In one example, if a wireless device is allowed (and / or enabled, enabled, authorized) to connect to (and / or use) the second PLMN, the first message may include the second PLMN identifier (e.g., and / or a first cell identifier (and / or a third cell identifier), a first gNB identifier, a first gNB-CU identifier, a first TAC, a first TAI, a first RAC, a first RAI, a first RNA identifier, a first RAN area identifier, a first resumption identifier, etc.). In one example, when a wireless device is allowed (and / or enabled, enabled, authorized) to connect to (and / or use) the first PLMN and the second PLMN, the first message may include a first PLMN identifier and a second PLMN identifier (e.g., and / or a second cell identifier (and / or a fourth cell identifier), a second gNB identifier, a second gNB-CU identifier, a second TAC, a second TAI, a second RAC, a second RAI, a second RNA identifier, a second RAN area identifier, a second resumption identifier, etc.). In one example, when a wireless device is allowed (and / or enabled, enabled, authorized) to connect to (and / or use) the first PLMN and the second PLMN, the first message may further include priority information between the first PLMN and the second PLMN.

[0266] In one example, the first message may include an RRC message. In one example, the first message comprises a wireless device identifier of the wireless device (e.g., TMSI, S-TMSI, IMSI, C-RNTI, RNTI, resumption ID, etc.), a counter check response message, a CSFB parameter request CDMA2000 message, an internal terminal mutual (IDC) indication message, a cross-frequency RSTD measurement indication message, an MBMS count response message, an MBMS interest indication message, a measurement report message, a proximity indication message, a relay node reconfiguration completion message, an RRC connection reconfiguration completion message, an RRC connection re-establishment request message, an RRC connection re-establishment completion message, an RRC connection request message, an RRC connection setup completion message, an RRC connection resumption request message, an RRC connection resumption completion message, an auxiliary cell group (SCG) fault information (NR) message, a security mode completion message, a side-link UE information message, a UE support information message, a UE function information message, a UE information response message, a UE handover readiness message, an uplink information transmission message (e.g., including at least one NAS message), an uplink information transmission MRDC message, a WLAN connection status report message, and / or an information associated with the wireless device. It may include at least one of the RRC messages.

[0267] In one example, the first message includes registered core network node information (e.g., registered Mobility Management Entity (MME), registered Access and Mobility Management Function (AMF), registered Session Management Function (SMF), registered Serving Gateway (SGW), registered User Plane Function (UPF), registered PDN Gateway (PGW), etc.), registered (e.g., preferred) base station information (e.g., registered base station identifier, registered gNB, registered gNB identifier, first gNB identifier, second gNB identifier, first eNB identifier, second eNB identifier, etc.), registered (e.g., preferred) gNB-CU information (e.g., gNB-CU identifier, first gNB-CU identifier, second gNB-CU identifier, etc.), dedicated non-access layer information (e.g., information between the core network (MME / AMF / SMF) and the radio device), RAN notification area identifier, RAN area information associated with the radio device (e.g., in an RRC disabled state), GUMMEI type (e.g., negative, mapped), and radio link fault information availability information. It may include at least one of the following: a relay node subframe configuration request, mobility status information (e.g., mobility speed of a wireless device, e.g., high / medium / low / normal / static speed), mobility history availability information (e.g., a list of cells where the wireless device stays), logged measurement result availability information (e.g., associated with MBSFN), wireless device identifier of a wireless device (e.g., S-TMSI, IMSI, TMSI, etc.), resumption identifier of a wireless device (e.g., in an RRC inactive state) (e.g., resumption ID), information on PDN connectionless access, user plane cellular Internet of Things (CIoT) optimization information (e.g., indicating data transmission based on control plane CIoT optimization), dcn identifier (e.g., dcn ID), and registered MME (e.g., including PLMN identity (first PLMN identifier and / or second PLMN identifier), MMEGI, MMEC, etc.).

[0268] In one example, in response to the receipt of a first message, the gNB-DU may select a central unit (e.g., a selected gNB-CU) (e.g., between a first gNB-CU and a second gNB-CU) based on the first message. In one example, in response to the receipt of a first message, the gNB-DU may select a central unit (e.g., a selected gNB-CU) between at least a first gNB-CU and a second gNB-CU based on at least one of a first PLMN identifier and / or a second PLMN identifier of the first message. In one example, if the first message includes a first PLMN identifier (e.g., indicating that a wireless device is allowed (and / or authorized to connect to, or use) the first PLMN), the gNB-DU may select a first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the first message includes a second PLMN identifier (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, or authorized) to connect to (and / or use) the second PLMN), the gNB-DU may select a second gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the first message includes a first PLMN identifier and a second PLMN identifier (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, or authorized) to connect to (and / or use) the first PLMN and the second PLMN), the gNB-DU may select one of a first gNB-CU or a second gNB-CU to forward the first message and / or one or more elements of the first message (e.g., based on priority information of the first PLMN and the second PLMN indicated in the first message).

[0269] In one example, in response to the reception of a first message, the gNB-DU may select a central unit (e.g., as a selected gNB-CU) between at least a first gNB-CU and a second gNB-CU based on at least one of the first PLMN-related parameters and / or the second PLMN-related parameters of the first message. In one example, if the first message includes at least one of a first PLMN identifier, a first cell identifier (and / or a third cell identifier), a first gNB identifier, a first gNB-CU identifier, a first TAC, a first TAI, a first RAC, a first RAI, a first RNA identifier, a first RAN area identifier, a first resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect (and / or use) the first PLMN and / or serving cell), the gNB-DU may select the first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the first message includes at least one of a second PLMN identifier, a second cell identifier (and / or a fourth cell identifier), a second gNB identifier, a second gNB-CU identifier, a second TAC, a second TAI, a second RAC, a second RAI, a second RNA identifier, a second RAN area identifier, a second resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect (and / or use) the second PLMN and / or serving cell), the gNB-DU may select the second gNB-CU to forward the first message and / or one or more elements of the first message.

[0270] In one example, in response to the reception of a first message, the gNB-DU may select a central unit (e.g., as a selected gNB-CU) between at least a first gNB-CU and a second gNB-CU based on at least one of the first gNB-CU related parameters (e.g., first gNB related parameters) and / or the second gNB-CU related parameters (e.g., second gNB related parameters) of the first message. In one example, if the first message includes at least one of a first PLMN identifier, a third cell identifier (and / or a first cell identifier), a first gNB identifier, a first gNB-CU identifier, a third TAC, a third TAI, a third RAC, a third RAI, a third RNA identifier, a third RAN area identifier, a third resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, or authorized) to connect (and / or use) the first gNB-CU / first gNB and / or serving cell), the gNB-DU may select the first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the first message includes at least one of a second PLMN identifier, a fourth cell identifier (and / or a second cell identifier), a second gNB identifier, a second gNB-CU identifier, a fourth TAC, a fourth TAI, a fourth RAC, a fourth RAI, a fourth RNA identifier, a fourth RAN area identifier, a fourth resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect (and / or use) the second gNB-CU / second gNB and / or serving cell), the gNB-DU may select the second gNB-CU to forward the first message and / or one or more elements of the first message.

[0271] In one example, in response to the reception of a first message, the gNB-DU may select a central unit (e.g., as a selected gNB-CU) between at least a first gNB-CU and a second gNB-CU based on the serving cell through which the wireless device transmits the first message to the gNB-DU. In one example, if the gNB-DU receives the first message through one or more first serving cells (e.g., if it supports a first PLMN and / or a first gNB-CU / first gNB), the gNB-DU may select the first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the gNB-DU receives the first message through one or more second serving cells (e.g., if it supports a second PLMN and / or a second gNB-CU / second gNB), the gNB-DU may select the second gNB-CU to forward the first message and / or one or more elements of the first message. In one example, when a gNB-DU receives a first message through one or more third serving cells (e.g., a first PLMN and a second PLMN; and / or a first gNB-CU / a first gNB and a second gNB-CU / a second gNB), the gNB-DU may select a first gNB-CU and / or a second gNB-CU to forward the first message and / or one or more elements of the first message (e.g., the gNB-DU may transmit / forward the first message to the first gNB-CU and / or the second gNB-CU (e.g., to the first gNB-CU or the second gNB-CU; or to both the first gNB-CU and the second gNB-CU)).

[0272] In one example, the gNB-DU may select a central unit (gNB-CU) between a first gNB-CU and a second gNB-CU based on one or more elements of a first message (e.g., registered core network node information, registered (preferred) base station information, registered (e.g., preferred) gNB-CU information, RAN notification area identifier, RAN area information, etc.). In one example, if one or more elements of the first message are associated with the first gNB-CU / first gNB and / or the first PLMN, the gNB-DU may select the first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if one or more elements of the first message are associated with the second gNB-CU / second gNB and / or the second PLMN, the gNB-DU may select the second gNB-CU to forward the first message and / or one or more elements of the first message. In one example, when a registered core network node of registered core network node information (e.g., MME, AMF, SMF, UPF, SGW, PGW, etc.) is connected to a first gNB-CU / first gNB (e.g., to service, operate, control, to have an NG / S1 interface, etc.), the gNB-DU may select the first gNB-CU to forward a first message and / or one or more elements of the first message. In one example, when a registered core network node of registered core network node information (e.g., MME, AMF, SMF, UPF, SGW, PGW, etc.) is connected to a second gNB-CU / second gNB (e.g., to service, operate, control, to have an NG / S1 interface, etc.), the gNB-DU may select the second gNB-CU to forward a first message and / or one or more elements of the first message.

[0273] In one example, if a registered base station (e.g., gNB, eNB, RNC, etc.) of the registered (preferred) base station information includes a first gNB-CU identifier / a first gNB identifier (e.g., associated therewith), the gNB-DU may select a first gNB-CU to forward a first message and / or one or more elements of the first message. In one example, if a registered base station (e.g., gNB, eNB, RNC, etc.) of the registered (preferred) base station information includes a second gNB-CU identifier / a second gNB identifier (e.g., associated therewith), the gNB-DU may select a second gNB-CU to forward a first message and / or one or more elements of the first message.

[0274] In one example, if the registered gNB-CU of the registered (e.g., preferred) gNB-CU information includes a first gNB-CU, the gNB-DU may select the first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the registered gNB-CU of the registered (e.g., preferred) gNB-CU information includes a second gNB-CU, the gNB-DU may select the second gNB-CU to forward the first message and / or one or more elements of the first message.

[0275] In one example, if the RAN notification area of ​​the RAN notification area identifier and / or the RAN area of ​​the RAN area information includes a first gNB-CU / first gNB, the gNB-DU may select the first gNB-CU to forward the first message and / or one or more elements of the first message. In one example, if the RAN notification area of ​​the RAN notification area identifier and / or the RAN area of ​​the RAN area information includes a second gNB-CU / second gNB, the gNB-DU may select the second gNB-CU to forward the first message and / or one or more elements of the first message.

[0276] In one example, based on a selection of a gNB-CU based on a first message and / or one or more elements of the first message, a gNB-DU may transmit (e.g., forward) the first message to a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU). In one example, based on a selection of a gNB-CU based on a first message and / or one or more elements of the first message, a gNB-DU may transmit (e.g., forward) one or more elements of the first message to a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU). In one example, a gNB-DU may transmit the first message and / or one or more elements of the first message to a selected gNB-CU through an F1 interface (e.g., at least one of a first F1 interface (first F1-CP) and / or at least one second F1 interface (second F1-CP)). In one example, the F1 interface may include an F1 control plane interface. In one example, if the selected gNB-CU is a first gNB-CU, the gNB-DU may transmit (forward) a first message and / or one or more elements of the first message to the first gNB-CU through at least one first F1 interface (e.g., a first F1-CP). In one example, if the selected gNB-CU is a second gNB-CU, the gNB-DU may transmit (forward) a first message and / or one or more elements of the first message to the second gNB-CU through at least one second F1 interface (e.g., a second F1-CP).

[0277] In one example, the gNB-DU may transmit a first message and / or one or more elements of the first message to a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU) through one or more first F1 messages. In one example, one or more first F1 messages may include at least one of an uplink (UL) RRC message transmission message, an initial UE context setup request message, an initial UE context message, a UE context setup response message, a UE context setup failure message, a UE context release request message, a UE context release completion message, a UE context modification response message, a UE context modification failure message, a UE context modification required message, and an F1 message transmitted from the gNB-DU to the selected gNB-CU.

[0278] In one example, one or more first F1 messages comprise: a first message; one or more elements of the first message; a UE identifier of a wireless device (e.g., gNB-CU UE F1-AP ID, gNB-DU UE F1AP ID, previous gNB-DU UE F1 AP ID, IMSI, TMSI, S-TMSI, C-RNTI, etc.); a resumption identifier (ID) received through the first message; a signaling radio bearer (SRB) associated with the first message; an RRC container comprising the first message and / or one or more elements of the first message; RRC information from the DU to the CU; one or more successful (accepted) bearer identifiers of one or more successful (accepted) bearers to be established / modified (e.g., data radio bearer (DRB), and / or signaling radio bearer (SRB)); one or more downlink tunnel endpoint identifiers for one or more successful (accepted) bearers (e.g., TEID, GTP TEID); and one or more failed bearers to be established / modified (e.g., One or more failed bearer identifiers of a Data Radio Bearer (DRB) and / or Signaling Radio Bearer (SRB), cause information for one or more failed bearers, one or more successful (accepted) cell identifiers of one or more successful (accepted) cells to be configured / modified (e.g., auxiliary cells, auxiliary cell groups, SpCell, master cell, PUCCH auxiliary cells, PUCCH cell, etc.), one or more failed cell identifiers of one or more failed cells to be configured / modified (e.g., auxiliary cells, auxiliary cell groups, SpCell, master cell, PUCCH auxiliary cells, PUCCH cell, etc.), cause information for one or more failed cells, resource coordination transport container, one or more bearer identifiers of one or more bearers to be modified / released (e.g., Data Radio Bearer (DRB) and / or Signaling Radio Bearer (SRB)), cause information for one or more bearers to be modified / released, one or more cells to be modified / released (e.g.,It may include at least one of the following: one or more cell identifiers of auxiliary cells, auxiliary cell groups, SpCell, master cell, PUCCH auxiliary cells, PUCCH cell, etc., cause information of one or more cells to be modified / released, etc.

[0279] In one example, in response to receiving a first message and / or one or more elements of the first message from a gNB-DU through an F1 interface and / or through one or more first F1 messages, a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU) may transmit a response message to the gNB-DU through the F1 interface and / or one or more second F1 messages, the response message comprising one or more elements of a downlink RRC message and / or a downlink RRC message associated with a wireless device. In one example, one or more second F1 messages may include at least one of a downlink (DL) RRC message transmission message, an initial UE context setup response message, an initial UE context message, a UE context setup request message, a UE context release command message, a UE context modification request message, a UE context modification confirmation message, and an F1 message transmitted from the selected gNB-CU to the gNB-DU. In one example, a selected gNB-CU may construct a response message and / or one or more elements of the response message based on a first message and / or one or more elements of the first message.

[0280] In one example, one or more second F1 messages include a response message (e.g., a downlink RRC message), one or more elements of the response message (e.g., a downlink RRC message), a UE identifier of a radio device (e.g., gNB-CU UE F1-AP ID, gNB-DU UE F1AP ID, former gNB-DU UE F1 AP ID, IMSI, TMSI, S-TMSI, C-RNTI, etc.), a signaling radio bearer (SRB) associated with the response message, an RRC container containing the response message and / or one or more elements of the response message, RRC information from the CU to the DU, one or more bearer identifiers of one or more bearers to be set / modified (e.g., a data radio bearer (DRB), and / or a signaling radio bearer (SRB)), one or more uplink tunnel endpoint identifiers for one or more bearers (e.g., TEID, GTP TEID), one or more release bearers to be released (e.g., a data radio bearer (DRB), and / or a signaling radio It may include at least one of the following: one or more release bearer identifiers of a bearer (SRB); cause information of one or more release bearers; one or more cell identifiers of one or more cells to be configured / modified (e.g., auxiliary cells, auxiliary cell groups, SpCell, master cell, PUCCH auxiliary cells, PUCCH cell, etc.); one or more release cell identifiers of one or more release cells to be released (e.g., auxiliary cells, auxiliary cell groups, SpCell, master cell, PUCCH auxiliary cells, PUCCH cell, etc.); cause information of one or more release cells; resource coordination transmission container, etc.

[0281] In one example, the response message (e.g., downlink RRC message) may include at least one of a counter check message, a downlink information transmission message, a handover from an NR / EUTRA readiness request message, a logged measurement configuration message, a master information block message, a master information block MBMS message, an MBMS count request, an MBSFN region configuration message, mobility from an NR / EUTRA command message, a paging message, a relay node reconfiguration message, an RRC connection reconfiguration message, an RRC connection re-establishment message, an RRC re-establishment refusal message, an RRC connection disconnection message, an RRC connection resumption message, an RRC connection setup message, an SCPTM configuration (e.g., BR) message, a security mode command message, a system information block, a system information block type 1, a system information block type 1 MBMS, a UE function query message, a UE information request message, and / or an RRC message associated with a wireless device. In one example, the gNB-DU can transmit / forward a response message and / or one or more elements of the response message (e.g., a downlink RRC message) to a wireless device through a wireless interface.

[0282] In one example, the response message may include at least one of an rrc-transactionidentifier information element (IE), a wireless resource configuration-only IE including one or more wireless resource configuration parameters, measurement configuration parameters, measurement configuration parameters, mobility control information parameters, one or more NAS layer parameters, security parameters, antenna information parameters, auxiliary cell addition / modification parameters, auxiliary cell release parameters, WLAN configuration parameters, WLAN offloading configuration parameters, LWA configuration parameters, LWIP configuration parameters, RCLWI configuration parameters, side link configuration parameters, V2X configuration parameters, uplink transmission power configuration parameters (e.g., p-MAX, p-MeNB, p-SeNB), power control mode information element, auxiliary cell group configuration parameters, etc.

[0283] In one example, a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU) may configure one or more elements of a response message. In one example, a gNB-DU may configure one or more elements of a response message. In one example, based on the first message, the selected gNB-CU may and / or transmit a message to the gNB-DU to configure one or more radio configuration parameters for a radio device (e.g., physical layer resource / power / cell configuration parameters, and / or RLC / MAC layer configuration parameters associated with the resource / power / cell), or may receive one or more radio configuration parameters configured by the gNB-DU from the gNB-DU. One or more radio configuration parameters configured by the gNB-DU may be added to the response message.

[0284] In one example, a selected gNB-CU and / or gNB-DU may configure / apply one or more parameters associated with and / or for servicing a wireless device, for example, based on a first message and / or a response message. The one or more parameters may include at least one of configuration parameters for an F1 bearer / logical channel, wireless resource parameters (e.g., SDAP, RRC, RLC, MAC, PHY, etc.), security parameters, NG interface session parameters (e.g., PDU session, QoS flow, network slice, etc.), resource scheduling parameters, priority management parameters, service policy-related parameters, etc. In one example, a response message to the first message (transmitted to the wireless device) may include one or more parameters. In one example, a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU) and / or gNB-DU may service a wireless device based on one or more parameters. In one example, a selected gNB-CU (e.g., a first gNB-CU and / or a second gNB-CU) and / or a gNB-DU can transmit (forward) / receive packets (e.g., PDCP packets) to / from a wireless device through a wireless interface and / or an F1 interface (e.g., an F1 user plane interface (e.g., a configured bearer / logical channel), an F1 control plane interface, etc.). In one example, if the selected gNB-CU is a first gNB-CU (e.g., a first PLMN), packets associated with the wireless device (e.g., PDCP packets, PDCP SDU, SDAP SDU, data, etc.) can be received / transmitted (forwarded) by a first core network (e.g., UPF, SGW, PGW, etc.) of the first PLMN (e.g., a first service operator).In one example, if the selected gNB-CU is a second gNB-CU (e.g., a second PLMN), packets associated with the wireless device (e.g., PDCP packets, PDCP SDU, SDAP SDU, data, etc.) can be received / transmitted (forwarded) by a second core network (e.g., UPF, SGW, PGW, etc.) of the second PLMN (e.g., a second service operator).

[0285] In one example, if the first message includes an RRC connection request message, the gNB-DU may receive an RRC connection setup message from the first gNB-CU and / or the second gNB-CU in response to the RRC connection request message. In one example, the gNB-DU may forward / transmit the RRC connection setup message to a wireless device and / or receive an RRC connection setup completion message in response to the transmission of the RRC connection setup message. The gNB-DU may transmit / forward the RRC connection setup completion message to the gNB-CU. In one example, if the first message includes an RRC connection resumption request message, the gNB-DU may receive an RRC connection resumption message from the first gNB-CU and / or the second gNB-CU in response to the RRC connection resumption request message. In one example, the gNB-DU may forward / transmit the RRC connection resumption message to a wireless device and / or receive an RRC connection resumption completion message in response to the transmission of the RRC connection resumption message. gNB-DU can send / forward an RRC connection resumption completion message to gNB-CU.

[0286] In one example, in response to / based on the reception of a first message (e.g., an RRC connection request message / RRC connection setup complete message, and / or an RRC connection resumption request message / RRC connection resumption complete message) comprising at least one of a first PLMN identifier, a first cell identifier (and / or a third identifier), a first gNB identifier, a first gNB-CU identifier, a first TAC, a first TAI, a first RAC, a first RAI, a first RNA identifier, a first RAN area identifier, a first resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect to (and / or use) the first PLMN and / or serving cell, the first gNB and / or base station (e.g., including a gNB-DU) may configure a UE context having one or more core network entities (e.g., an AMF, MME, UPF, SGW, PGW) by configuring an NG interface message (e.g., an initial UE message, and / or one or more UE context configurations). The relevant message can be transmitted to the core network entities (e.g., AMF, MME) of the first PLMN.

[0287] In one example, in response to / based on the reception of a first message (e.g., an RRC connection request message / RRC connection setup completion message, and / or an RRC connection resumption request message / RRC connection resumption completion message) comprising at least one of a first PLMN identifier, a third cell identifier (and / or a first identifier), a first gNB identifier, a first gNB-CU identifier, a third TAC, a third TAI, a third RAC, a third RAI, a third RNA identifier, a third RAN area identifier, a third resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect (and / or use) the first gNB-CU / first gNB / first PLMN and / or serving cell), the first gNB and / or base station (e.g., a gNB-DU) may configure an NG interface message (e.g., to configure a UE context having one or more core network entities (e.g., AMF, MME, UPF, SGW, PGW), Initial UE messages and / or one or more UE context configuration-related messages can be transmitted to the core network entities (e.g., AMF, MME) of the first PLMN.

[0288] In one example, in response to / based on the reception of a first message (e.g., an RRC connection request message / RRC connection setup complete message, and / or an RRC connection resumption request message / RRC connection resumption complete message) comprising at least one of a second PLMN identifier, a second cell identifier (and / or a fourth identifier), a second gNB identifier, a second gNB-CU identifier, a second TAC, a second TAI, a second RAC, a second RAI, a second RNA identifier, a second RAN area identifier, a second resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect (and / or use) the second PLMN and / or serving cell, the second gNB and / or base station (e.g., including a gNB-DU) may configure a UE context having one or more core network entities (e.g., an AMF, MME, UPF, SGW, PGW) by configuring an NG interface message (e.g., an initial UE message, and / or one or more UE context configurations). The relevant message can be transmitted to the core network entities (e.g., AMF, MME) of the second PLMN.

[0289] In one example, in response to / based on the reception of a first message (e.g., an RRC connection request message / RRC connection setup complete message, and / or an RRC connection resumption request message / RRC connection resumption complete message) comprising at least one of a second PLMN identifier, a fourth cell identifier (and / or a second identifier), a second gNB identifier, a second gNB-CU identifier, a fourth TAC, a fourth TAI, a fourth RAC, a fourth RAI, a fourth RNA identifier, a fourth RAN area identifier, a fourth resumption identifier, etc. (e.g., indicating that a wireless device is allowed (and / or enabled, enabled, approved) to connect (and / or use) the second gNB-CU / second gNB / second PLMN and / or serving cell, the second gNB and / or base station (e.g., a gNB-DU) may configure a UE context having one or more core network entities (e.g., AMF, MME, UPF, SGW, PGW) by sending an NG interface message (e.g., Initial UE messages and / or one or more UE context configuration-related messages can be transmitted to the core network entities (e.g., AMF, MME) of the second PLMN.

[0290] In one example, in response to / based on receiving a first message, a base station (e.g., gNB, first gNB, second gNB) may select a core network entity (e.g., AMF, MME) based on a serving cell in which a wireless device transmits the first message to the base station (e.g., gNB, first gNB, second gNB, gNB-DU).

[0291] In one example, when a base station receives a first message through one or more first serving cells (e.g., supporting a first PLMN and / or a first gNB-CU / first gNB), the base station may select a core network entity (e.g., AMF, MME) of the first PLMN, and / or transmit an NG interface message (e.g., an initial UE message, and / or one or more UE context configuration related messages) to the selected core network entity of the first PLMN to configure a UE context having one or more core network entities (e.g., AMF, MME, UPF, SGW, PGW).

[0292] In one example, when a base station receives a second message through one or more second serving cells (e.g., supporting a second PLMN and / or a second gNB-CU / second gNB), the base station may select a core network entity (e.g., AMF, MME) of the second PLMN, and / or transmit an NG interface message (e.g., an initial UE message, and / or one or more UE context configuration related messages) to the selected core network entity of the second PLMN to configure a UE context having one or more core network entities (e.g., AMF, MME, UPF, SGW, PGW).

[0293] In one example, when a gNB-DU receives a first message through one or more third serving cells (e.g., supporting a first PLMN and a second PLMN; and / or supporting a first gNB-CU / a first gNB and a second gNB-CU / a second gNB), the base station may select at least one core network entity (e.g., AMF, MME) of the first PLMN and / or the second PLMN, and / or transmit an NG interface message (e.g., an initial UE message, and / or one or more UE context configuration related messages) to at least one selected core network entity of the first PLMN and / or the second PLMN to configure a UE context having one or more core network entities (e.g., AMF, MME, UPF, SGW, PGW).

[0294] In one example, a base station distribution unit may receive a first message from a first base station central unit containing a first mobile phone system network (PLMN) identifier of a first PLMN supported by the first base station central unit. The base station distribution unit may receive a second message from a second base station central unit containing a second PLMN identifier of a second PLMN supported by the second base station central unit. In one example, the base station distribution unit may transmit (e.g., broadcast) at least one third message containing the first PLMN identifier and the second PLMN identifier. The base station distribution unit may receive a fourth message from a wireless device containing one of the first PLMN identifier or the second PLMN identifiers. The base station distribution unit may select one of the first base station central unit and the second base station central unit, which is selected based on one of the first PLMN identifier or the second PLMN identifier. The selected one may support one of the PLMNs of the first PLMN identifier or the second PLMN identifier. The base station distribution unit may forward the fourth message to the selected PLMN.

[0295] In one example, the first message and / or the second message may include at least one of an F1 setup response message, a base station central unit configuration update message, and / or a base station distributed unit configuration update confirmation message. In one example, the base station distributed unit may and / or transmit a fifth message indicating a first F1 setup request to the first base station central unit, or the first message may be a response to the fifth message. The base station distributed unit may and / or transmit a sixth message indicating a second F1 setup request to the second base station central unit, or the second message may be a response to the sixth message.

[0296] In one example, the base station distributed unit may transmit a seventh message indicating a first base station central unit configuration update confirmation to the first base station central unit and / or in response to the reception of the first message. In one example, the base station distributed unit may transmit an eighth message indicating a second base station central unit configuration update confirmation to the second base station central unit and / or in response to the reception of the second message. In one example, at least one third message may include a system information block (e.g., system information block type 1). In one example, the base station distributed unit may transmit a system information block including at least one of a first PLMN identifier and / or a second PLMN identifier to the first base station central unit and / or the second base station central unit. The base station distributed unit may receive at least one third message from the first base station central unit and / or the second base station central unit, and / or at least one third message may include a system information block (e.g., system information block type 1). In one example, the fourth message may include a wireless resource control message. In one example, the base station distribution unit may transmit at least one third message through a first cell supporting at least one of the first PLMN and / or the second PLMN. In one example, the base station distribution unit may transmit a first message containing a first PLMN identifier among at least one third message through a second cell. In one example, the base station distribution unit may transmit a second message containing a second PLMN identifier among at least one third message through a third cell.

[0297] In one example, a base station distribution unit may receive one or more second configuration parameters associated with the second base station central unit and / or the second PLMN from a second base station central unit. The base station distribution unit may transmit one or more second configuration parameters to a first base station central unit. The base station distribution unit may receive at least one system information block from the first base station central unit, comprising at least one of one or more first configuration parameters associated with the first base station central unit and / or the first PLMN (e.g., and / or a first system information block) and / or one or more second configuration parameters associated with the second base station central unit and / or the second PLMN (e.g., and / or a second system information block). The base station distribution unit may transmit (forward / broadcast) at least one system information block. The base station distribution unit may transmit at least one system information block to the second base station central unit.

[0298] In one example, a base station distribution unit may receive from a first base station central unit at least one system information block comprising at least one of one or more first configuration parameters (e.g., and / or a first system information block) associated with the first base station central unit and / or the first PLMN, and / or one or more second configuration parameters (e.g., and / or a second system information block) associated with the second base station central unit and / or the second PLMN. The first base station central unit may receive one or more second configuration parameters from a second base station central unit (e.g., through an interface between the first gNB-CU and the second gNB-CU). The base station distribution unit may transmit (forward / broadcast) at least one system information block. In one example, the base station distribution unit may transmit at least one system information block to the second base station central unit.

[0299] In one example, the base station distribution unit may receive one or more first configuration parameters associated with the first base station central unit and / or the first PLMN from the first base station central unit. The base station distribution unit may receive one or more second configuration parameters associated with the second base station central unit and / or the second PLMN from the second base station central unit. The base station distribution unit may determine at least one system information block comprising at least one of one or more first configuration parameters associated with the first gNB-CU and / or the first PLMN (e.g., and / or the first system information block) and / or one or more second configuration parameters associated with the second base station central unit and / or the second PLMN (e.g., and / or the second system information block). (In one example, the base station distribution unit may transmit at least one system information block to the first base station central unit and / or the second base station ce...

Claims

Claim 1 A method comprising: transmitting a first F1 setup request message to a first base station central unit by a base station distributed unit; receiving a first message from the first base station central unit by the base station distributed unit, the first message including a first PLMN identifier of a first mobile phone system network (PLMN) including the first base station central unit, the first message being a response to the first F1 setup request message; transmitting a second F1 setup request message to a second base station central unit by the base station distributed unit; receiving a second message from the second base station central unit by the base station distributed unit, the second message including a second PLMN identifier of a second PLMN including the second base station central unit, the second message being a response to the second F1 setup request message; and transmitting at least one system information block including the first PLMN identifier and the second PLMN identifier by the base station distributed unit. Claim 2 A method according to claim 1, further comprising: receiving a wireless resource control message based on at least one system information block from a wireless device by the base station distribution unit; and configuring wireless resources for the wireless device based on the wireless resource control message by the base station distribution unit. Claim 3 In paragraph 2, the wireless device is associated with at least one of the first PLMN or the second PLMN. Claim 4 A method according to claim 1, further comprising: receiving packets from at least one of the first base station central unit and the second base station central unit by the base station distribution unit; and transmitting the packets to a wireless device associated with at least one of the first PLMN or the second PLMN by the base station distribution unit. Claim 5 A method according to claim 1, wherein the first message and the second message comprise at least one of an F1 setup response message; a base station central unit configuration update message; or a base station distributed unit configuration update confirmation message. Claim 6 delete Claim 7 A method according to claim 1, wherein the at least one system information block comprises cell parameters for at least one of the first PLMN or the second PLMN, and the cell parameters comprise: a cell identifier of the cell to which the at least one system information block is transmitted; a closed subscriber group identifier of the cell; a first cell identifier of the cell associated with the first PLMN; a second cell identifier of the cell associated with the second PLMN; a first closed subscriber group identifier of the cell associated with the first PLMN; a second closed subscriber group identifier of the cell associated with the second PLMN; a first base station central unit identifier of the first base station central unit; a second base station central unit identifier of the first base station central unit; a first base station identifier of the first base station associated with the first base station central unit; or a second base station identifier of the second base station associated with the second base station central unit. Claim 8 A method according to claim 1, wherein the step of transmitting the at least one system information block comprises the step of transmitting the at least one system information block through a cell shared with the first PLMN and the second PLMN. Claim 9 A method according to claim 1, wherein the at least one system information block comprises: a first system information block including the first PLMN identifier; and a second system information block including the second PLMN identifier. Claim 10 A method according to claim 9, wherein the first system information block comprises at least one of: a first cell identifier of a cell associated with the first PLMN; a first closed subscriber group identifier of the cell associated with the first PLMN; a first base station central unit identifier of the first base station central unit; or a first base station identifier of the first base station associated with the first base station central unit. Claim 11 A method according to claim 9, wherein the first system information block comprises at least one of: a second cell identifier of a cell associated with the second PLMN; a second closed subscriber group identifier of the cell associated with the second PLMN; a second base station central unit identifier of the first base station central unit; or a second base station identifier of the second base station associated with the second base station central unit. Claim 12 A method according to claim 9, wherein the at least one system information block comprises: a first system information block including the first PLMN identifier and transmitted through the first cell of the first PLMN; or at least one of the second system information block including the second PLMN identifier and transmitted through the second cell of the second PLMN. Claim 13 A method according to claim 1, further comprising the step of receiving at least one system information block from the first base station central unit by the base station distribution unit. Claim 14 A method according to claim 1, further comprising the step of transmitting configuration parameters including the second PLMN identifier to the first base station central unit by the base station distribution unit, wherein at least one system information block is based on the configuration parameters. Claim 15 A method according to claim 1, further comprising the step of determining at least one system information block based on the first message and the second message by the base station distribution unit. Claim 16 A method according to claim 1, further comprising the step of transmitting the at least one system information block to at least one of the first base station central unit or the second base station central unit by the base station distribution unit. Claim 17 A method according to claim 1, wherein at least one system information block comprises system information block 1. Claim 18 A method according to claim 1, wherein the base station comprises the first base station central unit, the second base station central unit, and the base station distributed unit. Claim 19 A method according to claim 1, wherein the first base station includes the first base station central unit and the base station distributed unit, and the second base station includes the second base station central unit and the base station distributed unit. Claim 20 A method according to claim 1, wherein the base station distribution unit services at least one of a cell shared by the first PLMN and the second PLMN; a first cell of the first PLMN; or a second cell of the second PLMN. Claim 21 delete Claim 22 delete Claim 23 delete Claim 24 delete Claim 25 delete Claim 26 delete Claim 27 delete Claim 28 delete Claim 29 delete Claim 30 delete Claim 31 delete Claim 32 delete Claim 33 delete Claim 34 delete Claim 35 delete Claim 36 delete Claim 37 delete Claim 38 delete Claim 39 delete Claim 40 delete Claim 41 delete Claim 42 delete Claim 43 delete Claim 44 delete Claim 45 delete Claim 46 delete Claim 47 delete Claim 48 delete Claim 49 delete Claim 50 delete Claim 51 delete Claim 52 delete Claim 53 delete Claim 54 delete Claim 55 delete Claim 56 delete Claim 57 delete Claim 58 delete Claim 59 delete Claim 60 delete Claim 61 delete Claim 62 delete Claim 63 delete Claim 64 delete Claim 65 delete Claim 66 delete Claim 67 delete Claim 68 delete Claim 69 delete Claim 70 delete Claim 71 delete Claim 72 delete Claim 73 delete Claim 74 delete Claim 75 delete Claim 76 delete Claim 77 delete Claim 78 delete Claim 79 delete Claim 80 delete Claim 81 delete Claim 82 delete Claim 83 delete Claim 84 delete Claim 85 delete Claim 86 delete Claim 87 delete Claim 88 delete Claim 89 delete Claim 90 delete Claim 91 delete Claim 92 delete Claim 93 delete Claim 94 delete Claim 95 delete Claim 96 delete Claim 97 delete Claim 98 delete Claim 99 delete Claim 100 delete Claim 101 delete Claim 102 delete Claim 103 delete Claim 104 delete Claim 105 delete Claim 106 delete Claim 107 delete Claim 108 delete Claim 109 delete Claim 110 delete Claim 111 delete Claim 112 delete Claim 113 delete Claim 114 delete Claim 115 delete Claim 116 delete Claim 117 delete Claim 118 delete Claim 119 delete Claim 120 delete Claim 121 delete Claim 122 delete Claim 123 delete Claim 124 delete Claim 125 delete Claim 126 delete Claim 127 delete Claim 128 delete Claim 129 delete Claim 130 delete Claim 131 delete Claim 132 delete Claim 133 delete Claim 134 delete Claim 135 delete Claim 136 delete Claim 137 delete Claim 138 delete Claim 139 delete Claim 140 delete Claim 141 delete Claim 142 delete Claim 143 delete Claim 144 delete Claim 145 delete Claim 146 delete Claim 147 delete Claim 148 delete Claim 149 delete Claim 150 delete Claim 151 delete Claim 152 delete Claim 153 delete Claim 154 delete Claim 155 delete Claim 156 delete Claim 157 delete Claim 158 delete Claim 159 delete Claim 160 delete

Images