Dynamic network sharing

The dynamic network sharing method addresses the inefficiencies in current network sharing by using a DyNS function to dynamically adjust network cell activation and deactivation, optimizing energy consumption and resource allocation for improved performance and user experience.

WO2024231779A1PCT designated stage expired Publication Date: 2024-11-14NOKIA TECHNOLOGIES OY

Patent Information

Application Number
PCT/IB2024/054155
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-09
Filing Date
2024-04-29
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current network sharing between mobile operators lacks dynamic procedures for adapting to energy efficiency and user load requirements, leading to inefficient energy usage and suboptimal network resource utilization.

Method used

Implementing a dynamic network sharing (DyNS) method that allows operators to activate or deactivate network cells based on real-time energy and load conditions, using a DyNS function to identify and communicate with target network entities for temporary sharing agreements, optimizing energy consumption and resource allocation.

Benefits of technology

This approach conserves network resources, optimizes energy usage, and enhances user experience by dynamically adapting to changing conditions, enabling efficient energy savings and improved network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2024054155_14112024_PF_FP_ABST
    Figure IB2024054155_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Systems, methods, apparatuses, and computer program products for dynamic network sharing. One method may include transmitting towards at least one target network entity at least one network sharing activation request, receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection, in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.
Need to check novelty before this filing date? Find Prior Art

Description

DYNAMIC NETWORK SHARINGRELATED APPLICATION

[0001] This application claims priority to, and the benefit of, US Provisional Application No. 63 / 464979, filed May 9th, 2023, the contents of which are hereby incorporated by reference in their entirety.TECHNICAL FIELD

[0002] Some example embodiments may generally relate to mobile or wireless telecommunication systems, such as 3rdGeneration Partnership Project (3GPP) Long Term Evolution (LTE), 5thgeneration (5G) radio access technology (RAT), new radio (NR) access technology, 6thgeneration (6G), and / or other communications systems. For example, certain example embodiments may relate to systems and / or methods for network sharing.BACKGROUND

[0003] Examples of mobile or wireless telecommunication systems may include radio frequency (RF) 5G RAT, the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN), LTE Evolved UTRAN (E-UTRAN), LTE- Advanced (LTE-A), LTE-A Pro, NR access technology, and / or MulteFire Alliance. 5G wireless systems refer to the next generation (NG) of radio systems and network architecture. A 5G system is typically built on a 5G NR, but a 5G (or NG) network may also be built on E- UTRA radio. It is expected that NR can support service categories such as enhanced mobile broadband (eMBB), ultra-reliable low-latency-communication (URLLC), and massive machine-type communication (mMTC). NR is expected to deliver extreme broadband, ultra- robust, low-latency connectivity, and massive networking to support the Internet of Things (loT). The next generation radio access network (NG-RAN) represents the radio access network (RAN) for 5G, which may provide radio access for NR, LTE, and LTE-A. It is noted that the nodes in 5G providing radio access functionality to a user equipment (e.g., similar to the Node B in UTRAN or the Evolved Node B (eNB) in LTE) may be referred to as next-generation Node B (gNB) when built on NR radio, and may be referred to as next-generation eNB (NG- eNB) when built on E-UTRA radio.SUMMARY

[0004] In accordance with some example embodiments, a method may include transmitting towards at least one target network entity at least one network sharing activation request. The method may further include receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The method may further include, in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.

[0005] In accordance with certain example embodiments, an apparatus may include means for transmitting towards at least one target network entity at least one network sharing activation request. The apparatus may further include means for receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The apparatus may further include means for, in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.

[0006] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include transmitting towards at least one target network entity at least one network sharing activation request. The method may further include receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The method may further include, in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.

[0007] In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting towards at least one target network entity at least one network sharing activation request. The method may further include receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The method may further include, in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.

[0008] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit towards at least one target network entityat least one network sharing activation request. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to, in response to the receiving the at least one network sharing activation acknowledgement, deactivate at least one source cell.

[0009] In accordance with various example embodiments, an apparatus may include transmitting circuitry configured to transmit towards at least one target network entity at least one network sharing activation request. The apparatus may further include receiving circuitry configured to receive from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The apparatus may further include deactivating circuitry configured to, in response to the receiving the at least one network sharing activation acknowledgement, deactivate at least one source cell.

[0010] In accordance with some example embodiments, a method may include receiving from at least one source network entity at least one network sharing activation request. The method may further include determining whether the at least one network sharing activation request is approved. The method may further include transmitting towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The method may further include, when the at least one network sharing activation request is approved, activating at least one target cell.

[0011] In accordance with certain example embodiments, an apparatus may include means for receiving from at least one source network entity at least one network sharing activation request. The apparatus may further include means for determining whether the at least one network sharing activation request is approved. The apparatus may further include means for transmitting towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The apparatus may further include means for, when the at least one network sharing activation request is approved, activating at least one target cell.

[0012] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving from at least onesource network entity at least one network sharing activation request. The method may further include determining whether the at least one network sharing activation request is approved. The method may further include transmitting towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The method may further include, when the at least one network sharing activation request is approved, activating at least one target cell.

[0013] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving from at least one source network entity at least one network sharing activation request. The method may further include determining whether the at least one network sharing activation request is approved. The method may further include transmitting towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The method may further include, when the at least one network sharing activation request is approved, activating at least one target cell.

[0014] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive from at least one source network entity at least one network sharing activation request. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to determine whether the at least one network sharing activation request is approved. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to transmit towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to, when the at least one network sharing activation request is approved, activate at least one target cell.

[0015] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to receive from at least one source network entity at least one network sharing activation request. The apparatus may further include determining circuitry configured to determine whether the at least one network sharing activation request is approved. The apparatus may further include transmitting circuitry configured to transmit towards the at least one source network entity at least one network sharing activation acknowledgement or at leastone network sharing activation rejection. The apparatus may further include activating circuitry configured to, when the at least one network sharing activation request is approved, activate at least one target cell.

[0016] In accordance with some example embodiments, a method may include transmitting to at least one network entity at least one network sharing release request.

[0017] In accordance with certain example embodiments, an apparatus may include means for transmitting to at least one network entity at least one network sharing release request.

[0018] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include transmitting to at least one network entity at least one network sharing release request.

[0019] In accordance with some example embodiments, a computer program product may perform a method. The method may include transmitting to at least one network entity at least one network sharing release request.

[0020] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit to at least one network entity at least one network sharing release request.

[0021] In accordance with various example embodiments, an apparatus may include transmitting circuitry configured to transmit to at least one network entity at least one network sharing release request.

[0022] In accordance with some example embodiments, a method may include receiving from at least one network entity at least one network sharing release request. The method may further include determining whether the at least one network sharing release request is approved.

[0023] In accordance with certain example embodiments, an apparatus may include means for receiving from at least one network entity at least one network sharing release request. The apparatus may further include means for determining whether the at least one network sharing release request is approved.

[0024] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include receiving from at least onenetwork entity at least one network sharing release request. The method may further include determining whether the at least one network sharing release request is approved.

[0025] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving from at least one network entity at least one network sharing release request. The method may further include determining whether the at least one network sharing release request is approved.

[0026] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive from at least one network entity at least one network sharing release request. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to determine whether the at least one network sharing release request is approved.

[0027] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to receive from at least one network entity at least one network sharing release request. The apparatus may further include determining circuitry configured to determine whether the at least one network sharing release request is approved.

