WO2018118973A1 - Amélioration d'une agrégation de réseau local sans fil d'évolution à long terme pour une utilisation domestique et en entreprise - Google Patents

Amélioration d'une agrégation de réseau local sans fil d'évolution à long terme pour une utilisation domestique et en entreprise Download PDF

Info

Publication number
WO2018118973A1
WO2018118973A1 PCT/US2017/067390 US2017067390W WO2018118973A1 WO 2018118973 A1 WO2018118973 A1 WO 2018118973A1 US 2017067390 W US2017067390 W US 2017067390W WO 2018118973 A1 WO2018118973 A1 WO 2018118973A1
Authority
WO
WIPO (PCT)
Prior art keywords
wlan
enb
lwa
message
addition
Prior art date
Application number
PCT/US2017/067390
Other languages
English (en)
Inventor
Shadi Iskander
Jerome Parron
Ehud Reshef
Alexander Sirotkin
Umesh PHUYAL
Candy YIU
Karim E. MORSY
Ofer Hareuveni
Nageen Himayat
Victoria MORILLO-VELARDE
Martin Kolde
Original Assignee
Intel IP Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Intel IP Corporation filed Critical Intel IP Corporation
Publication of WO2018118973A1 publication Critical patent/WO2018118973A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H04W12/086—Access security using security domains
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/16—Performing reselection for specific purposes
    • H04W36/22—Performing reselection for specific purposes for handling the traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • 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

