text:
All motels should be like this one - Review of Pines Motel, Cottonwood, AZ - TripAdvisor
“Located off the main street, and a little...”
“When I checked in requested a room change to...”
“The rooms are of good size and comfortable”
“The location was by plenty of restaurants and not...”
All motels should be like this one - Pines Motel
See the most recent reviews Travellers221
8 helpful votes “All motels should be like this one”
Thank Travellers221 Report Ask Travellers221 about Pines Motel
English first French first German first Spanish first Any Larry E
We stayed 1 night while sightseeing in the area, and were totally happy with the accommodations. We were in 204 which was a king bed room. The bed was comfy, and had nice bedding. There was a comfortable easy chair. There was a convenient fridge and microwave, and the air conditioner worked well. Everything is fresh and updated -- albeit with a certain charm found only in older accommodations. The young man who checked us in was friendly, and helpful with finding a place to eat dinner. We would not hesitate to stay here again.
Room Tip: There is no elevator, so if it's difficult to climb stairs be aware.
Thank Larry E Report Ask Larry E about Pines Motel
This review is the subjective opinion of a TripAdvisor member and not of TripAdvisor LLC. naturalbeauty53
34 helpful votes “GOOD VALUE, NO ROMANCE”
By staying at this motel, I thought I would save lots of money to be better spent in Sedona for our Anniversary trip. There is really nothing wrong with this place......except that it lacks a certain charm and the views I was hoping for. Even though we had a mini-suite which was perfectly adequate and as represented, there was only one window in the room, which faced the back of the "front building". Our "view" was had only by venturing out onto the communal balcony and looking left over the top of the shell gas station on the corner. When you check in, you are treated to a view of the laundry and the owner's real estate office. The pool had a cover over it the entire time we were there. Nonetheless, the place was chock full of people enjoying the reasonable rates and almost views which is what this place offers........if you want "special" or "ambience", keep going. We rebooked into a hotel in Sedona with more privacy, more room, a terrace with red rock views and a higher price tag but once again, we realized that you get what you pay for.
Room Tip: front bldg, 2nd floor
Thank naturalbeauty53 Report Ask naturalbeauty53 about Pines Motel
Happy Anniversary! Thank you for the review! Sedona is 20 miles from us and we do offer one of the best values in the area. Our rooms are clean, affordable and centrally located to many attractions nearby. We don't pretend to be a resort and offer the best "basics" around with 32" flat screen TVs, feather blankets, kitchens, ironing boards, microwaves, hair dryers and clean rooms - Our pool is seasonal and "officially" opened from Memorial Day to Labor Day but those dates are flexible depending on the weather.
33 helpful votes “Had a Nice Stay at Pines Motel”
We stayed at Pines Motel in April 2014. Chose the property based on good Trip Advisor ratings. Room was clean, quiet, and very adequate. Staff were friendly and attentive. We were not disappointed and will stay here again if we come back to Cottonwood.
Thank Kilgore_Trout_88 Report Ask Kilgore_Trout_88 about Pines Motel
This review is the subjective opinion of a TripAdvisor member and not of TripAdvisor LLC. Kilgore_Trout_88 has 1 more review of Pines Motel “Another Nice Stay at Pines Motel”
Thank you for taking the time to write a review! This helps us so much and we appreciate it! We hope to see you next time you come to visit!
2 reviews 3 helpful votes “Gem of a find - Stay at Pines Motel!”
Pines Motel had the exact small-town feel I was looking for in my travels. Windows faced east which made it easy to get up in the morning, and you can see Sedona across the valley - they were so smart to build right there. I loved all the green initiatives, too: there was a separate recycling bin, etc. Checkin was so friendly, and it's in a really convenient spot in town. Everything worked in the room just perfectly which is unfortunately not something that can be said for the other hotels in my travels. To boot, the room was laid out really mindfully, with plenty of space for the suitcase near the bathroom/dressing area, and plenty of counter space that fit my cosmetics suitcase. It was nice not to have to unpack it to fit all the little bottles. It was all just right. I would certainly return there and suggest anyone traveling to Cottonwood, Jerome or Sedona, DO YOURSELF A BIG FAVOR and STAY HERE! It's way less expensive than the surrounding areas, you'll still probably get a better experience, and within a reasonable drive. The picnic are a was really nice too, to enable the time spent outdoors (that is why we're there, right)? I am more than happy to return mentally to the Pines Motel to write them an outstanding review. :D
Room Tip: I was in room #206. It was incredible - the window was placed in a way where I was able to keep the...
Green Features: More than I expected. So pleasantly surprised. At first I thought the little motel soaps were so small! Then realized, since most stays (mine included) are probably just a night or two, bigger soaps would just be excessive. This place just had it down.
Thank Jacqueline M Report Ask Jacqueline M about Pines Motel
16 helpful votes “Great Place.....will go back”
We spent 2 nights here in March while touring the Cottonwood/Sedona area and taking in the Verde Canyon Train Ride. Wonderful place for an older Motel.....quiet, neat, clean. Well run and the owner/employees were polite and helpful.. Location is great. Central to everything (Jerome, Clarkdale & Sedona). Price for a 2 night stay aver. $77 per night (Weekend rates are a bit higher). We also found a great place to dine.....The Cork & Catch, not far from the Motel. It was so good we went 2 nights in a row.We will be back to stay here again next winter.
Thank Robert P Report Ask Robert P about Pines Motel
66 helpful votes “nice motel”
spent only one night here while visiting nearby Jerome. Motel was clean, quiet, and is pet friendly (as evidenced by a little barking from a dog in the room above ours. At &79 per night, our room included( though we did not utilize) a nice little kitchenette with 2 burner electric stove top, microwave, and good sized fridge.Beds were comfy, though a little on the soft side for my taste.Overall, a good value. I would stay there again next time I'm in the Cottonwood/Jerome area.
Thank mac1075 Report Ask mac1075 about Pines Motel
Thank you for the comments! We even offer a "standard" room with no kitchen for a lower price also! See you next time!
TripAdvisor is proud to partner with Booking.com, Expedia, Hotels.com, Orbitz, Priceline, Travelocity, Hotwire and getaroom.com so you can book your Pines Motel reservations with confidence. We help millions of travelers each month to find the perfect hotel for both vacation and business trips, always with the best discounts and special offers.
Explore similar hotels Quality Inn - Cottonwood152 ReviewsShow Prices 1.6 miles Best Western Cottonwood Inn624 ReviewsShow Prices 0.2 miles The Iron Horse Inn274 ReviewsShow Prices 2.2 miles See all Cottonwood hotels Browse nearby


text:
new test probe for multimeter / tester for such as fluke vichy etc.5.99 | eBay
Details about new test probe for multimeter / tester for such as fluke vichy etc.5.99
new test probe for multimeter / tester for such as fluke vichy etc.5.99
Sell one like this	More chances to get what you wantFeedback on our suggestionsNEW MultiMeter Test Lead Alligator Crocodile Clip for tester Meter Fluke Vichy $1.99+ $1.89 Black + Red MultiMeter Test Lead Alligator Clip for tester Meter Fluke Vichy $1.99+ $1.89 Meter Alligator Crocodile Clip clamp test lead probe for tester such fluke etc.$3.99Free shipping P2008x10 Alligator Crocodile Test Clip Clamp For Fluke Multimeter Tester Probe $9.99Free shipping Description
eBay item number:271025064778
... Read moreabout the condition	Type: test probe
Model: test lead for multimeter / tester
Brand: dabudo
MPN: 5.99

type: global

value: This website is an American multinational e-commerce corporation based in San Jose, California, that facilitates consumer-to-consumer and business-to-consumer sales through its website.


text:
1,25253650
56141123
6,28242671
from http://www.python.org/doc/2.5.2/lib/imap4-example.html
1,33631224
I just ran into an issue with Python's imaplib and Gmail's authentication mechanism:
>>> imap = imaplib.IMAP4_SSL('imap.gmail.com', 993)
python gmail imap asked Dec 9 '08 at 6:07
2,65912155
1 2 3 4 5 … 40 next highest voted imap questions feed
email × 533
javamail × 156
gmail-imap × 138
pop3 × 110
email-client × 29

value: This website is a question and answer website for professional and enthusiast programmers. It is the flagship site of the Stack Exchange Network, created in 2008 by Jeff Atwood and Joel Spolsky.


text:
Wedding Gown Preservation in Asheville, North Carolina with Reviews & Ratings - YP.comFind People•Advertise With UsBrowseFind PeopleFeatured CollectionsRestaurantsAutomotiveHome ImprovementHealth & WellnessAttorneysPeople Searched For...AttorneysDentistsMovie TheatersPlumbersUsed Car DealersRoofing ContractorsChinese RestaurantsDrug Abuse & Addiction CentersPet StoresFuel OilsIndoor PlaygroundsMoversMobile Home ParksPaving ContractorsPawn ShopsHeating Contractors & SpecialtiesFloristsBlack Hair Salons24 Hour LaundromatsChinese DeliveryInsuranceCatholic ChurchesMetaphysical StoresAre you alocal business owner?Advertise with YPor call 888-367-2194What do you want to find?Search by business name, or keywordnearWhere? Address, ZIP Code, or NeighborhoodMy current locationSearchSign In•JoinHomeAsheville, NCWedding Gown PreservationAsheville Wedding Gown PreservationSort:DefaultDefaultDistanceRatingName (A - Z)FiltersFiltersMore NeighborhoodsClaxton CommunityDoneClear AllMore CategoriesBlinds-Venetian, Vertical, Etc-Repair & CleaningBridal Gown PreservationBridal ShopsCarpet & Rug CleanersClothing AlterationsClothing StoresDrapery & Curtain CleanersDry Cleaners & LaundriesFormal Wear Rental & SalesLeather CleaningTuxedosWedding Supplies & ServicesWedding Tailoring & AlterationsWomen's ClothingWomen's Fashion AccessoriesDoneClear AllCategoryWedding Supplies & ServicesBridal Gown PreservationBridal ShopsMore »FeaturesBook a TableCouponsBook an AppointmentBBB Rated A+/ANeighborhoodsClaxton CommunitySponsored LinksAdd to mybookRemove from mybookAdded to your home collection!Error when adding to home collectionThis business was removed from the home collection1. Asheville CleanersServicesBBB Rating: A+230 Merrimon AveAsheville, NC 28801(828) 348-5092Blinds-Venetian, Vertical, Etc-Repair...WebsiteYP AdDirectionsMore InfoFrom Business: •Fine Dry Cleaning & Shirt Service •In Home Carpet Cleaning •Oriental & Area Rug Cleaning •Garment Storage •Alterations & Repairs •Drapery Cleaning •Feather Pillow …Add to mybookRemove from mybookAdded to your services collection!Error when adding to services collectionThis business was removed from the services collection2. Hour Glass Cleaners Of Asheville IncINNSBRUCK MallAsheville, NC 28805(828) 254-0791Wedding Supplies & ServicesMore InfoAdd to mybookRemove from mybookAdded to your shopping collection!Error when adding to shopping collectionThis business was removed from the shopping collection3. The Marriage Vine Formal Wear(24)336 Rockwood RdArden, NC 28704(828) 483-6191Formal Wear Rental & SalesWebsiteAll the way to Asheville and nothing but a perfect place; lots of different selection and sizes. Very helpful and friendly staff as well. Great pl…Add to mybookRemove from mybookAdded to your shopping collection!Error when adding to shopping collectionThis business was removed from the shopping collection4. Fairy Tale Gowns(1)317 Banner Farm RoadMills River, NC 28759(828) 606-2221Bridal ShopsWedding Supplies & ServicesWebsiteThis place is elegant, clean, lovely, and peacefu. Most gowns are very high end - gorgeous & pristine. I loved one from Priscilla of Boston, and…Sponsored LinksShowing1-4
of 4resultsAdd a New CollectionOops! There was a problem saving the new custom collection.Please try again.Collection Name cannot be emptyUpload a Photo(optional)Remaining Characters: 100Remaining Characters: 500CancelSaveMap ViewFeatured Bridal Gown Preservationin Asheville, North CarolinaLace And Company(1)Serving the Asheville area.WebsiteContact UsMore InfoGroup USA and Camille LaVie Women's Apparel(28)Serving the Asheville area.(888) 293-9461Unmistakable Style at an Irresistible Value!WebsiteShop OnlineMore InfoDidn't find what you were looking for?magnifying glassPlease help others by helping us do better.Suggest a BusinessAboutAbout UsSite FeedbackContact UsAdvertise with UsCareers - We're HiringCorporate BlogEngineering BlogLegal

value: This website is a United States-based web site operated by YP Holdings that provides listings for local businesses. In 2013 it was re-branded as YP.com or simply "YP".


text:
- Overall, the picture doesn't brighten much over four years. After four years, 36 percent of students did not demonstrate significant improvement, compared to 45 percent after two.
He said he can't remember the last time he wrote a paper longer than three pages, doublespaced. He feels little connection to his professors and gets the sense that mastering material is not as important as the drudge work of meeting goals and getting through material on schedule.

value: This website is an American multinational conservative cable news television channel based in New York City. It is owned by Fox News Media, which itself is owned by the Fox Corporation.


text:
Top Hotels in Kobe City Centre - Kobe, Japan | Hotels.com
Hotels near Kobe City Centre, Kobe
Search all hotels in Kobe City Centre
Find out more about Kobe City Centre
What you should know about Kobe City Centre
What's Kobe City Centre Like?
People go to Kobe City Centre to see attractions like Kobe Anpanman Children's Museum & Mall and to explore its green spaces like Meriken Park. You might want to seek out the monuments and waterfront while you’re in the neighborhood. Kobe Tower and Kobe Harborland are a couple of popular sights sure to leave an impression.
Where are the Best Places to Stay in Kobe City Centre?
We have 94 accommodations in the neighborhood. Listed below are our travelers' top places to stay in Kobe City Centre:
• Free WiFi • Health club • Café • Terrace • Walkable location
4-star hotel with 4 restaurants, indoor pool
• Free WiFi • Free train station shuttle • Outdoor pool • Health club • Central location
Adults-only ryokan with 3 restaurants, 2 bars
• Free WiFi • Free area shuttle • Spa tub • Health club • Comfy beds
How to Get to Kobe City Centre
Kobe City Centre is located 0.3 mi (0.5 km) from the heart of Kobe.
• Kansai Intl. Airport (KIX), 17.8 mi (28.7 km) from Kobe City Centre
• Kobe Airport (UKB), 4.4 mi (7.1 km) from Kobe City Centre
• Itami Airport (ITM), 15.8 mi (25.5 km) from Kobe City Centre
Getting to Kobe City Centre on Metro
• Motomachi Station
Things to See and Do in and around Kobe City Centre
What to See in Kobe City Centre
• Kobe City Hall
• Harborland Park
Things to Do in Kobe City Centre
• Kobe Maritime Museum
Other Popular Kobe City Centre Attractions
• Higashi Yuenchi Park
• Kobe Eiko Church

value: This website is a website for booking hotel rooms online and by telephone. The company has 85 websites in 34 languages, and lists over 325,000 hotels in approximately 19,000 locations.


text:
807 Grand Blvd,
http://www.awesomeflowersvancouver.com/
Factors that raised the rating for Awesome Flowers include:
File a Complaint against Awesome Flowers
See Trends in Customer Reviews on Awesome Flowers
BBB knows of no government actions involving the marketplace conduct of Awesome Flowers.
BBB has nothing to report concerning Awesome Flowers's advertising at this time.
Joel Padley, Owner
Principal: Joel Padley, Owner
See trends in Customer Reviews for Awesome Flowers Associated Searches

value: This website is a private, nonprofit organization whose self-described mission is to focus on advancing marketplace trust, consisting of 106 independently incorporated local BBB organizations in the United States and Canada, coordinated under the International Association of Better Business Bureaus  in Arlington, Virginia.The Better Business Bureau is not affiliated with any governmental agency. Businesses that affiliate with the BBB and adhere to its standards do so through industry self-regulation.


text:
Patent US20040125800 - Associated systems and methods for providing data services using idle cell ... - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsAssociated systems and methods for providing data services using idle cell capacity in a communications system. The systems and methods assign priorities to each remote user device in the communications system. In response to a request for service for a remote user device, the switch determines whether...http://www.google.com/patents/US20040125800?utm_source=gb-gplus-sharePatent US20040125800 - Associated systems and methods for providing data services using idle cell resourcesAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20040125800 A1Publication typeApplicationApplication numberUS 10/663,087Publication dateJul 1, 2004Filing dateSep 16, 2003Priority dateJul 30, 1997Also published asUS7349333, US8908610, US20080165731Publication number10663087, 663087, US 2004/0125800 A1, US 2004/125800 A1, US 20040125800 A1, US 20040125800A1, US 2004125800 A1, US 2004125800A1, US-A1-20040125800, US-A1-2004125800, US2004/0125800A1, US2004/125800A1, US20040125800 A1, US20040125800A1, US2004125800 A1, US2004125800A1InventorsSam ZellnerOriginal AssigneeSam ZellnerExport CitationBiBTeX, EndNote, RefManPatent Citations (27), Referenced by (49), Classifications (11), Legal Events (3) External Links: USPTO, USPTO Assignment, EspacenetAssociated systems and methods for providing data services using idle cell resources
DETAILED DESCRIPTION OF EMBODIMENTS [0028] Embodiments of the invention provide systems and methods for managing network resources, such as during an incoming call and for terminating a call. These systems and methods improve the management of network resources in a communications system, such as a packet-based communications system or a circuit switched communications system. Embodiments of the invention also manage limited network resources in an overload situation. [0029] Various aspects of the invention provide call management logic including retrieval of a caller profile, assessment of network resources, comparison of priorities, allocation of network resources including assessing all channels accessible from a mobile device, decision to queue a call, notification of action in queuing or terminating, and termination of a call. For incoming calls, other aspects of the invention provide call management logic including utilization of a priority profile of a called number, determination of the type of call, and providing an option to store or buffer incoming data for later delivery. [0030] One environment for an embodiment of the invention is a conventional cellular communications system. Such cellular communications systems include among others those constructed and operated in accordance with various well known standards, such as TDMA (IS-54 and IS-136), AMPS (IS-41), NAMPS, GSM, DCS1800, DCS1900, CDMA (IS-95), PACS, TACS, JTACS, and PDC. The invention also has applicability to any circuit switched communications system or network, as well as to any packet-based communications system or network. An example of a switched circuit communications network is a system having a control switch and a controlled node access point with a limited number of channels at each node, such as digital loop carrier networks. A suitable packet-based communications network is a communications system constructed and operated in accordance with various well known standards such as Short Messaging Service (SMS), General Packet Radio Service (GPRS), Enhanced Data rates for Global Evolution (EDGE), and the 1XRTT standard for Code Division Multiple Access (CDMA). [0031] Turning to the drawings in which like numbers reference like elements or steps, in the several figures, FIG. 1 of this specification is a schematic diagram of a packet-based communications system 100 which constitutes one environment for the invention. The packet-based communications system 100 shown comprises at least one packet switch 102 and a number of nodes, such as illustrated node 104. The packet switch 102 can be a packet switch, router, a switch adapted to handle data packets, or a switch adapted to handle data calls and voice calls. [0032] Generally, a calling party 106 transmits voice or data via a network 108. Note that the network 108 can be a packet-based network such as the Internet or other compatible type of communications network that handles data packets. In other embodiments, the network 108 may be a public switched telecommunications system, or another compatible communications-type network or system that can handle packet-type or radio communications. [0033] Each node, such as the node 104, transmits data to and receives data from at least one remote user, such as remote users 110 (mobile 1), 112 (mobile 2), and 114 (mobile 3) via a transmitter/receiver 116. Typically, communication between node 104 and remote users 110, 112, 114 is via radio frequency. Each node 104 has a limited number of channels on which data can be transmitted and received. While each of the remote users 110, 112, and 114 is illustrated as an automobile-based or mobile communication device user, the remote users may include a variety of devices or applications, such as personal digital assistants (PDAs), wireless telephones, handheld telephones, facsimile machines, messaging devices, computers, telemetry devices, and control devices, among others. [0034] The packet switch 102 comprises a buffer 118, a node controller 120, and a database 122. The node controller 120 can be a high-speed general purpose digital computer that is programmed to control the functions required of the packet switch 102. The database 122 can be a memory or storage-type device under control of the node controller 120. The database 122 is similar in functionality to a home location register (HLR), in that the database 122 includes profile and authorization information including the priority for each of the remote users 110, 112, 114. The buffer 118 is also a memory device under control of the node controller 120 that is used to receive and store data for later delivery to a remote user in communication with the packet switch 102 in accordance with one aspect of the invention. While the buffer 118 and database 122 are illustrated as within the packet switch 102, the buffer 118 and database 122 could be remotely located. [0035] The database 122 is configured to store a profile for each remote user, such as a caller profile that includes caller information such as priority information. Priority information can be a predetermined priority for a particular caller, or a predetermined priority for a particular service that the caller is utilizing at a particular moment or time. Caller information can include identification information such as a caller's name, a predetermined user name, or directory number. A profile for remote users, including priority information and identification information associated with each remote user, can also be stored by the database 122. [0036] The node controller 120 can determine different priorities of service for voice calls and data calls. In order to determine different priorities of service, each remote user device is assigned a priority based on the nature of use of that remote user device. Each user's priority assignment is associated with the user's mobile identification number (MIN), another identification-type number or device, an application performed by the user, or a device operated by the user. When a remote user device communicates with the node controller 120, the node controller receives priority information associated with the respective remote user device, or can otherwise access the database to retrieve priority information associated with a profile for the remote user device. For example, the MIN associated priorities of each user are stored in the database 122 at the packet switch 102. Mobile telephones, which provide voice call service, can be assigned a relatively high priority. On the other hand, personal digital assistants (PDAs), wireless facsimile machines, wireless e-mail systems, and other devices or applications are assigned a relatively lower priority. In any instance, the node controller 120 calls to the database 122 to retrieve priority information of a user. [0037] While the system 100 shown is described in connection with at least two priorities, high priority for voice and low priority for data, the system 100 also lends itself to multiple priorities. Each lower level of priority offers the opportunity for lower charges by the service provider to customers with low priority needs for transmission of data. Conversely, high priority service rationally brings with it the opportunity to charge more by the service provider. [0038] Multiple priorities can be based on the application being used. For example, if one remote user is using a facsimile application, a relatively higher priority can be assigned to this remote user than to a remote user using an e-mail application. Typically, applications involving voice or large amounts of data will be assigned a higher priority than those applications involving data or relatively little amounts of data. In some instances, there could be multiple priorities within an application. For example, an e-mail application can be subdivided to provide higher and lower levels of priority service, such as in the case of a user identifying particular e-mails with a “high,” “medium,” or “low” priority. Those e-mails identified with a relatively higher priority receive higher priority service than those with a lower level of priority service. [0039] Priority can be based on a mobile address or other address used to route information to the mobile user. For example, an address can include, but is not limited to, a mobile identification number (MIN), and Internet Protocol (IP) address, or another similar type routing address associated with a remote user. [0040] In addition, a remote user device could be assigned multiple MINs each with a different priority or a mixture of priorities. Such multiple MIN devices could thus provide, for example, three channels of service, one channel of high priority service and two additional channels of lower priority data service. Such devices would have high priority access for data transmission at all times and during off-peak times could use all three channels for enhanced speed data transmission using all three channels together. [0041] In some instances, the system 100 shown can be used to notify large numbers of remote or mobile users in a “broadcast” call-type situation, such as an emergency situation. In these types of instances, an emergency message with a priority of an appropriate level is associated with the emergency call. A broadcast call could be in the form of a voice call or data call. When a broadcast call is placed, the call is provided an appropriate priority for the type of broadcast message being transmitted. [0042] The buffer 118 can be used to store and forward data to further assist with prioritizing delivery of data to remote users. For real-time services such as voice and some types of data (e.g., video conferencing), user satisfaction can be impacted by delays in data transmission. However, for many types of data transmission a few seconds or few minutes does not impact overall user satisfaction. Thus, methods for storing and forwarding data can further assist in implementing prioritization of calls in accordance with the invention. [0043] Using the system 100 shown, voice call service could obtain immediate access to a channel and continuity of connection over the channel for the duration of the voice call. Voice call service can be considered unacceptable by remote users if a remote user cannot acquire a channel quickly and/or if voice calls are dropped during a conversation. By contrast, data call service does not need the same immediacy of access or continuity of connection. An e-mail message or a facsimile document may be delayed for several minutes or even hours without adversely effecting the usefulness of the data call service. Likewise transmission of an e-mail message or a facsimile document can be interrupted and then resumed without adversely effecting the service as long as the resumption can pick up the transmission at the point of interruption. [0044] Various methods for managing network resources in accordance with the invention, such as during an incoming call and for terminating a call, can be implemented with the packet-based communications system 100 shown and described in FIG. 1. FIGS. 2, 3A, and 3B illustrate methods for managing network resources such as during an incoming call and for terminating a call. Each of the illustrated methods utilize specific call management logic routines with which an incoming call and a call termination are treated based upon the associated prior and current priorities of respective calls. [0045] Turning to FIG. 2, there is shown a flow diagram showing a method 200 of the invention when a remote user (mobile 1 110) requests service at a particular node 104. The method 200 begins at block 202 with a request for service from mobile 1 in node 104. The request for service is transmitted to the packet switch 102. In some instances, a determination of the type of service requested can be made at block 202. For example, a determination whether a request for service is for voice service, data service, or another type of service can be made. Depending upon the type of service requested, feedback to the caller can be provided, or the request for service can be routed or handled in a particular manner. [0046] Block 202 is followed by block 204, in which the node controller 120 queries the database 122 to determine the priority of service for mobile 1 based on mobile 1's profile and authorization information. Mobile 1's profile and authorization information was provided to the packet switch 102 when mobile 1 110 first registered with the service provider for the packet-based communications system 100. After acquiring the profile and authorization information including the priority for mobile 1 110 from the database 122 at block 204, the method 200 proceeds to decision block 206. [0047] At decision block 206, the node controller 120 of the packet switch 102 ascertains whether there is an idle channel available to service the request for service from mobile 1 110. If at decision block 206, the node controller 120 of the packet switch 102 determines that there is an idle channel at node 104, the method 200 follows the “yes” branch to block 208, and the idle channel is assigned to mobile 1 110 without regard to mobile 1's priority. When the call of mobile 1 110 is completed, the method 200 proceeds from block 208 to block 210 where the completed call is terminated for mobile 1 110. [0048] Note that the node controller 120 can also assess other network resources such as all available radio channels accessible from or by mobile 1 110. Other network resources include, but are not limited to, channels at one or more cell sites in communication with node 104, and channels associated with other nodes in communication with the network 108, similar to those associated with node 104. [0049] If on the other hand there is not an idle channel available at decision block 206, the method 200 follows the “no” branch from decision block 206 to decision block 212. At decision block 212, the method 200 determines if there is a current remote user in communication with node 104 that has a priority lower than mobile 1's priority. Note that a comparison is made between the priority associated with mobile 1 110 and a priority associated with at least one current remote user. Preferably, mobile 1's priority is compared to all current remote users in communication with the node 104. If all the users have a priority equal to or higher than mobile 1's priority, the method 200 follows the “no” branch to decision block 214. [0050] At decision block 214, based on the profile and authorization information for mobile 1, the node controller 120 determines whether mobile 1's call request should be queued for later connection. If mobile 1's profile and authorization information does not authorize queuing, the method 200 follows the “no” branch to block 216 where mobile 1's call request is ended. Mobile 1 110 may not want to queue its call request if, for example, mobile 1 110 is a low priority voice service. Such a low priority voice caller expects to be precluded from the network 108 from time to time, but such a voice caller probably does not want to wait in a queue of undermined length. Instead such a low priority voice caller may simple want to place the call later. [0051] On the other hand, if mobile 1 110 is a low priority data service, such a data caller may want to queue his call for later service. If the node controller 120 determines at decision block 214 that mobile 1 110 has registered with the service provider for queuing, the method then follows the “yes” branch to block 218. [0052] At block 218 the call request from mobile 1 110 is put into a queue to await the next available channel in node 104. At block 218, the node controller 120 also notifies mobile 1 110 that its call request has been queued so that mobile 1 110 does not continue to send new call requests to the packet switch 102. [0053] Alternatively, the call request from mobile 1 110 may be handled at block 218 if a request for data service is made. For example, if an incoming call requests transmission of data, data can be stored in buffer 118 for subsequent transmission at a later time. Still the call request may be queued as described in block 220, and the data transmitted when the call request is subsequently handled by the method 200. [0054] Block 218 is followed by block 220, in which the queue is ordered by priority and time of wait so that the call request with the highest priority and the longest waiting time is at the head of the queue and will be assigned the next available channel in node 104. Note that in other embodiments of the invention, the queue can be ordered based on other criteria based on priority. For example, the instant call request can be placed at the head of the queue if the call request has or is provided a sufficient priority. [0055] After ordering the queue at block 220, the method 200 returns to decision block 206 to seek the next available channel in node 104 for the call request for the remote user at the head of the queue. [0056] If, however, at decision block 212, the node controller 120 determines that a channel in node 104 is being used by a remote user, such as mobile 2 112, with a priority lower than mobile 1 110, the method 200 follows the “yes” branch to block 222. [0057] At block 222, the node controller 120 terminates mobile 2's lower priority data call, and at block 208, the node controller 120 allocates the vacated channel to mobile 1 110. Mobile 1's call is complete and terminated at block 210. [0058] The selection of mobile 2 112 for call termination at block 222 is based on the priority of mobile 2 112 and on the duration of mobile 2's call at the time of termination. For example, if several current remote users have the same priority as mobile 2 112, which is priority is lower than mobile 1 110, the node controller 120 will terminate the remote user that has been connected for the longest time. In this case, mobile 2 112 is assumed to be the call with the longest duration of those users with the same priority as mobile 2 112. As part of the termination process of mobile 2 112, the software or other device or method that controls the transmission of data to and from mobile 2 112 will recognize the termination and mark the point in the transmission where call termination occurred. On resumption of the call to mobile 2 112, the software or other device or method will be able to pick up the data transfer at the point of termination. [0059] Alternatively, transmission of data to and from mobile 2 112 may stored in buffer 118 for subsequent transmission at a later time. [0060] After the call of mobile 2 112 has been terminated at block 222, the method 200 proceeds to decision block 224 where, based on mobile 2's profile and authorization information, the node controller 120 determines whether a request by mobile 2 112 for resumption of its call should be put in the queue. If mobile 2's profile and authorization information does not authorize queuing, the method 200 follows the “no” branch from decision block 224 to block 216 where mobile 2's call request to resume is ended. [0061] Alternatively, the method follows the “yes” branch from decision block 224 to block 226 where the node controller 120 puts a request to resume the terminated call of mobile 2 112 into the queue. At block 226, the node controller 120 also notifies mobile 2 112 that its call has been queued so that mobile 2 112 will not try to reestablish its call by new call requests to the packet switch 102. [0062] The queue is ordered at block 220 as previously described, and the ordered call requests in the queue wait for the next available channel in node 104 as indicated by the return path to decision block 206. Note that in other embodiments of the invention, the queue can be ordered based on other criteria based on priority. For example, the instant call request can be placed at the head of the queue if the call request has or is provided a sufficient priority. [0063] If the terminated call for mobile 2 112 was transferring data to mobile 2 112 at the time of termination, the node controller 120 may maintain the connection to the network 108 for resumption of data transfer when the call to mobile 2 112 is resumed on an idle channel. Alternatively, the node controller 120 may store all of the data from the caller in buffer 118, terminate the call from the network 108, and transfer the data from the buffer 118 to mobile 2 112 upon reacquisition of an idle channel for mobile 2 112. Such storing and forwarding of data will be described in greater detail in connection FIG. 3A. If on the other hand, the terminated call of mobile 2 112 was transferring data from mobile 2 112 to a caller on the network 108, the node controller 120 will maintain the connection to the network 108 until a channel for mobile 2 112 is reacquired and the transmission is complete. [0064] Turning to FIGS. 3A and 3B, flow diagrams show another method 300 of the invention when a caller or calling party 106 from the network 108 requests service to the remote user (mobile 1 110) in communication with node 104. For an incoming call, at least one method implementing call management logic can include elements such as utilizing the priority profile of the called number; determining the type of call (voice or data); and/or providing the option to store (or buffer) the incoming data for later delivery. The call management logic implementing some or all of these elements can be combined as needed, and can be applied to packet-based communications systems and associated services, such as SMS, GPRS, EDGE, 1XRTT services, as well as the system 100 shown in FIG. 1. For some packet-based communications systems and associated services, the use of queuing (i.e., suspend transmission) rather than terminating a session is an option. [0065] The method 300 begins at block 302 with a request for service from the network 108 for a call to mobile 1 110 via node 104. The request for service to mobile 1 110 is transmitted from the network 108 to the packet switch 102. After receiving the call request at block 302, the method 300 proceeds to block 304. [0066] At block 304, the node controller 120 queries the database 122 to determine the priority of service for mobile 1 110 based on the profile and authorization information for mobile 1's MIN. Based on the priority of mobile 1 110, the node controller 120 determines at decision block 306 whether the call is a data transfer call. If at decision block 306 the node controller 120 determines that the call is not a data transfer call, the method 300 follows the “no” branch to decision block 308 described below and shown in FIG. 3B. [0067] If at decision block 306 the node controller 120 determines that the call is a data transfer call, the method 300 follows the “yes” branch to decision block 310. At decision block 310, the node controller 120 determines whether the data should be stored in the buffer 118. The decision to store or not to store data at decision block 310 is based on the node controller's estimation of the length of wait before a connection can be made to mobile 1 110. If data is not stored, the method 300 follows the “no” branch to decision block 308 (FIG. 3B) and retains the connection to the inbound caller on the network 108. If the data is stored at decision block 310, the method 300 follows the “yes” branch to block 312. [0068] At block 312, the inbound data from the network 108 is stored in buffer 118, and the connection from the network 108 is terminated. The use of buffer 118 and block 312 is optional, and the packet switch 102 could simply maintain the connection to the network 108 until the data transmission to mobile 1 110 is complete. After the data is stored in buffer 118 at block 312, the method 300 proceeds to block 308 (FIG. 3B). [0069] Referring now to FIG. 3B, at block 308, the node controller 120 of the packet switch 102 ascertains whether there is an idle channel available for servicing the call request to mobile 1 110. If there is an idle channel in node 104, the method 300 follows the “yes” branch to block 314, and the idle channel is allocated to mobile 1 110 without regard to the priority of mobile 1 110. Once the call to mobile 1 110 has been completed, the method 300 proceeds to block 316 where the call to mobile 1 110 is terminated and the data for mobile 1 110 is emptied (marked to be overwritten) from the buffer 118 if applicable. [0070] Turning back to decision block 308, if there is no idle channel available, the method 300 follows the “no” branch to decision block 318. At decision block 318, the method 300 determines if there is a current remote user in node 104 that has a priority lower than mobile 1's priority. If all the users have a priority equal to or higher than mobile 1's priority, the method 300 follows the “no” branch to block 320. At block 320, the node controller 120 determines from mobile 1's profile and authorization information and from the handling of the inbound data whether the call request to mobile 1 110 should be queued. If the inbound data was not stored at block 312 (shown in FIG. 3A), then the call request to mobile 1 110 may not be queued, and the method 300 follows the “no” branch to block 322 where the inbound call request is ended, and the inbound caller is notified that no connection was made to mobile 1 110. If the inbound data was stored at block 312 (FIG. 3A), then the call request to mobile 1 110 will be placed in an order queue by the node controller 120, and the method 300 will follow the “yes” branch to block 324. [0071] At block 324 the call request to mobile 1 110 is put into the ordered queue, mobile 1 110 is notified that it has an inbound queued call request awaiting the next available channel in node 104. [0072] Block 324 is followed by block 326, in which the queue is ordered by priority and time of wait so that the call request with the highest priority and the longest waiting time is moved to the head of the queue for assignment to the next available channel in node 104. Note that in other embodiments of the invention, the queue can be ordered based on other criteria based on priority. For example, the instant call request can be placed at the head of the queue if the call request has or is provided a sufficient priority. After ordering the queue at block 326, the method 300 returns to decision block 308 to seek the next available channel in node 104 for the call request at the head of the ordered queue. [0073] If, however, at decision block 318, the node 120 determines that a channel in node 104 is being used by a remote user, such as mobile 2 112, with a priority lower than mobile 1 110, the method 300 follows the “yes” branch to block 328. At block 328, the node controller 120 terminates mobile 2's lower priority data call, and at block 314 allocates the vacated channel to mobile 1. The selection of mobile 2 112 for call termination is based on the priority of mobile 2 112 and on the duration of mobile 2's call at the time of termination. As part of the termination process for mobile 2 112, the software that controls the transmission of data to and from mobile 2 112 will recognize the termination and mark the point in the transmission where call termination occurred. On resumption of the call to mobile 2, the software will pick up the data transfer at the point of termination. [0074] After the call of mobile 2 112 has been terminated at block 328, the method 300 proceeds to decision block 330 where the node controller 120 determines whether mobile 2's request to resume its connection should be queue or ended. If the call request to resume is to be ended, the method 300 follows the “no” branch to block 322 where the node controller 120 ends the request of mobile 2 112 to resume its terminated call. Alternatively, the method 300 follows the “yes” branch from decision block 330 to block 332 where the node controller 120 puts mobile 2's request to resume its terminated call into the ordered queue and notifies mobile 2 112 that its request to resume has been queued. [0075] Block 332 is followed by block 326, in which the queue is ordered, and the call requests in the queue wait for the next available channel in node 104 for the call request at the head of the ordered queue as indicated by the return path to decision block 308. [0076] Based on the foregoing it should also be appreciated that the invention also contemplates multiple priorities for multiple levels of service. For example, voice callers could be given multiple levels to distinguish emergency services from other voice calls. On a lower priority level, data transmissions could be further subdivided, for example, to provide a higher priority for facsimile transmission than for e-mail. Further, e-mail could be further subdivided to provide higher and lower levels of priority service. Priority can be based on a mobile address such as a MIN, IP (Internet Protocol), or any other address used to route information to a mobile user. Each priority could be offered to any mobile user 110, 112, 114 at a separate cost or billing rate by a communications service provider. The ordering of the queue in the packet switch 102 assures that the various requests for service for each calling device is serviced in the proper priority order as idle channels become available. [0077] While the invention has been described in connection with a packet-based communications system, the invention is equally applicable to any packet-based communications system having a packet switch for controlling access to a network access node with a limited number of access channels for serving remote users. Alternatively, the invention is applicable to a switched communications system having a switch for controlling access to a network access node with a limited number of access channels for serving remote users. Digital loop carriers are another example of such a switched communications system environment in which the invention finds applicability. [0078] In a communications network such as a packet-based communications network or switched communications network, a notification can be a message generated by a switch such as a packet switch, and sent via a control channel to a mobile or remote device. As described in the methods 200 of FIG. 2 and 300 of FIG. 3B, and implemented by the system 100 shown in FIG. 1, a packet switch 102 can notify a mobile or remote device 110, 112, 114. Specifically, in block 218 of FIG. 2, and also in block 324 of FIG. 3B, a notification is sent to a subscriber or remote user associated with a mobile or remote device, such as mobile 1 110. Alternatively, as shown in block 226 of FIG. 2 and also in block 332 of FIG. 3B, a notification can be sent to a subscriber or remote user associated with a mobile or remote device, such as mobile 2 112. Other mobile or remote devices can receive a notification in this or other embodiments of the invention. [0079] In a notification, information can be provided to the subscriber or remote user regarding the activities of the packet switch 102 and/or network 108. That is, the packet switch 102 and/or network 108 generates a message including information for the subscriber and sends the message to an application, mobile device, or end-user so that the subscriber can take appropriate action. Message information can include, but is not limited to, a termination alert, a queuing placement, duration of an expected delay, time-of-day, redirection regarding better frequency, service level, service type, pricing, recommended retry time, and an alternative service provider. Other types of notification to a mobile or remote device with various message information can be implemented in accordance with the invention. [0080] For example, a notification can inform a user of queuing status for a call. As shown in block 218 of FIG. 2 and in block 324 of FIG. 3B, a notification can be sent by the packet switch 102 to the mobile or remote device such as mobile 1 110. The notification can include a status message implemented in a predefined “CALL_PROCEEDING” field sent via a control channel to the mobile or remote device. The status message could include the text, “Queue 4”, signifying that the request has been placed in a queue, and that the current level assigned to the request is the fourth level from the top level, with the first level being the highest priority level. [0081] Shorter or longer messages may be generated in a “CALL_PROCEEDING” field sent via a control channel to the mobile or remote device. Generally, it is preferable to provide as much information as possible regarding the activities in the network to a user associated with a remote or mobile device so that the user can take appropriate action. [0082] Alternatively, a status message could include the listing of all queues by service level and placement of a service request. For example, a status message could include all or a portion of the following information: Q1-3, Q2-2*, Q3-5, . . . Q(n)-(x)*, wherein “Q(n)” represents a service level queue for number ‘n,’ “x” is the number of requests in a queue for a particular service level, and “*” represents the current placement of the particular service request. [0083] Notification can be implemented prior to call termination and queuing. In many instances involving call termination for lack of network resources and/or higher priority callers, the system determines a call to be terminated. The invention provides notification to this remote user prior to terminating and queuing the call. In some instances, message information can include an interactive query to obtain or otherwise receive information from the subscriber. Interactive features can guide or otherwise provide a remote user with various options to increase or decrease the remote user's priority. For example, a remote user can be prompted by a message notifying the user that the call will be terminated unless the remote user increases the class of service for the call, from class of service 1 to class of service 2. If the remote user accepts an increase in class of service to avoid termination of the call, the remote user can be charged or otherwise billed by the service provider for the increase in class of service for the call. Alternatively, a remote user can be prompted to increase the priority of the call based on the nature of the call, such as an emergency situation. The remote user could transmit a selected option indicating the call is for an emergency situation, and increase the priority of the call as needed. In other instances, the mobile device can be programmed to automatically request a higher priority to be associated with a call request. However, in most cases, if a call is made to a predetermined directory number for emergency services such as “911” or “1-800-555-1212,” the priority of the call can automatically be increased as needed. Information obtained from or received from the subscriber can be sent from the mobile or remote device back to the packet switch 102. In these types of interactions, improved Quality of Service (QoS) can result when the subscriber can obtain information from the network 108, and then take appropriate action or otherwise respond to the information. [0084] [0084]FIGS. 4, 5A, and 5B illustrate methods associated with a notification in accordance with other embodiments of the invention. In the following FIGS. 4, 5A, and 5B, a notification such as a termination alert is provided to a mobile or remote device. The notification described in the following examples also provides a query to a user of the mobile or remote device, and in response to the query, the user can send information back to the packet switch. [0085] Turning to FIG. 4, a flow diagram illustrates an associated method of notification in accordance with various embodiments of the invention. FIG. 4 is similar to the method shown in FIG. 2 when the remote user 110 (mobile 1) requests service from within the node 104, except method 400 of FIG. 4 provides additional elements of notification. The method 400 of FIG. 4 begins at block 402 with a request for service from mobile 1 110 in communication with node 104. The request for service is transmitted to the packet switch 102. [0086] Block 402 is followed by block 404, in which the node controller 120 queries the database 122 to determine the priority of service for mobile 1 110 based on mobile 1's profile and authorization information. Mobile 1's profile and authorization information was provided to the packet switch 102 when mobile 1 110 first registered with the service provider for the communications system 100. After acquiring the profile and authorization information including the priority for mobile 1 110 from the database at block 404, the method 400 proceeds to decision block 406. [0087] At decision block 406, the node controller 120 of the packet switch 102 ascertains whether there is an idle channel available to service the request for service from mobile 1 110. If at decision block 406, the node controller 120 of the packet switch 102 determines that there is an idle channel in node 102, the method 400 follows the “yes” branch to block 408 and the idle channel is assigned to mobile 1 110 without regard to mobile 1's priority. When the call of mobile 1 110 is completed, the method 400 proceeds to block 410 where the completed call is terminated for mobile 1 110. [0088] If on the other hand there is not an idle channel available at decision block 406, the method 400 follows the “no” branch from decision block 406 to decision block 412. At decision block 412, the method 400 determines if there is a current remote user in communication with node 104 that has a priority lower than mobile 1's priority. If all the users have a priority equal to or higher than mobile 1's priority, the method 400 follows the “no” branch to decision block 414. [0089] At decision block 414, based on the profile and authorization information for mobile 1 110, the node controller 120 determines whether mobile 1's call request should be queued for later connection. If mobile 1's profile and authorization information does not authorize queuing, the method 400 follows the “no” branch to block 416 where mobile 1's call request is ended. Mobile 1 110 may not want to queue its call request if, for example, mobile 1 110 is a low priority voice service. Such a low priority voice caller can expect to be precluded from the network from time to time, but such a voice caller probably does not want to wait in a queue of undermined length. Instead such a low priority voice caller may simple want to place the call later. [0090] On the other hand, if mobile 1 110 is a low priority data service, such a data caller may want to queue his call for later service. If the node controller 120 determines at block 414 that mobile 1 110 has registered with the service provider for queuing, the method 400 then follows the “yes” branch to block 418. At block 418 the call request from mobile 1 110 is put into a queue to await the next available channel in node 104. At block 418, the node controller 120 also notifies mobile 1 110 that its call request has been queued so that mobile 1 110 does not continue to send new call requests to the packet switch 102. [0091] Block 418 is followed by decision block 420, in which a determination is made whether the call is to be terminated. Typically, a notification sent to mobile 1 110 queries a remote user whether the call should be terminated. The notification can be a message to the remote user including a query prompting the remote user to accept or decline termination of the call. In any event, a response from the remote user and/or mobile 1 is sent back to the packet switch 102 for appropriate call handling. If the remote user does not accept call termination, then the “no” branch is followed to block 422. [0092] At block 422, the queue is ordered by priority and time of wait so that the call request with the highest priority and the longest waiting time is at the head of the queue and will be assigned the next available channel associated with node 104. After ordering the queue at block 422, the method 400 returns to block 406 to seek the next available channel associated with node 104 for the call request for the remote user at the head of the queue. [0093] If, however, the remote user accepts call termination at decision block 420, then the “yes” branch is followed to block 424 where the method 400 terminates the call. [0094] If, however, at block 412, the node controller 120 determines that a channel in node 104 is being used by a remote user, such as mobile 2 112, with a priority lower than mobile 1 110, the method 400 follows the “yes” branch to block 426. At block 426, the node controller 120 terminates mobile 2's lower priority data call, and at block 408, the node controller 120 allocates the vacated channel to mobile 1 110. Mobile 1's call is complete and terminated at block 410. [0095] The selection of mobile 2 for call termination at block 426 is based on the priority of mobile 2 112 and on the duration of mobile 2's call at the time of termination. For example, if several current remote users have the same priority as mobile 2 112, which is priority is lower than mobile 1 110, the node controller 120 will terminate the remote user that has been connected for the longest time. In this case mobile 2 112 is assumed to be the call with the longest duration of those users with the same priority as mobile 2 112. As part of the termination process of mobile 2 112, the software or device or method that controls the transmission of data to and from mobile 2 112 will recognize the termination and mark the point in the transmission where call termination occurred. On resumption of the call to mobile 2 112, the software or device or method will be able to pick up the data transfer at the point of termination. [0096] After the call of mobile 2 112 has been terminated at block 426, the method 400 proceeds to decision block 428 where, based on mobile 2's profile and authorization information, the node controller 120 determines whether a request by mobile 2 112 for resumption of its call should be put in the queue. If mobile 2's profile and authorization information does not authorize queuing, the method 200 follows the “no” branch from decision block 428 to block 416 where mobile 2's call request to resume is ended. Alternatively, the method follows the “yes” branch from decision block 428 to block 430 where the node controller 120 puts a request to resume the terminated call of mobile 2 112 into the queue. At block 430, the node controller 120 also notifies mobile 2 112 that its call has been queued so that mobile 2 112 will not try to reestablish its call by new call requests to the packet switch 102. [0097] Block 430 is followed by decision block 420, in which a determination is made whether the call is to be terminated. Typically, a notification sent to mobile 2 112 queries a remote user whether the call should be terminated. The notification can be a message to the remote user including a query prompting the remote user to accept or decline termination of the call. In any event, a response from the remote user and/or mobile 2 112 is sent back to the packet switch 102. If the remote user accepts call termination, then the “yes” branch is followed to block 424, where the call is terminated. [0098] If the user does not accept call termination at decision block 420, then the “no” branch is followed to block 422. As previously described, the queue is ordered, and the ordered call requests in the queue wait for the next available channel in node 104 as indicated by the return path to decision block 406. At decision block 406, the method 400 seeks the next available channel associated with node 104 for the call request for the remote user at the head of the queue. [0099] If the terminated call for mobile 2 112 was transferring data to mobile 2 112 at the time of termination, the node controller 120 may maintain the connection to the calling party 106 for resumption of data transfer when the call to mobile 2 112 is resumed on an idle channel. Alternatively, the node controller 120 may store all of the data from the caller in buffer 118, terminate the call from the network 108, and transfer the data from the buffer 118 to mobile 2 112 upon reacquisition of an idle channel for mobile 2 112. Such storing and forwarding of data will be described in greater detail in FIG. 5A. If on the other hand the terminated call of mobile 2 112 was transferring data from mobile 2 112 to a caller on the network 108, the node controller 120 will maintain the connection to the network 108 until a channel for mobile 2 112 is reacquired and the transmission is complete. [0100] [0100]FIGS. 5A and 5B illustrates a flow diagram showing another method of notification in accordance with various embodiments of the invention. FIGS. 5A and 5B illustrate a method 500 similar to the method in 300 shown in FIGS. 3A and 3B when a caller from network 108 requests service to the remote user 110 (mobile 1) within the node 104. The method 500 of the invention begins at block 502 with a request for service from the network 108 for a call to mobile 1 in node 104. The request for service to mobile 1 is transmitted from the network 108 to the packet switch 102. After receiving the call request at block 502, the method 500 proceeds to block 504. [0101] At block 504, the node controller 120 queries the database 122 to determine the priority of service for mobile 1 based on the profile and authorization information for mobile 1's MIN. Based on the priority of mobile 1, the node controller 120 determines at decision block 506 whether the call is a data transfer call. If at decision block 506 the node controller 120 determines that the call is not a data transfer call, the method follows the “no” branch to decision block 508 described and shown below in FIG. 5B. [0102] If at decision block 506 the node controller 120 determines that the call is a data transfer call, the method follows the “yes” branch to block 510. At block 510, the node controller 120 determines whether the data should be stored in the buffer 118. The decision to store or not to store data at block 510 is based on the node controller's estimation of the length of wait before a connection can be made to mobile 1 110. If data is not stored, the method 500 follows the “no” branch to decision block 508 (FIG. 5B) and retains the connection to the inbound caller on network 108. If the data is stored at block 510, the method 500 follows the “yes” branch to block 512. [0103] At block 512, the inbound data from the network 108 is stored in buffer 118, and the connection from the network 108 is terminated. The use of buffer 118 and block 512 is optional, and the packet switch 102 could simply maintain the connection to the network 108 until the data transmission to mobile 1 110 is complete. After the data is stored in buffer 118 at block 512, the method 500 proceeds to block 508 (FIG. 5B). [0104] At decision block 508, the node controller 120 of the packet switch 102 ascertains whether there is an idle channel available for servicing the call request to mobile 1 110. If there is an idle channel in node 104, the method 500 follows the “yes” branch to block 514, and the idle channel is allocated to mobile 1 110 without regard to the priority of mobile 1 110. Once the call to mobile 1 110 has been completed, the method 500 proceeds to block 516 where the call to mobile 1 110 is terminated and the data for mobile 1 110 is emptied (marked to be overwritten) from the buffer. [0105] If there is no idle channel available, the method 500 follows the “no” branch to decision block 518. At decision block 518, the method 500 determines if there is a current remote user in node 104 that has a priority lower than mobile 1's priority. If all the users have a priority equal to or higher than mobile 1's priority, the method follows the “no” branch to block 520. At block 520, the node controller 120 determines from mobile 1's profile and authorization information and from the handling of the inbound data whether the call request to mobile 1 110 should be queued. If the inbound data was not stored at block 512 in FIG. 5A, then the call request to mobile 1 110 may not be queued, and the method 500 follows the “no” branch to block 522 where the inbound call request is ended, and the inbound caller is notified that no connection was made to mobile 1 110. If the inbound data was stored at block 512 in FIG. 5A, then the call request to mobile 1 110 will be placed in an order queue by the node controller 120, and the method 500 will follow the “yes” branch to block 524. [0106] At block 524 the call request to mobile 1 110 is put into the ordered queue, mobile 1 110 is notified that it has an inbound queued call request awaiting the next available channel in node 104. [0107] Block 524 is followed by decision block 526, in which a determination is made whether the call is to be terminated. Typically, a notification sent to mobile 1 110 queries a remote user whether the call should be terminated. The notification can be a message to the remote user including a query prompting the remote user to accept or decline termination of the call. In any event, a response from the remote user and/or mobile 1 is sent back to the packet switch. If the remote user accepts call termination, then the “yes” branch is followed to block 528 where the method 500 terminates the call. [0108] If the user does not accept call termination at decision block 526, then the “no” branch is followed to block 530 where the queue is ordered. [0109] At block 530 the queue is ordered by priority and time of wait so that the call request with the highest priority and the longest waiting time is moved to the head of the queue for assignment to the next available channel in node 104. After ordering the queue at block 530, the method 500 returns to block 508 to seek the next available channel in node 104 for the call request at the head of the ordered queue. [0110] If, however, at block 518, the node controller 120 determines that a channel in node 104 is being used by a remote user, such as mobile 2 112, with a priority lower than mobile 1 110, the method 500 follows the “yes” branch to block 532. At block 532, the node controller 120 terminates mobile 2's lower priority data call, and at block 514 allocates the vacated channel to mobile 1 110. The selection of mobile 2 112 for call termination is based on the priority of mobile 2 112 and on the duration of mobile 2's call at the time of termination. As part of the termination process for mobile 2 112, the software that controls the transmission of data to and from mobile 2 112 will recognize the termination and mark the point in the transmission where call termination occurred. On resumption of the call to mobile 2 112, the software will pick up the data transfer at the point of termination. [0111] After the call of mobile 2 has been terminated at block 516, the method 500 proceeds to decision block 534 where the node controller 120 determines whether mobile 2's request to resume its connection should be queued or ended. If the call request to resume is to be ended, the method 500 follows the “no” branch to block 522 where the node controller 120 ends the request of mobile 2 112 to resume its terminated call. Alternatively, the method 500 follows the “yes” branch from block 534 to block 536 where the node controller 120 puts mobile 2's request to resume its terminated call into the ordered queue and notifies mobile 2 112 that its request to resume has been queued. [0112] At decision block 526, a determination is made whether the call is to be terminated. Typically, a notification sent to mobile 2 112 queries a remote user whether the call should be terminated. The notification can be a message to the remote user including a query prompting the remote user to accept or decline termination of the call. In any event, a response from the remote user and/or mobile 2 112 is sent back to the packet switch. If the remote user accepts call termination, then the “yes” branch is followed to block 528 where the method 400 terminates the call. [0113] If the user does not accept call termination at decision block 526, then the “no” branch is followed to block 530 where the queue is ordered. The call requests in the queue wait for the next available channel in node 104 for the call request at the head of the ordered queue as indicated by the return path to block 508. The method 500 then returns to block 508 to seek the next available channel in node 104 for the call request for the remote user at the head of the queue. [0114] While the above description contains many specifics, the specifics should not be construed as limitations on the scope of the invention, but merely as exemplifications of the disclosed embodiments. Those skilled in the art will envision many other possible variations that are within the scope of the invention. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS5131020 *Dec 29, 1989Jul 14, 1992Smartroutes Systems Limited PartnershipMethod of and system for providing continually updated traffic or other information to telephonically and other communications-linked customersUS5343511 *May 8, 1992Aug 30, 1994Fujitsu LimitedMethod for selecting a broadcast voice channel served in a telephone switching network, and a system thereofUS5404355 *Oct 5, 1992Apr 4, 1995Ericsson Ge Mobile Communications, Inc.Method for transmitting broadcast information in a digital control channelUS5513242 *May 31, 1994Apr 30, 1996At&T Corp.Method and apparatus for facilitating the ultimate making of wireless data transfersUS5521925 *Sep 9, 1993May 28, 1996Hughes Aircraft CompanyMethod and apparatus for providing mixed voice and data communication in a time division multiple access radio communication systemUS5574977 *Apr 17, 1995Nov 12, 1996Telefonaktiebolaget Lm EricssonSystem and method for providing priority access and channel assignment in a cellular telecommunication systemUS5583869 *Sep 30, 1994Dec 10, 1996Motorola, Inc.Method for dynamically allocating wireless communication resourcesUS5615249 *Nov 30, 1994Mar 25, 1997Lucent Technologies Inc.Service prioritization in a cellular telephone systemUS5694455 *Oct 3, 1996Dec 2, 1997Bell Atlantic Network Services, Inc.Mobile audio program selection system using public switched telephone networkUS5729541 *Jun 5, 1995Mar 17, 1998Nokia Mobile Phones Ltd.System for transmitting packet data in radio telephone TDMA systemsUS5732073 *Oct 30, 1995Mar 24, 1998Hitachi, Ltd.Slots assignment method for control channel signal in mobile telecommunication system and base station employing the slots assignment methodUS5742588 *Sep 18, 1995Apr 21, 1998Telefonaktiebolaget Lm EricssonPacket switched traffic management in a cellular telecommunications systemUS5761618 *Dec 22, 1994Jun 2, 1998Bell Atlantic Mobile Systems, Inc.Updating technique for downloading new system identification (SID) list into a handsetUS5914945 *Dec 31, 1996Jun 22, 1999Northern Telecom LimitedMethod and system for bandwidth allocation for multimedia services under aggregate traffic conditionsUS5926469 *Nov 12, 1996Jul 20, 1999Telefonaktiebolaget L/M Ericssoon (Publ)Channel resource management within a digital mobile communications networkUS6009331 *Mar 31, 1997Dec 28, 1999Nec CorporationCommunication system having means for enabling channel assignment to calling terminal according to priorityUS6192248 *Mar 24, 1997Feb 20, 2001Lucent Technologies Inc.Service customization in a wireless communication systemUS6226277 *May 22, 1998May 1, 2001Lucent Technologies Inc.Method for admitting new connections based on usage priorities in a multiple access system for communications networksUS6304578 *May 1, 1998Oct 16, 2001Lucent Technologies Inc.Packet routing and queuing at the headend of shared data channelUS6321093 *Jul 28, 1999Nov 20, 2001Samsung Electronics Co., Ltd.System and method for controlling priority calls in a wireless networkUS6363065 *Nov 10, 1999Mar 26, 2002Quintum Technologies, Inc.okApparatus for a voice over IP (voIP) telephony gateway and methods for use thereinUS6377548 *May 22, 1998Apr 23, 2002Lucent Technologies Inc.Method for admitting new connections based on measured quantities in a multiple access system for communications networksUS6567416 *May 22, 1998May 20, 2003Lucent Technologies Inc.Method for access control in a multiple access system for communications networksUS6665293 *Sep 21, 2001Dec 16, 2003Quintum Technologies, Inc.Application for a voice over IP (VoIP) telephony gateway and methods for use thereinUS6856628 *Oct 26, 2000Feb 15, 2005Motorola, Inc.Method and apparatus for tunneling packets in a packet data systemUS6885657 *Nov 30, 1999Apr 26, 2005Broadcom CorporationNetwork telephony systemUS7209437 *Oct 11, 1999Apr 24, 2007British Telecommunications Public Limited CompanyComputer communication providing quality of service* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7725491 *Aug 12, 2002May 25, 2010Lundberg James CCritical resource managementUS7809387 *Sep 22, 2003Oct 5, 2010Research In Motion LimitedMethods and apparatus for prioritizing voice call requests during data communication sessions with a mobile deviceUS7933620 *Feb 27, 2004Apr 26, 2011Research In Motion LimitedTransmit channel request messaging for half-duplex voice communications systemsUS7970107 *Jun 28, 2011On-Q Telecom Systems Co., Inc.Method and system for automated and selective determination of call completion servicesUS8099118Jan 17, 2012Research In Motion LimitedMethods and apparatus for prioritizing voice call requests during data communication sessions with a mobile deviceUS8185157 *May 22, 2012Spreadtrum Communications (Shanghai) Co., Ltd.Method of dealing with business conflict of dual-card-dual-standby mobile phoneUS8335530Dec 18, 2012Research In Motion LimitedMethods and apparatus for prioritizing voice call requests during data communication sessions with a mobile deviceUS8547919 *Sep 3, 2008Oct 1, 2013Telefonaktiebolaget Lm Ericsson (Publ)Method for allocating communication bandwidth and associated apparatusesUS8577404Jul 13, 2009Nov 5, 2013Qualcomm IncorporatedPrioritization of group communications at a wireless communication deviceUS8687573May 30, 2008Apr 1, 2014Nokia Siemens Networks OyAllocating resources within communication systemUS8738058Mar 30, 2010May 27, 2014Qualcomm IncorporatedHigh-priority communications sessions within a wireless communications systemUS8755831Mar 22, 2010Jun 17, 2014QYALCOMM IncorporatedSelectively allocating data channel resources to wireless communication devices within a wireless communications systemUS8799324 *Jan 16, 2004Aug 5, 2014Verizon Patent And Licensing Inc.Method and system for mobile telemetry device prioritized messagingUS9014741Mar 8, 2013Apr 21, 2015Qualcomm IncorporatedPrioritization of group communications at a wireless communication deviceUS9066313Dec 21, 2011Jun 23, 2015Ntt Docomo, Inc.Base station, radio communication system, and communication methodUS9313237Jun 11, 2014Apr 12, 2016Tencent Technology (Shenzhen) Company LimitedMethod, apparatus, and communication system for allocating and managing voice channelsUS9326189Feb 4, 2013Apr 26, 2016Seven Networks, LlcUser as an end point for profiling and optimizing the delivery of content and data in a wireless networkUS9380125Sep 11, 2012Jun 28, 2016Qualcomm IncorporatedApparatus and method for delivery control of application data to a mobile device in a communication networkUS9398491Sep 13, 2006Jul 19, 2016Nokia Technologies OyMethods and apparatus for resource allocation based on changeable service levelsUS9407713Jan 16, 2012Aug 2, 2016Seven Networks, LlcMobile application traffic optimizationUS9426632Jan 23, 2014Aug 23, 2016Qualcomm IncorporatedPrioritization of group communications at a wireless communication deviceUS20050064891 *Sep 22, 2003Mar 24, 2005Chaudry Shahid R.Methods and apparatus for prioritizing voice call requests during data communication sessions with a mobile deviceUS20050190723 *Feb 27, 2004Sep 1, 2005Rao Padakandla K.Transmit channel request messaging for half-duplex voice communications systemsUS20050251579 *Jan 16, 2004Nov 10, 2005Huey-Jiun NgoMethod and system for mobile telemetry device prioritized messagingUS20060052103 *Sep 8, 2005Mar 9, 2006Nec CorporationCommunication network, radio base station, radio network controller and resource management method thereforUS20060274713 *May 31, 2006Dec 7, 2006Motorola, Inc.Methods of channel access in a meshed networkUS20070047695 *Aug 7, 2006Mar 1, 2007On-Q Telecom System Co., Inc.Method and system for automated and selective determination of call completion servicesUS20080076421 *Sep 13, 2006Mar 27, 2008Nokia CorporationAccess controlUS20090156256 *Dec 13, 2008Jun 18, 2009Spreadtrum Communications (Shanghai) Co., Ltd.Method of dealing with business conflict of dual-card-dual-standby mobile phoneUS20090228545 *Mar 4, 2009Sep 10, 2009Mendez Jose AOnline mobile applications capable of dealing with occasional disconnectsUS20100016008 *Jan 21, 2010Qualcomm IncorporatedPrioritization of group communications at a wireless communication deviceUS20100218210 *Feb 22, 2010Aug 26, 2010Xcast Labs, Inc.Emergency broadcast systemUS20100248771 *Mar 22, 2010Sep 30, 2010Qualcomm IncorporatedSelectively allocating data channel resources to wireless communication devices within a wireless communications systemUS20100255826 *Mar 30, 2010Oct 7, 2010Qualcomm IncorporatedHigh-priority communications sessions within a wireless communications systemUS20110021204 *Oct 4, 2010Jan 27, 2011Research In Motion LimitedMethods And Apparatus For Prioritizing Voice Call Requests During Data Communication Sessions With A Mobile DeviceUS20110075744 *May 30, 2008Mar 31, 2011Daniela LaselvaAllocating Resources Within Communication SystemUS20110141999 *Sep 3, 2008Jun 16, 2011Telefonaktiebolaget L M Ericsson (Publ)Method for allocating communication bandwidth and associated apparatusesUS20120149352 *Jun 14, 2012Ari BackholmContext aware traffic management for resource conservation in a wireless networkUS20140018071 *Mar 3, 2011Jan 16, 2014Nokia Siemens Networks OyScheduling in Coordinated Multi-Point Transmission SchemeCN102356684A *Mar 24, 2010Feb 15, 2012高通股份有限公司Selectively allocating data channel resources to wireless communication devices within a wireless communications systemEP1635602A1 *Sep 7, 2005Mar 15, 2006Nec CorporationCommunication network, radio base station, radio network controller and resource management method thereforEP2658337A1 *Dec 21, 2011Oct 30, 2013Ntt Docomo, Inc.Base station, wireless communication system, and communication methodWO2008031919A1 *Aug 30, 2007Mar 20, 2008Nokia CorporationAccess controlWO2009143900A1 *May 30, 2008Dec 3, 2009Nokia Siemens Networks OyAllocating resources within a communication systemWO2010111420A1 *Mar 24, 2010Sep 30, 2010Qualcomm IncorporatedSelectively allocating data channel resources to wireless communication devices within a wireless communications systemWO2012021873A1 *Aug 13, 2011Feb 16, 2012T-Mobile Usa, Inc.Prioritization of data communicationWO2014043091A1 *Sep 10, 2013Mar 20, 2014Qualcomm IncorporatedApparatus and method for delivery control of application data to a mobile device in a communication networkWO2014183438A1 *Dec 18, 2013Nov 20, 2014Tencent Technology (Shenzhen) Company LimitedMethod, apparatus, and communication system for allocating and managing voice channelsWO2015018091A1 *Aug 9, 2013Feb 12, 2015Huawei Technologies Co., Ltd.Competition method for service channel resource and communication device* Cited by examinerClassifications U.S. Classification370/389International ClassificationH04L12/56, H04W8/18, H04W4/06, H04W28/14, H04W72/10Cooperative ClassificationH04W4/06, H04W72/10, H04W8/18, H04W28/14European ClassificationH04W72/10Legal EventsDateCodeEventDescriptionJan 14, 2008ASAssignmentOwner name: AT&T DELAWARE INTELLECTUAL PROPERTY, INC., DELAWARFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZELLNER, SAM;REEL/FRAME:020359/0545Effective date: 20080111Aug 24, 2011FPAYFee paymentYear of fee payment: 4Aug 25, 2015FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services

value: This website is a search engine provided by Google. Handling over 3.5 billion searches per day, it has a 92% share of the global search engine market.


text:
Amazon.com: Accessories - PlayStation 3: Video Games: Skins, Controllers, Cases & Protectors, Cables & Adapters & More
Video GamesFire TVXbox OneXbox 360PS4PS3Wii UWii3DSPS VitaDigital GamesKindle Fire GamesDealsBest SellersPre-ordersTrade-In PlayStation 3 (PS3) Controllers, Headsets and More
1-12 of 10,824 results for Video Games
PlayStation 3 DualShock 3 wireless controller - Metallic Gold by Sony Computer Entertainment
PlayStation 3 Dualshock 3 Wireless Controller (Classic White) by Sony Computer Entertainment
Trade in this item for up to: $3.27 for White
PlayStation 3 Dualshock 3 Wireless Controller (Red) by Sony Computer Entertainment
Trade in this item for up to: $6.62 for Red
PlayStation 3 Dualshock 3 Wireless Controller (Candy Pink) by Sony Computer Entertainment
Trade in this item for up to: $0.22 for Pink
Grip-iT Analog Stick Covers by Total Control
ASTRO Gaming A50 Wireless Headset by ASTRO Gaming
Trade in this item for up to: $130.28 for Xbox 360
Playstation Move Motion Controller by Sony Computer Entertainment
Accessory Kits (478)
Batteries & Chargers (456)
Cables & Adapters (537)
Cases & Protectors (1,101)
Controllers (2,272)
Skins (4,848)
$10 to $15 (1,757)
$15 to $25 (2,486)
$25 to $35 (279)
$35 & Above (906)
Fake Accessorirs

value: This website is an American multinational technology company which focuses on e-commerce, cloud computing, digital streaming, and artificial intelligence.


text:
Old toilet Seat in room 315
“Clean, peaceful, quiet suites”
“Not a fan of being stuck in the handicapped room!”
“Very good overall. Nice staff”
Photo: “Old toilet Seat in room 315
Residence Inn (Franklin...
“For a visit to Boston”	05/23/2017
“Stayed for a hockey tournament.”	05/14/2017
15 helpful votes “Residence Inn (Franklin, MA)”
I've stayed at this hotel once before a few years ago (and enjoyed it) - but my latest visit to the hotel again last week left me with a very different impression. My room (315) was clean but the bathroom was absolutely atrocious. The toilet seat in this room (when raised) was dirty, full of rotting...
More Helpful? Thank eciarma Report Colwen_Management, General Manager at Residence Inn Boston Franklin, responded to this review
I am very sorry to hear that we did not meet your expectation and
Deliver the service you received before.
We pride ourselves with a clean product and a great service therefore this matter
Will be looked into closely and necessary actions will be taken.
I thank you again for...
More Been to Residence Inn Boston Franklin? Share your experience!
Add Photo See all 371 reviews of Residence Inn Boston Franklin Explore similar hotels Hampton Inn Franklin 473 ReviewsShow Prices 2.6 miles Hawthorn Suites by Wyndham Franklin / Milford Area 976 ReviewsShow Prices 2.8 miles Doubletree by Hilton Boston Milford 584 ReviewsShow Prices 5.1 miles See all Franklin hotels Know better. Book better. Go better. © 2017 TripAdvisor LLC All rights reserved. Terms of Use | Privacy Policy | Site Map* TripAdvisor LLC is not a booking agent and does not charge any service fees to users of our site... (more) TripAdvisor LLC is not responsible for content on external web sites. Taxes, fees not included for deals content. EXPLOREAbout UsHelp CenterCURRENCY/COUNTRY$USDUnited States

value: This website is an American online travel company that operates a website and mobile app with user-generated content and a comparison shopping website.


text:
Patent US4778698 - Innerseal for container for use with liquid contents - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inAdvanced Patent SearchPatentsInnerseal suitable for use with containers made from glass. The innerseal of this invention comprises a facing bearing a layer of amorphous polyester on one major surface thereof. The innerseal forms a strong bond to glass and resists moisture better than do conventional innerseals....http://www.google.com/patents/US4778698?utm_source=gb-gplus-sharePatent US4778698 - Innerseal for container for use with liquid contentsAdvanced Patent SearchPublication numberUS4778698 APublication typeGrantApplication numberUS 07/030,730Publication dateOct 18, 1988Filing dateMar 26, 1987Priority dateMar 26, 1987Fee statusLapsedPublication number030730, 07030730, US 4778698 A, US 4778698A, US-A-4778698, US4778698 A, US4778698AInventorsDavid T. Ou-YangOriginal AssigneeMinnesota Mining And Manufacturing CompanyExport CitationBiBTeX, EndNote, RefManPatent Citations (17), Referenced by (39), Classifications (22), Legal Events (7) External Links: USPTO, USPTO Assignment, EspacenetInnerseal for container for use with liquid contents
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS2937481 *Jun 19, 1958May 24, 1960Fr CorpMethod of producing a packageUS3832314 *Aug 10, 1972Aug 27, 1974Du PontSegmented copolyester adhesive and coating compositionsUS3932326 *Feb 6, 1974Jan 13, 1976E. I. Du Pont De Nemours And CompanySoft thermoplastic segmented copolyesters as pressure sensitive adhesivesUS3959062 *Jun 13, 1974May 25, 1976E. I. Du Pont De Nemours And CompanyMethod of joining surfaces using segmented copolyester adhesiveUS4048128 *Nov 21, 1975Sep 13, 1977E. I. Du Pont De Nemours And CompanyThermally stabilized segmented copolyester adhesiveUS4322003 *Mar 26, 1980Mar 30, 1982Ludlow CorporationLaminate with heat-sealable polyester foil and packageUS4324601 *Feb 10, 1981Apr 13, 1982Brockway Glass Company, Inc.Preparation of glass container for thermoplastic closureUS4442129 *Jan 25, 1982Apr 10, 1984Kabushiki Kaisha Hosokawa YokoProcess for sealing glass container openingsUS4503123 *Aug 22, 1983Mar 5, 1985Minnesota Mining And Manufacturing CompanyInner seal for capped containersUS4523689 *Feb 27, 1984Jun 18, 1985Herman LaubReusable tamper-proof containerUS4579240 *Nov 9, 1984Apr 1, 1986Minnesota Mining And Manufacturing CompanyTamper indicating cap assemblyUS4588465 *Feb 4, 1983May 13, 1986Minnesota Mining And Manufacturing CompanyMethod for forming a sealed containerUS4596338 *Jul 8, 1985Jun 24, 1986Bahjat YousifAir permeable container cap lining and sealing materialUS4666052 *May 23, 1985May 19, 1987Minnesota Mining And Manufacturing CompanyTamper indicating cap assemblyUS4684554 *Apr 12, 1985Aug 4, 1987Minnesota Mining And Manufacturing CompanyPolymeric coating for container induction innersealUS4686133 *Feb 22, 1985Aug 11, 1987Takeda Chemical Industries, Ltd.Closure material for sealing glass containersUS4693385 *May 6, 1985Sep 15, 1987Nyffeler CortiSterilization-resistant glass container sealed with an aluminum composite film* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS4863061 *Jan 3, 1989Sep 5, 1989Phoenix Closures, Inc.Closure liner with pull tabUS4934544 *Feb 27, 1989Jun 19, 1990Minnesota Mining And Manufacturing CompanyZ-tab innerseal for a container and method of applicationUS4961986 *Mar 2, 1988Oct 9, 1990Stanpac Inc.Sealing member for a containerUS5004111 *Feb 27, 1989Apr 2, 1991Minnesota Mining & Manufacturing CompanyInternally delaminating tabbed innerseal for a container and method of applyingUS5057365 *Jul 12, 1989Oct 15, 1991501 Tri-Seal International, Inc.Cap liner and process for using cap liner to seal containersUS5121845 *Oct 16, 1990Jun 16, 1992Blanchard Floyd WRemovable seal for liquid containerUS5230427 *Jun 12, 1991Jul 27, 1993Ppg Industries, Inc.Sterilizable hermetically-sealed substantially glass containerUS5372268 *Apr 8, 1992Dec 13, 1994Minnesota Mining And ManufacturingPull tab innersealUS5433992 *Oct 14, 1992Jul 18, 1995Stanpac Inc.Sealing member for a containerUS5514442 *Nov 15, 1993May 7, 1996Stanpac, Inc.Sealing member for a containerUS5560989 *Sep 22, 1994Oct 1, 1996Minnesota Mining And Manufacturing CompanyMultilayer innerseal facingUS5603422 *Mar 1, 1993Feb 18, 1997Herrmann; ErnstPlastic safety closure for bottles simulating the appearance of a traditional cork-type wine bottle closureUS5712042 *Apr 17, 1995Jan 27, 1998Kerr Group Inc.Second seal for closure linersUS5720401 *Oct 21, 1996Feb 24, 1998Phoenix Closures, Inc.Foam front heat induction foilUS5797509 *Feb 18, 1997Aug 25, 1998Phoenix Closures, Inc.Closure package having a crimped liner pull tab and forming method thereforUS5915577 *Apr 30, 1997Jun 29, 1999Selig Sealing Products, Inc.Separating seal system for containers and method of making sameUS6096358 *Oct 8, 1997Aug 1, 2000Abbott LaboratoriesMethod of manufacturing an aseptically sterilized package containing a liquid nutritional productUS6131754 *Dec 15, 1998Oct 17, 2000Illinois Tool Works Inc.Synthetic two-piece induction sealUS6277478 *Nov 9, 1998Aug 21, 2001Taihei Paper ManufacturingContainer closure system with inner seal in capUS6428864 *Mar 29, 2001Aug 6, 2002Toyo Glass Company, LimitedGlass bottle for high-frequency heat sealingUS6908001Nov 21, 2002Jun 21, 2005Phoenix Closures, Inc.Narrow pull tabUS7267858 *Jun 18, 2004Sep 11, 2007Kureha CorporationPackaging material for and packaged product of medical supplies and the likeUS7648764Jun 30, 2005Jan 19, 2010Uchicago Argonne, LlcTwo-piece container seal and method of manufactureUS7713605Dec 9, 2004May 11, 2010Tech-Seal Products, Inc.Container seal with integral, heat-releasable promotional token and methodUS7740927Dec 9, 2004Jun 22, 2010Tech-Seal Products, Inc.Container seal with integral promotional token and methodUS7798359Jul 28, 2005Sep 21, 2010Momar Industries LLCHeat-sealed, peelable lidding membrane for retort packagingUS7819266Dec 9, 2004Oct 26, 2010Tech-Seal Products, Inc.Container sealing material having a heat-releasable interlayerUS7832580Sep 13, 2004Nov 16, 2010Brian Francis JackmanTamper evident container seal with integral pull openerUS7960001Mar 18, 2010Jun 14, 2011Tech-Seal Products, Inc.Container seal with integral promotional token and methodUS8080118Jan 14, 2010Dec 20, 2011Tech-Seal Products, Inc.Two-piece container seal and method of manufactureUS8113367 *Feb 20, 2007Feb 14, 2012Con Agra Foods RDM, Inc.Non-removable closure having a dispensing aperture extending therethroughUS20040099630 *Nov 21, 2002May 27, 2004Moore David N.Narrow pull tabUS20050013953 *Jun 18, 2004Jan 20, 2005Saichi OnoPackaging material for and packaged product of medical supplies and the likeUS20050025393 *Jul 29, 2003Feb 3, 2005Aaron HeynigerBag apparatusUS20120048825 *Aug 29, 2011Mar 1, 2012Kristi Bina AverettLong-term packaging of food for consumer useUS20120193267 *Sep 22, 2010Aug 2, 2012Boehringer Ingelheim International GmbhInduction seal diskUS20130032565 *Apr 26, 2011Feb 7, 2013Obrist Closures Switzerland GmbhSealCN100438847CJun 18, 2004Dec 3, 2008株式会社吴羽Packaging material for and packaged product of medical supplies and the likeWO2004020307A2 *Aug 15, 2003Mar 11, 2004Rjr Packaging LlcLidding components for containers* Cited by examinerClassifications U.S. Classification428/34.4, 215/347, 428/35.1, 428/458, 428/344, 215/232, 428/349International ClassificationB65D77/20, B65D23/02, B65D51/20Cooperative ClassificationY10T428/31681, B65D2251/0093, Y10T428/1331, B65D51/20, B65D2251/0015, Y10T428/2804, B65D2577/205, Y10T428/2826, Y10T428/131, B65D23/02European ClassificationB65D23/02, B65D51/20Legal EventsDateCodeEventDescriptionMar 26, 1987ASAssignmentOwner name: MINNESOTA MINING AND MANUFACTURING COMPANY, SAINTFree format text: ASSIGNMENT OF ASSIGNORS INTEREST.;ASSIGNOR:OU-YANG, DAVID T.;REEL/FRAME:004684/0482Effective date: 19870326Nov 12, 1991FPAYFee paymentYear of fee payment: 4May 28, 1996REMIMaintenance fee reminder mailedOct 20, 1996LAPSLapse for failure to pay maintenance feesDec 9, 1996ASAssignmentOwner name: MASSMUTUAL CORPORATE INVESTORS, MASSACHUSETTSFree format text: SECURITY AGREEMENT;ASSIGNOR:UNIPAC CORPORATION;REEL/FRAME:008261/0147Effective date: 19960209Owner name: MASSMUTUAL PARTICIPATION INVESTORS, MASSACHUSETTSFree format text: SECURITY AGREEMENT;ASSIGNOR:UNIPAC CORPORATION;REEL/FRAME:008261/0147Effective date: 19960209Owner name: MASSACHUSETTS MUTUAL LIFE INSURANCE COMPANY, MASSAFree format text: SECURITY AGREEMENT;ASSIGNOR:UNIPAC CORPORATION;REEL/FRAME:008261/0147Effective date: 19960209Dec 31, 1996FPExpired due to failure to pay maintenance feeEffective date: 19961023Jan 18, 2000ASAssignmentRotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services