text:
A method to deliver traffic to a mobile node that is undergoing a hand-off between two Access Routers (AR) is described. The method of the present invention operates to perform the following. Decrease or minimize, delays between the time the old link breaks and the first packet is sent from the new link. Reduce or eliminate packet bursts from old to new Access Router (AR) when an old (existing) link breaks. Ensure that packets are neither lost nor duplicated during hand-off. Maintain Quality of Service (QoS) control of delivery order to the Mobile Node (MN). Make best use of multiple links during Make before break hand-off. Support both uplink and downlink traffic.
1. A method of operating a first access router, the method comprising:
increasing the transmission scheduling priority of packets in an existing packet flow directed towards a mobile node undergoing a hand-off from the first access router to a second access router, said increase in transmission scheduling priority being relative to packets directed to mobile nodes at the first access router which are not undergoing a hand-off;
communicating at least some packets from said existing packet flow over an existing downlink between the first access router and said mobile node following said increase in transmission scheduling priority; and
wherein said packets which are provided an increase in the transmission scheduling priority are a portion of all packets to be transmitted that are stored in the first access router when said mobile node commences hand-off.
2. The method of
3. The method of
4. The method of
5. The method of
6. The method of
7. The method of
8. A method of operating a first access router, the method comprising:
increasing the transmission probability of packets directed towards a mobile node undergoing a hand-off from the first access router to a second access router, said packets corresponding to a packet flow existing prior to initiation of said hand-off;
communicating at least some of said packets over an existing downlink between the first access router and said mobile node following said increase in transmission probability; and
wherein said packets for which the transmission probability is increased are a portion of all packets to be transmitted that are stored in the first access router when said mobile node commences hand-off.
9. The method of
wherein the step of increasing said transmission probability includes the step of increasing a transmission scheduling priority.
10. The method of
11. The method of
wherein the transmission probability increase is of an amount that causes interference from the hand-off of the mobile node to be shared between the mobile nodes at the first and second access routers.
12. The method of
wherein increasing transmission probability includes increasing the transmission scheduling priority of said mobile node undergoing said hand-off.
13. The method of
14. The method of
15. The method of
16. The method of
17. A first access router, comprising:
means for increasing the transmission scheduling priority of packets in an existing packet flow directed towards a mobile node undergoing a hand-off from the first access router to a second, said increase in transmission scheduling priority being relative to packets directed to mobile nodes at the first access router which are not undergoing a hand-off;
means for communicating at least some packets from said existing packet flow over an existing downlink between the first access router and said mobile node following said increase in transmission scheduling priority; and
wherein said packets which are provided an increase in the transmission scheduling priority are a portion of all packets to be transmitted that are stored in the first access router when said mobile node commences hand-off.
18. The first access router of
19. The first access router of
20. The first access router of
21. The first access router of
22. The first access router of
23. A first access router, comprising:
means for increasing the transmission probability of packets directed towards a mobile node undergoing a hand-off from the first access router to a second access, said packets corresponding to a packet flow existing prior to initiation of said hand-off, said increase in priority being relative to packets of other mobile nodes not undergoing a hand-off;
means for communicating at least some of said packets over an existing downlink between the first access router and said mobile node following said increase in transmission probability; and
wherein said packets for which the transmission probability is increased are a portion of all packets to be transmitted that are stored in the first access router when said mobile node commences hand-off.
24. The first access router of
25. The first access router of
26. The first access router of
27. A first access router, comprising:
a scheduling module for increasing the transmission scheduling priority of packets in an existing packet flow directed towards a mobile node undergoing a hand-off from the first access router to a second access router, said increase in transmission scheduling priority being relative to packets directed to mobile nodes at the first access router which are not undergoing a hand-off;
an interface for communicating at least some packets from said existing packet flow over an existing downlink between the first access router and said mobile node following said increase in transmission scheduling priority; and
wherein said packets which are provided an increase in the transmission scheduling priority are a portion of all packets to be transmitted that are stored in the first access router when said mobile node commences hand-off.
28. The first access router of
The present invention claims the benefit of U.S. Provisional Patent Application Ser. No. 60/328,468 filed Oct. 10, 2001 titled "METHODS AND APPARATUS FOR QUICKLY EXPLOITING A NEW LINK DURING HAND-OFF IN A WIRELESS NETWORK", which is hereby expressly incorporated by reference.
The present invention relates to communications system and, more particularly, to methods and apparatus for implementing wireless communications systems.
Some link layers technologies (or mac technologies), like flash-OFDM developed by Flarion Technologies, Inc., provide a number (we use 16 for illustration but could be more or less) of mac_streams that each can hold a small number (e.g.: 1-10) of packets in them. In some systems of this type there is a potential for anything up to 160 packets or more that could be stored in mac_streams for a particular MN.
IP Packets (e.g.: 40-1500 bytes) are typically segmented into smaller mac_frames (e.g.: ˜24 bytes) within each mac_stream. For purposes of explaining the invention we assume that Link Layer Automatic Repeat Requests (ARQs) includes frames but that they also retain the knowledge of packet boundaries as occurs in some systems. Also, for purposes of discussion, note that a packet may start or end within the middle of a frame.
During a hand-off a Mobile Node (MN) 110, e.g., portable receiver/transmitter, in a mobile (wireless) communication system connects to a new Access Router (AR) 106 and an indication is sent to the old AR 104 used by the MN 108 about the movement. The old AR 104 may then need to forward 126 to the new AR 106 any packets stored for that MN 108 within mac_streams at the old AR 104, and any subsequently arriving packets 122 for that MN 108, e.g., so that they can be transmitted 130 by the new AR 106 to the MN 110. A typical network scenario when using Mobile IP for general mobility management and inter-AR hand-off, is shown in
In addition, note that whilst the flows described are delineated as packets, it is equally applicable and beneficial to be able to redirect partial packets delineated as mac_frames, when part of a packet as frames has been sent 124 via the old link to the MN 108 before the old link was lost, necessitating the remaining frames in that packet to be forwarded 126 to the new AR 106 for forwarding 130 via the new link.
A range of hand-off scenarios can be envisaged in general, and specifically with this example network scenario, depending on the hand-off triggers from the link-layer and the IP layer, as well as the capabilities of the access links, ARs and MN.
In a L2 Break before Make (L2BBM), where the L3 can only be BBM by implication, the old link is lost, whether by accident or design, and the new link is only available after this event, and not before.
In a L2 Make Before Break (L2 MBB) with L3 BBM, the old and new links are available in parallel but the MN IP stack can only operate over one of these links at the same time and there is a finite time for moving to the new link and configuring the IP stack on the new link.
In a L2 Make Before Break (L2 MBB) with L3 MBB, the old and new links are available in parallel as are the MN IP stacks to exploit those links.
Where possible, it is useful to send all packets A 124 and B 122 over the old AR link before hand-off (C=0). However, in hand-off cases, where the old link is lost prematurely, the remaining IP packets and mac_frames at the old AR 104 should be transferred 126 to the new AR 106 so that they can be delivered 130 to the MN 110 over the new link, and hence effect a loss-less hand-off.
A first problem is apparent in that the old AR 104 needs to know what packets/frames must be forwarded 126 to the new AR 106 but only the MN 108 knows with certainty what was actually received 124 from the old AR 104. In addition, the new AR 106 needs to know what packets/frames need to be sent 130 over the new link to the MN 110. This is particularly difficult in cases where the links use Automatic Repeat ReQuest (ARQ) techniques to deliver mac_frames reliably by managing repeat attempts over access links, and by receiving reception acknowledgments from the MN 108, 110. In this case it is necessary for the old AR 104 to send its ARQ state forward to the new AR 106 along with the associated packet/frame data in a process known as Context Transfer. If too much data is sent forward (safety first) then duplicate information may be sent to the MN 108,110 over the two links (inefficient, reduced throughput and increased latency to other packets for the MN 108,110) whilst if insufficient data is sent forward then frame and hence incomplete packet loss may result.
A second problem is then clear in that the forwarded packets/frames 126 will take a finite time to reach the new AR 106 link, via a core (e.g., land based) network used to connect ARs 104,106, during which time packets/frames can't be delivered 130 to the MN 110 even if the new AR mac-layer or IP stack are already configured. This appears to the MN 110 as a lack of connectivity that will temporarily increase the latency of application packets in transit.
A third problem is then apparent if we try to forward over all packets/frames 126, for a specific MN 108 undergoing hand-off, as fast as possible to the new AR 106 to minimize this latency. The result will be a burst of packets on the backhaul uplink from the old AR 104, through the core network, and on the backhaul downlink to the new AR 106. This burst of packets 126 can interfere with other packets e.g. 128 on the links, potentially causing buffer overflows (losses), increased latency and/or reduced throughput for other application flows.
A fourth problem is that the competition between the forwarded packets/frames 126 for the handed off MN 108, 110, and other application flows for other MNs, normally occurs independent of the relative importance of the underlying application QoS (Quality of Service) requirements. If we forward all packets 126, 130 quickly to exploit the new link early, then we maximally affect other application flows, whilst if we smooth the forwarded flow 126, 130 over time then the new link is under-utilized.
In view of the above discussion it becomes apparent that there is a need for improved methods and apparatus for handling hand-offs, which address some or all of the above discussed hand-off problems.
1) QoS Control Over Forwarded Packet/Frame Delivery
In the old AR 304 and new AR 306, the packets and frames under delivery to a MN 310 will typically have been classified into QoS classes. Packets and frames of each class are then provided, based on the QoS class, the appropriate resources and scheduler behavior, for correct delivery over the access link. For example Voice packets will typically require much lower latency than bulk data and these relative performance bounds are well known. For discussion purposes, we will call the classified IP packets 322, and its constituent mac_frames 317 after those packets 322 have been fragmented at the link layer 314, to form a mac stream 316. In general, each packet 322 can start at any point within a mac_frame 317, following completion of a previous packet from the same mac_stream 316, with the location of the packet start therefore being offset from the frame start. The scheduler 318 will treat each mac_stream 316 communicated by flow 325 independently, from a QoS perspective, as each constitutes a sequence of packets 322 that must be delivered in order, and the scheduler can allocate resources to each mac_stream 316 to affect relative mac_stream 316 performance. Note that whilst the packets 322 in each mac_stream 316 are delivered in order, the ARQ mechanism associated with each mac_stream 316 should be able to deliver mac_frames 317 out of order to support retransmissions of errored frames.
For ordered delivery of IP packets 301 within each mac stream, obviously,
For reliable packet delivery within each mac_stream 316, obviously, all outstanding packets, frames and associated ARQ state should be forwarded to the new AR 306 and the MN 310 should internally transfer the ARQ state for the old AR link 326 to the new AR link 346.
In accordance with a first feature of the invention the transfer 328 of the said packets, frames and ARQ state is split up into multiple parallel and serial phases, with one parallel phase for each mac_stream 316, each parallel phase then being broken up into multiple serial phases. Said phases and associated data are marked in sympathy with the QoS marking of the associated mac_stream 316, and then treated during forwarding 328 and Context transfer according to the relative QoS marking between other competing mac_streams from the same MN 108, and relative to forwarded mac_streams from competing MNs undergoing hand-off, and relative to other application flows to stationary MNs.
To facilitate this, the forwarded IP packets and frames 328 are appropriately marked using the IP header Type of Service or Diff-serv Code Point (TOS/DSCP) QoS fields for the mac_streams e.g., 316, appropriate bandwidth is assigned on the affected links (old AR backhaul uplink, in the core, and on the new AR backhaul downlink) for forwarded packets as part of hand-off, and a sympathetic scheduling algorithm 318, 338 is employed on these links and in the old and new AR mac layer, to arbitrate between the multiple flows on any link to ensure timely and fair delivery of packets and frames on the links.
The parallel phases between each mac_stream enables each new AR mac_stream 336 to be configured and populated with data at a rate suitable for that mac_stream for that MN 310 and specifically enables different MNs to have differential hand-off performance according to their service level (e.g., gold, silver, bronze, etc.).
The serial phases enable the context transfer to be undertaken in multiple stages, as not all data in any mac_stream 316 needs to get to the new AR 306 early, immediately, or at all. Only sufficient data needs to be sent to avoid the new AR 306, and hence the MN 310, from being starved of critical packets. The appropriate set of serial phases for a particular MN 310 and mac_stream 316,336 depends on other techniques described below as well as scheduler QoS configuration in the old AR 318. In particular, given network conditions and by using packet timestamps and serial numbers, the schedulers used in a system implementing the invention can detect stale and unwanted mac_frames and discard them locally rather than fruitlessly forwarding them to the new AR 306 where they will be dropped anyway.
Hand-off 'aggressiveness' in terms of advanced forwarding for any MN mac_stream 316 is controlled by the number of competing hand-offs at any point in time, the amount of bandwidth/latency assigned to those hand-offs on a per service level basis, the service level and other QoS attributes of a particular MN 310, the QoS attributes of the mac_stream 316, the number of packets and frames 317 in said mac_stream 316 that need to be transferred 328 to the new AR 306, the complexity of the associated ARQ state that itself is dependent on the retransmission status of frames within the mac_stream 316.
The advantages of this invention is that we get QoS control of hand-off providing early fair use of the new link 346, strict ordering of packets 301 is maintained with minimal duplication over the air-link, hand-off burstiness (to this and other MN traffic) is prevented, packets can be intelligently dropped early, and hand-off aggressiveness is controlled and can be sympathetic to link/network conditions.
2) ARQ State Scheduling
One feature of this invention is to break the old link state into different serial phases/packets/QoS markings so that QoS queuing can treat them correctly. Specifically, rather than waiting until the old link breaks, the ARQ state is sent gradually over from the moment the hand-off process starts and the new AR address is known. In accordance with the invention each mac_stream 316 has an Identification (ID). Each packet in the stream has a Sequence Number (SN) and an Offset for example. This Offset indicates the ARQ frame number 317 for the start of that packet and the byte offset of the packet start within that frame. The position of each byte in an IP packet is then known in its constituent frames. The packet sequence number increases the effective size of the frame numbering space from what is normally a relatively small ARQ retransmission window (typically 256). The packet sequence number can be used to detect packets that get lost/re-ordered during forwarding from old to new ARs 304,306, and the mac_frame number 317 and offset from front of packet is used to locate any packet in a normalized ARQ space for each mac_stream 336 at the new AR 306. The combination of the packet SN and the ARQ SN, hence referred to as the SN, uniquely identifies a mac_frame 317,337 in the system, and the offset of the packet within a mac_frame 317, 337 enables the packet boundary to be tracked.
The complete ARQ window state for each mac-stream would be, for example;
i) SN_Rightmost: SN of the next frame to be sent.
ii) A vector of Boolean elements, where the length of the vector is ARQ_WINDOW_SIZ, and each element indicates whether the corresponding frame is to be retransmitted (i.e. is outstanding at the MN as an ARQ Ack has not been received at the AR). The 1st element corresponds to frame SN=SN_Rightmost−ARQ_WINDOW_SIZ, and the last element corresponds to frame SN=SN_Rightmost−1.
An example packet forwarding strategy is one feature of this invention. The packet forwarding strategy sends all flow A packets 322 down the old link 326 whilst sending 321,328 flow B packets 301 (that arrive at the old AR after MIP hand-off commences) to the new AR 306. Flow D will arrive at the new AR 306 directly of course as a result of the MIP hand-off signal at the HA 102.
We wish to ensure that the MN 310 receives flow A, then flow B then flow C packets in order in each mac_stream 337. Therefore, at the new AR 306, flow D packets are queued 341,332 behind flow B packets 301,321,328, and neither should be sent 349, 343, 345, 346 to the MN 310 until flow A has been delivered to the MN 310 and the old link 326 dropped in a planned hand-off.
However, the old link 326 can be dropped at any time as a result of radio effects, forcing the timing of the hand-off. In this case, all the flow A packets might not have been delivered over the old link 326, and no flow B packets 301 might have arrived at the old AR 304 for forwarding, or those that have arrived might not have arrived 328,332 yet at the new AR 306 for the new link 346. We therefore have to still ensure that flow A, B and D packets can still be delivered in order to the MN 310, and ensure that the right packets are available at the new link 346 quickly so that the new link 346 can be used immediately after the old link 326 is dropped. Note that the arrival of flow B packets 301, 321,328 at the new AR 306 does not help us here if there are still flow A packets unsent 325 at the old AR 302. We still need to delay flow B packets until the unsent flow A packets (and constituent frames) have been sent over to the NAR 306. Note that this is not strictly necessary from a packet re-ordering perspective because many applications can cope with some re-ordering. However this may be beneficial for some applications that cannot cope with re-ordering and hence a characteristic of the specific mac_stream 316 used by that applications for its packets.
An additional aspect of this invention is therefore to queue packets from flow A, B and D in such a way that ordered delivery is maintained. This means flow B packets 301 are not sent 349 to the mac_layer 334 in the new AR 306, and fragmented or shredded into mac_frames 337 until the remaining flow A mac_frames 317 from the old AR 304 are received 329,328,349,343 at the new AR 306 following the loss of the old link 326. In addition, flow D packets 341 from the HA should be held up 332 behind both flow A and flow B packets.
An alternative and preferred implementation of this invention is to instead keep flow B packets 301 in the old AR 304 and classify 311,322 and queue them 323 behind the flow A packets into the mac-streams 316, and then send 329 remaining flow A packets (and frames) and then flow B packets to the new AR 306 when the old link 326 breaks. Note that this means that the hand-off signal from the new AR 306 to the old AR 304 does not affect flow B routing and it is only the breaking of the old link 326, with packets still outstanding in the old AR mac_streams 316 that causes packets to be forwarded to the new AR 306 as flow C 328.
Thus, ordering is controlled at the old AR 304 rather than at the new AR 306 between flow A and flow B, whilst ordering between A/B 328 and flow D 341,342 is controlled at the new AR. Whichever strategy we use though, we still have potentially ARQ state 327 and a lot of packets/frames to send 328 to the new AR 306 before the new link 346 can be used (more to be sent if A/B ordering is controlled at the new AR 306 of course).
4) Flow A/B Delivery Control Observations
The earlier we start the hand-off (higher signal to noise radio power threshold for hand-off) the longer the old link 326 can be up to forwarding remaining packets, at an increased cost to the overall system because of transmit powers to/from two base stations and the occupancy of two sets of radio resources such as tones and session ids etc.
The faster we try to make the hand-off, increasing efficiency of the radio system, the less chance we will have to drain flow A (and optionally B) over the old link 326.
We cannot predict how quickly the S/N will drop on the old link 326 in the future, so some unplanned (i.e. unexpected and premature) old link removal will still occur, independent of the above timings.
We cannot send 328 remaining old link 326 flow A frames 317 instantaneously to the new AR 306, and the delay will depend on paths lengths, network buffer status, QoS settings on the transferred packets.
We can therefore increase radio costs to increase probability that flow A (and optionally B) is fully delivered over old link 326, then accept a certain level of unplanned drops and associated new link 346 delays whilst flow A (and B) information is transferred 328, or put in new mechanisms that increase the probability that flow A will be delivered over the old link 326 and increase the probability of the correct packet (by flow order per mac_stream) being available at the new link 346.
a) QoS Solution
One aspect of this invention is for the QoS scheduler 318 to assign increased priority to flow A packets from a MN 310 undergoing hand-off, relative to other MNs flow A packets not undergoing hand-off, so that for a given hand-off time, the probability of flow A packets across all mac_streams being delivered is higher. In such an embodiment, even if all packets are not drained over the old link 326, we have given the MN 310 earlier service than it would have got without a hand-off, which compensates for the future lack of service that the MN 310 will experience as a result of the remaining flow A packets being forwarded 328 to the new AR 306 after the old link 326 is dropped. The shorter the hand-off time, the more efficiently we use radio resources, so the greater the increase in priority we need to give to the flow A packets to make up for the potential flow A packet transfer 328 delay between the old AR 304 and the new AR 306.
Two limitations occur with this approach though. The first is that the increase in priority we can give the handing off MN 310 is limited by the effect of that higher priority on competing traffic to other MNs at the old AR 304. In the same way that the forwarded 328 flow A/B packets interfere with traffic on the uplink from the old AR 304 and on the downlink to the new AR 306, so transferring some of those packets over the old AR downlink 326 (in additional to normal QOS treatment for that MN) can interfere with other MNs traffic over the air-link. Conceptually, we would wish to bound the priority increase so that the interference from the hand-off of a MN 310 is shared equally between the MNs at the old and new ARs 304, 306.
The second limitation is that this oversending is still dependent on the characteristics of the air-link and at any moment we could find that, from a priority perspective, we would wish to preferentially schedule this MN 310 during the hand-off, but that at the same time the radio channel to that MN 310 is very bad due to instantaneous effects or planned transmit diversity cycle. Therefore whilst clearly useful this may not be a complete solution in some instances.
b) Early Packet Forwarding
As well as sending the ARQ state 327 early to the new AR 306, one aspect of this invention is for the old AR 304 to send a copy 329, 328 of a flow A (then B) packet to the new AR 306 when it reaches a mac_stream 316 specific trigger depth 317 away from the front of that mac_stream 316 queue. The closer a packet gets to the front of a mac_stream 316 queue, then the more likely it is to be approaching imminent service over the air-link 326, and hence the greater the need for it to be at the new AR 306, 346 when the old link 326 breaks. In particular, when a packet is in the ARQ loop and has seen service for one of its associated mac_frames 317, then on loss of old link 326, that mac_stream 316 cannot deliver any additional mac_frames 317 (including repairs of the sent frame) to that MN 310 from that mac_stream 316, 336, until the packet under service is sent to the new AR 346. Therefore as well as delaying service to this packet, any subsequent packets 322,323 will also be blocked.
As a flow A packet progresses in the mac 316, it is marked when it reaches the trigger point 317, causing it to be forwarded to the backhaul QoS scheduler 329 along with an update of the ARQ progress 327 since the last report, and the ARQ SN information for this packet. This information 328 can be preferably combined into a single special packet (general ARQ plus packet ARQ state plus packet) or sent as two packets (general ARQ SN update+packet specific stuff) or even three individual packets. When combining the packet ARQ and actual packet into a single inter-AR packet (for example), the packet itself would be encapsulated before forwarding to the new AR 306 as in MIP, but will now include the ARQ_synch information which could be implemented as a shim layer underneath the MIP header or as an IP custom option header or a custom encapsulation. Note that the new AR 306 strips the ARQ_sync information 327 from the frames/packets before it delivers to the mobile node 310 in streams 345, 346.
At some point later, the data packet will be sent from the old AR 304, and eventually arrive at the new AR 306, as part of flow C. The packet sequence number information enables the new AR 306 to detect packet drops and adjust the mac-stream 336 and ARQ SN appropriately 338. As the ARQ SN updates are received at the old AR backhaul QoS scheduler 318, it can report on the completion or dropping of a previously delivered data packet copy from the old link mac_stream 316, and hence cancel 329 the transmission 328 of that data packet copy to the new AR 306. In addition, by sending that ARQ update 327, 328 onto the new AR 306, it can delete packets from the mac_stream queue 336 at the new AR 306, that have been delivered successfully (or dropped) from the old link mac_stream queue 316.
Some examples of non-exhaustive Trigger policies, which can be used, are;
The QoS mechanisms will try to improve the chance of flow A packets being delivered over the old air-link 326. Meanwhile, packets of high QOS flows are duplicated and sent early in flow 328 to the new AR 306 so that if the old link 326 breaks, these high QoS/low latency flows will be unaffected by the hand-off.
The longer we can afford to maintain the old link 326 in a planned hand-off, the less useful are the mechanisms described here, but they will always be useful for dealing with the unplanned loss of the old link 326. The longer the old link 326 is up, the less efficient is our use of the overall radio system resources and so appropriate alternative use of backhaul resources to save those air-link resources may be preferable.
Note that the greater the bandwidth per MN 310, as a fraction of the cell resource, the greater the saving as the required time to drain flow A for that MN 310 increases. In addition, the greater the service level of that MN 310 then the less effective is the use of the increased priority over the air-link 326 to drain flow A. Finally, the more bursty the packet arrivals 301 are for MN 310, the harder it is for the scheduler to instantaneously provide sufficient air-link resources to drain flow A because those resources would normally be spread over a period of time (but this is potentially ok because the fact that it would be spread over time at the old AR 304 means that it does not need to be instantaneously forwarded to the new AR 306).
5) Overall Implementations
In one implementation, packet copies and ARQ update signaling 327, 328, 329 is minimized in the old AR 304, by using the old link mac_stream 316 memory to hold the flow A packets that have reached the trigger point 317 in any mac_stream 316, until they have been scheduled by the backhaul scheduler 318. In addition, but independently, to efficiently maintain flow A/B ordering and to enable flow B packets to also be delivered over the old link 326 during BBM or MBB hand-offs, flow B packets should continue to be delivered to the old link mac_stream queues 316 as this will ensure they are classified 311,322 correctly behind the flow A packets, will only be forwarded to the new link 346 when they reach the trigger point 317, and will avoid the need for the hand-off completion timing being tied in an artificial way by the amount of packets in flow A when the hand-off commenced (e.g., by the desire to drain flow A over the old link 326, and to send all flow B packets to the new link 346, which leads to the problem of old link 326 under-utilization if there are no/few flow A packets when hand-off commences, and subsequently arriving flow B packets cannot make use of the old link 326).
Similarly, at the new AR 306, flow A and flow B packets arriving 328 at the new AR 306 should be placed in a single queue 332,349,343,336 in delivery order. This means only arriving flow D packets to the new AR 306 have to be kept in a separate queue 341,332 so that they can be added after hand-off completion 342 behind flow A and flow B packets, instead of having three queues which would be required if flow A and B weren't combined in order at the old AR 304, and if flow B was sent 328 to the new AR 306 in advance of flow A packets 325.
For the combined flow A/B queue at the new AR 306, this queue can be implemented at the IP layer 332 so that ARQ updates 328 can be efficiently processed without having to traverse the IP/mac interface 349. The IP A/B plus D queue 332 would only be pulled into 349 the layer 2 mac_streams 336 at the new AR 306 after the old link 326 is lost and the MN 310, 310′ sends a request to use the new link 346. This is because we wish to delay fragmentation 334 of the IP packets into mac_frames 337 until the final required packets (for delivery to the MN 310 from the new AR 306) are known. This avoids the ongoing intermediate complications arising from the reformatting of the mac_frames 337 (offset and ARQ SN start) due to the variable length of IP packets, as any packet that has been copied 329,328 to the new AR 306 is completed at the old AR 304, or as forwarded packets 328 are reordered during forwarding or retransmitted or lost during forwarding. This also saves linked list manipulations if the ARQ SN space and associated mac_frames 337 are implemented as a linked list of address locations pointing to the start and stop of each mac_frame 337 of each packet in mac memory 336. Note that the transfer 349,343 of these packets into the mac-layer 336 could still be made before or after the final ARQ state information 327,328 is received from the old AR 304 on loss of old link 326.
An additional aspect of this invention is to send the IP queue 332 to the mac layer 336 before the final ARQ information 327,328 is received and restart sending from the front of the first packet in each mac_stream 336. This ensures that sending 345,346 can commence immediately the new link 346 is set-up, and is decoupled from the arrival of the final ARQ state 327,328 because there is a chance of this state being either delayed or dropped in error. The effect of this is that the MN 310 may receive duplicate ARQ SN transmissions, for mac_frames 317 that it signaled that it had received over the old link 326. This looks to the MN 310 like a false retransmission (a known ARQ possibility) that is caused by an ACK from the MN 310 being converted to a NACK at the AR 306 as a result of a transmission error. In this case though, it occurs with the addition of an increased delay (and SN evolution) between the original mac_frame 317 being sent (and ACKed) and the unnecessary retransmission 337 being made. This is because in one exemplary example of such an ARQ system, the receipt of the NACK blocks the sending of any new mac_frames 337 until the retransmission processing is completed, which bounds the ARQ SN evolution that can occur between sending a mac_frame 337 and receiving the associated NACK (propagation decode/encode and processing delays). This increased ARQ SN evolution can be handled provided the SN space cannot wrap in this time. It is therefore important that incremental ARQ SN progress information 328 is sent from the old AR 304 to the new AR 306 to minimize this duplication and avoid the wrapping, or the information 328 should include the packet SN information as well and be exchanged with the MN 310 before sending over the new AR link 346 (new AR 306 to MN 310 report). The MN 310 can then simply and safely compare the SN of any mac_frame 337 with its own SN state, during hand-off, and reACK the retransmissions even if the contents of the mac_frames 337 have been corrupted because the contents 317 have already been received at the MN 310 via the old link 326.
Additional protection from this ARQ SN wrap is provided of course if the IP packets 332 are not sent to the new link mac layer 336 until the final ARQ state is received 327,328. An additional aspect of this invention is therefore to send this final ARQ state information from the MN 310 to the new AR 306. This is useful whether or not the IP queue 332 is sent to the mac layer 336 with or without old AR final ARQ state 327,328. If the old AR final ARQ state 327,328 is not received, and the IP queue 332 is sent to the mac_layer 336, then the MN 310 final ARQ state report to the new AR 306 will be delivering very similar (but more accurate) information and will therefore minimize unnecessary retransmission. Even if the IP queue 332 is sent to the mac 336 after reception and application of the final ARQ state 327,328,344 from the old AR 304, the MN 310 has more accurate information on the ARQ state for what was actually received by the MN 310 (as opposed to what was sent by the old AR 304). Therefore, the MN 310 sending its final ARQ state information to the new AR 306 will suppress additional unnecessary retransmissions.
6) MBB ARQ Correlation
In the next aspects of this invention, called ARQ correlation, the tracking of the ARQ SN state 318 across multiple parallel AR links 326 during L2, and the sending of packet copies 329,328 to the new AR 306, enables the system to support the transmission of mac_frames 317, 337 from the same packets to the MN 310 in parallel from multiple ARs 304,306. The MN 310 will, for example, be able to select mac_frames 317,337 from either (any) link 326,346 for the same packet and will correlate ACKs and NACKs across the two links 326,346 so that successful mac_frame 337 reception over the new link 346 will result in an ACK being sent over both the old and new links 326,346 even though the mac_frame 317 from the old link 326 was received in error. ARQ update reports from the MN 310 can then be sent uplink to the ARs 304,306 (and exchanged between ARs 304,306) to prevent one AR 306 attempting to send a mac_frame 337 that has already been received 317 from the old link 326, and has the additional benefit of avoiding the need for the two links 326,346 to be synchronized (same mac_frame must be sent at the same time as in CDMA soft-hand-off). As the two links 326,346 have different error characteristics, loads etc so their ARQ spaces will move relative to each other enabling both to contribute to the safe and efficient delivery of each packet. This mechanism will reduce the required S/N ratio required on a candidate new link 346 and for dropping the old link 326 because the combination of the two links 326,346 S/N ratio is reducing the effective BER, as in CDMA soft-hand-off. This is likely to produce operational and efficiency benefits for MBB capability.
7) Uplink Equivalents
In accordance with additional features of this invention, covering the case of the uplink transmission direction, the old AR 304 sends partially received packets 328, in the form of a subset of its component mac_frames 317, to the new AR 306 along with its final AR state 327,328, after old link breaks 326. The scheduler 318 is organized so that during hand-off whole packets are given higher priority than normal so that if a packet is started it is quickly completed in the uplink direction. These partially received packets potentially need to be sent 328 as soon as they are received, rather than as a block for the QoS reasons covered for the downlink direction. With early forwarding we therefore also send updates 327,328 to the old AR backhaul interface and the new AR 306 as whole packets are completed. The new AR 306 may or may not send any packets to the backhaul until the final ARQ report 327,328 is received from the old AR 304 (although the cost of sending a whole packet unnecessarily here is much less in terms of bandwidth although it does result in a duplicate packet (one from each AR 304,306)) towards the session peer of the MN 310 undergoing hand-off. Therefore, the MN 310 should send its uplink final ARQ state to the new AR 306 because this provides faster delivery of this information to the new AR 306, as well as additional reliability, for the equivalent information from the old AR 304 although in this case it is the old AR 304 information 328 that is more accurate. Finally, soft hand-off involves the correlation of the received frames 317 from the old link 326, with the frames 337 received over the new link 346, in the new AR 306, so that packets can be sent when fully formed irrespective of where each component frame was received. The ARQ state and packet sequence number information from the two links 326,346 enables this correlation to be made. The potential loss of a mac_frame 317,328 between the old AR 304 and the new AR 306 can be dealt with in one of two ways. They can be sent using TCP/SCTP retransmission capabilities or the new AR 306 signals to the MN 110 information on outstanding mac_frames 337 for a packet so that the MN 310 resending over either link 326,346 can repair this frame loss. This acts as a very slow ARQ repair mechanism and requires the MN 310 to keep packets until a packet completion event, containing a packet SN is received from the new AR 306.
Patent Citations
Non-Patent Citations
Referenced by
Legal Events
Original Image


