SYSTEM AND METHOD FOR OFFLOADING DEVICES IN A CELLULAR NETWORK - Patent application

Abstract

The present disclosure generally relates to a system and method for offloading user equipment, and thus unicast and / or broadcast / multicast content of the user equipment, from one broadcast / multicast system to another broadcast / multicast system and vice versa based on multiple criteria. The system collects one or more data parameters from the user equipment in a first network system, identifies a number of user equipment to be offloaded based on the one or more data parameters, determines whether the identified number of user equipment meets one or more offload criteria, and triggers offloading of the identified number of user equipment from the first network system to a second network system. The system facilitates switching network systems seamlessly without any manual intervention of the user and provides continuous broadcast / multicast services.

Description

[Technical field]

[0001] Reservation of Rights Portions of the disclosure of this patent document contain material that is subject to intellectual property rights, including, but not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred to as the Owner). The Owner has no objection to the facsimile reproduction by anyone of this patent document or this patent disclosure as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the Owner.

[0002] FIELD OF THE DISCLOSURE Embodiments of the present disclosure relate generally to wireless communication technologies. In particular, the present disclosure relates to a system and method for offloading or onloading broadcast or multicast sessions to or from a cellular network. [Background technology]

[0003] The following description of related art may be intended to provide background information related to the field of the present disclosure. This section may include some aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is not intended as an admission of prior art, but is intended only to enhance the reader's understanding of the present disclosure.

[0004] Broadcast / Multicast Service, also referred to as BMS, is a method of sharing media content across a set of users using a common set of resources. Traditional broadcasters, such as television (TV) broadcasters, view broadcasting over cellular networks as a medium with non-cellular networks. In addition, over-the-top (OTT) application providers are also interested in broadcast technology in cellular networks as well as non-cellular dedicated broadcast channels. In such scenarios, broadcast and / or multicast data streams may be passed over multiple air interface technologies, such as, but not limited to, 3rd Generation Partnership Project (3GPP®) evolved Multimedia Broadcast Multicast Service (eMBMS) or Multicast / Broadcast Service (MBS), Digital Video Broadcasting Handheld (DVB-H), Advanced Television Systems Committee 3.0 (ATSC 3.0), etc.

[0005] Existing mechanisms do not allow for switching between broadcast and / or multicast services across access technologies, requiring users to manually choose a broadcast channel as a one-time activity during a subscription.

[0006] Furthermore, existing 3GPP broadcast solutions require service providers to reserve a subset of licensed spectrum purchased for a specific purpose, for example, in the fourth generation (4G), 5 MHz of licensed spectrum needs to be reserved for eMBMS purposes, which means that the available bandwidth for regular mobile broadband users becomes limited. Such reservation of radio resources can be very expensive, potentially affecting the Quality of Service (QoS) of existing mobile broadband unicast users. Summary of the Invention [Problem to be solved by the invention]

[0007] Therefore, there is a need in the art for a system and method to address the problem of broadcast / multicast offload / onload across multiple channels or access networks based on multiple criteria. [Means for solving the problem]

[0008] This section is provided to introduce in a simplified form certain objects and aspects of the disclosure that are further described below in the Detailed Description. This Summary is not intended to identify key features or the scope of the claimed subject matter.

[0009] In one aspect, the present disclosure provides a system for offloading user equipment, the system including one or more processors and a memory operably coupled to the one or more processors, the memory including processor-executable instructions that, when executed, cause the one or more processors to collect one or more data parameters from user equipment, the user equipment being communicatively coupled to the system, identify a number of user equipment to be offloaded based on the one or more data parameters, determine whether the identified number of user equipment meets one or more offload criteria, and trigger an offload of the identified number of user equipment from a first network system to a second network system based on a determination that the identified number of user equipment meets the one or more offload criteria.

[0010] In one embodiment, the one or more data parameters include at least one of a first count of a number of user equipment in a particular area that are viewing particular broadcast or multicast content, user equipment that are subscribed to the system, a first threshold corresponding to a second count of a number of user equipment that can save a particular bandwidth, a second threshold corresponding to the bandwidth saved, and a third threshold corresponding to the signal strength required for offloading.

[0011] In one embodiment, the one or more offload criteria include a specified number of user equipment being greater than a first threshold. In one embodiment, the one or more offload criteria include a specified number of user equipment being subscribed to the system. In one embodiment, the one or more offload criteria include a bandwidth saved by the specified number of user equipment being greater than a second threshold. In one embodiment, the one or more offload criteria include a signal strength of the specified number of user equipment being greater than a third threshold.

[0012] In one embodiment, the first network system includes a cellular network system and the second network system includes a non-cellular network system.

[0013] In one embodiment, the memory includes processor-executable instructions that, when executed, cause the one or more processors to monitor media content of user equipment and determine, based on the monitored media content, a type of advertisement to be displayed on the user equipment.

[0014] In one embodiment, the memory includes processor-executable instructions that, when executed, cause one or more processors to trigger offloading by being configured to relay media content through the system to a specified number of user equipment. In another embodiment, the memory includes processor-executable instructions that, when executed, cause one or more processors to trigger offloading by being configured to communicate an endpoint node to a content provider of the media content for transmission of the content to the specified number of user equipment.

[0015] In one embodiment, the memory includes processor-executable instructions that, when executed, cause one or more processors to assign a unique identifier to each of a specified number of user equipment upon successful subscription to the system.

[0016] In another aspect, the present disclosure provides a method for offloading user equipment, the method including: collecting, by a processor, one or more data parameters from user equipment in a first network system, identifying, by the processor, a number of user equipment in the first network system to be offloaded based on the one or more data parameters, determining, by the processor, whether the identified number of user equipment meets one or more offload criteria, and triggering, by the processor, an offload of the identified number of user equipment from the first network system to a second network system based on the determination that the identified number of user equipment meets the one or more offload criteria.

[0017] In one embodiment, the method includes relaying, by the processor, the media content via a broadcast or multicast offload / onload system to a specified number of user equipment. In another embodiment, the method includes communicating, by the processor, the endpoint node to a content provider of the media content for content transmission to the specified number of user equipment.

[0018] In another aspect, the present disclosure provides a user equipment in a first network system for offloading broadcast or multicast content. The user equipment includes one or more processors communicatively coupled to the offload system. The one or more processors of the user equipment are configured to send a subscription request to the offload system, receive a subscription response from the offload system, the subscription response including a unique identifier associated with the user equipment, and provide one or more data parameters to the offload system in response to receiving the subscription response. The offload system includes a processor configured to identify user equipment for offloading based on the one or more data parameters, determine whether the user equipment meets one or more offload criteria, and trigger offloading of the user equipment from the first network system to the second network system based on a determination that the user equipment meets the one or more offload criteria.

[0019] In one aspect, the present disclosure provides a non-transitory computer-readable medium including processor-executable instructions to cause a processor to collect one or more data parameters from user equipment, identify a number of user equipment to be offloaded based on the one or more data parameters, determine whether the identified number of user equipment meets one or more offload criteria, and trigger an offload of the identified number of user equipment from a first network system to a second network system based on a determination that the identified number of user equipment meets the one or more offload criteria.

[0020] Purpose of this Disclosure An objective of the present disclosure is to offload or onload media sessions across multiple channels or access networks.

[0021] The objective of the present disclosure is to intelligently and seamlessly switch network systems without any manual intervention and provide continuous broadcast / multicast services to end users.

[0022] An objective of the present disclosure is to make efficient use of licensed radio resources.

