Patent Description:
During large live production events, such as music festivals, attendees desire to listen to live audio produced during the events. It is common that certain locations within an event site may have poor audio reproduction for listeners within those locations. In such scenarios, problems may arise due to distances from the loudspeakers to the audience resulting in propagation delays. If a listener is in a position to receive audio from more than one public address system (PA) system simultaneously, it is very likely that the propagation delays of the PAs are not synchronized, causing a noticeably echo/reverberation effect. Such conditions result in a poor quality listening experience. Another problem occurs when performances are played at more than one stage simultaneously, as is usual in a large music festival. In that case, the listener may receive audio simultaneously from more than one stage, which will also degrade its perceived audio quality.

Therefore, there is a need for systems and method for providing improved distribution of audio and other service traffic to users within a service area.

"<NPL>, describes a study on the enhancement of the <NUM> System for vertical and local area network services.

"<NPL>, describes system architecture for the <NUM> system.

<NPL>, describes a proposal for consolidated service requirements of AVPROD.

<NPL>, describes live production with integrated audience.

Further documents are "<NPL>, and <NPL>.

In accordance with the invention, there is provided a method by a user equipment, a method by a base station, a user equipment, and a base station, as set forth in the claims. The scope of protection is defined by the claims, and any examples described herein falling outside of the claims are for illustrative purposes only.

Example embodiments provide methods and apparatuses for a dual connection mechanism to support multi-operators with different service traffic simultaneously.

In accordance with an example embodiment, a method as according to claim <NUM> includes establishing, by a user equipment, UE, a communication tunnel with a first base station over a transmit, TX, chain, the TX chain being synchronized a second base station, wherein the communication tunnel allows the UE to communicate with a first wireless network associated with the first base station via a second wireless network associated with the second base station, wherein the first wireless network is a non-public network, NPN, and the second wireless network is a mobile network operator, MNO, network;receiving, by the UE, a request from the first base station or the second base station requesting the UE to synchronize a first receive, RX, chain of the UE to the first base station to receive first traffic from the first wireless network and synchronize a second RX chain of the UE to the second base station to receive second traffic from the second wireless network; transmitting, via the TX chain of the UE, an uplink signal to the first wireless network associated with the first base station or the second wireless network associated with the second base station, the uplink signal including information indicative of the first RX chain of the UE being synchronized to the first base station to receive the first traffic from the first wireless network and the second RX chain of the UE being synchronized to the second base station to receive the second traffic from the second wireless network; and transmitting, by the UE, uplink traffic for the first wireless network and the second wireless network to the second base station via the TX chain of the UE.

Optionally, in any of the preceding embodiments, the transmitting of the uplink signal to the first base station uses the communication tunnel.

Optionally, in any of the preceding embodiments, data associated with the uplink signal to the first base station is encapsulated in an over-the-top (OTT) internet protocol (IP) packet.

Optionally, in any of the preceding embodiments, the communication tunnel is established between the first wireless network and the second wireless network, the communication tunnel allowing the UE to communicate with the first wireless network associated with the first base station via the second wireless network associated with the second base station.

Optionally, in any of the preceding embodiments, the information further includes an indication that the TX chain of the UE will be synchronized with the second base station only, the uplink traffic to the first wireless network passing through the second wireless network associated with the second base station. Optionally, in any of the preceding embodiments, the information further includes an indication that the TX chain of the UE will be synchronized and communicate with the first base station associated with the first wireless network either periodically or on-demand, and will be re-synchronized with the second base station.

Optionally, in any of the preceding embodiments, the information further includes at least one of a reason code, an indication of an interval for periodic synchronization, or an indication of a time period for the TX chain of the UE to be synchronized with the first base station.

In accordance with another example embodiment, a user equipment (UE) as according to claim <NUM> is provided.

In accordance with another example embodiment, a method, performed by a first base station, as according to claim <NUM> is provided.

In accordance with another example embodiment, a first base station as according to claim <NUM> is provided.

Practice of the foregoing embodiments provides for a tunneling mechanism between a UE and a NPN via an MNO to allow the UE to establish and transmit data to the NPN without impacting the ongoing active communication with its MNO. Practice of the foregoing embodiments further provides for a notification mechanism between a UE and a network to allow a UE to split traffic between two networks, as defined by the claims.

The making and using of embodiments of this disclosure are discussed in detail below. It should be appreciated, however, that the concepts disclosed herein can be embodied in a wide variety of specific contexts, and that the specific embodiments discussed herein are merely illustrative and do not serve to limit the scope of the claims. Further, it should be understood that various changes, substitutions and alterations can be made herein without departing from the scope of this disclosure as defined by the appended claims.

<FIG> illustrates a wireless communications network <NUM> for communicating data. A wireless communications network is not covered by the claimed invention.

The network <NUM> comprises a base station <NUM> having a coverage area <NUM>, a plurality of mobile devices <NUM>, and a backhaul network <NUM>. As shown, the base station <NUM> establishes uplink (dashed line) and/or downlink (dotted line) connections with the mobile devices <NUM>, which serve to carry data from the mobile devices <NUM> to the base station <NUM> and vice-versa. Data carried over the uplink/downlink connections may include data communicated between the mobile devices <NUM>, as well as data communicated to/from a remote-end (not shown) by way of the backhaul network <NUM>. As used herein, the term "base station" refers to any component (or collection of components) configured to provide wireless access to a network, such as an enhanced base station (eNB), a macro-cell, a femtocell, a Wi-Fi access point (AP), or other wirelessly enabled devices. Base stations may provide wireless access in accordance with one or more wireless communication protocols, e.g., long term evolution (LTE), LTE advanced (LTE-A), High Speed Packet Access (HSPA), Wi-Fi <NUM>. 11a/b/g/n/ac, etc. As used herein, the term "mobile device" refers to any component (or collection of components) capable of establishing a wireless connection with a base station, such as a user equipment (UE), a mobile station (STA), and other wirelessly enabled devices. In some embodiments, the network <NUM> may comprise various other wireless devices, such as relays, low power nodes, etc..

