METHODS FOR PROVIDING A PLMN IDENTIFIER OF A PACKET DATA NETWORK GATEWAY TO A NODE OF A RAN

CROSS REFERENCE TO RELATED APPLICATION(S)

[ 001 ] 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

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

BACKGROUND

[ 003] 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).

[ 004 ] 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 telecommunications system (UMTS), long term evolution (LTE), etc.

SUMMARY

[ 005] According to an aspect of the present 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.

[ 006] According to another aspect of the present 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.

[ 007 ] According to another aspect of the present 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 of the PGW; and (ii) a radio access bearer (RAB) identifier information element including data identifying a RAB.

[ 008 ] According to another aspect of the present 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) of the 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. [ 009 ] The SIRIG function supports both roaming and network sharing scenarios.

(See SP-120252 and SP-120483). The solution to support the roaming scenario 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 GEPvAN access. In order to allow the GERAN to map the SCI into PvRM 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 GEPvAN uses the information from the

SGSN to determine 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 handover from (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."

[ 0010 ] Thus, the BS based on the knowledge of the 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 or Visited PLMN) interprets the semantics of SCI and apply relevant radio resource management (RRM) behaviors. But, the above solution may have 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. [ 0011 ] 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.".

[ 0012 ] 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 of the PGW (i.e., the PLMN in which the PGW is located) for each bearer contexts within a given PDN connection. The SGW or MME/SGSN can inform

RNC/eNB about the PLMN of the 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 have no PDN connection level concept but only bearer context within a PDN connection.

BRIEF DESCRIPTION OF DRAWINGS

[ 0013] FIG. 1 illustrates an example communication system 100 in which embodiments of this disclosure are implemented;

[ 0014 ] FIGS. 2-9 illustrates example flows in which embodiments of this disclosure are implemented; and

[ 0015] FIG. 10 illustrates an example block diagram of an example core network node.

DETAILED DESCRIPTION

[ 0016] This disclosure relates to providing a PLMN identifier to a node of a radio access network (RAN). In embodiments, the present 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 1 14, RNC 106, SGSN 108, SGW 1 18, 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.

[0017] I. Embed PLMN identifier in the user plane address

[0018] 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 1 12 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.

[0019] The SGW 1 18 (3G when DT is used or 4G for EPS), the SGSN 108 (when DT is not used in 3G), or the GGSN 1 10 (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 1 16/SGSN 108 (through S I -MME and Iu interface).

[0020 ] 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 1 16 during RAB assignment procedure or during initial UE context setup/E-RAB establishment procedure to the RNC 106 or the eNB 1 14. Those SGW F-TEID(s) are used by RNC 106 and eNB 1 14 to send any uplink user plane data. During SRNS relocation procedure in 3G or handover procedure in LTE, the target SGSN 108 or MME 1 16 provides the SGW 1 18 user plane F-TEID either received from the source MME 1 16/SGSN 108 (in case the SGW is not relocated) or from a new SGW (in case the SGW is relocated).

[0021] This disclosure proposes that the SGW 1 18 embed a PLMN identifier (PLMN ID) into the SGW F-TEID when it is sent to the MME 1 16/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 1 18 receiving a create session request message from an MME 1 16 (or SGSN 108) and then transmitting a create session response message to the MME 1 16/SGSN 108, which creates a session response message that includes an F-TEID information element that contains a field containing the PLMN ID.

[ 0022 ] 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.

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

[ 0023] 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.

[ 0024 ] 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.

[ 0025] 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 specifications 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 PvAB is established.

[ 0026] When indirect data forwarding is used during handover/SRNS relocation procedure and when the SGW 1 18 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 non-anchor 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 1 18 allocates SGW F-TEID for data forwarding, it can embed such PLMN information of the PGW into the SGW F-TEID.

[ 0027 ] II. Provide PLMN ID during bearer establishment

[ 0028 ] It is also possible to provide the PLMN ID of the PGW 120 serving the UE 128 to the RNC 106 or eNB 1 14 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 1 16.

[ 0029] 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.

[ 0030 ] 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. [ 0031 ] An MME may provide to an eNB 1 14 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.

[ 0032 ] An MME 1 16 may provide to an eNB 1 14 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 1 10 IE in the E-RAB SETUP REQUEST message is shown in Table 3. Once the PLMN of PGW 120/GGSN 1 10 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 1 12 and both for network based handovers (i.e. SI or RANAP handovers) or direct interface handovers such as X2 or Iur handovers. The SI handover procedure for E-UTRAN 1 12 is described in TS23.401 section 5.5.1.2.2 and it is shown in FIG. 9. In alternate embodiments, an equivalent procedure exists for UTRAN RANAP based handovers.

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

[ 0034 ] 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 equivalent modification can be applied to UTRAN 102 by adding the "PLMN of PGW/GGSN" IE by using a RANAP: RELOCATION REQUEST message.

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

[ 0036] 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 of the 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).

