Apparatus, method and computer program

Abstract

The present disclosure relates to apparatuses, methods and computer programs. A user equipment comprising at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the user equipment to at least perform: receiving, from a first network, a configuration related to performance measurements for candidate networks for network sharing with the first network; detecting, while being served by the first network, a node of at least one other network; measuring, based on the configuration, the at least one other network; and reporting, to the first network, at least one performance measurement of the at least one other network.

Description

Technical Field

[0001] Various embodiments of this disclosure generally relate to apparatuses, methods, and computer programs, and more specifically, but not exclusively, to apparatuses, methods, and computer programs for network sharing. Background Technology

[0002] A communication network can be viewed as a facility that enables communication between two or more communication devices or provides communication devices with access to a data network. Mobile or wireless communication networks are an example of communication networks. Communication devices may be served by application servers.

[0003] This type of communication network operates according to standards provided by organizations such as 3GPP (3rd Generation Partnership Project) or ETSI (European Telecommunications Standards Institute). Examples of these standards include the so-called 5G (5th generation) and 6G (6th generation) standards published by 3GPP. Summary of the Invention

[0004] Some embodiments of this disclosure will be described with reference to certain aspects. These aspects are neither intended to indicate key or essential features of the embodiments of this disclosure, nor are they intended to limit its scope. Other features, aspects, and elements will readily become apparent to those skilled in the art in light of this disclosure.

[0005] According to a first aspect, a user equipment is provided, including at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to at least: receive from a first network a configuration related to performance measurements of candidate networks for network sharing with the first network; detect nodes of at least one other network when served by the first network; measure at least one other network based on the configuration; and report at least one performance measurement of the at least one other network to the first network.

[0006] According to a second aspect, a method performed by a user equipment is provided, the method comprising: receiving from a first network a configuration related to performance measurements of candidate networks for network sharing with the first network; detecting nodes of at least one other network while being served by the first network; measuring at least one other network based on the configuration; and reporting at least one performance measurement of the at least one other network to the first network.

[0007] According to a third aspect, a computer program product is provided for: receiving from a first network a configuration related to performance measurements of candidate networks for network sharing with the first network; detecting nodes of at least one other network when served by the first network; measuring at least one other network based on the configuration; and reporting at least one performance measurement of the at least one other network to the first network.

[0008] According to a fourth aspect, a computer program product is provided, embodied on a computer-readable distributed medium and including program instructions that, when loaded into a device, execute a method comprising: receiving from a first network a configuration relating to performance measurements of candidate networks for network sharing with the first network; detecting nodes of at least one other network while being served by the first network; measuring the at least one other network based on the configuration; and reporting at least one performance measurement of the at least one other network to the first network.

[0009] According to a fifth aspect, an apparatus is provided, comprising components for performing: receiving from a first network a configuration relating to performance measurements of candidate networks for network sharing with the first network; detecting nodes of at least one other network while being served by the first network; measuring at least one other network based on the configuration; and reporting at least one performance measurement of the at least one other network to the first network.

[0010] According to a sixth aspect, an apparatus for a first network is provided, the apparatus comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: receive network sharing information, the network sharing information including at least one of: an instruction from a second network indicating that the second network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieve a network sharing policy from network functions; and create a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0011] According to a seventh aspect, a method is provided, comprising: receiving network sharing information, the network sharing information including at least one of the following: an indication from a second network indicating that the second network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieving a network sharing policy from network functions; and creating a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0012] According to an eighth aspect, a computer program product is provided for: receiving network sharing information, the network sharing information including at least one of the following: an instruction from a second network indicating that the second network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieving a network sharing policy from network functions; and creating a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0013] According to a ninth aspect, a computer program product is provided, embodied on a computer-readable distributed medium and including program instructions that, when loaded into a device, execute a method comprising: receiving network sharing information, the network sharing information including at least one of: an indication from a second network indicating that the second network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieving a network sharing policy from network functions; and creating a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0014] According to a tenth aspect, an apparatus is provided, comprising components for performing: receiving network sharing information, the network sharing information including at least one of: an indication from a second network indicating that the second network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieving a network sharing policy from network functions; and creating a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0015] According to an eleventh aspect, an apparatus for a first network is provided, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: receive network sharing information, the network sharing information including at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and based on the sharing information, create a network sharing policy for the first network and at least one other network.

[0016] According to the twelfth aspect, a method is provided, comprising: receiving network sharing information, the network sharing information including at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and creating a network sharing policy for the first network and at least one other network based on the sharing information.

[0017] According to a thirteenth aspect, a computer program product is provided for: receiving network sharing information, the network sharing information including at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and creating a network sharing policy for the first network and at least one other network based on the sharing information.

[0018] According to a fourteenth aspect, a computer program product is provided, embodied on a computer-readable distributed medium and including program instructions that, when loaded into a device, execute a method comprising: receiving network sharing information, the network sharing information including at least one of: an indication from at least one other network indicating that at least one other network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and creating a network sharing policy for the first network and at least one other network based on the sharing information.

[0019] According to the fifteenth aspect, an apparatus is provided, comprising components for performing: receiving network sharing information, the network sharing information including at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and creating a network sharing policy for the first network and at least one other network based on the sharing information.

[0020] According to a sixteenth aspect, an apparatus for a second network is provided, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: send an instruction to a network node of a first network indicating that the second network has capacity for network sharing with the first network; and receive from a network node of the first network a request for network sharing with the second network, wherein the request includes information indicating a reason for sharing.

[0021] According to the seventeenth aspect, a method is provided, comprising: sending an indication to a network node of a first network, the indication indicating that a second network has capacity for network sharing with the first network; and receiving from a network node of the first network a request for network sharing with the second network, wherein the request includes information indicating a reason for sharing.

[0022] According to the eighteenth aspect, a computer program product is provided for: sending an instruction to a network node of a first network, the instruction indicating that a second network has capacity for network sharing with the first network; and receiving from a network node of the first network a request for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

[0023] According to a nineteenth aspect, a computer program product is provided, embodied on a computer-readable distributed medium and including program instructions that, when loaded into a device, execute a method comprising: sending an instruction to a network node of a first network indicating that a second network has capacity for network sharing with the first network; and receiving from a network node of the first network a request for network sharing with the second network, wherein the request includes information indicating a reason for sharing.

[0024] According to a twentieth aspect, an apparatus is provided, comprising components for performing: sending an instruction to a network node of a first network, the instruction indicating that a second network has capacity for network sharing with the first network; and receiving from a network node of the first network a request for network sharing with the second network, wherein the request includes information indicating a reason for sharing.

[0025] According to a twenty-first aspect, a user equipment is provided, including at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to perform at least: upon being registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including the at least one measurement to a network node.

[0026] According to a twenty-second aspect, a method is provided performed by a user equipment, the method comprising: when registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including at least one measurement to a network node.

[0027] According to the twenty-third aspect, a computer program product is provided for: when registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including at least one measurement to a network node.

[0028] According to a twenty-fourth aspect, a computer program product is provided, embodied on a computer-readable distributed medium and including program instructions that, when loaded into a device, execute a method comprising: upon being registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including the at least one measurement to a network node.

[0029] According to a twenty-fifth aspect, an apparatus is provided, comprising components for performing: when registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including at least one measurement to a network node.

[0030] According to a twenty-sixth aspect, an apparatus for a first network is provided, comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least perform: initiating network sharing between the first network and the second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; sending a request to the user equipment to perform measurements of the second network; and receiving measurements from the user equipment of the second network.

[0031] According to the twenty-seventh aspect, a method is provided, comprising: initiating network sharing between a first network and a second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; sending a request to the user equipment to perform measurements on the second network; and receiving measurements from the user equipment on the second network.

[0032] According to the twenty-eighth aspect, a computer program product is provided for: initiating network sharing between a first network and a second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; sending a request to the user equipment to perform measurements on the second network; and receiving measurements from the user equipment on the second network.

[0033] According to the twenty-ninth aspect, a computer program product is provided, embodied on a computer-readable distributed medium and including program instructions that, when loaded into a device, execute a method comprising: initiating network sharing between a first network and a second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; sending a request to the user equipment to perform measurements of the second network; and receiving measurements from the user equipment from the second network.

[0034] According to a thirtieth aspect, an apparatus is provided, comprising components for performing: initiating network sharing between a first network and a second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; sending a request to the user equipment to perform measurements of the second network; and receiving measurements of the second network from the user equipment.

[0035] The subject matter of the independent claims is provided according to several aspects. Further aspects are defined in the dependent claims. Embodiments not falling within the scope of the claims should be interpreted as examples that aid in understanding this disclosure. Attached Figure Description

[0036] Some embodiments will now be described by way of non-limiting, illustrative example only, with reference to the accompanying drawings, in which:

[0037] Figure 1 An example of a communication network to which the examples disclosed herein can be applied is shown;

[0038] Figure 2 Examples of methods for dynamic network sharing according to some embodiments are shown;

[0039] Figure 3 A second example of a method for dynamic network sharing from the perspective of a donor MNO, according to some embodiments, is shown;

[0040] Figure 4 An example of a negotiation process according to some embodiments is shown;

[0041] Figure 5 Examples of dynamic network sharing policies created or updated according to some embodiments are shown;

[0042] Figure 6 Examples of measurements that a UE may perform, according to some embodiments, are shown;

[0043] Figure 7 Examples of methods according to some embodiments are shown;

[0044] Figure 8 Examples of methods according to some embodiments are shown;

[0045] Figure 9 Examples of methods according to some embodiments are shown;

[0046] Figure 10 Examples of methods according to some embodiments are shown;

[0047] Figure 11 Examples of methods according to some embodiments are shown;

[0048] Figure 12 Examples of methods according to some embodiments are shown; and

[0049] Figure 13 Examples of apparatuses according to some embodiments are shown.

[0050] Figure 14 Example use cases are shown for supplementary network deployment and its relationship with the MNO. Detailed Implementation

[0051] The following embodiments are provided by way of non-limiting, illustrative example. Although this disclosure may refer to "a," "an," or "some" embodiments in several places in the text, this does not necessarily mean that every reference is made to the same embodiment(s), or that a particular feature applies only to a single embodiment. Individual features of different embodiments may also be combined to provide other embodiments. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, the application of such feature, structure, or characteristic in connection with other embodiments (whether explicitly described or not) is within the knowledge of those skilled in the art.

[0052] It should be understood that although the terms "first," "second," etc., may be used in this document to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0053] As used herein, the phrases “at least one of A or B,” “at least one of A and B,” and “A and / or B” mean (A), (B), or (A and B). As used herein, the phrases “A, B, and / or C” mean (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0054] As used herein, the term “or” means non-exclusive “or” unless otherwise indicated (e.g., “otherwise” or “or in an alternative”).

[0055] As used herein, unless explicitly stated otherwise, “responding to A” to perform a corresponding feature, step, or function does not indicate that the corresponding feature, step, or function is performed immediately after the occurrence of “A,” because one or more intervening features, steps, or functions may be performed (at least partially) between the occurrence of the corresponding feature, step, or function and “A.” Similarly, “based on A” to perform a corresponding feature, step, or function does not indicate that the corresponding feature, step, or function is performed solely based on “A,” because the corresponding feature, step, or function may be further based on one or more other features, steps, or functions besides “A.”