text:
October 29, 2012
Pumpkin soups come and go, but this one has staying power. It is absolutely creamy and rich-a warm dish for a fall evening. Thanks to one of our favorite cooking channels: OriginalNakedChef
Image Sources:
Related Articles
- 5 Best Gluten Free Pumpkin Cheesecake Recipes
- Allergy Friendly Roasted Pumpkin Seeds 3 Ways
- Wheatless Wednesday: 3 Must Try Pumpkin Recipes
- 3 Best Gluten Free Cranberry Desserts - Cranberry Craze Pt 4
- 5 Best Gluten Free Acorn Squash Recipes
- Seriously Best Ever Bourbon Cranberry Sauce - Cranberry Craze Pt 2
- 5 Must Try Gluten Free Pumpkin Cookie Recipes - Allergy Friendly
- Easy DIY Pumpkin Marshmallows and Hot Chocolate Recipe
- Best Ever Cranberry Sauce with Pinot Noir & Hibiscus
- Best Ever Gluten Free Stuffing Recipe - Just In Time for Thanksgiving
Related Recipes
- Homemade Pumpkin Muffins
- Pumpkin Crème Soup with Shrimp, Cream Cheese and Basil
- Best Ever Cornbread Dressing
- Pumpkin Carrot Soup
- Apple, cinnamon and walnut rolls + cream cheese crispy rolls!
- Curried Pumpkin Seeds
- Hot Pumpkin Spice Buttered Rum
- Pumpkin-spice cake
- Gluten Free Dairy Free Pumpkin Spice Cupcakes
- Pumpkin Spice Waffles with Walnuts
Want more from Foodista? Sign up below!

