OA17643A - Methods for providing a PLMN identifier of a packet data network gateway to a node of a RAN. - Google Patents

Abstract

A method in a communication system includes a first core network node (CN), a second CN, a base station apparatus serving a user equipment (UE), and a packet data network gateway (PGW) associated with the UE, the method being performed by the first CN. The method includes the first CN receiving a tunneling endpoint identifier (TEID) information element from a second CN, the TEID information element comprises a plurality of fields. The one of the plutalityof fields includes a public Land Mobile Network (PLMN).

Description

CROSS REFERENCE TO RELATED APPLICATION(S)

This application claims the benefit of U.S. Provisional Application No. 61/827,343, filed May 24, 2013. The disclosure of the referenced application is incorporated herein in its entirety by reference.

TECHNICAL FIELD

This disclosure relates to providing a PLMN identifier to a node of a radio access network (RAN).

BACKGROUND

A RAN can improve its management of radio resources by knowing services currently being used by wireless communication devices (referred to herein as “user equipment (UE)”) that are served by the RAN. In 3GPP, such a function is called SIRIG (which stands for Service identification for improved radio utilization for GERAN), where the service identification is provided to the RAN (e.g., provided to a base station of the RAN or a radio network controlling in the RAN) by a core network node (CN) comprising a Mobility Management Entity (MME) or a serving GPRS support node (SGSN).

While SIRIG is currently only defined for GERANs (GSM EDGE Radio Access Networks), SIRIG can be extended to other radio access technologies (RATs), e.g., universal mobile télécommunications system (UMTS), long term évolution (LTE), etc.

SUMMARY

According to an aspect of the présent invention, a method in a communication System includes a first core network node (CN), a second CN, a base station apparatus serving a user equipment (UE), and a packet data network gateway (PGW) associated with the UE, the method being performed by the first CN. The method includes the first CN receiving a tunneling endpoint identifier (TEID) information element form a second CN, the TEID information element comprises a plurality of fields. The one of the plurality of fields includes a Public Land Mobile Network (PLMN) identifier of the PGW. The method further includes the first CN forwarding the received PLMN identifier to the base station apparatus.

According to another aspect ofthe présent invention, a method in a communication system includes an SGSN, a base station serving a user equipment (UE), an RNC controlling the base station, and a packet data network gateway (PGW) associated with the UE, the method being performed by the SGSN. The method includes the SGSN obtaining a PLMN identifier (ID) of the PGW. The method further includes the SGSN transmitting the PLMN ID to the RNC.

According to another aspect ofthe présent invention, a method in a communication system includes a first core network node (CN), a base station apparatus serving a user equipment (UE), and a packet data network gateway (PGW) associated with the UE, the method being performed by the first CN. The method includes the first CN obtaining a PLMN identifier of the PGW. The method further includes the first CN transmitting a message to the base station apparatus. The message includes: (i) an information element containing the PLMN ID ofthe PGW; and (ii) a radio access bearer (RAB) identifier information element including data identifying a RAB.

According to another aspect ofthe présent invention, a method in a communication System includes a first core network node (CN), a second CN, and a packet data network gateway (PGW) associated with user equipment (UE). The method is performed by the first CN and includes the first CN encoding a Public Land Mobile Network identifier (PLMN ID) ofthe PGW in a TEID/GRE Key field of a F-TEID information element. The method further includes the first CN transmitting the F-TEID information element containing the PLMN ID to the second CN.

The SIRIG function supports both roaming and network sharing scénarios. (See SP-120252 and SP-120483). The solution to support the roaming scénario is specified in section 5.3.5.3 in 3GPP TS 23.060 as follows:

“When the serving A/Gb mode SGSN receives SCI in a GTP-U packet, it copies it, without modifying its value, into a Gb interface information element that is sent by the SGSN in the downlink Gb interface user data packet to the GERAN access. In order to allow the GERAN to map the SCI into RRM behaviour, the downlink Gb interface user data packet also carries the HPLMN ID (in the IMSI parameter) and additional information, added by the SGSN, which indicates whether the SCI is assigned by a GGSN/P-GW in e.g. the Home PLMN or Visited PLMN. Absence of additional information is an indication of a VPLMN provided SCI

The A/Gb mode GERAN uses the information from the SGSN to détermine whether to map, and how to map, the SCI to the related RRM behaviour. If the GERAN is not configured with an SCI mapping for the SGSN provided information, then the GERAN shall treat the user plane packet normally, i.e. the GERAN ignores the SCI.

NOTE 4: When sending downlink GTP-U packets, there are some transient periods where the current RAT information for the user may be incorrect at the GGSN/P-GW e.g. after a handoverfrom (E)UTRAN to GERAN, or if the MS is in idle mode with ISR active, or if the MS is in idle mode and located in a Routing Area comprising GERAN and UTRAN cells. In these cases, the A/Gb mode GERAN may receive the first downlink user plane packets without Service Class Indicator.”

Thus, the BS based on the knowledge ofthe international mobile subscriber identity (IMSI) and the additional information indicating whether the subscriber controlled input (SCI) is assigned by a GGSN/P-GW (e.g., the Home PLMN orVisited PLMN) interprets the semantics of SCI and apply relevant radio resource management (RRM) behaviors. But, the above solution may hâve a problem when SIRIG function is extended to LTE and UMTS because the enodeB (eNB) has no knowledge of IMSI. Therefore the solution doesn’t work for LTE.

