How to implement the interface of Oauth2.0 's refresh token?

problem description
in Oauth2.0, when the access_token expires, you can use the previously obtained refresh_token to reapply for tokens. The problem now is that you don"t know how the authentication server reissues tokens to the client according to refresh_token.

the environmental background of the problem and what methods you have tried.
I have consulted some materials and feel that the implementation is diversified. The refresh interface of the authentication server mainly returns the following kinds of data:
1, returns brand-new access_token and refresh_token.
2. Return the new access_token, but the refresh_token is old. (it is possible that the expiration time of the old refresh_token will be updated)
3, return the old access_token and the old refresh_token. (I feel that the previous access_token can still be used because the expiration time has been updated.)

what result do you expect? What is the error message actually seen?
I personally feel that the first two are similar in nature, and the third is the old one, but the update time is not very good.
which of the above ways is better to ask the god to advise me? Or is there a better way to achieve it?

Mar.31,2021

personal advice No. 1, after all, you don't know if the user will accidentally let others know refresh_toekn , then it is obviously very dangerous in the case of 2 and 3.

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1b39f58-2c1e1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1b39f58-2c1e1.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?