Methods and system for dynamic spectrum arbitrage policy driven quality of service.
Abstract
A dynamic spectrum arbitrage (DSA) system includes a dynamic spectrum policy controller (DPC) and a dynamic spectrum controller (DSC) that together dynamically manage the allocation and use of resources (e.g., spectrum resources) across different networks. The DSC component may include wired or wireless connections to eNodeBs, a policy and charging rules function (PCRF) component/server, and various other network components. The PCRF may be configured to receive eNodeB congestion state information from the eNodeB, information identifying wireless devices attached to the eNodeB, categorize each of the identified wireless devices into a category selected from a plurality of categories, select a subset of the identified wireless devices based on the category into which they are categorized, and perform congestion response operations on the selected wireless devices so as to reduce the congestion of the eNodeB.

Term
7.7 yearsleft in the term
Expires 27 May 2034.
- Priority
- Filed
- Granted
- Today
- Expires
13 claims: 4 independent, 9 dependent
- 1REIVINDICACIONES Habiéndose descrito la invención como antecede, se reclama como propiedad lo contenido en las siguientes reivindicaciones:1. Un método para reducir congestión de un nodo eNodeB implementado en una primera red de comunicaciones que participa en arbitraje de espectro dinámico (DSA) a través de un servidor de la función de política y reglas de facturación comunicaciones, se implementa en la primera red de el método caracterizado porque comprende: desde el recibir, en un nodo eNodeB, procesador información del del servidor de nodo eNodeB PCRF que incluye: información del estado de congestión del nodo eNodeB;e información que identifica dispositivos inalámbricos incorporados al nodo eNodeB;identificar, por el procesador del servidor de PCRF, un primer subconjunto de los dispositivos inalámbricos incorporados como suscriptores a la primera red de comunicaciones: identificar, por el procesador del servidor de PCRF, un segundo subconjunto de los dispositivos inalámbricos 189 incorporados como suscriptores a una segunda red de comunicaciones que participa en las operaciones de DSA: clasificar, por el procesador del servidor de PCRF, el primer subconjunto identificado dentro de una categoría de dispositivo primario;clasificar, por el procesador del servidor de PCRF, el segundo subconjunto identificado dentro de una categoría de dispositivo secundario;determinar si cualquiera de los dispositivos inalámbricos clasificados en la categoría de dispositivo secundario son propensos a crear congestión;clasificar adicionalmente los dispositivos inalámbricos determinados para ser propensos a crear congestión dentro de una primera subcategoría: determinar si cualquiera de los dispositivos inalámbricos clasificados dentro de la categoría de dispositivo secundario incluyen aplicaciones de datos sensibles;clasificar adicionalmente los dispositivos inalámbricos determinados para incluir aplicaciones de datos sensibles dentro de una segunda subcategoría;determinar si cualquiera de los dispositivos inalámbricos clasificados dentro de la categoría de dispositivo secundario incluyen aplicaciones sensibles al retardo;clasificar adicionalmente los dispositivos inalámbricos determinados para incluir aplicaciones sensibles 190 al retardo dentro de una tercera subcategoría;seleccionar un tercer subconjunto de los dispositivos inalámbricos incorporados con base en la categoría y subcategorías dentro de las cuales se clasifican;y realizar operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB.
- 2El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB además comprende:impedir que nuevos dispositivos se incorporen al nodo eNodeB.
- 3El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos -.-MEF 191 IMPIf INSTITUTO MEXICANO Di LA FJoVIEDAI» tNÜL'STHUL incorporados al nodo eNodeB además comprende:impedir la creación de soportes adicionales por los dispositivos inalámbricos seleccionados.
- 4El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB además comprende:impedir mejoras del soporte de radio en el nodo eNodeB para los dispositivos inalámbricos seleccionados.
- 5El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB además comprende:determinar un emplazamiento de un dispositivo seleccionado;identificar un nodo eNodeB objetivo no congestionado con base en el emplazamiento determinado;y realizar operaciones de transferencia para efectuar una transferencia del dispositivo seleccionado al nodo eNodeB 192 X;·. njLrm/το MfxacAiÑQ ···— , v. p«la ΤΛ·., v .r * objetivo no congestionado.
- 6El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB además comprende modificar soportes para los dispositivos seleccionados con el fin de disminuir tasas binarias consumidas por los dispositivos seleccionados.
- 7El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican incorporados al nodo eNodeB soportes para los dispositivos liberar recursos consumidos seleccionados.
- 8El método de conformidad con la dispositivos inalámbricos además comprende suprimir seleccionados con el fin de por los dispositivos reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo ,.'.τ» 193 IMPI CKsmvrc msxjcang CtLA.««CniCAD eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB además comprende realizar operaciones de transferencia para efectuar la transferencia de los dispositivos seleccionados a un nodo eNodeB objetivo no congestionado en una red diferente a la de PCRF.
- 9El método de conformidad con la reivindicación 1, caracterizado porque la realización de operaciones de respuesta a la congestión en los dispositivos inalámbricos seleccionados con el fin de reducir la congestión del nodo eNodeB con base en las categorías y subcategorías dentro de las cuales se clasifican dispositivos inalámbricos incorporados al nodo eNodeB además comprende hacer que el nodo eNodeB elimine los dispositivos seleccionados.
- 10El método de conformidad con la reivindicación 1, caracterizado porque comprende además realizar operaciones de DSA que incluyen:determinar en un servidor de controlador de política de espectro dinámico (DPC) una cantidad de recursos de espectros de radiofrecuencias (RF) disponibles para 194 WSTíTV?G MÍJUCANO LA. ?¿U?IEOAD KWÜSTRÍM. recursos de espectro de RF disponibles de la primera red de comunicaciones para acceso y uso por dispositivos inalámbricos de la segunda red de comunicaciones;e informar a la segunda red de comunicaciones de que puede iniciarse el uso de recursos de espectro de RF asignados mediante la comunicación con un segundo servidor de DSC en la segunda red de comunicaciones.
- 11El método de conformidad con la reivindicación I, caracterizado porque comprende además:supervisar uso de recursos de red a través de un procesador del nodo eNodeB del nodo eNodeB;determinar a través del procesador del nodo eNodeB si el uso de recursos de red supera un valor umbral;restringir la creación de orígenes de nuevas sesiones de dispositivos inalámbricos incorporados al nodo eNodeB en respuesta a determinar que el uso de recursos de red supera el valor umbral;y restringir entregas de dispositivos inalámbricos adicionales al nodo eNodeB en respuesta a la determinación de que el uso de recursos de red supera el valor umbral.
- 12El método de conformidad con la reivindicación II, caracterizado porque comprende además:clasificar, por el procesador eNodeB, los dispositivos inalámbricos incorporados al nodo eNodeB en grupos de prioridad;195 TiHWl Ilililí I..;,—— _ cuando se restringe la creación de orígenes de nuevas sesiones de los dispositivos inalámbricos incorporados al nodo eNodeB en respuesta a la determinación de que el uso de recursos de red supera el valor umbral comprende restringir la creación de orígenes de nuevas sesiones de los dispositivos inalámbricos con base en los grupos de prioridad dentro de los cuales se clasifican los dispositivos inalámbricos.
- 13El método de conformidad con la reivindicación 12, caracterizado porque comprende además:determinar, por el procesador del nodo eNodeB si cualquiera de los dispositivos inalámbricos incorporados al nodo eNodeB se clasifican dentro del mismo grupo de prioridad;y enviar, por el procesador del nodo eNodeB, la información del nodo eNodeB al componente de PCRF en respuesta a la determinación de que los dispositivos inalámbricos incorporados al nodo eNodeB son clasificados dentro del mismo grupo de prioridad. 196 ΙΝΕΤΙΤΙΓΓΟ MEXICANO DE LA FP.CPlEfAD 1M?UST!UAL
Independent claims13
1,433 paragraphs in 73 sections, as filed
(54) Title: METHODS AND SYSTEM FOR DYNAMIC SPECTRUM ARBITRATION POLICY ORIENTED TO THE QUALITY OF SERVICE.
(54) Title: METHODS AND SYSTEM FOR DYNAMIC SPECTRUM ARBITRAGE POLICY DRIVEN QUALITY OF SERVICE.
(57) Summary
A dynamic spectrum arbitration system (DSA) that includes a dynamic spectrum policy controller (DPC) and a dynamic spectrum controller (DSC) that together dynamically manage the allocation and use of resources (eg, spectrum resources ) through different networks. The DSC component can include wired or wireless connections to eNodeBs nodes, a billing rule and policy function (PCRF) component / server, and various other network components. The PCRF function can be configured to receive eNodeB congestion status information from the eNodeB node, information identifying wireless devices incorporated into the eNodeB node, to classify each of the identified wireless devices into a category selected from a plurality of categories, select a subset of the identified wireless devices based on the category in which they are classified and perform congestion response operations on the selected wireless devices in order to reduce congestion of the eNodeB node.
(57) Abstract
A dynamic spectrum arbitrage (DSA) system includes a dynamic spectrum policy controller (DPC) and a dynamic spectrum controller (DSC) that together dynamically manage the allocation and use of resources (eg, spectrum resources) across different networks. The DSC component may inelude wired or wireless connections to eNodeBs, a policy and charging rules function (PCRF) component / server, and various other network components. The PCRF may be configured to receive eNodeB congestion state information from the eNodeB, information identifying wireless devices attached to the eNodeB, categorize each of the identified wireless devices into a category selected from a plurality of categories, select a subset of the identified wireless devices based on the category into which they are categorized, and perform congestion response operations on the selected wireless devices so as to reduce the congestion of the eNodeB.
IMPI í <5 t. I SF ', .. I, «Wñ *
PATENT TITLE No. 353239
Owner (s): RIVADA NETWORKS LLC
D micilio:
1755 Telstar Drive, Suite 300, Colorado Springs, Colorado, 80908, USA
<td>nomination:</td><td>METHODS AND SYSTEM FOR DYNAMIC SPECTRUM ARBITRATION POLICY ORIENTED TO THE QUALITY OF SERVICE.</td>
Classification:
CIP: CPC:
H04W16 / 06; H04W8 ^ 18,
H04W28 / 0247 ;. H04L41 / 0893; H04L47 / 122; H04W28 / 16; H04W28 / 0289;
H04W36 / 22; H04 -------- -------- H04W88 / 18; H04W28 / 08;
H04W72 / 0453
CLINT SMITH; PURNIMA Yes
Inventor (s):
<img file="MX353239B_D0001.tif" />
Number:
MX / a / 2015/016115
International SAMUEL SMITH:
2014
Validity: Twenty years - 7
Due Date: ffiayo 27, 2034
Expedition Date: January 5, 2018
The patent of referertf ^ septórga with funiíátnegto in Ic 'sajflfíi os and
In accordance with article'5® of the Law, the Industrial Property leaves the patent pending on its validity.<sup>* 1 </sup>from the preset date ^ b'EB la soHdtaeintwna<img file="MX353239B_D0002.tif" />go dg ^ jW ^^ ar »manrfe
Who subscribes to the present title loJhe & fwith foundation in the ^ qfeuéstgpíjrfai aÉdUÍlb 6 ° ftacciffim (Official Gazette of the Federation ¢ ****. +,) ^ 7/06/1991 «formed on 02í®8 / lSb4» / 10/1096, 26/25 / 01/2006, 06/05 / 2009,06 / 01 / 2010,10106 / 3 (). 10,26 / 06/2010, 27 / OV2012 O9 / OI4 / 2O12f artictiÚífM<sup>0</sup>, 3<sup>or</sup> betrayal and you
Regulations of the Mexican Institute djfíUj'rapieiiad fa ^ trtittW »(rf.QF i4 / 1Í / 1999, í AofttíadWel 01 # 7 / 5jp) 2; .16 items 1<sup>or</sup>, 3<sup>or</sup>. 4<sup>or</sup>, 5<sup>or</sup> fraction V subsection a). · ”® Sections l <III and 3tAtoWÜÍMlAÍ®ánit®« deHnstittad & fcfi 12/27/1999, amended on 10/10/2002, 29/0 ^ 1¾ Deputy Generals, Coordinator, Directors ** · Departmental and other subordinates of the Institute 08/04/2004 and 09/13/2007).
<img file="MX353239B_D0003.tif" />
<img file="MX353239B_D0004.tif" />
Number:
61/827,937 | <sub>r</sub> 4, and 59joe that of the Rropib ^ ad Industrial.
of twenty non-extendable efies, counted at current fer ^ hiuechos.
> 6th fractions III and 7th ¡HÍs zeená ^ íy of Industrial Property i / ÍÓ /> 996, 256/12/1997 ^ 17/05/1999, 01/26/2004, 06/16/2005, 3<sup>or</sup> fraction and / ínois © a), 4<sup>or</sup> and 12th fractions I and III of O1 # 7 / S0t »: 07/16/2004, 07/28/2004 and 09/07/2007); of Industrial Property (DOF ^ t® »Aa ^ do that delegates powers to the Directors is, Divisional Deputy Directors, Coordinators * 3JPCS¡ £ e << ran2 / 1999, amended on 02/04/2000, 07/29/2004,
This letter is signed with an advanced electronic signature (FIEL), based on articles 7 BIS 2 of the Industrial Property Law; 3 of its Regulations, and 1 section III, 2 section V. 26 BIS and 26 TER of the Agreement establishing the guidelines for the use of the Electronic Payment and Services Portal (PASE) of the Mexican Institute of Industrial Property, in the procedures indicated.
THE DIVISIONAL DIRECTOR OF PATENTS
NAHANNY CANAL REYES
<img file="MX353239B_D0005.tif" />
Original string;
NAHANNY MARISOL CANAL REYES | 00001000000403252793 | Administration Service
Tax | 1695 || MX / 2018/2556 | MX / a / 2015/016115 | PCT patent title | 1223 | GAGV | Page (s) | g4¡5NGr0q7acsmYMrbcsPVEtsgY =
Digital stamp:
e9D7TdRhCyl9wUMeXWBpxc1AUz / M4 / s0UQIwKUjlNkCnbjbYx6K8HfocPou8SNrM68nr4lw4TszW5ku0LIVQD0zm9W / wMLJOZmR9UaquVZ + V67k4mz0K99pVIVJj4Q AsFRf1jY0 + + + CdD7GStaD M8FMGj4iqfabjoLka8hS / fjsKR5NDVT1D 8f2OCKkX / K5w60Oohds¡V9j + gbHDsU / T06vOvts2LoF7MXbNMp / 2oVfZ + WVFA / NahGYJmZ / sZXwLd1Pe4NOCtwlnGS SEza5WMcrTTvArS1EpSSddNKIOpucjSwTJDkHMz8Z4TBhU4nmvUSn9FCf2CzRpy / == dujZZWOw
<img file="MX353239B_D0006.tif" />
.Arenal No 550. Floor 1, Pueblo Santa María Tepepan, Xochimilco. 16020.
Mexico City.
(55) 53340700 www.gob.mx/impi
MX / 2018/2556
<img file="MX353239B_D0007.tif" />
353237
<img file="MX353239B_D0008.tif" />
TOÍU-UTO MEXICANO v <t <.....— '* -T
OF THE EROPHTEDAD V '? 'í ·', ·
INDUSTSUL ·
METHODS AND SYSTEM FOR SPECTRUM ARBITRATION POLICY
DYNAMIC ORIENTED TO THE QUALITY OF THE SERVICE
Background of the invention
With the increasing use of wireless communication devices to access networks and download large files (eg video files), there is an increasing demand for radio frequency spectrum. Smartphone users complain about call elimination, slow Internet network access, and similar issues that are largely due to too many devices trying to access finite radio frequency (RF) bandwidth allocated to services . However, parts of the RF radio spectrum, such as RF bands dedicated to the emergency service (eg, police, fire, etc.), are largely unused due to the non-continuous and episodic use of the bands. voice-radio communications. Thus, improving methods and solutions for dynamically allocating underused telecommunication resources (eg, RF spectrum, etc.) from a first telecommunication network for access and use by wireless devices subscribing to other networks. will be beneficial for telecommunication networks, service providers and for users of
Ref. 261728 telecommunications.
<img file="MX353239B_D0009.tif" />
Summary of the Invention
<img file="MX353239B_D0010.tif" />
The various forms of modality include methods of intelligently reducing congestion of an eNodeB node by using a billing rule and policy function server (PCRF) by receiving congestion status information from the eNodeB node on a processor from a PCRF server, receiving of information that identifies wireless devices incorporated into the eNodeB node, the categorization of each of the identified wireless devices into a category selected from a plurality of categories (a primary device category, a secondary device category, etc.), selecting a subset of the identified wireless devices based on the category in which they are classified and the mode of congestion response operations on the selected wireless devices in order to reduce congestion of the eNodeB node. In one form of modality, the mode of congestion response operations on selected wireless devices in order to reduce congestion of the eNodeB node may include preventing new devices from joining the eNodeB node. In another form of mode, the mode of congestion response operations on the selected wireless devices in order to reduce congestion of the eNodeB node
<img file="MX353239B_D0011.tif" />
prevent the creation of additional media @ by Pog .........
selected wireless devices.
In another form of modality, the method may include categorizing the identified devices into one or more subcategories (eg, devices that tend to create congestion, etc.) and selecting the subset of the identified wireless devices may Include selection of the subset of wireless devices based on category (eg, primary, secondary, or both classes at the same time) and the one or more subcategories into which they are classified. In another form of modality, categorizing the identified devices into one or more subcategories may include determining whether some of the identified wireless devices are prone to congestion, determining whether any of the identified wireless devices include applications of sensitive data and the determination of whether the identified wireless devices include delay sensitive applications. In a modality form, the classification of devices identified in one or more subcategories may include classifying the category of wireless devices into one or more of the congestion prone subcategory, a data sensitive subcategory, and a sensitive subcategory. to delay.
<img file="MX353239B_D0012.tif" />
In another form of modality,
IMPI
MEXICAN INSTITUTE OF PROPERTY <sub>Ί</sub> j <sub>Ί</sub> · Jjj INDUSTRIAL congestion response operations mode on “Selected wireless devices in order to reduce eNodeB node congestion may include preventing enhancements to radio supports on the eNodeB node for selected wireless devices. In another form of mode, the mode of congestion response operations on selected wireless devices in order to reduce congestion of the eNodeB node may include determining a location of a selected device, the identification of an uncongested target eNodeB node based on the determined location and the mode of transfer operations to transfer the selected device to the uncongested target eNodeB node.
In another form of mode, the mode of congestion response operations on the selected wireless devices in order to reduce the congestion of the eNodeB node may include modifying the supports for the selected devices in order to decrease the bit rates consumed. by selected devices. In another form of mode, the mode of congestion response operations on selected wireless devices in order to reduce congestion of the eNodeB node may include removing media for the devices
<img file="MX353239B_D0013.tif" />
• MEXICAN PROPERTY INSTITUTE in order to free up resources consumed by selected 1W.
In another form of mode, the mode of congestion response operations on the selected wireless devices in order to reduce the congestion of the eNodeB node may include performing transfer operations (or giving / instructing an eNodeB node to perform operations Transfer) to transfer the selected devices to an uncongested target eNodeB node on a different network than the PCRF. In another form of mode, the mode of congestion response operations on the selected wireless devices in order to reduce the congestion of the eNodeB node may include causing the eNodeB node to remove the selected devices.
In another form of embodiment, the method may include determining at a Dynamic Spectrum Policy Controller (DPC) server an amount of Radio Frequency Spectrum (RF) resources available for allocation within a first communication network that includes the PCRF server and the eNodeB node communicating with a first Dynamic Spectrum Controller (DSC) server in the first communication network. In another form of modality, the method may include the allocation by the DPC server of a portion of spectrum resources.
<img file="MX353239B_D0014.tif" />
access and use by first communication network for wireless devices of a second communication network and inform the second communication network that the use of allocated RF spectrum resources may be initiated, such as communicating with a second DSC server in the second communications network.
In another form of embodiment, the categorization of each of the identified wireless devices may include the categorization of the wireless devices of the second communication network in the secondary device category. In another form of modality, the method may include monitoring the use of network resources on an eNodeB node processor of the eNodeB, determining on the eNodeB node processor whether or not the use of network resources exceeds a threshold value and restrict the origins of new sessions of wireless devices incorporated into the eNodeB node and the restriction of deliveries of additional wireless devices to the eNodeB node in response to the determination that the use of network resources exceeds the threshold value.
In another form of modality, the method may include classifying the wireless devices incorporated into the eNodeB node into priority groups by the processor of the eNodeB node and restricting the origins of new sessions • ΙΜΡΐ instituto Mexicano '· D £ LA PROPiSDAO de los wireless devices built into the
<img file="MX353239B_D0015.tif" />
may include restricting origins of new ”áétÜUIl'tib '' ile— wireless devices based on priority groups. In another form of embodiment, the method may include s en di n g the eNodeB node processor congestion status information from the eNodeB node and information identifying the wireless devices attached to the eNodeB node in response to the determination that the embedded wireless devices The node eNodeB belong to the same priority group.
Other modality forms may include a PCRF server computing compute device that includes a processor configured with instructions.
<img file="MX353239B_D0016.tif" />
include processor
<img file="MX353239B_D0017.tif" />
<img file="MX353239B_D0018.tif" />
czar
<img file="MX353239B_D0019.tif" />
<img file="MX353239B_D0020.tif" />
<img file="MX353239B_D0021.tif" />
<img file="MX353239B_D0022.tif" />
node congestion status reception information
<img file="MX353239B_D0023.tif" />
incorporated into an eNodeB node, the classification into categories of each of the identified wireless devices into a category selected from a plurality of categories, the plurality of categories including a category of the primary device and a category of secondary device, selecting a subset of the identified wireless devices based on the category in which they are classified and the mode of congestion response operations on the
<img file="MX353239B_D0024.tif" />
<img file="MX353239B_D0025.tif" />
<img file="MX353239B_D0026.tif" />
MEXICAN INSTITUTE OF PROPERTY selected wireless devices with eNodeB node congestion.
In a form of mode, the processor may be configured with executable instructions per processor to perform operations such that congestion response mode of operation on selected wireless devices to reduce congestion of the eNodeB node may include preventing new devices join the eNodeB node. In another form of mode, the processor may be configured with executable instructions per processor to perform operations such that the congestion response mode of operation on selected wireless devices in order to reduce congestion of the eNodeB node may include preventing congestion. creation of additional media by selected wireless devices.
In another form of embodiment, the processor may be configured with executable instructions per processor to perform operations that further include categorizing the identified devices into one or more subcategories where selection of the subset of the identified wireless devices may further include , the selection of the subset of wireless devices based on the category and the one or more subcategories in which they are classified. In
X another form of modality, the pufedj processor to -
<img file="MX353239B_D0027.tif" />
instructions executable by 'PUTU' process Te-at-rza-r'operations such as categorizing identified devices into one or more subcategories that may include determining whether any of the identified wireless devices are likely to create congestion, determining whether or not any of the identified wireless devices include sensitive data applications and determining whether or not any of the identified wireless devices include delay sensitive applications.
In another form of embodiment, the processor may be configured with executable instructions per processor to perform operations such as performing congestion response operations on selected wireless devices to reduce congestion of the node. ENodeB may include preventing media enhancements from radio on the eNodeB node for the selected wireless devices. In another form of embodiment, the processor may be configured with executable instructions per processor to perform operations such as performing congestion response operations on selected wireless devices to reduce node congestion. ENodeB may include determining a location of a device s chosen, tí · τ r \ '> ¡T
I hee ί
MEXICAN INSTITUTE identification of a target eNodeB node ffó ^ M & énaíge
<img file="MX353239B_D0028.tif" />
based on location <sup>n;</sup>1<sup>Hri</sup> And — rmliaa ».— transfer operations to transfer the selected device to the uncongested target eNodeB node.
In another form of embodiment, the processor may be configured with executable instructions per processor to perform operations such as performing congestion response operations on selected wireless devices to reduce node congestion. ENodeB may include modifying media for selected devices in order to reduce the binary rates consumed by the selected devices. In another form of embodiment, the processor may be configured with executable instructions per processor to perform operations such as performing congestion response operations on selected wireless devices to reduce node congestion. ENodeB may include removing media for selected devices in order to free up resources consumed by the selected devices.
In another form of embodiment, the processor may be configured with executable instructions per processor to perform operations such as performing congestion response operations on selected wireless devices to reduce node congestion. ENodeB may include
IM 12 Ti (.
Ha _TO. _iL 1L t MEXICAN INSTITUTE '. US.LA PWIEPAO conduct Hoásitíans operations
<img file="MX353239B_D0029.tif" />
for transfer of lOS di spng-j fivric aolarrinnarln.q to ..... I ^ n node eNodeB target not congested in a different network than PCRF. In another form of mode, the processor mode can be configured with executable instructions per processor to perform operations such as congestion response operations on selected wireless devices for the purpose of node congestion eNodeB may include making devices reduce the node eNodeB drop down to selected devices.
Other modes of embodiment include a system that includes an eNodeB node and a PCRF server compute device that has a PCRF processor that is coupled to the eNodeB node via the communications link. The PCRF processor can be configured with executable instructions per processor to perform operations that include receiving the congestion status information from the eNodeB node and information identifying the wireless devices attached to the eNodeB node from the eNodeB node, categorizing them into each one of
<td colspan="2">wireless devices</td><td>identified</td><td>in</td><td>a category</td>
<td>selected from</td><td>a</td><td>plurality</td><td>of</td><td>categories,</td>
<td>including plurality</td><td>of</td><td>categories</td><td>the</td><td>category of</td>
<td>primary device and</td><td colspan="2">a category</td><td>of</td><td>device</td>
secondary, selecting a subset of the identified wireless devices
<img file="MX353239B_D0030.tif" />
MEXICAN INSTITUTE OF PROPERTY on the category in which they are classified '' and the modaliJa ^ -dg · ^ · congestion response operations on the selected wireless devices in order to reduce congestion of the eNodeB node.
Other modes of embodiment may include a computing device that includes a processor configured with executable instructions per processor to perform various operations corresponding to the methods described above.
Other forms of embodiment may include a computing device including various means for performing functions corresponding to the operations of the method described above.
Other modes of embodiment may include a non-transient processor readable memory medium having processor executable instructions memorized configured to cause a processor to perform various operations corresponding to the operations of the method described above.
Brief Description of the Figures
The accompanying figures, which are incorporated herein and constitute part of this specification of the invention, illustrate exemplary embodiments of the invention and, together with the general description
<img file="MX353239B_D0031.tif" />
MEXICAN INSTITUTE OF PROPERTY previously provided and the detailed description 'KMSSá'
<img file="MX353239B_D0032.tif" />
Then, they serve to explain caradserí-ateícete 'ete - ^ - l-ainvention.
Figures ΙΑ-1E inclusive are system block diagrams illustrating various logical and functional components and communications links in communications systems that can be used to implement the various modes of embodiment.
Figure 2A is a processing flow diagram illustrating a resource allocation dynamic spectrum arbitration (DSA) methodology from the perspective of a dynamic spectrum policy controller (DPC) in accordance with one form of modality.
Figure 2B is a message flow diagram illustrating message communications between components of a DSA communication system when resources are allocated in accordance with one form of mode.
Figure 3-7 inclusive are process flow diagrams illustrating a DSA method of allocating and accessing resources in a communication system that includes a DPC, two dynamic spectrum controllers (DSCs), and a wireless device.
Figures 8A-8C inclusive are message flow diagrams illustrating a dynamic spectrum allocation (DSAAP) application parts registration method of a: luι
<img file="MX353239B_D0033.tif" />
<img file="MX353239B_D0034.tif" />
modality form
Figures 9A and 9B are TrU ^ CSfl'S diagrams illustrating one embodiment of the DSAAP warning method.
Figures 10Ά and 10B are message flow diagrams illustrating a modality form DSAAP method for communicating a list of available resources.
Figures 11A and 11B are message flow diagrams illustrating a DSAAP bidding method in one embodiment.
Figures 12A-12D inclusive are message flow diagrams illustrating a DSAAP notification method in a modality way to inform participating networks of the results of bidding operations.
Figures 13A and 13B are message flow diagrams illustrating a method of purchasing DSAAP in a modality way for immediate (or almost immediate) acquisition of a resource.
Figures 14A and 14B are message flow diagrams illustrating a DSAAP allocation method in a modality way to allocate resources in a lessor network for component access and use in a tenant network.
Figures 15A and 15B are message flow diagrams illustrating a DSAAP reservation method in a .'JK-ϋ selective management mode through
ί.
<img file="MX353239B_D0035.tif" />
ίΝΪΤίΤ'Λ'Ο MEXICAN D2 L \ WIRELESS PROPERTY from a '-' Landlord-to-tenant network (ie, a base PLMN).
Figure 16A is a message flow diagram illustrating a DSC in a modality form that is initiated by the DSAAP de-registration method for termination of DSA operations.
Figure 16B is a message flow diagram illustrating a DPC initiated DSAAP de-registration method in a modality way to terminate DSA operations.
Figure 17A is a message flow diagram illustrating a DSC-initiated DSAAP error indication method for error reporting.
Figure 17B is a message flow diagram illustrating a DPC initiated DSAAP error indication method for error reporting.
Figure 18 is an activity diagram illustrating the operations and information flows between various components in a communication system when performing a DSA resource update method.
Figures 19 and 20 are process flow diagrams illustrating DSA methods of one form of resource allocation and deallocation mode between different networks.
Figure 21 is a process flow diagram illustrating a method an eNodeB node in: IMPIO *
MACANO INSTITUTE for level control a f corpa, according to the invention.
Figure 22 is a process flow diagram illustrating a method of reducing the congestion level of an eNodeB node based on device categories or priorities in accordance with an embodiment of the invention.
Figure 23 is an illustration of various exemplary congestion response operations that can be performed in response to the determination that the eNodeB node is congested.
Figures 24-31 are process flow diagrams illustrating congestion response methods, in one form of modality, to reduce the level of congestion of an eNodeB node.
Figure 32 is a component block diagram of an exemplary wireless device suitable for use with the various forms of embodiment.
Figure 33 is a component block diagram of a server suitable for use in an embodiment.
Detailed description of the invention
The various forms of embodiment will be described in detail with reference to the accompanying figures. Wherever possible, the same reference numbers will be used to
<img file="MX353239B_D0036.tif" />
<img file="MX353239B_D0037.tif" />
through all the figures to refer to identical or similar parts.
References made to particular exemplary embodiments and embodiments are for illustrative purposes and are not intended to limit the scope of the invention or the claims.
As used herein, the terms wireless device, wireless device, and user equipment (UE) may be used interchangeably and refer to any of several mobile phones, personal data assistants (PDAs), laptops, laptops with wireless modems , wireless email receivers (eg, Blackberry® and Treo® devices), mobile phones enabled to use Internet multimedia (eg, iPhone®) and similar personal electronic devices. A wireless device can include a programmable processor and memory. In a preferred embodiment, the wireless device is a cellular portable device (eg, a wireless device), which can communicate via a cellular telephone communication network.
<td colspan="3">As used</td><td>in this</td><td colspan="3">patent application,</td>
<td>terms</td><td colspan="2">component,</td><td>module,</td><td>engine,</td><td>manager</td><td>is it so</td>
<td>planned</td><td>for</td><td>include</td><td>to one</td><td>entity</td><td>related</td><td>with</td>
computers, such as, without limitation, hardware, firmware, or a combination of hardware and software, running software, or software that are configured to
<img file="MX353239B_D0038.tif" />
s
MEXICAN INSTITUTE OF REAL PROPERTY ÍW * f un¡ or particular operations. By way of example Wipió, UTl ü'üiilpünente can be, without limitation, a process that runs on a processor, a processor, an object, an executable program, a computer execution device, a program, a computer, a server, hardware network etc. By way of illustration, an application running on a computing device and the computing device may be referred to as a component. One or more components can reside within an executing process and / or device and a component can be located in a processor or processing core and / or distributed between two or more processors or cores. Furthermore, these components can be run from non-transient computer readable media that have various instructions and / or data structures memorized.
Several different cellular and mobile communication services and applicable standards are available or contemplated in the future, and they can be fully implemented and benefit from the various forms of modality. Services and standards include, for example, the 3 association project<sup>to</sup> generation (3GPP), long-term evolution systems (LTE), wireless 3 mobile communication technology<sup>to</sup> 4th generation (3G) wireless mobile communication technology<sup>to</sup> generation (4G), global system for mobile communications (GSM), «I
IMPIOS
MEXICAN INSTITUTE '
PROPERTY Universal Mobile Telecommunications (UMTS), 3GSM<sup>1</sup>^<sup>ÜST</sup>S<sup>i</sup>ferv5t: ibsr 'packet radio communication us code division multiple access (CDMA) system (eg cdmaOne, CDMA2000TM), best data transmission rate for evolution system
GSM (EDGE), Advanced Mobile Phone System (AMPS), Digital AMPS (IS-136 / TDMA) Optimized Evolving Data Service (EV-DO) Digital Enhanced Wireless Telecommunications (DECT) Global Interoperability for Microwave Access (WiMAX) wireless local area network (WLAN), public switched telephone network (PSTN), WiFi protected access I and II (WPA, WPA2), Bluetooth®, integrated digital enhanced network (iden), land mobile radio (LMR) and evolved universal land radio access network (E-UTRAN).
Each of these technologies involves, by way of example, the transmission, reception of voice, data, signaling and / or content messaging. It should be understood that any terminology references and / or technical details related to an individual telecommunication standard or technology are for illustrative purposes only and are not within the scope of the claims for particular communications or technology intended.
<td colspan="3">to limit the</td>
<td>a</td><td>system</td><td>of</td>
<td>not</td><td>be that</td><td>I know</td>
A high priority in the response to any emergency or disaster situation is established for communications specifically indicated in the text of the claims.
effective
In disaster situations
<img file="MX353239B_D0039.tif" />
scale (natural and artificial), is fnndampnt-al mar.tpnpr_ ..
communications between all first responders and emergency personnel in order to effectively respond, manage and control the emergency situation. In the absence of effective communication between first responders and other emergency personnel, resources may not be effectively mobilized for the areas that need the most resources. Even in minor emergencies (eg, road accidents and fires), first responders must be able to request support equipment and coordinate tasks with other services (eg, utilities, hospitals, etc.).
With the ubiquity of ownership and use of wireless devices, emergency communication over wireless devices using commercial cellular communication networks is often the most efficient and cost-effective means of mobilizing emergency response personnel and resources. Enabling wireless devices to provide effective emergency communications obviates the technical challenges and expense of coordinating radio frequencies between various primary responding agencies (eg, police, fire, ambulance, FEMA, utilities, etc.). Also, the first responders
<img file="MX353239B_D0040.tif" />
MEXICAN INSTITUTE qualified to an accident that are outside of
<img file="MX353239B_D0041.tif" />
ordinarily provided with __ devices.
retired doctors, nurses, police officers, or military personnel) will have or can quickly borrow a wireless device.
Emergency communications through cellular communication networks are not without problems, however. Cellular networks and other telecommunications networks (networks) are designed to support access demands from only a fraction of the total number of wireless devices in a particular cell.
In times of emergency or crisis, resources may be overwhelmed when the predictable human network resources for the situation request an extraordinary number of wireless device users within a particular cell to access the network at the same time.
Wireless device users may be trying to notify emergency personnel of the emergency situation (such as an emergency call to 911) or to alert friends or family members that the user is in a safe condition despite being in the area of an emergency situation. Some users may be transmitting images of the emergency situation (fire, accident, etc.) to friends or news services. In a large-scale situation, respondents from
<img file="MX353239B_D0042.tif" />
Wireless for emergency communications will be added, jad call volume. Be that as it may, the predictable increase in call volume during an emergency situation can overload a commercial cellular communications network, particularly in the cellular area encompassing the emergency area, rendering the network unreliable for use. of staff communications in an emergency response.
To overcome these and other limitations of solutions
<td>existing,</td><td>the various forms of modality include</td>
<td>components</td><td>configured to provide</td>
<td>access of</td><td>tiered priority (TPA) to deliver</td>
wireless device communications based on quality of service (QoS) and grade of service (GoS) for first responders. Detailed descriptions of TPA systems, by way of example, are disclosed in United States Patent No. 8,275,349 dated September 25, 2012, the entire contents of which are incorporated herein in their entirety and for all purposes.
In an overall view, a TPA system or solution may include multiple components configured to perform various TPA operations to coordinate, make available, and / or provide wireless communication resources to high-priority users (eg, emergency personnel) during times of high congestion or
<img file="MX353239B_D0043.tif" />
MEXICAN INSTITUTE DS INDUSTRIAL PROPERTY in emergency situation. As an example, the 'l'PA' components can be configured to monitor a wireless network call volume, to determine whether or not the wireless network call volume exceeds a first preset threshold, partition of wireless network resources based on priorities when the wireless network call volume exceeds the first predetermined threshold and to reserve a portion of the partition for resource usage
<img file="MX353239B_D0044.tif" />
wireless personal emergency
<img file="MX353239B_D0045.tif" />
devices
<img file="MX353239B_D0046.tif" />
components
<img file="MX353239B_D0047.tif" />
TPA can be configured
<img file="MX353239B_D0048.tif" />
monitor incoming and outgoing calls to determine if a call is made from or to a high-priority device (eg, to or from a preregistered wireless device or wireless devices from authorized emergency personnel), to allow general access to wireless network resources as long as no calls are made from or to a high-priority device and to restrict general access to wireless network resources in response to the determination that a call is made to or from a high priority device. Consequently, TPA solutions allow telecommunications systems to use more of the available resources and ensure that users have high priority.
In the various forms of modality and ^ - 'cotao' ^ = and - ^ - others. .
TPA operations can be performed in (or in conjunction with) a dynamic spectrum arbitration system (DSA) configured allocation, to dynamically manage access and resource usage of (eg, RF spectrum, etc.) between two or between a lessor network and a detailed system description network is given to
8,711,721 complete
DSA, know in the patent of themselves and for all dated April 29 incorporated here for the purposes.
of
In summary.
an availability system, telecommunications plus networks (eg, by way of example,
state
United n °
2014, whose reference in its integrity content
DSA may include a spectrum policy controller managing DSA configured dynamic operations (DPC) and interactions between two or more networks (eg, between a tenant).
various components through
The controller network of lessor and a network
DPCs can communicate with networks in a network provider network, one dynamic spectrum (DSC) networks, or more processor components that can be included in or added to DSA communications.
to eNodeBs nodes, a component / server of the
The Billing Policy and Rules Function (PCRF), and other components of DSC may include wired connections or
various networking components.
The
IMPI
MEXICAN INSTITUTE OF PROPERTY controladrfP<sup>USTB</sup>effec
<img file="MX353239B_D0049.tif" />
Communicate with the demand and / or receive resources component from other networks. This allows two or more networks to collaborate and make better use of their resources (eg, leased resources during times of high congestion, removing leased resources when not in use, etc.).
In various forms of modality, the DPC, DSC, PCRF, eNodeB and other network components can be configured to communicate and perform various operations that together provide DSA-TPA solutions that more efficiently manage the availability and use of the telecommunications resources and improve the priority of access to available resources. These components can also be configured to perform DSA-TPA operations to better account for detected network activity, user traffic, the nature of user / subscriber data usage, user profiles, and congestion levels. from two or more participating networks.
In one form of modality, an eNodeB node can be configured to classify or organize wireless devices into priority classes or groups, such as primary users (eg, first responders, network subscribers, etc.) and secondary users (p eg non-priority users, roaming devices, Lyu devices: I ll 1% ·
MEXICAN INSTITUTE OF PROPERTY VUsa.
Visitors who subscribe to other networks, et '^ and ^ EI ^ Method eNodeB can be configured to model the wwlvlda ^' tie '· id ^ of wireless devices based on priority groups / classes. In a form of mode, the eNodeB node can model network activity so that wireless devices that belong to a higher priority group are allocated a higher percentage of the available network resources (eg, bandwidth, etc.) when network activity increases.
Ά As an example, the DSA-TPA solution may include an eNodeB node configured to monitor network activity (eg, data or call volume, resource usage, congestion, number of active connections, etc.) to determine if network activity exceeds two or more thresholds. When network activity exceeds a first threshold, the eNodeB node can reserve radio resources for the primary user's wireless device. When network activity exceeds a second (or later) threshold, the eNodeB node can dynamically model the network activity of the secondary user's wireless device. Modeling the network activity of a wireless device may include the mode of operations to control one or more characteristics of the wireless communication link and / or the data being communicated, such as reducing bandwidth, reducing the quality of eNodeB, transfer information, etc.
Alternatively or additionally, the eNodeB node can be configured to monitor network activity and congestion levels at the Radio Access Network (RAN) level, to generate congestion status information based on monitoring and to send the generated congestion status information to a DSC controller and / or other network components. The eNodeB node can be configured to send congestion status information to the DSC controller and / or other network components on a periodic basis, in response to detection of congestion and / or in response to detection of a major change in congestion levels.
The congestion status information can identify a current congestion status (eg, normal, minor, major, critical, etc.) of the eNodeB node and / or other network components. Each congestion state can be associated with a level of congestion. As an example, a normal congestion state may indicate that a network component (eg, eNodeB node, etc.) is operating under normal load (eg, user traffic is within range). normal operations, etc.). A congestion state of Minor may indicate that the network component is experiencing congestion
A Mavor congestion status may indicate that the network component is experiencing significant congestion and / or operating under heavy load. A Critical congestion state can indicate that the network component is experiencing severe congestion, experiencing an emergency situation, or operating under extremely heavy load.
A first DSC controller in a first network can be configured to receive congestion status information from eNodeBs nodes in the first network and to send the congestion status information to a DPC component that is outside the first network. The DSC may also send the congestion status information to various components on the first network, such as a component of the PCRF function. In one embodiment, a PCRF component can be configured to receive congestion status information directly from the eNodeB node (eg, via a direct or indirect communication link).
In response to receiving the congestion status information from the eNodeB node, the PCRF component can classify, organize, or establish categories for any or all of the wireless devices incorporated into that eNodeB node (and / or other eNodeBs nodes in the same network) in one or more categories and subcategories.
<img file="MX353239B_D0050.tif" />
MEXICAN INSTITUTE
The <sup>D</sup> the ones that the PCRF function groups the devices can be the same as, different, dependent or independent of the classes or priority groups in which the eNodeB node classifies or organizes the wireless devices. As an example, the PCRF function can establish categories of wireless subscriber devices on the network (that is, wireless devices that subscribe to the network that includes the eNodeB node and the PCRF function) that join the eNodeB node. as primary device / users The PCRF function can categorize wireless devices that subscribe to other networks and are embedded in the eNodeB node as secondary devices / users.
In one form of modality, the PCRF function can be configured to further classify primary or secondary devices / users into one or more subcategories, such as users prone to congestion, users with data sensitive applications, users with delay sensitive applications , etc. In various forms of modality, the PCRF function can establish categories of devices / users in these and other subcategories based on network, resource, usage, device and / or user information, such as the data applications used by devices,
<img file="MX353239B_D0051.tif" />
<img file="MX353239B_D0052.tif" />
INSTITUTO MEXICANO subscription details of users, the<sup>OF</sup>! naaSr £ ^ and user computing, profiles ..... fifi, iiñiiatXQa., ..... operator policies, etc.
In various forms of modality, the PCRF function can be configured to perform various congestion response operations in response to receiving the eNodeB node congestion status information, in response to device category establishment, in response to the determination that the eNodeB node is congested or under heavy load and / or based on the current congestion status of the eNodeB node. The PCRF function can be configured to perform congestion response operations based on categories and / or subcategories to which the devices belong. As part of these operations, the PCRF function can communicate with various network components and / or perform various policy or control operations to perform various functions. These functions / operations may include interrupting or preventing the creation of additional supports to select devices incorporated into the eNodeB node, interrupting or preventing new devices from joining the eNodeB node, interrupting or preventing the improvement of the radio supports of selected devices, transferring selected devices to an uncongested eNodeB node on the same network as the eNodeB node
MEXICAN INSTITUTE congested on the basis of location decrease binary rates
<img file="MX353239B_D0053.tif" />
consumed by selected devices by modifying device media, deleting selected device media to free up resources, transferring selected devices to an uncongested eNodeB node on a different network based on device placement and tiered agreement of services with another network, the termination or removal of selected devices (eg, devices determined to contribute, to a greater extent at eNodeB node congestion levels) and other similar operations to mitigate or reduce the eNodeB node congestion level.
In various forms of modality, the PCRF function can be configured to perform these and other congestion response operations based on the priorities, categories, and subcategories associated with wireless devices. As an example, the PCRF function can cause the eNodeB node (or an execution node) to increase the termination / removal of wireless devices based on their associated priorities, categories and / or subcategories until user traffic or congestion at the eNodeB node returns to its normal condition (that is, until the eNodeB node returns to the Normal congestion state). That is, the PCRF function can make the eNodeB node (u before another component) remove all the devices & 'S ^^^^ tújdá ^ or ^ INDUSTRIAL
Start removing the devices from another example, the PCRF function can be primary.
do what
<td>than</td><td>I know</td>
<td>TO</td><td>mode</td>
<td>the</td><td>node</td>
eNodeB first remove the secondary devices that are classified in the congestion-prone users subcategory, and then delete the primary devices classified in the congestion-prone users subcategory before removing the remaining secondary devices.
The various forms of embodiment can be practiced within a variety of communication systems, examples of which are illustrated in the
Figures 1A-1E. Referring to Figure 1A, wireless devices 102 can be configured to transmit and receive voice, data, and control signals to and from a base station 111, which may be a Transceiver Base Station (BTS), NodeB node, eNodeB node , etc. Base station 111 may communicate with an access gateway 113, which may include one or more of a controller, a gateway, a service gateway (SGW), a packet data network (PGW) gateway, a gateway Evolved packet data (ePDG), a packet data service node (PDSN), a service GPRS support node (SGSN) or any similar component or combinations of their provided features / functions. Since you are
IMPIOS
MEXICAN INSTITUTE \ .. r- · vj,
OF THE PRGÍIEDAD> '
INDUSTRIAL structures are well known and / or examined in more detail
1 ^ ΜΒΜ1Μ · ιΙΜΊ — ΓΜΙΓΊ · * - '· -<sup>7</sup> a * · »below, some details from Figure 1A have been omitted in order to focus the descriptions on the most important features.
Access gateway 113 can be any logical and / or functional component that. serve as the primary entry and exit point for wireless device traffic and / or connect wireless devices 102 to your immediate service provider and / or packet data networks (PDNs). Access gateway 113 can forward voice, data and control signals to other network components such as user data packets, provide connectivity to data networks in external packets, manage and store contexts (eg, information internal network routing, etc.) and act as a fixing element between different technologies (eg, 3GPP and non-3GPP systems). Access gateway 113 can coordinate the transmission and reception of data to and from Internet network 105, as well as the transmission and reception of voice signals, data and control information to and from an external service network 104, Internet network 105 , other base stations 111 and wireless devices 102.
In various modes of embodiment, base stations 111 and / or access gateway 113 may be coupled (eg, via wired or wireless communication links)
IMPI
MEXICAN INSTITUTE
to. j. J. PROPERTY to a dynamic spectrum arbitration system
<img file="MX353239B_D0054.tif" />
configured to dynamically manage allocation, access, and use of various network resources (eg, spectrum of
RF, RF spectrum resources, etc.). The DSA system is discussed in detail below.
Figure IB illustrates that wireless devices 102 can be configured to send and receive voice, data and control signals to and from service network 104 (and ultimately Internet network 105) using a variety of communications systems / technologies ( eg, GPRS, UMTS, LTE, cdmaOne, CDMA2000TM), the totality or any of which can be supported by, or used to implement, the various modality forms.
In the exemplary embodiment illustrated in Figure IB, evolved universal terrestrial radio access network (E-UTRAN) and / or long-term evolution (LTE) data transmitted from a wireless device 102 is received by an eNodeB node 116 and are sent to a service gateway (SGW) 118 located within base network 120. The eNodeB node 116 may send signaling / control information (eg, information pertaining to call setup, security, authentication, etc.) to a mobility management entity (MME) 130). Entity MME 130 may request user / subscription information from a base subscriber server (HSS) 132, communicate with others
<img file="MX353239B_D0055.tif" />
<img file="MX353239B_D0056.tif" />
MME components, perform (eg, authentication of various user administrative tasks, enforcement of roaming restrictions, etc.), select a gateway
SGW 118 and send authentication and administrative information to the eNodeB node 116 and / or the SGW 118 gateway. Upon receipt of the authentication information from the MME entity 130 (eg, a complete authentication indication, an identifier of a selected SGW gateway, etc.), node eNodeB 116 can send received data from wireless device 102 to a selected SGW gateway 118. The SGW gateway 118 can store information about the received data (eg, IP support service parameters, internal network routing information, etc.) and forward user data packets to a control execution function Policy (PCEF) and / or Packet Data Network Gateway (PGW) 128.
Figure IB further illustrates that general packet radio service (GPRS) data transmitted from wireless devices 102 can be received by a base transceiver station (BTS) 106 and sent to a base station controller (BSC) and / or or packet control unit (PCU) as a component (BSC / PCU) 108. Code division multiple access (CDMA) data transmitted from wireless device 102 can be received by a base transceiver station 106 and sent to a data controller.
<img file="MX353239B_D0057.tif" />
base station (BSC) áPI
INSTITUTO MEXICANO Dt THE PROPERTY and / or a function component
<img file="MX353239B_D0058.tif" />
Packet (PCF) (BSC / PCF) 110. Universal mobile telecommunications (UMTS) data transmitted from a wireless device 102 can be received by a node
<td>eNodeB</td><td>112 and send to</td><td colspan="4">a radio network controller (RNC)</td>
<td> 114 .</td><td></td><td></td><td></td><td></td><td></td>
<td>The</td><td>components of</td><td>BSC / PCU</td><td>108, BSC / PCF</td><td> 110</td><td>and RNC 114</td>
<td>they can</td><td>process the</td><td>data</td><td colspan="2">from GPRS, CDMA</td><td>and UMTS,</td>
respectively, and send the processed data to a component within the 12 0 base network. More specifically, the BSC / CPU 108 and RNC 114 units can send the processed data to a serving GPRS support node (SGSN) 122 and the BSC / PCF 110 can send the processed data to a data service node in packets (PDSN) and / or a high-rate-packet data video signal gateway (HSGW) component called (PDSN / HSGW) 126 The PDSN / HSGW 126 can act as a connection point between the network Radio access and IP 128-based PCEF / PGW. SGSN 122 may be responsible for routing data within a service area of a particular geographic area and sending signaling information (control plane) (eg, information pertaining to call setup, security, authentication, etc. .) to an MME entity 130. The MME entity 130 can request user and subscription information from a base subscriber server
<img file="MX353239B_D0059.tif" />
<img file="MX353239B_D0060.tif" />
(HSS) 132, to perform various tasks, administer the user authentication, execute the law 'LcjjLLiLLiünes' ®? · Roaming, etc.), select an SGW 118 gateway and send administrative and / or authorization information to the SGSN node 122.
The SGSN node 122 may send the GPRS / UMTS data to a selected SGW gateway 118 in response to receiving authorization information from the MME entity 130. The SGW gateway 118 may store information about the data (eg, parameters IP support service, internal network routing information, etc.) and forward user data packets to the PCEF / PGW 12 8. The PCEF / PGW 128 can send signaling information (control plane) to a policy control rule function (PCRF) 134. The PCRF function 134 can access the subscriber databases, create a set of policy rules and perform other specialized functions (eg, interact with online / offline billing systems, application functions, etc.). The PCRF 134 function can then send the policy rules to the PCEF / PGW 128 for execution. The PCEF / PGW 128 can implement policy rules to control bandwidth, quality of service (QoS), data characteristics, and services that are in communication between service network 104 and end users. .
<img file="MX353239B_D0061.tif" />
<img file="MX353239B_D0062.tif" />
MEXICAN INSTITUTE
DE LA PROHEDA », INDUSTRIAL
<img file="MX353239B_D0063.tif" />
In the various modality forms, all or any of the components described above (eg T7 ~ components 102-134) may be coupled to, or included in, a DSA system configured to dynamically manage availability, allocation, access and use of telecommunication resources.
FIG. 1C illustrates various logic components and communication links in a one-mode 100 form system that includes a DSA 142 system and an evolved universal terrestrial radio access network (E-UTRAN) 140. In the illustrated mode, a As an example, in Figure 1C the DSA system 142 includes a Dynamic Spectrum Controller (DSC) component 144 and a Dynamic Spectrum Policy Controller (DPC) component 146. The E-UTRAN network 140 includes a plurality of interconnected eNodeBs nodes 116 coupled to the base network 12 0 (eg, via a connection to an MME, SGW, etc.).
In various forms of mode, the DSC 144 controller can be included or coupled to the E-UTRAN 140 network, as part of its base 120 network or outside of the base 120 network. In one form of mode, the DSC 144 controller can be directly coupled (eg, via wired or wireless communication links) to one or more eNodeBs 116 nodes.
The eNodeBs 116 nodes can be configured to communicate with the DSC 144 controller through the
<img file="MX353239B_D0064.tif" />
<img file="MX353239B_D0065.tif" />
<img file="MX353239B_D0066.tif" />
MEXICAN INSTITUTE OF PROPERTY
INDUSTRIAL interface / reference point Xe. In various forms of modality, the Xe reference point between DSC and eNodeB node 116 can use the DSAAP protocol, the
TR-069 and / or TR-192 data model extensions to support the listing of available resources on node eNodeB 116 and to notify node eNodeB 116 of offer / purchase confirmations. The DSC 144 controller can be configured to communicate with the DPC 146 controller via the interface / reference point Xd. The Xd reference point between DSC and DPC can use the DSAAP protocol for resource arbitration and dynamic spectrum operations. The eNodeBs 116 nodes can be interconnected and configured to communicate over. intermediate of an X2 interface / reference point, which can also use the DSAAP protocol to communicate information. The eNodeBs 116 nodes can be configured to communicate with the components in the base 12 0 network through the SI interface. By way of example, the eNodeBs 116 nodes may be connected to an MME entity 130 via the Sl-MME interface and to an SGW gateway 118 via the Sl-U interface. The SI interface can support a 'many-to-many' relationship between MME entities 130, SGW gateways 118, and eNodeBs 116 nodes. In a form of mode, the DPC and / or DSC controller can also be configured to communicate with a server component HS 132.
I Ί Mllll ... .1 ----------- 40
The eNodeBs nodes
116 they can
<img file="MX353239B_D0067.tif" />
providing protocol terminations give ριίηϋο ·· (eg PDCP, RLC, MAC, PHY) and Control Plane (RRC) to wireless device 102. That is, eNodeBs nodes 116 can act as a bridge (eg, Layer 2 bridge) between wireless devices 102 and base network 120 serving as the termination point for all radio protocols to wireless devices 102. and retransmission of voice signals (eg, VoIP, etc.) data and control to network components on base network 120. The eNodeBs 116 nodes can also be configured to perform various radio resource management operations, such as controlling the use of radio interfaces, allocating resources based on demands, prioritizing, and planning traffic according to various quality of service (QoS) requirements, monitoring the use of network resources, etc. Furthermore, the eNodeBs nodes 116 can be configured to collect the results of the measurements of the levels of radio signals, analyze the measurements of the level of collected radio signals and effect the transfer of wireless devices 102 (or connections to mobile devices). ) to another base station (eg, a second eNodeB node) based on the analysis results.
The DSC 144 and DPC 146 controllers can be
<img file="MX353239B_D0068.tif" />
components
IMPI
MEXICAN INSTITUTE
PROPERTY, INDUSTRIAL functional configured to manage resource process of different component operations, dynamic spectrum arbitration to share radio frequencies and other network resources between E-UTRAN 14 0 networks. As an example, the
DPC 146 can be configured to manage DSA and multi-network interactions
E-UTRAN establishing communication with controllers
DSC 144 on the E-UTRAN network.
Figure ID illustrates various logical and functional components that can be included in a communication system 101 that is suitable for use in the DSA mode of operations in accordance with various modes of mode. In the exemplary embodiment illustrated in Figure ID, the communication system 101 includes an eNodeB node 116, a DSC controller 144, a DPC controller 146, an MME 13 0 entity, an SGW gateway
118 and a PGW 128 gateway.
The eNodeB node 116 may include a DSC 150 application protocol and congestion monitoring module, an Inter-Cell Radio Resource Management (RRM) module 151, a Radio Support Control (RB) module 152, a module mobility control module 153, a radio admission control module 154, an eNodeB node measurement configuration and provisioning module 155 and a dynamically allocating resource module 156. Each of
<img file="MX353239B_D0069.tif" />
INSTITUTO MEXICANO, _,, DE LA PROPIEDAD these modules 15 0-156 can be implemented «N®HTRua in software or in a combination of hardware · and gmffrwara,
In addition, the eNodeB node 116 may include multiple protocol layers, including a radio resource control (RRC) layer 157, a packet data convergence protocol (PDCP) layer 158, a radio link control layer (RLC) 159, a media access control layer (MAC) 160 and a physical layer (PHY) 161. At each of these protocol layers, various hardware and / or software components may implement functionality that is compatible with the responsibilities assigned to that layer. By way of example, data streams may be received at physical layer 161, which may include a radio receiver, buffers, and processing components that perform demodulation, symbol recognition operations within the radio frequency (RF) signal, and to perform other operations to extract raw data from the received RF signal.
The DSC controller 144 can include an eNodeB 162 node geographic area border management module, an eNodeB 163 node resource and congestion management module, a Flow Control Transmission Protocol (SCTP) module 164, a module Layer 2 buffer (L2) 165 and a layer 1 buffer (Ll) 166. The DPC 146 controller may include a management module ι
-Λ
<img file="MX353239B_D0070.tif" />
eNodeB node resource offerings
167, a DSC controller communications module 168, a
SCTP / Diameter 169, an L2 buffer module
170 and a buffer module L1 171. The entity MME 130 may include a non-access layer security module (ÑAS) 172 and a mobility management module in idle state 173 and a system support control module in evolved packet (EPS) 174. The SGW gateway 118 may include a mobility setting module 176. The PGW gateway 128 may include a UE IP address allocation module 178 and a packet filtering module 179. Each of these 162-179 modules can be put into
<td>practice</td><td>in</td><td>hardware,</td><td>in software</td><td colspan="2">in a combination</td><td>of</td>
<td>hardware</td><td>and of</td><td>software.</td><td></td><td></td><td></td><td></td>
<td>The</td><td>node</td><td>eNodeB</td><td>116 can</td><td>set up</td><td>for</td><td>the</td>
communication with the SGW 118 gateway and / or the MME entity 130 through the SI interface / protocol. The eNodeB node 116 can further be configured for communication with the DSC controller 144 via the Xe interface / protocol. The DSC 144 controller can be configured for communication with the DPC 146 controller via the Xd interface / protocol.
The eNodeB 116 node can be configured to perform various operations (eg, via modules / layers
150-161) to provide various functions, including
<img file="MX353239B_D0071.tif" />
<img file="MX353239B_D0072.tif" />
functions for radio resource management, such cqtuq rnntjrol. ... of radio support, radio admission control, connection mobility control, dynamic resource allocation to wireless devices 102 uplink and downlink (scheduling) etc. These functions may also include compression and encryption of IP headers of user data streams, selection of an MME entity in connection to the UE when no routing to an MME entity 130 can be determined from the information provided by the UE equipment, routing of user plane data to the SGW 118 gateway, scheduling and transmission of paging messages (originating from the MME entity), the planning and transmission of broadcast information (originating from the MME entity), measurement and configuration of measurement reports for mobility and planning, the planning and transmission of public warning systems (eg, possible earthquake warning system and tsunami, commercial mobile alert services, etc.) through messages (originating from the MME entity), closed group subscriber group (CSG) management and marking of transport level packets on the uplink. In an embodiment, eNodeB node 116 may be a donor eNodeB node (DeNB) providing additional functions, such as one that is configured to perform multiple operations to
<img file="MX353239B_D0073.tif" />
<img file="MX353239B_D0074.tif" />
IT S1 / X2 proxy functionality, SGW / PGW gateway termination for support
MEXICAN INSTITUTE OF PROPERTY \? - · -_. I
INDUSTRIAL .....
Sil and / or ruinir · - functionality of relay nodes (RNs).
Entity MME 130 can be configured to perform various operations (eg, via modules 172175) to provide various functions, including Non-Access Stratum Signaling (ÑAS), ÑAS Signaling Security, Stratum Security Control access (AS), signaling between CN nodes for mobility between 3GPP access networks, UE reachability in idle mode (including search relay control and execution) tracking area list management (eg for a wireless device in idle and active mode), selection of PGW and SGW gateways, selection of MME for transfers with change of MME, selection of SGSN for transfers to 3GPP 2G or 3G access networks, roaming authentication, support management functions including specialized support establishment, support for public warning system (eg, earthquake and tsunami warning system, commercial mobile alert services, etc.), with transmission of the corresponding messages and optimization modality of the paging system. The MME module can also communicate various information on connection / disconnection states and device states to the DSC controller. In a form of modality,
<img file="MX353239B_D0075.tif" />
I will configure<sup>i,</sup>'not to
<img file="MX353239B_D0076.tif" />
the MME entity
130 can search messages based on CSG identifiers
IDs to the eNodeBs macro-nodes.
The SGW gateway 118 can be configured to perform various operations (eg, via module 176) to provide various functions, including mobility fixation (eg, for mobility between 3GPP), serving a fixation point of local mobility for transfers between eNodeBs nodes, buffering of downlink packets in E-UTRAN network idle mode, initiation of service demand procedures initiated by the paging network, legal interception, packet routing and forwarding, transport level packet marking on the uplink (UL) and downlink (DL), taking into account counts QoS class identifier (CQI) granularity for inter-operator billing, uplink (UL) and downlink (DL) billing (eg, per device, PDN and / or CQI), etc.
The PGW gateway. 128 can be configured to perform various operations (eg, via modules 178179) to provide various functions, including packet filtering on a per user basis (eg, deep packet inspection), legal interception , UE IP address assignment, packet marking
<img file="MX353239B_D0077.tif" />
<img file="MX353239B_D0078.tif" />
transport level on the uplink and downlink Billing of service levels in UL and DL, execution of the rate and separation functions by gates, execution of the DL rate based on the maximum aggregated binary rate of APN (AMBR) , etc.
The DSC controller 144 can be configured to perform various operations (eg, via modules 162166) to provide various functions, including managing arbitrage operations of resources within a network (eg, PLMN), monitoring of network resource listings, monitoring of current ongoing offers.
monitoring of executed offers and monitoring of offer-specific Closed Subscriber Group Identifiers (CSG) (CSG-IDs) for mobility management of wireless devices 102 leased in lessor networks. The DSC controller 144 can be configured to transfer wireless devices 102 from the tenant network to the lessor network (i.e. make deliveries) and transfer of wireless devices 102 from the lessor network back to the tenant network ( that is, carry out the operative withdrawal operation).
The DSC 144 controller can also be configured to track congestion states of eNodeBs nodes, to select target eNodeBs nodes for 58 transfers, and to manage
INSTITUTO MEXICANO Yí »THE PROPERTY the traffic in nBffis eNodeBs of the lessor.
The controller
DSC
144 can “'C.'OTtlIg'urarsé to download users based on configured policies (eg, download of lowest priority users, download of highest priority users, download of users with QoS quality of service specific, etc.) from tenant networks to other less loaded eNodeBs nodes 116 within a lessor network. The DSC controller 144 can also perform operational pull-out operations for transferring a wireless device 102 from the lessor's network back to the lessee's network. The DSC 144 controller can also be configured to monitor, manage, and / or maintain historical congestion information that is being collected or received from one or more eNodeBs nodes in the system.
DPC controller 146 can be configured to perform various operations (eg, via modules 167-171) to provide various functions, including operating as a resource arbitrage agent between DSC 144 controllers of tenant and tenant networks (eg, PLMNs), lists of resources from various lessor networks for auction and auction process management. DPC 146 Controller can be configured to send notifications of bid override, offer
<img file="MX353239B_D0079.tif" />
A MEXICAN INSTITUTE '¡.)
OF THE I ROriEPAD t <sup>K</sup> „R INDUSTRIAL ^ -4 —- won, bid cancellation and bid withdrawal and _____t u -: --—» «* -» · ιΗΛ '· tender to DSC 144 controllers, completion of to install specific billing rules of the offers in the online and / or offline billing systems of the lessee and lessor networks, and continue the use of resources between DSC 144 controllers acting as a gateway between the lessee and lessor DSC 144 controllers.
Figure 1E illustrates network components and information flows in an exemplary communication system 103 that includes two E-UTRANs networks 140a, 140b, interconnected by a DPC controller 146 configured to manage DSA operations and interactions. In the exemplary illustrated mode in Figure 1E, each EUTRAN 14 0a, 14 0b network includes an eNodeB node 116a, 116b that is outside of its base network 120a, 120b, and a DSC controller 144a,
144b that is within the base network 120a, 120b.
DSC controllers 144a, 144b can be configured to communicate with DPC controller 146 via the Xd interface. DSC 144a, 144b controllers can also be connected, directly or indirectly, to various network components on their respective base networks 120a, 120b such as PCRF 134, HSS 132 and a PCEF / PGW 128 (not illustrated in Figure 1E) . In a modality form, one or more of the DSC 144a, 144b controllers can be connected
IMPIr -. 'M
MEXICAN INSTITUTE
FROM V-INDUSTRIAL PROPERTY directly to one or more of eNodeBs 116a, 116b nodes.
In addition to the aforementioned communications connections and links, system 103 may include additional connections / links to support data flows and communications between components in different E-UTRANs networks (eg, E-UTRANs 140a, 140b). As an example, the system
103 it may include a connection / communication link between an eNodeB node 116b in the second E-UTRAN network 14 0b to an SGW gateway 118 in the first E-UTRAN network 14 0a. By way of another embodiment, system 103 may include a connection / communication link between an SGW gateway 118 in the second E-UTRAN network 140b to a PGW gateway 128 in the first E-UTRAN network 140a. To focus on the description of the relevant mode forms, these additional components, connections and communication links are not illustrated in Figure 1E.
As described in detail below, DSC drivers 144a, 144b can be configured to send information regarding the availability of spectrum resources (eg, information received from an eNodeB node, PCRF, PCEF, PGW, etc.) to the DPC controller 146. This information may include data regarding the current and expected future use and / or capacity of each network and / or subnet. The DPC 146 controller can be configured to receive and use the information to intelligently assign, transfer.
Ρ '' '· ΙΜΡϊν INSTITUTO MEXICANO \,'
OF PROtILDAP<sup>1</sup> V INDUSTRY!
manage, coordinate or lease the available resources of ______<sub>ί | Ι | ΒΓ</sub>—_, U ---- the first E-UTRAN 14 0a network to the second E-UTRAN 14 0b network and vice versa.
As an example, DPC controller 146 can be configured to coordinate the allocation of spectrum resources to the second E-UTRAN network 140b (i.e., tenant network) from the E-UTRAN network 140a (i.e., lessor network) as part of dynamic spectrum arbitration operations. The operations may allow a wireless device 102 to be connected wirelessly to the eNodeB node 116b in the second E-UTRAN network 14 0b via a communication link 143 to be transferred to an eNodeB node 116a in the first network E-UTRAN 140a so that you can use the allocated spectrum resources of the first E-UTRAN 140a network. As part of this transfer procedure, wireless device 102 can establish a new connection 141 to eNodeB node 116a on the first E-UTRAN network 140a, terminate wireless connection 143 to original eNodeB node 116b and use allocated resources from the first network E-UTRAN 140a as if they are included in the second E-UTRAN 140b network. DSA operations can be performed such that the first DSC controller 144a is a lessor DSC for a first resource / time period and a lessee DSC for a second resource / other time period.
In a form of modality the
<img file="MX353239B_D0080.tif" />
MACANO INSTITUTE
DE LA PRCHEÜAD ΐΝεςπϊΜΐ. operations
<img file="MX353239B_D0081.tif" />
Transfer and / or DSA can be performed so that '* ~ éT wireless device 102 maintains a data connection to (or a data connection to be managed by) the original network after it is transferred. By way of example, transfer and / or DSA operations can be performed such that wireless device 102 maintains a data flow connection to a PGW 128 gateway on the second E-UTRAN network 140b after being transferred to the eNodeB node 116a in the first E-UTRAN network 140a.
Figure 2A illustrates an exemplary DSA 2 00 method of resource allocation in accordance with one embodiment. Method 200 can be performed by a processing core in a DPC component 146 (eg, server computing device, etc.).
At block 202, DPC controller 146 can establish a first communication link to a first DSC 144a in a first communication network (eg, E-UTRAN, etc.). At block 204, DPC controller 146 can establish a second communication link to a second DSC 144b on a second communication network. At block 2 06, DPC controller 146 can determine if radio frequency (RF) spectrum resources are available for allocation within the second communication network. The above can be done using communicating with a DSC 144 in communications through communications, which can be a
IMPI ú
INSTITUTO MEXICANO DE LA PtOriCMO <INDUSTRIAL '' DSAAP protocol for the second wired or wireless communications link second link network. At block 208, the
146 You can determine the amount of resources that is available for your allocation. In the controller assign the available network access
In block 210 spectrum RF DPC controller, the and use
DPC 146 may perform all or part of the second network of various operations for the RF communications resources for it by the wireless device 102 in the first communications.
block 212, the controller communications message to the first DSAAP protocol) to report communications that the
DPC
DSC use assigned RF spectrum. In the block
146 can send a
144a (eg, using the first network of the
214, the controller
DPC 146 can record a transaction in a transaction database that identifies a quantity of RF spectrum resources allocated for use by the first communications network.
At block 216, DPC controller 146 can receive messages and include resources from a communications station from information indicating allocated and / or demanding that the second DSC 144b that has been consumed be released from the allocated resources. In block 218 the
<img file="MX353239B_D0082.tif" />
INSTITUTO MEXICANO DE LA MWIEDAD NDUSTEIAl controller DPC 146
<img file="MX353239B_D0083.tif" />
can send a resource consumed / release message to the first
DSC 144a to cause the first network to end its use of allocated resources.
Figure 2B illustrates information flows, by way of example, between a DPC 146 and a plurality of DSC controllers 144a-d when the DSA method 250 is performed in another mode of allocating resources. In the following description, the DSA 250 method is examined from the perspective of the DPC 146 component and can be performed by a processing core in the DPC 146 controller. However, it should be understood that the DSA method 250 may be performed by processing cores in a DPC component 146, processing cores in DSC components 144a-d, or one of its components. Furthermore, it should be understood that all interactions and communications between the DPC 146 and the other components can be accomplished through DSAAP components and / or using the DSAAP. Consequently, all interactions and communications can be included in the DSAAP protocol.
In operation block 252, a processing core in a DPC component 146 may receive a resource request communication message from a first DSC component 144a in a first network (eg, E-UTRAN, etc.) . It should be understood that the communication message of
Γ-C®.
•• V.
IMPI 'Mexican Institute' OF THE Γ-ΟΓ'ΓΠαΠ 'INDUSTRIAL
<img file="MX353239B_D0084.tif" />
communication demand examined resources and all other messages from
.. ΙΙΙ ···· | Ι · <sub>Λ></sub>.,.
in this application they can be DSAAP messages.
The resource request communication message may include suitable information to inform the DPC controller 146 that the first network is interested in the operations of buying, leasing, accessing and / or using resources from other networks. The resource demand communication message may also include adequate information to identify the types and / or amounts of resources (eg, RF spectrum resources, etc.) that are demanded by the first network, the types and capabilities of the wireless devices 102 to which the requested resources and other similar information will be allocated.
In operations 254, 256, and 258, DPC controller 146 can generate and send a resource probe communication message to each of a second DSC 144b component on a second network, a third DSC 144c component on a third network and a fourth DSC 144d component on a fourth network, respectively. The DPC controller 146 can be configured to generate the resource probe communication messages to include various component information, device and resource requirements, criteria and other information. As an example, DPC 146 may generate a resource probe communication message to
<img file="MX353239B_D0085.tif" />
<img file="MX353239B_D0086.tif" />
include information identifying the types, capabilities and geographic criteria of wireless user devices 102 in the first network (and other networks) to which resources are to be allocated. Geographic criteria may include a geographic location, a geographic polygon, and / or a license area for a wireless user device 102 to which resources will be allocated.
In operations 260 and 262, DPC controller 146 may receive communication messages responding to resource probing from second and third controller 144b, 144c. These resource probe response communication messages may include information that identifies the availability of excess resources that meet the requirements / criteria included in the resource probe messages. In operation block 264, DPC controller 146 may receive another resource probe response communication message from fourth DSC controller 144d. These resource probe response communication messages may include information indicating the fourth network does not include resources that meet the demanded criteria / requirements.
In a modality form, as part of operations
260-264, the DPC 146 controller can update a database record to identify the second and third networks
Mfi
ÍNiTáVF? MSUCAXO bl la; rx> r «OAB INDUSTRiAL as having resources available for allocation and / or to identify the fourth network as not including the resources.
In operation block 266, DPC controller 146 can generate and send a resource availability communication message to a plurality of DSC controllers on a plurality of networks, including the first DSC controller 144a on the first network. DPC controller 146 can be configured to generate resource availability communication message to include information that is appropriate to inform networks that resources are available for allocation. In one form of embodiment, DPC controller 146 can be configured to inform networks that resources are available for allocation by broadcasting a communication signal that includes appropriate information to inform networks that resources are available for allocation by auction and / or a start time for the auction.
In operation block 268, DP C c on troller 146 may receive a resource reservation request communication message from the first DSC controller 144a. The communication message received resource reservation request may include adequate information to inform the DPC controller 146 that the first network intends to participate in the auction and / or the offer in at least a part of the available resources.
<img file="MX353239B_D0087.tif" />
In operations 270
INSTITUTO MEXICANO 'y 272, el controía ^^ rw ^ PÍSliíj ^<sup>1</sup> You can send a resource reservation message to the second and third controllers
DSC 144b, 144c, respectively. The resource reservation request communication message may include appropriate information to make the second and third DSC controllers 144b, 144c reserve all or part of their available resources for allocation and use by other networks
In operations 274 and 276, DPC controller 146 may receive a resource reservation response communication message from each of the secon d and th ird DSC controllers 144b, 144c. The resource reservation response messages may include adequate information to inform the DPC controller 146 that the requested resources have been reserved and / or adequate information to identify the reserved resources.
Optionally, in operation block 278, DPC controller 14 6 can pool reserved resources for allocation and use by wireless devices 102 in other networks (eg ..
the first network). As an example, the DPC controller
146 you can combine a reserved spectrum block on the second network with a reserved spectrum block on the third network. By way of another example, DPC controller 146 may pool available resources on the first and fourth channels of a reserved spectrum block on the second network.
<img file="MX353239B_D0088.tif" />
MEXICAN INSTITUTE CE LA PROFIK / AX »INDUSTRIAL
<img file="MX353239B_D0089.tif" />
In operation block 2 80, controller 'DÍ'C ~ TW "' 'can receive resource offer communication messages from a plurality of networks, including from the first DSC controller 144a in the first network. Each resource offer communication message may include a tender or offer for the access, use, lease, and / or purchase operations of a resource as well as other related tender information (eg, pricing, allocation / access methods demanded , etc.). As part of operation 280, DPC controller 146 can determine whether the received resource offerings meet DSA system policies and rules and / or the requirements established by the networks offering the resources for allocation (eg, meet the minimum demand price, etc.).
In operation block 282, DPC controller 146 can accept the bid / offer from the first network in response to the determination that the resource offer received from the first network meets DSA system policies / rules and requirements by the resource supply network (eg, offers a monetary amount for the use of all or part of the resources in the pool of available resources that is greater than or equal to a minimum amount specified by the second network). Also in block 282, the
<img file="MX353239B_D0090.tif" />
acceptance of offer to the first DSC 144a controller ...................
In operation block 284, DPC controller 146 may allocate the resources of the second network for access and use by wireless devices 102 in the first network by sending a resource allocation request communication message to the second DSC 144b. That is, In operation block 284, the DPC controller can determine that the portion of the resources (eg, in the pool of available resources) gained by the first DSC 144a is fully available through the second network and in response, only send the resource allocation request message to the second network.
In operation block 2 86, DPC controller 146 may receive a resource assigned communication message from second DSC controller 144b. In operation block 288, DPC 146 may send the communication message assigned resources to the first DSC 144a to inform the first network that the resources have been allocated for access and used by its wireless devices 102 and / or that the use of the allocated resources can be started. In operation block 290, DPC controller 146 can record a transaction in a transaction database that identifies these resources as being allocated for access and use by the first network.
--/9
In the block
IMPI
MEXICAN INSTITUTE v / r - * '/
PROPERTY> _.
INDUSTRIAL 'of operations 292, the DPC controller 146 may receive a from the second DSC controller 144b that includes information that identifies that the allocated resources have been consumed and / or adequate information to demand that the
<td>allocated resources. I</td><td>on the</td><td>block</td><td>of</td><td>operations</td><td>294 the</td>
<td>DPC 146 controller</td><td>can</td><td>Send</td><td>a</td><td>Message from</td><td>resources</td>
<td>consumed / release</td><td colspan="2">resource</td><td>to the</td><td>first DSC</td><td>144a for</td>
<td>make the first</td><td>net</td><td>I finished</td><td>its</td><td>use of</td><td>resources</td>
assigned.
Figures 3 to 7 illustrate a DSA method 300 of one embodiment of allocating and accessing resources in a communication system including a DPC controller component 146, two DSC controller components 144a, 144b, and wireless devices 102. All of or parts of the DSA method 300 can be performed by processing cores on a DPC 146, DSC 144a-by / or wireless device 102. In the various forms of embodiment, all or any of the interactions and communications between components 146a, 144a, 144b and 102 can be performed or facilitated by DSAAP components and / or the use of the DSAAP protocol. Consequently, all interactions and communications can include in the DSAAP protocol.
Referring to Figure 3, at block 302, a first DSC controller 144a on a first network can
X.
MEXICAN INSTITUTE ......- ·
QE ua PRCTi Eva »O--. ~ -i- 'tí¿üuswAL monitor user traffic (eg, data and call traffic, etc.) compared to the total spectrum resources available for the first network. First DSC 144a can generate a report of block 304, the resource status based on a result of its monitoring, record / store the resource status report in memory and send a resource status report to the DPC controller 146 using a resource status report determination communication message. In the block
DSC 144a can determine, based on
306, the first reports the status of resources received, whether or not additional resources are required (and / or whether or not there is a high probability that additional resources will be required in order to provide appropriate service to the devices existing wireless 102 on the first network.
In response to the determination that resources are required, determination block 306 at block 308, the first DSC controller 144a may send a resource request communication message to the DPC
146. In response to the determination that no additional resources are required (i.e., the DSC controller determination block 306
144a may continue to monitor user traffic and / or perform other DSC operations at block 302.
In operation block 310, a second controller
<img file="MX353239B_D0091.tif" />
<img file="MX353239B_D0092.tif" />
1 * / λ
INSTITUTE M £ X <CANV> V-Λ ** '· DILAPR3PUDA & DSC 144b in a second network can supervise the ^ raíu. as a user compared to the totaTeá spectrum resources available to the second network, generate resource status reports and / or perform all or any of the DSC operations examined in this description. At determination block 312, the second DSC controller 144b can determine whether or not there is an excess amount of resources available on the second network. In response to the determination that there are no resources available in the second network (that is, in excess of determination block 312
No), at block 310, the second DSC controller 144b may continue to monitor user traffic and / or perform other DSC operations.
In response to determining that there is an excess amount of resources available on the second network (i.e., determination block 312 = Yes), at block 314, the second DSC controller 144b may dial, designate, or allocate all or parts of your excess resources for access and use by other networks (eg, the first network, etc.). At block 316, the second DSC controller 144b can generate a resource allocation report and send the generated resource allocation report to DPC 146 (eg, via a resource communication message). The DSC 144b controller can be configured to generate the resource allocation report to include information
IMPI
WrrUT-ι MEXICANO
C6ía «so« or »a» tNDUSTí / AL (or parts or quantities second <* 'Λ
K * that identifies the resources available for allocation have been marked, designated or assigned by the
At block 320, DPC controller 146 can receive resource status and allocation reports from DSC controllers 144 on numerous different networks, including the first and second DSC controllers 144a, 144b on the first and second networks. These reports may include information that identifies various characteristics, criteria, requirements, and conditions of networks and their components, such as the ratio of detected user traffic to total available spectrum resources, the amount of resources required by a network, the amount of resources that are available for allocation on a network, the types and capacities of the wireless devices 102 that will use the allocated resources, system requirements that must be met before wireless devices 102 access assigned resources, network rules and policies regarding access and use of resources and other similar information.
At block 322, DPC controller 146 can store received reports (eg, resource status reports, resource allocation reports, etc.) in memory (eg, nonvolatile memory). In block 324, the *
'.x »
IMP1 INSTITUTO MEXICANO DE LA PSOHJDAD INPVSTilA Controller DPC 146 may receive a demand for resources from the
In the block <sup>r</sup> F- · W. uf «; <· λ here DSC 144 controllers in different networks first DSC 144a controller in the first network.
326, the DPC controller 146 can use the received / memorized information (eg, information received on resource requests, resource allocation reports, resource status reports, etc.) to identify and select the most suitable network / best available from which the first network can lease or buy additional resources. In the exemplary embodiment illustrated in Figure 3, DPC controller 146 identifies and selects the second network as the most suitable network to provide resources to the first network.
At block 328, DPC controller 146 may send a resource probe communication message to second DSC controller 1144b. At block 330, the second DSC controller 1144b may receive the resource probe communication message. At block 332, the second DSC controller 1144b can determine the availability, amounts, and / or quantity of the excess resources that are marked, designated, or allocated by the second network. In block 334, the second DSC controller 1144b can generate and send a resource probe response communication message to the DPC controller 146. The second DSC controller 1144b can generate a response to, son, resource probe to include information
T Μ PJ r
JL .h. Uh
MEXICAN INSTITUTE «DELA? RO? IEDAD J;
In identifying availability, yvant 1 resources are marked, designated, or assigned for access and use by other networks (eg, the first network). At block 336, DPC controller 146 can receive the resource probe response communication message from second DSC controller 1144b and, in response, perform the operations of determination block 400 illustrated in Figure 4.
Referring to FIG. 4, in determination block 400, DPC controller 146 can determine if resources are available based on the data (eg, resource probe response message) received from the second DSC controller. 144b in the second network. As an example, DPC controller 146 may determine that the identified resources are not available in response to the determination that all or part of the resources were purchased or won by other bidders before they were reserved.
In response to determining that resources are not available (eg, determination block 400 = No), at block 402, DPC controller 146 may send a communication message of no available resources to the first DSC controller 144a on the first network. At block 404, the first DSC controller 144a may receive message t
<img file="MX353239B_D0093.tif" />
<img file="MX353239B_D0094.tif" />
communication without available resources. At block 406, the first DSC controller 144a can search (eg, via DPC controller 146) for other available resources, demand resources from a different network, demand different resources, terminate connections or communication sessions with users to free up resources or perform other similar operations to manage network traffic and congestion on the first network.
In response to determining that resources are available (that is, determination block 400 = Yes), at block 408, DPC controller 146 may send a communication message of available resources to the first DSC controller 144a. the available resources message may include information that can be used by the first DSC controller 144a to determine the quality and quantity of resources on the second network that can be used by wireless devices 102 on the first network.
In block 410, the first DSC controller 144a can receive the available resource communication message sent from DPC controller 146. In block 412, the first DSC controller 144a can determine the amount / amount of resources required by the first network and / or try to acquire and send this and other resource information to the DPC controller 146 in a communication message requesting resources.
In block 414, the controller message requesting DSC controller resources 144a. In the block
146 You can use included information to generate and send a resource reservation message to the second network.
At block 418, receive the message
IMPI ib.
MEXICAN INSTITUTE OF PROPERTY - industrial = ^ - * · DPC 146 can receive the
416, the DPC controller in the message received communication request for second DSC controller 144b in the second DSC controller 144b may request reserve resources from the DPC
146. At block 420, the second DSC controller 144b may use the information included in the resource reservation request message received to reserve the demand amount of resources allocated for access and use by components on other networks. At block 422, the second DSC controller 144b may send a reserved resource communication message to the DPC controller 146 to confirm that the requested quantity of resources has been reserved and / or to identify the reserved resources.
At block 424, DPC controller 146 may receive the resource reserved communication message from second DSC controller 144b. At block 426, DPC 146 may offer the reserved resources for auction and / or initiate the acceptance of resource offers on the reserved resources.
Figure 5 illustrates a tender procedure for the
MEXICAN INSTITUTE? <- i »f'M jh DB PROPERTY V
INDUSTRIAL X ^ V ** ^<sup>8</sup>* DSA 300 method that can be performed after DPC 146 offers reserved resources for auction and / or initiates acceptance of resource bids on reserved resources (eg, after performing block 426 operations illustrated) in Figure 4).
Referring to Figure 5, at block 500, the first DSC controller 144a in the first network can negotiate access to the reserved resources of the second network by sending a resource offer (eg, via a message communication) to the DPC controller 146. In the block
502, DPC 146 can receive the resource offer from the first DSC controller 144a.
In determination block 504, DPC controller 146 can determine whether the received resource offer is to be accepted, which can be done by determining whether or not the resource offer complies with DSA system policies and rules and the requirements of the second network (eg, is greater than a minimum amount, etc.). In response to determining that the offer of resources received from the first DSC controller 144a (i.e. determination block 504 = Yes) in block 506 is to be accepted, the DPC controller 146 may send a communication message of accept offer to the first DSC 144a controller. In block 508, the first DSC controller 144a may receive the accept offer message and wait for iflFfl · * access instructions: ·
IMPI (MEXICAN NSTITUTE I HEARD THE PBCnl'OAD C-IDUSnUAL to resources. In block 510, the DPC 146 controller can
<img file="MX353239B_D0095.tif" />
send a communication message allocate resources to the second DSC controller 144b on the second network.
In block 512, the second DSC controller
144b may receive the resource allocate communication message from the DPC controller 146. At block 514, the second DSC controller 144b may use the information included in the allocate resources received message to allocate all or parts of its reserved resources for access and use by components in the first network. In block 516, the second controller
DSC 144b may generate a resource access communication message that includes information (eg, access parameters, etc.) that a wireless device 102 (that is, on the first network) can be used to access the allocated resources and sending the resource access message to the controller
DPC 146.
In the block
518, the second DSC controller
144b may perform various operations to prepare for establishing a communication link / session for wireless device 102 on the first network, such as by setting up or preparing to receive a voice or data call.
resource access communication message from the second DSC controller
144b and relay the message
In block 522, the DPC controller
146 can receive a
<img file="MX353239B_D0096.tif" />
IΜΡΙ
MEXICAN INSTITUTE OF PROPERTY
INDUSTRIAL access to resources to the first DSC 144a controller.
At block 524, the first DSC controller 144a may receive the resource access message eT from the DPC controller 146. The received resource access message may include access parameters that can be used by wireless devices 102 to access the allocated resources of the second network . At block 526, the first DSC controller 144a can send access parameters to wireless devices 102 that have communication sessions with the first network and / or to wireless devices 102 that the first network has designated / marked for migration to other networks.
At block 528, wireless devices 102 can receive access parameters from the second network with decryption of the first DSC controller 144a. In blocks 530 and 520, wireless devices 102 and / or second DSC controller 142b can perform various operations to establish a communication link / session between wireless devices 102 and the second network. The second DSC controller 144b can then perform the operations of block 700 illustrated in Figure 7 as will be described later.
As noted above, in determination block 504, DPC controller 146 can determine whether to accept the offer of resources received from the first DSC controller 144a. In response to the determination
<img file="MX353239B_D0097.tif" />
<img file="MX353239B_D0098.tif" />
that the resource offer received from the first controller does not have to be accepted
DSC 144a (eg determination block 504 DPC controller 14 6 can perform the operations of block 600 illustrated in
Figure 6.
Referring to the
Figure 6, at block 600, DPC controller 146 can send an offer rejected communication message to the first DSC controller 144a. In block 602, the first DSC controller 144a can receive the offer rejected message from DPC controller 146. In determination block 604, the first DSC controller 144a can determine whether the first network should / should make a new offer for the resources. In response to the determination that the first network should / should make a new offer for the resources (i.e., determination block 604
Yes), at block 606, the first DSC controller 144a may send a new resource offer (eg, in an offer communication message to DPC controller 146).
At block 608, DPC controller 146 may receive the new resource offer (or re-offer) from the first DSC controller 144a. At determination block 610, DPC controller 146 can determine whether or not to accept the new resource offer, such as by determining whether or not the new resource offer complies with the policies and rules of the
<img file="MX353239B_D0099.tif" />
INSTITUTO M «X! CANO M LA PROtrepao INDUSTRIAL
<img file="MX353239B_D0100.tif" />
DSA system and the requirements of the second network. In response to the determination that the new resource offer is to be accepted (i.e., determination block 610
Yes), the DPC controller 146 can perform the operations of block 506 illustrated in Figure 5. In response to the determination that the new resource offer does not have to be accepted (that is, determination block 610 = No), the controller DPC 146 can perform block operations
600.
In response to the determination that the first network should make a new offer for the resources (that is, determination block 604 = no), in block 612, the first DSC controller 144a may send a resource cancellation request communication message to the DPC controller 146. At block 614, DPC controller 146 may receive the resource request cancel message from the first DSC controller 144a. At block 616, DPC controller 146 can send a resource release communication message to second DSC controller 144b.
In block 618, the second DSC controller 144b can receive the resource release message from DPC controller 146. In block 620, the second DSC controller 144b can release the reserved resources so that they can be used by other networks. The second DSC 144b controller can then report the status of the resources
Tx ·.
- '• 7 r' '' 'to / ¿' r '
INSTITUTO MEXICANO VS- · * · D £ THE PROPERTY k> ij, INDUSTRIAL assigned to the DPC controller performing the operations of block 316, which is illustrated in Figure 3 and described previously.
Figure 7 illustrates a DSA method 300 resolution procedure that can be performed after the second network provides access to the wireless secondary user devices 102 on the first network (that is, after performing the illustrated block 520 operations in Figure 5).
In block 700, the second DSC controller 144b can send invoices and payment instructions regarding the use of resources allocated by the first network to the DPC controller 146. In block 704, the DPC controller 146 can retransmit the invoice and instructions for payment to the first DSC 144a controller. At block 706, the first controller
DSC 144a can receive invoices and payment instructions and settle charges with the second network in block 718.
Optionally or alternatively, at block 708, the second DSC controller 144b can send usage parameters and payment instructions to DPC 146. At block 710, DPC controller 146 can receive usage parameters and payment instructions from the second DSC 144b controller. In block 7Γ2, DPC controller 146 can create an invoice for access and use of resources. In block 714, DPC controller 146 can send the invoice to set: *
<img file="MX353239B_D0101.tif" />
<img file="MX353239B_D0102.tif" />
first DSC 144a controller on the first network. In the block
Μ - ΙΙΠΙιιΙ IWI
716, the first DSC controller 144a can receive the invoice and payment instructions and perform various operations to settle the charges with the second network in block 718.
In the various forms of mode, the components of the DPC 146 and DSC 144 controllers can be configured to communicate over an interface, which can be implemented in, or provided through, a component / module / protocol of an allocation application part Dynamic Spectrum (DSAAP) that is defined through the Xe and / or Xd reference points. The DSAAP protocol may allow, facilitate, support, or augment the communications between DPC controller 146 and DSC controller 144 in order to improve the efficiency and speed of the DSA system and the telecommunications network. In various modality forms all or parts of the DSAAP module / component may be included in a DPC 146 component, a DSC 144 component, a component that is independent of DPC 14 6 and DSC 144 components or any of their components. combinations. The DSAAP module / component can allow these and other DSA components to communicate information using the DSAAP protocol.
As an example, the DSAAP protocol may allow components of DPC 146 and DSC 144 controllers to communicate specific information and / or perform operations that <sup>76</sup> . IMPI Π
MEXICAN INSTITUTE: '
OF THE VV PROPERTY. '
INDUSTRIAL 'together provide various functions, including a —W — f M · - mm function, 1 DSC registration function, resource availability announcement function, tender and resource function assignment, tenant user transfer function to network of the lessor, reservation function of lessor networks, error management function (eg reporting of general error situations, for which no function-specific error messages are defined, etc.), DSC registration function, error indication function, DSC tender operational failure and success indication functions and DSC resource allocation withdrawal function. In various forms of embodiment, these functions may be provided, implemented, or performed by configuring the components of the DPC 146 and / or DSC 144 controllers to perform one or a combination of the DSAAP methods discussed below with reference to Figures 8A -17B. . The use of the DSAAP protocol and the modality of the DSAAP methods may include communication via one or more DSAAP messages.
In various modalities, the DSAAP messages used to communicate information between the DSC 144 and DPC 146 controllers may include a DSC REGISTRATION DEMAND message, DSC REGISTRY ACCEPT message, DSC REGISTRATION message, DSC RESOURCE REGISTRATION message, message ACCEPT RECORD RESOURCES DSC, message REJECT
IMPI
<img file="MX353239B_D0103.tif" />
RECORD RESOURCES DSC message and DEMAND OFFERS AVAILABLE, message RESPONSE TO DEMANDS AVAILABLE, message REJECT
OFFERS AVAILABLE, message DEMAND OFFER DSC, message
DSC OFFER ACCEPT message DSC OFFER REJECT, message
OFF DSC OFFER, DSC OFFER WON message, DSC OFFER LOSE message, DSC OFFER message CANCELED, DSC PURCHASE DEMAND message, DSC PURCHASE REJECT message, DSC RESOURCES ASSIGNED message, DSC RESOURCES message REMOVED and / or DSC ORD message . Each of these messages may include, or may be associated with, criticality information, presence information, margin information, and assigned criticality information. These messages and their contents are discussed in detail below.
In various forms of modality, DSAAP methods can be performed in a DSA system that includes a first DSC server in a first telecommunication network (eg, a tenant network), a second DSC server in the second telecommunication network (eg, a lessor network) and a DPC server that is outside of the first and second communication networks. The first DSC may include the first DSC processor coupled to the DPC via a first communication link, and the second DSC may include a second DSC processor coupled to the DPC via a second communication link. The second r> »« .vt L a. ” ·
<img file="MX353239B_D0104.tif" />
<img file="MX353239B_D0105.tif" />
MEXICAN INSTITUTE
OF THE INDUSTRIAL EROPISDAD
DSC can be coupled to an eNodeB node in the second telecommunication network through a third communication link. The first and second communication links can be defined through the Xd interface and the third communication link is defined through the Xe interface.
Figures 8A through 8C inclusive illustrate a DSAAP registration method of an 800 mode of registering a DSC 144 component with a DPC 146 controller to allow the DPC 146 controller to provide various services to DSC 144 (eg. ., Announcement of Resources from a Lessor DSC 144 for Tender, Permission to a Lessee DSC 144 to Bid on Provided Resources
<img file="MX353239B_D0106.tif" />
others
<img file="MX353239B_D0107.tif" />
etc.).
In the illustrated embodiments, including by way of example, in Figures 8A to 8C the DSAAP 800 registration method is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or parts of a DSAAP module / component. DSAAP 800 registration method operations may be performed after, or in response to detection by DSC 144 or DPC 146 that an XE signaling transport or communication link has been established.
In the 802 block of operations illustrated in Figures
8A to 8C inclusive, the DSC 144 controller can initiate the
<img file="MX353239B_D0108.tif" />
<img file="MX353239B_D0109.tif" />
jt 1
INSTITUTO MEXICANO DS LA PROPIEDAD INDUSTRIAL DSAAP 800 registration method generating and sending a DSC REGISTRATION DEMAND message to the DPC 146 controller '' In 'one' mode, the DSC 144 controller can be configured to generate and / or send the DSC REGISTRATION DEMAND message in response to the determination that it requires services from DPC 146. By way of example, DSC controller 144 may be configured to generate the DSC REGISTRATION DEMAND message in response to the determination that its corresponding network (that is, the network represented by the DSC controller) includes excess resources that can be allocated to other networks. By way of another example, DSC controller 144 can be configured to generate the DSC LOG DEMAND message in response to the determination that your network requires additional resources to provide appropriate service to your existing wireless devices 102 taking into account current user traffic or expected future, network congestion, etc.
In various forms of mode, the DSC controller 144 can be configured to generate the DSC RECORD DEMAND message to include some or all of a message type information element (IE), a message ID IE, a message identity IE DSC, a DSC Internet Protocol (IP) Address IE, a DSC type IE, a PLMN-ID DSC IE, a PLMN type IE, and a DSC Resource Update Timer IE.
The IE information element
IMFI / B
MEXICAN INSTITUTE k OF PROPERTY V '. . ..>
INDUSTRIAL ------------- of PLMN-ID DSC may include a PLMN ID that is suitable for use in identifying the network (eg E-UTRAN network) with the which is associated with, or represented by, the DSC driver 144. The IE information element of type
PLMN may include information that is suitable for use in determining the type of network (eg, public, commercial, etc.) represented by the controller.
DSC 144.
The address IE information element
DSC IP can include the IP address of a controller
DSC 144 that is responsible for the management, maintenance or provisioning functions of the DSAAP protocol XE interface.
In the operation block 804 illustrated in the Figures
8A and 8B, DPC controller 146 can perform various registration operations (i.e., DSC authentication, storing DSC identifier information in memory, etc.) to register the controller.
DSC 144 with the
DPC 146. In a modality form, as part of these registry operations, the controller
DPC
146 you can overwrite / abort an existing record with a new record, such as in response to receiving a duplicate message DEMAND
DSC REGISTRATION (that is, for an already registered DSC that is identified by the same unique DSC identity).
In operation block 806 illustrated in Figure 8Ά, DPC 146 can determine that the registration operations were operationally successful.
operations 808, the DPC 146 can generate ACCEPTANCE
DSC REGISTRY next to DSC modality acceptance, the
ACCEPTANCE whole
MEXICAN INSTITUTE
OF THE INDUSTRIAL FRGPÍEDAD
In the block and send
144 for a message indicate the registration of the DSC 144. In controller
DSC RECORD of an item various ways of
DPC 146 may to include a message IE identifier
DPC, a layer address IE generate any message or information (IE) from
Message ID, a transport network IE the XEh signaling ID type (TNL) and a tunneling information IE.
IE signaling TNL address XEh can include
The an address value that is suitable for use when establishing the transport layer session. The Tunneling Information IE may include information that can be used to encapsulate a different payload protocol, to establish secured communication through an unverified and untrusted network, transmit a payload over an incompatible delivery network, and / or or carry out other similar tunneling operations.
To support XEh connectivity through / to DPC 146, in operation block 810, DSC 144 may use the address value included in the XEh signaling TNL address IE of the DSC REGISTER ACCEPT message to establish a logon session. transport layer. In a form of mode, the DSC 144 controller can be configured to
ΊΤ p Τ <
JL JL.Vb-i. -one --- .
MEXICAN INSTITUTE rsr I ί 00 / ΊΡΤ6Γ> ΑΓ * 1 * «ΎΑ.
λα. ~ ίϊ '^ ί ~~' p¿'¿ PROPERLY set the transport layer session in response to the determination that the ACE Fl'AU 1ÜN message <sup>1</sup>REgí é TRO DSC includes an address value in the XEh signaling TNL address information element. In one form of mode, DSC controller 144 can be configured to determine that XEh connectivity via / for DPC 146 is not supported or required in response to the determination that XEh signaling TNL address information element is not is present, null, empty, or invalid.
Referring to Figure 8B, in operation block 812, DPC controller 146 can determine that the registration operations performed as part of operation 804 had an operational failure. The DPC controller 146 may determine that the registry had an operational failure in response to the detection of any of a variety of conditions / events, including failure of DSC authentication or authorization, network or component overload, parameter mismatch. DSC, etc. In operation block 814, DPC 146 controller may generate and send a REJECT DSC REGISTRATION message to DSC 144 controller to inform DSC 144 that a registration failure occurred and / or that DPC 146 cannot register DSC 144 In various forms of mode, the DPC 146 controller can generate the DSC REGISTRATION REJECT message for or. Mexican FSOPiEDAB ÍKPVJTRUi.
<img file="MX353239B_D0110.tif" />
include any information (IE) from or all of an element of a Message Type Cause IE, a Message ID IE, a Criticality Diagnostic IE and an Operational Withdrawal Timer IE.
The cause IE may include appropriate information to identify a specific reason for the failure (eg, overload, etc.) or to identify that the reason for the failure is unknown or unspecified.
At operation block 816, DSC 144 can perform various registration failure-response operations based on the information included in the RECORD REJECT message received. As an example, the DSC controller 144 may be waiting for a duration indicated in the IE of the operational withdrawal timer of the RECORD REJECT message received before retrying the registration with the same DPC 146 in response to the determination that the value the cause IE in the RECORD REJECT received message is set to overload.
Referring to Figure 8C, in operation block 852, DSC controller 144 may initiate operation of a register response timer in response to sending the DSC REGISTRATION DEMAND message to DPC controller 146 (that is, as of 802 operation). In operation block 854, DSC controller 144 can determine that the timer operation of
IMf 1
ΒΒΤΓτυτο wsxscAr »
OF THE HILTY
144 If it received an OPERATION RESPONSE message 856, the DSC controller 144 may forward the DSC REGISTER DEMAND message to the DPC controller 146 in response to the determination that the timer operation ended before it received a corresponding DSC REGISTRATION RESPONSE message. In operation block 858, DSC 144 can restart or reset the operation of the record response timer. In operation block 860, the DPC controller may send a DSC REGISTER RESPONSE message to DSC controller 144. In operation block 862, DSC controller 144 may interrupt operation of the record response timer in response to receiving the message. ANSWER
DSC REGISTRY.
Figures 9A and 9B illustrate a warning method of the DSAAP 900 protocol to warn that resources are available for bidding / purchasing in order to allow DPC 146 to store, organize and / or make the resources available for bidding / allocation via a financial agent. In the exemplary embodiments illustrated in Figures 9A and 9B, the DSAAP 900 warning method is performed by processing cores in a DPC 146 controller component and a DSC 144 controller component, each of which may include the all or parts of
<img file="MX353239B_D0111.tif" />
<img file="MX353239B_D0112.tif" />
a DSAAP module / component.
In operation block 902 illustrated in Figures 9A and 9B, DSC controller 144 can determine that resources are available for allocation within cells served by that DSC controller 144. In operation block 904, DSC 144 can generate and send a DSC RESOURCE REGISTRATION DEMAND message to DPC controller 146. In various forms of mode, the DSC controller 144 can generate the DSC RESOURCE REGISTRATION DEMAND message to include any or all of a message type information element (IE), a message ID IE, a message identity IE element DSC, a DSC type IE element, a PLMN-ID list IE element, a resource availability IE element, a resource availability start time IE element, a data bandwidth IE element, a distribution network list IE element, a bid or buy IE, a minimum bid quantity IE, a resource availability end time IE, a time of day IE, a time duration IE, a Megabit per second (Mbps) IE and a cell identity IE.
The DSC Controller Identity IE element may include information that can be used by DPC 146 to determine the identity of DSC 144. By way of example, the DSC Identity IE may include a DSC grouping ID, instance information of DSC and a PLMN ID of the
<img file="MX353239B_D0113.tif" />
ΙΜΡίίΓ network that the DSC is managing or representing. The DSC Pool ID may be a unique identifier for a pool of available resources and / or may be the same as, or similar to, MME Pool IDs and MME IDs in a 3GPP EPC architecture.
The Message ID IE can include a message identifier for the specific DSC RESOURCE REGISTRATION DEMAND message sent from the DSC 144. The DSC 144 and DPC 146 controller can be configured to use the Message ID IE as a message number. sequence to identify and establish the correlation between the DSC RESOURCE REGISTRATION DEMAND, DSC RESOURCE REGISTRATION ACCEPT and / or DSC RESOURCE REGISTRATION REJECT messages.
The Resource Availability IE may include information suitable for use by DPC 146 in determining the PLMN ID of the network that is advertising resources for allocation and use by other networks. DPC controller 146 can be configured to receive, memorize, and / or maintain resource availability IEs for multiple DSC controllers and / or for multiple different networks (ie, different PLMN IDs). Accordingly, each resource availability IE may include appropriate information to identify one or more of the networks that are advertising resources.
Time of day IE may include information
<img file="MX353239B_D0114.tif" />
<img file="MX353239B_D0115.tif" />
MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY
<img file="MX353239B_D0116.tif" />
Suitable for use by DPC 146 in determining the time of day when DSC 144 transmitted the DSC RESOURCE RECORD DEMAND message. The temporary duration IE may include information that is suitable for use in determining a period of time during which resources are to be made available for tender or purchase.
The data bandwidth IE may include suitable for use in determining the available bandwidth (that is, in Mbps) for the time duration specified in the optional time duration IE. DPC 146 may terminate that the bandwidth specified in the Mbps IE is to be made available until the bandwidth is consumed by the winning bidder or buyer in response to the determination that the time duration IE is not included in the DSC RESOURCE REGISTRATION DEMAND message received (or in response to the determination that IE time duration does not include a valid value).
The Distribution Network List IE may include Information suitable for use in determining distribution network identifiers for network bandwidth locations to be made available for tender or purchase. The Cell Identity IE may include information suitable for use in determining individual cells within each distribution network (identified by Network ID and Cell ID)
<img file="MX353239B_D0117.tif" />
<img file="MX353239B_D0118.tif" />
that have available resources offered for bidding or purchase as part of the offer in the REGISTRATION DEMAND message
DSC RESOURCES. The minimum bid amount IE may include a monetary amount in a denomination or currency, such as in United States dollars (USD).
In operation block 906 illustrated in Figure 9A, DPC controller 146 can accept the resources of DSC controllers 144 for bidding. In operation block 908, DPC controller 146 may generate and send a DSC RESOURCE REGISTRATION ACCEPT or DSC RESOURCE REGISTRATION ACCEPT message to DSC controller 144 to confirm that the resources were accepted. In various forms of mode, the DPC controller 146 can generate the DSC RESOURCE RECORD message to include any or all of a message type information element (IE), a Foreign Offer ID IE and a message ID IE . The Message ID IE may include the same message identifier value that is included in the received DSC RESOURCE LOG DEMAND message. The DPC 146 controller and / or the DSC can be configured to use the IE value of Message ID to identify and map the DSC RESOURCE LOG DEMAND and DSC RESOURCE LOG ACCEPT messages. In operation block 910, DPC controller 146 can memorize, organize, and / or make available network resources for bidding or purchasing through the
912, illustrated in Figure
IMPIbb ^
MEXICAN INSTITUTE V.'Λ OF PROPERTY V 'j
INDUSTRIAL financial agent platform.
In the operations block
9B, DPC 146 may reject the REGISTRATION DEMAND message
RESOURCE DSC and / or reject for the tender the resources identified in the DEMAND message received. The controller message / resources for a response to the detection of
REGISTRY
RESOURCE
DSC
DPC 146 diversity anyone can reject the motive and / or a diversity in events or conditions. As an example, the DPC controller
146 may reject resources in response to the determination that the DPC
146 it is not accepting resources from any operator, it is not accepting resources for the specific operator identified in the received message, it is not accepting the resources identified in the message, that the DPC is overloaded, that there is insufficient memory to memorize and serve the resources available to tender, etc. The DPC 146 controller may also reject the available resource message in response to the determination that a DPC 146 administrator has contested the additional bid from the specific PLMN ID included in the DSC RESOURCE REGISTRATION DEMAND message, from all networks ( eg all PLMN IDs) etc.
In operation block 914, illustrated in Figure
9B, DPC 146 controller can generate and send a message
REJECT RECOURSE DSC RESOURCE to DSC 144 controller. In ηκη
-and<sup>3</sup> various forms of modality, the iMPie;
MEXICAN INSTITUTE
OF EA PROPERTY V. * INDUSTRIAL
DPC 14 6 can generate the message REJECT RECOURSE RESOURCE
DSC to include any or all of a message element, a Message ID IE, a Cause IE, and a Criticality Diagnostic IE. The DPC controller 146 may also generate the DSC RESOURCE REGISTRATION REJECT message to include a Message ID IE that includes a value that is the same as the message identifier included in the DSC RESOURCE REGISTRATION DEMAND message received from DSC 144. DPC 146 and / or DSC 144 can be configured to use the value of the Message ID IE to identify and map messages
DEMAND RECORD RECOURSE DSC and REJECTION RECORD RESOURCE DSC.
At operation block 916, DSC controller 144 may perform various resource registration failure response operations based on the information included in the received DSC RESOURCE REGISTRATION REJECT message. As an example, the DSC controller 144 can use the information included in the DSC RESOURCE REGISTRATION REJECT message to determine whether or not to retry the resource record with DPC 146, try to register the resources with another DPC, retry the record with different resources or perform any of the other DSC operations described in this patent application.
Figures 10A and 10B illustrate a DSAAP 1000 method for
<img file="MX353239B_D0119.tif" />
communicate a list of
IHSTnVTO MEXICANO Dt U. MONEDAD tNDUyriUAt in accordance resources
<img file="MX353239B_D0120.tif" />
with a form of modality.
The DSAAP 1000 method can be performed to inform tenant networks of resource offerings or resources that are available for tender / purchase. In the exemplary embodiments illustrated in Figures 10A and 10B, the DSAAP 1000 method is performed by processing cores in a DPC component 146 and a DSC component 144, each of which may include all or parts of a DSAAP module / component. In one form of modality, a tenant DSC 144 can be configured to perform the DSAAP 1000 method to retrieve / receive a list of available resources
<td>before</td><td>that he</td><td>DSC 144 controller</td><td>participant</td><td>in</td><td>the</td>
<td>bidding</td><td>on,</td><td>or demand to lease or</td><td>to buy,</td><td colspan="2">resources</td>
<td colspan="2">from DPC 146.</td><td></td><td></td><td></td><td></td>
<td>At</td><td>block</td><td>from operations 1002,</td><td>illustrated</td><td>in</td><td>the</td>
Figures 10A and 10B, a tenant DSC 144 can generate and send a DEMAND AVAILABLE BIDS message to DPC 146 to request information about the resource offerings that are available for allocation from the lessor networks for tender or purchase. In various forms of mode, tenant DSC 144 may generate the DEMAND AVAILABLE OFFERS message to include any or all of a sequence number information element (IE), a message type IE, a PLMN list IE which includes one or
<img file="MX353239B_D0121.tif" />
<img file="MX353239B_D0122.tif" />
plus IE ID
PLMN, a Distribution Network ID List * IE that includes one or more Distribution Network ID IE.
In one form of modality, the tenant DSC 144 can be configured to request specific resources from a specific network by generating the DEMAND AVAILABLE OFFERS message to include the PLMN ID of the desired network, which can be included in the IE PLMN ID IE of PLMN list in the DEMAND OF OFFERS AVAILABLE message.
In one form of modality, the tenant DSC 144 can be configured to request resources from any available network by not including the PLMN list IE in the DEMAND AVAILABLE OFFERS message and / or generating the DEMAND AVAILABLE OFFERS message not to include a list IE of PLMN and / or a PLMN ID value.
In one form of modality, the tenant DSC controller 144 can be configured to demand resources from a specific distribution network within a lessor network by generating the DEMAND BIDS AVAILABLE message to include the distribution network IDs of the desired distribution networks, which may be included in the Distribution Network ID IE from the Distribution Networ k ID L ist IE in the DEMAND AVAILABLE OFFERS message.
In one form of modality, the tenant DSC 144 can be configured to demand resources from the entire
IMPIf '
MEXICAN INSTITUTE Κ <·. · '· Ό M LA PRCHEDAÜ <sup>1</sup> or any of the distribution networks showed ^^ l ^ un To ^^ üe
PLMN specified in a distribution network BK '<sup>-</sup>of the <sup>1</sup> IB TB '-' of PLMN not incorporating the Distribution Network ID List IE in the generated DEMAND OF AVAILABLE OFFERS message and / or generating the DEMAND AVAILABLE OFFERS message to not include a distribution network ID identifier.
In operation block 1004 illustrated in Figures 10A and 10B, DPC controller 146 can determine whether the PLMN ID and Distribution Network ID identifiers included in the received DEMAND AVAILABLE OFFERS message are valid or not. If the PLMN ID identifiers and the Distribution Network ID identifiers are incorrect, in operation bl ock 1005 , DPC 14 6 may determine a reason code for the erroneous / incorrect values. In operation block 1006, DPC 146 can determine if resources / offers are available for each distribution network that is identified in the received DEMAND AVAILABLE DEALS message or for all available distribution networks (eg, when IE list of distribution network IDs in the DEMAND OF AVAILABLE OFFERS message does not include valid values).
In operation block 1008, illustrated in Figure 10A, DPC controller 146 can generate and send a REPLY AVAILABLE OFFERS message to DSC controller 144. DPC
146 can be configured to generate the RESPONSE message
<img file="MX353239B_D0123.tif" />
OFFERS AVAILABLE to include any or all of a message type information element (IE), an IE of
Message ID, a DSC Identity IE, a PLMN-ID Distribution Network Cells Offering Information List IE, a Sequence Number IE, a PLMN List IE that includes one or more ID IE PLMN and a List IE distribution network . In one embodiment, the PLMN List IE and the Distribution Network List IE may be included in the Distribution Network Cell Offer Information List IE PLMN-ID. In one embodiment, the Distribution Network List IE may include one or more Cell ID List IE elements including one or more Cell ID IE.
In various modalities, the DPC controller 146 may generate the ANSWER AVAILABLE REPLY message to also include any or all of the Absolute Radio Frequency Channel Number (ARFCN) IE information elements, a channel bandwidth IE, one megabit or megabyte IE to identify the total available bandwidth, one Mbps IE to identify the maximum data rate for the resource, one resource available time IE, a resource expiration time IE, a bid / buy IE, a bid / buy expiration IE, a minimum bid amount IE, and a bid price IE. DPC 146 Driver May Generate RESPONSE Message
ΙΜΡΙ <? 5
MEXICAN INSTITUTE K *. , -,
OF THE PROPERTY · *
INDUSTRIAL
OFFERS AVAILABLE to include information for each
PLMN, each resource, each distribution network and / or each cell identified in the message.
In one form of modality, DPC controller 146 can be configured to generate the AVAILABLE OFFERS RESPONSE message to include the PLMN ID list, distribution network ID lists within each PLMN, and the resources / offers available within each PLMN network. distribution in response to the determination that there are bids for resources available for auction.
In one form of modality, DPC controller 146 can be configured to generate the AVAILABLE BID RESPONSE message to include message type and sequence number IE (or valid values for these IE) in response to the determination that no resources exist / bids for resources available for auction by that DPC 146 for the relevant PLMN / Network IDs. In one form of modality, DPC 146 can be configured to generate the AVAILABLE OFFERS RESPONSE message to include a sequence number IE that has the same value as the sequence number IE included in the received AVAILABLE OFFERS message. In one form of mode, the DSC 144 controller can be configured to use the sequence number IE in these request and response messages to establish a
<img file="MX353239B_D0124.tif" />
MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY correlation between messages.
In one form of mode, DPC controller 146 can be configured to generate the AVAILABLE BID RESPONSE message to include a PLMN List IE information element that includes a PLMN IE and a Distribution Network ID List IE. The Distribution Network ID List IE may include a list of cells available for auction within the distribution network. The Cell ID List IE can include a Cell ID and for each cell, the ARFCN, the channel bandwidth, the total available bandwidth, the maximum allowed data rate, the time of day (eg. (eg, in UTC) when resources are available and when they expire / end, if it is a bid or bid type auction, minimum bid quantity or purchase price, bid end time (e.g. in UTC) and other similar information.
In operation block 1010, controller DSC 144 can use the information included in the AVAILABLE BIDS ANSWER message to identify the resources that are available for bidding, to determine whether DSC 144 will bid on the available resources, determine the resources to which the DSC 144 will present offers and / or carry out other similar operations.
Referring to Figure 10B, in operation block 1012, DPC controller 146 may reject the
<img file="MX353239B_D0125.tif" />
DEMAND AVAILABLE DEALS message received from tenant DSC 144 generating and sending a REJECT message
OFFERS AVAILABLE to DSC 144. The DPC administrator 146 can be configured to reject the DEMAND AVAILABLE OFFERS message in response to the determination (eg, as part of operation block 1004 or 1006) that one or more of the PLMN IDs supplied in the request message do not comes from any of the known networks, that one or more of the distribution network ID identifiers supplied in the request message is invalid with respect to the supplied PLMN ID identifier and / or that there are no resources / offers available in the relevant distribution networks.
In one form of modality, DPC 146 can be configured to generate the REJECT AVAILABLE OFFERS message to include a message type information element (IE), a message ID IE, a cause IE, a criticality diagnostic ID and a sequence number IE. The cause IE may include a reason code (eg, invalid PLMN ID, invalid distribution network ID, etc.) for the rejection of the available offer demand, which can be determined in the operations 1005. The sequence number IE may include the same sequence number value that was included in the DEMAND AVAILABLE OFFERS message received from the tenant DSC 144. In consecuense,
IMPI ttCTnvro Mexican DE i'KOfÍEDAD the DPC 146 and / or the DSC 144 can trust to use the
<img file="MX353239B_D0126.tif" />
demand and response to establish a correlation between messages.
In operation block 1014, the DSC controller 144 may use the information included in the received REJECT AVAILABLE BIDS message to perform various response-failure operations. As an example, DSC controller 144 can determine whether or not to send another DEMAND AVAILABLE AVAILABLE message to DPC 146, determine whether or not to send another DEMAND AVAILABLE AVAILABLE message to a different DPC, etc.
Figures 11A and 11B illustrate a bidding method DSAAP 1100 for bidding for DSC resources, which allows different tenant networks to bid for resources that are available from the lessor networks. In the exemplary embodiments illustrated in Figures 11A and 11B, the DSAAP 1100 method is performed by processing cores in a DPC component 14 6 and a DSC component 144, each of which may include the entire or part of a DSAAP module / component.
In one form of mode, the DSC 144 and / or DPC 146 controllers can be configured to perform the DSAAP 1100 method after the DSC 144 controller retrieves the list of resources that are available for bidding (eg, after performing the mode DSAAP 1000), the DSC 144 controller and / or
146 They can be configured to perform the process continuously or repeatedly, up to the tender time. In a form DPC controller winning bid on completion £ 1V1 £ Jl \ ;; MEXICAN INSTITUTE
CE PROPERTY Vt INDUSTRIAL 'L
In various ways the DPC controller DSAAP method 1100, mode termination,
146 It can be configured to select (that is, the bid with a value one the highest one) of the bidding time.
In operation block 1102 of method 1100 illustrated in
Figures 11A and 11B, the
Tenant DSC 144 can generate and send a DEMAND SUPPLY message
DSC to DPC 146 to submit bids for one or more of the resources determined to be available from a lessor network (that is, one or more of the resources included in the list of resources obtained through the execution of method 1000 ). The tenant DSC 144 can be configured to generate the DSC OFFER DEMAND message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a DSC type, a bid ID IE, a PLMN ID IE, and a bid quantity IE. The Offering ID IE may include appropriate information to identify a specific resource for which the Tenant DSC 144 is bidding. The PLMN ID IE may include information suitable for use in identification
100 of the PLMN ID of identified in the offered IE can include
IMPI ^ í tNSTITUTO MSXICANO fe -— ¿C
DE LA MtONEDAO CVsjs,, -¡¿1 ·; INDUSTRIAL the network associated with offer ID resources. The IE of quantity is a monetary quantity in a currency (eg, USD) the value of the bid.
In one form of modality, tenant DSC 144 can be configured to generate the DSC BID DEMAND message to include a quantity bid IE value that is greater than a minimum bid quantity specified in a bid listing for the resource / bid ID specific. In another form of modality, the tenant DSC 144 can be configured to obtain the minimum bid quantity and / or offer listing from the REPLY AVAILABLE BIDS message (eg, the message sent as part of operation block 1008 illustrated in Figure 10A).
In the operation block 1104 illustrated in Figures 11A, the DPC controller 146 can use the information included in the received DSC SUPPLY DEMAND message to determine if the offer (resource offer) is valid and to be accepted, such as determining if the Offer meets DSA system policies and rules and lessor network requirements. In operation block 1106, DPC controller 146 may generate and send the DSC OFFER ACCEPT message to the DSC in response to the determination that the offer is valid and / or to be accepted. The DPC 146 controller can be configured to generate the
101
IMPIOo. ·.
Mexican institute V; r · -> 'D £ THE PROPERTY OR DSC OFFER ACCEPT message to include which ° <! ji ^ ra' ^ cr - ra totality of an information element 'fTEj message, an IE of message ID, an offer ID IE and other appropriate information to inform DSC 144 that the offer has been determined to be valid and / or has been accepted.
It should be noted that in the exemplary mode described above, the DSC OFFER ACCEPT message informs the DSC 144 controller that the offer is valid / accepted, and not that the tenant DSC 144 has won the offer. The winning tenant DSC may be informed by the DSC WIN BID message when DPC 146 determines that the bid time has expired and that the tenant DSC controller is the bidder who bid the highest bid at the time of bid termination. offer. Similarly, controller DPC 146 can inform tenant DSCs that participated in the bidding process, but submitted losing bids that were not presented as a winning bid by a LOSS DSC BID message. The DSC OFFER WON message and the DSC OFFER LOSE message are described in more detail below.
Referring to Figure 11B, in operation block 1108, DPC controller 146 may use the information included in the DSC OFFER DEMAND message received to determine that the offer is invalid and has not
102
<img file="MX353239B_D0127.tif" />
can
<img file="MX353239B_D0128.tif" />
INSTITUTO MEXICANO CE THE TNDUSTÍUAL PROPERTY to be accepted. As an example, the DPC controller 146 uses the received information to terminate<sup>_</sup> that the offer does not comply with the policies / rules of the DSA system and / or does not meet the requirements of the landlord network (eg, does not meet the minimum demand price, etc.). As additional exemplary modalities, DPC 146 may be configured to determine that the offer is invalid or not to be accepted in response to the determination that the specific quantity bid in quantity bid IE in the DEMAND BID message is no more higher than the minimum offer, that the quantity offered is not the highest among the offers currently made, that the bid identifier included in the bid ID IE is invalid or that the bid / resource is not available for bidding (eg, due to expiration, end of auction, bid withdrawn, or invalid bid identifier) .
In operation block 1110, DPC controller 146 can generate and send a DSC OFFER REJECT message to DSC controller 144. DPC controller 146 can be configured to generate DSC OFFER REJECT message to include any or all of an information item ( Message type IE), a message ID IE, a bid ID IE, a cause IE, and a criticality diagnostics IE. The Offer ID IE in the DSC OFFER REJECT message can include the same value as the identifier
103
<img file="MX353239B_D0129.tif" />
<img file="MX353239B_D0130.tif" />
<img file="MX353239B_D0131.tif" />
offer included in the DSC DEMAND OFFER message. The IE of _j l-λ- μι · ι ·· ιιβι ··· ι · —W- nrumrTkr — si.
Cause may include a reason code that identifies a reason for the offer to be rejected (eg, unsatisfied minimum offer, bid override, offer not found, etc.). In operation block 1112, DSC controller 144 may use the information included in the received DSC OFFER REJECT message to perform various offer-request fail-response operations, such as operations to determine whether to make a new offer for resources , to generate a new DSC SUPPLY DEMAND message that includes a valid offer ID identifier, etc.
Figures 12A to 12D inclusive illustrate a method of notifying DSAAP 1200 of information to participating networks of the results of bidding operations. That is, the DSAAP 1200 notification method can be performed to inform DSC 144 controllers of an auction result (eg, they submitted a winning bid, they were left out of the bid, they submitted a losing bid, that the auction was canceled, etc.). In the exemplary embodiments illustrated in Figures 12A through 12D, the DSAAP 1200 notification method is performed by processing cores in a DPC component 146 and a DSC component 144, each of which may include the all or parts of a DSAAP module / component.
104
INSTITUTO MXXJCANO *. «· **“ oe ui pr.o? 'EDAO V <sub>t</sub> t
The DSAAP notification method 12 00 · can ^^ cflizárstí 'after DPC 146 notifies DSC ^ rTT' ^ üV <sup>k</sup>The offer has been accepted (eg, after block 1106 illustrated in Figure 11). The DSAAP 1200 notification method can also be performed after the expiration of a bidding time and / or in response to DSAAP by DPC 146 of an event or condition (eg, new offer received, bid override, etc. .).
In the operation block 1202 illustrated in Figure 12A, the DPC controller 146 can determine that the specific bid quantity in the bid quantity IE is the latest, most recent, or most current SUPPLY DEMAND message accepted from DSC controller 144 is not the highest among current offers. In operation block 1204, DPC controller 146 may generate and send a DSC OVERBIDDING message to DSC 144 to inform tenant DSC 144 that its initial offer was exceeded by a higher offer from another tenant DSC and / or that your initial offer is no longer valid. In various forms of mode, DPC controller 146 can generate the DSC OFFER OVERLAP message to include any or all of a message type information element (IE), a message ID IE, a cause IE, an IE offer information, a Criticality Diagnostics IE, a DSC ID IE, and a BID ID IE.
105
;.> £? Z
INSTítuto.>. Íek: cang industrial
-----...„<sub>Μ</sub>νΛι · Λι ν '
FROM PP.OFIHDAt »Y
<td rowspan="2">The IE of suitable for</td><td rowspan="2">ID its</td><td colspan="5">DSC may include information that is</td>
<td>use</td><td colspan="2">in identifying the</td><td colspan="2">DSC 144 of</td>
<td>lessee.</td><td>The</td><td>IE</td><td>ID</td><td>IDB can</td><td>include</td><td>a</td>
<td>identifier</td><td>ID</td><td>of</td><td>offer</td><td>suitable for</td><td>use in</td><td>the</td>
<td>ID</td><td>of</td><td>the</td><td>offer</td><td>filed that</td><td>has not</td><td>been</td>
the block supported. In Operations 12 06, the lessee DSC 144 can perform various failure operations in response to overbid the offer, such as by determining whether or not to submit a higher offer for the resources for which the DPC 146 controller submits a offer to a
DPC 146 different, to eliminate the existing calls to
Making bandwidth free, etc.
Referring to Figure 12B, in operation block 1210, DPC controller 146 can determine that the bid time has expired and that the specific bid quantity in the bid quantity IE in the last, most recent, or most current DEMAND message. OFFER accepted from the DSC 144 controller is the highest among current offerings. In operation block 1212, DPC controller 146 may generate and send a DSC OFFER WON message to DSC controller 144 to inform tenant DSC 144 that its initial bid is the winning bid. In various forms of modality, DPC 146 may generate the DSC OFFER WON message to include any or all of a Type of Information Element (IE) of
106
<img file="MX353239B_D0132.tif" />
IMP
MEXICAN INSTITUTE
I NO nF THE IWrmJAí)
INDUSTRIAL message, a message ID IE, a bid ID IE, a bid information IE, a uSc ID IE and original bid details such as bandwidth, Mbps, duration, and the winning bid amount, etc. The DSC ID IE may include information that is suitable for use in identifying the specific tenant DSC 144. The Bid ID IE may include a suitable bid identifier to identify the bid that won the resource auction / bid operations.
In operation block 1214, the winning tenant DSC controller 144 may wait for the ALLOCATED DSC RESOURCES message from DPC controller 146 before its network equipment and device (eg, wireless devices) are scheduled to start To use the resources and / or the resources were made available for use (that is, planning for the time of day when the resources will be ready for use by the winning tenant network). At operations block 1216, DPC controller 146 may close the auction, such as rejecting new bids from other networks for resources earned by the bid submitted by tenant DSC 144.
Referring to Figure 12C, in operation block 1220, DPC controller 146 can determine that the bidding time is up and that the specific bid quantity in the bid quantity IE in the
107 impic; MEXICAN INSTITUTE 't' «5, OF THE PSC'rlíDAO last, most recent or most current message DEMAWIW OFFER accepted from the DSC 144 controller and oo --k> máo ^ elta among the current offers. In operations block 1222, DPC 146 can generate and send a DSC LOSS OFFER message to DSC 144 controller to inform tenant DSC 144 that their previous bid has not won the bid and the auction / bid is closed due to another Tenant DSC has won the auction. In various forms of mode, DPC controller 146 can generate the DSC OFFER LOSS message to include any or all of a message type information element (IE), a message ID IE, an offer ID IE, and a DSC ID IE. The DSC ID IE may include information that is suitable for use in identifying the specific tenant DSC 144 that submitted the losing offer and / or to which the LOST DSC OFFER message is sent. The Offer ID IE may include a suitable offer identifier for use in identifying the submitted offer.
At operation block 1224, the tenant DSC controller 144 can perform various failure response operations, such as determining whether or not to submit an offer for other available resources, without removing existing calls to free resources, etc. At block 1226, DPC controller 146 may close the auction and / or allow DSC controllers to
108
IMPI ^ n
MEXICAN INSTITUTE, losers lessee make an offer parí<sup>THE</sup>or ^^ L rSeSfiÍSOS available. _ -......... —— __________
Referring to FIG. 12D, in operation block 1230, DPC controller 146 can determine that the auction for a network resource that was previously submitted for bid by DSC 144 has been canceled. As an example, DPC 14 6 may determine that the auction has been withdrawn by the operator from the lessor network or that the auction has been canceled by the DPC operator for administrative reasons. In operation block 1232, DPC 146 can generate and send a DSC OFFER CANCELED message to DSC controller 144 to inform tenant DSC 144 that the auction has been canceled. In various forms of mode, DPC controller 146 can generate DSC OFFER CANCELED message to include all or any of a message type information element (IE), a message ID IE, an offer ID IE, a DSC ID IE and a cause IE. The DSC ID IE may include information that is suitable for use in identifying the specific tenant DSC controller 144. The Bid ID IE may include a suitable bid identifier for use in identifying the resource / bid for which the auction has been canceled. The cause IE may include a reason code for bid cancellation (eg, auction withdrawn,
109 auction canceled, etc.) i ivi riv MEXICAN INSTITUTE \ D £ THE PROPERTY
In the $ € »* tes block of operations, the lessee DSC 144 can perform vern? aa ope υα α iestes · of failure-response, such as determining whether or not to submit an offer for a different DPC 146, to eliminate calls, etc.
Figures 13A and 13B illustrate a DSAAP 1300 purchase method of allowing a tenant network to make an immediate (or almost immediate) purchase and / or use claim for a resource that is made available for allocation by a lessor network . In the exemplary embodiments illustrated in Figures 13A and 13B, the DSAAP 1300 purchase method is performed by processing cores in a DPC 146 component and a DSC 144 component, each of which may include the all or parts of a DSAAP module / component. In one form of modality, the DSC 144 and DPC 14 6 controllers can be configured to perform the DSAAP 1300 method after the DSC 144 controller retrieves / receives a list of resources that are available for purchase (eg, after performing the DSAAP 1000 method previously described with reference to Figure 10).
In operation block 1302 illustrated in Figures 13A and 13B, tenant DSC 144 can identify and select a specific resource for immediate purchase from the resource list (eg, resource list
110 obtained from the modality of the i
. MEXICAN INSTITUTE VVlj— '··. THE PROPERTY »ί · '-<sup>r</sup>.
Method ^ WLAP ^ - ^ Or previously described). In various ways to MódaridádT ^ 'he ·
Tenant DSC 144 can select a resource that is planned for bidding, is currently being auctioned, which is the only fact available for immediate purchase, etc. In operation block 1304, DSC controller 144 can generate and send a DSC BUY DEMAND message to DPC controller 146 to request the purchase of identified / selected resources from a lessor network.
In various forms of mode, the DSC controller 144 can generate the DSC BUY DEMAND message to include any or all of a message type information element (IE), a message ID IE, a DSC identity IE, a DSC type IE, a bid ID IE, a purchased quantity IE, and a PLMN ID IE. The PLMN ID ID may include information suitable for use in identifying the network PLMN ID associated with the offer, which can be identified through the Offer ID IE. The Purchased Quantity IE may include the amount (eg, in USD) of the offer (that is, the value of the offer) that was submitted by the Tenant DSC 144.
In one form of mode, the DSC 144 controller can be configured to generate the DSC BUY DEMAND message for
111
IMPI
Mexican INSTITUTE, _,. . , OF THE PROPERTY include a value of the purchase amount that steaST * ^
<img file="MX353239B_D0133.tif" />
amount identified by an IE from a listing for the offer ID included in a message
RESPONSE BIDS AVAILABLE received (discussed previously with reference to Figure 10).
In operation block 1306 illustrated in Figure 13A, DPC controller 146 can use the information included in the DSC BUY DEMAND message received to identify the requested resource, the network associated with the requested resource, if the requested resource is currently being object auction, if the requested resource was made available for immediate purchase, a minimum purchase amount demanded for the immediate purchase of that resource and / or if the purchased quantity included in the DSC PURCHASE DEMAND message is equal to (or greater than) the demanded purchase quantity. In the exemplary embodiment illustrated in Figure 13A as part of operation block 1306, DPC controller 146 determines that the purchased quantity included in the received DSC BUY DEMAND message is greater than or equal to the requested purchased quantity.
In operation block 1308, DPC controller 146 may generate and send a DSC OFFER ACCEPT message to DSC 144 to inform tenant DSC 144 that it has successfully acquired / leased the resource for use. In various forms of mode, the controller DPC 146 can
112
<img file="MX353239B_D0134.tif" />
<img file="MX353239B_D0135.tif" />
generate the ACCEPT message
OFFER any or all of a message type element, a Message ID IE, and an Offer ID IE. At operations block 1310, DPC controller 146 may end, stop, or close an active auction for that resource and / or perform similar operations so that the resource is not available for bidding or purchase by other tenant DSC controllers.
Referring to Figure 13B, in operation block 1312, DPC controller 146 can use the information included in the received DSC BUY DEMAND message (eg, as part of operation block 1304) to determine that the offer ( purchase request) has been rejected. As an example, the DPC 14 controller 6 can determine that the specific purchased quantity in the purchased quantity IE in the DSC BUY DEMAND message received is less than the purchase amount demanded. As another example, DPC controller 146 may determine that the bid ID value included in the bid ID IE is invalid or that the resource / bid is no longer available for bid (due to expiration, end of auction , Withdrawn Offer, Invalid Offer ID, etc.).
In operation block 1314, DPC controller 146 can generate and send a DSC BUY REJECT message to DSC controller 144. In various modes of mode, the
113
<img file="MX353239B_D0136.tif" />
<img file="MX353239B_D0137.tif" />
PURCHASE
MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY DPC 146 controller may generate the REJECT message
DSC to include any or all of a Message Type Information Element (IE), a Message ID IE, an Offer ID IE, and a Causes IE. The ^ value of the offer ID IE can be the same as the offer identifier included in the PURCHASE DEMAND DSC message received as part of operation block 1304. The cause IE may include an operating code for the rejection of the purchase request (eg, unfilled purchase price demanded, offer not found, etc.). At operation block 1316, DSC controller 144 can perform various failure-response operations, such as determining whether or not to submit a new purchase request with a higher bid quantity. At operations block 1318, DPC controller 146 performs various operations to make the resource available for tender or purchase by other lessee DSCs.
Figures 14A and 14B illustrate a DSAAP 1400 protocol resource allocation method of allocating resources in a lessor network for component access and use in a tenant network. In the examples illustrated in Figures 14A and 14B, the DSAAP 1400 resource allocation method is performed by processing cores in a DPC component 146, a tenant DSC component 144a, and a lessor DSC component 144b, each of the
114
<img file="MX353239B_D0138.tif" />
which can include the whole or paf ^ é ^^ of ^ brfi module / component of DSAAP. · ....... ......<sup>..</sup> .......
In operation block 1402 illustrated in Figures 14A and 14B, DPC controller 146 can determine that tenant DSC 144a has successfully purchased or won an auction for a resource on a lessor network represented by lessor DSC 144b. in operation block 1404 illustrated in Figure 14A, DPC controller 146 may generate and send a DSC OFFER SUCCESS message to lessor DSC 144b to inform the lessor network that one or more of its allocated resources / offers has been won by lessee 144a DSC.
In various forms of mode, the DPC controller 146 can generate the DSC OFFER SUCCESS message to include any or all of a message type information element (IE), a message ID IE, a cause IE, and an IE of criticality diagnoses. In another form of embodiment, DPC controller 146 may be configured to generate the DSC SUCCESS SUCCESS message to also include any or all of an Offer ID IE, a DSC ID IE, and an Offer Value IE. These additional information elements can be used to communicate information regarding the winning bid. As an example, the bid ID IE can include a bid ID that corresponds to the bid that has participated
115
<img file="MX353239B_D0139.tif" />
successfully on and won the auction for resources. The
DSC ID IE can include the DSC ID of the auction winner (that is, the tenant DSC controller 144a).
The bid value IE may include the winning bid quantity and / or the purchase price of the resources.
In operation block 1404, lessor DSC 144b can generate and send a DSC RESOURCE ALLOCATION message to DPC controller 146 to allocate / commit resources for component access and use in the tenant network. The lessor DSC 144b may be configured to generate a DSC RESOURCES ASSIGNED message to include any or all of a message type information element (IE), a message ID IE, an offer ID,
<td>a</td><td>IE</td><td colspan="2">of offer ID list,</td><td>a PLMN ID IE,</td><td>a</td><td>IE</td><td>of</td>
<td>ID</td><td>of</td><td>distribution network,</td><td>a</td><td>Cell IE, an IE</td><td>of</td><td>ID</td><td>of</td>
<td colspan="2">PLMN,</td><td>a network ID IE</td><td>of</td><td>distribution an IE</td><td>of</td><td>ID</td><td>of</td>
cell lists and various auction / resource data (eg, bandwidth,
Mbps, duration,
In one form of modality, the PLMN ID IE, a
Distribution network ID and a
Cell List ID IE can be included in the identifier list IE
PLMN-ID, Distribution Network ID, Cell ID. The PLMN ID IE can include the PLMN ID of the lessor network that allocates the resources, which can be the same PLMN ID network identified in the winning bid. The distribution network ID IE and
116
<img file="MX353239B_D0140.tif" />
<td>the IE of</td><td>List IDs</td><td colspan="2">cells</td><td>can</td><td>inc 1 ΐί ftááoxón</td>
<td>adequate</td><td>to identify</td><td>the</td><td>net</td><td>of</td><td>á.jatxib.1 j, qi fin / néljUaa</td>
<td>associated</td><td colspan="3">with resources. These</td><td colspan="2">values can be the</td>
<td colspan="2">same as the values</td><td>of</td><td>net</td><td>of</td><td>distribution / cells</td>
<td>included</td><td colspan="2">in the winning bid.</td><td></td><td></td><td></td>
In operation block 1406, DPC controller 146 may forward the DSC ALLOCATED RESOURCES message received to the winning tenant DSC 144a to allow the tenant DSC 144a to start using the allocated resources of the lessor network resources. In operations block 1408, tenant DSC 144a can schedule its network equipment to start using lessor network resources from the time of day specified as part of the offer and / or included in the received ASSIGNED DSC RESOURCES message.
Referring to Figure 14B, in operations block 1410, lessor DSC 144b can determine that the resources allocated for auction should be withdrawn and / or refrained from allocating the submitted resources to an auction winner. Landlord DSC 144b may determine withdrawal of resources after DPC 146 determines that the tenant's network acquired or won an auction for the resources and / or for any of a variety of reasons (eg, unforeseen reasons or administrative, etc.).
In block 1412, the lessor DSC
117
<td></td><td>ιμριγο> 7. MEXICAN INSTITUTE OF PROPERTY</td>
<td>144b</td><td>can generate and send a WITHDRAWN message 'ft'ÉííÜftS</td>
to the DPC 146 controller to remove the records. · Lessor 144b may generate the message DSC RESOURCES REMOVED to include any or all of a message type information element (IE), a message ID IE, a bid IE, a cause IE and a identifier IE Indicators PLMN-ID, Grid ID, ceil ID. The Offer ID IE may include information that is suitable for use in identifying the offer. The Cause IE may include a reason code that describes the reason for the removal of resource allocations (eg, unavailable resources, retired resources, administrative, etc.).
In operation block 1414, DPC controller 146 can forward the received DSC REMOVALS message received to lessee DSC 144a, which may have submitted a winning offer for the withdrawn resources. At operations block 1416, tenant DSC 144a can perform various failure-response operations, such as determining whether or not to participate in another auction, to bid, or not, on a different resource, to determine whether withdraw calls to free resources, etc.
Figures 15A and 15B illustrate one embodiment of a DSAAP 1500 operational withdrawal method of selective transfer through a wireless device from a lessor network back to the
118
<img file="MX353239B_D0141.tif" />
<img file="MX353239B_D0142.tif" />
tenant to which you subscribe (that is, your base PLMN). In the wireless device modalities illustrated, by way of example, in Figures 15A and 15B, the DSAAP 1500 operational withdrawal method is performed by processing cores in a component of DPC 146, a component of
Lessee DSC 144a and a lessor DSC component 144b, each of which may include all or parts of a DSAAP module / component.
In operations block 1502 illustrated in Figures 15A and 15B, lessor DSC 144b can determine that its network resources from cells that are part of a previous auction are in a congested condition. That is, lessor DSC 144b can determine that it requires access or use of its assigned resources. At operation block 1504, lessor DSC 144b can generate and send a DSC REMOVED ORDER message to DPC controller 146 for selective transfer of wireless devices that are using allocated resources from the lessor network back to the lessee network (that is, your base PLMN).
The lessor DSC 144b can be configured to generate the DSC REMOVED ORDER message to include any or all of a message type information element (IE), a message ID IE, an offer ID IE, a UE identity IE , an IE of measurement report, an IE of
119 cell operating recall information,
<img file="MX353239B_D0143.tif" />
a replay response timer IE
DSC.
The UE Identity IE may include information suitable for use in determining identity related information for the wireless device (or UE) such as an International Mobile Subscriber Identity (IMSI) of the wireless device or its network.
The Measurement Report IE may include the latest, latest, or most recent RRC E-UTRAN message regarding measurement information received by the lessor network for the identified wireless device (eg, wireless devices that are sue for tenant network or operational withdrawal).
The Bid ID IE can include a Bid ID value corresponding to the bid that successfully participated and completed / won the auction. The bid ID can be used to identify the auction / contract that is associated with the withdrawal operations (that is, the auction / contract for which the resources were allocated).
In one form of modality, lessor DSC 144b can be configured to determine if there are multiple offer IDs that correspond to a congested cell. In one form of modality, lessor DSC 144b can be configured to select the
120 offer ID value from a plurali
<img file="MX353239B_D0144.tif" />
MEXICAN INSTITUTE
BE THE FLOPIDITY
<img file="MX353239B_D0145.tif" />
offers in response to the 3S determination '' Are there multiple 'offer IDs' that correspond to a cell in a congested state. In various forms of modality, lessor DSC 144b can be configured to select the offer ID value based on an operator policy provided in lessor DSC 144b, based on a prior agreement, established pursuant to a policy / standard previously negotiated by lessor and lessee network operators, etc.
In operation block 1506, DPC controller 146 can forward the received DSC ORDER WITHDRAWN message to tenant DSC 144a. In operation block 1508, tenant DSC 144a may use the information in the UE Identity IE of the received DSC REMOVAL ORDER message to identify the wireless devices to undergo operational withdrawal operations (i.e., the devices wireless to be provided again).
In operation block 1510, the tenant DSC 144a may use the information included in the measurement report IE of the received DSC ORDER REMOVED message to determine, identify and / or select a target cell (within the tenant network) to the one to
121
INSTITUTO MEXICANO -, XX ce LA fSCWtf AB Cj-—, transferring wireless devices identSTÍ ^ clos ~ fta lessor network may have allowed coH¿Sád “TÓS '~ measurement reports from wireless devices, such as when attached, or transferred, to the landlord's network).
In operation block 1512, tenant DSC 144a can generate and send a DSC REPLY RESPONSE message to DPC controller 146. Tenant DSC 144a can be configured to generate the DSC REPLY RESPONSE message to include any or all of a Message Type Information Element (IE), Message ID IE, Offer ID IE, UE Identity IE, Cell Operational Withdrawal Information IE and Cause IE. In one form of modality, tenant DSC 144a can be configured to generate the BACKOFF DSC RESPONSE message to include the cause IE (or a value for the cause IE) in response to determining that a suitable target cell (within the tenant network) may not be identified or selected for transfer. The Cause IE value can identify a cause of the failure, such as a network overload, no suitable target cell was found, or an unknown UE / wireless device. In one form of modality, tenant DSC 144a can be configured to generate the BACKOFF DSC RESPONSE message to include a value (eg, target cell information)
122
<img file="MX353239B_D0146.tif" />
<img file="MX353239B_D0147.tif" />
for the operational cell removal information IE in response to the target identification (within the network to perform the transfer of the
In the successful operation block of a tenant cell) to which wireless device can.
1514, DPC controller 146 can identify tenant DSC 144a based on the offer ID IE included in the REPLY BACKOFF DSC message received and forward the REPLY BACKOFF DSC message received to the lessor DSC 144b. At operation block 1516, lessor DSC 144b can determine whether the received DSC BACKOFF RESPONSE message includes a Cell Operational Withdrawal Information IE (or a valid value for the Cell Operational Withdrawal Information IE). In response to determining that the received DSC BACKOFF RESPONSE message includes a Cell Operational Withdrawal Information IE (or a valid value for the Cell Transfer Information IE), in operation block 1518, the lessor DSC 144b may use the target cell information included in the Cell Operational Pickup Information IE to encode a TRANSFER REQUIRED message. In operation block 1520, lessor DSC 144b can initiate the SI-based transfer procedure to effect transfer of the wireless device from the lessor's network to the lessor's network.
123
Referring to the Figure
<img file="MX353239B_D0148.tif" />
¡KSTTTVTO UIíHCANO ds?;: O? ^ Oad
15B / 'in operations 1552, the lessor DSC 144Ep3 can determine that DPC controller 146 has not responded to the BACKOFF DSC ORDER message (sent as part of operations block 1504) within a time period identified in the IE of DSC operational withdrawal response timer included in the DSC BACKOFF ORDER message. Alternatively, or additionally, in operation block 1554, lessor DSC 144b may determine that there is significant or severe network congestion or administrative reasons that require the allocation to be removed from all remaining network resources that they belong to the offer / resource ID identifier included or identified in the DSC REMOVED ORDER message.
In operation block 1556, lessor DSC 144b may generate and send a DSC REMOVALS WITHDRAWN message to DPC controller 146. In operation block 1558, DPC controller 146 may forward the received DSC REMEDIES message to tenant DSC 144a. to unallocate the remaining network resources. At operations block 1560, tenant DSC 144a may perform various failure-response operations on withdrawn resources, such as call withdrawal, determining whether or not to bid for new resources, etc.
Figure 16A illustrates a DSAAP de-registration method.
124
<td>started by</td><td>DSC</td><td> 1600,</td><td>in</td><td>a</td>
<td>finish the</td><td colspan="2">operations.</td><td>In</td><td>the</td>
<td colspan="2">example in the</td><td>Figure</td><td>16A,</td><td>the</td>
performed started by DSC 1600 it
IMPIOUS
MEXICAN INSTITUTE
PROPERTY VV ... modSíl form<sup>i</sup>dhd7 ''<sup>i</sup>~ paci'á moda 1 i dad 'iluatrad'a; as a DSAAP de-registration method by processing cores in a DPC component
146 and in a DSC component 144, each of which may include all or parts of a DSAAP module / component.
In operations block 1602, the DSC
144 can determine that you need to finish operations
DSA.
In operation block 1604, the DSC controller
144 can generate and
DPC 146.
generate the send a DSC REGISTRATION message to the controller
The DSC controller 144 can be configured for DSC REGISTRATION message to include any or all of a message type information element (IE), a message ID IE, an operational retreat timer IE and a cause IE that identifies a cause for the termination of operations. In operation block 1606, DPC controller 146 can remove all related resources associated with DSC 144 and / or perform other similar operations for de-registering DSC 144 in response to receiving the DSC DE-REGISTER message.
Figure 16B illustrates a DSAAP de-registration method initiated by DPC 1650 to terminate operations, in a modality form. In the illustrated embodiment, by way of example,
125
DPC 1650 is made using prncpsamipnto „eri ...... a component of DPC 146 and a component of DSC 144, each of
<td colspan="2">which can</td><td>include the</td><td>whole or parts</td><td>of</td><td>a</td>
<td>module / component</td><td>of</td><td>DSAAP.</td><td></td><td></td><td></td>
<td>In the block</td><td>of</td><td>operations</td><td>1652, the controller</td><td>DPC</td><td> 146</td>
<td>can determine</td><td colspan="2">what do you need</td><td colspan="2">finish operations</td><td>DSA</td>
with the DSC controller 144. In operation block 1654, the DPC controller 146 can generate and send a DSC RETREAD message to DSC 144. The DPC controller 146 can be configured to generate the DSC REGISTRATION message to include any or all of a message type information element (IE), a message ID IE, an operational retreat timer IE and an IE cause that identifies a cause for termination of operations (eg, overhead, unspecified, etc.). In operation block 1656, DPC controller 146 can remove all related resources that are associated with DSC 144 and / or perform other similar operations for de-registration of DSC 144.
In operation block 1658, the DSC controller 144 may perform various registration failure-response operations based on the information included in the received DSC REGISTRATION message. As an example, the DSC 144 controller can be configured not to retry the
126
INSTITUTO MEXICANO V OS LA MOFIECAO y. DPC 146 controller for<sup>tN</sup>^<sup><</sup>F<sup>RJ</sup>% eriíJn ^ ící 'record for the same
<td>duration</td><td>indicated</td><td>in</td><td>the</td><td>IE's</td><td>timer</td><td>from '-rerirada</td>
<td>operative</td><td>included</td><td>in</td><td>the</td><td>message</td><td>REGISTER</td><td>DSC received</td>
<td>when the</td><td>value of</td><td>IE</td><td>of</td><td>cause in</td><td>the message FROM</td><td>-DSC REGISTRY</td>
is set to overload.
Figure 17A illustrates a DSAAP error indication method initiated by DSC 1700 to report errors in accordance with one form of mode. In the exemplary illustrated embodiment in Figure 17A, the 1700 method using processing cores in a DPC 146 component and a DSC 144 component, each of which may include all or parts of a DSAAP module / component .
In operation block 1702, DSC controller 144 may detect an error or error condition (eg, a protocol error, etc.). In operation block 1704, DSC 144 can generate and send an ERROR INDICATION message to DPC 146 controller. DSC 144 can be configured to generate an ERROR INDICATION message to include any or all of an information element (IE) of message type, message ID IE, cause IE, and a criticality diagnostic IE. The Cause IE may include information suitable for use in identifying a cause or type of the error (eg, transfer syntax error, abstract syntax error, logical error, etc.). The Criticality Diagnostic IE may include a
127
<img file="MX353239B_D0149.tif" />
Procedure Code IE, an Operational Initiation Message IE, and a Procedure Criticality IE. In operation block 1706, DSC controller 144 and DPC 146 may perform various error-response operations based on the detected error or the information included in the RECEIVED ERROR message. The error detection and response operations are described in detail later.
Figure 17B illustrates a DPC 1750 initiated DSAAP error indication method in one form of mode for reporting errors in accordance with another form of mode. In the exemplary illustrated embodiment, in Figure 17B, method 1750 is performed by processing cores in a DPC component 14 6 and a DSC component 144 each of which may include all or parts of a module / component from DSAAP.
In operation block 1752, DPC controller 146 may detect an error condition. In operation block 1754, controller DPC 146 can generate and send an ERROR INDICATION message to DSC 144. DPC 146 can be configured to generate ERROR INDICATION message to include a cause information element (IE) that identifies a cause for the error. In operation block 1756, DSC 144 and / or DPC 146 can perform various error-response operations based on the
128
<img file="MX353239B_D0150.tif" />
information included in the ERROR INDICATION message received.
As noted above, various error-response or failure-response operations may be configured to perform the DSC 144 and DPC 146 in response to detection of an error or failure condition. As part of these operations the DSC 144 and / or DPC 146 controllers can identify the type or cause of the error / fault condition and tailor their response based on the cause or type identified. As an example, the DSC controller
144 and / or DPC 146 can be configured to determine if a detected error is a protocol error and tailor its responses accordingly.
Protocol errors include transfer syntax errors, abstract syntax errors, and logical errors. A transfer syntax error can occur when the receiving functional DSAAP entity (eg, DSC, DPC, etc.) is unable to decode the received physical message. As an example, transfer syntax errors may be detected while decoding ASN.l information in a received message. In one form of modality, the components of DSC 144 and DPC 146 can be configured to retransmit or re-request a DSAAP message in response to determining that a detected error is a transfer syntax error (e.g. , as part of
129 error-response operations).
An abstract syntax error
MEXICAN INSTITUTE OF THE PROi'tE & AO INDUSTÍUAL
<img file="MX353239B_D0151.tif" />
can occur when '' the '
<img file="MX353239B_D0152.tif" />
DSAAP
<img file="MX353239B_D0153.tif" />
receiver
<img file="MX353239B_D0154.tif" />
it receives information elements (IE) or groups of IEs that cannot be assimilated or understood (that is, an unknown IE identifier). An abstract syntax error can also occur when the entity receives an information element (IE) for which a logical scope is violated (eg, allowed number of copies). The DSC 144 and DPC 146 components can be configured to detect or identify these types of abstract syntax errors (eg, they cannot assimilate the error and in response, perform error-response operations based on criticality information included in the corresponding DSAAP message.
Additional data regarding these operations and criticality information are provided below.
An abstract syntax error can also occur when the receiving functional DSAAP entity does not receive IEs or groups of IEs, but in accordance with the specified presence of the object, the IEs or groups of IEs must have been present in the received message. The components of
DSC 144 and DPC 146 can be configured to detect or identify these particular types of abstract syntax errors (ie IE or IE group missing) and in response,
130
<img file="MX353239B_D0155.tif" />
<img file="MX353239B_D0156.tif" />
perform error-response operations based on criticality information and presence information for the missing IE / IE group. Additional information regarding these operations, criticality information and presence information are provided below.
An abstract syntax error can also occur when the receiving entity receives IEs or groups of IEs that are defined to be part of a message in wrong order or with too many occurrences of the same IE or group of IE. Furthermore, an abstract syntax error can also occur when the receiving entity receives IEs or groups of IEs, but in accordance with the conditional presence of the object of interest and the specified condition, the IEs or groups of IEs must not have been present in the message received. The DSC 144 and DPC 146 components can be configured to detect or identify abstract syntax errors (that is, wrong order, too many occurrences, wrongly present, etc.) and in response, reject or terminate a procedure or method associated with the error (eg, the method that caused the error). The DSC 144 and DPC 146 components may reject or terminate the procedure / method as part of the error-response operations.
In various forms of mode, the components of DSC 144 and DPC 146 can be configured to continue decoding, reading, or processing a DSAAP message after
131
<img file="MX353239B_D0157.tif" />
to detect, identify or determine that of abstract syntax for that message.
DSC 144 and DPC components failed
As an example,
146 they can operationally skip one part of the message that includes an error and continue processing the other parts of the message.
As part of this ongoing processing, the DSC 144 and DPC 146 components can detect or identify more abstract syntax errors.
In one form of modality, the DSC 144 and DPC components can be configured to perform error response operations for each detected abstract syntax error and / or based on criticality information and presence information for the IE / IE group associated with the abstract syntax error.
As noted above, each DSAAP message may include, or may be associated with, criticality information, presence information, scope information, and assigned criticality information. In the various modality forms, a receiving functional DSAAP entity (eg, DSC, DPC, etc.) can be configured to use any or all of the information (eg, criticality information, presence information, etc.) When an error is detected, the type of error or the specific error-response operations to be performed are identified. That is, the entity can perform different
132
IMPI operations depending on the values of <sup>χ</sup> INDUSTRIAL criticality, presence information, scope information and / or assigned criticality information.
In one form of modality, the receiving functional DSAAP entity (eg, DSC, DPC, etc.) can be configured to use the presence information included in a DSAAP message when identifying the type of error and error operations- Specific responses to be made for the type of error identified. As an example, the entity may use the presence information to determine whether the presence of an information element (IE) is optional, conditional, or mandatory (eg, with respect to the RNS application) for that message, or communication. The entity may determine that an abstract syntax error has occurred when a received message lacks one or more information elements that are determined to be mandatory (or conditional when the condition is true).
In one embodiment, the receiving functional DSAAP entity (eg, DSC, DPC, etc.) can be configured to use criticality information when it is identified that specific error-response operations are to be performed. That is, each DSAAP message can include criticality information for each individual information element (IE) or group of IE included in that message. The
133
<img file="MX353239B_D0158.tif" />
<img file="MX353239B_D0159.tif" />
Criticality information values for each IE or IE group can include reject IE, ignore IE and notify sender and Ignore IE. The receiving entity (eg, DSC, DPC, etc.) can use this criticality information to determine that an IE, IE group, or EP is incomprehensible, identifying the condition as an abstract syntax error (this is , cannot understand an abstract syntax error) and / or to identify error-response operations to be performed (eg reject, ignore, notify, etc.).
In a modality form, the receiving entity (eg,
DSC, DPC, etc.) can be configured to reject a method / procedure and initiate a DSAAP error indication method of the Figures (previously disclosed with reference to
AB) in response to the determination that an information element included in a message received during the execution of that method / procedure is incomprehensible and that the value of the criticality information for that IE is set to Reject IE.
As an example, when a message that initiates a method / procedure (eg, a DSC REGISTRATION DEMAND message, etc.) is received, it is determined that it includes one or more IEs / groups of IEs that are incomprehensible and marked as Reject IE, the receiving entity can reject the method / procedure by not executing some of the requests
134
<img file="MX353239B_D0160.tif" />
functions included in that message. I enti
IEs that use the message normally used to report the unsatisfactory result of the procedure. When the information in the received initiation message is insufficient and cannot be used to determine a value for all IEs that are required to be present in the message that is used to report the unsatisfactory result of the procedure, the receiving entity may terminate the procedure and initiate a DSAAP error indication method / procedure.
As a further example, when a message is received that starts a method / processing that does not have a message to report an unsatisfactory result and where the message includes one or more IEs / groups of IEs marked with Reject IE than the receiving entity does not understand, the receiving entity may determine the method / procedure and initiate a DSAAP error indication method / procedure.
As a further example, when a response message is received (a DSC RECORD ANSWER message, etc.), which includes one or more IEs marked with Reject IE that does not comprise the receiving entity, the receiving entity may consider the method / processing such as being unsuccessfully terminated and starting a local error handling method.
135
In one form of modality, the to ignore or omit a method / procedure and initiate a DSAAP error indication method (described earlier with reference to Figures 17A-17B) in response to determining that an information element (IE ) included in a message received during the mode of that method / procedure is incomprehensible and that criticality information value for that IE is set to Ignore IE and notify sender.
As an example, when you receive a message that starts a method / procedure that contains one or more IEs / groups of
IEs marked with Ignore IE and notify issuer that does not understand the receiving entity, the receiving entity can ignore the content of the incomprehensible IEs / groups of IEs, continue with the method / procedure as if the incomprehensible IEs / groups of IEs had not been received (with the exception of the report) using the IEs / groups of IEs that can be understood and reported in the response message of the method / procedure in which one or more IEs / groups of IEs have been ignored. When the information received in the initiation message is insufficient to determine the value for all IEs that are required to be present in the response message, the receiving entity may determine the method / processing and initiate an error indication method / processing DSAAP.
136
As an additional example, ffifilTUTO MEXICANO Wa ^ eSI B £ THE PROPERTY
INDUSTRIAL when a message is received that starts a method / procedure that does not have a message to report the result of the method / procedure, containing one or more IEs / groups of IEs marked with Ignore IE and notify sender that the receiving entity does not understand, the receiving entity may ignore the content of the IEs / groups of IEs that it does not understand, continue the method / procedure as if the understood IEs / groups of IEs (with the exception of the report) using the understood IEs / groups of IEs have not been received, and initiate a DSAAP error indication method / procedure to report that one or more IEs / groups of IEs have been ignored.
In another embodiment, by way of example, when a response message is received containing one or more IEs / groups of IEs marked with Ignore IE and notify sender that the receiving entity does not understand, the receiving entity may ignore the content of the IEs / groups of IEs included, continue the method / procedure as if the misunderstood IEs / groups of IEs (with the exception of the report) had not been received with the use of the understood IEs / groups of IEs and initiate a DSAAP error indication method / procedure.
In a modality form, the entity (eg, DSC, DPC, etc.) can be configured to ignore or omit a method / procedure in response to the determination that an information element (IE) included in a message
137
<img file="MX353239B_D0161.tif" />
incomprehensible and that the criticality information value for that IE is set to Ignore IE.
As an example, when a message is received that initiates a method / procedure that contains one or more IEs / groups of IEs marked with ignore IE that the receiving entity does not understand, the receiving entity may ignore the content of the IEs / groups of IEs not understood and continue with the method / procedure as if the IEs / groups of IEs not understood had not been received using only the IEs / groups of IEs included.
As a further example, when you receive a reply message that includes one or more IEs / groups of IEs marked with Ignore
<img file="MX353239B_D0162.tif" />
can
<img file="MX353239B_D0163.tif" />
<img file="MX353239B_D0164.tif" />
receiving entity comprises, receiving
<img file="MX353239B_D0165.tif" />
continue
IEs./groups
<img file="MX353239B_D0166.tif" />
IEs
<img file="MX353239B_D0167.tif" />
included
<img file="MX353239B_D0168.tif" />
with
<img file="MX353239B_D0169.tif" />
method / procedure like
<img file="MX353239B_D0170.tif" />
<img file="MX353239B_D0171.tif" />
IEs / groups
<img file="MX353239B_D0172.tif" />
<img file="MX353239B_D0173.tif" />
<img file="MX353239B_D0174.tif" />
included
<img file="MX353239B_D0175.tif" />
IEs
<img file="MX353239B_D0176.tif" />
<img file="MX353239B_D0177.tif" />
Ignore
<img file="MX353239B_D0178.tif" />
<img file="MX353239B_D0179.tif" />
<img file="MX353239B_D0180.tif" />
included marked with
<td>notify</td><td colspan="2">transmitter</td><td>with the use of a</td><td>Message from</td><td>answer</td>
<td>definite</td><td>for</td><td>the</td><td colspan="3">method / procedure, the element of</td>
<td colspan="2">IE information</td><td>of</td><td>diagnosis of</td><td>criticality</td><td>or can</td>
<td>include</td><td>at</td><td>IE</td><td>diagnostic of</td><td>criticality</td><td>for each</td>
138
<img file="MX353239B_D0181.tif" />
<img file="MX353239B_D0182.tif" />
IEs / groups of informed IEs.
In a form of modality, the <sup>or</sup>> <~ ί <sup>Ι</sup>^=<sup>><;|</sup>^ _Γ £ .Γ '<? · Γ<sup>Ι</sup>~ Γ '^<sup>=</sup> (p — aj-, '
DSC, DPC, etc.) can be configured to initiate a method of
<td>indication of</td><td>error</td><td colspan="2">DSAAP (described</td><td>with</td><td>anteriority</td><td>with</td>
<td>reference to</td><td>the</td><td>Figures</td><td>17A-B)</td><td>in</td><td>answer to</td><td>the</td>
<td>determination</td><td>of what</td><td>can not</td><td colspan="2">decode</td><td>an IE type</td><td>of</td>
<td>message in a</td><td>message</td><td>received.</td><td>In a</td><td colspan="2">modality form,</td><td>the</td>
Entity can be configured to consider only the IEs specified in the version of the description used by the component when determining the correct order for the IE included in a message.
In a modality form, the receiving entity (eg DSC, DPC, etc.) can be configured to handle the missing IEs / groups of IEs in accordance with the criticality information for the IEs / groups of IEs in the message received specified in the version of this document used by the recipient.
As an example, the receiving entity (eg DSC, DPC, in order not to execute some of the functional requests of a received initiation message in response to the determination that the received message lacks one or more IEs / groups of IEs with specified criticality Reject IE The receiving entity may reject the method / procedure and report missing IEs / groups of IEs using the message normally used to
139 reporting a result received in the initiation message was insufficient to determine a value for all IEs that are required to be present in the message used to report the unsatisfactory result of the method / procedure, the receiving entity may terminate the method / procedure and initiate a DSAAP error indication method / procedure.
As a further exemplary modality, when a received message initiating a method / procedure that does not have a message to report unsatisfactory result lacks one or more IEs / groups of IEs with specified criticality Reject IE, the receiving entity may terminate the method / procedure starts a DSAAP error indication method / procedure.
In another form of exemplary mode, when a response message is received in which one or more IEs / groups of IEs with specified criticality are not present
Rejecting IE, the receiving entity may consider the method / procedure as unsuccessful and initiate an error handling method / procedure locally.
Another exemplary modality, when a received message initiating a method / procedure lacks one or more IEs / groups of IEs with specified criticality Ignore
140 i
and 14 pi ii. xva. .i ¡INSTITUTO MEXICANO DS LA PROPIEDAD INDUSTRIAL IE and notify issuer the receiving entity can ignore these
IEs are absent to continue method / procedure based on other IEs / groups
IEs are present in the message and report in the message
<img file="MX353239B_D0183.tif" />
response of the method / procedure that were more IEs / groups of IEs. When the initiation message information is insufficient for one absent or received in determining a value for all IEs / groups of IEs that are required to be present in the reply message, the receiving entity may terminate the method / procedure and initiate a DSAAP error indication method / procedure.
As another embodiment, by way of example, when a message is received that starts a method / procedure that does not have a message to report that the result of the method / procedure lacks one or more IEs / groups of IEs with specified criticality Ignore IE and notify issuer, the receiving entity may ignore that those IEs elements are absent and proceed with the method / procedure in the other IEs / groups of IEs present in the message and initiate a DSAAP error indication method / procedure to report that one or more IEs / groups IEs were absent.
By way of another example embodiment, when a received response message lacks one or more IEs / groups of IEs with specified criticality Ignore IE and notify sender, the receiving entity may ignore that those IEs are absent and
141
IMPIOS
MEXICAN INSTITUTE V_ ·
DE La Pf.Or-tlDAO VS-üJ-tSw ** 'iNtLÍSTÍUAL continue with
IEs / groups of the method / procedure based on the others
IEs present in the message and initiating a DSAAP error indication method / procedure to report that one or more IEs / groups of IEs were absent.
As another embodiment, by way of example, when a received message initiating a method / procedure lacks one or more IEs / groups of IEs with specified criticality Ignore
IE, the receiving entity can ignore that the IEs elements are absent and continue with the method / procedure based on the other IEs / groups of IEs present in the message.
As another form of mode, by way of example, when a received response message lacks one or more IEs / groups of IEs with specified criticality Ignore IE, the receiving entity may ignore the IEs / groups of IEs are absent and continue with the method / procedure based on the other IEs / groups of IEs present in the message
The receiving entity (eg DSC, DPC, etc.) can be configured to respond to messages that include IEs or groups of IEs that were received in the wrong order, include too many occurrences, or are erroneously present (that is, they are included and marked as conditional when the condition is not met) in various ways. As an example, the receiving entity (eg, DSC, DPC, etc.) may be configured not to execute any of the functional requests for an initiation message received in response
142
<img file="MX353239B_D0184.tif" />
to the determination that the message received groups of IEs in an incorrect order, includes
<img file="MX353239B_D0185.tif" />
occurrences of an IE or includes erroneously present IEs. The receiving entity may reject the method / procedure and report the value of causes of abstract syntax error (poorly constructed message) using the message normally used to report an unsatisfactory result of the method / procedure.
When the information received in the initiation message is insufficient to determine a value for all IEs elements that are required to be present in the message used to report the unsatisfactory result of the method / procedure, the receiving entity may terminate method / procedure and initiate a method / procedure of the DSAAP error indication.
By way of another example, when a message that starts a method / procedure that does not have a message to report the unsatisfactory result is received containing
IEs / groups of IEs in an incorrect order or with too many occurrences or erroneously present, the receiving entity may terminate the method / procedure and start a DSAAP error indication method / procedure using the cause value Abstract syntax error (poorly constructed message ).
As another example, when you receive a message from
<img file="MX353239B_D0186.tif" />
<img file="MX353239B_D0187.tif" />
<img file="MX353239B_D0188.tif" />
143 answer containing IEs or groups of IEs in, - ..
incorrect or over-occurring or erroneously present, the receiving entity may consider the method / procedure as unsatisfactorily completed and initiate error handling locally.
As previously described, protocol errors include transfer syntax errors, abstract syntax errors, and logical errors. A logical error occurs when a message is understood correctly, but the information contained within the message is invalid (eg, semantics error) or describes a method / procedure that is not compatible with the state of the receiving entity.
In a modality form, a receiving entity (eg DSC, DPC, etc.) can be configured to perform error response operations based on the method / procedure class and disregarding the criticality information of the IEs / groups of IEs that contain erroneous values in response to the determination / detection of a logical error.
As an example, when a logical error is detected in a class 1 method / procedure request message and the method / procedure has a message to report this unsatisfactory result, this message may be sent with an appropriate cause value ( that is, in a cause IE)
τ.γ—>
<img file="MX353239B_D0189.tif" />
144
IMPI
MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY such as semantic error or message not compatible with the state of the receiver.
When a logical error is detected in a class 1 method / procedure request message and the method / procedure does not have a message to report this unsatisfactory result, the method / procedure may be terminated and a method / procedure of indication of DSAAP error with an appropriate cause value. When the logical error exists in a response message to a class 1 procedure, the procedure can be considered as unsuccessful and local error handling can be initiated.
When a logical error is detected in a message from a class 2 procedure, the procedure may terminate and initiate a DSAAP error indication procedure with an appropriate cause value.
In the various forms of modality, the receiving entity (eg DSC, DPC, etc.) can be configured to perform an error handling method / procedure locally (as opposed to an error indication method / procedure DSAAP) when a protocol error is detected in the ERROR INDICATION message. In the event that a reply message or error indication message needs to be forwarded, but the information required to determine the recipient of that message is absent, the procedure may be considered unsuccessful and the
145
<img file="MX353239B_D0190.tif" />
<img file="MX353239B_D0191.tif" />
local error handling.
ends a procedure,
When an error is made, the forwarded cause value may reflect the error that caused the termination of the procedure even though one or more abstract syntax errors with criticality ignore and report have previously occurred within the same procedure.
Figure 18 illustrates the operations and information flows between various components when performing a resource update method of
DSA 1800 in accordance with an embodiment of the invention. In the exemplary embodiment, illustrated in Figure 18, the DSA 1800 resource update method operations are performed by various components, including a wireless device 102, a first eNodeB node 116a, a first SGW gateway 118a, a first DSC controller 144a, a DPC controller 146, a second DSC controller 144b, a second SGW gateway 118b, and a second eNodeB node 116b. The first eNodeB node 116a, the first SGW gateway 118a, and the first DSC controller 144a are included in a first network (that is, a lessor network). The second DSC controller 144b, the second gateway SGW 118b, and the second node eNodeB 116b are included in a second network (that is, a lessor network).
In operation block 1802, wireless device 102 can join the tenant network.
146
<img file="MX353239B_D0192.tif" />
Mexican INSTITUTE OS LA rRONEDAD industrial
<img file="MX353239B_D0193.tif" />
In operation block 1804, the first eNodeB node 116a can monitor and report resource usage and congestion levels at the node level to the first DSC controller 114a. This operation can be performed by the first eNodeB node 116a by generating and sending a resource update message to the first DSC 144a, either directly (eg via the Xe interface) or via the first SWG gateway 118a (eg via the Sl-U interface). In one embodiment, the first eNodeB node 116a may generate the resource update message to include appropriate information to report the level of resource usage for multiple cells, including the cell into which wireless device 102 is incorporated. In various modality forms, the first eNodeB node 116a can be configured to send the resource update message periodically or in response to detection of an operating condition or event (eg, a new embedded wireless device, etc.). ).
In operation block 1806, the first SGW gateway 118a may use the information included in the received resource update message to update its resource usage records and / or forward the resource update message to DSC controller 144a. At
<img file="MX353239B_D0194.tif" />
block
<img file="MX353239B_D0195.tif" />
operations
<img file="MX353239B_D0196.tif" />
SGW 118a
147 can start the operation of a
<img file="MX353239B_D0197.tif" />
MEXICAN INSTITUTE OF PROPERTY ¡KD tempor:
resource update confirmation. In ”eT * EToqüe * '' of“ 1810 operations, the first DSC 144a controller can generate and send a resource update confirmation message to the first eNodeB node, either directly or through the first SWG gateway 118a. In operation block 1812, the first SGW gateway 118a can forward the resource update confirmation message to the first eNodeB node 116a and / or use the information included in the received confirmation message to update its resource usage records. In operations block 1814, the first SGW 118a gateway can
<td>interrupt</td><td>the</td><td>functioning</td><td>of the</td><td>timer</td><td>of</td>
<td>confirmation</td><td colspan="2">update</td><td>resources</td><td>in response</td><td>to the</td>
<td colspan="3">confirmation message received</td><td>me in</td><td>answer to</td><td>the</td>
<td>determination</td><td>of</td><td colspan="2">that the message of</td><td>confirmation</td><td>of</td>
<td>upgrade</td><td>of</td><td>resources was</td><td colspan="2">received before</td><td>the</td>
<td>termination</td><td>of the</td><td>functioning</td><td>of the</td><td>timer</td><td>of</td>
resource update confirmation.
In operation blocks 1816-1822, the first eNodeB node 116a can periodically report usage / congestion levels and the first DSC controller 114a and the first SGW gateway 118a can update their resource usage records, which can be done by performing the same or similar operations as those carried out in the
148
<img file="MX353239B_D0198.tif" />
operations 1804-1814. Similarly, in operations block 1850-1866, the second eNodeB node 116b, the second DSC controller 114b, and the second SGW gateway 118b can perform the same or similar operations as those performed as part of operation blocks 1804-1822.
In operation blocks 1824 and 1826, the first DSC controller 114a can determine if excess resources are available on the first network for allocation to other networks and send a resource availability message to the DPC controller 146. The resource availability message it may include adequate information to inform DPC 146 of the resources determined to be available for allocation. DPC controller 146 can be configured to receive, store, or maintain resource availability information for multiple DSC controllers and / or for multiple different networks (eg, ID identifiers from different PLMNs).
At operation block 1828, the first DSC controller 114a can operatively start a timer. In operation blocks 1830 and 1832, the first DSC controller 114a can start or participate in an auction by monitoring its available / remaining resources and sending resource availability announcements to DPC 1830. In operation block 1834, the first DSC controller 114a can determine run time has expired
149
<img file="MX353239B_D0199.tif" />
Π './ ΠιΤ
VA Λ IWHT'JTO MEXICANO CE THE INDUSTRIAL PROPERTY of the timer and discontinue the announcement of its resources
In blocks of operations 1870-1880, the second controller
DSC 114b can perform the same or similar operations as those performed as part of the operations block
1824-1834.
Figure 19 illustrates a DSA 1900 method, in one embodiment, of allocating resources in a first communications network for access and use by a second communications network. The operations of the DSA 190 0 method can be performed per processing core of a DPC component 146.
In block 1902, a component of
DPC
146 you can establish a communications link with a
DSC
144 a in a first communication network. In the operations block
1904, DPC controller 146 can determine whether or not a telecommunication resource of the first communication network is available for allocation based on information received via the communication link. In one form of mode, DPC controller 146 can determine that the telecommunication resource is available for allocation at a future date and time.
can broadcast a communication signal that includes adequate information to inform a plurality of networks
In operations block 1906, the DPC driver
146
150
IMPIOS
MEXICAN INSTITUTE —P> ·
D? LA? * O> IEDAD T · ÍY tNOUSTMAL of communications of the telecommunications resource including a start time of the auction. In operations block 1908, DPC 146 may receive offers from a plurality of communication networks for the determined telecommunication resource to be available for allocation to it in response to the broadcast of the communication message and after the start time of the communication. auction that is included in the broadcast communications signal.
In one form of modality, the offers received from the plurality of communication networks may include the receipt of offers for access and use of the telecommunication resource determined at the future date and time.
In block of operations 1910, the DPC driver
146 You can only accept bids received from authorized networks determined to be eligible for your participation in the auction. By way of example, DPC controller 146 can determine whether or not the telecom resource is compatible with each of the plurality of communication networks, authorize networks in the plurality of communication networks as being eligible to participate in the auction based on its compatibility with the telecommunications resource and accepting offers from only authorized networks.
In block of operations 1912, DPC 146 can
151
<img file="MX353239B_D0200.tif" />
<img file="MX353239B_D0201.tif" />
<img file="MX353239B_D0202.tif" />
CB LA ÍXOHEDAD
INDUSTIUAL communications for access and use by a second communication network in the plurality of communication networks based on accepted offers. In one form of embodiment, the allocation of the telecommunication resource may include the allocation of the telecommunication resource of the first communication network to be accessed and used by the second communication network at the future date and time. In operation block 1914, DPC 146 may send a communication message to the second communication network including information suitable for informing the second communication network that use of the allocated telecommunication resource can be initiated. In the 1916 block of operations,
<td>the DPC</td><td> 146</td><td>can</td><td>register a</td><td>transaction in</td><td>one base</td><td>of</td>
<td>data</td><td>of</td><td colspan="2">transactions that</td><td>identify the</td><td>resource</td><td>of</td>
<td colspan="3">telecommunications</td><td>as being</td><td>assigned for your</td><td>use by</td><td>the</td>
second communications network.
In block of operations 1918, DPC 146 can demand the return of the assigned telecommunications resource. In block of operations 1920, DPC 146 can broadcast a second communication signal to inform the plurality of communication networks that the telecom resource is available for reallocation through a second auction.
Figure 20 illustrates another DSA 2000 method in one way.
152
<img file="MX353239B_D0203.tif" />
<img file="MX353239B_D0204.tif" />
modality of the
PI nermrro mexicana Dí LA FKGtltDAD INDUSTRIAL allocation of resources in a first communication network for access and use by a second communication network.
Method operations
DSA 2,000 can be performed by a component's processing core
DPC 146.
In block 2002, the component of
DPC
146 can establish a communications link with a DSC
144a in the first communication network. In the block
2004, the component of
DPC
146 You can determine that a resource on a first communication network is available for allocation. In block 2006, the DPC component
146 it can broadcast a first communication signal informing a plurality of communication networks that the resource is available for allocation and of a geographic area associated with the resource. In operations block 2008, DPC component 146 can allocate the resource of the first communication network for access and use by a second communication network in the plurality of communication networks. In operations block 2010, the DPC component 146 may broadcast a second communication signal informing the second communication network that the use of the assigned telecommunication resource may be initiated in the geographic area. In block of operations 2012 the DPC component 146 can record a transaction in a transaction database that identifies the resource of
153 telecommunications as being assigned
IW go 1 tNSTTTVTO MEXICANO DE LA PKOFUOM »ÍWUSTSUAL for use
<img file="MX353239B_D0205.tif" />
second communications network.
In the 2014 block of operations, the
DPC
146 You can demand the return of the assigned telecommunications resource. In the operations block
2016, DPC 146 can broadcast a second communication signal to inform the plurality of communication networks that the telecom resource is available for reassignment through a second auction.
In one form of embodiment, the DSA 2000 method may further include a DPC component 146 that receives the resource configuration information regarding a resource allocation system from a first DSC controller 144 in the first communication network and sending the resource configuration information to a second DSC 144 on the second communication network. In another form of modality, the DSA 2000 method may include the DPC component 146 that receives coordination information regarding the availability of the telecommunication resource based on geographic areas from the first DSC 144 and sending the information of Coordination configuration to the second DSC 144.
In another form of modality, the DPC component 146 can be configured to negotiate a resource leasing system between the first and second networks of
*. ♦ Λ »?; '
154
<img file="MX353239B_D0206.tif" />
ÜNSWTUTO MEXICANO OE ΙΑ ΗϊΟΗΕΟΛΠ tNDUSTMAL
<img file="MX353239B_D0207.tif" />
communications for a resource use and coordinating a transfer of a wireless device between the first and second communication networks based on the geographic boundaries defined in the resource leasing plan. The DPC 146 can further be configured to determine the validity of a subscriber device (eg, wireless device 102) of the second communication network based on the proximity of the subscriber device to the geographic area, the level of quality of service available for the subscriber device and / or information included in the resource leasing plan.
In various modalities, the DPC controller 146 can be configured to instruct the subscriber device to change networks or to establish a communication link for a resource in the first communication network based on the proximity of the subscriber device to the geographical area, the level of quality of service available to the subscriber device and / or terms of the resource leasing system. DPC controller 146 can be configured to instruct a subscriber device that is actively connected or that uses the telecommunication resource to change networks and / or incorporate another resource based on the proximity of the subscriber device to the geographic area.
As previously described, the various forms • jcrtrs> TSBr> »3j»
155 modality may include a
IMPIfs
MEXICAN INSTITUTE t '-'.- L
DE LA FF.OHSDAD Y '· .. · INDUSTRIAL component of PCRF 134 configured to receive congestion status information from node eNodeB from DSC 144 or from node eNodeB 116, to establish categories of wireless devices incorporated into the same network ) eNodeB node 116 (and / or other eNodeBs nodes in in one or more categories (eg primary, secondary, congestion-prone users, etc.) and to perform various congestion response operations based on the categories and / or subcategories to which the devices belong to reduce congestion at node eNodeB 116.
Figure 21 illustrates a method 2100 for controlling congestion levels of an eNodeB 116 node. Method 2100 can be performed by processing cores of a PCRF 134 component, a PCEF 128 component, an eNodeB 116 node component, or one of their combinations.
In operation block 2102, a processing core can monitor user traffic (eg, call and data traffic, etc.) or congestion of the eNodeB node at the RAN level. As part of these operations, the processing core can monitor call volume, resource usage, number of active connections, bandwidth, etc. to determine whether or not network activity exceeds a threshold value. In a form of modality, the processing kernel can monitor traffic from
156 users and congestion getting
IPI
MEXICAN INSTITUTE OF PROPERTY
<img file="MX353239B_D0208.tif" />
congestion from a DSC or the nodes a current congestion state (eg Normal, Minor, Major, Critical, etc.) of the eNodeB node. Each congestion state can be associated with a level of congestion. As an example, the Normal congestion state may indicate that the eNodeB node, etc., is operating under normal conditions, the Minor congestion state may indicate that the eNodeB node is experiencing minor congestion, the Major congestion status may indicate that the eNodeB node is experiencing significant congestion, and the Critical congestion status may indicate that the eNodeB node is experiencing severe congestion or an emergency situation.
At determination block 2104, the processing core can determine whether the eNodeB node is congested. As an example, the processing kernel can determine if the current congestion status of the eNodeB node is Minor, Major, or Critical. In response to the determination that the eNodeB node is congested (that is, it is verified that determination block 2104 = Yes), in operation block 2106 the processing kernel may perform various policy or control operations to put practice stricter policy rules and / or coordinate the operations of network components to
157 reduce node congestion level
ΙΜΡΙ £> ξ>.
MEXICAN INSTITUTE ''. <sup>1</sup> i
FROM THE raOPISUw AND '\ i ·' <
eNodes?<sup>lST</sup>5t<sup>or</sup>· Sample mode, the processing kernel can generate a strict policy nail that prevents new devices from joining the eNodeB node and sending the generated policy rule to a PCEF 128 for execution.
In other forms of embodiment, by way of example, in the operation of block 2104, the processing core may perform various congestion response operations to perform various functions, including interrupting or preventing the creation of additional media for the devices. selected incorporated into the eNodeB node, interrupting or preventing new devices from joining the eNodeB node, interrupting or preventing an upgrade of radio supports from selected devices, transferring selected devices to a non-congested eNodeB node on the same network as the congested eNodeB node based on device location, decrease of the binary rates consumed by the selected devices modifying the supports of the services, removing media from selected devices to free up resources, transferring selected devices to an uncongested eNodeB node on a different network based on device location and service level agreement with another network, the termination or
158
<img file="MX353239B_D0209.tif" />
<img file="MX353239B_D0210.tif" />
removal of selected devices (eg, devices determined to contribute to a greater extent to the congestion levels of the eNodeB node) and other similar operations to mitigate or reduce the level of congestion of the eNodeB node. The processing core may repeat the operations of blocks 2102 to 2106 inclusive until it determines that the eNodeB node is no longer congested (that is, it is in a Normal congestion state).
In response to the determination that the eNodeB node is not congested (that is, in determination block 2104 = No), in operation block 2108, the processing kernel can determine whether the current policy rules are strict rules with the goal of reducing congestion levels of the eNodeB node. In response to determining that current policy rules are strict rules (that is, in determination block 2108 = Yes), in operation block 2110, the processing kernel may establish normal or less strict policy rules. As an example, in operation block 2110, the processing core may generate an updated policy rule that allows (or does not prevent) new devices from joining the eNodeB node. In response to the determination that the current policy rules are not too strict or are mainly
159
<img file="MX353239B_D0211.tif" />
<img file="MX353239B_D0212.tif" />
Aimed at reducing congestion levels at node eNodeB (that is, at determination block 2108 = No), the processing kernel can continue monitoring congestion levels at node eNodeB in operation block 2102. Operations Blocks 2102-2110 can be performed repeatedly, periodically, continuously or almost continuously to control / manage the congestion levels of the eNodeB node.
Figure 22 illustrates a method 2200 for reducing the congestion level of an eNodeB node based on categories and / or subcategories in accordance with one form of modality. Method 2200 can be performed by a PCRF 134 component processing core.
In method 2200 block 2202, the processing core can receive congestion status information from an eNodeB node in its network and determine that the eNodeB node is congested. The congestion status information may include a wireless congestion status information that identifies the wireless devices that are attached to (or are being served by) the eNodeB node. In operation block 2204, the processing core can establish categories of identified wireless devices (ie devices attached to the eNodeB node) that are subscribers to its network as primary devices. In a form of modality,
160
IMPIOS
INSTITUTO MEXICANO D £ LA PROPIEDAD INDUSTRIAL the processing core can establish categories of wireless devices based on the information received from the eNodeB node, such as a device identifier, classification information, usage information, user profile information , etc. In another form of modality, setting the processing core can be configured for categories of wireless devices based on information received from other network components (eg,
MME,
Going back to the
Figure 22, in the operations block
2206, the processing core may establish categories of identified wireless devices that are subscribed to other networks (that is, to a tenant network, etc.) as secondary devices. In the operations block
2208, the processing core can further establish categories of primary and secondary devices into subcategories.
These subcategories can include users prone to congestion, users with data-sensitive applications, and users with server-sensitive applications. In various forms of modality, the processing core can classify devices into these and other subcategories based on the data applications used by the devices, user subscription details, user operational feedback, user profiles, operator policies ,
Λ ·.
IMPI f
VÜ --- Ί 'A MEXICAN INSTITUTE
OF PROPERTY 1
INDUSTRIAL PROCESSING MAY CONGESTION ON WHICH THEY BELONG
161 etc.
At block 2210, the core performs response operations based on the categories and / or subcategories of the devices. By performing congestion response operations based on the categories and / or subcategories to which the devices belong, the processing core can intelligently reduce or mitigate user traffic and congestion levels of the eNodeB node and / or continue providing an appropriate service to its highest priority users (ie., network subscribers, etc.).
Figure 23 illustrates various congestion response operations, for example, 2302-2316, any or all of which may be performed by a PCRF 134 component processing core in response to the determination that the eNodeB node it is congested (eg, as part of operation block 2210 illustrated in Figure 22).
More specifically, operation block 2302 of Figure 23 illustrates that the processing core may interrupt the creation of additional media for selected devices incorporated into the eNodeB node. Alternatively or additionally, the processing kernel can prevent new devices from joining the node
162
IMPIt
M5XKANO INSTITUTE '0: INDUSTRIAL PILOTISTY eNodeB in block 2304. The processing core the radio supports for can interrupt or prevent the upgrade of the selected devices in processing can perform the block 2306. The core a transfer of the selected devices to an uncongested eNodeB node on the same network as the congested eNodeB node based on the location of the device in block 2308. The processing core can decrease its bit rates consumed by selected devices by modifying the media of the devices in block 2310. The processing core can free up resources by deleting the media from selected devices in operation block 2312. The processing core may transfer selected devices to an uncongested eNodeB node in a different network based on a device location and service level agreement with another network in block 2314. The processing core may terminate / delete the selected devices in block 2316. As an example, the processing kernel may remove certain services to contribute more to eNodeB node congestion levels or devices classified in the congestion-prone user subcategory at block 2316.
In the various forms of modality, these and others
163
<img file="MX353239B_D0213.tif" />
<img file="MX353239B_D0214.tif" />
Priority-based, congestion response operations can be performed —WMWEmtWiH Rirt ir · »mu mcái-ú Vk categories and / or subcategories associated with wireless devices. As an example, a processing kernel can be configured to apply congestion response operations to secondary devices before applying them to primary devices.
Consequently, the congestion processing core at can intelligently reduce or mitigate the eNodeB node while continuing to provide an appropriate service to its highest priority users (ie primary devices).
Figure 24 illustrates a 2400 congestion response method, according to one form of modality, for reducing the level of congestion of an eNodeB node. Method 2400 can be performed by a processing core of a PCRF component. In one embodiment, method 2400 can be performed in response to the PCRF component's determination that the eNodeB node is congested (that is, in response to the determination that the eNodeB node's congestion status is Least, Highest , or Critical).
At block 2402, the processing core can select primary devices, secondary devices, or both at the same time. At block 2404, the processing kernel can interrupt or prevent the creation of additional media on the congested eNodeB node for
164 '^ 4 ··' .'- i
MEXICAN INSTITUTE V OF PROPERTY V t '' INDUSTRIAL XttXÍ and selected devices.
Ά 'jt
As an example, if the processing kernel selects secondary devices in the operations block
2402, in such a case, the processing core may interrupt or prevent the creation of additional media by secondary devices in the block
2404. In one embodiment, as part of operation block 2404, the processing core may interrupt / prevent the creation of additional media based on the priorities or categories to which the devices belong. As an example, when primary devices and secondary devices are selected in operation block 2402, the processing core may interrupt the creation of additional supports for secondary devices before stopping additional supports for primary devices in block 2404.
If these operations (that is, preventing the creation of additional media by secondary devices) are not adequate to reduce the congestion level of the eNodeB node, the processing kernel can perform these and other congestion response operations on the same or different categories of devices. In one form of modality, the processing kernel may be configured to perform these or other response operations to the
165
<img file="MX353239B_D0215.tif" />
IMPI tMrmUTO MEXICANO GIVE the congestion property until the congestion status of the node returns to its normal condition (that is, until qw Β1 ^ δί'3'βϋ congestion of the eNodeB node is set to Normal).
As described above, in operation block 2404, the processing core can interrupt / prevent the creation of additional media. The above can be done by generating strict policy rules and sending the generated policy rules to a PCRF component for execution. The processing core may also interrupt / prevent the creation of additional media by rejecting (or causing another component to reject) the other credit control (CCRs) that are associated with the selected devices (i.e. primary devices, secondary devices, or both at the same time).
Returning to Figure 24, in operation block 2406, the processing core can reject the CCRs of the selected devices and / or send fault messages to the devices that demand / require additional CCRs. In operation block 2408, the processing kernel may receive updated eNodeB node congestion state information indicating that the eNodeB node is now operating in the Normal congestion state (or a notification message indicating that the eNodeB node is already not congested). In operations block 2410, the ν ν η
166
V '.' ··:
processing core can start the selected devices proceed
IMPI
INSTITUTO MEXICANO ¡? Í LA a \ O> ic -'AO INDUSl ¡UAL permission for them to create additional supports in the eNodeB node. The above can be done by generating and sending updated (i.e. less stringent) policy rules to the PCRF component for execution, accepting CCRs from selected devices, etc.
FIG. 25 illustrates another congestion response method 2500, according to another form of modality, for reducing the congestion level of the eNodeB node. Method 2500 may be performed by a processing core of a PCRF 134 component, such as in response to PCRF determination that the eNodeB node is congested.
In operation block 2502, the processing core can select primary devices, secondary devices, or both at the same time. In operations block 2504, the processing core can prevent new devices from joining the congested eNodeB node. In a modality form, the above can be done by generating strict policy rules and sending the generated policy rules to a PCRF component for execution. In operation block 2506, the processing core may reject CCR messages that demand or require the creation of a new IP-CAN session from the selected devices and / or send
167 r,
V · '<
Fault messages to devices that send or demand CCRs. In processing operation block 2508, the kernel may receive updated eNodeB node congestion status information indicating that the eNodeB node is now operating in the Normal congestion status (or a notification message indicating that the eNodeB node is already not congested).
At operation block 2510, the processing kernel may begin to allow selected devices to join the eNodeB node. In various forms of modality, the above can be done by generating and sending updated policy rules to the
PCEF accepting the CCR that demand or require the creation of a new session of
IP-CAN from selected devices,
Figure 26 illustrates another 2600 congestion response method according to another form of modality, to reduce the congestion level of the eNodeB node. The 2600 method can be performed by a single component processing core
PCRF 134 in response to the determination that the eNodeB node is congested (that is, that the congestion status of the eNodeB node is Minor, Major, or Critical).
In operation block 2602, the processing core can select primary devices, secondary devices, or both at the same time. At block 2604, the processing core may additionally select
168 grouped devices prone to creating
MEXICAN INSTITUTE
DS LA PRORIBIMO \ ',
INDUSTRIAL in the congestion user sub-category from selected devices (ie primary devices, secondary devices, or both at the same time). As an example, if secondary devices are selected in the operation block
2602, the processing core can select only the secondary devices that are grouped in the sub-category of users prone to creating congestion. The foregoing allows the processing core to apply congestion response operations first to a concentrated subset of all identified wireless devices, and then to other groups / categories if congestion persists. Consequently, the processing kernel can intelligently reduce congestion (eg by first limiting the devices that are most likely to contribute greatly to network congestion etc.) and / or with better prioritization. for access and use of network resources (eg, allowing highest priority users to continue to use network resources, etc.).
In operation block 2606, the processing core may interrupt or prevent the enhancement of radio supports in the eNodeB node for selected devices and / or based on priorities / categories. In block 2608, the processing core
169
<img file="MX353239B_D0216.tif" />
can reject CCRs messages
IMPI
MEXICAN INSTITUTE OF INDUSTRIAL PROPERTY that demand / require increases in the binary rates for the existing supports from the selected devices and / or send fault messages to the devices that send / demand the CCRs.
At operation block 2610, the processing core may receive a notification message indicating that the eNodeB node is no longer congested (eg, updated eNodeB node congestion status information). In the operations block
2612, the processing kernel may begin to allow selected devices to enhance radio supports on the eNodeB node (eg, by generating updated policy rules,
Figure 27 illustrates another 2700 congestion response method to reduce the congestion level of the eNodeB node. Method 2700 can be performed by a PCRF 134 component processing core in response to the determination that the eNodeB node is congested.
In operation block 2702, the processing core can select primary devices, secondary devices, or both at the same time. In the operations block
2704, the processing kernel can also select devices grouped into the selected devices sub. As an example, if secondary devices are selected in the category of users prone to creating congestion from
170
<img file="MX353239B_D0217.tif" />
<img file="MX353239B_D0218.tif" />
In operations 2702, the processing core selects only the secondary devices that are grouped in the sub-category of users prone to creating congestion in block 2704.
In operation block 2706, the processing core can determine the locations of the selected devices (eg, secondary devices that are grouped into the sub-category of users prone to creating congestion), to identify the uncongested target eNodeBs nodes that are on the same network as the congested eNodeB node based on device locations and identify the selected devices to be transferred based on the availability and proximity of eNodeBs nodes uncongested targets. In block 2708,
<td>the processing core can report</td><td>to the</td><td>node</td><td>eNodeB</td><td>of</td>
<td>that the selected devices have</td><td>of</td><td>to be</td><td>obj eto</td><td>of</td>
<td>transfer to the target eNodeB node.</td><td>In</td><td>a</td><td>shape</td><td>of</td>
mode, the above can be done by the PCRF by instructing a DSC component to initiate a handover procedure, which can cause the DSC to report to the congested eNodeB node the devices that are selected for handover and the target eNodeB node to that the selected devices must be transferred.
171
<img file="MX353239B_D0219.tif" />
<img file="MX353239B_D0220.tif" />
Figure 28 illustrates 2800 congestion according to yet another mode form response method, to reduce the congestion level of the eNodeB node. Method 2800 can be performed by a processing core of a PCRF 134 component in response to the determination that the eNodeB node is congested.
In operation block 2802, the processing core can select primary devices, secondary devices, or both at the same time. In operation block 2804, the processing core may further select devices grouped into subcategories of users with delay sensitive applications and / or users prone to creating congestion from selected devices. As an example, the core
<img file="MX353239B_D0221.tif" />
processing can select
<img file="MX353239B_D0222.tif" />
grouped devices
<img file="MX353239B_D0223.tif" />
<img file="MX353239B_D0224.tif" />
subcategory
<img file="MX353239B_D0225.tif" />
users with
<img file="MX353239B_D0226.tif" />
delay sensitive ions and then select grouped devices
<img file="MX353239B_D0227.tif" />
<img file="MX353239B_D0228.tif" />
subcategory
<img file="MX353239B_D0229.tif" />
users
<img file="MX353239B_D0230.tif" />
create congestion. The processing kernel can then perform congestion response operations based on the order in which the devices are selected.
In operation block 2806, the processing core can modify the media for the selected devices to decrease the bit rates consumed by the devices. In a form of modality,
172 . £ 1vA hee. £ V · '· >>' tNSTÍTUTC MEXICANO ·>
¿Míafrofiedao). <··; '
INDUSTRIAL '' processing core can modify support about selected devices. As an example, if the processing kernel selects secondary devices in operation block 2802, the processing kernel can first modify the supports for secondary devices grouped into the user subcategory with delay sensitive applications, and then modify the supports to the secondary devices grouped into the sub-category of users prone to creating congestion. In operation block 2808, the processing core may send a command called Re-Auth-Request that identifies a reduced bit rate for the media on the devices selected for a PGW gateway (which is responsible for filtering user IP packets on downlink on different QoS-based media), so that media is modified across the network and / or across multiple network components.
Figure 2 9 illustrates another 2900 congestion response method, according to another form of embodiment, to reduce the level of the eNodeB node. The 2900 method can be performed by a processing core of a PCRF 134 component in response to determination that the eNodeB node is congested.
In Operations Block 2902, the core of
173
<img file="MX353239B_D0231.tif" />
processing can select secondary devices, or both to operations
2904, the processing core can also select devices grouped into the subcategories of congestion-prone users and / or users with delay sensitive applications from the selected devices. As an example, the processing kernel may first select devices grouped into the congestion-prone user subcategory, and then select devices grouped into the user subcategory with delay-sensitive applications. The processing kernel can then perform congestion response operations based on the order in which the devices are selected.
In operation block 2906, the processing core can delete media for the selected devices to free up the resources consumed by those devices. In one form of modality, the processing kernel can suppress support based on priorities, categories, or the order in which devices were selected. As an example, if the processing core selects secondary devices in operation block 2902, the processing core may delete media for secondary devices
174 grouped in congestion
IMPI títítí 'Mexican institute. FROM PSOf if.DAD V - ..r- V the user subcategory propenssj> ¡®ua before deleting the—— —for secondary devices grouped into the user subcategory with applications sensitive to operations block 2908, the core delay. In processing, you can send a Re-Auth-Request command to delete media from selected devices for a PGW gateway so that media is deleted across the network and / or across multiple network components.
Figure 30 illustrates another congestion response method 3000, according to another form of modality, to reduce the congestion level of the eNodeB node. Method 3000 can be performed by a processing core of a
<td>component</td><td>PCRF</td><td> 134</td><td>in response</td><td>to determination</td><td>of</td>
<td>that the node</td><td>eNodeB</td><td>this</td><td>congested,</td><td></td><td></td>
<td>At</td><td>block</td><td>of</td><td>operations</td><td>3002, the nucleus</td><td>of</td>
Processing can select primary devices, secondary devices, or both at the same time. In operation block 3004, the processing kernel can further select devices grouped into the subcategories of congestion-prone users and users with delay-sensitive applications from the selected devices. As an example, the processing kernel may first select devices grouped into the user subcategory, and then
175 select devices grouped into
IMPI
MEXICAN INSTITUTE 'Λ. >
PROPERTY the sub ^^ brf ^ & e ^ 'users with sensitive applications. El 'the<sup>1</sup> lock you— operations 3006, the processing core can initiate the transfer of selected devices to an uncongested eNodeB node on a different network based on device locations and service level agreement with the other network. In one form of modality, the processing core can initiate transfer of devices based on priorities, categories, or order in which devices were selected. In operation block 3008, the processing core may receive objective network information from the DSC and inform DSC of the selected devices to be transferred in order to cause the DSC to report to the congested eNodeB node, the devices selected and / or the target eNodeB node of the transfer operations.
Figure 31 illustrates another 3100 congestion response method, according to another form of modality, to reduce the node congestion level eNodeB. The 3100 method can be performed by a processing core of a
<td>component</td><td>PCRF</td><td> 134</td><td>in response to the</td><td>determination</td><td>of</td>
<td>that the node</td><td>eNodeB</td><td>this</td><td>congested.</td><td></td><td></td>
<td>At</td><td>block</td><td>of</td><td>operations 3102,</td><td>the nucleus</td><td>of</td>
processing can select primary devices,
176 secondary devices, or both to operations
3104, the core of aac am. jiue ¿fe,.
also select devices grouped in the subcategory of users prone to creating congestion from the selected devices. In operation block 3106, the processing core may initiate termination or deletion of the selected devices based on priorities, categories, or the order in which the devices were selected. In operations block 3108, the processing kernel will send a Re-Auth-Request command to delete the sessions of the users selected for the gateway
PGW.
The various forms of modality may include or use a Dynamic Spectrum Arbitration Application Part Protocol (DSAAP) and / or component that is configured to allow, facilitate, support, or augment communications between two or more DSA components (eg. eg, DPC, DSC, eNodeB node, MME entity, HSS server, etc.) in order to improve the efficiency and speed of the DSA system. A DSA component can be any component described in this application and / or any component that participates in any of the DSA operations, communications, or methods described in this application. As a result, DSAAP components can
177 »
configure allow, facilitate
<img file="MX353239B_D0232.tif" />
MEXICAN INSTITUTE OF THE PROFIF'JA'J support or communications between any of the UUlllpUll '^ lTL<sup>,,</sup>and<sup>,</sup>&<sup>r 1</sup> all described, including communications between a component of
DPC and a DSC component, between the component
DSC and an eNodeB node component, between the
DSC a component of
MME, between the component of
DSC a component of
HSS, between the component of
MME the component of
HSS, between the node component eNodeB and a wireless device,
To facilitate communications between two DSA components, DSAAP components can application programming interfaces (APIs) and / or more edit include client modules that facilitate communications between DSA components. In addition, DSAAP components can be configured to allow DSA components to communicate specific information, use specific communication messages, and / or perform specific operations that together provide various DSA functions that further improve the efficiency and speed of communication systems. DSA and participating networks.
As an example, DSAAP components can be configured to allow an eNodeB node to communicate with a DSC component (eg, through the Xe interface ), with other eNodeBs nodes (eg, through of an X2 interface) and with various other components (eg, by
178
<img file="MX353239B_D0233.tif" />
MEXICAN INSTITUTE OF INDPSTRLAL PROPERTY
<img file="MX353239B_D0234.tif" />
intermediate interface SI). By way of another example, DSAAP components can be configured to allow, facilitate, support, or augment communications between the DSC component and the DPC component in order to allow DPC and / or DSC components to better pool resources through the different networks, to better monitor the traffic and the use of resources in the various networks, to efficiently communicate offers and tender information, to register and reregister components quickly and efficiently and to better perform operational recall operations. DSAAP components can also enhance DSA's resource auction operations by improving the performance and efficiency of procedures for bidding, invoice generation, resource announcement, resource demand, resource purchase, bid credential validation, etc. .
In the various modality forms, all or parts of the DSAAP component can be included in one or more DSA components, such as a DPC component, a DSC component, an eNodeB node component, an MME component, and a component HSS. The DSAAP component can be implemented in hardware, software, or a combination of hardware and software. In one form of modality, the DSAAP component can be configured to implement a DSAAP protocol, which can be defined
179
IMPI
<img file="MX353239B_D0235.tif" />
through the Xe, Xd and / or X2 reference points.
In various forms of modality
WaMraMMWNNHMMMMnRNWKamtaMBW.KriN'-. ' the Xe reference point between DSC and the node a protocol TR-069 TR-192 data for eNodeB can use the DSAAP protocol, and / or model extreme caps to support the list of available resources in the node eNodeB and the notification to the node Offer / purchase confirmation eNodeB. Xd reference point between DSC and DPC can use protocol
DSAAP for resource arbitration and dynamic spectrum operations. Benchmark / interface
X2 between the eNodeBs nodes can also use the protocol
DSAAP to communicate information.
In various forms of modality, the components of
DSAAP can be configured to allow the various components of DSA (eg,
DSC, DPC, eNodeB node, etc.) for communication using the DSAAP protocol and / or to perform various methods of
DSAAP.
The methods of
DSAAP can be done on any of the systems
DSAs examined here, such as a system that includes a first server
DSC in a first telecommunication network (eg, a network in the second telecommunication network (eg, a lessor network) and a DPC server that is outside of the first and second telecommunication networks.
The various forms of modality can be put into
180
<img file="MX353239B_D0236.tif" />
<img file="MX353239B_D0237.tif" />
practice in a diversity of
4'
INSTITUTO ME DE LA INDUSTiU / mobile wireless computing devices, an example of which is illustrated in Figure
32. More specifically, the
Figure 32 is a system block diagram of a mobile transceiver device in the form of a smartphone / mobile phone 3200 suitable for use with any of the modality forms. Cell phone
3200 may include a processor
3201 coupled to an external memory 3202, a visual presentation screen
2 0 3 and to a 3204 speaker.
Additionally, the 3200 mobile phone may include a 32 05 antenna for sending and receiving an electromagnetic radio that can be connected to a wireless data link and / or 3206 mobile phone transceiver coupled to the processor.
3201. 3200 mobile phones also often include menu selector buttons or rocker switches 3207 to receive user input.
A typical 3200 mobile phone also includes a sound encoding / decoding circuit (CODEC)
3208, which digitizes sound received from a microphone into data packets suitable for wireless transmission and decodes received sound data packets to generate analog signals that are provided to speaker 3204 to generate sound.
Also, one or more of the 3201 processor, the transceiver
181
<img file="MX353239B_D0238.tif" />
Wireless 3206 and CODEC 3208 circuit may include a Digital Signal Processor (DSP) circuit (not separately illustrated). The 3200 mobile phone may further include a ZigBee-type transceiver (i.e., a transceiver according to the IEEE 802.15.4 standard) for short-range, low-power communications between wireless devices or other similar communication circuits (e.g. , circuits that implement the protocols of
Bluetooth® or WiFi etc.)
The previously described modes of embodiment, including percent spectrum functions, can be practiced within a broadcast system on any of a variety of commercially available server devices, such as the 3300 server illustrated in Figure 33. The 3300 server it typically includes a 3301 processor coupled to 3302 volatile memory and large capacity nonvolatile memory, such as a 3303 disk drive. The 3300 server may also include a floppy disk drive, compact disc (CD), or DVD 3304 disk drive attached to the 3301 processor. The 3300 server may also include 3305 network access ports coupled to the 3301 processor to establish network connections. data with a 3 3 06 network, such as a local area network coupled to other computers and servers in the communication system.
182
3201 processors,
3301,
IMPI
INSTITUTO MEXIL .... OF THE INDUSTRIAL PROPERTY can be programmable microprocessor, microcomputer or any multiple integrated circuits of processors that can be configured by means of software instructions (applications) that include for the described modalities to carry out a diversity of functions, functions of the diverse ones below. In some forms of wireless devices, multiple processors can be provided
3301, such as a processor dedicated to wireless communication functions and a processor dedicated to running other applications.
Under normal conditions, computer applications can be memorized in internal memory 3202, 3302 before they are accessed and loaded into processor 3201,
3301. Processor
3201, 3301 can include enough internal memory to memorize the application software instructions. On some servers, processor 3301 may include enough internal memory to memorize application software instructions. In some receiving devices, the secure memory may be on a separate memory integrated circuit coupled to the 3201 processor. Internal memory 3202, 3302 can be volatile or nonvolatile memory, such as flash memory or a mixture of both. For the purposes of this description, a general memory reference refers to all "rT.mv. to.
183
<img file="MX353239B_D0239.tif" />
memories accessible by processor 3201, 3301, including internal memory 3202, 3302, removable memory inserted into the device, and memory within processor 3201, 3301, by itself.
The above method descriptions and process flow diagrams are provided merely by way of illustrative examples and are not intended to require or imply that the steps of the various modality forms must be performed in the order presented. As will be appreciated by one skilled in this art, the order of the steps in the above embodiment forms can be performed in any other order. Terms such as hereinafter, then, next, etc., are not intended to limit the order of the stages; these terms are simply used to guide the reader through the description of the methods. Furthermore, any reference to elements of claims in the singular, by way of example, the use of the terms a, one or the / is not to be construed as limiting the element to the singular.
The various illustrative logic blocks, modules, circuits, and algorithm steps described in connection with the embodiment forms disclosed herein can be implemented as electronic equipment, software, or combinations of both. To clearly illustrate this interchangeability of hardware and software,
184
<img file="MX353239B_D0240.tif" />
Various illustrative components, blocks, modules, circuits and stages have been described above, in general, in terms of their functionality. Whether the functionality is implemented as hardware or software will depend on the particular application and the design limitations imposed on the overall system. Those skilled in this art can implement the described functionality in various ways for each particular application, but the implementation decisions should not be interpreted as causing a departure from the scope of protection of the present invention.
The equipment used to implement the various illustrative logics, logic blocks, modules, and circuits described in connection with the embodiment forms disclosed herein can be implemented or performed with a general-purpose processor, a digital signal processor (DPC ), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate, or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described here.
A general-purpose processor may be a microprocessor, but as an alternative.
the processor can be any conventional processor, controller,
185
<img file="MX353239B_D0241.tif" />
<img file="MX353239B_D0242.tif" />
microcontroller or state machine. A processor may also be implemented as a combination of computing devices, eg, a combination of a DPC and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DPC core, or any other of the configurations. . Alternatively, some steps or methods can be performed using circuits that are specific to a given function.
In one or more exemplary aspects of the inventive idea, the described functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be memorized as one or more instructions or code on a non-transient computer-readable medium or a non-transient processor-readable medium. The steps of a method or algorithm disclosed herein can be performed on a processor executable software module that may reside on a non-transient computer readable medium or a processor readable memory medium. The non-transient computer readable or processor readable memory media can be any memory media that can be accessed by a computer or a processor. As an example, but without limitation, the support readable by
186 non-transient computer or media
<img file="MX353239B_D0243.tif" />
MEXICAN INSTITUTE OF LA? Rc: readable ρ<sup>Ε</sup>They may include RAM, ROM, EEPROM, FLA'yH7 ”'^ U' - ^ 0M 'u<sup>1</sup>'another optical disk memory, magnetic disk memory or other magnetic storage device, or any other medium that can be used to store a desired program code in the form of instructions or data structure and that can be accessed by a computer. The disc and disc drive, as used herein, include a compact disc (CD), a laser disc, an optical disc, a digital versatile disc (DVD), a floppy disc, and a disc called a blu-ray where the Discs usually reproduce data magnetically, while the other class of discs reproduce data optically with the use of lasers. The combinations of the above are also included within the scope of non-transient computer readable and processor readable media. In addition, the operations of a method or algorithm may reside as one or any combination or set of codes and / or instructions on a non-transient processor-readable medium and / or a computer-readable medium, which may be incorporated into a computer program product. .
The preceding description of the disclosed embodiment forms is provided to enable any person skilled in this art to make or use the present invention. Various modifications to these forms of
187
<img file="MX353239B_D0244.tif" />
<img file="MX353239B_D0245.tif" />
<img file="MX353239B_D0246.tif" />
MEXICAN INSTITUTE · <'
OF THE FI.CITY t'l _.
INDUSTRIAL modality will be readily apparent to those skilled in this art and the generic principles defined herein can be applied to other forms of modality without thereby departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the forms of embodiment described herein, but must be in accordance with the widest scope compatible with the provisions of the following claims and the principles and features of novelty herein given 10 know.
It is noted that in relation to this date, the best method known by the applicant to put the aforementioned invention into practice is the one that is clear from the present description of the invention.
<img file="MX353239B_D0247.tif" />
<img file="MX353239B_D0248.tif" />
188
<img file="MX353239B_D0249.tif" />
Contents73
290 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25 Sheet 26 Sheet 27 Sheet 28 Sheet 29 Sheet 30 Sheet 31 Sheet 32 Sheet 33 Sheet 34 Sheet 35 Sheet 36 Sheet 37 Sheet 38 Sheet 39 Sheet 40 Sheet 41 Sheet 42 Sheet 43 Sheet 44 Sheet 45 Sheet 46 Sheet 47 Sheet 48 Sheet 49 Sheet 50 Sheet 51 Sheet 52 Sheet 53 Sheet 54 Sheet 55 Sheet 56 Sheet 57 Sheet 58 Sheet 59 Sheet 60 Sheet 61 Sheet 62 Sheet 63 Sheet 64 Sheet 65 Sheet 66 Sheet 67 Sheet 68 Sheet 69 Sheet 70 Sheet 71 Sheet 72 Sheet 73 Sheet 74 Sheet 75 Sheet 76 Sheet 77 Sheet 78 Sheet 79 Sheet 80 Sheet 81 Sheet 82 Sheet 83 Sheet 84 Sheet 85 Sheet 86 Sheet 87 Sheet 88 Sheet 89 Sheet 90 Sheet 91 Sheet 92 Sheet 93 Sheet 94 Sheet 95 Sheet 96 Sheet 97 Sheet 98 Sheet 99 Sheet 100 Sheet 101 Sheet 102 Sheet 103 Sheet 104 Sheet 105 Sheet 106 Sheet 107 Sheet 108 Sheet 109 Sheet 110 Sheet 111 Sheet 112 Sheet 113 Sheet 114 Sheet 115 Sheet 116 Sheet 117 Sheet 118 Sheet 119 Sheet 120 Sheet 121 Sheet 122 Sheet 123 Sheet 124 Sheet 125 Sheet 126 Sheet 127 Sheet 128 Sheet 129 Sheet 130 Sheet 131 Sheet 132 Sheet 133 Sheet 134 Sheet 135 Sheet 136 Sheet 137 Sheet 138 Sheet 139 Sheet 140 Sheet 141 Sheet 142 Sheet 143 Sheet 144 Sheet 145 Sheet 146 Sheet 147 Sheet 148 Sheet 149 Sheet 150 Sheet 151 Sheet 152 Sheet 153 Sheet 154 Sheet 155 Sheet 156 Sheet 157 Sheet 158 Sheet 159 Sheet 160 Sheet 161 Sheet 162 Sheet 163 Sheet 164 Sheet 165 Sheet 166 Sheet 167 Sheet 168 Sheet 169 Sheet 170 Sheet 171 Sheet 172 Sheet 173 Sheet 174 Sheet 175 Sheet 176 Sheet 177 Sheet 178 Sheet 179 Sheet 180 Sheet 181 Sheet 182 Sheet 183 Sheet 184 Sheet 185 Sheet 186 Sheet 187 Sheet 188 Sheet 189 Sheet 190 Sheet 191 Sheet 192 Sheet 193 Sheet 194 Sheet 195 Sheet 196 Sheet 197 Sheet 198 Sheet 199 Sheet 200 Sheet 201 Sheet 202 Sheet 203 Sheet 204 Sheet 205 Sheet 206 Sheet 207 Sheet 208 Sheet 209 Sheet 210 Sheet 211 Sheet 212 Sheet 213 Sheet 214 Sheet 215 Sheet 216 Sheet 217 Sheet 218 Sheet 219 Sheet 220 Sheet 221 Sheet 222 Sheet 223 Sheet 224 Sheet 225 Sheet 226 Sheet 227 Sheet 228 Sheet 229 Sheet 230 Sheet 231 Sheet 232 Sheet 233 Sheet 234 Sheet 235 Sheet 236 Sheet 237 Sheet 238 Sheet 239 Sheet 240 Sheet 241 Sheet 242 Sheet 243 Sheet 244 Sheet 245 Sheet 246 Sheet 247 Sheet 248 Sheet 249 Sheet 250 Sheet 251 Sheet 252 Sheet 253 Sheet 254 Sheet 255 Sheet 256 Sheet 257 Sheet 258 Sheet 259 Sheet 260 Sheet 261 Sheet 262 Sheet 263 Sheet 264 Sheet 265 Sheet 266 Sheet 267 Sheet 268 Sheet 269 Sheet 270 Sheet 271 Sheet 272 Sheet 273 Sheet 274 Sheet 275 Sheet 276 Sheet 277 Sheet 278 Sheet 279 Sheet 280 Sheet 281 Sheet 282 Sheet 283 Sheet 284 Sheet 285 Sheet 286 Sheet 287 Sheet 288 Sheet 289 Sheet 290
19 members in 12 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 201361827937 | United States of America | P | |
| 201361827937 | United States of America | P | |
| 61827937 | United States of America | – | |
| 2014039546 | United States of America | W | |
| 2014039546 | United States of America | W | |
| 61827937 | – | – | – |
| PCTUS2014039546 | – | – | – |
| US201361827937P | – | – | – |
| WO2014US39546 | – | – | – |
Members19
| Document | Office | Kind | |
|---|---|---|---|
| CA2911512A1 | Canada | A1 | |
| US2014355428A1 | United States of America | A1 | |
| WO2014193820A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CN105247910A | China | A | |
| AU2014274379A1 | Australia | A1 | |
| MX2015016115A | Mexico | A | |
| MX2015016115A | Mexico | A | |
| EP3005773A1 | European Patent Office (EPO) | A1 | |
| EA201501152A1 | Eurasian Patent Organization (EAPO) | A1 | |
| KR20160068697A | Republic of Korea | A | |
| JP2016525818A | Japan | A | |
| HK1218212A | Hong Kong, China | A | |
| HK1218212A1 | Hong Kong, China | A1 | |
| US9648545B2 | United States of America | B2 | |
| AU2014274379B2 | Australia | B2 | |
| US2017207975A1 | United States of America | A1 | |
| BR112015029655A2 | Brazil | A2 | |
| EP3005773A4 | European Patent Office (EPO) | A4 | |
| MX353239BThis record | Mexico | B |
1 legal event, as the office reported them to INPADOC
Events
| Event | Code | |
|---|---|---|
| Grant or registrationFG | FG |
Numbers
- Publication
- 353239
- Publication, DOCDB
- 353239
- Publication, EPODOC
- MX353239
- Application
- 2015016115
- Application, DOCDB
- 2015016115
- Application, EPODOC
- MX20150016115
Titles2
- Spanish
- MÉTODOS Y SISTEMA PARA POLÍTICA DE ARBITRAJE DE ESPECTRO DINÁMICO ORIENTADA A LA CALIDAD DEL SERVICIO.
- English
- METHODS AND SYSTEM FOR DYNAMIC SPECTRUM ARBITRAGE POLICY DRIVEN QUALITY OF SERVICE.
Classification
- CPC, 13
- H04W28/0289
- H04W48/06
- H04W28/0247
- H04W88/18
- H04L47/122
- H04W16/14
- H04W36/22
- H04L41/0894
- H04W16/06
- H04W28/0231
- H04L65/401
- H04L41/0893
- H04W72/0453
- IPC, 3
- H04W16 06
- H04W88 18
- H04W4 24