Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
  • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
  • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
  • H04N21/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
  • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L12/40—Bus networks
  • H04L12/407—Bus networks with decentralised control
  • H04L12/413—Bus networks with decentralised control with random access, e.g. carrier-sense multiple-access with collision detection [CSMA-CD]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
  • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
  • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
  • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
  • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
  • H04N7/00—Television systems
  • H04N7/10—Adaptations for transmission by electrical cable
  • H04N7/106—Adaptations for transmission by electrical cable for domestic distribution

Definitions

• the disclosed method and apparatus relates to communications systems, and more particularly, some embodiments relate to a method and apparatus for interfacing with the data link layer of a seven layer open systems interconnection (OSI) communication protocol stack.
• OSI open systems interconnection
• Home networks, and home entertainment networks in particular, are becoming more popular. These networks allow communications between various electronic devices in the home, most particularly, home entertainment devices, such as Televisions (TVs), home computers, laptop computers, digital video recorders (DVRs), cable set top boxes, digital video devices (DVDs), audio equipment, etc.
• home entertainment devices such as Televisions (TVs), home computers, laptop computers, digital video recorders (DVRs), cable set top boxes, digital video devices (DVDs), audio equipment, etc.
• TVs Televisions
• DVRs digital video recorders
• cable set top boxes such as the communication medium over which communications through the network will take place.
• DVDs digital video devices
• audio equipment etc.
• OSI Open Systems Interconnection
• FIG. 1 There are multiple configurations possible in the deployments of such networks.
• a satellite service provider and a cable television service provider provide content to the network.
• a satellite antenna 101 (with the associated amplifiers and front end equipment) is coupled to a splitter 103.
• the splitter 103 provides four taps out to the rest of the network 100.
• Each of the four taps is coupled to one of four layer 2 (L2) devices 105a, 105b, 105c, 105d.
• L2 devices typically have to handle both the presence and the absence of an Ethernet router (with or without Dynamic Host Configuration Protocol (DHCP)).
• DHCP Dynamic Host Configuration Protocol
• each L2 device will have to deal with a random startup order of the other network devices (i.e., the L2 device may start up before a DHCP router is ready).
• the L2 device may start up before a DHCP router is ready.
• network units connected behind an L2 device 105 there can be an incremental addition of network units connected behind an L2 device 105.
• the configuration shown in Figure 1 would likely be deployed by a commercial operator (such as the satellite service provider).
• Each of the L2 devices 105 receives packets over the coaxial connection from the satellite antenna 101. These packets are converted to an Ethernet format, output by the L2 devices 105 and distributed to the rest of the network 100.
• Figure 2 illustrates a similar configuration.
• an internet cable modem 201 provided by a cable television service provider is coupled to a splitter 203 with four taps that connect to the rest of the network 200.
• L2 devices 205 are coupled to the taps of the splitter 203 and provide a bridge between the cable modem 201 and the rest of the network 200.
• As the network grows and matures it may become desirable to update the functionality of the L2 devices 105, 205. Therefore, it is desirable to have an efficient way to perform the update of these L2 devices 105, 205. Furthermore, other management communication may be desirable to allow commands to be provided directly to the L2 devices.
• Figure 1 illustrates one configuration of a home network.
• Figure 2 illustrates a second configuration of a home network.
• FIG. 3 is a simplified block diagram of an L2 device in accordance with one embodiment of the disclosed method and apparatus.
• Figure 4 is an illustration of one image update process in accordance with the disclosed method and apparatus.
• Figure 5 is an illustration of an L2 hostless product.
• Figure 6 and Figure 7 illustrate virtual pages and addressing in accordance with one embodiment of the disclosed method and apparatus.
• FIG. 3 is a simplified block diagram of a layer 2 (L2) device 300.
• the L2 device of Figure 3 includes a processor 302, flash memory 304, physical layer (PHY) device 306, an RJ-45 style connector 310, a power indicating light emitting diode (LED) 312, a first and second RF connector 308, 314, a first and second filter 316, 318, an activity LED 320, a PHY rate LED 322, a reset switch 324, a serial port 326 and a 5 volt DC power supply 328.
• PHY physical layer
• the software image in the L2 device 300 can be updated over any of three interfaces provided in order to support both operator and retail deployments.
• the three interfaces include the serial port 326, the Ethernet port or Multi-media over Coax Alliance (MoCA).
• MoCA Multi-media over Coax Alliance
• the user when the L2 device 300 is purchased by a user directly from a retail store, the user can update the L2 device 300 via any of the interfaces that are populated.
• a user can update the L2 device 300 without having to disconnect the L2 device and connect it directly to a personal computer (PC).
• PC personal computer
• the L2 device continues to perform its MoCA operation without degradation to the MoCA performance.
• the user (operator technician in the operator case or customer in the retail case) may connect to the L2 device 300 and request that the L2 device download a different version of the firmware.
• the L2 device will download the firmware, verify that the firmware is valid for this type of unit and apply the firmware if so requested by the user. In accordance with one embodiment, applying the firmware will require a restart of the L2 device.
• the update mechanism within the L2 device 300 ensures that there is always one known good image on the device.
• Figure 4 is an illustration of one image update process in accordance with the disclosed method and apparatus.
• the flash layout supports both an active image and a backup image.
• the downloaded (new) image shall be validated prior to altering the backup image.
• the newly downloaded image will become the active image, while the previously active image becomes the backup image as illustrated in Figure 4.
• the field image update mechanism shall rely on a 3rd image area in flash memory 304 to store the new image as it is being downloaded.
• the L2 device 300 will maintain the original equipment manufacturer (OEM) customized settings and the customer settings.
• OEM original equipment manufacturer
• the interface to the L2 device will provide access to controls, configuration and diagnostics.
• a shell interface is provided consistent with other devices. The purpose of the interface is to ensure interface compatibility across a family of products and so provide an accelerated time to market for multiple partners that need access to control, configuration or diagnostics in MoCA nodes.
• Textual binding allows different programming languages to issue commands to the L2 devices without the need to develop or port a programming interface (such as a clink API) to that particular language (e.g.: JAVA, perl).
• a programming interface such as a clink API
• Virtual pages allow functional areas to be separated that are typically developed by separate groups. Pages could also be assigned to OEMs, original device manufacturers (ODMs) or service providers in products when they have the ability to add functionality to the software.
• ODMs original device manufacturers
• Virtual registers provide a more compact and generic means to interface with the L2 device 300 than can be provided by fully descriptive text.
• the use of virtual pages also isolates the user from the specifics regarding from where the data is obtained and to where data is written.
• the interface is accessible via any of the physical interfaces available on the L2 device 300, including: (1) serial port 326 using an 8N1 data format with a data rate of 115.2 kbps; (2) Ethernet, addressed through IP address and connecting via transmission control protocol (TCP) to a socket; (3) MoCA, addressed through IP address and connecting via TCP to a socket; (4) TCP via a predetermined port number.
• serial port 326 using an 8N1 data format with a data rate of 115.2 kbps
• Ethernet addressed through IP address and connecting via transmission control protocol (TCP) to a socket
• MoCA addressed through IP address and connecting via TCP to a socket
• TCP transmission control protocol
• the interface is "connection oriented" to allow a client to issue a sequence of commands to the L2 device 300. That is, a client may forget to disconnect from the unit once that client has completed its operation, in accordance with one embodiment of the disclosed method and apparatus. Therefore, upon receiving a connection request from another client, the firmware shall verify that the initial client still needs the interface.
• the interface can be human readable (ASCII).
• ASCII human readable
• the interface will have the following attributes:
• command packets Two types of packets are exchanged: command packets and result code packets.
• the interface is synchronous, meaning that a maximum of one command will be in progress at any given time. Additional concurrent commands are not buffered. Therefore, if a second command is received before the initial command completes, an error result code is issued.
• the firmware is viewed as a register mapped device with a virtual address map using "big endian" addressing in which low order bytes are stored in the higher order addresses and high order bytes are stored in lower order address. It will be understood by those skilled in the art that in an alternative embodiment, any other addressing scheme can be used.
• the virtual map concept in accordance with one embodiment is described in more detail below.
• Each register is 32 bits in length when it comes to the address map, but allows virtually mapping larger areas to that address.
• a register may be the address to access a software buffer. Reading N bytes from that buffer will return the N first bytes within that buffer.
• white spaces are used as delimiters (single white space is a delimiter; successive white spaces not allowed) for command and parameters. A carriage return indicates the end of the packet. Line feeds are ignored.
• non-ASCII characters generate an error response on the next carriage return received.
• the backspace character is not supported.
• a prompt ">" is provided upon connect and each time the L2 device 300 is ready for the next command (upon receiving an empty line with a carriage return; or after returning data in a synchronous response; or after sending data in an asynchronous notification).
• the interface is case sensitive and expects lower case.
• the interface does not provide an echo. If the user uses wishes to view the commands sent, the use can enable a local echo on the terminal used.
• cmd is issued by the user and is one of the supported
• Oxcd Oxef when listed from byte 0 to byte 7 in incremental byte addresses. It should be noted that for the purposes of this disclosure, the hexidecimal value "1A" is written as “Ox la", where the prefix "Ox" indicates that the value is shown in hexidecimal format:
• Data may be multiple of 8 bits, 16 bits or 32 bits (these are exclusive and each 8/16/32 element shall be separate with a white space). It may be provided in hexadecimal or decimal format. To provide hexadecimal values, prepend the value with "Ox". Data shall be provided MSB first (or most significant 16 bits or most significant 32 bits).
• Data may be multiple of 8 bits, 16 bits or 32 bits (these are exclusive and each 8/16/32 element shall be separate with a white space). It may be provided in hexadecimal or decimal format. To provide hexadecimal values, prepend the value with "Ox". Data shall be provided MSB first (or most significant 16 bits or most significant 32 bits).
• page ⁇ pageid> Selects the virtual page to be accessed for the following commands.
• Pageid Virtual page selected:
• MoCA host functionality all host functionalities specific controls, configuration or diagnostics
• Chip registers virtual page (effectively provides direct access to chip)
• Each page 601, 603, 605 has a number of registers 607, 609, 611, 613.
• Each register 607, 609, 611, 613 provides access to a particular function or data. In one embodiment, each may point to more than 32 bits of data.
• the user of the shell API does not need to know where the data is physically located (NVM, RAM, image itself). Because the same shell structure can be used by various devices, the user maintains a consistent access method across L2 hosted, L2 hostless and Layer 3 (L3) products.
• NVM non-transitory computer-readable media
• L3 Layer 3
• no programming interface e.g. C/C++ library
• a device API such as the "c.Link API" may be ported to access the shell.
• the L2 device can: use an IP address assigned via DHCP, statically or through LLA; consume IP packets that are targeted to that IP address; be discovered on the network; and limit the required footprint.
• the L2 hostless dongle may have its IP address configuration in one of three ways:
• the user may assign a static IP address and configuration.
• Dynamically through DHCP (default) the user may set the unit to request its IP address from a DHCP server on the network.
• Dynamically through LLA when configured for DHCP, if the DHCP server does not provide an IP address within one minute (no DHCP server present on the network or DHCP server being down), the unit shall still obtain an IP address automatically; to that end it shall negotiate via LLA with other devices on the network. When the unit obtains an LLA negotiated IP address, the unit shall continue to attempt to obtain a DHCP IP address (5 minutes interval) and if a DHCP lease is obtained, the unit shall switch back to DHCP and drop any on-going connection to that unit.
• any broadcast to obtain an IP address shall occur on both network interfaces (Ethernet and MoCA) as the remote devices may be located on either of these network interfaces.
• the L2 device will be addressable by machines located either on the Ethernet end or on the MoCA end of its interfaces. This implies the CCPU firmware and TCs firmware shall be modified to route locally IP frames that are targeted to its Ethernet MAC. In addition, the firmware will be modified to duplicate broadcast IP frames for local consumption and pass-through to the other network interface.
• a group of items linked with the conjunction "and” should not be read as requiring that each and every one of those items be present in the grouping, but rather should be read as “and/or” unless expressly stated otherwise.
• a group of items linked with the conjunction "or” should not be read as requiring mutual exclusivity among that group, but rather should also be read as “and/or” unless expressly stated otherwise.
• items, elements or components of the disclosed method and apparatus may be described or claimed in the singular, the plural is contemplated to be within the scope thereof unless limitation to the singular is explicitly stated.
• module does not imply that the components or functionality described or claimed as part of the module are all configured in a common package. Indeed, any or all of the various components of a module, whether control logic or other components, can be combined in a single package or separately maintained and can further be distributed in multiple groupings or packages or across multiple locations.

