AREAS FOR PUBLIC DATA NETWORK CONNECTION

Cross Reference to Related Applications

The present application claims priority to PCT Patent Application No.

PCT/CN2015/094011, filed on November 6, 2015, the entire specification of which is hereby incorporated by reference in its entirety.

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 (3GPP) 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 illustrates a schematic block diagram of an example of a mobility management entity (MME) in accordance with various embodiments;

Figure 3 illustrates a schematic block diagram of an example of a policy and charging rules function (PCRF) entity in accordance with various embodiments.

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

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

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

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

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

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

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

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

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

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

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

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

Figure 16 schematically illustrates an example 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.

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, steps, processes, 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, in accordance with some embodiments.

In some embodiments, UE 102 may communication with eNB 104 via, e.g., a Uu interface or any other suitable interface. The eNB 104 may communicate with a mobility management entity (MME) 106 via, e.g., a Sl-MME interface or any other suitable interface. The eNB 104 may further communicate with a serving gateway (S-GW) 108 via, e.g., a Sl-u interface or any other suitable interface.

The SGW 108 may communicate with a Serving General Packet Radio Service (GPRS) 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. The SGW 108 may further communicate with a public data network (PDN) gateway (P-GW) 112, e.g., via a S5/S8 interface or any other suitable interface.

The PGW 112 may further 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 a policy and charging control element or entity. The MME 106 may further communicate with a home subscriber server (HSS) 116, e.g., via an interface S6a or any other suitable interface. The MME 106 may further communicate with the SGSN 110, e.g., via an interface S3 or any other suitable interface.

In some embodiments, MME 106 may include, for example, a processor and/or a memory, e.g., central processing unit (CPU), a digital signal processor (DSP), 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 logic unit, an integrated circuit (IC), a controller, controller circuitry, scheduler circuitry, processor circuitry, memory circuitry, an application- specific IC (ASIC), or any other suitable multi-purpose or specific processor or controller, or any other suitable hardware, software and/or firmware components. 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. The processor may execute instruction, for example, of an OS of MME 106 and/or of one or more suitable applications.

In some embodiments, a LTE system may support a presence reporting area (PRA) for a PDN connection. A PRA may comprise an area to report UE presence within that area due to one or more policy control and/or charging reasons. In some embodiments, in E-UTRAN, a presence reporting area may comprise one or more neighbor or non-neighbor tracking areas, or eNBs and/or cells.

In some embodiments, MME 106 may be configured to indicate a MME ID and/or a PRA list in response to internet protocol-connectivity access network (IP-CAN) session establishment and/or modification of UE 102. In some embodiments, the PRA list may comprise, e.g., one or more PRAs or PRA IDs under the MME/MME ID. In some embodiments, the MME ID may comprise an ID, e.g., Globally Unique MME Identifier (GUMMEI), of MME 106 that may currently serve UE 102. In some embodiments, MME 106 may provide the PRA list that may be configured for MME 106 and/or the MME ID of MME 106 to PCRF 114 via SGW 108 and/or PGW 112. In some embodiments, the PRA list may comprise one or more PRAs and/or PRA IDs under the MME 106 or the MME ID.

In some embodiments, PCRF 114 may be configured to obtain PRA related information for a UE, e.g., UE 102, based on the MME ID and/or the PRA list from MME 106. PCRF 114 may be configured to provide the PRA related information, e.g., for a PDN connection of UE 102, to a policy and charging enforcement function (PCEF) entity 112A and/or PGW 112 and/or to

MME 106 via PGW 112 and SGW 108. In some embodiments, the PRA related information may comprise a PRA list that may be subscribed by UE 102. In some embodiments, the PRA related information may comprise a list of one or more PRA elements associated with each PRA/PRA ID in the PRA list.

In some embodiments, PCRF 114 may not transfer the list of PRA elements associated with each PRA/PRA ID to the PCEF 112A and/or to MME 106 to reduce a size of a message that may comprise the PRA related information, e.g., a list of PRAs or PRA ID(s) and/or related PRA element(s) for each PRA.

In some embodiments, PCRF 114 may be configured to have knowledge of which MME has been aware of the list of PRA elements for the PRA ID(s) under the MME's coverage. In some embodiments, PCRF 114 may send the PRA IDs subscribed for UE 102 to the PCEF 112A and/or to MME 106 via PGW 112 and SGW 108 without including the list of PRA elements for each of the PRAs/PRA IDs in response to knowing that MME 106 has been aware of the list of PRA elements associated with each PRA/PRA ID.

In some embodiments, PCRF 114 may be configured to transfer to the PCEF 112A and/or the MME 106 one or more PRA related information that may be used by MME 106. In some embodiments, PCRF 114 may not transfer the list of one or more PRA elements associated with each PRA/PRA ID to the PCEF 112A of PGW 112 and/or to MME 106 via PGW 112 and SGW 108, in response to determining that the list of one or more PRA elements may not be used by MME 106.

In some embodiments, MME 106 may be configured to explicitly indicate whether the MME 106 may receive all PRA related information belonging to UE 102 in the whole operator's network, e.g., the list of PRA elements associated with each PRA/PRA ID. In some

embodiments, MME 106 may be configured to explicitly indicate to PCRF 114, e.g., via PGW 112 and/or SGW 108, whether the MME 106 may receive the list of PRA elements associated with each PRA/PRA ID.

In some embodiments, MME 106 may be configured to explicitly indicate that MME 106 may not receive the list of PRA elements associated with each PRA/PRA ID in response to being configured with the list of PRA elements associated with each PRA/PRA ID. In some embodiments, PCRF 114 may send the PRA ID(s) for a PDN connection of UE 102 to the PCEF 112A in PGW 112 and/or to MME 106 via PGW 112 and SGW 108 without the list of PRA elements associated with each PRA/PRA ID in response to receiving the indication from MME 106 that MME 106 may not use the list of PRA elements associated with each PRA/PRA ID.

In some embodiments, PCRF 114 may be configured to maintain a mapping table between a set of one or more MME IDs and a PRA list configured for each MME. For example, the mapping table may comprise one or more MME IDs and the PRA list under each MME, e.g., 106. In some embodiments, PCRF 114 may be configured to maintain the mapping table between the one or more MME IDs and the PRA list corresponding to each MME/MME ID. In some embodiments, PCRF 114 may comprise a memory to store the mapping tables. In some embodiments, PCRF 114 may know, from MME 106, a MME ID (e.g., Globally Unique MME Identifier (GUMMEI)) of MME 106 that may currently serve a subscriber, e.g., UE 102, e.g., in internet protocol-connectivity access network (IP-CAN) session establishment and/or modification procedure. In some embodiments, in response to knowing the MME ID of MME 106, PCRF 114 may look up the mapping table to obtain the PRA list under MME 106.

In some embodiments, MME 106 may be configured to send, to PCRF 114, a PRA list, e.g. one more PRAs/PRA IDs configured for MME 106, via PGW 112 and/or SGW 108. In some embodiments, PCRF 114 may not maintain the mapping table between a MME ID for a MME and a PRA list under MME 106.

In some embodiments, PCRF 114 may filter the PRA list relating to MME 106 to obtain a filtered PRA list for UE 102 based on, e.g., subscription information of UE 102. In some embodiments, PCRF 114 may find out the filtered PRA list for UE 102 from the PRA list for MME 106 based on subscription information of UE 102. In some embodiments, PCRF 114 may send to the PCEF 112A of PGW 112 the filtered PRA list for UE 102 and/or the list of one or more PRA elements associated with each PRA or PRA ID in the filtered list. In some embodiments, PCRF 114 may be configured to send one or more event triggers to PCEF 112A of PGW 112 and/or to MME 106 via the PGW 112 and/or the SGW 108, e.g., as described below. In some embodiments, a PRA and/or a PRA ID may further be mapped to one or more PRA elements, e.g., one or more policy and charging control (PCC) related IP-CAN bearers and/or one or more IP-CAN session related policy information, or one or more other PRA elements associated with each PRA/PRAID. In some embodiments, a PRA element may comprise one or more as configured in Table 6.4 of 3GPP specification 23.203. In some embodiments, PCRF 114 may store a list of one or more PRA elements associated with each PRA/PRA ID.

Table 6.4: PCC related IP-CAN bearer and IP-CAN session related policy information

In some embodiments, eNB 104 may be 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 3GPP LTE network such as E-UTRAN, 3GPP LTE-A network, 4G network, 4.5G network, a 5G network 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 (MIMO) 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 MIMO (SU-MIMO), multi-user MIMO (MU-MIMO), close loop MIMO, open loop MIMO, full-dimension MIMO (FD-MIMO) or variations of smart antenna processing.

In some embodiments, eNB 104 may include a controller. The controller may be coupled with a transmitter and a receiver and/or one or more communications modules or units in eNB 104. In some embodiments, the transmitter and/or the receiver 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 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, the transmitter and/or the receiver may be elements or modules of a transceiver circuitry.

In some embodiments, the controller of eNB 104 may control one or more functionalities of eNB 104 and/or control one or more communications performed by eNB 104. In some embodiments, controller 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. Controller 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 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. UE 102 may communicate 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. The transmitter of UE 102 may transmit signals to eNB 104 via one or more antennas. The receiver of UE 102 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/or the transmitter of UE 102. In some embodiments, 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.

