System and method for creating and managing private subnetworks of LTE base stations

Abstract

To provide systems and methods for creating and maintaining a virtual subnetwork of base stations within a wider telecommunication network.SOLUTION: In an LTE base station, a subnetwork 100 includes a plurality of eNodeBs 125 inside the subnetwork and a connection aggregator S1-Conn 110 that is coupled among one or more MMEs 150 in an outer network. The connection aggregator intercepts all control plane messages between the MMEs and the internal eNodeBs, remaps eNodeB identifiers, and transmits repackaged messages so that the outer network sees the entire subnetwork as a single "giant" eNodeB.EFFECT: An operator of a virtual subnetwork is enabled to add and shut down eNodeBs as demand for connectivity fluctuates, and to do so such that all changes are unseen by the outer network.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to wireless communication base stations, and more particularly to large venues and urban environments. System for creating a private subnetwork of LTE base stations for use in The present invention relates to a system and method. [Background technology]

[0002] In the current state of LTE deployment, whether it is a network operator or a neutral host ,Anyone who deploys a base station (eNodeB) should be able to ,determine the capabilities of the eNodeB. This will make available a larger mobile network containing all relevant information. In many cases, an entity will deploy multiple eNodeBs as a local network. This is typically done in large venues such as stadiums, airports, and university campuses. In this case, the capabilities of each deployed eNodeB are made known to the larger mobile network. It is being done.

[0003] The drawback of the current state is that anyone deploying an eNodeB network is currently There is no way to reconfigure or redesign the network without impacting the entire network. Currently, one may think that the inner workings of a sub-network are related to the larger network. There is no way to deploy an LTE sub-network in such a way that it is hidden from the public.

[0004] Further drawbacks of the current state are: A given eNodeB has a 20-bit identity. Each eNodeB supports up to 256 cells. Each of them contains a unique 8-bit pattern for the 20-bit eNB ID. Each cell is identified by a global cell identifier (E-CGI) that is attached to the cell. NodeB supports 256 cells, which is basically impossible due to computational constraints. In practice, each eNodeB typically supports a maximum of about 12 cells. This not only limits the potential usefulness of a given eNodeB, but also reduces E-CGI address space. This also results in an inefficient use of time.

[0005] Therefore, a subnetwork can be managed by a single eNodeB in a larger network. A system for creating and managing LTE private sub-networks so that they are considered There is a need for systems and methods where the complexity of the subnetworks is greater than The subnetwork is hidden from the larger network, and the subnetwork is transparent to the larger network. The eNodeB may be redesigned and / or dynamically reconfigured as needed in a It can make the most of its ability to serve as many as 56 cells. Summary of the Invention

[0006] Aspects of the present invention include a plurality of internal baseband processors and a plurality of internal baseband processors. and connection aggregators coupled to the processors, each of the connection aggregators comprising a plurality of internal A telecommunications system that maintains multiple internal identifiers corresponding to one of the baseband processors. The connection aggregator receives the outgoing data from the internal baseband processor. Intercepts outbound messages and sends them to the internal baseband processor in the outbound messages. Replace the internal identifier of the virtual sub-network baseband processor with the virtual sub-network baseband processor identifier. The connection aggregator is further configured to: , intercepts inbound messages to the destination internal baseband processor, The virtual sub-network baseband processor identifier in the message is set as the destination internal identifier. Create a modified inbound message by replacing it, and then The baseband processor is configured to transmit the message to a destination internal baseband processor.

[0007] Another aspect of the present invention is a method for configuring a telecommunications subnetwork. This method involves receiving multiple PWS resume indication messages, each coming from an internal eNodeB. The PWS restart instruction message is intercepted and the internal eNodeB receives the PWS restart instruction message. extracting the identifier and one or more cell IDs and and allocating to a memory one or more cell IDs corresponding to the sub-network PW. and transmitting a subnetwork PWS resume instruction message. The message is generated by the virtual sub-network baseband processor from multiple PWS resume indication messages. The processor identifier and one or more cell IDs.

[0008] Another aspect of the present invention is a method for configuring a telecommunications subnetwork. This method relates to a method for generating a plurality of internal baseband processors, each of which corresponds to an internal identifier and an internal baseband processor. Corresponding internal baseband processors containing at least one cell ID for each cell Intercepting multiple initiation messages from the Extracting at least one cell ID and identifying each internal identifier and each at least one cell ID. storing the virtual sub-network baseband processor identifier in memory; generating a virtual sub-network baseband processor identifier and each one or transmitting a sub-network initiation message including the plurality of cell IDs.

[0009] Another aspect of the present invention is a source-internal-based To establish a connection between the band processor and the target's internal baseband processor The method includes generating a source internal baseband processor identifier. generating a target internal baseband processor identifier; and a source containing a baseband processor identifier and a target internal baseband processor identifier; a source configuration transfer message to the mobile management entity; and intercepting source configuration transfer messages to the mobility management entity. and a source internal baseband processor identifier and Extracting the target internal baseband identifier and Target configuration transfer including the target's internal baseband processor identifier and the target's internal baseband processor identifier Generates a target configuration transfer message and sends the target internal baseband and transmitting the data to the end processor.

[0010] Another aspect of the present invention is an internal eNodeB in a telecommunications sub-network. The present invention relates to a method for handing over a UE call from an external eNodeB to an external eNodeB. , a handover request including an internal eNodeB identifier and a target eNodeB identifier Sending a message, intercepting a handover required message, and Subnetwork eNodeB identifier is replaced with the virtual subnetwork eNodeB identifier. generating a subnetwork handover required message and generating a subnetwork handover required message; Sending handover messages to the MME and receiving handover commands from the MME and the virtual subnetwork eNodeB identifier is replaced with the internal eNodeB identifier. generating a sub-network handover command message; sending a handover command message to the internal eNodeB for transmission to the UE; It is equipped with:

