Enabling resource coordination in MRSS scenario

Abstract

A method includes identifying, by a first network apparatus, one or more prioritized resources for use by a second network apparatus. The first network apparatus transmits a first message to the second network apparatus, the first message including information relating to the one or more prioritized resources, and receives a second message from the second network apparatus, the second message indicating a coordination of the one or more prioritized resources.

Description

ENABLING RESOURCE COORDINATION IN MRSS SCENARIOFIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, for a method and apparatus for enabling resource coordination in an MRSS scenario.BACKGROUND

[0002] Various deployment architectures are possible with Multi-Radio Access Technology (RAT) Spectrum Sharing (MRSS) between 5G and 6G systems. For example, one deployment architecture may deploy a single vendor MRSS with joint 5G / 6G scheduler or separate schedulers for 5G resources and 6G resources. Another deployment architecture may deploy multi-vendor MRSS with separate schedulers for 5G resources and 6G resources.

[0003] In order to take advantage of dynamic sharing, fast and reliable coordination between a 5G radio access network (RAN) and 6G RAN may be implemented. Different deployments can be expected for 6G RAN which are reflected by the different exchange rate between a 5G L2 scheduler and a 6G L2 scheduler.SUMMARY

[0004] In an aspect of the present disclosure, a method includes identifying, by a first network apparatus, one or more prioritized resources for use by a second network apparatus. The first network apparatus transmits a first message to the second network apparatus, the first message including information relating to the one or more prioritized resources, and receives a second message from the second network apparatus, the second message indicating a coordination of the one or more prioritized resources.

[0005] In an aspect of the method, the one or more prioritized resources include protected resources for a first network that are prioritized for the first network apparatus.

[0006] In an aspect of the method, the second network apparatus uses the prioritized resources under at least one predefined condition.

[0007] In an aspect of the method, the predefined condition includes the first network apparatus having a low load.

[0008] In an aspect of the method, the first message includes a priority flag indicating the prioritized resources.

[0009] In an aspect of the method, the first message includes a validity indicating the time of using the prioritized resources by the first network.

[0010] In an aspect of the method, the prioritized resources are a subset of protected resources and have a predefined validity.

[0011] In an aspect of the method, the prioritized resources include one or more of the following: physical random access channel (PRACH) resources, synchronization signal block (SSB) resources, or paging resources.

[0012] In an aspect of the method, the prioritized resources are associated with an SSB configuration.

[0013] In an aspect of the method, the SSB configuration includes an SSB periodicity and the first network node transmits to the second network node one or more of the following: an SSB adaptation, a PRACH adaptation, or a paging adaptation.

[0014] In an aspect of the method, an indication of the prioritized resources are indicated by an information element (IE) included in an evolved universal terrestrial radio access (E-UTRA) - new radio (NR) cell resource coordination message.

[0015] In an aspect of the method, the first network apparatus operates in first radio access technology (RAT) and the second network apparatus operates in a second RAT.

[0016] In an aspect of the method, the first message includes information relating to one or more of the following: a fixed time in which the prioritized resources pattern repeats, a point in time where a given prioritized resource pattern starts, or a fixed interval in which the allocation of prioritized resources is valid.

[0017] In an aspect of the present disclosure, a method includes receiving, by a user equipment (UE) operating in a first synchronization signal block (SSB) configuration, a first message from a network apparatus, the first message including a dedicated SSB configuration for rate matching, and applying, by the UE, the SSB configuration for rate matching.

[0018] In an aspect of the method, the UE applies at least the first SSB configuration for rate matching.

[0019] In an aspect of the method, the first SSB configuration is a legacy SSB configuration.

[0020] In an aspect of the method, the UE applies at least a second SSB configuration for one or more of the following: LI measurements, L3 measurements, or rate matching.

[0021] In an aspect of the method, the UE receives an indication whether the first SSB or the second SSB is to be used for rate matching.

[0022] In an aspect of the method, the indication whether the first SSB or the second SSB is to be used for rate matching includes an indication based on one or more of the following: an SSB type, a CD-SSB, an NCD-SSB, an SSB on sync raster or no SSB on sync raster.

[0023] In an aspect of the method, the second SSB configuration includes a longer periodicity than the first SSB configuration.