For example, 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 eNB 104 and/or UE 102 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 eNB 104 and/or UE 102 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 and/or 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 antenna 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 PRA device, a handheld PRA device, an on-board device, an off- board device, a hybrid device (e.g., combining cellular phone functionalities with PRA 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.

While one or more examples of eNB 104 and/or UE 102 has been described with regard to Figure 1, eNB 104 and/or UE 102 may each comprise one or more radio modules or units (not shown) 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 Figure 1 illustrates examples of one or more apparatus and/or systems in the network architecture 100, one or more other apparatus and/or systems may be used in a network.

Figure 2 illustrates an example of a mobility management entity (MME) 200 in accordance with some embodiments. In some embodiments, MME 200 may be configured to manage one or more PRA related aspects as described in the disclosure. In some embodiments, 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/or one or more other apparatus in a network, e.g., as shown in Figure 1.

In some embodiments, MME 200 may include an eNB interface 202 to communicate with eNB 104. For example, eNB interface 202 may include an S I -MME interface to communicate with eNB 104, e.g., according to an S I Application protocol (AP) (S1AP).

In some embodiments, MME 200 may include a HSS interface 206 to communicate with 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 S-GW interface 204 to communicate with SGW 108. For example, SGW interface 204 may include a S l l 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 to the processor 210. 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 some 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, a baseband 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, or one or more circuits or circuitry, and/or any combination thereof. Processor 210 may executes instructions, for example, of an operating system (OS) of MME 200 and/or of one or more suitable applications.

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 or storage units. In some embodiments, memory 212 may be used to store data and/or instructions for MME 200, e.g., MME information and/or PRA related information and/or processes as described herein. For example, the memory 212 may store the MME ID, the PRA related information, e.g., the PRA list associated with the MME ID, and/or the list of PRA elements associated with each PRA/PRA ID, a mapping table between the MME ID and the PRA list, and/or a mapping table between one or more PRA elements and each PRA/PRA ID, and/or one or more instructions and/or associated data and/or processes as described herein.

In some embodiments, MME 200 may comprise a MME ID/PRA related information reporting or providing module or unit (hereinafter, "PRA module 208") that may be configured to manage and/or provide MME information and/or a PRA list under MME 200 and/or the MME ID. In some embodiments, the PRA module 208 may be configured to provide a MME ID of the MME 200 and/or a PRA list that may comprise one or more PRAs/PRA IDs under or in a coverage of MME 200 to PGW 112, e.g., PCEF 112A via SGW 108, as shown in Figure 1. In some embodiments, the PCEF 112A of PGW 112 may be configured to send the MME ID and/or the PRA list to PCRF 114. In some embodiments, MME 200 may report or provide the MME information and/or the PRA list and/or other PRA related information, e.g., as described below or in other embodiments in the disclosure.

In some embodiments, the PRA module 208 may send the MME ID and/or the PRA list to PCEF 112A/PGW 112 through SGW 108, e.g., via the transceiver 220. In some embodiments, in response to a change in MME and/or PRA list, e.g., in response to a new MME being used, the PRA module 208 in the new MME may be configured to report a new MME ID and/or a new PRA list relating to the new MME to PCRF 114 via PGW 112/PCEF 112A and SGW 108, e.g., via the transceiver 220 and/or the SGW interface 204.

In some embodiments, PRA module 208 may be configured to detect if there is a PRA list/PRA change relating to a UE's PDN connection. In some embodiments, PRA module 208 may be configured to report the PRA list/PRA change to PGW 112/PCEF 112A via SGW 108, e.g., through transceiver 220. PCEF 112A in PGW 112 may further report the PRA list/PRA change from MME 106 to PCRF 114.

In some embodiments, the PRA module 208 may report the MME/MME ID change reporting and/or PRA list change reporting and/or the PRA change reporting in a SI -based handover procedure, a tracking area update (TAU) procedure, a service request procedure and/or a location change reporting procedure, e.g., as described in 3GPP specification TS 23.401.

In some embodiments, memory 212 may be configured to store MME information, e.g., a MME ID, and/or PRA related information, e.g., a PRA list under the MME ID and/or one or more PRA elements associated with each PRA/PRA ID in the PRA list. In some embodiments, the memory 212 may be configured to store a mapping table between the MME ID and/or the PRA list under the MME ID. For example, the PRA list may comprise a PRA list for one or more PRAs associated with the MME ID. In some embodiments, memory 212 may be configured to store a mapping table between the one or more PRA elements and each PRA/PRA ID in the PRA list. In some embodiments, the PRA module 208 may be configured to report the MME information and/or the PRA list in a Create Session Request or a Modify Bearer Request to PCEF 112A/PGW 112 via SGW 108, e.g., through the transceiver 220 and/or SGW interface 204. The PGW 112/PCEF 112A may be configured to send the MME information and/or the PRA list to PCRF 114.

In some embodiments, the PRA module 208 may be configured to indicate whether MME 200 is to receive the list of PRA elements associated with each PRA/PRA ID from PCRF 114 via PGW 112/PCEF 112A and/or SGW 108.

In some embodiments, one or more PRA reporting messages on an interface, e.g., SI 1, S5/S8 and/or Gx may be enhanced. For example, for a single PRA for each PDN connection for a UE, e.g., in 3GPP specification TS 29.274, a PRA related information reporting may comprise a PRA ID for the PRA and an indication of whether the UE is inside or outside of the PRA from PRA module 208 of MME 200 to PGW 112/PCEF 112A via SGW 108. In some embodiments, PRA module 208 may report the PRA ID if UE 102 is inside or outside of the PRA, e.g., for 3GPP specification TS 29.274 that may support a PRA for each PDN connection. In some embodiments, for one or more PRAs under a MME, e.g., MME 200, for a PDN connection, UE 102 may be inside of a PRA or outside of any PRA in the one or more PRAs. In some embodiments, PRA module 208 may be configured to report PRA related information, e.g., a PRA list that may comprise a PRA ID of a PRA, in which UE 102 may be currently located, in response to indicating that UE 102 is in a PRA.

Contrarily, in some embodiments, PRA module 208 may be configured to indicate in PRA related information that UE 102 is outside of any PRA without reporting any PRA ID in response to detecting that UE 102 is outside of any PRA.

In some embodiments, the PRA related information may be reported based on one or more of Sl-based handover, TAU or location change reporting, e.g., as described in 3GPP

specification TS 23.401.

In some embodiments, MME 200 may be configured to perform one or more processes and/or functions as described with regard to MME 106 in the disclosure. In some embodiments, MME 200 may be configured to comprise one or more PRA related aspects as described in the disclosure.

While Figure 2 illustrates the PRA module 208 may be provided in MME 200, in some other embodiments, the PRA module 208 may be provided in or implemented by the processor 210. 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, the one or more interfaces 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. While Figure 2 illustrates an example of transceiver 220, in some embodiments, a data/signal exchange between MME 200 and/or SGW 108 may not use transceiver 220 but may be implemented via, e.g., IP

connection(s), etc.

Figure 3 illustrates an example system in accordance with some embodiments.

For one embodiment, Figure 3 illustrates example components of a PCRF entity 300 in accordance with some embodiments. In some embodiments, the PCRF entity 300 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, the PCRF entity 300 may be configured to comprise one or more PRA related aspects as described in the disclosure. In some embodiments, PCRF entity 300 may be configured to perform one or more processes and/or functions as described with regard to PCRF 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 for one or more operator's IP services, e.g., IMS, 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 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.

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, a baseband 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, or one or more circuits or circuitry, and/or any combination thereof. Processor 310 may executes instructions, for example, of an Operating System (OS) of PCRF entity 300 and/or of one or more suitable applications.

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 (SDRAM), 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 PRA related information reporting or providing module or unit (hereinafter "PRA module 308") that may be coupled to any other component in PCRF entity 300. In some embodiments, PRA module 308 may be configured to perform one or more processes and/or functions described in the disclosure. In some embodiments, the PRA module 308 may be configured to receive MME information and/or PRA list and/or other PRA related information from a MME, e.g., MME 106 that may currently serve UE 102. For example, the PRA module 308 may be configured to receive from MME 106 the MME ID of MME 106 and/or the PRA list under MME 106 and/or other PRA related information as described in the disclosure.

In some embodiments, PRA module 308 may be configured to obtain and/or provide PRA related information, e.g., a first PRA list that may comprise one or more PRAs/PRA IDs associated with a MME, e.g., MME 106, a second PRA list subscribed by a UE, e.g., UE 102, and/or a list of PRA elements associated with each PRA/PRA ID.

In some embodiments, PRA module 308 may be configured to provide one or more event triggers, e.g., as described below.

In some embodiments, PRA module 308 may be configured to maintain a mapping table between a MME ID of a MME, e.g., MME 106, and a PRA list for MME 106. In some embodiments, the PRA list for MME 106 may comprise one or more PRAs/PRA IDs that may be configured for MME 106. For example, the mapping table may be stored in memory 312. In some embodiments, PRA module 308 may not maintain the MME ID/PRA list mapping table for a MME in memory 312 if the MME may provide a PRA list for the MME to the PCRF entity 300. In some embodiments, the mapping table may comprise one or more MME ID/PRA list mappings relating to one or more other MMEs.

In some embodiments, PRA module 308 may be configured to maintain a PRA list/PRA element list mapping table between, e.g., a PRA list that may be subscribed for a UE, e,g., UE 102, and, e.g., a list of one or more PRA elements for each of the PRAs/PRA IDs. In some embodiments, the mapping table may be stored in memory 312. In some embodiments, the PRA module 308 may not maintain the PRA list/PRA element list mapping table if one or more MMEs may be configured with the one or more PRA elements for the PRAs/PRA IDs.

In some embodiments, PRA module 308 may be configured to look up the mapping table to obtain the first PRA list associated with the MME ID from MME 106. In some embodiments, the PRA module 308 may receive the first PRA PRA list from MME 106.

In some embodiments, the PRA module 308 may be configured to obtain from the first PRA list a second PRA list of one or more PRA/PRA IDs associated with UE 102 based on subscription information of the UE 106. In some embodiments, memory 312 may store the subscription information. In some information, PRA module 308 may receive the subscription information from UE 106. In some embodiments, the PRA module 308 may be configured to obtain a list of PRA elements associated with each PRA and/or PRA ID from the second PRA list based a mapping table between PRAs/PRA IDs and PRA elements associated with each PRAs/PRA IDs.

In some embodiments, the PRA module 308 may be configured to provide the second PRA list for UE 102 and/or the list of PRA elements associated with each PRA and/or PRA ID to, e.g., PCEF 112A in PGW 112, e.g., via transceiver 320 and/or PGW interface 302. In some embodiments, PGW 112 (e.g., the PCEF 112A) may send the second PRA list for UE 102 and/or the list of PRA elements may be transferred to MME 106 via SGW 108.

In some embodiments, the PRA module 308 may be configured to have knowledge of which MME may not need to know the list of PRA elements associated with each PRA/PRA ID or receive one or more indications from MME 106 and/or other MME(s). In some embodiments, the PRA module 308 may be configured to know whether MME 106 may receive the list of PRA elements associated with each PRA/PRA ID or receive from MME 106 an indication on whether MME 106 may receive the list of PRA elements. In some embodiments, in response to having knowledge that MME 106 may not need the list of PRA elements associated with each

PRA/PRA ID or receive MME 106's indication that MME 106 may not need the list of PRA elements, the PRA module 308 may only transfer the second PRA list without the list of PRA elements associated with each PRA/PRA ID. Contrarily, the PRA module 308 may be configured to send the list of PRAs (e.g., PRAs/PRA IDs) and the list of PRA elements associated with each PRA/PRA ID in response to determining that MME 106 may use the list of PRA elements associated with each PRA/PRA ID or receiving the indication on the requirement of the list of PRA elements from MME 106.

In some embodiments, PRA module 308 may be configured to receive a PRA list/PRA change reporting for a PDN connection of UE 106 from MME 106 in response to a PRA list/PRA change. In some embodiments, PRA module 308 may be configured to receive a reporting that may comprise a new MME ID reporting and/or a new PRA list and/or other PRA related information associated with a new MME from PGW/PREF 112 via SGW 108 in response to a change in MME and/or PRA list.

In some embodiments, PRA module 308 may be configured to perform one or more other processes and/or functions as described herein with regard to PCRF 114.

In some embodiments, the PRA module 308 may be coupled to the transceiver 320. In some embodiments, PRA module 308 may be configured to send the second PRA list and/or the list of one or more PRA elements associated with each PRA/PRA ID to the PCEF 112A/PGW 112 through the transceiver 320 and/or the PGW interface 302.

In some embodiments, memory 312 may store one or more from a group comprising the MME ID of MME 106, the mapping table between MME IDs and a PRA list and/or other PRA related information under each MME, the first PRA list under MME 106, the second PRA list for UE 102, the list of one or more PRA elements associated with each PRAs/PRA IDs of the second PRA list, the mapping table between one or more PRA elements and each PRAs/PRA IDs, PRA list/PRA change reporting and/or other MME related information and/or PRA related information associated with MME 106 that may currently serve UE 102.

In some embodiments, memory 312 may store the new MME ID reporting, and/or the new PRA list reporting, and/or other MME related information and/or PRA related information, e.g., associated with a new MME in response to a change on MME/MME ID and/or PRA list and/or other PRA related information. In some embodiments, memory 312 may store a PRA list/PRA change reporting for a PDN connection of UE 102 from MME 106 that may currently serve UE 102.

While Figure 3 illustrates the PRA module 308 may be provided in PCRF entity 300, in some other embodiments, PRA module 308 may be provided in or implemented by the processor 310. While Figure 3 illustrates the transceiver 320, in some embodiments, the transceiver 320 may be implemented by a transmitter and/or a receiver. While Figure 3 illustrates one or more interfaces, e.g., 302, in some embodiments, the one or more interfaces may not be used. In some embodiments, the one or more interfaces may be implemented in or by the transceiver 320. While Figure 3 illustrates an example of transceiver 320, in some embodiments, a data/signal exchange between PCRF entity 300 and PGW 112/PCEF 112A and/or one or more entities 120 that may be used for the one or more IP services may not use transceiver 320 but may be implemented via, e.g., IP connection(s), etc.

Figure 4 demonstratively illustrates an example of one or more processes in accordance with some embodiments.

In some embodiments of Fig. 4, the one or more processes may be used by a PCRF 114 and/or PCRF 300 in accordance with some embodiments. In some embodiments, PCRF 114 may maintain the mapping table between MME ID(s) and PRA list(s), e.g. PRAs/PRA IDs.

For example, at 410, PCRF 114 may receive a MME ID (e.g., Globally Unique MME Identifier (GUMMEI)) from MME 106 that may currently serve a subscriber, e.g., UE 102. For example, PCRF 114 may receive the MME ID from PGW 112 that may receive the MME ID from MME 106 via SGW 108.

In some embodiments, at 420, PCRF 114 may obtain a first PRA list corresponding to MME 106 based on a mapping table between MME IDs and PRA lists associated with the MME IDs. For example, the first PRA list may comprise one or more PRAs/PRA IDs for one or more PRAs associated with the MME ID of MME 106. In some embodiments, PCRF 114 may query its database to retrieve the first PRA list associated with the MME ID of MME 106 based on the mapping table. In some embodiments, PCRF 114 may look up the mapping table, e.g., in a memory of PCRF 114, to obtain the first PRA list under MME 106.

In some embodiments, at 430, PCRF 114 may obtain from the first PRA list a second PRA list that may be subscribed by the UE 402. For example, PCRF 114 may filter the first PRA list, e.g., based on subscription information of UE 402 to obtain the second PRA list relating to UE 402. In some embodiments, UE 102 may be configured to send the subscription information. In some embodiments, the subscription information may be stored in a memory of PCRF 114.

In some embodiments, at 440, PCRF 114 may send the filtered PRA list obtained at 430 to

PGW 112 (e.g., PCEF 112A). In some embodiments, PCRF 114 may obtain a list of PRA elements associated with each PRA/PRA ID in the second list based on a mapping table between one or more PRAs or PRA IDs and one or more PRA elements associated with each PRA/PRA ID. In some embodiments, PCRF 114 may include the second PRA list relating to UE 102, the list of PRA elements associated with each PRA/PRA ID in the second list, and/or one or more event triggers, e.g., in a response message to PGW 112 (e.g., PCEF 112A) over a Gx interface. In some embodiments, the one or more event triggers may enable the PRA list/PRA change reporting from PCEF 112A in PGW 112 to PCRF 114 and/or from MME 106 to PGW 112. In some embodiments, the one or more event triggers may comprise an event trigger of "Change of UE presence in Presence Reporting Area" that may enable a PRA list/PRA change reporting from PCEF 112A in PGW 112 to PCRF 114 in response to the PRA list/PRA change, and/or an event trigger of "Location Change (MME)" that may enable a MME/MME ID and/or PRA list/PRA change reporting from MME 106 to PGW 112 in response to the MME/MME ID and/or PRA/PRA list change.

Figure 5 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes may be used by a PGW 112. In some embodiments, at 510, PGW 112, e.g., PCEF 112A, may receive the response message from PCRF 114 via the Gx interface. At 520, the PGW 112 may send a Create Session Response message to MME 106 via SGW 108. The Create Session Response message may comprise the second PRA list, the list of PRA elements associated with each PRA/PRA ID and/or a Change Reporting Action, e.g., "Start Reporting MME ID" that may trigger the MME/MME ID change reporting (e.g., the MME/MME ID) from MME 106 to PGW 112 and/or "Start Reporting PRA list" to trigger PRA list/PRA change and/or other PRA related information reporting from PCEF 112A to PCRF 114.

Figure 6 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes may be used by PCRF 114. In some embodiments, MME 106 may send all configured PRA list (e.g. PRAs/PRA IDs) of MME 106 and/or other PRA related information to PCRF 114. PCRF 114 may not maintain the mapping table between a MME ID and a PRA list (e.g. PRAs/PRA IDs).

In some embodiments, at 610, in IP-CAN session establishment or modification, PCRF 114 may receive from MME 106 a PRA list (e.g. PRAs/PRA IDs) and/or other PRA related information configured for MME 106, e.g., via PGW 112 and SGW 108. At 620, PCRF 114 may obtain a filtered PRA list of one or more PRAs/PRA IDs for UE 102 from the PRA list for MME 106, e.g., based on subscription information of UE 102. In some embodiments, the subscription information may be stored in a memory of PCRF 114. In some embodiments, the subscription information may be transmitted by UE 102.

At 630, PCRF 114 may send a response message to the PCEF 112A in PGW 112 over the Gx interface. The response message may comprise the filtered PRA list for UE 102 obtained at 620, the list of PRA elements associated with each PRA/PRA ID, and/or other PRA related information, and/or one or more event triggers, e.g., "Change of UE presence in Presence

Reporting Area" that may enable a PRA list/PRA change reporting from PCEF 112A to PCRF 114 and/or "Location Change (PRA list)" that may enable a PRA list/PRA change reporting from PCEF 112A to PCRF 114. In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In response to receiving the response message from PCRF 114, PGW 112 (e.g., PCEF

112A) may send a Create Session Response message to MME 106, e.g., via SGW 108, wherein the Create Session Response message may comprise the filtered PRA list for UE 102 and the list of PRA elements associated with each PRA/PRA ID, and/or a Change Reporting Action, e.g., "Start Reporting PRA list" that may trigger MME 106 to report the PRA list (e.g., the filtered PRA list for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID).