subset: commoncrawl


text:
Freaking News
Funny Cowboy Pictures
Lyndon B Johnson Cowboy.
Funny cowboy rabbit
Member reactions:
... nice look in cow boy style and i am freaked to see the Gun is replaced with Carrot very funny
Great Job. I Think it would have been much better if you had added a few bushes of tumble weed rolling by.
Impressive, but I'd change the hands for paws too
Funny The Stone Cowboy
Made with the source pic only, I hope you like it...
Member reactions:
Mind blowing chop.... great work using only with the source pic... I love to see those two guns attached to the pic its really freaky wonderful work done
Great architectural and creative artist here fantastic pose Love it :-*
Fantastic work with the source, Mark. Congrats on a well deserved gold.
Funny Cowboy on Wanted Poster
Member reactions:
Thanks very much,SplatShot,D-man and pcrdds
Great composition looks like a real classical poster good job with the gun shots and the smoky fire from the gun wonderful composition created love the wordings -- Ass chopper
Great chop BW he's going to need plastic surgery to hide around here
I guess I gotta practice my ass chopping, great work nepaguy...I love this one
Thanks, a whole bunch everyone for the kind words.....I enjoyed making this one.
Funny Bashar Assad the American Cowboy
Member reactions:
Nice work-horrible possibility. probably move here and open a chain of Pizza restaraunts.
Excellent .... nice cleaner and brighter image. Good to see the Bigger heads nice thought All the best i like this entry
Very cute but she's way too pretty for him.
Thank you Rajesh, Eric, Pcr bad boys take all the beautiful girls, Balodiya Thanks everybody for the comments.
Now he's living the American Dream. Awesome image.
Thank you so much Steve, Ricky, LunaC, Crusader, Bill..
Zuper smooth work. Assad looks like a geek here, . Congrats on the bronze, Sun.
Sorry Sunshine, I've been away a little while just wanted to say congrats on the bronze great work.
Funny Child Cowboy in a Saloon
Member reactions:
Really awesome remake for the son. His mom is the bartender, hahaha.
U freak me boy, bar tender -mom's business ppl on queue.
Excellent Makeover of a Kid into a old man. even shadows were perfect in this image, and stopping for a drink remembers my old university days
Funny The Wild Mouse Cowboy Riding a Squirrel
Member reactions:
So sweet and lovable image, the mouse with a cowboy cap is amazing its as pure as honey like this
Fantastic job done The mouse looks great in the Cow boy Look
Great work . . . ready for a children's book.
Yet again, work of art from Mr. Mark. Congrats on the silver.
Nice to see all this nice comments..... I'm happy you enjoy my chops
Funny Herman Cain the Singing Cowboy
Sing, flirt and wear a cowboy hat...perfect.
Member reactions:
Great job changing the color of the ... Cowboy's skin.
Baby Cain.. How's wheather out there..
Funny Joe Biden Cowboy on Turkey Farm
How to get the freshest turkey
Member reactions:
Lots of work and creative. Love the turkey birds.
Thanks, Sunshin3. Thanks, Disasterman. Thanks,dsbinfo2011. Thanks, deaddog.
Thanks, rajeshstar. Thanks, ericnorthend. Thanks, ArchNemesiS.
Congrats Paul. Cowboy Joe's Turkey Roping Ranch. What will you think of next.
Congratulations Cowpoke. Mighty fine work here.
Thanks, dd. Thanks, G-Man. Thanks, Riccardo.
Way to go Paul , Loved this one you did ...
Gobble gobble, this is goood. I always knew Joe had a thing for turkeys Congrats on the bronze, Paul.
Funny Andy Rooney the Cowboy
Member reactions:
that's really cool work sunny big congrats on the gold dear .. Keep rocking
For the rest of us who compete, could you please stop being so good at this. On second thought, don't quit. I love looking at your work. Congrats..
Yippee-Skippy. Saddle-UP Pardner. Congratulations.
Congrats on the gold sunshin3 great work.
Joan, Mammabear, Paul , Best4best, Kratos, Ganmerland, Disasterman, Geri, Boulpix, Iboudesign many, many thanks I appreciate a lot your comments.
For more funny photoshop pix visit
Freaking News front page