[0024] In an aspect of the method, the UE applies rate matching based on one or more rules in a legacy SSB configuration.

[0025] In an aspect of the method, the UE applies rate matching based on the legacy SSB configuration if the SSB configuration is defined in a synchronization raster.

[0026] In an aspect of the method, the UE applies rate matching based on a second SSB configuration if the legacy SSB configuration defines an SSB transmission not in the synchronization raster.

[0027] In an aspect of the method, the first message is any one of a system information (SI) message or a radio resource control (RRC) message.

[0028] In an aspect of the present disclosure, a UE includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform any of the foregoing methods.

[0029] In an aspect of the present disclosure, a network apparatus includes at least one processor and at least one memory storing instructions which, when executed by the at least one processor, causes the network apparatus at least to perform any of the foregoing methods.

[0030] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0031] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Some example embodiments will now be described with reference to the accompanying drawings.

[0033] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0034] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0035] FIG. 3 is a diagram of an example 5G and 6GMRSS, according to one illustrated aspect of the disclosure;

[0036] FIG. 4 is a diagram of an example embodiment of signals and operations among an RAT1-NG-RAN and a RAT2-NG-RAN, according to one illustrated aspect of the disclosure;

[0037] FIG. 5 is a diagram of an example embodiment of signals and operations among UE, a first node and a second node, according to one illustrated aspect of the disclosure; and

[0038] FIG. 6 is a diagram of an example block diagram of a wireless station or node (e.g., network node (such as gNB), user node or UE, relay node, or other node), according to one illustrated aspect of the present disclosure.DETAILED DESCRIPTION

[0039] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0040] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0041] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE- Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0042] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0043] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0044] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5GNR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated thatembodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0045] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the UE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0046] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0047] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.: o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0048] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0049] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU. A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0050] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en- gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interfaceconnected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0051] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, and / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 5 below.

[0052] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller / cloud-RAN / virtual-RAN (BBU / REC / C-RAN / V-RAN), open-RAN (O- RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0053] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0054] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection withFIG. 6. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0055] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0056] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0057] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. 1 such that the UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0058] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any componentmay communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0059] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0060] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM) 223.

[0061] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described in connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0062] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0063] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide service to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0064] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0065] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics in the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0066] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0067] As mentioned above, in order to take advantage of dynamic sharing, fast and reliable coordination between a 5G radio access network (RAN) and 6G RAN may be implemented. Different deployments can be expected for 6G RAN which are reflected by the different exchange rate between a 5G L2 scheduler and a 6G L2 scheduler.

[0068] Accordingly, 5G / 6G Multi-RAT Spectrum Sharing (MRSS) is a feature for the migration to 6G as it allows new radio (NR) and 6G cells to share the same carrier(s) dynamically adapting to traffic requirements.

[0069] MRSS provides a dynamic spectrum sharing between 5G and 6G. To take advantage of the dynamic sharing, fast and reliable coordination between 5G RAN and 6G RAN may be implemented. In various embodiments, different deployments can be expected for an 6G RAN which are reflected by the different exchange rate between a 5G L2 scheduler and a 6G L2 scheduler.

[0070] For example, an MRS S system with a cloud native RAN deployment for 6G(e.g., cloud deployment) and a classical deployment for 5G (CU / DU and RU are co-located) may result in a delay between the 5G scheduler and 6G scheduler. Accordingly, the exchange rate may be limited due to non-collocated 5G and 6G RAN deployment. Hence, at the NW, side dynamic sharing of resources within each slot is may be effected.

[0071] In an MRSS scenario, in various embodiments, 5G and 6G cells share the same radio unit (RU). FIG. 3 is a diagram of an example 5G and 6G MRSS 300, according to one illustrated aspect of the disclosure. As shown in FIG. 3, a UE 150A connected in a 5G connection to the 5G gNB via the RU, while UE 150B connected in a 6G connection is also connected via the same RU to a 6G NB.

[0072] Accordingly, the same coverage is expected by the 5G MRSS cell and 6G MRSS cell. An inter-RAT resource coordination procedure for MRSS deployment targeting resource optimization and overhead decrease may facilitate these connections.