[0023] The objective of this disclosure is to save wireless bandwidth corresponding to user offloading.

[0024] An objective of the present disclosure is to provide a better quality of service to end users.

[0025] The accompanying drawings, which are incorporated herein and form a part of this disclosure, depict exemplary embodiments of the disclosed method and system, with like reference numbers referring to the same parts throughout the different drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed on clearly illustrating the principles of the present disclosure. Some drawings may use block diagrams to illustrate components and may not depict the internal circuitry of each component. It will be appreciated by those skilled in the art that the disclosure of such drawings includes a disclosure of electrical components, electronic components or circuitry commonly used to implement such components. [Brief description of the drawings]

[0026] [Figure 1] FIG. 1 is an example block diagram highlighting functional layers for delivery of Multimedia Broadcast Multicast Service (MBMS) based services. [Diagram 2] 1 is an exemplary representation of an end-to-end MBMS architecture with an xMB reference point. [Figure 3A] 1 is an exemplary representation of end-to-end eMBMS for a 4G network, in accordance with an embodiment of the present disclosure. [Figure 3B] 1 is an exemplary representation of end-to-end eMBMS for a 5G network, in accordance with an embodiment of the present disclosure. [Figure 4] FIG. 1 illustrates an example network architecture in which or in conjunction with which the systems of the present disclosure may be implemented, according to embodiments of the present disclosure. [Diagram 5] 1 is an exemplary detailed representation of a computer system according to or in conjunction with which embodiments of the present disclosure may be utilized. [Figure 6] FIG. 1 is an example system flow diagram supporting broadcast / multicast offload from a cellular network to a non-cellular broadcast network and vice versa, according to an embodiment of the disclosure. [Figure 7]FIG. 1 illustrates an exemplary architecture for transferring media streams from a content provider to an end user via a Broadcast / Multicast Offload / Onload System (BMOS), according to an embodiment of the present disclosure. [Figure 8] FIG. 1 is an exemplary block diagram of a system architecture for transferring media streams from a content provider to an end user, according to an embodiment of the present disclosure. [Figure 9] 1 is another exemplary representation of a BMOS architecture, according to an embodiment of the present disclosure. [Figure 10] FIG. 2 is an exemplary method flow diagram illustrating a method for offloading / onloading a user, according to an embodiment of the present disclosure. [Figure 11] 1 is an exemplary block diagram representation highlighting one or more interfaces between multiple modules and a BMOS system, according to an embodiment of the present disclosure. [Figure 12] 1 is another example block diagram representation highlighting one or more interfaces between multiple modules and a BMOS system, according to an embodiment of the present disclosure. [Figure 13A] 1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. [Figure 13B] 1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. [Figure 13C] 1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. [Figure 13D] 1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. [Figure 13E] 1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. [Figure 13F]1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. [Figure 13G] 1 is an exemplary sequence diagram representation for a call flow in a network implementing the proposed method according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] The above will become more apparent from the following more detailed description of the present disclosure.

[0028] In the following description, for purposes of explanation, various specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure. However, it will be apparent that the embodiments of the present disclosure may be practiced without these specific details. Some features described below may each be used independently of each other or with any combination of other features. Individual features may not address all of the problems described above, or may address only some of the problems described above. Some of the problems described above may not be fully addressed by any of the features described herein.

[0029] The following description provides only exemplary embodiments and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the following description of exemplary embodiments provides those skilled in the art with an enabling description for implementing the exemplary embodiments. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the present disclosure as described.

[0030] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by those skilled in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form so as not to obscure the embodiments with unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail so as to avoid obscuring the embodiments.

[0031] It should also be noted that the particular embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe operations as a sequential process, many of the operations may be performed in parallel or simultaneously. Additionally, the order of operations may be rearranged. A process terminates when its operations are completed, but may have additional steps not included in the diagram. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to the function returning to a calling function or a main function.

[0032] The words "exemplary" and / or "demonstrative" are used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as "exemplary" and / or "demonstrative" should not necessarily be construed as preferred or advantageous over other aspects or designs, nor is it intended to exclude equivalent exemplary structures and techniques known to those skilled in the art. Furthermore, to the extent the terms "includes," "has," "contains," and other similar terms are used in either the detailed description or the claims, such terms are intended to be inclusive, similar to the term "comprising" as an open transitional term, without excluding any additional or other elements.

[0033] References throughout this specification to "one embodiment" or "an embodiment" or "an instance" or "one instance" mean that a particular feature, structure, or characteristic described with respect to an embodiment is included in at least one embodiment of the disclosure. Thus, the appearances of the phrase "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0034] The terms used herein are merely for the purpose of describing particular embodiments and are not intended to limit the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising", as used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0035] Several terms and phrases are used throughout this disclosure and have the following meanings in the context of the continuing disclosure.

[0036] The term "broadcast" can refer to the distribution of audio or video content to a distributed audience in a one-to-many model, via any electronic mass communication medium, but typically one that uses the electromagnetic spectrum (radio waves).

[0037] The term "multicast" can refer to group communication in which a data transmission is addressed to a group of destination computers simultaneously. Multicast can be a one-to-many or a many-to-many delivery.

[0038] The term "Broadcast / Multicast Service" is commonly known as BMS, which may refer to a method of sharing media content across a set of users using a common set of resources.

[0039] The term "3GPP" stands for Third Generation Partnership Project, or 3GPP, a collaborative project between a group of telecommunications associations with the initial goal of developing globally applicable specifications for third-generation (3G) mobile systems. 3GPP specifications cover cellular telecommunications technologies, including radio access, core networks, and service capabilities, providing a complete system description for mobile telecommunications. 3GPP specifications also provide hooks for non-radio access to the core network, and for networking with non-3GPP networks.

[0040] The term "Multimedia Broadcast Multicast Service (MBMS)" refers to the existing 3GPP point-to-multipoint interface specification for cellular networks, designed to provide efficient distribution of broadcast and multicast services both within a cell and within the core network. For broadcast transmissions across multiple cells, the specification defines transmission over a single frequency network configuration. When the transmission is distributed over a Long Term Evolution (LTE) network, the specification is called evolved Multimedia Broadcast Multicast Service (eMBMS). eMBMS is also known as LTE Broadcast.

[0041] The term "content provider / multicast broadcast source" may provide discrete and continuous media as well as service description and control data to the Broadcast Multicast Service Center (BM-SC) to provide the service at once.

[0042] The term "Access and Mobility Management Function (AMF)" may refer to a functional module that terminates the control plane of different access networks on the 5G Core Network (5GC) and controls which UEs can access the 5GC to exchange traffic with the DN.

[0043] The term "5G Network Exposed Function (NEF)" facilitates secure, robust and developer-friendly access to the exposed network services and capabilities of 5G networks, enabling third-party developers and enterprises to create and orchestrate composite or dedicated network services on demand.

[0044] Figure 1 shows an exemplary block diagram (100) illustrating separate functional layers for the delivery of MBMS-based services. In particular, Figure 1 illustrates three functional layers for the delivery of MBMS-based services. The three layers may include bearer services (102), delivery methods (104), and user services or applications (106).

[0045] The first layer may include bearer services (102). Those skilled in the art will appreciate that the bearer services (102) provide a mechanism by which Internet Protocol (IP) data may be transported. One such type of bearer may be an MBMS bearer, which may be used to transport multicast and broadcast traffic in an efficient one-to-many manner and may be the basis of MBMS-based services. MBMS bearers may be used together with unicast bearers in providing a full service capability.

