Methods and systems of an all purpose broadband network

(Cross-reference of related applications) This application was filed on June 12, 2013, U.S. Patent Application No. 13 / 916,338, U.S. Patent Application No. 13 / 755,808, filed January 31, 2013, and April 11, 2013. Partial continuations of U.S. Patent Application No. 13 / 860,711 filed, each claiming the benefits of U.S. Patent Provisional Application No. 61 / 659,174 filed on June 13, 2012, November 2012. This is a partial continuation application of US Patent Application No. 13 / 667,424 filed on March 2. All of these applications are incorporated herein by reference in their entirety. (Technical field) The present disclosure relates to broadband networks, and more specifically to methods and systems for increasing bandwidth in wide area broadband networks.

(Explanation of prior art) Wireless networks are ubiquitous throughout the globe, and each of the new standard air interfaces provides users with faster data transfer rates than ever before. However, the proliferation of data applications, especially video applications, is so great that even as the data transfer rates provided by 3G and 4G networks increase and communication capacity increases, the current and expected demand for bandwidth can be met. I can't cut it. A combination of multiple factors makes it difficult to meet these user demands. One factor is the air interface itself. 3GPP (Third Generation Partnership) Project; Third Generation Partnership Project) New standards such as LTE offer the possibility to give users data transfer rates up to 10Mbps, 20Mbps or higher. However, users can expect an average cell throughput of approximately 13 Mbps for reasons that are generally distributed over the coverage area of the transmit cells. This is not enough to provide video services to just a few more users. Therefore, it is necessary to improve the utilization of the LTE air interface. Further, the inter-cell interference caused by the overlap of RF signals between the transmitting cells reduces the data transfer rate and the communication capacity that can be provided to the user located at the boundary between the cells. Some method of reducing or eliminating this cell-to-cell interference will improve the channel capacity and throughput of the system and provide these users with improved quality of service. Another factor is the overuse of backhaul equipment that connects LTE base stations (eNBs) to extended packet core (EPC) networks. Equipment operating at 1 Gbps cannot be deployed across all base stations, so a medium number of users of video applications can easily use a significant amount of backhaul bandwidth. Therefore, other services cannot be provided to the remaining users. Another factor is the way servers are deployed to offer services to wireless users. These servers are outside the wireless network and may be located far from user access points in the wireless network. The long packet transmission delay (latency) between the service program running on the server and the user access point in the wireless network can result in an inadequate user experience when using the service.

The US government needs to take advantage of many new user devices designed to run on new wireless networks such as LTE. For the US government, using a dedicated system for wireless communication requirements has become unattractive. Costs associated with collecting new spectra, and matching U.S. government user and general user requirements suggest that standard LTE networks are used in parallel by both types of users. Will be done. In this shared system, in an emergency, the government needs to be able to implement preferential access for authorized government use of the network, and when communication capacity is exhausted, non-governmental use is inevitably eliminated. .. This pattern of behavior may not be available to the extent required by the government in current wireless networks. In addition, government and commercial applications are increasingly using all types of sensors to gather information. Wireless networks capable of efficiently and quickly collecting, processing, storing, and redistributing sensor data are not available. In addition, the LTE wireless network ad hoc deployment is the best way to provide wireless services to emergency response personnel, the US military, or the general public during military operations or emergencies. Ad hoc networks can utilize airborne base stations deployed in disaster areas or military operations areas. In the case of an Airborne ad hoc network deployment (or any other deployment with a mobile-based station), the network will be serviced by the Airborne or mobile-based station due to reduced fuel or power or due to the loss of the Airborne or mobile vehicle. Must be kept up and running when it needs to be stopped.

Beamforming techniques have been used for many years to improve system operation in the areas of audio signal processing, sonar signal processing, and radio frequency signal processing. Often, these systems locate transmit or receive points and then focus the system antennas to generate a beam towards that point. Some of the teachings presented herein disclose systems that operate differently, and in cellular LTE systems, user devices are scheduled to receive or generate transmissions. I'm using it well. Such a system does not focus the antenna beam to a particular user, but rather, in a Frequency Division Duplex (FDD) system, N non-overlapping fixations at each of m 1ms intervals. Generates different patterns of position RF beams, and in a time-divided duplex (TDD) system, one of m different patterns of N fixed position RF beams in each 1 ms non-S subframe of each LTE frame. Is generated. Each RF beam covers a sub-area of the entire cell coverage area. The entire set of m × N RF beam patterns covers the cell area. After mms in the FDD system, the RF beam pattern is repeated, and after 10 ms in the TDD system, the beam pattern is repeated. Therefore, the RF beam pattern appears to rotate periodically over the cell coverage area. The user is scheduled to transmit or receive only when the beam is focused on the beam subarea containing the user position. Such systems are referred to herein by terms such as "Agile Beam Forming System", "Agile Beam Forming System", and "Periodic Beam Forming System", in frequency-divided duplex mode or time. Includes cellular LTE transceiver base stations operating in fractionated duplex mode.

In a cellular LTE system, downlink transmission can be scheduled by software in the base station called a scheduler. The scheduler can also grant authorization for uplink transmissions from the UE. In this way, the bandwidth available through the LTE air interface is allocated to different users at different times in a manner determined by the scheduler. Therefore, when agile RF beamforming techniques are used, it is important for the scheduler to recognize the current position of each UE to the accuracy of the RF beam subarea, which allows the RF beam to occur at specific 1ms intervals. Only these UEs will be allowed to authorize uplink transmissions in one of the N RF beam subareas that are about to be focused by the forming subsystem. Similarly, the scheduler needs to schedule downlink transmissions only to UEs that are found to be located in one of the N RF beam subareas that are about to be illuminated by the operation of the RF beamforming subsystem. There is.

Two modes of locating the UE within the RF beam subarea determine the RF beam position when the UE first accesses the cell (ie, after a random access procedure, after a handover procedure, or after a service request procedure). Then, the UE is tracked across the RF beam subarea as it travels across the cell coverage area. There are two ways to locate the UE within the RF beam and build an algorithm to track the UE across the RF beam: Channel Quality Indicator (CQI) measurements and Sounding Reference Signal (SRS) measurements. Can be made available. The CQI measurement can be returned after measuring the channel quality signal transmitted by the cellular radio RF base station by the UE. The SRS signal is transmitted by the UE and can be detected by a cellular radio RF base station. Therefore, CQI can be used to determine downlink channel quality, while SRS can be used to determine uplink channel quality.

In LTE TDD systems, the same frequency band is used for both uplink and downlink transmissions, so either uplink or downlink measurements of the RF channel state at each RF beam are used today. The beam that best covers the UE position is expected to make the same decision. LTE FDD systems use different frequency bands for uplink and downlink transmissions, so in RF environments where multipath reflections are common, downlink channel measurements and uplink channel measurements are the current UE. It is expected that the determination of the beam that best covers the position will be different. Therefore, the CQI-based algorithm and the SRS-based algorithm can be used to determine the RF beam for downlink transmission to the UE and the RF beam for uplink transmission from the UE.

The present disclosure relates to systems that support cellular mobile transceiver devices with multiple cellular LTE transceiver base stations, where each cellular LTE transceiver base station is in RF communication with multiple mobile transceiver devices in the RF cell coverage area and is cellular. Each RF includes an agile beam forming antenna system adapted to provide the entire coverage area of the cell coverage area by generating m different sets of fixed position patterns of N RF beams. The beam is sized to cover a sub-area of the cell coverage area, and the cell coverage area is covered by m × N RF beam patterns. Cellular LTE transceiver base stations are adapted to provide one of the following: RF Frequency Division Duplex (FDD) communication with multiple mobile transceiver devices, m 1 m 4. RF Time Division Duplex (TDD) communication with multiple mobile transceiver devices, 1 m 3, where m is the selected LTE Determined at least in part based on the TDD Uplink / Downlink (U / D) configuration settings. And whenever the RF beam is focused on a sub-area of the cell coverage area of the first cellular LTE transceiver base station adjacent to the cell coverage area of the second cellular LTE transceiver base station, the second cellular LTE transceiver The base station adjacent cell coverage area is a selective RF beam configuration configuration in which the RF beam subarea is constrained not to be adjacent to the RF beam subarea in the cell coverage area of the first cellular LTE transceiver base station.

The system is also adapted to communicate with multiple mobile transceiver devices through m different sets of cell-wide RF transmit signals, cell-wide RF receive signals, and fixed position patterns of N RF transmit beams and N RF receive beams. It can include a digital baseband processing facility, a backhaul network, and a base station optimum server. The base station optimal server is connected to the cellular LTE transceiver base station and in parallel with the cellular LTE transceiver base station to the backhaul network and is adapted to publish streaming or other application data to multiple mobile transceiver devices in the application. Includes at least one of the Publish-Subscribe broker communication facility and the base station optimal server utilization data reporting facility that collects and reports services and utilization for each of multiple mobile transceiver devices in the RF coverage area. it can.

The system is also communicably connected to a public data network gateway (PGW) on the public data network side of the PGW and (a) runs an application to serve at least one mobile transceiver device ( b) It may include a regional optimal server adapted to transfer the functionality of the application in at least one mobile transceiver device to the base station optimal server based on the utilization characteristics of at least one mobile transceiver device.

The system also provides radio control equipment communicatively connected to a regional optimal server and at least one of multiple cellular LTE transceiver base stations through a backhaul network, and a processor communicatively connected to the cellular LTE transceiver base station. Can include base scheduler equipment. The scheduler facility can schedule communication between the cellular LTE transceiver base station and multiple mobile transceiver devices, and the scheduler facility can schedule communication between the cellular LTE transceiver base station and the target mobile transceiver device. M × N based on the positioning of the target mobile transceiver device within the cell coverage area determined by a positioning algorithm that utilizes at least one of the collected channel quality indicator measurements and sounding reference signal measurements. Each of the multiple mobile transceiver devices currently accessing the LTE network through the cellular LTE transceiver base station associated with the scheduler and scheduling communication with the target mobile transceiver device to occur in one of the RF beams. Access to each mobile transceiver device to the LTE air interface can be scheduled based on the data transfer rate priority value assigned to.

The system can include multiple sensors deployed in the coverage area of at least one of the multiple cellular LTE transceiver base stations, which sensors are the base station optimal server through the Publish-Subscribe broker communication facility. Provides data collected, processed, stored, and placed by.

The access priority facility can determine the radio system access level for each of the multiple mobile transceiver devices, which radio system access level is to the cellular LTE transceiver base station while such access is restricted. Determine the priority given to the user for access and extend the priority level beyond the target audience specified in the standard.

The transceiver base station alternation facility can manage the handover of multiple mobile transceiver devices from the alternate transceiver base station to the alternate transceiver base station in the RF coverage area.

The system can include hot backup equipment, which utilizes the Publish-Subscribe broker communication equipment to retain the same application state information that is retained in the backed up active computer equipment. ..

In another aspect, the present disclosure relates to a system in which the system has a first cellular radio RF base station node that is RF-communicated with a mobile device, is connected to a backhaul network, and has an RF coverage area, and a first cellular. The radio RF base station includes at least one first base station optimum server connected to the backhaul network in parallel with the first cellular radio RF base station node, and at least one first base station. The best server is (a) between the first cellular radio RF base station node and the backhaul network, or (b) between at least one first base station best server and the backhaul network, or (c). First cellular radio RF base station node and at least one It enables data packets to be selectively sent to or from the first base station optimum server. The system also has a second cellular radio RF base station node connected to the backhaul network and having an RF coverage area, and parallel to the second cellular radio RF base station and the second cellular radio RF base station node. It can be equipped with at least one second base station optimum server connected to the backhaul network, and at least one second base station optimum server is (a) a second cellular radio RF base station. Between the node and the backhaul network, or (b) at least one Select data packets either between the second base station optimal server and the backhaul network, or (c) between the second cellular radio RF base station node and at least one second base station optimal server. It is possible to flow the target. The system is further communicably connected to a public data network gateway (PGW) on the public data network side of the PGW, (a) executing applications to provide services to mobile devices, and (b) mobile devices. Regional Optimal Servers, Regional Optimal Servers, and First and First It can include at least one of the second cellular radio RF base station nodes and radio control equipment communicatively connected. The RF coverage areas of the first and second cellular base station nodes overlap, and the radio control equipment of the mobile device from the first cellular radio RF base station node to the second cellular radio RF base station node. To manage (a) the connectivity of the application to the mobile device and (b) the transfer of application functionality to at least one base station optimal server of the second cellular radio RF base station node during the mobile device handover. It is adapted.

In another aspect, the present disclosure relates to a system that supports cellular mobile transceiver device communication with a cellular LTE transceiver base station, wherein the cellular LTE transceiver base station has a plurality of mobiles within the cell coverage area of the cellular LTE transceiver base station. Adapted for RF frequency split duplex (FDD) communication with transceiver devices, cellular radio frequency transceiver base stations generate m different sets of fixed position patterns for N RF beams to provide full coverage of the cell coverage area. Includes an agile beam forming antenna system adapted to provide an area, each RF beam is sized to cover a subarea of the cell coverage area, and the cell coverage area is covered by m x N RF beam patterns. And m is 1 m 4, and the antenna system produces each of m sets of N RF beams in different 1 millisecond subframes of the LTE frame, of the N RF beam patterns. A set of m is adapted to be generated sequentially over four consecutive 1 millisecond subframes.

In another aspect, the present disclosure relates to a system that supports a cellular mobile transceiver device with a cellular LTE transceiver base station, wherein the cellular LTE transceiver base station has multiple mobile transceivers within the cell coverage area of the cellular LTE transceiver base station. Agile beam forming antenna system adapted for RF Timed LTE (TDD) communication with devices and for cellular radio transceiver base stations to produce m different sets of fixed position patterns for N RF beams. Each RF beam is sized to cover a sub-area of the cell coverage area, and the cell coverage area is covered by m x N RF beam patterns, one of the sub-frames of the LTE TDD frame or it. In the above, each of m sets of N RF beam patterns is generated, and m sets of N RF beam patterns are sequentially generated over a plurality of consecutive LTE TDD subframes. M is 1 m 3 and the m is the selected LTE Determined at least in part based on the TDD Uplink / Downlink (U / D) configuration settings.

In another aspect, the present disclosure relates to a system for scheduling cellular mobile transceiver device communication, wherein the system comprises a cellular LTE transceiver base station and the cellular LTE transceiver base station is the cell coverage of the cellular LTE transceiver base station. Adapted to communicate with multiple mobile transceiver devices within the area, each RF includes an agile beam forming antenna system in which a cellular LTE transceiver base station produces m different sets of fixed position patterns of N RF beams. The beam covers the sub-area of the cell coverage area so that m × N RF beam patterns cover the cell coverage area. The system also features a processor-based scheduler facility communicatively connected to the cellular LTE transceiver base station, which schedules communication between the cellular LTE transceiver base station and multiple mobile transceiver devices. The facility utilizes at least one of the Channel Quality Indicator (CQI) and Sounding Reference Signal (SRS) measurements collected through the communication interaction between the cellular LTE transceiver base station and the target mobile transceiver device. Schedule communication with the target mobile transceiver device to occur in one of the m × N RF beams based on the positioning of the target mobile transceiver device within the cell coverage area determined by the positioning algorithm. To do.

In another aspect, the present disclosure relates to a system for transmitting and receiving baseband data in cellular mobile transceiver device communication. The system includes a cellular LTE transceiver base station adapted to communicate with multiple mobile transceiver devices within its cell coverage area. Cellular LTE radio transceiver base stations include digital baseband processing equipment, digital interfaces, RF equipment, and agile beamforming antenna systems. Cellular LTE transceiver base stations communicate with mobile transceiver devices through cell-wide RF transmit signals, cell-wide RF receive signals, and m different sets of fixed-position patterns of N RF transmit beams and N RF receive beams. Yes, each of the N RF transmit beams and the N RF receive beams covers the sub-area of the cell-wide coverage area, and the m × N RF beam patterns cover the area of the cell-wide coverage area. The digital baseband processing facility provides the RF facility with N transmit beam digital data streams and cell wide transmit digital data streams via a digital interface for transmission through the agile beam forming antenna system, which RF facility is an agile beam. It provides N receive beam digital data streams and cell wide receive digital data streams from the forming antenna system to the digital baseband processing facility via a digital interface. Digital baseband processing equipment is used for transmission in at least one of m × N RF beams and cell-wide RF transmission signals through at least one of N transmission beam digital data streams and cell-wide transmission digital data streams. Processes transmissions to mobile transceiver devices and N receive beam digital data streams and cell wide receive digital data streams from at least one of m × N RF receive beams and cell wide RF receive signals.

In another aspect, the present disclosure relates to a system that reduces cell-to-cell interference in a cellular mobile communication network. The system is adapted to communicate with multiple mobile transceiver devices within each cell coverage area and is agile to produce multiple cells and m1 different sets of fixed position patterns of N1 RF beams in each cell. Equipped with a first cellular LTE transceiver base station including a beam forming antenna system, each RF beam covers a sub-area of the cell coverage area of the first cellular LTE transceiver base station, with m1 x N1 in each cell. The RF beam pattern covers the area of each cell coverage area of the first cellular LTE transceiver base station. The first cellular LTE transceiver base station irradiates N1 RF beams in each cell so that none of the irradiated RF beam subareas are adjacent to each other. The system is adapted to communicate with multiple mobile transceiver devices within each cell coverage area and is agile that produces multiple cells and m2 different sets of fixed position patterns of N2 RF beams in each cell. Equipped with a second cellular LTE transceiver base station including a beam forming antenna system, each RF beam covers a sub-area of the cell coverage area of the second cellular LTE transceiver base station, with m2 x N2 in each cell. The RF beam pattern covers the area of each cell coverage area of the second cellular LTE transceiver base station. The second cellular LTE transceiver base station irradiates N2 RF beams in each cell so that none of the irradiated RF beam subareas are adjacent to each other. Whenever the first cellular LTE transceiver base station irradiates an RF beam onto a subarea of the cell coverage area adjacent to the cell coverage area of another cell of the first cellular LTE transceiver base station, these First cellular in the cell The RF beam pattern produced by the LTE transceiver base station is such that none of the subareas of the irradiated RF beam are adjacent to each other. Whenever a second cellular LTE transceiver base station irradiates an RF beam onto a subarea of the cell coverage area adjacent to the cell coverage area of another cell of that second cellular LTE transceiver base station, these The RF beam pattern produced by the second cellular LTE transceiver base station in the cell is such that none of the subareas of the irradiated RF beam are adjacent to each other and the first cellular LTE transceiver base station. However, whenever an RF beam is radiated onto a subarea of the cell coverage area adjacent to the cell coverage area of the second cellular LTE transceiver base station, the RF beam pattern generated by the second cellular LTE transceiver base station is It is as if none of the irradiated RF beam sub-areas are adjacent to the irradiated RF beam sub-area in the cell coverage area of the first cellular LTE transceiver base station.

In another aspect, the present disclosure relates to a system comprising a cellular LTE transceiver base station that has RF communication with first and second mobile transceiver devices, is connected to a backhaul network, and has an RF coverage area. The base station optimum server is connected to the backhaul network to the cellular LTE transceiver base station and in parallel with the cellular LTE transceiver base station, and (a) between the cellular LTE transceiver base station and the backhaul network, and (b) the base station. It will be possible to selectively flow data packets between the optimum server and the backhaul network, and (c) between the cellular LTE transceiver base station and the base station optimum server. The base station optimal server is communicably connected to the first and second mobile transceiver devices via an LTE bearer redirected through the cellular LTE transceiver base station to each mobile transceiver device. The system also includes Publish-Subscribe broker communication equipment to which first and second mobile transceiver devices are connected via these redirected bearers, which publish streaming application data. Adapted to route the packet stream to the first and second mobile transceiver devices on behalf of the application, both the first and second mobile transceiver devices subscribe to the application data and from the Publish-Subscribe broker communication facility. Make sure to receive at least the common part of the stream of application data.

In another aspect, the present disclosure relates to a system comprising a cellular LTE transceiver base station in RF communication with first and second mobile transceiver devices. The cellular LTE transceiver base station is connected to a backhaul network and has an RF coverage area. The base station optimum server is connected to the backhaul network to the cellular LTE transceiver base station and in parallel with the cellular LTE transceiver base station, and (a) between the cellular LTE transceiver base station and the backhaul network, and (b) the base. Allows selective flow of data packets either between the station-optimized server and the backhaul network and (c) between the cellular LTE transceiver base station and the base station-optimized server. The base station optimum server is communicably connected to the first and second mobile transceiver devices via the LTE bearer redirected through the cellular LTE transceiver base station to the first and second mobile transceiver devices. The Publish-Subscribe broker communication facility, to which the first and second mobile transceiver devices are connected through these redirected bearers, publishes the packet stream instead of the application that publishes the streaming application data. Adapted to route from to the first and second mobile transceiver devices, the first and second mobile transceiver devices subscribe to and request the application data stream at the time of the request, and the first and second at the time of the request. Different in mobile transceiver devices.

In another aspect, the present disclosure relates to a system comprising a cellular LTE transceiver base station in RF communication with a sensor device. The cellular LTE transceiver base station is connected to a backhaul network and has an RF coverage area. The base station optimum server is connected to the backhaul network to the cellular LTE transceiver base station and in parallel with the cellular LTE transceiver base station, and the sensor device is redirected to the sensor device through the cellular LTE transceiver base station via the LTE bearer. Connected to communicable. The system also includes a first Publish-Subscribe broker communication facility to which the sensor device is connected via its redirected bearer, with the first Publish-Subscribe broker communication facility transmitting data over the broker communication network. It is adapted to route application data to multiple applications that publish, and to route application data for each publishing application to all communication entities subscribed to receive the data published by that application. A regional optimal server is communicably connected to a public data network gateway (PGW) on the public data network side of the PGW and is adapted to run applications for servicing multiple mobile transceiver devices and sensors. The region-optimized server has a second broker communication facility, routes the data published by the application to the first Publish-Subscribe broker communication facility, and of multiple communication endpoints subscribed to receive the data. Adapted to route data to all other Publish-Subscribe broker communication facilities in a broker network that supports at least one of them. Sensor device is cellular LTE Deployed in the coverage area of a transceiver base station, the sensor device captures data subscribed to by an application adapted to run on at least one of the base station optimal server and the optimal server communicatively connected to the PGW. provide. One of the applications is the conferencing service, where the conferencing service and other applications are adapted to run on the Publish-Subscribe broker communication facility and application hosting the optimal server node. Publish-Subscribe Broker Collects, processes, stores, and distributes sensor data through at least one of the communication facilities.

In another aspect, the present disclosure relates to a system that supports cellular mobile transceiver device communication. The system comprises multiple cellular LTE transceiver base stations, each in RF communication with multiple mobile transceiver devices in the RF coverage area, and access priority equipment. The access priority facility determines the wireless system access priority level for each of the multiple mobile transceiver devices, and the wireless system access priority level is cellular LTE while network access is restricted at the cellular LTE transceiver base station. Mobile transceiver devices that attempt to access the base station and maintain access through the cellular LTE base station have access priority levels that exceed the values provisioned for the cellular LTE base station cells where such access is restricted. To determine whether or not to have. Available priority levels exceed the limit set specified in the LTE standard documentation, and all mobile transceiver devices with access priority levels below the provisioned threshold are on restricted cellular LTE radio base stations. Detached from the wireless network.

In another aspect, the present disclosure relates to a system for supporting cellular mobile transceiver device communication, wherein the system comprises a cellular LTE transceiver base station in RF communication with multiple mobile transceiver devices in an RF coverage area and a cellular LTE transceiver base station. It is equipped with a processor-based scheduler facility that is communicatively connected to a transceiver base station. The scheduler facility schedules mobile transceiver device access to the LTE air interface based on the data transfer rate priority value assigned to each mobile transceiver device, and the air interface access priority is a low data transfer rate priority value. An air interface that grants access to the air interface before other mobile transceiver devices with, and achieves a higher data transfer rate than is offered to other mobile transceiver devices with a lower data transfer rate priority value. Includes resource allocation. Setting the data transfer rate priority value for each mobile transceiver device that accesses the LTE network through the cellular LTE transceiver base station is based on the data transfer rate priority value database for the cellular LTE transceiver base station and the mobile transceiver device. Achieved by interaction with applications that have access to.

In another aspect, the present disclosure relates to a system for reporting cellular mobile transceiver device communications. This system includes a cellular LTE transceiver base station in RF communication state with a plurality of mobile transceiver devices in the RF coverage area, and a base station optimum server. The base station optimum server is connected to the backhaul network to the cellular LTE transceiver base station and in parallel with the cellular LTE transceiver base station. The base station optimal server is communicably connected to multiple mobile transceiver devices via an LTE bearer redirected through a cellular LTE transceiver base station to each mobile transceiver device. The system is equipped with Publish-Subscribe broker communication equipment to which multiple mobile transceiver devices are connected via these redirected bearers, and each of the multiple mobile transceiver devices in an RF coverage area with redirected bearers. It is equipped with a base station optimum server utilization rate data reporting facility for collecting service and data utilization rates. The Publish-Subscribe broker communication facility is adapted to report billing utilization data for each mobile transceiver device connected to the Publish-Subscribe broker communication facility, which allows the mobile transceiver on a route that does not include the PGW element. Utilization rate data for all data sent by the device Utilization data can be collected by the reporting facility, and such data is collected in the LTE network via a route including a redirect bearer in a cellular LTE transceiver base station. Collected.

In another aspect, the present disclosure relates to a system for performing a replacement procedure in which a base station deployed via a mobile platform is replaced by another base station deployed via a mobile platform in an ad hoc LTE system. The system is in RF communication with multiple mobile transceiver devices in the RF coverage area and is equipped with a cellular LTE transceiver base station that is ad hoc and deployed using a mobile deployment platform. Alternate cellular LTE transceiver base stations are adapted for RF communication with multiple mobile transceiver devices and are similarly deployed ad hoc using mobile deployment platforms so that they can communicate with multiple mobile transceiver devices in the RF coverage area. It is positioned in. Transceiver base station alternate computer equipment is communicably connected to backhaul networks and cellular LTE transceiver base stations, as well as alternate cellular LTE transceiver base stations, and RF coverage areas from cellular LTE transceiver base stations to alternate cellular LTE transceiver base stations. Manages the handover of multiple mobile transceiver devices in. The handover procedure is as follows: (a) the alternate cellular LTE transceiver base station is connected to the backhaul network, (b) the alternate cellular LTE transceiver base station is communicably connected to the transceiver base station alternate computer equipment, and (c) the transceiver. The base station change computer equipment is the cell identifier (Cell) Provision alternate cellular LTE transceiver base stations with the same parameters as cellular LTE transceiver base stations except Identifier), (d) cellular LTE transceiver base stations reduce their transmit power at rate Pr, alternate cellular LTE transceiver base stations However, the rate Pr increases its transmission power. The rate Pr is selected to emulate the power received by a standard mobile transceiver device in the RF coverage area from two standard fixed LTE transceiver base stations separated by a two-cell radius. The emulation is for the movement of a standard mobile transceiver device away from the cellular LTE transceiver base station and towards the alternate cellular LTE transceiver base station, with the emulated movement rate of the mobile transceiver device at 3-30 km / hr. is there. When the handover is determined by the power level and RF propagation based on a predetermined algorithm, each of the plurality of mobile transceiver devices is handed over from the cellular LTE transceiver base station to the alternate cellular LTE transceiver base station, and the plurality of mobile transceivers are transferred. When all of the devices are handed over to the alternate cellular LTE transceiver base station, the alternate cellular LTE transceiver base station is complete.

In another aspect, the present disclosure relates to a system with multiple cellular LTE transceiver base stations, each of which is in RF communication with multiple mobile transceiver devices in an RF coverage area. It is equipped with a base station optimum server and a Publish-Subscribe transceiver communication facility, and a plurality of base station optimum servers are partially connected to each other to form a distributed Publish-Subscribe broker network architecture. The system has a pair of identical service application instances, one designated as an active service instance hosted on one optimal server and one designated as a hot standby service instance hosted on a different optimal server. .. The active service instance leverages the distributed Publish-Subscribe broker network architecture to serve multiple mobile transceiver devices, and the hot standby service instance leverages the distributed Publish-Subscribe broker network architecture to enable the active service instance. The same application that the active service instance does, or the same application that multiple active service instances do, or the same application that the active service instance does by subscribing to the same communication, or each of the multiple active service instances does. Keep the same application.

These and other systems, methods, objectives, functions, and advantages of the present disclosure will become apparent from the following detailed description of embodiments and drawings preferred by those skilled in the art. All references referred to herein are incorporated herein by reference in their entirety.

Accordingly, the following detailed description of the present disclosure and specific embodiments can be understood by reference to the accompanying drawings.

<figref num="1">It is a figure which shows one embodiment of the typical deployment of an LTE network element.</figref><figref num="2">It is a figure which shows the addition of the optimum server to the LTE network.</figref><figref num="3">It is a figure which redirects a UE bearer in eNB.</figref><figref num="4">It is a figure which redirects a dedicated bearer in eNB.</figref><figref num="5">It is a high-level diagram of LTE handover processing.</figref><figref num="6">It is a figure of integration of the change of the optimum server during LTE handover processing.</figref><figref num="7">It is a figure of one embodiment of the Airborn eNB deployment.</figref><figref num="8">It is a diagram to replace Airborn eNB without losing service provision to UE.</figref><figref num="9">FIG. 5 is a diagram of an exemplary embodiment in which the cell coverage area is scanned with 16 RF beams every 4 milliseconds.</figref><figref num="10">It is a figure of one embodiment of the LTE TDD uplink / downlink configuration setting.</figref><figref num="11">FIG. 5 is a diagram of an exemplary embodiment showing a 4 millisecond beam rotation in an FDD system that supports H-ARQ operation.</figref><figref num="12">6 It is a diagram of an exemplary embodiment of distribution of a real-time event service to wireless users.</figref><figref num="13">It is a diagram of one embodiment of the publish-subscriber broker architecture.</figref><figref num="14">It is a figure which shows one example of the deployment of the P / S broker architecture in the APN optimal server architecture.</figref><figref num="15">It is a figure which shows the real-time event service using the P / S broker architecture and APN bearer redirection.</figref><figref num="16">It is a figure which shows the KeepAlive message interaction of the service instance state monitoring mode.</figref><figref num="17">It is a figure which shows the exemplary embodiment of the deployment of the streaming movie distribution service on the APN optimum server.</figref><figref num="18">FIG. 5 illustrates one exemplary embodiment of finding the closest SMD service instance and delivering movie streaming to the UE.</figref><figref num="19">It is a figure which shows the exemplary embodiment about the movie distribution streaming when the download from a centralized main memory becomes necessary.</figref><figref num="20">FIG. 5 illustrates an exemplary embodiment in which a roaming UE is detached when the cell is constrained for government use.</figref><figref num="21">It is a figure which shows the element and the interface which implements a dual use function in an LTE network.</figref><figref num="22">It is a figure which shows one embodiment of the UE application for a biopsy.</figref><figref num="23">Automatic UE Detachment from Cell with GU CB Enabled: Figure shows the initial stage of roaming user detachment.</figref><figref num="24">It is a figure which shows the exemplary embodiment which automatically detaches a low priority UE from an exclusion cell.</figref><figref num="25">FIG. 5 is a diagram of an exemplary embodiment including a biopsy when cell exclusion is first enabled.</figref><figref num="26">FIG. 5 is a diagram of an exemplary embodiment of initial attach processing when a UE accesses a cell in which a GU CB is enabled.</figref><figref num="27">It is a figure which shows one embodiment of the modification of a network trigger service request in a dual-use network.</figref><figref num="28">It is a figure which shows the exemplary embodiment of the process added to the LTE service request in a dual-use network.</figref><figref num="29">It is a figure which shows the exemplary embodiment added to the X2 handover procedure in a dual-use network.</figref><figref num="30">It is a figure which shows the exemplary embodiment added to the S1 handover procedure in a dual-use network.</figref><figref num="31">It is a figure which shows the exemplary deployment of the conference function on the optimum server in the APN LTE wireless network.</figref><figref num="32">It is a figure which shows one embodiment of ad hoc network deployment in an emergency measure scenario.</figref><figref num="33">It is a functional diagram of one embodiment of an emergency action service architecture with sensor processing.</figref><figref num="34">It is a figure which shows one embodiment of the deployment of the emergency action service architecture with sensor processing.</figref><figref num="35">It is a diagram of one embodiment in which an emergency measure multimedia conference is started.</figref><figref num="36">FIG. 5 is a diagram of one embodiment relating to participants' participation in a conference and participation in a session.</figref><figref num="37">It is a figure of collection and analysis of fixed sensor data, and alarm generation and distribution.</figref><figref num="38">It is the figure of one Embodiment which discovers an image server instance and starts and uses an image service in emergency action.</figref><figref num="39">FIG. 5 is a diagram of one embodiment that acquires a UE data transfer rate priority value and updates an eNB having this value in the case of initial access.</figref><figref num="40">FIG. 5 is a diagram of one embodiment that acquires a UE data transfer rate priority value and updates an eNB having this value in the case of a service request.</figref><figref num="41">It is a figure of one Embodiment which acquires a UE data transfer rate priority value, and updates the target eNB which has this value in the case of a handover.</figref><figref num="42">It is a figure of one Embodiment which updates a UE data transfer rate priority value when a data transfer rate priority service is enabled in a serving cell.</figref><figref num="43">FIG. 5 is a diagram of one embodiment in which the UE data transfer rate priority value is updated when the data transfer rate priority service is disabled in the serving cell.</figref><figref num="44">FIG. 5 is a diagram of one embodiment of an architecture that collects, transfers, and processes billing data that can be collected on an APN Optimal Server.</figref><figref num="45">It is a diagram of one embodiment of a message exchange that allows a program to collect and report billing data for utilization via a redirected bearer.</figref><figref num="46">It is a diagram of one embodiment of a message exchange that allows a billing data collection program to recognize when to stop its collection measures when the UE enters the ECM-IDLE state.</figref><figref num="47">It is a diagram of one embodiment of a message exchange that allows a billing data collection program to recognize when to stop its collection measures when the UE is detached from the LTE network.</figref><figref num="48">It is a figure which shows two adjacent cells and showed the concept of cell-to-cell interference by overlapping RF transmission of each cell in the coverage area of the other cell.</figref><figref num="49">Represents a hexagonal representation of a cell, the cell coverage area is divided into four sets of four subareas (ie, 16 subareas), and each subarea is generated by the cell antenna system using agile beamforming techniques. It is a figure covered by the RF beam.</figref><figref num="50">We show three cells of an exemplary base station system using agile beamforming and how the RF beam rotation pattern in each cell can be configured to avoid cell-to-cell interference at the boundaries of any cell. It is a figure shown.</figref><figref num="51">It shows all the cells which can be adjacent to a given cell and shows how the RF beam rotation pattern in each cell can be constructed to avoid cell-to-cell interference at the boundary of any cell.</figref><figref num="52">Shows all cells in four base station systems with agile beamforming and shows how the RF beam rotation pattern in each cell can be configured to avoid cell-to-cell interference at the boundaries of any cell. This is a diagram clarified that cell-to-cell interference avoidance can be extended to all cells in a wireless network.</figref><figref num="53">Shows the baseband subsystem and RF and antenna subsystems of LTE radiobase stations that generate periodically scanned RF beams, interfaces between the two subsystems, MAC layer software and PHY layers that perform baseband signal processing. It is the figure which highlighted the software.</figref>

Although methods and systems have been described with certain preferred embodiments, those skilled in the art will understand and embrace other embodiments herein.

The following is a description of this disclosure and describes the methods and processes of manufacture and use in terms that are clear, concise and accurate enough to be manufactured and used by those skilled in the art related to or closest to this disclosure. It also describes the best embodiments intended by the inventors with respect to carrying out the present disclosure.

The present disclosure relates to broadband wireless networks, and more specifically, as an alternative, in the present disclosure, "general purpose networks (All Purpose)". With respect to multipurpose networks called "Network" or "APN" multipurpose networks, this can implement large-scale (eg, national) broadband wireless networks that provide extremely large wireless data communication capacities, all of the challenges mentioned above. Can be solved. APN can combine proven, state-of-the-art commercial radio design and architectural techniques with advanced RF technology to substantially improve spectral efficiency, spectral utilization, and data performance. Intrinsic beamforming techniques can be used to improve spectral efficiency and spectral utilization, and some of the methods and systems disclosed herein as part of the APN network are RF in a manner appropriate for LTE networks. Includes adjusting the periodicity of the beam. Efficient algorithms for locating and tracking users within the beam can also be part of this disclosure. In addition, it should be noted that the interference provided to the user in one cell by the transmission occurring in the adjacent cell usually reduces the quality of service provided to the user located near the boundary between the two adjacent cells. .. Part of this disclosure describes how to use an Agile Beam Forming system in each of the cells of an APN network, without the use of special communication between cells and cell coverage. Interference between cells can be substantially reduced without reducing the bandwidth available to the user located in any part of the area. The challenges associated with service delays, backhaul utilization, and servers and longhaul networks are addressed by deploying servers as close as possible to wireless users, ie, eNB (E-UTRAN Node B or Evolved Node). B) By deploying in association with network elements, for example, by providing the server with a high-speed connection to the eNB, positioning the server close to the eNB, placing the server and the eNB in the same location, and so on. , Can be solved in the APN network. Such deployments may require the integration of servers into LTE wireless network operations in a unique manner disclosed herein. When users are allowed access to the servers associated with the eNB, these bearer packets no longer pass through the Serving Gateway (SGW) and Public Data Network (PDN) Gateway (PGW) elements. Therefore, part of this disclosure shows how to maintain a billing data set in these cases. These servers can also form the basis of a platform for collecting, processing, storing, and redistributing sensor data as disclosed herein when integrated into an APN wireless network. Further, as disclosed herein, the introduction of Publish / Subscribe data communication into an APN network allows the APN network to be implemented as a dual-use network, in the event of a disaster or other emergency. Only government users can be allowed access to parts of the network. The disclosure may also relate to the use of the APN Network's Publish / Subscribe communication infrastructure to implement Hot-Standby services, where hot standby improves network operations and user experience. Can play an important role in improvement. The disclosure also addresses challenges regarding how to replace Airborn or other mobile eNB-based stations while the mobile-based station is in operation. It does not pass through the SGW) and Public Data Network (PDN) Gateway (PGW) elements, and thus part of this disclosure shows how to maintain a billing data set in these cases. These servers can also form the basis of a platform for collecting, processing, storing, and redistributing sensor data as disclosed herein when integrated into an APN wireless network. Further, as disclosed herein, the introduction of Publish / Subscribe data communication into an APN network allows the APN network to be implemented as a dual-use network, in the event of a disaster or other emergency. Only government users can be allowed access to parts of the network. The disclosure may also relate to the use of the APN Network's Publish / Subscribe communication infrastructure to implement Hot-Standby services, where hot standby improves network operations and user experience. Can play an important role in improvement. The disclosure also addresses challenges regarding how to replace Airborn or other mobile eNB-based stations while the mobile-based station is in operation.