Definitions

  • LTE Long-Term Evolution
  • WLAN Wireless Local Area Network
  • eNB evolved NodeB
  • the device on the WLAN side referred to as the WLAN termination (WT)
  • WT The device on the WLAN side
  • the corporate information technology (IT) department may prefer to prioritize the usage of WLAN over LTE, and control when, which user equipment (UE) devices, and what kinds of traffic are offloaded to LTE access.
  • UE user equipment
  • Such enhancements to LWA implementation may be useful for cellular network operators to control load balancing of traffic between LTE access and WLAN access.
  • Another objective is to facilitate deployment of LWA with home WLAN access points (APs) which may be owned and/or controlled by a network operator.
  • APs home WLAN access points
  • Such a use case may be supported by standalone WT that is not integrated with the access point (AP) and/or access controller (AP) deployed at an aggregation point.
  • AP access point
  • AP access controller
  • One limitation of the current LWA architecture is that it requires the WLAN AP/AC and the WT to reside on the same data link layer, Layer 2 (L2), network, for example the same Ethernet network which may not always be the case.
  • L2 Layer 2
  • FIG. 1 is a diagram of a network architecture for Long-Term Evolution Wireless Local Area Network Aggregation for enterprise use in accordance with one or more embodiments;
  • FIG. 2 is a diagram of an end-to-end protocol architecture to implement
  • FIG. 3 is a flow diagram illustrating the exchange of user equipment (UE) and WLAN Termination (WT) Internet Protocol (IP) addresses via radio resource control signaling in accordance with one or more embodiments;
  • UE user equipment
  • WT WLAN Termination
  • IP Internet Protocol
  • FIG. 4 is a diagram illustrating examples of LWA protocol data unit (PDU) formats to be exchanged between the WT and the UE in accordance with one or more embodiments;
  • PDU protocol data unit
  • FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments
  • FIG. 6 illustrates example components of a device in accordance with some embodiments.
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • FIG. 1 a diagram of a network architecture for Long-Term Evolution Wireless Local Area Network Aggregation for enterprise use in accordance with one or more embodiments will be discussed.
  • network 100 may be deployed in or proximate to an enterprise environment at least in part.
  • a user equipment (UE) 110 may be operated by a user in the enterprise environment to access network 110 wherein UE 110 may access network 100 over a wireless local area network (WLAN) 104 via WLAN termination (WT) 112 which also may include an access controller.
  • WLAN wireless local area network
  • WT WLAN termination
  • UE 110 may access network 100 over a Long-Term Evolution (LTE) network 102 operating in accordance with a Third Generation Partnership Project (3 GPP) standard via evolved NodeB (eNB) 114.
  • LTE Long-Term Evolution
  • 3 GPP Third Generation Partnership Project
  • eNB 114 and WT 112 may be coupled via an Xw interface 116, and eNB 114 may be coupled to a serving gateway (S-GW) 120 via an SI interface 118.
  • S-GW 120 is in turn coupled to a packet data network (PDN) gateway (P-GW) 122 to allow network 100 to communicate with the outside world.
  • PDN packet data network gateway
  • offload of traffic for UE 110 to WLAN 104 and/or from WLAN 104 is fully controlled by eNB 114.
  • the WT 112 at the WLAN 104 may accept or reject the offload.
  • the enterprise may prioritize the usage of WLAN 104 over the usage of LTE 102.
  • the enterprise may control when, which UEs 110, and/or what kinds of traffic are offloaded to LTE 102 from WLAN 104.
  • Such control may be provided by network 100 using signaling mechanisms between WT 112 and eNB 114 via the Xw interface, or between UE 110 and eNB 114 via a Uu interface, or a combination thereof.
  • signaling mechanisms between WT 112 and eNB 114 via the Xw interface, or between UE 110 and eNB 114 via a Uu interface, or a combination thereof.
  • Such arrangements as discussed in further detail, below, allow an enterprise to offer part of its WLAN infrastructure to an LTE network operator for LWA, for example using separate service set identifiers (SSIDs) and/or homogenous extended service set (ESS) SSIDs (HESSIDs), since the enterprise has full control over its resources.
  • SSIDs separate service set identifiers
  • ESS homogenous extended service set
  • HESSIDs homogenous extended service set
  • an enterprise may be paid by an LTE network operator for providing WLAN resources to extend the operator's coverage, or an LTE network operator may be paid by an enterprise for extending LTE network coverage, for example to fill in coverage holes in a campus location, although the scope of the claimed subject matter is not limited in these respects.
  • Admission control (Accepting/Rejecting specific UEs)
  • WT 112 can reject a WT Addition message sent by eNB 114 to WT 112 via Xw interface 116.
  • This capability may be extended by defining rejection cause values so that eNB 114 can understand the reason for the WT Addition rejection.
  • rejection cause values may include an indication that UE 110 is not authorized to use this WLAN 104, that the WLAN 104 is overloaded, and so on.
  • access control may be implanted using Institute of Electrical and Electronics Engineers (IEEE) 802.1x-based authentication. A non-authorized UE 110 will not be able to connect to the enterprise WT 112.
  • eNB 114 shall not configure a security key derivation based on an eNB key (KeNB).
  • KeNB eNB key
  • WLAN Initiated LWA Wi-Fi First, or Reverse LWA
  • the WT 112 is capable of initiating LWA activation instead of the eNB 114.
  • these embodiments may be achieved in two ways.
  • a first option when the eNB 114 detects that an enterprise UE 110 enters network 100, for example at an enterprise campus where LWA is available, eNB 114 immediately may initiate LWA regardless of whether UE 110 has enough traffic to offload to WLAN 104 by using a WT Addition Xw message towards WT 112. The eNB 114 does not schedule any traffic on WLAN 104 unless eNB 114 is instructed so by the WT 112 or by UE 110.
  • WT 112 can trigger LWA activation, for example by using a WT-initiated WT Addition Xw message, when WT 112 determines it is necessary to use LWA.
  • Xw signaling over Xw interface 116 may be enhanced, for example with a WT resume/suspend indication or with an addition of a parameter in existing signaling that WT 112 is an enterprise WT.
  • the call flow of such enhanced signaling may be as follows. If a WT resume/suspend indicates is used, first eNB 114 sends a WT Addition message to WT 112 indicating that LWA is suspended. Next, WT 112 sends a WT Resume command to eNB 114, and eNB 114 starts scheduling traffic on WLAN 104. Then, WT 112 sends a WT Suspend command to eNB 114, and eNB 114 stops scheduling traffic on WLAN 104.
  • a flag is utilized to indicate that WT 112 is an enterprise WT, one UE 110 connected to an access point (AP) of WT 112, eNB 114 does not schedule data on WLAN 104. Instead, eNB 114 waits for an additional trigger from WT 112 before scheduling data on WLAN 104. Additionally, the WT 112 may indicate which traffic needs to be scheduled on LTE 102 and which traffic needs to be scheduled on WLAN 104. For option, either the eNB 114 or the WT 112 would have to perform shallow deep packet inspection (DPI) to inspect at least the Internet Protocol (IP) header of the traffic to map IP flows to bearers.
  • DPI shallow deep packet inspection
  • IP Internet Protocol
  • the WT 112 may indicate which IP flows WT 112 wants reverse-offloaded and/or onloaded from WLAN 104 to LTE 102, and the eNB 114 would map these to bearers and reconfigure LWA accordingly.
  • Either a WT Resume command can carry the indication about which flows must be onloaded, or a new Xw command may be defined for this purpose.
  • a new Xw message may be defined, for example an WT-initiated WT Addition message or a WT Addition Required message.
  • Such a message would carry a UE identifier to identify the UE 110 for which the WT 112 is requesting LWA activation.
  • a suitable UE identifier may include, for example, a cellular UE identifier used to identify UE 110 on LTE access network 102 such as Cell Radio Network Temporary Identifier (C-RNTI), an International Mobile Subscriber Identity (IMSI), an International Mobile Equipment Identity (IMEI), a Globally Unique Temporary Identity (GUTI), an Internet Protocol (IP) address assigned to UE 110 by P-GW 122, and so on, a temporary UE Xw identifier, or WLAN media access control (MAC) information of the UE 110 on WLAN 104, although the scope of the claimed subject matter is not limited in this respect.
  • C-RNTI Cell Radio Network Temporary Identifier
  • IMSI International Mobile Subscriber Identity
  • IMEI International Mobile Equipment Identity
  • GUI Globally Unique Temporary Identity
  • IP Internet Protocol
  • IP Internet Protocol
  • MAC media access control
  • WT 112 sends a WT Addition Required message with the UE WLAN MAC address and optionally IP flows to be offloaded indicators.
  • the eNB 114 initiates LWA by sending WT Addition message knowing the UE WLAN MAC address received in the UE capability exchange.
  • the first option (option A) and the second option (option B) are not mutually exclusive and may be used together, and the scope of the claimed subject matter is not limited in this respect.
  • the eNB 114 may still track and record traffic sent on this special bearer.
  • the establishment of the special bearer occurs with cooperation of the mobility management entity (MME), but no EPC bearers are setup and tracked.
  • MME mobility management entity
  • the eNB 114 uses the default bearer for routing traffic but makes sure that traffic is not routed to the EPC.
  • the eNB 114 ensures that the UE 110 stays in connected mode even when no data is sent over the EPC.
  • the WT 112 has the radio resource management intelligence to make decisions on when to route WLAN traffic to LTE network 102 opportunistically.
  • the eNB 114 then may report LTE link qualities to WT 112 over the Xw interface 116. Further messages from eNB 114 to WT 112 supporting flow etc. may also be added on the Xw interface 116.
  • the WT 112 may not need to perform any special user plane modifications to route packets to eNB 114, beyond the shallow DPI indicated above.
  • Fast switching or aggregation will require the WT 112 to support an adaptation layer, for example the packet data convergence protocol (PDCP) adaptation layer, which will allow for tracking of IP packets on the WT side.
  • PDCP packet data convergence protocol
  • the WT 112 provides to the eNB 114 certain policies that eNB 114 should use when activating LWA and scheduling traffic on LTE network 102 and WLAN 104, for example via a WT configuration update message, in an Xw Setup Response message, or in a new message defined specifically for this purpose.
  • policies may include UE 110 identifiers for which WLAN 104 is the preferred access technology, or quality of service (QoS) characteristics of bearers for which WLAN104 is the preferred technology.
  • QoS quality of service
  • the WT 112 may assign different services or quality of service (QoS) to one or more UEs 110.
  • QoS quality of service
  • Example of such services may include the following.
  • WT 112 of WLAN 104 recommends offloading a UE 110 and/or dedicated radio bearer (DRB) completely to WLAN/LTE instead of split.
  • DRB dedicated radio bearer
  • WT 112 of WLAN 104 recommends the split ratio for a specific UE 110.
  • WT 112 of WLAN 104 recommends switching the bands being used, for example WT 112 may force the UE 110 to use a 60 GHz.
  • at least some of the following information should be shared via Xw signaling over Xw interface 116.
  • shared information may include measurement configurations for the UEs 110, a list of UEs 110 to be offloaded completely to WLAN 104 or LTE network 102, MobilitySet modifications such as bands or channels, and so on, split ratio information per UE 110, inquiry of data rates per UE 110, and/or data rates per UE/DRB at WLAN 104.
  • shared information may include WLAN measurement results done by the UEs 110 that were requested by the WT 112 and/or WLAN 104, approximate data rates to be delivered to specific UEs 110, and/or QoS of offloaded bearers for each UE 110.
  • an enterprise may try to fill in gaps due to bad WLAN 104 coverages with LTE 102.
  • the WT 112 and/or WLAN 104 detects that a UE 110 is approaching a low coverage area, for example based on the measurements received from UE 110 either directly via IEEE 802.11 with WT 112 or via eNB 114, the WT 112 may request the eNB 114 to offload this UE 110 to LTE network 102, or at least modify the split ratio. Then, once UE 110 is back in a good coverage area for WLAN 104, WT 112 may restore the previous configuration. Such an arrangement also may help in mobility scenarios across multiple WTs 112 or within the same WT 112. Another example of this embodiment is where WIT 112 of WLAN 104 provides user profiles to certain UEs 110. The WT 112 then may prioritize those UEs 110 by providing more bandwidth, better QoS, and so on.
  • Closed Subscriber Groups may be provided wherein access to one or more WTs 112 may be limited to UEs 110 that are subscribers to a closed subscriber group.
  • the WT 112 of WLAN 104 may configure UE 110 identifiers (IDs) for the subscribers, and those IDs may be the same IDs used for an LTE CSG, or the UE MAC Address, or any new defined identifiers.
  • IDs UE 110 identifiers
  • the UE 110 would share this ID while activating LWA
  • the eNB 114 would share this ID with the WT 112 while activating, and the WT 112 may decide to accept and/or reject the configuration based on the UE ID and associated Subscriber Groups.
  • a UE 110 could inform the eNB 114 that it is in an Enterprise Mode via a capability message, or via new signaling.
  • Enterprise Mode may be provisioned in the UE 110 for the enterprise access point (AP) so that the UE 110 can detect when entering an enterprise network 100 and notify the network accordingly to the eNB 114.
  • the eNB 114 may prefer WLAN 104 access for LWA.
  • the UE 110 may prefer WLAN 104 access for transmitting UL data.
  • the WT 112 then has the capability to control users, offload, or split them based on the above.
  • the WT 112 can notify the UE 110 to change the split ration between LTE 102 access and WLAN 104 access, for example using the LWA Adaption Protocol (LWAAP) extension.
  • LWAAP LWA Adaption Protocol
  • the UE 110 switches normally to LTE.
  • the eNB gets notified 104, for example by the UE 110, and the eNB 114 then activates LWA again, even if no measurements were configured for LWA.
  • One option to implement Enterprise Mode may be via the Suspend/Resume mechanism wherein the UE 110 suspends WLAN 104 access if the UE 110 detects bad coverage, and then resumes WLAN 104 access again when UE 110 is back in good coverage.
  • This option may be implemented only in Enterprise Mode, or always, and then the eNB 114 decides to keep or release the connection, since the eNB is also aware of the Enterprise Mode.
  • a network layer, Layer 3 (L3), transport mechanism may be provided to send LWA packets over WLAN 104 between the WT 112 and the UE 110 for the ease of deployment of LWA with a home wireless local area network (WLAN) access point (AP),
  • WLAN wireless local area network
  • Such a transport mechanism may comprise a tunnel 212 established between the WT 112 and the UE 110 to transfer the LWA packets.
  • the tunnel 212 preferably may not be encrypted and may be based on Generic Routing Encapsulation (GRE) which requires involves modifications in the LWA architecture 200 as shown in FIG. 2.
  • GRE Generic Routing Encapsulation
  • the WT 112 and the UE 110 support GRE tunneling.
  • the LWA packets are encapsulated over the GRE tunnel 212 and transferred over Internet Protocol (IP).
  • IP Internet Protocol
  • the tunnel 212 may terminate in the transmission control protocol (TCP)/Internet Protocol (TCP/IP) stack of the application operating system (OS), wherein the LWA packets are to be forwarded to the LTE modem of the UE 110 for deciphering and/or reordering.
  • TCP transmission control protocol
  • IP/IP Internet Protocol
  • OS application operating system
  • the UE 110 may include a Packet Data Convergence Protocol (PDCP) module 214, LTE-WLAN Aggregation Adaptation Protocol (LWAAP) module 216, Generic Routing Encapsulation (GRE) module 218, and Internet Protocol (IP) module 220.
  • WLAN AP 210 may include IP modules 220 to facilitate the tunnel 212.
  • the WT 112 may include LWAAP modules 216, a GRE module 218, IP modules 220, and a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) module 222.
  • the eNB 114 may include a PDCP module 214, a LWAAP module 216, a GRP module 222, and an IP module 220.
  • the UE 110 may acquire an IP address on the WLAN 104, and then communicates this IP address to the eNB 114.
  • the eNB 114 then communicates the IP address of the WT 112 to the UE 110, and a GRE tunnel 212 is established between the WT 112 to carry LWA packets over the WLAN 104.
  • the IP address of the WT 112 may be communicated from the WT 112 to the eNB 114 using Xw signaling via the Xw interface 116.
  • a L3 transport mechanism such as GRE tunnel 212, between the WT 112 and the UE 110, allows LWA deployment with little or no WLAN infrastructure impact.
  • use of a GRE tunnel 212 allows utilization of APs 210 existing in the WLAN infrastructure, in particular APs deployed in the home where network operators may not have the ability to modify such home APs. Such an arrangement may simplify the LWA deployment in the home.
  • L3 transport mechanism such as GRE tunnel 212
  • GRE tunnel 212 Another advantage of using a L3 transport mechanism, such as GRE tunnel 212, is the alignment of the protocol architecture with the Lightweight IP (LWIP) feature.
  • LWIP Lightweight IP
  • Using a GRE tunnel 212 also may simplify the implementation of LWA in discrete modems where no WLAN chipset is integrated, as the packets arrive directly to the TCP/IP stack of the application processor and easily may be redirected to the LTE modem, although the scope of the claimed subject matter is not limited in this respect.
  • UE 110 may perform a radio resource control (RRC) connection establishment with eNB 114 at operation 310.
  • RRC radio resource control
  • the UE 110 may perform WLAN measurement configuration at operation 312, and provide WLAN measurement reporting to eNB 114 at operation 314.
  • the WT 112 may be added y eNB 114 for LWA at WT addition operation 316.
  • a RRC connection reconfiguration operation 318 may be performed between UE 110 and eNB 114 including LWA bearer addition.
  • UE 110 may then perform a WLAN association operation 320 with AP 210, and the UE 110 may acquire an IP address from AP 210 at IP address acquisition operation 322.
  • a GRE tunnel 212 can be setup.
  • the UE 110 provides its IP address on WLAN 104 to the eNB 114 via WLAN connection status report operation 324 wherein the report includes the IP address of the UE 110.
  • the eNB 114 notifies the WT 112 of the IP address of the UE 110 via UE IP address notification operation 326.
  • the eNB 114 also provides the WT IP address to the UE 110 via an RRC connection reconfiguration operation 328 which includes a WLAN- MobilityConfiguration information element (IE) that includes the IP address of the WT 112.
  • the GRE may then be established between UE 110 and WT 112 at GRE tunnel establishment operation 330. Once established, LWA packets between the WT 112 and the UE 110 are exchanged over the GRE tunnel 212.
  • IE WLAN- MobilityConfiguration information element
  • the exchange of the IP addresses of the UE 110 UE and the WT 112 between the UE 110 and the eNB 114 may be done via RRC signaling wherein existing RRC messages may be reused to provide this information.
  • first the UE 110 acquires an IP address on WLAN 104, and communicates the IP address to the eNB 114.
  • the existing WLAN connection status report may be extended to provide UE IP address as shown below.
  • IP-Address-rXX IP-Address-rl3 OPTIONAL IP-Address-rl3 OPTIONAL, nonCriticalExtension SEQUENCE ⁇ ⁇ OPTIONAL
  • the eNB 114 communicates the IP address of the WT 112 to the UE 110, which may be provided by using a relXX extension to WLAN-MobilityConfig- rl3 IE as shown below.
  • WLAN-MobilityConfig-rl3 :: SEQUENCE ⁇
  • LWA packet 410 may comprise an Internet Protocol (IP) header 412, Generic Routing Encapsulation (GRE) header 414, LWA Adaption Protocol (LWAAP) header 416, the packet data convergence protocol (PDCP) header 418, and an IP packet 420.
  • IP Internet Protocol
  • GRE Generic Routing Encapsulation
  • LWAAP LWA Adaption Protocol
  • PDCP packet data convergence protocol
  • PDU 410 may include the legacy LWAAP header 416 with the dedicated radio bearer (DRB) identifier (ID) which may provide less impact on existing implementations.
  • LWA packet 422 may have the LWAAP header 418 removed, and the DRB ID instead may be included in GRE header 414 in a manner similar to Lightweight IP (LWIP).
  • LWIP Lightweight IP
  • the LWA packets may be exchanged between the eNB 114 and the UE 110 in the downlink.
  • the eNB 114 sends LWA packets over GPRS Tunneling Protocol (GTP) to the WT 112.
  • GTP GPRS Tunneling Protocol
  • the WT 112 extracts the LWAAP packet and encapsulates the LWAAP or the PDCP PDU, depending on the selected option, using the GRE protocol and sends the packets to the IP address of the UE 110.
  • the AP 210 delivers the IP packet to the UE 110, and the IP packet is decapsulated by the UE 110 and delivered to the GRE stack.
  • the GRE stack then delivers the LWAAP or PDCP PDU, depending on the selected option, to the LWAAP entity or PDCP entity for deciphering and/or reordering.
  • the UE 110 In the uplink direction, the UE 110 encapsulates the LWAAP or the PDCP PDU, depending on the selected option, using the GRE protocol and sens it to the IP address of the WT 112.
  • the AP 210 delivers the IP packet to the WT 112, and the WT 112 decapsulates the received packet, extracts the LWAAP or the PDCP PDU, depending on the selected option, and sends it over GTP protocol to the eNB 114.
  • the eNB 114 knows the outer WT IP address, which may be provided via operations, administration, and maintenance (OAM).
  • OAM operations, administration, and maintenance
  • Xw signaling is enhanced for the WT 112 to communicate the outer IP address of the WT 112 to the eNB 114.
  • a WT Configuration Update message or an Xw Setup Response Xw message may be used for this purpose with appropriate extensions.
  • the GRE tunnel 212 may be established between the UE 110 and the eNB 114 directly.
  • the WT 112 functionality may be integrated in the eNB 114, but it is also possible to keep the eNB 114 and the WT 112 as different nodes, and establish a GRE tunnel 212 to the UE 114 and use IP transport between the eNB 114 and the WT 112 instead of the GTP protocol.
  • the UE 110 should know the IP address of the eNB 114 to send the data, therefore the IP address of the eNB 114 be provided by the eNB 114 to the WT 112 in a similar manner described herein, above, via RRC signaling.
  • FIG. 5 illustrates an architecture of a system of a network in accordance with some embodiments.
  • the system 500 is shown to include a user equipment (UE) 501 and a UE 502.
  • the UEs 501 and 502 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.
  • PDAs Personal Data Assistants
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • any of the UEs 501 and 502 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections.
  • An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.
  • the UEs 501 and 502 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 510—
  • the RAN 510 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Evolved Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Mobile Telecommunications System
  • NG RAN NextGen RAN
  • the UEs 501 and 502 utilize connections 503 and 504, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 503 and 504 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push- to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push- to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth generation
  • NR New Radio
  • the UEs 501 and 502 may further directly exchange communication data via a ProSe interface 505.
  • the ProSe interface 505 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 502 is shown to be configured to access an access point (AP) 506 via connection 507.
  • the connection 507 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 506 would comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 506 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 510 can include one or more access nodes that enable the connections 503 and 504. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • BSs base stations
  • eNBs evolved NodeBs
  • gNB next Generation NodeBs
  • RAN nodes and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the RAN 510 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 511, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 512.
  • macro RAN node 511 e.g., macro RAN node 511
  • femtocells or picocells e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells
  • LP low power
  • any of the RAN nodes 511 and 512 can terminate the air interface protocol and can be the first point of contact for the UEs 501 and 502.
  • any of the RAN nodes 511 and 512 can fulfill various logical functions for the RAN 510 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.
  • RNC radio network controller
  • the UEs 501 and 502 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 511 and 512 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency- Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect.
  • OFDM signals can comprise a plurality of orthogonal subcarriers.
  • a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 511 and 512 to the UEs 501 and 502, while uplink transmissions can utilize similar techniques.
  • the grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot.
  • a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation.
  • Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively.
  • the duration of the resource grid in the time domain corresponds to one slot in a radio frame.
  • the smallest time- frequency unit in a resource grid is denoted as a resource element.
  • Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements.
  • Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated.
  • the physical downlink shared channel may carry user data and higher-layer signaling to the UEs 501 and 502.
  • the physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 501 and 502 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel.
  • downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 511 and 512 based on channel quality information fed back from any of the UEs 501 and 502.
  • the downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 501 and 502.
  • the PDCCH may use control channel elements (CCEs) to convey the control information.
  • CCEs control channel elements
  • the PDCCH complex- valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching.
  • Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs).
  • RAGs resource element groups
  • QPSK Quadrature Phase Shift Keying
  • the PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition.
  • DCI downlink control information
  • There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L l, 2, 4, or 8).
  • Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts.
  • some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission.
  • the EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.
  • EPCCH enhanced physical downlink control channel
  • ECCEs enhanced the control channel elements
  • each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs).
  • EREGs enhanced resource element groups
  • An ECCE may have other numbers of EREGs in some situations.
  • the RAN 510 is shown to be communicatively coupled to a core network (CN) 520— via an SI interface 513.
  • the CN 520 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN.
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the S 1 interface 513 is split into two parts : the S 1 -U interface 514, which carries traffic data between the RAN nodes 511 and 512 and the serving gateway (S-GW) 522, and the Sl-mobility management entity (MME) interface 515, which is a signaling interface between the RAN nodes 511 and 512 and MMEs 521.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 520 comprises the MMEs 521, the S-GW 522, the Packet Data Network (PDN) Gateway (P-GW) 523, and a home subscriber server (HSS) 524.
  • the MMEs 521 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 521 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 524 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 520 may comprise one or several HSSs 524, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 524 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • the S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • the S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • the S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • the S-GW 522 may terminate the SI interface 513 towards the RAN 510, and routes data packets between the RAN 510 and the CN 520.
  • 522 may be a local mobility anchor point for inter- RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 523 may terminate an SGi interface toward a PDN.
  • the P-GW 523 may terminate an SGi interface toward a PDN.
  • the EPC network 523 may route data packets between the EPC network 523 and external networks such as a network including the application server 530 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 525.
  • the application server 530 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS Packet Services
  • LTE PS data services etc.
  • the P-GW 523 is shown to be communicatively coupled to an application server 530 via an IP communications interface 525.
  • the application server 530 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 501 and 502 via the CN 520.
  • VoIP Voice-over-Internet Protocol
  • PTT sessions PTT sessions
  • group communication sessions social networking services, etc.
  • the P-GW 523 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Enforcement Function (PCRF) 526 is the policy and charging control element of the CN 520.
  • PCRF Policy and Charging Enforcement Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • HPLMN Home Public Land Mobile Network
  • V- PCRF Visited PCRF
  • VPLMN Visited Public Land Mobile Network
  • the PCRF 526 may be communicatively coupled to the application server 530 via the P-GW 523.
  • the application server 530 may signal the PCRF 526 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters.
  • the PCRF 526 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 530.
  • PCEF Policy and Charging Enforcement Function
  • TFT traffic flow template
  • QCI QoS class of identifier
  • FIG. 6 illustrates example components of a device 600 in accordance with some embodiments.
  • Device 600 may realize any one or more of the devices or network elements as shown in any of the figures described herein, with more of fewer components, although the scope of the claimed subject matter is not limited in these respects.
  • the device 600 may include application circuitry 602, baseband circuitry 604, Radio Frequency (RF) circuitry 606, front-end module (FEM) circuitry 608, one or more antennas 610, and power management circuitry (PMC) 612 coupled together at least as shown.
  • RF Radio Frequency
  • FEM front-end module
  • PMC power management circuitry
  • the components of the illustrated device 600 may be included in a UE or a RAN node.
  • the device 600 may include less elements (e.g., a RAN node may not utilize application circuitry 602, and instead include a processor/controller to process IP data received from an EPC).
  • the device 600 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/ output)I/0( interface.
  • the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).
  • the application circuitry 602 may include one or more application processors.
  • the application circuitry 602 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.).
  • the processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 600.
  • processors of application circuitry 602 may process IP data packets received from an EPC.
  • the baseband circuitry 604 may include circuitry such as, but not limited to, one or more single-core or multi-core processors.
  • the baseband circuitry 604 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry606 and to generate baseband signals for a transmit signal path of the RF circuitry606.
  • Baseband circuitry 604 may interface with the application circuitry 602 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 606.
  • the baseband circuitry 604 may include a third generation (3G) baseband processor 604A, a fourth generation (4G) baseband processor 604B, a fifth generation (5G) baseband processor 604C, or other baseband processor(s) 604D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.).
  • the baseband circuitry 604 e.g., one or more of baseband processors 604 A-D
  • baseband processors 604A-D may be included in modules stored in the memory 604G and executed via a Central Processing Unit (CPU) 604E.
  • the radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc.
  • modulation/ demodulation circuitry of the baseband circuitry604 may include Fast- Fourier Transform)FFT( , precoding ,or constellation mapping/demapping functionality.
  • encoding/decoding circuitry of the baseband circuitry 604 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality.
  • LDPC Low Density Parity Check
  • the baseband circuitry 604 may include one or more audio digital signal processor(s) (DSP) 604F.
  • the audio DSP(s) 604F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments.
  • Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments.
  • some or all of the constituent components of the baseband circuitry604 and the application circuitry602 may be implemented together such as, for example, on a system on a chip (SOC).
  • SOC system on a chip
  • the baseband circuitry 604 may provide for communication compatible with one or more radio technologies.
  • the baseband circuitry 604 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN).
  • EUTRAN evolved universal terrestrial radio access network
  • WMAN wireless metropolitan area networks
  • WLAN wireless local area network
  • WPAN wireless personal area network
  • multi-mode baseband circuitry Embodiments in which the baseband circuitry 604 is configured to support radio communications of more than one wireless protocol.
  • RF circuitry 606 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium.
  • the RF circuitry606 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network.
  • RF circuitry 606 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 608 and provide baseband signals to the baseband circuitry 604.
  • RF circuitry 606 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 604 and provide RF output signals to the FEM circuitry 608 for transmission.
  • the receive signal path of the RF circuitry 606 may include mixer circuitry 606a, amplifier circuitry 606b and filter circuitry 606c.
  • the transmit signal path of the RF circuitry 606 may include filter circuitry 606c and mixer circuitry 606a.
  • RF circuitry 606 may also include synthesizer circuitry 606d for synthesizing a frequency for use by the mixer circuitry 606a of the receive signal path and the transmit signal path.
  • the mixer circuitry 606a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 608 based on the synthesized frequency provided by synthesizer circuitry 606d.
  • the amplifier circuitry 606b may be configured to amplify the down-converted signals and the filter circuitry 606c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down- converted signals to generate output baseband signals.
  • Output baseband signals may be provided to the baseband circuitry 604 for further processing.
  • the output baseband signals may be zero-frequency baseband signals, although this is not a requirement.
  • mixer circuitry 606a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.
  • the mixer circuitry 606a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 606d to generate RF output signals for the FEM circuitry 608.
  • the baseband signals may be provided by the baseband circuitry 604 and may be filtered by filter circuitry 606c.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection).
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a may be arranged for direct downconversion and direct upconversion, respectively.
  • the mixer circuitry 606a of the receive signal path and the mixer circuitry 606a of the transmit signal path may be configured for super-heterodyne operation.
  • the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect.
  • the output baseband signals and the input baseband signals may be digital baseband signals.
  • the RF circuitry 606 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 604 may include a digital baseband interface to communicate with the RF circuitry 606.
  • ADC analog-to-digital converter
  • DAC digital-to-analog converter
  • a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.
  • the synthesizer circuitry 606d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable.
  • synthesizer circuitry 606d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.
  • the synthesizer circuitry 606d may be configured to synthesize an output frequency for use by the mixer circuitry 606a of the RF circuitry 606 based on a frequency input and a divider control input.
  • the synthesizer circuitry 606d may be a fractional N/N+l synthesizer.
  • frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement.
  • VCO voltage controlled oscillator
  • Divider control input may be provided by either the baseband circuitry 604 or the applications processor 602 depending on the desired output frequency.
  • a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 602.
  • Synthesizer circuitry 606d of the RF circuitry 606 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator.
  • the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA).
  • the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio.
  • the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop.
  • the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line.
  • Nd is the number of delay elements in the delay line.
  • synthesizer circuitry 606d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other.
  • the output frequency may be a LO frequency (fLO).
  • the RF circuitry 606 may include an IQ/polar converter.
  • FEM circuitry 608 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 610, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 606 for further processing.
  • FEM circuitry 608 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 606 for transmission by one or more of the one or more antennas 610.
  • the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 606, solely in the FEM 608, or in both the RF circuitry 606 and the FEM 608.
  • the FEM circuitry 608 may include a TX/RX switch to switch between transmit mode and receive mode operation.
  • the FEM circuitry may include a receive signal path and a transmit signal path.
  • the receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 606).
  • the transmit signal path of the FEM circuitry 608 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 606), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 610).
  • PA power amplifier
  • the PMC 612 may manage power provided to the baseband circuitry 604.
  • the PMC 612 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion.
  • the PMC 612 may often be included when the device 600 is capable of being powered by a battery, for example, when the device is included in a UE.
  • the PMC 612 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.
  • FIG. 6 shows the PMC 612 coupled only with the baseband circuitry 604.
  • the PMC 6 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 602, RF circuitry 606, or FEM 608.
  • the PMC 612 may control, or otherwise be part of, various power saving mechanisms of the device 600. For example, if the device 600 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 600 may power down for brief intervals of time and thus save power.
  • DRX Discontinuous Reception Mode
  • the device 600 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc.
  • the device 600 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again.
  • the device 600 may not receive data in this state, in order to receive data, it must transition back to RRC_Connected state.
  • An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.
  • Processors of the application circuitry 602 and processors of the baseband circuitry 604 may be used to execute elements of one or more instances of a protocol stack.
  • processors of the baseband circuitry 604 alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 604 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers).
  • Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below.
  • RRC radio resource control
  • Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below.
  • Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.
  • FIG. 7 illustrates example interfaces of baseband circuitry in accordance with some embodiments.
  • the baseband circuitry 604 of FIG. 6 may comprise processors 604A-604E and a memory 604G utilized by said processors.
  • Each of the processors 604A-604E may include a memory interface, 704A-704E, respectively, to send/receive data to/from the memory 604G.
  • the baseband circuitry 604 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 712 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604), an application circuitry interface 714 (e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6), an RF circuitry interface 716 (e.g., an interface to send/receive data to/from RF circuitry 606 of FIG. 6), a wireless hardware connectivity interface 718 (e.g.
  • a memory interface 712 e.g., an interface to send/receive data to/from memory external to the baseband circuitry 604
  • an application circuitry interface 714 e.g., an interface to send/receive data to/from the application circuitry 602 of FIG. 6
  • an RF circuitry interface 716 e.g., an interface to send/receive data to/from
  • NFC Near Field Communication
  • Bluetooth® components e.g., Bluetooth® Low Energy
  • Wi-Fi® components e.g., Wi-Fi® components
  • power management interface 720 e.g., an interface to send/receive power or control signals to/from the PMC 612.
  • an apparatus of an evolved NodeB comprises one or more baseband processors to encode a wireless local area network (WLAN) Termination (WT) Addition message to be sent to a WT of a WLAN for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA), and to receive a WT Addition Rejection message from the WT in response to the WT Addition message if the UE is rejected by the WT, wherein the WT Addition Rejection message includes a cause for the rejection of the UE, and a memory to store the WT Addition message or the WT Addition Rejection message, or a combination thereof.
  • WLAN wireless local area network
  • WT Termination
  • LTE Long-Term Evolution
  • LWA Long-Term Evolution
  • WT Addition Rejection message includes a cause for the rejection of the UE, and a memory to store the WT Addition message or the WT Addition Rejection message, or a combination thereof.
  • Example two may include the subject matter of example one or any of the examples described herein, wherein the cause includes an indication that the UE is not authorized for the WLAN, the WLAN is overloaded, or a combination thereof.
  • Example three may include the subject matter of example one or any of the examples described herein, wherein the WT Addition message is configured to be sent from the eNB to the WT via an Xw interface, or the WT Addition Rejection message is to be sent from the WT to the eNB via the Xw interface.
  • an apparatus of a wireless local area network (WLAN) termination comprises one or more baseband processors to process a WT Addition message received from an evolved NodeB (eNB) via an Xw interface for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA), and to generate a command to be sent to the eNB via the Xw interface to control offloading traffic for the UE to the WLAN if the WT Addition message is accepted by the WT, and a memory to store the WT Addition message or the command to the eNB, or a combination thereof.
  • eNB evolved NodeB
  • LTE Long-Term Evolution
  • LWA Long-Term Evolution
  • Example five may include the subject matter of example four or any of the examples described herein, wherein the WT Addition message includes an indication that LWA is activated or an indication that LWA is suspended.
  • Example six may include the subject matter of example four or any of the examples described herein, wherein the command to the eNB comprises a WT Resume command, a WT suspend command, an indication of traffic to be scheduled on the eNB, an indication of traffic to be scheduled on the WT, or a UE identifier for the UE, one or more services, a quality of service (QoS), or a band to be used for the UE for which WLAN access is preferred, or a combination thereof.
  • QoS quality of service
  • Example seven may include the subject matter of example four or any of the examples described herein, wherein the one or more baseband processors are to initiate LWA by generating the command to the eNB when deemed necessary, wherein a WT Addition message is received from the eNB upon the UE entering a LWA location, wherein the WT Addition message includes a group identifier for subscriber UEs authorized for WLAN access via LWA.
  • Example eight may include the subject matter of example four or any of the examples described herein, wherein the command to the eNB includes a measurement configuration for the UE, a list of one or more UEs to be offloaded to LTE access, a list of one or more UEs to be offloaded to WLAN access, Mobility Set information, split ratio information per UE, or data rate per UE or per data radio bearer, or a combination thereof.
  • Example may include the subject matter of example four or any of the examples described herein, wherein the WT Addition message received from the eNB includes WLAN measurement results for the UE, data rates to be delivered to the UE, the quality of service (QoS) of offloaded bearers for the UE, or an indication that the UE is configured for enterprise mode, or a combination thereof.
  • the WT Addition message received from the eNB includes WLAN measurement results for the UE, data rates to be delivered to the UE, the quality of service (QoS) of offloaded bearers for the UE, or an indication that the UE is configured for enterprise mode, or a combination thereof.
  • the WT Addition message received from the eNB includes WLAN measurement results for the UE, data rates to be delivered to the UE, the quality of service (QoS) of offloaded bearers for the UE, or an indication that the UE is configured for enterprise mode, or a combination thereof.
  • QoS quality of service
  • an apparatus of a user equipment comprises one or more baseband processors to encode a capability message for an evolved NodeB (eNB) to indicate to the eNB that the UE is capable of utilizing Long-Term Evolution (LTE) wireless local area network (WLAN) Aggregation (LWA), wherein the capability message includes an indication that the UE prefers WLAN access when LWA is activated, and a memory to store the capability message.
  • LTE Long-Term Evolution
  • WLAN wireless local area network
  • Example eleven may include the subject matter of example ten or any of the examples described herein, wherein capability message includes an indication that the UE is configured for enterprise mode, an indication that the UE prefers WLAN for uplink (UL) traffic, or a specific identifier (ID) for LWA, or a combination thereof.
  • Example twelve may include the subject matter of example ten or any of the examples described herein, wherein the one or more baseband processors are to configure the UE to use IEEE 802. lx based authentication for WLAN access.
  • an apparatus of an evolved NodeB comprises one or more baseband processors to decode a Layer 3 transport message received from a wireless local area network (WLAN) Termination (WT) indicating an internet protocol (IP) address of the WT on a WLAN, and to encode a radio resource control (RRC) Connection Reconfiguration message for a user equipment (UE) indicating the IP address of the WT, wherein the WT and the UE may establish a tunnel to carry LWA packets via the WLAN, and a memory to store the Layer 3 transport message or the RRC Connection Reconfiguration message, or a combination thereof.
  • WLAN wireless local area network
  • RRC radio resource control
  • Example fourteen may include the subject matter of example thirteen or any of the examples described herein, wherein the one or more baseband processors are to encode one or more LWA packets to be sent to the UE via the WT using the tunnel.
  • Example fifteen may include the subject matter of example thirteen or any of the examples described herein, wherein the one or more baseband processors are to decode one or more LWA packets received from the UE via the WT using the tunnel.
  • one or more machine-readable media may have instructions stored thereon that, if executed by an apparatus of an evolved NodeB (eNB), result in encoding a wireless local area network (WLAN) Termination (WT) Addition message to be sent to a WT of a WLAN for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA), and receiving a WT Addition Rejection message from the WT in response to the WT Addition message if the UE is rejected by the WT, wherein the WT Addition Rejection message includes a cause for the rejection of the UE.
  • eNB evolved NodeB
  • WT Addition message to be sent to a WT of a WLAN for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA)
  • LTE Long-Term Evolution
  • LWA Long-Term Evolution
  • WT Addition Rejection message includes a cause for the rejection of the UE.
  • Example seventeen may include the subject matter of example sixteen or any of the examples described herein, wherein the cause includes an indication that the UE is not authorized for the WLAN, the WLAN is overloaded, or a combination thereof.
  • Example eighteen may include the subject matter of example sixteen or any of the examples described herein, wherein the instructions, if executed, further result in the WT Addition message being configured to be sent to the WT via an Xw interface, or processing the WT Addition Rejection message received from the WT via the Xw interface.
  • one or more machine-readable media may have instructions stored thereon that, if executed by an apparatus of a wireless local area network (WLAN) termination (WT), result in processing a WT Addition message received from an evolved NodeB (eNB) via an Xw interface for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA), and generating a command to be sent to the eNB via the Xw interface to control offloading traffic for the UE to the WLAN if the WT Addition message is accepted by the WT.
  • WLAN wireless local area network
  • eNB evolved NodeB
  • UE user equipment
  • LTE Long-Term Evolution
  • LWA Long-Term Evolution
  • Example twenty may include the subject matter of example nineteen or any of the examples described herein, wherein the WT Addition message includes an indication that LWA is activated or an indication that LWA is suspended.
  • Example twenty-one may include the subject matter of example nineteen or any of the examples described herein, wherein the command to the eNB comprises a WT Resume command, a WT suspend command, an indication of traffic to be scheduled on the eNB, an indication of traffic to be scheduled on the WT, or a UE identifier for the UE, one or more services, a quality of service (QoS), or a band to be used for the UE for which WLAN access is preferred, or a combination thereof.
  • QoS quality of service
  • Example twenty-two may include the subject matter of example nineteen or any of the examples described herein, wherein the instructions, if executed, further result in initiating LWA by generating the command to the eNB when deemed necessary, and processing a WT Addition message received from the eNB upon the UE entering a LWA location, wherein the WT Addition message includes a group identifier for subscriber UEs authorized for WLAN access via LWA.
  • Example twenty-three may include the subject matter of example nineteen or any of the examples described herein, wherein the command to the eNB includes a measurement configuration for the UE, a list of one or more UEs to be offloaded to LTE access, a list of one or more UEs to be offloaded to WLAN access, Mobility Set information, split ratio information per UE, or data rate per UE or per data radio bearer, or a combination thereof.
  • Example twenty-four may include the subject matter of example nineteen or any of the examples described herein, wherein the WT Addition message received from the eNB includes WLAN measurement results for the UE, data rates to be delivered to the UE, the quality of service (QoS) of offloaded bearers for the UE, or an indication that the UE is configured for enterprise mode, or a combination thereof.
  • the WT Addition message received from the eNB includes WLAN measurement results for the UE, data rates to be delivered to the UE, the quality of service (QoS) of offloaded bearers for the UE, or an indication that the UE is configured for enterprise mode, or a combination thereof.
  • the WT Addition message received from the eNB includes WLAN measurement results for the UE, data rates to be delivered to the UE, the quality of service (QoS) of offloaded bearers for the UE, or an indication that the UE is configured for enterprise mode, or a combination thereof.
  • QoS quality of service
  • one or more machine-readable media may have instructions stored thereon that, if executed by an apparatus of a user equipment (UE), result in encoding a capability message for an evolved NodeB (eNB) to indicate to the eNB that the UE is capable of utilizing Long-Term Evolution (LTE) wireless local area network (WLAN) Aggregation (LWA), and providing an indication in the capability message that the UE prefers WLAN access when LWA is activated.
  • UE user equipment
  • eNB evolved NodeB
  • LTE Long-Term Evolution
  • WLAN wireless local area network
  • LWA wireless local area network
  • Example twenty- six may include the subject matter of example twenty-five or any of the examples described herein, wherein capability message includes an indication that the UE is configured for enterprise mode, an indication that the UE prefers WLAN for uplink (UL) traffic, or a specific identifier (ID) for LWA, or a combination thereof.
  • Example twenty- seven may include the subject matter of example twenty-five or any of the examples described herein, wherein the instructions, if executed, further result in configuring the UE to use IEEE 802. lx based authentication for WLAN access.
  • one or more machine-readable media may have instructions stored thereon that, if executed by an apparatus of an evolved NodeB (eNB), result in decoding a Layer 3 transport message received from a wireless local area network (WLAN) Termination (WT) indicating an internet protocol (IP) address of the WT on a WLAN, and encoding a radio resource control (RRC) Connection Reconfiguration message for a user equipment (UE) indicating the IP address of the WT, wherein the WT and the UE are to establish a tunnel to carry LWA packets via the WLAN.
  • eNB evolved NodeB
  • Example twenty-nine may include the subject matter of example twenty-eight or any of the examples described herein, wherein the instructions, if executed, further result in encoding one or more LWA packets to be sent to the UE via the WT using the tunnel.
  • Example thirty may include the subject matter of example twenty-eight or any of the examples described herein, wherein the instructions, if executed, further result in decoding one or more LWA packets received from the UE via the WT using the tunnel.
  • an apparatus of an evolved NodeB comprises means for encoding a wireless local area network (WLAN) Termination (WT) Addition message to be sent to a WT of a WLAN for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA), and means for receiving a WT Addition Rejection message from the WT in response to the WT Addition message if the UE is rejected by the WT, wherein the WT Addition Rejection message includes a cause for the rejection of the UE.
  • WLAN wireless local area network
  • WT Termination
  • LTE Long-Term Evolution
  • LWA Long-Term Evolution
  • Example thirty-two may include the subject matter of example thirty-one or any of the examples described herein, wherein the instructions, if executed, further result in the WT Addition message being configured to be sent to the WT via an Xw interface, or processing the WT Addition Rejection message received from the WT via the Xw interface.
  • an apparatus of a wireless local area network (WLAN) termination comprises means for processing a WT Addition message received from an evolved NodeB (eNB) via an Xw interface for a user equipment (UE) to connect with the WLAN using Long-Term Evolution (LTE) WLAN Aggregation (LWA), and means for generating a command to be sent to the eNB via the Xw interface to control offloading traffic for the UE to the WLAN if the WT Addition message is accepted by the WT.
  • eNB evolved NodeB
  • LTE Long-Term Evolution
  • LWA Long-Term Evolution
  • Example thirty-four may include the subject matter of example thirty-three or any of the examples described herein, further comprising means for initiating LWA by generating the command to the eNB when deemed necessary, and means for processing a WT Addition message received from the eNB upon the UE entering a LWA location, wherein the WT Addition message includes a group identifier for subscriber UEs authorized for WLAN access via LWA.
  • an apparatus of a user equipment comprises means for encoding a capability message for an evolved NodeB (eNB) to indicate to the eNB that the UE is capable of utilizing Long-Term Evolution (LTE) wireless local area network (WLAN) Aggregation (LWA), and means for providing an indication in the capability message that the UE prefers WLAN access when LWA is activated.
  • eNB evolved NodeB
  • LTE Long-Term Evolution
  • WLAN wireless local area network
  • Example thirty-six may include the subject matter of example thirty-five or any of the examples described herein, wherein capability message includes an indication that the UE is configured for enterprise mode, an indication that the UE prefers WLAN for uplink (UL) traffic, or a specific identifier (ID) for LWA, or a combination thereof.
  • Example thirty-seven may include the subject matter of example thirty-five or any of the examples described herein, further comprising means for configuring the UE to use IEEE 802. lx based authentication for WLAN access.
  • an apparatus of an evolved NodeB comprises means for decoding a Layer 3 transport message received from a wireless local area network (WLAN) Termination (WT) indicating an internet protocol (IP) address of the WT on a WLAN, and means for encoding a radio resource control (RRC) Connection Reconfiguration message for a user equipment (UE) indicating the IP address of the WT, wherein the WT and the UE are to establish a tunnel to carry LWA packets via the WLAN.
  • Example thirty-nine may include the subject matter of example thirty-eight or any of the examples described herein, further comprising means for encoding one or more LWA packets to be sent to the UE via the WT using the tunnel.
  • Example forty may include the subject matter of example thirty-eight or any of the examples described herein, further comprising means for decoding one or more LWA packets received from the UE via the WT using the tunnel.
  • machine-readable storage may include machine-readable instructions, when executed, to realize an apparatus as claimed in any preceding claim.
  • Coupled may mean that two or more elements are in direct physical and/or electrical contact. Coupled, however, may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other.
  • Coupled may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements.
  • on may be used in the following description and claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un appareil d'un nœud b évolué (eNB) comprend un ou plusieurs processeurs de bande de base pour coder un message d'ajout de terminaison de réseau local sans fil (WLAN) (WT) devant être envoyé à une WT pour qu'un équipement d'utilisateur (UE) se connecte au WLAN au moyen d'une agrégation de WLAN (LWA) à évolution à Long terme (LTE), et reçoive un message de refus d'ajout de WT de la WT si l'UE est refusé par la WT, le message contenant une cause du refus. Un appareil d'une WT comprend un ou plusieurs processeurs de bande de base pour traiter un message d'ajout de WT reçu de l'eNB pour que l'UE se connecte à la WT à l'aide d'une LWA, et pour générer une instruction devant être envoyée à l'eNB pour contrôler un délestage du trafic vers le WLAN si le message d'ajout de WT est accepté par la WT. Une tunnellisation GRE peut être établie entre l'UE et la WT pour un déploiement domestique de la LWA.
