5-30). BIR/BIA (in GAA); 5-31). GPR/GPA (in GBA Push); 5-32). MPR/MPA (for MMS);
1). GAA = Generic Authentication Architecture (via Zn)
§ GAA application: is an application that uses the security association created by GBA Bootstrapping procedure.
§ The network architecture of the GAA applications procedure using Zn
§ GAA: UE --- (Ua) --- NAF --- (Zn) --- BSF
§ GBA Push: UE --- (Upa) --- NAF --- (Zpn) --- BSF
§ Two options of Zn protocol: DIAMETER based Zn interface or Web Services (via SOAP/WSDL Message) based Zn interface
§ The requirements for Zn interface are defined in 3GPP TS 33.220.
§ The requirements for Zpn interface are defined in 3GPP TS 33.223
§ The protocol Zn retrieves the key material and possibly user security settings data by NAF from BSF. After UE is authenticated with the BSF, every time the UE wants to interact with an NAF
2). GBA = Generic Bootstrapping Architecture via Zh (to HSS)
§ GBA: UE --- (Ub) --- BSF --- (Zh) --- HSS
§ GBA Push: UE --- (Upa) --- NAF --- (Zpn) --- BSF --- (Zh) --- HSS
§ The Bootstrapping Zh interface performs the retrieval of an authentication vector and possibly GBA User Security Settings from the HSS
§ The network architecture of GBA push procedure using Zpn
§ A NAF sends a bootstrapping push request to the BSF via Zpn interface including the IMPI or IMPU of the user
The BSF starts protocol Zh with user’s HSS (via MAR)
§ The BSF requests user’s authentication vector and GBA User Security Settings (GUSS) corresponding to the IMPI or IMPU.
§ The HSS supplies to the BSF the requested authentication vector and GUSS (if any)
5.30). (310) Bootstrapping-Info-Request / Answer (BIR and BIA) in GAA:
§ (Zn for GAA) BIR/BIA between NAF and BSF
§ The protocol Zn retrieves the key material and possibly user security settings data by NAF from BSF. After UE is authenticated with the BSF, every time the UE wants to interact with an NAF
§ The NAF shall send a Bootstrapping-Info-Request message (BIR) to the BSF.
Message Flow: (N/A)
§ Diameter based GAA (Zn) application procedure (via Diameter BIR)
§ Web Services based GAA (Zn) application procedure (via WSDL BIR)
5.31). (312) GBA-Push-Info-Request / Answer (GPR and GPA) in GBA Push:
§ The NAF shall send a GBA-Push-Info-Request (GPR) message to the BSF.
§ (Zh for GBA) MAR/MAA between BSF and HSS
§ The BSF shall send a MA-Request (MAR) message to the HSS.
§ The Bootstrapping Zh interface performs the retrieval of an authentication vector and possibly GBA User Security Settings from the HSS
Message Flow: (N/A)
§ Diameter based GBA (Zh) push (Zpn) procedure over Zpn (via Diameter GPR)
§ Web Services based GBA (Zh) Push (Zpn) application procedure (via WSDL GPR)
§ GBA (Zh) bootstrapping procedure (via Diameter MAR)
§ GBA (Zh) Push (Zpn) bootstrapping procedure (via Diameter MAR)
5.32. (311) Message-Process-Request (MPR and MPA) in MM10:
MM10: MPR/MPA between MMS Relay/Server and MSCF
§ The Message-Process-Request (MPR) command is sent by a Diameter client (MMS Relay/Server) to a Diameter server (MSCF) in order to request the processing of a multimedia message.
§ The command codes for the MM10 interface application are taken from the range allocated by IANA as assigned in this specification. For these commands, the Application-ID field shall be set to 16777226
§ The vendor identifier value of 3GPP (10415) shall be included
§ The MMS Relay/Server and MSCF shall advertise support of the Diameter MM10 interface Application by including the value of the application identifier
§ Diameter sessions are implicitly terminated between the MMS Relay/Server and the MSCF. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server.
§ Diameter messages over the MM10 interface shall make use of SCTP IETF RFC 2960 and shall utilise the new SCTP checksum method specified in RFC 3309
§ The MMS Relay/Server shall derive the address/name of the MSCF for a certain user or use case from the MMS user profile or from the MMS Relay/Server configuration.
§ The MMS Relay/Server shall present both the Destination-Realm and Destination-Host AVPs in the request.
§ Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the MMS Relay/Server.
The multimedia message in Diameter application that allows a Diameter client and a Diameter server:
§ to indicate that a submission or delivery request for a multimedia message has been received. The Diameter client provides the message data and additional data qualifying the messaging event to the server.
§ to request in result to continue the processing of the multimedia message with the original or modified information or to reject the multimedia message.
§ MM10 Interrogation Procedure (via MPR)
§ This procedure is used between the MMS Relay/Server and the MSCF.
§ This procedure is invoked by the MMS Relay/Server and is used to request processing of addressing information related to a multimedia message (see 3GPP TS 23.140).
沒有留言:
張貼留言