Abstract: A method is performed by a first fog node of a plurality of fog nodes. In some implementations, the first fog node includes a non-transitory memory and one or more processors coupled with the non-transitory memory. In some implementations, the method includes maintaining a distributed ledger in coordination with the remaining fog nodes of the plurality of fog nodes. In some implementations, the distributed ledger stores configuration information associated with one or more devices. In some implementations, the method includes obtaining a request for configuration information from a device that breaches a resource threshold associated with the distributed ledger. In some implementations, the method includes transmitting, to the device, the configuration information associated with the device in order to allow the device to be configured in accordance with the configuration information while the device breaches the resource threshold associated with the distributed ledger.

Abstract: A method is performed by a first fog node of a plurality of fog nodes. In some implementations, the first fog node includes a non-transitory memory and one or more processors coupled with the non-transitory memory. In some implementations, the method includes maintaining a distributed ledger in coordination with the remaining fog nodes of the plurality of fog nodes. In some implementations, the distributed ledger stores configuration information associated with one or more devices. In some implementations, the method includes obtaining a request for configuration information from a device that breaches a resource threshold associated with the distributed ledger. In some implementations, the method includes transmitting, to the device, the configuration information associated with the device in order to allow the device to be configured in accordance with the configuration information while the device breaches the resource threshold associated with the distributed ledger.

Abstract: In various implementations, a method of managing transactions in a distributed ledger is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes a processor, a non-transitory memory, and a network interface. In various implementations, the method includes synchronizing a first clock of the first network node with respective clocks maintained by one or more of the plurality of network nodes. In various implementations, the method includes obtaining a transaction indicator including respective transaction data. For example, in some implementations, the method includes receiving a transaction request from a client device. In various implementations, the method includes synthesizing, by the first network node, a timestamp for the transaction based on the first clock.

Abstract: In various implementations, a method of identifying anomalies is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes one or more processors, a non-transitory memory, and one or more network interfaces. In various implementations, the method includes determining a characteristic value based on information associated with the distributed ledger. In some implementations, the distributed ledger stores blocks of transactions that were added to the distributed ledger based on a consensus determination between the plurality of network nodes. In various implementations, the method includes determining whether a current transaction satisfies the characteristic value. In various implementations, the method include indicating whether there is an anomaly based on a function of the current transaction in relation to the characteristic value.

Abstract: In various implementations, a method of managing transactions in a distributed ledger is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes a processor, a non-transitory memory, and a network interface. In various implementations, the method includes synchronizing a first clock of the first network node with respective clocks maintained by one or more of the plurality of network nodes. In various implementations, the method includes obtaining a transaction indicator including respective transaction data. For example, in some implementations, the method includes receiving a transaction request from a client device. In various implementations, the method includes synthesizing, by the first network node, a timestamp for the transaction based on the first clock.

Abstract: In various implementations, a method of identifying anomalies is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes one or more processors, a non-transitory memory, and one or more network interfaces. In various implementations, the method includes determining a characteristic value based on information associated with the distributed ledger. In some implementations, the distributed ledger stores blocks of transactions that were added to the distributed ledger based on a consensus determination between the plurality of network nodes. In various implementations, the method includes determining whether a current transaction satisfies the characteristic value. In various implementations, the method include indicating whether there is an anomaly based on a function of the current transaction in relation to the characteristic value.

Abstract: A system and method for preventing e-mail spoofing, in which a receiving e-mail checking server system sends a message to a confirmation server associated with a network domain of the sending system of a received e-mail message, to determine if the sender transmitted the message. The e-mail checking server sends a confirmation request e-mail, including a transmission time or unique message “key” associated with the received e-mail, to the sending domain's confirmation server. When a confirmation request is received at the confirmation server, it replies with an indication whether the message was sent at the time indicated in the confirmation request, and/or whether the message key matches that of a previously transmitted message. The confirmation server checks whether the message was in fact sent based on stored values corresponding to the send time and/or message key stored for the confirmation request message. A message may further include indication that its origin can be confirmed.

Abstract: A system providing video data in which a constant bit rate data stream is provided between a video source and a video destination, and has a fixed data rate exceeding a predetermined minimum display rate associated with the video destination. Video data is conveyed from the video source to the video destination at the data rate, and is processed for display at the video destination at a varying display rate, between a minimum rate and a maximum rate. The minimum video data display rate at the video destination is less than the fixed data rate of the stream between the video source and the video destination, and excess received video data is stored in buffers in the video destination. Display of the received video data by a display device at the video destination is delayed from when the video data is received by a delay period, allowing buffers at the video destination to fill with video data.

