encapsulating SCTP packets in UDP packets

Abstract

A method for enabling an SCTP packet to be encapsulated in a UDP packet is provided, the method being performed by a source network node. The method comprises the steps of: obtaining a source number based on an identifier of the source network node; obtaining a destination number based on an identifier of a destination network node; generating an SCTP packet comprising: setting a source port of the SCTP packet to a predefined port number and setting a destination port of the SCTP packet to the destination number; generating a UDP packet comprising: setting a source port of the UDP packet to the source number and setting a destination port of the UDP packet to the destination number; encapsulating the SCTP packet in the UDP packet; and sending the UDP packet for transmission to the destination network node.

Description

[0001] This application is a divisional application of Chinese invention patent application entitled "Encapsulating SCTP packets in UDP packets" (application number 202180096297.4, application date March 26, 2021). Technical Field

[0002] This disclosure relates to the field of network communications, and in particular to enabling Stream Control Transmission Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. Background Technology

[0003] The development of cellular networks requires support for many different communication paths. One such communication path is peer-to-peer communication between network nodes.

[0004] In LTE (Long Term Evolution) networks, peer-to-peer communication between network nodes occurs on the so-called X2 interface, while in 5G (Fifth Generation) networks, peer-to-peer communication occurs on the so-called Xn interface. Both the X2 and Xn interfaces rely on the Flow Control Transfer Protocol (SCTP) based on the Internet Protocol (IP) for communication. Therefore, each network node also needs its own IP address. However, the number of IP addresses is finite, and any reduction in the number of public IP addresses would be highly beneficial. Summary of the Invention

[0005] One objective is to provide a solution that enables SCTP communication from the source network node to the destination network node when at least one of the source network node and the destination network node is behind a network address translation device.

[0006] According to a first aspect, a system is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. The system includes a source network node, a source adapter, and a destination adapter. The source network node includes: a processor; and a memory storing instructions that, when executed by the processor, cause the source network node to: obtain a source number based on an identifier of the source network node; obtain a destination number based on an identifier of the destination network node; generate an SCTP packet, including: setting the source port of the SCTP packet to a predefined port number and setting the destination port of the SCTP packet to the destination number; generate a UDP packet, including: setting the source port of the UDP packet to the source number and setting the destination port of the UDP packet to the destination number; encapsulate the SCTP packet in a UDP packet; and send the UDP packet for transmission to the destination network node. The source adapter includes: a processor; and a memory storing instructions that, when executed by the processor, cause the source adapter to: receive a UDP packet encapsulating an SCTP packet; set the destination port of the SCTP packet to the same port number as the source port of the SCTP packet; and send the UDP packet for transmission to the destination network node. The destination adapter includes: a processor; and a memory storing instructions that, when executed by the processor, cause the destination adapter to: receive a UDP packet encapsulating an SCTP packet; set the source port in the SCTP packet to be the same as the source port of the received UDP packet; and send the UDP packet for transmission to the destination network node.

[0007] According to a second aspect, a method is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node, the method being performed by the source network node. The method includes the following steps: obtaining a source number based on an identifier of the source network node; obtaining a destination number based on an identifier of the destination network node; generating an SCTP packet, comprising: setting the source port of the SCTP packet to a predefined port number and setting the destination port of the SCTP packet to the destination number; generating a UDP packet, comprising: setting the source port of the UDP packet to the source number and setting the destination port of the UDP packet to the destination number; encapsulating the SCTP packet in a UDP packet; and sending the UDP packet for transmission to the destination network node.

[0008] The identifier of the destination network node can be a base station identifier, and the identifier of the source network node can also be a base station identifier.

[0009] The steps to obtain the source number may include: calculating a hash value within a sixteen-bit range based on the identifier of the source network node; and the steps to obtain the destination number may include: calculating a hash value within a sixteen-bit range based on the identifier of the destination network node.

[0010] The steps to obtain the source number may include: querying the central node for the source number based on the identifier of the source network node; and the steps to obtain the destination number may include: querying the central node for the destination number based on the identifier of the destination network node.

[0011] Predefined port numbers can be assigned numbers for peer-to-peer communication between network nodes.

[0012] Predefined port numbers can be assigned for SCTP-based 3GPP X2 or Xn communications.

[0013] The method may further include the following steps: reading an information element indicating that the destination node supports distinguishing base stations within the site, wherein the information element is configured for self-organizing network configuration.

[0014] According to a third aspect, a source network node is provided for enabling Flow Control Transfer Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from the source network node to a destination network node. The source network node includes: a processor; and a memory storing instructions that, when executed by the processor, cause the source network node to: obtain a source number based on an identifier of the source network node; obtain a destination number based on an identifier of the destination network node; generate an SCTP packet, including: setting the source port of the SCTP packet to a predefined port number and setting the destination port of the SCTP packet to the destination number; generate a UDP packet, including: setting the source port of the UDP packet to the source number and setting the destination port of the UDP packet to the destination number; encapsulate the SCTP packet in a UDP packet; and send the UDP packet for transmission to the destination network node.

[0015] The identifier of the destination network node can be a base station identifier, and the identifier of the source network node can also be a base station identifier.

[0016] Instructions for obtaining the source number may include instructions that, when executed by the processor, cause the source network node to perform the following operation: calculate a hash value within a sixteen-bit range based on the identifier of the source network node; and instructions for obtaining the destination number may include instructions that, when executed by the processor, cause the source network node to perform the following operation: calculate a hash value within a sixteen-bit range based on the identifier of the destination network node.

[0017] Instructions for obtaining a source number may include instructions that, when executed by the processor, cause the source network node to perform the following operation: query the central node for a source number based on the identifier of the source network node; and instructions for obtaining a destination number may include instructions that, when executed by the processor, cause the source network node to perform the following operation: query the central node for a destination number based on the identifier of the destination network node.

[0018] Predefined port numbers can be assigned numbers for peer-to-peer communication between network nodes.

[0019] Predefined port numbers can be assigned for SCTP-based 3GPP X2 or Xn communications.

[0020] The source network may further include instructions that, when executed by the processor, cause the source network node to perform the following operations: read information elements that indicate to the destination node that it supports distinguishing base stations within the site, wherein the information elements are configured for self-organizing network configuration.