During large live production events, such as music festivals, attendees desire to listen to live audio produced during the events. It is common that certain locations within an event site may have poor audio reproduction for listeners within those locations. In such scenarios, problems may arise due to distances from the loudspeakers to the audience resulting in propagation delays. If a listener is in a position to receive audio from more than one public address system (PA) system simultaneously, it is very likely that the propagation delays of the PAs are not synchronized, causing a noticeably echo/reverberation effect. Such conditions result in a poor quality listening experience. A PA may refer to an electronic system used to increase the apparent volume (e.g., loudness) of acoustic sound sources. PAs are typically used in a public venue for amplification of sound sources to make them sufficiently audible over the whole event area. Another problem occurs when performances are played at more than one stage simultaneously, as is usual in a large music festival. In that case, the listener may receive audio simultaneously from more than one stage, which will also degrade its perceived audio quality. The degradation in audio quality may be particularly significant to listeners with hearing impairments.

A listener may obtain a better quality sound experience by listening to a direct mix coming from the mixing desk, or by the inclusion of 3D sound effects that would not be possible to provide with loudspeakers over the wide festival area. In order to achieve the benefits of better audio experience, a possible solution is to provide high quality audio playback over headphones to listeners who are carrying their own devices. Services are being considered to allow concert attendants to use user equipment (UE) devices, such as smartphones, to connect to a <NUM> concert private network to receive a high quality audio stream, and also connect to their own mobile network operators (MNOs) to receive other data service at the same time. An MNO may be an operator owning and operating a network for public use. Such services have been launched using WiFi connections, but due to the nature of unlicensed WiFi deployment, the performance is not satisfactory. Accordingly, <NUM> technology is being considered for providing audio services to attendees using UEs. In addition, if using a WiFi private network, there is no standard impact for 3GPP because current smartphones already support simultaneously connecting to both an MNO's mobile network and a WiFi private network.

<FIG> illustrates a wireless communication network <NUM> showing an example use case. A wireless communication network is not covered by the claimed invention.

The network <NUM> includes an audio distribution non-public network (NPN) <NUM> in communication with a first public land mobile network (PLMN) 220A associated with a first MNO (MNO A) having a core 222A and base station 224A, and a second PLMN associated with a second MNO (MNO B) having a core 222B and base station 224B. An NPN may refer to a network that is intended for non-public use. The audio distribution NPN <NUM> is configured to receive audio from a stage <NUM> audio processing system <NUM> associated with a first stage and a stage <NUM> audio processing system <NUM> associated with a second stage. The audio distribution NPN <NUM> includes an audio distribution system <NUM>, a core <NUM>, and a base station <NUM>. The stage <NUM> audio processing system <NUM> includes a stage <NUM> having one or more audio sources, such as microphones and/or musical instruments, an audio mixing system <NUM>, an audio processing system <NUM>, and speakers <NUM>. The one or more audio sources of stage <NUM> provide audio signals to the audio mixing system <NUM> and audio processing system <NUM> for mixing and processing the audio signals, respectively. The processed audio is provided to the audio distribution system <NUM> of audio distribution NPN <NUM> and speakers <NUM>.

Similarly, the stage <NUM> audio processing system <NUM> includes a stage <NUM> having one or more audio sources, an audio mixing system <NUM>, an audio processing system <NUM>, and speakers <NUM>. The one or more audio sources of stage <NUM> provide audio signals to the audio mixing system <NUM> and audio processing system <NUM> for mixing and processing the audio signals, respectively. The processed audio is provided to the audio distribution system <NUM> of audio distribution NPN <NUM> and speakers <NUM>.

The base station <NUM> of audio distribution NPN <NUM> is configured to broadcast one or more multicast audio streams to UEs 250A-250E. Each of the UEs 250A-250E is associated with an attendee of an event. In a particular embodiment, each of the UEs 250A-250E is associated with a headset for providing an audible reproduction of one or more of the multicast audio streams. The first PLMN 220A and second PLMN 220B are configured to provide a general data connection to one or more of the UEs 250A-250E. In a particular use case, a listener, Paul, associated with the UE 250A (e.g., a smart phone) A is located at a good position to listen to a band playing in the first stage <NUM>, but wants to hear a better quality audio stream including a three-dimensional (3D) enhanced version using the UE 250A and high-quality headphones. If Paul doesn't have a subscription the audio distribution NPN <NUM>, he can quickly sign up for the service online and receive a correct credential from the network. Paul turns on an application installed on the UE 250A, which connects to the audio distribution system <NUM> using the audio distribution NPN <NUM>. A list of available channels is displayed to Paul by the UE 250A, and he chooses to listen to stage <NUM> with enhanced 3D. The applications starts playback of the requested audio through Paul's headphones, which may have not enough acoustic insulation to block the PA system of the event, and Paul listens to both the PA system and the requested audio using headphones. The time difference between Paul's headphone sound and the sound coming from the PA system is small, and doesn't result in noticeable audio artifacts like reverberation or echo effects.

Example performance requirements to support such use cases having live production with integrated audience service are given in Table <NUM> below:.

A 3GPP system should be able to enable a UE to receive low-latency downlink multicast traffic from one network (e.g. an NPN), and paging as well as other data services from another network (e.g. PLMN) simultaneously.

Many existing UEs include one transmitter and two receivers, and when the UE is receiving broadcast traffic from a private network, no uplink is allowed for the private network, e.g., when the UE is accessing the NPN. A problem arises regarding how the UE can transmit uplink traffic to an MNO when connected to the NPN, especially for control plane traffic to an eNB. Additionally, when only one transmitter is available to the UE, when the UE switches between networks the other network RAN is suspended which can be detrimental to the user experience. In addition, switching of the transmitter between different networks increases system complexity. When the UE is connected to the private network, in order for the UE to split the transmitter between the private network and the MNO, it would be desirable for a mechanism to exist to inform the network of the UE's capability and transmitter/receiver configuration changes to enable the network to respond correspondingly. Accordingly, it is desirable to provide a solution to allow a single transmitter of a UE to communicate simultaneously with two networks (e.g., a private network and an MNO).

