Radio access network sharing using transport proxy functionality

Abstract

Methods, systems, and devices for wireless communication are described. An access and mobility management function (AMF) agent may establish a first communication link between a radio access network (RAN) of a first network operator and a first AMF of the first network operator via the AMF agent, and establish a second communication link between the RAN of the first network operator and a second AMF of a second network operator via the AMF agent. The AMF proxy may receive a message from the RAN via the first communication link or the second communication link directed to a target proxy endpoint address of the first AMF or the second AMF. Thus, the AMF proxy may send a message from the RAN to the first AMF or the second AMF based on a mapping between a set of target proxy endpoint addresses and one or more source proxy endpoint addresses.

Description

[0001] Cross-references

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 317,885, filed May 15, 2023, entitled “RADIO ACCESSNETWORK SHARING USING A TRANSPORT PROXY FUNCTION”, which is assigned to the assignee of this application and is expressly incorporated herein by reference. Technical Field

[0003] The following discussion pertains to wireless communications, including Radio Access Network (RAN) sharing using transport proxy functionality. Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication for communication devices, which may be referred to as User Equipment (UE). Summary of the Invention

[0005] The described technology relates to improved methods, systems, devices, and apparatuses for supporting Radio Access Network (RAN) sharing using transport agent functions. For example, the described technology provides an Access and Mobility Management Function (AMF) agent that establishes a first communication link between a first network operator's RAN and a first AMF of the first network operator, and a second communication link between the first network operator's RAN and a second AMF of a second network operator, via the AMF agent. The AMF agent can receive messages via the first or second communication link from a source agent endpoint address corresponding to the RAN, the messages being directed to a target agent endpoint address of the first or second AMF. Therefore, the AMF agent can send messages from the RAN to the first AMF via the first communication link or to the second AMF via the second communication link based on a mapping between a set of target agent endpoint addresses including the target agent endpoint addresses of the first and second AMFs and one or more source agent endpoint addresses including the source agent endpoint address.

[0006] A method for wireless communication at an AMF (Advanced Management Function) agent is described. The method may include: establishing a first communication link via the AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator; establishing a second communication link via the AMF agent between the RAN associated with the first network operator and a second AMF associated with a second network operator; receiving a message via the first or second communication link from a source agent endpoint address corresponding to the RAN, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and sending the message from the RAN associated with the first network operator to the first AMF associated with the first network operator via the first communication link, or sending the message from the RAN associated with the first network operator to the second AMF associated with the second network operator via the second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0007] An apparatus for wireless communication at an AMF (Advanced Management Function) agent is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executable by the processor to cause the apparatus to: establish a first communication link via the AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator; establish a second communication link via the AMF agent between a RAN associated with the first network operator and a second AMF associated with a second network operator; receive a message via the first or second communication link from a source agent endpoint address corresponding to the RAN, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and send a message from the RAN associated with the first network operator to the first AMF associated with the first network operator via the first communication link, or send a message from the RAN associated with the first network operator to the second AMF associated with the second network operator via the second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including a source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0008] Another apparatus for wireless communication at an AMF agent is described. The apparatus may include: components for establishing a first communication link via an AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator; components for establishing a second communication link via an AMF agent between a RAN associated with the first network operator and a second AMF associated with a second network operator; components for receiving a message via the first or second communication link from a source agent endpoint address corresponding to the RAN, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and components for sending a message from the RAN associated with the first network operator to the first AMF associated with the first network operator via the first communication link or sending a message from the RAN associated with the first network operator to the second AMF associated with the second network operator via the second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including a source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0009] A non-transitory computer-readable medium is described, storing code for wireless communication at an AMF agent. The code may include instructions executable by a processor for: establishing a first communication link via the AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator; establishing a second communication link via the AMF agent between a RAN associated with the first network operator and a second AMF associated with a second network operator; receiving a message via the first or second communication link from a source agent endpoint address corresponding to the RAN, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and sending a message from the RAN associated with the first network operator to the first AMF associated with the first network operator via the first communication link, or sending a message from the RAN associated with the first network operator to the second AMF associated with the second network operator via the second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0010] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a set of multiple communication links between a set of multiple RANs and a set of multiple AMFs via an AMF agent, wherein each of the multiple communication links is between a corresponding RAN in the set of multiple RANs and a corresponding AMF in the set of multiple AMFs, wherein the set of multiple communication links includes a first communication link and a second communication link.

[0011] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, operations, features, components, or instructions may also be included. In the case where the first communication link is established directly between the RAN and the first AMF, the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a second communication link between the RAN and a second AMF associated with a second network operator via the first AMF, wherein the first AMF acts as an AMF agent.

[0012] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, receiving a message from the RAN via a first or second communication link may include operations, features, components, or instructions for: avoiding decoding the message from the RAN, and sending the message via the first communication link to a first AMF or via the second communication link to a second AMF using one or more source agent endpoint addresses, wherein the one or more source agent endpoint addresses correspond to the RAN.

[0013] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving a second message for a RAN from a first AMF via a first communication link or from a second AMF via a second communication link, the second message being directed to a second target agent endpoint address corresponding to the RAN; and sending the second message to the RAN via the first communication link or the second communication link based on the second target agent endpoint address corresponding to the RAN.

[0014] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, a first communication link terminates at a RAN associated with a first network operator and a first AMF associated with the first network operator, and a second communication link terminates at a RAN associated with the first network operator and a second AMF associated with a second network operator.

[0015] A method for wireless communication at a RAN associated with a first network operator is described. The method may include: establishing a first communication link between first AMFs associated with the first network operator via an AMF agent; establishing a second communication link between second AMFs associated with a second network operator via an AMF agent; and sending a message for the first AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the first communication link, or sending a message for the second AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a set of multiple target agent endpoint addresses and one or more source agent addresses including the source agent endpoint address, wherein the set of multiple target agent endpoint addresses includes the target agent endpoint address.

[0016] An apparatus for wireless communication at a RAN associated with a first network operator is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: establish a first communication link between first AMFs associated with the first network operator via an AMF agent; establish a second communication link between second AMFs associated with a second network operator via an AMF agent; and send a message for the first AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the first communication link, or send a message for the second AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0017] Another apparatus for wireless communication at a RAN associated with a first network operator is described. The apparatus may include: components for establishing a first communication link between first AMFs associated with the first network operator via an AMF agent; components for establishing a second communication link between second AMFs associated with a second network operator via an AMF agent; and components for sending a message for the first AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the first communication link, or sending a message for the second AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0018] A non-transitory computer-readable medium is described, storing code for wireless communication at a RAN associated with a first network operator. The code may include instructions executable by a processor for: establishing a first communication link between first AMFs associated with the first network operator via an AMF agent; establishing a second communication link between second AMFs associated with a second network operator via an AMF agent; and sending a message for the first AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the first communication link, or sending a message for the second AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0019] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a set of multiple communication links between a set of multiple AMFs and a set of multiple RANs via an AMF agent, wherein each of the multiple communication links is between a corresponding RAN in the set of multiple RANs and a corresponding AMF in the set of multiple AMFs, wherein the set of multiple communication links includes a first communication link and a second communication link.

[0020] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, operations, features, components, or instructions may also be included. Where a first communication link is established directly between the RAN and the first AMF, the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a second communication link between the second AMF and the RAN via the first AMF, wherein the first AMF acts as an AMF proxy.

[0021] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second message from a first AMF via a first communication link or from a second AMF via a second communication link, the second message being directed to a target agent endpoint address corresponding to the RAN.

[0022] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, both the first and second communication links terminate at the RAN.

[0023] A method for wireless communication at a first AMF is described. The method may include: establishing a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent; receiving a message directed to a target agent endpoint address corresponding to the first AMF from a source agent endpoint address corresponding to the RAN via the communication link; and decoding the message from the RAN based on the source agent endpoint address and the target agent endpoint address of the message.

[0024] An apparatus for wireless communication at a first AMF is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. These instructions may be executed by the processor to cause the apparatus to: establish a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent; receive, via the communication link, a message directed to a target agent endpoint address corresponding to the first AMF from a source agent endpoint address corresponding to the RAN; and decode the message from the RAN based on the source agent endpoint address and the target agent endpoint address of the message.

[0025] Another apparatus for wireless communication at a first AMF is described. The apparatus may include: components for establishing a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent; components for receiving, via the communication link, a message directed to a target agent endpoint address corresponding to the first AMF from a source agent endpoint address corresponding to the RAN; and components for decoding the message from the RAN based on the source agent endpoint address and the target agent endpoint address of the message.

[0026] A non-transitory computer-readable medium is described, storing code for wireless communication at a first AMF. The code may include instructions executable by a processor for: establishing a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent; receiving, via the communication link, a message directed to a target agent endpoint address corresponding to the first AMF from a source agent endpoint address corresponding to the RAN; and decoding the message from the RAN based on the source agent endpoint address and the target agent endpoint address of the message.

[0027] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a set of multiple communication links between a set of multiple RANs and a set of multiple AMFs via an AMF agent, wherein each of the multiple communication links in the set of multiple communication links is between a corresponding RAN in the set of multiple RANs and the AMF, wherein the set of multiple communication links includes the communication link.

[0028] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, establishing a communication link may include operations, features, components, or instructions for establishing a communication link between a RAN associated with a first network operator and a first AMF via an AMF agent, wherein the first AMF may be associated with a first network operator or a second network operator.

[0029] Some examples of the methods, apparatuses, and nontransitory computer-readable media described herein may also include operations, features, components, or instructions for sending a second message for the RAN to an AMF agent via the communication link, the second message being directed to a second target agent endpoint address corresponding to the RAN.

[0030] In some examples of the methods, apparatuses, and nontransitory computer-readable media described herein, the communication link terminates at the AMF. Attached Figure Description

[0031] Figure 1 An example of a wireless communication system supporting radio access network sharing (RAN) using a transmission proxy function, according to one or more aspects of this disclosure, is shown.

[0032] Figure 2 An example of a RAN-shared network architecture supporting the use of transport proxy functionality according to one or more aspects of this disclosure is shown.

[0033] Figure 3 An example of a RAN-shared wireless communication system that supports the use of a transport proxy function according to one or more aspects of this disclosure is shown.

[0034] Figure 4 An example of a RAN-shared network architecture supporting the use of transport proxy functionality according to one or more aspects of this disclosure is shown.

[0035] Figure 5 An example of a process flow supporting the use of a transport agent function in RAN sharing according to one or more aspects of this disclosure is shown.

[0036] Figure 6 and Figure 7 A block diagram of a RAN-shared device supporting the use of a transport agent function according to one or more aspects of this disclosure is shown.

[0037] Figure 8 A block diagram of a RAN-shared communication manager supporting the use of transport agent functionality, according to one or more aspects of this disclosure, is shown.

[0038] Figure 9A diagram of a system including devices supporting RAN sharing using transport agent functionality, according to one or more aspects of this disclosure, is shown.

[0039] Figure 10 and Figure 11 A block diagram of a RAN-shared device supporting the use of a transport agent function according to one or more aspects of this disclosure is shown.

[0040] Figure 12 A block diagram of a RAN-shared communication manager supporting the use of transport agent functionality, according to one or more aspects of this disclosure, is shown.

[0041] Figure 13 A diagram of a system including devices supporting RAN sharing using transport agent functionality, according to one or more aspects of this disclosure, is shown.

[0042] Figure 14 and Figure 15 A block diagram of a RAN-shared device supporting the use of a transport agent function according to one or more aspects of this disclosure is shown.

[0043] Figure 16 A block diagram of a RAN-shared communication manager supporting the use of transport agent functionality, according to one or more aspects of this disclosure, is shown.

[0044] Figure 17 A diagram of a system including devices supporting RAN sharing using transport agent functionality, according to one or more aspects of this disclosure, is shown.

[0045] Figures 18 to 22 A flowchart illustrating a method for RAN sharing that supports the use of a transport agent function according to one or more aspects of this disclosure is shown. Detailed Implementation

[0046] In some wireless communication systems, equipment (e.g., User Equipment (UE), network entities, core network nodes) may belong to a network operator. Some network operators may deploy network entities (e.g., base stations) and core network nodes (e.g., Access and Mobility Management Functions (AMF)) to serve UEs. For example, a first network operator may deploy network entities to establish a Radio Access Network Share (RAN) supporting wireless communication for first network operator UEs (e.g., UEs subscribed to or operated by the first network operator). The RAN may include one or more components, such as base stations or network entities, supporting communication for one or more wireless devices (such as UEs). In some cases, a first network operator may share its deployment (e.g., its RAN) with a second network operator, allowing the second network operator to avoid establishing or placing network entities to support the RAN that supports wireless communication for the second network operator's UEs. In doing so, the second network operator may alternatively use the RAN deployed by the first network operator to support the second network operator's UEs' communication within the RAN.

[0047] Traditionally, to support network sharing in this manner, the RAN can independently connect to the AMF of both the first and second network operators, and can forward messages to the appropriate AMF based on the network operator of the UE that sends the message to the RAN. However, the second network operator may avoid placing any local AMF for connecting to the RAN deployed by the first network operator (e.g., due to cost constraints, hardware constraints, or both). Therefore, without any local second network operator AMF, the RAN (deployed by the first network operator) may not be able to share with the second network operator, and thus may not be able to forward messages from second network operator UEs to the second network operator's core network.

