Transport for wireless radio access networks

A radio access network includes a transport network layer; a radio network layer having a layer 2 network for communicating between entities within the radio network layer by exchanging datagrams having a predetermined format used only within the radio network layer. Accordingly, the present invention provides for a true decoupling at layer 2 between the radio network layer and the transport network layer. Addressing at layer 2 can enable both connectionless and connection oriented using an overlay connectivity model. Layer 2 in the radio network layer is implemented as an Ethernet network.

FIELD OF THE INVENTION

The present invention relates to transport for wireless radio access networks.

BACKGROUND OF THE INVENTION

FIG. 1illustrates a known reference model for a radio access network (RAN). A base station controller/radio network controller (BSC/RNC)10is coupled to a plurality of wireless base station12,14,16,18via a radio access network20. The radio access network can be modeled as a radio network layer (RNL)22and a transport network layer24and three planes intersecting those layers, a radio network control plane26, a transport network control plane28and a user plane30. The network may be leased from a service provider (SP) or owned by the wireless service operator.

In operation, the transport network layer (TNL) receives a request from the RNL22to establish a bi-directional transport bearer for datagram traffic. The request includes the end system address and transport bearer association received from the peer. It also includes the quality of service and resources required from the transport network. In summary it shall:Provide unique connection identifiers such that individual flows can be uniquely addressed for both user plane as well as control plane (eg VPI, VCI, CID in AAL2/ATM) [mandatory];Provide in-sequence delivery of PDUs to upper layers [mandatory];Support sending coordinated dedicated channels (DCHs) multiplexed onto the same transport bearer (i.e., frame multiplexing, e.g. AAL2/ATM) [mandatory];Provide proper mappings of required RNL bearer channels QoS to TNL resources (eg AALx in ATM) [mandatory]Provide transport signalling protocol used to setup and tear down transport bearers (eg ALCAP in 3GPP r3) [mandatory];Provide segmentation and re-assembly mechanism in order to fit to the maximum PDU size (i.e., R3 ATM AAL2 SSSAR layer function) [mandatory]

FIG. 2illustrates a known RAN network system model. The RAN network system model includes the wireless base station controller10, the wireless base station12and an intervening transport network (TRAN)40. The TRAN40includes points of attachment (PoA)42and44and intranetwork switching collectively represented by function block46. For the system model ofFIG. 2the current network connectivity model is a peering model. For the peering model: User traffic is “peered” with Service Provider's network at point of attachment (PoA) via rudimentary/sophisticated User Network Interface (UNI). In this model, user quality of service (QoS) requirements are snooped by the SP or signaled from user to the SP (via the UNI interface) in order to satisfy required QoS guarantees.

Consequently wireless datagrams need to be processed by both wireless end points and SP TRAN equipment. This means all sub-systems need to have common understanding of: QoS information, Signaling capabilities and Flow segregation ID across PoA.

The known RNL peering connectivity model imposes upon the TNL the need to also implement a peering connection-oriented model; current implementations of datagram addressing are peering-like, coupling RNL22(DCH-ID, etc) and TNL24(AAL2 CID, etc) identifiers.

Emerging connectionless protocols, such as IP are being proposed as the new TNL transport mechanism and will have to meet connection-oriented requirements

In order to use connectionless IP, development of mechanisms to offer connection-oriented capabilities to wireless TNL layer needs to take place.

SUMMARY OF THE INVENTION

An object of the present invention is to provide an improved transport for wireless radio access networks.

In accordance with an aspect of the present invention there is provided a method of operating a radio access network comprising: establishing a radio network layer; establishing a transport network layer; and communicating between entities within the radio network layer by exchanging datagrams having a predetermined format used only within the radio network layer.

In accordance with an aspect of the present invention there is provided a radio access network comprising: a transport network layer; a radio network layer including a layer 2 network for communicating between entities within the radio network layer by exchanging datagrams having a predetermined format used only within the radio network layer.

Accordingly, the present invention provides for a true decoupling at layer 2 between the radio network layer and the transport network layer.

