Maintenance requirements and new requirements

In general, the project time required for maintenance is urgent. Maintenance is required. Users are waiting for release. In fact, our definition of maintenance requirements and new requirements is not clear here.
How can this problem be solved? My personal understanding:
Maintenance Requirement refers to the requirement documents for users to raise problems in the system usage process and integrate some functions that users feel need to improve the system.
A new requirement is a requirement document created when the user does not meet the requirements of the current system and does not include the new features in the previous requirement document, it does not contain user bugs that the user continues to solve.
Therefore, I personally distinguish from the definition. Most maintenance requirements only fix and verify bugs for user problems. Of course, some user interface experience and new small functions are also incorporated. The new requirements may not be a small new feature point in project development.
For large project system branches and functional modules, more details are required for writing business rules.

Maintenance requirements and new requirements