[0028] In accordance with some example embodiments, a method may include authenticating and authorizing a source network function. The method may further include receiving a dynamic network sharing request from or through the source network function. The method may further include attempting to identify at least one target network entity for a provided geographical area, and at least one of the following: if no target network entity is identified for the provided geographical area, transmit a dynamic network sharing rejection towards the source network function, transmit identification of at least one identified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0029] In accordance with certain example embodiments, an apparatus may include means for authenticating and authorizing a source network function. The apparatus may further include means for receiving a dynamic network sharing request from or through the source network function. The apparatus may further include means for attempting to identify at least one target network entity for a provided geographical area, and at least one of the following: if no target network entity is identified for the provided geographical area, transmit a dynamic network sharing rejection towards the source network function, transmit identification of at least oneidentified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0030] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method. The method may include authenticating and authorizing a source network function. The method may further include receiving a dynamic network sharing request from or through the source network function. The method may further include attempting to identify at least one target network entity for a provided geographical area, and at least one of the following: if no target network entity is identified for the provided geographical area, transmit a dynamic network sharing rejection towards the source network function, transmit identification of at least one identified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0031] In accordance with some example embodiments, a computer program product may perform a method. The method may include authenticating and authorizing a source network function. The method may further include receiving a dynamic network sharing request from or through the source network function. The method may further include attempting to identify at least one target network entity for a provided geographical area, and at least one of the following: if no target network entity is identified for the provided geographical area, transmit a dynamic network sharing rejection towards the source network function, transmit identification of at least one identified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0032] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to authenticate and authorize a source network function. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to receive a dynamic network sharing request from or through the source network function. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to attempt to identify at least one target network entity for a provided geographical area, and at least one of the following: if no target network entity is identified for the provided geographical area, transmita dynamic network sharing rejection towards the source network function, transmit identification of at least one identified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0033] In accordance with various example embodiments, an apparatus may include authenticating circuitry configured to authenticate and authorize a source network function. The apparatus may further include receiving circuitry configured to receive a dynamic network sharing request from or through the source network function. The apparatus may further include identifying circuitry configured to attempt to identify at least one target network entity for a provided geographical area, and at least one of the following: if no target network entity is identified for the provided geographical area, transmit a dynamic network sharing rejection towards the source network function, transmit identification of at least one identified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0034] In accordance with some example embodiments, a method may include receiving a dynamic network sharing request from a source network entity. The method may further include attempting to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical area associated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.

[0035] In accordance with certain example embodiments, an apparatus may include means for receiving a dynamic network sharing request from a source network entity. The apparatus may further include means for attempting to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical area associated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.

[0036] In accordance with various example embodiments, a non-transitory computer readable medium may include program instructions that, when executed by an apparatus, cause theapparatus to perform at least a method. The method may include receiving a dynamic network sharing request from a source network entity. The method may further include attempting to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical area associated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.

[0037] In accordance with some example embodiments, a computer program product may perform a method. The method may include receiving a dynamic network sharing request from a source network entity. The method may further include attempting to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical area associated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.

[0038] In accordance with certain example embodiments, an apparatus may include at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive a dynamic network sharing request from a source network entity. The at least one memory and instructions, when executed by the at least one processor, may further cause the apparatus at least to attempt to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical area associated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.

[0039] In accordance with various example embodiments, an apparatus may include receiving circuitry configured to receive a dynamic network sharing request from a source network entity. The apparatus may further include identifying circuitry configured to attempt to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical areaassociated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.BRIEF DESCRIPTION OF THE DRAWINGS

[0040] For a proper understanding of example embodiments, reference should be made to the accompanying drawings, wherein:

[0041] FIGs. 1A and IB illustrate a generic architecture of some example embodiments of such procedures to be executed between network entities of different operators;

[0042] FIG. 2 illustrates an example of a signaling diagram according to various example embodiments;

[0043] FIG. 3 illustrates an example of a signaling diagram according to certain example embodiments;

[0044] FIG. 4 illustrates an example of a signaling diagram according to some example embodiments;

[0045] FIG. 5 illustrates an example of a signaling diagram according to various example embodiments;

[0046] FIG. 6 illustrates an example of a signaling diagram according to certain example embodiments;

[0047] FIG. 7 illustrates an example of a flow diagram of a method according to some example embodiments;

[0048] FIG. 8 illustrates an example of a flow diagram of another method according to various example embodiments;

[0049] FIG. 9 illustrates an example of a flow diagram of another method according to certain example embodiments;

[0050] FIG. 10 illustrates an example of a flow diagram of another method according to some example embodiments;

[0051] FIG. 11 illustrates an example of a flow diagram of another method according to various example embodiments;

[0052] FIG. 12 illustrates an example of a flow diagram of another method according to certain example embodiments;

[0053] FIG. 13 illustrates an example of various network devices according to some example embodiments; and

[0054] FIG. 14 illustrates an example of a 5G network and system architecture according to various example embodiments.DETAILED DESCRIPTION

[0055] It will be readily understood that the components of certain example embodiments, as generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for dynamic network sharing is not intended to limit the scope of certain example embodiments, but is instead representative of selected example embodiments.

[0056] 3GPP continues to develop network energy savings (e.g., RAN1 / 2 / 3 / 4) for release (Rel-18) NR and Service and System Aspects (SA)1 for Rel-19 NR. For example, one of the strategies to save energy with mobile networks is to shut down some RAN nodes during periods of low usage. Based upon energy efficiency (EE) calculations and objectives, a local operator (i.e., participating) may want to switch off part of its network (e.g., cells / network entities / sites) at night during low traffic, and have its users instead use a network shared by other operators (e.g., hosting), including potentially degraded QoS. This temporary / dynamic network sharing for energy-efficiency purposes may be referred to as “green sharing.” Such network sharing agreements between operators, including leveraging “indirect network sharing” (i.e., assuming no direct connectivity between the shared RAN of the hosting operator and the core network of participating operators), may allow dynamic strategies such that two or more operators temporarily apply cell shutdown to obtain network energy savings, while one operator remains active in an area and provides services to the subscribers of all participating operators. This may also apply between non-public network (NPN) operators and / or with public land mobile network (PLMN) operators.

[0057] Predefined agreements currently control network sharing between operators that can configure their own networks via operations, administration, and management (0AM) (e.g., to broadcast another network ID and serve its subscribers). Assuming that operators have such predefined agreements in place, and interconnections exist between their networks to enable network sharing, there are no dynamic procedures allowing an operator to inform another operator to activate or deactivate such capabilities with time and space constraints.Thus, dynamic adaptation of user load & requirements and energy constraints (e.g., availability and pricing) is not feasible.

[0058] Certain example embodiments described herein may have various benefits and / or advantages to overcome the disadvantages described above. For example, certain example embodiments may conserve network resources of a single operator, thereby saving energy. Some example embodiments may also optimize energy usage of network resources of the target operator by hosting as many UEs as possible. In addition, various example embodiments may globally optimize energy consumption over an area throughout operators (e.g., for energy-constrained areas). Furthermore, some example embodiments may allow for improved dynamic / adaptive utilization of network sharing and user experience, and may define how a NE of one network may discover relevant NEs of another network (e.g., either directly or via a novel DyNS function) to achieve energy savings. Thus, certain example embodiments discussed below are directed to improvements in computer-related technology.

[0059] Various example embodiments discussed herein relate to a dynamic network sharing activation and release procedure between different operators. FIG. 1 illustrates a generic architecture of some example embodiments of such procedures to be executed either between network entities of different operators, or via a dynamic network sharing (DyNS) function. The decision to trigger dynamic network sharing may be performed by a network entity, or autonomously by the DyNS function. Some example embodiments may also trigger this request without knowledge of the other operator’s network entities (i.e., target NEs), while certain example embodiments may allow the DyNS to initiate this procedure with no prior involvement of network entities. The release of dynamic (i.e., temporary) network sharing may be initiated either by the source or the target network.

[0060] Various example embodiments described herein relating to network sharing release procedures (i.e., triggered either by source or target NEs) may also apply to example embodiments involving DyNS functions, in which source or target DyNS may be used (e.g., to transfer or initiate the network sharing release messages).

[0061] FIG. 2 illustrates an example of a signaling diagram depicting for triggering and issuing a network sharing activation request. Source NE 220 and target NE 230 may be similar to NE 1310, as illustrated in FIG. 13, according to certain example embodiments. Based on external conditions, source NE 220 may decide to trigger a network sharing activation request to target NE 230. The triggering condition may be based on source NE 220 detecting low usageon one or more of its cells, or poor energy efficiency (e.g., based on internal dynamic or predefined thresholds or algorithms, or based on predefined agreements or regulator request). The triggering condition may for example also be based on source NE 220 determining a low energy level or an equipment failure. In various example embodiments, the triggering condition may be a high load experienced on source NE 220, in order to temporarily offload some traffic to another operator based on commercial agreements. An incentive-based cooperation mechanism may be used to identify or validate the target network dynamically (e.g., on a round-robin basis between multiple network operators). An OAM-based mechanism may also be used, for example, based on a radio resource partitioning policies update. Communication of the operations described below between source NE 220 and target NE 230 may occur over an Xninterface.