text:
About this Vendor
Picturesque Mountain Venue for Your Special Day
Nestled in the beautiful Sierra Nevada Mountains near Lake Tahoe, Sugar Bowl's historic lodge serves up a unique setting where the resort can be yours for an unforgettable private wedding. Sugar Bowl is known for its picturesque setting, gourmet food, imaginative menus and beautiful presentations.
Amenities + Details
Indoor Ceremony Area
Kosher Available
Liability Insurance
Liquor License
On the Water
Onsite Catering
Onsite Overnight Accommodations
Onsite Parking
Onsite Wedding Consultant
Outdoor Ceremony Area
Outdoor Reception Area
Outside Caterers Allowed
Site Fee
Tented Area
Valet Parking
Wheelchair Accessible
For more details about amenities, please message the Venue.
Banquet/Reception Hall, Hotel/Resort, Restaurant, Unusual/Alternative
Contact Info
Simply the bestReviewed on 9/25/2013 Meredith B
Can I give 10 stars!? Sugar Bowl was the perfect place for our wedding! We knew we wanted an outdoor location for the ceremony and the venue, and we are also avid skiers so the chairlift ride was on the top of our list as well. In addition to the perfect mountain setting, the staff at Sugar Bowl is out of this world. Meghon and her team were attentive to our every need without being overbearing. They supported every creative idea we had and made practical suggestions along the way - but they let us plan our own twist on everything, which is something that is very undervalued in many planners. It was also great that Sugar Bowl was a one-stop show for us. They took care of the catering, the bar, the flowers, and the rehearsal dinner and after party spots. They handed out welcome bags to the hotel guests as they arrived, and were so attentive throughout the entire weekend. The entire staff has a great attitude and that really made all our guests feel comfortable. Overall, our experience with Sugar Bowl was phenomenal and I wouldn't change a thing about it. Many guests told us that our wedding was the best and the most fun wedding that they have ever attended. You will not find a better vendor or service team anywhere in the Reno/Tahoe area! Meredith and Dan Herr
Sugar Bowl summer weddingReviewed on 9/20/2013 Emily M
Coordinator Meghon Shrewsbury goes above and beyond to provide excellent service, communicating all the way through the process. Though planning a wedding involves many details, the staff at Sugar Bowl made sure that every question was answered and handled all elements big and small with aplomb. A beautiful setting where many of your guests can stay on site and even ride a ski lift to the top of the mountain, Sugar Bowl offers a very unique and memorable wedding experience. Where some venues tend to nickle and dime you at every turn, Sugar Bowl was excellent in providing amenities such as heat lamps, parasols and other general decor for no extra charge. We would not hesitate to recommend this site to future couples!
Best day Ever!Reviewed on 9/17/2013 Katie H
My Husband and I had an amazing day. Sugar Bowl was a perfect place to make such amazing memories with family and friend that we will remember for the rest of our lives. Sugar Bowl brings a special touch to the wedding weekend. Having the hotel for only wedding guests makes it special; it is truly an exclusive get away weekend with the people you love. The chairlift was a very special touch to the occasion. Our guests really enjoyed it. The Sugar Bowl staff was incredible. I honestly cannot think there is a more attentive staff out there. They were incredible with every detail. The venue looked absolutely gorgeous and the food was delicious. Everything with Sugar Bowl was fantastic. I could not have asked for a better place to get married. There is not one thing that I would have changed. Sugar Bowl exceeded our expectations. Thank you!
AmazingReviewed on 9/30/2014
Our wedding experience at Sugar Bowl was absolutely amazing and perfect. Our plans started with our family arriving on Friday and staying for the weekend. Friday–Lake Mary barbeque and movie night- As our guests started arriving, we had a casual event to start off the weekend. Early in the day we brought our own coolers and snacks and enjoyed the relaxing and beautiful location. We enjoyed paddleboards, kayaks, etc. on the lake, tossed horseshoes and played a few of our own games we brought along. We didn't have a wedding party so instead of having a rehearsal dinner, Sugar Bowl set up a great barbeque for us. Later, we enjoyed a movie under the stars, popcorn and s'mores around the fire pit. Sugar Bowl put everything together so well and really took care of everyone. Saturday–Wedding day- Our ceremony was set up perfectly. It was simple and elegant just as we had wanted, with trees, wildflowers and Mt. Disney as a backdrop. After our short ceremony, the chairlift fired up and took us all to the top for drinks and appetizers. The view is amazing and it was such a great addition to our event. This is such an awesome option that Sugar Bowl offers and we couldn't imagine not having it part of our wedding memories. Once we returned, our reception was on the deck, which was perfectly set up. The dinner buffet was beautiful and the food was incredible (yes, we were able to enjoy our dinner). We chose not to have a traditional wedding cake so we had Sugar Bowl prepare a dessert for us. They prepared an amazing strawberry shortcake that was fantastic. The night moved into dancing and celebrating with a perfect intimate setting under the mountain stars. We can't say enough how unique and beautiful Sugar Bowl is and the privacy of having the resort to ourselves made it such a special event for our friends and family. Meghon was wonderful to work with and kept us on track through all of our planning. We didn't realize how many details needed attention but Meghon worked with us on the details that were important to us and took care of the rest. When we made it to the day of our wedding, we were relaxed knowing that we were in good hands. Meghon also did our flowers, which came out so beautiful. We selected some of the flowers we wanted and left it to her to put together what we felt were perfect arrangements for us. We started working with Meghon long before we booked our event and she was there for us even after our event was over. During both the barbeque and the wedding, we also worked with Pat who we were quickly impressed with. To be blunt, Pat is a pro who kept every detail of our day on track. Some of the smallest details can mean so much and we really appreciated how well he took care of us. While you might expect that the bride and groom be treated extra special during their wedding weekend, we heard from our guests that all of the staff they encountered was incredibly nice and helpful. From the wait staff, the bartenders, the front desk and to those working in the background cleaning rooms or setting up, everyone was polite and courteous. Long after our weekend wedding has ended, our friends and family (and us) are still raving about what an awesome wedding we had at Sugar Bowl. It is such a unique venue and a hidden treasure. Sugar Bowl, specifically Meghon, worked with us to create a custom fit wedding that matched us perfectly and we are amazed at how wonderful it all turned out. THANK YOU!!! Lee & Wendy Wells
Dream Wedding - Dream VenueReviewed on 9/28/2014
I cannot say enough amazing things about Sugar Bowl Resort. From our first meeting with Meghon to our wedding day we felt completely comfortable and supported throughout the process. Meghon and her team do an excellent job supporting the bride and groom, family and guests throughout the entire planning process and wedding weekend. I had multiple people comment on the "excellent service" and "attention to detail". Everything went off without a hitch thanks to Meghon's experience and expertise! It was the wedding of our dreams in our favorite place on earth. I would highly recommend it to any bride considering it as their venue.
Still in awe of how AMAZINGLY things wentReviewed on 9/20/2014 Rachel H
My husband and I got married at the Sugar Bowl Village Lodge on August 23rd. Before I get into just how awesome the staff was the weekend of our wedding, just a few reasons that we chose Sugar Bowl: 1. Compared to the outdoor venues we were looking at the in the San Francisco Bay Area and the other ski resorts in the area, Sugar Bowl was an absolute steal! Plus, included in the price is Meghon, their in-house wedding planner, who seriously kept me sane during the planning process, as well as free lift tickets when you come to do your tasting. 2. The Village Lodge is yours for the weekend. No other people to deal with. Just you and your loved ones. The bridal suite is also comped. 3. It's absolutely beautiful, and the weather is amazing during the summer. We actually had an organized hike during the weekend, and it turned out amazingly. As for the wedding itself, I am definitely a Type A person who did a ton of DIY before the wedding. I showed up to Sugar Bowl Friday afternoon and was tired, stressed, and worried about how things would turn out. Come Friday night, though, I was completely relaxed and was able to truly enjoy the wedding weekend. Every time I turned around, something else had been set up perfectly by the staff--decorations, cake, flowers, DJ equipment. I didn't have to lift a finger all weekend. They coordinated everything with the vendors as well. They took care of the entire rehearsal dinner, the post-rehearsal festivities, the wedding, reception, and Sunday brunch. Literally, everything was perfect, and this was huge because it let me bask in the happiness of marrying the man I love. Other people even commented that the staff were able to solve every problem before the guests even knew it was a problem. There's also a lot of freedom to customize your wedding into something that reflects you and your partner. Meghon was totally open to all our ideas (even the crazy ones!). We had hiking, yoga, lawn games, post-rehearsal pizza, bride & groom cocktails, and late night s'mores. They also will do customized menus, though we stuck with one of their packages, and it was great. I would also recommend doing the Disney Lift if it fits within your budget. Guests are still commenting how fun it was. Every single one of our guests (even the grandparents!) went up the lift. On the way up, you'll also have some alone time to just sit with your new husband or wife and enjoy the view. Honestly, looking back, it was just a perfect weekend because of the amazing venue and staff. I am so happy that we chose Sugar Bowl.
Medium wedding? SB is the best!Reviewed on 9/19/2014 Sarah G
SB was perfect for us! We wanted a wedding near Lake Tahoe for around 100 people at a reasonable price. Meghon was very willing to work within our budget for both the site and food/drink options. We opted to use the Lake Mary location for a lunch time wedding with the SB chef's awesome BBQ lunch spread. Amanda was so helpful as our day-of coordinator - between Amanda and our DJ, we didn't have to worry about anything the entire day! There was a minor hitch early on with the speaker system we rented from SB, but Amanda was able to have it rigged just in time for the ceremony. Another set of speakers was brought in by the SB staff right after the ceremony for the dancing and Amanda comped us the cost of the speaker rental for the (very minor) hassle. The staff, food, and view were perfect - couldn't have asked for a better day!
Best wedding venue EVER!Reviewed on 9/18/2014 Nicole T
Sugarbowl is amazing. We originally chose the location because of sentimental value (my husband taught me to ski here) but were blown away at what a perfect wedding venue it turned out to be. Staff are always friendly and go above and beyond. The wedding co-ordinator Meghon was so easy to work with and always made herself available whenever we needed something. She also did our flowers for the wedding and they were gorgeous. She worked with what I wanted but added her own touch and they turned out beautifully. Both my husband and I grew up in Canada so most of our guests had travelled quite a ways to be at our wedding. Sugarbowl was such a special place as you have the whole resort to yourself for 3 days. It was a spectacular setting to have a family reunion. Many of our family members had never been to Tahoe and were blown away. Everyone said it was the best wedding venue they had ever experienced. We did the chairlift for cocktail hour and had drinks and appetizers at the top of the mountain. It was spectacular and worth every penny. The food was delicious!! We were very impressed and everyone was raving about it. The fire pit that was lit every night was also a highlight. Smores for the kids then late-night talks with our family and friends sitting in Adarondak chairs around the camp fire was a great way to cap off the evenings. The prices were reasonable and the co-ordinator Meghon made suggestions to help us stay within our budget. There were no surprises when we saw the bill. I would would say that Sugarbowl as the perfect wedding venue. I have no regrets and would have my wedding there again in a heartbeat. We have perfect memories of our wedding day thanks to Sugarbowl.
Most amazing wedding venue!!Reviewed on 9/18/2014 rachel s
We had just gotten married last weekend at Sugar Bowl and it was simply incredible. Almost every single guest let me know it was the best wedding they had ever attended. The entire weekend was seamless with the on-site wedding coordinator Meghon behind the scenes for everything. This had to have been a hard task, as we had activities and things planned as early as Thursday night through Sunday morning. I couldn't have imagined a more perfect wedding and am SO happy we chose Sugar Bowl!!
Sugar Bowl WeddingReviewed on 9/17/2014 Lauren B
I got married at Sugar Bowl Resort this past July and it was a perfect venue for an outdoorsy couple who wants to be in the mountains but also have comfortable accommodations for their guests. I highly recommend this venue!
We Loved Everything!Reviewed on 9/17/2014 Alexis V
Everyone at Sugar Bowl was amazing! From the moment we checked in, they took care of everything, I could actually enjoy the whole weekend instead of stressing about all the small details that I didn't quite have time to finish. We gave them all our stuff for the wedding, cocktail hour, reception, after party when we got there and they took care of it from there. Each stage of the event was set up better than I could have hoped for and the whole event was incredibly well organized-no thanks to me. The entire staff, from the front desk to housekeeping to the bartender to Meghon and Pat (the two people in charge of weddings and events), were genuinely friendly and wanting to help. Our guests are still telling me what a great wedding it was and how nice everyone was. They worked seamlessly with our other vendors, and took care of any questions they had. The food was also amazing! We couldn't have picked a better place in Tahoe for a wedding!
The Absolute Best Day of My LifeReviewed on 9/07/2014 Lindsay G
I don't think my words could possibly do justice to explain how happy my husband and I were with our Sugar Bowl wedding. Here goes nothing... I had been looking for places close to my hometown but nothing seemed to be quite right. A friend suggested I check out Sugar Bowl (which in the past I had only associated with winter and skiing), so we decided to take a look. We knew almost immediately that this was the place we wanted to get married. Not only is the location breathtakingly beautiful, but we were greeted by loveliest wedding planner on the planet. We loved Meghon immediately. She truly helped us navigate to the wedding of our dreams. She was available from the very beginning and guided us with her extensive knowledge and expertise. She is a beautiful person, inside and out. We decided to get married at the Village Lodge, which we would HIGHLY recommend. Our families and close friends checked in on Thursday. On Friday, we did the rehearsal dinner at Lake Mary, which included use of the lake for the entire day. We played, we swam, hung out, and finished our evening with the best BBQ dinner. Our wonderful wedding ceremony and reception took place at the Village Lodge. Every single staff member was excellent. Lisa, the hotel manager, helped me coordinate accommodations and bent over backwards to make sure that we were all taken care of. The entire weekend was magical. They set out all of the snacks and lunches we brought, took great care of every single guest that arrived, and were always available (24/7) to help with anything we needed. The kids has SO much fun the entire weekend and all the adults felt safe letting them play around the grounds. We didn't have to think about any of wedding details while we were there. All we had to do was show up and enjoy. Sugar Bowl set everything up (way more beautifully than I ever could). It was such an incredible opportunity for both of our families and our friends so spend time together over the weekend and celebrate as one. Sugar Bowl made this possible and I will forever be grateful for that experience. It was truly the best reflection of our love and such a happy way to start a marriage. Thank you, Sugar Bowl! From the bottom of our hearts.
Sugar Bowl Wedding WeekendReviewed on 7/23/2014
Sugar Bowl gave us the best possible wedding weekend we could ask for - from the timely, professional and patient correspondence in the planning of our event to the wonderful food and service throughout our wedding weekend, I can honestly say that I can't imagine a more fun and memorable way to get married. Meghon and her assistant Amanda were outstanding in their efforts to make sure that everything went according to plan and were extremely diligent and accommodating in handling any problems that came up (which was bound to happen). We have no hesitation in giving our highest recommendation to Sugar Bowl for anyone who is looking for a unique and memorable way to share an unforgettable experience with their friends and family.
HANDS DOWN WONDERFULLY UNIQUE VENUEReviewed on 7/21/2014 Dhonna A
WOW! What a wonderful venue for my June 21 wedding!! It was just perfect for our rustic/outdoorsy themed wedding! Even if you did not have any decorations..this venue SCREAMS rustic and woodsy. The staff were wonderful during the whole process: before, during, AND even after. Weather was great and we did not know we were marrying on the first day of summer aka the longest day of the year! Meghon was sooo wonderful and absolutely responsive. After hearing all my friends current horror stories, I appreciate her fast response! When you talk/email her she felt genuine..Again my friends' current experience with their CURRENT venue planners..cringe worthy. I loved and appreciated her suggestions. We also decided to hire her for flowers. Again, it fit perfectly with what I wanted. It was also very convenient to have the food, flowers, hotel, setup all under Meghon! It helps to have someone who sees the vision the bride sees! Thank you Meghon many of my guest commented on just how wonderful you all were! Booking Sugar Bowl meant you had the whole place to yourself. We decided to book the Disney Lift...and the ONLY complaint I have was that I wish that the person operating the lift told my guest that the bar on the ski lift came down...BOY riding the skilift during the summer is FAR different than in the winter...SCARY ISH! I had a few guest who were literally crying so be prepared. My husband and I are outdoorsy and we ski/snowboard often I did NOT expect to be THAT terrified! Other than that it was a wonderfully unique experience for our 170 guest. BEFORE: We loved that we had a private food tasting and was able to invite 2 other people. We definitely got drunk from all the wine! We ended up having open beer and wine at the wedding. We also got 4 tickets to ski at the venue. Sadly we didnt get to use this as there was no snow! =( DAY OF: The weather was great. The grounds well groomed. The ceremony was setup just the way I wanted. For the wedding I had lawn games, rented decor, and had my own DIY decor...Meghon set it up exactly as I wanted. After the ceremony, they made sure the bridal party had wine and appetizers...yay! Our photog was also going picture crazy and Meghon had to remind him "THEY NEED TO GET ON THE LIFT NOW"...lol... Anyhoo I can't stress how wonderful this venue is. Many of my guest kept commenting on it too. I wish I can get married all over again! =)
Amazing wedding at Sugar BowlReviewed on 7/09/2014 carly n
My husband and I had our wedding at Sugar Bowl this June. I just have to mention that our guests are still talking about it and telling us it was the best wedding they have ever been to. I know this is purely because of the staff at Sugar Bowl. Yes, the scenery is spectacular, the food was amazing but the staff went above and beyond to make our day so special. We opted to host a whole weekend of events for our guests; movie night on Thursday, welcome dinner Friday and of course our wedding on Saturday. The whole weekend was perfect! It was so nice for my husband and I just to relax and enjoy the weekend and have the staff take care of everything. We even had Meghon do our wedding flowers, they were beautiful! I would highly recommend Sugar Bowl as a wedding venue.
Sugar Bowl was the talk of the townReviewed on 10/15/2013 Landen R
Sugar Bowl made our prep hassle-free and our wedding day smooth and easy. Meghon and Pat were excellent coordinators on site and their team was there to answer any questions and help make our guests feel comfortable. Flowers - Meghon & Pat happen to be florists, so that was easy. Catering - they have excellent chefs and menus on site, so no need to outsource. The tasting was a wonderful experience in the snow! Photographer - they have a list of recommended vendors and we loved Chris Cooke! Cake - we ordered apple pie from a local bakery and Meghon took care of the whole process, from the tasting to the cutting Decorations - we went with a rustic, woodsy theme and Sugar Bowl helped out significantly by providing baskets, wooden rounds for the tables, mason jars for flowers, an archway, and shepherd's hooks for the ceremony aisles. We described our style and they created it for us - so easy! We even intended to write out table seating with chalk and Sugar Bowl staff, Riza, took care of us for us with her beautiful handwriting. Location - up in the mountains; it's definitely a destination for most, but at only 45 minutes from the Reno Airport and about 3.5 hours for our Bay Area friends and family, we decided that a "convenient getaway" fit the bill. Keep in mind, the 20-minute drive down to Truckee is a windy mountain road, so stay away after drinking or late at night. Lodge - the rooms are quaint and clean and fit a wide range of numbers, so we could house our relatives and groups of friends easily on site. We only wish they had more rooms to fit all of our 117 guests. Luckily, it's just a short drive down to Truckee where hotels and restaurants are located. Fun perk - we booked the Disney ski lift for our cocktail hour, which was a huge hit - even my grandparents went up the lift! Our friends and family are still raving about the scenery, the location, the Disney lift, the food, and the service. We really could not be happier with our choice and would absolutely recommend it to others.
Perfect September Wedding!Reviewed on 10/02/2013
sugar bowl was a great place for a wedding. we chose it because both of us grew up skiing at sugar bowl, worked there for a few years, and still ski there all the time together. from the beginning our coordinator Meghon was a huge help. she responded immediately to all of our questions and emails and was always prepared for our meetings. you could tell she knew what she was doing and we immediately felt like we should trust whatever she suggested. after Meghon went on maternity leave, our new coordinator Pat transitioned seemlessly and took over our event. we had originally planned an outdoor wedding, but as it started raining (and then snowing!!! in September!) on our wedding day, many of our plans had to change and everyone at Sugar Bowl was extremely helpful and prepared for everything. needless to say the final result was perfect. they were also super helpful in terms of set up, such as setting up all of our table decorations, place cards, goodie bags, guestbook, etc. one of the best things about getting married at sugar bowl, at least if you choose the Village Lodge location, is that you get to have the whole hotel to yourselves for the weekend, including using the lodge for the rehearsal dinner the night before, as well as whatever events you choose during the weekend (we had a groom-hosted pre-wedding pizza party and after-party and breakfast was provided both mornings for all our guests in the hotel). they can basically cater to whatever request you have. all expenses were very clearly spelled out in their prospectus that we were given before the event. we highly recommend it!
Mrs. Kathleen AckerReviewed on 9/09/2013 Kathleen B
Words can't express how glad I am that we chose this venue. They were professional, organized, and so incredibly helpful. They took an otherwise stressful day and turned it into one of the most relaxing and fun experiences with my family and friends. Damien and I will be forever grateful.
My Island Wedding Wrapped in a Bow!Reviewed on 9/05/2013
John and I got married on June 22, 2013, at the Sugar Bowl Resort. Let me tell you... I've always dreamt of my wedding day, but then it came to real life! Everything was perfect; from the staff, the food, and most of all the wedding coordinator: Lisa and Meghon. The whole day went so smooth and perfect.The decor was beautiful, but the scenery was unbelievable. I would defiantly recommend Sugar Bowl Resort to any Bride that is looking for an extravagant wedding.
Island - Mountain dream dayReviewed on 9/05/2013
My special day could, and would not have been possible without Sugar Bowl and its staff!!
Mother of the BrideReviewed on 8/28/2013 Susan T
Best Wedding ever! People are still talking about it. I run into people that weren't even there and they are saying we heard it was amazing!
Best wedding venue EVER.Reviewed on 8/16/2013 Jessica O
I'm still in awe at how magical our wedding was at the Sugarbowl Resort. Let me start by saying we toured Sugarbowl during the winter, in the middle of ski season. We had seen pictures of what it looked like in summertime and it looked great, but we still didn't know what to expect. Even without seeing the venue in full bloom, we were sold on Sugarbowl for 1. The fact that they have a package that includes exclusive access to the resort from Friday until Sunday, 2. Rooms were on property, and 3. Meghon, the most amazing wedding coordinator ever. The added bonuses that we found once we arraived were the ABSOLUTELY GORGEOUS scenery and grounds. The resort is spectacular during the summer time; green, wild flowers, flowing creeks, Lake Mary, hiking trails. Just pure bliss. The exclusive access makes you feel like you're at your own personal relaxation destination. Most of our families/friends stayed up there for the weekend. Every day we all got to eat breakfast together and set out on hikes, or to the lake, or whatever event was planned for that day. It was incredible to get to spend such quality time with our friends & family before the wedding, and made it so we really got to enjoy the wedding night (without having to go table to table trying to spend time with everyone) because we had the chance to be with everyone all weekend. I'm sure a lot of brides can relate to the need to be in control of all the details of your wedding. I was very hesitant to give up control to a wedding coordinator, but Meghon put my worries to ease very quickly. She is a pro. She has put on so many wedding at Sugarbowl, that she made me feel confident that she had everything under control from our first meeting. Everything ran very smoothly, and there were no surprises. Everything I needed to know was told to me well in advance and she answered all of the questions we had (even when we asked them multiple times). Her staff is very professional. Her colleague, Pat handled a lot of the reception and after party details and was equally as fantastic. It's a HUGE relief as a bride or groom to not have to worry about getting the ceremony started on time, setting up tables, flowers, etc., getting everyone in the right order, making sure the wine gets on the tables, getting everything cleaned up afterward, and so on… The coordinator staff handles all of those details, and makes it MUCH more enjoyable for the wedding party and family. I mean, the wedding is supposed to be a celebration not a chore right! And that's how the staff at Sugarbowl makes sure it is, a spectacular celebration! There are all sorts of activities to choose from. They really can cater to any and all types of weddings. There are SO many options and add-ons, chair lift rides to the top of the mountain for cocktail hour, lakeside dining for the rehearsal dinner, etc. I wish we could have done them all. The reception food was delicious. The chef at Sugarbowl really knows how to please a crowd. Everyone raved about the appetizers and dinner! There are so many things I can say about our stay and celebration at Sugarbowl, but I'd be writing all day. It's a very special place and an incredible wedding destination. It's been 6 weeks since the wedding and our family and friends are still talking about how amazing the weekend and the venue were. Everyone really enjoyed themselves and we will always have an incredible memory of our wedding at Sugarbowl.
Made my dream wedding come true!!Reviewed on 8/09/2013 Sarah m
Meghon, Pat, Lisa, and all the Sugar Bowl wedding crew are amazing. They all went above and beyond any expectations I have of a wedding venue. They took all my projects and decorations and took care of it all so I didn't have to worry about it and I could just enjoy the days leading up to the wedding. The food is outstanding, we got lots of compliments on that. DO THE DISNEY CHAIR/COCKTAIL HOUR...SO WORTH IT. Everyone loved it, it was the highlight of the event. The staff is so amazing and provide outstanding unforgettable service. They treat you like a VIP/celebrity status person! So attentive and helpful and approachable. Meghon is also outstanding. She made herself available to me all the time and answered all of my questions promptly and thoroughly every time. She even joined my pinterest boards to look at my ideas/colors/overall theme...truly a dream wedding coordinator! Meghon also did the flowers for the entire event as well as the rehearsal dinner. They were everything I wanted and envisioned. She worked with me after I had some flowers in her original "quote" that I didn't like 100% and changed them to be truly everything I wanted. She also respected my budget and desire to keep the costs down. Got so many compliments on the wedding and all I could think and say back to people was, "it wasn't me, it was Sugar Bowl!!"
Sugar Bowl weddingReviewed on 8/09/2013 karen h
The BEST wedding venue ever if you want to spend a weekend with your guests. Lake Mary is a beautiful small lake, equipped with paddle boats, canoe, kayak. Entire day and Rehearsal Dinner here. The next day spent at the lake and then wedding and reception at the Sugar Bowl Lodge Food, staff were great. The beautiful mountain location, topped off by ski lift ride to mountain top where there is a beautiful decked building to enjoy cocktails and take in the great scenery. Staff was fabulous. Perfect!! Exactly what the bride and groom envisioned.
Sugar Bowl ResortReviewed on 7/14/2013 Susie W
My daughter was married at Sugar Bowl Resort on June 15, and it was a magical day. We have always loved spending time in the Tahoe Mountains and knew it would be a lovely backdrop for this special event, but we had no idea just how special this day would be with the help of Meghan, their event planner, and all the Sugar Bowl staff. My daughter had very specific ideas of what she wanted for the ceremony, for the meal, for the décor; and the staff simply accommodated us with a smile! We invited our close friends and family to stay with us at the Lodge for a few nights before the big event. The staff there provided such a wonderful and relaxed atmosphere for our early morning hikes and late night chats in the lobby or out around the campfire. It was just like summer camp with all your favorite people. The wedding day was pure happiness. The staff at Sugar Bowl have a calm but professional attitude that puts everyone at ease and helps you just enjoy the day. Meghan knew just what my daughter envisioned for this day and took it upon herself to make it happen. I had such faith that everyone there was working to make her day amazing that I did not worry for a minute. We also took the chair lift to the top for Happy Hour which was a big hit with all our guests. The views were fabulous, and what a cool environment to start the party. The venue at Sugar Bowl is amazing, but I cannot say enough about the Sugar Bowl staff. They were all so friendly, caring and attentive. Words cannot express how thankful I am that we found Meghan and Sugar Bowl for my daughter's big day.