When Direct Tunnel is used in 3G or 4G is used, the payload path may be RNC/eNB -SGW PGW, which indicates that the SGW has to insert such “additional information indicating whether the SCI is assigned by a GGSN/P-GW in e.g. the Home PLMN or Visited PLMN.” When Direct Tunnel is not used, the payload path would be RNC - SGSN - SGW - PGW, which indicates that the SGSN has to insert such “additional information indicating whether the SCI is assigned by a GGSN/P-GW in e.g. the Home PLMN or Visited PLMN.”.

Because both RNC and eNB support the Bearer Service concept (where the UMTS bearer service is specified in 3GPP TS 23.107 and EPS bearer is specified in the section 4.7 in TS

23.401), the SGW or MME/SGSN can inform RNC or eNB about PLMN ofthe PGW (i.e., the

PLMN in which the PGW is located) for each bearer contexte within a given PDN connection.

The SGW or MME/SGSN can inform RNC/eNB about the PLMN ofthe PGW during, for example, RAB assignment procedure and SRNS relocation procedure in 3G (or during initial

UE context setup/E-RAB establishment and handover procedure in LTE). Both RNC and eNB hâve no PDN connection level concept but only bearer context within a PDN connection.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrâtes an example communication System 100 in which embodiments of this disclosure are implemented;

FIGS. 2-9 illustrâtes example flows in which embodiments of this disclosure are implemented; and

FIG. 10 illustrâtes an example block diagram of an example core network node.

DETAILED DESCRIPTION

This disclosure relates to providing a PLMN identifier to a node of a radio access network (RAN). In embodiments, the présent invention enables roaming support for SIRIG when it is used for UMTS and LTE. Thus, comparing with the existing solution, one or more embodiment are much more efficient as the PLMN information of the PGW is provided per bearer context, not per GTP-U packet, which reduces very much processing load in eNB 114, RNC 106, SGSN 108, SGW 118, as shown in FIG. 1. The disclosure also allows for transfer of information during handover procedures, useful for SIRIG solutions in UTRAN and E-UTRAN.

I, Embed PLMN identifier in the user plane address

Before user plane data can be transferred to the UE 128 (see FIG. 1), a user plane path, i.e., a bearer has to be established. The bearer establishment may happen during one or more of the following procedures: Initial attach (in E-UTRAN 112 in FIG. 1), TAU with Active flag, PDP Context Activation, RAU with Follow-on-request flag, SRNS relocation (RAB need to be established in the target RAN before UE is moving in), etc.

The SGW 118 (3G when DT is used or 4G for EPS), the SGSN 108 (when DT is not used in 3G), or the GGSN 110 (3G when DT is used but it is connected with Gn/Gp SGSN), will provide user plane transportation address (IP address + TEID = F-TEID) to the RAN via the MME 116/SGSN 108 (through S1-MME and lu interface).

For 3G and when direct tunnel is used (or for 4G), the SGW will provide SGW F-TEID(s) for the user plane for each bearer context. The F-TEID(s) will be forwarded by the SGSN 108 or the

MME 116 during RAB assignment procedure or during initial UE context setup/E-RAB establishment procedure to the RNC 106 or the eNB 114. Those SGW F-TEID(s) are used by

RNC 106 and eNB 114 to send any uplink user plane data. During SRNS relocation procedure in 3G or handover procedure in LTE, the target SGSN 108 or MME 116 provides the SGW 118 user plane F-TEID either received from the source MME 116/SGSN 108 (in case the SGW is not relocated) or from a new SGW (in case the SGW is relocated).

This disclosure proposes that the SGW 118 embed a PLMN identifier (PLMN ID) into the SGW F-TEID when it is sent to the MME 116/SGSN 108, where the embedded PLMN ID identifies the PLMN of the PGW 120 (i.e., the PLMN in which the PGW is located) associated with the UE 128. This is illustrated in FIG. 2, which shows the SGW 118 receiving a create session request message from an MME 116 (or SGSN 108) and then transmitting a create session response message to the MME 116/SGSN 108, which créâtes a session response message that includes an F-TEID information element that contains a field containing the PLMN ID.

F-TEID is an existing information element as specified in section 8.22 TS 29.274 as follows:

8.22 Fully Qualified TEID (F-TEID)

Fully Qualified Tunnel Endpoint Identifier (F-TEID) is coded as depicted in Figure 8.22-1.

Octets	Bits
8 7 6	5 4 3 2 1
1	Type = 87 (décimal)
2to 3	Length = n
4	Spare	| Instance
5	V4 | V6 |	Interface Type
6 to 9	TEID/GRE Key
m to (m+3)	IPv4 address
pto(p+15)	IPv6 address
k to (n+4)	These octet(s) is/are présent only if explicitly specified

Figure 8.22-1: Fully Qualified Tunnel Endpoint Identifier (F-TEID)

The Octets 6-9 (a.k.a., the TEID/GRE Key field) is encoded for TEID, where PLMN ID of the PGW 120 may be embedded according to an operator’s configuration. That is, the PLMN ID of the PGW 120 may be encoded in the TEID/GRE Key field of the F-TEID information element.