[0062] At operation 201, source NE 220 may create one or more network sharing activation requests. Each such request may include one or more of at least one network ID to be broadcasted, at least an indication of a concerned geographical area and / or target cells / sectors, specific bands on which source NE 220 expects target NE 230 to serve users, current traffic load and characteristics e.g., QoS, number of active / idle users), minimum acceptable characteristics to be accepted by the target NE 230 (e.g. , allowing some quality of service (QoS) degradation), the expected end time of sharing by the source NE 220, and a minimum start time before target NE 230 actually begins broadcasting the network ID. Source NE 220 may determine whether any agreements exist that permit sending network sharing activation requests to target NE 230.

[0063] At operation 202, source NE 220 may transmit the one or more network sharing activation requests to target NE 230, which may have been previously known, for example, based upon a predefined 0AM configuration, historical data, and / or a dynamic procedure (e.g. , via measurements).

[0064] At operation 203, target NE 230 may identify source NE 220 as the requesting entity, and determine whether any agreements exist to authorize the one or more network sharing activation requests received from source NE 220.

[0065] At operation 204, upon target NE 230 authorizing the one or more network sharing activation requests, at operation 205, target NE 230 may transmit a network sharing activation acknowledgment, which may comprise target cell information, minimum guaranteed characteristics, supported traffic load, or at least one acknowledgement ID to serve as anidentifier for later release of this temporary sharing. Target NE 230 may transmit multiple ACK IDs to source NE 230 (e.g. , one per band, per cell or per received request). The network sharing activation acknowledgment may include alternative target cell information which may provide the same coverage and / or may include a new minimum start time and / or end time of sharing.

[0066] At operation 206, source NE 220 may store ACK IDs and related information received from target NE 230 at operation 204.

[0067] At operation 207, source NE 220 and / or target NE 230 may wait for a sharing start time.

[0068] At operation 208, target NE 230 may begin broadcasting the network ID(s) included in the one or more acknowledged network sharing activation requests.

[0069] At operation 209, in response to source NE 220 receiving the network sharing activation acknowledgment from target NE 230, source NE 220 may start triggering a handover procedure for its currently active UE(s) and / or a cell reselection procedure for inactive / idle UE(s) in its concerned cells towards cells of target NE 230 indicated in the network sharing activation acknowledgment.

[0070] In some example embodiments, if the network sharing activation acknowledgment transmitted at operation 205 is a partial acknowledgement (e.g., all traffic characteristics, target cells, and / or bands could not be satisfied), source NE 220 may explicitly select a subset of UEs to be handed over.

[0071] At operation 210, upon source NE 220 handing over the selected UEs to the target cells of target NE 230, source NE 220 shuts down / deactivates its concerned cells. Source NE 220 may also temporarily disconnect a backhaul link to save energy and costs (e.g., until the agreed end time of sharing). Source NE 220 may continue to broadcast another network ID, be connected with the core network of that network, and serve customers of that network via other cells. Source NE 220 may also maintain a coverage cell. Source NE 220 and target NE 230 may maintain in memory the network sharing activation request acknowledgement ID and the related information.

[0072] At operation 211, upon target NE 230 rejecting the one or more network sharing activation requests at operation 204, target NE 230 may transmit a network sharing activation rejection to source NE 220 indicating a cause (e.g., requested bands or minimumcharacteristics cannot be met), and may indicate a prohibit timer (e.g., request source NE 220 to not transmit future requests within a specific time or duration).

[0073] FIG. 3 illustrates an example of a signaling diagram for issuing a network sharing activation request by leveraging a dynamic network sharing (DyNS) function. Source DyNS function 310, target DyNS function 320, source NE 330, and target NE 340 may be similar to NE 1310, as illustrated in FIG. 13, according to certain example embodiments. Some example embodiments may be performed over an N2 interface.

[0074] In certain example embodiments, a dynamic network sharing (DyNS) function (e.g., source DyNS function 310, target DyNS function 320) may communicate with source NE 330 and target NE 340 in its own network, and with peer DyNS functions in other networks. The DyNS function may be embedded in the corresponding NE (e.g. , source NE 330 and target NE 340) in an existing control plane (CP) or operations, administration, and management (0AM) function, or as a new network function within the network. Multiple instances of DyNS may be present in each network.

[0075] For example, if target NE 230 at operation 202 is unreachable (e.g., unknown, lack of connectivity, did not respond to a previous network sharing activation request), source NE 220 may instead transmit this request to source DyNS function 310, providing the concerned geographical area and / or target NE 340. In this request, source NE 330 may include an indication as whether the request should be proxied by the DyNSs, or whether it would only serve at retrieving the list of target NE(s), before subsequent direct inter-NEs interactions as per FIG. 2.

[0076] In another embodiment, the source DyNS function can take the decision autonomously to initiate a “dynamic network sharing” request. This can be triggered, for example, after registering within the source network to monitor radio usage resources measurements at NEs (e.g. , via known 0AM procedures, NWDAF, etc.). Based on such measurements (e.g. , low-cell usage) and other information, as well as internal algorithms, the source DyNS may then decide to activate or deactivate network sharing.

[0077] At operation 301, source DyNS function 310 may identify a peer target DyNS function 320 using known procedures, and may forward a dynamic network sharing request. If not provided by source NE 330, or if decided autonomously, source DyNS function 310 may insert an indication of whether the request should be proxied by target DyNS function 320, or whether target DyNS function 320 would only provide the list of target NEs.

[0078] At operation 302, target DyNS function 320 may authenticate and authorize the requesting entity, and checks whether agreements exist to authorize the specific request.

[0079] At operation 303, if the dynamic network sharing request is authorized by target DyNS function 320, target DyNS function 320 may attempt to identify target serving NE(s) 340 for the provided geographical area.

[0080] If target DyNS function 320 identifies that target NE(s) 340 is(are) unavailable (e.g., for coverage, maintenance or load reasons), target DyNS function 320 may reject the dynamic network sharing request.

[0081] If the dynamic network sharing request includes an indication to only retrieve the list of target NE(s), target DyNS function 320 may transmit an acknowledgement of the request to source DyNS function 310 with the list of target NE(s) 340 identified, including information allowing source NE 330 to interact directly with those NEs for future requests.

[0082] If the dynamic network sharing request includes an indication to be proxied, target DyNS function 320 may forward the request to these target NE(s) 340.

[0083] At operation 304, target NE(s) 340 may acknowledge or reject the dynamic network sharing request, and forward this response to target DyNS function 320. A backhaul link between the source network and target NE 340 may also be dynamically reactivated.

[0084] At operation 305, target DyNS function 320 may consolidate the response(s) from the target NE(s) 340, and transmit the consolidated response(s) to source DyNS function 310.

[0085] At operation 306, source DyNS function 310 may transmit the information received at operation 305 to source NE 330 in order to enable source NE 330 either to reactivate its concerned source cells or to trigger HO / cell-reselection towards the target cells and deactivate the concerned source cells.

[0086] If source DyNS function 310 initiated the request, depending on whether the request intended to be proxied or not, the information sent to source NE 330 may or may not respectively include information allowing source NE 330 to interact directly with the target NE(s) 340 for future requests.

[0087] FIG. 4 illustrates an example of a signaling diagram for issuing a network sharing release request. Source NE 420 and target NE 430 may be similar to NE 1310, as illustrated in FIG. 13, according to certain example embodiments. Some example embodiments may be performed over an N2 interface.

[0088] Based on a later condition (e.g., increasing load on a “coverage” cell, end of predefined sharing period, etc.), source NE 420 may decide to reactivate one or more cells that were previously deactivated / shut down (e.g., for energy efficiency / saving reasons).

[0089] Similarly, target NE 430 may inform source NE 420 that it cannot share its network anymore on some cells (e.g., based on high load or after the expected end sharing time). In some example embodiments, source NE 420 may want to cancel / abort the request shortly after its initial request (e.g., in case it is not satisfied with the “partial acknowledgment”). This may be useful if source NE 420 has provided a minimum start time in its request and decides to cancel its request before the end of this period.

