High priority notification system and method

High priority notification system and method

HIGH PRIORITY NOTIFICATION SYSTEM AND METHOD

<b>[Cross reference of related applications]</b>

This application claims priority from U.S. Patent Application No. 62/137,511 filed on March 24, 2015, which is incorporated herein by reference in its entirety.

The present invention relates to the field of wireless communications, and more specifically, to a mechanism for enabling high-priority notifications in broadcast networks.

The broadcasting spectrum is divided into different frequencies and allocated among different broadcasters for various purposes in different geographical areas. The frequency of the spectrum is allocated based on the license granted to the broadcaster. Based on these allocations, a broadcaster can be restricted to broadcasting a specific type of content (such as a television signal) on a specific frequency within a specific geographic radius. Broadcasting beyond the range of an allocated spectrum may be a violation for the broadcaster.

If a broadcaster wishes to transmit another type of content within that geographic radius, it may need the broadcaster to obtain an additional spectrum license and then allocate an additional frequency within that frequency to the broadcaster. Similarly, if a broadcaster wishes to transmit content within another geographic radius, it may be necessary for the broadcaster to obtain an additional spectrum license for that area. However, obtaining additional spectrum licenses can be difficult, time-consuming, expensive, and impractical.

In addition, a broadcaster may not always make full use of the entire part of the frequency spectrum. Grant the broadcaster a license to the spectrum. This can lead to inefficiencies in the use of broadcast spectrum.

In addition, the expected use of the broadcast spectrum may be constantly changing. For example, current broadcast television solutions are monolithic and designed for primary single services. However, broadcasters are expected to provide multiple wireless-based content in addition to broadcast and television in the future, including mobile broadcast and IoT services. In particular, there are many situations in which a large number of devices may wish to receive the same data from a common source other than broadcast television. One such example is a mobile communication service, where a large number of mobile communication devices in various geographic locations may all need to receive a common broadcast signal that conveys the same content, such as, for example, a software update or an emergency alert. In these situations, it is significantly more effective to broadcast or multicast data to these devices instead of individually signaling the same data to each device. Therefore, a hybrid solution can be expected.

To make more effective use of the broadcast spectrum, different types of content can be multiplexed together in a single RF channel. In addition, it may be necessary to use different encoding and transmission parameters to transmit the different transmitted content simultaneously, in a time division multiplexing (TDM), a frequency division multiplexing (FDM), a layered multiplexing (LDM) method, or a combination. set. The amount of content to be transmitted can vary with time and/or frequency.

In addition, content with different quality levels (for example, high-definition video, standard-definition video, etc.) may need to be transmitted to different device groups with different propagation channel characteristics and different receiving environments. In other situations, it may be desirable to transmit device-specific data to a specific device, and the parameters used to encode and transmit that data may depend on the location of the device and/or the propagation channel conditions.

At the same time, the demand for high-speed wireless data continues to increase, and it is expected that the available wireless resources (such as a specific part of the wireless spectrum) can be utilized as efficiently as possible on a potentially time-varying basis.

In addition, a receiver can be expected to recognize and distinguish high-priority communications, for example, even if When a receiver is in an idle state, it should also be given immediate or high priority attention (such as) an emergency communication. For example, a receiver can be in one of two states. In an active state, a receiver is switched on (from the perspective of the end user) and is receiving, decoding, and presenting the transmitted information (such as a TV show or movie). While an active state receiver is decoding a regular transmission, it can also easily monitor a high priority transmission. In an idle state, a receiver is turned off (from the perspective of the end user), but the power is not completely cut off. An idle receiver will not present the transmitted information to the end user on a continuous basis. However, an idle receiver may still need to monitor and identify high-priority communications. For example, it may be desirable for a mobile phone to receive an emergency alert notification when the mobile phone is turned off (although the power is not completely cut off). If a high priority communication is identified, an idle receiver can be expected to process the accompanying information and then present such information to the end user.

It should be understood that a receiver may be a battery-powered mobile device (such as a tablet computer or smart phone) rather than a fixed device connected to a power grid. Switching this device from an idle state to an active state can consume additional battery power. Therefore, in order to conserve battery power, improved efficiency can be expected to maximize the time that a receiver is in an idle state and minimize the time that the receiver is in an active state while still effectively monitoring and identifying high data with a small delay. Priority communication.

In an exemplary solution, an idle receiver can be configured to detect each transmitted communication to determine whether the communication is a high priority communication. However, this solution may not be effective and may not effectively preserve the battery power of a receiver.

An exemplary method for notifying a battery-powered device of the existence of high-priority broadcast content while enabling the device to conserve battery power includes generating a high-priority broadcast signal and broadcasting the high-priority broadcast signal to the battery-powered device . The signal includes a high-priority symbol identifier for notifying the battery-powered device to switch from an idle state to a capturing state to detect the remaining part of the high-priority broadcast signal. The signal further A high-priority indicator is included for notifying the battery-powered device to transition from the capture state to an active state to receive high-priority broadcast content before returning to the idle state. The signal further includes a timing symbol for notifying the battery-powered device that the minimum time period before a high-priority broadcast signal should be expected, so that the battery-powered device can be before the next high-priority broadcast signal Stay in this idle state.