(Integration of optimal server function into LTE wireless network) FIG. 1 illustrates one embodiment of the deployment of network elements capable of providing LTE wireless services to users and user equipment (UEs). The eNB102 element can be deployed in a local area where RF waves can reach UE104. Mobility Management Entity (MME) 108 and Serving Gateway (SGW) 110 elements can be deployed in regional locations to handle many (eg, hundreds) eNB 102 elements. The MME108 is connected to the eNB102 element via the LTE backhaul network 112 to manage UE104 access to the LTE network, and the UE104 also hands the wireless network from one eNB cell (antenna) to another. It can handle the mobility of UE104 when it goes over. The SGW110 is connected to the eNB102 element via the LTE backhaul network 112 and can provide a semi-static connection point for routing packets between the UE 104 and the target server 124 computer. The SGW110 can be changed during the UE handover procedure, but in many cases the SGW110 can remain fixed during the handover operation. The SGW110 maintains a bearer (using a generic packet radio service tunneling protocol, also known as a generic tunneling protocol or GTP tunnel) for the UE104 even when the UE104 is idle and not actively connected to the network. Can be done. PDN gateways (PGWs) 114 are typically deployed in centrally located data centers and interface with many (eg, hundreds) SGW110 elements. The PGW 114 can configure a connection point between the UE 104 and a particular packet data network 122 (eg, the Internet) and is immutable with multiple handover procedures as the UE 104 travels around the LTE network. To be it can. The home subscriber server (HSS) 120 can provide a database of user subscription data. The Policy Billing Rule Function (PCRF) 118 can control the permissible connection pattern of each UE 104. Thus, LTE radio network boundaries can include UE104, eNB102, MME108 and SGW110, as well as PGW114, HSS120 and PCRF118. The PGW 114 can interface to a particular packet data network 122, one embodiment of which is the Internet.

A user typically calls a service program on UE104 to connect to, for example, a computer (server 124) that needs to be accessed over the Internet. Packets are routed from UE104 through the LTE air interface to eNB102, where they are placed in a specific GTP tunnel (called bearer-302), sent to SGW110, then to PGW114, and then to Internet 122 (or Internet 122). It can be sent to the destination server 124 via another packet data network). The packet is then sent from server 124 over the Internet 122 (or other packet data network) to PGW114, then through a specific LTE tunnel (called bearer-302) to SGW110, eNB102, and finally. Can be sent to the UE 104 via the LTE air interface.

Importantly, it should be noted that in FIG. 1, the server 124 computer servicing a wireless user is usually remote from that user and his UE 104. Thus, packets can be delayed as they pass through the Internet 122, PGW114 and SGW110 network elements, the LTE backhaul network 112, and the eNB102 element and the LTE air interface. Congestion at these points in the packet traversal path impairs the user experience. In addition, the server computer 124 servicing the wireless user can be completely independent of the LTE network and the real-time state of the wireless network (eg, air interface utilization, backhaul utilization in a given eNB 102, or PGW 114. And no data on SGW110 element (congestion) can be collected. Therefore, the current server computer 124 cannot change its behavior in response to the real-time state of the LTE wireless network and is therefore presented by the server computer when using the LTE wireless network and utilizing the real-time network data. The user experience when using the service cannot be improved.

The present disclosure is a collection of server computers 202, 204 (a collection of server computers) that are integrated into a wireless network at one or more points and are referred to herein as opt servers (OptServers) or preferred optimal processors (POPs) as alternatives. It describes a method to solve the problems pointed out above through (can). The optimal server can be designed as a platform for running programs servicing the UE 104, and thus in this regard the server computer 124 currently connected to the wireless UE via the Internet or another packet data network. Is equivalent to.

Aspects of "integration" can include management through a network management system that manages wireless network elements (eg, LTE wireless network elements shown in FIG. 1), and for the purpose of extracting real-time network data. And having an interface to the wireless network element for the purpose of controlling the wireless network element in servicing the wireless user. In addition, real-time network data can be used to change the behavior of service programs executed on optimal servers 202, 204, where changes in behavior improve the user experience. As an example, a service program that delivers streaming video to a user can use different bidet encoding rates based on real-time awareness of the capabilities of the air interface to provide the UE 104 with a particular data transfer rate. Further, by arranging the optimum servers 202 and 204 in the wireless network, the packet transmission delay experienced by the user can be reduced. As shown below, the interface of the optimal servers 202, 204 to the wireless network element can be used to minimize the delay in packet switching between the server program and the UE 104.

One embodiment of the deployment point for the optimal server in the LTE wireless network is shown in Figure 2. One deployment point is to provide the optimal server with a high-speed connection to the PGW, to position the optimal server close to the PGW, to locate the optimal server in the same location as the PGW, and so on, thereby making the optimal server 202 PGW114. Illustrated to associate with the element. In this way, the optimal server 202 is located at the end of the LTE wireless network, thus avoiding packet transmission delays that would otherwise occur when traversing a packet data network such as the Internet. Services such as streaming video or real-time video can be successfully provided to many simultaneous users in the area of LTE wireless networks by this technique. In addition, packet delays can be further reduced if the PGW 114 (and Optimal Server 202) is deployed locally rather than centrally in the country. This deployment configuration is shown in Figure 2. It should also be noted that by servicing through the optimal server 202 associated with the PGW 114, it may still be necessary for the packet to pass through the LTE backhaul network 112 and reach the wireless UE 104. Next to the air interface, the backhaul network 12 is an important resource whose utilization must be reduced. This is illustrated by having a large number of users accessing through the same eNB 102 and watching all real-time video events. If all streaming video packets pass through the backhaul network, other users accessing through the eNB 102 may not have sufficient bandwidth available.

The need to reduce the use of the backhaul 112 is to provide the optimal server with a high-speed connection to the eNB, to position the optimal server close to the eNB, to place the optimal server and the eNB in the same position, and similar. It may result in an association of optimal server 204 with the eNB element. If the service to the UE 104 (eg, streaming of real-time video events) can be provided through the optimal server 204 associated with the eNB 102 servicing the UE 104, backhaul in providing the service to the UE 104. The utilization rate of network 112 can be minimized. Also, the delay caused by the packets exchanged between the service access point (ie, the optimal server 204) and the UE 104 is minimized due to these packets passing only through the eNB 102 and LTE air interfaces. can do.

As an example, consider the task of providing video in a real-time event to 200 users connected through the same eNB 102. If the best server 204 is not associated with the eNB 102, the service access point is across the wireless network and a single video packet stream for each UE 104 has a PGW 114, SGW 110, backhaul network 112, eNB 102, and LTE air interface. pass. The simultaneous viewing of this service through the same eNB 102 by 200 UE 104s means that 200 times the base video rate could be used on the backhaul network 112. Now consider the situation where the optimal server 204 is associated with the serving eNB 102. Further assume that the optimal servers 204 and UE 104 implement the Publish / Subscribe communication paradigm described herein, and thus all 200 UEs are subscribed to receive the same real-time video transmission. The video data stream is sent from the origin of the Internet through the LTE network to the optimal server 204 associated with the serving eNB 102 via the backhaul 112. The Publish / Subscribe software on the optimal server 204 then delivers a video packet stream to each of the 200 UE 104s that were subscribed to the service via the optimal server 204.

There is no clear way to connect the UE to the best server associated with the eNB due to the way the bearer 302 (ie GTP tunnel) is configured in the LTE network to propagate packets to and from the UE. There is. Part of this disclosure shows how this connectivity can be established. Furthermore, when service is provided by server 124 attached to the Internet or by optimal server 202 associated with PGW, the UE moves through the LTE wireless network and continues uninterrupted from the same service access point. The service can be provided, and a handover state is established between the eNB 102 elements of the LTE network. However, when the service access point is the optimal server 204 associated with the eNB 102, it may be necessary to change the access point when the UE 104 is handed over to another eNB 102. Part of this disclosure describes how service access points can be quickly switched between optimal servers 204 associated with the eNB 102 element. If the service access point switchover is performed quickly enough, the user will not experience any interruption in the service being provided. Before switching service access points, it may be necessary to connect UE104 to the optimal server 204 associated with the eNB102 element.

Figure 3 shows that in an LTE network, different bearers 302 can be configured for each UE 104 to connect the UE 104 with the PGW 114 element. The PGW114 element can provide an interface with a packet data network (eg, the Internet 122), where a user service computer is typically located. In an embodiment, each bearer 302 is a tunnel that encapsulates a packet with a simple GTP (general purpose tunneling protocol) header, and the packet is routed through this tunnel. Packet routing to the tunnel uses the IP address of the packet and the number of ports as the "Traffic Flow template" attached to the bearer 302. It can be achieved with UE104 and PGW114 by associating with the Internet Protocol (IP) address and number of ports of "Template)". Each bearer 302 configured on the UE 104 has a different quality of service (QoS) associated with it. Up to 15 bearers 302 can be configured for a single UE 104. The first bearer 302 set on a given PGW 114 is called the default bearer 302. Any additional bearer 302 set in the PGW 114 is referred to as a dedicated bearer 302.

FIG. 3 shows one embodiment in which one dedicated bearer 302 is "redirected" to the optimal server 204 associated with the eNB 102 servicing the UE 104. In this case, the optimal server 204 associated with the eNB 102 is represented by OptServer eNB308, while the optimal server 202 associated with PGW 114 is represented by OptServer PGW 304. Application 310 on the UE 104 can communicate with the OptServer PGW 304 by sending the packet through the default bearer 302, which propagates the packet to the PGW 114 associated with the OptServer PGW 304. Packets can be sent from the OptServer PGW 304 to the UE 104 by passing through the same default bearer 302. After the redirection of the dedicated bearer 302 is achieved, the application 310 on the UE 104 can communicate with the OptServere NB308 by sending a packet through the redirected dedicated bearer 302. Packets can be sent from the OptServere NB308 to the UE by passing through the same redirected dedicated bearer 312, eliminating the need to utilize a backhaul for packet switching via the redirected bearer 312.

Redirection of the bearer 302 should be achieved through OAM-type interfaces (Operations, Administration, and Maintenance interfaces) to the eNB 102, rather than standard operation. Also note in Figure 3 that after the dedicated bearer 312 was redirected on the eNB 102, the tunnel information in which the bearer was pre-linked to the SGW 110 is still maintained on the eNB 102. This is required to allow the handover to be performed without changing to the existing handover procedure and to allow rapid redirection of the same dedicated bearer 312 on the target eNB during the handover. be able to. The dedicated bearer 302 does not need to be reconfigured after the handover, as it does not have to be excluded from the bearer 302's eNB102 list that was configured when the bearer was redirected to the OptServer eNB308.

In the architecture shown in FIGS. 2 and 3, the OptServer PGW304 can be used as a control point for redirecting the bearer 312 with the eNB102 element for any UE104. Figure 4 shows a series of message interactions that can be used to perform redirection. When UE104 accesses the LTE network, the default bearer 302 can be set to PGW114 associated with OptServer PGW304. UE104 can perform Domain Name System (DNS) queries to find the IP address of the OptServer PGW304. UE104 uses the default bearer 302 to connect to the radio control process 3902 on the OptServer PGW304 and subscribe to the program. The subscription information is the Cell of the LTE cell that the UE is currently accessing the network. ID, IMSI (International Mobile Phone) used to identify UE104 in all LTE networks except eNB102, Cell Radio Network Temporary Identifier (C-RNTI), which is a parameter used in eNB102 to identify UE104. It can include a subscriber identification number) and a GUTI (terminal unique temporary identifier) used to identify the MME108 element currently serving UE102. Other parameters can be sent by the UE 104 to the radio control process 3902 via register messages (eg, the IP address of the UE) to allow implementation of other services, as discussed herein. ..

When UE104 is subscribed to a program on OptServer PGW304, it can receive an acknowledgment, which can include a command to set a dedicated bearer linked to the default bearer currently in use. As an alternative, LTE network provisioning with PCRF (Policy Billing Rule Function) can initiate settings such as a dedicated bearer for UE104. The UE 104 can set up a dedicated bearer 302 using standard LTE procedures, and once this is done, the UE 104 will have an IMSI (to identify the UE 104 to the radio control program 3902) and the bearer ID of the bearer 302 just set up. Send a response containing to OptServer PGW304. Since the radio control process 3902 can have a cell ID for the UE 104, it can determine the ID of the eNB 102 currently serving the UE 104. For example, the provisioned OAM of the eNB102 element Using the IP address, the radio control process 3902 can send a message to the serving eNB 102 and command the bearer 302 to redirect. The C-RNTI can identify the UE104 context for the eNB104 and the bearer ID can identify the UE bearer 302 to redirect. The server IP address represents the eNB 104 for which the OptServer eNB 308 is the target of redirection (so more than one optimal server 308 can be associated with the eNB 102). Once the eNB 102 completes the redirection operation, it can reply to the radio control process 3902. The radio control process 3902 then sends the packet through the default bearer 302 to the UE 104, notifying that it can be started with the dedicated bearer 312 redirected to start the service using the OptServere NB308 as a service access point. can do. By sending a packet through the redirected dedicated bearer 312, the UE 104 can initiate any of a plurality of services. The use of backhaul 112 can be minimized for all of these services, and thus packet delays can be minimized as well.

(Transfer of service provision between eNB-based optimal servers during handover) In FIG. 2, as an example, it is assumed that the UE 104 receives a service from the OptServer eNB 308 associated with the serving eNB 102. When the UE 104 moves, it goes into a handover state for another eNB 102 and the service access point must change to the OptServer eNB 308 associated with the new target eNB 102 element. In this case, service interruptions are unavoidable and therefore need to be as short as possible. To minimize service interruptions, additional message interactions that make service access point changes can be embedded in the standard handover process used in LTE networks. Therefore, the standard handover process will be schematically described here.

The standard handover process can be divided into three stages such as handover preparation, handover execution, and handover completion. See Figure 5. The eNB 102 currently serving is called the source eNB. The new eNB 102 is called the target eNB. In the handover preparation stage, the source eNB 102 receives a signal measurement from the UE 104 and determines that an antenna at another eNB 102 is providing a stronger signal to the UE 104 and should perform the handover. The source eNB 102 transfers to the target eNB 102 contextual information about the UE, including an ID and tunnel parameters for each actual bearer to the UE. The tunnel information for the redirected bearer 312 can be included in the set of bearer information, but the information is for the tunnel endpoint in the SGW 110, not in the OptServer eNB 308 associated with the source eNB 102. In this way, the standard handover process can be unaffected by the inclusion of the OptServer eNB 102 and the redirected bearer 312. The parameters associated with redirecting the bearer 312 are not transferred in the handover process. On the other hand, the target eNB 102 can transmit the C-RNTI value for the UE 104 to the source eNB 102 for use with the target eNB 102. When the handover preparation phase is complete, the source eNB102 sends a handover command message to UE104 to include the new C-RNTI value. Any downlink data received by the source eNB 102 for the UE 104 may not be transmitted wirelessly to the UE 104, but will be forwarded to the target eNB 102, where it will be queued until the UE 104 connects to the target eNB 104. Be done. SGW110 is still unaware of the handover

When the UE 104 receives the handover command, the handover execution stage can be started. The UE 104 synchronizes with the signal transmitted by the target eNB 102, and when the synchronization occurs, the UE 104 accesses the target eNB 102 cell with the new C-RNTI value and then issues a Handover Confirm message. Send to target eNB102. The target eNB 102 begins transmitting the queued transfer data to the UE 104 via the air interface. Since the tunnel information about the UE bearer 302 is available at the target eNB 102 from the handover preparation stage, the UE 102 can start transmitting the uplink packet through the target eNB 102. Since the redirection has not yet occurred on the target eNB 102, the bearer 302 uplink packets that need to be redirected are not sent at the same time.

At the handover completion stage, the SGW 110 can include the tunnel parameters of the bearer 302 used in the target eNB 102, where downlink data can be transferred to the target eNB 102. The context information of UE104 can be deleted by the source eNB102, and the handover process is completed. See Figure 5.

Figure 6 shows the interaction between the UE 104 and the optimal servers 202, 204, where these servers are integrated into the LTE handover procedure and the service delivery point is from the optimal server 308 located at the source eNB 102. Effectively relocate to the optimal server 308 located on the target eNB 102. The UE104 client can play a role in ensuring no data loss in the relocation of optimal server 308, as shown in Figure 6. The OptServerPGW304 is responsible for sending a command to the target eNB 102 to redirect the bearer 312, which was previously redirected on the source eNB 102, here on the target eNB 102. Using a small number of messages (for example, five) to make a service access point change means that this change can be completed quickly. In this case, the message can include disconnection from OptServer eNB308 at source eNB 102, Handover (), RedirectBearer (), RedirectBearerDone (), ResumeSession (), and the like. See Figure 6.

In FIG. 6, the UE104 client can be notified by the LTE software running on the UE104 that it has received the handover command message. Before allowing the UE LTE software to advance in sync with the target cell, the UE104 client can send a packet through the redirected dedicated bearer 312 and disconnect from the OptServer eNB308 associated with the source eNB 102. When this is complete, the UE104 client will be UE LTE software can be started. When the UE 104 sends a handover confirmation message to the target eNB 102, it can provide another notification to the UE 104. The client then sends a Handover () message to the radio control process 3902 running on the OptServer PGW304 to redirect the new cell ID, new C-RNTI, IMSI, and GUTI (which may have changed). In addition to the bearer ID of the dedicated bearer 312 that needs to be provided, other parameters that may be needed to provide additional services (eg, the IP address of the UE 104) can be notified. The radio control process 3902 derives a new eNB ID from the new cell_ID and eNB OAM from the provisioned data or other data. You can get an IP address. Target eNB102 receives a command to redirect UE104 bearer 312 and replies when this is complete. At this point, the radio control process 3902 can send a resume session () message to UE104 via the default bearer 302, and the UE104 client sends a packet to OptServer eNB308 on target eNB 102 via the redirected dedicated bearer 312. , The session that was interrupted at the source eNB102 position can be continued.

(Replacement of airbone eNB using LTE handover mechanism) Seeing Figure 1 again, in an emergency, the wireless infrastructure may be destroyed or not in operation, resulting in the need to deploy a temporary network in an ad hoc manner. .. One way to carry out the deployment is to place the eNB102 network element on an airborne mobile and overlay it on an area where LTE radio service is required, as shown in cell coverage area 712. .. The airbone mobile can be manned or unmanned. In the latter case, the aircraft can be referred to as an unmanned aircraft (UAV708). Extended Packet Core (EPC) 710 network elements include MME108, SGW110, PGW114, HSS120, PCRF118, and the like, as well as router 702, which can provide communication interconnectivity between network elements. .. The MME108, SGW110, and PGW114 network elements can be deployed on a second airbone mobile 710 that can be located remote from the operating area of the eNB 102. The MME108 and PGW114 network elements can communicate with the HSS120 and PCRF118 network elements via the Long Haul Network connection 704 and the Longhaul network 804. The eNB-based mobile 708 and the EPC-based mobile 710 can communicate via the wireless backhaul interface 112. All LTE network elements can communicate with the element management system (EMS) 802 using the long-hole network 804. This configuration is shown in Figure 7. The alternative deployment of the EPC710 element is at the ground node. In this case, the aerial eNB 102 mobile 708 communicates via a wireless link 112 to a ground station that provides connectivity to the EPC710 element and EMS802.

Other deployment configurations are feasible, but it may be best to deploy the eNB102 element alone without adding other LTE network elements to the aerial mobile 708 holding the eNB102. This deployment can be particularly useful when an unmanned aerial vehicle (UAV) is used. Weight and output limits can be important in these deployments, and by holding only the eNB102 and not any of the other LTE network elements, the UAV708 holding the eNB102 will have the least payload weight and output loss. Can be ensured to be held at.

(Replacement of eNB UAV in the operation area) In some remote deployment situations, especially if the platform containing the LTE network is a UAV, there will come a time when it will be necessary to replace the UAV. The reason is that the battery that powers the LTE device is low, the UAV is out of fuel, or the LTE device that needs to be removed and serviced in some circumstances is the UAV. Can be held by. In either case, it may be possible to switch UAV platforms between UAVs while in the field. The following algorithm shows how the eNB UAV708 can be replaced while it is up and running across the production area. The algorithm that achieves this shift will provide the continuous service provided to the UE 104 in the operational area of the eNB 102.

Figure 8 depicts the situation where the eNB1 UAV708 is being replaced by another eNB2 UAV708 that has reached the operational area. One embodiment of the alternation procedure is as follows. 1. Alternate UAV708 hosting eNB2 102 reaches the site of UAV708 hosting eNB1 102. The eNB2 102 establishes wireless communication with the UAV710 backhaul antenna / radio that hosts the EPC710 element. 2. The eNB2 102 establishes communication with the remote element management system (EMS802) via the router 702 included in the EPC UAV710 equipment. 3. EMS802 provisions eNB2 102 with the same parameters that eNB1 102 has, except that the cell IDs are different. 4. EMS802 starts the alternation procedure at eNB1 102, commands eNB1 102 to reduce transmit power at rate Pr, and at the same time turns on the transmitter and tells eNB2 102 to increase transmit power at rate Pr. Command. Rate Pr, the movement of UE104 is from eNB1 102 to eNB2 When moving towards 102, you should choose to emulate the power received by UE104 from two fixed antennas, which are usually separated by two cell radii in the deployed commercial LTE system, and emulate UE104. The rate movement speed is 3 to 30 km / hr. 5. All user equipment (mobile phones,) in RF area 712 covered by eNB1 102 (and now covered by eNB2 102) at a point determined by rate Pr and RF propagation characteristics on the operational area. Digital elements, sensors, etc.) determine that the cell at eNB 2 102 has a sufficiently strong signal compared to the cell at eNB 1 102 where the cell at eNB 2 102 should be handed over. Here, all UE 104s in the RF coverage area 712 perform a handover from eNB1 102 to eNB2 102. 6. When all UE 104 have moved from eNB 1 102, eNB 1 102 will send a "replacement complete" indication to EMS802, where eNB1 102 is commanded to reduce the transmit power to zero. The eNB1 102 can leave the operational area. The eNB replacement was completed without loss of service to UEs in the operational area.

(Beamforming LTE radio system with periodic scan of agile beam pattern allowed beam periodicity) In embodiments, the present disclosure can provide RF beamforming techniques in LTE radio systems. A particular beamforming technique can simultaneously generate "N" RF beams, such as at 1 msec intervals for each LTE frame 1002, where the LTE frame 1002 can have a duration of 10 msec. N RF beams 902 can cover N sub-areas of the total coverage area 712 of the LTE cell, with coverage area 712 using the same total transmit power used in beamforming resolution techniques. It is determined by the LTE cell, but it is not necessary to use beamforming technology. At the next interval, another RF beam 902 is generated, which can cover different sets of N subareas 902. This process can be repeated until the entire cell coverage area is scanned by RF beam pattern 902. The RF beam pattern 902 is periodically repeated by this scanning method.

The present disclosure can provide information related to constraints on scan periodicity that must follow RF beam pattern 902. For example, in a frequency division duplex (FDD) system, but not limited to, the periodicity of the RF beam pattern 902 can be required to be 4 msec. In Time Division Duplex (TDD) systems, the periodicity can generally be 10 msec (ie, 1 LTE frame 1002), but the TDD uplink / downlink (U / D) configuration 1002 used in LTE systems. Depending on the situation, the interval may be shorter. The data presented herein are the results of analysis by the methods and systems of the present disclosure. Some specific constraints are given below.

Beamforming technology has been used for many years in the areas of audio signal processing, sonar signal processing, and radio signal processing. In many embodiments, techniques are used to locate the signal source (because it is received by the antenna array) and concentrate the antenna array at that point. In the beamforming technology according to the present disclosure in LTE radio systems, beamforming operates differently, and in LTE, data transmission to and from UE104 is scheduled by software at LTE base station 102. We are using. This beamforming technique focuses a set of RF beams on a specific non-overlapping sub-area of cell coverage area 712 at short fixed time intervals and then at the same short fixed time interval a specific non-overlapping sub area of cell coverage area 712. Move to another set of areas. The beam pattern can be moved in this way until the entire cell coverage area 712 has been scanned for transmission from the antenna array and reception by the antenna array. The coverage beam pattern is then periodically repeated. See FIG. 9 for an example of a beam scan pattern consisting of four RF beams 902 generated in each of four consecutive 1 msec subframes of an LTE frame and repeated every 4 msec. At the first 1 msec interval, RF beams 902 numbered 1, 11, 9, and 14 can occur, which constitute a non-adjacent set of RF beams 902. At the second 1 msec interval, RF beams 902 numbered 3, 6, 7, and 13 can be generated. At the third 1 msec interval, RF beams 902 numbered 4, 8, 10, and 16 can be generated. At the fourth 1 msec interval, RF beams 902 numbered 2, 5, 12, and 15 can be generated. At the fifth 1 msec interval, the pattern is repeated. Agile beamforming

The present disclosure can include constraints on the reception rate of beam pattern 902 and on the subframe set of frame 1002 where the RF beam pattern 902 is required to be identical in the TDD system. ..

LTE is an OFDM (Orthogonal Frequency Division Multiplexing) system. The transmission interval is systematized into a set of subframes, and a set of 10 subframes constitutes LTE frame 1002. Each subframe has a duration of 1 msec and each of these is further decomposed into two slots each having a duration of 0.5 msec. In LTE FDD systems, different frequency bands are used for uplink and downlink transmission. Thus, the UE 104 can be scheduled to receive downlink transmissions in any subframe and / or schedule for uplink transmissions. In LTE TDD systems, the same frequency band is used to send uplink and downlink transmissions. To systematize these transmissions, each subframe within a set of 10 subframes in each LTE frame 1002 can be configured for uplink or downlink transmission. As shown in Figure 10, there are seven different TDD U / D configuration settings 1002 with LTE operating specifications. Specific LTE The eNB 102 can be configured to use one of these configuration settings 1002. The subframes represented by "S" in FIG. 10 are used to transmit the uplink pilot signal and the downlink pilot signal. Subframe S is not used to determine the constraints imposed on RF beamforming techniques.

(Hybrid automatic repeat request (H-ARQ) processing) Transmission over the air interface is error prone due to interference and fading. Each transmission in the uplink and downlink directions must be acknowledged by the other party. This is done by sending a hybrid automatic repeat request (H-ARQ) acknowledgment or negative response to the control channel. H-ARQ is an effective technique for improving the performance of LTE systems, which is superior to the performance of other wireless systems, and must be retained when using beamforming technology.

In the downlink direction, the H-ARQ ACK / NAK is for uplink transmission and is sent over the physical H-ARQ indicator channel (PHICH), which is part of the PDCCH (Physical Downlink Control Channel), ie , PHICH is transmitted in the first 1-3 symbols of each subframe. In the uplink direction, the H-ARQ ACK / NAK (acknowledged or negative response character) is sent over the physical uplink control channel (PUCCH), which is implicitly scheduled immediately after the downlink transmission. To.

When a downlink transmission is "negatively replied" (ie, receives a negative response character) and needs to be retransmitted, the media access control (MAC) layer on the eNB102 element needs to schedule the retransmission. be able to. When beamforming techniques are used, the MAC is required to schedule retransmissions in the subframe where the RF beam 902 covering the current UE104 position is formed, and the data covers the RF beam. It can be sent to UE 104 via 902. Since all user plane data must be sent to UE 104 in the subframe where the RF beam 902 covering the UE 104 position is formed, the statement for downlink transmission is that the first transmission of user plane data is beamforming technology. It may be necessary to handle the retransmission data in the same way as it is processed in. These statements apply equally to FDD and TDD systems. Maintaining retransmission efficiency in the downlink direction is not a problem when using beamforming techniques.

Uplink retransmissions are not explicitly scheduled and can be implicitly scheduled. For example, UE104 assumes that the eNB102 beamforming receiver forms an uplink transmission in the subframe that focuses at the UE104 position. In an FDD system, if the UE 104 receives a NAK for any transmission over the downlink PHICH, the NAK shall be required to send four subframes after the subframe containing the harmful UE104 transmission. Can be done. UE104 uses implicit scheduling to resend information to four subframes after receiving a NAK. Therefore, in the FDD system, the cell subarea<u style="single">902</u>The RF beam 902 mosquitoes when time period barrage is different from 4msec the retransmission of UE104 is, UE by the RF beam 902<u style="single">902</u>This means that the position can occur in unilluminated subframes. As mentioned above, interpret the ACK or NAK received on PHICH in subframe n as applied to UE104 in subframe (n-4). See TS 36.213 va40 8.3. On the other hand, UE104 implicitly reschedules its retransmission in subframe (n + 4). See TS 36.213 va40 8.0. Therefore, unless the rotation of the RF beam 902 through the cell coverage area 712 is 4 msec (4 subframes) in the FDD system, uplink retransmission is unsuccessful (eNB102 looks for a receive beam for user plane transmission of UE104). The beam position 902 of the subframe, which does not cause retransmission in a rotation state other than 4 msec, does not cover the UE104 position). See FIG. 11 for an example of an LTE FDD system using a 5 msec beam 902 rotation period and a 4 msec beam 902 rotation period.

(H-ARQ processing for uplink retransmission in TDD system) The situation in the TDD system can be more complicated, which is This is due to the fact that the relationship of the subframe that received the NAK to the reference subframe of the original transmission is different in various TDD U / D configuration settings 1002. The same applies to the relationship between the NAK subframes received by UE104 for the subframes that schedule retransmissions. Table 8.3-1 of TS 36.213 a40 is duplicated below to obtain these relationships. If a NAK is received in subframe n, it implicitly indicates that this is a transmission sent by UE104 in subframe (nk), where the value k is the various TDD U / D. It is shown below in configuration setting 1002.

Table 1: NAK subframe relationships received in the original transmission in the TDD system<img id="000002" he="67" wi="145" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

NAK transmissions from the eNB 102 can only come in at specific downlink subframes, but not necessarily four subframes apart, as in FDD systems.

Another way to look up the information is to look at the subframe in which the original UE104 transmission was formed and use this value to determine when the NAK for that transmission was sent by the eNB 102. This study is presented in Table 2 below, where the notation h} means that the NAK was received in the subframe h of the subsequent LTE frame. The TDD configuration settings show the uplink / downlink (or S) behavior of the system at each subframe, as shown in Figure 10 and Table 4.2-1 of TS 36.211 a40.

Table 2: Original UE transmission subframe and subframe received NAK in TDD system<img id="000003" he="104" wi="145" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Now that it is clear in which subframe the NAK was sent in the UE104 transmission, the next thing to understand is the subframe in which the UE104 can retransmit that information. The offset from the subframe in which the NAK was received can also depend on the TDD configuration setting 1002, and the subframe in which the NAK was received. If the NAK is received in subframe n, UE104 schedules its retransmission in subframe (n + k), where k is given in the table below (table for TS 36.213 a40 in normal HARQ operation). According to 8-2).

Table 3: k value of UE retransmission in subframe (n + k) when NAK is received in subframe n<img id="000004" he="88" wi="137" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Tables 1, 2, and 3 show a set of constraints on where the RF beam 902 should be to maintain HARQ functionality in TDD systems that use beamforming techniques. For example, if the RF beam 902 is focused at a position in subframe n when the UE 104 transmits information, the same pattern of RF beam 902 will actually appear in the subframe when the UE resends that data. Must be present in. For example, Table 2 shows that in TDD configuration setting 0, when UE104 transmits information in subframe 3, the NAK of the transmission comes in 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 the NAK is received). This relationship means that the RF beam pattern 902 in subframe 3 (where the original transmission was made) and the RF beam pattern 902 in subframe 4 (the subframe where the retransmission occurred) must be the same. There is. All of the constraints implied by these H-ARQ tables are how many separate sets of RF beam patterns 902 can be in a TDD system with a particular U / D configuration setting, and thus how in RF beam pattern 902. Determine if the repeat rate needs to be high. The result is not as simple as an FDD system, with four RF beam patterns repeating every four subframes.

Before analyzing Tables 1, 2, and 3 for all HARQ constraints on beam patterns, another aspect of the system is in subframes where the number of sets of beam patterns 902 and the RF beam patterns need to be the same. It is necessary to analyze the additional constraints imposed on it. Additional constraints can be imposed by channel quality index (CQI) measurements, which are due to the ability to use these measurements to position the UE 104 at different RF beam positions 902. Descriptions of UE104 positioning and tracking in the RF beam 902 of a periodic scan RF beam system, as described herein, include CQI measurements and these CQI measurements in LTE systems that utilize this beamforming technology. Clarify how to use.

(Channel Quality Index (CQI)) To allow downlink transmission to be optimized by adapting Modulation Coding Method (MCS), the mobile device 104 is channeled over PUCCH (Physical Uplink Control Channel) or PUSCH (Physical Uplink Shared Channel). You may need to submit a quality indicator (CQI). CQI is the result of 4 bits representing the measured value. The measurements can span the entire frequency range of the cell bandwidth, or can span a subset of that frequency range. The entire frequency range can be divided into sets of physical resource blocks, and these sets are defined as "sub-bands" for the purpose of making CQI measurements over a frequency range smaller than the total RF bandwidth allocated to the cell. Will be done. In LTE systems, subband CQI measurements can be made on an aperiodic basis, in which case the report is sent via PUSCH. Periodic wideband CQI measurements are obtained using PUCCH and the report can be sent to the eNB 102.

When the eNB 102 requires the UE 104 to make a channel quality measurement and return a CQI measurement, the eNB 102 can send command information (called downlink command information (DCI)) to the UE 104. In the FDD system, if DCI is sent in subframe n, QCI measurements are reported by the UE in subframe (n + 4). And adding the (n + 8) HARQ constraint on the uplink retransmission can represent that the FDD system contains four sets of RF beam patterns 902 that repeat every four subframes. In the TDD system, DCI commands can be constrained to be sent by the eNB 102 in the subframes shown in Table 2, i.e. the same subframes where ACK / NAK is allowed to be sent. The UE104 CQI measurement report is returned to eNB102 after k subframes, where k is shown in Table 3. The UE104 position determination algorithm uses a so-called aperiodic CQI report, which is returned via the PUSCH channel (ie, within the RF beam), so this is the subframe to which the DCI command is sent. And the corresponding subframe, including the CQI measurement report, means that the same RF beam pattern 902 should be generated.

(Determination of the number of RF beam patterns in the TDD system) Here, using the information in Tables 1, 2, and 3, we use the number of RF beam patterns 902 that can be maintained in a TDD system with a particular U / D configuration setting, as well as the same RF beam pattern 902. You can determine which subframes you need. The constraint is based on the fact that HARQ must be preserved in UE104 retransmission, that is, the original transmission subframe and the retransmission subframe must have the same RF beam. Also, the DCI of channel quality information measurements in a given subframe and the CQI report in another subframe may need to have the same RF beam 902 coverage in each subframe. The rationale for this statement is to locate the UE 104 in the RF beam 902 when the UE 104 first accesses the cell, and to track the UE 104 as it travels across a set of RF beam 902 positions covering the cell area 712. It is clear from the algorithms presented herein to do so. The information in Table 1, Table 2, and Table 3 is for each TDD. Incorporated in the table below to facilitate analysis for visualization of U / D configuration setting 1002.