[0046] Referring to FIG. 1, the second layer may include a distribution method (104). When MBMS content is distributed to a receiving user service or user application, one or more distribution methods (104) may be used, such as, but not limited to, download, streaming, transparent, and group communication. The second layer, i.e., the distribution method (104), provides security and key distribution, reliability control through forward error correction techniques, and related distribution procedures such as file repair, delivery confirmation, etc. The distribution method (104) may use bearer services (102), such as MBMS bearers and unicast bearers (point-to-point bearers), through a set of MBMS-related procedures.

[0047] Referring to FIG. 1, the third layer may include user services or user applications (106). Different applications (106) may impose different requirements when delivering content to MBMS users and may use different delivery methods (104). For example, messaging applications such as Multimedia Messaging Service (MMS) may use a download delivery method, streaming applications such as Packet Switched Streaming Service (PSS) may use a streaming delivery method, and group communication applications such as Mission Critical Push-to-Talk (MCPTT) may use a group communication delivery method. Those skilled in the art will recognize that MBMS user services (106) may use one or several delivery methods (104) simultaneously.

[0048] 2 shows an architecture (200) with xMB reference points illustrating content delivery from a content provider (208) / content source (210) to an MBMS client (204) via a content receiver application (202). The content provider (208) may provide discrete and continuous media as well as service descriptions and control data to the BM-SC (206) to provide services at once. In one embodiment, the content provider (208) may provide media formats to the BM-SC (206) typically through the xMB interface and initiate services and sessions through the xMB interface.

[0049] 2, the content receiver application (202) is an MBMS-aware application, i.e., an application in user space that communicates with the MBMS client (204) through an application programming interface (API). The MBMS client (204) may provide API and protocol-related methods to expose related functionality to the content receiver application (202).

[0050] Furthermore, when using the xMB reference point, the content provider (208) may invoke procedures supported by the BM-SC (206) to set up and manage the MBMS user service from the BM-SC (206) to the MBMS client (204). The BM-SC (206) may define endpoints with all supported procedures on the xMB interface, and these procedures may then be translated into SGmb procedures for the interface between the BM-SC (206) and the MBMS Gateway (GW). The BM-SC (206) may forward received content for unicast delivery (212) to the MBMS client (204) for the appropriate function. For example, the MBMS user service fallback is unicast delivery (212).

[0051] Furthermore, in 4G and 5th generation (5G) networks, the content provider (208) may always be located on the network infrastructure side, and the MBMS client (204) and the content receiver application (202) may be located on the UE or device side. The UE may also act as a content source for broadcasting or multicasting content. However, the UE may have to be authenticated by the BM-SC (206) before it can initiate any content transfer to the BM-SC (206).

[0052] Figure 3A shows an end-to-end eMBMS architecture for a 4G network (300). Additionally, also with reference to Figure 3B, a projected end-to-end MBMS architecture for a 5G network (330) is shown.

[0053] In particular, Figure 3A shows a content provider or application service provider (320) providing content to an MBMS client (304). The MBMS client (304) is associated with a UE modem (306), which is further coupled to an evolved UMTS terrestrial radio access network (E-UTRAN) (308). The E-UTRAN (308) is associated with a multicast coordination entity (MCE) (310), which may be further connected to an MBMS-GW (314) through a mobility management entity (MME) (312). Using the xMB reference point, the content provider (320) may invoke procedures supported by the BM-SC (316) to set up and manage MBMS user services from the BM-SC (316) to the MBMS client (304). The BM-SC (316) is an endpoint connecting the MBMS-GW (314) and the Service Capability Exposure Function (SCEF) (318).

[0054] Similarly, in FIG. 3B, for a 5G network, the MME (312) is replaced by an Access Mobility Function module (AMF) (332), the E-UTRAN (308) is replaced by a gNodeB (334), and the SCEF (318) is replaced by a NEF (336).

[0055] Existing 3GPP broadcast solutions require service providers to reserve a subset of licensed spectrum purchased for a specific purpose, however such a scenario limits the bandwidth available for typical mobile broadband users.

[0056] Furthermore, broadcast bandwidth remains unused due to non-use of digital terrestrial TV for significant periods of time. In addition, existing solutions do not provide a mechanism for switching broadcast / multicast services across access technologies, which forces users to manually select a broadcast channel as a one-time activity during a subscription. Existing technologies and methodologies do not solve the above-mentioned problems.

[0057] Accordingly, the present disclosure relates to a Broadcast / Multicast Offload / Onload System (BMOS) that enables offloading / onloading unicast and / or broadcast / multicast data streams or sessions from one broadcast / multicast system to another broadcast / multicast system and vice versa based on multiple factors including, but not limited to, subscription data, user interests, medium / channel availability, etc.

[0058] Furthermore, the disclosed solution allows for seamless medium switching without any manual user intervention, providing continuous broadcast / multicast services. Thus, the present disclosure allows for efficient use of licensed radio resources since there is no need to reserve radio resources. Furthermore, offloading certain unicast users saves radio bandwidth and ultimately provides better QoS to users.

[0059] Various embodiments throughout the disclosure will be described in more detail with reference to FIGS.

[0060] 4 illustrates an example network architecture (400) in or with which the BMOS (410) (hereinafter referred to as the system) of the present disclosure may be implemented. As shown, the network architecture (400) includes a system (410) for offloading / onloading unicast and / or broadcast / multicast data streams or sessions from one broadcast / multicast system to another broadcast / multicast system and vice versa in the network (406) based on a number of factors including, but not limited to, subscription data, user interests, medium / channel availability, etc. In one embodiment, the system (410) broadcasts or multicasts content in the network (406) to users associated with one or more computing devices or UEs (402-1, 402-2...402-N) (individually referred to as UEs (402) and collectively referred to as UEs (402)).

[0061] Referring to FIG. 4, the system (410) may be operatively coupled to a centralized server (412) associated with an entity (408). In another exemplary embodiment, the centralized server (412) may include or comprise, by way of example and not limitation, a standalone server, a server blade, a server rack, a bank of servers, a server farm, hardware supporting a cloud service or part of a system, a home server, hardware running a virtual server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, any combination thereof. In one embodiment, the entity (408) may include, but is not limited to, a vendor, a network operator, a company, an organization, a university, a lab facility, a business, a defense facility, or any other facility that provides content.

[0062] Additionally, the system (410) may be communicatively coupled to one or more UEs (402) via a network (406) having a plurality of nodes (404). In one embodiment, the network (406) may include at least one of a 4G network, a 5G network, and the like.

[0063] In an exemplary embodiment, network (406) may include at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, of one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, etc. Network (406) may also include, by way of example and not limitation, one or more of a wireless network, a wired network, the Internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad-hoc network, an infrastructure network, a public switched telephone network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0064] In one embodiment, the system (410) may support multicast / broadcast offload from a cellular network to a non-cellular broadcast network and vice versa. The system (410) may include an offload / onload function or entity consisting primarily of a broadcast offload / onload decision entity (not shown in FIG. 4) responsible for determining whether a unicast / broadcast session should be offloaded to a fiber or wired connection. In one embodiment, the system (410) may further include an intelligent data collection entity (including access network monitoring) (not shown in FIG. 4) that interfaces with the underlying broadcast / unicast network to enforce the decision made by the broadcast offload / onload decision entity. In one embodiment, the system (410) may include a mapping entity (not shown in FIG. 4) that links cellular network sessions to broadcast sessions in the non-cellular network (backchannel linking). In particular, the mapping entity associates broadcast network users with cellular network uplink channels. In one embodiment, the system (410) may include a monitoring entity (not shown in FIG. 4) that monitors the content type and determines the insertion and type of advertisements. In one embodiment, the system (410) may be implemented in, but is not limited to, an electronic device, a mobile device, a server, etc. Such servers may include, but are not limited to, a standalone server, a remote server, a cloud server, a dedicated server, etc.

