WO2017078794A1

WO2017078794A1 - Solution for proxy-call session control function

Info

Publication number: WO2017078794A1
Application number: PCT/US2016/035586
Authority: WO
Inventors: Changhong Shan
Original assignee: Intel IP Corporation
Priority date: 2015-11-06
Filing date: 2016-06-02
Publication date: 2017-05-11

Abstract

A mobility management entity (MME) may comprise a processor to look up a mapping table between a list of one or more evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (ECGI) list and one or more geographical identifiers for a user equipment (UE) to obtain a first geographical identifier corresponding to a current ECGI; and provide to a serving gateway (SGW) the first geographical identifier in a Create Session Request message; and a memory coupled to the processor to store the geographical identifier obtained from the mapping table. Other embodiments may be described and/or claimed.

Description

SOLUTION FOR PROXY-CALL SESSION CONTROL FUNCTION

Cross Reference to Related Applications

The present application claims priority to PCT Patent Application No.

PCT/CN2015/094012, filed on November 6, 2015 (attorney docket no. P92853PCT-Z), the entire specification of which is hereby incorporated by reference in its entirety for all purposes, except for those sections, if any, that are inconsistent with this specification.

BACKGROUND

Wireless mobile communication technology uses various standards and protocols to provide telecommunication services to fixed or mobile subscribers, e.g., a base station and a wireless mobile device. In the third generation partnership project (3 GPP) long term evolution (LTE) systems, a base station may be an evolved Node Bs (eNode Bs or eNBs) that may communicate with the wireless mobile device, known as a user equipment (UE).

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure described herein is illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. For example, the dimensions of some elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements. Aspects, features and advantages of embodiments of the present disclosure will become apparent from the following description of the disclosure in reference to the appended drawing in which like numerals denote like elements and in which:

Figure 1 schematically illustrates a block diagram of an example wireless network in accordance with various embodiments;

Figure 2 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 3 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 4 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 5 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 6 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 7 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 8 schematically illustrates a block diagram of an example of a structure in accordance with various embodiments;

Figure 9 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 10 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 11 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 12 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 13 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 14 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 15 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 16 schematically illustrates an example of a flow chart of one or more processes in accordance with various embodiments;

Figure 17 illustrates an example of a block diagram of a mobile communication device in accordance with various embodiments; and

Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended.

DETAILED DESCRIPTION

Before the present disclosure is disclosed and described, it is to be understood that this disclosure is not limited to the particular structures, process steps, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element.

References in the specification to "one embodiment", "an embodiment", "an example embodiment", etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

Embodiments of the disclosure may be implemented in hardware, firmware, software, or any combination thereof. Embodiments of the disclosure may also be implemented as instructions stored on a machine-readable medium, which may be read and executed by one or more processors. A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device, a mobile device, a smartphone, etc.). For example, a non-transitory machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices. For another example, a transitory machine-readable medium may include electrical, optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and others.

The following description may include terms, such as first, second, etc. that are used for descriptive purposes only and are not to be construed as limiting. As used herein, the term "module" and/or "unit" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

Further, various operations will be described as multiple discrete operations, in turn, in a manner that is most helpful in understanding the illustrative embodiments; however, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not need to be performed in the order of presentation.

The following embodiments may be used in a variety of applications including transmitters and receivers of a radio system, although the present disclosure is not limited in this respect. Examples of radio systems may include, but are not limited to, network interface cards (NICs), network adaptors, fixed or mobile client devices, relays, base stations, femtocells, gateways, bridges, hubs, routers, access points, or other network devices. Further, the radio systems within the scope of the disclosure may be implemented in cellular radiotelephone systems, satellite systems, two-way radio systems as well as computing devices including such radio systems, e.g., personal computers, tablets and related peripherals, personal digital assistants, personal computing accessories, hand-held communication devices and all systems which may be related in nature and to which the principles of the inventive embodiments could be suitably applied.

In third generation partnership project (3 GPP) radio access network (RAN) long term evolution (LTE) systems, a transmission station may comprise a combination of an evolved universal terrestrial radio access network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs), which may communicate with a wireless mobile device, known as a user equipment (UE). A downlink transmission may comprise a communication from the transmission station (or eNodeB) to the wireless mobile device (or UE), and an uplink transmission may comprise a

communication from the wireless mobile device to the transmission station.

Some embodiments may be used in conjunction with various devices and/or systems, for example, a UE, a mobile device, a mobile wireless device, a mobile communication device, a wireless station, a mobile station, a personal computer, a desktop computer, a mobile computer, a laptop computer, a netbook computer, a notebook computer, a tablet computer, a smartphone device, a mobile phone, a cellular phone, a server computer, a handheld computer, a handheld mobile device, a personal digital assistant (PDA) device, a handheld PDA device, an on-board device, an off-board device, a hybrid device, a vehicular device, a non-vehicular device, a mobile or portable device, a consumer device, a non-mobile or non-portable device, a wireless communication station, a wireless communication device, a wireless access point (AP), a wireless node, a base station (BS), a wired or wireless router, a wired or wireless modem, a video device, an audio device, an audio-video (A/V) device, a wired or wireless network, a wireless area network, a cellular network, a cellular node, a cellular device, a wireless local area network (WLAN) device, an universal integrated circuit card (UICC), an ultra mobile PC (UMPC), a customer premise equipment (CPE), a multiple input multiple output (MIMO) transceiver or device, a device having one or more internal antennas and/or external antennas, a digital video broadcast (DVB) device, a multi- standard radio device, a wired or wireless handheld device, a wireless application protocol (WAP) device, vending machines, sell terminals, a wearable device, a handset, and/or other consumer electronics such as MP3 players, digital cameras and the like, personal computing accessories and existing and future arising wireless mobile devices which may be related in nature and to which the principles of the embodiments could be suitably applied.

Figure 1 demonstratively illustrates examples of a network architecture 100, in accordance with some demonstrative embodiments.

In some embodiments, UE 102 may communication with a base station, e.g., eNB 104 via, e.g., a Uu interface or any other suitable interface. The eNB 104 may be in an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) that may comprise one or more eNB 104. The eNB 104 may communicate with a mobility management entity (MME) 106 via, e.g., a S 1 -MME interface or any other suitable interface. The eNB 104 may further communicate with a serving gateway (SGW) 108 via, e.g., a Sl-u interface or any other suitable interface.

In some embodiments, SGW 108 may communicate with a serving GPRS (General Packet Radio Service) support node (SGSN) 110, e.g., via a S4 interface or any other suitable interface. The SGW 108 may communicate with MME 106, e.g., via a SI 1 interface or any other suitable interface. MME 106 may communicate with SGSN 110, e.g., via a S3 interface or any other suitable interface. MME 106 may communicate with a home subscriber server (HSS) 116, e.g., via an interface S6a or any other suitable interface. The SGW 108 may further communicate with a public data network (PDN) gateway (PGW) 112, e.g., via a S5/S8 interface or any other suitable interface. In some embodiments, the network 100 may comprise a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) and/or a global system for mobile communication (GSM) Enhanced Data Rate for GSM Evolution (EDGE) Radio Access Network (GERAN) that may be in VPLMN 140.

In some embodiments, PGW 112 may communicate with a policy and charging rules function (PCRF) 114, e.g., via a S5/S8 interface or any other suitable interface. PCRF 114 may be implemented in an entity, an apparatus, a device, a system, a circuitry, a module, a unit, and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, PCRF 114 may be configured to communicate, e.g., via a Rx interface, with one or more entities for internet protocol (IP) service(s) of an operator, e.g., IP multimedia subsystem (IMS), packet switching service (PSS) and/or other services. For example, the one or more IP service entities may comprise an IMS entity, e.g., a call session control function (CSCF) 120 that may support IMS.

In some embodiments, PGW 112 may comprise a policy and charging enforcement function (PCEF) entity 112A that may perform one or more processes or functions of PGW 112 as described in the disclosure. In some embodiments, PCEF 112A may be configured to comprise one or more geographical identifier related aspects, e.g., Figure 9 or Figure 14, as described in the disclosure.

In some embodiments, CSCF 120 may comprise a proxy-CSCF (P-CSCF) 120A, an interrogating CSCF (I-CSCF) 120B and/or a serving CSCF (S-CSCF) 120C. In some embodiments, the CSCF 120 may be implemented in an entity, an apparatus, a device, a system, a circuitry, a module, a unit, and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, P-CSCF 120A may be configured to communicate with PGW 112 via a SGi interface or any other suitable interface. In some embodiments, PGW 112, PCRF 114 and/or P-CSCF 120A may be located in a home public land mobile network (UPLMN) 130 for, e.g., Voice over LTE (VoLTE) home-routed roaming.

In some embodiments, UE 102, e B 104, MME 106, SGW 108 and/or SGSN 110 may be located in a virtual public land mobile network (VPLMN) 140. For a local breakout (LBO) routing, VPLMN 140 may use the same configuration used for subscriber(s) of the VPLMN 140 to support translation and/or routing of service number(s), e.g., local number(s). In some embodiments, for a roaming UE 102 that is home routed, e.g., in a S8 home routed (S8HR) roaming model, P-CSCF 120A in the home may retrieve a geographical identifier from, e.g., evolved packet core (EPC). In some embodiments, user location change reporting feature in 3GPP specification TS 23.401 may be enhanced to support geographical identifier granularity.

In some embodiments, MME 106 may be configured to maintain a mapping table between an E-UTRAN cell global identifier (ECGI) list and one or more geographical identifiers to support service number, e.g., local number, translation and/or routing. For example, a geographical identifier may identify a geographical area within a country or a territory. In some embodiments, a geographical identifier may be described in a geospatial manner (e.g. geodetic coordinates) within a country or a territory and/or as civic user location information (e.g. a postcode, area code, etc.) and/or may use an operator-specific format. In some embodiments, it may be assumed that a cell may not belong to more than one area or region or section identified by a geographical identifier.

In some embodiments, P-CSCF 120A in the home network, e.g., UPLMN 130, may be configured to retrieve a geographical identifier from PCRF 114, e.g., in a mobile origination session setup for a home-routed roaming or other procedure, e.g., in an IMS session establishment.

For example, in an attach (e.g., section 5.3.2 of TS 23.401) or a UE requested PDN connectivity (e.g., section 5.10.2 of 23.401) procedure, MME 106 may look up a geographical identifier in the mapping table to obtain the corresponding geographical identifier based on ECGI information, e.g., a current ECGI. In some embodiments, MME 106 may store in a memory of MME 106 the obtained geographical identifier corresponding to the ECGI information. MME 106 may send the geographical identifier to SGW 108 in, e.g., a create session request message. SGW 108 may forward the geographical identifier information to PGW 112. PGW 112 may send to PCRF 114 the geographical identifier information in an internet protocol-connectivity access network (IP-CAN) session establishment procedure.

In some embodiments, in response to receiving an updated ECGI, MME 106 may be configured to look up the updated ECGI in the mapping table between the ECGI list and the geographical identifiers to find out an updated geographical identifier corresponding to the updated ECGI. In some embodiments, MME 106 may compare the updated geographical identifier with a geographical identifier stored in MME 106. In response to determining that the updated geographical identifier is changed to be different from the geographical identifier stored in MME 106, MME 106 may be configured to report the updated geographical identifier, e.g., in a location change reporting procedure (e.g., section 5.9. 2 of TS 23.401). In some embodiments, MME 106 may store in a memory of MME 106 the updated geographical identifier corresponding to the updated ECGI.

In some other embodiments, MME 106 may report a geographical identifier or an updated geographical identifier to PCRF 114 via SGW 108 and/or PGW 112 in one or more other procedures, e.g., a tracking area update (TAU) procedure, a SI -based handover procedure, a UE triggered service request procedure, a location change reporting procedure.

In some embodiments, P-CSCF may retrieve a geographical identifier from PCRF 114. For example, in response to receiving a session initiation protocol (SIP) invite message, e.g., at an IP multimedia subsystem (FMS) session setup, P-CSCF 120A in the HPLMN 130 may be configured to send a request message to PCRF 114 in HPLMN 130 to retrieve a geographical identifier of UE 102 from PCRF 114, e.g., in response to detecting that the SIP invite may comprise a local number of a callee of UE 102. In some embodiments, the request message to PCRF 114 may comprise an indication to request for a geographical identifier and/or one or more user identifier (ID) of UE 102, e.g., international mobile subscriber identity (IMSI), international mobile equipment identity (IMEI), IP Multimedia Public Identity (IMPU) and/or IP Multimedia Private Identity (EVIPI).