[0073] Therefore, described herein in further detail is a method to enable a first RAT to indicate dynamically to a second RAT the modification applied to resources (e.g., C-plane resources), which in various embodiments are protected / static resources, and to inform a UE the modification to be applied to a rate-matching pattern.

[0074] In various embodiments, a first gNB from 1st RAT performs one or more of the following: activates additional prioritized uplink resources (e.g., PRACH resources), de-activates prioritized uplink resources (e.g., PRACH resources), activates additional prioritized downlink resources (e.g., paging resources), de-activates prioritized downlink resources (e.g., paging resources), activates prioritized additional downlink signals (e.g., a synchronization signal block (SSB) signal), de-activates some prioritized downlink signals (e.g., SSB signal), modifies the SSB periodicity, and modifies SSB resource usage.

[0075] In various embodiments, the first gNB from the first RAT initiates the procedure by sending a resource coordination request to a second gNB of a second RAT over, for example, the Xn interface. The second gNB extracts the new pattern indicated in the request and replies by sending a response message containing at least an acknowledgement about the reception of request.

[0076] After replying to the first gNB of the first RAT, the second gNB of second RAT may update the resource allocation for user-plane channels. In various embodiments, validity is added to the request.

[0077] In various embodiments, SSB periodicity is indicated to a UE via SIB1 or RRC config message. This periodicity is used by UE for rate-matching purposes.

[0078] In various embodiments, for a 5G or 6G cell, the SSB periodicity is 20 ms. If these cells enable the SSB adaptation feature, then SSB periodicity can be extended (e.g., 40 ms). Then, the UEs will consider the 40 ms periodicity for rate-matching, which means that the UE does not assume any SSB transmission within the period of 40 ms.

[0079] In addition, the UE may assume 40 ms for SSB monitoring, L1 / L3 measurements and for rate- matching computation. However, the NW does not transmit data in the free SSB resources to not confuse legacy UE and idle / inactive UE that they keep monitoring SSB every 20 ms. Any transmission in these resources increase the interference at UE side. Accordingly, the UE performs rate matching around what it supposes free resources for data, while the network is not using them for any transmission to not impact legacy UEs.

[0080] Accordingly, in various embodiments, the UE uses the indicated SSB periodicity in SSB monitoring, L1 / L3 measurements and considers legacy SSB in rate-matching around SSB to avoid wrong rate matching around SSB resources.

[0081] In various embodiments, the UE determines whether to do rate matching based on configured periodicity in SIB 1 / RRC or based on (dynamically) adapted SSB periodicity depending on one or more of the following: if the SSB is transmitted in the synchronization raster then UE applies legacy SSB periodicity configured in SIB 1 / RRC for rate matching, or if the SSB is not transmitted in the synchronization raster then UE applies adapted SSB periodicity for rate matching. In various embodiments, signaling that configures or indicates SSB adaptation also informs if rate matching is done based on initial SSB periodicity or based on adapted SSB periodicity.

[0082] Described herein is resource optimization in a shared network (e.g., an MRSS network) that shares spectrum between two RATs (e.g., 5G and 6G). Resource categorizations for an MRSS network are described herein.

[0083] In various embodiments, three resource categories for an MRSS cell may include protected resources, prioritized resources, and data resources. In various embodiments, protectedresources include a radio resource (frequency resource, time resource) that is reserved for a given RAT. These resources are static and no validity is associated. One example of protected resources is 5G SSB resources. Each RAT should be aware of the protected resources in MRSS cell to avoid that one RAT is using the protected resources of the other RAT.

[0084] In various embodiments, prioritized resources are protected radio resources that a given RAT has a priority to use them, while they could be used by the second RAT when they are available. A priority flag may be included as an indication that some protected resources can be used by the second RAT under some conditions. One example could be when the first RAT has low load, a part / all its protected resources can be used by the second RAT without any harm to legacy devices of the first RAT, (e.g., PRACH resources, SSB resources and paging resources).

[0085] In various embodiments, data resources (e.g., for user-plane channels) are radio resources that are used for user data, network data, and service data, each playing a crucial role in the overall functionality and performance of the MRSS ecosystem. Neither 5G nor 6G has a given priority to use those resources except some types of services, (e.g., URLLC services). The accessibility to data resources is based on the need of each RAT and decided by the scheduling mechanism.