[0048] Based on various aspects of this document, a first network operator and a second network operator can use the AMF proxy function to provide connectivity between the first network operator's RAN and the second network operator's remote AMFs. In some cases, the AMF proxy function may be referred to as a transport proxy. When used as a transport proxy, the AMF proxy allows the first network operator to share its RAN deployment with the second network operator, while the second network operator can avoid placing any local AMFs. For example, the first network operator's RAN can be directly connected to the AMF proxy with an equal number of connections (e.g., communication links and interfaces) to the AMF proxy. The AMF proxy can connect to the first network operator's AMFs and the second network operator's AMFs via separate connections. That is, the RAN can use different connections or interfaces to connect to each corresponding AMF via the AMF proxy. When sending messages, the RAN can send messages for each AMF via the AMF proxy on the appropriate connection or interface between the RAN and the AMF. The AMF proxy can receive messages and, based on the connection or interface on which the AMF proxy receives the messages and the target proxy endpoint address to which the messages are directed, can forward the messages to the correct AMF. Therefore, using the AMF proxy function can lead to reduced latency and improved communication efficiency.

[0049] Various aspects of this disclosure are first described in the context of wireless communication systems. Additional aspects of this disclosure are described with reference to wireless communication systems, network architecture diagrams, and process flows. Various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts related to RAN sharing using transport proxy functions.

[0050] Figure 1 An example of a RAN-shared wireless communication system 100 supporting the use of a transport proxy function according to one or more aspects of this disclosure is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not expressly mentioned herein.

[0051] Network entity 105 may be distributed across a geographical area to form wireless communication system 100 and may include devices in different forms or with different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, RAN node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support signal communication according to one or more radio access technologies (RATs).

[0052] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0053] As described herein, a node in the wireless communication system 100 (which may be referred to as a network node or a wireless node) may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Alternatively, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0054] In some examples, network entity 105 may communicate with core network 130 or with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entity 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entity 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0055] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home eNodeB, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, self-contained) base station architecture that may be configured to utilize a protocol stack physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0056] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105 (such as an Integrated Access Backhaul (IAB) network, an Open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a Virtualized RAN (vRAN) (e.g., a Cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a Central Unit (CU) 160, a Distributed Unit (DU) 165, a Radio Unit (RU) 170, a RAN Intelligent Controller (RIC) 175 (e.g., a near-real-time RIC, a non-real-time RIC), a Service Management and Orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0057] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU160 can connect to one or more DU 165s or RU 170s, and one or more DU 165s or RU 170s can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by the CU 160. Additionally or alternatively, a protocol stack functional split can be employed between the DU 165 and RU 170, such that the DU 165 can support one or more layers of the protocol stack, and the RU 170 can support one or more different layers of the protocol stack. The DU 165 can support one or more different cells (e.g., via one or more RU 170s). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165s via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170s via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 that communicate via these communication links.

[0058] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access can support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0059] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Alternatively, the CU 160 may communicate with the core network via an interface (which may be part of a backhaul link) and with other CU 160s (e.g., CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be part of a backhaul link).

[0060] IAB node 104 may refer to a RAN node that provides IAB functions (e.g., access for UE 115, radio self-backhaul capability, etc.). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Alternatively or additionally, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115.

[0061] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0062] When the techniques described herein are applied in the context of a decomposed RAN architecture, one or more components of the decomposed RAN architecture can be configured to support RAN sharing using transport proxy functions as described herein. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) can additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0063] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0064] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0065] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources that define the physical layer structure used to support the communication link 125. For example, a carrier for the communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used for both frequency division duplex (FDD) and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU 160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0066] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0067] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0068] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have a hardware configuration that supports communication using a specific carrier bandwidth, or may be configured to support communication using one of the carrier bandwidths in the set of carrier bandwidths. In some examples, the wireless communication system 100 may include a network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0069] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high-order modulation scheme can correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources can increase the data rate or data integrity used for communication with UE 115.

[0070] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0071] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which This can represent the supported subcarrier spacing, while The supported Discrete Fourier Transform (DFT) size can be represented. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0072] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0073] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0074] Physical channels can be multiplexed using various techniques to enable communication using carriers. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels for signaling via downlink carriers. The control region of a physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of a carrier or a subset of that bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0075] Network entity 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used to communicate with network entity 105 (e.g., using a carrier) and may be associated with an identifier used to distinguish adjacent cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other cell identifier). In some examples, a cell may also refer to a coverage area 110 or a portion of coverage area 110 (e.g., a sector) in which a logical communication entity operates. Depending on various factors such as the capabilities of network entity 105, the extent of such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping coverage areas 110, etc.

[0076] Macro cells typically cover a relatively large geographical area (e.g., a radius of several kilometers) and allow unrestricted access to UE 115 that has a service subscription with a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power network entity 105 (e.g., a lower-power base station 140) and can operate using the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 that has a service subscription with a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), UE 115 associated with a user in a home or office). Network entity 105 can support one or more cells and can also use one or more component carriers to support communication via one or more cells.

[0077] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0078] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0079] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, network entities 105 (e.g., base station 140) can have similar frame timings, and transmissions from different network entities 105 can be approximately time-aligned. For asynchronous operation, network entities 105 can have different frame timings, and in some examples, transmissions from different network entities 105 may not be time-aligned. The techniques described herein can be used for both synchronous and asynchronous operation.

[0080] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with network entity 105 (e.g., base station 140) without human intervention. In some examples, M2M communication or MTC may include communication from devices with integrated sensors or meters to measure or acquire information and relay such information to a central server or application that uses the information or presents it to people interacting with the application. Some UE 115 devices can be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geographic event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0081] Some UE 115s can be configured to operate in a power-saving mode, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not involve concurrent transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UE 115s include entering a power-saving deep sleep mode when not engaged in active communication, operating with limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UE 115s can be configured to operate using a narrowband protocol type associated with a defined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a carrier's guard band, or outside a carrier.

[0082] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritizing services, and such services may be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0083] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled) by network entity 105. In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0084] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU170) using vehicle-to-network (V2N) communication, or both.

[0085] The core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an AMF) and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnections to external networks. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0086] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer wavelengths in the lower frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0087] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or in the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band) using the spectrum. In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmission, EHF transmission may experience even greater attenuation and a shorter range. The techniques disclosed herein can be adopted for transmission across one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0088] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology. When operating using unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating using licensed frequency bands in a carrier aggregation configuration (e.g., LAA). Operations using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0089] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0090] Network entity 105 or UE 115 can use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique is known as spatial multiplexing. The multiple signals can be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals can be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0091] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device by the transmitting or receiving device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0092] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0093] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0094] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate combined beams for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback on beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0095] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0096] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmissions to improve link efficiency. In the control plane, the RRC layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0097] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device can provide HARQ feedback in subsequent time slots or according to a different time interval.

[0098] In some examples of the wireless communication system 100, devices (e.g., UE 115, network entity 105, core network 130 nodes) may belong to a network operator. Some network operators may deploy network entity 105 (e.g., base station 140) and core network 130 nodes (e.g., AMF) to serve UE 115. For example, a first network operator may deploy network entity 105 to establish a RAN supporting wireless communication for the first network operator's UE 115 (e.g., a UE 115 subscribed to or operated by the first network operator). In some cases, the first network operator may share its deployment (e.g., its RAN) with a second network operator, allowing the second network operator to avoid establishing or placing network entities to support the RAN supporting the wireless communication of the second network operator's UE 115. In doing so, the second network operator may alternatively use the RAN deployed by the first network operator to support the second network operator's UE 115's communication within the RAN.

[0099] Traditionally, to support network sharing in this manner, the RAN can independently connect to the AMF of both the first and second network operators, and can forward messages to the appropriate AMF based on the network operator of the UE 115 that sends the message to the RAN. However, the second network operator may avoid placing any local AMF for connecting to the RAN deployed by the first network operator (e.g., due to cost constraints, hardware constraints, or both). Therefore, without any local second network operator AMF, the RAN (deployed by the first network operator) may not be able to share with the second network operator, and thus may not be able to forward messages from the second network operator UE 115 to the second network operator's core network.

[0100] Therefore, both the first and second network operators can use the AMF proxy function to provide connectivity between the first network operator's RAN and the second network operator's remote AMFs. In some cases, the AMF proxy function may be referred to as a transport proxy. When used as a transport proxy, the AMF proxy allows the first network operator to share its RAN deployment with the second network operator, while the second network operator avoids placing any local AMFs. For example, the first network operator's RAN can be directly connected to the AMF proxy with an equal number of connections (e.g., communication links and interfaces) to the AMF proxy. The AMF proxy can connect to the first and second network operators' AMFs via separate connections. That is, the RAN can use different connections or interfaces to connect to each corresponding AMF via the AMF proxy. When sending messages, the RAN can send messages for each AMF via the AMF proxy on the corresponding connection or interface between the RAN and the AMF. The AMF proxy can receive messages, and based on the connection or interface on which the AMF proxy receives the messages and the target proxy endpoint on which the messages are directed, the AMF proxy can forward the messages to the correct AMF. Therefore, using the AMF proxy function can lead to reduced latency and improved communication efficiency.

[0101] Figure 2 An example of a network architecture 200 (e.g., a decomposed base station architecture, a decomposed RAN architecture) supporting the use of transport proxy functions according to one or more aspects of this disclosure is shown. Network architecture 200 may exemplify examples of one or more aspects for implementing wireless communication system 100. Network architecture 200 may include one or more CUs 160-a that can communicate directly with core network 130-a via backhaul communication link 120-a, or indirectly with core network 130-a via one or more decomposed network entities 105 (e.g., near-RT RIC 175-b via an E2 link or a non-RT RIC 175-a associated with SMO 180-a (e.g., an SMO framework) or both). CUs 160-a may communicate with one or more DUs 165-a via a corresponding midhaul communication link 162-a (e.g., an F1 interface). DUs 165-a may communicate with one or more RUs 170-a via a corresponding fronthaul communication link 168-a. RU 170-a may be associated with a corresponding coverage area 110-a and may communicate with UE 115-a via one or more communication links 125-a. In some implementations, UE 115-a may be served by multiple RU 170-a simultaneously.

[0102] Each network entity in network entity 105 of network architecture 200 (e.g., CU 160-a, DU 165-a, RU170-a, non-RT RIC 175-a, near-RT RIC 175-b, SMO 180-a, Open Cloud (O-Cloud) 205, Open eNB (O-eNB) 210) may include one or more interfaces or may be coupled to one or more interfaces configured to receive or transmit signals (e.g., data, information) via wired or wireless transmission media. Each network entity 105 or an associated processor (e.g., a controller) that provides instructions to the interfaces of network entity 105 may be configured to communicate with one or more network entities in other network entities 105 via transmission media. For example, these network entities 105 may include wired interfaces configured to receive signals or transmit signals to one or more network entities in other network entities 105 via wired transmission media. Additionally or alternatively, network entity 105 may include a wireless interface that may include a receiver, transmitter, or transceiver (e.g., an RF transceiver) configured to receive signals via a wireless transmission medium or to transmit signals to one or more other network entities in network entity 105, or both.

[0103] In some examples, the CU 160-a can host one or more higher-level control functions. Such control functions may include RRC, PDCP, SDAP, etc. Each control function can be implemented using an interface configured to communicate signaling with other control functions hosted by the CU 160-a. The CU 160-a can be configured to handle user plane functionalities (e.g., CU-UP), control plane functionalities (e.g., CU-CP), or combinations thereof. In some examples, the CU 160-a can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 160-a can be implemented to communicate with the DU 165-a for network control and signaling purposes, as needed.

[0104] DU 165-a may correspond to a logic unit that includes one or more functions (e.g., base station functions, RAN functions) for controlling the operation of one or more RU 170-a. In some examples, DU 165-a may at least partially host one or more aspects of the RLC layer, MAC layer, and PHY layer (e.g., high PHY layers, such as modules for FEC encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional partitioning, such as those defined by the 3rd Generation Partnership Project (3GPP). In some examples, DU 165-a may also host one or more low PHY layers. Each layer may be implemented using an interface configured to communicate with other layers hosted by DU 165-a or with control functions hosted by CU160-a.

[0105] In some examples, lower-layer functionality may be implemented by one or more RU 170-a units. For example, an RU 170-a controlled by a DU 165-a may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (e.g., performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, or both) based at least in part on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 170-a may be implemented to handle over-the-air (OTA) communications with one or more UE 115-a units. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 170-a may be controlled by the corresponding DU 165-a unit. In some examples, such configurations enable the DU 165-a and CU 160-a to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0106] The SMO 180-a can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network entities 105. For non-virtualized network entities 105, the SMO 180-a can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operation and maintenance interface (e.g., the O1 interface). For virtualized network entities 105, the SMO 180-a can be configured to interact with a cloud computing platform (e.g., O-Cloud 205) via a cloud computing platform interface (e.g., the O2 interface) to perform network entity lifecycle management (e.g., to instantiate virtualized network entities 105). Such virtualized network entities 105 may include, but are not limited to, CU 160-a, DU 165-a, RU 170-a, and near-RT RIC 175-b. In some specific implementations, the SMO 180-a can communicate with components configured according to the 4G RAN (e.g., via the O1 interface). Additionally or alternatively, in some implementations, the SMO 180-a may communicate directly with one or more RU 170-a via the O1 interface. The SMO 180-a may also include a non-RT RIC 175-a configured to support the functionality of the SMO 180-a.

[0107] The non-RT RIC 175-a can be configured to include logical functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) or machine learning (ML) workflows (including model training and updates, or policy-based guidance of applications / features in the near-RT RIC 175-b). The non-RT RIC 175-a can be coupled to or communicate with the near-RT RIC 175-b (e.g., via the A1 interface). The near-RT RIC 175-b can be configured to include logical functions that enable near real-time control and optimization of RAN elements and resources via data collection and actions on an interface (e.g., via the E2 interface) connecting one or more CU 160-a, one or more DU 165-a, or both, and the O-eNB 210 to the near-RT RIC 175-b.