In some embodiments, PCRF 114 may provide to P-CSCF 120 A a geographical identifier of UE 120 that may be stored in a memory of PCRF 114. In some other embodiments, PCRF 114 may request for a geographical identifier of UE 120 from MME 106 and/or may provide the obtained geographical identifier to P-CSCF 120A. In some embodiments, P-CSCF 120A may insert the retrieved geographical identifier from PCRF 114 in SIP signaling, e.g., the SIP invite to enable a routing decision in one or more downstream IMS entities, e.g., S-CSCF 120C and/or an application server (AS) 122, and/or the interconnected network.

Similarly, in some embodiments, AS 122 in UPLMN 130 may retrieve a geographical identifier of UE 102 from PCRF 114, e.g., at an IMS session establishment.

For example, in the attach procedure (e.g., section 5.3.2 of TS 23.401) and/or UE requested PDN Connectivity procedure (e.g., section 5.10. 2 of TS 23.401), MME 106 may be configured to look up a geographical identifier in the mapping table based on ECGI information to obtain the geographical identifier. In some embodiments, MME 106 may store in a memory of MME 106 the obtained geographical identifier corresponding to the ECGI. In some embodiments, MME 106 may send the obtained geographical identifier to SGW 108 in a create session request message. SGW 108 may forward the obtained geographical identifier in the create session request message to PGW 112 that may further send the obtained geographical identifier to PCRF 114 in the IP-CAN session establishment procedure.

In some embodiments, in response to receiving an updated ECGI, MME 106 may be configured to look up the updated ECGI in the mapping table between the ECGI list and geographical identifier(s) to find out an updated geographical identifier corresponding to the updated ECGI. In some embodiments, MME 106 may compare the updated geographical identifier with a geographical identifier stored in MME 106. In response to determining that the updated geographical identifier is change to be different from the geographical identifier stored in MME 106, MME 106 may be configured to report the updated geographical identifier, e.g., in a location change reporting procedure (e.g., section 5.9. 2 of TS 23.401). In some embodiments, MME 106 may store in a memory of MME 106 the updated geographical identifier corresponding to the updated ECGI.

In some embodiments, in response to receiving a SIP invite message from S-CSCF 120C, e.g., at an IMS session establishment, AS 122 may detect if a local number for a callee of UE 120 is included in the SIP invite message. In response to detecting that the local number for the callee is included, AS 122 may send a request message to PCRF 114, wherein the request message may comprise a user ID of UE 120 that may comprise, e.g., IMSI, IMEI, IMPU and/or EVIPI and/or an indication to request for a geographical identifier. In some embodiments, PCRF 114 may be configured to obtain the geographical identifier for the user, e.g., UE 102, from MME 106 via SGW 108 and/or may send the obtained geographical identifier of the user to AS 122.

In some other embodiments, AS 122 in UPMN 130 may retrieve a geographical identifier from HSS 116 and/or MME 106, e.g., at an IMS session establishment.

In some embodiments, in response to receiving a SIP invite message, e.g., of UE 102, from S-CSCF 120C, AS 122 may detect if a local number for a callee of UE 102 is included in the SIP invite message. In some embodiments, in response to detecting that the local number is included for the callee, AS 122 may provide to HSS 116 one or more user IDs of UE 102, e.g., IMSI, IMEI, IMPU and/or IMPI, and/or an indication to request for the geographical identifier of UE 102. In some embodiments, HSS 116 may provide to MME 106 one or more of the user ID(s), e.g. IMSI, IMEI, IMPU, and/or IMPI, and/or the indication of requesting geographical identifier to request MME 106 for the geographical identifier. MME 106 may send to HSS 116 the geographical identifier of the user that may be stored in MME 106 or a new or updated geographical identifier of the user associated with a UE location change. HSS 116 may send the geographical identifier received from MME 106 to AS 122 in HPLMN 130.

In some embodiments, the geographical identifier may be reported in one or more of an attachment procedure, a UE requested PDN connectivity, a tracking area update (TAU) procedure, a SI -based handover procedure, a UE triggered service request procedure, a location change reporting procedure and/or other procedures that may have a geographical identifier change.

In some embodiments, P-CSCF 120A and/or AS 122 may retrieve a geographical identifier from PCRF 114, e.g., in an FMS session setup or establishment. In some embodiments, P-CSCF 120A may retrieve a geographical identifier from PCRF 114, e.g., in a mobile origination (MO) session setup. In some embodiments, AS 122 may retrieve a geographical identifier from HSS 116 at an IMS Session setup.

In some embodiments, e B 104 may comprise a fixed station (e.g., a fixed node) or a mobile station/node. In various embodiments, the network 100 may comprise an access network of an access network of a 3 GPP LTE network such as E-UTRAN, 3 GPP LTE-A network, 4G network, 4.5G network, a 5G network, a 6G newtork or any other future communication network, a WiMax cellular network, HSPA, Bluetooth, WiFi or other type of wireless access networks or any other future standards.

In some embodiments, eNB 104 and/or UE 102 may support multiple-input and multiple-output (MTMO) communication with each other. For example, eNB 104 and/or UE 102 may comprise one or more antennas to utilize one or more radio resources of the wireless communication network 100. The eNB 104 and/or UE 102 may each comprise a set of one or more antennas to implement a multiple-input-multiple-output (MIMO) transmission/reception system. The MIMO transmission/reception system may operate in a variety of MIMO modes, including single-user MFMO (SU-MIMO), multi -user MIMO (MU-MIMO), close loop MIMO, open loop MIMO, full-dimension MIMO (FD-MFMO) or variations of smart antenna processing.

In some embodiments, eNB 104 may include a controller. The controller of eNB 104 may be coupled with a transmitter and a receiver and/or one or more communications modules or units in eNB 104. In some embodiments, eNB 104 may comprise the transmitter and/or the receiver that may be elements or modules of a transceiver. The transmitter and/or the receiver of eNB 104 may be coupled with the one or more antennas to communicate with UE 102.

UE 102 may comprise a transmitter and a receiver and/or one or more

communications modules or units. The transmitter and/or the receiver of UE 102 may communicate with a base station (BS), e.g., eNB 104 or other type of wireless access point such as wide area network (WW AN) via one or more antennas of the UE 102.

In some embodiments, eNB 104 may comprise other hardware, software and/or firmware components, e.g., a memory, a storage, an input module, an output module, one or more radio modules and/or one or more digital modules, and/or other components. The transmitter of eNB 104 may be configured to transmit signals to UE 102 via one or more antennas. The receiver of eNB 104 may be configured to receive signals from UE 102 via one or more antennas.

In some embodiments, controller of UE 102 may control one or more functionalities of eNB 104 and/or control one or more communications performed by eNB 104. In some embodiments, the controller of UE 102 may execute instructions of software and/or firmware, e.g., of an operating system (OS) of eNB 104 and/or of one or more applications. The controller of UE 102 may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, configuration circuitry, baseband circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller. In some embodiments, one or more functionalities of controller may be implemented by logic, which may be executed by a machine and/or one or more processors.

In various embodiments, UE 102 may communicate with e B 104 using one or more wireless communication standards including 3 GPP LTE, worldwide interoperability for microwave access (WiMAX), high speed packet access (HSPA), Bluetooth, WiFi, 5G standard and/or other wireless standards or future wireless standards. In some embodiments, UE 102 may communicate with eNB 104 via separate antenna(s) for each wireless communication standard or shared antenna(s) for multiple wireless communication standards. In some embodiments, UE 102 may communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a wireless wide area network (WW AN) or other network.

In some embodiments, UE 102 may comprise a controller, a transmitter, a receiver and one or more antennas. In some embodiments, UE 102 may comprise other hardware components, software components and/or firmware components, e.g., a memory, a storage, an input unit, an output unit and/or any other components. Transmitter may transmit signals to eNB 104 via one or more antennas. Receiver may receive signals from eNB 104 via one or more antennas. In some embodiments, the transmitter and/or the receiver may be elements or modules of a transceiver.

In some embodiments, the controller of UE 102 may be coupled to the receiver and the transmitter of UE 102. In some embodiments, the controller may control one or more functionalities of UE 102 and/or control one or more communications performed by UE 102. In some embodiments, controller may execute instructions of software and/or firmware, e.g., of an operating system (OS) of UE 102 and/or of one or more applications. The controller may comprise or may be implemented using suitable circuitry, e.g., controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, and/or any other circuitry, which may be configured to perform at least part of the functionality of controller. In some embodiments, one or more functionalities of controller may be implemented by logic, which may be executed by a machine and/or one or more processors.

In some embodiments, the controller of UE 102 and/or eNB 104 may comprise a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, circuitry, a baseband circuitry, a configuration circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), an application-specific IC (ASIC), or any other suitable

multi-purpose or specific processor or controller and/or any combination thereof.

The transmitter and/or the receiver of eNB 104 may comprise, or may be coupled with one or more antennas to communicate wirelessly with other components of the wireless communication network 100, e.g., UE 102. The transmitter and/or the receiver of UE 102 may comprise, or may be coupled with one or more antennas to communicate wirelessly with other components of the wireless communication network 100, e.g., eNB 104. In some embodiments, the transmitter/the receiver of UE 102 and/or eNB 104 may comprise one or more transmitters, one or more receivers, one or more transmitters, one or more receivers and/or one or more transceivers that may send and/or receive wireless communication signals, radio frequency (RF) signals, frames, blocks, transmission streams, packets, messages, data items, data, information and/or any other signals.

In some embodiments, the antennas of UE 102 and/or eNB 104 may comprise any type of antennas suitable to transmit and/or receive wireless communication signals, RF signals, blocks, frames, transmission streams, packets, messages, data items and/or data. For example, the antennas may comprise any suitable configuration, structure and/or arrangement of one or more antenna elements, components, units, assemblies and/or arrays. In some embodiments, the antennas may implement transmit and/or receive functionalities using separate transmit and/or receive antenna elements. In some embodiments, the antennas may implement transmit and/or receive functionalities using common and/or integrated transmit/receive elements. The antennas may comprise, for example, a phased array antenna, a single element antenna, a dipole antenna, a set of switched beam antennas, and/or the like.

In some embodiments, the eNB 104 may optionally comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in the eNB 104. In some embodiments, UE 102 may comprise other suitable hardware, software and/or firmware components that may be interconnected or operably associated with one or more components in UE 102. For example, eNB 104 and/or UE 102 may comprise one or more radio modules (not shown) to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules (not shown) to process signals transmitted and received on the air interface.

In some embodiments, eNB 104 and/or UE 102 may comprise one or more input units (not shown) and/or one or more output units (not shown). For example, one or more input units may comprise a keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a stylus, a microphone, or any other pointing/input unit or device. For example, one or more output units may comprise a monitor, a screen, a touch-screen, a flat panel display, a Cathode Ray Tube (CRT) display unit, a Liquid Crystal Display (LCD) display unit, a plasma display unit, one or more audio speakers or earphones, or any other output unit or device.

In some embodiments, UE 102 may comprise, for example, a mobile computer, a mobile device, a station, a laptop computing device, a notebook computing device, a netbook, a tablet computing device, an Ultrabook™ computing device, a handheld computing device, a handheld device, a storage device, a PDA device, a handheld PDA device, an on-board device, an off-board device, a hybrid device (e.g., combining cellular phone functionalities with PDA device functionalities), a consumer device, a vehicular device, a non-vehicular device, a mobile or portable device, a mobile phone, a cellular telephone, a PCS device, a mobile or portable GPS device, a DVB device, a wearable device, a relatively small computing device, a non-desktop computer, a "carry small live large" (CSLL) device, an ultra mobile device (UMD), an ultra mobile PC (UMPC), a mobile internet device (MID), an "Origami" device or computing device, a video device, an audio device, an audio/video (A/V) device, a gaming device, a media player, a smartphone, a mobile station (MS), a mobile wireless device, a mobile communication device, a handset, a cellular phone, a mobile phone, a personal computer (PC), a handheld mobile device, an universal integrated circuit card (UICC), a customer premise equipment (CPE), or other consumer electronics such as digital cameras and the like, personal computing accessories and existing and future arising wireless mobile devices which may be related in nature and to which the principles of the embodiments could be suitably applied.

In some embodiments, the network 100 may comprise a radio network controller (RNC) 118 that may communicate with an eNB, e.g., 104, and/or a MME, e.g., 106, or one or more other apparatus and/or devices and/or systems in the network 100.