Figure 7 demonstratively illustrates an example of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes may be used by MME 106. In some embodiments, at 710, MME 106 may track a change in MME and/or PRA list (e.g., PRAs/PRA IDs). MME 106 may detect if there is a change in MME and/or a PRA list. At 720, MME 106 may report the new MME ID and/or the new PRA list to PCEF 112A in PGW 112 via SGW 108 in response to detection of the change.

In some embodiments, in response to receiving the new MME ID and the new PRA list, PCEF 112A in PGW 112 may report the new MME ID and the new PRA list to PCRF 114. In some embodiments, one or more processes relating to Sl-based handover, e.g., 5.5.1.2 of 3GPP specification 23.401, one or more processes relating to Tracking Area Update procedure, e.g.,

5.3.3 of 3GPP specification 23.401, one or processes relating to Service Request procedure, e.g.,

5.3.4 of 3GPP specification 23.401 and one or more processes relating to Location Change Reporting procedure, e.g., 5.9.2 of 3GPP specification 23.401, may be used for the change reporting. For example, in response to detecting a PRA list/PRA change for a PDN connection for a UE, e.g., UE 102, MME 106 may report the PRA list/PRA change to PCRF 114 via one or more of the above described processes according to 3GPP specification 23.401.

In some embodiments, PCRF 114 may not transfer the list of PRA elements associated with each PRA/PRA ID to MME 106, which may reduce a size of a message with the PRA ID and the related PRA elements associated with each PRA/PRA ID. Figures 8 and 9