In accordance with an aspect of the present invention a method of processing layer 2 datagrams within RNL is provided that facilitate decoupling thereof.

Addressing at layer 2 can enable both connectionless and connection oriented using an overlay connectivity model

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

Referring toFIG. 2, there is illustrated in a block diagram a known RAN system model implemented in an overlay model in accordance with an embodiment of the present invention.

For the overlay model: User datagram requirements are much simplified. The service provider (SP) offers quality of service (QoS) guarantees as part of the service in a point-to-point or point-to-multipoint (via Dedicated or Virtual Private Line service framework). Hence, the user datagram does not need to carry any flow segregation ID peering with SP, nor does it need to offer any signaling capability, nor any QoS information as the service leased corresponds to common denominator user flows characteristics, i.e. highest QoS.

Consequently, datagrams processed by wireless can be totally independent from SP TRAN datagram processing functions enabled via PoA edge translation (physical port-based mapping): This means each point of attachment (PoA)42and44provides an operational independence of: QoS, signaling and flow segregation technologies.

The wireless base station controller10and wireless base station12include wireless radio frames computing platforms. Host systems intercommunicating using either L2 frames or L3 packets as datagrams.

The network points of attachment (POA)42and44either map wireless datagrams into lower layer transport services (examples: DSx, STSx, OCs for dedicated PL) or actively switches the datagrams (examples: Ethernet Switching, MPLS, IP routing for virtual PL)

The transport provided by the TRAN40, as represented by a pipe48provides physical port-based, point-to-point flow of datagrams over dedicated or virtual Ethernet private line sessions with a specific service level agreement (SLA).

The cellular terrestrial radio access network (TRAN)40, typically uses private addressing space (examples, A/Z PL, IPV4/6, Ethernet Mac).

Referring toFIG. 3, there is illustrated in a functional block diagram a wireless base station and a base station controller communicating via a datagram service in accordance with an embodiment of the present invention. The base station function block12′ includes a radio frequency domain50, a digital domain52and a datagram service54. The base station controller function block10′ includes a mobility function60, a packet processing function62, a wireless application core steering64and a datagram service66. A datagram is an independent, self-contained message sent over the network whose arrival, arrival time, and content integrity guarantees are assured by network service and not by the datagram protocol capabilities. Datagrams can be either wireless radio frames or OA&M signals.

Referring toFIGS. 4aand4b, there are illustrated in block diagrams transport options for the datagram service ofFIG. 3. Behind the POA-edge (42and44), once the traffic is encapsulated, the carrier is free to use the most economic L1, L2, L3 switching fabric that provides desired SLA. The embodiments of the present invention are based on an overlay network system design, enabling carrier providers to operate TRAN (40) networks independent of wireless operator's equipment (10&12).FIG. 4aillustrates how a carrier frame80having an embedded Ethernet frame82can be transported using sonnet84as payload86or optical channels88as payload90.FIG. 4billustrates how carrier frame94and Ethernet frame96are combined to form a frame97, where the 2 optical Ethernet label98includes an Ethernet MAC adding100and where the optical Ethernet MPLS label102includes the Ethernet MAC address104.

Referring toFIG. 5, there is illustrated in a block diagram the main hardware components of the wireless base station and the base station controller ofFIG. 3.

The base station12includes a host platform switch110, a plurality of process modules111each having a plurality of application processes (AP)112. Similarly the base station controller10includes a host platform switch120, a plurality of process modules121each having a plurality of application processes (AP)122.

The application processes include radio modems, RLC & RRL S/W. Radio PDU may or may not contain AP-ID information for necessary for flow steering function performed at PM level111and121(second tier address options)

Each process module111,121has a single Ethernet MAC address (OUI=0). A simple packet steering function is performed by the PM111,121in order to send PDU to individual AP112,122(2 second tier address options).

Host platform switches110and120are Ethernet switching points that do not possess Ethernet MAC addresses (except for OAM&P agent, etc) as it performs layer-2 bridging algorithm. A direct 1:1 PM address and Host Switch port mapping is used for design simplicity.