[0065] 4, in some embodiments, the UE (402) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, etc.), a wearable computing device (e.g., a head mounted display computing device, a head mounted camera device, a wristwatch computing device, etc.), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playback device, a portable gaming system, and / or any other type of computing device having wireless communication capabilities, etc. In one embodiment, the UE (402) may communicate with the system (410) via a set of executable instructions resident on any operating system. In one embodiment, the UE (402) may include, but is not limited to, any electric, electronic, electromechanical or electrical device or combination of one or more of the above devices, such as a virtual reality (VR) device, an augmented reality (AR) device, a laptop, a general purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device, where the computing device may include one or more built-in or externally coupled accessories, including, but not limited to, a camera, an audio aid, a microphone, a keyboard, an input device for receiving input from a user, e.g., a visual aid device such as a touchpad, a touch-enabled screen, an electronic pen, etc. It may be appreciated that the UE (402) may not be limited to the devices mentioned, and various other devices may be used.

[0066] In some embodiments, one of the UEs (402) may act as a content provider or source. In another implementation, the entity (408) may provide content to the UEs (402) via the system (410). In yet another embodiment, the UEs (402) may act as content receivers.

[0067] In some embodiments, the network (406) may include a number of nodes (404), such as, but not limited to, base stations or other access points that provide wireless connectivity to a corresponding number of cells (not shown in FIG. 4). Those skilled in the art will recognize that the actual geographical extent of a cell may depend on factors including, but not limited to, geography, topology, environmental conditions, transmit power, or transmit power distribution, and thus may be irregular or time-varying. In one embodiment, the number of nodes (404) may be any or a combination of, but not limited to, eNodeBs, small cells, and the like.

[0068] In some embodiments, the network (406) may include a controller (not shown in FIG. 4) that may be used to configure a cell for unicast or multicast / broadcast transmissions, such as transmission of MBMS. As used herein, the term "multicast" may be used to refer to the transmission of information over a channel or group of channels that may be received or accessed by multiple users, such as UEs (402) that subscribe to MBMS. As used herein, the term "broadcast" may also be used to refer to the transmission of information over a channel or group of channels that may be received or accessed by multiple UEs (402). Broadcast and multicast may be distinguished, at least in part, because multicast may provide the ability to form a multicast group of users. As used herein, the term "broadcast / multicast session" should be understood to refer to a session that may be used to carry broadcast or multicast transmissions. Examples of broadcast / multicast sessions may include, but are not limited to, an MBMS session or an eMBMS session. Furthermore, a broadcast / multicast session may not necessarily carry either a broadcast or multicast transmission at any particular time, since the transmission may depend on available programming and the selection made by the individual users. Broadcast or multicast may be contrasted with unicast, where information may be transmitted from a base station or access point to a single user and other users are not permitted or able to access the unicast information. A cell may broadcast or unicast data to a user, such as a UE (402). As used herein, the term "user" may refer to a wireless device, such as a UE (402), or a human using a UE (402).

[0069] Wireless communication standards such as Long Term Evolution (LTE), LTE Advanced, 4G, Next Generation (New Radio (NR)), 5G, etc. may support broadcast services such as MBMS or eMBMS. MBMS services broadcast or multicast data from a base station over an air interface on a channel that can be received by one or more UEs (402). eMBMS may be an enhanced version of MBMS that provides additional features such as architecture and physical layer enhancements that enable the eMBMS service to carry multimedia information to the UEs (402). eMBMS services may transmit information toward the UEs (402) by broadcasting or multicasting to the UEs (402) in a Multicast Broadcast Single Frequency Network (MB-SFN) mode. SFN may be generally understood to be a broadcast network in which two or more transmitters send the same signal simultaneously or in parallel over the same frequency channel. The MB-SFN mode may be used to transmit the same information from all of the base stations in a selected group of cells or coverage area. Each of the base stations in the MB-SFN area transmits the same content time-aligned in the same resource block of the physical layer. Constructive combination of signals transmitted by different base stations within an MB-SFN area increases the received signal strength and reduces interference within cells of the MB-SFN area.

[0070] Although Figure 4 illustrates example components of network architecture (400), in other embodiments, network architecture (400) may include fewer components, different components, differently arranged components, or additional functional components than those illustrated in Figure 4. Additionally or alternatively, one or more components of network architecture (400) may perform functions described as being performed by one or more other components of network architecture (400).

[0071] For example, the network architecture (400) may include several layers (not shown in FIG. 4 ), including, but not limited to, a network platform (e.g., servers, databases), a network infrastructure (e.g., fiber network, cellular towers, cable network, switches), computing devices (e.g., client devices, computers, smartphones, tablets), operating systems, applications (e.g., social network applications, e-commerce applications, third party applications, operator applications, carrier applications), etc. The network platform may provide content and services to the UEs through the network infrastructure and the computing devices. The computing devices may include device hardware (e.g., computers, smartphones, and tablets) and may be associated with particular data plans offered by one or more network operators.

[0072] Further, in one embodiment, the system (410) may include one or more processors coupled with a memory, where the memory may store instructions that, when executed by the one or more processors, may cause the system (410) to perform offload / onload of broadcast or multicast content in a network. An exemplary representation of a system (410) for such purposes, according to an embodiment of the present disclosure, is shown in FIG. 5. In one embodiment, the system (410) may be implemented in a non-transitory computer-readable medium that includes processor-executable instructions that may cause the one or more processors (502) to perform steps of the methods disclosed herein. In one embodiment, the system (410) may include one or more processors (502). The one or more processors (502) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitry, and / or any device that processes data based on operational instructions. The one or more processors (502) may be configured to fetch and execute computer-readable instructions stored in a memory (504) of the system (410), among other capabilities. The memory (504) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium that may be fetched and executed to create or share data packets via a network service. The memory (504) may comprise any non-transitory storage device, including, for example, a volatile memory, such as a random access memory (RAM), or a non-volatile memory, such as an electrically erasable programmable read-only memory (EPROM), flash memory, or the like.

[0073] In one embodiment, the system (410) may include an interface (506). The interface (506) may comprise various interfaces, for example, interfaces for data input and output devices, referred to as input / output (I / O) devices, storage devices, etc. The interface (506) may facilitate communications for the system (410). The interface (506) may also provide a communication path for one or more components of the system (410). Examples of such components include, but are not limited to, a processing unit / processing engine (508) and a database (510).

[0074] The processing unit / processing engine (508) may be implemented as a combination of hardware and programming (e.g., programmable instructions) for implementing one or more functions of the processing engine (508). In the examples described herein, such a combination of hardware and programming may be implemented in a number of different ways. For example, the programming for the processing engine (508) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (508) may comprise processing resources (e.g., one or more processors) for executing such instructions. In this example, the machine-readable storage medium may store instructions that, when executed by the processing resources, implement the processing engine (508). In such an example, the system (410) may include a machine-readable storage medium that stores instructions and processing resources for executing the instructions, or the machine-readable storage medium may be separate but accessible to the system (410) and the processing resources. In other examples, the processing engine (508) may be implemented by electronic circuitry. In one aspect, the database (510) may comprise data that may be either stored or generated as a result of functions implemented by any of the components of the processor (502) or the processing engine (508).

