Interworking between cell and packet based networks
Summary by NHIP
Cell-to-Packet Data Interworking
The apparatus forms transport packets from received data segments regardless of whether complete data units arrive. A segmentation layer adds indications identifying specific data units to segments before transmitting them to an Ethernet packet network.
Claim Score by NHIP
Abstract
A method and apparatus of communicating data between a cell based network and a packet based network. Received segments of data units are formed into new data segments which are transmitted irrespective of whether a complete data unit has been received. The received segments may be stored, used to form cells and/or transport packets, and transmitted to the cell based network or the packet based network. Also, conditions may be detected, such as timer expiration or a maximum reception capacity achieved, before the segments are used to form the cells and/or transport packets. Forming transport packets may comprise including segments belonging to a specific data unit in a transport packet and/or adding an indication of a specific data unit to which a segment belongs. These operations may be performed by a base station, an interworking unit, or a radio network controller.

Term
Projected expiry 4 February 2028.
- Priority
- Filed
- Granted
- Today
- Projected expiry
28 claims: 4 independent, 24 dependent
- 1An apparatus, comprising:a receiver configured to receive segments of data units from a cell based network, wherein the data units are data units of a higher layer of the cell based network, and wherein the higher layer of the cell based network terminates at the apparatus;a processor configured to form transport packets out of the segments of the data units irrespective of whether a complete data unit has been received, using a segmentation/reassembly and multiplexing/demultiplexing layer of the apparatus which is introduced on top of a transport layer of the apparatus, wherein the segmentation/reassembly and multiplexing/demultiplexing layer is configured to add an indication to a segment out of the segments received, the indication configured to indicate a specific data unit to which the segment belongs, and put the segment with the indication into a transport packet to be transmitted to a packet based network, wherein the segmentation/reassembly and multiplexing/demultiplexing layer is configured to repeat these processes for each of the segments received, thereby forming the transport packets;and a transmitter configured to transmit the transport packets to the packet based network.
- 16Broadest claimClaim Score 55, average(NHIP)A method for an apparatus, comprising:receiving segments of data units from a cell based network, wherein the data units are data units of a higher layer of the cell based network, and wherein the higher layer of the cell based network terminates at the apparatus;forming transport packets out of the segments of the data units irrespective of whether a complete data unit has been received, using a segmentation/reassembly and multiplexing/demultiplexing layer of the apparatus, which is introduced on top of a transport layer of the apparatus, wherein the segmentation/reassembly and multiplexing/demultiplexing layer adds an indication to a segment out of the segment received, the indication indicating a specific data unit to which the segment belongs, and puts the segment with the indication into a transport packet to be transmitted to a packet based network, wherein the segmentation/reassembly and multiplexing/demultiplexing layer repeats these processes for each of the segments received, thereby forming the transport packets;and transmitting the transport packet to a packet based network.
- 26A computer program embodied in a computer-readable medium, the computer program configured to control a processor to perform operations comprising:receiving segments of data units from a cell based network, wherein the data units are data units of a higher layer of the cell based network, and wherein the higher layer of the cell based network terminates at the apparatus;forming transport packets out of the segments of the data units irrespective of whether a complete data unit has been received, using a segmentation/reassembly and multiplexing/demultiplexing layer of the apparatus which is introduced on top of a transport layer of the apparatus, wherein the segmentation/reassembly and multiplexing/demultiplexing layer adds an indication to a segment out of the segments received, the indication indicating a specific data unit to which the segment belongs and puts the segment with the indication into a transport packet to be transmitted to a packet based network, wherein the segmentation/reassembly and multiplexing/demultiplexing layer repeats these processes for each of the segments received, thereby forming the transport packets;and transmitting the transport packets to the packet based network.
- 28An apparatus, comprising:receiving means for receiving segments of data units from a cell based network, wherein the data units are data units of a higher layer of the cell based network, and wherein the higher layer of the cell based network terminates at the apparatus;forming means for forming transport packets out of the segments of the data units irrespective of whether a complete data unit has been received, using a segmentation/reassembly and multiplexing/demultiplexing layer of the apparatus which is introduced on top of a transport layer of the apparatus, wherein the segmentation/reassembly and multiplexing/demultiplexing layer is configured to add an indication to a segment out of the segments received, the indication configured to indicate a specific data unit to which the segment belongs, and put the segment with the indication into a transport packet to be transmitted to a packet based network, wherein the segmentation/reassembly and multiplexing/demultiplexing layer is configured to repeat these processes for each of the segments received, thereby forming the transport packets;and transmitting means for transmitting the transport packets to the packet based network.
Independent claims4
95 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
p-0002The present invention relates to a method and apparatus for communicating data in a communication network system. In particular, the present invention relates to transmitting data between cell and packet based networks.
BACKGROUND OF THE INVENTION
p-0003Within the Terrestrial Radio Access Network (UTRAN) of the Universal Mobile Telecommunication System (UMTS) the Iub interface is located between the Radio Network Controller (RNC) and the base stations (Node B). For the Iub interface, the Asynchronous Transfer Mode (ATM) and ATM Adaptation Layer type 2 (AAL2) are used for transporting Frame Protocol (FP) PDUs (Protocol Data Units).
p-0004Ethernet is becoming a reasonable alternative to cell based transport infrastructure. In case of Ethernet the Internet Protocol (IP) is seen as the most feasible network layer. A typical way to transport Iub traffic over IP is to transport FP PDU frames over UDP/IP.
p-0005Due to existing legacy systems, interworking between cell based protocols, e.g. ATM, and packet based protocols, e.g. IP, based nodes is required, e.g. between an ATM based RNC and an IP based Node B (base station, BTS). This functionality may be either located in explicit nodes (Interworking Unit, IWU) or be part of other network elements, like e.g. the RNC and Node Bs themselves. For user plane traffic those nodes terminate the AAL2 layer on the ATM interface and then send the received FP frames over UDP/IP (User Datagram Protocol/Internet Protocol) to the BTS and vice versa.
p-0006As shown in <figref idrefs="DRAWINGS">FIG. 11</figref>, Frame protocol (FP) PDUs, which are larger than 45 octets, are segmented by the AAL2 SSSAR (Service Specific Transmission and Reassembly Sublayer) into multiple, up to 45 octets long CPS (Common Part Sublayer) SDUs (Service Data Units). Each of those CPS SDUs is given a CPS header, and the complete CPS PDUs are then multiplexed into ATM cells.
p-0007<figref idrefs="DRAWINGS">FIG. 12</figref> shows the format of an AAL2 CPS packet in greater detail. A CPS packet header (CPS-PH) comprises a Channel Identifier (CID) of eight bits identifying a user channel out of 256 channels, a Length Indicator (LI) of six bits indicating the length of a packet payload, a User-to-User Indication (UUI) of five bits as an SSCS (Service Specific Convergence Sublayer) specific indication, and a Header Error Control (HEC) of five bits serving for error detection in the CPS-PH. CPS-INFO represents the CPS packet payload (CPS-PP) comprising 1 to 45 bytes. Thus, a CPS packet may comprise 4 to 48 bytes.
p-0008In order to use the transport resources efficiently, each AAL2 connection might be shaped individually on a CPS packet basis before multiplexing it into ATM cells. Without shaping, the CPS packets are transmitted back-to-back as a burst whereas the shaping allows the transmission of the segments (i.e. CPS packets) with a finite inter-departure time. During the inter-departure time the CPS packets of other AAL2 connections using the same path may use the path capacity.
p-0009A node which is terminating the AAL2 layer and further processes the received AAL2 SDU normally has to wait until it has received all CPS packets for a complete AAL2 SDU. This is called “Store-and-forward” method, because first the complete AAL2 SDU must be received before it can be forwarded to the next processing layer. The time needed until the complete AAL2 SDU has been received depends on the shaping parameters, transport capacities and the size of the AAL2 SDUs.
p-0010Due to this “store-and-forward” method the delay imposed by an intermediate ATM/IP Interworking Unit (IWU) between the RNC and BTS, will be significantly increased, especially in case of large FP frames like for example those typical for HSDPA (High Speed Downlink Packet Access).
p-0011Another critical aspect for Iub is not only the total delay of the transport layer, but even more the delay variation the transport layer imposes. The frame protocol layer used on the Iub has the capability to adapt to the transport delay between RNC and BTS, but it still requires that the total delay remains within a given range. Thus, any larger variation will cause data losses. With ATM the delay variation remains small and is controllable, however, with a packet based transport network with intermediate nodes the delay is depending on the packet size, number of nodes, link capacity between the nodes and how large other packets are when they are blocking the link. Thus, the delay variation can become quite large.
p-0012Another drawback is that on the IP interfaces large UDP payload (more than 1472 bytes) is problematic, since due to the limited MTU (maximum transfer unit) size of Ethernet (1500 bytes) IP segmentation is required, which is a quite complicated and memory demanding functionality on the receiver side. In general, large packets are not recommended when the transport network consists of several nodes (e.g. IP routers, Ethernet switches) and low capacity links, because at each node the complete packet has to be received before it can be forwarded.
p-0013In addition, in case of small FP frames (e.g. voice frames), the overhead/payload ratio is poor if only a single small frame is transported within an IP packet, thus transport bandwidth will be wasted.
p-0014A prior art solution allows to multiplex small packets called “CIP” of variable size in one CIP container, also of variable size. This may allow an efficient use of the transport bandwidth by amortizing the IP/UDP overhead over several CIP packets.
p-0015A segmentation/re-assembly mechanism allows to split large FP PDUs in smaller segments, which will be the CIP packets. There has to be a trade-off between efficiency (IP header/payload ratio) and transmission delay. Large data packets have to be segmented in order to avoid IP fragmentation and to keep transmission delays low.
p-0016However, this solution assumes that the complete FP PDU is received before the frame is split into smaller segments.
SUMMARY OF THE INVENTION
p-0017It is an object of the present invention to improve interworking between a cell based network and a packet based network by reducing delay and delay variation and increasing transport efficiency.
p-0018According to an aspect of the invention, this object is achieved by a network entity for communicating data between a cell based network and a packet based network. The network entity comprises a receiving means for receiving segments of data units, a forming means for forming new data segments out of the segments of the data units, and a transmitting means for transmitting the new data segments, wherein the transmitting means is configured to transmit the new data segments irrespective of whether a complete data unit has been received.
p-0019The cell based network may comprise an ATM network, and the packet based network may comprises Ethernet.
p-0020When data is communicated in the direction from the packet based network to the cell based network, wherein the segments of data units received by the receiving means are distributed over a plurality of packets from the packet based network, a storing means of the network entity temporarily stores received segments, and the forming means of the network entity forms cells, wherein the transmitting means transmits the cells formed by the forming means to the cell based network.
p-0021When data is transmitted in the direction from the cell based network to the packet based network, wherein the segments of data units received by the receiving means are distributed over a plurality of cells from the cell based network, a storing means of the network entity temporarily stores received segments, and a forming means of the network entity forms transport packets, wherein the transmitting means transmits the packets formed by the forming means to the packet based network.
p-0022The network entity may further comprise a detecting means for detecting conditions to be fulfilled in order to build a transport packet out of the stored segments from the storing means.
p-0023The detecting means may, as one of the conditions, detect a timer expiration or detect that the number of received segments reaches a maximum size of the transport packets.
p-0024The network entity may further comprise a determining means for determining a maximum size of the transport packets, wherein the transport packets each may have the same maximum size.
p-0025The forming means may form the transport packets by including segments belonging to a specific data unit into different transport packets and/or by including segments belonging to different data units into one transport packet.
p-0026The forming means may also add an indication to the segments out of which the transport packet is formed, the indication indicating a specific data unit to which the segments belong.
p-0027The network entity may comprises at least one of a base station, an interworking unit and a radio network controller.
p-0028According to another aspect of the invention, the above object is achieved by a method of communicating data between a cell based network and a packet based network, the method comprising a receiving step of receiving segments of data units, a forming step of forming new data segments out of the segments of the data units, and a transmitting step of transmitting the new data segments, wherein the new data segments are transmitted irrespective of whether a complete data unit has been received.
p-0029The invention may also be implemented as computer program product for a computer, wherein the computer program product may comprise a computer-readable medium on which the software code portions are stored, or wherein the computer program product is directly loadable into an internal memory of the computer.
p-0030It is a benefit of the present invention that the processing delay within a network entity such as an Interworking Unit between a cell and packet based network is reduced, since it is not required that a complete higher layer SDU has to be received before a further processing can be started, and so reducing the introduced delay (so called “cut-through” processing).
p-0031Moreover, the packet based interfaces (e.g. IP and/or Ethernet) are used very efficiently by using an optimum overhead/payload ratio.
p-0032Furthermore, according to an embodiment of the invention, delay variation is reduced by using a fixed packet length.
p-0033Furthermore, according to the invention, large higher layer SDUs (e.g. from HSDPA traffic) can be transported over Ethernet, without the need for intermediate IP segmentation.
p-0034An additional advantage of the present invention is that due to the “cut-through” processing of higher layer SDUs less memory is required.
BRIEF DESCRIPTION OF THE DRAWINGS
p-0035<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates an example protocol stack of a cell based/packet based Interworking Unit for user plane processing according to the present invention.
p-0036<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a procedure of building transport packets using segments from higher layer SDUs from multiple higher layer connections according to an embodiment of the present invention.
p-0037<figref idrefs="DRAWINGS">FIG. 3</figref> illustrates a procedure of building transport packets of maximum size using segments from higher layer SDUs from multiple higher layer connections according to an embodiment of the present invention.
p-0038<figref idrefs="DRAWINGS">FIG. 4</figref> illustrates a procedure of building several transport packets using segments from a higher layer SDU of one higher layer connection according to an embodiment of the present invention.
p-0039<figref idrefs="DRAWINGS">FIG. 5</figref> shows a schematic block diagram illustrating functionality of a network entity <b>10</b> according to the invention, interfacing a cell based network and a packet based network, in a direction from the cell based network to the packet based network.
p-0040<figref idrefs="DRAWINGS">FIG. 6</figref> shows a flow diagram illustrating a process of forming a new transport data packet according to the present invention.
p-0041<figref idrefs="DRAWINGS">FIG. 7</figref> illustrates a procedure of building ATM cells of higher layer SDUs from transport packet segments according to an embodiment of the present invention.
p-0042<figref idrefs="DRAWINGS">FIG. 8</figref> shows a schematic block diagram illustrating functionality of the network entity <b>40</b> according to the invention, in a direction from the packet based network to the cell based network.
p-0043<figref idrefs="DRAWINGS">FIG. 9</figref> shows a flow diagram illustrating a process of forming cells carrying segments of data units according to the present invention.
p-0044<figref idrefs="DRAWINGS">FIG. 10</figref> shows a flow diagram illustrating a process of forming data segments according to the present invention.
p-0045<figref idrefs="DRAWINGS">FIG. 11</figref> illustrates processing performed in ATM Adaptation Layer 2.
p-0046<figref idrefs="DRAWINGS">FIG. 12</figref> illustrates a format of an AAL2 CPS packet.
DESCRIPTION OF THE PREFERRED EMBODIMENTS
p-0047The main idea of the present invention is to use a “cut-through” processing instead of a “store-and-forward” mechanism between cell and packet based networks, where on the packet based interface several optimization methods are used for increasing efficiency and decreasing delay and delay variations.
p-0048In particular, the present invention is applicable to UMTS (Universal Mobile Telecommunications System) networks, specifically in the RAN (Radio Access Network) area, where a mixture of cell and packet based transmission technologies will be used.
p-0049In the context of the preferred embodiment a protocol data unit is a frame protocol (FP) PDU, which is equal to a higher layer SDU such as an AAL2 SDU (as shown also in <figref idrefs="DRAWINGS">FIG. 11</figref>). According to ATM, segments of a service data unit are SDUs created by the SSSAR sublayer of AAL2, which will be used for forming AAL2 CPS packets. A transport packet is a packet according to the protocol used in the packet based network, carrying segments of one or multiple frame protocol PDUs.
p-0050In order to keep the delay variation below a certain limit, it is beneficial when all packets have the same size. Further on in order to keep the transport delay small, especially in a multihop and/or low capacity packet based network, a reasonable maximum transport data packet size is calculated according to network properties, which all packets should have. The size calculation is also affected by the payload/packet size ratio (transport efficiency), which is decreasing with smaller packets sizes, because the transport overhead remains the same and only less payload is transported within the packet.
p-0051The actual data, which is transported over the packet based network, may have a variable size which may be much smaller than the reasonable maximum packet size or also much larger.
p-0052In the latter case, it is known to segment a large piece of data into several smaller chunks called “segments”, where each of those will result in a packet having the maximum packet size, with the possible exception of the packet carrying the last segment.
p-0053If the piece of data is smaller, it is known to multiplex data from several connections into the same packet, so that the packet reaches the reasonable maximum packet size. If there is not enough data available to reach a target packet size with multiplexing, then the node is waiting until there is enough data available. This waiting time may be limited by an upper value, which is used to keep the introduced delay below a certain limit.
p-0054Thus, a new transport data packet is built together, when <ul><li id="ul0001-0001" num="0000"><ul><li id="ul0002-0001" num="0054">a timer expires, or</li><li id="ul0002-0002" num="0055">the resulting transport packet size reaches a maximum transport packet size.</li></ul></li></ul>
p-0055According to the present invention, data segments can be already transmitted before the complete (FP) PDU has been received, thus reducing the introduced transmission delay.
p-0056According to an implementation example to be described in the following referring to <figref idrefs="DRAWINGS">FIGS. 1 to 4</figref> and <b>7</b>, <ul><li id="ul0003-0001" num="0000"><ul><li id="ul0004-0001" num="0058">a new segmentation/reassembly and multiplexing/demultiplexing layer is introduced between an application layer (e.g. Frame Protocol handler) and a transport layer (e.g. IP/UDP) in the BTS and on top of the transport layer in the IWU,</li><li id="ul0004-0002" num="0059">on a Service Access Point (SAP) between an AAL2 SSCS/SSSAR Layer (Segmentation and Reassembly Service Specific Convergence Sublayer) and an AAL2 user layer (e.g. Frame Protocol handler) also partial AAL2 SDUs can be exchanged, and</li><li id="ul0004-0003" num="0060">the size and content of the transport packet is determined according to link capacities, a delay budget, connection priorities, timer values per AAL2 connection, a Path MTU size (to avoid additional IP fragmentation), etc.</li></ul></li></ul>
p-0057In particular, the present invention may be used beneficially in ATM/IP interworking units (IWU) where FP PDUs have to be transported over an IP network, especially when the delay issues are critical and the transport capacities in the IP network are low.
p-0058In such applications the maximum size for the IP transport packets has to be determined as a trade-off between transport efficiency (payload/packet size ratio) and transmission delay and delay variation.
p-0059<figref idrefs="DRAWINGS">FIG. 1</figref> illustrates an example protocol stack of a cell based (ATM)/packet based (Ethernet, optionally with IP) Interworking Unit (IWU) <b>100</b> for user plane processing according to the present invention. As shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, a protocol stack at an ATM based RNC comprises an application layer on top, followed by a frame protocol layer FP, an AAL2 SSSAR layer, AAL2 CPS layer, ATM layer and physical layer. At a cell based interface <b>101</b> of the IWU <b>100</b> a protocol stack comprises the AAL2 SSSAR layer on top, followed by the AAL2 CPS layer, the ATM layer and the physical layer. At a packet based interface <b>102</b> of the IWU <b>100</b> a protocol stack comprises a segmentation/multiplexing and reassembly/demultiplexing layer (which is simply referred to as segmentation/multiplexing layer) on top of a transport layer, which is followed by an Ethernet layer. A protocol stack at a packet or Ethernet based BTS comprises the application layer on top followed by the FP layer, the segmentation/multiplexing layer, the transport layer and the Ethernet layer.
p-0060The transport layer shown in <figref idrefs="DRAWINGS">FIG. 1</figref> may be IP/UDP or something proprietary. The segmentation/multiplexing layer is introduced on the Ethernet/IP interface of the IWU <b>100</b> and the BTS between the transport and FP (Frame Protocol) layers.
p-0061AAL2 CPS packets are received at the ATM interface of the IWU <b>100</b> and the CPS payload is put into a receive (reassembly) buffer according to the CID value in the CPS packet. According to the invention, data from this receive buffer can be used even before a complete AAL2 SDU (FP PDU, consisting of multiple AAL2 CPS packets) has been received. When some parts of the already received data of an AAL2 SDU (FP PDU) are used for further processing, then those can be already removed from the receive buffer.
p-0062On the packet-based interface of the IWU <b>100</b> (e.g. Ethernet), transport data packets are used. A transport data packet contains a transport header and data from one or multiple AAL2 connections, separated by multiplex headers.
p-0063<figref idrefs="DRAWINGS">FIG. 2</figref> illustrates a procedure of building transport data packets using segments from FP PDUs from multiple higher layer connections (e.g. AAL2 connections) according to an embodiment of the present invention.
p-0064The transport header may be e.g. IP/UDP or some proprietary header, which can be used on top of Ethernet or any other packet based protocol.
p-0065As mentioned earlier, the multiplexed payload may contain either one or more complete FP PDUs or one or more segments. The multiplex header may contain a connection identifier, information about the length of the following multiplex payload and an indication whether this is the first or last segment of the initial FP PDU.
p-0066A new transport data packet is built together when a dedicated timer expires (limiting the introduced delay and ensuring continuous usage of resources) or when the resulting transport packet size has reached an upper limit.
p-0067If one of these conditions is fulfilled, then some or the complete amount of data is taken from the receive buffer of the AAL2 connection, the multiplex header is attached and then put into the new transport data packet. This may be done for one or multiple AAL2 connections, depending on several parameters like the initial trigger for sending out a transport packet (i.e. the above-mentioned conditions), the size of each segment and the priorities of the AAL2 connections.
p-0068Forming a new transport packet out of SSSAR PDUs as shown in <figref idrefs="DRAWINGS">FIG. 2</figref>, a segment of received data of an AAL2 connection <b>1</b> is included in the new transport packet with multiplex header <b>1</b>, and a segment of received data of an AAL2 connection <b>2</b> is included with multiplex header <b>2</b> into the new transport packet to be formed. The new transport packet consists of a transport header plus the segment with the associated multiplex header <b>1</b> plus the segment with the associated multiplex header <b>2</b>. The transport packet is further provided with a header corresponding to the used packet network, e.g. Ethernet.
p-0069<figref idrefs="DRAWINGS">FIGS. 3 and 4</figref> illustrate an embodiment of the invention in which the formed transport packets each have the maximum size. <figref idrefs="DRAWINGS">FIG. 3</figref> shows multiplexing of segments of several higher layer connections into different transport packets, and multiplexing new formed segments from different higher layer connections in one transport packet. Segments are taken from receiving buffers of these higher layer connections and are included into transport packets as described above, wherein each transport packet has the same maximum transport packet size. As can be seen from <figref idrefs="DRAWINGS">FIGS. 2 to 3</figref>, the size of each new formed segment to be transported over the packet network may be different.
p-0070Moreover, the transport packets may be formed by including segments belonging to a specific data unit into different transport packets which can be seen from <figref idrefs="DRAWINGS">FIG. 4</figref>. According to <figref idrefs="DRAWINGS">FIG. 4</figref>, segments of one higher layer connection are transported via two transport packets.
p-0071Thus, a transport packet may contain data from one or multiple higher layer connections (e.g. AAL2 connections), separated by multiplex headers. The multiplex payload may contain either a complete higher layer (e.g. AAL2) SDU (FP PDU) frame or only a part of it (i.e. a segment).
p-0072Then the complete transport data packet is sent out over the packet-based interface of the IWU <b>100</b>.
p-0073On the receiving side, e.g. the BTS shown in <figref idrefs="DRAWINGS">FIG. 1</figref>, the segments are buffered for each connection separately. When the last segment of a FP frame has been received (indicated by a special bit in the multiplex header), then the complete frame is given to the next layer for further processing.
p-0074<figref idrefs="DRAWINGS">FIG. 5</figref> shows a schematic block diagram illustrating functionality of a network entity <b>10</b> such as the IWU <b>100</b> in a more general way, the network entity <b>10</b> interfacing a cell based network such as an ATM network and a packet based network, in a direction from the cell based network to the packet based network. The network entity <b>10</b> shown in <figref idrefs="DRAWINGS">FIG. 1</figref> may be part of an Interworking Unit (IWU) or a network node such as an RNC or BTS.
p-0075<figref idrefs="DRAWINGS">FIG. 6</figref> shows a flow diagram illustrating a process of forming a new transport packet by the network entity <b>10</b>. The network entity <b>10</b> comprises a storing block <b>11</b>, a forming block <b>12</b> and a detecting block <b>14</b>. The network entity <b>10</b> may further comprise a receiving block <b>16</b>, a transmitting block <b>13</b> and a determining block <b>15</b>.
p-0076The storing block <b>11</b> stores or temporarily holds segments of higher layer SDUs (e.g. AAL2 CPS packet payload) received by the receiving block <b>16</b> from the ATM network (S<b>31</b>).
p-0077The forming block <b>12</b> is used for forming transport packets out of the segments of service data units stored by the storing block <b>11</b>. The stored segments of service data units belong to protocol data units (e.g. FP PDUs). The transport packets each have a size equal or less a determined maximum packet size. The forming block <b>12</b> forms (S<b>33</b>) a transport packet out of the segments of service data units stored in the storing block <b>11</b>. The forming block <b>12</b> may form the transport packet in response to a predetermined condition detected by the detecting block <b>14</b> (S<b>32</b>). The transport packet is formed irrespective of whether a complete service data unit has been received.
p-0078The determining block <b>15</b> determines the maximum size of the transport packets, e.g. according to link capacities, a delay budget, connection priorities, timer values per AAL2 connection, the Path MTU size (in order to avoid additional IP fragmentation), etc. The calculated maximum packet size is then used by the detecting block <b>14</b> to check whether enough data segments are present in the storing block <b>11</b> to form a packet with the maximum size, and if enough segments are available to inform the forming means to form the packet. The formed packet is transmitted by the transmitting block <b>13</b> to the packet based network (S<b>34</b>).
p-0079As mentioned above, the data stored by the storing block <b>11</b> may be segments of a higher layer SDU (e.g. segments of an AAL2 service data unit from AAL2 CPS packets), received from an cell based network, and the forming block <b>12</b> may form the transport packet in response to the detecting block <b>14</b> detecting the at least one predetermined condition.
p-0080The predetermined condition used by the detecting block <b>14</b> may comprise at least one of the following: <ul><li id="ul0005-0001" num="0000"><ul><li id="ul0006-0001" num="0085">a timer expires</li><li id="ul0006-0002" num="0086">a resulting transport packet size would reach the maximum transport packet size.</li></ul></li></ul>
p-0081Thus, the forming block <b>12</b> may form the transport packet out of all the data from stored segments of service data units in response to the detecting block <b>14</b> detecting a timer expiration, in which case the transport packet size will be less than the maximum size.
p-0082In addition, the forming block <b>12</b> may form the transport packet out of a maximum amount of data from stored segments of service data units in response to the detecting block <b>14</b> detecting the maximum amount of data fitting into the transport packet. In this case the transport packet size will be equal to the maximum size.
p-0083Moreover, the forming block <b>12</b> may form the transport packets by including data belonging to a specific FP PDU into different transport packets. The forming block <b>12</b> may also form the transport packets by including data belonging to different service data units into one transport packet. In this context, the forming block <b>12</b> may add an indication to the data out of which the transport packet is formed, the indication indicating a specific service data unit to which the data belongs.
p-0084According to <figref idrefs="DRAWINGS">FIG. 6</figref>, a new transport packet is formed by the network entity <b>10</b> and transmitted to the packet based network.
p-0085Processing in the other direction, i.e. from a network node of the packet based network via the interworking unit (e.g. from the BTS to the IWU <b>100</b> as shown in <figref idrefs="DRAWINGS">FIG. 1</figref>) to the cell based network is done similarly. However, on the sending side the complete FP frames may be given in one piece to the segmentation/multiplexing and transport layers. In the segmentation/multiplexing and transport layers transport packets are formed as described above, by dividing the FP PDU into one or multiple segments. In addition it is also possible to multiplex several smaller FP PDUs into a single transport packet. The complete transport data packet is then sent to the interworking unit (e.g. the IWU <b>100</b>).
p-0086At the IWU <b>100</b> the segments are removed from the transport packet and stored in an AAL2 SDU (FP PDU) transmit buffer for each AAL2 connection separately. <figref idrefs="DRAWINGS">FIG. 7</figref> shows this segmentation procedure. A segment from a transport packet belonging to a higher layer connection <b>1</b> is held in a transmit buffer for the higher layer connection <b>1</b>. As soon as enough data to fill at least one AAL2 CPS packet is available in the transmit buffer of the higher layer connection <b>1</b>, or the last segment of a FP PDU is received, the AAL2 SSSAR function starts to segment the AAL2 SDU (FP PDU) into CPS packets and send them out over the ATM interface as shown in <figref idrefs="DRAWINGS">FIG. 11</figref>.
p-0087<figref idrefs="DRAWINGS">FIG. 8</figref> shows a schematic block diagram illustrating functionality of a network entity <b>40</b> according to the invention, in the direction from the packet based network to the cell based network. The functionality of the network entity <b>40</b> may be contained in the IWU <b>100</b> as described above. The network entity <b>40</b> comprises a storing block <b>41</b>, a forming block <b>42</b>, a transmitting block <b>43</b> and a receiving block <b>46</b>.
p-0088<figref idrefs="DRAWINGS">FIG. 9</figref> shows a flow diagram illustrating a process of forming cells (segments of data units) by the network entity <b>40</b>.
p-0089The storing block <b>41</b> stores or temporarily holds data from transport packets received from the packet based network (S<b>81</b>), the transport packets comprising segments of FP PDUs. The forming block <b>42</b> forms cells (e.g. ATM cells) out of the segments extracted from the transport data packets and stored in the storing block <b>41</b>.
p-0090Segments are removed from the transport packets and may be stored in a section of the storing block <b>41</b> acting as higher layer SDU transmit buffer (S<b>81</b>). According to ATM, the AAL2 SSSAR function (which is part of the forming block <b>42</b>) segments the AAL2 SDU (FP PDU) into CPS packets and the CPS packets are packed into ATM cells (S<b>82</b>), which are then sent (S<b>83</b>) by the transmitting block <b>43</b> over the ATM interface as shown in <figref idrefs="DRAWINGS">FIG. 11</figref>. The forming of CPS packets to be sent over the ATM interface can be done even before the complete AAL2 SDU has been received. More generally speaking, the forming of segments to be sent over the cell based interface can be done even before the complete higher layer SDU has been received.
p-0091<figref idrefs="DRAWINGS">FIG. 10</figref> shows a flow chart generally illustrating the communication of data between a packet based network and a cell based network according to the present invention. In a first step S<b>61</b>, segments of data units are received. These segments may be segments distributed over a plurality of packets from the packet based network, and/or segments distributed over a plurality of cells from the cell based network.
p-0092In step S<b>62</b>, new data segments are formed out of the received segments of the data units, and in step S<b>63</b> the new data segments are transmitted, wherein the new data segments are transmitted irrespective of whether a complete data unit has been received.
p-0093The above described functionalities of the network entity <b>10</b>/<b>40</b> may also be implemented as computer programs running in an Interworking Unit, BTS and/or RNC.
p-0094According to the present invention, a method and apparatus for communicating data between a cell based network and a packet based network are provided. Received segments of a service data unit which are extracted from a cell based network interface and belong to protocol data units, are formed into transport packets, regardless of whether a complete protocol data unit has been received.
p-0095Moreover, received segments of transport packets, which are extracted from a packet based network interface and belong to protocol data units, are formed into service data units, regardless of whether a complete protocol data unit has been received.
p-0096It is to be understood that the above description is illustrative of the invention and is not to be construed as limiting the invention. Various modifications and applications may occur to those skilled in the art without departing from the true spirit and scope of the invention as defined by the appended claims.
Contents5
12 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8249057B1 | Cited by | United States of America | Applicant |
| US2013148672A1 | Cited by | United States of America | Pre-grant |
| US9112690B2 | Cited by | United States of America | Applicant |
| US8824476B2 | Cited by | United States of America | Search report |
| TWI501582B | Cited by | Taiwan Province of China | Examiner |
| US2011051669A1 | Cited by | United States of America | Pre-grant |
| US8045585B2 | Cited by | United States of America | Search report |
| US2009245260A1 | Cited by | United States of America | Pre-grant |
| WO0113599A2 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| WO03067921A1 | Cites | World Intellectual Property Organization (WIPO) | Applicant |
| US2002085564A1 | Cites | United States of America | Applicant |
| US2004076179A1 | Cites | United States of America | Search report |
| US2004090949A1 | Cites | United States of America | Search report |
| US2004213525A1 | Cites | United States of America | Search report |
| US2005141509A1 | Cites | United States of America | Search report |
| US2005157729A1 | Cites | United States of America | Search report |
| US5526349A | Cites | United States of America | Search report |
| US6393025B1 | Cites | United States of America | Applicant |
| US6539011B1 | Cites | United States of America | Search report |
| US6603766B1 | Cites | United States of America | Applicant |
| US6625171B1 | Cites | United States of America | Applicant |
| US6654376B1 | Cites | United States of America | Applicant |
| US6738384B1 | Cites | United States of America | Search report |
| US7136384B1 | Cites | United States of America | Search report |
| US7139271B1 | Cites | United States of America | Search report |
| US7248604B2 | Cites | United States of America | Search report |
| US7336607B2 | Cites | United States of America | Search report |
4 priority claims, no other members on record
Priority claims4
| Document | Office | Kind | Date |
|---|---|---|---|
| 05000916 | European Patent Office (EPO) | A | |
| 05000916 | European Patent Office (EPO) | A | |
| 05000916 | – | – | – |
| EP20050000916 | – | – | – |
62 transactions on the USPTO file
Allowed after 2 non-final rejections, 1 final rejection and 1 RCE.
- Non-final rejections
- 2
- Final rejections
- 1
- RCEs
- 1
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Correspondence Address ChangeC.ADB | C.ADB | |
| Application Is Considered for C of CCOFC | COFC | |
| Mail-Petition Decision - GrantedMP034 | MP034 | |
| Petition Decision - GrantedP034 | P034 | |
| Petition EnteredPET. | PET. | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| Correspondence Address ChangeC.AD | C.AD | |
| Correspondence Address ChangeC.AD | C.AD | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Final ActionA.NE | A.NE | |
| Mail Examiner Interview Summary (PTOL - 413)MEXIN | MEXIN | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Mail Notice of Restarted Response PeriodMNRES | MNRES | |
| Letter Restarting Period for Response (i.e. Letter re References)NRES | NRES | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Is Now CompleteCOMP | COMP | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Request for Foreign Priority (Priority Papers May Be Included)RQPR | RQPR | |
| Initial Exam Team nnIEXX | IEXX |
11 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| Fee paymentFPAY | FPAY | |
| AssignmentAS | AS | |
| Fee paymentFPAY | FPAY | |
| Certificate of correctionCC | CC | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP | FEPP | |
| AssignmentAS | AS |
Numbers
- Publication, DOCDB
- 7609702
- Publication, EPODOC
- US7609702
- Application
- 11086557
- Application, DOCDB
- 8655705
- Application, EPODOC
- US20050086557
Titles
- English
- Interworking between cell and packet based networks
Patent term adjustment
- A delay
- +702 daysthe office missed an examination deadline
- B delay
- +378 dayspendency past three years
- Overlap
- −32 daysdelays counted once
- Net adjustment
- 1,048 days
Classification
- CPC, 8
- H04L12/5601
- H04L12/66
- H04L2012/5656
- H04W4/18
- H04W28/06
- H04W92/02
- H04W16/32
- H04L69/08
- IPC, 6
- H04L12 28
- H04J3 16
- H04L12 54
- H04W4 18
- H04W28 06
- H04W92 02
- USPC, 2
- 370395600
- 370466000