[0021] According to a fourth aspect, a computer program is provided for enabling Flow Control Transfer Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. The computer program includes computer program code that, when executed on the source network node, causes the source network node to: obtain a source number based on an identifier of the source network node; obtain a destination number based on an identifier of the destination network node; generate an SCTP packet, comprising: setting the source port of the SCTP packet to a predefined port number and setting the destination port of the SCTP packet to the destination number; generate a UDP packet, comprising: setting the source port of the UDP packet to the source number and setting the destination port of the UDP packet to the destination number; encapsulate the SCTP packet in a UDP packet; and send the UDP packet for transmission to the destination network node.

[0022] According to a fifth aspect, a computer program product is provided, comprising the computer program described in the fourth aspect and a computer-readable component having the computer program stored thereon.

[0023] According to a sixth aspect, a method is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node, the method being performed by a source adapter. The method includes the steps of: receiving a UDP packet encapsulating an SCTP packet; setting the destination port of the SCTP packet to the same port number as the source port of the SCTP packet; and sending the UDP packet for transmission to the destination network node.

[0024] Predefined port numbers can be assigned for SCTP-based 3GPP X2 or Xn communications.

[0025] According to a seventh aspect, a source adapter is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. The source adapter includes: a processor; and a memory storing instructions that, when executed by the processor, cause the source adapter to: receive a UDP packet encapsulating an SCTP packet; set the destination port of the SCTP packet to the same port number as the source port of the SCTP packet; and send the UDP packet for transmission to the destination network node.

[0026] Predefined port numbers can be assigned for SCTP-based 3GPP X2 or Xn communications.

[0027] According to an eighth aspect, a computer program is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. The computer program includes computer program code that, when executed on a source adapter, causes the source adapter to: receive the UDP packet encapsulating the SCTP packet; set the destination port of the SCTP packet to the same port number as the source port of the SCTP packet; and send the UDP packet for transmission to the destination network node.

[0028] According to a ninth aspect, a computer program product is provided, comprising the computer program described in the eighth aspect and a computer-readable component having the computer program stored thereon.

[0029] According to a tenth aspect, a method is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node, the method being performed by a destination adapter. The method includes the steps of: receiving a UDP packet encapsulating an SCTP packet; setting the source port in the SCTP packet to be the same as the source port of the received UDP packet; and sending the UDP packet for transmission to the destination network node.

[0030] According to the eleventh aspect, a destination adapter is provided for enabling Flow Control Transport Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. The destination adapter includes: a processor; and a memory storing instructions that, when executed by the processor, cause the destination adapter to: receive a UDP packet encapsulating an SCTP packet; set the source port in the SCTP packet to be the same as the source port of the received UDP packet; and send the UDP packet for transmission to the destination network node.

[0031] According to a twelfth aspect, a computer program is provided for enabling Flow Control Transfer Protocol (SCTP) packets to be encapsulated in User Datagram Protocol (UDP) packets for transmission from a source network node to a destination network node. The computer program includes computer program code that, when executed on a destination adapter, causes the destination adapter to: receive a UDP packet encapsulating an SCTP packet; set the source port in the SCTP packet to be the same as the source port of the received UDP packet; and send the UDP packet for transmission to the destination network node.

[0032] According to the thirteenth aspect, a computer program product is provided, comprising the computer program described in the twelfth aspect and a computer-readable component having the computer program stored thereon.

[0033] Generally, unless otherwise expressly defined herein, all terms used in the claims shall be interpreted according to their ordinary meaning in the art. Unless otherwise expressly stated, all references to “a / an / the element, device, component, part, step, etc.” shall be openly interpreted as referring to at least one instance of that element, device, component, part, step, etc. Unless expressly stated otherwise, the steps of any method disclosed herein need not be performed in the exact order disclosed. Attached Figure Description

[0034] Aspects and embodiments will now be described by way of example with reference to the accompanying drawings, wherein:

[0035] Figure 1 This is a schematic diagram illustrating an environment in which the embodiments provided herein can be implemented;

[0036] Figure 2 It shows that it is encapsulated in a way that can be used Figure 1 A diagram illustrating SCTP packets within UDP packets of IP packets in an environment;

[0037] Figure 3 It is shown Figure 2 The grouping of structures in Figure 1 A schematic diagram illustrating the evolution of various parameters in the environment;

[0038] Figure 4A -B is a flowchart illustrating an embodiment of a method performed in a source network node to enable SCTP packets to be encapsulated in UDP packets for transmission from the source network node to the destination network node;

[0039] Figure 5 This is a flowchart illustrating an embodiment of a method performed in a source adapter to enable SCTP packets to be encapsulated in UDP packets for transmission from a source network node to a destination network node;

[0040] Figure 6 This is a flowchart illustrating an embodiment of a method performed in a source adapter to enable SCTP packets to be encapsulated in UDP packets for transmission from a source network node to a destination network node;

[0041] Figure 7 This illustrates an embodiment. Figure 1 A schematic diagram of the components of each of the source network node, source adapter, and destination adapter;

[0042] Figure 8 This illustrates an embodiment. Figure 1 A schematic diagram of the functional modules of the source network node;

[0043] Figure 9 This illustrates an embodiment. Figure 1 A schematic diagram of the functional modules of the source adapter;

[0044] Figure 10 This illustrates an embodiment. Figure 1 A schematic diagram of the functional modules of the destination adapter; and

[0045] Figure 11 An example of a computer program product that includes computer-readable components is shown. Detailed Implementation

[0046] Various aspects of this disclosure will now be described more fully below with reference to the accompanying drawings, in which certain embodiments of the invention are illustrated. However, these aspects may be embodied in many different forms and should not be construed as limiting; rather, these embodiments are provided by way of example so that this disclosure will be thorough and complete, and will fully convey the scope of all aspects of the invention to those skilled in the art. Throughout the description, the same numerals refer to the same elements.

[0047] Figure 1This is a schematic diagram illustrating an environment in which the embodiments provided herein can be implemented. Cellular network 9 includes a core network 3 in a central site 5. Central site 5 may optionally include an additional central node 7, which may optionally be part of the core network 3. Central node 7 may be implemented as a server. Core network 3 provides central functions and connectivity to wide area networks (such as the Internet).

[0048] exist Figure 1 In the example shown, there is peer-to-peer communication from source site 5a to destination site 5b, indicated by the dashed arrow. It should be noted that whenever the terms source and destination are used herein, these terms are used to describe specific communication in that direction. However, at subsequent points in time, or even simultaneously, communication in the opposite direction may exist between the same or other nodes. In other words, the terms source and destination are interchangeable, depending on the direction of communication for each specific instance.

[0049] Central site 5 is located in the center so that both source site 5a and destination site 5b can access central site 5.