[0056] The embodiments described herein can be implemented in communication networks such as any of the following radio access technologies (RATs): WiMAX, GSM (2G), GSM EDGE Radio Access Network (GERAN), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS, 3G) based on Basic Wideband Code Division Multiple Access (W-CDMA), High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE and Enhanced LTE (eLTE), 5G (also known as NR), or any future RAT (such as 6G). In addition, communication within the communication network can utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple Access (OFDMA), and / or Discrete Fourier Transform Spread Spectrum OFDM (DFT-s-OFDM).

[0057] As used herein, the term "network device" or "network node" refers to a node in a communication network through which user equipment can access the network, and / or through which the node can control wireless communication and manage wireless resources within a cell. A network node or network device may be referred to as a base station (BS), access point (AP), or access node. Depending on the technology applied, a network device may be, for example, a Node B (NodeB or NB), an evolved Node B (eNodeB or eNB), an NR NB (also known as a gNB), a Remote Radio Unit (RRU), a Radio Headend (RH), a Remote Radio Headend (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low-power node, a non-terrestrial network (NTN), or an ungrounded network device (such as satellite network equipment, low Earth orbit (LEO) satellites and geostationary orbit (GEO) satellites, or aerospace network equipment).

[0058] In addition, for split radio access networks (RANs), network devices can refer to the centralized unit (CU) and / or the distributed unit (DU) of a base station. The interface between the CU and the DU may be referred to as the F1 interface in NR. In a split RAN architecture, node operations can be performed at least partially in a central / centralized unit (CU, e.g., a server, host, or node) that is operationally coupled to a DU (e.g., a radio headend / node). A CU can control one or more DUs, which at least act as transmit / receive (Tx / Rx) nodes. In some embodiments, a DU may include, for example, the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and the Physical (PHY) layer, while a CU may include layers above the RLC layer, such as the Packet Data Convergence Protocol (PDCP) layer, the Radio Resource Control (RRC) layer, and the Internet Protocol (IP) layer. Other functional splitting is also possible. In practice, any processing task can be performed in a CU or a DU, and the boundary for transferring responsibility between the CU and the DU may depend on the applied implementation.

[0059] The term "terminal device" refers to any end device capable of wireless communication. By way of non-limiting, illustrative example, a terminal device may be referred to as a communication device, user equipment (UE), subscriber station (SS), or mobile station (MS). A terminal device may be implemented as or included in the following: mobile phone, cellular phone, smartphone, IP-based voice (VoIP) phone, wireless local loop phone, tablet computer, wearable terminal device, personal digital assistant (PDA), portable computer, desktop computer, image capture terminal device (such as a digital camera), gaming terminal device, music storage and playback device, in-vehicle wireless terminal device, USB dongle, Internet of Things (IoT) device, watch or other wearable device, head-mounted display (HMD), vehicle, drone, medical device and application (e.g., remote surgery), industrial device and application (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics device, device operating on commercial and / or industrial wireless networks, etc.

[0060] As used herein, the term "resource" can refer to radio resources in the time domain, frequency domain, spatial domain, and / or code domain. Some examples of resources include, for example, physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. The terms "transmit" and / or "receive" can refer to wireless transmission and / or reception via a radio propagation channel on a radio resource.

[0061] Figure 1An example of a communication network to which the examples disclosed herein can be applied is shown. The communication network, or cellular communication network, may include a network node 110 configured to provide one or more cells (such as cell 100), and a network node 112 configured to provide one or more other cells (such as cell 102). For example, each cell may be, for example, a macrocell, microcell, femtocell, or picocell. A cell may define the coverage area or service area of ​​the corresponding node.

[0062] Network node 110 can provide radio access to a communication network to user equipment (UE) 120 (one or more UEs). Radio access may include downlink (DL) communication from the network node to UE 120 and uplink (UL) communication from UE 120 to the network node. Examples of uplink channels include a Physical Uplink Control Channel (PUCCH) for transmitting control information and a Physical Uplink Shared Channel (PUSCH) for transmitting data toward the network. Examples of downlink channels include a Physical Downlink Control Channel (PDCCH) for transmitting control information and a Physical Downlink Shared Channel (PDSCH) for transmitting data toward the user equipment.

[0063] Multiple UEs 120 and 122 can exist in the system. Each of the multiple UEs 120 and 122 can be served by the same or different network nodes 110 and 112. UEs can be configured to have dual connectivity (DC), where a UE (e.g., UE 120) can connect to multiple network nodes 110 and 112. UEs 120 and 122 can communicate with each other when a device-to-device (D2D) communication interface is established between them via a so-called "side link" (SL). For example, such D2D communication can be referred to as machine-to-machine communication, peer-to-peer (P2P) communication, or vehicle-to-vehicle (V2V) communication.

[0064] In a communication network with multiple network nodes, these nodes can connect to each other via interfaces. The LTE specification refers to this interface as the "X2" interface. The interface between an LTE node and a 5G node, or between two 5G nodes, can be called an Xn interface.

[0065] Network nodes 110 and 112 can be further connected to the core network 116 of the communication network via another interface.

[0066] For example, the LTE specification designates the core network as an Evolved Packet Core (EPC), and the core network may include, for example, a Mobility Management Entity (MME) and gateway nodes. The MME can handle the mobility of terminal devices within a tracking area covering multiple cells and handle signaling connections between the terminal devices and the core network. Gateway nodes can handle data routing to / from terminal devices within the core network.

[0067] For example, the 5G specification designates the core network as the 5G Core (5GC). The 5G Core can include, for example, Access and Mobility Management Functions (AMF), User Plane Functions / Gateways (UPF), and other functions. AMF can handle Non-Access Stratum (NAS) signaling termination, NAS encryption and integrity protection, registration management, connection management, mobility management, access authentication and authorization, and security context management. For example, UPF nodes can support packet routing and forwarding, packet inspection, and Quality of Service (QoS) processing.

[0068] Network sharing can be helpful in situations where network outages may occur, such as during natural disasters or major events.

[0069] Due to their extensive geographical coverage, mobile communication networks have become a primary source of communication during humanitarian efforts in major disasters. Importantly, mobile communication networks are resilient and capable of rapid recovery during major disasters.

[0070] The GSMA Disaster Response Plan report outlines key aspects of disaster response strategy, such as: -Early warning systems and preparedness; - Improve the ability to provide necessary services to customers; - Improve the capacity to support the work of humanitarian agencies; -Reduce damage to the physical network infrastructure during disasters; - Reduce mobile network failures during disasters; and - Improve business continuity and revenue protection.

[0071] Disaster scenarios typically lead to increased traffic, infrastructure damage, and different data prioritization mechanisms. Current solutions utilize disaster roaming (defined by 3GPP as Minimize Service Interruption (MINT)), where a UE can access any available Public Land Mobile Network (PLMN) to obtain basic communication services, regardless of the UE's operator. For disaster roaming to be activated, the government entity needs to declare the affected area a disaster zone. MINT does not cover situations where no public disaster has been declared. MINT also does not cover situations where no public disaster exists but one or more operators are affected, such as localized power outages, localized fires, or infrastructure collapses affecting one or more operators. Furthermore, MINT requires UEs compatible with MINT, excluding certain user groups.

[0072] Some examples described in this article consider the concept of network sharing in disaster roaming, where the protocols of the MNO can guide the UE on the specific PLMN to select in the event of a disaster. 3GPP TS 22.261 V20 has defined service requirements for disaster response via “indirect network sharing,” a technology introduced in TS 23.501 V19 that simplifies the protocols for interactions between MNOs at the core network level.

[0073] Network sharing solutions typically rely on well-defined protocols and fixed resources (i.e., defined by the percentage (%) of network resources allocated to other MNOs for providing network sharing capabilities). However, this type of reservation solution is not suitable for adapting to dynamic needs related to network resource availability, usage, energy status, etc., including in disaster situations.

[0074] Some examples described in this document relate to “dynamic network sharing,” which can allow, enable, or otherwise facilitate optimal use of network resources and also expand disaster roaming (previously proposed in 3GPP TS23.122 V19.0.0). Dynamic sharing can determine the dynamic use of resources by the sharing operator, thus allowing for the utilization of more network sharing concepts. Some examples relate to notification and negotiation methods for dynamic network sharing, which allow, enable, or otherwise facilitate one or more of the collection, negotiation, and maintenance of all necessary information to determine whether and under what conditions sharing is acceptable.

[0075] The examples described in this article can be used to improve energy efficiency, load balancing, public safety, and / or quality of service (QoS) / quality of experience (QoE).

[0076] For energy efficiency, beneficiary nodes (nodes that benefit from services from another node) and donor nodes (nodes that provide services to UEs) can place their PLMN and CN (Core Network) in a given geographical area (they may partially overlap). Reduced traffic load can occur (e.g., due to time of day, etc.). Beneficiary mobile network operators (MNOs) can offload one or more UEs connected to their PLMN and shut down the PLMN in a given area for greater energy efficiency.

[0077] For load balancing, donor nodes may have unused resources while beneficiary nodes experience higher traffic than they can handle (e.g., due to special events, competitions, or concerts). Beneficiary nodes can move some UEs to the donor's network to maintain service continuity.

[0078] For public safety purposes, there may be situations where government agencies (e.g., acting as mobile virtual network operators (VMNOs)) require resources in a specific geographic area during a given time period.

[0079] QoS / QoE improvements can be achieved when the benefiting PLMN has agreements with neutral hosts or other third-party network providers (e.g., stores, shopping malls, etc.), where the neutral hosts or other third-party network providers may temporarily offer better network coverage than the PLMN itself, for example, in an indoor context. Therefore, the PLMN can decide to trigger network sharing whenever a sufficient number of its UEs are under the coverage of these providers (as long as they remain there). Since the benefiting PLMN may be separately billed by the providers for this coverage service, it may want to deactivate network sharing once a threshold is reached (e.g., none of its UEs are residing under that network). The benefiting PLMN can offer this functionality to its own subscribers and charge them additional fees to authorize them to benefit from the service.

[0080] The decision to trigger dynamic network sharing can be made autonomously by the base station (e.g., gNB) or the Dynamic Network Sharing Function (DyNS) feature. In some examples, the request can be triggered without prior knowledge of other operators' gNBs (also known as the target gNB). In some examples, DyNS initiates the process without prior involvement of any gNB. The release of dynamic (e.g., temporary) network sharing can be initiated by either the source or target network. The Dynamic Network Sharing Function (DyNSF) can handle inter-MNO interactions and configure intra-MNO sharing settings.

[0081] Some examples address the discovery of (multiple) candidate MNOs for network sharing. In a geographic area, there is often available coverage from more than one MNO. However, not all MNOs within an MNO can be sharing candidates or preferred sharing candidates due to the following: (1) The services they provide in a given area, (2) The type of energy they are using in their gNBs (e.g., renewable, non-renewable, etc.). (3) The level of flexibility / sharing types they support, (4) Their billing mechanisms, and / or (5) Special MNO / service provider agreements.

[0082] After identifying potential sharing MNOs (as future beneficiaries or donors), in some examples, a better understanding of the surrounding participants and sharing conditions can be determined. Metrics can be exchanged for network sharing decisions. One or more metrics determined on the donor or beneficiary MNO side can be used to perform the sharing decision to assess the value of the sharing. The conditions and requirements for enabling a donor MNO to share its resources or for a beneficiary MNO often vary by time and location. Additionally: (1) Available resources may be located in an unwanted portion of the spectrum. (2) The available services on the donor side may not cover the services provided by the beneficiary node (and therefore potentially requested), and / or (3) One of the partners (beneficiaries or donors) may be an undesirable sharing partner in that particular area or service (due to competition).

[0083] Some examples also provide a method for negotiation between MNOs. Further examples involve evaluating shared partners and creating / updating policies, for example, by taking measurements to demonstrate whether the UE is being properly served by the partner (to bill the UE and reimburse the donor).

[0084] The examples described in this article may involve the following situations / scenarios: 1) Declared public disasters – Public alert systems mark events as disasters and notify MNOs in the area (e.g., tsunamis, earthquakes, terrorist attacks, etc.). 2) Undeclared disasters – Disasters have varying degrees of impact on subsets of MNOs. These are events that public authorities do not declare as disasters (fires, building collapses, etc.). 3) Temporary network sharing for energy efficiency / energy saving purposes—such as an MNO using shared resources from another MNO to shut down its own gNB under low load; 4) Network sharing with business-driven entities (e.g., providing coverage to new areas, minimizing TCO (Total Cost of Ownership) per MNO, expanding coverage); and / or 5) Network sharing with flexible network resource management – ​​sharing during peak demand periods.