While examples of eNB 104 and/or UE 102 have been described with regard to Fig. 1, eNB 104 and/or UE 102 may each comprise one or more radio modules or units that may modulate and/or demodulate signals transmitted or received on an air interface, and/or one or more digital modules or units (not shown) that may process signals transmitted and received on the air interface. While Fig. 1 illustrates examples of one or more apparatus and/or devices and/or systems in a network architecture, other embodiments may comprise other apparatus and/or devices and/or systems.

Figure 2 illustrates an example of a structure 200 in accordance with some embodiment. In some embodiments, the structure 200 may be implemented as a MME that may be configured to provide a geographical identifier as described in the disclosure. In some embodiments, the MME 200 may be implemented in an apparatus, a device, a system a circuitry, and/or any other structure using any suitably configured hardware, software and/or firmware.

In some embodiments, MME 200 may include one or more interfaces to interface between MME 200 and one or more other elements in a network, e.g., as described in the disclosure.

In some embodiments, MME 200 may include an eNB interface 202 to

communicate with eNB 104. For example, the eNB interface 202 may include an SI -MME interface to communicate with eNB 104 according to an SI Application protocol (AP) (S1AP).

In some embodiments, MME 200 may include a Home Subscriber Server (HSS) interface 206 to communicate with an HSS 116. For example, HSS interface 206 may include a S6 interface, or any other suitable interface.

In some embodiments, MME 200 may include a serving gateway (S-GW) interface 204 to communicate with an SGW 108. For example, SGW interface 204 may include a SI 1 interface, or any other suitable interface.

In some embodiments, MME 200 may comprise a processor 210 and/or a memory 212 that may be coupled with each other. MME 200 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of MME 200 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of MME 200 may be distributed among multiple or separate devices.

Processor 210 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor (shared, dedicated, or group), or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof, or any other suitable hardware, software and/or firmware components.

Processor 210 may execute instructions, for example, of an operating system (OS) of MME 200 and/or of one or more suitable applications. In some embodiments, some or all of the components of MME 106 may be enclosed in a common device and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of MME 106 may be distributed among multiple or separate devices.

In some embodiments, memory 212 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units and/or other storage units, e.g., a hard disk drive, a floppy disk drive, a compact disk (CD) drive, a CD-ROM drive, a DVD drive, or other suitable removable or non-removable storage units.

In some embodiments, the geographical identifier reporting module 208 may be configured to perform one or more processes and/or function as described in the disclosure. In some embodiments, MME 200 may comprise a geographical identifier reporting module or unit 208 that may be configured to report a geographical identifier, e.g., in an attach and/or UE requested PDN Connectivity procedure. In some embodiments, the geographical identifier reporting module 208 may be configured to provide a geographical identifier corresponding to an ECGI to SGW 108 that may forward the geographical identifier to PGW 112. PGW 112 may send the geographical identifier to PCRF 114.

In some embodiments, the geographical identifier reporting module 208 may be configured to maintain a mapping table between an ECGI list of one or more ECGIs and one or more geographical identifiers. For example, memory 212 may be configured to store the mapping table. In some embodiments, the geographical identifier reporting module 208 may be configured to look up a geographical identifier in the mapping table to obtain a geographical identifier that may correspond to the ECGI information, e.g., a current ECGI. In some embodiments, the geographical identifier reporting module 208 may report to SGW 108 the obtained geographical identifier in, e.g., a create session request message via, e.g., a transceiver 220 and/or a SGW interface 204. SGW 108 may forward the geographical identifier to PGW 112 that may send the geographical identifier to PCRF 114, e.g., in an IP-CAN session establishment procedure. In some embodiments, memory 212 may be configured to store the obtained geographical identifier corresponding to the ECGI information.

In some embodiments, the geographical identifier reporting module 208 may be configured to track a change in the ECGI and/or the geographical identifier. In some embodiments, the geographical identifier reporting module 208 may be configured to report the change in the geographical identifier and/or may provide an updated geographical identifier to PCRF 114 via SGW 108 and PGW 112 in response to detecting the change in the geographical identifier. In some embodiments, the geographical identifier reporting module 208 may be configured to look up the updated geographical identifier in the mapping table between the ECGI list and the geographical identifier(s) based on the updated ECGI and to obtain the updated geographical identifier corresponding to the updated ECGI. In some embodiments, the geographical identifier reporting module 208 may compare the updated geographical identifier with the geographical identifier stored in the memory 212. In response to determining that the updated geographical identifier is changed to be different from the geographical identifier stored in the memory 212, geographical identifier reporting module 208 may report the updated geographical identifier to PCRF 114 via SGW 108 and PGW 112, e.g., in a location change reporting procedure. In some embodiments, memory 212 may store the updated geographical identifier.

In some embodiments, the geographical identifier reporting module 208 may report a geographical identifier in a Tracking Area Update (TAU) procedure, a SI -based handover procedure, a UE triggered service request procedure, and/or a location change reporting procedure.

In some embodiments, in response to receiving a request for geographical identifier from the AS 122 in HPLMN 130, e.g., in an IMS session setup, HSS 116 may be configured to request MME 200 for a geographical identifier. In response to receiving from HSS 116 an indication of requesting graphical identifier and/or a user ID for a callee of UE 102, e.g., via the transceiver 220 and/or HSS interface 206, the geographical identifier reporting module 208 may send the geographical identifier of the user to HSS 1 16 that may further send the geographical identifier to the AS 122.

In some embodiments, the geographical identifier reporting module 208 may be configured to perform one or more processes and/or functions as described with regard to MME 106, MME 200 and/or other embodiments in the disclosure.

While Figure 2 illustrates the geographical identifier reporting module 208 may be provided in MME 200, in some other embodiments, the geographical identifier reporting module 208 may be provided in or implemented by one or more processors 210 or a baseband circuitry. While Figure 2 illustrates the transceiver 220, in some embodiments, the transceiver 220 may be implemented by one or more transmitters and/or one or more receivers. While Figure 2 illustrates one or more interfaces, e.g., 202, 204 or 206, in some embodiments, one or more other interfaces may be utilized. In some embodiments, the structure 200 may not comprise the one or more interfaces and/or other interfaces that may be included in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 220.

Figure 3 illustrates an example of a structure 300 in accordance with some embodiment. In some embodiments, the structure 300 may comprise a PCRF entity that may be configured to comprise one or more geographical identifier related aspects as described in the disclosure. In some embodiments, PCRF entity 300 may be implemented in an entity, an apparatus, a device, a system, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, PCRF entity 300 may be configured to perform one or more processes and/or functions as described with regard to PCRF entity 114 in the disclosure.

In some embodiments, PCRF entity 300 may include one or more interfaces to interface between PCRF entity 300 and one or more other elements in a network.

In some embodiments, PCRF entity 300 may include a PGW interface 302 to communicate with, e.g., PGW 112 as described above. For example, the PGW interface 302 may include a Gx interface or any other suitable interface to communicate with PGW 112.

In some embodiments, PCRF entity 300 may comprise an interface 304 that may be used for one or more operator's IP services, e.g., EVIS, PSS, etc. In some embodiments, the interface 304 may comprise a Rx interface or any other suitable interface to communicate with one or more entities, e.g., CSCF 120, that may be used for the one or more IP services.

In some embodiments, PCRF entity 300 may comprise a processor 310 and/or a memory 312 that may be coupled with each other. PCRF entity 300 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of PCRF entity 300 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of PCRF entity 300 may be distributed among multiple or separate devices.

In some embodiments, processor 310 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor (shared, dedicated, or group), or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof, or any other suitable hardware, software and/or firmware components.

Processor 310 may execute instructions, for example, of an operating system (OS) of

PCRF entity 300 and/or of one or more suitable applications. In some embodiments, some or all of the components of PCRF entity 300 may be enclosed in a common device and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of PCRF ENTITY 300 may be distributed among multiple or separate devices.

In some embodiments, memory 312 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 312 may be configured to store, for example, data and/or instructions for PCRF entity 300.

In some embodiments, PCRF entity 300 may comprise a geographical identifier reporting obtaining module or unit 306 that may be coupled to any other component in PCRF entity 300. In some embodiments, geographical identifier reporting module 306 may be configured to perform one or more processes and/or functions described in the disclosure. In some embodiments, geographical identifier reporting module 306 may be configured to obtain a geographical identifier from MME 106 via SGW 108 and PGW 112, e.g., in an attach procedure, a UE requested PDN Connectivity procedure, and/or a TAU procedure. In some embodiments, geographical identifier reporting module 306 may be configured to store the geographical identifier in the memory 312. The geographical identifier reporting module 306 may respond to an indication of IP-CAN session establishment message from PGW 112 with an Acknowledge of IP-CAN session establishment message that may comprise a new event trigger (Location Change (geographical identifier)). In some embodiments, the new event trigger may be used to enable a geographical identifier change reporting from MME 106 and/or PGW 112/PCEF 112A to PCRF 114, e.g., the geographical identifier reporting module 306. In some embodiments, the geographical identifier reporting module 306 may provide the new event trigger to PCEF 112A and/or a MME, e.g., 106, 106t, or 106n, to trigger or request the geographical identifier change reporting by the MME.

In some embodiments, in a SI -based handover procedure or a UE requested service request procedure, geographical identifier reporting module 306 may be configured to obtain the geographical identifier from MME 106 via SGW 108 and PGW 112 through the transceiver 320 and/or the PGW interface 302. The geographical identifier reporting module 306 may store the obtained geographical identifier in the memory 312. In some

embodiments, geographical identifier reporting module 306 may respond to an indication of IP-CAN session modification message from PGW 112 with an Acknowledge of IP-CAN session modification message via transceiver 320 and/or the PGW interface 302.

In some embodiments, in a location change reporting procedure, geographical identifier reporting module 306 may be configured to obtain a new geographical identifier from MME 106 via SGW 108 and PGW 112 through the transceiver 320 and/or the PGW interface 302. The geographical identifier reporting module 306 may store the obtained new geographical identifier in memory 312. In some embodiments, geographical identifier reporting module 306 may respond to an indication of IP-CAN session modification message from PGW 112 with an Acknowledge of IP-CAN session modification message via transceiver 320 and/or the PGW interface 302.

In some embodiments, during mobile origination session setup, geographical identifier reporting module or unit 306 may provide or report the geographical identifier to P-CSCF 120A, e.g., in an AA-Answer via the transceiver 320 and/or the interface 304, in response to receiving an AA-Request message from P-CSCF 120A. In some embodiments, geographical identifier reporting module or unit 306 may send to P-CSCF 120 A the geographical identifier that may be stored in the memory 312 of PCRF 114. For example, in response to receiving an indication of requesting graphical identifier and/or a local number for a callee, in the AA-request from P-CSCF 120A, e.g., via the transceiver 320 and/or P-CSCF interface 302, the geographical identifier reporting module 306 may send the geographical identifier to P-CSCF 120 A in the AA-Answer. In some embodiments,

P-CSCF 120 may insert the geographical identifier in a SIP signaling to enable routing decision in one or more downstream FMS entities, e.g., S-CSCF 120C and/or AS 122, and/or interconnected network.

In some embodiments, the geographical identifier reporting module 306 may store the received geographical identifier in memory 312 and/or may provide an Acknowledge of IP-CAN session establishment message and/or an Acknowledge of IP-CAN session modification message.

In some embodiments, the geographical identifier reporting module 306 may be configured to perform one or more processes and/or functions, e.g., as described with regard to PCRF 114, PCRF ENTITY 300 and/or other embodiments in the disclosure.

In some embodiments, the geographical identifier reporting module 306 may be configured to store in memory 312 one or more geographical identifiers received from MME 106 via SGW 108 and/or PGW 112.

While Figure 3 illustrates the geographical identifier reporting module 306 may be provided in PCRF entity 300, in some other embodiments, geographical identifier reporting module 306 may be provided in or implemented by one or more processors 310 or a baseband circuitry. While Figure 3 illustrates the transceiver 320, in some embodiments, the transceiver 320 may be implemented by one or more transmitters and/or one or more receivers. While Figure 3 illustrates one or more interfaces, e.g., 302 or 304, in some embodiments, one or more other interfaces may be utilized. In some embodiments, the one or more interfaces or other interfaces may not be required but may be implemented in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 320.

Figure 4 illustrates a structure 400 in accordance with some embodiment. In some embodiments, the structure 400 may be used by a SGW, e.g., 108 that may be configured to comprise one or more geographical identifier related aspects as described in the disclosure. In some embodiments, SGW 400 may be implemented in an entity, an apparatus, a device, a system, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, SGW 400 may be configured to perform one or more processes and/or functions as described with regard to SGW 108 in the disclosure.