Landscapes

• Engineering & Computer Science (AREA)
• Signal Processing (AREA)
• Computer Networks & Wireless Communication (AREA)
• Multimedia (AREA)
• Computer Security & Cryptography (AREA)
• Communication Control (AREA)
• Computer And Data Communications (AREA)
• Telephonic Communication Services (AREA)
• Small-Scale Networks (AREA)
• Information Transfer Systems (AREA)

Priority Applications (6)

Applications Claiming Priority (2)

Publications (1)

Family

ID=44225488

Family Applications (1)

Country Status (10)

Families Citing this family (5)

Citations (4)

Family Cites Families (12)

• 2010
  • 2010-12-23 KR KR1020127016680A patent/KR20120125238A/ko not_active Withdrawn
  • 2010-12-23 US US12/977,778 patent/US20110167466A1/en not_active Abandoned
  • 2010-12-23 PE PE2012000895A patent/PE20130373A1/es not_active Application Discontinuation
  • 2010-12-23 MX MX2012007862A patent/MX2012007862A/es active IP Right Grant
  • 2010-12-23 BR BR112012016550A patent/BR112012016550A2/pt not_active IP Right Cessation
  • 2010-12-23 WO PCT/US2010/062050 patent/WO2011084844A1/en not_active Ceased
  • 2010-12-23 CA CA2785691A patent/CA2785691A1/en not_active Abandoned
  • 2010-12-23 JP JP2012547175A patent/JP2013516844A/ja active Pending
• 2012
  • 2012-07-01 IL IL220710A patent/IL220710A0/en unknown
  • 2012-07-04 CL CL2012001811A patent/CL2012001811A1/es unknown

Patent Citations (4)

Also Published As

Similar Documents

Legal Events