[0085] The examples described in this paper provide a method for identifying (multiple) candidate donor PLMNs for RAN sharing for a benefiting PLMN in a given area. This can be performed using UE measurements of available PLMNs in a geographic area and during a certain time period.

[0086] Some examples involve sharing policies regarding candidate PLMNs. This could include dynamic network sharing to allow, enable, or otherwise facilitate MNO negotiation of sharing conditions. It could also include assessments of the quality of service to the benefiting UE to enforce the sharing policies committed between the donor MNO and the benefiting MNO.

[0087] Figure 2 A method for signaling between beneficiary network 252 and donor network 250 is described, wherein beneficiary network 252 is the initiator (e.g., requester) of network sharing.

[0088] The background processes can occur from 201a to 203b. To determine the sharing partner, the benefiting DyNSF 258 can use previous incoming announcements received in 201a from one or more donor networks 250, and / or can use previous incoming UE measurements regarding candidate donor PLMNs as shown in 201b. These previously received UE measurements can be stored in a measurement store (Measurement Collection Entity (MCE)) as shown in 264, a UE Data Collector Function (UDC), a Unified Data Store (UDR), or can be received directly from the UE.

[0089] At 203, incoming announcements or UE measurements can initiate the creation or update of a shared policy at PCF (Policy and Control Function) 260 in the beneficiary network 252, and / or can trigger new UE measurement activities for the candidate donor PLMN in 203b.

[0090] At section 203b, the creation or updating of a policy (e.g., based on receiving a new notification from a potential donor PLMN) can trigger new UE measurement activities toward that donor PLMN candidate. Triggering can also be based on reasons for the activation of dynamic network sharing; for example, in the event of a disaster, new UE measurement activities can be triggered before the PLMN is compromised. UE measurement and UE selection are discussed further below.

[0091] At 205, the OAM (Operation, Administration, and Maintenance) 262 of the beneficiary network 252 detects a trigger for dynamic network sharing, which can be based on specific needs (e.g., due to disaster, energy saving, or load balancing). OAM 262 can initiate sharing by sending a signaling message to DyNSF 258 at 207 to notify the relevant geographic area and the reason for sharing. In other examples, the role of OAM 262 can be replaced by a core network entity (e.g., a core network function (NF)).

[0092] At 209, DyNSF 258 receives (e.g., obtains) a sharing policy corresponding to the sharing reason received at 207 from PCF 260 (or other core network NF or OAM) of beneficiary network 252.

[0093] At 211, DyNSF 258 can process the PCF response and create a sharing request for resources for donor network 250. At 213, the sharing request for resources can be sent from DyNSF 258 to DyNSF 256 of donor network 250. The request can describe at least one of the following: the requested resource; the requested frequency band; the reason for the sharing request (which can be indicated as, for example, a flag or code); and the conditions of the request (e.g., the requested duration or the requested price). In some examples, the request can be a probe (e.g., test / query) request sent to one or more donor networks.

[0094] At point 215, donor network 250 can determine its available resources and return a "shared response," thereby using its available resources to reject, accept, or partially accept the request. In some cases, negotiation between networks 250 and 252 can be performed at point 215.

[0095] At 217, DyNSF 258 may accept the response provided at 215, or may reject or partially reject the response to specifically confirm the probe request as an actual request. In the event of partial rejection, DyNSF 258 may negotiate further conditions with DyNSF 256, for example, by issuing a new request.

[0096] At 219, the beneficiary network 252 and the donor network 250 can activate network sharing for (multiple) beneficiary UEs 254. They can also indicate the behavior and / or thresholds that (multiple) of the beneficiary UEs should be returned to the beneficiary network 252. The node of the donor network 250 serves UE 264 and broadcasts the PLMN of the first network 252.

[0097] At point 221, a measurement of the benefiting UE regarding the identifier of the benefiting PLMN currently served by donor PLMN 250 can be requested (i.e., feedback regarding quality can be requested). An example of such a UE measurement is further discussed below. It should be noted that when a benefiting UE joins a sharing partner, they will provide quality feedback regarding their serving PLMN 250. Although the PLMN ID is not changed, the PLMN has been changed (the PLMN reachable frequency is changed to the sharing partner frequency). The quality feedback regarding their serving PLMN 250 can be provided to the benefiting network through forwarding by the donor network. The quality feedback can be visible to the donor network and can be used, for example, as evidence of QoS provided to the UE.

[0098] At point 223, beneficiary UE measurements are evaluated at point 252 of the beneficiary network under the donor's coverage. In this step, the beneficiary can assess whether the donor adheres to a specific Service Level Agreement (SLA) in terms of coverage or the services it provides (e.g., throughput). These measurements can also be used to adequately bill UEs and to reward / repay the donor network for the services provided.

[0099] At 225, a sharing policy can be enforced. This could be the result of the measurement at 223. Specifically, if the UE provides a measurement indicating that the beneficiary network 250 is not providing good coverage / service, the beneficiary network 252 can then update the sharing policy toward that beneficiary network 250 by blocking or restricting its access or issuing an alert to treat it as offline. The result of the enforcement may also lead to the updating of existing (e.g., current) sharing policies or the creation of new policies.

[0100] Figure 3 An example of a sharing process from the perspective of donor network 350, according to some embodiments, is shown.

[0101] At 327, PCF 358 of donor network 350 creates sharing policies for different sharing scenarios (e.g., energy saving, disaster recovery, load balancing, etc.).

[0102] At 329, PCF 358 configures the sharing policy at DyNSF 356 based on the generated policy. DyNSF 356 can subscribe to sharing policy updates at PCF 358.

[0103] At position 331, PCF 358 receives requests for resources, as referenced above. Figure 2 The request may include the reason for the sharing request (or the corresponding flag / code) and various technical details (e.g., regarding frequency band, target location, time, PLMN ID, etc.). The request may be a probe request.

[0104] At 333, DyNSF 356 can inspect network sharing conditions. This can include checking available resources, the sharing policy received at 331 for that reason (e.g., use case), and / or checking the MNO-specific policy for a given reason (e.g., use case).

[0105] At 335, DyNSF 356 prepares a response. Because strategies may differ based on reasons (e.g., use cases), the response from DyNSF 356 may vary depending on the use case.

[0106] At point 337, based on the shared conditions, the donor node's DyNSF 356 generates a response and notifies the beneficiary node 352. The response conditions may differ from the original request, as this is determined by the available resources in the donor network 350. If the response differs from the original request, negotiation can be triggered, as shown in the following reference. Figure 4 As stated above.

[0107] At 339, following the response from 337 (or, in some examples, after negotiation), the beneficiary node 352 can accept or reject the proposed shared configuration to specifically confirm the probe request.

[0108] Figure 4 An example notification method, according to some embodiments, can be performed between beneficiary node 452 and donor node 450. The notification method can be referenced above. Figure 2 This is used when reproducing the incoming notification step 201a (e.g., sent spontaneously or periodically based on internal or external triggers). The notification method can be referenced above. Figure 2 and Figure 3 The negotiation steps 215 and 337 are used. For example, the negotiation method can be used for inter-MNO negotiation in non-disaster situations.

[0109] Donor nodes 450 (e.g., DyNSF or gNB) may be limited to achieving specific quotas (e.g., the capacity supported by a specific amount of green energy).

[0110] At point 443, donor node 450 determines that the shared quota criteria are met (i.e., there is available capacity margin) and creates an announcement of available capacity. In some examples, the need to maximize the energy efficiency of the currently well-loaded network may trigger the sending (i.e., forwarding) of such announcements to UEs seeking to benefit from hosting them. In some examples, donor nodes periodically verify these shared quota criteria.

[0111] At 445, donor DyNSF 450 forwards the available capability announcement to beneficiary MNO DyNSF 452. In another example, a donor-sharing function can forward announcements from one or more donor nodes to one or more beneficiary-sharing functions. In another example, a donor-sharing function can aggregate information from one or more donor nodes and send an announcement to a beneficiary-sharing function that is valid for beneficiary nodes in a geographic region (added to the announcement). In another example, a donor-sharing function may not receive announcements from one or more donor nodes and autonomously generate available capability announcements based on similar information retrieved via other segments (e.g., OAM). In some examples, the identification of the beneficiary node used to send the announcement may be based on an internal sharing policy. In some examples, the announcement may be sent to intermediaries (e.g., broker nodes of organizations independent of one or more beneficiaries).

[0112] Benefit-sharing node 452 (e.g., DyNSF or gNB) receives advertisements from donor nodes. In some examples, the benefit-sharing node (e.g., DyNSF) propagates the received advertisements to another benefit-sharing node (e.g., gNB). In another example, the benefit-sharing node (e.g., DyNSF) can propagate advertisements from one or more donor nodes to one or more benefit-sharing nodes (e.g., gNB). In yet another example, the benefit-sharing node (e.g., DyNSF) can propagate advertisements to one or more benefit-sharing nodes (e.g., gNB) in an optimized manner (e.g., based on the provided geographic region).

[0113] After receiving the initial notification, potential beneficiary node 452 evaluated the notification at 447. Based on the results of this evaluation: • Beneficiary node 452 can return an "Accept" message to donor node 449 to indicate that the advertised aspect is "acceptable". In another example, the beneficiary can create a new "Share Request" message to send to the donor along with, for example, a subset of the advertised aspect. • If the announced conditions are not within the acceptable range for the potential beneficiary node 452, then at 449, node 450 may return a counter-proposal to indicate the preferred / acceptable conditions for the announced resource. • If a notice is unacceptable for non-negotiable reasons (e.g., due to competition in a given area, regulatory aspects, service availability at the donor community, etc.), then in 449, the beneficiary node 452 can directly send a “reject” response to indicate that any follow-up to the specific notice is closed. • Depending on the protocol or implementation shared between the MNOs, the beneficiary node 452 can submit a bid to the donor node 450 using a counter-proposal message at 449. The donor node 450 can then decide on the winning bid and provide a response.