In some embodiments, SGW 400 may include one or more interfaces to interface between SGW 400 and one or more other elements in a network.

In some embodiments, SGW 400 may include an eNB interface 402 to communicate with, e.g., eNB 104 as described above. For example, the eNB interface 402 may include a Sl-U interface or any other suitable interface to communicate with eNB 104.

In some embodiments, SGW 400 may include a MME interface 404 to communicate with, e.g., MME 106 as described above. For example, the PCRF interface 504 may include a SI 1 interface or any other suitable interface to communicate with MME 106.

In some embodiments, SGW 400 may include a PGW interface 406 to communicate with, e.g., PGW 112 as described above. For example, the PGW interface 406 may include a S8 interface or any other suitable interface to communicate with PGW 112.

In some embodiments, SGW 400 may comprise a processor 410 and/or a memory

412 that may be coupled with each other. SGW 400 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of SGW 400 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of SGW 400 may be distributed among multiple or separate devices.

In some embodiments, processor 410 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor (shared, dedicated, or group), or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof, or any other suitable hardware, software and/or firmware components.

Processor 410 may execute instructions, for example, of an operating system (OS) of SGW 400 and/or of one or more suitable applications. In some embodiments, some or all of the components of SGW 400 may be enclosed in a common device and may be

interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of SGW 400 may be distributed among multiple or separate devices.

In some embodiments, memory 412 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 412 may be configured to store, for example, data and/or instructions for SGW 400.

In some embodiments, SGW 400 may comprise a geographical identifier reporting module or unit 408 that may be coupled to any other component in SGW 400. In some embodiments, geographical identifier reporting module 408 may be configured to perform one or more processes and/or functions described in the disclosure. In some embodiments, geographical identifier reporting module 408 may be configured to obtain a geographical identifier from MME 106, e.g., via transceiver 420 and/or MME interface 404.

In some embodiments, the geographical identifier reporting module 408 may be configured to perform one or more processes and/or function as described with regard to SGW 108, SGW 300 and/or other embodiments in the disclosure.

In some embodiments, in an attach procedure, a UE requested PDN Connectivity procedure, and/or a Tracking Area Update (TAU) procedure, geographical identifier reporting module 408 may be configured to receive from MME 106 a create session request message that may comprise a geographical identifier via transceiver 420 and/or MME interface 404. In response to receiving the geographical identifier, the geographical identifier reporting module 408 may report or provide to PGW 112 the received geographical identifier, e.g., in a create session request message via the transceiver 420 and/or PGW interface 406. In some embodiments, PGW 112 may send the geographical identifier to PCRF 114, e.g., in an indication of IP-CAN session establishment message.

In some embodiments, in a SI -based handover procedure or a UE triggered service request procedure, geographical identifier reporting module 408 may be configured to receive from MME 106 a modify bearer request message that may comprise a geographical identifier, e.g., via transceiver 420 and/or MME interface 404. In response to receiving the geographical identifier in the modify bearer request message, geographical identifier reporting module 408 may provide or report to PGW 112 the received geographical identifier, e.g., in a modify bear request message via the transceiver 420 and/or PGW interface 406. In some embodiments, PGW 112 may send the geographical identifier to PCRF 114, e.g., in an indication of IP-CAN session establishment message.

In some embodiments, in a location change reporting procedure, geographical identifier reporting module 408 may be configured to receive from MME 106 a change notification message to indicate a new geographical identifier, e.g., via transceiver 420 and/or MME interface 404. In response to receiving the new geographical identifier, geographical identifier reporting module 408 may forward the change notification message with the new geographical identifier to PGW 112 via the transceiver 420 and/or the PGW interface 406. PGW 112 may send the geographical identifier in an indication of IP-CAN session modification message to PCRF 114. While Figure 4 illustrates the geographical identifier reporting module 408 may be provided in SGW 400, in some other embodiments, geographical identifier reporting module 408 may be provided in or implemented by one or more processors 410 or a baseband circuitry. While Figure 4 illustrates the transceiver 420, in some embodiments, the transceiver 420 may be implemented by one or more transmitters and/or one or more receivers. While Figure 4 illustrates one or more interfaces, e.g., 402, 404, or 406, in some embodiments, other interfaces may be utilized. In some embodiments, the one or more interfaces and/or other interfaces may be implemented in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 420.

Figure 5 illustrates a structure 500 in accordance with some embodiment. In some embodiments, the structure 500 may be used by a PGW, e.g., 112 that may be configured to comprise one or more geographical identifier related aspects as described in the disclosure. In some embodiments, PGW 500 may be implemented in an entity, an apparatus, a device, a system, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, PGW 500 may be configured to perform one or more processes and/or functions as described with regard to PGW 114 in the disclosure.

In some embodiments, PGW 500 may include one or more interfaces to interface between SGW 400 and one or more other elements in a network.

In some embodiments, PGW 500 may include an SGW interface 502 to

communicate with, e.g., e B 104 as described above. For example, the SGW interface 502 may include a S8 interface or any other suitable interface to communicate with SGW 108.

In some embodiments, PGW 500 may include a PCRF interface 504 to

communicate with, e.g., PCRF 114 as described above. For example, the PCRF interface 504 may include a Gx interface or any other suitable interface to communicate with PCRF 114.

In some embodiments, PGW 500 may include an interface 506 that may be used for one or more operator's IP services, e.g., EVIS, PSS, etc. In some embodiments, the interface 506 may comprise a Rx interface or any other suitable interface to communicate with one or more entities, e.g., CSCF 120, that may be used for the one or more IP services.

In some embodiments, PGW 500 may comprise a processor 510 and/or a memory 512 that may be coupled with each other. PGW 500 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of PGW 500 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of PGW 500 may be distributed among multiple or separate devices.

In some embodiments, processor 510 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor

(shared, dedicated, or group), or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof, or any other suitable hardware, software and/or firmware components.

Processor 510 may execute instructions, for example, of an operating system (OS) of PGW 500 and/or of one or more suitable applications. In some embodiments, some or all of the components of PGW 500 may be enclosed in a common device and may be

interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of PGW 500 may be distributed among multiple or separate devices.

In some embodiments, memory 512 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 512 may be configured to store, for example, data and/or instructions for PGW 500.

In some embodiments, PGW 500 may comprise a geographical identifier reporting module or unit 408 that may be coupled to any other component in PGW 500. In some embodiments, geographical identifier reporting module 408 may be configured to perform one or more processes and/or functions described in the disclosure. In some embodiments, geographical identifier reporting module 508 may be configured to obtain a geographical identifier from SGW 108, e.g., via transceiver 520 and/or SGW interface 502.

In some embodiments, the geographical identifier reporting module 408 may be configured to perform one or more processes and/or function as described in PGW 112 and/or PGW 500 and/or other embodiments in the disclosure. In some embodiments, in an attach procedure, a UE requested PDN Connectivity procedure, and/or a Tracking Area Update (TAU) procedure, geographical identifier reporting module 508 may be configured to receive from SGW 108 a create session request message that may comprise the geographical identifier via transceiver 520 and/or SGW interface 502. In response to receiving the geographical identifier, the geographical identifier reporting module 508 may send or report the received geographical identifier to PCRF 114, e.g., in an indication of IP-CAN session establishment message via the transceiver 520 and/or PCRF interface 406.

In some embodiments, in a SI -based handover procedure or a UE triggered service request procedure, geographical identifier reporting module 508 may be configured to receive from SGW 108 a modify bearer request message that may comprise a geographical identifier, e.g., via transceiver 520 and/or SGW interface 502. In response to receiving the geographical identifier, geographical identifier reporting module 508 may send the received geographical identifier in an indication of IP-CAN session modification message to PCRF 114 via the transceiver 520 and/or the PCRF interface 506.

In some embodiments, in a location change reporting procedure, geographical identifier reporting module 508 may be configured to receive from SGW 108 a change notification message to indicate a new geographical identifier, e.g., via transceiver 520 and/or SGW interface 502. In response to receiving the new geographical identifier, geographical identifier reporting module 508 may send the geographical identifier in an indication of IP-CAN session modification message to PCRF 114 via the transceiver 520 and/or the PCRF interface 506.

While Figure 5 illustrates the geographical identifier reporting module 508 may be provided in PGW 500, in some other embodiments, geographical identifier reporting module 508 may be provided in or implemented by the one or more processors 510 or a baseband circuitry. While Figure 5 illustrates the transceiver 520, in some embodiments, the transceiver 520 may be implemented by one or more transmitters and/or one or more receivers. While Figure 5 illustrates one or more interfaces, e.g., 502, 504, or 506, in some embodiments, the one or more interfaces or other interfaces may not be required in structure 500 but may be implemented in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 520.

While Figure 5 illustrates an example of a structure that may comprise PGW 500, in some embodiments, the structure 500 may comprise a PCEF, e.g., 112A, that may be provided in PGW 500 to perform one or more processes or functions of PGW 112 and/or PGW 500. In some embodiments, the PCEF may comprise one or more components in PGW 112 and/or PGW 500. For example, PCEF may comprise one or more of processor 510, memory 512, interfaces 502, 504, or 506, geographical identifier reporting module 508, and/or transceiver 520.

Figure 6 illustrates an example of a structure 600 in accordance with some embodiment. In some embodiments, the structure 600 may comprise a P-CSCF entity that may be configured to comprise one or more geographical identifier related aspects as described in the disclosure. In some embodiments, P-CSCF entity 600 may be implemented in an entity, an apparatus, a device, a system, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, P-CSCF entity 600 may be configured to perform one or more processes and/or functions as described with regard to P-CSCF entity 120A in the disclosure.

In some embodiments, P-CSCF entity 600 may include one or more interfaces to interface between P-CSCF entity 600 and one or more other elements in a network.

In some embodiments, P-CSCF entity 600 may include a PGW interface 602 to communicate with, e.g., PGW 112 as described above. For example, the PGW interface 602 may include a SGi interface or any other suitable interface to communicate with PGW 112.

In some embodiments, P-CSCF entity 600 may include a PCRF interface 604 to communicate with, e.g., PCRF 114 as described above. For example, the PCRF interface 604 may include a Rx interface or any other suitable interface to communicate with PCRF 114.

In some embodiments, P-CSCF entity 600 may comprise a processor 610 and/or a memory 612 that may be coupled with each other. P-CSCF entity 600 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of P-CSCF entity 600 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of P-CSCF entity 600 may be distributed among multiple or separate devices.

In some embodiments, processor 610 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor (shared, dedicated, or group), or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof, or any other suitable hardware, software and/or firmware components.

Processor 610 may execute instructions, for example, of an operating system (OS) of

P-CSCF entity 600 and/or of one or more suitable applications. In some embodiments, some or all of the components of P-CSCF entity 600 may be enclosed in a common device and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of P-CSCF entity 600 may be distributed among multiple or separate devices.

In some embodiments, memory 612 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 612 may be configured to store, for example, data and/or instructions for P-CSCF entity 600.

In some embodiments, P-CSCF entity 600 may comprise a geographical identifier requesting module or unit 606 that may be coupled to any other component in P-CSCF entity 600. In some embodiments, during mobile origination session setup, geographical identifier requesting module 606 may be configured to send PCRF 114 with a request for geographical identifier, e.g., an AA-Request message, to retrieve the geographical identifier in response to receiving from UE 102 a SIP invite that may comprise a local number of a callee of UE 102. In some embodiments, geographical identifier requesting module 606 may be configured to obtain the geographical identifier in an AA- Answer message from PCRF 114 via the transceiver 620 and/or the PCRF interface 604.

In some embodiments, P-CSCF entity 600 may comprise a geographical identifier inserting module or unit 608 to insert the geographical identifier in SIP signaling, e.g., the SIP invite, to enable routing decision in one or more downstream IMS entities , e.g., S-CSCF 120C and/or AS 122, and/or interconnected network.

In some embodiments, the geographical identifier requesting module 606 and/or geographical identifier inserting module 608 may be configured to perform one or more processes and/or functions, e.g., as described with regard to P-CSCF 120A, P-CSCF 600 and/or other embodiments in the disclosure.

