Logical roles are defined by package developers, and allow developers to define identities that each application uses to indicate access rights to its different objects. Logical roles may or may not replicate physical names already defined for your security provider.
Logical roles allow secured access to Unwired Platform resources for several users at once, and you can define them for one or more packages in a domain. If a developer has created a logical role for a package, you may need to manually map it to one or more physical roles.
In the absence of explicit mapping, the default role mapping is set to AUTO, which is equivalent of logical role mapping to a physical role of the same name, in the underlying provider of that security configuration.