[0108] In some examples, to generate AI / ML models to be deployed in a near-RT RIC 175-b, a non-RT RIC 175-a may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 175-b and can be received from non-network data sources or network functions at the SMO 180-a or non-RT RIC 175-a. In some examples, a non-RT RIC 175-a or near-RT RIC 175-b may be configured to tune RAN behavior or performance. For example, a non-RT RIC 175-a may monitor long-term trends and patterns in performance and employ AI or ML models to perform corrective actions via the SMO 180-a (e.g., via O1 reconfiguration) or via the generation of RAN management policies such as the A1 policy.

[0109] In some examples of network architecture 200, network entity 105 may use the AMF proxy function to provide connectivity between the RAN of a first network operator and remote AMFs of a second network operator. In some cases, the AMF proxy function may be referred to as a transport proxy. When used as a transport proxy, the AMF proxy allows the first network operator to share its RAN deployment with the second network operator, while the second network operator avoids placing any local AMFs. For example, the first network operator's RAN may connect directly to the AMF proxy with an equal number of connections (e.g., communication links and interfaces) to the AMF proxy. The AMF proxy may connect to the AMFs of the first and second network operators via separate connections. That is, the RAN may use different connections or interfaces to connect to each corresponding AMF via the AMF proxy.

[0110] When sending messages, the RAN can send messages for each AMF via an AMF agent on the appropriate connection or interface between the RAN and the AMF. The AMF agent can receive messages, and based on the connection or interface on which the AMF agent receives the message and the target agent endpoint on which the message is directed, the AMF agent can forward the message to the correct AMF. Therefore, using the AMF agent function can lead to reduced latency and improved communication efficiency. Furthermore, when RAN sharing is performed via the AMF agent, network architecture 200 can support one or more CUs 160-a communicating with the core networks 130 of different network operators (e.g., a first network operator and a second network operator). See also... Figure 3 – Figure 5 Additional description of this type of technology that uses AMF agents.

[0111] Figure 3An example of a wireless communication system 300 supporting RAN sharing using a transport proxy function according to one or more aspects of this disclosure is shown. In some examples, the wireless communication system 300 may implement, or be implemented by, wireless communication system 100 or network architecture 200. For example, wireless communication system 300 may include UE 115-a, UE 115-b, network entity 105-a, core network 130-b, and core network 130-c, which may be referenced herein. Figure 1 and Figure 2 Examples of the corresponding devices described herein. UE 115-a, UE 115-b, network entity 105-a, core network 130-b, and core network 130-c can communicate via communication links 125 (e.g., communication links 125-a, 125-b, 125-c, 125-d, 125-e, 125-f, 125-g, and 125-h), which may be referenced herein. Figure 1 Examples of the described communication links. Communication link 125 can be an example of a Uu link, a side link, a backhaul link, a D2D link, or some other type of communication link 125.

[0112] In the wireless communication system 300, wireless devices can subscribe to or be served by a network operator. A network operator can be an operator or service provider that can provide cellular or wireless services (e.g., data communications) to wireless devices (e.g., UE 115, network entity 105). For example, UE 115-a, network entity 105-a, and core network 130-b can be operated by a first network operator 305 (e.g., configured to operate with the first network operator), while UE 115-b and core network 130-c can be operated by a second network operator 310 (e.g., configured to operate with the second network operator). Furthermore, a network operator can establish one or more RANs to provide support for UE 115 subscribed to or operated by a given network operator. For example, the first network operator 305 can establish RAN 315 including network entity 105-a.

[0113] In some cases, RAN 315 can be shared between different operators (e.g., in a Multi-Operator Core Network (MOCN) architecture). That is, a first network operator 305 can share RAN 315 with a second network operator 310 (e.g., and network entity 105-a included in RAN 315). For example, UE 115-b of the second network operator 310 can be within the coverage area of ​​RAN 315 and outside the coverage area of ​​the RAN used by the second network operator 310. In some cases, RAN 315 can be shared with the second network operator 310, allowing UE 115-b of the second network operator 310 to connect to the RAN 315 of the first network operator 305. In some examples, this can be referred to as roaming, where a device connects to a network operator different from its own. During network sharing, network entity 105-a of RAN 315 can establish and connect with UE 115-a of the first network operator 305 via communication link 125-a, and with UE 115-b of the second network operator 310 via communication link 125-b. Therefore, both the first network operator 305 and the second network operator 310 can connect to and communicate with network entity 105-a. Furthermore, network entity 105-a can independently connect to the core network 130-b of the first network operator 305 and the core network 130-c of the second network operator 310.

[0114] In some examples, network entity 105-a in RAN 315 of first network operator 305 can send a message indicating each network operator among the network operators supported by RAN 315. This message can be a broadcast message and can include the Public Land Mobile Network (PLMN) ID of each network operator that RAN 315 can connect to. In some examples, UE 115 can receive broadcast messages even if it is using a different network operator than network entity 105-a. For example, UE 115-b of second network operator 310 can receive a broadcast message from network entity 105-a of first network operator 305, which can indicate that network entity 105-a can connect to core network 130-c of second network operator 310. UE 115-b can then establish a communication link 125-b and send one or more messages to RAN 315 of the first network operator intended for use with core network 130-c of the second network operator. In one or more messages sent to network entity 105-a, UE 115-b may include the PLMN of core network 130-c to instruct network entity 105-a to route one or more messages to the core network 130-c of the second network operator.

[0115] In some cases, RAN 315 and core network 130 of different network operators (e.g., first network operator 305 and second network operator 310) can be connected using a Gateway Core Network (GWCN) to share RAN 315. The GWCN may include a gateway MME that connects core network 130 to network entity 105-a in RAN 315. Therefore, the gateway MME can declare the PLMN ID of the core network 130 it is connected to and send it to RAN 315, allowing RAN 315 to determine which network operator core networks 130 (e.g., core networks 130-b and 130-c) network entity 105 can communicate with. Furthermore, the gateway MME can also know any shared PLMN IDs, and thus can be able to forward messages to the corresponding core network 130.

[0116] exist Figure 3 In this configuration, RAN 315 can connect to core network 130 via AMFs (e.g., local AMF 320 and remote AMF 330). For example, UE 115-a of the first network operator 305 can communicate with RAN 315 and its corresponding network entity 105-a of the first network operator 305 via communication link 125-a, and network entity 105-a of RAN 315 can communicate with local AMF 320 of the first network operator 305 via communication link 125-c. Furthermore, local AMF 320 of the first network operator 305 can communicate with core network 130-b of the first network operator 305 via communication link 125-d. Therefore, UE 115-a can send messages to core network 130-b of the first network operator 305 via RAN 315 and local AMF 320.

[0117] In some cases, UE 115-b of the second network operator 310 may send messages to RAN 315 of the first network operator 305 that are intended for use in the core network 130-c of the second network operator 310. However, the second network operator 310 may avoid placing any local AMF within the coverage area of ​​RAN 315 of the first network operator 305 (e.g., due to cost constraints, hardware constraints, or both). Without placing any local AMF for the second network operator 310, RAN 315 of the first network operator 305 may be unable to forward messages from UE 115-b of the second network operator 310 to the core network 130-c of the second network operator 310.

[0118] In the wireless communication system 300, RAN 315 can utilize AMF proxy 325 to communicate with a first network operator 305 and a second network operator 310 without requiring any local AMF for the second network operator 310. AMF proxy 325 can be a local AMF of the first network operator 305, which may be different from or the same as local AMF 320. For example, the local AMF of the first network operator 305 may be dedicated to serving as AMF proxy 325, or AMF proxy 325 may be integrated with an existing local AMF of the first network operator 305 (e.g., local AMF 320 may act as AMF proxy 325). In some examples, when AMF proxy 325 may be different from local AMF 320, RAN 315 may avoid establishing a communication link 125-c with the local AMF 320 of the first network operator 305 and may instead establish a communication link 125-e with AMF proxy 325. Then, AMF agent 325 can establish a communication link 125-f with the remote AMF 330 of the second network operator 310 and a communication link 125-g with the local AMF 320 of the first network operator 305. AMF agent 325 can then forward messages from the RAN 315 of the first network operator 305 to the core network 130-c of the second network operator 310.

[0119] Such techniques can utilize existing RAN 315 sharing procedures. For example, in the technique disclosed herein, network entity 105-a of RAN 315 broadcasts the PLMN ID of an operator connected to AMF agent 325 and allows UE 115 to select one of the broadcast PLMNs. However, remote shared PLMNs may not be able to establish connectivity between their AMF and network entity 105. Furthermore, RAN 315 of the first network operator 305 may have interface connections to each AMF of the first network operator 305 (e.g., local AMF 320) and may not be able to connect to remote AMFs (e.g., remote AMF 330). Therefore, AMF agent 325 may send messages to remote AMFs of different operators (e.g., remote AMF 330 of the second network operator 310) because RAN 315 may not be able to do so. AMF agent 325 may receive messages from network entity 105-a that may originate from devices of the first network operator 305 (e.g., UE 115-a) and devices of the second network operator 310 (e.g., UE 115-b). AMF agent 325 may distinguish these messages from each other, and if a message is addressed to the core network 130-c of the second network operator 310, AMF agent 325 may forward such messages to a remote AMF 330 via communication link 125-f, while avoiding processing or decoding the messages.

[0120] Additionally or alternatively, the local AMF 320 may act as an AMF agent 325, and the local AMF 320 may connect directly to the remote AMF 330 (not illustrated). That is, the local AMF 320 may receive messages intended for both the core network 130-b of the first network operator 305 and the core network 130-c of the second network operator 310. In some examples, the local AMF 320 and RAN 315 may send this configuration before establishing communication link 125-c. In some other examples, RAN 315 may be aware that the local AMF 320 may act as an AMF agent 325 when establishing communication link 125-c.

[0121] For example, network entity 105-a may be configured with the IP address of a local AMF 320, and the local AMF 320 may be configured to support a remote PLMN and its corresponding AMF (e.g., remote AMF 330), and may have already initiated a connection with the corresponding AMF. Furthermore, when RAN 315 establishes a communication link 125-c with network entity 105-a, RAN 315 may send a setup request message (e.g., an NGAP SETUP REQUEST message) to the local AMF 320, and RAN 315 may query the connectivity of the remote AMF. In some cases, the query regarding remote AMF connectivity may be specific to the connection between the local AMF 320 of the first network operator 305 and the remote AMF 330 of the second network operator 310. In response to a setup request message, the local AMF 320 can process the setup request and send a reply message (e.g., an NGAP SETUP RESPONSE message), wherein the message may include a list of such supported AMFs if the local AMF 320 is capable of supporting connections to remote AMFs of different operators. If the message includes a query about a specific remote AMF connection (e.g., remote AMF 330) or a specific network operator (e.g., a second network operator 310), the list of supported connections may be limited to the initial query from network entity 105-a. Upon receiving such an indication, RAN 315 can trigger an additional setup request message to be sent to the remote AMF of such indication, wherein the additional setup request message may be routed via the local AMF 320 to the indicated remote AMF (e.g., remote AMF 330) via the communication link 125 between the local AMF 320 and the remote AMF 330.

[0122] In some examples, the interface used for the connection between the local AMF 320 and the remote AMF 330 can be a secure transport communication link 125 that includes an IP connection or Stream Send Control Protocol (STCP) / IP. Where STCP is available, the remote AMF 330 can send messages as if it had a direct communication link with network entity 105-a of RAN 315. Furthermore, to support such connections between AMFs of different network operators, network operators may have to collaborate to establish connectivity across security domains. For example, inter-operator connections (e.g., communication link 125 between the local AMF 320 and the remote AMF 330) can use existing interfaces (e.g., N32 interfaces) between different PLMNs or different network operators' Security Edge Protection Agents (SEPPs). The architecture of the communication link can also assume a shared secure direct connection between RAN 315 and the User Plane Function (UPF) of a second network operator 310 for service processing.

[0123] Therefore, using the AMF proxy 325, it is possible to share RAN 315 among different operators. In some examples, the architecture can be extended to share RAN 315 among more than two network operators. For example, a first network operator 305 and a third network operator can have local AMFs placed within the coverage area of ​​RAN 315 and can be able to share RAN 315 using conventional techniques. However, in some cases, the local AMF 320 of the first network operator 305 can be connected to the remote AMF 330 of the second network operator 310, and the local AMF of the third network operator can be connected to the remote AMF of a fourth network architecture, where the local AMFs of the first and third network operators can act as AMF proxies 325 for RAN 315. Therefore, using the AMF proxy, communication efficiency in the wireless communication system 300 can be increased because more operators can be able to share RAN 315, regardless of hardware constraints within the coverage area of ​​RAN 315. See also Figure 4 – Figure 5 The description provides further details on using AMF Proxy 325 and using AMF Proxy 325 as a transport proxy.

[0124] Figure 4 An example of a network architecture 400 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Network architecture 400 may exemplify one or more aspects for implementing wireless communication system 100 or wireless communication system 300. For example, the network architecture may include RAN 405, AMF agent 420, first AMF 435, and second AMF 445, which may be examples of the devices described herein. First RAN 405, AMF agent 420, first AMF 435, and second AMF 445 may also communicate with each other using communication links (e.g., communication link 410, communication link 415, communication link 430, and communication link 440). In some examples, the communication links may use interfaces for communicating with RAN 405, AMF agent 420, first AMF 435, and second AMF 445, which may terminate at interface termination points 425 (e.g., interface termination points 425-a, 425-b, 425-c, and 425-d).