[0090] Some example embodiments may be performed using Xn and / or N2 interfaces.

[0091] At operation 401, as the releasing NE, source NE 420 and / or target NE 430 may retrieve from its memory associated information, such as a broadcasted network ID and cells, as well as a network sharing activation request acknowledge ID(s) provided by target NE 430 in the initial network sharing activation request acknowledgement.

[0092] At operation 402, releasing NE (i. e. , source NE 420 and / or target NE 430) may initiate a network sharing release request to the other network’s NE, including at least one ID. Optionally, some specific information related to target NE 430 (e.g., cell, band) may be added to perform a partial release request (e.g., only requesting to release the temporary network sharing over specific cells or bands, whilst keeping the remaining active).

[0093] At operation 403, when source NE 420 is the releasing NE, source NE 420 may include information about the source cells to be reactivated in the network sharing release request to target NE 430, and may provide a minimum start time before target NE 430 actually starts HO / cell reselection process. In response, target NE 430 may acknowledge or reject this request, including providing a cause and / or prohibit timer.

[0094] In case target NE 430 provides an acknowledgment, with this information, target NE 430 may wait for the requested start time. After this requested start time, target NE 430 may trigger an HO procedure and / or a cell reselection procedure towards the new cells under source NE 420. Once the UEs have been handed over or reselected to the new source cells, the target NE 430 may stop broadcasting the source network ID(s), and may perform other related actions to save energy (e.g., deactivating / shutting down resources that were previously allocated during temporary network sharing). Source NE 420 may reactivate its own concerned cells and starts broadcasting the related network ID(s).

[0095] In case of rejection of target NE 430, source NE 420 may or may not reactivate its own cells.

[0096] At operation 404, when target NE 430 is the releasing NE, target NE 420 may include information about the cells it doesn’t want to share anymore in a network sharing release request to source NE 420.

[0097] Source NE 420 may acknowledge or reject the request. For example, source NE 420 may provide new information (e.g., related to cells or bands) to be used with respect to the original network sharing activation request, as well as a minimum start time by when it would be ready to serve UEs. Alternatively, source NE 420 may reject this request with a cause informing target NE 430 that it will not be able to handle it (e.g., reactivate cells), and optionally a prohibit timer.

[0098] Source NE 420 may reactivate its own concerned cells, and may start to broadcast the related network ID.

[0099] In case of acknowledgment by source NE 420, using the updated source NE 420 information if provided, or otherwise the one associated to the initial network sharing activation request (e.g., cells, bands), target NE 430 may trigger an HO procedure and / or a cell reselection procedure towards those cells under source NE 420.

[0100] Once the UEs have been handed over or reselected to the new source cells, target NE 430 may stop broadcasting the source network ID(s), and may perform other related actions to save energy (e.g., deactivating / shutting down resources that were previously allocated during temporary network sharing).

[0101] In case of rejection by source NE 420, target NE 430 may or may not stop broadcasting the source network ID(s).

[0102] FIG. 5 illustrates an example of a signaling diagram for issuing a network sharing release request initiated by a source NE. Source NE 520 and target NE 530 may be similar to NE 1310, as illustrated in FIG. 13, according to certain example embodiments.

[0103] At operation 501, source NE 520 may retrieve at least one ACK ID and related information.

[0104] At operation 502, source NE 520 may transmit to target NE 530 at least one network sharing release request. The at least one network sharing release request may include any combination of ACK IDs, geographical areas / target cells pairs, bands, source cell / band pairs, and sharing-release start time.

[0105] At operation 503, target NE 530 may determine whether a dynamic network sharing agreement exists. If target NE 530 determines that no dynamic network sharing agreement exists, target NE 530 may perform operation 506. However, if target NE 530 determines that at least one dynamic network sharing agreement exists, target NE 530 may proceed to operation 504.

[0106] At operation 504, target NE 530 may determine whether at least one ACK ID is active. If target NE 520 determines that at least one ACK ID is not active, target NE 530 may perform operation 506. However, if target NE 530 determines that at least one ACK ID is active, target NE 530 may perform operation 505.

[0107] At operation 505, target NE 530 may determine whether the at least one network sharing release request is approved. If target NE 530 determines that the at least one network sharing release request is not approved, target NE 530 may proceed to operation 506. However, if target NE 530 determines that the at least one network sharing release request is approved, target NE 530 may proceed to operation 508.

[0108] At operation 506, target NE 530 may transmit at least one network sharing release rejection to source NE 520, which may indicate at least one cause and / or at least one prohibit timer.

[0109] At operation 507, source NE 520 may reactivate at least one source cell.

[0110] At operation 508, target NE 530 may transmit at least one network sharing release acknowledgement to source NE 520, which may indicate at least one target cell and / or band.

[0111] At operation 509, source NE 520 may reactivate at least one source cell.

[0112] At operation 510, target NE 530 may wait for a sharing-release start time.

[0113] At operation 511, target NE 530 may start HO / cell-reselection procedure on source cells / bands.

[0114] At operation 512, target NE 530 may stop broadcasting source network ID(s) on target cells / bands.

[0115] FIG. 6 illustrates an example of a signaling diagram for issuing a network sharing release request initiated by a target NE. Source NE 620 and target NE 630 may be similar to NE 1310, as illustrated in FIG. 13, according to certain example embodiments.

[0116] At 601, target NE 630 may retrieve at least one ACK ID and related information.

[0117] At 602, target NE 630 may transmit to source NE 620 at least one network sharing release request, which may include any combination of ACK IDs, geographical area / target cell pairs, and bands.

[0118] At operation 603, source NE 620 may determine whether a dynamic network sharing agreement exists. If source NE 620 determines that no dynamic network sharing agreement exists, source NE 620 may perform operation 611. However, if source NE 620 determines that at least one dynamic network sharing agreement exists, source NE 620 may proceed to operation 604.

[0119] At operation 604, source NE 620 may determine whether at least one ACK ID is active. If source NE 620 determines that at least one ACK ID is not active, source NE 620 may perform operation 611. However, if source NE 620 determines that at least one ACK ID is active, source NE 620 may perform operation 605.

[0120] At operation 605, source NE 620 may determine whether the at least one network sharing release request is approved. If source NE 620 determines that the at least one network sharing release request is not approved, source NE 620 may proceed to operation 611. However, if source NE 620 determines that the at least one network sharing release request is approved, source NE 620 may proceed to operation 606.

[0121] At operation 606, source NE 620 may transmit at least one network sharing release acknowledgement to target NE 630, which may indicate at least one target cell and / or band.

[0122] At operation 607, source NE 620 may reactivate at least one source cell.

[0123] At operation 608, target NE 630 may wait for a sharing-release start time.

[0124] At operation 609, target NE 630 may start HO / cell-reselection procedure on source cells / bands.

[0125] At operation 610, target NE 630 may stop broadcasting source network IDs on target cells / bands.

[0126] At operation 611, source NE 620 may transmit at least one network sharing release rejection to target NE 530, which may indicate at least one cause and / or at least one prohibit timer.

[0127] At operation 612, target NE 630 may stop broadcasting source network IDs on target cells / bands.

[0128] It may be understood that if sharing for any source NE 220 is limited to having no more than a single ongoing activation or outstanding (de)activation request at any given timewith any target NE 230, that any ACK ID may be omitted from the methods described herein, because it will be clear to both the source NE and target NE that any received response signaling (e.g., 205, 211, 506, 508, 606, 611) refers back to the preceding signal (e.g., 202, 502, 602), where any deactivation request (e.g., 502, 602) will then unequivocally refer to the sole ongoing activated sharing. In such cases, such a sole ongoing activated sharing may be modified by sending additional activation requests to add additional cells and / or bands as specified in the additional activation requests, or modified by sending deactivation requests specifying the deactivation of a subset of the cells and / or bands currently being shared as long as the NE waits for acknowledgement or rejection for a (de)activation request before sending a next (de)activation request.

[0129] FIG. 7 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments.

[0130] At step 701, the method may include transmitting towards at least one target network entity at least one network sharing activation request. In some example embodiments, the transmitting towards the at least one target network entity comprises one of transmitting to the at least one target network entity over an Xn interface, transmitting to a source network sharing function for forwarding to the at least one target network entity through a target network sharing function, or transmitting to a source network sharing function for forwarding to a target network sharing function to respond on behalf of the at least one target network entity.