While Figure 6 illustrates the geographical identifier requesting module 606 and/or geographical identifier inserting module 608 may be provided in P-CSCF entity 600, in some other embodiments, geographical identifier requesting module 606 and/or geographical identifier inserting module 608 may be provided in or implemented by one or more processors 610 or a baseband circuitry. While Figure 6 illustrates geographical identifier requesting module 606 and/or geographical identifier inserting module 608 may be provided in different blocks, in some embodiments, geographical identifier requesting module 606 and/or geographical identifier inserting module 608 may be provided in the same module or unit or processor or baseband circuitry. While Figure 6 illustrates the transceiver 620, in some embodiments, the transceiver 620 may be implemented by one or more transmitters and/or one or more receivers. While Figure 6 illustrates one or more interfaces, e.g., 602 or 604 and/or one or more interfaces for downstream EVIS entity(s), in some embodiments, the one or more interfaces and/or other interfaces may not be required in P-CSCF 600 but may be implemented in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 620.

Figure 7 illustrates an example of a structure 700 in accordance with some embodiment. In some embodiments, the structure 700 may comprise an application server that may be configured to comprise one or more geographical identifier related aspects as described in the disclosure. In some embodiments, AS 700 may be implemented in an entity, an apparatus, a device, a system, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, AS 700 may be configured to perform one or more processes and/or functions as described with regard to AS 122 in the disclosure.

In some embodiments, AS 700 may include one or more interfaces to interface between AS 700 and one or more other elements in a network.

In some embodiments, AS 700 may include a HSS interface 702 to communicate with, e.g., HSS 116 as described above. For example, the HSS interface 702 may include an interface or any other suitable interface to communicate with HSS 116.

In some embodiments, AS 700 may include an interface 704 to communicate with, e.g., CSCF 120 as described above. For example, the interface 704 may include an interface or any other suitable interface to communicate with CSCF 120.

In some embodiments, AS 700 may comprise a processor 710 and/or a memory 712 that may be coupled with each other. AS 700 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of AS 700 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of AS 700 may be distributed among multiple or separate devices.

In some embodiments, processor 710 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor

Processor 710 may execute instructions, for example, of an operating system (OS) of AS 700 and/or of one or more suitable applications. In some embodiments, some or all of the components of AS 700 may be enclosed in a common device and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of AS 700 may be distributed among multiple or separate devices.

In some embodiments, memory 712 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 712 may be configured to store, for example, data and/or instructions for AS 700.

In some embodiments, AS 700 may comprise a geographical identifier requesting module or unit 706 that may be coupled to any other component in AS 700. In some embodiments, during mobile origination session setup, geographical identifier requesting module 706 may be configured to receive a SIP invite from S-CSCF 120C, e.g., via transceiver 720 and/or the interface 704. In some embodiments, geographical identifier requesting module 706 may detect whether a local number is included for a callee of UE 102. In response to detecting that the local number is included in the SIP invite, geographical identifier requesting module 706 may determine that a geographical identifier is required. The geographical identifier requesting module 706 may send to HSS 116 a request that may comprise a user ID of UE 102 (e.g. FMSI, IMEI, FMPU, FMPI) and/or an indication of requesting geographical identifier via transceiver 720 and/or HSS interface 702.

In some embodiments, HSS 116 may send to MME 106 a request that may comprise the user ID of UE (e.g. IMSI, EVIEI, IMPI and/or IMPU) and/or the indication of requesting geographical identifier. MME 106 may inquiry the user's geographical identifier. MME 106 may send the user's geographical identifier to HSS 116 that may further send the geographical identifier to AS 700.

In some embodiments, the geographical identifier requesting module 706 may be configured to perform one or more processes and/or functions, e.g., as described with regard to AS 122, AS 700 and/or other embodiments in the disclosure.

While Figure 7 illustrates the geographical identifier requesting module 706 may be provided in AS 700, in some other embodiments, geographical identifier requesting module 706 may be provided in or implemented by one or more processors 710 or a baseband circuitry. While Figure 7 illustrates the transceiver 720, in some embodiments, the transceiver 720 may be implemented by one or more transmitters and/or one or more receivers. While Figure 7 illustrates one or more interfaces, e.g., 702 or 704, the one or more interfaces and/or other interfaces may not be required in AS 700 but may be implemented in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 720.

Figure 8 illustrates an example of a structure 800 in accordance with some embodiment. In some embodiments, the structure 800 may comprise a HSS that may be configured to comprise one or more geographical identifier related aspects as described in the disclosure. In some embodiments, HSS 800 may be implemented in an entity, an apparatus, a device, a system, a circuitry and/or any other structure using any suitably configured hardware, software and/or firmware. In some embodiments, HSS 800 may be configured to perform one or more processes and/or functions as described with regard to HSS 116 in the disclosure.

In some embodiments, HSS 800 may include one or more interfaces to interface between HSS 800 and one or more other elements in a network.

In some embodiments, HSS 800 may include a MME interface 702 to communicate with, e.g., MME 106 as described above. For example, the MME interface 702 may include a S6a interface or any other suitable interface to communicate with MME 106.

In some embodiments, HSS 800 may include an AS interface 704 to communicate with, e.g., AS 122 as described above. For example, the interface 704 may include an interface or any other suitable interface to communicate with AS 122. In some embodiments, HSS 800 may comprise a processor 810 and/or a memory 812 that may be coupled with each other. HSS 800 may further comprise one or more other suitable hardware components and/or software and/or firmware components. In some embodiments, some or all of the components of HSS 800 may be enclosed in a housing or packaging, and may be interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of HSS 800 may be distributed among multiple or separate devices.

In some embodiments, processor 810 may include, for example, a central processing unit (CPU), a digital signal processor (DSP), a graphic processing unit (GPU), one or more processor cores, a single-core processor, a dual-core processor, a multiple-core processor, a microprocessor, a host processor, a controller, a plurality of processors or controllers, a chip, a microchip, one or more circuits, controller circuitry, a logic unit, a baseband circuitry, a radio frequency (RF) circuitry, a logic unit, an integrated circuit (IC), scheduler circuitry, processor circuitry, memory circuitry, an application-specific IC (ASIC), a processor (shared, dedicated, or group), or any other suitable multi-purpose or specific processor or controller, or one or more circuits or circuitry, and/or any combination thereof, or any other suitable hardware, software and/or firmware components.

Processor 810 may execute instructions, for example, of an operating system (OS) of HSS 800 and/or of one or more suitable applications. In some embodiments, some or all of the components of HSS 800 may be enclosed in a common device and may be

interconnected or operably associated using one or more wired or wireless links. In other embodiments, components of HSS 800 may be distributed among multiple or separate devices.

In some embodiments, memory 812 may include, for example, a random access memory (RAM), a read only memory (ROM), a dynamic RAM (DRAM), a synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile memory, a cache memory, a buffer, a short term memory unit, a long term memory unit, or other suitable memory units or storage units. Memory 812 may be configured to store, for example, data and/or instructions for HSS 800.

In some embodiments, HSS 800 may comprise a geographical identifier requesting module or unit 806 that may be coupled to any other component in HSS 800. In some embodiments, during mobile origination session setup, AS 122 may be configured to receive a SIP invite from S-CSCF 120C. In some embodiments, AS 122 may detect whether a local number for a callee of UE 102 is included in the SIP invite. In response to detecting that the local number is included in the SIP invite, AS 122 may determine that a geographical identifier is required. The geographical identifier requesting module 806 may receive from AS 122 a request that may comprise a user ID of the UE 102 (e.g. IMSI, IMEI, IMPU, IMPI) and/or an indication of requesting geographical identifier via transceiver 820 and/or AS interface 804.

In some embodiments, geographical identifier requesting module 806 may send to MME 106 a request that may comprise the user ID of UE 102 (e.g. IMSI, IMEI, IMPU, IMPI) and/or the indication of requesting geographical identifier via the transceiver 820 and/or the MME interface 802. MME 106 may inquiry the user's geographical identifier. MME 106 may send the user's geographical identifier to geographical identifier requesting module 806 that may further send the geographical identifier to AS 122 via the transceiver 820 and/or the AS interface 804.

In some embodiments, the geographical identifier requesting module 806 may be configured to perform one or more processes and/or functions, e.g., as described with regard to HSS 116, HSS 800 and/or other embodiments in the disclosure.

While Figure 8 illustrates the geographical identifier requesting module 806 may be provided in HSS 800, in some other embodiments, geographical identifier requesting module 806 may be provided in or implemented by one or more processors 810 or a baseband circuitry. While Figure 8 illustrates the transceiver 820, in some embodiments, the transceiver 820 may be implemented by one or more transmitters and/or one or more receivers. While Figure 8 illustrates one or more interfaces, e.g., 802 or 804, in some embodiments, the one or more interfaces and/or other interfaces may not be required in HSS 800 but may be implemented in a network, e.g., 100. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 820.

Figure 9 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 9 may be used to report a geographical identifier in an Attach procedure, e.g., as shown in section 5.3.2.1 of TS 23.401. In some embodiments, a UE, e.g., 120, may register with a network, e.g., E-UTRAN, to receive services that may require registration. For example, the registration may be described as Network Attachment. In some embodiments, a geographical identifier may be reported in the Attach procedure.

In some embodiments, at 902, UE 102 may initiate an Attach procedure, e.g., via an Attach request to eNB 104. In some embodiments, the Attach procedure may comprise one or more processes 1 to 11, e.g., as shown in section 5.3.2.1 or Figure 5.3.2.1-1 of TS 23.401, that may be performed at 902.

In some embodiments, at 904, based on ECGI information of a serving cell for UE 102 that may be obtained from eNB 104, MME 106 may look up a mapping table between a list of one or more ECGIs and one or more geographical identifier to find out a geographical identifier corresponding to the ECGI information. In some embodiments, the mapping table may be stored in a memory, e.g., 212, of MME 106. In some embodiments, MME 106 may send the obtained geographical identifier to SGW 108, e.g., in a create session request message.

In some embodiments, at 906, SGW 108 may be configured to send or forward the geographical identifier to PGW 112/PCEF 112A, e.g., in response to receiving the create session request message and/or the geographical identifier from MME 106. In some embodiments, SGW 108 may send to PGW 112/PCEF 112A the create session request message from MME 106 that may comprise the geographical identifier.

In some embodiments, at 908, PGW 112/PCEF 112A may send the geographical identifier to PCRF 114 in, e.g., an indication of IP-CAN session establishment message, e.g., in response to receiving the create session request message and/or the geographical identifier from SGW 108.

In some embodiments, at 910, PCRF 114 may store the geographical identifier received from PGW 112/PCEF 112A in a memory, e.g., 312, of PCRF 114. In some embodiments, PCRF 114 may respond to PGW 112/PCEF 112A, e.g., the indication of IP-CAN session establishment message, with an acknowledge of IP-CAN session modification message that may comprise a new event trigger, e.g., Location Change (geographical identifier).

In some embodiments, at 912, PGW 112/PCEF 112A may respond to SGW 108, e.g., the create session request message, with a create session response message that may comprise a change reporting action of "Start Reporting Geographical Identifier".

In some embodiments, at 914, SGW 108 may respond to MME 106, e.g., the create session request message, with a create session response message that may comprise the change reporting action of "Start Reporting Geographical Identifier" that may be received from PGW 112/PCEF 112 A. In some embodiments, in response to receiving the change reporting action of "Start Reporting Geographical Identifier, MME 106 may report the geographical identifier corresponding to the ECGI information.

In some embodiments, the Attach procedure may comprise one or more processes 17 to 26 as described in section 5.3.2.1 or Figure 5.3.2.1-1 of TS 23.401, that may be performed at 916.

While Figure 9 illustrate some embodiments of one or more processes that may be used in an Attach procedure, in some embodiments, the Attach procedure may comprise one or more other processes as described in the disclosure.

Figure 10 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 10 may be used to report a geographical identifier in a UE requested packet data network (PDN) connectivity procedure, e.g., as shown in section 5.10.2 of TS 23.401. In some embodiments, a geographical identifier may be reported in the UE requested PDN Connectivity procedure.

In some embodiments, at 1002, UE 120 may send a PDN connectivity request message to MME 106 to establish a secondary PDN connection over a network, e.g., E-UTRAN.

In some embodiments, at 1004, based on ECGI information of a serving cell for UE 102 that may be obtained from eNB 104, MME 106 may look up a mapping table between a list of one or more ECGIs and one or more geographical identifier to find out a geographical identifier corresponding to the ECGI information. In some embodiments, the mapping table may be stored in a memory, e.g., 212, of MME 106. In some embodiments, MME 106 may send the obtained geographical identifier to SGW 108, e.g., in a create session request message.

In some embodiments, at 1006, SGW 108 may be configured to send or forward the geographical identifier to PGW 112, e.g., in response to receiving the create session request message and/or the geographical identifier from MME 106. In some embodiments, SGW 108 may send to PGW 112 the create session request message from MME 106 that may comprise the geographical identifier.