[0125] In some examples, AMF agent 420 may be referred to as a transport agent. When AMF agent 420 is used as a transport agent, RAN 405 (which may subscribe to or be served by the first network operator) can establish a first communication link (e.g., consisting of communication link 410 and communication link 430) between RAN 405 and the first AMF 435 of the first network operator via AMF agent 420 using a first interface. In some cases, communication link 410 may be a first instance of the first interface, and communication link 430 may be a second instance of the first interface, and together they may constitute the complete first interface. RAN 405 can also establish a second communication link (e.g., consisting of communication link 415 and communication link 440) between RAN 405 and the second AMF 445 of the second network operator via AMF agent 420 using a second interface. In other words, RAN 405 may have two connections to AMF agent 420 (e.g., communication link 410 and communication link 415), one connection for each AMF (e.g., first AMF 435 and second AMF 445). The first communication link and the first interface may terminate at interface termination point 425-a at RAN 405 and interface termination point 425-c at the first AMF 435, and the second communication link and the second interface may terminate at interface termination point 425-b at RAN 405 and interface termination point 425-d at the second AMF 445. In some cases, interface termination point 425 may also be associated with the endpoint address of the corresponding interface. That is, based on the interface on which messages are received, AMF agent 420 may use the endpoint address corresponding to interface termination point 425 to forward messages.

[0126] Therefore, the communication links and corresponding interfaces can be independent of each other, and the AMF agent 420 can establish separate communication links and interfaces for each RAN 405 and AMF (e.g., first AMF 435 or second AMF 445) pair. Furthermore, using the first and second interfaces, the AMF agent 420 can route messages from RAN 405 to the first AMF 435 or the second AMF 445 based on the target agent endpoint address to which the message from RAN 405 is directed. Thus, the AMF agent 420 can send messages to the target endpoint address of the interface used to receive messages from RAN 405. The target agent endpoint address can be the IP address of the AMF agent 420 or a combination of IP address and IP port. In some cases, RAN 405 and AMF agent 420 can be initialized using a set of mappings between target agent endpoint addresses and the first AMF 435 and the second AMF 445. Additionally, each network operator's core network 130 can be configured with this set of agent endpoint addresses and mappings to one or more source RANs.

[0127] In some examples, a set of RANs may exist in a network architecture 400 including RAN 405, where each RAN in the set of RANs may be configured with a corresponding communication link and interface for each corresponding AMF in a set of AMFs (including first AMF 435 and second AMF 445). Therefore, the number of communication links and interfaces may be based on the number of RAN-AMF pairs (e.g., RAN 405 to first AMF 435 or RAN 405 to second AMF 445). Furthermore, as described, each pair may have different communication links and interfaces, so the AMF agent 420 may forward messages based on the communication links and interfaces used to receive messages. Therefore, the AMF agent 420 may be memoryless because it avoids creating any form of mapping between RANs (e.g., RAN 405) and AMFs (e.g., first AMF 435 and second AMF 445) within the network architecture 400. In some cases, because the AMF agent 420 can avoid decoding or processing messages, it can use the target agent endpoint address and the interface for receiving messages to forward messages. In some examples, the RAN 405 can send messages to the AMF agent 420 as if it were sending messages directly to the AMF. Additionally or alternatively, the RAN 405 may be configured with an identifier (ID) for each AMF and Public Land Mobile Network (PLMN) and a corresponding transport address (e.g., the target agent endpoint address). In some cases, the network operator's core network 130 may configure a mapping of this information, or the RAN 405 may generate the mapping when initializing connections with the first AMF 435 and the second AMF 445.

[0128] In some examples, the AMF agent 420 used may be a dedicated AMF without services (e.g., no UE115 can transmit messages to this AMF), or the AMF agent 420 may be a local AMF of the first network operator or integrated with a local AMF (e.g., the first AMF 435 may act as the AMF agent 420). When the first AMF 435 can act as the AMF agent 420, the AMF agent 420 may be referred to as the integrated AMF agent 420. Furthermore, any reference elsewhere in this document to the AMF agent 420 may refer to the dedicated AMF used for the AMF agent 420 or the first AMF 435 integrated with that AMF. In the case where the first AMF 435 acts as the AMF agent 420, the first AMF 435 may connect to the RAN 405 using a first interface via a first communication link and a second interface via a second communication link. The first interface may then terminate at both the RAN 405 and the first AMF 435. Furthermore, instead of routing the second communication link and the second interface through a separate AMF that acts as an AMF agent 420, the second communication link and the second interface can be routed through a first AMF that can act as an AMF agent 420.

[0129] In some other examples, regardless of whether AMF agent 420 is within a dedicated AMF of the first AMF 435, RAN 405 can select which AMF to which RAN 405 can transmit the message based on the UE 115 that transmitted the initial message. For example, if RAN 405 receives a message from UE 115 of the first network operator, RAN 405 can determine and select to transmit the message to the first AMF 435 on the first interface. Therefore, if RAN 405 receives a message from UE 115 of the second network operator, RAN 405 can determine and select to transmit the message to the second AMF 445 on the second interface. That is, the network operator of UE 115 can determine which interface RAN 405 should use and which AMF (e.g., the first AMF 435 or the second AMF 445) RAN 405 should transmit the message to via AMF agent 420.

[0130] In some other cases, AMF agent 420 may also receive messages for RAN 405 from a first AMF 435, a second AMF 445, or both. Similar to sending messages from RAN 405, AMF agent 420 may use the same interface used to receive messages from the first AMF 435 or the second AMF 445 to route messages destined for RAN 405 to the endpoint address of RAN 405. For example, AMF agent 420 may receive a message from the first AMF 435 via a first interface (e.g., using communication link 430), and AMF agent 420 may forward or send the message to RAN 405 using the same interface (e.g., via communication link 410) based on the target agent endpoint address used by the first AMF 435 when the message was sent to AMF agent 420. When forwarding messages from the first AMF 435 or the second AMF 445 to the RAN 405 (and vice versa), the AMF agent 420 can also avoid processing, decoding, or manipulating the message, or even inspecting the message content or any part of the message header. Therefore, using the AMF agent 420 as a transport agent can improve communication efficiency between devices from different network operators. (See reference...) Figure 5 The description provides a further description of this type of technology that uses the AMF Agent 420 as a transport agent, as described herein.

[0131] Figure 5 An example of a process flow 500 supporting the use of a transport agent function in RAN sharing according to one or more aspects of this disclosure is shown. In some examples, process flow 500 may be implemented by or by wireless communication system 100 or wireless communication system 300. For example, process flow 500 may include a RAN 505 of a first network operator, an AMF agent 510, a first AMF 515 of the first network operator, and a second AMF 520 of a second network operator, which may be referenced herein. Figure 1 – Figure 3 An example of the device described.

[0132] In the following description of process flow 500, the operations between RAN 505, AMF agent 510, first AMF 515, and second AMF 520 may be performed in different order or at different times. Some operations may also be excluded from process flow 500, or other operations may be added. Although RAN 505, AMF agent 510, first AMF 515, and second AMF 520 are shown as performing the operations of process flow 500, some aspects of some operations may also be performed by one or more other radio devices.

[0133] At 525-a, AMF agent 510 may establish a first communication link between the first network operator's RAN 505 and the first AMF 515 of the first network operator (e.g., illustrated by the black circle on the first communication link at 525-a). At 525-b, AMF agent 510 may establish a second communication link between the first network operator's RAN 505 and the second network operator's second AMF 520. In some cases, AMF agent 510 may establish a set of communication links, including the first and second communication links, between a set of RANs including RAN 505 and a set of AMFs including the first AMF 515 and the second AMF 520. In some other cases, at 525-a, AMF agent 510 may establish a first communication link directly between RAN 505 and the first AMF 515, and at 525-b, AMF agent 510 may establish a second communication link between RAN 505 and the second AMF 520 via the first AMF 515, based on the first AMF 515 acting as AMF agent 510. Furthermore, the first communication link may terminate at RAN 505 and the first AMF 515, and the second communication link may terminate at RAN 505 and the second AMF 520. Each communication link between RAN 505 and the first AMF 515 or the second AMF 520 may include two separate sub-communication links, wherein the first sub-communication link may be between RAN 505 and AMF agent 510, and the second sub-communication link may be between AMF agent 510 and the first AMF 515 or the second AMF 520.

[0134] At 530, AMF agent 510 may receive a message from a source agent endpoint address corresponding to RAN 505 via a first or second communication link, the message being directed to a target agent endpoint address mapped to a first AMF 515 or a second AMF 520. In some cases, AMF agent 510 may avoid decoding messages from RAN 505. Therefore, at 535, AMF agent 510 may send a message from RAN 505 to the first AMF 515 via the first communication link, or to the second AMF 520 via the second communication link. AMF agent 510 may send messages to the first AMF 515 or the second AMF 520 based on a mapping between a set of target agent endpoint addresses and one or more source agent endpoint addresses (including the source agent endpoint addresses) of RAN 505, wherein the set of target agent endpoint addresses includes these target agent endpoint addresses.

[0135] At 540-a or 540-b, based on the destination proxy endpoint address of the message from AMF proxy 510 and the source endpoint address of the message from the AMF proxy, the first AMF 515 or the second AMF 520 can decode the message from RAN 505. In some cases, the first AMF 515 or the second AMF 520 can detect the identity of the originating RAN 505 based on the mapping between RAN 505 and the source proxy endpoint address or the destination proxy endpoint address of the message.

[0136] At 545, in some cases, AMF agent 510 may receive a second message from first AMF 515 via a first communication link or from second AMF 520 via a second communication link. The second message may indicate a second target agent endpoint address corresponding to RAN 505. Then, at 550, AMF agent 510 may send the second message to RAN 505 based on the second target endpoint address of RAN 505 via the first communication link or via the second communication link. In some cases, RAN 505 may decode the second message, or RAN 505 may avoid decoding the second message and send the second message to a radio device (e.g., network entity 105 or UE 115).

[0137] Figure 6 A block diagram 600 of a RAN-shared device 605 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Device 605 may be an example of various aspects of an AMF agent as described herein. Device 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0138] Receiver 610 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions). The information may be transmitted to other components of device 605. Receiver 610 may utilize a single antenna or a group of multiple antennas.

[0139] Transmitter 615 may provide components for transmitting signals generated by other components of device 605. For example, transmitter 615 may transmit information associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 615 may be co-located with receiver 610 in a transceiver module. Transmitter 615 may utilize a single antenna or a group of multiple antennas.

[0140] The communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of RAN sharing using the transport agent function as described herein. For example, the communication manager 620, receiver 610, transmitter 615, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0141] In some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs, or other programmable logic devices, microcontrollers, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0142] Additionally or alternatively, in some examples, the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 620, receiver 610, transmitter 615, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0143] In some examples, the communication manager 620 may be configured to use or otherwise cooperate with the receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 620 may receive information from the receiver 610, transmit information to the transmitter 615, or be integrated in combination with the receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0144] According to the examples disclosed herein, the communication manager 620 may support wireless communication at an AMF agent. For example, the communication manager 620 may be capable of, configured to, or operable to support components for establishing a first communication link via an AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator. The communication manager 620 may be capable of, configured to, or operable to support components for establishing a second communication link via an AMF agent between a RAN associated with a first network operator and a second AMF associated with a second network operator. The communication manager 620 may be capable of, configured to, or operable to support components for receiving messages via the first or second communication link from a source agent endpoint address corresponding to a RAN, the messages being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator. The communication manager 620 is capable of, configured to, or operable to support components for sending messages from a RAN associated with a first network operator to a first AMF associated with the first network operator via a first communication link or sending messages from a RAN associated with the first network operator to a second AMF associated with a second network operator via a second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0145] By including or configuring a communication manager 620 according to an example as described herein, device 605 (e.g., controlling receiver 610, transmitter 615, communication manager 620, or a combination thereof or a processor otherwise coupled to them) can support techniques for using an AMF agent to communicate with multiple network operators to reduce processing and utilize communication resources more efficiently.

[0146] Figure 7 A block diagram 700 of a RAN-shared device 705 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Device 705 may be an example of aspects of a device 605 or an AMF agent as described herein. Device 705 may include a receiver 710, a transmitter 715, and a communication manager 720. Device 705 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0147] Receiver 710 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions). The information may be transmitted to other components of device 705. Receiver 710 may utilize a single antenna or a group of multiple antennas.

[0148] Transmitter 715 may provide components for transmitting signals generated by other components of device 705. For example, transmitter 715 may transmit information associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 715 may be co-located with receiver 710 in a transceiver module. Transmitter 715 may utilize a single antenna or a group of multiple antennas.

[0149] Device 705 or its various components may be examples of parts used to perform various aspects of RAN sharing using the transport agent function as described herein. For example, communication manager 720 may include AMF agent communication link component 725, message receiver 730, message transmitter 735, or any combination thereof. Communication manager 720 may be examples of aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to use or otherwise cooperate with receiver 710, transmitter 715, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or be integrated in combination with receiver 710, transmitter 715, or both to acquire information, output information, or perform various other operations as described herein.