[0050] At source site 5a, there are a first source network node 1a, a second source network node 1b, and a third source network node. At destination site 5b, there are a first destination network node 2a and a second destination network node 2b. The embodiments provided herein facilitate communication from source network nodes to destination network nodes (and vice versa) based on 3GPP-compliant SCTP.

[0051] The source site 5a, the destination site 5b, and the central site 5 are all connected via the transmission network 6, which is an Internet Protocol (IP) based network.

[0052] To conserve IP address space, source site 5a uses a first Network Address Translation (NAT) 4a, as is known in the art. NAT translates, for example, based on port numbers, the local IP addresses (of source network nodes 1a-c) to public IP addresses used on transport network 6, and vice versa, thereby enabling correct routing of IP packets to and from source network nodes 1a-c. Similarly, destination site 5b uses a second Network Address Translation (NAT) 4b. Using NATs 4a and 4b, network nodes at each site can share a single IP address (per site) destined for transport network 6.

[0053] According to the embodiments provided herein, a source adapter 8a also exists at the source site 5a, and a destination adapter 8b also exists at the destination site 5b. The source adapter 8a and the destination adapter 8b are functional modules and do not need to be separate entities on the network; that is, the source adapter and the destination adapter can be implemented in the host device, and thus they do not have their own IP addresses.

[0054] For example, such as Figure 1 As shown, source adapter 8a can be implemented as part of a first NAT 4a, and destination adapter 8b can be implemented as part of a second NAT 4b. Alternatively, source adapter 8a can be implemented as part of source network node 1, and destination adapter 8b can be physically implemented as part of destination node 2. Adapters 8a-b modify the SCTP port in the communication between the source network node and the destination network node, as described in more detail below.

[0055] Network nodes (also referred to as radio base stations) 1a-c and 2a-b are here implemented as evolved Node B, also referred to as eNode B or eNB. Network nodes 1a-c and 2a-b may also be implemented as gNode B, or as any other current or future network node, provided the embodiments provided herein are applicable. If applicable, each network node may then be implemented using several child nodes. Network nodes 1a-c and 2a-b provide radio access to instances of user equipment (UE, not shown) on a wireless communication link. The term UE is also referred to as a mobile communication terminal, wireless device, mobile terminal, user terminal, user agent, wireless terminal, machine-to-machine device, etc., and may be implemented, for example, as a mobile phone, smartphone, or tablet / laptop computer with wireless connectivity as commonly known today.

[0056] Cellular 9 may conform to any suitable cellular network standard, such as LTE (Long Term Evolution), Advanced LTE, 5G NR (New Radio), 6G, or any other current or future wireless network, provided that the principles described below apply.

[0057] Peer-to-peer communication can occur on either the X2 (LTE) or Xn (5G) interface when a network node needs to send data to a peer network node, for example, for handover purposes. Both the X2 and Xn interfaces are based on SCTP. Therefore, SCTP packets are then sent from the source network node to the destination network node. According to the 3GPP specification, when applied to X2 / Xn, both the source and destination ports for SCTP should be set to 0x8E46, where "0x" indicates the application of hexadecimal representation whenever used in this document. In other words, 0x8E46 is equivalent to 36422 in decimal representation.

[0058] According to the embodiments provided herein, when source network nodes 1a-c behind NAT 4a send SCTP packets to destination network nodes 2a-b behind NAT 4b, instead of sending the SCTP packets directly over IP, the SCTP packets are encapsulated in UDP packets, which are then sent within IP packets. The ports for the SCTP and UDP packets are configured and tuned in a specific manner to allow efficient routing and transparent transmission, as described in more detail below, thereby enabling network nodes to remain behind their respective NATs and still support SCTP-based peer-to-peer communication (e.g., X2 / Xn) while conforming to 3GPP specifications.

[0059] Figure 2 It shows that it is encapsulated in a way that can be used Figure 1 A diagram illustrating SCTP packets within IP packets, UDP packets, and SCTP packets in an environment.

[0060] IP packet 10 has a source IP address 11 and a destination IP address 12 as part of its header. Within the payload of IP packet 10, a UDP packet 20 is provided. UDP packet 20 includes a source port 21 and a destination port 22 in its header, and an SCTP packet 30 in its payload. SCTP packet 30 includes a source port 31 and a destination port 32 in its header, and contains payload data. The payload data of the SCTP packet may, for example, relate to peer-to-peer communication between network nodes (e.g., X2 / Xn).

[0061] Figure 3 It is shown Figure 2 The grouping of structures in Figure 1 This is a schematic diagram illustrating the evolution of various parameters between nodes in the environment. (In order to...) Figure 3 For clarity, it will not be repeated here. Figure 2 The reference label, but the IP address and port are located in the same position as... Figure 2 The positions correspond to the positions in the diagram. Time flows from left to right. Each active node is shown sequentially from left to right at the top of the diagram, with the topmost box indicating the IP address of each node. Any changes to the parameters of the packets are indicated by bold borders. Thus, each group of packets is shown so that they appear to be sent from the corresponding node (except for the last node, i.e., destination network node 2).

[0062] In the descriptive naming conventions used for IP addresses in this document, letters without suffixes (e.g., “A” and “B”) are public IP addresses, and letters with suffixes (e.g., X.1, X.2, Y.1, Y.2) are local IP addresses. The letters allow for contextual distinction within this document, even if the same IP address may be applied to each local subnet, for example, within the IPv4 private address range of 192.168.0.0–192.168.255.255.

[0063] IP addresses A and B represent the public IP addresses of the first NAT 4a and the second NAT 4b, respectively. IP addresses X.1 and Y.1 represent the local IP addresses (also known as private IP addresses) of the first NAT 4a and the second NAT 4b, respectively. IP address X.2 represents the local IP address of the source network node 1, and IP address Y.2 represents the local IP address of the destination network node 2. Figure 3 In this embodiment, adapters 8a and 8b are implemented in the host device (in one of network nodes 1 and 2 or one of NATs 4a and 4b). Therefore, source adapter 8a is shown without any IP address, as this is indistinguishable from the host device.

[0064] The core network has informed network nodes 1 and 2 of their node identifiers, and network nodes 1 and 2 know the SCTP port numbers to be used for SCTP services (e.g., X2 / Xn). The core network provides the source network node with the identifier of the destination network node and the (public) IP address B of the destination network node, for example, to enable peer-to-peer communication (e.g., X2 / Xn) used for handover preparation and execution. The network node identifier may, for example, take the form of a Radio Access Network (RAN) node ID.