The notes used in Table 4 are described here. In each TDD U / D configuration setting 1002, the configuration settings from FIG. 10 are repeatedly used for the convenience of the reader. The rows on the configuration settings are the subframe X (ie, any U subframe) through which the UE 104 can send uplink transmissions, the subframe (N) on which the corresponding NAK is received, and the corresponding retransmission. Is used to indicate the subframe (R) in which. If the relevant subframe occurs in the preceding LTE frame (Table 4 shows the 2 + LTE frame), this is N {j (in NAK, the reference transmission is in the previous LTE frame). Indicated by subframe j) or R {j (in retransmission, the original transmission occurred in subframe j of the previous LTE frame). In one case (TDD configuration setting 6), retransmission is for the original transmission 2 LTE frames before, so the notation R {j is used.

The column immediately below the configuration settings is used to indicate when the eNB 102 can send DCI commands to result in CQI measurements. The notation dci-j is used to indicate that the DCI command is sent in subframe j (this has already been shown in subframe j, so this part is for visual convenience). The corresponding CQI measurement result is returned to eNB102 and is a subframe represented by CQI-j. Similarly, if the corresponding DCI command occurs in the preceding LTE frame, the notation CQI- {j Is used.

<img id="000005" he="249" wi="152" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000006" he="247" wi="160" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

The data in Table 4 is analyzed as follows to determine the number of sets of RF beams 902 that a particular TDD U / D configuration setting 1002 can support, as well as the subframes that should use the same RF beam pattern 902. .. The results in Table 5 constitute the key constraints in this disclosure for LTE TDD systems that utilize RF beam scan antenna systems. A limitation in the corresponding LTE FDD system is that the RF beam pattern 902 is repeated every 4 msec.

Table 5: Number of RF beam sets and subframes requiring the same RF beam coverage in LTE TDD systems<img id="000007" he="222" wi="159" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000008" he="161" wi="147" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000009" he="161" wi="147" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000010" he="171" wi="143" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000011" he="161" wi="143" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000012" he="161" wi="145" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

(Positioning and tracking of UE in RF beam of periodic scan RF beam system) The present disclosure describes aspects of locating and tracking users in combination with RF beamforming techniques. Certain beamforming techniques simultaneously generate N RF beams 902, such as at 1 msec intervals. The N RF beams 902 cover the N subareas of the total coverage area 712 of the LTE cell, and the coverage area 712 is determined by the LTE cell using the same total transmit power without using beamforming techniques. Will be done. At the next 1 msec interval, another N RF beams 902 are generated to cover different sets of N subareas. This process can be repeated m times in an LTE Frequency Division Duplex (FDD) system, for example, after 4 msec (for m = 4) until the cell coverage area 712 is covered by 4 * N RF beams 902. it can. For example, with N = 4, 16 RF beam 902 subareas cover the entire cell area 712 in the FDD system. See Figure 9.

The RF beamforming technique depicted in FIG. 9 does not focus the RF beam 902 on a particular user device (UE104) as was done with other beamforming techniques. Rather, RF beams 902 are continuously generated at 1 msec each, covering the same RF beam 902 subarea every 4 msec in the FDD system. In FIG. 9, four sets of non-adjacent subareas are illuminated (for transmission) and focused (for reception) over four consecutive 1 msec time intervals.

In LTE radio systems, downlink transmission can be scheduled by software in base station 102 called a scheduler. The scheduler can also grant authorization for uplink transmission. In this way, the bandwidth available through the LTE air interface is allocated to different users at different times in a manner determined by the scheduler.

When using the RF beamforming technique outlined in Figure 9, it is important for the scheduler to know the current position of each UE, and as a result, at this 1msec interval at a particular 1msec interval. RF subsystem Allows uplink transmission permission to be granted only to the UE 104 at one of the four locations that are about to be focused by beamforming. Similarly, the scheduler schedules downlink transmission only for UE104, which is known to be located in one of the four RF beam 902 subareas that are about to be irradiated by the RF subsystem beamforming operation. You need to do it.

Therefore, it may be essential for the scheduler to know which RF beam 902 covers the current UE position in order to enable the effective use of RF beamforming techniques. There are two aspects to this problem that need to be resolved. One is when the UE 104 first accesses the cell (ie, during the Initial Attach to the LTE system, or during a neighboring cell-to-cell handover, or when the UE 104 exits the IDLE state. (While reconfiguring the connection to the current cell) is to determine the RF beam 902 that covers the UE104 position. A second aspect of this problem is tracking the UE 104 as the user travels across a subarea covered by the RF beam 902 generated by the cell's RF subsystem. This disclosure addresses these two aspects for the purpose of prioritizing the development of the technique and for providing the teaching necessary to locate and track the UE 104 for use with RF beamforming techniques. Provides the disclosed information.

In one example, in an LTE Time Division Duplex (TDD) system, 10 1msec subframes of each LTE frame 1002 are a set of subframes used for downlink transmission and a set of subframes used for uplink. Divided into sets. There are seven different configuration settings for subframes to k uplink subframes and m downlink subframes. See Figure 10. (Subframes marked with "S" are not used in the UE position algorithm presented herein). When the RF beamforming technique is used in an LTE TDD system, the UE 104 needs to schedule uplink and downlink transmissions in subframes (ie, 1 msec intervals) when the RF beam 902 covers the UE 104 position. Therefore, the need to determine the UE104 position within the RF beam 902 and the need to track the UE104 position across the RF beam 902 is LTE. Same as the need in the FDD system. However, rather than designing the RF beam 902 to have a pattern that repeats every 4 msec, as in FDD systems, the RF beam 902 pattern is used in any of the uplink / downlink configuration settings selected for the TDD system. Is repeated every 10 msec in the TDD system. See Table 6 for an exemplary list of subframes in each TDD configuration setting 1002 where the RF beam 902 patterns can be the same. As described herein, in each TDD U / D configuration setting, there are seven different acceptable modes of operation for assigning RF beam patterns to U / D subframes. Therefore, the number of sets of subframes indicates the number of different sets of 4-beam patterns that can be sustained in a given TDD configuration setting 1002.

Table 6: Number of RF beam pattern sets supported for each TDD configuration setting<img id="000013" he="166" wi="158" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

(Channel quality index) To allow downlink transmission to be optimized by adapting modulation coding schemes (MCS), mobile device 104 channels on the physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH). You may need to submit a quality indicator (CQI). CQI is the result of 4 bits representing the measured value. The measurements can span the entire frequency range of the cell bandwidth, or can span a subset of that frequency range. The entire frequency range can be divided into sets of physical resource blocks, and these sets are defined as "sub-bands" for the purpose of obtaining CQI measurements over a frequency range smaller than the total RF bandwidth allocated to the cell. Will be done. In LTE systems, subband CQI measurements can be made on an aperiodic basis, in which case the report is sent via PUSCH. Periodic wideband CQI measurements are obtained using PUCCH and the report can be sent to the eNB 102.

When the eNB 102 requests that the UE 104 make a channel quality measurement and return a CQI measurement, the eNB 102 sends command information (called downlink command information (DCI)) to the UE 104. In the FDD system, if DCI is sent in subframe n, QCI measurements are reported by UE104 in subframe (n + 4). In the TDD system, DCI commands are constrained to be sent by the eNB 102 in a subset of the subframes used for downlink transmission. The UE104 CQI measurement report is returned to the eNB102 after k subframes, where k depends on the TDD uplink / downlink configuration setting 1002 and (n + k) is in line with the uplink transmission in the TDD system. It is a configured subframe.

(CQI-based algorithm for finding UE location after random access, handover, or service request) Initial position of UE104 in FDD system The eNB102 system can recognize the presence of UE104 in cell coverage area 712 via random access (RA) procedure, handover procedure, or service request procedure, where the UE104 is a cell. Will be connected via. In order for this UE104 to be able to use beamforming techniques, it may be necessary to determine the current UE104 position in one of the 16 RF beams 902 in the FDD system. The following algorithm uses CQI measurements to determine the UE104 position within the RF beam 902. If the RF environment contains most of the multipath components, CQI measurements can be used to determine the RF beam for downlink transmission, and SRS measurements (disclosed below) can be used to determine the UE. The RF beam for uplink transmission can be determined by.

In an embodiment, if there is no contention immediately after the eNB 102 sends RA authorization to the UE 104, the eNB 102's MAC (Medium Access Control) software will force the UE 104 to provide an aperiodic report of the subband CQI value. Commands can be sent to each of the four consecutive subframes (ie, subframes n, (n + 1), (n + 2), and (n + 3)). (If there is a conflict, the command will issue Contention Resolution after the contention has been resolved, i.e. the eNB 102 will be on the PDSCH. It is sent after sending message). The eNB 102's MAC and PHY (Physical Layer) software is configured so that a selected set of measurement subbands is included in each of the transmission beam signals of each measurement subframe, and the beam irradiated with any transmission beam. It is possible to ensure that the transmitted energy from the subband focused on the area 902 is provided, i.e., if the UE 104 is within the irradiated beam area 902, make the desired CQI measurement of the configured subband. be able to. These aperiodic measurements are returned via the UE 104 PUSCH. If the measurement is made in subframe n, the report is returned in subframe (n + 4) in the FDD system.

The eNB 102's PHY and MAC software is UE in each of the four receive beam streams (n + 4), (n + 5), (n + 6), and (n + 7) at each of the reporting subframe intervals. Find PUSCH measurements. The received beam 902 covers a non-adjacent area (see Figure 9). This means that the measurement report for UE104 should generally be received in only one subframe and in only one received beam 902 signal in that subframe. However, it is also possible for the eNB 102 to receive measurement reports in the data stream of one receive beam 902 in each of the subframes reporting more than one. This situation occurs when the UE 104 is on the boundary between the RF beam 902 location areas. In this case, the MAC can select the measurement with the best CQI value (or one of the measurements if they are the same). The MAC can describe a subframe and a received beam 902 signal that includes the UE104CQI measurement report to determine which of the 16 beam 902 positions contains the UE104. This position is recorded as the current UE104 position (ie, the position that the eNB 102 can use when sending user plane transmissions to UE104 or when scheduling UE104 for uplink transmission in a non-multipath RF environment). ..

(UE initial position determination in TDD system) A technique similar to that used in the FDD system can be used to determine the position of the UE 104 within the RF beam 902 when the UE 104 first accesses the TDD system. Depending on the TDD U / D configuration setting 1002 (see Figure 10), if the contention does not exist immediately after the eNB102 sends the RA authorization to the UE, or after the contention is released when the RA contention occurs, the eNB102 MAC software for specific TDD Different RF beam 902 patterns occur in U / D configuration setting 1002, and commands can be sent to the next first subframe in each of the set of subframes in which DCI commands can be sent. See Table 4. This command causes UE104 to perform aperiodic reporting of subband CQI measurements. The MAC and PHY of the eNB 102 can be configured such that the DCI command is included in each of the subframe transmit beam 902 signals transmitted to the UE 104. This technique ensures that any transmit beam 902 has transmit energy from focused subbands on the irradiated beam area 902, ie, if the UE 104 is within the irradiated beam area 902, it is configured. The desired CQI measurement of the subband can be made. (The S subframe may not be used to send these commands to make aperiodic channel quality measurements to locate the UE 104 in the RF beam 902 area.)

These aperiodic measurements are returned via the UE's PUSCH. Depending on the TDD U / D configuration setting 1002, the subframes that can be used to send DCI and make aperiodic measurements are constrained. See Figure 10. Thus, if the measurement is made in subframe n, the report is returned in subframe (n + k) in a TDD system using normal hybrid ARQ operation. The value that can be n and the corresponding value k are specified in TS 36.213 a40. As an example, assume that the UE 104 accesses the cell in subframe 2 and the TDD U / D configuration setting 1002 used is configuration setting 0. Using the values of configuration setting 0 shown in Table 6 and FIG. 10, the MAC of the eNB 102 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 report in subframe 4 of that LTE frame.

The eNB102's PHY and MAC are UE104 in each of the four receive beam 902 streams at each of the reporting subframe intervals, depending on the TDD U / D configuration setting 1002. Find PUSCH measurements. If possible, the receive beam 902 (for configuration settings 5 or 6, in every U or D subframe, only one set of RF beam 902 is repeated, thus part of the RF beam 902 area. Cover non-adjacent areas (which may need to be adjacent to each other). This means that the measurement report for UE104 should generally be received in only one subframe and in only one received beam 902 signal in that subframe. However, it is also possible for the eNB 102 to receive measurement reports in more than one reporting subframe and / or in more than one received beam 902 data stream in each of those subframes. .. This situation occurs when UE 104 is on the boundary between RF location areas 902. In this case, the MAC selects the measurement with the best CQI value (or picks one of the measurements if they are the same, and / or receives more than one report with the best CQI value. If received as an RF beam signal, one of the received RF beam 902 signals can be picked out). The MAC can describe a subframe and a received beam 902 signal that includes the UE104CQI measurement report to determine which of the beam 902 positions contains the UE104. This position can be used by the eNB 102 when sending user plane transmissions to the current UE104 position (ie, when scheduling UE104 for uplink transmission when the RF environment is unaffected by multipath transmission. It is recorded as a possible position).

(CQI-based algorithm for tracking UE position) UE position tracking in FDD system If the UE104 position is determined after completing a random access procedure, a handover procedure, or a service request procedure, the UE104 needs to be tracked when it moves to another RF beam 902 position within the same cell coverage area 712. There is. The following algorithm uses the CQI report to track UE104 over a set of RF beam 902 positions that overlap the cell coverage area in an FDD system.

The value k (hundreds of msec, eg K = 20 at 2000 msec intervals) can be provisioned for a periodic check of the UE104 position. The eNB102 MAC can implement a CQI-based UE104 positioning algorithm similar to the algorithm specified above for initial access to the FDD cell. Therefore, commands can be sent to UE104 to perform aperiodic CQI reports in four consecutive subframes n, (n + 1), (n + 2), and (n + 3). Therefore, the UE104 measurement report is transmitted via PUSCH in subframes (n + 4), (n + 5), (n + 6), and (n + 7). As with UE104 positioning at the completion of the random access procedure, the eNB102 MAC ensures that the subband physical resource block (PRB) selected for measurement is on each of the transmitted beam signals on the measurement downlink. To be included. The eNB102's PHY and MAC are UE104 in each of the four received beamstreams 902 (n + 4), (n + 5), (n + 6), and (n + 7) at each of the reporting subframe intervals. Find PUSCH measurements. The receiving beam 902 covers a non-adjacent area. This means that the measurement report for UE104 should generally be received in only one subframe and in only one received beam 902 signal in that subframe. The MAC can describe the subframe and the received beam signal to determine which of the beam 902 positions contains the UE.

Since the RF beam covers non-adjacent areas in any subframe, the eNB 102 MAC should recover measurements from only one received beam 902 stream in any given report subframe. .. However, if the UE 104 is on the boundary between two or more RF beam 902 positions, the eNB 102 MAC will report the measurement in each of 2, 3, or all four of the measurement report subframes. You can receive it. The MAC records the position or multiple positions (up to 4) of the UE 104 in the temporary data set assigned to the UE 104. If the current UE104 position is not one of those determined through the measurement report just received, and if more than one UE position is determined, the MAC will be associated with the best CQI value of UE104. Select a position and update the current UE104 position accordingly. If the current UE104 location is one of the ones reported now, or if only one is reported, the current UE104 location will not be updated at this time.

Regardless of whether the current UE104 position is updated at this point, the aperiodic CQI report is repeated at Hmsec intervals until a single UE104 position is determined (a set number of 20msec intervals, eg, every 500ms). H = 25) to make aperiodic measurements of, which does not change at consecutive H * 20 msec intervals of M (provisioning value). If the UE104 check interval for the Kmsec period occurs before the UE104 position determined from the report remains fixed in M consecutive reports, the position check for the Kmsec period will not be performed on this UE104 and will be M. The check for consecutive fixed UE104 positioning continues at the H * 20msec rate.

If UE104 positioning remains fixed in M consecutive aperiodic report instances, update UE104 location information when it changes and perform H * 20msec execution of CQI-based location checking procedure. Cancel and resume Kmsec's UE104 position check procedure on this UE. This iteration of the four consecutive subframe CQI measurement procedures handles cases where the UE 104 is on the boundaries of different coverage areas illuminated by the RF beam 902 or moves periodically between RF beam 902 positions. (Note: The subband CQI measurement interval is one subframe, that is, the subframe when UE104 receives a command to make an aperiodic CQI measurement.)

(UE position tracking in TDD system) A technique similar to that for the FDD system can be used to track the position of the UE 104 within the RF beam 902 as it travels over the cell coverage area 712 of the TDD system.

The value K (hundreds of msec, eg K = 20 at 2000 msec intervals) is provisioned for a periodic check of the UE104 position. The eNB102 MAC can implement a CQI-based UE104 positioning algorithm similar to the algorithm specified above for initial access to TDD cells. Therefore, we send commands to UE104 and perform aperiodic CQI reports in non-S subframes where DCI commands can be sent, from each of the sets of subframes where different sets of RF beam patterns are generated. One subframe is selected to initiate aperiodic CQI measurements and the S subframe is not used for this purpose. Therefore, the number of DCI commands sent is a particular TDD. Equal to the number of sets of RF beams 902 generated by U / D configuration setting 1002 (see Figure 6). Therefore, the UE104 measurement report is sent via PUSCH in the subframe that is actually appropriate for the particular TDD configuration 1002 for the cell. The received RF beam area 902 covered by the TDD system in a given subframe may or may not be non-adjacent. This means that the measurement report for UE104 should generally be received in only one subframe and in only one received beam 902 signal in that subframe. However, it is also possible for the eNB 102 to receive measurement reports in more than one reporting subframe and / or in more than one received beam 902 data stream in each of those subframes. .. If the report is received in only one subframe and in only one received RF beam 902 signal, the MAC will subframe to determine which of the RF beam 902 positions contains the UE 104. And the received beam 902 signal can be described.

However, if the UE 104 is on the boundary between two or more RF beam 902 positions, the MAC of the eNB 102 will be in each of the measurement report subframes and / or one of the report subframes or it. Measurement reports can be received on more than one of the above received RF beam 902 signals. The MAC records the position or multiple positions of the UE 104 in the temporary data set assigned to the UE 104. If the current UE104 position is not one of those determined through the measurement report just received, and if more than one UE position is determined, the MAC will be associated with the best CQI value of UE104. Select a position and update the current UE104 position accordingly. If the current UE104 location is one of the ones reported now, or if only one is reported, the current UE104 location will not be updated at this time.

Regardless of whether the current UE104 position is updated at this point, the aperiodic CQI report is repeated at Hmsec intervals until a single UE104 position is determined (provisioning numbers at 20msec intervals, eg, every 500ms). H = 25) to make aperiodic measurements of, which does not change at consecutive H * 20 msec intervals of M (provisioning value). If the UE104 check interval for the Kmsec period occurs before the UE104 position determined from the report remains fixed in M consecutive reports, the position check for the Kmsec period will not be performed on this UE104 and will be M. The check for consecutive fixed UE104 positioning continues at the H * 20msec rate.

If UE104 positioning remains fixed in M consecutive aperiodic report instances, update UE104 location information when it changes and perform H * 20msec execution of CQI-based location checking procedure. Cancel and resume the UE104 position check procedure for Kmsec on this UE104. This iteration of the 4CQI measurement procedure handles cases where the UE 104 is on the boundaries of different coverage areas irradiated by the RF beam 902 or moves periodically between RF beam 902 locations. (Note: The subband CQI measurement interval is one subframe, that is, the subframe when UE104 receives a command to make an aperiodic CQI measurement.)

(Sounding reference signal in LTE system) The LTE standard defines an optional sounding reference signal (SRS) in the uplink direction. The SRS is transmitted by the UE 104 using a known sequence and using the set of PRBs assigned by the eNB 102 MAC software. SRS can be scheduled when UE104 is not sending user data and is commonly used to make uplink channel state estimates. The eNB102 MAC can schedule the periodic transmission of SRS in a short cycle of about 2 subframes. The eNB 102 MAC can also schedule a single aperiodic SRS transmission. SRS is detected by eNB102 and processed by the PHY layer. The PHY layer reports to the MAC layer the received SRS signal vs. noise level per resource block allocated for SRS. See Femto Forum, Doc.No.FF_Tech_003_v1.11 on page 104, 2010.

(SRS-based algorithm for finding UE location after random access, handover, or server request) UE initial position fixing in FDD system The UE104 positioning algorithm in the FDD system can operate in the same way as using the CQI report, except that the eNB102 MAC command causes the UE104 to make CQI measurements in four consecutive subframes. The difference is that it commands the UE 104 to send an SRS in each of the four consecutive subframes. These are aperiodic SRS transmissions. Each SRS transmission is transmitted at the subframe offset defined for all UE 104 by the cell specification parameter. The SRS transmission received on the eNB 102 can be used in a manner similar to the method used by the eNB 102 for CQI measurements to determine the RF beam 902 covering the UE 104 position.

(UE initial position determination in TDD system) The UE104 positioning algorithm in the TDD system can operate in the same way as using the CQI report, except that the eNB102's MAC can be sent a DCI command to allow the UE104 to make CQI measurements. Instead, the DCI command differs in that it now sends SRS transmissions. The command is a specific TDD Different RF beam 902 patterns occur in the U / D configuration setting 1002 and are transmitted in the next first subframe in each of the set of subframes in which the DCI command can be transmitted. See Table 4. This command causes the UE 104 to send an aperiodic SRS transmission in the PRB specified in the DCI command and in the U subframe corresponding to the subframe in which the DCI command was received. Each SRS is returned at the subframe offset defined for all UE 104 by the cell specification parameter. The SRS transmission received on the eNB 102 can be used in a manner similar to the method used by the eNB 102 for CQI measurements to determine the RF beam 902 covering the UE 104 position.

(SRS-based algorithm for tracking UE position) Tracking UE location in FDD system The UE104 position tracking algorithm in the FDD system can behave similarly to using CQI reporting, except that the eNB102 MAC command causes the UE104 to make CQI measurements in four consecutive subframes. The difference is that it commands the UE 104 to send SRS in each of the four consecutive subframes. Commands and reports are generated in the FDD system according to the time period values defined in the CQI-based tracking procedure outlined herein. These are aperiodic SRS reports. Each SRS report is returned at the subframe offset defined for all UE 104 by the cell specification parameter. The SRS transmission received on the eNB 102 uses CQI measurements on the eNB 102 to track the UE 104 as it moves from one RF beam 902 covering the UE 104 position to another RF beam 902 covering the UE 104 position. It can be used in the same manner as the method used.

(UE position tracking in TDD system) The UE104 position tracking algorithm in the TDD system can behave as it would with a CQI report, except that the eNB102 MAC command does not send a DCI command to force the UE104 to make a CQI measurement. Will send SRS transmissions. The command is a specific TDD Different RF beam 902 patterns occur in the U / D configuration setting 1002 and are transmitted in the next first subframe in each of the set of subframes in which the DCI command can be transmitted. See Table 4. This command causes 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 was received. Each SRS is transmitted at the subframe offset defined for all UE 104 by the cell specification parameter. The SRS transmission received on the eNB 102 uses CQI measurements on the eNB 102 to track the UE 104 as it moves from one RF beam 902 covering the UE 104 position to another RF beam 902 covering the UE 104 position. It can be used in the same manner as the method used.

(Efficient delivery of real-time event services across wireless networks) The real-time event service 1502 is a service that simultaneously delivers the same information content (for example, video and audio) to a plurality of users. An example is the delivery of the State of the Union address. The event does not have to occur in real time, i.e., delivering a pre-recorded TV program to users who simultaneously watch the same content constitutes another embodiment of this type of service. Providing real-time event services using the architecture shown in Figure 1 can be difficult. In a typical deployment, there can be approximately 600 eNB 102 elements that provide coverage for a particular geographic area. In the case of wireless users using the current architecture (ie, Figure 1), this means that each end user 104 connects to a server 124 that delivers these data streams, and the data streams to other end users. It can mean that it can be sent from server 124 to each end user independently of delivery. The situation when the LTE wireless user 104 receives the service is depicted in FIG. The real-time event server 124 can maintain a separate connection for each wireless user, thus the real-time event server 124 has 6 connections, as well as 6 independent packet transmissions for video and 6 independents for audio. Note that packet transmission can be required. The PGW 114 can also handle the delivery of 6 video streams and 6 audio streams to the SGW 110 element, which will serve the individual LTE users 104 to the eNB 102 element with 6 video streams and 6 Note that one audio stream can be delivered. Finally, each LTE The eNB 102 element delivers a separate video and audio stream to end users 104 who access the system through the eNB. Therefore, in the embodiment shown in FIG. 12, one eNB 102 can process the wireless delivery of the packet to the three users 104, and another eNB 102 wirelessly delivers the packet to the two users 104. , The third eNB 102 can wirelessly deliver packets to one user 104.

If the video data stream rate is 500 kbps (standard rate) and the audio stream rate is 32 kbps (standard rate), the example in Figure 12 handles 6 independent connections and sends them to these end users at about 3 Mbps. Will have a real-time event server 124. Similarly, the PGW 114 and SGW 110 can handle packet transfers at similar rates. These rates are well within the capabilities of current server and wireless network elements. However, the six users of this service are merely examples. In real-life situations, you can have 60,000 users 104 distributed across 600 eNB 102 elements, watching real-time events (eg, TV shows, sporting events, political events) at the same time. In the architecture of Figure 1, the real-time event server 124 may need to support 60,000 user connections and deliver a total data transfer rate of 60,000 x 500 kbps, or 30 Gpbs. This rate far exceeds the capabilities of the current server 124. It may be necessary to utilize multiple servers 124 (eg, 10 servers 124) in order for the transmission rate on each server to be manageable. Similarly, with multiple servers 124, the number of user connections on each server can be reduced to a more manageable value, perhaps 6,000 per server. The economic impact of deploying approximately 10 real-time event servers 124 to deliver this service to 60,000 concurrent users may not be favorable to service providers.

The situation at PGW114 cannot be easily improved. Deploying a large number of PGW114 elements servicing a geographically large area is uneconomical, and when servicing 60,000 wireless users 104 in this real-time event service, the PGW114 is said to be a 30 Gbps relay. Extremely difficult challenges need to be addressed, which can only be solved at great expense using the architecture in Figure 1. The situation with respect to the SGW110 element is not as bad as the PGW114 element, which is due to the fact that there are multiple SGW110 elements servicing a subset of 600 eNB102 elements in a region. In the eNB102 element, each eNB102 element must deliver the service to each of the approximately 100 users 104 connected through the cell, so each eNB102 element handles a 50 Mbps delivery over the LTE air interface. There must be. This value is the current LTE It may slightly exceed the capabilities of the eNB102 element, but can be well within the capabilities of the APN beamforming RF system presented in Figure 9. However, as a result, each eNB 102 may need to support 50Mbps utilization on the backhaul 112 interface in order to receive packets destined for the user from the SGW110 element. This value is problematic to resolve with each eNB 102 and can be costly. If not resolved uniformly across LTE wireless networks, the user experience will be compromised depending on which eNB 102 is used to access the LTE wireless network.

From the above, the problems associated with providing real-time event services (including commercial TV service distribution) to wireless users are the number of connections required by the real-time event server 124, the real-time event server 124 and the PGW 114 elements. It can include the required data transmission rate, and secondarily, the real-time data transmission rate required by the SGW 110, and the communication capacity used on the backhaul 112 interface to each eNB 102 element.

(Efficient and economical real-time event delivery architecture) The challenge associated with the economic delivery of real-time event services in LTE networks is when the Publish / Subscribe (P / S) architecture concept delivered to enhance the capabilities of optimal servers 202 and 204 is introduced into the APN wireless network. Can be resolved. Figure 13 shows an architecture that deploys the Publish / Subscribe broker program 1304 on a set of computer nodes 1302. One or more P / S brokers 134 can be deployed on each computer node 1302, depending on the number of entities expected to be connected on each computer node 1302. Each communication entity (ie, user device or server) can connect to a single P / S broker 1304 to receive services in the P / S broker architecture. Endpoints are not directly connected to each other in this architecture. Packets containing a particular data stream can be identified by tags called topics. Packets in the topic stream can be called events. In FIG. 13, one entity 1308 connected to P / S broker 1304 at node 1 1302 can publish a stream of packets, where publisher 1308 inserts a stream topic into each packet. On the other hand, 10 other users 1310 (ie, programs running on end-user devices, or other computers) may have previously subscribed to this topic. These users 1310 can be distributed across the three computer nodes 1302 shown in FIG. 13 in any case connected to the P / S broker 1304 running on the add-on node 1302.

The P / S Broker 1304 network is designed to deliver publish packets to all destinations that have subscribed to a given topic. P / S broker 1 1304 is aware of delivering packets to P / S broker 2 1304 within unique node 1 1302, and is also directly connected to the broker that was subscribing to the publish topic. Knows to deliver the packet to entity 1310. P / S Broker 2 1304 is aware of delivering packets on P / S Broker 3 1304 on Node 2 1302 and on P / S Broker 5 1304 on Node 3 1302, and is also on the publish topic. It knows to deliver packets to two entities 1310 that are directly connected to the broker it was subscribing to. P / S Broker 5 1304 is aware that it will deliver packets to the three directly connected entities 1310 that were subscribing to the publish topic. P / S Broker 3 1304 is a P / S Broker 4 Recognized to deliver packets to 1304 and to two directly connected entities 1310 that were subscribed to the publish topic. Finally, P / S Broker 4 1304 is aware that it will deliver the packet to a single directly connected entity 1310 that was subscribing to the publish topic. The publisher sends a single packet, and the P / S broker network handles packet replication whenever needed. Each packet is replicated by each P / S broker 1304 only to the required range. Therefore, the P / S broker network distributes packet replication operations in an efficient manner.

The distributed set of Publish / Subscribe (P / S) broker 1304 can be configured to run on the set of optimal servers 202, 204 shown in Figure 2, where the P / S broker 1304 is Publish / Subscribe. The communication paradigm can be used to efficiently route packets between entity 1308, which publishes a packet stream, and all entities 1310, which subscribe to receive packets from that stream topic. See the exemplary development of Figure 14.

As described herein, techniques that can be used to redirect the UE104 dedicated bearer 312 so that it has a local OptServere NB308 as the endpoint instead of the regular SGW110 endpoint are described. If each UE 104 in FIG. 14 is connected via a bearer that is also redirected to the OptServer eNB 308 associated with the serving eNB 102, the UE 104 can connect to a P / S broker 1304 program running on that computer. .. In FIG. 14, the P / S broker 1304 program can also run on server 124, which is remote from the LTE wireless network and can be located on the Internet. All P / S brokers 1304 in Figure 14 can be interconnected within the Publish / Subscribe broker network infrastructure.

If a server 124 remotely connected over the Internet provides the real-time event service 1502, the P / S broker 1304 network configuration shown in Figure 14 delivers this service when delivered using the traditional architecture of Figure 1. It can be seen that the problem that occurred when providing it was solved. See Figure 15 for the results that can be obtained using the Publish / Subscribe broker architecture along with the bearer redirection techniques described above herein.

Here, it can be seen that the above-mentioned problems related to the problem of providing the real-time event service 1502 to the wireless user 104 have been solved. The entity 1502 that generates the real-time event data stream is connected to one P / S broker, and the end-user 104 devices are not directly connected to the P / S broker. It turns out that the challenge of maintaining simultaneous connections to 60,000 users comes down to maintaining a single connection (which can be used to deliver other services in addition to the real-time event service). In addition, the real-time event service access program 1502 produces one video packet per video timeframe and one audio packet per audio timeframe to send to the P / S broker network, so this program It turns out that it is no longer necessary to generate 60,000 video packets per video timeframe and 60,000 audio packets per audio timeframe to send to 60,000 concurrent end users 104. It can be seen that packet replication is performed by the P / S broker network when needed. One real-time event server 124 can handle service delivery to 60,000 concurrent users, revealing that having a large number of real-time event servers 124 is no longer necessary. Therefore, it can be clarified that the economic impact of delivering this service is improved as compared with the case of using the current wireless network architecture. Therefore, it can be seen that the economic impact of delivering this service has been improved compared to using the current wireless network architecture.

Furthermore, it can be seen here that the Internet and longhaul networks transmit one packet per video timeframe and one audio packet per audio timeframe instead of 60,000 per timeframe. Therefore, it can be seen that the bandwidth utilization of the long-hole network has been reduced to 1 / 60,000 from 30 Gbps to 500 kbps.

It can be seen that PGW114 is not involved in routing packets in this service due to the presence of OptServer PGW304 and OptServer eNB308 servers associated with the eNB102 element. The communication capacity of PGW114 can be retained for delivering other services. Packets are routed by the P / S broker 1304 on the OptServer PGW304 to the P / S broker 1304 on each of the OptServer eNB308 servers with UE104 subscribed to the real-time event service data stream. To correlate the situation in FIG. 15 with the situation estimated from FIG. 12 (to 60,000 users), it is assumed that each of the 600 eNB 102 elements has 100 UE 104s subscribed to the real-time event service. Therefore, the P / S broker 1304 on the OptServer PGW304 replicates one packet per video timeframe and one audio packet per audio timeframe 600 times and forwards each of these packets to one OptServer eNB308 server. From the above, it can be seen that the transmission rate of the OptServer PGW304 is 600 x 500 kbps, that is, 300 Mbps, which is a value that can be appropriately processed by the current server computer. Furthermore, it can be seen that the transmission rate to each OptServer eNB308 via the LTE backhaul network is 500 kbps, which is one-hundredth of the required 500 Mbps using the current architecture.

It is also acknowledged that the need for OptServer PGW304 to deliver real-time event service packets at 300 Mbps can be reduced by having more than one server instance associated with PGW114. For example, if five OptServer PGW304 instances are deployed and each covers 120 of 600 OptServer eNB308 servers, the data transfer rate required for each OptServer PGW304 instance to deliver real-time event services is: It is reduced to 60Mbps.

In each OptServere NB308, the P / S broker 1304 receives one video packet per video timeframe and one audio packet per audio timeframe from the P / S broker 1304 running on the OptServer PGW304 (ie). Deliver packets to directly connected UE104 entities (at a rate of about 500kbps). In this embodiment, each eNB 102 supports 100 UEs involved in real-time event services, so the transmit data transfer rate on the OptServer eNB 308 is 100 x 500 kbps, or 50 Mbps. It can also be seen that this value can be performed using current server computer technology.

In this disclosure, it can be seen that the integration of the Publish / Subscribe broker architecture, bearer redirection capability, and optimal server into the LTE wireless network enables economical delivery of real-time event services, including commercial TV, to wireless users.

(Implementation of active-hot standby redundancy in server architecture using the Publish / Subscribe paradigm) In an active-hot standby redundancy architecture, two identical service instances 1602 and 1604 are installed in the network. The server 124 running each service instance can be located away from its concatenated server 124, or it can be co-located with the concatenated server 124 but on a different power source. The actual deployment situation can depend on the expected failure mode associated with server 124. The standby service instance 1604 can retain state information for each session maintained by the active service instance 1602, which is ready to be replaced. In the event of a failure in the active instance 1602, the standby instance 1604 activates itself and undertakes all aspects and rules of service identification information for the active instance 1602 to replace. Service to the user entity continues uninterrupted, but transactions that were in progress at the time of the failure can be lost.

KeepAlive messages can be used between the active instance 1602 and the standby instance 1604, so when the standby instance 1604 activates itself and takes on the service identity function and all aspects of the alternate failed instance. Can be determined.

When a point-to-point communication architecture is used, it can generally be difficult to transfer state information from the active instance to the standby instance. Retaining lock step state information on both the active service instance 1602 and the standby service instance 1604 can require significant overhead on the active service instance 1602 when providing state information to the standby service instance 1604. .. In a typical implementation configuration where service instances can run on different computer nodes, as in this case, state changes are first collected on the active instance 1602 and then forwarded to the standby instance 1604. Can be done. Therefore, many CPU cycles can be used in the active instance 1602 hosted to implement the hot standby architecture.

When the Publish / Subscribe paradigm is used with a distributed P / S broker architecture, it can be much easier to maintain a common state between active instance 1602 and standby instance 1604. Standby instance 1604 can be programmed to subscribe to exactly the same topics as active service instance 1602, including topics with unique instance ID tags used by active instance 1602. Therefore, the standby instance 1604 can receive exactly the same message that the active instance 1602 receives without taking any action on the part of the active instance 1602. The standby instance 1604 can process these messages exactly as the active instance 1602 does, with the exception of the standby instance while the active instance 1602 publishes responses and other service-specific messages. 1604 is unable to publish service-specific messages. The state information held in the standby instance 1604 can be held together with the state information held in the active instance 1602.

Each service instance can have an instance ID value that distinguishes one service instance from another. These values can be used in the KeepAlive exchange used by the standby instance 1604 to monitor the health of the active instance (s) 1602. The KeepAlive interactions shown in Figure 16 and described herein can be used in this active hot standby redundancy architecture. Standby service instance 1604 already uses the same instance ID that active service instance 1602 uses for service-specific interactions, so when a rule change occurs, standby instance 1604 fails to provide the service identification information of active instance 1602. You don't have to undertake it. Standby service instance 1604 turns on a software switch that activates itself and allows you to publish messages that were not published while in standby. The previous standby instance 1604 is now servicing and all service sessions continue uninterrupted.

The above paragraph shows how the standby instance 1604 can monitor the active service instance 1602, and if the active instance 1602 fails, it takes on all aspects of the rules of the active instance 1602. .. This active hot standby redundancy architecture is also shown to work when a single standby instance 1604 is ready to replace any of the N active service instances 1602. In this case, standby instance 1604 subscribes to the service topic to which each of the monitored active instances 1602 subscribes. Session state information can be organized on standby instance 1604 to allow identification of service sessions with a particular active service instance 1602. Standby instance 1604 can also maintain a separate KeepAlive exchange with each active service instance 1602 being monitored. When a failure is detected on the active service instance 1602, the standby instance 1604 activates itself, deletes session state information for all sessions except the session associated with the alternate service instance 1602, and alternates the service instance. Unsubscribe from all service-specific topics except 1602, and then turn on a software switch that previously couldn't publish service-specific messages. Service sessions previously processed by the failed service instance 1602 are now processed by the standby (now active) service instance 1604. The newly activated service instance also reports to the element management system 802 (EMS) and reports that the unique service instance 1602 has failed.

How the active hot standby redundancy architecture disclosed herein using the P / S broker messaging system is used to provide a hot standby redundancy server for the real-time event service 1502 described herein. It can be clarified what can be done. The hot standby redundancy server 124 can be deployed in addition to the real-time event server 124 shown in FIG. The service program 1502 running on the standby server 124 can exchange KeepAlive messages with the active service instance 1501 shown in FIG. 15 to determine the operating state of the active instance 1502. On the other hand, the standby service 1502 subscribes to the same topic that it subscribed to the active instance 1502 through the P / S broker network, and thus has the same state information that is held on the active instance 1502. Can be maintained.

(Status monitoring of active instance using KeepAlive message) Service instances 1602 and 1604 can implement a method of determining whether to assume an active or standby state when initializing. Further, the standby instance 1604 and the active instance 1602 can carry out KeepAlive communication exchange, so that the standby instance 1604 can determine the time when the active instance 1602 fails. The KeepAlive message repeat rate can determine the rate at which the standby instance 1604hs active instance 1602 fails and can activate itself. In general, the set number of consecutive non-replies to KeepAlive messages sent by standby instance 1604 can be used to declare the failure of active instance 1602. Since the processing of KeepAlive messages can be prioritized, there is no false declaration of service instance failure.

Figure 16 shows an example of KeepAlive messages that can be used with this redundancy architecture. All interactions are done using a service program connection to P / S broker instance 1304 running on server 124, 304, 308 machines. However, passing messages through the P / S broker 1304 architecture is omitted in Figure 16 for brevity. The active service instance (s) 1602 and the standby service instance 1604 can run on different server machines (124, 304, 308), which is resolved in the redundancy architecture of the server (124, 124,). This is due to the failure of 304, 308). In addition, the active service instance 1602 does not start sending KeepAlive messages, but always replies to KeepAlive messages it receives.

In the design of these service instances 1602 and 1604, each instance of &lt;serviceType&gt; can be configured with &lt;instanceID&gt;. Also, multiple topics (eg, text strings) can be hard-coded for communication with KeepAlive messages. All active service instances 1602 of &lt;serviceType&gt; can be subscribed to Topic ServiceControl / &lt;serviceType&gt; / KeepAlive. In addition, when initializing a service instance, you must decide whether it is active or standby, so you can subscribe to Topic ServiceControl / &lt;serviceType&gt; / KeepAlive / &lt;instanceID&gt;, where &lt;instanceID&gt; is unique. Can be the value assigned to the service instance of. The initialization program is also Topic You can subscribe to ServiceControl / &lt;serviceType&gt; / KeepAlive. The latter topic can be used to receive KeepAlive messages from another service instance that is initializing or in standby. There can be N active service instances 1602, but only one standby service instance 1604. Therefore, when the service instance is determined to be the standby instance 1604, it subscribes to Topic ServiceControl / &lt;serviceType&gt; / KeepAlive and also subscribes to ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby. The former subscription is used to receive KeepAlive messages from the active service instance 1602 that restarts for some reason.