For 3G when direct tunnel is not used, the SGSN 108 will provide SGSN F-TEID to the RNC 106 during RAB assignment procedure (this is illustrated in FIG. 3). Accordingly, the SGSN 108 can embed PLMN information of the PGW 120 for a given PDN connection into SGSN F-TEID, as described above.

For legacy Gn/Gp SGSN interworking with a GGSN in another PLMN when direct tunnel is used, the GGSN may embed PLMN ID of the GGSN for a given PDP into GGSN TEID on the user plane, which will be forwarded by the Gn/Gp SGSN to the RNC 106 as described in FIG. 4. Stage 2 changes to current spécifications may be needed in order to describe that the TEID forwarded to

RNC 106 or eNB contains information about the HPLMN ID or VPLMN ID corresponding to the PGW 120 where the RAB is established.

When indirect data forwarding is used during handover/SRNS relocation procedure and when the SGW 118 selected as data forwarding is NOT the anchor SGW, the forwarding SGW has no knowledge of PLMN information of the PGW 120, thus those packets received via indirect tunneling may not associated with a PLMN information, hence they may not be correctly handled. This requires when setting up the indirect tunnel, the SGSN 108 /MME 116 shall either not use nonanchor SGW, or shall let the data forwarding SGW know about PLMN information of PGW 120. This implies a protocol change - to add PLMN information of the PGW 120 in the GTP message “Create Indirect Data Forwarding Tunnel Request message”, so when data forwarding SGW 118 allocates SGW F-TEID for data forwarding, it can embed such PLMN information of the PGW into the SGW F-TEID.

II. Provide PLMN ID during bearer establishment

It is also possible to provide the PLMN ID of the PGW 120 serving the UE 128 to the RNC 106 or eNB 114 during RAB assignment procedure and SRNS relocation procedure (for 3G) or Initial UE context setup / E-RAB establishment procedure and handover procedure (for 4G), by the SGSN 108 or MME 116.

The procedure for RAB assignment procedure for 3G is described in the section 12.7.4.1 of TS 23.060 RAB Assignment Procedure Using Gn/Gp and in the section 8.2.2 of TS 25.413 and illustrated in FIG. 5.

In the RAB Assignment Request message, a new IE, preferably called “PLMN of PGW/GGSN” is included, and associated with each RAB. Addition of the new PLMN of PGW/GGSN IE in the RAB Assignment Request message is shown in Table 1. FIG. 6 illustrate a core network node (CN) transmitting a message of type RAB assignment request to an RNC 106. The RAB assignment request message includes the PLMN ID of the PGW serving the UE that the RAB identified in the message is for.

An MME may provide to an eNB 114 the PLMN ID using a message of type Initial Context Setup Request, as shown in FIG. 7. Addition of the new PLMN of PGW/GGSN IE in the INITIAL COTEXT SETUP message is shown in Table 2.

An MME 116 may provide to an eNB 114 the PLMN ID using a message of type E-RAB Setup

Request, as shown in FIG. 8. Addition of the new PLMN of PGW 120/GGSN 110 IE in the E-RAB

SETUP REQUEST message is shown in Table 3. Once the PLMN of PGW 120/GGSN 110 has been transferred to the serving RAN according to the embodiment above, there is also the need to transfer such information during handover procedures across different base stations. This should be done both for UTRAN 102 and E-UTRAN 112 and both for network based handovers (i.e. S1 or RANAP handovers) or direct interface handovers such as X2 or lur handovers. The S1 handover procedure for E-UTRAN 112 is described in TS23.401 section 5.5.1.2.2 and it is shown in FIG. 9. In alternate embodiments, an équivalent procedure exists for UTRAN RANAP based handovers.

In addition, when indirect tunneling is applicable, the target RAN should apply the received PLMN ofthe PGW 120 via Handover Request and Relocation Request also to that associated data forwarding tunnel.

The new PLMN of PGW IE shall be added to the HNDOVER REQUEST message to communicate to the target RAN the PLMN ID of the PGW associated to the handed over RAB. An example of how such new IE could be included is shown in table 4. An équivalent modification can be applied to UTRAN 102 by adding the “PLMN of PGW/GGSN” IE by using a RANAP: RELOCATION REQUEST message.

In case of mobility for E-UTRAN 112 and UTRAN 102 not involving the CN (i.e., X2 or lur based mobility), the new information may be added to the respective mobility messages. For E-UTRAN 112 the X2 handover procedure is described in TS36.300 section 10.1.2.1.1. An équivalent procedure, SRNS relocation, exists for UTRAN over the lur interface.

For UTRAN 102, the new PLMN of PGW IE shall be added to the HANDOVER REQUIRED message to communicate to the target RAN the PLMN ID ofthe PGW 120 associated with the handed over RAB. An example of how such new IE could be included is shown in the Table 5: Example of inclusion of new “PLMN of PGW” IE in the X2: HANDOVER REQUIRED message (see TS36.423).

In the case of UTRAN 102, the new PLMN of PGW/GGSN IE shall be added in the RNSAP: Enhanced Relocation Request message and in particular in the RANAP Enhanced Relocation Information Required IE defined in TS25.413. An example of how this could be achieved is shown in Table 6: Example of inclusion of new “PLMN of PGW/GGSN” IE in the RANAP Enhanced Relocation Information IE included in the RNSAP: Enhanced Relocation Request message (see TS25.423).