[0065] This process was used in the source network node 1 (which is...) Figure 1 The source network node 1a-c (any one of them) and the destination network node 2 (is Figure 1 Establish an SCTP association between any of the destination network nodes 2a-b.

[0066] The embodiments provided in this document are based on the ability of nodes at both the source and destination sites to determine (16-bit) source and (16-bit) destination numbers based on network node identifiers for use when configuring specific ports. The following will refer to... Figure 4A Steps 42 and 44 of -B describe the numbering process in more detail.

[0067] First, source network node 1 generates an SCTP packet with an SCTP payload for transmission, for example, for peer-to-peer communication from source network node 1 to destination network node 2. Source network node 1 is behind a first NAT 4a and has a local IP address X.2, being part of its local network, where the address range is identified by "X.". The source port of the SCTP packet is a predetermined number for peer-to-peer communication for a specific service or protocol, for example, 0x8E46 for X2 / Xn communication. The destination port of the SCTP packet is set to the destination number (0x5413 in this example). A UDP packet is generated, encapsulating the SCTP packet within a UDP payload. The source port of the UDP packet is the source number (0x118E in this example), and the destination port of the UDP packet is the destination number. An IP packet carrying the UDP packet is generated. The source address of the IP packet is set to the (local) IP address X.2 of source network node 1. The destination address of the IP packet is set to B, which is the public IP address of destination network node 2. More specifically, public IP address B is the public address of the second NAT 4b. The identifiers of the SCTP association (source IP address X.2, destination IP address B, SCTP source port 0x8E46, SCTP destination port 0x5413) remain unique among multiple radio network nodes in the source site. Since the SCTP destination port depends on the destination node identifier, this association is locally unique, i.e., unique among multiple radio network nodes in the source site using the SCTP protocol. Even if multiple source network nodes have the same public IP address, their network node identifiers differ, resulting in different source numbers and therefore different UDP source port numbers. Once all these parameters are set, IP packets are sent to source adapter 8a.

[0068] Source adapter 8a modifies the destination port of the SCTP packet and sets it to the same port number as the source port of the SCTP packet. This port number can be a predefined number used for peer-to-peer communication of related services or protocols, such as 0x8E46 for X2 / Xn communication, when it is set to the source port of the SCTP packet as described above. In this way, the adapted SCTP packet conforms to the 3GPP specification. Then, source adapter 8a sends IP packets to the first NAT 4a.

[0069] The first NAT 4a changes the source address of the IP packet from the local IP address X.2 to the public IP address A of the first NAT 4a, and sends the packet to the second NAT 4b over the transport network. Some NATs can be configured to use source port randomization for UDP (and / or TCP (Transmission Control Protocol)). To keep the UDP port as configured, source port randomization is not used in the embodiments provided herein.

[0070] As is known in the art itself, for the NAT process, the second NAT 4b changes the destination address of the IP packet from the public IP address B to the local IP address Y.2, which corresponds to the destination node 2 located behind the second NAT 4b. The IP packet is then forwarded to the destination adapter 8b. The second NAT 4b can determine the local IP address Y.2, for example, based on a table of site-local IP addresses and their corresponding UDP ports.

[0071] Destination adapter 8b sets the source port of the SCTP packet to the source number, i.e., the UDP source port number. In this way, information about the SCTP source transmitted using the UDP source port is correctly provided to the SCTP destination (destination network node 2) to ensure that the SCTP association between the source and destination remains unique. Then, destination adapter 8b forwards IP packets to destination network node 2. It should be noted that source network node 1 and destination network node 2 (unbeknownst to each other) do not have the same SCTP port number value for their respective associations involving the same connection. Their own SCTP port numbers (i.e., the source SCTP port of source network node 1 and the destination SCTP port of destination SCTP network node 2) are predefined port numbers for the service / protocol, while the port number at the other end is the same as the unique port number used for UDP.

[0072] This specific process, using port configuration for SCTP packets, allows NAT to be used for effective IP address usage, while the SCTP packets consistently conform to 3GPP standards between source adapter 8a and destination adapter 8b. Specifically, both the source and destination ports of the SCTP packets are set to port numbers specified by 3GPP, in this case 0x8E46. This allows any diagnostic, routing, firewall, performance, and maintenance equipment to identify and evaluate communications in a conventional manner. While UDP-based SCTP is known in itself (see, for example, RFC 6951), this solution is not suitable for X2 / Xn communications provided behind NAT because static 3GPP port numbers cannot be used to distinguish multiple network nodes behind NAT that therefore have the same public IP address. According to the embodiments provided herein, since the destination number is used by the source node as the SCTP destination port, multiple destination nodes at the same site (and therefore with the same public IP address) can be addressed using the same public IP address, even for the same service or protocol, where their SCTP associations remain different, thus avoiding conflicts between associations at the same site. Furthermore, if the association seen by the source or destination network node (the two ends will see different associations) is based on another network node, the association involves its services / protocols.

[0073] Because of NAT, public IP addresses no longer uniquely identify network nodes across all network nodes behind NAT; therefore, additional identifiers are needed. For compliance, debugging, and ease of implementation, it is desirable to keep SCTP ports as standard ports as possible. Carrying SCTP over UDP on IP provides additional port pairs, which are used for this purpose in this paper. A unique port number is created for each network node from an existing unique network node ID. These numbers are used for UDP port numbers, based on the identifiers of the source and destination nodes (and the NAT public IP address), respectively. For transmissions from the source network node, the destination SCTP port of the outgoing message is set to the destination UDP port to ensure that SCTP associations between different destination nodes within the same site remain unique. For receptions by the destination network node, the source SCTP port of the incoming message has been set to the source UDP port, also maintaining unique SCTP associations between destination nodes within the same destination site.

[0074] Figure 4A -B is a flowchart illustrating an embodiment of a method performed in a source network node to enable SCTP packets to be encapsulated in UDP packets for transmission from the source network node to the destination network node.

[0075] In step 42, the source network node obtains its source number based on its identifier. The source network node's identifier can be a base station identifier, also known as a RAN node ID. When this step is performed, the process is deterministic, consistently generating the same source number based on the same source network node. Furthermore, the risk of two different identifiers from the source network node resulting in the same source number is negligible, being one of 65536 for a 16-bit source number. Even so, network installers can perform source number calculations during deployment and assign identifiers to network nodes at the same site to ensure that the same source number never appears at a single site.

[0076] The source number can be obtained, for example, by calculating a hash value within a 16-bit range based on the identifier of the source network node. For instance, the source number can be obtained by performing a 16-bit hash calculation (e.g., CRC (Cyclic Redundancy Check) - 16) on the input (which is the identifier of the source network node). Alternatively, other factors can be added to the input.

[0077] The source number is then used to define the port number, as described below. Port numbers used for UDP and SCTP communication are in the range of 16 bits, that is, between 0 and (0xFFFF-1) (in hexadecimal representation), or between 0 and (65536-1) (in decimal).

[0078] In one embodiment, the source number is obtained by querying the central node 7 for the source number based on the identifier of the source network node. The central node 7 can be used to ensure that, under the same NAT (e.g., identified by the public IP address of the query from the source network node), duplicate source numbers are not generated for network nodes at the same site. The central node 7 can perform this determination itself, or it can query the information from another device.

[0079] In step 44, the source network node obtains the destination number based on the identifier of the destination network node, in the same way as obtaining the source number, but based on a different identifier. The identifier of the destination network node can be a base station identifier (e.g., RAN node ID). In one example, the destination network node is the handover target node in the handover preparation process. When this step is performed, the same identifier of the destination network node consistently produces the same destination number.

[0080] When obtaining the destination number by calculating a hash value based on the identifier of the destination network node, the destination number can be obtained by calculating a hash value within a sixteen-bit range based on the identifier of the destination network node, for example, similar to what was explained above for the source number.

[0081] When obtaining the destination number through communication with the central node, the destination number can be obtained by querying the central node 7 for the destination number based on the identifier of the destination network node, for example, as described above for the source number.

[0082] In step 46 of generating the SCTP packet, the source network node generates SCTP packet 30. The source port 31 of SCTP packet 30 is set to a predefined port number. The destination port 32 of SCTP packet 30 is set to the destination number obtained in step 44.

[0083] A predefined port number can be a number assigned for peer-to-peer communication between network nodes. For example, a predefined port number can be a number assigned for SCTP-based 3GPP X2 or Xn communication. This number is defined as 0x8E46.

[0084] In step 48 of generating the UDP packet, the source network node generates the UDP packet. The source port 21 of UDP packet 20 is set to the source number obtained in step 42. The destination port 22 of UDP packet 20 is set to the destination number obtained in step 44.

[0085] In encapsulation step 50, the source network node encapsulates SCTP packet 30 within UDP packet 20. In other words, the payload of the UDP packet contains the entire SCTP packet, including its header.

[0086] In sending step 52, the source network node sends UDP packet 20 to the destination network nodes 2, 2a, and 2b.

[0087] Now look Figure 4B , will only describe with Figure 4A Compared to new or modified steps.

[0088] In the optional IE reading step 40, the source network node reads an information element (IE) indicating that the destination nodes 2, 2a, and 2b support distinguishing base stations within a site, wherein this information element is configured for ad hoc network (SON) configuration. This allows the source network node to know when to apply the method according to the embodiments provided herein.

[0089] When signaling occurs between the source and destination network nodes for the purpose of establishing X2 / Xn, the IE used for this purpose will instruct the destination nodes 2, 2a, and 2b when they support distinguishing intra-site network nodes. This instruction may be useful when presenting the embodiments described herein, where some network nodes support intra-site network nodes while others do not.

[0090] Furthermore, the source network node can then indicate whether it supports the described method. This indication can be used by the destination network node when it switches roles and acts as the source network node, thereby allowing the destination network node to establish an outgoing SCTP association even before it has received any UDP-encapsulated SCTP packets according to this disclosure.

[0091] Table 1, based on TS 38.413v16.1.0, illustrates an example of how enhancements to a standardized IE can be implemented. This IE contains configuration information for SON functionality. Furthermore, the IE includes the network node identifier (RAN node ID) of the IE destination and the network node identifier of the IE source.

[0092]

[0093]

[0094] Table 1: Information Elements

[0095] The last two lines of the IE contain additional content for the embodiments provided herein, indicating whether the embodiments disclosed herein are supported.

[0096] Specifically, the field “Support for Intra Site ID” indicates (if included) that the source network node is enabled to identify target nodes within a site that are assigned to a single IP address and host multiple network nodes therein. The node receiving this information (i.e., the destination adapter 8b) learns that the UDP port number included in the possible process for establishing Xn triggered by the source node should be used for identifying target nodes within the site.

[0097] The field "Intra Site Identification Capability" indicates that the node sending this information is hosted by a site that supports intra site node identification as described in the embodiments provided herein. The node receiving this information knows that if, for example, it needs to establish an Xn interface with such a node, it can use the intra site identification information, thereby enabling it to contact the node sending the information according to the embodiments provided herein.

[0098] Figure 5 This is a flowchart illustrating an embodiment of a method performed in a source adapter to enable SCTP packets to be encapsulated in UDP packets for transmission from a source network node to a destination network node.

[0099] In step 140 of receiving UDP packets, source adapter 8a receives UDP packet 20 encapsulated with SCTP packet 30.

[0100] In step 142 of setting the SCTP destination port, the source adapter 8a sets the destination port 32 of the SCTP packet 30 to the same port number as the source port of the SCTP packet.

[0101] As explained above, the predefined port number can be a number assigned for SCTP-based 3GPP X2 communication.

[0102] In sending step 144, source adapter 8a sends UDP packet 20 via first NAT 4a and second NAT 4b to the destination network nodes 2, 2a, 2b.

[0103] Figure 6 This is a flowchart illustrating an embodiment of a method performed in a destination adapter to enable SCTP packets to be encapsulated in UDP packets for transmission from a source network node to a destination network node.

[0104] In step 240 of receiving UDP packets, the destination adapter 8b receives UDP packet 20 encapsulated with SCTP packet 30.

[0105] In step 242 of setting the SCTP source port, the destination adapter sets the source port 31 in the SCTP packet 30 to be the same as the source port 21 of the received UDP packet 20.

[0106] In sending step 244, destination adapter 8b sends UDP packets to transmit to destination network nodes 2, 2a, and 2b.

[0107] Deploying the embodiments provided herein in an existing network can be done using a staggered approach to allow for applicability without network disruption. First, all network nodes implement the embodiments provided herein, for example, in a software update. This can be done on a per-network-node basis. The updated network nodes are able to operate in both legacy and new modes (for the embodiments provided herein). Each network node retains a globally unique IP address until deployment covers all network nodes.

[0108] When operating as a server on X2 / Xn, the network node listens on IP port 0x8E46 and SCTP / UDP at port 0x8E4, as well as on the UDP port whose number is calculated according to step 44 above. Therefore, regardless of whether the incoming X2 / Xn service is in traditional mode or new mode, the server can take action based on the incoming service.

[0109] When acting as a client on X2 / Xn, the network node first attempts to establish an outgoing association using SCTP / UDP according to the embodiments provided herein, and reverts to traditional SCTP after a predefined timeout if the establishment attempt fails. This behavior is temporary and can be disabled once full deployment of the embodiments provided herein is complete. When the entire radio access network is suitable for this invention, SCTP / UDP will only be used for outgoing associations on X2. Once full deployment is complete, NAT can be used to configure sites with a single IP address. Alternatively, instead of using a timeout, IE as described above can be used to signal support for the embodiments provided herein, resulting in faster association establishment, especially for traditional SCTP, since the timeout does not need to expire.

[0110] Using the embodiments provided herein, NAT can be used at each site, whereby each site uses only a single public IP address. This allows for multiple network nodes per site, such as eNodeB, gNodeB, etc., thereby supporting different radio access technologies from the same site. Furthermore, because the SCTP port numbers between sites are set according to standards, this allows any firewall, diagnostic, performance, and maintenance equipment to identify and evaluate communications based on this process. Additionally, the (3GPP standard) port numbers do not conflict with any other standard services such as S1, NG-C, IuB, etc.

[0111] Figure 7 This illustrates an embodiment. Figure 1 A schematic diagram of the components of each of the source network node 1, source adapter 8a, and destination adapter 8b. Processor 60 is provided using any combination of one or more of a suitable central processing unit (CPU), graphics processing unit (GPU), multiprocessor, microcontroller, digital signal processor (DSP), etc., capable of executing software instructions 67 stored in memory 64; therefore, it can be a computer program product. Processor 60 can alternatively be implemented using application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), etc. Processor 60 can be configured to execute the above-referenced... Figure 4A -B (for the source network node) Figure 5 (for source adapter) and Figure 6 The method described (for the destination node).

