MIPv4 Security Context Derivation via Access Point Name

The patent segments the security association structure by introducing separate security contexts for each PDN connection. Instead of using a single security association for all connections, the system creates distinct security contexts (EPS security context and MIPv4 security context) for each PDN, ensuring that security parameters are uniquely derived per connection while maintaining overall system security consistency.

The patent applies local quality by deriving security parameters locally for each specific PDN connection using the APN as a unique identifier. The MIPv4 security context is locally derived from the EPS security context using connection-specific parameters (APN, IP address), ensuring that each PDN connection has customized security parameters tailored to its specific requirements rather than using generic shared parameters.

The patent introduces an intermediary mechanism where the 3GPP AAA server acts as a mediator between non-3GPP access networks and the MIPv4 protocol. The AAA server performs EAP authentication to establish an EPS security context, then derives MIPv4-specific security parameters from this context. This intermediary process allows non-3GPP networks to use standard MIPv4 while incorporating 3GPP-level security through the AAA server's key derivation and distribution functions.

The patent changes security parameters by transforming the EPS security context into MIPv4-specific security parameters through a derivation process. The system changes the parameter representation from generic EPS security parameters to MIPv4-specific parameters (MIPv4 keys, SPI, authentication extensions) while maintaining the cryptographic strength of the original EPS security context. This parameter transformation enables compatibility with MIPv4 infrastructure while preserving 3GPP security requirements.