In some embodiments, at 1008, PGW 112 may send the geographical identifier to PCRF 114 in, e.g., an indication of IP-CAN session establishment message, e.g., in response to receiving the create session request message and/or the geographical identifier from SGW 108.

In some embodiments, at 1010, PCRF 114 may store the geographical identifier received from PGW 112 in a memory, e.g., 312, of PCRF 114. In some embodiments, PCRF 114 may respond to PGW 112, e.g., the indication of IP-CAN session establishment message, with an acknowledge of IP-CAN session modification message that may comprise a new event trigger, e.g., Location Change (geographical identifier). In some embodiments, at 1012, PGW 112 may respond to SGW 108, e.g., the create session request message, with a create session response message that may comprise a change reporting action of "Start Reporting Geographical Identifier".

In some embodiments, at 1014, SGW 108 may respond to MME 106, e.g., the create session request message, with a create session response message that may comprise the change reporting action of "Start Reporting Geographical Identifier" that may be received from PGW 112. In some embodiments, in response to receiving the change reporting action of "Start Reporting Geographical Identifier, MME 106 may report the geographical identifier corresponding to the ECGI information.

In some embodiments, the UE requested PDN Connectivity procedure may comprise one or more of processes 7 to 16, e.g., as described in section 5.10.2 or Figure 5.10.2-1 of TS 23.401, that may be performed at 1016.

While Figure 10 illustrate some embodiments of one or more processes that may be used in a UE requested PDN Connectivity procedure, in some embodiments, the UE requested PDN Connectivity procedure may comprise one or more other processes as described in the disclosure.

Figure 11 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 11 may be used to report a geographical identifier in a Tracking Area Update (TAU) procedure, e.g., as shown in section 5.3.3.1 of TS 23.401. In some embodiments, a geographical identifier may be reported in the TAU procedure.

In some embodiments, the TAU procedure may comprise one or more procedures 1 to 7, e.g., as described in section 5.3.3.1 or Figure 5.3.3.1-1 of TS 23.401, that may be performed at 1102. In some embodiments, the TAU procedure may be associated with a MME change, e.g., from an old MME 106o to a new MME 106n, and/or a SGW change, e.g., from an old SGW 108o to a new SGW 108n.

In some embodiments, at 1104, the new MME 106n may send the new SGW 108n a create session request message that may comprise a geographical identifier.

In some embodiments, at 1106, the new SGW 108n may send a create session request message that may comprise the received geographical identifier.

In some embodiments, at 1108, PGW 112 may send the received geographical identifier to PCRF 114 in, e.g., an indication of IP-CAN session establishment message.

In some embodiments, at 1110, PCRF 114 may store the geographical identifier received from PGW 112. In some embodiments, PCRF 114 may respond to PGW 112, e.g., the indication of IP-CAN session establishment message, with an acknowledge of IP-CAN session modification message.

In some embodiments, at 1112, PGW 112 may send a create session response message to the new SGW 108n to respond to the new SGW 108n, e.g., the create session request message from the new SGW 108n, in response to receiving the acknowledge of IP-CAN session modification message from PCRF 114.

In some embodiments, at 1114, the new SGW 108n may send a create session response message to the new MME 106n to respond to the new SGW 108n, e.g., the create session request message from the new SGW 108n.

In some embodiments, the TAU procedure may comprise one or more processes 12 to 19, e.g., as described in section 5.3.3.1 or Figure 5.3.3.1-1 of 23.401, that may be performed at 1116.

While Figure 11 illustrate some embodiments of one or more processes that may be used in a TAU procedure, in some embodiments, the TAU procedure may comprise one or more other processes as described in the disclosure.

Figure 12 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 12 may be used to report a geographical identifier in a SI -based handover procedure, e.g., as shown in section 5.5.1.2.2 of TS 23.401. In some embodiments, a geographical identifier may be reported in the SI -based handover procedure.

In some embodiments, the SI -based handover procedure may comprise one or more procedures 1 to 14b, e.g., as described in section 5.5.1.2.2 or Figure 5.5.1.2.2-1 of TS 23.401, that may be performed at 1202. In some embodiments, the Sl-based handover procedure may be associated with a Sl-based handover, e.g., from a source eNB 104s to a target eNB 104t.

In some embodiments, at 1204, a new MME, e.g., target MME 106t may detect whether there is a change of geographical identifier. For example, the target MME 106 may detect if a geographical identifier is different form another geographical identifier stored in the memory of target MME 106. In some embodiments, in response to detecting a geographical identifier change, e.g.., the geographical identifier is different from the another geographical identifier in the target MME 106. In some embodiments, in response to detecting a geographical identifier change, the target MME 106t may send a create session request message that may comprise the geographical identifier to a new SGW, e.g., target SGW 108t. In some embodiments, at 1206, the target SGW 108t may send to PGW 112 a create session request message that may comprise the geographical identifier in response to receiving the geographical identifier from the target MME 106t.

In some embodiments, at 1208, PGW 112 may send to PCRF 114 the geographical identifier in an indication of IP-CAN session modification message.

In some embodiments, at 1210, PCRF 114 may store the geographical identifier in the memory of PCRF 114. In some embodiments, PCRF 114 may respond to PGW, e.g., the indication of IP-CAN session modification message with an acknowledge of IP-CAN session modification message.

In some embodiments, at 1212, PGW 112 may send a modify bearer response message to the target SGW 108t to respond to the target SGW 108t, e.g., the modify bearer request message from the target SGW 108t.

In some embodiments, at 1214, the target SGW 108t may send a modify bearer response message to the target MME 106t to respond to the target MME 106t, e.g., the modify bearer request message from the MME 106t.

In some embodiments, the SI -based handover procedure may comprise one or more processes 18 to 21b, e.g., as described in section 5.5.1.2.2 and/or Figure 5.5.1.2.2-1 of 23.401 that may be performed at 1216.

While Figure 12 illustrate some embodiments of one or more processes that may be used in a SI -based handover procedure, in some embodiments, the SI -based handover procedure may comprise one or more other processes as described in the disclosure.

Figure 13 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 13 may be used to report a geographical identifier in a UE triggered Service Request procedure, e.g., as shown in section 5.3.4.1 of TS 23.401. In some embodiments, a geographical identifier may be reported in the UE triggered Service Request procedure.

In some embodiments, the UE triggered Service Request procedure may comprise one or more processes 1 to 7, e.g., described in section 5.3.4.1 or Figure 5.3.4.1-1 of 23.401, that may be performed at 1302.

In some embodiments, at 1304, MME 106 may detect if there is a change of geographical identifier. For example, MME 106 may compare a geographical identifier with another geographical identifier stored in the memory of MME 106 to detect if there is a geographical identifier change. In some embodiments, in response to detecting a geographical identifier change, e.g.., the geographical identifier is different from the another geographical identifier in MME 106, MME 106 may send to SGW 108 a modify bearer request message that may comprise the geographical identifier.

In some embodiments, at 1306, SGW 108 may send to PGW 112 a modify bearer request message that may comprise the geographical identifier.

In some embodiments, at 1308, PGW 112 may send to PCRF 114 an indication of

IP-CAN session modification message that may comprise the geographical identifier.

In some embodiments, at 1310, PCRF 114 may store the geographical identifier in the memory of PCRF 1 14. In some embodiments, PCRF 114 may respond to the PGW 112, e.g., the indication of IP-CAN session modification message, with an acknowledge of IP-CAN session modification message.

In some embodiments, at 1312, PGW 112 may respond to SGW 108, e.g., the modify bearer request with a modify bearer response message.

In some embodiments, at 1314, SGW 108 may respond to MME 106, e.g., the modify bearer request with a modify bearer response message.

While Figure 13 illustrate some embodiments of one or more processes that may be used in a UE triggered Service Request procedure, in some embodiments, the UE triggered Service Request procedure may comprise one or more other processes as described in the disclosure.

Figure 14 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, a MME, e.g., 106, 106t, or

106n, may report a new or updated geographical identifier in a Location Change Reporting procedure. In some embodiments, the one or more processes of Figure 14 may be used to report a geographical identifier in a Location Change Reporting procedure. In some embodiments, the one or more processes of Figure 14 may be used in notification of a geographical identifier change.

In some embodiments, PCRF 114 may provide an event trigger for a geographical identifier change reporting to PCEF 112A and/or MME 106, e.g., at an IP-CAN Session Establishment or Modification, e.g., in an Attach procedure, a UE requested PDN

Connectivity procedure, a UE triggered Service Request procedure, a SI -based handover procedure and/or a Bearer Modification procedure or other procedure that may have a geographical identifier change to enable the geographical identifier change reporting from MME 106 to PCRF 114.

In some embodiments, at 1402a, MME 106 may have received an ECGI information update from eNB 104. In some embodiments, at 1402b, MME 106 may look up the updated ECGI in the mapping table to find out a new or an updated geographical identifier. MME 106 may compare a geographical identifier of a user (e.g., UE 102) with an old geographical identifier of the user that may be stored in MME 106. In some embodiments, MME 106 may detect a geographical identifier change, e.g., via the comparison.

In some embodiments, at 1404, if MME 106 has been requested to report one or more location changes to PCRF 114 for UE 102 based on one or more conditions, e.g., as specified in section 5.9.2 of TS 23.401, MME 106 may send a change notification message to SGW 108 to indicate the new or updated geographical identifier. In some embodiments, MME 106 may store the geographical identifier of the UE 102 that may be notified by MME 106, e.g., the change notification message.

In some embodiments, at 1406, SGW 108 may forward the change notification message to PGW 112 that may comprise the geographical identifier of UE 102.

In some embodiments, at 1408, PGW 112 may send the geographical identifier of UE 102 to PCRF 114 in an indication of IP-CAN session modification message.

In some embodiments, at 1410, PCRF 114 may store the geographical identifier of UE 102 that may be received from PGW 112. In some embodiments, at 14010, PCRF 1 14 may respond to PGW 112, e.g., the indication of IP-CAN session modification message, with an acknowledge of IP-CAN session modification message.

In some embodiments, PGW 112 may respond to SGW 108, e.g., the change notification message, with a change notification acknowledgement (Ack) message.

In some embodiments, SGW 108 may respond to MME 106, e.g., the change notification message, with a change notification acknowledgement message.

While Figure 14 illustrates an example of one or more processes relating to geographical identifier reporting by MME 106 in the location change reporting procedure, in some embodiments, the one or more processes may be used by a target MME 106t and/or a new MME 106n. While Figure 14 illustrates SGW 108, in some embodiments, a target SGW 108t and/or a new SGW may perform one or more processes in Figure 14. While Figure 14 illustrates an example of one or more processes relating to geographical identifier reporting in location change reporting procedure, in some embodiments, one or more other processes, e.g., as described in the disclosure, may be used for the geographical identifier reporting.

Figure 15 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, P-CSCF 120 A may perform one or more processes of Figure 15 to retrieve a geographical identifier from PCRF 114, e.g., during a mobile origination (MO) session setup, e.g., for home-routed roaming.

In some embodiments, at 1502, UE 102 may send a session initiation protocol (SIP) invite to P-CSCF 120A in HPLMN 130. In some embodiments, the SIP invite may comprise a local number of a callee of UE 102.

In some embodiments, at 1504, P-CSCF 120A may send an AA-Request message to PCRF 114 in HPLMN 130. In some embodiments, the AA-Request may comprise an indication that a geographical identifier is required. In some embodiments, P-CSCF 120 may use the AA-Request to request for a geographical identifier.

In some embodiments, at 1506, PCRF 114 may answer P-CSCF 120A with an

AA- Answer that may comprise a geographical identifier of UE 102.

In some embodiments, at 1508, P-CSCF 120A may insert the geographical identifier in the SIP signalling, e.g., the SIP invite, to enable a routing decision in one or more downstream FMS entities, e.g., S-CSCF 120C and/or AS 122, and/or the interconnected network. In some embodiments, P-CSCF 120 A may send the SIP invite with the geographical identifier to S-CSCF 120C.

While Figure 15 illustrate some embodiments of one or more processes that may be used to retrieve a geographical identifier from PCRF 114, in some embodiments, one or more other processes in the disclosure may be used.

Figure 16 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, AS 122 may perform one or more processes of Figure 16 to retrieve a geographical identifier from HSS 116 and/or MME 106, e.g., at an IP multimedia subsystem (IMS) session setup.

In some embodiments, at 1602, AS 122 may receive from S-CSCF 120C an SIP invite that may be from UE 102, e.g., as shown in Figure 15.

