Patent Application
20140302850
This application claims the benefit of United Kingdom Application No. GB1306351.6 filed Apr. 9, 2013. The content of this application is fully incorporated herein in its entirety.
The field of this invention relates to methods and apparatus for direct communications between devices outside of a network coverage area.
A recent development in third generation (3G) wireless communications is the long term evolution (LTE) cellular communication standard, sometimes referred to as 4th generation (4G) systems. Both of these technologies are compliant with third generation partnership project (3GPP™) standards. Irrespective of whether these LTE spectral allocations use existing second generation (2G) or 3G allocations being re-farmed for fourth generation (4G) systems, or new spectral allocations for existing mobile communications, they will be primarily paired spectrum for frequency division duplex (FDD) operation.
In these systems, user plane data is carried over intermediary nodes, which define the functions of an access network. In LTE, the access network, Evolved Universal Terrestrial Radio Access Network (E-UTRAN), generally comprises a network of evolved NodeBs (eNodeBs). The eNodeBs are generally inter-connected with each other by means of an interface known as X2, and to the Evolved Packet Core (EPC) by means of an S1 interface. Specifically, the access network is connected to the Mobility Management Entity (MME) via an S1-MME interface and to the Serving GateWay (S-GW) via an S1-U interface. The protocols that run between the eNodeBs and any UEs are known as the Access Stratum (AS) protocols. The E-UTRAN is responsible for all radio-related functions, for example, radio resource management, header compression, security, positioning and connectivity to the EPC.
Referring to
Generally, the access network 101 facilitates communication by receiving control plane (c-plane) data and user plane (u-plane) data from each eNodeB 102, and transmitting this control plane data and user plane data to the other eNodeBs 102 in the access network 101.
Different eNodeBs 102 within the access network 101 may utilise different receiving and transmitting frequencies, for example if Frequency Division Duplexing (FDD) is utilised. Further, different eNodeBs 102 within the access network 101 may utilise different waveforms, signal modulation and coding schemes between the different eNodeBs 102. Specifically, in a generic LTE system, E-UTRAN, the Uu radio interface 108 generally utilises Orthogonal Frequency Division Multiple Access (OFDMA) in the Downlink and Single Carrier Frequency Division Multiple Access (SC-FDMA) in the Uplink. OFDMA distributes subcarriers to different users (UEs) at the same time, allowing multiple users to be scheduled to receive data simultaneously. Generally, subcarriers are allocated in contiguous groups for simplicity and to reduce any overhead of indicating which subcarriers have been allocated to each user; however subcarriers groups allocated to a UE may also be non-contiguous. SC-FDMA is generally utilised in the Uplink case as it has a lower peak-to-average power ratio compared to OFDMA, which can benefit mobile terminal devices in terms of transmit power efficiency, for example. As discussed above, FDD may be utilised resulting in differing transmit and receive carrier frequencies. Further, Time Division Duplexing (TDD) may be utilised, resulting in separate outward and return signals.
A potential problem occurs when, for example, UEs 114 are outside of the access network's coverage 106, but where the UEs 114 may still be in relative proximity to each other. In the case of the prior art system in
Therefore, in some instance there may be a need to provide a system that may enable UEs that are outside of a network's coverage area 106, to be able to facilitate communication. In particular, there may be a need to facilitate communication between UEs in close proximity to each other that may be outside of the network's coverage area 106.
Based on the prior art system of
Further details, aspects and embodiments of the invention will be described, by way of example only, with reference to the drawings. In the drawings, like reference numbers are used to identify like or functionally similar elements. Elements in the figures are illustrated for simplicity and clarity and have not necessarily been drawn to scale.
Referring now to
The wireless communication system 200 architecture consists of radio access network (RAN) and core network (CN) elements 204, with the core network elements 204 being coupled to external networks 202 (named Packet Data Networks (PDNs)), such as the Internet or a corporate network. The CN elements 204 comprise a packet data network gateway (P-GW) 207. In order to serve up local content, the P-GW may be coupled to a content provider. The P-GW 207 may be further coupled to a policy control and rules function entity (PCRF) 297 and a Gateway 206.
The PCRF 297 is operable to control policy control decision making, as well as for controlling the flow-based charging functionalities in a policy control enforcement function PCEF (not shown) that may reside in the P-GW 207. The PCRF 297 may further provide a quality of service (QoS) authorisation class identifier and bit rate information that dictates how a certain data flow will be treated in the PCEF, and ensures that this is in accordance with a UE's 225 subscription profile.
In example embodiments, the Gateway 206 is a Serving Gateway (S-GW). The Gateway 206 is coupled to a mobility management entity MME 208 via an S11 interface. The MME 208 is operable to manage session control of Gateway bearers and is operably coupled to a home subscriber server (HSS) database 230 that is arranged to store subscriber communication unit 225 (user equipment (UE)) related information. As illustrated, the MME 208 also has a direct connection to each eNodeB 210, via an S1-MME interface.
The HSS database 230 may store UE subscription data such as QoS profiles and any access restrictions for roaming. The HSS database 230 may also store information relating to the P-GW 207 to which a UE 225 can connect. For example, this data may be in the form of an access point name (APN) or a packet data network (PDN) address. In addition, the HSS database 230 may hold dynamic information relating to the identity of the MME 208 to which a UE 225 is currently connected or registered.
The MME 208 may be further operable to control protocols running between the user equipment (UE) 225 and the CN elements 204, which are commonly known as Non-Access Stratum (NAS) protocols. The MME 208 may support at least the following functions that can be classified as functions relating to bearer management (which may include the establishment, maintenance and release of bearers), functions relating to connection management (which may include the establishment of the connection and security between the network and the UE 225) and functions relating to inter-working with other networks (which may include the handover of voice calls to legacy networks). The Gateway 206 predominantly acts as a mobility anchor point and is capable of providing internet protocol (IP) point-to-point (p2p)/unicast/multicast distribution of user plane data to eNodeBs 210. The Gateway 206 may receive content via the P-GW 207, from one or more content providers 209 or via the external PDN 202. The MME 208 may be further coupled to an evolved serving mobile location centre (E-SMLC) 298 and a gateway mobile location centre (GMLC) 299.
The E-SMLC 298 is operable to manage the overall coordination and scheduling of resources required to find the location of the UE that is attached to the RAN, in this example embodiment the E-UTRAN. The GMLC 299 contains functionalities required to support location services (LCS). After performing an authorisation, it sends positioning requests to the MME 208 and receives final location estimates.
The P-GW 207 is operable to determine or participate in determination of IP address allocation for a UE 225, as well as QoS enforcement and flow-based charging according to rules received from the PCRF 297. The P-GW 207 is further operable to control the filtering of downlink user IP packets into different QoS-based bearers (not shown). The P-GW 207 may also serve as a mobility anchor for inter-working with non-3GPP technologies such as CDMA2000 and WiMAX networks.
As the Gateway 206 comprises an S-GW, the eNodeBs 210 would be connected to the S-GW 206 and the MME 208 directly. In this case, all UE packets would be transferred through the S-GW 206, which may serve as a local mobility anchor for the data bearers when a UE 225 moves between eNodeBs 210. The S-GW 206 is also capable of retaining information about the bearers when the UE 225 is in an idle state (known as EPS connection management IDLE), and temporarily buffers downlink data while the MME 208 initiates paging of the UE 225 to re-establish the bearers (for example the bearers at the S1/Uu interfaces). In addition, the S-GW 206 may perform some administrative functions in the visited network, such as collecting information for charging (i.e. the volume of data sent or received from the UE 225). The S-GW 206 may further serve as a mobility anchor for inter-working with other 3GPP™ technologies such as GPRS™ and UMTST™.
As illustrated, the CN 204 is operably connected to two eNodeBs 210, with their respective coverage zones or cells 285, 290 and a plurality of UEs 225 receiving transmissions from the CN 204 via the eNodeBs 210. In accordance with example embodiments of the present invention, at least one eNodeB 210 and at least one UE 225 (amongst other elements) have been adapted to support the concepts hereinafter described.
The main component of the RAN is an eNodeB (an evolved NodeB) 210, which performs many standard base station functions and is connected to the CN 204 via an S1 interface and to the UEs 225 via a Uu interface. A wireless communication system will typically have a large number of such infrastructure elements where, for clarity purposes, only a limited number are shown in
In some examples, one or more UEs 295, 296 (with three UEs 295, 296 shown for clarity purposes only) may be located outside of the coverage zones of both cells 285, 290 of eNodeBs 210, but still be, relatively speaking, in close proximity to each other. In these examples, it may be advantageous for the UEs 295, 296 to be able to communicate with each other 221 without having to utilise the coverage zones or cells 285, 290 of eNodeBs 210. In some examples, UEs 295, 296 may communicate only with other UEs in close proximity to, but outside of the coverage zones or cells 285, 290. In other examples, UEs 295, 296 may additionally communicate with UEs 225 that are in close proximity to UEs 295, 296 and that are inside of the coverage zones or cells 285, 290. In this example only one UE, UE 296, has been modified in accordance with examples hereinafter described. In other examples, other UEs may also be modified.
In some examples, the one or more modified UE 296 shown in
In other examples, the additional transceiver logic and signal processing logic 330 may additionally facilitate communications between UEs 225 within coverage zones or cells 285, 290 and UEs 295, 296 outside of coverage zones or cells 285, 290.
In some examples, one or more UEs 295, initially outside of a coverage zone 285, 290, may transition 226 into coverage zone 285, 290 while connected to UE 296. Further, UE 296 may initially be outside of coverage zones 285, 290 and may transition into coverage zones 285, 290 while connected to one or more UEs 295. Therefore, there may be a potential problem of how to maintain/disconnect connections between UEs 295, 296 initially outside of network coverage if they subsequently transition 226 into network coverage.
Clearly, the various components within the eNodeB 210 can be realized in discrete or integrated component form, with an ultimate structure therefore being an application-specific or design selection.
Referring now to
In some examples, receive side baseband switch 305 may be operably coupled between receiver front-end circuitry 306 and signal processor module 328. Receive side baseband switch 305 may be operable to connect either signal processing module 330 or signal processing module 328 to receiver front-end circuitry 306. In this manner, receive side baseband switch 305 may be operable to couple base band signals to either signal processing module 330 or signal processor module 328. Further, transmit side switch 309 may be operable to couple signal processing module 330 or signal processing module 330 to transmitter/modulation circuitry 322. In this example, transmit side switch 309 may be situated between transmitter/modulation circuitry 322 and signal processor module 328. In some examples, the controller 314 is also coupled to a buffer module 317 and a memory device 316 that selectively stores operating regimes, such as decoding/encoding functions, synchronization patterns, code sequences, and the like. Further, in some examples, controller 314 may be operably coupled to signal processing module 330 (not shown for clarity purposes). A timer 318 is operably coupled to the controller 314 to control the timing of operations (e.g. transmission or reception of time-dependent signals) within the wireless communication unit 296. In some examples, signal processing module 330 may receive/transmit user plane data via receive/transmit switching devices 307 and may receive/transmit control plane data via receive/transmit switching devices 309.
It should be noted that switching devices 303, 305, 307, 309 may be operably coupled to controller 314, in order to control the switching devices. In order not to obfuscate from the invention, these connections have not been shown. Further, controller 314 may be controlled via signal processing module 330, which may determine what functionality, via 301, the signal processing module 330 requires.
As regards the transmit chain, this essentially includes an input module 320, coupled in series through transmitter/modulation circuitry 322 and a power amplifier 324 to the antenna 302, antenna array, or plurality of antennas. The transmitter/modulation circuitry 322 and the power amplifier 324 are operationally responsive to the controller 314.
The signal processor module 328 in the transmit chain may be implemented as distinct from the signal processor in the receive chain. Alternatively, a single processor may be used to implement a processing of both transmit and receive signals, as shown in
In this example, additional transceiver logic 336 and signal processing logic 330 may be operable to facilitate communications between UEs 296 that are outside of an access network's coverage area. In this example, when switching devices 303 and/or 305 couple additional transceiver 336 and/or signal processing logic 330 into the remaining circuitry of UE 296, UE 296 may be operable to directly communicate with other UEs 296 outside of a network's coverage area. Further, in this example, if additional transceiver 336 and signal processing logic 330 is isolated from the remaining circuitry in UE 296, UE 296 may be operable to function as a prior art UE and communicate with other UEs within a network's coverage area.
In some examples, when the additional transceiver 336 and signal processing logic 330 of the UE 296 is configured to assist communication from another UE located outside of the coverage range of the NodeB, e.g. where the communication unit (UE 296) is operating in a repeater-type mode of operation, the signals received via additional transceiver 336 and signal processing logic 330 may be processed and re-transmitted (say, in one example via signal processing logic 328 and UE transmitter (322, 324) to the NodeB.
In some examples, additional transceiver logic and signal processing logic module 330 is integrated into the remaining circuitry of UE 296. In other examples, the additional transceiver logic and signal processing logic module 330 may be a discrete module that may be externally operably coupled to a UE device.
Referring to
Referring first to the example where device 404 is inside a coverage area 401. In this case, access network 410 provides coverage area 401 that allows devices 404, 412 and 414 (n devices) to communicate with each other via, for example, radio interface/Uu 416. In this case, device 404 may be in a first mode of operation, wherein Node-T module 408 is isolated from transceiver module 418 and UE module 406. In this case, UE module receives transmissions 416 via transceiver module 418 and switching module Sw1 420. In this case, Sw1 420 is in position 1, coupling UE module 406 to transceiver module 418. Further, switching module Sw2 422 is in position 1, isolating Node-T module 408 from UE module 406. In this mode of operation, device 404 may operate in a similar way to a UE as defined in the art, and in a similar way to devices 412 and 414 that in this example do not comprise Node-T modules 408. In this example, only device 404 has additional Node-T module 408. However, in other examples, a plurality of devices within access network's coverage 401 may comprise Node-T modules 408.
Referring now to the example where device 404 is outside of a coverage area 402. In this example, device 404 may now have transitioned to a second mode of operation. In this example, Sw1 420 may have transitioned to position 2, coupling transceiver module 418 to Node-T module 408. Further, Sw2 422 may have transitioned to position 2, coupling UE module 406 to Node-T module 408. In this mode of operation, device 404 may be operable to communicate with further devices 412, 414 (n devices), without the need for access network's coverage area 401. In some examples, device 404 may be operable to communicate directly with devices 412 and 414 that are in close proximity to device 404.
In other examples, device 404 may facilitate communication between, for example, device 412 and device 414. In further examples, device 404 may facilitate communication with devices outside of a coverage area, for example device 412, and devices inside a coverage area.
In some examples, device 404 may communicate directly with devices, in close proximity to but, outside of a coverage area, and communicate with devices inside a coverage area via the access network 410. In examples, the abovementioned example may occur if, for example, device 404 transitioned from being outside of a coverage area to being inside of a coverage area.
In examples, Node-T module 408 may be a translation module, operable to facilitate communications between devices outside of a coverage area. In examples, Node-T module 408 may be co-located within device 404. However, in other examples, Node-T module 408 may be a discrete component that can be operably coupled to device 408. In yet further examples, Node-T module 408 may be integrated within UE module 406. In some examples, Node-T module 408 may be an eNodeB type device, capable of adopting rules, signals and protocols, for example, which may be used by an access network, for example access network 410. In some further examples, Node-T module 408 may be an eNodeB type device with some additional core network functionality, thereby potentially allowing existing LTE UEs to connect to Node-T modules 408 without further modification. For example, existing LTE UEs radio part, protocols and hardware may be utilised.
In some examples, Node-T modules 408 may require different scheduling and radio resource allocation policies compared to the access network's scheduling and radio resource allocation policies. This may be to prevent interference between LTE UEs at an edge of the network that may be utilising the same resources as the Node-T module 408. In other examples, macro cells, eNodeBs making up the access network 401, may require modification rather than the Node-T modules 408. In this case, the macro cells may be modified to prevent interference between LTE UEs at an edge of the network and device(s) incorporating Node-T module(s) 408. Therefore, the macro cells may require different scheduling and radio resource allocation policies for LTE UEs at the edge of the network compared to LTE UEs that may be centrally located within the network.
In some examples, device 404 may, at the RAN level, perform scheduling, some RRC functionality without mobility management, PDCP/RLC/MAC, may ensure proper multiplexing/de-multiplexing at the MAC layer, may perform termination of the RRC layer, U-Plane data routing at the PDCP SDU layer. At the Core network level, device 404 may terminate the NAS protocols, implement limited tracking in the ECM-IDLE (only presence and no tracking of UE's location), and one or more of the following subset of functions:—
With regard to some mobility/handover examples, it is envisaged that a UE (that is not a terminal device 404 with a Node-T module and is supervised/controlled by a terminal device with a Node-T module 408) may be handed over to a base station/Node-B should they enter ‘macro-cell’ E-UTRAN coverage. In this situation, the UE's context information may be moved between the controlling Node-T module and the recipient base station/Node-B via an X2-like interface. In general, UE-controlled mobility occurs in ECM-IDLE mode of operation (although some network support for cell reselection may be possible). In ECM-CONNECTED mode of operation, the mobility is controlled by the radio access network (RAN) & Access Stratum (AS) (however also in the ECM-CONNECTED mode of operation, the UE may still elect to move to ECM-IDLE and perform a cell reselection.)
In some examples, the handover scenario may be slightly different as compared to the legacy system, as two UEs may be handled by the Node-T module, but both UEs desiring to be handed over (or requiring to be handed over) to another Node-T module in proximity, as compared to just one UE.
Thus, in some examples, two UEs may be handed over from the terminal device that is a Node-T module to another Node-T module. Such a multiple handover scenario may occur as part of an ‘out of coverage’ determination, irrespective of whether at least one more NodeT(s) is/are present in proximity to the UEs. In this example, the Node-T module may be required to obtain information from the UEs that are in direct communication (e.g. from the UEs when in ECM-CONNECTED mode), as to whether they both can see a candidate (alternative Node-T module in proximity to the both communicating UEs) to be handed over to.
Alternatively, in another example, the two UEs may be handed back to be under the control of the eNodeB/EPC. In this example, one or more of the UEs may choose to invoke a registration with the network when they determine that they are back within the coverage of the base station/Node-B/EPC, for example by indicating a visibility of a macro eNodeB and/or indicating a signal strength of signals received from a macro eNodeB. However, in such a situation, the UEs may cause their session(s) to be terminated, with the effect that these sessions will need to be re-established (service interruption aspects) when being handed over to the base station/Node-B/EPC.
In some further examples, translation module 408 may perform the functions of an access network, for example access network 410. In examples, the translation module 408 may adopt signals and protocols utilised by, for example, access network 410, thereby simulating access network 410, allowing direct communication between device 404 and devices 412, 414 in close proximity to device 404. Further, in examples, translation module 408 may relay user plane data between itself and devices 412, 414 in close proximity to device 404, as well as manage radio resources and schedule transmissions between itself and other devices 412, 414 in close proximity to device 404 that are outside of a coverage area.
In examples, translation module 408 may be coupled between UE module 406 and transceiver module 418, thereby allowing device 404 to directly communicate with other devices in close proximity that are outside of a coverage area.
In some examples, device 404 may transition between being inside a coverage area and being outside of a coverage area, and vice versa. In examples, device 404 may be initially outside of a coverage area and may be communicating directly with other devices/UEs outside of the coverage area that are in close proximity to device 404. In this example, device 404 may be in the second mode of operation, as discussed above, wherein Node-T module 408 may be operably coupled in the communication path between UE module 406 and transceiver module 418. If device 404 were to enter a coverage area, for example coverage area 401 defined by access network 410, then device 404 may have several modes of operation. For example, device 404 may sever communications that it may have established with devices whilst outside of coverage area 401, for example, with devices 412, 414 that were also outside of coverage area 401, and in close proximity to device 404, before connecting to access network 410 by switching to the first mode of operation, discussed above. Alternatively, device 404 may maintain communications that it may have established with devices whilst outside of coverage area 401 and, for example, it enters coverage area 401, additionally connects with access network 410. In this example, if a different frequency band is utilised between access network 410 and Node-T module 408 in device 404, then both these communication modes can co-exist without further modification being required. Therefore, in this example, device 404 may be able to maintain communication with devices outside of coverage area 401, whilst still connecting to devices within the coverage area 401 via access network 410. In other examples, if the same or similar frequency band is utilised by access network 410 and Node-T module 408 in device 404, then a macro cell, for example an eNodeB making up access network 410, may require modification to minimise any interference to other devices utilising that macro cell. For example, different scheduling and/or radio resource allocation policies may need to be utilised for devices/UEs that may be at an edge of the macro cell's coverage area due, in part, to these UEs being closer to device 404, and, therefore, may be more likely to receive interfering messages from device 404 if transmitted on the same frequency as the macro cell within the access network 410. A yet further option facilitates continued communications with devices that are outside of coverage area 401 until the session is finished, and then the Node-T module 408 switches its operational mode from the second mode of operation to the first mode of operation and connect to access network 410, for example. Alternatively, the Node-T module 408 may just stop employing control functions for the selected devices for which the communication session(s) have been stopped). Thus, in certain conditions and configurations the Node-T module 408 may release its supervision and control functions for some UEs that stopped sessions, thereby allowing them to use the macro cell network. In this example, similar modifications may need to be made, as discussed above, based on whether the frequency bands utilised by access network 410 and Node-T module 408 are the same or different.
In examples relating to
Utilising a translation module 408 may allow different devices utilising different frequencies for signal transmission and reception, different waveforms, different modulation and coding schemes in the uplink and downlink scenario to communicate when outside of a network's coverage area. Without utilising translation module 408, direct communications between devices outside of a network's coverage area would not be possible.
In a further example, device 404, for example, may communicate with UEs outside of a coverage area using the Uu interface as defined in the LTE system. In this example, if a UE with a Node-T module 408 is outside of a coverage area, and in close proximity to another UE 412, that may or may not have a Node-T module 408, that it wishes to connect with (which may also be outside of the coverage area) it may utilise its Node-T module 408 to convert its uplink message, which is generally sent using SC-FDMA, to OFDMA, allowing the other UE 412 to receive UEs 404 transmission, thereby facilitating communication between the two devices 404, 412. Without translation module 408 being enabled, direct communication between UEs 404 and 412 would not be possible without being inside a network's coverage area, for example coverage area 401. In another example, additionally or in combination with the abovementioned examples, FDD may be utilised. In this example, the translation module 408 may also swap the frequencies on which the UE 404 would normally transmit and receive, thereby allowing other UEs 412, 414 to receive signals from the device with translation module 408 on a frequency F2, for example. In examples, frequency F2 may have been utilised by the other UEs 412, 414 to receive transmissions when within the network's coverage area 401, thereby allowing the other UEs 412, 414 to receive UEs 404 transmissions. Similarly, translation module 408 may swap received frequencies from the other UEs 412, 414 before reaching UE module 406, thereby allowing the other UEs 412, 414 to transmit on their normal frequency F1 of the duplex pair, whilst allowing UE module 406 to receive their transmissions. Similarly, if UEs 412, 414 wish to establish a communications link with the UE with translation module 408, the translation module may need to be utilised. Otherwise, the UE 404 may not be able to receive the UEs 412, 414 transmissions. In examples, translation device 408 is operable to determine the frequencies, waveforms, modulation and coding techniques of UEs attempting to communicate with translation device 408.
It should be noted that the abovementioned examples are not limited to communication between two UEs, and communication between a plurality of UEs is envisaged.
Referring to
In a further example, the translation device/Node-T module 506 may terminate control plane and user plane protocols of device 502 that wishes to communicate with device 512, for example, which may embody an LTE UE or a further device with at least one Node-T 506 module. In this example, translation device 506 may perform protocol translation and adopt message formats required by the target device, in this example UE 512. In this example, the translation device 506 may transmit user plane data to the target device, UE 512, at the service data unit (SDU) level of the packet data convergence protocol (PDCP) layer. In this example, communications link 507 may be operable to carry signals of different types. In examples, communications link 507 may be operable to carry the following:—
It is generally known that the L2 protocol structure for the downlink and uplink for any two given conventional UEs attempting to communicate directly will fail due to the fact multiplexing at the MAC layer will fail due to likelihood of using different logical channel identifiers for DTCH logical channels (This is due to the fact that mapping of bearer ids to logical channels ids allowing multiplexing is implementation specific. Therefore, these UEs would not be able to demultiplex correctly at the MAC layer allowing data to be linked with the right bearer. Therefore, a potential problem may be how to implement a system that may allow two given UEs to successfully communicate directly with each other when one or all of the UEs are not within network coverage.
In this example, UE 603 may comprise a Node-T module 602, and UE device 604 may be an LTE UE without a Node-T module 602.
Note that it may not possible to use conventional UEs for device to device communications outside of a coverage area, due, in part, to the fact that the conventional UEs would expect that the termination point is not at the UE, for example as in an LTE system the RRC protocol is terminated at the eNodeB. Therefore a translation device may be required. Further, it may be that a subset of RRC functions could be required, rather than the complete set of functions. For example, the mobility functions may not be required as mobility could be controlled by a UE with a translation device and not as in a conventional system where the mobility is controlled by the network (i.e. the radio access network).
In an LTE/EPC system the NAS protocol may be terminated at the MME. The NAS protocol facilitates the following functions at the MME:
If the security context and the UE context information are pre-provisioned at the UE and the eNodeB, the Authentication and Authorisation as well as the Attach procedure may not be required.
The presence tracking in ECM-IDLE helps a Node-T determine whether a UE is still in proximity. The presence tracking may be implemented by periodic invocation of the Tracking Area Update procedure, which is used primarily to indicate a UE's presence. When the Node-T does not receive the expected signalling from a UE, a UE is marked as not present and the UE's context information stored at the Node-T may be removed or kept for some time as indicated by the system configuration parameters.
In some examples, another use of the presence tracking may be to facilitate the UE's context transfer to another Node-T, or even back to the fixed core network/Infrastructure. In that case, the information passed by a UE in the notification message may include information about other Node-Ts in proximity, or information as to whether a UE is now in network coverage. However to implement this feature, the UE may be required to invoke the Node-T discovery procedure and/or PLMN search procedure in ECM-IDLE (in order to improve the search efficiency, the latter may be restricted to specific PLMN(s) pointing to defined parts of spectrum to be searched). The Node-T that is currently used by a UE makes a decision as to whether context transfer should be initiated and carries out the procedure if it needs to be. This is referred to as the network managed mobility. This does not restrict the UE's ability to trigger the UE controlled mobility. Whether the UE and/or network controlled mobility is used is defined by the configuration parameters or system indication such as for example the information sent on the broadcast channel. The same information may specify priority criteria and conditions governing the order in which a mobility scheme shall be applied.
In a conventional system the mobility is controlled by the network (i.e. the eNodeB).
In some examples, the mobility management may be controlled by the UE as far as the switching between a Direct mode of Operation (DMO) network and a macro cell is concerned. After switching back to a macro cell, the UE's mobility may be controlled by a macro access network.
In a legacy system NodeBs may be considered to be stationary, and UEs may be considered mobile. Whereas in a DMO network, NodeBs may be mobile as well as the UE(s). The mobility, as such, may not be required as UE's access to the services may be limited by the DMO network coverage and geographical location of the entity providing coverage i.e. the UE with the translation device. However the UE may still make a decision as to when to switch over to the macro cell.
In terms of service continuity when the UE is back in network coverage, there may be several options as how to control the switching process at the UE. For example:—
In some examples, if the same frequency band is used the latter approach may require special arrangement in a macro cell to minimise the interference level to other devices in its neighbourhood which use a macro cell. This may entail different scheduling and radio resource allocation policies for devices which are at the edge of a cell. However if a different frequency band is used these two communication modes can coexist without any further arrangements.
Effectively one Node-T may be active for a group of devices communicating together because this device may take on a role of a radio resource controller/manager. However there could be some means for Node-Ts to communicate with one another in order to impact their radio resource allocation policies to minimize the inter cell interference. In the prior art for the LTE system, the Inter Cell Interference Coordination (ICIC) techniques may be used over the X2 interface. In this invention the X2 interface could be implemented although handover is not required. This wireless X2 interface would be only used over the pre-allocated spectrum while out of network coverage to minimize inter cell interferences generated by several Node-Ts which in proximity. This would allow establishing of several groups/clouds each of them using a different Node-T as a radio resource manager.
This may be especially useful in the public safety context when several types of service e.g. special disaster handling units/squads and for example fire brigades use the same frequency band.
Abovementioned
Referring to
The above list of example EPC functions may differ if the target UE 714 is not an LTE UE 714 without additional functionality. For example, if LTE UE 714 were a UE with additional functionality, for example, like UE 603 or UE 702, the abovementioned list of example EPC functions may differ. Further, in examples, there may be no need for a SGi interface to external PDN networks. In this example, S1 interfaces and S5 interfaces may be internal. Therefore, external S1-U bearers and S5 bearers within the network may be collapsed as, in this example, they may be internal to device 702.
In a further example, devices utilising a translation device/Node-T module may be preconfigured with security credentials that may render any authentication procedures as unnecessary. For example, for an LTE/EPC system, at least security credentials relating to KASME may be preconfigured into devices utilising a translation device/Node-T module. In other examples, in order to enable complete initialisation of security functions, parameters such as NAS/AS algorithms and eKSI may also be required. Further, in some examples, NAS keys and COUNT may also need to be derived and initialised. Further, in some examples, devices utilising a translation device/Node-T module may be preconfigured with UE context information. By potentially preconfiguring UEs with this context information may remove the necessity to utilise Attach and authentication procedures, which would usually be utilised to generate this UE context information. By preconfiguring particular UEs, these devices may be able to initiate communications without having to attach to the system, as UE context information and security credentials may be preconfigured in to these UEs, thereby allowing the core network to establish secure communication without further signalling being required. Potential examples of context information that may be preconfigured into a UEs translation device/Node-T module is shown in Table. 1. In this example, the information presented in Table 1 is a subset of entries normally required.
In a yet further example, a UE device that incorporates a translation device/Node-T module, may implement a subset of network side functions of the application layer.
The EPC functions differ from the conventional system in at least one or more of the following ways:
Referring to
In a further example, devices utilising a translation device/Node-T module may be preconfigured with IMS security credentials that may render any IMS authentication procedures unnecessary. For example, for an IMS system, at least IMS security credentials relating to IMS security key may be preconfigured into devices utilising a translation device/Node-T module and the S-CSCF. Further, in some examples, devices utilising a translation device/Node-T module may be preconfigured with IMS context information. Preconfiguring UEs with IMS context information renders IMS Registration and authentication procedures unnecessary, which would otherwise have been triggered to create IMS context for the UE. By preconfiguring particular UEs, these devices may be able to initiate IMS communications without having to perform IMS Registration with the system, as IMS context information and security credentials are available for use at the UEs and IMS network, thereby allowing the IMS network to establish secure communication without further signalling being required.
Referring now to
Referring now to
Computing system 1000 can also include a main memory 1008, such as random access memory (RAM) or other dynamic memory, for storing information and instructions to be executed by processor 1004. Main memory 1008 also may be used for storing temporary variables or other intermediate information during execution of instructions to be executed by processor 1004. Computing system 1000 may likewise include a read only memory (ROM) or other static storage device coupled to bus 1002 for storing static information and instructions for processor 1004.
The computing system 1000 may also include information storage system 1010, which may include, for example, a media drive 1012 and a removable storage interface 1020. The media drive 1012 may include a drive or other mechanism to support fixed or removable storage media, such as a hard disk drive, a floppy disk drive, a magnetic tape drive, an optical disk drive, a compact disc (CD) or digital video drive (DVD) read or write drive (R or RW), or other removable or fixed media drive. Storage media 1018 may include, for example, a hard disk, floppy disk, magnetic tape, optical disk, CD or DVD, or other fixed or removable medium that is read by and written to by media drive 1012. As these examples illustrate, the storage media 1318 may include a computer-readable storage medium having particular computer software or data stored therein.
In alternative embodiments, information storage system 1010 may include other similar components for allowing computer programs or other instructions or data to be loaded into computing system 1000. Such components may include, for example, a removable storage unit 1022 and an interface 1020, such as a program cartridge and cartridge interface, a removable memory (for example, a flash memory or other removable memory module) and memory slot, and other removable storage units 1022 and interfaces 1020 that allow software and data to be transferred from the removable storage unit 1018 to computing system 1000.
Computing system 1000 can also include a communications interface 1024. Communications interface 1024 can be used to allow software and data to be transferred between computing system 1000 and external devices. Examples of communications interface 1024 can include a modem, a network interface (such as an Ethernet or other NIC card), a communications port (such as for example, a universal serial bus (USB) port), a PCMCIA slot and card, etc. Software and data transferred via communications interface 1024 are in the form of signals which can be electronic, electromagnetic, and optical or other signals capable of being received by communications interface 1024. These signals are provided to communications interface 1024 via a channel 1028. This channel 1028 may carry signals and may be implemented using a wireless medium, wire or cable, fiber optics, or other communications medium. Some examples of a channel include a phone line, a cellular phone link, an RF link, a network interface, a local or wide area network, and other communications channels.
In this document, the terms ‘computer program product’, ‘computer-readable medium’ and the like may be used generally to refer to media such as, for example, memory 1008, storage device 1018, or storage unit 1022. These and other forms of computer-readable media may store one or more instructions for use by processor 1004, to cause the processor to perform specified operations. Such instructions, generally referred to as ‘computer program code’ (which may be grouped in the form of computer programs or other groupings), when executed, enable the computing system 1000 to perform functions of embodiments of the present invention. Note that the code may directly cause the processor to perform specified operations, be compiled to do so, and/or be combined with other software, hardware, and/or firmware elements (e.g., libraries for performing standard functions) to do so.
In an embodiment where the elements are implemented using software, the software may be stored in a computer-readable medium and loaded into computing system 1000 using, for example, removable storage drive 1022, drive 1012 or communications interface 1024. The control logic (in this example, software instructions or computer program code), when executed by the processor 1004, causes the processor 1004 to perform the functions of the invention as described herein.
In one example, a tangible non-transitory computer program product comprises executable program code operable for, when executed at the first wireless network element: intercepting a communication from the wireless communication unit to a second network element; decoding the communication to determine whether the communication relates to a request for a first item of information; requesting the first item of information from the data store, wherein the control processor is further arranged to not forward the request for the first item of information to the second network element if it is determined that first item of information is stored in the data store; receiving the first item of information from the data store; and transmitting the first information to the wireless communication unit.
It will be further appreciated that, for clarity purposes, the described embodiments of the invention with reference to different functional units and processors may be modified or re-configured with any suitable distribution of functionality between different functional units or processors is possible, without detracting from the invention. For example, functionality illustrated to be performed by separate processors or controllers may be performed by the same processor or controller. Hence, references to specific functional units are only to be seen as references to suitable means for providing the described functionality, rather than indicative of a strict logical or physical structure or organization.
Aspects of the invention may be implemented in any suitable form including hardware, software, firmware or any combination of these. The invention may optionally be implemented, at least partly, as computer software running on one or more data processors and/or digital signal processors. For example, the software may reside on non-transitory computer program product comprising executable program code to increase coverage in a wireless communication system.
Thus, the elements and components of an embodiment of the invention may be physically, functionally and logically implemented in any suitable way. Indeed, the functionality may be implemented in a single unit, in a plurality of units or as part of other functional units.
Those skilled in the art will recognize that the functional blocks and/or logic elements herein described may be implemented in an integrated circuit for incorporation into one or more of the communication units. Furthermore, it is intended that boundaries between logic blocks are merely illustrative and that alternative embodiments may merge logic blocks or circuit elements or impose an alternate composition of functionality upon various logic blocks or circuit elements. It is further intended that the architectures depicted herein are merely exemplary, and that in fact many other architectures can be implemented that achieve the same functionality. For example, for clarity the signal processor 308, control processor 414, and additional transceiver circuitry and signal processing logic 330 have been illustrated and described as a single processing module, whereas in other implementations they may comprise separate processing modules or logic blocks.
Although the present invention has been described in connection with some example embodiments, it is not intended to be limited to the specific form set forth herein. Rather, the scope of the present invention is limited only by the accompanying claims. Additionally, although a feature may appear to be described in connection with particular embodiments, one skilled in the art would recognize that various features of the described embodiments may be combined in accordance with the invention. In the claims, the term ‘comprising’ does not exclude the presence of other elements or steps.
Furthermore, although individually listed, a plurality of means, elements or method steps may be implemented by, for example, a single unit or processor. Additionally, although individual features may be included in different claims, these may possibly be advantageously combined, and the inclusion in different claims does not imply that a combination of features is not feasible and/or advantageous. Also, the inclusion of a feature in one category of claims does not imply a limitation to this category, but rather indicates that the feature is equally applicable to other claim categories, as appropriate.
Furthermore, the order of features in the claims does not imply any specific order in which the features must be performed and in particular the order of individual steps in a method claim does not imply that the steps must be performed in this order. Rather, the steps may be performed in any suitable order. In addition, singular references do not exclude a plurality. Thus, references to ‘a’, ‘an’, ‘first’, ‘second’, etc. do not preclude a plurality.
| Number | Date | Country | Kind |
|---|---|---|---|
| GB1306351.6 | Apr 2013 | GB | national |