[0086] The table below shows an example of protected and prioritized resource indications.

[0087] Therefore, in an MRSS cell, resource coordination information may be exchanged between the 6G network entity (e.g.,gNB) and 5G gNB to optimize the resource sharing process between RATs. For that, an inter-RAT resource coordination signaling procedure (e.g., X2AP and F1AP message exchange) may be utilized, with the inclusion of the prioritized resources in the coordination procedure.

[0088] In various embodiments, for MRSS an XnAP signaling procedure for inter-RAT resource coordination may be utilized similar to conventional E-UTRA - NR Cell Resource Coordination procedure. In an MRSS cell, this procedure may be triggered when a resource reservation indication occurs, where the NR or 6G must inform each other on the reserved dataand / or control needed resources, or a resource release indication occurs where one RAT informs the other if some protected control resources can be released into the prioritized resources.

[0089] In various embodiments, a data resources coordination information exchange is effected (e.g., over the X2AP).

[0090] When data resources coordination is needed between 5G gNB and 6G gNB due to resource allocation change (e.g., load change), a gNB of a first RAT initiates the procedure by sending the E-UTRA - NR CELL RESOURCE COORDINATION REQUEST message to the gNB of a second RAT over the X2AP interface.

[0091] The gNB of a second RAT extracts the Data Traffic Resource Indication information element (IE) from the message, and replies by sending the E-UTRA - NR CELL RESOURCE COORDINATION RESPONSE message. The gNB of a second RAT calculates the full first RAT resource allocation by combining the “Data Traffic Resource Indication ” IE and the “Protected E-UTRA Resource Indication ” IE that were most recently received from the first RAT, described below.

[0092] In various embodiments, the “Data Traffic Resource Indication” IE may be defined as follows:Activation SFNCHOICE Shared Resource Type>UL Only Sharing»UL Resource Bitmap>UL and DL Sharing»CHOICE UL Resources»>Unchanged»>Changed»»UL Resource Bitmap»CHOICE DL Resources»>Unchanged»>Changed»»DL Resource Bitmap Reserved Subframe Pattern.

[0093] In various embodiments, control resources coordination information (e.g., over the X2AP) may be effected.

[0094] For example, control resource coordination between the 5G gNB and 6G gNB may be effected. When some NR control resources (e.g., PRACH, Paging and / or SSB resources) areavailable due to some network changes (low load, NES state,... , etc.), the NR may indicate the availability of those resources at a given starting time and periodicity.

[0095] In various embodiments, an IE “Prioritized Resource List” may be added in the process of E-UTRA - NR Cell Resource Coordination to indicate the prioritized resources for one RAT that can be used by the other RAT once available. In various embodiments, the “Prioritized Resource List” IE may be defined as follows:Protected Resource List>Protected Resource List Item»Resource Type»Intra-PRB Protected Resource Footprint»Protected Footprint Frequency Pattern»Protected Footprint Time Pattern»>Protected Footprint Time-periodicity»>Protected Footprint Start TimePrioritized Resource List>Prioritized Resource List Item»Resource Type»Intra-PRB Protected Resource Footprint» Prioritized Footprint Frequency Pattern» Prioritized Footprint Time Pattern»> Prioritized Footprint Time-periodicity»> Prioritized Footprint Start Time»> Prioritized Footprint validityMBSFN Control Region LengthPDCCH Region Length.

[0096] In various embodiments, prioritized resources may be defined by a time pattern that includes one or more of the following:Prioritized Footprint Time-periodicity: a fixed time in which the prioritized resources pattern repeats.Prioritized Footprint Start Time: it’s the point in time (e.g. subframe number or slot number), where a given prioritized resource pattern starts (e.g. relative to an absolute time).Prioritized Footprint validity: a fixed interval in which the allocation of prioritized resources does not change. The may be defined by a start time and an end time or by a start time and a time window.

[0097] In various embodimetns, the first RAT indicates the availability of the resources that are prioritized for the second RAT for a given period by indicating the prioritized resources timepatern elements in the IE explained above. The prioritized resources are available until the validity time is expired or until a new notification that the prioritized resources are no more available is sent from the first RAT.