When initializing a service instance, a single KeepAlive message can be sent to Topic ServiceControl / &lt;serviceType&gt; / KeepAlive at a periodically configured rate, indicating in the message payload that the state is "initializing". Can also include &lt;instanceID&gt;. The P / S broker 1304 messaging system handles replication of this packet when there are more than one service instance 1602 backed up in a redundant architecture. Each service instance that receives this message will Topic a KeepAliveResp message. It responds by publishing to ServiceControl / &lt;serviceType&gt; / KeepAlive / &lt;instanceID&gt;, where &lt;instanceID&gt; is the value received in the KeepAlive message. Therefore, messages can only be routed to the initialization service instance by the P / S broker 1304 system. The KeepAliveResp message contains the state of the sending instance and the &lt;instanceID&gt; of the sending instance.

If, after a set or a specified number of KeepAlive attempts, the Initialize Service Instance does not receive a response from any of the other Service Instances, the Initialize Service Instance sets its state to Standby, thereby setting the other. The active state can be assumed and the service can be started to be provided to the user without creating a gap in the state information collected later when the service instance is initialized. Once in standby, the service instance can unsubscribe to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / &lt;instanceID&gt;" and subscribe to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby". Can be added. Subscriptions for the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive" can be retained. Standby service instance 1604 initiates the publishing of KeepAlive messages at a set or specified periodic rate after a set or specified time that can wait to allow initialization of other service instances. Can be done. KeepAlive messages published by standby service instance 1604 use the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive" and include the standby state and the message publisher's &lt;instanceID&gt;. Responses to KeepAlive messages received from the standby service instance are published to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby".

If a response is received from the standby service instance 1604 in response to any KeepAlive message sent by the initialize service instance, the initialize instance activates itself and the topic "ServiceInstance / &lt;serviceType&gt; / KeepAlive / You can unsubscribe from "&lt;instanceID&gt;" and keep the subscription to "ServiceControl / &lt;serviceType&gt; / KeepAlive".

If, after sending a configured or specified number of KeepAlive messages, the Initialize Service Instance receives a response from less than N Active Service Instances 1602 and does not receive a response from the Standby Service Instance 1604, the Initialize Instance puts the state on standby. You can change it, unsubscribe from the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / &lt;instanceID&gt;", and add a subscription to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby". Can be done. Subscriptions to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive" can be retained. Standby instance 1604 can start publishing KeepAlive messages at a configured or specified time period rate.

If the initialize instance receives a response from all N active service instances 1602, the initialize instance should change state to standby and unsubscribe from the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / &lt;instanceID&gt;". And you can add a subscription to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby". Alternatively, if the Initialize Service Instance receives a reply from the Standby Instance 1604, the Initialize Service Instance activates itself, unsubscribes from the topic "ServiceInstance / &lt;serviceType&gt; / KeepAlive / &lt;instanceID&gt;", and " Keep a subscription to "ServiceControl / &lt;serviceType&gt; / KeepAlive".

After a set or specified number of KeepAlive attempts, the initialization instance receives responses from other service instances, where the total number of replies is N or less, and some responses (including 0) are active. If a service instance is indicated, another response indicates a service instance in the initialized state, and no response indicates a standby state, then the outbound service instance has its &lt;instanceID&gt; of the &lt;instanceID&gt; value of all other initialized instances. It can be active if it is less than one, and it is on standby if its &lt;instanceID&gt; is greater than the value of all other service instances reporting that it is in the initialized state. Can be. Depending on the state assigned by the Initialize Service instance, the subscription described above may be deleted, added, or retained depending on the state assigned by the Initialize Service instance.

If standby service instance 1604 receives a KeepAlive response from another service instance that also indicates that it is in standby, the instance that receives the response has an &lt;instanceID&gt; value greater than the value indicated in the response message. If it is large, it keeps the standby state, but if &lt;instanceID&gt; is smaller than the value indicated in the response message, it changes the state to active. When transitioned to the active state, the changed service instance unsubscribes from the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby" and retains the subscription to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive".

Whenever a service instance receives a KeepAlive message from standby instance 1604, it publishes a response message to the topic "ServiceControl / &lt;serviceType&gt; / KeepAlive / Standby" and its current state in addition to the unique identifier of the responding service instance. Is shown. Therefore, this response message is routed to standby service instance 1604 by the P / S broker 1304 networking architecture.

From the above, it can be seen that the logic for determining the active / standby status of the service instance is complicated. Figure 16 shows the KeepAlive interaction between one active service instance 1602 and one standby service instance 1604. The P / S broker 1304 subsystem is not shown to maintain the most orderly diagram possible. Also, for brevity, FIG. 16 does not show all the examples illustrated in the paragraph above. Those skilled in the art will appreciate that the description herein constitutes a perfect algorithm for determining the active or standby state of an Initialize Service instance.

Figure 16 shows the &lt;instanceID&gt; identity of a service instance that can retain the &lt;instanceID&gt; identity for KeepAlive message exchanges when the standby instance 1604 activates itself, but alternates for all service-specific messages. Note that it indicates that&gt; can be used. By doing so, the UE 104 whose session was interrupted at the failed service instance restarts or resumes those service sessions at the alternate service instance using the same service instance ID value obtained at the start of the service session. It becomes possible to do. It can also generate an alarm message with the previous standby service instance 1604, report the failure of the service instance 1602 that was active before a particular one, and report the state change of the standby instance 1604 to the active state. The alarm message is not shown in Figure 16.

(Architecture to reduce backhaul usage when servicing wireless users) What is disclosed herein allows the UE 104 to connect to the optimal server 308 associated with the serving eNB 102 via a redirected bearer 312, in addition to the usage of the optimal server architecture integrated into the LTE wireless network. It provides a means, as well as a Publish / Subscribe broker architecture that provides efficient delivery of real-time event services to wireless users. In a real-time event service, many users receive the same information (eg video, audio) at the same time. One of the efficiencies provided by the architecture is that it is significantly reduced compared to the backhaul 112 utilization required to serve services using the current architecture.

Other types of services deliver the same information (eg, video, audio) to a large number of users, but not so much at the same time. One embodiment can be a streaming movie distribution service. With this service, many users may choose to watch the same movie, each at a different time. When the traditional architecture shown in Figure 1 is used, each such end user 104 in an LTE wireless network is an Internet 122, a longhaul network 804, an extended packet core (EPC) network element (PGW114 and SGW110), serving. It receives a unique video data stream and a unique audio data stream through the backhaul network 112 that connects the eNB 102 to the EPC and the LTE interface.

A better approach could be to use the set of optimal servers 304, 308 described in this disclosure, along with the Publish / Subscribe broker architecture as shown in FIG. When the service (eg, Streaming Movie Distribution Service (SMD) 1702) is provided by OptServer eNB308 shown in Figure 14, and for each user who wants to receive Streaming Movie Distribution Service 1702, see Figures 3 and 4. When the UE 104 dedicated bearer redirection 312 shown is called, the movie distribution to each such user does not use the LTE backhaul network 112. It can be seen that the video and audio packet streams travel from the OptServer eNB 308 associated with the user serving eNB 102 through the eNB 102 and across the LTE interface to the user equipment 104. This technique is applicable to any service that has features that require the same information to be sent to multiple users 104, but not necessarily at the same time. The streaming movie distribution service 1702 is just one example of a service having this feature.

To provide a streaming movie distribution service, a streaming movie distribution (SMD) application 1702 can be deployed and run on each of the optimal servers 304 and 308. See Figure 17. This application 1702 can access movies stored locally in permanent storage, but the number of movies stored may be more limited in the OptServere NB308 element than in the OptServer PGW304 element. Movies that are not stored on either the Optimal Servers 304 or 308 in the APN wireless network are obtained from a more remote storage device 1704 via the Internet and stored on the OptServer PGW 304. The delivery of movies to the eNB 102 location can be controlled by a Streaming Movie Delivery Service (SMD) 1702 service instance running on the OptServer PGW304 and is based on the number of 104 users accessing a particular movie from a particular eNB 102 location. Can be done.

Video streaming can utilize not only a large amount of radio bandwidth, but also a large amount of bandwidth on the backhaul connection 112 between the eNB 102 and the SGW 110 in general. Therefore, a relatively small number of users participating in the video streaming service in one eNB 102 can utilize most of the wireless and backhaul 112 communication capacity of the eNB 102. The beamforming system discussed in the present disclosure can enhance the air interface communication capacity and thus serve a larger number of higher bandwidth users 104 than the current eNB 102 implementation configuration, but backhaul 112 bandwidth. Corresponding increase in may not be available. Therefore, it is important to reduce backhaul 112 bandwidth as much as possible, especially when delivering video services. When the backhaul 112 is highly utilized, the service provision to all users 104 may be impaired, and the service quality for all users 104 may be deteriorated. In addition to deploying the APN optimal server 308 at the eNB102 location and bearer redirection 312 on the eNB102 element, the Publish / Subscribe 1304 message delivery system deployed on the optimal servers 304, 308 reduces backhaul 112 utilization of the eNB 102. Therefore, the quality of service for all users 104 can be maintained. Also, due to the short path between the UE 104 and the point at which the service is provided, the delay in transmitting the audio and video data streams to the UE 104 is minimized as much as possible. This subsection shows how backhaul 112 utilization is minimized when one or more users access the streaming movie distribution service 1702.

FIG. 4 shows the interaction between the UE 104 and the software running on the OptServer PGW 304 when the user 104 calls the streaming movie distribution service 1702 on the UE 104. Dedicated bearer 302 can be configured to support service 1702 called by the user, who is redirected 312 to OptServer eNB308 associated with eNB 102 servicing UE 104. UE104 may need to be connected to P / S broker 1304 running on OptServer eNB308 in order to receive its services via P / S broker middleware.

The following is an example of how the streaming movie distribution service 1702 can be designed. Other designs can also be implemented. See Figure 17 for the service deployment architecture. See Figure 18 for the service message interaction to be considered next.

When the user selects the streaming movie distribution icon on the UE104 display and enters the movie with the name to watch, the UE104 software uses the linkedBearerID, DedBearerID, ServerIP, and ServerPort parameters obtained from OptServerPGW304 to P on the OptServere NB308. / S Can connect to broker 1304. The UE104 must deploy a service instance that can stream the selected movie to the UE104, so the UE104 publishes a Service Discovery message to the topic string "ServiceInquiry / StreamingMovieDelivery / &lt;movie name&gt;" and the message payload. The IMSI and serving eNB ID of UE104 can be included in. UE104 also has the topic "Service Description / StreamingMovieDelivery / &lt;movie" Send a subscription to "name&gt; / &lt;IMSI&gt;". By including the UE IMSI in these messages, it is possible to allow the broker network to route the response from any streaming movie distribution service instance 1702 only to the UE 104 making this request.

All streaming movie distribution server programs 1702 can subscribe to the topic "ServiceInquiry / StreamingMovieDelivery / *", so that all instances of this service can receive UE104 inquiry messages. In the embodiment shown in FIG. 18, the service instance 1702 executed on the OptServer eNB 308 at the serving eNB 102 position can receive the Service Inquiry message that the service instance 1702 can execute on the OptServer PGW 304. The UE104 Service Inquiry message is replicated by the P / S broker 1304 instance connected to the UE104 on the OptServer eNB308. The configuration of P / S broker 1304 of OptServer PGW304 is this Service It is assumed that in the serving eNB 102 and PGW 114, only the streaming movie distribution instance 1702 can respond if they can serve the movie, blocking further routing of the Inquiry. (In this embodiment, the service instance in the OptServer PGW 304 can store all the movie sets that can be provided by any OptServer eNB308, but the movie set stored in a particular OptServer eNB 308 is as follows: UE104 may include the serving eNB102 identifier in the Service Discovery message it sends, so the Streaming Movie Distribution Service Instance 1702 in PGW114 is relevant if it has not yet been stored. It is possible to determine when sufficient downloads are required from that location to authorize the transmission and storage of the movie at the eNB102 location.)

Each responding streaming movie distribution instance 1702 can publish a service response message to the topic "ServiceDescription / StreamingMovieDelivery / &lt;movie name&gt; / &lt;IMSI&gt;". This message can only be routed to the requesting UE104. In this case, two response messages can be returned to UE104. The UE104 software determines from the parameters contained in the message (eg, the associated eNB ID, or PGW) that the service instance 1702 in the OptServer eNB308 is closer to the UE104 and selects the UE104 to deliver the service. be able to. The Service Description message can include a unique ID assigned to service instance 1702.

Each SMD service instance 1702 subscribes to a control message stream topic for that service. In this case, the topic can be "ServiceControl / StreamingMovieDelivery / &lt;unique ID&gt;". Therefore, the UE104 software has the topic "ServiceControl / StreamingMovieDelivery / &lt;unique". If you publish a service request message for "ID&gt;", you can route it to service instance 1702 at the serving eNB102 location. The movie name is used by UE104 to receive the payload of this message, as well as the "StartMovie" indicator, and any other parameters needed to start the service (eg, billing information, audio portion of the movie). Topics (including UE104IMSI to reliably route back to UE104), topics used by UE104 to receive movie video streams (including UE104IMSI to reliably route back to UE104), movie control It can be placed on topics used by UE104 to receive information, including UE104IMSI to ensure routing back to UE104.

Audio and video streams can be published by service instance 1702 running on OptServer eNB308 associated with serving eNB 102, so backhaul 112 is not used to send these streams to UE 104. The UE104 software receives the streams and renders these streams to the user.

As a result of this event, as long as some UE 104 are provided by a particular eNB 102 and the requested movie is available on the OptServer eNB 308 associated with the eNB 102, it will transmit either an audio / video stream to these users 104. The backhaul 112 is not used. Due to this architecture, significant backhaul 112 utilization is saved.

(Providing streaming movie distribution when the movie is not stored in the serving eNB position) If the requested movie is not available on the Streaming Movie Distribution Service Instance 1702 at the serving eNB102 location, the Service Instance 1702 may not reply to the Service Inquiry published by UE104. See Figure 19. If the movie is available on service instance 1702 at PGW 114, service instance 1702 can respond to the Service Inquiry of UE104 and the movie is served by service instance 1702. The service-only bearer 312 for UE104 is redirected in the serving eNB102, so the routing for the movie stream is from the streaming movie distribution instance 1702 in PGW114 through the P / S broker 1304 connection on the OptServer eNB308 associated with the serving eNB102. P / S broker 1304, then UE104. See FIGS. 17 and 19.

On the other hand, the SMD service instance 1702 in PGW 114 can increment the count of requests for this movie at the eNB 102 location because the UE 104 can include the current serving eNB 102 identity in the Service Inquiry message. Future requests for this movie by UE104 attached through the eNB102 will be provided by the Streaming Movie Distribution Service Instance 1702 associated with the eNB102. Therefore, the SMD service instance 1702 in PGW 114 can hold a record of the SMD service instance 1702 and their eNB 102 locations and can provide each movie. This information can be used in the OptServer PGW 304 in a handover situation with the wireless control process 3902 software to help the service-only bearer 302 decide whether to redirect at the target eNB. Utilization-based algorithms can also be implemented to determine when a movie should be erased from a storage device at a particular eNB 102 location.

If the streaming movie distribution service instance 1702 on PGW114 does not have local storage for the specified movie in the ServiceInquiry message on UE104, the SMD instance 1702 will be centralized main storage for this movie service over the Internet 122. It can interact with 170, so that the movie can be retrieved. When a movie packet is received from centralized main storage 1704, the packet is stored on disk. If SMD instance 1702 on OptServer PGW304 determines that a movie is available from centralized main storage 1704, it can send a ServiceDescription response to the UE104's ServiceInquiry message. In this case, the movie is served by SMD service instance 1702 running on OptServer PGW304. See Figure 19 for the messages associated with this situation.

Although only some embodiments of the present disclosure have been illustrated and described, many modifications and amendments to them without departing from the technical ideas and scope of the present disclosure set forth in the appended claims. It will be clear to those skilled in the art that this can be done. All patent applications and patents, both domestic and international, and all other publications cited herein are incorporated herein in their entirety to the full extent permitted by law.

(APN LTE network that functions as a dual-use network) Dual use means that it can be used simultaneously by public and government agencies with the following conditions: Whenever deemed necessary (ie, under the control of the U.S. Government without waiting for a court order), network access has a lower priority than the minimum permissible priority set by the Government Administrator, or It can be denied for all users / entities that are not one of a subset of the allowed highest priority access classes set by the government administrator. In addition, network access can be denied to all users / entities who are not members of designated government agencies that are allowed access to the network. The LTE cell exclusion feature for government use can be applied to any cell, or all cells, or a subset of cells in a 3GPP wireless network. Also, when cell exclusion for government use (CB for GU) is enabled, the network is not a member of an allowed government agency and / or has a lower priority than the lowest allowed priority, or It can be possible to cause detachment of all users who are not one of a subset of the permissible highest priority access classes set by government administrators. It can also allow exceptions to established emergency sessions on the network, and as a result, allow emergency access at the discretion of the U.S. Government administrator. it can. Finally, the network can allow a user identification validation test to be performed before allowing the user to maintain access to the GU CB enabled network or parts of the network. It can be made clear to those skilled in the art that the above-mentioned CB capacity for GU is far superior to the 3GPP cell exclusion capacity specified for 3GPP networks. The rest of this disclosure with respect to this feature is 3GPP with the features described above. Focus on how to design dual-use capabilities for LTE wireless networks. It is understandable that this same principle can be used when building dual-use capabilities in other types of 3GPP wireless networks such as the 3G Universal Mobile Telecommunications System (UMTS).

See 3GPP documents TS36.331 and TS22.011; TS23.203 (policy management rule function, etc.) and TS23.228 (IP multimedia services, etc.) for standardized cell exclusion specifications. See also TS22.153, Multimedia Priority Service Requirements. These standardization specifications do not allow dual-use networks as described above. Moreover, not all of the details for proper implementation of these standardization functions are given in these 3GPP documents. These standardization features can be combined with additional new features and features to implement the types of dual-use wireless networks described above. The information contained in this disclosure is described in clear terms that can be understood by anyone skilled in the art capable of implementing dual-use LTE wireless networks. Standardization features will be integrated with new additional features to achieve this goal.

(Identification of government users from general users using the concept of network roaming) The international mobile telephone subscriber identification number, or IMSI, is a unique identifier assigned to each user device (UE104) that has access to the 3GPP wireless network. The 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 mobile phone network code (MNC) in that country. The remaining 9 (or 10) digits are the mobile telephone subscriber identification number within the network. Therefore, the home network of a 3GPP wireless network is identified by a particular MCC and an MNC value that identifies a particular public land mobile network (PLMN). A user who has a contract with a network operator can be assigned an IMSI within the network and access the operator's cell. These cells are in the IMSI home network.

In many cases, each network operator has a mutual agreement, in which a user within one operator's network is granted access to another operator's network and vice versa. Such users are called roaming when they access cells on an operator network that is different from their home network.

Network operators can generally provision wireless network elements to define both a home network and a set of allowed roaming networks. UE104 with an IMSI that is not in the home network of the cell being accessed or is not in the list of roaming networks provisioned in the home network is not allowed access to the cell.

The roaming concept described above can be used to help implement some of the requirements for dual-use networks. UE104, a member of a government agency, can be assigned an IMSI within the home network of a dual-use network. Members of different agencies can be identified by agency by using a subset of MSIN values to assign to members of a particular agency. Alternatively, members of different institutions can be assigned IMSIs with different MCC and MNC values, where each of these networks is defined to be equivalent to the home network in a dual-use network. To. In a home network, members of the equivalent network are treated the same as members of the home network. As with home networks, the equivalent networks in the list are provisioned to the network elements used to control access to the home network. The concept of equivalent networks is defined in the 3GPP standard.

According to the previous paragraph, members of the agency are assigned the IMSI value in the home network of the dual-use network or the value in the set of equivalent networks of the dual-use network. All other users can be assigned IMSI values in the traditional network operator's network and can access the dual-use network as roaming users. General users have low cost services, can receive faster data transfer rates than cells in their home network, are less congested than cells in their home network, or for other reasons. And may prefer access to dual-use networks.

Generally, ordinary users can access cells in a dual-use network as roaming users and receive the same quality of service provided to members of government agencies who access the dual-use network as a home or equivalent network. .. An element management system (EMS802) that manages the network elements of a dual-use network can be used to provision the network elements with home network values, network values for each equivalent network, and network values for each allowed roaming network.

In an emergency, or when a government administrator deems it necessary, access to one cell, multiple cells, or all cells in a dual-use network can be restricted to use only by government users. One step in achieving this constraint is to have the EMS provision each mobility management entity (MME108) dealing with one or more constrained cells to eliminate the allowed roaming networks on the list. be able to. In this case, MME108 rejects users who access the constrained cell or access any of the constrained cells if they are members of a non-home network or equivalent network. Can be done. In this case, the attempted access can be denied due to the "permanent PLMN constraint". Upon receiving this factor value, the UE 104 can put the PLMN on the prohibited PLMN list so that the UE 104 attempts additional access to the PLMN only by manually selecting cells in the PLMN. Alternatively, if only the selected cell set is constrained, the rejection factor value can be a "temporary PLMN constraint". In this case, the UE 104 can put the tracking area (TA) of the constrained cell in its constrained TA list to prevent it from trying to access another cell in this TA. It may also be a case of constraining a subset of roaming networks and provisioning to allow the rest of the roaming networks. This type of provisioning can be at the individual discretion of the government network administrator.

FIG. 20 below is a modification of FIG. 1 of the present disclosure, which includes an EMS 802 that manages network elements in an LTE network. Figure 20 shows that when a cell is constrained, the MME108 dealing with the cell can be provisioned to exclude or constrain the roaming network in the allowed list, and the MME108 is a home network, or equivalent network, or It shows that all UE104s that are not members of an authorized roaming network can be detached in a dual-use network. The MME108 holds the UE104 IMSI as part of the contextual information held for each UE104 handled by the MME108. See section 5.3.8.3 of TS23.401 v9.4.0 for the detachment procedure by starting MME.

The use of roaming concepts helps to detach non-governmental users 104 from constraint cells and deny access to these users' constraint cells, but these UE 104s still attempt to access the constraint portion of the dual-use network. there's a possibility that. In the event of a disaster or other emergency, such access attempts may block or delay access for high priority government users, police users, fire department users, or emergency personnel users. In such an emergency, these users must be provided with prompt access. The 3GPP cell exclusion concept can be extended as described in this disclosure to achieve another aspect of implementing dual-use LTE wireless networks.

(Architectural component that performs cell exclusion and user identification confirmation) Cell exclusion is a standardization mechanism that can be used to limit the set of UE104s that are allowed access to a cell. When cell exclusion is enabled on a particular cell, the broadcast information from the cell is the CellBarred parameter, ac-BarringFactor parameter, ac-BarringTime parameter, ac. -Includes a list of allowed / disallowed high priority access classes included in the BarringForEmergency and ac-BarringForSpecialAC parameters. The CellBarred parameter in System Information Block 1 (SIB1) indicates whether any access constraints are enabled on the cell. The SIB2ac-BarringFactor and ac-BarringTime parameters are Access Class between 0 and 9. Determines how often a UE 104 with Priority) may attempt to access a cell. The SIB2ac-BarringForEmergency parameter indicates whether E911 calls are also excluded on the cell. ac-BarringForSpecialAC is a Boolean list detailing access rights to each high priority access class. The UE104's access class (AC) priority stored in the SIM card allows the UE104 to determine what to do when it detects that a cell is excluded from access. The legitimate user is assigned an AC value between 0 and 9 (this value is randomly assigned to the legitimate user) to the user's UE104. For TS22.011, AC10 will be used for E911 calls, AC11 for PLMN users, AC15 for PLMN staff, AC12 for security services, and AC13 for utilities (eg gas and water suppliers). , And AC14 are for emergency service users. The 3GPP standard indicates that there are no priorities associated with AC11-AC15. No other access class values are defined in the 3GPP standard, so dual-use networks must be able to operate using only these values configured on the UE104's SIM card.

According to the 3GPP standard, UE104 with an access class priority value greater than 10 is always allowed to access excluded cells when CellBarred is set to "excluded". This may or may not be desirable by government officials when cells are excluded for government use. Fine-grained exclusions based on UE104 access class priority may be required (eg, access must be excluded for ACs less than 12 or other users with AC12). Must be excluded against, or to identify government users More access class values may be required than in the 3GPP standard). The disclosure of the present invention provides design information to achieve a higher fine particle cell access exclusion capability. Also, in a dual-use network, it may be necessary to restrict access for users of equal high priority as described above (eg, FBI users with access class priority 12 access excluded cells. Other users with access class priority 12 will need to restrict access to the excluded cells). The design information presented in the disclosure of the present invention uses the UE 104 IMSI to further restrict access to excluded cells by high priority users. Finally, in a particular environment, the UE 104 SIM card may have been illegally set to a high priority access class by a criminal or terrorist, or may have a programmed IMSI assigned to a high priority user. .. Therefore, it can be a requirement in a dual-use network to be able to perform a biopsy of any high priority user who is connected through a cell excluded for government use. The biopsy can include voice matching, fingerprint matching, or any other type of test with unique user characteristics or knowledge (eg, password). This need for biopsy is also considered as the information presented in this disclosure for dual-use networks.

It may be the case that it is necessary to set the cell exclusion strictly according to the 3GPP standard to one or more LTE cells. On the other hand, the paragraph above indicates that additional access restrictions should be enabled when cells are excluded for government use. Therefore, the design description of this disclosure defines a particular CellBarred type, called CellBarred (CB for GU) for government use, and is distinct from the CellBarred capability defined in the 3GPP standard document. The design information included in this disclosure and understood by those skilled in the art indicates how to add the CB CellBarred capability for GU to be used in addition to the CellBarred specified in the 3GPP standard.

The system design 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 modifications to the design information presented herein can be implemented with the same results. A particular set of design information is presented herein to illustrate to those skilled in the art how a dual-use network is implemented.

Figure 21 shows the LTE network components that can be required to implement the GU CB capabilities described above. Note that FIG. 21 includes the optimal server concept and the P / S broker concept described herein. By including these components in the design information, the system disclosed herein will probably be more efficient than having other types of element interfaces. The solid line in Figure 21 shows the standard interfaces in the LTE network, including the mnemonics used in the 3GPP standard for each interface. The dashed line shows the additional interfaces that can be needed to provide dual- use functionality. The dashed line connected to the government-executed element management system (EMS802) is the type of OAM interface (Operations, Administration, and Maintenance) that exists in any LTE network. Interfaces), but in this case, they can provision information that can be related to dual-use network capabilities. The interface between the LTE MME108 and the P / S broker 1304 running on the OptServer PGW304 node plays a central role in providing multiple MME108 elements deployed in the LTE network and dual-use functionality to the LTE network. Can provide an efficient interface to and from the application function (AF) 2102.

If CellBarred does not actually exist in any cell in the LTE network, EMS802 does not provision AF2102 with additional CellBarre information and does not provision MME108 element with additional CellBarre information. If the standardized CellBarred does not actually exist in any cell in the LTE network, the EMS802 also does not provision the AF2102 with additional CellBarre information and the MME108 element with no additional CellBarre information. When CellBarred is enabled for government use in one or more cells in the LTE network, the EMS802 will AF2102 additional data related to the CB for GU, the MME108 element servicing the exclusion cell, and the exclusion. Provision to the eNB102 element that activates the cell (the information provisioned to the eNB102 element is the same as the information required for the standardized CellBarred function). The following sections describe the processing design that implements the dual-use wireless network feature elements.

In addition to the network elements and interfaces shown in Figure 21, new applications can be added to the UE 104 to enable biometric user verification in dual-use LTE networks. The added capabilities of UE104 are illustrated in Figure 22. UE104 can also connect to the P / S broker 1304 network for services other than biopsy. The advantage of using P / S broker 1304 middleware is that a single connection of UE104 to the P / S broker 1304 network is sufficient to support several UE104 applications. Each application uses application-specific topics through the P / S broker interface 2204. Therefore, the UE104 app for biopsy 2202 can be called the first time UE104 is turned on and connected to the LTE network. The biopsy app 2202 is subscribed to receive messages via a specific topic and can wait until the initial biopsy message is received (testing is generally not required, so the message should be sent). Not). It can be understood by those skilled in the art that P / S brokers are not essential for biotesting capabilities, as UE104 can be individually connected to network-based programs for such testing. P / S broker 1304 middleware makes the solution more efficient.

(Automatic detachment of constrained users when government-only use is enabled) The 3GPP standard defines mechanisms for allowing, gated, or denying user access to a network. To achieve this, the 3GPP standard provides a policy billing rule function (PCRF118) and an application function (AF2102) that can be involved in the interaction with PGW114 when the user first establishes access to the LTE network. It has established. These elements are shown in Figure 21. Certain features can be added to the AF2102 to implement the capabilities required in a dual-use network. AF2102 can provision a list of cell ID values for cells that are excluded from access for government use. In each cell with GU CB enabled, the provisioning data is in a subset of the minimum access class priority allowed to access the cell, or in the high priority access class value allowed, excluded cells. It can include a parameter that indicates whether an E911 call is accepted, a parameter that indicates whether biotests have been enabled to access the cell, and a parameter that indicates the shortest time interval between biopsies in the same UE104. .. In addition, AF2102 can provision or access a list of IMSI values and access class priorities for each value. Since these AC priority values are associated with the IMSI in the database used by AF2102 and are not included in the UE104's SIM card, the AC priority values are not constrained to the standard values 11-15 and are any. Note that you can assign a value. Therefore, in the GU CB, extremely fine access class constraints can be imposed by using these AC priority values as described in the present disclosure.

As shown in FIG. 21, AF2102 maintains an Rx Diameter interface for a set of PCRF118 deployed in the LTE network and also maintains an interface for P / S broker 1304, thus AF2102 for communication. Publish / Subscribe broker 1304 Can participate in message exchanges with other entities that use middleware. The MME108 entity in this dual-use network design can also interface with the P / S broker 1304 middleware to communicate with AF2102, as shown in Figure 21. The UE 104 can also interface with the P / S broker 1304 middleware to communicate with the AF2102, as shown in Figure 22.

The first step that can be performed when the GU CB is enabled in a particular cell is for the EMS802 to send provisioning information to the eNB 102 that provides the constraint cell, thus allowing roaming. A varied set of networks can be broadcast. The next step could be to provision each MME108 servicing a cell, so that provisioned information would not allow roaming in that cell, or only a subset of the roaming network would be constrained. Changed to indicate that it remains configured to roam in the cell.

When the allowed roaming network is changed in a cell, it is determined that it was accessed through a cell that does not allow roaming from the UE104 home network, and the UE104 attached through that cell selects a different cell. Can be done. On the other hand, one or more MME108s can search the UE104 context for each UE104 accessed through a cell provisioned as no roaming or as constrained roaming. For each UE104 whose IMSI MCC, MNC value does not match the home network, or equivalent network, or allowed roaming network, the MME108 can initiate a detach procedure and these UE104s are removed from the cell. The detachment procedure with standardized MME initiation is specified in Section 5.3.8.3 of TS23.401 v9.4.0. See Figure 23.

The next step could be for EMS802 to provision AF2102 with a Cell-Barring for Government-Use entered by a government administrator in this instance of access exclusion for government use. According to the first paragraph of this section, these parameters are Cell_ID, the lowest access class priority allowed to access the cell, or the list of high priority access class values allowed to access the cell, E911. It can include whether the call is allowed through the cell, whether biopsy is enabled in the cell, and the time interval between biopsy for UE104. It should be noted that the list of AC priority values can include values above sets 11-15 specified in the 3GPP standard, as explained in the paragraph above. The government-used CellBarred parameter can then be provisioned into a set of MME108 servicing excluded cells. Finally, the cell-providing eNB 102 can provision the CellBarred parameter for the constrained cell. These parameters are those specified in the 3GPP standard, namely the CellBarred parameter, ac-BarringFactor parameter, ac-BarringTime parameter, acBarringForEmergency parameter, and ac-BarringForSpecialAC parameter. The ac-BarringFactor can be set to zero to ensure that low priority UE104 does not access excluded cells.

When the eNB102 cell broadcasts CellBarred information, the low priority UE104 can be prevented from accessing the excluded cell.

However, low priority UE104 already accessed through the current exclusion cell needs to be detached. To achieve this, one or more MME108 servicing the excluded cell can search for a set of UE104 contexts for the UE104 accelerated through the excluded cell. The UE104 context contains an Establishment Cause parameter, which was sent by UE104 when accessing the LTE network. If the probabilistic factor does not indicate high priority, MME108 may initiate the detach procedure for UE104. See Figure 24.

If the high-priority UE104 becomes detached according to Figure 24 due to initiating its LTE attach without showing a high-priority call, it will now retouch the exclusion cell to give it a high priority. Can show LTE. The low priority UE104 cannot be accessed through excluded cells, especially if ac-BarringFactor is set to zero. Figure 24 shows that the low-priority UE104 is no longer trying to access the LTE network through the GU CB-enabled cell, and that the establishing factor is not the high-priority UE104 that was already attached. Indicates that it will be detached from. Therefore, the UE 104, which remains attached via the GU CB enabled cell, is a high priority user, but as mentioned above, these priorities may be attached via the excluded cell. It is not certain that it is high enough to allow it to be, and it may be necessary to perform a biopsy to allow it to remain attached via the exclusion cell. These aspects are not part of the LTE network's standards-based cell exclusion capability, but are part of the dual-use network's capability when cells are excluded for government use. The following process details how to place these checks on UEs that remain attached via excluded cells.

To carry out these additional checks, this dual-use network design checks the access priority of the UE 104 with the MME108 element servicing the GU CB enabled cell interacting with the AF2102. However, it may be necessary to carry out a biopsy as needed. As described herein, entities connected via the P / S broker 1304 network convey messages by tagging topics that can be strings and each public message. The message is delivered to all entities that subscribe to the topic. Therefore, the topic "AF / biometric / *" can be subscribed to when the AF2102 initializes. The "*" character indicates that any character following the second slash sign fits into this subscription topic. On the other hand, each MME108 can subscribe to the topic "AF / biometric / &lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is the globally unique MME identification information assigned to the MME108 instance. When publishing any message, the sending entity can indicate that the message is not routed back to itself, which in this case the sender subscribes to the same topic to publish the message. This is because it may have been.

For each UE 104 that remains attached through a cell with the GU CB enabled, the MME 108 servicing the UE 104 now publishes a UE accessed Check message for the topic "AF / biometric / &lt;GUMMEI&gt;". be able to. This message is received by AF2102 due to wildcard notation in topics subscribed to by AF2102. The message can include the UE104 IMSI value in addition to the cell_ID of the excluded cell. AF2102 may perform additional verification through its provisioning data that the Cell_ID referenced in the received UEaccessedCheck message is actually a cell with GU CB enabled. it can. (Otherwise, AF2102 will be referred to as the topic "AF / biometric / &lt;GUMMEI&gt;". You can publish a UE accessed Check Response message to indicate that UE 104 has passed the access check and also indicate the difference between MME108 and AF2102 provisioning data. This message is only received by MME108 sending the original UEaccessedCheck message due to the unique GUMMEI value in the topic string). Assuming the Cell_ID is for a cell with GU CB enabled, AF2102 will access the minimum access priority or cell that is allowed to access the excluded cell from its provisioning data. You can get a list of high priority access class values that you are allowed to do. One or more AC priority values may exceed the values allowed by the 3GPP standard. The AF2102 can then obtain the IMSI priority of UE104 from either its provisioned IMSI value or from an accessible database of IMSI values, and this IMSI was received in the UEaccessedCheck message. The value. The AC priority value assigned to the IMSI may exceed the AC priority value allowed by the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, AF2102 can return a UEaccessedCheckResponse message to the instance of MME108 to indicate that UE104 should be detached. Only high-priority government-approved users are allowed access to GU CB-enabled cells, allowing MME108 to initiate the detach procedure for UE104. The value received in the ccessedCheck message. The AC priority value assigned to the IMSI may exceed the AC priority value allowed by the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, AF2102 can return a UEaccessedCheckResponse message to the instance of MME108 to indicate that UE104 should be detached. Only high-priority government-approved users are allowed access to GU CB-enabled cells, allowing MME108 to initiate the detach procedure for UE104. The value received in the ccessedCheck message. The AC priority value assigned to the IMSI may exceed the AC priority value allowed by the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, AF2102 can return a UEaccessedCheckResponse message to the instance of MME108 to indicate that UE104 should be detached. Only high-priority government-approved users are allowed access to GU CB-enabled cells, allowing MME108 to initiate the detach procedure for UE104.

Alternatively, if the AF2102 places the UE104's IMSI in its provisioning data or in the IMSI database, the AF2102 retrieves the UE104's AC priority value and provisions it in the exclusion cell. It can be compared to the minimum degree or to the provisioned set of allowed high priority access class values. If the IMSI has a very low priority, or does not have a matched high priority, the AF2102 may return a UEaccessedCheckResponse message to the instance of the MME108 to detach the UE104. However, if UE104 has a sufficiently high AC priority or matches one of the allowed high priority access classes, AF2102 will check its provisioning data and enable CB for GU. It can be determined whether a biopsy is required for this cell that has been provisioned. Otherwise, AF2102 can return a UEaccessedCheckResponse message to the instance of MME108 to indicate that UE104 remains attached via the exclusion cell. If biopsy is enabled for excluded cells, the following actions may be taken before making a final decision on UE104's capabilities to keep the GU CB attached through the enabled cell: It can be performed.

The above description allows the UE biopsy application to be started when the UE is connected to the LTE network, and the UE 104 automatically populates the P / S broker 1304 instance on the optimal server 304 in the network (without user intervention). Indicates that you can connect. The UE104 software can subscribe to the topic "AF / biometric / test / &lt;IMSI&gt;", where &lt;IMSI&gt; is the unique IMSI value assigned to the UE104. The UE Biopsy App 2202 is a special purpose application loaded on all UE 104s that need access to a dual-use network in an emergency. On the other hand, the topic "AF / biometric / test / *" can be subscribed to when the AF2102 initializes. When these mechanisms are ready and the check in the previous paragraph is complete, AF2102 publishes the StartBiometricTest message to the topic "AF / biometric / test / &lt;IMSI&gt;", where &lt;IMSI&gt; serves UE104. The value received in the UEaccessedCheck message sent by the MME108. Therefore, this message is delivered by the P / S broker 1304 network to a unique UE 104 with an &lt;IMSI&gt; value, which is utilized by the UE biopsy app 2202. This message may include data such as the type of biopsy to be performed, or some other data regarding the performance of the test. Another data is to get the GPS position of the UE104, generate a periodic report of the GPS position, and let the user use the UE104 for Evolved packet system Connection Management; ECM) These reports can be continued even when trying to enter the ECM-IDLE state or when the user tries to turn off UE104. (These latter features may be required during military or other government operations.) StartBiometricTest messages can be reliably delivered by the P / S broker 1304 network. The AF2102 can activate a timer to receive biopsy data from the UE 104 in case the user chooses not to enter the data. In this case, if the timer expires, the AF2102 can send a UEaccessedChecResponse message to the MME108 to indicate that the UE104 should be detached.