[0114] At 451, upon receiving a counter-proposal message, donor node 450 can re-evaluate the advertisement and determine whether and how to continue the sharing process. If donor node 450 receives a counter-proposal from beneficiary node 452, donor node 450 can assess whether the given conditions are acceptable for the advertised resources. Here, the donor node may choose to implement admission controls for potential resource reallocation or some configuration to accept the request. If, under the new configuration, the donor node manages to create an advertisement in which resources can be shared for the given conditions, a new advertisement with the new resource configuration is prepared. If the configuration has not been changed, but only some conditions have been changed, the donor resends the previous advertisement with the updated conditions. The acceptability of a counter-proposal to donor node 450 can be determined by the donor node based on changes to the conditions or changes to the advertised resources (donor band), the duration of resource availability, etc. In some examples, upon receiving a counter-proposal, donor node 450 may determine to optimize some of its resource allocations to satisfy the counter-proposal.

[0115] If, at point 449, beneficiary node 452 returns a bid for the advertised resource, donor node 450 can evaluate that bid and other bids, and determine the winning bid. After this determination, donor node 450 can send an instruction to the winning beneficiary 452 at point 453 to accept the bid for network sharing.

[0116] At point 453, an updated announcement can be provided to the beneficiary node. If the counterproposal is unacceptable to the donor node 450, the donor node 450 can send a rejection at point 453.

[0117] When a new notification is received, although the entire process could be repeated (e.g., for the updated resource conditions mentioned in Option 1), the conditions are at an acceptable level from the beneficiary's perspective. Therefore, it directly sends an accept message to initiate sharing. In the event of malicious operation, such as the beneficiary node 452 resending a new set of conditions for the same resource, or refusing after the negotiation process, the donor node 450 may choose to blacklist node 452 to exclude it from future sharing opportunities.

[0118] Figure 5 Methods for creating and / or updating sharing policies on the donor side are illustrated according to some embodiments.

[0119] In order to decide to implement network sharing, the following may occur: (1) determining what the expected conditions of the required resources are, (2) configuring / checking the sharing policy for a given area, and (3) comparing the expected conditions with the announced conditions.

[0120] To determine the anticipated sharing conditions, specifically for energy-saving reasons, NWDAF 560 can collect predicted UE energy impacts from energy information functions 562 (e.g., from gNB, UPF, and AF) at 555 to create a new analysis. At 557, NWDAF can generate an analysis designed to generate a sharing strategy. At 559, NWDAF 560 can share the new analysis with PCF 558 to generate the sharing strategy.

[0121] The conditions for sharing policies may include: i. Minimum / maximum price (e.g., per UE / minute); ii. Geographical location of the resource / share; iii. The amount of resources requested; iv. Available donor options / resources; v. Pricing differences (e.g., better or worse portions of the spectrum, specific hardware, etc.); and / or vi. Carbon footprint offset (e.g., maximum per UE / minute).

[0122] The AF, NWDAF 560, and OAM at the donor network can be configured with sharing policies at the PCF 558. The PCF 558 can provide these conditions to the donor-side DyNSF.

[0123] Operators can have different policies for different locations (e.g., driven by their business dynamics), different times of day, or different sharing partners (e.g., different SLAs). When a request is received from the requester, it will be considered within the correct context and policy.

[0124] To track the correct context information, a shared policy entry that can include three parts can be used: • Expected / preferred conditions (this can be derived from NWDAF 560) • Strategies based on benefit, such as excluded or permitted MNOs (which could come from OAM), and / or • Carbon / energy sharing strategy (this can come from AF).

[0125] Now for reference Figure 6 The process for MNO discovery between MNO1 (donor node) 650 and MNO2 (beneficiary node 652) according to some embodiments will be discussed. Discovery can be delegated via UE 654.

[0126] The commissioned discovery process can be used by both donor 650 PLMN and beneficiary 652 PLMN to identify the best potential sharing partners around the geographic area and to create or update the corresponding sharing strategy.

[0127] The UE 654, which benefits from MNO2, can scan available VPLMNs (i.e., candidate donor PLMNs, such as MNO1) and can perform measurements.

[0128] In some examples, measurements can be performed by UE 654 and simultaneously serviced by the beneficiary node 652. UE 654 can be configured to measure (multiple) detectable VPLMNs and report the Received Reference Signal Power (RSRP) of (multiple) VPLMNs to the beneficiary node 652. These measurements on other cells of other available (“detected”) VPLMNs prior to sharing establishment can help understand which VPLMNs are available / optimal for sharing in a particular area, even if the beneficiary UE 654 has not yet connected to them.

[0129] In some examples, measurements can be performed by UE 654 when UE 654 is already being served by the donor PLMN 650 architecture. This can be performed when the donor PLMN 650 node broadcasts the benefiting PLMN ID (i.e., network sharing is activated). UE 654 can be configured to report the RSRP of its serving cell, strongest inter-frequency cell, and strongest inter-RAT cell.

[0130] UE measurements of the detected cells of the VPLMN can be performed before and / or after sharing is established. After sharing is established, UE measurements can help verify that the VPLMN effectively serves the UE (e.g., for billing purposes) and / or verify that the VPLMN effectively serves a specific area and is under committed and acceptable conditions, depending on the sharing policy (e.g., bit rate, QoS, etc.).

[0131] The UE is configured to perform and report recorded measurements for certain VPLMN cells, including inter-frequency measurements and inter-RAT (Radio Access Technology) measurements. This includes measurements such as signal strength, RSRP, RSRQ (Reference Signal Received Quality), and interference level (3GPP TS23.700-13–v1.0.0).

[0132] In addition to measuring radio quality, or as a substitute for measuring radio quality, the QoS level achieved by UE654 can be tracked during network sharing activation. To this end, the VPLMN can select a specific UE to generate a signaling-based trace or a signaling-based MDT (Minimum Drive Test), and request that UE to report UE throughput while being served to estimate whether the quality of service provided matches the committed SLA. Measurements can be configured at the per-UE throughput, per PDU (Protocol Data Unit) session throughput, per slice throughput, and / or per QoS flow throughput.

[0133] If the VPLMN (i.e., donor) and HPLMN (home PLMN) (i.e., beneficiary) are not configured to have the same slice or the same operator-defined 5G QoS identifier (5QI), then the VPLMN can be configured to have slice mapping and 5QI mapping in order to match the final result file in the Tracking Control Entity (TCE).

[0134] TCE can be shared as part of the RAN sharing strategy, allowing measurement files to be accessed by any partner MNO to assess the quality of benefiting UEs. Alternatively, when UEs return from donor to beneficiary status, they can collect and report quality statistics.

[0135] Alternatively, the VPLMN 5GC can delegate to the RAN to select UEs to collect the aforementioned measurements using managed tracking or managed MDT. In this case, the operator can correlate the radio conditions of the selected beneficiary UEs with the final quality of service they receive in the VPLMN.

[0136] In some examples, VPLMNs, whether based on or not based on HPLMN requests, can define a QoE Measurement Collection (QMC) configuration associated with the benefiting UE to collect experience quality data at the application layer. QMC reports can then be compared to the quality expected by the SLA.

[0137] In some examples, UE 654 may be requested to perform the following types of measurements (see 3GPP TS 36.331) to evaluate the donor PLMN 650. These measurements are performed based on OAM-based configuration triggers / parameters supplied to the UE, either when the UE is camped in the HPLMN or as part of the initial UE configuration process, as described in TS 32.422: • In-frequency measurement: Measurements at (multiple) downlink carrier frequencies of (multiple) serving cells. • Inter-frequency measurement: Measurement at a frequency different from the downlink carrier frequency of any of the (multiple) serving cells. • RAT measurements at NR frequency. • RAT inter-frequency measurement of UTRA frequency. • CBR measurement for V2X side link communication. • Sensing measurements for V2X side link communication.

[0138] Determining which UE(s)(s) to use to perform the measurement can depend on the network sharing scenario / purpose. To determine where to move the UE(s) (e.g., for energy efficiency purposes), all UEs connected to the PLMN are selected to perform the measurement.

[0139] Alternatively, if the purpose of the measurement is to gather PLMN availability and generate a location-based sharing policy, the UE that provides the most information can be selected to perform the measurement task. Therefore, a subset of UEs (e.g., those connected to the PLMN) is selected to minimize signaling overhead. For example, the DyNSF directly or indirectly (e.g., through UE data collection functions) examines UE context data in the UDM / UDR and identifies UEs in CM_connected mode and located in a specific tracking area (or TAI). Alternatively, the AMF can receive a list of UEs from the DyNSF to provide measurements, and the AMF accordingly forwards this information to the gNB serving those UEs.

[0140] In another example, DyNSF obtains the UE information list directly from OAM. Following this step, the network generates a shared policy and determines which PLMNs to use (e.g., in the event of a disaster), and provides this information to the UE. Unlike current implementations with priority lists, this approach allows the UE to know exactly which PLMN to connect to, speeding up the process and reducing signaling.

[0141] For the evaluation and implementation of sharing policies based on QoS measurements, if the evaluation is primarily driven by coverage, the RAN's selection of the benefiting UE can preferably be achieved through managed trace / MDT and contact with the relevant RAN nodes in the core network. If the evaluation of the sharing policy is primarily driven by the services provided, then signaling-based trace / MDT or QMC configuration should preferably be used in conjunction with UE selection performed by the core network.

[0142] Figure 7 An example of the method is shown. According to some embodiments, the method can be implemented by a computer. The method can be executed by a UE (such as UE 264).

[0143] like Figure 7 As shown, in 710, the method includes: receiving from a first network a configuration related to performance measurements of candidate networks for network sharing with the first network.

[0144] In 720, the method includes: detecting at least one node of another network while being served by a first network.

[0145] In 730, the method includes: measuring at least one other network based on the configuration.

[0146] In 740, the method includes: reporting at least one performance measurement of at least one other network to the first network.

[0147] Figure 8Examples of methods according to some embodiments are shown. The method can be implemented by a computer. For example, the method can be performed by a DyNSF 258.

[0148] like Figure 8 As shown, in 810, the method includes: receiving network sharing information, the network sharing information including at least one of the following: an indication from a second network indicating that the second network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network.

[0149] In 820, the method includes retrieving the network sharing policy from the network function.

[0150] In 830, the method includes: creating a network sharing request for a second network based at least on a network sharing policy and network sharing information.

[0151] Figure 9 Examples of methods according to some embodiments are shown. The method may be implemented by a computer. The method may be performed by a PCF (such as PCF 260).

[0152] like Figure 9 As shown in Figure 910, the method includes: receiving network sharing information, the network sharing information including at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network.

[0153] In 920, the method includes: creating a network sharing policy for a first network and at least one other network based on shared information.

[0154] Figure 10 Examples of methods according to some embodiments are shown. The method can be implemented by a computer. For example, the method can be performed by a DyNSF 256.

[0155] like Figure 10 As shown in 1010, the method includes: sending an indication to a network node of a first network, the indication indicating that a second network has capacity for network sharing with the first network.

[0156] In 1020, the method includes: receiving from a network node of a first network a request for network sharing with a second network, wherein the request includes information indicating the reason for the sharing.