PCT/US2017/067390 2016-12-20 2017-12-19 Amélioration d'une agrégation de réseau local sans fil d'évolution à long terme pour une utilisation domestique et en entreprise WO2018118973A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201662436973P 2016-12-20 2016-12-20
US62/436,973 2016-12-20
US201662439348P 2016-12-27 2016-12-27
US62/439,348 2016-12-27

Publications (1)

Publication Number Publication Date
WO2018118973A1 true WO2018118973A1 (fr) 2018-06-28

Family

ID=61074505

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2017/067390 WO2018118973A1 (fr) 2016-12-20 2017-12-19 Amélioration d'une agrégation de réseau local sans fil d'évolution à long terme pour une utilisation domestique et en entreprise

Country Status (1)

Country Link
WO (1) WO2018118973A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2458916A1 (fr) * 2009-08-11 2012-05-30 ZTE Corporation Procédé et système pour la gestion de défaillances de transfert vers une cellule de groupe fermé d abonnés

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2458916A1 (fr) * 2009-08-11 2012-05-30 ZTE Corporation Procédé et système pour la gestion de défaillances de transfert vers une cellule de groupe fermé d abonnés

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access Network (E- UTRAN) and Wireless LAN (WLAN); Xw application protocol (XwAP) (Release 13)", 3GPP STANDARD ; TECHNICAL SPECIFICATION ; 3GPP TS 36.463, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG3, no. V13.1.0, 1 July 2016 (2016-07-01), pages 1 - 94, XP051295307 *
NOKIA NETWORKS ET AL: "Cause Values in LWA", vol. RAN WG3, no. St. Julian's, Malta; 20160215 - 20160219, 14 February 2016 (2016-02-14), XP051056246, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/Meetings_3GPP_SYNC/RAN3/Docs/> [retrieved on 20160214] *
RICHARD BURBIDGE (INTEL CORPORATION): "Liaison from 3GPP on LWA and LWIP ; 11-16-0351-01-0000-liaison-from-3gpp-on-lwa-and-lwip", IEEE DRAFT; 11-16-0351-01-0000-LIAISON-FROM-3GPP-ON-LWA-AND-LWIP, IEEE-SA MENTOR, PISCATAWAY, NJ USA, vol. 802.11, no. 1, 14 March 2016 (2016-03-14), pages 1 - 25, XP068105227 *

