Abstract
The invention relates to a method for establishing a connectionless bearer service and a method for forwarding data packets in a connectionless bearer service. The data packet has a virtual access network identifier in the header data. The virtual access network identifier defines a unique data path from a source to a destination of the data packet and vice versa. The invention further relates to a network node for forwarding data packets based on a virtual access network identifier received with the data packets and by using a forwarding table for forwarding the data packets.
Claims
1. Method for establishing a connectionless bearer service, the method comprising: transmitting a data packet comprising user data and header data, the header data comprising at least a virtual access network identifier, wherein the virtual access network identifier is a unique identifier defining a unique virtual access network for the connectionless bearer service, the virtual access network defining a unique data path from a source to a destination of the data packet and vice versa.
2. Method for establishing a connectionless bearer service according to claim 1, wherein the virtual access network defined by the virtual access network identifier has a tree topology.
3. Method for establishing a connectionless bearer service according to claim 1, wherein the header data further comprises an access destination address, wherein the access destination address is a unique identifier of a destination of the data packet.
4. Method for establishing a connectionless bearer service according to claim 1, wherein the header data further comprises an access source address, wherein the access source address is a unique identifier of a source of the data packet.
5. Method for establishing a connectionless bearer service according to claim 1, wherein different virtual access network identifiers are assigned to different services used by the same device.
6. Method for forwarding data packets in a connectionless bearer service, the method comprising: forwarding a data packet comprising user data and header data, the header data comprising at least a virtual access network identifier, wherein the virtual access network identifier is a unique identifier extending across virtual networks and defines a unique virtual access network for the connectionless bearer service, the virtual access network defining a unique data path from a source to a destination of the data packet and vice versa.
7. Method for forwarding data packets in a connectionless bearer service according to claim 6, wherein the virtual access network defined by the virtual access network identifier has a tree topology and the method further comprises: forwarding by a network node a data packet sent by a User Equipment to the virtual access network to the neighbouring network node one level higher in the hierarchy of the virtual access network tree structure; and providing by the network node a forwarding table in which the network node one level lower in the hierarchy of the virtual access network from which the data packets was received and a source address of the data packet is stored.
8. Method for forwarding data packets in a connectionless bearer service according to claim 7, further comprising: forwarding by a network node a data packet to a neighbouring network node one level lower in the hierarchy of the virtual access network according to the forwarding table of the network node.
9. Method for forwarding data packets in a connectionless bearer service according to claim 6, wherein the header data further comprises an access destination address, wherein the access destination address is a unique identifier of a address of the data packet and the header data further comprises an access source address, wherein the access source address is a unique identifier of a source of the data packet.
10. Method for forwarding data packets in a connectionless bearer service according to claim 7, wherein the forwarding tables in the network nodes and the virtual access network identifiers define a connectionless tunnel protocol for forwarding data packets from a source to a destination.
11. Network node for forwarding data packets in a connectionless bearer service, wherein the network node performs a method according to claim 1.
12. Network node for forwarding data packets in a connectionless bearer service, the network node comprising: a receiver for receiving a data packet comprising user data and header data, the header data comprising at least a virtual access network identifier, wherein the virtual access network identifier is a unique identifier extending across virtual networks and defining a unique virtual access network for the connectionless bearer service, the virtual access network defining a unique data path from a source to a destination of the data packet and vice versa; a source address analyser for analysing the source of a data packet according to the header data of the data packet; a memory configured to store a forwarding table, the forwarding table indicating the network node one level lower in the hierarchy of the virtual access network from which the data packet was received and a source address of the data packet; and a transmitter for sending a data packet to a network node one level lower in hierarchy of the virtual access network according to the information stored in the forwarding table.
13. User Equipment for establishing a connectionless bearer service, wherein the user equipment performs a method according to claim 1.
14. Virtual access network comprising: at least one source endpoint; at least one sink endpoint; and at least one network node in the network path between the source endpoint and the sink endpoint, wherein the virtual access network is a network slice of a physical radio access network; and wherein the virtual access network has a tree structure; and is allocated to a dedicated service; and wherein the at least one network node is a network node according to claim 12.
Description
BRIEF DESCRIPTION OF THE DRAWINGS
[0025] Some embodiments of apparatus and methods in accordance with embodiments of the present invention are now described, by way of examples only, and with reference to the accompanying drawings, in which:
[0026] FIG. 1 schematically depicts a wireless network architecture;
[0027] FIG. 2 depicts a schematic overview of a connection oriented bearer service;
[0028] FIG. 3 schematically depicts a data packet according to an embodiment of the invention;
[0029] FIG. 4 depicts a schematic overview of a network according to an embodiment of the invention;
[0030] FIG. 5 depicts a method for forwarding data packets according to an embodiment of the invention;
[0031] FIG. 6 depicts a schematic overview of a connectionless bearer service according to an embodiment of the invention;
[0032] FIG. 7 depicts a schematic overview of a connectionless bearer service according to an embodiment of the invention;
[0033] FIG. 8 depicts a schematic overview of a connectionless bearer service according to an embodiment of the invention; and
[0034] FIG. 9 schematically depicts a network node that may be used in embodiments of the invention.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[0035] The description and drawings merely illustrate the principles of the invention. It will thus be appreciated that those skilled in the art will be able to devise various arrangements that, although not explicitly described or shown herein, embody the principles of the invention and are included within its spirit and scope. Furthermore, all examples recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventors to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass equivalents thereof.
[0036] FIG. 1 schematically depicts an architecture for a wireless network, e.g. a 4G or a future 5G network. A User Equipment 1 communicates to a base station, e.g. an eNodeB 2. A communication direction from User Equipment 1 to base station, e.g. eNodeB 2, may be referred to as upstream. A communication direction from base station, e.g. eNodeB 2, to User Equipment 1 may be referred to as downstream. User Equipment 1 and eNodeB 2 belong to the Evolved Universal Mobile Telecommunication System Terrestrial Radio Access Network (E-UTRAN). The eNodeB 2 is connected to a Serving Gateway (S-GW) 3. The Serving Gateway 3 is connected to a Packet Data Network Gateway (P-GW) 4, which provides access to the external network 5, e.g. the Internet.
[0037] FIG. 2 depicts a schematic view of a connection oriented bearer service. An end-to-end connection between a User Equipment 1 and an external network 5 is depicted as end-to-end bearer 21. It is provided by an Evolved Packet Switched System bearer (EPS-bearer) 22 and an external bearer 23 providing connection to an external network 5, e.g. the Internet. An EPS-bearer 22 uniquely identifies traffic flows that receive a common Quality of Service (QoS) treatment between a User Equipment 1 and a Packet Data Network Gateway (P-GW) 4. The EPS-Bearer 22 is a virtual connection between the User Equipment 1 and the Packet Date Network Gateway 4, which identifies data sent and received between these two end points with specific QoS attributes, e.g QCI, GBR, Allocation Retention Priority. The Evolved UTRAN Radio Access Bearer (e-RAB) 24 transports the packet of an EPS-Bearer 22 between the User Equipment 1 and the Serving Gateway (S-GW) 3. The S5/S8 Bearer 25 transports the packets of an EPS bearer 22 between the Serving Gateway 3 and the Packet Data Network Gateway 4. The Radio Bearer 26 transports packet of an E-RAB 24 between the User Equipment 1 and the eNodeB 2. An S1 Bearer 27 transports the packets of an E-RAB 24 between the eNodeB 2 and the Serving Gateway 3. Packet exchange between the User Equipment 1 and the external network 5 are assigned to one or more EPS-Bearer 22 by means of Traffic Flow Templates (TFT) Defining Service Data Flows (SDF). The Radio Bearer 26, S1 Bearer 27 and S5/S8 Bearer 25 are bound together by switching tables. The switching tables thus providing a connection oriented connection.
[0038] FIG. 3 schematically depicts a message format for a data packet 30 to be transmitted with a connectionless tunnelling protocol CLTP according to an embodiment of the invention. The data packet 30 being formed includes payload data 31, also referred to as user data, and header data. The header data includes header data as known in the art which is necessary for data transmission, e.g. checksum data, flags, etc. and which are not described in further detail.
[0039] Further, the data packet 30 contains a virtual access network identifier 32. The virtual access network identifier 32 is a unique identifier extending across physical networks and defining a unique virtual access network for the connectionless bearer service. A unique virtual access network is described in more detail with regard to the figures below.
[0040] Further, the data packet 30 contains an access source address 33. The access source address 33 is an identifier of the origin of the data packet. Preferably, the access source address 33 is a unique source address identifying the source device from which the data packet 30 originates. In upstream communication, the source device of a data packet 30 is e.g. a User Equipment 1. In downstream communication, the source device of a data packet 30 is e.g. a Packet Data Network Gateway 4.
[0041] Further, the data packet 30 contains an access destination address 34. The access destination address 34 is an identifier of the destination of the data packet 30. Preferably, the access destination address 34 is a unique destination address identifying the destination device to which the data packet is to be sent. In upstream communication, the destination device of a data packet 30 is e.g. Packet Data Network Gateway 4. In downstream communication, the destination device of a data packet 30 is e.g. a User Equipment 1.
[0042] Preferably, both access source address 33 and access destination address 34 are unique addresses. This means, each access source address 33 and each access destination address 34 is assigned to a concrete device even when considering multiple networks, including neighbouring networks. This way, it is assured that one access source address 33 or one access destination address 34 is not assigned to two devices in different physical networks and the addresses allow therefore a distinct identification of the source and destination device, respectively.
[0043] FIG. 4 schematically depicts a wireless network scenario 40 according to an embodiment of the invention. For sake of simplicity, only a few network elements are shown. Wireless access is provided to User Equipments 42, e.g. by an LTE or 5G network. The User Equipments 42 are connected to a external networks 50, e.g. the Internet including servers, cloud like infrastructure and other network devices 50. The User Equipments 42 connect to respective base stations 44, e.g. eNodeBs by a Radio Access link 43a, 43b, 43c, which provides a wireless connection. The base stations 44 are connected to Serving Gateways 46 by corresponding network links 45a, 45b, 45c. The Serving Gateways 46 are connected to Packet Data Network Gateways 48 by corresponding network links 47a, 47b, 47c. The Packet Data Network Gateways 48 are connected to the external networks 50, e.g. by an external bearer. Multiple links 49 to the external networks 50 are available. The external networks 50 are e.g. the Internet, Operator Networks and Private Networks based on IP technology and devices of the external network 50 are e.g. servers and cloud devices. The path on which data packets 30 are sent through the network is defined by the virtual access network identifier (vACC-ID) 32. The virtual access network defined by the virtual access network identifier 32 is to be understood as a network, e.g. a hierarchical network having a tree structure connecting a source and a sink, i.e. a network node which is the destination of a data packet 30 transmitted. In FIG. 4, in the upstream, a source of a data packet 30 is a User Equipment 42 and a sink of the data packet 30 is a Packet Data Network Gateway 48, which provides connection to the external networks 50. In the downstream, a source of a data packet 30 is a Packet Data Network Gateway 48 and a sink of the data packet 30 is a User Equipment 42. The Packet Data Network Gateway 48 identifies by means of the destination address of the IP packet and in general by the traffic flow template (TFT) on which virtual access network a data packet is to be sent and assigns a virtual access network identifier 32. The source is identified in the data packet 30 by an access source address 33. The sink of a data packet 30, i.e. the destination of a data packet 30 is identified by its access destination address 34. The access source address 33 and the access destination address 34 are unique addresses also when exceeding a virtual access network. Thus, the access source address 33 and the access destination address 34 are unique addresses when considering the radio access network, e.g. an LTE or 5G network. The virtual access network contains only networks elements 42, 44, 46, 48 between the source and the destination of a data packet 30 transmitted. No multiple paths are possible from a source to a sink in the virtual access network. In other words, the virtual access network defines a unique data path from the source to the sink and vice versa. The virtual access network is composed of a subset of all network nodes of the network. FIG. 4 depicts three virtual access networks. The first one contains links 43a, 45a, 47a, 49a. The links of the first virtual access network are depicted by solid lines and the tree structure is shown. The second virtual access network contains links 43b, 45b, 47b, 49b. The links of the second virtual access network are depicted by dashed lines and the tree structure is shown. The third virtual access network contains links 43c, 45c, 47c, 49c. The links of the third virtual access network are depicted by crossed lines and the tree structure is shown.
[0044] In a network having a tree structure, receiving data packets and subsequently forwarding the received data packets in the upstream path from the User Equipment 42 to the network 51 is distinct. At each network node, due to the tree structure, only one data path is available to a network node one level higher in hierarchy. In contrast, in the downstream path from the network 51 to the User Equipment 42, at each network node a decision has to be made on which link the data packet 30 that is received by the network node is forwarded in order to provide it to the right receiving User Equipment 42. This decision is made based on a forwarding table, which is generated in the upstream path as described below.
[0045] FIG. 5 schematically depicts a method for forwarding data packets in a connectionless bearer service between a User Equipment 42 and a Packet Data Network Gateway 48, which is connected to an external network 50 and for forwarding data packet between the Packet Data Network Gateway 48 and the User Equipment 42. A data packet 30 originating from a User Equipment 42 is received 52 in a network node 44, 46, 48. The data packet 30 comprises a virtual access network identifier 32 describing a virtual access network 43a, 45a, 47a, 49a; 43b, 45b, 47b, 49b; 43c, 45c, 47c, 49c. The data packet further comprises an access source address 33 and an access destination address 34. In step 53, the virtual access network identifier 32, the virtual access source address 33 and the virtual access destination address 34 are extracted from the data packet 30. In step 54, a forwarding table is established in the network node 44, 46, 48 or if the forwarding table already exists in the network node 44, 46, 48, a new data entry is added to the forwarding table. The forwarding table is dedicated to at least one virtual access network which is identified by the virtual access network identifier 32. The forwarding table at least contains information about the source address 33 from which a data packet 30 originates in the upstream, which is the destination address of downstream data packets. Further, the forwarding table at least contains a corresponding logical link (port) on which the data packet 30 has been received, which is the link on which downstream data packets will be sent if they have the corresponding destination address. This information is tied to a virtual access network and hence associated to a corresponding virtual access network identifier 32. In one embodiment, for each virtual access network a forwarding table is established in a network node 44, 46, 48 including the virtual access network identifier 32, the address information and the link information as described above. In one embodiment, only one forwarding table is generated in a network node 44, 46, 48 including the above mentioned information for all virtual access networks which are present in the network node 44, 46, 48. In step 55, a data packet 30 is forwarded upstream to a network node 44, 46, 48 one level higher in hierarchy. In step 56, a data packet 30 is received from a network node 44, 46, 48 one level higher in hierarchy. The access destination address 34 of the data packet 30 is extracted in step 57. In step 58, preferably by using the virtual access network identifier, it is determined if this access destination address 34 is available in a forwarding table of a virtual access network of the network node 44, 46, 48. If the access destination address 34 is available in the forwarding table of the network node 44, 46, 48, the corresponding link is determined and the data packet 30 is forwarded on this link in step 59. If the access destination address 34 is not available, the data packet 30 is broadcast to all links in the direction to network nodes 44, 46, 48 on a lower hierarchy level. This way, it is ensured that the data packet 30 is provided to the right link, even if it is also provided to links which would not be necessary. This enhances data traffic only for the exceptional case, as in most cases the link would be available in the forwarding table of a network node 44, 46, 48 due to previous uplink communication. Each network node 44, 46, 48 between a source and a sink of a virtual access network establishes and manages a forwarding table as described above. As each virtual access network is organized as a tree structure and no loops are present, upstream communication is easily possible within the virtual access network just by forwarding a data packet 30 to the corresponding network node 44, 46, 48 in the same virtual access network one hierarchy higher, and at the same time a forwarding table is generated for downstream forwarding in the virtual access network. According to one embodiment, the forwarding information which was not used for a certain time is deleted from the forwarding table, as it can be assumed that this link is not further used in the next future. The information is again included in the forwarding table, if a further corresponding upstream request is received at the corresponding network node 44, 46, 48.
[0046] FIG. 6 depicts a schematic view on a connectionless bearer service. An end-to-end connection between a User Equipment 1 and sink in the external network 5 is depicted as end-to-end bearer 21. It is provided by an Evolved Packet switched System bearer (EPS-bearer) 22 and an external bearer 23 providing connection to an external network 5, e.g. the Internet. An EPS-bearer 22 uniquely identifies traffic flows that receive a common Quality of Service (QoS) treatment between a User Equipment 1 and a Packet Data Network Gateway 4. The EPS-Bearer 22 is a virtual connection between the User Equipment 1 and the Packet Date Network Gateway 4, which identifies data sent and received between these two end points with specific QoS attributes, e.g QCI, GBR, Allocation Retention Priority. This corresponds to the connection oriented bearer service as described with regard to FIG. 2. Further, in FIG. 6 a connectionless bearer 61 is illustrated which is based on a connectionless tunnel protocol. According to the connectionless tunnel protocol, data packets 30 are forwarded from the User Equipment 1 to the Packet Data Network Gateway 4. From there, the data packets 30 are forwarded to the external network, e.g. the Internet.
[0047] FIG. 7 illustrates a further embodiment of a connectionless bearer service. The radio bearer 26 between User Equipment 1 and the base station 2 is realized as known in the art, i.e. with a 4G or 5G connection oriented radio link. A connectionless tunnel protocol as described above provides a connectionless bearer 71 between the base station 2 and the Packet Data Network Gateway 4.
[0048] FIG. 8 illustrates a further embodiment of a connectionless bearer service. A connectionless tunnel protocol provides a connectionless bearer 81 between the User Equipment 1 and the Serving Gateway 3. The data packets 30 are then transported by the S5/S8 Bearer 25 of an EPS bearer 22 between the Serving Gateway 3 and the Packet Data Network Gateway 4.
[0049] FIG. 9 schematically depicts a network node 80 that may be used in embodiments of the invention. The network node 80 is configured to forward data packets in a connectionless bearer service. The network node 80 comprises a receiver 81, a source address analyser 83, a memory 85 and a transmitter 87.
[0050] The receiver 81 is configured to receive a data packet, the data packet comprising user data and header data as described above with respect to data packet 30. The header data thus comprises at least a virtual access network identifier, wherein the virtual access network identifier is a unique identifier extending across virtual networks and defines a unique virtual access network for the connectionless bearer service. The virtual access network defines a unique data path from a source to a destination of the data packet and vice versa.
[0051] The source address analyser 83 is configured for analysing the source of a data packet according to the header data of the data packet, the source being upstream from the network node 80. The source address analyser 83 may take the form of a processor or may be part thereof. Such processor may be a single dedicated processor, a single shared processor, a plurality of individual processors, some of which may be shared, or may be realized with hardware logic optimized for the purposes of embodiments of the invention.
[0052] The memory 85 is configured to store a forwarding table. The forwarding table indicates the network node a received data packet shall be forwarded to. For downstream packets the forwarding table indicates the network node one level lower in the hierarchy of the virtual access network from which a data packet with a certain source address was received. The forwarding table is indexed by source addresses of data packets received in upstream.
[0053] A transmitter 87 configured to send a data packet to a network node one level lower in hierarchy of the virtual access network does this according to the information stored in the forwarding table. A transmitter 87 configured to send a data packet upstream just forwards packets received from any receiver configured to receive upstream data packets. For this it might use a default entry in the forwarding table.
[0054] The functions of the various elements shown in the Figures, including any functional blocks, may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, the functions may be provided, without limitation, by digital signal processor (DSP) hardware, network processor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), read only memory (ROM) for storing software, random access memory (RAM), and non volatile storage. Other hardware, conventional and/or custom, may also be included.