[0011] Another aspect of the present invention is a method for reconfiguring a telecommunications subnetwork. This method assesses connection demand within a telecommunications subnetwork. and identifying a low activity internal baseband processor and Activity internal baseband processor to one or more neighboring internal baseband processors Handing off one or more UE connections to a server and low activity internal baseband Shutdown of the baseband processor and active internal baseband processor From the corresponding memory to the internal eNo corresponding to the low activity internal baseband processor and removing the DEV identifier and at least one cell ID.

[0012] Another aspect of the present invention is a method for reconfiguring a telecommunications subnetwork. This method assesses connection demand within a telecommunications subnetwork. identifying one or more high-demand internal baseband processors; and Instantiating an internal baseband processor and creating a virtual internal baseband processor assigning one or more cells to a processor and one or more high demand baseband processors handing off the UE connection from the processor to the virtual baseband processor and An initiation message containing an internal identifier corresponding to the band processor and one or more cell IDs. and sending a message to the server, intercepting the initiation message and providing an internal identifier and one or more and obtaining and storing a number of cell IDs from the initiation message.

[0013] Another aspect of the invention relates to a method for determining the location of an event within a venue. The method includes intercepting a first plurality of call establishment messages, each of the first plurality of call establishment messages coming from one of the plurality of UEs. and each call establishment message in the first plurality of call establishment messages is a voice call. determining whether a second plurality of call establishment methods correspond to a voice call; determining a call establishment message corresponding to each of the second plurality of call establishment messages; obtaining the establishment message times and extracting an internal base time from the second plurality of call establishment messages; obtaining a subband processor identifier and a subband processor identifier in a second plurality of call establishment messages; identifying a cluster of call establishment messages, Each call establishment message corresponds to a single eNodeB. The interval occurs within a narrow time window. [Brief explanation of the drawings]

[0014] [Figure 1] 1 illustrates an exemplary private subnetwork of an LTE base station according to the present disclosure. [Figure 2]1 illustrates an exemplary process for configuring a private subnetwork of an LTE base station according to the present disclosure. [Figure 3] 1 illustrates a typical process by which a UE establishes a connection with an eNodeB within a private sub-network. [Figure 4] 1 illustrates an exemplary process for establishing an X2 connection between two eNodeBs in a private subnetwork, according to the present disclosure. [Figure 5] 1 illustrates a typical process for performing an X2 handover between two eNodeBs within a private subnetwork. [Figure 6] 1 illustrates an exemplary process for performing an S1 handover between an eNodeB inside a private subnetwork and an eNodeB outside the private subnetwork. [Figure 7] 1 illustrates an exemplary process for reconfiguring private subnetworks based on increases or decreases in traffic demand. [Figure 8] 1 illustrates a typical process by which a private sub-network interacts with a positioning system implemented, for example, according to the LTE Positioning Protocol Annex (LPPa). [Figure 9] 1 illustrates an exemplary process by which a private sub-network may identify patterns in call establishment messages to identify a possible emergency and notify venue security. DETAILED DESCRIPTION OF THE INVENTION

[0015] FIG. 1 illustrates a typical private subnetwork (hereinafter, referred to as a "private subnetwork") of an LTE base station according to the present disclosure. The subnetwork 100 includes a connection aggregator (hereinafter referred to as a connection aggregator). , S1-Conn 110) and a calculation and maintenance module 120, each corresponding Each of the supervisor modules 130 has one or more corresponding cells 135 and a plurality of internal baseband processors (or internal eNodeBs 125) having Each internal eNodeB 125 may be a conventional eNodeB as defined in the LTE specifications. Standard S as performed between Node B and conventional MME (Mobility Management Entity) Each S1-Conn 110 is coupled to an S1-Conn 110 by an internal S1 connection 140. Each supervisor module 130 provides computing and maintenance services over a conventional IP connection 145. The network management module 120 may be coupled to the network management module 120.

[0016] The S1-Conn 110 connects to one or more MMEs via corresponding external S1 connections 155 Each external S1 connection 155 may be coupled to 150, each of which is defined in the LTE specification as Each internal S1 connection 140 is identical in that it is a standard S1 connection as defined. That's fine.

[0017] Also shown in FIG. 1 is an external eNodeB 160 having at least one corresponding cell 165. The external eNodeB 160 is connected to the illustrated MME 1 via an S1 connection 170. 50. Also, the one or more cells 135 / 165 may be in communication with 1 shows a UE 170 that may be in a variety of states.

[0018] The subnetwork 100 may be used in, for example, a stadium, an airport, a shopping center, or a university campus. It can be deployed or integrated in dense urban environments or large venues such as: The NodeB 125 can be a macrocell, small cell, femtocell, or distributed antenna system. Each internal eNodeB 125 may support any number of cells 135. may have

[0019] Individual internal eNodeBs 125 can be instantiated and de-instantiated as needed. Each is implemented as a pure software-based virtual baseband processor that can be or each may be dedicated hardware in close proximity to the corresponding RF and antenna components. implemented as a hardware-based baseband processor deployed in or any combination of the above. Although LTE-specific terminology is used to describe the As long as it is in communication with S1-Conn110, it will be able to use different or legacy RAT techniques. As used herein, a baseband processor and an eNode may be implemented. The terms B may be interchangeable.