[0112] Memory 64 may be any combination of random access memory (RAM) and / or read-only memory (ROM). Memory 64 also includes a permanent storage device, which may be any one or a combination of magnetic storage, optical storage, solid-state storage, or even remotely mounted storage.

[0113] A data memory 66 is also provided for reading and / or storing data during the execution of software instructions in the processor 60. The data memory 66 can be any combination of RAM and / or ROM.

[0114] I / O interface 62 is provided for communicating with external and / or internal entities. Optionally, I / O interface 62 may also include a user interface.

[0115] Other components have been omitted so as not to confuse the concepts presented in this article.

[0116] Figure 8 This illustrates an embodiment. Figure 1A schematic diagram of the functional modules of the source network node. These modules are implemented using software instructions (such as computer programs executed in the source network node). Alternatively or additionally, these modules are implemented using hardware such as ASICs (Application-Specific Integrated Circuits), FPGAs (Field-Programmable Gate Arrays), or any one or more discrete logic circuits. These modules are related to... Figure 4A The steps in the method shown in -B correspond to those in B.

[0117] IE reader 70 corresponds to step 40. Source number obtainr 72 corresponds to step 42. Destination number obtainr 74 corresponds to step 44. SCTP packet generator 76 corresponds to step 46. UDP packet generator 78 corresponds to step 48. Encapsulator 80 corresponds to step 50. Sender 82 corresponds to step 52.

