How do I understand the OAuth2 and OIDC JWTs that are generated or accepted by Identity Cloud or AM (All versions)?

Used to authenticate the client application. By checking the signature, Identity Cloud or AM can be certain that the request was made by the client application, without needing the client credential in the POST parameter.

This is the recommended way to authenticate the client.

Used to dynamically register clients. 

A software statement is a JWT that holds registration claims about the client, such as the issuer and the redirection URIs that it will register.

There are several reasons to use a request parameter (request or request_uri), including the ability to obscure the request from the user by encrypting the request parameter.

Using the request parameter with the authorization code grant flow is advised since this grant requires the user to interact; however, they will be able to read the request unless it is encrypted.

There are other reasons to use the request parameter, which you can find in the standards section 6.

A Remote Consent Service handles the consent-gathering part of an OAuth 2.0 flow.

AM creates the consent request JWT that contains the necessary information to render a consent gathering page.

Used to identify the user when performing Client Initiated Backchannel Authentication (CIBA).

CIBA allows a client application, known as the consumption device, to obtain authentication and consent from a user, without requiring the user to interact with the client directly.