An exemplary method for consuming high-priority content at a battery-powered device while preserving battery power includes the battery-powered device transitioning from an idle state to a capture state. The method further includes the battery-powered device receiving a high-priority broadcast signal including a high-priority symbol identifier, a high-priority indicator symbol, and a timing symbol. The method further includes the battery-powered device detecting the high-priority indicator immediately after successfully decoding the high-priority symbol identifier to determine whether high-priority content exists. The method further includes the battery-powered device transitioning from the capturing state to an active state in response to determining that the high-priority content exists and consuming the high-priority content. The method further includes the battery-powered device detecting the timing symbol to determine the minimum time before the next expected high priority broadcast signal. The method further includes the battery-powered device returning to the idle state before the minimum time expires.

<p>100: state diagram</p><p>102: Idle</p><p>104: active state/active</p><p>106: Capture</p><p>108: Unpowered state</p><p>200: Broadcasting network communication system/system</p><p>202A: content provider</p><p>202B: content provider</p><p>202C: content provider</p><p>204A: Content</p><p>204B: Content</p><p>204C: Content</p><p>206: Broadcast Network</p><p>208: Gateway</p><p>210: RF channel</p><p>212A: Broadcasting: Broadcasting Receiver/Laptop</p><p>212B: Broadcast receiver/mobile phone</p><p>212C: Broadcast receiver/TV</p><p>212D: Broadcast receiver/wearable device</p><p>214: Broadcast signal/signal/normal signal/regular broadcast signal</p><p>302: Start/start signal/start city frame</p><p>304: Waveform after startup</p><p>400: System</p><p>404: Start signal</p><p>406: ZC module or sequence generator</p><p>407: Conjugate Signal Mechanism</p><p>408: Pseudo-noise module or sequence generator</p><p>500: High priority signal</p><p>502: High priority start symbol</p><p>502A: High priority start symbol/previous high priority start symbol</p><p>502B: High priority start symbol/next high priority start symbol</p><p>504: Reverse the last symbol</p><p>506: Reversed Sign/Last Sign</p><p>700: frame sequence</p><p>702: Minimum time interval</p><p>802: First Heterogeneous Network/First HetNet/Broadcast</p><p>804: Second Heterogeneous Network/Second HetNet</p><p>806: LTE-A/third HetNet</p><p>808: Receiver/Coordination Universal Time Reference</p><p>900: frame sequence</p><p>902A: Private high-priority startup symbol/first private high-priority startup symbol</p><p>902B: Next private high priority start symbol</p><p>904: Private payload</p><p>906: minimum time interval</p><p>1000: Target hyper-local advertising materials</p><p>1002: beacon</p><p>1004A: The first super local area</p><p>1004B: The second super local area</p><p>1006: Broadcast coverage area / coverage area</p><p>1008A: The first device</p><p>1008B: second device</p><p>1102: host broadcasting station/broadcasting station</p><p>1104: received signal/blank frame</p><p>1108: Data Storage/Third-Party Content/Data Frames Stored on This Machine</p><p>1200: Land Positioning System/System</p><p>1202A: Transmitter</p><p>1202B: Transmitter</p><p>1202C: Transmitter</p><p>1204: Management database/database</p><p>1210: receiver</p><p>1302: subcarrier</p><p>1304: First start symbol</p>

In the drawings, the structure of an exemplary embodiment of the claimed invention is shown together with the detailed description provided below. Use the same component symbols to identify similar components. It should be understood that multiple components may be used in place of an element shown as a single component, and a single component may be used in place of an element shown as multiple components. The drawings are not to scale and the proportions of certain elements may be exaggerated for illustration purposes.

FIG. 1 shows an example state diagram including a potential state that can be occupied by a battery-powered communication device.

Figure 2 shows an exemplary broadcast network communication system.

Figure 3 shows an exemplary broadcast symbol.

Figure 4 illustrates an exemplary system for generating a startup.

Figure 5 shows an exemplary implementation of a high priority signal.

Figure 6 shows an example of cascading high-priority signals.

Figure 7 shows an example frame sequence.

Figure 8 shows an exemplary broadcast network communication system.

Figure 9 shows an example frame sequence.

Figure 10 shows an exemplary high-priority signal use case.

Figure 11 shows an exemplary high-priority signal use case.

Figure 12 shows an exemplary high-priority signal use case.

Figure 13 illustrates an exemplary system for generating a startup.

Figure 14 shows an exemplary method for consuming high priority content at a battery powered device.

One of the activation signals designed to enable robust detection and service discovery, system synchronization, and receiver configuration has been previously described in U.S. Patent Application No. 15/065,427 and the U.S. Patent Application is incorporated herein by reference in its entirety. Start provides two main functions: synchronization and signal to find the waveform transmitted by low-level signal to start decoding the next waveform. It is a robust waveform that provides scalability to evolve over time. In particular, the activation signal is the work of the current broadcasting system and allows new services to be supported, including mobile broadcasting and IoT services.

This article describes an exemplary high-priority notification system based on the previously described activation signal to allow a battery-powered communication device to effectively detect high-priority broadcast communications while enabling the battery-powered device to maximize the cost of an idle state It also reduces the amount of resources consumed by the battery-powered communication device to identify high-priority communications, thus conserving battery power. Figure 1 shows an example of the potential state that can be occupied by a battery-powered communication device Exemplary state diagram 100. In an idle 102 state, a device is powered on even though it is in a low power consumption state, which means that the device does not continuously process or consume content or data except for some possible background activity. Therefore, a device can conserve power when in the idle 102 state. On the other hand, in an active state 104, the device may continuously process and consume data, and therefore utilize more power. A capture 106 state represents a temporary state that can be triggered by a user or a task or a background application running on the device. The device temporarily remains in the capture 106 only when deciding whether to enter the active 104 state or the idle 102 state. For example, a device triggered by a user action will continue to an active 104 state to continue processing information or input from the user. A device triggered by an application running in the background on the device (for example) can determine whether to return to the idle 102 state or transition to the active 104 state based on the received data or content. A device can also be in an unpowered state 108, in which case the device cannot be transitioned to an active state unless the power device is first energized and transitioned to an idle 102 state.