text:
Colts nonsense and a Chargers emerging rookie
• Several Colts defenders I interviewed after the game hit the same point: Philip Rivers makes the Chargers go. Vontae Davis, a starting cornerback, said a few times that Rivers pulled off reads and throws that few quarterbacks can make. Remember, the Colts hadn't faced a passer who is nearly as advanced as Rivers is. The parts continue to change because of injuries, but with an offense made more versatile by the expanded audibles, the constant threat of changing tempo and the quick-passing game, the Chargers should feel like they can win any game. Going off six games, a foundation seem to be taking shape there. You wonder how far it can go, though, until more talent is added to the whole roster. As for the Colts, if young Andrew Luck becomes proficient at some of the tools that Rivers is mastering this year with help from new coaches, they could be a bear in the AFC for years to come.


text:
Declaration Sculpture
Windward Avenue, Venice, CA 90291Map
Created in 2001, the Declaration is a steel installation by renowned artist Mark di Suvero. His industrial and futuristic work is famous worldwide, and this landmark on Venice Beach is no exception. At 60 feet (18 meter) high, its design features two triangles tilting skywards while resting on supporting beams. The meaning behind the sculpture is open to interpretation.
Write a ReviewSign in
Thank you for submitting your review!
See All: Hotels » | Things To Do » | Restaurants » | Nightlife »
- Type:
Attractions & Landmarks


