Methods and systems of an all purpose broadband network

Method and system for universal broadband network

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application is a US patent application filed on June 12, 2013 with serial number no. 13/916,338, and a serial number filed on January 31, 2013 as no. 13 /755,808 US patent application and part of the US patent application serial number no. 13/860,711 filed on April 11, 2013. The above-mentioned US patent applications were filed on November 2, 2012. Part of the U.S. patent application with serial number no. 13/667, 424 is a continuation application, which requires the rights and interests of U.S. provisional patent application 61/659, 174 filed on June 13, 2012. All these applications are incorporated herein by reference in their entirety.

Technical field

[0002] The present disclosure relates to broadband networks, and more specifically, the present disclosure relates to methods and systems for increasing bandwidth in large-area broadband networks.

Background technique

[0003] Wireless networks are deployed ubiquitously on a global scale, and each new standardized air interface provides users with increasingly higher data rates. However, the popularity of data applications, and especially video applications, has become so great that the high data rates and increased capacity provided by 3G and 4G networks cannot even meet the current and expected demand for bandwidth. The combination of several factors makes it difficult to meet these user needs. One factor is the air interface itself. For example, new standards such as 3GPP (Third Generation Partnership Project) LTE (Long Term Evolution) provide the possibility to provide users with data rates of up to 10 Mbps, 20 Mbps or even higher. However, due to the general distribution of users in the coverage area of the transmitting cell, an average cell throughput of about 13 Mbps can be expected. This is not enough to provide video services to more than a small number of users. Therefore, it is necessary to improve the use of the LTE air interface. In addition, the inter-cell interference caused by the overlap of the RF signals between the transmission cells reduces the data rate and capacity that can be provided to users located at the boundary between the cells. Any method of reducing or eliminating such inter-cell interference will increase system capacity and throughput, and provide these users with improved quality of service. Another factor is the excessive use of backhaul facilities connecting LTE base stations (eNB) to the enhanced packet core (EPC) network. use. It may not be possible to deploy facilities operating at 1Gbps to reach all base stations, so a moderate amount of video applications can easily use so much backhaul bandwidth that it cannot provide other services to the remaining users. Another factor is the way in which servers are deployed to bring services to wireless users. These servers are external to the wireless network and may be located far away from the user's access point in the wireless network. The long packet transmission delay (delay) between the service program running on the server and the user's access point in the wireless network can lead to a poor user experience using the service.

[0004] The US government needs to take advantage of a large number of new user equipment being manufactured in order to operate on new wireless networks such as LTE. The use of proprietary systems for their wireless communication needs is becoming increasingly unattractive for the government. The cost involved in acquiring new spectrum and the overlap of the needs of US government users and general users suggest that the standard LTE network is used by both types of users at the same time. In this shared system, in an emergency, it is necessary to enable the government to implement priority access to the network or part of the network for authorized government use, and when the capacity is exhausted, it is necessary to exclude the use for non-governmental purposes. This behavior may not reach the level of availability required by the government in today's wireless networks. In addition, government and commercial applications are increasingly using all types of sensors to collect information. With efficient and fast acquisition, processing,

Wireless networks with the ability to store and redistribute sensor data are not available. In addition, during military operations, or during emergencies, self-organizing deployment of LTE wireless networks may be the best way to provide wireless services to emergency rescuers, to the US military, or to the general public. The self-organizing network can use airborne base stations deployed above the disaster area or operation area. In the case of airborne ad hoc network deployment (or other deployments involving mobile base stations), when airborne or mobile base stations need to withdraw from service due to low fuel or power, or the loss of airborne or mobile vehicles, the network must Keep running.

Summary of the invention

[0005] Beamforming technology has been used in the fields of audio signal processing, sonar signal processing, and radio frequency signal processing for many years in order to improve system operation. In many cases, these systems locate the transmitting or receiving point, and then focus the system antenna to create a beam aimed at that point. Among the teachings given herein are those that disclose systems that operate in different ways, and they take advantage of the fact that in a cellular LTE system, user equipment is scheduled to receive transmissions or generate transmissions. This system does not focus the antenna beam on a specific user, but: for a frequency division duplex (FDD) system, N non-overlapping fixed position RFs are generated in each of m 1 millisecond intervals Different beam patterns; for a time division duplex (TDD) system, one pattern of m different patterns of N fixed position RF beams is generated in each 1ms non-S subframe of each LTE frame . Each RF beam covers a sub-area of the total cell coverage area. The area of the cell is covered by the total set of m times N RF beam patterns. In the FDD system, the RF beam pattern repeats after m milliseconds; in the TDD system, the beam pattern repeats after 10 milliseconds. Therefore, the RF beam pattern appears to rotate periodically over the cell coverage area. Only when the beam is focused on the beam sub-region that includes the user's location, the user is scheduled for transmission or reception. Such systems are referred to as "agile beamforming systems", "agile beam systems" and "weekly beamforming systems" in this article. Term beamforming system" and includes cellular LTE base station transceivers operating in frequency division duplex mode or time division duplex mode.

[0006] In a cellular LTE system, downlink transmission can be scheduled by software called a scheduler in a base station. The scheduler can also grant grants for uplink transmissions from the UE. In this way, the bandwidth available via the LTE air interface is allocated to different users at different times in a manner determined by the scheduler. Therefore, when using agile RF beamforming technology, it is important for the scheduler to know the current location of each UE with the accuracy of the RF beam sub-region. Therefore, in a specific 1 millisecond interval, it can only be given to the current position of each UE. In a millisecond interval, those UEs in one of the N RF beam sub-regions focused by the RF beamforming subsystem are authorized for uplink transmission. Likewise, the scheduler may need to schedule downlink transmissions only to those UEs known to be located in one of the N RF beam subareas to be irradiated by the RF beamforming subsystem operation.

[0007] Two aspects of determining the positioning of the UE within the RF beam sub-area are: when the UE accesses the cell for the first time (ie, after the random access procedure, or after the handover procedure, or after the service request procedure ) Determine the position of the RF beam; then, when the UE moves around in the cell coverage area, track the UE across the RF beam sub-area. Two methods can be used to develop algorithms for determining the location of the UE within the RF beam and for tracking the UE across the RF beam, namely, channel quality indicator (CQI) measurement and sounding reference signal (SRS) measurement. The CQI measurement result can be returned by the UE after it measures the channel quality signal sent by the cellular radio RF base station. The SRS signal can be sent by the UE and detected by the cellular radio RF base station. Therefore, CQI can be used to determine downlink channel quality, and SRS can be used to determine uplink channel quality.

[0008] In the LTE TDD system, the same frequency band is used for both uplink and downlink transmission. Therefore, it can be expected to use uplink measurement of RF channel conditions in each RF beam or use downlink The measurement results in the same determination of the beam that best covers the current UE position. The LTE FDD system uses different

Therefore, in an RF environment where multipath reflections are ubiquitous, it can be expected that the measurement of the downlink channel and the measurement of the uplink channel can lead to different determinations of the RF beam that best covers the current UE location. Therefore, both the CQI-based algorithm and the SRS-based algorithm can be used to determine the RF beam used for downlink transmission to the UE and the RF beam used for uplink transmission from the UE.

[0009] The present disclosure relates to a system for supporting cellular mobile transceiver device communication. The system includes: multiple cellular LTE base station transceivers, each cellular LTE base station transceiver and multiple mobile transceiver devices in an RF coverage area Perform RF communication; the cellular LTE base station transceiver includes: an agile beamforming antenna system suitable for providing full coverage of the cell coverage area by generating m different sets of fixed position patterns of N RF beams ; Each RF beam is dimensioned so as to cover a sub-area of the cell coverage area, wherein the cell coverage area is covered by the number m multiplied by the number N RF beam patterns. The cellular LTE base station transceiver is adapted to provide at least one of the following: RF frequency division duplex (FDD) communication with the plurality of mobile transceiver devices, wherein 1 Wm W 4; and RF Time Division Duplex (FDD) communication of multiple mobile transceiver devices, where 1 Wm W 3; and m is determined based at least in part on the selected LTE TDD ± uplink/downlink (U/D) configuration And the selected RF beam configuration, which is constrained so that whenever the RF beam is focused on the cell coverage of the first cellular LTE base transceiver station adjacent to the cell coverage area of the second cellular LTE base transceiver station When the area is a sub-area, the second cell The RF beam pattern in the coverage area of the adjacent cell of the LTE base station transceiver is such that its RF beam sub-area does not correspond to the RF beam sub-area in the cell coverage area of the first cellular LTE base station transceiver. The area is adjacent.

[0010] The system may further include: the difference between the number m of fixed position patterns suitable for transmitting signals through cell-wide RF, cell-wide RF receiving signals plus a number of N RF transmitting beams and a number of N RF receiving beams A digital baseband processing and RF facility, a backhaul network, and a base station optimization server assembled to communicate with the plurality of mobile transceiver devices. The base station optimization server is connected to the cellular LTE base station transceiver and the backhaul network parallel to the cellular LTE base station transceiver, and may include at least one of the following: suitable for moving to the plurality of The transceiver device publishes its streaming or other application data publish-subscribe agent communication facilities for the application, as well as services and services to each of the plurality of mobile transceiver devices in the RF coverage area Data usage is collected and reported by the base station optimization server usage data reporting facility.

[0011] The system may further include: an area optimization server communicatively connected with the PGW on the public data network side of the public data network gateway (PGW), and the area optimization server is suitable for: (a) running for At least one mobile transceiver device provides an application for the service, and (b) transmitting the function of the application of the at least one mobile transceiver device to the base station optimization server based on the usage characteristics of the at least one mobile transceiver device.

[0012] The system may further include: a wireless control facility communicatively connected with the area optimization server and at least one of the plurality of cellular LTE base station transceivers through the backhaul network, and transmitting and receiving with the cellular LTE base station A processor-based scheduler facility connected to the machine. The scheduler facility can schedule communications between the cellular LTE base station transceiver and the plurality of mobile transceiver devices, wherein the scheduler facility is based on the use of the cellular LTE base station transceiver and all mobile transceiver devices. The location of the target mobile transceiver device in the coverage area of the cell determined by the location determination algorithm of at least one of channel quality indicator measurement and sounding reference signal measurement collected by the communication interaction between the target mobile transceiver devices The communication with the target mobile transceiver device is scheduled to occur in one of m multiplied by N RF beams, and each mobile transceiver devices access to the LTE air interface is based on the current pass and all The data rate priority value assigned by each of the plurality of mobile transceiver devices of the cellular LTE base station transceiver associated with the scheduler to access the LTE network.

[0013] The system may include: a plurality of sensors deployed in the coverage area of at least one of the plurality of cellular LTE base station transceivers, and the sensors are provided by the base station optimization server Collect, process, store and distribute data through the publish-subscribe agent communication facility.

[0014] The access priority facility may determine the wireless system access level of each mobile transceiver in the plurality of mobile transceiver devices, and the wireless system access level determination is given to the user for the When the access of the cellular LTE base station transceiver is restricted, the priority of accessing the cellular LTE base station transceiver is extended, and the priority level is extended beyond those given in the standard.

[0015] The base station transceiver replacement facility can manage the switching of multiple mobile transceiver devices in the RF coverage area from the replaced base station transceiver to the replacement base station transceiver.

[0016] The system may include a hot standby facility, wherein the hot standby facility uses a publish-subscribe agent communication facility to maintain the same application state information as maintained in the active computing facility that is on standby.

[0017] In another aspect, the present disclosure relates to a system including a first cellular wireless RF base station node for RF communication with a mobile device, the first cellular wireless RF base station node being connected to a backhaul network and having an RF coverage area; And at least one first base station optimization server, which is connected to the first cellular wireless RF base station and to the backhaul network parallel to the first cellular wireless RF base station node, so as to allow data packets between the following Selectively flow (a) between the first cellular wireless RF base station node and the backhaul network, (b) between the at least one first base station optimization server and the backhaul network, or (c) Between the first cellular wireless RF base station node and the at least one first base station optimization server. The system further includes: a second cellular wireless RF base station node connected to the backhaul network and having an RF coverage area; and at least one second base station optimization server connected to the second cellular A wireless RF base station and the backhaul network connected in parallel with the second cellular wireless RF base station node so as to allow data packets to selectively flow between (a) at the second cellular wireless RF base station node And the backhaul network, (b) between the at least one second base station optimization server and the backhaul network, or (c) between the first cellular wireless RF base station node and the at least one first Base station is excellent The system also includes: a regional optimization server, which is communicatively connected with the public data network gateway (PGW) on the public data network side of the public data network gateway (PGW), and is suitable for (a) operation for An application that provides services to the mobile device, and (b) based on the usage characteristics of the mobile device, transfer all the resources for the mobile device to the at least one base station optimization server of the first cellular radio RF base station node The function of the application; and a wireless control facility, which is communicatively connected to at least one of the area optimization server and the first and second cellular wireless RF base station nodes; the first and second cellular base station nodes The corresponding RF coverage areas overlap, and the wireless control facility is adapted to manage the following items during the handover of the mobile device from the first cellular wireless RF base station node to the second cellular wireless RF base station node (a) The connection of the application with the mobile device, and (b) the function of the application transferred to the at least one base station optimization server of the second cellular wireless RF base station node.

[0018] In another aspect, the present disclosure relates to a system for supporting communication with a cellular mobile transceiver device, the system comprising: a cellular LTE base station transceiver, which is suitable for cell coverage with the cellular LTE base station transceiver RF frequency division duplex (FDD) communication of multiple mobile transceiver devices in the area, the cellular LTE wireless base station transceiver includes: m different sets of fixed position patterns suitable for generating N RF beams To provide an agile beamforming antenna system for full coverage of the cell coverage area; each RF beam is sized to cover a sub-area of the cell coverage area, where the cell coverage area is multiplied by the number m. The number of N RF beam patterns covered. Wherein, 1 W m W 4, and the antenna system is suitable for generating N in different 1 millisecond subframes of the LTE frame

Each of the m sets of RF beam patterns, such that the m sets of N RF beams are generated in a sequence spanning four consecutive 1 millisecond subframes.

[0019] In yet another aspect, the present disclosure relates to a system for supporting cellular mobile transceiver device communication, the system includes: a cellular LTE base station transceiver, which is suitable for cell coverage with the cellular LTE base station transceiver RF Time Division Duplex (TDD) communication of multiple mobile transceiver devices in the area, the cellular LTE wireless base station transceiver includes: m different sets of fixed position patterns suitable for generating N RF beams Beamforming antenna system; each RF beam is dimensioned to cover a sub-area of the cell coverage area, wherein the cell coverage area is covered by the number m times the number N RF beam patterns, so that N Each of the m sets of RF beam patterns is generated in one or more of the subframes of the LTE TDD frame, and thus the m sets of N RF beams are Generated in a sequence of LTE TDD subframes, where 1 W m W 3, and m is determined based at least in part on the selected LTE TDD uplink/downlink (U/D) configuration.

[0020] In another aspect, the present disclosure relates to a system for scheduling communications with a cellular mobile transceiver device, the system comprising: a cellular LTE base station transceiver, which is suitable for cell coverage with the cellular LTE base station transceiver Communication of multiple mobile transceiver devices in the area, the cellular LTE base station transceiver includes: agile beamforming antenna systems with m different sets of fixed position patterns that generate a number of N RF beams, each RF beam covering A sub-area of the cell coverage area, where m times N RF beam patterns cover the area of the cell coverage area. The system further includes: a processor-based scheduler facility communicatively connected to the cellular LTE base station transceiver, wherein the scheduler facility provides a way for the cellular LTE base station transceiver and the plurality of mobile transceiver equipment. Communication between the cellular LTE base station transceiver and the target mobile transceiver device by using the channel quality indicator (CQI) measurement and sounding reference collected through the communication interaction between the cellular LTE base station transceiver and the target mobile transceiver device. The location of the target mobile transceiver device in the cell coverage area determined by the location determination algorithm of at least one of the signal (SRS) measurements. Occurs in one of the RF beams.

[0021] In another aspect, the present disclosure relates to a system for baseband data transmission and reception in cellular mobile transceiver device communications. The system includes a cellular LTE base station transceiver, which is suitable for communication with multiple mobile transceiver devices in a cell coverage area of the cellular LTE base station transceiver. The cellular LTE wireless base station transceiver includes: Digital baseband processing facilities, digital interfaces, RF facilities, and agile beamforming antenna systems. The cellular LTE base station transceiver transmits a signal through a cell-wide RF transmission signal, a cell-wide RF reception signal, an additional number N of RF transmission beams and a number of N RF reception beams. The number of fixed position patterns of m is different sets In communication with the mobile transceiver device, each of the N RF transmission and N RF reception beams covers a sub-area of the coverage area of the cell range, where m is multiplied by the coverage of the N RF beam patterns. The area covered by the cell range. The digital baseband processing facility provides N transmission beam digital data streams and cell-wide transmission digital data streams to the RF facility through the digital interface for transmission through the agile beamforming antenna system; and the RF facility passes The digital interface provides the digital baseband processing facility with N receive beam digital data streams and cell-wide receive digital data streams from the agile beamforming antenna system. The digital baseband processing facility pairs the N transmission beam digital data streams and the cell range transmission digital data for transmitting in at least one of m multiplied by N RF beams and the cell range RF transmission signal The transmission of at least one of the streams to the mobile transceiver device is processed, and the N obtained from at least one of m multiplied by N RF reception beams and the cell-wide RF reception signal is processed. At least one of the received beam digital data stream and the cell-wide received digital data stream is from the mobile receiver

The receiver of the sender device is processed.

[0022] In another aspect, the present disclosure relates to a system for reducing inter-cell interference in a cellular mobile communication network. The system includes: a first cellular LTE base station transceiver, which is suitable for communication with multiple mobile transceiver devices in each cell coverage area of the first cellular LTE base station transceiver, and the first cellular LTE wireless The base station transceiver includes: a plurality of cells and an agile beamforming antenna system with different sets of fixed position patterns generating N1 RF beams in each cell; each RF beam covers the first cellular LTE base station The sub-area of the cell coverage area of the transceiver, wherein the ml in each cell multiplied by N1 RF beam patterns covers the area of the cell coverage area of the first cellular LTE base station transceiver. The first cellular LTE base station transceiver irradiates the N1 RF beams in each cell, so that the irradiated RF beam sub-regions are not adjacent to each other. The system includes: a second cellular LTE base station transceiver, which is suitable for communication with multiple mobile transceiver devices in each cell coverage area of the second cellular LTE base station transceiver, and the second cellular LTE wireless The base station transceiver includes: a plurality of cells and the number of fixed position patterns m2 that generate N2 RF beams in each cell The same set of agile beamforming antenna systems; each RF beam covers a sub-area of the cell coverage area of the second cellular LTE base station transceiver, where m2 in each cell is multiplied by N2 RF beam pattern coverage The area of the coverage area of each cell of the first cellular LTE base station transceiver. The second cellular LTE base station transceiver irradiates the N2 RF beams in each cell, so that the irradiated RF beam sub-areas are not adjacent to each other. Whenever the first cellular LTE base station transceiver irradiates RF on a sub-area of its cell coverage area adjacent to the cell coverage area of another cell of the first cellular LTE base station transceiver Beams, the RF beam patterns generated by the first cellular LTE base station transceiver in these cells are such that the irradiated RF beam sub-regions are not adjacent to each other. Whenever the second cellular LTE base station transceiver irradiates RF on a sub-area of its cell coverage area adjacent to the cell coverage area of another of the cells of the second cellular LTE base station transceiver Beams, the RF beam pattern generated by the second cellular LTE base station transceiver in these cells makes the irradiated RF beam sub-regions not adjacent to each other; and whenever the first cellular LTE base station transceiver The device irradiates an RF beam on a sub-area of its cell coverage area adjacent to the cell coverage area of the first cellular LTE base station transceiver, and The RF beam pattern generated by the second cellular LTE base station transceiver is such that the irradiated RF beam sub-area is not identical to all that is being irradiated in the cell coverage area of the first cellular LTE base station transceiver. The RF beam sub-regions are adjacent.

[0023] In another aspect, the disclosure relates to a system including a cellular LTE base station transceiver in RF communication with first and second mobile transceiver devices, the cellular LTE base station transceiver being connected to a backhaul network And has RF coverage area. A base station optimization server is connected to the cellular LTE base station transceiver and to the backhaul network parallel to the cellular LTE base station transceiver to allow data packets to selectively flow between any of the following ( a) the cellular LTE base station transceiver and the backhaul network, (b) the base station optimization server and the backhaul network, or (c) the cellular LTE base station transceiver and the base station optimization server. The base station optimization server is communicatively connected to the first and second mobile transceiver devices via an LTE bearer redirected by the cellular LTE base station transceiver of each mobile transceiver device. The system also includes a publish-subscribe proxy communication facility to which the first and second mobile transceiver devices are connected via their redirected bearers, and wherein the publish-subscribe proxy communication facility is adapted to represent The packet stream of the application publishing its streaming application data is routed to the first and the second mobile transceiver device, wherein both the first and the second mobile transceiver device subscribe to the application data And receive at least the common part of the stream of application data from the publish-subscribe agent communication facility.

[0024] In another aspect, the disclosure relates to a system including a cellular LTE base station transceiver in RF communication with first and second mobile transceiver devices. The cellular LTE base station transceiver is connected to the backhaul network and has an RF coverage area. A base station optimization server is connected to the cellular LTE base station transceiver and to the backhaul network parallel to the cellular LTE base station transceiver, so as to allow data packets to selectively flow between at least one of the following ( a) the cellular LTE base station transceiver and the backhaul network, (b) the base station optimization server and the backhaul network, or (c) the cellular LTE base station transceiver and the base station optimization server. The base station optimization server is communicatively connected to the first and second mobile transceiver devices via an LTE bearer redirected by the cellular LTE base station transceivers of the first and second mobile transceiver devices. The publish-subscribe proxy communication facility to which the first and second mobile transceiver devices are connected via their redirected bearers is adapted to: from the publish-subscribe, a packet stream representing an application publishing its streaming application data The subscription agent communication facility is routed to the first and the second mobile transceiver device, wherein both the first and the second mobile transceiver device subscribe to and request the application data stream at the moment of request, so The request moment is different for the first and second mobile transceiver devices.

[0025] In another aspect, the present disclosure relates to a system including a cellular LTE base station transceiver for RF communication with a sensor device. The cellular LTE base station transceiver is connected to the backhaul network and has an RF coverage area. The base station optimization server is connected to the cellular LTE base station transceiver and the backhaul network parallel to the cellular LTE base station transceiver, and is connected to the cellular LTE base station transceiver for the sensor device via redirected LTE bearer communication The sensor device. The system further includes: a first publish-subscribe proxy communication facility to which the sensor device is connected via its redirected bearer, and the first publish-subscribe proxy communication facility is adapted to: The application data of multiple applications whose data is transmitted is routed; and the application data of each published application is routed to all communication entities that subscribe to receive the data published by the application. The area optimization server is communicatively connected with the PGW on the public data network side of the public data network gateway (PGW), and the area optimization server is adapted to run a server for providing services to the plurality of mobile transceiver devices and sensors application. The regional optimization server includes a first publish-subscribe agent communication facility, and is adapted to route data published by an application to the first publish-subscribe agent communication facility and to a plurality of supporting agents that have subscribed to receive the data. All other publish-subscribe agent communication facilities in the agent network of at least one of the communication endpoints. The sensor device is deployed in the coverage area of the cellular LTE base station transceiver, and is provided for operation on at least one of the optimization servers that are adapted to run on the base station optimization server and communicatively connected to the PGW The data subscribed to by the app. One of these applications is a conference service, and the conference service and other applications pass through the publish-subscribe agent communication facility adapted to run on the base station optimization server and pass through the communication facility adapted to host the application. At least one of the publish-subscribe agent communication facilities running on the optimized server node collects, processes, stores, and distributes the sensor data.

[0026] In another aspect, the present disclosure relates to a system for supporting cellular mobile transceiver device communication. The system includes: multiple cellular LTE base station transceivers, each cellular LTE base station transceiver performs RF communication with multiple mobile transceiver devices in an RF coverage area, and accesses priority facilities. The access priority facility determines the wireless system access priority level of each mobile transceiver in the plurality of mobile transceiver devices. During the period of limited network access at the cellular LTE base station transceiver, the wireless The system access level determines whether the mobile transceiver device, which is one of the mobile transceiver devices attempting to access the cellular LTE base station and maintaining access through the cellular LTE base station, has more than the limit for this access restriction. The access priority level of the value provided by the cellular LTE base station cell. The available priority level exceeds the restricted set of values specified in the LTE standard document, and the access priority level is lower than the provided threshold.

The mobile transceiver equipment is separated from the wireless network at the restricted cellular LTE radio base station.

[0027] In another aspect, the present disclosure relates to a system for supporting cellular mobile transceiver device communication, the system comprising: a cellular LTE base station transceiver for RF communication with multiple mobile transceiver devices in an RF coverage area And a processor-based scheduler facility communicatively connected with the cellular LTE base station transceiver. The scheduler facility schedules the access of the mobile transceiver device to the LTE air interface based on the data rate priority value assigned to each mobile transceiver device, and this air interface access priority includes: Other mobile transceiver devices with a lower data rate priority value previously authorized access to the air interface and allocating air interface resources in order to reach and provide data to other mobile transceiver devices with a lower data rate priority value The rate is higher than the data rate. The data rate priority value of each mobile transceiver device that accesses the LTE network through the cellular LTE base station transceiver is set via the cellular LTE base station transceiver and the mobile transceiver device that can access the mobile transceiver device. The data rate priority value is completed by the interaction between the applications of the database.

[0028] In another aspect, the present disclosure relates to a system for reporting cellular mobile transceiver device communications. The system includes: a cellular LTE base station transceiver that performs RF communication with multiple mobile transceiver devices in an RF coverage area; and a base station optimization server. The base station optimization server is communicatively connected to the cellular LTE base station transceiver and a backhaul network parallel to the cellular LTE base station transceiver. The base station optimization server is communicatively connected to the plurality of mobile transceiver devices via an LTE bearer redirected by the cellular LTE base station transceiver of each mobile transceiver device. The system includes a publish-subscribe proxy communication facility to which the plurality of mobile transceiver devices are connected via its redirected bearer, and includes a base station optimization server usage data reporting facility for reporting to the bearer having redirected The service and data usage of each of the plurality of mobile transceiver devices in the RF coverage area are collected. The publish-subscribe agent communication facility is adapted to report the billing usage data of each mobile transceiver device connected to the publish-subscribe agent communication facility, so that the usage data reporting facility can be targeted by the mobile transceiver The device collects billing usage data for all data sent on the path that does not include the PGW unit, where such data is through the redirected bearer included in the cellular LTE base station transceiver The paths are collected in the LTE network.

[0029] In another aspect, the present disclosure relates to a system for implementing a replacement process in which a base station deployed via a mobile platform in an ad hoc LTE system is replaced by another base station deployed via the mobile platform. The system includes: a cellular LTE base station transceiver that provides RF communication with multiple mobile transceiver devices in an RF coverage area, wherein the cellular LTE base station is deployed in an ad hoc manner using a mobile deployment platform. The replacement cellular LTE base station transceiver is suitable for RF communication with the plurality of mobile transceiver devices, and the replacement cellular LTE base station transceiver is also deployed in a self-organizing manner using a mobile deployment platform, and is arranged so as to be able to cover with the RF The plurality of mobile transceiver devices in the area communicate. The base station transceiver is communicatively connected to the backhaul network and to the cellular LTE base station transceiver in the alternative computing facility, and is connected to the alternative cellular LTE base station transceiver, and the base station transceiver replaces the computing facility to manage the RF Handover of the plurality of mobile transceiver devices in the coverage area from the cellular LTE base station transceiver to the replacement cellular LTE base station transceiver. The handover process includes: a) the replacement cellular LTE base station transceiver is connected to the backhaul network, b) the replacement cellular LTE base station transceiver is communicatively connected to the base station transceiver replacement computing facility, c) the The base transceiver station replaces the computing facility provided with the cell identifier in addition to the cell identifier. The replacement cellular LTE base station transceiver with the same parameters as the LTE base station transceiver, d) the cellular LTE base station transceiver reduces its transmission power at the rate Pr, and the replacement cellular LTE base transceiver station increases its transmission power at the rate Pr . The rate Pr is selected from two typical fixed LTE base stations separated by a 2 cell radius to simulate the transceiver in the RF coverage.

The power received at a typical mobile transceiver device in the cover area. The simulation is a simulation of the movement of the typical mobile transceiver device away from the cellular LTE base station transceiver and towards the replacement cellular LTE base station transceiver, and the simulated movement rate of the mobile transceiver device is between 3 and 30 km /hr between. When the power level and RF propagation characteristics determine the handover based on a predetermined algorithm, each mobile transceiver device of the plurality of mobile transceiver devices moves from the cellular LTE base station transceiver to the replacement cellular LTE base station transceiver Handover, wherein when all the mobile transceiver devices in the plurality of mobile transceiver devices switch to the replacement cellular LTE base station transceiver, the replacement of the cellular LTE base station transceiver is completed.

[0030] In another aspect, the present disclosure relates to a system including multiple cellular LTE base station transceivers, each cellular LTE base station transceiver performing RF communication with multiple mobile transceiver devices in an RF coverage area, the cellular The LTE base station transceiver includes a base station optimization server and a publish-subscribe agent communication facility, wherein the multiple base station optimization server networks are connected together to partially form a distributed publish-subscribe agent network architecture. The system includes: a pair of identical service application instances, one designated as an active service instance, and one designated as a hot standby service instance, wherein the active service instance is hosted on an optimized server, and the hot standby service The instances are hosted on different optimized servers. The active service instance uses the distributed publish-subscribe agent network architecture to provide its services to the plurality of mobile transceiver devices, and the hot standby service instance uses the distributed publish-subscribe agent network architecture through The active service instance or each active service instance in the some active service instances subscribes to the same communication to maintain the same application state information like the active service instance or the some active service instances.

[0031] These and other systems, methods, objectives, features, and advantages of the present disclosure will become apparent to those skilled in the art through the following detailed description of the preferred embodiments and the accompanying drawings. The complete contents of all documents mentioned in this article are incorporated into this article by reference.

Description of the drawings

[0032] The present disclosure and the following detailed description of certain embodiments thereof can be understood by referring to the following drawings: FIG. 1 depicts an embodiment of a typical deployment of an LTE network element.

[0033] FIG. 2 depicts the addition of an optimization server to the LTE network.

[0034] FIG. 3 depicts the redirection of UE bearers at the eNB.

[0035] FIG. 4 depicts the redirection of dedicated bearers at the eNB.

[0036] FIG. 5 depicts a high-level view of the LTE handover process.

[0037] FIG. 6 depicts the changes of the integrated optimization server during the LTE handover process.

[0038] FIG. 7 depicts an embodiment of airborne eNB deployment.

[0039] FIG. 8 depicts the replacement of an onboard eNB without losing service to the UE.

[0040] FIG. 9 depicts an example embodiment of scanning a cell coverage area with 16 RF beams every 4 milliseconds.

[0041] FIG. 10 depicts an embodiment of an LTE TDD uplink/downlink configuration.

[0042] FIG. 11 depicts an example embodiment showing 4 millisecond beam rotation for supporting H-ARQ operation in an FDD system.

[0043] FIG. 12 depicts an example embodiment of delivering a real-time event service to six wireless users.

[0044] FIG. 13 shows an embodiment of a publish-subscribe proxy architecture.

[0045] FIG. 14 depicts an example embodiment of the deployment of the P/S proxy in the APN optimized server architecture.

[0046] FIG. 15 depicts a real-time event service using P/S proxy architecture and APN bearer redirection.

[0047] FIG. 16 depicts a keep-alive message interaction for monitoring the status of a service instance.

[0048] FIG. 17 depicts an embodiment deployment of a streaming movie delivery service on an APN optimization server.

[0049] FIG. 18 depicts an example embodiment for finding the nearest SMD service instance and transmitting a movie stream to the UE.

[0050] FIG. 19 depicts an example embodiment for streaming movie delivery when downloads from central storage are required.

[0051] FIG. 20 depicts an example embodiment for separating a roaming UE when the cell is restricted for government use.

[0052] FIG. 21 depicts units and interfaces for implementing dual-use capabilities in an LTE network.

[0053] FIG. 22 depicts an embodiment of a UE application for biometric testing.

[0054] FIG. 23 depicts the initial phase of the UE's automatic separation from the cell where the CB for GU is enabled: separation of the roamer.

[0055] FIG. 24 depicts an example embodiment for automatically separating low priority UEs from blocked cells.

[0056] FIG. 25 depicts an example embodiment including biometric testing when cell lockout is enabled for the first time.

[0057] FIG. 26 depicts an example embodiment of initial attach processing when the UE accesses a cell where CB for GU may be enabled.

[0058] FIG. 27 shows a modified embodiment of a network-triggered service request in a dual-use network.

[0059] FIG. 28 depicts an example embodiment of processing in an LTE service request process added to a dual-use network.

[0060] FIG. 29 depicts an example embodiment of an X2 handover process added to a dual-use network.

[0061] FIG. 30 depicts an example embodiment of an S1 handover process added to a dual-use network.

[0062] FIG. 31 depicts an example deployment of the conference function on the optimization server in the APN LTE wireless network.

[0063] FIG. 32 depicts an embodiment of self-organizing network deployment for emergency action scenarios.

[0064] FIG. 33 depicts a functional view of an embodiment of an emergency action service architecture involving sensor processing.

[0065] FIG. 34 depicts an embodiment deployment view of an emergency action service architecture involving sensor processing.

[0066] FIG. 35 depicts an embodiment of initiating an emergency action multimedia conference.

[0067] FIG. 36 depicts an embodiment in which a participant joins a conference and joins its session.

[0068] FIG. 37 depicts fixed sensor data collection, analysis, and alarm generation and distribution.

[0069] FIG. 38 depicts an embodiment for finding an image server instance, initiating and using an image service in an emergency action scene.

[0070] FIG. 39 depicts an embodiment of obtaining a UE data rate priority value and using the value to update the eNB for the initial access situation.

[0071] FIG. 40 depicts an embodiment of obtaining a UE data rate priority value and using the value to update the eNB for service request situations.

[0072] FIG. 41 depicts an embodiment of obtaining a UE data rate priority value and using the value to update the target eNB for a handover situation.

[0073] FIG. 42 depicts an embodiment of updating the UE data rate priority value when the data rate priority service is enabled at the serving cell.

[0074] FIG. 43 depicts an embodiment of updating the UE data rate priority value when the data rate priority service is disabled at the serving cell.

[0075] FIG. 44 depicts an embodiment of an architecture for collecting, transmitting, and further processing charging data that may be collected on the APN optimization server.

[0076] FIG. 45 depicts an embodiment of a message exchange that enables a program to collect and report used charging data via a redirected bearer.

[0077] FIG. 46 depicts an embodiment of the message exchange that enables the charging data collection program to learn when to stop its collection action when the UE enters the ECM-IDLE state.

[0078] FIG. 47 depicts an embodiment of the message exchange that enables the charging data collection program to learn when to stop its collection action when the UE becomes detached from the LTE network.

[0079] FIG. 48 depicts two adjacent cells, and shows the overlap of the RF transmission of each cell with the coverage area of another cell, thereby demonstrating the concept of inter-cell interference.

[0080] FIG. 49 depicts a hexagonal representation of a cell, where the cell coverage area is divided into four sets of four sub-regions (ie, a total of 16 sub-regions), and wherein each sub-region is used by the cell antenna system RF beam coverage generated by agile beamforming technology.

[0081] FIG. 50 depicts three cells of an example base station system using agile beamforming, and shows how the RF beam rotation pattern in each cell can be constructed to avoid inter-cell interference at any cell boundary.

[0082] FIG. 51 depicts all cells that may be adjacent to a given cell, and shows how the RF beam rotation pattern in each cell can be constructed to avoid inter-cell interference at any cell boundary.

[0083] FIG. 52 depicts all cells in four base station systems using agile beamforming, and shows how the RF beam rotation pattern in each cell can be constructed to avoid inter-cell interference at any cell boundary, thereby It shows that inter-cell interference avoidance can be extended to all cells in the wireless network.

[0084] FIG. 53 depicts the baseband subsystem and the RF and antenna subsystems of an LTE wireless base station that generates periodic scanning RF beams, emphasizing the interface between these two subsystems and the MAC layer software and the PHY layer software that perform baseband signal processing.

[0085] Although the method and system are described in conjunction with certain preferred embodiments, other embodiments will also be understood by those of ordinary skill in the art and included herein.

Detailed ways

[0086] The following is a written description of the present disclosure and the manner and process of making and using the present disclosure, using sufficient, clear, concise and precise terminology to enable those skilled in the relevant field or the field most closely related to it The same can be made and used, and the best way to implement the present disclosure conceived by the inventor of the present disclosure is explained.

[0087] The present disclosure relates to broadband wireless networks, and more specifically, the present disclosure relates to multi-purpose networks, or referred to as "universal networks" or "APNs" in this disclosure, which can achieve large-scale (for example, Nationwide) broadband wireless network in order to provide extremely high wireless data capacity, and can solve all the above problems. APN can combine mature and cutting-edge commercial wireless design architecture methods with advanced RF technology to greatly improve spectrum efficiency, spectrum utilization and data performance. Unique beamforming techniques can be used to improve spectrum efficiency and spectrum utilization, and part of the methods and systems disclosed herein as part of the APN network can involve scheduling the RF beam period in a manner suitable for the LTE network. In addition, efficient algorithms for locating and tracking users in the beam may be part of the present disclosure. In addition, it should be noted that the interference provided to users in one cell by transmissions originating from neighboring cells generally reduces the quality of service provided to users located near the border between these two neighboring cells. A part of this disclosure describes that the use of agile beamforming system in each cell in the APN network can be used without resorting to special communication between cells, and without reducing the use by users located in any part of the cell coverage area. Of available bandwidth

How to greatly eliminate inter-cell interference under the circumstances. Involved in service traffic delay, the backhaul, and the above problems and long backhaul network server may be used in the APN network via the wireless server deployed as close as possible to resolve the user, i.e., via the eNB (E-UTRAN Node B or Evolved Type Node B) deployment associated with network elements, such as by providing a server with a high-speed connection to the eNB, placing the server near the eNB, co-locating the server with the eNB, and so on. This deployment may require the integration of servers into LTE wireless network operations in the unique manner disclosed herein. When the user is allowed to access the server associated with the eNB unit, the users bearer packet no longer flows through the Serving Gateway (SGW) and Public Data Network (PDN) Gateway (PGW) units. Therefore, part of the present disclosure shows How to retain the collection of billing data in these situations. As disclosed in this disclosure, when integrated into an APN wireless network, these servers can also form the basis of a platform for collecting, processing, storing, and redistributing sensor data. In addition, as disclosed in this disclosure, the introduction of publish/subscribe data communication into the APN network makes it possible to implement the APN network as a dual-use network, where only government users can be allowed to access the network during disasters or other emergencies. Some parts of it. This disclosure can also The use of the publish/subscribe communication infrastructure involving the APN network to implement hot standby services can play an important role in improving network operations and enhancing user experience. The present disclosure also solves the problem of how to replace an airborne or other mobile eNB base station while the mobile base station is working.

[0088] Integrating optimization server functions into an LTE wireless network FIG. 1 shows an embodiment of the deployment of network elements that can provide LTE wireless services to users and their user equipment (UE). The eNB 102 unit may be deployed in a local area where its RF radiation can reach the UE 104. The Mobility Management Entity (MME) 108 and Serving Gateway (SGW) 110 units may be deployed in regional locations and handle multiple (for example, hundreds) of eNB 102 units. The MME 108 can connect to the eNB 102 unit via the LTE backhaul network 112 and manage the access of the UE 104 to the LTE network, and when the UE 104 switches its wireless network connection from one eNB cell (antenna) to another eNB cell, it also The movement of the UE 104 is processed. The SGW 110 may be connected to the eNB 102 unit via the LTE backhaul network 112 and provide a semi-static connection point for routing packets between the UE 104 and its target server 124 computer. Although the SGW 110 can change during the UE handover procedure, in many cases, the SGW 110 can remain fixed during the handover operation. Even when the UE 104 is in an idle state and is not actively connected to the network, the SGW 110 can maintain the bearer for the UE 104 (using the general packet radio service channel transmission protocol, also known as the general channel transmission protocol or GTP channel). The PDN gateway (PGW) 114 can generally be deployed in a more centralized data center and can be handed over to many (for example, hundreds) of SGW 110 units. The PGW 114 may constitute a connection point between the UE 104 and a specific packet data network 122 (for example, the Internet), and may not change, although the UE 104 passes through multiple handover procedures when it moves around in the LTE network. The home subscriber server (HSS) 120 may provide a database of subscriber subscription data. The Policy and Charging Rules Function (PCRF) 118 can control the allowed connection mode of each UE 104. The LTE wireless network boundary may therefore include UE 104, eNB 102, MME 108 and SGW 110, as well as PGW 114, HSS 120, and PCRF 118. The PGW 114 may interface with a specific packet data network 122, and an example of the packet data network is the Internet.

[0089] The user usually invokes the service program of his UE 104± and connects to the computer (server 124) that needs to be accessed, for example, via the Internet. Packets are routed from the UE 104 to the eNB 102 over the LTE air interface, where they can be placed in a specific GTP channel (called bearer 302) and sent to the SGW 110, then to the PGW 114, and then via the Internet 122 (or Other packet data networks) are sent to the server 124, and the server 124 is their destination. Then, the packet is sent from the server 124 to the PGW 114 via the Internet 122 (or other packet data network), and then sent to the SGW 110, the eNB 102 via a specific GTP channel (bearer 302), and finally sent to the UE 104 via the LTE air interface .

[0090] It is important to note that the computer of the server 124 that provides services to wireless users in FIG. 1 is generally away from those users and their UE 104. Therefore, the packet may suffer from delays caused by traversing the Internet 122, PGW 114 and SGW 110 network elements, LTE backhaul network 112, and eNB 102 elements and the LTE air interface. When congestion occurs at any of those points in the packet traversing path, the user experience is impaired. In addition, the server computer 124 that provides services to wireless users can be completely separated from the LTE wireless network and cannot collect real-time status about the wireless network (e.g., air interface usage, LTE backhaul usage at a given eNB 102, or PGW 114 and SGW 110 units of congestion). Therefore, today's server computers 124 may not be able to change their behavior in response to the real-time status of the LTE wireless network, and therefore cannot use real-time network data to improve the user experience in using the LTE wireless network and using the services provided by the server computer.

[0091] The present disclosure describes a method for solving the problems pointed out above by integrating server computers 202.204 (which may be a collection of server computers) into a wireless network at one or more points. In this article, it is alternatively referred to as OptServer or Priority and Optimization Processor (POP). The optimization server may be designed as a platform for running programs that provide services to the UE 104, and is therefore equivalent in this respect to the server computer 124 connected to the wireless UE today via the Internet or via another packet data network.

[0092] The "integration" aspect may include: management via a network management system that also manages wireless network units (for example, the LTE wireless network unit shown in FIG. 1), and may also include: having an interface with the wireless network unit , For the purpose of extracting real-time network data, and for the purpose of controlling the wireless network unit to deliver services to wireless users. The real-time network data can also be used to change the behavior of the service program executed on the optimization server 202.204, where the changed behavior improves the user experience. As an example, a service program that delivers streaming video to a user may use different video encoding rates based on real-time knowledge of the ability of the air interface to deliver a specific data rate to the UE 104. In addition, the arrangement of optimized server 202.204 in the wireless network can reduce the packet transmission delay experienced by users. As will be shown below, optimizing the interface of the server 202, 204 to the wireless network unit can be used to minimize the delay of exchanging packets between the server program and the UE 104.

[0093] FIG. 2 shows an embodiment of a deployment point of an optimization server in an LTE wireless network. A deployment point is shown associating the optimization server 202 with the PGW 114 unit, such as by providing the optimization server with a high-speed connection to the PGW, placing the optimization server near the PGW, co-locating the optimization server with the PGW, and so on. Doing so will place the optimization server 202 at the edge of the LTE wireless network, and therefore avoid the packet transmission delay that would otherwise be incurred in a packet data network that passes through the Internet. Using this method can better provide services such as streaming video or real-time video to a large number of concurrent users in the LTE wireless network area. In addition, if the PGW 114 (and the optimization server 202) are deployed regionally instead of centrally deployed in the country, the packet delay can be further reduced. The deployment configuration is shown in Figure 2. Also note that providing services via the optimization server 202 associated with the PGW 114 may still require packets to traverse the LTE backhaul network 112 to the wireless UE 104. The second important thing for the air interface is that the backhaul network 112 is a key resource that must be saved in its use. This point is shown by having a large number of users accessing through the same eNB 102 unit and all watching real-time video events. If all streaming video packets pass through the backhaul network, then there may not be enough bandwidth available to pass through the eNB 102 is used by other users connected.

[0094] The need to save backhaul 112 usage may result in the optimization server 204 being associated with the eNB unit, such as by providing the optimization server with a high-speed connection to the eNB, placing the optimization server near the eNB, co-locating the optimization server with the eNB, and so on. If a service to the UE 104 (eg, streaming real-time video events) can be provided via the optimization server 204 associated with the eNB 102 serving the UE 104, then the backhaul network can be used in delivering the service to the UE 104.

The use of 112 is minimized. In addition, the delay experienced by the packets exchanged between the serving access point (ie, the optimization server 204) and the UE 104 can be minimized because those packets only pass through the eNB 102 and the LTE air interface.

[0095] As an example, consider the task of providing video for real-time events to 200 hundreds of users connected through the same eNB 102. Without the optimization server 204 associated with the eNB 102, the serving access point is located outside the wireless network, and a single video packet stream for each UE 104 traverses the PGW 114. The SGW 110, the backhaul network 112, and the eNB 102 And LTE air interface. For 200 hundreds of UEs 104 watching the service at the same time through the same eNB 102, this means that the basic video rate can be consumed 200 times on the backhaul network 112. Now consider the case where the optimization server 204 is associated with the serving eNB 102. Suppose further that the optimization server 204 and the UE 104 implement the publish/subscribe communication paradigm described herein, so all 200 UEs subscribe to receive the same real-time video transmission. The video data stream is sent once from its generation point in the Internet through the LTE network, and through the backhaul 112 to the optimization server 204 associated with the serving eNB 102. Then, the publish/subscribe software on the optimization server 204 distributes the video packet stream to each of the 200 UEs 104 that have subscribed to the service via the optimization server 204.

[0096] Because the bearer 302 (ie, GTP channel) is set up in the LTE network to carry packets to and from the UE, there may not be a clear way to connect the UE to the optimization server associated with the eNB. Part of this disclosure shows how this connection can be established. In addition, when the service is provided by the server 124 attached to the Internet or the optimization server 202 associated with the PGW, the service can continue to be provided from the same service access point without interruption, even if the UE moves through the LTE wireless network and is Handover is performed between eNB 102 units in the LTE network. However, when the serving access point is the optimization server 204 associated with the eNB 102, when the UE 104 enters a handover to another eNB 102, the access point may need to be changed. A portion of this disclosure shows how the serving access point can quickly switch between the optimization server 204 associated with the eNB 102 unit. If the service access point switching is performed fast enough, then the user will not experience the interruption of the service being provided. Before switching the serving access point, the UE 104 may be required to connect to the optimization server 204 associated with the eNB 102 unit.

[0097] FIG. 3 shows that in an LTE network, a different bearer 302 can be established for each UE 104 in order to connect the UE 104 to the PGW 114 unit. The PGW 114 unit may provide an interface with a packet data network (eg, the Internet 122) where the user service computer is usually located. In an embodiment, each bearer 302 is a channel, which uses a simple GTP (General Tunnel Transport Protocol) header to encapsulate packets routed through the channel. The packet routing entry channel can be at the UE 104 and at the PGW 114 by associating the IP address and port number in the packet with the Internet Protocol (IP) address and port number in the "service flow template" associated with the bearer 302. achieve. Each bearer 302 established for the UE 104 has a different quality of service (QoS) associated with it. Up to 15 bearers 302 can be established for a single UE 104. The first bearer 302 established to a given PGW 114 is referred to as the default bearer 302. Any other bearers 302 established to the PGW 114 are referred to as dedicated bearers 302.

[0098] FIG. 3 shows an embodiment in which a dedicated bearer 302 is "redirected" to point to the optimization server 204 associated with the eNB 102 serving the UE 104. In this example, the optimization server 204 associated with the eNB 102 is marked as OptServereNB 308, and the optimization server 202 associated with the PGW 114 is marked as OptServerPGW 304. The application 310 of the UE 104± can be communicated with the OptServerPGW 304 by carrying it. The default bearer 302 of the packet of the associated PGW 114 sends the packet to communicate with the OptServerPGW 304. Packets can be sent from OptServerPGW 304 to UE 104 by traversing the same default bearer 302. After the redirection of the dedicated bearer 312 is completed, the application 310 on the UE 104 can communicate with the OptServer eNB 308 by sending packets via the redirected dedicated bearer 312. Packets can be sent from OptServereNB 308 to the OptServereNB 308 via dedicated bearers 312 that traverse the same redirection

UE; there is no need to use backhaul in the packet exchange through the redirected bearer 312.

[0099] Redirecting the bearer 302 may not be a standard operation, and therefore, it may need to be completed via an OAM type interface (operation, management, and maintenance interface) to the eNB 102. In addition, note that in FIG. 3, after the dedicated bearer 312 is redirected at the eNB 102, the channel information that previously linked the bearer to the SGW 110 is still maintained in the eNB 102. This may be necessary to be able to perform handover without changing the existing handover process, and to be able to perform fast redirection to the same dedicated bearer 312 at the target eNB during the handover. The dedicated bearer 302 may not have to be re-established after the handover, because when the bearer is redirected to the OptServer eNB 308, it may not be deleted from the list of established bearers 302 of the eNB 102.

[0100] In the architecture shown in FIGS. 2 and 3, the OptServerPGW 304 can be used as a control point for redirecting the bearer 312 at the eNB 102 unit for any UE 104. Figure 4 shows a collection of message interactions that can be used to achieve redirection. When the UE 104 accesses the LTE network, the default bearer 302 to the PGW 114 associated with the OptServerPGW 304 can be established. The UE 104 may perform a Domain Name System (DNS) query in order to retrieve the IP address of OptServerPGW 304. The UE 104 can use the default bearer 302 to connect to the wireless control process 3902 of OptServerPGW 304 ±, And register itself with the program. The registration information may include: the cell ID of the LTE cell through which the UE currently accesses the network, the cell radio network temporary identifier (C-RNT 1) (which is a parameter used in the eNB 102 to identify the UE 104), and The IMS1 (International Mobile Subscriber Identity) of the UE 104 in all LTE network units except the eNB 102 and the GUTI (Globally Unique Temporary Identifier) used to identify the MME 108 unit currently serving the UE 102. As discussed herein, other parameters may be passed by the UE 104 to the radio control process 3902 via a registration message (for example, the IP address of the UE) in order to facilitate the implementation of other services.

[0101] When the UE 104 registers with the program on the OptServerPGW 304, it may receive a confirmation response, which may contain a command for establishing a dedicated bearer linked to the currently used default bearer. Alternatively, the LTE network provided at the PCRF (Policy and Charging Rules Function) can initiate the establishment of such a dedicated bearer for the UE 104. The UE 104 can use the standard LTE procedure to establish the dedicated bearer 302, and when it is completed, the UE 104 sends a response containing the IMSI (used to identify the UE 104 to the radio control program 3902) and the bearer ID of the newly established bearer 302 to the OptServerPGW 304 . Because the radio control process 3902 can have the cell ID of the UE 104, it can determine the ID of the eNB 102 currently serving the UE 104. For example, using the OAM IP address provided for the eNB 102 unit, the radio control process 3902 can send a message to the serving eNB 102 to order it to redirect the bearer 302. The C-RNTI can identify the context of the UE 104 to the eNB 104, and the bearer ID can identify the Redirected UE bearer 302. The server IP address informs the eNB 104 which OptServereNB 308 is the target of redirection (so more than one optimization server 308 can communicate with the eNB 102 Associated). When the eNB 102 completes the redirection operation, it can reply to the radio control procedure 3902. Next, the radio control process 3902 can send a packet to the UE 104 via the default bearer 302 to inform the UE 104 that it can start using the redirected dedicated bearer 312 to start the service using the OptServereNB 308 as a service access point. By directing the packet via the redirected dedicated bearer 312, the UE 104 can start any one of a variety of services. For all of these services, the use of the backhaul 112 can be minimized, and similarly, the packet delay can be minimized.

[0102] Transfer of service delivery between eNB-based optimization servers during handover. In FIG. 2, it is assumed in the example that the UE 104 is receiving a service from the OptServereNB 308 associated with its serving eNB 102. If the UE 104 moves, it is in the process of handover to another eNB 102, then the serving access point must be changed to the OptServereNB 308 associated with the new target eNB 102 unit. In this case, service interruption is not possible

Avoided, so it should be made as short as possible. In order to minimize service interruption, it is necessary to embed additional message interactions for implementing changes in service access points along with the standard handover process used in LTE networks. Therefore, this article provides a brief discussion of standard handover processing.

[0103] The standard handover process can be divided into three stages: for example, handover preparation, handover execution, and handover completion. See Fig. 5. The current serving eNB 102 is called a source eNB. The new eNB 102 is called a target eNB. In the handover preparation phase, the source eNB 102 receives signal measurements from the UE 104 and determines that the antenna at another eNB 102 provides a stronger signal to the UE 104 and that the handover should occur. The source eNB 102 transmits its context information for the UE to the target eNB 102, which includes the ID and channel parameters of each bearer valid for the UE. The channel information for the redirected bearer 312 may be included in the set of bearer information, but the information is for the channel end point at the SGW 110 instead of the OptServereNB 308 associated with the source eNB 102. In this way, the standard handover process may not be affected by the inclusion of the OptServereNB 308 and the redirected bearer 312. The parameters involved in the redirection of the bearer 312 are not transmitted in the handover process. At the same time, the target eNB 102 may send the C-RNTI value of the UE 104 to the source eNB 102 for use at the target eNB 102. When the handover preparation phase is completed, the source eNB 102 sends a handover command message to the UE 104 and includes the new C-RNTI value. Source eNB Any downlink data for the UE 104 received by 102 may not be sent to the UE 104 in the air, but forwarded to the target eNB 102, and queued at the target eNB 102 until the UE 104 connects at the target eNB 104. The SGW 110 may not yet be aware of the handover, and therefore, it may continue to forward the downlink data to the source eNB 102.

[0104] When the UE 104 receives the handover command, the handover execution phase can start. The UE 104 synchronizes with the signal sent by the target eNB 102, and when the synchronization is completed, the UE 104 uses the new C-RNTI value to access the target eNB 102 and sends a handover confirmation message to the target eNB 102. The target eNB 102 starts to send the queued forwarded data to the UE 104 via the air interface. Because the channel information for the UE bearer 302 from the handover preparation phase is available at the target eNB 102, the UE 102 can start to send uplink packets through the target eNB 102. The uplink packet for the bearer 302 that needs to be redirected is not sent at this moment because the redirection has not yet occurred at the target eNB 102.

[0105] In the handover completion phase, the SGW 110 can be provided with the bearer 302 channel parameters used at the target eNB 102, and the SGW 110 can now forward the downlink data to the target eNB 102. The UE 104 ± the following information can be deleted at the source eNB 102, and the handover process is completed. See Figure 5.

[0106] FIG. 6 shows the interaction between the UE 104 and the optimization server 202.204, which integrates these servers into the LTE handover process and effectively transfers the service delivery point from the optimization server 308 located at the source eNB 102 to the optimization server 308 located at the target. The optimization server 308 of the eNB 102. According to FIG. 6, the UE 104 client can play a role in ensuring that no data is lost in the conversion of the optimization server 308 unit. The OptServerPGW 304 plays a role in sending a command to the target eNB 102 so that the bearer 312 that was previously redirected to the source eNB 102 is now redirected to the target eNB 102. The use of a small number of messages (e.g., five) for implementing changes in the service access point means that changes can be completed quickly. In this example, the message may include: disconnect from OptServereNB 308 at the source eNB 102>Handover (), RedirectBearer (), RedirectBearerDone (), ResumeSession (), and so on. See Figure 6.

[0107] In FIG. 6, the LTE software executed on the UE 104± can notify the UE 104 client that the handover command message has been received. Before allowing the UE LTE software to continue synchronization with the target cell, the UE 104 client can send packets through the redirected dedicated bearer 312 to disconnect from the OptServereNB 308 associated with the source eNB 102. When this operation is completed, the UE 104 client may allow the UE LTE software to continue. When the UE 104 sends a handover confirmation message to the target eNB 102, another notification may be provided to the UE 104 client. Then, the client can

The radio control process 3902 executed on OptServerPGW 304 sends a Handover () message to notify it of the new cell ID, the new C-RNTKIMSI and GUTI (which may have changed), and the bearer ID of the dedicated bearer 312 that needs to be redirected , Plus other parameters that may be required to provide additional services (for example, the IP address of UE 104). The radio control process 3902 can derive a new eNB ID based on the new cell ID, and obtain the OAM IP address of the eNB based on the provided data or other data. The target eNB 102 may be instructed to redirect the bearer 312 for the UE 104 and reply when it is completed. At this time, the radio control process 3902 can send a ResumeSession() message to the UE 104 via the default bearer 302, and the UE 104 client can send packets to the OptServereNB 308 at the target eNB 102 via the redirected dedicated bearer 312 in order to continue at the source eNB 102 The interrupted session at the location.

[0108] Using the LTE handover mechanism to replace the airborne eNB Referring again to FIG. 1, in an emergency, the wireless infrastructure may be destroyed or may not work, and it becomes necessary to deploy a temporary network in a self-organizing manner. One way to achieve this deployment is to place the eNB 102 network element in an airborne vehicle and make it hover over an area that requires LTE wireless service (as indicated by the cell coverage area 712). The airborne vehicle can be manned or unmanned. In the latter case, the aircraft can be called an unmanned aerial vehicle (UAV 708). Enhanced packet core network (EPO710 network unit can include: MME 108, SGW 110, PGW 114, HSS 120, PCRF 118, etc.) Etc., plus a router 702 for providing communication interconnection between network elements. The MME 108, SGW 110, and PGW 114 network elements may be deployed in a second airborne vehicle 710 that may be located away from the operation area of the eNB 102 unit. The MME 108 and PGW 114 network elements can communicate through the long backhaul network connection 704 and the long backhaul network 804 with the HSS 120 and PCRF 118 network elements. The eNB-based vehicle 708 and the EPC-based vehicle 710 can communicate through the wireless backhaul interface 112 . All LTE network units can use The long backhaul network 804 is used to communicate with the element management system (EMS) 802. This configuration is shown in FIG. 7. Another deployment of EPC 710 units is in ground-based nodes. In this case, the airborne eNB 102 vehicle 708 communicates via a wireless radio link 112 to a ground station that provides connections to the EPC 710 unit and to the EMS 802.

[0109] Although other deployment configurations are possible, it may be better for the eNB 102 unit to deploy the eNB 102 unit itself instead of adding other LTE network units to the air vehicle 708 carrying the eNB 102. It is especially useful to follow this deployment when using unmanned aerial vehicles (UAV). In these deployments, weight and power limitations can be important, and carrying only the eNB 102 instead of any other LTE network unit can ensure that the UAV 708 carrying the eNB 102 has minimal load weight and power consumption.

[0110] Replacing the eNB UAV in the operating area In any far-field deployment situation, but especially when the platform containing the LTE network element is a UAV, the time to replace the UAV will come. The reason may be that the battery power for the LTE device is insufficient, or the UAV fuel is insufficient, or it may be that the UAV carrying the LTE device needs to be removed from the site and repaired. In any case, it is possible to replace the UAV platform with the UAV platform working in the field. The following algorithm shows how the eNB UAV 708 can be replaced while the UAV 708 is serving on the operating area. The algorithm used to implement the replacement is such that continuous service is provided to the UE 104 in the operating area of the eNB 102.

[0111] FIG. 8 depicts a situation where the eNB1 UAV 708 is being replaced by another eNB2 UAV 708 that has reached the operating area. An example of the replacement process is as follows:

1. The replacement UAV 708 carrying the eNB2 102 arrives at the location of the UAV 708 carrying the eNB1 102, and the eNB2 102 establishes radio communication with the backhaul antenna/radio of the UAV 710 hosting the EPC 710 unit.

[0112] 2. eNB2 102 establishes management with remote unit via router 702 included in EPC UAV 710 equipment

System (EMS 802) communication.

[0113] 3. The EMS 802 provides the eNB2 102 with the same parameters as the eNB1 102, except that its cell ID is different.

4. The EMS 802 starts the replacement process at the eNB1 102, and orders the eNB1 102 to reduce its transmission power at the rate Pr, and at the same time orders the eNB2 102 to turn on its transmitter and increase its transmission power output at the rate Pr. When UE 104 moves away from eNB1 102 and towards eNB2 102, the rate Pr should be selected to simulate the power received at UE 104 from two fixed antennas separated by a general 2-cell radius in the deployed commercial LTE system, And the simulated motion rate of UE 104 is 3-30 km/hro

[0115] 5. At a certain point determined by the rate Pr and the RF propagation characteristics on the operating area, all user equipment (mobile phones, digital units) in the RF area 712 covered by the eNB1 102 (and now also covered by the eNB2 102) , Sensors, etc.) determine that the cell at eNB2 102 has a sufficiently strong signal compared to the cell at eNB1 102, and a handover to the cell at eNB2 102 should be performed. All UEs 104 in the RF coverage area 712 now perform handover from eNB1 102 to eNB2 102.

[0116] 6. When all UEs 104 migrate away from eNB1 102, eNB1 102 sends a "replacement complete" instruction to EMS 802, and eNB1 102 is now ordered to reduce its transmit power to zero. The eNB1 102 can leave the operating area. The eNB replacement is completed without losing service to the UE in the operating area.

[0117] Beamforming using periodic scanning of agile beam patterns Allowable beam periods in an LTE wireless system In an embodiment, the present disclosure may provide an RF beamforming technology in an LTE wireless system. A specific beamforming technology can generate a number of "N" RF beams at the same time (for example, in each 1 millisecond interval of the LTE frame 1002), where the duration of the LTE frame 1002 can be 10 milliseconds. The N RF beams 902 can cover N sub-areas 902 of the total coverage area 712 of the LTE cell, the coverage area 712 is determined by the LTE cell using the same total transmit power used for the beamforming solution, but it may not use the beamforming technology. In the next interval, another set of N RF beams 902 can be generated in order to cover a different set of N sub-regions 902. This process can be repeated until the entire cell coverage area is scanned by the RF beam pattern 902. The RF beam pattern 902 periodically repeats in this scanning manner.

[0118] The present disclosure may provide information related to constraints on the scan period that may need to be complied with by the RF beam pattern 902. For example, without limitation, for a frequency division duplex (FDD) system, the period of the RF beam pattern 902 may be required to be 4 milliseconds. For a time division duplex (TDD) system, the period can usually be 10 milliseconds (ie, one LTE frame 1002), but it can be a shorter interval, which depends on the TDD uplink/downlink used in the LTE system (U/D) Configuration 1002. The data presented herein is the result of analysis through the methods and systems of the present disclosure. Some specific constraints are given below.

[0119] Beamforming technology has been used in the fields of audio signal processing, sonar signal processing, and radio signal processing for many years. In many implementations, a technique is used to determine the location of the signal source (used for reception at the antenna array) and then focus the antenna array at that point. Using beamforming techniques related to the present disclosure for LTE wireless systems, beamforming operates in different ways and takes advantage of the fact that in LTE, data transmission to and reception from UE 104 is performed by the LTE base station. Scheduled by the software in 102. Beamforming technology focuses the RF beam set on a specific, non-overlapping sub-area of the cell coverage area 712 during a fixed, short time interval, and then moves to a non-overlapping sub-area of the cell coverage area 712 during the same fixed, short time interval Another collection of. The beam pattern can be moved in this manner until the entire cell coverage area 712 is scanned for transmission from the antenna array and for reception by the antenna array. Then, the covered beam pattern is repeated in a periodic manner. See Figure 9 by the LTE frame

An example of a beam scanning pattern composed of four RF beams 902 generated in each of four consecutive 1 millisecond subframes, where the pattern repeats every 4 milliseconds. In the first 1 millisecond interval, RF beams 902 numbered 1, 11, 9, and 14 can be generated, where these RF beams form a non-contiguous set of RF beams 902. In the second 1 millisecond interval, RF beams 902 numbered 3, 6, 7, and 13 can be generated. In the third 1 millisecond interval, RF beams 902 numbered 4, 8, 10, and 16 can be generated. In the fourth 1 millisecond interval, RF beams 902 numbered 2, 5, 12, and 15 can be generated. In the fifth 1 millisecond interval, the pattern repeats. Other sets of RF beam patterns 902 can be used, provided that they are non-adjacent to ensure optimal operation of the agile beamforming system.

[0120] The present disclosure may cover the restriction on the repetition rate of the beam pattern 902, and for the TDD system, also cover the restriction on the set of subframes of the frame 1002 in which the RF beam pattern 902 needs to be exactly the same.

[0121] LTE is an OFDM (Orthogonal Frequency Division Multiplexing) system. Organize the transmission interval into a set of subframes, and the set of 10 subframes includes LTE frame 1002, each subframe has a duration of 1 millisecond, and each of these subframes is further divided into two time slots, each time slot The duration is 0.5 milliseconds. In the LTE FDD system, different frequency bands are used for uplink and downlink transmission. Therefore, in any subframe, the UE 104 may be scheduled to receive downlink transmission and/or may be scheduled for uplink transmission. In the LTE TDD system, the same frequency band is used to carry uplink and uplink transmissions. To organize these transmissions, each subframe in the set of 10 subframes in each LTE frame 1002 may be configured for uplink transmission or for downlink transmission. As shown in FIG. 10, there are 7 different TDD U/D configurations 1002 specified for LTE operation. A specific LTE eNB 102 may be configured to use one of these configurations 1002. The subframes marked as "S" in FIG. 10 are used to transmit uplink pilot signals and downlink pilot signals. The S-subframe is not used to determine the constraints imposed on the RF beamforming technology.

[0122] Hybrid automatic repeat request (H-ARQ) processing transmission over the air interface is prone to errors caused by interference and fading. Each transmission in the uplink direction and the downlink direction must be confirmed by the other end. This is done by sending a hybrid automatic repeat request (H-ARQ) acknowledgment or negative acknowledgment on the control channel. H-ARQ is a powerful technology used to improve the performance of LTE systems better than other wireless systems, and it may be necessary to maintain H-ARQ when beamforming technology is used.

[0123] In the downlink direction, H-ARQ ACK/NAK is used for uplink transmission and sent on the physical H-ARQ indicator channel (PHICH), which is the PDCCH (Physical Downlink Control Channel) One part, that is, PHICH is sent in the first 1-3 symbols of each subframe. In the uplink direction, Η-ARQACK/NACK (acknowledgement character or negative acknowledgement character) is sent on the physical uplink control channel (PUCCH), which is implicitly scheduled shortly after the downlink transmission.

[0124] When a downlink transmission is "NAKed" (ie, a negative acknowledgement character is received) and needs to be retransmitted, the media access control (MAC) layer in the eNB 102 unit may need to schedule the retransmission. When beamforming technology is used, the MAC may be required to schedule retransmissions to occur in a subframe that forms the RF beam 902 covering the current UE 104 location, and data may be sent to the UE 104 via the covering RF beam 902. Because all user plane data may need to be sent to the UE 104 in the subframe that forms the RF beam 902 covering the location of the UE 104, the statement of downlink transmission may require the use of beamforming technology to be consistent with the initial transmission of the user plane data. Treat the retransmitted data in the same way. These statements apply equally to FDD systems and TDD systems. When using beamforming technology, maintaining the efficiency of retransmission in the downlink direction is not a problem.

[0125] The uplink retransmission may not be explicitly scheduled, but implicitly scheduled. For example, assume that the UE 104 performs uplink transmission in a subframe where the eNB 102 beamforming receiver focuses on the location of the UE 104. In the FDD system, if the UE

If 104 receives any NAK transmitted via the downlink PHICH, it may be necessary to send the NAK after four subframes including the subframe transmitted by the harmful UE 104. The UE 104 uses implicit scheduling to retransmit information four subframes after receiving NAK. Therefore, in the FDD system, if the period covered by the RF beam 902 of the cell subregion 902 is different from 4 milliseconds, this means that the UE 104 retransmission can occur in a subframe where the location of the UE 902 is not illuminated by the RF beam 902. As mentioned earlier, the UE 104 interprets the ACK or NAK received on the PHICH in the subframe n as applicable to the UE 104 transmission in the subframe 5-4), see section &3 of TS 36.213 va40. At the same time, the UE 104 implicitly reschedules its retransmission in the subframe (n+4). See TS 36. 213 va40 section &0. Therefore, unless the RF beam 902 rotation through the cell coverage area 712 is 4 milliseconds (4 subframes) in the FDD system, the uplink retransmission fails (the eNB 102 is searching for the receive beam for UE 104 user plane transmission, and In the case of a rotation other than 4 milliseconds, the beam position 902 in the subframe where the retransmission occurs does not cover the UE 104 position). An example of using a beam 902 rotation period of 5 milliseconds compared to a beam 902 rotation period of 4 milliseconds in an LTE FDD system is shown in Figure IL·

[0126] H-ARQ processing for uplink retransmission in TDD system

The situation of the TDD system may be more complicated because the relationship between the subframe in which the NAK is received and the reference subframe of the original transmission is different for different TDD U/D configurations 1002. Therefore, the relationship between the received NAK subframe and the subframe in which the UE 104 implicitly schedules retransmission is also different for different TDD U/D configurations 1002. Table & 3-1 in TS 36. 213 a40 is reproduced below, which gives the above relationship. If a NAK is received in subframe n, it implicitly mentions the transmission sent by UE 104 in subframe (nk), where the value k is shown below for different TDD U/D configurations 1002.

[0127] Table 1: The relationship between the NAK subframe received in the TDD system and the original transmission

<td>TDD1 l, l&gt;L configuration</td><td colspan="10">Number of subframes received by PHICH NAK (π)</td>

<td></td><td>0</td><td>1</td><td>2</td><td>3</td><td>4</td><td>5</td><td>6</td><td>7</td><td>8</td><td>9</td>

<td>0</td><td>7</td><td>i:</td><td></td><td></td><td></td><td>7</td><td>4</td><td></td><td></td><td></td>

<td>1</td><td></td><td>4</td><td></td><td></td><td>6</td><td></td><td>4</td><td></td><td></td><td>6</td>

<td>2</td><td></td><td></td><td></td><td>6</td><td></td><td></td><td></td><td></td><td>6</td><td></td>

<td>3</td><td>6</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>6</td><td>6</td>

<td>4</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>6</td>

<td>5</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>6</td><td></td>

<td>6</td><td>6</td><td>4—..................</td><td></td><td>...................................................</td><td></td><td>7</td><td>4</td><td>__</td><td>_</td><td>6</td>

[0128] The NAK transmission from the eNB 102 may only come in a specific downlink subframe, and is not always four deleted subframes like the FDD system.

[0129] Another way to view this information is to view the subframe where the original UE 104 transmission was made, and then use this value to show when the NAK for this transmission can be sent by the eNB 102. This view is presented in Table 2 below. In Table 2, the symbol h} means that NAK is received in subframe h of the following LTE frame. According to Figure 10 and Table 4.2-1 of TS 36.211 a40, the TDD configuration shows the uplink/downlink (or S) behavior of the system in each subframe.

[0130] Table 2: Original UE transmission subframe and subframe in which NAK was received in TDD system

<td rowspan="2">TDDH/D with 7!</td><td rowspan="2">The switch point f «Μ|&lt;φ· Jiij JPJ:</td><td colspan="10"></td>

<td colspan="9">Note; Huxian means PHIO ft F a fT "frame n arrival" in the indicated sub-.</td><td>i NAK</td>

<td></td><td></td><td>0</td><td>1</td><td>2</td><td>3</td><td>4</td><td>5</td><td>b</td><td>7</td><td>8</td><td>»I</td>

<td>0</td><td>5 rm</td><td>1&gt;</td><td>S</td><td>176</td><td>IJ7(U</td><td>I</td><td>1&gt;</td><td>S</td><td>t/l}</td><td>U/5}</td><td>U</td>

<td>I</td><td>5 tn buzzard</td><td>D</td><td>S</td><td>IV6</td><td>U/9</td><td>D</td><td>D</td><td>s</td><td>li/c</td><td>(!/4|</td><td>I)</td>

<td>2</td><td>5 rm</td><td>1&gt;</td><td>S</td><td>1^!/8</td><td>1）</td><td>1)</td><td>1）</td><td>s</td><td>ΙΊ31</td><td>1&gt;</td><td>0</td>

<td>3</td><td>10 nis</td><td>D</td><td>S</td><td>11/8</td><td>179</td><td></td><td>D</td><td>I)</td><td>1)</td><td>1)</td><td>D</td>

<td>4</td><td>10 ms</td><td>η</td><td>S</td><td>1-V8</td><td>179</td><td></td><td>l&gt;</td><td>0</td><td>1)</td><td>1&gt;</td><td>D</td>

<td>5</td><td>1ft in*.</td><td>0</td><td>S</td><td>178</td><td>0</td><td>I)</td><td>I)</td><td>D</td><td>h</td><td>1)</td><td>II</td>

<td>6</td><td>5 ms</td><td>1&gt;</td><td>S</td><td>I'M</td><td>I: /9</td><td>U/0}</td><td>1&gt;</td><td>s</td><td>JET</td><td>II/5J</td><td>I&gt;</td>

[0131] Now that it is clear in which subframe the NAK can be sent for UE 104 transmission, the next point to understand is the subframe in which UE 104 can retransmit its information. The offset relative to the subframe in which the NAK is received may also depend on the TDD configuration 1002, and on the subframe in which the NAK is received. If NAK is received in subframe n, then UE 104 schedules its retransmission in subframe (n+k), where k is given in the following table (from TS 36.213 a40 for normal HARQ operation) Table 8-2).

Table 3: Value k used for UE retransmission in subframe (n+k) when NAK is received in subframe n

<img file="CN104662994A_D0001.tif" />

[0133] Table 1, Table 2, and Table 3 provide a set of constraints on where the RF beam 902 must be in order to retain HARQ capabilities in a TDD system using beamforming technology. For example, if the RF beam 902 is focused on the position in the subframe n when the UE 104 transmits information, then when the UE retransmits its data, the same RF beam 902 pattern may need to take effect in the subframe. For example, Table 2 shows that for TDD configuration 0, if the UE 104 sends information in subframe 3, the NAK for this transmission comes in subframe 0 of the subsequent LTE frame. Table 3 specifies that the NAK received in subframe 0 causes the UE to reschedule its retransmission in subframe 4 (4 subframes after receiving the NAK). This relationship means that the RF beam pattern 902 in subframe 3 (the subframe where the original transmission occurs) and subframe 4 (the subframe where the retransmission occurs) may need to be the same. All constraints implied by these H-ARQ tables determine how many separate sets of RF beam patterns 902 can be for a TDD system using a particular U/D configuration, and therefore determine the repetition rate that may be required for that RF beam pattern 902 . This result is not as straightforward as for FDD systems. In FDD systems, there are 4 RF beam patterns that repeat every 4 subframes.

[0134] Before analyzing Table 1, Table 2, and Table 3 for all HARQ constraints on beam patterns, it may be necessary to

Another aspect of the system is analyzed with regard to the number of subsets applied to the RF beam pattern 902 and the additional constraints in which the RF beam pattern may not require the same subframe. Additional constraints can be imposed by channel quality indicator (CQI) measurements, as these measurements can be used to place the UE 104 in different RF beam positions 902. As described herein, the description for positioning and tracking the UE 104 in the RF beam 902 of the periodic scanning RF beam system explains CQI measurements and how they can be used in an LTE system using this beamforming technique.

[0135] Channel Quality Indicator (CQI) In order to be able to optimize the downlink transmission by adjusting the modulation and coding scheme (MCS), the mobile device 104 may have to use the PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared The channel quality indicator (CQI) is sent on the channel. The CQI is a 4-bit result indicating the measured value. The measurement can be on the entire frequency range of the cell bandwidth, or it can be on a certain subset of the frequency range. The entire frequency range can be divided into a set of physical resource blocks, and in order to perform CQI measurement on a frequency range smaller than the total RF bandwidth allocated to the cell, a set of these physical resource blocks is defined as a "subband". In the LTE system, subband CQI measurement can be performed aperiodically, where the report is sent via PUSCH. Periodic wideband CQI measurement can be performed by sending a report to the eNB 102 using PUCCH.

[0136] When the eNB 102 wants the UE 104 to perform channel quality measurement and return a CQI measurement value, it may send command information called downlink command information (DCI) to the UE 104. In the FDD system, if the DCI is sent in subframe n, the QCI measurement is reported by the UE in subframe (n+4). This plus the (n+8) HARQ constraint for uplink retransmission can indicate that the FDD system includes four sets of RF beam patterns 902 that are repeated every 4 subframes. In the TDD system, the DCI command may be restricted from being sent in the subframes shown in Table 2 by the eNB 102 (ie, the same subframe in which the ACK/NAK is allowed to be sent). The UE 104 CQI measurement report is returned to the eNB 102 after k subframes, where k is shown in Table 3. Because the UE 104 location determination algorithm uses the so-called aperiodic CQI report, where the report is returned via the PUSCH channel (ie, within the RF beam 902), this means that the subframe in which the DCI command is sent and contains the CQI The corresponding subframe of the measurement report may need to generate the same RF beam pattern 902.

[0137] Determination of the number of RF beam patterns in a TDD system. The information in Table 1, Table 2 and Table 3 can now be used to determine the RF beam pattern 902 that can be maintained in a TDD system using a specific U/D configuration 1002 And the number of subframes that may need to use the same RF beam pattern 902. The constraint is based on the fact that HARQ may need to be reserved for UE 104 retransmission; the original transmitted subframe and the retransmitted subframe may need to have the same RF beam coverage 902. In addition, the DCI measured for channel quality information in a given subframe and the CQI report in another subframe may need to have the same RF beam coverage 902 in those two subframes. According to what is presented herein for positioning the UE 104 in the RF beam 902 when the UE 104 accesses the cell for the first time, and for tracking the UE when the UE 104 moves across the set of RF beam 902 positions covering the cell area 712 The 104 algorithm, the reason for this statement is clear. Combine the information in Table 1, Table 2, and Table 3 into the following table to make the analysis for each TDD U/D configuration 1002 easier to visualize.

[0138] The notation used in Table 4 is described here. For each TDD U/D configuration 1002, the configuration is repeated from Figure 10 for the convenience of the reader. The row above the configuration is used to indicate the subframe X in which the UE 104 can send uplink transmissions (that is, in any U subframe), the subframe (N) in which the corresponding NAK is received, and the subframe (N) in which the corresponding reconfiguration occurs Transmission subframe (R). If the relevant subframe appears in the previous LTE frame (2+LTE frame is shown in Table 4), it is indicated by N{j (for NAK, the reference transmission is the subframe j in the previous LTE frame ), or indicated by R{j (for retransmission, the original transmission occurred in subframe j of the previous LTE frame). In one case (TDD configuration 6), the retransmission is for the original transmission two LTE frames before, so the flag is used {j ο

[0139] The row below the configuration row is now used to indicate when a DCI command can be sent by the eNB 102 to cause CQI measurement. The mark dci-j is used to indicate that the DCI command is sent in subframe j (it has been indicated in subframe j, so this part is for easy viewing). The corresponding CQI measurement result returned to the eNB 102 is a subframe marked by CQI-j, where again, if the corresponding DCI command appears in the previous LTE frame, then the mark CQI-{jo

[0140] Table 4: HARQ and DCI/CQI data used to determine the number of RF beam sets in a TDD system.

ο

1" ο

Yi Xuan: Sky" T Ni \ Ϊ X: nr· R i N it ίί

<img file="CN104662994A_D0002.tif" />

<td></td><td>ft</td><td></td><td>2</td><td>Λ</td><td>4</td><td>5</td><td></td><td>7</td><td>H</td><td>&lt;&gt;</td><td>«</td><td>I</td><td>2</td><td>3</td><td>4</td><td>5</td><td>ή</td><td>7</td><td>H</td><td>9</td><td>0</td><td>1</td><td>² -¹</td>

<td>X-Warbler</td><td></td><td></td><td>X</td><td></td><td></td><td></td><td></td><td>X cattle</td><td>N*</td><td></td><td></td><td></td><td>R2</td><td>N</td><td></td><td></td><td></td><td>R"</td><td></td><td></td><td></td><td></td><td>^{： ：}1| ^：：i:: i</td>

<td>Match</td><td>0</td><td>s</td><td>r</td><td>D</td><td>0</td><td>D</td><td>-S</td><td>I</td><td>D</td><td>D</td><td>B</td><td>s</td><td>V</td><td>D</td><td>D</td><td>D</td><td>s</td><td>Γ</td><td>D</td><td>D</td><td>D</td><td>s</td><td>V 0:|:^：-s</td>

<td>Set 3</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>:j: J</td>

<td>tk Pro&lt;P</td><td></td><td></td><td></td><td>dc</td><td></td><td></td><td></td><td>e4</td><td>dA</td><td></td><td></td><td></td><td>c*;; UX</td><td>dvi;</td><td></td><td></td><td></td><td>cq!\</td><td></td><td></td><td></td><td></td><td>i" KindI: 4</td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>0</td><td></td><td>2</td><td>i</td><td>4</td><td>5</td><td>fr</td><td>7</td><td>s</td><td>turn</td><td>H</td><td>1</td><td>2</td><td>5</td><td>4</td><td>5</td><td>0</td><td>7</td><td>H</td><td>type</td><td></td><td>1</td><td>2 *</td>

<td>£Μ</td><td></td><td></td><td>X test</td><td>X1</td><td>X--i</td><td></td><td></td><td></td><td>X?</td><td>N</td><td>Ni</td><td></td><td>R2</td><td>Build 3</td><td>R: -i</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>：^：l^:j</td>

<td>Match</td><td>D</td><td></td><td>1</td><td>Γ</td><td>V</td><td>l&gt;</td><td>D</td><td>1)</td><td>D</td><td>D</td><td>n</td><td>s</td><td>l·</td><td>F</td><td>I:</td><td>0</td><td>I)</td><td>i&gt;</td><td>l&gt;</td><td>O</td><td>I&gt;</td><td>s</td><td>I 1</td>

<td>Set</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td> ;Ji</td>

<td>tk</td><td>d</td><td></td><td></td><td></td><td>c</td><td></td><td></td><td></td><td>d</td><td>d</td><td>d</td><td></td><td>c</td><td>V</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>afraid</td><td>fi</td><td></td><td></td><td></td><td>H^：: B&lt;1</td><td></td><td></td><td></td><td>CN</td><td></td><td>t-11</td><td></td><td>&lt;r*</td><td>n</td><td>&lt;1 ll'i0</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>-1</td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>0</td><td></td><td>1</td><td>3</td><td>4</td><td>5</td><td>i&gt;</td><td>7</td><td>X</td><td></td><td>If</td><td>I</td><td>2</td><td>3</td><td>4</td><td>5</td><td>6</td><td>7</td><td>X</td><td>medical</td><td>ϋ</td><td></td><td>2 3...... Er Tan</td>

<td>X.»</td><td></td><td></td><td>X2</td><td>、:</td><td></td><td></td><td></td><td></td><td>N2</td><td>X*</td><td></td><td></td><td>R</td><td>R?</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>--: | ί</td>

<td>Configuration</td><td>η</td><td>s</td><td>1</td><td>t</td><td>11</td><td></td><td>0</td><td>0</td><td>»</td><td>^D</td><td>¹¹</td><td>s</td><td>r</td><td>V</td><td>I)</td><td>n</td><td>l&gt;</td><td>I&gt;</td><td>1)</td><td>n</td><td>n</td><td>Si</td><td>r |-::ί</td>

<td>dei</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td>uK</td><td>u Ren</td><td></td><td></td><td> qi:X</td><td>Device</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>β</td><td>1</td><td>2</td><td>Λ</td><td>4</td><td>5</td><td>t.</td><td>7</td><td>8</td><td></td><td>0</td><td>1</td><td></td><td></td><td>4</td><td>5</td><td>b</td><td>7</td><td>K</td><td></td><td>0</td><td></td><td>2</td>

<td>£NR</td><td></td><td></td><td>X2</td><td></td><td></td><td></td><td></td><td></td><td>N</td><td></td><td></td><td></td><td>R</td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td>Match 5</td><td>0</td><td>s</td><td></td><td>ο</td><td>0</td><td>h</td><td>π</td><td>D</td><td>1)</td><td>I&gt;</td><td>Ding</td><td>s</td><td></td><td>□</td><td>I)</td><td>Gate</td><td>Gate</td><td>D</td><td>D</td><td></td><td>D</td><td>s</td><td>V</td>

<td>&lt;lc chess</td><td></td><td>::</td><td></td><td></td><td></td><td></td><td></td><td></td><td>dcis</td><td></td><td></td><td></td><td>% Caustic</td><td></td><td></td><td></td><td></td><td></td><td>.：:.</td><td></td><td></td><td></td><td></td>

<td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td><td></td>

<td></td><td>(1</td><td></td><td>2</td><td>Λ</td><td>4</td><td>5</td><td>(f</td><td>7</td><td>K</td><td>g</td><td>ί!</td><td>I</td><td>2</td><td>Λ</td><td>4</td><td>5</td><td></td><td>7</td><td>s</td><td>0</td><td>0</td><td>1</td><td>2</td>

<td>X.</td><td></td><td></td><td>X2</td><td>\support</td><td>X Xin</td><td></td><td>Chi 2</td><td>strict</td><td>XX</td><td>X3</td><td>κ-4</td><td>N</td><td></td><td>Rf</td><td>re</td><td>\X</td><td></td><td>R4</td><td>K:i;</td><td></td><td></td><td></td><td>R Erfeng T|</td>

<td>Configure ft</td><td>1&gt;</td><td></td><td>ί^:</td><td>1-</td><td></td><td>t&gt;</td><td>s</td><td>t</td><td>Ϊ</td><td>0</td><td>D</td><td>s</td><td>V</td><td>Γ</td><td>r</td><td>n</td><td>shock</td><td>1-</td><td></td><td>.0</td><td>D</td><td>s</td><td>I</td>

<td>&lt;1&lt;r/r</td><td>di)</td><td>d</td><td></td><td></td><td></td><td>dc5</td><td>d6</td><td>c</td><td>cMif</td><td>d&lt;</td><td>d1ϊ</td><td>d1</td><td>Vq</td><td>cqi: right</td><td>cq order M</td><td>d1-</td><td>dcl6</td><td>Mti</td><td colspan="2">V | dM"1 9</td><td>&lt;1r'r-display</td><td>d</td><td>c Electricity 1: 5</td>

[0141] The data in Table 4 is analyzed as follows in order to determine the number of sets of RF beams 902 that can be supported in a specific TDD U/D configuration 1002, and the subframes in which the same RF beam pattern 902 may need to be used. The results in Table 5 constitute the main constraints for the LTE TDD system using the RF beam scanning antenna system in this disclosure. The constraint for the corresponding LTE FDD system is to repeat the RF beam pattern 902 every 4 milliseconds.

[0142] Table 5: Number of RF beam sets and subframes requiring the same RF beam coverage in the LTE TDD system

<td>TOI) configuration</td><td>analysis</td><td>The RF beam may need to be the same as the set of f-frames listed</td>

<td rowspan="2">0</td><td>The HARQ constraint shows that the energy lags of f frames 3 and 4 must have the same RF beam 902 "Ii, and IL·near frame 9 can require the same KF beam 9 (»coverage ο W?T). The constraints show that frame , protection if can be covered by the same RF beam 9 and frame f is also covered by the same RF beam 9 and 9 nffl Yu Toys#1. Subframe 2 and sub 7 are not covered. Regarding beam-forming beam fishing *Because the IKI command sent in the QC1 report frame in the Natuo subframe is thought to be sent in the sf frame data can always be sent in the signal of the cell range, and does not affect the RF beam set The number of houses imposes constraints. As described in the text, beamforming technology is required: the requirement is that Ying frame well is not used to send DEF commands, or fill fifi ^ UE position Η to receive COI measurement</td><td rowspan="2">&lt;0,3»4, 7) (5, 9, 8, 2)₅Wft, the two sets of RF beams such as 2 ^rOJ j'On can be used in frame teams 3, 4 and 7 and beam 9 (0 of ... sets; time is in subframes 2, 5.8 and The RF beam WK generated in 9...: The set can not be used as a fat beam M2 in the sub-frame reading, and the gate frames 1 and 6 are Sf frames. In the tool, the same sub-frame of the RF beam #2 may need to be used. The auspicious swap set is (0, 3, 4, 2) (5, 9, 87). In Mo, the two f-frames of the compatible set of RF beam patterns can be created. Yes, UU(0. 3/4, 2, 7) W (5; B, 9); (0, 3, 4) and (5, 8, 9, 2, 7).</td>

<td>The requirement is to limit the number of RE beam 9(«sets used by Ding to determine the position of the frame to 2*frame 2 and? So it may need to be included in these 1W beam 2 sets...) Because of the rule of the apricot, the two pieces of different fCQi»rtW|-&lt;M returned are broken, and the comfort of the loyal player cannot pass through the [Described in this article for the 1W wave 902 application LIE 104» line Positioning method to dragon position </td>

<td>1</td><td>HARQRS does not give constraints on RF beamforming, because the retransmission is the same as the original transmission. The GQ1 constraint shows that the sub-frame can have the same RF wave *902«&gt;, and Also subframes 4 and 8 need to have the same RF beam Zhe 2 coverage_eBecause the Q-port report may need to be able to identify any beam 902-bit 71 «1« l!E, W. Therefore, no more than two RF beams can be set. The remaining subframes may need to be included in the CQI report of the return network. In the two sub-frames of the sub-frame, any "collection" ridicules the right single of the single you in the suit shows the song-a small example</td><td>3, 9, 0, 5) (4, 8, 2, 7) ΜΛ. Two sets of RF beam 9G2 "i use γ-® «κ can be used in subframes (1, 3, Rong and *&gt; Quasi-to-KF Bodong 902... set; can coax Xie Yue, 4, 7#8 into the second set of RF beams such as 2. In subframe query 6, not half of RF beams 902, /frame 1#6&gt;S f frame. As mentioned above, the alternative two sets of KF beam 902 can be used to generate different sets of two sets 1 by playing different allocations of Li, 2, and 7 Ge Zi Xie "1, 2, 5»? Divided into two sets of KF beam pattern contains 30 different ways, of which..., one way is shown in the | dagger surface*</td>

<td>2</td><td>HARQMS4&lt; gives constraints on the RF beamforming set, because 31 transmissions live in the same subframe as the original transmission. CQIM constrains the use of two RF beam patterns, because COIJUEW frames are awkward. "These two frames can be used for any RF beam 902 (*» in the llE»ff» bit 3 QCT relationship shows that subframes 2 and 8 can be used for the RF beam 2 Square|«] map, and M3, 7 can be married A has the same RF beam 902 pattern = the remaining r-ttO. 4. Rolling 9 inches can be included in the two collections of the r frame ...In a set rule. /ET ...an example is shown in the table unit"</td><td>(2.8» 0,4K(X?_f 5,9) Two sets of this * HF beam 2 can be used for configuration 2 = can be in subframes 0, 2.4 and &amp; 4-&lt;RF1 Cambodian 2...-a set of pieces; the set is in ftt3 5. The first of the generation of F beam 902 in 7 and 9: Set. In subframe 1 and fancy RF beam 902, -fttlflift is £0 frame" As mentioned above, KF beam "« is an alternative to The first song on the set number 1 shows the different assignments of sub-frames 4, 5W9 to the two sets of 1 tones to generate the four frame 0, 4, 5, and 9 divided into two HF beam patterns. There are 30 different ways to store houses, one of which is shown in 1: Imperial.</td>

<td>3</td><td>HARQ asks the JS car to give an agreement to the KF beamforming group. The retransmission occurs in the same subframe as the original transmission. There is a CQI report &amp; its return to the ί order subframe. Frame-associated" to use two sets of KF beam% 2, where CQI report constraints 2, 8 have the same RF ««902 pattern, Menluo has the same XF beam 2 pattern, and , OJWfffl is the same as the RF wave Kangjia 2 pattern. The other sub-frames 5 and 6.7 can be used in the set of n rj=«. Therefore, the sub-frames are used in the set of frames. Other combinations of 1 As long as (2, 8) stays at -..., (3, 9) keeps [stay together, and hate (4, 0) «IWI: together.</td><td>(0,4,6X2,83)(33,7); Therefore, RF&amp;MC902: three sets are used to configure a set of RF beams 02 can be generated in subframes 0, 4, and 6; f frame 2, the 3Γ of the quasi-fatty liquid beam sha2 in the shochu: collection; the third collection of the ting in frames 3, 7 and 9·|'Φ: &lt;The third group of the ΚΡ beam 902. A f«1 sub-frame) in 1iJ«RF Wavebook 2* As mentioned above* The three sets of alternatives of KF Polk 902 are shown in different directions from the dagger plane: a set of allocators Frame rolling "6 and come to live into. There are 39 different ways to divide each frame 5, 6, and 7 into the direction of the RF wave. There are 39 different ways in the Umbrella Collection, English and Chinese... The ways are in Ι-.ιίιί; to show the universe.</td>

<td>4</td><td>The H ARQ that is transmitted urgently in the uplink does not affect the formation of the KF wave cam in the same sub-frame of the vehicle. Wl«J always because X2 is urgently transmitted in sub-frame 2 (1) The important time),&gt;II.X3£ In frame 3 Shenzhuang (when required), when there are only two uplink frames, T\ to the MgiiW of the RF beam pattern is set because the two uplink frames on the right are transmitted in the frame. ί·Ίwcoiffl may be required to say all other (I)). The eclipse uses J'-Ή-γΜ» to transmit OWE dci/CQI relationship indicating that sub-frame gas 2 is required to have a good beam 2 Directional pattern, parallel to L·subframe atmosphere 9 possible ®&lt;JWi+flkJ RF beam laying 2 pattern. Wita sub-frame team 4, the rolling river can need to be collected with any pair in order to map the remaining f-frames to these two good beam sha2 patterns. On the right side of the farm, you are in the car out of the car-an exception (</td><td>C 2,8,04,6) (3,9,5,7); Tao this, the two collection towns of RF Jidong purchased 2 are used for matching Η4_Ο nj-iM/nf W(l, 2, 4, 6 car hate Niu. into a set of RF waves such as 2; town live subframes 3, 5, 7 and 9 apply to generate RF beam Μ». No.: Set. [In subframe 1 cs-fii) Li Xiaozhu[ into KF Bodong 902" As mentioned above, the alternative blue sets of IIF beams 2 should be shown in different directions by passing and BU: Two sets are allocated sub-frames 0, 4. Qi 6#7 to generate "there are five frames 0, 4, 5, 6. divided into two sets of RF wave beam pattern; Way, of which...· kinds of ways are shown above</td>

<td>5</td><td>Because there is only one link "frame" in the configuration $, because the CQ code passed in the frame (2&gt;) is the position where the HE can be captured most *goldly in the WilK field 712 Where.W, the set of MWRF beam 2 in this configuration contains, and 1L the entire cell a iS constant area 712 energy; it is recommended to be set by the roll of the beam</td><td>(2, 8, 0, 5, 4, ?, 6, 7, 9): Therefore, the ... sets of RF Bodon 2 can be configured with the single set of random RF beams in subframe teams 2, 3, and 4. 5, 6, 7, &amp; and Xizhong multiply complex. No RF beam is generated in λ mi 902</td>

<td>6</td><td>It is used for uplink turn transmission F and each pair of f frames make j IW114's RF beam 902 pattern; (2, 3), (3, 4), (4, 7), (7, 8), (2, 8 ) * '^l1DCIfheNB102 when sending * subframe; lUAaCQI11eNB 102XW, the corresponding fwm beam is F each for the frame use and the same RF wave form as 2 direction M_； (9,4), (O,7h (5,2h RF wave «902 directional pattern constraints across all sub-frequency overlap {except for Sf sail, which is not used to send I'-MUE for positioning in the public content MDCI)</td><td>(0,234,5,7,8,9)_;Therefore, RF Jidongru 2's... a single collection with T-RK6. Division beam intensity 2 is in frames 3, 4, 5.7, and ^9. No RF beam is generated in csmio ψ 902"</td>

[0143] Positioning and tracking UEs in the RF beams of a periodic scanning RF beam system This disclosure describes aspects for positioning and tracking users in conjunction with RF beamforming technology. A particular beamforming technique generates N RF beams 902 in parallel, for example in each 1 millisecond interval. The N RF beams 902 cover N sub-areas of the total coverage area 712 of the LTE cell. The coverage area 712 is determined by the LTE cell using the same total transmit power, but it does not use beamforming technology. In the next 1 millisecond interval, another set of N RF beams 902 are generated in order to cover a different set of N sub-areas. This process may be repeated m times in an LTE frequency division duplex (FDD) system, until, for example, after 4 milliseconds (where m=4), the entire cell coverage area 712 has been covered by 4*N RF beams 902. For example, let N=4, therefore, 16 RF beams 902 sub-areas cover the entire cell area 712 in the FDD system. See Figure 9o

[0144] The RF beamforming technique described in FIG. 9 does not focus the RF beam 902 on a specific user equipment (UE 104) as in other beamforming methods. Instead, the RF beam 902 is continuously generated every 1 millisecond, Among them, the same RF beam 902 sub-area is covered every 4 milliseconds in the FDD system. In Fig. 9, four sets of non-adjacent sub-regions are illuminated (for transmission) and focused (for reception) over the course of four consecutive 1 millisecond time intervals.

[0145] In an LTE wireless system, downlink transmission may be scheduled by software called a scheduler in the base station 102. The scheduler can also grant grants for uplink transmission. In this way, the bandwidth available via the LTE air interface is allocated to different users at different times in a manner determined by the scheduler.

[0146] When the RF beamforming technique summarized in FIG. 9 is used, it is important for the scheduler to know the current location of each UE. Therefore, in a specific 1 millisecond interval, it can only be used in the 1 millisecond interval. Those UEs 104 in one of the four positions that will be focused by the RF subsystem beamforming are authorized for uplink transmission. Likewise, the scheduler may need to schedule downlink transmissions only to those UEs 104 that are known to be located in one of the four RF beam subareas 902 to be illuminated by the RF subsystem beamforming operation.

[0147] Therefore, in order to be able to effectively use the RF beamforming technology, it may be important for the scheduler to know which RF beam 902 covers the current UE location. There are two aspects to the problem that needs to be solved. One aspect is to determine when UE 104

When accessing a cell for the first time (ie, during the initial attachment to the LTE system, or during a handover from a neighboring cell to the cell, or during when the UE 104 leaves the idle state and re-establishes its connection with the current cell ), the RF beam 902 covering the location of the UE 104. The second aspect of the problem is that the UE 104 is tracked when the user moves across the sub-area covered by the RF beam 902 generated by the RF subsystem of the cell. In order to provide priority for the development of this technology, and to provide the teaching needed to locate and track the UE 104 for use with RF beamforming technology, this disclosure provides information that discloses the technology used to deal with these two aspects .

[0148] In an example, in an LTE time division duplex (TDD) system, ten 1 millisecond subframes of each LTE frame 1002 are divided into a set of subframes for downlink transmission and a set of subframes for uplink transmission. The collection of transmitted subframes. There are 7 different configurations that divide these subframes into k uplink subframes and m downlink subframes. See Figure 10. (The subframes marked "S" are not used in the UE positioning algorithm given in this article.) When the RF beamforming technology is used in the LTE TDD system, when the RF beam 902 covers the location of the UE 104, the UE 104 needs to be scheduled for Uplink and downlink transmission in subframes (i.e., 1 millisecond interval). Therefore, the need to determine the location of the UE 104 in the RF beam 902 and the need to track the location of the UE 104 across the RF beam 902 are exactly the same as those in the LTE FDD system. However, in a TDD system, for any of the uplink/downlink configurations selected for the TDD system, the RF beam 902 pattern repeats every 10 milliseconds, instead of designing the RF beam in the FDD system 902 has an RF beam 902 pattern that repeats every 4 milliseconds. See Table 6 for an example list of subframes in each TDD configuration 1002 in which the RF beam 902 pattern may be the same. As described herein, for each TDD U/D configuration, there may be Assign several different acceptable modes of operation for the RF beam pattern. Therefore, the number of sets of subframes indicates the number of different sets of 4-beam patterns that can be maintained in a given TDD configuration 1002.

[0149] Table 6: The number of sets of RF beam patterns supported in each TDD configuration

<td>TDD U/D configuration</td><td>A collection of sub-frames with exactly the same beam pattern</td>

<td>0</td><td>(0, 3, 4, 7) and (5, 9, &amp; 2): Therefore, the U/D configuration 1002 supports two sets of 4-beam beam pattern respectively. No RF beam 902 is generated in subframe 1 or 6.</td>

<td>1</td><td>(3, 9, 0, 5) and (4, &amp; 2, 7): Therefore, the U/D configuration 1002 supports two sets of 4-beam beam patterns respectively. No RF beam 902 is generated in subframe 1 or 6.</td>

<td>2</td><td>(2, &amp; 0, 4) and (3, 5, 7, 9): Therefore, the U/D configuration 1002 supports two sets of 4-beam beam pattern respectively. No RF beam 902 is generated in subframe 1 or 6.</td>

<td>3</td><td>(0, 4, 6), (2, 5, 8) and (3, 7, 9): Therefore, the U/D configuration 1002 supports three sets of 4-beam beam pattern respectively. No RF beam 902 is generated in subframe 1.</td>

<td>4</td><td>(0, 2, 4, 6, 8) and (3, 5, 7, 9): Therefore, the configuration 1002 supports two sets of 4-beam beam patterns respectively. No RF beam 902 is generated in subframe 1.</td>

<td>5</td><td>(0, 2, 3, 4, 5, 6, 7, 8, 9): Therefore, the configuration 1002 supports one 4-beam pattern. No RF beam 902 is generated in subframe 1.</td>

<td>6</td><td>(0, 2, 3, 4, 5, 7, 8, 9): Therefore, the configuration 1002 supports one 4-beam pattern. No RF beam 902 is generated in subframe 1 or 6.</td>

[0150] In order to optimize the downlink transmission by adjusting the modulation and coding scheme (MCS), the mobile device 104 may need to use the physical uplink control channel (PUCCH) or the physical uplink shared channel (PUSCH). The channel quality indicator (CQI) is sent on. CQI is a 4-bit result indicating the measured value. The measurement can be on the entire frequency range of the cell bandwidth, or on a certain subset of the frequency range. The entire frequency range is divided into a set of physical resource blocks, and in order to perform CQI measurement on a frequency range smaller than the total RF bandwidth allocated to the cell, a set of these physical resource blocks is defined as a "subband". In the LTE system, the subband CQI measurement can be performed aperiodically, where the report is sent via the PUSCH. Periodic wideband CQI measurement can be performed by sending a report to the eNB 102 using PUCCH.

[0151] When the eNB 102 wants the UE 104 to perform channel quality measurement and return a CQI measurement value, it sends command information called downlink command information (DCI) to the UE 104. In the FDD system, if the DCI is sent in subframe n, the QCI measurement is reported by UE 104 in subframe (n+4). In a TDD system, the constrained DCI command will be sent by the eNB 102 in a subset of subframes used for downlink transmission. The UE 104 CQI measurement report returns to the eNB 102 after k subframes, where k depends on the TDD uplink/downlink configuration 1002, and where (n+k) is configured for uplink transmission in the TDD system Subframe.

[0152] CQI-based algorithm for finding UE location after random access, handover or service request

The UE 104 in the FDD system determines the initial position of the UE 104. The eNB 102 system can learn the existence of the UE 104 in its cell coverage area 712 through a random access (RA) process, a handover process, or a service request process. In the above process, The UE 104 becomes connected via a cell. In order to allow the beamforming method to be used for the UE 104, it may be necessary to determine the current UE 104 position in one of the 16 RF beam 902 positions in the FDD system. The following algorithm uses CQI measurements to determine the location of the UE 104 within the RF beam 902. If the RF environment includes major multipath components, then CQI measurement can be used to determine the RF beam for downlink transmission to the UE, and SRS measurement (disclosed below) can be used to determine the uplink transmission for the UE RF beam.

[0153] In an embodiment, after the eNB 102 sends the RA authorization to the UE 104, if there is no contention, the eNB 102 MAC (Media Access Control) software can be used in 4 consecutive subframes (ie, subframes n, (n) +1), (n+2), and (n+3)) in each subframe to send a command to make the UE 104 provide an aperiodic report of the subband CQI value (if there is contention, then the contention The command is sent after the resolution, that is, after the eNB 102 sends the contention resolution message on the PDSCH±). The eNB 102 MAC and PHY (physical layer) software can be arranged for a selected set of measurement subbands in each signal in the transmission beam signal to be included in each measurement subframe in the measurement subframe, so as to ensure Each transmit beam focuses the transmit energy from the subband on the illuminated beam area 902; if the UE 104 is in the illuminated beam area 902, it can perform the required CQI measurement for the configured subband. These aperiodic measurements are returned via the UE 104 PUSCH. If the measurement is performed in subframe n, the report is returned in subframe (n+4) in the FDD system.

[0154] The eNB 102 PHY and MAC software report the four received beam streams in each of the subframe intervals (n+4), (n+5), (n+6), and (n+7) Look for UE PUSCH measurement in each receive beam stream. The receiving beam 902 covers a non-adjacent area (see FIG. 9). This means that the UE 104 measurement report should normally only be received in one subframe, and in only one received beam 902 signal for that subframe. However, it is possible for the eNB 102 to receive the measurement report in more than one reporting subframe, in one of the receive beams 902 data stream in each of those subframes. This can happen if the UE 104 is on the boundary between the RF beam 902 location areas. In this case, the MAC can choose the measurement with the best CQI value (or if they are the same, choose one of these measurements). MAC can

The subframe and the received beam 902 signal containing the UE 104 CQI measurement report are recorded to determine which of the 16 beam 902 positions contains the UE 104. The location is recorded as the current UE 104 location (ie, when the eNB 102 sends a user plane transmission to the UE 104, or when the UE 104 is scheduled for uplink transmission in a non-multipath RF environment, the eNB 102 can use position).

[0155] The UE initial position determination in the TDD system is similar to the method used in the FDD system, which can be used to determine the UE 104 position in the RF beam 902 when the UE 104 accesses the TDD system for the first time. Depending on the TDD U/D configuration 1002 (see Figure 10), after the eNB 102 sends the RA authorization to the UE, if there is no contention, or after the contention is resolved in the case of RA contention, the eNB 102 MAC software can Different RF beam patterns 902 are generated in the specific TDD U/D configuration 1002, and the DCI command can be sent in the first upcoming subframe in each of the set of subframes sent therein. See Table 4o. The command causes the UE 104 to perform aperiodic reporting of the subband CQI measurement. The eNB 102 MAC and PHY may be arranged for a selected set of measurement subbands in each of the transmission beams 902 to be included in the subframe in which the DCI command is transmitted to the UE 104. This method ensures that each transmit beam 902 focuses the transmit energy from the subband on the illuminated beam area 902; if the UE 104 is in the illuminated beam 902 area, then it can perform the required CQI measurement for the configured subband . (S subframes may not be used to transmit for the UE in the RF beam region 902 104 performs these commands for aperiodic channel quality measurement for positioning purposes. ).

[0156] These aperiodic measurements are returned via UE PUSCH. Depending on the TDD U/D configuration 1002, the subframes that can be used to transmit DCI for aperiodic measurement are restricted. See Figure 10. Therefore, if the measurement is performed in subframe n, the report is returned in subframe (n+k) in a TDD system using normal hybrid ARQ operation. TS 36.213 a40 specifies the values that η can take and the corresponding values of k. As an example, assume that the UE 104 accesses the cell in subframe 2 and the TDD U/D configuration 1002 being used is configuration 0. Using the values in Table 6 and the configuration 0 listed in FIG. 10, the eNB 102 MAC sends a DCI command in subframe 5 and receives a report in subframe 9. The eNB 102 MAC also sends a DCI command in subframe 0 of the next LTE frame, and receives a corresponding CQI measurement report in subframe 4 of the LTE frame.

[0157] The eNB 102 PHY and MAC look for UE 104 PUSCH measurements in each of the four receive beam 902 streams in each of the reporting subframe intervals (which depends on the TDD U/D configuration 1002). Where possible (in the case of configuration 5 or 6, only one set of RF beam 902 is repeated in each U or D subframe, therefore, some areas in the RE beam 902 area may need to be adjacent to each other), The receiving beam 902 covers non-adjacent areas. This means that the UE 104 measurement report should normally only be received in one subframe, and in only one received beam 902 signal for that subframe. However, it is possible for the eNB 102 to receive measurement reports in more than one reporting subframe, and/or in more than one receive beam 902 data stream in each of those subframes. This can happen if the UE 104 is on the boundary between the RF location areas 902. In this case, the MAC can select the measurement with the best CQI value (or if they are the same, select one of these measurements; and/or if the report with the same best CQI value is in more than one receiving RF beam If the signal is received, select one of the signals of the RF beam 902). The MAC may record the subframe and the received beam 902 signal containing the UE 104 CQI measurement report in order to determine the RF beam 902 Which of the locations contains the UE 104. This location is recorded as the current UE 104 location (ie, when the eNB 102 sends a user plane transmission to the UE 104; or when the RF environment is not affected by multipath transmission when the UE 104 is scheduled for uplink transmission, the eNB 102 Available locations).

[0158] CQI-based algorithm for tracking UE location

UE location tracking in the FDD system Once the location of the UE 104 is determined after the random access process, handover process, or service request process is completed, in the case where the UE 104 moves to another RF beam 902 location in the same cell coverage area 712 , UE 104 needs to be tracked. The following algorithm uses the CQI report to track the UE 104 across the set of RF beam 902 positions that overlap the cell coverage area 712 in the FDD system.

[0159] The value K (some number of several hundreds of milliseconds, for example, K=20 for 2000 millisecond intervals) may be provided for periodic checking of the location of the UE 104. The eNB 102 MAC can execute a CQI-based UE 104 location determination algorithm similar to the algorithm specified above for the initial access situation of the FDD cell. Therefore, a command can be sent to the UE 104 to perform aperiodic CQI reporting in four consecutive subframes n, (n+1), (n+2), and (n+3). Therefore, the UE 104 measurement report is sent via the PUSCH in subframes (n+4), (n+5), (n+6), and (n+7). As in the case where the location of the UE 104 is determined when the random access procedure is completed, the eNB 102 MAC ensures that the subband physical resource block (PRB) selected for measurement is included in the transmission beam signal in each measurement subframe in the measurement subframe Of each transmitted beam signal. The eNB 102 PHY and MAC receive each of the four receive beams 902 streams in each of the reporting subframe intervals (n+4), (n+5), (n+6), and (n+7) Look for the UE 104 PUSCH measurement report in the beam stream. The receiving beam 902 covers non-adjacent areas. This means that the UE 104 measurement report should normally only be received in one subframe, and only one received beam 902 signal in that subframe in. The MAC may record the subframe and the received beam signal to determine which of the 16 beam positions 902 contains the UE.

[0160] Because the RF beams in any subframe cover non-adjacent areas, the eNB 102 MAC should resume measurement from only one receive beam 902 flow in a given reporting subframe. However, if the UE 104 is on the boundary between two or more RF beam 902 positions, then the eNB 102 MAC can be used in each of the 2, 3 measurement report subframes, or in all 4 measurement report subframes. The measurement report is received in the frame. The MAC records the UE 104 location or some locations (up to four) in the temporary data set allocated to the UE 104. If the current UE 104 location is not among those determined via the measurement report just received, and if more than one UE location has been determined, then the MAC selects the UE 104 location associated with the best return CQI value and updates the current location accordingly. Location of UE 104. If the current UE 104 location is among those just reported, or if it is the only location reported, then the current UE 104 location is not updated at that moment.

[0161] Regardless of whether the current UE 104 location is updated at that moment, the aperiodic CQI report is repeated at H millisecond intervals (20 millisecond intervals of the provided number, for example, H=25 for aperiodic measurements performed every 500 ms) Until a single UE 104 location is determined, and it does not change during M (provided value) consecutive H*20 millisecond intervals. If the UE 104 check interval of the K millisecond period occurs before the UE 104 position determined according to the report that remains fixed in M consecutive reports, then the K millisecond periodic location check is not performed for the UE 104, and the UE 104 is fixed for M consecutive UEs. 104 The checking of position determination continues at a rate of H*20 milliseconds.

[0162] If the location of the UE 104 is determined to remain fixed in M consecutive aperiodic reporting instances, then if it changes, the location information of the UE 104 is updated, the operation of the H*20 milliseconds based on the CQI location check process is cancelled, and the operation for the CQI location check process is restarted. Operation of UE 104 location check procedure in K milliseconds of UE 104. This repetition of the CQI measurement process for 4 consecutive subframes deals with the situation where the UE 104 is located on the boundary of different coverage areas irradiated by the RF beam 902, or fluctuates between the positions of the RF beam 902. (Note: The subband CQI measurement interval is 1 subframe, that is, the subframe in which the UE 104 receives a command to perform aperiodic CQI measurement.).

[0163] UE location tracking in TDD system

A method similar to that used for the FDD system can be used to track the UE 104 position in the RF beam 902 when the UE 104 moves across the cell coverage area 712 of the TDD system.

[0164] The value K (some number of several hundred milliseconds, for example, K=20 for 2000 millisecond intervals) is provided for periodic checking of the location of the UE 104. The eNB 102 MAC may execute a CQI-based UE 104 location determination algorithm similar to the algorithm specified above for the initial access situation of the TDD cell. Therefore, a command is sent to the UE 104 to perform aperiodic CQI reporting in non-S subframes in which DCI commands can be sent, where a single subframe is selected from a different set of subframe sets in which the RF beam pattern is generated In order to initiate aperiodic CQI measurement, the S subframe is not used for this purpose. The number of DCI commands sent is equal to the number of sets of RF beams 902 generated in a particular TDD U/D configuration 1002 (see Table 6). Therefore, the UE 104 measurement report is sent via the PUSCH in the subframe used for the specific TDD configuration 1002 in effect for the cell. The receiving RF beam area 902 covered in a given subframe in the TDD system may or may not be non-adjacent. This means that the UE 104 measurement report should normally only be received in one subframe, and in only one received beam 902 signal in that subframe. However, it is possible for the eNB 102 to receive measurement reports in more than one reporting subframe, and/or in more than one receive beam 902 data stream in each of those subframes. If report Only in one subframe and only in one received RF beam 902 signal, then the MAC can record the subframe and the received RF beam 902 signal to determine which RF beam 902 position contains the UE 104.

[0165] However, if the UE 104 is on the boundary between two or more RF beam 902 positions, the eNB 102 MAC may be in each measurement report subframe and/or in the report subframe. The measurement report is received in more than one received RF beam 902 signal in one or more reporting subframes in the frame. The MAC records the UE 104 location or some locations in the temporary data set allocated to the UE 104. If the current UE 104 location is not among those determined via the measurement report just received, and if more than one UE location has been determined, then the MAC selects the UE 104 location associated with the best return CQI value and updates the current location accordingly. Location of UE 104. If the current UE 104 location is among those just reported, or if it is the only location reported, then the current UE 104 location is not updated at that moment.

[0166] Regardless of whether the current UE 104 position is updated at that moment, the aperiodic CQI report is repeated at H millisecond intervals (the provided number of 20 millisecond intervals, for example, H=25 for aperiodic measurements performed every 500 ms) Until a single UE 104 location is determined, and it does not change during M (provided value) consecutive H*20 millisecond intervals. If the UE 104 check interval of the K millisecond period occurs before the UE 104 position determined according to the report that remains fixed in M consecutive reports, then the K millisecond periodic location check is not performed for the UE 104, and the UE 104 is fixed for M consecutive UEs. 104 The checking of position determination continues at a rate of H*20 milliseconds.

[0167] If the location of the UE 104 is determined to remain fixed in M consecutive aperiodic reporting instances, then if it changes, the location information of the UE 104 is updated, the operation of the H*20 millisecond based on the CQI location check process is cancelled, and the operation for the CQI location check process is restarted. Operation of UE 104 location check procedure in K milliseconds of UE 104. This repetition of the CQI measurement process deals with the situation where the UE 104 is located on the boundary of different coverage areas irradiated by the RF beam 902, or swings between the positions of the RF beam 902. (Note: The subband CQI measurement interval is 1 subframe, that is, the subframe in which the UE 104 receives a command to perform aperiodic CQI measurement.).

[0168] Sounding Reference Signal (SRS) in LTE system

The LTE standard defines an optional sounding reference signal (SRS) in the uplink direction_OIt is sent by the UE 104 using a known sequence and using a set of PRBs allocated by the eNB 102 MAC software. When the UE 104 is not transmitting user data and is usually used to estimate the uplink channel condition, the SRS can be scheduled. eNB 102 MAC can use as few as 2 sub

The period of the frame is used to schedule the periodic transmission of SRS. The eNB 102 MAC can also schedule a single aperiodic SRS transmission. The SRS is detected at the eNB 102 and processed by the PHY layer. The PHY layer reports the received SRS signal-to-noise ratio level of each resource block allocated for the SRS to the MAC layer. Refer to Femto Forum, document number FF_Tech_003_vl. 11 104 pages, 2010.

[0169] SRS-based algorithm for finding UE location after random access, handover, or after service request

UE initial location determination in FDD systems The UE 104 location determination algorithm used in FDD systems can operate in the same manner as when CQI reporting is used, except instead of having the eNB 102 MAC order the UE 104 to perform CQI in four consecutive subframes Instead, it commands the UE 104 to send SRS in each of four consecutive subframes. These are aperiodic SRS transmissions. Each SRS transmission is sent with a subframe offset defined by cell-specific parameters for all UEs 104. The SRS transmission received at the eNB 102 may be used in a similar manner to the CQI measurement used at the eNB 102 to determine the RF beam 902 that covers the location of the UE 104.

[0170] UE initial location determination in a TDD system The UE 104 location determination algorithm used in a TDD system can operate in the same way as when using CQI reporting, except instead of having the eNB 102 MAC send a DCI command to make the UE 104 perform CQI measurement , But the DCI command is to send SRS transmission. These commands are generated in different RF beam patterns 902 for a specific TDD U/D configuration 1002, and DCI commands can be sent in the first upcoming subframe of each subframe in the set of subframes in which it is sent Sent. See Table 4. These commands cause the UE 104 to send aperiodic SRS transmissions in the PRB specified in the DCI command and in the U subframe corresponding to the subframe in which the DCI command is received. Each SRS is returned with a subframe offset defined by cell-specific parameters for all UEs 104. The SRS transmission received at the eNB 102 may be used in a similar manner to the CQI measurement used at the eNB 102 to determine the RF beam 902 that covers the location of the UE 104.

[0171] SRS-based algorithm for tracking UE location

UE location tracking in FDD systems The UE 104 location tracking algorithm for FDD systems can operate in the same way as when using CQI reporting, except instead of having the eNB 102 MAC order the UE 104 to perform CQI measurements in four consecutive subframes Instead, it commands the UE 104 to send SRSo in each of the four consecutive subframes. These commands and reports are generated according to the period value defined in the CQI-based tracking process outlined in this article for the FDD system. These are aperiodic SRS reports. Each SRS report is returned with a subframe offset defined by cell-specific parameters for all UEs 104. The SRS transmission received at the eNB 102 can track the UE 104 when the UE 104 moves from one RF beam 902 covering the location of the UE 104 to another RF beam 902 covering the location of the UE 104 in a similar manner as the CQI measurement used at the eNB 102. .

[0172] UE location tracking in a TDD system The UE 104 location tracking algorithm used in a TDD system can operate in the same way as when using CQI reporting, except instead of causing the eNB 102 MAC to send a DCI command to make the UE 104 perform CQI measurement, Instead, DCI commands are sent for SRS transmissions. These commands are generated in different RF beam patterns 902 for a specific TDD U/D configuration 1002, and DCI commands can be sent in each subframe in the set of subframes. Sent in the first upcoming subframe. See Table 4. These commands cause the UE 104 to send aperiodic SRS transmissions in the PRB specified in the DCI command and in the U subframe corresponding to the subframe in which the DCI command is received. Each SRS is transmitted with a subframe offset defined by cell-specific parameters for all UEs 104. The SRS transmission received at the eNB 102 can track the UE 104 when the UE 104 moves from one RF beam 902 covering the location of the UE 104 to another RF beam 902 covering the location of the UE 104 in a manner similar to the CQI measurement used at the eNB 102. .

[0173] Efficient delivery of real-time event services on wireless networks

The real-time event service 1502 is a service that delivers the same information content (for example, video and audio) to multiple users at the same time. Examples include the transmission of the State of the Union address. Events need not occur in real time; the delivery of pre-recorded TV programs to users who see and hear the same content at the same time constitutes another example of this type of service. Using the architecture shown in FIG. 1 may be difficult to provide real-time event services. In a typical deployment, there may be approximately 600 eNB 102 units that provide coverage for a particular geographic area. In the case of wireless users using today's architecture (ie, FIG. 1), this may mean that each end user 104 is connected to the server 124 that transmits these data streams, and the data stream can be transmitted from the server 124 independently to other end users. Deliver to each end user. This situation is depicted in FIG. 12 for the example of 6 LTE wireless users 104 receiving service. Note: The real-time event server 124 can maintain a separate connection to each wireless user, therefore, 6 connections may be required at the real-time event server 124, as well as 6 independent packet transmissions for video and 6 independent packet transmissions for audio. Note also that the PGW 114 can handle the transmission of 6 video streams and 6 audio streams to the SGW 110 unit, and the SGW 110 unit can transmit 6 video streams and 6 audio streams to the eNB 102 unit serving each LTE user 104. Finally, each LTE eNB 102 unit transmits a separate video and audio stream to end users 104 accessing the system via the eNB. Therefore, in the example shown in FIG. 12, one eNB 102 can handle over-the-air transmission of packets for three users 104, another eNB 102 can do so for two users 104, and a third eNB 102 can target one user 104. Do it.

[0174] If the video data stream rate is 500 kbps (typical rate), and the audio stream rate is 32 kbps (typical rate), then the example in FIG. The user sends about 3 Mbps. Similarly, PGW 114 and SGW 110 can handle packet transmissions at similar rates. These rates are completely within the capabilities of today's servers and wireless network units. However, the 6 users of the service are just examples. The actual situation may have 60,000 users 104 distributed among 600 eNB 102 units watching real-time events (for example, TV programs, sports events, political events) at the same time. Using the architecture of FIG. 1, the real-time event server 124 may have to support 60,000 user connections and transmit 60,000 times 500 kbps, or 30Gbps aggregated data rate. This rate far exceeds the capacity of today's server 124. It may be necessary to use multiple servers 124 (for example, 10 servers 124) to increase the transmission rate at each server to a manageable value. Likewise, in the case of using multiple servers 124, the number of user connections at each server can be reduced to a manageable value that may be 6,000 per server. Deploy about 10 real-time event servers 124 to 60, The economics of thousands of concurrent users delivering the service may not be pleasant for the service provider.

[0175] The situation at PGW 114 cannot be resolved so easily. It is not economical to deploy a large number of PGW 114 units in a large geographic area, and it is not economical to serve 60, In the case of 000 wireless users 104, PGW 114 must handle 30 Gbps transmission, which is a difficult task, which may only be solved at the huge cost of using the architecture of Figure 1. The situation of the SGW 110 unit may not be as bad as the situation of the PGW 114 unit, because in practice there are several SGW 110 units serving a subset of the 600 eNB 102 units in the area. At the eNB 102 unit, each eNB 102 unit may have to deliver service to each of the approximately 100 users 104 connected through its cell, and therefore, each eNB 102 unit must handle 50 Mbps over the LTE air interface. Transmit. Although this value may slightly exceed the capabilities of today's LTE eNB 102 unit, it is completely within the capabilities of the APN beamforming RF system presented in FIG. 9. However, each eNB 102 may then be required to support the use of 50 Mbps on its backhaul 112 interface in order to receive packets for its users from the SGW 110 unit. At each eNB 102, solving this value can be problematic and costly. If this problem is not uniformly solved in the LTE wireless network, the user experience will be affected, depending on which eNB 102 is used to access the LTE wireless network.

[0176] According to the above, it can be seen that the provision of real-time event services (including commercial TV service delivery) to wireless users will involve a large number of connections required at the real-time event server 124, at the real-time event server 124, and at the PGW 114 unit. The required data transmission rate, and secondly, the real-time data transmission rate required at the SGW 110, and the transmission capacity used by the backhaul 112 interface to each eNB 102 unit.

[0177] An architecture for efficient and economical real-time event delivery. If the concept of a distributed publish/subscribe (P/S) architecture is introduced into the APN wireless network to enhance the capabilities of the optimization servers 202 and 204, it can solve the problem with the LTE network. Issues related to the economic delivery of real-time event services. FIG. 13 shows the architecture of deploying a publish/subscribe agent 1304 on a collection of computing nodes 1302. One or more P/S agents 1304 may be deployed on each computing node 1302, depending on the number of entities expected to be connected at each computing node 1302. Each communication entity (ie, user equipment or server) can be connected to a single P/S agent 1304 in order to receive the services of the P/S agent architecture. In this architecture, the endpoints may not be directly connected to each other. Packets that include specific data streams can be identified by tags called topics. Groups within a topic stream can be referred to as events. In FIG. 13, an entity 1308 connected to the P/S agent 1304 at node 1 1302 can publish a packet stream, where the publisher 1308 inserts a stream topic into each packet. At the same time, 10 other users 1310 (ie, end-user devices, or programs running on other computers) may have subscribed to the topic before. These users 1310 can straddle the three calculations shown in Figure 13 The nodes 1302 are distributed, in each case, connected to the P/S agent 1304 running on its attached node 1302.

[0178] The P/S proxy 1304 network is designed to distribute published packets to all destinations that have subscribed to a given topic. P/S agent 1 1304 knows to assign packets to P/S agent 2 1304 in its own node 1 1302, and also knows to directly connect to the two entities that are directly connected to P/S agent 1 1304 that have subscribed to the published topic 1310 allocation group. P/S agent 2 1304 knows to distribute packets to P/S agent 3 1304 of node 2 1302 ± and P/S agent 5 1304 of node 3 1302 ±, and also knows that it has been connected directly to P/S agent 2 1304. The two entities 1310 that have subscribed to the published topic assign groups. P/S agent 5 1304 knows to assign packets to its three directly connected entities 1310 that have subscribed to the published topic. P/S agent 3 1304 knows to assign packets to P/S agent 4 1304 and to its two directly connected entities 1310 that have subscribed to the published topic. Finally, P/S agent 4 1304 knows to assign packets to a single directly connected entity 1310 that has subscribed to the published topic. The publisher sends a group, And the P/S proxy network is responsible for packet replication whenever needed. Each packet is replicated only to the extent necessary at each P/S agent 1304. Therefore, the P/S proxy network distributes the task of copying packets in an efficient manner.

[0179] A distributed set of publish/subscribe (P/S) agents 1304 can be established to run on the set of optimization servers 202, 204 shown in FIG. 2, where the P/S agent 1304 can use the publish/subscribe communication paradigm to The packets are efficiently routed between the entity 1308 that publishes the packet flow and all entities 1310 that subscribe to receive packets from the flow topic. See the example deployment in Figure 14.

[0180] As previously described herein, a technique that can be used to redirect the dedicated bearer 312 of the UE 104 so that it has the local OptServereNB 308 as its end point instead of the usual SGW 110 end point is described. If each UE 104 in FIG. 14 is connected to the OptServereNB 308 associated with its serving eNB 102 via its redirected bearer, then the UE 104 can connect to the P/S proxy 1304 program running on the computer. Note that in Figure 14, the P/S proxy 1304 program can also run on a server 124 that can be located on the Internet, far away from the LTE wireless network. All P/S agents 1304 in Figure 14 can be interconnected into a logical publish/subscribe agent network infrastructure. [0181] If a server 124 remotely connected via the Internet provides a real-time event service 1502, it can be seen that the network arrangement of the P/S proxy 1304 shown in FIG. The

Problems occurred in the service. When the publish/subscribe proxy architecture is used in combination with the bearer redirection technology described earlier in this article, the results that can be obtained are shown in Figure 15.

[0182] It can now be seen that the previously discussed issues regarding the provision of real-time event services 1502 to wireless users 104 will be resolved. The entity 1502 that generates the real-time event data stream is connected to a P/S agent, and no end user 104 device is directly connected to it. The problem of maintaining 60,000 parallel user connections can be considered to be resolved into maintaining a single connection (in addition to the real-time event service, it can also be used to transmit other services). In addition, the real-time event service program 1502 generates one in each video time frame Video packet, and generate an audio packet in each audio time frame to be sent to the P/S proxy network, and it can be seen that the program is no longer needed to generate 60,000 video packets in each video time frame, and every Each audio time frame generates 60,000 audio packets to be sent to 60,000 parallel end users 104. It can be seen that: packet replication is performed when necessary by the P/S proxy network. It can be seen that one real-time event server 124 can handle transmissions to 60,000 parallel users 104, and multiple real-time event servers 124 are no longer needed. Therefore, compared with using the current wireless network architecture, the economy of delivering this service has been improved.

[0183] In addition, it can be seen that the Internet and long backhaul networks now carry one packet per video time frame and one packet per audio time frame, instead of 60,000 packets per time frame. Therefore, it can be seen that the use of long backhaul network bandwidth has been reduced from 30 Gbps to 500 kpbs, a factor of 60,000.

[0184] It can be seen that because of the existence of the OptServerPGW 304 and OptServereNB 308 servers associated with the eNB 102 unit, the PGW 114 is no longer involved in routing packets for this service. The capacity of PGW 114 can be reserved for delivery of other services. The packet is routed by the P/S agent 1304 of OptServerPGW 304± to the P/S agent 1304 on each OptServereNB 308 server with UE 104 subscribed to the real-time event service data stream. In order to link the situation in Figure 15 with an extrapolation (to 60,000 users) in Figure 12, assume that each of the 600 eNB 102 units has 100 UEs 104 subscribed to the real-time event service. Therefore, The P/S proxy 1304 of OptServerPGW 304 ± copies 600 times the number of times one video packet per video time frame and one audio packet per audio time frame, And forward each of these packets to the OptServereNB 308 server. The transmission rate at OptServerPGW 304 can therefore be seen as 600 times 500 kbps or 300 Mbps, which can be reasonably handled by today's server computers. In addition, the transmission rate to each OptServereNB 308 on the LTE backhaul network can be regarded as 500 kbps instead of the 50 Mbps required by today's architecture, which reduces the factor by 100.

[0185] It can also be observed that the need to allocate real-time event service packets by OptServerPGW 304 at a rate of 300 Mbps can be reduced by having more than one server instance associated with PGW 114. For example, if five OptServerPGW 304 instances are deployed, and each OptServerPGW 304 instance covers 120 of the 600 OptServereNB 308 servers, then the data rate required for delivering real-time event services from each OptServerPGW 304 instance is reduced to 60 Mbps.

[0186] At each OptServereNB 308, the P/S proxy 1304 receives one video packet per video time frame from the P/S proxy 1304 running at OptServerPGW 304± and one audio packet per audio time frame (ie, approximately 500 kbps rate), and allocate packets to the UE 104 entity directly connected to it. In this example, it is assumed that each eNB 102 supports 100 UEs involved in real-time event services. Therefore, the transmission data rate at OptServereNB 308 can be regarded as 100 times 500 kbps, or 50 Mbps. It can also be seen that this value is feasible using today's server computer technology.

[0187] The publish/subscribe proxy architecture, bearer redirection capabilities, and integration of optimization servers into the LTE wireless network in the present disclosure can be regarded as enabling the economic delivery of real-time event services (including commercial TV) to wireless users.

[0188] Using the publish/subscribe paradigm to implement active-hot standby redundancy in the server architecture. In the active-hot standby redundancy architecture, two identical service instances 1602 and 1604 are installed in the network. The server 124 running each service instance may be located far away from its pairing server 124, or may be co-located with the pairing server 124, but placed on a different power source. The actual deployment situation may depend on the expected failure mode associated with the server 124. The standby service instance 1604 may maintain state information for each session maintained at the active service instance 1602 that it is ready to replace. When the active instance 1602 fails, the standby instance 1604 promotes itself to active and assumes all aspects of the service identity and role of the active instance it is replacing. Although the ongoing transaction may be lost as if it fails, the service to the user entity continues without interruption.

[0189] Keep-alive messaging can be used between the active instance and the standby instance 1602 and 1604, so that the standby instance 1604 can determine when to promote itself to the active state and assume the sum of the service identities of the failed instance it is replacing. All aspects of functionality.

[0190] When using a peer-to-peer communication architecture, it may often be difficult to transfer state information from the active instance to the standby instance. Maintaining lockstep state information at both the active service instance 1602 and the standby service instance 1604 may involve a large amount of overhead at the active service instance 1602 for providing state information to the standby service instance 1604. In a typical implementation, in this case, the service instance can be executed on different computing nodes, and the state change can be accumulated on the active instance 1602 first, and then transmitted to the standby instance 1604. Therefore, a large number of CPU cycles can be used for the active instance 1602 host to implement the hot standby architecture.

[0191] When the publish/subscribe paradigm is used with the distributed P/S proxy architecture described herein, it may be much easier to maintain public state in the active and standby instances 1602 and 1604. The standby instance 1604 can be programmed to subscribe to the exact same topic as the active service instance 1602, including topics with unique instance ID tags used by the active instance 1602. Therefore, without taking any action on the part of the active instance 1602, the standby instance 1604 can receive exactly the same message as the active instance 1602 received. The standby instance 1604 can process these messages in exactly the same manner as the active instance 1602, except that the active instance 1602 publishes responses and other service-specific messages, while the standby instance 1604 may not publish any service-specific messages. Therefore, the state information held in the standby instance 1604 can be kept in lockstep with the state information held in the active instance 1602.

[0192] Each service instance may have an instance ID value that distinguishes one service instance from another service instance. These values can be used by the standby instance 1604 to monitor the operating status of the active instance 1602 in a keep-alive exchange. The keep-alive interaction shown in Figure 16 and discussed in this article can be used in an active-hot standby redundancy architecture. Because the standby service instance 1604 has used the same instance ID as the active service instance 1602 for service-specific interactions, the standby instance 1604 does not need to assume the service identity of the failed active instance 1602 when the role changes. The standby service instance 1604 promotes itself to an active state and turns on a software switch that allows it to publish messages that were not published when it was previously in standby state. In the case that the previous standby instance 1604 is now providing services, all service sessions continue without interruption.

[0193] The above paragraphs indicate how the standby instance 1604 can monitor the active service instance 1602 and assume all aspects of the role of the active instance 1602 when the active instance 1602 fails (including publishing service-specific messages). When a single standby instance 1604 is ready to replace any of the N active service instances 1602, this active-hot standby redundancy architecture can also show work. In this case, the standby instance 1604 subscribes to each service topic to which the monitored active instance 1602 subscribes. The session state information may be organized in the standby instance 1604± in a manner that allows the use of the active service instance 1602 to identify the service session. In addition, the standby instance 1604 can maintain every active service it is monitoring

A separate keep-alive exchange for instance 1602. When a failure is detected in the active service instance 1602, the standby instance 1604 promotes itself to the active state, deletes all session state information except for the session associated with the service instance 1602 it is replacing, and unsubscribes all service-specific information Themes (except those of the service instance 1602 it is replacing), and turn on the software switch that prevents it from publishing service-specific messages so far. The service session that was previously handled by the failed service instance 1602 is now handled by the standby (now active) service instance 1604. The newly promoted active service instance can also report to the unit management system 802 (EMS), indicating the failure of the specific service instance 1602, and the assumption of the active service role by the reporting service instance 1604.

[0194] It can be seen how the active-hot standby service redundancy architecture disclosed herein using a P/S proxy messaging system can be used to provide a hot standby redundant server for the real-time event service 1502 described in this disclosure. In addition to the real-time event server 124 shown in FIG. 15, a hot standby redundant server 124 may also be deployed. The service program 1502 running on the standby server 124 may exchange keep-alive messages with the active service instance 1502 shown in FIG. 15 to determine the operating state of the active instance 1502. At the same time, the standby server 1502 subscribes to the same topic as the active instance 1502 subscribed via the P/S proxy network, and therefore can maintain the same state information as the state information maintained on the active instance 1502.

[0195] Using keep-alive messages to monitor the status of active instances. Service instances 1602 and 1604 can implement a method for determining whether they adopt an active state or a standby state when they are initialized. In addition, the standby instance 1604 and the active instance 1602 can implement keep-alive communication exchange, so that the standby instance 1604 can determine when the active instance 1602 fails. The repetition rate of keep-alive messages can determine the rapidity, using this rapidity, the standby instance 1604 can determine the failure of the active instance 1602 and promote itself to the active state. Generally, a configured number of consecutive no replies to keep-alive messages sent by the standby instance 1604 can be used to declare the failure of the active instance 1602. The processing priority of keep-alive messages can be given, so that false claims about service instance failures do not occur.

[0196] FIG. 16 shows an example of keep-alive messages that can be used in this redundant architecture. These interactions all take place using the connection of the service program to the P/S proxy instance 1304 running on its server 124.304.308 machine. However, for the sake of simplicity, the delivery of messages through the P/S proxy 1304 architecture is omitted in FIG. 16. The active service instance 1602 and the standby service instance 1604 can be executed on different server machines (124.304.308) because the failure of the server (124.304.308) is being overcome on the redundant architecture. In addition, the active service instance 1602 does not initiate the sending of keep-alive messages, but always responds to the received keep-alive messages.

[0197] In the design of these service instances 1602&gt;1604, each instance of &lt;serviceType&gt; can be configured using &lt;instance1D&gt;. In addition, several topics (e.g., text strings) may be hard-coded for the delivery of keep-alive messages. All active service instances 1602 of &lt;servieeType&gt; can subscribe to the topic ServiceControl/&lt;ServiceType&gt;/KeepAliveo. In addition, when the service instance is being initialized, it must determine whether it is active or standby, so it subscribes to the topic ServiceControl/&lt;ServiceType&gt;/ KeepAlive/&lt;instanceID&gt;, where &lt;instanceID&gt; can be a value assigned to its own service instance. The initializer can also subscribe to the topic ServiceControl/&lt;serviceType&gt;KeepAliveo. The latter topic can be used to receive keep-alive messages from another service instance that is being initialized or in a standby state. Although there may be M active service instances 1602, there is only one standby service instance 1604. Therefore, when the service instance is determined When this is the standby instance 1604, it subscribes to ServiceControl/&lt;serviceType&gt;/KeepAlive, and also subscribes to ServiceControl/&lt;serviceType&gt;/KeepAlive/Standby. The previous subscription is used to

The restarted active service instance 1602 receives the keep-alive message.

[0198] When a service instance is initialized, it can send a single keep-alive message to the topic ServiceControl/&lt;serviceType&gt;/KeepAlive at a periodically configured rate, and it can indicate in the message payload that its status is "initialized", and it can also include Its &lt;instancelD&gt;. The P/S agent 1304 messaging system is responsible for duplicating the packet when there is more than one service instance 1602 that is being backed up in the redundant architecture. Each service instance that receives the message responds by publishing a KeepAliveResp message to the topic ServiceControl/&lt;serviceType&gt;/KeepAHve/&lt;instanceID&gt;, where &lt;instanceID&gt; is the value received in the keep alive message. Therefore, the message can be routed by the ρ/s proxy 1304 system only to the service instance that is undergoing initialization. The KeepAliveResp message contains the status of the sending instance and the &lt;instanceID&gt;o of the sending instance

[0199] If the initialized service instance does not receive a response from any other service instance after configuring or providing a number of keep-alive attempts, then the initialized service instance can set its status to standby, and then act as another service instance. When the service instance is initialized, there is no gap in the state information collected subsequently, and the active state is adopted, and services are provided to users. When transitioning to the standby state, the service instance can unsubscribe from the topic^uServiceControl/&lt;serviceType&gt;/KeepAlive/&lt;instanceTD&gt;^,&gt;And you can add to the subject^uServiceControl/&lt;serviceType&gt;/KeepAlive/Standby^&gt;,Subscription. Subscription to the topic ServiceControl/&lt;serviceType&gt;/KeepAlive can be reserved. The standby service instance 1604 may begin to publish keep-alive messages at the configured or provided periodic rate after the time it may wait to allow the configuration or provision of initialization by other service instances. The keep-alive message issued by the standby service instance 1604 uses the topic ServiceControl/&lt;serviceType&gt;/KeepAlive, and includes the standby status of the publisher of the message and &lt;instance 1D&gt;. Publish the response to the keep-alive message received from the standby service instance to the topic SendceControl/&lt;serviceType&gt;/KeepAlive/Standby.

[0200] If the response is received from the standby service instance 1604 in response to any keep-alive message sent by the initializing service instance, then the initializing instance can promote itself to the active state, contacting the topic ^u Service Instance/&lt;serviceType&gt;/KeepAl i ve/&lt; instance 10&gt;^,?And keep its subscription to ServiceControl/&lt;serviceType&gt;/KeepAlive.

[0201] If after configuring or providing the transmission of a number of keep-alive messages, the initialized service instance receives responses from less than N active service instances 1602, and no response is from the standby service instance 1604, then initialize The instance of can change its status to standby, cancel the subscription to the topic SendceControl/&lt;serviceType&gt;/KeepAlive/&lt;instanceID&gt;, and add the topic^uServiceControl/&lt;serviceType&gt;/KeepAlive/Standby^&gt;,Subscription. Subscription to the topic ServiceControl/&lt;serviceType&gt;/KeepAlive can be reserved. The standby service instance 1604 may start to publish keep-alive messages at a configured or provided periodic rate.

[0202] If the initialized instance receives responses from all N active service instances 1602, the initialized instance can change its status to standby, and can unsubscribe to the topic SendceControl/&lt;serviceType&gt;/KeepAlive/&lt;instanceID&gt; , And you can add a subscription to the topic ServiceControl/&lt;serviceType&gt;/KeepAlive/Standby". Or, if the initialized service instance receives a response from the standby instance 1604, the initialized service instance will promote itself to the active state and release On the subject ^uSendceControl/&lt;serviceType&gt;/KeepAlive/&lt;instanceID&gt;^,&gt; Subscribe and keep their

ServiceControl/&lt;serviceType&gt;/KeepAlive subscription.

[0203] After configuring or providing multiple keep-alive attempts, if the initialized instance receives a response from another service instance, where the total number of replies is N or less, and some responses (including no response) indicate the service The instance is active, and other responses indicate that the service instance is in the initializing state, but no response indicates the standby state, then if the &lt;instanceID&gt; of the sending service instance is less than at least one of the &lt;instanceID&gt; values of all other initializing instances &lt;instancelD&gt; value, then the sending service instance can promote itself to the active state; and if the sending service instance's &lt;instancelD&gt; is greater than the &lt;instancelD&gt; of all other service instances reporting that they are in the initializing state Value, then the sending service instance can promote itself to a standby state. According to the state allocated by the service instance for initialization, the above subscription can be deleted, added, or maintained, depending on the state allocated by the service instance for initialization.

[0204] If the standby service instance 1604 receives a keep-alive response from another service instance indicating that it is also in a standby state, if the &lt;instance1D&gt; value of the instance receiving the response is greater than the &lt;instance1D&gt; value indicated in the response message, then receive the The responding instance remains in the standby state, but if the &lt;instance^&gt; of the instance receiving the response is less than the value of &lt;instance1D&gt; indicated in the response message, the instance receiving the response changes its state to active. If the transition from T to the active state is performed, the changed service instance cancels the subscription to the topic ServiceControl/&lt;serviceType&gt;/KeepAlive/Standby, and keeps its subscription to the topic^uServiceControl/&lt;serviceType&gt;/ KeepAlive subscription.

[0205] Whenever a service instance receives a keep-alive message from the standby service instance 1604, it publishes a response message to the topic ServiceControl/&lt;serviceType&gt;/KeepAlive/Standby, and indicates the unique identifier of the responding service instance plus its current state. Therefore, the response message can be routed to the backup service instance 1604 by the P/S agent 1304 network architecture.

[0206] It can be seen from the above that the logic for determining the active/standby status of a service instance is complicated. Figure 16 shows a keep-alive interaction for an active service instance 1602 and a standby service instance 1604. In order to keep the figure as clean as possible, the P/S agent 1304 subsystem is not shown. In addition, for the sake of simplicity, not all the situations described in the above paragraphs are shown in FIG. 16. Those skilled in the art may note that the description in this article constitutes a complete algorithm for determining the active or standby state of the service instance to be initialized.

[0207] Note that FIG. 16 shows that when the standby instance 1604 promotes itself to the active state, it can retain its &lt;instance1D&gt; identifier for keeping active message exchange, but it can use the service instance &lt;instance1D&gt; it is replacing. Information specific to all services. Doing so allows the UE 104 whose session was interrupted at the failed service instance to use the same service instance ID value obtained at the beginning of the service session to restart those service sessions or restart them at the replacement service instance. The alert message may also be generated by the previous backup service instance 1604 in order to report the failure of a specific, previously active service instance 1602, and report the state change of the backup service instance 1604 to the active state. The warning message is not shown in FIG. 16.

[0208] Architecture for saving backhaul usage when providing services to wireless users The content disclosed herein provides how to use an optimized server architecture integrated into the LTE wireless network, plus allowing the UE 104 to connect to its serving eNB via the redirected bearer 312 102 The associated optimization server 308 means, plus a publish/subscribe proxy architecture for providing wireless users with efficient delivery of real-time event services. In the real-time event service, many users receive the same information (for example, video, audio) at the same time. One of the efficiencies provided by this architecture is that compared with the usage required when todays architecture is used to provide the service, the

Greatly reduced.

[0209] Other types of services distribute the same information (for example, video, audio) to a large number of users, but not at the same time. An example could be a streaming movie delivery service. In this service, a large number of users can choose to watch the same movie or video, but do so at different times. If the traditional architecture shown in FIG. 1 is used, each such end user 104 in the LTE wireless network receives data across the Internet 122, the long backhaul network 804, and the enhanced packet core (EPC) network (PGW 114 and SGW 110). The unit, the backhaul network 112 connecting its serving eNB 102 to the EPC, and the only video data stream and the only audio data stream of the LTE air interface.

[0210] A better approach may be to use the set of optimization servers 304 and 308 described in this disclosure, together with the publish/subscribe proxy architecture as shown in FIG. 14. It can be pointed out that if the service (for example, streaming movie delivery service (SMD) 1702) is provided at the OptServereNB server 308 shown in FIG. 14, and if for each user who desires to receive the streaming movie delivery service 1702, Invoking the UE 104 dedicated bearer redirection 312 shown in Figures 3 and 4, then the movie delivery to each such user does not use the LTE backhaul network 112. It can be seen that the video and audio packet streams span the slave and user services. The OptServereNB 308 associated with the eNB 102 passes through the eNB 102 and passes through the LTE air interface to reach the user equipment 104. This technology is applicable to any service with the following characteristics: the same information may need to be sent to multiple users 104, but not It must be at the same moment. The streaming movie delivery service 1702 is just one example of a service with this feature.

[0211] In order to provide streaming movie delivery services, a streaming movie delivery (SMD) application 1702 can be deployed to run on each optimization server 304 and 308 ±. See Figure 17. The application 1702 can access movies stored locally in permanent storage, but the number of movies stored in the OptServereNB 308 unit may be more limited than that in the OptServerPGW 304 unit. Movies at any one of the optimization servers 304 or 308 that are not stored in the APN wireless network are obtained from a more remote storage 1704 via the Internet, and are stored at OptServerPGW 304. The allocation of movies to eNB 102 locations can be controlled by a streaming movie delivery (SMD) 1702 service instance running on OptServerPGW 304, and can be based on the number of users 104 accessing a particular movie from a particular eNB 102 location.

[0212] Video streaming not only consumes a large amount of air bandwidth, but also generally consumes a large amount of bandwidth on the backhaul connection 112 between the eNB 102 and the SGW 110. Therefore, a relatively small number of users 104 participating in a video streaming service at one eNB 102 can consume most of the air and backhaul 112 capacity of the eNB 102. Although the beamforming system discussed in this disclosure enhances the air interface capacity, it can serve a larger number of high-bandwidth users 104 compared to current eNB 102 implementations, and the corresponding increase in the backhaul 112 bandwidth may not be provided. Therefore, it is important to save the bandwidth of the backhaul 112 as much as possible (especially when transmitting video services). When the backhaul 112 is highly utilized, the service delivery to all users 104 may be disrupted, and the service quality of all users 104 may deteriorate. The deployment of the APN optimization server 308 at the location of the eNB 102 plus the bearer redirection 312 at the unit of the eNB 102, plus the publish/subscribe 1304 messaging system deployed on the optimization servers 304 and 308 can save the use of the eNB 102 backhaul 112 and therefore can maintain High quality of service for all users 104. In addition, because of the short path between the UE 102 and the point where the service is provided, Therefore, the lowest possible delay is incurred in sending audio and video data streams to the UE 104. This subsection shows how the backhaul 112 usage is minimized when one or more users access the streaming movie delivery service 1702.

[0213] FIG. 4 shows the interaction between the UE 104 and the software running on the OptServerPGW 304 when the user 104 invokes the streaming movie delivery 1702 service of the UE 104 ±. A dedicated bearer 302 may be established to support the service 1702 invoked by the user, and the bearer may be redirected to the OptServereNB 308 node associated with the eNB 102 serving the UE 104. UE 104 may need to connect to P/S proxy 1304 running on OptServereNB 308 ± in order to pass

P/S proxy middleware to receive its services.

[0214] The following is an example of the manner in which the streaming movie delivery service 1702 can be designed. Other designs may be possible. See Figure 17 for the service deployment architecture. Refer to Figure 18 for the service message interaction discussed next.

[0215] When the user selects the streaming movie transfer icon on the UE 104 display and enters the name of the movie to be watched, the UE 104 software can use the link bearer ID, Ded bearer ID, server IP, and server port obtained from OptServerPGW 304 The parameter (see the start service message in Figure 4) is connected to the P/S proxy 1304 at OptServereNB 308. The UE 104 may have to locate the service instance that can stream the selected movie to the UE 104, so the UE 104 points to the subject character The string ^Servicelnquiry/StreamingMovieDelivery/&lt;movie name&gt; publishes a service discovery message, and the message payload may include the UE 104 IMSI and the serving eNB ID. UE 104 also added to the topic^uServiceDescription/StreamingMovieDelivery/&lt;movie name&gt;/&lt;IMSI&gt; send subscription. Including UE IMSI in these messages may allow responses from any streaming movie delivery service instance 1702 to be routed by the proxy network only to the requesting UE 104.

[0216] All streaming movie delivery server programs 1702 can subscribe to the topic Serviceinquiry/StreamingMovieDelively/*, so all instances of the service can receive UE 104 query messages. In the example shown in FIG. 18, the service instance 1702 running by OptServereNB 308± at the location of the serving eNB 102 can receive service query information, just like the service instance 1702 running by OptServerPGW 304±. The UE 104 service query information is copied by the P/S proxy 1304 instance of the UE 104 connected to the OptServereNB 308. Assume that the configuration of the OptServerPGW 304P/S proxy 1304 prohibits further routing of the service query, and therefore, if the streaming movie delivery instances 1702 at the serving eNB 102 and the PGW 114 can provide movies, only they can respond. Assuming they can (in this example, the service instance at OptServerPGW 304 can store a collection of all movies that can be provided at any OptServereNB 308, but the collection of movies stored at a particular OptServereNB 308 can be a subset of these. UE 104 may include the serving eNB 102 identifier in the service discovery message sent by it, so the streaming movie delivery service instance 1702 at the PGW 114 may determine when enough downloads are requested from the location to ensure that the eNB 102 is at the location Send and store the movie if the movie is not already stored there).

[0217] Each streaming movie delivery instance 1702 that responds can publish a service response message to the topic ServiceDescription/StreamingMovieDelivery/&lt;movie name&gt;/&lt;IMSI&gt;. The message may only be routed to the requesting UE 104. In this case, two response messages can be returned to the UE 104. The UE 104 software may determine that the service instance 1702 at OptServereNB 308 is closer to the UE 104 according to the parameters included in the message (for example, the associated eNB ID or PGW), and select this to deliver the service. The service description message may contain the unique ID assigned to the service instance 1702.

[0218] Each SMD service instance 1702 subscribes to the control message flow topic for its service. In this example, the subject could be^uServiceControl/StreamingMovieDelivery/&lt;unique ID&gt;. Therefore, when the UE 104 software publishes a service request message to the topic ServiceControl/'StreamingMovieDelivery/&lt;unique ID&gt;, it can be routed to the service instance 1702 at the location of the serving eNB 102. The movie name can be placed in the payload of these messages, along with the "StartMovie" indication, as well as any other parameters that need to start the service (for example, charging information, topics used by UE 104 to receive the audio part of the movie (including The UE 104 IMSI used to ensure routing back to the UE 104), the subject of the video stream used by the UE 104 to receive the movie (including the UE 104 IMSI used to ensure routing back to the UE 104), the UE 104 used to receive the movie Subject of control information (including UE 104 IMSI used to ensure routing back to UE 104) o

[0219] The audio and video streams can be published by the service instance 1702 running by the OptServereNB 308 ± associated with the serving eNB 102, therefore, there is no backhaul 112 for sending these streams to the UE 104. The UE 104 software receives these streams and presents them to the user.

[0220] This scenario is followed by any number of UEs 104 served by a specific eNB 102, and as long as the requested movie is available at the OptServereNB 308 associated with the eNB 102, there is no backhaul 112 for carrying these to these users 104. Any audio/video stream in the audio/video stream. Because of this architecture, a lot of backhaul 112 usage is saved.

[0221] Streaming movie delivery is provided when the movie is not stored at the serving eNB location. If the requested movie is not provided at the streaming movie delivery service instance 1702 at the serving eNB 102 location, the service instance 1702 may be wrong. The UE 104 responds to the service query issued by the UE 104. See Figure 19. If the movie is available at the service instance 1702 at the location of the PGW 114, it can respond to the service query of the UE 104, and the movie is provided by the service instance 1702. Because the service dedicated bearer 312 for the UE 104 is relocated to its serving eNB 102, the routing of the movie stream is from the streaming movie delivery instance 1702 at the location of the PGW 114 to the OptServereNB 308 associated with the serving eNB 102 The P/S agent 1304 of the P/S agent 1304 connects with its P/S agent 1304 and then reaches the UE 104. See Figure 17 and Figure 19.

[0222] At the same time, because the UE 104 can include its current serving eNB 102 identification in the service query message, the SMD service instance 1702 at the PGW 114 can increase the count of the number of requests for the movie at the location of the eNB 102. If the count exceeds the provided value, the service instance 1702 at the location of the PGW 114 may download the movie to the service instance 1702 at the location of the eNB 102 where it may be stored. The UE 104 attached through the eNB 102 may request the movie further by the UE 104 The streaming movie delivery service 1702 associated with the eNB 102 is sent. The SMD service instance 1702 at the PGW 114 can therefore maintain a record of the SMD service instance 1702 and its eNB 102 location, as well as the various movies that can be provided. This information can be used by the wireless control process 3902 software at OptServerPGW 304 to switch scenarios to help it determine whether the service dedicated bearer 302 should be redirected to the target eNB. In addition, it can be implemented based on the algorithm used to determine when the movie should be from a specific eNB 102 The storage at the location is deleted.

[0223] In the case that the streaming movie delivery service 1702 at the PGW 114 does not have local storage of the movie specified in the UE 104 service query message, the SMD instance 1702 can communicate with the centralized host for the movie service via the Internet 122. The storage 1704 interacts and can start to retrieve the movie. When a movie packet is received from the centralized main storage 1704, it is stored to disk. Once the SMD instance 1702 on the OptServerPGW 304 determines that it can obtain the movie from the centralized storage 1704, it can send a service description response to the service query message of the UE 104. In this case, the movie is provided by the SMD service instance 1702 running on OptServerPGW 304±. Refer to Figure 19 for the messaging involved in this scenario.

[0224] Although only a few embodiments of the present disclosure have been shown and described, it is obvious to those skilled in the art that it is possible without departing from the spirit and spirit of the present disclosure described in the following claims. Changes and modifications are made to these embodiments in the context of the scope. The complete contents of all foreign and domestic patent applications and patents and all other publications cited in this article are hereby incorporated into this article to the full extent permitted by law.

[0225] APN LTE network used as a dual-use network dual-use means that the network can be used by the public and government agencies at the same time under the following conditions. Whenever it may be deemed necessary (that is, under the control of the U.S. government without the need to obtain a court order), the priority can be refused to be lower than the minimum allowable priority set by the government manager, or not set by the government manager A subset of the allowed high-priority access categories

Network access of all users/entities in a subset. In addition, it is possible to deny network access for all users/entities who are not members of a particular government agency that is allowed to access the network. In 3GPP wireless networks, the LTE cell blocking feature for government use can be applied to any cell, or all cells, or a subset of cells. In addition, when cell blockade for government use (CB for GU) is enabled, the network may result in members who are not allowed by government agencies, and/or the priority is lower than the lowest allowed priority, or is not managed by the government. Set the separation of all users in a subset of the subset of the allowed high-priority access category. It is also possible to make exceptions to emergency sessions already established in the network, and it is possible to allow emergency access to the network, which is determined by the US government administrator. Finally, it is possible for the network to perform a verification test of the user's identity before allowing the user to maintain access to the network or part of the network where CB for GU is enabled. It may be obvious to those skilled in the art that the above-mentioned CB capability for GU far exceeds the 3GPP cell blockade capability specified for the 3GPP network. In the rest of this disclosure for this feature, the focus is on how to design dual-use capabilities into the 3GPP LTE wireless network with the aforementioned features. It is understandable that the same principle can be used to implant dual-use capabilities into other types of 3GPP wireless networks, such as the 3G universal mobile telecommunications system (UMTS)ο

[0226] For standardized cell blockade regulations, refer to 3GPP documents TS 36. 331 and TS 22. 01, KTS 23. 203 (policy control rule functions, etc.), and TS 23. 228 (IP multimedia services, etc.). See also TS 22.153 for requirements for multimedia priority services. These standardized regulations do not allow the operation of dual-use networks as described above. In addition, these 3GPP documents do not give all the details for realizing or even these standardized capabilities. These standardized capabilities can be combined with additional, new features and capabilities in order to achieve the above-mentioned types of dual-use wireless networks. The content contained in the present disclosure describes the ways in which the dual-use LTE wireless network can be implemented in clear terms that can be understood by any person skilled in the art. To achieve this goal, standardization capabilities are integrated with new additional capabilities.

[0227] The concept of network roaming is used to distinguish government agency users from ordinary users. The International Mobile Subscriber Identity (IMSI) is a unique identifier assigned to each user equipment (UE 104) that can access the 3GPP wireless network. IMSI is a 64-bit value consisting of up to 15 numbers. The first three digits are the mobile country code (MCC). The next three digits (or two digits in Europe and other non-North American networks) are the domestic mobile network code (MNC). The remaining 9 (or 10) digits are in the network Mobile Subscriber Identification Number (MSIN). Therefore, the home network of the 3GPP wireless network is identified by specific MCC and MNC values that identify a specific public land mobile network (PLMN). Users who have signed a contract with a network operator are assigned an IMSI within the network and can visit the operator's cell. Those cells are in the home network.

[0228] Generally, network operators enter into bilateral agreements to allow users in one operator's network to access another operator's network, and vice versa. When such users access a cell of an operator's network different from their home network, these users are said to be roaming.

[0229] Network operators can usually provide their wireless network elements to define the allowed set of home networks and roaming networks. A UE 104 that has an IMSI that is not in the home network of the accessed cell or is not in the list of roaming networks provided in the home network element is not allowed to access the cell.

[0230] The above roaming concept can be used to help achieve part of the dual-use network requirements. The UE 104 that is a member of a government agency can be assigned the IMSI in the home network of the dual-use network. Members of different government agencies can be distinguished by the agency using a subset of the MSIN value assigned to members of a specific agency. Alternatively, members of different government agencies may be assigned IMSIs with different MCC and MNC values, where each of these networks is defined as a network equivalent to the home network in the dual-use network. In the home network, the members of the equivalent network are equal to the members of the home network

treat. For the home network, the list of equivalent networks is provided to the network element used to control access to the home network. The concept of equivalent network is defined in the 3GPP standard.

[0231] According to the previous paragraph, the members of the government agency are assigned the IMSI value in the home network of the dual-use network, or the IMSI value in the set of equivalent networks of the dual-use network. All other users can be assigned the IMSI value in their traditional network operator's network and can access the dual-use network as a roamer. General users may be due to lower service costs, because of the ability to receive higher data rates compared to cells in their home network, because of lower congestion compared to cells in their home network, Or it is preferred to access the dual-use network for other reasons.

[0232] Generally, a general user can access a cell in a dual-use network as a roamer and receive the same quality of service as provided to members of government agencies that access the dual-use network as their home or equivalent network. The element management system (EMS 802) that manages the network elements of the dual-use network can be used to provide the network elements with the home network value, the network value of each equivalent network, and the network value of each assigned roaming network.

[0233] In an emergency, or when government administrators consider it necessary, one cell, several cells, or all cells that access the dual-use network may need to be restricted to only government users. One step to achieve this restriction could be to make the EMS provide each mobility management entity (MME 108) that handles restricted cells or some cell deletion list of allowed roaming networks. In this case, MME 108 can deny access Restricted cells, or users who access any restricted cell in some restricted cells (if they are members of any network other than the home network, or are members of an equivalent network). In this case, the reason of "permanent PLMN restriction" can be used to reject the attempted access. Receiving the cause value causes the UE 104 to enter the PLMN into its forbidden PLMN list, and only manual selection of a cell in the PLMN can cause the UE 104 to try to access the cell again. Or, if only the selected set of cells is restricted, the rejection reason value may be "temporary PLMN rejection". In this case, the UE 104 enters the tracking area (TA) of the restricted cell into its restricted TA list, and may not try to access another cell in the TA. It may also be the case that when the remaining roaming networks are allowed, the subset of roaming networks is restricted. This type of regulation can be determined by government network administrators.

[0234] The following FIG. 20 is a modification of FIG. 1 of the present disclosure, and includes an EMS 802 that manages network elements in an LTE network. FIG. 20 shows that when a cell is restricted, the MME 108 processing the cell can be provided to delete or restrict the list of allowed roaming networks, and the MME 108 can be separated from a home network that is not a dual-use network, or an equivalent network Or all UEs 104 that are members of the allowed roaming network. The MME 108 maintains the UE 104 IMSI as part of the context information maintained for each UE 104 handled by the MME 108. For the separation process initiated by MME, refer to section 5. 3. &amp; 3 of TS 23.401 v9. 4.0.

[0235] Although the roaming concept is used to separate non-government users 104 from restricted cells and deny their access to the restricted cells, these UEs 104 may still try to access restricted parts of the dual-use network. In a disaster or other emergency situation, this access attempt may prevent or delay the access of high-priority government users of police department users, or fire department users, or emergency response users. In this emergency situation, these users must be provided with fast access. The 3GPP cell lockout concept can be used and extended as described in this disclosure to achieve another aspect of the dual-use LTE wireless network.

[0236] Architectural components that implement cell lockout and user authentication. Cell lockout is a standardized mechanism that can be used to restrict the set of UEs 104 that are allowed to access a cell. When cell blockade is enabled at a specific cell, the broadcast information from the cell includes: cell blockade parameters, ac-blocking factor parameters, ac-blocking

Time parameter, ac-for emergency blocking parameter, and ac-for a list of allowed/not allowed high-priority access categories included in the special AC blocking parameter. The System Information Block 1 (SIB 1) cell blocking parameter indicates whether any access restrictions are enabled at the cell. The SIB 2 ac-blocking factor parameter and the ac-blocking time parameter determine how often UE 104 with an access category priority between 0 and 9 may try to access the cell. The SIB 2 ac-for emergency blocking parameter indicates whether E911 calls are also blocked on the cell. ac-for a special AC blocking parameter is a Boolean list containing the access rights of each high priority access category. The UE 104 access category (AC) priority stored in the SIM card at the UE 104 allows the UE 104 to determine what to do when it detects that a cell is blocked for access. Regular users have their UE 104 assigned AC values between 0 and 9 (these values are randomly assigned to regular users). TS 22.011 specifies that AC 10 is used for E911 calls; AC 11 is used for PLMN users; AC 15 is used for PLMN employees; AC 12 is used for security services; AC 13 is used for utilities (for example, gas and water suppliers); and AC 14 is for emergency service users. There is no 3GPP standard instruction: no priority and AC 11 to AC 15 associated. No other access categories are defined in the 3GPP standard, so the dual-use network must be able to operate using only these values configured in the SIM card of the UE 104.

[0237] According to the 3GPP standard, when the cell blockade is set to "blocked", the UE 104 with an access category priority of more than 10 is always allowed to access the blocked cell. This may or may not be what the government administrator expects when the cell is blocked for government use. A more fine-grained blocking based on UE 104 access category priority may be required (e.g., It may be necessary to block access for ACs smaller than 12, or it may be necessary to allow access for some users with AC 12, but it may be necessary to block access for other users with AC 12, or it may require more than in the 3GPP standard To distinguish government users). This patent disclosure provides design information for achieving a more fine-grained cell access blocking capability. In addition, in dual-use networks, it may be necessary to restrict access to even high-priority users as described above (for example, FBI users with access category priority 12 may need to access blocked cells but have access Other users of category priority 12 may need to be restricted from accessing the blocked cell). The design information presented in this disclosure uses UE 104 IMSI to further restrict high priority users' access to blocked cells. Finally, in some environments, it may be that the UE 104 SIM card has been illegally set by criminals or terrorists to have a high-priority access category, or the IMSI assigned to high-priority users has been programmed. Therefore, dual-use networks may be required to be able to perform biometric testing of any high-priority users that have become connected through a cell that is blocked for government use. Biometric testing can include voice matching, fingerprint matching, or anything that involves unique user characteristics or knowledge (such as passwords). What other types of testing. The need for biometric testing is also described in the information presented for dual-use networks in this disclosure.

[0238] It may be necessary to establish cell blockade strictly in accordance with the 3GPP standard at one or more LTE cells. At the same time, the paragraph above shows that additional access restrictions need to be enabled when a cell is blocked for government use. Therefore, the design description of the present disclosure of this patent defines a special cell blockade type, called cell blockade for government use (CB for GU), which is different from the cell blockade capability defined in the 3GPP standard documents. The design information contained in the present disclosure and understandable by those skilled in the art shows how to add the CB cell lockout capability for GU to be used in addition to the cell lockout specified in the 3GPP standard.

[0239] The design of the system disclosed herein is only one of several designs that can be used to implement the capabilities required in a dual-use network. It should be noted that while achieving the same results , it is possible to modify the design information presented in this article. A specific collection of design information is presented in this article to illustrate to those skilled in the art how a dual-use network can be implemented.

[0240] FIG. 21 shows LTE network components that may be required to implement the aforementioned CB capabilities for GU. Note Figure 21

Including the optimized server concept and the ρ/s proxy concept described in this article. Including these components in the design information makes the system disclosed in this article efficient and may be more efficient than other types of unit docking. The solid line in FIG. 21 shows standardized interfaces for the LTE network, and includes mnemonics used in the 3GPP standard for each interface. The dashed lines indicate that additional interfaces may be needed to provide dual-use capabilities. The dotted line connected to the government-run unit management system (EMS 802) is the kind of 0AM interface (operation, management, and maintenance interface) that exists in any LTE network, although in this case, they can provide possible and dual-use network capabilities Relevant information. The interface between the LTE MME 108 and the P/S proxy 1304 running on the OptServerPGW 304 node can provide multiple MME 108 units deployed in the LTE network and application functions that can play a central role in providing dual-use capabilities to the LTE network (AF) Efficient docking between 2102.

[0241] If cell lockout is not implemented at any cell in the LTE network, the EMS 802 does not provide any additional cell lockout information to the AF 2102, and does not provide any additional cell lockout information to the MME 108 unit. If standardized cell lockout is implemented at any cell in the LTE network, the EMS 802 also does not provide any additional cell lockout information to the AF 2102, and does not provide any additional cell lockout information to the MME 108 unit. When cell blockade for government use is enabled at one or more cells in an LTE network, EMS 802 provides AF 2102 to the MME 108 unit serving the blocked cell, and to the eNB 102 unit operating on the blocked cell. Additional data related to CB for GU. (The information provided to the eNB 102 unit is the same as that required for standardized cell blocking capabilities). The following sections may describe the process design to achieve dual-use wireless network features.

[0242] In addition to the network elements and interfaces shown in FIG. 21, a new application can be added to the UE 104 to enable biometric user authentication in a dual-purpose LTE network. The additional UE 104 capabilities are shown in FIG. 22. The UE 104 may also be connected to a P/S proxy 1304 network for services other than biometric testing. The advantage of using the P/S proxy 1304 middleware is that a single connection from the UE 104 to the P/S proxy 1304 network can be sufficient to support any number of UE 104 applications. Each application uses an application-specific theme via the P/S proxy interface 2204. Therefore, when the UE 104 is turned on and connected to the LTE network for the first time, the UE 104 application for the biometric test 2202 can be invoked. The biometric test application 2202 subscribes to receive messages via a specific topic, and can wait until the initial biometric test message is received (the message may never be sent because the test is not generally required). Those skilled in the art can understand that the P/S agent is not critical to the biometric test feature, because the UE 104 can instead each connect to a network-based program to perform such a test. The P/S proxy 1304 middleware makes the solution more efficient.

[0243] Automatic separation of restricted users when separate government use is enabled

The 3GPP standard defines a mechanism for allowing, or restricting, or denying users' access to the network. In order to implement this mechanism, the standard defines the policy and charging rule functions (PCRF 118) and application functions (AF 2102) that may be involved in the interaction with the PGW 114 when the user 104 establishes access to the LTE network for the first time. These units are shown in FIG. 21. In order to achieve the required capabilities in dual-use networks, special functions can be added to the AF 2102. The AF 2102 may be provided with a list of cell ID values for cells whose access is blocked for government use. For each cell in which the CB for GU is enabled, the provided data may include: the minimum value of the access category priority of the cell allowed to access, or a subset of the allowed high priority access category values, A parameter indicating whether E911 calls are allowed at the blocked cell, a parameter indicating whether the biometric test for access to the cell is enabled, and the minimum time interval between biometric tests for the same UE 104 Parameters. In addition, it can be provided to the AF 2102, or the AF 2102 can access the list of IMSI values, and for each IMSI value, its access category priority. Note: Because these AC priority values are associated with the IMSI in the database used by AF 2102 and are not included in the UE 104 SIM, the AC priority value can be It is not constrained to a standardized value of 11 to 15, but can be assigned any value. Therefore, as described in this disclosure

As mentioned, for the CB for GU, very fine access category restrictions can be imposed through the use of these AC priority values.

[0244] As shown in FIG. 21, the AF 2102 maintains the Rx diameter interface to the set of PCRF 118 functions deployed in the LTE network, and also maintains the interface to the P/S proxy 1304. Therefore, the AF 2102 can participate in and use the release/ The subscribing agent 1304 middleware is used for message exchange with other entities in communication. As shown in FIG. 21, the MME 108 entity in this dual-purpose network design can also interface with the P/S proxy 1304 middleware to communicate with the AF 2102. As shown in FIG. 22, the UE 104 may also interface with the P/S agent 1304 middleware to communicate with the AF 2102.

[0245] When the CB for GU is enabled at a specific cell, the first step that can be performed is to make the EMS 802 send prescribed information to the eNB 102 that provides the restricted cell, so it can broadcast the information of the allowed roaming network. The collection of changes. The next step can be: specify each MME 108 serving the cell, so its specified information changes to indicate that roaming is not allowed in the cell, or only a subset of the roaming network is still configured for the restricted cell. roaming.

[0246] When the allowed roaming network changes at a cell, the UE 104 attached through the cell can select a different cell once it determines that they access through a cell that does not allow roaming from the UE 104 home network. At the same time, the MME 108 can search for each UE 104 that is accessed through a cell that does not provide roaming or provides restricted roaming through the UE 104 ± below. For each UE 104 whose IMSI MCC, MNC value does not match the home network or equivalent network, or the allowed roaming network, the MME 108 can initiate a separation process, and these UEs 104 are deleted from the cell. The separation process initiated by the standardized MME is specified in section 5. 3. &amp; 3 of TS 23. 401 v9. 4.0. See Figure 23.

[0247] The next step may be: the EMS 802 provides the AF 2102 with the parameters of the cell that is blocked for government use input by the government administrator for the instance of the access blockade for government use. According to the first paragraph of this section, these parameters can include: cell ID, the minimum access category priority of the cell allowed to access, or the list of high priority access category values of the cell allowed to access, whether E911 is allowed via the cell The time interval between calls, whether biometric testing is enabled for the cell, and the time interval between biometric testing for the UE 104. Note: As described in the previous paragraph, the list of AC priority values can contain values beyond the settings 11 to 15 specified in the 3GPP standard. After that, the set of MME 108 units serving the blocked cell can be provided with parameters for cell blockade used by the government. Finally, the eNB 102 that provides the cell may be provided with cell blocking parameters for the restricted cell. These parameters are the parameters specified in the 3GPP standard, namely: cell blockade parameters, ac-blocking factor parameters, ac-blocking time parameters, ac-for emergency blocking parameters, and ac-for special AC blocking parameters. In order to ensure that no low-priority UE 104 accesses the blocked cell, the ac-blocking factor can be set to zero.

[0248] Once the eNB 104 cell broadcasts cell lock information, no low priority UE 104 can access the blocked cell. However, the low priority UE 104 that has been accessed via the now blocked cell needs to be separated. In order to achieve this operation, the MME 108 serving the blocked cell can search for the UE 104 accessed through the blocked cell through their UE 104 ± the following set. The UE 104 includes the establishment reason parameter below, which is sent by the UE 104 when it accesses the LTE network. If the establishment reason does not indicate a high priority, the MME 108 may initiate a separation procedure for the UE 104. See Figure 24.

[0249] If the high-priority UE 104 becomes detached via Figure 24 because it initiated its LTE attachment without indicating a high-priority call, it can now reattach to the blocked cell, thereby indicating high Priority call. Low-priority UE 104 may not be able to access via a blocked cell, especially if the ac-blocking factor has been set to 0o

[0250] FIG. 24 shows that a low-priority UE 104 may no longer attempt to access via a cell with a CB for GU enabled.

In the LTE network, the UE 104 whose previous attachment is not established due to a high priority is detached from the cell. UEs 104 that remain attached via the cell with the CB for GU enabled are therefore high-priority users, but as mentioned above, it is not certain that their priority is high enough to allow them to remain attached via the blocked cell, and it may be necessary Perform a biometric test to allow them to remain attached via the blocked cell. These aspects are not part of the cell blockade capabilities of standard-based LTE networks, but are part of the dual-use network capabilities when the cell is blocked for government use. The following processing can detail the way to perform these additional checks for UEs that remain attached via the blocked cell.

[0251] In order to achieve these further checks, this design of the dual-use network may require the MME 108 unit serving the cell where the CB for GU is enabled to interact with the AF 2102 in order to check the access priority of the UE 104, and Lead to the execution of biometric tests when necessary. As described herein, entities connected via the P/S proxy 1304 network transmit information by adding a subject tag (which can be a character string) to each posted message. The message is delivered to all entities that have subscribed to the topic. Therefore, when the AF 2102 is initialized, it can subscribe to the topic "AF/biometric/*". The character "*" indicates that any text after the second slash mark matches the subscription topic. At the same time, each MME 108 can subscribe to the topic "AF/biometric/&lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is a globally unique MME identifier assigned to the MME 108 instance. When publishing any message, the sending entity can indicate that the message should be routed back to itself. In this case, the sender may have subscribed to the same topic as the message it published.

[0252] For each UE 104 that remains attached via the cell where the CB for GU is enabled, the MME 104 serving the UE 104 can now issue a UE access check message to the topic "AF/biometric/&lt;GUMMEI&gt;" . Because of the wildcard in the topic subscribed by AF 2102, the message is received by AF 2102. The message may contain the cell ID of the cell being blocked, plus the IMSI value of the UE 104. The AF 2102 can perform additional verification via its provided data: the cell ID referenced in the received UE access check message is indeed the cell where the CB for GU is enabled. (If not, AF 2102 can report to the subject^uAF/biometric/&lt;GUMMEI&gt; ^ sends a UE access check response message to indicate that the UE 104 has passed the access test, and also indicates the inconsistency between the data provided by the MME 108 and the AF 2102. Because the unique GUMMEI value is included in the subject string, the message is only received by the MME 108 that sent the original UE access check message). Assuming that the cell ID is the cell ID of the cell where the CB for GU is enabled, AF 2102 can obtain the minimum value of the access priority that allows access to the blocked cell from the data it provides, or the high priority that allows access to the cell A list of class access category values. The value of the AC priority value may exceed the value allowed in the 3GPP standard. Then, the AF 2102 can obtain the priority of the UE 104 IMSI from the IMSI value it is provided or from an accessible database of IMSI values, the IMSI being the value received in the UE access check message. The AC priority assigned to the IMSI may exceed the value of AC priority allowed in the 3GPP standard. If the IMSI is not found in the provided data or in the IMSI database, the AF 2102 may return a UE access check response message to the MME 108 instance, thereby indicating that the UE 104 should be detached. In this case, the MME 108 can initiate the separation process for the UE 104, because only the high-quality confirmed by the government is allowed. The access of the advanced user to the cell where the CB for GU is enabled.

[0253] Alternatively, if the AF 2102 locates the UE 104 IMSI in the data provided to it, or in the IMSI database, it can retrieve the AC priority value of the UE 104 and compare it with the minimum value provided for the blocked cell. The AC priority value is compared, or compared with the provided set of allowed high priority access category values. If the IMSI has a too low priority, the AF 2102 may return a UE access check response message to the MME 108 instance to cause the UE 104 to be detached. However, if the AC priority of the UE 104 is high enough, or matches one of the allowed high-priority access categories, then the AF 2102 can check the data provided to it to determine whether the CB for GU has been enabled. Does the community require biometric testing? If not needed, AF 2102 can return to the MME 108 instance

The UE accesses the check response message, thereby indicating that the UE 104 can remain attached via the blocked cell. If the biometric test is enabled for the blocked cell, the following process can be followed before determining the final solution regarding the UE 104's ability to remain attached via the cell that has enabled the CB for GU.

[0254] The above text indicates that when the UE is connected to the LTE network, the UE biometric test application 2202 can be started, and the UE 104 can automatically (ie, without user intervention) connect to the P/ on the optimization server 304 in the network. S Proxy 1304 instance. The UE 104 software can subscribe to the topic "AF/biometric/test/&lt;IMSI&gt;", where &lt;IMSI&gt; is the only IMSI value assigned to the UE 104. The UE biometric test application 2202 is a dedicated application loaded to all UEs 104± that may need to access the dual-use network in an emergency. At the same time, when the AF 2102 is initialized, it subscribes to the topic "AF/biometric/test/*". With these mechanisms, and having completed the inspections in the previous paragraphs, AF 2102 publishes a biometric test start message to the subject "AF/biometric/test/&lt;IMSI&gt;", where &lt;IMSI&gt; is used by the MME 108 serving UE 104 The value received in the sent UE access check message. Therefore, the message is transmitted by the P/S agent 1304 network to the only UE 104 with the value of &lt;IMSI&gt;. At the UE 104, it is used by the UE biometric test application 2202. Consumption. The message may include data such as the type of biometric test that should be performed, or any other data related to the performance of the test. Other data may include: obtaining the GPS location of the UE 104; generating periodic reports on the GPS location; even when the user tries to put the UE 104 in the Evolved Packet System Connection Management (ECM) ECM idle state, or even when the user tries to turn off the UE Continue to produce the report at 104 o'clock. (These latter capabilities may be required during military operations or during other government operations.) Initiating biometric test messages can be reliably transmitted by the P/S agent 1304 network. In the case that the user chooses not to input data, the AF 2102 may start a timer to receive the biometric test data from the UE 104. In this case, if the timer expires, the AF 2102 may send a UE access check response message to the MME 108 to indicate that the UE 104 should be detached.

[0255] When the biometric test is performed at the UE 104±, the biometric test application 2202 of the UE 104 issues a biometric test result message to the subject AF/biometric/test/&lt;IMSI&gt;, and the message is still received by the AF 2102. AF 2102 cancels the timer set up to receive the message before and starts the analysis of multiple return data. Depending on the type of test being performed (for example, matching voice phrases, matching fingerprints or other biometric information, matching passwords), the AF 2102 can analyze the data on its own, or it can send the data to another service program to perform the analysis. The analysis reveals whether the T UE 104 should remain attached via the cell where the CB for GU is enabled. When the AF 2102 issues a UE access check response message, the determination returns to the sending MME 108. Therefore, the UE 2102 either detaches from the cell or is allowed to remain attached via the blocked cell. In the latter case, AF 2102 can set biometric test pass parameters for IMSI and can start a timer whose duration is determined by the time between biometric tests provided at AF 2102 for a given cell ID Value to set.

[0256] When a biometric test is enabled at a cell where CB for GU is enabled, whenever the UE passes the initial access procedure at the blocked cell, the service request process to the blocked cell, or the handover to the blocked cell During the process, you can perform the test. The purpose of the timer is to avoid testing the UE 104 too frequently. When the timer expires, the AF 2102 can reset the value of the biometric test pass parameter associated with the IMSI, so that another biometric test can be performed for the IMSI of the UE 104. (The value of the time between biometric tests can be set to INDEFINITE (indeterminate) to ensure that only one test is performed for each UE 104, if this is what the government administrator expects.).

[0257] FIG. 25 shows the processing described in the previous paragraph for the UE that has enabled the CB for GU to remain attached after the initial processing check at the serving MME 108.

[0258] The UEs 104 that remain attached via the cell with the CB for GU enabled have verified their access priority

Level, and may have verified the identity of the user via a biometric test. It is also possible that the UE 104 that has not yet attached via the blocked cell will attempt to access the cell via the initial attach LTE procedure, or via the service request LTE procedure, or via the handover LTE procedure. These UEs 104 must also be checked before allowing access to the cell where the GU-enabled CB is maintained. The following sections describe the processing that may be required to ensure that only properly authenticated UEs 104 maintain access to cells that are blocked for government use.

[0259] Initial access to the cell with the CB for GU enabled As described above, when the cell is blocked for government use, the UE 104 with an AC priority of less than 10 usually does not try to access the cell, except for E911 calls (if E911 calls are allowed in the blocked cell). If the ac-blocking factor is set to 0, the UE 104 with a low AC priority may not try to access through the blocked cell. Therefore, when an initial access request is received at the eNB 102 via a blocked cell, the initial access request comes from the high-priority UE 104. The attach request is sent from the eNB 102 to one of the MME 108 serving the cell. Refer to section 5. 3. 2. 1 of TS 23.401 v9. 4.0 for the LTE initial attach process. If the cell is blocked for some reason other than government use, then no additional processing is required or indicated in this disclosure. However, if the cell is blocked for government use, then the additional processing described in this article may be required.

[0260] As mentioned earlier, whenever one of the cells processed by the MME 108 is blocked for government use, each MME 108 is provided with CB parameters for GU. Therefore, when an attach request is received from the eNB 102, the MME 108 that has received the attach request message can check the data provided to it in order to determine whether the cell through which the access occurs is blocked for government use. If so, then the modifications to the MME 108 processing can be introduced during the initial LTE attach procedure as follows.

[0261] There are several points in the LTE initial attach process at which the MME 108 can initiate an interaction with the AF 2102 to determine whether the UE 104 should be allowed to continue the process, or whether the MME 108 should reject the attachment attempt. One point may be: when the MME 108 learns the IMSI of the UE for the first time (ie, when it receives the attach request message from the eNB 102). Another point may be when the MME 108 receives UE 108 subscription data from the home subscriber server (HSS 120) (ie, when the MME 108 receives the update location ACK message from the HSS 120). The following points of interaction between MME 108 and AF 2102 do not substantially affect the design described in this disclosure. (Actually, another alternative could be that HSS 120 stores the AC priority of UE 104 along with the remaining IMSI subscription data, and allows MME 108 to determine whether UE 104 should continue through the remaining initial access procedure, instead of using AF 2102 makes this determination). Next, if the MME 108 determines that the cell through which the UE 104 accesses the network is blocked for government use, the MME 108's reception of the attach request message is used to initiate the AF 2102 interaction. See Figure 26.

[0262] In order to more easily operate the dual-use network, the default APN (3GPP access point name) of the UE 104 in all home networks and all equivalent networks is used to distinguish the advanced wireless The general network of the network type (the opposite) can be sent to the APN including the optimization server 304 on which the AF 2102 program runs. When an attach request is received from a UE 104 accessing an LTE network via a cell that is blocked for government use, the MME 108 can be programmed to only allow setup to the default APN (ie, to the PGW 114 unit serving the default APN) The initial default bearer.

[0263] As shown in the process in FIG. 26, when the MME 108 receives an attach request from the eNB 104, the MME 108 can determine whether the cell being accessed is blocked for government use. As previously described, this determination is made based on the provision information that can be sent to it by the government EMS 802. If the cell is not blocked for government use, the attachment process continues according to the unmodified LTE standard (TS 23.401 ν9.4.0, section 5. 3. 2. 1). However, if

If the CB for GU is enabled at the district, the MME 108 can issue a UE access check message to the topic "AF/biometric/&lt;GUMMEI&gt;", where &lt;GUMMED is the unique ID assigned to the MME 108. The message contains the IMSI of the UE 104 and the cell ID of the cell being accessed. As mentioned earlier, this message is received by AF 2102. The AF 2102 can perform additional verification via its provided data: the cell ID referenced in the received UE access check message is indeed the cell where the CB for GU is enabled. (If it is not, AF 2102 can send a UE access check response message to the subject "AF/biometric/&lt;GUMMEI, ^ to indicate that UE 104 has passed the access test, no biometric test is required, and also instruct MME 108 to interact with AF 2102 Provide the inconsistency between the data. Because the subject string includes a unique GUMMEI value, the message is only received by the MME 108 that sent the original UE access check message). Assume that the cell ID is enabled for GU CB The cell ID of the cell, AF 2102 can obtain the minimum value of the access priority that allows access to the blocked cell from the data it provides, or the set of high priority access category values that allow access to the cell. Note: AC priority The level value may include a value that exceeds the AC priority value specified in the 3GPP standard in order to achieve a more fine-grained priority access feature than can be provided by standardized cell blockade. Then, the AF 2102 can obtain the priority of the UE 104 IMSI from the IMSI value it is provided or from an accessible database of IMSI values, where the IMSI is the value received in the UE access check message. If the IMSI is not found in the provided data or in the IMSI database, the AF 2102 may return a UE access check response message to the MME 108 instance, thereby indicating that the UE 104 access request should be rejected. In this case, the MME 108 may initiate a rejection response to the UE 104.

[0264] Alternatively, if the AF 2102 locates the UE 104 IMSI in the data provided to it, or in the IMSI database, it can retrieve the AC priority value of the UE 104 and compare it with the minimum value provided for the blocked cell. Compare the AC priority value or compare it with the list of allowed high priority access category values. Note: The AC priority value stored using the IMSI of the UE 104 can exceed the AC priority value allowed in the 3GPP standard, so as to introduce more fine-grained access priority class distinctions compared to what can be provided in the 3GPP standard. If the IMSI has too low priority, or does not have a priority value that matches one of the allowed values, AF 2102 may return a UE access check response message to the MME 108 instance to cause the UE 104 to be attached. Refuse. However, if the AC priority of the UE 104 is high enough, or if the AC priority of the UE 104 matches one of the allowed values, then the AF 2102 can check the data provided to it to determine whether the cell is blocked A biometric test is required. If it is not required, AF 2102 may return a UE access check response message to the MME 108 instance, thereby indicating that the UE 104 attach request processing should continue, and no biometric test is required. If biometric testing is enabled for a blocked cell, Then the AF 2102 may return a UE access check response message to the MME 108 instance, thereby indicating that the UE 104 attach request processing should continue, and a biometric test is required.

[0265] According to FIG. 26, if the attach request processing continues to access via the cell where the CB for GU is enabled, and if the AF 2102 response to the initial MME 108 interaction indicates that further biometric testing is required, the MME 108 may wait Until it determines the IP address assigned to the UE 104. This can happen when the MME 108 receives the create session response message from the SGW 110 during the LTE initial attach procedure. At this moment, the MME 108 can publish a UEipInfo message to the topic "AF/biometric/&lt;GUMMEI&gt;", so the message is received by the AF 2102. The message may include: the cell ID, IMSI, the IP address assigned to the UE 104, and the IP address of the PGW 114 serving the UE 104. Then, the AF 2102 can use this information along with the additional data provided to interact with the PCRF 118 function to request that the filtering strategy be set in the PGW 114 for the UE 104. The filtering strategy may be to restrict the packets that will be forwarded by the PGW 114 on the uplink or carried by the UE 104 for downlink transmission. The allowed uplink grouping is only for the IP address and port number of each P/S proxy 1304 instance running on the available OptServerPGW 304 node (in PGW

There may be more than one server node among these server nodes at location 114, and there may be more than one P/S proxy instance on each of these servers). The allowed downlink packets can come from only one of these P/S proxy 1304 instances. The purpose of the filtering strategy is to isolate the communication capabilities of the UE 104 until the biometric test is completed. When the default bearer is established for the first time, the dedicated software 2204 of the UE 104 can usually try to connect and dock with the P/S agent 1304. This communication is allowed by the filtering strategy.

[0266] At the same time, the standardized LTE attach procedure continues for UE 104, eNB 102, MME 108, etc. When the eNB 102 sends an attach complete message to the MME 108, it indicates that the UE 104 has obtained its IP address and it can start sending uplink messages. (The UE 104 should try to connect to the P/S proxy 1304, which will be allowed by the filtering strategy at the PGW 114.) When the MME 108 receives the modify bearer response message from the SGW 110, it indicates that it can send the first Downlink data. Therefore, at this moment, the MME 108 can publish a biometric test message to the topic "AF/biometric/&lt;GUMMEI&gt;". This message contains the cell ID and the IMSI of the UE 104 concerned. This message is received by AF 2102. The AF 2102 checks the biometric test pass variable held for the IMSI, and if the variable is set, the biometric test is not performed. AF 2102 can be added to the subject^uAF/biometric/&lt;GUMMEI&gt; sends a UE biometric test information message, so the message is received by the serving MME 108. This message indicates that the UE 104 is allowed to access the cell. On the other hand, if the biometric test pass variable for IMSI is not set, then the biometric test then occurs as follows.

[0267] Similar to that shown in FIG. 25, AF 2102 publishes a biometric test start message to the topic "AF/biometric/test/&lt;IMSI&gt;", where &lt;IMSI&gt; is sent by the MME 108 serving the UE 104 Initiate the value received in the biometric test message. Therefore, the message is transmitted by the P/S proxy 1304 network to the only UE 104 with the value of &lt;IMSI&gt;. At this UE 104, it is consumed by the UE biometric test application 2202. The message may include data such as the type of biometric test that should be performed, or any other data related to the performance of the test. Other data may include: obtaining the GPS location of the UE 104; generating periodic reports of the GPS location; even when the user tries to put the UE 104 in the ECM idle state, or even when the user tries to turn off the UE 104, continue to make the report. (These latter capabilities may be required during military operations or during other government operations.) Initiating biometric test messages can be reliably transmitted by the P/S agent 1304 network. In the case that the user chooses not to input data, the AF 2102 can start a timer to receive the biometric test data from the UE biometric test application 2202. In this case, if the timer expires, AF 2102 can send a UE deny message to MME 108 to indicate that the UE attachment request should be denied. In this case, the MME 108 denies the UE 104 access, and access via the cell where the CB for GU is enabled is denied for the UE 104.

[0268] When the biometric test is performed at the UE 104±, the biometric test application 2202 of the UE 104 issues a biometric test result message to the subject AF/biometric/test/&lt;IMSI&gt;, and the message is still received by the AF 2102. AF 2102 cancels the timer set up to receive the message before and starts the analysis of multiple return data. Depending on the type of test being performed (for example, matching voice phrases, matching fingerprints or other biometric information, matching passwords), the AF 2102 can analyze the data on its own, or it can send the data to another service program to perform the analysis. The analysis reveals whether the T UE 104 should remain attached via the cell where the CB for GU is enabled. When the AF 2102 issues the UE biometric test information message, the determination is returned to the serving MME 108. Therefore, the UE 104 is either denied access to the cell or allowed to maintain access via the blocked cell. In the latter case, AF 2102 can set biometric test pass parameters for IMSI and can start a timer whose duration is determined by the time between biometric tests provided at AF 2102 for a given cell ID Value to set. The purpose of the timer is to avoid testing the UE 104 too frequently. When the timer expires, AF 2102 can reset the biometric test associated with IMSI

With the value of the parameter, another biometric test can be performed for the IMSI of the UE 104. (The value of the time between biometric tests can be set to INDEFINITE (indeterminate) to ensure that only one test is performed for each UE 104, if this is what the government administrator expects.).

[0269] If the UE 104 passes the biometric test, then the AF 2102 can interact with the PCRF 118 via its Rx diameter interface to cause the deletion of the filtering strategy previously installed at the PGW 114.

[0270] Avoid unnecessary paging at a cell where CB for GU is enabled

5.3.4 of TS 23.401 v9.4.0 Section 3 specifies the service request process triggered by the LTE network. When the UE 104 transitions from the ECM active state to the ECM idle state, there is no connection between the UE 104 and the eNB 102, and therefore, there is no communication between the LTE network element and the UE 104. Because the UE 104 was in the ECM active state before, the context is maintained in the MME 108 instance that served the UE 104 last. If if, when in this state, the downlink packet arrives at the UE 104 at the SGW 110, The SGW 110 sends a downlink data notification message to the MME 108. The MME 108 attempts to locate the UE 104 by sending a paging message to one or more eNB 102 units that the MME 108 has determined most likely to cover the area where the UE 104 is located. In a dual-use network, it may be advantageous not to send a paging message to the eNB 102 for transmission using a cell with GU-enabled CB, unless it is first determined that the UE 104 is allowed to access such a cell. Figure 27 shows a modification to a network-triggered service request process that can be effectively used in a dual-purpose LTE network. Note: If the AC priority of the UE 104 (which may have been obtained from the HSS 120 UE subscription data) is kept at the UE 104 ± the following at the MME 108, then the initial access feasibility can be determined by the logic unit in the MME 108 Execution without the need to interact with AF 2102 for this. Figure 27 shows a procedure that can be used when the AC priority of the UE 104 is not maintained in the HSS 120 UE subscription data.

[0271] In FIG. 27, when the MME 108 receives a downlink data notification for the UE 104, it determines that a paging message should be sent thereon in an attempt to reach the set of cells of the UE 104. Using the data provided by the government EMS to the MME 108, the MME 108 can determine the subset of these cells for which CB for GU is enabled. Using a subset of cells, MME 108 can issue a UE paging check message to the topic AF/biometric/&lt;GUMMEI&gt;"", where &lt;GUMMEI&gt; is a unique ID assigned to MME 108. As mentioned earlier, the message is Received at AF 2102.

[0272] For each cell ID in the received message, the AF 2102 can obtain the minimum value of the access priority allowed to access the blocked cell or the value of the allowed high priority access category from the data provided by it. list of. Note: The AC priority value assigned to the cell with the CB for GU enabled may exceed the set of values allowed in the 3GPP standard. Then, the AF 2102 can obtain the AC priority of the UE 104 IMSI from the provided IMSI value or from an accessible database of IMSI values, the IMSI being the value received in the UE paging check message. Note: The AC priority value assigned to the IMSI can exceed the value allowed in the 3GPP standard. If the IMSI is not found in the provided data or in the IMSI database, AF 2102 may return a UE paging check response message to the MME 108 instance, thereby indicating that the paging message for UE 104 has not been sent to the cell received in the request message Any one of them. The MME 108 may initiate paging to other cells, but not those cells that have enabled CB for GU.

[0273] Alternatively, if the AF 2102 locates the UE 104 IMSI in the data provided to it, or in the IMSI database, it can retrieve the AC priority value of the UE 104, and in turn compare it with each blocked Compare the minimum AC priority value provided by the cell, or compare it with the list of allowed high-priority access category values for each cell in the checklist. If the IMSI has a too low priority for a given cell ID, or if the IMSI access priority does not match one of the values allowed for the cell, then AF 2102 can compose a UE page check response message to Indicates that paging is not allowed for the given cell ID. However, if the AC priority of the UE 104 is for a given cell

If the ID is high enough, or matches one of the allowed values, AF 2102 can check the data provided to it to determine whether a biometric test is required for this blocked cell. If not, AF 2102 can compose a UE paging check response message to indicate that paging is allowed for the cell ID, and no biometric test is required. If the biometric test is enabled for a given blocked cell, the AF 2102 can compose a UE paging check response message to indicate that paging is allowed for the given blocked cell ID, and the biometric test is required. When all the cell ID values in the request message have been processed in this way, the AF 2102 can issue a UE paging check response message to the topic "AF/biometric/&lt;GUMMEI&gt;", so it is an instance of the MME 108 sending the request message Received.

[0274] When the MME 108 receives the UE paging check response message, it uses the result of each blocked cell to determine whether the paging message can be sent to the eNB 102 that handles the cell. In this way, no paging message is sent to the cell to which the UE 104 is barred from access by the CB for GU. For those cells that have enabled CB for GU to which paging messages can be sent, MME 108 can save the status of paging in progress to the cell, and can save whether UE 104 is required to access the network through this cell. The status of the biometric test. The following describes the processing modifications to the service request process used to support dual-use networks.

[0275] Automatic processing of restricted users during service requests

Section 5. 4. 3. 1 of TS 23. 401 v9. 4.0 specifies the processing of the service request process initiated by the UE in the LTE network. As described in the previous sections of this document, this procedure is also called when the UE 104 responds to a paging message.

[0276] As shown in the process in FIG. 28, when the MME 108 receives a service request from the eNB 102, the MME 108 can determine whether the cell being accessed is blocked for government use. As previously described, this determination is made based on the provision information that can be sent to it by the government EMS 802. If the cell is not blocked for government use, or if the service request is the result of a paging message (see previous sections of this disclosure), then the service request process is based on the LTE standard (TS 23.401 v9.4.0 of 5. 4. Section 1.3) proceed without modification. However, if the CB for GU is enabled for the cell, and the service request is initiated by the UE, the MME 108 can issue a UESrvcReq check message to the topic "AF/biometric/&lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is allocated to the MME 108 Unique ID. The message contains the IMSI of the UE 104 and the cell ID of the cell being accessed. As mentioned earlier, this message is received by AF 2102. The AF 2102 can perform additional verification via its provided data: the cell ID referenced in the received UESrvcReq check message is indeed the cell where the CB for GU is enabled. (If not, AF 2102 can post a UESrvcReq check response message to the subject "AF/biometric/&lt;GUMMEI&gt;" to indicate that UE 104 has passed the access test, no biometric test is required, and also instruct MME 108 and AF 2102 to provide data Because the subject string includes a unique GUMMEI value, the message is only received by the MME 108 instance that sent the original UESrvcReq check message). Assuming that the cell ID is the cell ID of the cell where the CB for GU is enabled, AF 2102 can obtain it from the data provided Allow access to the minimum value of the access priority of the blocked cell, or obtain a list of high priority access category values that are allowed to access the blocked cell. Note: The AC priority value in this case can exceed the value used in the 3GPP standard, so compared with the case of the 3GPP standard, a more fine-grained distinction can be made for priority users in this case. Then, the AF 2102 can obtain the AC priority of the UE 104 IMSI from the IMSI value it is provided or from an accessible database of IMSI values, where the IMSI is the value received in the UESrvcReq check message. Note: The value of the AC priority assigned to the IMSI of the UE 104 may be greater than the set of values specified in the 3GPP standard. If the IMSI is not found in the provided data or in the IMSI database, the AF 2102 may return a UESrvcReq check response message to the serving MME 108 instance, thereby indicating that the UE 104 service request should be rejected. In this case, the MME 108 may initiate a rejection response to the UE 104.

[0277] Alternatively, if the AF 2102 locates the UE 104 IMSI in the data provided to it, or in the IMSI database, it can retrieve the AC priority value of the UE 104 and compare it with the minimum value provided for the blocked cell. The AC priority value is compared, or compared with the list of allowed high-priority access categories allowed for the cell. If the IMSI has a too low priority, or if the AC priority of the IMSI does not match one of the allowed access category values, AF 2102 may return a UESrvcReq check response message to the MME 108 instance to cause the UE 104 to serve The request was denied. However, if the AC priority of the UE 104 is high enough or matches one of the values allowed for the cell, the AF 2102 can check the data provided to it to determine whether a biometric test is required for this blocked cell. If it is not required, AF 2102 may return a UESrvcReq check response message to the MME 108 instance, thereby indicating that the UE 104 service request processing should continue, and no biometric test is required. If the biometric test is enabled for the blocked cell, AF 2102 can return a UESrvcReq check response message to the MME 108 instance, thereby indicating: UE 104 Service request processing should continue and biometric testing is required.

[0278] If the service request will continue, then the remainder of the process specified in section 5.4.1.1 of TS 23.401 v9.4.0 is completed. When the MME 108 receives the modify bearer response message from the SGW 110, the standardized service request process is completed, but when the accessed cell enables the CB for GU, the MME 108 causes the subsequent additional processing to be performed in the dual-purpose network. See Figure 28.

[0279] When the MME 108 receives the modify bearer response message from the SGW 110 to end the service request process, the MME 108 may check the information stored for the IMSI of the UE 104. If the information indicates that the biometric test should be performed, the MME 108 may issue a biometric test initiation message to the topic "AF/biometric/&lt;GUMMEI&gt;". The message contains the cell ID and the IMSI about the UE 104. The message is received by the AF 2102, and the biometric test then occurs as follows. [0280] Similar to that shown in FIG. 25, the AF 2102 checks the biometric test pass variable held for the IMSI, and if the variable is set, the biometric test is not performed. Instead, the AF 2102 may publish a UE biometric test information message to the topic "AF/biometric/&lt;GUMMEI&gt;", so the message is received by the serving MME 108. This message indicates that the UE 104 is allowed to access the cell. On the other hand, if the biometric test pass variable for the IMSI is not set, then the biometric test then occurs as follows. AF 2102 publishes a biometric test start message to the topic "AF/biometric/test/&lt;IMSI&gt;", where &lt;IMSI&gt; is the initiating biometric test message sent by the MME 108 serving the UE 104 Meter the value received in the test message. Therefore, the message is transmitted by the P/S agent 1304 network to the only UE 104 with the value of &lt;IMSI&gt;, where it is consumed by the UE biometric test application 2202. The message may include data such as the type of biometric test that should be performed, or any other data related to the performance of the test. Other data may include: obtaining the GPS location of the UE 104; generating a periodic report of the GPS location; even when the user tries to put the UE 104 in the ECM idle state, or even when the user tries to turn off the UE 104, continue to make the report. (These latter capabilities may be required during military operations or during other government operations.) This message can be reliably transmitted by the P/S agent 1304 network. In the case that the user chooses not to input data, the AF 2102 can start a timer to receive the biometric test data from the UE biometric test application 2202. In this case, if the timer expires, the AF 2102 can send a UE deny message to the MME 108 to indicate that the UE 104 should be detached from the network. In this case, the MME 108 initiates the detach procedure initiated by the MME, and the UE 104 detaches from the cell where the CB for GU is enabled.

[0281] When the biometric test is performed at the UE 104±, the biometric test application 2202 of the UE 104 issues a biometric test result message to the subject AF/biometric/test/&lt;IMSI&gt;, and the message is still received by the AF 2102. AF 2102 cancels the timer set up to receive the message before and starts the analysis of multiple return data. According to the type of test being performed (for example, matching voice phrases, matching fingerprints or other biometric information, matching passwords), AF

2102 can analyze the data by itself, or it can send the data to another service program to perform analysis. The analysis reveals whether the TUE 104 should remain attached via the blocked cell. When the AF 2102 issues the UE biometric test information message, the determination is returned to the serving MME 108. Therefore, the UE 104 is either detached from the cell or allowed to maintain access via the blocked cell. In the latter case, AF 2102 can set biometric test pass parameters for IMSI and can start a timer whose duration is determined by the time between biometric tests provided at AF 2102 for a given cell ID Value to set. The purpose of the timer is to avoid testing the UE 104 too frequently. When the timer expires, the AF 2102 can reset the value of the biometric test pass parameter associated with the IMSI, so that another biometric test can be performed for the IMSI of the UE 104. (The value of the time between biometric tests can be set to INDEFINITE (indeterminate) to ensure that only one test is performed for each UE 104, if this is what the government administrator expects.).

[0282] Automatic separation of restricted users during handover

The LTE standard specifies two different types of handover procedures. In the first type called X2 handover, the source eNB 102 (that is, the eNB 102 that manages the current cell through which the UE 104 is accessed) and the target eNB 102 (that is, the one that the UE 104 is handing over to) There is a direct communication path between the eNBs 102 that are managed by the cell. When there is no direct path between the source eNB 102 and the target eNB 102, the MME 108 becomes involved in the handover process at an earlier stage of the handover, and uses its S1 link to arrange the communication between the source eNB 102 and the target eNB 102. Therefore, this type of handover is called S1 handover. In X2 handover, the MME does not change, but if the UE 104 is moving to a cell that is not handled by the current (source) SGW 110, the SGW 110 unit can change. In the S1 handover, the new (target) MME 108 may change (ie, relocate), and the new (target) SGW 110 unit may change (ie, relocate). [0283] As shown in FIG. 5 A high-level view of LTE handover processing is presented. There are three different stages in the handover process, namely, the handover preparation phase, the handover execution phase, and the handover completion phase. In the handover preparation phase, the UE 104 in the source eNB 102 is transmitted to the target eNB 102. In the handover execution phase, the UE 104 104 leaves the cell at the source eNB 102, and synchronizes and accesses the cell at the target eNB 102. Once the handover execution phase is completed, uplink and downlink data can be exchanged with the UE 104. In the handover completion phase, the UE 104 GTP channel at the SGW 110 is modified, so the data is sent from the SGW 110 to the target eNB 102 (until the operation is completed, the data is sent to the source eNB 102 and forwarded to the target eNB 102 via the X2 communication path, At the target eNB 102, the data is queued until the data can be sent to the UE 102 without data loss) o

[0284] Section 5.5.1.1.2 of TS 23.401 v9.4.0 specifies the T X2 handover procedure for the case where there is no relocation of the SGW 110. 5. 5. 1. 1. Section 3 provides provisions for X2 handover situations with SGW 110 relocation. In the X2 handover, the MME 108 serves both the source eNB 102 and the target eNB 102, so there is no change in the MME 108, that is, there is no relocation of the MME 108 in the X2 handover. Section 5.5.1.2.2 of TS 23. 40.1 v9. 4.0 provides the provisions for the S1 handover situation, and includes the possibility of relocation of the MME 108 and the relocation of the SGW 110.

[0285] This part of the present disclosure can identify changes in the processing of the MME 108 for implementing dual-use network capabilities when the UE 104 switches to a cell where the CB for GU is enabled. Those skilled in the art can realize that the points used to initiate the MME-AF interaction in the standardization process selected in this article are examples, because other processing points can be selected without changing the result and substantially changing the description provided herein. . In addition, it can be pointed out that if the AC priority of the UE 104 is kept together with the subscription data stored at the HSS 120, when the UE 104 accesses the LTE network for the first time, the AC priority of the UE 104 can be obtained by the MME 108, And the check of the AC priority of the UE 104 with respect to the priority allowed at the cell where the CB for GU is enabled can be used when there is no need to interact with the AF 2102 for this purpose.

The following is executed by MME 108.

[0286] X2 handover in the dual-purpose network In X2 handover, the MME 108 first learns of the handover at the beginning of the handover completion phase. The target eNB 102 sends an LTE path switch message to the MME 108, and recognizes the UE 104 and the target cell ID. Figure 29 shows an introduction of additional MME 108 processing for implementing a dual-use network. When receiving the path switching message, the MME 108 determines whether the CB for GU is enabled in the target cell according to the data provided to it. If not, then the X2 switching process remains unchanged. However, if the target cell enables the CB for GU, the MME 108 can check the UE 104 ± the following data it holds, and determine whether the UE 104 is making a high-priority call, or is making an emergency call (ie, checking the UE 104's Establish reason value). If the UE 104 is making a normal call, or if the UE 104 is making an emergency call, but E911 calls are not allowed at the target cell, the MME 104 can return a path switch request failure message to the target eNB 102, and can start the MME for the UE 104 Initiated separation process.

[0287] If the UE 104 is making a high-priority call, the MME 108 needs to determine whether the AC priority of the UE 104 is high enough to be allowed to access the target cell. Therefore, the MME 104 can issue a UEX2 handover check message to the topic "AC/biometric/&lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is the unique ID assigned to the MME 108 instance. As noted in this article, this message is received by AF 2102. The message contains the IMSI of the UE 104 and the cell ID of the cell being accessed. The AF 2102 can perform additional verification via its provided data: the cell ID referenced in the received UEX2 handover check message is indeed enabled for GU CBs cell. (If not, AF 2102 can issue a UEX2 handover check response message to the subject "AF/biometric/&lt;GUMMEI&gt;" to indicate that UE 104 has passed the access test and does not require biometric testing, and also instruct MME 108 and AF 2102 to provide Inconsistent data. Because the subject string includes a unique GUMMEI value, this message is only received by the MME 108 instance that sent the original UEX2 handover check message). Assuming that the cell ID is the cell ID of the cell where the CB for GU is enabled, then AF 2102 can obtain The data it provides obtains the minimum value of the access priority that allows access to the blocked cell, or the list of high priority access category values that allow access to the cell. Note: The value received in this case can exceed the set of values allowed by the 3GPP standard. Then, the AF 2102 can obtain the priority of the UE 104 IMSI from the IMSI value it is provided or from an accessible database of IMSI values, where the IMSI is the value received in the UEX2 handover check message. Note: The value of the AC priority assigned to the IMSI of the UE 104 in this case can exceed the set of values allowed by the 3GPP standard, so that compared with the standard cell blockade feature, it can be implemented for the CB feature for GU. A more fine-grained identification of the AC priority category of the UE 104. If the IMSI is not found in the provided data or in the IMSI database, the AF 2102 may return a UEX2 handover check response message to the serving MME 108 instance, thereby indicating that the UE 104 handover should fail. In this case, the MME 108 may send a path switch request failure message to the target eNB 102, and then initiate the MME-initiated separation process for the UE 104.

[0288] Alternatively, if the AF 2102 locates the UE 104 IMSI in the data provided to it, or in the IMSI database, it can retrieve the AC priority value of the UE 104 and compare it with the minimum value provided for the blocked cell. The AC priority value is compared, or compared with the list of allowed high-priority access category values. If the IMSI has too low priority, or does not match one of the allowed high priority values, AF 2102 may return a UEX2 handover check response message to the MME 108 instance to cause the UE 104 to fail handover, and the UE 104 separation. However, if the AC priority of the UE 104 is high enough, or if it matches one of the allowed high priority values, then AF 2102 can check the data provided to it to determine whether a biologic is required for this blocked cell. Measurement test. If it is not required, AF 2102 may return a UEX2 handover check response message to the MME 108 instance, thereby indicating: UE 104

The handover process should continue and no biometric testing is required. If the biometric test is enabled for the blocked cell, the AF 2102 may return a UEX2 handover check response message to the MME 108 instance, thereby indicating that the UE 104 handover process should continue and the biometric test is required.

[0289] If the X2 handover process will continue, then some parts of the process will follow as specified in 5.5.1.1.2 of TS 23.401 v9.4.0 until there is no relocation of the SGW 110 In the case, the modified bearer response is received by the MME 108. In the case of SGW 110 relocation, some parts of the process are then as specified in 5.5.1.1.3 of TS 23.401 v9.4.0, until the session creation response is received by MME 108. When the MME 108 receives the Modify Bearer Response/Create Session Response message from the SGW 110, the MME 108 checks whether a biometric test is required for the UE 104, and if necessary, initiates an interaction with the AF 2102 to perform the biometric test. See Figure 29 .

[0290] As shown in FIG. 29, the MME 108 may post a biometric test initiation message to the topic "AF/biometric/&lt;GUMMEI&gt;". This message contains the cell ID and the IMSI of the UE 104 concerned. The message was received by AF 2102, and the biometric test then took place as follows.

[0291] Similar to that shown in FIG. 25, the AF 2102 checks the biometric test pass variable held for the IMSI, and if the variable is set, the biometric test is not performed. Instead, the AF 2102 can publish a UE biometric test information message to the topic "AF/biometric/&lt;GUMMEI&gt;", so the message is received by the serving MME 108. This message indicates that the UE 104 is allowed to access the cell. On the other hand, if the biometric test pass variable for the IMSI is not set, then the biometric test then occurs as follows. The AF 2102 may publish a biometric test initiation message to the topic AF/biometric/test/&lt;IMSI&gt;, where &lt;IMSI&gt; is the value received in the biometric test initiation message sent by the MME 108 serving the UE 104. Therefore, The message is transmitted by the P/S agent 1304 network to the only UE 104 with the value of &lt;IMSI&gt;, where it is consumed by the UE biometric test application 2202. The message may include information such as the biometric test that should be performed Type of data, or any other data related to the execution of the test. Other data may include: obtaining the GPS location of the UE 104; generating periodic reports on the GPS location; even when the user tries to connect the UE When 104 is placed in the ECM idle state, or even when the user tries to turn off the UE 104, the report continues to be made. (These latter capabilities may be required during military operations or during other government operations.) The message can be reliably transmitted by the P/S agent 1304 network. In the case where the user chooses not to input data, the AF 2102 may start a timer to receive the biometric test data from the UE biometric test application 2202. In this case, if the timer expires, the AF 2102 can send a UE deny message to the MME 108 to indicate that the UE 104 should be detached from the network. In this case, the MME 108 initiates the MME-initiated detach procedure, and the UE 104 detaches from the cell where the CB for GU is enabled.

[0292] When the biometric test is performed at the UE 104±, the biometric test application 2202 of the UE 104 issues a biometric test result message to the subject AF/biometric/test/&lt;IMSI&gt;, and the message is still received by the AF 2102. AF 2102 cancels the timer set up to receive the message before and starts the analysis of multiple return data. Depending on the type of test being performed (for example, matching voice phrases, matching fingerprints or other biometric information, matching passwords), the AF 2102 can analyze the data on its own, or it can send the data to another service program to perform the analysis. The analysis reveals whether the TUE 104 should remain attached via the blocked cell. When the AF 2102 issues the UE biometric test information message, the determination is returned to the serving MME 108. Therefore, the UE 104 is either detached from the cell or allowed to maintain access via the blocked cell. In the latter case, the MME 108 can continue the X2 handover process by sending a path switch request Ack message to the target eNB 102, and execute TS 23.401 v9. 4, 0 for the remaining processing indicated. At the same time, the AF 2102 can set biometric test pass parameters for the IMSI and can start a timer whose duration is set by the value of the time between biometric tests provided at the AF 2102 for a given cell ID. The purpose of the timer is

Avoid testing the UE 104 too frequently. When the timer expires, the AF 2102 can reset the value of the biometric test pass parameter associated with the IMSI, so that another biometric test can be performed for the IMSI of the UE 104. (The value of the time between biometric tests can be set to INDEFINITE (indeterminate) to ensure that only one test is performed for each UE 104, if this is what the government administrator expects.).

[0293] S1 Handover in Dual-Purpose Network

Section 5.5.1.2.2 of TS 23.401 v9.4.0 specifies the S1 handover process, and covers the case of MME 108 relocation and SGW 110 relocation. These standard specifications show that the MME 108 participates in all three stages of the S1 handover process. Here again, it is pointed out that there may be multiple possible points suitable for inserting the extra behavior required in the dual-use network in the S1 handover process. Regardless of the point selected in the S1 handover process, the results of these interactions must be the same, that is, the AC priority of the UE 104 must be checked to determine whether the UE 104 can remain attached through the target cell with the CB for GU enabled, and If the target cell with the CB for GU enabled is configured for such a test, then a biometric test is performed. Figure 30 shows the points in the S1 handover process selected in this article to show how additional processing can be used to implement dual-use networks.

[0294] In S1 handover, when the MME 108 (if it involves MME relocation, then the target MME 108) receives a handover notification message from the target eNB 102, it first learns the identity of the target cell. This message is sent during the handover completion phase, so the UE 104 has been synchronized with the target cell and can perform uplink and downlink data exchange with the UE 104. As shown in FIG. 30, the reception of the modify bearer response message from the (target) SGW 110 is used to trigger additional actions required in the dual-purpose network. The selection of this processing point ensures that the (target) MME 108 starts the deletion timer for the indirect data forwarding path in case the check performed for the dual-use network causes the UE 104 to detach.

[0295] When the (target) MME 108 receives the modify bearer response message, it can check the data provided to it to determine whether the target cell has enabled the CB for GU. If not, the S1 switching process continues without modification. However, if the target cell has enabled the CB for GU, the MME 108 can check the UE 104 ± the following data it holds, and determine whether the UE 104 is making a high-priority call, or is making an emergency call (ie, checking the UE 104s Establish reason value). If the UE 104 is making a normal call, or if the UE 104 is making an emergency call but E911 calls are not allowed at the target cell, the MME 108 may initiate the MME-initiated separation process for the UE 104.

[0296] If the UE 104 is making a high-priority call, the MME 108 needs to determine whether the AC priority of the UE 104 is high enough or matches one of the allowed high-priority AC values in order to be allowed to access the target Community. Therefore, the MME 108 may issue a UES1 handover check message to the topic "AC/biometric/&lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is the unique ID assigned to the MME 108 instance. As noted in this article, this message is received by AF 2102. The message contains the IMSI of the UE 104 and the cell ID of the cell being accessed. The AF 2102 may perform additional verification via its provided data: the cell ID referenced in the received UE S1 handover check message is indeed the cell where the CB for GU is enabled. (If not, AF 2102 can issue a UE S1 handover check response message to the subject "AF/biometric/&lt;GUMMEI&gt;" to indicate that UE 104 has passed the access test, no biometric test is required, and also instruct MME 108 to interact with AF 2102 Provide inconsistencies between the data. Because the subject string includes a unique GUMMEI value, Therefore, this message is only received by the MME 108 instance that sent the original UE S1 handover check message). Assuming that the cell ID is the cell ID of the cell where the CB for GU is enabled, AF 2102 can obtain the minimum value of the access priority that allows access to the blocked cell from the data it provides, or the high access priority that allows access to the cell. Enter a list of priority values for the category. Note: The AC priority value can exceed the value allowed by the 3GPP standard in this case. Then, AF 2102 can obtain the access category priority of UE 104 IMSI from the IMSI value it is provided or from the accessible database of IMSI value, IMSI

It is the value received in the UE S1 handover check message. Note that in this case, the value of the AC priority assigned to the IMSI of the UE 104 can exceed the set of AC priority values allowed in the 3GPP standard, so that a finer granularity can be obtained compared to what is possible in the standardized 3GPP cell blocking feature The identification of the UE 104 access priority category. If the IMSI is not found in the provided data or in the IMSI database, the AF 2102 may return a UE S1 handover check response message to the serving MME 108 instance, thereby indicating that the UE 104 handover should fail. In this case, the MME 108 may initiate the MME-initiated separation procedure for the UE 104.

[0297] Alternatively, if the AF 2102 locates the IMSI of the UE 104 in the data provided to it, or in the IMSI database, it can retrieve the AC priority value of the UE 104 and compare it with the minimum value provided for the blocked cell. Compare the AC priority value or compare it with the list of allowed priority values for high access categories. If the IMSI has a too low priority or does not match one of the allowed values, AF 2102 may return a UE S1 handover check response message to the MME 108 instance to cause the UE 104 to be separated. However, if the AC priority of the UE 104 is high enough, or matches one of the allowed high-priority access category priority values, then the AF 2102 can check the data provided to it to determine for the blocked cell Whether biometric testing is required. If it is not required, AF 2102 may return a UE S1 handover check response message to the MME 108 instance, thereby indicating that the UE 104 handover process should continue, and no biometric test is required. If the biometric test is enabled for the blocked cell, the AF 2102 may return a UE S1 handover check response message to the MME 108 instance, thereby indicating that the UE 104 handover process should continue and the biometric test is required.

[0298] If the reception of the UE S1 handover check response message indicates that the UE 104 is allowed to access, but no biometric test is required, the MME 108 can continue the S1 handover process without further modification. However, if the message indicates that a biometric test is required, the MME 108 may initiate an interaction with AF 2102 to perform the biometric test. See Figure 30.

[0299] As shown in FIG. 30, the MME 108 may post a biometric test initiation message to the topic "AF/biometric/&lt;GUMMEI&gt;". This message contains the cell ID and the IMSI of the UE 104 concerned. The message was received by AF 2102, and the biometric test then took place as follows.

[0300] Similar to that shown in FIG. 25, the AF 2102 checks the biometric test pass variable held for the IMSI, and if the variable is set, the biometric test is not performed. Instead, the AF 2102 can publish a UE biometric test information message to the topic "AF/biometric/&lt;GUMMEI&gt;", so the message is received by the serving MME 108 instance. This message indicates that the UE 104 is allowed to access the cell. On the other hand, if the biometric test pass variable for the IMSI is not set, then the biometric test then occurs as follows. The AF 2102 may publish a biometric test initiation message to the topic "AF/biometric/test/&lt;IMSI&gt;", where &lt;IMSI&gt; is the value received in the biometric test initiation message sent by the MME 108 serving the UE. Therefore, the message is transmitted by the P/S proxy 1304 network to the only UE 104 with the value of &lt;IMSI&gt;, where it is consumed by the UE biometric test application 2202. The message may include data such as the type of biometric test that should be performed, or any other data related to the performance of the test. Other data may include: obtaining the GPS location of the UE 104; generating periodic reports on the GPS location; even when the user tries to connect the UE When 104 is placed in the ECM idle state, or even when the user tries to turn off the UE 104, the report continues to be made. (These latter capabilities may be required during military operations or during other government operations.) This message can be reliably transmitted by the P/S agent 1304 network. In the case where the user chooses not to input data, the AF 2102 may start a timer to receive the biometric test data from the UE biometric test application 2202. In this case, if the timer expires, the AF 2102 can send a UE deny message to the MME 108 to indicate that the UE 104 should be detached from the network. In this situation

Next, the MME 108 initiates the MME-initiated separation process, and the UE 104 is separated from the cell where the CB for GU is enabled. [0301] When the biometric test is performed at the UE 104±, the biometric test application 2202 of the UE 104 issues a biometric test result message to the subject AF/biometric/test/&lt;IMSI&gt;, and the message is still received by the AF 2102. AF 2102 cancels the timer set up to receive the message before and starts the analysis of multiple return data. Depending on the type of test being performed (for example, matching voice phrases, matching fingerprints or other biometric information, matching passwords), the AF 2102 can analyze the data on its own, or it can send the data to another service program to perform the analysis. The analysis reveals whether the TUE 104 should remain attached via the blocked cell. When the AF 2102 issues the UE biometric test information message, the determination is returned to the serving MME 108. Therefore, the UE 104 is either detached from the cell or allowed to maintain access via the blocked cell. In the latter case, MME 108 can continue with Figure 5.5.1. 2. of TS 23.401 v9.4.0. S1 switching process indicated in 2-1. At the same time, the AF 2102 can set biometric test pass parameters for the IMSI and can start a timer whose duration is set by the value of the time between biometric tests provided at the AF 2102 for a given cell ID. The purpose of the timer is to avoid testing the UE 104 too frequently. When the timer expires, the AF 2102 can reset the value of the biometric test pass parameter associated with the IMSI, so that another biometric test can be performed for the IMSI of the UE 104. (The value of the time between biometric tests can be set to INDEFINITE (indeterminate) to ensure that only one test is performed for each UE 104, if this is what the government administrator expects.).

[0302] Use access blocking and roaming restrictions to protect government bases. In some cases, it may be desirable to allow only restricted users to gather access to government-controlled areas or cells that provide coverage to the base. One method that can be used is to allocate all cells that provide RF coverage to the base to a closed subscriber group (CSG). The CSG is then broadcast in one of the system information blocks sent periodically by each cell. Only UEs 104 whose SIM cards are configured with a specific CSG value bound to each of these cells are allowed to access those cells. This method may have the following vulnerabilities or problems. Invalid users may gain access to the CSG value of the cell (just by monitoring the system information sent by these cells), and may be able to put the CSG value in their SIM card. Then these invalid UEs 104 can access the cell. Second, it may be necessary to allow access to personnel who are not normally present at the base and therefore are not equipped with UE 104 with a specifically configured CSG. Because of these problems, it is desirable to use another method to restrict access to cells covering government bases. The cell blockade and roaming restrictions described in this disclosure can provide a good alternative to providing restricted access.

[0303] The roaming concept can be used as the first line of defense to prevent unauthorized access to cells covering government bases. Each of these cells may be provided with a set of permitted roaming networks covering government users authorized to access these cells. The roaming list may be an empty list, so only UEs from the home network belonging to these cells and from the set of equivalent networks belonging to these cells are allowed to access these cells. In this case, it may be that all government users have UE 104 in one PLMN (MCC, MNC), where members of different government agencies can be distinguished by using different IMSI ranges for members of different agencies. Or, as mentioned earlier, the IMSI values can be assigned to members of different government agencies in different equivalent networks.

[0304] Cells that provide RF coverage for government bases can also be placed in one or more tracking areas (TAs), where TA only includes cells that cover government bases. By providing data, it is possible to send a handover restriction list containing the cell covering the government base to the MME 108 in the LTE network that submits the neighboring cell to the cell covering the government base. Then, the handover restriction list can be transmitted to all UEs 104 that are not eligible to access the cell covering the government base. The list can also be transmitted to all UEs 104 on neighboring cells that are not allowed to access the cell covering the government base for other reasons.

If the target cell is a cell covering a government base, then these UE 104 handovers are prohibited.

[0305] It is also possible to further restrict access to these cells by introducing cell blockade for government use to cells covering government bases. In this case, the UE 104 that can access these cells must be a high-priority UE 104. The capabilities previously described for the CB for GU in this disclosure can then be applied. Therefore, the verification check of the IMSI of the UE 104 and the AC priority value of the UE 104 relative to the access priority allowed in the restricted cell can be performed by an entity separate from the UE 104 (ie, by the MME 108, or by the deployment in the LTE network). Optimize the execution of AF 2102 running on the server 304. In addition, the user identity can be verified via the biometric test previously described in the present disclosure. These inspections and biometric tests are performed as described herein.

[0306] APN LTE network government and commercial applications used as a platform for sensor data collection, processing, storage, and distribution are increasingly using various types of sensors to collect information. Sensors may include image capture devices, video capture devices, audio capture devices, scanning devices, chemical detectors, smoke detectors, and so on. Sensors can be carried on aerial drones or manned aircraft, or deployed in mobile vehicles or robots on the ground, or they can be deployed at fixed points such as lamp posts, buildings or buildings, supermarkets, or other In shopping areas, in mobile phones carried by multiple users, etc. It can be seen that the amount of data collected by sensors in different applications is growing rapidly. The sensor data needs to be collected and sent to the points where it can be stored and processed. Depending on the application, data from multiple sensors of the same or different types may need to be analyzed together to generate results, or three-level data may be generated, and then the data may need to be distributed to one or more endpoints for further processing or for making Decided. Wireless technology can provide beneficial ways to acquire and transmit data collected by sensors. However, the amount of data that needs to be collected in a sensor-based application may exceed the capacity of current wireless networks. In addition, wireless networks with the ability to efficiently and quickly acquire, process, store and distribute sensor data are not available. These capabilities are referred to as the characteristics of the sensor platform in this article.

[0307] The system described herein uses the parts of the APN LTE wireless network presented in the previous sections of this disclosure plus additional concepts to create the sensor platform outlined in the previous paragraphs. These aspects can include: the higher data capacity that can be provided by using APN network beamforming technology, the ability to co-locate the optimization server 308 with the eNB 102 unit close to the wireless access point of a large set of sensors, The ability to use publish/subscribe 1304 communication in the APN LTE wireless network to collect and distribute sensor data between large collections, and the ability to use optimization servers 304 and 308 as storage and analysis processing points for sensor data. As disclosed in the following example scenarios illustrating the present disclosure, these capabilities can be used to build a large collection of sensor-based applications. Those skilled in the art can understand that the example shown in this article is an illustration of the capabilities and applicability of the APN LTE wireless network in providing sensor platforms, and the capabilities described in this article can be used to build many other sensor-based applications .

[0308] Using optimized servers and publish/subscribe messaging to process data from multiple sensors FIG. 13 shows a publish/subscribe (P/S) agent 1304 that can be used to provide a means to interconnect a collection of multiple endpoints The middleware messaging system, in this case, can be a variety of collections of sensors, computer programs for processing and storing sensor data, and user terminals and devices that can receive the results of sensor data processing and data distribution. According to the teachings disclosed in the previous sections of this disclosure, the publishing endpoint 1308 and the subscribing endpoint 1310 do not directly interact with each other and are therefore decoupled. Decoupling provides benefits in that these entities (for example, sensors, processors, user terminals) can be added to or removed from the network without affecting any publisher 1308 or any subscription to the data being sent or receivedBy1310's behavior. All communicating entities can have a connection to the P/S proxy 1304 network

Through the connection, it can send to or receive from multiple other endpoints. The publisher 1308 can send a packet, and any copy of the packet that needs to reach multiple subscribers 1310 is handled by the P/S proxy 1304 middleware. Therefore, the system is efficient and can be operated in a simpler way than other communication architectures.

[0309] FIG. 14 shows an example deployment of a P/S proxy 1304 instance that can be deployed on the set of optimization servers 304 and 308 in an APN LTE wireless network. Note: At least one OptServereNB 308 is associated with each eNB 102 network element. In addition, the OptServerPGW 304 may be associated with the PGW 114 serving users accessed via the eNB 102 unit. The teachings in this disclosure also describe how the UE bearer 302 can be redirected to the eNB 102 so that it connects to the OptServer eNB 308 associated with the eNB 102. This process can give the UE 104 a short path to the services that can be provided by the OptServer eNB 308, especially allowing the UE 104 to connect to an instance of the P/S proxy 1304 that can run on the server 308. In addition, the use of the redirected bearer 312 may result in the reduction or elimination of the use of backhaul 112 resources when sending data to or when receiving data from the UE 104. When the server is running at OptServereNB 308± associated with the eNB 102 serving the UE 104, it can also cause the lowest delay in sending or receiving data from the server program to/from the UE 104. In this example, UE 104 may be a sensor, or it may It is a user terminal that displays sensor data or controls sensors that can be connected via this type of LTE wireless network. The number of sensors connected to the network may be large, especially when the beamforming system mentioned in this disclosure is used at the eNB 102 unit to increase the system capacity. Many sensors may be able to connect to the LTE network at each eNB 102 unit.

[0310] In the past ten years, several universities around the world have participated in the regulation and construction of a service architecture that can accommodate collaborative audio and video conferences. These types of services may be exactly what is needed to support troops deployed to serve the scene, or to support emergency rescuers at the scene of a disaster, or to support various types of commercial services involving sensors. People involved in emergency rescue or military operations may require collaborative audio communication. The video stream may be generated by sensors and may need to be distributed to a collection of people who need this information to improve their decision-making capabilities and notify them before proceeding to the next step. Likewise, large collections of images taken by sensors may need to be stored so that they can be subsequently sent to users who need to make decisions based on the content of these images. The ability to use the P/S proxy 1304 middleware of the APN LTE wireless network to interconnect sensors with users in a conference arrangement can facilitate the storage, processing, and distribution of communication needs of applications involving sensors. These services can also naturally extend into the business world, although they may use person-to-person or sensor-to-person communications more frequently than conference services. However, the conference service can have its place in the business field, and the P/S agent 1304 communication can facilitate the operation of the conference service. At the same time, person-to-person and sensor-to-person communication can also be efficiently processed by using the P/S proxy 1304 middleware described in this disclosure.

[0311] FIG. 31 shows a minimum set of functions that may need to use P/S proxy 1304 middleware for communication to set up and manage multimedia conference services. Figure 31 shows how these functions can be distributed among the sets of optimization servers 304 and 308 that can be deployed in the APN LTE wireless network. The conference resource library 3110 may contain a list of scheduled conferences, along with a set of IMSI values of users 104 who are allowed to access the conference, and the role of each user 104 in the conference (for example, specific types of sensors, general participants, chairpersons, etc.) Speaker, audience), and the start and end time of the meeting. The conference manager 3102 can start and terminate the conference, interact with the session manager 3104 to add or delete specific types of sessions (for example, audio, video, alarm), and manage the orderly use of conference resources by participants. The session manager 3104 can interact with the media server 3108 to initiate and delete media types from the conference. The media server 3108 can provide

Services specific to the same type of media. The session manager 3104 is an interface point for sensors, devices, and users 104 that wish to participate in a specific session associated with a conference that an endpoint (sensor, device, or user 104) has joined.

[0312] The general idea presented in FIG. 31 is that the optimization servers 304 and 308 and the associated P/S proxy 1304 communication middleware can be used as a platform for receiving, processing, storing, and redistributing sensor data in an LTE wireless network . Conference capabilities may be needed to facilitate the implementation of allocation and collection functions (depending on the application), and can be used to organize sensor processing and end-user resources into one application. Other functions required for specific sensor applications can be deployed on the set of optimization servers 304 and 308, and can be connected to the P/S agent 1304 system. There are no restrictions on the types of functions that can be added. The following subsections of the present disclosure describe the collection of additional functions such as the image server 3302 and the alarm server 3304 that receive, process, store, and redistribute sensor data as part of a specific application. The inclusion of these functions can be used to show how the APN LTE wireless network can be used as a platform for building sensor applications.

[0313] The deployment of these sensor services may be at the optimization server 304 associated with the PGW 114, or may be at the optimization server 308 associated with the eNB 102. The choice may depend on the location of the human and machine participant sensors to which the sensor is applied. As described below, selecting appropriate servers 304 and/or 308 to perform functions can result in substantial savings in bandwidth utilization on network communication links 112 and 704 and/or delays in obtaining information from or to endpoints. Greatly reduced.

[0314] Emergency application example involving sensors This example application of sensors can be used to show that the ability to be implanted in an APN LTE wireless network can be used as a platform for building sensor-based applications. The collection of various sensor capabilities is used in this example to emphasize and show how to use the sensor platform.

[0315] When a disaster occurs, it often happens that the wireless infrastructure mode required to support the communication needs of emergency responders is destroyed along with other infrastructures. The enhanced data capacity of APN beamforming technology and the use of optimized server 304 and 308 technologies in the APN network can be used to restore LTE wireless capabilities in areas where emergency responders must work. In addition, the deployment of an associated set of publish/subscribe broker 1304 messaging middleware and conferencing software can be used to support emergency sensor data collection, analysis, and distribution that are critical to the safety of responders and the success of emergency operations. The details provided in this disclosure may show how to solve these aspects. Multimedia conferencing capabilities are also important for response teams and staff who are far from the operating area in the guide. The ability to co-locate service applications with eNB 102 units provides savings in backhaul 112 usage and minimizes the delay in providing information to the response team. The following example scenarios can show how the APN network can be used to support the important requirements of these emergency action applications.

[0316] An example scenario showing the use of the APN LTE wireless network as a sensor platform is a scenario where wireless infrastructure has been deployed in a disaster area. Therefore, the unmanned aerial vehicle (UAV) 708 is used to deploy the eNB 102 unit and the OptServer eNB 308 unit above the disaster area. The UAV-based APN network deployment shown in Figure 32 can be used in this example scenario. It is assumed that the single eNB 102 carried in the UAV 708 is sufficient to cover the emergency operation area. Although FIG. 32 shows the use of a second UAV 710 for carrying enhanced packet core (EPC) components (MME 108, SGW 110, and PGW 114), those skilled in the art understand that: from eNB 102 to Ground-based EPC communication is another possible deployment option.

[0317] Table 7 shows the subjects and functions involved in the communication and processing aspects of the emergency action operation example scenario, and indicates where each function can be deployed in the architecture. The functional architecture for this scenario is shown in Figure 33. Fig. 34 shows the deployment architecture for this scenario (a person skilled in the art should understand that: due to the lack of space in the figure, Fig. 34 does not show all the service functions listed in Table 7).

[0318] Table 7: Actors, deployment and descriptions for an example emergency action scenario involving sensors

<td>Features</td><td>description</td><td>Where to deploy</td><td>Annotation</td>

<td>Emergency response personnel team members and their UE equipment 3310</td><td>People involved in the activities of the first responders in the emergency operation area.</td><td>Deployed in the entire operating area.</td><td>All are in the audio conference call, so their actions can be coordinated and modified based on the conditions in the field.</td>

<td>Conference chairman UE device 3308 or 3310</td><td>The entity is recognized by the conference software as being able to make decisions about the conference.</td><td>Usually, one of the emergency responders 3310, or someone at the headquarters 3308.</td><td>Decide whether to give the "participants" of the meeting to others; decide whether someone who is not on the initial attendance list can join the meeting.</td>

<td>Command personnel and their UE equipment (computers, mobile phones) 3308</td><td>The personnel who respond to the actions of the personnel 3310 and the sensors 3312 and 3314 can be coordinated.</td><td>Deploy in a fixed location away from the operating area.</td><td>An audio conference is being conducted with all responders 3310 and command personnel 3308, and has control of the robot sensors 3314 deployed in the emergency operation area.</td>

<td>Conference Manager 3102</td><td>The software service function to manage the meeting.</td><td>Deployed on 0ptServer_PGW304 Node_t </td><td>Start the meeting, terminate the meeting, interact with the session manager 3104 to start and terminate the media session. Maintain a database of meeting participants and session templates. Maintain a collection of the roles played by participants in the conference, including the identity of the conference chairperson.</td>

<td>Session Manager 3104</td><td>A software service function that manages media sessions (for example, audio session 3324, video session 3328, alarm session 3330, robot control session 3332) that are part of the conference. Participants are permitted to join the conversation of their choice and send a message to initiate communication within the conversation.</td><td>Deployed on 0ptServer_PGW304 Node_t </td><td>Generally, sessions for the conference are created based on control commands from the conference manager software, and data streams used by the participants to be used in each of these sessions are managed.</td>

<td>Media Processing Server 3108</td><td>Audio mixer 3318 for processing multiple audio streams arriving at the same time. Distribute the mixed audio stream to each participant. A video mixer 3320 for processing multiple parallel video streams in a video session. A frame grabber 3322 used to "capture" a single image from each video stream, so that a representation of the user or sensor video can be displayed on each participant's 3308 or 3310 device. Other functions can include speech encoder conversion.</td><td>Deployed in the 0ptServer associated with the eNB 102 unit serving the emergency operations area_eNB308 on.</td><td>When the participant's audio stream is added to the conference, the participant's stream is added to the audio stream mixing function 3318, and contains all participants 3308 and 3310 except the one published to the unique topic subscribed by the added participant 3308 or 3310 Audio streaming.</td>

<td>Fixed sensor (dedicated UE for LTE network) 3312</td><td>In this scenario, the fixed sensor is carried by the robot to a certain point and dropped into place under the command of the operator 3308 or 3310. These sensors detect things such as fire, smoke, specific chemicals, actions, sounds, etc. No video.</td><td>Based on the command from the command center 3308 or from the first responder 3310 to the mobile robots carrying them, they are placed in the entire emergency operation area.</td><td>The fixed sensor 3312 was not involved in the meeting. Instead, they send their data to the fixed sensor data analysis server 3304.</td>

<td>Mobile sensor (dedicated UE installed on the robot in the case of LTE network) 3314</td><td>In this scenario, these sensors are installed on the mobile robots and the movement of these robots in the emergency operation area is controlled by the command staff 3308 or the first responder 3310. The video stream they generate is part of the meeting. Their control data stream is also used to control the movement of robots carrying sensors.</td><td>The sensors installed on the robot are distributed throughout the emergency operation area.</td><td>When the sensor installed on the robot is set up near the operation area, the personnel 3308 of the command or the first responder 3310 place the robot at a point where the fixed sensor 3312 carried by the robot can be placed. Further control commands direct the robot to other points in the operating area, where the conference participants are assigned videos of the area at these points.</td>

<td>Fixed sensor data analysis server 3304</td><td>This function receives data from each of the fixed sensors 3312 deployed in the emergency operation area. If it is determined that there is an alarm condition, an alarm is issued to all conference participants 3308 and 3310 set up to receive the alarm.</td><td>Deployed on 0ptServer_PGW304 Node_t </td><td>Each conference participant 3308 or 3310 can obtain details about the alarm, including the type of alarm (for example, the movement or sound from the detected disaster victim), the location of the sensor, and so on. The command 3308 (or any participant 3310 who obtains full conference control) can direct the sensor 3314 installed on the robot to reach the alarm position and send video information.</td>

<td>Image server 3302</td><td>The image sent from the camera integrated into the UE 3310 of the responding team member is stored. Images are delivered to participants 3308 and 3310 for display.</td><td>Deployed in the 0ptServer associated with the eNB 102 unit serving the emergency operations area_eNB308 on.</td><td>During emergency operation, you can take many detailed photos of different areas to get a closer, different and better observation of the scene. Tuyu can be used for historical comparison, or for near real-time information collection and analysis.</td>

<td>P/S agent 1304</td><td>An attachment point is provided for each entity (sensors 3312 and 3314, UE 3308 and 3310) involved in accessing the APN LTE network and obtaining the services provided on the APN optimization servers 304 and 308. Allow connected entities to publish and subscribe to "topics". Route messages published to a topic to all entities subscribed to that topic.</td><td>Deployed on 0ptServer_PGW304 And 0ptServer_eNB308 on.</td><td>Decouple the sender of the data from the receiver of the data. Allow any number of publishers and subscribers to participate in the service, and allow entities to be dynamically added to or removed from the service.</td>

[0319] Because the media server 3108 is deployed on the OptServerPGW 304 located above the emergency operation area, all audio and video data streams can be mixed and transmitted to the team members of each first responder 3310 who seldom use the backhaul 112 interface . The audio data stream from each first responder 3310 can be routed via its redirected dedicated LTE bearer 312 to the OptServereNB 308 associated with eNB2 102 covering the operating area. The audio streams are mixed in the media server 3108, so parallel groups of audio streams from different users can appear in each parameter.

100

Participants 3308 and 3310 in a single audio data stream received from the media server 3108 (packets sent by a specific user 3308 or 3310 are not mixed in the audio stream returned to that user). Because the redirected bearer 312 is used to carry data to/from the UE 3310 and the OptServereNB 308, the backhaul 112 is not used for these interactions, where the media server 3108 performs (see Figure 3 for the meaning of the redirected bearer 312).

[0320] If the UE 3308 in the steering section joins the audio session 3324 of the conference, the audio packets from the UE 3308 can be routed to the PGW 114 associated with the PGW 114 via the P/S proxy 1304 associated with the eNB_1 102 and via the wireless backhaul 112. The P/S proxy 1304, the P/S proxy 1304 associated with the eNB_2 102, and then route to the media server 3108. The audio stream generated at the media server 3108 that is mixed for the UE 3308 can be routed via the opposite path. Therefore, a lower packet delay can be achieved for the first responder group members 3310, and the overall lower backhaul 112 usage than the traditional architecture can be achieved.

[0321] The image server 3302 may be deployed on the OptServereNB 308 associated with the eNB_2 102. Therefore, no backhaul 112 can be used to store the images collected by the first responder 3310 team members. Because each image is a large file, the backhaul 112 savings of using this architecture is enormous. When uploading an image, the application of UE 3310± for image processing can add tags of date, time, GPS coordinates, and user comments to the image. By interacting with the image server 3302, the UE 3308 or 3310 in operation can obtain a list of images filtered by the metric set by the user. Therefore, any user can view an arbitrarily large collection of detailed images that can be recorded during the group action. In this case, because of the APN optimization server 304 and 308 architecture, the image from OptServereNB 308 is downloaded to the UE 3310 or 3308 with a small delay, and there is no backhaul 112 that can be used to send the image to the first responder group member 3310 . See Figure 34.

[0322] With UAVs 708 and 710 deployed above the operating area, the first responder group 3310 can address the disaster area, load the mobile robot 3314 with their fixed sensor 3312 payload, and turn on the mobile robot 3314. Responder group members 3310, guidance staff 3308, and robots 3314 with their video sensors can all join the multimedia conference. In this scenario, the robot 3314 may only send a video stream. They do not receive video, but they have a control channel 3332 for receiving commands for movement and control of the fixed sensor 3312 they carry. The sensor video stream 3314 of the mobile robot can be displayed on the display of the guidance unit 3308 personnel, who use the communication control channel to guide the robot to further enter the disaster area. Based on the video stream from the sensor 3314 specifically installed on the robot, its fixed sensor 3312 payload can be stored on the ground and opened. The software/firmware in these fixed sensors 3312 can be connected to the LTE network, and then connected to the P/S proxy 1304 network, to locate the fixed sensor data analysis service 3304, and notify themselves and their capabilities (e.g., fire detection, sound Detection, chemical detection, motion detection) and their GPS location coordinates. From each fixed sensor The data sent by 3312 may be collected and analyzed by the fixed sensor analysis service program 3304 running on OptServerPGW 304 (in this example), and an alarm may be generated based on the data received from the fixed sensor 3312. All participants UE 3310 and 3308 subscribe to receive the alarm data stream 3330.

[0323] At the same time, all participants UE 3310 and 3308 may be able to communicate via voice conference setup, and may be able to choose from any one of the sensors 3314 installed on the robot, or from any one of the first responders 3310. The video of the video feed. Based on the needs of the first responder 3310, the robot 3314 can be commanded to move in a specific direction. The command may come from the guidance staff 3308 or the first responder group member 3310. As an example, the robot 3314 near the area of the fixed sensor 3312 may be sent to "investigate" the alarm generated by the data from the fixed sensor 3312. In addition, it is possible to communicate to all conference participants 3308 and 3310 via the conference video session capability.

101

Provides a video stream that can be generated by the UE 3310 of the first responder. The conference participants 3308 and 3310 may have the ability to select the video data stream for the displays of a series of all entities in the conference in which the video data is generated via the still images provided by the frame grabber 3322. Likewise, the image captured by the response group mobile device 3310 can be selected for display on the UE 3308 or 3310 of any participant.

[0324] Subsequent sections of the present disclosure provide details about the following items that can be understood by those skilled in the art: How can a multimedia conference be set up to allow audio and video communication between all conference participants; Conference participants 3308 and 3310 provide video streams from sensors 3314 installed on mobile robots; how can they provide alarm notification messages to conference participants 3308 and 3310; and how can a control channel be set up to allow users at the guidance section 3308 to control The movement of the mobile robot 3314 and the position where the fixed sensor 3312 is placed by the mobile robot 3314 are controlled. The interaction between the participant UE 3308 and 3310 devices and the image server 3302 is outside the scope of the multimedia conference, just like the interaction between the fixed sensor 3312 and the fixed sensor data analysis server 3304. The interaction between the image server 3302 and the fixed sensor 3312 and the interaction between the fixed sensor data analysis server 3304 and the fixed sensor 3312 are described in subsequent subsections of the present disclosure.

[0325] The setup multimedia conference conference manager 3102 application may already be associated with the conference registry 3110. The data for each meeting stored in the registry 3110 may have the following information: meeting name, meeting ID (defined by the meeting manager 3102 when the meeting is activated), start time, end time, participant list, chairperson ID , A list of roles and abilities, and a template for each session that can be selected for the meeting. The fields in each session template can indicate whether the session should be activated by the conference manager 3102 when the conference is started. Participants can not join the session until the session is activated, and once the meeting starts, the session can be dynamically activated by any participant 3308, 3310 or 3314. In this scenario, all sessions are initiated by the conference manager 3102 based on the information in the registry 3110 for the "emergency action" conference. The conference manager 3102 can also create a collection of topics for the publish/subscribe communication mode for all the behaviors required in the conference. Additional topics can be created and assigned by the conference manager 3102 when each participant 3308, 3310, or 3314 joins the session, so the participant may be able to receive a unique and appropriate view of the conference data.

[0326] The registry 3110 information can be created by any authorized UE 104 to set up future conferences, but it can also be set up by the unit management system 802. In this scenario, it is assumed that the registry 3110 entry for the "emergency action" meeting has already been set up when the emergency operation needs to start.

[0327] UE 3308, 3310, and 3314 can join and leave the conference at any time, UE 3308, 3310, and 3314 can join or leave any of the sessions 3324, 3328, 3330, and 3332 that are activated for the conference and they are allowed to be joined, All or a subset. Therefore, in an emergency action scenario, the number of participants 3308, 3310, and 3314 can change dynamically. For example, one or more robots 3314 can be disabled, and new robots can replace them, or additional robots can be added to the operation as needed.

[0328] Table 8 can show that the registration form 3110 can contain some of the information for the "emergency action" meeting before and after the meeting is activated (some entries can be made after the meeting starts, such as the meeting ID and the activated session And a list of topics). These entries can be made by the meeting manager 3102 once at the start of the meeting, but can be made by any entity (for example, EMS 802 or a user) before the start of the meeting.

[0329] Table 8: Emergency Action Conference Parameters

102

<td>Conference parameters</td><td>fi</td><td>When will the strips be made £1</td>

<td>Dagon Admonishment</td><td>Urgent action</td><td>The commandment for the beginning of the meeting</td>

<td>^&lt;11）</td><td>&lt;»Xiecheng text string&gt;</td><td>At the beginning of the panel discussion</td>

<td>Starting time</td><td>&lt;Time ridicule but IMMEDIATE in this scene (m tick)</td><td>Orchid that should begin at the meeting</td>

<td>End Time</td><td>&lt;Time&gt;, but this situation is apricot If NT1 L-TERMINATED (1Ϊ to the final ratio)</td><td>Before the ceremony begins</td>

<td>Participate in the stubble</td><td>It can be the user's name or the user's IMSI, or a name such as "alarm generator", or a name such as "responder", "arbitrary robot" or "arbitrary commander"... ·General in</td><td>At the beginning of the meeting, Zrn, although DingygftlllEMS 8(12, or if approved by the chairman</td>

<td>Seat m</td><td>&lt;Only in the meeting--H»WlUJ4iMSI or the famous family name</td><td>Before the meeting will be rolled away, but it can be passed through; the Ri.'qt! csi (hair/(._fivei hnir cross the tiles to dynamically change the mansions</td>

<td>Roles and abilities</td><td>"No.-Respondents," (Quan shop conversation eight "command headquarters, 7 Quan shop conversation): "Alarm cattle salter," [Send alarms and alarm messages, receive alarms and inquiries 8 "Mobile robots," (send » «, receive command); "Tree fixed magnetic transmitter," f send data ";</td><td>Before the meeting begins</td>

<td>Will advise on the topic</td><td>Scn-iceControl/ConlSvc/EmcrgcncyAc tion /&lt;conflI)&gt; (Conf Mgr orders this: * questions); ^WM1/&lt;1 MSI&gt;K guides CM MgrXi specific UE response</td><td>When the meeting starts</td>

<td>Topic:</td><td>See below·Order</td><td>When the Ke session is activated, when the scene starts, Fang will remonstrate</td>

<td>Voice-off session control</td><td>SeniceControi/ConfSvc/EmergencyAction /&lt;confll)&gt;/audio</td><td>When the Yin Yang frequency conversation 33 is activated, in this case, when the meeting starts.</td>

<td>Video session control</td><td>Servicc&lt;^: HihO'i\ niifSxc/Emr(:eiic)A ciion^-cfinxidcu</td><td>Does the video session 33 Lake activate the elbow, in this case, choose the beginning of the meeting"</td>

<td>Alert session</td><td>ScniecCoiitrel/tonKvc/EmcrgencyAalarm</td><td>When the alarm session 33 is activated, in this case F, it is called the beginning of the meeting.</td>

103

<td>Robot control session</td><td>Se niceCo rt t rol/Co n CSvc/Ewi e rge n cyA c tifHl/&lt;1: (Hl 1Ή )&gt;/</td><td>When Peach Robot Control Club K3332 is activated, this situation is at the beginning of the F. Coincident meeting.</td>

<td>Session control</td><td>SerA icct (bar 1 meter, ¥Xibu on *wei cha", person 1*tion /&lt;con Discussion</td><td>When the... session is active* In this case, when the Fang session starts. The conversation can be activated or terminated by the participant posting a message to the topic. In the session management coupling 31()4, you can obtain the session manager 3102 Λ session manager 3104 assigned by the conference ««_nJlU uses a separate... for mustache questions to come in and usually order</td>

<td>Session notification</td><td>Ser\ il ti on(i-nl/( i'/i&lt;.niergencyActiori /&lt;confl l)&gt;/&lt;session Nan»e-Notift-&gt;</td><td>The Junche theme processor is used to notify all UEs participating in the special eunuch session of the changes in the list of session participants. The hatred in a specific conversation: E subscribe to this question to receive this music update.</td>

[0330] The following descriptions of how the conference can be started and operated are shown in Figure 35, Figure 36, Figure 37, and Figure 38. In order to simplify these figures, the use of the P/S proxy 1304 network is omitted in these figures, but it is obvious to those skilled in the art that the message transfer interaction occurs through the actions of the P/S proxy 1304 middleware system.

[0331] FIG. 35 shows how a meeting can be started. Because the registration form 3110 contains an entry for the emergency action meeting indicating that it will start immediately, once the registration form 3110 entry is made, the conference manager 3102 can be notified. The conference manager 3102 can start a conference, assign a ConfID to the conference, and subscribe to the topic: ServiceControl/ConfSvc/ EmergencyAction/&lt;confID&gt;o &lt;confID&gt; can embed the unique ID assigned to the conference manager 3102 (as opposed to any other instance), Therefore, messages related to the conference are routed only to the conference manager 3102 instance by the P/S proxy 1304 network.

[0332] The conference manager 3102 may determine the session that needs to be started according to the information in the registry 3110, and may issue a service query to the topic Serviceinquiry/Conf Session/&lt;ContMgrID&gt; to locate the instance of the session manager 3104, where &lt;ConfMgrID&gt; may be The unique ID assigned to this instance of the conference manager 3102. All Session Manager 3104 instances can subscribe to the topic Service Inquiry/Conf Session/* to receive these inquiries. In this case, there is only one instance of the session manager 3104. Therefore, the conference manager 3102 can receive a service description reply carrying the unique SessMgrID among all the instances of the session manager 3104. The session manager 3104 can subscribe to its unique control channel (ServiceControl/ConfSession/&lt;SessMgrID&gt;) outside the scope of any particular meeting. In the case that each communication entity has a unique ID assigned to another communication entity, the meeting The manager 3102 and the session manager 3104 can now exchange messages via the P/S proxy 1304 network.

[0333] The conference manager 3102 may publish a message to the session manager 3104 to indicate the start of the emergency action conference, and may provide a list of sessions that need to be started. The topic of each session can also be included in the session manager 3104

104

In the information passed. In this case, the audio session 3324, the video session 3328, the alarm session 3330, and the robot control session 3332 can be activated. Because the audio conference session 3324 is activated, and because the video conference session 3328 is activated, the session manager 3104 must locate the media server 3108 to reserve and start the audio mixer 3318, video mixer 3320, and frame grabber for conference participants 3322 capabilities so that these capabilities are available when each participant joins the corresponding session.

[0334] The location of the media server 3108 may involve a service query issued by the session manager 3104 to a general topic subscribed by all media server 3108 instances (in this example, there is only one instance), and a service description response returned to the topic By adding the unique ID of the session manager 3104 instance, it becomes unique. The reply contains the unique ID assigned to the media server 3108 instance, and from this point, the two instances can communicate via the P/S proxy 1304 network to set up media processing for audio and video sessions. The availability of resources of the audio mixer 3318, video mixer 3320, and frame grabber 3322 can be included in the service description response generated by the media server 3108. Therefore, when more than one instance is available in the network, the session manager 3104 can obtain information from several To select from three media servers 3108. Therefore, the topic subscribed by the session manager 3104 for the audio session in this conference may be Servicecontrol/Conf Svc/EmergencyAction/&lt;conf ID&gt;/audio/&lt;SessMgrID&gt;. The topic subscribed by the media server 3108 for the audio session in this conference can be ServiceControl/ConfSvc/EmergencyAction/&lt;conf ID&gt;/ audio/&lt;SessMgrID&gt;o audio mixing resources 3318, video mixing resources 3320, and image collection resources can be reserved at the media server 3108 instance for emergency action meetings. Emergency action meeting restriction is active. The conference manager 3102 may return a confirmation to the registry 3110 to indicate the start of the conference, and may provide the registry 3110 with the ConfID that has been assigned to the conference. The value must be passed to each participant to allow the participant to join the conference.

[0335] FIG. 35 shows the interaction discussed above for initiating an emergency action meeting. As mentioned above, in order to simplify the period, Figure 35 does not show the use of P/S proxy 1304 to route these messages. Therefore, the inclusion of P/S agent 1304 routing is understood by the reader to support each of the interactions shown in FIG. 35. It should be remembered that the only point-to-point connection is the connection between the entity (eg, session manager 3104, media server 3108, sensor 3314) and the P/S agent 1304. There is no explicit connection between the communication service entity, sensor or participant UE. In addition, every message sent is actually published to the topic, and every message received implies a subscription to the published topic. The themes that can be used in this scenario can be found in Table 8.

[0336] Participants Joining Conferences and Joining Sessions A description of how entities can join conferences and sessions that allow them is shown in Figure 36. Each conference participant UE 3308, 3310 and each sensor 3314 need to communicate with the conference manager 3102 to join the conference. For the purpose of this conference control and other conferences, the conference manager can subscribe to ServiceControl/Conf Svc/ EmergencyAction/&lt;confID&gt;. Therefore, the participant device must obtain the conference name and &lt;confID&gt; before it can issue a request to join the conference. Although the conference name can be provided to the participant devices, it may not be possible to provide &lt;confTD&gt; because &lt;confTD&gt; is assigned by the conference manager 3102 at the beginning of the conference. This behavior increases the security of the conference joining process.

[0337] When the user 3308, 3310 or 3314 chooses to join the conference, the UE 3308, 3310 or 3314 can issue a service query to the topic Servicelnqiuty/Conffivc/Registry/&lt;IMSI&gt;, where &lt;IMSI&gt; is a unique value assigned to the UE. Because all registry 3110 instances can subscribe to the topic Serviceinquiry/ConfSvc/Registry/*, UE 3308, 3310 or 3314 messages can be routed to all registry 3110 instances by the P/S agent 1304 network. The service description response message issued by the instance of the registry 3110 may include the only UE 3308,

105

The IMSI of 3310 or 3314 to allow routing of the response to that particular UE 3308, 3310 or 3314. The service query message may include the conference name (emergency action), so if the registration form 3110 has information for the conference, the registration form 3110 can respond. In this example, there is only one registry 3110, so only one service description response message can be returned to UE 3308, 3310 or 3314. It contains the unique ID of the conference manager 3102 and information about the emergency action conference, which includes &lt;conflD&gt; (in this case, the sensor 3314 and other UEs 3308 and 3310 that need to join the conference can be provided with the conference name).

[0338] The UE 3308, 3310 or 3314 can now publish a join message to the conference manager 3102 of the emergency operations conference. The participant list that can be provided to the conference manager 3102 can allow it to allow the UE 3308, 3310, or 3314 to participate in the conference. The joining may have information about the role of the UE 3308, 3310, or 3314, and therefore, the conference manager 3102 may determine the set of sessions that the UE 3308, 3310, or 3314 may be able to join, and may inform the UE in the confirmation of the join request 3308, 3310, or 3314 sends a list of conversations. Therefore, the UE 3308, 3310 or 3314 can display all the sessions that the UE 3308, 3310 or 3314 can join. As the initiator of the session, the conference manager 3102 sends an invite () message to the UE 3308, 3310 or 3314 for each session that the UE 3308, 3310 or 3314 can join. The UE 3308, 3310 or 3314 may not join the session without first receiving the invitation () from the session initiator. In this scenario, the session initiator may be the conference manager 3102.

[0339] In the case of other conferences, the user can select the session to join. In this case, the UE 3308, 3310, or 3314 can be programmed to automatically join those sessions related to its role. Therefore, the UE 3308 of the steering staff and those UE 3310 of the first responder can accept the invitation to join the audio 3324, video 3328, alarm 3330, and robot control 3332 sessions (). The video sensor 3314 installed on the robot can only accept the invitation to join the video session 3328 () when it only has the ability to send/post videos but not to receive the video. In this example scenario, the fixed sensor 3312 is not a participant in the conference. They can publish their data only on the topic indicated in the next subsection, where the topic is subscribed by the fixed sensor data analysis service 3304.

[0340] When the UE 3308, 3310 or 3314 issues a request to join the session (for example, for the video session 3328: ServiceControl/ConfSvc/EmergencyAction/&lt;conflD&gt;/video), the conference manager 3102 can receive the request, according to the UE 3308 , 3310, or 3314 to determine whether the request can be authorized, and if possible, it can generate one or more topics assigned to the UE 3308, 3310, or 3314 for the session. For example, the joining of the audio session 3324 can generate two topics. One theme is for UE 3308 or 3310 to use in publishing its audio stream. Another topic is to subscribe to the UE 3308 or 3310 so that it can receive the mixed audio stream sent to it by the audio mixer 3318 in the media server 3108. The mixed audio stream has parallel audio packets generated by all UE participants except the UE receiving the stream. In this scenario, the sensor UE 3314 installed on the robot does not participate in the audio session 3324.

[0341] For the video session 3328, two topics may be generated for the first responder 3310 and for the guidance unit 3308 UE. Only one theme can be generated for the sensor 3314 UE installed on the robot. The first topic can be used by UE 3308, 3310 or 3314 to publish its video stream. If generated, the second topic may be to subscribe to the UE 3308 or 3310 to receive the mixed video stream generated by the video mixer 3320 at the media server 3108. Here, the mixed video includes a video stream generated by all video generating sensors and all participants 3308.3310 or 3314 except the receiving UE. (Actually, it is possible to send a series of captured images, each image from a participant 3308 and 3310 and sensor stream 3314. When the user selects a particular video stream, only from the selected participant 3308 or 3310, or sensor 3314 The video stream can be sent to the requesting UE 3308 or 3310.

106

[0342] For the alarm session 3330, a topic can be generated, and the topic is subscribed by the UE 3308 or 3310 to receive the alarm. Only the first responder 3310 and the guidance unit 3308 UE can join the alert session, and it is likely that the same alert topic can be assigned to all UEs 3308 and 3310 that join the alert session, so the alert is issued once by the fixed sensor data analysis 3304 alert generator function , And all subscribed UEs 3308 and 3310 may be able to receive the alert.

[0343] For the robot-controlled conversation 3332, two topics can be generated. The first topic can be for UE 3308 or 3310 to issue robot control commands. The second topic may be for UE 3308 or 3310 to subscribe to the reception of robot responses to those commands.

[0344] Since the participant list changes for each session, the conference manager 3102 may publish an updated session participant list so that it is received by each UE 3308 and 3310 participating in the conference session. According to Table 8, all UEs 3308 and 3310 participating in the session named "session name" subscribe to the topic: ServiceControl/ConfSvc/Eme rgencyActioa^z&lt;conflD&gt;/&lt;sessionName-Notify&gt; to receive the session participant change notification for the specific session (for example, for the video session 3328, the last part of the topic string may be "video-notification").

[0345] The topic generated by the conference manager 3102 may not be a character string, but may be an 8-byte number. The transmission of audio 3324 and video 3328 streams requires low latency, so the use of string themes can be avoided to reduce the time it takes for the P/S proxy 1304 network to determine the routing of these packets. Because the theme generation is processed by the conference manager 3102, their uniqueness can be guaranteed. When a UE 3308, 3310 or 3314 joins a session, the conference manager 3102 must generate topics, and can send these topics to the UE 3308, 3310 or 3314 and also to the session manager 3104, which is responsible for publishing these to the media server 3108 Subject, the audio and video streams from the UE are collected at the media server 3108, and the mixed streams 3324 and 3328 are published at the media server 3108. In the case of the alarm session 3330, the conference manager 3102 may send topics to the fixed sensor data analysis service 3304 and to UEs 3308 and 3310 that have joined the alarm session 3330. For the robot-controlled conversation 3332, the topic can be sent to the robot participants 3314 who join the robot-controlled conversation 3332 (in this scenario they are all), and to UEs 3308 and 3310 who join the robot-controlled conversation.

[0346] At the same time, the first responder UE 3310 and the director UE 3308 can display all available sessions to the user, as well as those sessions that the user may have joined.

[0347] FIG. 36 shows message interactions that can occur when a UE 3308, 3310, or 3314 joins a conference and then joins one or more sessions. In order to simplify the message transfer diagram, P/S proxy 1304 routing and interaction is omitted again in FIG. 36. In order to keep the interactions to a limited number in Figure 36, all sessions of UE 3308, 3310 or 3314 are not shown to join. Readers of those skilled in the art can realize that all sessions required by a specific UE type can be added in the manner indicated in FIG. 36.

[0348] Once a UE 3308, 3310 or 3314 has joined all of its sessions, it can participate in all of its allowed services during the conference. The UE 3308 or 3310 that has joined the audio session 3324 can now publish its audio packet to the topic received in the join (audio) interaction. It can also receive the mixed audio stream 3324 via the audio topic that it subscribes to for this purpose. Therefore, the user 3308 or 3310 conducts an audio conference with each of the other users 3308 and 3310 in the audio session 3324. Similarly, the UE 3308 or 3310 can display the collected images of each video stream in the video session 3328 of the conference, which includes the image of the sensor 3314 installed on the robot and the image of the first responder group member 3310. When the user 3308 or 3310 selects one of the captured images on the display, the UE 3308 or 3310 may send a control message to the conference manager 3102 to select a specific video stream. The conference manager 3102 can send to the session manager 3104

107

After sending an instruction, the session manager 3104 informs the media server 3108 to stop sending the mixed video stream to the topic published by the UE 3308 or 3310. The conference manager 3102 may return to the UE 3308 or 3310 the topic number used by another UE 3308, 3310 or 3314 to publish the selected video stream. The requesting UE 3308 or 3310 can subscribe to the topic and can start receiving the selected video stream. The first response 3310 or the guide 3308 may receive a video stream sent by any sensor 3314 or by any video publisher 3310 in the meeting. Note: The P/S proxy 1304 middleware used in this disclosure does not change the way the video stream generator (in this case) sends its video packets. If another endpoint (ie, user 3308 or 3310) needs to receive a video stream, then the P/S proxy 1304 network arranges the delivery of the stream, as long as the new viewer subscribes to the topic for publishing video stream packets.

[0349] Likewise, once the UE 3308, 3310 or 3314 joins any other session, and the corresponding topic is appropriately allocated, the UE 3308, 3310 or 3314 may be able to participate in the session. The first responder 3310 and the guidance unit 3308 UE may receive the alert generated by the fixed sensor data analysis service 3304. The first responder 3310 and the guidance unit 3308 UE can send a motion command to the mobile robot UE 3314 (when each mobile robot UE 3314 joins the robot-controlled session 3332, the conference manager 3102 assigns a subscription topic to it, and sends a motion command to the mobile robot UE 3314. Each of the first responders 3310 and the guidance section 3308 UE of the conversation 3332 assigns this topic as the publishing topic).

[0350] Fixed sensor data collection and alarm distribution As pointed out in the above description in this disclosure, the fixed sensor 3312 in this scenario does not directly participate in the multimedia conference. Depending on their capabilities, they can monitor movement, or they can detect smoke or chemicals, or they can detect heat or sound, etc. But when they sense something to report, these sensors 3312 can send their information to the fixed sensor data analysis service 3304, and the fixed sensor data analysis service 3304 can analyze the data and generate an alarm as appropriate. Therefore, when the fixed sensor 3312 is turned on, it can connect to the LTE network, it can connect to the P/S proxy 1304, and it can send a service query to locate one or more instances of the fixed sensor data analysis service 3304 (in this scenario There is only one in the example). Assume that the fixed sensor data analysis service 3304 subscribes to the topic Servicelnquiry/FixedSensor/* to receive service query messages. Each fixed sensor 3312 can publish a service inquiry message to the topic ServiceInquiry/FixedSensor/&lt;myIMSI&gt;. By including its unique IMSI value, the fixed sensor data analysis service 3304 software can publish a service description reply, which is handled by the P/S agent 1304 The network only routes to fixed sensors 3312 that generate service queries. The service description may include a unique identification value among fixed sensor data analysis 3304 service instances in the network. Once the fixed sensor 3312 and the fixed sensor data analysis 3304 program hold the unique ID of the other party, the fixed sensor 3312 and the analysis 3304 service program can thereafter exchange messages with each other via the P/S proxy 1304 network.

[0351] The fixed sensor 3312 may send a message Initiateservice() to the fixed sensor data analysis 3304 service instance, thereby providing information such as its GPS location coordinates and its detection capabilities. The fixed sensor data analysis 3304 service software can publish an InitiateServiceAck 0 message, in which it allocates the topic that the fixed sensor 3312 will use to publish data for its detected.

[0352] At the same time, as indicated in FIG. 36 above, each UE 3308 and 3310 that joins the alert session can receive the subject of its subscription to receive the alert, and the subject can also be maintained at the fixed sensor analysis 3304 service program. The subject of the alert. If all UEs 3308 and 3310 in the session will receive all alerts, then the same topic can be assigned to each UE 3308 and 3310 participating in the alert session. If different UEs 3308 and 3310 will respond to different sets of alarms, the topics of the alarm conversations assigned by the conference manager to the different UEs 3308 and 3310 can be different. In any case, when the fixed sensor 3312 publishes data to its assigned topic, it is determined by the fixed sensor 3312.

108

The sensor data analysis 3304 service software receives, analyzes, and if an alert is generated, then issues an alert to the topic or some topics associated with the alert type. The alert is then received by all UEs 3308 and 3310 that have subscribed to the published topic in the alert session. These interactions are shown in Figure 37. In order to simplify the interaction diagram, the P/S proxy 1304 network is again omitted in Figure 37.

[0353] Image collection, storage, and distribution As indicated in the above description of the emergency action scenario, the UE 3310 of the first responder group member may be able to take pictures when the members pass through the operation area. These images may need to be loaded on the server and provided to other members of the first responder group 3310 and to the personnel 3308 located in the guidance department. The image server 3302 shown in FIG. 34 can run on the OptServereNB 308 associated with the eNB 102 covering the operating area, and can provide for uploading and storing these images, and making them downloadable to any participant in the emergency operation operation Means 3308 or 3310. By executing the image server 3302 software on OptServereNB 308, the backhaul 112 is not used to carry images from the first responder group member UE 3310 to the storage site, and the backhaul 112 is not used to download images to the members of the first responder group 3310. In this architecture, the transmission delay on the backhaul 112 can be avoided, and the use of the backhaul 112 is minimized, so it can be used for other services. When the image was downloaded to participant 3308 at the guidance department, The backhaul 112 is used because in this example scenario, their UE 3308 accesses the network via an eNB 102 unit that is different from the eNB 102 associated with the OptServereNB 308 running the image server 3302. See Figure 34.

[0354] When the user invokes the image processing program of the UE 3308 or 3310±, the program must first locate the image server 3302 in the APN network. To this end, it can publish a service query message to the topic ServiceInquiry/ImageService/&lt;IMSI&gt;, where &lt;IMSI&gt; is a unique ID assigned to UE 3308 or 3310. At the same time, all image server 3302 instances subscribe to the general topic Servicelnquiry/ImageService/*, and therefore receive the service query message issued by the UE 3308 or 3310. The image server 3302 can publish a service description response reply message to the topic Serviceinquiry/ImageService/&lt;IMSI&gt;, so the P/S proxy 1304 network can only route the reply to the UE 3308 or 3310 that sends the service query. In this example scenario, there is only one image server 3302 in the network, so a service description is returned to the UE 3308 or 3310 for its query. The service description message may include a unique ID assigned to the image server 3302 program. Therefore, from this point, the UE 3308 or 3310 and the image server 3302 instance can exchange messages via the P/S proxy 1304 network. UE The 3308 or 3310 image processing program can register itself to the image server 3302 instance, and can receive the theme used when publishing images to the server (in this example scenario, only the UE 3310 performs this operation), when the image server 3302 The second topic used when publishing service requests (for example, for image download and for image information), the third topic used to subscribe to receive service response information from the image server 3302, and the third topic used to receive image downloads from the image server 3302 Fourth theme.

[0355] When recording an image at the UE 3310, the image processing program of the UE 3310± can tag the image with the current GPS coordinates of the UE 3310, can add the date and time, and can allow the user to input comments. This information can be kept with the image in the UE 3310 memory. When the user chooses to upload the image to the image server 3302, the UE 3310 image processing program can upload the image and associated tag information to the image server 3302 using the publishing theme given to it during its initial interaction with the image server 3302. The image and its tag data can be saved to permanent storage by the image server 3302.

[0356] When the user (3308 or 3310) chooses to view one or more images saved on the image server 3302, the UE 3308 or 3310 may publish a request message via its assigned service request topic. The request may request a list of images from a specific user 3310, or from date/time, or from a collection of locations, or the like. The list can be accessed via

109

The assigned subject for receiving the response to the service request is returned to the user UE 3308 or 3310. Another service request issued by the user UE 3308 or 3310 may request the download of one or more specific images in the list. These images can be downloaded to the user UE 3308 or 3310 via the theme assigned to the UE 3308 or 3310 for receiving image downloads. These interactions are shown in Figure 38. For the sake of simplification, the P/S agent 1304 interaction in the message transmission scheme is also omitted. [0357] The disclosure presented in this article using emergency action scenarios shows the APN LTE wireless network and its associated optimization servers 304 and 308, plus the redirected bearer 312 capability and how the P/S proxy 1304 middleware component can be used To handle various sensor needs. It should be clear to those skilled in the art that: any sensor data collection and processing not covered in this example scenario can use the APN LTE wireless network optimization servers 304 and 308, the bearer redirection 312 capability, and the associated P/S proxy 1304. The software is deployed in an efficient manner, demonstrating that the capabilities of the system disclosed in this document will be used as a platform for sensor data collection, storage, analysis, and distribution.

[0358] The APN LTE network used to give priority to the data rate of LTE users In LTE networks, and especially in dual-use LTE networks, users can be given access priority and bearer priority can be assigned to users, but not The user is assigned a priority for the air interface resources allocated to transmit or receive data. When there are multiple users accessing through a specific cell, it may be desirable to assign priority to the users for receiving high data rates. This can happen when there is no emergency, and therefore cell blockade for government use (CB for GU) is not activated at the cell. Or, there may be an emergency or disaster situation, and the cell may be blocked for government use, but there are still a large number of users accessing the LTE network through the restricted cell, so that the highest priority users cannot receive the high data rates they may need.

[0359] In the LTE system, a user equipment (UE 104) is granted a set of physical resource blocks (each PRB is a set of 12 consecutive subcarriers used in the system) and time for transmitting uplink data. Similarly, the LTE system schedules time and a set of PRBs to carry downlink data destined for a specific UE 104. The software component that performs this function in the LTE system is the scheduler in the eNB 102 unit. The scheduler may be generally designed to give fair treatment to all UEs 104 that access the LTE network through the cell of the eNB 102. However, there may be cases where the UE 104 is designated as a high-priority UE 104 that requires preferential treatment in the allocation of PRBs for over-the-air transmission. The number of PRBs allocated to UE 104, plus the coding method applied to the data, determines the data rate provided to UE 104.

[0360] Allocate data rate priority to UEs and configure the eNB scheduler to use the value. This disclosure describes the use of data rate priority values for each UE 104 that accesses a cell included in the eNB 102 to configure the eNB 102 Scheduler method and system. The scheduler may use the data rate priority value associated with a given user to guide the allocation of its physical resource blocks (PRB) to users for sending and receiving data over the LTE air interface, and/or to give UE 104 time-based priority The level is used to access the LTE air interface. The previous sections of this disclosure are related to the current disclosure, that is, the use of Publish/Subscribe (P/S) proxy 1304 middleware to achieve efficient communication between units in the APN LTE network; the network is associated with LTE network units And the use of a collection of optimization servers 304 and 308 nodes integrated into the LTE process processing; using the Wireless Control Process (WCP) 3902 and its interface to the eNB 102 unit to implement the UE 102 data rate priority value to the eNB 102 and therefore to the eNB 102 Scheduler transmission; use of an application function (AF 2102) that contains provision data (IMSI value) for high-priority UE 104, or can access a database that can contain informative IMSI values related to data rate priority capabilities . See the previous sections of this disclosure.

[0361] The following set of list entries describes the mechanisms that can be implemented to achieve the data rate priority capabilities mentioned above. Those skilled in the art can realize that the same result can be achieved by deviating from the description given below. because

110

Therefore, the teaching specifically presented below is an illustration of how the data rate priority feature can be implemented in an LTE wireless network. [0362] 1. When all users 104 access a cell for the first time, the eNB 102 scheduler can assign a data rate priority value of 1 to them by default. The default value of the UE 104 data rate priority may be inserted by the scheduler into the data record maintained for the UE 104 by the scheduler.

[0363] 2. The AF 2102 program that can run on the OptServerPGW 304 node can be provided with data rate priority off or on on a per cell basis. The default value can be off. When the value of the data rate priority variable changes for a cell, the AF 2102 can interact with an application program referred to herein as the radio control procedure 3902 to cause the data rate of each currently registered UE 102 served by the cell The priority value will be updated appropriately (ie, if the data rate priority becomes off at the cell, then update to a value of 1; or if the data rate priority becomes on at the cell, then update to the value assigned to the UE 104 UE 104 data rate priority value).

[0364] 3. The eNB 102 interface to the radio control process 3902 running in the OptServerPGW 304± can be used to send the data rate priority value of a given UE 104 to the eNB 102 (as the radio control process 3902 for each UE 104). The C-RNTI retained as part of the saved data is used to identify the UE 104 at the eNB 102).

[0365] 4. Therefore, for all UEs 104 that do not interface with the radio control process 3902, their data rate priority is still set to the default value 1. These UEs 104 may be UEs 104 of non-governmental organization users who can roam on the dual-purpose APN wireless network. All government agency users and many or all other users of the same dual-use APN wireless network may have software that interfaces with the wireless control process 3902 via the P/S proxy 1304 middleware. For the UE 104 that interfaces with the radio control process 3902, such docking can occur whenever the UE 104 accesses a cell in the APN wireless network, that is, whenever the UE 104 sends a registration message to the radio control process 3902 (ie, in After the initial LTE access procedure), or when sending a more detailed registration message (that is, after the LTE service request procedure), or when sending a handover message (that is, after the LTE handover procedure). See Figure 4 and Figure 6. During the processing of any of these messages, the wireless control process 3902 may interface with the AF 2102 via the P/S proxy 1304 middleware in order to obtain the data rate priority value associated with the IMSI of the UE 104. If the cell ID is provided at AF 2102 in the radio control procedure 3902 request message to indicate the data rate priority OFF, then AF 2102 can be the UE 104 The data rate priority returns the value 1. Otherwise, the AF 2102 may check the priority of the data rate provided to the IMSI of the UE 104, or check the value provided to the accessible IMSI database. If the AF 2102 does not retrieve the information provided for the IMSI of the UE 104, the default value 1 may be returned. Otherwise, the AF 2102 can obtain the data rate priority value provided for the IMSI of the UE 104 and return this value to the radio control process 3902. Therefore, the radio control process 3902 can send the UE 104 data rate priority value to the eNB 102 when it processes the UE 102 registration message, or the registration update message, or the handover message, regardless of whether the UE 102 bearer 302 is subsequently renewed by the radio control process 3902. Directed to eNB 102. The value for the UE 104 data rate priority can be any value 1, or a larger value, where a larger value implies a higher data rate priority for the UE 104.

[0366] 5. The eNB 104 scheduler can be changed from the current implementation to consider the data rate priority value when scheduling the UE 104 to receive or transmit data. For example, if the eNB 102 scheduler is to schedule downlink data to be sent to the set of UE 104, it can allocate the available PRB based on the RF conditions previously reported by the UE 104 and also based on the data rate priority associated with the UE 104. set. The UE 104 with the highest data rate priority value may receive the maximum number of PRBs consistent with the data queued for the UE 104 or may be processed by the scheduler before the scheduler processes the UE 104 with a lower data rate priority value. deal with. At the same time, all UEs 104 with a data rate priority of 1 can receive a number of PRBs less than the maximum number that might otherwise be allocated, because some number of PRBs have been allocated to UEs 104 with a higher data rate priority value. All UEs 104 with the same data rate priority value are being allocated

111

In terms of the number of allocated PRBs, or in terms of being processed by the scheduler first, the scheduler can receive the same treatment.

[0367] The disclosures in the above paragraphs can be seen in FIGS. 39, 40, 41, 42 and 43. The first three figures in these figures add a data rate priority interaction to the interaction shown in Figures 4 and 6, where the wireless control process 3902 and the P/S agent 1304 messaging infrastructure mode are explicitly shown (These components are not explicitly shown in Figures 4 and 6). Figure 39 can be applied to the case where the UE 104 has not registered to the radio control procedure 3902 (ie, during the initial access procedure). FIG. 40 can be applied to the following situation: the UE 104 was previously registered to the radio control procedure 3902, but because, for example, the UE 104 is in the transition process from the ECM idle state to the ECM connected state, it must provide an update. Fig. 41 can be applied to a situation where the UE 104 is handing over to a new eNB 102. Each of these three cases may cause the UE 104 to access a different cell from the previous one, and therefore, the newly accessed eNB 102 must be notified of the data rate priority of the UE 104. FIG. 42 can be applied to a case where it is specified that AF 2102 opens the data rate priority of one or more cells in the LTE network. FIG. 43 can be applied to a situation where it is specified that AF 2102 turns off the data rate priority of one or more cells in the LTE network.

[0368] FIG. 39 shows a detailed elaboration and modification of the process shown in FIG. 4 and previously described in the present disclosure. The detailed description shows how the UE 104 can use the P/S proxy 1304 middleware to communicate with the wireless control process 3902 running on the OptServerPGW 304 node. The port number in the service start message is the port number of the UE 104 to which the P/S proxy is connected. At the same time, it can also provide IMSI data to the AF 2102 software that plays a role in the disclosure provided in this article for implementing dual-use networks, or the AF 2102 software can access the priority value including the data rate assigned to the IMSI of the UE 104 IMSI database. As shown in Figure 39, Figure 40, Figure 41, Figure 42 and Figure 43, in a modification to the process described in Figure 4, the wireless control process 3902 and AF 2102 can be performed via the service of the P/S proxy 1304 middleware. Communicate in order to provide a data rate priority value for a given IMSI, and use that value to update the serving eNB 102. [0369] In order to receive messages from multiple UEs 104, the wireless control process 3902 may subscribe to the topic "WirelessControl/*". In order to communicate with the radio control process 3902, the UE 104 may inform the subject WirelessContol/&lt;myIMSI&gt; publishes its message, where &lt;mylMSI&gt; is the only IMSI value assigned to the UE 104. When the radio control process 3902 responds to a specific UE 104, it can publish a message to the topic "WirelessControl/&lt;IMSI&gt;", where &lt;IMSI&gt; is the value assigned to the target UE 104. The UE 104 must have previously subscribed to the topic in order to receive messages about the topic.

[0370] In order to implement the message exchange between the wireless control process 3902 and the AF 2102, the AF 2102 may subscribe to the topic "AF/data/*". Then, the wireless control process 3902 can issue a data rate priority check () message to the topic "AF/data/&lt;WCPid&gt;", where &lt;WCPid&gt; is a unique ID assigned to the wireless control process 3902, and where the wireless control process 3902 subscribe to receive messages about the topic "AF/data/&lt;WCPid&gt;". Then, the AF 2102 can reply to the wireless control process 3902 by issuing a data rate priority check () message to the subject "AF/data/&lt;WCPid&gt;".

[0371] When the UE 104 accesses the LTE network for the first time, it proceeds as described in the previous sections in this disclosure (see Figure 4), until the dedicated bearer establishment message is issued by the UE 104 to the radio control process 3902 ( See Figure 39). At this point in the registration process, the wireless control process 3902 may be adapted to issue a data rate priority check message to the AF 2102. The AF 2102 may use the cell ID and IMSI in the message to obtain the data rate priority value of the IMSI, and may then issue a data rate priority check response message to the radio control process 3902. The radio control process 3902 can then use its direct interface with the eNB 102 serving the UE 104 to transmit the data rate priority value associated with the UE 104, and this value can be transmitted by the eNB 102 software to the eNB 102 scheduler. The rest of the registration process proceeds as described in Figure 4 (and Figure 39).

112

[0372] FIG. 40 shows processing that can be used when the UE 104 transitions from the ECM idle state to the ECM connected state and successfully completes the LTE service request procedure. The interaction that occurs after the UE 104 is registered with the radio control procedure 3902 for the new cell ID and the new C-RNTI value is the same as that shown in Figure 39, except that the registration update and registration update Ack messages are exchanged instead of Figure 39 The registration and registration Ack message. The same parameters can be included in the message in both cases. [0373] FIG. 41 shows a detailed elaboration and modification of the process shown in FIG. 6 and previously described in the present disclosure. The detailed description shows how the UE 104 can use the P/S proxy 1304 middleware to communicate with the wireless control process 3902 running on the OptServerPGW 304 node. The port number in the restart session message received by the UE 104 is the port number of the UE 104 to which the P/S proxy is connected. 6 shows the integration of the optimization servers 304 and 308 into the LTE network behavior during the handover process, and the UE bearer 312 for the purpose of allowing the UE 104 to directly communicate with the OptServereNB 308 node associated with the target eNB 102 Redirect to the target eNB 102 interaction. According to the present disclosure, FIG. 41 shows how the process of FIG. 6 can be modified to also include The data rate priority value of 104 is updated at the target eNB 102 scheduler.

[0374] When the handover is completed and the UE 104 issues a handover message to the radio control process 3902, the new C-RNTI and the new cell ID value, together with the IMSI value of the UE 104, are available to the radio control process 3902. Therefore, the radio control process 3902 can interact with the AF 2102 to obtain the data rate priority assigned to the UE 104 (or, if the new cell ID has a data rate priority that is off, the value is 1). Then the radio control process 3902 may transmit the UE 104 data rate priority to the target eNB 102 via direct communication interaction, so it may be transmitted to the eNB 102 scheduler. Thereafter, the radio control process can continue the handover process by exchanging the redirected bearer and the redirected bearer response message with the target eNB 102, and cause the UE 104 to restart its service session via the OptServereNB 308 associated with the target eNB 102 . See Figure 6 and Figure 41.

[0375] Turning on the data rate priority for one or more cells is shown in Figure 42 for the description of the following message interactions. As indicated in the previous paragraph, the AF 2102 can be provided with the data rate priority value assigned to each cell in the LTE network. When the data rate priority variable changes from off to on for a certain cell, all UEs 104 that are registered to the radio control process 3902 and access the LTE network via the cell need to be updated at the scheduler of the serving eNB 102 containing the cell Their data rate priority value. The current data rate priority of the UE 104 may have the value b at the scheduler because the data rate priority value previously associated with the cell is off. Figure 42 shows the processing that may be required to update the eNB 102 scheduler using the data rate priority value of each registered UE 104 that accesses the network via a cell.

[0376] The wireless control process 3902 may subscribe to the general topic "WirelessControl/*" to receive messages from multiple endpoints. When the AF 2102 is provided with the data rate priority of a given cell whose value is on, the AF 2102 can publish the cell data rate priority on message to the topic WirelessControl/dataRatePriority/&lt;AFid&gt;, so this message can be used by all of the radio control process 3902 Instance reception. The message contains a list of cell ID values. This message is received by the wireless control process 3902. For each cell ID in the message, the radio control process 3902 can search for its data for all UEs 104 that have been registered to it and have indicated that their serving cell ID is a value selected from the message sent by AF 2102. structure. Therefore, the list of IMSI values of the UE 104 collected by the radio control process 3902 can be placed in the block data rate priority request message issued to the topic "AF/&lt;WCPid&gt;", so it is received by the AF 2102. The message is sent for each cell ID in the message received by WCP 3902. When the block data rate priority request message is received by the AF 2102, the AF 2102 can search for the data provided to it or the number of accessible IMSIs based on each IMSI. The database is used to find the data rate priority value of each IMSI. These results can be placed in the subject "AF/&lt;WCPid&gt;"

113

The issued block data rate priority request message, so it is received by the requesting wireless control process 3902 instance. Then, the radio control process 3902 can retrieve the C-RNTI value corresponding to each IMSI from the data provided to it, and also retrieve the value of the C-RNTI that serves each cell in the received message from the data provided to it. The IP address of the eNB 102, and send the data rate priority value (C-RNTI) of each UE that accesses the network through each corresponding cell. For each cell ID value in the cell data rate priority on message, follow These interactions.

[0377] Turning off data rate priority for one or more cells is shown in Figure 43 for the description of the following message interactions. When the data rate priority variable changes from on to off for a certain cell, all UEs 104 that are registered to the radio control process 3902 and access the LTE network via the cell need to update them at the scheduler of the eNB 102 containing the cell The priority value of the data rate. At the scheduler, the current data rate priority of the UE 104 may have the value provided for the IMSI of the UE 104 because the data rate priority value previously assigned to the cell is on. Now these values need to be changed to a value of 1, so that all UEs 104 that access the network through the cell can obtain equal priority treatment from the eNB 102 scheduler. Figure 43 shows the processing that may be required to update the eNB 102 scheduler using a data rate priority value of 1 for each registered UE 104 that accesses the network via a cell.

[0378] When a change is provided to the AF 2102, and therefore the data rate priority value of one or more cells changes from on to off, the AF 2102 can publish a cell data rate priority off message to the topic WirelessControl/dataRatePriority/&lt;AFid&gt;, Therefore, the message can be received by all instances of the wireless control process 3902. The message contains a list of cell ID values. For each cell ID in the received message, the wireless control process 3902 can be directed to the cell ID that has been registered to it and has indicated that their serving cell ID is the slave AF 2. All UEs 104 of the selected value in the message sent by 102 search for their data structure. The data maintained at the radio control process 3902 for each such UE 104 includes a C-RNTI value, which is an identifier of the UE 104 that is known at the serving eNB 102. The list of C-RNTI values of the UE 104 can be collected by the radio control process 3902, and placed in the UE data rate priority list message sent to the eNB 102 that processes the selected cell whose data rate priority value becomes off. For each C-RNTI value, the message may indicate that a data rate priority value of 1 will be associated with the C-RNTI that identifies the UE 104 to the eNB 102 scheduler. When the message is received by the eNB 102, the UE 104 value is updated by the scheduler accordingly.

[0379] Collect and report charging data at the optimization server in the APN LTE network. When the UE bearer is redirected to the serving eNB 102, the bearer is therefore connected to the local optimization server 308 instead of the SGW 110 unit and then the PGW Unit 114, PGW 114 cannot create charging information used by the air interface based on the data across the redirected bearer. This situation may not be important for some applications (for example, for military applications or for emergency applications), but may be important for commercial applications. In the latter case, OptServer_eNB The program on 308 can keep track of the bytes, packets, connection time, etc. required to generate the equivalent of the cell detailed record (CDR) for data transmission across the redirected bearer 312, and must be able to Pass the information to PGW 114, or to some other charging data processor. (Different charges can be applied for this purpose, because the backhaul 112 may not be used to transmit data between OptServe-NB 308 and UE 104.) In addition, the resources provided by the optimization servers 304 and 308 may include permanent data storage, temporary data storage , Program execution time, etc., and the operator of the APN network may wish to charge for the use of these system resources. Therefore, charging data must be collected for optimizing server 304 and 308 resource usage.

[0380] TR 232 (httu://www.broadband-fonun.orx/technical/download/TR-232. edf) specifies the Broadband Forum IPDR (IP Session Detailed Record), and provides specific information that can be used for organization and Report OptServereNB 308 and 0ptServer_PGW Data report of the collection of billing data at 304, and report to PGW 114 or

114

The author sends an overview of the detailed report to another processing point for this data. The delivery of billing details requires the precise data to be collected, as well as the provision of any interface of the PGW 114 that allows the optimization server 304 or 308 to implement the transmission of the information, or the provision of another processing entity that charges for processing the information.

[0381] In addition, the collection of the IP detailed records of the specific redirected bearer 312 associated with a specific UE 104 remains to be resolved, because the OptServer with the redirected bearer 312_eNB At 308, no mapping to IMSI is immediately available. The extension of the redirected bearer 312 reserved at the PGW 114 no longer applies to this case, because the packets across the redirected bearer 312 do not pass through the PGW 114 and therefore cannot be collected by the PGW 114 in its usual manner of charging data To be responsible. The bearer to IMSI mapping of bearer 312 for redirection may need to be transmitted to OptServer_eNB The billing data collection program on 308, and may need to be designed to generate data and transmit the billing data to the billing data collection service. The present disclosure can provide such a design. In addition, when the UE 104 moves from one eNB 102 to another eNB 102, the redirected bearer 312 is transferred from an OptServer_eNB 308 moved to OptServer_eNB 308, and the charging data collection point may need to migrate data across the redirected bearer 312. The present disclosure may also provide details on how this movement of billing data collection points can be arranged.

[0382] As noted above, in addition to the transmission of user data packets via the redirected bearer 312 entity, it may also be necessary to report OptServerPGW 304 and OptServer_eNB 308 Use of resources at the entity. To this end, you can collect and use operating system statistics, such as process text size and .bss (random access memory) size, permanent memory file size and storage time, etc. The present disclosure can provide information on how to optimize OptServerPGW 304 and OptServer in the APN network architecture_eNB The details of the data collection and report are arranged at node 308.

[0383] An architecture that can be used to collect and report billing data at the optimization server. Readers skilled in the art will recognize that a variety of alternative means can be devised to organize the collections that can be used with integrated optimization servers 304 and 308. Collection and reporting of data for billing purposes in LTE networks. However, it can be seen that any architecture that successfully completes this task provides a means to determine the collection of usage data with a particular user or other billing entity (possibly including usage duration), and to transmit the collected data in a timely manner to the correct Means of designated billing center. The teachings provided in this disclosure provide one such architecture. This architecture utilizes the capabilities inherent in the APN network via the disclosures previously reported in this document, and therefore provides the most efficient means that can be used to collect and report the required billing data.

[0384] FIG. 44 shows that on each OptServereNB 308 node, it is called an IP charging data record (IPBDR_eNB4404) The program running of the program instance is used to collect and use OptServer_eNB 308's resource-related and collection and use are terminated in OptServer_eNB The 308 node redirects the transmission of user data related to the bearer 312 for the purpose of charging information related to the charging data. In addition, a similar program example IPBDR can be seen_pgw 4402 in the OptServer associated with the PGW 114 unit in the APN LTE network_PGW Run on 304 nodes. Among them, IPBDR_eNB The 4404 program can focus on collecting billing data for resource usage on its local server and also for the transmission of data through the redirected bearer 312 of the UE 104. The IPBDRp program can only focus on collecting billing data for resource usage on its local server. Fee data. The reason for this difference is that any user data transmitted from the LTE bearer to OptServerPGW passes through the PGW 114 unit, so the charging data used for this transmission is collected and reported by the PGW 114 unit in the usual manner known to those skilled in the art. . FIG. 44 also shows a set of service programs 4408 running on the optimization servers 304 and 308. These can be the same service program (as depicted in Figure 17), or they can be different service programs. Figure 44 also shows a central IP billing data collection and processing program 4410. The program 4410 is shown as running on the server 124 outside the APN LTE network, but the server location can also be within the APN LTE network, for example, in OptServer_PGW 304

115

Node. The function of the program in the architecture shown in this disclosure is_pgw 4402 procedures and multiple IPBDR_eNB The data collected and reported by the 4404 program are aggregated; the aggregated results are stored in the database for easier access by the operators of the APN LTE network; and the aggregated accounting is allocated to the formal billing system program used by the LTE network operator. The fee data is used for wireless network billing purposes. Note: In Figure 44, all the program components mentioned above are connected to the P/S proxy 1304 instance, and are therefore able to participate in the publish/subscribe messaging described throughout this disclosure.

[0385] It can be sent to each OptServegB 308 node and to OptServer_PGW 304 nodes are assigned a unique ID. This allocation may be needed to facilitate the creation of a unique ID for each P/S proxy 1304 instance deployed in the APN LTE network. In the present disclosure, when IPBDRpgw 4402 or IPBDReNB 4404 is initialized, the IDo assigned to the optimization server 304 or 308 running on it can be provided to it, respectively, and the processor type (ie, OptServerpGw 304 or OptServerpGw 304 or OptServer_eNB 308) so that the initialization program can determine whether to register with the wireless control process 3902 for the purpose of collecting data related to the transmission of user packets via the redirected bearer 312. As shown in Figure 45, IPBDR_eNB The 4404 program can be registered to the wireless control process 3902.

[0386] At the same time, the wireless control process 3902 may have the ability to set each OptServer_eNB Each P/S proxy 1304 instance on 308 and OptServerpGw 304 is respectively associated with the associated eNB 102 unit or PGW 114 unit to provide data, so as to allocate the P/S proxy 1304 to the UE 104 for the use of dedicated bearers. Communication. The start service message and restart session message in FIG. 4, FIG. 6, FIG. 39, FIG. 40, and FIG. 41 show the allocation of the IP address and port number of the P/S proxy 1304 to the UE 104. The provided data for each P/S proxy 1304 instance at the wireless control process 3902 can now also include the server ID. This allows the wireless control process 3902 to combine the registered IPBDI^b 4404 program with the IMSI and P/S proxy of the UE 104. The ID or IP address is associated with the port number information.

[0387] Once these associations are made, FIG. 45 shows that whenever the UE 104 bearer 312 is redirected to the hosted IPBDR_eNB0ptServer for 4404 instances_eNB 308, IPBDR_eNB The 4404 instance receives from the radio control process 3902 the IMSI of the UE 104 plus the IP address and port number of the P/S proxy 1304 that the UE 104 is connected to via the redirected bearer, plus the IP address assigned to the UE 104 (the IP address of the UE 104 can be Included in the registration and registration update messages sent by the UE 104 to the radio control process 3902, see the registration and registration update messages in FIG. 39 and FIG. 40). Refer to FIG. 39, FIG. 40, and FIG. 41 for the LTE processing situation in which the dedicated bearer 312 can be redirected for the UE 104.

[0388] Once the IPBDR eNB 4404 instance obtains the IP address of the UE and the IP address and port number of the P/S proxy 1304 to which the UE 104 is connected, FIG. 45 shows that the IPBDR eNB 4404 can communicate with the P/S proxy 1304 instance for notification It collects the charging data for the UE (initiated by the agent to collect () message), and makes it to the IPBDI^b 4404 program continuously or at periodic intervals, or transmit the charging data when the IPBDRew 4404 program commands. Because the P/S proxy 1304 instance is on the direct path of packets to and from the bearer 312 redirected by the UE 104, all such data can be counted, and the result is transmitted by the P/S proxy 1304 instance to IPBDI ^b 4404 instance. The data that can be collected includes: the start time and end time of charging data collection, the bearer ID of the redirected bearer 312, the number of bytes and packets sent to and received from the UE 104 via the redirected bearer 312, and These numbers send and receive bursts of bytes and packets for each topic. The association of these values with the topic can help determine whether it spans the backhaul 112 network, or whether the data is related to real-time services that require very low latency (such as interactive games) Exchange. Then, when the data is differentiated by the theme for communicating the data via the P/S proxy 1304, different charging policies can be applied to the usage data.

[0389] It is used to determine whether the backhaul 112 is used, or to determine whether it is caused by a nearby OptServer_eNB 308 to

116

The data transmission of the user 104 access point provides low latency and the analysis of topic-based usage data on whether different billing policies should be applied can be most conveniently provided by the central IP billing data collection 4410 program. The program 4410 can be provided with information that associates the topics used in the APN LTE network with other information that can be used to determine charging policies that can be applied to the collected data. Subsequently, the billing data can be reported to the billing system used by the APN LTE network operator by the central IP billing data collection 4410 program.

[0390] In addition, FIG. 45 shows that when a handover occurs, a resume session () message is sent to the UE 102. In this case, OptServer_eNB Unit 308 changes from the location of the source eNB 102 to the location of the target eNB 102. The via start data collection() message shows an explicit message interaction for initiating charging data collection at the target location. The situation can also be that the collection of charging data for redirected bearers at the source location must be ended, and any unreported data restrictions can be reported to the central IP charging data collection 4410 program. Figure 45 shows: the wireless control process 3902 can report to the IPBDR at the source location_eNB The 4404 instance sends a stop data collection () message to cause a final report from the program to the central IP billing data collection 4410 program, which causes the P/S agent 1304 at this location to stop data collection for the UE 102 and delete the source location Context data for UE 102 at the IPBDRew 4404 instance at. These latter interactions are not shown in Figure 45, but can be understood by those skilled in the art to occur as described herein.

[0391] FIG. 45 shows a stop data collection () message to indicate how to stop charging for the redirected bearer 312 of the UE 102 during the handover when the UE 102 moves away from the source location where the redirected bearer 312 was terminated. data collection. When the UE 102 transitions from the ECM connected state to the ECM idle state, and also when the UE is separated from the LTE network, data collection also needs to be stopped. In Figure 46 for the case of transition to the idle state ECM, and FIG. 47 of the needle of the UE 102 from the LTE network shown isolated out of the interaction may be used to achieve this behavior.

[0392] The transition of the UE 104 from the ECM active state to the ECM idle state is shown in section 5.3.5 of TS 23.401 v9.4.0. The LTE process is called the S1 release process. The 3GPP specification shows that the UE 104 may or may not be involved in the S1 release message exchange, but the MME 108 entity is always involved. Figures 25, 26, 27, 28, 29, and 30 show that the MME 108 entity can be connected to the P/S proxy 1304 middleware in the APN LTE network, and therefore can be used to facilitate IPBDI when the UE 104 transitions to the ECM idle state. 4404 instance notification. Figure 46 shows how the LTE S1 release procedure can be extended for the MME 108 unit so that the current IPBDR used for the UE 104 to collect the redirected bearer 312 data_eNBThe 4404 instance will be notified by the MME 108 when the UE 104 transitions to the ECM idle state. Per IPBDR_eNB The 4404 instance may subscribe to the topic "IPBDR/&lt;IMSI&gt;" when it first starts collecting usage data for the IMSI of a specific UE 104, that is, it receives the start data collection () message from the radio control process 3902 (see FIG. 45). As shown in FIG. 46, when the MME 108 receives the UE S1 context release complete message from the eNB 102 that previously served the UE 104, the UE 104 is no longer connected to the LTE network via any eNB 102 unit. The MME 108 can then publish a stop data collection (IMSI) message to the topic "IPBDR/&lt;IMS1&gt;", so it is received via the IPBDI^4404 instance serving the IMSI. IPBDR_eNB The 4404 instance can then send the remaining usage data for the UE 104 to the central IP billing data collection 4410 program, and interact with the local P/S proxy 1304 instance to stop collecting usage data for the UE 104 from the IPBDR_eNB The memory of 4404 deletes the UE 104 context data and unsubscribes to the topic "IPBDR/&lt;IMS1&gt;".

[0393] The LTE procedure for detaching the UE 104 from the LTE network is specified in section 5.4.8 of TS 23.401 v9.4.0. Three situations may be related to the current public content: that is, the UE-initiated separation process specified in TS 23.401 v9. 4.0 section 5.3. &amp; 2 is S 23. 401 v9. 4.0 section 5. 3 The separation process initiated by the MME specified in Section &amp; 3; and the separation process initiated by the HSS specified in Section 5. 3. &amp; 4 of TS 23.401 v9. 4.0. Some of these processes are in the first two

117

In this case, MME 108 can be used to send IPBDR_eNB The 4404 instance issued a stop data collection (IMSI) message. One situation is when the MME 108 receives the LTE delete session response message from the SGW 110, and the other situation is when the S1 release process is completed with the MME 108 receiving the SI UE context release complete message (see TS 23.401 v9. 4. Figure 5. 3. 8. 2-1 and 5.&amp; 3. 3-l) in 0) o If the S1 release process occurs during these interactions, the preferred point for the MME 108 to issue the stop data collection () message can be separated This end of that part of the process. Otherwise, the MME 108 may issue a stop data collection () message when it receives the LTE delete session response message from the SGW 110. When the separation is a separation process initiated by the HSS, the MME 108 may preferably issue a stop data collection () message after the S1 release part of the separation process is completed, but alternatively, when the MME 108 sends a location cancellation Ack message to the HSS 120. See Figure 47.

[0394] Note: Although Figure 45, Figure 46, and Figure 47 illustrate message interactions using the P/S proxy 1304 middleware facility, the description provided herein does not include a complete set of topics that can be used for these exchanges. The previous paragraphs and the above sections of this disclosure have included teachings on how these topics can be structured to provide effective communication between all participating entities, and those skilled in the art can apply these teachings to the message exchanges in this disclosure. .

[0395] In addition to collecting and reporting usage data across the redirected bearer 312 associated with a particular UE 104, the IPBDI ^b 4404 procedure, and likewise, IPBDR_pgw The 4402 programs can also report charging data for resource usage that occurs on their processing nodes. In one embodiment of this capability, program instances can periodically obtain data collected by the operating system for their computing nodes. Generally, these programs can collect the size of the program text and the .bss (BP, RAM memory) used by each service program 4408 shown in FIG. 44. Therefore, the collected usage data can be released to the central IP billing data collection program 4410 for aggregation, accumulation into a database, and for sending to the LTE network billing system.

[0396] In order to obtain the number of bytes of permanent storage used by the service program 4408 instance, and the amount of time for permanent storage of the service program 4408 data, IPBDRpcw 4402 and IPBDR_eNB The 4404 instance can be used to construct the interface of the local disk system used to provide this information to these billing data collection programs. For example, the disk or persistent storage system may be segmented, so the service program 4408 data is stored in one or more specific segments. The IPBDRpgw 4402 instance and the IPBDRew 4404 instance can be registered on their respective optimization servers 304 and 308 processors in order to receive notifications whenever these segments are changed. The agreement with the provider of the service program 4408 may be necessary to allow the stored data to be tagged with an ID that identifies the provider of the service program 4408 for which the data is stored. With this type of agreement, it can be seen: IPBDR_pgw 4402 and IPBDR_eNB The 4404 instance can collect permanent storage usage data for a specific chargeable entity. The usage data may include: the number of bytes stored, the start time, the end time, or the duration of the storage, the node that stores the data, the amount of access to a specific storage item per hour, and the amount of access to a specific storage item per day. The total amount of visits, the average length of time the user spends to access the content item, the total amount of data involved in using the backhaul 112 to transmit a specific stored content item, and the total amount of data involved in not using the backhaul 112 to transmit a specific content item Quantity, the number of control messages used to deliver specific content items per hour per day. Then, the permanent storage usage data can be formatted and released to the central IP billing data collection program 4410 for aggregation and accumulation into a database, and for sending to the LTE network billing system.

[0397] The effective reduction of inter-cell interference using agile beams in all wireless networks is the interference to users in a cell coverage area caused by signals sent by neighboring cells. This kind of interference is called inter-cell interference, and is especially encountered by users near the border of two adjacent cells. See Fig. 48, Fig. 48 shows two adjacent cells simulated as a hexagonal area 4802, where the solid dots represent the antennas of the cells that generate the RF signal 4808. The RF signal 4808 from each cell is set to correspond to that of neighboring cells

118

The coverage areas overlap, because otherwise it will lead to RF coverage holes. The area 4804 where RF signals overlap is an area where inter-cell interference occurs. Because of this interference, the data rate provided to users located in the cell boundary area 4804 will be reduced, and therefore the cell capacity and throughput, and user experience will be negatively affected. In an LTE wireless network, users are allocated subcarriers on which user data is sent or received. These sub-carriers are designed with orthogonal standards, so that users allocated to a subset of sub-carriers will not be interfered by transmissions of other users from different sets of allocated sub-carriers. However, near the cell boundary, each of the two neighboring cells may have allocated the same set of subcarriers to users in its respective cell boundary area 4804 (which is part of its cell coverage area 712). In this case, each of these users may be interfered by transmissions in neighboring cells that use the same subcarriers as the subcarriers allocated to a given user.

[0398] Technologies for reducing or eliminating such inter-cell interference have been sought for a long time. The current technology for LTE may include: dividing the frequency band of subcarriers into subsets, so that one subset of subcarriers is allocated only to users near the border of the serving cell, and the second subset is allocated to users located inside the serving cell. user. The subsets may be arranged in each of the sets of neighboring cells, so that different subsets of subcarriers are used at the boundaries of these cells. Although this technique alleviates the problem of inter-cell interference, it leads to a decrease in overall cell throughput and a decrease in the data rate of a single user because only a subset of all available subcarriers can be used for allocation to any user.

[0399] Another technique currently being explored may be to enable neighboring cells to communicate with each other in real time in order to notify the set of subcarriers to be allocated to users located in the boundary 4804 of their cell coverage area 712. This technique may allow any user to use the entire set of subcarriers, but may result in additional communication between base stations to coordinate their use of the available set of subcarriers. If sub-carriers are being allocated to users at the cell boundary of neighboring cells, this technique results in the failure to allocate sub-carriers to users at the cell boundary of one cell. Therefore, cell throughput and single user data rate will be negatively affected. This technique is called inter-cell interference coordination.

[0400] The present disclosure does not use any of the above-mentioned technologies. Instead, it can take advantage of the use of agile beamforming previously discussed in this disclosure. In a given 1 millisecond interval, a cell using agile beamforming generates a set of RF beams 902 (eg, four beams) covering a subset of the total cell coverage area 712. Different sets (four) of RF beams 902 are generated in each of the four 1 millisecond intervals in the LTE FDD system, so that the 16 RF beams 902 generated in this way span the entire cell coverage area 712. In the fifth millisecond, the first set of RF beams 902 is generated again, followed by the second set of RF beams 902 in the first millisecond, and so on, and the rotation of the agile beam can continue to sweep the cell coverage area with a period of four milliseconds . An example of a set of sixteen agile beams 902 covering the area 712 of the FDD LTE cell is shown in FIG. 9.

[0401] Using the hexagonal model of the cell coverage area 712, FIG. 49 shows an example arrangement of sixteen RF beam areas 902 that collectively span the cell coverage area 712. FIG. 49 shows a set of sixteen RF beam 902 areas divided into four groups with four RF beam areas 902 as a group, which is used to span the cell coverage area 712, in which, in the same manner, the groups belonging to the same set are Add shadows to sub-regions. All sub-regions with the same shadow are covered by RF beams generated in the same 1 millisecond interval. It can be pointed out in Fig. 49 that the RF beam 902 cannot be included in the sub-area shown, but to some extent spreads to the adjacent sub-area, and also spreads to the cell boundary of the sub-area of the adjacent cell. . By using a large set of antennas to generate agile beams, the spread to adjacent sub-regions can be minimized, because the RF beam 902 can be better focused, and the RF signal level of the specific beam 902 can be outside its target coverage area Fast decay. Note that in Figure 49, in general, the sub-regions 902 generated in any single 1 millisecond interval are separated by one or more sub-regions 902 in the same cell. Therefore, in any 1 millisecond interval, the use of agile beamforming allows the same

119

The sub-carriers are allocated to users in the same cell but in different sub-regions 902 (up to four users). Compared with a cell that does not use agile beamforming, the cell capacity and throughput, as well as the maximum data rate that can be allocated to any user, can be greatly increased.

[0402] Therefore, it can be pointed out that if the RF beam 902 in the neighboring cell can be arranged to rotate so that the RF beam 902 covering the neighboring sub-areas in the neighboring cell is not generated in the same 1 millisecond interval, then you can not resort to The problem of inter-cell interference is solved by additional communication without resorting to limiting the set of subcarriers that can be allocated to users.

[0403] Establishing non-adjacent RF beam patterns in cells of the same LTE base station This disclosure presents a situation where the same set of four RF beam sub-regions 902 is generated in each cell (although not necessarily in each cell). It is at the same time in the cell). It should be noted that if sixteen RF beams 902 are arranged in a pattern where only one, two or three RF beams 902 cover any boundary 4804 of the cell, then it is possible to arrange the beam selection in adjacent cells so that there are no two The adjacent RF beam 902 sub-regions are generated in the same 1 millisecond interval. However, if the pattern of the RF beam sub-regions causes them to be four or more RF beam 902 sub-regions at any cell boundary 4804, it is impossible not to cause two or more adjacent sub-regions to be in the same In the case of generation in 1 millisecond interval, beam rotation is selected in each cell.

[0404] FIG. 50 shows the case of a base station supporting three cells. The antenna of the base station system is located at the solid black dot in FIG. 50, and the three cells are marked as α1, B1, and Y1. The RF beam region 902 sub-regions are labeled 1-16. The same set of four RF beam regions 902 is used for each cell, and for the RF beam 902 geometry shown in FIG. 50, the same RF beam 902 rotation pattern can be used for each cell. Therefore, in the first 1 millisecond interval, each of the three cells generates an RF beam 902 that covers sub-areas 4, 6, 11, 13 in the coverage area 712 of its corresponding cell. In Figure 50, these sub-regions are shaded with vertical lines. Note: At the boundary between any two cells, adjacent sub-regions in adjacent cells are not generated in this time interval, therefore, there is no inter-cell interference in this first millisecond of operation.

[0405] In the first millisecond of operation, FIG. 50 shows that each cell generates RF beam regions 902 covering sub-regions 2.8.10 and 16 in its corresponding cell coverage area 712, these regions having dotted shading. It can be seen again that at the boundary between any two cells, adjacent sub-areas in adjacent cells are not generated in this time interval. Therefore, there is no inter-cell interference in the second millisecond of operation.

[0406] In the third millisecond of operation, FIG. 50 shows that each cell generates RF beam regions 902 covering sub-regions 1, 7, 9, 15 in its corresponding cell coverage area 712, these regions having fine hashes. Shaped shadows. It can be seen again that at the boundary between any two cells, adjacent sub-areas in adjacent cells are not generated in this time interval. Therefore, there is no inter-cell interference in the third millisecond of operation.

[0407] In the fourth millisecond of operation, FIG. 50 shows that each cell generates an RF beam area 902 covering sub-areas 3, 5, 12, and 14 in its corresponding cell coverage area 712, and these areas have oblique blocks. shadow. It can be seen again that at the boundary between any two cells, adjacent sub-regions in adjacent cells are not generated. Therefore, there is no inter-cell interference in the fourth millisecond of operation.

[0408] The first set of RF beam regions 902 4, 6, 11, 13 are generated again in the fifth millisecond of operation, so the pattern generated by the RF beam 902 repeats again. Therefore, it can be seen that the RF beam rotation pattern selected for each cell in FIG. 50 does not cause inter-cell interference. No inter-cell communication or coordination is required, and no restrictions are imposed on the LTE subcarriers that can be allocated to users in any of the RF beam 902 areas in any given millisecond of operation. The selection of the sub-regions of the RF beam 902 that constitute a group of four is not unique, and the rotation pattern shown in FIG. 50

120

not the only one. It is obvious to those skilled in the art that other options for the sub-region of the RF beam 902 and other options for the RF beam rotation mode can be selected without the same result of inter-cell interference. [0409] Establishing non-adjacent RF beam patterns in neighboring cells of different LTE base stations FIG. 51 extends the results shown in FIG. 50 by adding neighboring cells of neighboring LTE base stations 2, 3, and 4. To make it easier to understand these results, FIG. 51 shows only the neighboring cells of the cell α1. In this hexagonal representation of cells, each cell has six sides, so each cell has six neighboring cells. Two of the adjacent cells, B1 and Y1, are in the same base station system as a1, and the result of their RF beam rotation pattern has been shown in FIG. 50. As shown in Figure 51, the other cells adjacent to the cell α1 are B2 and Y2 in the base station system 2, B3 in the base station system 3, and γ4 in the base station system 4._οThe boundary of cell α 1 is highlighted to make it easier to see that in any two adjacent cells (that is, at any boundary 4804 of cell α 1), no adjacent sub-regions are generated at the same time. When the RF sub-area is generated in the cell, the adjacent sub-area (with different shadows) in the adjacent cell is not generated.

[0410] FIG. 51 lists the subsequent RF beam rotation patterns of the cells B2 and Y2 adjacent to the cell α1 but not in the same base station system, and each cell in β3 and Y4. Table 9 shows beam rotation patterns selected for these cells adjacent to the cell a1 and located in a base station system different from the cell a1. It should be pointed out that in Figure 51, the adjacent sub-regions at the boundary between cells Y2 and B2 and the boundary between cell Y2 and B3 also have different shading patterns, thereby indicating that there is a difference between these cells. No inter-cell interference occurs between. The same conclusion can be drawn for the boundary between cells B2 and Y4 and for the boundary between cells B3 and Y1. See Figure 51.

[0411] Table 9: Examples of beam rotation patterns for cells adjacent to a given cell but located in a different base station system

<td>Base station system</td><td>Community</td><td>Spindle to ΛΊί-Jffi</td>

<td>1</td><td>α 1</td><td>msi. 1: 4, 6, Ή, 13msc2j 2, 8» 10» 161, 7.% 15msc4: 3, 5, 12, 14</td>

<td rowspan="2">2</td><td>Ρ2</td><td>ins cl· 4- 6- H-'138, 10. 16niscJ: 3· 5# Hi 14msc4: It 15</td>

<td>¥2</td><td>inscl: 4. 6, ί1 13msc2: 3, 5, 12, 14mse3: 2. 8, 10, 16msc4: 1. 7. 9, 15</td>

<td>3</td><td>03</td><td>mscl: 4, 6, 11&gt; 131. 7. 9, 15wise?: 3, 5, 12, 14 msc4: 2, 8, 10, 16</td>

<td>4</td><td>¥4</td><td>inscl: 4, 6. 11. 13msc2: 3, 5, 12, 14 [inse.^: 1. 7. 9, 15msc4: 2» 8, 10, 16</td>

[0412] The example of FIG. 51 can be continued to show that when the remaining cells of base station systems 2, 3, and 4 are added, RF can be selected

121

The beam 902 rotates the pattern so that no inter-cell interference is generated again at any boundary of any cell. The process of selecting the rotation pattern of the RF beam 902 can be extended to each base station system and each cell in the LTE wireless network. FIG. 52 shows the results when the cell α 2 is added to the base station system 2, the cells α 3 and Y 3 are added to the base station system 3, and the cells α 4 and B 4 are added to the base station system 4. The rotation pattern of the RF beam 902 is shown for each of these cells in Figure 52, and the boundary between each pair of adjacent cells is highlighted to make it easier to see that there is no same shadow across any inter-cell boundary The sub-regions are adjacent to each other. Therefore, as disclosed herein, when agile beams are used in an LTE wireless system, inter-cell interference can be avoided.

[0413] Arrangement of time synchronization in each cell for RF beamforming Figures 50, 51, and 52 show the use of agile beamforming for three cells in one base station system and systems in multiple base station systems. How to avoid inter-cell interference in a wireless system. In each case, the base station system must maintain the same concept of start time, so each cell can determine which subset of the RF beam area 902 must be generated in any given millisecond interval. Therefore, the accuracy of time synchronization across all cells must be much less than the tolerance of 1 millisecond. The RF beam pattern 902 repeats every 4 milliseconds in each cell, therefore, a given set of four RF beams 902 appears in the same subframe of the LTE frame every twenty milliseconds (ie, every other LTE frame) . If each cell can determine when the first millisecond of an odd (or even) LTE frame occurs, then all cells can generate the correct subset of the RF beam 902 pattern in each 1 millisecond interval.

[0414] There are at least two methods of generating the desired results, wherein no new invention is required for this purpose. The first method can be if all base station systems in the wireless network use GPS for timing to operate. In this case, each base station system can have the concept of the same current time with an accuracy better than 20 nanoseconds. Therefore, each cell can be synchronized, for example, starting an odd number of LTE frames that coincide with the 1 second mark of the GPS timing system. (The duration of each LTE frame is 10 milliseconds) If GPS is not available for any or all base station systems in the LTE network, then the Precision Time Protocol (PTP) specified in the IEEE 1588 standard can be used. For example, the master clock that is part of the IEEE 1588 timing system can be synchronized with GPS time, and precise timing information can be allocated to each base station system in the LTE network that is synchronized with the master clock. Here, since GPS timing is used, then each cell can, for example, synchronize its odd LTE frame with the 1-second mark of the IEEE 1588 system. The accuracy obtained can be better than 1 millisecond, and can therefore be used for the purpose of synchronizing LTE cells with the pattern of the RF beam 902 they generate.

[0415] Baseband data transmission and reception beamforming techniques in LTE wireless base stations using periodic scanning RF beamforming have been used in the fields of audio signal processing, sonar signal processing, and radio frequency signal processing for many years in order to improve system operation. In many cases, these systems locate the transmitting or receiving point, and then focus the system antenna to create a beam aimed at that point. The system disclosed herein operates in a different way and takes advantage of the fact that in an LTE wireless system, user equipment is scheduled to receive downlink transmissions or generate uplink transmissions. The disclosed system does not focus the antenna beam on a specific user, but generates m sets of N RF beam patterns 902, where a given set of N RF beams 902 covers N sub-regions of the total cell coverage area Fixed collection. The performance of the system is best when these sub-areas are not adjacent. As disclosed herein, the maximum number of sets of N RF beam patterns 902 can be limited to 4 in the LTE FDD system, and the maximum number of sets of N RF beam patterns 902 can be limited to 4 in the LTE TDD system 1, 2, or 3, as disclosed herein, this depends on the U/D configuration 1002 of the TDD system. The total number of RF beams 902, m multiplied by N, can be designed to overlap the total cell coverage area 712. In the LTE FDD system, the RF beam direction Each of the m sets of the graph 902 can be generated in a 1 millisecond subframe of an LTE frame, where the m sets can fill every four consecutive subframes in the LTE FDD system with the same order, and therefore as described herein As disclosed in, there are 4

122

The period of the subframe. In the LTE TDD system, each of the m sets of RF beam patterns can be generated in a 1 millisecond subframe of an LTE frame, where, as disclosed herein, these m sets can depend on TDD U/ The restricted way of D configuration 1002 is allocated across 10 subframes of each LTE frame. In the LTE FDD system, or in the LTE TDD system, it can be seen that the RF beam rotates on the cell coverage area 712 in a periodic manner. These types of beamforming systems are called periodic scanning RF beamforming systems, or periodic beamforming systems, or periodic agile beamforming systems.

[0416] The present disclosure teaches and can be used by the wireless base station digital baseband subsystem 5302 to construct and process the interface between the RF and antenna subsystem 5304 and the baseband processing subsystem 5302 of an LTE wireless RF base station using periodic scanning RF beamforming Information about the system and method of transferring data. Therefore, the present disclosure does not deal with systems and methods in the RF and antenna subsystem 5304 for generating RF beam signals transmitted or received by wireless RF base stations. The present disclosure teaches that enabling the RF and antenna subsystem 5304 to form N parallel focused RF beams 902 requires the RF and antenna subsystem 5304 to use N+1 separate data streams 5308 in the transmit direction and N+ in the receive direction. 1 separate data stream 5310 to work. For each transmit or receive direction of transmission, each of the N data streams corresponds to a different beam of the N focused RF beams 902, and an additional data stream with energy covers the entire area of the cell The additional RF signal corresponds to the cell-wide sending data stream or the cell-wide receiving data stream. The teachings disclosed herein are related to the placement of different types of information into each of these data streams, and the extraction of different types of information from the received data streams. Therefore, these teachings describe the operation of the baseband subsystem 5302 of a wireless RF base station using periodic scanning RF beamforming.

[0417] FIG. 53 shows a depiction of the docking of the RF and antenna subsystem 5304 to the digital baseband processing subsystem 5302 of the wireless RF base station for the case of N=4. Therefore, Figure 53 shows five digital transmission data streams 5308 between the two subsystems, represented by cell ranges t, Bit, B2t, B3t, B4t. These streams can be carried on separate physical interfaces or can be multiplexed to a single physical interface between two subsystems. Figure 53 also shows five received digital data streams 5310 between two cells, represented by cell ranges r, Blr, B2r, B3r, B4r. These streams can be carried on separate physical interfaces or can be multiplexed to a single physical interface between two subsystems.

[0418] In each 1 millisecond LTE subframe interval in the FDD system, or in each D subframe interval in the TDD system, the MAC (Media Access Control) layer software 5312 must generate 5308 for five transmission data streams. Information. One set of information corresponds to "cell range t", where this is a stream whose data is intended to be sent across the entire cell coverage area during the upcoming 1 millisecond subframe interval. Each of the four other information sets corresponds to four transmit beam data streams labeled Blt, B2t, B3t, and B4t. Each transmit beam data stream is intended to be transmitted via a separate RF beam that "illuminates" a specific fixed cell sub-region in the upcoming 1 millisecond sub-frame interval. The PHY (physical) layer software 5314 processing can be applied to convert each set of transmission information received from the MAC layer software 5312 into a digital representation of the modulated subcarriers of the composite signal that needs to be transmitted over the LTE air interface. Therefore, the LTE physical resource block (PRB) allocated to the information in each data stream 5308 can be applied by the PHY layer software 5314.

[0419] The digital samples of each generated transmit data stream 5308 are transmitted to the RF and antenna subsystem 5304, which contains an array of antenna elements for generating RF beam signals 902 and cell-wide RF signals. Each of the five digital data streams 5308 is further processed to generate a cell-wide RF transmission signal, plus four RF transmission beam signals 902 sent over the air interface.

[0420] The receiving process is similar to the sending process of beamforming. In each 1 millisecond interval in the FDD system, or in each U subframe in the TDD system, the array of antenna elements in the RF and antenna subsystem 5304, plus additional processing components, generates five digital received signals 5310 , One corresponding to each RF receiving beam generated in the interval, outside

123

Add one to correspond to the cell-wide RF received signal. These signals are marked by cell ranges r, Blr, B2r, B3r, B4r in FIG. 53, and are sent to the wireless base station digital baseband subsystem 5302 through the interface.

[0421] LTE is an OFDMA (Orthogonal Frequency Division Multiple Access) system. Orthogonal Frequency Division Multiple Access is a scheme that multiplexes multiple users onto the 0FDM (Orthogonal Frequency Division Multiplexing) air interface. The multiple sub-carrier frequencies include the entire LTE bandwidth for a particular system, where the sub-carrier spacing is selected so that these sub-carriers are orthogonal to each other in the sense specified by TS 36.211 a40. The spacing between sub-carriers is usually 15 kHz. User multiple access is achieved by allocating a subset of the total set of subcarriers to different users at different times. Therefore, sub-carrier resources are allocated to users in a time-sharing manner and a frequency-sharing manner. LTE signals are allocated to users in units of 12 adjacent subcarriers (180 kHz) called physical resource blocks (PRBs). The allocation is for a time interval of 0.5 milliseconds, and usually contains 7 symbols. In the current version of the standard, the modulation mode of these symbols can be QPSK.16QAM or 64QAM. The OFDMA symbol period is 66.7 microseconds.

[0422] The PRB and the time domain are shown as a collection of resources, where the PRB can be used for allocation to the UE in a given time slot. The time domain is divided into a series of frames, each frame is 10 milliseconds long. Each frame includes 10 subframes each having a length of 1 millisecond, and each subframe includes two time slots each having a length of 0.5 milliseconds. In each 0.5 millisecond time slot, there are 7 (usually) symbol intervals. In each symbol time interval (66.7 us), the symbol can modulate the assigned sub-carrier. The combination of symbol time and subcarrier is called a resource unit. In each slot, there are 84 (12 times 7) resource units per PRB; and in each subframe, there are 168 resource units per PRB. The view of the resource unit (subcarrier frequency and symbol time axis) is called the resource grid.

[0423] Some of the resource units are allocated to the reference signal, and the reference signal is transmitted with a predetermined amplitude and phase. These signals are sent by the PHY layer software of the wireless base station and the UE PHY layer software, and allow the receiving end to perform relevant demodulation of the radio channel or determine the radio channel status. Other resource units are allocated to a set of channels used to convey control and other information. The remaining (most of) resource units can be used to allocate to the UE for downlink user data transmission and for uplink user data transmission.

[0424] Table 10 lists a set of reference signals used for downlink transmission, and describes the function of each signal. Table 11 lists the set of physical layer data channels used for downlink transmission and describes the function of each data channel. Table 12 lists the set of reference signals used for uplink transmission and also describes their functions. Table 13 lists the set of uplink physical layer data channels and describes their functions. These tables can be used to determine the placement of each reference signal and each data channel in the data stream used in the periodic scanning RF beamforming system.

[0425] Table 10: Summary of Downlink Reference Signals

124

<td>Road signal</td><td>Reference Xinfang subtype</td><td>Features</td>

<td>Pssl: synchronization signal</td><td></td><td>Use]: cell search and initial synchronization; small KlOfllW system's synchronized disk and timing transmission</td>

<td>Synchronization signal</td><td></td><td>few# (10W) late, and transmit the rest of the cell ID</td>

<td rowspan="5">Reflect Ruoxinxi (Pilot)</td><td>RS on the right of the cell</td><td rowspan="5">Use Τ-ΤίΓ link channel accounting and 11Γ» data relative demodulation</td>

<td>Ugly</td>

<td>Track status information &lt;CSI) RS</td>

<td>RS</td>

<td>Positioning extension</td>

[0426] Table 11: Downlink Physical Layer Data Channel Summary

<td>Downlink channel</td><td>Features</td>

<td>Physical Downlink Broadcast Channel (PBCH)</td><td>Transmit cell-specific information (for example, the number of transmitting antennas, system bandwidth)</td>

<td>Physical Control Format Indicator Channel (PCFICH)</td><td>The number of OFDM symbols used for PDCCH in the transmission subframe</td>

<td>Physical Hybrid ARQ Indicator Channel (PHICH)</td><td>Transmit H-ARQ feedback for UE transmission to UE</td>

<td>Physical Downlink Control Channel (PDCCH)</td><td>Transmit UL and DL scheduling information and other information</td>

<td>Physical Downlink Shared Channel (PDSCH)</td><td>Some system block information (SBI) for transmitting user data, paging messages and broadcast channels</td>

[0427] Table 12: Summary of Uplink Reference Signals

<td>Uplink reference signal</td><td>Features</td>

<td>Demodulation reference signal for shared channel (PUSCII-DMRS)</td><td>For uplink shared channel related demodulation (per UE)</td>

<td>Demodulation reference signal for control channel (PUCCH-DMRS)</td><td>For uplink control channel related demodulation (per UE)</td>

<td>Sounding Reference Signal (SRS)</td><td>When PUSCH or PUCCH is not scheduled, it is used for uplink channel estimation</td>

[0428] Table 13: Uplink Physical Layer Data Channel Summary

<td>Uplink channel</td><td>Features</td>

<td>Physical Random Access Channel (PRACH)</td><td>Used to request signaling establishment from the wireless RF base station</td>

<td>Physical Uplink Control Channel (PUCCH)</td><td>Carry ACK/NAK, CQI information and scheduling request for downlink packets</td>

<td>Physical Uplink Shared Channel (PUSCH)</td><td>Carry user data</td>

[0429] Based on the function of each reference signal and each data channel, it is possible to make information about which digital data stream is used for the baseband when each reference signal is transmitted or received, and when the information for each data channel is transmitted or received. The decision of the interface between the subsystem and the RF and antenna subsystem. The decision may be to use a digital data stream corresponding to a cell-wide RF signal, or to use a digital data stream corresponding to a specific RF beam signal covering the current user location. The resulting determinations can be reflected in the following table: Table 14 for downlink reference signals, Table 15 for downlink physical layer data channels, Table 16 for uplink reference signals, Table 16 for uplink physical layer data channelsTable of17. The table 17.

[0430] Table 14: Mapping Downlink Reference Signals to Transmission Data Streams

125

<td>Reference signal</td><td>Cell-wide transmission data stream</td><td>Transmission data stream for each beam</td>

<td>Master sync signal</td><td>Must be seen by all UEs at all times and at all locations</td><td></td>

<td>Auxiliary sync signal</td><td>Must be seen by all UEs at all times and at all locations</td><td></td>

<td>UE-specific reference signal</td><td>When the UE location is unknown, this signal can be sent with the downlink PDSCH transmission of user data to allow relevant demodulation at the UE.</td><td>When the UE location is known, this signal can be sent with the downlink PDSCH transmission of user plane data to allow relevant demodulation at the UE.</td>

<td>Cell-specific reference signal</td><td>These signals must be seen by all UEs at all times and at all locations.</td><td></td>

<td>MBS FN reference signal</td><td>If these signals are used, they must be seen by all UEs at all times and at all locations.</td><td></td>

<td>Positioning reference signal</td><td>If these signals are used, they must be seen by all UEs at all times and at all locations.</td><td></td>

<td>CST reference signal</td><td></td><td>The signal can be sent in the beam signal that needs to be measured by the UE</td>

[0431] Table 15: Mapping the downlink physical layer data channel to the transmission data stream

<td>Downlink physical layer data channel</td><td>Cell-wide transmission data stream</td><td>Transmission data stream for each beam</td>

<td>PBCH</td><td>System timing information, cell ID and MIB information must be received by any UE in any location at any time. The UE must receive this information before the UE accesses the cell.</td><td></td>

<td>PDCCH</td><td>Before the location of the UE is known, send PDCCH control information to the UE during the random access procedure</td><td></td>

<td>PHICH</td><td>H-ARQ ACK/NAK must be sent to any UE at any location at any time.</td><td></td>

<td>PMCH</td><td>Multicast data must be received by any UE at any location at any time.</td><td></td>

<td>PDSCH</td><td>The data used for the logical multicast channel needs to be sent in the cell range so that it can be received by UEs at any location.</td><td></td>

<td>PDSCH</td><td>When the location of the UE is unknown, for example, when the RA contention resolution message is sent, user plane data is sent to the UE via a cell-wide data flow.</td><td>If the UE location is unknown, the user plane data scheduling is used for downlink transmission in the RF beam covering the UE location. The data may include data sent from the application being used by the user, as well as data sent to the UE via a logical dedicated control channel.</td>

<td>PDSCH</td><td>The logical common control channel information from the high-level protocol in the wireless RF base station is sent via the PDSCH, and needs to be received by the UE before the location of the UE is known.</td><td></td>

<td>PDSCH</td><td>The broadcast channel SIB sent via the PDSCH must be received by the UE before the UE accesses the system and before the location of the UE is known.</td><td></td>

<td>PDSCH</td><td>The paging message must be sent in the cell area in order to reach the UE in any location at any time.</td><td></td>

[0432] Table 16: Mapping the uplink reference signal to the received data stream

<td>Uplink reference signal</td><td>Cell-wide received data stream</td><td>Receive data stream for each beam</td>

<td>PUSCH-DMRS</td><td>When the UE location is unknown, transmit and receive the corresponding UE PUSCH in the cell-wide RF signal</td><td>When the UE position is known, transmit and receive in the RF beam together with the corresponding UE PUSCH</td>

<td>PUCCH-DMRS</td><td>Receive UE PUCCH data in the received signal in the cell range</td><td></td>

<td>Sounding reference signal</td><td></td><td>Receive in the RF beam signal to allow the wireless base station to determine the uplink channel characteristics of the beam-based reception of user plane data</td>

[0433] Μ ΙΛ

126

<td>Uplink physical layer data channel</td><td>The received data it</td><td>Receive data stream for each beam</td>

<td>PRACH</td><td>PKACIM1 sends data</td><td></td>

<td>ίΊ &lt;&lt;Η</td><td>It is received in the receiving stream of the fan cell to allow reporting requests and measuring stations at the total time, and to avoid each: When M Siam moves to a new IC wave position, the channel is newly allocated.</td><td></td>

<td>1Ί S( li</td><td>If the location of IE is unknown*, then receive user peace data via Xiaofanguos access to animal husbandry streams</td><td>If the location is known, then the data sent on the logical dedicated control channel of the number of user plane data is received through the receive beam signal</td>

<td>PUSCH</td><td>The logical common control channel signaling is sent to the student at the location L1 Zhizhiba. This must be connected to the receiving signal of the cell country.</td><td></td>

[0434] It can be seen from Table 14 and Table 15 that the reference signal and the physical layer data channel information sent to the UE using the RF beam signal corresponding to the RF beam signal covering the location of the UE may be restricted to allow access via RF A UE-specific reference signal for demodulation of user data sent by beam signals, a CS1 reference signal sent on the downlink that allows the UE to report downlink channel conditions, and UE data sent via PDSCH when the location of the UE is known. All other downlink reference signals and physical layer data channel information can be sent via the cell-wide transmission data stream. When the location of the UE is unknown or when the UE data is also sent via the transmit RF beam data stream, the UE data can be sent to the RF and antenna subsystem via the cell-wide transmit data stream. In the latter case, transmission mode 2 (transmit diversity) can be used. When UE data is only sent in transmit RF data, transmission mode 7 can be used (ie, logical antenna port 5, beamforming port is implied).

[0435] It can be seen from Table 16 and Table 17 that the reference signal and physical layer data channel information received from the UE using the RF beam covering the location of the UE can be limited to: when the location of the UE is known, it can be sent together with the UE data And the PUSCH-DMRS that can be received via RF beam signals, the SRS signal sent by the UE when the radio base station determines the uplink channel condition and the UE location is known, and the UE data sent via the PUSCH when the UE location is known. All other uplink reference signals and physical layer data channel information can be received via the cell-wide received data stream.

[0436] Therefore, the teachings presented in this disclosure can be used to constrain and guide the behavior of the MAC layer software 5312 and the PHY layer software 5314 in the operation of an LTE wireless base station using a periodic scanning RF beamforming system. In each transmission time interval (TTI, 1 millisecond interval of LTE frames) in the FDD system, or in each D sub-frame in the TDD system, the MAC layer software can interact with the PHY layer software in order to target the The data sent during the TTI gives a set of transport blocks, where, for each transport block, the MAC layer software can also indicate the transmit beam data stream that will be used to send the data block. For each common channel, the MAC layer software can provide the transmit beam data to the PHY layer software in advance

127

The mapping of the flow. In addition, the PHY layer software may be provided in advance by the MAC layer, or indicated by the MAC layer in each TTI so as to include reference signals suitable for the set of transport blocks in the transmission data stream presented to the PHY layer.

[0437] Similarly, in each TTI in the FDD system (that is, the 1 millisecond interval of the LTE frame), or in each U subframe in the TDD system, the MAC layer software can interact with the PHY layer software for instructions. A set of resource units or PRBs used to detect data for a specific common or control channel, reference signal, or uplink shared channel, and can also indicate a received beam data stream for performing detection processing. The MAC layer software may provide some of these items in advance to the PHY layer software (for example, for the PRACH channel). It may be important for the PHY layer software to indicate to the MAC layer software the received data flow for each entry of the detected data presented by the PHY layer to the MAC layer.

[0438] Other teachings in this disclosure solve the problem of locating and tracking UEs in sub-regions covered by RF beams generated in a periodic scanning RF beamforming system. In order for the wireless base station MAC layer software to better determine which UEs are allowed to be scheduled for data transmission uplink and downlink, the MAC layer can maintain a list of each RF beam in the RF beams generated by the system, where Each list contains a set of UEs known to be located in the sub-region corresponding to the RF beam represented by the list.

[0439] Although only a few embodiments of the present disclosure have been shown and described, it is obvious to those skilled in the art that the spirit and spirit of the present disclosure described in the following claims can be Changes and modifications are made to these embodiments in the context of the scope. The complete contents of all foreign and domestic patent applications and patents and all other publications cited in this article are hereby incorporated into this article to the full extent permitted by law.

[0440] The methods and systems described herein may be partially or wholly deployed by a machine that executes computer software, program code, and/or instructions on a processor. The present disclosure can be implemented as: a method on a machine, a system or device as a part of the machine or related to the machine, or a computer program product embodied as a computer readable medium executed on one or more machines. The processor can be a part of a server, a client, a network infrastructure, a mobile computing platform, a stationary computing platform, or other computing platforms. The processor may be any type of computing or processing device capable of executing program instructions, codes, binary instructions, etc. The processor can be or include a signal processor, a digital processor, an embedded processor, a microprocessor, or any variant such as a coprocessor that can directly or indirectly facilitate the execution of the program code or program instructions stored thereon ( Math coprocessor, graphics coprocessor, communication coprocessor, etc.) and so on. In addition, the processor may be capable of executing multiple programs, threads, and codes. Threads can be executed at the same time to improve the performance of the processor and facilitate simultaneous operation of applications. By way of implementation, the methods, program codes, program instructions, etc. described in this document can be implemented in one or more threads. A thread can derive other threads that may have been assigned a priority associated with it, and the processor can execute these threads based on the instructions provided in the program code, based on the priority or in any other order. The processor may include: memory Store methods, codes, instructions, and programs as described in this article and elsewhere. The processor can access a storage medium that can store methods, codes, and instructions as described herein and elsewhere through the interface. The storage medium associated with the processor for storing methods, programs, codes, program instructions, or other types of instructions that can be executed by computing or processing equipment may include, but is not limited to, CD-ROM, DVD, memory, hard disk, flash drive, One or more of RAM, ROM, cache, etc.

[0441] The processor may include one or more cores that can increase the speed and performance of the multiprocessor. In an embodiment, the processor may be a dual-core processor, a quad-core processor, other chip-level multiprocessors that combine two or more independent cores (referred to as silicon cores), and the like.

[0442] The methods and systems described herein may be partially or wholly deployed by machines that execute computer software on servers, clients, firewalls, gateways, hubs, routers, or other such computers and/or network hardware. software

128

The program can be associated with servers that can include file servers, print servers, domain servers, Internet servers, intranet servers, and other variants such as auxiliary servers, host servers, distributed servers, and the like. The server may include one or more memories, processors, computer-readable media, storage media, ports (physical and virtual), communication devices, and interfaces that can access other servers, clients, machines, and devices through wired or wireless media Wait. The methods, programs, or codes as described herein and elsewhere can be executed by the server. In addition, other devices used to perform the methods as described in this application may be considered as part of the infrastructure associated with the server.

[0443] The server may provide an interface to other devices, including but not limited to: clients, other servers, printers, database servers, print servers, file servers, communication servers, distributed servers, etc. In addition, this coupling and/or connection can facilitate remote execution of programs across a network. Without departing from the scope of the present disclosure, the network connection of some or all of these devices may facilitate parallel processing of programs or methods at one or more locations. In addition, any of the devices attached to the server through an interface may include at least one storage medium capable of storing methods, programs, codes, and/or instructions. The central storage library can provide program instructions to be executed on different devices. In this implementation, the remote storage library can be used as a storage medium for program codes, instructions, and programs.

[0444] The software program may be compatible with clients that may include file clients, print clients, domain clients, Internet clients, intranet clients, and other variants such as auxiliary clients, host clients, distributed clients, etc. End associated. The client can include one or more memories, processors, computer-readable media, storage media, ports (physical and virtual), communication devices, and other clients, servers, machines, and devices that can access other clients, servers, machines, and devices through wired or wireless media Interface, etc. The methods, programs or codes described in this article and elsewhere can be executed by the client. In addition, other devices used to perform the methods as described in this application may be considered as part of the infrastructure associated with the client.

[0445] The client may provide an interface to other devices, and these devices include, but are not limited to: servers, other clients, printers, database servers, print servers, file servers, communication servers, distributed servers, etc. In addition, this coupling and/or connection can facilitate remote execution of programs across a network. Without departing from the scope of the present disclosure, the network connection of some or all of these devices may facilitate parallel processing of programs or methods at one or more locations. In addition, any of the devices attached to the client through an interface may include at least one storage medium capable of storing methods, programs, applications, codes, and/or instructions. The central storage library can provide program instructions to be executed on different devices. In this implementation, the remote storage library can be used as a storage medium for program codes, instructions, and programs.

[0446] The methods and systems described herein can be deployed in part or as a whole through a network infrastructure. The network infrastructure may include units such as computing equipment, servers, routers, hubs, firewalls, clients, personal computers, communication equipment, routing equipment, and other active and passive devices, modules and/or components known in the art . In addition to other components, computing and/or non-computing devices associated with the network infrastructure may include storage media such as flash memory, buffers, stacks, RAM, ROM, and so on. The processes, methods, program codes, and instructions described here and elsewhere can be executed by one or more units in the network infrastructure unit.

[0447] The methods, program codes, and instructions described here and elsewhere can be implemented on a cellular network with multiple cells. The cellular network can be a frequency division multiple access (FDMA) network or a code division multiple access (CDMA) network. Cellular networks can include mobile devices, cell sites, base stations, repeaters, antennas, towers, and so on. The cell network can be GSM, GPRS, 3G, EVDO, mesh or other network types.

[0448] The methods, program codes, and instructions described here and elsewhere can be used on mobile devices or through mobile

129

Equipment realization. Mobile devices may include navigation devices, cell phones, mobile phones, mobile personal digital assistants, laptop computers, palmtop computers, netbooks, pagers, e-book readers, music players, and so on. Among other components, these devices may include storage media such as flash memory, buffer RAM, ROM, and one or more computing devices. The computing device associated with the mobile device may be able to execute the program code, methods, and instructions stored thereon. Alternatively, the mobile device may be configured to cooperate with other devices to execute instructions. The mobile device can communicate with a base station that interfaces with the server and is configured to execute program code. Mobile devices can communicate on peer-to-peer networks, mesh networks, or other communication networks. The program code can be stored on a storage medium associated with the server and executed by a computing device embedded in the server. The base station may include computing devices and storage media. The storage device may store program codes and instructions executed by a computing device associated with the base station.

[0449] Computer software, program codes, and/or instructions may be stored on and/or accessed on a machine-readable medium. The machine-readable medium may include: Computer components, equipment, and recording media; semiconductor storage called random access memory (RAM); mass storage generally used for more permanent storage, such as optical disks, such as hard disks, tapes, drums, cards, and other types of magnetic Storage form; processor register, high-speed buffer memory, volatile memory, non-volatile memory; optical storage such as CD, DVD; such as flash memory (such as USB stick or key), floppy disk, magnetic tape, paper tape, punch card , Independent RAM disk, Zip drive, removable mass storage, offline storage, etc. removable media; such as dynamic memory, static memory, read/write memory, variable memory, read only memory, random access memory, sequential access Storage, location addressable storage, file addressable storage, content addressable storage, network attached storage, storage area network, barcode, magnetic ink, etc. other computer storage.

[0450] The methods and systems described herein can transform physical and/or non-physical items from one state to another state. The methods and systems described herein can also transform data identifying physical and/or non-physical items from one state to another.

[0451] The units described and depicted herein (including those in the flowcharts and block diagrams in the various drawings) imply logical boundaries between the units. However, according to software or hardware engineering practices, the depicted units and their functions can be executed as a whole software structure, as a separate software module, or as a module using external routines, codes, services, etc. through a computer executable medium. , Or any combination of these modules are implemented on a processor machine with program instructions stored thereon, and all such implementations may be within the scope of the present disclosure. Examples of these machines may include, but are not limited to: personal digital assistants, laptop computers, personal computers, mobile phones, other handheld computing devices, medical devices, wired or wireless communication devices, sensors, chips, calculators, satellites, tablet computers , E-books, accessories, electronic devices, devices with artificial intelligence, computing devices, networking devices, servers, routers, etc. In addition, the units or any other logical components depicted in the flowcharts and block diagrams may be implemented on a machine capable of executing program instructions. Therefore, although the preceding drawings and descriptions set forth the functional aspects of the disclosed system, unless explicitly stated or otherwise clearly visible from the context, Otherwise, the specific arrangement of the software used to implement these functional aspects should not be inferred from these descriptions. Similarly, it will be understood that the various steps identified and described above can be changed, and the order of the steps can be adapted to the specific application of the technology disclosed herein. All these changes and modifications are intended to fall within the scope of this disclosure. In this way, unless required by a specific application, or explicitly stated or otherwise clearly visible from the context, the depiction and/or description of the order of the various steps should not be understood as requiring a specific execution order for those steps.

[0452] The above methods and/or processes and their steps can be implemented in hardware, software, or any combination of hardware and software suitable for specific applications. The hardware may include: general-purpose computers and/or dedicated computing devices, or specific computing devices or specific aspects or components of specific computing devices. These processes can be implemented in one or more microprocessors, microcontrollers, embedded

130

It is implemented in a microcontroller, programmable digital signal processor or other programmable device together with internal and/or external memory. These processes can also or instead be embodied as: application specific integrated circuits, programmable gate arrays, programmable array logic, or any other device or combination of devices that can be configured to process electrical signals. It will also be understood that one or more of these processes can be implemented as computer executable code that can be executed on a machine readable medium.

[0453] The computer executable code can be created using a structured programming language such as: C, an object-oriented programming language such as C++, or can be stored, compiled, or interpreted to run on one of the above devices Any other high-level or low-level programming language (including assembly language, hardware description language, and database programming language and technology), as well as a heterogeneous combination of processors and processor architectures, or a combination of different hardware and software, or any combination of program instructions Other machines.

[0454] Therefore, in one aspect, each of the above methods and combinations thereof can be embodied as computer executable code that executes its steps when executed on one or more computing devices. In another aspect, these methods can be embodied as a system that performs their steps, and can be distributed among devices in a variety of ways, or all functions can be integrated into dedicated, separate devices or other hardware. In another aspect, the unit for performing the steps associated with the above-mentioned process may include any of the above-mentioned hardware and/or software. All these permutations and combinations are intended to fall within the scope of the present disclosure.

[0455] Although the present disclosure has been disclosed and described in detail in conjunction with the illustrated preferred embodiments, various modifications and improvements will become apparent to those skilled in the art. Therefore, the spirit and scope of the present disclosure are not limited by the above examples, but should be understood in the broadest sense permitted by law.

[0456] All cited documents are incorporated herein by reference.

131