[0131] At step 702, the method may include receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. In various example embodiments, the receiving from the at least one target network entity comprises receiving from the at least one target network entity over an Xn interface, receiving from the at least one target network entity through a source network sharing function and a target network sharing function, or receiving through a source network sharing function from target network sharing function responding on behalf of the at least one target network entity.

[0132] At step 703, the method may include, in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.

[0133] At step 704, the method may include, in response to the receiving the at least one network sharing activation acknowledgement, at least one of the following: storing at least one acknowledgement identifier, initiating a sharing start timer for the deactivating and / orstarting, starting at least one of handover or cell reselection procedures for user equipment associated with the at least one source cell. The at least one acknowledgement identifier may indicate in the at least one network sharing activation acknowledgement.

[0134] At step 705, the method may include transmitting the at least one network sharing activation request in response to determining the existence of a dynamic network sharing agreement with the target network.

[0135] At step 706, the method may include transmitting to a source dynamic network sharing function at least one request, and receiving from the source dynamic network sharing function at least one identifier of the at least one target network entity.

[0136] FIG. 8 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments.

[0137] At step 801, the method may include receiving from at least one source network entity at least one network sharing activation request. The receiving from the at least one target network entity may include receiving from the at least one target network entity over an Xn interface, receiving from the at least one target network entity through a source network sharing function and a target network sharing function, or receiving through a source network sharing function from target network sharing function responding on behalf of the at least one target network entity.

[0138] At step 802, the method may include determining whether the at least one network sharing activation request is approved.

[0139] At step 803, the method may include transmitting towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection. The transmitting towards the at least one target network entity may include one of transmitting to the at least one target network entity over an Xn interface, transmitting to a source network sharing function for forwarding to the at least one target network entity through a target network sharing function, or transmitting to a source network sharing function for forwarding to a target network sharing function to respond on behalf of the at least one target network entity.

[0140] At step 804, when the at least one network sharing activation request is approved, the method may include activating at least one target cell.

[0141] At step 805, the method may include determining whether the at least one network sharing activation request is approved based on a network sharing agreement with the source network.

[0142] At step 806, the method may include storing at least one acknowledgement identifier, and initiating a sharing start timer for the activating.

[0143] FIG. 9 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments.

[0144] At step 901, the method may include transmitting to at least one network entity at least one network sharing release request. The at least one network sharing release request may be indicative of at least one retrieved acknowledgement identifier. The transmitting towards the at least one source network entity may include at least one of transmitting to the at least one source network entity over an Xn interface, transmitting to a target network sharing function for forwarding to the at least one source network entity through a source network sharing function, or transmitting to a target network sharing function for forwarding to a source network sharing function to respond on behalf of the at least one source network entity.

[0145] At step 902, the method may include retrieving at least one acknowledgement identifier.

[0146] At step 903, the method may include receiving at least one network sharing release rejection from the at least one network entity comprising at least one indication of at least one cause or at least one prohibition timer. The receiving from the at least one source network entity may include receiving from the at least one source network entity over an Xn interface, receiving from the at least one source network entity through a target network sharing function and a source network sharing function, or receiving through a target network sharing function from source network sharing function responding on behalf of the at least one source network entity.

[0147] At step 904, the method may include receiving at least one network sharing release acknowledgement from the at least one network entity comprising at least one target cell or band.

[0148] The apparatus may be, or may be comprised in, a target network entity, the method may include initiating a sharing release timer for the deactivating and / or starting, starting handover and / or cell reselection procedures for user equipment associated with at least one cell associatedwith the acknowledgement, or deactivating at least one cell associated with the acknowledgement.

[0149] The apparatus may be, or may be comprised in, a source network entity, and the network entity may be a target network entity, and, in response to the receiving, the method may include reactivating at least one source cell.

[0150] The receive from the network entity may include receiving from the network entity over an Xn interface, receiving from the network entity through a network sharing function in a network of the apparatus and a network sharing function in a network of the network entity, or receiving through a network sharing function in a network of the apparatus from a network sharing function in a network of the network entity responding on behalf of the network entity.

[0151] The transmitting towards the network entity may include at least one of transmitting to the network entity over an Xn interface, transmitting to a network sharing function in a network of the apparatus for forwarding to the network entity through a network sharing function in a network of the network entity, or transmitting to a network sharing function in a network of the apparatus for forwarding to the network sharing function in a network of the network entity to respond on behalf of the network entity.

[0152] FIG. 10 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments.

[0153] At step 1001, the method may include receiving from at least one network entity at least one network sharing release request.

[0154] At step 1002, the method may further include determining whether the at least one network sharing release request is approved.

[0155] In some example embodiments, the at least one network sharing release request may include at least one acknowledgement identifier, and the method may include determining whether the at least one network sharing release request is approved comprises determining whether the at least one acknowledgment identifier is active.

[0156] At step 1003, the method may further include determining whether a dynamic network sharing agreement exists.

[0157] At step 1004, the method may further include transmitting at least one network sharing release rejection to the network entity comprising at least one indication of at least one cause or at least one prohibition timer.

[0158] At step 1005, the method may further include transmitting at least one network sharing release acknowledgement to the network entity.

[0159] In various example embodiments, the apparatus may be, or may be comprised in, a target network entity, and the network entity may be a source network entity, and the method may further include initiating a sharing release timer for the deactivating and / or starting, starting handover and / or cell reselection procedures for user equipment associated with at least one cell associated with the acknowledgement, or deactivating at least one cell associated with the acknowledgement.

[0160] In certain example embodiments, the apparatus may be, or may be comprised in, a source network entity, and the network entity may be a target network entity, and the method may further include, in response to the transmitting, reactivate at least one source cell.

[0161] In some example embodiments, the transmitting towards the network entity may include at least one of transmitting to the network entity over an Xn interface, transmitting to a network sharing function in a network of the apparatus for forwarding to the network entity through a network sharing function in a network of the network entity, or transmitting to a network sharing function in a network of the apparatus for forwarding to the network sharing function in a network of the network entity to respond on behalf of the network entity.

[0162] In certain example embodiments, the receiving from the network entity may include receiving from the network entity over an Xn interface, receiving from the network entity through a network sharing function in a network of the apparatus and a network sharing function in a network of the network entity, and receiving through a network sharing function in a network of the apparatus from a network sharing function in a network of the network entity responding on behalf of the network entity.

[0163] FIG. 11 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments.

[0164] At step 1101, the method may include authenticating and authorizing a source network function.

[0165] At step 1102, the method may further include receiving a dynamic network sharing request from or through the source network function.

[0166] At step 1103, the method may further include attempt to identify at least one target network entity for a provided geographical area; and at least one of if no target network entity is identified for the provided geographical area, transmit a dynamic network sharingrejection towards the source network function, transmit identification of at least one identified target network entity towards the source network function, or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

[0167] At step 1104, the method may further include consolidating information received in at least one dynamic network sharing acknowledgement and / or dynamic network sharing rejection received from the at least one identified target network entity, wherein the information received in response to the transmitting the at least a portion of the dynamic network sharing request to the at least one identified target network entity, and transmitting the consolidated information towards the source network function, wherein the consolidated information is configured to enable a source network entity to at least one of: deactivate or reactivate at least one predetermined source cell or trigger handover towards a target cell.

[0168] FIG. 12 illustrates an example of a flow diagram of a method that may be performed by a NE, such as NE 1310 illustrated in FIG. 13, according to various example embodiments.

[0169] At step 1201, the method may include receiving a dynamic network sharing request from a source network entity.

[0170] At step 1202, the method may further include attempt to identify at least one target network sharing function, and at least one of if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity, identifying a geographical area associated with the dynamic network sharing request, or transmitting the dynamic network sharing request to the identified target network sharing function.

[0171] At step 1203, the method may further include, in response to transmitting the dynamic network sharing request to the identified target network sharing function, receiving at least one of a dynamic network sharing rejection or a dynamic network sharing acknowledgement or a list of target network entities from the identified target network sharing function, and transmitting at least a portion of the received dynamic network sharing rejection or the dynamic network sharing acknowledgement or the list of target network entities to the source network entity.