text:
Join FREE | Login
& Deals
& Celebrations
Instead of making individual sandwiches, make one big loaf in 10 minutes!
©2014 General Mills, Inc. All Rights Reserved. This information will only be used to send an email to your friend(s) and will not be saved. Please read our Privacy Policy.
Look for the garlic focaccia bread in the deli or bakery. Plain focaccia bread or a loaf of soft French bread can also be used for this sandwich.
Silly Snake Dogs
Tangy Asian Chicken and Coleslaw Rolls
Italian Meatball Subs
Snappy Joes on Texas Toast
Witches Finger Sandwiches
Turkey Club Sandwich Ring with Avocado Aioli


text:
Give an old lamp new life with a simple shade change.
A delightful shade from the Imperial Collection. Bell-shaped lamp shade in a delicate taupe fabric. Side ribbing adds additional style. Spider fitting. The correct size harp is included free with this shade.
Customers most agreed on the following attributes:
Got the product very quickly, nicely packed and easy to assemble. Nice soft light source for a standing lamp!
was looking for lampshades, and was surprised what products that was associated with lamps plus. If I need other items I will be sure to return to this site.
Our associates are standing by to assist you.


text:
Idaho Farmer-to-Farmer Exchange Honors Pioneers
by Jennifer Miller — last modified Feb 14, 2014 01:10 PM
Farmers committed to organic and sustainable agriculture aren't the new kids on the block, anymore. read more...
Managing Mummy Berry and Spotted Wings in Blueberries
by Jennifer Miller — last modified Feb 13, 2014 02:05 PM
Plump, juicy blueberries are a nutritious and tasty treat, well loved by children and adults, alike. Two pests also find these berries to be a great food source, thus creating challenges for farmers. read more...