When a biotest is performed on the UE 104, the UE 104 biometric app 2202 publishes a Biometric Test Results message to the topic "AF / biometric / test / &lt;IMSI&gt;", again in this case. The message is received by AF2102. AF2102 cancels the previously established timer, receives this message, and begins parsing the reply data. Depending on the type of test performed (eg, speech phrase matching, fingerprint or other biometric matching, password matching), the AF2102 can parse the data itself, or the data into another service program. Can be sent to perform analysis. This analysis reveals whether the UE 104 should remain attached through the cell with the GU CB enabled. This decision is returned to the serving MME108 when AF2102 publishes a UEaccessedChecResponse message. as a result,<u style="single">UE2102</u>Is allowed to be detached from the cell or left attached via the excluded cell. In the latter case, AF2102 can start the timer with the BiometricTestPassed parameter for the IMSI, the duration of which depends on the value of TimeBetweenBiometricTests provisioned by AF2102 for a given Cell_ID. Set.

When biopsy is enabled in a cell with GU CB enabled, whenever the UE proceeds to an initial access procedure, a service request procedure to an excluded cell, or a handover procedure to an excluded cell in an excluded cell, , Can run the test. The purpose of the timer is to prevent the UE 104 from being inspected too often. When the timer expires, the AF2102 can reset the value of the BiometricTestPassed parameter associated with the IMSI, thus allowing another biopsy to be performed on the IMSI of the UE 104. (If desired by government officials, the TimeBetweenBiometricTests value can be set to INDEFINITE to ensure that only one test is performed per UE104.)

The processing described in all paragraphs for the UE in which the GU CB remains attached via the enabled cell after the initial processing check on the serving MME 108 is shown in FIG.

UE104, which remains attached via a cell with GU CB enabled, has been validated for access priority and, in some cases, user identification information via biopsy. It is also possible for UE104, which has not yet been attached via the excluded cell, to attempt to access the cell via the initial attach LTE procedure, the service request LTE procedure, or the handover LTE procedure. Is. Such UE104 must also be checked before the GU CB is allowed to remain accessed in the enabled cell. The following section describes the actions that can be required to compensate that only properly validated UE104 remains accessed in cells excluded for government use.

(Initial access to cells with GU CB enabled) As mentioned above, UE104 with an AC priority of less than 10 when a cell is excluded for government use is generally a cell except for E911 calls (if E911 calls are allowed in the excluded cell). Do not try to access. When ac-BarringFactor is set to zero, UE104 with low AC priority can prevent attempts to access through excluded cells. Therefore, when an Initial Access Request is received by the eNB 102 via the exclusion cell, it is provided by the high priority UE 104. An Attach Request is sent from the eNB 102 to one of the MME 108s servicing the cell. LTE initial attachment procedure specifications TS 23.401 See section 5.3.2.1 of v9.4.0. If the cell is excluded for any reason other than government use, no additional processing is required, i.e., as indicated in this disclosure. However, if the cell is excluded for government use, additional processing described herein may be required.

As mentioned above, each MME108 is provisioned with a CB parameter for GU whenever one of the cells being treated is excluded for government use. Therefore, when an Attach Request from the eNB 102 is received, the MME108 that receives the Attach Request message checks its provisioning data to see if the cell being accessed is excluded for government use. Can be determined. If excluded, modifications can be introduced into the MME108 process during the initial attach LTE procedure as follows:

Multiple points in the LTE initial attach procedure that allow the MME108 to interact with the AF2102 to determine whether the UE104 should be allowed to continue the procedure or whether the MME108 should reject the attach attempt. Exists. One point can be when the MME108 first recognizes the UE's IMSI (ie, when it receives an Attach Request message from the eNB 102). Another point is when receiving UE108 subscription data from the home subscriber server (HSS120) (ie, MME108 Update Location from HSS120). When receiving an Ack message). The point at which the interaction of MME108 with AF2102 occurs does not significantly affect the design exemplified in this disclosure. (In fact, another alternative is that the HSS120 remembers the AC priority of the UE104 as a result of the IMSI subscription data, and the AF2102 determines whether the UE104 should proceed through the result of the initial access procedure. Instead, the MME108 can be made to make the decision). In the following, if the MME108 determines that the cell in which the UE104 accesses the network is excluded for government use, the AF2102 will start interacting with the reception of the Attach Request message by the MME108. See Figure 26.

To make dual-use networks easier to operate, the default APN for all UE104s in home networks and all equivalent networks (used herein to distinguish between the types of advanced wireless networks that are the subject of this disclosure). In contrast to the general purpose network, the 3GPP access point name) can be set to the APN that contains the optimal server 304 on which the AF2102 program runs. Upon receiving an Attach Request from UE104 accessing the LTE network through a cell excluded for government use, the MME108 can be programmed so that only the initial default bearer can set this default APN.

As the process in FIG. 26 shows, when the MME108 receives an Attach Request from the eNB 102, the MME108 can determine if the cell being accessed is excluded for government use. This determination is made by the provisioning information that can be sent by the government EMS802, as described above. If the cell is not excluded for government use, follow the LTE standard without modification (TS 23.401) Section 5.3.2.1 of v9.4.0) Proceed with the attach procedure. However, if the GU CB is enabled on the cell, the MME108 can publish a UEaccessCheck message for the topic "AF / biometric / &lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is the MME108. A unique ID assigned to. This message contains the UE104's IMSI and the Cell_ID of the cell being accessed. As mentioned above, this message is received by AF2102. Through its provisioning data, AF2102 can perform further verification that the Cell_ID referenced in the received UEaccessedCheck message is actually a cell with GU CB enabled. (Otherwise, AF2102 will be referred to as the topic "AF / biometric / &lt;GUMMEI&gt;". You can publish a UE accessed Check Response message to indicate that UE 104 has passed the access check and also indicate the difference between MME108 and AF2102 provisioning data. This message is only received by MME108 sending the original UEaccessedCheck message due to the unique GUMMEI value contained in the topic string. ) Assuming the Cell_ID is for a cell with GU CB enabled, AF2102 will from its provisioning data to the minimum access priority or cell that is allowed to access the excluded cell. You can get a list of high priority access class values that you are allowed to access. It should be noted that these AC priority values include values that exceed the AC priority values specified in the 3GPP standard and can implement fine-grained, high-priority access functions that can include standardized cell exclusions. I want to. The AF2102 can then obtain the IMSI priority of UE104 from either its provisioned IMSI value or from an accessible database of IMSI values, and this IMSI was received in the UEaccessedCheck message. The value. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UEaccessedCheckResponse message to the MME108 instance to indicate that the UE104 access request should be denied. MME108 can initiate a rejection response to UE104 in this case. The value received in the EaccessedCheck message. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UEaccessedCheckResponse message to the MME108 instance to indicate that the UE104 access request should be denied. MME108 can initiate a rejection response to UE104 in this case. The value received in the EaccessedCheck message. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UEaccessedCheckResponse message to the MME108 instance to indicate that the UE104 access request should be denied. MME108 can initiate a rejection response to UE104 in this case.

Alternatively, if the AF2102 places the UE104's IMSI in its provisioning data or in the IMSI database, the AF2102 retrieves the UE104's AC priority value and provisions it in the exclusion cell. It can be compared to the minimum degree or to the list of allowed high priority access class values. The AC priority value stored with the UE104's IMSI is the AC priority allowed in the 3GPP standard to introduce a finer-grained access priority class distinction than can be provided in the 3GPP standard. Note that the value can be exceeded. If the IMSI has a very low priority, or does not have a priority that matches one of the allowed values, the AF2102 returns a UEaccessedCheckResponse message to the instance of MME108 to attach the UE104. Requests can be rejected. However, if the AC priority of UE104 is high enough, or if the AC priority of UE104 matches one of the allowed values, AF2102 will check its provisioning data and this exclusion cell. It is possible to determine whether or not a biopsy is required for the. If not, AF2102 can return a UEaccessedCheckResponse message to the instance of MME108 to indicate that UE104 Attach Request processing should proceed and that biopsy is not required. If biopsy is enabled for the excluded cell, AF2102 returns a UEaccessedCheckResponse message to the instance of MME108 to indicate that UE104 Attach Request processing should proceed and that biopsy is required. Can be done.

Figure 26 shows that if Attach Request processing continues on access through a cell with the GU CB enabled, and AF2102's response to the MME108 interaction requires additional biopsy. In some cases, the MME108 can wait until it determines the IP address assigned to the UE104. This is a Create Session from SGW110 by MME108 during the LTE initial attach procedure. Response Can occur when a response is received. At this point, MME108 can publish a UEipInfo message for the topic "AF / biometric / &lt;GUMMEI&gt;", so the message will be received by AF2102. The message can include the Cell_ID, the IMSI, the IP address assigned to the UE 104, and the IP address of the PGW 114 servicing the UE 104. AF2102 can then use this information with additional provisioning data to interact with the PCRF118 feature and request that a filter policy be set on PGW114 for this UE104. The filter policy can constrain the packet to be uploaded by PGW114 or accommodated for downlink transmission across the UE104 bearer. Only uplink packets are allowed for the IP address and port number of each P / S broker 1304 instance running on the available OptServer PGW304 nodes (more than one of these server nodes at PGW114 location). Can exist, but there can be more than one P / S broker instance on each of these servers). Allowed downlink packets can only come from one of these P / S broker 1304 instances. The purpose of the filter policy is to block the communication function of UE104 until the biopsy is completed. UE104-specific software 2204 can generally attempt to connect and interface to P / S broker 1304 when the default bearer is first established. This communication is allowed by the filter policy.

Meanwhile, standardized LTE attachment procedures will be promoted for UE104, eNB102, MME108, and others. When the eNB102 sends an Attach Complete message to the MME108, it indicates that the UE104 has obtained an IP address and can start sending an uplink message. (UE104 should try to connect to P / S broker 1304, which will be allowed by the filter policy in PGW114.) MME108, Modify Bearer Upon receiving a Response (Modified Bearer Response) message, this indicates that the first downlink data can be sent to UE104. Therefore, at this point, MME108 can publish an initiateBiometricTesting message for the topic "AF / biometric / &lt;GUMMEI&gt;". The message contains the relevant UE104 Cell_ID and IMSI. The message is received by AF2102. AF2102 checks the BiometricTestingPassed variable maintained in the IMSI and does not perform a biopsy if set. Instead, AF2102 can publish a UEBiometricTestInfo message for the topic "AF / biometric / &lt;GUMMEI&gt;", thus receiving the message by the serving MME108. This message indicates that UE104 is allowed access to the cell. On the other hand, if the BiometricTestingPassed variable for IMSI is not set, the biopsy is performed as follows.

Similar to the one shown in Figure 25, AF2102 publishes a StartBiometricTest message for the topic "AF / biometric / test / &lt;IMSI&gt;", where &lt;IMSI&gt; is sent by the MME108 servicing UE104. This is the value received in the initiateBiometricTesting message. Therefore, the message is delivered by the P / S broker 1304 network to a unique UE 104 with an &lt;IMSI&gt; value, where the UE. Used by the biopsy app 2202. The message can include data such as the type of biopsy to be performed, or some other data regarding the performance of the test. Another data is to get the GPS position of the UE104, generate a periodic report of the GPS position, even when the user tries to put the UE104 in the ECM-IDLE state or when the user tries to turn off the UE104. These reports can include continuing. (These latter features may be required during military or other government operations.) StartBiometricTest messages can be reliably delivered by the P / S broker 1304 network. The AF2102 can activate a timer to receive biopsy data from the UE biopsy app 2202 in case the user chooses not to enter data. In this case, if the timer expires, AF2102 sends a UErejectAccess message to MME108, UE104. It can indicate that the attach request should be rejected. In this case, MME108 denies access to UE104, and access through the cell with GU CB enabled is denied in UE104.

, And again, this message is received by AF2102. AF2102 cancels the previously established timer, receives this message, and begins parsing the reply data. Depending on the type of test performed (eg, speech phrase matching, fingerprint or other biometric matching, password matching), the AF2102 can parse the data itself, or the data into another service program. Can be sent to perform analysis. This analysis reveals whether the UE 104 should remain attached through the cell with the GU CB enabled. This decision is returned to the serving MME108 when AF2102 publishes a UEBiometricTestInfo message. As a result, the UE 104 is denied access to the cell or is allowed to remain accessed through the excluded cell. In the latter case, AF2102 can start the timer with the BiometricTestPassed parameter for the IMSI, the duration of which depends on the value of TimeBetweenBiometricTests provisioned by AF2102 for a given Cell_ID. Set. The purpose of the timer is to prevent the UE 104 from being inspected too often. When the timer expires, the AF2102 can reset the value of the BiometricTestPassed parameter associated with the IMSI, thus allowing another biopsy to be performed on the IMSI of the UE 104. (If desired by government officials, the TimeBetweenBiometricTests value can be set to INDEFINITE to ensure that only one test is performed per UE104.)

If UE104 passes the biopsy, AF2102 can interact with PCRF118 via the Rx Diameter interface to remove previously installed filter policies on PGW114.

(Avoiding unnecessary paging (calling) in cells with GU CB enabled) Section 5.3.4.3 of TS 23.401 v9.4.0 specifies the LTE Network Triggered Service Request procedure. 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 no communication between the LTE network element and the UE 104. Since UE104 was previously in the ECM-ACTIVE state, the context is held by the MME108 instance that last served UE104. If a downlink packet arrives at UE104 in SGW110 during this state, SGW110 will send Downlink Data. Send a Notification message to MME108. The MME108 attempts to locate the UE104 by sending a paging message to one or more eNB102s that the MME108 determines are most likely to cover the area in which the UE104 resides. In a dual-use network, in transmission using a cell with GU CB enabled, the paging message may not be sent to the eNB 102 unless the UE 104 first determines that access to such a cell is allowed. It can be advantageous. Figure 27 shows changes to the network trigger service request procedure that can be effectively used in dual-use LTE networks. If the UE104 AC priority (which can be obtained from the HSS120 UE subscription data) is maintained in the UE104 context in the MME108, the initial access feasibility determination does not need to interact with the AF2102 for that purpose. It can be implemented by the logic in MME108. In Figure 27, the AC priority of UE104 is HSS120. It shows the procedure that can be used when it is not retained in the UE subscription data.

In FIG. 27, when the MME 108 receives the downlink data notification to the UE 104, it determines the set of cells to which it should send a paging message to attempt to reach the UE 104. Using the data provisioned to MME108 by government EMS, MME108 can determine a subset of these cells for which CB for GU is enabled. Using this subset of cells, MME108 can publish a UE paging Check message for the topic "AF / biometric / &lt;GUMMEI&gt;". As mentioned above, this message is received by AF2102.

For each Cell_ID in the received message, AF2102 can retrieve from its provisioning data a list of minimum or high priority access class values that are allowed to access excluded cells. .. Note that the AC priority value assigned to a cell with GU CB enabled may exceed the set of values allowed by the 3GPP standard. The AF2102 can then obtain the IMSI's AC priority for UE104, either from its provisioned IMSI value or from an accessible database of IMSI values, which is received in the UEpagingCheck message. Value. Note that the AC priority value assigned to the IMSI may exceed the value allowed by the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, AF2102 returns a UEpagingCheckResponse message to the instance of MME108 and UE104 is not sent to any of the cells received in the request message. Can be shown. The MME108 can start paging to other cells, but cannot paging to cells with GU CB enabled.

Alternatively, if the AF2102 places the UE104's IMSI in its provisioning data or in the IMSI database, the AF2102 retrieves the UE104's AC priority value and provisions the AC priority in each exclusion cell. It can be compared with the minimum degree or the list of high priority access class values allowed for each cell in the checklist. AF2102 is acceptable for a given Cell_ID if the IMSI has a very low priority for a given Cell_ID, or if the IMSI access priority does not match one of the allowed values for the cell. The UEpagingCheckResponse message can be configured to indicate no-paging-allowed. However, if the AC priority of UE104 is high enough for a given Cell_ID or matches one of the allowed values for that cell, AF2102 will check its provisioning data. , It can be determined whether biopsy is required for this excluded cell. Otherwise, AF2102 may configure a UEpagingCheckResponse message to indicate that paging is not allowed for this Cell_ID and no biopsy is required. If biopsy is enabled for a given exclusion cell, AF2102 will indicate that the paging is allowed for the given exclusion cell and that a biopsy is required in the UEpagingCheckResponse message. Can be configured. When all Cell_ID values in the request message are processed in this way, AF2102 will be referred to as the topic "AF / biometric / &lt;GUMMEI&gt;".

Upon receiving the UEpagingCheckResponse message, the MME108 uses the results obtained for each excluded cell to determine whether it can send a paging message to the eNB 102 that handles that cell. In this way, the paging message is not sent to the cell where the access of UE104 is prohibited by the CB for GU. In these cells with the GU CB enabled to which the paging message is sent, the MME108 can save the status that paging is in progress for the cell and biopsy when UE104 accesses the network through the cell. You can save the status of whether or not you need. Next, processing changes to the service request procedure to support dual use will be described.

(Automatic processing of constrained users during service requests) Section 5.4.3.1 of TS 23.401 v9.4.0 specifies the processing of the LTE network in the UE service start request procedure. As mentioned in the previous section of this specification, this procedure is also called when the UE 104 responds to a paging message.

As the process in FIG. 28 shows, when the MME108 receives a Service Request from the eNB 102, the MME108 can determine if the cell being accessed is excluded for government use. This determination is made by the provisioning information that can be sent by the government EMS802, as described above. If the cell is not excluded for government use, according to the LTE standard without modification (TS 23.401 v9.4.0 Section 5.4.1.3) Service Proceed with the Request (service request) procedure. However, if the GU CB is enabled in the cell and the service request is UE-initiated, the MME108 can publish a UESrvcReqCheck message for the topic "AF / biometric / &lt;GUMMEI&gt;". , Where &lt;GUMMEI&gt; is the unique ID assigned to MME108. This message contains the IMSI of UE104 and the Cell_ID of the cell being accessed. As mentioned above, this message is received by AF2102. Through its provisioning data, AF2102 can perform additional verification that the Cell_ID referenced in the received UESrvcReqCheck message is actually a GU CB enabled cell. (Otherwise, AF2102 will be referred to as the topic "AF / biometric / &lt;GUMMEI&gt;". You can publish a UESrvcReqCheckResponse message to indicate that UE104 has passed the access test and that no biopsy is required, and that there is a difference between the MME108 and AF2102 provisioned data. This message is only received by MME108 sending the original UESrvcReqCheck message due to the unique GUMMEI value in the topic string. ) Assuming the Cell_ID is for a cell with GU CB enabled, AF2102 will use its provisioning data to indicate the minimum access priority that is allowed to access the excluded cell, or the excluded cell. You can get a list of high priority access class values that are allowed to access. One or more AC priority values in this case may exceed the values used in the 3GPP standard, so this case provides a finer-grained distinction of priority users than in 3GPP. Please note that you can. The AF2102 can then obtain the IMSI access class priority of UE104 from either its provisioned IMSI value or from an accessible database of IMSI values, which IMSI receives in the UESrvcReqCheck message. Value. Note that the AC priority value assigned to UE104 can be greater than the set of values specified in the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UESrvcReqCheckResponse message to the serving MME108 instance to indicate that the UE104 service request should be rejected. MME108 can initiate a rejection response to UE104 in this case. Please note that it can be done. The AF2102 can then obtain the IMSI access class priority of UE104 from either its provisioned IMSI value or from an accessible database of IMSI values, which IMSI receives in the UESrvcReqCheck message. Value. Note that the AC priority value assigned to UE104 can be greater than the set of values specified in the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UESrvcReqCheckResponse message to the serving MME108 instance to indicate that the UE104 service request should be rejected. MME108 can initiate a rejection response to UE104 in this case. Please note that it can be done. The AF2102 can then obtain the IMSI access class priority of UE104 from either its provisioned IMSI value or from an accessible database of IMSI values, which IMSI receives in the UESrvcReqCheck message. Value. Note that the AC priority value assigned to UE104 can be greater than the set of values specified in the 3GPP standard. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UESrvcReqCheckResponse message to the serving MME108 instance to indicate that the UE104 service request should be rejected. MME108 can initiate a rejection response to UE104 in this case.

Alternatively, if the AF2102 places the UE104's IMSI in its provisioning data or in the IMSI database, the AF2102 retrieves the UE104's AC priority value and provisions it in the exclusion cell. It can be compared to the minimum degree or to the list of high priority access classes allowed for the cell. If the IMSI has a very low priority, or if the IMSI AC priority does not match one of the allowed access class values, the AF2102 returns a UESrvcReqCheckResponse message to the instance of MME108 for the UE104Service. Requests can be rejected. However, if UE104 has a sufficiently high AC priority or matches one of the allowed values for the cell, AF2102 will check its provisioning data and perform a biopsy on this excluded cell. Can be determined if is required. If not, AF2102 can return a UESrvcReqCheckResponse message to the instance of MME108 to indicate that UE104's Service Request processing should proceed and that biopsy is not required. If biopsy is enabled for the excluded cell, AF2102 returns a UEReqCheckResponse message to the instance of MME108 to indicate that UE104's Service Request processing should proceed and that biopsy is required. Can be done.

If the Service Request is processed, the remaining procedures specified in Section 5.4.3.1 of TS 23.401 v9.4.0 are completed. When the MME108 receives a Modify Bearer Response message from the SGW110, the standardized Service Request procedure ends, but the MME108 is dual when the GU CB for the cell being accessed is enabled. It has the following additional processing to be performed in the youth network. See Figure 28.

When the MME108 receives the Modify Bearer Response message from the SGW110 and the Service Request procedure is complete, the MME108 can check the information stored for the UE104's IMSI. If this information indicates that a biopsy should be performed, MME108 may publish an initiateBiometricTesting message for the topic "AF / biometric / &lt;GUMMEI&gt;". The message contains the relevant UE104 Cell_ID and IMSI. The message is received by AF2102 and a biopsy is done as follows.

Similar to that shown in FIG. 25, the AF2102 checks the BiometricTestingPassed variable maintained in the IMSI and does not perform a biopsy if set. Instead, AF2102 can publish a UEBiometricTestInfo message for the topic "AF / biometric / &lt;GUMMEI&gt;", thus receiving the message by the serving MME108. This message indicates that UE104 is allowed access to the cell. On the other hand, if the BiometricTestingPassed variable for IMSI is not set, the biopsy is performed as follows. AF2102 publishes a StartBiometricTest message for the topic "AF / biometric / test / &lt;IMSI&gt;", where &lt;IMSI&gt; is the value received in the initiateBiometricTesting message sent by MME108 servicing UE104. .. Therefore, the message is &lt;IMSI&gt; by the P / S broker 1304 network. Delivered to a unique UE 104 with a value, where it is utilized by the UE biopsy app 2202. The message can include data such as the type of biopsy to be performed, or some other data regarding the performance of the test. Another data is to get the GPS position of the UE104, generate a periodic report of the GPS position, even when the user tries to put the UE104 in the ECM-IDLE state or when the user tries to turn off the UE104. These reports can include continuing. (These latter features may be required during military or other government operations.) Messages can be reliably delivered by the P / S broker 1304 network. The AF2102 can activate a timer for receiving biopsy data from the UE biopsy app 2202 in case the user chooses not to enter data. In this case, if the timer expires, the AF2102 can send a UErejectAccess message to the MME108 to indicate that the UE104 should be detached from the network. In this case, the MME 108 initiates the MME start detach procedure and the UE 104 is detached from the cell where the GU CB is enabled.

Publish a Biometric Test Results message, again this message is received by AF2102. AF2102 cancels the previously established timer, receives this message, and begins parsing the reply data. Depending on the type of test performed (eg, speech phrase matching, fingerprint or other biometric matching, password matching), the AF2102 can parse the data itself, or the data into another service program. Can be sent to perform analysis. This analysis reveals whether UE 104 should remain attached via excluded cells. This decision is returned to the serving MME108 when AF2102 publishes a UEaccessedTestInfo message. As a result, the UE 104 is allowed to be detached from the cell or remain accessed through the excluded cell. In the latter case, AF2102 can start the timer with the BiometricTestPassed parameter for the IMSI, the duration of which depends on the value of TimeBetweenBiometricTests provisioned by AF2102 for a given Cell_ID. Set. The purpose of the timer is to prevent the UE 104 from being inspected too often. When the timer expires, the AF2102 can reset the value of the BiometricTestPassed parameter associated with the IMSI, thus allowing another biopsy to be performed on the IMSI of the UE 104. (If desired by government officials, the TimeBetweenBiometricTests value can be set to INDEFINITE to ensure that only one test is performed per UE104.)

(Automatic detachment 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 (ie, the eNB 102 that manages the current cell in which the UE 104 is accessed) and the target eNB 102 (ie, the eNB 102 that manages the cell in which the UE 104 is handed over). There is a direct communication path between them. If there is no direct route between the source eNB 102 and the target eNB 102, the MME 108 will be involved in the handover process prior to the handover and will use its S1 link to connect the source eNB 102 and the target eNB 102. Get ready for communication between. Therefore, this type of handover is called an S1 handover. In the X2 handover, the MME does not change, but the SGW110 element can change if the UE104 moves to a cell that is not processed by the current (source) SGW110. In the S1 handover, there can be changes (ie relocations) to the new (target) MME108, as well as possible changes (ie relocations) to the new (target) SGW110 element.

Figure 5 shows a high-level diagram of LTE handover processing. There are three separate stages of the handover procedure: the handover preparation stage, the handover execution stage, and the handover completion stage. During the handover preparation phase, the UE104 context at the source eNB102 is transferred to the target eNB102. In the handover execution stage, the UE 104 moves away from the cell in the source eNB 102 and synchronizes and accesses the cell in the target eNB 102. When the handover execution stage is completed, the uplink and downlink data can be exchanged with the UE 104. At the handover completion stage, the UE104's GTP tunnel in the SGW110 is modified, thus sending data from the SGW110 to the target eNB102 (until this is complete, this data is sent to the source eNB102 and targeted over the X2 communication path. Transferred to eNB102, where this data is queued until it can be sent to UE102 without data loss).

The X2 handover procedure is specified in Section 5.5.1.1.2 of TS 23.401 v9.4.0 in the absence of SGW110 relocation. Section 5.5.1.1.3 specifies specifications for X2 handover in the presence of SGW110 relocations. In the X2 handover, the MME 108 serves both the source eNB 102 and the target eNB 102, so there are no changes in the MME 108, i.e. there is no MME 108 relocation in the X2 handover. Section 5.5.1.2.2 of TS 23.401 v9.4.0 specifies the specification of the S1 handover case and includes the possibility of MME108 relocation as well as SGW110 relocation.

This part of the disclosure allows the UE 104 to identify changes to the processing of the MME 108 and perform dual-use network functions when the GU CB is in a handover state to an enabled cell. The point at which the MME-AF interaction in the standard procedure selected herein is initiated is another process without altering the results obtained and substantially without altering the description provided herein. Those skilled in the art will recognize that it is exemplary in that points can be selected. Also, if the AC priority of the UE104 is held in the subscription data stored in the HSS120, this point can be obtained by the MME108 when the UE104 first accesses the LTE network. It is pointed out that the check of the AC priority of UE104 against the priority allowed in the cell with CB for GU enabled can be performed by MME108 for this purpose without the need for an interface with AF2102. ..

(X2 handover in dual-use network) In the X2 handover, the MME108 first recognizes the handover when the handover completion stage begins. Target eNB 102 is LTE path switching (LTE Path) Switch) Send a message to MME108 to identify UE104 and target cell ID. Figure 29 shows the introduction of another MME108 process for running a dual-use network. Upon receiving the routing message, MME108 determines from the provisioning data whether or not the target cell has GU CB enabled. If not enabled, there are no changes to the X2 handover. However, if the target cell has GU CB enabled, the MME108 will check the context data of the UE104 held by the MME108 to see if the UE104 is making a high priority call or urgent. It is possible to determine if a call is being made (ie, check the probability factor value for UE104). If UE104 is making a normal call, or UE104 is making an emergency call, but the E911 call is not allowed in the target cell, the MME104 will fail the Path Switch Request. A Failure) message can be returned to the target eNB102 to initiate the MME start detach procedure for UE104.

If the UE104 is making a high priority call, the MME108 needs to determine if the AC priority of the UE104 is high enough to allow access to the target cell. Therefore, MME104 is a UEX2 Handover Check (UE) for the topic "AC / biometric / &lt;GUMMEI&gt;". X2 Handover Check) message can be published, where &lt;GUMMEI&gt; is a unique ID assigned to this instance of MME108. As shown herein, this message is received by AF2102. This message contains the UE 104 IMSI and the Cell_ID of the cell being accessed. Through its provisioning data, AF2102 can perform further verification that the Cell_ID referenced in the received UEX2HandoverCheck message is actually a cell with GU CB enabled. (Otherwise, AF2102 will be referred to as the topic "AF / biometric / &lt;GUMMEI&gt;". Publish a UEX2 HandoverCheckResponse message to indicate that UE104 has passed the access test and does not require a biopsy, and between the MME108 and AF2102 provisioning data. Can show the difference. This message contains a unique GUMMEI value in the topic string, so it will only be received by the instance of MME108 that sent the original UEX2HandoverCheck message). Assuming the Cell_ID is for a cell with GU CB enabled, AF2102 will access the minimum access priority or cell that is allowed to access the excluded cell from its provisioning data. You can get a list of high priority access class values that you are allowed to do. Note that the values received in this case may exceed the set of values allowed by the 3GPP standard. The AF2102 can then obtain the IMSI priority of UE104 from either its provisioned IMSI value or an accessible database of IMSI values, which is the value received in the UEX2HandoverCheck message. In this case, the AC priority value assigned to the UE104's IMSI may exceed the set of values allowed by the 3GPP standard, and the UE104's AC priority class identification that can be performed for the GU CB function is Note that the finer particle size is higher than the identification that can be performed for the standard cell exclusion function. If the IMSI is not found in the provisioning data or IMSI database, the AF2102 can return a UEX2HandoverCheckResponse message to the serving MME108 instance, indicating that the UE104 handover should fail. In this case, MME108 switches the route.

Alternatively, if AF2102 places the IMSI of UE104 in either its provisioning data or the IMSI database, AF2102 retrieves the AC priority value of UE104 and provisions it in the exclusion cell. It can be compared with the minimum priority value or the list of allowed high priority access class values. If the IMSI has a very low priority or does not match one of the allowed high priority values, the AF2102 returns a UEX2HandoverCheckResponse message to the instance of MME108 and fails the UE104 handover. The UE 104 can be detached. However, if the AC priority of UE104 is high enough or matches one of the allowed high priority values, AF2102 will check its provisioning data and perform a biopsy on this excluded cell. Can be determined if is required. If not, AF2102 can return a UEX2HandoverCheckResponse message to the instance of MME108 to indicate that the UE104 handover process should proceed and that biopsy is not required. If biopsy is enabled for the excluded cell, AF2102 returns a UEX2HandoverCheckResponse message to the instance of MME108 to indicate that the UE104 handover process should proceed and that biopsy is required. be able to.

If the X2 handover procedure is to proceed, part of this procedure is specified in Section 5.5.1.1.2 of TS 23.401 v9.4.0 until MME108 receives a Modify Bearer Response in the absence of SGW110 relocation. Continue as it is done. In the case of SGW110 relocation, part of this procedure continues as specified in Section 5.5.1.1.3 of TS 23.401 v9.4.0 until MME108 receives a Create Session Response. If the MME108 receives a Modify Bearer Response / Create Session Response message from the SGW110, the MME108 will check if a biopsy is required for the UE104 and if so, interact with the AF2102. To perform a biopsy. See Figure 29.

As shown in FIG. 29, MME108 can publish an initiate Biometric Testing message for the topic "AF / biometric / &lt;GUMMEI&gt;". This message contains the relevant UE104 Cell_ID and IMSI. AF2102 receives this message and a biopsy is done as follows:

Similar to that shown in FIG. 25, AF2102 checks the BiometricTestPassed variable maintained for the IMSI and if that variable is set, no biotest is performed. Instead, AF2102 can publish a UEBiometricTestInfo message for the topic "AF / biometric / &lt;GUMMEI&gt;" and the serving MME108 will receive this message. This message indicates that UE104 is allowed to access the cell. On the other hand, if the BiometricTestPassed variable for IMSI is not set, the biopsy is performed as follows. AF2102 can publish a StartBiometricTest message for the topic "AF / biometric / test / &lt;IMSI&gt;", where &lt;IMSI&gt; is received in the initiateBiometricTesting message sent by the MME108 servicing the UE104. The value. Therefore, the message is &lt;IMSI&gt; by the P / S broker 1304 network. Delivered to a unique UE 104 with a value and utilized by the UE biopsy app 2202. This message may include data such as the type of biopsy to be performed, or some other data regarding the test performed. Other data is to get the GPS position of the UE104, generate a periodic report of the GPS position, if the user attempts to put the UE104 in the ECM-IDLE state, or the user attempts to turn the UE104 off. It can include continuing these reports even if. (These latter functions may be required during military operations or during another government operation.) Messages can be reliably delivered by the P / S broker 1304 network. The AF2102 can activate a timer to receive biopsy data from the UE biopsy app 2202 in case the user chooses not to enter data. In this case, if the timer expires, the AF2102 can send a UE reject Access 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 start detach procedure and the UE 104 is detached from the cell where the GU CB is enabled.

When the biotest is performed in UE104, the UE biotest app 2202 publishes a Biometric Test Results message for the topic "AF / biometric / test / &lt;IMSI&gt;", again this The message is received by AF2102. AF2102 cancels the previously established timer, receives this message, and begins parsing the reply data. Depending on the type of test performed (eg, speech phrase matching, fingerprint or other biometric matching, password matching), the AF2102 may analyze the data itself or send the data to another service program. You can perform the analysis. This analysis reveals whether UE 104 should remain attached via excluded cells. This determination result is returned to the serving MME108 when AF2102 publishes a UEBiometricTestInfo message. As a result, the UE 104 is allowed to be detached from the cell or remain accessed through the excluded cell. In the latter case, the MME 108 continues the X2 handover processing procedure by sending a Path Switch Request Ack message to the target eNB 102, TS 23.401 v9.4. The rest of the processing indicated by 0 can be performed. On the other hand, AF2102 can start the timer with the BiometricTestPassed parameter for IMSI, and the duration of this timer is set by the value of TimeBetweenBiometricTests provisioned in AF2102 for a given Cell_ID. .. The purpose of the timer is to prevent the UE 104 from being inspected too often. When the timer expires, the AF2102 can reset the value of the BiometricTestPassed parameter associated with the IMSI so that another biopsy can be performed on the IMSI of this UE 104. (If desired by government officials, the TimeBetweenBiometricTests value can be set to INDEFINITE to ensure that only one test is performed per UE104.)

(S1 handover in dual-use network) S1 handover procedure is TS 23.401 It is specified in Section 5.5.1.2.2 of v9.4.0 and includes cases of MME108 relocation and SGW110 relocation. This standard shows that MME108 is involved in all three stages of the S1 handover procedure. As used herein, again, there are multiple potential points in the S1 handover process, at which point it may be appropriate to insert the additional behavior required in the dual-use network. Please note that. Regardless of the point selected in the S1 handover procedure, the outcome of these interactions must be the same, i.e., check the AC priority of UE104 and through the target cell with the GU CB enabled. It is necessary to determine if the UE 104 can remain attached and a biopsy is performed when the target cell with the GU CB enabled is configured for testing such as biotesting. FIG. 30 shows the points in the S1 handover procedure selected herein to show how additional processing can be used to implement a dual-use network.

In the S1 handover, the MME108 (or the target MME108 if MME relocation is included) first receives a Handover Notify message from the target eNB 102 to identify the target cell. Recognize. This message is sent during the handover completion stage, so the UE 104 is already in sync with the target cell and can exchange uplink and downlink data with the UE 104. As Figure 30 shows, receiving a Modify Bearer Response message from the (target) SGW110 is used to trigger additional actions required in a dual-use network. Choosing this processing point ensures that the (target) MME108 fires a timer for deleting indirect data transfer paths in case a check performed on a dual-use network results in a UE104 detachment. Will be.

When the (target) MME108 receives the Modify Bearer Response message, the MME108 can check its provisioning data to determine if the target cell has GU CB enabled. Otherwise, the S1 handover process proceeds unchanged. However, if the target cell has GU CB enabled, the MME108 will check the UE104 context data that is maintained and whether the UE104 is making a high priority call or an emergency call. It can be determined (ie, check the probability factor value for UE104). If UE104 is making a normal call, or UE104 is making an emergency call, but E911 calls are not allowed in the target cell, MME104 may initiate the MME start detach procedure for UE104. ..

If the UE104 is making a high priority call, the AC priority of the UE104 is high enough or high enough to allow the MME108 to remain accessed in the target cell. It is necessary to determine whether it matches one of the priority AC values. Therefore, MME108 can publish a UES1HandoverCheck message for the topic "AC / biometric / &lt;GUMMEI&gt;", where &lt;GUMMEI&gt; is a unique ID assigned to this instance of MME108. As shown herein, this message is received by AF2102. This message contains the IMSI of UE104 and the Cell_ID of the cell being accessed. Through its provisioning data, AF2102 can perform additional verification that the Cell_ID referenced in the received UES1HandoverCheck message is actually a cell with GU CB enabled. (Otherwise, AF2102 will be referred to as the topic "AF / biometric / &lt;GUMMEI&gt;". Publish the UES1 HandoverCheck message to indicate that no biopsy is required, that UE104 has passed the access test, that no biopsy is required, and that the MME108 and AF2102 provisioning data Can show the difference between. This message contains a unique GUMMEI value in the topic string, so it is only received by the instance of MME108 that sent the original UES1HandoverCheck message. ) Assuming the Cell_ID is for a cell with GU CB enabled, AF2102 will from its provisioning data to the minimum access priority or cell that is allowed to access the excluded cell. You can get a list of high priority access class values that you are allowed to access. Note that the AC priority value in this case may exceed the value allowed by the 3GPP standard. The AF2102 can then obtain the IMSI access class priority of UE104 from either its provisioned IMSI value or the accessible database of the IMSI value, which is the value received in the UES1HandoverCheck message. In this case, the AC priority value assigned to the UE104's IMSI may exceed the set of AC priority values allowed by the 3GPP standard, and the UE104's access priority class identification that can be obtained is standard. Note that the finer particle size is higher than the identification possible with the 3GPP cell exclusion function. If the IMSI is not found in the provisioning data or the IMSI database, the AF2102 can return a UES1HandoverCheckResponse message to the instance of the serving MME108 to indicate that the UE104 handover should fail. In this case, the MME108 is the MME start detach hand for the UE104.