[0098] FIG. 4 is a diagram of an example embodiment of signals and operations among an RAT1-NG-RAN and a RAT2-NG-RAN, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 4 may correspond to similar components described above in FIGS. 1-3. It will be understood that a described signal may have associated operations and a described operation may have associated signals. In the example architecture shown in FIG. 4, the existence of an MRSS-NG-RAN is shown, however the signals and operations described herein are applicable regardless of any specific RAN architecture choices.

[0099] At operation 401, the RATI resources needed are identified by the RATl-gNB-DU. At operation 402, the RATl-gNB-DU triggers a gNB-DU configuration update to the RATl-gNB- CU. In various embodiments, the gNB-DU configuration update is performed over Fl when resource allocation needs to be initialized or updated and includes the introduced “Prioritized Resource List” IE described above.

[0100] At operation 403, the RATl-gNB-CU updates the RAT needed resources sends a gNB- DU configuration acknowledge signal to the RATl-gNB-DU (e.g., over the Fl AP) and the RATl- gNB-DU receives the configuration acknowledge signal.

[0101] At operation 404, the RAT2-gNB-DU shares RAT2 cell resource configuration information with the RAT2-gNB-CU.

[0102] At operation 405, the RATl-gNB-CU transmits an E-UTRA-NR cell resource coordination request that includes the prioritized resource list to the RAT2-gNB-CU (e.g., over the XnAP) and the RAT2-gNB-CU receives the E-UTRA-NR cell resource coordination request that includes the prioritized resource list.

[0103] At operation 406, the RAT2-gNB-CU triggers the gNB-CU Configuration Update (e.g., over Fl) to the RAT2-gNB-DU. In various embodiments, the gNB-CU configuration cpdate is triggered in various scenarios within the 5G NR (New Radio) network as initial configuration, dynamic configuration changes, network optimization, resource allocation, security updates, frequency band changes, network synchronization, resource allocation, etc.

[0104] At operation 407, the RAT2-gNB-DU updates the RAT2 needed resources and at operation 408, the RAT2-gNB-DU sends a gNB-CU configuration acknowledge message to theRAT2-gNB-CU (e.g., over the Fl AP) and the RAT2-gNB-CU receives the gNB-CU configuration acknowledge message.

[0105] At operation 409, the RAT2-gNB-CU triggers an E-UTRA-NR cell resource coordination response including the prioritized resource list to the RATl-gNB-CU (e.g., over XnAP) and the RATl-gNB-CU receives the E-UTRA-NR cell resource coordination response including the prioritized resource list.

[0106] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 4.

[0107] FIG. 5 is a diagram of an example embodiment of signals and operations among UE, a first node and a second node, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 4 may correspond to similar components described above in FIGS. 1-3. It will be understood that a described signal may have associated operations and a described operation may have associated signals. In the example architecture shown in FIG. 4, the first node may be a network node of a first RAT (RATI) while the second node may be a network node of a second RAT (RAT2).

[0108] At operation 501, the first node that has configured a UE with a first SSB periodicity activates a new SSB configuration. In various embodiments, the new SSB configuration may include enabling an SSB adaptation feature and change the SSB configuration (e.g., SSB periodicity).

[0109] At operation 502, the first node transmits the SSB configuration and validity to the second node and the second node receives the SSB configuration and validity.

[0110] At operation 503, the first node transmits a new rate-matching rules indication message to the UE and the UE receives the new rate-matching rules indication message. Accordingly, at operation 504, the UE applies the new rate matching rules.

[0111] In various embodiments, the new SSB configuration may be applied between two cells from the same RAT. In various embodiments, the indication from the NW (e.g., first node) may include information about rate-matching pattern associated with legacy SSB configuration. In various embodiments, the indication may be signaled by a system information (SI) message for idle / inactive UEs or a radio resource control (RRC) message.

[0112] The operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 5. In embodiments, the operations may not include every operation illustrated in FIG. 5. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 5.

[0113] The following describes operations from the perspective of a UE. From such a perspective, a method includes receiving, by the UE operating in a first synchronization signal block (SSB) configuration, a first message from a network apparatus, the first message including a dedicated SSB configuration for rate matching, and applying, by the UE, the SSB configuration for rate matching.