text:
London, United Kingdom
My Rating
Tour guide is good but the itinerary was very packed, totally not enough time to even walk around, suggest to stay longer time in Oxford rather than in Stonehenge
My Photos
London, United Kingdom
My Rating
Some content licensed under a Creative Commons Attribution 3.0 License.
© 1997–2015 Viator, Inc. 330203 All rights reserved. Viator is a registered trademark of Viator, Inc.
is a Service Mark of Viator, Inc. Travel with an Insider is a Service Mark of Viator, Inc.
Use of this website constitutes acceptance of Viator's Terms & Conditions.
Viator uses cookies to improve your experience on our website. Learn more about how we use cookies and how to change your cookie settings | Close message


text:
Click to expand
What do you think? Give us your opinion. Anonymous comments allowed.
#18 - Absolute Madman (02/06/2013) [-]
Drinking is bad. It's a weakness. I hate the people who go to parties and can't have fun with their friends without alcohol. It's pathetic that they can't enjoy themselves at a ******* party with all their friends without needing to drink. Or the people who hide in a bottle from their problems. It's just a crutch. Man the **** up and deal with your problems. Life is hard, man up. It's also horrible for you body basically like drinking poison.
Reply+1#20 to #18 - mrfop (02/06/2013) [-]
I completely get what you mean but I don't feel as if it's THAT bad unless you're an alcoholic or like what you said, can't enjoy themselves without it. I do tend to drink quite a lot, maybe most weekends and a couple of beers at home when I'm chilling (not everyday don't get me wrong). Do you not drink at all? Even at a party every now and then?
#27 to #25 - teenytinyspider (02/06/2013) [-]
You are not alone anon. I don't drink either and have never done so.