[0157] Figure 11Examples of methods according to some embodiments are shown. This method can be implemented by a computer. For example, the method can be performed by UE 264.

[0158] like Figure 11 As shown in 1110, the method includes: when registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing.

[0159] In 1120, the method includes: performing at least one measurement on the second network.

[0160] In 1130, the method includes: sending a measurement report to a network node that includes at least one measurement.

[0161] Figure 12 Examples of methods according to some embodiments are shown. The method can be implemented by a computer. For example, the method can be performed by a DyNSF 258.

[0162] like Figure 12 As shown in 1210, the method includes: initiating network sharing between a first network and a second network, such that when a user equipment is registered to the first network, the second network serves the user equipment.

[0163] In 1220, the method includes: sending a request to the user equipment to perform measurements of the second network.

[0164] In 1230, the method includes: receiving measurements from a second network from a user equipment.

[0165] Figure 13 A block diagram of an apparatus 10 according to some embodiments is shown by way of example. The apparatus 10 includes, for example, at least one processor 12 and at least one memory 14 storing instructions 15, which, when executed by the at least one processor, cause the apparatus 10 to perform at least one or more methods disclosed herein and any embodiments thereof. In one example, at least one memory and instructions (e.g., computer program code, software) and at least one processor are configured to cause the apparatus 10 to perform one or more methods disclosed herein and any embodiments thereof.

[0166] The processor 12 may include, or be configured as, one or more circuit systems configured to perform stages of the method (or portions thereof) according to any embodiment described herein.

[0167] As used herein, the term “circuit system” may refer to one or more of the following: (a) a purely hardware circuit implementation, such as an implementation in an analog circuit system, a digital circuit system, and / or a quantum circuit system; (b) a combination of (multiple) hardware circuits and software, such as, where applicable: (i) a combination of (multiple) analog hardware circuits, digital hardware circuits, and / or quantum hardware circuits with software / firmware; and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital processors and / or quantum processors) with software and (multiple) memories, which work together to enable a device (such as a mobile device (e.g., user equipment, terminal equipment, etc.)) to perform various functions; and (c) any or all portions of (multiple) hardware circuits (such as (multiple) microprocessors and / or (multiple) quantum processors) that require software (e.g., firmware) to operate, but where the software is not required to operate, the software may be absent.

[0168] This definition of "circuit system" applies to all uses of the term herein, including in any claim. As a further example, as used herein, the term "circuit system" also covers the implementation of hardware circuitry or a processor (or processors) or a portion thereof, along with its accompanying software and / or firmware. For instance, if applicable to a particular claim element, the term "circuit system" also covers baseband integrated circuits or processor integrated circuits in mobile devices, or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0169] The memory 14 can be implemented using any suitable data storage technology. The memory may include a database for storing data. The memory 14 may be at least partially external to the device 10, but may be accessible by the device 10.

[0170] Instruction 15 may be included in a computer-readable medium or a non-transitory computer-readable medium. The term “non-transitory” as used herein refers to a limitation on the medium itself (i.e., tangible, non-signal), rather than a limitation on the persistence of data storage (e.g., random access memory RAM compared to read-only memory ROM).

[0171] For example, device 10 is a terminal device. As another example, the device is included in such a terminal device, for example, as a chipset configured to control the terminal device.

[0172] The apparatus 10 may be made or configured to perform at least the methods of one or more of the described embodiments.

[0173] Device 10 includes a wireless interface 16. The wireless interface 16 can provide communication capabilities to device 10. The wireless interface 16 may include a receiver configured to receive information according to at least one cellular or non-cellular standard. The wireless interface 16 may include a transmitter configured to transmit information according to at least one cellular or non-cellular standard. The receiver may include more than one receiver. The transmitter may include more than one transmitter. The wireless interface 16 may include a transceiver configured to receive and transmit information according to at least one cellular or non-cellular standard. The transceiver may include more than one transceiver.

[0174] Device 10 may include an interface (e.g., a user interface) 18, which includes at least one of, for example, a keyboard, microphone, touch display, monitor, speaker, etc. Interface 18 can be used by a user to control the device. Interface 18 may be external to device 10. For example, device 10 may be connected to another device (such as a computer) via a wireless or wired connection, and device 10 may be controlled via the computer.

[0175] In one embodiment, at least some of the processes described herein may be performed by an apparatus including components for performing at least some of the processes. Components for performing the method steps disclosed herein may include software and / or hardware components of apparatus 10. For example, at least one processor 12, memory 14, and computer program code form components for performing one or more methods disclosed herein and any embodiments thereof.

[0176] In some embodiments, further examples are provided in Appendix A.

[0177] In some embodiments, further examples are provided in Appendix B. As used herein, the term "component" should be interpreted as either the singular (i.e., a single element) or the plural (i.e., a combination of single elements). Therefore, the term "component for [performing A, B, C]" should be interpreted to cover an apparatus in which there is only one component for performing A, B, and C, or separate components for performing A, B, and C, or partially or completely overlapping components for performing A, B, and C. Furthermore, the terms "component for performing A," "component for performing B," and "component for performing C" should be interpreted to cover an apparatus in which there is only one component for performing A, B, and C, or separate components for performing A, B, and C, or partially or completely overlapping components for performing A, B, and C.

[0178] Here is a list of some aspects.

[0179] According to a first aspect, a method performed by a user equipment is provided, the method comprising: receiving from a first network a configuration related to performance measurements of candidate networks for network sharing with the first network; detecting nodes of at least one other network while being served by the first network; measuring the at least one other network based on the configuration; and reporting at least one performance measurement of the at least one other network to the first network.

[0180] Various embodiments of the first aspect may include at least one feature from the following list of dot symbols: • The first network includes the Public Land Mobile Network (PLMN); • The configuration includes at least one of the following: a list of PLMNs as candidates for network sharing with the first network; or a list of frequency layers in which candidates can operate for network sharing with the first network. • This configuration is for at least one of the following: Reference Signal Received Power (RSRP) measurement; Reference Signal Received Quality (RSRQ) measurement; Interference Level measurement; Inter-frequency measurement; or Inter-Radio Access Technology (RAT) measurement; • The method further includes: receiving a request to perform further measurements on at least one other network; performing the further measurements; and sending a report of the further measurements on at least one other network to the first network; • Further measurements of at least one other network include at least one of the following: RSRP measurement of at least one other network; QoS measurement of at least one other network; or QoE measurement of at least one other network.

[0181] According to a second aspect, a method is provided, comprising: receiving network sharing information, the network sharing information including at least one of the following: an indication from a second network indicating that the second network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieving a network sharing policy from network functions; and creating a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0182] Various embodiments of the second aspect may include at least one feature from the following list of dot symbols: •The method also includes: sending network sharing information to network functions; • Network functions include policy and control functions (PCF); • The method also includes: requesting further measurements for the second network from the user equipment; • The method also includes: receiving further measurements from the user equipment; retrieving a second network sharing policy from the network function; and creating a second network sharing request for the second network based at least on the network sharing policy and the further measurements; • The method further includes: receiving an instruction from an operation, management and maintenance OAM, core network function or other network function indicating that network sharing is required for a sharing situation; retrieving a network sharing policy for the sharing situation from the network function; generating a sharing request based on the sharing policy; and sending the sharing request to at least one other network; • The request includes at least one of the following: a request for a frequency range; information indicating the reason for the request to share; and the conditions for the requested sharing. • The reason includes at least one of the following: a declared public disaster; an undeclared disaster; energy efficiency or energy-saving purposes; expanded coverage; or flexible network resource management; • The method further includes: receiving a response from a second network, the response including acceptance of the request in whole or in part, rejection of the request, or a counter-proposal of the request; • The method further includes: sending a request to the user equipment to perform further measurements of the second network; receiving a report of the further measurements of the second network from the user equipment; and sending a report of the further measurements of the second network from the user equipment to the network function. • The method also includes: retrieving a third network sharing policy from network functions; and creating a third network sharing request for the second network based at least on the third network sharing policy and the report; • Further measurements of at least one other network include at least one of the following: RSRP measurement of at least one other network; QoS measurement of the second network; or QoE measurement of the second network.

[0183] According to a third aspect, a method is provided, comprising: receiving network sharing information, the network sharing information including at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with a first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and creating a network sharing policy for the first network and at least one other network based on the sharing information.

[0184] Various embodiments of the third aspect may include at least one feature from the following list of dot symbols: • The method further includes: receiving a request including information indicating the reason for sharing the network; selecting a sharing policy based on the request; and sending the sharing policy to network nodes of the first network; • The method further includes: receiving further measurements performed by the user equipment against at least one other network, wherein the further measurements are acquired during the service of the user equipment by the first network; and creating a new sharing policy or updating a sharing policy based on the further measurements.

[0185] According to a fourth aspect, a method is provided, comprising: sending an indication to a network node of a first network, the indication indicating that a second network has capacity for network sharing with the first network; and receiving from a network node of the first network a request for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

[0186] Various embodiments of the fourth aspect may include at least one feature from the following list of dot symbols: •The method also includes: registering the second network service with the user equipment of the first network; • The method also includes: receiving from the network node one or more sharing policies corresponding to at least the received sharing reason; • Network nodes are configured to provide PCF; • The request includes the requested conditions for network sharing; • The method further includes: in response to the request, sending information to network nodes of the first network indicating acceptance of the request in whole or in part, rejection of the request, or a counter-proposal of the request; The method further includes: determining that the second network has capacity for network sharing; and sending an indication to the first network indicating that the second network has capacity for network sharing.

[0187] According to a fifth aspect, a method is provided, comprising: when registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including at least one measurement to a network node.

[0188] Various embodiments of the fifth aspect may include at least one feature from the following list of dot symbols: • The network node belongs to the second network; • The network node belongs to the first network and sends the measurement report after the network share is deactivated; • The second network broadcasts the first network's Public Land Mobile Network (PLMN); • This configuration includes at least one measurement threshold derived from at least one Service Level Agreement (SLA) requirement; • This measurement includes the reference signal received power (RSRP) measurement of the second network; • This configuration includes a request to measure at least one of the following: at least one quality of service (QoS) measurement of another network; or at least one quality of experience (QoE) measurement of another network; throughput per UE; throughput per PDU session; throughput per slice; throughput per QoS flow; • The measurement report indicates whether at least one measurement threshold has been met or exceeded; • The method also includes: performing further RSRP measurements on the strongest frequency cell and the strongest radio access technology cell; and reporting the further measurements to the network nodes of the first network; • The method further includes: receiving QoE measurement collection QMC configuration; and reporting QoE measurements to network nodes of the first network based on the QMC configuration; • The first network is served by the beneficiary PLMN, and the second network is served by the donor PLMN.

[0189] According to a sixth aspect, a method is provided, comprising: initiating network sharing between a first network and a second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; sending a request to the user equipment to perform measurements on the second network; and receiving measurements from the user equipment on the second network.