[0118] Figure 9 This illustrates an embodiment. Figure 1 A schematic diagram of the functional modules of the source adapter. These modules are implemented using software instructions (such as computer programs executed in the source adapter). Alternatively or additionally, these modules are implemented using hardware such as ASICs (Application-Specific Integrated Circuits), FPGAs (Field-Programmable Gate Arrays), or any one or more discrete logic circuits. These modules are related to... Figure 5 The steps in the method shown correspond to those in the example.

[0119] UDP packet receiver 170 corresponds to step 140. SCTP destination port setter 172 corresponds to step 142. Transmitter 174 corresponds to step 144.

[0120] Figure 10 This illustrates an embodiment. Figure 1 A schematic diagram of the functional modules of the destination adapter. These modules are implemented using software instructions (such as computer programs executed in the destination adapter). Alternatively or additionally, these modules are implemented using hardware such as ASICs (Application-Specific Integrated Circuits), FPGAs (Field-Programmable Gate Arrays), or any one or more discrete logic circuits. These modules are related to... Figure 6 The steps in the method shown correspond to those in the example.

[0121] UDP packet receiver 270 corresponds to step 240. SCTP source port setter 272 corresponds to step 242. Transmitter 274 corresponds to step 244.

[0122] Figure 11An example of a computer program product including computer-readable components is shown. A computer program 91, which can cause a processor to perform methods according to the embodiments described herein, can be stored on this computer-readable component. In this example, the computer program product takes the form of removable solid-state memory, such as a Universal Serial Bus (USB) drive. As mentioned above, the computer program product can also be embodied in the memory of a device, such as... Figure 7 Computer program product 64. Although computer program 91 is schematically shown herein as part of removable solid-state storage, computer program may be stored in any manner suitable for computer program products such as another type of removable solid-state storage or optical discs such as CD (compressed optical disc), DVD (digital versatile optical disc) or Blu-ray disc.

[0123] Various aspects of this disclosure have been described above with primary reference to several embodiments. However, as will be readily understood by those skilled in the art, other embodiments besides those disclosed above are equally possible within the scope of the invention, as defined by the appended claims. Therefore, while various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for illustrative purposes and are not intended to be limiting; their true scope and spirit are indicated by the appended claims.

Claims