text:
CU: Home • A to Z • Campus Map
In a scene from the 2006 movie, The Devil Wears Prada, the powerful and demanding editor of a New York fashion magazine orders her assistant to obtain a hard-to-get advance copy of one of J.K. Rowling's Harry Potter books. The almost insurmountable feat took all the employee's resources to accomplish.
In the predawn darkness in the heart of winter, as most of their classmates are still in bed, four University of Colorado Boulder undergraduates ready themselves for an often brutal and bone-chilling ski uphill to research sites in the snow-encrusted Indian Peaks high above Boulder.
As I know many of you are interested in the status of permitted concealed weapons on campus, I want to update you on recent actions in the state legislature. This past Friday, the Senate ended further consideration of a bill to ban concealed weapons on college campuses across Colorado. The bill's sponsor, Senator Rollie Heath, pulled the bill because the votes to support it were not there. As a result, both the law and the campus policy on concealed carry remain in effect. Any changes to the law would have to come through a future state legislative process.
By Brittini Hernandez, Student Body President
Over the past few months, CU Student Government (CUSG) has been working with administrators to plan for the upcoming 4/20.
To best represent students, CUSG convened a task force of student leaders from areas across campus to work to develop ideas for short-term and long-term plans for 4/20. The conversations we had with administrators and students have been productive and have established long-term working relationships that will serve students in future years.
I want to take this opportunity to inform you that the CU-Boulder campus will once again be closed to non-affiliates on April 20. We are continuing this approach, begun last year, to ensure that the business of the campus continues without being materially disrupted, and that our teaching, research and academic work and other university operations can proceed.
Ligia Duarte Botelho says her recently-completed internship with the Centers for Disease Control (CDC) gave her a rewarding opportunity to explore her interest in different cultures, government, and global health policy.
A junior majoring in international affairs, Botelho, who is originally from Brazil, wants to pursue a career as a diplomat in India or Thailand. She was drawn to the CDC internship because it involved the topics she wants to study in the region of the world she wants to focus on.
By Sarah Tamura, Community Health student coordinator
As a student coordinator at Community Health, I'm really excited for our "One Little Change" campaign this semester.
Sophomore Daniel Mullan is preparing for a career in music by learning business and entrepreneurial skills from the Entrepreneurship Center for Music (ECM) at the College of Music.
Mullan is majoring in classical saxophone performance with a minor in business, and will be one of the first students enrolled in the new certificate in music and entrepreneurship debuting in the fall. He realizes that to be successful, musicians need to be adaptable to a rapidly changing marketplace.
Every gift matters, no matter the size.
What kind of Buff will you be?
Be in the know. Know what to do.
© Regents of the University of Colorado
Contact Us • Privacy • Legal & Trademarks • Accessibility • Student Consumer Information


text:
News from WTOP
News from the AP
Mike Causey
Shows & Panels
Shows & Panels
- Agency of the Month
- Business of Government Hour
- The CFO Agenda: Delivering value from financial transparency and audit efforts in the public and private sector
- Cloud-Driven Data Insights in Government
- CXO Surveys
- Disaster Resilience for America
- Federal News Countdown
- Government Perspectives on Mobility and the Cloud
- Reducing Risk in the Cloud
- Reimagining the Next Generation of Government
Shows & Panels
- AFCEA Answers
- American Readiness: Renewable Power and Efficiency Technologies
- Ask the CIO
- The Business Case for Cloud Computing in Government
- Cloud-Driven Data Insights in Government
- Connecting the Dots: Digital Authentication in Government
- Cybersecurity Game Changer: Real-Time Event Processing in Government
- Data-Centric Approaches to Government in the Cloud
- Delivering the Digital Government Mission
- Federal Executive Forum
- Federal News Radio's National Cyber Security Awareness Month Special Panel Discussion
- Federal Tech Talk
- The Future of Government Data Centers
- Government Perspectives on Mobility and the Cloud
- Industrialized, Interoperable and Insight-driven Federal Health Panel
- Innovation and Tech Superiority through Acquisition Reform
- Mitigating Insider Threats in Virtual & Cloud Environments
- Moving Agency Applications to the Cloud with PaaS
- Reducing Risk in the Cloud
- Security in the Age of Targeted Attacks
- Air Traffic Management Transformation Report
- The Business of Cloud
- Cloud First Report
- Data Driven Cloud Series
- Disaster Resilience for America
- General Dynamics IT Enterprise Center
- Gov Cloud Minute
- Government in Technology Series
- Homeland Security Cybersecurity Market Report
- The Intersection: Where Technology Meets Transformation
- Modern Mission Critical Series
- National Cybersecurity Awareness Month
- The New IP for Federal IT
- The Social Platform Solution for the Department of Veterans Affairs
- Technology Insights
- The Cyber Security Report
- The Next Generation Cyber Security Experts
Shows & Panels
- Cloud-Driven Data Insights in Government
- Disaster Resilience for America
- F-35 Lightning II Program
- Government Perspectives on Mobility and the Cloud
- On DoD
- Pentagon Solutions
- Reducing Risk in the Cloud
- Reimagining the Next Generation of Government
- Transforming Business Operations at the Defense Department
Search Result
Search Tags: pay rates
Downsizing, Relocations, Benefit Reductions Up Next?
If you want a preview of coming attractions in your own agency, check out what is happening in the giant US Postal Service. It is looking at a major cutback of administrative personnel, consolidating post offices and relocating employees, not to mention possible pay and benefit changes. Senior Correspondent Mike Causey says you could be next.
Tags: pay and benefits , Mike Causey , USPS , pension , downsizing , Interior , GSA , Commerce , SSA , High-3
OPM trying to correct fed salary facts
Agency said latest statistics find on average federal employees make 22 percent less than their private sector counterparts. Sheldon Friedman, chairman of the Federal Prevailing Rate Advisory Committee, says recent news stories about feds making more than the private sector do not accurately depict the data.
Tags: pay and benefits , John Berry , Sheldon Friedman , OPM , Federal Prevailing Rate Advisory Committee , general schedule , Jason Miller , pay debate


text: Better use firewall to protect the port from unwanted access. This way you'll have better protection and also you'll have a trace of unsuccessful (and maybe successful) connection attempts :) Ivailo Tanusheff Senior System administrator ProCredit Bank (Bulgaria) AD tel. +359 2 921 7161 fax +359 2 921 7110 http://www.procreditbank.bg Disclaimer: The information contained in this message is intended solely for the use of individual or entity to whom it is addressed and other authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or taking any action in reliance on the contents of this message is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by responding to this email and then delete it from your system. ProCredit Bank is neither liable for the proper and complete transmission of the information contained in this message nor for any delay in its receipt. "Efren Bravo" <efrenba at dhl.co.cu> Sent by: owner-freebsd-questions at freebsd.org 09/27/2005 10:27 PM To "freeBSD " <freebsd-questions at freebsd.org> cc Subject Limit client connections ssh Hi, I'm using ssh to connect me to fBSD server, how can I limit the client connections?, I mean, I only only that the server(ssh) accept incoming connections from a specific IP or IPs range? Thanks.... _______________________________________________ freebsd-questions at freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"


text:
Mon-Fri: 7am-1am EST / Sat-Sun: 7am-11pm EST
ApplianceGeneral Electric Range
Level of DifficultyEasy
Time to do repair15 - 30 mins
Age of ApplianceMore than 10 years
PliersNutdriverScrew drivers
0 out of 1 people found this instruction helpful
Replacing the electric oven element was easy. It took about 20 minutes and all you need is a screwdriver and a pair of pliers. What you have to do first, turn the power to the oven OFF. Remove the original element carefully observing howit was installed and install the new element in the same order.I have used Parts Select a couple of times in the past years and the delivery came quicly without any problems.Spyro.
Help other customers find the most helpful instructions.
Were these instructions helpful?
Part Number: PS249424
All brand logos are trademarks of their respective owners.
The PartSelect logo is a Registered Trademark of Atlantic Laundry Centres, Ltd.
Copyright © 1999-2015 , Eldis Group Partnership. All rights reserved.


text:
To embed, copy and paste the code into your website or blog:
[author: Jodi Frankel]
On October 31, 2012, the National Labor Relations Board's (NLRB) Office of the General Counsel issued two advice memoranda addressing at-will provisions in employee handbooks. In both cases, the NLRB concluded that the specific at-will provision could not reasonably be interpreted to restrict protected activity and, therefore, was permissible under federal labor law.
The NLRB's guidance follows a controversial decision earlier this year from an NLRB administrative law judge (ALJ). In that decision, the ALJ held that an at-will disclaimer adopted by an American Red Cross regional unit was unlawfully overbroad to the extent it conveyed that at-will status could never be changed. Notably, Red Cross employees were required to sign a form stating "I further agree that the at-will employment relationship cannot be amended, modified, or altered in any way." In the Red Cross matter, the ALJ found the language to be unlawful because it implied any concerted effort undertaken by employees to alter the at-will status would be futile. (We previously commented on the Red Cross decision in our October 2012 Employer Alert.)
The ALJ's ruling in Red Cross generated significant attention and raised concerns that more challenges to the at-will language commonly included in employee handbooks would follow. The NLRB's recent advice memos, however, provide welcome guidance and serve to allay these concerns.
The first advice memo (available here) addressed language in a restaurant's handbook that "No representative of the Company has authority to enter into any agreement contrary to the foregoing 'employment at will' relationship." The second advice memo (available here) addressed a challenge to a trucking company's handbook, which advised drivers that employment was at will and that at-will status could be modified only in writing by the employer's president.
The NLRB found both provisions to be lawful. Distinguishing Red Cross, the NLRB noted that the two provisions at issue did not imply that the at-will relationship could never be changed. Rather, the disclaimers left open the possibility of modification through collective bargaining or other concerted efforts. According to the NLRB, the provisions simply reinforced the at-will employment relationship and highlighted that the employer's own representatives have limited authority to modify at-will status. The NLRB went on to acknowledge that "[i]t is commonplace for employers to rely on policy provisions such as those at issue here as a defense against legal actions by employees asserting that the employee handbook creates an enforceable employment contract."
While the NLRB's advice memos do not reverse the ALJ's findings in Red Cross, they do provide much-needed clarification on what at-will disclaimers the NLRB will find acceptable going forward. To be sure, all employment handbooks should include, at the least, a statement that "the employment relationship is at will and can be terminated by either the employee or employer at any time and for any reason." Employers also would be well-advised to indicate that only the highest officers have authority to modify the at-will relationship, and that such modifications must be in writing. When drafting disclaimers, however, employers must be cautious to avoid language that could be interpreted to foreclose any possibility of modifying at-will status. As the NLRB's recent guidance indicates, such language will be found to be overbroad and a violation of federal labor law.
We will keep you updated through our blog on any further developments in this area.
DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.
© McNees Wallace & Nurick LLC
Read fresh new writing on compliance, cybersecurity, Dodd-Frank, whistleblowers, social media, hiring & firing, patent reform, the NLRB, Obamacare, the SEC…
…or whatever matters the most to you. Follow authors, firms, and topics on JD Supra.
Create your news brief now - it's free and easy »
McNees Wallace & Nurick exists to provide professional services of superior value which exceed our...
View Profile »
See more »
Sign up for your custom alerts now, using LinkedIn ›
Back to Top
Copyright ©