[0190] Various embodiments of the sixth aspect may include at least one feature from the following list of dot symbols: • This measurement includes the reference signal received power (RSRP) measurement of the second network; • The measurement includes at least one of the following: at least one Quality of Service (QoS) measurement of another network; or at least one Quality of Experience (QoE) measurement of another network; • This measurement indicates whether the Service Level Agreement (SLA) between the network node and the user equipment is met; • The method further includes: receiving at least one QoE measurement from a user equipment, the at least one QoE measurement being based on a QMC configuration applied at the user equipment; and creating a second sharing policy for the first network and the second network, or updating the sharing policy for the first network and the second network; • The method further includes: receiving further RSRP measurements from the user equipment for the strongest frequency cell and the strongest radio access technology cell; and creating a third sharing policy for the first network and the second network, or updating the sharing policy for the first network and the second network.

[0191] According to a seventh aspect, a user equipment is provided, including at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to at least: receive from a first network a configuration related to performance measurements of candidate networks for network sharing with the first network; detect nodes of at least one other network while being served by the first network; measure at least one other network based on the configuration; and report at least one performance measurement of the at least one other network to the first network.

[0192] Various embodiments of the seventh aspect may include at least one feature from the list of dot symbols under the first aspect.

[0193] According to an eighth aspect, an apparatus for a first network is provided, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: receive network sharing information, the network sharing information including at least one of: an indication from a second network indicating that the second network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, the report including radio-related information of at least one other network, the at least one other network including the second network; retrieve a network sharing policy from network functions; and create a network sharing request for the second network based at least on the network sharing policy and the network sharing information.

[0194] Various embodiments of the eighth aspect may include at least one feature from the list of dot symbols under the second aspect.

[0195] According to a ninth aspect, an apparatus for a first network is provided, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: receive network sharing information, the network sharing information including at least one of: an indication from at least one other network indicating that at least one other network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, the report including the signal strength of at least one other network; and based on the sharing information, create a network sharing policy for the first network and at least one other network.

[0196] Various embodiments of the ninth aspect may include at least one feature from the list of dot symbols under the third aspect.

[0197] According to a tenth aspect, an apparatus for a second network is provided, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to at least: send an instruction to a network node of a first network indicating that the second network has capacity for network sharing with the first network; and receive a request from a network node of the first network for network sharing with the second network, wherein the request includes information indicating a reason for sharing.

[0198] Various embodiments of the tenth aspect may include at least one feature from the list of dot symbols under the fourth aspect.

[0199] According to an eleventh aspect, a user equipment is provided, including at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to perform at least: when registered to a first network and served by a second network, wherein the first network and the second network use network sharing, receiving from the second network a configuration for performing measurements of the second network related to the performance of the network sharing; performing at least one measurement of the second network; and sending a measurement report including at least one measurement to a network node.

[0200] Various embodiments of the eleventh aspect may include at least one feature from the list of dot symbols under the fifth aspect.

[0201] According to a twelfth aspect, an apparatus for a first network is provided, comprising at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the apparatus to at least: initiate network sharing between the first network and the second network, such that when a user equipment is registered to the first network, the second network serves the user equipment; send a request to the user equipment to perform measurements of the second network; and receive measurements from the user equipment of the second network.

[0202] Various embodiments of the twelfth aspect may include at least one feature from the list of dot symbols under the sixth aspect.

[0203] According to the thirteenth aspect, a computer program product is provided, embodied on a distributed medium and including program instructions that, when executed by a device, cause the device to perform the method according to the first, second, third, fourth, fifth or sixth aspect.

[0204] According to a sixth aspect, a computer program product including program instructions is provided, which, when executed by a device, cause the device to perform the method according to the first aspect, second aspect, third aspect, fourth aspect, fifth aspect, or sixth aspect.

[0205] According to a seventh aspect, an apparatus is provided, including components for performing the method according to a first aspect or a second aspect, and / or components configured to cause the apparatus to perform the method according to a first aspect, a second aspect, a third aspect, a fourth aspect, a fifth aspect, or a sixth aspect.

[0206] Even though various embodiments of this disclosure have been described above with reference to examples in conjunction with the accompanying drawings, it is clear that this disclosure is not limited thereto and can be modified in various ways. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate rather than limit the corresponding embodiments. It will be apparent to those skilled in the art that the various embodiments of this disclosure can be implemented in various ways as technology advances. Furthermore, it will be clear to those skilled in the art that the described embodiments(s) (or portions thereof) can, but are not necessarily, be combined in various ways with any other embodiments(s) (or portions thereof) to form additional embodiments. Appendix A

[0207] In some embodiments, an example 3GPP pseudo change request (pCR) is provided as follows.

[0208] Title: Use Cases for Supplementing Network Extensions

[0209] Agenda item: 8.1.7

[0210] Abstract: This paper proposes new use cases for 6G TR.

[0211] ---pCR Proposal---

[0212] W Other use cases

[0213] First change (all new text below)

[0214] W.1 Use Cases Regarding Supplemental Coverage and Capacity Expansion

[0215] W.1.1 Description

[0216] For mobile network operators (MNOs) aiming to deploy new radio access network (RAN) nodes to enhance coverage or capacity, minimizing capital and operating expenditures and managing the cost per gigabyte is a critical challenge. This is particularly difficult for densely populated small cells, indoor coverage (e.g., shopping malls, commercial / enterprise / factory buildings), remote areas with no or limited MNO coverage, and self-organized hotspots (e.g., music festivals, stadiums). Therefore, deployment models with supplementary RAN nodes provided by third-party entities can be quite beneficial. Furthermore, various industries such as smart manufacturing, next-generation utility networks, and shipping are increasingly demanding network redundancy, multi-tenancy and multi-tiered services, and shared RAN / core network (CN) services. For example, stadiums may need to establish temporary multi-MNO access for visitors, while factories may operate multiple non-public networks (NPNs) from different providers, combining independent non-public networks (SNPNs) with non-public networks integrated with public networks (PNI-NPNs). In such scenarios, third-party entities (e.g., site / real estate owners, enterprises) can deploy RAN nodes as needed / as required, supporting supplementary coverage / capacity expansion services.

[0217] In this context, a network deployed by a third party (such as a site / property owner or enterprise) is referred to as a "supplementary network." Managing and coordinating coverage and capacity expansion services can be a significant burden for both the owners of the supplementary network nodes and the mobile network operator (MNO), making a direct business relationship less than ideal. Therefore, an intermediary entity, called a "supplementary network service provider," can exist to manage the supplementary network and provide coverage / capacity expansion services to the MNO. The supplementary network service provider can be an MNO or a third-party entity, and it may or may not be the same as the supplementary network node owner. The supplementary network service provider acts as an intermediary between the supplementary network and the MNO, thereby providing management and coordination for coverage and capacity expansion services.

[0218] like Figure 14 As shown, various business models and deployment options can exist. A supplemental network service provider (SNSP) can have business relationships with multiple MNOs, allowing it to allocate supplemental network nodes to serve certain MNO users. The SNSP can own and manage the required spectrum (i.e., shared spectrum), enabling RAN-sharing modes with other MNOs. As a private network operator, the SNSP can enable access to NPN or public network services.

[0219] The spectrum can be licensed or unlicensed bands owned by the MNO or supplemental network service provider being served. The access network technology for supplemental network nodes can be terrestrial or non-terrestrial.

[0220] To foster a healthy ecosystem between supplemental network owners (responsible for deploying RAN nodes and contributing coverage / capacity expansion services) and MNOs (funding coverage / capacity expansion services), a robust means of enabling verification of coverage / capacity expansion services is crucial. Supplemental network owners should be incentivized (e.g., compensated by MNOs) based on their contributions to coverage / capacity expansion services, according to the actual coverage and / or data usage of the supplemental network. Therefore, mechanisms for providing reliable reporting of coverage / capacity metrics should be considered, including: a) Coverage proof: The UE can collect and report configuration information to the network (supplementary NW provider), such as the monitored radio bands, the measured RF quality, the timestamps of the measurements, and the location. b) Justification: Existing mechanisms and metrics can be used to collect UE or RAN traffic measurements (e.g., MDT), or enhanced mechanisms or metrics can be considered.

[0221] In this use case context, the UE performing the coverage verification is referred to as the "auxiliary UE". The auxiliary UE should be authorized by the supplemental network service provider and configured as a participant in the coverage verification. An auxiliary UE located in a geographic area where the supplemental network is deployed can perform coverage verification and report the necessary information without needing to access or reside in the network through supplemental network coverage. The auxiliary UE can be any UE with or without an MNO subscription and only monitors / reports certain information about the supplemental network node for coverage verification operations. The auxiliary UE can be a regular UE (e.g., a smartphone) or a dedicated UE for coverage verification purposes (e.g., an IoT device). A UE performing usage verification is a regular UE that accesses the MNO network through a supplemental network node, for which coverage / capacity extension services for the MNO are enabled.

[0222] The supplementary network service provider operates a coverage verification node, which configures the auxiliary UE for coverage verification operations (i.e., configures the information for coverage verification reports) and collects coverage verification reports from the auxiliary UE. Since the auxiliary UE does not access the network through the supplementary network node, it can send coverage verification reports to the coverage verification node using another connectivity technology (i.e., Bluetooth, WiFi) or another MNO subscription (not part of the coverage / capacity extension service). Based on the coverage verification reports collected from multiple auxiliary UEs, the coverage verification node verifies the coverage verification results and shares these results with the MNO for settlement of the coverage / capacity extension service.

[0223] The supplemental network service provider can also operate a usage verification node, configure the supplemental network node and UEs using connectivity services through the supplemental network node, and collect usage verification reports from these entities. This information can be supplementary to the usage collection performed by the MNO. Based on this report, the usage verification node verifies the results of the usage verification and shares the settlement of coverage / capacity extension services with the MNO. The usage verification node can be integrated into the coverage verification node, as it is designed to provide the MNO with reliable results of coverage / capacity extension service utilization.

[0224] Another aspect of fostering the ecosystem is defining appropriate interfaces and signaling for supplemental coverage / capacity expansion services between supplemental network nodes, supplemental network service providers, and MNOs. a) Interface between the supplementary network node and the supplementary network service provider: In order to configure and report proof of use, the supplementary network node is configured to serve in the requested frequency band(s), at the requested location and time of operation, or under any other radio parameters based on the MNO requirements. b) Interface between the supplementary network service provider and the MNO: Enables an open API for coverage / capacity expansion services. Through this API, the MNO can provide the supplementary network provider with the necessary requirements for coverage / capacity expansion services. Furthermore, it enables signaling exchange to update or terminate coverage / capacity expansion services.

[0225] W.1.2 Prerequisites

[0226] Brokerverage is a supplemental network service provider (SNLP) that has entered into business deals with MNO #1 for coverage / capacity expansion services in the country. Brokerverage acts as a broker, enabling SNLPs to use the MNO's spectrum for coverage / capacity expansion services within the business relationship, since Brokerverage is not an MNO and does not have licensed spectrum available to these SNLPs. Brokerverage has the largest number of service SNLPs nationwide because, among other SNLPs, it has consistently promoted the most competitive compensation for participation in coverage / capacity expansion services. Compensation for participation in coverage / capacity expansion includes compensation for SNLPs based on the presence and quantity of offloaded data, compensation for UEs performing proof of use, and compensation for auxiliary UEs performing proof of coverage.