[0020] S1-Conn 110 and the computing and maintenance module 120 (and possibly and possibly one or more of the internal eNodeBs 125 within the sub-network 100. a single location (e.g., one or more racks) in or near a distributed environment Implemented in software running on conventional server hardware that may be located on the Pure software-based virtual baseband program for the internal eNodeB 125 The advantage of having eNode processors is that they can be easily configured to handle fluctuations in traffic demand within a venue. Dynamically instantiating and de-instantiating B125 in subnetwork 100 This can be advantageous in that it maximizes the capacity of each internal eNode. With the eNodeB 125 implemented entirely in software, each internal eNodeB 125 Interaction with the corresponding supervisor module 130 and calculation and maintenance to allow easier configuration and maintenance from the security module 120. However, it is possible to implement hardware-based internal eNodeB1 25 instead of instantiating / de-instantiating the virtual internal eNodeB 125 It is understood that the number of active / inactive nodes may be varied.

[0021] FIG. 2 illustrates an exemplary process for configuring a subnetwork 100 according to the present disclosure. vinegar.

[0022] In step 205, the S1-Conn 110 establishes an S1 interface with each of the MMEs 150. At that time, S1-Conn 110 establishes the interface. NB ID (Virtual Sub-Network Baseband Processor Identifier) ​​and all internal To the MME 150, including all E-CGIs corresponding to each of the constituent cells of the NodeB 125. In response to this, each MME 150 issues an S1 configuration request message. By sending a constant response message to S1-Conn 110, S1-Conn 110 An external S1 connection 155 between the MME 150 and each MME 150 may be established.

[0023] In step 210, each internal eNodeB 125 starts up according to its nominal capabilities. Each internal eNodeB 125 has the same 20-bit identifier and the A plurality of 8 bits are allocated for each possible cell 135 that can correspond to odeB 125. This information is stored in a configuration file within each internal eNodeB 125. and can be provided by the corresponding supervisor module 130. Configuration information about the eNodeBs 125 may be stored in a distributed database. Examples of suitable distributed data sources may include systems such as consul and etcd. Assuming that all internal eNodeBs 125 have the same 20-bit identifier, each internal To uniquely identify the eNodeBs 125, each one must identify one of its cells 135 (e.g., For example, the 8-bit cell identifier of its first cell 135 is selected and used as the It may be appended to the 20-bit identifier to create a 28-bit eNodeB identifier. The identifier is the same as that used previously for the Home eNodeB (HeNB). This internal 28-bit eNodeB identifier is referred to herein as the "internal identifier." It can be called.

[0024] Upon powering up, each internal eNodeB 125 may, in step 215, The S1 connection with the S1-Conn 110 is established using the 2-bit eNodeB identifier. An example of how the eNodeB 125 may establish an S1 connection with the MME 150 is shown in FIG. This is described in GPP TS36.413. In this case, a given internal eNodeB 125 functions to establish an S1 connection with each MME 150. n110 intercepts each S1 configuration request from each internal eNodeB. 0 uses this information to establish an S1 interface with each internal eNodeB 125, It then generates and issues an S1 configuration response message to each of the internal eNodeBs 125. In this case, each of the internal eNodeBs 125 has many capabilities (actually a collection of MMEs 150). It "thinks" it has established an S1 interface with a single MME with What we actually did was to establish an internal S1 connection 140 with S1-Conn 110. do.

[0025] In step 220, each internal eNodeB 125 receives one or more functioning This start message contains the information that the MME 150 has. The identifier of the cell 135 and the cell identifier of its corresponding cell 135. In one embodiment, each internal eNodeB 125 is intercepted by an S1-Conn 110. In 3GPP TS36.413, the PWS resumes the PWS. The PWS Resume Indication message, an example of which is illustrated, contains the following information: E-CGI (Enhanced Cell Global ID) of each cell corresponding to B125, send The group of internal eNodeBs 125 (which is the internal 28-bit eNodeB identifier mentioned above) Global eNB ID, Tracking Information (TAI) for internal eNodeB125-supported cells Area Identifier) ​​list and emergency area ID for internal eNodeB125-supported cells Contains a list.

[0026] It is understood that the described functions performed by each internal eNodeB 125 are: machine-readable memory allocated to or associated with each corresponding internal eNodeB 125; stored in the corresponding eNodeB125 and by a dedicated processor embedded in the corresponding eNodeB125. runs on server hardware located at the venue or elsewhere in the subnetwork 100 Server processors or servers generated in cloud computing environments It may correspond to a sequence of computer instructions executed by a virtual machine. The same is true for the nn 110 and the calculation and maintenance module 120. These components are stored in non-volatile memory and correspond to the sub-network 100. Server computer hardware that may be located in or near the venue or distributed throughout the venue Each of these components may comprise computer instructions that can be executed on software. Depending on the given subcomponents in each of these components, C, C++, Java a, one or more scripting languages, or any combination thereof.

[0027] In step 225, the S1-Conn 110 receives the signal from each internal eNodeB 125. Each PWS resume instruction message is intercepted, and in step 230, each internal eNodeB Regarding 25, the internal 28-bit eNodeB identifier, the configured cell ID (E-CGI), and and other information provided in the corresponding PWS Resume Indication message. In addition to step 230, the S1-Conn 110 creates a B125 to itself, and assigns the 20-bit eNodeB ID common to B125 and the constituent cell ID ( E-CGI) and any additional information collected from each corresponding PWS Resume Instruction Message and add this information to the new "repackaged" PWS resume instruction message. S1-C The 20-bit eNodeB ID assigned to onn110 is the virtual subnetwork It may be referred to as a baseband processor identifier.

[0028] In step 235, the S1-Conn 110 Each PWS sends its own PWS resume indication message via its respective external S1 connection 155. It is sent to the corresponding MME 150.

[0029] Therefore, each MME 150 interacts only with the S1-Conn 110. Even in this case, a single cell may potentially have a large number of aggregate cells 135 (possibly as many as 256 cells). It behaves as if it is interacting with a "giant" eNodeB. Even if the internal eNodeB 125 is only interacting with S1-Conn 110 , MME 150. To achieve this, the S1-Conn 110 is used to connect a given MME 150 to an internal eNodeB 125. and each subsequent message between the MME 150 and a given UE 170 in both directions. For example, S1-Conn110 is stored in the memory allocated to S1-Conn110. Remaps cell IDs and other required information using a stored lookup table and repackaging the given message using the remapped information. For our purposes, from a given MME 150 The internal eNodeB 125 to which an incoming message is destined is identified by the message destination baseband. The processor may be referred to as a hand processor.

[0030] The above advantages include: First, the cell ID of each eNodeB is an 8-bit identifier. Suppose any given (non-home) eNodeB has a 20-bit identifier, and 2 As many as 56 cells can be allocated. However, given the practical limitations on computing power, And any given eNodeB typically has no more than 12 cells. The resulting subnetwork 100 is connected to a given eNodeB (in this case, a "giant" eNodeB). The S-Conn (110) that acts like a NodeB uses all 8 bits of the cell ID. This allows each internal eNodeB 125 to The system must have sufficient memory and computational resources (either dedicated hardware or is allocated in either provisioned cloud computing resources This is because

[0031] Second, an external network (for example, from the MME 150 to the outside) We only know of a single "giant" eNodeB that encompasses 110 functions. Then, the number of internal eNodeBs 125 (and the number of subsequent cells 135) is This means that one day a week may be full and other days may be full. This can be very useful for venues such as stadiums that may be quiet during peak hours. To accommodate changes in demand, each cell has multiple corresponding cells 135. eNodeBs 125 may be created and assigned, and all these changes are handled by external networks. It is hidden in the work.

[0032] It will be understood that the described functions performed by S-Conn 110 are further Stored in machine-readable memory allocated to or associated with 1-Conn 110 and dedicated by a dedicated processor or located at the venue or elsewhere in the subnetwork 100 generated in a cloud computing environment running on server hardware A sequence of computer instructions executed by a server processor or virtual machine represents.

[0033] FIG. 3 illustrates an exemplary process 3 for a UE 170 to establish a connection with an internal eNodeB 125. Indicates 00.

[0034] In step 305, the UE 170 and a given internal eNodeB 125 establish a connection. For example, the UE 170 may exchange appropriate conventional signaling to establish an internal eNode B 125, and then the internal eNodeB 125 The UE 170 may respond with a configuration message or the like. As a result, the UE 170 may Once connected, the internal eNodeB 125 has established an internal identifier corresponding to the UE.

[0035] In sub-process 310, the internal eNodeB 125 receives the S1-Conn 110 via the S1-Conn 110. As shown in Figure 3, subprocess 3 10 is based on the default bearer establishment procedure described in 3GPP TS24.301, for example. With some steps added, for example steps 315, 320, and 325 describes modifications / improvements to the conventional procedures described in the 3GPP technical specifications.

[0036] In step 315, the S1-Conn 110 receives the The default base address sent by the internal eNodeB 125, including the generated UE ID. Intercept the Ara establishment message.

[0037] In step 320, the S1-Conn (generated by the internal eNodeB 125) replaces the UE ID generated by the S1-Conn 110 with the unique This means that each of the internal eNodeBs 125 can Generates a UE ID without knowing any UE ID generated by any of the deB125 This is necessary because two eNodeBs 125 generate duplicate UE IDs. If this is possible, S1-Conn will 25, replacing the UE ID generated by the unique value and repackaging the message; A message is sent to the appropriate MME 150.

[0038] In step 325, the S1-Conn 110 receives the internal eNode Intercept the default bearer establishment message to B125 and remap the UE ID, The repackaged message is sent to the internal eNodeB 125 .

[0039] The purpose is to ensure that a given internal eNodeB 125 does not directly interact with the MME 150. and that the MME 150 does not directly interface with the internal eNodeB 125. In the former case, S1-Conn110 is It acts as an MME 150 for the internal eNodeB 125, and in the latter case, the S1-Con n110 acts as an eNodeB that interacts with MME150 (and UE170). It works.

[0040] In sub-process 330, the internal eNodeB 125 receives the S1-Conn 110 via the S1-Conn 110. 3, the subprocess 330 is , some additional procedures are added to the default bearer establishment procedure described in 3GPP TS24.301. The steps required to establish a dedicated bearer are the steps mentioned above. 320 and 325. As a result, the UE 170 and the MME 1 50, and at least one dedicated bearer is established between S1-Conn11 0 acts as an invisible intermediary between the internal eNodeB 125 and the MME 150.

[0041] Figure 4 shows a typical process for establishing an X2 connection between two eNodeBs 125. Indicates 00.

[0042] In step 405, the UE 170 receives a strong signal from another internal eNodeB 125. The UE 170 communicates with the currently connected source internal eNodeB 125 having the same signal. This is done by comparing the nearby internal eNodeBs 125 and ce by sending a measurement report identifying the source internal eNodeB 125 Step 405 can be a conventional process, an example of which is 3GPP TS36 From this information, the UE 170 determines the target for handover. Identify and recommend a get internal eNodeB 125.

[0043] In step 410, the source internal eNodeB 125 retrieves its valid Returning to step 210, each internal eNodeB have the same 20-bit eNodeB identifier as the default. To prevent collisions within 100, the supervisor module 120 of each internal eNodeB , each internal eNodeB 125 has 8 of its own cells (e.g., the first cell) It selects a 20-bit identifier and adds the 8-bit identifier of its own cell to its own 20-bit identifier. The spoofed eNodeB identifier is appended to the spoofed eNodeB identifier, which is referred to herein as the internal eNodeB identifier. Step 410 instructs the UE to create an internal eNodeB (HeNB) identifier. In addition, the source internal eNodeB 125 receives the measurement information from the UE 170 (via measurement reports). and obtains the E-CGI of the target cell identified by The 28-bit cell identifier is used.

[0044] In step 415, the source internal eNodeB 125 is conventionally connected to one of the MMEs 150. and transmitting an eNB configuration transfer command to the eNB. The source internal eNodeB 125 receives its own internal eNodeB identifier and the target internal eNodeB identifier. It identifies itself by an internal eNodeB identifier of the eNodeB identifier.

[0045] In step 420, S1-Conn 110 receives the In step 425, the S1-Conn 110 intercepts the source eNB configuration transfer. The internal eNodeB identifier of the source internal eNodeB 125 and the target internal eNodeB Extract 125 internal eNodeB identifiers (as well as other information in the eNB configuration transfer command) and uses this information to construct an MME configuration transfer command. The S1-Conn then sends the MME configuration transfer command to the target internal eNodeB 125. Send.

[0046] Once the configuration transfer is complete, the source internal eNodeB 125 and the target eNodeB 125 may establish an X2 connection between them. In this case, the S1-Conn 110 is connected to the source internal eNodeB 125 or the target eNodeB Neither of the eB125s seem to realize that they are not communicating directly with the MME150. In this way, the MME 150 functions as the MME 150. This is because the MME150 is not involved in the process of If there is only one eNodeB, the X2 connection will not exist. Because it does not exist.

[0047] Figure 5 shows a typical example for performing an X2 handover between two internal eNodeBs 125. 5 shows a process 500.

[0048] In step 505, the UE 170 receives the target cell 135 and the target internal Identifying the eNodeB 125 and the source internal eNodeB to which the UE 170 is currently connected 125. This process is substantially similar to step 405 of process 400. It's okay.

[0049] In step 510, the source internal eNodeB 125 Any data packets (downlink) corresponding to the UE 170 are sent via the established X2 connection. and possibly uplink) to the target internal eNodeB 125 .

[0050] In step 515, the target internal eNodeB 125 sends a path switch request message. The path switching request is sent to the target internal eNodeB 12. 5 target cell 135 TAI (Tracking Area Identity) and It includes the E-CGI of the target cell. S1-Conn110 relays this message to the associated MME 150.

[0051] In step 520, the target internal eNodeB125 sends a resource release message to the source internal eNodeB 125 via their mutual X2 connection, thereby completing the handover process of UE170 between the two internal eNodeBs125 within the subnetwork 100 in a manner hidden from the external network.

[0052] Figure 6 shows a typical process 600 for performing an S1 handover between an internal eNodeB125 and an external eNodeB160. This relates to the situation where UE170 moves out of the range of the internal eNodeB125 of the subnetwork 100. The steps of process 600 can be incorporated into the S1-based handover process.

[0053] In step 605, UE170 identifies the target cell 165 and the target external eNodeB160 and notifies the source internal eNodeB 125 to which UE170 is currently connected. This process may be substantially the same as steps 405 of process 400 and step 5 05 of process 500.

[0054] In step 610, the source internal eNodeB125 sends a handover required message to the associated MME150. In so doing, the source internal eNodeB125 uses its own internal eNodeB identifier within the message.

[0055] In step 615, S1-Conn110 sidelays the handover required message Receives its own 20-bit virtual sub-network baseband processor identifier and and the E-CGI of the cell that currently connects the UE 170 to the source internal eNodeB 125. The MME 150 then repackages the message using the RFC 2224 protocol and sends the message to the associated MME 150 .

[0056] In step 620, the MME 150 sends a handover command to the S1-Conn1 10. It is understood that the MME 150 interacts with the conventional eNodeB. It behaves as if it is operating.

[0057] In step 625, the S1-Conn 110 receives a handover request from the MME 150. The command is received, and the internal eNodeB identifier of the source internal eNodeB 125 is set to the eNB Remap IDs and source the repackaged handover command to the internal eNod Then, in step 630, the source internal eNodeB 12 5 sends a handover command to the UE 170.

[0058] One of the E-RABs (next generation radio access bearers) corresponding to UE170 is PDC If configured for P (Packet Data Convergence Protocol) preservation, the source internal eN The odeB 125 may send an eNB status transfer message to the associated MME 150. S1-Conn110 intercepts this message and sends it to the virtual sub-network baseband. Remaps information in the message to reveal the processor identifier and associates it with It may be sent to MME 150 (source MME).

[0059] In step 635, the source MME 150 sends a UE context release command to In step 640, the S1-Conn 110 However, the eNB ID is remapped to the internal eNodeB identifier of the source internal eNodeB 125. and sends the message to the source internal eNodeB 125.

[0060] In step 645, the source internal eNodeB 125 notifies the UE context release complete. The MME 150 then sends a completion message to the source MME 150.

[0061] In step 650, the S1-Conn 110 sends a UE context release complete message. The message is intercepted and the information is modified to reflect the virtual sub-network baseband processor identifier. remaps the information, repackages the message, and sends it to the source MME 150 do.

[0062] It is understood that (for example) between steps 615 and 620 and step 62 S as described in 3GPP TS23.401 occurring between 0 and 635 There are many steps to the traditional process of I-based handover. The steps are as follows: (e.g., MME 150, S-GW and P-GW (not shown) and external eNod It is understood that these The outer steps are well known and are described in detail in the referenced 3GPP documents.

[0063] Therefore, to the external network, the S1-based The handoff is to the "Giant" eNodeB represented by S1-Conn110. and an external eNodeB 160. The work is hidden from the external network.

[0064] FIG. 7 illustrates a method for reconfiguring the subnetwork 100 based on increases or decreases in traffic demand. 7 shows an exemplary process 700 for updating a subnetwork with changes to the external network. The subnetwork 100 grows and shrinks based on demand while hiding from the network. This makes it possible.

[0065] In step 705, the calculation and maintenance module 120 n110, an assessment of current traffic usage and demand may be performed. This may involve analyzing historical usage data as well as estimating near-future demand. For example, if the sub-network 100 is deployed in a stadium, the computation and maintenance The event module 120 may also monitor upcoming events to predict periods of high and low demand. The calendar may be stored in accessible memory, for example in a dense urban environment. For this deployment, the calculation and maintenance module 120 may be configured to calculate the time of day, day of the week, holidays, and The system may have historical data accumulated on demand based on dates and special events. If so, the calculation and maintenance module 120 calculates the current and near future demand. Perform appropriate analysis to estimate the requirements and accordingly determine the virtual internal eNodeB 125. to provide cloud-based computing capacity provisioning for hardware Take action to power on / off the internal eNodeB 125 in the base may be possible.

[0066] In addition, the virtual internal eNodeB 125 may set configurable threshold(s). assessing (i.e., determining) demand, including the actual demand and the threshold(s); The mechanism described in 3GPP may be used to compare the eNodeB 12. 5 may then transmit the results of the comparison to the calculation and maintenance module 120. The computing and maintenance module 120 then determines whether demand is below a low threshold (e.g., a configured If demand drops below a high threshold (for example, 5% of configured maximum capacity) or Alternatively, each of the eNodeBs may further determine whether the above-mentioned Further decisions are made and maintenance, such as warning signals, are calculated if any of the thresholds are exceeded. This mechanism generates a 30-second nonce every 15 minutes and may send it to the nonce module 120. The core network is connected via a northbound interface (not shown) that is also described in GPP. Standard PM-Stat files (performance measurements) sent to the network may be used. It is understood that variations are possible and are within the scope of the present disclosure.

[0067] Depending on the outcome of the assessment made in step 705, process 700 may take action. (not shown in FIG. 7) or the calculation and maintenance module 120 , by adding one or more internal eNodeBs 125 to the subnetwork 10 701, which may increase the capacity of the The maintenance module 120 may remove one or more internal eNodeBs 125. Thus, a sub-process path 702 may be taken that may reduce capacity.

[0068] Regarding subpath 701, the evaluation in step 705 determines whether the operation and maintenance If the module 120 determines that it needs additional capacity, it will The subnetwork module 120 proceeds to step 710 and determines where in the subnetwork 100 125. The method may execute instructions to identify whether additional internal eNodeBs 125 or multiple internal eNodeBs 125 are required. This can be done, for example, by determining the location of the internal eNodeB 125 with the greatest demand, and Determine availability of remote radio units and antenna hardware in the vicinity This may include:

[0069] In step 715, the calculation and maintenance module 120 Executes the command that results in a new internal eNodeB 125. The nonce module 120 may include one or more software programs installed on the local server hardware. and / or instantiating one or more virtual baseband processors based on the An instruction may be executed to power up a number of dormant hardware-based base stations.

[0070] In step 720, the calculation and maintenance module 120 The currently operating high-speed Issue a command to S1-Conn 110 to command the demand internal eNodeB 125 This may be done alternatively, whereby the calculation and maintenance module The module 120 then sends the corresponding internal eNodeB 125 a request to perform a UE connection handoff. , issue instructions to the appropriate supervisor module 130 via IP connection 145. stomach.

[0071] When a new eNodeB 125 is up and running, the identification The child mapping information needs to be updated. Therefore, in step 725, Each internal eNodeB 125 that comes online will have its own internal eNodeB identifier and and the constituent cell IDs. It is permissible to do so.

[0072] In step 730, the S1-Conn 110 receives each newly online internal Intercept one or more PWS resume indication messages from the eNodeB 125 and The odeB identifier and the corresponding cell ID are extracted and this information is sent to the S1-Conn110. Add to any existing mappings stored in your memory.

[0073] In step 735, S1-Conn 110 performs step 735 in process 200. Similar to 235, it may issue an indication to one or more MMEs 150 to resume its PWS. In this case, the external network is unaware of the addition of the new internal eNodeB 125. Instead, the external network may create a single "giant" with one or more additional cells. It just knows the eNodeB.

[0074] Regarding subpath 702, the assessment in step 705 determines whether the operation and maintenance If module 120 determines that subnetwork 100 has excess capacity, The calculation and maintenance module 120 proceeds to step 750 and 100 where one or more internal eNodeBs 125 should be shut down. The instruction may be executed to identify an internal eNodeB 125 that has insufficient demand. Internal identifiers of neighboring eNodeBs 125 that may be available for location and handoff purposes may include determining:

[0075] In step 755, the calculation and maintenance module 120 The UEs 170 are connected to the designated internal eNodeB 125 and the UEs 170 are connected to the designated internal eNodeB 125. Execute a command to handoff to a neighboring eNodeB that can provide As with step 720, this may occur in one or more ways. and the maintenance module 120 uses S1-Conn1 to command the handoff. 10 or the operation and maintenance module 120 issues instructions to the The relevant supervisor module 130 issues a command to perform the power-off. It is understood that such variations are possible and are within the scope of the present disclosure.

[0076] In step 760, the calculation and maintenance module 120 The internal eNodeB 125 specified by 0 may be shut down. Software-based In the case of a virtual internal eNodeB125, this is the server hardware of the subnetwork. This may involve terminating the corresponding virtual machine running on the This may involve powering down the appropriate hardware-based base station. The maintenance module 120 then passes this information to the associated supervisor module 130. This may be done by issuing the command:

[0077] In step 765, the S1-Conn 110 receives the terminated internal eNodeB identifier and executes instructions to remove the corresponding cell ID from its memory. In this case, S1-Conn 110 corresponds to the corrected (terminated internal eNodeB 125) The PWS issues a new resume indication with the cell ID list (minus the cell IDs that are being used).

[0078] Intercepting messages between the internal eNodeB 125 and the MME 150 and extracting information therein The S1-Conn110's ability to remap, repackage, and transmit is unmatched by any other For example, S1-Conn110 can receive the message from the internal eNodeB. and derive location information from one or more of the UEs 170 connected to them. You can put it out.

[0079] Figure 8 shows how S1-Conn110 is used for E-SMLC (Next Generation Serving Mobile Location Control). LTE communication between the service center 801 and the internal eNodeB 125 and the UE 170, respectively. Two typical methods for processing location-related information according to the Positioning Protocol Annex (LPPa) 8 shows a process 800 in which the E-SMLC 801 communicates with the subnetwork via one of the MMEs 150. The connection between the MME 150 and the E-SMLC 801 can be May be via the SL interface as described in GPP TS23.271. Details regarding Pa may be found in 3GPP TS36.455.

[0080] Through process 800, the E-SMLC 801 follows the LPPa procedure to and in fact, except for the intervention of S1-Conn110 as mentioned above. It acts as a proxy for the internal eNodeBs 125 within the subnetwork 100. interacting with a single "giant" eNodeB, the S1-Conn110 The E-SMLC functions as if it were a

[0081] In step 805, the E-SMLC 801 receives the Emitted Data by the S1-Conn 110. In this case, the E-SMLC8 issues a simulated request / command to the eNodeB. 01 does not know the internal eNodeB 125 of the subnetwork 100 and 10. Requests / commands are e.g. E-CID (Enhanced Observed Cell ID) measurement start request, E-CID measurement end command, OTDOA (Observed Cell ID) These interactions may include requests for information such as arrival time difference. S1-Conn110 is the actual location of the instantiation of S1-Conn110. For example, if the sub-network 100 is When deployed at a venue such as a stadium or airport, the The selected location may be a location such as a security room or main entrance of the venue; or The S1-Conn 110 stores a list of the locations of each cell 135 in the subnetwork 100. You may reply.

[0082] In step 810, the S1-Conn 110 receives and processes the request / command. Then, in step 820, S1-Conn 110 packages the response and sends it to E -Send to SMLC801.

[0083] FIG. 9 illustrates an S1-Conn 110 connected to one or more eNodes in a subnetwork 100. The device selectively intercepts requests from a large number of UEs 170 connected to the eB 125 and continues to or intervene with parties / entities related to the location of abnormal behavior among connected UEs 170. 9 illustrates an exemplary process 900 that may take action to notify a user of a problem.

[0084] In step 905, the plurality of UEs 170 are connected to a VoIP or 3G / 2G cell (not shown). These messages initiate a call with CS fallback to the A call can be routed to one internal eNodeB 125 or two or more neighboring internal eNodeBs 125 can be initiated via

[0085] In step 910, the S1-Conn 110 intercepts the call initiation message. In the case of VoIP, S1-Conn 110 extracts the QCI (QoS Class Identifier) ​​from each message. If QCI is equal to 1, the bearer to be established corresponds to a voice call. Alternatively, if the QCI is equal to 5, the message is identified as a VoIP IMS (IP Multimedia Subsystem) used to establish and release connections As with any message, the S1-Conn 110 eNodeB cell I uses its own virtual sub-network baseband processor identifier D, repackage the message, and send it to the intended MME 150 With each recognized VoIP call initiation, S1-Conn110 sends Related information corresponding to the start (e.g., UE identifier, internal eNodeB identifier, 28-bit Cell Identifier (ECGI), S-TMSI (SAE Temporary Mobile Subscriber Identifier), Message The device may execute instructions to record the time of receipt of a message, etc.

[0086] In step 915, the S1-Conn 110 confirms the call establishment in step 910. In addition to step 915, S1-Conn1 stores information related to the event. 10 executes instructions to identify patterns including a history of call patterns as a function of time. In the process of executing these instructions, the S1-Conn 110 may, for example, connected to an internal cell 135 or multiple neighboring cells 135 of a single eNodeB 125 A spike in call establishment messages from UEs 170 or multiple In the call establishment, such as multiple single instances of UE 170 initiating calls simultaneously, As used herein, simultaneous means identifying anomalies in the associated cell(s). At the position(s) corresponding to the 5 antenna(s), for example, 1 second, 5 seconds, etc. It may imply events within any single narrow time window. In this case, S1-Conn110 may store multiple identifiers, each corresponding to an identified UE 170 in the cluster.

[0087] In step 920, the S1-Conn 110 is connected to the S1-Conn 110 identified in step 915. The associated internal eNodeB 125 is instructed to provide the most recent lead angle value corresponding to each UE. Thereafter, in step 925, the associated internal eNodeB 125 Each UE 170 identified in step 915 may be provided with the corresponding requested advance angle information. .

[0088] In step 930, upon receiving these values, the S1-Conn 110 The call establishment procedures performed by E are in response to an event at their common location. may execute instructions to determine whether the advance angle values ​​are sufficiently clustered to indicate It is understood that the S1-Conn 110 then comprises one or more known classes of The instructions corresponding to the filtering algorithm may be executed. If the clustering indicates a possible event, the S1-Conn 110 The neighboring internal The S1-Conn 110 may then send a command to the eNodeB 125. The cluster location of the UE 170 may be determined based on the

[0089] In step 935, the S1-Conn 110 calculates the cluster location (by triangulation). (regardless of whether or not the instruction to determine the timing is executed) In this case, the S1-Conn 110 identifies a specific endpoint within the venue of the sub-network 100. An example of a predetermined entity is, for example, For example, it may include a customer room such as a security room.

Claims

1. a plurality of internal baseband processors; a connection aggregator operatively coupled to the plurality of internal baseband processors; each of the connection aggregators is connected to one of the plurality of internal baseband processors; maintain multiple internal identifiers corresponding to The connection aggregator is connected to an internal baseband processor that is one of the plurality of internal baseband processors. intercepting an outbound message from a baseband processor; The internal identifier of the internal baseband processor in the virtual sub-network base and sending the modified outbound message. It is configured to The connection aggregator may include a destination internal baseband processor that is one of the plurality of internal baseband processors. intercepting an inbound message to an internal baseband processor, the virtual sub-network baseband processor identifier in the message to the destination internal baseband processor Create a modified inbound message by replacing the internal identifier of the subband processor and sending the modified inbound message to the destination internal baseband processor. a telecommunications system configured to receive

2. The connection aggregator further comprises: a second internal baseband processor that is one of the plurality of internal baseband processors; intercepting an outbound message from the The internal identifier of the second internal baseband processor is set to the virtual sub-network baseband and transmitting the modified outbound message; a second destination internal baseband processor, which is one of the plurality of internal baseband processors; intercepting an inbound message to a processor and detecting the virtual a sub-network baseband processor identifier to said second destination internal baseband processor; creating a modified inbound message by replacing the internal identifier of the and transmitting the inbound message to the second destination internal baseband processor.

2. The telecommunications system of claim 1, configured to:

3. The connection aggregator may further comprise a plurality of sub-network baseband processors, each of which may be configured to communicate with the other sub-network baseband processors. the modified outbound message from the internal baseband processor including a baseband identifier; and the modified outbound message from the second internal baseband processor. configured to transmit a message to a mobility management entity (MME), The connectivity aggregator further receives from the MME a request for both the virtual sub-network based bridges. the inbound baseband processor for the destination internal baseband processor including a baseband processor identifier; the inbound message and the second destination internal baseband processor.

3. The telecommunications device of claim 2, configured to receive a message. system.

4. 10. The method of claim 9, wherein each of the plurality of internal baseband processors comprises an internal eNodeB.

1. A telecommunications system according to claim 1.

5. The telecommunications system of claim 4, wherein the internal eNodeB comprises a virtual eNodeB. communication system.

6. The telecommunications system of claim 5, wherein the virtual eNodeB comprises a supervisor module. Communication system.

7. a calculation and maintenance module coupled to each of said supervisor modules; The telecommunications system of claim 6 further comprising:

8. 5. The method of claim 4, wherein each internal identifier comprises a 28-bit internal eNodeB identifier. Communication system.

9. The 28-bit internal eNodeB identifier is a 28-bit identifier of a cell of the internal eNodeB.

9. The telecommunications system of claim 8, wherein the cell identifier corresponds to the cell identifier of the mobile station.

10. The virtual sub-network baseband processor identifier comprises 20 bits, The 0 bit is the same as the first 20 bits of the 28-bit internal eNodeB identifier.

9. The telecommunications system of claim 8.

11. 1. A method for configuring a telecommunications subnetwork, comprising: each of which is a corresponding one of a plurality of internal baseband processors in said sub-network. intercepting a plurality of messages coming from the An internal baseband processor identifier and one or more Extracting a cell ID; Each internal baseband processor identifier and corresponding one or more cell IDs are stored in a memory. and assigning corresponding to the plurality of intercepted messages, and a virtual sub-network baseband processor identifier and the one or more cell IDs sending a subnetwork message including A method for providing the above.

12. Each of the plurality of messages is a public warning system (PWS) restart instruction message. The method of claim 11 .

13. The method of claim 11 , wherein each of the plurality of messages is an initiation message.

14. The virtual sub-network baseband protocol included in the sub-network message The method of claim 11 , further comprising generating a processor identifier.

15. Source internal baseband processor and timer in telecommunications subnetwork 1. A method for establishing a connection between a target internal baseband processor, the method comprising: generating a source internal baseband processor identifier; generating a target internal baseband processor identifier; the source internal baseband processor identifier and the target internal baseband processor identifier generating a source configuration transfer message including a processor identifier; sending the source configuration transfer message to a mobility management entity; intercepting the source configuration transfer message to the mobility management entity; the source internal baseband processor identifier and and extracting the target internal baseband identifier; the source internal baseband processor identifier and the target internal baseband processor identifier generating a target configuration transfer message including a processor identifier; Sending the target configuration transfer message to the target internal baseband processor To believe A method for providing the above.

16. 16. The method of claim 15, wherein the source configuration transfer message comprises an eNB configuration transfer message. The method described.

17. 10. The method of claim 9, wherein the target configuration transfer message comprises a MIME configuration transfer message.

15. The method according to claim 15.

18. Generating the source internal baseband processor identifier comprises: generating a 28-bit internal identifier, the 28-bit internal identifier being a 20-bit eNodeB an 8-bit identifier of a cell corresponding to said source internal baseband processor; The method of claim 15, comprising:

19. The generating of the target internal baseband processor identifier comprises:

16. The method of claim 15, comprising obtaining a 28-bit cell identifier from the

20. Internal eNodeB to external eNodeB within a telecommunications subnetwork 1. A method for handing over a UE call to a mobile station, comprising: Handover requirements including internal eNodeB identifier and target eNodeB identifier Sending messages and Intercepting the handover required message; Replace the internal eNodeB identifier with a virtual sub-network eNodeB identifier. generating a subnetwork handover required message; sending the subnetwork handover required message to an MME; receiving a handover command from the MIME; replacing the virtual sub-network eNodeB identifier with the internal eNodeB identifier; generating a sub-network handover command message in addition to the sub-network handover command message; The subnetwork handover command message is sent to the UE. and transmitting the data to the internal eNodeB. A method for providing the above.

21. receiving a UE context release command message from the MME; replacing the virtual sub-network eNodeB identifier with the internal eNodeB identifier; generating a Sub-Network UE Context Release Command message in addition to the The subnetwork UE context release command message is sent to the internal eNode Sending to B 21. The method of claim 20, further comprising:

22. 1. A method for reconfiguring a telecommunications subnetwork, comprising: assessing connection demand within said telecommunications sub-network; Based on the assessment of connection demand within said telecommunications subnetwork, Identifying an activity internal baseband processor; The low activity internal baseband processor may be connected to one or more neighboring internal baseband processors. handing off one or more UE connections to a band processor; shutting down the low activity internal baseband processor; from a memory corresponding to an active internal baseband processor, an internal eNodeB identifier corresponding to the internal baseband processor and at least one Removing the cell ID; A method for providing the above.

23. assessing connection demand within the telecommunications subnetwork, Demands on the internal baseband processor and pre-configured low activity states 23. The method of claim 22, comprising comparing the signal to a predetermined threshold.

24. 24. The method of claim 23, wherein the threshold indicating the low activity state is based on a percentage of maximum capacity. How to post.

25. 1. A method for reconfiguring a telecommunications subnetwork, comprising: assessing connection demand within said telecommunications sub-network; based on an assessment of connection demand within said telecommunications subnetwork, or identifying a plurality of high-demand internal baseband processors; instantiating a virtual internal baseband processor; assigning one or more cells to the virtual internal baseband processor; The one or more high-demand baseband processors are connected to the virtual baseband processor. handing off the UE connection to the remote server; an internal identifier corresponding to the virtual baseband processor and one or more cell IDs; sending an initiation message including: Intercepting the initiation message; obtaining the internal identifier and the one or more cell IDs from the origination message; Storing and A method for providing the above.

26. assessing connection demand within the telecommunications subnetwork, Demand on the internal baseband processor and a pre-set threshold indicating a high demand condition.

26. The method of claim 25, comprising comparing:

27. 27. The method of claim 26, wherein the threshold indicating the high demand condition is based on a percentage of maximum capacity.

Images