[0150] According to the examples disclosed herein, the communication manager 720 can support wireless communication at an AMF agent. The AMF agent communication link component 725 is capable of, configured to, or operable to support components for establishing a first communication link via the AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator. The AMF agent communication link component 725 is capable of, configured to, or operable to support components for establishing a second communication link via the AMF agent between a RAN associated with a first network operator and a second AMF associated with a second network operator. The message receiver 730 is capable of, configured to, or operable to support components for receiving messages via the first or second communication link from a source agent endpoint address corresponding to a RAN, the messages being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator. The message transmitter 735 is capable of, configured to, or operable to support components for sending messages from a RAN associated with a first network operator to a first AMF associated with the first network operator via a first communication link or to a second AMF associated with a second network operator via a second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0151] Figure 8 A block diagram 800 is shown of a communication manager 820 supporting RAN sharing using transport agent functionality according to one or more aspects of this disclosure. Communication manager 820 may be an example of aspects of communication manager 620, communication manager 720, or both as described herein. Communication manager 820 or its various components may be examples of parts for performing various aspects of RAN sharing using transport agent functionality as described herein. For example, communication manager 820 may include AMF agent communication link component 825, message receiver 830, message transmitter 835, integrated AMF agent communication link component 840, AMF communication link component 845, decoding component 850, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0152] According to the examples disclosed herein, the communication manager 820 may support wireless communication at an AMF agent. The AMF agent communication link component 825 is capable of, configured to, or operable to support components for establishing a first communication link via the AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator. In some examples, the AMF agent communication link component 825 is capable of, configured to, or operable to support components for establishing a second communication link via the AMF agent between a RAN associated with a first network operator and a second AMF associated with a second network operator. The message receiver 830 is capable of, configured to, or operable to support components for receiving messages via the first or second communication link from a source agent endpoint address corresponding to a RAN, the messages being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator. The message transmitter 835 is capable of, configured to, or operable to support components for sending messages from a RAN associated with a first network operator to a first AMF associated with the first network operator via a first communication link or via a second communication link to a second AMF associated with a second network operator, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0153] In some examples, the AMF agent communication link component 825 is capable of, configured to, or operable to support components for establishing a set of multiple communication links between a set of multiple RANs and a set of multiple AMFs via an AMF agent, wherein each of the multiple communication links is between a corresponding RAN in the set of multiple RANs and a corresponding AMF in the set of multiple AMFs, and the set of multiple communication links includes a first communication link and a second communication link.

[0154] In some examples, the integrated AMF agent communication link component 840 is capable of, configured to, or operable to support components for establishing a first communication link directly between the RAN and a first AMF associated with a first network operator. In some examples, the AMF communication link component 845 is capable of, configured to, or operable to support components for establishing a second communication link via the first AMF between the RAN and a second AMF associated with a second network operator, wherein the first AMF acts as an AMF agent.

[0155] In some examples, to support message reception from the RAN via a first or second communication link, the decoding component 850 is capable of, configured to, or operable to support components for avoiding decoding messages from the RAN. In some examples, to support message reception from the RAN via a first or second communication link, the message transmitter 835 is capable of, configured to, or operable to support components for sending messages to a first AMF via the first communication link or to a second AMF via the second communication link using one or more source agent endpoint addresses, wherein the one or more source agent endpoint addresses correspond to the RAN.

[0156] In some examples, message receiver 830 is capable of, configured to, or operable to support components for receiving a second message for the RAN from a second AMF associated with a first network operator via a first communication link or via a second communication link from a first AMF, the second message being directed to a second target agent endpoint address corresponding to the RAN. In some examples, message sender 835 is capable of, configured to, or operable to support components for sending a second message to the RAN via the first communication link or the second communication link based on the second target agent endpoint address corresponding to the RAN.

[0157] In some examples, the first communication link terminates at a RAN associated with the first network operator and a first AMF associated with the first network operator, and the second communication link terminates at a RAN associated with the first network operator and a second AMF associated with the second network operator.

[0158] Figure 9 A diagram of a system 900 including device 905 supporting RAN sharing using a transport agent function, according to one or more aspects of this disclosure, is shown. Device 905 may be an example of device 605, device 705, or an AMF agent as described herein, or may include components thereof. Device 905 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 920, transceiver 910, antenna 915, memory 925, code 930, and processor 935. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 940).

[0159] In some cases, device 905 may include a single antenna 915. However, in other cases, device 905 may have more than one antenna 915, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 910 may communicate bidirectionally via one or more antennas 915 as described herein, a wired link, or a wireless link. For example, transceiver 910 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 910 may also include a modem for: modulating packets, providing modulated packets to one or more antennas 915 for transmission, and demodulating packets received from one or more antennas 915. Transceiver 910, or transceiver 910 and one or more antennas 915, may be an example of transmitter 615, transmitter 715, receiver 610, receiver 710, or any combination thereof or components thereof as described herein.

[0160] Memory 925 may include RAM and ROM. Memory 925 may store computer-readable, computer-executable code 930, including instructions that, when executed by processor 935, cause device 905 to perform the various functions described herein. Code 930 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 930 may not be directly executable by processor 935, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, memory 925 may also contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0161] Processor 935 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 935 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 935. Processor 935 may be configured to execute computer-readable instructions stored in memory (e.g., memory 925) to cause device 905 to perform various functions (e.g., supporting RAN-shared functions or tasks using transport agent functions). For example, device 905 or components of device 905 may include processor 935 and memory 925 coupled to or coupled to processor 935, processor 935 and memory 925 being configured to perform the various functions described herein.

[0162] According to the examples disclosed herein, the communication manager 920 may support wireless communication at an AMF agent. For example, the communication manager 920 may be capable of, configured to, or operable to support components for establishing a first communication link via an AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator. The communication manager 920 may be capable of, configured to, or operable to support components for establishing a second communication link via an AMF agent between a RAN associated with a first network operator and a second AMF associated with a second network operator. The communication manager 920 may be capable of, configured to, or operable to support components for receiving messages via the first or second communication link from a source agent endpoint address corresponding to a RAN, the messages being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator. The communication manager 920 is capable of, configured to, or operable to support components for sending messages from a RAN associated with a first network operator to a first AMF associated with the first network operator via a first communication link or sending messages from a RAN associated with the first network operator to a second AMF associated with a second network operator via a second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target endpoint address.

[0163] By including or configuring a communication manager 920 according to an example as described herein, device 905 can support techniques for using an AMF agent to communicate with multiple network operators for improved communication reliability, improved user experience associated with reduced processing, more efficient use of communication resources, and improved coordination between devices.

[0164] In some examples, the communication manager 920 may be configured to use or otherwise coordinate with the transceiver 910, one or more antennas 915, or any combination thereof to perform various operations (e.g., receiving, monitoring, transmitting). Although the communication manager 920 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 920 may be supported or performed by the processor 935, memory 925, code 930, or any combination thereof. For example, code 930 may include instructions executable by the processor 935 to cause the device 905 to perform various aspects of RAN sharing using the transport agent function as described herein, or the processor 935 and memory 925 may be otherwise configured to perform or support such operations.

[0165] Figure 10A block diagram 1000 of a RAN-shared device 1005 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Device 1005 may be an example of aspects of network entity 105 as described herein. Device 1005 may include a receiver 1010, a transmitter 1015, and a communication manager 1020. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0166] Receiver 1010 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1005. In some examples, receiver 1010 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1010 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0167] Transmitter 1015 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1005. For example, transmitter 1015 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1015 and receiver 1010 may be co-located in a transceiver, which may include or be coupled to a modem.

[0168] The communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of RAN sharing using the transport agent function as described herein. For example, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0169] In some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs, or other programmable logic devices, microcontrollers, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0170] Additionally or alternatively, in some examples, the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1020, receiver 1010, transmitter 1015, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0171] In some examples, the communication manager 1020 may be configured to use or otherwise cooperate with the receiver 1010, transmitter 1015, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1020 may receive information from the receiver 1010, transmit information to the transmitter 1015, or be integrated with the receiver 1010, transmitter 1015, or both to acquire information, output information, or perform various other operations as described herein.

[0172] According to the examples disclosed herein, the communication manager 1020 may support wireless communication at a RAN associated with a first network operator. For example, the communication manager 1020 may be capable of, configured to, or operable to support components for establishing a first communication link between first AMFs associated with a first network operator via an AMF agent. The communication manager 1020 may be capable of, configured to, or operable to support components for establishing a second communication link between second AMFs associated with a second network operator via an AMF agent. The communication manager 1020 may be capable of, configured to, or operable to support components for sending a message for a first AMF to an AMF agent via the first communication link or a message for a second AMF to an AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses corresponding to the first and second AMFs, the plurality of target agent endpoint addresses corresponding to the first and second AMFs.

[0173] By including or configuring a communication manager 1020 according to an example as described herein, device 1005 (e.g., a processor that controls receiver 1010, transmitter 1015, communication manager 1020, or a combination thereof, or otherwise coupled to them) can support techniques for using an AMF agent to communicate with multiple network operators to reduce processing and utilize communication resources more efficiently.

[0174] Figure 11 A block diagram 1100 of a RAN-shared device 1105 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Device 1105 may be an example of aspects of device 1005 or network entity 105 as described herein. Device 1105 may include a receiver 1110, a transmitter 1115, and a communication manager 1120. Device 1105 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0175] Receiver 1110 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 1105. In some examples, receiver 1110 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 1110 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0176] Transmitter 1115 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 1105. For example, transmitter 1115 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 1115 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 1115 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 1115 and receiver 1110 may be co-located in a transceiver, which may include or be coupled to a modem.

[0177] Device 1105 or its various components may be examples of parts used to perform various aspects of RAN sharing using the transport agent function as described herein. For example, communication manager 1120 may include AMF agent communication link manager 1125, message transmitter 1130, or any combination thereof. Communication manager 1120 may be examples of aspects of communication manager 1020 as described herein. In some examples, communication manager 1120 or its various components may be configured to use or otherwise cooperate with receiver 1110, transmitter 1115, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1120 may receive information from receiver 1110, transmit information to transmitter 1115, or be integrated in combination with receiver 1110, transmitter 1115, or both to acquire information, output information, or perform various other operations as described herein.

[0178] According to the examples disclosed herein, communication manager 1120 can support wireless communication at a RAN associated with a first network operator. AMF agent communication link manager 1125 is capable of, configured to, or operable to support components for establishing a first communication link between first AMFs associated with the first network operator via an AMF agent. AMF agent communication link manager 1125 is capable of, configured to, or operable to support components for establishing a second communication link between second AMFs associated with a second network operator via an AMF agent. Message transmitter 1130 is capable of, configured to, or operable to support components for sending messages for the first AMF to an AMF agent via the first communication link or for the second AMF to an AMF agent via the second communication link, the messages being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses corresponding to the first and second AMFs, the plurality of target agent endpoint addresses corresponding to the first and second AMFs.

[0179] Figure 12 A block diagram 1200 is shown of a communication manager 1220 supporting RAN sharing using transport agent functionality according to one or more aspects of this disclosure. Communication manager 1220 may be an example of aspects of communication manager 1020, communication manager 1120, or both as described herein. Communication manager 1220 or its various components may be examples of components for performing various aspects of RAN sharing using transport agent functionality as described herein. For example, communication manager 1220 may include AMF agent communication link manager 1225, message sender 1230, integrated AMF agent communication link manager 1235, AMF communication link manager 1240, message receiver 1245, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses), and this communication may include communication within protocol layers of a protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0180] According to the examples disclosed herein, communication manager 1220 may support wireless communication at a RAN associated with a first network operator. AMF agent communication link manager 1225 is capable of, configured to, or operable to support components for establishing a first communication link between first AMFs associated with a first network operator via an AMF agent. In some examples, AMF agent communication link manager 1225 is capable of, configured to, or operable to support components for establishing a second communication link between second AMFs associated with a second network operator via an AMF agent. Message sender 1230 is capable of, configured to, or operable to support components for sending messages for a first AMF to an AMF agent via a first communication link or for a second AMF to an AMF agent via a second communication link, the messages being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses corresponding to the first and second AMFs, the plurality of target agent endpoint addresses corresponding to the first and second AMFs.

[0181] In some examples, the AMF agent communication link manager 1225 is capable of, configured to, or operable to support components for establishing a set of multiple communication links between a set of multiple AMFs and a set of multiple RANs via an AMF agent, wherein each of the multiple communication links is between a corresponding RAN in the set of multiple RANs and a corresponding AMF in the set of multiple AMFs, and the set of multiple communication links includes a first communication link and a second communication link.

[0182] In some examples, the integrated AMF agent communication link manager 1235 is capable of, configured to, or operable to support components for establishing a first communication link directly between the RAN and the first AMF. In some examples, the AMF communication link manager 1240 is capable of, configured to, or operable to support components for establishing a second communication link between a second AMF and the RAN via the first AMF, wherein the first AMF acts as an AMF agent.

[0183] In some examples, message receiver 1245 is capable of, configured to, or operable to support components for receiving a second message from a first AMF via a first communication link or from a second AMF via a second communication link, the second message being directed to a second target agent endpoint address corresponding to the RAN.

[0184] In some examples, both the first and second communication links terminate at the RAN.

[0185] Figure 13A diagram of a system 1300 including device 1305 supporting RAN sharing using transport proxy functionality, according to one or more aspects of this disclosure, is shown. Device 1305 may be an example of device 1005, device 1105, or network entity 105 as described herein, or a component including such devices. Device 1305 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof, and such communication may include communication via one or more wired interfaces, one or more wireless interfaces, or any combination thereof. Device 1305 may include components supporting output and acquisition of communication, such as a communication manager 1320, transceiver 1310, antenna 1315, memory 1325, code 1330, and processor 1335. These components may communicate electronically or otherwise (e.g., operative ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 1340).