It should be understood that, for example, a high-priority notification that will be described may include an emergency event or other notification that is suitable for a high-priority event, or information that can be expected to be presented to a user immediately or in the near future.

It should be understood that the battery-powered devices as cited throughout the example descriptions herein include any mobile communication or computing devices that are not directly connected to a power grid and may be under power utilization restrictions. This may include, for example, solar powered devices or devices powered by other alternative energy sources.

FIG. 2 illustrates an exemplary broadcast network communication system 200 in which an exemplary high-priority notification system may be provided. Specifically, the system 200 includes a plurality of content providers 202A, 202B, and 202C (hereinafter referred to as content providers 202) that provide various types of content 204A, 204B, and 204C (hereinafter referred to as content 204) via a broadcast network 206 . It should be understood that although three content providers 202 are shown, the system 200 may include any suitable number of content providers 202. In addition, the content provider 202 can be any suitable type of content ( Such as TV broadcast signals, software updates, emergency warnings, etc.) providers. It should be further understood that the content provider 202 can provide the content 204 via a wireless connection to a gateway 208 or a wired connection.

The content 204 is multiplexed into a single RF channel 210 at the gateway 208 over time. The broadcast receivers 212A, 212B, 212C, and 212D (hereinafter referred to as the broadcast receiver 212) are configured to recognize the broadcast signal 214 and receive the broadcast signal 214 via the RF channel 210. It should be understood that although four different types of broadcast receivers 212 are shown (a laptop 212A, a mobile phone 212B, a television 212C, and a wearable device 212D), the system 200 may include any suitable number and Any suitable type of broadcast receiver 212 includes wearable and IoT devices and other suitable mobile battery-powered communication devices.

To help identify the content of a broadcast signal and distinguish different types of broadcasts and, for example, the priority of a broadcast, the broadcast signal 214 includes code points or identifiers. A code point can indicate whether a broadcast signal 214 includes, for example, TV/video content, application data (such as weather information), or an emergency alert. It should be understood that such things are only some examples, and a code point can potentially have a wide range of applications and achieve flexibility and scalability. In particular, if a broadcast receiver 212 is not familiar with a code point or cannot detect or decode the content of a broadcast signal 214 containing a specific code point, the broadcast receiver 212 can only ignore the broadcast signal 214.

Define a code point based on certain syntax and semantics. In particular, grammar refers to the structure or format of data bits, which means the order of presenting bits (for example, signalling). On the other hand, semantics refers to the meaning of each segment of a bit. More specifically, how the semantic definition will interpret a prescribed pattern and what actions will be taken based on that interpretation. Therefore, based on the defined syntax and semantics, code points can be very versatile in terms of potential applications and uses.

For example, code points can be defined as public or private. Specifically, a common code point can be a code point that anyone can use to transmit broadcast signals to a wide range of broadcast receivers 212. A code point defined as private can be used by a broadcaster to update a new business model. Specific and limited applications. For example, a broadcaster can, for example, use a private code point identified by a software application to deliver a service that has been authorized and distributed by an organization (such as an application storage) to the application. Software applications can be pre-programmed to recognize these code points. These applications can run in the background on a receiving device or broadcast receiver 212 and periodically check new data through this mechanism in the broadcast channel to save the battery power of the receiver 212. This private mode can be called, for example, discontinuous reception or DRX and can be incorporated in one of the next generation broadcasting systems as previously described in US Patent Application No. 14/092,993.

In addition to being designated as public or private, code points can be used in combination with or without a subsequent associated waveform or data depending on the signal being sent. This versatility enables the use of code points in a variety of ways as will be described in more detail, including (for example): for delivering emergency alerts; for sending application data and updates and for delivering ultra-local target content, for The geographic location and transmitter identification can be transmitted, and these operations can be performed with or without the associated signal waveform or data (as will be described by some examples) that can be public or private in nature.

In an exemplary implementation that includes a specific type of grammar, as shown in FIG. 3, an activation 302 is before a post-activation waveform 304 and is designed to indicate at a low level during a specific time period The type or form of a signal 214 is transmitted so that the broadcast receiver 212 can discover and recognize whether the waveform 304 after activation is present, and it instructs how to receive available services through the waveform 304 after activation. Therefore, activation is relied upon as a component of each transmission frame to allow synchronization/detection and system configuration. However, it should be understood that the waveform 304 may not necessarily exist in all implementations after startup. The startup design includes a flexible signaling method to convey frame configuration and content control information to the broadcast receiver 212. Signal design describes the mechanism by which it modulates signal parameters on physical media. The signaling protocol describes the specific code used to transfer the parameter selection of the control transmission frame configuration. This achieves reliable service discovery while providing scalability to adapt to the evolving signaling needs from a common frame structure. Specifically, the start-up design realizes universal signal discovery independent of channel bandwidth, as previously described in the U.S. Patent Application, which is incorporated by reference in its entirety. 15/065, No. 427.

Startup also achieves reliable detection in the presence of various channel impairments (such as time dispersion and multipath fading, Doppler shift, and carrier frequency offset). In addition, multiple service context contents can be accessed based on pattern detection during signal discovery, so as to achieve wide flexibility in system configuration. The activation also promotes scalability to adapt to the continuous evolution of service capabilities based on a hierarchical signaling structure. Therefore, new signal types that have not yet been envisaged can be provided by a content provider 202 and identified in a transmitted signal 214 through the use of an activation signal.

