Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 23.282  Word version:  19.3.0

Top   Top   Up   Prev   Next
1…   5…   6…   6.6…   7…   7.4…   7.4.2.1.10…   7.4.2.2…   7.4.2.5…   7.4.2.8…   7.4.3…   7.5…   7.5.2.1.12…   7.5.2.2…   7.5.2.4…   7.5.2.6…   7.5.2.8…   7.5.2.11…   7.5.2.14…   7.5.3…   7.6   7.7…   7.7.2.1.13…   7.7.2.2…   7.8…   7.9…   7.13…   7.13.3.1.19…   7.13.3.2…   7.13.3.8…   7.13.3.16…   7.13.4…   7.14…   7.14.2.2…   7.17…   7.17.2.13…   7.17.3…   7.17.3.1.4…   7.17.3.2…   7.17.3.2.4…   7.17.3.2.6…   7.17.4…   7.17.6…   7.17.7…   A…   B… 
7.14 IP connectivity  7.14.1 General  7.14.2 IP connectivity for on-network  7.14.2.1 Information flows for IP connectivity  7.14.2.1.1 MCData IPcon point-to-point request  7.14.2.1.2 MCData IPcon point-to-point response  7.14.2.1.3 MCData remote IPcon point-to-point request  7.14.2.1.4 MCData remote IPcon point-to-point response  7.14.2.1.5 MCData remote IPcon point-to-point tear down request  7.14.2.1.6 MCData remote IPcon point-to-point tear down response  7.14.2.1.7 MCData remote IPcon point-to-point application priority change request  7.14.2.1.8 MCData remote IPcon point-to-point application priority change response 
...

 

7.14  IP connectivity |R16|  p. 205

7.14.1  General  p. 205

IP data shall be exchanged between two or more data hosts. The MCData client as the link between data host and MC system enables the exchange of IP Data. For addressing the corresponding MCData users either MCData ID or the functional alias can be used independently of each other. The MCData server provides the mechanisms to establish the association between MCData ID and corresponding functional alias.

7.14.2  IP connectivity for on-network  p. 206

7.14.2.1  Information flows for IP connectivity  p. 206