In order to keep latency to controllable levels, it is desirable that the audio distribution system is at the edge of the network, meaning that the UEs will only benefit from the audio distribution system if the UEs are in the same physical network as the audio distribution system. Therefore, any solution which uses a public network to route those ultra-reliable low latency communication (URLLC) data is not desirable. In addition, for reasons of data privacy and performance guarantee, a media production company may prefer to have a private network with a dedicated spectrum for the concert or performance so that users may connect to and are authorized into the private network instead of using their own MNO network. Accordingly, mechanisms for guaranteeing the quality of service for both users using the MNO (e.g., normal cellular network data/voice services) as well as the users listening to the stream of the audio distribution system. Additionally, the listeners of the audio distribution system would bring their own mobile devices which will most likely be served by different MNOs. Therefore, a mechanism is desired to allow different MNOs' users to connect to the same private network.

Because the concert as well as multicast broadcast service (MBMS) received by the user may require payment of a fee, the NPN may need to make sure that only UEs that are located in the premise of the event (e.g., a concert) can receive the MBMS traffic. Therefore, a mechanism may apply a restriction on who can receive MBMS in this particular location, or restrictions specifying that those who subscribe to the service can listen to the MBMS.

Embodiments of the present disclosure provide a tunneling mechanism between a UE and a NPN via an MNO to allow the UE to establish and transmit data to the NPN via an application server, without impacting the ongoing active communication with its MNO.

Embodiments of the present disclosure also provide a notification mechanism between a UE and a network to allow a smooth UE receiver split to support two networks, in which the network receives a notification of a potential Quality of Service (QoS) performance impact caused by the traffic split. In some embodiments, a new radio access network (RAN) user indirect function (UIF) and APIs are provided to allow a UE which is receiving Multicast/broadcast traffic via this RAN to indirectly interact with the RAN via an over-the-top tunnel connection through another network, without transmitting data via a Uu interface with the RAN. In other embodiments, the communication tunnel may be established with another function of the RAN or to an eNB.

The RAN UIF may include the following the functionalities: establish and maintain the over the top IP connection with the authorized UE, collect the UE's air-interface measurement, including statistic measurement, or real-time measurement, and conduct normal interact with the UE using a Uu protocol, but the Uu protocol messages exchanged between UE and RAN are encapsulated in the over-the-top (OTT) IP packets. The RAN UIF may expose several types of API to the UE or other authorized functions, such as core functions including a network exposure function (NEF). Through a UE measurement collection API, the UE may provide air-interface measurements, including statistic measurements, or real-time measurements, in order to assist a gNB for better resource scheduling. Through Uu interaction APIs, the UE may be allowed to interact with gNB as if the UE is in contact with a gNB via the Uu interface, but actually through a secure IP connection such as a URLLC connection to reduce the control message latency. In particular embodiments, the API may be accessed via the NEF or a security tunnel via a normal data plane. In some embodiments, the RAN may use this UIF and API to collect UE's measurement. Embodiments allow for the UE to actively connect to two different networks with only one transmission channel (TX).

<FIG> illustrates a diagram of a system <NUM> for a UE <NUM> to establish a communication channel with an NPN <NUM> via a public network <NUM>, which does not contain all of the features required by the claimed invention. The public network <NUM> includes a first gNB <NUM> and a user plane function (UPF) <NUM>. The NPN <NUM> includes a second gNB <NUM>, an NEF <NUM>, and a RAN UIF <NUM>. The public network <NUM> is in communication with the NPN <NUM> via the internet <NUM>. In a first step, the UE <NUM> establishes a new dedicated URLLC data connection <NUM> with the first gNB <NUM> of the public network <NUM> for the purpose of establishing a secure communication channel with the NPN <NUM>. In an alternative embodiment, the UE <NUM> can reuse an existing data connection. In a second step, the gNB <NUM> establishes a data plane connection <NUM> with UPF <NUM>. In a third step, the UE <NUM> uses the connection of the public network <NUM> to create an over-the-top connection <NUM> with the NPN <NUM>. In an embodiment of a fourth step, the UE <NUM> establishes a connection <NUM>, <NUM> with the RAN UIF <NUM> directly via the PNP's UPF <NUM> via a core network, by sending a message via a particular port of the RAN UIF <NUM>. In an alternative embodiment of the fourth step, the UE <NUM> interacts with the NEF <NUM> of the NPN <NUM> by using an API exposed by the NEF <NUM> using a control plane connection <NUM>, then the NEF <NUM> forwards the information to the RAN UIF <NUM> or the second gNB <NUM> using the control plane, and forwards the control information of the second gNB <NUM> to the UE <NUM> via the API to the UE <NUM>.

In some embodiments, the network notification for the UE to split two receive (RX) channels is sent between the NPN and the MNO network. In order to keep two active connections between the NPN and public MNO, the UE needs to allocate one RX channel for the MNO and the other for the NPN. However, when the UE splits the RX channels, the QoS of the connections with the MNO while using two RX channels may be impacted. Some QoS related core network functions, such as the QoS monitor, policy analytic functions (e.g., policy control function (PCF), network work data analytic function (NWDAF), or charging function (CHF)), may need to be notified. Also in order for network to activate the UE for receiving MBMS, the network may need to send an activation request to the UE after it is aware that the UE is able to receive.

In accordance with an embodiment, a UE driven UE and network coordinated RX split mechanism is provided. In this mechanism, a hardware configuration change notification information element (IE) is provided, which is sent by the UE to indicate to the network that some UE configuration has changed which may impact the QoS. An IE set may be provided to include a TX split start indicator. The TX split start indicator may also associate with timer information, which indicates when the split is expected to start after the indicator is sent.

In an embodiment, the IE can be carried in a layer <NUM> MAC message between the UE and the RAN, and then sent to a <NUM> Core, or in NAS message between UE and the <NUM> Core. A UE Rx split notification may be sent to the MNO via an API exposed by the MNO. In this case, the NPN MBMS server may establish an N33 connection with the MNO as an application function (AF). The AF may interact with 3GPP network functions. After the network receives the TX split indicator, the network may configure the network resource accordingly, or update a QoS configuration for the services provided to the UE.