1. A system (9) for enabling Flow Control Transmission Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the system comprising the source network node (1, 1a, 1b, 1c), a source adapter (8a) and a destination adapter (8b). in, The source network nodes (1, 1a, 1b, 1c) include: Processor (60); and A memory (64) storing instructions (67) that, when executed by the processor, cause the source network nodes (1, 1a, 1b, 1c) to: Based on the identifiers of the source network nodes (1, 1a, 1b, 1c), the source number is obtained; Based on the identifiers of the destination network nodes (2, 2a, 2b), the destination number is obtained; Generating an SCTP packet (30) includes setting the source port (31) of the SCTP packet (30) to a predefined port number and setting the destination port (32) of the SCTP packet (30) to the destination number; Generating a UDP packet includes: setting the source port (21) of the UDP packet (20) to the source number and setting the destination port (22) of the UDP packet (20) to the destination number; The SCTP packet (30) is encapsulated (50) within the UDP packet (20); and Send (52) the UDP packet (20) to the destination network node (2, 2a, 2b); The source adapter (8a) includes: Processor (60); and A memory (64) storing instructions (67) that, when executed by the processor, cause the source adapter (8a) to: Receive the UDP packet (20) encapsulating the SCTP packet (30); Set the destination port (32) of the SCTP packet (30) to be the same as the port number of the source port of the SCTP packet; The UDP packet (20) is sent to the destination network node (2, 2a, 2b). The destination adapter (8b) includes: Processor (60); and A memory (64) storing instructions (67) that, when executed by the processor, cause the destination adapter (8b) to: Receive the UDP packet (20) encapsulating the SCTP packet (30); Set the source port (31) in the SCTP packet (30) to be the same as the source port (21) of the received UDP packet (20); and The UDP packet is sent to the destination network node (2, 2a, 2b).

2. A method for enabling Flow Control Transport Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the method being performed by the source network node (1, 1a, 1b, 1c), the method comprising the following steps: Based on the identifiers of the source network nodes (1, 1a, 1b, 1c), the source number (42) is obtained; Based on the identifiers of the destination network nodes (2, 2a, 2b), the destination number (44) is obtained; Generate (46) SCTP packet (30), which includes: setting the source port (31) of the SCTP packet (30) to a predefined port number, and setting the destination port (32) of the SCTP packet (30) to the destination number; Generate (48) UDP packets, which includes: setting the source port (21) of the UDP packet (20) to the source number and setting the destination port (22) of the UDP packet (20) to the destination number; The SCTP packet (30) is encapsulated (50) within the UDP packet (20); and Send (52) the UDP packet (20) to the destination network node (2, 2a, 2b).

3. The method according to claim 2, wherein, The identifier of the destination network node is a base station identifier, and the identifier of the source network node is a base station identifier.

4. The method according to claim 2 or 3, wherein, The step of obtaining (42) the source number includes: calculating a hash value in the range of sixteen bits based on the identifier of the source network node (1, 1a, 1b, 1c); and wherein the step of obtaining (44) the destination number includes: calculating a hash value in the range of sixteen bits based on the identifier of the destination network node (2, 2a, 2b).

5. The method according to claim 2 or 3, wherein, The step of obtaining (42) the source number includes: querying the source number to the central node (7) based on the identifier of the source network node (1, 1a, 1b, 1c); and wherein the step of obtaining (44) the destination number includes: querying the destination number to the central node (7) based on the identifier of the destination network node (2, 2a, 2b).

6. The method according to claim 2 or 3, wherein, The predefined port number is a number assigned for peer-to-peer communication between network nodes.

7. The method according to claim 2 or 3, wherein, The predefined port number is a number assigned for SCTP-based 3GPP X2 or Xn communication.

8. The method according to claim 2 or 3, further comprising the following steps: Read (40) indicates that the destination node (2, 2a, 2b) supports distinguishing information elements of base stations within the site, wherein the information elements are configured for self-organizing network configuration.

9. A source network node (1, 1a, 1b, 1c) for enabling Flow Control Transmission Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from the source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the source network node (1, 1a, 1b, 1c) comprising: Processor (60); as well as A memory (64) storing instructions (67) that, when executed by the processor, cause the source network nodes (1, 1a, 1b, 1c) to: Based on the identifiers of the source network nodes (1, 1a, 1b, 1c), the source number is obtained; Based on the identifiers of the destination network nodes (2, 2a, 2b), the destination number is obtained; Generating an SCTP packet (30) includes setting the source port (31) of the SCTP packet (30) to a predefined port number and setting the destination port (32) of the SCTP packet (30) to the destination number; Generating a UDP packet includes: setting the source port (21) of the UDP packet (20) to the source number and setting the destination port (22) of the UDP packet (20) to the destination number; The SCTP packet (30) is encapsulated within the UDP packet (20); and The UDP packet (20) is sent to the destination network node (2, 2a, 2b).

10. The source network nodes (1, 1a, 1b, 1c) according to claim 9, wherein, The identifier of the destination network node is a base station identifier, and the identifier of the source network node is a base station identifier.

11. The source network node (1, 1a, 1b, 1c) according to claim 9 or 10, wherein, The instructions for obtaining the source number include instructions (67) that, when executed by the processor, cause the source network node (1, 1a, 1b, 1c) to: calculate a hash value in the range of sixteen bits based on the identifier of the source network node (1, 1a, 1b, 1c); Furthermore, the instruction for obtaining the destination number includes instruction (67), which, when executed by the processor, causes the source network node (1, 1a, 1b, 1c) to calculate a hash value in the range of sixteen bits based on the identifier of the destination network node (2, 2a, 2b).

12. The source network node (1, 1a, 1b, 1c) according to claim 9 or 10, wherein, The instructions for obtaining the source number include instructions (67), which, when executed by the processor, cause the source network nodes (1, 1a, 1b, 1c) to query the central node (7) for the source number based on the identifier of the source network nodes (1, 1a, 1b, 1c); and wherein the instructions for obtaining the destination number include instructions (67), which, when executed by the processor, cause the source network nodes (1, 1a, 1b, 1c) to query the central node (7) for the destination number based on the identifier of the destination network nodes (2, 2a, 2b).

13. The source network node (1, 1a, 1b, 1c) according to claim 9 or 10, wherein, The predefined port number is a number assigned for peer-to-peer communication between network nodes.

14. The source network node (1, 1a, 1b, 1c) according to claim 9 or 10, wherein, The predefined port number is a number assigned for SCTP-based 3GPP X2 or Xn communication.

15. The source network node (1, 1a, 1b, 1c) according to claim 9 or 10, further comprising instructions (67) that, when executed by the processor, cause the source network node (1, 1a, 1b, 1c) to: Reading the information elements indicating that the destination node (2, 2a, 2b) supports distinguishing base stations within the site, wherein, The information element is configured for self-organizing network configuration.