[0114] The following describes operations from the perspective of a network apparatus (e.g., first network apparatus). From such a perspective, a method includes identifying, by the first network apparatus, one or more prioritized resources for use by a second network apparatus, transmitting, by the first network apparatus, a first message to the second network apparatus, the first message including information relating to the one or more prioritized resources, and receiving, by the first network apparatus, a second message from the second network apparatus, the second message indicating a coordination of the one or more prioritized resources.

[0115] FIG. 6 is a block diagram of a wireless station or node (e.g., UE, user device, AP, BS, eNB, gNB, RAN node, network node, TRP, or other node) 600, according to one illustrated aspect of the present disclosure. The wireless station 600 may include, for example, one or more (e.g., two as shown in FIG. 6) RF (radio frequency) or wireless transceivers 602A, 602B, where each wireless transceiver includes a transmitter to transmit signals and a receiver to receive signals. Thewireless station also includes a processor or control unit / entity (controller) 604 to execute instructions or software and control transmission and receptions of signals, and a memory 606 to store data and / or instructions.

[0116] Processor 604 may also make decisions or determinations, generate frames, packets or messages for transmission, decode received frames or messages for further processing, and other tasks or functions described herein. Processor 604, which may be a baseband processor, for example, may generate messages, packets, frames or other signals for transmission via wireless transceiver 602 (602A or 602B). Processor 604 may control transmission of signals or messages over a wireless network, and may control the reception of signals or messages, etc., via a wireless network (e.g., after being down-converted by wireless transceiver 602, for example). Processor 604 may be programmable and capable of executing software or other instructions stored in memory or on other computer media to perform the various tasks and functions described above, such as one or more of the tasks or methods described above. Processor 604 may be (or may include), for example, hardware, programmable logic, a programmable processor that executes software or firmware, and / or any combination of these. Using other terminology, processor 604 and transceiver 602 together may be considered as a wireless transmitter / receiver system, for example.

[0117] In addition, referring to FIG. 6, a controller (or processor) 608 may execute software and instructions, and may provide overall control for the station 600, and may provide control for other systems not shown in FIG. 6, such as controlling input / output devices (e.g., display, keypad), and / or may execute software for one or more applications that may be provided on wireless station 600, such as, for example, an email program, audio / video applications, a word processor, a Voice over IP application, or other application or software.

[0118] In addition, a storage medium may be provided that includes stored instructions, which when executed by a controller or processor may result in the processor 604, or other controller or processor, performing one or more of the functions or tasks described above.

[0119] According to another example embodiment, RF or wireless transceiver(s) 602A / 602B may receive signals or data and / or transmit or send signals or data. Processor 604 (and possibly transceivers 602A / 602B) may control the RF or wireless transceiver 602A or 602B to receive, send, broadcast or transmit signals or data.

[0120] Example embodiments are provided or described for each of the example methods,including: An apparatus (e.g., 600, FIG. 6) including means (e.g., processor 604, RF transceivers 602A and / or 602B, and / or memory 606, in FIG. 6) for carrying out any of the methods; a non- transitory computer-readable storage medium (e.g., memory 606, FIG. 6) comprising instructions stored thereon that, when executed by at least one processor (processor 604, FIG. 6), are configured to cause a computing system (e.g., 600, FIG. 6) to perform any of the example methods; and an apparatus (e.g., 600, FIG. 6) including at least one processor (e.g., processor 604, FIG. 6), and at least one memory (e.g., memory 606, FIG. 6) including computer program code, the at least one memory (606) and the computer program code configured to, with the at least one processor (604), cause the apparatus (e.g., 600) at least to perform any of the example methods.

[0121] Further embodiments of the present disclosure include the following examples.

[0122] Example 1.1. A network apparatus, comprising: means for identifying, by a first network apparatus, one or more prioritized resources for use by a second network apparatus; means for transmitting, by the first network apparatus, a first message to the second network apparatus, the first message including information relating to the one or more prioritized resources; and means for receiving, by the first network apparatus, a second message from the second network apparatus, the second message indicating a coordination of the one or more prioritized resources.