demonstratively illustrates examples of one or more processes in accordance with some embodiments.

In some embodiments, the one or more processes of Figure 8 may be used by PCRF 114. In some embodiments, PCRF 114 may be configured to determine which MME may not need to know the list of PRA elements associated with each PRA/PRA ID.

In some embodiments, at 810, PCRF 114 may be configured to determine which MME has been aware of the list of PRA elements associated with each PRA/PRA ID under the coverage of the MME. At 820, in response to determining that MME 106 knows the list of PRA elements associated with each PRA/PRA ID under MME 106, PCRF 114 may only send to MME 106 the PRA list without the list of PRA elements associated with each PRA/PRA ID under MME 106.

In some embodiments, the one or more processes of Figure 9 may be used by MME 106.

In some embodiments, MME 106 may be configured to indicate to PCRF 114 whether MME 106 is to receive the list of PRA elements associated with each PRA/PRA ID under MME 106 and/or for a UE.

In some embodiments, at 910, MME 106 may send its MME ID to PCRF 114. At 920, MME 106 may send an indication to PCRF 114 to indicate whether MME 106 is to receive the list of PRA elements associated with each PRA/PRA ID under MME 106 or MME 106 is configured with the list of PRA elements associated with each PRA/PRA ID.

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 by PCRF 114. In some embodiments, MME 106 may be configured to indicate to PCRF

114 whether MME 106 is to receive the list of PRA elements associated with each PRA/PRA ID under MME 106.

In some embodiments, MME 106 may be configured with the PRA list under MME 106 and/or the list of PRA elements associated with each PRA/PRA ID under MME 106. At 1110, PCRF 114 may receive the MME ID from MME 106 and/or an indication of whether MME 106 is to receive the list of PRA elements associated with each PRA/PRA ID under MME 106, e.g., via a Create Session Request message and/or a Modify Session Request message. At 1020, in response to having knowledge that MME 106 has the list of PRA elements associated with each PRA/PRA ID under MME 106 or MME 106 may not need to know the list of PRA elements associated with each PRA/PRA ID, PCRF 114 may only provide to MME 106 the PRA IDs subscribed by UE 102, e.g., via PGW 112 and/or SGW 108.

Figure 11 demonstratively illustrates examples of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 11 may be used in an Attach procedure, e.g., as shown in Figure 5.3.2.1-1 of 3GPP specification 23.401. In some embodiments, a UE/user may register with the network, e.g., E-UTRAN, to receive services that may use registration. For example, the registration may be described as Network Attachment.

In some embodiments, at 1102, a UE, e.g., UE 102, may initiate an Attach procedure, e.g., via an Attach request. In some embodiments, one or more processes 1 to 11 as described in 5.3.2.1 of 3GPP specification 23.401 may be performed.

At 1104, if there is a change in MME/MME ID at 1102 or a new MME 106n is to be used during the Attach procedure, the new MME 106n may send its MME ID and/or one or more PRAs/PRA IDs associated with MME 106n in a Create Session Request message to SGW 108. In some embodiments, the Create Session Request message may further comprise other information.

At 1106, SGW 108 may send a Create Session Request message that may comprise the MME ID and/or the one or more PRAs/PRA IDs to PGW 112, e.g., PCEF 112A.

At 1108, PGW 112 may use PCEF 112A to send the MME ID and/or the one or more PRAs/PRA IDs in an indication of IP-CAN Session Establishment or Modification message to PCRF 114.

In some embodiments, at 1110, in response to receiving the MME ID from MME 106, PCRF 114 may look up a mapping table between a MME ID and a PRA list in PCRF 114 to obtain the one or more PRAs/PRA IDs associated with the MME ID of MME 106. From the set of the one or more PRAs/PRA IDs associated with the MME ID of MME 106, PCRF 114 may find out another PRA list associated with UE 102 based on UE 102's subscription information. PCRF 114 may send a response message to PGW 112, e.g., an Acknowledge associated with the IP-CAN Session Establishment or Modification message. For example, PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID associated with UE 102 to PGW 112 in the Acknowledge message associated with the IP- CAN Session Establishment or Modification message. In some embodiments, the Acknowledge message may further comprise one or more event trigger, e.g., "Location Change (MME)". In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In some other embodiments, at 1110, in response to receiving the list of the one or more PRAs/PRA IDs from MME 106, PCRF 114 may find out another PRA list for UE 102 based on UE 102's subscription information. PCRF 114 may send another PRA list associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID for UE 102 to PGW 112 in the Acknowledge of IP CAN Session Establishment or Modification message. For example, the Acknowledge of IP CAN Session Establishment or Modification message may comprise one or more event triggers, e.g., Location Change (PRA list). In some embodiments, PCEF 112A may store or enforce the one or more new event triggers provided by PCRF 114.

In some embodiments, if MME 106 is configured with the one or more PRAs/PRA IDs and/or the list of PRA elements associated with each PRA/PRA ID, an indication that the list of PRA elements associated with each PRA/PRA ID is not needed may be included in one or more messages from MME 106 to SGW 108, PGW 112 and/or PCRF 114.

In some embodiments, at 1110, PCRF 114 may only send to PGW 112 the PRA list for UE 102 and/or may not send the list of PRA elements associated with each PRA/PRA ID, in response to determining that MME 106 may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to MME 106. For example, PCRF 114 may be configured to determine whether MME 106 may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to MME 106 or may be explicitly indicated by MME 106, e.g., via the indication in one or more messages from MME 106 to PCRF 114 via PGW 112 and/or SGW 108.

At 1112, PGW 112 may send, e.g., via PCEF 112A, to SGW 108 a Create Session

Response message that may comprise the PRA IDs for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID. The Create Session Response message may comprise a Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1114, SGW 108 may send to MME 106 a Create Session Response message that may comprise the PRA IDs, and/or the list of PRA elements associated with each PRA/PRA ID, and/or the Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1116, one or more processes, e.g., processes 17 to 26 in 5.3.2.1 of 3GPP specification of 23.401 may be performed in the Attach procedure.