Alternatively, if the AF2102 places the UE104's IMSI in either its provisioning data or the IMSI database, the AF2102 will retrieve the UE104's AC priority value and provision it in the exclusion cell. It can be compared with the AC priority minimum value or the list of allowed high priority access class values. If the IMSI has a very low priority or does not match one of the allowed values, the AF2102 may return a UES1HandoverCheckResponse message to the instance of MME108 to detach the UE104. However, if the AC priority of UE104 is high enough or matches one of the allowed high priority access class values, AF2102 will check its provisioning data and the biopsy will do this. It is possible to determine whether or not it is necessary for the excluded cells. Otherwise, AF2102 can return a UES1HandoverCheckResponse message to the instance of MME108 to indicate that the UE104 handover process should proceed and that no biopsy is required. If biopsy is enabled for the excluded cell, AF2102 returns a UES1HandoverCheckResponse message to the instance of MME108 to indicate that the UE104 handover process should proceed and that biopsy is required. Can be done.

If the UES1HandoverCheckResponse message indicates that the UE104 is granted access but does not require a biopsy, the MME108 may continue the S1 handover procedure without further modification. However, if this message indicates that a biopsy is required, the MME108 can initiate an interaction with AF2102 to perform the biopsy. See Figure 30.

As shown in Figure 30, MME108 can publish an initiateBiometricTesting message for the topic "AF / biometric / &lt;GUMMEI&gt;". This message contains the relevant UE104 Cell_ID and IMSI. AF2102 receives this message and a biopsy is performed as follows.

Similar to that shown in FIG. 25, AF2102 checks the BiometricTestPassed variable maintained for the IMSI and if that variable is set, no biopsy is performed. Instead, AF2102 can publish a UEBiometricTestInfo message for the topic "AF / biometric / &lt;GUMMEI&gt;" and an instance of the serving MME108 will receive the message. This message indicates that UE104 is allowed to access the cell. On the other hand, if the BiometricTestPassed variable for IMSI is not set, the biopsy is performed as follows. AF2102 can publish a StartBiometricTest message for the topic "AF / biometric / test / &lt;IMSI&gt;", where &lt;IMSI&gt; is received in the initiateBiometricTesting message sent by the MME108 servicing the UE. The value. Therefore, this message is sent by the P / S broker 1304 network to &lt;IMSI&gt;. Delivered to a unique UE 104 with a value and utilized by the UE biopsy app 2202. This message may include data such as the type of biopsy to be performed, or some other data regarding the test performed. Other data is to get the GPS position of the UE104, generate a periodic report of the GPS position, if the user attempts to put the UE104 in the ECM-IDLE state, or the user attempts to turn the UE104 off. It can include continuing these reports even if. (These latter functions may be required during military operations or during another government operation). Messages can be reliably delivered by the P / S broker 1304 network. The AF2102 can activate a timer to receive biopsy data from the UE biopsy app 2202 in case the user chooses not to enter data. In this case, when the timer expires, AF2102 can send a UErejectAccess message to MME108 to indicate that UE104 should be detached from the network. In this case, the MME108 initiates the MME start detach procedure and the UE104 is detached from the cell where the GU CB is enabled.

When the biotest is performed in UE104, the UE biometric app 2202 can publish a BiometricTestResults message for the topic "AF / biometric / test / &lt;IMSI&gt;", again this message is Received by AF2102. AF2102 cancels the previously established timer, receives this message, and begins parsing the reply data. Depending on the type of test performed (eg, speech phrase matching, fingerprint or other biometric matching, password matching), the AF2102 can parse the data itself, or the data into another service program. Can be sent to perform analysis. This analysis reveals whether UE 104 should remain attached via excluded cells. This decision is returned to the serving MME108 when AF2102 publishes a UEBiometricTestInfo message. As a result, the UE 104 is allowed to be detached from the cell or remain accessed through the excluded cell. In the latter case, MME108 is shown in Figure 5.5.1.2. Of TS 23.401 v9.4.0. The S1 handover process shown in 2-1 can be continued. On the other hand, AF2102 can start the timer with the BiometricTestPassed parameter for IMSI, and the duration of this timer is set by the value of TimeBetweenBiometricTests provisioned in AF2102 for a given Cell_ID. The purpose of the timer is to prevent the UE 104 from being inspected too often. When the timer expires, the AF2102 can reset the value of the BiometricTestPassed parameter associated with the IMSI so that another biopsy can be performed on the IMSI of this UE 104. (If desired by government officials, the TimeBetweenBiometricTests value can be set to INDEFINITE to ensure that only one test is performed per UE104.)

(Security protection of government bases using access exclusions and roaming restrictions) In some situations, it may be desirable to allow only a limited set of users to access cells that provide coverage for government controlled areas or bases. One method that can be used is to assign all cells that provide RF coverage for the base to a limited subscriber group (CSG). The CSG is then broadcast in one of the system information blocks sent periodically by each cell. Only UE104, whose SIM is configured with a specific CSG value associated with each of the cells, is allowed to access these cells. This technique may have the following blind spots or problems: An invalid user could access the cell's CSG value (simply by monitoring the system information sent by the cell) and set this CSG value in the user's SIM card. As a result, these invalid UE 104s can access the cell. Second, it may be necessary to grant access to people who are not normally present at the base station, and thus those who do not have a UE 104 configured for a particular CSG. Due to these issues, it is desirable to use another method of restricting access to cells that cover government bases. The cell exclusion and roaming restrictions described in this disclosure can provide an effective alternative to allow restricted access.

Roaming can be used as the first line of defense against unauthorized access to cells covering government bases. Each of the cells can provision a set of authorized roaming networks covering government users who are authorized to access these cells. Also, the roaming list can be a blank list, so that only UEs from the home network belonging to the cell and UEs from the set of equivalent networks belonging to the cell are allowed to access these cells. In this case, all government users may have a UE104 with an IMSI in one PLMN (MCC, MNC), where members of different government agencies are members of different agencies. It can be distinguished by using different IMSI ranges. Alternatively, as mentioned above, members of different government agencies can be assigned IMSI values in different equivalent networks.

Cells that provide RF coverage for government bases can also be placed in one or more tracking areas (TAs) that contain only specific cells that cover government bases. Through provisioning data, the MME108 in the LTE network that processes between neighboring cells covering the government base can send a handover regulation list containing the TA containing the cells covering the government base. This handover regulation list can then be delivered to all UE 104s that are ineligible for access to cells covering government bases. This list can also be delivered to all UE104s on neighboring cells that are not allowed access to cells covering government bases for another reason. These UE104 handovers are prohibited if the target cell is a cell that covers a government base.

Access to cells covering government bases can also be further restricted by introducing cell exclusions for government use in these cells. In this case, the UE 104 that can access these cells must be a high priority UE 104. Next, the functions described above in the present disclosure can be applied to the GU CB. Therefore, the validation check of the UE104's AC priority value against the UE104's IMSI and the access priority allowed in the restricted cell is deployed by an entity separate from the UE104 (ie, by the MME108 or within the LTE network). It can be run (by AF2102 running on the optimal server). Further, the user identification information can be verified via the biopsy described above in the present disclosure. These checks and biopsy are performed as described herein.

(APN LTE network that acts as a platform for sensor data collection, processing, storage, and distribution) Government and commercial applications are increasingly using all types of sensors to collect information. Sensors can include image capture devices, video capture devices, audio capture devices, scanning devices, chemical detectors, smoke detectors, and more. The sensor can be held on an airborn drone or manned aircraft, or can be deployed on the ground in a mobile vehicle or robot, or at a fixed point such as a ramp post, in a building or on a building, in a supermarket. , And in other shopping areas, such as mobile phones carried by various users. It can be recognized that the amount of data collected by the sensor in various applications is increasing rapidly. Sensor data needs to be collected and transmitted to points where the data can be stored and processed. Depending on the application, data from a variety of sensors of the same type or different types must be analyzed together to produce results or produce tertiary data, and then for further processing or decision making. It may need to be delivered to one endpoint or multiple endpoints. Radio technology can provide a useful method of acquiring and transporting data collected by sensors. However, the amount of data that a particular sensor-based application needs to collect can exceed the capacity of current wireless networks. Moreover, wireless networks capable of efficiently and quickly acquiring, processing, storing, and distributing sensor data are not available. Such capabilities are referred to herein as characteristics of the sensor platform.

The system described herein utilizes additional concepts in addition to the aspects of the APN LTE wireless network presented in the previous section of this disclosure to generate the sensor platform outlined in the previous paragraph. These aspects include faster data capacity available using APN network beam forming technology and the ability to co-locate the optimal server 308 with the eNB 102 element near a wireless access point consisting of a large collection of sensors. Ability to collect and distribute sensor data between large sets of endpoints in an efficient manner using Publish / Subscribe1304 communication in APN LTE wireless networks, and optimal servers 304 and 308 as storage and analysis processing points for sensor data. Can include the ability to use. A large collection of sensor-based applications can be built using these capabilities, as will be apparent in the following exemplary scenarios exemplifying this disclosure. For those skilled in the art, the examples presented herein are APNs in providing a sensor platform. It is an illustration of the output and applicability of LTE wireless networks, and it is understandable that many other sensor-based applications can be built using the features described herein.

(Data processing from optimal servers and various sensors using Publish / Subscribe messaging) Figure 13 shows how the Publish / Subscribe (P / S) broker 1304 middleware messaging system can be used to provide a means of interconnecting different sets of endpoints, and in this case, these. The endpoint can be a diverse set of sensors, a computer program for processing and storing sensor data, and user terminals and devices capable of receiving the results of sensor data processing and data distribution. According to the techniques disclosed in the previous sections of this disclosure, publishing to endpoint 1308 and subscribing to endpoint 1310 do not interact directly with each other and are therefore separated. This decoupling allows an entity (eg, a sensor, processor, user terminal) to add to or network with data transmitted or received without affecting the behavior of either Publisher 1308 or any Subscriber 1310. It offers the advantage of being able to remove from. Every communication entity can have one connection to the P / S broker 1304 network, through which it can send to or receive from many other endpoints. Publisher 1308 can send a single packet, and the P / S broker 1304 middleware takes a copy of any of the packets needed to reach a large number of subscribers 1310. Therefore, the system is efficient and can operate in a simpler way than when using other communication architectures.

Figure 14 illustrates an exemplary deployment of P / S broker 1304 instances on a set of optimal servers 304 and 308 that can be deployed in an APN LTE wireless network. At least one OptServer_eNBNote that the 308 is associated with each eNB102 network element. In addition, OptServer_PGWThe 304 can be associated with a PGW 114 servicing a user accessing through the eNB 102 element. Further, the teaching in this disclosure is how the UE bearer 302 is redirected in the eNB 102 and the OptServer associated with the eNB 102._eNBDescribes whether it can be connected to 308. This procedure is for OptServer_eNBIt can give UE104 a short route that allows it to reach the services provided by 308 and in particular allow UE104 to connect to an instance of P / S broker 1304 that can run on this server 308. In addition, the use of redirected bearer 312 can result in reduced or eliminated resource usage of backhaul 112 when sending data to or receiving data from UE 104. This also means that the server is associated with the eNB 102 servicing the UE 104 OptServer._eNBWhen running on the 308, the delay that can occur when sending data from the server program to or receiving data from the UE 104 can be minimized. In this case, the UE 104 can be a sensor, or a user terminal that controls a sensor that can display sensor data or connect via this type of LTE wireless network. The number of sensors that can be connected to the network can be increased, especially if the beamforming system referred to in the present disclosure is used in the eNB 102 element to increase the system communication capacity. Many sensors can be connected to the LTE network at each eNB 102 element.

Over the past few decades, several universities around the world have been involved in the specification and construction of service architectures for collaborative audio and video conferencing. This type of service, to be precise, is to support sensors deployed to serve the military in the field, to assist emergency workers in disaster situations, or to include sensors. It can be required to support many types of commercial services. Collaborative audio communications may be needed by those involved in emergencies or military operations. Video streams can be generated by sensors and need to be delivered to groups of people who need information to improve their decision-making ability and notify them before making their next move. In some cases. Similarly, a large collection of images captured by the sensor needs to be stored and thus sent later to users who need to make decisions based on the image content. APN The ability of sensors to interact with users in conference configurations using P / S broker 1304 middleware in LTE wireless networks may facilitate the need for storage, processing, and distribution of applications that include sensors. These services can, of course, be extended to the commercial realm, but individual-to-individual or sensor-to-individual communications may be used more frequently than conferencing services. However, the conference service has its significance in the commercial domain, and the communication of the P / S broker 1304 can promote the operation of the conference service. On the other hand, individual-to-individual or sensor-to-individual communications can also be efficiently processed by using the P / S broker 1304 middleware as shown in this disclosure.

Figure 31 shows the minimal set of features that can be needed to set up and manage multimedia conferencing services using the P / S Broker 1304 middleware for communication. In Figure 31, these features are APN It shows how it can be distributed across a set of optimal servers 304 and 308 that can be deployed in an LTE wireless network. The conference repository 3110 is a set of IMSI values for users 104 who are granted access to the conference, the role of each user 104 in the conference (eg, certain types of sensors, general participants, moderators, speakers, listeners). , And a list of scheduled meetings, along with meeting start and end times. Conference Manager 3102 manages the start and end of a conference, the addition or removal of certain types of sessions (eg audio, video, alarms) by interacting with Session Manager 3104, and the orderly use of conference resources by participants. It can be performed. The session manager 3104 can interact with the media server 3108 to start and remove media types from the conference. The media server 3108 can provide services specific to various types of media. Session manager 3104 is an interface point for sensors, devices, and user 104 who wish to participate in a particular session related to the conference in which the endpoint (sensor, device, or user 104) was attending.

The general concept presented in Figure 31 is a platform for optimal servers 304 and 308 and associated P / S broker 1304 communication middleware to receive, process, store and redistribute sensor data in LTE wireless networks. It can be used as. The conferencing function is needed to facilitate the implementation of distribution and collection functions, depending on the application, and can serve to organize sensors, processing, and end-user resources into one application. Another feature required by a particular sensor application can be deployed in a set of optimal servers 304 and 308 to connect to the P / S broker 1304 system. There are no restrictions on the types of features you can add. The following subsections of this disclosure describe a set of additional features, such as Image Server 3302 and Alarm Server 3304, that receive, process, store, and redistribute sensor data as part of a particular application. Including these features is an APN It serves as an example of how LTE wireless networks can function as a platform for building sensor applications.

The deployment of these sensor services can be based on Optimal Server 304 associated with PGW 114 or Optimal Server 308 associated with eNB 102. This choice can depend on the position of the sensor as well as the position of the human and machine participants in the sensor application. Significant savings in bandwidth utilization on network communication links 112 and 704 and / or endpoints by selecting the appropriate servers 304 and / or 308 to perform the function, as shown in the subsections below. It can bring about a significant reduction in the delay in acquiring information with and from.

(Example of emergency application including sensor) This exemplary sensor application can serve to illustrate how the features built into the APN LTE wireless network can be used as a platform for building sensor-based applications. This example highlights and illustrates how the sensor platform can be used with a diverse set of sensor functions.

In the event of a disaster, the wireless infrastructure needed to meet the communication needs of emergency response personnel is often destroyed along with other infrastructure. Utilizing the expanded data capacity of APN Beam Forming Technology and the application of Optimal Servers 304 and 308 Technology in APN Networks, LTE radio capabilities can be restored across areas that emergency response personnel must operate. it can. In addition, it leverages the deployment of Publish / Subscribe broker 1304 message delivery middleware and associated conferencing software sets to support the collection, analysis, and delivery of sensor data essential to the safety of response personnel and successful emergency operations. be able to. The details provided in the present disclosure can indicate how to address these aspects. Multimedia conferencing capabilities are also important for response teams and for staff located away from the operational area at the command post. The ability to co-locate the service application with the eNB102 element saves backhaul 112 usage and minimizes delays in providing information to the response team. The following exemplary scenario shows how an APN network can be used to meet these critical requirements of an emergency response application.

An exemplary scenario demonstrating the use of APN LTE wireless networks as a sensor platform is when a wireless infrastructure is deployed in a disaster area. Therefore, the eNB102 element and OptServer_eNBAn unmanned aerial vehicle (UAV) 708 is used to deploy the 308 element on the disaster ground. In this exemplary scenario, the UAV-based APN network deployment shown in Figure 32 can be used. It is assumed that the single eNB 102 held by the UAV708 is sufficient to cover the emergency operation area. Figure 32 shows the use of a second UAV710 to hold the components (MME108, SGW110, and PGW114) of the Enhanced Packet Core (EPC), but for those skilled in the art, from eNB102. Communication to ground-based EPCs is understood to be another viable deployment option.

Table 7 shows key stakeholders and features that handle aspects of an exemplary scenario of emergency response operations involved in communications, and shows where each feature is deployed in the architecture. .. The functional architecture for this scenario is shown in Figure 33. The deployment architecture for this scenario is shown in Figure 34 (for those skilled in the art, not all service features listed in Table 7 are shown in Figure 34 due to lack of drawing space. Please understand).

Table 7: Stakeholders, deployments, and descriptions of exemplary emergency response scenarios, including sensors.<img id="000014" he="203" wi="152" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000015" he="109" wi="160" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000016" he="171" wi="157" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000017" he="203" wi="158" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000018" he="156" wi="150" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000019" he="161" wi="157" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

OptServer located over the emergency response operation area_eNBDue to the deployment of media server 3108 on 304, all audio and video data streams are mixed and delivered to each of the first response personnel team members 3310 with little use of the backhaul 112 interface. can do. Audio data streams from each of the first response personnel 3310 are OptServers associated with eNB_2 102 covering the production area via a redirected dedicated bearer 312._eNBCan be routed to 308. The audio stream is mixed on the media server 3108, so that concurrent packets from different users' audio streams can appear in a single audio data stream received by each participant 3308 and 3310 from the media server 3108 (individually). Packets sent by user 3308 or 3310 are not mixed into the audio stream returned to this user). Media server 3108 runs, UE3310 and OptServer_eNBBackhaul 112 is not used in this interaction due to the use of redirect bearer 312 to carry data to and from 308 (see Figure 3 for the meaning of redirect bearer 312).

If UE3308 located at the command post participates in conference audio session 3324, audio packets from UE3308 will be sent to PGW114 via wireless backhaul 112 via P / S broker 1304 associated with eNB_1 102. It can be routed to the associated P / S broker 1304, to the P / S broker 1304 associated with eNB_2 102, and to the media server 3108. The audio stream generated and mixed by the media server 3108 with respect to the UE 3308 can be routed via the reverse route. Therefore, less packet delay can be achieved for the first response personnel team member 3310, and less backhaul 112 can be used as a whole than when using the conventional architecture.

Image Server 3302 is an OptServer associated with eNB_2 102_eNBCan be deployed on 308. Therefore, the images collected by the first response personnel team member 3310 can be stored without using the backhaul 112. Since each image is a large file, the savings in backhaul 112 have a significant impact on this architecture. When the image is uploaded, the image processing application on the UE3310 can tag the image with date, time, GPS coordinates, and user comments. By interacting with the image server 3302, any UE3308 or 3310 in operation can obtain a list of images filtered by criteria set by the user. In this way, any user can see any of the large collections of detailed images that can be recorded during team operation. In this case, due to the architecture of APN Optimal Servers 304 and 308, the images downloaded to UE3310 or 3308 will be OptServer with a slight delay._eNBComing from 308, images can be sent to first response team member 3310 without using the backhaul 112. See Figure 34.

Using the UAV 708 and 710 deployed across the operational area, the first response personnel team member 3310 approaches the disaster area, mounts the payload of its fixed sensor 3312 on the mobile robot 3314, and turns on the mobile robot 3314. can do. Response personnel Team members 3310, command posts 3308, and robots 3314 equipped with their video sensors can all participate in multimedia conferences. In this scenario, only Robot 3314 can send a video stream. The robot 3314 does not receive video, but has a control channel 3332 for receiving commands related to movement and commands related to the control of the fixed sensor 3312 carried by the robot 3314. The video stream 3314 of the mobile robot's sensor can be displayed on the display of the command post 3308, which uses the communication control channel 3332 to further direct the robot to the disaster area. Based on the video stream from the particular robot-mounted sensor 3314, the payload of the fixed sensor 3312 can be accurately placed and turned on on the ground. The software / firmware in this fixed sensor 3312 connects to the LTE network and then to the P / S broker 1304 to locate the fixed sensor data analysis service 3304 and itself and its function (eg, fire detection). , Sound detection, chemical substance detection, motion detection) and GPS position coordinates can be notified. OptServer_PGWThe fixed sensor data analysis service program 3304 running on the 304 (in this example) can collect and analyze the data sent from each fixed sensor 3312 and based on the data received from the fixed sensor 3312, an alarm. Can be generated. All participants UE3310 and 3308 subscribe to receive the alarm data stream 3330.

On the other hand, all participants UE3310 and 3308 can communicate via an audio conferencing setup and source the video from any of the robot-mounted sensors 3314 or from the video played by the first responder 3310. You can choose. Based on the needs of the first responder 3310, the robot 3314 can receive commands to move in a particular direction. This command can come from either Command Post 3308 or First Response Team Member 3310. As an example, a robot 3314 near the area of this fixed sensor 3312 can be directed to "investigate" the alarm generated by the data from the fixed sensor 3312. Also, the video stream produced by the first responder UE3310 will be available to all conference participants 3308 and 3310 via the conference video session feature. Conference participants 3308 and 3310 may have the ability to select a video data stream from a list of all entities in the conference for display, but this entity is available via image grabber 3322. To generate video data. Similarly, images taken by the response team's mobile device 3310 can be selected for display on any participant's UE3308 or 3310.

The following subsections of this disclosure describe how multimedia conferences can be set up to enable audio and video communication among all conference participants, and how video streams from the mobile robot-equipped sensor 3314 can be set up. Whether it can be made available to all participants 3308 and 3310, how alarm notification messages can be made available to participants 3308 and 3310, and how the command post user 3308 controls the movement of the mobile robot 3314. And provide details that can be understood by those skilled in the art as to how the control channel can be set up to allow the mobile robot 3314 to control the exact location of the fixed sensor 3312. The interaction between the devices of Participants UE3308 and 3310 and the image server 3302, as well as the interaction between the fixed sensor 3312 and the fixed sensor data analysis server 3304, is outside the scope of the multimedia conference. The interaction of the image server 3302 with the fixed sensor 3312 and the interaction of the fixed sensor data analysis server 3304 will also be described in the next subsection of this disclosure.

(Multimedia conference setup) The conference manager application 3102 can be associated with the conference registry 3110. The data about each meeting stored in the registry 3110 includes the following information: meeting name, meeting ID (determined by meeting manager 3102 when the meeting becomes active), start time, end time, attendees: You can have a list, a moderator ID, a list of roles and features, and a template for each session you can choose for this meeting. A field in each session template can indicate whether the session should be activated by the conference manager 3102 when the conference is started. Attendees cannot join a session until it is active, and once the meeting begins, any participant 3308, 3310, or 3314 can dynamically activate the session. In this scenario, the conference manager 3102 initiates all sessions based on the information in the "emergency action" conference registry 3110. The conference manager 3102 can also generate a topic set for use in the publish / subscribe communication mechanism for all operations required for a conference. Conference Manager 3102 can generate and deliver different topics as each participant 3308, 3310 or 3314 joins a session, thus allowing participants to receive a unique and appropriate view of conference data. it can.

The information in Registry 3110 can be generated by any UE 104 authorized to set up future conferences, but may also be set up by Element Management System 802. In this scenario, it is assumed that the entry in Registry 3110 in the "Emergency Actions" meeting has already been set up when emergency operations need to be started.

UE3308, 3310, and 3314 may join and leave the conference at any time. UE3308, 3310, and 3314 are active for the conference and join or leave any, all, or subset of sessions 3324, 3328, 3330, and 3332 that the UE is allowed to join. it can be Ru. Therefore, in this emergency scenario, the number of participants 3308, 3310, and 3314 can change dynamically. For example, one or more robots 3314 can be disabled, replaced by a new robot, or added to operation as needed.

Table 8 can show some of the information that Registry 3110 can contain for "emergency" meetings before and after the meeting becomes active (like the meeting ID, as well as a list of active sessions and their topics. Some entries can be made after the meeting has started). These entries can be created by the conference manager 3102 when the conference begins, but by any entity (eg, EMS802 or user) before the conference begins.

Table 8: Emergency Measures Meeting Parameters<img id="000020" he="229" wi="153" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000021" he="171" wi="150" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000022" he="156" wi="145" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

See FIGS. 35, 36, 37, and 38 for the following explanation of how a conference can be initiated and manipulated. These drawings omit the use of the P / S broker 1304 network to simplify the drawing, but those skilled in the art will appreciate the messaging interaction through the operation of the P / S broker 1304 middleware system. It will be clear that it will be done.

Figure 35 shows how a meeting can be initiated. Registry 3110 contains an entry for an emergency response meeting that indicates that the meeting will start immediately, so that the conference manager 3102 can be notified when registry 3110 is created. Conference Manager 3102 can start a conference, assign a ConfID to the conference, and subscribe to the topic: ServiceControl / ConfSvc / EmergencyAction / &lt;confID&gt;. The &lt;confID&gt; can embed a unique ID assigned to this conference manager 3102, as opposed to any other instance, so messages related to this conference will be sent to the P / S broker 1304 network. Is routed only to this instance of Conference Manager 3102.

The conference manager 3102 determines the session that needs to be started from the registry 3110 information, publishes the Service Inquiry to the topic ServiceInquiry / ConfSession / &lt;ConfMgrID&gt;, and locates an instance of session manager 3104. It can be specified, where &lt;ConfMgrID (Conference Manager ID)&gt; can be a unique ID assigned to this instance of Conference Manager 3102. All instances of Session Manager 3104 can subscribe to the topic ServiceInquiry / ConfSession / * to receive these queries. In this case, there is only one instance of Session Manager 3104, so Conference Manager 3102 is one Service that sends a SessMgrID (Session Manager ID) that is unique among all instances of Session Manager 3104. Description (service description) You can receive replies. Session manager 3104 can subscribe to a unique control channel (ServiceControl / ConfSession / &lt;SessMgrID&gt;) that is outside the scope of any particular conference. If each communication entity has a unique ID assigned to the other entity, the conference manager 3102 and session manager 3104 can exchange messages over the P / S broker 1304 network.

The conference manager 3102 can publish a message to the session manager 3104 indicating the start of an emergency meeting and can provide a list of sessions that need to be started. In addition, topics related to each session can be included in the information passed to Session Manager 3104. In this case, audio session 3324, video session 3328, alarm session 3330, and robot control session 3332 can be activated. Due to the activation of audio conferencing session 3324 and due to the activation of video conferencing session 3328, session manager 3104 locates media server 3108 for audio to conference participants. Mixer 3318, Video Mixer 3320, and Image Grabber 3322 features need to be reserved and started, so they will be available when each participant joins the corresponding session.

The location of the media server 3108 is the Service Inquiry published by the session manager 3104 for generic topics subscribed to by all instances of the media server 3108 (in this example, there is only one instance) and the session manager. It can be related to the Service Description response returned to the topic that becomes unique by adding the unique ID of the 3104 instance. This reply contains a unique ID assigned to an instance of media server 3108, after which the two instances communicate over the P / S broker 1304 network to set up media processing for audio and video sessions. can do. The resource availability of Audio Mixer 3318, Video Mixer 3320, and Image Grabber 3322 is the Service generated by Media Server 3108. It can be included in the Description response, so the Session Manager 3104 can choose from several media servers 3108 if there are more than one instance available in the network. Therefore, the topic subscribed to by Session Manager 3104 for an audio session in this conference can be ServiceControl / ConfSvc) / EmergencyAction / &lt;confID&gt; / &lt;SessMgrID&gt;. The topic subscribed to by Media Server 3108 for an audio session in this conference can be ServiceControl / ConfSvc / EmergencyAction / &lt;confID&gt; / audio / &lt;MediaServerID&gt;. Audio mixer resource 3318, video mixer resource 3320, and image grabber resource 3322 can be reserved on an instance of media server 3108 for emergency response meetings. Here, the emergency response meeting is in an active state. The conference manager 3102 can return an Acknowledgment (acknowledgment) to the registry 3110 to indicate the start of the conference and can provide the registry 3110 containing the ConfID assigned to the conference. This value must be passed to each participant to allow them to attend the meeting.

Figure 35 shows the above-mentioned interaction for initiating an emergency response meeting. As mentioned above, the use of P / S broker 1304 to route these messages is not shown in Figure 35 for simplicity. Therefore, the reader should be understood as demonstrating each interaction shown in Figure 35 to include the routing of P / S broker 1304. Note that point-to-point connections are only connections between entities (eg session manager 3104, media server 3108, sensors 3314) and P / S broker 1304. There is no explicit connection between communication service entities, sensors, or participant UEs. Also, any message sent is actually published to a topic, and any message received is a subscription to a published topic. The topics available in this scenario can be found in Table 8.

(Participation in participants' meetings and sessions) See Figure 36 for a description herein of how an entity can participate in authorized meetings and sessions. Each conference participant UE3308, 3310, and each sensor 3314 must communicate with the conference manager 3102 to join the conference. In this and other conference controls, the conference manager can subscribe to the topic: ServiceControl / ConfSvc / EmergencyAction / &lt;confID&gt;. Therefore, the participant's device needs to get both the conference name and the &lt;confID&gt; before it can publish the request to join the conference. The meeting name can be provisioned on the participant's device, but the &lt;confID&gt; cannot be provisioned because it is assigned by the meeting manager 3102 when the meeting starts. This operation improves the degree of security for the conference participation procedure.

If user 3308, 3310, or 3314 chooses to join the conference, UE3308, 3310, or 3314 can publish Service Inquiry to the topic ServiceInquiry / ConfSvc / Registry / &lt;IMSI&gt;, where &lt;IMSI&gt; is a unique value assigned to the UE. All instances of Registry 3110 can be subscribed to the topic ServiceInquiry / ConfSvc / Registry / *, so messages in UE3308, 3310, or 3314 will be sent to all instances of Registry 3110 by the P / S broker 1304 network. Can be routed to. Service published by an instance of registry 3110 The Description response message may include a unique IMSI of this UE3308, 3310, or 3314 within the topic to allow the response to be routed to a particular UE3308, 3310, or 3314. The ServiceInquiry message can include the conference name (emergency action), so Registry 3110 can respond if it has information about this conference. In this example, there is only one registry 3110, so it is possible to return only one Service Description response message to UE3308, 3310, or 3314. This message contains the unique ID of Conference Manager 3102 and information about the emergency meeting, including &lt;confID&gt;. (In this case, the conference name can be provisioned to sensors 3314 and other UEs 3308 and 3310 that need to attend the conference.)

Here, UE3308, 3310, or 3314 may publish a participation message regarding the emergency response meeting to the conference manager 3102. The list of attendees available to the conference manager 3102 can allow the conference manager 3102 to approve UE3308, 3310, or 3314 for the conference. Since a join can have information about the role of UE3308, 3310, or 3314, the conference manager 3102 can determine the set of sessions that UE3308, 3310, or 3314 can join, and in the Acknowledgment for the Join request. The session list can be sent to UE3308, 3310, or 3314. In this way, UE3308, 3310, or 3314 can display all sessions in which UE3308, 3310, or 3314 can participate. The conference manager 3102 as the session initiator sends an Invite () (invitation) message to UE3308, 3310, or 3314 for each session in which UE3308, 3310, or 3314 can participate. UE3308, 3310, or 3314 cannot join a session without first receiving Invite () from the session initiator, which can be conference manager 3102 in this scenario.

In another conference situation, the user can choose which session to join. In this case, UE3308, 3310, or 3314 can be programmed to automatically participate in these sessions associated with that role. Thus, the command post personnel UE3308 and the first responder UE3310 can accept Join Invite () for sessions of audio 3324, video 3328, and alarm 3330, and robot control 3332. The robot-mounted video sensor 3314 can accept Join Invite () for video session 3328 only, which is capable of sending / publishing video but not receiving video. Fixed sensor 3312 is not a conference participant in this exemplary scenario. The fixed sensor 3312 can only publish its data to the topics shown in the next subsection, and the fixed sensor data analysis service 3304 subscribes to this topic.

When UE3308, 3310, or 3314 publishes a request to join a session (for example, for video session 3328: ServiceControl / ConfSvc / EmergencyAction / &lt;confID&gt; / video), conference manager 3102 receives this request and UE3308. , 3310, or 3314 can determine whether this request can be granted, and if so, conference manager 3102 has one or more to assign to UE3308, 3310, or 3314 for the session. Can generate topics for. For example, participation in audio session 3324 can generate two topics. One is for the UE 3308 or 3310 to use to publish its audio stream. The other is for the UE 3308 or 3310 to subscribe, which can receive the audio stream mixed by the audio mixer 3318 on the media server 3108 and sent to the UE. The mixed audio stream has co-occurring audio packets generated by all UE participants except the UE that receives the stream. In this scenario, the robot-mounted sensor UE3314 does not participate in audio session 3324.

For video session 3328, two topics can be generated for the UE of first responder 3310 and command post 3308. Only one topic can be generated for the UE of the robot-mounted sensor 3314. UE3308, 3310, or 3314 can use the first topic when publishing its video stream. A second topic, if generated, could be for the UE 3308 or 3310 to subscribe to receive the mixed video stream produced by the video mixer 3320 on the media server 3108. Again, the mixed video includes a video stream generated by all video generation sensors and UEs 3308, 3310, or 3314 of all participants except the receiving UE. (In fact, it is possible to send a series of captured images, ie images from each participant 3308 and 3310 and sensor stream 3314. When the user selects a particular video stream, the selected participant UE3308 Alternatively, only the video stream from 3310, or sensor 3314, can be sent to request UE3308 or 3310.)

For alarm session 3330, one topic can be generated and UE3308 or 3310 subscribes to this topic to receive the alarm. Only the UEs of the first responder 3310 and command post 3308 can participate in the alarm session, and most likely the same alarm topic can be assigned to all UEs 3308 and 3310 participating in the alarm session. The alarm generation function of the fixed sensor data analysis 3304 publishes this alarm once, and all UE3308 and 3310 subscribing can receive this alarm.

Two topics can be generated for robot control session 3332. One can be used by the UE 3308 or 3310 to publish robot control commands. The other can be used by the UE 3308 or 3310 to subscribe to receive the robot's response to this command.

If there is a change in the participant list for each session, the conference manager 3102 can publish the updated session participant list, so that each UE 3308 and 3310 participating in this conference session will have this list. To receive. According to Table 8, all UE3308 and 3310 participating in the session whose name is "sessionName" subscribe to the topic: ServiceControl / ConfSvc / EmergencyAction / &lt;confID&gt; / &lt;sessionName-Notify&gt;. And receive a session participant change notification for this particular session (for example, in video session 3328, the last part of the topic string can be "video-Notify").

The topic generated by Conference Manager 3102 may not be a string and may be an 8-byte number. Streaming audio 3324 and video 3328 requires low latency, thus avoiding the use of string topics and reducing the time the P / S broker 1304 network spends determining the routing of these packets. can do. Since the conference manager 3102 handles the topic generation, the uniqueness of the topic can be guaranteed. When UE3308, 3310, or 3314 joins a session, the conference manager 3102 needs to generate a topic, which can be sent to UE3308, 3310, or 3314 and then to session manager 3104, said session. Manager 3104 processes the publishing of this topic to the media server 3108, where audio and video streams from the UE are collected and the mixed streams 3324 and 3328 are published. When alarm session 3330 occurs, conference manager 3102 can send topics to fixed sensor data analysis service 3304, as well as UEs 3308 and 3310 participating in alarm session 3330. In robot control session 3332, the topic is sent to robot participants 3314 who participate in robot control session 3332 (in this scenario, all robot participants 3314 do this), and UE3308 and 3310 who participate in robot control session 3332. Can be done.

On the other hand, the first responder UE3310 and the command post personnel UE3308 can display all sessions available to the user, as well as sessions that the user may have attended.

FIG. 36 shows the message interactions that can occur when UE3308, 3310, or 3314 joins a conference and then joins one or more sessions. In FIG. 36, again, the routing and interaction of P / S broker 1304 is omitted to simplify the message flow diagram. Figure 36 does not show all session participation for UE3308, 3310, or 3314 in order to maintain a limited number of interactions. Readers of ordinary skill in the art will recognize that all sessions required by a particular UE type can be attended in the manner shown in FIG.

If UE3308, 3310, or 3314 participates in all of its sessions, it may participate in all services authorized to UE during the conference. Here, a UE 3308 or 3310 that participates in audio session 3324 can publish its audio packet to a topic that is received in a Join (audio) interaction. The UE can also receive an audio stream 3324 mixed through an audio topic that is currently subscribed to for that purpose. In this way, user 3308 or 3310 is in the state of an audio conference with any other user 3308 and 3310 in audio session 3324. Similarly, the UE 3308 or 3310 can display captured images of each video stream in the conference video session 3328, including those of the robot-mounted sensor 3314 and the first response personnel team member 3310. When the user 3308 or 3310 selects one of the captured images on the display, the UE 3308 or 3310 can send a control message to the conference manager 3102 to select a particular video stream. The conference manager 3102 can send a command to the session manager 3104 to notify the media server 3108 to stop sending the mixed video stream for the topic to be published to this UE 3308 or 3310. Conference manager 3102 can publish the selected video stream by returning the topic number used by another UE3308, 3310, or 3314 to UE3308 or 3310. The requesting UE3308 or 3310 can subscribe to the topic and start receiving the selected video stream. In this way, the first response personnel 3310 or command personnel 3308 meet. You can receive a video stream sent by any sensor 3314 or any video publisher 3310 in the discussion. Note that the P / S broker 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 (eg, user 3308 or 3310) needs to receive this video stream, while the new viewer subscribes to the topic used to publish the video stream packet. , P / S broker 1304 network prepares for stream delivery.

Similarly, if UE3308, 3310, or 3314 participates in any other session and the corresponding topic is properly distributed, UE3308, 3310, or 3314 may participate in this session. The UE of the first responder 3310 and the command post 3308 can receive the alarm generated by the fixed sensor data analysis service 3304. The UE of the first responder 3310 and the command post 3308 can send a move command to the mobile robot UE 3314 (conference manager 3102 indicates that each mobile robot UE when the mobile robot UE participates in the robot control session 3332. Deliver a subscribe topic to 3314 and deliver this topic as a publish topic to each UE of the first responder 3310 and command post 3308 participating in robot control session 3332).

(Fixed sensor data collection and alarm distribution) As shown in the above description in the present disclosure, the fixed sensor 3312 does not directly participate in the multimedia conference in this scenario. Depending on the function of the fixed sensor 3312, the fixed sensor 3312 can monitor movement, detect smoke or chemicals, or detect heat, or sound, and so on. When the fixed sensor 3312 detects what should be reported, these fixed sensors 3312 can send that information to the fixed sensor data analysis service 3304, which analyzes this data and is appropriate. If this is the case, an alarm can be generated. In this way, the fixed sensor 3312 is connected to the LTE network when turned on, connected to the P / S broker 1304, sends a Service Inquiry, and is one or more instances of the fixed sensor data analysis service 3304 (this example). There is only one in a typical scenario). Fixed sensor data analysis service 3304 is a service Suppose you subscribe to the topic ServiceInquiry / FixedSensor / * for receiving Inquiry messages. Each fixed sensor 3312 can publish its Service Inquiry message to the topic ServiceInquiry / FixedSensor / &lt;myIMSI&gt;. By including the unique IMSI value of the fixed sensor 3312, the fixed sensor data analysis service software 3304 can publish the Service Description reply, which generates the Service Inquiry by the P / S broker 1304 network. It is routed only to the fixed sensor 3312. Service The Description can include a unique identification value across all instances of Fixed Sensor Data Analysis Service 3304 in the network. When the fixed sensor 3312 and the fixed sensor data analysis program 3304 have a unique ID of another party, the fixed sensor 3312 and the fixed sensor data analysis program 3304 then message each other via the P / S broker 1304 network. Can be exchanged.