[0123] Example 1.2. The network apparatus of example 1.1, wherein the one or more prioritized resources include protected resources for a first network that are prioritized for the first network apparatus.

[0124] Example 1.3. The network apparatus of any one of examples 1.1 or 1.2, wherein the second network apparatus uses the prioritized resources under at least one predefined condition.

[0125] Example 1.4. The network apparatus of example 1.3, wherein the predefined condition includes the first network apparatus having a low load.

[0126] Example 1.5. The network apparatus of any one of examples 1.1 to 1.4, wherein the first message includes a priority flag indicating the prioritized resources.

[0127] Example 1.6. The network apparatus of any one of examples 1.1 to 1.4, wherein the first message includes a validity indicating the time of using the prioritized resources by thefirst network.

[0128] Example 1.7. The network apparatus of any one of examples 1.1 to 1.6, wherein the prioritized resources are a subset of protected resources and have a predefined validity.

[0129] Example 1.8. The network apparatus of any one of examples 1.1 to 1.7, wherein the prioritized resources include one or more of the following: physical random access channel (PRACH) resources, synchronization signal block (SSB) resources, or paging resources.

[0130] Example 1.9. The network apparatus of any one of examples 1.1 to 1.8, wherein the prioritized resources are associated with an SSB configuration.

[0131] Example 1.10. The network apparatus of example 1.9, wherein the SSB configuration includes an SSB periodicity and the first network node transmits to the second network node one or more of the following: an SSB adaptation, a PRACH adaptation, or a paging adaptation.

[0132] Example 1.11. The network apparatus of any one of examples 1.1 to 1.10, wherein an indication of the prioritized resources are indicated by an information element (IE) included in an evolved universal terrestrial radio access (E-UTRA) - new radio (NR) cell resource coordination message.

[0133] Example 1.12. The network apparatus of any one of examples 1.1 to 1.11, wherein the first network apparatus operates in first radio access technology (RAT) and the second network apparatus operates in a second RAT.

[0134] Example 1.13. The network apparatus of any one of examples 1.1 to 1.12, wherein the first message includes information relating to one or more of the following: a fixed time in which the prioritized resources pattern repeats, a point in time where a given prioritized resource pattern starts, or a fixed interval in which the allocation of prioritized resources is valid.

[0135] Example 2.1. A user equipment (UE), comprising: means for receiving, by the UE operating in a first synchronization signal block (SSB) configuration, a first message from a network apparatus, the first message including a dedicated SSB configuration for rate matching; and means for applying, by the UE, the SSB configuration for rate matching.

[0136] Example 2.2. The UE of example 2.1 , wherein the UE applies at least the first SSB configuration for rate matching.

[0137] Example 2.3. The UE of example 2.2, wherein the first SSB configuration is alegacy SSB configuration.

[0138] Example 2.4. The UE of example 2.1, wherein the UE applies at least a second SSB configuration for one or more of the following: LI measurements, L3 measurements, or rate matching.

[0139] Example 2.5. The UE of example 2.4, wherein the UE receives an indication whether the first SSB or the second SSB is to be used for rate matching.

[0140] Example 2.6. The UE of example 2.5, wherein the indication whether the first SSB or the second SSB is to be used for rate matching includes an indication based on one or more of the following: an SSB type, a CD-SSB, an NCD-SSB, an SSB on sync raster or no SSB on sync raster.

[0141] Example 2.7. The UE of any one of examples 2.1 to 2.6, wherein the second SSB configuration includes a longer periodicity than the first SSB configuration.

[0142] Example 2.8. The UE of any one of examples 2.1 to 2.6, wherein the UE applies rate matching based on one or more rules in a legacy SSB configuration.

[0143] Example 2.9. The UE of example 2.8, wherein the UE applies rate matching based on the legacy SSB configuration if the SSB configuration is defined in a synchronization raster.

[0144] Example 2.10. The UE of example 2.8, wherein the UE applies rate matching based on a second SSB configuration if the legacy SSB configuration defines an SSB transmission not in the synchronization raster.

[0145] Example 2.11. The UE of any one of examples 2.1 to 2.10, wherein the first message is any one of a system information (SI) message or a radio resource control (RRC) message.