A more detailed description of an activation and associated structure and how an activation is constructed and signaled has been previously described in US Patent Application No. 15/065,427, which is incorporated herein by reference in its entirety.

FIG. 4 shows an exemplary system 400 for generating an activation 302. As shown in FIG. The start signal 302 generated by the system 400 is composed of (N) OFDM symbols labeled (0 to N). The post-activation signal 404 represents a service notified by the activation signal and consumed by a receiver. As previously described, the activation signal is generated by the following method: a Zadoff-Chu (hereinafter referred to as "ZC") module or sequence generator 406 uses one value to generate a ZC sequence, a pseudo noise (PN) module The group or sequence generator 408 generates a PN sequence based on a sub-value, and then modulates the ZC sequence with the PN sequence before translating the resulting complex sequence into a time domain and applying a cyclic shift to the symbols used for signalling. The conjugate signaling mechanism 407 activates additional signaling information by introducing the conjugate of the ZC root.

It should be understood that the length of a ZC (N_zc) Is a prime number. In particular, the ZC root (a Zadoff-Chu sequence that does not have a cyclic shift) can have N_zc-1 possible values. For example, if you choose N_zcIf the prime number is 1499, the number of possible root values is 1498. Based on the initialization vector of the PN module 408 of the 16-bit linear feedback shift register, a sub-value can have one of 65,535 possible values. Therefore, given a single ZC length, the potential number of combinations of root value and seed value is N(ZC)X root(q)X PN seed=1 X 1498 X 65,535=about 98,171,430 possible groups combine. It should be understood that as N_zcWith the increase in the number, the total possible combination increases to an even larger potential total. For example, if N_zcCan be one of 9 different possible prime numbers (including 1483, 1487, 1489, 1493, 1499, 1511, 1523, 1531 and 1543), then N(ZC)X root(q)X PN seed potential combination The total number will be approximately 883,000,000. These combinations are referred to herein as code points.

It should be understood that each code point uniquely identifies an activation symbol, and therefore uniquely identifies the purpose of the symbol. Therefore, based on the defined syntax and semantics, code points can be very versatile in terms of potential applications and uses. For example, several code points can be assigned in groups or individually depending on the intended use. Therefore, the code point can be a potentially valuable and underutilized resource.

As an example use of these underutilized assets, code points can be defined as indicating high-priority communications and used as a wake-up flag according to an example grammar. For example, the code point can be defined as indicating an emergency alert notice or other high-priority notice by certain standards.

It should be understood that other battery-powered devices (such as IoT devices) can be similarly configured to periodically check code points in the broadcast stream and receive high-priority communications while remaining in a low-power idle state in other ways. It should be further understood that the device can only be configured to detect and decode certain code points, and only ignore one code point that is not understood. This promotes further scalability of code points, and the use of code points for various purposes in high-priority communications.

To facilitate high-priority broadcast communications, a signal 214 incorporates a notification mechanism that indicates the existence of high-priority information. Then, a broadcast receiver 212 can identify and decode high-priority information, and present such information to a user. For example, the presence of high-priority information may be indicated by the presence of a high-priority indicator (or a flag, according to an example syntax) in a code point or activation 302. A broadcast receiver 212 that recognizes the indication can switch from an idle state to an active state to receive high-priority information, and then return to the idle state. Alternatively, if the high priority indication is not recognized, the broadcast receiver 212 may remain in an idle state.

FIG. 5 shows an exemplary implementation of a high-priority signal 500 that enables a battery-powered device to effectively detect high-priority broadcast communications while enabling the battery-powered device to maximize the time spent in an idle state. The high priority signal 500 includes a normal signal 214 as described earlier, and the normal signal 214 includes a start 302 and a post-start waveform 304. In addition, the high-priority signal 500 includes one/several high-priority activation symbols ("HPBS" hereinafter) 502 before activation 302. In an example, the use of an activation mechanism as can be cited herein is an exemplary activation implementation, and the syntax and semantics are an ATSC 3.0 implementation. It should be understood that this is one of the first standards, which uses a universal activation mechanism for synchronization and discovery, as described in US Patent Application No. 15/065,427. It should be understood that the concept of an HPBS is not included in the current ATSC 3.0 standard. However, this may be synergistic in the future, and any reference to HPBS in this example is hypothetical herein.

The HPBS 502 includes a wake-up flag symbol, which enables the broadcast receiver 212 to detect and recognize the high-priority signal 500 and to synchronize with the high-priority signal 500. A broadcast receiver 212 can monitor this flag to determine whether an HPBS is being delivered. If the wake-up flag (an example syntax) of the HPBS 502 is detected to be true, the broadcast receiver 212 in an idle state can be fully awakened and transition to an active state to receive high-priority information. If this wake-up flag is detected to be false, the broadcast receiver 212 can return to sleep and remain in the idle state before a next HPBS 502 occurs, and thus save battery power.

The state during which the broadcast receiver 212 is checking the HPBS 502 to determine whether a wake-up flag is true or false can be referred to as a capture state, as described in FIG. 1. This is a transient state and only means that a short period of time is occupied by the broadcast receiver 212 while checking whether the wake-up flag is true or false. It is expected that the broadcast receiver 212 exits the capture state quickly, and moves to an active state or returns to an idle state depending on whether a wake-up flag is judged to be true or false.

