# US 2014/0155019 A1 · Moving cellular communication system operative in an emergency mode > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2014/0155019 A1 - Document ID: US20140155019A1 - Status: Published application - Kind: A1 - Application number: 14/004,291 - Filed: 2012-03-08 - Published: 2014-06-05 - Earliest claimed: 2011-03-10 - Assignees: Elta Systems Ltd. - Inventors: Adi SCHWARTZ; Yaakov Shoshan; Itay Sherman; Udi Weinsberg - Web page: https://patentgrep.com/patent/US20140155019A1 ## CPC - H04W 40/22: using selective relaying for reaching a BTS [Base Transceiver Station] or an access point - H04B 7/15542: {Selecting at relay station its transmit and receive resources (selection of wireless resources by user or terminal H04W72/02; arrangements affording multiple use of the transmission path by two-dimensional division of the resources H04L5/0003, or by allocating sub-channels H04L5/003)} - H04B 7/1555: {Selecting relay station antenna mode, e.g. selecting omnidirectional -, directional beams, selecting polarizations} - H04B 7/2606: {Arrangements for base station coverage control, e.g. by using relays in tunnels} - H04J 11/005: {of intercell interference} - H04J 11/0056: {Inter-base station aspects} - H04L 1/0018: {based on latency requirement} - H04L 61/2517: using port numbers - H04W 4/40: for vehicles, e.g. vehicle-to-pedestrians [V2P] - H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS] - H04W 8/085: {involving hierarchical organized mobility servers, e.g. hierarchical mobile IP [HMIP]} - H04W 8/26: Network addressing or numbering for mobility support - H04W 28/0215: {based on user or device properties, e.g. MTC-capable devices (services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51)} - H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)} - H04W 28/14: using intermediate storage - H04W 36/04: Reselecting a cell layer in multi-layered cells - H04W 40/02: Communication route or path selection, e.g. power-based or shortest path routing - H04W 72/02: Selection of wireless resources by user or terminal - H04W 72/0453: Resources in frequency domain, e.g. a carrier in FDMA - H04W 72/21: in the uplink direction of a wireless link, i.e. towards the network - H04W 72/23: in the downlink direction of a wireless link, i.e. towards a terminal - H04W 72/30: Resource management for broadcast services - H04W 76/10: Connection setup - H04W 76/11: Allocation or use of connection identifiers - H04W 76/12: Setup of transport tunnels - H04L 2212/00: Encapsulation of packets - H04W 40/00: Communication routing or communication path finding - H04W 72/00: Local resource management - H04W 80/04: Network layer protocols, e.g. mobile IP [Internet Protocol] - H04W 84/005: {Moving wireless networks} - H04W 84/045: {using private Base Stations, e.g. femto Base Stations, home Node B} - H04W 84/047: {using dedicated repeater stations} - H04W 88/04: adapted for relaying to or from another terminal or user - H04W 88/08: Access point devices - H04W 88/16: Gateway arrangements - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - H04B: TRANSMISSION - H04J: MULTIPLEX COMMUNICATION (transmission in general H04B; peculiar to transmission of digital information H04L5/00; systems for the simultaneous or sequential transmission of more than one television signal H04N7/08; in exchanges H04Q11/00; stereophonic systems H04S) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A communication system comprising moving relay/s including base- and mobile-station functionality and a radio manager, all co-located, emergency moving relay/s further including a simulated stationary network that includes a simulated IP connectivity gateway communicating with a simulated mobility management entity and simulating the operation of a stationary network; the emergency moving relay being a root of a subtree including moving relay/s and mobile station/s, and utilizing its mobile-station functionality, base station functionality and radio manager for normal and emergency operation including communicating to a designated mobile station in the subtree each message received from a moving relay mobile in the subtree, the message having an IP address of the designated mobile station; or communicating to the simulated stationary network each message received from a moving relay/mobile station in the subtree and having an IP address not matching any mobile station in the subtree. ## Claims ### Claim 1 A moving cellular communication system forming part of a cellular communication network having a core element, the system comprising: at least one emergency moving relay including: at least one base station functionality serving at least one mobile station; at least one mobile station functionality providing at least one backhauling link toward the core element; and a relay resource manager operative to manage at least one resource pertaining to at least one of the base station functionality and mobile station functionality, all co-located, wherein the relay resource manager includes a core functionality operative, selectably, to take over at least one core function performed by said core element, for said at least one mobile station served by said base station functionality. ### Claim 2 (depends on 1) The system according to claim 1 wherein the core functionality takes over said functionality in real time and without disrupting ongoing communication over the network. ### Claim 3 (depends on 1) The system according to claim 1 wherein the core functionality is also operative, selectably, to hand back said at least one functionality taken over from said core element. ### Claim 4 (depends on 1) The system according to claim 1 wherein said core functionality comprises connecting between at least a pair of mobile stations characterized in that at least one core function pertaining to said pair which was previously performed at the core element is now performed by the core functionality of the relay resource manager. ### Claim 5 (depends on 1) The system according to claim 1 wherein said core functionality comprises connecting between: at least one mobile station characterized in that the core element previously performed at last one core function for the mobile station whereas the core functionality of the relay resource manager now performs said core function for the mobile station; and at least one additional mobile station characterized in that the core element still performs said at last one core function for the additional mobile station's core. ### Claim 6 (depends on 1) The system according to claim 1 wherein said at least one core function comprises connecting between at least one mobile station characterized in that the core element previously served as the mobile station's core whereas the core functionality of the relay resource manager now serves as the mobile station's at least one core function and an application service server. ### Claim 7 (depends on 6) The system according to claim 6 wherein said server includes one of the following types of servers: internet server, internet gateway, terrestrial communication network server, terrestrial communication network gateway, video broadcasting server, video conference server, gaming server, voice calls server, SIP server, mapping server, messaging server, data services server. ### Claim 8 (depends on 3) The system according to claim 3 wherein the core functionality hands back said at least one core function without disrupting ongoing communication over the network. ### Claim 9 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one mobility-management function in the core element's functioning. ### Claim 10 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one policy-management and control function in the core element's functioning. ### Claim 11 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one QoS-management function of the core element's functioning. ### Claim 12 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one load-management function of the core element's functioning. ### Claim 13 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one billing-management function of the core element's functioning. ### Claim 14 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one mobility-management function of the core element's functioning. ### Claim 15 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one policy-management and control function of the core element's functioning. ### Claim 16 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one QoS-management function of the core element's functioning. ### Claim 17 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one load-management function of the core element's functioning. ### Claim 18 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one billing-management function of the core element's functioning. ### Claim 19 (depends on 1) The system according to claim 1 wherein the core functionality includes a simulated stationary network having a simulated IP connectivity gateway operative to communicate with a simulated mobility management entity and said simulated stationary network simulates the operation of a stationary network. ### Claim 20 (depends on 1) The system according to claim 1 wherein said emergency moving relay is a root of a sub tree that includes at least one moving relay and at least one mobile station, and is configured for utilizing its mobile station functionality, base station functionality and radio manager for operating in at least the following modes of operations: i. normal mode of operation wherein the emergency moving relay communicating with other relays in the network and with the stationary network; ii. in response to an emergency event, operating in an emergency mode of operation, including a. communicating to a designated mobile station in the sub-tree each message that was received from a moving relay or a mobile station in said sub-tree and said message having an IP address of the designated mobile station; or b. communicating to said core functionality each message that was received from a moving relay or a mobile station in said sub-tree and having an IP address that does not match any mobile station in the sub-tree. ### Claim 21 (depends on 1) The system according to claim 1 and also comprising at least one moving relay other than said emergency moving relay. ### Claim 22 (depends on 20) The system according to claim 20, wherein said core functionality is further operative for simulating at least one application service having at least one respective application IP address, and wherein said operating in an emergency mode of operation, further includes communicating, to a designated application service in said core functionality, each message, received from a moving relay or mobile station in said sub-tree, and having an IP address of the designated application service. ### Claim 23 (depends on 20) The system according to claim 20, wherein said emergency event includes a detected disconnection of the emergency relay from another relay. ### Claim 24 (depends on 1) The system according to claim 1, wherein said core functionality further includes a router service application. ### Claim 25 (depends on 20) The system according to claim 20, wherein said emergency event includes a detected disconnection of the emergency relay from a stationary network. ### Claim 26 (depends on 20) The system according to claim 20, wherein said emergency relay is configured to revert to operate in accordance with said normal mode, upon termination of an emergency event. ### Claim 27 (depends on 1) The system according to claim 1 wherein said at least one emergency moving relay comprises a plurality of at least one emergency moving relays to accommodate for a situation of separation of a subset of moving relays from a larger group of moving relays necessitating each of the two separate groups is having one of its core element or its core functionality. ### Claim 28 An emergency communication method for a moving cellular communication system forming part of a cellular communication network having a core element, the method comprising: providing at least one emergency moving relay including: at least one base station functionality serving at least one mobile station; at least one mobile station functionality providing at least one backhauling link toward the core element; and a relay resource manager operative to manage at least one resource pertaining to at least one of the base station functionality and mobile station functionality, all co-located; and providing the relay resource manager with a core functionality operative, selectably, to take over at least one core function performed by said core element, for said at least one mobile station served by said base station functionality. ### Claim 29 (depends on 28) The method according to claim 28 wherein the core element serves a core of a static cellular communication network. ### Claim 30 (depends on 28) The method according to claim 28 wherein the core element serves a core of a moving cellular communication network. ### Claim 31 (depends on 1) The system according to claim 1 wherein said mobile station comprises a mobile station functionality of another relay. ### Claim 32 (depends on 1) The system according to claim 1 wherein the core functionality takes over said functionality while backhauling link is active. ### Claim 33 (depends on 1) The system according to claim 1 wherein the core functionality takes over said functionality while said at least one mobile station functionality is connected to one of: another relay base station functionality; and a static base station. ### Claim 34 (depends on 32) The system according to claim 32 wherein said taking over is activated responsive to measurements collected by one of said at least one mobile station functionality and said at least one base station functionality. ### Claim 35 (depends on 34) The system according to claim 34 wherein said measurements includes link quality parameters. ### Claim 36 (depends on 34) The system according to claim 34 wherein said measurements includes at least one of: SNR, SNIR, SIR, BER, BLER, PER, Eb/No, Ec/No, Ec/Io, RSSI, RSRP, RSRQ. ### Claim 37 (depends on 1) The system according to claim 1, wherein the core functionality takes over said functionality while backhauling link is not active. ### Claim 38 (depends on 8) The system according to claim 8 wherein said handing back is done in response to mobile station functionality connected to one of: other relay base station functionality or static base station. ### Claim 39 (depends on 9) The system according to claim 9 wherein the at least one mobility-management function comprises at least one of: LTE MME, 3G RNC and WiMAX ASN. ### Claim 40 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one gateway function of the core element's functioning. ### Claim 41 (depends on 40) The system according to claim 40 wherein said gateway function comprises at least one of LTE PDN-GW function, and LTE Serving-GW function, and 3G GGSN, and 3G SGSN, and WiMAX CSN. ### Claim 42 (depends on 1) The system according to claim 1 where said at least one mobile station functionality is not connected to another relay base station functionality and it is not connected to a static base station. ### Claim 43 A moving cellular communication system comprising: at least one moving relay including at least one base station functionality and at least one mobile station functionality and a relay resource manager, all co-located, at least one emergency moving relay from among said moving relays further including a simulated stationary network that includes a simulated IP connectivity gateway operative to communicate with a simulated mobility management entity; said simulated stationary network simulates the operation of a stationary network; said emergency moving relay being a root of a sub tree that includes at least one moving relay and at least one mobile station, and is configured to utilize its mobile station functionality, base station functionality and relay resource manager for operating in at least the following modes of operations: (i) normal mode of operation wherein the emergency moving relay communicates with other relays in the network and with the stationary network; (ii) in response to an emergency event, operating in an emergency mode of operation, including: a. communicating to a designated mobile station in the sub-tree each message that was received from a moving relay or a mobile station in said sub-tree and said message having an IP address of the designated mobile station; or b. communicating to said simulated stationary network each message that was received from a moving relay or a mobile station in said sub-tree and having an IP address that does not match any mobile station in the sub-tree. ### Claim 44 (depends on 43) The system according to claim 43, wherein said simulated stationary network further includes simulating at least one application service having a respective application IP address, and wherein said operating in an emergency mode of operation, further includes: communicating to a designated application service in said simulated network each message that was received from a moving relay or a mobile station in said sub-tree and said message having an IP address of the designated application service. ### Claim 45 (depends on 43) The system according to claim 43, wherein at least one of said moving relays being an upgraded moving relay. ### Claim 46 (depends on 43) The system according to claim 43, wherein said relay resource manager further includes a router service application. ### Claim 47 (depends on 43) The system according to claim 43, wherein said emergency event includes detecting disconnection of the emergency relay from the stationary network. ### Claim 48 (depends on 43) The system according to claim 43, further comprising, in response to undo emergency event, said emergency relay is configured to revert to operate in accordance with said normal mode. ### Claim 49 (depends on 2) The system according to claim 2 wherein said core functionality's taking over is performed by at least one of: manual operation and autonomous operation. ### Claim 50 (depends on 49) The system according to claim 49 wherein said autonomous operation is performed by a command originated by at least one of: an internal element of said emergency moving relay, an internal element of a relay other than said emergency moving relay, an element of said cellular communication network and an element external to said cellular communication network. ### Claim 51 (depends on 3) The system according to claim 3 wherein said core functionality's handing back is performed by at least one of: manual operation and autonomous operation. ### Claim 52 (depends on 51) The system according to claim 51 wherein said autonomous operation is performed by a command originated by at least one of: an internal element of said emergency moving relay, an internal element of a relay other than said emergency moving relay, an element of said cellular communication network and an element external to said cellular communication network. ### Claim 53 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one IP-connectivity gateway function of the core element's functioning. ### Claim 54 (depends on 1) The system according to claim 1 wherein the core functionality's take-over of the at least one core function from the core element includes taking over at least one security management function of the core element's functioning. ### Claim 55 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one connectivity gateway function of the core element's functioning. ### Claim 56 (depends on 3) The system according to claim 3 wherein the core functionality's hand-back of the at least one core function from the core element includes handing back at least one security management function of the core element's functioning. ### Claim 57 (depends on 20) The system according to claim 20, wherein said core functionality is further operative for simulating at least one application having at least one respective application IP address, and wherein said operating in an emergency mode of operation, further includes communicating, to a designated mobile station in the sub-tree, each message, received from said application having an IP address of the designated application. ### Claim 58 (depends on 1) The system according to claim 1 wherein the core functionality comprises an IP connectivity gateway and a mobility management functionality. ### Claim 59 (depends on 1) The system according to claim 1 wherein the core functionality also comprise identification user data information storage and authentication functionality. ### Claim 60 (depends on 59) The system according to claim 59 wherein the identification user data information storage and authentication functionality stores and shares with the mobility management entity subscriber's information. ### Claim 61 (depends on 59) The system according to claim 59 employing a home subscriber server which comprises an LTE HSS. ### Claim 62 (depends on 58) The system according to claim 58 wherein the IP connectivity gateway comprises an LTE P/S-GW entity at the core and the mobility management functionality comprises an LTE MME. ### Claim 63 (depends on 1) The system according to claim 1 wherein a tunnel that was connecting the static network core P/S-GW to the relay's base station functionality and was originally to be terminated at the core network P/S-GW, whose tunnel header destination address was said P/S-GW, is terminated in a local simulated P/S-GW by setting said tunnel's tunnel header destination address to the local simulated P/S-GW. ### Claim 64 (depends on 1) The system according to claim 1 wherein communication in an emergency mode in a multi-hop scenario is effected by terminating a tunnel that was originally to be terminated at the core network P/S-GW by the root of a disconnected moving relay sub-tree that simulates the core network and wherein a second moving relay and mobile stations anchored thereto are unaware of the emergency event. ### Claim 65 (depends on 1) The system according to claim 1 wherein communication is based on GPRS tunneling, and wherein the relay resource manager alters at least one tunnel, so that it can enable to communicate with the source and destination of said tunnel. ### Claim 66 (depends on 65) The system according to claim 65 and wherein, when an undo emergency event is received, the relay resource manager is operative to alter local (emergency-mode) tunnels to the original tunnels (normal-mode). ### Claim 67 (depends on 66) The system according to claim 66 wherein the resource manager alters local (emergency-mode) tunnels to the original tunnels (normal-mode) by creating an alternative using a GTP-C standard tunnel by sending a create packet data protocol context. ### Claim 68 (depends on 65) The system according to claim 65 wherein said relay resource manager alters said at least one tunnel e.g. by creating an alternative using a GTP-C standard tunnel by sending a create packet data protocol context, Create Bearer Request to its collocated core. ### Claim 69 (depends on 67) The system according to claim 67 wherein said GTP-C standard tunnel comprises a 3GPP TS 29.274 tunnel. ### Claim 70 (depends on 1) The system according to claim 1 wherein User and control plane data goes through the mobile station functionality and Base station functionality and wherein, when there is an emergency event, all relays in a relevant topology tree change to emergency mode. ### Claim 71 (depends on 70) The system according to claim 70 and wherein connections are made between the relays in the topology tree in order to form one unified tree. ### Claim 72 (depends on 1) The system according to claim 1 wherein a Network event listener sniffs standard interfaces (e.g. S1) and notifies of at least one change in the network to the Network event listener's subscribers. ### Claim 73 (depends on 72) The system according to claim 72 wherein a Network Event Handler which is a Network event listener's subscriber is responsible for synchronization of a local EPC core to a last known state of the core element in case of an emergency event. ### Claim 74 (depends on 72) The system according to claim 72 wherein a Network Event Handler which is a Network event listener's subscriber is responsible for synchronization of the stationary core state to the state of the local EPC core (Stand-Alone Subsystem) in case of an undo emergency event. ### Claim 75 (depends on 73) The system according to claim 73 wherein the Network Event Handler synchronizes the local EPC core to the last known state of the core element, in case of emergency, by: a. sending, for each disconnected nodes a “create packet data protocol (PDP)” context request to a local simulated mobility management entity; and b. enabling an alternate tunnel by sending a modify bearer request for each disconnected bearer to a local simulated P/S-GW in case of emergency. ### Claim 76 (depends on 74) The system according to claim 74 wherein the Network Event Handler synchronizes the stationary core state to the state of the local EPC core (Stand-Alone Subsystem) in case of an undo emergency event by: sending, for each reconnected node, a create context request to the stationary or remote-simulated network mobility management entity; and sending a modify bearer request for each reconnected tunnel to the stationary or remote-simulated network P/S-GW. ### Claim 77 (depends on 72) The system according to claim 72 wherein said change comprises a disconnection from the core. ### Claim 78 (depends on 72) The system according to claim 72 wherein said change comprises attachment of a user. ### Claim 79 (depends on 72) The system according to claim 72 wherein said change comprises creation of a bearer. ### Claim 80 (depends on 72) The system according to claim 72 wherein the Network event listener's subscribers include the Relay Resource Manager. ### Claim 81 (depends on 72) The system according to claim 72 wherein the Network event listener's subscribers include a Network Event Handler. ### Claim 82 (depends on 28) The method according to claim 28 and also comprising informing idle mode mobile stations (MSs) of a disconnection caused by an emergency event. ### Claim 83 (depends on 82) The method according to claim 82 wherein said informing comprises: changing a public land mobile network (PLMN) ID to another public land mobile network (PLMN); and broadcasting said public land mobile network (PLMN) ID to all Base station functionalities (TeNb) in a cluster. ### Claim 84 (depends on 82) The method according to claim 82 wherein the public land mobile network (PLMN) is operative to inform at least one mobile station of the identity of a head relay of a cluster. ### Claim 85 (depends on 82) The method according to claim 82 wherein the public land mobile network (PLMN) is operative to inform at least one mobile station of the number of relays in a cluster. ### Claim 86 (depends on 1) The system according to claim 1 wherein if handoff occurs in which a relay disconnects from its core, at least one virtual core subsystem, having an encapsulation manager, recreates all relevant PDP contexts and bearers according to information stored on said encapsulation manager and switches packet data to a local stand-alone subsystem. ### Claim 87 (depends on 1) The system according to claim 1 wherein one mobile station is connected to a core functionality of the relay resource manager and another mobile station is connected to the core element of the network, and there is a link between said core functionality and said core element of the network. ### Claim 88 (depends on 1) A system according to claim 1 wherein said cellular communication network has at least one inter-node interface operable according to at least one of the following standards: 2G, GSM, CDMA, 3G, UMTS, WCDMA, HSPA, LTE, WiMAX, WiFi.