[0172] In certain example embodiments, the identification of the target network sharing function based on the identified geographical area, and / or the transmitted dynamic network sharing request is indicative of the identified geographical area.

[0173] FIG. 13 illustrates an example of a system according to certain example embodiments. In one example embodiment, a system may include multiple devices, such as, for example, NE1310 and / or UE 1320.

[0174] NE 1310 may be one or more of a base station (e.g., 3G UMTS NodeB, 4G LTE Evolved NodeB, or 5G NR Next Generation NodeB), a serving gateway, a server, and / or any other access node or combination thereof.

[0175] NE 1310 may further include at least one gNB -centralized unit (CU), which may be associated with at least one gNB -distributed unit (DU). The at least one gNB-CU and the at least one gNB-DU may be in communication via at least one Fl interface, at least one Xn-C interface, and / or at least one NG interface via a 5thgeneration core (5GC).

[0176] UE 1320 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA), tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof. Furthermore, NE 1310 and / or UE 1320 may be one or more of a citizens broadband radio service device (CBSD).

[0177] NE 1310 and / or UE 1320 may include at least one processor, respectively indicated as1311 and 1321. Processors 1311 and 1321 may be embodied by any computational or data processing device, such as a central processing unit (CPU), application specific integrated circuit (ASIC), or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

[0178] At least one memory may be provided in one or more of the devices, as indicated at1312 and 1322. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein. Memories 1312 and 1322 may independently be any suitable storage device, such as a non-transitory computer-readable medium. The term “non-transitory,” as used herein, may correspond to a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory (RAM) vs. read-only memory (ROM)). A hard disk drive (HDD), random access memory (RAM), flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory, and which may be processed by the processors, may beany suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language.

[0179] Processors 1311 and 1321, memories 1312 and 1322, and any subset thereof, may be configured to provide means corresponding to the various blocks of FIGs. 1-12. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted, and may be configured to determine location, elevation, velocity, orientation, and so forth, such as barometers, compasses, and the like.

[0180] As shown in FIG. 13, transceivers 1313 and 1323 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 1314 and 1324. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple RATs. Other configurations of these devices, for example, may be provided. Transceivers 1313 and 1323 may be a transmitter, a receiver, both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

[0181] The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus, such as UE, to perform any of the processes described above (i.e., FIGs. 1-12). Therefore, in certain example embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain example embodiments may be performed entirely in hardware.

[0182] In certain example embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGs. 1-12. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry), (b) combinations of hardware circuits and software, such as (as applicable):(i) a combination of analog and / or digital hardware circuit(s) with software / firmware and(ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions), and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requiressoftware (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0183] FIG. 14 illustrates an example of a 5G network and system architecture according to certain example embodiments. Shown are multiple network functions that may be implemented as software operating as part of a network device or dedicated hardware, as a network device itself or dedicated hardware, or as a virtual function operating as a network device or dedicated hardware. The NE and UE illustrated in FIG. 14 may be similar to NE 1310 and UE 1320, respectively. The user plane function (UPF) may provide services such as intra-RAT and inter- RAT mobility, routing and forwarding of data packets, inspection of packets, user plane quality of service (QoS) processing, buffering of downlink packets, and / or triggering of downlink data notifications. The application function (AF) may primarily interface with the core network to facilitate application usage of traffic routing and interact with the policy framework.

[0184] According to certain example embodiments, processors 1311 and 1321, and memories 1312 and 1322, may be included in or may form a part of processing circuitry or control circuitry. In addition, in some example embodiments, transceivers 1313 and 1323 may be included in or may form a part of transceiving circuitry.

[0185] In some example embodiments, an apparatus (e.g., NE 1310 and / or UE 1320) may include means for performing a method, a process, or any of the variants discussed herein. Examples of the means may include one or more processors, memory, controllers, transmitters, receivers, and / or computer program code for causing the performance of the operations.

[0186] The features, structures, or characteristics of example embodiments described throughout this specification may be combined in any suitable manner in one or more example embodiments. For example, the usage of the phrases “various embodiments,” “certain embodiments,” “some embodiments,” or other similar language throughout this specificationrefers to the fact that a particular feature, structure, or characteristic described in connection with an example embodiment may be included in at least one example embodiment. Thus, appearances of the phrases “in various embodiments,” “in certain embodiments,” “in some embodiments,” or other similar language throughout this specification does not necessarily all refer to the same group of example embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more example embodiments.

[0187] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or,” mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0188] Additionally, if desired, the different functions or procedures discussed above may be performed in a different order and / or concurrently with each other. Furthermore, if desired, one or more of the described functions or procedures may be optional or may be combined. As such, the description above should be considered as illustrative of the principles and teachings of certain example embodiments, and not in limitation thereof.

[0189] One having ordinary skill in the art will readily understand that the example embodiments discussed above may be practiced with procedures in a different order, and / or with hardware elements in configurations which are different than those which are disclosed.Therefore, although some embodiments have been described based upon these example embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the example embodiments.

[0190] Partial Glossary

[0191] 3GPP 3rdGeneration Partnership Project

[0192] 5G 5thGeneration

[0193] 5GC 5thGeneration Core

[0194] 6G 6thGeneration

[0195] AF Application Function

[0196] ASIC Application Specific Integrated Circuit

[0197] CBSD Citizens Broadband Radio Service Device

[0198] CP Control Plane

[0199] CPU Central Processing Unit

[0200] CU Centralized Unit

[0201] DU Distributed Unit

[0202] DyNS Dynamic Network Sharing

[0203] EE Energy Efficiency

[0204] eMBB Enhanced Mobile Broadband

[0205] eNB Evolved Node B

[0206] gNB Next Generation Node B

[0207] GPS Global Positioning System

[0208] HDD Hard Disk Drive

[0209] HO Handover

[0210] ID Identifier

[0211] loT Internet of Things

[0212] LTE Long-Term Evolution

[0213] LTE-A Long-Term Evolution Advanced

[0214] MEMS Micro Electrical Mechanical System

[0215] MIMO Multiple Input Multiple Output

[0216] mMTC Massive Machine Type Communication

[0217] NE Network Entity

[0218] NG Next Generation

[0219] NG-eNB Next Generation Evolved Node B

[0220] NG-RAN Next Generation Radio Access Network

[0221] NPN Non-Public Network

[0222] NR New Radio

[0223] NWDAF Network Data Analytics Function

[0224] OAM Operations, Administration, and Management

[0225] PDA Personal Digital Assistance

[0226] PLMN Public Land Mobile Network

[0227] QoS Quality of Service

[0228] RAM Random Access Memory

[0229] RAN Radio Access Network

[0230] RAT Radio Access Technology

[0231] RF Radio Frequency

[0232] ROM Read-Only Memory

[0233] UE User Equipment

[0234] UMTS Universal Mobile Telecommunications System

[0235] UPF User Plane Function

[0236] URLLC Ultra-Reliable and Low-Latency Communication

[0237] UTRAN Universal Mobile Telecommunications System Terrestrial RadioAccess Network

Claims

WE CLAIM:

1. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: transmit towards at least one target network entity at least one network sharing activation request; receive from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection; and in response to the receiving the at least one network sharing activation acknowledgement, deactivate at least one source cell.

2. The apparatus of claim 1, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: in response to the receiving the at least one network sharing activation acknowledgement, at least one of the following: store at least one acknowledgement identifier; initiate a sharing start timer for the deactivating and / or starting; start at least one of handover or cell reselection procedures for user equipment associated with the at least one source cell.

3. The apparatus of claim 2, wherein the at least one acknowledgement identifier is indicated in the at least one network sharing activation acknowledgement.

4. The apparatus of any of claims 1-3, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: transmit the at least one network sharing activation request in response to determining the existence of a dynamic network sharing agreement with the target network.

5. The apparatus of any of claims 1-4, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to:transmit to a source dynamic network sharing function at least one request; and receive from the source dynamic network sharing function at least one identifier of the at least one target network entity.