It should be understood that the HPBS 502 is small and light, and does not need to carry a large amount of information, and therefore does not need to transmit a large amount of resources. This is because the main purpose of HPBS 502 is to broadcast receiver 212 It informs whether a high-priority communication is transmitted, so that if no high-priority communication is transmitted, the broadcast receiver 212 can immediately return to sleep. Therefore, HPBS 502 does not need to carry any further information other than this wake-up flag notification.

By using a small number of activation symbols, a negligible amount of transmission resources are occupied by the HPBS 502. In addition, it is not expected that the HPBS 502 is transmitted as frequently as the activation 302 of other types of frames. For example, an ATSC 3.0 activation may have a frame length of about 250ms. Therefore, four ATSC 3.0 launches can occur every second. By comparison, the HPBS 502 may have a length of, for example, 0.5 ms. Therefore, an HPBS 502 (when present) can only be transmitted once every few seconds.

It should be further understood that although the HPBS 502 is shown as including 3 symbols, this shows an exemplary implementation as will be described. However, HPBS 502 may contain any suitable number of symbols. Therefore, since activation includes an inverted last symbol 504 to indicate the end of activation 302 and promote scalability and flexibility, the last symbol 506 of HPBS 502 can also be inverted to indicate the end of HPBS 502 and promote the availability of HPBS 502. Scalability and flexibility. In particular, by detecting the inverted symbol 506, the broadcast receiver 212 can recognize the end of the HPBS 502 and therefore the number of symbols included in the HPBS 502 does not need to be predefined.

In an exemplary grammatical and semantic implementation (such as an ATSC 3.0 implementation), the ZC root is also used to identify a major version number, which identifies a service type to which an activation frame 302 belongs. In addition, a PN seed indicates the one-time version. The combination of major/minor versions used to identify the waveform or service type can be referred to as one of the code points described previously.

It should be understood that although a large number of possible code points may be available (as described), an exemplary implementation initiated by one of ATSC 3.0 may use only a limited number of code points (ie, using one of 137 single ZC roots). And a PN seed contains one of 8 values). Table 1 shows the seeds selected as part of the only minor version in an ATSC 3.0 implementation.

<tables><img file="TWI718135B_D0001.tif" /></tables>

The remainder of the HPBS 502 following the wake-up flag symbol may include high-priority communication and timing information. In particular, for power efficiency reasons, an idle broadcast receiver 212 benefits by knowing when the next HPBS 502 notification activation occurs. This allows an idle broadcast receiver 212 to return to sleep before the next HPBS 502 notification activation expires. At that point in time, the idle broadcast receiver 212 can wake up again and use a minimum amount of search, calculation cost, and power loss to capture the next HPBS 502 notification activation.

In one example, one of the first symbols of HPBS 502 includes a CAB time domain structure, and the remaining symbols include a BCA time domain structure, such as U.S. Patent Application No. 15/065,427 (and the U.S. Patent Application is cited in its entirety The method is incorporated into the description in this article). In one example, the same mechanism of signaling (i.e., cyclic shift) and phase reversal of the last signaling symbol is used in HPBS 502 to signal a high priority event and so on. The start of the major/minor version symbol of activation 302 starts after the phase inversion in the pre-HPBS 502.

It should be understood that the total length or number of symbols in the HPBS 502 notification activation can be proportional Scaling to meet different future needs for signalling. The mapping of syntax, semantics, and signaling information of HPBS 502 notification activation can be specifically defined for each use case in the future to utilize a large number of available code points.

In one example, as shown in FIG. 6, two or more HPBS 502 notifications can be activated in tandem to indicate two or more high-priority events in the broadcast. In one example, when a single HPBS 502 notification activation may not be sufficient to convey all necessary information, two or more HPBS 502 notification activations can be connected in series to provide additional information related to a single high-priority event. In one example, the concatenation may include two different types of events, such as an emergency alert indicated by a public code point and an application software update indicated by a private code point.

To facilitate this timing, an HPBS 502 notification is activated and therefore uses HPBS 502 and appropriate syntax and semantics to signal the minimum time interval before an HPBS 502 notification is activated. For example, more symbols can result in more nuance, while fewer symbols can result in less nuance. Ensure that the next HPBS 502 notification activation does not occur earlier than this minimum time interval after the current HPBS 502 notification activation. In one example, the reference time point from which this minimum time interval is measured is the start or end of the current HPBS 502 notification activation. In one example, the reference time point from which the minimum time interval is measured is later than a certain fixed time point (for example, 1 second, 2 seconds, 3 seconds, etc.) at which the current HPBS 502 notification is activated. It should be understood that the minimum time interval for signal notification should be as close as possible to the actual time interval so that an idle broadcast receiver 212 will have to perform to find the next HPBS 502 notification activation search (or power loss) to minimize. It should also be understood that it can be expected to use a signal to notify an HPBS 502 notification interval of a suitable one for a sufficiently long period of time. For example, every 100ms may be too frequent for a reasonable HPBS 502 notification interval, while every few seconds may represent a more reasonable HPBS 502 notification interval.

FIG. 7 shows a frame sequence 700, which includes the expected relative occurrence of HPBS 502A notification activation and HPBS 502B notification activation, and other types of regular broadcast signals 214. And the minimum time interval 702 from the previous HPBS 502A notification activation signal to the next HPBS 502B notification activation. As can be seen, most of the frame and transmission resources are dedicated to carrying data (such as TV programs, movies, etc.) incorporated in the regular broadcast signal 214. At periodic intervals, an HPBS 502 notification starts to be inserted into the transmitted broadcast signal 214 and only occupies a relatively small amount of the total transmission resources. Each HPBS 502 notification activation is also signaled to the next or some other future HPBS 502 notification activation minimum time interval, so that the idle state broadcast receiver 212 can save power by bypassing the owner of the data frame .