In some embodiments, at 1604, in response to receiving the SIP invite from S-CSCF 120C, AS 122 may detect if a local number for a callee of UE 102 is included the SIP invite. In response to detecting the local number for the callee in the SIP invite, AS 122 may determine that a geographical identifier for UE 102 is required.

In some embodiments, at 1604, AS 122 may request HSS 1 16 for the geographical identifier. In some embodiments, AS 122 may send to HSS 116 a request message that may comprise a user identifier (ID) of UE 120 and/or an indication of requesting geographical identifier. In some embodiments, examples of the user ID may comprise IMSI, IMEI, IMPU, IMP! In some embodiments, at 1606, HSS 116 may request MME 106 to provide a geographical identifier of the UE 102 to HSS 116. For example, HSS 116 may provide to MME 106 one or more user ID of UE 102, e.g., FMSI, IMEI, IMPI, and/or FMPU, and/or an indication of requesting geographical identifier.

In some embodiments, at 1608, MME 106 may send the geographical identifier of the user, e.g., UE 102, to HSS 116.

In some embodiments, at 1610, HSS 116 may send the obtained geographical identifier to AS 122 in HPLMN 130.

In various embodiments as described in Figure 16 and/or in the disclosure, IMPI can be an IMS! If an IMPI is not an IMSI, HSS 116 may be configured to maintain a mapping between one or more IMPIs and one or more IMSIs.

While Figure 16 illustrates an example of one or more processes relating to retrieving a geographical identifier from HSS 116 and/or MME 106, in some embodiments, AS 122 may perform one or more other processes, e.g., in the disclosure, to retrieving the geographical identifier.

Embodiments described herein may be implemented into a system using any suitably configured hardware, software and/or firmware. Figure 17 illustrates,

for one embodiment, an example system comprising radio frequency (RF) circuitry 1730, baseband circuitry 1720, application circuitry 1710, front end module (FEM) circuitry 1760, memory/storage, one or more antennas 1750, and/or one or more displays, one or more cameras, one or more sensors, and/or one or more input/output (I/O) interfaces, coupled with each other at least as shown. For one embodiment, Figure 17 illustrates example components of a UE device 1700 in accordance with some embodiments.

The application circuitry 1710 may include one or more application processors. For example, the application circuitry 1710 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems to run on the system.

The baseband circuitry 1720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1720 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 1730 and to generate baseband signals for a transmit signal path of the RF circuitry 1730. Baseband processing circuity 1720 may interface with the application circuitry 1710 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1730. For example, in some embodiments, the baseband circuitry 1720 may include a second generation (2G) baseband processor 1720a, a third generation (3G) baseband processor 1720b, a fourth generation (4G) baseband processor 1720c, and/or other baseband processor(s) 1720d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 1720 (e.g., one or more of baseband processors) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 1730. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1720 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1720 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of

modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 1720 may include elements of a protocol stack such as, for example, elements of an E-UTRAN protocol including, for example, physical (PHY), media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), and/or RRC elements. A central processing unit (CPU) 1720e of the baseband circuitry 1720 may be configured to run elements of the protocol stack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. In some

embodiments, the baseband circuitry 1720 may include one or more audio digital signal processor(s) (DSP) 1720f that may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1720 and the application circuitry 1710 may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 1720 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1720 may support communication with an evolved universal terrestrial radio access network (E-UTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1720 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

RF circuitry 1730 may enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 1730 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 1730 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1760 and provide baseband signals to the baseband circuitry 1720. RF circuitry 1730 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1720 and provide RF output signals to the FEM circuitry 1760 for transmission.

In some embodiments, the RF circuitry 1730 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 1730 may include mixer circuitry 1730a, amplifier circuitry 1730b and/or filter circuitry 1730c. The transmit signal path of the RF circuitry 1730 may include filter circuitry 1730c and/or mixer circuitry 1730a.

RF circuitry 1730 may also include synthesizer circuitry 1730d for synthesizing a frequency for use by the mixer circuitry 1730a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1730a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1760 based on the synthesized frequency provided by synthesizer circuitry 1730d.

The amplifier circuitry 1730b may be configured to amplify the down-converted signals. The filter circuitry 1730c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1720 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 1730a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect. In some embodiments, the mixer circuitry 1730a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1730d to generate RF output signals for the FEM circuitry 1760. The baseband signals may be provided by the baseband circuitry 1720 and may be filtered by filter circuitry 1730c. The filter circuitry 1730c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1730a of the receive signal path and the mixer circuitry 1730a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 1730a of the receive signal path and the mixer circuitry 1730a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1730a of the receive signal path and the mixer circuitry 1730a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 1730a of the receive signal path and the mixer circuitry 1730a of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1730 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1720 may include a digital baseband interface to communicate with the RF circuitry 1730.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1730d may be a fractional -N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1730d may be a delta-si gma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 1730d may be configured to synthesize an output frequency for use by the mixer circuitry 1730a of the RF circuitry 1730 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1730d may be a fractional N/N+l synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1720 or the applications processor 1710 depending on the desired output frequency. In some embodiments, a divider control input (e.g., X) may be determined from a look-up table based on a channel indicated by the applications processor 1710.

Synthesizer circuitry 1730d of the RF circuitry 1730 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DP A). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 1730d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1730 may include an IQ/polar converter.

FEM circuitry 1760 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1750, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1730 for further processing. FEM circuitry 1760 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 1730 for transmission by one or more of the one or more antennas 1750.

In some embodiments, the FEM circuitry 1760 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1730). The transmit signal path of the FEM circuitry 1760 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 1730), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1750.

In some embodiments, the UE 1700 comprises a plurality of power saving mechanisms. If the UE 1700 is in an RRC Connected state, where it is still connected to the e B 104 as it expects to receive traffic shortly, then it may enter a state known as

Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device may power down for brief intervals of time and thus save power.

If there is no data traffic activity for an extended period of time, then the UE 1700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The UE 1700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device cannot receive data in this state, in order to receive data, it must transition back to RRC Connected state.

An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

In various embodiments, transmit circuitry, control circuitry, and/or receive circuitry discussed or described herein may be embodied in whole or in part in one or more of the RF circuitry 1730, the baseband circuitry 1720, FEM circuitry 1760 and/or the application circuitry 1710. As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules or units.

In some embodiments, some or all of the constituent components of the baseband circuitry 1720, the application circuitry 1710, and/or the memory/storage may be implemented together on a system on a chip (SOC).

Memory/storage may be used to load and store data and/or instructions, for example, for system. Memory/storage for one embodiment may include any combination of suitable volatile memory (e.g., dynamic random access memory (DRAM)) and/or

non-volatile memory (e.g., Flash memory).

In various embodiments, the I/O interface(s) may include one or more

user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface.

In various embodiments, the one or more sensors may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite.

In various embodiments, the display(s) may include a display (e.g., a liquid crystal display, a touch screen display, etc.).

In various embodiments, the system 1700 may be a mobile computing

device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, etc. In various embodiments, system may have more or less components, and/or different architectures.

As used herein, the term "circuitry" may refer to, be part of, or include

an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules or units. EXAMPLES

Example 1 may include a mobility management entity (MME), comprising: a processor to look up a mapping table between a list of one or more evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (ECGI) list and one or more geographical identifiers for a user equipment (UE) to obtain a first geographical identifier corresponding to a current ECGI; and provide to a serving gateway (SGW) the first geographical identifier in a Create Session Request message; and a memory coupled to the processor to store the geographical identifier obtained from the mapping table.

Example 2 may include the subject matter of Example 1 or any other examples described herein, wherein the processor is further to, in response to receiving an updated ECGI, look up in the mapping table to obtain an updated geographical identifier corresponding to the updated ECGI.

Example 3 may include the subject matter of Example 2 or any other examples described herein, wherein the processor is further to: compare the updated geographical identifier with the first geographical identifier to detect a geographical identifier change, wherein the first geographical identifier is stored in a mobile management (MM) context of the UE in the memory.

Example 4 may include the subject matter of Example 3 or any other examples described herein, wherein the processor is further to: report the updated geographical identifier in response to detecting the geographical identifier change, wherein the geographical identifier change is to indicate the updated geographical identifier is different from the first geographical identifier.

Example 5 may include the subject matter of any one of Examples 2 to 4 or any other examples described herein, wherein the processor is further to: report the updated geographical identifier in a location change reporting procedure.

Example 6 may include the subject matter of any one of Examples 1 to 5 or any other examples described herein, wherein the processor is further to: in response to receiving a geographical identifier request from a home subscriber server (HSS), provide to the HSS a second geographical identifier based on the one or more user identifiers (IDs) in the geographical identifier request.

Example 7 may include the subject matter of any one of Examples 1 to 6 or any other examples described herein, wherein the one or more user IDs comprise one or more of an international mobile subscriber identity (EVISI), an international mobile equipment identity (EVIEI), IP Multimedia Public Identity (IMPU) and/or an IP Multimedia Private Identity (IMPI).

Example 8 may include the subject matter of any one of Examples 2 to 7 or any other examples described herein, wherein the processor is further to: provide to the SGW the updated geographical identifier in a modify bearer request message.

Example 9 may include the subj ect matter of any one of Examples 2 to 7 or any other examples described herein, wherein the processor is further to: provide to SGW the updated geographical identifier in a change notification message in response to the geographical identifier change.

Example 10 may include the subject matter of any one of Examples 2 to 7 or any other examples described herein, wherein the processor is further to: provide the updated geographical identifier to a policy and charging rules function (PCRF) entity via the SGW in response to obtaining a change reporting action of Start Reporting geographical identifier in a modify or create session response message from the SGW.

Example 11 may include the subject matter of any one of Examples 1 to 10 or any other examples described herein, wherein the processor is further to: provide the first geographical identifier to the SGW in an attach procedure, a UE requested public data network (PDN) connectivity procedure, a SI - procedure or a UE triggered Service Request procedure.

Example 12 may include a policy and charging rules function (PCRF) entity, comprising: a processor to provide an event trigger to a policy and charging enforcement function (PCEF) entity to trigger a geographical identifier change report from the PCEF entity to the PCRF entity, and to obtain a geographical identifier of a user equipment (UE) in the geographical identifier change report from the PCEF entity; and a memory coupled to the processor to store the geographical identifier from the PCEF entity.

Example 13 may include the subject matter of Example 12 or any other examples described herein, wherein the processor is further to: provide the event trigger to the PCEF at an internet protocol-connectivity access network (IP-CAN) session establishment or modification procedure.

Example 14 may include the subject matter of any one of Examples 12 to 13 or any other examples described herein, wherein the processor is further to: provide the event trigger to the PCEF in an attach procedure, a UE requested public data network (PDN) connectivity procedure, or a tracking area update (TAU) procedure.

Example 15 may include the subject matter of any one of Examples 12 to 14 or any other examples described herein, wherein the processor is further to: obtain an updated geographical identifier of the UE from the PCEF in one or more of the attach procedure, the UE requested PDN connectivity, the tracking area update (TAU) procedure, a SI -based handover procedure, a user location reporting procedure, a UE triggered Service Request procedure, a SI -based handover procedure or a bearer modification procedure.

Example 16 may include the subject matter of any one of Examples 12 to 15 or any other examples described herein, wherein the processor is further to: provide a requested geographical identifier to a proxy call session control function (P-CSCF) entity or an application server (AS) in response to receiving a request from the P-CSCF entity or the AS, wherein the AS and the P-CSCF entity are in a home public land mobile network (FIPLMN).

Example 17 may include the subject matter of any one of Examples 12 to 16 or any other examples described herein, wherein the processor is further to: obtain the requested geographical identifier for the P-CSCF or the AS based on one or more user identities (IDs) in the request.

Example 18 may include the subject matter of any one of Examples 12 to 17 or any other examples described herein, wherein the processor is further to: obtain from PGW an updated geographical identifier corresponding to an updated ECGI.

Example 19 may include the subject matter of any one of Examples 12 to 18 or any other examples described herein, wherein the processor is further to: obtain an indication of internet protocol-connectivity access network (IP-CAN) session establishment or modification message in geographical identifier change report from PCEF entity.

Example 20 may include the subject matter of any one of Examples 12 to 19 or any other examples described herein, wherein the processor is further to: respond to the indication of IP-CAN session establishment or modification message from PCEF entity with an acknowledge of the indication of IP-CAN session establishment or modification message.

Example 21 may include a machine-readable medium having instructions, stored thereon, that, when executed cause a policy and charging rules function (PCRF) to: receive a geographical identity of a user equipment (UE) from a public data network (PDN) gateway (PGW); store the geographical identity from the PGW; and send to the PGW an

