Yes, I added some code to the umbim source code. The major purpose is to intergate the AKA_AUTH to our call flow. I want to simulate an LTE connection via software. The software uses EAP AKA for the authenciation. It works well with a software AKA library. Now I want to replace the soft aka library with the SIM card via MBIM. That’s why I tried the MC7455 with the MBIM interface. I believe the whole procedures works well, as I can make a connection to the LTE packet core via the soft aka library.
It is not easy to copy the whole source code here, I list some related cose as below:
//the request structure
struct mbim_auth_aka_q {
/* array type: byte-array /
uint8_t rand[MBIM_AUTH_RAND_LEN];
/ array type: byte-array */
uint8_t autn[MBIM_AUTH_RAND_LEN];
} attribute((packed));
//send the aka parameters to the mbim
//the __autn and __rand1 are retrieved from the AAA server
static int
mbim_aka_request(void)
{
struct mbim_auth_aka_q *rs =
(struct mbim_auth_aka_q *) mbim_setup_command_msg(basic_auth,
MBIM_MESSAGE_COMMAND_TYPE_QUERY, MBIM_CMD_AUTH_AKA,
sizeof(struct mbim_auth_aka_q));
So from your point of view, the AKA works as expected. It must be a good begin for me
Is there any mbim AKA samples? or do you have the AKA authention experiences on the mbim interface that can share with me? like how did you gerenated the right antn and what AKA identifier you used in you verification. Now I use a AAA server to retrieve the autn. The AAA server also serves for the LTE network. so I believe it can generate the right autn. I’m not sure what kind of AKA identifier was used between the AAA server and the SIM card.IMSI or APN?