In another embodiment, a network driven RX channel split in which the network is an initiator and controller for UE RX channel split is provided in which a first RX channel of the UE is allocated to a first network (e.g., a NPN) and a second RX channel of the UE is allocated to a second network (e.g., a MNO). In some embodiments, a UE successfully connects to the NPN, but has not started to receive MBMS traffic from the NPN. If there is business agreement between the MNO (network <NUM>) and the NPN, the MNO is notified that the UE has been successfully authorized to connect to the NPN and is ready to receive MBMS traffic.

In an embodiment, the MNO acts as an authenticator proxy for the NPN to authenticate and authorize the UE. Accordingly, the MNO is aware if the UE is authorized to receive MBMS from the NPN. In another embodiment, an MBMS server associated with the NPN establishes a connection with the MNO as an AF, and sends a traffic split request to the MNO via an API of the MNO, such as an API of a NEF or other API function, to request the MNO to allow the UE to receive traffic from the NPN. In particular embodiments, the API may be a new API to allow an application to conduct communication level configurations, such as split traffic, and support dual active connections with two RX channels.

In an embodiment, after the MNO is notified that the UE is ready for RX channel split, the MNO may configure its network resource and potentially reconfigure the QoS of the services to prepare for possible performance deterioration. The MNO then sends an RX channel split request to the UE. In particular embodiments, the RX channel split request may be sent via a non-standalone access (NSA) message or a media access control (MAC) layer message. Upon receiving the Rx split request, the UE may split the RX channels of the UE to connect to the NPN and start to receive MBMS traffic from the NPN.

<FIG> illustrates a diagram of an embodiment, which is not according to the claimed invention, of a process <NUM> for network notification of a UE-driven RX channel split. The process <NUM> includes a UE <NUM>, a MNO network (network <NUM>) <NUM>, an NPN (network <NUM>) <NUM>, and an NPN mobile broadcast service (MBS) server <NUM> associated with the NPN <NUM>. At <NUM>, the UE <NUM> establishes a connection with the NPN <NUM>. At <NUM>, the UE <NUM> decides to split the two RX channels of the UE <NUM> to allocate a first RX channel to the MNO network <NUM> and a second RX channel to the NPN <NUM>.

At <NUM>, the UE <NUM> sends a hardware configuration change indication to the MNO network <NUM> to indicate that the UE channel configuration has changed that may require QoS and/or UP changes for the UE <NUM>. The indication may include a TX channel split start indicator indicative of a time at which the RX channel split is to occur. The split start indicator may associate timer information which indicates a time at which the split is expected to start.

As an alternative embodiment to the UE <NUM> sending the hardware configuration change indication at <NUM>, at <NUM> the UE <NUM> notifies the MBS server <NUM> of the split using an application level indication and at <NUM> the MBS server <NUM> notifies the MNO network <NUM> of the UE RX channel configuration change. In some embodiments, both of the methods of notifying the MNO network <NUM> of the split may be used together.

At <NUM>, the MNO network <NUM> conducts the necessary QoS and user plane (UP) changes for the UE <NUM>. At <NUM>, the UE <NUM> starts to split the RX channel allocation by allocating the first RX channel to the MNO network <NUM> and the second RX channel to the NPN <NUM>. At <NUM>, the UE <NUM> receives MBMS traffic from the NPN <NUM>. At <NUM>, UE <NUM> exchanges uplink/downlink traffic with the MNO network <NUM>.

<FIG> illustrates a flowchart <NUM> of a procedure of a UE during a UE-driven RX channel split according to an embodiment not covered by the claimed invention.

In step <NUM>, the UE <NUM> registers to the NPN <NUM>. In step <NUM>, the UE establishes a unicast communication tunnel with the NPN <NUM> on top of the MNO network <NUM>. In step <NUM>, the UE <NUM> self-configures to receive MBS service by configuring a first RX channel for the MNO network <NUM> and a second RX channel for the NPN <NUM>. In step <NUM>, the UE <NUM> configures a start timer indicating a time that the RX split will occur when the start timer expires.

In step <NUM>, the UE <NUM> sends an RX split notification message to one or more of the MNO network <NUM> or the NPN <NUM>. In step <NUM>, the UE <NUM> determines whether the start timer has expired. If the start timer has not expired, the UE <NUM> returns remains at step <NUM>. If the start time has expired, at step <NUM> the UE <NUM> begins receiving the MBS from the NPN <NUM> using the first RX channel and data from the MNO network <NUM> using the second RX channel. In step <NUM>, the UE <NUM> continues to use the TX channel of the UE <NUM> to send data to the MNO network <NUM>, and the established tunnel to send data to the NPN <NUM>.

<FIG> illustrates a diagram of a process <NUM> for network notification of a network-driven RX channel split, which does not contain all of the features required by the claimed invention. The process <NUM> includes a UE <NUM>, a MNO network (network <NUM>) <NUM>, an NPN (network <NUM>) <NUM>, and an NPN MBS server <NUM> associated with the NPN <NUM>. The UE <NUM> establishes a connection <NUM> with the NPN <NUM> via the MNO network <NUM> as an authentication proxy <NUM>. In an alternative embodiment, at <NUM> the UE <NUM> establishes a direction connection with the NPN <NUM>. In some embodiments, both methods of establishing a connection between the UE <NUM> and the NPN <NUM> may be used together.

At <NUM>, the NPN MBS server <NUM> receives an indication from the NPN <NUM> that the UE <NUM> is ready for receiving MBMS data. At <NUM>, the NPN MBS server sends a UE RX configuration change request to the MNO network <NUM>. At <NUM>, the MNO network <NUM> conducts any necessary QoS and user plane (UP) changes for the UE <NUM>. At <NUM>, the MNO network <NUM> sends an RX split request to the UE <NUM> requesting that the UE <NUM> allocate a first RX channel to the MNO network <NUM> and a second RX channel to the NPN <NUM>.