While Figure 11 illustrates 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 5.3.2.1 of 3GPP specification 23.401.

Figure 12 demonstratively illustrates examples of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 12 may be used in a procedure, e.g., UE requested PDN connectivity, as shown in Figure 5.10.2.1-1 of 3GPP specification 23.401. For example, the procedure may allow the UE to request for connectivity to an additional PDN over E-UTRAN, e.g., including allocation of a default bearer, if the UE has an active PDN connections over E-UTRAN.

In some embodiments, at 1202, a UE, e.g., UE 102, may initiate the UE requested PDN connectivity via, e.g., a PDN connectivity request message. In some embodiments, one or more processes as described in 5.10.2 of 3GPP specification 23.401 may be performed to initiate the UE requested PDN connectivity.

At 1204, MME 106 may send the MME ID of MME 106 and/or one or more PRAs/PRA IDs under MME 106 in a Create Session Request message to SGW 108, in response to receiving the PDN connectivity request message from UE 102.

At 1206, SGW 108 may send a Create Session Request message that may comprise the MME ID and/or the one or more PRAs/PRA IDs to PGW 112, e.g., PCEF 112A.

At 1208, PGW 112 may use PCEF 112A to send the MME ID and/or the one or more PRAs/PRA IDs in an indication of IP-CAN Session Establishment message to PCRF 114.

In some embodiments, at 1210, in response to receiving the MME ID from MME 106,

PCRF 114 may look up a mapping table between a MME ID and a PRA list in PCRF 114 to obtain the one or more PRAs/PRA IDs associated with the MME ID of MME 106. From the set of the one or more PRAs/PRA IDs associated with the MME ID of MME 106, PCRF 114 may find out another PRA list associated with UE 102 based on UE 102's subscription information. PCRF 114 may send a response message to PGW 112, e.g., an Acknowledge associated with the IP-CAN Session Establishment message. For example, PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID associated with UE 102 to PGW 112 in the Acknowledge message associated with the IP-CAN Session Establishment message. In some embodiments, the Acknowledge message may further comprise one or more event trigger, e.g., "Location Change (MME)". In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In some other embodiments, at 1210, in response to receiving the list of the one or more PRAs/PRA IDs from MME 106, PCRF 114 may find out another PRA list for UE 102 based on UE 102's subscription information. PCRF 114 may send another PRA list associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID for UE 102 to PGW 112 in the Acknowledge of IP CAN Session Establishment message. For example, the Acknowledge of IP CAN Session Establishment message may comprise one or more event triggers, e.g., Location Change (PRA list). In some embodiments, PCEF 112A may store or enforce the one or more new event triggers provided by PCRF 114.

In some embodiments, if MME 106 is configured with the one or more PRAs/PRA IDs and/or the list of PRA elements associated with each PRA/PRA ID, an indication that the list of PRA elements associated with each PRA/PRA ID is not needed may be included in one or more messages from MME 106 to SGW 108, PGW 112 and/or PCRF 114.

In some embodiments, at 1210, PCRF 114 may only send to PGW 112 the PRA list for UE 102 and/or may not send the list of PRA elements associated with each PRA/PRA list, in response to determining that MME 106 may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to MME 106. For example, PCRF 114 may be configured to determine whether MME 106 may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to MME 106 or may be explicitly indicated by MME 106, e.g., via the indication in one or more messages from MME 106 to PCRF 114 via PGW 112 and/or SGW 108.

At 1212, PGW 112 may send, e.g., via PCEF 112A, to SGW 108 a Create Session Response message that may comprise the PRA IDs for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID. The Create Session Response message may comprise a Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1214, SGW 108 may send to MME 106 a Create Session Response message that may comprise the PRA IDs, and/or the list of PRA elements associated with each PRA/PRA ID, and/or the Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1216, one or more processes, e.g., processes 7 to 16 in 5.10.2 of 3GPP specification 23.401 may be performed in the UE requested PDN connectivity procedure.

While Figure 12 illustrates 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 5.10.2 of 3 GPP specification 23.401.

Figure 13 demonstratively illustrates examples of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 13 may be used in a S I based handover procedure, e.g., as shown in Figure 5.5.1.2.2-1 of 3GPP specification 23.401.

In some embodiments, at 1302, a source eNB 104s may decide to initiate an SI -based handover to a target eNB 104t. In some embodiments, one or more processes 1 to 14b as described in 5.5.1.2.2 of 3GPP specification 23.401 may be performed.

At 1304, a target MME 106t may transmit a Modify Bearer Request message to a target SGW 108t. In some embodiments, the Modify Bearer Request message may comprise the MME ID of the target MME 106t and/or one or more PRAs/PRA IDs for the target MME 106t.

At 1306, a target SGW 108t may forward the MME ID and/or the one or more PRAs/PRA IDs to PGW 112 in a Modify Bearer Request message.

At 1308, PGW 112 may send the MME ID and/or the one or more PRAs/PRA IDs in an Indication of IP-CAN Session Modification message to PCRF 114.

In some embodiments, at 1310, in response to receiving the MME ID from the target MME 106t, PCRF 114 may look up a mapping table between a MME ID and a PRA list in PCRF 114 to obtain the one or more PRAs/PRA IDs associated with the MME ID of the target MME 106t. From the set of the one or more PRAs/PRA IDs associated with the MME ID of the target MME 106t, PCRF 114 may find out another PRA list associated with UE 102 based on UE 102's subscription information. PCRF 114 may send a response message to PGW 112, e.g., an Acknowledge of IP-CAN Session Modification message. For example, PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID associated with UE 102 to PGW 112 in the Acknowledge message associated with the IP- CAN Session Modification message. In some embodiments, the Acknowledge message may further comprise one or more event trigger, e.g., "Location Change (MME)". In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In some other embodiments, at 1310 in response to receiving the list of the one or more PRAs/PRA IDs from MME 106, PCRF 114 may find out another PRA list for UE 102 based on UE 102's subscription information. PCRF 114 may send another PRA list associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID for UE 102 to PGW 112 in the Acknowledge of IP CAN Session Modification message. For example, the Acknowledge of IP CAN Session Modification message may comprise one or more event triggers, e.g., Location Change (PRA list). In some embodiments, PCEF 112A may store or enforce the one or more new event triggers provided by PCRF 114.

In some embodiments, if target MME 106t is configured with the one or more PRAs/PRA IDs and/or the list of PRA elements associated with each PRA, an indication that the list of PRA elements associated with each PRA/PRA ID is not needed may be included in one or more messages from target MME 106t to SGW 108, PGW 112 and/or PCRF 114.

In some embodiments, at 1310, PCRF 114 may only send to PGW 112 the PRA list for UE 102 and/or may not send the list of PRA elements associated with each PRA, in response to determining that target MME 106t may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each

PRA/PRA ID to MME 106. For example, PCRF 114 may be configured to determine whether target MME 106t may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to target MME 106t or may be explicitly indicated by the target MME 106t, e.g., via the indication in one or more messages from target MME 106t to PCRF 114 via PGW 112 and/or SGW 108.

At 1312, PGW 112 may respond to target SGW 108t with a Modify Bearer Response message that may comprise the PRA IDs for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID. The Modify Bearer Response message may comprise a Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1314, the target SGW 108t may respond to the target MME 106t with a Modify Bearer Response message that may comprise the PRA IDs, and/or the list of PRA elements associated with each PRA/PRA ID, and/or the Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1316, one or more processes, e.g., processes 18 to 21b in 5.5.1.2.2 of 3GPP

specification 23.401 may be performed in the SI -based handover procedure.

While Figure 13 illustrates 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 5.5.1.2.2 of 3GPP specification 23.401.

Figure 14 demonstratively illustrates examples of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 11 may be used in a Tracking Area Update (TAU) procedure, e.g., as shown in Figure 5.3.3.1-1 of 3GPP specification 23.401. In some embodiments, Radio Network Controller (RNC) 318 may be used.

In some embodiments, at 1402, a UE, e.g., UE 102, may initiate a TAU procedure via, e.g., a TAU request, in response to a TAU trigger. In some embodiments, one or more processes 1 to 7 as described in 5.3.3.1 of 3GPP specification 23.401 may be performed.

At 1404, in response to MME changing to a new MME 106n, the new MME 106n may send to a new SGW 108n a Create Session Request message with the MME ID of the new MME 106n and/or one or more PRAs/PRA IDs relating to the new MME 106n.

At 1406, the new SGW 108n may forward the MME ID and/or the PRA IDs to PGW 112 in a Create Session Request message.

At 1408, PGW 112 may send the MME ID or the PRA IDs in an Indication of IP-CAN

Session Establishment message to PCRF 114.

