composer require drupal/sms

when use composer require drupal/sms show this erro but work whit composer require 'drupal/smsframework:^2.1'.

Problem 1
- drupal/sms[1.0.0, ..., 1.1.0] require drupal/core ^8.0 -> found drupal/core[8.0.0, ..., 8.9.20] but the package is fixed to 10.2.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/sms 1.2.0 requires drupal/core ^8.5 -> found drupal/core[8.5.0, ..., 8.9.20] but the package is fixed to 10.2.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/sms 1.3.0 requires drupal/core >=8.6 <8.9 -> found drupal/core[8.6.0, ..., 8.8.12] but the package is fixed to 10.2.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/sms[2.0.0, ..., 2.0.1] require drupal/core ^8.9 || ^9 -> found drupal/core[8.9.0, ..., 8.9.20, 9.0.0, ..., 9.5.11] but the package is fixed to 10.2.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- drupal/sms 2.1.0 requires drupal/core ^9.2 -> found drupal/core[9.2.0, ..., 9.5.11] but the package is fixed to 10.2.6 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
- Root composer.json requires drupal/sms * -> satisfiable by drupal/sms[1.0.0, 1.1.0, 1.2.0, 1.3.0, 2.0.0, 2.0.1, 2.1.0].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require drupal/sms:*" to figure out if any version is installable, or "composer require drupal/sms:^2.1" if you know which you need.