At <NUM>, the UE <NUM> starts to split the RX channel allocation by allocating the first RX channel to the MNO network <NUM> and the second RX channel to the NPN <NUM>. At <NUM>, the UE <NUM> sends a split confirmation message to the MNO network <NUM>. At <NUM>, the UE <NUM> receives MBMS traffic from the NPN <NUM>. At <NUM>, UE <NUM> exchanges uplink/downlink traffic with the MNO network <NUM>.

<FIG> illustrates a flowchart <NUM> of a procedure of a UE during a network-driven RX channel split. <FIG> does not contain all of the features required by the claimed invention. In step <NUM>, the UE <NUM> registers to the NPN <NUM>. In step <NUM>, the UE establishes a unicast communication tunnel with the NPN <NUM> on top of the MNO network <NUM>. In step <NUM>, the UE <NUM> receives a split indication/request from the NPN <NUM> or the MNO network <NUM>. In step <NUM>, the UE <NUM> self-configures to receive MBS service by configuring a first RX channel for the MNO network <NUM> and a second RX channel for the NPN <NUM>. In particular embodiments, the UE <NUM> may send a confirmation message to the NPN <NUM> or the MNO network <NUM> acknowledging receipt of the split indication/request.

In step <NUM>, the UE <NUM> begins receiving the MBS from the NPN <NUM> using the first RX channel and data from the MNO network <NUM> using the second RX channel. In step <NUM>, the UE <NUM> continues to use the TX channel of the UE <NUM> to send data to the MNO network <NUM>, and the established tunnel to send data to the NPN <NUM>.

<FIG> illustrates a flowchart <NUM> of operations of a UE according to an embodiment. In the embodiment, the UE is configured to communication with a first wireless network associated with a first base station and a second wireless network associated with a second base station. In step <NUM>, the UE establishes a communication tunnel with the first base station over a transmit chain (TX chain) of the user equipment. In the embodiment, the TX chain is synchronized with the second base station. The communication tunnel established between the first wireless network and the second wireless network allows the UE to communicate with the first wireless network associated with the first base station via the second wireless network associated with the second base station.

In step <NUM>, the UE transmits, via the TX chain of the UE, an uplink signal to the first wireless network associated with the first base station or the second wireless network associated with the second base station. According to the invention, the uplink signal includes information indicative of a first receive chain (RX chain) of the UE being synchronized to the first base station and a second RX chain of the UE being synchronized to the second base station. The UE receives a request from the first base station or the second base station requesting the UE to synchronize the first RX chain of the UE to the first base station and synchronize the second RX chain of the UE to the second base station. In an embodiment, the synchronizing of the first RX chain and the second RX chain is responsive to receiving the request. In an embodiment, the request further requests the UE to synchronize the TX chain to one or more of the first base station or the second base station. In another embodiment not according to the claimed invention, the synchronizing of the first RX chain and the second RX chain is initiated by the UE.

In an embodiment, the uplink signal further includes an indication of a start time for the UE to receive at least one of first data from the first base station or second data from the second base station.

In step <NUM>, the UE transmits uplink traffic for the first wireless network and the second wireless network to the second base station via the TX chain of the UE. In an embodiment, the uplink signal transmitted to the first base station uses the communication tunnel. In an embodiment, data associated with the uplink signal to the first base station is encapsulated in an over-the-top (OTT) internet protocol (IP) packet.

In an embodiment, the information further includes an indication that the TX chain of the UE will be synchronized with the second base station only, and the uplink data to the first wireless network passes through the second wireless network associated with the second base station.

In an embodiment, the UE transmits the uplink signal to an application server and the second wireless network associated with the second base station. In the embodiment, the application server and the second wireless network are configured to notify the first base station of the synchronizing of the first RX chain and the second RX chain.

In an embodiment, the first base station is associated with one of a mobile network operator (MNO) network or a non-public network (NPN). In an embodiment, the second base station is associated with one of a mobile network operator (MNO) network or a non-public network (NPN).

In an embodiment, the first base station is configured to provide one or more of a mobile broadcast service (MBS), unicast service, or other services to the UE. In another embodiment, the synchronizing of the first RX chain and the second RX chain are responsive to the UE receiving user and control traffic from the first wireless network and the second wireless network, respectively.

<FIG> illustrates a diagram of a system <NUM> for a UE <NUM> to establish a communication channel with an NPN via a public network, wherein such a system for a UE is not covered by the claimed invention. In the embodiment illustrated in <FIG>, the NPN is a standalone NPN (SNPN) and the public network is a PLMN. The UE <NUM> includes a first RX 910A, a second RX 910B, and a TX <NUM>. The UE <NUM> further includes a PLMN application <NUM>, a PLMN communication module <NUM>, an SNPN application <NUM>, and a SNPN communication module <NUM>. The PLMN includes a PLMN Next-Generation Radio Access Network (NG-RAN) <NUM> and a PLMN <NUM> core (5GC) <NUM>. The SNPN includes a SNPN NG-RAN <NUM>, a SNPN Non-3GPP Interworking Function (N3IWF) <NUM>, and a SNPN 5GC <NUM>. In particular embodiments, the UE <NUM> is in overlapped coverage areas served by the both the PLMN NG-RAN <NUM> and the SNPN NG-RAN <NUM>.

In the embodiment, N3IWF <NUM> provides an interworking gateway to allow the UE <NUM> to send and receive data to and from two different wireless networks (e.g., the PLMN and the SNPN) simultaneously with a single transmission channel (TX <NUM>) and two receiving channels (RXs 910A-910B). In the embodiment, a traffic split and routing mechanism is provided using the N3IWF <NUM>.