In some embodiments, at 1410, in response to receiving the MME ID from the new MME 106n, PCRF 114 may look up a mapping table between a MME ID and a PRA list in PCRF 114 to obtain the one or more PRAs/PRA IDs associated with the MME ID of the new MME 106n. From the set of the one or more PRAs/PRA IDs associated with the MME ID of the new MME 106n, PCRF 114 may find out another PRA list associated with UE 102 based on UE 102's subscription information. PCRF 114 may send a response message to PGW 112, e.g., an Acknowledge of IP-CAN Session Establishment message. For example, PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID associated with UE 102 to PGW 112 in the Acknowledge message of the IP-CAN Session Establishment message. In some embodiments, the Acknowledge message may further comprise one or more event trigger, e.g., "Location Change (MME)". In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In some other embodiments, at 1410, in response to receiving the list of the one or more PRAs/PRA IDs from MME 106, PCRF 114 may find out another PRA list for UE 102 based on UE 102's subscription information. PCRF 114 may send another PRA list associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID for UE 102 to PGW 112 in the Acknowledge of IP CAN Session Modification message. For example, the Acknowledge of IP CAN Session Modification message may comprise one or more event triggers, e.g., Location Change (PRA list). In some embodiments, PCEF 112A may store or enforce the one or more new event triggers provided by PCRF 114.

In some embodiments, if new MME 106n is configured with the one or more PRAs/PRA IDs and/or the list of PRA elements associated with each PRA, an indication that the list of PRA elements associated with each PRA/PRA ID is not needed may be included in one or more messages from new MME 106n to SGW 108, PGW 112 and/or PCRF 114.

In some embodiments, at 1410, PCRF 114 may only send to PGW 112 the PRA list for UE 102 and/or may not send the list of PRA elements associated with each PRA, in response to determining that new MME 106n may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each

PRA/PRA ID to MME 106. For example, PCRF 114 may be configured to determine whether new MME 106n may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to new MME 106n or may be explicitly indicated by the new MME 106n, e.g., via the indication in one or more messages from new MME 106n to PCRF 114 via PGW 112 and/or SGW 108.

At 1412, PGW 112 may respond to new SGW 108n with a Create Session Response message that may comprise the PRA IDs for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID. The Create Session Response message may comprise a Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1414, the new SGW 108n may respond to the new MME 106n with a Create Session Response message that may comprise the PRA IDs, and/or the list of PRA elements associated with each PRA/PRA ID, and/or the Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1416, one or more processes, e.g., processes 12 to 19 in 5.3.3.1 of 3GPP specification 23.401 may be performed in the TAU procedure.

While Figure 14 illustrates 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 5.3.3 of 3GPP specification 23.401.

Figure 15 demonstratively illustrates examples of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 15 may be used in a UE Triggered Service Request procedure, e.g., as shown in Figure 5.3.4.1-1 of 3GPP specification 23.401.

In some embodiments, at 1502, UE 102 may, e.g., send Non- Access-Stratum (NAS) message Service Request towards MME 106 in an RRC message to eNB 104. In some embodiments, one or more processes 1 to 7 as described in 5.3.4.1 of 3GPP specification 23.401 may be performed.

At 1504, MME 106 may send a Modify Bearer Request message to SGW 108. In some embodiments, the Modify Bearer Request message may comprise the MME ID of MME 106 and/or one or more PRAs/PRA IDs for MME 106.

At 1506, SGW 108 may forward the MME ID and/or the one or more PRAs/PRA IDs to PGW 112 in a Modify Bearer Request message.

At 1508, PGW 112 may send the MME ID and/or the one or more PRAs/PRA IDs in an Indication of IP-CAN Session Modification message to PCRF 114.

In some embodiments, at 1510, in response to receiving the MME ID from MME 106, PCRF 114 may look up a mapping table between a MME ID and a PRA list in PCRF 114 to obtain the one or more PRAs/PRA IDs associated with the MME ID of MME 106. From the set of the one or more PRAs/PRA IDs associated with the MME ID of MME 106, PCRF 114 may find out another PRA list associated with UE 102 based on UE 102's subscription information. PCRF 114 may send a response message to PGW 112, e.g., an Acknowledge of IP-CAN Session Modification message. For example, PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID associated with UE 102 to PGW 112 in the Acknowledge message associated with the IP-CAN Session Modification message. In some embodiments, the Acknowledge message may further comprise one or more event trigger, e.g., "Location Change (MME)". In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In some other embodiments, at 1510, in response to receiving the list of the one or more PRAs/PRA IDs from MME 106, PCRF 114 may find out another PRA list for UE 102 based on UE 102's subscription information. PCRF 114 may send another PRA list associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID for UE 102 to PGW 112 in the Acknowledge of IP CAN Session Modification message. For example, the Acknowledge of IP CAN Session Modification message may comprise one or more event triggers, e.g., Location Change (PRA list). In some embodiments, PCEF 112A may store or enforce the one or more new event triggers provided by PCRF 114.

In some embodiments, if MME 106 is configured with the one or more PRAs/PRA IDs and/or the list of PRA elements associated with each PRA, an indication that the list of PRA elements associated with each PRA/PRA ID is not needed may be included in one or more messages from MME 106 to SGW 108, PGW 112 and/or PCRF 114.

In some embodiments, at 1510, PCRF 114 may only send to PGW 112 the PRA list for UE 102 and/or may not send the list of PRA elements associated with each PRA, in response to determining that MME 106 may not need the list of PRA elements associated with each

PRA/PRA ID or there is no need to send the list of PRA elements associated with each

PRA/PRA ID to MME 106. For example, PCRF 114 may be configured to determine whether MME 106 may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to MME 106 or may be explicitly indicated by MME 106, e.g., via the indication in one or more messages from MME 106 to PCRF 114 via PGW 112 and/or SGW 108.

At 1512, PGW 112 may respond to SGW 108 with a Modify Bearer Response message that may comprise the PRA IDs for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID. The Modify Bearer Response message may comprise a Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1514, the SGW 108 may respond to MME 106 with a Modify Bearer Response message that may comprise the PRA IDs, and/or the list of PRA elements associated with each PRA/PRA ID, and/or the Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

While Figure 15 illustrates 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 5.3.4.1 of 3GPP specification 23.401.

Figure 16 demonstratively illustrates examples of one or more processes in accordance with some embodiments. In some embodiments, the one or more processes of Figure 16 may be used in a Location Change Reporting procedure. In some embodiments, PCRF 114 may be configured to provide an event trigger for MME ID change reporting to PCEF 112 A in PGW 112 and/or to MME 106 via PGW 112 and SGW 108 in response to IP-CAN Session Establishment or Modification, e.g., during Attach, UE requested PDN Connectivity, UE triggered Service Request, S l-based handover and/or Bearer Modification procedures, etc., to enable MME ID change reporting from MME 106 to PCRF 114.

In some embodiments, at 1602a, MME 106 may receive an E-UTRAN Cell Global Identifier (ECGI) information Update from eNB 104.

At 1602a, MME 106 may detect if UE 102's serving MME ID is changed.

At 1604, if MME 106 is requested to report a location change to PGW 112 for UE 102, e.g., in response to start reporting MME/MME ID change is enable, or under one or more conditions specified in 5.9.2 of 3GPP specification 23.401, MME 106 may send a Change Notification message to SGW 108 to indicate a new MME ID relating to the location change.

At 1606, SGW 108 may forward a Change Notification message with the new MME 106 ID to the PGW 112.

At 1608, the PGW 112 may send the new MME ID to PCRF 114 in an Indication of IP- CAN Session Modification message.

In some embodiments, at 1510, in response to receiving the MME ID from MME 106, PCRF 114 may look up a mapping table between a MME ID and a PRA list in PCRF 114 to obtain the one or more PRAs/PRA IDs associated with the MME ID of MME 106. From the set of the one or more PRAs/PRA IDs associated with the MME ID of MME 106, PCRF 114 may find out another PRA list associated with UE 102 based on UE 102's subscription information. PCRF 114 may send a response message to PGW 112, e.g., an Acknowledge of IP-CAN Session Modification message. For example, PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID associated with UE 102 to PGW 112 in the Acknowledge message associated with the IP-CAN Session Modification message. In some embodiments, the Acknowledge message may further comprise one or more event trigger, e.g., "Location Change (MME)". In some embodiments, PCEF 112A may store or enforce the one or more event triggers provided by PCRF 114.

In some other embodiments, at 1610, in response to receiving the list of the one or more

PRAs/PRA IDs from MME 106, PCRF 114 may find out one or more PRAs/PRA IDs for UE 102 based on UE 102's subscription information. PCRF 114 may send the PRA IDs associated with UE 102 and/or a list of PRA elements associated with each PRA/PRA ID for UE 102 to PGW 112 in an Acknowledge of IP CAN Session Modification message. For example, the Acknowledge of IP CAN Session Modification message may comprise one or more event triggers, e.g., Location Change (PRA list). In some embodiments, PCEF 112A may store or enforce the one or more new event triggers provided by PCRF 114.

In some embodiments, if MME 106 is configured with the one or more PRAs/PRA IDs and/or the list of PRA elements associated with each PRA, an indication that the list of PRA elements associated with each PRA/PRA ID is not needed may be included in one or more messages from MME 106 to SGW 108, PGW 112 and/or PCRF 114.

In some embodiments, at 1610, PCRF 114 may only send to PGW 112 the PRA list for UE 102 and/or may not send the list of PRA elements associated with each PRA, in response to determining that MME 106 may not need the list of PRA elements associated with each

PRA/PRA ID or there is no need to send the list of PRA elements associated with each