It should be understood that the minimum time interval 702 for signal notification to the next (or some other future occurrence) HPBS 502 notification activation may depend on the total length of the data frame to be transmitted between adjacent HPBS 502 notification activations. From the start of an HPBS 502 notification to the next change. That is, the minimum time interval 702 to the next HPBS 502 notification activation is not constrained to a constant value and on the contrary is flexible and therefore scalable.

In one embodiment, the payload length of a frame that occurs immediately before or after an HPBS 502 notification is activated is reduced by the time length of the HPBS 502 notification activation, so that the frame start boundary continues to occur at regular periodic intervals , Its not about the existence of an HPBS 502 notification activation. This ensures that the regular frame timing is not affected by the activation of the HPBS 502 notification.

In one example, HPBS 502 may contain 3 activation symbols. The first symbol can identify an HPBS 502 notification that a start has occurred and facilitates the initial time synchronization by a receiver. The second symbol and the third symbol can each carry eight signal bits, one of which is used for the HPBS 502 wake-up flag. The remaining fifteen signaling bits can indicate the minimum time interval before the next HPBS 502 notification is activated. For example, fifteen signalling bits can be used to signal values from 0 to 32767. Therefore, if the signal fineness is 0.5ms, the signal can be used to notify one of the maximum time intervals of 16383.5ms (or about 16.4 seconds). If the fineness of the signal is 0.25ms, the signal can be used to notify one of the maximum time intervals of 8191.75ms (or about 8.2 seconds). exist With this level of fineness, the time interval before the next HPBS 502 notification is activated can be signaled extremely accurately, and therefore the idle state broadcast receiver 212 will spend very little extra time searching for the next HPBS 502 notification activation. electricity. It should be understood that the number of signaling bits used for this time interval indication can be slightly reduced (ie, reduced to 14) to release one or more predetermined bits for possible future use.

In one example, the HPBS 502 notification activation may consist of only two activation symbols. In this configuration, only seven signaling bits can be used to signal the minimum time interval before the next HPBS 502 notification is activated. This may require the use of a coarser time nuance. It should be understood that this can be a trade-off, as adding more symbols can be used to increase the fineness.

As previously disclosed in U.S. Patent Application No. 14/092,993, it should be understood that in order to facilitate the regular delivery of content on the broadcast network, a coordinated universal time (hereinafter referred to as "UTC") reference clock will be used by the broadcast entity The layer carries UTC information and is created at each client receiver or broadcast receiver 212. These UTC time stamps are calibrated to the transmitting point or air interface of the transmission antenna, and the only time inaccuracy that will be introduced will be the propagation time of the calibrated UTC time stamp to a receiver. The UTC reference time can also be used when encoding content at a transmitter and used to decode and present timing content at a receiver by establishing a timing and buffer model based on the UTC reference.

As shown in Figure 8, the first heterogeneous network (hereinafter referred to as "HetNet") 802 and the second heterogeneous network 804 with a common broadcast radio access technology (hereinafter referred to as "RAT") have a different The third HetNet 806, one of the RATs (such as LTE-A), can be used to improve the consumer experience by delivering content based on a UTC global reference time at the receiver 808.

It should be understood that the definition of a physical layer frame is the sum of activation + payload. Ideally for HetNet, the frame length should be fixed to a certain integer millisecond (for example, 250ms, 500ms, 1000ms, etc.). As shown in Figure 8, the UE establishes a UTC reference via the broadcast entity layer. The third HetNet 806 (for example) may have a fixed frame length of 10ms and The initial phasing of a frame can be made to the air interface to support the coordination between the first HetNet 802 and the second HetNet 804. Therefore, maintaining a fixed frame length and a common UTC reference 808 can achieve interoperability across these two different RATs.

However, it should be understood that there may be a potential problem regarding extending the length of an activation without compensating for the payload length of the corresponding frame to keep the total frame length constant. This can complicate the interoperability between broadcast 802 and LTE-A 806 (for example) and between several broadcasters 802 and 804 using the same RAT. The UTC time stamp in a broadcast signal can be kept calibrated at the air interface (ie, the reference time point is the start of each frame) and continue to deliver accurate UTC information. This is because the frame length uses HPBS 502 with different rhythms and Change between stations in different ways. The problem is that when the frame length is changed between stations by using the HPBS 502, the relative start of each frame (as indicated by the activation) can be continuously shifted between different stations.

However, in order to start receiving any broadcast content, a receiver must find the activation (ie, the entry point of a frame) to receive the critical low-level signal information. However, if the start time of this entry point of the frame continuously drifts between two cooperating stations, the interoperability will be complicated. Therefore, in one example, when HPBS 502 is used and interoperability is a concern, the time length of a frame is made by adjusting the number of payload symbols and/or the length of the payload symbol used in a frame keep constant. This time drift at the beginning of a frame can add a delay of hundreds of microseconds or more that must be compensated by a seamless handover between content broadcasts on the cooperative station, or implement other timing service enhancements or to other RATs ( Such as LTE-A) interoperability.