Similar Documents

Publication Publication Date Title
US11778631B2 (en) Transmission of group common PDCCH (physical downlink control channel) for NR (new radio)
US10986548B2 (en) Enhanced conditional handover
US11895547B2 (en) Network controlled small gap configuration
US11122453B2 (en) Systems, methods and devices for measurement configuration by a secondary node in EN-DC
US11006425B2 (en) Mechanisms to handle DL (downlink) control and data channels with different numerologies in NR (new radio)
JP2023537716A (ja) Ｖ－ｐｏｌ／ｈ－ｐｏｌ仮想化によるｆｒ２のためのビーム管理拡張
WO2018144781A1 (fr) Mesure de rsrp pour norme nouvelle radio
US11997530B2 (en) QoS management aspects for NR sidelink to support advanced V2X use cases
US20210400633A1 (en) Resource Allocation and Configuration for Broadcast and Unicast Operation Over Sidelink for NR V2X
US20210385681A1 (en) Measurement Gap Enhancements
US20210400738A1 (en) Connection Management Solution to Support Unicast and Groupcast Communication Over Sidelink for EV2X
US11924919B2 (en) Self-learning UE capability verification from partial reported capabilities
US11102846B2 (en) Downlink control information to support uplink partial subframe transmission on licensed assisted access secondary cell
US20220345953A1 (en) Apparatuses for partially offloading protocol processing
US20190044810A1 (en) Channel whitelist and flexible frame design for enhanced machine-type communications systems in unlicensed spectrum
WO2018144670A1 (fr) Mesures à large bande dans des systèmes de nouvelle radio
US11930443B2 (en) Enhancement for SMTC configuration for new radio
WO2018118973A1 (fr) Amélioration d&#39;une agrégation de réseau local sans fil d&#39;évolution à long terme pour une utilisation domestique et en entreprise
WO2018053160A1 (fr) Conception de canal de commande de liaison descendante pour des systèmes de formation de faisceau
WO2018031649A1 (fr) Accès à des technologies existantes au moyen d&#39;un équipement utilisateur
US20230180207A1 (en) Optimizing of scheduling
WO2018140608A1 (fr) Actions elwa/lwip suite à une déconnexion de wlan

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17835970

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17835970

Country of ref document: EP

Kind code of ref document: A1