Patent Application
20180167870
The present disclosure relates generally to communications, and more particularly to communications involving wireless access points and related nodes.
The disclosure herein is provided in the context of integration of LTE and WLAN. It should be understood that embodiments described herein may also be applicable to wireless access networks and User Equipment (UE) implementing other access technologies and standards. LTE and WLAN are used as example technologies where some embodiments are suitable, and discussion of LTE and WLAN herein may be useful to understand some embodiments.
LTE and WLAN aggregation (LWA) is a feature where a wireless terminal (also referred to as a mobile terminal, a UE, a user equipment, a user equipment node, etc.) may receive and transmit using radio links with both an eNB (also referred to as base stations) and a WLAN access point AP, and LWA is currently being standardized by 3GPP in Release 13 as part of [RP-150510], revised in [RP-151114]. In a split bearer architecture option (denoted also as 3C) of LTE/WLAN aggregation, the downlink data is split on the PDCP layer in the eNB. The eNB may route PDCP PDUs dynamically via eNB RLC to the UE directly, or via a backhaul channel to WLAN and then to the UE. In a separate bearer architecture (also denoted 2C), lower layers of a bearer are switched to LTE or WLAN meaning all PDCP packets of that bearer are routed via either LTE or WLAN side.
The approaches described above could be pursued, but are not necessarily approaches that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, the approaches described above are not prior art to embodiments in this application and are not admitted to be prior art by inclusion above.
According to some embodiments of inventive concepts, a method may be provided to operate a termination node connected to a plurality of wireless access points. The method may include providing a list of wireless access point identifications, and each of the wireless access point identifications may correspond to a respective one of the plurality of wireless access points connected to the termination node. The method may include receiving an interface setup request at the termination node from a communication node of a wireless communication network. The method may include transmitting a subset of the wireless access point identifications from the list to the communication node responsive to receiving the interface setup request from the communication node of the wireless communication network.
In addition, the method may include identifying the subset of the wireless access point identifications from the list as being wireless access point identifications for wireless access points that are relevant with respect to the communication node of the wireless communication network, responsive to receiving the interface setup request at the termination node, responsive to receiving the interface setup request at the termination node. Identifying the subset may include identifying the subset of the wireless access point identifications from the list as being wireless access point identifications for wireless access points that are in a coverage area of the communication node of the wireless communication network. Moreover, the interface setup request may include an identification of the communication node of the wireless communication network, and identifying the subset of the wireless access point identifications may include identifying the subset of wireless access point identifications based on the identification of the communication node.
The method may also include transmitting an update to the communication node indicating removal of one of the subset of wireless access point identifications, responsive to removing the one of the subset of wireless access point identifications from the list after transmitting the subset.
In addition, the method may include determining if a new wireless access point identification should be included in the subset responsive to adding the new wireless access point identification to the list after transmitting the subset. The method may also include transmitting an update to the communication node indicating addition of the new wireless access point identification responsive to determining that the new wireless access point identification should be included in the subset.
The plurality of wireless access points may provide wireless communications in accordance with a first radio access technology, and the communication node of the wireless communication network be a base station that provides wireless communications in accordance with a second radio access technology different than the first radio access technology. For example, the first radio access technology may be a Wireless Local Area Network access technology, and the second radio access technology may be a Long Term Evolution access technology.
Responsive to receiving the interface setup request, an interface may be established between the termination node and the communication node. After establishing the interface, downlink data may be received over the interface from the communication node. After receiving the downlink data, the downlink data may be transmitted to a respective one of the wireless access points for wireless transmission to a wireless terminal. For example, the interface may be an Xw interface.
According to some embodiments of inventive concepts, a method may be provided to operate a communication node of a wireless communication network. The method may include transmitting an interface setup request to a termination node, and the termination node may be connected to a plurality of wireless access points. The method may include receiving an interface setup response from the termination node, and the interface setup response message may include wireless access point identifications for a subset of the plurality of wireless access points connected to the termination node. The method may include establishing an interface between the communication node and the termination node based on the interface setup request and/or the interface setup response. The method may include transmitting downlink data over the interface to the termination node for downlink transmission through one of the subset of wireless access points to a wireless terminal in a coverage area of the communication node after establishing the interface.
The interface setup request may include information relating to the communication node, and the information relating to the communication node may include an identification of the communication node. The subset of the plurality of wireless access points may include wireless access points that are relevant with respect to the communication node based on the information relating to the communication node included in the setup request.
The method may further include receiving an update from the termination node indicating removal of one of the subset of wireless access point identifications.
In addition, the method may include receiving an update from the termination node indicating addition of a new wireless access point identification.
The communication node of the wireless communication network may be a base station that provides wireless communications in accordance with a first radio access technology, and the plurality of wireless access points may provide wireless communications in accordance with a second radio access technology, different than the first radio access technology. For example, the first radio access technology may be a Long Term Evolution access technology, and the second radio access technology may be a Wireless Local Area Network access technology.
The interface setup request may be an Xw interface setup request, and the interface setup response may be an Xw interface setup response.
The method may also include transmitting the wireless access point identifications from the interface setup response to the wireless terminal in the coverage area of the communication node. In addition, the method may include receiving a measurement report from the wireless terminal regarding at least one of the subset of the plurality of wireless access points, and transmitting the downlink data over the interface may include transmitting the downlink data over the interface responsive to the measurement report received from the wireless terminal.
Transmitting downlink data over the interface for downlink transmission to the wireless terminal may include transmitting the downlink data over the interface while the wireless terminal is in an RRC_Connected state with respect to the communication node.
According to some embodiments of inventive concepts, a termination node may be provided for use in connection with a plurality of wireless access points. The termination node may include a network interface and a processor connected to the network interface. The network interface may be configured to communicate with the plurality of wireless access points and with a communication node of a wireless communication network. The processor may be configured to provide a list of wireless access point identifications, and each of the wireless access point identifications may corresponds to a respective one of the plurality of wireless access points connected to the termination node. The processor may be configured to receive an interface setup request at the termination node through the network interface from the communication node of the wireless communication network. The processor may be configured to transmit a subset of the wireless access point identifications from the list through the network interface to the communication node responsive to receiving the interface setup request from the communication node of the wireless communication network.
According to some embodiments of inventive concepts, a termination node may be provided for use in connection with a plurality of wireless access points. The termination node may be adapted to provide a list of wireless access point identifications, and each of the wireless access point identifications may correspond to a respective one of the plurality of wireless access points connected to the termination node. The termination node may be adapted to receive an interface setup request at the termination node from a communication node of a wireless communication network. The termination node may be adapted to transmit a subset of the wireless access point identifications from the list to the communication node responsive to receiving the interface setup request from the communication node of the wireless communication network.
According to some embodiments of inventive concepts, a termination node may be provided for use in connection with a plurality of wireless access points. The termination node may include a list providing module, and interface setup request receiving module, and a subset transmission module. The list providing module may be configured to provide a list of wireless access point identifications, and each of the wireless access point identifications may correspond to a respective one of the plurality of wireless access points connected to the termination node. The interface setup request receiving module may be configured to receive an interface setup request at the termination node from a communication node of a wireless communication network. The subset transmission module may be configured to transmit a subset of the wireless access point identifications from the list to the communication node responsive to receiving the interface setup request from the communication node of the wireless communication network.
According to some embodiments of inventive concepts, a communication node of a wireless communication network may be provided. The communication node may include a network interface, a wireless interface, and a processor coupled with the network interface and the wireless interface. The network interface may be configured to communicate with a termination node. The wireless interface configured to provide wireless communication with a plurality of wireless terminals in a coverage area of the communication node. The processor may be configured to transmit an interface setup request through the network interface to the termination node, and the termination node may be connected to a plurality of wireless access points. The processor may be configured to receive an interface setup response from the termination node through the network interface, and the interface setup response message may include wireless access point identifications for a subset of the plurality of wireless access points connected to the termination node. The processor may be configured to establish an interface through the network interface between the communication node and the termination node based on the interface setup request and/or the interface setup response. The processor may be configured to transmit downlink data over the interface to the termination node for downlink transmission through one of the subset of wireless access points to a wireless terminal in a coverage area of the communication node after establishing the interface.
According to some embodiments of inventive concepts, a communication node of a wireless communication network may be provided. The communication node may be adapted to transmit an interface setup request to a termination node, and the termination node may be connected to a plurality of wireless access points. The communication node may be adapted to receive an interface setup response from the termination node, and the interface setup response message may include wireless access point identifications for a subset of the plurality of wireless access points connected to the termination node. The communication node may be adapted to establish an interface between the communication node and the termination node based on the interface setup request and/or the interface setup response. The communication node may be adapted to transmit downlink data over the interface to the termination node for downlink transmission through one of the subset of wireless access points to a wireless terminal in a coverage area of the communication node after establishing the interface.
According to some embodiments of inventive concepts, a communication node of a wireless communication network may be provided, The communication node may include a request transmission module, a response reception module, an interface establishing module, and a downlink transmission module. The request transmission module may be configured to transmit an interface setup request to a termination node, and the termination node may be connected to a plurality of wireless access points. The response reception module may be configured to receive an interface setup response from the termination node, and the interface setup response message may include wireless access point identifications for a subset of the plurality of wireless access points connected to the termination node. The interface establishing module may be configured to establish an interface between the communication node and the termination node based on the interface setup request and/or the interface setup response. The downlink transmission module may be configured to transmit downlink data over the interface to the termination node for downlink transmission through one of the subset of wireless access points to a wireless terminal in a coverage area of the communication node after establishing the interface.
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:
Inventive concepts will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.
Although various embodiments are disclosed herein in the context of being performed by a UE and/or a network node, they are not limited thereto and instead can be performed in any type of electronic communication device or system.
Note that although terminology from LTE and WLAN is generally used in this disclosure to exemplify embodiments of inventive concepts, this should not be seen as limiting the scope of inventive concepts to only these systems. Other wireless systems, including variations and successors of 3GPP LTE and WCDMA systems, WiMAX (Worldwide Interoperability for Microwave Access), 1 MB (Ultra Mobile Broadband), HSDPA (High-Speed Downlink Packet Access), GSM (Global System for Mobile Communications), etc., may also benefit from exploiting embodiments of present inventive concepts disclosed herein.
Also note that terminology such as base station (also referred to as NodeB, eNB, eNodeB, or Evolved Node B) and wireless terminal or mobile terminal (also referred to as User Equipment, User Equipment node, or UE) should be considered as non-limiting and does not imply a certain hierarchical relation between the two. In general, a base station (e.g., a “NodeB” or “eNodeB”) and a wireless terminal (e.g., a “UE”) may be considered as examples of respective different communications devices that communicate with each other over a wireless radio channel.
Using LTE-WLAN aggregation (LWA), base station 1101a may configure wireless terminal 1301 to use radio resources of base station 1101a and to use radio resources of one or more of WLAN access points 1201 (e.g., AP-1 and AP-2) through WLAN termination node 1001 while wireless terminal 1301 is in an RRC connected state. Similarly, base station 1101a may configure wireless terminal 1302 to use radio resources of base station 1101a and to use radio resources of one or more of WLAN access points 1201 (e.g., AP-1′ and AP-2′) through WLAN termination node 1002 while wireless terminal 1302 is in an RRC connected state. Operations of LWA are discussed in greater detail below.
The stage two CR R2-152922 currently captures the following assumptions (not a full list):
In order for the eNB and the WT to activate LWA functionality over the Xw interface, they may need to exchange a basic set of parameters which are useful/necessary to set up the user plane UP and control plane CP. In the intra-LTE case, 2 eNBs set up an X2 interface between them using X2AP [3GPP TS 36.423, TS 36.300]. The interface setup function is provided by the application protocol, but X2AP cannot be reused because the WT does not necessarily reside in an eNB. A new protocol, here called XwAP, may have to be defined between the eNB and the WT for the LWA case.
At interface setup, the eNB and the WT may need to exchange a basic set of identifiers (including, for example, the list of BSSIDs corresponding to the APs connected to the WT so that the eNB may use them for LWA). The same paradigm that is used between eNBs in X2AP may not be usable between the eNB and the WT. In X2AP, the two eNBs exchange their full list of cells at X2 setup, but in this case the exchange of the full list of BSSIDs from the WT may be undesirable. In case the WT is implemented in an AC, it may be possible for several thousands of APs to be connected to it, covering a very large area. In case such area is much greater than the coverage area of the eNB, only a small subset of those APs will actually overlap with the eNB cells and will be of interest for LWA. Any AP not overlapping with the eNB will not be measured by a UE served by the eNB and therefore will never be considered for LWA. Including non-overlapping/non-neighboring APs in the list will result in unnecessary processing and resource burden for the receiving eNB.
The WT is made aware of the coverage area of the eNB, so that when the Xw interface is established between an eNB and the WT, the WT only includes BSSIDs which are relevant (e.g., of interest) to the eNB (e.g., which are deployed in the eNB coverage area). The same criterion may be used when the WT signals a configuration change to the eNB, for example, when APs are added/removed/modified from the set which is connected to the WT itself: only information related to those which are relevant to the eNB will be signaled to the eNB.
The information on eNB coverage area can be obtained, for example, from the Global eNB ID signaled by the eNB in the Xw SETUP REQUEST message, from a list of served cells (and/or neighbor cells) in case it is signaled from the eNB to the WT, and/or from geographical information signaled by the eNB itself to the WT.
Embodiments of inventive concepts may reduce/avoid the need for the eNB to process and store long lists of BSSIDs coming from its WTs. A benefit(s) in terms of scalability, signaling, and/or implementation may be significant. In LWA scenarios, an eNB may overlap with several dozens of APs, which will be connected to one or more WTs, and each WT may reside in an AC, which may serve thousands of APs. Without filtering, the eNB may need to process and store several thousands of BSSIDs at every Xw setup as opposed to only the few dozens with which it may interoperate.
In case of WT configuration update, benefits may be even more evident. For example, there may be no need to initiate a configuration update procedure toward an eNB in case APs are added, removed, and/or modified outside the eNB coverage area.
A signaling flow for some embodiments of inventive concepts is described below and shown in
In some other embodiments, BSSIDs are added/removed/modified from the WT configuration. The signaling flow is shown in
In a still another embodiment, the association table in the WT is organized per-cell instead of per-eNB, i.e. the rows of the table contain ECGIs instead of Global eNB IDs (see
In a yet another embodiment, conceptually similar to the embodiment discussed above with respect to
In another embodiment, the eNB-BSSID association table in the WT may be organized according to geographical position (e.g. latitude/longitude/height), where the AP positions are reported by the APs themselves to the WT (e.g. using an on-board GPS receiver), or from previous positioning measurements from associated UEs, or configured via e.g. OAM. The eNB signals its own position in the Xw SETUP REQUEST message (e.g. encoding it as in the E-UTRAN Access Point Position IE [3GPP TS 36.455]), as well as a “maximum distance of interest” (MaxDistOfInterest): the WT may then includes all BSSIDs deployed within that distance of the position signaled by the eNB. A signaling flow for the Xw Setup is shown in
In another embodiment, each BSSID in the WT is associated with one or more Tracking Area Codes (TACs), defined as in 3GPP TS 36.300. The eNB includes its TAC in the Xw SETUP REQUEST message, and the WT includes in the Xw SETUP RESPONSE message a filtered list with only those BSSIDs associated with the TAC signaled by the eNB.
In another embodiment, the eNB indicates to the WT whether it requires the BSSID list to be filtered or not, by including the BSSID List Filtering IE (see
In another embodiment, the eNB indicates to the WT the maximum desired periodicity for WT CONFIGURATION UPDATE messages, by including the Maximum WT Update Periodicity IE (see
Embodiments disclosed herein may thus provide methods for associating WLAN APs to one or more LTE eNBs, organizing such associations in a network node, and/or using such associations to set up network interfaces in an improved/optimal way, to thereby reduce signaling and/or node resource usage.
Further discussion of possible signaling mechanisms to set up Xw and transfer configuration information between the eNB and the WT is provided below.
As discussed in [R3-151638], the eNB may/should initiate Xw setup toward the WT (e.g. following UE measurements). The WT may reply with the list of broadcasted ESSIDs and BSSIDs it supports (included with any radio-related information useful/necessary to set up the relation).
The eNB may initiate the Xw Setup procedure and the WT may reply signaling the list of broadcasted ESSIDs and BSSIDs it supports, included with radio-related information useful/necessary to set up the relation. A possible signaling flow for such a class 1 Xw procedure (normal condition) is shown in
It may also be beneficial to envisage a class 1 WT Configuration Update procedure, to enable a WT to signal a change of configuration to an eNB with which it has a relation. A class 1 WT Configuration Update procedure, to enable a WT to signal configuration change to eNBs, may be beneficial.
It is possible for a WT to have a large number of APs connected (up to several thousands), but only a small subset of those APs will typically be in the coverage area of the eNB. Therefore, it is likely that only a small subset of the BSSID list signaled by the WT will be relevant to the eNB. In order to save processing time and/or resources in the eNB, it may be desirable for the WT to filter the BSSID list, to include only those BSSIDs for APs deployed in the same coverage area of the eNB. This could be done e.g. by looking at the Global eNB ID, TAC, and/or location signaled by the eNB at Xw Setup.
It may thus be desirable for the WT to filter the BSSID list signaled to the eNB at Xw Setup and WT Configuration Update, including only BSSIDs for APs deployed in the coverage area of the eNB (identified e.g. by looking at the Global eNB ID, TAC, and/or location signaled by the eNB at Xw Setup).
In the event of an abnormal failure or at initialization of the Xw interface, the Xw AP UE-related context may need to be set to a defined state. It may be useful to envisage a class 1 Xw Reset procedure. This procedure may/should result in the receiving node aborting any other ongoing procedures but maintaining the application-level configuration data exchanged at interface setup. Both eNB-initiated and WT-initiated Xw Reset procedures may be beneficial. A class 1 Xw Reset procedure may thus be introduced.
Signaling mechanisms to set up and maintain Xw and to exchange information between the eNB and the WT have thus been discussed. For example, the eNB may initiate the Xw Setup procedure and the WT may reply signaling the list of broadcasted ESSIDs and BSSIDs it supports, included with radio-related information useful/necessary to set up the relation. A class 1 WT Configuration Update procedure, to enable a WT to signal configuration change to eNBs, may be provided. It may be desirable for the WT to filter the BSSID list signaled to the eNB at Xw Setup and WT Configuration Update, including only BSSIDs for APs deployed in the coverage area of the eNB (identified e.g. by looking at the Global eNB ID, TAC, and/or location signaled by the eNB at Xw Setup). Moreover, a class 1 Xw Reset procedure may be provided.
Operations of a termination node 1001 (e.g., an access point controller) will now be discussed with reference to the flow chart of
At block 1501 processor 1007 may provide a list of wireless access point identifications (e.g., using instructions of list providing module 1601), with each of the wireless access point identifications corresponding to a respective one of the plurality of wireless access points 1201 connected to the termination node 1001. Processor 1003 may wait at blocks 1503 and 1505 until the list changes or an interface setup request is received. A first interface setup request may be received by processor 1003 (through network interface 1005) at block 1505 (e.g., using instructions of interface setup request receiving module 1603). Responsive to receiving such an interface setup request at block 1505, processor 1003 may determine at block 1507 whether a list filtering information element (IE) of the interface setup request has a first value or a second value (e.g., using instructions of List Filtering IE Determining Module 1605).
Responsive to receiving a first interface setup request from a first communication node 1101a of a wireless communication network at block 1505 and responsive to the list filtering IE having the first value at block 1507, processor 1003 may identify at block 1509a subset of the wireless access point identifications from the list as being wireless access point identifications for wireless access points that are relevant with respect to first communication node 1101a of the wireless communication network (e.g., using instructions of subset identification module 1607). Identifying the subset at block 1509 may include identifying the subset of the wireless access point identifications from the list as being wireless access point identifications for wireless access points that are in a coverage area of first communication node 1101a of the wireless communication network.
The first interface setup request may also include an identification of first communication node 1101a of the wireless communication network, and identifying the subset of the wireless access point identifications at block 1509 may include identifying the subset of wireless access point identifications based on the identification of first communication node 1101a. For example, the identification of first communication node 1101a may include a global eNB identification, and/or a cell identification, such as a E-UTRAN cell global identifier.
At block 1511, processor 1003 may then transmit the subset of the wireless access point identifications from the list (through network interface 1005) to first communication node 1101a (e.g., using instructions of subset transmission module 1608).
Responsive to receiving a second interface setup request from a second communication node 1101b (through network interface 1005) at block 1505 and responsive to the list filtering IE having the second value at block 1507, processor 1003 may transmit the list of wireless access point identifications (through network interface 1005) to second communication node 1101b without filtering (e.g., using instructions of list transmission module 1609).
Responsive to detecting a change in the list at block 1503 (e.g., using instructions of change detecting module 1611), processor 1003 may determine if a subset of the list or the entire list was last transmitted at block 1515 (e.g., using instructions of subset/list determining module 1613). Responsive to determining at block 1515 that a subset was transmitted, processor 1003 may determine at block 1517 if the change affects the subset (e.g., using instructions of change determining module 1615). For example, processor 1003 may transmit (through network interface 1005) an update at block 1519 (e.g., using instructions of subset update transmission module 1619) to communication node 1101a indicating removal of one of the subset of wireless access point identifications responsive to removing the wireless access point identifications from the subset.
Responsive to determining that a new wireless access point identification has been added to the list after transmitting the subset, processor 1003 may determine at block 1517 if the new wireless access point identification should be included in the subset (e.g., using instructions of change determining module 1615). Responsive to determining that the new wireless access point identification should be included in the subset at block 1517, processor 1003 may transmit an update at block 1519 (through network interface) to communication node 1101a indicating addition of the new wireless access point identification to the subset (e.g., using instructions of subset update transmission module 1619). If processor 1003 determines at block 1517 that the change in the list does affect the subset, no update may be needed.
At block 1531, processor 1003 may establish an interface (e.g., an Xw interface) between termination node 1001 and communication node 1101a/1101b (through network interface 1005) responsive to receiving the respective interface setup request from a communication node (e.g., using instructions of interface establishing module 1621). At block 1533, processor 1003 may receive downlink data over the interface from the respective communication node 1101 after establishing the interface (e.g., using instructions of DL data reception module 1623). At block 1535, processor 1003 may transmit the downlink data (through network interface 1005) to a respective one of wireless access points 1201 for wireless transmission to a wireless terminal after receiving the downlink data (e.g., using instructions of DL data transmission module 1625).
According to some embodiments of
Various operations of
Operations of a communication node 1101 (e.g., a base station or eNB) of a wireless communication network will now be discussed with reference to the flow charts of
At block 1701, processor 1103 may determine when to transmit an interface setup request. Responsive to determining that a first interface setup request should be transmitted at block 1701, processor 1103 may determine at block 1703 whether list filtering should be applied (e.g., using instructions of list filtering determination module 1801). Responsive to determining that list filtering should be applied at block 1703, processor 1103 may transmit a first interface setup request (through network interface 1105) to first termination node 1001 at block 1705 (e.g., using instructions of first request transmission module 1803), with first termination node 1001 being connected to a plurality of wireless access points 1201, and with the first interface setup request including a list filtering information element having a first value. The interface setup request may include information relating to communication node 1101a, such as an identification of the communication node 1101a.
At block 1707, processor 1103 may then receive a first interface setup response (through network interface 1105) from first termination node 1001 (e.g., using instructions of first response reception module 1805). In particular, the first interface setup response message may include wireless access point identifications for a subset of the plurality of wireless access points connected to the termination node 1001. The subset of the plurality of wireless access points, for example, may include wireless access points that are relevant with respect to the communication node 1101a based on the information relating to the communication node 1101a included in the setup request.
At block 1713, processor 1103 may then establish an interface between the communication node 1101a and first termination node 1001 (through network interface 1105) based on the first interface setup request and/or the first interface setup response (e.g., using instructions of first interface establishing module 1807). After establishing the interface, at block 1715, processor 1103 may transmit downlink data over the interface to first termination node 1001 (through network interface 1105) for downlink transmission through one of the subset of wireless access points 1201 to a wireless terminal 1301 in a coverage area CA of the communication node 1101a (e.g., using instructions of first downlink DL transmission module 1809).
Communication node 1101a of the wireless communication network may be a base station that provides wireless communications in accordance with a first radio access technology, and the plurality of wireless access points 1201 may provide wireless communications in accordance with a second radio access technology (different than the first radio access technology). For example, the first radio access technology may be a Long Term Evolution (LTE) access technology, and wherein the second radio access technology may be a Wireless Local Area Network (WLAN) access technology. Moreover, the interface setup request may be an Xw interface setup request, and the interface setup response may be an Xw interface setup response.
Responsive to determining that a second interface setup request should be transmitted at block 1701, processor 1103 may determine at block 1703 whether list filtering should be applied (e.g., using instructions of list filtering determination module 1801). Responsive to determining that list filtering should not be applied at block 1703, processor 1103 may transmit a second interface setup request (through network interface 1105) to a second termination node 1002 at block 1709 (e.g., using instructions of second request transmission module 1811), with second termination node 1002 being connected to a second plurality of wireless access points 1201, and with the second interface setup request including a list filtering information element having a second value (different than the first value).
At block 1711, processor 1103 may receive (through network interface 1103) a second interface setup response from the second termination node 1002 (e.g., using instructions of second response reception module 1813), with the second interface setup response message including wireless access point identifications for all of the plurality of wireless access points 1201 connected to the second termination node 1002. At block 1713, processor 1103 may establish a second interface (through network interface 1105) between communication node 1101a and second termination node 1002 based on the second interface setup request and/or the second interface setup response (e.g., using instructions of second interface establishing module 1815). After establishing the second interface, processor 1103 may transmit downlink data (through network interface 1105) over the second interface to second termination node 1002 at block 1715 (e.g., using instructions of second downlink transmission module 1817) for downlink transmission through one of the wireless access points 1201 to a wireless terminal 1302 in a coverage area CA of the communication node 1101a.
At block 1716, processor 1103 may receive an update (through network interface) from a termination node 1001/1002 (e.g., using instructions of update reception module 1819). Responsive to determining at block 1717 that the update indicates removal, processor 1103 may remove an indicated wireless access point identification from the subset/list of wireless access point identifications for the respective termination node at block 1721 (e.g., using instructions of identification removal module 1821). Responsive to determining at block 1717 that the update indicates addition, processor 1103 may add an indicated wireless access point identification to the subset/list of wireless access point identifications for the respective termination node at block 1719 (e.g., using instructions of identification addition module 1823).
Operations of block 1715 will now be discussed in greater detail with respect to
Various operations of
A method of operating a termination node (1001) connected to a plurality of wireless access points (1201), the method comprising:
The method of Embodiment 1 further comprising:
The method of Embodiment 2 wherein identifying the subset comprises identifying the subset of the wireless access point identifications from the list as being wireless access point identifications for wireless access points that are in a coverage area of the communication node (1101a) of the wireless communication network.
The method of any of Embodiments 2-3 wherein the interface setup request includes an identification of the communication node (1101a) of the wireless communication network, and wherein identifying the subset of the wireless access point identifications comprises identifying the subset of wireless access point identifications based on the identification of the communication node (1101a).
The method of Embodiment 4, wherein the identification of the communication node (1101a) comprises a global eNB identification.
The method of Embodiment 4, wherein the identification of the communication node (1101a) comprises a cell identification.
The method of Embodiment 6, wherein the cell identification comprises a E-UTRAN cell global identifier.
The method of any of Embodiments 4-7 wherein the interface setup request includes a list of neighbor cell identifications for cells of other nodes of the wireless communication network neighboring the communication node (1101a), and wherein identifying the subset comprises identifying the subset further based on the list of neighbor cells.
The method of any of Embodiments 2-8 wherein the interface setup request includes position information for the communication node (1101a) of the wireless communication network, and wherein identifying the subset of the wireless access point identifications comprises identifying the subset of wireless access point identifications based on the location of the communication node (1101a).
The method of Embodiment 9 where the interface setup request includes information for a maximum distance of interest, and wherein identifying the subset of the wireless access point identifications comprises identifying the subset of wireless access point identifications as wireless access point identifications for wireless access points located within the maximum distance of interest from the communication node (1101a).
The method of any of Embodiments 2-10 wherein the interface setup request includes an identifications of a plurality of cells of the communication node (1101a), and wherein identifying the subset of the wireless access point identifications comprises identifying the subset of wireless access point identifications based on the identifications of the plurality of cells (1101a).
The method of Embodiment 11 wherein the identifications of the plurality of cells comprise E-UTRAN Cell Global Identifiers.
The method of any of Embodiments 2-12 wherein the interface setup request includes a tracking area code for the communication node (1101a), and wherein identifying the subset of the wireless access point identifications comprises identifying the subset based on the tracking area code for the communication node (1101a).
The method of any of Embodiments 1-13 wherein the interface setup request includes a list filtering information element having a first value, and wherein transmitting the subset comprises transmitting the subset responsive to the list filtering information element having the first value, the method further including:
The method of any of Embodiments 1-14 further comprising:
The method of any of Embodiments 1-15 further comprising:
The method of any of Embodiments 1-16 wherein the interface setup request includes a maximum desired periodicity for termination node updates, wherein transmission of updates from the termination node (1001) to the communication node (1101a) are limited according to the maximum desired periodicity for termination node updates.
The method of any of Embodiments 1-17 wherein the plurality of wireless access points (1201) provide wireless communications in accordance with a first radio access technology, and wherein the communication node (1101a) of the wireless communication network comprises a base station that provides wireless communications in accordance with a second radio access technology different than the first radio access technology.
The method of Embodiment 18, wherein the first radio access technology is a Wireless Local Area Network (WLAN) access technology, and wherein the second radio access technology is a Long Term Evolution (LTE) access technology.
The method of any of Embodiments 1-19 wherein the list of wireless access point identifications comprises a list of Basic Service Set Identifiers (BSSIDs), wherein each basic Service Set Identifier corresponds to a respective one of the plurality of wireless access points (1201) connected to the termination node.
The method of any of Embodiments 1-20 wherein the interface setup request is an Xw interface setup request, and wherein transmitting the subset of the wireless access point identifications comprises transmitting an Xw interface setup response message including the subset of the wireless access point identifications.
The method of any of Embodiments 1-21 further comprising:
The method of Embodiment 22 wherein the interface comprises an Xw interface.
The method of any of Embodiments 1-23 wherein the termination node (1001) comprises an access point controller.
The method of any of Embodiments 1-24 wherein the wireless communication network including the communication node (1101a) is a first wireless communication network, and wherein a second wireless communication network includes the plurality of wireless access points (1201) connected to the termination node (1001).
A termination node (1001) for use in connection with a plurality of wireless access points (1201), wherein the termination node (1001) is adapted to perform according to any of Embodiments 1-25.
A termination node (1001) for use in connection with a plurality of wireless access points (1201), the termination node (1001) comprising:
A method of operating a communication node (1101a) of a wireless communication network, the method comprising:
The method of Embodiment 28 wherein the interface setup request includes information relating to the communication node (1101a).
The method of any of Embodiments 28-29 wherein the information relating to the communication node (1101a) includes an identification of the communication node (1101a).
The method of Embodiment 30, wherein the identification of the communication node (1101a) comprises a global eNB identification.
The method of Embodiment 30, wherein the identification of the communication node (1101a) comprises a cell identification.
The method of Embodiment 32, wherein the cell identification comprises a E-UTRAN cell global identifier.
The method of any of Embodiments 29-33 wherein the information relating to the communication node (1101a) includes a list of neighbor cell identifications for cells of another node (1101b) of the wireless communication network neighboring the communication node (1101a).
The method of any of Embodiments 29-44 wherein the information relating to the communication node (1101a) includes position information for the communication node (1101a).
The method of Embodiment 35 where the information relating to the communication node (1101a) includes information for a maximum distance of interest from the communication node (1101a).
The method of any of Embodiments 29-36 wherein the information relating to the communication node (1101a) includes an identifications of a plurality of cells of the communication node (1101a).
The method of Embodiment 37 wherein the identifications of the plurality of cells comprise E-UTRAN Cell Global Identifiers.
The method of any of Embodiments 29-38 wherein the information relating to the communication node (1101a) includes a tracking area code for the communication node (1101a).
The method of any of Embodiments 29-39 wherein the subset of the plurality of wireless access points includes wireless access points that are relevant with respect to the communication node (1101a) based on the information relating to the communication node (1101a) included in the setup request.
The method of any of Embodiments 28-40 wherein the interface setup request includes a list filtering information element having a first value, the method further including:
The method of any of Embodiments 28-41 further comprising:
The method of any of Embodiments 28-41 further comprising:
The method of any of Embodiments 28-43 wherein the interface setup request includes a maximum desired periodicity for termination node updates.
The method of any of Embodiments 28-44 wherein the communication node (1101a) of the wireless communication network comprises a base station that provides wireless communications in accordance with a first radio access technology, and wherein the plurality of wireless access points (1201) provide wireless communications in accordance with a second radio access technology, different than the first radio access technology.
The method of Embodiment 45, wherein the first radio access technology is a Long Term Evolution (LTE) access technology, and wherein the second radio access technology is a Wireless Local Area Network (WLAN) access technology.
The method of any of Embodiments 28-46 wherein the wireless access point identifications comprises a Basic Service Set Identifiers (BSSIDs), wherein each basic Service Set Identifier corresponds to a respective one of the subset of wireless access points (1201) connected to the termination node.
The method of any of Embodiments 28-47 wherein the interface setup request is an Xw interface setup request, and wherein the interface setup response is an Xw interface setup response.
The method of Embodiment 48 wherein the interface comprises an Xw interface.
The method of any of Embodiments 28-49, wherein the termination node (1001) comprises an access point controller.
The method of any of Embodiments 28-50 further comprising:
The method of Embodiment 51 further comprising:
The method of any of Embodiments 28-52, wherein transmitting downlink data over the interface for downlink transmission to the wireless terminal (1301) comprises transmitting the downlink data over the interface while the wireless terminal (1301) is in an RRC_Connected state with respect to the communication node (1101a).
A communication node (1101a) of a wireless communication network, wherein the communication node (1101a) is adapted to perform according to any of Embodiments 28-53.
A communication node (1101a) of a wireless communication network, the communication node (1101a) comprising:
A termination node for use in connection with a plurality of wireless access points, the termination node comprising:
A termination node for use in connection with a plurality of wireless access points, wherein the termination node is adapted to:
A termination node for use in connection with a plurality of wireless access points, the termination node comprising:
A communication node of a wireless communication network, the communication node comprising:
A communication node of a wireless communication network, wherein the communication node is adapted to:
A communication node of a wireless communication network, the communication node comprising:
3GPP 3rd Generation Partnership Project
AC WLAN AP Controller
ANR Autonomous Network Relation setup
AP WLAN Access Point
BSSID Basic Service Set IDentifier
CP Control Plane
ECGI E-UTRAN Cell Global Identifier
eNB Evolved Node B
E-UTRAN Evolved Universal Terrestrial Radio Access Network
GPS Global Positioning System
IE Information Element
IP Internet Protocol
MAC Media Access Control
MME Mobility Management Entity
LTE Long Term Evolution
LWA LTE-WLAN Aggregation
OAM Operations and Maintenance
PDCP Packet Data Convergence Protocol
PDU Packet Data Unit
PHY Physical Layer
RLC Radio Link Control
RRC Radio Resource Control
RRU Remote Radio Unit
SCTP Stream Control Transport Protocol
TAC Tracking Area Code
UE User Equipment
UP User Plane
X2AP X2 Application Protocol
XwAP Xw Application Protocol
WLANWireless Local Area Network
WT WLAN Termination
In the above-description of various embodiments of present inventive concepts, it is to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of present inventive concepts. Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which present inventive concepts belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.
When an element is referred to as being “connected”, “coupled”, “responsive”, or variants thereof to another element, it can be directly connected, coupled, or responsive to the other element or intervening elements may be present. In contrast, when an element is referred to as being “directly connected”, “directly coupled”, “directly responsive”, or variants thereof to another element, there are no intervening elements present. Like numbers refer to like elements throughout. Furthermore, “coupled”, “connected”, “responsive”, or variants thereof as used herein may include wirelessly coupled, connected, or responsive. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. Well-known functions or constructions may not be described in detail for brevity and/or clarity. The term “and/or” includes any and all combinations of one or more of the associated listed items.
It will be understood that although the terms first, second, third, etc. may be used herein to describe various elements/operations, these elements/operations should not be limited by these terms. These terms are only used to distinguish one element/operation from another element/operation. Thus a first element/operation in some embodiments could be termed a second element/operation in other embodiments without departing from the teachings of present inventive concepts. The same reference numerals or the same reference designators denote the same or similar elements throughout the specification.
As used herein, the terms “comprise”, “comprising”, “comprises”, “include”, “including”, “includes”, “have”, “has”, “having”, or variants thereof are open-ended, and include one or more stated features, integers, elements, steps, components or functions but does not preclude the presence or addition of one or more other features, integers, elements, steps, components, functions or groups thereof. Furthermore, as used herein, the common abbreviation “e.g.”, which derives from the Latin phrase “exempli gratia,” may be used to introduce or specify a general example or examples of a previously mentioned item, and is not intended to be limiting of such item. The common abbreviation “i.e.”, which derives from the Latin phrase “id est,” may be used to specify a particular item from a more general recitation.
Example embodiments are described herein with reference to block diagrams and/or flowchart illustrations of computer-implemented methods, apparatus (systems and/or devices) and/or computer program products. It is understood that a block of the block diagrams and/or flowchart illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, can be implemented by computer program instructions that are performed by one or more computer circuits. These computer program instructions may be provided to a processor circuit of a general purpose computer circuit, special purpose computer circuit, and/or other programmable data processing circuit to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, transform and control transistors, values stored in memory locations, and other hardware components within such circuitry to implement the functions/acts specified in the block diagrams and/or flowchart block or blocks, and thereby create means (functionality) and/or structure for implementing the functions/acts specified in the block diagrams and/or flowchart block(s).
These computer program instructions may also be stored in a tangible computer-readable medium that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable medium produce an article of manufacture including instructions which implement the functions/acts specified in the block diagrams and/or flowchart block or blocks. Accordingly, embodiments of present inventive concepts may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.) that runs on a processor such as a digital signal processor, which may collectively be referred to as “circuitry,” “a module” or variants thereof.
It should also be noted that in some alternate implementations, the functions/acts noted in the blocks may occur out of the order noted in the flowcharts. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved. Moreover, the functionality of a given block of the flowcharts and/or block diagrams may be separated into multiple blocks and/or the functionality of two or more blocks of the flowcharts and/or block diagrams may be at least partially integrated. Finally, other blocks may be added/inserted between the blocks that are illustrated, and/or blocks/operations may be omitted without departing from the scope of inventive concepts. Moreover, although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.
Many variations and modifications can be made to the embodiments without substantially departing from the principles of the present inventive concepts. All such variations and modifications are intended to be included herein within the scope of present inventive concepts. Accordingly, the above disclosed subject matter is to be considered illustrative, and not restrictive, and the examples of embodiments are intended to cover all such modifications, enhancements, and other embodiments, which fall within the spirit and scope of present inventive concepts. Thus, to the maximum extent allowed by law, the scope of present inventive concepts are to be determined by the broadest permissible interpretation of the present disclosure including the examples of embodiments and their equivalents, and shall not be restricted or limited by the foregoing detailed description.
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2016/050513 | 6/1/2016 | WO | 00 |
| Number | Date | Country | |
|---|---|---|---|
| 62205371 | Aug 2015 | US |