It should be understood that the HPBS 502 notification activation concept can be implemented to facilitate the signaling of various event notifications that may need to be provided to the idle or active state broadcast receiver 212. For example, an idle state broadcast receiver 212 may want to receive weather forecasts or software updates in the background, and a notification signal within the HPBS 502 notification activation can be used to notify an idle state broadcast receiver 212 that such data will be in the main broadcast stream. Streaming, and therefore broadcast receivers 212 should wake up and receive the required information. Therefore, the HPBS 502 activation can contain multiple signal bits to indicate the positive or negative state of a specific event, and at least one signal bit is associated with each event. The additional signal bit will be used to provide information about the time when the next or some other future notification is activated.

For example, as shown in FIG. 9, a private HPBS 902A notification activation can be followed by a private payload 904. The private payload 904 can be any suitable high-priority payload, such as broadcast data and weather updates associated with HTML5 application content or broadcaster news (as some possible examples). Following the first private HPBS 902A, the frame sequence 900 will continue to be defined by the first private HPBS 902A with a regular broadcast signal 214 for a minimum time interval 906 before the next private HPBS 902B is notified to start. It can be seen that the private data is only associated with 902A (indicated by signaling the availability of the private data), and the private data will then be consumed by entering the active state and then quickly transitioning back to the idle state.

It should be understood that the high priority activation signal can be public or private. For example, a code point can be designated as public, which means that the code point has been designated as a code point that can be used by anyone for a specific purpose (such as transmitting an emergency alert). Therefore, the associated high-priority activation signal transmitted using that code point can reach many types of devices that have been configured to recognize and interpret a given code point. On the other hand, a code point designated as private can be reserved for the business model of the broadcaster to transmit a specific type of content to a restricted audience or a new type of device. It should be further understood that, whether public or private, the high-priority activation signal may or may not be followed by the next post-activation payload. For example, it can indicate whether a payload follows in the signal part of the high-priority start signal.

In one example, as shown in FIG. 10, a high-priority activation signal can be used to target super-local advertising materials 1000 using beacons 1002. These beacons can be used to deliver targeted content to a specific super-local geographic area or area of beacons 1004 within a broadcast coverage area 1006. For example, a high-priority activation symbol can be defined to warn of being in a specific ultra-local area 1004 The device 1008 specific content availability. Therefore, a first device 1008A can use a specific code point to detect and consume content delivered to a first ultra-local area 1004A, and a second device 1008B in a second ultra-local area 1004B can detect and consume content at the same time. Consumption of content delivered in a larger coverage area 1006.

Figure 11 shows in more detail the physics that makes this hyperlocal reception possible. The main host broadcast station 1102 that provides the larger broadcast coverage area 1006 described in FIG. 10 is shown. The display beacon 1002 is synchronized to the received signal 1104 in one of the broadcast coverage areas 1006, and the availability of the blank frame 1104 is included to indicate the opportunity to transmit content via the synchronized beacon. The third-party content 1108 is stored or cached in the data storage 1108 in advance. When the time comes (in the air via the broadcast coverage area 1006 signaled), the data frame 1108 stored in the machine is transmitted. It should be understood that this strict synchronization enables this transmission to occur without interfering with the receiver device 1008. For example, the host transmitter or broadcast station 1102 may be part of a larger synchronization network, such as one of the host transmitters in a single frequency network (SFN). It should be understood that as long as the coverage areas 1004 do not overlap, there may be an unlimited number of beacons 1002.

In one example, as shown in FIG. 12, a single high-priority activation symbol 1206 can be used in a situation where a terrestrial positioning system 1200 is based on the geographic location of the receiver and is identified as a unique transmitter to support local services . Transmitter identification is used in SFN service monitoring and so on. As previously disclosed in U.S. Patent Application No. 14/092,993, the UTC time stamp in the frame is calibrated to the transmission of the transmission antennas of all transmitters 1202A, 1202B, 1202C, and 1200D (hereinafter referred to as transmitter 1202) Point the air interface 1208, and the only time inaccuracy introduced at the receiver will be the propagation time of a calibrated UTC time stamp to a receiver. All individual HPBSs 1206 are shown in time alignment, and all air interfaces 1208 of all transmitters 1202 are released at the same time. A management database 1204 assigns a unique code point of the HPBS to each station 1202. Therefore, for each of the four transmitters 1202 shown in the example, each code point is unique to each transmitted HPBS. It is assumed that the receiver 1210 has knowledge of this database 1204, which does not change often. Information (such as the name of the transmitter 1202, geographic longitude/latitude, antenna height, etc.) is associated with each code point in the database 1204. A receiver 1210 can identify the received code points and the time-of-arrival distance ("TDOA") of the signal. Combining the knowledge from the database 1204 to apply this information about the identified code point and TDOA, the software on the receiver 1210 can calculate its position in a direct way. It should be understood that this terrestrial positioning system 1202 as a result of the propagation and indoor penetration of broadcast signals and the fixed position of each transmitter (ie, not from orbiting satellites) may have some advantages over GPS. This system can support, for example, a location-based service that a broadcaster can provide. The system 1200 can also enable a broadcaster to use a geo-fence to send public warnings in an emergency. In addition, receiving a code point will enable a transmitter 1202 to be uniquely identified. As long as the station 1202 appears in the database 1204, the system 1202 can also be used for monitoring SFN or for interference investigation. It should be understood that these examples can be regarded as effective methods of operation because only one HPBS is consumed for such use cases.

In an example, as shown in FIG. 13, in order to increase efficiency, the frequency domain structure of the first HPBS is modified to carry an optional 1 bit of the signal. Specifically, as shown in FIG. 13, the subcarrier 1302 of the first activation symbol 1304 uses the conjugate of the ZC sequence to indicate that an event is true. The normal ZC sequence indicates that the event is false. Leave the application (syntax and semantics) to the use case.