7.14.2.1.1  MCData IPcon point-to-point request  p. 206
Table 7.14.2.1.1-1 describes the information flow of the MCData IPcon point-to-point request sent from the MCData client to the MCData server.
Information Element Status Description
MCData IDMThe MCData identity of the originator MCData user;
Functional aliasOThe associated functional alias of the originator MCData user;
SDP offerMOffered media parameters describing the requested characteristics of the IP tunnel between the MCData UEs.
MCData IDO (NOTE 2)The MCData identity of the target MCData client IP connectivity is requested.
Functional aliasO (NOTE 2)The functional alias of the target MCData client.
Requested Priority (NOTE 3)OApplication priority level requested for this communication.
Location InformationO (NOTE 1)Actual location information of the originating MCData user;
Time LimitOProposed time limit of the requested IP connectivity (1min- infinite);
Establishment reasonOIP connectivity establishment reason
NOTE 1:
This information contains the latest available location information of the requesting MCData user that may be different to the latest available location information in the MC system.
NOTE 2:
At least one identity shall be present. If both are present the MCData ID shall be used to route the request and the functional alias is just for information.
NOTE 3:
The predefined priority of the MC service user is applied by the MCData server if the requested priority is not present or not accepted by the MCData server.
Information Element Status Description
MCData IDMThe MCData identity of the originator MCData user;
MCData IDMThe MCData identity of the target MCData client IP connectivity is requested.
SDP offerMOffered media parameters describing the requested characteristics of the IP tunnel between the MCData UEs.
Location InformationO (NOTE 1)Actual location information of the originating MCData user;
Time LimitOProposed time limit of the requested IP connectivity (1min- infinite);
Establishment reasonOIP connectivity establishment reason
NOTE:
This information contains the latest available location information of the requesting MCData user.
Up
7.14.2.1.2  MCData IPcon point-to-point response  p. 206
Table 7.14.2.1.2-1 describes the information content of the MCData IPcon point-to-point response as answer to MCData IPcon point-to-point request.
Information Element Status Description
MCData IDMThe MCData identity of the targeted MCData user.
MCData IDMThe MCData identity of the requesting MCData user.
SDPOMedia parameters selected. This shall be present if the IP connectivity establishment result is successful.
Time LimitONegotiated time (1 min - infinite)
IP connectivity statusMIP connectivity establishment result
Up
7.14.2.1.3  MCData remote IPcon point-to-point request |R17|  p. 207
Table 7.14.2.1.3-1 describes the information flow of the MCData remote IPcon point-to-point request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Information Element Status Description
MCData ID remoteMThe MCData identity of the remote MCData client that requests another MCData user to establish an IP connectivity point-to-point session.
Functional alias remoteOThe associated functional alias of the remote MCData user.
MCData ID askedMThe MCData identity of the MCData client that is required to establish an IP connectivity point-to-point session.
Functional alias askedOThe functional alias associated with the MCData identity of the MCData client that is required to establish an IP connectivity point-to-point session.
MCData ID targeted (NOTE 1)OThe MCData identity of the MCData client that is the target of the requested IP connectivity point-to-point session.
Functional alias targeted (NOTE 1)OThe functional alias associated with the MC MCData identity of the MCData client that is the target of the requested IP connectivity point-to-point session.
Requested Priority (NOTE 2)OApplication priority level requested for this call.
Time LimitOProposed time limit of the requested IP connectivity (1min- infinite).
Establishment reasonOIP connectivity establishment reason
NOTE 1:
At least one identity shall be present. If both are present the MCData ID shall be used to route the request and the functional alias is just for information.
NOTE 2:
The predefined priority of the MC service user is applied by the MCData server if the requested priority is not present or not accepted by the MCData server.
Up
7.14.2.1.4  MCData remote IPcon point-to-point response |R17|  p. 207
Table 7.14.2.1.4-1 describes the information content of the MCData remote IPcon point-to-point response as answer to MCData remote IPcon point-to-point request.
Information Element Status Description
MCData ID askedMThe MCData identity of the asked MCData client in the request message;
MCData ID targetedMThe MCData identity of the targeted MCData client in the request message;
IP connectivity statusMThe status information about the IP connectivity session to the remote MCData user.
Up
7.14.2.1.5  MCData remote IPcon point-to-point tear down request |R17|  p. 208
Table 7.14.2.1.5-1 describes the information flow of the MCData remote IPcon point-to-point tear down request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Information Element Status Description
MCData ID remoteMThe MCData identity of the remote MCData client that requests another MCData user to tear down an IP connectivity point-to-point session.
Functional alias remoteOThe associated functional alias of the remote MCData user;
MCData ID askedMThe MCData identity of the MCData client that is asked to tear down an IP connectivity point-to-point session.
MCData ID targetedMThe MCData identity of the MCData client that is the target to be tear down from the IP connectivity point-to-point session.
Up
7.14.2.1.6  MCData remote IPcon point-to-point tear down response |R17|  p. 208
Table 7.14.2.1.6-1 describes the information content of the MCData remote IPcon point-to-point tear down response as answer to MCData remote IPcon point-to-point tear down request.
Information Element Status Description
MCData ID askedMThe MCData identity of the asked MCData client in the request message.
MCData ID targetedMThe MCData identity of the targeted MCData client in the request message.
Tear down statusMThe status information about the IP connectivity tear down status information
Up
7.14.2.1.7  MCData remote IPcon point-to-point application priority change request |R17|  p. 208
Table 7.14.2.1.7-1 describes the information flow of the MCData remote IPcon point-to-point application priority change request sent from the remote MCData client to the MCData server and from the MCData server to the asked MCData client.
Information Element Status Description
MCData ID remoteMThe MCData identity of the remote MCData client that requests to change the application priority of an IP connectivity point-to-point session.
Functional alias remoteOThe associated functional alias of the remote MCData user;
MCData IDMThe first MCData identity of the MCData client that is involved in the IP connectivity point-to-point session.
MCData IDMThe second MCData identity of the MCData client that is involved in the IP connectivity point-to-point session.
Requested PriorityMContains the required application priority for the IP data communication between both MCData clients.
Up
7.14.2.1.8  MCData remote IPcon point-to-point application priority change response |R17|  p. 209
Table 7.14.2.1.8-1 describes the information content of the MCData remote IPcon point-to-point application priority change response as answer to MCData remote IPcon point-to-point application priority change request.
Information Element Status Description
MCData IDMThe MCData identity of the first MCData client involved in the IP connectivity point-to-point session.
MCData IDMThe MCData identity of the second MCData client involved in the IP connectivity point-to-point session.
Requested priority change statusMThe status information about the application priority of the addressed IP connectivity session.
Up

Up   Top   ToC