The new information concerning the PLMN ID of the PGW 120/GGSN 110 associated to the RAB handed over may be sent for each RAB.

The information added to the messages and procedures above shall not be limited to the PLMN ID ofthe PGW 120/GGSN 110 to which the RAB is associated. Such information could include any indication that allows the RAN to understand the actions to be taken upon réception of SIRIG-like marking. For example, the information added could consist of an index pointing at a particular SIRIG policy, which allows the RAN to understand the RRM policy so as to apply packets with spécifie SIRIG marking.

III. Example network node

FIG. 10 illustrâtes a block diagram of an example core network node. As shown in FIG. 10, the core network node includes: a data processing system (DPS) 402, which may include one or more processors (P) 455 (e.g., microprocessors) and/or one or more circuits, such as an application spécifie integrated circuit (ASIC), Field-programmable gâte arrays (FPGAs), etc.; a network interface 403 for connecting the network node to a network 130; a data storage system 406, which may include one or more computer-readable data storage médiums, such as non-transitory memory unit (e.g., hard drive, flash memory, optical disk, etc.) and/or volatile storage apparatuses (e.g., dynamic random access memory (DRAM)).

In embodiments where data processing system 402 includes a processor 455 (e.g., a microprocessor), a computer program product 433 may be provided, which computer program product includes: computer readable program code 443 (e.g., instructions), which implements a computer program, stored on a computer readable medium 442 of data storage system 406, such as, but not limited, to magnetic media (e.g., a hard disk), optical media (e.g., a DVD), memory devices (e.g., random access memory), etc. In some embodiments, computer readable program code 443 is configured such that, when executed by data processing system 402, code 443 causes the data processing system 402 to perform steps described herein.

In some embodiments, network node is configured to perform steps described above without the need for code 443. For example, data processing system 402 may consist merely of specialized hardware, such as one or more application-specific integrated circuits (ASICs). Hence, the features ofthe présent invention described above may be implemented in hardware and/or software. For example, in some embodiments, the functional components of network node described above may be implemented by data processing system 402 executing program code 443, by data processing System 402 operating independent of any computer program code 443, or by any suitable combination of hardware and/or software.

While various aspects and embodiments ofthe présent disclosure hâve been described above, it should be understood that they hâve been presented by way of example only, and not limitation.

Thus, the breadth and scope of the présent disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination ofthe éléments described in this disclosure in ail possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

Additionally, while the processes described herein and illustrated in the drawings are shown as a sequence of steps, this was done solely for the sake of illustration. Accordingly, it is contemplated that some steps may be added, some steps may be omitted, the order of the steps may be rearranged, and some steps may be performed in parallel.

TABLES

Table 1 is an example table of inclusion of new “PLMN of PGW/GGSN” IE in a RAB ASSIGNMENT

REQUEST message (see TS25.413)). Table 2 is an example table of inclusion of new “PLMN of PGW/GGSN” IE in an INITIAL CONTEXT SETUP message (see TS36.413). Table 3 is an example table of inclusion of new “PLMN of PGW” IE in a E-RAB SETUP REQUEST message (see

TS36.413)). Table 4 is an example table of inclusion of new “PLMN of PGW” IE in the HANDOVER

REQUEST message (see TS36.413). Table 5 is an example table of inclusion of new “PLMN of

PGW” IE in the X2: HANDOVER REQUIRED message (see TS36.423). Table 6is an example table of inclusion of new “PLMN of PGW/GGSN” IE in the RANAP Enhanced Relocation Information IE included in the RNSAP: Enhanced Relocation Request message (see TS25.423).

Table 7 is an example table of RAB Assignment Request message with new IE for PLMN ID.

Table 8 is an example table indicating an Initial Context Setup Request message with new IE for

PLMN ID). Table 9 is an example table indicating an E-RAB SETUP REQUEST with new IE for PLMN ID.

TABLE 1
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	reject
RABs To Be Setup Or Modified List	0				YES	ignore
>RABs To Be Setup Or Modified Item IEs		1 to <maxnoofRABs>
»First Setup Or Modify Item	M			Grouping reason: same criticality.	EACH	reject
»>RAB ID	M		9.2.1.2	The same RAB ID must only be présent in one group.
»>NAS Synchronisation Indicator	O		9.2.3.18		-
»>PLMNof PGW/GGSN	O		9.2.3.33	The PLMN ID ofthe PGW/GGSN involved in the RAB assignment
»>RAB Parameters	O		9.2.1.3	Includes ali necessary parameters for RABs (both for MSC and SGSN) including QoS.
»>User Plane Information	o				-
»»User Plane Mode	M		9.2.1.18		-
»»UP Mode Versions	M		9.2.1.19		-
»>Transport Layer Information	O				-
»»Transport Layer Address	M		9.2.2.1		-
»»Iu Transport Association	M		9.2.2.2		-
»>Service Handover	0		9.2.1.41		-
»>E-UTRAN Service Handover	0		9.2.1.90		YES	Ignore
»>Correlation ID	0		9.2.2.5		-
»Second Setup Or Modify Item	M			Grouping reason: same criticality.	EACH	Ignore
»>PDP Type Information	0		9.2.1.40		-
»>Data Volume Reporting Indication	0		9.2.1.17
»>DLGTP-PDU Sequence Number	0		9.2.2.3		-
»>ULGTP-PDU Sequence Number	0		9.2.2.4		-
»>DL N-PDU Sequence Number	o		9.2.1.33		-
»>UL N-PDU Sequence Number	0		9.2.1.34		-
»> Alternative RAB Parameter Values	o		9.2.1.43		YES	Ignore
»>GERAN BSC Container	0		9.2.1.58		YES	Ignore
>»PDP Type Information extension	0		9.2.1.40a	The PDP Type Information extension IE can only be included if PDP Type Information IE	YES	Ignore

				is not présent.