[0146] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[0147] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[0148] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[0149] The phrases “in an embodiment,” “in embodiments,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) ”

[0150] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta- languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist in more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[0151] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

WHAT IS CLAIMED IS:

1. A method, comprising: identifying, by a first network apparatus, one or more prioritized resources for use by a second network apparatus; transmitting, by the first network apparatus, a first message to the second network apparatus, the first message including information relating to the one or more prioritized resources; and receiving, by the first network apparatus, a second message from the second network apparatus, the second message indicating a coordination of the one or more prioritized resources.

2. The method of claim 1, wherein the one or more prioritized resources include protected resources for a first network that are prioritized for the first network apparatus.

3. The method of any one of claims 1 or 2, wherein the second network apparatus uses the prioritized resources under at least one predefined condition.

4. The method of claim 3, wherein the predefined condition includes the first network apparatus having a low load.

5. The method of any one of claims 1 to 4, wherein the first message includes a priority flag indicating the prioritized resources.

6. The method of any one of claims 1 to 4, wherein the first message includes a validity indicating the time of using the prioritized resources by the first network.

7. The method of any one of claims 1 to 6, wherein the prioritized resources are a subset of protected resources and have a predefined validity.

248. The method of any one of claims 1 to 7, wherein the prioritized resources include one or more of the following: physical random access channel (PRACH) resources, synchronization signal block (SSB) resources, or paging resources.

9. The method of any one of claims 1 to 8, wherein the prioritized resources are associated with an SSB configuration.

10. The method of claim 9, wherein the SSB configuration includes an SSB periodicity and the first network node transmits to the second network node one or more of the following: an SSB adaptation, a PRACH adaptation, or a paging adaptation.

11. The method of any one of claims 1 to 10, wherein an indication of the prioritized resources are indicated by an information element (IE) included in an evolved universal terrestrial radio access (E-UTRA) - new radio (NR) cell resource coordination message.

12. The method of any one of claims 1 to 11, wherein the first network apparatus operates in first radio access technology (RAT) and the second network apparatus operates in a second RAT.

13. The method of any one of claims 1 to 12, wherein the first message includes information relating to one or more of the following: a fixed time in which the prioritized resources pattern repeats, a point in time where a given prioritized resource pattern starts, or a fixed interval in which the allocation of prioritized resources is valid.

14. A method, comprising: receiving, by a user equipment (UE) operating in a first synchronization signal block (SSB) configuration, a first message from a network apparatus, the first message including a dedicated SSB configuration for rate matching; and applying, by the UE, the SSB configuration for rate matching.

15. The method of claim 14, wherein the UE applies at least the first SSB configuration for rate matching.

16. The method of claim 15, wherein the first SSB configuration is a legacy SSB configuration.

17. The method of claim 14, wherein the UE applies at least a second SSB configuration for one or more of the following: LI measurements, L3 measurements, or rate matching.

18. The method of claim 17, wherein the UE receives an indication whether the first SSB or the second SSB is to be used for rate matching.

19. The method of claim 18, wherein the indication whether the first SSB or the second SSB is to be used for rate matching includes an indication based on one or more of the following: an SSB type, a CD-SSB, an NCD-SSB, an SSB on sync raster or no SSB on sync raster.

20. The method of any one of claims 14 to 19, wherein the second SSB configuration includes a longer periodicity than the first SSB configuration.

21. The method of any one of claims 14 to 19, wherein the UE applies rate matching based on one or more rules in a legacy SSB configuration.

22. The method of claim 21, wherein the UE applies rate matching based on the legacy SSB configuration if the SSB configuration is defined in a synchronization raster.

23. The method of claim 21, wherein the UE applies rate matching based on a second SSB configuration if the legacy SSB configuration defines an SSB transmission not in the synchronization raster.

24. The method of any one of claims 14 to 23, wherein the first message is any one of a system information (SI) message or a radio resource control (RRC) message.

25. A network apparatus, comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the network apparatus at least to perform a method as in any one of claims 1 to 13.

26. A user equipment (UE), comprising: at least one processor; and at least one memory storing instructions which, when executed by the at least one processor, causes the UE at least to perform a method as in any one of claims 14 to 24.

27. A processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1 to 24.27

Images