[0075] The processing engine (508) may include one or more modules / engines, such as, but not limited to, an intelligent data collector engine (512), a broadcast offload / onload decision engine (514) (hereinafter referred to as the decision engine (514)), and other units or other engines (516).

[0076] In one embodiment, the system (410) may support multicast / broadcast offload from a cellular network to a non-cellular broadcast network and vice versa. In one embodiment, the intelligent data collector engine (512) may collect required data, such as, but not limited to, data from UEs connected to and subscribed to the system (410), data from access or core network entities, data from content providers, etc.

[0077] In one embodiment, the intelligent data collector engine (512) may collect, without limitation, the number of users (N User ), whether the user is subscribed to the system (410), i.e., for offload or onload functionality (S User ), whether a particular piece of content is subscribed to the system (410), i.e., for offload or onload functionality (S cp ), whether the signal strength as perceived by the user or UE is sufficient for a particular content to be offloaded for a period of time (UE rsrp ), total bandwidth saved by offloading, technologies supported by the UE, actions initiated by the end user, etc.

[0078] In one embodiment, based on the data collected by the intelligent data collector engine (512), the decision engine (514) may use data analytics to analyze the collected data. In one embodiment, the one or more processors (502) may be configured to identify a number of users for offloading based on the collected data and determine whether the identified number of users meet one or more offloading criteria. In one embodiment, the decision engine (514) may determine the number of users (N User ) is the user's threshold (ThN User ), and, as a result, whether the saved bandwidth (Bw) is greater than a bandwidth threshold (ThBw). Further, in one embodiment, the one or more processors (502) may be configured to determine whether a signal strength (Rx) perceived by a UE associated with the user is greater than a signal strength threshold (ThRx). If one or more offloading criteria, such as those described above, are met, the one or more processors (502) may be configured to offload a specified number of users from one network to another network via the system (410).

[0079] In one embodiment, based on data collected by the intelligent data collector engine (512) and decisions made by the decision engine (514), the one or more processors (502) may be configured to offload user or data therefrom, for example, from a 3GPP unicast to a non-3GPP broadcast network, or from a 3GPP broadcast to a non-3GPP broadcast network, and vice versa.

[0080] With reference to FIG. 5, in one embodiment, the other engines (516) may include an advertisement insertion engine, a mapping engine, etc. (not shown in FIG. 5). In one embodiment, the advertisement insertion engine (not shown in FIG. 5) may refer to an entity that monitors the content types viewed by end users and may determine the insertion and type of advertisements to the end users. In one embodiment, the mapping engine (not shown in FIG. 5) may refer to an entity that links cellular network sessions to broadcast sessions in non-cellular networks. In another embodiment, the mapping engine associates broadcast network users with cellular network uplink channels.

[0081] In one embodiment, the network architecture (500) can be modular and flexible to accommodate any kind of changes in the system (410) since proximate processing can be obtained for stock re-estimation. The configuration details of the system (410) can be modified on the fly. In one embodiment, the system (410) can be remotely monitored and the data, application and physical security of the system (410) can be fully guaranteed. In one embodiment, data can be meticulously collected and put into a cloud-based data lake for processing to extract actionable insights. Thus, aspects of predictive maintenance can be achieved.

[0082] FIG. 6 illustrates an example representation (600) in or with which a system such as the BMOS (410) of FIGS. 4 and 5 may be implemented, according to one embodiment of the present disclosure.

[0083] As shown in Figure 6, a content provider / OTT provides content via BMOS (602) to a user device (608). Those skilled in the art will understand that the user device (608) is similar in function to the UE (402) of Figure 2, and therefore may not be described in detail again for the sake of brevity.

[0084] In one embodiment, based on the data collected by the BMOS (602), the BMOS (602) determines whether content provided by a content provider / OTT is offloaded from a cellular system (604) supporting unicast and broadcast / multicast to a broadcast-only network (606) and vice versa. In one embodiment, the broadcast-only network (606) may include, but is not limited to, DVB-H, ATSC 3.0, etc.

[0085] In this manner, the BMOS (602) determines whether a particular content being viewed by a user device (608) needs to be offloaded from the cellular network to the non-cellular broadcast network and vice versa. Additionally, the BMOS (602) allows for seamless medium switching without any manual intervention by the user, providing continuous broadcast / multicast services.

[0086] FIG. 7 illustrates an example architecture (700) for transferring media streams from a content provider to an end user via BMOS, according to an embodiment of the present disclosure.

[0087] Referring to FIG. 7, the architecture (700) may include content providers (CPs) (710-1, 710-2, 710-3, 710-4...710-N) (individually referred to as CPs (710) and collectively referred to as CPs (710)). In one embodiment, as previously described, the CPs (710) provide media content to end users associated with user devices such as converged UEs (702). In one embodiment, the CPs (710) provide media content to the UEs (702) via a media-agnostic common platform (706). In one embodiment, the media-agnostic common platform (706) may include a service continuity and offload management module, such as the BMOS (410) of FIGS. 4-5, an intelligent data controller, such as the intelligent data collector engine (512) of FIG. 5, and an ad insertion management module.

[0088] As shown in FIG. 7, the converged UE (702) may include a common media application and a common middleware including a service continuity and offload management module, an intelligent data controller, and an ad insertion management module. In addition, the UE (702) may include a modem, a physical and a smart card. In one embodiment, the converged UE (702) is bidirectionally connected to a media agnostic common platform (706) through a radio access network (RAN) and a core network (CN) (704) including a 3GPP / non-3GPP based terrestrial / non-terrestrial broadcast / multicast network. The broadcast network may be 3GPP based or non-3GPP based such as ATSC, DVB-IP network, or even a non-terrestrial based network.

[0089] In one embodiment, a service continuity and offload management module of the common middleware in the converged UE (702) may act as a subscription management entity in addition to collecting data from the UE (702). The common middleware resident in the UE (702) subscribes to the media agnostic common platform (706), where a unique identifier (ID) may be assigned to the UE (702) along with a middleware ID.

[0090] In one embodiment, the service continuity and offload management module makes a decision as to whether the media content should be offloaded to another dedicated broadcast / multicast system or returned to the cellular network, i.e., unicast data transfer or broadcast session. Further, in one embodiment, the intelligent data collector collects necessary data, such as, but not limited to, data from the converged UE (702), the RAN and CN (704), and data from the CP (710). Further, in one embodiment, the advertisement insertion management module monitors the type of media content viewed on the converged UE (702) and determines the insertion and type of advertisements to the converged UE (702). In one embodiment, the advertisement content provider (708) provides advertisements to the advertisement insertion management module, and based thereon, the advertisement insertion module determines the insertion and type of advertisements to be sent to the converged UE (702).

[0091] In one embodiment, the architecture (700) can be modular and flexible to accommodate any type of change.

[0092] FIG. 8 illustrates an example block diagram of a system architecture (800) for transferring media streams from a content provider to an end user, according to an embodiment of the present disclosure.

[0093] As shown, a common media application or content provider (802) provides media content to a terminal (810) via a broadcast offload / onload management module, such as BMOS (804). BMOS (804) may include an intelligent data collector controller, such as the intelligent data collector engine (512) of FIG. 5, a backchannel linking module, and an ad insertion management module. In one embodiment, an association is maintained between a downlink broadcast channel in one radio access technology and an uplink channel in another cellular radio technology. In particular, the uplink channel is used by the content provider (802) to provide data-related services. Because of the ad insertion management module in BMOS (804), when an end user clicks on an advertisement to purchase a particular product or to get more information about the product, an association needs to be made to the uplink data being processed for the downlink broadcast.