»>OffloadRAB parameters	O		9.2.1.94	Applicable only for SIPTO at Iu-PS.	YES	Ignore
RABs To Be Released List	0				YES	Ignore
>RABs To Be Released Item IEs		1 to <maxnoofRABs>			EACH	Ignore
»RAB ID	M		9.2.1.2	The same RAB ID must only be présent in one group.
»Cause	M		9.2.1.4		-
UE Aggregate Maximum Bit Rate	O		9.2.1.91		YES	Ignore
MSISDN	O		9.2.1.95	Applicable only for SIPTO at Iu-PS.	YES	Ignore

TABLE 2
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	reject
MMEUES1APID	M		9.2.3.3		YES	reject
eNBUESlAPID	M		9.2.3.4		YES	reject
UE Aggregate Maximum Bit Rate	M		9.2.1.20		YES	reject
E-RAB to Be Setup List		1			YES	reject
>E-RAB to Be Setup Item IEs		1.. <maxnooJE- RABs>			EACH	reject
»E-RAB ID	M		9.2.1.2		-
»E-RAB Level QoS Parameters	M		9.2.1.15	Includes necessary QoS parameters.
»Transport Layer Address	M		9.2.2.1		-
»GTP-TEID	M		9.2.2.2		-
»NAS-PDU	0		9.2.3.5		-
»Correlation ID	0		9.2.1.80		YES	ignore
»PLMN of PGW	O		9.2.3.8	The PLMN ID of the PGW/GGSN involved in the RAB assignaient

TABLE 2
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
UE Security Capabilities	M		9.2.1.40		YES	reject
Security Key	M		9.2.1.41	TheKeNB is provided after the key-generation in the MME, see TS 33.401 [15],	YES	reject
Trace Activation	O		9.2.1.4		YES	ignore
Handover Restriction List	O		9.2.1.22		YES	ignore
UE Radio Capability	0		9.2.1.27		YES	ignore
Subscriber Profile ID for RAT/Frequency priority	0		9.2.1.39		YES	ignore
CS Fallback Indicator	o		9.2.3.21		YES	reject
SRVCC Operation Possible	0		9.2.1.58		YES	ignore
CSG Membership Status	0		9.2.1.73		YES	ignore
Registered LAI	0		9.2.3.1		YES	ignore
GUMMEI	0		9.2.3.9	This IE indicates the MME serving the UE.	YES	ignore
MME UE SI AP ID2	0		9.2.3.3	This IE indicates the MME UE SI AP ID assigned by the MME.	YES	ignore
Management Based MDT Allowed	0		9.2.1.83		YES	ignore
Management Based MDT PLMN List	0		MDT PLMN List 9.2.1.89		YES	ignore

TABLE 3
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	reject
MME UE SI AP ID	M		9.2.3.3		YES	reject
eNBUESlAPID	M		9.2.3.4		YES	reject
UE Aggregate Maximum Bit Rate	O		9.2.1.20		YES	reject
E-RAB to be Setup List		1			YES	reject
>E-RAB To Be Setup Item IEs		1.. <tnaxnoofERABs>			EACH	reject
»E-RAB ID	M		9.2.1.2		-
»E-RAB Level QoS Parameters	M		9.2.1.15	Includes necessary QoS parameters.
»Transport Layer Address	M		9.2.2.1		-
»GTP-TEID	M		9.2.2.2	EPC TEID.	-
»NAS-PDU	M		9.2.3.5		-
»Correlation ID	O		9.2.1.80		YES	ignore
»PLMNofPGW	0		9.2.3.8	ThePLMN ID ofthe PGW/GGSN involved in the RAB assignment

TABLE 4
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	reject
MMEUES1APID	M		9.2.3.3		YES	reject
Handover Type	M		9.2.1.13		YES	reject
Cause	M		9.2.1.3		YES	ignore
UE Aggregate Maximum Bit Rate	M		9.2.1.20		YES	reject
E-RABs To Be Setup List		1			YES	reject
>E-RABs To Be Setup Item IEs		1.. <maxnoofERABs>			EACH	reject
»E-RAB ID	M		9.2.1.2		-
»Transport Layer Address	M		9.2.2.1		-
»GTP-TEID	M		9.2.2.2	To deliver UL PDUs.	-
»E-RAB Level QoS Parameters	M		9.2.1.15	Includes necessary QoS parameters.
»Data Forwarding Not Possible	0		9.2.1.76		YES	ignore
»PLMN of PGW	0		9.2.3.8	The PLMN IDof the PGW/GGSN involved in the RAB assignment
Source to Target Transparent Container	M		9.2.1.56		YES	reject
UE Security Capabilities	M		9.2.1.40		YES	reject
Handover Restriction List	O		9.2.1.22		YES	ignore
Trace Activation	0		9.2.1.4		YES	ignore
Request Type	O		9.2.1.34		YES	ignore
SRVCC Operation Possible	o		9.2.1.58		YES	ignore
Security Context	M		9.2.1.26		YES	reject
NAS Security Parameters to EUTRAN	cifiromUTRANGERAN		9.2.3.31	The eNB shall use this IE as specified in TS 33.401 [15],	YES	reject
CSG Id	O		9.2.1.62		YES	reject
CSG Membership Status	O		9.2.1.73		YES	ignore
GUMMEl	O		9.2.3.9	This IE indicates the MME serving the UE.	YES	ignore
MME UES1APID2	0		9.2.3.3	This IE indicates the MME UES1APID assigned by the MME.	YES	ignore
Management Based MDT Allowed	O		9.2.1.83		YES	ignore
Management Based MDT PLMN List	0		MDT PLMN List 9.2.1.89		YES	ignore