PRA/PRA ID to MME 106. For example, PCRF 114 may be configured to determine whether MME 106 may not need the list of PRA elements associated with each PRA/PRA ID or there is no need to send the list of PRA elements associated with each PRA/PRA ID to MME 106 or may be explicitly indicated by MME 106, e.g., via the indication in one or more messages from MME 106 to PCRF 114 via PGW 112 and/or SGW 108.

At 1612, PGW 112 may respond to SGW 108 with a Modify Bearer Response message that may comprise the PRA IDs for UE 102 and/or the list of PRA elements associated with each PRA/PRA ID. The Modify Bearer Response message may comprise a Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

At 1614, the SGW 108 may respond to MME 106 with an Acknowledge of Change

Notification message that may comprise the PRA IDs, and/or the list of PRA elements associated with each PRA/PRA ID, and/or the Change Reporting Action of "Start Reporting MME ID" and/or "Start Reporting PRA list".

While Figure 16 illustrates some embodiments of one or more processes that may be used in a Location Change Reporting procedure, in some embodiments, the Location Change

Reporting procedure may comprise one or more other processes as described in 5.9.2 of 3GPP specification 23.401.

In some embodiments, one or more PRA (Presence Reporting Area) reporting messages on SI 1, S5/S8 and/or Gx may be enhanced. For example, PRA related information reporting from MME 106 to PCEF 112A in PGW 112 via SGW 108 may include a PRA list and/or an indication of whether UE 102 is inside or outside of a PRA. For a single PRA for each PDN connection, the PRA ID may be reported to PCRF 114 even if UE 102 is outside of the PRA. If there are multiple PRAs under MME 106, UE 102 may only be inside of a single PRA or outside of any PRA, there is no need to know whether UE 102 is outside of a PRA.

In some embodiments, MME 106 may be configured to provide PRA related information to comprise a PRA/PRA ID of the PRA where UE 102 is located in response to indicating UE 102 is in a PRA. If UE 102 is not in any PRA, the PRA related information may indicate that UE 102 is outside of any PRA and may not include any PRA ID.

In some embodiments, the PRA related information may be reported via SI -based handover, Tracking Area Update and/or Location Change Reporting procedure.

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 1740, one or more antennas 1750, display, camera, sensor, and input/output (I/O) interface, 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 EUTRAN 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 (EUTRAN) 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+l 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-sigma 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 eNB 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 1740 may be used to load and store data and/or instructions, for example, for system. Memory /storage 1740 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 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 nonvolatile memory port, a universal serial bus (USB) port, an audio jack, and a power

supply interface.

In various embodiments, sensor 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 may include a display (e.g., a liquid crystal display, a touch screen display, etc.).

In various embodiments, the system 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 presence reporting area (PRA) module to provide to a serving gateway (SGW) a MME identifier (ID) or a PRA list comprising one or more PRA IDs associated with the MME ID in a Create Session Request or a Modify Bearer Request; and a memory to store a mapping table between the MME ID and the PRA list.

Example 2 may include the subject matter of Example 1 or any other examples described herein, wherein the memory is further to: store the PRA list or a list of PRA elements associated with the one or more PRA IDs in the PRA list.

Example 3 may include the subject matter of any one of examples 1 and 2 or any other examples described herein, wherein the PRA module is further to: indicate to a policy and charging rules function (PCRF) entity that a list of PRA elements associated with each

PRA/PRA ID is not used based on a determination that the list of PRA elements associated with each PRA ID is stored by the MME.

Example 4 may include the subject matter of any one of examples 1 to 3 or any other examples described herein, track a change in the MME ID or the PRA list; and report the change in the MME ID or the PRA list to the SGW in response to detection of the change.

Example 5 may include the subject matter of any one of examples 1 to 4 or any other examples described herein, wherein the PRA module is further to: in response to detection of the change in the MME ID or the PRA list, provide a new MME ID or a new list of PRA IDs to the

SGW.

Example 6 may include the subject matter of any one of examples 1 to 5 or any other examples described herein, wherein the PRA module is further to: provide to the SGW a PRA ID in which a user equipment (UE) is currently located in, or PRA related information to indicate that the UE is outside of any PRA relating to the PRA list.

Example 7 may include a policy and charging rules function (PCRF) entity, comprising: a presence reporting area (PRA) module to receive a Mobility Management Entity (MME) identifier (ID) or a PRA list of one or more presence reporting area (PRA) IDs associated with the MME ID from a Packet Data Network (PDN) gateway (PGW) PGW; and a memory to store the MME ID or the PRA list.

Example 8 may include the subject matter of example 7 or any other examples described herein, wherein the PRA module is to receive the MME ID or the PRA list in an indication of an internet protocol-connectivity access network (IP-CAN) session establishment message or an IP- CAM modification message from the PGW.

Example 9 may include the subject matter of any one of examples 7 or 8 or any other examples described herein, wherein the PRA module is further to: provide only another list of one or more PRA IDs associated with a user equipment (UE) based on subscription information of the UE in response to receiving an indication that the MME is not to receive a list of PRA elements associated with each PRA ID.

Example 10 may include the subject matter of any one of examples 7 to 9 or any other examples described herein, wherein the PRA module is further to: in response to reception of the MME ID, retrieve PRA related information associated with the MME ID to obtain the PRA list and a list of PRA elements belonging to each PRA ID; and send the PRA list, a list of PRA elements belonging to each PRA ID and an event trigger of location reporting for MME change or PRA list change to the PGW.

Example 11 may include the subject matter of any one of examples 7 to 10 or any other examples described herein, wherein the PRA module is further to: send the PRA list, a list of PRA elements belonging to each PRA ID and the event trigger in an Acknowledge of IP-CAN Session Establishment message.

Example 12 may include the subject matter of any one of examples 7 to 11 or any other examples described herein, wherein the PRA module is further to: trigger the MME to report a new MME ID in response to the event trigger for MME change reporting.

Example 13 may include the subject matter of any one of examples 7 to 12 or any other examples described herein, wherein the PRA module is further to: obtain a new list of one or more PRA IDs relating to the MME ID change; and send the new list of one or more PRA IDs to the PGW.

Example 14 may include the subject matter of any one of examples 7 to 13 or any other examples described herein, wherein the PRA module is further to: store the event trigger for PRA list change reporting to trigger the MME to report a new PRA list in response to detection of a PRA list change.

Example 15 may include the subject matter of any one of examples 7 to 14 or any other examples described herein, wherein the PRA module is further to: obtain, from MME via the PGW, a PRA ID in which currently a user equipment (UE) is located or indicate that the UE is outside of any PRA.

Example 16 may include the subject matter of any one of examples 7 to 15 or any other examples described herein, wherein the PRA module is further to: obtain the PRA list from the MME ID based on a mapping table between the MME ID and the PRA list.

Example 17 may include the subject matter of any one of examples 7 to 16 or any other examples described herein, wherein the PRA module is further to: obtain a filtered list of PRA IDs associated with a UE from the PRA list based on subscription information of the UE.

Example 18 may include a machine-readable medium having instructions, stored thereon, that, when executed cause a mobility management entity (MME) to: provide to a serving gateway (SGW) a Mobility Management Entity (MME) identifier (ID) or a presence reporting area (PRA) list associated with the MME ID in a Crate Session Request or a Modify Bearer Request; and store a mapping table between the MME ID and the PRA list.

Example 19 may include the subject matter of example 18 or any other examples described herein, having instructions, stored thereon, that, when executed cause the MME further to: provide to the SGW a PRA ID in which a user equipment (UE) is currently located in, or PRA related information to indicate that the UE is outside of any PRA relating to the PRA list.

Example 20 may include the subject matter any one of examples 18 or 19 or any other examples described herein, having instructions, stored thereon, that, when executed cause the MME further to: indicate to a policy and charging rules function (PCRF) entity that PRA related information is not used in response to knowing the PRA related information to the SGW.

Example 21 may include the subject matter of any one of examples 18 to 20 or any other examples described herein, having instructions, stored thereon, that, when executed cause the MME further to: report a change in the MME ID or PRA list to the SGW in response to detection of the change.

Example 22 may include the subject matter of any one of examples 18 to 21 or any other examples described herein, having instructions, stored thereon, that, when executed cause the MME further to: provide a new MME ID or a new PRA list to the SGW in response to detection of a change in the MME ID or PRA list.

Example 23 may include the subject matter of any one of examples 18 to 22 or any other examples described herein, having instructions, stored thereon, that, when executed cause the MME further to: indicate to a policy and charging rules function (PCRF) entity that a list of PRA elements associated with each PRA ID is not used based on a determination that the list of PRA elements associated with each PRA ID is stored by the MME.

Example 24 may include the subject matter of any one of examples 18 to 23 or any other examples described herein, having instructions, stored thereon, that, when executed cause the MME further to: track a change in the MME ID or the PRA list; and report the change in the MME ID or the PRA list to the SGW in response to detection of the change.

Example 25 may include a method or an apparatus comprising a MME that sends PRA IDs or MME ID in the Create Session Request or Modify Bearer Request to SGW.