[0094] Furthermore, as described above with reference to Figure 7, BMOS (804) may include a peer device as a common middleware (806) in a terminal (810). In particular, the middleware (806) in the terminal (810) may subscribe to BMOS (804). In such a scenario, a unique ID and middleware ID are assigned to the terminal (810).

[0095] Referring to FIG. 8, media content is provided to a terminal (810) through a connectivity medium or modem (808). The connectivity medium or modem (808) may include a broadcast network (BN-1) (3GPP), a BN-2 (non-3GPP), a BN-N non-terrestrial network (NTN), and a unicast network. In one embodiment, the BMOS (804) determines whether a broadcast / multicast session should be offloaded from one network to another network based on data collected by an intelligent data collector controller of the BMOS (804). In an exemplary implementation, the offloading may be performed via at least two methods, including but not limited to a relay method and a transparent method.

[0096] In the relay method, when the BMOS (804) decides to offload a broadcast / multicast session from one network system to another, the data packets of the media content are routed through the BMOS (804), and thus the data packets are relayed. To this effect, the data packets should be routed or alternatively IP-in-IP encapsulated.

[0097] In the transparent method, when the BMOS (804) decides to offload a broadcast / multicast session from one system to another, the data packets are sent transparently to the terminals (810) without the knowledge of the BMOS (804). For example, after establishing a suitable route based on traffic needs, the BMOS (804) may communicate the suitable end point node to the content provider (802). The content provider (802) may then start sending data packets and manage the data packet transmission from this point on until the next communication about the routing is obtained from the BMOS (804). In the transparent method, since the data packets are not relayed by the BMOS (804), the BMOS (804) may not have any direct way to track the data being sent to the end user. Therefore, in this method, BMOS (804) needs to be able to access such data in an indirect manner from various components in the overall ecosystem, such as from the middleware (806) resident in the terminal (810), the content provider (802), and other modules present in the 3GPP or non-3GPP architecture components.

[0098] In an exemplary embodiment, the choice of selecting the offloading method is left to the implementation of the service provider. Those skilled in the art will recognize that the architecture (800) can be modular and flexible to accommodate any kind of change.

[0099] 9 illustrates another exemplary representation of a BMOS architecture (900) according to an embodiment of the present disclosure. Those skilled in the art will recognize that the BMOS (904) is similar in function to the BMOS described with reference to FIGS. 4-8 and therefore may not be described extensively again for the sake of brevity.

[0100] 9, the BMOS (904) provides media content from a content provider (902) to a UE (908) through one of a network, such as, but not limited to, a non-3GPP broadcast network (906-1), a 3GPP broadcast / multicast network (906-2), and a 3GPP unicast network (906-3). In one embodiment, as described above, the BMOS (904) collects data from each entity of the architecture (900), analyzes the data, and determines whether media content should be offloaded from one network system to another, i.e., among (906-1, 906-2, or 906-3), to overcome problems and concerns of conventional solutions.

[0101] As described above with reference to Figure 8 above, offloading may be performed via either a relay method or a transparent method. Descriptions related to these methods have been described with reference to Figure 8 above and therefore may not be described extensively again for the sake of brevity.

[0102] FIG. 10 illustrates an example method flow diagram illustrating a method (1000) for offloading / onloading a media session according to an embodiment of the present disclosure.

[0103] As shown, in step (1002) of the method (1000), an intelligent data collector engine, such as that described above with reference to FIG. 5, may collect the necessary data, including, but not limited to, data from UEs connected and subscribed to the BMOS, data from access network entities or core network entities, data from content providers, etc. In one embodiment, the intelligent data collector engine may collect the necessary data, including, but not limited to, data from the ... number of users (N User), whether the user is subscribed to BMOS, i.e., for offload or onload functionality (S User ), whether a particular content is subscribed to BMOS, i.e., for offload or onload functionality (S cp ), whether the signal strength as perceived by the UE is sufficient for a particular content to be offloaded for a period of time (UE rsrp ), total bandwidth saved by offloading, technologies supported by the UE, end user initiated actions, etc. In one embodiment, in step (1002), the method (1000) may include analyzing the collected data by an intelligent data collector engine to identify the number of users to be offloaded.

[0104] 10, in step (1004), the method (1000) may include determining whether a specified number of users meet one or more offloading criteria. In one embodiment, the method (1000) includes determining whether a specified number (N) of users under a given area (and subscribed to BMOS) who are viewing a particular content meets one or more offloading criteria. User ) is the user's threshold (ThN User ) (also referred to herein as a first threshold) and, as a result, whether the saved bandwidth (Bw) is greater than a bandwidth threshold (ThBw) (also referred to herein as a second threshold). Further, in one embodiment, the method (1000) in step (1004) may include determining whether a signal strength (Rx) as perceived by the UEs associated with the identified number of users is greater than a signal strength threshold (ThRx) (also referred to herein as a third threshold). In one embodiment, if one or more offloading criteria are not met, the method (1000) continues to analyze (1006) the data collected by the intelligent data collector engine.

[0105] In step (1008), the method (1000) may include determining whether one or more offload criteria from step (1004) are met, and then offloading is triggered. If the one or more offload criteria are met, the method (1000) may include offloading a specified number of users from one network to another network via BMOS. When the offloaded users exit the media content and leave the serving area, the method (1000) may include triggering onload (1010), i.e., broadcast stops and unicast resumes.

[0106] In one embodiment, as described above, the one or more offload criteria include a specified number of user equipment being greater than a first threshold. In one embodiment, the one or more offload criteria include a specified number of user equipment being subscribed to the system. In one embodiment, the one or more offload criteria include a bandwidth saved by a specified number of user equipment being greater than a second threshold. In one embodiment, the one or more offload criteria include a signal strength of a specified number of user equipment being greater than a third threshold.

[0107] The data is then continuously tracked and collected by BMOS to determine if the media session needs to be offloaded from one network system to another without causing any session interruption and without any manual intervention from the end user.

[0108] According to embodiments presented herein, one or more processors 502 of FIG. 5 of the system (410) may be configured to perform the steps of the method (1000) described above with reference to FIG. 10.

[0109] Those skilled in the art will readily ascertain that the illustrated steps are set forth to explain the exemplary embodiments shown, and it should be expected that ongoing technological developments will change the manner in which certain functions are implemented. These examples are presented herein for purposes of illustration and not limitation. Moreover, boundaries of functional building blocks have been arbitrarily defined herein for convenience of description. Alternative boundaries may be defined so long as the specified functions and relationships thereof are appropriately performed. Alternatives (including equivalents, extensions, variations, deviations, etc. of those described herein) will be apparent to those skilled in the art based on the teachings contained herein. Such alternatives fall within the scope and spirit of the disclosed embodiments.

[0110] FIG. 11 illustrates an example block diagram representation (1100) highlighting one or more interfaces between multiple modules and a BMOS system, according to an embodiment of the present disclosure.