For dedicated Ethernet private line the inter-host frame walk through is as follows: AP112,122are identified by STA (second tier address). PM111,121have a single Ethernet MAC address. PM frame steering function is based on STA information.

There is simple 1:1 relationship between Host Switch110,120port and PM111,121MAC address. Host switches frames based on FTA address information (i.e. Ethernet DA and SA) where a forwarding decision is based on destination address (DA) MAC/egress Port and learning tables that are populated via secondary addresses (SA) MAC/ingress Port information.

Host Switch110forwards frames to PoA44using PM DA MAC address information. TNL40simply encapsulates user flow with no regard of user address/QoS information as service is offered on dedicated port basis (non shared). Private Ethernet addressing space enables wireless operator to assign any type of networking identifier (examples: URL, IP, MPLS/LSP, ATM VP/VC, L2 Macs).

The overlay TNL network40point of attachment40,44forwarding is based on dedicated physical or virtual port mapping (examples DSx, STSx, LSP).

AP112,122addresses are mapped to Ethernet FTA& STA address space. Ethernet FTA can be learned or manually provisioned at AP driver interface. If automatically provisioned, Ethernet DA MAC addresses can utilize standard registration protocol (ie GARP, GVRP, or even other simpler methods).

The simple method referred here aims at leveraging the simple 802.1D bridging algorithm where MAC addresses are learned and aged out as a fundamental behaviour that can be exploited for end-host Ethernet MAC address discovery and thus simplify tremendously the software investment on each nodal system to perform such a task at boot time. The highlights are as follows:1) end host (e.g. BTS) that needs to discover the other end host(s) (e.g. BSC/RNC) can simply issue from the AP a specially VLAN-tagged broadcast packet to network (e.g. backhaul).2) This special VLAN-tagged broadcast (or VLAN-contained broadcast) restricts ENET pollution to only VLAN-aware switches and registered end-host MAC station. It also requires all ENET switch along the path to be VLAN-capable.3) Once the other host receives that special VLAN-tagged broadcast frame, it responds by issuing a Unicast back to the sender.4) Once sender receives the unicast frame, the process is over as both end hosts now has both respective destination MAC address for remaining of datagram exchange.
Inter-Host Frame Walkthrough Over EPL Service Framework:
AP<-> PM

APs are identified by STA148(second tier address). PM have single Ethernet MAC address. PM datagram steering function performed by host switch is based on FTA information146.

PM <-> Host

There is simple 1:1 relationship between Host Switch port and PM MAC address. Host switches frames based on FTA address information where forwarding decision is based on DA MAC/egress Port and learning tables are populated via SA MAC/ingress Port information;

Host Switch110forwards frames to PoA44using PM110DA MAC address information146. TNL40simply encapsulates user flow with no regard of user address/QoS information as service is offered on dedicated port basis (non shared). Private Ethernet addressing space enables wireless operator to assign any type of networking identifier (examples: URL, IP, MPLS/LSP, VLAN tags, L2 Macs).

TNL40Network point of attachment forwarding based on dedicated physical or virtual port mapping (examples Label insertion, MPLS-like, Martini, etc). QoS traffic management is implemented based on queuing model where statistical multiplexing is possible.

End Points Address Determination

AP addresses are mapped to Ethernet FTA& STA address space (seeFIGS. 7 & 8). Ethernet FTA can be learned or manually provisioned at AP driver interface. If automatically provisioned, Ethernet DA MAC addresses can utilize standard registration protocol (i.e. GARP, GVRP, or even other simpler methods) as described herein above.

Referring toFIG. 6shows functional components of the host platform switch ofFIG. 5in further detail. The host platform switch has an Ethernet address, a bearer function130which performs the 802.1D forwarding algorithm, and a control function132which requires an Ethernet & IP addresses to terminate host management house keeping tasks. Binding of Host Ethernet address with higher host-level provisioned address, such as IP address or URLs, can be accomplished by ARP or DHCP-like procedures.

