GB2534200A - Wireless access technology configuration - Google Patents
Wireless access technology configuration Download PDFInfo
- Publication number
- GB2534200A GB2534200A GB1500755.2A GB201500755A GB2534200A GB 2534200 A GB2534200 A GB 2534200A GB 201500755 A GB201500755 A GB 201500755A GB 2534200 A GB2534200 A GB 2534200A
- Authority
- GB
- United Kingdom
- Prior art keywords
- mobile terminal
- base station
- access technology
- wireless access
- firmware
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/18—Selecting a network or a communication service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/02—Terminal devices
- H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/08—Access point devices
- H04W88/10—Access point devices adapted for operation in multiple networks, e.g. multi-mode access points
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
An approach for configuring the wireless access technology to allow a mobile terminal to access a wireless network is provided. A broadcast message is communicated from a base station of the wireless network to the mobile terminal. An access procedure is performed between the mobile terminal and the base station in response to the broadcast message, such that a comparison is made between the configuration of the mobile terminal and the configuration of the base station. Then, a wireless access technology software and/or firmware of the mobile terminal and/or the base station is selected based on the comparison, in order to allow the mobile terminal to access the wireless network through the base station. If the mobile terminal does not have compatible software then the base station sends software and/or firmware in a software download message.
Description
WIRELESS ACCESS TECHNOLOGY CONFIGUARATION
Technical Field of the Invention
The invention concerns a method of configuring wireless access technology to allow a mobile terminal to access a wireless network and/or a wireless network device configured to operate accordingly.
Background to the Invention
A significant driving force in the growth of wireless networks has been 0 standardisation. Wireless network may include cellular networks, sensor networks; Wireless Local Area Networks (LAN) and other types of configuration. In particular, the standardisation of the wireless access technologies (often referred to as a Radio Access Technology or RAT) has enabled interoperability of equipment or devices from different manufacturers, whether mobile terminals or fixed network entities. Standards have developed to accommodate different wireless access technologies and equipment and devices have been created to operate with multiple wireless access technologies, each defined by a respective standard Wireless access technologies are typically defined by a combination of hardware with software and/or firmware, although parts or all of a wireless access technology may be defined in software and/or firmware alone.
As further wireless access technologies are developed, the number of standards will multiply. Devices that can operate in accordance with wireless access technologies defined by a range of different standards will be increasingly challenging to engineer. This challenge is significant for fixed network entities, but even more pronounced for mobile terminals having additional size, power and cost constraints.
Summary of the Invention
Against this background, there is provided a method of configuring wireless access technology to allow a mobile terminal to access a wireless network in accordance with claim 1. A corresponding program in line with claim 21 may also be considered, although the invention may also be embodied in the
_
form of programmable logic, firmware or other configurable system. A wireless network device as defined by claim 22 is also provided. Other preferred features are disclosed with reference to the claims and in the description below.
A procedure is specified in which a broadcast message is transmitted by a base station and/or a mobile terminal receives the broadcast message Then, an access procedure (which may he termed a random access procedure) is performed, allowing the configuration (particularly in terms of the wireless access technology) of the base station and the mobile terminal to be compared. On the basis of this comparison, a wireless access technology software and/or firmware 0 is selected for the mobile terminal, base station or both. There can therefore be considered a wireless networking system that uses only a basic wireless access technology standard, which may define the broadcast message and access (ACH or RACH) procedure, but can then allow any wireless access technology to be used for network access by the mobile terminal. Typically, the wireless access technology used for access will differ from that used for the broadcast message and RACH procedure and need not be standardised. This may allow use of a wide range of standardised or proprietary wireless access technologies, without the need for the mobile device to know or use that wireless access technology before beginning the access procedure.
Although the invention will be discussed in detail largely by reference to cellular network technology, this is an example only. The invention may equally be applicable to other types of wireless access system, such as wireless Local Area Network (LAN), wireless Wide Area Network (WAN), short-range wireless networking and other wireless systems that provide access to a wider network.
The general terminology used in this disclosure is intended to cover analogous parts of different types of wireless access system. For instance, a mobile terminal may he a User Equipment (UE), a wireless client or user device or similar and a base station may be a cell, an access point, a transmission and/or reception point (for example in a virtuaksed system) or similar.
The wireless access technology of the mobile terminal and/or base station may then be configured, potentially in a dynamic way. Advantageously, this configuration (or re-configuration) may take place over the wireless interface or -3 -another interface. For example, instructions for configuration of the mobile terminal's wireless access technology may be communicated from the base station to the mobile terminal. Additionally or alternatively, a server associated with the selected wireless access technology software and/or firmware may be identified and instructions for configuration of the base station's wireless access technology may be received from the identified server. In either or both cases, the instructions may be the selected wireless access technology software arid/or firmware, thereby allowing ihe possibility for over the air reconfiguration.
In some embodiments, communication of the broadcast message and 0 performance of the access procedure may be effected by initialisation hardware and separate wireless access hardware that may be configurable in accordance with the selected wireless access technology software and/or firmware. For example, the wireless access hardware may be re-configurable hardware or it may be configured to operate in accordance with a plurality of different technologies, the technology for use at one time being selectable.
Brief Description of the Drawings
The invention may be put into practice in a number of ways, and a preferred embodiment will now be described by way of example only and with reference to the accompanying drawings, in which: Figure 1 shows a schematic diagram of a known general Software-Defined Networking (SDN) architecture; Figure 2 depicts a block diagram of an existing processor architecture, suitable for a wireless network device for operation with the present invention; Figure 3 schematically illustrates a wireless networking architecture in accordance with an embodiment; Figure 4A shows flow of information between a mobile terminal and a network base station in line with an embodiment; Figure 4B shows flow of information between a mobile terminal and a network base station for an authentication process for use in the embodiment of Figure 4A; and -4 -Figure 5 illustrates a schematic of interfaces between network elements in accordance with an embodiment.
Detailed Description of a Preferred Embodiment
Inspiration for the present invention may be found in the Software-Defined Networking (SDN) concept. Referring first to Figure 1, there is shown a schematic diagram of a general SDN architecture. SON separates a network into a management layer 10 and an infrastructure layer 20. Virtualisation of both layers is possible and this is depicted by management layer virtualisation 15 and 0 infrastructure layer virtualisation 25. The architecture decouples network control and forwarding functions; allowing the underlying infrastructure to be abstracted from applications and services. The management layer 10 and infrastructure layer 20 communicate by means of a protocol 18, such as OpenFlow.
In this way, routers 31 can interface with an MNG, RCN, ORC unit 30 "I 5 through a management, reconfiguration, orchestration layer 50. Moreover, the routers 31 can interface with one another through a connectivity layer 40. Another form of inspiration for the present invention is found in the area of hardware controlled by software and/or firmware. Referring next to Figure 2, there is depicted a block diagram of an existing processor architecture, suitable for a wireless network device. Such a processor architecture may be suitable for use with embodiments of the present invention. The processor 100 comprises: a multicore fabric 105; one or more DSP cores 110; a shared memory 120; one or more main processor cores 130; one or more memory controllers 140; one or more output ports 150; one or more input/output ports 160; and one or more additional processors 170.
The one or more DSP cores 110 may be suitable for implementing a physical layer (Layer 1) and the one or more main processor cores may be implement a data link layer (Layer 2). The one or more additional processors 170 may include accelerators. These can be used for one or more of coding/decoding; DFTIFFT; and CRC checks.
Referring now to Figure 3, there is schematically illustrated a wireless networking architecture in accordance with an embodiment. Common features -5 -between this embodiment and the existing SON architecture shown in Figure 1 are indicated by the use of identical reference numerals. A management layer 10 with its virtualisation 15 interfaces with an infrastructure layer 20 with its virtualisation 25. This interface is provided by protocol 19, which may be based on the existing protocol 18 shown in Figure 1 (such as OpenFlow), but with some additions and/or changes.
The existing architecture is extended to handle radio access interfaces and this is indicated by device layer 60 (with virtualisation 65). The infrastructure layer 20 and device layer 60 interact by means of two interfaces. An open it 0 interface 70 (which may be termed "open G") deals with reconfiguration, management and basic connectivity. This interface may be standardised, to ensure that the device layer 60 has basic interoperability with the infrastructure layer 20. The second interface 80 provides full connectivity between the infrastructure layer 20 and the device layer 60. This interface may be configured "I 5 by the open interface 70 and may be a proprietary interface. The open interface and second interface 80 are typically air interfaces. Routers 31, wireless base stations 32 and devices 33 can thereby all interact with the MNG, RCN, ORC unit 30 by means of a management, reconfiguration, orchestration layer 50. The interaction between router 31, base station 32 and device 33 is split over two layers: the open interface 70; and the second interface 80.
The open interface 70 is typically a standardised air interface providing a basic set of capabilities. For example, it may manage one or more of: a first connection; inter-operator handover; and roaming. Moreover, the open interface 70 allows operators to use proprietary wireless interfaces, as will be explained below. Particular advantages may include: lower time-to market for new services; ability to easily swap RATs and vendor/manufacturer-specific technology; product and/or service differentiation; ability to handle problematic technologies by reprogramming related features. Rather than needing to wait for new hardware or new devices for new technologies or services to be deployed, they may be immediately updated over the air interface, for example.
One key distinction between existing air interfaces and the open interface 70 may relate to the initialisation procedure or first connection. Although this will -6 -be discussed in the form of a cellular network, it will be understood that the procedure may be analogously performed in other kinds of wireless network, as noted above. When a mobile terminal (or specifically user equipment, UE) powers up, it tunes to each and every channel it supports and takes measurements, such as RSSI (energy or power measured at the receiver, not needing any channel coding or processing). This means that the mobile terminal does not need to know anything about the network that it measures.
Based on these measurements, the UE may choose a few candidate networks from this list. A range of criteria may be used for determining candidate 0 networks and this may be left to specific implementations of the mobile terminal.
For example, an RSSI above a certain threshold may be used.
For each candidate on the list, the UE reads a universal broadcast message. This may be a standardised message that includes a range of data items, for example a network identifier, software version, base station capabilities and/or configurations. This is sent by a base station in respect of a single network or may be sent by one base station on behalf of a number of different networks. Based on the broadcast message, the mobile terminal typically gives preference to certain networks. Other information (such as services or information stored in a part of the mobile terminal, such as a USN) may additionally be used for making a determination at the mobile terminal. For example, this may allow the UE to prefer a base station operated by its home public land mobile network (HPLMN) and/or a PLMN communicating using the same air interface as the UE is currently configured to operate in accordance with.
As explained above, the UE has a software and/or firmware configuration that allows it to operate in accordance with the basic air interface and may also allow it to operate in accordance with one or more other air interfaces (RATs). If the UE identifies a preferred base station operating with an RAT with which the UE is currently configured to operate (for instance, because the relevant RAT software and/or firmware is already stored at the UE), the UE may be able to switch to that RAT and start operation with the base station. Alternatively, the UE may not find any network operating in accordance with an RAT for which it is currently configured or it may find that a preferred base station does riot operate in accordance with an RAT for which it is currently configured. In that case, the UE may consider itself as "alien". It initiates a procedure to indicate its capabilities and/or configuration to the chosen network. This may be done as part of an access procedure that for the context of this description will be referred to as a random access (RACH) procedure, which may be similar to an initial network attach request. However, the 'open RACH" procedure may be considered more of a request for configuration than only a request for access. The network may then decide to upload to the UE a compatible radio software or 0 firmware (if a compatible radio software or firmware is not already available), for example based on the information provided The UE then can switch to the uploaded RAT arid connect to the proprietary air interface. Thus, physical layer messages and procedures to support these steps need to be standardised, such as a universal broadcast channel and an open RACH procedure, which may include software updates/upgrade. However, other parts of the air interface may not need to be standardised and this will be discussed in more detail below. It should also be understood that the base station RAT may be additionally or alternatively be changed in view of the RACH procedure, which may not require reconfiguration of the mobile terminal RAT, but will still require an initialisation procedure to indicate compatibility.
In a generalised sense, this may be seen as a method of configuring wireless access technology to allow a mobile terminal to access a wireless network. The method may comprise: communicating a broadcast message from a base station of the wireless network to the mobile terminal; performing an access procedure between the mobile terminal and the base station in response to the broadcast message, such that a comparison is made between the configuration of the mobile terminal and the configuration of the base station; and selecting a wireless access technology software and/or firmware of the mobile terminal and/or the base station based on the comparison, in order to allow the mobile terminal to access the wireless network through the base station. As identified above, the terms mobile terminal and base station may encompass a wide range of devices, with the mobile terminal being a device seeking access to -8 -a network via a wireless interface arid the base station being a device providing access to the network via the wireless interface. The terms software and firmware cover all types of reconfigurable or programmable system and they may interact with reconfigurable or programmable hardware. The method may be implemented as a computer program, programmable logic, firmware or other configurable system.
Also provided is a wireless network device, configured to operate in accordance with any method disclosed herein. The wireless network device may be a mobile terminal (such as a UE, a client device, a user device or a controller for such a device) or a base station (such as a NodeB, eNodeB or similar or a controller for such a device). The wireless network device may have structural features configured to carry out any of the specific process or method features discussed. For example, it may have a transmitter and/or a receiver configured to communicate (transmit and/or receive) a broadcast message from a base station of the wireless network to the mobile terminal. It may have a processor and/or a controller configured to perform the random access procedure and/or selecting the wireless access technology software and/or firmware.
The wireless network device optionally comprises initialisation hardware, configured for communication of the broadcast message and performing the access procedure. Then, the wireless network device may further comprise wireless access hardware, separate from the initialisation hardware, which may be configurable in accordance with the selected wireless access technology software and/or firmware, to allow the mobile terminal to access the wireless network through the base station. Thus, separate hardware may be provided for the basic connectivity in comparison with the configurable connectivity provided in order to allow network access. The method may operate on such separated hardware in some embodiments.
Communicating the broadcast message and performing the access procedure typically use one or more first wireless access technology software and/or firmware. The step of selecting may comprise selecting one or more second wireless access technology software and/or firmware, different from the one or more first wireless access technology software and/or firmware. It will be -9 -understood that the mobile terminal and base station may use different first wireless access technology software and/or firmware, although these different first wireless access technology software and/or firmware will normally correspond with one another to allow successful communication. Similarly, the mobile terminal and base station may use different second wireless access technology software and/or firmware, although these different second wireless access technology software and/or firmware will normally correspond with one another to allow successful communication.
Prior to the step of selecting, an association between the one or more second wireless access technology software and/or firmware and the base station is preferably not stored at the mobile terminal. Additionally or alternatively, an association between the one or more second wireless access technology software and/or firmware and the mobile terminal is not stored at the base station, prior to the step of selecting. In other words, the mobile terminal only discovers the wireless access technology software and/or firmware for use with the base station through the access procedure and/or the base station only discovers the wireless access technology software and/or firmware for use with the mobile terminal through the access procedure. In some embodiments, the one or more second 'wireless access technology software and/or firmware is not stored at the mobile terminal and/or the base station prior to the step of selecting.
Then, the second wireless access technology software and/or firmware may be downloaded, as will be discussed below.
In some embodiments, the wireless access technology software and/or firmware defines a complete configuration for the respective wireless access technology of the mobile terminal and/or the base station. Preferably, the wireless access technology software and/or firmware defines (typically completely or at least substantially, for example by a complete set of parameters) one or more of: one or multiple protocols (potentially in software); a protocol stack (possibly in firmware and/or software); and a hardware configuration (typically in 30 firmware).
Referring now to Figure 4A, there is shown a flow of information between a mobile terminal 180 and a network base station 190 in accordance with an -10 embodiment. As discussed above, the network base station 190 transmits (broadcasts) a Universal Broadcast Message (UBM) 200, which is received by the mobile terminal 180 (and probably further received by other mobile terminals, although these are not shown). The channel for the UBM 200 may be defined by the open G standard.
In a generalised sense, the broadcast message may be understood as comprising one or more of: an identifier for the wireless network; an identifier for the base station; an indication of the software version in use by the base station; an indication of one or multiple hardware and/or software capabilities of the base 0 station; a system bandwidth; an initial transmission rate; an indication of physical resources for transmission of configuration information from the base station to the mobile station; a frequency hopping pattern; synchronisation information; header information; and error detection information. A specific example for the broadcast message will be discussed below. Typically, the step of "I 5 communicating the broadcast message from the base station comprises transmitting the broadcast message from the base station repeatedly with a time interval of predetermined length (for example, every 10ms, 20ms, 30ms, /10ms, 50ms, 100ms, 200ms, 500ms, 1 second, 5 seconds or other suitable period). In embodiments, the synchronisation information comprises one or more of: a timestamp; a system frame number; a periodicity for transmission of the broadcast message; an indication of pilot signal power; an indication of reference signal power; and an indication of pilot signal power relative to reference signal power.
In a detection and decoding step 210, the mobile terminal 180 detects and decodes the universal broadcast message 200. An initial synchronisation (SYNC) procedure 220 is then performed. In general terms, the method may be considered such that the step of performing the access procedure comprises carrying out a synchronisation between the mobile terminal and the base station.
In a generalised sense, the method may further comprise identifying that the mobile terminal is not attached or connected to a wireless network. This might be when the device is first powered up (or reset), or it may be following disconnection from a wireless network (for example, after a time duration of predetermined length has passed). Then, the method may additionally comprise initialising the wireless access technology software and/or firmware of the mobile terminal with a base configuration, the base configuration being compatible with the broadcast message and access procedure. Thus, the mobile terminal may be initialised with a configuration (RAT) suitable for basic connectivity only.
The mobile terminal 180 may store one or more preferences reaarding a suitable access network. For example, this may be analogous to the existing preferred networks stored in the SIM (or USIM) of a cellular network device. Then, the mobile terminal 180 may decide to access the network or not dependent on these preferences. Additionally or alternatively, the mobile terminal may make such a decision based on other information provided in the UBM 200, which may indicates possible the compatible RAT (or similar) that the base station 190 may require. If the hardware of the mobile terminal 180 will not support such a RAT, the mobile terminal 180 may decide not to even begin access.
In general terms, this may be seen as a step of comparing, at the mobile terminal, one or multiple data items communicated in the broadcast message with one or multiple preferences stored at the mobile terminal. Then, the step of performing the access procedure may be performed based on the step of comparing the one or multiple data items.
If the mobile terminal 180 decides to access the network through the base station 190, an authentication procedure 225 may be performed. This will be discussed in more detail below.
If the UE 180 decides to proceed, a random access procedure 230 (which may be referred to as an "open RACH" procedure) is performed. The open RACH procedure 230 comprises: transmission of an access request 232 from the mobile terminal 180 to the base station 190. The access request 232 carries hardware and/or software capabilities and may further include requested services. The base station 190 then carries out a capability verification 234.
Based on the results of the capability verification 234 (when a determination is made that the mobile terminal 180 does not have a compatible wireless access technology currently installed and/or the mobile terminal 180 has -12 the ability to operate with a compatible wireless access technology), the base station 190 sends software and/or firmware to the mobile terminal 180 in a software download message 236. The mobile terminal 180 then installs the downloaded software and/or firmware 238 and transmits a setup complete message 240 to the base station 190.
Generally, the step of performing the access procedure may comprise communicating signalling from the mobile terminal to the base station to allow the base station to determine a configuration for the mobile terminal's wireless access technology. Then, the signalling optionally comprises one or more of: an 0 identifier for the mobile terminal; an indication of one or multiple hardware and/or software capabilities of the mobile terminal; a hardware status for the mobile terminal; a subscription profile associated with the mobile terminal; and an indication of one or multiple communication services requested by the mobile terminal from the wireless network.
In some embodiments, the step of communicating the broadcast message or the step of performing the access procedure comprises communicating signalling from the base station to allow the mobile terminal to determine a configuration for the base station's wireless access technology.
In a generalised sense, the method may be considered as further comprising configuring the wireless access technology of the mobile terminal and/or base station in accordance with the selected wireless access technology software and/or firmware. The step of configuring the wireless access technology optionally comprises communicating from the base station to the mobile terminal instructions for configuration of the mobile terminal's wireless access technology to allow the mobile terminal to access the base station. Additionally or alternatively, the step of configuring the wireless access technology comprises configuring the wireless access technology of the base station; For example, the step of configuring the wireless access technology may comprise identifying a server associated with the selected wireless access technology software and/or firmware. Then, the step of configuring the wireless access technology may further comprise receiving from the identified server at the base station instructions for configuration of the base station's wireless access technology to allow the mobile terminal to access the base station. In all cases, the instructions may be the selected wireless access technology software and/or firmware or they may be an indication of the selected wireless access technology software and/or firmware (for instance, a type and/or version).
The base station 190 and the mobile terminal 180 then interact in a connection step 250 to achieve a connection. Subsequent communication 260 is then formed in accordance with the RAT configuration previously set up, which may be proprietary.
The authentication process 225 may not be an authentication procedure in the same sense as in LTE. In the present case, the UBM 200 should carry enough information so that the authentication (which may be considered more of a simple handshake, in fact, that could serve as a manner for the mobile terminal 180 to recognise the network) can happen before the open RACH procedure 230.
Referring next to Figure 4B, there is shown a flow of information between a mobile terminal and the network base station for an authentication process 225 as shown in Figure 4A. This authentication process 225 allows the network to authenticate the mobile terminal 180. The authentication process 225 begins with an authentication request 270, which is sent by the mobile terminal 180 to the base station 190. The base station 190 replies with a challenge phrase 280.
The mobile terminal returns an encrypted challenge phrase 290 to the base station 190. Then, the base station 190 can verify and/or authenticate the mobile terminal 180 and determine whether to grant or deny access in authentication step 295. Additionally or alternatively to this type of authentication, authentication can take place later (for example, when the mobile terminal 180 has full access, using a compatible RAT). It will also be understood that authentication can be reversed (for example by reversing the direction of the arrows in Figure 4B, so that the messages are sent in the other direction), so that the mobile terminal 180 can authenticate the base station 190. Indeed, such an approach may be preferred in some embodiments. Also, it may be possible for authentication in one direction (that is, authentication of the network by the mobile terminal 180 or authentication of the mobile terminal 180 by the network) to take place before or during the access procedure and for authentication in the opposite direction to -14 take place subsequently. For example the authentication in the opposite direction may take place after reconfiguration of the mobile terminal 180 and/or base station 190 RAT. Thus, a more complex form of authentication (or a second authentication step) could then happen proprietarily or between UE setup complete and Connection, to authenticate the UE.
This may more generally be understood as a step of running at least one authentication procedure between the mobile terminal and the base station before or as part of the access procedure and/or subsequent to the step of selecting.
IL 0 Some specific example parameters and parameter ranges for the UBM and RACH procedure 230 will now be discussed For the UBM 200, the following data items (fields) may be included in the format (with an example number of bits for each field in parentheses). Any combination of these data fields may be provided, although preferably all fields are used.
System bandwidth (3 bits): up to 5 or 6 supported bandwidths, for example 1.4MHz, 3MHz, 5MHz, 10MHz, 20MHz; Network ID (6 bits): Mobile Country Code (MCC, 3 bits) + Mobile Network Code (MNC, 3 bits); Timestamp (10 bits): window size/periodicity (2bits, for example lOrns/40ms or 20ms/100ms) + system frame number (8 bits); Reference signals/Pilot power: (8bits) : for instance -60 to 50 dBrn in 0.5dBm steps (220 possible values), RS enable fine frequency synchronisation; Reserved for future use (10bits); 2 Parameters to receive software and/or firmware update (16 bits): - Supported modulations (2 bits, bandwidth dependent): for example QPSK, 160AM, 64QAM, 256QAM: - PHY resources (13 bits): supporting all possible combinations of resource allocation assignments; arid -Hopping flag (1 bit): frequency hopping on or off; MAC header (48 bits): for example, could use a MAC-48 identified format; and CRC (16 bits): error detection.
Possible generation and transmission parameters of the UBM 200 are as follows. These may correspond with the data format outlined above. Some or all of these parameters may be used in any combination.
Payload length: 101 bits; - CRC generation and attachment: 16 bits; - Convolutional encoding, using a tail bit encoder with 1/3 rate: 351 bits output; - Rate Matching: repeating 16 times the bits above (for robustness), L0 resulting in 5616 bits; - Scrambling: using a fixed and known scrambling sequence; and - Modulation: OFOM, couple with OPSK, resulting in 2808 complex QPSK symbols. The UBM can then be transmitted within a time window, for example 10ms, repeatedly every 40ms. Another option could be (as in LTE) to divide the total number of bits (5616 bits in the format above) into a number (for instance 4) self-decodable redundancy versions (so 1404 bits in this example), transmitted each in the corresponding fraction of the time repetition period (so in this example; every 40ms /4 = 10ms). This has the advantage of enabling time diversity, while still allowing timely decoding of the UBM 200. The version is derived through the tirnestamp.
Suitable example parameters for open RACH procedure 230 are now detailed. The access request message 232 may have the following fields or format (example numbers of bits per field shown in parentheses).
-Preamble (16 bytes); - Hardware/Software capabilities (50-100 bytes), such as power classes, supported frequency bands, supported services, for example VolP or M2M traffic, supported features, for example CoMP, elOC, Carrier Aggregation, MIMO, etc; Requested services (4 bytes): such as M2M VoIP, Video Streaming, web browsing, etc.; Similarly to the UBM 200 transmission, the access request message 232 uses QPSK modulation and is sent using a 1/3 rate convolutional code. The rate matching can ensure a constant output; depending of the size of the hardware/software.
The software download message 236 may have the following ields or format (example numbers of bits per field shown in parentheses).
Short header (2 bytes): to indicate presence or not of software update and size (similar to MAC header); 1 flag bit indicating presence, 15 bits indicating payload size; Payload, using PHY resources indicated in UBM 200, modulation is also indicated in UBM.
Error correcting code is 1/3 convolutional and rate matching is used to ensure output compatible with PHY resources.
The setup complete message 240 is typically a ACK/NACK type of signal.
Referring, now to Figure 5, there is illustrated a schematic of interfaces between network elements. As noted above, the features that are common to other drawings are indicated by the same reference numerals, The management layer 10 (with virtualisation 15) at the base station may have wireless access technology firmware and/or software stored locally. Alternatively, these can be stored at the infrastructure layer 20 (not shown) or remote servers. It is possible for there to be multiple remote servers. For example, each server could relate to a specific device manufacturer or a specific technology originator. Three servers (first server 310, second server 320 and third server 330) are shown.
The servers 310, 320, 330 interact with the management layer 10 via a 25' specific interface 300 (termed Xx). This Xx interface 300 could either be left proprietary or standardised. In this way, different software versions may be provided to support terminals (or croups of terminals) with different capabilities or regions serving terminals in need of specific services.
Although a specific embodiment has been described, the skilled person 3 0 will understand that variations and modifications are possible. The SYNC procedure 200, the authentication procedure 225 are optional in nature and their timing, implementation and order can be varied. The specific details of the -17 random access procedure 230 can also be adjusted, for example in the data formats used; the nature of the messages communicated and their order. Similarly, the format for the UBM 200 can be varied, depending on the specific nature of the system being implemented.
Although an SDN--based approach has been described; it will be appreciated that SDN at the network need not be implemented in conjunction with the invention and the open air interface now described may be used alone. Likewise, it will be understood that the use of multiple servers to provide software to the base station can be implemented without SDN. Although the use of 0 virtualisation is suggested in the specific embodiment, it will also be understood that this is optional -18
Claims (4)
- CLAIMS1. A method of configuring wireless access technology to allow a mobile terminal to access a wireless network; the method comprising: communicating a broadcast message from a base station of the wireless network to the mobile terminal; performing an access procedure between the mobile terminal and the base station in response to the broadcast message, such that a comparison is made between the configuration of the mobile terminal and the configuration of a the base station; and selecting a wireless access technology software and/or firmware of the mobile terminal and/or the base station based on the comparison, in order to allow the mobile terminal to access the wireless network through the base station. 1 5
- 2. The method of claim 1, wherein the steps of communicating the broadcast message and performing the access procedure use one or more first wireless access technology software and/or firmware and the step of selecting comprises selecting one or more second wireless access technology software and/or 2 0 firmware, different from the one or more first wireless access technology software and/or firmware.
- 3. The method of claim 2, wherein prior to the step of selecting: an association between the one or more second wireless access technology software and/or firmware and the base station is not stored at the mobile terminal; and/or an association between the one or more second wireless access technology software and/or firmware and the mobile terminal is not stored at the base station. 3 (D -19
- 4. The method of claim 2 or claim 3, wherein prior to the step of selecting, the one or more second wireless access technology software and/or firmware is not stored at the mobile terminal and/or the base station.J. The method of any preceding claim, wherein the wireless access technology software and/or firmware defines a complete configuration for the respective wireless access technology of the mobile terminal and/or the base station.0 6. The method of any preceding claim; wherein the wireless access technology software and/or firmware defines one or more of: one or multiple protocols; a protocol stack; and a hardware configuration.7. The method of any preceding claim, further comprising: configuring the wireless access technology of the mobile terminal and/or base station in accordance with the selected wireless access technology software and/or firmware.8. The method of claim 7, wherein the step of configuring the wireless access technology comprises communicating from the base station to the mobile terminal instructions for configuration of the mobile terminal's wireless access technology to allow the mobile terminal to access the base station.9. The method of claim 7 or claim 8, wherein the step of configuring the wireless access technology comprises: identifying a server associated with the selected wireless access technology software and/or firmware; and receiving from the identified server at the base station instructions for configuration of the base station's wireless access technology to allow the mobile terminal to access the base station. 1 5-20 - 10. The method of claim 8 or 9, wherein the instructions are the selected wireless access technology software and/or firmware.11. The method of any preceding claim, where the step of performing the access procedure comprises communicating signalling from the mobile terminal to the base station to allow the base station to determine a configuration for the mobile terminal's wireless access technology.12. The method of claim 11, wherein the signalling comprises one or more of: an identifier for the mobile terminal; an indication of one or multiple hardware and/or software capabilities of the mobile terminal; a hardware status for the mobile terminal; a subscription profile associated with the mobile terminal; and an indication of one or multiple communication services requested by the mobile terminal from the wireless network.13. The method of any preceding claim, wherein the step of communicating the broadcast message or the step of performing the access procedure comprises communicating signalling from the base station to allow the mobile terminal to determine a configuration for the base station's wireless access technology.14. The method of any preceding claim, wherein the step of communicating the broadcast message from the base station comprises transmitting the broadcast message from the base station repeatedly with a time interval of 2 5 predetermined length.15. The method of any preceding claim, wherein the broadcast message comprises one or more of: an identifier for the wireless network; an identifier for the base station; an indication of the software version in use by the base station; an indication of one or multiple hardware and/or software capabilities of the base station; a system bandwidth; an initial transmission rate; an indication of physical resources for transmission of configuration information from the base station to the mobile station; a frequency hopping pattern; synchronisation inforrnation; header information; and error detection information.16. The method of claim 15, wherein the synchronisation information comprises one or more of: a timestamp; a system frame number; a periodicity for transmission of the broadcast message; an indication of pilot signal power; an indication of reference signal power; and an indication of pilot signal power relative to reference signal power.17. The method of any preceding claim; wherein the step of performing the access procedure comprises carrying out a synchronisation between the mobile terminal and the base station.18. The method of any preceding claim, further comprising: comparing, at the mobile terminal, one or multiple data items communicated in the broadcast message with one or multiple. preferences stored at the mobile terminal; and wherein the step of performing the access procedure s performed based on the step of comparing the one or multiple data items.19. The method of any preceding claim, further comprising: identifying that the mobile terminal is not attached or connected to a wireless network; initialising the wireless access technology software and/or firmware of the mobile terminal with a base configuration: the base configuration being compatible with the broadcast message and access procedure.20. The method of any preceding claim, further comprising: running at least one authentication procedure between the mobile terminal and the base station before or as part of the access procedure and/or subsequent to the step of selecting.-22 - 21. A computer program, configured to perform the method of any preceding claim when operated by a computer.22. A wireless network device; configured to operate in accordance with any one of claims 1 to 20.23. The wireless network device of claim 22, wherein the wireless network device is a mobile terminal or a base station.24. The wireless network device of claim 22 or claim 23, comprising: initialisation hardware, configured for communication of the broadcast message and performing the access procedure; and wireless access hardware, separate from the initialisation hardware and configurable in accordance with the selected wireless access technology software and/or firmware, to allow the mobile terminal to access the wireless network through the base station.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1500755.2A GB2534200A (en) | 2015-01-16 | 2015-01-16 | Wireless access technology configuration |
PCT/EP2015/079890 WO2016113060A1 (en) | 2015-01-16 | 2015-12-15 | Wireless access technology configuration |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
GB1500755.2A GB2534200A (en) | 2015-01-16 | 2015-01-16 | Wireless access technology configuration |
Publications (2)
Publication Number | Publication Date |
---|---|
GB201500755D0 GB201500755D0 (en) | 2015-03-04 |
GB2534200A true GB2534200A (en) | 2016-07-20 |
Family
ID=52630708
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
GB1500755.2A Withdrawn GB2534200A (en) | 2015-01-16 | 2015-01-16 | Wireless access technology configuration |
Country Status (2)
Country | Link |
---|---|
GB (1) | GB2534200A (en) |
WO (1) | WO2016113060A1 (en) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20240298166A1 (en) * | 2021-06-30 | 2024-09-05 | Telefonaktiebolaget Lm Ericsson (Publ) | Modifying Communication Behavior of a Communication Device |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020082044A1 (en) * | 2000-12-21 | 2002-06-27 | Davenport David Michael | Wireless communication with a mobile asset employing dynamic configuration of a software defined radio |
EP2613592A1 (en) * | 2012-01-09 | 2013-07-10 | Telefonaktiebolaget L M Ericsson (Publ) | Method and device for selecting radio access technology |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2371713A (en) * | 2001-01-26 | 2002-07-31 | Motorola Inc | Method and apparatus for pre-configuring a wireless communication device for future operation in a distant wireless communication system |
US20060068777A1 (en) * | 2004-06-30 | 2006-03-30 | Sadowsky John S | Air interface cooperation between WWAN and WLAN |
US8396041B2 (en) * | 2005-11-08 | 2013-03-12 | Microsoft Corporation | Adapting a communication network to varying conditions |
US20100111097A1 (en) * | 2008-11-04 | 2010-05-06 | Telcom Ventures, Llc | Adaptive utilization of a network responsive to a competitive policy |
-
2015
- 2015-01-16 GB GB1500755.2A patent/GB2534200A/en not_active Withdrawn
- 2015-12-15 WO PCT/EP2015/079890 patent/WO2016113060A1/en active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020082044A1 (en) * | 2000-12-21 | 2002-06-27 | Davenport David Michael | Wireless communication with a mobile asset employing dynamic configuration of a software defined radio |
EP2613592A1 (en) * | 2012-01-09 | 2013-07-10 | Telefonaktiebolaget L M Ericsson (Publ) | Method and device for selecting radio access technology |
Also Published As
Publication number | Publication date |
---|---|
WO2016113060A1 (en) | 2016-07-21 |
GB201500755D0 (en) | 2015-03-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN111698723B (en) | Method and apparatus for sidelink logical channel establishment in a wireless communication system | |
JP5345634B2 (en) | User equipment function update in wireless communication | |
US10085297B2 (en) | Method and apparatus supporting device-to-device (D2D) communication in a wireless communication system | |
Roessler et al. | Lte-advanced (3gpp rel. 12) technology introduction white paper | |
US20140071942A1 (en) | Apparatuses, systems, and methods for offloading data traffic | |
US11070954B2 (en) | Distributed QoS control for multicast | |
US9351336B2 (en) | Method for supporting communication using two or more radio access technologies and apparatus for same | |
CN112423319B (en) | Method and apparatus for header compression configuration for side-link radio bearers | |
US11849502B2 (en) | Inter-operator device-to-device operation | |
US20220330352A1 (en) | Disaggregated ue | |
EP2763439A1 (en) | Method and apparatus for establishing a direct connection in a proximity-services communication system | |
WO2022062846A1 (en) | Method and apparatus for path switch | |
EP4193618A1 (en) | Relaying techniques for d2d or sidelink communications | |
AU2020290975A1 (en) | Device-to-device quality of service flow management | |
US8064480B2 (en) | Method and apparatus for providing interoperability between a first protocol and a second protocol | |
GB2534200A (en) | Wireless access technology configuration | |
EP3991459B1 (en) | Method and apparatus for enabling 5g services with pre-5g universal integrated circuit card (uicc) | |
CN116963211A (en) | Method and apparatus for supporting direct communication path from PC5 to Uu | |
EP3211949B1 (en) | Terminal device and communication method | |
JP6867338B2 (en) | Inter-operator D2D operation | |
US20170245264A1 (en) | Terminal device, base station device, integrated circuit, and communication method | |
WO2022238153A1 (en) | A method of and a node device for communicating network information to an uncommissioned node device to be added to a network and a method of joining an uncommissioned node device into a network | |
KR20240136140A (en) | Method and apparatus for configuring mobile backhaul in communication system | |
EP4331294A1 (en) | Apparatus and methods for improving multi-sim devices performance and operation | |
ES2685093T3 (en) | Server and procedure for server operation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WAP | Application withdrawn, taken to be withdrawn or refused ** after publication under section 16(1) |