[0227] Brokerverage operates coverage verification nodes and usage verification nodes within its system. Brokerverage has commercially advertised its supplementary UE program to increase the number of supplementary UEs participating in their coverage / capacity extension service verification. Users can participate in the supplementary UE program using their smartphones, or Brokerverage provides IoT devices for supplementary UE operation. Supplementary UE participant information is managed in the coverage verification node, which can select / configure a list of supplementary UEs to verify the participation of supplementary network nodes in coverage / capacity extension services for MNOs in a specific geographic area or at a specific time. The usage verification node uses information to be measured for usage verification reports to configure supplementary network nodes and UEs with connectivity through the supplementary network nodes.

[0228] Donald is a representative of a franchised restaurant chain with over 100 locations nationwide, many of which are located in suburban areas with poor cellular coverage. Donald decided to deploy supplemental network nodes in their locations to provide better coverage not only for their customers but also for those outside their restaurants. By providing cellular coverage both inside and outside their restaurants, Donald aimed to generate economic benefits from the coverage / capacity extension service. Donald reviewed available supplemental network service providers and their bids for compensation for the coverage / capacity extension service, and selected the one offering the greatest economic benefit: Brokerverage.

[0229] MNO#1 has noticed customer complaints regarding the shopping mall location (where the Donald Buck franchise restaurant is located) due to poor coverage. MNO#1 has decided to enter into a deal with Brokerverage for their coverage / capacity expansion services in the shopping mall area, with payment based on verification of the presence of supplemental network nodes (proof of coverage) and the amount of data offloaded by the supplemental network nodes.

[0230] Miles is an energetic person whose life is filled with morning jogs and evening bike rides through town. After seeing the announcement of the Coverage Proof program, Miles became interested in using her workout time to earn money. Miles's device doesn't have any specific MNO subscription.

[0231] Ethan, a tech enthusiast and college student, recently learned about the Coverage Proof program. He wants to join to earn some pocket money on his way to school or while hanging out.

[0232] John is a subscriber to MNO#1. He enjoys shopping and frequently posts his outfits on social media. Sometimes, he gets frustrated with posting video clips online due to the lack of coverage in the indoor shopping areas.

[0233] Mike is John's friend who roams from another country. Mike's HPLMN has a roaming agreement with MNO#1, so he uses MNO#1's coverage when he visits John. John and Mike are both enrolled in the Proof of Use program from Brokerverage.

[0234] Note: The users mentioned above are just individual examples; there may be many other auxiliary user interfaces (from other users).

[0235] W.1.3 Service Process 1) Donald signed a supplemental network service provider (SNF) agreement with MNO#1 for coverage / capacity expansion services. Based on this agreement, the SNF (Brokerverage in this example) selects and uses operational parameters to configure the supplemental network nodes. These parameters include, for example, time, location, coverage / usage proof-related parameters, and radio configuration parameters for using MNO#1's spectrum. Based on this configuration, the supplemental network nodes begin broadcasting MNO#1's PLMN in MNO#1's frequency band and connect to MNO#1's core network for control plane and user plane procedures. 2) Miles participated in a coverage verification program hosted by a supplemental network service provider (Brokerverage in this example) and received a miniature coverage verification device to wear on her wrist. This device was authenticated and authorized by Brokerverage's coverage verification node for coverage verification operations. Authentication and authorization were performed over the air interface (via connectivity enabled by the secondary UE, such as Bluetooth or WiFi). The coverage verification node configured the device (secondary UE) using information from coverage verification information, including which frequency band to monitor, location and time validity conditions, time slots for continuous reporting, and security materials. Using this device, she was eligible to earn financial rewards by contributing to coverage verification operations as a secondary UE. As she passed Donald's restaurant, the secondary UE detected the supplemental network node's broadcast cell and the PLMN of MNO#1, and measured the radio signaling configured for coverage verification operations. The secondary UE neither resided on nor registered with the supplemental network node. The auxiliary UE sends a coverage verification report for the detected supplementary network node to the coverage verification node via the air interface. The report includes information about the supplementary network node, the UE's location, the timestamp of the report, and radio signaling measurements. 3) Ethan subscribes to a coverage verification program hosted by a supplemental network service provider (Brokerverage in this example), and his smartphone is authenticated and enabled by Brokerverage's coverage verification node for coverage verification operations, acting as a secondary UE. The coverage verification node configures the device (secondary UE) using information from coverage verification information, including which frequency band to monitor, location and time validity conditions, time slots for continuous reporting, and security materials. When he is at a restaurant (for a date), his smartphone resides on MNO#2 (home MNO) and performs the supplemental NW's coverage verification operations as a secondary UE. The UE detects the broadcast cell of the supplemental network node and the PLMN of MNO#1, measures the radio signaling configured for coverage verification operations, and the secondary UE sends a coverage verification report for the detected supplemental network node to the coverage verification node via the air interface (through the secondary UE's connectivity to another MNO). This report includes information about the supplemental network node, the UE's location, the reporting timestamp, and the radio signaling measurements. When he uses his smartphone for data services, no coverage verification operations are performed. 4) When shopping near the Donald restaurant, John and Mike's UEs access the locally deployed supplemental network node (registered to MNO#1) and perform a usage proof operation configured by the network. The UE's usage proof report includes the amount of data transmitted through the supplemental network node's cell, the UE's geographic location, the timestamp of its stay in the cell, and radio signaling measurement information (e.g., average RF strength / quality). The supplemental network node also collects usage proof records based on, for example, the number of UEs served by the node, the amount of data offloaded by the node, the node's geographic location, and the operating time, and sends the report to the usage proof node in the supplemental network service provider (Brokerverage in this example). 6) The supplemental network service provider (Brokerverage in this example) collects reports of coverage and usage certificates to verify supplemental network operations and to determine the quality / quantity of MNO coverage / capacity expansion services achieved in the desired area and / or within the desired timeframe.

[0236] W.1.4 Postconditions

[0237] Based on the records of usage and coverage proofs, the supplementary network service provider (Brokerverage in this example) and MNO#1 can settle compensation amounts for contributions to coverage / capacity expansion services. Brokerverage can also verify the effectiveness of auxiliary UEs in determining their contributions to economic returns. In the coverage proof node, there are multiple coverage proof reports sent from multiple auxiliary UEs. Similarly, in the usage proof node, there are multiple usage proof reports sent from multiple UEs and the supplementary network node at that location.

[0238] Once more supplementary network nodes are deployed or some nodes are removed, the supplementary network service provider updates the configuration of the connected supplementary network nodes to meet the MNO's coverage / capacity expansion requirements.

[0239] Coverage / capacity expansion services can be terminated at any time via a request from the MNO. Coverage proofs can also be used to check for errors in the operation of replenishing network nodes after service termination.

[0240] W.1.5 Existing features that partially or fully cover the functionality of the use case.

[0241] Regarding the configuration of supplementary network nodes, the management requirements of the radio access network can be applied to the management of supplementary network nodes. Considering the inputs from the MNO for coverage / capacity expansion services (e.g., the location of the operation, the time validity conditions of the operation), the configuration parameters for coverage proof operations (information of the supplementary network node for coverage proof reports to assist UEs), and usage proof operations (information on the endpoint address of the usage proof node, various measurements of usage proof, such as the number of UEs served, the total amount of data offloaded), a new configuration mechanism will be required for the interface between the supplementary network node and the third party (i.e., the supplementary network service provider).

[0242] Minimized Drive Test (MDT) can partially cover coverage proof / use proof operations, although UE measurements will terminate in the RAN / OAM. Coverage proofs not connected to the RAN or coverage proofs / use proofs reported to network nodes belonging to a third party (i.e., supplemental network service providers) will require new functionality.

[0243] W.1.6 supports potential new requirements for use cases.

[0244] [PR W.1.6-1] The 6G system should be able to support mechanisms for coverage verification operations and usage verification operations, including the configuration and collection of information from UE and / or RAN nodes to verify the appropriate operation of certain network nodes, such as the location, frequency, RF metric, traffic measurement, timestamps, discovery of RAN sharing partners, and quality feedback after sharing.

[0245] [PR W.1.6-2] The 6G system should be able to support components used to authorize and configure participants (i.e., auxiliary UEs, network nodes) to perform coverage verification operations and usage verification operations and handover based on thresholds of these two measurements.

[0246] Note: Coverage verification can be performed by a UE that is not registered or connected to the network for normal communication operations. Verification is used under the assumption that the UE is connected to the network.

[0247] [PR W.1.6-3] 6G systems should be able to support open mechanisms between third-party entities (e.g., supplemental network service providers) and MNOs to enable negotiation of overlay proof operations and use proof operations, such as geographic region or time, number of UEs to be served, and target traffic offloading.

[0248] [PR W.1.6-4] The 6G system should be able to support suitable components for managing and configuring network nodes provided by third-party network providers, for example, for performing coverage proof operations and usage proof operations.

[0249] [PR W.1.6-5] 6G systems should be able to support appropriate security mechanisms for covering proof operations and using proof operations.

[0250] Changes complete

[0251] Appendix B

[0252] Example 1: A user equipment includes at least one processor and at least one memory storing instructions, which, when executed by the at least one processor, cause the user equipment to perform at least the following: Receive configuration related to performance measurements of candidate networks for network sharing with the first network from the first network; When served by the first network, detect at least one node from another network; Based on this configuration, measure at least one other network; and Report at least one performance measurement from at least one other network to the first network.

[0253] Example 2: The user equipment according to Example 1, wherein the first network includes a Public Land Mobile Network (PLMN).

[0254] Example 3: The user equipment according to Example 1 or 2, wherein the configuration includes at least one of the following: a list of candidate PLMNs for network sharing with a first network; or a list of candidate frequency layers in which network sharing with a first network can be operated.

[0255] Example 4: A user equipment according to any of the foregoing examples, wherein the configuration is for at least one of the following: Reference signal received power (RSRP) measurement; Reference signal reception quality (RSRQ) measurement; Interference level measurement; Frequency measurement; or Measurement between wireless access technologies (RATs).

[0256] Example 5: A user equipment according to any of the foregoing examples, wherein the instruction, when executed by at least one processor, causes the user equipment to perform at least the following: Receive a request to perform further measurements on at least one other network; Perform further measurements; and Send a report of further measurements from at least one other network to the first network.

[0257] Example 6: According to the user equipment described in Example 5, further measurements of at least one other network include at least one of the following: At least one other network's RSRP measurement; At least one other network's Quality of Service (QoS) measurement; or At least one other network's Quality of Experience (QoE) measurement.

[0258] Example 7: A user equipment according to any of the preceding examples, wherein a first network is associated with a first PLMN and a second network is associated with a second PLMN.

[0259] Example 8: A method executed by a user device, the method comprising: Receive configuration related to performance measurements of candidate networks for network sharing with the first network from the first network; When served by the first network, detect at least one node from another network; Based on this configuration, measure at least one other network; and Report at least one performance measurement from at least one other network to the first network.

[0260] Example 9: A computer program including instructions stored thereon for performing at least the following: Receive configuration related to performance measurements of candidate networks for network sharing with the first network from the first network; When served by the first network, detect at least one node from another network; Based on this configuration, measure at least one other network; and Report at least one performance measurement from at least one other network to the first network.

[0261] Example 10: An apparatus for a first network, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to perform at least the following: Receive network sharing information, which includes at least one of the following: an indication from a second network indicating that the second network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, which includes radio-related information of at least one other network, including the second network. Retrieve network sharing policies from network functions; and At least based on network sharing policies and network sharing information, create a network sharing request for the second network.

