Patent Grant
11489931
Traditionally, service provider systems solely utilize wireline communication standards or protocols, such as a version of a Data Over Cable Service PHY device Specification (DOCSIS) communication standard or protocol, such as DOCSIS 3.0, DOCSIS 3.1, and/or DOCSIS 3.1 Full Duplex to provide some examples, to provide a service to one or more subscriber devices. As more wireline communication standards or protocols and wireless communication standards or protocols become available, it would be advantageous for service provider systems to implement these additional communication standards or protocols to provide the service.
The present disclosure is described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left most digit(s) of a reference number identifies the drawing in which the reference number first appears. In the accompanying drawings:
The present disclosure will now be described with reference to the accompanying drawings.
The present disclosure describes a point-to-multipoint communication system having a service provider system and one or more subscriber devices. The one or more subscriber devices include multiple physical layer (PHY) devices that can be used for upstream direction and/or downstream direction transfer of information to and/or from the service provider system. The one or more subscriber devices receive subscriber device configuration information from the service provider system indicating which of these multiple PHY devices are to be used for the upstream direction and/or the downstream direction transfer of the information to and/or from the service provider system. In some situations, the subscriber device configuration information identifies various types of information, such as video, audio, and/or data to provide some examples, to be transferred in the upstream direction and/or the downstream direction and/or one or more PHY devices to be used for transferring the various types of information.
Exemplary Point-to-Multipoint Communication System
In the exemplary embodiment illustrated in
The subscriber devices 104.1 through 104.n negotiate the upstream direction and/or the downstream direction transfer of the information with the service provider system 102. In an exemplary embodiment, this negotiation is performed upon activation of the service, for example, upon powering up the subscriber devices 104.1 through 104.n. In this exemplary embodiment, the subscriber devices 104.1 through 104.n represent universal subscriber devices that can be configured to transfer the information in the upstream direction and the downstream without the need for prior configuration of the subscriber devices 104.1 through 104.n which is conventionally achieved through prior configuration of specialized software within the subscriber devices 104.1 through 104.n by a specialized technician. The negotiation between the service provider system 102 and the subscriber devices 104.1 through 104.n can allow the subscriber devices 104.1 through 104.n to be configured in real-time often by customers of the service to transfer the information in the upstream direction and/or the downstream direction.
In the exemplary embodiment illustrated in
Moreover, in this exemplary embodiment, each of the subscriber devices 104.1 through 104.n and the service provider system 102 can optionally negotiate the types of information, such as video, audio, and/or data to provide some examples, to be transferred in the upstream direction and/or the downstream direction using the one or more negotiated PHY devices. In some situations, the service agreement predefines the one or more negotiated PHY devices to be used for the upstream direction and/or the downstream direction transfer of the information and/or the types of information, such as video, audio, and/or data to provide some examples, to be transferred in the upstream direction and/or the downstream direction. For example, each of the subscriber devices 104.1 through 104.n and the service provider system 102 can negotiate one or more wireless PHY devices are to be used for transferring data in the upstream direction and/or the downstream direction and one or more wireline PHY devices are to be used for transferring video and/or audio in the upstream direction and/or the downstream direction. As another example, each of the subscriber devices 104.1 through 104.n and the service provider system 102 can negotiate one or more wireline PHY devices are to be used for transferring video, audio, and/or data in the upstream direction and/or the downstream direction. As a further example, each of the subscriber devices 104.1 through 104.n and the service provider system 102 can negotiate one or more wireless PHY devices are to be used for transferring video, audio, and/or data in the upstream direction and/or the downstream direction.
The communication network 108 communicatively couples the service provider system 102 and the subscriber devices 104.1 through 104.n. The communication network 108 can implemented as a wireless communication network, a wired communication network, and/or any combination thereof that will be apparent to those skilled in the relevant art(s) without departing from the spirit and scope of the present disclosure. For example, the communication network 108 can include one or more radio networks, such as terrestrial radio frequency networks or satellite radio frequency networks, one or ore coaxial cable networks, and/or one or more fiber optic cable networks.
Exemplary Negotiation Between a Subscriber Device and a Service Provider System within the Point-to-Multipoint Communication System
At operation 202, the operational control flow 200 selects a PHY device from among multiple PHY devices of the subscriber device to communicate with the service provider system. As described above in
At operation 204, the operational control flow 200 scans a communication network, such as the communication network 108 as described above in
At operation 206, the operational control flow 200 determines whether the service provider identification signal from the service provider system. In some situations, the operational control flow 200 is unable to discover any service provider identification signals for any service provider systems during the scan of the communication network. In these situations, the operational control flow 200 reverts to operation 202 to select another PHY device from among multiple PHY devices of the subscriber device to communicate with the service provider system. In other situations, the operational control flow 200 discovers the service provider identification signal during the scan of the communication network. Thereafter, the operational control flow 200 determine whether the service provider identification signal corresponds to the service provider system or another service provider system without the service agreement. For example, the operational control flow 200 recovers the information from the service provider identification signal and compares this information with previously stored information of the service provider system within the subscriber device. In these situations, when the recovered information from the service provider identification signal does not match the previously stored information of the service provider system, the operational control flow 200 has discovered the other service provider system without the service agreement. Thereafter, the operational control flow 200 can revert to operation 204 to continue to scan the communication network for the service provider identification signal. Otherwise, the operational control flow 200 has discovered the service provider system when the recovered information from the service provider identification signal matches the previously stored information of the service provider system. Thereafter, the operational control flow 200 proceeds to operation 208.
At operation 208, the operational control flow 200 receives subscriber device configuration information from the service provider system to configure the subscriber device for the upstream direction and/or the downstream direction transfer of information between the service provider system and the subscriber device. In an exemplary embodiment, the upstream direction and/or the downstream direction transfer of the information between the service provider system and the subscriber device is in accordance with the service agreement. In this exemplary embodiment, the service agreement identifies various types of information, such as video, audio, and/or data to provide some examples, to be transferred in the upstream direction and/or the downstream direction and/or one or more PHY devices, for example, one or more wireless PHY devices or protocols and/or one or more wireline PHY devices, to be used for transferring the various types of information.
In this exemplary embodiment, the subscriber device configuration information identifies one or more PHY devices from among the multiple PHY devices to be used for the upstream direction and/or the downstream direction transfer of information between the service provider system and the subscriber device. Optionally, the subscriber device configuration information can identify types of information, such as the video, the audio, and/or the data to provide some examples, to be transferred in the upstream direction and/or the downstream direction using the one or more PHY devices. For example, the configuration information can indicate a wireless PHY device, such as Wi-Fi to provide an example, is to be used for transferring data in the upstream direction and/or the downstream direction and a wireline PHY device, such as a DOCSIS compliant PHY device, fiber optic PHY device, or Ethernet PHY device to provide some examples, is to be used for transferring video and/or audio in the upstream direction and/or the downstream direction. As another example, the configuration information can indicate the wireline PHY device is to be used for transferring video, audio, and/or data in the upstream direction and/or the downstream direction. As a further example, the configuration information can indicate the wireless PHY device is to be used for transferring video, audio, and/or data in the upstream direction and/or the downstream direction. In some situations, the subscriber device configuration information need not identify the PHY device from operation 202 as being used to transferring video, audio, and/or data in the upstream direction and/or the downstream direction.
At operation 210, the operational control flow 200 configures the subscriber device in accordance with the subscriber device configuration information. In an exemplary embodiment, the operational control flow 200 can activate one or more wireless PHY devices and/or one or more wireline PHY devices from among the multiple PHY devices of the subscriber device in accordance with the subscriber device configuration information to communicate with the service provider system. For example, the operational control flow 200 can request the consumer of the service that is associated with the subscriber device to communicatively couple, for example, plug in, one or more communication cables, such as one or more coaxial cables and/or one or more fiber optics cables to provide some examples, that are associated with one or more wireline PHY devices in accordance with the subscriber device configuration information. In this example, the operational control flow 200 activates a wireline PHY device from among the one or more wireline PHY devices which is communicatively coupled to the one or more communication cables to communicate with the service provider system. In another example, the operational control flow 200 can request identifying information, such as a username or a password to provide some examples, from the consumer of the service before selecting the PHY device. In this other example, the operational control flow 200 activates a wireless PHY device from among the one or more wireless PHY devices which is associated with the identifying information to communicate with the service provider system.
Exemplary Subscriber Device within the Point-to-Multipoint Communication System
The PHY circuitry 302 represents an interface between the subscriber device 300 and a communication network, such as the communication network 108 as described above in
During a scan mode of operation, the PHY circuitry 302 selects one or more of the wireline PHY devices 308.1 through 308.a and the wireless PHY devices 310.1 through 310.b to scan the communication network for a service provider identification signal from the service provider system. In this scan mode of operation, the PHY circuitry 302 iteratively selects, for example, in a round-robin manner, through the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b to scan the communication network for a service provider identification signal from the service provider system until discovering the service provider system. Thereafter, one of more of the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b which discovered the service provider identification signal demodulates, decodes, and/or converts the service provider identification signal to recover information from the service provider identification signal that uniquely identifies the service provider system to the subscriber device. For example, the information can include a network identifier of the service provider system, a geographic location of the service provider system, and/or a network address of the service provider system to provide some examples. Thereafter, these PHY devices which discovered the service provider identification signal sends the recovered information to the MAC circuitry 304 to determine whether the service provider identification signal corresponds to the service provider system or another service provider system without the service agreement.
During a configuration mode of operation, the one of more of the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b which discovered the service provider identification signal are utilized by the PHY circuitry 302 to receive subscriber device configuration information from the service provider system to configure the PHY circuitry 302 for the upstream direction and/or the downstream direction transfer of information between the service provider system and the subscriber device 300. In an exemplary embodiment, the subscriber device configuration information identifies the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b to be used for the upstream direction and/or the downstream direction transfer of information between the service provider system and the subscriber device. Optionally, the subscriber device configuration information can identify types of information, such as the video, the audio, and/or the data to provide some examples, to be transferred in the upstream direction and/or the downstream direction using the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b. For example, the configuration information can indicate a first wireless PHY device from among the wireless PHY devices 310.1 through 310.b is to be used for transferring data in the upstream direction and/or the downstream direction and a first wireline PHY device from among the wireline PHY devices 308.1 through 308.a is to be used for transferring video and/or audio in the upstream direction and/or the downstream direction. As another example, the configuration information can indicate the first wireless PHY device is to be used for transferring video, audio, and/or data in the upstream direction and/or the downstream direction. As a further example, the configuration information can indicate the first wireline PHY device is to be used for transferring video, audio, and/or data in the upstream direction and/or the downstream direction.
During a service mode of operation, the PHY circuitry 302 transfers information between the service provider system and the MAC 308 utilizing the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b which have been identified in the subscriber device configuration information.
The MAC circuitry 304 represents an interface between the PHY circuitry 302 and the processor circuitry 306. The MAC circuitry 304 manages and maintains communication of the subscriber device 300 by coordinating access to the PHY circuitry 302 and formats communication in accordance with the one or more wireline communication standards or protocols that are supported by the wireline PHY devices 308.1 through 308.a and the one or more wireless communication standards or protocols that are supported by the wireless PHY devices 310.1 through 310.b. For example, the MAC circuitry 304 routes the types of information, such as the video, the audio, and/or the data to provide some examples, to be transferred in the upstream direction and/or the downstream direction to their corresponding wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b in accordance with the subscriber device configuration information. Moreover, in the downstream direction, the MAC circuitry 304 decapsulates or de-frames information from the PHY circuitry 302 in accordance with the one or more wireline communication standards or protocols and/or the one or more wireless communication standards or protocols and provides this decapsulated or de-framed information to the processor circuitry 306. Otherwise in the upstream direction, the MAC circuitry 304 encapsulates or frames information from the processor circuitry 306 in accordance with the one or more wireline communication standards or protocols and/or the one or more wireless communication standards or protocols and provides this encapsulated or framed information to the PHY circuitry 302.
The processor circuitry 306 controls overall operation and/or configuration of the subscriber device 300. During the scan mode of operation, the processor circuitry 306 monitors the decapsulated or de-framed information provided by the MAC circuitry 304 from the service provider identification signal to determine whether the selected one or more of the wireline PHY devices 308.1 through 308.a and the wireless PHY devices 310.1 through 310.b have discovered the service provider identification signal from the service provider system. For example, the processor circuitry 306 compares the decapsulated or de-framed information provided by the MAC circuitry 304 with previously stored information of the service provider system within the subscriber device 300. In this example, when the decapsulated or de-framed information provided by the MAC circuitry 304 does not match the previously stored information of the service provider system, the selected one or more of the wireline PHY devices 308.1 through 308.a and the wireless PHY devices 310.1 through 310.b have discovered the other service provider system without the service agreement. Otherwise, the selected one or more of the wireline PHY devices 308.1 through 308.a have discovered the service provider system when the decapsulated or de-framed information provided by the MAC circuitry 304 matches the previously stored information of the service provider system.
During the configuration mode of operation, the processor circuitry 306 monitors the decapsulated or de-framed information provided by the MAC circuitry 304 from the subscriber device configuration information to determine the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b to be used for the upstream direction and/or the downstream direction transfer of information between the service provider system and the subscriber device. Optionally, the processor circuitry 306 can determine types of information, such as the video, the audio, and/or the data to provide some examples, to be transferred in the upstream direction and/or the downstream direction using the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b. Thereafter, the processor circuitry 306 sends one or more activation commands to the PHY circuitry 302 to activate the wireline PHY devices 308.1 through 308.a and/or the wireless PHY devices 310.1 through 310.b to be used for the upstream direction and/or the downstream direction transfer of the information. Optionally, the processor circuitry 306 can send one or more deactivation commands to the PHY circuitry 302 to deactivate wireline PHY devices 308.1 through 308.a and/or wireless PHY devices 310.1 through 310.b not to be used for the upstream direction and/or the downstream direction transfer of the information. In some situations, the processor circuitry 306 can send various instructions to a consumer of the service that is associated with the subscriber device 300 to communicatively couple, for example, plug in, one or more communication cables, such as one or more coaxial cables and/or one or more fiber optics cables to provide some examples, to the wireline PHY devices 308.1 through 308.a. Optionally, the operational control flow 200 can request identifying information, such as a username or a password to provide some examples, from the consumer of the service before the upstream direction and/or the downstream direction transfer of the information.
During the service mode of operation, the processor circuitry 306 transfers information between the consumer of the service provider system and the MAC 308 in accordance with the service agreement.
Exemplary Service Provider System within the Point-to-Multipoint Communication System
The PHY circuitry 402 represents an interface between the service provider system 400 and a communication network, such as the communication network 108 as described above in
The PHY circuitry 402 selects one or more of the wireline PHY devices 408.1 through 408.a and the wireless PHY devices 410.1 through 410.b to provide a service provider identification signal to the communication network. In an exemplary embodiment, the service provider identification signal includes information that uniquely identifies the service provider system 400 to the one or more subscriber devices. For example, the information can include a network identifier of the service provider system, a geographic location of the service provider system, and/or a network address of the service provider system to provide some examples. Thereafter, the selected one or more of the wireline PHY devices 408.1 through 408.a and the wireless PHY devices 410.1 through 410.b receive a request for subscriber device configuration information from the one or more one or more subscriber devices. In an exemplary embodiment, the subscriber device configuration information identifies various PHY devices of the one or more subscriber devices to be used for the upstream direction and/or the downstream direction transfer of information between the service provider system 400 and the one or more subscriber devices. Optionally, the subscriber device configuration information can identify types of information, such as the video, the audio, and/or the data to provide some examples, to be transferred in the upstream direction and/or the downstream direction using the various PHY devices of the one or more subscriber devices. The PHY circuitry 402 then transfers information between the MAC 408 and the one or more subscriber devices utilizing the various PHY devices of the one or more subscriber devices in accordance with the subscriber device configuration information.
The MAC circuitry 404 represents an interface between the PHY circuitry 402 and the processor circuitry 406. The MAC circuitry 404 manages and maintains communication of the service provider system 400 by coordinating access to the PHY circuitry 402 and formats communication in accordance with the one or more wireline communication standards or protocols that are supported by the wireline PHY devices 408.1 through 408.a and the one or more wireless communication standards or protocols that are supported by the wireless PHY devices 410.1 through 410.b. In the downstream direction, the MAC circuitry 404 decapsulates or de-frames information from the PHY circuitry 402 in accordance with the one or more wireline communication standards or protocols and/or the one or more wireless communication standards or protocols and provides this decapsulated or de-framed information to the processor circuitry 406. Otherwise in the upstream direction, the MAC circuitry 404 encapsulates or frames information from the processor circuitry 406 in accordance with the one or more wireline communication standards or protocols and/or the one or more wireless communication standards or protocols and provides this encapsulated or framed information to the PHY circuitry 402.
The processor circuitry 406 controls overall operation and/or configuration of the service provider system 400. For example, the processor circuitry 406 receives the decapsulated or de-framed request for the subscriber device configuration information from the MAC circuitry 404. This request includes information that uniquely identifies the one or more subscriber devices to the service provider system 400. For example, the information can include one or more network identifiers of the one or more subscriber devices, one or more geographic locations of the one or more subscriber devices, and/or one or more network addresses of the one or more subscriber devices to provide some examples. In this example, the processor circuitry 406 queries the service agreement storage 408 for the subscriber device configuration information corresponding to the information.
The service agreement storage 408 stores subscriber device configuration information for all subscribers having service agreements with the service provider system 400 to implement the service. In an exemplary embodiment, the service agreement storage 408 stores the subscriber device configuration information in a database that is indexed to information that uniquely identifies each subscriber. The service agreement storage 408 can include non-transitory machine-readable mediums such as read only memory (ROM), random access memory (RAM), magnetic disk storage media, optical storage media, and/or flash memory devices to provide some examples. In an exemplary embodiment, the service agreement identifies various types of information, such as video, audio, and/or data to provide some examples, to be transferred in the upstream direction and/or the downstream direction between the service provider system 400 and subscribers to the service agreement and/or one or more PHY devices of the subscribers, for example, one or more wireless PHY devices or protocols and/or one or more wireline PHY devices, to be used for transferring the various types of information.
Although the embodiments of the disclosure described herein refer specifically, and by way of example, to cable modem systems, including cable modem termination systems and cable modems, it will be readily apparent to those skilled in the relevant art(s) that the disclosure is equally applicable to satellite systems, optical communication systems, telephone wire systems, home network systems, and/or any combination thereof. It will be readily apparent to those skilled in the relevant art(s) that the disclosure is applicable to any point-to-multipoint system.
The Detailed Description referred to accompanying figures to illustrate exemplary embodiments consistent with the disclosure. References in the disclosure to “an exemplary embodiment” indicates that the exemplary embodiment described can include a particular feature, structure, or characteristic, but every exemplary embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same exemplary embodiment. Further, any feature, structure, or characteristic described in connection with an exemplary embodiment can be included, independently or in any combination, with features, structures, or characteristics of other exemplary embodiments whether or not explicitly described.
The Detailed Description is not meant to limiting. Rather, the scope of the disclosure is defined only in accordance with the following claims and their equivalents. It is to be appreciated that the Detailed Description section, and not the Abstract section, is intended to be used to interpret the claims. The Abstract section can set forth one or more, but not all exemplary embodiments, of the disclosure, and thus, are not intended to limit the disclosure and the following claims and their equivalents in any way.
The exemplary embodiments described within the disclosure have been provided for illustrative purposes and are not intended to be limiting. Other exemplary embodiments are possible, and modifications can be made to the exemplary embodiments while remaining within the spirit and scope of the disclosure. The disclosure has been described with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined so long as the specified functions and relationships thereof are appropriately performed.
Embodiments of the disclosure can be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the disclosure can also be implemented as instructions stored on a machine-readable medium, which can be read and executed by one or more processors. A machine-readable medium can include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing circuitry). For example, a machine-readable medium can include non-transitory machine-readable mediums such as read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; and others. As another example, the machine-readable medium can include transitory machine-readable medium such as electrical, optical, acoustical, or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.). Further, firmware, software, routines, instructions can be described herein as performing certain actions. However, it should be appreciated that such descriptions are merely for convenience and that such actions in fact result from computing devices, processors, controllers, or other devices executing the firmware, software, routines, instructions, etc.
The Detailed Description of the exemplary embodiments fully revealed the general nature of the disclosure that others can, by applying knowledge of those skilled in relevant art(s), readily modify and/or adapt for various applications such exemplary embodiments, without undue experimentation, without departing from the spirit and scope of the disclosure. Therefore, such adaptations and modifications are intended to be within the meaning and plurality of equivalents of the exemplary embodiments based upon the teaching and guidance presented herein. It is to be understood that the phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the present specification is to be interpreted by those skilled in relevant art(s) in light of the teachings herein.
The present application is a continuation of U.S. patent application Ser. No. 16/039,669, filed Jul. 19, 2018, now U.S. Pat. No. 10,757,198, which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 7570612 | Loc | Aug 2009 | B1 |
| 10757198 | Almeida et al. | Aug 2020 | B1 |
| 20040162092 | Marisco et al. | Aug 2004 | A1 |
| 20060268902 | Bonner | Nov 2006 | A1 |
| 20070191057 | Kamada | Aug 2007 | A1 |
| 20080095173 | Bugenhagen | Apr 2008 | A1 |
| 20080175362 | Bangor | Jul 2008 | A1 |
| 20110222477 | Wu | Sep 2011 | A1 |
| 20120094594 | Rofougaran et al. | Apr 2012 | A1 |
| 20120220240 | Rothschild et al. | Aug 2012 | A1 |
| 20130150096 | Hanchate | Jun 2013 | A1 |
| 20140200048 | Cheng | Jul 2014 | A1 |
| 20140256302 | Chirayil | Sep 2014 | A1 |
| 20150281929 | Shih et al. | Oct 2015 | A1 |
| 20160119860 | Chawla | Apr 2016 | A1 |
| 20160381710 | Bansal | Dec 2016 | A1 |
| 20170048855 | Garg | Feb 2017 | A1 |
| 20170134994 | Chinthalapudi | May 2017 | A1 |
| 20180027406 | Murray | Jan 2018 | A1 |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 16039669 | Jul 2018 | US |
| Child | 16999675 | US |