Abstract: A network element is configured to implement scheduled high-power Point-To-Point (PTP) and low-power Point-To-MultiPoint (TMP) transmissions. The high-power PTP and low-power PTMP transmissions may be scheduled as bursts on an 802.16 network to occur in both the downlink subframe and uplink subframe on a given frequency channel in the wireless network. The use of an air interface for both types of communications allows the PTP and PTMP communications to be scheduled relative to each other in a unified manner to increase quality of service and minimize interference between the backhaul PTP and access PTMP networks, even though the PTP and PTMP communications take place on the same channel using the same underlying wireless technology. Buffers may be used to store data received in a PTP downlink burst prior to transmission in a PTMP downlink burst, and may be used to store data received in an uplink PTMP burst prior to transmission in an uplink PTP burst.

Abstract: A load balancer is capable of receiving and identifying multicast streams associated with a multicast session, and selecting at least one of the multicast streams for delivery to a selected stream processor. The selected stream processor is selected from a group of stream processors that are capable of providing the Layer 4-7 processing required for the multicast stream. The load balancer will monitor the processed multicast stream provided by the output of the selected stream processor, and send the processed multicast stream toward its destination. The load balancer can detect a failure in the selected stream processor by monitoring the output of the selected stream processor. If there is a failure of the selected stream processor, the load balancer will select another stream processor for processing the multicast stream, and redirect the multicast stream from the failed stream processor to the selected stream processor, wherein the process continues.

Abstract: The present invention provides a hyperlinking convention for Internet Protocol (IP) Television (TV) program content. A hyperlink comprises a resource identifier that identifies a location of the program content, and an index to a content segment within the program content. The content segment corresponds to a portion of the program content that is not directly addressable using a resource identifier from a defined content source at which the program content is stored. When user equipment receives the hyperlink, a user may select the hyperlink, and a request is routed based on the resource identifier to a content server where the program content is stored. The content server uses the resource identifier and the index to identify the content segment. The content server accesses the program content based on the resource identifier and selects the content segment based on the index. The content server sends the content segment to the user equipment in response to the request.

Abstract: A rights management technique allows user terminals to share usage rights that are necessary for accessing associated media content, while ensuring that the media content is not accessed in violation of the usage rights. A content provider may deliver the media content and the associated usage rights to a first user terminal. The usage rights may be sharable as well as divisible. The first user terminal will account for all or that portion of the usage rights that are subsequently transferred, and may retain any remaining usage rights. The first user terminal may transfer all or a portion of any usage rights at the first user terminal to a second user terminal, wherein the transferred usage rights allow the second user terminal to access the media content. The second user terminal may also transfer the usage rights, and perhaps the media content, to other user terminals.

Abstract: The present invention provides a network based time-shifting architecture where broadcast content is replicated and delivered toward subscribers at different times in different content streams. In operation, a content source delivers unshifted content over a network to a media server, which replicates the unshifted content to provide multiple content blocks. Each content block represents a time-shifted content block of the unshifted content, and as such each time-shifted content block will have essentially the same content. At different times, each time-shifted content block is delivered over a transmission network toward the same or different subscribers. In one embodiment, the time-shifted content blocks are delivered directly or through an encryption function to a multicast server, which controls delivery of the different time-shifted content blocks to television clients of the subscribers.

Abstract: A system and method for securely partitioning a media library of a media-on-demand system is provided. Middleware instances are created for each user group defined in the media-on-demand system. Users or clients that are part of a particular user group can only access content that has been registered with the associated middleware instance. A common media server can service multiple middleware instances reducing hardware resources and administration costs. Only content that has been registered with the middleware associated with a particular user group is viewable by the user thus providing a more secure media library.

Abstract: The present invention provides a customer service gateway acting as an interface between various customer premise equipment for a customer and a local access network. The customer service gateway has one or more customer agents and network agents. A network agent is a secure and trusted agent of the service providers, and is not accessible by the customer or the customer premise equipment for manipulation. The customer service gateway may support different types of services using different types of media from the different service providers. In operation, the service providers may sent applications to a network agent, which will run the applications to implement functions to monitor or control services or service flows for the services. The monitoring and control functions may be used to implement various types of service or service flow analysis, as well as any type of tagging, characterization, or processing of the service flows.

Abstract: A system and method for preventing e-mail spoofing, in which a receiving e-mail checking server system sends a message to a confirmation server associated with a network domain of the sending system of a received e-mail message, to determine if the sender transmitted the message. The e-mail checking server sends a confirmation request e-mail, including a transmission time or unique message “key” associated with the received e-mail, to the sending domain's confirmation server. When a confirmation request is received at the confirmation server, it replies with an indication whether the message was sent at the time indicated in the confirmation request, and/or whether the message key matches that of a previously transmitted message. The confirmation server checks whether the message was in fact sent based on stored values corresponding to the send time and/or message key stored for the confirmation request message. A message may further include indication that its origin can be confirmed.