[ 0037 ] 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).

[ 0038 ] The new information concerning the PLMN ID of the PGW 120/GGSN 1 10 associated to the RAB handed over may be sent for each RAB.

[ 0039] The information added to the messages and procedures above shall not be limited to the PLMN ID of the PGW 120/GGSN 1 10 to which the RAB is associated. Such information could include any indication that allows the RAN to understand the actions to be taken upon reception 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 specific SIRIG marking.

[ 0040 ] III. Example network node

[ 0041 ] FIG. 10 illustrates 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 specific integrated circuit (ASIC), Field- programmable gate 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 mediums, 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)).

[ 0042 ] 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.

[ 0043] 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 of the present 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.

[ 0044 ] While various aspects and embodiments of the present disclosure have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described exemplary embodiments. Moreover, any combination of the elements described in this disclosure in all possible variations thereof is encompassed by the disclosure unless otherwise indicated herein or otherwise clearly contradicted by context.

[ 0045] 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 re-arranged, and some steps may be performed in parallel.

TABLES [ 0046] 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.

»> Alternative RAB o 9.2.1.43 YES Ignore Parameter Values

»>GERAN BSC O 9.2.1.58 YES Ignore

Container

>»PDP Type o 9.2.1.40a The PDF YES Ignore

Information extension Type

Information

extension IE

can only be

included if

PDF Type

Information

IE is not

present.

»>Offload RAB o 9.2.1.94 Applicable YES Ignore parameters only for

SIPTO at Iu- PS.

RABs To Be Released List o YES Ignore

>RABs To Be Released / to EACH Ignore

Item IEs <maxnoqfRABs>

»RAB ID M 9.2.1.2 The same

RAB ID must

only be

present in one

group.

»Cause M 9.2.1.4

UE Aggregate Maximum O 9.2.1.91 YES Ignore

Bit Rate

MSISDN o 9.2.1.95 Applicable YES Ignore only for

SIPTO at Iu- PS.

TABLE 2

Πϊ/Group Name Presence Range IE type Semantics Criticality Assigned and description Criticality reference

Message Type M 9.2.1.1 YES reject

MME UE S1AP ID M 9.2.3.3 YES reject eNB UE S1AP ID M 9.2.3.4 YES reject

UE Aggregate M 9.2.1.20 YES reject Maximum Bit Rate

E-RAB to Be Setup 1 YES reject

List

>E-RAB to Be Setup 1 .. EACH reject Item IEs <maxnoofli- RABs>

»E-RAB ID M 9.2.1.2 -

»E-RAB Level M 9.2.1.15 Includes -

QoS Parameters necessary QoS

parameters.

»Transport Layer M 9.2.2.1 - Address

»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 0 9.2.3.8 The PLMN

PGW ID of the

PGW/GGSN

involved in

the RAB

assignment

TABLE 3

IE/Group Name Presence Range W, type and Semantics Criticality Assigned reference description Criticality