16. A computer-readable storage medium having stored thereon computer program code, which, when executed on a source network node (1, 1a, 1b, 1c), causes the source network node (1, 1a, 1b, 1c) to perform a method for enabling Flow Control Transmission Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from the source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the method comprising the steps of: Based on the identifiers of the source network nodes (1, 1a, 1b, 1c), the source number is obtained; Based on the identifiers of the destination network nodes (2, 2a, 2b), the destination number is obtained; Generating an SCTP packet (30) includes setting the source port (31) of the SCTP packet (30) to a predefined port number and setting the destination port (32) of the SCTP packet (30) to the destination number; Generating a UDP packet includes: setting the source port (21) of the UDP packet (20) to the source number and setting the destination port (22) of the UDP packet (20) to the destination number; The SCTP packet (30) is encapsulated within the UDP packet (20); and The UDP packet (20) is sent to the destination network node (2, 2a, 2b).

17. A computer program product (64, 90) comprising computer program code that, when executed on a source network node (1, 1a, 1b, 1c), causes the source network node (1, 1a, 1b, 1c) to perform the method according to any one of claims 2 to 8.

18. A method for enabling Flow Control Transport Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the method being performed by a source adapter (8a), the method comprising the steps of: Receive (140) a UDP packet (20) encapsulating an SCTP packet (30), wherein the source port (31) of the SCTP packet (30) is set to a predefined port number and the destination port (32) of the SCTP packet (30) is set to a destination number obtained based on the identifier of the destination network node (2, 2a, 2b), and wherein the source port (21) of the UDP packet (20) is set to a source number obtained based on the identifier of the source network node (1, 1a, 1b, 1c) and the destination port (22) of the UDP packet (20) is set to the destination number; Set (142) of the destination port (32) of the SCTP packet (30) to the same port number as the source port of the SCTP packet; and Send (144) the UDP packet (20) to the destination network node (2, 2a, 2b).

19. The method according to claim 18, wherein, The predefined port number is a number assigned for SCTP-based 3GPP X2 or Xn communication.

20. A source adapter (8a) for enabling Flow Control Transport Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), said source adapter (8a) comprising: Processor (60); as well as A memory (64) storing instructions (67) that, when executed by the processor, cause the source adapter (8a) to: Receive a UDP packet (20) encapsulating an SCTP packet (30), wherein the source port (31) of the SCTP packet (30) is set to a predefined port number and the destination port (32) of the SCTP packet (30) is set to a destination number obtained based on the identifier of the destination network node (2, 2a, 2b), and wherein the source port (21) of the UDP packet (20) is set to a source number obtained based on the identifier of the source network node (1, 1a, 1b, 1c) and the destination port (22) of the UDP packet (20) is set to the destination number; Set the destination port (32) of the SCTP packet (30) to the same port number as the source port of the SCTP packet; and The UDP packet (20) is sent to the destination network node (2, 2a, 2b).

21. The source adapter (8a) according to claim 20, wherein, The predefined port number is a number assigned for SCTP-based 3GPP X2 or Xn communication.

22. A computer-readable storage medium having stored thereon computer program code, which, when executed on a source adapter (8a), causes the source adapter (8a) to perform a method for enabling Flow Control Transmission Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the method comprising the steps of: Receive a UDP packet (20) encapsulating an SCTP packet (30), wherein the source port (31) of the SCTP packet (30) is set to a predefined port number and the destination port (32) of the SCTP packet (30) is set to a destination number obtained based on the identifier of the destination network node (2, 2a, 2b), and wherein the source port (21) of the UDP packet (20) is set to a source number obtained based on the identifier of the source network node (1, 1a, 1b, 1c) and the destination port (22) of the UDP packet (20) is set to the destination number; Set the destination port (32) of the SCTP packet (30) to the same port number as the source port of the SCTP packet; and The UDP packet (20) is sent to the destination network node (2, 2a, 2b).

23. A computer program product (64, 90) comprising computer program code that, when executed on a source adapter (8a), causes the source adapter (8a) to perform the method according to claim 18 or 19.

24. A method for enabling Flow Control Transport Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the method being performed by a destination adapter (8b), the method comprising the steps of: Receive (240) a UDP packet (20) encapsulating an SCTP packet (30), wherein the source port (31) of the SCTP packet (30) is set to a predefined port number and the destination port (32) of the SCTP packet (30) is set to the same port number as the source port of the SCTP packet, and wherein the source port (21) of the UDP packet (20) is set to a source number obtained based on the identifier of the source network node (1, 1a, 1b, 1c) and the destination port (22) of the UDP packet (20) is set to the destination number; Set (242) the source port (31) in the SCTP packet (30) to be the same as the source port (21) of the received UDP packet (20); and Send (244) the UDP packet to the destination network node (2, 2a, 2b).

25. A destination adapter (8b) for enabling Flow Control Transport Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), said destination adapter (8b) comprising: Processor (60); as well as The memory (64) stores instructions (67), which, when executed by the processor, cause the destination adapter (8b) to: Receive a UDP packet (20) encapsulating an SCTP packet (30), wherein the source port (31) of the SCTP packet (30) is set to a predefined port number and the destination port (32) of the SCTP packet (30) is set to the same port number as the source port of the SCTP packet, and wherein the source port (21) of the UDP packet (20) is set to a source number obtained based on the identifier of the source network node (1, 1a, 1b, 1c) and the destination port (22) of the UDP packet (20) is set to the destination number; Set the source port (31) in the SCTP packet (30) to be the same as the source port (21) of the received UDP packet (20); and The UDP packet is sent to the destination network node (2, 2a, 2b).

26. A computer-readable storage medium having stored thereon computer program code, which, when executed on a destination adapter (8b), causes the destination adapter (8b) to perform a method for enabling Flow Control Transmission Protocol (SCTP) packets (30) to be encapsulated in User Datagram Protocol (UDP) packets (20) for transmission from a source network node (1, 1a, 1b, 1c) to a destination network node (2, 2a, 2b), the method comprising the steps of: Receive a UDP packet (20) encapsulating an SCTP packet (30), wherein the source port (31) of the SCTP packet (30) is set to a predefined port number and the destination port (32) of the SCTP packet (30) is set to the same port number as the source port of the SCTP packet, and wherein the source port (21) of the UDP packet (20) is set to a source number obtained based on the identifier of the source network node (1, 1a, 1b, 1c) and the destination port (22) of the UDP packet (20) is set to the destination number; Set the source port (31) in the SCTP packet (30) to be the same as the source port (21) of the received UDP packet (20); and The UDP packet is sent to the destination network node (2, 2a, 2b).

27. A computer program product (64, 90) comprising computer program code that, when executed on a destination adapter (8b), causes the destination adapter (8b) to perform the method according to claim 24.

Images