[0186] Transceiver 1310 may support bidirectional communication via a wired link, a wireless link, or both, as described herein. In some examples, transceiver 1310 may include a wired transceiver and may communicate bidirectionally with another wired transceiver. Additionally or alternatively, in some examples, transceiver 1310 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, device 1305 may include one or more antennas 1315 that may be capable of (e.g., concurrently) transmitting or receiving wireless transmissions. Transceiver 1310 may also include a modem for: modulating a signal; providing the modulated signal for transmission (e.g., via one or more antennas 1315, via a wired transmitter); receiving the modulated signal (e.g., from one or more antennas 1315, from a wired receiver); and demodulating the signal. In some embodiments, transceiver 1310 may include one or more interfaces, such as one or more interfaces coupled to one or more antennas 1315 configured to support various receive or acquire operations, or one or more interfaces coupled to one or more antennas 1315 configured to support various transmit or output operations, or combinations thereof. In some embodiments, transceiver 1310 may include one or more processor or memory components or be configured to couple to one or more processor or memory components capable of operating to perform or support operations based on received or acquired information or signals, or to generate information or other signals for transmission or other output, or any combination thereof. In some embodiments, transceiver 1310, or transceiver 1310 and one or more antennas 1315, or transceiver 1310 and one or more antennas 1315 and one or more processor or memory components (e.g., processor 1335 or memory 1325 or both) may be included in a chip or chip assembly mounted in device 1305. In some examples, the transceiver may be able to operate to support communication via one or more communication links (e.g., communication link 125, backhaul communication link 120, midhaul communication link 162, and fronthaul communication link 168).

[0187] Memory 1325 may include RAM and ROM. Memory 1325 may store computer-readable, computer-executable code 1330, including instructions that, when executed by processor 1335, cause device 1305 to perform the various functions described herein. Code 1330 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 1330 may not be directly executable by processor 1335, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, in addition, memory 1325 may also contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0188] Processor 1335 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, ASICs, CPUs, FPGAs, microcontrollers, programmable logic devices, discrete gate or transistor logic units, discrete hardware components, or any combination thereof). In some cases, processor 1335 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 1335. Processor 1335 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1325) to cause device 1305 to perform various functions (e.g., supporting RAN-shared functions or tasks using transport agent functions). For example, device 1305 or components of device 1305 may include processor 1335 and memory 1325 coupled to processor 1335, processor 1335 and memory 1325 being configured to perform the various functions described herein. Processor 1335 may be an example of a cloud computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that can (e.g., by executing code 1330) host functions to perform the functions of device 1305. Processor 1335 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in device 1305, such as in memory 1325. In some implementations, processor 1335 may be a component of a processing system. A processing system generally refers to a system or series of machines or components that receive inputs and process those inputs to produce a set of outputs that can be passed to, for example, other systems or components of device 1305. For example, the processing system of device 1305 may refer to a system that includes various other components or sub-components of device 1305, such as processor 1335, or transceiver 1310, or communication manager 1320, or other components or combinations of components of device 1305. The processing system of device 1305 may interface with other components of device 1305 and may process information received from other components (such as inputs or signals) or output information to other components. For example, a chip or modem of device 1305 may include a processing system and one or more interfaces for outputting information or for receiving information or both. One or more interfaces may be implemented as, or otherwise include, a first interface configured to output information and a second interface configured to receive information, or the same interface configured to both output and receive information, as well as other specific implementations. In some specific implementations, the one or more interfaces may refer to an interface between the processing system of the chip or modem and the transmitter, enabling device 1305 to transmit information output from the chip or modem.Additionally or alternatively, in some embodiments, the one or more interfaces may refer to the interface between the processing system of the chip or modem and the receiver, enabling device 1305 to receive information or signal input, and such information to be transmitted to the processing system. Those skilled in the art will readily recognize that the first interface may also receive information or signal input, and the second interface may also output information or signal output.

[0189] In some examples, bus 1340 may support communication at the protocol layer of the protocol stack (e.g., within a protocol layer). In some examples, bus 1340 may support communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack), which may include communication performed within components of device 1305, or communication performed between different components of device 1305 that may be co-addressable or located in different locations (e.g., where device 1305 may refer to a system in which one or more of communication manager 1320, transceiver 1310, memory 1325, code 1330, and processor 1335 may be located in one of the different components or partitioned between the different components).

[0190] In some examples, the communication manager 1320 can manage (e.g., via one or more wired or wireless backhaul links) various aspects of communication with the core network 130. For example, the communication manager 1320 can manage the transfer of data communication for client devices, such as one or more UEs 115. In some examples, the communication manager 1320 can manage communication with other network entities 105 and may include a controller or scheduler for coordinating with other network entities 105 to control communication with UE 115. In some examples, the communication manager 1320 may support the X2 interface within LTE / LTE-A wireless communication network technology to provide communication between network entities 105.

[0191] According to the examples disclosed herein, the communication manager 1320 may support wireless communication at a RAN associated with a first network operator. For example, the communication manager 1320 may be capable of, configured to, or operable to support components for establishing a first communication link between first AMFs associated with a first network operator via an AMF agent. The communication manager 1320 may be capable of, configured to, or operable to support components for establishing a second communication link between second AMFs associated with a second network operator via an AMF agent. The communication manager 1320 may be capable of, configured to, or operable to support components for sending a message for a first AMF to an AMF agent via the first communication link or a message for a second AMF to an AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent based on a mapping between a plurality of target agent endpoint addresses and one or more source agent addresses corresponding to the first and second AMFs, the plurality of target agent endpoint addresses corresponding to the first and second AMFs.

[0192] By including or configuring a communication manager 1320 according to an example as described herein, device 1305 can support techniques for using an AMF agent to communicate with multiple network operators for improved communication reliability, improved user experience associated with reduced processing, more efficient use of communication resources, and improved coordination between devices.

[0193] In some examples, the communication manager 1320 may be configured to use or otherwise coordinate with the transceiver 1310, one or more antennas 1315 (e.g., where applicable), or any combination thereof to perform various operations (e.g., receive, acquire, monitor, output, transmit). Although the communication manager 1320 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1320 may be supported or performed by the transceiver 1310, processor 1335, memory 1325, code 1330, or any combination thereof. For example, code 1330 may include instructions that can be executed by the processor 1335 to cause the device 1305 to perform various RAN-shared aspects of using the transport agent functionality as described herein, or the processor 1335 and memory 1325 may be otherwise configured to perform or support such operations.

[0194] Figure 14A block diagram 1400 of a RAN-shared device 1405 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Device 1405 may be an example of various aspects of an AMF as described herein. Device 1405 may include a receiver 1410, a transmitter 1415, and a communication manager 1420. Device 1405 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0195] Receiver 1410 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions). The information may be passed to other components of device 1405. Receiver 1410 may utilize a single antenna or a group of multiple antennas.

[0196] Transmitter 1415 may provide components for transmitting signals generated by other components of device 1405. For example, transmitter 1415 may transmit information associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 1415 may be co-located with receiver 1410 in a transceiver module. Transmitter 1415 may utilize a single antenna or a group of multiple antennas.

[0197] The communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of RAN sharing using the transport agent function as described herein. For example, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations thereof, or components thereof, may support methods for performing one or more of the functions described herein.

[0198] In some examples, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include processors, DSPs, CPUs, ASICs, FPGAs, or other programmable logic devices, microcontrollers, discrete gate or transistor logic components, discrete hardware components, or any combination thereof, configured as or otherwise to support components for performing the functions described herein. In some examples, the processor and memory coupled to the processor may be configured to perform one or more of the functions described herein (e.g., by executing instructions stored in memory by the processor).

[0199] Additionally or alternatively, in some examples, the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be implemented in code executed by a processor (e.g., implemented as communication management software or firmware). If implemented in code executed by a processor, the functionality of the communication manager 1420, receiver 1410, transmitter 1415, or various combinations or components thereof may be performed by (e.g., a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or any combination of these or other programmable logic devices configured as or otherwise supporting components for performing the functions described in this disclosure).

[0200] In some examples, the communication manager 1420 may be configured to use or otherwise coordinate with the receiver 1410, transmitter 1415, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 1420 may receive information from the receiver 1410, transmit information to the transmitter 1415, or be integrated in combination with the receiver 1410, transmitter 1415, or both to acquire information, output information, or perform various other operations as described herein.

[0201] According to the examples disclosed herein, the communication manager 1420 can support wireless communication at a first AMF. For example, the communication manager 1420 can be, configured, or operated to support components for establishing a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent. The communication manager 1420 can be, configured, or operated to support components for receiving messages from the RAN via the communication link, directed to a source agent endpoint address corresponding to the RAN and a target agent endpoint address corresponding to the first AMF. The communication manager 1420 can be, configured, or operated to support components for decoding messages from the RAN based on the target agent endpoint address of the message.

[0202] By including or configuring a communication manager 1420 according to an example as described herein, device 1405 (e.g., controlling receiver 1410, transmitter 1415, communication manager 1420, or a combination thereof, or a processor otherwise coupled to them) can support techniques for using an AMF agent to communicate with multiple network operators to reduce processing and utilize communication resources more efficiently.

[0203] Figure 15A block diagram 1500 of a RAN-shared device 1505 supporting the use of a transport agent function according to one or more aspects of this disclosure is shown. Device 1505 may be an example of a device 1405 or an aspect of an AMF as described herein. Device 1505 may include a receiver 1510, a transmitter 1515, and a communication manager 1520. Device 1505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0204] Receiver 1510 may provide components for receiving information (such as packets, user data, control information, or any combination thereof) associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions). The information may be transmitted to other components of device 1505. Receiver 1510 may utilize a single antenna or a group of multiple antennas.

[0205] Transmitter 1515 may provide components for transmitting signals generated by other components of device 1505. For example, transmitter 1515 may transmit information associated with various information channels (e.g., control channels, data channels, information channels shared with RANs using transport proxy functions), such as packets, user data, control information, or any combination thereof. In some examples, transmitter 1515 may be co-located with receiver 1510 in a transceiver module. Transmitter 1515 may utilize a single antenna or a group of multiple antennas.

[0206] Device 1505 or its various components may be examples of parts used to perform various aspects of RAN sharing using the transport agent function as described herein. For example, communication manager 1520 may include AMF agent communication link component 1525, message receiver 1530, decoding component 1535, or any combination thereof. Communication manager 1520 may be examples of aspects of communication manager 1420 as described herein. In some examples, communication manager 1520 or its various components may be configured to use or otherwise cooperate with receiver 1510, transmitter 1515, or both to perform various operations (e.g., receive, acquire, monitor, output, transmit). For example, communication manager 1520 may receive information from receiver 1510, transmit information to transmitter 1515, or be integrated in combination with receiver 1510, transmitter 1515, or both to acquire information, output information, or perform various other operations as described herein.

[0207] According to the examples disclosed herein, the communication manager 1520 can support wireless communication at the first AMF. The AMF agent communication link component 1525 is capable of, configured to, or operable to support components for establishing a communication link between the RAN associated with the first network operator and the first AMF via the AMF agent. The message receiver 1530 is capable of, configured to, or operable to support components for receiving messages from the RAN via the communication link, directed to a source agent endpoint address corresponding to the RAN and a destination agent endpoint address corresponding to the first AMF. The decoding component 1535 is capable of, configured to, or operable to support components for decoding messages from the RAN based on the destination agent endpoint address of the message.

[0208] Figure 16 A block diagram 1600 is shown of a communication manager 1620 supporting RAN sharing using transport agent functionality according to one or more aspects of this disclosure. Communication manager 1620 may be an example of aspects of communication manager 1420, communication manager 1520, or both as described herein. Communication manager 1620 or its various components may be examples of parts for performing various aspects of RAN sharing using transport agent functionality as described herein. For example, communication manager 1620 may include AMF agent communication link component 1625, message receiver 1630, decoding component 1635, message transmitter 1640, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0209] According to the examples disclosed herein, the communication manager 1620 can support wireless communication at the first AMF. The AMF agent communication link component 1625 is capable of, configured to, or operable to support components for establishing a communication link between the RAN associated with the first network operator and the first AMF via the AMF agent. The message receiver 1630 is capable of, configured to, or operable to support components for receiving messages from the RAN via the communication link, directed to a source agent endpoint address corresponding to the RAN and a destination agent endpoint address corresponding to the first AMF. The decoding component 1635 is capable of, configured to, or operable to support components for decoding messages from the RAN based on the destination agent endpoint address of the message.

[0210] In some examples, the AMF agent communication link component 1625 is capable of, configured to, or operable to support components for establishing a set of multiple communication links between a set of multiple RANs and a set of multiple AMFs via an AMF agent, wherein each of the multiple communication links is between a corresponding RAN and an AMF in the set of multiple RANs, and wherein the set of multiple communication links includes the communication link.

[0211] In some examples, to support the establishment of a communication link, the AMF agent communication link component 1625 can be, configured, or operated to support components for establishing a communication link between a RAN associated with a first network operator and a first AMF via an AMF agent, wherein the first AMF is associated with a first network operator or a second network operator.

[0212] In some examples, message sender 1640 is capable of, configured to, or operable to support components for sending a second message for the RAN to an AMF agent via a communication link, the second message being directed to a second target agent endpoint address corresponding to the RAN.

[0213] In some examples, the communication link terminates at the AMF.

[0214] Figure 17 A diagram of a system 1700 including device 1705 supporting RAN sharing using a transport agent function, according to one or more aspects of this disclosure, is shown. Device 1705 may be an example of device 1405, device 1505, or AMF as described herein, or a component including such devices. Device 1705 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 1720, transceiver 1710, antenna 1715, memory 1725, code 1730, and processor 1735. These components may communicate electronically or otherwise (e.g., operatively, communicatively, functionally, electronically, or electrically) via one or more buses (e.g., bus 1740).

