Cause indicates the reason why the PDP context could not be established:. The actions taken depend on the cause of the delivery failure. The Protection procedure is illustrated in Figure The Mobile User Activity procedure is illustrated in Figure Only dynamic PDP addressing is applicable. The MS shall use Access Point Name to select a reference point to a certain external network that provides anonymous services. Selection Mode indicates how the APN was selected.
The following parameters can be modified:. Charging agreements Authentication and accounting message flows IP PDP type Accounting Update Annex A informative Annex B informative Change history The present document describes the network interworking for the Packet Domain. Interworking to various external networks is defined together with the interworking for data forwarding while subscribers roam within the 3GPP system.
The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:. The present document defines the requirements for Packet Domain interworking between a:. The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
In the case of a reference to a 3GPP document including a GSM document , a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. Calhoun, C. Aboba and M. Estrin, D. Farinacci, A. Helmy, D.
Thaler, S. Deering, M. Handley, V. Jacobson, C. Liu, P. Sharma, L. Waitzman, C. Partridge, S. Solomon, S. Rigney, S. Willens, A. Rubens, W. Rigney, Livingston. Chiba, M. Eklund, D. Mitton, B. Narten, E. Nordmark , W. Droms, W. Droms, J. Bound, B. Volz, T. Lemon, C. Perkins, M. Deering , W. Fenner, B. Deering, R. Adoba, G. Zorn, D.
Iu mode: indicates that the text applies only to a system or a sub-system which operates in Iu mode of operation, i. For the purposes of the present document, the following additional abbreviations apply:.
BG Border Gateway. IP Internet Protocol. IPv4 Internet Protocol version 4. IPv6 Internet Protocol version 6. MS Mobile Station. MT Mobile Terminal. PS Packet Switched. TE Terminal Equipment. For the purposes of the present document, the following symbols apply:. Gi Reference point between Packet Domain and an external packet data network.
Iu Interface between the RNS and the core network. It is also considered as a reference point. Typically this reference point supports a standard serial interface. Uu Interface between the mobile station MS and the fixed network part in Iu mode. The Uu interface is the Iu mode network interface for providing packet data services over the radio to the MS.
The Internet is a conglomeration of networks utilising a common set of protocols. The networks topologies may be based on LANs e. Service interworking is required when the Teleservice at the calling and called terminals are different. For Packet Domain, service interworking is not applicable at the Gi reference point.
Network interworking is required whenever a PLMN is involved in communications with another network to provide end-to-end communications. Interworking appears exactly like that of Packet Data Networks. The GGSN implicitly checks its internal context related to the destination address for each mobile terminated packet. If there is a context associated with the PDP address the packet shall be forwarded to the MS, otherwise the packet shall be discarded or rejected depending on the implemented protocol.
Screening may be applicable for only certain protocols. Screening is outside the scope of the present document. These interworked networks may be either intranets or the Internet. The interworking point with IP networks is at the Gi reference point as shown in figure 7. In this case the Packet Domain network will look like any other IP network or subnetwork. Typically in the IP networks, the interworking with subnetworks is done via IP routers.
The L2 and L1 layers are operator specific. It is out of the scope of the present document to standardise the router functions and the used protocols in the Gi reference point.
In this case the Packet Domain, i. The mechanisms for host configuration and user authentication described in this subclause and its subclauses are only applicable to the activation of the first context activated for a specific PDP address using the 'PDP Context Activation Procedure'.
The address or IPv6 Prefix is given either at subscription in which case it is a static address or at PDP context activation in which case it is a dynamic address. These procedures are as described in the IPv6 non-transparent access case except that the addresses belong to the operator addressing space. The use of stateful or stateless is configured per APN. The transparent case provides at least a basic ISP service.
As a consequence of this it may therefore provide a bearer service for a tunnel to a private Intranet. NB The remainder of this subclause deals with this specific case. The communication between the PLMN and the Intranet may be performed over any network, even an insecure network e.
There is no specific security protocol between GGSN and the Intranet because security is ensured on an end to end basis between MS and the intranet by the "Intranet Protocol". User authentication and encryption of user data are done within the "Intranet Protocol" if either of them is needed. This "Intranet Protocol" may also carry private IP addresses belonging to the address space of the Intranet. If IPsec is used for this purpose then IPsec authentication header or security header may be used for user data authentication and for the confidentiality of user data see RFC [62] and RFC [63].
In this case private IP tunnelling within public IP takes place. The address is given either at subscription in which case it is a static address or at PDP context activation in which case it is a dynamic address.
The following description bullet items describe the signal flow. The MT responds with an AT-response. The MT stores the necessary authentication data and sends a forced positive acknowledgement of the authentication to the TE.
As an example the GGSN may use one of the following options:. The MT sends either the configuration-ack packet e. In the case where a configure-nack packet was sent by the MT, a local negotiation may take place at the R reference point i.
The first signalling phase is done in the control plane and consists of the PDP context activation, followed by a second signalling phase done in the user plane. The user plane signalling phase shall be either stateless or stateful.
Stateful and Stateless Autoconfiguration may also co-exist. In that case, the MS shall use Stateless to configure the address and Stateful to configure additional parameters only. A dynamic IPv6 address shall be given using either stateless or stateful address autoconfiguration. The GGSN ensures the uniqueness of this interface-identifier. This is valid for both stateless and stateful address autoconfiguration. If a list of servers is received, the MS shall adhere to the explicit prioritisation order of the list.
In the following signalling flow example, PPP is used as layer 2 protocol over the R reference point. The Interface-Identifier shall be used in the TE to create a link-local address to be able to perform the IPv6 address autoconfiguration see subclauses The cause value shall be set according to the outcome of the host authentication and configuration.
Figure 11ba is valid for both Stateless and Stateful Address Autoconfiguration case. In the Stateful case though, option 2 does not apply and option 1 may only be used for authentication. The use of DHCPv6 above is different and used in a different context than when used for Stateful Address Autoconfiguration as in subclause The MS may select any value for the Interface-Identifier part of the address.
The procedure is consistent with RFC [29]. The procedure below takes place through signalling in the user plane. The MS may issue a Router Solicitation directly after the user plane establishment. An MS shall not perform stateless and stateful address autoconfiguration simultaneously, since multiple prefixes are not allowed in GPRS. The O-flag may be set though, since it does not result in additional addresses being acquired see below.
The Prefix is contained in the Prefix Information Option of the Router Advertisements and shall have the A-flag set "Autonomous address configuration flag" and the L-flag cleared i.
The lifetime of the prefix shall be set to infinity. There shall be exactly one Prefix included in the Router Advertisements. The randomisation part to determine when Router Advertisements shall be sent may be omitted since the GGSN is the only router on the link. These relate to the periodicity of the Router Advertisements initially and during continued operation. The motivation for this is to have a faster user-plane set-up even in bad radio conditions and to minimize MS power consumption during long continued operation.
Interface-Identifiers shall in any case be bit long. If the MS finds more than one Prefix in the Router Advertisement message, it shall only consider the first one and silently discard the others.
See subclause This shall be consistent with what is specified in RFC [44]. RFC [44] specifies a set of conceptual router configuration variables. Some of these variables require particular attention in GPRS in order to preserve radio resources and MS power consumption while still allowing for appropriate robustness and fast user-plane set-up time even in bad radio conditions, or simply because they have a particular meaning in GPRS.
The content provider makes an arrangement to reimburse the mobile operator by paying them directly, doing a revenue-sharing deal, or some other business arrangement. Personal Hotspot — Some mobile operators charge different rates when the connection is being used as a personal hotspot.
You can use multiple PDP contexts to differentiate between the two. For more information, see Developing apps using multiple PDP contexts. See Steps for installing HLK. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
0コメント