The fixed sensor 3312 can send an InitiateService () message to an instance of the fixed sensor data analysis service 3304 to provide information such as GPS position coordinates and detection capabilities of the fixed sensor 3312. Fixed sensor data analysis service software 3304 can publish an InitiateServiceAck () message, in which fixed sensor data analysis service software 3304 prints data about everything that fixed sensor 3312 detects. Assign the topic that the fixed sensor 3312 will use to publish.

On the other hand, as shown above in FIG. 36, each UE 3308 and 3310 participating in the alarm session can receive a topic to which these UEs subscribe to receive the alarm, which topic further relates to the alarm. It can be maintained as a publish topic in the Fixed Sensor Data Analysis Service Program 3304. If all UE3308 and 3310 in the session will receive all alarms, then each participant UE3308 and 3310 in the alarm session can be assigned the same topic. If the different UEs 3308 and 3310 will respond to different alarm sets, the alarm session topics 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 for its assigned topic, this data is received and analyzed by the fixed sensor data analysis service software 3304, which generates an alarm. If so, it will be published for topics related to this alarm type. All UE3308 and 3310 in the alarm session that subscribed to the published topic can then receive the alarm. This interaction is shown below in Figure 37. In FIG. 37, again, the P / S broker 1304 network is omitted to simplify the interaction diagram.

(Image collection, memory, and distribution) As shown in the above description of the emergency response scenario, the first response personnel team member UE3310 can take an image as the member passes through the operational area. It can be said that this image needs to be loaded on the server and made available to another member 3310 of the first response personnel team, as well as personnel 3308 located at the command post. The image server 3302 shown in Figure 34 is the OptServer associated with the eNB 102 that covers the production area._eNBIt can operate on the 308 and can provide a means for uploading and storing this image and making it available for download to any participant 3308 or 3310 in the emergency area. OptServer_eNBBy running the software of image server 3302 on the 308, the image from the first response personnel team member UE3310 is transported to the storage site without using the backhaul 112, and the first response personnel team member 3310 Download the image to. In this way, this architecture avoids transmission delays through the backhaul 112, minimizes backhaul 112 utilization, and is available for other services. In this exemplary scenario, when the image is downloaded to the command post participant 3308, that UE3308 runs the image server 3302 on the OptServer._eNBThe backhaul 112 is used because the network is accessed through an eNB102 element that is different from the eNB102 element associated with the 308. See Figure 34.

When the user calls an image processing program on UE3308 or 3310, the program must first locate the image server 3302 in the APN network. To do this, the UE can publish a Service Inquiry message to the topic ServiceInquiry / ImageService / &lt;IMSI&gt;, where &lt;IMSI&gt; is the unique ID assigned to UE3308 or 3310. On the other hand, all instances of image server 3302 subscribe to the generic topic ServiceInquiry / ImageService / * and therefore receive the Service Inquiry message published by UE3308 or 3310. The image server 3302 can publish a ServiceDescription reply message to the topic ServiceInquiry / ImageService / &lt;IMSI&gt;, and the P / S broker 1304 network is a Service. Reply can only be routed to UE3308 or 3310 sending Inquiry. In this exemplary scenario, there is only one image server 3302 in the network and one Service Description is returned to UE3308 or 3310 for UE queries. Service The Description message can contain a unique ID assigned to the program on image server 3302. Therefore, after this point, instances of UE3308 or 3310, and image server 3302 can exchange messages over the P / S broker 1304 network. A topic for the image processing program of UE3308 or 3310 to register itself with an instance of image server 3302 and use when publishing images to the server (in this exemplary scenario, only UE3310 does this). , A second topic for use when publishing service requests (eg, image downloads, and image information) to image server 3302, to subscribe to receiving service response information from image server 3302. You can receive a third topic to use for, as well as a fourth topic to use to receive image downloads from image server 3302.

When an image is recorded in UE3310, the image processing program on UE3310 can tag this image with the current GPS coordinates of UE3310, add the date and time, and allow the user to enter a comment. can do. This information can be maintained with the image in the memory of the UE3310. When the user chooses to upload this image to the image server 3302, the UE3310 image processor uses the publish topic given to the image server during the initial interaction with the image server 3302. , Images and related tag information can be uploaded to the image server 3302. The image and its tag data can be stored in the permanent storage device by the image server 3302.

When the user (3308 or 3310) chooses to view one or more images maintained on the image server 3302, the UE 3308 or 3310 publishes the request message through its assigned service request topic. Can be done. This request can request a list of stored images from a particular user 3310, a set of dates / times, or a set of location information, and so on. This list can be returned to user UE3308 or 3310 via a topic assigned to the UE to receive a response to a service request. Another service request published by user UE3308 or 3310 may request the download of one or more specific images from the list. These images can be downloaded to user UE3308 or 3310 via a topic assigned to UE3308 or 3310 to receive image downloads. This interaction is shown in Figure 38. Again, the interaction of P / S broker 1304 in the messaging mechanism has been omitted for simplicity.

Utilizing the emergency response scenarios presented herein, this disclosure provides the APN LTE wireless network, in addition to the redirect bearer 312 feature, and the P / S broker 1304 middleware component, to handle various sensor requirements. And how to use the optimal server 304 and 308 architectures associated with it. For those of you who are skilled in the art, any sensor data collection and processing not included in the examples of this scenario will be the optimal servers 304 and 308 of the APN LTE wireless network, the bearer redirection 312 features, and the associated P / S broker. It can be deployed in an efficient manner using 1304 middleware, thereby demonstrating that the capabilities of the system disclosed herein can be used as a platform for sensor data collection, storage, analysis, and distribution. It will be clear.

(APN LTE network to give LTE users data transfer rate priority) In LTE networks, especially dual-use LTE networks, users can be given access priorities and bearer priorities, but not the priorities for air interface resources that are assigned to send and receive data. If there are many users accessing through a particular cell, it may be desirable to assign priorities to the users in order to receive high data rates. This situation can occur in the absence of emergencies, so cell exclusion for government use (CB for GU) is not enabled in the cell. On the other hand, there may be emergencies or disaster situations, and cells can be excluded for government use, but the highest priority users still receive the high data rates they need. There are still many users accessing the LTE network through restricted cells that cannot.

In LTE systems, the user equipment (UE104) authorizes a set of physical resource blocks (each PRB is a set of 12 consecutive subcarriers used in the system) and the time to send the uplink data. Will be done. Similarly, the LTE system schedules the time and PRB set to send the downlink data to a particular UE 104. The software component in the LTE system that performs this function is the scheduler in the eNB102 element. This scheduler can generally be designed to give fair processing to all UE 104s accessing the LTE network through the cells of the eNB 102. However, there may be situations where a UE 104 designated as a high priority UE 104 requires priority processing in PRB allocation for transmission over air. In addition to the coding applied to the data, the number of PRBs assigned to the UE 104 determines the data transfer rate provided to the UE 104.

(Data transfer speed priority assignment to UE and configuration of eNB scheduler using this value) This disclosure describes methods and systems for configuring the eNB 102 scheduler with data transfer rate priority values for each UE 104 accessing cells contained within the eNB 102. The scheduler uses the data transfer rate priority value associated with a given user to guide the physical resource block (PRB) allocation to the user to send and receive data through the LTE air interface and / or the LTE air interface. You can give UE 104 a time-based priority for access to. The previous section of this disclosure relates to this disclosure, i.e. APN. Optimal integration with the use of Publish / Subscribe (P / S) broker 1304 middleware to perform efficient communication between elements in LTE wireless networks and the LTE procedures associated with LTE network elements and processed in the network. With the use of the server 304 and 308 node sets and the use of interfaces with the Radio Control Process (WCP) 3902 and eNB102 elements to result in the delivery of UE102 data transfer rate priority values to eNB102 and thereby to the scheduler. With respect to the use of an application function (AF2102) that can access an IMSI value database that can contain provisioning data (IMSI values) for high priority UE104 or can contain provisioning information for data transfer speed priority features. See the previous section of this disclosure.

The following list item set describes the mechanisms that can be implemented to implement the data transfer rate priority feature mentioned above. It can be understood by those skilled in the art that deviations from the description given below are possible while achieving the same results. Therefore, the teachings specifically presented below exemplify how the data transfer rate priority function can be implemented in an LTE wireless network. 1. All users 104 can be assigned a data transfer speed priority with a value of 1 by default by the eNB102 scheduler the first time they access a cell. The scheduler can insert the default value of UE104's data transfer rate priority into the data records maintained by the scheduler for UE104. 2.AF2102 program is OptServer_PGWIt can run on 304 nodes and can provision OFF or ON Data Rate Priority based on cell-by-cell criteria. The default value can be OFF. When the value of the DataRatePriority variable changes with respect to the cell, the AF2102 interacts with an application program referred to herein as Radio Control Process (WCP) 3902 to provide data for each current registration UE102 serviced by the cell. Set the transfer speed priority value appropriately (that is, to the value 1 if the DataRatePriority in the cell is OFF, or to the UE104 data transfer speed priority value assigned to the UE104 if the DataRatePriority in the cell is ON). It can be updated. 3. OptServer_PGWUsing the eNB102 interface with the wireless control process 3902 running on 304, send the data transfer rate priority value for a given UE104 to the eNB102 (maintained by the wireless control process 3902 as part of the data stored per UE104). The C-RTNI can be used to identify the UE 104 in the eNB 102). 4. Therefore, for all UE 104s that do not interact with the radio control process 3902, their data transfer rate priority remains set to the default value of 1. Such a UE 104 can be a UE of a non-governmental user who can roam to a dual-use APN wireless network. All government users, and many or all users of similar or other dual-use APN radio networks, may have software that interacts with the radio control process 3902 via the P / S broker 1304 middleware. .. For UE104 that interacts with the radio control process 3902, UE104 is the APN When accessing a cell in an LTE wireless network, i.e. when UE104 sends a Register message to the radio control process 3902 (ie, after the LTE initial access procedure), it sends a RegisterUpdate message (ie, LTE service). Such an interaction can occur whenever (after the request procedure) or when sending a handover message (ie, after the LTE handover procedure). See Figures 4 and 6. During the processing of any of these messages, the radio control process 3902 may interact with AF2102 via the middleware of P / S broker 1304 to obtain the data transfer rate priority value associated with the UE 104's IMSI. it can. AF2102 may return a value of 1 for UE104's data transfer rate priority when provisioning on AF2102 for cell ID in the request message of wireless control process 3902 indicates a DataRatePriority of OFF. Otherwise, the AF2102 can check the data transfer speed priority provisioned to the AF2102 for the UE104's IMSI or the value provisioned to the accessible IMSI database. If AF2102 does not retrieve provisioned information about the UE104's IMSI, it can return a default value of 1. Otherwise, the AF2102 may obtain the data transfer rate priority value provisioned for the UE 104 IMSI and return this value to the radio control process 3902. Therefore, if the eNB 102 processes a UE 102 Register message, Register Update message, or Handover message, the radio control process 3902 will be redirected by the radio control process 3902 for the UE 102 bearer 302 to continue in the eNB 102. The data transfer speed priority value of UE104 can be sent to eNB102 regardless of whether or not it is used. The value used for the UE 104 data transfer rate priority can be any value of 1 or higher with a large number meaning a higher data transfer rate priority for the UE 104. 5. The eNB104 scheduler has been modified from the current run to allow the data transfer rate priority value to be taken into account when scheduling the transmission and reception of UE104 data. For example, if the eNB104 scheduler is trying to schedule downlink data sent to a set of UE104, then the set of PRBs available is based on the RF state previously reported by UE104 and is also relevant to UE104. It can be assigned based on the data transfer speed priority. The UE 104 with the highest data transfer rate priority value can receive the maximum number of PRBs consistent with sending queued data for this UE 104, or the scheduler has the lowest data transfer rate priority value. The scheduler can process before processing UE104 with. On the other hand, all UE 104s with a data transfer rate priority of value 1 are assigned otherwise because some number of PRBs are assigned to UE 104 with a higher data transfer rate priority value. You may receive less than the maximum number of PRBs you cannot win. All UE 104s with the same data transfer rate priority value can receive equal processing by the scheduler with respect to being assigned several PRBs or being processed by the scheduler first.

The disclosures in the above paragraphs can be understood in FIGS. 39, 40, 41, 42, and 43. The first three of these drawings add data transfer speed priority interactions to the interactions shown in Figures 4 and 6, with wireless control process 3902 and P / S broker 1304 messaging infrastructure. Is explicitly shown (Figures 4 and 6 do not explicitly show these components). FIG. 39 can be applied in situations where the UE 104 has not yet been registered with the radio control process 3902 (ie, during the initial access procedure). In Figure 40, UE104 was previously registered with wireless control process 3902, but needs to provide update information, for example, because UE104 is in the transition from the ECM-IDLE state to the ECM-CONNECTED state. It can be applied to certain situations. FIG. 41 can be applied to the situation where the UE 104 is in the process of handing over to the new eNB 102. Each of these three situations can result in a UE 104 accessing a different cell than before, so the newly accessed eNB 102 needs to be notified of the data transfer rate priority for the UE 104. FIG. 42 can be applied to the situation where AF2102 is provisioned to turn on Data Rate Priority for one or more cells in the LTE network. FIG. 43 can be applied to the situation where AF2102 is provisioned to turn off Data Rate Priority for one or more cells in the LTE network.

FIG. 39 shows the details and modifications of the procedure shown in FIG. 4 and previously described in this disclosure. For more information on this, UE104 has OptServer_PGWShows how the P / S broker 1304 middleware can be used to communicate with the wireless control process 3902 running on 304 nodes. The portNumber in the Start Services message is the port number of the P / S broker 1304 to which UE104 connects. On the other hand, the AF2102 software, which plays a role in the disclosure provided herein to implement a dual-use network, also provisions IMSI data or the data transfer rate priority value assigned to the UE104's IMSI. You can access the IMSI database that contains. In a modification to the procedure described in FIG. 4, the wireless control process 3902 and AF2102 communicate via the services of the P / S broker 1304 middleware, as shown in FIGS. 39, 40, 41, 42, and 43. It can then provide a data transfer rate priority value for a given IMSI, which can be used to update the serving eNB 102.

To receive messages from a large number of UE 104s, the wireless control process 3902 can subscribe to the topic "Wireless Control / *". To communicate with the wireless control process 3902, UE104 can publish its message to the topic "WirelessContol / &lt;myIMSI&gt;" where &lt;myIMSI&gt; is the unique IMSI value assigned to UE104. is there. When the radio control process 3902 responds to a particular UE 104, the radio control process 3902 can publish to the topic "WirelessContol / &lt;IMSI&gt;" where &lt;IMSI&gt; is the value assigned to the target UE 104. Is. UE104 must have previously subscribed to this topic in order to receive messages about this topic.

To exchange messages between the radio control process 3902 and AF2102, AF2102 can subscribe to the topic "AF / data / *". The wireless control process 3902 can then publish a DataRatePriorityCheck () message for the topic "AF / data / &lt;WCPid&gt;", where &lt;WCPid&gt; is wirelessly controlled. A unique ID assigned to process 3902, which radio control process 3902 subscribes to receive messages about the topic "AF / data / &lt;WCPid&gt;". The AF2102 can then reply to the radio control process 3902 by publishing a DataRatePriorityCheckResponse () message to the topic "AF / data / &lt;WCPid&gt;".

When UE104 first accesses the LTE network, UE104 as described in the previous section of this disclosure (see Figure 4) until UE104 publishes a Dedicated Bearer Established message to wireless control process 3902. Proceed to (see Figure 39). At this point in the registration process, it may be appropriate for the radio control process 3902 to publish a Data Rate Priority Check () message to AF2102. The AF2102 can use the Cell_ID and IMSI in the message to obtain the data transfer rate priority value for the IMSI and then publish the DataRatePriorityCheckResponse () message to the radio control process 3902. The wireless control process 3902 can then use a direct interface with the eNB 102 servicing the UE 3310 to deliver the data transfer rate priority value associated with the UE 104, and the eNB 102 software will use this. The value can be passed to the eNB102 scheduler. The rest of the registration process proceeds as shown in Figure 4 (and Figure 39).

FIG. 40 shows the 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 ensures that UE104 registers with the radio control process 3902 for the new cell ID and new C-RNTI value is similar to that shown in Figure 39, but the Register and registration acknowledgment in Figure 39 ( The difference is that the RegisterAck message is replaced by the RegisterUpdate and RegisterUpdateAck messages. In both cases, the same parameters can be included in the message.

FIG. 41 shows the details and modifications of the procedure described above in this disclosure as shown in FIG. For more information on this, UE104 has OptServer_PGWIt shows how the P / S broker 1304 middleware can be used to communicate with the wireless control process 3902 running on 304 nodes. The portNumber sent by UE104 in the ResumeSession message is the port number of the P / S broker 1304 to which UE104 connects. Figure 6 shows a handover procedure for redirecting the UE bearer 312 on the target eNB 102 so that the UE 104 can communicate directly with the OptServer eNB 308 node associated with the target eNB 102 in order to integrate the optimal servers 304 and 308 into the LTE network behavior. Shows the interaction inside. According to the present disclosure, FIG. 41 shows how the procedure of FIG. 6 can be modified to include updating the data transfer rate priority value of UE 104 with the scheduler of target eNB 102.

When the handover is complete and UE104 publishes the handover message to wireless control process 3902, the new C-RNTI and new Cell_ID values will be available to wireless control process 3902 along with the UE104's IMSI value. Therefore, the radio control process 3902 can interact with the AF2102 to obtain the data transfer rate priority assigned to the UE 104 (or the value 1 if the new Cell_ID has an OFF DataRatePriority). The radio control process 3902 can then deliver the UE 104 data transfer speed priority to the target eNB 102 via direct communication interaction, thus passing this data transfer speed priority to the eNB 102 scheduler. Can be done. The radio control process can then continue processing the handover procedure by exchanging Redirect Bearer and Redirect Bearer Response messages with the target eNB 102, and the UE 104 via the OptServer eNB 308 associated with the target eNB 102. Allows the service session to resume. See FIGS. 6 and 41.

(Data transfer rate priority turn-on for one or more cells) See Figure 42 for a description of the message interactions below. As shown in the previous paragraph, AF2102 can provision a DataRatePriority value assigned to each cell in the LTE network. When the DataRatePriority value for a cell is changed from OFF to ON, all UE104s registered in the wireless control process 3902 and all UE104s accessing the LTE network via the cell are sent by the scheduler of the serving eNB102 including the cell. Must have updated UE104 data transfer speed priority values. The UE 104's current data transfer speed priority can have a value of 1 in the scheduler because the DataRatePriority value previously assigned to the cell is OFF. FIG. 42 shows a process that requires updating the eNB 102 scheduler with the data transfer rate priority value of each registered UE 104 that accesses the network via the cell.

The wireless control process 3902 can subscribe to the generic topic "WirelessControl / *" and receive messages from a large number of endpoints. When AF2102 is provisioned with an ON value for DataRatePriority for a given cell, AF2102 publishes a CellDataRatePriorityON message for the topic WirelessControl / dataRatePriority / &lt;AFid&gt;. And all instances of wireless control process 3902 can receive this message. This message contains a list of cell ID values. This message is received by the radio control process 3902. For each Cell_ID in the message, the radio control process 3902 can retrieve its data structure for all UE 104, which data structure is registered with the radio control process 3902 and is selected from the messages sent by AF2102. The serving cell ID of the UE is shown as the value given. The UE104 IMSI value list collected by the radio control process 3902 in this way is described in the topic "AF / &lt;WCPid&gt;. Can be set in the BulkDataRatePriorityRequest message published for ", and this message is received by AF2102. This message is sent for each Cell_ID in the message received by WCP3902. When the AF2102 receives the BulkDataRatePriorityRequest message, the AF2102 can search its provisioning data or accessible IMSI database based on IMSI units for each IMSI's data transfer rate priority value. This result can be set in a BulkDataRatePriorityResponse message that can be published for the topic "AF / &lt;WCPid&gt;", and the requesting instance of wireless control process 3902 Receive this message. The wireless control process 3902 then retrieves the C-RNTI value corresponding to each IMSI value from the provisioning data, and then retrieves and responds to the IP address of the eNB 102 servicing each cell in the message received from the provisioning data. A data transfer rate priority value can be sent for each UE (C-RNTI) that accesses the network through each cell. These interactions are continuously performed for each Cell_ID value in the CellDataRatePriorityON message. Can be set in a BulkDataRatePriorityResponse message that can be published to, and the requesting instance of wireless control process 3902 receives this message. The wireless control process 3902 then retrieves the C-RNTI value corresponding to each IMSI value from the provisioning data, and then retrieves and responds to the IP address of the eNB 102 servicing each cell in the message received from the provisioning data. A data transfer rate priority value can be sent for each UE (C-RNTI) that accesses the network through each cell. These interactions are continuously performed for each Cell_ID value in the CellDataRatePriorityON message. Can be set in a BulkDataRatePriorityResponse message that can be published to, and the requesting instance of wireless control process 3902 receives this message. The wireless control process 3902 then retrieves the C-RNTI value corresponding to each IMSI value from the provisioning data, and then retrieves and responds to the IP address of the eNB 102 servicing each cell in the message received from the provisioning data. A data transfer rate priority value can be sent for each UE (C-RNTI) that accesses the network through each cell. These interactions are continuously performed for each Cell_ID value in the CellDataRatePriorityON message.

(Off data transfer rate priority for one or more cells) See Figure 43 for a description of the message interactions below. When the DataRatePriority value is changed from ON to OFF for the cell, all UE104s registered in the wireless control process 3902 and all UE104s accessing the LTE network through the cell are in the scheduler of the eNB 102 that houses the cell. Must have updated UE104 data transfer speed priority values. The UE 104's current data transfer rate priority in the scheduler can have a value provisioned for the UE 104's IMSI because the DataRatePriority value previously assigned to the cell is ON. Here, this value needs to be changed to 1, and all UE104s accessing the network through this cell can get equal priority processing by the eNB102 scheduler. FIG. 43 shows what happens when it may be necessary to update the eNB 102 scheduler with a data transfer rate priority of value 1 for each registered UE 104 accessing the network through this cell.

When the AF2102 provisioning is changed, the DataRatePriority value of one or more cells is changed from ON to OFF, and AF2102 is set to CellDataRatePriorityOFF (cell data transfer speed priority) for the topic "WirelessControl / dataRatePriority / &lt;AFid&gt;". Off) A message can be published and all instances of wireless control process 3902 can receive this message. This message contains a list of cell ID values. For each cell ID in the received message, the radio control process 3902 can retrieve the data structure of the radio control process 3902 for all UE 104, which data structure is registered with the radio control process 3902, AF2102. Shows the serving cell ID of the UE as the value selected from the message sent by. The data maintained by the radio control process 3902 for each such UE 104 includes the C-RNTI value, which is the identifier that the UE 104 recognizes on the serving eNB 102. A list of UE104 C-RNTI values is collected by wireless control process 3902 and can be set in a UEDataRatePriorityList message, which is a selected cell whose DataRatePriority value has been changed to OFF. Is sent to the eNB 102 to process. For each C-RNTI value, this message can indicate that the data transfer rate priority of value 1 is related to the C-RNTI for identifying the UE 104 with respect to the eNB 102 scheduler. When eNB102 receives this message, the scheduler updates the value of UE104 accordingly.

(Collection and reporting of billing data on the optimal server in the APN LTE network) When a UE bearer is redirected in its serving eNB102, it is connected to the local best server server 308 instead of the SGW110 element, then to PGW114, where PGW114 is the data that goes through the redirected bearer. Cannot generate billing information regarding air interface usage by. This situation may not be important for some applications (eg, for military or emergency applications), but it may be important for commercial applications. In this latter case, OptServer_eNBThe program on the 308 can maintain the bytes, packets, connection times, and other tracking information needed to generate a call detail record (CDR) equivalent for data transport through the redirected bearer 312. , It is necessary to be able to convey this information to PGW114 or some other billing data processor at an appropriate time. (OptServer_eNBSince the backhaul 112 cannot be used to carry data between the 308 and the UE 104, another billing method can be applied to this utilization. In addition, the resources provided by Optimal Servers 304 and 308 can include permanent data storage, temporary data storage, program execution time, etc., and APN network operators can use these system resources. Can be requested to charge. Therefore, billing data also needs to be collected for the resource utilization of optimal servers 304 and 308.

Broadband forum IPDR (IP session detail record) is specified in TR 232 (http://www.broadband-forum.org/technical/download/TR-232.pdf) and OptServer_eNB308 and OptServer_PGWIt provides an overview of data reports that can be used to systematize and report billing data collection in 304 and send detailed records to PGW 114 or other processing points for such data. To pass billing details, the specifications of the precision data collected, and the interface to PGW114 that allows the optimal server 304 or 308 to transfer information, or any other processing charged for processing this information. Requires one of the entity's specifications.

In addition, OptServer with redirected bearer 312_eNBIn 308, bearer-to-IMSI mapping is not immediately available, so collection of IP detail records for a particular redirect bearer 312 associated with a particular UE 104 needs to be achieved. In this situation, the redirected bearer 312 remains in the PGW 114 due to the fact that the redirected bearer 312 does not pass through the PGW 114 and therefore the PGW 114 cannot reveal the details in the usual way for collecting billing data. Extensions are no longer available. The bearer-to-IMSI mapping for the redirected bearer 312 is OptServer_eNBIt can be said that it needs to be communicated to the billing data collection program on 308 and that it needs to be designed to generate data and transfer the billing data to the billing data collection service. The present disclosure can provide such a design. In addition, when the UE104 moves from one eNB102 to another, the redirected bearer 312 will have one OptServer._eNBAnother OptServer from 308_eNBGoing to 308, it can be said that the billing data collection point needs to be migrated for data passing through the redirected bearer 312. The disclosure can further provide details on how this movement of billing data collection points can be negotiated.

As shown above, in addition to delivering user data packets through the redirected bearer 312 entity, OptServer_PGW304 and OptServer_eNB308 It can be said that resource usage on an entity needs to be reported. For this purpose, operating system statistics such as process text size and .bss (random access memory) size, permanent memory file size and storage time, etc. can be collected and used. This disclosure is based on this data collection and reporting of OptServer in APN network architecture._PGW304 and OptServer_eNBIt can provide details on how it can be negotiated on the 308 node.

(Architecture that can be used for collecting and reporting billing data on the optimal server) A person skilled in the art can devise many alternatives to systematize the collection and reporting of billable data in the APN LTE network using a set of integrated optimal servers 304 and 308 in the APN LTE network. Can be recognized. However, some architecture that makes this task successful is a means of identifying a set of usage data that may include usage periods for a particular user or another billing entity and timing the collected data to a designated appropriate billing center. It can be considered to provide a means of good transfer. The teachings provided in this disclosure provide one such architecture. This architecture is the most efficient means for collecting and reporting the required billing data by leveraging the unique features of the APN network through the disclosures already reported herein. Provide things.

Figure 44 shows each OptServer_eNBIP Billing Data Record Program (IPBDR) for 308 nodes_eNB An instance of a program called 4404) is OptServer_eNBRelated to 308 resource usage and also OptServer_eNBIt shows that it can be executed for the purpose of collecting billing data related to billing information collection related to user data transport using redirect bearer 312 terminated at 308 nodes. In addition, a similar program instance, i.e. IPBDR_PGW 4402 is the OptServer associated with the PGW114 element in the APN LTE network_PGWRecognized to run on 304 nodes. IPBDR_eNB The 4404 program can be involved in billing data collection for resource utilization on its local server and for data transport through the UE104's redirected bearer 312, while IPBDR._PGWCan only be involved in billing data collection regarding resource utilization on its local server. The reason for this difference is the LTE Bearer 312 with OptServer_PGWThis is because any user data transported to the PGW 114 element passes through the PGW 114 element, and thus the billing data for this transfer is collected and reported by the PGW 114 element in a conventional manner well known to those skilled in the art. FIG. 44 further shows a set of service programs 4408 running on optimal servers 304 and 308. These service programs can be the same service program as shown in FIG. 17, or can be different service programs. Also shown in FIG. 44 is the centralized IP billing data collection and processing program 4410. This program 4410 runs on server 124 outside the APN LTE network, but the server location is instead within the APN LTE network, eg OptServer._PGWCan be on 304. The function of this program in the architecture presented in this disclosure is IPBDR._PGW 4402 program and numerous IPBDRs_eNB 4404 Aggregates the data collected and reported by the program, stores the aggregated results in a database for easy access by APN LTE network operators, and uses this aggregated billing data for wireless network billing by LTE network operators. Is to deliver to the official billing system program. Note that in Figure 44, all the program components described above are connected to an instance of P / S Broker 1304 and thus can participate in the Publish / Subscribe messaging described throughout this disclosure.

Each OptServer_eNB308 nodes and OptServer_PGWA unique ID can be assigned to 304 nodes. This assignment can be desirable to facilitate the generation of a unique ID for each instance of P / S broker 1304 deployed in the APN LTE network. In this disclosure, IPBDR_PGW 4402 or IPBDR_eNB Once the 4404s are initialized, they can have the ID assigned to the best server 304 or 308 running. Also, the processor type (ie OptServer)_PGW304 or OptServer_eNB308) can be provided to the initialization program to determine whether to register with the radio control process 3902 to collect data related to user packet transport via the redirected bearer 312. IPBDR_eNB The 4404 program can be registered with the radio control process 3902, as shown in Figure 45.

On the other hand, the radio control process 3902 can have provisioning data, which is used by each OptServer to assign the P / S broker 1304 to UE104 for communication using a dedicated bearer._eNB308 on and OptServer_PGWAssociate each instance of P / S broker 1304 on 304 with the associated eNB102 or PGW114 element. The Start Services and Resume Session messages in Figures 4, 6, 39, 40, and 41 show this assignment of the P / S broker 1304's IP address and port number to UE104. Here, the provisioning data in wireless control process 3902 for each instance of P / S broker 1304 can also include a server ID. By doing this, the radio control process 3902 can register the IPBDR._eNB It is possible to associate the 4404 program with the UE104's IMSI and P / S broker 1304 ID or IP address and port number information.

When this association is made, Figure 45 shows the UE104 bearer 312 with an IPBDR._eNB OptServer providing a host for 4404 instances_eNBIPBDR whenever redirected to 308_eNBThe instance of 4404 receives the IMSI of UE104 from the radio control process 3902, and the IP address and port number of P / S broker 1304 to which UE104 connects via the redirected bearer, and the IP address assigned to UE104. (The IP address of UE104 can be included in the Register and RegisterUpdate messages sent by UE104 to the radio control process 3902, see the Register and RegisterUpdate messages in Figures 39 and 40). See Figures 39, 40, and 41 for LTE processing status when the dedicated bearer 312 can be redirected for UE104.

IPBDR_eNB When an instance of 4404 gets the IP address of the UE and the IP address and port number of the P / S broker 1304 to which the UE 104 connects, Figure 45 shows the IPBDR._eNB 4404 communicates with an instance of P / S broker 1304 and informs this instance that it will collect billing data for the UE (via the BrokerStartCollection () message) and continues to this instance. Targeted and periodic intervals or IPBDR_eNB 4404 IPBDR billing data based on programmatic commands_eNB 4404 Indicates that the program should be transferred. An instance of P / S broker 1304 resides in the direct path of the packet to and from the redirected bearer 312 of UE104, so all such data can be counted and the result is P / S broker 1304. IPBDR by instance of_eNB Propagated to 4404 instances. The data that can be collected are the start time and end time of billing data collection, the bearer ID of the redirected bearer 312, the number of bytes and packets sent to and received from UE104 via the redirected bearer 312, and these numerical values. Includes breakout information for bytes and packets sent and received for each topic. The association of these values with the topic determines whether the data traverses the backhaul 112 network or is exchanged with real-time services such as interactive games that require very little latency. Can help you to. Another billing policy can then be applied to the utilization data when the data is identified by the topic used to convey the data over the P / S broker 1304 communication.

To determine whether to use backhaul 112 or OptServer_eNBTopic-based utilization data analysis to determine whether a different billing policy should be applied due to the low latency provided for data delivered to user 104's access point near 308. , Can be provided most conveniently by the centralized IP billing data collection program 4410. Program 4410 can provision information that associates topics used in APN LTE networks with other information that can be used to determine the billing policies that can be applied to the collected data. The centralized IP billing data collection program 4410 can then report the billing data to the billing system used by the operators of the APN LTE network.

In addition to this, FIG. 45 shows that a ResumeSession () message is sent to the UE 102 when the handover takes place. In this case, OptServer_eNBThe 308 element is changed from the element at the source eNB 102 position to the element at the target eNB 102 position. An explicit message interaction is shown to initiate billing data collection at the target location via the StartDataCollection () message. This is also the case when the billing data collection for the redirect bearer at the source location needs to be finished and any unreported data can be reported to the centralized IP billing data collection program 4410. Figure 45 shows the IPBDR where the wireless control process (WCP) 3902 is sourcing a StopDataCollection () message._eNB Send to an instance of 4404, bring the final report from this program to the centralized IP billing data collection program 4410, stop the P / S broker 1304 in this location from collecting data about UE102, and IPBDR in the source location._eNB It shows that the context data related to UE102 can be deleted in the instance of 4404. These latter interactions are not shown in FIG. 45, but those skilled in the art can understand that they occur as described herein.

In Figure 45, the StopDataCollection () message shows how billing data collection for the redirected bearer 312 on the UE 102 stops during the handover when the UE 102 leaves the source location where the redirected bearer 312 was previously terminated. It is designed to indicate whether to do it. Data collection also needs to be stopped when the UE 102 transitions from the ECM-CONNECTED state to the ECM-IDLE state and when the UE is detached from the LTE network. The interactions that can be used to perform this behavior are shown in Figure 46 when transitioning to the ECM-IDLE state and in Figure 47 when UE102 is detached from the LTE network.

The transition of UE104 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 procedure is called the S1 release procedure. The 3GPP standard shows that UE104 may or may not have S1 release message interactions, but MME108 entities will always. Figures 25, 26, 27, 28, 29, and 30 show that the MME108 entity can connect to the P / S broker 1304 middleware within the APN LTE network, which causes the UE104 to transition to the ECM-IDLE state. IPBDR using the MME108 entity_eNB It shows that the instance notification of 4404 can be easily done. Figure 46 currently collects redirect bearer 312 data utilization for UE104 and is notified by MME108 when UE104 transitions to the ECM-IDLE state._eNB Shows how the LTE S1 release procedure for MME108 elements can be extended to enable an instance of 4404. IPBDR_eNB Each instance of 4404 subscribes to the topic "IPBDR / &lt;IMSI&gt;" when it first initiates utilization data collection for the IMSI of a particular UE 104, that is, when it receives a StartDataCollection () message from the radio control process 3902. Can be live (see Figure 45). As shown in Figure 46, when the MME108 receives a UE S1 context release complete message from the eNB102 that previously served the UE104, the UE104 is no longer connected to the LTE network through any eNB102 element. Absent. The MME108 can then publish a StopDataCollection (IMSI) message for the topic "IPBDR / &lt;IMSI&gt;", thus servicing the IMSI IPBDR._eNB Messages are only received by instances of 4404. IPBDR_eNB The 4404 instance then sends some remaining utilization data about the UE 104 to the centralized IP billing data collection program 4410, interacting with an instance of the local P / S broker 1304 to stop the utilization data collection for the UE 104. IPBDR of UE104 context data_eNB It can be deleted from the 4404's memory and unsubscribed from the topic "IPBDR / &lt;IMSI&gt;".