[0215] In some cases, device 1705 may include a single antenna 1715. However, in other cases, device 1705 may have more than one antenna 1715, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 1710 may communicate bidirectionally via one or more antennas 1715 as described herein, a wired link, or a wireless link. For example, transceiver 1710 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 1710 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 1715 for transmission; and demodulating packets received from one or more antennas 1715. Transceiver 1710, or transceiver 1710 and one or more antennas 1715, may be an example of transmitter 1415, transmitter 1515, receiver 1410, receiver 1510, or any combination thereof or components thereof as described herein.

[0216] Memory 1725 may include RAM and ROM. Memory 1725 may store computer-readable, computer-executable code 1730, including instructions that, when executed by processor 1735, cause device 1705 to perform the various functions described herein. Code 1730 may be stored in a non-transitory computer-readable medium, such as system memory or another type of memory. In some cases, code 1730 may not be directly executable by processor 1735, but may (e.g., when compiled and executed) cause the computer to perform the functions described herein. In some cases, memory 1725 may also contain a BIOS, which controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0217] Processor 1735 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1735 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1735. Processor 1735 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1725) to cause device 1705 to perform various functions (e.g., supporting RAN-shared functions or tasks using transport agent functions). For example, device 1705 or components of device 1705 may include processor 1735 and memory 1725 coupled to or coupled to processor 1735, processor 1735 and memory 1725 being configured to perform the various functions described herein.

[0218] According to the examples disclosed herein, the communication manager 1720 can support wireless communication at a first AMF. For example, the communication manager 1720 can be, configured, or operated to support components for establishing a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent. The communication manager 1720 can be, configured, or operated to support components for receiving messages from the RAN via the communication link, directed to a source agent endpoint address corresponding to the RAN and a target agent endpoint address corresponding to the first AMF. The communication manager 1720 can be, configured, or operated to support components for decoding messages from the RAN based on the target agent endpoint address of the message.

[0219] By including or configuring a communication manager 1720 according to an example as described herein, device 1705 can support techniques for using an AMF agent to communicate with multiple network operators for improved communication reliability, improved user experience associated with reduced processing, more efficient use of communication resources, and improved coordination between devices.

[0220] In some examples, the communication manager 1720 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise cooperating with transceiver 1710, one or more antennas 1715, or any combination thereof. Although the communication manager 1720 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 1720 may be supported or performed by processor 1735, memory 1725, code 1730, or any combination thereof. For example, code 1730 may include instructions executable by processor 1735 to cause device 1705 to perform various RAN-shared aspects of using the transport agent functionality as described herein, or processor 1735 and memory 1725 may be otherwise configured to perform or support such operations.

[0221] Figure 18 A flowchart illustrating method 1800 for RAN sharing using a transport agent function, according to various aspects of this disclosure, is shown. Operation of method 1800 may be implemented by an AMF agent or its components as described herein. For example, operation of method 1800 may be implemented by, as referenced... Figures 1 to 9 The described AMF agent is used to perform this function. In some examples, the AMF agent can execute a set of instructions to control the functional elements of the AMF agent to perform the described function. Additionally or alternatively, the AMF agent may use dedicated hardware to perform aspects of the described function.

[0222] At 1805, the method may include establishing a first communication link between a RAN associated with a first network operator and a first AMF associated with the first network operator via an AMF agent. Operation of block 1805 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1805 may be provided by reference to [reference needed]. Figure 8 The AMF agent communication link component 825 is described to perform this function.

[0223] At 1810, the method may include establishing a second communication link between a RAN associated with a first network operator and a second AMF associated with a second network operator via an AMF agent. Operation of block 1810 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1810 may be provided by reference to [reference needed]. Figure 8 The AMF agent communication link component 825 is described to perform this function.

[0224] At 1815, the method may include receiving a message via a first or second communication link from a source agent endpoint address corresponding to the RAN, the message being directed to a target agent endpoint address corresponding to a first AMF associated with a first network operator or a second AMF associated with a second network operator. Operation of block 1815 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1815 may be referenced from... Figure 8 The message receiver 830 described is used to perform this action.

[0225] At 1820, the method may include sending a message from a RAN associated with a first network operator to a first AMF associated with the first network operator via a first communication link, or sending a message from a RAN associated with a first network operator to a second AMF associated with a second network operator via a second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address. Operation of block 1820 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1820 may be provided by reference to [reference needed]. Figure 8 The message sender 835 described is used to perform this.

[0226] Figure 19 A flowchart illustrating a method 1900 for RAN sharing that supports the use of a transport agent function according to various aspects of this disclosure is shown. The operation of method 1900 can be implemented by an AMF agent or its components as described herein. For example, the operation of method 1900 can be implemented by, as referenced... Figures 1 to 9 The described AMF agent is used to perform this function. In some examples, the AMF agent can execute a set of instructions to control the functional elements of the AMF agent to perform the described function. Additionally or alternatively, the AMF agent may use dedicated hardware to perform aspects of the described function.

[0227] At 1905, the method may include establishing a first communication link between a RAN associated with a first network operator and a first AMF associated with the first network operator via an AMF agent. Operation of block 1905 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1905 may be provided by reference to [reference needed]. Figure 8 The AMF agent communication link component 825 is described to perform this function.

[0228] At 1910, the method may include establishing a second communication link between a RAN associated with a first network operator and a second AMF associated with a second network operator via an AMF agent. Operation of block 1910 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1910 may be derived from references... Figure 8 The AMF agent communication link component 825 is described to perform this function.

[0229] At 1915, the method may include receiving a message from a source agent endpoint address corresponding to the RAN via a first or second communication link, the message being directed to a target agent endpoint address corresponding to a first AMF associated with a first network operator or a second AMF associated with a second network operator. Operation of block 1915 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1915 may be referenced from... Figure 8 The message receiver 830 described is used to perform this action.

[0230] At 1920, the method may include avoiding decoding messages from the RAN. The operation of box 1920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 1920 may be provided by reference to [reference needed]. Figure 8 The decoding component 850 is described and executed.

[0231] At 1925, the method may include sending a message via a first communication link to a first AMF or via a second communication link to a second AMF using one or more source agent endpoint addresses, wherein the one or more source agent endpoint addresses correspond to the RAN. Operation of block 1925 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 1925 may be provided by reference to [reference needed]. Figure 8 The message sender 835 described is used to perform this.

[0232] Figure 20 A flowchart illustrating a method 2000 for RAN sharing that supports the use of a transport agent function according to various aspects of this disclosure is shown. The operation of method 2000 may be implemented by an AMF agent or its components as described herein. For example, the operation of method 2000 may be implemented by, as referenced... Figures 1 to 9 The described AMF agent is used to perform this function. In some examples, the AMF agent can execute a set of instructions to control the functional elements of the AMF agent to perform the described function. Additionally or alternatively, the AMF agent may use dedicated hardware to perform aspects of the described function.

[0233] At 2005, the method may include establishing a first communication link between a RAN associated with a first network operator and a first AMF associated with the first network operator via an AMF agent. Operation of block 2005 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2005 may be provided by reference to [reference needed]. Figure 8 The AMF agent communication link component 825 is described to perform this function.

[0234] At 2010, the method may include establishing a second communication link between a RAN associated with a first network operator and a second AMF associated with a second network operator via an AMF agent. Operation of block 2010 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2010 may be provided by reference to [reference needed]. Figure 8 The AMF agent communication link component 825 is described to perform this function.

[0235] At 2015, the method may include receiving a message from a source agent endpoint corresponding to the RAN via a first or second communication link, the message being directed to a target agent endpoint address corresponding to a first AMF associated with a first network operator or a second AMF associated with a second network operator. Operation of box 2015 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2015 may be referenced from... Figure 8 The message receiver 830 described is used to perform this action.

[0236] At 2020, the method may include sending a message from a RAN associated with a first network operator to a first AMF associated with the first network operator via a first communication link, or sending a message from a RAN associated with a first network operator to a second AMF associated with a second network operator via a second communication link, wherein the message is sent to the first AMF or the second AMF based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address. Operation of box 2020 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2020 may be provided by reference to [reference needed]. Figure 8 The message sender 835 described is used to perform this.

[0237] At 2025, the method may include receiving a second message for the RAN from a second AMF associated with a first network operator via a first communication link or from a second AMF via a second communication link, the message being directed to a second target agent endpoint address corresponding to the RAN. Operation of block 2025 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2025 may be referenced from... Figure 8 The message receiver 830 described is used to perform this action.

[0238] At 2030, the method may include sending a second message to the RAN via a first or second communication link based on the second target agent endpoint address corresponding to the RAN. The operation of block 2030 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2030 may be provided by reference to [reference needed]. Figure 8 The message sender 835 described is used to perform this.

[0239] Figure 21 A flowchart illustrating method 2100 for RAN sharing using transport proxy functionality, according to various aspects of this disclosure, is shown. Operation of method 2100 may be implemented by a network entity or its components as described herein. For example, operation of method 2100 may be implemented by, as referenced... Figures 1 to 5 and Figures 10 to 13 The network entity described herein performs the function. In some examples, the network entity may execute a set of instructions to control the functional elements of the network entity to perform the described function. Additionally or alternatively, the network entity may use dedicated hardware to perform aspects of the described function.

[0240] At 2105, the method may include establishing a first communication link between first AMFs associated with a first network operator via an AMF agent. The operation of block 2105 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2105 may be derived from references... Figure 12 The AMF agent communication link manager 1225 is described and used to perform this.

[0241] At 2110, the method may include establishing a second communication link between second AMFs associated with a second network operator via an AMF agent. The operation of block 2110 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 2110 may be derived from references... Figure 12 The AMF agent communication link manager 1225 is described and used to perform this.

[0242] At 2115, the method may include sending a message for a first AMF from a source agent endpoint address corresponding to the RAN to an AMF agent via a first communication link, or sending a message for a second AMF from a source agent endpoint address corresponding to the RAN to an AMF agent via a second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with a first network operator or the second AMF associated with a second network operator, wherein the message is sent to the AMF agent based on a mapping between a set of multiple target agent endpoint addresses and one or more source agent addresses including the source agent endpoint address, wherein the set of multiple target agent endpoint addresses includes the target agent endpoint address. The operation of block 2115 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2115 may be provided by reference to [reference needed]. Figure 12 The message sender 1230 described is used to perform this.

[0243] Figure 22 A flowchart illustrating method 2200 for RAN sharing using a transport proxy function, according to various aspects of this disclosure, is shown. Operation of method 2200 may be implemented by an AMF or its components as described herein. For example, operation of method 2200 may be implemented by, as referenced... Figures 1 to 5 and Figures 14 to 17 The AMF is executed as described. In some examples, the AMF executes a set of instructions to control the functional elements of the AMF to perform the described functions. Additionally or alternatively, the AMF may use dedicated hardware to perform aspects of the described functions.

[0244] At 2205, the method may include establishing a communication link between a RAN associated with a first network operator and a first AMF via an AMF agent. Operation of block 2205 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2205 may be provided by reference to [reference needed]. Figure 16 The AMF agent communication link component 1625 is described to perform this function.

[0245] At 2210, the method may include receiving, via a communication link, a message directed to a target agent endpoint address corresponding to a first AMF from a source agent endpoint address corresponding to the RAN. Operation of block 2210 may be performed according to examples as disclosed herein. In some examples, aspects of operation of 2210 may be referenced. Figure 16 The message receiver 1630 described is used to perform this action.

[0246] At 2215, the method may include decoding a message from the RAN based on the source broker endpoint address and the destination broker endpoint address of the message. The operation of block 2215 may be performed according to the examples disclosed herein. In some examples, aspects of the operation of 2215 may be provided by reference to [reference needed]. Figure 16 The described decoding component 1635 is used to perform this.

[0247] The following provides an overview of the various aspects of this disclosure:

[0248] Aspect 1: A method for wireless communication at an AMF agent, the method comprising: establishing a first communication link via the AMF agent between a RAN associated with a first network operator and a first AMF associated with the first network operator; establishing a second communication link via the AMF agent between the RAN associated with the first network operator and a second AMF associated with a second network operator; receiving a message via the first communication link or the second communication link from a source agent endpoint address corresponding to the RAN, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and sending the message from the RAN associated with the first network operator to the first AMF associated with the first network operator via the first communication link, or sending the message from the RAN associated with the first network operator to the second AMF associated with the second network operator via the second communication link, wherein the message is sent to the first AMF or the second AMF at least in part based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, the plurality of target agent endpoint addresses including the target agent endpoint address.

[0249] Aspect 2: According to the method of aspect 1, the method further includes: establishing a plurality of communication links between a plurality of RANs and a plurality of AMFs via the AMF agent, wherein each of the plurality of communication links is between a corresponding RAN in the plurality of RANs and a corresponding AMF in the plurality of AMFs, wherein the plurality of communication links includes the first communication link and the second communication link.

[0250] Aspect 3: The method according to any one of Aspects 1 to 2, wherein the first communication link is established directly between the radio access network and the first AMF, and the method further comprises: establishing the second communication link between the RAN and the second AMF associated with the second network operator via the first AMF, wherein the first AMF acts as the AMF.

[0251] Aspect 4: The method according to any one of Aspects 1 to 3, wherein receiving the message from the RAN via the first communication link or the second communication link comprises: avoiding decoding the message from the RAN; and sending the message via the first communication link to the first AMF or via the second communication link to the second AMF using the one or more source agent endpoint addresses, wherein the one or more source agent endpoint addresses correspond to the RAN.