TABLE 5
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.13		YES	reject
Old eNB UE X2AP ID	M		eNB UE X2AP ID 9.2.24	Allocated at the source eNB	YES	reject
Cause	M		9.2.6		YES	ignore
Target Cell ID	M		ECGI 9.2.14		YES	reject
GUMMEI	M		9.2.16		YES	reject
UE Context Information		1			YES	reject
>MME UES1APID	M		INTEGER (O..232-l)	MMEUES1APID allocated at the MME
>UE Security Capabilities	M		9.2.29		-	-
>AS Security Information	M		9.2.30		-	-
>UE Aggregate Maximum Bit Rate	M		9.2.12		—	—
>Subscriber Profile ID for RAT/Frequency priority	O		9.2.25		—	—
>E-RABs To Be Setup List		1			—	—
»E-RABs To Be Setup Item		1.. <maxnoof Bearers>			EACH	ignore
>»E-RAB ID	M		9.2.23		-	-
»>E-RAB Level QoS Parameters	M		9.2.9	Includes necessary QoS parameters	—	—
»>DL Forwarding	O		9.2.5		-	-
»>UL GTP Tunnel Endpoint	M		GTP Tunnel Endpoint 9.2.1	SGW endpoint of the SI transport bearer. For delivery of UL PDUs.
»PLMNofPGW	O		9.2.3.8	The PLMN ID of the PGW/GGSN involved in the RAB assignment
>RRC Context	M		OCTET STRING	Includes the RRC Handover Préparation Information message as defined in subclause 10.2.2 ofTS 36.331 [9]
>Handover Restriction List	0		9.2.3		-	-
>Location Reporting Information	O		9.2.21	Includes the necessary parameters for location reporting
>Management Based MDT Allowed	O		9.2.59		YES	ignore
>Management Based MDT PLMN List	0		MDT PLMN List 9.2.64		YES	ignore
UE History Information	M		9.2.38	Same définition as in TS 36.413 [4]	YES	ignore
Trace Activation	O		9.2.2		YES	ignore
SRVCC Operation Possible	0		9.2.33		YES	ignore
CSG Membership Status	o		9.2.52		YES	reject
Mobility Information	o		BIT STRING (SIZE (32))	Information related to the handover; the source eNB provides it in order to enable later	YES	ignore

analysis of the conditions that led to a wrong HO.

TABLE 6
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	ignore
Source RNC To Target RNC Transparent Container	M		9.2.1.28		YES	reject
Old lu Signalling Connection Identifier CS domain	O		9.2.1.38		YES	ignore
Global CN-ID CS domain	O		9.2.1.46		YES	reject
Old lu Signalling Connection Identifier PS domain	O		9.2.1.38		YES	ignore
Global CN-ID PS domain	o		9.2.1.46		YES	reject
RABs To Be Setup List	0				YES	reject
>RABs To Be Setup Item lEs		1 to <maxnoofRABs>			EACH	reject
»CN Domain Indicator	M		9.2.1.5		-
»RAB ID	M		9.2.1.2		-
»RAB Parameters	M		9.2.1.3		-
»Data Volume Reporting Indication	C-ifPS		9.2.1.17
»PDP Type Information	C-ifPS		9.2.1.40		-
»>PLMN of PGW/GGSN	0		9.2.3.33	The PLMN ID ofthe PGW/GGSN involved in the RAB assignment
»User Plane Information	M
»>User Plane Mode	M		9.2.1.18		-
»>UP Mode Versions	M		9.2.1.19		-
»Data Forwarding TNL Information	O
»>Transport Layer Address	M		9.2.2.1
»>Transport Association	M		iu Transport Association 9.2.2.2	Related to TLA above.
»Source Side lu UL TNL Information	O
»>Transport Layer Address	M		9.2.2.1
»>Iu Transport Association	M		9.2.2.2
»Service Handover	0		9.2.1.41
»Altemative RAB Parameter Values	O		9.2.1.43
»E-UTRAN Service Handover	0		9.2.1.90		YES	ignore
»PDP Type Information extension	o		9.2.1.40a	The P DP Type Information extension IE can only be included if P DP Type	YES	Ignore

				Information IE is présent.