The LTE procedure used to detach UE 104 from the LTE network is specified in Section 5.4.8 of TS 23.401 v9.4.0. Three situations: the UE start detach procedure specified in section 5.3.8.2 of TS 23.401 v9.4.0, the MME start detach procedure specified in section 5.3.8.3 of TS 23.401 v9.4.0, and TS 23.401 v9. The HSS start detach procedure specified in Section 5.3.8.4 of .4.0 may be relevant to the current disclosure. In the first two situations, MME108 can use some points in these procedures to publish a StopDataCollection (IMSI) message to an instance of IPBDeNBReNB 4404. One is when the MME108 receives the LTE Delete Session Response message from the SGW110, and the other is when the MME108 receives the S1 UE. This is when the S1 release procedure is completed by receiving the Context Release Complete message (see Figures 5.3.8.2-1 and 5.3.8.3-1 in TS 23.401 v9.4.0). If the S1 opening procedure takes place in these interactions, the preferred point for MME108 to publish the StopDataCollection () message can be at the end of this part of the detaching procedure. Otherwise, the MME108 can publish a StopDataCollection () message when it receives an LTE Delete Session Response message from the SGW110. When the detach is an HSS start detach procedure, preferably after the S1 open portion of the detach procedure is completed, or the MME108 is in the LTE Cancel Location. You can publish a StopDataCollection () message when sending an Ack (LTE position cancellation acknowledgment) message to the HSS120. See Figure 47.

Although FIGS. 45, 46, and 47 show message interactions using the functionality of the P / S broker 1304 middleware, the descriptions provided herein are complete that can be used to exchange these messages. Note that it does not include a topic set. The preceding paragraph and the aforementioned section of this disclosure include teachings on how topics can be structured to provide efficient communication between all participating entities, and those skilled in the art will appreciate this. The teachings can be applied to message exchanges in current disclosures.

In addition to collecting and reporting utilization data passing through redirect bearer 312 associated with a particular UE 104, IPBDR_eNB 4404 program, and IPBDR as well_PGW The 4402 program can also report billing data regarding resource utilization occurring on these processing nodes. In one embodiment of this feature, instances of these programs can periodically acquire the data collected by the operating system for these computer nodes. Typically, these programs can collect the size of the program text and .bss (ie, RAM memory) used by each service program 4408 shown in FIG. The utilization data collected in this way can be published to the centralized IP billing data collection program 4410 for aggregation, submission to the database, and transmission to the LTE network billing system.

IPBDR to get the number of bytes of permanent storage used by an instance of service program 4408 and the amount of time used for permanent storage of data in service program 4408._PGW 4402 and IPBDR_eNB Instances of the 4404 can use an interface with the local disk system, which is constructed to provide this information to these billing data collection systems. For example, a disk or permanent memory system can be segmented, so that the data in service program 4408 is stored in one or more specific segments. IPBDR_PGW 4402 and IPBDR_eNB Instances of 4404 can register with the processors of their respective optimal servers 304 and 308 to be notified whenever these segments change. An arrangement with the service program 4408 provider can be required to enable tagging of stored data with an ID that identifies the provider of service program 4408 in which the data is stored. IPBDR with this type of arrangement_PGW 4402 and IPBDR_eNB It can be seen that 4404 instances can collect permanent storage utilization data for specific billable entities. This utilization data includes the number of bytes stored, the start time, end time, or duration of storage, the node where the data is stored, the number of accesses to specific storage elements per hour each day, and per day. The total number of accesses to a particular storage element, the average time a user spends accessing this content element, the total amount of data involved in delivering a particular storage element using the backhole 112, the backhole 112 It can include the total amount of data involved in delivering a particular stored content element without use, the number of control messages used in delivering a particular content element per hour each day. Permanent storage utilization data can then be formatted and published to the centralized IP billing data collection program 4410 for aggregation, submission to the database, and transmission to the LTE network billing system.

(Efficient reduction of cell-to-cell interference using agile beams) A problem to be noted in all wireless networks is the interference caused by the signals transmitted by adjacent cells to the user in the coverage area of one cell. This interference is called cell-to-cell interference and is especially encountered by users located near the boundary between two adjacent cells. See Figure 48, which shows two adjacent cells modeled as hexagonal area 4802. Here, the shadeless dots represent the antennas that generate the RF signal 4808 for these cells. The RF signal 4808 from each cell inevitably overlaps the coverage area of the adjacent cell, otherwise resulting in an RF coverage hole. Area 4804 where RF signals overlap is an area where cell-cell interference occurs. Due to the interference, the data transfer rate provided to the user located in the cell boundary area 4804 may be reduced, which may adversely affect the cell communication capacity and throughput as well as the user experience. In LTE wireless networks, users are assigned subcarriers to send or receive data. Subcarriers are designed to be orthogonal in the standard, and a user assigned to one subcarrier set does not observe transmission interference for another user assigned to another subcarrier set. However, near the cell boundary, each of the two adjacent cells may assign the same subcarrier set to the user in each cell boundary area 4804, which is part of these cell coverage areas 712. is there. In this case, each of these users may interfere with transmission in adjacent cells using the same subcarrier set assigned to a given user.

Techniques for reducing or eliminating this cell-cell interference have been sought for many years. Current technology for LTE can include dividing the bandwidth of a subcarrier set into subsets, one subset of the subcarriers being allocated only to users near the boundaries of the serving cell and the other subset. , Assigned to users located inside the serving cell. Subsets can be arranged in each of adjacent cell sets, and another subset of subcarriers is used at the boundaries of these cells. This technique alleviates the cell-to-cell interference problem, but it reduces the overall throughput of the cell because only a subset of all available subcarriers are available for allocation to any user. , And slows down the data transfer rate of individual users.

Another technology currently being explored could allow adjacent cells to communicate with each other in real time to notify the subcarrier set to be assigned to a user located at boundary 4804 of the cell's coverage area 712. This technique can allow any user to use the entire subcarrier set, but may result in additional communication between base stations to coordinate the use of the user's available subcarrier set. is there. With this technique, if a subcarrier is assigned to a user at the cell boundary of an adjacent cell, the subcarrier cannot be assigned to a user at the cell boundary of one cell. Therefore, cell throughput and individual user data transfer rates may have a negative impact. This technique is called cell-to-cell interference coordination.

The present disclosure does not use any of the above techniques. More precisely, the present disclosure can take advantage of the use of agile beamforming previously described in the present disclosure. At a given interval of 1 millisecond, cells with agile beamforming generate an RF beamset 902 (eg, 4 beams) that covers a subset of 712 across the cell coverage area. In the LTE FDD system, another set of (4) RF beams 902 is generated at each of the four intervals of 1 millisecond, and the 16 RF beams 902 thus generated are the entire cell coverage area. Over 712. At 5 ms, again the first set of RF beam 902 was generated, then at 6 ms, the second set of RF beam 902, and so on, followed by agile beam rotation of 4 mm. It can continue to pass through the cell coverage area quickly in a cycle of seconds. An example of 16 agile beam sets 902 covering area 712 of the FDD LTE cell is shown in FIG.

FIG. 49 shows an exemplary sequence of 16 agile beams 902 over the cell coverage area 712 as a whole, using a hexagonal model for the cell coverage area 712. FIG. 49 shows a set of 16 agile beam areas 902 used to span cell coverage area 712 and grouped into 4 sets consisting of 4 RF beam areas 902, subs belonging to the same set. The area is similarly shaded. All similarly shaded sub-areas are covered by RF beams generated at the same 1 millisecond interval. In FIG. 49, the RF beam 902 cannot be included in the indicated sub-area, but to some extent spreads to the adjacent sub-area and also to the cell boundary to the adjacent cell sub-area. Can be noted. By generating an agile beam using a large set of antennas, the RF beam 902 can be more properly focused and the RF signal level of a particular beam 902 is of its intended sub-coverage sub-area. Ripple to adjacent sub-areas can be minimized as it can decay rapidly on the outside. Note that FIG. 49 shows that subareas 902 generated at any single 1 millisecond interval are generally separated by one or more subareas 902 in the same cell. Therefore, at any 1 millisecond interval, the use of agile beamforming assigns the same subcarriers to users in the same cell (up to 4 users), but to users located in different subareas 902. It can be prevented from being assigned. The cell communication capacity and throughput, as well as the minimum data transfer rate that can be assigned to any user, can be significantly increased compared to cells that do not use agile beamforming.

Therefore, if the rotation of the RF beam 902 in the adjacent cell can be configured so that the RF beam 902 covering the adjacent subarea in the adjacent cell is not generated at the same 1 millisecond interval, the cell-to-cell interference problem arises. It can be noted that this can be resolved without the use of additional communications and without the restrictions on the subcarrier set that can be assigned to the user.

(Establishment of non-adjacent RF beam patterns in cells of the same LTE base station) The present disclosure presents an example in which the same set of four RF beam subareas 902 is generated in each cell, but not necessarily in each cell at the same time. Two adjacent RF beams 902 if 16 RF beams 902 are arranged in one pattern in which one, two, or only three RF beams 902 cover any boundary 4804 of the cell. Note that beam rotations in adjacent cells can be configured so that subareas are not generated at the same 1ms interval. However, if there are four or more RF beam 902 subareas at any cell boundary 4804 due to the pattern of RF beam subareas, then two or more adjacent subareas are placed at the same 1 millisecond interval. It is not possible to make it possible to select the beam rotation in each cell without generating it.

Figure 50 shows an example of a base station that supports three cells. In FIG. 50, the antenna of the base station system is located at the black dot, and these three cells are represented by α1, β1, and γ1. RF beam area 902 subareas are indicated by 1 to 16. The same set of four RF beam areas 902 is used in each cell, and the same rotation pattern of RF beam 902 can be used in each cell with respect to the shape of RF beam 902 shown in FIG. Thus, in the first 1 millisecond interval, each of the three cells produces an RF beam 902 covering subareas 4, 6, 11, and 13 in each cell coverage area 712. In Figure 50, all of these sub-areas are shaded by vertical lines. Note that at the boundary between any two cells, adjacent subareas in adjacent cells are not generated at this time interval, so there is no cell-to-cell interference in this 1 millisecond operation.

FIG. 50 shows that in the second millisecond operation, each cell produces an RF beam area 902 covering subareas 2, 8, 10 and 16 in its respective cell coverage area 712. Areas are shaded with a dot pattern. Again, at the boundary between any two cells, it can be recognized that the adjacent subareas in the adjacent cells are not generated at this time interval. Therefore, there is no cell-to-cell interference in the second millisecond operation.

FIG. 50 shows that in the third millisecond operation, each cell produces an RF beam area 902 covering subareas 1, 7, 9, and 15 in its cell coverage area 712. The area is shaded with a fine hash pattern. Again, at the boundary between any two cells, it can be recognized that the adjacent subareas in the adjacent cells are not generated at this time interval. Therefore, there is no cell-to-cell interference in the 3rd millisecond operation.

FIG. 50 shows that in the 4th millisecond operation, each cell produces an RF beam area 902 covering subareas 3, 5, 12, and 14 in its cell coverage area 712. The area is shaded with a diagonal brick pattern. Again, at the boundary between any two cells, it can be recognized that the adjacent subareas in the adjacent cells have not been generated. Therefore, there is no cell-to-cell interference in the 4th millisecond operation.

The first set 4, 6, 11, and 13 of the RF beam area 902 are again generated in the 5th millisecond operation, so that the RF beam 902 generation pattern is repeated again. In this way, it can be recognized that the RF beam rotation pattern selected for each cell in FIG. 50 does not result in cell-to-cell interference. No inter-cell communication or coordination is required and no restrictions are set on the LTE subcarriers that can be assigned to the user in any RF beam area 902 in any given millisecond operation. The selection of RF beam area 902 subareas grouped into four sets is not unique, and the rotation pattern shown in FIG. 50 is not unique. Those skilled in the art will appreciate that another option for the RF beam 902 subarea and another option for the RF beam rotation pattern can be selected to achieve similar results without cell-to-cell interference.

(Establishment of non-adjacent RF beam pattern in adjacent cell of another LTE base station) FIG. 51 is an extension of the results shown in FIG. 50 by adding adjacent cells of neighboring LTE base stations 2, 3, and 4. To make it easier to understand the results obtained, FIG. 51 shows only the adjacent area of cell α1. In this hexagonal representation of cells, each cell has 6 edges, so each cell has 6 adjacent cells. The two adjacent cells β1 and γ1 exist in the same base station system as α1, and the results of these RF beam rotation patterns are already shown in FIG. Another cell adjacent to cell α1 is β2 and γ2 in base station system 2, cell β3 in base station system 3, and cell γ4 in base station system 4, which is shown in FIG. There is no adjacent subarea generated at the same time in any of the two adjacent cells, that is, at any boundary 4804 of cell α1, whenever an RF subarea is generated in that cell, it is adjacent in the adjacent cell. The boundaries of cell α1 are highlighted so that it is easy to see that no subareas are generated (with different shading).

FIG. 51 lists RF beam rotation patterns that follow cells β2, γ2, β3, and γ4, which are adjacent to cell α1 but not in the same base station system. Table 9 shows the beam rotation patterns selected for these cells located adjacent to cell α1 and in a separate base station system from cell α1. Further, in FIG. 51, the adjacent subareas at the boundary between cell γ2 and cell β2 and the boundary between cell γ2 and cell β3 have similarly different shading patterns, thereby causing these. Note that this indicates that there is no cell-to-cell interference between cells. The same conclusions can be drawn regarding the boundary between cell β2 and cell γ4 and the boundary between cell β3 and cell γ1. See Figure 51.

Table 9: Examples of beam rotation patterns for cells adjacent to a given cell and in another base station system<img id="000023" he="135" wi="151" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

In the embodiment of FIG. 51, the rotation pattern of the RF beam 902 can then be selected when the remaining cells of base station systems 2, 3, and 4 are added, and thus any of the cells as well. It can be shown that there is no cell-cell interference that occurs at the boundary of. The process of selecting the rotation pattern of the RF beam 902 can be extended per base station system and per cell in the LTE wireless network. FIG. 52 shows the results when cell α2 is added for base station system 2, cells α3 and γ3 are added for base station system 3, and cells α4 and β4 are added for base station system 4. Shown. The rotation pattern of the RF beam 902 is shown for each of these cells in FIG. 52, where the boundaries between each pair of adjacent cells are similarly shaded with similar sub-areas, but any cell-to-cell boundaries. It is highlighted so that it is easy to see that it is not adjacent to each other. In this way, cell-to-cell interference can be prevented when the agile beams disclosed herein are used in LTE radio systems.

(Time synchronization configuration for each cell in RF beam generation) 50, 51, and 52 show how cell-to-cell interference can be prevented in a radio system that utilizes agile beamforming for a three-cell system in one base station system and many base station systems. ing. In each case, the base station system needs to maintain the start time of the same concept, so each cell needs to generate which subset of RF beam area 902 at any given millisecond interval. Can be decided. Therefore, time synchronization across all cells needs to be as accurate as with a margin of error less than 1 millisecond. The pattern of RF beam 902 is repeated every 4 ms in each cell, so a given set of 4 RF beam 902 is every 20 ms (ie every 1 LTE frame) the same subframe of LTE frame. Occurs in the frame. If each cell can determine when the first millisecond of an odd (or even) numbered LTE frame occurs, then all cells are an exact subset of the RF beam 902 pattern every millisecond interval. Can be generated.

There can be at least two approaches to achieving the desired result, and no new invention is needed for this purpose. The first method can be the case where all base station systems in the wireless network operate using GPS with respect to timing. In this case, each base station system can have the same concept of current time with accuracy better than 20 nanoseconds. Thus, each cell can be synchronized, for example, to start an odd numbered LTE frame in sync with the 1 second mark of the GPS timing system. (Each LTE frame has a duration of 10 ms) Precision Time Protocol as specified in the IEEE 1588 standard if GPS is not available for any or all base station systems in the LTE network. PTP) can be used. For example, the master clock, which is part of the IEEE 1588 timing system, can be synchronized with GPS time and deliver highly accurate timing information to each base station system in the LTE network synchronized with the master clock. Here, as in the use of GPS timing, each cell can synchronize, for example, the odd-numbered LTE frame of the cell with the 1-second mark of the IEEE 1588 system. The accuracy obtained can be much better than 1 millisecond and can therefore be used to synchronize LTE cells in the RF beam 902 pattern generation of LTE cells.

(Baseband data transmission and reception in LTE radio base stations using periodic scanning RF beamforming) Beamforming technology has been used for many years in the areas of audio signal processing, sonar signal processing, and radio frequency signal processing to improve the operation of systems. Often, these systems position a transmit or receive point and then focus on the system antenna to generate a beam towards that point. The systems disclosed herein operate in different ways and take advantage of the fact that user devices in LTE wireless networks are scaled to receive or generate uplink transmissions. The disclosed system does not focus the antenna beams to a particular user, but produces m sets of N RF beam patterns 902, where N RF beams 902 are located. The given set covers a fixed set of N subareas across the cell coverage area. The system works best when the subareas are not adjacent. The maximum number of sets of N RF beam patterns 902 is LTE It can be limited to 4 as disclosed herein in the FDD system and is either 1, 2 or 3 as disclosed herein, depending on the U / D configuration 1002 of the TDD system. Can be limited to. The total number of RF beams 902, or m × N, can be designed to overlap the entire cell coverage area 712. In the LTE FDD system, each of the m sets of RF beam patterns 902 can be generated in 1 millisecond subframes of the LTE frame, where the m sets are 4 consecutive in the LTE FDD system. Since each subframe can be filled in the same order, it has a periodicity of four subframes as disclosed herein. In LTE TDD systems, each of the m sets of RF beam patterns can be generated in 1 millisecond subframes of LTE frames, where the m sets are TDD U / D as disclosed herein. It can be delivered over 10 subframes of each LTE frame in a restricted way depending on configuration 1002. LTE FDD system or LTE In any of the TDD systems, it can be confirmed that the RF beam rotates over the cell coverage area 712 in a cyclical manner. These types of beamforming systems are referred to as periodic scanning RF beamforming systems, periodic beamforming systems, or periodic agile beamforming systems.

The present disclosure is for constructing and processing data passing through an interface between the RF and antenna subsystem 5304 and the baseband processing subsystem 5302 of an LTE radio RF base station utilizing periodic scanning RF beam forming. Provides information on the systems and methods that the radio frequency base station digital baseband subsystem 5302 can use. Therefore, this disclosure does not process the systems and methods used in RF and antenna subsystem 5304 to generate RF beam signals transmitted or received by radio RF base stations. The present disclosure allows RF and antenna subsystems 5304 to form focused N co-occurring RF beams 902 so that RF and antenna subsystems 5304 are N + 1 separate in transmission direction. It teaches that it is necessary to work with the data stream 5308 and N + 1 separate data streams 5310 in the receiving direction. For each of the transmit or receive directions of transmission, one of the N data streams corresponds to a different one of the N RF beams 902 each focused, and another data stream Corresponding to another RF signal, the energy of this signal covers the entire area of the cell, Cell-Wide transmit data stream, or Cell-Wide receive data stream. The teachings disclosed herein relate to the presentation of different types of information in each of these transmission data streams and the retrieval of different types of information from the received data streams. Therefore, this teaching describes the operation of the baseband subsystem 5302 of a radio RF base station utilizing periodic scanning RF beamforming.

FIG. 53 illustrates the interface of the RF and antenna subsystem 5304 with the digital baseband processing subsystem 5302 of the radio RF base station for the case of N = 4. Therefore, FIG. 53 shows the Cell-Wide.^t, B1^t, B2^t, B3^t, B4^tShows five digitally transmitted data streams 5308 between the two subsystems, indicated by. These streams can be sent on separate physical interfaces or can be multiplexed into a single physical interface between the two subsystems. Figure 53 further shows the Cell-Wide.^r, B1^r, B2^r, B3^r, B4^rIt shows five digitally received data streams 5310 between the two subsystems, indicated by. These streams can be sent on separate physical interfaces or can be multiplexed into a single physical interface between the two subsystems.

Every 1 millisecond LTE subframe interval in the FDD system, or every D subframe interval in the TDD system, the MAC (Medium Access Control) layer software 5312 needs to generate information about the five transmit data streams 5308. is there. One set of information is "Cell-Wide"^tCorresponding to, here, "Cell-Wide"^tIs a stream whose data is intended to be transmitted over the entire cell coverage area during the next 1 millisecond subframe interval. Each of the other four information sets is B1^t, B2^t, B3^t, And B4^tCorresponds to one of the four transmitted beam data streams marked with. Each transmit beam data stream is intended to be transmitted via a separate RF beam that "illuminates" a particular fixed cell subarea at the next 1 millisecond interval. The processing of the PHY (physical) layer software 5314 is 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 through the LTE air interface. Can be applied. Therefore, the PHY layer software 5314 can apply LTE physical resource block (PRB) allocation to information in each data stream 5308.

A digital sample for each transmitted data stream 5308 generated is transmitted to the RF beam signal 902, as well as the RF and antenna subsystem 5304, which includes the array antenna elements used to generate the Cell-Wide RF signal. Each of the five digital data streams 5308 is further processed to generate a Cell-Wide RF transmit signal in addition to the four RF transmit beam signals 902, which are transmitted through the air interface.

The receiving process for beamforming is similar to the transmitting process. In each 1 millisecond interval in the FDD system, or in each U subframe in the TDD system, the array antenna elements in the RF and antenna subsystem 5304 in addition to the separate processing components generate five digital receive signals 5310. However, one corresponds to each RF received beam generated at this interval, and one corresponds to a Cell-Wide RF received signal. These signals are Cell-Wide^r, B1^r, B2^r, B3^r, B^rAs shown in Figure 53, transmitted through an interface with the radio base station digital baseband subsystem 5302.

LTE is an OFDMA (Orthogonal Frequency Division Multiple Access) system. Orthogonal Frequency Division Multiple Access is a mechanism that multiplexes multiple users into an OFDM (Orthogonal Frequency Division Multiple Access) air interface. Some subcarrier frequencies include the overall LTE bandwidth for a particular system, where carrier spacing is subcarrier TS 36.211. Selected to be orthogonal to each other in the sense specified in a40. Spacing between subcarriers is typically 15 kHz. Multiple user access is achieved by assigning a subset of the entire subcarrier set to different users at different times. In this way, subcarrier resources are allocated to users in a time-sharing and frequency-sharing manner. LTE signals are assigned to users in units of 12 adjacent subcarriers (180kHz), called physical resource blocks (PRBs). This allocation typically includes 7 symbols for a time interval of 0.5 ms, and the modulation scheme for this symbol can be either QPSK, 16QAM, or 64QAM in the current version of the standard. The symbolic period of OFDMA is 66.7 microseconds.

The PRB and time domain are recognized as a set of resources, and the PRB is available for allocation to the UE in a given time slot. The time domain is divided into a series of frames, each of which is 10 milliseconds long. Each frame is composed of 10 subframes, each of which is 1 millisecond, and each subframe is composed of two slots, each of which is 0.5 milliseconds. For every 0.5 ms slot, there are 7 (typical) symbol time intervals. At each symbol time interval (66.7 μs), the symbol can modulate the assigned subcarriers. The combination of symbol time and subcarriers is called a resource element. There are 84 (7 × 12) resource elements for each PRB in each slot, and 168 resource elements for each PRB in each subframe. A view of resource elements (subcarrier frequency and symbol time axis) is called a resource grid.

A part of the resource element is assigned to a reference signal, and the reference signal is transmitted using a predetermined amplitude and phase. This signal is transmitted by the radio base station PHY layer software and the UE PHY layer software, allowing the receiving end to perform coherent demodulation of the radio channel or determine the radio channel state. Another resource element is assigned to the set of channels used to convey control information and other information. The remaining (most) resource elements are available for allocation to the UE for downlink user data transmission and uplink user data transmission.

Table 10 lists the set of reference signals used in downlink transmission and shows the function of each signal. Table 11 lists the set of physical layer data channels used in downlink transmission and shows the functionality of each data channel. Table 12 lists the set of reference signals used in uplink transmission and further describes its function. Table 13 lists the set of uplink physical layer data channels and shows their function. These tables can be used to determine the placement of each reference signal and each data channel in the data stream used in a periodic scanning RF beamforming system.

Table 10: Overview of downlink reference signals<img id="000024" he="99" wi="149" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Table 11: Overview of downlink physical layer data channels<img id="000025" he="83" wi="140" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Table 12: Overview of uplink reference signals<img id="000026" he="57" wi="147" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Table 13: Overview of uplink physical layer data channels<img id="000027" he="57" wi="147" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Which digital data stream to use on the interface between the baseband subsystem and the RF and antenna subsystems based on the function of each reference signal and each data channel, and when to transmit or receive each reference signal. , And when to send or receive information about each data channel. This decision can be made by using a digital data stream corresponding to the Cell-Wide RF signal, or by using a digital data stream corresponding to a particular RF beam signal covering the current user position. The resulting decisions are in Table 14 for the downlink reference signal, in Table 15 for the downlink physical layer data channel, in Table 16 for the uplink reference signal, and further for the uplink physical layer data channel. Can be shown in Table 17.

Table 14: Mapping of downlink reference signal to transmitted data stream<img id="000028" he="166" wi="145" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Table 15: Mapping of downlink physical layer data channels to outbound data streams<img id="000029" he="229" wi="152" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" /><img id="000030" he="99" wi="145" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Table 16: Mapping of uplink reference signal to received data stream<img id="000031" he="99" wi="149" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

Table 17: Mapping of uplink physical layer data channels to incoming data streams<img id="000032" he="151" wi="149" file="JP6251256B2_D0001.tif" img-format="tif" img-content="drawing" />

From Tables 14 and 15, the reference and physical layer data channel information transmitted to the UE using the transmit RF beam data stream corresponding to the RF beam signal covering the location of the UE is transmitted over the RF beam signal. The UE-specific reference signal used to enable the demodulation of user data and the CSI reference signal sent to the downlink to allow the UE to report the downlink channel condition, and the position of the UE. It can be seen that it can be limited to UE data sent via PDSCH when recognized. All other downlink reference signals and physical layer data channel information can be sent via the Cell-Wide transmit data stream. UE data can be sent to the RF and antenna subsystem via the Cell-Wide transmit data stream if the location of the UE is not recognized or if the data is further transmitted via the transmit RF beam data stream. In the latter case, transmission mode 2 (transmission diversity) can be used. Transmission mode 7 can be used if UE data is sent only to the transmit RF data stream (ie, includes logical antenna port 5, beamforming port).

From Tables 16 and 17, when the reference signal and physical layer data channel information received from the UE using the RF beam covering the position of the UE can be transmitted using the UE data and the position of the UE is recognized. PUSCH-DMRS that can be received via RF beam signal, SRS signal transmitted by UE and UE position are recognized when the radio base station determines the uplink channel status and the UE position is recognized. It can be seen that it is limited to UE data sent via PUSCH when it is done. All other uplink reference signals and physical layer data channel information can be received via the Cell-Wide receive data stream.

Therefore, the teachings presented in this disclosure are used to limit and guide the behavior of MAC layer software 5312 and PHY layer software 5314 in their operation in LTE radio base stations utilizing periodic scanning RF beamforming systems. can do. At each transmission time interval (TTI, ie, 1 millisecond interval of LTE frames) in each D subframe of the FDD or TDD system, the MAC layer software interacts with the PHY layer software and is transmitted during the TTI. A set of transport blocks for different data can be presented, and the MAC layer software can further indicate, for each transport block, a transmit beam data stream that will be used to transmit the data blocks. For each common channel, the PHY layer software can be pre-provisioned by the MAC layer software with a mapping to the transmit beam data stream. In addition, the PHY layer software can include appropriate reference signals in the set of transport blocks in the transmit data stream pre-provisioned or directed by the MAC layer at each TTI and presented to the PHY layer.

Similarly, at each TTI in each D subframe in an FDD system or TDD system (ie, at 1 millisecond intervals in LTE frames), the MAC layer software interacts with the PHY layer software to create a particular common or control channel. It can indicate a reference signal, or a set of resource elements or PRBs used to detect data about the uplink shared channel, and can also indicate a received beam data stream used to perform the detection process. The MAC layer software can reprovision the PHY layer software for some of these elements, eg, for the PRACH channel. It is important that the PHY layer software presents the received data stream to the MAC layer software and uses this received data stream to discover each element of the detection data presented to the MAC layer by the PHY layer. Can be done.

Another teaching in the present disclosure addresses the problem of locating a UE within a subarea covered by an RF beam generated in a periodic scanning RF beamforming system and tracking this UE. To better allow the radio base station MAC layer software to better determine which UEs can be scheduled for uplink and downlink data transmission, a MAC layer is created by each system. A list of RF beams can be maintained, where each list contains a set of UEs that are known to be in the subarea corresponding to the RF beam represented by this list.

Although only some embodiments of the present disclosure have been shown and described, those skilled in the art will appreciate these embodiments without departing from the ideas and scope of the present disclosure described in the claims below. It will be clear that many changes and modifications can be made. All patent applications and patents, both foreign and domestic, and all other publications referred to herein are incorporated herein in their entirety to the full extent permitted by law.

The methods and systems described herein, in part or in whole, can be deployed via 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, as a system or device relating to the machine, or as a computer program product embodied in a computer-readable medium running one or more machines. .. The processor can be part of a server, client, network infrastructure, mobile computer platform, fixed computer platform, or other computer platform. The processor can be any kind of computing or processing device capable of executing program instructions, code, binary instructions, and the like. A processor is any variant of a signal processor, digital processor, embedded processor, microprocessor, or coprocessor (computational coprocessor, graphics coprocessor, communication coprocessor, and the like), and the programs stored in them. It can be similar, or include them, that facilitates the execution of code or program instructions directly or indirectly. In addition, the processor can allow the execution of multiple programs, threads, and code. Threads can run concurrently to extend processor performance and facilitate simultaneous application operations. Depending on the implementation, the methods, program code, program instructions, and the like described herein can be executed in one or more threads. A thread can wake up another thread that can have an assigned priority associated with the thread, and the processor in some other order based on the priority or the instructions provided in the program code. You can run these threads based on. Processor Can include memory for storing methods, codes, instructions, and programs described herein and elsewhere. The processor can access the storage medium through an interface that can store the methods, codes, and instructions described herein and elsewhere. A processor-related storage medium for storing a method, program, code, program instruction, or other type of instruction that a computing or processing device can execute is, but is not limited to, one or more CDs. -Can include ROMs, DVDs, memories, hard disk drives, flash drives, RAM, ROMs, caches, and the like.

Processors can include one or more cores that can extend the speed and performance of multiprocessors. In embodiments, the processor can be similar to a combination of dual core processors, quad core processors, other chip level multiprocessors, and two or more independent cores (referred to as dies).

The methods and systems described herein, in part or in whole, are computer software on servers, clients, firewalls, gateways, hubs, routers, or other such computers and / or networking hardware. Can be deployed via a machine running. Software programs may relate to file servers, print servers, domain servers, internet servers, intranet servers, and other variants that may include secondary servers, host servers, distributed servers, and the like. it can. Servers include one or more memories, processors, computer-readable media, storage media, ports (physical and virtual), communication devices, and other servers, clients, machines, and devices, wired or wireless media, and the like. It can include interfaces that can be accessed through. The server may execute the methods, programs, or code described herein and elsewhere. In addition, other devices required to perform the methods described in this application can be considered as part of the infrastructure associated with the server.

The server is not limited to providing an interface with a client, another server, a printer, a database server, a print server, a file server, a communication server, a distributed server, and other devices including the same. Can be done. In addition, this concatenation and / or connectivity can facilitate remote execution of programs across networks. Networking of some or all of these devices can facilitate parallel processing of programs or methods in one or more locations without departing from the scope of the present disclosure. Additionally, any device attached to the server via an interface can include at least one storage medium capable of storing methods, programs, codes, and / or instructions. Centralized repositories can provide program instructions to be executed on various devices. In this embodiment, the remote repository can act as a storage medium for program code, instructions, and programs.

Software programs may relate to file clients, print clients, domain clients, internet clients, intranet clients, and other variants that can include, for example, secondary clients, host clients, distributed clients, and the like. it can. Clients include one or more memories, processors, computer-readable media, storage media, ports (physical and virtual), communication devices, and other clients, servers, machines, and devices, wired or wireless media, and the like. Can include interfaces that can be accessed via. The client may execute the methods, programs, or code described herein and elsewhere. In addition, other devices required to perform the methods described in this application can be considered as part of the infrastructure associated with the client.

A client is not limited to providing an interface with another device, including but not limited to a server, another client, a printer, a database server, a print server, a file server, a communication server, a distributed server, and the like. Can be done. In addition, this concatenation and / or connectivity can facilitate remote execution of programs across networks. Networking of some or all of these devices can facilitate parallel processing of programs or methods in one or more locations without departing from the scope of the present disclosure. Additionally, any device attached to the client via an interface can include at least one storage medium capable of storing methods, programs, applications, codes, and / or instructions. Centralized repositories can provide program instructions to be executed on various devices. In this embodiment, the remote repository can act as a storage medium for program code, instructions, and programs.

The methods and systems described herein can be deployed, in part or in whole, through a network infrastructure. Network infrastructure includes elements such as computer devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices, other active and passive devices, modules and / or components known to those of skill in the art. Can include. Computer-based and / or non-computer-based devices associated with network infrastructure can include storage media such as flash memory, buffers, stacks, RAM, ROM, and the like, in addition to other components. .. One or more network infrastructure elements may execute the processes, methods, program codes, instructions described herein and elsewhere.

The methods, program codes, and instructions described herein and elsewhere can be executed on a cellular network with multiple cells. The cellular network can be either 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 the like. The cell network can be GSM®, RPRS, 3G, EVDO, mesh, or any other network type.

The methods, program codes, and instructions described herein and elsewhere can be executed on or through mobile devices. Mobile devices can include navigation devices, cell phones, mobile phones, personal digital assistants, laptops, palmtops, netbooks, pagers, e-readers, music players, and the like. In addition to other components, these devices can include storage media such as flash memory, buffers, RAM, ROM, and one or more computer devices. Computer devices associated with mobile devices can execute program code, methods, and instructions stored therein. Alternatively, the mobile device can be configured to execute instructions in conjunction with other devices. Mobile devices have servers and interfaces and can communicate with base stations that are configured to execute program code. Mobile devices can communicate over peer-to-peer networks, mesh networks, or other communication networks. The program code can be stored in a storage medium associated with the server and executed by a computer device embedded in the server. Base stations can include computer devices and storage media. The storage device can store program code and instructions executed by the computer device associated with the base station.

Computer software, program code, and / or instructions can be stored and / or accessed in machine-readable media, which is used to calculate computer components, devices, and some time intervals. A recording medium for holding digital data, a semiconductor storage device known as a random access memory (RAM), and typically a large capacity storage device for further storage devices, such as an optical disk, a magnetic storage device. Hard disk forms such as tapes, drums, cards and other types, processor registers, cache memory, volatile memory, and non-volatile memory, optical storage devices such as CDs, DVDs, and flash memory (eg, Detachable media such as USB sticks or keys), floppy (registered trademark) discs, magnetic tapes, paper tapes, punch cards, stand-alone RAM discs, Zip drives, removable mass storage devices, offline, and similar And dynamic memory, static memory, read / write storage, variable storage, read-only storage, random access storage, sequential access storage, positionable storage, file specifiable storage, content specifiable storage Can include, network-mounted storage devices, storage area networks, bar codes, magnetic inks, and other computer memory such as the like.

The methods and systems described herein can transform physical and / or intangible elements from one state to another. The methods and systems described herein can further transform data representing physical and / or intangible elements from one state to another.

The elements described and illustrated herein include flowcharts and block diagrams throughout the drawing, including logical boundaries between the elements. However, by performing software or hardware engineering, these indicated elements and their functions utilize as monolithic software structures, as stand-alone software modules, external routines, code, services, etc., or any combination thereof. As a module to be executed, it can be executed on a machine via a computer executable medium, which medium has a processor capable of executing program instructions stored in the medium, and all such embodiments are disclosed herein. Can be within the range of. Examples of such machines include, but are not limited to, personal digital assistants, laptops, personal computers, mobile phones, other handheld computer devices, medical devices, wired or wireless communication devices, transducers, chips, etc. It can include computers, satellites, tablet PCs, electronic books, gadgets, electronic devices, devices with artificial intelligence, computer devices, networking devices, servers, routers and the like. Further, the elements shown in the flowchart and the block diagram, or any other logical component, can be implemented on a machine capable of executing program instructions. Accordingly, the drawings and description described above describe functional aspects of the disclosed system, unless the specific mechanism of software for implementing these functional aspects is explicitly stated. , Or otherwise, should not be inferred from these explanations unless it is clear from the context. Similarly, it will be appreciated that the various steps identified and described above can be different and the order of the steps can be applied to the particular application of the technology disclosed herein. All such modifications and modifications are intended to be included within the scope of this disclosure. Therefore, the illustration and / or description of the order for the various steps is specific.

The methods and / or processes described above, as well as these steps, can be implemented with hardware, software, or any combination of hardware and software suitable for a particular application. Hardware can include general purpose computers and / or dedicated computer devices, specific computer devices, or specific aspects or components of specific computer devices. The process can be implemented in one or more microprocessors, microcontrollers, embedded microcontrollers, programmable digital signal processors, or other programmable devices, along with external and / or internal memory. The process is further or instead embodied in application-specific integrated circuits, programmable gate arrays, programmable array logic, or any other device or combination of devices that can be configured to process electronic signals. Can be done. Furthermore, it will be appreciated that one or more processes can be implemented as computer executable code that can be executed on a machine readable medium.

Computer executable code is a structured programming language such as C, an object-oriented programming language such as C ++, or any other high-level or low-level programming language (assembly language, hardware description language, and database programming language). And can be generated using technology), these languages can execute one of the above devices, as well as heterogeneous combinations of processors, processor architectures, various hardware and software combinations, or programming instructions. It can be stored, compiled, or interpreted to run on any other machine.

Thus, in one aspect, each of the methods described above and combinations thereof may be embodied in computer executable code for performing these steps when performed on one or more computer devices. it can. In another aspect, the method can be embodied in the system for performing that step, distributed across devices in several ways, or integrating all functionality into a dedicated stand-alone device or other hardware. be able to. In another aspect, the means for performing the steps associated with the process described above can include any of the hardware and / or software described above. All such replacements and combinations are intended to be included within the scope of this disclosure.

Although the present disclosure has been disclosed in connection with the preferred embodiments shown and described in detail, various modifications and improvements to them will be readily apparent to those skilled in the art. Therefore, the ideas and scope of this disclosure are not limited to the examples described above, but should be understood in the broadest sense permitted by law.

All documents referred to herein are incorporated herein by reference.

102 eNB 104 User Equipment (UE) 108 MME 110 SGW 112 LTE Backhaul Network 114 PGW 118 PCRF 120 HRF 122 internet 124 server