[0252] Aspect 5: The method according to any one of Aspects 1 to 4, the method further comprising: receiving a second message for the RAN from the first AMF via the first communication link or from the second AMF via the second communication link, the second message being directed to a second target agent endpoint address corresponding to the RAN; and sending the second message to the RAN via the first communication link or the second communication link, at least in part based on the second target agent endpoint address corresponding to the RAN.

[0253] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the first communication link terminates at the RAN associated with the first network operator and the first AMF associated with the first network operator, and wherein the second communication link terminates at the RAN associated with the first network operator and the second AMF associated with the second network operator.

[0254] Aspect 7: A method for wireless communication at a RAN associated with a first network operator, the method comprising: establishing a first communication link between first AMFs associated with the first network operator via an AMF agent; establishing a second communication link between second AMFs associated with a second network operator via the AMF agent; and sending a message for the first AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the first communication link, or sending a message for the second AMF from a source agent endpoint address corresponding to the RAN to the AMF agent via the second communication link, the message being directed to a target agent endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF agent at least in part based on a mapping between a plurality of target agent endpoint addresses and one or more source agent endpoint addresses including the source agent endpoint address, wherein the plurality of target agent endpoint addresses includes the target agent endpoint address.

[0255] Aspect 8: According to the method of aspect 7, the method further includes: establishing a plurality of communication links between a plurality of AMFs and a plurality of RANs via the AMF agent, wherein each of the plurality of communication links is between a corresponding RAN in the plurality of RANs and a corresponding AMF in the plurality of AMFs, wherein the plurality of communication links includes the first communication link and the second communication link.

[0256] Aspect 9: The method according to any one of Aspects 7 to 8, wherein the first communication link is established directly between the radio access network and the first AMF, and the method further comprises: establishing the second communication link between the second AMF and the RAN via the first AMF, wherein the first AMF acts as an AMF proxy.

[0257] Aspect 10: The method according to any one of Aspects 7 to 9, the method further comprising: receiving a second message from the first AMF via the first communication link or from the second AMF via the second communication link, the second message being directed to a target agent endpoint address corresponding to the RAN.

[0258] Aspect 11: The method according to any one of Aspects 7 to 10, wherein both the first communication link and the second communication link terminate at the RAN.

[0259] Aspect 12: A method for wireless communication at a first AMF, the method comprising: establishing a communication link between a RAN associated with a first network operator and the first AMF via an AMF agent; receiving, via the communication link, a message directed to a target agent endpoint address corresponding to the first AMF from a source agent endpoint address corresponding to the RAN; and decoding the message from the RAN based at least in part on the source agent endpoint address and the target agent endpoint address of the message.

[0260] Aspect 13: The method according to aspect 12, the method further comprising: establishing a plurality of communication links between a plurality of RANs and a plurality of AMFs via the AMF agent, wherein each of the plurality of communication links is between a corresponding RAN in the plurality of RANs and the AMF, wherein the plurality of communication links includes the communication link.

[0261] Aspect 14: The method according to any one of Aspects 12 to 13, wherein establishing the communication link comprises: establishing the communication link between the RAN associated with the first network operator and the first AMF via the AMF agent, wherein the first AMF is associated with the first network operator or a second network operator.

[0262] Aspect 15: The method according to any one of Aspects 12 to 14, the method further comprising: sending a second message for the RAN to the AMF agent via the communication link, the second message being directed to a second target agent endpoint address corresponding to the RAN.

[0263] Aspect 16: The method according to any one of Aspects 12 to 15, wherein the communication link terminates at the AMF.

[0264] Aspect 17: An apparatus for wireless communication at an AMF agent, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 1 to 6.

[0265] Aspect 18: An apparatus for wireless communication at an AMF agent, the apparatus comprising at least one component for performing the method according to any one of Aspects 1 to 6.

[0266] Aspect 19: A non-transitory computer-readable medium storing code for wireless communication at an AMF agent, the code comprising instructions executable by a processor to perform the method according to any one of Aspects 1 to 6.

[0267] Aspect 20: An apparatus for wireless communication at a RAN associated with a first network operator, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 7 to 11.

[0268] Aspect 21: An apparatus for wireless communication at a RAN associated with a first network operator, the apparatus comprising at least one component for performing the method according to any one of aspects 7 to 11.

[0269] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication at a RAN associated with a first network operator, the code including instructions executable by a processor to perform the method according to any one of aspects 7 to 11.

[0270] Aspect 23: An apparatus for wireless communication at a first AMF, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method according to any one of Aspects 12 to 16.

[0271] Aspect 24: An apparatus for wireless communication at a first AMF, the apparatus comprising at least one component for performing the method according to any one of aspects 12 to 16.

[0272] Aspect 25: A non-transitory computer-readable medium storing code for wireless communication at a first AMF, said code including instructions executable by a processor to perform the method according to any one of Aspects 12 to 16.

[0273] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more methods can be combined.

[0274] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0275] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0276] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternative embodiments, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0277] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, these functions can be stored as one or more instructions or code on a computer-readable medium, or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in different locations, including portions distributed such that the functions are implemented in different physical locations.

[0278] Computer-readable media include both non-transitory computer storage media and communication media, with the latter including any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Additionally, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, while optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media.

[0279] As used herein (including in the claims), the word "or" used in an enumeration of items (e.g., an enumeration of items accompanied by phrases such as "at least one of" or "one or more of") indicates an inclusive enumeration, such that an enumeration of at least one of, for example, A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Additionally, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0280] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0281] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0282] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0283] The description provided herein is intended to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An apparatus for wireless communication at an access and mobility management function (AMF) proxy, the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establish, via the AMF proxy, a first communication link between a radio access network associated with a first network operator and a first AMF associated with the first network operator; establish, via the AMF proxy, a second communication link between the radio access network associated with the first network operator and a second AMF associated with a second network operator; receive, via the first communication link or the second communication link, a message from a source proxy endpoint address corresponding to the radio access network, the message being directed to a target proxy endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and transmit, via the first communication link, the message from the radio access network associated with the first network operator to the first AMF associated with the first network operator or, via the second communication link, the message from the radio access network associated with the first network operator to the second AMF associated with the second network operator, wherein the message is transmitted to the first AMF or the second AMF based at least in part on a mapping between a plurality of target proxy endpoint addresses and one or more source proxy endpoint addresses including the source proxy endpoint address, wherein the plurality of target proxy endpoint addresses includes the target proxy endpoint address.

2. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: establish, via the AMF proxy, a plurality of communication links between a plurality of radio access networks and a plurality of AMFs, wherein each communication link of the plurality of communication links is between a respective radio access network of the plurality of radio access networks and a respective AMF of the plurality of AMFs, wherein the plurality of communication links includes the first communication link and the second communication link.

3. The apparatus of claim 1, wherein the first communication link is established directly between the radio access network and the first AMF, and the instructions are further executable by the processor to cause the apparatus to: establish, via the first AMF, the second communication link between the radio access network and the second AMF associated with the second network operator, wherein the first AMF acts as the AMF proxy.

4. The apparatus of claim 1, wherein the instructions to receive, via the first communication link or the second communication link, the message from the radio access network are executable by the processor to cause the apparatus to: avoid decoding the message from the radio access network; and ​ sending the message to the first AMF via the first communication link or to the second AMF via the second communication link using the one or more source proxy endpoint addresses, wherein the one or more source proxy endpoint addresses correspond to the radio access network.

5. The apparatus of claim 1, wherein the instructions are further executable by the processor to cause the apparatus to: receive, from the first AMF via the first communication link or from the second AMF via the second communication link, a second message for the radio access network associated with the first network operator, the second message being directed to a second target proxy endpoint address corresponding to the radio access network; and send the second message to the radio access network via the first communication link or the second communication link based at least in part on the second target proxy endpoint address corresponding to the radio access network.

6. The apparatus of claim 1, wherein the first communication link terminates at the radio access network associated with the first network operator and at the first AMF associated with the first network operator, and wherein the second communication link terminates at the radio access network associated with the first network operator and at the second AMF associated with the second network operator.

7. An apparatus for wireless communication at a radio access network associated with a first network operator, the apparatus comprising: a processor; a memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establish a first communication link between a first access and mobility management function (AMF) associated with the first network operator via an AMF proxy; establish a second communication link between a second AMF associated with a second network operator via the AMF proxy; and send, to the AMF proxy via the first communication link, a message for the first AMF from a source proxy endpoint address corresponding to the radio access network or send, to the AMF proxy via the second communication link, a message for the second AMF from a source proxy endpoint address corresponding to the radio access network, the message being directed to a target proxy endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator, wherein the message is sent to the AMF proxy based at least in part on a mapping between a plurality of target proxy endpoint addresses and one or more source proxy addresses including the source proxy endpoint address, wherein the plurality of target proxy endpoint addresses includes the target proxy endpoint address.

8. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: establish a plurality of communication links between a plurality of AMFs and a plurality of radio access networks via the AMF proxy, wherein each communication link of the plurality of communication links is between a respective radio access network of the plurality of radio access networks and a respective AMF of the plurality of AMFs, wherein the plurality of communication links includes the first communication link and the second communication link.

9. The apparatus of claim 7, the first communication link is established directly between the radio access network and the first AMF, and the instructions are further executable by the processor to cause the apparatus to: establish the second communication link between the second AMF and the radio access network via the first AMF, wherein the first AMF acts as the AMF proxy.

10. The apparatus of claim 7, wherein the instructions are further executable by the processor to cause the apparatus to: receive, via the first communication link from the first AMF or via the second communication link from the second AMF, a second message that is directed to a second target proxy endpoint address corresponding to the radio access network.

11. The apparatus of claim 7, wherein both the first communication link and the second communication link terminate at the radio access network.

12. An apparatus for wireless communication at a first access and mobility management function (AMF), the apparatus comprising: a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establish a communication link between a radio access network associated with a first network operator and the first AMF via an AMF proxy; receive, via the communication link from a source proxy endpoint address corresponding to the radio access network, a message that is directed to a target proxy endpoint address corresponding to the first AMF; and decode the message from the radio access network based at least in part on the source proxy endpoint address and the target proxy endpoint address of the message.

13. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: establish a plurality of communication links between a plurality of radio access networks and a plurality of AMFs via the AMF proxy, wherein each communication link of the plurality of communication links is between a respective radio access network of the plurality of radio access networks and an AMF of the plurality of AMFs, wherein the plurality of communication links includes the communication link.

14. The apparatus of claim 12, wherein the instructions to establish the communication link are executable by the processor to cause the apparatus to: establish the communication link between the radio access network associated with the first network operator and the first AMF via the AMF proxy, wherein the first AMF is associated with the first network operator or a second network operator.

15. The apparatus of claim 12, wherein the instructions are further executable by the processor to cause the apparatus to: ​ sending, to the AMF proxy via the communication link, a second message for the radio access network, the second message being directed to a second target proxy endpoint address corresponding to the radio access network.

16. The apparatus of claim 12, wherein the communication link terminates at the AMF.

17. A method for wireless communication at an access and mobility management function (AMF) proxy, the method comprising: establishing, via the AMF proxy, a first communication link between a radio access network associated with a first network operator and a first AMF associated with the first network operator; establishing, via the AMF proxy, a second communication link between the radio access network associated with the first network operator and a second AMF associated with a second network operator; receiving, via the first communication link or the second communication link, a message from a source proxy endpoint address corresponding to the radio access network, the message being directed to a target proxy endpoint address corresponding to the first AMF associated with the first network operator or the second AMF associated with the second network operator; and sending, via the first communication link, the message from the radio access network associated with the first network operator to the first AMF associated with the first network operator or sending, via the second communication link, the message from the radio access network associated with the first network operator to the second AMF associated with the second network operator, wherein the message is sent to the first AMF or the second AMF based at least in part on a mapping between a plurality of target proxy endpoint addresses and one or more source proxy endpoint addresses including the source proxy endpoint address, wherein the plurality of target proxy endpoint addresses includes the target proxy endpoint address.

18. The method of claim 17, further comprising: establishing, via the AMF proxy, a plurality of communication links between a plurality of radio access networks and a plurality of AMFs, wherein each communication link of the plurality of communication links is between a respective radio access network of the plurality of radio access networks and a respective AMF of the plurality of AMFs, wherein the plurality of communication links includes the first communication link and the second communication link.

19. The method of claim 17, wherein the first communication link is established directly between the radio access network and the first AMF, and the method further comprises: establishing, via the first AMF, the second communication link between the radio access network and the second AMF associated with the second network operator, wherein the first AMF acts as the AMF proxy.

20. The method of claim 17, wherein receiving the message from the radio access network via the first communication link or the second communication link comprises: avoiding decoding the message from the radio access network; and ​ ​ sending the message to the first AMF via the first communication link or to the second AMF via the second communication link using the one or more source proxy endpoint addresses, wherein the one or more source proxy endpoint addresses correspond to the radio access network.

21. The method of claim 17, further comprising: receiving a second message for the radio access network associated with the first network operator via the first communication link from the first AMF or via the second communication link from the second AMF, the second message being directed to a second target proxy endpoint address corresponding to the radio access network; and sending the second message to the radio access network via the first communication link or the second communication link based at least in part on the second target proxy endpoint address corresponding to the radio access network.

22. The method of claim 17, wherein the first communication link terminates at the radio access network associated with the first network operator and at the first AMF associated with the first network operator, and wherein the second communication link terminates at the radio access network associated with the first network operator and at the second AMF associated with the second network operator.

Images