Returning to Figure 12 and the following use case: A terrestrial positioning system supports local services by means of a single HPBS, based on the geographic location of the receiver, and as a unique transmitter identification. It is also possible to use 1 bit to send a signal to modulate a single HPBS. An example may indicate that the EAS is active or inactive. Three use cases from one symbol can be considered even more effective as an option.

It should be understood that when multiple broadcasters try to use the same code point for different purposes at the same time, there may be a potential risk of air conflict. For example, a receiver may experience confusion when an emergency weather or news update uses a code point broadcast that is said to be reserved for only emergency warnings. As described in an exemplary ATSC 3.0 implementation, there may only be 8 used Possible code points. Therefore, such conflicts may not be a problem in this discrete application. However, there are actually a large number of potential code points (ie, approximately 98 million) that can be defined as indicating high-priority communications. Therefore, it may be necessary to manage the code space and the use of code points to prevent such conflicts and achieve future scalability. In particular, it may be necessary to manage the designation and allocation of code points to ensure that different broadcasters will not interfere with each other's broadcasts. For example, it should be expected that a management entity that may be similar to the management entity type that manages the allocation of Internet IP addresses may exist to manage the allocation of code points.

It can be assigned to this code point management entity to assign code points to tasks in different categories. For example, a specific range of code points can be designated for public use, while other code points can be designated for private use. In one example, a group of code points may be designated to represent the type of waveform and the type of service. In one example, groups of code points may be designated for use with specific types of devices, such as IoT or wearable devices. In one example, code points can be specified based on regions. For example, a first range of code points can be designated for use in a first region, and a second range of code points can be designated for use in a second region. In an example, the same range of code points can be assigned multiple times in different regions, as long as the regions do not overlap within the physical broadcast range to avoid potential interference and conflicts.

In one example, the use of code points can be authorized by the management entity. Therefore, a broadcaster that requires the use of code points may need to issue a request for one of the code points and is only authorized to use a code point within a specified range granted by a license to broadcast.

Figure 14 shows an exemplary method for consuming high priority content at a battery-powered device while conserving battery power. At step 1402, the battery-powered device transitions from an idle state to a capture state. At step 1404, the battery-powered device receives a high-priority broadcast signal including a high-priority symbol identifier, a high-priority indicator, and a timing symbol. At step 1406, the battery-powered device detects the high-priority indicator immediately after successfully decoding the high-priority symbol identifier to determine whether the high-priority content exists. At step 1408, the battery-powered device transitions from the capture state to an active state in response to the judgment. High priority content exists and high priority content is consumed. At step 1410, the battery-powered device detects the timing symbol to determine the minimum time before the next expected high priority broadcast signal. At step 1410, the battery-powered device returns to the idle state before the minimum time expires.

Any of the various embodiments described herein can be implemented in any of various forms, for example, implemented as a computer-implemented method, a computer-readable memory medium, a computer system, and so on. A system can be made up of one or more customized hardware devices (such as application-specific integrated circuits (ASIC)), one or more programmable hardware components (such as field programmable gate arrays (FPGA)), stored by execution The program commands one or more processors or is implemented by any combination of the foregoing.

In some embodiments, a non-transitory computer-readable memory medium can be configured to store program instructions and/or data, where the program instructions, if executed by a computer system, cause the computer system to execute a method, such as , Any of the method embodiments described herein or any combination of the method embodiments described herein or any subset of any of the method embodiments described herein or any combination of such subsets.

In some embodiments, a computer system can be configured to include a processor (or a set of processors) and a memory medium, where the memory medium stores program instructions, and where the processor is configured to read and execute Program instructions from a memory medium, where the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein or any of the method embodiments described herein) Any subset or any combination of these subsets). The computer system can be implemented in any of various forms. For example, the computer system can be a personal computer (any of its various implementations), a workstation, a computer on a card, a dedicated computer in a box, a server computer, a client computer, a handheld device, A mobile device, a wearable computer, a sensing device, a television, a video capture device, a computer embedded in a lifetime object, etc. The computer system may include one or more display devices. Any of the various calculation results disclosed herein can be displayed via a display device or presented as an input in other ways via a user interface device. out.

As far as the term "includes or including" is used in the specification or the scope of the patent application, it is intended to have an inclusive meaning in a manner similar to the term "comprising", such as being used as a transition in a claim Explain that term when using the word. In addition, as far as the term "or" (for example, A or B) is used, it is intended to mean "A or B or both." When the applicant intends to indicate "only A or B but not both", the term "only A or B but not both" will be adopted. Therefore, the use of the term "or" in this article has an inclusive meaning and is not an exclusive use. See Bryan A. Garner's "A Dictionary of Modern Legal Usage 624" (2nd edition, 1995). In addition, as far as the term "in" or "to...in" is used in the specification or the scope of the patent application, it is intended to additionally mean "on" or "to...on". In addition, when the term "connected" is used in the specification or the scope of the patent application, it not only means "directly connected to" but also means "indirectly connected to" (such as connected through another component or another component).

Although this application has been illustrated by the description of the embodiments of this application, and although these embodiments have been described in considerable detail, the applicants intention is not to restrict or limit the scope of the appended patent application in any way. Such details. Those who are familiar with this technology will easily understand the additional advantages and modifications. Therefore, the application is not limited to the specific details, representative equipment and methods, and illustrative examples shown and described in its broader aspects. Accordingly, it is possible to deviate from these details without departing from the spirit or scope of the applicant's general inventive concept.