Referring toFIG. 7, there is illustrated ethernet encapsulation for the datagram service for length encapsulation. Wireless datagrams for Mobile customer traffic (examples: direct radio frames (RFP) or RFP/AAL2/ATM or RFP/BCN, etc), as well as wireless host IP OA&M & control datagrams are encapsulated as Ethernet payloads144.

One or many wireless datagrams can be encapsulated (coordinated DCHs over single transport bearer*)

For 802.3 Ethernet Length Encapsulation the first tier address146includes 12 Bytes (2×48-bit) Destination & Source MAC are used as first tier address (FTA)146, and a second tier address148(STA) that is 8 Bytes total that contains a fixed LLC Header150[(3B) (DSAP=0xAA, SSAP=0xAA, Ctrl=0x3)] & SNAP Header152(5B) available for second tier address. The SNAP header152contains SNAP OUI (3B) and SNAP Pid (2B).

Intra-Host Ethernet Length STA Walk Through:

Host <-> PM

There is 1:1 relationship between Host Switch port and PM MAC address. Host switches frames based on FTA address information146where forwarding decision is based on DA MAC/egress Port and learning tables are populated via SA MAC/ingress Port information.

PM <-> Host

APs are identified by STA (148 second tier address). PM have single Ethernet MAC address. PM frame steering function is based on STA SNAP Header address152information, (i.e. fixed LLC header150fixed to DSAP=0xAA, SSAP=0xAA, Ctrl=0x03+SNAP header (5B-152). When using the Length encapsulation, the 2 bytes154following the SA field represent the actual length of data payload. The LLC being fixed, the SNAP OUI & SNAP Pid can be used (Pid=216available address space) to address higher-layer protocol (e.g. application).

Referring toFIG. 8, there is illustrated Ethernet encapsulation for the datagram service for type encapsulation.

12 Bytes Destination & Source MAC are used as first tier address (FTA)

4 Bytes VLAN tags (VPID & TCI) are available for second tier address (STA)

Intra-Host Ethernet Type STA Walkthrough

Host <-> PM

There is 1:1 relationship between Host Switch port and PM MAC address. Host switches frames based on FTA address information146where forwarding decision is based on DA MAC/egress Port and learning tables are populated via SA MAC/ingress Port information;

PM <-> Host

APs are identified by STA (160 second tier address). PM have single Ethernet MAC address. PM frame steering function is based on STA 802.1Q VLAN tag information160. When using the Type encapsulation, the 2 bytes162following the SA field identifies the nature of the client protocol running above Ethernet (e.g. IP uses Type field=0x0800). AP identification and steering is done via Tag Control Information (TCI)164field which contains 3-bits for QoS priority, 1 bit for control and remaining 12 bits for VLAN-ID, thus 212=4096 available addressable space to address higher-layer protocol (e.g. applications).

Referring toFIG. 9, there is illustrated in a functional block diagram second tier address assignment in accordance with an embodiment of the present invention

A mobile terminal user entity200having an application layer202and an L2204becomes associated with a base station12having a radio network layer22RNL MAC layer206. The RNL MAC layer206needs to be bound to the Ethernet208, which makes use of a L1 wrapper210.

For second tier address (STA) assignment there are three possible methods. Endpoints for end-to-end datagram communication are uniquely identified by FTA and STA. STA can be assigned by a manual212, learning214or connection oriented216procedures. RNL link setup signaling can be used to manage Host & Port address, that is, from an architectural perspective one does not have to rely on the existence of UDP/IP stack

Referring toFIG. 10, there is illustrated in a block diagram various point of attachment operational configurations possible using the datagram service ofFIG. 3.

224One POA44is connected to only one BTS12, with one port appearance on the BTS12HPS110. This is applicable to both configurations220and230.220One POA42port appearance on BSC10HPS20for each BTS12.236One POA44connected to more than one BTS12, with one port appearance on each BTS HPS10. This is applicable to both configurations220and230.230One POA42is connected to only one BSC10, with one port appearance on BSC HPS20for more than one BTS12.
POA Interface Addressing & Management
For22,236all TRAN traffic passing through the POA228,238is steered to the customer facing port (BTS12or BSC10). All Ethernet first tiered addresses146receive the same steering treatment to the customer port. Second tiered addresses are not processed by the POA. The steering function is manually provisioned at startup and does not change.
For220, all TRAN traffic passing through the POA222is steered to the corresponding BTS based on Ethernet first tiered addresses146. Second tiered addresses are not processed by the POA.

Steering function is manually provisioned or realized through an Ethernet learned/auto discovery process, as described with regard toFIG. 2.

Optional UNI signaled be applied for all BTS groomed traffic (logical channels) flowing over the high speed medium using second tiered addresses.

Embodiments of the present invention embrace an overlay model that enables TRAN POA-to-POA addressing to be independent from wireless equipment addressing. Addressing within the TRAN can be accomplished two different ways:A dedicated Ethernet Private line tunnel where the TRAN network40is used to tunnel traffic between two POAs42and44.A Virtual Ethernet switched service where the TRAN network40operates like a distributed Ethernet switch between POAs42and44.
In both cases the TRAN wireless traffic is encapsulated using any Layer 1, Layer 2, or Layer 3 networking scheme. Embodiments of the present invention described herein have emphasized an all Ethernet layer 2 approach, however the architecture foundation of the all Ethernet approach does not exclude encapsulating Ethernet frames at POAs42and44using either IP or SONET techniques. TRAN addressing scheme between POA can be any techniques; using one or both FTA and STAs methods. The only requirement is that TRAN FTA and STAs remain independent of encapsulated wireless equipment FTA and STAs.

Referring toFIG. 11, there is illustrated in a block diagram how a soft hand-off is handled using the datagram service ofFIG. 3. For simplicity the TRAN40is represented by an Ethernet switch46. The process for a downlink TNL multicast (Soft Hand-Off) is illustrated.

Today's RNL (RLC, etc) needs to perform packet duplication while in soft hand off mode.

An Ethernet-switched TNL offers integrated multicast capabilities where only objects needs to be exchanged between the BSC10and BTS10and BTS12(DCHsource, BTS-ID1, BTS-IDn, Event-ID).

If the Type STA option ofFIG. 7is used two methods is possible:

GARP signaling events triggered at power measurement messages passing a threshold value invoking soft-hand off operation of drift-BTS14. This results in GARP registration exchange for all BTS participating in soft-hand off operation. GARP tear-down triggered by power measurement going below a threshold forcing to leave multicast. This method needs the creation of new GARP multicast address specific for wireless multicast soft hand-off application.
Use VLAN registration during soft hand off scenario where contained frame broadcast is performed inside VLAN paths only (VLAN-contained broadcast). Here GVRP is used as part of registration/removal exchange.
GlossaryAP=wireless application process. That's usually physically instantiated at silicon/silicon island level but abstraction boundary can be extended up to board packaging level.PM=Process Module. Includes many AP processes. Typically physically instantiated at the board level but abstraction boundary can be extended up to shelves and frame packaging level.Host=Platform addressable entity. Include several PMs. Typically physically instantiated at the shelf level but abstraction boundary can be extended up to set of shelves and/or frame packaging level.Frame=layer 2 protocol information definition (eg ATM, Ethernet, FR, PPP, etc). Data link addressing visibility and link error detection done on a per hop/segment basis;Packet=Layer 3 protocol information definition (eg IP, IPX, etc). Network layer where addressing visibility is beyond hop/segment subnet.STA=Second Tier Address componentFTA=First Tier Address componentRFP=Radio Frame ProtocolALCAP=Generic name for the transport signalling protocols used to set-up and tear-down transport bearersEPL=Ethernet Private Line service;D-EPL=Dedicated Ethernet Private Line service. Not statistical multiplexing occurs and usually maps onto dedicated circuits (eg DSx/STx, etc);V-EPL=Virtual Ethernet Private Line service. Statistical multiplexing benefits exists applying QoS traffic management principles over queuing model;HPS=Host Platform Switch.