SNA Access Information	O		9.2.3.24		YES	ignore
UESBI-Iu	0		9.2.1.59		YES	ignore
Selected PLMN Identity	O		9.2.3.33		YES	ignore
CNMBMS Linking Information	O				YES	ignore
>Joined MBMS Bearer Service IEs		1 to <maxnoofMulticastSemcesPerUE>			EACH	ignore
»TMGI	M		9.2.3.37		-
»PTP RAB ID	M		9.2.1.75		-
Integrity Protection Information	O		9.2.1.11	Integrity Protection Information includes key and permitted algorithms.	YES	ignore
Encryption Information	O		9.2.1.12	Integrity Protection Information includes key and permitted algorithms.	YES	ignore
UE Aggregate Maximum Bit Rate	O		9.2.1.91		YES	ignore
RAB Parameters List	o		9.2.1.102	Applicable only to RNSAP relocation.	YES	reject
CSGID	o		9.2.1.85	Applicable only to Enhanced Relocation fromRNC towards a hybrid cell and RNSAP relocation.	YES	reject
CSG Membership Status	o		9.2.1.92	Applicable only to Enhanced Relocation from RNC towards a hybrid cell and RNSAP relocation.	YES	reject
Anchor PLMN Identity	o		9.2.3.33	Indicates the PS core network operator in case of SRVCC (see TS 23.251 [39]).	YES	ignore

TABLE 7
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	reject
RABs To Be Setup Or Modified List	0				YES	ignore
>RABs To Be Setup Or Modified Item lEs		1 to <maxnoofRABs>
»First Setup Or Modify Item	M			Grouping reason: same criticality	EACH	reject
>»RAB ID	M		9.2.1.2	The same RAB ID must only be présent in one group·
»>NAS Synchronisation Indicator	0		9.2.3.18
»>RAB Parameters	0		9.2.1.3	Includes ail necessary parameters for RABs (both for MSC and SGSN) including QoS.
»>User Plane Information	0				-
»»User Plane Mode	M		9.2.1.18		-
»»UP Mode Versions	M		9.2.1.19		-
»>Transport Layer Information	O				-
»»Transport Layer Address	M		9.2.2.1		-
»»Iu Transport Association	M		9.2.2.2		-
»>Service Handover	0		9.2.1.41		-
»>E-UTRAN Service Handover	0		9.2.1.90		YES	ignore
»>Correlation ID	0		9.2.2.5		-
»>PLMN of PGW/GGSN	O				YES	ignore
»Second Setup Or Modify Item	M			Grouping reason: same criticality	EACH	ignore
»>PDP Type Information	0		9.2.1.40		-
»>Data Volume Reporting Indication	0		9.2.1.17
»>DL GTP-PDU Sequence Number	0		9.2.2.3		-
»>UL GTP-PDU Sequence Number	0		9.2.2.4		-
»>DL N-PDU Sequence Number	0		9.2.1.33		-
>»UL N-PDU Sequence Number	0		9.2.1.34		-
»> Alternative RAB Parameter Values	O		9.2.1.43		YES	ignore

»>GERAN B SC Container	O		9.2.1.58		YES	ignore
»>PDP Type Information extension	0		9.2.1.40a	TheADF Type Information extension IE can only be included if PDP Type Information IE is not présent.	YES	ignore
»>Offload RAB parameters	0		9.2.1.94	Applicable only for SIPTO at IuPS	YES	ignore
RABs To Be Released List	0				YES	ignore
>RABs To Be Released Item lEs		1 to <maxnoofRABs>			EACH	ignore
»RAB ID	M		9.2.1.2	The same RAB ID must only be présent in one group.
»Cause	M		9.2.1.4		-
UE Aggregate Maximum Bit Rate	0		9.2.1.91		YES	ignore
MSISDN	O		9.2.1.95	Applicable only for SIPTO at IuPS	YES	ignore

TABLE 8
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticaiity	Assigned Criticaiity
Message Type	M		9.2.1.1		YES	reject
MME UE SI AP ID	M		9.2.33		YES	reject
eNBUESlAPID	M		9.23.4		YES	reject
UE Aggregate Maximum Bit Rate	M		9.2.1.20		YES	reject
E-RAB to Be Setup List		1			YES	reject
>E-RAB to Be Setup Item IEs		1 to <maxnoofE- RABs>			EACH	reject
»E-RAB ID	M		9.2.1.2		-
»E-RAB Level QoS Parameters	M		9.2.1.15	Includes necessary QoS parameters	-
»Transport Layer Address	M		9.2.2.1		-
»GTP-TEID	M		9.2.2.2		-
»NAS-PDU	O		9.23.5		-
»Correlation ID	0		9.2.2.80		YES	ignore
»PLMNofPGW	0				YES	ignore
UE Security Capabilities	M		9.2.1.40		YES	reject
Security Key	M		9.2.1.41	TheKeNB is provided after the key-generation in the MME, see TS 33.401 [15]	YES	reject
Trace Activation	0		9.2.1.4		YES	ignore
Handover Restriction List	0		9.2.1.22		YES	ignore
UE Radio Capability	0		9.2.1.27		YES	ignore
Subscriber Profile ID for RAT/Frequency priority	0		9.2.139		YES	ignore
CS Fallback Indicator	0		9.23.21		YES	reject
SRVCC Operation Possible	0		9.2.1.58		YES	ignore
CSG Membership Status	o		9.2.1.73		YES	ignore
Registered LAI	0		9.23.1		YES	ignore
GUMMEI ID	0		9.23.9	This IE indicates the MME serving the UE	YES	ignore
MMEUES1APID2	0		9.23.3	This IE indicates the MME UE SI AP ID assigned by the MME	YES	ignore
Management Based MDT Allowed	0		9.2.1.83		YES	ignore