In an embodiment, UE <NUM> can be simultaneously attached and connected to both the SNPN and PLMN while keeping active data sessions with both networks at the same time, for example, during a live production with integrated audience services. In particular embodiments, the PLMN and the SNPN) can be operated by different operators, and the UE <NUM> may have separated subscriptions to both the PLMN and the SNPN. In an embodiment, the UE <NUM> shares the TX <NUM> for the UL traffic for both the SNPN and the PLMN, and splits the first RX 910A and the second RX 910B to each network for their DL user plane traffic. In particular, the first RX 910A receives PLMN downlink traffic (PLMN DL) directly from the PLMN NG-RAN <NUM>, and the second RX 910B receives SNPN downlink traffic (SNPN DL) directly from the SNPN NG-RAN <NUM>. The TX <NUM> of UE <NUM> is connected to the PLMN NG-RAN <NUM>, and the UE <NUM> sends PLMN UL traffic and SNPN UL traffic over the PLMN to SNPN N3IWF <NUM>. In one or more embodiments, the system <NUM> may support both multicast and unicast traffic.

Accordingly, the UE <NUM> is configured to receive SNPN DL user plane traffic from the PLMN NG-RAN <NUM> via the SNPN N3IWF <NUM> using the first RX 910A when it is needed. At the same time, the UE <NUM> can use the second RX 910B as well as the shared TX <NUM> to send and receive user PLMN traffic. Using this traffic split capability and selecting a network to which the TX will be camped may be configured by UE implementation or by operator policy. By splitting the traffic between going through a corresponding RAN for downlink traffic and the SNPN N3IWF <NUM> for uplink traffic, the UE <NUM> can simultaneously send data to both networks at the same time without suspending transmission in any network.

In one or more embodiments, when the UE <NUM> registers with one overlay network (e.g., the PLMN) using a gateway (e.g., N3IWF <NUM>), the UE <NUM> provides the underlay network (which provides underlay connectivity for a tunnel with the overlay network) with the connectively information of the overlay network in order to assist the overlay network to acquire QoS information from the underlay network. In particular embodiments, the connectivity information may include a Cell ID, a data session ID, or a timing advance (TA).

In a particular embodiment, the same SNPN Access and Mobility Management Function (AMF) is selected and user for the UE <NUM> for registrations with both networks via the SNPN NG-RAN <NUM> and SNPN N3IWF <NUM>. In an embodiment, the UE <NUM> registers to the SNPN via a <NUM> Uu interface for DL only traffic and registers to the SNPN via a <NUM> NWu interface for UL traffic and other DL traffics. During the registrations, the UE <NUM> provides a split indication to the network to assist the network in configuring the different traffic paths. In one or more embodiments, the split indication includes information indicating how the UE <NUM> wants to split traffic in the upper layer, for example, to maximize the data session for each path. In a particular embodiment, a Non-Access Stratum (NAS) control plane between the AMF and the UE <NUM> is implemented via the NWu interface. In particular embodiments, a session management function (SMF) and user plane function (UPF) utilize the split indication from UE <NUM> and network policies to create, configure and correlate the DL and UL traffic flows following defined session management procedures.

In one or more embodiments, the UE <NUM> is able to receive enhanced <NUM> core network paging responses while the UE <NUM> is also connected to the network with the N3IWF <NUM>. In a particular embodiment, the SNPN sends paging messages to the UE <NUM> via the Uu interface and the UE <NUM> responds to the paging messages via the NWu interface. If the UL data UE sent is a paging response or other NAS message, the data is transmitted via a signaling IPSec Security Association (SA). In an embodiment, if the UL data is normal user plane data, the UL data may be transmitted via an IPsec child SA. <FIG> illustrates a diagram of an embodiment not covered by the claimed invention of a process <NUM> for network notification of a UE-driven RX channel split and simultaneous connection with a NPN and a PLMN. The process <NUM> includes the UE <NUM> having a simultaneous connection with a PLMN and a SNPN. The PLMN includes the PLMN RAN <NUM>, a PLMN AMF <NUM>, and a PLMN UPF <NUM>. The SNPN includes the SNPN RAN <NUM>, the N3IWF <NUM>, a <NUM> AMF <NUM>, a <NUM> SMF <NUM>, and a UPF <NUM>.

In step <NUM>, the UE <NUM> switches its transmitter to the SNPN RAN <NUM> to conduct initial registration with the SNPN RAN <NUM> to be configured with an N2 interface between the SNPMN <NUM> and the <NUM> AMF <NUM>, and allow the UE <NUM> to synchronize with the SNPN RAN <NUM> for receiving data. It is assumed that the UE <NUM> is already registered in the PLMN, so that the UE <NUM> can suspend traffic transmission with the PLMN and use the transmitter to communicate with the SNPN.

In step <NUM>, the SNPN RAN <NUM> communicates the UE registration with the <NUM> AMF <NUM>. During the UE registration with the <NUM> AMF <NUM>, the UE <NUM> sends traffic split indication to indicate to the network that the UE <NUM> can split the <NUM> RX channels and <NUM> TX channel, and communicate corresponding UL/DL traffic via different paths after the network registration. During step <NUM>, the <NUM> AMF <NUM> may allocate a <NUM> Global Unique Temporary Identifier (<NUM>-GUTI) for the UE <NUM>, which the UE <NUM> will provide to the <NUM> AMF <NUM> during secondary registration via the N3WIF <NUM>. In step <NUM>, the <NUM> AMF <NUM> correlates these two phases of registrations together and send an N2 message to SNPN RAN <NUM> as a verification that the UE <NUM> has successfully registered to SNPN RAN <NUM>. The split indication indicates to the <NUM> AMF <NUM> that the NAS control plane between the <NUM> AMF <NUM> and the UE <NUM> is passed by the NWu interface. In a particular embodiment, the <NUM> AMF <NUM> will not accept any new protocol data unit (PDU) session establishment request until the UE <NUM> completes its secondary registration with the <NUM> AMF <NUM> via the NWu interface and is ready to receive and send data simultaneously.

