(Cat? OR feline) AND NOT dog?
Cat? W/5 behavior
(Cat? OR feline) AND traits
Cat AND charact*

This guide provides a more detailed description of the syntax that is supported along with examples.

This search box also supports the look-up of an IP.com Digital Signature (also referred to as Fingerprint); enter the 72-, 48-, or 32-character code to retrieve details of the associated file or submission.

Concept Search - What can I type?

For a concept search, you can enter phrases, sentences, or full paragraphs in English. For example, copy and paste the abstract of a patent application or paragraphs from an article.

Concept search eliminates the need for complex Boolean syntax to inform retrieval. Our Semantic Gist engine uses advanced cognitive semantic analysis to extract the meaning of data. This reduces the chances of missing valuable information, that may result from traditional keyword searching.

MDIO OBJECT INFORMATION MODEL

Publishing Venue

The IP.com Prior Art Database

Abstract

The present disclosure relates a Management Data Input/Output (MDIO) object information model for managing (Operations, Administration, Maintenance, and Provisioning (OAM&P)) pluggable optical modules. The present disclosure uses an object-oriented register-based interface to allow attributes within an object to be collected together. Further, understanding that the actions of creating, reading, updating, and deleting these objects may impede performance and in order to prevent any performance degradation, the present disclosure supports multiple object classes to be inspected at the same time (e.g., fault points, performance monitoring, object statuses).

Country

Undisclosed

Language

English (United States)

This text was extracted from a Microsoft Word document.

At least one non-text object (such as an image or picture) has been suppressed.

This is the abbreviated version, containing approximately
14% of the total text.

MDIO OBJECT INFORMATION MODEL

ABSTRACT

The present disclosure relates a Management
Data Input/Output (MDIO) object information model for managing (Operations,
Administration, Maintenance, and Provisioning (OAM&P)) pluggable optical
modules. The present disclosure uses an
object-oriented register-based interface to allow attributes within an object
to be collected together. Further, understanding that the actions of creating,
reading, updating, and deleting these objects may impede performance and in
order to prevent any performance degradation, the present disclosure supports
multiple object classes to be inspected at the same time (e.g., fault points,
performance monitoring, object statuses).

DETAILED DESCRIPTION

The present disclosure relates to
a Management Data Input/Output (MDIO) object information model. In networks, pluggable optical transceivers
are used for connectivity between switches, routers, servers, nodes, network
elements, etc. Pluggable optical
transceivers are standardized under various Multi-Source Agreements (MSAs) such
as CFP and variants thereof, QSFP and variants thereof, etc. From an Operations, Administration,
Maintenance, and Provisioning (OAM&P) perspective, these pluggable optical modules
need to be managed. The conventional
approach uses a register map and values that are accessed in memory using a
low-speed interface such as Inter-Integrated Circuit (I2C), MDIO, etc.

Even with the best of intentions,
over time the register map becomes nothing more than an eclectic set of
seemingly random attribute address locations.
While there appears to be some semblance of order, the module vendors
are left to fit in attributes in and around other attributes [fill in the
address holes] to ensure there is no attribute collision across the overall address
range. For completeness, there are address ranges wherein module vendors are
free to use at will. However, overtime, these vendor specific address ranges
become nothing more than a collection seemingly random attribute address
locations.

Thus, the industry practiced
solution are to use the defined register map and for additional attributes, the
vendor specified sections are used to unlock additional capabilities that are
beyond the specifications.

In the various MSA
specifications, there is various MDIO
management interface specification shortcomings such as:

•
Only a very few attributes appear to be logically
grouped together (i.e., 8000h range, the start
of B000h range).

•
No attribute addresses are included as the module
technology evolves (e.g., 10-year-old thinking by now defunct companies using
obsolete technology is still present in the interface specification).

•
Need to define attribute values (address location
values) for items that are not applicable to a particular optical module.

Variously, the present disclosure
provides an object-oriented register-based interface to allow attributes within
an object to be collected together. Further, recogni...