6. The apparatus of any of claims 1-4, wherein the transmitting towards the at least one target network entity comprises at least one of: transmitting to the at least one target network entity over an Xn interface; transmitting to a source network sharing function for forwarding to the at least one target network entity through a target network sharing function; or transmitting to a source network sharing function for forwarding to a target network sharing function to respond on behalf of the at least one target network entity; and wherein the receiving from the at least one target network entity comprises at least one of: receiving from the at least one target network entity over an Xn interface; receiving from the at least one target network entity through a source network sharing function and a target network sharing function; or receiving through a source network sharing function from target network sharing function responding on behalf of the at least one target network entity.

7. An apparatus comprising at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive from at least one source network entity at least one network sharing activation request; determine whether the at least one network sharing activation request is approved; transmit towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection; and when the at least one network sharing activation request is approved, activate at least one target cell.

8. The apparatus of claim 7, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: determine whether the at least one network sharing activation request is approved based on a network sharing agreement with the source network.

9. The apparatus of claim 7 or 8, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus, when the at least one network sharing activation request is approved, at least to: store at least one acknowledgement identifier; and initiate a sharing start timer for the activating.

10. The apparatus of any of claims 7-9, wherein the transmitting towards the at least one source network entity comprises one of: transmitting to the at least one source network entity over an Xn interface; transmitting to a target network sharing function for forwarding to the at least one source network entity through a source network sharing function; or transmitting to a target network sharing function for forwarding to a source network sharing function to respond on behalf of the at least one source network entity; and wherein the receiving from the at least one source network entity comprises: receiving from the at least one source network entity over an Xn interface; receiving from the at least one source network entity through a target network sharing function and a source network sharing function; or receiving through a target network sharing function from source network sharing function responding on behalf of the at least one source network entity.

11. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: transmit to at least one network entity at least one network sharing release request.

12. The apparatus of claim 11 , wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: retrieve at least one acknowledgement identifier.

13. The apparatus of claim 12, wherein the at least one network sharing release request is indicative of at least one retrieved acknowledgement identifier.

14. The apparatus of any of claims 11-13, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: receive at least one network sharing release rejection from the at least one network entity comprising at least one indication of at least one cause or at least one prohibition timer.

15. The apparatus of any of claims 11-13, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: receive at least one network sharing release acknowledgement from the at least one network entity comprising at least one target cell or band.

16. The apparatus of claim 15, wherein the apparatus is, or is comprised in, a target network entity, and the at least one network entity is a source network entity, and wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to at least one of: initiate a sharing release timer for the deactivating and / or starting; start handover and / or cell reselection procedures for user equipment associated with at least one cell associated with the acknowledgement; or deactivate at least one cell associated with the acknowledgement.

17. The apparatus of claim 15, wherein the apparatus is, or is comprised in, a source network entity, and the network entity is a target network entity, and wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to at least one of: in response to the receiving, reactivate at least one source cell.

18. The apparatus of any of claims 15-17, wherein the receiving from the network entity comprises: receiving from the network entity over an Xn interface; receiving from the network entity through a network sharing function in a network of the apparatus and a network sharing function in a network of the network entity; or receiving through a network sharing function in a network of the apparatus from a network sharing function in a network of the network entity responding on behalf of the network entity.

19. The apparatus of any of claims 11-18, wherein the transmitting towards the network entity comprises one of: transmitting to the network entity over an Xn interface; transmitting to a network sharing function in a network of the apparatus for forwarding to the network entity through a network sharing function in a network of the network entity; or transmitting to a network sharing function in a network of the apparatus for forwarding to the network sharing function in a network of the network entity to respond on behalf of the network entity.

20. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive from at least one network entity at least one network sharing release request; and determine whether the at least one network sharing release request is approved.

21. The apparatus of claim 20, wherein the at least one network sharing release request comprises at least one acknowledgement identifier; and determining whether the at least one network sharing release request is approved comprises determining whether the at least one acknowledgment identifier is active.

22. The apparatus of claim 20 or 21, wherein the at least one memory and theinstructions, when executed by the at least one processor, further cause the apparatus at least to: determine whether a dynamic network sharing agreement exists.

23. The apparatus of any of claims 20-22, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: transmit at least one network sharing release rejection to the network entity comprising at least one indication of at least one cause or at least one prohibition timer.

24. The apparatus of any of claims 20-22, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: transmit at least one network sharing release acknowledgement to the network entity.

25. The apparatus of claim 24, wherein the apparatus is, or is comprised in, a target network entity, and the network entity is a source network entity, and wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus to at least one of: initiate a sharing release timer for the deactivating and / or starting; start handover and / or cell reselection procedures for user equipment associated with at least one cell associated with the acknowledgement; or deactivate at least one cell associated with the acknowledgement.

26. The apparatus of claim 24, wherein the apparatus is, or is comprised in, a source network entity, and the network entity is a target network entity, and wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: in response to the transmitting, reactivate at least one source cell.

27. The apparatus of any of claims 23-26, wherein the transmitting towards the network entity comprises one of: transmitting to the network entity over an Xn interface; transmitting to a network sharing function in a network of the apparatus for forwarding to the network entity through a network sharing function in a network of the network entity; ortransmitting to a network sharing function in a network of the apparatus for forwarding to the network sharing function in a network of the network entity to respond on behalf of the network entity.

28. The apparatus of any of claims 20-27, wherein the receiving from the network entity comprises: receiving from the network entity over an Xn interface; receiving from the network entity through a network sharing function in a network of the apparatus and a network sharing function in a network of the network entity; or receiving through a network sharing function in a network of the apparatus from a network sharing function in a network of the network entity responding on behalf of the network entity.

29. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: authenticate and authorize a source network function; receive a dynamic network sharing request from or through the source network function; attempt to identify at least one target network entity for a provided geographical area; and at least one of the following: if no target network entity is identified for the provided geographical area, transmit a dynamic network sharing rejection towards the source network function; transmit identification of at least one identified target network entity towards the source network function; or transmit at least a portion of the dynamic network sharing request to at least one identified target network entity.

30. The apparatus of claim 29, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: consolidate information received in at least one dynamic network sharingacknowledgement and / or dynamic network sharing rejection received from the at least one identified target network entity, wherein the information received in response to the transmitting the at least a portion of the dynamic network sharing request to the at least one identified target network entity; and transmit the consolidated information towards the source network function, wherein the consolidated information is configured to enable a source network entity to at least one of: deactivate or reactivate at least one predetermined source cell or trigger handover towards a target cell.

31. An apparatus comprising: at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to: receive a dynamic network sharing request from a source network entity; attempt to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmit at least one dynamic network sharing rejection towards the source network entity; identify a geographical area associated with the dynamic network sharing request; or transmit the dynamic network sharing request to the identified target network sharing function.

32. The apparatus of claim 31, wherein the identification of the target network sharing function is based on the identified geographical area.

33. The apparatus of claim 31 or 32, wherein the transmitted dynamic network sharing request is indicative of the identified geographical area.

34. The apparatus of claim 31-33, wherein the at least one memory and the instructions, when executed by the at least one processor, further cause the apparatus at least to: in response to transmitting the dynamic network sharing request to the identified target network sharing function:receive at least one of a dynamic network sharing rejection or a dynamic network sharing acknowledgement or a list of target network entities from the identified target network sharing function; transmit at least a portion of the received dynamic network sharing rejection or the dynamic network sharing acknowledgement or the list of target network entities to the source network entity.

35. A method comprising: transmitting towards at least one target network entity at least one network sharing activation request; receiving from the at least one target network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection; and in response to the receiving the at least one network sharing activation acknowledgement, deactivating at least one source cell.

36. The method of claim 35, further comprising: in response to the receiving the at least one network sharing activation acknowledgement, at least one of the following: storing at least one acknowledgement identifier; initiating a sharing start timer for the deactivating and / or starting; and starting at least one of handover or cell reselection procedures for user equipment associated with the at least one source cell.

37. The method of claim 35, wherein the at least one acknowledgement identifier is indicated in the at least one network sharing activation acknowledgement.

38. The method of any of claims 35-37, further comprising: transmitting the at least one network sharing activation request in response to determining the existence of a dynamic network sharing agreement with the target network.

39. The method of any of claims 35-38, further comprising: transmitting to a source dynamic network sharing function at least one request; andreceiving from the source dynamic network sharing function at least one identifier of the at least one target network entity.