In step <NUM>, the UE <NUM> switches its transmitter to the PLMN and resumes data transmission with the PLMN after the UE completes initial registration with the SNPN. In step <NUM>, the UE establishes an IPsec by creating a new PDU session or re-uses an existing PDU session of the PLMN to start second registration with the <NUM> AMF <NUM> via the N3IWF <NUM> to prepare the UL data path with the SNPN. In this step, the UE <NUM> provides the <NUM> AMF <NUM> with the traffic split indication, as well as the previously allocated <NUM>-GUTI. The N3IWF <NUM> or the <NUM> AMF <NUM> can use the split indication and <NUM>-GUTI to select the same AMF with which the UE <NUM> has conducted the first registration via the SNPN RAN <NUM>. With this <NUM>-GUTI, the <NUM> AMF <NUM> can associate this registration with the previous registration to identify the traffic split UE and skip some registration procedures if already conducted in step <NUM>. After step <NUM>, the <NUM> AMF <NUM> and the UE <NUM> establish a NAS connection via the N3IWF <NUM>.

In step <NUM>, the UE <NUM> initiates a PDU session establishment procedure with the <NUM> AMF <NUM> for DL/UL data services. Because the <NUM> AMF <NUM> has received traffic split information of the UE <NUM>, the <NUM> AMF <NUM> forwards the traffic split information to the <NUM> SMF <NUM> which later also forwards the traffic split information to the UPF <NUM>. In particular embodiments, the traffic split information can include indication information such as that all UL traffic will be established via the Uu interface, or different DL filters for different DL paths such as that some DL traffic pass through the NWu interface, while other traffic will pass through the Uu interface, etc. In particular embodiments, based on network policy, different PDU sessions may be created based upon on the direction of traffic (e.g., DL/UL). In particular embodiments, within one bi-directional PDU session different QoS flows that are direction specific may be configured.

In step <NUM>, based upon the traffic split information, the <NUM> AMF <NUM> sends a N2 PDU session establish request to the SNPN RAN <NUM> and the N3IWF <NUM> to set up downlink N2 with the SNPN RAN <NUM> and uplink with the N3IWF <NUM>. In step <NUM>, the <NUM> AMF <NUM> sends an N2 message to the SNPN RAN <NUM> to confirm the session establish request. If there is no NPN traffic to UE <NUM> for a predetermined time period, the UE <NUM> enters into an idle mode in the SNPN, and triggers an SNPN PDU session release with the <NUM> AMF <NUM> and the UPF <NUM>. When new SNPN downlink data is available for the UE <NUM> is available at the UPF <NUM>, in step <NUM>, <NUM> AMF <NUM> initiates a paging procedure and sends paging requests to the SNPN RAN <NUM>. Subsequently, in step <NUM> the SNPN RAN <NUM> broadcasts the paging requests.

In step <NUM>, after the paging request via the SNPN RAN <NUM>, the UE initiates a service request procedure with the SNPN via the N3IWF <NUM> over the PLMN by sending a paging response message. In a particular embodiment, the UE <NUM> may insert a "response to paging" as a reason code within a response to the paging request. In <NUM>, the N3IWF <NUM> forwards the paging response to the UPF <NUM> in the SNPN. In an embodiment, the UE <NUM> sends RRC messages to both the SNPN RAN <NUM> and the PLMN RAN <NUM> network with the single TX of the UE <NUM>.

In step <NUM>, after the PDU session in the SNPN is established, the SNPN UPF <NUM> starts to forward the DL data to the UE <NUM> via the SNPN RAN <NUM>, while the UE <NUM> transmits the UL data via the over-the-top IPsec tunnel with the N3IWF <NUM> through the PLMN (step <NUM>). During this period, the UE <NUM> can still exchange data with the PLMN freely without interruptions (step <NUM>).

In one or more embodiments, one or more network elements provide a QoS mapping between a session or path associated with a first network (e.g., a PLMN) and session or path associated with a second network (e.g., a SNPN) indicative of a QoS associated with each session. One or more embodiments further provide a QoS mapping change notification mechanism between the first network and the second network to indicate QoS changes to one or more of the first network or the second network that may be necessary or desired.

In a particular embodiment, a service level agreement (SLA) may be in effect between the SNPN and the PLMN, and a policy for PLMN and SNPN QoS mapping change notification may be provisioned in a PCF. After the SLA change level agreement is reached, the PCF provisions the new QoS mapping policy to a UPF, and a PCF in the SNPN provisions the new QoS mapping policy to a N3IWF.

In another particular embodiment, the PLMN sends a QoS downgrade notification to the SNPN via an NEF indicating that the SNPN UE traffic has an unacceptable negative impact on the PLMN, and that the QoS of the SNPN is to be downgraded. In the embodiment, the SNPN receives the QoS downgrade notification via an AF and NEF interface.

In one or more embodiments, a network element maintains a QoS mapping relationship between the PDU session in the PLMN and the IPsec with the SNPN which includes information indicative of a QoS associated with the PDU session path and the IPSec path. One or more embodiments provides a PLMN and SNPN QoS mapping change notification mechanism between the overlay and underlay network to indicate QoS changes that may be required due to UE traffic. For example, if a large amount of SNPN traffic with the UE <NUM> is detected that may have a negative impact on the PLMN, the PLMN may send a QoS mapping change notification including a QoS downgrade notification to the SNPN indicating that a QoS of the SNPN is to be downgraded. If the condition causing the QoS downgrade is determined to no longer be present, the PLMN may send a QoS mapping change notification including a QoS upgrade notification indicating that the QoS of the SNPN is to be upgraded. In particular embodiments, the QoS mapping change notification can be per N3IWF or a group of IPSec such as including all of the per-IPSec Child Security Associations related to the same QoS/service. In a particular embodiment, the QoS mapping change notification may include a <NUM> QoS Identifier (5QI).