[0111] As shown, a UE (1102), such as a 5G smartphone or a 5G cellular device, connects to a 5G core via a 5G new radio access network (1116) and further connects to a data network (DN), such as the Internet. The AMF (1104) serves as a single entry point for the UE connection. Based on the service requested by the UE (1102), the AMF (1104) selects a respective session management function (SMF) (1106) to manage the user session. The user plane function (UPF) (1118) transports IP data traffic (user plane) between the UE (1102) and external networks. The multicast broadcast server function (MBSF) (1110) enables the AMF (1104) to manage the access services of the UE (1102) and the 5G core. Other functions, such as the policy control function (PCF) (1124), provide a policy control framework that applies policy decisions and accesses subscription information to govern network behavior.

[0112] In one embodiment, N3BN_EXT_A is an interface that may be defined between BMOS (1114) and non-3GPP broadcast networks (1126). BMOS (1114) interfaces with the 3GPP system in the same way that any other Application Server (AS) does.

[0113] FIG. 12 illustrates another example block diagram representation (1200) highlighting one or more interfaces between multiple modules and a BMOS system, according to an embodiment of the present disclosure.

[0114] As shown, in one embodiment, the first interface, DC_EXT_1, is an interface between the intelligent data collector (1204) and all external entities such as a network data analysis function (NWDAF), a UE, or any other similar analysis system in a 3GPP system. In one embodiment, the second interface, DC_INT_1, is an interface between the intelligent data collector (1204) and the offload / onload management system (1202). In one embodiment, the third interface, Oms_Pcf, is an interface between the offload / onload management system (1202) and a policy control function (PCF) (1206). For example, the PCF (1206) specifies the offload / onload management settings to be applied based on a specific policy configured either based on end user input or based on configuration server settings. In one embodiment, a fourth interface, Oms_Blc, is an interface between the Offload / Onload Management System (1202) and the Backchannel Linking Module (1208) to understand the association between UL data and multicast / broadcast sessions and by which user. In one embodiment, a fifth interface, PCF_EXT_1, is an interface between the PCF (1206) and external agents such as UEs, configuration servers, etc.

[0115] In one embodiment, all the above mentioned interfaces are service-based APIs defined for the purpose of sharing reports and maintaining multiple configurations across control paths.

[0116] 13A-13G show example sequence diagram representations for different call flows in a network implementing a proposed method, such as the method (1000) of FIG. 10, according to an embodiment of the present disclosure.

[0117] For example, FIG. 13A shows a sequence diagram (1300-1) for offload / onload management registration and policy making. In particular, when a UE (1302) registers with a unicast broadcast network such as (1304), the UE (1302) sends a registration request to the BOMS platform (1306) either upon power-up or upon returning from out-of-service to in-service. In particular, the BOMS (1306) assigns a unique ID and a middleware ID to the UE (1302) and responds with these IDs to the UE (1302) in response. An end user associated with the UE (1302) then initiates content viewing, which may comprise a content request being sent from the UE (1302) to a content provider (CP) (1308) via the BOMS (1306). In response, the CP (1308) checks whether the UE (1302) is subscribed to view media content. Once confirmed, the CP (1308) provides the requested media content to the UE (1302) over the unicast broadband network (1304) via the BOMS (1306). At the same time, the BOMS (1306), specifically, the intelligent data collector engine in the BOMS (1306), collects the necessary data required for offload / onload management.

[0118] Figure 13B shows a sequence diagram (1300-2) for data collection performed by an intelligent data collector engine of BMOS (1306). In particular, the intelligent data collector engine collects data from networks such as (1304) and from integrated UEs (1302) via periodic data sessions. Based on the collected data, BMOS (1306) decides and triggers offload / onload management.

[0119] Further, Figure 13C shows a sequence diagram (1300-3) for offloading a data session from a 3GPP unicast network to a non-3GPP broadcast network. As shown, media content is distributed from a CP (1308) to a UE (1302) via a 3GPP unicast network (1304). Based on the collected data, the BOMS (1306) decides to trigger an offload mechanism, and as a result, the media content is provided to a non-3GPP broadcast network (1310) via the BOMS (1306), which routes the media content to the UE (1302). Those skilled in the art will understand that the manner in which the BOMS (1306) decides to trigger an offload mechanism has been described in detail with reference to previous figures and may not be described again for brevity.

[0120] Similarly, Figure 13D shows a sequence diagram (1300-4) for offloading a data session from a 3GPP broadcast network to a non-3GPP broadcast network. As shown, media content is distributed from a CP (1308) to a UE (1302) via a 3GPP broadcast network (1304). Based on collected data, the BOMS (1306) decides to trigger an offload mechanism, so that the media content is provided from the BOMS (1306) to the non-3GPP broadcast network (1310), which routes the media content to the UE (1302).

[0121] Similarly, Figure 13E shows a sequence diagram (1300-5) for offloading a data session from a non-3GPP broadcast network to a 3GPP unicast network. As shown, media content is distributed from a CP (1308) to a UE (1302) via a non-3GPP broadcast network (1310). Based on collected data, the BOMS (1306) decides to trigger an offload mechanism, so that the media content is provided from the BOMS (1306) to a 3GPP unicast network (1304), which routes the media content to the UE (1302) via unicast.

[0122] Further, Figure 13F shows a sequence diagram (1300-6) for offloading a data session from a non-3GPP broadcast network to a 3GPP broadcast network. As shown, media content is distributed from a CP (1308) to a UE (1302) via a non-3GPP broadcast network (1310). Based on the collected data, the BOMS (1306) decides to trigger an offload mechanism, so that the media content is provided from the BOMS (1306) to the 3GPP broadcast network (1304), which routes the media content to the UE (1302).

[0123] Referring to FIG. 13G, a sequence diagram (1300-7) for sharing buffer status reports is shown. As shown, a UE (1302) registers with a BOMS platform (1306) upon power-up or when returning from out-of-service to in-service. The registration is performed via a unicast broadband network (1304). In addition, an intelligent data collector engine in the BOMS (1306) collects data from the unicast broadband network (1304) as well as from the UE (1302) via periodic data sessions. In one embodiment, all UEs send their respective buffer status reports to the BOMS (1306), based on which the BOMS (1306) decides whether to offload a data session from one network system to another network system.

[0124] Although considerable emphasis has been placed herein on the preferred embodiment, it will be appreciated that many embodiments may be made, and that many changes may be made in the preferred embodiment without departing from the principles of the present disclosure. These and other changes in the preferred embodiment of the present disclosure will become apparent to those skilled in the art from the present disclosure herein, and it is to be clearly understood thereby that the above illustrative matter is implemented merely as an illustration of the present disclosure, and not as a limitation.

[0125] Advantages of the present disclosure The present disclosure provides systems and methods for offloading or onloading media sessions across multiple channels or access networks.

[0126] The present disclosure provides a system and method for intelligently and seamlessly switching between network systems without any manual intervention to provide continuous broadcast / multicast services to end users.

[0127] The present disclosure enables efficient use of licensed radio resources.

[0128] The present disclosure provides an effective system and method for saving wireless bandwidth corresponding to user offloading.

[0129] The present disclosure provides better quality of service to end users. [Explanation of symbols]