[0262] Example 11: The apparatus according to Example 10, wherein when the instruction is executed by at least one processor, the apparatus causes the apparatus to further perform at least the following: Send network sharing information to the network function.

[0263] Example 12: The apparatus according to Example 10 or 11, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: The user equipment requests further measurements for the second network.

[0264] Example 13: An apparatus according to any one of Examples 10 to 12, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Receive further measurements from the user equipment; Retrieve the second network sharing policy from the network functions; and Based at least on the network sharing policy and further measurements, a second network sharing request is created for the second network.

[0265] Example 14: An apparatus according to any one of Examples 10 to 13, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Receive instructions from the operation, management and maintenance of OAM, core network functions or other network functions, indicating that network sharing is required for the sharing situation; Retrieve the network sharing policy for the sharing situation from the network function; Based on the sharing strategy, a sharing request is generated; and Send a sharing request to at least one other network.

[0266] Example 15: An apparatus according to any one of Examples 10 to 14, wherein the request includes at least one of the following: Requests for frequency ranges; Indicates information regarding the reason for the sharing request; or The conditions requested for sharing.

[0267] Example 16: The apparatus according to Example 15, wherein the cause includes at least one of the following: Public disasters that have already been declared; An undeclared disaster; For energy efficiency or energy-saving purposes; Expand coverage; or Flexible network resource management.

[0268] Example 17: An apparatus according to Example 15 or 16, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Receive a response from the second network, which may include acceptance of the request in whole or in part, rejection of the request, or a counter-proposal of the request.

[0269] Example 18: The apparatus according to Example 17, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Send a request to the user equipment to perform further measurements on the second network; and Receive reports of further measurements from the second network from the user equipment; and Send a report of further measurements from the second network of the user equipment to the network function.

[0270] Example 19: The apparatus according to Example 18, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Retrieve the third network sharing policy from network functions; and At least based on the third network sharing policy and this report, create a third network sharing request for the second network.

[0271] Example 20: In the apparatus described in Example 18 or 19, further measurements of at least one of the other networks include at least one of the following: At least one other network's RSRP measurement; Quality of Service (QoS) measurement of the second network; or The second network's Quality of Experience (QoE) is measured.

[0272] Example 21: A method comprising: Receive network sharing information, which includes at least one of the following: an indication from a second network indicating that the second network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, which includes radio-related information of at least one other network, including the second network. Retrieve network sharing policies from network functions; and At least based on network sharing policies and network sharing information, create a network sharing request for the second network.

[0273] Example 22: A computer program including instructions stored thereon for performing at least the following: Receive network sharing information, which includes at least one of the following: an indication from a second network indicating that the second network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, which includes radio-related information of at least one other network, including the second network. Retrieve network sharing policies from network functions; and At least based on network sharing policies and network sharing information, create a network sharing request for the second network.

[0274] Example 23: An apparatus for a first network, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to perform at least the following: Receive network sharing information, which includes at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, which includes the signal strength of at least one other network. Based on shared information, create network sharing policies for the first network and at least one other network.

[0275] Example 24: The apparatus according to Example 23, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Receive a request that includes information indicating the reason for the network sharing; Based on this request, select a sharing policy; and Send the sharing policy to the network nodes of the first network.

[0276] Example 25: The apparatus according to Example 24, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Receive further measurements performed by the user equipment for at least one other network, wherein the further measurements were acquired during the service of the user equipment on the first network; and Based on further measurements, create a new sharing policy or update the existing sharing policy.

[0277] Example 26: A method comprising: Receive network sharing information, which includes at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, which includes the signal strength of at least one other network. Based on shared information, create network sharing policies for the first network and at least one other network.

[0278] Example 27: A computer program including instructions stored thereon for performing at least the following: Receive network sharing information, which includes at least one of the following: an indication from at least one other network indicating that at least one other network has capacity for network sharing with the first network; or a report from a user equipment serving the first network, which includes the signal strength of at least one other network. Based on shared information, create network sharing policies for the first network and at least one other network.

[0279] Example 28: An apparatus for a second network, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to perform at least the following: Send an indication to network nodes of the first network, indicating that the second network has capacity for network sharing with the first network; and Receive a request from a network node of the first network for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

[0280] Example 29: The apparatus according to Example 28, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: This enables the second network service to register with the user equipment of the first network.

[0281] Example 30: An apparatus according to Example 28 or 29, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Receive one or more sharing policies from the network node that correspond to at least the received sharing reason.

[0282] Example 31: The apparatus according to Example 30, wherein the network node is configured to provide PCF.

[0283] Example 32: An apparatus according to any one of Examples 28 to 31, wherein the request includes the requested conditions for network sharing.

[0284] Example 33: The apparatus according to Example 32, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: In response to the request, a message indicating acceptance of the request in whole or in part, rejection of the request, or a counter-proposal of the request is sent to the network nodes of the first network.

[0285] Example 34: An apparatus according to any one of Examples 28 to 33, wherein the instruction, when executed by at least one processor, causes the apparatus to perform at least: Determine that the second network has the capacity for network sharing; and Send an instruction to the first network indicating that the second network has capacity for network sharing.

[0286] Example 35: A method that includes: Send an indication to network nodes of the first network, indicating that the second network has capacity for network sharing with the first network; and Receive a request from a network node of the first network for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

[0287] Example 36: A computer program including instructions stored thereon for performing at least the following: Send an indication to network nodes of the first network, indicating that the second network has capacity for network sharing with the first network; and Receive a request from a network node of the first network for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

Claims

1. A user equipment comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the user equipment to perform at least the following: Receive configuration related to performance measurements of candidate networks for network sharing with the first network from the first network; When the service is provided by the first network, detect at least one node of another network; Based on the configuration, measure the at least one other network; as well as Report at least one performance measurement of the at least one other network to the first network.

2. The user equipment of claim 1, wherein the first network includes a Public Land Mobile Network (PLMN).

3. The user equipment of claim 1, wherein the configuration includes at least one of the following: a list of PLMNs as candidates for network sharing with the first network; or a list of frequency layers in which candidates can operate for network sharing with the first network.

4. The user equipment of claim 1, wherein the configuration is for at least one of the following: Reference signal received power (RSRP) measurement; Reference signal reception quality (RSRQ) measurement; Interference level measurement; Frequency measurement; or Measurement between wireless access technologies (RATs).

5. The user equipment of claim 1, wherein the instructions, when executed by the at least one processor, cause the user equipment to perform at least: Receive a request to perform further measurements on the at least one other network; Perform the further measurements; and Send a report of the further measurements from the at least one other network to the first network.

6. The user equipment of claim 5, wherein the further measurement of the at least one other network includes at least one of the following: RSRP measurements of at least one other network; The QoS measurement of at least one other network; or The Quality of Experience (QoE) measurement of at least one other network.

7. The user equipment of claim 1, wherein the first network is associated with a first PLMN and the second network is associated with a second PLMN.

8. An apparatus for a first network, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to perform at least: Receive network sharing information, the network sharing information including at least one of the following: an indication from a second network, the indication indicating that the second network has capacity for network sharing with the first network; Alternatively, it may come from a report from a user device serving the first network service, the report including wireless-related information from at least one other network, the at least one other network including the second network; Retrieve network sharing policies from network functions, and Based at least on the network sharing policy and network sharing information, a network sharing request is created for the second network.

9. The apparatus of claim 8, wherein the instructions, when executed by the at least one processor, cause the apparatus to further perform at least the following: Send the network sharing information to the network function.

10. The apparatus of claim 8, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: The user equipment requests further measurements for the second network.

11. The apparatus of claim 8, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: Receive the further measurement from the user equipment; Retrieve the second network sharing policy from the network function; and Based at least on the network sharing policy and the further measurements, a second network sharing request is created for the second network.

12. The apparatus of claim 8, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: Receive instructions from the operation, management and maintenance of OAM, core network functions or other network functions, indicating that network sharing is required for the sharing situation; Retrieve the network sharing policy for the shared situation from the network function; Based on the aforementioned sharing strategy, a sharing request is generated; as well as Send the sharing request to the at least one other network.

13. The apparatus of claim 8, wherein the request comprises at least one of the following: Requests for frequency ranges; Indicates information regarding the reason for the request to share; or The shared conditions requested.

14. The apparatus of claim 13, wherein the cause comprises at least one of the following: Public disasters that have already been declared; An undeclared disaster; For energy efficiency or energy-saving purposes; Expand coverage; or Flexible network resource management.

15. The apparatus of claim 13, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: Receive a response from the second network, the response including acceptance of the request in whole or in part, rejection of the request, or a counter-proposal of the request.

16. An apparatus for a first network, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to perform at least: Receive network sharing information, the network sharing information including at least one of the following: an indication from at least one other network, the indication indicating that the at least one other network has capacity for network sharing with the first network; Alternatively, it may come from a report from a user device serving the first network service, the report including the signal strength of the at least one other network; Based on the shared information, a network sharing policy is created for the first network and the at least one other network.

17. The apparatus of claim 16, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: Receive a request that includes information indicating the reason for the network sharing; Based on the request, select a sharing strategy; and The sharing policy is sent to the network nodes of the first network.

18. The apparatus of claim 17, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: Receive further measurements performed by the user equipment of the at least one other network, wherein the further measurements are acquired during the service of the user equipment by the first network; and Based on the further measurements, create a new sharing policy or update the existing sharing policy.

19. An apparatus for a second network, the apparatus comprising at least one processor and at least one memory storing instructions, the instructions, when executed by the at least one processor, causing the apparatus to perform at least: Send an indication to a network node of the first network, the indication indicating that the second network has capacity for network sharing with the first network; and Receive a request from a network node of the first network for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

20. The apparatus of claim 19, wherein the instructions, when executed by the at least one processor, cause the apparatus to perform at least: This enables the second network service to register with the user equipment of the first network.

21. A method for a user equipment, the method comprising: Receive configuration related to performance measurements of candidate networks for network sharing with the first network from the first network; When the service is provided by the first network, detect at least one node of another network; Based on the configuration, measure the at least one other network; as well as Report at least one performance measurement of the at least one other network to the first network.

22. A method for an apparatus for a first network, the method comprising: Receive network sharing information, the network sharing information including at least one of the following: an indication from a second network, the indication indicating that the second network has capacity for network sharing with the first network; Alternatively, it may come from a report from a user device serving the first network service, the report including wireless-related information from at least one other network, the at least one other network including the second network; Retrieve network sharing policies from network functions, and Based at least on the network sharing policy and network sharing information, a network sharing request is created for the second network.

23. A method for an apparatus for a first network, the method comprising: Receive network sharing information, the network sharing information including at least one of the following: an indication from at least one other network, the indication indicating that the at least one other network has capacity for network sharing with the first network; Alternatively, it may come from a report from a user device serving the first network service, the report including the signal strength of the at least one other network; Based on the shared information, a network sharing policy is created for the first network and the at least one other network.

24. A method for an apparatus for a second network, the method comprising: Send an indication to a network node of the first network, the indication indicating that the second network has capacity for network sharing with the first network; as well as Receive a request from a network node of the first network for network sharing with the second network, wherein the request includes information indicating the reason for the sharing.

Images