<FIG> illustrates a block diagram of an embodiment of a processing system <NUM>, not covered by the claimed invention, for performing methods described herein, which may be installed in a host device. As shown, the processing system <NUM> includes a processor <NUM>, a memory <NUM>, and interfaces <NUM>-<NUM>, which may (or may not) be arranged as shown in <FIG>. The processor <NUM> may be any component or collection of components adapted to perform computations and/or other processing related tasks, and the memory <NUM> may be any component or collection of components adapted to store programming and/or instructions for execution by the processor <NUM>. In an embodiment, the memory <NUM> includes a non-transitory computer readable medium. The interfaces <NUM>, <NUM>, <NUM> may be any component or collection of components that allow the processing system <NUM> to communicate with other devices/components and/or a user. For example, one or more of the interfaces <NUM>, <NUM>, <NUM> may be adapted to communicate data, control, or management messages from the processor <NUM> to applications installed on the host device and/or a remote device. As another example, one or more of the interfaces <NUM>, <NUM>, <NUM> may be adapted to allow a user or user device (e.g., personal computer (PC), etc.) to interact/communicate with the processing system <NUM>. The processing system <NUM> may include additional components not depicted in <FIG>, such as long term storage (e.g., non-volatile memory, etc.).

In some embodiments, the processing system <NUM> is included in a network device that is accessing, or part otherwise of, a telecommunications network. In one example, the processing system <NUM> is in a network-side device in a wireless or wireline telecommunications network, such as a base station, a relay station, a scheduler, a controller, a gateway, a router, an applications server, or any other device in the telecommunications network. In other embodiments, the processing system <NUM> is in a user-side device accessing a wireless or wireline telecommunications network, such as a mobile station, a user equipment (UE), a personal computer (PC), a tablet, a wearable communications device (e.g., a smartwatch, etc.), or any other device adapted to access a telecommunications network.

In some embodiments, one or more of the interfaces <NUM>, <NUM>, <NUM> connects the processing system <NUM> to a transceiver adapted to transmit and receive signaling over the telecommunications network.

<FIG> illustrates a block diagram of an embodiment of a transceiver <NUM>, not covered by the claimed invention, adapted to transmit and receive signaling over a telecommunications network. The transceiver <NUM> may be installed in a host device. As shown, the transceiver <NUM> comprises a network-side interface <NUM>, a coupler <NUM>, a transmitter <NUM>, a receiver <NUM>, a signal processor <NUM>, and a device-side interface <NUM>. The network-side interface <NUM> may include any component or collection of components adapted to transmit or receive signaling over a wireless or wireline telecommunications network. The coupler <NUM> may include any component or collection of components adapted to facilitate bi-directional communication over the network-side interface <NUM>. The transmitter <NUM> may include any component or collection of components (e.g., up-converter, power amplifier, etc.) adapted to convert a baseband signal into a modulated carrier signal suitable for transmission over the network-side interface <NUM>. The receiver <NUM> may include any component or collection of components (e.g., down-converter, low noise amplifier, etc.) adapted to convert a carrier signal received over the network-side interface <NUM> into a baseband signal. The signal processor <NUM> may include any component or collection of components adapted to convert a baseband signal into a data signal suitable for communication over the device-side interface(s) <NUM>, or vice-versa. The device-side interface(s) <NUM> may include any component or collection of components adapted to communicate data-signals between the signal processor <NUM> and components within the host device (e.g., the processing system <NUM>, local area network (LAN) ports, etc.).

The transceiver <NUM> may transmit and receive signaling over any type of communications medium. In some embodiments, the transceiver <NUM> transmits and receives signaling over a wireless medium. For example, the transceiver <NUM> may be a wireless transceiver adapted to communicate in accordance with a wireless telecommunications protocol, such as a cellular protocol (e.g., long-term evolution (LTE), etc.), a wireless local area network (WLAN) protocol (e.g., Wi-Fi, etc.), or any other type of wireless protocol (e.g., Bluetooth, near field communication (NFC), etc.). In such embodiments, the network-side interface <NUM> comprises one or more antenna/radiating elements. For example, the network-side interface <NUM> may include a single antenna, multiple separate antennas, or a multi-antenna array configured for multi-layer communication, e.g., single input multiple output (SIMO), multiple input single output (MISO), multiple input multiple output (MIMO), etc. In other embodiments, the transceiver <NUM> transmits and receives signaling over a wireline medium, e.g., twisted-pair cable, coaxial cable, optical fiber, etc. Specific processing systems and/or transceivers may utilize all of the components shown, or only a subset of the components and levels of integration may vary from device to device.

It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by an establishing unit/module, a determining unit/module, an evaluating unit/module, a storing unit/module, a requesting unit/module, and/or a multiplexing unit/module. The respective units/modules may be hardware, software, or a combination thereof. For instance, one or more of the units/modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

It should be appreciated that one or more steps of the embodiment methods provided herein may be performed by corresponding units or modules. For example, a signal may be transmitted by a transmitting unit or a transmitting module. A signal may be received by a receiving unit or a receiving module. A signal may be processed by a processing unit or a processing module. Other steps may be performed by a registering unit/module, an establishing unit/module, a splitting unit/module, and/or a notification unit/module. The respective units/modules may be hardware, software, or a combination thereof. For instance, one or more of the units/modules may be an integrated circuit, such as field programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs).

Claim 1:
A method comprising:
establishing (<NUM>), by a user equipment, UE, a communication tunnel with a first base station over a transmit, TX, chain, the TX chain being synchronized with a second base station, wherein the communication tunnel allows the UE to communicate with a first wireless network associated with the first base station via a second wireless network associated with the second base station, wherein the first wireless network is a non-public network, NPN, and the second wireless network is a mobile network operator, MNO, network;
receiving, by the UE, a request from the first base station or the second base station requesting the UE to synchronize a first receive, RX, chain of the UE to the first base station to receive first traffic from the first wireless network and synchronize a second RX chain of the UE to the second base station to receive second traffic from the second wireless network;
transmitting (<NUM>), via the TX chain of the UE, an uplink signal to the first wireless network associated with the first base station or the second wireless network associated with the second base station, the uplink signal including information indicative of the first RX chain of the UE being synchronized to the first base station to receive the first traffic from the first wireless network and the second RX chain of the UE being synchronized to the second base station to receive the second traffic from the second wireless network; and
transmitting (<NUM>), by the UE, uplink traffic for the first wireless network and the second wireless network to the second base station via the TX chain of the UE.