diff --git a/docs_src/design/TOC.md b/docs_src/design/TOC.md
index 729c4e133f..08dbeb9ec9 100644
--- a/docs_src/design/TOC.md
+++ b/docs_src/design/TOC.md
@@ -12,6 +12,7 @@
 | [Core Data Retention and Persistent Cap](./ucr/Core-Data-Retention.md)              | Use Case for capping readings in Core Data                          |
 | [Device Parent-Child Relationships](./ucr/Device-Parent-Child-Relationships.md)     | Use Case for Device Parent-Child Relationships                      |
 | [Extending Device Data](./ucr/Extending-Device-Data.md)                             | Use Case for Extending of Device Data by Application Services       |
+| [Protocol Info In Device](./ucr/Protocol-Info-In-Device.md)                         | Use Case for adding Protocol Information into the Device object.    |
 | [Provision Watch via Device Metadata](./ucr/Provision-Watch-via-Device-Metadata.md) | Use Case for Provision Watching via Additional Device Metadata      |
 | [Record and Replay](./ucr/Record-and-Replay.md)                                     | Use Case for Recording and Replaying event/readings                 |
 | [System Events for Devices](./ucr/System-Events-for-Devices.md)                     | Use Case for System Events for Device add/update/delete             |
diff --git a/docs_src/design/ucr/Protocol-Info-In-Device.md b/docs_src/design/ucr/Protocol-Info-In-Device.md
new file mode 100644
index 0000000000..c7c97061c8
--- /dev/null
+++ b/docs_src/design/ucr/Protocol-Info-In-Device.md
@@ -0,0 +1,39 @@
+# Use Case Title
+Protocol-specific Attribute Values in Device
+
+## Submitters
+Darryl Mocek (Oracle Corporation)
+
+## Changelog
+
+## Market Segments
+Any segments using EdgeX with device services that contain protocol-specific values in Device Profile attributes.
+
+## Motivation
+The Device Profile describes a type of device.  There are many different manufacturers of the same type of device (e.g. HVAC).  The Device Profile of a specific type of device could used be for many or all of the Devices of that type, reducing the need to duplicate a Device Profile just to account for differences in the protocol-specific attribute values.
+
+## Target Users
+Any users that create Device Profiles and Devices that have protocol-specific attribute values.
+
+## Description
+The Device Profile **describes** the device type and its attributes, it's type.  Different manufacturers can build the same type of device using different protocols and the same device using the same protocol but different configuration (e.g. different Modbus HoldingRegister's).  For example, two different manufacturers may build an HVAC using ModBus, and another may build an HVAC using SNMP.  In the case of two Modbus devices, there will need to be two different Device Profiles, even though the devices are the same and have the same attributes, because the protocol configurations (e.g. HoldingRegister) will conflict.
+
+If all the protocol information resides in the Device definition (not just the protocol information, but the attribute-specific protocol information e.g. HOLDING_REGISTERS), which describes a specific (instance of a) device, only a single Device Profile is needed as all devices of the same type can use the same Device Profile.  This becomes more important as you have more devices, potentially increasing the number and management of Device Profiles when a single one will do.
+
+## Existing solutions
+<!--
+How is the given use case currently implemented in the industry, with or without EdgeX?
+List and describe each approach. Highlight possible gaps.
+-->
+
+## Requirements
+The requirement is to support the protocol-specific attribute values (e.g. HOLDING_REGISTER's) in the Device definition as well as the Device Profile (for backward compatibility).
+
+- If only the Device definition contains a protocol-specific attribute, it is used for that device.
+- If only the Device Profile contains a protocol-specific attribute, it is used for all Devices having that Device Profile.
+- If both the Device Profile and the Device definition contain a protocol-specific attribute, the entry in the Device definition overrides the one in the Device Profile.
+
+## Related Issues
+
+## References
+- https://github.com/edgexfoundry/device-modbus-go/blob/main/cmd/res/profiles/modbus.test.device.profile.yml