Message Type M 9.2.1.1 YES reject

MME UE S1AP ID M 9.2.3.3 YES reject eNB UE S1AP ID M 9.2.3.4 YES reject

UE Aggregate Maximum 0 9.2.1.20 YES reject

Bit Rate

E-RAB to be Setup List 1 YES reject

>E-RAB To Be Setup I .. <maxnoof EACH reject

Item IEs E-RABs>

»E-RAB ID M 9.2.1.2 -

»E-RAB Level QoS M 9.2.1.15 Includes -

Parameters necessary

QoS

parameters.

»Transport Layer M 9.2.2.1 - Address

»GTP-TEID M 9.2.2.2 EPC TEID. -

»NAS-PDU M 9.2.3.5 -

»Correlation ID 0 9.2.1.80 YES ignore

»PLMN of PGW 0 9.2.3.8 The PLMN

ID of the

PGW/GGSN

involved in

the RAB

assignment

wrong HO.

TABLE 6

IE/Group Name Presence Range IE type Semantics Criticality Assigned and description Criticality reference

Message Type M 9.2.1.1 YES ignore

Source RNC To M 9.2.1.28 YES reject

Target RNC

Transparent

Container

Old Iu Signalling O 9.2.1.38 YES ignore

Connection

Identifier CS

domain

Global CN-ID CS O 9.2.1.46 YES reject domain

Old Iu Signalling o 9.2.1.38 YES ignore

Connection

Identifier PS

domain

Global CN-ID PS o 9.2.1.46 YES reject domain

RABs To Be Setup o YES reject

List

>RABs To Be 1 to <maxnoqfRABs> EACH reject

Setup Item IEs

»CN Domain M 9.2.1.5 -

Indicator

»RAB ID M 9.2.1.2 -

»RAB M 9.2.1.3 -

Parameters

»Data C - ifPS 9.2.1.17 -

Volume

Reporting

Indication

»PDP Type C - ifPS 9.2.1.40 -

Information

»>PLMN of O 9.2.3.33 The PLMN

PGW/GGSN ID of the

PGW/GGSN

involved in

the RAB

assignment

»User Plane M

Information

»>User M 9.2.1.18 -

Plane Mode

»>UP Mode M 9.2.1.19 -

Versions

»Data O

Forwarding

TNL

Information

»>Transport M 9.2.2.1

Layer

Address

»>Transport M Iu Related to

Association Transport TLA above.

Association

9.2.2.2

»Source Side O

Iu UL TNL

Information

»>Transport M 9.2.2.1 -

Layer

Address

»>Iu M 9.2.2.2 -

Transport Association

»Service O 9.2.1.41 -

Handover

»Alternative O 9.2.1.43 -

RAB Parameter

Values

»E-UTRAN o 9.2.1.90 YES ignore

Service

Handover

»PDP Type o 9.2.1.40a The PDF YES Ignore

Information Type

extension Information

extension IE

can only be

included if

PDF Type

Information

IE is present.

SNA Access o 9.2.3.24 YES ignore

Information

UESBI-Iu o 9.2.1.59 YES ignore

Selected PLMN o 9.2.3.33 YES ignore

Identity

CN MBMS o YES ignore

Linking

Information

>Joined MBMS / to EACH ignore

Bearer Service <maxnoofMulticastServicesPerUE>

IEs

»TMGI M 9.2.3.37 -

»PTP RAB ID M 9.2.1.75 -

Integrity Protection o 9.2.1.11 Integrity YES ignore

Information Protection

Information

includes key

and

permitted

algorithms.

Encryption o 9.2.1.12 Integrity YES ignore Information Protection

Information

includes key

and

permitted

algorithms.

UE Aggregate o 9.2.1.91 YES ignore

Maximum Bit Rate

RAB Parameters o 9.2.1.102 Applicable YES reject

List only to

RNSAP

relocation.

CSG ID o 9.2.1.85 Applicable YES reject only to