[0130] 100 Block Diagram 102 Bearer Services 104 Delivery Method 106 User service or user application, application, MBMS user service 200 Architecture 202 Content Receiver Application 204 MBMS Client 206 BM-SC 208 Content Provider 210 Content Sources 212 Unicast Distribution 300 End-to-end eMBMS Architecture 304 MBMS Client 306 UE modem 308 E-UTRAN 310 Multicast Coordination Entity (MCE), MCE 312 Mobility Management Entity (MME), MME 314 MBMS-GW 316 BM-SC 318 Service Capability Exposure Function (SCEF), SCEF 320 Content Provider or Application Service Provider 330 Anticipated End-to-End MBMS Architecture 332 Access Mobility Function Module (AMF) 334 gNodeB 336 NEF 400 Network Architecture 402, 402-1, 402-2, 402-N UE 404 Node 406 Network 408 Entity 410 BMOS, System, Off-load System 412 Centralized Server 500 Network Architecture 502 processor 504 Memory 506 Interface 508 Processing Unit / Processing Engine, Processing Engine 510 Database 512 Intelligent Data Collector Engine 514 Broadcast Offload / Onload Decision Engine, Decision Engine 516 Other units or other engines, other engines 600 expressions 602 BMOS 604 Cellular systems supporting unicast and broadcast / multicast 606 Broadcast-only network 608 User Devices 700 Architecture 702 Converged UE, UE 704 Radio Access Network (RAN) and Core Network (CN), RAN and CN 706 Media Agnostic Common Platform 708 Advertising Content Provider 710, 710-1, 710-2, 710-3, 710-4, 710-N Content Provider (CP), CP 800 System Architecture, Architecture 802 Common Media Application or Content Provider, Content Provider 804 BMOS 806 Common middleware, middleware 808 Connectivity Media or Modem 810 Terminal 900 BMOS Architecture, Architecture 902 Content Provider 904 BMOS 906-1 Non-3GPP Broadcast Networks 906-2 3GPP Broadcast / Multicast Networks 906-3 3GPP Unicast Network 908 UE 1000 ways 1100 Block diagram representation 1102UE 1104 AMF 1106 Session Management Facility (SMF) 1110 Multicast Broadcast Server Function (MBSF) 1114 BMOS 1116 5G New Wireless Access Network 1118 User Plane Function (UPF) 1124 Policy Control Function (PCF) 1126 Non-3GPP Broadcast Networks 1200 Block Diagram Representation 1202 Off-road / On-road Management System 1204 Intelligent Data Collector 1206 Policy Control Function (PCF), PCF 1208 Backchannel Linking Module 1300-1 Sequence diagram 1300-2 Sequence diagram 1300-3 Sequence diagram 1300-4 Sequence diagram 1300-5 Sequence diagram 1300-6 Sequence diagram 1300-7 Sequence diagram 1302 UE, Integrated UE 1304 unicast broadcast network, unicast broadband network, 3GPP unicast network, 3GPP broadcast network 1306 BOMS Platform, BOMS 1308 Content Provider (CP), CP 1310 Non-3GPP Broadcast Networks

Claims

1. A system (410) for offloading a user equipment (402), the system (410) comprising: one or more processors (502); and a memory (504) operably coupled to the one or more processors (502), the memory (504), upon execution, causing the one or more processors (502) to: collecting one or more data parameters from the user equipment (402), the user equipment (402) being communicatively coupled to the system (410); determining a number of user equipment (402) to be offloaded based on the one or more data parameters; determining whether the identified number of user equipment (402) meets one or more offload criteria; triggering the offloading of the identified number of user equipment (402) from a first network system to a second network system based on a determination that the identified number of user equipment (402) meets the one or more offloading criteria; The system (410) comprises processor-executable instructions for causing the system to:

2. 2. The system of claim 1, wherein the one or more data parameters comprise at least one of: a first count of a number of user equipment (402) in a particular area that are viewing a particular broadcast or multicast content; user equipment (402) that are subscribed to the system (410); a first threshold corresponding to a second count of the number of user equipment (402) that can save a particular bandwidth; a second threshold corresponding to the bandwidth saved; and a third threshold corresponding to a signal strength required for the offload.

3. 2. The system of claim 1, wherein the one or more offload criteria include a determined number of the user equipment being greater than a first threshold.

4. 4. The system of claim 3, wherein the one or more offload criteria include the specified number of user equipment (402) being subscribed to the system (410).

5. 5. The system of claim 4, wherein the one or more offload criteria include a bandwidth saved by the identified number of user equipment (402) being greater than a second threshold.

6. 6. The system of claim 5, wherein the one or more offload criteria include a signal strength of the identified number of user equipment devices being greater than a third threshold.

7. The system (410) of claim 1, wherein the first network system comprises a cellular network system and the second network system comprises a non-cellular network system.

8. 2. The system of claim 1, wherein the memory comprises processor-executable instructions that, when executed, cause the one or more processors to monitor media content of the user equipment and determine, based on the monitored media content, a type of advertisement to be displayed on the user equipment.

9. The system of claim 1, wherein the memory comprises processor-executable instructions that, when executed, cause the one or more processors to trigger the offloading by being configured to relay media content to the identified number of user equipment devices via the system.

10. 2. The system of claim 1, wherein the memory comprises processor-executable instructions that, when executed, cause the one or more processors to trigger the offload by being configured to communicate an endpoint node to a content provider of media content for content transmission to the identified number of user equipment devices.

11. 2. The system of claim 1, wherein the memory comprises processor-executable instructions that, when executed, cause the one or more processors to assign a unique identifier to each of the identified number of user equipment devices upon successful subscription to the system.

12. A method for offloading a user equipment, the method (1000) comprising: collecting, by a processor (502), one or more data parameters from the user equipment in a first network system; determining, by the processor (502), a number of user equipment in the first network system to be offloaded based on the one or more data parameters; determining, by the processor (502), whether the identified number of user equipment satisfies one or more offload criteria; triggering, by the processor (502), the offloading of the identified number of user equipment from the first network system to a second network system based on a determination that the identified number of user equipment meets the one or more offload criteria; A method comprising:

13. The method of claim 12 , wherein the one or more offload criteria include a determined number of user equipment being greater than a first threshold.

14. The method of claim 13 , wherein the one or more offload criteria include the specified number of user equipment being subscribed to a broadcast or multicast offload / onload system.

15. The method of claim 14 , wherein the one or more offload criteria include a bandwidth saved by the identified number of user equipment being greater than a second threshold.

16. 16. The method of claim 15, wherein the one or more offload criteria include a signal strength of the identified number of user equipment being greater than a third threshold.

17. 13. The method of claim 12, wherein triggering the offload by the processor (502) comprises relaying, by the processor (502), media content to the identified number of user equipment via a broadcast or multicast offload / onload system.

18. 13. The method of claim 12, wherein triggering the offload by the processor comprises communicating, by the processor, an endpoint node to a content provider of media content for content transmission to the identified number of user equipment.

19. A user equipment (402) in a first network system, the user equipment (402) comprising: One or more processors communicatively coupled to the offload system, the one or more processors comprising: sending a subscription request to the offload system (410); receiving a subscription response from the offload system (410), the subscription response comprising a unique identifier associated with the user equipment (402); providing one or more data parameters to the offload system (410) in response to receiving the subscription response; configured to: The off-load system (410) comprises: identifying the user equipment (402) for offloading based on the one or more data parameters; determining whether the user equipment (402) satisfies one or more offloading criteria; triggering the offloading of the user equipment (402) from the first network system to a second network system based on a determination that the user equipment (402) satisfies the one or more offloading criteria; A user equipment (402) comprising a processor (502) configured to perform the following:

20. The processor: collecting one or more data parameters from a user device (402); determining a number of user equipment (402) to be offloaded based on the one or more data parameters; determining whether the identified number of user equipment (402) meets one or more offload criteria; triggering the offloading of the identified number of user equipment (402) from a first network system to a second network system based on a determination that the identified number of user equipment (402) meets the one or more offloading criteria; 23. A non-transitory computer-readable medium comprising processor-executable instructions for causing a

Images