acknowledge message that comprise an event trigger to request the PGW to provide a geographical identifier change report.

Example 22 may include the machine-readable medium of example 21 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: receive the geographical identity from an indication of internet protocol-connectivity access network (IP-CAN) session establishment or modification message from PGW.

Example 23 may include the machine-readable medium of example 21 or 22 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: send the event trigger to the PGW in an acknowledge of the indication of IP-CAN session establishment or modification message.

Example 24 may include the machine-readable medium of one or more of example 21 to 23 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: obtain an updated geographical identity of the UE from the geographical identity change report from the PGW.

Example 25 may include the machine-readable medium of one or more of example 21 to 24 having instructions, stored thereon, that, when executed cause the PCRF further to: provide the event trigger to the PGW in an attach procedure, a UE requested public data network (PDN) connectivity procedure, a tracking area update (TAU) procedure, or a location change reporting procedure.

Example 26 may include the machine-readable medium of one or more of example 21 to 25 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: obtain the updated geographical identifier of the UE from the PGW in one or more of the attach procedure, the UE requested PDN connectivity, the tracking area update (TAU) procedure, the user location reporting procedure, a UE triggered Service Request procedure, a SI -based handover procedure or a bearer modification procedure.

Example 27 may include the machine-readable medium of one or more of example 21 to 26 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: obtain from the PGW the updated geographical identifier corresponding to an updated evolved universal terrestrial radio access network (E-UTRAN) cell global identifier (ECGI).

Example 28 may include the machine-readable medium of one or more of example 21 to 27 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: provide a requested geographical identifier to a proxy call session control function (P-CSCF) entity or an application server (AS) in response to receiving a request from the P-CSCF entity or the AS, wherein the AS and the P-CSCF entity are in a same home public land mobile network (UPLMN) as the PCRF.

Example 29 may include the machine-readable medium of one or more of example 21 to 28 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: obtain the requested geographical identifier for the P-CSCF or the AS based on one or more user identities (IDs) in the request, wherein the one or more user IDs comprise one or more of an international mobile subscriber identity (EVISI), an international mobile equipment identity (IMEI), an internet protocol (IP) multimedia public identity (EVIPU) and an IP multimedia private identity (EVIPI).

Example 30 may include the machine-readable medium of one or more of example 21 to 29 or any other examples described herein, having instructions, stored thereon, that, when executed cause the PCRF further to: provide an AA-answer that comprise the requested geographical identifier in response to receiving the request from P-CSCF in an AA-request.

Example 31 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method or a MME or PCRF entity described in or related to any of examples 1-20 and/or any other process described herein.

Example 32 may include a method of communicating in a wireless network as shown and described herein and/or comprising one or more elements of a method, a MME or a PCRF entity described in or related to any of examples 1-30 and/or any other method or process described herein.

Example 33 may include a wireless communication system as shown and described herein and/or comprising one or more elements of a MME or a PCRF entity described in or related to any of examples 1-20 and/or any other embodiments described herein.

Example 34 may include a wireless communication device as shown and described herein and/or comprising one or more elements of a MME or a PCRF entity described in or related to any of examples 1-20 and/or any other embodiments described herein.

Example 35 may include a P-CSCF, comprising: a processor to request for a user's geographical identifier from PCRF entity in a same UPLMN in response to receiving a SIP invite message from a UE to indicate the user's geographical identifier information is required.

Example 36 may include an AS, comprising: a processor to request for a user's geographical identifier information from PCRF entity in a same UPLMN in response to receiving a SIP invite message from a UE to indicate that the user's geographical identifier information is required. Example 37 may include the AS of example 36 or any other examples described herein, wherein the processor is to request the user's geographical identifier from an HSS.

Example 38 may include a HSS, comprising: a processor to request for a user's geographical identifier information from a MME in response to receiving a request for the user's geographical identifier information from an AS, and to send to the AS the user's geographical identifier information obtained from the MME.

Example 39 may include a policy and charging rules function (PCRF)

comprising: means for receiving a geographical identity of a user equipment (UE) from a public data network (PDN) gateway (PGW); means for storing the geographical identity from the PGW; and means for sending to the PGW an acknowledge message that comprise an event trigger to request the PGW to provide a geographical identifier change report.

Example 40 may include the PCRF of Example 39, further comprising: means for receiving the geographical identity from an indication of internet protocol-connectivity access network (IP-CAN) session establishment or modification message from PGW.

Example 41 may include the PCRF of Example 31 or 32, further comprising: means for sending the event trigger to the PGW in an acknowledge of the indication of IP-CAN session establishment or modification message.

Example 42 may include the PCRF of one or more of Examples 31 to 33, further comprising: means for obtaining an updated geographical identity of the UE from the geographical identity change report from the PGW.

Example 43 may include the PCRF of one or more of Examples 31 to 34 further comprising: means for providing the event trigger to the PGW in an attach procedure, a UE requested public data network (PDN) connectivity procedure, a tracking area update (TAU) procedure, or a location change reporting procedure.

It should be understood that many of the functional units described in this specification have been labeled as modules or units, in order to more particularly emphasize their implementation independence. For example, a module or unit may be implemented as a hardware circuit comprising custom VLSI circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module or unit may also be implemented in programmable hardware devices such as field

programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules or units may also be implemented in software for execution by various types of processors. An identified module or unit of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executable code of an identified module or unit need not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module or unit and achieve the stated purpose for the module or unit.

A module or unit of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules or units, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules or units may be passive or active, including agents operable to perform desired functions.

Reference throughout this specification to "an example" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present disclosure. Thus, appearances of the phrases "in an example" in various places throughout this specification are not necessarily all referring to the same embodiment.

As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as an equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present disclosure may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as equivalents of one another, but are to be considered as separate and autonomous representations of the present disclosure.

Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of search spaces, to provide a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the disclosure may be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.

While the forgoing examples are illustrative of the principles of the present disclosure in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation may be made without the exercise of inventive faculty, and without departing from the principles and concepts of the disclosure. Accordingly, it is not intended that the disclosure be limited, except as by the claims set forth below.

While Figures 9-16 are illustrated to comprise a sequence of processes, the methods in some embodiments may perform illustrated processes in a different order.

While certain features of the disclosure have been described with reference to embodiments, the description is not intended to be construed in a limiting sense. Various modifications of the embodiments, as well as other embodiments of the disclosure, which are apparent to persons skilled in the art to which the disclosure pertains are deemed to lie within the spirit and scope of the disclosure.

Claims

CLAIMS What is claimed is:

1. A mobility management entity (MME), comprising:

a processor to:

look up a mapping table between one or more evolved universal terrestrial radio access network (E-UTRAN) cell global identifiers (ECGIs) and one or more geographical identifiers of a user equipment (UE) to obtain a first geographical identifier corresponding to a current ECGI, and

provide to a serving gateway (SGW) the first geographical identifier in a Create Session Request message; and

a memory coupled to the processor to store the first geographical identifier obtained from the mapping table.

2. The MME of claim 1, wherein the processor is further to:

in response to receiving an updated ECGI, look up in the mapping table to obtain an updated geographical identifier corresponding to the updated ECGI.

3. The MME of claim 2, wherein the processor is further to:

compare the updated geographical identifier with the first geographical identifier to detect a geographical identifier change, wherein the first geographical identifier is stored in a mobile management (MM) context of the UE in the memory.

4. The MME of claim 3, wherein the processor is further to:

report the updated geographical identifier in response to detecting the geographical identifier change, wherein the geographical identifier change is to indicate that the updated geographical identifier is different from the first geographical identifier.

5. The MME of claim 3 or 4, wherein the processor is further to:

report the updated geographical identifier in a location change reporting procedure.

6. The MME of any one of claims 1 to 3, wherein the processor is further to:

in response to receiving a geographical identifier request from a home subscriber server (HSS), provide to the HSS a second geographical identifier based on the one or more user identifiers (IDs) in the geographical identifier request.

7. The MME of claim 6, wherein the one or more user IDs comprise one or more of an international mobile subscriber identity (EVISI), an international mobile equipment identity (EVIEI), IP Multimedia Public Identity (IMPU) and/or an IP Multimedia Private Identity (IMPI).

8. The MME of any one of claims 2 to 3, wherein the processor is further to:

provide to the SGW the updated geographical identifier in a modify bearer request message.

9. The MME of any one of claims 2 to 3, wherein the processor is further to:

provide to the SGW the updated geographical identifier in a change notification message in response to the geographical identifier change.

10. The MME of any one of claims 2 to 3, wherein the processor is further to:

provide the updated geographical identifier to a policy and charging rules function

(PCRF) entity via the SGW in response to obtaining a change reporting action of a Start Reporting geographical identifier in a modify or create session response message from the SGW.

11. The MME of any one of claims 1 to 3, wherein the processor is further to:

provide the first geographical identifier to the SGW in an attach procedure, a UE requested public data network (PDN) connectivity procedure, a SI - procedure or a UE triggered Service Request procedure.

12. A policy and charging rules function (PCRF) entity, comprising:

a processor to provide an event trigger to a policy and charging enforcement function (PCEF) entity to trigger a geographical identifier change report from the PCEF entity to the PCRF entity, and to obtain a geographical identifier of a user equipment (UE) in the geographical identifier change report from the PCEF entity; and

a memory coupled to the processor to store the geographical identifier from the PCEF entity.

13. The PCRF entity of claim 12, wherein the processor is further to:

provide the event trigger to the PCEF as part of an internet protocol-connectivity access network (IP-CAN) session establishment or modification procedure.

14. The PCRF entity of claim 12, wherein the processor is further to:

provide the event trigger to the PCEF in an attach procedure, a UE requested public data network (PDN) connectivity procedure, or a tracking area update (TAU) procedure

15. The PCRF entity of claim 14, wherein the processor is further to:

obtain an updated geographical identifier of the UE from the PCEF in one or more of the attach procedure, the UE requested PDN connectivity, the tracking area update (TAU) procedure, a SI -based handover procedure, a user location reporting procedure, a UE triggered Service Request procedure, a SI -based handover procedure or a bearer modification procedure.

16. The PCRF entity of any one of claims 12 to 15, wherein the processor is further to: provide a requested geographical identifier to a proxy call session control function

(P-CSCF) entity or an application server (AS) in response to receiving a request from the P-CSCF entity or the AS, wherein the AS and the P-CSCF entity are in a home public land mobile network (HPLMN).

17. The PCRF entity of claim 15, wherein the processor is further to:

obtain the requested geographical identifier for the P-CSCF or the AS based on one or more user identities (IDs) in the request.

18. The PCRF entity of any one claims 12 to 15, wherein the processor is further to: obtain from a packet gateway (PGW) an updated geographical identifier corresponding to an updated ECGI.

19. The PCRF entity of any one of claims 12 to 15, wherein the processor is further to: obtain an indication of internet protocol-connectivity access network (IP-CAN) session establishment or modification message in a geographical identifier change report from the PCEF entity.

20. The PCRF entity of any one of claims 12 to 15, wherein the processor is further to: respond to the indication of IP-CAN session establishment or the modification message from the PCEF entity with an acknowledge of the indication of IP-CAN session establishment or modification message.

21. A machine-readable medium having instructions, stored thereon, that, when executed cause a policy and charging rules function (PCRF) to:

receive a geographical identity of a user equipment (UE) from a public data network (PDN) gateway (PGW);

store the geographical identity from the PGW; and

send to the PGW an acknowledge message that comprises an event trigger to request the PGW to provide a geographical identifier change report.

22. The machine-readable medium of claim 21 having instructions, stored thereon, that, when executed cause the PCRF further to:

receive the geographical identity from an indication of internet protocol-connectivity access network (IP-CAN) session establishment or modification message from the PGW.

23. The machine-readable medium of claim 22 having instructions, stored thereon, that, when executed cause the PCRF further to:

send the event trigger to the PGW in an acknowledge of the indication of IP-CAN session establishment or modification message.

24. The machine-readable medium of any one of claims 21 to 23 having instructions, stored thereon, that, when executed cause the PCRF further to:

obtain an updated geographical identity of the UE from the geographical identity change report from the PGW.

25. The machine-readable medium of any one of claims 21 to 23 having instructions, stored thereon, that, when executed cause the PCRF further to:

provide the event trigger to the PGW in an attach procedure, a UE requested public data network (PDN) connectivity procedure, or a tracking area update (TAU) procedure, or a location change reporting procedure.