Example 26 may include a method or an apparatus comprising a SGW that sends PRA IDs or MME ID in the Create Session Request or Modify Bearer Request to PGW/PCEF.

Example 27 may be a method or an apparatus comprising a PGW/PCEF that sends PRA IDs or MME ID in the indication of IP-CAN session establishment message to PCRF.

Example 28 may include the method or the apparatus of any one of examples 25-27, or of any other example herein, wherein if the MME knows the list of elements for each PRA, it will include an indication of not needing the list of elements for each PRA in the messages mentioned in any one of examples 25-27.

Example 29 may include the method or apparatus of any one of examples 25-27, or of any other example herein, wherein when the PCRF receives PRA IDs or MME ID, it will query its database to retrieve the PRA related information (PRA IDs and the list of elements belonging to each PRA ID), then it will send the PRA related information to PGW/PCEF in the Acknowledge IP CAN Session Establishment/Modification message.

Example 30 may include the method or apparatus of any one of examples 25-27, or of any other example herein, wherein the PGW/PCEF sends the PRA IDs and the list of elements belonging to each PRA ID to SGW in Create Session Response or Modify Bearer Response message.

Example 31 may include the method or apparatus of any one of examples 25-27, or of any other example herein, wherein the SGW sends the PRA IDs and the list of elements belonging to each PRA ID to MME in Create Session Response or Modify Bearer Response message.

Example 32 may include the method or apparatus of any one of examples 29-31, or of any other example herein, wherein if the PCRF knows there is no need to send the list of elements for each PRA to MME, then only PRA IDs may be included in the messages from PCRF to MME as described in any one of examples 29-31.

Example 33 may include the method or apparatus of any one of examples 25-32, or of any other example herein, wherein when using the Location Change Reporting procedure to report the MME ID change, the PCRF may provision an event trigger for the MME ID change reporting to the PCEF and the MME, then when MME detects there is MME ID change, it will report the new MME ID to the PCRF. The PCRF then finds out the related PRA IDs and sends them to the MME via the PGW and the S GW. Example 34 may be a mobility management entity, MME, apparatus, comprising: network interface controller, NIC, circuitry to transmit and to receive signals; baseband circuitry, coupled to the NIC circuitry, the baseband circuitry to: identify one or more presence reporting areas, PRAs; identify one or more PRA identifications, PRA IDs, associated respectively with the one or more identified PRAs, or identify an MME identification, MME ID; send or cause to send to a servicing gateway, SGW, a create session request message or a modify bearer request message that includes the identified one or more PRA IDs or the identified MME ID.

Example 35 may include the MME apparatus of example 34, or of some other example herein, wherein the baseband circuitry is further to: attempt to identify a list of elements for the every respective PRA; and include in the create session request message or modify bearer request message an indication of not needing a list of elements for every respective PRA, if the list of elements for the every respective PRA is identified.

Example 36 may be a method for implementing a mobility management entity, MME, the method comprising: identifying, by a MME, one or more presence reporting areas, PRAs;

identifying, by the MME, one or more PRA identifications, PRA IDs, associated respectively with the one or more identified PRAs, or identifying, by the computing system, an MME identification, MME ID; and sending or causing to send, by the MME, to a servicing gateway, SGW, a create session request message or a modify bearer request message that includes the identified one or more PRA IDs or the identified MME ID.

Example 37 may be the method of example 36, of some other method herein, wherein the method further comprises: attempting to identify, by the MME, a list of elements for the every respective PRA; and including, by the MME, in the create session request message or modify bearer request message an indication of not needing a list of elements for every respective PRA, if the list of elements for the every respective PRA is identified.

Example 38 may be a serving gateway, SGW, apparatus, comprising: network interface controller, NIC, circuitry to transmit and to receive signals; baseband circuitry, coupled to the NIC circuitry, the baseband circuitry to: identify one or more presence reporting areas, PRAs; identify one or more PRA identifications, PRA ID, associated respectively with the identified one or more PRAs, or identify a mobile management entity, MME, identification, MME ID; send or cause to send to a packet data network gateway, PGW, or to a policy and charging enforcement function, PCEF, a create session request message or a modify bearer request message that includes the identified PRA IDs or the identified MME ID.

Example 39 may include the SGW apparatus of example 38, or of some other example herein, wherein the baseband circuitry is further to: include in the create session request message or modify bearer request message an indication of not needing a list of elements for every respective PRA, if the list of elements for the every respective PRA is identified by a mobility management entity, MME.

Example 40 may be the SGW apparatus of example 38, or some other example herein, wherein the baseband circuitry is further to transmit the PRA IDs and the list of elements respectively for the PRA to the MME in the create session response message or modify bearer response message.

Example 41 may be a method for implementing a serving gateway, SGW, the method comprising: identifying, by the SGW, one or more presence reporting areas, PRAs; identifying, by the SGW, one or more PRA identifications, PRA ID, associated respectively with the identified one or more PRAs, or identify a mobile management entity, MME, identification,

MME ID; sending or causing to send, by the SGW, to a packet data network gateway, PGW, or to a policy and charging enforcement function, PCEF, a create session request message or a modify bearer request message that includes the identified PRA IDs or the identified MME ID.

Example 42 may include the method of example 40, or of some other example herein, further comprising: including, by the SGW, in the create session request message or modify bearer request message an indication of not needing a list of elements for every respective PRA, if the list of elements for the every respective PRA is identified by a mobility management entity, MME.

Example 43 may be a communications apparatus, comprising: network interface controller, NIC, circuitry to transmit and to receive signals; baseband circuitry, coupled to the NIC circuitry, the baseband circuitry to: identify a PRA identification, PRA ID or a MME identification, MME

ID; identify an IP connectivity access network, IP-CAN, establishment message; and send or cause to send the identified PRA ID or the identified MME ID in the indication of the IP-CAN session establishment message to a policy and charging rules function, PCRF, apparatus.

Example 44 may include the apparatus of example 43, or of some other example herein, wherein the communications apparatus may be a packet data network gateway, PGW, apparatus, or a policy and charging enforcement function, PCEF, apparatus.

Example 45 may include the apparatus of example 43, or of some other example herein, wherein the baseband circuitry is further to include in the create session request message or modify bearer request message an indication of not needing a list of elements for every respective PRA, if the list of elements for the every respective PRA is identified by a mobility management entity, MME.

Example 46 may be a method of implementing communications, the method comprising: identifying, by a computing system, a PRA identification, PRA ID or a MME identification, MME ID; identifying, by a computing system, an IP connectivity access network, IP-CAN, establishment message; and sending or causing to send, by the computing system, the identified PRA ID or the identified MME ID in the indication of the IP-CAN session establishment message to a policy and charging rules function, PCRF, apparatus.

Example 47 may be the method of example 46, or of any other example herein, the method further comprising including in the create session request message or modify bearer request message an indication of not needing a list of elements for every respective PRA, if the list of elements for the every respective PRA is identified by a mobility management entity, MME.

Example 48 may be a policy and charging enforcement function, PCEF, apparatus comprising: network interface controller, NIC, circuitry to transmit and to receive signals;

baseband circuitry, coupled to the NIC circuitry, the baseband circuitry to: receive a presence resource area, PRA, identification, PRA ID or a MME identification, MME ID; retrieve, based on the received PRA ID or MME ID, from a database PRA-related information; transmit the retrieved PRA-related information to a packet data network gateway, PGW, or to a policy and charging enforcement function, PCEF, apparatus, the PRA-related information included in an acknowledgement IP connectivity access network, IP-CAN, session establishment/modification message.

Example 49 may be the PCEF apparatus of example 48, or of some other example herein, wherein the baseband circuitry is further to transmit the one or more PRA IDs and the list of elements belonging respectively to the one or more PRA IDs to a servicing gateway, SGW, in the create session response message or modify bearer response message.

Example 50 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1- 49, or any other method or process described herein.

Example 51 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 described in or related to any of examples 1- 49, or any other method or process described herein.

Example 52 may include an apparatus comprising logic, modules, and/or circuitry to perform one or more elements of a method described in or related to any of examples 1- 50, or any other method or process described herein.

Example 53 may include a method, technique, or process as described in or related to any of examples 1- 50, or portions or parts thereof.

Example 54 may include an apparatus comprising: one or more processors and one or more computer readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- 50, or portions thereof.

Example 54 may include a method of communicating in a wireless network as shown and described herein.

Example 55 may include a system for providing wireless communication as shown and described herein.

Example 56 may include a device for providing wireless communication as shown and described herein.

Example 57 may comprise a non-transitory machine-readable medium having instructions, stored thereon, that, when executed cause an electronic device to perform one or more elements of a MME or PCRF entity described in or related to any one of examples 1-50 and/or any other examples described herein.

Example 58 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 MME or PCRF entity described in or related to any one of examples 1-50 and/or any other process described herein.

Example 59 may include a method of communicating in a wireless network 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 one of examples 1-50 and/or any other method or process described herein.

Example 60 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 one of examples 1-50 and/or any other embodiments described herein.

Example 61 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 one of examples 1-50 and/or any other embodiments described herein.

Example 62 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1 to 50, or any other method or process described herein.

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 4-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.