40. The method of any of claims 35-39, wherein the transmitting towards the at least one target network entity comprises at least one of: transmitting to the at least one target network entity over an Xn interface; transmitting to a source network sharing function for forwarding to the at least one target network entity through a target network sharing function; or transmitting to a source network sharing function for forwarding to a target network sharing function to respond on behalf of the at least one target network entity; and wherein the receiving from the at least one target network entity comprises at least one of: receiving from the at least one target network entity over an Xn interface; receiving from the at least one target network entity through a source network sharing function and a target network sharing function; or receiving through a source network sharing function from target network sharing function responding on behalf of the at least one target network entity.

41. A method comprising : receiving from at least one source network entity at least one network sharing activation request; determining whether the at least one network sharing activation request is approved; transmitting towards the at least one source network entity at least one network sharing activation acknowledgement or at least one network sharing activation rejection; and when the at least one network sharing activation request is approved, activating at least one target cell.

42. The method of claim 41 , further comprising: determining whether the at least one network sharing activation request is approved based on a network sharing agreement with the source network.

43. The method of claim 41 or 42, further comprising, when the at least one network sharing activation request is approved: storing at least one acknowledgement identifier; and initiating a sharing start timer for the activating.

44. The apparatus of any of claims 41-43, wherein the transmitting towards the at least one source network entity comprises one of: transmitting to the at least one source network entity over an Xn interface; transmitting to a target network sharing function for forwarding to the at least one source network entity through a source network sharing function; or transmitting to a target network sharing function for forwarding to a source network sharing function to respond on behalf of the at least one source network entity; and wherein the receiving from the at least one source network entity comprises: receiving from the at least one source network entity over an Xn interface; receiving from the at least one source network entity through a target network sharing function and a source network sharing function; or receiving through a target network sharing function from source network sharing function responding on behalf of the at least one source network entity.

45. A method comprising: transmitting to at least one network entity at least one network sharing release request.

46. The method of claim 45, further comprising: retrieving at least one acknowledgement identifier.

47. The method of claim 45, wherein the at least one network sharing release request is indicative of at least one retrieved acknowledgement identifier.

48. The method of any of claims 45-47, further comprising: receiving at least one network sharing release rejection from the at least one network entity comprising at least one indication of at least one cause or at least one prohibition timer.

49. The method of any of claims 45-48, further comprising: receiving at least one network sharing release acknowledgement from the at least one network entity comprising at least one target cell or band.

50. The method of claim 49, wherein the method is performed by a target network entity, and the at least one network entity is a source network entity, further comprising at least one of: initiating a sharing release timer for the deactivating and / or starting; starting handover and / or cell reselection procedures for user equipment associated with at least one cell associated with the acknowledgement; or deactivating at least one cell associated with the acknowledgement.

51. The method of claim 50, wherein the method is performed by a source network entity, and the network entity is a target network entity, further comprising at least one of: in response to the receiving, reactivating at least one source cell.

52. The method of any of claims 45-51, wherein the receiving from the network entity comprises: receiving from the network entity over an Xn interface; receiving from the network entity through a network sharing function in a network of the apparatus and a network sharing function in a network of the network entity; or receiving through a network sharing function in a network of the apparatus from a network sharing function in a network of the network entity responding on behalf of the network entity.

53. The method of any of claims 45-52, wherein the transmitting towards the network entity comprises one of: transmitting to the network entity over an Xn interface; transmitting to a network sharing function in a network of the apparatus for forwarding to the network entity through a network sharing function in a network of the network entity; or transmitting to a network sharing function in a network of the apparatus for forwardingto the network sharing function in a network of the network entity to respond on behalf of the network entity.

54. A method comprising: receiving from at least one network entity at least one network sharing release request; and determining whether the at least one network sharing release request is approved.

55. The method of claim 54, wherein the at least one network sharing release request comprises at least one acknowledgement identifier; and further comprising: determining whether the at least one network sharing release request is approved comprises determining whether the at least one acknowledgment identifier is active.

56. The method of claim 54 or 55, further comprising: determining whether a dynamic network sharing agreement exists.

57. The method of any of claims 54-56, further comprising: transmitting at least one network sharing release rejection to the network entity comprising at least one indication of at least one cause or at least one prohibition timer.

58. The method of any of claims 54-57, further comprising: transmitting at least one network sharing release acknowledgement to the network entity.

59. The method of claim 58, wherein the method is performed by a target network entity, and the network entity is a source network entity, and further comprising at least one of: initiating a sharing release timer for the deactivating and / or starting; starting handover and / or cell reselection procedures for user equipment associated with at least one cell associated with the acknowledgement; or deactivating at least one cell associated with the acknowledgement.

60. The method of claim 59, wherein the method is performed by a source networkentity, and the network entity is a target network entity, and further comprising: in response to the transmitting, reactivating at least one source cell.

61. The method of any of claims 54-60, wherein the transmitting towards the network entity comprises one of: transmitting to the network entity over an Xn interface; transmitting to a network sharing function in a network of the apparatus for forwarding to the network entity through a network sharing function in a network of the network entity; or transmitting to a network sharing function in a network of the apparatus for forwarding to the network sharing function in a network of the network entity to respond on behalf of the network entity.

62. The method of any of claims 54-61, wherein the receiving from the network entity comprises: receiving from the network entity over an Xn interface; receiving from the network entity through a network sharing function in a network of the apparatus and a network sharing function in a network of the network entity; or receiving through a network sharing function in a network of the apparatus from a network sharing function in a network of the network entity responding on behalf of the network entity.

63. A method comprising: authenticating and authorizing a source network function; receiving a dynamic network sharing request from or through the source network function; attempting to identify at least one target network entity for a provided geographical area; and at least one of the following: if no target network entity is identified for the provided geographical area, transmitting a dynamic network sharing rejection towards the source network function; transmitting identification of at least one identified target network entity towards the source network function; ortransmitting at least a portion of the dynamic network sharing request to at least one identified target network entity.

64. The method of claim 63, further comprising: consolidating information received in at least one dynamic network sharing acknowledgement and / or dynamic network sharing rejection received from the at least one identified target network entity, wherein the information received in response to the transmitting the at least a portion of the dynamic network sharing request to the at least one identified target network entity; and transmitting the consolidated information towards the source network function, wherein the consolidated information is configured to enable a source network entity to at least one of: deactivate or reactivate at least one predetermined source cell or trigger handover towards a target cell.

65. A method comprising: receiving a dynamic network sharing request from a source network entity; attempting to identify at least one target network sharing function, and at least one of the following: if no target network sharing function is identified within a geographical area, transmitting at least one dynamic network sharing rejection towards the source network entity; identifying a geographical area associated with the dynamic network sharing request; or transmitting the dynamic network sharing request to the identified target network sharing function.

66. The method of claim 65, wherein the identification of the target network sharing function is based on the identified geographical area.

67. The method of claim 65 or 66, wherein the transmitted dynamic network sharing request is indicative of the identified geographical area.

68. The method of any of claims 65-67, further comprising:in response to transmitting the dynamic network sharing request to the identified target network sharing function: receiving at least one of a dynamic network sharing rejection or a dynamic network sharing acknowledgement or a list of target network entities from the identified target network sharing function; and transmitting at least a portion of the received dynamic network sharing rejection or the dynamic network sharing acknowledgement or the list of target network entities to the source network entity.

69. A non-transitory computer readable medium comprising program instructions that, when executed by an apparatus, cause the apparatus to perform at least a method according to any of claims 35-68.

70. An apparatus comprising means configured to perform a method according to any of claims 35-68.

71. A computer program comprising instructions, which, when executed by an apparatus, cause the apparatus to perform the method of any of claims 35-68.

Citation Information

Patent Citations

  • Flexible network sharing

    WO2013170045A2

  • Method and electronic device for providing tethering service

    WO2017131441A1

Cited By

  • Energy consumption determination method, electronic equipment, storage medium and program product

    CN119789121A

  • Energy consumption determination method, and electronic device, storage medium and program product

    WO2026114431A1

  • Energy efficiency determination method, electronic device, storage medium, and program product

    WO2026130236A1

  • Method and device for supporting execution of network sharing in mobile communication system

    WO2026160939A1