Enhanced

Relocation

from RNC

towards a

hybrid cell

and RNSAP

relocation.

CSG Membership o 9.2.1.92 Applicable YES reject

Status only to

Enhanced

Relocation

from RNC

towards a

hybrid cell

TABLE 7

IE/Group Name Presence Range IE type Semantics Criticality Assigned and description Criticality reference

Message Type M 9.2.1.1 YES reject

RABs To Be Setup Or 0 YES ignore

Modified List

>RABs To Be Setup I to

Or Modified Item IEs <maxnoofl{ABs>

»First Setup Or M Grouping EACH reject

Modify Item reason:

same

criticality

»>RAB ID M 9.2.1.2 The same

RAB ID

must only

be present

in one

group.

»>NAS 0 9.2.3.18 -

Synchronisation

Indicator

»>RAB 0 9.2.1.3 Includes all -

Parameters necessary

parameters

for RABs

(both for

MSC and

SGSN)

including

QoS.

»>User Plane 0 -

Information

»»User Plane M 9.2.1.18 -

Mode

»»UP Mode M 9.2.1.19 -

Versions

»>Transport 0 -

Layer

Information

»»Tran sport M 9.2.2.1 - Layer Address

»»Iu M 9.2.2.2 -

Transport

Association

»>Service 0 9.2.1.41 -

Handover

»>E-UTRAN 0 9.2.1.90 YES ignore

Service Handover

»>Correlation ID 0 9.2.2.5 -

»>PLMN of 0 YES ignore

PGW/GGSN

»Second Setup Or M Grouping EACH ignore

Modify Item reason:

same

criticality

»>PDP Type 0 9.2.1.40 - Information »>Data Volume 0 9.2.1.17 -

Reporting

Indication

»>DL GTP-PDU 0 9.2.2.3 -

Sequence Number

»>UL GTP-PDU 0 9.2.2.4 -

Sequence Number

»>DL N-PDU 0 9.2.1.33 -

Sequence Number

»>UL N-PDU 0 9.2.1.34 -

Sequence Number

»>Alternative 0 9.2.1.43 YES ignore

RAB Parameter

Values

»>GERAN BSC 0 9.2.1.58 YES ignore

Container

»>PDP Type 0 9.2.1.40a The D YES ignore

Information Type

extension Information

extension IE

can only be

included if

PDP Type

Information

IE is not

present.

>»Offload RAB 0 9.2.1.94 Applicable YES ignore parameters only for

SIPTO at

Iu-PS

RABs To Be Released 0 YES ignore

List

>RABs To Be I to EACH ignore

Released Item IEs <maxnoqfRABs>

»RAB ID M 9.2.1.2 The same

RAB ID

must only

be present

in one

group.

»Cause M 9.2.1.4 -

UE Aggregate Maximum 0 9.2.1.91 YES ignore

Bit Rate

MSISDN 0 9.2.1.95 Applicable YES ignore only for

SIPTO at

Iu-PS

TABLE 9

IE/Group Name Presence Range W, type and Semantics Criticality Assigned reference description Criticality

Message Type M 9.2.1.1 YES reject

MME UE S1AP ID M 9.2.3.3 YES reject eNB UE S1AP ID M 9.2.3.4 YES reject

UE Aggregate Maximum 0 9.2.1.20 YES reject

Bit Rate

E-RAB to be Setup List 1 YES reject

>E-RAB To Be Setup I to <maxnoof EACH reject

Item IEs E-RABs>

»E-RAB ID M 9.2.1.2 -

»E-RAB Level QoS M 9.2.1.15 Includes -

Parameters necessary

QoS

parameters

»Transport Layer M 9.2.2.1 - Address

»GTP-TEID M 9.2.2.2 EPC TEID -

»NAS-PDU M 9.2.3.5 -

»Correlation ID 0 9.2.2.80 YES ignore

»PLMN of PGW 0 YES ignore