WO2018060540A1 - Amélioration d'efficacité de communication - Google Patents

Amélioration d'efficacité de communication Download PDF

Info

Publication number
WO2018060540A1
WO2018060540A1 PCT/FI2016/050678 FI2016050678W WO2018060540A1 WO 2018060540 A1 WO2018060540 A1 WO 2018060540A1 FI 2016050678 W FI2016050678 W FI 2016050678W WO 2018060540 A1 WO2018060540 A1 WO 2018060540A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
data packet
service
identifier
terminal device
Prior art date
Application number
PCT/FI2016/050678
Other languages
English (en)
Inventor
Daniela Laselva
Frank Frederiksen
Jari MUSTAJÄRVI
Original Assignee
Nokia Technologies Oy
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 Nokia Technologies Oy filed Critical Nokia Technologies Oy
Priority to PCT/FI2016/050678 priority Critical patent/WO2018060540A1/fr
Publication of WO2018060540A1 publication Critical patent/WO2018060540A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/66—Layer 2 routing, e.g. in Ethernet based MAN's
    • 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

  • the invention relates to communications. BACKGROUND
  • aggregated communication may increase data communication capabilities.
  • aggregated communication is the use of wireless local area network in co-operation with a cellular network. Enhancing co-operation between said networks may further increase said data communication capabilities of said system.
  • FIGS 1A to IB illustrate example wireless communication systems to which embodiments of the invention may be applied;
  • FIGS. 2 and 3 illustrate flow diagrams according to some embodiments
  • FIGS. 4A to 4D illustrate signal diagrams according to some embodiments
  • Figure 5 illustrates a signal diagram according to an embodiment
  • FIGS. 6A and 6B illustrate embodiments
  • FIGS 7A and 7B illustrate embodiments
  • FIGS 8 and 9 illustrate block diagrams of apparatuses according to some embodiments. DETAILED DESCRIPTION OF SOME EMBODIMENTS
  • Embodiments described may be implemented in a radio system, such as in at least one of the following: Worldwide Interoperability for Micro-wave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, LTE/Wireless Local Area Network (WLAN, WLAN may sometimes be referred to as WiFi) aggregation (LWA) system, and/or Enhanced LWA (eLWA) system.
  • WiMAX Worldwide Interoperability for Micro-wave Access
  • GSM Global System for Mobile communications
  • GERAN GSM EDGE radio access Network
  • GRPS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • W-CDMA basic wideband-code division multiple access
  • HSPA high-speed packet
  • 5G is likely to use multiple input - multiple output (MIMO) techniques (including MIMO antennas), many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • 5G will likely be comprised of more than one radio access technology (RAT), each optimized for certain use cases and/or spectrum.
  • RAT radio access technology
  • 5G mobile communications will have a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control.
  • 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE.
  • 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave.
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware.
  • Cloud computing or cloud data storage may also be utilized.
  • radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labor between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Some other technology advancements probably to be used are Software-Defined Networking (SDN), Big Data, and all-IP, which may change the way networks are being constructed and managed.
  • SDN Software-Defined Networking
  • Big Data Big Data
  • all-IP all-IP
  • SDN may refer to a system feature where data and control place functionalities are completely separated.
  • the routers or switches may only execute low level forwarding rules that are established by governing SDN controllers.
  • NFV may virtualize the router function to a generic purpose hardware. By separating the control and forwarding function, SDN may be used to control NFV router, for example. Thus, NFV and SDN may complement each other.
  • FIGS 1A and IB illustrate some examples of wireless systems to which embodiments may be applied.
  • wireless communication networks such as the Long Term Evolution (LTE), the LTE- Advanced (LTE -A) of the 3 rd Generation Partnership Project (3GPP), WLAN, or the predicted future 5G solutions, are typically composed of at least one network element, such as a network element 102, providing at least one cell, such as cell 104.
  • LTE Long Term Evolution
  • LTE -A LTE- Advanced
  • 3GPP 3 rd Generation Partnership Project
  • WLAN Wireless Fidelity
  • the predicted future 5G solutions are typically composed of at least one network element, such as a network element 102, providing at least one cell, such as cell 104.
  • cells 104, 114, 124 are shown.
  • the cell 114 may be provided by a network element 112
  • the cell 124 may be provided by a network element 122, for example.
  • the cell 104 may be provided by the network element 102.
  • a network element of the radio system may provide more than one cell.
  • the network element 102 may provide the cell 104, the cell 114, and/or the cell 124.
  • the system may comprise one or more network elements, wherein each network element provides one or more cells providing service to one or more terminal devices in the cells.
  • Each cell of the radio communication network may be, e.g., a macro cell, a micro cell, a femto, or a pico-cell, for example, meaning that there may be one or more of each of the described cells.
  • Each network element of the radio communication network such as the network elements 102, 112, 122, may be an evolved Node B (eNB) as in the LTE and LTE-A, a radio network controller (RNC) as in the UMTS, a base station controller (BSC) as in the GSM/GERAN, or any other apparatus capable of controlling wireless communication and managing radio resources within a cell or cells. That is, there may be one or more of each of the described apparatuses or entities.
  • eNB evolved Node B
  • RNC radio network controller
  • BSC base station controller
  • the implementation may be similar to LTE-A, as described above.
  • the network elements 102, 112, 122 may be base station(s) or a small base station(s), for example.
  • the eNBs may be connected to each other with an X2 interface as specified in the LTE. Other communication methods between the network elements may also be possible.
  • the wireless system may further comprise at least one terminal device 110, 120, 130, 140 to which the one more network elements 102, 112, 122 may provide communication services.
  • the cells 104, 114, 124 may provide service for the at least one terminal device 110, 120, 130, 140, wherein the at least one terminal device 110, 120, 130, 140 may be located within or comprised in at least one of the cells 104, 114, 124.
  • the at least one terminal device 110, 120, 130, 140 may communicate with the network elements 102, 112, 122 using communication link(s), which may be understood as communication link(s) for end-to-end communication, wherein source device transmits data to the destination device.
  • the cells 104, 114, 124 may provide service for a certain area, and thus the at least one terminal device 110, 120, 130, 140 may need to be within said area in order to be able to use said service (horizontally and/or vertically).
  • a third terminal device 130 may be able to use service provided by the cells 104, 114, 124.
  • a fourth terminal device 140 may be able to use only service of the cell 104, for example.
  • the cells 104, 114, 124 may be at least partially overlapping with each other.
  • the at least one terminal device 110, 120, 130, 140 may be enable to use service of more than one cell at a time.
  • the sub-cells 114, 124 may be small cells that are associated with the macro cell 104.
  • the network element 102 e.g. macro network element 102
  • the network elements 112, 122 e.g. local area access nodes
  • the macro network element 102 may cause the local area access nodes 112, 122 to transmit data to the at least one terminal device 110, 120, 130, 140. It may also be possible to receive data, by the network element 102, from the at least one terminal device 110, 120, 130, 140 via the network elements 112, 122.
  • the at least one terminal device 110, 120, 130, 140 may comprise mobile phones, smart phones, tablet computers, laptops and other devices used for communication with the wireless communication network.
  • the wireless system may comprise, in addition to one or more cellular network elements (e.g. network element 102), one or more access points (AP) 112, 122. That is, in general, the wireless system may comprise, for example, one or more eNBs 102 and one or more APs 112, 114.
  • the AP(s) 112, 122 may provide wireless communication according to WLAN specifications and/or cellular communication specifications. That is, for example, AP 112 may act as a regular WLAN AP and/or as an AP for providing aggregated communication with one or more network elements 102 of a cellular network.
  • the wireless system of Figure 1A may support Carrier Aggregation (CA).
  • CA Carrier Aggregation
  • CA may enable increasing usable bandwidth between the terminal devices and network elements of the radio system.
  • CA may be used for LTE-A in order to support wider transmission bandwidths enhancing increased potential peak data rates to meet LTE-A requirements.
  • more than one component carriers may be aggregated, by a network element (e.g. network element 102), contiguously and/or non-contiguously to provide a wider bandwidth.
  • a network element e.g. network element 102
  • uplink carrier aggregation multiple uplink component carriers may be aggregated and can be allocated in a subframe to a terminal device.
  • the radio system may support intra-band CA with contiguous and/or non-contiguous resource allocation.
  • the radio system may also support inter- band CA enabling non-contiguous resource allocation from more than one radio band.
  • the radio system of Figure 1A supports Licensed-Assisted Access (LAA) which relates to using unlicensed radio band(s) for data transfer.
  • LAA Licensed-Assisted Access
  • the network element 102 and/or a second network element 112 may provide one or more unlicensed cells in order to increase data transfer capability on the radio communication system.
  • the network element 102 may allocate radio resources of the one or more unlicensed cell for the at least one terminal device 110, 130, through CA, thus increasing the data transfer between the at least one terminal device 110, 130 and the network element(s).
  • One example of utilizing unlicensed and/or licensed radio bands may be an aggregation technique that utilizes WLAN communication.
  • Such aggregation technique may be referred to as LTE/WLAN aggregation (LWA) or enhanced LWA (eLWA).
  • LWA LTE/WLAN aggregation
  • eLWA enhanced LWA
  • aggregation utilizing a 5G cellular network and WLAN network may be possible.
  • Aggregation utilizing WLAN and cellular communication may denote Dual Connectivity (DC) in which aggregation may occur at Packet Data Convergence Protocol (PDCP) -layer.
  • DC Dual Connectivity
  • aggregation as used in this application may refer to utilizing, for example, use of DC on licensed and/or unlicensed radio bands.
  • DC may provide one communication link and cellular communication link may be the other communication link.
  • DC (or aggregation in more general terms) may be adaptable for a multi connection scenario in which more than two communication links are utilized. Therefore, embodiments of the invention may also be adaptable for such multi connection system.
  • the network element 102 may provide a primary cellular service for a terminal device in a cell (e.g. Primary Serving Cell (PSC), PCell). Further, the same network element 102 or some other network element (e.g. AP 112) may provide a secondary cellular service (e.g. Secondary Serving Cell (SSC), SCell). Said secondary cellular service may at least partially be controlled by the network element 102. Thus, for example, data rates may be increased. Thus, for example, the terminal device 110 may transmit cellular data via the AP 112 (e.g. WLAN AP) and/or via the network element 102.
  • the AP 112 e.g. WLAN AP
  • a wireless system comprising at least the AP 112 and the network element 102 is shown.
  • the wireless system of Figure IB may be a part of the wireless system described with reference to Figure 1A, for example.
  • the AP 112 may co-operate with one or more network elements of a cellular system (e.g. network element 102) for providing aggregation (i.e. aggregated communication utilizing DC) to one or more terminal devices 110.
  • the AP 112 may provide WLAN services, such as access to one or more local servers 156 and/or Internet access 154.
  • the Internet access 154 may happen via one or more gateways 152.
  • the AP 112 may be connected with the one or more network elements 102 via Xw-interface 164. This may, for example, mean that the AP 112 is connected (i.e. communicatively connected) with an entity 190 (e.g. Wireless Controller) which terminates Xw-interface 164 from the network element 102 (e.g. eNB 102).
  • entity 190 e.g. Wireless Controller
  • the entity 190 may be comprised in the Wireless Controller or in a separate physical entity.
  • the entity 190 may be comprised in the AP 112.
  • the entity 190 may be comprised in the network element 102.
  • the entity 190 is referred to as Wireless Termination entity (e.g. WLAN Termination entity).
  • the entity 190 may control one or more APs 112. As said, it may be co-located with a WLAN AP as well, but functionally it may have dedicated functions (e.g. terminating the General Packet Radio Service (GPRS) Tunneling Protocol (GTP) user plane (U) and control plane (C) tunnels, i.e. GTP-U and GTP-C), wherein a user-plane data packet sent over the GTU-U tunnel (per bearer granularity) may be according to the LWAAP protocol for a given bearer (e.g. split LWA bearer 167).
  • GPRS General Packet Radio Service
  • GTP General Packet Radio Service
  • U General Packet Radio Service
  • C control plane
  • a user-plane data packet sent over the GTU-U tunnel per bearer granularity
  • a given bearer e.g. split LWA bearer 167.
  • the WT 190 may, when utilized in WLAN, terminate the Xw-interface 164 on the WLAN network side.
  • the Xw-interface 164 may enable communication between the WLAN(s) and the cellular network(s) as described.
  • the WT 190 may be understood as a functional feature that may be comprised in a separate entity (i.e. specifically reserved for at least the WT 190), in the AP 112 or in the network element 102, to name a few examples.
  • the one or more network elements 102 may be connected to an Evolved Packet Core (EPC) 160 via a Sl-interface 162.
  • the EPC 160 may comprise one or more mobility management entities/serving gateways (MMEs/SGWs) and at least one Packet Data Network Gateway (PGW).
  • MMEs/SGWs mobility management entities/serving gateways
  • PGW Packet Data Network Gateway
  • the one or more network elements 102 may communicate with each other and the AP 112 may communicate with the one or more network elements 102 using, for example, the described interfaces 162, 164.
  • PLMN Public Land Mobile Network
  • IDs Public Land Mobile Network
  • Using the Xw-interface 164 may enable the use of a split LWA bearer, wherein, for example, the network element 102 and the AP 112 co-operate to provide aggregation for the terminal device 110 and/or to some other terminal devices.
  • master cell group bearer 166 and split LWA bearer 167 may be utilized.
  • the wireless system of Figure IB utilizes Xw-interface 164 providing communication between the WLAN(s) and the cellular network(s), other solutions to provide such communication may be utilized to achieve benefits of the provided solution.
  • the described system of Figure 1A or Figure IB may not be necessary.
  • any communication means suitable for conveying user data between the AP 112 and the network element 102, for example, in LWA system may be utilized.
  • the same AP 112 may be used as a part of a cellular system and as a part of a WLAN system some difficulties may arise.
  • the AP 112 may not necessarily be aware of what kind of data it has received. Therefore, the AP 112 may not necessarily know whether the received data should be conveyed to the one or more network elements 102 (e.g. cellular services) (or more particularly to the WT 190), to the gateway 152 (e.g. Internet access via WLAN services) or to the one or more local servers 156 (e.g. local WLAN services).
  • the provided solution may be applicable to various systems and networks in which the data packet destination should be indicated to a receiving entity.
  • the solution may be applicable to L2 layer data packets, and specifically indication of required service of a transmitted L2 layer data packet.
  • Figure 2 illustrates a flow diagram according to an embodiment.
  • a terminal device operating with at least one first network and at least one second network, may obtain a data packet to be transmitted (block 210); determine a required service associated with said data packet, wherein the required service is a service associated with the at least one first network or a service associated with the at least one second network (block 220); generate an identifier based at least on the required service (block 230); and transmit said data packet including the generated identifier (block 240).
  • Said terminal device may be, for example, the terminal device 110.
  • FIG. 3 illustrates a flow diagram according to an embodiment.
  • a network element of at least one second network co- operating with at least one first network for providing communication services to at least one terminal device may receive a data packet from a terminal device amongst said at least one terminal device (block 310); determine a required service associated with said data packet based on an identifier included in said data packet, wherein the required service is a service associated with the at least one first network or a service associated with the at least one second network (block 320); and initiate routing of said data packet to a first network amongst the at least one first network if the required service is the service associated with the at least one first network (block 330).
  • Said network element may be, for example, the AP 112 and said terminal device may be, for example, the terminal device 110.
  • first and second network(s) may be different networks than cellular and WLAN networks.
  • both first and second networks may be WLAN networks.
  • both first and second networks may be cellular networks.
  • both first and second networks may utilized wired communication.
  • a service type identifier may be included in a layer 2 data packet in order to enable the receiver to know what to do with said data packet.
  • MAC Media Access Control
  • MAC addresses may be unique identifiers (e.g. Globally Unique Identifier (GUID)) associated with network devices (e.g. terminals, APs, cellular network elements) of a wireless or wired network.
  • GUID Globally Unique Identifier
  • MAC addresses may be used to identify said network devices.
  • One MAC address may identify one network device (e.g. network element 102, AP 112, terminal device 110).
  • a WLAN data packet may have the address options indicated in Table 1 below.
  • Table 1 MAC address options for a WLAN data packet.
  • the data packet transmitted in step 240 of Figure 2 and received in step 310 of Figure 3 may utilize, at least in some embodiments, the third row of Table 1. That is, said data packet may comprise the MAC address information (i.e. address 1, 2, and 3) of the third row of Table 1. Said third row may be reserved for a LWA or eLWA use.
  • address 1 of said data packet indicates a Basic Service Set Identifier (BSSID)
  • address 2 indicates source address (i.e. terminal device MAC address)
  • address 3 indicates said identifier indicating at least the required service associated with said data packet. That is, the address 3 may be used to indicate, by the terminal device 110 to the AP 112, at least whether the data packet is for a cellular service (e.g.
  • BSSID Basic Service Set Identifier
  • address 2 indicates source address (i.e. terminal device MAC address)
  • address 3 indicates said identifier indicating at least the required service associated with said data packet. That is, the address 3 may be used to indicate, by the
  • the data packet comprises an identifier indicating a logical entity (i.e. service) instead of indicating a physical entity (i.e. actual receiver).
  • a physical entity or group of physical entities may be indicated. This may even further enhance the solution.
  • Table 1 may be one example of how the identifier is transmitted with the data packet. However, there may be other ways to include said identifier to the data packet that is transmitted, and thus indicate the logical entity or the logical entity and the physical entity.
  • the proposed solution may enable the AP 112 to determine what to do with the received data packet. Further, it may provide a further benefit by possibly concealing the actual receiver entity in case that the data packet is for a cellular network element. That is, the AP 112 may only determine based on the identifier that the data packet is to be conveyed to a cellular network without knowing the actual receiver entity of the cellular network. The AP 112 may in such case transmit the data packet, for example, to the network element 102 that is configured with the AP 112 to provide aggregation (e.g. LWA, eLWA) service to the terminal device 110. However, the network element 102 may determine to which entity the data packet is to be further conveyed after receiving said data packet.
  • aggregation e.g. LWA, eLWA
  • the AP 112 may only know that the data packet is for a cellular network and transmit the data packet to the cellular network. Hence, security of cellular communication may be enhanced as the AP 112 may be unaware of the actual target entity of the data packet.
  • the network element 102 may determine said target entity based on, for example, terminal device MAC address and the identifier indicating the required service. For example, in case of more than one operators, the identity of the target operator may be concealed from the AP 112.
  • the AP 112 may be used to provide aggregation for more than one operator and thus more than one cellular network. Even further, by utilizing the WLAN services, there may be no need to transmit data via the cellular network when the data is related to Internet services.
  • the network element 102 does not broadcast WT 190 identifier (e.g. WT 190 MAC address).
  • the terminal device 110 may not receive the WT 190 MAC address.
  • the data packet transferred, for example, in block 240 does not include WT 190 MAC address.
  • the network element 102 may also not indicate Ethernet protocol type (EtherType) to the terminal device 110. If the WT 190 MAC address is not broadcasted and/or not included by the terminal device 110 to the data packet, security may be increased. Further, signaling in the network(s) may be decreased leading to, for example, more power-friendly solutions.
  • the AP 112 may determine, based on the required service indicated by the identifier, whether the data packet is associated with local services(s), local break-out traffic, or with cellular communication (e.g. Uplink LWA). Thus, in the case of cellular communication, the AP 112 may route the data packet to the WT 190.
  • the AP 112 may be preconfigured with the WT 190 so that it may determine where the route the data packet in case of cellular communication.
  • Figures 4A to 4D illustrate signal diagrams according to some embodiments.
  • the terminal device 110 may obtain a data packet (block 402) as also discussed with reference to block 210. This may mean that the terminal device 110 has a need to transmit a data packet or data packets.
  • a data packet may comprise a payload part and a part for including the identifier generated in block 406. Further, the data packet may comprise, at least in some embodiments, the address 1 and address 2 as shown in Table 1.
  • the data packet may be for a cellular communication or for a WLAN communication, for example. That is, a required service associated with the data packet may be a cellular communication service or a WLAN communication service.
  • the terminal device 110 may determine the required service associated with said data packet. E.g. is the data packet associated with the cellular communication service or with the WLAN communication service. It needs to be noted here that when the AP 112 provides aggregation with the network element 102, the AP 112 may not be providing WLAN communication services, but cellular communication services. However, as indicated above, the AP 112 may also provide WLAN communication services to the terminal device 110 for accessing Internet 154 or local server(s) 156, for example.
  • the terminal device 110 may generate an identifier based at least on the required service.
  • the identifier may at least indicate the service the data packet is associated with.
  • the terminal device 110 may select the identifier or a part of the identifier amongst a static and/or preconfigured identifiers, wherein each of the static and/or preconfigured identifiers is associated with a service.
  • a first service identifier may indicate cellular communication services (e.g. LWA Uplink (UL) services meaning that the data packet should be routed via the AP 112 to a cellular network (e.g. network element 102)).
  • a second service identifier may indicate local WLAN communication services (e.g.
  • a third service identifier may indicate external WLAN communication services (e.g. the data packet should be routed to the gateway 152 for access to an external network, such as the Internet 154)). This may be the case e.g. in local break-out where the address indicates that the terminal device's traffic is intended for the Internet / servers not operated by the current mobile network operator (MNO), and should be routed towards the WLAN gateway.
  • the identifier generated in block 406 comprises said first identifier, said second identifier, or said third identifier (i.e. referring to service identifiers indicating services).
  • the part comprising or containing said first identifier, said second identifier, or said third identifier may be denoted as a static part.
  • said first identifier, said second identifier, and said third identifier are MAC addresses.
  • the said first identifier, said second identifier, or said third identifier may be static MAC addresses.
  • local break-out may refer to local break-out traffic. It may sometimes be referred to as traffic break-out, local breakout or local break out. However, in general it means that the traffic or data packet targets an entity outside the network (e.g. outside the WLAN).
  • Said first identifier, said second identifier, and said third identifier may be indicated by, for example, the cellular network (e.g. network element 102) or the WLAN network to the terminal device 110, or preconfigured to the terminal device 110. Further, said first identifier, said second identifier, and said third identifier may be preconfigured to the AP 112 or indicated by the cellular communication network to the AP 112.
  • the static part further indicates, in addition to the indicated service, at least one characteristics of the indicated service.
  • the at least one characteristics may denote a target routing entity for the data packet.
  • the static part could further indicate the gateway 152.
  • the static part could specifically indicate a printer or some other local server.
  • the AP 112 determines the gateway 152 or the local server(s) based on the indication of the required service. For example, the AP 112 may select one server amongst the one or more local servers 156 based on the required service. Similarly, the gateway 152 may be selected by the AP 112.
  • the AP 112 may be configured to utilize a set of rules in determining the target routing destination based on the required service.
  • the indicated service in general may denote outer address or destination, and the at least one characteristics (e.g. service provider) may be understood as inner address or destination.
  • the terminal device 110 does not use PDCP, or if PDCP is used, the data packet is encrypted with null- encryption.
  • the AP 112, WT 190, gateway 152 and/or the local server(s) 156 may be able to decode the data packet. If the data packet would be encrypted, without the WLAN network entities knowing the PDCP encryption keys, the data packet may not be successfully decoded. In general, this may mean that in addition that the required service is indicated, the data packet may be formed differently (e.g. differently encoded) when used for LWA purposes and for WLAN purposes.
  • the terminal device 110 may transmit the data packet including the generated identifier (block 406).
  • the data packet is transmitted to the network element performing the steps of Figure 3.
  • said network element may be the AP 112.
  • the AP 112 may be an access point of at least one WLAN as indicated above. That is, the AP 112 may operate as an access point for more than one WLAN. However, in an embodiment, the AP 112 is an access point of a WLAN.
  • the AP 112 may determine, based on the identifier in the received data packet, the required service associated with said data packet.
  • the AP 112 may determine what to do with the received data packet. However, the AP 112 may determine, based on the generated identifier in block 406, an action to be performed to the received data packet (i.e. which service is required, by the terminal device 110 for the received data packet).
  • the data packet, transmitted in block 408, is transmitted to said network element (e.g. the AP 112) directly via air-interface. That is, the data packet may not travel via some other entities to said network element (e.g. the AP 112). This may, for example, reduce delay for the transmitted data packet.
  • the AP 112 may determine required service associated with the received data packet based on the identifier in said data packet. If the identifier indicates a cellular communication service (e.g. LWA UL services), the AP 112 may transmit or route the data packet to a cellular network (e.g. to network element 102) (block 412). In some embodiments, this means that the data packet is transmitted to the WT 190. The WT 190 may further transmit the data packet to the network element 102, for example. If the AP 112 is configured to operate with only one cellular network, the AP 112 may know, based on the determined required service (block 410) where to transmit or route the data packet.
  • a cellular communication service e.g. LWA UL services
  • the AP 112 may in such case be configured to route all cellular communication service associated data packets to a certain network element (e.g. WT 190), wherein said certain network element may further route the data packet to correct cellular network.
  • said certain network element may determine the correct cellular network based on source address (e.g. address 2 of Table 1) of the data packet.
  • the identifier included in the data packet may indicate a certain cellular network to which the AP 112 should route the data packet.
  • some other network e.g. not cellular network, similar identification of the correct non-cellular network may be used. Let us discuss these options in further detail.
  • the terminal device 110 determines a cellular network identifier indicating a cellular network amongst at least one cellular network, wherein the generating the identifier (block 406) included in said data packet is based on the required service and the cellular network identifier.
  • Figure 5 indicates one example how the cellular network identifier may be obtained by the terminal device 110.
  • the network element 102 co-operating with the AP 112 for providing aggregation for the terminal device 110 transmits, in block 502, a cellular network identifier indicating a cellular network.
  • the cellular network identifier may be broadcasted, multicasted and/or unicasted.
  • the terminal device 110 may receive said cellular network identifier, and hence utilize it when generating the identifier included in the transmitted data packet.
  • the cellular network identifier may indicate a PLMN, for example.
  • the use of the cellular network identifier may enable multiple operators (e.g. multiple PLMNs) to utilize the same AP 112 for aggregated communication.
  • the AP 112 may know whether to process the data packet itself, route the data packet to local server(s) 156, route the data packet to the gateway 152, or to route the data packet to the identified cellular network amongst a plurality of cellular networks.
  • the terminal device 110 determines a first network identifier indicating a first network amongst at least one first network, wherein the generating the identifier included in said data packet is based on the required service and the first network identifier.
  • the first network may denote the cellular network.
  • the identifier may indicate that the data packet is to be routed to the first network indicated by the first network identifier.
  • the required service is the service associated with the at least one cellular network (e.g. cellular Uplink (UL) data packet, e.g. UL LWA data packet), wherein the identifier included in said data packet further indicates that the data packet is to be routed to the cellular network indicated by the cellular network identifier.
  • UL cellular Uplink
  • the identifier included in said data packet indicates that the data packet is to be routed to the WT 190.
  • the identifier may indicate one the first and second cellular networks.
  • the AP 112 may route the data packet to the correct cellular network.
  • the required service is the service associated with the at least one cellular network, wherein the identifier included in said data packet does not indicate a specific network element of the indicated cellular network. That is, the identity of the target entity may be concealed from the AP 112 for improved security.
  • the AP 112 may transmit all traffic to a network element (e.g. network element 102) that is comprised in the indicated cellular network or to the WT 190.
  • Said network element may further determine, based on the received data packet which may still include said identifier, to which network element of the indicated cellular network the data packet should be further transmitted to.
  • the cellular network not the target network entity of the cellular network, may further reduce control signaling between the terminal device 110 and the cellular network.
  • the target network element may not need to indicate its MAC address to the terminal device 110 using Radio Resource Control (RRC) signaling as the cellular network identifier (e.g. block 502, e.g. PLMN ID) may be known by the terminal device 110.
  • RRC Radio Resource Control
  • the identifier included in said data packet does not indicate an address of an entity (e.g. WT 190) enabling data packet transfer between the at least one first network and the at least one second network (e.g. between the cellular network(s) and the WLAN(s)).
  • entity e.g. WT 190
  • this provides some benefits, e.g. security may be enhanced as the terminal device 110 may not know MAC address of said entity, and also there may be no need to transmit said MAC address to the terminal device 110.
  • the required service associated with the data packet to be transmitted by the terminal device 110
  • the identifier included in said data packet may so indicate.
  • the AP 112 may determine, in block 410, that the required service is associated with WLAN.
  • the AP 112 may perform an action on the data packet based on said determination.
  • the identifier included in said data packet further indicates whether the data packet is for the AP 112 or to be routed, by the AP 112, to another network element (e.g. gateway 152 in case of local break-out, or local server(s) 156).
  • the AP 112 may, in some embodiments, act as an AP for more than one WLAN.
  • the AP 112 routes said data packet to another network element of the WLAN if the identifier included in said data packet indicates that the data packet is to be routed to said another network element (block 414, 416).
  • the identifier indicates that the required service is a service of an external network (e.g. Internet 154)
  • the data packet may be routed to the gateway 152 (block 414).
  • the identifier indicates that the required service is a service of the WLAN (e.g. local service)
  • the data packet may be routed to the local server(s) 156.
  • One example of such local service may be printer service that is comprised in the same network with the AP 112.
  • the identifier included in said data packet may indicate the required local service (e.g. data packet to printer).
  • the identifier included in said data packet indicates where to route the data packet within the at least one second network.
  • the identifier included in said data packet indicates whether the required service is associated with a local break-out traffic (e.g. external service via the second network) or with at least one local service provided by the at least one second network (e.g. WLAN).
  • said identifier may indicate, in the case of local service, a specific server or service amongst one or more servers or services provided by the at least one second network. For instance, there may be a mapping table configured at the AP 112, the table comprising one or more service identifiers each associated with a certain service.
  • a first service identifier may denote a first service or server of the second network and a second service identifier may denote a second service or a server of the second network.
  • the AP 112 may determine, based on said identifier included in said data packet and on the mapping table, where to route the data packet to.
  • the identifier indicates a local service, but in some other embodiments it may potentially also indicate a gateway (e.g. gateway 152) amongst a plurality of gateways.
  • one server of the second network may provide plurality of services, and thus the service identifier may indicate specific service and not only a server.
  • the AP 112 processes a payload part of said data packet if the identifier included in said data packet indicates that the data packet is for the AP 112. Thus, if the required service is provided or may be provided by the AP 112, the data packet may not be routed to other network elements of the WLAN or the cellular network(s).
  • a Same Service Set Identifier is used for data packets regardless of the required service. That is, same SSID may be used for a data packet associated with cellular service, local break-out, or with local server(s) 156.
  • the first data packet may be UL LWA data packet associated with said SSID.
  • the second data packet may be a WLAN data packet associated with local break-out, wherein the second data packet is associated with the same SSID as the first data packet.
  • the first and second data packets may comprise BSSIDs (as shown in Table 1), wherein the BSSIDs are bound to the same SSID.
  • the same SSID may be indicated in the data packet.
  • Figure 5 illustrates an embodiment.
  • the network element 102 co-operating with the AP 112 to provide aggregated communication to the terminal device 110 broadcast the cellular network identifier (e.g. comprised in PLMN information broadcasted by the network element 102).
  • the terminal device 110 may receive said cellular network identifier.
  • the AP 112 acquires one or more cellular network identifiers each associated with a cellular network.
  • the AP 112 may receive the cellular network identifier broadcasted by the network element 102.
  • the network element 102 may transmit said cellular network identifier to the AP 112 via Xw-interface 164.
  • the block 502 may be performed by the AP 112 and/or the network element 102.
  • the AP 112 acquires the cellular network identifier via Hotspot 2.0 (3GPP cellular network information that contains the cellular operator's PLMN ID).
  • This cellular network identifier may allow flexibility to have multiple operators to use the same APs, scenario that may be useful in case of Radio Access Network (RAN) sharing and sharing of the same transport network.
  • RAN Radio Access Network
  • MNOs Mobile Network Operators
  • the proposed solution may be applicable to MulteFire use case in which one operator may own the network, and more than one operator may use said network (e.g. WLAN network co-operating with one or more cellular networks).
  • the AP 112 is one of a plurality of APs controlled by at least one WT 190, wherein the WT 190 terminates the Xw-interface 164 from the cellular network. That is the WT 190 may be in communication with the one or more cellular networks via the Xw-interface 164.
  • the WT 190 may be in wireless or wired communication with one or more APs (e.g. AP 112).
  • a data packet associated with the cellular communication service may travel from the AP 112 to the WT 190 and further to the cellular network.
  • the AP 112 is comprised in the WT 190 or is the WT 190.
  • the blocks 402 and 404 performed by the terminal device 110 may be similar as in Figure 4A.
  • the terminal device 110 may generate the identifier based on the required service and the received cellular network identifier (block 504).
  • said identifier included in said data packet may indicate and/or comprise both the required service and the cellular network identifier.
  • the data packet including said identifier may be transmitted in block 408 of Figure 5 to the AP 112.
  • the AP 112 may perform a certain action to the data packet. Said action may comprise action of block 412, block 414, block 416 or processing the payload part of the data packet by the AP 112 independently.
  • the required service is a service associated with the WLAN (e.g. local break-out or local server(s)).
  • the terminal device 110 may not necessarily include the cellular network identifier into said data packet. However, in some embodiments it may be that the terminal device includes said cellular network identifier even though the required service is the service associated with the WLAN.
  • the identifier included in said data packet indicates where to route, by the receiving network element (e.g. AP 112), the data packet within the at least one second network. For example, said identifier indicates should the data packet be routed to the gateway 152 or to the local server(s) 156.
  • Said receiving network element may further be configured to route said data packet to another network element of the at least one second network if the required service is the service associated with the at least one second network, wherein said another network element is responsible of either at least one local service of the at least one second network or local break-out traffic.
  • An arrow 197 may indicate a communication link between the network element 102 and the terminal device 110.
  • the network element 102 of a first network may provide LWA configuration to the terminal device 110. This may include PLMN info at least in some embodiments.
  • the terminal device 110 is aware of the PLMN information (e.g. PLMN ID) as it may acquire Registered PLMN (RPLMN) and/or Home PLMN (HPLMN).
  • PLMN may denote PLMN of a home network (i.e. network that is operated by same entity that provides Subscriber Identity Module (SIM)).
  • SIM Subscriber Identity Module
  • the PLMN may be different than the HPLMN as the network may be provided by a different entity.
  • the communication link may be used to transmit Uplink data packets on the master cell group bearer, for example.
  • Another communication link is indicated with an arrow 198.
  • This communication link may be between the network element 112 of a second communication network and the terminal device 110.
  • the network elements 102, 112 may be in communication with each other via one or more elements and/or interfaces (e.g. via WT 190 and Xw- interface 164).
  • the terminal device 110 may compute and populate a data packet to be transmitted with an identifier that is based on PLMN info and/or required service associated with the data packet.
  • Such data packet may be transmitted to the network element 112.
  • the required service may be one of split bearer 199A (i.e.
  • the data packet is intended to the network element 102 via the network element 112), local service 199C (i.e. provided by the second network) or local break-out 199B (e.g. some external network service via the second network).
  • the network element 112 may receive the data packet and determine where to route the data packet based on pre-configured mapping between the received service identifier (i.e. included in the data packet) and possible routing destinations (e.g. gateway 152, local server(s) 156, or cellular network (e.g. via WT 190)).
  • the data packet may be routed using routes 199A, 199B, or 199C, for example.
  • the AP 112 may receive a data packet wherein the identifier in said data packet indicates a service domain (e.g. local service such as printing, external network (e.g. Internet) or the cellular communication (possibly also a specific cellular network).
  • the AP 112 may then route the data packet to the correct service domain.
  • a service specific domain may be utilized to provide bidirectional communication between the terminal device 110 and the required service.
  • the terminal device 110 may communicate with the service specific domain (e.g. a specific gateway for the service domain in question).
  • the terminal device 110 deploys tunneling over the service domain.
  • also direct communication with a specific service may be possible. For this, as described above, instead of indicating only the service domain (i.e. outer address or outer header) both service domain and the specific service (i.e. inner address or inner header) are indicated. When only the outer header is indicated, the inner header (i.e. the specific service) may be concealed.
  • the identifier included in said data packet comprises a MAC address.
  • the MAC address in this context needs to be understood as an identifier made according to the MAC address structure or standards, wherein the identifier indicates the required service and/or the network amongst one or more networks (e.g. PLMN). Therefore, in an embodiment, the MAC address needs to be understood as an identifier generated according to the MAC address structure. However, it may not indicate a physical layer address as it is generally done with MAC addresses (e.g. there may be no need to indicate the WT 190 MAC address). In an embodiment, the MAC address is referred to as a modified MAC address.
  • said MAC address may denote more than one
  • the static part of the identifier may indicate the required service.
  • a dynamic part of the identifier e.g. the MAC address
  • the MAC address may be indicated with 48 bits comprising the static part (i.e. required service) 602 and possibly the dynamic part (i.e. PLMN or similar identifier) 604.
  • the first 24 bits of the MAC address may be used to indicate the required service and the last 24 bits of the MAC address may be used to indicate the first network identifier (e.g. PLMN).
  • the OUI 602 may denote Organizationally Unique Identifier 602.
  • Figure 6B illustrate an embodiment.
  • a Company ID (CID) 612 may also be used to indicate the required service.
  • CID 612 may also be used to indicate the required service.
  • rest of the 48 bits i.e. 24 bits
  • the first network identifier e.g. PLMN
  • the MAC address may comprise a MAC-L OUI comprising 24 bits.
  • 24 bits may remain in to indicate the PLMN if needed.
  • the MAC address may comprise a MAC-M OUI comprising 28 bits.
  • the 28 bits may be used to indicate the required service, for example.
  • the MAC address may comprise a MAC-S OUI comprising 36 bits.
  • the 36 bits may be used to indicate the required service, for example.
  • the first network identifier is indicated with using 20 or 12 bits only. It may be possible to utilize pre-known hash functions, and thus it may be possible to address specific PLMN with lesser bits than 24 bits. Thus, for example 20 bits may suffice for indicating said PLMN.
  • the MAC address of Figure 6B may be locally (i.e. within the local network) unique.
  • the MAC address of Figure 6A may be globally unique.
  • Locally administered MAC address may have bitl set to 1 and bitO set to 0 in its first octet.
  • Globally administered MAC address may have bitl set to 0 and bitO set to 0 in its first octet.
  • FIGS 7A to 7B illustrate some embodiments.
  • a data packet comprising Ethernet header 702, LWAAP header 704, PDCP PDU 706 and Cyclic Redundancy Check (CRC) 708 may be shown.
  • the Ethernet header 702 may comprise indication about the EtherType.
  • the EtherType may indicate LWA, meaning that the data packet is related to the LWA.
  • the Ethernet header 702 may indicate the required service utilizing, for example, one of the MAC addresses discussed with respect to Figures 6A to 6B.
  • the Ethernet header 702 may indicate whether the required service is cellular communication (e.g. UL LWA), local break-out, or local services of the second network (e.g. WLAN network).
  • the LWAAP header 704 may indicate Data Radio Bearer (DRB) ID, for example.
  • the PDU 706 may comprise PDCP header and Service Data Unit (SDU) i.e. payload of the data packet.
  • SDU Service Data Unit
  • the data packet may comprise the Ethernet header 702, IP datagram 712 and the CRC 708.
  • An IP datagram is a packet which uses IP protocol such as IPv4 or IPv6 and is composed by a header and payload part. I.e. the IP datagram 712 may depict the payload part comprising data.
  • the header 702 may the header of the data packet.
  • the header may comprise info on IP source/destination addresses, protocol, header checksum, and the like.
  • the PDCP SDU may be or comprise an IP datagram.
  • the data packet transmitted for instance in block 240, may be structured as the data packet in Figure 7A or 7B, for example.
  • the CRC 708 of Figure 7 A or 7B does not exists. This means that the data packet of Figure 7A or 7B does not comprise the shown CRC 708.
  • the data packet of Figure 7A or 7B utilizes a different checksum mechanism than the CRC 708.
  • the terminal device 110 transmits the data packet of block 408 directly to the network element 102 if the required service is a cellular communication service.
  • the required service is a cellular communication service.
  • this may be beneficial as there may not be need to specifically generate a data packet of the cellular communication system to be transmitted via the WLAN link or via the cellular link.
  • the same data packet in case of cellular communication service, may be transmitted via the WLAN link (AP 112) and/or via the direct cellular link (network element 102).
  • Terminal device and AP implementation may become simplified, i.e. pre-configured MAC address (i.e. MAC address of Figure 6A or 6B and particularly block 602 or block 612) is a firm indication that the data is supposed to go to the Xw interface and this eases implementation.
  • the AP does not need to be aware that there is WT behind as addressing may work solely based on preconfigured MAC addresses (i.e. MAC address of Figure 6A or 6B and particularly block 602 or block 612).
  • Same fixed MAC address could be used also for DL LWA as source MAC address, providing additional opportunities to recognize the LWA use in the device.
  • Figures 8 to 9 provide apparatuses 800, 900 comprising a control circuitry (CTRL) 810, 910, such as at least one processor, and at least one memory 830, 930 including a computer program code (software) 832, 932, wherein the at least one memory and the computer program code (software) 832, 932, are configured, with the at least one processor, to cause the respective apparatus 800, 900 to carry out any one of the embodiments of Figures 2 to 7B, or operations thereof.
  • CTRL control circuitry
  • the memory 830, 930 may be implemented using any suitable data storage technology, such as semiconductor based memory devices, flash memory, magnetic memory devices and systems, optical memory devices and systems, fixed memory and removable memory.
  • the memory 830, 930 may comprise a database 834, 934 for storing data.
  • the apparatuses 800, 900 may further comprise radio interface (TRX) 820, 920 comprising hardware and/or software for realizing communication connectivity according to one or more communication protocols.
  • the TRX may provide the apparatus with communication capabilities to access the radio access network, for example.
  • the TRX may comprise standard well-known components such as an amplifier, filter, frequency-converter, (de) modulator, and encoder/decoder circuitries and one or more antennas.
  • the TRX may realize communication by the terminal device 110 with the AP 112 and/or the network element 102.
  • the TRX may realize communication by the AP 112 with the terminal device 110 and/or with the WT 190.
  • TRX may enable the AP 112 to utilize the Xw-interface 164.
  • the apparatuses 800, 900 may comprise user interface 840, 940 comprising, for example, at least one keypad, a microphone, a touch display, a display, a speaker, etc.
  • the user interface 840, 940 may be used to control the respective apparatus by a user of the apparatus 800, 900.
  • the apparatus 800 may be or be comprised in a terminal device, such as a mobile phone or cellular phone, for example.
  • the apparatus 800 may be the terminal device 110, for example.
  • the apparatus 800 is comprised in the terminal device 110 or in some other terminal device. Further, the apparatus 800 may be the terminal device performing the steps of Figure 2, for example.
  • control circuitry 810 may comprise a data obtaining circuitry 812 obtaining configured to obtain a data packet to be transmitted; a service determining circuitry 814 configured to determine a required service associated with said data packet, wherein the required service is a service associated with the at least one first network or a service associated with the at least one second network; a identifier generating circuitry 816 configured to generate an identifier based at least on the required service; and a data transmitting circuitry 818 configured to transmitting said data packet including the generated identifier.
  • the apparatus 900 may be or be comprised in the
  • the apparatus 900 may be the network element 112, for example. Further, the apparatus 900 may be the network element performing the steps of Figure 3.
  • control circuitry 910 comprises a data receiving circuitry 912 configured to receive a data packet from a terminal device; a service determining circuitry 914 configured to determine a required service associated with said data packet based on an identifier included in said data packet, wherein the required service is a service associated with at least one first network or a service associated with at least one second network; and a routing circuitry 916 configured to initiate routing of said data packet to a first network amongst the at least one first network if the required service is the service associated with the at least one first network.
  • the apparatus 900 may be shared between two physically separate devices, forming one operational entity. Therefore, the apparatus may be considered to depict the operational entity comprising one or more physically separate devices for executing at least some of the above-described processes.
  • a SDN controller may be used to control AP 112, for example.
  • the SDN controller may configure routing rules to the AP 112, wherein the AP 112 may implement said rules for received data packets.
  • the AP 112 determines a data packet for which it does not have routing rules, it may communicate this to the SDN controller.
  • the SDN controller may respond with updated rules set, for example.
  • the first network(s) and second network(s) discussed with reference to Figures 2 and 3 may denote first type of network(s) and second type of network(s).
  • the first networks may be cellular networks and the second networks may be a WLANs.
  • a solution comprising: obtaining a data packet by the terminal device 110; determine required service associated with said data packet; determine a communication link amongst a plurality of communication links between the terminal device 110 and at least one other network element based at least on the required service and availability of the plurality of communication links; and transmit said data packet on the determined communication link.
  • the data packet may further indicate the required service and/or network identifier (e.g. PLMN), as discussed above.
  • PLMN network identifier
  • the terminal device 110 may determine based on the required service and the availability of the communication links which communication link to use.
  • the terminal device 110 may use the other.
  • circuitry refers to all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and/or digital circuitry, and (b) combinations of circuits and soft- ware (and/or firmware), such as (as applicable) : (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.
  • circuitry' applies to all uses of this term in this application.
  • the term 'circuitry' would also cover an implementation of merely a processor (or multiple processors) or a portion of a processor and its (or their) accompanying software and/or firmware.
  • the term 'circuitry' would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
  • At least some of the processes described in connection with Figures 2 to 7B may be carried out by an apparatus comprising corresponding means for carrying out at least some of the described processes.
  • Some example means for carrying out the processes may include at least one of the following: detector, processor (including dual-core and multiple-core processors), digital signal processor, controller, receiver, transmitter, encoder, decoder, memory, RAM, ROM, software, firmware, display, user interface, display circuitry, user interface circuitry, user interface software, display software, circuit, antenna, antenna circuitry, and circuitry.
  • the at least one processor, the memory, and the computer program code form processing means or comprises one or more computer program code portions for carrying out one or more operations according to any one of the embodiments of Figures 2 to 7B or operations thereof.
  • the apparatus carrying out the embodiments comprises a circuitry including at least one processor and at least one memory including computer program code. When activated, the circuitry causes the apparatus to perform at least some of the functionalities according to any one of the embodiments of Figures 2 to 7B, or operations thereof.
  • the techniques and methods described herein may be implemented by various means. For example, these techniques may be implemented in hardware (one or more devices), firmware (one or more devices), software (one or more modules), or combinations thereof.
  • the apparatus(es) of embodiments may be implemented within one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
  • ASICs application-specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGAs field programmable gate arrays
  • processors controllers, microcontrollers, microprocessors, other electronic units designed to perform the functions described herein, or a combination thereof.
  • the implementation can be carried out through modules of at least one chip set
  • the software codes may be stored in a memory unit and executed by processors.
  • the memory unit may be implemented within the processor or externally to the processor. In the latter case, it can be communicatively coupled to the processor via various means, as is known in the art.
  • the components of the systems described herein may be rearranged and/or complemented by additional components in order to facilitate the achievements of the various aspects, etc., described with regard thereto, and they are not limited to the precise configurations set forth in the given figures, as will be appreciated by one skilled in the art.
  • Embodiments as described may also be carried out in the form of a computer process defined by a computer program or portions thereof. Embodiments of the methods described in connection with Figures 2 to 7B may be carried out by executing at least one portion of a computer program comprising corresponding instructions.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • the computer program may be stored on a computer program distribution medium readable by a computer or a processor.
  • the computer program medium may be, for example but not limited to, a record medium, computer memory, read-only memory, electrical carrier signal, telecommunications signal, and software distribution package, for example.
  • the computer program medium may be a non-transitory medium, for example. Coding of software for carrying out the embodiments as shown and described is well within the scope of a person of ordinary skill in the art.
  • a computer-readable medium comprises said computer program.

Landscapes

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

Abstract

L'invention concerne un procédé comprenant les étapes suivantes : obtenir, par un dispositif terminal fonctionnant avec au moins un premier réseau et au moins un deuxième réseau, un paquet de données à transmettre ; déterminer un service requis associé audit paquet de données, le service requis étant un service associé audit premier réseau ou un service associé audit deuxième réseau ; produire un identifiant au moins en fonction du service requis ; et transmettre ledit paquet de données contenant l'identifiant produit.
PCT/FI2016/050678 2016-09-28 2016-09-28 Amélioration d'efficacité de communication WO2018060540A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/FI2016/050678 WO2018060540A1 (fr) 2016-09-28 2016-09-28 Amélioration d'efficacité de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/FI2016/050678 WO2018060540A1 (fr) 2016-09-28 2016-09-28 Amélioration d'efficacité de communication

Publications (1)

Publication Number Publication Date
WO2018060540A1 true WO2018060540A1 (fr) 2018-04-05

Family

ID=61759295

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/FI2016/050678 WO2018060540A1 (fr) 2016-09-28 2016-09-28 Amélioration d'efficacité de communication

Country Status (1)

Country Link
WO (1) WO2018060540A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110855677A (zh) * 2019-11-15 2020-02-28 北京小米移动软件有限公司 配网方法及装置、电子设备及存储介质

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009034071A2 (fr) * 2007-09-10 2009-03-19 Nokia Siemens Networks Oy Procédé, système radio et station de base
US20140369329A1 (en) * 2013-06-18 2014-12-18 Qualcomm Incorporated Lte and external wifi bandwidth aggregation
US20160036922A1 (en) * 2011-11-28 2016-02-04 Cisco Technology, Inc. System and method for extended wireless access gateway service provider wi-fi offload
US20160234752A1 (en) * 2015-02-05 2016-08-11 Mediatek Inc. Method and Apparatus of LWA PDU Routing
WO2016131493A1 (fr) * 2015-02-20 2016-08-25 Telefonaktiebolaget Lm Ericsson (Publ) Commande de réseau central de raccordement local pour un nuage distribué
WO2016148626A1 (fr) * 2015-03-13 2016-09-22 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil permettant une agrégation de trafic établie entre un réseau wlan et un réseau 3 gpp

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009034071A2 (fr) * 2007-09-10 2009-03-19 Nokia Siemens Networks Oy Procédé, système radio et station de base
US20160036922A1 (en) * 2011-11-28 2016-02-04 Cisco Technology, Inc. System and method for extended wireless access gateway service provider wi-fi offload
US20140369329A1 (en) * 2013-06-18 2014-12-18 Qualcomm Incorporated Lte and external wifi bandwidth aggregation
US20160234752A1 (en) * 2015-02-05 2016-08-11 Mediatek Inc. Method and Apparatus of LWA PDU Routing
WO2016131493A1 (fr) * 2015-02-20 2016-08-25 Telefonaktiebolaget Lm Ericsson (Publ) Commande de réseau central de raccordement local pour un nuage distribué
WO2016148626A1 (fr) * 2015-03-13 2016-09-22 Telefonaktiebolaget Lm Ericsson (Publ) Procédé et appareil permettant une agrégation de trafic établie entre un réseau wlan et un réseau 3 gpp

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110855677A (zh) * 2019-11-15 2020-02-28 北京小米移动软件有限公司 配网方法及装置、电子设备及存储介质

Similar Documents

Publication Publication Date Title
US11516733B2 (en) Connectivity to a local area network via a cellular radio access technology
US10855814B2 (en) Non-access stratum capability information
CN112995977B (zh) 一种接入目标小区的方法以及设备
US11026276B2 (en) Inter-PGW handover architecture
US10993135B2 (en) SSID to QCI mapping
US11129240B2 (en) 5G interoperability architecture
EP3213580B1 (fr) Procédé et appareil de routage lwa de pdu
CA2973048C (fr) Communication de reseau local ponte entre un dispositif et un noeud de reseau d'acces cellulaire
US20150078167A1 (en) Systems and Methods for Providing LTE-Based Backhaul
JP2018534854A (ja) 発展型マシンタイプ通信をもつデバイスツーデバイス通信のためのシステムおよび方法
KR20130129869A (ko) 고정 광대역 액세스 네트워크를 통한 3ｇｐｐ 디바이스 및 고정 디바이스 베어러 트랜스포트를 위한 공존 지원
EP3257214B1 (fr) Connexions de protocole de commande de transmission multi-chemin
US10841834B2 (en) Legacy network maximum transmission unit isolation capability through deployment of a flexible maximum transmission unit packet core design
US10939485B2 (en) Mechanism for realizing LWA/LWIP aggregator function
US11632812B2 (en) Inter-PGW handover architecture
WO2018060540A1 (fr) Amélioration d'efficacité de communication

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: 16917591

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: 16917591

Country of ref document: EP

Kind code of ref document: A1