3GPP TSG-T WG2 SWG3#9
Paris, France
14th – 18th January 2002	T2M-010068 	

Agenda Item:	MM7

Source:	Nokia

Title:	MM7 Addressing

Document for:	Discussion

___________________________________________________________________________

During the discussions on MMS adhoc #9 CR to 23.140 Rel-5 MM7 (Functional Description and Abstract Messages for MM7 realization) was discussed.

It was decided to introduce new abstract messages between MMS Relay/Server and VASP to support functionalities between these two entities. Two most important abstract messages are MM7_Submit and MM7_Delivery (both includes Request and Response abstract messages).

Both abstract messages include several addresses, which some may be used only between MMS Relay/Server and VASP (in MM7 reference point) others may be used also in other reference points. Also some of the address may not be considered as addresses in MM7 reference point but are treated as an addresses in this discussion document. Some addresses may be used in transport layer.

MM7 Address mapping

During the meeting some offline discussion appeared. The following chapters describe different addresses used in different abstract messages and how addresses should be mapped to addresses in other reference points.

MM7_Submit

MM7_Submit.REQ (VASP => MMS Relay/Server) contains the following addressing related fields:
•	VASP ID
•	VAS ID
•	Sender Address
•	Recipient Address

The mapping of addressing fields between MM7 and other reference points (MM1 and MM4) should be the following: 
•	MM7_Recipient_address is transferred to “to:” address (in MM1_retrieve.RES “Recipient address”)
•	If MM7_Sender_address exists it is transferred to “from:” address (in MM1_retrieve.RES “sender address”)
•	If MM7_Sender_address does not exist MMS Relay/Server is responsible to define “from:” address (in MM1_retrieve.RES “sender address”) based on VASP ID and/or VAS ID

VASP ID and VAS ID are only used in reference point MM7 and there are no direct mapping to any addresses used in different reference points. 

MM7_Delivery

MM7_Delivery.REQ (MMS Relay/Server => VASP) contains the following addressing related fields:
•	MMS Relay/Server ID
•	VAS Address
•	Sender Address
•	Recipient Address

The mapping of addressing fields between other reference points (MM1 and MM4) and MM7 should be the following: 
•	Recipient address (to)(in MM1_submit.REQ “Recipient address”) is transferred to MM7_Recipient_address or/and MM7_VAS_Address
•	Recipient address (to)(in MM1_submit.REQ “Recipient address”) is mapped by the MMS Relay/Server to MM7_VAS_Address
•	Originator address (from)(in MM1_submit.REQ “Sender address”) is transferred to MM7_Sender_address

MMS Relay/Server ID is only used in reference point MM7 and there are no direct mapping to any addresses used in different reference points.

MM7 Address formats

Different addressing related fields may contain different type of addresses:

In MM7_Submit.REQ:
•	VASP ID – IP-address of VASP or URL of VASP
•	VAS ID – specific name or number of the service, e.g. string or short code
•	Sender Address – same address formats as used in MM1
•	Recipient Address – same address formats as used in MM1, usually MSISDN

In MM7_Delivery.REQ:
•	MMS Relay/Server ID – IP address of MMS R/S or URL of MMS R/S
•	VAS Address – same address formats as used in MM1 or specific name of service, e.g. string or short code
•	Sender Address – same address formats as used in MM1, always MSISDN
•	Recipient Address – same address formats as used in MM1

Conclusion

Some of the MM7 fields described this document shall be mapped to the fields in other reference points. However some of the fields may not be considered as an addressing field e.g. VASP ID. However, Nokia believe it is important to understand the usage of all the fields described in this document. This helps also to define Stage 3 for MM7. Nokia believes that some fields should be directly mapped to the transport level (HTTP) and not to transfer those in application level.

If this proposal is generally approved, corresponding changes shall be proposed to TS 23.140 v 5.1.0 based on guidelines described in this document.