TABLE 9
IE/Group Name	Presence	Range	IE type and reference	Semantics description	Criticality	Assigned Criticality
Message Type	M		9.2.1.1		YES	reject
MME UE SI AP ID	M		9.233		YES	reject
eNB UE SI AP ID	M		9.23.4		YES	reject
UE Aggregate Maximum Bit Rate	0		9.2.1.20		YES	reject
E-RAB to be Setup List		1			YES	reject
>E-RAB To Be Setup Item lEs		1 to <maxnoofE- RABs>			EACH	reject
»E-RAB ID	M		9.2.1.2		-
»E-RAB Level QoS Parameters	M		9.2.1.15	Includes necessary QoS parameters
»Transport Layer Address	M		9.2.2.1		-
»GTP-TEID	M		9.2.2.2	EPC TEID	-
»NAS-PDU	M		9.23.5		-
»Correlation ID	0		9.2.2.80		YES	ignore
»PLMN ofPGW	0				YES	ignore

Claims (20)

1. A method in a communication System (100) comprising a first core network node (CN), a second CN, a base station apparatus (104, 114) serving a user equipment (UE) (128), and a packet data network gateway (PGW) (120) associated with the UE, the method being performed by the first CN and comprising:

the first CN receiving a tunneling endpoint identifier (TEID) information element from a second CN, the TEID information element comprises a plurality of fields, wherein one of said plurality offields includes a Public Land Mobile Network (PLMN) identifierofthe PGW; and the first CN forwarding the received PLMN identifier to the base station apparatus.

2. The method of claim 1, wherein the TEID information element is a fully qualified TEID (FTEID) information element.

3. The method of claim 1, wherein the base station apparatus is an enodeB (eNB)(114).

4. The method of embodiment 1, wherein:

the base station apparatus comprises a radio network controller (RNC)(106) and a base station, and forwarding the received PLMN identifier to the base station apparatus comprises forwarding the PLMN identifier to the RNC.

5. The method of claim 1, wherein the first CN is a serving general packet radio service support node (SGSN) (108) and the second CN is a gateway general packet radio service support node (GGSN)(110).

6. The method of claim 1, wherein the first CN is an mobility management entity (MME) (116) and the second CN is an signaling gateway (SGW) (118).

7. The method of claim 1, wherein said on of said plurality of fields of the information element includes a TEID/GRE Key field.

8. A method in a communication System comprising an SGSN (108), a base station (114) serving a user equipment (UE) (128), an RNC (106) controlling the base station, and a packet data network gateway (PGW) (120) associated with the UE, the method being performed by the SGSN and comprising:

the SGSN obtaining a PLMN identifier (ID) ofthe PGW; and the SGSN transmitting the PLMN ID to the RNC.

9. A method in a communication system comprising a first core network node (CN), a base station apparatus (114) serving a user equipment (UE) (128), and a packet data network gateway (PGW) (120) associated with the UE, the method being performed by the first CN and comprising:

the first CN obtaining a PLMN identifier of the PGW; and the first CN transmitting a message to the base station apparatus, wherein the message comprises: i) an information element containing the PLMN ID ofthe PGW and ii) a radio access bearer (RAB) identifier information element comprising data identifying a RAB.

10. The method of claim 9, wherein the message further comprises a message type information element indicating that the message is a RAB Assignment Request message.

11. The method of claim 9, wherein the message further comprises a message type information element indicating that the message is an Initial Context Setup Request message.

12. The method of claim 9, wherein the message further comprises a message type information element indicating that the message is a EUTRAN RAB (E-RAB) Setup Request message.

13. The method of claim 9, wherein the message further comprises a message type information element indicating that the message is a Handover Request message.

14. The method of claim 9, wherein the first CN is an MME (116).

15. The method of claim 9, wherein the RAB is an E-RAB.

16. The method of claim 9, further comprising:

the base station apparatus transmitting to a source MME a handover message comprising the PLMN ID ofthe PGW;

the source MME transmitting to a target MME a relocation request message comprising the

PLMN ID received by the source MME in the handover message; and the target MME transmitting to a target base station apparatus a message comprising the PLMN ID the target MME received from the source MME via the relocation message.

17. A method in a communication system comprising a first core network node (CN), a second CN, and a packet data network gateway (PGW) (120) associated with user equipment (UE) (128), the method being performed by the first CN and comprising:

the first CN encoding a Public Land Mobile Network identifier (PLMN ID) of the PGW in a TEID/GRE Key field of a F-TEID information element; and the first CN transmitting the F-TEID information element containing the PLMN ID to the second CN.

18. The method of claim 17, wherein the first CN is a SGW and the second CN is an MME (116).

19. The method of claim 17, further comprises the second CN transmitting the received PLMN ID to a base station apparatus serving the UE.

20. The method of claim 17, wherein the step of transmitting the F-TEID information element to the second CN comprises transmitting a create session response, including the F-TEID information element, to the second CN; and the method further comprises:

prior to the first CN encoding the PLMN ID in the TEID/GRE key field, the first CN receiving a create session request message from the second CN, wherein the create session request identifies the PGW.